View a markdown version of this page

Microsoft Teams integration - Amazon Quick

Microsoft Teams integration

Use the Microsoft Teams action connector to send messages, manage channels, schedule meetings, and manage team collaboration directly in Amazon Quick through natural language.

Setting up this integration involves two steps. First, you register an application in Microsoft Entra and configure its permissions. Then, you create the integration in Amazon Quick and connect it to your Entra app. For information about the authentication methods that Amazon Quick supports, see Authentication methods.

Before you begin

Make sure you have the following before you set up the integration.

Configure Microsoft Entra

Before you configure Amazon Quick, create an app registration in Microsoft Entra. Complete all of the following steps in Entra before moving to the Amazon Quick console.

For more information about app registrations, see Register an application with the Microsoft identity platform in the Microsoft documentation.

Register the application

  1. Open the Microsoft Entra admin center.

  2. In the left navigation, choose Entra ID, then choose App registrations.

  3. Choose New registration.

  4. For Name, enter a descriptive name for your integration.

  5. For Supported account types, choose Accounts in this organizational directory only.

  6. For Redirect URI, select Web and enter https://{region}.quicksight.aws.amazon.com/sn/oauthcallback. Replace {region} with the AWS Region where your Amazon Quick instance is deployed.

  7. Choose Register.

  8. On the overview page, copy the Application (client) ID and Directory (tenant) ID. You need these values for the Amazon Quick configuration.

Create a client secret

Amazon Quick needs a client secret to authenticate with Microsoft Entra. This secret acts as a password for the app registration.

  1. From your app registration, choose Certificates & secrets.

  2. Choose New client secret.

  3. Enter a description and choose an expiration period.

  4. Choose Add.

  5. Copy the Value immediately. This value is only displayed once.

Important

Copy the secret Value, not the Secret ID. The Value is the longer string used for authentication.

Configure API permissions

Microsoft Graph supports two permission types for this integration. Delegated permissions allow the app to act on behalf of a signed-in user. Application permissions allow the app to act without a signed-in user. For more information, see Overview of Microsoft Graph permissions in the Microsoft documentation.

  1. From your app registration, choose API permissions.

  2. Choose Add a permission, then choose Microsoft Graph.

  3. Choose Delegated permissions or Application permissions based on your authentication method, and add the permissions from the appropriate table below.

  4. Choose Grant admin consent for [your tenant name] to approve the permissions.

For user authentication (delegated permissions):

Add the following as Delegated permissions in your Entra app registration. For the full permissions reference, see Microsoft Graph permissions reference in the Microsoft documentation.

Teams action integration – delegated permissions
Permission Description
Chat.ReadWrite Allows the app to read and write the signed-in user's chat messages.
ChatMessage.Send Allows the app to send chat messages on behalf of the signed-in user.
Team.ReadBasic.All Allows the app to read the names and descriptions of teams on behalf of the signed-in user.
Channel.ReadBasic.All Allows the app to read channel names and descriptions on behalf of the signed-in user.
Channel.Create Allows the app to create channels in any team on behalf of the signed-in user.
ChannelMessage.Read.All Allows the app to read all channel messages on behalf of the signed-in user.
ChannelMessage.Send Allows the app to send messages in channels on behalf of the signed-in user.
ChannelMember.ReadWrite.All Allows the app to add and remove members from channels on behalf of the signed-in user.
TeamMember.ReadWrite.All Allows the app to add and remove members from all teams on behalf of the signed-in user.
User.Read.All Allows the app to read the full set of profile properties of all users on behalf of the signed-in user.
OnlineMeetings.ReadWrite Allows the app to read and create online meetings on behalf of the signed-in user.
OnlineMeetingTranscript.Read.All Allows the app to read all transcripts of online meetings on behalf of the signed-in user.
Calendars.ReadWrite Allows the app to read and write events in user calendars on behalf of the signed-in user.
offline_access Allows the app to refresh access tokens without requiring the user to sign in again. This reduces how often users need to re-authenticate.

For service authentication (application permissions):

Add the following as Application permissions in your Entra app registration.

Teams action integration – application permissions
Permission Description
Chat.Read.All Allows the app to read all chat messages in your organization without a signed-in user.
Chat.Send Allows the app to send chat messages without a signed-in user.
Team.ReadBasic.All Allows the app to read the names and descriptions of all teams without a signed-in user.
Channel.ReadBasic.All Allows the app to read all channel names and descriptions without a signed-in user.
ChannelMessage.Read.All Allows the app to read all channel messages without a signed-in user.
ChannelMessage.Send Allows the app to send messages to any channel without a signed-in user.
ChannelMember.ReadWrite.All Allows the app to add and remove members from all channels without a signed-in user.
TeamMember.ReadWrite.All Allows the app to add and remove members from all teams without a signed-in user.
User.Read.All Allows the app to read the full set of profile properties of all users without a signed-in user.
OnlineMeetingTranscript.Read.All Allows the app to read all transcripts of online meetings without a signed-in user.
Important

With service authentication, all actions execute as the service account. Any user with access to this integration can perform actions across all teams and channels that the service account can access. Scope the application permissions appropriately for your organization's security requirements.

Record your credentials

Before leaving the Microsoft Entra admin center, confirm you have the following values. You need them for the Amazon Quick configuration.

Required credentials from Microsoft Entra
Value Where to find it
Application (client) ID App registration overview page
Directory (tenant) ID App registration overview page
Client secret value Certificates & secrets page

Set up the integration in Amazon Quick

After you complete the Entra configuration, create the integration in Amazon Quick.

  1. In the Amazon Quick console, choose Integrations.

  2. Choose the Actions tab.

  3. Choose Microsoft Teams and choose the Add (plus "+") button.

  4. Fill in the integration details:

    • Name – Descriptive name for your Teams integration.

    • Description (Optional) – Purpose of the integration.

  5. Choose your connection type and fill in the connection settings:

    1. For User authentication (OAuth), configure the following fields:

      • Base URLhttps://graph.microsoft.com/v1.0

      • Client ID – Application (client) ID from your Entra app registration.

      • Client Secret – Client secret value from your Entra app registration.

      • Token URLhttps://login.microsoftonline.com/{tenant-id}/oauth2/v2.0/token

      • Auth URLhttps://login.microsoftonline.com/{tenant-id}/oauth2/v2.0/authorize

      • Redirect URLhttps://{region}.quicksight.aws.amazon.com/sn/oauthcallback

    2. For Service authentication, configure the following fields:

      • Client ID – Application (client) ID from your Entra app registration.

      • Client Secret – Client secret value from your Entra app registration.

      • Token URLhttps://login.microsoftonline.com/{tenant-id}/oauth2/v2.0/token

      • Scope.default

  6. Choose Create and continue.

  7. Choose users to share the integration with.

  8. Choose Next.

Available actions

After you set up the integration, the following actions are available.

Microsoft Teams available actions
Category Action Description
Chats List Chats View your chat conversations.
Chats Create Chat Start a new chat conversation.
Chats Send Chat Message Send a message in a chat.
Teams List Teams View teams you're a member of.
Teams List Team Members View members of a team.
Teams Add Team Member Add a member to a team.
Channels List Channels View channels in a team.
Channels Create Channel Create a new channel in a team.
Channels List Channel Messages View messages in a channel.
Channels Send Channel Message Post a message to a channel.
Channels List Channel Members View members of a channel.
Channels Add Channel Member Add a member to a channel.
Users List Users View users in your organization.
Meetings List Online Meetings View your scheduled online meetings.
Meetings Create Online Meeting Schedule a new online meeting.
Meetings List Meeting Transcripts View transcripts from meetings.
Calendar List Calendar Events View events on your calendar.
Calendar Create Calendar Event Create a new calendar event.

Manage and troubleshoot

To edit, share, or delete your integration, see Managing existing integrations.

Authentication issues

  • Incorrect app registration – Verify the app registration in Microsoft Entra includes the required API permissions and that admin consent has been granted.

  • Expired client secret – Check if the client secret has expired in Certificates & secrets and generate a new one if needed.

  • Incorrect redirect URI – Verify the redirect URI in Microsoft Entra matches https://{region}.quicksight.aws.amazon.com/sn/oauthcallback.

Common error messages

  • Access denied. You do not have permission to perform this action – The authenticated user does not have the required permissions. Contact your administrator to verify and grant appropriate permissions.

  • AADSTS50020: User account from identity provider does not exist in tenant – The user account is not configured in the correct Microsoft Entra tenant. Verify the user account exists in the tenant that matches the Directory (tenant) ID in your app registration.