unable to read emails from outlook, extract text from it and send teams message using logic app. This used to work fine and suddenly we are seeing this error message from morning

Question

unable to read emails from outlook, extract text from it and send teams message using logic app. This used to work fine and suddenly we are seeing this error message from morning

V J 0 Microsoft External Staff

We use consumption tier logic app for reading emails from outlook connection(this connection was created using my mailbox), extract text and post it in teams channel. This was working fine from last 4 months and suddenly stopped working today. We are getting below message when checked for trigger.

can you let me know how we can fix this issue.

Note: there is no change in email count which it reads.

    "body": {
        "status": 429,
        "message": "Too many requests from Identifier:xxxxxxx-xxxx-xxxx-8a45-xxxxx under category:throttle.aad.ags.subscriptionservice.app.extended2. Please try again later.\r\nclientRequestId: ddddd-ddd-dddd-dddd-dddddd\r\nserviceRequestId: ccccc-cc-429c-cc-ccccccc",
        "error": {
            "message": "Too many requests from Identifier:
xxxxxxx-xxxx-xxxx-8a45-xxxxx
 under category:throttle.aad.ags.subscriptionservice.app.extended2. Please try again later."
        },
        "source": "office365-wus2.xxx-wus2-xxx.xx.azurewebsites.net"
    }
}

Siddhesh Desai 5,850 Reputation points Microsoft External Staff Moderator

2026-03-12T08:21:23.7433333+00:00

Hi @V J Thank you for reaching out to Microsoft Q&A.

Thank you for reaching out to Microsoft Q&A.

The issue you are experiencing is not related to any change in your Logic App workflow, trigger configuration, or email volume. The error message clearly indicates an HTTP 429 (Too Many Requests) coming from Azure AD / Microsoft Graph, which is used internally by the Office 365 Outlook connector. Since you are using a Consumption-tier Logic App with a polling Outlook trigger authenticated using a user mailbox, the workflow runs on shared infrastructure and is subject to dynamic throttling limits enforced by Microsoft Graph. These limits can change at any time due to regional load, backend enforcement updates, or accumulated usage against the same connection. As a result, even workflows that have been running successfully for months can suddenly start failing with throttling errors. This is a documented and expected platform behavior, not a regression or misconfiguration.

Refer below points to resolve this issue or use as workaround:

Recreate the Office 365 Outlook connection Delete the existing Outlook connection and create a new one, then rebind it to the trigger. This resets the throttling state associated with the connection identity and often restores functionality temporarily. This is a mitigation, not a permanent fix.

Reduce polling and concurrency on the trigger Increase the recurrence interval of the Outlook trigger and avoid very frequent polling. If trigger concurrency is enabled, disable it or limit it to a single run. Reducing parallel executions lowers the number of Microsoft Graph calls and helps avoid throttling.

Configure retry policy for 429 errors Ensure the trigger or downstream actions use the default or exponential retry policy so Logic Apps can honor Microsoft Graph backoff behavior (Retry-After). This helps absorb transient throttling instead of immediately failing runs.

Avoid using personal mailboxes for automation Personal user mailboxes are more aggressively throttled. Use a shared mailbox or a dedicated service account mailbox for Logic App automation workloads. This is a recommended best practice for stability.

Consider migrating to Logic Apps Standard for production workloads Consumption Logic Apps run on shared infrastructure where throttling behavior can vary with regional load. Logic Apps Standard provides better isolation and predictable throughput, making it more suitable for business-critical email-processing workflows.
Siddhesh Desai 5,850 Reputation points Microsoft External Staff Moderator

2026-03-12T08:22:57.83+00:00

Hi,

I have messaged you on Private chat, Can you please reply?
Tony Valentine 0 Reputation points

2026-03-12T15:08:39.86+00:00

We also started experiencing a lot of these same failures midday yesterday (March 11). We use a stateful standard Logic App. The failures are continuing up to the moment of me writing this. Most of the triggers are still succeeding, but a significant number are failing.
Siddhesh Desai 5,850 Reputation points Microsoft External Staff Moderator

2026-03-13T08:29:27.86+00:00

Hi @Tony Valentine have you raised a question for your issue for us to look at?
Tony Valentine 0 Reputation points

2026-03-13T11:54:32.43+00:00

No, we have not yet created a support ticket. We did try re-creating the outlook connection, but this did not help. Since this happened to us the same time as the original poster, it appears that perhaps Microsoft has lowered a throttle on Office.
Tony Valentine 0 Reputation points

2026-03-16T11:23:16.77+00:00

In our case, converting the mailbox from a personal to a shared mailbox has solved the issue. Not sure why this became an issue all of a sudden, perhaps Microsoft recently lowered this throttle threshold.
Tony Valentine 0 Reputation points

2026-03-18T12:31:54.3166667+00:00

Unfortunately, I was mistaken. We are still getting the same sporadic 429 failures that we did not get prior to March 11th.
Praveen Kumar Gudipudi 2,280 Reputation points Microsoft External Staff Moderator

2026-03-20T12:25:20.4133333+00:00

Hello @Tony Valentine,

Could you please share me the logic app designer screenshot to proceed further?

1 answer

Your answer

Siddhesh Desai 5,850 Reputation points Microsoft External Staff Moderator

2026-03-12T08:22:57.83+00:00

Hi,

I have messaged you on Private chat, Can you please reply?
Tony Valentine 0 Reputation points

2026-03-12T15:08:39.86+00:00

We also started experiencing a lot of these same failures midday yesterday (March 11). We use a stateful standard Logic App. The failures are continuing up to the moment of me writing this. Most of the triggers are still succeeding, but a significant number are failing.
Siddhesh Desai 5,850 Reputation points Microsoft External Staff Moderator

2026-03-13T08:29:27.86+00:00

Hi @Tony Valentine have you raised a question for your issue for us to look at?
Tony Valentine 0 Reputation points

2026-03-13T11:54:32.43+00:00

No, we have not yet created a support ticket. We did try re-creating the outlook connection, but this did not help. Since this happened to us the same time as the original poster, it appears that perhaps Microsoft has lowered a throttle on Office.
Tony Valentine 0 Reputation points

2026-03-16T11:23:16.77+00:00

In our case, converting the mailbox from a personal to a shared mailbox has solved the issue. Not sure why this became an issue all of a sudden, perhaps Microsoft recently lowered this throttle threshold.
Tony Valentine 0 Reputation points

2026-03-18T12:31:54.3166667+00:00

Unfortunately, I was mistaken. We are still getting the same sporadic 429 failures that we did not get prior to March 11th.
Praveen Kumar Gudipudi 2,280 Reputation points Microsoft External Staff Moderator

2026-03-20T12:25:20.4133333+00:00

Hello @Tony Valentine,

Could you please share me the logic app designer screenshot to proceed further?

Answer 1

Hi V J

Thanks for reaching out on Microsoft Q&A!

429 errors mean the backend has enforced a rate limit, originating from AAD Graph/Graph Subscription Services. This is Usually tied to triggers like “When a new email arrives” and occurs before Outlook even processes the email payload.

Below are the recommended fixes from Microsoft’s throttling guidance:

By default, retry logic is enabled on Logic App triggers; Remove those to make sure your logic app will execute the trigger only once, instead of exponentially every run (which even raises more problems); Please note not every trigger supports this value, it depends on what Outlook trigger you use;
Set concurrency control to 1, which avoid most of the issue; This makes processing slower though, but if it's not time-critical this may be a solution; Beware: once the trigger is set to concurrency control it's irreversible.
Use a Shared Mailbox Instead of a User Mailbox, as personal mailbox traffic counts against your identity's Graph limits. Shared Mailboxes distribute load differently.

Please click ‘Accept answer’ if you think my answer is helpful. Feel free to drop additional queries in the comments below!

Kind regards,

Sonny

Share via

unable to read emails from outlook, extract text from it and send teams message using logic app. This used to work fine and suddenly we are seeing this error message from morning

1 answer

Your answer