Release 10.6 of ZIRO Platform is planned for General Availability April 2026
Teams Calling PSTN Usage – Suggested Calling Product Insights
For a detailed explanation on how calculations are performed and limitations, please see Teams PSTN Call Usage Report
Ziro Platform has enhanced the Teams Calling PSTN Usage Report to provide deeper insights into user calling habits and to recommend an appropriate Calling Product for each user.
This report consumes Microsoft Teams Call Detail Records (CDRs) to analyze user calling patterns and provide actionable recommendations on the most suitable calling product.
Based on historical usage, the report evaluates whether a user would benefit from one of the following calling options:
- Shared Calling – Ideal for users with very low PSTN usage, including minimal incoming calls and low outgoing minute consumption, who can share a pool of minutes.
- Per-Minute Calling – Best suited for users with a low volume of outbound PSTN minutes but a higher level of incoming calls.
- Bundled Minutes – Recommended for users with consistent or high outbound PSTN minutes usage who would benefit from a fixed monthly allocation of minutes.
By identifying users who may be over-licensed or under-licensed, the PSTN Utilization Report helps administrators:
-
Reduce unnecessary telephony costs
-
Ensure users have the most appropriate calling plan
-
Make data-driven licensing decisions
This feature provides clear upgrade and downgrade insights, enabling organizations to continuously optimize their Teams calling environment based on real user usage patterns.
PSTN Call Record Finder
For information on how Call Record Logs are Collected and Stored, see PSTN Call Records - How it Works & Use Cases
Ziro Platform has introduced the PSTN Call Record Finder, a new report designed to provide detailed visibility into Teams PSTN call activity and enable advanced call record searches.
While the Teams Calling PSTN Usage Report provides aggregated metrics such as total calls and minutes used, many organizations require deeper insights into individual call records for auditing and usage analysis. The PSTN Record Finder addresses these needs by allowing administrators to search and analyze detailed PSTN call records across their environment.
With the PSTN Record Finder, administrators can:
-
Search CDRs for specific users (by UPN or Display Name), phone numbers, or time ranges
-
Investigate whether specific users communicated with particular numbers or individuals
The report includes a flexible expression-based search interface, allowing administrators to build queries and quickly locate relevant call records.
By enabling long-term storage and searchable PSTN call data, the PSTN Call Record Finder provides administrators with the visibility required for compliance, cost analysis, and operational insights within their Teams calling environment.
Reduced Permission Requirements for Groups and Teams Roles
Ziro Platform has reduced the permission requirements needed to use group and Teams voice management features, helping organizations better follow least-privilege security practices.
Previously, the platform required elevated permissions, such as the Teams Administrator role and the GroupMember.ReadWrite.All Graph permission for managing user group membership. These permissions were broader than necessary for the functionality provided and could potentially allow access to groups or resources outside the intended scope.
With this update:
-
Teams Communications Administrator is now sufficient for all Teams voice–related functionality
-
A new, more secure option for user group management allows administrators to manage groups based on group ownership rather than broad directory-wide permissions
This new group management model is optional. Organizations can continue using the existing permission model or choose to adopt the new ownership-based approach for improved security.
For details on how to implement the new group permissions, please see Grant ZIRO Platform access to specific security group membership via Ownership in Entra
These changes reduce the overall permission footprint of the application while maintaining flexibility, making it easier for organizations to deploy the platform in environments with strict security and compliance requirements.
Emergency Location Management
In Teams, Emergency Locations and network topology determine the address sent to first responders during a 911 call—making them critical for compliance with Kari’s Law and Ray Baum’s Act.
With our introduction of Emergency Location Management is is now simpler than ever to:
- Create and manage Emergency Locations
- Map locations to network topology (subnets, switches, Wi-Fi)
- Keep location data accurate as networks change
The result: simpler compliance, safer emergency calling, and less administrative overhead.
ZIRO Administrator Role Required
Currently, only Administrators can create & manage Emergency Locations. In a future release, Role-Based Access Control will let administrators choose who can modify emergency locations.
CUCM Migration – Migration Status Tracking
We’ve enhanced the CUCM Migration Directory Number Report to provide better visibility into the progress of Teams migration projects.
The Directory Number Report now includes migration status tracking, allowing administrators to easily categorize numbers as Migrated, Ready, Not Ready, Staged, or Ignored. This makes it much easier to understand the current state of a migration and identify which users still require action.
A new dashboard widget also provides a high-level overview of overall migration progress. Additionally, administrators can mark numbers as ignored to exclude numbers that do not need to be migrated.
These enhancements help migration teams easily track progress and manage CUCM to Teams migrations at scale.
Other Enhacements
- Ability to copy values on hover from search results
Fixed Bugs
-
Users & Group Permissions page wouldn’t load when there is no tenants configured
-
Fixed an issue where the Migrate DN report export to excel would inject commas into the External Mask when not needed
-
Fixed an issue where searching for Teams users on the Call Queue page would timeout
-
Fixed an issue where the PSTN Usage Report would attribute failed calls to a user
-
Fixed an issue where the UI would allow deleting a number from an active resource account
-
Fixed an issue where the Zero Touch Provisioning jobs would run when the numbers api is unavailable