Updated August 12, 2025: We have updated the timeline. Thank you for your patience.
We’re introducing enhanced Microsoft Graph API capabilities that now support full Create, Read, Update, and Delete (CRUD) operations for Microsoft Places directory objects. This update enables developers and partners to programmatically manage Places data—including buildings, floors, sections, rooms, and desks—using a consistent and extensible API surface.
This change is associated with Microsoft 365 Roadmap ID: 488101
[When this will happen:]
General Availability (Worldwide): Available now.
[How this will affect your organization:]
There is no immediate impact by default. However, these APIs provide a more efficient and scalable way to onboard and maintain location data in Microsoft Places. Organizations using third-party systems to manage location hierarchies can now integrate directly with Microsoft Places, ensuring data accuracy and consistency across systems.
[What you can do to prepare:]
- If you’re planning to onboard to Microsoft Places or expand its use across regions, consider using these APIs to streamline your data import and management processes.
- If you’re currently using a third-party system of record, contact your provider to understand their plans for integrating with these APIs.
- Review: Working with the Places API in Microsoft Graph
[Compliance considerations:]
- Does the change alter how existing customer data is processed, stored, or accessed? Yes – it introduces new API endpoints for managing location data.
Source: Microsoft
<<< [MC1133514] Archive
Tooltip: View earlier revisions of this post
Latest Posts
- (Updated) Microsoft Loop – User Accessible Recycle Bin for Loop workspaces [MC929021]
- (Updated) Microsoft Loop – Require Existing Microsoft 365 Group for New Loop workspaces [MC929022]
- (Updated) Microsoft Loop – Departed User Content Workflows for User-Owned Loop workspaces [MC929014]
- GCP Release Notes: August 12, 2025