Merge pull request #303791 from MicrosoftDocs/main

Auto Publish – main to live - 2025-08-04 17:00 UTC

Author: learn-build-service-prod[bot]

articles/application-gateway/for-containers/web-application-firewall.md

@@ -64,12 +64,12 @@ The following functionality is not supported on an Azure Web Application Firewal
 
 ## Pricing
 
-Azure Web Application Firewall is incrementally billed in addition to Application Gateway for Containers. Two metrics track Azure Web Application Firewall consumption:
+Azure Web Application Firewall is incrementally billed in addition to Application Gateway for Containers. Two meters track Azure Web Application Firewall consumption:
 
-* `AGC WAF Hour`
-* `AGC 1M WAF Requests`
+* **Application Gateway for Containers WAF Hour**
+* **Application Gateway for Containers 1 million WAF Requests**
 
-An `AGC WAF Hour` rate is incurred for the duration that a security policy references an Azure Web Application Firewall policy.
+An **Application Gateway for Containers WAF Hour** rate is incurred for the duration that a security policy references an Azure Web Application Firewall policy.
 
 As Azure Web Application Firewall rules or bot protection processes each request, a consumption rate is billed per 1 million requests.
 

articles/azure-app-configuration/concept-private-endpoint.md

@@ -23,7 +23,7 @@ Private endpoints availability varies by App Configuration tier:
 - **Free tier**: Not available
 - **Developer tier**: Up to 1 private endpoint
 - **Standard tier**: Up to 10 private endpoints
-- **Premium tier**: Up to 100 private endpoints
+- **Premium tier**: Up to 40 private endpoints
 
 For more information about pricing, see [Azure App Configuration pricing](https://azure.microsoft.com/pricing/details/app-configuration/).
 

articles/azure-netapp-files/double-encryption-at-rest.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: concept-article
-ms.date: 05/05/2025
+ms.date: 08/01/2025
 ms.author: anfdocs
 ms.custom: references_regions
 # Customer intent: "As a cloud administrator, I want to implement double encryption at rest for Azure NetApp Files, so that I can safeguard sensitive data from breaches and ensure compliance with security regulations."
@@ -45,7 +45,8 @@ Azure NetApp Files double encryption at rest is supported for the following regi
 * East US 2
 * France Central  
 * Germany West Central 
-* Israel Central 
+* Israel Central
+* Italy North
 * Japan East  
 * Korea Central 
 * Korea South 

articles/iot-hub/iot-hub-tls-support.md

@@ -29,7 +29,7 @@ IoT Hub uses Transport Layer Security (TLS) to secure connections from IoT devic
 > - US Gov Arizona 
 > - US Gov Virginia (TLS 1.0/1.1 support isn't available in this region. TLS 1.2 enforcement must be enabled or IoT Hub creation fails). 
 >
-> To find out the version of TLS your IoT Hub devices are running, refer to [TLS 1.0 and 1.1 end of support guide](#checking-tls-versions-for-iot-hub-devices).
+> To find out the version of TLS your IoT Hub devices are running, refer to [TLS 1.0 and 1.1 end of support guide](#checking-tls-versions-and-cipher-suites-for-iot-hub-devices).
 
 ## Mutual TLS support
 
@@ -58,7 +58,7 @@ Root CA migrations are rare. You should always prepare your IoT solution for the
 
 Starting **August 31, 2025**, IoT Hub enforces the use of recommended strong cipher suites for all existing and new IoT Hubs. Non-recommended (weak) cipher suites aren't supported past this date.  
 
-To comply with Azure security policy for a secure connection, IoT Hub only supports the following RSA and ECDSA cipher suites that require minimum TLS 1.2 enforcement:
+To comply with Azure security policy for a secure connection, IoT Hub only supports the following RSA and ECDSA cipher suites:
 
 * TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
 * TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
@@ -69,7 +69,7 @@ To comply with Azure security policy for a secure connection, IoT Hub only suppo
 * TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
 * TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
 
-The following non-recommended cipher suites are allowed until August 31, 2025: 
+The following non-recommended cipher suites are allowed on hubs **without minTlsVersion:1.2** until August 31, 2025: 
 
 * TLS_DHE_RSA_WITH_AES_256_GCM_SHA384
 * TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
@@ -154,32 +154,29 @@ The created IoT hub resource using this configuration refuses device and service
 > [!NOTE] 
 > Upon failover, the `minTlsVersion` property of your IoT Hub remains effective in the geo-paired region post-failover.
 
-## Checking TLS versions for IoT Hub devices
+## Checking TLS versions and cipher suites for IoT Hub devices
 
-Azure IoT Hub provides the capability to check the TLS version and other device connection metrics to help monitor the security of IoT devices. You can either use IoT Hub metrics or diagnostic logs to track TLS version usage and other related properties like [Cipher Suites](#cipher-suites).
+Azure IoT Hub provides the capability to check the TLS version, cipher suites, and other device connection metrics to help monitor the security of IoT devices. You can either use IoT Hub metrics or diagnostic logs to track TLS version usage and other related properties like [Cipher Suites](#cipher-suites).
 
-### Checking TLS versions using IoT Hub metrics
+### Checking TLS versions and cipher suites using IoT Hub metrics
 
-If you want to validate that device traffic to IoT Hub is utilizing TLSv1.2, you can check IoT Hub’s metrics. This allows you to filter by TLS version or Cipher Suite and check the number of successful connections. 
+If you want to validate that device traffic to IoT Hub is utilizing TLSv1.2 and strong cipher suites, you can check IoT Hub’s metrics. This allows you to filter by TLS version or cipher suite and check the number of successful connections. 
 
 1. In the [Azure portal](https://portal.azure.com), go to your IoT hub.
 1. In the left-side menu under **Monitoring**,  select **Metrics**.
 1. Add the metric **Successful Connects**.
 
     :::image type="content" source="./media/iot-hub-tls-support/tls-versions-support-metrics.png" alt-text="Screenshot showing how to add the Successful Connects metric.":::
 
-1. Filter by TLS Version or Cipher Suite by selecting the **Add filter** button and choosing the appropriate property, TLS Version or Cipher Suite, operator, for example "=", and value, for example, TLSv1.2.
+1. Filter by TLS Version or cipher suite by selecting the **Add filter** button and choosing the appropriate property, TLS Version or cipher suite, operator, for example "=", and value, for example, TLSv1.2.
 
     :::image type="content" source="./media/iot-hub-tls-support/tls-versions-support-metrics-filter.png" alt-text="Screenshot showing how to filter by TLS Version or Cipher Suite.":::
 
 1. After applying the filter, you see the sum of devices with successful IoT Hub connections based on the filtered property and value(s).  
 
-> [!NOTE]
-> TLS version query isn't available for devices using HTTPS connections.
-
-### Checking TLS versions using IoT Hub diagnostic logs
+### Checking TLS versions and cipher suites using IoT Hub diagnostic logs
 
-Azure IoT Hub can provide diagnostic logs for several categories that can be analyzed using Azure Monitor Logs. In the connections log you can find the TLS version for your IoT Hub devices. 
+Azure IoT Hub can provide diagnostic logs for several categories that can be analyzed using Azure Monitor Logs. In the connections log you can find the TLS version and cipher suite for your IoT Hub devices. 
 
 To view these logs, follow these steps: 
 

articles/iot-operations/discover-manage-assets/howto-configure-opc-ua.md

@@ -173,12 +173,14 @@ Now you can define the tags associated with the asset. To add OPC UA tags:
     | ns=3;s=FastUInt10 | Temperature |
     | ns=3;s=FastUInt100 | Humidity |
 
-1. Select **Manage default settings** to configure default settings for messages from the asset. These settings apply to all the OPC UA tags that belong to the asset. You can override these settings for each tag that you add. Default settings include:
+1. To configure default settings for messages from the asset, select **Manage default settings**. These settings apply to all the OPC UA tags that belong to the asset. You can override these settings for each tag that you add. Default settings include:
 
     - **Sampling interval (milliseconds)**: The sampling interval indicates the fastest rate at which the OPC UA server should sample its underlying source for data changes.
     - **Publishing interval (milliseconds)**: The rate at which OPC UA server should publish data.
     - **Queue size**: The depth of the queue to hold the sampling data before publishing it.
 
+1. To configure the MQTT topic to publish the tag data to, select **Manage default dataset**. Enter an MQTT topic name such as `azure-iot-operations/data/thermostat`, then select **Update**.
+
 1. On the **Tags** page, select **Next** to go to the **Add events** page.
 
 # [Azure CLI](#tab/cli)
@@ -187,16 +189,16 @@ Use the following commands to add a "thermostat" namespace asset to your device
 
 ```azurecli
 # Create the asset
-az iot ops ns asset opcua create --name thermostat --instance {your instance name} -g  {your resource group name} --device opc-ua-connector --endpoint-name opc-ua-connector-0  --description 'A simulated thermostat asset'
+az iot ops ns asset opcua create --name thermostat --instance {your instance name} -g  {your resource group name} --device opc-ua-connector --endpoint opc-ua-connector-0  --description 'A simulated thermostat asset'
 
 # Add the dataset
-az iot ops ns asset opcua dataset add --asset thermostat --instance {your instance name} -g {your resource group name} --name default --data-source "ns=3;s=FastUInt10"
+az iot ops ns asset opcua dataset add --asset thermostat --instance {your instance name} -g {your resource group name} --name default --data-source "ns=3;s=FastUInt10" --dest topic="azure-iot-operations/data/thermostat" retain=Keep qos=Qos1 ttl=3600
 
 # Add the datapoints
 az iot ops ns asset opcua dataset point add --asset thermostat --instance {your instance name} -g {your resource group name} --dataset default --name temperature --data-source "ns=3;s=FastUInt10"
 az iot ops ns asset opcua dataset point add --asset thermostat --instance {your instance name} -g {your resource group name} --dataset default --name humidity --data-source "ns=3;s=FastUInt100"
 
-# Show the datapoints
+# Show the dataset and datapoints
 az iot ops ns asset opcua dataset show --asset thermostat -n default -g {your resource group name} --instance {your instance name}
 ```
 

articles/iot-operations/end-to-end-tutorials/tutorial-add-assets.md

@@ -198,7 +198,6 @@ To create an asset, select **Create namespace asset**. Then enter the following
 | Inbound endpoint | `opc-ua-connector-0` |
 | Asset name | `thermostat` |
 | Description | `A simulated thermostat asset` |
-| Default MQTT topic | `azure-iot-operations/data/thermostat` |
 
 Remove the existing **Custom properties** and add the following custom properties. Be careful to use the exact property names, as the Power BI template in a later tutorial queries for them:
 
@@ -216,18 +215,20 @@ Select **Next** to go to the **Add tags** page.
 
 ### Create OPC UA tags
 
-Add an OPC UA tag on the **Add tags** page. To add a tag, select **Add tag**. Enter the tag details shown in the following table:
+Add an OPC UA tag on the **Tags** page. To add a tag, select **Add tag**. Enter the tag details shown in the following table:
 
-| Node ID            | Tag name    |
+| Data source        | Tag name    |
 | ------------------ | ----------- |
 | ns=3;s=SpikeData   | temperature |
 
-The node ID here is specific to the OPC UA simulator. The node generates random values within a specified range and also has intermittent spikes.
+The data source value here is a specific OPC UA simulator node. The node generates random values within a specified range and also has intermittent spikes.
 
 You can select **Manage default settings** to change the default sampling interval and queue size for each tag.
 
 :::image type="content" source="media/tutorial-add-assets/add-tag.png" lightbox="media/tutorial-add-assets/add-tag.png" alt-text="Screenshot of Azure IoT Operations add tag page.":::
 
+To configure the MQTT topic to publish the tag data to, select **Manage default dataset**. Enter `azure-iot-operations/data/thermostat` as the MQTT topic, then select **Update**. This topic is used by the data flow in the next tutorial to send messages to the cloud.
+
 Select **Next** to go to the **Add events** page and then **Next** to go to the **Review** page.
 
 ### Review
@@ -236,10 +237,10 @@ Review your asset and tag details and make any adjustments you need before you s
 
 :::image type="content" source="media/tutorial-add-assets/review-asset.png" lightbox="media/tutorial-add-assets/review-asset.png" alt-text="Screenshot of Azure IoT Operations create asset review page.":::
 
-This configuration deploys a new asset called `thermostat` to the cluster. You can view your assets in your resource group in the Azure portal. You can also use `kubectl` to view the assets locally in your cluster:
+This configuration deploys a new asset called `thermostat` to the cluster. You can also use `kubectl` to view the assets locally in your cluster:
 
 ```console
-kubectl get assets -n azure-iot-operations
+kubectl get assets.namespace -n azure-iot-operations
 ```
 
 ## View resources in the Azure portal
@@ -256,7 +257,7 @@ The portal enables you to view the asset details. Select **JSON View** for more
 
 [!INCLUDE [deploy-mqttui](../includes/deploy-mqttui.md)]
 
-To verify that the thermostat asset you added is publishing data, view the messages in the `azure-iot-operations/data` topic:
+To verify that the thermostat asset you added is publishing data, view the messages in the `azure-iot-operations/data/thermostat` topic:
 
 ```output
 Client $server-generated/0000aaaa-11bb-cccc-dd22-eeeeee333333 received PUBLISH (d0, q0, r0, m0, 'azure-iot-operations/data/thermostat', ... (92 bytes))

articles/migrate/appcat/appcat-7-quickstart.md

@@ -15,15 +15,9 @@ ms.date: 06/27/2025
 
 This quickstart shows you how to download, install, and run AppCAT 7 against a sample Java project.
 
-## Prerequisites
-
-Before downloading AppCAT, be sure the JDK is installed and configured correctly.
-
-- [The Microsoft Build of OpenJDK 17](/java/openjdk/install). Ensure that the `JAVA_HOME` environment variable is set.
-
 ## Download and install
 
-To use the `appcat` CLI, you must download the package specific to your environment, and have the required dependencies in your environment. The `appcat` CLI runs on any environment such as Windows, Linux, or Mac, using Intel, Arm, or Apple Silicon hardware. For the JDK requirement, we recommend you use the [Microsoft Build of OpenJDK](/java/openjdk).
+To use the `appcat` CLI, you must download the package specific to your environment, and have the required dependencies in your environment. The `appcat` CLI runs on any environment such as Windows, Linux, or Mac, using Intel, Arm, or Apple Silicon hardware. 
 
 | OS      | Architecture    | Download Link  | Other files              |
 |---------|-----------------|----------------|--------------------------|
@@ -68,6 +62,7 @@ Extract the binary from the downloaded file. You should see the following folder
 ├── NOTICE.txt
 ├── maven.default.index
 ├── jdtls/
+├── justj.zip (Windows) / justj.tar.gz (Linux/macOS)
 ├── static-report/
 ├── maven-wrapper/
 ├── .appcat-ignore

articles/migrate/appcat/appcat-7-release-notes.md

@@ -17,6 +17,14 @@ This article provides the release notes for Azure Migrate application and code a
 
 ## Release history
 
+### 7.7.0.2
+
+This release contains the following fixes and enhancements:
+
+- Removed JDK from the prerequisites. 
+- Removed **output.json** or **output.yaml** from result output.
+- Fixed the issue where the `azure-password-01000` rule detects only one violation, even when multiple violations exist in the same file.
+
 ### 7.7.0.1
 
 This release contains the following fixes and enhancements:
@@ -118,6 +126,12 @@ This release is based on a different set of components of the Konveyor project.
 
 ## Known issues
 
+### 7.7.0.2
+
+- Rules issues:
+  - The `azure-system-config-01000` rules aren't being triggered.
+- An error in the **Watcher Error** channel on Windows: `Windows system assumed buffer larger than it is, events have likely been missed`. This error message appears on the command line during long-running jobs on Windows.
+
 ### 7.7.0.1
 
 - Rules issues:

articles/partner-solutions/palo-alto/manage.md

@@ -1,5 +1,5 @@
 ---
-title: Manage a Cloud Next-Generation Firewall (NGFW) by Palo Alto Networks Resource by Using the Azure Portal
+title: Manage a Cloud Next-Generation Firewall (NGFW) by Palo Alto Networks Resource by Using the Azure portal
 description: Manage your Cloud NGFW resource in the Azure portal, including networking, NAT, rulestack settings, logging, Domain Name System (DNS) proxy configuration, and billing plan changes.
 ms.topic: how-to
 ms.date: 06/26/2025
@@ -40,9 +40,18 @@ To change the Cloud NGFW's billing plan, go to **Overview** and select **Change
 > [!NOTE]
 > The **Delete** button on the resource is activated only if all connected resources are already deleted. For more information, see [Azure Resource Manager resource group and resource deletion](/azure/azure-resource-manager/management/delete-resource-group).
 
+## Get support
+
+Contact [Palo Alto Network](https://support.paloaltonetworks.com/Support/Index) for customer support.
+
+You can also request support in the Azure portal from the [resource overview](#resource-overview).
+
+Select **Support + Troubleshooting** > **New support request** from the service menu, then choose the link to [Contact PAN customer support](https://support.paloaltonetworks.com/Support/Index). 
+
 ## Related content
 
 - [Azure Virtual Network FAQ](../../virtual-network/virtual-networks-faq.md)
 - [Virtual WAN FAQ](../../virtual-wan/virtual-wan-faq.md)
 
 
+

articles/partner-solutions/palo-alto/toc.yml

@@ -14,7 +14,12 @@ items:
   items:
   - name: Manage your resource
     href: manage.md
-  - name: Troubleshoot
-    href: /troubleshoot/azure/partner-solutions/welcome-native-integrations
   - name: Deploy Cloud NGFW by Palo Alto Networks with the Application Gateway
     href: application-gateway.md
+  - name: Troubleshoot
+    items:
+    - name: Get support
+      href: https://support.paloaltonetworks.com/Support/Index
+    - name: Troubleshoot
+      href: /troubleshoot/azure/partner-solutions/welcome-native-integrations
+