Microsoft: User Offboarding Crate
Last updated
Was this helpful?
Last updated
Was this helpful?
Our Microsoft: User Offboarding Crate streamlines the offboarding process for users within an organization, for time savings and increased efficiency. The automation is triggered via a form submission, allowing designated personnel to initiate the offboarding tasks.
Detailed ticketing: Automation logging steps that are done throughout the offboarding process are documented by logging entries to the ticket, via a single note, making it easier to tell where an issue occurred and what steps were performed.
Efficiency: Streamline the user offboarding process by increasing time savings and decreasing the potential for user error.
Security: Ensure that necessary offboarding steps are performed when an account is terminated.
This Crate does not handle On-Prem Exchange and will only handle Exchange functionality via Office 365.
Before unpacking this Crate, you'll need to successfully set up the Microsoft Graph integration, now a part of our .
Azure AD Only
Hybrid On-Prem and Azure AD: Synced
Hybrid On-Prem and Azure AD: No Sync
On-Prem Only
Navigate to Crates > Crate Marketplace in the Rewst platform.
Search for Microsoft: User Offboarding
.
Click Unpack Crate.
Click Continue.
Click Unpack.
Navigate to Automations > Workflows in the Rewst platform
Search for Microsoft: User Offboarding
.
Click into the workflow.
Click View Direct URLs.
Select the company you'd like to use to test the workflow. Copy the URL and paste it into a new window.
Fill out the form as appropriate for the company and user you are offboarding. Make sure to click Submit at the end of the form.
Click into the results to see the execution results with successes and failures, if there are any.
agent_smith_is_installed
automation_task_new_user_time
automation_task_offboard_user_time
azure_iothub_name
azure_iothub_resource_group
azure_iothub_subscription_id
cwControl_CompanyName
cw_automate_client_id
cw_control_session_group_override
cw_manage_company_id
datto_company_id
datto_note_type
datto_rmm_site_id
default_psa
default_rmm
failure_email
freshdesk_company_id
halo_psa_client_id
halo_ticket_site_name
immybot_tenant_id
kaseya_bms_account_id
kaseya_vsa_10_scriptid
kaseya_vsa_org_id
kaseya_vsa_x_org_id
nable_customer_id
nable_device_filter_id
nable_rewst_powershell_script_id
new_user_approval_email
ninja_org_id
ninja_run_as_user
no_azure_ad
no_ticket_time
onprem_no_adsync
preferred_domain_controller
primary_domain_controller
primary_identity_provider
priority
psa_alert_ticket_type
psa_all_notes_internal
psa_datto_default_issue_type
psa_datto_default_sub_issue_type
psa_datto_default_ticket_category
psa_datto_default_ticket_type
psa_default_agreement_name
psa_default_board_id
psa_default_tech_id
psa_default_tech_workrole
psa_default_tech_worktype
psa_default_ticket_impact
psa_default_ticket_priority
psa_default_ticket_source
psa_default_ticket_status
psa_default_ticket_urgency
psa_halo_cab_id
psa_halo_cab_type
psa_halo_ticket_outcome_completed_task
psa_new_user_ticket_subtype
psa_new_user_ticket_type
psa_no_ticket_time
psa_offboarding_user_ticket_item
psa_offboarding_user_ticket_subtype
psa_offboarding_user_ticket_type
psa_ticket_status_completed_task
psa_ticket_status_waiting_input
require_approval_for_offboarding_users
rmm_preferred_adconnect_server
servicenow_account_id
time_entry_ticket_status
Click on the Crate tile to begin unpacking.
Click to navigate to the trigger.
Once the form is submitted, the workflow will begin to run. To view the results, click in the workflow editor page.
For information specific to these org variables please review our guidance organization variables .
If you haven't done so already, it's recommended that you run the , which will help you set org variables that are relevant to you and your customer's environments.