The following article presents the release notes for version 10 of ZPM, scheduled for sometime in the first quarter of 2025.
Phone Numbers in Search Results
Search Results now display assigned numbers.
Manage Call Queue Membership
Phone Enabled Teams Users can now easily be added/removed to queues from within the 360 View.
Performance Improvements
We have improved the performance of the 360 View, allowing users to spend less time on loading screens and more time provisioning users for Teams Phone.
Provisionning Teams Users for Shared Calling
About Shared calling
Microsoft Teams Shared Calling reduces costs by allowing a single phone number and calling plan to be shared by a group of users. This is particularly useful for users who do not require a dedicated phone number.
Provisioning Users for Shared Calling involves the following steps which can now be done through ZPM
- Assigning Teams Phone licenses (existing behaviour)
- Enabling Voice and Assigning the User to a Shared Calling Policy
About Shared Calling Plans - Shared Calling is only available with Microsoft Pay-As-You-Go Teams Calling Plans and participating third-party operator plans.
Provisioning Shared Calling through ZPM
When assigning a number through the 360 view, selecting a Dial Plan configured for Shared Calling will now display the number the user will share, along with the assigned policy and associated Resource Account.
Administrators can configure a Dial Plan for Shared Calling by “Shared Calling” as the Calling Type and choose a shared calling policy instead of specifying a range of numbers.
Note: Teams Admin Center is still required to create the Shared Calling Policy and associated Resource Account.
Live Write Down of Teams Phone to Active-Directory
Thanks
to our valued customers who helped us refine this feature with its pre-release; we proudly announce that it is now Generally Available (GA).
to our valued customers who helped us refine this feature with its pre-release; we proudly announce that it is now Generally Available (GA).Teams Phone to AD Write-Down - How it Works
Organizations often need to update their on-premise Active Directory (AD) with the assigned numbers in Teams for various scenarios. This is important to ensure that Session Border Controllers (SBCs) can route calls correctly based on Active Directory information and to enable auto-attendants to dial by extension accurately.
By leveraging the ZPM Proxy (ZPM Proxy - How it works & Use Cases), administrators can now enable ZPM to update AD in real-time when assigning phone numbers to Teams Users.
AD attributes are assigned Dynamically based on the user’s assigned number and the dial plan configuration. Similar to voice policies, feedback is provided to the helpdesk when the value in AD does not match what was is defined in Microsoft Teams
How to enable Teams Phone to AD Write-Down
For a more comprehensive setup guide, see ZPM Proxy - How to Configure On-Premise AD (LDAP) Write-Down.
Administrators can enable the feature and then specify the fields they want to write to along with their corresponding values with wildcards to populate the user’s DID and/or Extension dynamically.
View Numbers across CUCM and Microsoft Teams
Thanks
CUCM and Microsoft Teams Dial Plan - How it Works
By leveraging the ZPM Proxy (ZPM Proxy - How it works & Use Cases), customers with Direct Routing between Cisco CUCM and Teams can now view assigned numbers in real-time across both environments.
This is incredibly valuable for customers who share a dial plan between both Microsoft Teams Phone and CUCM with the use of route patterns to route to teams when the number is not assigned in CUCM while ensuring no two people share the same number.
How to enable CUCM and Microsoft Teams Dial Plan
For a more comprehensive setup guide, see ZPM Proxy - How to Configure CUCM and Teams Synced Dial Plan Groups.
When enabling the proxy feature, administrators can also match based on exact match or numbers ending in a specified amount of digits for CUCM environments that are not on an e164 dial plan and where shorthand dial is still in place with translation patterns.
(ex. Directory number 36555 would show +1-5149-403-555 as assigned and block the helpdesk from assigning it to a Teams User)
Other Enhancements
- Enhanced Audit log JSON Structure for Unordered Lists
- Enhanced Ability to Bulk Generate Ranges in Dial Plan & Dial Plan Exception Management Pages
- Changes to ZIRO DRaaS and ZIRO DRaaS BYOC Dial Plan Groups To Make Clear What Settings require ZIRO Support ticket to modify
- Added link to https://learn.goziro.com/release-notes/ to the ZPM Release Notes Modal
- API - Added Ability to handle undocumented SKUs from Microsoft
- API - Added Support to Zero-Touch Provisioning for Provisioning Security Group membership and return Assigned Phone Number
- API - Simplified ITSM Endpoint for End-user Provisioning
- API - Added Dial Plan Group Name as a Tag to the Teams Line Audit Entry
- API - Added Ability for the bulk job to validate user account status
Fixed Bugs
- REST Logs Not Formatted Correctly
- Billing Report Page Crashes when the past run fails
- Bulk Provisioning Page Crashes When CSV Contains non-UPN User Targets
- Datatable is truncating cell values too aggressively
- The last run time of reports is not recorded if the last run was an error
- API calls that get audited fail when using OAuth API tokens
- Loading 360 view of users associated to ATA and 3rd Party devices Causes Errors on the 360 View
- Dial Plan Group Creation Toast Does Not Include Name of Dial Plan Group
- Emergency Call Routing Policy is not disabled for Microsoft Calling Plans
- Automation Jobs do not ignore unlicensed Teams Phone Users Causing Failures to Spam the Audits
- Search by FirstName Lastname doesn’t return users when the displayname is “LastName, Firstname”
- Powershell clients are poisoned by
This parameter set requires WSMan…error - Bulk Provisioning, Zero Touch & Reporting Pages Route to System Health Status page when there’s a system health warning