If you are unsure about approaching this issue please call our helpdesk as you can irreversibly damage your PC if you are not careful
After you have prepared your environment for single sign-on, you will need to set up a new on-premises STS infrastructure to provide your local and remote Active Directory users with single sign-on access to the cloud service. If you currently have an STS in your production environment, you can use it for single sign-on deployment rather than setting up a new infrastructure as long as it is supported by Windows Azure AD.
Currently, Windows Azure AD supports either of the following security token services:
- Active Directory Federation Services (AD FS)
For more information about how to get started with setting up an AD FS STS, follow the steps provided in Checklist: Use AD FS to implement and manage single sign-on.
- Shibboleth Identity Provider
For more information about how to get started with setting up a Shibboleth STS, follow the steps provided in Use Shibboleth Identity Provider to implement single sign-on.
- Other third-party identity providers
For more information about how to get started with setting up third-party identity providers for single sign-on, see Use third-party identity providers to implement single sign-on.