Question About Rate Limits for Standard and Enterprise Connector rate limits in Azure Logic Apps

Question

Question About Rate Limits for Standard and Enterprise Connector rate limits in Azure Logic Apps

Sreekanth Reddy Pattem 20

Hello,

I hope you're doing well. I am currently exploring the Azure Logic Apps and would appreciate some help in understanding the rate limits for connectors, specifically:

Standard connectors in Azure Logic Apps.
Enterprise connectors in Azure Logic Apps & others

Are there any rate limits for these connectors similar to the ones in Microsoft Power Automate?

Thanks,
Sreekanth

Khadeer Ali 4,960 Reputation points Microsoft External Staff

2025-04-28T11:52:01.3766667+00:00

@Sreekanth Reddy Pattem ,
Thanks for reaching out.

Every connector in Azure Logic Apps has its own set of limitations and constraints. If you could specify which connector you are primarily focusing on, we can refer to the official documentation here:

https://learn.microsoft.com/en-us/connectors/connector-reference/connector-reference-logicapps-connectors

and review the relevant details together.
Sreekanth Reddy Pattem 20 Reputation points

2025-04-28T14:12:12.8866667+00:00

Hi @Khadeer Ali
Thank you for your quick response and for offering your help.
I would like to understand the rate limits for Office 365 connectors (such as SharePoint, OneDrive, Excel, and other commonly used services) and Azure services (such as Storage Queues, Key Vault, Azure AI services, and other frequently used services). I reviewed the URL you shared, but couldn’t find specific details regarding the rate limits for internal and external connectors.
Could you please share relevant information or point me to the appropriate documentation? Thanks again for your support :)
Khadeer Ali 4,960 Reputation points Microsoft External Staff

2025-04-28T18:11:21.55+00:00
@Sreekanth Reddy PattemOffice 365 and Azure services enforce specific rate limits that impact how connectors and APIs are used, especially within automated workflows like Logic Apps.

For example:

Exchange Online enforces limits such as 30 messages per minute and 10,000 recipients per day per mailbox, as detailed in the Exchange Online limits - Service Descriptions | Microsoft Learn

Azure Key Vault allows 4,000 GET operations per 10 seconds for software-protected keys and 250 GET operations per 10 seconds for HSM-protected keys. If these limits are exceeded, Key Vault returns HTTP 429 (Too Many Requests) errors. Microsoft recommends using exponential backoff and caching strategies to handle throttling, as explained in the Key Vault throttling guidance.

Azure Queue Storage supports up to 2,000 messages per second per queue, with detailed quotas outlined in the Azure subscription and service limits, quotas, and constraints - Azure Resource Manager | Microsoft Learn

In Azure Logic Apps, the platform itself enforces limits such as 10,000 concurrent runs per region (for Consumption plans). Additionally, connector throttling behavior is governed by the limits of the backend services they interact with (e.g., SharePoint, Excel). To manage scenarios like 429 Too Many Requests errors, Microsoft recommends applying retry policies with exponential backoff and implementing usage monitoring to proactively handle throttling scenarios.
Khadeer Ali 4,960 Reputation points Microsoft External Staff

2025-04-29T10:31:28.8233333+00:00

@Sreekanth Reddy Pattem ,

I wanted to check in and see if my earlier response addressed your question. If you still need assistance or have additional questions, feel free to share more details.
Sreekanth Reddy Pattem 20 Reputation points

2025-04-29T10:34:55.99+00:00

Yeah, this is helpful. Any info on Office 365 connectors (such as SharePoint, OneDrive, Excel, and other commonly used services) will be great. I couldn't find that info in any of the Microsoft docs.
Khadeer Ali 4,960 Reputation points Microsoft External Staff

2025-04-29T10:58:21.83+00:00

@Sreekanth Reddy Pattem ,

Thanks for getting back. Here's a quick overview of commonly used connectors:

Outlook (Exchange Online): Limited to 30 messages per minute and 10,000 recipients per mailbox per day. Exchange Online limits.

SharePoint Online: Allows up to 600 API calls per connection every 60 seconds. If this limit is exceeded, you’ll receive a “429 Too Many Requests” error. SharePoint throttling details.

Excel Online (Business): Typically allows around 100 API calls per 60 seconds. While exact limits aren't published, it's best to use delays and retries to avoid throttling. Excel connector documentation.

OneDrive for Business: Shares similar limits to SharePoint. Throttling is handled through Microsoft Graph API. Microsoft Graph throttling.

Other connectors (e.g., Teams, Planner): Also follow Microsoft Graph API rules and may return 429 errors during high usage. More on Graph throttling.

If a connector gets throttled, Logic Apps won’t automatically retry unless retry policies are in place. It’s recommended to use retry policies with exponential backoff to handle such cases.
Sreekanth Reddy Pattem 20 Reputation points

2025-04-29T11:23:29.48+00:00

Thanks, Khadeer! Are these values (mentioned above) applicable only to Logic Apps, or do they also apply to Power Automate and other tools that interact with Office 365 services? I'm trying to understand whether Logic Apps has the capability to extend these rate limits.
Khadeer Ali 4,960 Reputation points Microsoft External Staff

2025-04-29T12:08:50.2133333+00:00

@Sreekanth Reddy Pattem ,

I don't think in that way, but just to clarify, the rate limits for Office 365 connectors (such as SharePoint, Excel, Outlook, etc.) are not specific to Azure Logic Apps. They are applied at the backend service level, so the same limits apply to any tool that interacts with those services — whether it’s Power Automate, Logic Apps, or any custom applications using Microsoft Graph.

Therefore, Logic Apps cannot extend or bypass these rate limits. However, it does provide better flexibility for handling throttling by allowing you to define retry policies, control execution frequency, and monitor workflows more effectively.
Sreekanth Reddy Pattem 20 Reputation points

2025-04-29T13:18:21.07+00:00

Thank you so much!

Accepted answer

0 additional answers

Your answer

Khadeer Ali 4,960 Reputation points Microsoft External Staff

2025-04-28T11:52:01.3766667+00:00

@Sreekanth Reddy Pattem ,
Thanks for reaching out.

Every connector in Azure Logic Apps has its own set of limitations and constraints. If you could specify which connector you are primarily focusing on, we can refer to the official documentation here:

https://learn.microsoft.com/en-us/connectors/connector-reference/connector-reference-logicapps-connectors

and review the relevant details together.
Sreekanth Reddy Pattem 20 Reputation points

2025-04-28T14:12:12.8866667+00:00

Hi @Khadeer Ali
Thank you for your quick response and for offering your help.
I would like to understand the rate limits for Office 365 connectors (such as SharePoint, OneDrive, Excel, and other commonly used services) and Azure services (such as Storage Queues, Key Vault, Azure AI services, and other frequently used services). I reviewed the URL you shared, but couldn’t find specific details regarding the rate limits for internal and external connectors.
Could you please share relevant information or point me to the appropriate documentation? Thanks again for your support :)
Khadeer Ali 4,960 Reputation points Microsoft External Staff

2025-04-28T18:11:21.55+00:00

@Sreekanth Reddy PattemOffice 365 and Azure services enforce specific rate limits that impact how connectors and APIs are used, especially within automated workflows like Logic Apps.

For example:

Exchange Online enforces limits such as 30 messages per minute and 10,000 recipients per day per mailbox, as detailed in the Exchange Online limits - Service Descriptions | Microsoft Learn

Azure Key Vault allows 4,000 GET operations per 10 seconds for software-protected keys and 250 GET operations per 10 seconds for HSM-protected keys. If these limits are exceeded, Key Vault returns HTTP 429 (Too Many Requests) errors. Microsoft recommends using exponential backoff and caching strategies to handle throttling, as explained in the Key Vault throttling guidance.

Azure Queue Storage supports up to 2,000 messages per second per queue, with detailed quotas outlined in the Azure subscription and service limits, quotas, and constraints - Azure Resource Manager | Microsoft Learn

In Azure Logic Apps, the platform itself enforces limits such as 10,000 concurrent runs per region (for Consumption plans). Additionally, connector throttling behavior is governed by the limits of the backend services they interact with (e.g., SharePoint, Excel). To manage scenarios like 429 Too Many Requests errors, Microsoft recommends applying retry policies with exponential backoff and implementing usage monitoring to proactively handle throttling scenarios.
Khadeer Ali 4,960 Reputation points Microsoft External Staff

2025-04-29T10:31:28.8233333+00:00

@Sreekanth Reddy Pattem ,

I wanted to check in and see if my earlier response addressed your question. If you still need assistance or have additional questions, feel free to share more details.
Sreekanth Reddy Pattem 20 Reputation points

2025-04-29T10:34:55.99+00:00

Yeah, this is helpful. Any info on Office 365 connectors (such as SharePoint, OneDrive, Excel, and other commonly used services) will be great. I couldn't find that info in any of the Microsoft docs.
Khadeer Ali 4,960 Reputation points Microsoft External Staff

2025-04-29T10:58:21.83+00:00

@Sreekanth Reddy Pattem ,

Thanks for getting back. Here's a quick overview of commonly used connectors:

Outlook (Exchange Online): Limited to 30 messages per minute and 10,000 recipients per mailbox per day. Exchange Online limits.

SharePoint Online: Allows up to 600 API calls per connection every 60 seconds. If this limit is exceeded, you’ll receive a “429 Too Many Requests” error. SharePoint throttling details.

Excel Online (Business): Typically allows around 100 API calls per 60 seconds. While exact limits aren't published, it's best to use delays and retries to avoid throttling. Excel connector documentation.

OneDrive for Business: Shares similar limits to SharePoint. Throttling is handled through Microsoft Graph API. Microsoft Graph throttling.

Other connectors (e.g., Teams, Planner): Also follow Microsoft Graph API rules and may return 429 errors during high usage. More on Graph throttling.

If a connector gets throttled, Logic Apps won’t automatically retry unless retry policies are in place. It’s recommended to use retry policies with exponential backoff to handle such cases.
Sreekanth Reddy Pattem 20 Reputation points

2025-04-29T11:23:29.48+00:00

Thanks, Khadeer! Are these values (mentioned above) applicable only to Logic Apps, or do they also apply to Power Automate and other tools that interact with Office 365 services? I'm trying to understand whether Logic Apps has the capability to extend these rate limits.
Khadeer Ali 4,960 Reputation points Microsoft External Staff

2025-04-29T12:08:50.2133333+00:00

@Sreekanth Reddy Pattem ,

I don't think in that way, but just to clarify, the rate limits for Office 365 connectors (such as SharePoint, Excel, Outlook, etc.) are not specific to Azure Logic Apps. They are applied at the backend service level, so the same limits apply to any tool that interacts with those services — whether it’s Power Automate, Logic Apps, or any custom applications using Microsoft Graph.

Therefore, Logic Apps cannot extend or bypass these rate limits. However, it does provide better flexibility for handling throttling by allowing you to define retry policies, control execution frequency, and monitor workflows more effectively.
Sreekanth Reddy Pattem 20 Reputation points

2025-04-29T13:18:21.07+00:00

Thank you so much!

Answer 1

@Sreekanth Reddy Pattem ,

To summarize our discussion — we reviewed the rate limits applicable to Office 365 and Azure connectors in Azure Logic Apps. Logic Apps itself does not enforce connector-specific limits; instead, each connector is subject to the throttling policies of its underlying service. These limits apply universally across tools such as Power Automate, Power Apps, and custom solutions using Microsoft Graph APIs.

Here’s a quick overview of some commonly used services and their limits:

Exchange Online (Outlook Connector): Allows 30 messages per minute and 10,000 recipients per day per mailbox.

SharePoint Online: Limits to 600 API calls per connection per 60 seconds. Returns HTTP 429 when exceeded.

Excel Online (Business): Typically supports around 100 API calls per 60 seconds. Microsoft recommends adding delays or retries to avoid throttling, although exact limits are not officially documented.

OneDrive for Business: Shares throttling behavior with SharePoint, as detailed in the Microsoft Graph throttling documentation.

Microsoft Teams, Planner, and other Graph-based connectors: Follow Microsoft Graph API throttling rules, which vary by service and request type.

Azure Services (e.g., Key Vault, Storage Queues): Enforce their own limits, such as 4,000 GET operations per 10 seconds for Key Vault software keys and 2,000 messages per second per Azure Storage Queue.

These limits cannot be increased or bypassed using Logic Apps. However, Logic Apps offers robust capabilities to manage these constraints, such as retry policies with exponential backoff, trigger controls, and monitoring tools (e.g., Azure Monitor, Log Analytics).

Hope this helps. Do let us know if you have any further queries.

If this answers your query, do click Accept Answer and Yes for "Was this answer helpful." And if you have any further questions, let us know.

Share via

Question About Rate Limits for Standard and Enterprise Connector rate limits in Azure Logic Apps

0 additional answers

Your answer