Skip to main content

Why Can't I Log In to AXP via Single Sign-On (SSO)?

If you're unable to log in to AXP using Single Sign-On (SSO) and see an error message from Microsoft, this guide explains the most common cause and what to do. Relevant topics: SSO login error, Microsoft failed, AXP access denied, identity provider error.

Summary: When SSO login fails after allowing 3rd party to continue, it's usually because your account hasn't been granted access in your organisation's identity provider (e.g. Microsoft Azure AD, Okta, or another SSO system). This isn't something AXP can fix — your IT team needs to grant you access on their side.

Permissions Required: No special role required — this applies to all AXP users logging in via SSO.


Steps to follow

  1. Check the error message on your screen. It will typically come from your organisation's identity provider (e.g. a Microsoft login screen), and may say something like:

    "Your administrator has configured the application Alliants Experience Platform to block users unless they are specifically granted access to the application.

    Please contact your administrator to assign access to this application"

    This confirms the issue is with your organisation's SSO permissions — not your AXP account itself.

  2. Contact your property's IT manager or the team that manages your organisation's SSO system, and ask them to grant your account access to AXP with a screenshot of the error you are seeing.

  3. Once your IT team confirms they've made the change, try logging in to AXP again at alliants.app via SSO.

  4. If you're still unable to log in after your IT team has made the change, contact your AXP support team and let them know the steps already taken.


Common Questions

Q: Why am I seeing an error from my organisation's login screen?

A: AXP uses your organisation's Single Sign-On (SSO) system to verify your identity. If your account hasn't been granted permission to access AXP within that system, the login will fail. This is controlled entirely by your organisation's IT team, not by AXP.

Q: I've been using AXP before — why is this happening now?

A: This can happen if your organisation has made changes to their SSO configuration, such as reorganising teams, offboarding / onboarding users, or updating access permissions. Even if you had access previously, your account may have been removed or moved to a different group.

Q: Who do I contact to fix this?

A: Reach out to your property's IT manager or whoever manages your organisation's SSO or identity provider. Ask them to confirm that your account has been given access to AXP.

Q: Can AXP support fix this for me?

A: No — access permissions within your organisation's SSO system are managed entirely by your IT team. AXP support cannot make changes to your company's identity provider. Your IT admin is the right person to contact. If your IT team needs further technical details about how AXP integrates with your SSO, they can liaise directly with AXP support.

Did this answer your question?