Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into snapshotClarity

Author: roygara

articles/active-directory/cloud-sync/what-is-cloud-sync.md

@@ -64,7 +64,7 @@ The following table provides a comparison between Azure AD Connect and Azure AD
 | Allow removing attributes from flowing from AD to Azure AD |● |● |
 | Allow advanced customization for attribute flows |● | |
 | Support for password writeback |● |● |
-| Support for device writeback|● |Customers should use [Cloud kerberose trust](https://learn.microsoft.com/windows/security/identity-protection/hello-for-business/hello-hybrid-cloud-kerberos-trust?tabs=intune) for this moving forward|
+| Support for device writeback|● |Customers should use [Cloud Kerberos trust](/windows/security/identity-protection/hello-for-business/hello-hybrid-cloud-kerberos-trust?tabs=intune) for this moving forward|
 | Support for group writeback|● | |
 | Support for merging user attributes from multiple domains|● | |
 | Azure AD Domain Services support|● | |

articles/active-directory/develop/reference-claims-mapping-policy-type.md

@@ -11,7 +11,7 @@ ms.workload: identity
 ms.topic: reference
 ms.date: 01/06/2023
 ms.author: davidmu
-ms.reviewer: ludwignick, jeedes, luleon
+ms.reviewer: ludwignick, jeedes
 ---
 
 # Claims mapping policy type

articles/active-directory/manage-apps/configure-admin-consent-workflow.md

@@ -38,19 +38,23 @@ To enable the admin consent workflow and choose reviewers:
 1. Sign-in to the [Azure portal](https://portal.azure.com)  with one of the roles listed in the prerequisites.
 1. Search for and select **Azure Active Directory**.
 1. Select **Enterprise applications**.
-1. Under **Manage**, select **User settings**.
+1. Under **Security**, select **Consent and permissions**.
+1. Under **Manage**, select **Admin consent settings**.
 Under **Admin consent requests**,  select **Yes** for **Users can request admin consent to apps they are unable to consent to** .
-   :::image type="content" source="media/configure-admin-consent-workflow/enable-admin-consent-workflow.png" alt-text="Configure admin consent workflow settings":::
+
+   ![Screenshot of configure admin consent workflow settings.](./media/configure-admin-consent-workflow/enable-admin-consent-workflow.png)
+   
 1. Configure the following settings:
 
    - **Select users, groups, or roles that will be designated as reviewers for admin consent requests** - Reviewers can view, block, or deny admin consent requests, but only global administrators can approve admin consent requests. People designated as reviewers can view incoming requests in the **My Pending** tab after they have been set as reviewers. Any new reviewers won't be able to act on existing or expired admin consent requests.
    - **Selected users will receive email notifications for requests** - Enable or disable email notifications to the reviewers when a request is made.  
-   - **Selected users will receive request expiration reminders** - Enable or disable reminder email notifications to the reviewers when a request is about to expire.  
+   - **Selected users will receive request expiration reminders** - Enable or disable reminder email notifications to the reviewers when a request is about to expire.
    - **Consent request expires after (days)** - Specify how long requests stay valid.
+
 1. Select **Save**. It can take up to an hour for the workflow to become enabled.
 
-> [!NOTE]
-> You can add or remove reviewers for this workflow by modifying the **Select admin consent requests reviewers** list. A current limitation of this feature is that a reviewer can retain the ability to review requests that were made while they were designated as a reviewer.
+ > [!NOTE]
+ > You can add or remove reviewers for this workflow by modifying the **Select admin consent requests reviewers** list. A current limitation of this feature is that a reviewer can retain the ability to review requests that were made while they were designated as a reviewer.
 
 ## Configure the admin consent workflow using Microsoft Graph
 

articles/applied-ai-services/form-recognizer/service-limits.md

@@ -80,7 +80,9 @@ This article contains both a quick reference and detailed description of Azure F
 | Adjustable | No | No |
 | **Training dataset size * Neural** | 1 GB <sup>3</sup> | 1 GB (default value) |
 | Adjustable | No | No |
-| **Training dataset size * Template** | 50 MB <sup>4</sup> | 50 MB (default value) |
+| **Training file size * Template** | 50 MB <sup>4</sup> | 50 MB (default value) |
+| Adjustable | No | No |
+| **Total Training dataset size * Template** | 150 MB <sup>4</sup> | 150 MB (default value) |
 | Adjustable | No | No |
 | **Max number of pages (Training) * Template** | 500 | 500 (default value) |
 | Adjustable | No | No |

articles/azure-maps/about-azure-maps.md

@@ -64,7 +64,7 @@ For more details, read the [Geolocation service documentation](/rest/api/maps/ge
 
 ### Render service
 
-[Render service V2](/rest/api/maps/render-v2) introduces a new version of the [Get Map Tile V2 API](/rest/api/maps/render-v2/get-map-tile) that supports using Azure Maps tiles not only in the Azure Maps SDKs but other map controls as well. It includes raster and vector tile formats, 256x256 or 512x512 (where applicable) tile sizes and numerous map types such as road, weather, contour, or map tiles created using Azure Maps Creator. For a complete list see [TilesetID](/rest/api/maps/render-v2/get-map-tile#tilesetid) in the REST API documentation. It's recommended that you use Render service V2 instead of Render service V1. You are required to display the appropriate copyright attribution on the map anytime you use the Azure Maps Render service V2, either as basemaps or layers, in any third-party map control. For more information see [How to use the Get Map Attribution API](how-to-show-attribution.md).
+[Render service V2](/rest/api/maps/render-v2) introduces a new version of the [Get Map Tile V2 API](/rest/api/maps/render-v2/get-map-tile) that supports using Azure Maps tiles not only in the Azure Maps SDKs but other map controls as well. It includes raster and vector tile formats, 256x256 or 512x512 (where applicable) tile sizes and numerous map types such as road, weather, contour, or map tiles created using Azure Maps Creator. For a complete list, see [TilesetID](/rest/api/maps/render-v2/get-map-tile#tilesetid) in the REST API documentation. It's recommended that you use Render service V2 instead of Render service V1. You're required to display the appropriate copyright attribution on the map anytime you use the Azure Maps Render service V2, either as basemaps or layers, in any third-party map control. For more information, see [How to use the Get Map Attribution API](how-to-show-attribution.md).
 
 :::image type="content" source="./media/about-azure-maps/intro_map.png" border="false" alt-text="Example of a map from the Render service V2":::
 
@@ -154,7 +154,7 @@ For more information, see the [Traffic service documentation](/rest/api/maps/tra
 
 ### Weather services
 
-Weather services offer APIs that developers can use to retrieve weather information for a particular location. The information contains details such as observation date and time, brief description of the weather conditions, weather icon, precipitation indicator flags, temperature, and wind speed information. Additional details such as RealFeel™ Temperature and UV index are also returned.
+Weather services offer APIs that developers can use to retrieve weather information for a particular location. The information contains details such as observation date and time, brief description of the weather conditions, weather icon, precipitation indicator flags, temperature, and wind speed information. Other details such as RealFeel™ Temperature and UV index are also returned.
 
 Developers can use the [Get Weather along route API](/rest/api/maps/weather/getweatheralongroute) to retrieve weather information along a particular route. Also, the service supports the generation of weather notifications for waypoints that are affected by weather hazards, such as flooding or heavy rain.
 

articles/azure-monitor/snapshot-debugger/snapshot-debugger-app-service.md

@@ -6,17 +6,16 @@ ms.author: hannahhunter
 author: hhunter-ms
 ms.reviewer: charles.weininger
 reviewer: cweining
-ms.date: 08/18/2022
+ms.date: 01/24/2023
 ms.custom: devdivchpfy22
 ---
 
 # Enable Snapshot Debugger for .NET apps in Azure App Service
 
 Snapshot Debugger currently supports ASP.NET and ASP.NET Core apps that are running on Azure App Service on Windows service plans.
 
-We recommend that you run your application on the Basic service tier, or higher, when using Snapshot Debugger.
-
-For most applications, the Free and Shared service tiers don't have enough memory or disk space to save snapshots.
+> [!NOTE]
+> We recommend that you run your application on the Basic service tier, or higher, when using Snapshot Debugger. For most applications, the Free and Shared service tiers don't have enough memory or disk space to save snapshots. The Consumption tier is not currently available for Snapshot Debugger.
 
 ## <a id="installation"></a> Enable Snapshot Debugger
 

articles/azure-vmware/deploy-arc-for-azure-vmware-solution.md

@@ -15,7 +15,7 @@ In this article, you'll learn how to deploy Arc for Azure VMware Solution. Once
 Before you begin checking off the prerequisites, verify the following actions have been done:
 
 - You deployed an Azure VMware Solution private cluster. 
-- You have a connection to the Azure VMware Solution private cloud through your on-prem environment or your native Azure Virtual Network. 
+- You have a connection to the Azure VMware Solution private cloud through your on-premises environment or your native Azure Virtual Network. 
 - There should be an isolated NSX-T Data Center segment for deploying the Arc for Azure VMware Solution Open Virtualization Appliance (OVA). If an isolated NSX-T Data Center segment doesn't exist, one will be created.
 
 ## Prerequisites 
@@ -35,7 +35,7 @@ The following items are needed to ensure you're set up to begin the onboarding p
 > [!NOTE]
 > Only the default port of 443 is supported. If you use a different port, Appliance VM creation will fail. 
 
-At this point, you should have already deployed an Azure VMware Solution private cloud. You need to have a connection from your on-prem environment or your native Azure Virtual Network to the Azure VMware Solution private cloud.
+At this point, you should have already deployed an Azure VMware Solution private cloud. You need to have a connection from your on-premises environment or your native Azure Virtual Network to the Azure VMware Solution private cloud.
 
 For Network planning and setup, use the [Network planning checklist - Azure VMware Solution | Microsoft Docs](./tutorial-network-checklist.md)
 
@@ -93,7 +93,7 @@ Use the following steps to guide you through the process to onboard in Arc for A
     - `GatewayIPAddress` is the gateway for the segment for Arc appliance VM. 
     - `applianceControlPlaneIpAddress` is the IP address for the Kubernetes API server that should be part of the segment IP CIDR provided. It shouldn't be part of the k8s node pool IP range.  
     - `k8sNodeIPPoolStart`, `k8sNodeIPPoolEnd` are the starting and ending IP of the pool of IPs to assign to the appliance VM. Both need to be within the `networkCIDRForApplianceVM`. 
-    - `k8sNodeIPPoolStart`, `k8sNodeIPPoolEnd`, `gatewayIPAddress` ,`applianceControlPlaneIpAddress` are optional. You may choose to skip all the optional fields or provide values for all. If you choose not to provide the optional fields then you must use /28 address space for `networkCIDRForApplianceVM`
+    - `k8sNodeIPPoolStart`, `k8sNodeIPPoolEnd`, `gatewayIPAddress` ,`applianceControlPlaneIpAddress` are optional. You may choose to skip all the optional fields or provide values for all. If you choose not to provide the optional fields, then you must use /28 address space for `networkCIDRForApplianceVM`
 
     **Json example**
     ```json
@@ -306,9 +306,9 @@ When the extension installation steps are completed, they trigger deployment and
 
 ## Change Arc appliance credential
 
-When **cloudadmin** credentials are updated, use the following steps to update the credentials in the appliance store.
+When **cloud admin** credentials are updated, use the following steps to update the credentials in the appliance store.
 
-1. Log into the jumpbox VM from where onboarding was performed. Change the directory to **onboarding directory**.
+1. Log in to the jumpbox VM from where onboarding was performed. Change the directory to **onboarding directory**.
 1. Run the following command for Windows-based jumpbox VM.
 
     `./.temp/.env/Scripts/activate`
@@ -344,7 +344,7 @@ Use the following steps to perform a manual upgrade for Arc appliance virtual ma
     1. Power off the VM.
     1. Delete the VM.
 1. Delete the download template corresponding to the VM.
-1. Delete the resource bridge ARM resource.
+1. Delete the resource bridge Azure Resource Manager resource.
 1. Get the previous script `Config_avs` file and add the following configuration item:
     1. `"register":false`
 1. Download the latest version of the Azure VMware Solution onboarding script.
@@ -361,7 +361,7 @@ Use the following steps to uninstall extensions from the portal.
 >[!NOTE]
 >**Steps 2-5** must be performed for all the VMs that have VM extensions installed.
 
-1. Log into your Azure VMware Solution private cloud. 
+1. Log in to your Azure VMware Solution private cloud. 
 1. Select **Virtual machines** in **Private cloud**, found in the left navigation under “Arc-enabled VMware resources”.
 1. Search and select the virtual machine where you have **Guest management** enabled.
 1. Select **Extensions**.
@@ -401,9 +401,9 @@ For the final step, you'll need to delete the resource bridge VM and the VM temp
 
 ## Preview FAQ
 
-**Is Arc supported in all the Azure VMware Solution regions?**
+**Region support for Azure VMware Solution**
 
-Arc is supported in EastUS, WestEU, UK South, Australia East, Canada Central and Southeast Asia regions however we are working to extend the regional support.
+Arc for Azure VMware Solution is supported in all regions where Arc for VMware vSphere on-premises is supported. For more details, see [Azure Arc-enabled VMware vSphere](https://learn.microsoft.com/azure/azure-arc/vmware-vsphere/overview).
 
 **How does support work?**
 
@@ -419,7 +419,7 @@ Yes
 
 **Is DHCP support available?**
 
-DHCP support is not available to customers at this time, we only support static IP.
+DHCP support isn't available to customers at this time, we only support static IP.
 
 >[!NOTE]
 > This is Azure VMware Solution 2.0 only. It's not available for Azure VMware Solution by Cloudsimple.

articles/batch/batch-customer-managed-key.md

@@ -42,8 +42,8 @@ resourceGroupName='myResourceGroup'
 accountName='mybatchaccount'
 
 az batch account create \
-    -n $accountName \
-    -g $resourceGroupName \
+    --name $accountName \
+    --resource-group $resourceGroupName \
     --locations regionName='West US 2' \
     --identity 'SystemAssigned'
 ```
@@ -52,8 +52,8 @@ After the account is created, you can verify that system-assigned managed identi
 
 ```azurecli
 az batch account show \
-    -n $accountName \
-    -g $resourceGroupName \
+    --name $accountName \
+    --resource-group $resourceGroupName \
     --query identity
 ```
 
@@ -109,14 +109,14 @@ In the [Azure portal](https://portal.azure.com/), go to the Batch account page.
 
 ### Azure CLI
 
-After the Batch account is created with system-assigned managed identity and the access to Key Vault is granted, update the Batch account with the `{Key Identifier}` URL under `keyVaultProperties` parameter. Also set **encryption_key_source** as `Microsoft.KeyVault`.
+After the Batch account is created with system-assigned managed identity and the access to Key Vault is granted, update the Batch account with the `{Key Identifier}` URL under `keyVaultProperties` parameter. Also set `--encryption-key-source` as `Microsoft.KeyVault`.
 
 ```azurecli
 az batch account set \
-    -n $accountName \
-    -g $resourceGroupName \
-    --encryption_key_source Microsoft.KeyVault \
-    --encryption_key_identifier {YourKeyIdentifier} 
+    --name $accountName \
+    --resource-group $resourceGroupName \
+    --encryption-key-source Microsoft.KeyVault \
+    --encryption-key-identifier {YourKeyIdentifier}
 ```
 
 ## Create a Batch account with user-assigned managed identity and customer-managed keys
@@ -159,9 +159,9 @@ You can also use Azure CLI to update the version.
 
 ```azurecli
 az batch account set \
-    -n $accountName \
-    -g $resourceGroupName \
-    --encryption_key_identifier {YourKeyIdentifierWithNewVersion} 
+    --name $accountName \
+    --resource-group $resourceGroupName \
+    --encryption-key-identifier {YourKeyIdentifierWithNewVersion}
 ```
 
 ## Use a different key for Batch encryption
@@ -176,9 +176,9 @@ You can also use Azure CLI to use a different key.
 
 ```azurecli
 az batch account set \
-    -n $accountName \
-    -g $resourceGroupName \
-    --encryption_key_identifier {YourNewKeyIdentifier} 
+    --name $accountName \
+    --resource-group $resourceGroupName \
+    --encryption-key-identifier {YourNewKeyIdentifier}
 ```
 
 ## Frequently asked questions

articles/batch/jobs-and-tasks.md

@@ -19,7 +19,7 @@ A job specifies the [pool](nodes-and-pools.md#pools) in which the work is to be
 
 You can assign an optional job priority to jobs that you create. The Batch service uses the priority value of the job to determine the order of scheduling (for all tasks within the job) wtihin each pool.
 
-To update the priority of a job, call the [Update the properties of a job](/rest/api/batchservice/job/update) operation (Batch REST), or modify the [CloudJob.Priority](/dotnet/api/microsoft.azure.batch.cloudjob.priority) (Batch .NET). Priority values range from -1000 (lowest priority) to 1000 (highest priority).
+To update the priority of a job, call the [Update the properties of a job](/rest/api/batchservice/job/update) operation (Batch REST), or modify the [CloudJob.Priority](/dotnet/api/microsoft.azure.batch.cloudjob.priority) (Batch .NET). Priority values range from -1000 (lowest priority) to +1000 (highest priority).
 
 Within the same pool, higher-priority jobs have scheduling precedence over lower-priority jobs. Tasks in lower-priority jobs that are already running won't be preempted by tasks in a higher-priority job. Jobs with the same priority level have an equal chance of being scheduled, and ordering of task execution is not defined.
 

articles/cognitive-services/openai/reference.md

@@ -175,5 +175,5 @@ curl https://YOUR_RESOURCE_NAME.openai.azure.com/openai/deployments/YOUR_DEPLOYM
 
 ## Next steps
 
-Learn about [managing deployments, models, and finetuning with the REST API](/rest/api/cognitiveservices/azureopenai/deployments/create).
+Learn about [managing deployments, models, and finetuning with the REST API](/rest/api/cognitiveservices/azureopenaistable/deployments/create).
 Learn more about the [underlying models that power Azure OpenAI](./concepts/models.md).