Pull commits for update to IoT Edge

Author: sethmanheim

articles/iot-edge/using-private-link.md

@@ -3,7 +3,7 @@ title: Use Azure Private Link and Private Endpoints to secure Azure IoT traffic
 description: Learn how to use IoT Edge while completely isolating your network from the internet traffic using various Azure services such as Azure ExpressRoute, Private Link, and DNS Private Resolver
 author: sethmanheim
 ms.author: sethm
-ms.date: 07/22/2025
+ms.date: 01/29/2026
 ms.topic: concept-article
 ms.service: azure-iot-edge
 services: iot-edge
@@ -32,18 +32,18 @@ Azure Private Link lets you use Azure PaaS services and Azure-hosted customer-ow
 
 Azure DNS Private Resolver lets you query Azure DNS private zones from an on-premises environment and the other way around without deploying VM-based DNS servers. Azure DNS Private Resolver makes it easier to manage both private and public IPs. The DNS forwarding ruleset feature in Azure DNS Private Resolver helps an IoT admin easily configure rules and manage which address an endpoint should resolve. To learn more about Azure DNS Private Resolver, see [What is Azure DNS Private Resolver?](../dns/dns-private-resolver-overview.md).
 
-### Configuring IoT Edge endpoints when using Private Link
+### Configure IoT Edge endpoints when using Private Link
 
-When Private Link is enabled, IoT Edge must be configured to use the **private endpoint FQDNs**, not the public service hostnames. If public hostnames are used, IoT Edge modules will fail to connect after public network access is disabled.
+When Private Link is enabled, IoT Edge must be configured to use the **private endpoint FQDNs**, not the public service hostnames. If public hostnames are used, IoT Edge modules fail to connect after public network access is disabled.
 
 #### Which hostname should be used?
 
 | Azure service | Public FQDN | Private Link FQDN | What IoT Edge should use |
 |---------------|-------------|-------------------|---------------------------|
-| IoT Hub | `<hubname>.azure-devices.net` | `<hubname>.privatelink.azure-devices.net` | **Use Private Link FQDN** |
-| DPS | `global.azure-devices-provisioning.net` | `global.privatelink.azure-devices-provisioning.net` | **Use Private Link FQDN** |
-| Azure Container Registry (ACR) | `<registry>.azurecr.io` | `<registry>.privatelink.azurecr.io` | **Use Private Link FQDN** |
-| Storage (Blob) | `<account>.blob.core.windows.net` | `<account>.privatelink.blob.core.windows.net` | **Use Private Link FQDN** |
+| IoT Hub | `<hubname>.azure-devices.net` | `<hubname>.privatelink.azure-devices.net` | Use Private Link FQDN |
+| DPS | `global.azure-devices-provisioning.net` | `global.privatelink.azure-devices-provisioning.net` | Use Private Link FQDN |
+| Azure Container Registry (ACR) | `<registry>.azurecr.io` | `<registry>.privatelink.azurecr.io` | Use Private Link FQDN |
+| Storage (Blob) | `<account>.blob.core.windows.net` | `<account>.privatelink.blob.core.windows.net` | Use Private Link FQDN |
 
 #### Example IoT Edge `config.yaml`
 
@@ -56,6 +56,7 @@ provisioning:
 agent:
   env:
     IOTEDGE_IOTHUBHOSTNAME: "<hubname>.privatelink.azure-devices.net"
+```
 
 #### DNS requirement