◆ Microsoft Azure

Create an Automation task in Azure

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 taskCreate an Automation account named 'ProdOpsAutomation' in the 'East US' region under the…+
Create an Automation account named 'ProdOpsAutomation' in the 'East US' region under the 'Production' resource group. Configure it to use a system-assigned managed identity and link it to our existing Log Analytics workspace 'ProdLogs'.
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 deploy this new Automation account for our production operations, make sure it's…+
Before I deploy this new Automation account for our production operations, make sure it's resilient and secure. Should I be using a user-assigned managed identity instead of system-assigned for better control, and what's the best way to ensure it has only the minimal necessary permissions across our subscriptions for the tasks it will run?
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'm trying to set up an Automation account for a new critical production workflow, but I'm…+
I'm trying to set up an Automation account for a new critical production workflow, but I'm getting permission errors when it tries to interact with a different subscription.
I'm trying to set up an Automation account for a new critical production workflow, but I'm getting permission errors when it tries to interact with a different subscription, even though I thought I granted the necessary roles. The procurement lead is pressing for this automation to go live by Friday. I can't tell if it's an RBAC inheritance issue, a firewall rule I missed, or something deeper with cross-subscription access. What's the most likely problem, and what's the quickest way to verify the permissions needed across subscriptions?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI frequently run into permission issues when setting up new Automation accounts or runbooks,…+
I frequently run into permission issues when setting up new Automation accounts or runbooks, leading to delays and security concerns.
I frequently run into permission issues when setting up new Automation accounts or runbooks, leading to delays and security concerns. My current approach of trial-and-error with RBAC roles is inefficient and risky. What habit should I change to consistently define and apply the principle of least privilege for Automation accounts and their managed identities from the start, across different environments?
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.