Merge pull request #221016 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-provisioning/on-premises-application-provisioning-architecture.md

@@ -37,6 +37,8 @@ There are three primary components to provisioning users into an on-premises app
 
 You don't need to open inbound connections to the corporate network. The provisioning agents only use outbound connections to the provisioning service, which means there's no need to open firewall ports for incoming connections. You also don't need a perimeter (DMZ) network because all connections are outbound and take place over a secure channel.
 
+The required outbound endpoints for the provisioning agents are detailed [here](../cloud-sync/how-to-prerequisites.md#firewall-and-proxy-requirements).
+
 ## ECMA Connector Host architecture
 The ECMA Connector Host has several areas it uses to achieve on-premises provisioning.  The diagram below is a conceptual drawing that presents these individual areas.  The table below describes the areas in more detail.
 

articles/azure-monitor/containers/container-insights-reports.md

@@ -39,7 +39,7 @@ To create a custom workbook based on any of these workbooks, select the **View W
 
 - **Subnet IP Usage**: Interactive IP usage charts for each node within a cluster by the following perspectives:
 
-    - IPs allocated form subnet.
+    - IPs allocated from subnet.
     - IPs assigned to a pod.
 
 >[!NOTE]

articles/communication-services/quickstarts/email/includes/send-email-net.md

@@ -232,7 +232,7 @@ var emailAttachment = new EmailAttachment(
     attachmentFileInBytes
 );
 
-emailMessage.Add(emailAttachment);
+emailMessage.Attachments.Add(emailAttachment);
 ```
 
 You can download the sample app demonstrating this from [GitHub](https://github.com/Azure-Samples/communication-services-dotnet-quickstarts/tree/main/SendEmailAdvanced/SendEmailWithAttachments)

articles/event-grid/receive-events.md

@@ -69,11 +69,11 @@ namespace Function1
                     {
                         log.LogInformation($"Got SubscriptionValidation event data, validation code: {subscriptionValidationEventData.ValidationCode}, topic: {eventGridEvent.Topic}");
                         // Do any additional validation (as required) and then return back the below response
-
-                        var responseData = new SubscriptionValidationResponse()
+                        var responseData = new
                         {
                             ValidationResponse = subscriptionValidationEventData.ValidationCode
                         };
+
                         return new OkObjectResult(responseData);
                     }
                 }
@@ -171,7 +171,7 @@ namespace Function1
                         log.LogInformation($"Got SubscriptionValidation event data, validation code: {subscriptionValidationEventData.ValidationCode}, topic: {eventGridEvent.Topic}");
                         // Do any additional validation (as required) and then return back the below response
 
-                        var responseData = new SubscriptionValidationResponse()
+                        var responseData = new
                         {
                             ValidationResponse = subscriptionValidationEventData.ValidationCode
                         };
@@ -305,7 +305,7 @@ namespace Function1
                         log.LogInformation($"Got SubscriptionValidation event data, validation code: {subscriptionValidationEventData.ValidationCode}, topic: {eventGridEvent.Topic}");
                         // Do any additional validation (as required) and then return back the below response
 
-                        var responseData = new SubscriptionValidationResponse()
+                        var responseData = new
                         {
                             ValidationResponse = subscriptionValidationEventData.ValidationCode
                         };

articles/hdinsight/hdinsight-hadoop-use-data-lake-storage-gen2-azure-cli.md

@@ -65,10 +65,10 @@ az storage account create --name <STORAGEACCOUNTNAME> \
     --kind StorageV2 --hierarchical-namespace true
 ```
 
-Next, sign in to the portal. Add the new user-assigned managed identity to the **Storage Blob Data Contributor** role on the storage account. This step is described in step 3 under [Using the Azure portal](hdinsight-hadoop-use-data-lake-storage-gen2.md).
+Next, sign in to the portal. Add the new user-assigned managed identity to the **Storage Blob Data Owner** role on the storage account. This step is described in step 3 under [Using the Azure portal](hdinsight-hadoop-use-data-lake-storage-gen2.md).
 
  > [!IMPORTANT]
- > Ensure that your storage account has the user-assigned identity with **Storage Blob Data Contributor** role permissions, otherwise cluster creation will fail.
+ > Ensure that your storage account has the user-assigned identity with **Storage Blob Data Owner** role permissions, otherwise cluster creation will fail.
 
 ```azurecli
 az deployment group create --name HDInsightADLSGen2Deployment \

articles/machine-learning/reference-yaml-mltable.md

@@ -31,7 +31,7 @@ The source JSON schema can be found at https://azuremlschemas.azureedge.net/late
 
 
 > [!Note]
-> If you just want to create an data asset for a job or you want to write your own parsing logic in python you could just use `uri_file`, `uri_folder` as mentioned in [CLI (v2) data YAML schema](reference-yaml-data.md).
+> If you just want to create an data asset for a job or you want to write your own parsing logic in Python you could just use `uri_file`, `uri_folder` as mentioned in [CLI (v2) data YAML schema](reference-yaml-data.md).
 
 
 [!INCLUDE [schema note](../../includes/machine-learning-preview-old-json-schema-note.md)]

articles/spring-apps/quickstart-deploy-apps-enterprise.md

@@ -248,7 +248,8 @@ Use the following steps to deploy and build applications. For these steps, make
        --name payment-service \
        --service <Azure-Spring-Apps-service-instance-name> \
        --config-file-pattern payment/default \
-       --source-path apps/acme-payment
+       --source-path apps/acme-payment \
+       --build-env BP_JVM_VERSION=17
    ```
 
 1. Use the following command to build and deploy the catalog service:
@@ -259,7 +260,8 @@ Use the following steps to deploy and build applications. For these steps, make
        --name catalog-service \
        --service <Azure-Spring-Apps-service-instance-name> \
        --config-file-pattern catalog/default \
-       --source-path apps/acme-catalog
+       --source-path apps/acme-catalog \
+       --build-env BP_JVM_VERSION=17
    ```
 
 1. Use the following command to build and deploy the order service: