Microsoft 365 Places: Setup, Policies, and Admin Configuration Guide 2026
Why Microsoft 365 Places Is So Hard to Get Working
I've seen this exact scenario play out in dozens of enterprise tenants: an IT admin rolls out Microsoft 365 Places, users open Teams or the new Outlook, and , nothing. No desk booking panel. No Places finder. No work location sharing. Sometimes there's a vague error, but more often it's just a blank screen or a missing menu option that was definitely supposed to be there.
The frustration is real. Microsoft 365 Places is genuinely one of the most powerful tools for managing hybrid workspaces, it surfaces who's coming into the office, lets people book individual desks in advance, tracks actual room occupancy versus what was reserved, and feeds AI-powered recommendations into Copilot. But getting it fully functional requires threading together three separate configuration layers, licensing, the Places building hierarchy, and feature-specific policies, and if any one of those layers has a gap, the whole thing goes dark for users.
The error messages don't help. When a user can't access the Places app or book a desk, Microsoft doesn't show them "you haven't been assigned a space license yet" or "your mailbox is on Exchange on-premises, which blocks this feature." They just see a missing button or a dead-end screen. The diagnostic burden lands entirely on the admin, which is exactly why you're here.
The most common reasons Microsoft 365 Places features fail to appear or behave unexpectedly include:
- Missing or mismatched licenses, especially now that the April 2026 transition has moved several features from per-user Teams Premium to a per-space model. If your building's desks haven't been assigned a Microsoft Teams Shared Space (MTSS) or MTSS-SS license, nobody can book them regardless of what their user license says.
- Incomplete building hierarchy, Places depends on a fully configured structure of buildings, floors, and rooms/workspaces/desks. Skip even one level and the finder, booking, and analytics features will silently fail or simply not show up.
- Exchange on-premises mailboxes, this one catches a lot of hybrid organizations off guard. If a user's mailbox is hosted on Exchange on-premises rather than Exchange Online, Places features are completely unavailable to them. No Places app access, no Places finder, no work plan sharing with colleagues.
- Policy gaps, features like automatic work location detection require specific Teams policies to be enabled and assigned. They won't just turn on by themselves.
- Propagation delays, license and policy changes in Microsoft 365 can take up to 24 hours to fully propagate. A lot of "it's not working" tickets are actually "it hasn't applied yet" tickets.
The good news is that every single one of these is fixable. And with the April 2026 licensing changes now in effect, bringing Places Explorer, Places Finder, and most analytics features to the Core tier, this is actually a great time to revisit your Places configuration and unlock capabilities your users didn't have before. Browse all Microsoft fix guides →
The Quick Fix, Try This First
Before spending an hour in PowerShell, run through this fast diagnostic. It catches the majority of Microsoft 365 Places setup problems in under five minutes.
Open the Microsoft 365 Admin Center (admin.microsoft.com). Navigate to Users > Active users, find an affected user, and click their name. Under the Licenses and apps tab, confirm they hold at least one of these plans: Microsoft 365 Business Basic, Standard, or Premium; Microsoft 365 E1, E3, or E5; Teams Enterprise; Teams Essentials; or one of the frontline F1/F3 plans. If none of those are checked, that's your problem, assign the appropriate license and wait up to 24 hours.
If the license looks correct, your next check is the Places building hierarchy. Go to the Microsoft Places Management Portal, which you can reach directly from the Places app in Teams (requires the Places admin or Global admin role). Click Buildings in the left navigation. If this list is empty, that's the root cause. No buildings configured means no Places features for anyone, regardless of licensing.
Next, and this one is easy to miss, check whether the affected user has an Exchange Online mailbox or an on-premises mailbox. In the Microsoft 365 Admin Center, under Users > Active users, look at the user's mailbox type. If it says "On-premises," Places features simply won't work for that person. Work location sharing changes they make in Teams are visible only to themselves, not to colleagues, a silent, frustrating limitation that won't go away until the mailbox is migrated to Exchange Online.
Finally, confirm that Places features haven't been administratively disabled at the policy level. In the Teams Admin Center (admin.teams.microsoft.com), go to Teams apps > Setup policies and check that the Places app is installed or pinned in the policy assigned to your users. If Places isn't in the app setup policy, it simply won't appear in the Teams sidebar for those users.
Getting licensing right is the foundation. With the April 2026 changes now active, the Places licensing picture is significantly different from how it worked even six months ago, so this step is worth doing carefully even if you've already reviewed licenses before.
Core features, work plans, workplace presence, in-person events, hybrid RSVP, Places card, room and workspace booking (desk pools), desk assignment, and now also Places Explorer and Places Finder, are available to any user holding a supported Microsoft 365 or Teams license. No Teams Premium required for these anymore. That's a meaningful change if you've been holding back the Places rollout because of Premium costs.
Individual desk booking and Autorelease, however, now operate on a per-space model rather than per-user. Each desk you want to make bookable needs its own Microsoft Teams Shared Space (MTSS) or Microsoft Teams Shared Space – Single Space (MTSS-SS) license assigned to it. Here's the exact path to check this in the Microsoft 365 Admin Center:
# Check which resource accounts have space licenses assigned
# Run in Exchange Online PowerShell after connecting with Connect-ExchangeOnline
Get-Place -Type Desk | Select-Object DisplayName, Identity, IsManaged | Format-Table -AutoSizeFor the transition period (which started April 2026), any user who held a Teams Premium license before April 2026 can still book any desk until their Teams Premium subscription renews. After renewal, they'll need desks to have the MTSS or MTSS-SS license attached. Build that migration into your renewal planning now.
Copilot room booking and Quick Book features require a Microsoft 365 Copilot license for the user, this is separate from space licenses and unaffected by the April 2026 changes. If your executives or power users want AI-powered room recommendations, that's the license they need.
After assigning or changing any licenses, allow up to 24 hours for propagation. You can verify the assignment took effect by asking the affected user to open the Places app in Teams and attempt to access Places Finder, if it loads, the license is active.
I cannot stress this enough, the building hierarchy is the spine of the entire Microsoft 365 Places experience. Without it, most features simply don't function. Individual desk booking, Places Finder, occupancy analytics, Autorelease, all of them depend on having a complete, correctly structured hierarchy of buildings, floors, and rooms or workspaces.
You configure this through two paths: the Places Management Portal (the GUI option, easier for small deployments) and PowerShell with Set-PlaceV3 (essential for bulk configuration at scale). The Management Portal is accessible from within the Places app in Teams, click the settings gear, then Open Places Management. You need either the Global Administrator role or the specific Places Administrator role.
To create a building via PowerShell after connecting to Exchange Online:
# Connect first
Connect-ExchangeOnline -UserPrincipalName admin@yourtenant.onmicrosoft.com
# Create a building
New-Place -Type Building -Name "Headquarters - Chicago" -CountryOrRegion "US" -State "IL" -City "Chicago" -PostalCode "60601"
# Create a floor within that building (use the Identity of the building you just created)
New-Place -Type Floor -Name "Floor 3" -ParentId "building-guid-here" -FloorNumber 3
# Associate a room resource account with that floor
Set-PlaceV3 -Identity "conferenceroom3a@contoso.com" -ParentId "floor-guid-here"For individual desks, each desk needs its own room resource mailbox created in Exchange Online, then associated with a floor via Set-PlaceV3, and finally assigned a space license in the Microsoft 365 Admin Center. This is the step that most admins miss, the resource mailbox and the space license are separate requirements that must both be in place.
Once the hierarchy is built, give it 30–60 minutes before testing Places Finder with a licensed user. You should see the building appear in the finder interface with floor maps (if you've uploaded them) and available spaces listed by type and amenities.
This is the step that most admins hit a wall on after the April 2026 transition. User licenses are handled in the Microsoft 365 Admin Center under Users > Active users. Space licenses are completely different, they're assigned to room resource accounts, not to people. If you're looking for the space license assignment in the wrong place, you'll never find it.
Here's where to go: Microsoft 365 Admin Center > Billing > Licenses. Find your Microsoft Teams Shared Space (MTSS) or Microsoft Teams Shared Space – Single Space (MTSS-SS) licenses in the list. Click into the license, then click Assign licenses. In the search box that appears, search for your room or desk resource accounts by name or email address. These are the accounts you created in Exchange Online for each room and desk, not user accounts.
The relationship between MTSS and MTSS-SS matters here and it trips people up constantly. For every MTSS license you purchase, Microsoft includes 3 free MTSS-SS licenses, but there's a catch. If you assign that MTSS license to a Teams common area phone, you lose access to all 3 of those free MTSS-SS licenses. Assign the MTSS to a BYOD room or an individual desk, and all 3 free MTSS-SS licenses remain available for additional rooms or desks. Plan your license assignments around this rule to avoid burning your free allocations accidentally.
Once you've assigned space licenses, verify in PowerShell that the assignment registered:
# Check license assignment on a specific desk resource account
Get-MsolUser -UserPrincipalName "desk-3b@contoso.com" | Select-Object -ExpandProperty Licenses | Select-Object AccountSkuIdAfter confirming the license, test Autorelease behavior by making a test booking, not checking in within the release window, and verifying the desk shows as available again. The Autorelease grace period and behavior are configurable per-space through the Places Management Portal.
Work plans and workplace presence are Core features, meaning every supported Microsoft 365 license holder can use them, but automatic work location detection requires an admin to explicitly enable it at the policy level. This is a Teams policy, not an Exchange or Places-specific setting, and it lives in a different admin console than most Places configuration.
Go to Teams Admin Center (admin.teams.microsoft.com) and navigate to Teams policies in the left sidebar (you may see this under the Meetings or Calling section depending on your tenant). Look for Work location detection policies. The relevant policy type is CsTeamsWorkLocationDetectionPolicy. By default, auto-detection is off:
# Check current policy state
Get-CsTeamsWorkLocationDetectionPolicy
# Enable automatic work location detection for all users
Set-CsTeamsWorkLocationDetectionPolicy -Identity Global -EnableWorkLocationDetection $true
# Or create a specific policy for a group of users
New-CsTeamsWorkLocationDetectionPolicy -Identity "AutoDetect-Enabled" -EnableWorkLocationDetection $true
# Assign to a specific user
Grant-CsTeamsWorkLocationDetectionPolicy -Identity "user@contoso.com" -PolicyName "AutoDetect-Enabled"When automatic detection is active, the Teams desktop app checks for corporate Wi-Fi networks and supported peripherals (like certain certified headsets and docking stations) to automatically update a user's work location. Users see this as a notification asking them to confirm their location, it's not completely silent, which is good from a privacy standpoint.
Work plans, the feature where users set their schedule in advance so colleagues can see when they're planning to be in the office, are visible in the Calendar in new Outlook, Calendar in Teams, and the Places app itself. Users configure these themselves, but admins can control whether the feature is available through the Teams app setup policy. Make sure the Places app is pinned in the relevant setup policies so users have easy access to set their weekly work plans without digging through the app catalog.
Places analytics, visualizing actual versus intended occupancy for buildings, rooms, and workspaces, is now a Core feature for most of its functionality, following the April 2026 changes. However, the occupancy report specifically (which shows whether rooms and desks were actually used, based on sensor or badge data) still requires rooms and desks to have a space license (MTR, MTSS, or MTSS-SS).
To enable Places analytics for your organization, navigate to the Places Management Portal and look for the Analytics section in the left navigation. Microsoft's documentation notes that this feature needs to be "specifically enabled", it isn't on by default. Toggle the setting to enable it, and allow 24–48 hours for historical occupancy data to begin populating the dashboards.
Once enabled, Places analytics surfaces occupancy data at the building, floor, and individual room/desk level. You can see the delta between reservations made and actual check-ins, a powerful signal for right-sizing your real estate. For the occupancy data to be meaningful, you need either Microsoft-compatible occupancy sensors installed in rooms, or you need users actively checking in to their bookings through the Places app or Teams.
To verify analytics is active and pulling data, open the Places app in Teams, navigate to the Analytics tab, and check whether building-level data populates. If you see "No data available" for spaces that have been in use, check three things: the space license is assigned, the feature was explicitly enabled in the Management Portal, and sufficient time has passed since enablement (the first 48 hours often show sparse data).
# Verify rooms have the correct setup for occupancy tracking
Get-Place -Type Room | Select-Object DisplayName, Identity, Capacity, IsWheelChairAccessible, AudioDeviceName | Export-Csv -Path "C:\Temp\RoomAudit.csv" -NoTypeInformationAdvanced Troubleshooting for Microsoft 365 Places
When the standard fixes don't resolve a Microsoft 365 Places issue, these deeper-level diagnostics usually find the culprit.
Exchange Hybrid Environment Limitations
This deserves its own section because it's invisible in the error messages. In a hybrid Exchange environment, Places features work only for users whose mailbox is managed in Exchange Online. A user with an on-premises mailbox can open Teams, navigate to Calendar, even see the work location option, but any changes they make are visible only to themselves. Colleagues won't see their work location, their work plans won't sync, and they can't access the Places app or Places Finder at all.
Identifying affected users:
# Find users with on-premises mailboxes in a hybrid environment
Get-Recipient -ResultSize Unlimited | Where-Object {$_.RecipientTypeDetails -eq "UserMailbox" -and $_.IsDirSynced -eq $true} | Select-Object DisplayName, PrimarySmtpAddress, RecipientTypeDetails | Export-Csv -Path "C:\Temp\HybridUsers.csv" -NoTypeInformationThe only real fix is mailbox migration to Exchange Online. Until that happens, these users can continue using Room Finder in Outlook for basic room booking, but the full Places experience, including work plans, workplace presence sharing, individual desk booking, and Places analytics, remains unavailable to them.
Missing Places App in Teams, Policy Audit
If users can't find the Places app at all in Teams, the most likely cause is that it hasn't been added to their Teams app setup policy. Check this in Teams Admin Center > Teams apps > Setup policies. Look at the policy assigned to your users and confirm Places appears in the "Installed apps" or "Pinned apps" list. If it's not there, add it, click Add apps, search for "Places," and add it.
Also check whether there's a permission policy blocking the app. Under Teams apps > Permission policies, verify that Microsoft apps are allowed (or that Places specifically isn't blocked) in the policy assigned to affected users.
Desk Booking Showing as Unavailable Despite Available Desks
After the April 2026 transition, users outside the Teams Premium grandfathering window can only book desks that have an MTSS or MTSS-SS space license. If a desk appears in Places Finder but shows as unavailable or unselectable, check whether that specific desk resource account has a space license assigned. This is extremely common when an organization has a mix of licensed and unlicensed desks, some work fine, others silently refuse to be booked.
Event Viewer and Diagnostic Logs
For deep-dive diagnostics on the Teams client side, look in Event Viewer under Applications and Services Logs > Microsoft > Windows > Teams. Look for Event ID 4000 series errors relating to app loading failures. On the admin side, the Microsoft 365 Unified Audit Log (found in the Microsoft Purview compliance portal under Audit) captures Places booking events, check-in events, and policy change events, useful for verifying that changes you made actually fired.
Prevention & Best Practices for Microsoft 365 Places
Getting Microsoft 365 Places working is one thing. Keeping it working, and scaling it cleanly as your organization grows or changes, requires a few deliberate habits.
The single most important practice is maintaining your building hierarchy as your physical offices change. When a floor gets reconfigured, desks get added or removed, or a new office opens, the Places hierarchy needs to reflect those changes in near real-time. Stale data in the hierarchy means booking panels showing desks that no longer exist, or users trying to navigate to a room that's been repurposed. Assign a specific owner (ideally a facility manager who also has the Places Administrator role) responsible for keeping the hierarchy current. Don't leave this to IT alone, they often don't know when a desk cluster gets moved.
With the April 2026 space licensing model, track your MTSS and MTSS-SS license assignments in a spreadsheet alongside your physical desk inventory. Microsoft's admin portal doesn't give you a clean "which desks are licensed" view without running a PowerShell report. Maintain that mapping yourself and review it quarterly against your Billing licenses page to catch unused or incorrectly assigned space licenses before renewal.
For organizations with a hybrid Exchange environment, proactively identify all on-premises mailbox users and include them in your next mailbox migration wave. The gap in Places functionality for these users grows more visible as Places adoption increases, coworkers using work plans will notice that their hybrid-mailbox colleagues never show a work location, which creates confusion and erodes trust in the tool.
Finally, monitor Places analytics monthly. The occupancy data, especially the gap between reservations and actual check-ins, tells you which spaces are working and which are being over-booked or under-used. Use it to right-size space licenses: desks that are consistently unbooked don't need a paid space license. Spaces that are always in conflict might need Autorelease enabled to recover wasted time.
- Run a monthly PowerShell audit (
Get-Place -Type Desk) to verify all bookable desks have space licenses, a five-minute script that prevents months of user complaints. - Enable Autorelease on all rooms and desks with space licenses, it recovers reserved but empty spaces automatically and is one of the most visible wins for real estate teams.
- Pin the Places app in your Teams app setup policies rather than just installing it, pinned apps appear in the left sidebar immediately and dramatically improve adoption rates.
- Migrate Exchange on-premises mailboxes to Exchange Online before marketing Places to employees, discovering the limitation after a company-wide rollout announcement is an avoidable embarrassment.
Frequently Asked Questions
Do we still need Teams Premium for individual desk booking after April 2026?
Not for new deployments, no. Starting April 2026, individual desk booking is tied to space licenses (MTSS or MTSS-SS on the desk itself) rather than a Teams Premium license on the user. If you had active Teams Premium subscriptions before April 2026, those users can still book any desk until their subscription renews, after which they'll need the desks themselves to be licensed. Plan your renewal dates carefully and make sure space license assignments are in place before any Teams Premium renewals hit.
Why can some of my users see Places Explorer and others can't, even with the same license?
Before April 2026, Places Explorer required a Teams Premium license. If some users were on Teams Premium and others weren't, that explains the discrepancy you're seeing. As of April 2026, Places Explorer is a Core feature available to all supported Microsoft 365 licenses, but the change may not have propagated to all users immediately. Verify that affected users have a supported license (M365 Business Basic or higher, Teams Enterprise, Teams Essentials, etc.), wait 24 hours after any license changes, and confirm the Places app is included in their Teams app setup policy.
We bought MTSS licenses for our common area phones. Did we lose our free MTSS-SS licenses?
Yes, if you've assigned an MTSS license to a Teams common area phone, the 3 free MTSS-SS licenses that come with each MTSS purchase are not available for rooms or desks. This is one of the trickier aspects of the space licensing model. If you want to use the free MTSS-SS licenses for BYOD rooms or individual desks, the parent MTSS license needs to be assigned to a BYOD room or a desk, not to a common area phone. Review your MTSS license assignments in Billing > Licenses and consider whether any of your common area phones can be reclassified to free up those MTSS-SS allocations.
My users' work location updates in Teams but coworkers can't see it. What's wrong?
The most likely cause is that the affected user has an on-premises Exchange mailbox rather than an Exchange Online mailbox. In Exchange hybrid environments, work location setting changes are stored locally and not shared across the organization, the user sees their own location, but nobody else does. This is a documented limitation that only goes away when the mailbox is migrated to Exchange Online. You can identify hybrid-mailbox users in the Microsoft 365 Admin Center under Users > Active users, look for the mailbox type listed on the user's profile page.
How do I set up the Microsoft Places building hierarchy in bulk for a large office?
For large-scale deployments, PowerShell is the only practical route. Connect to Exchange Online with Connect-ExchangeOnline and use New-Place to create building and floor records, then Set-PlaceV3 to associate existing room and desk resource accounts with the correct floor. You can script the entire hierarchy from a CSV export of your physical room list. Microsoft's official cmdlet documentation for Set-PlaceV3 covers all available metadata fields, floor number, capacity, accessibility features, A/V equipment, and more, that power the Places Finder filtering experience. Uploading floor plan images is done through the Places Management Portal GUI after the hierarchy records are created in PowerShell.
Does Microsoft 365 Places work on mobile, or is it desktop-only?
Places works on mobile, desktop, and web. The Places app is available as a connected app inside Outlook, Teams, and the Microsoft 365 app, and it's accessible directly on the web as well. That said, some features have surface-specific behavior: automatic work location detection currently works on the Teams desktop app only, connecting through corporate Wi-Fi or a supported peripheral. The mobile app supports manual work location updates and desk booking, but won't trigger automatic location detection. For users who are primarily mobile, make sure they understand the manual update workflow through the Teams calendar or Places app on their phone.