---
title: "September 2025"
canonical: "https://help.callroute.com/space/CKB/1881505793/September%202025"
format: markdown
---
> Macro (toc)


### Bulk Assign users Personas and phone numbers via CSV

Until now, bulk assignment of phone numbers and personas was only available through the **Numbers** section. This made it difficult to provision Microsoft 365 users during migrations — for example, assigning personas without phone numbers, or allocating phone numbers with extensions.

This update introduces a **CSV export/import process** designed for **day 1 provisioning at scale**. You can download a CSV of users (including their current phone number and persona assignments), update it as needed, and re-upload to apply all changes in bulk. While particularly valuable for migrations and initial tenant setup, it can also simplify ongoing management when needed.


![Screenshot 2025-09-12 at 12.43.38.png](media://358e8000-cb1e-4971-82bf-b3f0c25061be)

**Example CSV format. **

|  |  |  |
| --- | --- | --- |
| upn | persona | line_uri |
| [john.smith@example.com](mailto:john.smith@example.com) | Callroute | 441256211111 |
| [adam.smith@example.com](mailto:adam.smith@example.com) | Alternate | 441256211112;ext=1111 |


### Improvements to reporting

Reporting has undergone a significant update to improve performance and usability. Key enhancements include:

- **Faster load times** for reports.
- **New filtering options** — you can now filter call data by the country dialled.
- **Enhanced charting** — reports now include the ability to plot data by destination country, providing clearer insights into calling patterns.

These improvements make it quicker and easier to analyse usage trends and spot key activity across your tenant.


![Screenshot 2025-09-12 at 13.30.12.png](media://a917ee34-16e1-4136-b8a8-34d9032cb971)


### Task Manager Detail

Each task can now be expanded to show more information about the specific activity being performed. This makes it easier to see what is happening during syncs with Microsoft 365 to ensure that Callroute data stays aligned with the tenant.

This enhancement also lays the groundwork for a future release, where we’ll populate **full audit detail** of what was updated during these sync operations — giving admins complete visibility into changes between Callroute and Microsoft 365.

![Screenshot 2025-09-12 at 13.32.30.png](media://4b105c66-ba9e-4486-a9b5-2307186a1bd3)


### Microsoft Teams delta sync

Synchronizing with a connected Microsoft tenant has historically been a compute-intensive and time-consuming process, particularly for larger tenants (500+ users).

This update introduces support for Microsoft’s new **delta sync** capability. With delta sync, Microsoft issues a token at the end of each synchronization. On the next sync, Callroute sends this token with the request, and Microsoft responds only with the changes since the last sync.

By processing only the updated records rather than the entire tenant, sync times are dramatically reduced. For example, a sync that previously took 30 minutes for a 15,000-user tenant can now complete in just a few seconds.

> 📝 NOTE: When delta sync is first enabled, Callroute must perform a **full sync** of all users in order to obtain the initial token. After this, all subsequent syncs will run using the faster delta method.

> ℹ️ The initial implementation of **Delta Sync** applies to **all users within the tenant**. As a result, adopting this method will increase the total number of users synchronised compared to the **Teams Voice** or **Teams Only** sync options. A future release will introduce the ability to **exclude users before processing** (for example, to remove non–Teams Voice users). Once this capability is available, the **Teams Voice** and **Teams Only** sync options will be retired.

More details on the Sync can be found [here](https://callroute.atlassian.net/wiki/spaces/CKB/pages/761757699)


### Auto Provision based on Entra Groups membership - Initial workaround 

The Auto Provisioning feature allows admins to define rules for provisioning users based on Entra attributes (e.g., *job title contains “manager”*) or on membership in specific Microsoft 365 groups.

Previously, Microsoft’s sync process limited results to the first **20 group memberships** for each user. If the group targeted by an Auto Provisioning rule fell outside that set, affected users could be skipped during provisioning.

This release introduces a **workaround**: *Sync by Entra Group* now retrieves all memberships for the groups targeted by the sync. This ensures that if an Auto Provisioning rule is based on a group targeted in the sync, all eligible users will be correctly provisioned.

Because Entra Group sync does not leverage delta sync efficiency, a **future release** will enhance delta sync to check for any active Auto Provisioning rules that target specific groups, and automatically sync those groups as part of the delta process. This will allow delta sync to be used as the default method, without missing any group-based provisioning rules.

![Screenshot 2025-09-13 at 10.03.21.png](media://b2f93cfd-51d8-4036-9bae-eb1d4eac7be2)


### Auto Provisioning and Microsoft sync flow

We’ve improved how Callroute’s Microsoft 365 sync interacts with the Auto Provisioning (AP) process.

Previously, if AP was enabled, it would begin firing **during** the user sync. For large tenants, this could trigger provisioning while the sync was still running, creating excessive concurrent read/write operations to Microsoft and risking overload.

Now, the sync process must **complete in full** before AP is launched, ensuring stability and reliability. In addition, AP can now be **run independently of a user sync**, using data already held within Callroute. The only caveat is that the tenant must have been synced within the last **24 hours** to ensure data accuracy.

When combined with the new **delta sync** capability, this results in a much more efficient and controlled sync and provisioning flow, particularly for large-scale environments and migrations.

![Screenshot 2025-09-12 at 13.34.02.png](media://17677fe7-318b-42c4-a614-9784fcb3de46)


### New scopes for roles based access

To provide more granular control over Callroute admin permissions, the following new scopes have been added:

| Scope | Description |
| --- | --- |
| **Number Assign** | Allows an admin to assign a phone number to a user or service. |
| **Persona Assign** | Allows an admin to assign a persona to a user. Also enables bulk migration from one persona to another. |
| **User Synchronise – All Modes** | Grants the ability to initiate any type of sync with the connected Microsoft tenant. |
| **User Synchronise – Entra ID Groups Mode** | Grants the ability to initiate a sync for Entra ID groups only. |
| **User Synchronise – Identities Mode** | Grants the ability to sync individual users and import missing users. |
| **User Synchronise – Teams Only Mode** | Grants the ability to initiate a sync targeting Microsoft Teams users only. |
| **User Synchronise – Voice Only Mode** | Grants the ability to initiate a sync targeting Teams Voice users only. |

These new scopes give organisations finer control over what actions different administrators can perform, helping to improve security and delegate responsibility more effectively.

> 📝 Any existing admin user with the **Services: create and edit permission **will be automatically granted the above scopes. Removing the above scopes to leave only **Services: create and edit permission** will result in a reduced permission set (Configure a service, edit service metadata and create service assets eg license groups)