Forum Discussion
SfB OnPrem to Te
Hello.
We plan to migrate all our SfB OnPrem users to Teams.
On Teams for voice we setup Direct Routing.
Now I have some question.
To enable Direct Routing for Teams user some data should be setup in SfB OnPrem like line uri. Also user should be first created in SfB OnPrem and then migrated to the cloud.
So what in situation if we move all users to Teams? Could we shut down SfB OnPrem?
19 Replies
msabat From SFB onprem to Teams migration, you need to follow the below steps in chronological order:
1. Complete the SFB hybrid configuration if not its not done.
2. Configure the Direct routing with certified SBC (With Onpremise SBC/hosted one)
3. Configure the Voice routing and PSTN usage
4. move the users to Teams only mode
5. Apply the Voice routing policy to users so that users can call to PSTN World.
6. Do the testing
7. then decommision the onprem servers, remove the certificates
pankmishra Ok. So when I finish moving all users from SfB on Prem to Team and when I delete hybrid connectivity what should I do next?
Could I decomm whole SfB on Prem enviroment? Is there anything else I should do?
Based on that doc - https://docs.microsoft.com/en-us/skypeforbusiness/hybrid/cloud-consolidation-disabling-hybrid - I will still have manage phone numbers thru AD or could I use -OnPremLineURI paramether?
I have another question.
What about CAPs?
How could I migrate them and assign Direct Routing number?
The term Common Area Phone means two entirely different things when talking about Lync and Skype for Business Server deployments versus Skype for Business Online.
- In server-based environments a Common Area Phone (CAP) account is a special type of user account which in essence is simply an Active Directory Contact Object that is enabled in Lync/SfB Server differently than standard AD User objects. This model was first introduced in Lync Server 2010 with the advent of the Aries model family of the Lync Phone Edition platform and leverages only Certificate-based Authentication (TLS-DSK) via PIN Authentication and DHCP Options 43/120. These accounts are not Exchange mailbox-enabled and thus address a simple goal: the ability to register a phone using generic credentials, provisioned and managed by an administrator, which is intended solely to provide basic ‘dial-tone’ features to a handset or conference phone. These CAP accounts then also provide the hot-desking capability to the registered device so that a fully-featured user can temporarily sign-in with their own account.
- With Skype for Business Online/Teams though the CAP terminology is completely different as this is currently related only to licensing and device provisioning. A new, dedicated Office 365 license has been added to reduce the overall cost for common-use IP phones and a new Web Sign-in method specific to these common-area use cases as also been added. There is no special account type like with the server platform as any standard online user account can be used with the new license, meaning that Exchange calendaring is available for phones registered using a CAP-enabled account. Registering a phone to Skype for Business online is also completely different than the server-only PIN Authentication method.
For configuring Direct routing, Teams should be in "TeamsOnly" mode and then there is no connection from OnPremSetup. You can setup dial-plan, VP , PSTN usage , route and line uri directly in Teams ,same as we do in S4BonPrem.
you can refer the MS migration document, it's clearly mentioned there.
Ok.
I should only mention that I have hybrid configuration.
I checked in Teams and there is no way to assigne my number with Direct Routing straight to the user.
- Have you setup a gateway for direct routing in your infrastructure? If yes then follow the instruction in below document to enable user with telephone number , voice routing and Dial plan etc... you should have Teams power shell access to enable /configure these setting.
https://docs.microsoft.com/en-us/microsoftteams/direct-routing-configure
