◆ Microsoft Azure

Run Azure Function app on different port

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 taskRun the 'api-gateway-function' app locally on port 7072 instead of the default. Make sure it's…+
Run the 'api-gateway-function' app locally on port 7072 instead of the default. Make sure it's accessible for testing by the front-end team.
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 running the 'api-gateway-function' app on port 7072 for the front-end team, verify that…+
Before running the 'api-gateway-function' app on port 7072 for the front-end team, verify that port 7072 is free and won't conflict with any other local services. If it's in use, find the next available port and notify the front-end lead of the change to avoid 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 'api-gateway-function' app isn't responding on port 7072, and the front-end team is…+
The 'api-gateway-function' app isn't responding on port 7072, and the front-end team is blocked.
The 'api-gateway-function' app isn't responding on port 7072, and the front-end team is completely blocked, pushing back their release. I'm afraid it's a port conflict, but I can't tell if another process is using it or if the function app simply isn't binding correctly. What's the quickest way to diagnose this and get them unblocked before our stand-up in an hour?
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 troubleshooting local function app testing because of port conflicts or…+
I frequently struggle with local function app testing due to port conflicts or misconfigurations, delaying local development.
I frequently waste time troubleshooting local function app testing because of port conflicts or configuration issues, which slows down my development cycle. It's frustrating to keep hitting the same walls. What habit should I change to ensure my local function app environments are always ready to run on a specified or available port without these recurring snags?
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.