Merge pull request #211776 from barclayn/patch-7

Update how-to-use-vm-token.md

Author: prmerger-automator[bot]

articles/active-directory/managed-identities-azure-resources/how-to-use-vm-token.md

@@ -359,6 +359,7 @@ The managed identities endpoint signals errors via the status code field of the
 | Status Code | Error Reason | How To Handle |
 | ----------- | ------------ | ------------- |
 | 404 Not found. | IMDS endpoint is updating. | Retry with Exponential Backoff. See guidance below. |
+| 410  | IMDS is going through updates |  IMDS will be available within 70 seconds |
 | 429 Too many requests. |  IMDS Throttle limit reached. | Retry with Exponential Backoff. See guidance below. |
 | 4xx Error in request. | One or more of the request parameters was incorrect. | Don't retry.  Examine the error details for more information.  4xx errors are design-time errors.|
 | 5xx Transient error from service. | The managed identities for Azure resources subsystem or Azure Active Directory returned a transient error. | It's safe to retry after waiting for at least 1 second.  If you retry too quickly or too often, IMDS and/or Azure AD may return a rate limit error (429).|
@@ -392,7 +393,7 @@ This section documents the possible error responses. A "200 OK" status is a succ
 
 ## Retry guidance 
 
-It's recommended to retry if you receive a 404, 429, or 5xx error code (see [Error handling](#error-handling) above).
+It's recommended to retry if you receive a 404, 429, or 5xx error code (see [Error handling](#error-handling) above). If you receive a 410 error, it indicates that IMDS is going through updates and will be available in a maximum of 70 seconds.  
 
 Throttling limits apply to the number of calls made to the IMDS endpoint. When the throttling threshold is exceeded, IMDS endpoint limits any further requests while the throttle is in effect. During this period, the IMDS endpoint will return the HTTP status code 429 ("Too many requests"), and the requests fail.