Automate joiners
and leavers
Joiner and leaver processes often run on checklists and manual work. We implement them as runbooks in Azure Automation, and from the Corporate package department changes too: account, licenses, groups and mailbox by fixed rules, with a log of every run and a documented handover.
Scope & packages
Three packages by tenant size and complexity. You receive a binding fixed-price quote for your scope. User counts and packages are a guide. The binding scope also depends on the existing architecture, number of sites, hybrid scenarios, security requirements, integrations and technical special cases.
- Joiner runbook: account, license and groups from a template
- Leaver runbook: block sign-in, end sessions, release the license
- Convert the mailbox to a shared mailbox on leaving, forwarding as specified
- Azure Automation with a managed identity and minimal permissions for Graph and Exchange Online
- A log of every run
- Everything in Essentials
- Request by form or list, approved by HR or the line manager
- Groups and licenses by department and role (group-based licensing)
- Mover runbook: remove old permissions, assign new ones
- Scheduled reports: inactive accounts, unused licenses, guest accounts
- Notifications to IT and line managers
- Everything in Corporate
- HR system as the source (API-driven provisioning in Entra ID)
- Hybrid environments: runbooks with a Hybrid Runbook Worker for Active Directory
- Lifecycle Workflows and Access Reviews (Entra ID Governance, separate license)
- Runbooks in Git with a deployment pipeline
Technical details
Details for technical validation.
Platform (Azure Automation & Managed Identity)
The runbooks run in an Azure Automation account in your subscription. They sign in with a managed identity, without stored passwords or client secrets.
- Automation account with a system-assigned managed identity
- Permissions for Microsoft Graph and Exchange Online following least privilege
- PowerShell 7 runtime with the Microsoft Graph PowerShell SDK
Joiner
A few details become a finished account. Naming rules, licenses and groups follow a template per department or role.
- User provisioning with naming convention & UPN check
- Group-based licensing & assignment to teams and distribution lists
- Notification to IT as soon as the account is ready
Leaver
Leaving always follows the same order, so no step is forgotten.
- Sign-in block & revoke sessions
- Shared mailbox conversion & forwarding
- License release & group clean-up
Operations (logging & handover)
Every run can be traced. Failed runs raise an alert, and your IT team can adjust the runbooks themselves using the documentation.
- Job logs in Log Analytics, alert on failed runbooks
- Documentation per runbook: trigger, parameters, permissions
- Test run with test accounts before production release
Benefits for your business
The ROI for management.
Frequently asked questions
What needs to be in place before the sprint starts?
A Microsoft 365 tenant with Entra ID P1 (included in Business Premium), an Azure subscription for the Automation account and an admin account for the setup. Microsoft bills the usage costs of Azure Automation and Log Analytics directly to you.
How are the runbooks triggered?
In the Essentials package your IT team starts the runbook with the required details. From Corporate, the request comes from a form or list and runs automatically after approval. In the Enterprise package the HR system can be the source.
We still have an on-premises Active Directory. Does it still work?
Yes, from the Enterprise package. For accounts created in the on-premises Active Directory, the runbooks run through a Hybrid Runbook Worker in your network.
How secure is the automation itself?
The runbooks use a managed identity without stored passwords. It only receives the permissions for Graph and Exchange Online that the agreed processes need. We test every process with test accounts before release.
How much effort is needed on our side?
Plan for 6–8 hours: describe the current processes and templates per department, provide test accounts, review the test runs and sign off.
Who maintains the runbooks after the sprint?
Your IT team or your IT partner, using our documentation per runbook. We automate further processes on request with a separate fixed-price quote. For ongoing development we can agree regular reviews, improvements or an engineering allowance; services and intervals are quoted individually.