Provision new Teams user accounts without SfB Hybrid account migration

%3CLINGO-SUB%20id%3D%22lingo-sub-893543%22%20slang%3D%22en-US%22%3EProvision%20new%20Teams%20user%20accounts%20without%20SfB%20Hybrid%20account%20migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-893543%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20successfully%20migrated%20users%20from%20on-prem%20SfB%20Server%202019%20to%20Teams%20with%20PSTN%20calling%20and%20is%20planning%20on%20decommissioning%20the%20SfB%20servers%20that%20is%20currently%20configured%20in%20a%20hybrid.%26nbsp%3B%20We%20currently%20provision%20new%20hire%20AD%20accounts%20on%20our%20on-prem%20Exchange%20(although%20we%20fully%20utilize%20O365%20w%2F%20AD%20Sync)%20and%20in%20SfB%20Server%20Control%20Panel%20and%20then%20migrate%20the%20SfB%20account%20to%20Teams.%26nbsp%3B%20When%20we%20do%20decommission%20the%20SfB%20servers%2C%20how%20do%20I%20provision%20a%20new%20account%20for%20Teams%20use%3F%26nbsp%3B%20I've%20also%20researched%20the%20AD%20attribute%20differences%20between%20an%20AD%20account%20that%20was%20migrated%20from%20SfB%20to%20Teams%20and%20a%20vanilla%20AD%20account%20that%20was%20just%20created%20with%20the%20on-prem%20Exchange%20server%20with%20an%20O365%20mailbox%20and%20found%20that%20a%20SfB%20migrated%20account%20populates%20the%20following%20AD%20attributes.%26nbsp%3B%20Do%20I%20need%20to%20keep%20the%20on-prem%20SfB%20server%20running%20forever%20if%20I%20don't%20populate%20those%20attributes%20manually%3F%26nbsp%3B%20Is%20there%20a%20way%20that%20I%20can%20provision%20a%20new%20account%20with%20minimal%20manual%20AD%20attribute%20population%20for%20Teams%20usage%20assuming%20that%20there%20won't%20be%20any%20on-prem%20SfB%20servers%20around%20in%20the%20future%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EmsRTCSIP-DeploymentLocator%3CBR%20%2F%3EmsRTCSIP-FederationEnabled%3CBR%20%2F%3EmsRTCSIP-InternetAccessEnabled%3CBR%20%2F%3EmsRTCSIP-Line%3CBR%20%2F%3EmsRTCSIP-OptionFlags%3CBR%20%2F%3EmsRTCSIP-PrimaryHomeServer%3CBR%20%2F%3EmsRTCSIP-PrimaryUserAddress%3CBR%20%2F%3EmsRTCSIP-UserEnabled%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-893543%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdministrator%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EHow-to%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-893697%22%20slang%3D%22en-US%22%3ERe%3A%20Provision%20new%20Teams%20user%20accounts%20without%20SfB%20Hybrid%20account%20migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-893697%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F420184%22%20target%3D%22_blank%22%3E%40ADGAdmin%3C%2FA%3E%26nbsp%3BDo%20you%20ultimately%20have%20users%20set%20to%20TeamsOnly%20mode%20once%20their%20Skype%20account%20is%20moved%20from%20on-prem%20SkypeOnline%3F%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIve%20been%20recently%20researching%20this%20and%20one%20snag%20I%20realized%20is%20for%20my%20school...the%20UPN%20and%20SIP%20address%20(for%20an%20on-prem%20Skype%20user)%20is%20different.%26nbsp%3B%20The%20reason%20why%20I%20mention%20this%20is%20when%20you%20provision%20a%20user%20for%20Skype%20Online%20(via%20adding%20the%20Skype%20Online%20license)%20the%20SIP%20address%20will%20match%20UPN.%26nbsp%3B%26nbsp%3B%20Then%20when%20you%20set%20TeamsOnly%20for%20federated%20chat%2C%20users%20will%20be%20searchable%20via%20that%20same%20address.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-893655%22%20slang%3D%22en-US%22%3ERe%3A%20Provision%20new%20Teams%20user%20accounts%20without%20SfB%20Hybrid%20account%20migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-893655%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3CBR%20%2F%3E%3CBR%20%2F%3Eif%20you%20say%20Teams%20with%20PSTN%20calling%20you%20mean%20Teams%20with%20a%20calling%20Plan%20from%20Microsoft%3F%3CBR%20%2F%3EYou%20don't%20need%20to%20keep%20an%20SfB%20server%20for%20managing%20Teams%20if%20you%20are%20pure%20Online%20for%20SfB%2FTeams.%20To%20decommission%20the%20SfB%20server%20environment%20here%20is%20a%20guide%20that%20you%20can%20use%20for%20your%20planning.%3CBR%20%2F%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fblogs.technet.microsoft.com%2Ffasttracktips%2F2017%2F06%2F27%2Fdecommissioning-skypelync-on-premises%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fblogs.technet.microsoft.com%2Ffasttracktips%2F2017%2F06%2F27%2Fdecommissioning-skypelync-on-premises%2F%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3EAt%20the%20end%2C%20you%20should%20ensure%20that%20the%20SfB%20online%20attribute%20InterpretedUserType%20is%20DirSyncSfBUser%26nbsp%3Bfor%20your%20csonlineusers%3CBR%20%2F%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fmsunified.net%2F2019%2F07%2F11%2Fmy-post-migration-from-skype-to-teams-toolbox%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fmsunified.net%2F2019%2F07%2F11%2Fmy-post-migration-from-skype-to-teams-toolbox%2F%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3EYou%20can%20achieve%20this%20by%20disabling%20all%20SFB%20user%20accounts%20and%20ensure%20that%20all%20msRTC%20attributes%20are%20blank.%20You%20don't%20need%20them%20for%20a%20Teams%20deployment%20without%20SfB%20Server.%3CBR%20%2F%3E%3CBR%20%2F%3EDoing%20an%20unprep%20of%20the%20forest%20and%20domain%20is%20also%20an%20option%20so%20you%20don%E2%80%99t%20have%20any%20OnPrem%20msRTC%20attributes.%3CBR%20%2F%3EA%20new%20user%20will%20be%20added%20to%20the%20OnPrem%20AD%2C%20then%20synced%20and%20then%20enabled%20for%20teams%20by%20adding%20a%20license.%3CBR%20%2F%3E%3CBR%20%2F%3EHope%20this%20helps%3CBR%20%2F%3E%3CBR%20%2F%3ERegards%2C%3CBR%20%2F%3E%3CBR%20%2F%3EPaul%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-893704%22%20slang%3D%22en-US%22%3ERe%3A%20Provision%20new%20Teams%20user%20accounts%20without%20SfB%20Hybrid%20account%20migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-893704%22%20slang%3D%22en-US%22%3E%3CP%3EHello%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F44596%22%20target%3D%22_blank%22%3E%40Paul%20Lange%3C%2FA%3E%26nbsp%3B%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%20for%20the%20reply%20and%20yes%2C%20we're%20currently%20using%20Microsoft%20calling%20plan%20for%20PSTN.%26nbsp%3B%20The%20reference%20posts%20do%20make%20sense%20and%20I%20will%20further%20look%20into%20decommissioning%20process%20and%20un-prepping%20AD%20to%20remove%20the%20on-prem%20msRTC%20attributes.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-893705%22%20slang%3D%22en-US%22%3ERe%3A%20Provision%20new%20Teams%20user%20accounts%20without%20SfB%20Hybrid%20account%20migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-893705%22%20slang%3D%22en-US%22%3EYes%2C%20we%20are%20on%20TeamsOnly%20as%20this%20is%20the%20method%20for%20supporting%20PSTN%20dialing%20on%20Teams.%20Our%20UPN%20and%20email%20address%20are%20also%20different%2C%20but%20created%20a%20matching%20alias%20domain%20and%20made%20it%20our%20default%20UPN%20to%20match%20our%20organization%20email%20address.%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

Hello,

 

We have successfully migrated users from on-prem SfB Server 2019 to Teams with PSTN calling and is planning on decommissioning the SfB servers that is currently configured in a hybrid.  We currently provision new hire AD accounts on our on-prem Exchange (although we fully utilize O365 w/ AD Sync) and in SfB Server Control Panel and then migrate the SfB account to Teams.  When we do decommission the SfB servers, how do I provision a new account for Teams use?  I've also researched the AD attribute differences between an AD account that was migrated from SfB to Teams and a vanilla AD account that was just created with the on-prem Exchange server with an O365 mailbox and found that a SfB migrated account populates the following AD attributes.  Do I need to keep the on-prem SfB server running forever if I don't populate those attributes manually?  Is there a way that I can provision a new account with minimal manual AD attribute population for Teams usage assuming that there won't be any on-prem SfB servers around in the future?

 

msRTCSIP-DeploymentLocator
msRTCSIP-FederationEnabled
msRTCSIP-InternetAccessEnabled
msRTCSIP-Line
msRTCSIP-OptionFlags
msRTCSIP-PrimaryHomeServer
msRTCSIP-PrimaryUserAddress
msRTCSIP-UserEnabled

4 Replies
Highlighted

Hi,

if you say Teams with PSTN calling you mean Teams with a calling Plan from Microsoft?
You don't need to keep an SfB server for managing Teams if you are pure Online for SfB/Teams. To decommission the SfB server environment here is a guide that you can use for your planning.

https://blogs.technet.microsoft.com/fasttracktips/2017/06/27/decommissioning-skypelync-on-premises/

At the end, you should ensure that the SfB online attribute InterpretedUserType is DirSyncSfBUser for your csonlineusers

https://msunified.net/2019/07/11/my-post-migration-from-skype-to-teams-toolbox/

You can achieve this by disabling all SFB user accounts and ensure that all msRTC attributes are blank. You don't need them for a Teams deployment without SfB Server.

Doing an unprep of the forest and domain is also an option so you don’t have any OnPrem msRTC attributes.
A new user will be added to the OnPrem AD, then synced and then enabled for teams by adding a license.

Hope this helps

Regards,

Paul

Highlighted

@ADGAdmin Do you ultimately have users set to TeamsOnly mode once their Skype account is moved from on-prem SkypeOnline?  

 

Ive been recently researching this and one snag I realized is for my school...the UPN and SIP address (for an on-prem Skype user) is different.  The reason why I mention this is when you provision a user for Skype Online (via adding the Skype Online license) the SIP address will match UPN.   Then when you set TeamsOnly for federated chat, users will be searchable via that same address.

 

Highlighted

Hello @Paul Lange ,

 

Thank you for the reply and yes, we're currently using Microsoft calling plan for PSTN.  The reference posts do make sense and I will further look into decommissioning process and un-prepping AD to remove the on-prem msRTC attributes.

Highlighted
Yes, we are on TeamsOnly as this is the method for supporting PSTN dialing on Teams. Our UPN and email address are also different, but created a matching alias domain and made it our default UPN to match our organization email address.