Microsoft Teams

Modernize Communications
Workshop
Moving to Microsoft Teams Phone
Speaker name and date here
Agenda Migration strategies to move users from PBX to Microsoft Teams Phone

User experience moving to Microsoft Teams Phone

Administrator experience moving to Microsoft Teams Phone

Business experience moving to Microsoft Teams Phone

Questions and answers

Migration strategies
Microsoft Teams Phone is more than a technical migration

Change doesn’t Shadow IT People and Technical readiness

automagically is more prominent change are not and user adoption
happen than ever one-size-fits-all go hand in hand

Resistance is a 80% admit to Organizations are Plan, pilot, and

normal, using their made up of early deploy both
adopting to communication adopters, laggards, readiness activities
change takes tool of choice1 and everyone in together
time between

1
“What is Shadow IT?”, https://www.skyhighnetworks.com/cloud-security-university/what-is-shadow-it/ (accessed March 2017)
How to accelerate the
move today

Determine the migration strategy

Turn on Microsoft Teams Phone
(licensing, Teams Calling
Plans/Operator Connect)
Get champions going right away
Demystify call control and delegation
Allow calling between systems with
PSTN, Direct Routing, or both
Which migration path should customers take?
Microsoft offers flexibility for customers to choose their upgrade path on the road to
Microsoft Teams only

Path A Path B
Co-existence migration Cutover migration
Overlapping capabilities Replacement of solutions
Modular and agile process Coordinated move of services

Considerations:
Set up Direct Routing for PBX and Microsoft Teams Phone
to function side by side
Voice capabilities available in both PBX and Microsoft
Teams Phone
Enables controlled velocity move to Microsoft Teams Phone
Considerations:
More complex environments are nearly impossible to
immediately replace all services
Creates more points of no return during the project
Project timeline is significantly shorter
Path A

Co-existence migration

Overlapping capabilities, considerations, and impact

Feature requirements Moving users one at a Additional

and overlap time or in groups considerations

Calling features available in both PBX and Granular control: Migration experience can be Proof of Concept testing of solution to ensure the
Microsoft Teams Phone controlled on a per user or per group basis separate systems will function as expected

Requires setup of Direct Routing as well as Individuals: Champions and super users can be Setup dial plans to allow for individual numbers to
Microsoft Teams Calling Plans or Operator early adopters leading to greater exposure and be routed to specific destinations - requires more
Connect building excitement around the solution administration during migration

Dial Plan planning is critical
Allows both solutions access to most of the
other systems resources
Groups: Organizational groups can be moved
together for a shared experience
Plan which non-user devices will move during
which stages. For example, common area phones,
analog devices, and integrated solutions
Emergency calling needs to be fully functional in
both systems
Path A

Co-existence migration with overlapping capabilities method

Introduce Microsoft Teams Phone side-by-side with a traditional PBX

Drive your adoption program with features and abilities

Teams Phone PSTN Call controls Auto attendant Conferencing Call center Modern calling API integration
Path B
Cutover migration
Overlapping capabilities, considerations, and impact
Feature requirements
and overlap
Calling features available in the system of
choice until the decided cutover time
Fastest method of moving users to
Microsoft Teams Phone
Requires all users be moved at one time
May create points of no return where the
ability to back out of the change is not
feasible, such as porting telephone
numbers or removing and replacing
telephones.
Moving users on a PBX
all at once
Quick velocity: All users have the same capability
and experience at once which simplifies adoption
Site level move: May be able to move high-level
sites at a single time rather than entire PBX. This
depends on the setup of carrier services and PBX
configuration.
Shorter runway: Allows for an organization to
focus intense effort on moving users quickly to
Microsoft Teams Phone.
Additional
considerations
Adoption and change management is crucial for
user acceptance of new solution.
Extensive testing in proof of concept will avoid
many issues found during cutover.
Full discovery of non-user devices will ensure that
no services are missed during cutover.
User experience
 Microsoft Teams Phone user experience
Teams to Teams calling
Federation and Skype calling
Primary telephony service
PSTN calling
Local extension dialing
PBX Contact centers
Analog devices
Integrated solutions
Phase 1
Microsoft Teams only mode
without calling features
Teams Calling Plans and/or Extension dialing to resources Primary telephony service
Operator Connect remaining on PBX
PSTN calling
Call queue Analog stations
Local Extension dialing
Auto attendant Local PSTN services are made
Contact Centers
available for Microsoft Teams
Delegation
Analog devices
Digital and analog integrations into
Call controls
legacy systems Integrated solutions
Dial plan
Calling policies
Emergency calling
Telephony service for select number
of users
Teams
Separate systems able to
communicate via PSTN
network only
Legacy telephony service
during migration
Legacy integrations unable to
migrate
Digital and analog stations during
migration to Microsoft Teams
Phase 2 Phase 3 Phase 4
Microsoft Teams Phone with Microsoft Teams Phone with Microsoft Teams Phone
Calling Plans and/or Operator Calling Plans and/or Operator
Connect Connect with Direct Routing
Microsoft Teams Phone
feature transition
From (PBX) To (Teams Phone)
Bridged call/Shared lines Delegate feature

Call park Call park

Call pickup Group call pickup

Caller-ID Caller-ID policies

Cover path Call answering rules

Cover answer group Call queues

Directory Active Directory lookup

Distinctive ring Ringtones

Single number reach Call answering rules

Extend call Call transfer to cell

Forward Call forward settings

Group page Group chat

History Call history

Hold Hold

Intercom Teams calling and chat

Posted messages Status feed

Send calls (to voicemail) Status to do not disturb

Transfer (announced) Consultative transfer

Transfer (blind) Call transfer

Administrator experience
 Microsoft Teams Phone administrator experience
Basic Microsoft Teams enablement
Microsoft Teams admin center
defaults
Traditional PBX administration
Digital and analog wiring
Dial plan management
Physical phone inventory and
PBX management
Traditional reporting methods
Carrier services
Phase 1
Teams only mode without
calling features
Dial plan shared between systems
Microsoft Teams devices for calling
inventory and management
Microsoft Teams policies for calling
in Teams admin center
Call Quality Dashboard
Administration of both systems
required
Carrier services working
independent of each other
Calling between systems via PSTN
Legacy call detail reporting
Phase 2
Teams Phone with Teams
Calling Plans and/or Operator
Connect
Dial plan administration Primary telephony service
Microsoft Teams devices move to Teams policies
primary telephony device
Teams devices
Microsoft Teams Phone features
Call Quality Dashboard
replace legacy PBX features
Call analytics
Call queue and auto attendant
replace legacy call routing systems
Call Quality Dashboard and call
analytics
Teams
Legacy integrations unable to
migrate
Digital and analog stations during
migration to Microsoft Teams
Phase 3 Phase 4
Teams Phone with Teams Calling Teams Phone
Plans and/or Operator Connect
with Direct Routing
Business experience
 Microsoft Teams Phone experience
Microsoft Teams deployment
without Teams Phone or Teams
Calling Plans
Chat, P2P, or federated calling and
collaboration only
Primary telephony service
PBX contracts remain
Service provider contracts remain
Existing abilities
PBX
Phase 1
Teams only mode without
calling features
Adding Microsoft Teams Phone
licensing
Adding Microsoft Teams Calling
Plans and/or Operator Connect to
Teams
Equivalent voice abilities
Users, groups, or sites can be
moved
May port telephone numbers
Separate systems able to
communicate via PSTN
network only
Legacy telephony service
during migration
Phase 2
Microsoft Teams Phone with
Teams Calling Plans and/or
Operator Connect
Extension dialing to resources Primary telephony service
remaining on PBX
PSTN calling
Analog stations
Local Extension dialing
Local PSTN services are made
Contact centers
available for Microsoft Teams
Phone Analog devices
Digital and analog integrations into Integrated solutions
legacy systems
Teams
Legacy integrations unable to
migrate
Digital and analog stations during
migration to Microsoft Teams
Phase 3 Phase 4
Microsoft Teams Phone with Microsoft Teams Phone with
Teams Calling Plans, Operator Calling Plans and/or Operator
Connect and/or Direct Routing Connect
Microsoft Teams Phone migration cost over time
Existing telephony equipment

Teams Phone devices and peripherals

Dial-in conference telephony service

Legacy conferencing service Teams meetings audio conference service

PSTN services

Legacy carrier service Legacy and Teams Calling Plans and/or Operator Connect Calling Plans and/or Operator Connect

Teams licensing

Non-calling Teams licenses Teams Phone with Teams Calling Plans and/or Operator Connect

Integrated Solutions i.e.. Contact center, Paging systems, Call out dialers, Analog services

Legacy integrations Legacy integrations and Teams Phone solutions Teams Phone certified solutions

Teams Phone certified integrations 

Teams Calling Plans and/or Operator Connect

Teams without PBX and Teams Phone side-by-side Teams and Direct Teams with
PBX only
calling Routing Teams Phone
Migrating PBX calling to Direct
Routing: High level topology
Migrating PBX calling to Direct Routing: Topology

Telco-provided
connection
• SIP trunk
• PRI line (T1/E1)

SIP trunk/PRI
PSTN
Integrated
solutions

SIP trunk/PRI

Legacy PBX

Phase 1 “Current”
Legacy PBX
Stations and trunks
Integrated solutions
Migrating PBX calling to Direct Routing: Topology

Telco-provided
connection
• SIP trunk
• PRI line (T1/E1)

SIP trunk/PRI
PSTN
Integrated
solutions

SIP trunk/PRI

Session Border Controller

Legacy PBX

Phase 1.5 “Preparing for Microsoft Teams”

Session Border Controller
Allows granular control of PSTN services
Connect multiple integrated systems
Migrating PBX calling to Direct Routing: Topology

Telco-provided
connection
• SIP trunk Internet Teams Phone
• PRI line (T1/E1)

SIP trunk/PRI
PSTN
Integrated
solutions

SIP trunk/PRI

Session Border Controller

Legacy PBX

Phase 2
Teams Phone
working side by side
with legacy systems
Migrating PBX calling to Direct Routing: Topology

Telco-provided
connection Direct Routing
• SIP trunk Internet Teams Phone
• PRI line (T1/E1)

SIP trunk/PRI
PSTN
Integrated
solutions

SIP trunk/PRI

Session Border Controller

Legacy PBX

Phase 3 - Teams Phone with Direct Routing

Direct Routing allows Microsoft Teams Phone to interact with legacy systems for
extension dialing, analog connections, integrated solutions, and other on-prem systems.
Migrating PBX calling to Direct Routing: Topology

Telco-provided
connection Direct Routing
• SIP trunk Internet Teams Phone
• PRI line (T1/E1)

SIP trunk/PRI SIP trunk/PRI

PSTN
Integrated
solutions

SIP trunk/PRI

Session Border Controller

Legacy PBX

Phase 4 - Teams Phone

Teams calling is the primary telephony solution
SBC provides integration with required legacy systems
Local trunks and/or Microsoft Calling Plan may be used
Extension dialing still possible
Analog, paging, custom solutions through SBC
Migrating PBX calling to Direct Routing: Topology

Telco-provided Direct Routing

connection
• SIP trunk Internet Teams Phone
• PRI line (T1/E1)

SIP trunk/PRI
PSTN

Integrated
solutions

Session Border Controller

Migrating PBX calling to
Calling Plans / Operator
Connect: High level topology
Migrating PBX calling to Calling Plans/Operator Connect: Topology

Telco-provided
connection
• SIP trunk
• PRI line (T1/E1)

SIP trunk/PRI
PSTN
Integrated
solutions

SIP trunk/PRI

Legacy PBX

Phase 1 “Current”
Legacy PBX
Stations and trunks
Integrated solutions
Migrating PBX calling to Calling Plans/Operator Connect: Topology

Telco-provided
connection
• SIP trunk
• PRI line (T1/E1)

SIP trunk/PRI
PSTN
Integrated
solutions

SIP trunk/PRI

Legacy PBX

Phase 1.5 - Preparing for Microsoft Teams Phone with Calling Plans / Operator Connect
Planning for Teams Calling Plans / Operator Connect
Get Phone numbers for your users
If you will be re-using the numbers, submit a porting request to your carrier.
Alternatively, you can acquire new numbers directly from Microsoft.
Migration of existing PBX integrated solutions to alternative solutions
Migrating PBX calling to Calling Plans/Operator Connect: Topology

Telco-provided Microsoft-provided
connection PSTN connection PSTN

• SIP trunk Teams Phone

• PRI line (T1/E1)

Internet

SIP trunk/PRI
PSTN
Integrated
solutions

Teams user

SIP trunk/PRI

Legacy PBX

Phase 2
Teams Phone with Calling Plans / Operator Connect working side by side with
legacy systems
Calling between users on legacy system and Teams available via PSTN but call
rates may apply
Migrating PBX calling to Calling Plans/Operator Connect: Topology

Telco-provided Microsoft-provided
connection PSTN connection PSTN

• SIP trunk Teams Phone

• PRI line (T1/E1)

Internet

SIP trunk/PRI
PSTN
Integrated
solutions

Teams user

SIP trunk/PRI

Legacy PBX

Phase 3
Decommission PBX and legacy systems
Migrating PBX calling to Calling Plans/Operator Connect: Topology

Microsoft-provided
PSTN connection PSTN

Teams Phone

Internet

Teams user

Phase 4
Users migrated to Microsoft Teams Phone with Calling
Plans / Operator Connect
Migrating Skype for Business
Enterprise Voice to Direct
Routing: High level topology
Migrating Skype for Business Enterprise Voice calling
to Direct Routing: Topology
Telco-provided
connection
• SIP trunk
• PRI line (T1/E1)

SIP trunk
/PRI
PSTN
Integrated
solutions

Skype for Business

SIP trunk/PRI Server Enterprise
Voice
Session Border Controller

Phase 1 “Current”
Skype for Business Server Enterprise Voice
Stations and trunks
Integrated solutions: Analog, paging, custom solutions through SBC
Migrating Skype for Business Enterprise Voice calling
to Direct Routing: Topology
Telco-provided
connection
• SIP trunk Internet Teams Phone
• PRI line (T1/E1)

SIP trunk
/PRI
PSTN
Integrated
solutions

Skype for Business

SIP trunk/PRI Server Enterprise
Voice
Session Border Controller

Phase 2
Skype for Business Server Hybrid
Configure tenant for Direct Routing
Teams Phone working side by side with legacy systems
Migrating Skype for Business Enterprise Voice calling
to Direct Routing: Topology
Telco-provided Direct Routing
connection
• SIP trunk Internet Teams Phone
• PRI line (T1/E1)

SIP trunk
/PRI
PSTN
Integrated
solutions

Skype for Business

SIP trunk/PRI Server Enterprise
Voice
Session Border Controller

Phase 3 – Microsoft Teams Phone with Direct Routing

Direct Routing allows Teams Phone to interact with legacy Skype for Business Enterprise Voice users for
Extension dialing, analog connections, integrated solutions and other on-prem systems
Migrating Skype for Business Enterprise Voice calling
to Direct Routing: Topology
Telco-provided Direct Routing
connection
• SIP trunk Internet Teams Phone
• PRI line (T1/E1)

SIP trunk
/PRI
PSTN
Integrated
solutions

Skype for Business

SIP trunk/PRI Server Enterprise
Voice
Session Border Controller

Phase 4 – Microsoft Teams Phone with Direct Routing

Teams Phone Direct Routing is the primary telephony solution
SBC provides integration with required Skype for Business Enterprise Voice users
Local trunks and/or Teams Calling Plans/Operator Connect may be used
Extension dialing still possible
Migrating Skype for Business Enterprise Voice calling
to Direct Routing: Topology
Telco-provided Direct Routing
connection
• SIP trunk Internet Teams Phone
• PRI line (T1/E1)

SIP trunk
/PRI
PSTN
Integrated
solutions

Skype for Business

SIP trunk/PRI Server Enterprise
Voice
Session Border Controller

Phase 5
Decommission Skype for Business Server
Migrating Skype for Business
Enterprise Voice to Calling
Plans / Operator Connect:
High level topology
Migrating Skype for Business Server Enterprise Voice to Calling
Plans/Operator Connect: Topology
Telco-provided
connection
• SIP trunk
• PRI line (T1/E1)

SIP trunk SIP trunk

/PRI /PRI
PSTN
Integrated
solutions

Skype for Business

SIP trunk/PRI Server Enterprise
Voice
Session Border Controller

Phase 1 “Current”
Skype for Business Server Enterprise Voice
Stations and trunks
Integrated solutions: analog, paging, custom solutions through SBC
Migrating Skype for Business Server Enterprise Voice to Calling
Plans/Operator Connect: Topology
Telco-provided Microsoft-provided
connection PSTN connection PSTN

• SIP trunk Teams Phone

• PRI line (T1/E1)

Internet
SIP trunk
/PRI
PSTN
Integrated
solutions

Teams user
Skype for Business
SIP trunk/PRI Server Enterprise
Voice

Phase 2
Skype for Business Hybrid
Teams Phone with Calling Plans / Operator Connect working side by side with legacy systems
Calling between users on legacy system and Teams available via PSTN, but call rates may apply
Migrating Skype for Business Server Enterprise Voice to Calling
Plans/Operator Connect: Topology
Telco-provided Microsoft-provided
connection PSTN connection PSTN

• SIP trunk Teams Phone

• PRI line (T1/E1)

Internet
SIP trunk
/PRI
PSTN
Integrated
solutions

Teams user
Skype for Business
SIP trunk/PRI Server Enterprise
Voice

Phase 3
Decommission Skype for Business Server
Migrating Skype for Business Server Enterprise Voice to Calling
Plans/Operator Connect: Topology
Microsoft-provided
PSTN connection PSTN

Teams Phone

Internet

Teams user

Phase 4
Users migrated to Microsoft Teams Phone with Calling Plans / Operator Connect
Questions and answers
Thank you.