4th article

Author: v-thepet

articles/iot-hub-device-update/import-concepts.md

@@ -1,15 +1,15 @@
 ---
-title: Azure Device Update for IoT Hub import manifest
+title: Azure Device Update for IoT Hub import manifest concepts
 description: Understand the important concepts and sections in the Azure Device Update for IoT Hub import manifest.
 author: andrewbrownmsft
 ms.author: andbrown
-ms.date: 12/31/2024
+ms.date: 01/02/2025
 ms.topic: concept-article
 ms.service: azure-iot-hub
 ms.subservice: device-update
 ---
 
-# Azure Device Update for IoT Hub import manifest
+# Azure Device Update for IoT Hub import manifest concepts
 
 To deploy an update to devices using Azure Device Update for IoT Hub, you first import the update into the Device Update service, which stores the imported update and deploys it to devices. Along with the update payload, you submit a JSON import manifest file that defines important information about the update. This article describes the important concepts and sections in the import manifest JSON file.
 

articles/iot-hub-device-update/import-schema.md

@@ -3,7 +3,7 @@ title: Import manifest schema for Azure Device Update for IoT Hub
 description: Understand the schema used to create the required import manifest for importing updates into Azure Device Update for IoT Hub.
 author: andrewbrownmsft
 ms.author: andbrown
-ms.date: 12/31/2024
+ms.date: 01/02/2025
 ms.topic: concept-article
 ms.service: azure-iot-hub
 ms.subservice: device-update

articles/iot-hub-device-update/import-update.md

@@ -3,7 +3,7 @@ title: Import an update to Azure Device Update for IoT Hub
 description: Learn how to import update files into Azure Device Update for IoT Hub by using the Azure portal, Azure CLI, or programmatically.
 author: andrewbrownmsft
 ms.author: andbrown
-ms.date: 12/31/2024
+ms.date: 01/02/2025
 ms.topic: how-to
 ms.service: azure-iot-hub
 ms.subservice: device-update
@@ -38,6 +38,9 @@ To import an update, you first upload the update files and import manifest into
 
 1. On the **Storage accounts** page, select an existing storage account or create a new account by selecting **Storage account**. You use the storage account for a container to stage the update files.
 
+   > [!IMPORTANT]
+   > Make sure the storage account you use or create doesn't have private endpoints enabled. To see if private endpoints are enabled, you can check for your Azure Storage account name under **Private endpoints** in the [Private Link Center](https://portal.azure.com/#blade/Microsoft_Azure_Network/PrivateLinkCenterBlade/overview).
+
 1. On the **Containers** page, select an existing container or create a new container by selecting **Container**. You use the container to stage the update files for import.
 
    :::image type="content" source="media/import-update/storage-account-ppr.png" alt-text="Screenshot that shows Storage accounts and Containers.":::

articles/iot-hub-device-update/update-manifest.md

@@ -1,32 +1,31 @@
 ---
-title: Device Update for IoT Hub update manifest
-description: Learn how properties are sent from the Device Update service to the device during an update
+title: Azure Device Update for IoT Hub update manifest
+description: Learn how the Azure Device Update for IoT Hub service uses the update manifest to send properties to devices during updates.
 author: andrewbrownmsft
 ms.author: andbrown
-ms.date: 08/19/2022
+ms.date: 01/02/2025
 ms.topic: concept-article
 ms.service: azure-iot-hub
 ms.subservice: device-update
 ---
 
 
-# Device Update for IoT Hub update manifest
+# Azure Device Update for IoT Hub update manifest
 
-Device Update for IoT Hub uses [IoT Plug and Play](./device-update-plug-and-play.md) to send data to devices during deployment. One of them is the _update manifest_, a serialized JSON object string containing metadata of the update to install. It's also cryptographically signed to allow the Device Update agent to verify its authenticity. For more information on how the update manifest is used to securely install content, see [Device Update security](./device-update-security.md).
+This article describes how Azure Device Update for IoT Hub uses [IoT Plug and Play](./device-update-plug-and-play.md) to send *update manifest* data to devices during update deployment. The update manifest is a serialized JSON object string containing metadata about the update to install. The update manifest is cryptographically signed so the Device Update agent can verify its authenticity. For more information about how the update manifest is used to securely install content, see [Device Update security](./device-update-security.md).
 
 ## Import manifest vs update manifest
 
-It's important to understand the differences between the import manifest and the update manifest concepts in Device Update for IoT Hub:
+The update manifest is different from the Device Update *import manifest*.
 
-* The [import manifest](./import-concepts.md) is created by whomever creates the corresponding update. It describes the contents of the update that will be imported into Device Update for IoT Hub.
-* The update manifest is automatically generated by the Device Update for IoT Hub service, using some of the properties that were defined in the import manifest. It's used to communicate relevant information to the Device Update agent during the update process.
+- Whoever creates the update for Device Update also creates the corresponding [import manifest](./import-concepts.md), which describes the contents of the update to import into Device Update.
+- The Device Update service automatically generates the update manifest, using some of the same properties defined in the import manifest, to communicate information to the Device Update agent during the update process.
 
-Each manifest type has its own schema and schema version.
+Each manifest type has its own schema and schema version. For more information about the import manifest schema, see [Device Update import manifest schema](import-schema.md).
 
 ## Update manifest schema
 
-> [!IMPORTANT]
-> Update manifest JSON schema version 4 is hosted at [SchemaStore.org](https://json.schemastore.org/azure-deviceupdate-update-manifest-4.json).
+The update manifest JSON schema version 4 is hosted at [SchemaStore.org](https://json.schemastore.org/azure-deviceupdate-update-manifest-4.json).
 
 ### Example update manifest
 
@@ -72,9 +71,9 @@ Each manifest type has its own schema and schema version.
 
 ### Full vs mini update manifest
 
-When an update manifest exceeds a certain size that prevents it from being communicated efficiently, Device Update for IoT Hub will send it to the device in _detached_ format, also known as a _mini update manifest_. A mini manifest is technically metadata for update manifest and contains information needed for the Device Update agent to download the full update manifest and verify its authenticity.
+If an update manifest is too large to be communicated efficiently, Device Update sends it to the device in *detached* format, also known as a *mini update manifest*. A mini manifest contains metadata about the update manifest that Device Update agent needs to download the full update manifest and verify its authenticity.
 
-Example mini update manifest:
+The following example shows a mini update manifest:
 
 ```json
 {
@@ -96,3 +95,8 @@ Example mini update manifest:
   }
 }
 ```
+## Related content
+- [Device Update import manifest concepts](import-manifest.md)
+- [Device Update import manifest schema](import-schema.md)
+- [Prepare an update to import into Device Update](create-update.md)
+- [Import an update into Device Update](import-update.md)