After trying to get SAML single sign-on to work with Azure AD I can't login anymore

[Tom Horton]

I was trying to configure Azure AD and Atlassian cloud for SAML single sign-on and I thought it configured correctly. But I may have configured two tenants.

When I try to login as an Atlassian administrator I get the following error:

Request Id: daa2afe1-b25c-458f-8def-de39110a0300

Correlation Id: 534761d7-b271-4245-b857-a2fcdfda7877

Timestamp: 2020-04-07T00:25:32Z

Message: AADSTS700016: Application with identifier 'https://auth.atlassian.com/saml/ceffa91e-a55e-4ab4-b185-60119714b336' was not found in the directory 'c8a43e29-f09d-477a-8567-335b11f6596a'. This can happen if the application has not been installed by the administrator of the tenant or consented to by any user in the tenant. You may have sent your authentication request to the wrong tenant.

I can't login to Support to request help, so I'm hoping a support person in the community will help me out. I need to get this resolved as soon as possible since none of our users can login.

Thanks!

[Dave Meyer · Accepted solution]

Hi @Jason Li Ting Chung ,

Only SAML SSO is supported with AD FS. Our SAML implementation supports just-in-time provisioning, but AD FS does not support user provisioning via the indstury-standard SCIM protocol. To set up user provisioning, you will need to connect AD to a cloud identity provider like Azure AD. See Microsoft's documentation here for details: https://docs.microsoft.com/en-us/azure/active-directory/app-provisioning/user-provisioning