This article describes how to troubleshoot free/busy issues that occur in a hybrid deployment of on-premises Microsoft Exchange Server and of Microsoft Exchange Online in Office 365.
For more information about how deploy Exchange federation, go to the following Microsoft website:
After you set up Exchange federation, you may experience one or more of the following issues:
- Free/busy information can't be retrieved from any account in either environment.
- Free/busy information can't be retrieved from one environment.
- Free/busy information can't be retrieved from an on-premises account by using a cloud account.
- Free/busy information can't be retrieved from a cloud account by using an on-premises account.
- Free/busy information is unavailable in a hybrid deployment scenario between an on-premises Exchange Server 2003 organization or a mixed on-premises Exchange Server 2003 or Exchange Server 2007 organization and Exchange Online.
Free/busy information can't be retrieved from any account in either environment
Users in either environment in the Exchange federated organization can't retrieve free/busy information from mailboxes that are located in the other environment.
In this case, the problem may be a local issue on the individual computers. Or, Exchange federation may not be set up correctly.
To help troubleshoot this issue, ask users to determine whether the issue occurs when they use Microsoft Outlook and when they use Outlook Web App for Office 365. If the behavior differs in Outlook and in Outlook Web App, the problem may be that the individual computer doesn't meet the requirements for Exchange federation. Ask the user to follow these steps:
- Sign in to the Office 365 portal (https://portal.office.com
- Click Settings (
), click Software, and then click Desktop setup.
Collapse this imageExpand this image
- Click Set up.
After the user sets up his or her Office 365 desktop applications, the free/busy issue should be resolved. Also, make sure that the computer has Microsoft Office Outlook 2007 or Microsoft Outlook 2010 installed. Earlier versions of Outlook aren't supported with Office 365.
If this problem occurs identically in Outlook and in Outlook Web App, there's probably an issue with how Exchange federation is set up in your organization. In this case, see the Microsoft Exchange Server Deployment Assistant
to make sure that the environment meets the system requirements.
Free/busy information can't be retrieved from one environment
Users can't access free/busy information through Exchange federation in one direction only. For example, on-premises users can't access free/busy information from cloud mailboxes. Or, cloud users can't access free/busy information from on-premises mailboxes.
In this scenario, the problem may be caused by a misconfiguration of the Application Target URI. Or, the sharing policies in the on-premises Exchange Server environment and in Exchange Online may not match.
To help troubleshoot this issue, follow these steps:
- On an on-premises computer that's running Microsoft Exchange 2010 Server Service Pack 1 (SP1), click Start, click All Programs, click Microsoft Exchange Server 2010, and then click Exchange Management Shell.
- At the command line, type the following command, and then press Enter:
In this command, the <Office 365 Domain> placeholder represents the default Office 365 domain (for example, adatum.onmicrosoft.com).
Get-FederationInformation -domainname <Office 365 Domain>
- In the results, note the TargetApplicationUri and TargetAutodiscoverEpr values. These are the settings that the target domain must have to make sure that the federation trust is set up correctly.
- To display the trust information that is currently set up for the default Office 365 domain, run the following command:
Get-OrganizationRelationship | FL
- In the DomainNames section, make sure that the following are displayed:
If they aren't displayed in the DomainNames section, there may be a problem with the setup of Exchange federation. Review the Microsoft Exchange Server Deployment Assistant
- The name of the company’s service routing domain (for example, service.adatum.com)
- The name of the company’s federated domain (for example, adatum.com)
to make sure that your configuration aligns to the recommended steps and that the environment meets all the system requirements. If the two domains are displayed correctly in the DomainNames section, note the following sections in the results:
The TargetApplicationUri and TargetAutodiscoverEpr values should match the equivalent values from the Get-FederationInformation cmdlet. If the values don't match, run the following command to correct the difference:
Set-OrganizationRelationship -Identity <Name> -TargetApplicationUri <TargetApplicationUri> -TargetAutodiscoverEpr <TargetAutodiscoverEpr>
- If the free/busy problem persists, make sure that the sharing policies in the on-premises Exchange Server environment and in Exchange Online match. To determine this, run the following command in the Exchange Management Shell, and then note the value in the Domains field in the results:
- Connect to Exchange Online by using Windows PowerShell to run the same test in the other environment. You do this so that you can determine whether the sharing policies match. For more information about how to connect to Exchange Online by using Windows PowerShell, go to the following Microsoft website:
- After you connect to Exchange Online, run the following command in the Windows PowerShell window, as you did for the on-premises environment, and then note the value in the Domains field:
- The Domains values for the two environments should match. If they don't match, you can use the Set-SharingPolicy cmdlet to set up the Domains field so that it matches on both sides. For more information about the Set-SharingPolicy cmdlet and about how to use this sharing policy setting, go to the following Microsoft TechNet website:
Free/busy information can't be retrieved from a cloud account by using an on-premises account
The problem is limited to on-premises users who try to retrieve free/busy information for cloud mailboxes.
In this case, you can use the Test-FederationTrust
cmdlet to collect more details about the failure. To do this, follow these steps:
- In the Exchange Management Shell, run the following command, where the <OnPremisesMailbox> placeholder represents the email address of a user mailbox that's hosted in the on-premises environment:
Note This command tests the federation trust token that's used by the on-premises user.
Test-FederationTrust -UserIdentity <OnPremisesMailbox> -verbose
- Assuming that the results contain at least one
section where the Type is Failed, copy the results into a text file, and then send the file to Exchange Online Services Support for more help.
Free/busy information can't be retrieved from an on-premises account by using a cloud account
The problem is limited to cloud users who try to retrieve free/busy information for on-premises mailboxes.
In this case, the mailboxes that are involved may be hosted on Microsoft Exchange Server 2003 instead of on Exchange Server 2007 or instead of on Exchange Server 2010. Exchange Server 2003 doesn't support the Exchange Web Services requests that later versions use to obtain free/busy information. Make sure that any free/busy data that is held in Exchange Server 2003 public folders is being replicated to an Exchange Server 2010 mailbox server that can support a public folder database.
- You can install the mailbox role on the same server on which the Client Access Server (CAS) role that you use to support federation is installed. For more information about how to do this by using the Microsoft Exchange Server Deployment Assistant, go to Exchange Server Deployment Assistant.
- If the cloud users still have problems when they try to retrieve free/busy information for on-premises mailboxes, determine whether there is a problem connecting to the Autodiscover service on-premises. To do this, follow these steps:
- Open the Microsoft Remote Connectivity Analyzer at the following Microsoft website:
- On the Outlook Autodiscover page, complete the form by using the email address and the password of an account in the on-premises environment that has problems. Click to select the check box to confirm that you have the authority to enter the credentials of a working account.
- To confirm that an automated program is making a request, you must complete a human interface challenge. Type the letters and numbers from the picture into the box, and then click Perform Test.
- If the test fails, check the settings for the on-premises proxy server and for the firewall. Make sure that Exchange Online CAS can be accessed from the Internet over port 443.
Free/busy information is unavailable in a hybrid deployment between an on-premises Exchange 2003 organization or a mixed on-premises Exchange 2003 or Exchange 2007 organization and Exchange Online
In this scenario, the OU=EXTERNAL (FYDIBOHF25SPDLT) public folder is missing from the public folder hierarchy and must be added.
To add the OU=EXTERNAL (FYDIBOHF25SPDLT) public folder, follow these steps:
- Connect to the on-premises Exchange 2010 SP1 public folder server from the public folder server.
- Open Windows PowerShell.
- Run the following command:
- Run the following command:
If you experience issues with the Hybrid Configuration wizard, you can run the Exchange Hybrid Configuration Diagnostic
. This diagnostic is an automated troubleshooting experience. Run it on the same server on which the Hybrid Configuration wizard failed. Doing this collects the Hybrid Configuration wizard logs and parses them for you.
If you're experiencing a known issue, a message is displayed that tells you what went wrong. The message includes a link to an article that contains the solution. Currently, the diagnostic is supported only in Internet Explorer.
Still need help? Go to the Office 365 Community
website or the Exchange TechNet Forums
Article ID: 2555008 - Last Review: March 12, 2015 - Revision: 31.0
- Microsoft Exchange Online
|o365 o365a o365e o365m o365022013 hybrid gwt guided walk through kbtshoot kbgraphic KB2555008|