This article covers the process for integrating Chronus with your organization's enterprise Microsoft Teams account, which will enable your organization's users to create meetings via Teams Video call.

This process requires the following:

1. An active global Chronus administrator account & a Microsoft Teams Enterprise account.

2. A dedicated account/service account in Azure

It is recommended to have the name of the dedicated account as ‘Teams Scheduler’/’Chronus Scheduler’

3. Users in Chronus must be a member of the organization's Enterprise account to set up Teams meetings within Chronus.

Approach 1: Dedicated Host Account with administrative privileges in Teams

With this approach, you’ll set up a "link" between Chronus and Teams so they can communicate with each other.

Step 1: Add the dedicated/service account user as a global administrator in Chronus. The integration of Teams with Chronus has to be done from a dedicated account created for Chronus. This dedicated account will act as a host for all Teams meetings created through Chronus (refer to item 2 in the section above for additional context).

Step 2: Login to Chronus using the dedicated user account and go to the Manage page at the Global level. From there, click the Engagements card, then click the Integrations icon.

Step 3: On this page, integrations available to your organization will be listed. Click Teams to proceed.

Clicking on Integrate will cause the pop-up shown below to be displayed:

Click Accept—you have finished Integrating your enterprise Microsoft account with the Chronus Platform!

​Approach 2: Organization-wide Approval

The below action has to be performed by MS Teams' global admin to get the required permission for this integration.

Update the URL below by replacing the 'customer_tenant_id' (bolded below) with your organization's tenant ID, then copy and paste the URL into your browser to grant Chronus the needed permissions for creating Teams Video meetings:
​
​URL - https://login.microsoftonline.com/customer_tenant_id/v2.0/adminconsent?scope=offline_access+https%3A%2F%2Fgraph.microsoft.com%2FUser.ReadBasic.All%20OnlineMeetings.ReadWrite&client_id=ded487a6-3555-47b1-a66f-82177581baaf&redirect_uri=https%3A%2F%2Fsecureproductioneu.chronus.com%2Fsession%2Foauth_callback&response_type=code
​
Running this URL will authenticate Chronus with two permissions for users in your organization: User.ReadBasic.All and OnlineMeetings.ReadWrite for Chronus' client ID (ded487a6-3555-47b1-a66f-82177581baaf).

After completing the above action, proceed by following steps 1, 2, and 3 as detailed above in Approach 1.

Once the integration is complete, you will need to add ‘Teams Video call’ as a meeting mode under the Permissions tab of the Program Settings tool in each track that the feature will be available for:

On enabling ‘Teams video call’ as a meeting mode option, participants will see the following interface when creating new meetings:

And the following interface when viewing a meeting set up with Teams Video Call as the meeting mode:

If a program participant does not have access to the organization's Teams account, the Teams meeting option will not be available to them.

Global administrators will have control over the integration and removal of integration and the ability to enable or disable Teams for specific programs in their instance. Track-level administrators can only enable or disable Teams for the program they administer.

A global administrator can log in to Chronus and remove Teams from the Integrations tool on the global Manage page.

What kind of data will Chronus be able to access from customers’ Teams account?
Chronus will only have permission to view and manage all user meetings and view basic user information which is First Name, Last Name, Email, and Photo.

Would program participants need to authorize their Teams account?
No, the participants do not need to do any authorization on their end. Note however, that users who are not part of the organization's enterprise account will not have the ability to create Teams meetings.

Can I extend Teams capabilities to only one or a selected list of programs in my organization?
Yes—track-level administrators and global administrators can enable or disable the ability to create Teams meetings in their specific program, under the Permissions tab in the Program Settings tool of each individual track.

Can the administrator who authenticated Teams be removed from Chronus once the integration has been completed?
Yes—after the integration is complete, the administrator can be removed or deactivated.

How do I remove Teams integration to Chronus?
Global administrators will have the option to remove the integration from Chronus under the Integrations tool, found on the global Manage page beneath the Engagements card.

Should a program participant be logged in to their Teams account if they want to create a meeting?
The user does not need to be logged in to Teams when they are creating the meeting as long as their individual account is listed under the organization's Teams account.

Who will be the host of the meetings created?
By default, the host of the meeting will always be the dedicated account created for Chronus in the customer’s enterprise Microsoft account. Refer to item 2 under the Prerequisites section for more context.

Will the meetings be recorded and will Chronus have access to them?
No, Teams Integration API (Graph API) does not support partner (Chronus) access to recordings. This is not something that Chronus has any control over.

What does the error "To set-up Teams video calls directly from here, you have to be part of organization's Teams account. For further details, please reach out to your Program Administrator" indicate?.
The most common cause of this type of error is a permissions-related component (i.e. if users are categorized under departments in their Active Directory, permissions may need to be granted to users in specific departments to utilize Chronus).

We would definitely recommend reaching out to whoever set up the integration between Teams and Chronus and sharing the error message with them—they should be able to fix this issue.