mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-25 16:26:09 +03:00
[GH-ISSUE #1425] Issue offboarding groups #790
Labels
No labels
API
Feature
NotABug
NotABug
Planned
Sponsor Priority
Sponsor Priority
bug
documentation
duplicate
enhancement
needs more info
no-activity
no-priority
not-assigned
pull-request
react-conversion
react-conversion
roadmap
security
stale
unconfirmed-by-user
unconfirmed-by-user
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/CIPP#790
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @BNWEIN on GitHub (Mar 20, 2023).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/1425
Originally assigned to: @BNWEIN on GitHub.
Description
Offboarding wizard fails to remove users from M365 groups. I believe this is because for mail enabled groups it tries to use an exo request.
I think it needs to look if the group is "unified" and then use a different command to remove the user from those groups.
I tried to fix this my self and had a brain melt!
Environment data
@github-actions[bot] commented on GitHub (Mar 20, 2023):
Thank you for creating a bug. Please make sure your bug is indeed a unique case by checking current and past issues, and reading the complete documentation at https://kelvintegelaar.github.io/CIPP
If your bug is a known documentation issue, it will be closed without notice by a contributor. To confirm that this is not a bug found in the documentation, please copy and paste the following comment: "I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.".
Without confirming, your report will be closed in 24 hours. If you'd like this bug to be assigned to you, please comment "I would like to work on this please!".
@BNWEIN commented on GitHub (Mar 20, 2023):
I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.
@BNWEIN commented on GitHub (Mar 22, 2023):
I would like to work on this please!
@github-actions[bot] commented on GitHub (Mar 22, 2023):
Great! I assigned you (@BNWEIN) to the issue. Have fun working on it!
@BNWEIN commented on GitHub (Mar 22, 2023):
Fixed in PR #290