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
-
Navigate to Moveworks Setup Portal. Go to Core Platform > Connectors > Built-in Connectors and select Microsoft Teams.

-
Click on NEXT: ADD CREDS

-
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.

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.

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).

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.
Finding your Tenant ID and Primary domain
To find a tenant ID and a primary domain name, use the following steps:
- Sign in to the Azure portal.
- Select Microsoft Entra ID from the hamburger menu in the top left.
- 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:
- Bot Name
- Bot Friendly Name
- Microsoft Teams Tenant ID

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.