Admin PowerShell Checks to Fix Shared Microsoft 365 Calendars in NSW

Most shared Outlook calendar problems are fixed by removing the old calendar entry and re-adding it via Add, then Open shared calendar. Accept outstanding share invites in Outlook on the web or the mobile app rather than desktop, and confirm shared calendar improvements are switched on. If the calendar still won't sync after that, the issue usually sits at the mailbox permission level, and fixing this typically requires IT admin support rather than more client-side tinkering.

Quick fixes checklist: try these in order

Before calling anyone, run through this sequence. It resolves the vast majority of shared calendar faults we see in NSW homes and offices, and each step takes only a few minutes.

1. Sign out of Outlook completely, sign back in, and check the Microsoft 365 service health dashboard for known outages affecting calendar sharing.
2. Remove the shared calendar from your calendar list, then re-add it using Add, then Open shared calendar, never through the address book shortcut.
3. Open Outlook on the web or your mobile app and accept any pending share invites sitting unread in your inbox.
4. Update Outlook to the latest build through your Microsoft 365 update channel, then restart the application fully.
5. If the calendar still misbehaves, rebuild your Outlook data file (OST) or create a fresh Outlook profile, since local corruption often masquerades as a sync fault.

Pro Tip: Write down which shared calendars you currently have before removing anything. Re-adding is quick, but only if you remember exactly what to re-add.

This checklist mirrors what Microsoft Q&A threads confirm works for reappearing or frozen shared calendars: removing the stale entry and reconnecting through Open shared calendar forces Outlook to re-authenticate the share properly.

Step-by-step fixes by platform

The exact menu path changes depending on which version of Outlook you're running, so match your platform below rather than guessing.

• Classic Outlook for Windows: close Outlook, run Outlook.exe /resetnavpane from the Run dialog to rebuild the folder pane, then reopen Outlook and go to Home, Add calendar, Open shared calendar to re-add the entry. If the calendar still won't display, the next step is a new Outlook profile rather than more pane resets.
• New Outlook for Windows: check that "Turn on shared calendar improvements" is enabled in settings, since this moves your calendar onto the modern sharing platform. Use Add, then Open shared calendar, and confirm the calendar type shows as REST rather than the older cached format.
• Outlook on the web: accept the share invite directly from your inbox, then confirm the calendar appears under "Shared calendars" in the left pane. If it's missing, ask the calendar owner to re-share rather than retrying the accept yourself.
• Mobile (iOS and Android): only shares accepted recently through Outlook on the web or the mobile app itself will show up here, according to Microsoft's guidance on mobile visibility. Add the calendar through the plus icon in Calendar view, or have the owner re-share and accept the invite again from your phone.

The navigation pane reset deserves a quick explanation because it looks drastic but isn't. Microsoft documents it as a non-destructive step that forces Outlook to rebuild its folder list from scratch, which often restores the ability to tick a shared calendar checkbox that had stopped responding.

Pro Tip: If you manage calendars across both desktop and mobile, accept the share on mobile first. Desktop-only acceptances can leave the share registered inconsistently on the Microsoft 365 backend.

Why re-adding works: shared calendar improvements explained

Outlook has quietly moved shared calendars from an older MAPI-based model to a newer REST-based model, and that shift explains almost every fix in this article.

• Legacy MAPI sharing relied on cached folder references that could go stale, especially after permission changes, password resets or mailbox moves.
• The modern REST-based sharing model behaves differently and more reliably, and it changes how settings like "Download shared folders" interact with your calendar once upgraded.
• Removing and re-adding a shared calendar forces Outlook to request a fresh sharing token, which effectively upgrades that calendar to the modern platform instead of leaving it stuck on the old one.

One old piece of advice worth retiring: unchecking "Download shared folders" used to be a common workaround, but Microsoft notes this mitigation is obsolete once a calendar has moved to the modern sharing platform, and relying on it can delay the real fix. Beyond client settings, some faults trace back to service incidents, propagation delays across Exchange Online, or a genuinely corrupted sharing token, none of which any amount of clicking in Outlook will resolve.

Admin checks and PowerShell actions for IT teams

When the steps above don't stick, especially if several people on the same tenant report the same fault, it's time for an admin to look at mailbox permissions directly rather than repeating client-side fixes.

• Run Get-MailboxFolderPermission "<mailbox>:\Calendar" to see exactly what access level (Reviewer, Editor or Delegate) each user currently holds on the calendar folder.
• If permissions look wrong or inconsistent, revoke and reapply them with Set-MailboxFolderPermission, which clears corrupted entries that client-side removal can't touch.
• In hybrid environments, confirm Azure AD replication has actually completed, since a permission change can look applied in one system and not the other for a period.
• If sync faults persist across a shared mailbox, check for profile corruption and consider removing the affected GroupStore registry entries or simply building a new Outlook profile, which Microsoft documents as a standard remediation for mailboxes that stop refreshing properly.

When user-level fixes fail, admins often need to check mailbox-folder permissions with PowerShell and verify the backend state directly, according to Microsoft Q&A guidance on Exchange Online backend issues, rather than continuing to troubleshoot from the client side.

When to escalate and what to collect for support

Some symptoms are a clear signal to stop self-troubleshooting and bring in help, and knowing what to hand over saves hours of back-and-forth.

1. Escalate if the calendar shows correctly in Outlook on the web but never appears in desktop Outlook, since that points to a client-side or permission-token problem rather than a sharing fault.
2. Escalate if Sync Issues logs show repeated permission or token errors, or if more than one person on the tenant reports the same calendar fault at the same time.
3. Before contacting support, gather screenshots, the exact error text, the affected account usernames, timestamps, a snapshot of tenant service health, and a list of every step already tried.
4. If possible, run a simple reproduction test: have one user share a calendar, have the second user accept it through Outlook on the web, then check visibility across every client involved.

Prevention and best practice for shared calendars

A little routine maintenance stops most of these faults from recurring in the first place.

• Keep Outlook on a current update channel and make sure shared calendar improvements stay enabled across your team's devices.
• Accept every share invite through Outlook on the web or mobile, and consider a shared mailbox instead of personal calendar sharing for read-only, organisation-wide calendars.
• Document who has access to what centrally, and use PowerShell scripts to apply permissions consistently when a change affects a larger group.

Pro Tip: Review shared calendar permissions every few months, especially after staff changes. A permission left over from someone who's moved teams is a common source of confusing "it used to work" tickets.

Our take on diagnosing stubborn shared calendar faults

Most shared calendar faults clear up with the removal and re-add trick, and we'd rather you try that first than book a technician for a five-minute fix. Where it gets genuinely tricky is mixed environments: a business running a hybrid Exchange setup, several Outlook versions across different machines, or a profile that's been quietly corrupting itself for months. In those cases, a remote session can usually confirm whether the fault sits in Outlook or on the Microsoft 365 backend, and an onsite visit makes sense when a full profile rebuild or exchange-level permission reset is involved across multiple machines. If you've worked through the checklist above and you're still stuck, that's the point where professional eyes save you more time than another forum search.

- PC Scientist

Get hands-on help with your Microsoft 365 calendar

We fix these calendar faults for households and businesses across the areas we serve every week, and we'd rather solve it properly once than have you re-adding the same calendar every month. Our Email Systems Scientist service covers Microsoft 365 and Outlook calendar troubleshooting specifically, from permission resets to full profile rebuilds, and our broader Computer Support Scientist team handles the client-side side of things when a device itself needs attention.

• We offer both remote and onsite troubleshooting, so a quick permission check can often happen the same day without anyone leaving their desk.
• If your business is on a hybrid setup or a Microsoft Silver Cloud migration path, our team can work alongside specialist migration partners where that's relevant to your tenant.
• Browse our case studies to see how we've resolved similar IT support outcomes for other clients.

If you've tried the fixes above and your calendar still won't behave, book a session through PC Scientist and we'll sort the backend permissions properly rather than leaving you to guess.

Sources

• Outlook shared calendar reappearing (Microsoft Q&A)
• Shared calendars updates in Outlook for Windows (Microsoft Support)

Recommended

• Business Email & Microsoft 365 NSW
• Outlook not receiving emails: fix it fast