You need to be assigned permissions before you can perform this procedure. To see what permissions you need to create an organization relationship, see the "Organization relationships" entry in Mailbox Permissions. To modify public folder replicas in Exchange 2003, you must be a member of the Exchange Full Administrator or Exchange Administrator groups.

You can use the New Organization Relationship wizard in the Exchange Management Console on the hybrid server to create the organization relationship.

1. In the console tree, click Organization Configuration for the on-premises Exchange forest.
   
   
2. In the action pane, click New Organization Relationship.
   
   
3. On the Introduction page, complete the following fields:
   
   
   • Name   Type a name for the organization relationship. For example, "To Cloud" would mean that this relationship is for the cloud-based organization.
     
     
   • Enable this organization relationship   Select this check box to enable this organization relationship.
     
     
   • Enable free/busy information access   Select this check box to specify that this organization relationship should be used for retrieving free/busy information from the on-premises organization by the cloud-based organization.
     
     
   • Specify free/busy data access level   Select the Free/busy access with time only option to specify that basic free/busy information should be retrieved from the on-premises organization by the cloud-based organization.
     
     

     Note:
     The Free/busy access with time, plus subject and location access level is not supported with Exchange 2003.

   • Specify a security distribution group that indicates what internal users free/busy data is accessible   Select this check box if you want to specify a distribution group to list your users who can have their free/busy information accessed by the cloud-based service organization. Use the corresponding box to type the SMTP address of a security distribution group within your organization, or click Browse to search for the group.
     
     
4. On the External Organization page, complete the following fields:
   
   
   • Automatically discover configuration information   Select this option to have Exchange locate the configuration information of the cloud-based organization by using Autodiscover.
     
     
   • Specify a federated domain of the external Exchange organization   Enter a federated domain of the cloud-based organization (for example, service.contoso.com). You can't specify more than one domain.
     
     

     Note:

     You can also choose to manually enter the federated domains for the cloud-based organization during this step. If you elect to manually configure the federated domains, enter both the service-routing namespace and the primary SMTP namespaces for your on-premises organization. For example, the federated domains include both the service.contoso.com and contoso.com domains. If either of these domains is missing from the organization relationship, the sharing of free/busy availability information may not function correctly.

5. On the New Organization Relationship page, review your configuration settings. Click New to create the organization relationship. Click Back to make changes.
   
   
6. On the Completion page, review the following, and then click Finish to close the wizard:
   
   
   • A status of Completed indicates that the wizard completed the task successfully.
     
     
   • A status of Failed indicates that the task wasn't completed. If the task fails, review the summary for an explanation, and then click Back to make any configuration changes.
     
     

After creating the organization relationship, you must also manually add the primary SMTP namespace and enable MailTips and message tracking for the organization relationship so these features function correctly. If you chose to manually add both the service-routing and primary SMTP namespaces as federated domains in the New Organization wizard, you will only have to enable MailTips and message tracking.

To add the primary SMTP namespace and enable MailTips and message tracking to the on-premises organization relationship, use the following command in the Shell on the hybrid server.

	Copy Code
Set-OrganizationRelationship -Identity "To Cloud" -DomainNames "service.contoso.com","contoso.com" -MailTipsAccessEnabled $True -MailTipsAccessLevel All -DeliveryReportEnabled $True

To enable free/busy information sharing in a hybrid deployment, the following folders located in the Schedule+ FREE BUSY public folder in your organization must be replicated to the hybrid server:

• OU=EXTERNAL (FYDIBOHF25SPDLT)
  
  
• OU=Exchange Administrative Group (FYDIBOHF23SPDLT)
  
  

If the OU=EXTERNAL (FYDIBOHF25SPDLT) folder is missing from your public folder hierarchy on the hybrid server, you’ll need to add it prior to replication. Follow the steps below to add the OU=EXTERNAL (FYDIBOHF25SPDLT) public folder to the hybrid server if needed.

1. Open Windows PowerShell on the hybrid server.
   
   
2. Run the Add-PSSnapin Microsoft.Exchange.Management.Powershell.Setup command and press Enter.
   
   
3. Type Install-FreeBusyFolder at the prompt and press Enter.
   
   
4. Exit Windows PowerShell.
   
   

To replicate these folders to the hybrid server, you must use the Exchange System Manager located on an Exchange 2003 server.

1. In Exchange System Manager, navigate to Administrative Groups > First Administrative Group > Servers.
   
   
2. Select your Exchange 2003 server and navigate to First Storage Group > Public Folder Store > Public Folders > Schedule+ FREE BUSY.
   
   
3. In the action pane, select the OU=EXTERNAL (FYDIBOHF25SPDLT) folder for the First Administrative Group.
   
   
4. Right-click the OU=EXTERNAL (FYDIBOHF25SPDLT) folder, and then click Properties.
   
   
5. In OU=EXTERNAL (FYDIBOHF25SPDLT) Properties, select the Replication tab.
   
   
6. To replicate the OU=EXTERNAL (FYDIBOHF25SPDLT) folder to the hybrid server, click Add.
   
   
7. In Select a Public Folder Store, select the Public Folder Database for the hybrid server and then click OK.
   
   

   Note:
   By default, Exchange uses the replication schedule set on the public folder database.

8. Click OK to close OU=EXTERNAL (FYDIBOHF25SPDLT) Properties and save your changes.
   
   
9. Complete the same steps above for the OU=Exchange Administrative Group (FYDIBOHF23SPDLT) folder.
   
   

Note:
Depending on the size of your public folders, this replication could take several hours to complete.

After the OU=EXTERNAL (FYDIBOHF25SPDLT) and OU=Exchange Administrative Group (FYDIBOHF23SPDLT) public folders have replicated to the hybrid server, you must remove the replicas for these public folders on the Exchange 2003 server.

Important:
To avoid a single point of failure for these public folder replicas, you should consider adding additional Exchange 2010 SP1 servers to your on-premises organization for redundancy. Additional Exchange 2010 SP1 servers used for hosting public folder replicas should only have the Mailbox server role installed to avoid mail transport configuration problems.

You must use the Exchange System Manager located on an Exchange 2003 server to remove the OU=EXTERNAL (FYDIBOHF25SPDLT) and OU=Exchange Administrative Group (FYDIBOHF23SPDLT) public folder replicas.

1. In Exchange System Manager, navigate to Administrative Groups > First Administrative Group > Servers.
   
   
2. Select your Exchange 2003 server and navigate to First Storage Group > Public Folder Store > Public Folders > Schedule+ FREE BUSY.
   
   
3. In the action pane, select the OU=EXTERNAL (FYDIBOHF25SPDLT) folder for the First Administrative Group.
   
   
4. Right-click the OU=EXTERNAL (FYDIBOHF25SPDLT) folder, and then click Properties.
   
   
5. In OU=EXTERNAL (FYDIBOHF25SPDLT) Properties, select the Replication tab.
   
   
6. To remove the OU=EXTERNAL (FYDIBOHF25SPDLT) folder from the Exchange 2003 server, select the Exchange 2003 server from the list of servers in Replicate content to these public stores and click Remove.
   
   
7. Click OK to close OU=EXTERNAL (FYDIBOHF25SPDLT) Properties and save your changes.
   
   
8. Complete the same steps above for the OU=Exchange Administrative Group (FYDIBOHF23SPDLT) folder.
   
   

You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "Organization relationships" entry in Mailbox Permissions.

First, use the following command in the Shell on the cloud-based organization to enable customization. This action may take several minutes to complete.

	Copy Code
Enable-OrganizationCustomization

Important:
If a This operation is not available in current service offer error is returned after running this command in the Shell, your cloud-based organization is already configured for customization. You can safely ignore this error and continue with the checklist steps.

Next, you can use the New Organization Relationship wizard in the Exchange Management Console on the hybrid server to create the organization relationship.

1. In the console tree, click Organization Configuration for the cloud-based organization Exchange forest.
   
   
2. In the action pane, click New Organization Relationship.
   
   
3. On the Introduction page, complete the following fields:
   
   
   • Name   Type a name for the organization relationship. For example, "To On-Premises" would mean that this relationship is for the on-premises organization.
     
     
   • Enable this organization relationship   Select this check box to enable this organization relationship.
     
     
   • Enable free/busy information access   Select this check box to specify that this organization relationship should be used for retrieving free/busy information from the cloud-based organization by the on-premises organization.
     
     
   • Specify free/busy data access level   Select the Free/busy access with time only option to specify that basic free/busy information should be retrieved from the on-premises organization by the cloud-based organization.
     
     

     Note:
     The Free/busy access with time, plus subject and location access level is not supported with Exchange 2003.

   • Specify a security distribution group that indicates what internal users free/busy data is accessible   Select this check box if you want to specify a distribution group to list your users who can have their free/busy information accessed by the on-premises organization. Use the corresponding box to type the SMTP address of a security distribution group within your organization, or click Browse to search for the group.
     
     
4. On the External Organization page, complete the following fields:
   
   
   • Automatically discover configuration information   Click this button to have Exchange locate the configuration information of the on-premises organization by using Autodiscover.
     
     
   • Specify a federated domain of the external Exchange organization   Enter a federated domain of the on-premises organization (for example, contoso.com). You can't specify more than one domain.
     
     

     Note:

     You can also choose to manually enter the federated domains for the on-premises organization during this step. If you elect to manually configure the federated domains, enter both the federated delegation namespace and the primary SMTP namespace for your on-premises organization. For example, the federated domains include both the exchangedelegation.contoso.com and contoso.com domains. If either of these domains is missing from the organization relationship, the sharing of free/busy availability information may not function correctly.

5. On the New Organization Relationship page, review your configuration settings. Click New to create the organization relationship. Click Back to make changes.
   
   
6. On the Completion page, review the following, and then click Finish to close the wizard:
   
   
   • A status of Completed indicates that the wizard completed the task successfully.
     
     
   • A status of Failed indicates that the task wasn't completed. If the task fails, review the summary for an explanation, and then click Back to make any configuration changes.
     
     

After creating the organization relationship, you must also manually add the federated delegation namespace and enable MailTips and message tracking for the organization relationship so these features function correctly. If you chose to manually add both the federated delegation and primary SMTP namespaces as federated domains in the New Organization wizard, you will only have to enable MailTips and message tracking.

To add the federated delegation namespace and enable MailTips and message tracking for the cloud-based organization relationship, use the following command in the Shell on the cloud-based organization.

	Copy Code
Set-OrganizationRelationship -Identity "To On-premises" -DomainNames "exchangedelegation.contoso.com","contoso.com" -MailTipsAccessEnabled $True -MailTipsAccessLevel All -DeliveryReportEnabled $True

The successful completion of the New Organization Relationship wizards will be your first indication that creating the organization relationships worked as expected. To further verify that the organization relationships are configured correctly, you can also run the following command in the Shell for both the on-premises and cloud-based organizations.

	Copy Code
Get-OrganizationRelationship | fl

Learn more at: Set-OrganizationRelationship and Configure Organization Relationship Properties

To verify that both public folder replicas have replicated to the hybrid server, you can confirm that the public folder item count is the same for both replicas. To display the public folder item count for the Exchange 2003 replicas created on the hybrid server, run the following command using the Shell on the hybrid server:

	Copy Code
Get-PublicFolderStatistics "path to the OU=EXTERNAL (FYDIBOHF25SPDLT) or OU=Exchange Administrative Group (FYDIBOHF23SPDLT) replica"| fl

Learn more at: Controlling Exchange Server 2003 Public Folder Replication

Having problems? Ask for help in the Office 365 forums. To access the forums, you'll need to sign in using an account that's granted administrator access to your cloud-based service. Visit the forums at: Office 365 Forums