Merge pull request #291842 from daphnemamsft/daphneMa_fields-slow-updates

Add section for ARG fields that have slower update times

Author: prmerger-automator[bot]

articles/governance/resource-graph/concepts/guidance-for-throttled-requests.md

@@ -8,10 +8,7 @@ ms.custom: devx-track-csharp
 
 # Guidance for throttled requests in Azure Resource Graph
 
-When creating programmatic and frequent use of Azure Resource Graph data, consideration should be
-made for how throttling affects the results of the queries. Changing the way data is requested can
-help you and your organization avoid being throttled and maintain the flow of timely data about your
-Azure resources.
+When programmatically using Azure Resource Graph data, it is important to consider how throttling affects the results of the queries. Changing the way data is requested can help you and your organization avoid throttling issues and maintain the flow of timely data about your Azure resources.
 
 This article covers four areas and patterns related to the creation of queries in Azure Resource
 Graph:

articles/governance/resource-graph/troubleshoot/general.md

@@ -99,6 +99,30 @@ If the customer doesn't have read permission to all the provided subscriptions,
 
 Include at least one subscription in the subscription list that the customer running the query has at least read access to. For more information, see [Permissions in Azure Resource Graph](../overview.md#permissions-in-azure-resource-graph).
 
+### Scenario: Azure Resource Graph fields not being updated immediately
+
+#### Issue
+
+There are specific fields, when using Azure Resource Graph, that are updated at a slower cadence. These fields will converge to true values over time, provided there are no updates in between. 
+
+##### List of fields affected
+
+> [!IMPORTANT]
+> - This concept is not limited to specific properties. The following list are examples that you might find delayed, but eventually become updated.
+> - There are certain cases where VM states are updated asynchronously, which means that the current state does not match the "goal state" (desired state set by customers). However, these VM fields will converge over time.
+
+- properties.extended.instanceView.osName
+- properties.extended.instanceView.osVersion
+- properties.extended.instanceView.computerName
+
+#### Cause
+
+Some fields are coming from agent blobs that don't have notification coverage, therefore updates to these fields are delayed.
+
+#### Resolution
+
+These fields update at a slower cadence today, but will converge to true values over time, provided there are no updates in between.
+
 ## Next steps
 
 If you didn't see your problem or are unable to solve your issue, visit one of the following channels for more support: