Merge pull request #296106 from MicrosoftDocs/main

3/11/2025 AM Publish

Author: Taojunshen

articles/azure-netapp-files/azure-netapp-files-quickstart-set-up-account-create-volumes.md

@@ -407,11 +407,6 @@ The following code snippets show how to set up a VNet and create an Azure NetApp
 
 :::code language="terraform" source="~/terraform_samples/quickstart/101-azure-netapp-files/main.tf" range="21-46,64-84":::
 
-> [!IMPORTANT]
-> To prevent accidental deletion of the volume, set `prevent_destroy` to **true** when declaring the provider.
-
-:::code language="terraform" source="~/terraform_samples/quickstart/101-azure-netapp-files/providers.tf" highlight="19":::
-
 ---
 
 ## Clean up resources
@@ -478,7 +473,7 @@ Use the Azure portal, PowerShell, or the Azure CLI to delete the resource group.
 
 # [Terraform](#tab/terraform)
 
-Use the Azure portal, Azure PowerShell, or the Azure CLI to delete the resource group.
+[!INCLUDE [Terraform destroy](~/azure-dev-docs-pr/articles/terraform/includes/terraform-plan-destroy.md)]
 
 ---
 

articles/azure-vmware/attach-azure-netapp-files-to-azure-vmware-solution-hosts.md

@@ -91,7 +91,7 @@ There are some important best practices to follow for optimal performance of NFS
 - Based on your performance requirements, select the correct service level needed for the Azure NetApp Files capacity pool. See [Service levels for Azure NetApp Files](../azure-netapp-files/azure-netapp-files-service-levels.md) to understand the throughput allowed per provisioned TiB for each service level. 
 
     >[!IMPORTANT]
-    > If you've changed the Azure NetApp Files volumes performance tier after creating the volume and datastore, see [Service level change for Azure NetApp files datastore](#service-level-change-for-azure-netapp-files-datastore) to ensure that volume/datastore metadata is in sync to avoid unexpected behavior in the portal or the API due to metadata mismatch. 
+    > If you've changed the Azure NetApp Files volumes performance tier or the volume size after creating the volume and datastore, see [Service level change for Azure NetApp files datastore](#service-level-change-for-azure-netapp-files-datastore) to ensure that volume/datastore metadata is in sync to avoid unexpected behavior in the portal or the API due to metadata mismatch. To do any kind of change to the volume you can use Azure Portal or any other supported solution (CLI\Powershell\API).
     
 - Create one or more volumes based on the required throughput and capacity. See [Performance considerations](../azure-netapp-files/azure-netapp-files-performance-considerations.md) for Azure NetApp Files to understand how volume size, service level, and capacity pool QoS type determines volume throughput. For assistance calculating workload capacity and performance requirements, contact your Azure VMware Solution or Azure NetApp Files field expert. The default maximum number of Azure NetApp Files datastores is 8, but it can be increased to a maximum of 256 by submitting a support ticket. To submit a support ticket, see [Create an Azure support request](/azure/azure-portal/supportability/how-to-create-azure-support-request).
 -  Ensure that the Azure VMware Solution private cloud and the Azure NetApp Files volumes are deployed within the same [availability zone](../reliability/availability-zones-overview.md) using the [the availability zone volume placement](../azure-netapp-files/manage-availability-zone-volume-placement.md) in the same subscription. Information regarding your AVS private cloud's availability zone can be viewed from the overview pane within the AVS private cloud.

articles/confidential-computing/quick-create-confidential-vm-arm.md

@@ -173,7 +173,7 @@ Use this example to create a custom parameter file for a Linux-based confidentia
     New-MgServicePrincipal -AppId bf7b6499-ff71-4aa2-97a4-f372087be7f0 -DisplayName "Confidential VM Orchestrator"
     ```
 
-1. Set up your Azure key vault. For how to use an Azure Key Vault Managed HSM instead, see the next step.
+1. Set up your Azure Key Vault. For how to use an Azure Key Vault Managed HSM instead, see the next step.
 
     1. Create a resource group for your key vault. Your key vault instance and your confidential VM must be in the same Azure region.
 
@@ -198,7 +198,7 @@ Use this example to create a custom parameter file for a Linux-based confidentia
         az keyvault set-policy --name $KeyVault --object-id $cvmAgent.Id --key-permissions get release
         ```
 
-1. (Optional) If you don't want to use an Azure key vault, you can create an Azure Key Vault Managed HSM instead.
+1. (Optional) If you don't want to use an Azure Key Vault, you can create an Azure Key Vault Managed HSM instead.
 
     1. Follow the [quickstart to create an Azure Key Vault Managed HSM](/azure/key-vault/managed-hsm/quick-create-cli) to provision and activate Azure Key Vault Managed HSM.
     1. Enable purge protection on the Azure Managed HSM. This step is required to enable key release.

articles/container-apps/TOC.yml

@@ -390,10 +390,10 @@
       - name: Launch your first Java app
         items:
         - name: Dockerfile
-          href: /azure/developer/java/toolkit-for-intellij/java-get-started-dockerfile.md
+          href: /azure/developer/java/toolkit-for-intellij/java-get-started-dockerfile
           displayName: java
         - name: Github repository
-          href: /azure/developer/java/toolkit-for-intellij/java-get-started-github-repository.md
+          href: /azure/developer/java/toolkit-for-intellij/java-get-started-github-repository
           displayName: java
         - name: IntelliJ
           href: /azure/developer/java/toolkit-for-intellij/create-container-apps-intellij?toc=/azure/container-apps/toc.json&bc=/azure/container-apps/breadcrumb/toc.json

articles/event-hubs/event-hubs-emulator-whats-new.md

@@ -19,15 +19,20 @@ This article provides a detailed overview of the enhancements introduced in the
 > Kindly report any problems or suggestions in the emulator's [GitHub installer repository](https://github.com/Azure/azure-event-hubs-emulator-installer/issues).
 
 
-## Latest version ``2.0.1``
+## Latest version ``2.1.0``
 
-> *Released November 19th, 2024*
+> *Released March 11th, 2025*
 
-This release introduces Apache Kafka support in Event Hubs emulator. 
-- The producer and consumer APIs are now compatible with the Event Hubs emulator.
+This release introduces health check API in Event Hubs emulator. 
+- Health check API can be accessed at *http://localhost:5300/health*
 
 ## Previous releases
 
+### ``2.0.1`` (November 19th,2024)
+
+This release introduces Apache Kafka support in Event Hubs emulator. 
+- The producer and consumer APIs are now compatible with the Event Hubs emulator.
+
 ### ``1.2.4`` (July 1st,2024)
 
 This release provides enhanced connectivity fixes for Emulator. 

articles/event-hubs/test-locally-with-event-hub-emulator.md

@@ -33,13 +33,20 @@ Before you run an automated script, clone the emulator's [GitHub installer repos
 
 ### Windows
 
-Use the following steps to run the Event Hubs emulator locally on Windows:
-
-1. Allow the execution of unsigned scripts by running this command in the PowerShell window:
-
-   `$>Start-Process powershell -Verb RunAs -ArgumentList 'Set-ExecutionPolicy Bypass –Scope CurrentUser'`
-
-1. Run the setup script *LaunchEmulator.ps1*. Running the script brings up two containers: the Event Hubs emulator and Azurite (a dependency for the emulator).
+Use the following steps to run the Event Hubs emulator locally on Windows.
+
+1. **Open PowerShell** and navigate to the directory where the [common](https://github.com/Azure/azure-event-hubs-emulator-installer/tree/main/EventHub-Emulator/Scripts/Common) scripts folder is cloned using `cd`:
+   ```powershell
+   cd <path to your common scripts folder> # Update this path
+      
+2. Issue wsl command to open WSL at this directory.
+   ```powershell
+   wsl
+
+3. **Run the setup script** *./LaunchEmulator.sh* Running the script brings up two containers: the Event Hubs emulator and Azurite (a dependency for the emulator).
+   ```bash
+   ./Launchemulator.sh
+ 
 
 ### Linux and macOS
 
@@ -81,41 +88,45 @@ To run the Event Hubs emulator locally on Linux or macOS:
 
 2. To spin up containers for Event Hubs emulator, Save the following .yaml file as *docker-compose.yaml*.
 
-   ```
-   name: microsoft-azure-eventhubs
-   services:
-     emulator:
-       container_name: "eventhubs-emulator"
-       image: "mcr.microsoft.com/azure-messaging/eventhubs-emulator:latest"
-       volumes:
-         - "${CONFIG_PATH}:/Eventhubs_Emulator/ConfigFiles/Config.json"
-       ports:
-         - "5672:5672"
-         - "9092:9092"
-       environment:
-         BLOB_SERVER: azurite
-         METADATA_SERVER: azurite
-         ACCEPT_EULA: ${ACCEPT_EULA}
-       depends_on:
-         - azurite
-       networks:
-         eh-emulator:
-           aliases:
-             - "eventhubs-emulator"
-     azurite:
-       container_name: "azurite"
-       image: "mcr.microsoft.com/azure-storage/azurite:latest"
-       ports:
-         - "10000:10000"
-         - "10001:10001"
-         - "10002:10002"
-       networks:
-         eh-emulator:
-           aliases:
-             - "azurite"
-   networks:
-     eh-emulator:
-   ```
+  ```
+  name: microsoft-azure-eventhubs
+  services:
+  emulator:
+    container_name: "eventhubs-emulator"
+    image: "mcr.microsoft.com/azure-messaging/eventhubs-emulator:latest"
+    pull_policy: always
+    volumes:
+      - "${CONFIG_PATH}:/Eventhubs_Emulator/ConfigFiles/Config.json"
+    ports:
+      - "5672:5672"
+      - "9092:9092"
+      - "5300:5300" 
+    environment:
+      BLOB_SERVER: azurite
+      METADATA_SERVER: azurite
+      ACCEPT_EULA: ${ACCEPT_EULA}
+    depends_on:
+      - azurite
+    networks:
+      eh-emulator:
+        aliases:
+          - "eventhubs-emulator"
+  azurite:
+    container_name: "azurite"
+    image: "mcr.microsoft.com/azure-storage/azurite:latest"
+    pull_policy: always
+    ports:
+      - "10000:10000"
+      - "10001:10001"
+      - "10002:10002"
+    networks:
+      eh-emulator:
+        aliases:
+          - "azurite"
+networks:
+  eh-emulator:
+
+```
 
 3. Create an .env file to declare the environment variables for the Event Hubs emulator:
 

articles/hdinsight/interactive-query/apache-hive-warehouse-connector.md

@@ -5,7 +5,7 @@ author: reachnijel
 ms.author: nijelsf
 ms.service: azure-hdinsight
 ms.topic: how-to
-ms.date: 01/02/2025
+ms.date: 03/11/2025
 ---
 
 # Integrate Apache Spark and Apache Hive with Hive Warehouse Connector in Azure HDInsight
@@ -57,6 +57,7 @@ Hive Warehouse Connector needs separate clusters for Spark and Interactive Query
 |:---:|:---:|---|
 | v1 | Spark 2.4 \| HDI 4.0 | Interactive Query 3.1 \| HDI 4.0 |
 | v2 | Spark 3.1 \| HDI 5.0 | Interactive Query 3.1 \| HDI 5.0 |
+| v2.1 | Spark 3.3.0 \| HDI 5.1 | Interactive Query 3.1 \| HDI 5.1 |
 
 ### Create clusters
 
@@ -170,9 +171,9 @@ This is a way to run Spark interactively through a modified version of the Scala
 
 ### Spark-submit
 
-Spark-submit is a utility to submit any Spark program (or job) to Spark clusters.
+`Spark-submit` is a utility to submit any Spark program (or job) to Spark clusters.
 
-The spark-submit job will set up and configure Spark and Hive Warehouse Connector as per our instructions, execute the program we pass to it, then cleanly release the resources that were being used.
+The `spark-submit` job will set up and configure Spark and Hive Warehouse Connector as per our instructions, execute the program we pass to it, then cleanly release the resources that were being used.
 
 Once you build the scala/java code along with the dependencies into an assembly jar, use the below command to launch a Spark application. Replace `<VERSION>`, and `<APP_JAR_PATH>` with the actual values.
 

articles/iot-operations/deploy-iot-ops/howto-enable-secure-settings.md

@@ -35,7 +35,7 @@ This article provides instructions for enabling secure settings if you didn't do
 
 ## Enable the cluster for secure settings
 
-To enable secrets synchronization for your Azure IoT Operations instance, your cluster must be enabled as an OIDC issuer and for workload identity federation. This configuration is required for the Secret Store extension to sync the secrets from an Azure key vault and store them on the edge as Kubernetes secrets.
+To enable secrets synchronization for your Azure IoT Operations instance, your cluster must be enabled as an OIDC issuer and for workload identity federation. This configuration is required for the Secret Store extension to sync the secrets from an Azure Key Vault and store them on the edge as Kubernetes secrets.
 
 For Azure Kubernetes Service (AKS) clusters, the OIDC issuer and workload identity features can be enabled only at the time of cluster creation. For clusters on AKS Edge Essentials, the automated script enables these features by default. For AKS clusters on Azure Local, follow the steps to [Deploy and configure workload identity on an AKS enabled by Azure Arc cluster](/azure/aks/aksarc/workload-identity) to create a new cluster if you don't have one with the required features.
 
@@ -85,16 +85,16 @@ For k3s clusters on Kubernetes, you can update an existing cluster. To enable an
 
 ## Set up secrets management
 
-Secrets management for Azure IoT Operations uses the Secret Store extension to sync the secrets from an Azure key vault and store them on the edge as Kubernetes secrets. The Secret Store extension requires a user-assigned managed identity with access to the Azure key vault where secrets are stored. To learn more, see [What are managed identities for Azure resources?](/entra/identity/managed-identities-azure-resources/overview).
+Secrets management for Azure IoT Operations uses the Secret Store extension to sync the secrets from an Azure Key Vault and store them on the edge as Kubernetes secrets. The Secret Store extension requires a user-assigned managed identity with access to the Azure Key Vault where secrets are stored. To learn more, see [What are managed identities for Azure resources?](/entra/identity/managed-identities-azure-resources/overview).
 
 To set up secrets management:
 
-1. [Create an Azure key vault](/azure/key-vault/secrets/quick-create-cli#create-a-key-vault) that's used to store secrets, and [give your user account permissions to manage secrets](/azure/key-vault/secrets/quick-create-cli#give-your-user-account-permissions-to-manage-secrets-in-key-vault) with the `Key Vault Secrets Officer` role.
+1. [Create an Azure Key Vault](/azure/key-vault/secrets/quick-create-cli#create-a-key-vault) that's used to store secrets, and [give your user account permissions to manage secrets](/azure/key-vault/secrets/quick-create-cli#give-your-user-account-permissions-to-manage-secrets-in-key-vault) with the `Key Vault Secrets Officer` role.
 1. [Create a user-assigned managed identity](/entra/identity/managed-identities-azure-resources/how-manage-user-assigned-managed-identities?pivots=identity-mi-methods-azp#create-a-user-assigned-managed-identity) for the *secret store* extension to use to access the key vault.
 1. Use the [az iot ops secretsync enable](/cli/azure/iot/ops/secretsync#az-iot-ops-secretsync-enable) command to set up the Azure IoT Operations instance for secret synchronization. This command:
 
     - Creates a federated identity credential by using the user-assigned managed identity.
-    - Adds a role assignment to the user-assigned managed identity for access to the Azure key vault.
+    - Adds a role assignment to the user-assigned managed identity for access to the Azure Key Vault.
     - Adds a minimum secret provider class associated with the Azure IoT Operations instance.
 
     # [Bash](#tab/bash)

articles/logic-apps/secure-single-tenant-workflow-virtual-network-private-endpoint.md

@@ -132,6 +132,7 @@ To secure outbound traffic from your logic app, you can integrate your logic app
   |-------------|------------------|--------|-------------|----------|---------|
   | * | 443 | Subnet integrated with Standard logic app | Storage account | TCP | Storage account |
   | * | 445 | Subnet integrated with Standard logic app | Storage account | TCP | Server Message Block (SMB) File Share |
+  | * | 20000-30000 | Subnet integrated with Standard logic app | Worker process | TCP | Communication between App Service Plan and Standard logic app nodes |
 
 - For Azure-hosted managed connectors to work, you need to have an uninterrupted connection to the managed API service. With virtual network integration, make sure that no firewall or network security policy blocks these connections. If your virtual network uses a network security group (NSG), user-defined route table (UDR), or a firewall, make sure that the virtual network allows outbound connections to [all managed connector IP addresses](/connectors/common/outbound-ip-addresses#azure-logic-apps) in the corresponding region. Otherwise, Azure-managed connectors won't work.
 

articles/network-watcher/frequently-asked-questions.yml

@@ -9,7 +9,7 @@ metadata:
   ms.date: 03/10/2025
 title: "Network Watcher frequently asked questions (FAQ)"
 summary: |
-  This article provides answers to the most frequently asked questions asked about Azure Network Watcher.
+  This article provides answers to the most frequently asked questions about Azure Network Watcher.
   
 
 sections: