Skip to main content
The Microsoft Teams app channel publishes your agent as an installable app in a customer’s Teams app catalog. It supports personal chats only.

​
Prerequisites

On a Noxus-managed deployment the Teams App Catalog provider is configured from platform settings, and its form shows no fields. Disconnecting the provider still turns it off: tenant administrators cannot connect, existing connections stop refreshing, and Teams apps are not provisioned. On a self-hosted deployment a platform administrator configures it under Settings → Platform → Integrations: the OAuth client that tenant administrators connect with, and the provisioning identity Noxus publishes apps with (Noxus Entra tenant ID, provisioning app client ID and secret, Azure subscription ID and resource group). Teams app deployments report that the platform is not configured until all of them are set. In both cases the instance’s OAuth callback URL, shown in the provider dialog as https://<host>/api/backend/integrations/oauth/callback, must be registered as a redirect URI on the Azure app that tenant administrators sign in with. A tenant administrator must:
  • Connect the Teams App Catalog integration in Noxus and grant AppCatalog.ReadWrite.All.
  • Allow custom app uploads in the Teams admin center.
  • Approve the published app in the Teams admin center when tenant policy requires approval.

​
Publish the app

Create a Microsoft Teams app deployment, select the tenant administrator’s catalog connection and choose a published agent version. Set the deployment online to begin publication. The deployment moves through these states:
  • Publishing while Noxus creates and submits the app.
  • Awaiting approval when the Teams tenant requires an administrator to approve it.
  • Online when people can install and message the app.
If publication fails, the deployment shows the failure reason. Resolve the reported problem, then select Retry.

​
Operate the deployment

Pause an online app to stop receiving and sending messages without removing it from Teams. Resume it when you are ready to serve messages again. You can change the pinned agent version on a published app. The next conversation uses the selected version without republishing the Teams package.

​
Configure the deployment

Use deployment-specific instructions to tailor the agent for Teams, and choose which channel actions it may use. You can also set message and conversation rate limits, expire idle conversations, and choose whether replies show tool calls, sources, and thinking.

​
Use the app in Teams

People can install the app from Built for your org and chat with the agent in a personal conversation. Teams shows the agent’s progress while it works, and messages can include documents or images for the agent to read. When the agent sends a file, Teams first displays a consent card. Accept the card to upload and receive the file in the chat. Answers can show native source citations alongside the Teams AI-generated label.

​
Retire or delete the app

Deleting a published app starts retirement, which can take a few minutes while Noxus removes it from Microsoft Teams and Azure.