-
Notifications
You must be signed in to change notification settings - Fork 798
Update 4me-provisioning-tutorial.md: Remove DELETE limitation #1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
According to 4Me's documentation they do support DELETE operations so no need to mention that as a limitation (anymore). See: * https://developer.4me.com/v1/scim/users/#delete-a-user * https://developer.4me.com/v1/scim/groups/#delete-a-group
@CelesteDG - can you review the proposed changes? Or tell use whom to direct this to? The author appears to not be available. IMPORTANT: When the changes are ready for publication, add a #label:"aq-pr-triaged" @MicrosoftDocs/public-repo-pr-review-team |
Update directory-delete-howto.md
Thank you, @American-Dipper |
@twimmers, will you please confirm me the change so, we'll update the document as per the request? |
@matsimon @v-hgampala - 4me doesn’t support HARD DELETE of Users. SCIM users are never really deleted in 4me, instead the "active" attribute of the SCIM user will be set to "false " and the related 4me person's record will be disabled. This is specified in the link https://developer.4me.com/v1/scim/users/#delete-a-user . So, we will update our tutorial with the above statement. |
We created a separate PR for these changes in our private repo for better content validation. So, the changes will be live in 1 to 2 business days. |
Thanks for highlighting that fine, yet important detail. When I was debugging a stalled SCIM sync at that moment, the current doc first lead me down the wrong track as it indicated a "doesn't support DELETE at all". Whereas it actually means "we do support DELETE, but actually won't actually delete users". I'll welcome that update on the private branch whenever it hits the public docs :-) |
Tests adding script in code tags.
Updating images for Entra branding
Update copilot-entra-risky-user-summarization.md
Update entitlement-management-roles.md
Update how-to-manage-groups.yml
Update how-to-configure-web-content-filtering.md
Update jwt-claims-customization.md
Various minor updates
Update managed-policies.md
edited image
Update access-reviews-downloadable-review-history.md
Update how-to-universal-tenant-restrictions.md
update: add missing md file extension
Update lifebalance-program-oidc-tutorial.md There were some more changes left behind, due to a branch difference Big thanks out to the review team for looking over this a second time
Add zone pivots and option for Graph PowerShell
[EXID] Update author metadata | Pull request #1
Updating the notes to make it clear that MicrosoftDocs#1, #2 and so on should not be added to Reply URI when configuring multi instancing.
According to 4Me's documentation they do support DELETE operations so no need to mention that as a limitation (anymore).
See: