◆ Microsoft Azure

Set up 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 taskSet up an automation account in the 'Development' subscription for the 'DevOpsTeam' resource…+
Set up an automation account in the 'Development' subscription for the 'DevOpsTeam' resource group. Enable the Update Management and Change Tracking features, and link it to our 'DevLogs' Log Analytics workspace.
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 finalize the automation setup for our development environment, ensure it's…+
Before I finalize the automation setup for our development environment, ensure it's cost-effective and doesn't create unnecessary overhead. Should I consolidate this with an existing automation account in another subscription, or are there specific features I should disable or configure differently to optimize costs for a non-production environment, especially regarding log retention and runbook execution frequency?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI just set up an automation account for our new project, but the runbooks I'm deploying aren't…+
I just set up Azure Automation for our new project, but the runbooks I'm deploying aren't showing up or executing, and I can't figure out why.
I just set up an automation account for our new project, but the runbooks I'm deploying aren't showing up or executing, and I can't figure out why. The project manager expects a demo of the automated deployment by end of day. I'm not sure if it's a connectivity issue with the hybrid worker, a problem with the runbook's module dependencies, or if I missed a crucial configuration step during the initial setup. What's the most likely culprit, and what's the first thing I should check to get these runbooks running?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI consistently struggle with inconsistent runbook behavior across different Automation accounts…+
I consistently struggle with inconsistent runbook behavior across different Automation accounts and environments.
I consistently struggle with inconsistent runbook behavior across different Automation accounts and environments, leading to unpredictable results and wasted debugging time. My current practice of deploying runbooks ad-hoc isn't working. What habit should I change to ensure a more standardized and reliable runbook deployment and testing process, especially when moving from development to production, to avoid these recurring inconsistencies?
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.