Federation trusts give Exchange 2010 administrators an easy way to share calendar and contact information across...
organizational boundaries, but there are various requirements be aware of before using this feature.
When two Exchange-based companies form a strategic partnership, they may want to share calendaring and contact information.
Companies have been sharing information this way for quite some time, but setting it up is cumbersome. The process involves Active Directory-level trusts, opening firewall ports and in some cases, public folder replication.
The most common collaboration method involves organizational relationships, which allows calendar sharing across organizational boundaries. You can choose to share free/busy information one time only, or you can include subject and location information. There is also an option to disable free/busy access.
Additionally, users can create sharing policies. Sharing policies let internal users share calendar and contact information with users in an external organization.
Here are some requirements and best practices for creating a federation trust between two organizations.
Exchange 2010 federated trust requirements
- Client access server. Both organizations must have at least one Exchange 2010 client access server (CAS) in place. Although it is preferred for all Exchange servers to be running Exchange 2010, it is not required.
Users running Outlook 2007 can’t manually specify the SMTP address of external recipients when they want to access availability information. They can only access the information by picking the external recipient from the global address list (GAL). This also requires GAL synchronization with the external Exchange organization, which is another issue altogether.
- Microsoft Federation Gateway. The federation trust is not established directly between the two Exchange organizations. Instead, each organization must establish a trust with the Microsoft Federation Gateway. The Microsoft Federation Gateway is a cloud service that acts as a trust broker between organizations.
- DNS requirements. When an organization establishes a trust with the Microsoft Federation Gateway, it must prove that it owns the domain. To establish this proof, Microsoft provides each organization with an AppID. When an organization receives the ID number, it creates a special TXT record on its DNS server and includes the AppID. Microsoft uses this DNS record for verification purposes.
- The Organization Identifier. The Exchange organization must also establish an Organization Identifier (OrgID). The OrgID is a list of accepted domains that is e enabled for federation. Larger organizations that use a complex domain structure may decide they only want to enable federation for certain domains. Domains will not be federated unless they’re included in the AppID.
- The federated delegation namespace. Regardless of whether an organization is federating some or all of its domains, it must create a special namespace for federated delegation. This namespace must be different from any of the accepted domains. Microsoft recommends using ExchangeDelegation as the federated delegation name. For example, if an organization’s primary accepted domain name is Contoso.com, then the federated delegation namespace would be ExchangeDelegation.contoso.com.
Certificate requirements. The Exchange server that the federation trust is created from must be provisioned with either a self-signed certificate or an X.509 certificate. Microsoft normally advises against self-signed certificates in production environments, but a self-signed certificate is actually preferred over an external CA certificate when it comes to setting up federated trusts.
Microsoft doesn’t elaborate on this recommendation, but it probably has to do with the complexities of managing certificates from external CAs. Regardless of which type of certificate you use, the certificate is only used for signing and encrypting delegation tokens. Additionally, the certificate is automatically replicated to any additional Exchange servers that need it.
ABOUT THE AUTHOR:
Brien Posey is an eight-time Microsoft MVP with two decades of IT experience. Before becoming a freelance technical writer, Brien worked as a CIO for a national chain of hospitals and healthcare facilities. He has also served as a network administrator for some of the nation’s largest insurance companies and for the Department of Defense at Fort Knox.