# Deprovisioning with New Azure AD and SCIM

**URL:** <https://community.auth0.com/t/deprovisioning-with-new-azure-ad-and-scim/195502>\
**Category:** Get Help\
**Tags:** azure-ad-enterprise-connection, connections\
**Created:** [December 15, 2025, 5:16am UTC](https://community.auth0.com/t/deprovisioning-with-new-azure-ad-and-scim/195502 "2025-12-15T05:16:16Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![swarner1033](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/swarner1033/32/77621_2.png) [@swarner1033](https://community.auth0.com/u/swarner1033)\
**Post date:** [December 15, 2025, 5:16am UTC](https://community.auth0.com/t/deprovisioning-with-new-azure-ad-and-scim/195502/1 "2025-12-15T05:16:16Z")

</div>

I’ve set up 2 seperate Enterprise Applications in EntraID, one for Azure OIDC and one for SCIM as per [Inbound SCIM for New Azure AD Connections](https://auth0.com/docs/authenticate/protocols/scim/inbound-scim-for-new-azure-ad-connections)

If the user is removed from the SCIM app they’ll no longer have a role in my app but they’ll still have access through OIDC. Is there a way to couple these two processes, or do I just really on the user being authenticated but not authorised? The deprovisioned users will always hang around in my Auth0 tenant right as OIDC has no way to remove users?

---

<div class="post-metadata">

**Author:** ![gerald.czifra](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/gerald.czifra/32/75301_2.png) [@gerald.czifra](https://community.auth0.com/u/gerald.czifra)\
**Post date:** [December 16, 2025, 12:27am UTC](https://community.auth0.com/t/deprovisioning-with-new-azure-ad-and-scim/195502/3 "2025-12-16T00:27:14Z")

</div>

Hi @swarner1033

Thank you for reaching out to us!

Reading through your use-case, I would advise to rely on SCIM provisioning for blocking/deactivating users in Auth0 and removing their access, which should prove as a reliable method of managing the user’s lifecycle.

This can be achieved by using the [Blocked attribute behavior](https://auth0.com/docs/authenticate/protocols/scim/configure-inbound-scim#:~:text=Blocked%20attribute%20behavior). When the SCIM **active** attribute is mapped to the **blocked** attribute in Auth0 and contains a value of either true or false, Auth0 will reverse the value and set it to the user’s blocked attribute. If the **active** attribute is set to false, then the Auth0’s user attributed **blocked** will be set as true. This should prevent the user from logging in and having access.

If you happen to encounter issues along the way, please take a moment to read through our documentation on [Blocked Users in Azure AD are not Blocked in Auth0 when Using SCIM](https://support.auth0.com/center/s/article/Blocked-users-in-Azure-AD-do-not-get-blocked-in-Auth0-when-using-SCIM), which covers a know issue for this flow to not work as expected.

Hope this helped, let me know if this worked for you!

Best regards,  
Gerald

---

<div class="post-metadata">

**Author:** ![swarner1033](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/swarner1033/32/77621_2.png) [@swarner1033](https://community.auth0.com/u/swarner1033)\
**Post date:** [December 16, 2025, 2:08am UTC](https://community.auth0.com/t/deprovisioning-with-new-azure-ad-and-scim/195502/4 "2025-12-16T02:08:40Z")

</div>

Just to clarify: this means the user will still exist in the tenant, they’re just blocked?

---

<div class="post-metadata">

**Author:** ![gerald.czifra](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/gerald.czifra/32/75301_2.png) [@gerald.czifra](https://community.auth0.com/u/gerald.czifra)\
**Post date:** [December 17, 2025, 9:53pm UTC](https://community.auth0.com/t/deprovisioning-with-new-azure-ad-and-scim/195502/5 "2025-12-17T21:53:10Z")

</div>

Hi @swarner1033

That is correct, the users will remain on your tenant in a blocked state. With further implementation, it would be possible to make a call to the [Delete a User](https://auth0.com/docs/api/management/v2/users/delete-users-by-id) endpoint and apply logic in order to delete users blocked for X amount of time.

Hope this helped!  
Gerald

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [December 31, 2025, 9:54pm UTC](https://community.auth0.com/t/deprovisioning-with-new-azure-ad-and-scim/195502/6 "2025-12-31T21:54:11Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
