![]() ![]() ![]() Lync 2013 deployed with no hybrid and no intentions of Hybrid setup ever.Ĥ. AD accounts synchronized with Azure with MSRTCsip/Lync attributes.ģ. We removed the O365 Licenses from the user, waited for a while and reassigned the licenses to the users, yet the message above remained.ġ. This message was a little misleading because I verified that the users were enabled with Skype for Business Online licenses. When the user attempts to sign in to Skype for Business online, they get the message below. However, as we eventually discovered, that wasn’t the case. Scenario and Symptoms: Theoretically, disabling Lync or Skype for Business on premise users, then resyncing their AD identities back to Azure AD was supposed to clear the way for users to sign in to the cloud successfully. The customer isn’t looking at setting up Skype for Business Hybrid at all, so the only option is to switch off the users accounts on premise (Deactivate or delete or simply abandon) and redirect users to log in to the Skype for Business online account. After identity synchronization, users were assigned O365 E3 license with Skype for Business plan 2 activated. Customer activates Microsoft Office 365 Cloud tenant, then synchronizes User AD identities to Azure Active Directory in the Cloud – with attributes including MSRTCsip* attributes, needed for Skype for Business online to work, when Users are migrated to Skype online from Lync on premise. ![]() Issue: Lync or Skype for Business on Premise users who have been cut over to Skype for Business online are unable to sign-in.īackground: Microsoft Lync Server 2013 have been deployed for years and fully functional on premise. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |