This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(275.2, 3%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPL%3C/text%3E%3C/svg%3E)
I noticed very recently that we are having issues when have multiple steps using the "Create and Send E-mail" step. We are getting the following error. Is there any way to cache the token or adjust the limits before the app gets throttled? It seems to happen around 15-18 emails. This has not been an issue and we have been running the same runbook for the last few year + and havent started having issues until 12/28. We haven't changed anything with our APP in Azure AD, haven't changed settings in Exchange online. What is the best route to go about here because I thought using the Integration pack was the best way to go.?
Your app has been throttled by AAD due to too many requests. To avoid this, cache your tokens see https://aka.ms/msal-net-throttling.
Exception: Exception
Target site: ExchangeGateway..ctor
Stack trace:
at SystemCenter.IntegrationPack.ExchangeUser.Web.Core.ExchangeGateway..ctor(IExchangeConfiguration configuration)
at SystemCenter.IntegrationPack.ExchangeUser.Activities.ExchangeActivity`1.Execute(IActivityRequest request, IActivityResponse response)
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(150.4, 92%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EXM%3C/text%3E%3C/svg%3E)
We could insert a Wait activity before the 'Create and Send E-mail' step.
As the error message mentioned, this issue is not related to Orchestrator or Exchange. Instead, Microsoft Entra ID (AAD) throttles applications when the authentication API is called too frequently.
https://learn.microsoft.com/en-us/entra/msal/dotnet/advanced/client-and-server-throttling
Please review the following log for further findings:
True if you wish to inspect authentication failures in detail. The logs will be generated on the path %windir%\Temp\sc-orchestrator\exchange_user\{date-time-stamp}.msal.txt. One file will be generated for each execution of an Exchange User activity.True if you wish to inspect EWS failures in detail. The logs will be generated on the path %windir%\Temp\sc-orchestrator\exchange_user\{date-time-stamp}.ews-trace.xml.log. One file will be generated for each execution of an Exchange User activity. We recommend that you use SOAPe to visually inspect the traces.We could add an interval time to the "Create and Send E-mail" step. Avoid making authentication API calls too frequently.
My initial step pulls users from Active directory that have pw expirations less than 15 days away. The run behavior is not set to flatten so the next steps are processed as they come individually. Is there a way to build in a delay to throttle the send email requests in this use case?
To be Honest I never understood where the looping properties feature comes into play. Would this were that would be used?
Please see below for my existing workflow diagram.
If you are using a loop to process each user, you can add a delay within the loop. This ensures that each email send action is spaced out.
What is the formal process to request the throttle option built into the integration pack?
Thank you for your feedback. I will report this to the product team and let you know as soon as there is any response.
looking at the sample of my runbook Im not sure how I would be able to add the delay.
If My first step runs a script that returns 25 results will the delay be inserted before it processes each result individually or will it delay and then process all 25 results at the next step?