◆ Microsoft Azure

Set and access run-time configuration parameters

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 taskSet the 'API_KEY' configuration parameter for the 'ReportingService' web app to 'abc-123-xyz'…+
Set the 'API_KEY' configuration parameter for the 'ReportingService' web app to 'abc-123-xyz' in the production slot. This needs to be done before the 2 PM data refresh.
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 the 'OrderProcessing' web app goes live, review all its runtime configuration…+
Before the 'OrderProcessing' web app goes live, review all its runtime configuration parameters. Ensure sensitive values like database passwords are not exposed in plain text and that all environment-specific settings for production are correctly overridden from staging.
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 'FeatureToggleA' configuration parameter is set to 'true' for the 'CustomerPortal' web app,…+
The 'FeatureToggleA' parameter is correctly set to 'true' in the web app, but the application is still behaving as if it's 'false'.
The 'FeatureToggleA' configuration parameter is set to 'true' for the 'CustomerPortal' web app, but the application is still behaving as if it's 'false'. I've checked the deployment slot settings, and it looks correct there. Our client is expecting this feature live by end of day. Could there be caching issues, a code problem accessing the parameter, or something else I'm missing? What's the quickest way to diagnose why the application isn't reading the correct value?
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 waste time debugging why runtime configuration parameters aren't being correctly…+
I often find myself debugging issues where runtime configuration parameters aren't being picked up by the application.
I frequently waste time debugging why runtime configuration parameters aren't being correctly accessed or applied by web applications, leading to unexpected behavior. This impacts release schedules and my credibility. What habit can I change to ensure that configuration parameters are always correctly set and reliably accessible by the application code, preventing these recurring issues?
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.