From e3228a09536be93dbb1035b117d6274c4b1c25ef Mon Sep 17 00:00:00 2001 From: Bogdan Gavril Date: Wed, 27 Nov 2024 11:34:10 +0000 Subject: [PATCH] Update client-and-server-throttling.md --- .../advanced/client-and-server-throttling.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/msal-dotnet-articles/advanced/client-and-server-throttling.md b/msal-dotnet-articles/advanced/client-and-server-throttling.md index d5982b1e8..e1cb14ef7 100644 --- a/msal-dotnet-articles/advanced/client-and-server-throttling.md +++ b/msal-dotnet-articles/advanced/client-and-server-throttling.md @@ -7,11 +7,13 @@ description: "Microsoft Entra ID throttles applications when you call the authen ## Server throttling -Microsoft Entra ID throttles applications when you call the authentication API too frequently. Most often this happens when token caching is not used because: +Microsoft Entra ID throttles applications when you call the authentication API too frequently. Most often this happens when **token caching** is misused: -1. Token caching is not setup correctly (see [Token cache serialization](/azure/active-directory/develop/msal-net-token-cache-serialization)). -2. Not calling before calling , . -3. If you are asking for a scope which does not apply to Microsoft Account (MSA) users, such as `User.ReadBasic.All`, resulting in cache misses. +1. The most common cause is not setting up token caching correctly (see [Token cache serialization](/azure/active-directory/develop/msal-net-token-cache-serialization)). +2. Or you are not calling before calling or + or +. +3. It can also happen in the rare case where an application asks for a scope which does not apply to Microsoft Account (MSA) users, such as `User.ReadBasic.All`. This results in token cache misses. The server signals throttling in two ways: