Calendar connection errors explained

The Connections page always tells you whether a calendar problem is yours to fix, your Microsoft admin's, or Quorum's. This article lists the states you can meet and the right response to each.

Connection states

Waiting on Microsoft 365 approval. Meetings will start coming in once a Microsoft 365 admin approves calendar access. Use Show the approval link to reopen or forward the link. Approval is checked automatically every minute while you are on the page.

Quorum could not sign in to Microsoft 365. This is on Quorum's side and our team has been notified. There is nothing to do here, and re-approving in Microsoft will not help, which is why the page does not ask you to.

No calendars could be read. Microsoft returned no readable calendar for anyone. A Microsoft 365 policy is the usual cause, typically an Exchange application access policy that excludes the Quorum app. The page includes a PowerShell check your Exchange admin can run behind "Details for your IT team".

Microsoft 365 is not responding. Nothing is lost. The next scan retries on its own.

Quorum could not read your member list. There was nobody to scan. This is on Quorum's side, not Microsoft's, and it retries by itself.

Quorum's calendar permission has been removed. A Microsoft 365 admin withdrew calendar access, so nothing new is being imported. Reconnecting from the Connections page starts a fresh approval.

When a scan will not start

These notices are conditions, not faults:

• A scan is already running. Normal for a service that sweeps continuously. Watch its progress below.
• Microsoft has asked us to pause. Scanning is paused for a short while and clears on its own. Both scan buttons explain this while disabled.
• Teams calendars are not connected. The link may have been removed in another tab.
• Calendar import is not switched on. Contact Quorum support to enable it for the deployment.
• We could not find your mailbox. You are not showing as an active member of this workspace.

When your own calendar cannot be read

After Scan my calendar, you may see "We could not read your calendar". Your account may have no Exchange mailbox, or a Microsoft 365 policy may be blocking access. Microsoft reports both the same way, so Quorum honestly cannot tell which it is. "Microsoft asked us to slow down" simply means the next scan picks your calendar up and nothing is lost.

A scan that found nothing new is not an error. Private, all-day, cancelled, and free entries are never imported, so "Your calendar is up to date" with zero meetings can be entirely correct.

After the Microsoft approval screen

Coming back from Microsoft can land on a few outcomes. "Teams calendars connected" means scanning begins shortly. "Approved, finishing up" means Microsoft is still processing the approval and the page updates as soon as it lands. "Approval was not granted" means nothing changed and no calendar was read. "That approval link had expired" appears because approval links are single use and expire quickly, so start again. "Approved, but Quorum could not sign in" means your approval is in place and the remaining problem is on Quorum's side, with nothing for you to redo.

Unreadable calendars in the coverage list

The panel names people whose calendars could not be read, worst first, because their meetings cannot be imported until it is resolved. Unreadable calendars are normal if Quorum is scoped to a security group. Deferred calendars are counted but not listed, because Microsoft throttling resolves itself.

Scans that end early

"The last scan ran out of time" means it kept working and the next one picks up where it stopped. "The last scan stopped part way through" usually indicates a Quorum restart, and the next scan carries on. In both cases nothing already read is lost.