How can we help?

Strata currently supports Microsoft SQL Server — both on-premise and Azure SQL. When you connect a database, Strata automatically discovers your schema, including tables, columns, foreign keys, and data types.

No. Your queries, results, and database content are never used to train any AI models. Strata accesses AI models through Microsoft Azure AI Foundry, which prohibits the use of your data for model training. See our Privacy Policy for full details.

Strata uses Microsoft Entra ID (Azure AD) Single Sign-On. There's no separate account to create — your existing Microsoft credentials handle everything. MFA and conditional access policies from your organization are inherited automatically.

By default, Strata connects with read-only permissions and only executes SELECT queries. Write access depends on the SQL Server credentials you provide. We recommend using read-only credentials. Strata's permission setting (Viewer/Editor/Admin) controls which query types the AI will generate.

Strata gives you a curated catalog of frontier models from every major provider — OpenAI, Anthropic, xAI, DeepSeek, Mistral, Cohere, and Microsoft — all served through Microsoft Azure AI Foundry. Your administrator chooses which models your organization enables, and you can switch between them mid-conversation; context carries over seamlessly.

Strata exports to Excel (.xlsx), PDF, CSV, JSON, and interactive HTML dashboards. Excel exports include styled headers, proper data types, and auto-filters. PDF exports include charts, tables, and a formatted cover page.

Strata integrates with SQL Server (live queries on databases you connect), OneDrive and SharePoint (read and save files, plus knowledge-base search), Outlook (search your inbox, read threads and attachments, send email), and Microsoft Teams (the Strata bot in your channels). There’s also Strata for Outlook, an add-in that runs inside Outlook itself to summarize and draft replies to the email you’re reading. Beyond Microsoft, Atlassian brings Jira and Confluence in over a single connection — Jira Software issues, Jira Service Management requests, and Confluence pages — with Jira and Confluence enabled separately by your admin. Either each person signs in with their own Atlassian account, or an admin configures one organization account for everyone. Your admin pins the Atlassian site, and writing to Jira or Confluence is off until an admin turns it on. Microsoft 365 integrations use OAuth 2.0; SQL Server uses encrypted credentials you provide. Each only accesses the data needed for your request, and you can connect or disconnect any integration at any time.