Microsoft Places is transforming how organizations manage hybrid workplaces by connecting people, spaces, and schedules. Whether you are an IT administrator setting up the foundation or a facility manager looking to optimize desk utilization, the PowerShell module for Microsoft Places provides the necessary tools.
This article serves as a step-by-step guide, derived from standard implementation processes, to help you set up and manage your Microsoft Places environment effectively.
1. Getting Started: Installation and Connection
Before you can manage your floorplans or buildings, you need to set up the PowerShell environment. The process begins with installing the specific Microsoft Places module.
Install the Module
Open your PowerShell terminal (run as Administrator) and execute the following command to install the module directly from the PowerShell Gallery:
![ffwefe]()
Install-Module -Name MicrosoftPlaces -Force
Connect to Microsoft Places
Once the module is installed, you must establish a connection to your Microsoft 365 tenant. Run the Connect-MicrosoftPlaces cmdlet. This will prompt you to sign in with the appropriate administrative credentials. Make sure your account has the necessary permissions to manage Places settings.
![ffggg]()
2. Initializing Your Data and Importing Buildings
After connecting, the next step is to bring your existing building and floor data into the system. This is done using the Initialize-Places cmdlet.
The Export Process
Run Initialize-Places. The system will detect that you haven't set up locations yet and will present you with options. Choose the option to export a .CSV file.
![hhhh]()
This CSV file acts as a template containing all your inferred building and floor data, along with metadata.
![lll]()
Modifying the CSV File
You must edit this CSV file to ensure accuracy:
Update Core Names: Correct or add building and floor names in the first two columns (InferredBuildingName, InferredFloorName). Ensure these names match the physical structures in your office.
Clean Up Metadata: For a successful import, you must remove all columns except for the following four:
InferredBuildingName
InferredFloorName
InferredSectionName
PrimarySmtpAddress
Uploading the Finalized CSV
Once your CSV file is cleaned and updated, run the Initialize-Places cmdlet again. This time, select Option 2 to import your finalized CSV file. This populates the directory with your building and floor structures.
![mmm]()
Note: Any changes made to rooms and workspaces may take up to 24 hours to update across the system.
3. Verifying the Setup in Microsoft Teams
Once the import is complete, you can verify the setup directly in the end-user environment.
Open Microsoft Teams or the New Outlook calendar.
Navigate to the account manager or your profile settings.
Check whether you can set your workplace presence to a specific building.
If the building appears in the dropdown menu, your foundational setup is successful.
![nnn]()
![bbb]()
You can check via below link or Microsoft Teams --> Places app.
People | Microsoft Places
![fff]()
Also you can create Buldings, Floors, Sections, Desks, Desk Pools in Microsoft Places as well.
![ccc]()
![vvvvvv]()
![bbbbb]()
![ddd]()
4. Managing Desk Attributes
A critical part of Microsoft Places is defining how desks can be used. Desks can be configured into four distinct types.
Reservable: Desks that are configured to be booked in advance or on-the-spot.
Drop-in: The desk is available for on-the-spot use and cannot be reserved in advance. You can link peripheral devices (like monitors or docks) to these desks using Teams.
Assigned: A desk permanently linked to a specific user. It cannot be booked by others and must always have a designated user.
Unavailable: The desk is not available for reservation due to maintenance or other reasons.
![xxx]()
![qqq]()
![sss]()
5. Creating New Places via PowerShell
If you need to add new buildings or floors (rather than importing via CSV), you can do so using specific cmdlets.
Create a Building
New-Place -Type Building -Name "Austin 550"
This creates a new building object in the directory.
Create a Floor
To add a floor to the building you just created, you need the PlaceId of the building.
New-Place -Type Floor -Name "1" -ParentId {PlaceId of Austin550}
Replace {PlaceId of Austin550} with the actual ID obtained during the building creation.
Update a Room
If you have an existing meeting room and want to associate it with a specific floor, use the Set-PlaceV3 cmdlet:
Set-PlaceV3 -Identity {smtpAddressOfRoom} -ParentId {PlaceId of Floor1}
This links the room to the correct floor location.
6. Enabling Analytics
To gain insights into how your office is being used, you must enable analytics for your buildings. This allows administrators to view utilization reports and make data-driven decisions regarding space management.
To enable analytics for all buildings, run:
Set-PlacesSettings -Collection Places -SpaceAnalyticsBuildingsList 'Default:All'
7. Notes
Licensing requirements
Supported user licenses
Users with one the following plans can access Microsoft Places:
Microsoft 365 Business Basic, Standard, Premium
Microsoft 365 or Office 365 (E1, E3, E5)
Microsoft 365 or Office 365 for Education (A1, A3, A5)
Microsoft 365 for frontline workers (F1, F3)
Microsoft Teams Enterprise
Microsoft Teams Essentials
Microsoft Teams standalone
Core features
These features are available to all users with one of these plans. Some features need to be explicitly enabled, as described in the Configure Places section of this guide.
Work plans and workplace presence
In-person events and hybrid RSVP
Workplace check-in
Book room and workspaces (also known as desk pools)
Desk assignment
Places Management portal (requires specific permissions described here)
Places explorer
Places finder
Places analytics (with some limitations. Also requires specific enablement described here)
Premium features
The following features used to require a Teams Premium license. As of April 1st, 2026, these features have shifted to a per-space licensing model:
Individual desk booking shifts from a per-user to a per-space licensing model. To ensure a smooth transition, customers with active Teams Premium subscriptions continue to enjoy premium features until renewal.
Auto-release requires rooms and desks to have a space license.
Occupancy reports in Places analytics requires rooms and desks to have a space license. Other analytics features don't require any other license.
Supported space licenses
Microsoft Teams Room ("MTR"), which can be used on meeting rooms.
Microsoft Teams Shared Space ("MTSS"). This was previously called Microsoft Teams Shared Device and is renamed to Shared Space for clarity. This license can be used with BYOD rooms, common area phones, and now with individual desks.
Microsoft Teams Shared Space – Single Space ("MTSS-SS"). You can acquire 3 free MTSS-SS licenses for each purchased MTSS license. MTSS-SS licenses can be used with BYOD rooms or individual desks, but not with common area phones.
Conclusion
Implementing Microsoft Places requires a methodical approach to data management. By leveraging the PowerShell module, you can seamlessly import existing building structures, define desk usage policies, and enable analytics. While changes may take up to 24 hours to propagate, these steps set the stage for a more efficient hybrid workplace, giving employees the clarity they need about where and how to work.