replaced screenshot/removed bullet

Author: shellyhaverkamp

articles/healthcare-apis/dicom/deploy-dicom-services-in-azure-data-lake.md

@@ -10,7 +10,7 @@ ms.author: mmitrik
 ms.custom: mode-api, devx-track-arm-template
 ---
 
-# Deploy the DICOM service with Data Lake Storage
+# Deploy the DICOM service with Azure Data Lake Storage
 
 Deploying the [DICOM® service with Azure Data Lake Storage](dicom-data-lake.md) enables organizations to store and process imaging data in a standardized, secure, and scalable way.
 
@@ -25,7 +25,7 @@ After deployment completes, you can use the Azure portal to see the details abou
 > [!NOTE]
 > The Azure Data Lake Storage option is only available for new instances of the DICOM service. After the option becomes generally available, we plan to offer a migration path for existing DICOM service instances.
 
-## Deploy the DICOM service with Data Lake Storage using the Azure portal
+## Deploy the DICOM service with Azure Data Lake Storage by using the Azure portal
 
 1. On the **Resource group** page of the Azure portal, select the name of the **Azure Health Data Services workspace**.
 
@@ -41,9 +41,9 @@ After deployment completes, you can use the Azure portal to see the details abou
 
 1. Enter a name for the DICOM service.
 
-1. Select **External** for the Storage Location.  
+1. Select **Data Lake Storage (default)** for the storage location.  
 
-    :::image type="content" source="media/deploy-data-lake/dicom-deploy-options.png" alt-text="Screenshot showing the options in the Create DICOM service view." lightbox="media/deploy-data-lake/dicom-deploy-options.png":::
+    :::image type="content" source="media/deploy-data-lake/create-dicom-service-data-lake-sml.png" alt-text="Screenshot showing the storage location option." lightbox="media/deploy-data-lake/create-dicom-service-data-lake-smlrg":::
 
 1. Select the **subscription** and **resource group** that contains the storage account.
 

articles/healthcare-apis/dicom/deploy-dicom-services-in-azure.md

@@ -4,7 +4,7 @@ description: This article describes how to deploy the DICOM service in the Azure
 author: mmitrik
 ms.service: healthcare-apis
 ms.topic: how-to
-ms.date: 10/06/2023
+ms.date: 03/11/2024
 ms.author: mmitrik
 ms.custom: mode-api
 ---
@@ -26,19 +26,23 @@ To deploy the DICOM service, you need a workspace created in the Azure portal. F
 
 1. On the **Resource group** page of the Azure portal, select the name of your **Azure Health Data Services workspace**.
 
-   [![Screenshot that shows selecting a workspace resource group.](media/select-workspace-resource-group.png) ](media/select-workspace-resource-group.png#lightbox)
+:::image type="content" source="media/select-workspace-resource-group.png" alt-text="Screenshot showing selecting a workspace resource group." lightbox="media/select-workspace-resource-group.png":::
+
 
 1. Select **Deploy DICOM service**.
 
-   [![Screenshot that shows deploying the DICOM service.](media/workspace-deploy-dicom-services.png) ](media/workspace-deploy-dicom-services.png#lightbox)
+:::image type="content" source="media/workspace-deploy-dicom-services.png" alt-text="Screenshot showing deployment of the DICOM service." lightbox="media/workspace-deploy-dicom-services.png":::
+
 
 1. Select **Add DICOM service**.
 
-   [![Screenshot that shows adding the DICOM service.](media/add-dicom-service.png) ](media/add-dicom-service.png#lightbox)
+:::image type="content" source="media/add-dicom-service.png" alt-text="Screenshot showing how to add the DICOM service." lightbox="media/add-dicom-service.png":::
+
 
 1. Enter a name for the DICOM service, and then select **Review + create**.
 
-    [![Screenshot that shows the DICOM service name.](media/enter-dicom-service-name.png) ](media/enter-dicom-service-name.png#lightbox)
+:::image type="content" source="media/enter-dicom-service-name.png" alt-text="Screenshot showing the DICOM service name." lightbox="media/enter-dicom-service-name.png":::
+
 
 1. (Optional) Select **Next: Tags**.
 
@@ -48,11 +52,11 @@ To deploy the DICOM service, you need a workspace created in the Azure portal. F
 
 1. After the deployment process is finished, select **Go to resource**.
 
-   [![Screenshot that shows Go to resource.](media/go-to-resource.png) ](media/go-to-resource.png#lightbox)
+:::image type="content" source="media/go-to-resource.png" alt-text="Screenshot showing Go to resource." lightbox="media/go-to-resource.png":::
 
    The result of the newly deployed DICOM service is shown here.
 
-   [![Screenshot that shows the DICOM finished deployment.](media/results-deployed-dicom-service.png) ](media/results-deployed-dicom-service.png#lightbox)
+:::image type="content" source="media/results-deployed-dicom-service.png" alt-text="Screenshot showing the DICOM finished deployment." lightbox="media/results-deployed-dicom-service.png":::
 
 ## Next steps
 

articles/healthcare-apis/dicom/dicom-data-lake.md

@@ -72,7 +72,6 @@ The DICOM service with data lake storage has these limitations:
 - UPS-RS work items aren't stored in the data lake storage account.  
 - User data added to the data lake storage account isn't read and indexed by the DICOM service. It's possible that a filename collision could occur, so we recommend that you don't write data to the folder structure used by the DICOM service.
 - If DICOM data written by the DICOM service is modified or removed, errors might result when accessing data with the DICOMweb APIs.
-- Configuration of customer-managed keys isn't supported during the creation of a DICOM service when you opt to use external storage.
 - The archive access tier isn't supported. Moving data to the archive tier will result in errors when accessing data with the DICOMweb APIs.
 
 ## Next steps