Merge pull request #219834 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: huypub

articles/azure-resource-manager/management/delete-resource-group.md

@@ -118,6 +118,9 @@ az resource delete \
 
 To delete a resource group, you need access to the delete action for the **Microsoft.Resources/subscriptions/resourceGroups** resource.
 
+> [!IMPORTANT]
+> The only permission required to delete a resource group is permission to the delete action for deleting resource groups.  You do **not** need permission to delete individual resources within that resource group.  Addtionally, delete actions that are specified in **notActions** for a roleAssignment are superseded by the resource group delete action.  This is consistent with the scope heirarchy in the Azure role-based access control model.
+
 For a list of operations, see [Azure resource provider operations](../../role-based-access-control/resource-provider-operations.md). For a list of built-in roles, see [Azure built-in roles](../../role-based-access-control/built-in-roles.md).
 
 If you have the required access, but the delete request fails, it may be because there's a [lock on the resources or resource group](lock-resources.md). Even if you didn't manually lock a resource group, it may have been [automatically locked by a related service](lock-resources.md#managed-applications-and-locks). Or, the deletion can fail if the resources are connected to resources in other resource groups that aren't being deleted. For example, you can't delete a virtual network with subnets that are still in use by a virtual machine.

articles/machine-learning/resource-limits-capacity.md

@@ -26,6 +26,16 @@ This section lists basic limits and throttling thresholds in Azure Machine Learn
 | --- | --- |
 | Workspace name | 2-32 characters |
 
+## Experiments
+| Limit | Value |
+| --- | --- |
+| Name | 256 characters |
+| Description | 5,000 characters |
+| Number of tags | 50 |
+| Length of tag key | 250 characters |
+| Length of tag value | 1000 characters |
+| Artifact location | 1024 characters |
+
 ## Runs
 | Limit | Value |
 | --- | --- |
@@ -46,7 +56,6 @@ This section lists basic limits and throttling thresholds in Azure Machine Learn
 | Number of input datasets |200 |
 | Number of output datasets |20 |
 
-
 ## Metrics
 | Limit | Value |
 | --- | --- |
@@ -73,4 +82,4 @@ Some limits can be increased for individual workspaces. To learn how to increase
 
 ## Next steps
 
-- Learn how increase resource quotas in ["Manage and increase quotas for resources"](how-to-manage-quotas.md).
+- Learn how increase resource quotas in ["Manage and increase quotas for resources"](how-to-manage-quotas.md).

articles/search/search-howto-indexing-azure-blob-storage.md

@@ -189,15 +189,15 @@ Once the index and data source have been created, you're ready to create the ind
     ```http
     POST https://[service name].search.windows.net/indexers?api-version=2020-06-30
     {
-      "name" : "my-blob-indexer,
+      "name" : "my-blob-indexer",
       "dataSourceName" : "my-blob-datasource",
       "targetIndexName" : "my-search-index",
       "parameters": {
           "batchSize": null,
           "maxFailedItems": null,
           "maxFailedItemsPerBatch": null,
           "base64EncodeKeys": null,
-          "configuration:" {
+          "configuration": {
               "indexedFileNameExtensions" : ".pdf,.docx",
               "excludedFileNameExtensions" : ".png,.jpeg",
               "dataToExtract": "contentAndMetadata",

articles/virtual-machines/ncv2-series-retirement.md

@@ -5,7 +5,7 @@ author: sherrywangms
 ms.service: virtual-machines
 ms.subservice: sizes
 ms.topic: conceptual
-ms.date: 09/01/2021
+ms.date: 11/21/2022
 ms.author: sherrywang
 ---
 # Migrate your NCv2 series virtual machines by August 31, 2023