I have a single Cloud Sync configuration syncing from on-premises AD to Entra ID. During testing I discovered that when a user falls out of sync scope and I evaluate them via Provision on Demand, their Entra account gets deleted.
I need to change the deprovisioning behavior so that out-of-scope users are made cloud-only instead of deleted.
Environment:
- Single Cloud Sync agent on one server
- AD to Entra provisioning job (AD2AADProvisioning)
- PHS enabled
- Scheduled sync currently disabled — still in testing
Question: Is there a supported way to configure deprovisioning behavior for a Cloud Sync AD→Entra job to leave accounts as cloud-only instead of deleting them when they fall out of scope?I have a single Cloud Sync configuration syncing from on-premises AD to Entra ID. During testing I discovered that when a user falls out of sync scope and I evaluate them via Provision on Demand, their Entra account gets deleted.
I need to change the deprovisioning behavior so that out-of-scope users are made cloud-only instead of deleted.
What I've already tried:
- Looking for the setting in the Cloud Sync UI — not present
-
SkipOutOfScopeDeletions — did not prevent deletion
- Checking job schema for deprovision settings — nothing returned
Environment:
- Single Cloud Sync agent on one server
- AD to Entra provisioning job (AD2AADProvisioning)
- PHS enabled
- Scheduled sync currently disabled — still in testing
Question:
Is there a supported way to configure deprovisioning behavior for a Cloud Sync AD→Entra job to leave accounts as cloud-only instead of deleting them when they fall out of scope?