Resource Booking and Locking in Microsoft Teams

If your company runs on Microsoft 365, the first instinct for "how do we share X" is to look for a Microsoft answer. For meeting rooms there's a good one. For desks there's a newer one. For a staging server, a test phone or a single licence seat, the Microsoft stack has no built-in concept, and teams end up improvising in a channel.

This guide walks through what Microsoft provides (checked against Microsoft documentation in October 2026), where each option fits, and how to handle the engineering resources that don't belong on a calendar.

Option 1: Room mailboxes and Room Finder

Meeting rooms in Microsoft 365 are typically room mailboxes in Exchange Online. People book them by adding the room to a meeting in Outlook, usually through the Scheduling Assistant and Room Finder, and the room accepts or declines based on availability. A Teams meeting scheduled from Outlook or Teams can include a room the same way.

Good for: scheduled meetings in physical rooms, booked ahead, with conflict detection.

Limits: it's a calendar. It handles "Room 4, Tuesday at 2" well. It doesn't fit things that aren't rooms, and it's not designed for "I'm taking this for the next hour" claims on non-space resources.

Option 2: Microsoft Places

Microsoft Places covers hybrid-office coordination: finding rooms and desks, seeing who's in the office, and booking workspaces.

Licensing changed in 2026. According to Microsoft's message center post MC1235124, Places moved from a per-user to a per-space licensing model, with general availability on April 1, 2026. Places Finder and the Places app became available across most user licences without Teams Premium. More advanced functionality, including desk reservation, auto-release policies for desks and rooms, and space-based analytics, requires a Shared Space licence. Existing Teams Premium customers keep their current Places capabilities until their subscription renews.

Good for: offices that want desk booking, room finding and attendance visibility inside the Microsoft stack.

Limits: it's about physical space. It won't track who holds the QA environment. Check which features need Shared Space licences for the spaces you care about before rolling it out.

Option 3: Microsoft Bookings

Bookings is sometimes suggested for internal resource sharing because it has "booking" in the name. Microsoft's service description describes it as a tool for scheduling and managing appointments: a web booking page, staff and service management, notifications, and a Bookings app in Teams.

Good for: appointment-style scheduling, such as IT help desk slots, office hours, or customer meetings with staff.

Limits: it models staff and services, not things. You can bend it into booking a shared device by treating the device as a "staff member," but you get an appointment system with booking pages, not a live view of who holds what.

Option 4: A list or tracker in a channel

Many teams create a Microsoft List or a channel tab with a table of resources, an "In use by" column and a "Until" column. It's visible, everyone has access, and it costs nothing.

It's also a spreadsheet, with all the usual problems: nothing expires, people forget to clear their row, and there's no way to be notified when something frees up. We wrote about this failure mode in the spreadsheet alternative for environment booking.

Where engineering resources fall through

None of the Microsoft options model these well:

• Dev, QA and staging environments
• Shared databases and test tenants
• Test devices and hardware dev boards
• Single licence seats of a tool
• Build agents or VMs that can run one job at a time

What these need is simpler than a calendar: one holder at a time, a visible end time, a way to be told when it's free, and a polite way to ask for it.

Option 5: A lock bot in Teams

Lockit is a chat bot for exactly that. Each shared thing is a named resource. You lock it, it shows you as the holder until an end time, and you release it when you're done. It also runs in Slack and Discord.

Getting access

Lockit for Microsoft Teams is available on request rather than through self-serve install. Email hello@lockitbot.com with your company name and we set it up with you. Setup and usage guides are in the docs.

Using it

In a channel, mention the bot:

@Lockit lock qa-env 2 hours

In a one-to-one chat with Lockit, leave the mention out:

lock qa-env 2 hours

Lockit replies with an Adaptive Card. Lock end times on the card are shown in each reader's own timezone, which matters more than it sounds. When the holder is in London and the person waiting is in Bangalore, "locked until 17:00" is ambiguous. The card shows each reader the time that applies to them.

When it's taken

The card shows who holds the resource and until when, with two buttons:

• Alert when released tells you as soon as it's free.
• Ask for takeover sends the holder a request with Release and Approve and Reject Request buttons.

On Teams, approving a takeover locks the resource straight to the requester, so nobody can grab it in between.

Details that differ from Slack

• Resource names match case-insensitively. QA-Env and qa-env are the same resource.
• Creating a resource with new defaults its updates channel to the channel you're in, so create resources where the team will see lock and release updates.
• A resource can have admins. When it does, only an admin or the creator can delete it.

Lock durations

Every lock ends. Lockit uses the duration you give, else the resource's default, else the workspace default, else 48 hours. For a busy QA environment, a short default keeps forgotten locks from blocking the next person all day.

What it doesn't do

• No calendar integration and no future-dated reservations. You lock something when you start using it.
• No Outlook room mailbox or Places integration. Keep meeting rooms where they are.
• No REST API or MCP server for Teams yet. Those work with Slack workspaces only for now, so CI-driven locking currently needs Slack.

Which to use for what

Resource	Best fit in a Microsoft shop
Meeting rooms booked ahead	Room mailboxes in Outlook / Teams meetings
Desks and office attendance	Microsoft Places (check Shared Space licensing)
Appointment-style slots with staff	Microsoft Bookings
Environments, devices, licence seats, build agents	A lock bot such as Lockit
Low-stakes, rarely contested items	A list in a channel tab

A worked example

A team of twelve across London and Bangalore shares qa-env, uat-env and two test phones. Before, they coordinated in a channel thread that was never up to date.

After setup:

1. Each of the four resources is created from the Engineering > Environments channel, so every lock and release lands there.
2. qa-env gets a two-hour default; the phones get end of working day.
3. A London engineer locks qa-env for 90 minutes in the morning. The card in Bangalore shows the end time in IST, so nobody does timezone arithmetic.
4. A Bangalore tester who needs it clicks Alert when released and picks up other work.
5. When a release is blocked, they use Ask for takeover with a one-line reason in the channel. The holder approves, and qa-env is locked straight to the tester.

Nothing here needs a calendar, because none of it is planned in advance.

Rollout tips for Teams

1. Pick one channel. Create resources from a channel the engineering team already reads, like Engineering > Environments. Lock and release updates land there.
2. Start with the most contested resource. Usually the shared QA or staging environment. Get people used to locking it before adding devices and licences.
3. Set short defaults on busy resources. One or two hours for environments, end of day for devices.
4. Write the convention down. A pinned post: "Lock before you deploy to QA. Release when you're done. Use Ask for takeover only if you're blocked."

For deeper reading on the environment side, see how to manage shared staging environments and our QA environment scheduling guide. Plans are on the pricing page: free for two resources, $17/month for up to 100.

FAQ

Can Lockit book Teams meeting rooms?

Not as calendar bookings. You can create a room as a Lockit resource for first-come use, but Lockit doesn't connect to room mailboxes, Outlook or Places. For rooms booked in advance, use Outlook or Places.

Is Lockit in the Teams app store?

Teams access is set up on request. Email hello@lockitbot.com and we'll get your tenant running.

Can I use the Lockit API with Teams?

Not yet. The API and MCP server currently work with Slack workspaces only.

Do people in different timezones see the right end time?

Yes. Lockit's Teams cards show lock times in each reader's own timezone.