TWL-KB-019 · Power Automate · Maker / builder

Connection failed or needs sign-in

Read the actual connection state before re-authorising.

Applies to: Power Automate and Power Platform connections.

Revision 5 · 18 November 2026 · General first-line guidance. Wording varies by version; a symptom is not a confirmed diagnosis.

Invalid connection / authentication failure (wording varies). Read the actual connection state before re-authorising.
Original explainer illustration, not a product screenshot. Select it to enlarge. All information is also in the text.

What does the message mean?

Some rows describe a visible symptom rather than an exact message. Wording marked “varies” may differ on your screen.

What you seeWhat it may indicateWhat to check
Invalid connection / authentication failure (wording varies)Expired tokens, policy changes, disabled accounts or missing permissions can break a connection.Read the actual connection state before re-authorising.
No message at allProblems can happen without any message. A blank screen or a missing control is still useful evidence.Record the visible behaviour, the time and who is affected. Do not guess a code.
First checks: Identify the connector; Read connection status; Ask about recent changes; Route policy blocks to IT
Original explainer illustration, not a product screenshot. Select it to enlarge. All information is also in the text.

Step-by-step checks

Work in order and stop when it is resolved. If your screen differs, note what is different and ask IT or the owner.

  1. Identify the connector

    Do this
    Open the failed action and note the connector and connection used.
    What you should see
    You know which connection this action uses.
    Then what?
    If this explains what you see, record it and continue only if the next check still applies.
  2. Read connection status

    Do this
    View Connections in the intended environment without changing its owner.
    What you should see
    A sign-in warning, a policy block, or a normal status.
    Then what?
    Record the result without changing settings. Stop if work, data or security could be affected.
  3. Ask about recent changes

    Do this
    Ask the owner about password, licence, account or policy changes.
    What you should see
    A change is known, or none is known.
    Then what?
    Use only the approved action described here. If it does not match your screen, stop and ask IT.
  4. Route policy blocks to IT

    Do this
    Record sanitised error details and ask the connection owner to review.
    What you should see
    The right owner and support route are identified.
    Then what?
    If unresolved, contact IT or the owner with sanitised evidence. Do not repeat actions that could duplicate data.

When to stop and contact IT or the owner

What to put in your support request

The app and version if visible, your device, the time, the exact message, who is affected, and the checks you tried with what you saw. Remove names, addresses and confidential content from screenshots. Never send passwords or MFA codes.

Microsoft reference

Microsoft documentation for this topic (opens a new tab). Some links are product hubs. Official pages may include advanced steps; ask IT before applying them on a managed device.

Related guides

The Workflow Lab is independent of Microsoft and is not your employer’s service desk.