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-08-new-ps-cli.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ ms.author: jasteppe
11
11
12
12
# Quickstart: Deploy the MedTech service using an Azure Resource Manager template and Azure PowerShell or Azure CLI
13
13
14
-
In this quickstart, you'll learn how to use Azure PowerShell and Azure CLI to deploy the MedTech service using an Azure Resource Manager (ARM) template. When you call the template from PowerShell or CLI, it provides automation that enables you to distribute your deployment to large numbers of developers. Using PowerShell or CLI allows for modifiable automation capabilities that will speed up your deployment configuration in enterprise environments.
14
+
In this quickstart, you'll learn how to use Azure PowerShell or Azure CLI to deploy the MedTech service using an Azure Resource Manager (ARM) template. When you call the template from PowerShell or CLI, it provides automation that enables you to distribute your deployment to large numbers of developers. Using PowerShell or CLI allows for modifiable automation capabilities that will speed up your deployment configuration in enterprise environments.
15
15
16
16
For more information about ARM templates, see [What are ARM templates?](./../../azure-resource-manager/templates/overview.md).
17
17
@@ -21,14 +21,14 @@ The ARM template used in this article is available from the [Azure Quickstart Te
21
21
22
22
The ARM template will help you automatically configure and deploy the following resources. Each one can be modified to meet your deployment requirements.
23
23
24
-
- Azure Event Hubs namespace and device message event hub (the device message event hub is named: **devicedata**).
25
-
- Azure event hub consumer group (named **$Default**).
26
-
- Azure event hub sender role (named **devicedatasender**).
24
+
- Azure Event Hubs namespace and device message event hub (the device message event hub is named: `devicedata`).
25
+
- Azure event hub consumer group (named `$Default`).
26
+
- Azure event hub sender role (named `devicedatasender`).
27
27
- Azure Health Data Services workspace.
28
28
- Azure Health Data Services Fast Healthcare Interoperability Resources (FHIR®) service.
29
29
- Azure Health Data Services MedTech service. This resource includes setup for:
30
-
-[system-assigned managed identity](../../active-directory/managed-identities-azure-resources/overview.md) access roles needed to read from the device message event hub (named **Azure Events Hubs Receiver**)
31
-
- system-assigned managed identity access roles needed to read and write to the FHIR service (named **FHIR Data Writer**)
30
+
-[system-assigned managed identity](../../active-directory/managed-identities-azure-resources/overview.md) access roles needed to read from the device message event hub (named `Azure Events Hubs Receiver`)
31
+
- system-assigned managed identity access roles needed to read and write to the FHIR service (named `FHIR Data Writer`)
32
32
- An output file containing the ARM template deployment results (named **medtech_service_ARM_template_deployment_results.txt**). The file is located in the directory from which you ran the script.
33
33
34
34
If you need to see a diagram with information on the MedTech service deployment, there's an architecture overview at [Choose a deployment method](deploy-iot-connector-in-azure.md#deployment-architecture-overview). This diagram shows the data flow steps of deployment and how MedTech service processes data into a FHIR Observation.
@@ -182,7 +182,7 @@ For example: `az group delete --resource-group ArmTestDeployment`
182
182
183
183
## Next steps
184
184
185
-
In this article, you learned how to use Azure PowerShell and Azure CLI to deploy the MedTech service using an Azure Resource Manager (ARM) template. To learn more about other methods of deployment, see
185
+
In this article, you learned how to use Azure PowerShell or Azure CLI to deploy the MedTech service using an Azure Resource Manager (ARM) template. To learn more about other methods of deployment, see
186
186
187
187
> [!div class="nextstepaction"]
188
188
> [Choosing a method of deployment for MedTech service in Azure](deploy-iot-connector-in-azure.md)
Copy file name to clipboardExpand all lines: articles/healthcare-apis/iot/deploy-new-bicep-ps-cli.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -189,7 +189,7 @@ For example: `az group delete --resource-group BicepTestDeployment`
189
189
190
190
## Next steps
191
191
192
-
In this article, you learned how to use Azure PowerShell and Azure CLI to deploy an instance of the MedTech service using a Bicep file. To learn more about other methods of deploying the MedTech service, see
192
+
In this article, you learned how to use Azure PowerShell or Azure CLI to deploy an instance of the MedTech service using a Bicep file. To learn more about other methods of deploying the MedTech service, see
193
193
194
194
> [!div class="nextstepaction"]
195
195
> [Choosing a method of deployment for the MedTech service in Azure](deploy-iot-connector-in-azure.md)
0 commit comments