◆ Microsoft Azure

Perform Azure migrations

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 taskMigrate the 'FinanceApp-Prod' virtual machine and its associated disks from the…+
Migrate the 'FinanceApp-Prod' virtual machine and its associated disks from the 'Old-Subscription-001' subscription to 'New-Subscription-002'. Ensure minimal downtime, and update the networking to use the 'Prod-VNet-EastUS2' virtual network in the new subscription by Friday afternoon.
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 start migrating the 'HR-Portal' resources, tell me how to best group them for the move…+
Before I start migrating the 'HR-Portal' resources, tell me how to best group them for the move to 'New-Subscription-002' to simplify future cost management and access control for the HR team. Also, flag any dependencies that might cause issues if not moved together.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe 'SalesCRM-Dev' migration just failed with a generic 'resource not found' error, even though…+
The 'SalesCRM-Dev' migration just failed with a generic 'resource not found' error.
The 'SalesCRM-Dev' migration just failed with a generic 'resource not found' error, even though all resources were verified as existing in the source. I'm worried this will delay the UAT scheduled for tomorrow morning. I can't tell if it's a permission issue or a misconfiguration on my side. What's the most likely cause, and what should I check first to get this back on track?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep hitting unexpected roadblocks during migrations, often due to subtle network or identity…+
I keep hitting unexpected roadblocks during migrations, often due to subtle network or identity issues.
I keep hitting unexpected roadblocks during migrations, often due to subtle network or identity issues that only surface during the actual move. This costs us extra hours and pushes deadlines. What habit should I change in my pre-migration planning to catch these hidden dependencies earlier and make migrations smoother?
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.