Migrating to Teams Phone Real-World Experience & Dealing with the Pace of Microsoft 365 Change

Prefer audio?

Who should listen: Microsoft 365 service owners, Teams Phone project leads and UC operations teams planning a legacy PBX migration or trying to build a repeatable process for handling Message Center change.

Guest: Damian Lewis — Digital Workplace Specialist (Teams system owner - telephony, Teams Rooms), Global enterprise (undisclosed)

Damian Lewis is a digital workplace specialist at a global enterprise where he owns Teams telephony, Microsoft Teams Rooms and the weekly Message Center review board. He shares hard-won lessons from migrating legacy telephony to Teams Phone across regions, the realities of number porting and operator differences, and the process his team built to triage Microsoft 365 change and communicate it to users.

Many thanks to Numonix, sponsor of this episode.

Key insights

• Number porting, not feature parity, was the single biggest source of project friction. Confirmed port windows sometimes collapsed to 30 minutes' notice, and on one cutover only 4 of the 30-40 expected numbers actually moved, forcing an immediate corrective comms to users. ▶ 3:03
• Reseller chains break porting: one US port dragged on for two and a half to three months because nobody could identify the owning address or authorised account name behind a reseller. Capture account holder details early, and expect ex-employee names on old contracts to be a blocker. ▶ 4:05
• Operator commercial models differ materially. The Americas operator charged roughly $8 per number per month for numbers held in Teams versus 99 cents for numbers parked in the operator's own management console, prompting a bulk exercise to pull ~200-300 unassigned numbers back out of Teams. The EMEA operator charged a flat rate regardless. ▶ 7:12
• Operator Connect provisioning speed varies wildly between suppliers - new numbers in the US arrived within hours, while the European supplier quoted four weeks because of internal ordering, billing and deployment handoffs. Numbers can appear in Teams and still be unusable until the operator releases them. ▶ 9:15
• Teams Phone simplified rather than limited use cases: an Ireland office process that required manual portal logins and an hour of replication to divert numbers for planned leave was replaced with holiday schedules routing to the UK number in minutes. ▶ 11:21
• Ownership of telephony is unresolved in most orgs - it historically sat with the network team but as a cloud feature of Teams it needs clear lines of engagement with the collaboration/digital workplace team, otherwise user requests get bounced between teams. ▶ 14:55
• A weekly Tuesday Message Center review board covering 15-25 key messages, staffed by operations, security, Intune and digital workplace specialists, ensures each change is triaged, assigned to a named owner in Planner and either actioned or dropped. ▶ 18:26
• A utility account pulls new Message Center posts into a Planner bucket at 2am daily so nothing is missed; anything user-facing becomes a Wednesday 'did you know?' post on Yammer. Without this, features like Forms response editing can sit unused for years after release. ▶ 20:59
• Treat Microsoft's stated rollout dates as optimistic - the published date reflects the very first tenant, and Damian reckons a message flagged for mid-May typically lands nearer July, often with a 'based on user feedback' extension. ▶ 27:05

Insights summarised by AI from the episode transcript, reviewed by the Empowering.Cloud team.

Listen: Apple Podcasts · Spotify · Other platforms