AI Assistant in Microsoft Teams (Non-App Store) Setup Guide
AI Assistant in Microsoft Teams (Non-App Store) Setup Guide
AI Assistant in Microsoft Teams (Non-App Store) Setup Guide
This guide will walk you through the process of setting up a Moveworks AI Assistant in Microsoft Teams. Along the way, you will capture the following information:
Once you have these items, add the connector in Moveworks Setup by following this guide: System Connectors.
If you are leveraging a Firewall, CASB, or VDI, and have another layer of network firewall rules. Ensure the following Moveworks owned domain is in an allowlist so that Moveworks can render content in Microsoft Teams Task Modules.
https://app.moveworks.aiYou can find the Tenant ID prior to the call by visiting the following URL. Replace <domain_name> with your company domain name.
https://login.microsoftonline.com/<domain_name>/.well-known/openid-configuration
You will receive a JSON response. Look for the key token_endpoint and find the Tenant ID in the url.
{“token_endpoint”:“https://login.microsoftonline.com/<tenant_id_here>/oauth2/token” ….
Navigate to https://portal.azure.com/#create/Microsoft.AzureBot
Fill out the information as follows:
Bot handle - should be named the AI Assistant name that was approved.
Subscription - This should default to “Pay-as-you-go” or another subscription that you have available.
Resource Group - Create new group for the bot.
Resource Group Location - Choose lowest latency.
Pricing tier - Set this to F0 (this is a free tier).

Messaging Endpoint leave this blank for now and we will revisit it later in the configuration.
Under Microsoft App ID,
Type of App - select Single Tenant for the selection.

Select Create new Microsoft App ID and hit Review + create

Find the Azure Bot that was created by waiting for the deployment to finish and then clicking on the “Go to resource” button. Or, by searching for the bot in the Azure console.

Navigate to Bot Profile on the left hand pane.
Upload the approved bot icon to the Icon field.
Set the Display name of the bot to the approved AI Assistant name or set this to “Moveworks” temporarily.
Click Apply.
Navigate to Configuration on the left hand pane.
Add the following URL based on your region (where<MSappId> is the string in the “Microsoft App ID” you copied in the above step).
US Region: https://app.moveworks.ai/<MSappId>/api/messages
EU Region: https://app.am-eu-central.moveworks.ai/<MSappID>/api/messages
Canada Region: https://app.am-ca-central.moveworks.ai/<MSappID>/api/messages
Australia Region: https://app.am-ap-southeast.moveworks.ai/<MSappID>/api/messages
Note: If you are installing your Moveworks AI Assistant in a GovCloud, please follow this guide: /ai-assistant/chat-platform-experiences/microsoft-teams/ai-assistant-in-microsoft-teams-gcch-setup-guide
Only use non “US Region” messaging endpoints if your Moveworks tenant is not hosted in the US region.
If you have any questions please reach out to your Moveworks team.

Add the Microsoft Teams Feature Channel
Navigate back to your Azure Bot configuration.
Select the Channels tab on the left. Beneath Add a feature channel, select the Microsoft Teams icon and on the next screen, click Save.


Next you will add the Teams and MS Graph connector to Moveworks Setup by following this guide: System Connectors, using the following information:
If you are connecting multiple Teams tenants to a single Moveworks organization, refer to the Multi-Tenant Moveworks Setup Guide for guidance on naming and mapping your connectors.
Follow implementation steps in this guide. The configuration is similar whether you are connecting a single tenant or setting up a multi-tenant environment.
You will need these assets to publish the app:
Using the following file template to create the manifest.json file, replace the <MSAP_ID> and <AI_ASSISTANT_NAME > text in the template below, with your Microsoft App ID and the name of your AI Assistant respectively. If you have not decided on a name yet, you can use the name “Moveworks” as a temporary placeholder name.



Tip: You can right click and save the example images in .png format as placeholders if the AI Assistant avatar has not been finalized yet._



Moveworks is able to ensure that the bot’s functionalities are only accessible by approved users during development. The AI Assistant will be visible in the MS Teams app store but users will not be able to communicate with it.
In some cases our customers would like to have more granular control over this access. You can do this in the Microsoft Teams Administration Console.
Navigate to https://admin.teams.microsoft.com/.
Go to the dashboard on the left → Select Teams apps> Setup policies -> Add New Policy.
Create a custom app policy to allow the AI Assistant you just created.
The steps below should be completed when the AI Assistant is ready for go-live.
Visit admin.teams.microsoft.com.
From the options on the left, select Teams apps ⇨ Setup policies.
Click on the Global (Org-wide default) policy and then click Edit.

Toggle the order of the apps so that the installed AI Assistant application is below the Chat option.



Option B: Create policy for a specific group of users in Azure using Powershell
Locate your group in Azure that you want to apply the policy to. Copy the object id for the group.

Open Powershell and enter the following commands. Once complete this can take up to 72 hours to take effect, depending on the size of the group. See here for more information.
Replace the group_id with the correct value above. The group_id is the Azure object id and “Moveworks Bot Users” is the name of the policy you used in the previous step.Example based on above:
A: Moveworks AI Assistant can be unpinned from the sidebar in Microsoft Teams by the user.
A: Moveworks AI Assistant will remain removed from the current Teams session, however once the user logs out of teams and logs back on the app setup policy kicks in and re-adds Moveworks Bot.
A: user can move the Moveworks AI Assistant around in the left side bar, however the App Setup Policy will overwrite this once the user logs off and logs back onto teams.
A: Try using Microsoft’s App Validation tool, this will tell you if there are any issues with the package you are uploading.