Merge pull request #172217 from DCtheGeek/dmc-arg-firstupdate

ARG: Update First to 1000

Author: PRMerger8

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

@@ -1,7 +1,7 @@
 ---
 title: Guidance for throttled requests
 description: Learn to group, stagger, paginate, and query in parallel to avoid requests being throttled by Azure Resource Graph.
-ms.date: 08/17/2021
+ms.date: 09/13/2021
 ms.topic: conceptual
 ms.custom: devx-track-csharp
 ---
@@ -218,7 +218,7 @@ looking for. However, some Azure Resource Graph clients handle pagination differ
   var results = new List<object>();
   var queryRequest = new QueryRequest(
       subscriptions: new[] { mySubscriptionId },
-      query: "Resources | project id, name, type | top 5000");
+      query: "Resources | project id, name, type");
   var azureOperationResponse = await this.resourceGraphClient
       .ResourcesWithHttpMessagesAsync(queryRequest, header)
       .ConfigureAwait(false);
@@ -235,22 +235,6 @@ looking for. However, some Azure Resource Graph clients handle pagination differ
   }
   ```
 
-- Azure CLI / Azure PowerShell
-
-  When using either Azure CLI or Azure PowerShell, queries to Azure Resource Graph are automatically
-  paginated to fetch at most 5,000 entries. The query results return a combined list of entries from
-  all paginated calls. In this case, depending on the number of entries in the query result, a
-  single paginated query may consume more than one query quota. For example, in the following
-  examples, a single run of the query may consume up to five query quota:
-
-  ```azurecli-interactive
-  az graph query -q 'Resources | project id, name, type' --first 5000
-  ```
-
-  ```azurepowershell-interactive
-  Search-AzGraph -Query 'Resources | project id, name, type' -First 5000
-  ```
-
 ## Still get throttled?
 
 If you're getting throttled after exercising the above recommendations, contact the [Azure Resource