Resolving pre-check issues

stevenmatthew · stevenmatthew · commit 47a14faec275 · 2025-03-21T14:15:10.000-07:00
diff --git a/articles/databox/data-box-audit-logs.md b/articles/databox/data-box-audit-logs.md
@@ -1,5 +1,5 @@
 ---
-title: Audit logs for Azure Azure Data Box, Azure Data Box Next Gen, and Azure Data Box Heavy events | Microsoft Docs 
+title: Audit logs for Azure Data Box, Azure Data Box Next Gen, and Azure Data Box Heavy events | Microsoft Docs
 description: Describes the full audit logs for Data Box that are collected at the various stages of your Azure Data Box, Data Box Next Gen, and Data Box Heavy order.
 services: databox
 author: stevenmatthew
diff --git a/articles/databox/data-box-cable-options.md b/articles/databox/data-box-cable-options.md
@@ -1,6 +1,6 @@
 ---
 title: Azure Data Box cabling options | Microsoft Docs 
-description: Learn about the different the ways to cable your Azure Data Box for data transfer by using MGMT port or DATA port.
+description: Learn about the different ways to cable your Azure Data Box for data transfer by using MGMT port or DATA port.
 services: databox
 author: stevenmatthew
 
@@ -145,7 +145,7 @@ Do the following steps to cable your device.
 
 1. Use an RJ45 cable to connect the MGMT port to the server that has the data.
 
-    ![One-port setup](media/data-box-cable-options/cabling-mgmt-only.png)
+    ![Screenshot illustrating one-port setup and data flow to the Data Box device.](media/data-box-cable-options/cabling-mgmt-only.png)
 
 2. On the server, set:
 
@@ -178,7 +178,7 @@ Do the following steps to cable your device.
    - **IP address** to 192.168.100.5
    - **Subnet** to 255.255.255.0
 
-     ![Two-port setup](media/data-box-cable-options/cabling-2-port-setup.png)
+     ![Screenshot illustrating two-port setup and data flow to the Data Box device.](media/data-box-cable-options/cabling-2-port-setup.png)
 
 3. Access the local web UI of the device at: 192.168.100.10. Sign in and unlock the Data Box using the unlock password from the Azure portal.
 4. Assign static IPs to the data ports that you've configured.
@@ -194,7 +194,7 @@ Do the following steps to cable your device.
    - **IP address** of 192.168.100.5
    - **Subnet** of 255.255.255.0.
   
-   ![Two-port setup with a switch](media/data-box-cable-options/cabling-with-static-ip.png)
+   ![Screenshot illustrating two-port setup with a switch and data flow to the Data Box device.](media/data-box-cable-options/cabling-with-static-ip.png)
 
 3. Access the local web UI of the device at: 192.168.100.10. Sign in and unlock the Data Box using the unlock password from the Azure portal.
 4. Identify the IP addresses assigned by the DHCP server.
@@ -218,7 +218,7 @@ Do the following steps to cable your device.
    - **IP address** of 192.168.100.5
    - **Subnet** of 255.255.255.0.
 
-     ![Two-port setup with a switch 2](media/data-box-cable-options/cabling-with-switch-static-ip.png)
+     ![Screenshot illustrating a variation of the two-port setup with a switch and data flow to the Data Box device.](media/data-box-cable-options/cabling-with-switch-static-ip.png)
 
 3. Access the local web UI of the device at: 192.168.100.10. Sign in and unlock the Data Box using the unlock password from the Azure portal.
 4. Assign static IPs to the data ports that you've configured.
@@ -238,7 +238,7 @@ Do the following steps to cable your device.
 
 1. Use an RJ45 or QSFP cable via a switch (where DHCP server is accessible) to the server.
 
-    ![Two port setup with a switch 3](media/data-box-cable-options/cabling-dhcp-data-only.png)
+    ![Screenshot illustrating a second variation of the two-port setup with a switch and data flow to the Data Box device.](media/data-box-cable-options/cabling-dhcp-data-only.png)
 
 2. Use DHCP server or DNS server to identify the IP address.
 3. From a server on the same network, access the local web UI of the device using the IP address assigned by the DHCP server. Sign in and unlock the Data Box using the unlock password from the Azure portal.
diff --git a/articles/databox/data-box-customer-managed-encryption-key-portal.md b/articles/databox/data-box-customer-managed-encryption-key-portal.md
@@ -154,15 +154,15 @@ Use the following steps to update the identity that manages access to the custom
 
      - To change to a different user identity, select **Select a different user identity**. Then select a different identity in the panel on the right side of the screen, and choose **Select**.
 
-       :::image type="content" source="media/data-box-customer-managed-encryption-key-portal/customer-managed-key-18-sml.png" alt-text="Screen shot showing options for changing the user-assigned identity for a customer-managed key." lightbox="media/data-box-customer-managed-encryption-key-portal/customer-managed-key-18-lrg.png":::
+       :::image type="content" source="media/data-box-customer-managed-encryption-key-portal/customer-managed-key-18-sml.png" alt-text="Screenshot showing options for changing the user-assigned identity for a customer-managed key." lightbox="media/data-box-customer-managed-encryption-key-portal/customer-managed-key-18-lrg.png":::
 
    - To switch to the system-assigned identity generated during order creation, select **System assigned** by **Select identity type**.
 
-     :::image type="content" source="media/data-box-customer-managed-encryption-key-portal/customer-managed-key-19-sml.png" alt-text="Screen shot showing options for changing to a system-assigned key from for a customer-managed key." lightbox="media/data-box-customer-managed-encryption-key-portal/customer-managed-key-19-lrg.png":::
+     :::image type="content" source="media/data-box-customer-managed-encryption-key-portal/customer-managed-key-19-sml.png" alt-text="Screenshot showing options for changing to a system-assigned key from for a customer-managed key." lightbox="media/data-box-customer-managed-encryption-key-portal/customer-managed-key-19-lrg.png":::
 
 3. Select **Save**.
 
-    :::image type="content" source="media/data-box-customer-managed-encryption-key-portal/customer-managed-key-17-a-sml.png" alt-text="Screen shot showing the location of the button used to save your updated encryption settings." lightbox="media/data-box-customer-managed-encryption-key-portal/customer-managed-key-17-a-lrg.png":::
+    :::image type="content" source="media/data-box-customer-managed-encryption-key-portal/customer-managed-key-17-a-sml.png" alt-text="Screenshot showing the location of the button used to save your updated encryption settings." lightbox="media/data-box-customer-managed-encryption-key-portal/customer-managed-key-17-a-lrg.png":::
 
 ## Use Microsoft managed key
 
@@ -172,11 +172,11 @@ To change from using a customer-managed key to the Microsoft managed key for you
 
 2. By **Select type**, select **Microsoft managed key**.
 
-    :::image type="content" source="media/data-box-customer-managed-encryption-key-portal/customer-managed-key-20-sml.png" alt-text="Screen shot showing a Data Box order's Overview pane." lightbox="media/data-box-customer-managed-encryption-key-portal/customer-managed-key-20-lrg.png":::
+    :::image type="content" source="media/data-box-customer-managed-encryption-key-portal/customer-managed-key-20-sml.png" alt-text="Screenshot showing a Data Box order's Overview pane." lightbox="media/data-box-customer-managed-encryption-key-portal/customer-managed-key-20-lrg.png":::
 
 3. Select **Save**.
 
-    :::image type="content" source="media/data-box-customer-managed-encryption-key-portal/customer-managed-key-21-sml.png" alt-text="Screen shot showing the location of the button used to save the updated encryption settings for a Microsoft managed key." lightbox="media/data-box-customer-managed-encryption-key-portal/customer-managed-key-21-lrg.png":::
+    :::image type="content" source="media/data-box-customer-managed-encryption-key-portal/customer-managed-key-21-sml.png" alt-text="Screenshot showing the location of the button used to save the updated encryption settings for a Microsoft managed key." lightbox="media/data-box-customer-managed-encryption-key-portal/customer-managed-key-21-lrg.png":::
 
 ## Troubleshoot errors
 
diff --git a/articles/databox/data-box-deploy-copy-data-via-copy-service.md b/articles/databox/data-box-deploy-copy-data-via-copy-service.md
@@ -34,10 +34,10 @@ In this tutorial, you learn how to:
 :::zone pivot="dbx"
 Before you begin, make sure that:
 
-1. You've completed the [Tutorial: Set up Azure Data Box](data-box-deploy-set-up.md).
-2. You've received your Data Box and the order status in the portal is **Delivered**.
-3. Ensure that you have the credentials of the NAS device containing your source data.
-4. You have a host computer that has the data that you want to copy over to Data Box. Your host computer must:
+* You've completed the [Tutorial: Set up Azure Data Box](data-box-deploy-set-up.md).
+* You've received your Data Box and the order status in the portal is **Delivered**.
+* Ensure that you have the credentials of the NAS device containing your source data.
+* You have a host computer that has the data that you want to copy over to Data Box. Your host computer must:
    * Run a [Supported operating system](data-box-system-requirements.md).
    * Be connected to a high-speed network. We strongly recommend that you have at least one 10-GbE connection. If a 10-GbE connection isn't available, use a 1-GbE data link but the copy speeds are impacted.
 
@@ -46,10 +46,10 @@ Before you begin, make sure that:
 :::zone pivot="dbx-ng"
 Before you begin, make sure that:
 
-1. You've completed the [Tutorial: Set up Azure Data Box](data-box-deploy-set-up.md).
-2. You've received your Data Box and the order status in the portal is **Delivered**.
-3. Ensure that you have the credentials of the NAS device containing your source data.
-4. You have a host computer that has the data that you want to copy over to Data Box. Your host computer must:
+* You've completed the [Tutorial: Set up Azure Data Box](data-box-deploy-set-up.md).
+* You've received your Data Box and the order status in the portal is **Delivered**.
+* Ensure that you have the credentials of the NAS device containing your source data.
+* You have a host computer that has the data that you want to copy over to Data Box. Your host computer must:
    * Run a [Supported operating system](data-box-system-requirements.md).
    * Be connected to a high-speed network. We strongly recommend that you have at least one 100-GbE connection. If a 100-GbE connection isn't available, use a 10-GbE or 1-GbE data link but the copy speeds are impacted.
 
diff --git a/articles/databox/data-box-deploy-copy-data-via-nfs.md b/articles/databox/data-box-deploy-copy-data-via-nfs.md
@@ -16,7 +16,7 @@ zone_pivot_groups: data-box-sku
 > [!IMPORTANT]
 > Azure Data Box now supports access tier assignment at the blob level. The steps contained within this tutorial reflect the updated data copy process and are specific to block blobs. 
 >
->For help with determining the appropriate access tier for your block blob data, refer to the [Determine appropriate access tiers for block blobs](#determine-appropriate-access-tiers-for-block-blobs) section. Follow the steps containined within the [Copy data to Data Box](#copy-data-to-data-box) section to copy your data to the appropriate access tier.
+>For help with determining the appropriate access tier for your block blob data, refer to the [Determine appropriate access tiers for block blobs](#determine-appropriate-access-tiers-for-block-blobs) section. Follow the steps contained within the [Copy data to Data Box](#copy-data-to-data-box) section to copy your data to the appropriate access tier.
 >
 > The information contained within this section applies to orders placed after April 1, 2024.
 
diff --git a/articles/databox/data-box-deploy-copy-data-via-rest.md b/articles/databox/data-box-deploy-copy-data-via-rest.md
@@ -17,7 +17,7 @@ zone_pivot_groups: data-box-sku
 # Tutorial: Use REST APIs to Copy data to Azure Data Box Blob storage
 
 > [!CAUTION]
-> This article references CentOS, a Linux distribution that is End Of Life (EOL) status. Please consider your use and planning accordingly. For more information, see the [CentOS End Of Life guidance](/azure/virtual-machines/workloads/centos/centos-end-of-life).
+> This article references CentOS, a Linux distribution that is end of support status. Please consider your use and planning accordingly. For more information, see the [CentOS End Of Life guidance](/azure/virtual-machines/workloads/centos/centos-end-of-life).
 
 This tutorial describes procedures to connect to Azure Data Box Blob storage via REST APIs over *http* or *https*. Once connected, the steps required to copy the data to Data Box Blob storage and prepare the Data Box to ship, are also described.
 
diff --git a/articles/databox/data-box-deploy-export-ordered.md b/articles/databox/data-box-deploy-export-ordered.md
@@ -286,7 +286,7 @@ Follow these guidelines to create your XML file if you choose to select blobs an
 
 This sample XML file includes examples of each XML tag that is used to select blobs and files for export in a Data Box export order.
 
-- For a XML file requirements, go to the **XML file overview** tab.
+- For XML file requirements, go to the **XML file overview** tab.
 - For more examples of valid blob and file prefixes, go to the **Prefix examples** tab.
 
 ```xml
diff --git a/articles/databox/data-box-deploy-set-up.md b/articles/databox/data-box-deploy-set-up.md
@@ -64,7 +64,7 @@ Perform the following steps to cable your device.
 2. Transport the device to the location where you wish to power it on. Place the device on a flat surface. The device can also be placed on a standard rack shelf.
 3. Connect the power and network cables. The backplane of a connected device for a common configuration is shown below. Depending on your environment, you could choose from other [cabling options](data-box-cable-options.md).
     
-    ![Data Box device backplane cabled](media/data-box-deploy-set-up/data-box-cabled-dhcp.png)
+    ![Screenshot illustrating the Data Box device's backplane cabled, including a diagram of data flow to the device.](media/data-box-deploy-set-up/data-box-cabled-dhcp.png)
 
     1. Connect the power cable to the labeled power input location. The other end of the power cable should be connected to a power distribution unit.
     2. Use the RJ-45 CAT 6 cable to connect the MGMT port on one end and a laptop on the other end.            
@@ -74,7 +74,7 @@ Perform the following steps to cable your device.
 
 4. Locate the power button on the front operating panel of the device. Turn on the device.
 
-    ![Data Box power button](media/data-box-deploy-set-up/data-box-powered-door-open.png)
+    ![Screenshot showing the location of the Data Box power button, illustrating that the door will remain open while the device is operating.](media/data-box-deploy-set-up/data-box-powered-door-open.png)
 :::zone-end
 
 :::zone pivot="dbx"
diff --git a/articles/databox/data-box-disk-deploy-copy-data.md b/articles/databox/data-box-disk-deploy-copy-data.md
@@ -44,7 +44,7 @@ After the disks are connected and unlocked, you can copy data from your source d
 > The information contained within this section applies to orders placed after April 1, 2024.
 
 > [!CAUTION]
-> This article references CentOS, a Linux distribution that is End Of Life (EOL) status. Please consider your use and planning accordingly.
+> This article references CentOS, a Linux distribution that is end of support status. Please consider your use and planning accordingly.
 
 This tutorial describes how to copy data from your host computer and generate checksums to verify data integrity.
 
diff --git a/articles/databox/data-box-disk-deploy-set-up.md b/articles/databox/data-box-disk-deploy-set-up.md
@@ -22,7 +22,7 @@ ms.author: shaas
 > Azure Data Box disk with hardware encryption requires a SATA III connection. All other connections, including USB, are not supported.
 
 > [!CAUTION]
-> This article references CentOS, a Linux distribution that is End Of Life (EOL) status. Please consider your use and planning accordingly. For more information, see the [CentOS End Of Life guidance](/azure/virtual-machines/workloads/centos/centos-end-of-life).
+> This article references CentOS, a Linux distribution that is end of support status. Please consider your use and planning accordingly. For more information, see the [CentOS End Of Life guidance](/azure/virtual-machines/workloads/centos/centos-end-of-life).
 
 This tutorial describes how to unpack, connect, and unlock your Azure Data Box Disk.
 
diff --git a/articles/databox/data-box-export-logs.md b/articles/databox/data-box-export-logs.md
@@ -1,6 +1,6 @@
 ---
-title: Track and log Azure Azure Data Box, Azure Data Box Next Gen, and Azure Data Box Heavy events for export order| Microsoft Docs
-description: Describes how to track and log events at the various stages of your Azure Azure Data Box, Data Box Next Gen, and Data Box Heavy export order.
+title: Track and log Azure Data Box, Azure Data Box Next Gen, and Azure Data Box Heavy events for export order| Microsoft Docs
+description: Describes how to track and log events at the various stages of your Azure Data Box, Data Box Next Gen, and Data Box Heavy export order.
 services: databox
 author: stevenmatthew
 
diff --git a/articles/databox/data-box-faq.yml b/articles/databox/data-box-faq.yml
@@ -14,7 +14,7 @@ metadata:
 
 title: "Azure Data Box: Frequently Asked Questions"
 summary:
-  The Azure Azure Data Box, Data Box Next Gen, and Data Box Heavy hybrid solution enables you to send terabytes of data to Azure in a quick, inexpensive, and reliable way using a transfer device. This FAQ contains questions and answers that you may have when you use Data Box in the Azure portal.
+  The Azure Data Box, Data Box Next Gen, and Data Box Heavy hybrid solution enables you to send terabytes of data to Azure in a quick, inexpensive, and reliable way using a transfer device. This FAQ contains questions and answers that you may have when you use Data Box in the Azure portal.
 
   Sections with tabs have some questions that apply to **Data Box only**, **Data Box Next Gen**, and **Data Box Heavy only**.
 
@@ -156,7 +156,7 @@ sections:
 
           ### I placed my Data Box order few days back. When will I receive my Data Box?
 
-          When you place an order, we check whether a device is available for your order. If a device is available, we will ship it within 10 days. It is conceivable that there are periods of high demand. In this situation, your order will be queued and you can track the status change in the Azure portal. If your order is not fulfilled in 90 days, the order is automatically cancelled.
+          When you place an order, we check whether a device is available for your order. If a device is available, we will ship it within 10 days. It is conceivable that there are periods of high demand. In this situation, your order will be queued and you can track the status change in the Azure portal. If your order is not fulfilled in 90 days, the order is automatically canceled.
 
           ## [Data Box Heavy only](#tab/data-box-heavy)
 
diff --git a/articles/databox/data-box-local-web-ui-admin.md b/articles/databox/data-box-local-web-ui-admin.md
@@ -108,7 +108,7 @@ To get the credentials for a share:
    ![Screenshot showing the Access Share And Copy Data dialog box in the local Web UI for an SMB share on the Data Box. The Copy icon for the Storage Account and Password options, and the OK button, are highlighted.](media/data-box-local-web-ui-admin/get-share-credentials-02.png)
 
 > [!NOTE]
-> After several failed share connection attempts using an incorrect password, the user account will be locked out of the share. The account lock will clear after a few minutes, and you can connect to the shares again.  
+> After several failed attempts to connect to a share while using an incorrect password, the user account will be locked out of the share. The account lock will clear after a few minutes, and you can connect to the shares again.  
 > - Data Box 4.1 and later: The account is locked for 15 minutes after 5 failed login attempts. 
 > - Data Box 4.0 and earlier: The account is locked for 30 minutes after 3 failed login attempts.
 
diff --git a/articles/databox/data-box-troubleshoot.md b/articles/databox/data-box-troubleshoot.md
@@ -167,12 +167,12 @@ For more information, see [Overview of Page blobs](../storage/blobs/storage-blob
 
 ### ERROR_DIRECTORY_DISALLOWED_FOR_TYPE
 
-**Error description:** A directory isn't allowed in any of the pre-existing folders for the managed disks. Only fixed VHDs are allowed in these folders.
+**Error description:** A directory isn't allowed in any of the preexisting folders for the managed disks. Only fixed VHDs are allowed in these folders.
 
 **Suggested resolution:** For managed disks, within each share, the following three folders are created which correspond to containers in your storage account: Premium SSD, Standard HDD, and Standard SSD. These folders correspond to the performance tier for the managed disk.
 
 - Make sure that you copy your page blob data (VHDs) into one of these existing folders.
-- A folder or directory isn't allowed in these existing folders. Remove any folders that you have created inside the pre-existing folders.
+- A folder or directory isn't allowed in these existing folders. Remove any folders that you have created inside the preexisting folders.
 
 For more information, see [Copy to managed disks](data-box-deploy-copy-data-from-vhds.md#connect-to-data-box).
 
diff --git a/includes/data-box-order-portal.md b/includes/data-box-order-portal.md
diff --git a/includes/media/data-box-order-portal/DBX-NG-Order-Portal-sku-selection-image.png b/includes/media/data-box-order-portal/DBX-NG-Order-Portal-sku-selection-image.png
diff --git a/includes/media/data-box-order-portal/dbx-ng-order-portal-sku-selection-image-lrg.png b/includes/media/data-box-order-portal/dbx-ng-order-portal-sku-selection-image-lrg.png
diff --git a/includes/media/data-box-order-portal/dbx-ng-review-order-page.png b/includes/media/data-box-order-portal/dbx-ng-review-order-page.png

Original file line number	Diff line number	Diff line change
`@@ -16,7 +16,7 @@ zone_pivot_groups: data-box-sku`
`16`	`16`	`> [!IMPORTANT]`
`17`	`17`	`> Azure Data Box now supports access tier assignment at the blob level. The steps contained within this tutorial reflect the updated data copy process and are specific to block blobs.`
`18`	`18`	`>`
`19`		`->For help with determining the appropriate access tier for your block blob data, refer to the [Determine appropriate access tiers for block blobs](#determine-appropriate-access-tiers-for-block-blobs) section. Follow the steps containined within the [Copy data to Data Box](#copy-data-to-data-box) section to copy your data to the appropriate access tier.`
	`19`	`+>For help with determining the appropriate access tier for your block blob data, refer to the [Determine appropriate access tiers for block blobs](#determine-appropriate-access-tiers-for-block-blobs) section. Follow the steps contained within the [Copy data to Data Box](#copy-data-to-data-box) section to copy your data to the appropriate access tier.`
`20`	`20`	`>`
`21`	`21`	`> The information contained within this section applies to orders placed after April 1, 2024.`
`22`	`22`