◆ Microsoft Azure

Understand shared responsibility model

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
See the prompt↓All Microsoft Azure tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskGenerate a report outlining the shared responsibility model for our 'Customer Portal'…+
Generate a report outlining the shared responsibility model for our 'Customer Portal' application. Specifically, include who is responsible for network controls, operating system patching, and application code security.
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 present this to the new security auditor, make the shared responsibility model for our…+
Before I present this to the new security auditor, make the shared responsibility model for our 'Customer Portal' application absolutely clear. Highlight where our responsibilities end and the cloud provider's begin for IaaS, PaaS, and SaaS components, and flag any areas where we've historically had confusion.
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 security auditor just asked about data encryption at rest for our 'Customer Portal'…+
The security auditor just asked about data encryption at rest for our 'Customer Portal' database, and I'm not sure if that's our job or Azure's. I'm afraid of misstating our responsibility and causing a compliance issue. What's the definitive answer for a PaaS SQL database, and how should I communicate it?
The security auditor just asked about data encryption at rest for our 'Customer Portal' database, and I'm not sure if that's our job or the cloud provider's. I'm afraid of misstating our responsibility and causing a compliance issue. What's the definitive answer for a PaaS SQL database, and how should I communicate it clearly without confusing the auditor further? I need to be sure about who owns that control.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternWe frequently have misunderstandings with auditors and internal teams about who owns specific…+
We frequently have misunderstandings with auditors and internal teams about who owns specific security controls in Azure.
We frequently have misunderstandings with auditors and internal teams about who owns specific security controls, leading to repeated questions and delays. We keep losing time and credibility because our understanding of the shared responsibility model isn't consistent. What habit should I change to ensure everyone on the team has a clear, current, and consistent grasp of these boundaries?
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.