How to Audit, Consolidate, and Govern Shared Calendars in Microsoft 365

A new hire on the facilities team asks which calendar she should check for the building’s planned power outages. It’s a fair question. You open the shared calendars list to show her, but you just keep scrolling. “Facilities.” “Facilities Team.” “Facilities – Maintenance.” “FM Calendar (old).” “Building Ops.” And one, notably, called “Calendar2.” 

Three of these have events from this month. Two have been unused since 2023. When you ask around the room, no one can say for sure which one Security actually reads. So, the honest answer to her question is that you don’t have a calendar to give her yet. You have five to clean up first. 

This is where the usual advice falls short. “Here is how to create a shared calendar in Outlook” doesn’t address the real issue. Your calendars exist, but the problem is that there are too many and no way to tell the active ones from the inactive ones. That task requires a different approach, roughly five steps. 

Why shared calendars become unmanageable

The mess is due to how the defaults work. In Microsoft 365, pretty much anyone with a mailbox can create a calendar and share it. There’s no approval, no naming standard, no assigned owner, and no expiration. It’s handy on a Tuesday when you need something quickly. It’s less helpful three years and two reorganizations later. 

Every campaign, every short-term project, and every employee who has left the company tends to leave a calendar behind. None of these were mistakes at the time. The organization just never had a place to keep track of them, so they piled up. 

Separate calendars earn their place when the audiences genuinely differ: a team that needs its own working calendar the rest of the company shouldn’t see, a bookable resource that has to stay distinct from the schedules using it, or a read-only feed like maintenance windows that several departments watch but none should edit. The problem isn’t having many calendars. It’s having many with no owner, no purpose on record, and no way to tell which is current. Consolidation is about cutting the duplicates and the orphans, not collapsing every legitimately separate calendar into one.

Step 1: Inventory every shared calendar before deciding what stays

You can’t tidy up what you can’t see. And the calendars causing the most confusion are often the informal ones that never made it onto any list. Start by creating that list. 

The Exchange Admin Center and PowerShell do most of the work, though discovery takes a few passes rather than one command. For the individual and secondary calendars, enumerate the mailboxes you care about:

• Run Get-MailboxFolderStatistics -FolderScope Calendar against each to list its calendar folders.
• Then run Get-MailboxFolderPermission on each folder to see who it’s shared with. This cmdlet needs a specific folder identity, so it can’t scan the whole tenant on its own.
• Inventory the Microsoft 365 Group calendars separately with Get-UnifiedGroup, and the bookable resources with Get-Mailbox filtered by RecipientTypeDetails for RoomMailbox and EquipmentMailbox.
• Don’t skip the secondary calendars tucked inside individual mailboxes, since those often go unnoticed when the employee who made them leaves. 

What you need is one clear list: name, type, which mailbox it belongs to, and who has access. Nothing fancy; a spreadsheet works. 

Step 2: Sort calendars into keep, merge and retire

Now go through the list and categorize every calendar into one of three groups. Some are clearly important and will stay, some duplicate others and will be merged, and the ones with no recent events and no owner will be removed. 

Judging real use is harder than it sounds, so weigh several signals together: recent calendar activity, current permissions, any documented dependencies, and feedback from the teams involved.

Technical activity on its own won’t always tell you which calendar people actually rely on. Watch for the calendar that people genuinely use, which may not be the official one. Promote that one. The tidiest name isn’t always the real source of truth.

Step 3: Assign business and technical owners before migration

Each calendar you keep needs to have two names associated with it: someone who decides what gets added, and someone who manages its permissions and eventual retirement. A calendar without an owner is just a future item for your next cleanup. 

Pay special attention to the secondary calendars in an individual’s mailbox. These are fragile. If that person changes teams or leaves, the calendar could go with them and take a department’s schedule along. Move important items to a shared mailbox or a Microsoft 365 Group so they remain accessible. 

Step 4: Move each calendar to the Microsoft 365 home that fits its purpose

For each calendar you keep, decide where it should live going forward rather than sticking with whatever it is now. A Microsoft 365 Group calendar is the right home when the calendar belongs to an ongoing collaboration group that also uses Teams, SharePoint, or the group mailbox.

When a department only needs a centrally managed schedule without all that, a shared mailbox calendar is often the better fit. For anything bookable, like a conference room or a pool vehicle, use a room or equipment mailbox, which lets Exchange accept and decline requests on its own and heads off the double bookings that probably started this whole process.

Then merge the duplicates, carefully. Recreating or moving calendar items can disrupt organizers, attendee responses, recurring series, and reminders. So, before you consolidate: confirm any retention or compliance requirements, export or otherwise preserve the old calendar, test the migration on a small scale, and keep the retired calendar read-only through a transition period rather than deleting it outright.

Be especially cautious about recreating organized meetings, since reissuing invitations can re-notify every attendee and break existing responses. Direct people to the surviving calendar, and communicate the change clearly in an email or channel post, because a consolidation no one hears about just becomes another stray calendar down the line.

Step 5: Use naming, ownership, and reviews to prevent calendar sprawl

A simple register makes a big difference: name, purpose, business owner, technical owner, calendar type, permission model, and last reviewed. Check it once a quarter, agree on a naming standard, and retire anything that has gone quiet. 

If anyone in your tenant can create Microsoft 365 Groups freely, lean on governance rather than a blanket block, since restricting group creation is a tenant-wide switch that also affects Teams, Planner, and SharePoint and can require Microsoft Entra ID P1 licensing. Microsoft’s own guidance is to keep self-service on and govern it: apply a naming policy, require named owners, and set expiration or renewal policies where your licensing allows. Restrict group creation outright only when you have a clear governance reason to. 

Calendar cleanup does not guarantee native mobile visibility

Say you finish all of that and land on exactly one trusted calendar per purpose. There is still a quiet gap. Shared and Group calendars are accessible through Outlook mobile, but they may not appear consistently in the native calendar application included with the device. Permission to access a calendar in Microsoft 365 does not necessarily mean that Apple Calendar or an Android calendar application will display and synchronize it. The result varies by calendar type, device, application and Microsoft 365 configuration.

Where native-calendar visibility is a genuine requirement, one option is a centrally managed synchronization service that writes a copy of the shared calendar into each user’s own Exchange mailbox, so it can reach native iOS and Android calendars through the device’s existing Exchange connection. Several tools in the Microsoft 365 ecosystem work this way. It’s worth weighing against Outlook mobile if native-app display is the only gap you’re trying to close.

The audit is nobody’s favorite afternoon. It is also the thing that makes every calendar decision after it holds up. Do it once, keep half an eye on the register, and the next new hire on the facilities team gets a one-word answer instead of a tour of the graveyard.