> For the complete documentation index, see [llms.txt](https://atlas.anywhere.now/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://atlas.anywhere.now/attendant-console/shared-components/deploy-teams-app-manifest.md).

# Deploy as a Microsoft Teams app

Upload and assign the Attendant Console Microsoft Teams app manifest.

Attendant Console can be made available in Microsoft Teams by uploading the supplied Microsoft Teams app manifest. The same deployment options apply to Attendant Console for Microsoft Teams and Attendant Console for Dialogue Cloud; use the manifest file supplied for the correct product track.

## Manifest files

| Product                               | Manifest file                     |
| ------------------------------------- | --------------------------------- |
| Attendant Console for Microsoft Teams | `attendant.anywhere365.io.zip`    |
| Attendant Console for Dialogue Cloud  | `dr-attendant.anywhere365.io.zip` |

{% hint style="info" %}
Keep the manifest file zipped. If Windows blocks the downloaded `.zip` file, unblock it in the file properties before uploading it.
{% endhint %}

## Option A: Allow a user to upload the custom app

### Administrator steps

1. Open the Microsoft Teams admin center.
2. Go to **Microsoft Teams apps** > **Setup policies**.
3. Open the policy assigned to the operator users.
4. Enable **Upload custom apps**.
5. Save the policy.

### User steps

1. Open Microsoft Teams.
2. Select **Apps** or **Manage your apps**.
3. Select **Upload an app**.
4. Choose the option that matches the tenant policy:
   * **Upload a custom app** for the user's client.
   * **Submit an app to your org** when administrator approval is required.
5. Select the supplied manifest `.zip` file.
6. Select **Add**.

<figure><img src="https://4184412221-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ffsyg51MeZptkjIReLgC5%2Fuploads%2Fgit-blob-f2a9207479061c9f5860832819644f5264bbbf7e%2Fattendant-console-teams-upload-app-add.png?alt=media" alt="Microsoft Teams upload app dialog showing the Add action for the Attendant app"><figcaption><p>Add the supplied Attendant Console app package in Microsoft Teams.</p></figcaption></figure>

{% hint style="info" %}
If Microsoft Teams displays a sideload warning because the app has a live SaaS offer, the source says the user can acknowledge the warning and continue.
{% endhint %}

## Option B: Upload the app to the organization catalog

1. Open the Microsoft Teams admin center.
2. Go to **Microsoft Teams apps** > **Manage apps**.
3. Select **Upload**.
4. Select the supplied manifest `.zip` file.
5. Confirm that the app is visible in the organization catalog.

After the app is available, users can add it from **Built for your org** in Microsoft Teams.

{% hint style="warning" %}
If an older Attendant app is also visible in the Microsoft Teams app store, select the organization app with the higher version number from **Built for your org**.
{% endhint %}

## Option C: Install or pin the app for users

1. Open the Microsoft Teams admin center.
2. Go to **Microsoft Teams apps** > **Manage apps**.
3. Confirm that the supplied manifest has been uploaded.
4. Go to **Microsoft Teams apps** > **Setup policies**.
5. Open the policy assigned to the operator users.
6. Add the Attendant app under **Installed apps** to install it automatically.
7. Add the Attendant app under **Pinned apps** if it must appear in the Microsoft Teams side rail.
8. Save the policy.

The app becomes available to users who receive the setup policy.

<figure><img src="https://4184412221-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ffsyg51MeZptkjIReLgC5%2Fuploads%2Fgit-blob-f3625045cc98ed2985510719174a9fb1edd3ae85%2Fattendant-console-teams-app-pin.png?alt=media" alt="Microsoft Teams side rail with the Attendant app pinned"><figcaption><p>Pinned Attendant app in Microsoft Teams.</p></figcaption></figure>


---

# 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://atlas.anywhere.now/attendant-console/shared-components/deploy-teams-app-manifest.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.