If your company requires admin approval, share the Microsoft administrator section below with your IT team. Approval requests go to your company's Microsoft 365 / Entra administrators.
Connect BlazeSQL to Microsoft Teams so your team can ask data questions without leaving their daily workflow.
Getting Started
Install the BlazeSQL app from the Microsoft Teams app store to your workspace.
A BlazeSQL workspace admin connects Teams from Workspace Settings → Integrations → Microsoft Teams. Sign in with your work Microsoft account and accept the requested permissions if your company allows it. If Microsoft asks for admin approval, follow the steps below, then start Connect again after approval.
Add the BlazeSQL app to any team where you want it available. After that, team members can @mention BlazeSQL in channels within that team.
For Your Microsoft Administrator
There are two separate controls: whether people can use the BlazeSQL app in Teams, and whether BlazeSQL can connect to their Microsoft account. Your company's policies determine whether either step needs IT approval. A BlazeSQL workspace admin is not automatically a Microsoft administrator.
1. Allow the Teams app
In the Teams admin center, open Teams apps → Manage apps, find BlazeSQL, and make it available to the intended users or groups. Allow them to install it, or install it for them. See Microsoft's app management guide for details.
2. Approve the Microsoft connection, if required
If the person connecting BlazeSQL sees Approval required, they can submit a request if that option is available. The request goes to your company's Microsoft Entra reviewers, not to BlazeSQL, even when the approval screen shows the BlazeSQL logo. If there is no request button, contact your Microsoft administrator directly.
The designated reviewer opens the Microsoft Entra admin center and goes to Entra ID → Enterprise apps → Admin consent requests → My Pending.
Select the BlazeSQL request, choose Review permissions and consent, and approve it if it meets your company's requirements.
Once approved, the BlazeSQL workspace admin returns to Workspace Settings → Integrations → Microsoft Teams and starts Connect again.
If BlazeSQL is already listed in Enterprise apps → All applications, an authorized administrator can also open its Permissions page and select Grant admin consent. This requires an appropriate Microsoft Entra role, such as Cloud Application Administrator or Application Administrator. The Teams Administrator role alone does not grant this permission. See Microsoft's instructions for reviewing requests and granting consent.
The Microsoft administrator can approve access separately. The BlazeSQL workspace admin should then complete the connection with their normal work Microsoft account. Use an account that belongs to the teams where you want to deliver reports, so BlazeSQL can find their channels. This integration does not require Microsoft Copilot or a separate BlazeSQL SSO setup.
What permissions does BlazeSQL request?
The connection requests the following Microsoft permissions on behalf of the account that signs in:
Permission | Purpose |
| Sign in and identify the connected Microsoft account. |
| Maintain the connection without asking the user to sign in for every operation. |
| Read basic user profiles, including names and email addresses, to identify Teams users and match BlazeSQL accounts. |
| Read chat names, descriptions and members for the connected account. |
| Read team and channel names and descriptions to find report destinations. |
These permissions do not grant Microsoft Graph access to mailbox contents, files, or all Teams message history. The BlazeSQL bot receives direct messages and @mentions addressed to it, and sends replies and reports where it has been added. See the Microsoft permission definitions.
How to Use it
Tag BlazeSQL in a Channel
Mention @BlazeSQL in any channel within a team where the app has been added. Blaze will respond in a thread with the answer.
Important: BlazeSQL works in standard channels and private teams, but not in private channels. If you need to restrict who can interact with Blaze, use a private team rather than a private channel.
Direct Messages
You can also chat with the BlazeSQL app directly for private, 1-on-1 conversations — just open the BlazeSQL app in Teams and send a message.
Access Controls
Restrict to BlazeSQL Users
By default, any member of your Teams tenant can interact with BlazeSQL. To limit this, enable "Only reply to BlazeSQL users" in Workspace Settings → Integrations. When turned on, BlazeSQL will only respond to Teams users whose email matches a BlazeSQL account. This setting controls who can ask BlazeSQL questions. It does not restrict who can read answers or report summaries already posted in a channel, so choose a channel with the appropriate audience.
Access Groups
You can control which databases, tables, and columns BlazeSQL can access when responding to Teams messages. In Workspace Settings → Access Groups, configure the Microsoft Teams integration access group to define exactly what data is queryable through Teams. This lets you make BlazeSQL available to your broader team while keeping sensitive data restricted.
Agent Reports
You can deliver scheduled Agent Reports to Teams channels or as a direct message. Teams receives a summary and a link to the full report in BlazeSQL.
Add BlazeSQL to the intended team and send it an @mention in the target standard channel. For direct delivery, open the BlazeSQL app in Teams and send it a message.
Open the Agent Report's delivery settings in BlazeSQL and select the Teams destination.
Confirm that the next scheduled report arrives in Teams. Generating a test report by itself does not confirm channel delivery.
If a channel is missing, check that BlazeSQL has been added to that team and that the Microsoft account used to connect belongs to it. Send an @mention in the channel, then reopen the report's delivery settings. Private channels are not supported.
If a report does not arrive, check its run status. Suppressed means the significance filter found no meaningful update to send; Delivery Failed means the report was generated but could not be delivered to one or more destinations. For schedules, delivery settings and status details, see Agent Reports.