Defense AI: Microsoft 365 and Third-Party Connectors

Last updated: November 11, 2026

Short answer: The Microsoft 365 connector runs in your own Azure environment, and each person signs in with their own work account. It's optional, off unless your admin turns it on, and available to both GCC and GCC High companies. Vendor connectors such as Grain, Quo, Pylon, HubSpot and Notion send data to those vendors and are not approved for CUI.

The Microsoft 365 connector

It lets Claude Desktop, Claude Code and other tools search and work with your email, calendar and files.

  • Where it runs: as a separate Container App in your company's Azure environment, not on Atomus servers and not on your computer. It's available to both GCC and GCC High companies.

  • How people sign in: each person signs in with their own Microsoft work account and grants delegated permissions. The connector can only reach what that person can already reach.

  • What Atomus sees: nothing from it. Atomus doesn't access or store your email, files or sign-in tokens.

  • Permission levels: your admin chooses Read only or Read & edit. With Read & edit, actions like sending email or changing calendar events need Microsoft consent. Whether people confirm each action before it runs depends on how your company sets up its AI tools. Your company is responsible for those settings and for actions its AI tools take, including actions taken on a person's behalf. Start with Read only unless people need to make changes.

  • How results come back: the connector gives the model a small search tool instead of loading every Microsoft 365 action at once. Ask about specific things ("unread mail from my manager this week"); results come back 10 at a time.

Data the connector reads goes to your Defense AI models, the same as anything else you send.

Turning it on

Your admin deploys the connector from the Defense AI portal. Then each person adds it from their company's Connect your tools page:

  • Claude Desktop: include Microsoft 365 when you download your setup file, then import the file again. If you don't see the option, ask your admin whether the connector has been deployed.

  • Claude Code: run the command shown on the Claude Code card, then type /mcp in Claude Code and choose m365 to sign in.

  • Codex and OpenCode: add the Microsoft 365 address shown on the card to the tool's MCP settings, with your key. Contact your Atomus contact if you need help with the exact settings.

Connectors that run on your computer

Claude Desktop can also include connectors that run locally, such as a private GitLab, Jira, or a command you add yourself. They reach those systems directly from your computer, for example over your VPN. They're only appropriate for CUI if the system they connect to is inside your CUI boundary. Use read-only access where you can.

Vendor connectors:

Connectors to outside services include Grain, Quo, Pylon, HubSpot, Linear, Notion, Supabase, ClickHouse and Google Cloud services among others. Some sign in through your gateway and some sign in directly with the vendor, but either way, data you send through them goes to that vendor and is handled under the vendor's terms.

  • They may not be approved for CUI or ITAR data. Company Admins are responsible for managing the connectors in their environment.

Web links and web search

Tools that open web pages or search the web send requests outside your environment. The web address or search terms can include text from your conversation. Don't ask the model to search for or open links using CUI details.

Related articles: Defense AI: Can We Use It for CUI or ITAR Data? · Defense AI: Using CUI Documents for Proposals and Reports · Defense AI: Using AI Coding Agents: Files, Secrets and Repository Content