Copilot prompt for an Azure Logic Apps workflow
A prompt for an Azure Logic Apps workflow: Consumption or Standard, the trigger, connectors and their authentication (API connection or managed identity), scopes with run-after error handling, and deployment parameters.
Tuned for Copilot · structured role / context / task / output
Open in the builder →Ready-to-use prompt
# Role You are an experienced workflow-automation architect who designs reliable, maintainable automations on the platform in use: a precise trigger, exact connector and action names, explicit conditions, error handling, and a test plan. # Context Design an Azure Logic App that archives blobs older than 90 days from one storage container to another every night. # Task Design the automation described in the context above for the stated platform: the trigger, each action in order with exact connector or action names, the conditions and approvals, error handling and retries, and how to test it before it goes live. # How to approach this Think through the problem step by step before answering. Work the hard parts out explicitly, then give a clear final answer. Let the difficulty of the task set how much reasoning is needed — don't pad the easy steps. - Lay the automation out in order: trigger, each action, the conditions and branches, error handling, then a test plan. Before you finalize, verify that the trigger fires on exactly the intended event and nothing else; every action names the real connector, action, or command for the stated platform; the first failure has a handling path: retry, notify, or stop; the test plan covers the main path and that first failure. # Constraints - Do not invent connector, action, or command names. If unsure one exists, say so and use the closest real alternative. - Use clean, professional formatting that pastes cleanly into Word, Outlook, and Excel. Prefer tables and numbered steps for anything structured. - Deliver one finished, office-ready result rather than a set of options. - Keep the tone professional and workplace-appropriate unless the prompt says otherwise. - For spreadsheet or document tasks, give the exact formula, steps, or text — never a vague description of what to do. - Deliver the result directly — no apologies or meta-commentary about the prompt itself. # Output format Return only the requested output. If multiple distinct variants would clearly help, label them (e.g., "Option A", "Option B"). # Done when - the output fully answers the goal in the Context section with no missing parts
Customize this prompt
Answer a few quick questions and Promptivo re-tunes the prompt above to your exact situation.
Start the interview →Why this prompt works
Consumption and Standard Logic Apps differ in hosting, connectors and cost. The prompt asks which one, because the design and the deployment change.
Authentication is where Logic Apps get stuck. The prompt asks whether each connector uses an API connection or a managed identity.
Production workflows need error handling and parameters. The prompt asks for scopes with run-after and for the values that change between environments.
Using this prompt in Copilot
For logic apps workflow, Copilot is a strong choice — it's especially good at Office-ready output you can finish in Word, Outlook, and Excel. Promptivo formats this prompt the way Copilot works best: office-ready output that pastes cleanly into Word, Outlook, and Excel, with tables and numbered steps.
Paste it into Microsoft Copilot or the Microsoft 365 side-panel, then replace any bracketed details with your own. Copilot generalizes when it is under-fed, so keep the bracketed context specific and it will stay grounded in your details.
Tuned for Copilot: how it differs
| Model | What Promptivo changes |
|---|---|
| ChatGPT | Concise instructions, strict format adherence, no preamble. |
| Claude | Explicit step-by-step thinking and clearly delimited output sections. |
| Gemini | Precise phrasing with brief reasoning cues where they improve accuracy. |
| Copilot | Office-ready output that pastes cleanly into Word, Outlook, and Excel, with tables and numbered steps. |
Questions, answered
- Logic Apps or Power Automate?
- Logic Apps for Azure-hosted integration owned by IT, with ARM or Bicep deployment and managed identities. Power Automate for Microsoft 365 users automating their own work. The prompt designs for the one you choose.
- How do I handle errors in a Logic App?
- Group actions in a Scope, add a parallel branch configured to run after the scope has failed or timed out, and notify or retry there. The prompt asks for that branch.
- Can a Logic App use a managed identity?
- Yes, for Azure services that support Microsoft Entra authentication, such as Storage, Key Vault and Service Bus. Other connectors use API connections.
- Is Copilot good for logic apps workflow?
- Yes. Copilot handles logic apps workflow well thanks to its Office-ready output you can finish in Word, Outlook, and Excel, and Promptivo tunes the prompt to match — office-ready output that pastes cleanly into Word, Outlook, and Excel, with tables and numbered steps. Paste it into Microsoft Copilot or the Microsoft 365 side-panel.