Configure federated sharing
Applies to: Exchange Server 2013
Topic Last Modified: 2014-02-15
With federated sharing in Exchange Server 2013, users can share information with recipients in external federated organizations. This includes sharing their free/busy (also known as calendar availability) information for scheduling purposes or, depending on the nature of the business relationship, sharing more detailed calendar information. To learn more about federation sharing, see Sharing.
|This feature of Exchange Server 2013 isn’t fully compatible with Office 365 operated by 21Vianet in China and some feature limitations may apply. For more information, see Learn about Office 365 operated by 21Vianet.|
Estimated time to complete this task: 1 hour.
Procedures in this topic require specific permissions. See each procedure for its permissions information.
For information about keyboard shortcuts that may apply to the procedures in this topic, see Keyboard shortcuts in the Exchange admin center.
A federation trust establishes a trust relationship between an Exchange 2013 organization and the Windows Azure AD authentication system and is a requirement for federated sharing.
For detailed instructions, see Configure a federation trust.
An organization relationship enables users in your Exchange organization to share calendar free/busy information as part of federated sharing with other federated Exchange organizations. Federated sharing can be configured between two federated Exchange 2013 organizations or between a federated Exchange 2013 organization and federated Exchange 2010 organizations.
For detailed instructions, see Create an organization relationship.
Sharing policies enable user-established, people-to-people sharing of calendar information with different types of external users. They support the sharing of calendar and contact information with external federated organizations, external non-federated organizations, and individuals with Internet access. If you don’t need to configure people-to-people or contact sharing (organization-level sharing only), you don’t need to configure a sharing policy.
For detailed instructions, see Create a sharing policy.
You need to add an alias canonical name (CNAME) resource record to your public-facing DNS. The new CNAME record should point to an Internet-facing Exchange 2013 Client Access server that's running the Autodiscover service.
For detailed instructions about how to add CNAME records, see the host service for your public DNS records. Typically this is an Internet-based service that may also host your domain website.