ElectroNeek

Use case · For automation and integration agencies

Microsoft 365 user onboarding and offboarding from a PSA ticket — in minutes, per client

The request comes in as a ticket, an email or the client's onboarding form. An agent extracts name, role, manager, start date and the template to apply; the workflow asks the client contact to approve, then creates the account in Entra ID, assigns licences and groups from the role template, configures the mailbox and Teams, writes the credentials to the client's documentation, and closes the ticket with a summary. Offboarding blocks sign-in, converts the mailbox, removes licences, hands over OneDrive and records every step.

Who it is for
MSPs managing Microsoft 365 for many clients, where joiner and leaver requests arrive as tickets or emails and a technician spends twenty to forty minutes per user in the admin portals.
Systems involved
HaloPSA / ConnectWise / Autotask or a formMicrosoft Graph (Entra ID, Exchange, Teams, OneDrive)AI Workflows agentTeams approvalHudu / IT Glue

How the run goes

5 steps · logged per run

  1. Trigger01

    Ticket, email or form

    Joiner / leaver request

  2. Agent02

    Extract the request

    Name, role, manager, dates, template

  3. Person03

    Client contact approves

    Teams / email approval

  4. System04

    Graph API steps

    User, licences, groups, mailbox, Teams

  5. System05

    Documented and closed

    Hudu / IT Glue, PSA note

Agent decidesDocument becomes fieldsBot does the clicksPerson approves

How it runs, step by step

  1. 1

    A PSA ticket with the onboarding type, an email to the service desk or the client's form starts the run. An agent extracts the fields and checks them against the client's role templates (sales, finance, field); anything missing is asked back in the ticket.

  2. 2

    The client's authorized contact gets an approval with the summary — new user, role, licences, cost. Nothing is created before the approval; the answer is logged with who and when.

  3. 3

    The workflow calls Microsoft Graph with the client's tenant credentials: create the user, set the manager, assign licences from the template, add to groups, enable the mailbox and Teams, apply the MFA policy. Each call's result is recorded; failures roll back what was created.

  4. 4

    Credentials are delivered through the client's agreed secure channel, never in the ticket; the documentation platform gets the new user record, and the PSA ticket is closed with the steps taken and time spent for billing.

  5. 5

    Offboarding runs the reverse list — block sign-in, revoke sessions, convert to shared mailbox, forward, remove licences, OneDrive handover to the manager — and produces the audit record the client's compliance asks for.

Limits — what this does not do

  • Per-client Graph credentials are managed in connections today; per-client workspaces in AI Workflows are in development, so larger MSPs name connections by client carefully.
  • Hybrid AD environments need the on-prem step done by a bot or a script runner; Entra-only is the fully API path.
  • Licence assignment follows your template; it does not decide which licence a role needs.

Questions about this process

  • Yes, through app registrations per client tenant consistent with GDAP; the credentials are stored as connections, scoped to the minimum permissions listed in the template.

  • Hybrid clients get a bot or script step on a runner in their network for the AD part, with Graph handling the cloud part.

  • Yes — a public form in their portal that creates the ticket and starts the run, with your approval step still in place.

Build this on your systems in a guided sandbox.

Tell us the process; after a 30-minute call the sandbox is ready from 24 hours, and we build the first run with your team.