Understand 401, 403 and 429 responses
Do not treat every code as “reconnect and retry”.
Applies to: Power Automate and connectors.
Revision 5 · 18 November 2026 · General first-line guidance. Wording varies by version; a symptom is not a confirmed diagnosis.

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 see | What it may indicate | What to check |
|---|---|---|
| 401 / 403 / 429 | Broadly: 401 is an authentication problem, 403 is a refusal or missing permission, and 429 means too many requests. The service message gives the context. | Do not treat every code as “reconnect and retry”. |
| 401 | The request was not properly authenticated. | Check the connection account and sign-in state. |
| 403 | The request was understood but refused. | Check permissions on the target resource with its owner. |
| 429 | The service is limiting how fast requests arrive. | Do not re-run repeatedly. Ask the owner about delay and retry design. |
| No message at all | Problems 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. |

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.
Read the actual response
- Do this
- Expand the failed action and note the status and sanitised error body.
- What you should see
- The code and service message are known.
- Then what?
- If this explains what you see, record it and continue only if the next check still applies.
Identify the acting account
- Do this
- Read the connection identity without replacing it.
- What you should see
- The account used may differ from the person viewing the flow.
- Then what?
- Record the result without changing settings. Stop if work, data or security could be affected.
Check scope and frequency
- Do this
- Note the target resource and whether many calls failed together.
- What you should see
- A single-resource refusal differs from widespread throttling.
- Then what?
- Use only the approved action described here. If it does not match your screen, stop and ask IT.
Avoid retry storms
- Do this
- Ask the owner to review retry and delay design, or permissions, in a test copy.
- What you should see
- A controlled next step exists rather than repeated retries.
- 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
- Work could be lost, or you cannot tell which version is current.
- The problem repeats, or a managed setting blocks you.
- A step would change production data, shared connections, permissions or security.
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
Was this guide helpful? Leave feedback
Tell us what worked, what was unclear, or what is missing. Feedback is private and goes to The Workflow Lab for review. It is not shown publicly and is not an IT support request.
The Workflow Lab is independent of Microsoft and is not your employer’s service desk.