◆ Microsoft Azure

Troubleshoot Azure Storage Blob authentication

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 taskInvestigate why the 'customer-data' storage account's 'invoices' blob container is returning…+
Investigate why the 'customer-data' storage account's 'invoices' blob container is returning 403 Forbidden errors for the 'reporting-service' managed identity. Check its assigned roles and permissions on the storage account and container, and review any network access rules or firewall configurations that might be blocking access. Get me the root cause and a proposed fix by 3 PM.
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 403 error for the 'reporting-service' trying to access 'customer-data',…+
Before I escalate this 403 error for the 'reporting-service' trying to access 'customer-data', help me quickly rule out the usual suspects. Prioritize checking for missing RBAC roles on the storage account or container, then look for IP firewall blocks, and finally, any SAS token expiry issues if applicable. I need a clear pathway to resolution, not just a diagnosis.
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 'reporting-service' suddenly can't read from the 'customer-data' blob container, throwing…+
The 'reporting-service' is failing to access 'customer-data' blobs, and I'm getting mixed signals from the logs.
The 'reporting-service' suddenly can't read from the 'customer-data' blob container, throwing 403s. The logs show some access denied, but also some 'network connection closed' errors, which feels contradictory. I've checked the service principal's 'Storage Blob Data Reader' role, and it's there. I'm afraid I'm missing some subtle interaction between network security groups and IAM policies. What's the most likely culprit here, and what's my quickest next step to pinpoint it before the data team loses their minds?
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 firefighting urgent 403 errors when services try to access storage blobs, and it…+
I keep getting pulled into urgent 403 issues for services accessing storage, often due to subtle permission or network misconfigurations.
I'm constantly firefighting urgent 403 errors when services try to access storage blobs, and it always feels like a scramble. I suspect I'm not being proactive enough in how I review access patterns or provision new storage. What habit should I change to prevent these recurring incidents, maybe around initial setup or ongoing monitoring, so I can catch these before they become critical outages?
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.