Why standardize new hires and leavers

Every client has new people and people who leave, and each one is a ticket. When the steps live in someone's head, they get done differently and sometimes missed, especially for leavers, where a missed step can leave access open. A written checklist, applied the same way every time, fixes most of it.

New hire checklist

  1. Create the Microsoft 365 account with the client's naming convention.
  2. Set the manager.
  3. Assign the correct license.
  4. Add the user to the right groups and shared resources.
  5. Help them register for multi-factor authentication.
  6. Record every step in the ticket.

Leaver checklist

  1. Block sign-in.
  2. Revoke active sessions.
  3. Remove group memberships and licenses.
  4. Decide what happens to the mailbox (convert, forward or share) and to files.
  5. Handle devices and any other accounts.
  6. Record every step in the ticket.

The first two leaver steps in PowerShell

With the Microsoft Graph PowerShell module, you can block sign-in and revoke sessions. You need an account with the right permissions; see the Microsoft Graph PowerShell documentation for the exact scopes.

Connect-MgGraph -Scopes "User.ReadWrite.All"
Update-MgUser -UserId [email protected] -AccountEnabled:$false
Revoke-MgUserSignInSession -UserId [email protected]

Run it against a test user first. Blocking sign-in stops new sign-ins; revoking sessions ends the ones already open.

Write everything back to the ticket

The record matters as much as the action. For each step, note what was done, when and by whom or by which automation. If a client asks later what happened to a leaver's access, the ticket should answer it.

Test before you trust it

Try the whole process in a test tenant first and watch it succeed on a few test users. For a new automation, run it in a mode where it reports what it would have done before it changes anything.

What to automate

The repeat, rule-based steps are the best candidates: creating accounts, setting managers, assigning licenses and groups, blocking sign-in, revoking sessions and writing the result to the ticket. Judgment calls, such as what to do with a mailbox, can stay as manual steps in the checklist.

What Pontavia builds

Pontavia's automation for MSPs includes a New hire and leaver automation. A ticket or form starts it. For a hire, it creates the Microsoft 365 account, sets the manager and adds the license and groups. For a leaver, it blocks sign-in, revokes sessions and removes groups and licenses. Every step is written back to the ticket, and mailbox conversion stays a listed manual step. Each step is proven in a test tenant before your acceptance test. You keep your PSA and RMM.

Partner pricing is posted on the MSP page: one automation is $850 to set up and $169 a month, and a Starter Pack of any three is $2,125 to set up and $339 a month. There are no order minimums or partner fees.

Frequently asked questions

What is the first step when an employee leaves?

Block their sign-in and revoke active sessions, so they cannot use the account, then work through licenses, groups, mailbox and devices.

Does blocking sign-in end an already open session?

Not by itself. Revoking sign-in sessions ends the sessions that are already open, which is why both steps come first.

Should mailbox conversion be automated?

It involves judgment about what to keep, forward or share, so many MSPs leave it as a manual step in the checklist. Pontavia's version keeps it as a listed manual step.

Do I need to change my PSA or RMM to automate this?

No. Pontavia's automations work with your existing tools; you keep your PSA and RMM.

Questions about your own setup? Send a message or book a free 15-minute call.