◆ Microsoft Azure

Create a sub container in Azure storage location

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 taskCreate a new sub-container named 'invoices-2024-q3' within the 'customer-data' storage account,…+
Create a new sub-container named 'invoices-2024-q3' within the 'customer-data' storage account, under the 'financial-records' blob container. Set it for private access.
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 start uploading Q3 invoices, create a new container within our 'financial-records'…+
Before we start uploading Q3 invoices, create a new container within our 'financial-records' storage account. It needs to be easily identifiable for Q3 2024 data, and secured so only authorized applications can access it directly. Make sure the naming convention is consistent with previous quarters.
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 need to store new client financial documents for a new project, and I'm unsure if I should…+
I need to store new client financial documents, but I'm unsure about the best container structure.
I need to store new client financial documents for a new project, and I'm unsure if I should create a new top-level container or a sub-container within an existing one. The project has strict data retention policies, and I'm afraid of creating a structure that will be hard to manage or secure later. I can't tell if a new top-level container will make billing more complex or if a sub-container will hit storage limits or access issues. What's the best approach for this new project's data, considering future scalability and compliance?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternOur storage accounts are becoming a mess of unorganized containers, making it hard to find…+
Our storage accounts are becoming a mess of unorganized containers.
Our storage accounts are becoming a mess of unorganized containers, making it hard to find specific data or manage access policies efficiently. This leads to wasted time and potential compliance risks. What habit should I change in how we plan and create new storage containers to ensure a consistent, logical, and easily auditable structure from now on?
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.