Merge pull request #235836 from msjasteppe/fixing-media-folders

Updating media folder names

Author: AnnaMHuff

articles/healthcare-apis/iot/deploy-arm-template.md

@@ -1,12 +1,12 @@
 ---
 title: Deploy the MedTech service using an Azure Resource Manager template - Azure Health Data Services
-description: In this article, you'll learn how to deploy the MedTech service using an Azure Resource Manager template.
+description: Learn how to deploy the MedTech service using an Azure Resource Manager template.
 author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.custom: devx-track-arm-template
 ms.topic: quickstart
-ms.date: 04/14/2023
+ms.date: 04/25/2023
 ms.author: jasteppe
 ---
 
@@ -17,7 +17,7 @@ ms.author: jasteppe
 
 To implement infrastructure as code for your Azure solutions, use Azure Resource Manager templates (ARM templates). The template is a [JavaScript Object Notation (JSON)](https://www.json.org/) file that defines the infrastructure and configuration for your project. The template uses declarative syntax, which lets you state what you intend to deploy without having to write the sequence of programming commands to create it. In the template, you specify the resources to deploy and the properties for those resources. 
 
-In this quickstart, you'll learn how to:
+In this quickstart, learn how to:
 
 - Open an ARM template in the Azure portal.
 - Configure the ARM template for your deployment.
@@ -40,7 +40,7 @@ When you have these prerequisites, you're ready to configure the ARM template by
 
 ## Review the ARM template - Optional
 
-The ARM template used to deploy the resources in this quickstart is available at [Azure Quickstart Templates](/samples/azure/azure-quickstart-templates/iotconnectors-with-iothub/) by using the *azuredeploy.json* file on [GitHub](https://github.com/azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.healthcareapis/workspaces/iotconnectors-with-iothub). 
+The ARM template used to deploy the resources in this quickstart is available at [Azure Quickstart Templates](/samples/azure/azure-quickstart-templates/iotconnectors/) by using the *azuredeploy.json* file on [GitHub](https://github.com/azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.healthcareapis/workspaces/iotconnectors/). 
 
 ## Use the Deploy to Azure button
 
@@ -66,23 +66,23 @@ To begin deployment in the Azure portal, select the **Deploy to Azure** button:
 
    - **Destination Mapping** - Don't change the default values for this quickstart.
 
-   :::image type="content" source="media\deploy-new-arm\iot-deploy-quickstart-options.png" alt-text="Screenshot of Azure portal page displaying deployment options for the Azure Health Data Service MedTech service." lightbox="media\deploy-new-arm\iot-deploy-quickstart-options.png":::
+   :::image type="content" source="media\deploy-arm-template\iot-deploy-quickstart-options.png" alt-text="Screenshot of Azure portal page displaying deployment options for the Azure Health Data Service MedTech service." lightbox="media\deploy-arm-template\iot-deploy-quickstart-options.png":::
 
 2. To validate your configuration, select **Review + create**.
 
-   :::image type="content" source="media\deploy-new-arm\iot-review-and-create-button.png" alt-text="Screenshot that shows the Review + create button selected in the Azure portal.":::
+   :::image type="content" source="media\deploy-arm-template\iot-review-and-create-button.png" alt-text="Screenshot that shows the Review + create button selected in the Azure portal.":::
 
 3. In **Review + create**, check the template validation status. If validation is successful, the template displays **Validation Passed**. If validation fails, fix the detail that's indicated in the error message, and then select **Review + create** again.
 
-   :::image type="content" source="media\deploy-new-arm\iot-validation-completed.png" alt-text="Screenshot that shows the Review + create pane displaying the Validation Passed message.":::
+   :::image type="content" source="media\deploy-arm-template\iot-validation-completed.png" alt-text="Screenshot that shows the Review + create pane displaying the Validation Passed message.":::
 
 4. After a successful validation, to begin the deployment, select **Create**.
 
-   :::image type="content" source="media\deploy-new-arm\iot-create-button.png" alt-text="Screenshot that shows the highlighted Create button.":::
+   :::image type="content" source="media\deploy-arm-template\iot-create-button.png" alt-text="Screenshot that shows the highlighted Create button.":::
 
 5. In a few minutes, the Azure portal displays the message that your deployment is completed.
 
-   :::image type="content" source="media\deploy-new-arm\iot-deployment-complete-banner.png" alt-text="Screenshot that shows a green checkmark and the message Your deployment is complete.":::
+   :::image type="content" source="media\deploy-arm-template\iot-deployment-complete-banner.png" alt-text="Screenshot that shows a green checkmark and the message Your deployment is complete.":::
 
    > [!IMPORTANT]
    > If you're going to allow access from multiple services to the device message event hub, it's required that each service has its own event hub consumer group.
@@ -91,29 +91,29 @@ To begin deployment in the Azure portal, select the **Deploy to Azure** button:
    >
    > Examples:
    >
-   > - Two MedTech services accessing the same device message event hub.
+   > * Two MedTech services accessing the same device message event hub.
    >
-   > - A MedTech service and a storage writer application accessing the same device message event hub.
+   > * A MedTech service and a storage writer application accessing the same device message event hub.
 
 ## Review deployed resources and access permissions
 
 When deployment is completed, the following resources and access roles are created in the ARM template deployment:
 
-- Azure Event Hubs namespace and device message event hub. In this deployment, the device message event hub is named *devicedata*.
+* Event Hubs namespace and event hub. In this deployment, the event hub is named *devicedata*.
 
-  - An event hub consumer group. In this deployment, the consumer group is named *$Default*.
+  * An event hub consumer group. In this deployment, the consumer group is named *$Default*.
 
-  - An Azure Event Hubs Data Sender role. In this deployment, the sender role is named *devicedatasender* and can be used to provide access to the device event hub using a shared access signature (SAS). To learn more about authorizing access using a SAS, see [Authorizing access to Event Hubs resources using Shared Access Signatures](../../event-hubs/authorize-access-shared-access-signature.md).
+  * An Azure Event Hubs Data Sender role. In this deployment, the sender role is named *devicedatasender* and can be used to provide access to the device event hub using a shared access signature (SAS). To learn more about authorizing access using a SAS, see [Authorizing access to Event Hubs resources using Shared Access Signatures](../../event-hubs/authorize-access-shared-access-signature.md).
 
-- A Health Data Services workspace.
+* A Health Data Services workspace.
 
-- A Health Data Services Fast Healthcare Interoperability Resources FHIR service.
+* A Health Data Services Fast Healthcare Interoperability Resources FHIR service.
 
-- A Health Data Services MedTech service with the required [system-assigned managed identity](../../active-directory/managed-identities-azure-resources/overview.md) roles:
+* A Health Data Services MedTech service with the required [system-assigned managed identity](../../active-directory/managed-identities-azure-resources/overview.md) roles:
 
-  - For the device message event hub, the Azure Events Hubs Data Receiver role is assigned in the [Access control section (IAM)](../../role-based-access-control/overview.md) of the device message event hub.
+  * For the event hub, the Azure Event Hubs Data Receiver role is assigned in the [Access control section (IAM)](../../role-based-access-control/overview.md) of the device message event hub.
 
-  - For the FHIR service, the FHIR Data Writer role is assigned in the [Access control section (IAM)](../../role-based-access-control/overview.md) of the FHIR service.
+  * For the FHIR service, the FHIR Data Writer role is assigned in the [Access control section (IAM)](../../role-based-access-control/overview.md) of the FHIR service.
 
 > [!IMPORTANT]
 > In this quickstart, the ARM template configures the MedTech service to operate in **Create** mode. A patient resource and a device resource are created for each device that sends data to your FHIR service.
@@ -122,15 +122,15 @@ When deployment is completed, the following resources and access roles are creat
 
 ## Post-deployment mappings
 
-After you've successfully deployed an instance of the MedTech service, you'll still need to provide conforming and valid device and FHIR destination mappings.
+After you have successfully deployed an instance of the MedTech service, you'll still need to provide conforming and valid device and FHIR destination mappings.
 
- - To learn about the device mapping, see [Overview of the MedTech service device mapping](overview-of-device-mapping.md).
+ * To learn about the device mapping, see [Overview of the MedTech service device mapping](overview-of-device-mapping.md).
 
- - To learn about the FHIR destination mapping, see [Overview of the MedTech service FHIR destination mapping](overview-of-fhir-destination-mapping.md).
+ * To learn about the FHIR destination mapping, see [Overview of the MedTech service FHIR destination mapping](overview-of-fhir-destination-mapping.md).
 
 ## Next steps
 
-In this quickstart, you learned how to deploy an instance of the MedTech service in the Azure portal using an ARM template with a **Deploy to Azure** button. 
+In this quickstart, you learned how to deploy the MedTech service in the Azure portal using an ARM template with the **Deploy to Azure** button. 
 
 To learn about other methods for deploying the MedTech service, see
 

articles/healthcare-apis/iot/deploy-manual-config.md

@@ -77,7 +77,7 @@ Follow these six steps to fill in the Basics tab configuration:
 
 The Basics tab should now look like this after you've filled it out:
 
-  :::image type="content" source="media\deploy-new-config\select-device-mapping-button.png" alt-text="Screenshot of Basics tab filled out correctly." lightbox="media\deploy-new-config\select-device-mapping-button.png":::
+  :::image type="content" source="media\deploy-manual-config\select-device-mapping-button.png" alt-text="Screenshot of Basics tab filled out correctly." lightbox="media\deploy-manual-config\select-device-mapping-button.png":::
 
 You're now ready to select the Device mapping tab and begin setting up the device mappings for your MedTech service.
 
@@ -186,7 +186,7 @@ To begin the validation process of your MedTech service deployment, select the *
 
 Your validation screen should look something like this:
 
-   :::image type="content" source="media\deploy-new-config\validate-and-review-medtech-service.png" alt-text="Screenshot of validation success with details displayed." lightbox="media\deploy-new-config\validate-and-review-medtech-service.png":::
+   :::image type="content" source="media\deploy-manual-config\validate-and-review-medtech-service.png" alt-text="Screenshot of validation success with details displayed." lightbox="media\deploy-manual-config\validate-and-review-medtech-service.png":::
 
 If your MedTech service didn't validate, review the validation failure message, and troubleshoot the issue. Check all properties under each MedTech service tab that you've configured. Go back and try again.
 

articles/healthcare-apis/iot/deploy-manual-post.md

@@ -5,7 +5,7 @@ author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: quickstart
-ms.date: 03/10/2023
+ms.date: 04/25/2023
 ms.author: jasteppe
 ---
 
@@ -31,7 +31,7 @@ When you're satisfied with your configuration and it has been successfully valid
 
 Your screen should look something like this:
 
-   :::image type="content" source="media\deploy-new-deploy\created-medtech-service.png" alt-text="Screenshot of the MedTech service deployment completion." lightbox="media\deploy-new-deploy\created-medtech-service.png":::
+   :::image type="content" source="media\deploy-manual-post\created-medtech-service.png" alt-text="Screenshot of the MedTech service deployment completion." lightbox="media\deploy-manual-post\created-medtech-service.png":::
 
 ## Manual post-deployment requirements
 
@@ -79,7 +79,7 @@ Follow these steps to grant access to the device message event hub:
 
 13. After the role assignment has been successfully added to the event hub, a notification will display on your screen with a green check mark. This notification indicates that your MedTech service can now read from your device message event hub. It should look like this:
 
-    :::image type="content" source="media\deploy-new-deploy\validate-medtech-service-managed-identity-added-to-event-hub.png" alt-text="Screenshot of the MedTech service system-assigned managed identity being successfully granted access to the event hub with a red box around the message." lightbox="media\deploy-new-deploy\validate-medtech-service-managed-identity-added-to-event-hub.png":::
+    :::image type="content" source="media\deploy-manual-post\validate-medtech-service-managed-identity-added-to-event-hub.png" alt-text="Screenshot of the MedTech service system-assigned managed identity being successfully granted access to the event hub with a red box around the message." lightbox="media\deploy-manual-post\validate-medtech-service-managed-identity-added-to-event-hub.png":::
 
 For more information about authorizing access to Event Hubs resources, see [Authorize access with Azure Active Directory](../../event-hubs/authorize-access-azure-active-directory.md).