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 Gemini good for logic apps workflow?

Yes. Gemini handles logic apps workflow well thanks to its concise, factual output and precise instruction-following, and Promptivo tunes the prompt to match — precise phrasing with brief reasoning cues where they improve accuracy. Paste it into gemini.google.com.

Gemini 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 Gemini · 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
Be precise and literal about the requirements. Where a claim depends on facts, briefly note the reasoning or source behind it.

- 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.
- Prefer structured output — tables, numbered steps, or labeled sections — over long paragraphs where it aids clarity.
- Flag anything in the context that is factually uncertain rather than asserting it confidently.
- Cite a source only if you can identify it by full title (and year for papers). Never fabricate a URL.
- Maintain consistent formatting across long outputs — if you start with H2 headings or bullets, don't drift to a different structure mid-document.
- 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 Gemini

For logic apps workflow, Gemini is a strong choice — it's especially good at concise, factual output and precise instruction-following. Promptivo formats this prompt the way Gemini works best: precise phrasing with brief reasoning cues where they improve accuracy.

Paste it into gemini.google.com, then replace any bracketed details with your own. Gemini is sensitive to wording, so this prompt pins down the exact terms and structure to keep the result from drifting.

Tuned for Gemini: 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 Gemini good for logic apps workflow?: Yes. Gemini handles logic apps workflow well thanks to its concise, factual output and precise instruction-following, and Promptivo tunes the prompt to match — precise phrasing with brief reasoning cues where they improve accuracy. Paste it into gemini.google.com.