Copilot prompt for a PowerShell script to onboard Microsoft 365 users
A prompt for a PowerShell onboarding script with the Microsoft Graph SDK: the input CSV, user creation, group and license assignment, least-privilege scopes, WhatIf support, logging and idempotent re-runs.
Tuned for Copilot · structured role / context / task / output
Open in the builder →Ready-to-use prompt
# Role You are an experienced workflow-automation architect who designs reliable, maintainable automations on the platform in use: a precise trigger, exact connector and action names, explicit conditions, error handling, and a test plan. # Context Write a PowerShell script that reads new hires from a CSV, creates their Microsoft 365 accounts, adds them to department groups and assigns licenses, with WhatIf and logging. # Task Design the automation described in the context above for the stated platform: the trigger, each action in order with exact connector or action names, the conditions and approvals, error handling and retries, and how to test it before it goes live. # How to approach this Think through the problem step by step before answering. Work the hard parts out explicitly, then give a clear final answer. Let the difficulty of the task set how much reasoning is needed — don't pad the easy steps. - Lay the automation out in order: trigger, each action, the conditions and branches, error handling, then a test plan. Before you finalize, verify that the trigger fires on exactly the intended event and nothing else; every action names the real connector, action, or command for the stated platform; the first failure has a handling path: retry, notify, or stop; the test plan covers the main path and that first failure. # Constraints - Do not invent connector, action, or command names. If unsure one exists, say so and use the closest real alternative. - Use clean, professional formatting that pastes cleanly into Word, Outlook, and Excel. Prefer tables and numbered steps for anything structured. - Deliver one finished, office-ready result rather than a set of options. - Keep the tone professional and workplace-appropriate unless the prompt says otherwise. - For spreadsheet or document tasks, give the exact formula, steps, or text — never a vague description of what to do. - Deliver the result directly — no apologies or meta-commentary about the prompt itself. # Output format Return only the requested output. If multiple distinct variants would clearly help, label them (e.g., "Option A", "Option B"). # Done when - the output fully answers the goal in the Context section with no missing parts
Customize this prompt
Answer a few quick questions and Promptivo re-tunes the prompt above to your exact situation.
Start the interview →Why this prompt works
Onboarding scripts run against production identity. The prompt requires WhatIf, logging with object IDs, and a check for existing accounts before creating anything.
Graph permissions are the main blocker. The prompt asks for the exact scopes (User.ReadWrite.All, Group.ReadWrite.All, and Directory.ReadWrite.All where needed) and admin consent.
License assignment fails without a usage location. The prompt asks for the licensing rule and includes the usage location step.
Using this prompt in Copilot
For powershell m365 onboarding, Copilot is a strong choice — it's especially good at Office-ready output you can finish in Word, Outlook, and Excel. Promptivo formats this prompt the way Copilot works best: office-ready output that pastes cleanly into Word, Outlook, and Excel, with tables and numbered steps.
Paste it into Microsoft Copilot or the Microsoft 365 side-panel, then replace any bracketed details with your own. Copilot generalizes when it is under-fed, so keep the bracketed context specific and it will stay grounded in your details.
Tuned for Copilot: how it differs
| Model | What Promptivo changes |
|---|---|
| ChatGPT | Concise instructions, strict format adherence, no preamble. |
| Claude | Explicit step-by-step thinking and clearly delimited output sections. |
| Gemini | Precise phrasing with brief reasoning cues where they improve accuracy. |
| Copilot | Office-ready output that pastes cleanly into Word, Outlook, and Excel, with tables and numbered steps. |
Questions, answered
- How do I create Microsoft 365 users with PowerShell?
- Connect with Connect-MgGraph and the right scopes, then New-MgUser with display name, UPN, password profile and usage location, followed by group membership and license assignment. The prompt designs the script with input from a CSV.
- Which PowerShell module should I use for Microsoft 365?
- The Microsoft Graph PowerShell SDK (Microsoft.Graph). The older Azure AD and MSOnline modules are retired.
- How do I make an onboarding script safe to re-run?
- Check whether the user exists by UPN, skip or update instead of creating, support WhatIf, and log every change. The prompt asks for all four.
- Is Copilot good for powershell m365 onboarding?
- Yes. Copilot handles powershell m365 onboarding well thanks to its Office-ready output you can finish in Word, Outlook, and Excel, and Promptivo tunes the prompt to match — office-ready output that pastes cleanly into Word, Outlook, and Excel, with tables and numbered steps. Paste it into Microsoft Copilot or the Microsoft 365 side-panel.