ZoomGov error 202 in Outlook for Mac — OWA works, desktop add-in fails after SSO
I’m troubleshooting a ZoomGov scheduling issue in Outlook for Mac. The user can create Zoom calendar invites through Outlook on the web, but the desktop add-in displays error 202 and does not become usable after SSO.
Environment
- macOS: 26.6.2, build 25G83, as reported by Intune
- Mac model identifier: Mac15,4
- Outlook for Mac: Believed to be 16.x; exact version/build pending confirmation
- Mailbox: Microsoft 365 / Exchange Online
- Integration: Zoom for Outlook add-in using ZoomGov and organizational SSO
- Management: Intune managed, supervised, and reporting compliant; registered in Microsoft Entra
Symptoms
The desktop add-in displays:
“Something went wrong. Please refresh this page. (Error code: 202).”
We also encounter the following sequence:
- The user opens the Zoom add-in and completes the initial SSO sign-in.
- The add-in returns to the meeting-settings window.
- The “Signed in as” field remains blank.
- “Add Zoom Meeting” is visible but unresponsive.
Signing out and back in repeats the incomplete loading state. We have not yet established whether error 202 occurs at the same stage on every attempt.
What works
Zoom scheduling and calendar invites work through Outlook on the web. The unresolved failure is in the Outlook for Mac desktop add-in.
Troubleshooting performed
- Signed out and back into the add-in.
- Cleared Outlook-related caches and WebKit data.
- Tested Safari privacy settings, including cross-site tracking and cookie settings.
None of these attempts has produced a confirmed desktop fix.
Has anyone encountered error 202 with ZoomGov in Outlook for Mac, particularly when SSO returns to a blank account field and an unresponsive meeting button?
- Are there known Outlook or macOS compatibility issues matching this behavior?
- Does the Safari cross-site tracking/popup guidance for OWA also apply to the Mac desktop add-in?
- Which logs or diagnostic tools can identify whether the failure is in the SSO return, session initialization, or account retrieval?
- Is there a specific cache reset or confirmed fix for this scenario?
We have not established that Intune or its SSO configuration is responsible, so we would like to narrow down the failure before changing those policies.
Thanks