Microsoft Teams Phone in Large Enterprise with Alistair Pidd

Prefer audio?

Who should listen: Microsoft 365 service owners, enterprise voice architects and UC partners running Teams Phone at thousands-of-seats scale, particularly those handling direct routing, SBC estates and handset migrations.

Guest: Alistair Pidd — Professional Services Director, Pure IP

Alistair Pidd, Professional Services Director at Pure IP, leads the teams that configure Teams, deploy SBCs on site and run enterprise voice projects. He and Tom Arbuthnot look at where Teams Phone has got to in large enterprises, the operational burden of Microsoft's pace of change, how internal responsibilities are splitting, and the growing pull towards managed SBCs and automation.

Many thanks to Pure IP, sponsor of this episode.

Key insights

• Teams Phone has reached feature parity with legacy PBXs for what enterprises actually need — Pidd puts it at 90-95% of most requirements. Features such as hunt groups and pickup groups that were once deal-breakers have simply fallen away in practice. ▶ 2:02
• SIP Gateway has shifted from a transitional bridge to a core part of the service: DECT support, intercom and paging, ATAs, and recently PowerShell for managing devices at scale. ▶ 4:07
• The 3PIP retirement caught organisations out because the old management systems for large handset estates had no immediate Teams equivalent, forcing a choice between migrating the legacy estate to SIP Gateway, refreshing hardware, or shrinking the estate — and 24 months' notice felt like plenty until it wasn't. ▶ 4:37
• Individually small 2023 changes — SBC certificates, 3PIP to SIP Gateway, extension attributes, number normalisation — each needed unpicking at scale, so planning and change authorisation dominated the effort, not the change itself. ▶ 6:09
• Desk phones are no longer a phone team problem: Android handsets pull in onboarding, conditional access, Intune and identity management teams, so rolling out a phone can involve several teams and a proxy/VLAN rethink versus the old Cisco model. ▶ 8:11
• Team structures are amalgamating — network and voice, or applications and voice with voice treated as an application — and almost always the meeting room estate collapses into the same team, having previously sat with facilities who often chose devices without knowing the platform decision. ▶ 9:43
• End-to-end joiner automation still stalls at Teams Phone: identity, SharePoint and Exchange provision automatically, but number assignment rarely does. Group policy assignment and API-driven provisioning are pushing this work towards developers rather than voice teams. ▶ 11:15
• Operator Connect simplifies telephony and is easier to automate, but global single-platform requirements still need direct routing — hence rising demand for managed SBCs, where the partner absorbs certificate changes, attribute changes, patching and security monitoring at the network edge. ▶ 13:17
• The biggest remaining gap is reporting: enterprises running informal call queues for support desks want near-real-time and historic visibility, graphed and dashboarded, including wait times, beyond what Teams Admin Center provides. ▶ 15:52

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

Listen: Apple Podcasts · Spotify · Other platforms