Insights

What You Need to Know About Microsoft Teams Licensing Changes Effective September 30

Imagine it’s a crisp October morning, and your team arrives at the office ready to tackle the day. But something’s off. The phones aren’t ringing. Customers aren’t getting through. Panic sets in as you realize that your call queues and IVRs have gone silent. What happened?

You missed a critical Microsoft Teams licensing change that went into effect just days earlier. Here is how to ensure you can enjoy those first days of October without adding extra stress to your plate. 

What Microsoft Is Changing With Teams Licensing 

This isn’t necessarily a change; it is more closely related to tightening the governance around licensing, as Microsoft is enforcing a licensing change to Microsoft Teams that could disrupt call routing and functionality for many organizations. Effective September 30, 2025, bot-initiated PSTN (Public Switched Telephone Network) transfers in Teams will require users to have a Phone System license and be Enterprise Voice enabled. 

Microsoft is also aligning the Microsoft Graph API with this requirement, meaning organizations that use these APIs for automated call routing must take immediate action.

This change may seem technical, but its impact is far-reaching. Organizations using embedded telephony apps that bypassed Microsoft’s licensing model will find themselves facing service disruptions if they do not act now.

Microsoft Teams Licensing Changes Effective September 30th

Microsoft is closing a loophole that previously allowed bot-initiated call transfers within Teams without requiring Phone System licenses. These transfers often supported queue-based systems or automated workflows commonly used in the contact center.

Here’s what’s being enforced as of September 30, 2025:

  • Manual transfers within Teams are still allowed without a Phone System license.
  • Bot-initiated transfers and add participant actions (such as automated conferencing or adding users to a live call) will be blocked for users who don’t have a Phone System license.

This change primarily affects users connected through embedded apps that leveraged this loophole to avoid additional licensing costs. These apps, previously marketed as “Teams-integrated” solutions, will stop working unless licensing is brought into compliance.

What The Microsoft Teams Licensing Changes Mean For Your Organization

As we all know, every configuration is unique to your organization, depending on the integrations and functionality of your platform. Those companies that are at risk of interruption would be those whose Teams experience includes:

  • Embedded telephony apps from providers that bypass licensing
  • Call queues or auto-attendants routing calls via bots
  • AI or automation features initiating transfers on behalf of users

For industries such as healthcare, retail, logistics, finance, or any organization relying on contact centers or IVRs, this could mean:

  • Inbound calls are not reaching their intended recipients
  • Outbound communications failing
  • Poor user experience and operational downtime

In its simplest form, if your team isn’t prepared, your phones might stop ringing, literally for you and the customer calling in. There will be no ring, and therefore no answer to the inbound calls. 

Which Solutions Will Be Impacted By The Microsoft Teams Licensing Changes? 

Some solution providers have already announced they will sunset their Teams-embedded solutions because they cannot support the new licensing model. This includes major players like 8×8 and Vonage. 

RingCentral has been proactive in announcing that they have a compliant embedded solution that will not be affected by these changes, come September. Amplix helps clients evaluate all viable options to support their unified communications strategies—including, but not limited to, RingCentral. Our focus is on outcomes, not just technology.

What You Should Do Now Regarding Your Microsoft Teams Licensing

  • Audit Your Microsoft Teams Call Flow: If you’re relying on automated or bot-initiated transfers, find out if your users are licensed.
  • Review Applications Using Graph API: Ensure your developers and partners review and update any apps using Microsoft’s transfer and add participant APIs to align with the new enforcement.
  • Identify Your Technology Partners: Know whether your current embedded telephony provider is compliant with Microsoft’s new enforcement.
  • Engage With Amplix: We’ll conduct a no-cost readiness assessment and build a contingency plan to protect your business continuity.

How Amplix Helps You Navigate This Shift

At Amplix, we don’t just sell solutions—we advise, optimize, and future-proof your tech stack. Here’s how we can help in light of the Teams licensing change:

  • Discovery and Assessment: We evaluate your current Teams and telephony integration to identify risk areas.
  • Vendor-Agnostic Roadmapping: Whether you stay with your current provider or explore others, we develop a migration plan that minimizes disruption.
  • License Optimization: We ensure the right Microsoft Phone System licenses are applied to the right users—nothing more, nothing less.
  • Seamless Transition: If a platform shift is needed, we handle project management, vendor coordination, and training.
  • Strategic Cost Management: Our team ensures you avoid unnecessary spend, uncovering ways to reduce OpEx while maintaining voice quality and functionality.

Don’t Wait Until September 30, Act Now With Amplix 

The organizations that plan now will avoid outages and retain control over their communications. Those who don’t may find themselves scrambling to restore essential services.

Let Amplix help you stay ahead of the deadline.

Contact us today to schedule your free Teams Licensing Readiness Assessment.

Share this:

Key Takeaways:

  • Effective September 30, 2025, Microsoft will block bot-initiated PSTN transfers/add-participant actions in Teams unless the user has a Phone System license (manual transfers remain unaffected).

  • Organizations using embedded telephony apps or Graph API workflows to route calls via bots are at risk of service disruption if they don’t bring licensing into compliance.

  • Some vendors are sunsetting Teams-embedded solutions (e.g., 8×8, Vonage), while RingCentral has announced a compliant embedded option.

  • Potential impacts include inbound calls not reaching recipients, failed outbound communications, and degraded CX—especially for contact-center and IVR use cases.

  • Immediate actions: audit call flows, review Graph API usage, verify partner compliance, and consider an Amplix readiness assessment with license optimization and a migration plan if needed.

Share this:

Insights in Your Inbox

Never miss what’s new from Amplix! Subscribe to get notified.

Ready to amplify your technology investment?