How to connect Microsoft Teams with Sally AI

Connect Sally AI with Microsoft Teams to share what came out of a meeting straight in your team's chat or channels. With the Sally Microsoft Teams integration you send action items and notes to Teams in one click, so nothing gets typed twice and everyone sees the same thing.

Quick navigation

1. How to connect Microsoft Teams with Sally AI
2. How to send insights to Microsoft Teams
   • 2.1. Create a chat message in Teams
   • 2.2. Create a post in Teams channel
3. Required OAuth scopes

1. How to connect Microsoft Teams with Sally AI

Follow these steps to set up the Sally-Microsoft Teams integration.

1. Open Settings at the bottom of the left sidebar.

Figure 1: Open Settings

2. Under Configuration, go to Integrations and click Discover integrations.

Figure 2: Discover integrations

3. Pick the Collaboration category on the left, then select Microsoft Teams. The search bar at the top takes you straight there as well.

Figure 3: Select Microsoft Teams from the list

4. The panel on the right tells you what the integration transfers. Click Connect in the bottom right, then sign in with your Microsoft account.

Grant admin consent for the whole organization

If you are a Microsoft 365 administrator, you can approve the required OAuth permissions for your entire organization once. After that, individual users no longer have to confirm the consent screen when connecting this integration.

Grant admin consentYou need to be signed in as a Microsoft 365 Global Administrator. The consent is granted tenant-wide and can be revoked at any time via Entra ID (Azure AD). Admin consent does not give Sally any automatic access to user data: each user still has to connect the integration individually, and an access token is only issued after that user signs in.

5. Once you have signed in, Microsoft Teams is connected. The Actions tab shows what Sally offers through this integration and lets you switch off individual actions for the organization account. Helper functions stay locked while an active action needs them, which is why some toggles cannot be moved. Disconnect in the top right ends the connection again.

Figure 4: Control what the integration may do

Info

With a personal Microsoft account, only the chat message is available. A post in a channel needs a work, school, or university account, because channels belong to an organization in Microsoft 365. If a personal account is connected, that action cannot be used.

Microsoft distinguishes between two main account types:

1. Microsoft account (personal): A personal account you use to access consumer services like Outlook.com, Xbox Live, or Microsoft Store. These accounts are usually linked to an email ending with @outlook.com, @hotmail.com, or similar.

2. Work, school, or university account: An account provided by your organization (e.g. a company or educational institution) that gives access to Microsoft 365, Teams, OneDrive for Business, and other enterprise tools.

Whether an integration may be connected at all is up to owners and admins, see managing integrations for your users.

---

2. How to send insights to Microsoft Teams

Once Microsoft Teams is connected, a few clicks are enough to move content from a recording into Teams, either as a chat message to individual people or as a post in a channel.

The route is always the same: open the recording you need and click the Integrations icon. It sits at the top of every section and on every single line. Below it you find the two Microsoft Teams actions.

You can:

• Create a chat message in Teams
• Create a post in Teams channel

Both actions come prefilled with the content from the summary, and you can edit it before sending.

2.1. Create a chat message in Teams

Send a line from the summary to individual people as a chat message.

1. Choose Create chat message in the Integrations menu.

Figure 5: Choose Create chat message

2. Under Recipients, pick the people who should receive the message. The field is mandatory, and the search lets you select several people.
3. Check the content and click Send message.

Figure 6: Pick recipients and send the message

Best practice

Use chat messages for direct, quick follow-ups with colleagues after meetings.

---

2.2. Create a post in Teams channel

Share a line from the summary as a post in a channel so the whole team sees the context.

1. Choose Create post in channel in the Integrations menu.

Figure 7: Choose Create post in channel

2. Under Team and Channel, pick where the post should go. Both fields are mandatory.
3. Check the subject, which is mandatory as well, and the content. Both are prefilled and can be edited.
4. Click Create post.

Figure 8: Fill the fields and create the post

Best practice

Use channel posts to share decisions, next steps, or updates with the entire project team.

---

3. Required OAuth scopes

For the integration with Microsoft Teams, Sally uses OAuth 2.0 for authorization. The following scopes define which areas Sally can access on behalf of the authenticated user.

Technical overview of required scopes

Disclaimer

1. Sally accesses this information solely to technically establish and maintain the connection to the user account.

2. Sally does not make any autonomous changes. Actions are performed exclusively upon the explicit initiative of the user.

3. API endpoints are only called within the scope of an active action initiated by the user within the platform.

Scope	Type	What Microsoft technically allows with this scope	How Sally uses this scope
Channel.Create	Delegated	API permission to create channels	Technically defined within the Microsoft Teams permission model. Sally does not create channels independently outside explicitly user-initiated actions.
Channel.ReadBasic.All	Delegated	Read basic channel information	Part of Microsoft's permission model. Sally reads basic information solely for display within the integration.
ChannelMessage.ReadWrite	Delegated	Read and write channel messages	Technically provided for integrations. Sally does not modify channel messages independently without explicit user action.
ChannelMessage.Send	Delegated	Send messages in channels	Part of the OAuth model. Sally does not send channel messages independently outside explicitly user-initiated actions.
Chat.Create	Delegated	Create chats	Technically defined within the Teams API model. Sally does not create chats independently.
Chat.ReadWrite	Delegated	Read and write chat messages	Part of the permission model. Sally does not modify chat conversations without explicit user action.
ChatMessage.Read	Delegated	Read chat messages	Sally reads messages solely within the context of the active integration. No independent processing occurs outside user initiation.
ChatMessage.Send	Delegated	Send chat messages	Technically defined within Microsoft's API model. Sally does not send messages independently without explicit user action.
Contacts.ReadWrite.Shared	Delegated	API permission for shared contacts	Part of Microsoft's permission model. Sally does not modify contact data.
email	Delegated	Access to the user's email address	Sally reads the email address to uniquely identify the connected account.
Group-Conversation.ReadWrite.All	Delegated	Read and write group conversations	Technically defined within the Microsoft 365 model. Sally does not independently interfere with group conversations.
Group.ReadWrite.All	Delegated	API permission for Microsoft 365 groups	Part of the permission model. Sally does not independently alter group structures.
offline_access	Delegated	Issuance of long-lived access tokens	Enables a stable connection without repeated login. No Teams data is modified.
openid	Delegated	OpenID Connect authentication	Secure authentication via Microsoft Identity.
profile	Delegated	Access to basic profile data	Sally reads basic profile information to identify the authenticated account.
Team.ReadBasic.All	Delegated	Read basic team information	Part of the Microsoft Teams model. Sally reads basic information solely for display within the integration.
User.Read	Delegated	Read basic user information	Sally reads basic account information for authentication purposes.
User.ReadBasic.All	Delegated	Read basic information of other users	Sally reads this information solely for display within the integration.