AtlasWork, planned itself.

    The AI-native, all-in-one work platform. Tasks, projects, CRM, contracts, and analytics in one calm workspace.

    System status
    • SSO
    • SCIM
    • Two-factor sign-in
    • Audit log

    Product

    • Overview
    • PDF tools
    • Diagram tools
    • People & HR
    • Integrations
    • Marketplace
    • Pricing

    Resources

    • Guides
    • Glossary
    • Compare
    • Docs
    • API reference
    • Support
    • Changelog
    • Status

    Company

    • About
    • Careers
    • Press
    • Contact

    Legal & trust

    • Trust center
    • Security
    • Privacy
    • Terms
    • DPA
    • GDPR
    • SLA
    • Refunds
    • Google API data
    Atlas, a product by wrxstack.com·© 2026 wrxstack·All rights reserved
    PrivacyTermsSecurityStatus

    You are in control of your cookies

    Atlas uses strictly necessary cookies to keep you signed in. With your consent, we add anonymized product analytics, conversion attribution, and remembered preferences. Change your mind any time at /privacy/cookies.

    Off until you agree · Change it any time

    • Necessaryalways on
    • Analyticsopt-in
    • Marketingopt-in
    • Preferencesopt-in
    Skip to documentation
    Docs
    Back to Atlas

    Start here

    • Overview

    Developer

    • REST API guide
    • Authentication
    • API reference
    • MCP (AI agents)
    • MCP tools reference
    • SDKs
    • Quick actions
    • Changelog

    Webhooks

    • Overview
    • Quickstart
    • Events
    • Payloads and headers
    • Security and signing
    • Delivery and retries
    • Managing via API

    Connect

    • Connectors
    • Integrations

    Product

    • Collaboration and chat
    • Signing in and security
    • Client portal

    Reference

    • Glossary
    • Keyboard shortcuts
    • Module reference
    Microsoft 365 logo

    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

    1

    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

    2

    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.

    3

    Start OAuth from Atlas

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

    4

    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

    1. Confirm MICROSOFT_OAUTH_CLIENT_ID and MICROSOFT_OAUTH_CLIENT_SECRET are configured for the Atlas API.
    2. Click Connect and complete Microsoft Graph OAuth consent.
    3. Confirm Atlas shows the persisted Microsoft 365 connection and delegated scopes.
    4. Run the Graph-read verification and confirm Outlook and Teams reads complete without exposing provider payloads.
    5. 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

    1. Click Disconnect on the Atlas Microsoft 365 connector page to revoke the stored Atlas connection.
    2. Remove the Atlas enterprise app grant in Microsoft Entra if you want to revoke provider-side access immediately.
    3. 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

    On this page

    • What this connector does
    • Before you begin
    • Get your credentials
    • Required scopes and permissions
    • Setup checklist
    • Troubleshooting
    • Webhooks
    • Disconnect and data deletion