◆ Microsoft Azure

Create subdirectory in blob container

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 subdirectory named 'q1-2024' inside the 'sales-reports' blob container within the…+
Create a subdirectory named 'q1-2024' inside the 'sales-reports' blob container within the 'reporting-storage' account. Ensure it's ready for files to be uploaded into it.
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 create the 'q1-2024' subdirectory in 'sales-reports', help me ensure it follows our…+
Before I create the 'q1-2024' subdirectory in 'sales-reports', help me ensure it follows our naming conventions and access patterns. Confirm the 'sales-reports' container is in the 'reporting-storage' account, and suggest any best practices for organizing date-based data within blob containers. I want to make sure this is set up correctly for future use and easy retrieval.
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 create a 'q1-2024' subdirectory in the 'sales-reports' container for new reports.…+
I need to create a new subdirectory for reports, but I'm unsure about the best way to structure it for future archiving.
I need to create a 'q1-2024' subdirectory in the 'sales-reports' container for new reports. However, I'm thinking about how we'll archive these at year-end. Should I just create 'q1-2024' directly, or should I nest it under a '2024' directory first? I'm afraid of creating a messy structure that's hard to manage later or impacts cost. What's the recommended approach for this kind of time-series data in blob storage, and what should I do right now?
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 create new subdirectories and containers in blob storage on the fly, and I've…+
I often find myself creating new blob storage structures without a consistent strategy, leading to disorganization.
I frequently create new subdirectories and containers in blob storage on the fly, and I've noticed our storage accounts are becoming a bit of a jungle. It's hard to find things and enforce consistent access. What habit should I change to ensure a more organized and scalable approach to blob storage hierarchy, maybe by defining clear naming conventions or a review process, so I avoid future headaches and improve data governance?
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.