Office 365 users experience this issue even though the following conditions are true:
- Internal out-of-office replies are working correctly for the on-premises user.
- The internal out-of-office MailTip of the on-premises user is displayed in the mail client of the Office 365 user.
- The properties of the on-premises remote domain are correctly set to InternalLegacy.
Note After you perform either of these procedures, Office 365 mailboxes are treated as external mailboxes for the purposes of out-of-office messages. You may want to modify on-premises external out-of-office messages, if that becomes necessary.
Exchange Server 2010: Change the out-of-office setting for the remote domainIf you have an Exchange 2010 hybrid server, follow these steps:
- On the Exchange Server 2010 hybrid server, open the Exchange Management Console.
- Navigate to Organization Configuration, select Hub Transport, click the Remote Domains tab, and then double-click the remote domain.
- Click the General tab, select Allow external out-of-office message only, and then click OK.
Exchange Server 2013: Use the Exchange Management Shell to change the –AllowedOOFType property of the remote domainIf you have an Exchange Server 2013 hybrid server, use the Set-RemoteDomain cmdlet to change the –AllowedOOFType property of the Office 365 remote domain. Here are two examples:
Set-RemoteDomain Contoso -AllowedOOFType External
Set-RemoteDomain Contoso -AllowedOOFType ExternalLegacy
Article ID: 2871053 - Last Review: Dec 28, 2016 - Revision: 1