Connecting Outlook calendars for Microsoft 365 firms

In short: Nobody at the firm needs to be made a Microsoft 365 admin just to connect calendars. Two things must be true: (1) your firm’s IT admin has granted tenant-wide admin consent for the Glade app, and (2) each user’s connect attempt does not include prompt=consent in the Microsoft login URL. When both are true, connections stay connected.

When to use this guide

Use this if your firm runs email on Microsoft 365 with a real organization tenant (not personal outlook.com accounts), and you see any of the following:

A user clicks Connect Outlook Calendar and gets a message that approval is required from your IT administrator.
The calendar shows as connected for a few seconds or minutes, then disappears.
It works for IT admins (or anyone with a Microsoft admin role) and fails for everyone else.

People on personal outlook.com accounts typically do not run into this.

Why it happens

Two issues often stack:

The Microsoft login URL includes prompt=consent. That forces a fresh per-user consent screen on every connect, even when the organization has already granted admin consent. On a locked-down tenant, users cannot clear that screen, so they never finish connecting.
A failed token refresh can remove the connection. Instead of only marking the account as needing re-auth, the connection (and its calendars/token) can be cleared. That matches the “connects, then vanishes” symptom, and each retry can look like a brand-new connect.

Making someone a Microsoft admin can appear to fix it because the admin role changes how Microsoft evaluates the request. That is a side effect, not a requirement — and it is not something you should ask IT to do as the “fix.”

Who does what

Firm IT admin — Steps 1 and 2 (one-time tenant consent; clean re-add only if Glade was already modified on the tenant). Needs Global Administrator or Privileged Role Administrator.
Each user connecting a calendar — Step 3 (sign in and authorize their own account, including the URL edit). Usually about two minutes per person.

Have the IT admin open this link and sign in with their admin account:

https://login.microsoftonline.com/organizations/adminconsent?client_id=9303b717-627d-4270-9821-b532411c87cf

The app appears as Glade. They review the permissions and approve.
organizations in the URL resolves to whichever tenant they sign in with, so there is no tenant ID to look up.
This pre-approves permissions only. It does not connect anyone’s calendar — each user still signs in and authorizes in Step 3.
Review or revoke anytime: Entra admin center → Enterprise applications → Glade → Permissions.

Step 2 — If the tenant was already modified, do a clean re-add

Do this when Glade was already granted and then changed — permissions granted then revoked, groups created, scopes reclassified, or conditional access policies added. Muddled state can prevent a fresh consent from taking cleanly.

Remove all Glade permissions (user-specific grants and group assignments).
Remove Glade from tenant access entirely.
Re-add Glade, then re-run the consent link from Step 1.

If the firm is new to Glade and IT has not changed anything yet, skip this step.

Step 3 — Each user connects with `prompt=consent` removed from the URL

This is what gets non-admin users through. It is a manual URL edit for now.

In Glade, start the connection: Integrations → Connect Outlook Calendar (labels may vary slightly).
You land on a login.microsoftonline.com URL that contains &prompt=consent&.
Before signing in, delete prompt=consent from the address bar and one &, then press Enter.
Sign in normally and authorize.

Why this works: the tenant already approved Glade in Step 1, so there is nothing left for the user to request. prompt=consent forces that request anyway — and that is where it fails on locked-down tenants.

Tip: Walk the first user through on a screenshare so you can confirm the URL edit. After that, most people can do it themselves.

Step 4 — Verify the connection held

Do not stop at “Connected.” The failure mode can look connected for a fraction of a second up to about a minute.

Confirm the account shows connected on the firm’s Integrations page, with calendars listed.
Check again at least two hours later and confirm it is still connected with a recent sync time. Microsoft access tokens typically last 60–90 minutes, so lasting past that means background refresh succeeded.
Check again the next day, including at least one person who connected after the fix.

Optional — limit who can connect

If IT wants to control who can use the integration: Entra admin center → Enterprise applications → Glade → Properties, set Assignment required? to Yes, then assign only specific users or a group. Everyone else is blocked from the app and never reaches the connect screen.

Approaches that usually do not work

Make the user an admin temporarily, connect, then remove the role. The connection often dies when the admin role is removed.
Reclassify calendar permissions as “low impact” so users can self-consent. On its own this often changes nothing, and it can depend on publisher-verification status.
Send one-off approvals to individual users as they request access. This has not reliably produced lasting connections.
Treat MFA enrollment as the root cause. MFA errors can appear in logs even when staff are enrolled. Check MFA only if Steps 1–3 still fail.
Ask Glade to “add offline_access.” Glade already requests it when needed; a missing offline_access registration is rarely the real issue.

If it still fails after Steps 1–3

Contact Glade support and include:

Firm name and the exact user email addresses that fail.
Whether the user removed prompt=consent from the URL (confirmed, not assumed).
Approximate timestamps of the failed attempts (so Glade can pull Microsoft error codes and correlation IDs from logs).

Separately, ask your IT admin to pull the Entra sign-in log for that user, filtered to the Glade app, around the attempt. It often names the exact conditional access policy or control that blocked the sign-in.

What Glade asks Microsoft for

Glade uses delegated Microsoft Graph permissions so each user can connect their own calendar after tenant admin consent. Exact permission names can be reviewed in the Entra consent screen and under Enterprise applications → Glade → Permissions.

For the general calendar connection steps (Google or Microsoft), see also Connect an external calendar to Glade.