Power Automate with Teams

Analogy categoryAnalogies

What Power Automate Adds to Teams

Power Automate is Microsoft's low-code workflow engine, and its dedicated Teams connector exposes triggers like 'When a new channel message is added' or 'When someone responds to an adaptive card,' alongside actions like 'Post a message in a chat or channel' or 'Post an adaptive card and wait for a response.' Because it's built from a visual designer rather than hand-written code, a business analyst — not just a developer — can wire together a flow such as posting a Teams approval card whenever a new item lands in a SharePoint list, with zero lines of custom code.

🏏

Cricket analogy: This is like a modern DRS review system that umpires operate through a simple on-field signal rather than needing to understand the underlying ball-tracking software — Power Automate lets a business user trigger complex automation through a simple visual flow.

Common Flow Patterns: Approvals and Adaptive Cards

The 'Post an adaptive card and wait for a response' action posts a structured card (defined in Adaptive Card JSON) directly to a user or channel and pauses the flow until the recipient submits it, making it ideal for approvals, surveys, or acknowledgments — for example, a manager approves an expense report directly inside Teams and the flow branches based on their Approve or Reject choice. This pattern eliminates the need to build a custom bot just to collect a yes/no decision, since the adaptive card's Action.Submit button feeds structured JSON straight back into the flow's next step.

🏏

Cricket analogy: This is like the third umpire pausing play and waiting for the on-field umpire's final decision on a run-out review before the match resumes — the flow pauses at the adaptive card exactly the same way until a response arrives.

json

{
  "type": "AdaptiveCard",
  "version": "1.5",
  "body": [
    { "type": "TextBlock", "text": "Expense report #4821", "weight": "Bolder", "size": "Medium" },
    { "type": "TextBlock", "text": "Amount: $342.50 — Submitted by Priya Sharma", "wrap": true }
  ],
  "actions": [
    { "type": "Action.Submit", "title": "Approve", "data": { "decision": "approve" } },
    { "type": "Action.Submit", "title": "Reject", "data": { "decision": "reject" } }
  ]
}

Power Automate's 'For a selected message' flow type can be surfaced as a message extension action directly inside the Teams message context menu, letting a user right-click any message and trigger a flow — no separate app install required beyond enabling the flow.

Governance, Licensing, and Limits

Not every Power Automate action is free under a standard Microsoft 365 license — premium connectors (certain HTTP, SQL, or third-party connectors) require a Power Automate per-user or per-flow plan, and flows are subject to daily run-count and API request limits that scale with license tier. Tenant admins can also govern which connectors are allowed via Data Loss Prevention (DLP) policies in the Power Platform admin center, blocking flows that would, for example, mix a 'Business' data connector like SharePoint with a 'Non-Business' one like an arbitrary public HTTP endpoint in the same flow.

🏏

Cricket analogy: This is like a domestic T20 league capping the number of overseas players per team — a standard license lets you use a certain roster of connectors, and premium ones require paying for extra 'overseas slots.'

A flow that silently starts failing after working for months is often a DLP policy change or a licensing tier change made by an admin elsewhere in the tenant, not a bug in the flow itself — check the Power Platform admin center's DLP policies and connector licensing before debugging the flow logic.

Power Automate's Teams connector provides triggers (new message, card response) and actions (post message, post adaptive card) with no custom code.
The 'Post an adaptive card and wait for a response' action is the standard low-code pattern for approvals inside Teams.
Adaptive Card Action.Submit buttons return structured JSON that drives the flow's next branch.
Flows can be surfaced as message extension actions in the Teams message context menu.
Premium connectors require a paid Power Automate license tier beyond what's bundled in standard Microsoft 365.
Tenant admins enforce Data Loss Prevention (DLP) policies that can block certain connector combinations in a flow.
Unexplained flow failures are often caused by admin-side licensing or DLP changes, not flow logic bugs.