> For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://help.moveworks.com/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://help.moveworks.com/_mcp/server. # Single Tenant Microsoft Teams Moveworks Setup Guide This guide explains how to set up a single Microsoft Teams chatbot in Moveworks. It covers connector creation, identity ingestion, service account configuration, chatbot setup, roster validation, and notification routing. ## Implementation Steps ### Step 1: Create MS Teams Connector 1. Navigate to **Moveworks Setup** Portal. Go to **Core Platform > Connectors > Built-in Connectors** and select Microsoft Teams. ![Built-in Connectors page with Microsoft Teams selected](https://files.buildwithfern.com/moveworks.docs.buildwithfern.com/12ff620bbea77fb797789e94ea11ad0e632c0cfe310f1c42ac9bd8d34efd051d/docs/assets/images/microsoft-teams/builtin-connectors-ms-teams.png) 2. Click on **NEXT: ADD CREDS** ![Microsoft Teams connector page with NEXT: ADD CREDS button highlighted](https://files.buildwithfern.com/moveworks.docs.buildwithfern.com/b9c56438f96c6a26824c13cb1d308357ca51084860890c4a02d9c8620c909e72/docs/assets/images/microsoft-teams/next-add-creds.png) 3. Name the connector "msteams" and for the **Authentication Type** select ***Microsoft Bot App Store Auth*** if you are leveraging the Microsoft Teams App Store, then Click **Save**. ![Credential Details with Microsoft Bot App Store Auth authentication type selected](https://files.buildwithfern.com/moveworks.docs.buildwithfern.com/eaae59874a400ee494b2a00ad38f8897597e3d70570326d1d46c103ed85f16e0/docs/assets/images/microsoft-teams/ms-teams-appstore-auth.png) If you are configuring a Non-App Store based installation for a Moveworks sandbox, EU, GovCloud, AU, or CAC based installation you should use **OAuth2 Client Credentials Grant**. ![Credential Details with OAuth2 Client Credentials Grant authentication type selected](https://files.buildwithfern.com/moveworks.docs.buildwithfern.com/31d7c52319f6adaf0c40723b9097fae699a1a1a4d9fac226de6109ab640c630e/docs/assets/images/microsoft-teams/ms-teams-non-appstore.png) ### Step 2: Create MS Graph Connector Similarly, add an **MS Graph** connector named `msgraph`. This connector handles identity/user data ingestion from your Microsoft / Entra tenant. For the **Authentication Type**, select **Microsoft App store Auth** if you are leveraging the Microsoft Teams App Store. For the **Tenant ID**, use the **Primary domain** of your Entra/Azure tenant (in the format `company.com`). ![MS Graph connector Credential Details with Microsoft App store Auth selected](https://files.buildwithfern.com/moveworks.docs.buildwithfern.com/90055aaa2b265da90b11f915c2e9f05a0010c14d1c3b0af4c0011c781f85d3cf/docs/assets/images/microsoft-teams/ms-graph-connector-appstore-auth.png) If you are configuring a Non-App Store based installation for a Moveworks sandbox, EU, GovCloud, AU, or CAC based installation you should use **OAuth2 Client Credentials Grant** and enter in the information from the AzureBot you created by following the steps here: [Create the Azure Bot in your tenant](/ai-assistant/chat-platform-experiences/microsoft-teams/microsoft-teams-bot-non-app-store-setup-guide#create-the-azure-bot-in-your-tenant). #### Finding your Tenant ID and Primary domain To find a tenant ID and a primary domain name, use the following steps: 1. Sign in to the Azure portal. 2. Select **Microsoft Entra ID** from the hamburger menu in the top left. 3. The **Microsoft Entra ID Overview** page appears. To find the Microsoft Entra tenant ID or primary domain name, look for **Tenant ID** and **Primary domain** in the **Basic information** section. You can also find a tenant ID in the Azure portal in other ways: * Select **Microsoft Entra ID** from the menu. Then, locate the **Manage** section on the menu and select **Properties**. The **Properties** page also displays a user's associated Tenant ID. ### Step 3: Add MS Graph Connector to Identity Configuration Navigate to **Core Platform → User Identity → Import Users**, click **Add Identity Source**, and select the `msgraph` connector as the source. Add the `user_id_info.channel_id_info` for the `msteams` connector so Moveworks identity user records carry the Teams Channel ID. Note: If your Moveworks org was created after May 2026, you will need to navigate to **Core Platform → User Identity → Identity Configuration** to add ms\_graph as a connector leveraged in Identity Ingestion. Note: MS Graph does not need to be added as the primary source connector. ### Step 4: Create Chatbot Config Navigate to **Setup → Manage Chatbots → Chatbots**, click **Add New Chatbot**, configure it for the Teams tenant, and select the `msteams` connector created in Step 1. Note the `integration_id` for use in later steps. Navigate to **Chat Platforms > Manage Chatbots** and configure your Chatbot with the following settings. Be sure to replace: 1. Bot Name 2. Bot Friendly Name 3. Microsoft Teams Tenant ID ![Chatbot configuration page with Bot Name, Bot Friendly Name, and Microsoft Teams Tenant ID fields](https://files.buildwithfern.com/moveworks.docs.buildwithfern.com/5face5cb47f3c2522a7a87c851b17836e1aae586cd54d6b2e2639317683fb20c/docs/assets/images/microsoft-teams/ms-teams-chatbot-config.png) **NOTE: For a Microsoft Teams App Store Installation, all other configurations should match the screenshot above exactly.** If you are configuring a Non-Appstore based Installation, be sure to update the Microsoft Teams App Id, and Microsoft Teams App GUID accordingly. ### Step 5: Validate User Identity Once 4 hours have passed, and Moveworks User Import has ran successfuly, navigate to **Setup → User Identity → View Users** and search for test users. Verify that expected users have a valid `channel_id` for the `msteams` integration and that the `integration_id` appears in user records. ### Step 6: Configure Notification Routes Navigate to **Setup → AI Assistant → Notification Routes** and confirm `msteams` is set as the bot channel for outbound notifications.