Claude prompt for a PowerShell script to onboard Microsoft 365 users

# 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
You reason carefully on your own. Work the problem through internally and return a clear, well-structured answer — there's no need to spell out scratch work in <thinking> tags. Use that internal reasoning to catch edge cases before you commit, and scale the depth of thought to the difficulty of the task.

- 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 clear markdown sections and headings. Favor well-structured, thorough output over terse output.
- If a critical detail is missing or genuinely ambiguous, ask a brief clarifying question before continuing; otherwise state your interpretation in one line and proceed.
- Do not open with "I'd be happy to help" or any variant. Just start.
- Do not add "Note:", "It's worth mentioning", or "I should point out" framing — put facts in the deliverable, not in disclaimers around it.
- Treat clearly benign tasks as safe and complete them directly.
- 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

Why this prompt works

Using this prompt in Claude

Tuned for Claude: how it differs

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 Claude good for powershell m365 onboarding?

Yes. Claude handles powershell m365 onboarding well thanks to its careful step-by-step reasoning and cleanly structured long-form writing, and Promptivo tunes the prompt to match — explicit step-by-step thinking and clearly delimited output sections. Paste it into claude.ai or the Claude desktop app.