Fixed quote after a free call

Microsoft 365 user onboarding and offboarding automation for MSPs

Starter and leaver requests touch accounts, licenses, groups, shared mailboxes, devices and line-of-business apps, and small steps get missed. We build a workflow that turns the client's request into a checklist from their role templates, prepares Microsoft 365 or Google Workspace changes for a technician to approve, revokes sign-in sessions and removes licenses for leavers, and records each step on the PSA ticket and in documentation. A typical build costs $1,000 to $2,500 per workflow and takes about four to five weeks.

The problem

Why starters and leavers slip through MSP checklists

A client's office manager emails on Friday afternoon that someone starts on Monday. The technician works from memory or an old checklist: account, license, groups, mailbox, MFA, laptop, the CRM, the finance app. Something is always missed, usually discovered when the new hire cannot open a shared folder.

Leavers are riskier. If access is not removed everywhere, a former employee keeps a working mailbox or a SaaS login. Joint guidance from CISA and partner agencies tells organisations to disable accounts that are no longer needed, yet offboarding is the step most often rushed.

What we build

What our Microsoft 365 onboarding and offboarding automation includes

Structured request form

A starter and leaver form for each client that asks for role, manager, dates, mailbox handling and devices up front.

Role-based checklists

The request becomes a checklist from the client's role templates in IT Glue, Hudu or a shared sheet.

Prepared tenant changes

Account creation, group membership and license assignment through Microsoft Graph or the Google Admin SDK, waiting for technician approval.

Leaver lockdown

On the leaving date: sign-in blocked, sessions revoked, licenses removed and mailbox converted or forwarded as the client chose.

Access outside the tenant

Line-of-business apps listed from documentation and tracked as tasks until a technician confirms removal.

Record and confirmation

Each step logged on the PSA ticket, documentation updated and a summary sent to the requester.

Who does what

Automation does the chasing, people make the calls.

Every step is marked: what runs on its own, what a member of staff reviews and what stays with a person who decides.
  1. 01 Automated

    Request submitted

    The client submits a starter or leaver form, or a ticket is matched to the form.

  2. 02 Automated

    Checklist built

    The role template becomes a checklist, and missing details are requested from the client.

  3. 03 Automated

    Changes prepared

    Account, group, license and mailbox changes are staged for approval.

  4. 04 Technician review

    Technician approves

    A technician reviews and approves the staged changes, which are then applied and logged.

  5. 05 Engineer or vCIO decides

    Privileged and data decisions

    Admin roles, data retention and handover are decided by a named engineer and the client.

How it behaves

How starter and leaver automation behaves

What each person sees and what runs in the background, including what happens when something goes wrong.

What the client sees

  • One form for starters and leavers that asks the right questions
  • A confirmation listing every step done
  • New hires who can sign in and open what they need on day one

What technicians see

  • A checklist built from the client's role template
  • Staged tenant changes to approve in one click
  • Open tasks for apps outside Microsoft 365

What the automation does

  • Builds the checklist and chases missing details
  • Applies approved changes through Microsoft Graph
  • Logs every step on the ticket and in documentation

Edge cases and fallbacks

Leaver date moved forward
The client updates the form and the lockdown reschedules; the technician is told.
Role template missing
The request goes to a technician to build one; nothing is guessed.
No license available
Flagged to the account manager to order before the start date.
Graph call fails
The step stays open on the checklist and the technician is alerted.
Leaver holds an admin role
Removal goes to a named engineer and is never automated.

Architecture

Starter and leaver automation for an MSP at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Request form Starter or leaver n8n workflow Checklist builder Role templates IT Glue or Hudu Staged changes Awaiting approval Technician Approves changes Microsoft Graph Users, licenses PSA ticket Every step logged
  • Input
  • Logic and services
  • Data
  • People
  • Output

How it flows

  1. 1 The client submits a starter or leaver request through the form or portal.
  2. 2 n8n reads the role template from documentation and stages the account, group, license and mailbox changes.
  3. 3 A technician reviews the staged changes and approves them in the ticket or chat.
  4. 4 Approved changes are applied through Microsoft Graph and every step is logged on the PSA ticket.

Project planner

How the project runs, phase by phase.

Typical durations for a first version. Your proposal lists the exact phases, dates and what you sign off at each step.

Microsoft 365 user onboarding & offboarding project plan

Typical time to launch: about 4 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    Current checklists, role templates, tenants, apps outside Microsoft 365 and approval rules.

  2. 02

    Design

    2 to 3 days

    Form fields, Graph permissions, staging and approval flow, leaver sequence and logging.

  3. 03

    Build

    About 2 weeks

    Form, checklist builder, staged Graph changes, approval step, documentation updates.

  4. 04

    Shadow run

    About 1 week

    Requests produce staged changes in a test tenant while technicians work as usual.

  5. 05

    Launch

    1 to 2 days

    One client first, then roll out role templates for others.

  6. 06

    Support

    Ongoing

    New role templates, new clients and app checklists.

What it runs on

Real products only, connected through the access each vendor provides. See all integrations

n8n Microsoft Graph (users, assignLicense, revokeSignInSessions) Google Workspace Admin SDK, where used ConnectWise PSA, Autotask or HaloPSA API IT Glue or Hudu API Microsoft Forms or your client portal

Cost estimate

What it costs, line by line.

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and design

    Checklists, role templates, permissions and approvals.

    $200 – $400

  • Build

    Form, checklist builder, staged changes and leaver sequence.

    $500 – $1,300

  • Integrations

    Microsoft Graph, PSA and documentation platform.

    $150 – $400

  • Testing and shadow run

    Test tenant run and technician comparison.

    $100 – $250

  • Launch and training

    First client go-live and team walkthrough.

    $50 – $150

  • Total project estimate

    $1,000 – $2,500

Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. Covers one tenant platform; adding Google Workspace alongside Microsoft 365 or many line-of-business apps may need a second workflow.

Monthly running costs you pay directly

Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.

  • n8n: Free self-hosted Community edition, or n8n Cloud from about €20 a month (Starter) or €50 (Pro), billed annually.
  • Microsoft 365: No extra charge for Graph calls beyond the client's existing Microsoft licensing.

What pushes cost up

  • Systems without an API, or with integration access that must be requested from the vendor
  • Writing data back into your core system rather than only reading from it
  • Several locations, brands or very different processes to support
  • Custom apps, dashboards or a voice line on top of the workflows

What keeps cost down

  • One location and one clear process to start with
  • Cloud software with a documented API
  • Using tools you already pay for instead of adding new ones
  • Approved wording and sample data ready at the start
Get a fixed quote

Privacy and consent

Rules we design for, with the sources.

General information to plan with, not legal advice. Your counsel or data protection adviser confirms what applies to your practice.

Disable accounts that are no longer needed

CISA and partner agencies tell organisations to disable user and MSP accounts when personnel change or access is no longer needed, and to audit for unused accounts.

Source: www.cisa.gov

Least-privileged Graph permissions

License changes use the LicenseAssignment.ReadWrite.All permission Microsoft lists as least privileged, rather than broad directory write access.

Source: learn.microsoft.com

Session revocation has a short delay

Microsoft notes there may be a delay of a few minutes after revokeSignInSessions before tokens are revoked, so the leaver sequence blocks sign-in first.

Source: learn.microsoft.com

EU and UK: employee data

Starter and leaver data is personal data processed on the client's behalf, so it needs a GDPR Article 28 processor contract between you and each client.

Source: gdpr-info.eu

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
  2. 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
  3. 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
  4. 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.

How scope stays under control

Product backlog
Every feature, fix and question in one prioritised list you can see at any time.
Acceptance criteria
Plain-language conditions for "done" on each item, agreed before work starts.
Change requests
New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
User acceptance testing (UAT)
Before launch your team tests the real workflow against the acceptance criteria and signs off.

Tools we use

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

Project manager / Scrum master

Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.

Business analyst

Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.

Automation engineer

Builds the n8n workflows, integrations, AI steps and error handling.

Backend developer

Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.

Frontend / mobile developer

Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.

QA engineer

Tests every workflow against the acceptance criteria, including edge cases and failure paths.

DevOps engineer

Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.

Who does what at each phase

Free call
Project manager, business analyst
Understand the problem, check it is worth automating and outline a rough range.
Discovery
Business analyst, automation engineer
Map the current process, systems and data, and agree success measures.
Design
Business analyst, automation engineer, backend developer
Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
Sprints
Automation engineer, developers, QA
Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
UAT and launch
QA, DevOps, project manager
Your team tests and signs off, we switch on, monitor closely and train the team.
Support
Automation engineer, DevOps
Stabilisation window, then optional monthly care with monitoring and changes.

A point of contact

One person who can answer questions and approve decisions, with about an hour a week during the project.

Access

Admin or API access to the systems involved, created as separate accounts with the least access needed.

Sample data

Real but non-sensitive records (or de-identified ones) so we can design and test against reality.

Approved wording

Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.

Vendor agreements

Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.

Time for testing

A few hours from the people who will use the system, for the demos and user acceptance testing.

Working system

Workflows, integrations and any apps running in your accounts, under your keys.

Documentation

Workflow specification, data-flow map, run book and exported workflow files.

Training

A walkthrough for the team and a short recorded video for new starters.

Handover

All access, credentials and code handed over; you can keep us or take it in-house.

Stabilisation window

Fixes for anything that does not meet the agreed acceptance criteria after launch.

Support options after launch

  • No plan

    You run it yourselves after the stabilisation window and contact us when you need a change.

  • Monthly care

    Monitoring, error alerts, small changes and updates each month, with an agreed response time.

  • Priority care

    Faster response times for business-critical workflows and a monthly review call.

How a project moves through our team

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

FAQ

Microsoft 365 user onboarding & offboarding questions, answered.

On the leaving date the workflow blocks sign-in, revokes sessions, removes licenses and converts or forwards the mailbox as the client chose, all through Microsoft Graph after a technician approves. Apps outside the tenant are tracked as tasks until removal is confirmed.

A script is fine for one technician. A workflow adds the client form, role templates, approval, logging on the ticket and confirmation to the requester, and it still calls the same Microsoft Graph endpoints underneath.

Yes, through a form or your client portal. The request is matched to the client and nothing changes in their tenant until a technician approves.

The workflow runs per client tenant with the permissions you grant. How you delegate admin access across tenants is part of discovery, and we keep the scopes as narrow as Microsoft allows.

The Admin SDK covers users, groups and licenses for Google Workspace. Clients on both platforms can share the same form and checklist with a branch per platform.

Requests completed by the start or leaving date, steps missed in audits, time from request to completion and leavers with licenses still assigned after their date.

Free 20-minute call

Want this for your it support & msp?

Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.

Book a free 20-minute call