Dear readers, I have an important update to share regarding PSTN (Public Switched Telephone Network) bot calls in Microsoft Teams. Starting in June 2025, Microsoft will enforce licensing controls for bot-initiated call transfers to Teams users. This measure aims to align Teams Phone functionality with current licensing requirements and ensure compliant use of telephony services.
What’s Changing?
Currently, there is a gap in the system that allows bots, such as an Auto Attendant, to transfer calls to Teams users without checking whether these users have a phone system license. From June 2025, this gap will be closed. Call transfers initiated by bots and requests to add participants to users without phone system authorization will be blocked.
Impact on Users
Teams users will still be able to manually transfer calls to other Teams users, even if they don’t have a phone system license. However, applications that use the transfer and add participant APIs will need to be updated to reflect this new default behavior. If you currently rely on the absence of license controls, it’s crucial to inform your customers of this change to avoid any service disruption.
Recommended actions
To prepare for this update, we recommend that you :
- Review and update your applications: Ensure that all applications using the transfer and add participant APIs comply with the new licensing requirements.
- Inform your customers: Communicate with your customers to inform them of this change and its potential impact on their services.
- Test changes: Carry out in-depth tests to ensure that your applications work properly with the new license controls in place.
Conclusion
This update is an important step in guaranteeing compliant and secure use of telephony services in Microsoft Teams. By taking the necessary steps now, you can ensure a smooth transition and avoid any service disruption for your users. Below you’ll find a note mentioned in Learn about setting up Auto Attendants.
Source
For more details, see the full article on the Microsoft 365 developer blog below: