Collaboration

Microsoft 365

Connect Microsoft 365 through Graph OAuth and verify bounded Outlook and Teams reads.

AuthOAuth 2.0UpdatesReal-timeAvailable

What this connector does

Start Microsoft Graph OAuth from Atlas and store encrypted connector tokens server-side.
Show persisted connection status and delegated scopes from the shared connector store.
Run bounded Outlook inbox and Teams list reads from explicit operator actions.
Keep mailbox/channel background sync and subscriptions as separately verified scheduler workflows.

Before you begin

You can edit the Atlas tenant Integrations settings.
Your Atlas deployment has Microsoft OAuth client credentials configured.
You can approve the Microsoft tenant and delegated scopes Atlas requests.

Get your credentials

Configure the Microsoft app

Open Microsoft Entra ID, register or review the Atlas app, and confirm its redirect URI points at the Atlas connector callback route. Azure portal

Set Atlas OAuth credentials

Set MICROSOFT_OAUTH_CLIENT_ID and MICROSOFT_OAUTH_CLIENT_SECRET on the Atlas API and restart the service if your platform requires it.

Start OAuth from Atlas

Open the Atlas Microsoft 365 connector page, click Connect, approve Graph consent, and return to Atlas.

Verify Graph access

Use the Graph-read verification action to prove the stored credential can read Outlook inbox metadata and Teams membership.

Required scopes and permissions

Read Outlook inbox metadataMail.Read

Send Outlook mailMail.Send

Read Teams membershipsTeam.ReadBasic.All

Send Teams channel messagesChannelMessage.Send

Send Teams chat messagesChatMessage.Send

Read basic profile and retain refresh grantsopenid profile email offline_access User.Read

Setup checklist

Confirm MICROSOFT_OAUTH_CLIENT_ID and MICROSOFT_OAUTH_CLIENT_SECRET are configured for the Atlas API.
Click Connect and complete Microsoft Graph OAuth consent.
Confirm Atlas shows the persisted Microsoft 365 connection and delegated scopes.
Run the Graph-read verification and confirm Outlook and Teams reads complete without exposing provider payloads.
Enable background sync only after scheduler and subscription evidence is retained for the deployment environment.

Troubleshooting

OAuth cannot start
Confirm Microsoft client credentials and the redirect URI before trying the Connect button again.
Graph verification is blocked
Check that the stored grant includes Mail.Read and Team.ReadBasic.All, then rerun the bounded read check.
Verification fails before connect
Complete Microsoft Graph OAuth consent before running provider operations.

Webhooks

Manual verification reads Outlook and Teams through Graph. Durable mail, Teams, file, and calendar subscriptions are operated separately from the connector verification console.

Events Atlas listens for

Mail received
Teams channel message
Chat message
Calendar event changed

Provider docs: https://learn.microsoft.com/graph/webhooks

Disconnect and data deletion

Click Disconnect on the Atlas Microsoft 365 connector page to revoke the stored Atlas connection.
Remove the Atlas enterprise app grant in Microsoft Entra if you want to revoke provider-side access immediately.
Atlas does not cache Microsoft Graph provider payloads in the browser.

Once you have the credentials above, paste them into the live connector page to finish connecting Microsoft 365.

Open the Microsoft 365 connector page