Engineering sprint · Automation

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.

2–3
weeks
Depending on scope
Runbooks
Azure Automation
With a log
PowerShell

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.

Essentials
Fixed price on request
Up to 25 users
The two most important processes as runbooks: joiner and leaver, started by your IT team.
Deliverables
  • 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
Corporate
Fixed price on request
Up to 500 users
Joiners and leavers requested by form, with approval and assignment by department and role.
Deliverables
  • 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
Enterprise
Fixed price on request
500+ users
Lifecycle automation with an HR system as the source, hybrid environments and Entra ID Governance. Duration depends on scope.
Deliverables
  • 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

Benefits for your business

The ROI for management.

Joiners without manual work
On the first day, account, license, groups and mailbox are ready. IT fills in one request instead of setting each option by hand.
Leavers in a fixed order
Leaving always follows the same order: block sign-in, end sessions, convert the mailbox, release the license. No step is forgotten.
Licenses come back
The license is released when someone leaves. Scheduled reports show unused licenses and inactive accounts.
Traceable
Every run is logged: who requested it, what changed and when. That helps with audits and follow-up questions.

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.

Ready for automation?

By submitting, you agree to the privacy policy.

You will receive a reply by email within one business day. If your scope is already clear, we send the fixed-price quote right away.