Skip to main content
Promptivo logoPromptivo
Build a prompt

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.

Open in the builder →

Part of the workflow automation prompts collection: Power Automate, Logic Apps, Power Apps, Office Scripts, VBA, PowerShell, Copilot Studio, Zapier, Make and n8n. Writing your own? Read the automation prompt guide.

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
Work the problem internally, then give only the result. Do not narrate your reasoning unless it is part of the deliverable.

- 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.
- Follow the requested format exactly. Default to clean markdown. Be concise — no filler, no restating the question.
- Deliver the single best answer rather than hedging across several.
- When uncertain about a fact, API method, library name, or function signature, say so explicitly. Do not produce a plausible guess.
- Do not invent citations, URLs, or package names. If you don't know one, omit it or flag that you don't.
- 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

Tuned for your model

Get a version optimized for the AI you actually use:

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.

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.

Related prompts