MS Bookings

We’ve seen this come up in larger tenants with lots of “test” or inactive Shared Bookings calendars. A practical approach is to combine Microsoft Graph Bookings data with Exchange Online mailbox telemetry to determine true inactivity over a 90‑day window, then decommission with a short, well‑communicated grace period.

Recommended steps (high level):

Inventory Bookings businesses and check appointment activity within the last 90 days to identify calendars with zero usage.

Corroborate with scheduling mailbox signals (e.g., last logon or item growth) to avoid false positives from seasonal services.

Governance: notify owners, set an opt‑out deadline, and remove or disable unused calendars; keep an exception list for seasonal departments.

References:

Turn Bookings on or off (tenant‑level controls, scoping, and governance):

https://learn.microsoft.com/en-us/microsoft-365/bookings/turn-bookings-on-or-off?view=o365-worldwide

Bookings in Outlook (behavior and user experience differences that affect monitoring):

https://learn.microsoft.com/en-us/microsoft-365/bookings/bookings-in-outlook?view=o365-worldwide

Microsoft Graph Bookings module (endpoints and cmdlets to enumerate businesses and query appointments):

https://learn.microsoft.com/en-us/powershell/module/microsoft.graph.bookings/?view=graph-powershell-1.0

After you identify candidates with no activity in the 90‑day window, send a final notice to owners with a removal date. Anything without a response by that date can be safely decommissioned, while documented exceptions remain active.