◆ Microsoft Azure

Automate workflows with Azure Logic Apps

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 taskBuild a Logic App that triggers when a new file is uploaded to the 'Invoice Approvals'…+
Build a Logic App that triggers when a new file is uploaded to the 'Invoice Approvals' SharePoint folder. It should then send an email notification to Maria in finance with a link to the file and mark it for review.
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 deploy this invoice approval Logic App, make sure it's resilient and easy to maintain.…+
Before I deploy this invoice approval Logic App, make sure it's resilient and easy to maintain. Consider edge cases like large files, duplicate uploads, or if Maria is out of office. How can I build in error handling and logging so we can quickly diagnose issues without me getting paged every time?
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 new Logic App I built for expense report approvals is failing intermittently, usually once…+
The new Logic App for expense report approvals is failing intermittently, but I can't see why.
The new Logic App I built for expense report approvals is failing intermittently, usually once or twice a day, and I'm getting complaints from John in accounting. The run history shows 'Failed' but offers no clear error message, and I'm worried about financial data getting lost. Is this a common issue with connectors, or am I missing a fundamental design flaw? What's the most effective diagnostic step I should take 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 find that my Logic Apps, while solving immediate problems, often grow into complex, brittle…+
My Logic Apps often become complex and hard to debug over time.
I find that my Logic Apps, while solving immediate problems, often grow into complex, brittle systems that are difficult to debug or modify months later. This costs me significant time in maintenance. What habit should I change in my initial design and documentation process to ensure future maintainability and reduce technical debt?
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.