![]() I've been hunting for a solution to this issue and no one seems to have a good way to fix this during a pilot migration. This is definitely due to the autodiscover DNS entries not pointing to the Exchange online Tenant URLs for our Domain, but is there a way we can fix this for our pilot users during the migration?I can't change theĪutodiscover DNS entries as it will break the remaining 500 or so users' integration between Skype for Business and Exchange. ![]() Whenever they have Skype for Business open. ![]() They will be using Skype for Business On Premises with Exchange Online, and at the moment the are all continually prompted to enter their Exchange credentials Unfortunately though, we have a small pilot user group who now have their Mail in Exchange Online. Once we have migratedĮveryone we change our Autodiscover DNS entries to match the Exchange Online URLs. This works very well with Skype For Business On-Premises integrating Calendar and Status information.Įventually all of our users will be using On-Premise Skype for Business with Exchange Online. We are in the midst of migrating On-Premise Exchange mailboxes to Exchange Online.Ĭurrently, our Autodiscover DNS entries point to our On-Premises Exchange Client Access Server.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |