---
title: "How Voice4Teams is provisioned"
canonical: "https://help.callroute.com/space/CKB/2632318981/How%20Voice4Teams%20is%20provisioned"
format: markdown
---
Voice4Teams requires a connection between Callroute and your Microsoft 365 tenant.

The initial connection is started from the **8x8 Admin Portal**. Once authorised, Callroute can synchronise with Microsoft 365 and configure the Microsoft Teams users that use Voice4Teams.

## Before you begin

The Microsoft 365 account used to establish the connection must have the administrator permissions required to authorise Callroute.

For the initial connection, the following Microsoft 365 administrator roles are required:

- **Teams Administrator**
- **Domain Name Administrator**
- **User Administrator**
- **Application Administrator**

A **Global Administrator** has the required permissions, but Global Administrator is not specifically required. The roles above can instead be assigned to the user completing the authorisation.

Callroute uses Microsoft Graph permissions to discover and manage the Microsoft 365 configuration required by the service.

For a detailed explanation of the Microsoft Graph permissions requested by Callroute, see: **[Microsoft Permissions Deep Dive](https://callroute.atlassian.net/wiki/spaces/CKB/pages/860192770)**

## Connect your Microsoft 365 tenant

Once your Voice4Teams service has been created, the **8x8 Admin Portal** will provide the option to connect your Microsoft 365 tenant.

To establish the connection:

1. Start the Microsoft 365 connection from the 8x8 Admin Portal.
2. Sign in to Microsoft 365 using an account with the required administrator permissions.
3. Review the permissions requested by Callroute Voice.
4. Accept the Microsoft permissions request.
5. Continue through the remaining authorisation steps using the **same Microsoft 365 user account**.

It is important that you use the **same Microsoft 365 account throughout the authorisation process**. Using a different account during a subsequent authorisation step can prevent the connection from completing successfully.

## What happens after authorisation?

Once Microsoft consent has been granted successfully, Callroute establishes the connection to your Microsoft 365 tenant and performs the initial synchronisation.

By default, Voice4Teams synchronises **Teams voice users**. The synchronisation scope can subsequently be changed from the Teams service settings within Callroute.

As part of the initial Voice4Teams setup, 8x8 and Callroute also prepare the service information required to connect your 8x8 users to Microsoft Teams.

For customers moving from the legacy DSTNY Voice4Teams service, the existing Voice4Teams users can then be identified and prepared for migration.

See **[Microsoft 365 user synchronisation](https://callroute.atlassian.net/wiki/spaces/CKB/pages/2633695233)** and **[Migrate from legacy Voice4Teams](https://callroute.atlassian.net/wiki/spaces/CKB/pages/2633465862)** for more information.

## Do I need to re-authorise Callroute?

Routine re-authorisation is not required.

Callroute automatically refreshes the Microsoft authentication tokens used by the service.

However, the Microsoft 365 account used by Callroute must continue to have sufficient permissions for ongoing operation.

After the initial connection has been successfully established, the account requires either of the following Microsoft 365 administrator roles:

- **Teams Administrator**
- **Teams Communications Administrator**

Either role provides the permissions Callroute requires for ongoing Voice4Teams synchronisation and management.

This means that if you use a dedicated service account for the Voice4Teams connection, the additional administrator roles required during initial authorisation can be removed once the connection has been successfully established, provided the account retains either **Teams Administrator** or **Teams Communications Administrator**.

If the account no longer has sufficient permissions, Callroute will be unable to perform required Microsoft Teams moves, adds, changes and deletes.

The **[Callroute Health Checker](https://callroute.atlassian.net/wiki/spaces/CKB/pages/868581416)** will display a warning if the permissions required for ongoing operation are no longer available.

## Microsoft 365 synchronisation

Once connected, Callroute automatically synchronises with Microsoft 365 every **24 hours**.

This scheduled synchronisation keeps Callroute's view of your Microsoft Teams environment up to date.

For customers migrating from legacy Voice4Teams, normal Microsoft 365 synchronisation is separate from the **Identify V4T** process used to identify and validate existing Voice4Teams users before migration.

See **[Microsoft 365 user synchronisation](https://callroute.atlassian.net/wiki/spaces/CKB/pages/2633695233)** for more information.