Required confirmations before submitting
Issue Description
Hi,
We're using the CIPP API to disable compromised users.
When attempting to disable an AD-synced user, we receive the following response:
Failed to set sign-in state ... WARNING: User ... is AD Sync enabled. Please enable/disable in the local AD.
Our AD synchronization setup is configured so that the account status can be synchronized/written both ways, so we don't need to manually disable the user in the local AD first.
Is there a way to disable an AD-synced user through CIPP/API without this check blocking the operation? Alternatively, is there another endpoint or setting intended for this scenario?
Environment Type
Sponsored (paying) user
Front End Version
API
Back End Version
API
Relevant Logs / Stack Trace
Required confirmations before submitting
Issue Description
Hi,
We're using the CIPP API to disable compromised users.
When attempting to disable an AD-synced user, we receive the following response:
Failed to set sign-in state ... WARNING: User ... is AD Sync enabled. Please enable/disable in the local AD.
Our AD synchronization setup is configured so that the account status can be synchronized/written both ways, so we don't need to manually disable the user in the local AD first.
Is there a way to disable an AD-synced user through CIPP/API without this check blocking the operation? Alternatively, is there another endpoint or setting intended for this scenario?
Environment Type
Sponsored (paying) user
Front End Version
API
Back End Version
API
Relevant Logs / Stack Trace