> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/guides-and-quickstarts/interfaces-and-end-user-experiences/publish-a-microsoft-teams-interface.md).

# Publish a Microsoft Teams interface

The legacy **Teams App** interface makes a workflow available through a Microsoft Teams application. Its deployment setup is separate from Teams actions that a workflow uses to access Microsoft services.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSQ1Sgy933krTyK0S4JpP%2Fuploads%2FYmbmhm1lXiiehBzYB4eG%2FG068.mp4?alt=media&token=b9a15c91-51e7-4e6f-b1f0-0918d6313812>" %}

## Before you start

This guide covers the legacy Microsoft Teams interface. Use it only where supported. Have permission to configure Entra, Azure Bot resources, and custom Teams apps in the intended tenant.

## Open manual deployment

Choose Microsoft Teams in Interface and read the legacy notice before opening Manual Deployment.

![Teams manual deployment settings](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/UdqHMkHWekOzAlbwl3iN/assets/g068-g068-01-legacy.png)

Follow the setup instructions shown for the supported interface in your deployment.

## Register and configure the application

Register the application in Microsoft Entra for the intended tenant.

![Microsoft application registration settings](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/EQy3tRKM5iAWqPEZT3b0/assets/g068-g068-02-identity.png)

Retain its application and tenant identifiers for the matching StackAI configuration.

Configure the Web authentication settings required by the deployment.

![Microsoft application registration settings](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/PJSITuzYDyw86IdaSn61/assets/g068-g068-03-web.png)

Copy its redirect and logout values rather than using identifiers from another application.

Review the required API permissions with your tenant administrator.

![Microsoft application registration settings](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/GLEbBt8Fxta4Kkz8eN7r/assets/g068-g068-04-permissions.png)

Configure only the permissions required by the integration and complete any required consent.

Use Expose an API to configure the application identifier, scope, and authorized clients.

![Microsoft application registration settings](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/byaHrDr0dUwEaGzk2PDS/assets/g068-g068-05-scope.png)

Use the values specified for your own deployment.

## Create and configure the Azure Bot

Create the Azure Bot resource with the matching application identity and tenant type.

![Azure Bot resource configuration](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/oE5GuywIeEIQGFWLcxzr/assets/g068-g068-06-bot.png)

Review these settings before creating the resource.

Configure the bot's channel and OAuth connection settings.

![Azure Bot resource configuration](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/bZckvs2rpT6BdEoqlhMG/assets/g068-g068-07-oauth.png)

Use the deployment's messaging endpoint and manage its secret through the required credential fields.

## Save matching settings in StackAI

Enter the matching application, tenant, and secret settings in StackAI and save.

![Teams integration credential configuration](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/o7tCd1vKdECyHHU41G87/assets/g068-g068-08-save.png)

A mismatch between the application and bot configuration can prevent authentication or message delivery.

## Generate and install the Teams package

Under Upload App Manifest, enter the bot's name and description and generate the package.

![Teams application package setup](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/q6u1N5dnh5JVm7T5DphA/assets/g068-g068-09-package.png)

Follow the tenant's approved process for uploading a custom Teams app.

## Use the bot and inspect its run

Open the installed bot in Teams and submit a representative request.

![Messaging bot response and execution](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/rWmUzlLbmIiB4EpJTBNX/assets/g068-g068-10-test.png)

Inspect the response to confirm the user-facing integration is working.

Locate the corresponding execution in Analytics.

![Messaging bot response and execution](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/SKTbQFkFpFD1HV94qEsH/assets/g068-g068-11-run.png)

Compare the received input and returned output with the Teams conversation, as well as checking run status.

## Important behavior

The Entra application, Azure Bot, and StackAI configuration must use matching identifiers and credentials. Mismatches can prevent sign-in or message delivery.

Use the current redirect URLs, endpoints, and client values supplied by your deployment.

## Continue

* [Microsoft Teams connector and tool setup](https://docs.stackai.com/guides-and-quickstarts/using-tools-and-actions/microsoft-teams-connector-and-tool-setup.md)
* [Publish a Chat Assistant](https://docs.stackai.com/guides-and-quickstarts/interfaces-and-end-user-experiences/publish-a-chat-assistant.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/guides-and-quickstarts/interfaces-and-end-user-experiences/publish-a-microsoft-teams-interface.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
