Verify that you meet the following requirements before you import the connector:
An understanding of identity federation using the WS-Federation protocol.
For more information about WS-Federation, see the OASIS website or see Understanding WS-Federation in the Microsoft Developer Network Library.
A Microsoft Azure account.
A Windows Azure Access Control Service.
For more information, see How to Authenticate Web Users with Windows Azure Access Control Service.
Administrator access to the Azure account. An understanding of Azure and its account management tools are presumed.
An Azure user account for each user who wants to authenticate to Azure through the CloudAccess single sign-on service. The connector for Azure does not provision user accounts.
The location in the Azure administration console where you will configure the WS-Federation federation for CloudAccess.
When you configure the connector, the Federation Instructions provide the information that you will need to set up the federation in Azure for CloudAccess. This information includes the metadata; the field values to use; and other guidance.
The metadata file from the Windows Azure Access Control Service.
Login URL: The value found in the PassiveRequestorEndpoint field. For example:
https://ncssacs.accesscontrol.windows.net/v2/WS-Federation
EntityID: The value in the entityID field.
NOTE:Azure does not provide a logout URL for WS-Federation. Users who log in to Azure through CloudAccess must close their browser in order to log out.
If the connector for Office 365 is configured in the same domain, ensure that you configure WS-Federation as the federation protocol for the connector for Office 365.