I need to federate a SAML-P 2.0 Identity Provider with Azure Active Directory so I can pass a federated claim back to ACS and then to my application. This is appears to be fully supported by looking at the commands on the Oracle Identity Federation (OIF) Server website and other MSDN Azure sources. My problem is that the client is already using Office 365 and ADFS integration on their side. They do not want to use ADFS for SSO integration with our application. The problem is that when I enter a userid for logging in at the login.windows.net page, it redirects to their ADFS SSO provider instead of the integration I setup with their OIF identity provider.
How can I work with this? It looks like this used to be supported on ACS, but it looks like ACS is no longer supported by Microsoft. (Powershell cmd-lets and other tools have been pulled from Codeplex.) I need to have a UPN domain suffix that can be setup for multiple domains. I would think that the service should know this based on my relying party, no?
Joseph Nielsen
This is the article I used to setup the SAML 2.0 federation with Azure AD.