◆ Microsoft Azure

Switch accounts in VS Code Azure extension

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 taskSwitch my VS Code extension for cloud resources to use my 'dev-subscription-owner' account. I…+
Switch my VS Code extension for cloud resources to use my 'dev-subscription-owner' account. I need to access resources in the development environment.
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 switching my VS Code extension for cloud resources to the 'dev-subscription-owner'…+
Before switching my VS Code extension for cloud resources to the 'dev-subscription-owner' account, ensure that the current context is saved or noted. After switching, verify that I can successfully list resources in the 'dev-eastus' resource group to confirm the account is active and has the correct permissions.
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 just switched my VS Code extension for cloud resources to the 'dev-subscription-owner'…+
I switched accounts in VS Code, but I still can't see the development resources, and the sprint demo is tomorrow.
I just switched my VS Code extension for cloud resources to the 'dev-subscription-owner' account, but I still can't see the resources in the 'dev-eastus' resource group, and our sprint demo is tomorrow. I'm afraid I'll look unprepared. I can't tell if it's a caching issue, a permissions problem that wasn't granted correctly, or if I'm somehow in the wrong tenant. What's the most likely reason for this, and what's the fastest way to get the correct view of the resources?
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 lose time and confidence when switching between cloud accounts and subscriptions…+
I often lose time and confidence when switching between Azure accounts and subscriptions in my local tools.
I frequently lose time and confidence when switching between cloud accounts and subscriptions in my local development tools. It feels like a gamble every time, and I often end up troubleshooting rather than working. What habit should I change to make these account switches reliable and quick, ensuring I always land in the correct context with the right permissions without second-guessing?
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.