Skip to main content
Back to messaging or digital channels Integrate your agent into Microsoft Teams channels, chats, and Microsoft 365 Copilot through an Azure Bot registration and a Teams application.
The Microsoft App ID must be the same value in the Azure Bot registration and in the App ID field of the channel connection in Artemis. A mismatch is the most common cause of a Teams integration that won’t connect.

​
Configure the integration

The setup runs across four surfaces in this order: the Azure Portal, the Microsoft Teams Developer Portal, the Teams Admin Center, and Artemis.
1

Create an Azure Bot

  1. Sign in to the Azure Portal and search for Azure Bot in the Create a resource section.
  2. Select Create and complete the bot registration.
  3. When the deployment completes, select Go to resource under Next steps.
2

Create a client secret

  1. In the Azure Bot resource, go to Settings -> Configuration.
  2. Select the Manage password link beside the Microsoft App ID. This opens the app registration’s Certificates & secrets page.
  3. Select + New client secret and create the secret.
  4. Copy the secret value immediately and store it securely.
When you copy the client secret, use the Value, not the Secret ID. The Secret ID won’t authenticate. The Value appears only once. If you navigate away before copying it, create a new client secret.
While you’re in the app registration, copy the Application (client) ID from the Overview page. This is your Microsoft App ID, also referred to as the Enterprise App ID in the steps below. Copy the Directory (tenant) ID from the same page.
3

Configure supported account types

  1. In the app registration, go to Authentication (Preview) -> Supported accounts.
  2. Select Multiple Entra ID tenants, choose Allow all tenants, and save.
4

Enable the Microsoft Teams and Microsoft 365 channels

  1. Return to the Azure Bot resource and go to Settings -> Channels.
  2. Enable Microsoft Teams and Microsoft 365.
5

Create or import the Teams application

  1. Sign in to the Microsoft Teams Developer Portal.
  2. Create a new application or import an existing manifest.
  3. Go to Configure -> Basic information, enter the Short name and Long name, and set the Application (client) ID to the Microsoft App ID you copied in step 2.
6

Configure the bot, commands, and scopes

  1. Go to Configure -> App features and select Bot.
  2. Enter the Enterprise App ID as the bot ID.
  3. Add the project commands, utterances, and descriptions.
  4. Select the Personal, Team, and Group Chat scopes.
7

Update the app package

  1. Go to App package editor -> Actions -> Edit to open manifest.json.
  2. Update the Web App ID (webApplicationInfo.id) and the Copilot/Agents ID (copilotAgents.customEngineAgents.id) to the Enterprise App ID in both locations.
  3. To support file attachments, set bots[0].supportsFiles to true.
  4. Select Update and confirm.
Attachment ingestion currently supports personal chat scope only.
8

Publish the application

  1. In the Teams Developer Portal, go to Publish -> Publish to org, select Get started, and publish the application.
  2. Open the Teams Admin Center and go to Teams apps -> Manage apps.
  3. Search for the application, open it, and publish it.
Before you leave the Teams Developer Portal, copy the App ID from the application’s Dashboard. This is the Bot App ID that Artemis asks for in the next step.
9

Create the connection in Artemis

Open Artemis, select the required project, and go to Deployments -> Channels -> Microsoft Teams -> + New. On the New Microsoft Teams Connection dialog, provide the following fields.Select Create.
10

Configure the messaging endpoint

  1. Open the connection you created and copy the Webhook URL from the Overview tab.
  2. In the Azure Portal, open the Azure Bot resource and go to Configuration.
  3. Paste the Webhook URL into the Messaging endpoint field.
  4. Enable the Streaming Endpoint and select Apply.
11

Validate in Teams and Copilot

  1. Open Teams and go to Apps.
  2. Search for the published application, open it, and select Add. To validate in Copilot, select Open with Copilot.
  3. Trigger the configured queries and verify the Artemis response.

​
Key values reference

​
Validation checklist

Confirm each item before you hand the channel to users.
  • Azure Bot is created and accessible.
  • Client secret is generated and securely saved.
  • Supported accounts are configured as required.
  • Microsoft Teams and Microsoft 365 channels are enabled.
  • Teams application is created or imported and basic information is configured.
  • Bot ID, Enterprise App ID, commands, and scopes are configured.
  • App package IDs are updated and the app is published.
  • Artemis Microsoft Teams connection is created successfully.
  • Webhook URL is configured as the Azure Bot messaging endpoint.
  • Streaming Endpoint is enabled and changes are applied.
  • Application is available in Teams and Copilot, and responses come from Artemis.

​
Manage an existing Microsoft Teams channel

Opening a channel from Deployments -> Channels -> Microsoft Teams shows four tabs: Overview, Credentials, Configuration, and Deployment.
The Connection Summary shows these fields.Under Setup Instructions, the tab shows the Webhook URL to set as the bot’s messaging endpoint in Azure, the Bot App ID for reference, and the Require verified Teams identity toggle.

​
Require verified Teams identity

Turn this on to require Microsoft-resolved Teams profile identity before the connection starts or resumes a session. Leave it off for baseline Teams conversations.When the toggle is on, Runtime resolves the sender’s Microsoft profile email or UPN through the Bot Connector member endpoint before it allows the turn. If the identity can’t be resolved, the turn doesn’t proceed. This confirms that the person on the other end is the Teams user their profile claims they are, which matters for agents that act on a user’s behalf or return information scoped to that user.The toggle relies on the credentials already configured for this connection or its selected auth profile, and on the bot staying installed and reachable in Teams. It doesn’t use Microsoft Graph consent, OBO settings, or Graph scopes.The Stronger identity verification setup panel below the toggle lists the specific requirements to complete when you enable it.