Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Gettign Error: blockedByReason=Blocked%20by%20SCIM&blockedBy

Arpit Gupta
March 26, 2026

Setup SAML SSO login from IDP to Atlassian from teo domain directory from IDP.

But when login from the user giving error: https://id.atlassian.com/login/inactive?blockedByReason=Blocked%20by%20SCIM&blockedByType=orgAdmin

1 answer

0 votes
Arkadiusz Wroblewski
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
March 26, 2026

Hello @ Arpit Gupta 

this error points to SCIM provisioning, not to SAML itself.

blockedByReason=Blocked by SCIM means the user is still being controlled by the IdP sync, so I would check the user there first:

- confirm the account is still active
- confirm the user is still assigned to the Atlassian app / provisioning scope
- then let SCIM sync again

I would also check the Atlassian Admin audit log to see whether the user was deactivated or removed by provisioning.

The key point is:
if the account is still SCIM-managed, the fix usually has to happen in the IdP, not in Jira.

If the user is no longer SCIM-managed, then you can handle it in Managed accounts in Atlassian Admin.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
ENTERPRISE
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events