Applies to: Office 365 for enterprises, Live@edu
Topic last modified: 2011-12-19
Federated delegation, also known as federated sharing, uses the Microsoft Federation Gateway, a cloud-based identity service offered by Microsoft, as the trust broker between your on-premises Exchange Server 2010 organisation and your cloud-based email organisation.
With federated delegation, end users in one cloud-based organisation can share information with end users in another cloud-based organisation. For example, after you have enabled and configured federated delegation, users in one organisation can view the free/busy information for users in the cloud-based organisation of a business partner, if the partner has also enabled and configured federated delegation.
The infrastructure of the cloud-based email service is already federated with Microsoft Federation Gateway. All you need to do to enable federated delegation is create a new organisational relationship with another cloud-based email organisation.
By default, calendar sharing between users in other organisations that are federated with Microsoft Federation Gateway is enabled. This means that users with mailboxes in your cloud-based email service can create individual calendar-sharing invitations to users in other organisations who are federated with Microsoft Federation Gateway. To disable this default policy, see Disable a Sharing Policy.
By default, free/busy access isn't enabled between organisations that are federated with Microsoft Federation Gateway. This topic explains how to enable free/busy access with another cloud-based email organisation.
Because federated delegation uses the Autodiscover information in your domain to configure the federated relationship, you must make sure that the CNAME Autodiscover records for both organisations for which you are enabling federated delegation are configured in DNS. See Use a CNAME Record to Enable Outlook to Connect.
You use Windows PowerShell to configure federated delegation.
To enable free/busy sharing between two cloud-based organisations, run the following command:
Get-FederationInformation -DomainName <the other cloud-based organization> | New-OrganizationRelationship -Name <the other tenant domain> -FreeBusyAccessEnabled $true -FreeBusyAccessLevel LimitedDetails
Here's an example of what the command would look like in the Contoso scenario, where the administrator for the Contoso organisation configures an organisational relationship with Fabrikam College:
Get-FederationInformation -DomainName fabrikam.edu | New-OrganizationRelationship -Name Fabrikam -FreeBusyAccessEnabled $true -FreeBusyAccessLevel LimitedDetails
To learn how to configure federated delegation between your on-premises organisation and your cloud-based email organisation, see Understanding Federated Delegation and the Exchange Calendar Sharing FAQ.
For an example of implementation of a cross-premises federated delegation scenario, see Set up Federated Free/Busy and Calendar Sharing between Exchange 2010 SP1 and Outlook Live.
|The third-party Web site information in this topic is provided to help you find the technical information you need. The URLs are subject to change without notice.|