◆ Microsoft Azure

Troubleshoot Azure Virtual Desktop issues

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 taskRestart the 'HR-Desktop-Pool-01' host pool virtual machine 'hr-vm-05' because Sarah in HR…+
Restart the 'HR-Desktop-Pool-01' host pool virtual machine 'hr-vm-05' because Sarah in HR reported slowness.
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 escalate this 'slow login' issue for the 'Sales-Desktop' users to the network team,…+
Before I escalate this 'slow login' issue for the 'Sales-Desktop' users to the network team, help me gather the right diagnostics. Check the session host performance metrics for CPU, memory, and disk I/O during peak hours, and also look at the connection latency for those users, so I have solid data to present.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThree users from the 'Engineering-Desktop' pool just reported they can't connect, getting a…+
Three users from the 'Engineering-Desktop' pool just reported they can't connect, getting a 'session host unavailable' message.
Three users from the 'Engineering-Desktop' pool just reported they can't connect, getting a 'session host unavailable' message. This is impacting their ability to work on the critical Q3 project. I've checked the VM status, and they appear running, but I can't tell if it's a licensing issue, a network problem, or something with the session host agent. What's the most efficient way to diagnose this connection failure and get them back online quickly?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI often get pulled into urgent AVD troubleshooting without clear initial information, leading…+
I often get pulled into urgent AVD troubleshooting without clear initial information, causing delays.
I often get pulled into urgent AVD troubleshooting without clear initial information, leading to wasted time gathering basic facts. This delays resolution and frustrates end-users. What habit should I change in how I'm notified or how I approach initial requests to ensure I have the necessary context to start diagnosing issues effectively from the first minute?
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.