AI Chat Onboarding Information

Who will be involved in the technical onboarding?

  1. Provide the Microsoft 365/Azure Tenant Id to allow the Chime V5 Teams app to route chats.

  2. Azure Admin consents to the use of Graph API permission needed to enable Azure AD/Entra login for the Chime V5 web application. See Detailed Documentation >>

  3. Teams Admin approves Chime V5 Teams app for the organization. See Detailed Documentation >>

  4. Teams Admin pushes Chime V5 app org-wide or to specific user groups. See Detailed Documentation >>

Technical steps and process to onboard our AI chat service including integration with Microsoft Teams

  • Azure AD/Entra Admin - Approve the use of Graph API permissions for Chime V5 web application.

  • Teams Admin - Approve Chime V5 Teams app for the organization, configure user group permissions, and optionally configure any theming or branding options.

  • If you are a Project Lead or coordinator, you may want to review this page covering the POC Roadmap before going further into this page.

Required Steps

Step 1: Provide the Microsoft 365/Azure Tenant Id to allow the Chime V5 Teams app to route chats

During the setup process, Instant will need the Tenant Id for your organization. Typically, we will get this from you in the initial set of questions for setting up a POC. The Tenant Id is required to stand up Chime V5 in order to route chats to your agents. Here is some Microsoft documentation on how to Find your Microsoft 365 tenant ID - Microsoft resource

The Tenant Id will also be used to configure Azure AD/Entra authentication for your Chime V5 tenant.

Step 2: Azure Admin consents to the use of Graph API permission needed to enable Azure AD/Entra login for the Chime V5 web application

The next step involves configuring Azure AD/Entra authentication, which enables you to use your Office 365 account for authentication. This configuration is important for the Chime V5 Azure AD App registration, which has specific permissions:

[ email - Delegated ] [ openid - Delegated ] [ profile - Delegated ] [ User.Read - Delegated ]

For more detailed documentation, we have a comprehensive article covering the requested permissions. This article covers the list of API permissions you will need and details of what each of them do and are used for. See Detailed Documentation >>

O365 cross tenant authorization to enable chatbot service

Once the setup of your Chime Tenant is complete, your Azure Admin will need to go to the login page for Chime and will be prompted to consent on behalf of your organization. Once that is completed, Chime will be updated to use Office 365 authentication.

Step 3: Teams Admin approves Chime V5 Teams app for the organization

Once you have gone through the configuration process, a Teams Admin can make Chime V5 available for the group you want to test with. Depending on how your organization is set up, there are some settings in the Teams Admin Center that would need to updated.

Here is a general guide the Teams Admin could use to locate the settings for allowing the download of the Chime V5 app, for a more detailed walkthrough of this please follow this guide:

Teams Admin: How to approve the Chime V5 app and allow it to be installed by users in your organization

Planning on running a POC for Chime V5 - here are some commons tasks with branding and deployment:

Here is some additional documentation from Microsoft on managing Apps and App permissions for a Teams Admin:

Overview of app management and governance in Teams admin center - Microsoft resource

Step 4: Teams Admin pushes Chime V5 app org-wide

At this point you will want to know if Chime V5 is an app that you will want to add into the Global (Org-wide default) permission group. Before pushing the app to the whole tenant, here are a few things to consider for the end user experience:

Follow this guide for instructions on How to have a Teams Admin push the Chime V5 app org-wide