Merge pull request #201385 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/active-directory/app-proxy/application-proxy-configure-custom-domain.md

@@ -103,7 +103,7 @@ To publish your app through Application Proxy with a custom domain:
 
    ![Add CNAME DNS entry](./media/application-proxy-configure-custom-domain/dns-info.png)
 
-10. Follow the instructions at [Manage DNS records and record sets by using the Azure portal](../../dns/dns-operations-recordsets-portal.md) to add a DNS record that redirects the new external URL to the *msappproxy.net* domain.
+10. Follow the instructions at [Manage DNS records and record sets by using the Azure portal](../../dns/dns-operations-recordsets-portal.md) to add a DNS record that redirects the new external URL to the *msappproxy.net* domain in Azure DNS. If a different DNS provider is used, please contact the vendor for the instructions.
 
    > [!IMPORTANT] 
    > Ensure that you are properly using a CNAME record that points to the *msappproxy.net* domain. Do not point records to IP addresses or server DNS names since these are not static and may impact the resiliency of the service.

articles/active-directory/app-proxy/application-proxy-faq.yml

@@ -240,7 +240,7 @@ sections:
               Internal URL: https://app1.contoso.com:/test/
               ```
               
-              Making the external and internal URLs identical is not possible. Different ports or using http and https must be used in the internal and external URLs.
+              Making the external and internal URLs identical is not possible at all, if the internal URL contains a non-standard port (other than TCP 80 / 443).
               
               In some scenarios changes must be done in the configuration of the web app.
 

articles/active-directory/governance/access-reviews-external-users.md

@@ -65,7 +65,7 @@ In addition to the option of removing unwanted external identities from resource
 
 ![upon completion settings](media/access-reviews-external-users/upon-completion-settings.png)
 
-When creating a new Access Review, in the “Upon completion settings” section, for **Action to apply on denied users** you can define **Block users from signing-in for 30 days, then remove user from the tenant**.
+When creating a new Access Review, choose the **Select Teams + groups** option and limit the scope to **Guest users only**. In the “Upon completion settings” section, for **Action to apply on denied users** you can define **Block users from signing-in for 30 days, then remove user from the tenant**.
 
 This setting allows you to identify, block, and delete external identities from your Azure AD tenant. External identities who are reviewed and denied continued access by the reviewer will be blocked and deleted, irrespective of the resource access or group membership they have. This setting is best used as a last step after you have validated that the external users in-review no longer carries resource access and can safely be removed from your tenant or if you want to make sure they are removed, irrespective of their standing access. The “Disable and delete” feature blocks the external user first, taking away their ability to signing into your tenant and accessing resources. Resource access is not revoked in this stage, and in case you wanted to reinstantiate the external user, their ability to log on can be reconfigured. Upon no further action, a blocked external identity will be deleted from the directory after 30 days, removing the account as well as their access.
 

articles/cloud-services-extended-support/available-sizes.md

@@ -18,7 +18,7 @@ This article describes the available virtual machine sizes for Cloud Services (e
 |---|---|
 |[Av2](../virtual-machines/av2-series.md) | 100 | 
 |[D](../virtual-machines/sizes-previous-gen.md?bc=%2fazure%2fvirtual-machines%2flinux%2fbreadcrumb%2ftoc.json&toc=%2fazure%2fvirtual-machines%2flinux%2ftoc.json#d-series) | 160 | 
-|[Dv2](../virtual-machines/dv2-dsv2-series.md) | 160 - 190* |
+|[Dv2](../virtual-machines/dv2-dsv2-series.md) | 210 - 250* |
 |[Dv3](../virtual-machines/dv3-dsv3-series.md) | 160 - 190* |
 |[Dav4](../virtual-machines/dav4-dasv4-series.md) | 230 - 260 |
 |[Eav4](../virtual-machines/eav4-easv4-series.md) | 230 - 260 |

articles/cosmos-db/how-to-setup-rbac.md

@@ -476,7 +476,7 @@ Azure portal support for role management is not available yet.
 
 ### Which SDKs in Azure Cosmos DB SQL API support RBAC?
 
-The [.NET V3](sql-api-sdk-dotnet-standard.md), [Java V4](sql-api-sdk-java-v4.md) and [JavaScript V3](sql-api-sdk-node.md) SDKs are currently supported.
+The [.NET V3](sql-api-sdk-dotnet-standard.md), [Java V4](sql-api-sdk-java-v4.md), [JavaScript V3](sql-api-sdk-node.md) and [Python V4.3+](sql-api-sdk-python.md) SDKs are currently supported.
 
 ### Is the Azure AD token automatically refreshed by the Azure Cosmos DB SDKs when it expires?
 

articles/data-factory/concepts-data-flow-performance-pipelines.md

@@ -30,7 +30,7 @@ If you execute your data flow activities in sequence, it is recommended that you
 
 ## Overloading a single data flow
 
-If you put all of your logic inside of a single data flow, the service will execute the entire job on a single Spark instance. While this may seem like a way to reduce costs, it mixes together different logical flows and can be difficult to monitor and debug. If one component fails, all other parts of the job will fail as well. Organizing data flows by independent flows of business logic is recommended. If your data flow becomes too large, splitting it into separates components will make monitoring and debugging easier. While there is no hard limit on the number of transformations in a data flow, having too many will make the job complex.
+If you put all of your logic inside of a single data flow, the service will execute the entire job on a single Spark instance. While this may seem like a way to reduce costs, it mixes together different logical flows and can be difficult to monitor and debug. If one component fails, all other parts of the job will fail as well. Organizing data flows by independent flows of business logic is recommended. If your data flow becomes too large, splitting it into separate components will make monitoring and debugging easier. While there is no hard limit on the number of transformations in a data flow, having too many will make the job complex.
 
 ## Execute sinks in parallel
 

articles/iot-dps/how-to-troubleshoot-dps.md

@@ -62,8 +62,11 @@ Use this table to understand and resolve common errors.
 |-------|------------|------------|
 | 400 | The body of the request is not valid; for example, it cannot be parsed, or the object cannot be validated.| 400 Bad format |
 | 401 | The authorization token cannot be validated; for example, it is expired or does not apply to the request’s URI. This error code is also returned to devices as part of the TPM attestation flow. | 401 Unauthorized|
-| 404 | The Device Provisioning Service instance, or a resource (e.g. an enrollment) does not exist. |404 Not Found |
+| 404 | The Device Provisioning Service instance, or a resource (e.g. an enrollment) does not exist. | 404 Not Found|
+| 405 | The client service knows the request method, but the target service doesn't recognize this method; for example, a rest operations is missing the enrollment or registration Id parameters | 405 Method Not Allowed |
+| 409 | The request could not be completed due to a conflict with the current state of the target Device Provisioning Service instance; for example, the customer has already created the data point and is attempting to recreate the same datapoint again. | 409 Conflict |
 | 412 | The ETag in the request does not match the ETag of the existing resource, as per RFC7232. | 412 Precondition failed |
+| 415 | The server refuses to accept the request because the payload format is in an unsupported format. For supported formats, see [Iot Hub Device Provisioning Service REST API](/rest/api/iot-dps/) | 415 Unsupported Media Type |
 | 429 | Operations are being throttled by the service. For specific service limits, see [IoT Hub Device Provisioning Service limits](../azure-resource-manager/management/azure-subscription-service-limits.md#iot-hub-device-provisioning-service-limits). | 429 Too many requests |
 | 500 | An internal error occurred. | 500 Internal Server Error|
 

articles/search/cognitive-search-custom-skill-interface.md

@@ -134,7 +134,7 @@ When you create a Web API enricher, you can describe HTTP headers and parameters
     "skills": [
       {
         "@odata.type": "#Microsoft.Skills.Custom.WebApiSkill",
-        "name": "myCustomSkill"
+        "name": "myCustomSkill",
         "description": "This skill calls an Azure function, which in turn calls TA sentiment",
         "uri": "https://indexer-e2e-webskill.azurewebsites.net/api/DateExtractor?language=en",
         "context": "/document",
@@ -172,4 +172,4 @@ This article covered the interface requirements necessary for integrating a cust
 + [Example: Creating a custom skill for AI enrichment](cognitive-search-create-custom-skill-example.md)
 + [How to define a skillset](cognitive-search-defining-skillset.md)
 + [Create Skillset (REST)](/rest/api/searchservice/create-skillset)
-+ [How to map enriched fields](cognitive-search-output-field-mapping.md)
++ [How to map enriched fields](cognitive-search-output-field-mapping.md)

articles/storage/queues/authorize-managed-identity.md

@@ -51,13 +51,12 @@ The following code example shows how to get the authenticated token credential a
 public static void CreateQueue(string accountName, string queueName)
 {
     // Construct the blob container endpoint from the arguments.
-    string queueEndpoint = string.Format("https://{0}.queue.core.windows.net/{1}",
-                                                accountName,
-                                                queueName);
+    string queueEndpoint = $"https://{accountName}.queue.core.windows.net/{queueName}";
 
     // Get a token credential and create a service client object for the queue.
-    QueueClient queueClient = new QueueClient(new Uri(queueEndpoint), 
-                                                new DefaultAzureCredential());
+    QueueClient queueClient = new QueueClient(
+        new Uri(queueEndpoint), 
+        new DefaultAzureCredential());
 
     try
     {

articles/virtual-machines/ebdsv5-ebsv5-series.md

@@ -71,15 +71,15 @@ Ebsv5-series sizes run on the Intel® Xeon® Platinum 8272CL (Ice Lake). These V
 - [Ephemeral OS Disks](ephemeral-os-disks.md): Not supported
 - Nested virtualization: Supported
 
-| Size | vCPU | Memory: GiB | Max data disks | Max temp storage throughput: IOPS / MBps | Max uncached storage throughput: IOPS / MBps | Max burst uncached disk throughput: IOPS/MBp | Max NICs | Network bandwidth |
-| --- | --- | --- | --- | --- | --- | --- | --- | --- |
-| Standard_E2bs_v5 | 2 | 16 | 4 | 9000/125 | 5500/156 | 10000/1200 | 2 | 10000 |
-| Standard_E4bs_v5 | 4 | 32 | 8 | 19000/250 | 11000/350 | 20000/1200 | 2 | 10000 |
-| Standard_E8bs_v5 | 8 | 64 | 16 | 38000/500 | 22000/625 | 40000/1200 | 4 | 10000 |
-| Standard_E16bs_v5 | 16 | 128 | 32 | 75000/1000 | 44000/1250 | 64000/2000 | 8 | 12500 
-| Standard_E32bs_v5 | 32 | 256 | 32 | 150000/1250 | 88000/2500 | 120000/4000 | 8 | 16000 |
-| Standard_E48bs_v5 | 48 | 384 | 32 | 225000/2000 | 120000/4000 | 120000/4000 | 8 | 16000 |
-| Standard_E64bs_v5 | 64 | 512 | 32 | 300000/4000 | 120000/4000 | 120000/4000 | 8 | 20000 | 
+| Size | vCPU | Memory: GiB | Max data disks | Max uncached storage throughput: IOPS / MBps | Max burst uncached disk throughput: IOPS/MBp | Max NICs | Network bandwidth |
+| --- | --- | --- | --- | --- | --- | --- | --- |
+| Standard_E2bs_v5 | 2 | 16 | 4 | 5500/156 | 10000/1200 | 2 | 10000 |
+| Standard_E4bs_v5 | 4 | 32 | 8 | 11000/350 | 20000/1200 | 2 | 10000 |
+| Standard_E8bs_v5 | 8 | 64 | 16 | 22000/625 | 40000/1200 | 4 | 10000 |
+| Standard_E16bs_v5 | 16 | 128 | 32 | 44000/1250 | 64000/2000 | 8 | 12500 
+| Standard_E32bs_v5 | 32 | 256 | 32 | 88000/2500 | 120000/4000 | 8 | 16000 |
+| Standard_E48bs_v5 | 48 | 384 | 32 | 120000/4000 | 120000/4000 | 8 | 16000 |
+| Standard_E64bs_v5 | 64 | 512 | 32 | 120000/4000 | 120000/4000 | 8 | 20000 | 
 
 > [!NOTE]
 > Accelerated networking is required and turned on by default on all Ebsv5 VMs.