Implementation of OWA unified login after local exchange and Exchange online hybrid deployment

After you deploy Exchange 2013 locally, we can use the specified OWA address for mail access, such as: mail.contoso.com. When we implement a hybrid deployment of on-premises Exchange 2013 and Office Exchange online, Whether you are an Exchange online user or a local exchange2013 mailbox user, you can also use mail.contoso.com for a unified login, and the answer is yes.

When a user accesses through a local OWA address, they see a hint like the following:

650) this.width=650; "height=" 275 "title=" clip_image001 "style=" border:0px;padding-top:0px;padding-right:0px; Padding-left:0px;background-image:none, "alt=" clip_image001 "src=" http://s3.51cto.com/wyfs02/M00/82/B6/ Wkiol1dfy9bq5cfnaacw1dt-z7e072.gif "border=" 0 "/>

After users click on the link above, they will jump to Office365 (if a single sign-on SSO is deployed and the domain machine is added), then the user does not need to enter the username password and the user will have a single sign-on experience. If not, the user needs to enter a user name and password)

650) this.width=650; "height=" 278 "title=" clip_image002 "style=" border:0px;padding-top:0px;padding-right:0px; Padding-left:0px;background-image:none, "alt=" clip_image002 "src=" http://s3.51cto.com/wyfs02/M01/82/B6/ Wkiol1dfy9fqzspvaabgqbbswxm775.gif "border=" 0 "/>

Note : The following versions of Exchange CU3, owaredirection do not work

Http://support.microsoft.com/kb/2890814/zh-cn

After the Office 365 hybrid deployment is complete, the default is OWA unified login, if not implemented, we can view and set the following methods

The specific inspection steps are as follows:

1. First, on the local Exchange 2013 server, run the following command through the Exchange Management Shell:

Get-hybridconfiguration

Then in the features output, make sure that the owaredirection exists as shown in:

650) this.width=650; "height=" 247 "title=" clip_image003 "style=" border:0px;padding-top:0px;padding-right:0px; Padding-left:0px;background-image:none, "alt=" clip_image003 "src=" http://s3.51cto.com/wyfs02/M02/82/B6/ Wkiol1dfy9jy1hk2aac6uokx0pe218.jpg "border=" 0 "/>

If Owaredirection does not exist, you need to configure it with the Set-hybridconfiguration command

Example:

Set-hybridconfiguration-features onlinearchive,mailtips,owaredirection, freebusy,messagetracking

2. Next, you want to make sure that the Targetowaurl parameter in the Organizationrelationship (Organization relationship) configuration on the local Exchange server points to Office365, in the following steps:

, open the Exchange Management Shell on the local server, and run the following command:

Get-organizationalrelationship–identity enter a local to Office365 relationship name here |FL

Note: If there is only an organization relationship to Office365 locally, you can run Get-organizationrelationship directly |FL

As shown in the output, you need to make sure that the Targetowaurl attribute points to Office365, which is http://outlook.com/owa/contoso.com here for your hybrid primary SMTP domain

650) this.width=650; "height=" 145 "title=" clip_image004 "style=" border:0px;padding-top:0px;padding-right:0px; Padding-left:0px;background-image:none, "alt=" clip_image004 "src=" http://s3.51cto.com/wyfs02/M00/82/B8/ Wkiom1dfysicw8qpaaay2dzqh1q594.jpg "border=" 0 "/>

If this setting is empty, run the set-organizationrelationship command to set

Example:

Set-organizationrelationship-identity "on-premises to O365-xxxxxx" –targetowaurl http://outlook.com/owa/contoso.com

This article is from "Jianbin Liu's Blog" blog, please be sure to keep this source http://liujb.blog.51cto.com/269257/1789008

Implementation of OWA unified login after local exchange and Exchange online hybrid deployment