Skip to content

Conversation

matsimon
Copy link
Contributor

According to 4Me's documentation they do support DELETE operations so no need to mention that as a limitation (anymore).

See:

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
@American-Dipper
Copy link
Contributor

@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 #sign-off comment to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"

@MicrosoftDocs/public-repo-pr-review-team

learn-build-service-prod bot pushed a commit that referenced this pull request Dec 1, 2023
Update directory-delete-howto.md
@CelesteDG
Copy link
Collaborator

CelesteDG commented Dec 4, 2023

Thank you, @American-Dipper
Reassigning this to @v-hgampala to review with the SaaS tutorials team and make the necessary updates.

@v-hgampala
Copy link
Contributor

@v-missam, can you please review and update the document as per the request?
cc: @twimmers

@v-hgampala
Copy link
Contributor

@twimmers, will you please confirm me the change so, we'll update the document as per the request?

@v-missam
Copy link
Contributor

@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.

@Harshita-130901
Copy link
Contributor

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.
#please-close

@matsimon
Copy link
Contributor Author

@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.

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 :-)

@matsimon matsimon deleted the patch-1 branch December 14, 2023 11:05
learn-build-service-prod bot pushed a commit that referenced this pull request Jan 12, 2024
Tests adding script in code tags.
learn-build-service-prod bot pushed a commit that referenced this pull request Feb 8, 2024
learn-build-service-prod bot pushed a commit that referenced this pull request Mar 31, 2024
Update copilot-entra-risky-user-summarization.md
learn-build-service-prod bot pushed a commit that referenced this pull request Apr 16, 2024
Update entitlement-management-roles.md
learn-build-service-prod bot pushed a commit that referenced this pull request Apr 22, 2024
Update how-to-manage-groups.yml
learn-build-service-prod bot pushed a commit that referenced this pull request Apr 22, 2024
Update how-to-configure-web-content-filtering.md
learn-build-service-prod bot pushed a commit that referenced this pull request May 21, 2024
Court72 pushed a commit that referenced this pull request Jul 15, 2024
learn-build-service-prod bot pushed a commit that referenced this pull request Jul 29, 2024
learn-build-service-prod bot pushed a commit that referenced this pull request Dec 12, 2024
Update managed-policies.md
learn-build-service-prod bot pushed a commit that referenced this pull request Dec 19, 2024
edited image
ttorble pushed a commit that referenced this pull request Feb 7, 2025
Update access-reviews-downloadable-review-history.md
learn-build-service-prod bot pushed a commit that referenced this pull request Feb 26, 2025
Update how-to-universal-tenant-restrictions.md
v-dirichards pushed a commit that referenced this pull request Mar 5, 2025
v-dirichards pushed a commit that referenced this pull request Apr 16, 2025
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
learn-build-service-prod bot pushed a commit that referenced this pull request Apr 29, 2025
Add zone pivots and option for Graph PowerShell
learn-build-service-prod bot pushed a commit that referenced this pull request May 21, 2025
[EXID] Update author metadata | Pull request #1
secherka added a commit to secherka/entra-docs that referenced this pull request Sep 22, 2025
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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants