Merge branch 'main' into patch-49

sreekzz · web-flow · commit 09981beea4b9 · 2024-05-23T20:03:11.000+05:30
diff --git a/articles/ai-services/openai/how-to/deployment-types.md b/articles/ai-services/openai/how-to/deployment-types.md
@@ -29,13 +29,13 @@ Our global deployments will be the first location for all new models and feature
 Azure OpenAI offers three types of deployments. These provide a varied level of capabilities that provide trade-offs on: throughput, SLAs, and price. Below is a summary of the options followed by a deeper description of each.
 
 | **Offering** | **Global-Standard** <sup>**1**</sup> | **Standard** | **Provisioned**  |
-|---|---|---|---|
+|---|:---|:---|:---|
 | **Best suited for**      | Applications that don’t require data residency. Recommended starting place for customers. | For customers with data residency requirements. Optimized for low to medium volume. | Real-time scoring for large consistent volume. Includes the highest commitments and limits.|
 | **How it works**         | Traffic may be routed anywhere in the world | | |
 | **Getting started**      | [Model deployment](./create-resource.md) | [Model deployment](./create-resource.md) | [Provisioned onboarding](./provisioned-throughput-onboarding.md) |
 | **Cost**                 | [Baseline](https://azure.microsoft.com/pricing/details/cognitive-services/openai-service/) | [Regional Pricing](https://azure.microsoft.com/pricing/details/cognitive-services/openai-service/) | May experience cost savings for consistent usage |
 | **What you get**         | Easy access to all new models with highest default pay-per-call limits.<br><br> Customers with high volume usage may see higher latency variability | Easy access with [SLA on availability](https://azure.microsoft.com/support/legal/sla/). Optimized for low to medium volume workloads with high burstiness. <br><br>Customers with high consistent volume may experience greater latency variability. | Regional access with very high & predictable throughput. Determine throughput per PTU using the provided [capacity calculator](./provisioned-throughput-onboarding.md#estimate-provisioned-throughput-and-cost) |
-| **What you don’t get**   | Data residency guarantees | High volume w/consistent low latency | Pay-per-call flexibility |
+| **What you don’t get**   | ❌Data residency guarantees | ❌High volume w/consistent low latency | ❌Pay-per-call flexibility |
 | **Per-call Latency**     | Optimized for real-time calling & low to medium volume usage. Customers with high volume usage may see higher latency variability. Threshold set per model | Optimized for real-time calling & low to medium volume usage. Customers with high volume usage may see higher latency variability. Threshold set per model | Optimized for real-time. |
 | **Sku Name in code**     |    `GlobalStandard`               | `Standard`   |      `ProvisionedManaged`       |
 | **Billing model**        | Pay-per-token | Pay-per-token | Monthly Commitments |
diff --git a/articles/azure-monitor/logs/cost-logs.md b/articles/azure-monitor/logs/cost-logs.md
@@ -44,7 +44,7 @@ The following [standard columns](log-standard-columns.md) are common to all tabl
 
 ### Excluded tables
 
-Some tables are free from data ingestion charges altogether, including [AzureActivity](/azure/azure-monitor/reference/tables/azureactivity), [Heartbeat](/azure/azure-monitor/reference/tables/heartbeat), [Usage](/azure/azure-monitor/reference/tables/usage), and [Operation](/azure/azure-monitor/reference/tables/operation). This information will always be indicated by the [_IsBillable](log-standard-columns.md#_isbillable) column, which indicates whether a record was excluded from billing for data ingestion, retention and archive.
+Some tables are free from data ingestion charges altogether, including, for example, [AzureActivity](/azure/azure-monitor/reference/tables/azureactivity), [Heartbeat](/azure/azure-monitor/reference/tables/heartbeat), [Usage](/azure/azure-monitor/reference/tables/usage), and [Operation](/azure/azure-monitor/reference/tables/operation). This information will always be indicated by the [_IsBillable](log-standard-columns.md#_isbillable) column, which indicates whether a record was excluded from billing for data ingestion, retention and archive.
 
 ### Charges for other solutions and services
 
diff --git a/articles/communication-services/how-tos/telephony/domain-validation.md b/articles/communication-services/how-tos/telephony/domain-validation.md
@@ -6,7 +6,7 @@ author: boris-bazilevskiy
 
 ms.service: azure-communication-services
 ms.subservice: pstn
-ms.date: 10/02/2023
+ms.date: 05/23/2024
 ms.topic: how-to
 ms.custom: include file
 ms.author: nikuklic
@@ -23,8 +23,7 @@ To use direct routing in Azure Communication Services, you need to validate that
 When you're verifying the ownership of the SBC FQDN, keep in mind that the `*.onmicrosoft.com` and `*.azure.com` domain names aren't supported. For example, if you have two domain names, `contoso.com` and `contoso.onmicrosoft.com`, use `sbc.contoso.com` as the SBC name.
 
 Validating domain part makes sense if you plan to add multiple SBCs from the same domain name space. For example if you're using `sbc-eu.contoso.com`, `sbc-us.contoso.com`, and `sbc-af.contoso.com` you can validate `contoso.com` domain once and add SBCs from that domain later without extra validation.
-Validating entire FQDN is helpful if you're a service provider and don't want to validate your base domain ownership with every customer. For example if you're running SBCs `customer1.Azure Communication Services.adatum.biz`, `customer2.Azure Communication Services.adatum.biz`, and `customer3.Azure Communication Services.adatum.biz`, you don't need to validate `acs.adatum.biz` for every Communication resource, instead you validate the entire FQDN each time. This option provides more granular security approach.
-
+Validating entire FQDN is helpful if you're a service provider and don't want to validate your base domain ownership with every customer. In that case, you must validate base domain only in resource you control. For example if you're running SBCs `customer1.acs.adatum.biz`, `customer2.acs.adatum.biz`, and `customer3.acs.adatum.biz`, you don't need to validate `acs.adatum.biz` for every Communication resource, instead you validate `acs.adatum.biz` in your resource (resource you own), and your customers validate the entire FQDN as a domain name in their resources. This option provides more granular security approach.
 
 ## Add a new domain name
 
diff --git a/articles/container-apps/java-config-server-usage.md b/articles/container-apps/java-config-server-usage.md
@@ -1,12 +1,12 @@
 ---
-title: Configure settings for the Spring Cloud Configure Server component in Azure Container Apps (preview)
+title: Configure settings for the Spring Cloud Config Server component in Azure Container Apps (preview)
 description: Learn how to configure a Spring Cloud Config Server component for your container app.
 services: container-apps
 author: craigshoemaker
 ms.service: container-apps
 ms.custom: devx-track-azurecli
 ms.topic: how-to
-ms.date: 03/13/2024
+ms.date: 05/23/2024
 ms.author: cshoe
 ---
 
diff --git a/articles/dms/migrate-azure-mysql-consistent-backup.md b/articles/dms/migrate-azure-mysql-consistent-backup.md
@@ -28,8 +28,9 @@ With this feature, we don't take a read lock on the server. We instead read tabl
 :::image type="content" source="media/migrate-azure-mysql-consistent-backup/reconciliation-tab.png" alt-text="MySQL to Azure Database for MySQL Data Migration Wizard - Reconciliation progress." lightbox="media/migrate-azure-mysql-consistent-backup/reconciliation-tab.png":::
 
 Key features of Consistent Snapshot without locks:
-    *Ability to support heavy workload servers or servers with long-running transactions without the need for read locks.
-    *Resilient in completing migrations even in the event of failures caused by transient network/server blips that result in loss of all the precreated connections.
+
+* Ability to support heavy workload servers or servers with long-running transactions without the need for read locks.
+* Resilient in completing migrations even in the event of failures caused by transient network/server blips that result in loss of all the pre-created connections.
 
 ### Enable Consistent Snapshot with read lock (GA)
 
diff --git a/articles/hdinsight/hadoop/apache-hadoop-use-hive-dotnet-sdk.md b/articles/hdinsight/hadoop/apache-hadoop-use-hive-dotnet-sdk.md
@@ -4,7 +4,7 @@ description: Learn how to submit Apache Hadoop jobs to Azure HDInsight Apache Ha
 ms.service: hdinsight
 ms.topic: how-to
 ms.custom: hdinsightactive, devx-track-csharp, devx-track-dotnet
-ms.date: 05/23/2023
+ms.date: 05/23/2024
 ---
 
 # Run Apache Hive queries using HDInsight .NET SDK
diff --git a/articles/hdinsight/hdinsight-hadoop-manage-ambari.md b/articles/hdinsight/hdinsight-hadoop-manage-ambari.md
@@ -4,7 +4,7 @@ description: Learn how to use Apache Ambari UI to monitor and manage HDInsight c
 ms.service: hdinsight
 ms.topic: how-to
 ms.custom: hdinsightactive
-ms.date: 04/25/2023
+ms.date: 05/23/2024
 ---
 
 # Manage HDInsight clusters by using the Apache Ambari Web UI
diff --git a/articles/hdinsight/hdinsight-restrict-outbound-traffic.md b/articles/hdinsight/hdinsight-restrict-outbound-traffic.md
@@ -3,7 +3,7 @@ title: Configure outbound network traffic restriction - Azure HDInsight
 description: Learn how to configure outbound network traffic restriction for Azure HDInsight clusters.
 ms.service: hdinsight
 ms.topic: how-to
-ms.date: 04/24/2023
+ms.date: 05/23/2024
 ---
 
 # Configure outbound network traffic for Azure HDInsight clusters using Firewall
@@ -26,7 +26,7 @@ A summary of the steps to lock down egress from your existing HDInsight with Azu
 
 1. Create a subnet.
 1. Create a firewall.
-1. Add application rules to the firewall.
+1. `Add application` rules to the firewall.
 1. Add network rules to the firewall.
 1. Create a routing table.
 
@@ -66,7 +66,7 @@ Create an application rule collection that allows the cluster to send and receiv
 
     **Target FQDNs section**
 
-    | Name | Source addresses | Protocol:Port | Target FQDNS | Notes |
+    | Name | Source addresses | Protocol: Port | Target FQDNS | Notes |
     | --- | --- | --- | --- | --- |
     | Rule_2 | * | https:443 | login.windows.net | Allows Windows login activity |
     | Rule_3 | * | https:443 | login.microsoftonline.com | Allows Windows login activity |
@@ -81,9 +81,9 @@ Create an application rule collection that allows the cluster to send and receiv
 
 Create the network rules to correctly configure your HDInsight cluster. 
 
-1. Continuing from the prior step, navigate to **Network rule collection** > **+ Add network rule collection**.
+1. Continuing from the prior step, navigate to **Network rule collection** > `+ Add network rule collection`.
 
-1. On the **Add network rule collection** screen, provide the following information:
+1. On the `Add network rule collection` screen, provide the following information:
 
     **Top section**
 
@@ -97,7 +97,7 @@ Create the network rules to correctly configure your HDInsight cluster.
 
     | Name | Protocol | Source Addresses | Service Tags | Destination Ports | Notes |
     | --- | --- | --- | --- | --- | --- |
-    | Rule_6 | TCP | * | SQL | 1433 , 11000-11999 | If you are using the default sql servers provided by HDInsight, configure a network rule in the Service Tags section for SQL that will allow you to log and audit SQL traffic. Unless you configured Service Endpoints for SQL Server on the HDInsight subnet, which will bypass the firewall. If you are using custom SQL server for Ambari, Oozie, Ranger and Hive metastores then you only need to allow the traffic to your own custom SQL Servers. Refer to [Azure SQL Database and Azure Synapse Analytics connectivity architecture](/azure/azure-sql/database/connectivity-architecture) to see why 11000-11999 port range is also needed in addition to 1433. |
+    | Rule_6 | TCP | * | SQL | 1433, 11000-11999 | If you are using the default sql servers provided by HDInsight, configure a network rule in the Service Tags section for SQL that will allow you to log and audit SQL traffic. Unless you configured Service Endpoints for SQL Server on the HDInsight subnet, which will bypass the firewall. If you are using custom SQL server for Ambari, Oozie, Ranger and Hive metastore then you only need to allow the traffic to your own custom SQL Servers. Refer to [Azure SQL Database and Azure Synapse Analytics connectivity architecture](/azure/azure-sql/database/connectivity-architecture) to see why 11000-11999 port range is also needed in addition to 1433. |
     | Rule_7 | TCP | * | Azure Monitor | * | (optional) Customers who plan to use auto scale feature should add this rule. |
     
    :::image type="content" source="./media/hdinsight-restrict-outbound-traffic/hdinsight-restrict-outbound-traffic-add-network-rule-collection.png" alt-text="Title: Enter application rule collection.":::
diff --git a/articles/hdinsight/hdinsight-rotate-storage-keys.md b/articles/hdinsight/hdinsight-rotate-storage-keys.md
@@ -3,7 +3,7 @@ title: Update Azure Storage account access key in Azure HDInsight
 description: Learn how to update Azure Storage account access key in Azure HDInsight cluster.
 ms.service: hdinsight
 ms.topic: how-to
-ms.date: 04/26/2023
+ms.date: 05/23/2024
 ---
 
 # Update Azure storage account access keys in HDInsight cluster
diff --git a/articles/mysql/migrate/migrate-single-flexible-in-place-auto-migration.md b/articles/mysql/migrate/migrate-single-flexible-in-place-auto-migration.md
@@ -30,7 +30,7 @@ The in-place migration provides a highly resilient and self-healing offline migr
 
 ## Eligibility
 
-If you own a Single Server workload with Basic, General Purpose or Memory Optimized SKU, data storage used <= 20 GiB and no complex features (CMK, Microsoft Entra ID, Read Replica, Private Link) enabled, you can now nominate yourself (if not already scheduled by the service) for automigration by submitting your server details through this [form](https://forms.office.com/Pages/ResponsePage.aspx?id=v4j5cvGGr0GRqy180BHbR4lhLelkCklCuumNujnaQ-ZUQzRKSVBBV0VXTFRMSDFKSUtLUDlaNTA5Wi4u).
+If you own a Single Server workload with data storage used <= 100 GiB and no complex features (CMK, Microsoft Entra ID, Read Replica, Private Link) enabled, you can now nominate yourself (if not already scheduled by the service) for automigration by submitting your server details through this [form](https://forms.office.com/Pages/ResponsePage.aspx?id=v4j5cvGGr0GRqy180BHbR4lhLelkCklCuumNujnaQ-ZUQzRKSVBBV0VXTFRMSDFKSUtLUDlaNTA5Wi4u).
 
 ## Configure migration alerts and review migration schedule
 
diff --git a/articles/mysql/single-server/whats-happening-to-mysql-single-server.md b/articles/mysql/single-server/whats-happening-to-mysql-single-server.md
@@ -40,7 +40,7 @@ Learn how to migrate from Azure Database for MySQL - Single Server to Azure Data
 For more information on migrating from Single Server to Flexible Server using other migration tools, visit [Select the right tools for migration to Azure Database for MySQL](../migrate/how-to-decide-on-right-migration-tools.md).
 
 > [!NOTE]  
-> In-place auto-migration from Azure Database for MySQL – Single Server to Flexible Server is a service-initiated in-place migration during planned maintenance window for select Single Server database workloads. The eligible servers are identified by the service and are sent an advance notification detailing steps to review migration details. If you own a Single Server workload with Basic or GP SKU, data storage used <= 20 GiB and no complex features (CMK, Microsoft Entra ID, Read Replica, Private Link) enabled, you can now nominate yourself (if not already scheduled by the service) for auto-migration by submitting your server details through this [form](https://forms.office.com/Pages/ResponsePage.aspx?id=v4j5cvGGr0GRqy180BHbR4lhLelkCklCuumNujnaQ-ZUQzRKSVBBV0VXTFRMSDFKSUtLUDlaNTA5Wi4u). All other Single Server workloads are recommended to use user-initiated migration tooling offered by Azure - Azure DMS, Azure Database for MySQL Import to migrate. Learn more about in-place auto-migration [here](../migrate/migrate-single-flexible-in-place-auto-migration.md).
+> In-place auto-migration from Azure Database for MySQL – Single Server to Flexible Server is a service-initiated in-place migration during planned maintenance window for select Single Server database workloads. The eligible servers are identified by the service and are sent an advance notification detailing steps to review migration details. If you own a Single Server workload with data storage used <= 100 GiB and no complex features (CMK, Microsoft Entra ID, Read Replica, Private Link) enabled, you can now nominate yourself (if not already scheduled by the service) for auto-migration by submitting your server details through this [form](https://forms.office.com/Pages/ResponsePage.aspx?id=v4j5cvGGr0GRqy180BHbR4lhLelkCklCuumNujnaQ-ZUQzRKSVBBV0VXTFRMSDFKSUtLUDlaNTA5Wi4u). All other Single Server workloads are recommended to use user-initiated migration tooling offered by Azure - Azure DMS, Azure Database for MySQL Import to migrate. Learn more about in-place auto-migration [here](../migrate/migrate-single-flexible-in-place-auto-migration.md).
 
 ## What happens post sunset date (September 16, 2024)?
 
diff --git a/articles/security/fundamentals/customer-lockbox-overview.md b/articles/security/fundamentals/customer-lockbox-overview.md
@@ -26,6 +26,7 @@ The following services are currently supported for Customer Lockbox for Microsof
 - Azure AI Search
 - Azure Chaos Studio
 - Azure Cognitive Services
+- Azure Communications Gateway
 - Azure Container Registry
 - Azure Data Box
 - Azure Data Explorer
@@ -40,6 +41,7 @@ The following services are currently supported for Customer Lockbox for Microsof
 - Azure HDInsight
 - Azure Health Bot
 - Azure Intelligent Recommendations
+- Azure Information Protection
 - Azure Kubernetes Service
 - Azure Load Testing (CloudNative Testing)
 - Azure Logic Apps
diff --git a/articles/virtual-desktop/add-session-hosts-host-pool.md b/articles/virtual-desktop/add-session-hosts-host-pool.md
@@ -157,7 +157,7 @@ Here's how to create session hosts and register them to a host pool using the Az
 
 1. The **Basics** tab will be greyed out because you're using the existing host pool. Select **Next: Virtual Machines**.
 
-1. On the **Virtual machines** tab, complete the following information, depending on whether you want to create session hosts on Azure or Azure Stack HCI:<br /><br />
+1. On the **Virtual machines** tab, expand one of the following sections and complete the information, depending on whether you want to create session hosts on Azure or Azure Stack HCI. For guidance on sizing session host virtual machines, see [Session host virtual machine sizing guidelines](/windows-server/remote/remote-desktop-services/virtual-machine-recs).<br /><br />
 
    <details>
        <summary>To add session hosts on <b>Azure</b>, select to expand this section.</summary>
@@ -170,7 +170,7 @@ Here's how to create session hosts and register them to a host pool using the Az
       | Availability options | Select from **[availability zones](../reliability/availability-zones-overview.md)**, **[availability set](../virtual-machines/availability-set-overview.md)**, or **No infrastructure dependency required**. If you select availability zones or availability set, complete the extra parameters that appear.  |
       | Security type | Select from **Standard**, **[Trusted launch virtual machines](../virtual-machines/trusted-launch.md)**, or **[Confidential virtual machines](../confidential-computing/confidential-vm-overview.md)**.<br /><br />- If you select **Trusted launch virtual machines**, options for **secure boot** and **vTPM** are automatically selected.<br /><br />- If you select **Confidential virtual machines**, options for **secure boot**, **vTPM**, and **integrity monitoring** are automatically selected. You can't opt out of vTPM when using a confidential VM. |
       | Image | Select the OS image you want to use from the list, or select **See all images** to see more, including any images you've created and stored as an [Azure Compute Gallery shared image](../virtual-machines/shared-image-galleries.md) or a [managed image](../virtual-machines/windows/capture-image-resource.yml). |
-      | Virtual machine size | Select a SKU. If you want to use different SKU, select **Change size**, then select from the list. |
+      | Virtual machine size | Select a SKU. If you want to use different SKU, select **Change size**, then select a value from the list. |
       | Hibernate (preview) | Check the box to enable hibernate. Hibernate is only available for personal host pools. For more information, see [Hibernation in virtual machines](/azure/virtual-machines/hibernate-resume). If you're using Teams media optimizations you should update the [WebRTC redirector service to 1.45.2310.13001](whats-new-webrtc.md#updates-for-version-145231013001).|   
       | Number of VMs | Enter the number of virtual machines you want to deploy. You can deploy up to 400 session hosts at this point if you wish (depending on your [subscription quota](../quotas/view-quotas.md)), or you can add more later.<br /><br />For more information, see [Azure Virtual Desktop service limits](../azure-resource-manager/management/azure-subscription-service-limits.md#azure-virtual-desktop-service-limits) and [Virtual Machines limits](../azure-resource-manager/management/azure-subscription-service-limits.md#virtual-machines-limits---azure-resource-manager). |
       | OS disk type | Select the disk type to use for your session hosts. We recommend only **Premium SSD** is used for production workloads. |
diff --git a/articles/virtual-desktop/deploy-azure-virtual-desktop.md b/articles/virtual-desktop/deploy-azure-virtual-desktop.md
diff --git a/articles/virtual-desktop/includes/include-whats-new-client-ios-ipados.md b/articles/virtual-desktop/includes/include-whats-new-client-ios-ipados.md
diff --git a/articles/virtual-desktop/whats-new-client-ios-ipados.md b/articles/virtual-desktop/whats-new-client-ios-ipados.md
