You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/healthcare-apis/iot/deploy-iot-connector-in-azure.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -244,9 +244,9 @@ Tags are name and value pairs used for categorizing resources. For more informat
244
244
245
245
:::image type="content" source="media\iot-deploy-manual-in-portal\display-medtech-service-configurations.png" alt-text="Screenshot of the MedTech service main configuration page." lightbox="media\iot-deploy-manual-in-portal\display-medtech-service-configurations.png":::
246
246
247
-
## Granting the MedTech service system-assigned managed identity access to the event hub and FHIR service
247
+
## Granting the MedTech service access to the device message event hub and FHIR service
248
248
249
-
To ensure that your MedTech service works properly, it's system-assigned managed identity must be granted access permissions to the device message event hub and FHIR service.
249
+
To ensure that your MedTech service works properly, it's system-assigned managed identity must be granted access permissions to your device message event hub and FHIR service.
250
250
251
251
### Granting access to the device message event hub
0 commit comments