mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-25 16:26:09 +03:00
[GH-ISSUE #57] Feature Request: Offboarding user Wizard #36
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#36
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 @KelvinTegelaar on GitHub (Oct 18, 2021).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/57
Originally assigned to: @KelvinTegelaar on GitHub.
Describe the solution you'd like
I'd like to be able to have engineers run a Wizard to offboard a user, with checkboxes to convert a user to a shared mailbox, remove the licenses, block sign-in, and set an OoO.
Describe alternatives you've considered
manually doing it, blergh
@dbeta commented on GitHub (Oct 18, 2021):
You read my mind. To give details of our process:
We don't do self service password resets, but that should probably be disabled as well.
Useful feedback for the technician:
@wezzydev commented on GitHub (Oct 18, 2021):
I have created an off-boarding Powershell script that does the following for Azure. I have a separate one for 365 only (Just so you can get some ideas)
@dbeta commented on GitHub (Oct 18, 2021):
Good call on the GAL, totally forgot that step. If there is some way to break the immutable ID so that syncing stops on that user, without the risk of automatic re-pairing, that would be nice. That was the relationship between the AD account and the AAD account would be permanently broke and I don't have to worry about an AD action causing an AAD reaction.
This is important since the process is obviously going to be disconnected between AAD and AD, since I don't see any AD interactions to be in-scope of CIPP.
@KelvinTegelaar commented on GitHub (Oct 23, 2021):
Almost done on this, perfecting some API error handling. :)
@KelvinTegelaar commented on GitHub (Oct 25, 2021):
Added in dev build