Closed paulfedyk-phg closed 1 year ago
@paulfedyk-phg Thanks for your feedback! We will investigate and update as appropriate.
@paulfedyk-phg
Thank you for bringing this to our attention!! 1, if the output of your GET request is missing 'SyncAgentCompitabilityKey' and 'SyncAgentADContainer', you can leave them out when posting "SkipOutOfScopeDeletions".
2, the "SkipOutOfScopeDeletions" flag is used to override the default behavior of de-provisioning out of scope users in Azure Active Directory. By default, the Azure AD provisioning engine soft deletes or disables users that go out of scope. However, for certain scenarios like Workday to AD User Inbound Provisioning, this behavior may not be the expected and you may want to override this default behavior1.
This flag is set at the Provisioning App level and can be configured using the Graph API1. It is not related to guest access.
@paulfedyk-phg We are going to close this thread.if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.
Hello,
My Graph Explorer output is missing 'SyncAgentCompitabilityKey' and 'SyncAgentADContainer' when I run GET. Should I leave them out when posting "SkipOutOfScopeDeletions"?
Also, would this cover all out of scope accounts including guest access?
Thanks, Paul
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.