Teams Direct Routing - SFB to Teams Migration - User Phone Number Synchronization

%3CLINGO-SUB%20id%3D%22lingo-sub-2024195%22%20slang%3D%22en-US%22%3ETeams%20Direct%20Routing%20-%20SFB%20to%20Teams%20Migration%20-%20User%20Phone%20Number%20Synchronization%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2024195%22%20slang%3D%22en-US%22%3E%3CP%3EHi%3C%2FP%3E%3CP%3EI%20am%20currently%20looking%20at%20the%20MS%20Direct%20Routing%20guidelines%20for%20enablement%20of%20users%3A%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fdirect-routing-enable-users%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fdirect-routing-enable-users%3C%2FA%3E%3C%2FP%3E%3CP%3EAs%20part%20of%20this%20article%2C%20there%20is%20a%20sub%20section%20%3CSTRONG%3E%E2%80%9CEnsure%20that%20the%20user%20is%20homed%20online%20and%20phone%20number%20is%20not%20being%20synced%20from%20on-premises%20(applicable%20for%20Skype%20for%20Business%20Server%20Enterprise%20Voice%20enabled%20users%20being%20migrated%20to%20Teams%20Direct%20Routing)%E2%80%9D%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3EIn%20this%20section%2C%20it%20states%20that%20a%20users%20%E2%80%98OnPremLineUriManuallySet%E2%80%99%20parameter%20should%20be%20set%20to%20%E2%80%98True%E2%80%99%20when%20checking%20via%20SFBO%20PowerShell%20session%20using%20the%20%E2%80%98Get-CsOnlineUser%E2%80%99%20cmdlet.%3C%2FP%3E%3CP%3EIf%20the%20result%20does%20come%20back%20as%20%E2%80%98False%E2%80%99%20(which%20it%20is%20does%20when%20i%20migrate%20an%20EV%20enabled%20SFB%20test%20user)%20then%20the%20following%20cmdlet%20should%20be%20run%20via%20SFB%20on-premise%20management%20shell%3A%3C%2FP%3E%3CP%3ESet-CsUser%20-Identity%20%22%3CUSER%20name%3D%22%22%3E%22%20-LineUri%20%24null%20-EnterpriseVoiceEnabled%20%24False%20-HostedVoiceMail%20%24False%3C%2FUSER%3E%3C%2FP%3E%3CP%3EFollowing%20this%20then%20the%20user%20can%20be%20re-enabled%20via%20SFBO%20PS%20session%20with%20the%20associated%20phone%20number.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUp%20until%20now%20I%20have%20been%20preparing%20my%20customer%20environment%20for%20mass%20EV%20enabled%20user%20migration%20from%20SFB2015%20on-premise%20to%20Teams%20and%20following%20the%20MS%20guidance%20from%20the%20following%20articles%3A%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fskypeforbusiness%2Fhybrid%2Fplan-hybrid-connectivity%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fskypeforbusiness%2Fhybrid%2Fplan-hybrid-connectivity%3C%2FA%3E%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fskypeforbusiness%2Fhybrid%2Fmove-users-from-on-premises-to-teams%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fskypeforbusiness%2Fhybrid%2Fmove-users-from-on-premises-to-teams%3C%2FA%3E%3C%2FP%3E%3CP%3EThese%20articles%20cover%20the%20setup%20of%20SFB%20hybrid%20with%20attribute%20synchronization%20%3CSTRONG%3Eincluding%20the%20users%20phone%20number%20%3C%2FSTRONG%3Eand%20then%20simply%20executing%20the%20%E2%80%98Move-CsUser%E2%80%99%20cmdlet%20for%20%E2%80%98TeamsOnly%E2%80%99%20mode%20to%20move%20users%20from%20on-premise%20to%20Teams.%3C%2FP%3E%3CP%3EWith%20this%20approach%20it%20is%20my%20understanding%20that%20management%20of%20migrated%20users%20phone%20numbers%20should%20still%20be%20performed%20%3CSTRONG%3Eon-premise%3C%2FSTRONG%3E(and%20synched)%2C%20and%20eventually%20once%20all%20users%20are%20migrated%20we%20can%20disable%20hybrid%20and%20decommission%20the%20SFB%20servers%20%E2%80%93%20covered%20in%20following%20article%3A%20%3CU%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fskypeforbusiness%2Fhybrid%2Fcloud-consolidation-disabling-hybrid%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fskypeforbusiness%2Fhybrid%2Fcloud-consolidation-disabling-hybrid%3C%2FA%3E%3C%2FU%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECan%20someone%20provide%20clarity%20on%20whether%20the%20synchronization%20for%20the%20phone%20number%20should%20be%20broken%20for%20SFB%20on-premise%20EV%20enabled%20users%20being%20migrated%20to%20Teams%20as%20the%20various%20current%20MS%20docs%20would%20not%20appear%20to%20be%20aligned%20and%20a%20bit%20confusing%3F%20This%20is%20important%20as%20I%20need%20to%20be%20clear%20in%20my%20migration%20plan%20for%20moving%20users%20from%20on-premise%20to%20Teams.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2024195%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2024940%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Direct%20Routing%20-%20SFB%20to%20Teams%20Migration%20-%20User%20Phone%20Number%20Synchronization%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2024940%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F76246%22%20target%3D%22_blank%22%3E%40paul%20schofield%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F9476%22%20target%3D%22_blank%22%3E%40Linus%20Cansby%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F63228%22%20target%3D%22_blank%22%3E%40Thorsten%20Pickhan%3C%2FA%3E%26nbsp%3Bone%20for%20you%20guys%20as%20I%20need%20to%20look%20after%20the%20boy%20tonight%20%3AD%3C%2Fimg%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EBest%2C%20Chris%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2025304%22%20slang%3D%22de-DE%22%3ERe%3A%20Teams%20Direct%20Routing%20-%20SFB%20to%20Teams%20Migration%20-%20User%20Phone%20Number%20Synchronization%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2025304%22%20slang%3D%22de-DE%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F76246%22%20target%3D%22_blank%22%3E%40paul%20schofield%3C%2FA%3E%20and%20happy%20New%20Year!%3C%2FP%3E%3CP%3EFrom%20my%20point%20of%20view%20we%20are%20talking%20about%20two%20different%20things.%3C%2FP%3E%3CP%3EThe%20first%20scenario%2C%20where%20you%20manage%20phone%20number%20OnPrem%20and%20let%20them%20synchronize%20to%20Azure%20AD%20and%20SFBO%2FTeams%20is%20Skype%20for%20Business%20Hybrid%20Voice.%20In%20this%20scenario%20the%20Office%20365%20platform%20route%20all%20outbound%20PSTN%20calls%20to%20the%20OnPrem%20environment.%20The%20SfB%20Server%20OnPrem%20check%20the%20PSTN%20usage%20records%20etc.%20and%20routes%20the%20call%20to%20a%20defined%20PSTN%20Gateway%20which%20is%20connected%20to%20OnPrem%20environment.%20For%20inbound%20calls%2C%20the%20call%20is%20routed%20from%20the%20PSTN%20Gateway%20to%20the%20OnPrem%20SfB%20Server.%20The%20server%20makes%20a%20lookup%20where%20the%20is%20user%20is%20located.%20In%20case%20of%20an%20online%20user%2C%20the%20call%20is%20routed%20to%20Office%20365.%20As%20far%20as%20I%20know%2C%20this%20scenario%20is%20not%20recommended%20or%20even%20supported%20by%20Microsoft%20for%20Teams%20Only%20user%2C%20but%20it%20works%20because%20there%20is%20still%20the%20SfBO%20backend%20as%20middleware%20in%20place.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20the%20second%20scenario%20we%20are%20talking%20about%20Teams%20Direct%20Routing.%20In%20this%20scenario%20the%20gateway%20is%20connected%20directly%20to%20the%20Office%20365%20platform.%20Calls%20are%20routed%20to%20and%20from%20Teams%20directly%20to%20and%20from%20the%20gateway%20or%20SBC.%3C%2FP%3E%3CP%3ETherefor%20if%20you%20plan%20to%20decommission%20the%20OnPrem%20SfB%20environment%20to%20a%20give%20date%2C%20I%20suggest%20implementing%20Teams%20Direct%20Routing%20in%20parallel%20to%20your%20SfB%20trunk.%20Build%20a%20second%20trunk%20from%20your%20gateway%20or%20SBC%20to%20Microsoft%20Teams%20and%20build%20routing%20rules%20for%20inbound%20and%20outbound%20calls.%20For%20the%20migration%20of%20SfB%20users%20to%20Teams%20I%20would%20follow%20the%20Teams%20Direct%20Routing%20guide%20from%20Microsoft%2C%20as%20you%20mentioned.%20Disable%20EV%20feature%20OnPrem%2C%20synchronize%20the%20change%20to%20Office%20365%20and%20enable%20the%20user%20for%20Teams%20Direct%20Routing.%3C%2FP%3E%3CP%3EBTW%3A%20Microsoft%20wants%20to%20retire%20the%20SfB%20Cloud%20Connector%20Edition%20on%2031th%20of%20July%202021.%20Because%20Hybrid%20Voice%20is%20using%20the%20same%20PSTN%20routing%20mechanism%2C%20I%20guess%20this%20won't%20work%20after%2031th%20of%20July%20anymore.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2036906%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Direct%20Routing%20-%20SFB%20to%20Teams%20Migration%20-%20User%20Phone%20Number%20Synchronization%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2036906%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F63228%22%20target%3D%22_blank%22%3E%40Thorsten%20Pickhan%3C%2FA%3E%26nbsp%3B---%20Happy%20New%20Year%20to%20you%20also.%3C%2FP%3E%3CP%3EThankyou%20for%20your%20reply.%3C%2FP%3E%3CP%3EI%20already%20have%20my%20environment%20set%20up%20for%20Direct%20Routing%20with%20certified%20SBC's%20and%20associated%20trunks%20and%20routing%20rules%20-%20all%20is%20good%20and%20ready.%3C%2FP%3E%3CP%3EMy%20query%20was%20really%20more%20for%20the%20user%20migration%20from%20SFB%20on-premise%20to%20Teams%20as%20with%20this%20and%20other%20previous%20deployments%20i%20have%20followed%20the%20MS%20guidelines%20to%20set%20up%20SFB%20hybrid%2FAAD%20connect%20so%20SFB%20on-premise%20attributes%20can%20synch%20with%20online%20-%20with%20this%20scenario%20any%20phone%20number%20admin%20would%20be%20done%20on-premise%20(msRTCSIP)%20but%20now%20MS%20tell%20us%20for%20Direct%20Routing%20users%20to%20affectively%20break%20the%20synch%20for%20the%20phone%20number%20-%20looking%20at%20their%20article%2C%20the%20only%20way%20to%20set%20the%20'%3CSPAN%3EOnPremLineUriManuallySet'%20from%20false%20to%20true%20is%20to%20disable%20EV%20for%20the%20user%20on-premise%20and%20then%20wait%20for%20synch%26nbsp%3Bto%20take%20place%20for%20enabling%20on-line.%20Not%20ideal%20when%20we%20are%20dealing%20with%20bulk%20migrations%20as%20a%20process.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3ERegards%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2051875%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Direct%20Routing%20-%20SFB%20to%20Teams%20Migration%20-%20User%20Phone%20Number%20Synchronization%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2051875%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F76246%22%20target%3D%22_blank%22%3E%40paul%20schofield%3C%2FA%3E%26nbsp%3B%2C%20yes%2C%20this%20is%20my%20understanding.%26nbsp%3B%3C%2FP%3E%3CP%3EOf%20course%20you%20can%20force%20Azure%20AD%20to%20sync%20after%20made%20some%20changes%20OnPrem%3A%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fitops-talk-blog%2Fpowershell-basics-how-to-force-azuread-connect-to-sync%2Fba-p%2F887043%22%20target%3D%22_blank%22%3EPowerShell%20Basics%3A%20How%20to%20Force%20AzureAD%20Connect%20to%20Sync%20(microsoft.com)%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

Hi

I am currently looking at the MS Direct Routing guidelines for enablement of users: https://docs.microsoft.com/en-us/microsoftteams/direct-routing-enable-users

As part of this article, there is a sub section “Ensure that the user is homed online and phone number is not being synced from on-premises (applicable for Skype for Business Server Enterprise Voice enabled users being migrated to Teams Direct Routing)”

In this section, it states that a users ‘OnPremLineUriManuallySet’ parameter should be set to ‘True’ when checking via SFBO PowerShell session using the ‘Get-CsOnlineUser’ cmdlet.

If the result does come back as ‘False’ (which it is does when i migrate an EV enabled SFB test user) then the following cmdlet should be run via SFB on-premise management shell:

Set-CsUser -Identity "<User name>" -LineUri $null -EnterpriseVoiceEnabled $False -HostedVoiceMail $False

Following this then the user can be re-enabled via SFBO PS session with the associated phone number.

 

Up until now I have been preparing my customer environment for mass EV enabled user migration from SFB2015 on-premise to Teams and following the MS guidance from the following articles:

https://docs.microsoft.com/en-us/skypeforbusiness/hybrid/plan-hybrid-connectivity

https://docs.microsoft.com/en-us/skypeforbusiness/hybrid/move-users-from-on-premises-to-teams

These articles cover the setup of SFB hybrid with attribute synchronization including the users phone number and then simply executing the ‘Move-CsUser’ cmdlet for ‘TeamsOnly’ mode to move users from on-premise to Teams.

With this approach it is my understanding that management of migrated users phone numbers should still be performed on-premise(and synched), and eventually once all users are migrated we can disable hybrid and decommission the SFB servers – covered in following article: https://docs.microsoft.com/en-us/skypeforbusiness/hybrid/cloud-consolidation-disabling-hybrid

 

Can someone provide clarity on whether the synchronization for the phone number should be broken for SFB on-premise EV enabled users being migrated to Teams as the various current MS docs would not appear to be aligned and a bit confusing? This is important as I need to be clear in my migration plan for moving users from on-premise to Teams.

 

Thanks

4 Replies

@paul schofield 

 

@Linus Cansby @Thorsten Pickhan one for you guys as I need to look after the boy tonight :D

 

Best, Chris

Hi @paul schofield and happy New Year!

From my point of view we are talking about two different things.

The first scenario, where you manage phone number OnPrem and let them synchronize to Azure AD and SFBO/Teams is Skype for  Business Hybrid Voice. In this scenario the Office 365 platform route all outbound PSTN calls to the OnPrem environment. The SfB Server OnPrem check the PSTN usage records etc. and routes the call to a defined PSTN Gateway which is connected to OnPrem environment. For inbound calls, the call is routed from the PSTN Gateway to the OnPrem SfB Server. The server makes a lookup where the is user is located. In case of an online user, the call is routed to Office 365. As far as I know, this scenario is not recommended or even supported by Microsoft for Teams Only user, but it works because there is still the SfBO backend as middleware in place.

 

In the second scenario we are talking about Teams Direct Routing. In this scenario the gateway is connected directly to the Office 365 platform. Calls are routed to and from Teams directly to and from the gateway or SBC.

Therefor if you plan to decommission the OnPrem SfB environment to a give date, I suggest implementing Teams Direct Routing in parallel to your SfB trunk. Build a second trunk from your gateway or SBC to Microsoft Teams and build routing rules for inbound and outbound calls. For the migration of SfB users to Teams I would follow the Teams Direct Routing guide from Microsoft, as you mentioned. Disable EV feature OnPrem, synchronize the change to Office 365 and enable the user for Teams Direct Routing.

BTW: Microsoft will retire the SfB Cloud Connector Edition on 31th of July 2021. Because Hybrid Voice is using the same PSTN routing mechanism, I guess this won't work after 31th of July anymore.

Hi @Thorsten Pickhan --- Happy New Year to you also.

Thankyou for your reply.

I already have my environment set up for Direct Routing with certified SBC's and associated trunks and routing rules - all is good and ready.

My query was really more for the user migration from SFB on-premise to Teams as with this and other previous deployments i have followed the MS guidelines to set up SFB hybrid/AAD connect so SFB on-premise attributes can synch with online - with this scenario any phone number admin would be done on-premise (msRTCSIP) but now MS tell us for Direct Routing users to affectively break the synch for the phone number - looking at their article, the only way to set the 'OnPremLineUriManuallySet' from false to true is to disable EV for the user on-premise and then wait for synch to take place for enabling on-line. Not ideal when we are dealing with bulk migrations as a process.

Regards

 

Hi @paul schofield , yes, this is my understanding. 

Of course you can force Azure AD to sync after made some changes OnPrem:

PowerShell Basics: How to Force AzureAD Connect to Sync (microsoft.com)