Merge pull request #217818 from rwike77/patch-20

Reviewed

Author: prmerger-automator[bot]

articles/active-directory/develop/test-throttle-service-limits.md

@@ -9,7 +9,7 @@ ms.service: active-directory
 ms.subservice: develop
 ms.topic: conceptual
 ms.workload: identity
-ms.date: 09/17/2021
+ms.date: 11/09/2022
 ms.author: ryanwi
 ms.reviewer: arcrowe
 #Customer intent: As a developer, I want to understand the throttling and service limits I might hit so that I can test my app without interruption.
@@ -64,4 +64,4 @@ Throttling behavior can depend on the type and number of requests. For example,
 When you exceed a throttling limit, you receive the HTTP status code `429 Too many requests` and your request fails. The response includes a `Retry-After` header value, which specifies the number of seconds your application should wait (or sleep) before sending the next request. Retry the request.  If you send a request before the retry value has elapsed, your request isn't processed and a new retry value is returned. If the request fails again with a 429 error code, you are still being throttled. Continue to use the recommended `Retry-After` delay and retry the request until it succeeds.
 
 ## Next steps
-Learn how to [setup a test environment](test-setup-environment.md).
+Learn how to [setup a test environment](test-setup-environment.md).