moving to troubleshooting page

Author: daphnemamsft

articles/governance/resource-graph/toc.yml

@@ -79,8 +79,6 @@
   - name: Guidance for throttled requests
     displayName: pagination, batching, throttling, parallel
     href: ./concepts/guidance-for-throttled-requests.md
-  - name: Azure Resource Graph fields that have slower update
-    href: ./concepts/fields-slow-updates.md
   - name: Security
     items:
     - name: Security baseline for Azure Security Benchmark

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

@@ -99,6 +99,21 @@ 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
+
+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.
+> For virtual machines, VMs 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
+
+
 ## 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: