Multi-Tenant Support
You can now manage multiple Microsoft tenants from the ZIRO platform, eliminating the need to navigate between different ZIRO platform instances.
Helpdesk Users can be restricted to dial plans on a single or multiple tenants. When access to multiple tenants is granted to the user, a drop down will allow them to select which tenant they’d like to work on.
Administrators can add additional Microsoft tenants by adding additional app registration in the administration page and then configure tenant-specific settings (ex., Dial Plans, Licenses or Security Groups to show or hide).
Known Limitation when adding Multiple Microsoft Tenants:
Multi-Tenant Management is not supported for the following use cases:
- On-Premises Connectivity - Environments requiring on-premises connection with proxy should only point to a single Microsoft Tenant.
- ZIRO DRaaS - Direct Routing as a Service from ZIRO requires a dedicated ZPM pointing to a single Microsoft Tenant.
- Dubber Compliance Recording - Customers requiring provisioning of Dubber Compliance Recording through ZIRO can only point their ZPM to a single Microsoft Tenant.
- Max 20 tenants / 100K endpoints - A single instance of the platform can manage up to 20 instances or a total of 100K endpoints (users, shared devices, resource accounts)
- SAML SSO - Multi-Tenanncy must use OIDC. SAML is only supported for a ZPM on a single tenant.
Improved Insights on the Global Dial Plan Inventory Report
This update to the Dial Plan Inventory Report provides more comprehensive information about the numbers in your dial plan.
Enhanced Visibility for Unavailable Numbers
The ZIRO Platform now takes into account additional scenarios that render a number that is unavailable for assignment:
- Extensions are now considered by the report (previously only supported E.164 numbers)
- Numbers that are part of ZP Dial Plan Exception Groups.
- Numbers configured as Unassigned Number Routing Rules in Microsoft Teams.
- Numbers included in hybrid dial plan groups that span both Teams and Cisco will now be marked as unavailable if they are assigned on the Cisco PBX.
A Richer Excel Export of your Dial Plan
The Excel export now includes much more detailed information about your numbers, such as:
- The ZP Dial Plan Exception Group they belong to.
- The Unassigned Number Routing Rule associated with them.
- The Microsoft Teams Usage Types linked to them.
- The date on which previously assigned available numbers were released.
Move CUCM Numbers to the most cost-effective product in Microsoft Teams Phone
As companies transition their phone systems from CUCM to Microsoft Teams Phone, it’s an excellent opportunity to evaluate their users’ calling habits. This helps ensure that the most cost-effective phone solutions are assigned to employees.
Moving to Microsoft Teams often provides significant savings, particularly for low-usage users who can be transitioned to Microsoft Shared Calling.
Migrations through ZIRO now provide insights into your CUCM Directory Number usage, enabling you to identify the most cost-effective Teams Calling Solution for each user or shared device/public phone.
How do the suggestions work
ZIRO Platform interprets a provided CUCM config export (.tar) and Call Detail Record (CDR) dump to suggest a Calling Product—Shared Calling, Per-Minute Plan, or Bundled Minute Plan—based on monthly incoming calls and outgoing minutes.
Administrators can customize their own thresholds to tailor the logic behind these recommendations. For more details on how the recommendations are calulated based on the provided thresholds, see Calling Product Thresholds
Moving Cisco To Microsoft Teams - Auto Attendant Analyzer
Migrating from Cisco Unity to Microsoft Teams often means untangling a web of call handlers, transfer rules, and schedules—usually buried deep in complex admin menus. Without a clear view, mapping Unity’s call flows into Teams call queues can be error-prone, time-consuming, and frustrating.
With ZIRO Platform’s new Cisco Auto-Attendant Viewer, you can see your entire configuration in one clean layout—sources, transfer rules, destinations, and full schedules, including holidays. Whether it’s business hours routing, off-hours greetings, or specific button actions, you can get a clear, accurate picture of how callers move through your system while browsing your entire Auto-Attendant call tree in real-time. This eliminates guesswork, reduces migration errors, and speeds up your transition to Microsoft Teams.
Other Enhancements
-
Enforce Escaped HTML in innerHTML attributes to prevent HTML injection
-
Enhanced Call Queues API to include richer information (userPrincipalName, UUID, lineUri, extension, and displayName)
-
Ability to display user Display Names in Policy Misconfiguration Report
-
API - New Multi-Tenant License Usage Report
Fixed Bugs
-
Wrong number shown in delete confirmation modal after failure
-
Large custom PowerShell reports can cause the application to crash when logging or pretty printing large JSON responses Constant unnecessary polling of status on Billing Subscriptions and Bulk page
-
Re-using a Deleted Bulk Jobs Name Gives a Bulk job name already in use Error
-
Matching algorithm for User Lines is a bit too loose on the Directory Number Report
-
Bottom Nav Button Tooltip Shown When Tenant Is Configured
-
Text Inputs Not Stripping Leading+Trailing Spaces
-
Broken Audit Logs’ side-by-side view
-
Storing Duplicate Call Records
-
Call Records Database Resiliency Problem
-
Security groups are not stored in the same order they are entered in the settings
-
Login page malfunctions after 30 seconds when Recovery URL is clicked
-
Directory Number Report File Progress Modal Not Aligned
-
Health Status Category for Microsoft Graph API is confusing
-
DN Ranges Alignment & Spacing Issue
-
Reusing a deleted bulk job’s name results in a “bulk job name already in use” error
-
The delete button in the edit bulk job view is not re-enabled after the job is completed
-
DataTable action buttons have no background unless scrolled.
-
ZP returns an error when Bandwidth DLR creation takes too long
-
Re-uploading File Fails on Migrations Page
-
Unchecking the Dial Plan Group filter item on the Policy Misconfiguration Report table does not restore the original number of rows in the table.
-
userPrincipalName validation endpoint is case sensitive
-
Tech Support Page Uses Outdated Styling
-
Incorrectly polling status in Billing Subscriptions and Bulk Jobs pages
-
Toast for missing Roles is Unclear
-
Search bar is displayed in the Reports and Automations modules
-
“To Teams - User” Input has Invalid Character Limit
-
Prepended text can be rendered unsafely
-
RoleManagement.Read.DirectoryandGroupMember.Read.Allroles are no longer required -
Success Toast does not appear after running a job on the Zero-Touch Provisioning page
-
The 365 Licenses tile displays as “In Progress” indefinitely when a group-based license with no remaining licenses is assigned to a user.