Merge pull request #313507 from MicrosoftDocs/main

Auto Publish – main to live - 2026-03-23 11:00 UTC

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

articles/iot-edge/how-to-manage-device-certificates.md

@@ -4,7 +4,7 @@ titleSuffix: Azure IoT Edge
 description: How to install and manage certificates on an Azure IoT Edge device to prepare for production deployment. 
 author: sethmanheim
 ms.author: sethm
-ms.date: 03/02/2026
+ms.date: 03/23/2026
 ms.topic: concept-article
 ms.service: azure-iot-edge
 services: iot-edge
@@ -482,7 +482,7 @@ This approach requires you to manually update the files as certificate expires.
 
 ## Automatic certificate management using EST server
 
-IoT Edge can interface with an [Enrollment over Secure Transport (EST) server)](https://wikipedia.org/wiki/Enrollment_over_Secure_Transport) for automatic certificate issuance and renewal. Using EST is recommended for production as it replaces the need for manual certificate management, which can be risky and error-prone. You can configure it globally and override it for each certificate type.
+IoT Edge can interface with an [Enrollment over Secure Transport (EST) server](https://wikipedia.org/wiki/Enrollment_over_Secure_Transport) for automatic certificate issuance and renewal. Using EST is recommended for production as it replaces the need for manual certificate management, which can be risky and error-prone. You can configure it globally and override it for each certificate type.
 
 In this scenario, the bootstrap certificate and private key are long-lived and potentially installed on the device during manufacturing. IoT Edge uses the bootstrap credentials to authenticate to the EST server for the initial request to issue an identity certificate for subsequent requests and for authentication to DPS or IoT Hub.
 

articles/migrate/define-manage-applications.md

@@ -85,7 +85,7 @@ You can start identifying the applications running in your datacenter. Here are
 1. Select **Add applications> Create new application**, start by providing basic details of an application like **Name**, **Description** and **Type**. You can choose to provide same name for the application as on-premises, add a description that helps the service understand about the application and choose between **Custom** or **Packaged** for application type. 
 
     >[!Note]
-    > The application **Name** also allows for alphanumeric and special characters except ',' and '\'. The type **Packaged** refers to the Commercial-off-the-shelf (COTS) applications you are running in your datacenter.
+    > The application **Name** also allows for alphanumeric and special characters except `','` and `'\'`. The type **Packaged** refers to the Commercial-off-the-shelf (COTS) applications you are running in your datacenter.
 
 2. In the next step, you can link the workloads that are hosting this application. You can select **Link workloads** to go to the All inventory view, which helps you select the workloads that you want to add to this new application. 
 3. You can scope the All inventory view by searching for specific workloads or filtering workloads by Category, Type, OS name etc. and **Add** the selected workloads.
@@ -118,7 +118,7 @@ If you want to define applications at scale, you can select **Import> Import app
 3. In the exported CSV, you can add names of the applications, a workload is a part of. You can add more than one name if the workload is shared amongst multiple applications. For instance, if a database- "SQLDB01" is shared by 2 applications, then you can add- "App01, App02" under Application name column in the same row. 
 
     >[!Note]
-    > The **Application name(s)** are case-sensitive. The application name also allows for alphanumeric and special characters except ',' and '\'. You can add applications in multiple import operations but it is recommended to not trigger multiple import operations in parallel. 
+    > The **Application name(s)** are case-sensitive. The application name also allows for alphanumeric and special characters except `','` and `'\'`. You can add applications in multiple import operations but it is recommended to not trigger multiple import operations in parallel. 
 
 4. After adding the application names to the file, you can browse and select the CSV file. 
 5. If the selected file passes the validation checks, you can select **Import** to upload the details of the applications, as added in the CSV file.

articles/network-watcher/connection-monitor-overview.md

@@ -41,7 +41,7 @@ Here are some of the benefits of using Connection monitor:
 
 - Supported source endpoints enabled with Network Watcher extension: Azure VMs, Azure virtual machine scale sets, and Arc enabled on-premises hosts.
 
-- Supported destination endpoints: Azure VMs, Azure virtual machine scale sets, Arc enabled on-premises hosts, URLs, FQDNs, and IP addresses. Destination endpoints don't require the Network Watcher extension.
+- Supported destination endpoints: Azure Virtual Machines, Azure virtual machine scale sets, Arc enabled on-premises hosts, URLs, FQDNs, or IP addresses, including on-premises endpoints without Arc. Destination endpoints don't require the Network Watcher extension.
 
 - High probing frequencies and visibility into network performance  
 

articles/storage/blobs/storage-blob-change-feed.md

@@ -664,6 +664,8 @@ This section describes known issues and conditions in the current release of the
 - BlobDeleted events are not generated when blob versions or snapshots are deleted. A BlobDeleted event is added only when a base (root) blob is deleted.
 - Event records are added only for changes to blobs that result from requests to the Blob Service endpoint (`blob.core.windows.net`). Changes that result from requests to the Data Lake Storage endpoint (`dfs.core.windows.net`) endpoint aren't logged and won't appear in change feed records.
 
+- If the **`$blobchangefeed`** container is deleted while there are pending events to be published, the system automatically recreates the container. In this scenario, the customer may delete the container later.
+
 ## Frequently asked questions (FAQ)
 
 See [Change feed support FAQ](storage-blob-faq.yml#change-feed-support).