Merge branch 'MicrosoftDocs:main' into Broken-link-fix-wenxwei

Author: pritamso

articles/healthcare-apis/iot/deploy-new-bicep-powershell-cli.md

@@ -5,7 +5,7 @@ author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: quickstart
-ms.date: 12/16/2022
+ms.date: 12/27/2022
 ms.author: jasteppe
 ---
 
@@ -168,15 +168,15 @@ When deployment is completed, the following resources and access roles are creat
 
 - Azure Event Hubs namespace and device message event hub. In this deployment, the device message 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*.
 
-- The Azure Event Hubs Data Sender role. In this deployment, the sender role is named *devicedatasender*.
+  - 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](/azure/event-hubs/authorize-access-shared-access-signature). 
 
 - A Health Data Services workspace.
 
 - A Health Data Services Fast Healthcare Interoperability Resources (FHIR®) service.
 
-- An instance of the MedTech service for Health Data Services, 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.
 

articles/healthcare-apis/iot/deploy-new-button.md

@@ -5,7 +5,7 @@ author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: quickstart
-ms.date: 12/16/2022
+ms.date: 12/27/2022
 ms.author: jasteppe
 ---
 
@@ -98,15 +98,15 @@ When deployment is completed, the following resources and access roles are creat
 
 - Azure Event Hubs namespace and device message event hub. In this deployment, the device message 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*.
 
-- The Azure Event Hubs Data Sender role. In this deployment, the sender role is named *devicedatasender*.
+  - 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](/azure/event-hubs/authorize-access-shared-access-signature).
 
 - A Health Data Services workspace.
 
 - A Health Data Services Fast Healthcare Interoperability Resources (FHIR®) service.
 
-- An instance of the MedTech service for Health Data Services, 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.
 

articles/healthcare-apis/iot/deploy-new-powershell-cli.md

@@ -5,7 +5,7 @@ author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: quickstart
-ms.date: 12/16/2022
+ms.date: 12/27/2022
 ms.author: jasteppe
 ---
 
@@ -161,15 +161,15 @@ When deployment is completed, the following resources and access roles are creat
 
 - Azure Event Hubs namespace and device message event hub. In this deployment, the device message 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*.
 
-- The Azure Event Hubs Data Sender role. In this deployment, the sender role is named *devicedatasender*.
+  - 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](/azure/event-hubs/authorize-access-shared-access-signature).
 
 - A Health Data Services workspace.
 
 - A Health Data Services Fast Healthcare Interoperability Resources (FHIR®) service.
 
-- An instance of the MedTech service for Health Data Services, 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.
 

articles/healthcare-apis/iot/device-data-through-iot-hub.md

@@ -6,7 +6,7 @@ author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: iomt
 ms.topic: tutorial 
-ms.date: 12/22/2022
+ms.date: 12/27/2022
 ms.author: jasteppe
 ---
 
@@ -117,9 +117,9 @@ When deployment is completed, the following resources and access roles are creat
 
 - An Azure Event Hubs namespace and a device message 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 role is named *devicedatasender*. The Azure Event Hubs Data Sender role isn't used in this tutorial.
+  - 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](/azure/event-hubs/authorize-access-shared-access-signature). The Azure Event Hubs Data Sender role isn't used in this tutorial.
 
 - An Azure IoT Hub with [message routing](../../iot-hub/iot-hub-devguide-messages-d2c.md) configured to send device messages to the device message event hub.
 
@@ -129,7 +129,7 @@ When deployment is completed, the following resources and access roles are creat
 
 - A Health Data Services FHIR service.
 
-- A Health Data Services MedTech service with the required [system-assigned managed identity](../../active-directory/managed-identities-azure-resources/overview.md) access 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.