Skip to content

Commit e0e91d1

Browse files
committed
Final edits.
1 parent 018f9fa commit e0e91d1

File tree

2 files changed

+8
-8
lines changed

2 files changed

+8
-8
lines changed

articles/healthcare-apis/iot/deploy-08-new-ps-cli.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ ms.author: jasteppe
1111

1212
# Quickstart: Deploy the MedTech service using an Azure Resource Manager template and Azure PowerShell or Azure CLI
1313

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.
1515

1616
For more information about ARM templates, see [What are ARM templates?](./../../azure-resource-manager/templates/overview.md).
1717

@@ -21,14 +21,14 @@ The ARM template used in this article is available from the [Azure Quickstart Te
2121

2222
The ARM template will help you automatically configure and deploy the following resources. Each one can be modified to meet your deployment requirements.
2323

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`).
2727
- Azure Health Data Services workspace.
2828
- Azure Health Data Services Fast Healthcare Interoperability Resources (FHIR®) service.
2929
- 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`)
3232
- 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.
3333

3434
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`
182182
183183
## Next steps
184184

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
186186

187187
> [!div class="nextstepaction"]
188188
> [Choosing a method of deployment for MedTech service in Azure](deploy-iot-connector-in-azure.md)

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -189,7 +189,7 @@ For example: `az group delete --resource-group BicepTestDeployment`
189189
190190
## Next steps
191191

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
193193

194194
> [!div class="nextstepaction"]
195195
> [Choosing a method of deployment for the MedTech service in Azure](deploy-iot-connector-in-azure.md)

0 commit comments

Comments
 (0)