◆ Microsoft Azure

Automatically create AD users using Azure Automation

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskWrite a PowerShell runbook for the 'HRUserProvisioning' automation account that takes a new…+
Write a PowerShell runbook for the 'HRUserProvisioning' automation account that takes a new user's name, email, and department as parameters and creates a new user account, setting a temporary password and forcing a password change on first login.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore I put this user creation runbook into production for HR, make it resilient and easy to…+
Before I put this user creation runbook into production for HR, make it resilient and easy to troubleshoot. Add error handling for common AD creation failures, ensure it logs all actions to our central Log Analytics workspace, and include a rollback mechanism if the user creation partially fails.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe new user provisioning runbook just failed for Sarah Miller, but the error message in the…+
The AD user creation runbook failed for a new hire, but the logs aren't clear why, and HR needs the account ASAP.
The new user provisioning runbook just failed for Sarah Miller, but the error message in the logs is generic, 'user creation failed.' HR is calling every five minutes because she can't start work. I'm afraid to just rerun it without knowing the root cause, and I can't tell if it's an AD sync issue or something in the script. What's the most likely cause for a generic AD user creation failure, and how can I quickly diagnose and resolve it without impacting other users?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI'm always getting stuck when our user creation runbooks fail, especially when the error…+
I consistently struggle with debugging AD user creation runbooks and understanding their failures.
I'm always getting stuck when our user creation runbooks fail, especially when the error messages are vague. It takes me too long to pinpoint the exact issue, whether it's a permission, a duplicate UPN, or something else. What's a better habit for designing these runbooks from the start so they provide clearer diagnostics and make troubleshooting faster when things go wrong?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from Microsoft Azure's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.