Teams Phone Fall 2026 Changes: What Telephony Admins Must Do

Why do routine Teams Phone updates deserve a plan? Because each one touches a different part of your voice environment, and few organizations have a single owner for all of them.

• Metered AI changes the cost model. Teams Phone Agent requires Teams Phone, a resource account and a spending policy, and it is charged by usage. That is a different financial model from per-user licensing. Without a spending policy and monitoring, call volume spikes translate directly into cost.
• Scripts can break quietly. The roundup reports that the calls-waiting count disappears from the Get-CsCallQueue cmdlet output in mid-October. Any reporting or wallboard script that parses that field may fail or show blanks.
• User experience can shift overnight. When Teams Phone Mobile calls default to the native dialer, users who expect incoming calls in Teams may think the service is broken. Administrators can keep Teams as the default through the MobileDialerPreference setting in the Teams mobility policy, but someone has to decide and communicate it.
• Similar names create confusion. The retiring ACS Direct Routing is an Azure service. The roundup lists Teams Phone and Teams Phone extensibility among the services that are not affected. Even so, organizations that use SBC-based routing should confirm exactly which service their numbers and applications depend on, rather than assuming.
• Calls are only as good as the network under them. Voice quality in Teams depends on bandwidth, latency, jitter and the PSTN connectivity behind it. Software changes do not fix a congested or single-carrier path.

The common thread is ownership. Telephony touches networking, security, licensing and the business, and these changes land on all of them at once.

How should an enterprise prepare for these Teams Phone changes? Work through the following checklist over the next few weeks:

1. Inventory your PSTN connectivity. Document how each number reaches Teams today: Calling Plans, Direct Routing through your own or a provider's session border controllers, Operator Connect, or another service. Confirm that none of it depends on the retiring ACS Direct Routing or PSTN Direct Offer services, and plan a migration if it does, well before 2028.
2. Audit scripts and reports. Search your automation, wallboards and reporting for Get-CsCallQueue and for anything that reads the calls-waiting value. Test against the new output and use call queue analytics instead where needed.
3. Set a Teams Phone Mobile policy. Decide whether incoming calls should ring in Teams or in the native dialer, set MobileDialerPreference accordingly, and tell users before the change reaches them.
4. Pilot Teams Phone Agent narrowly. Start with one low-risk call queue, create the resource account, set a spending policy and review the usage costs for a full cycle before expanding.
5. Review licensing for delegation. If executives and assistants will use intelligent call delegation, confirm that they hold both Teams Phone and the required Copilot license.
6. Prepare users for security reporting. The roundup notes that user reporting of suspicious messages, calls and meetings, which feeds Defender for Office 365, is on by default from October 25. Brief your security team and tell employees what the new option means.
7. Test the path, not just the app. Measure latency, jitter and packet loss to Microsoft's network, and confirm you have redundant SIP trunking and voice routes so that a carrier problem does not take down your telephony.

Finish with a short pilot group and a rollback plan for each change.

Why do enterprises need to manage Teams Phone actively rather than set it and forget it? Because telephony is where operational detail meets customer experience, and a well-run Teams Phone environment pays back in several ways.

• Fewer surprises. Planning for billing, policy defaults and script changes avoids help-desk spikes and unexpected invoices.
• Controlled AI adoption. A narrow pilot of an AI voice agent, with spending limits and measurable outcomes, shows whether it deflects real call volume before you scale it.
• Better productivity. Longer call history, delegation and consistent mobile behavior help users find and return calls faster, which matters most for sales, support and executive offices.
• Stronger security posture. Giving users a simple way to report suspicious calls and messages helps detect voice and collaboration phishing earlier.
• Resilient voice. Redundant carriers and routes keep calls flowing when one provider has a problem, which protects revenue and customer trust.
• Cleaner architecture. Knowing which PSTN service each number uses avoids a rushed migration when a platform is retired.

For organizations that operate across Latin America, the United States and Europe, consistency matters even more. Numbering rules, carriers and regulations differ by country, and a design that works in one market needs to be adapted, not copied, in the next.

HIT Communications has more than 30 years of experience building and operating enterprise voice and data networks across Latin America, the United States and Europe, and Microsoft Teams telephony is one of the areas where we help clients most often.

With our Microsoft Teams Direct Routing and cloud telephony services, we connect Teams Phone to the public telephone network through carrier-grade SIP connectivity, with the number portability, local coverage and monitoring that multinational organizations need. We help you design and document routing so that you always know which services your numbers depend on.

If your organization runs queues, receptions or service desks, our cloud PBX and call center solutions can complement Teams with the queue management, reporting and integrations that contact teams require. And because voice quality starts with the network, we can pair telephony with redundant, multi-carrier connectivity.

If you want a second opinion on your Teams Phone readiness, we can review your call flows, licensing and PSTN architecture and give you a prioritized action list.

Teams Phone is changing quickly. A usage-billed AI agent, a longer call history, new delegation features, native-dialer defaults for mobile calls and the retirement of ACS Direct Routing all arrive within a few weeks of one another. None of them is dramatic on its own, but together they can disrupt a voice environment that nobody is actively managing.

The practical response is simple: inventory your PSTN connectivity, audit your scripts, set your mobile policy, pilot the AI agent with a spending policy, prepare users for security reporting and test the network path that carries your calls. Verify each date with Microsoft before you commit to a plan.

If you would like expert help preparing your Teams telephony, contact the HIT Communications team and we will help you turn this checklist into a project plan.