◆ Microsoft Azure

Perform daily Azure administration activities

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 taskGenerate a report of all cloud resources in the 'Development-RG' resource group that have been…+
Generate a report of all cloud resources in the 'Development-RG' resource group that have been running for more than 30 days and are not tagged with a 'Project' name, and email it to 'devops-leads@contoso.com' by end of day for review.
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 perform the monthly cost optimization review for the 'Staging' environment, analyze…+
Before I perform the monthly cost optimization review for the 'Staging' environment, analyze the current resource usage and configuration. Identify any virtual machines that are oversized for their actual CPU/memory usage, storage accounts with low utilization, or unattached disks, and suggest specific actions to reduce costs without impacting development workflows or data integrity.
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 supposed to clean up orphaned resources in the 'Test-RG' by Friday, but I found several…+
I'm supposed to clean up orphaned resources in the 'Test-RG' by Friday, but I found several resources that are untagged, and I'm not sure if they're still in use or if I can safely delete them.
I'm supposed to clean up orphaned resources in the 'Test-RG' by Friday, but I found several resources that are untagged, and I'm not sure if they're still in use or if I can safely delete them. I'm afraid of accidentally deleting something critical that a developer is actively using, and I don't have a clear point of contact for every untagged item. What's the safest way to identify potential owners or usage patterns for untagged resources, and what's the best process to follow to ensure I don't break anything while meeting the cleanup deadline?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternDaily administration tasks often get delayed or become reactive firefighting due to a lack of…+
Daily administration tasks often get delayed or become reactive firefighting due to a lack of clear visibility into resource ownership or purpose.
Daily administration tasks often get delayed or become reactive firefighting due to a lack of clear visibility into resource ownership or purpose. I frequently spend too much time trying to figure out who owns a resource or if it's still needed, especially in our development and test environments. What habit should I change in our resource provisioning or tagging strategy to ensure I always have the necessary context to perform my daily admin activities efficiently and confidently, reducing uncertainty and delays?
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.