To eliminate these issues for users with cloud mailboxes, perform the following steps:Ĭreate a CNAME record in DNS (for example, ) that points to :īe sure to create this CNAME record in your internal and external (public) DNS, because users might connect from internal or external Internet connections. The endpoint causes users to see certificate mismatch warnings. The endpoint requires the domain in the URL (to distinguish between Microsoft 365 Apps for business and consumer offerings). The endpoint for the cloud mailboxes is external (it's not in the domain that users expect). The experience isn't seamless for the affected users.Ĭonfigure the TargetOWAUrl setting on the organization relationship: The issues with this option are: Tell the users the new URL (for example, ): The issues with this option are: To allow the affected users to connect to their mailboxes by using Outlook on the web, you have two options: On Monday after the move, those same users now get an error when they try to access their mailboxes by using that URL. On Friday before the move, the users accessed their on-premises mailboxes by using the URL. With that in mind, the Outlook on the web (formerly known as Outlook Web App) coexistence story is important.Ĭonsider the following scenario: a company uses a hybrid deployment to move some of their mailboxes from on-premises Exchange to Microsoft 365 or Office 365. Users need uninterrupted access to their mailboxes regardless of where or when their mailbox is moved. Learn how to configure a URL for Outlook on the web (Outlook Web App) for cloud mailbox users in a hybrid environment.Ī major concern for organizations that move to Microsoft 365 or Office 365 from on-premises Exchange is the user experience.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |