◆ Microsoft Azure

Define data collection methods

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 taskList the best ways to collect diagnostic data from our virtual machines running Windows Server…+
List the best ways to collect diagnostic data from our virtual machines running Windows Server 2022, so we can monitor performance and troubleshoot issues efficiently.
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 we finalize our diagnostic data collection strategy for the new customer environment,…+
Before we finalize our diagnostic data collection strategy for the new customer environment, suggest methods that are cost-effective and minimize performance impact on production VMs, while still giving us enough detail to quickly resolve critical incidents.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentOur new diagnostic agent is causing performance issues on the development VMs, but the current…+
Our new monitoring agent is crashing the dev VMs, but the old method is too slow for production.
Our new diagnostic agent is causing performance issues on the development VMs, but the current production data collection is too slow to catch critical errors quickly. My team is pushing back on any changes, saying it's too risky before the big launch next month. I need to propose a solution that satisfies both performance and speed without delaying the release. What's the best way to collect detailed diagnostic data without impacting performance, given the tight deadline and team resistance?
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 constantly fighting to get consistent and reliable diagnostic data from our cloud…+
I keep struggling to get consistent, reliable diagnostic data across different Azure environments.
I'm constantly fighting to get consistent and reliable diagnostic data from our cloud environments, leading to wasted time troubleshooting and missed alerts. We have a mix of new and old applications, and each seems to require a different approach. What habit should I change to establish a unified and effective data collection strategy that works across all our cloud resources, so I'm not constantly reinventing the wheel?
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.