Extensions overview
Extensions are how you give Strata access to your data, your files, and your inbox. Once your organization connects its own Azure AI Foundry — the one-time setup that powers every response — Strata works as a general-purpose AI assistant even before you connect any extension, and grows into a full intelligence platform as you add them.
What an extension is
An extension is a connector that exposes a specific external system to the AI as a set of tools. Each extension adds capabilities — when you connect one, the AI can call its tools during a chat or an agent run; when you disconnect it, the tools disappear from the AI's toolset.
Strata's connectors are no longer Microsoft-only. Atlassian brought the first non-Microsoft extensions — Jira and Confluence — behind one sign-in, and beyond the first-party integrations an admin can now add dozens more outside tools through the connector catalog (GitHub, Datadog, Notion, Stripe, Snowflake and more) over the open Model Context Protocol. See Connectors. The first-party extensions you connect yourself appear in Settings > Apps:
| Extension | What it adds | Connected via |
|---|---|---|
| Microsoft SQL Server | Live database queries, schema discovery, multi-connection management, the Tables / Procedures / Explorer / Schema Map pages | A credentials form in Settings, or an admin-published connection. See /docs/integrations/sql-server. |
| Microsoft OneDrive | Search, read, and save files (Excel, PDF, Word, PowerPoint) | A Microsoft OAuth popup. See /docs/integrations/onedrive. |
| Microsoft Outlook | Search and read email, read attachments, draft and send messages with AI-generated attachments | A Microsoft OAuth popup. See /docs/integrations/outlook. |
| Teams chats | Search and read your own Teams chats (one-to-one, group and meeting chats), read only | A Microsoft OAuth popup, once an admin allows it. See /docs/integrations/teams-chats. |
| Jira | Issue and request search across Jira Software and Jira Service Management, issue counts, single-issue reads, and JSM queues — plus creating issues, commenting, changing an issue's status and editing its fields, if your organization has turned writes on | An Atlassian OAuth popup, when your organization runs Atlassian in "each person signs in" mode. See /docs/integrations/atlassian. |
| Confluence | Page search, reading a page, and listing spaces — plus creating pages and commenting, if your organization has turned writes on | The same Atlassian connection as Jira. See /docs/integrations/atlassian. |
Jira and Confluence share a single Atlassian row — "Jira and Confluence, one connection" — so you connect once and get whichever of the two your organization has enabled. They stay separate extensions everywhere else: an admin can allow one and deny the other, and each has its own writes setting.
Atlassian is also the one row that is not always yours to action. If an admin has chosen One organization account mode, an Atlassian service account covers everyone in the organization and there is nothing for you to connect — the row reads as connected through the organization account and offers no Disconnect.
Two more connectors are never in the per-user Settings > Apps list at all, because an admin sets them up for the whole organization:
| Extension | What it adds | Set up by |
|---|---|---|
| Microsoft Teams | Chat with Strata directly from a Teams conversation | Per-tenant bot registration coordinated by Kronisys. See /docs/integrations/teams. |
| SharePoint | Powers the Knowledge Base — an admin indexes selected SharePoint sites so everyone can ask questions across them with cited sources | An admin enables it (it requires OneDrive) and connects sites in Organization > Knowledge Base. See /docs/admin/knowledge-base. |
NoteStrata also ships Strata for Outlook, an add-in that runs inside Outlook itself so you can summarize, draft, and analyze the email you're reading without leaving your inbox. It's separate from the Outlook mailbox connector above — see /docs/integrations/outlook-add-in.
Connectors: the long tail
Beyond the first-party extensions, an admin can plug Strata into dozens of other tools — GitHub, Datadog, Notion, Stripe, Snowflake, Slack and more — through a catalog of connectors built on the open Model Context Protocol. A connector is added once by an admin under Organization > Connectors, and each member then turns on the ones they want from the Connectors tab of the Directory. Once a member opts in, the connector's own actions join the AI's toolset for their chats.
Connectors sit beside the first-party extensions rather than replacing them: the deep integrations above are built against each vendor's API for capabilities a generic tool bus cannot express (attachment extraction, approval gates on a send, retention rules), while connectors cover the long tail beside them. A connector still answers the identity question — an admin chooses per connector between one shared sign-in and each member signing in with their own account, so a tool whose data is bounded by who is asking stays that way. Each is governed as the synthetic extension id mcp:<slug>, so the same role and per-user controls apply. See Connectors for the full picture.
Connecting an extension
Open Settings > Apps. Each extension is a row that shows a Connect button when it's not connected, or a Connected status with the linked account or database underneath when it is. A More menu (the three-dot button at the end of each row) holds the Disconnect action.
- For OneDrive and Outlook, click Connect on the tile. A Microsoft OAuth popup opens; sign in with your work account and approve the requested scopes. The popup closes and the tile flips to its connected state.
- For Jira and Confluence, click Connect on the single Atlassian tile and sign in to Atlassian — one consent covers both products. An admin has to pin the organization's Atlassian site before anyone can connect; until they do, the attempt returns a message saying so.
- For SQL Server, click Connect to open the connection manager and add credentials. You can save more than one connection and switch between them — only one is "active" at a time and powers the database-aware pages.
To remove an extension, open its More menu and click Disconnect. Strata closes the underlying session immediately. For SQL Server, Disconnect clears the active connection without deleting any saved credentials — your saved connections stay in the list and you can reactivate any of them later.
NoteIf your organization's list, your role or a setting on your account leaves an extension out, its page in the Directory says it is not available to you, with the line Your organization's list, your role or a setting on your account leaves <X> out. Only an administrator can put it back. When Strata couldn't read your access just then, the page says so and offers Check again.
How extensions change the AI
Each connected extension activates one or more tools the AI can call mid-response. With your organization's Azure AI Foundry connected but no extensions, Strata behaves as a general-purpose AI: it can reason, write, do math, and search the web (if web search is on), but it cannot read your data. Connect SQL Server and the same chat can suddenly run run_sql. Connect Outlook and it can search and send email. Connect OneDrive and it can save the styled Excel it just generated to your drive.
The sidebar reflects the SQL Server state directly — its Data place, which opens the database pages (Tables, Procedures, Explorer and Schema map), only appears when at least one SQL Server connection is active.
Admin: restricting which extensions an org can use
Admins control the org-wide extension list under Organization > Extensions (/admin/extensions), where How members get an extension decides what the list means. In Ceiling mode, turning an extension off there hides its row from every member's Settings > Apps and blocks the corresponding API endpoints at the server, whatever their role allows. In Menu mode each role's own list decides, so an extension that is off for the organization still reaches members whose role lists it. A member who tries to hit /api/connection/*, /api/onedrive/*, /api/outlook/*, /api/jira/*, or /api/confluence/* for a disabled extension gets a 403. The Microsoft endpoints carry the response flag extensionDisabled: true; the Atlassian endpoints answer with a message naming the product — "Jira is not enabled for your organization." Jira and Confluence are separate switches, so turning one off leaves the other working, and turning Confluence off does not disconnect Atlassian.
WarningSharePoint requires OneDrive. Disabling SharePoint also turns off the Knowledge Base, since Knowledge Base search runs on SharePoint-indexed content.
Admins can also restrict extensions per user. In Organization > Users, open a member and use the Access tab to control which integrations that one user can connect — alongside their Analysis access and which AI models they can use. The agent-specific extension mask lives separately, under that member's Agents tab; see /docs/agents/per-user-governance for how that mask overrides what a single user's agents are allowed to call at runtime.
Connectors are governed by the same controls. Each appears to roles and per-user overrides as the synthetic id mcp:<slug>, so a role's extension allow-list can grant or withhold a connector and a per-user deny removes it for one member — no separate connector permission system. A deployment-wide switch can also turn all connectors off at once. See /docs/integrations/connectors.
Where to go next
- /docs/integrations/sql-server — connecting a personal SQL Server database.
- /docs/integrations/sql-server/org-connections — admin-provisioned databases shared with the org.
- /docs/integrations/onedrive — file search, read, and save.
- /docs/integrations/outlook — email search, read, draft, send.
- /docs/integrations/outlook-add-in — the Strata add-in inside Outlook.
- /docs/integrations/teams — chatting with Strata inside Microsoft Teams.
- /docs/integrations/teams-chats — Strata reading your own Teams chats.
- /docs/integrations/atlassian — Jira, Jira Service Management, and Confluence on one connection, the two connection modes, and writes.
- /docs/integrations/connectors — the connector catalog and adding outside tools over MCP.