Skip to content

Commit b2c865a

Browse files
authored
Merge pull request #223554 from msjasteppe/choose-edits
Updates based on usage feedback
2 parents e118541 + 6bcaadd commit b2c865a

File tree

1 file changed

+20
-9
lines changed

1 file changed

+20
-9
lines changed

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

Lines changed: 20 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: msjasteppe
55
ms.service: healthcare-apis
66
ms.subservice: fhir
77
ms.topic: quickstart
8-
ms.date: 1/5/2023
8+
ms.date: 1/10/2023
99
ms.author: jasteppe
1010
---
1111

@@ -16,27 +16,38 @@ The MedTech service provides multiple methods for deployment into Azure. Each de
1616
In this quickstart, you'll learn about these deployment methods:
1717

1818
> [!div class="checklist"]
19-
> - Azure Resource Manager template (ARM template) using the **Deploy to Azure** button.
19+
> - Azure Resource Manager template (ARM template) including an Azure Iot Hub using the **Deploy to Azure** button.
20+
> - ARM template using the **Deploy to Azure** button.
2021
> - ARM template using Azure PowerShell or the Azure CLI.
21-
> - Azure portal manually.
22+
> - Manually in the Azure portal.
23+
24+
## ARM template including an Azure Iot Hub using the Deploy to Azure button
25+
26+
Using an ARM template with the **Deploy to Azure** button is an easy and fast deployment method because it automates the deployment, most configuration steps, and uses the Azure portal. The deployed MedTech service and Azure IoT Hub are fully functional including conforming and valid device and Fast Healthcare Interoperability Resources (FHIR®) destination mappings. Use the Azure IoT Hub to create devices and send device messages to the MedTech service.
27+
28+
[![Deploy to Azure](https://aka.ms/deploytoazurebutton)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2Fazure-quickstart-templates%2Fmaster%2Fquickstarts%2Fmicrosoft.healthcareapis%2Fworkspaces%2Fiotconnectors-with-iothub%2Fazuredeploy.json)
29+
30+
To learn more about deploying the MedTech service including an Azure IoT Hub using an ARM template and the **Deploy to Azure** button, see [Receive device messages through Azure IoT Hub](device-data-through-iot-hub.md).
2231

2332
## ARM template using the Deploy to Azure button
2433

25-
Using an ARM template with the **Deploy to Azure** button is an easy and fast deployment method because it automates the deployment, most configuration steps, and uses the Azure portal.
34+
Using an ARM template with the **Deploy to Azure** button is an easy and fast deployment method because it automates the deployment, most configuration steps, and uses the Azure portal. The deployed MedTech service will still require conforming and valid device and FHIR destination mappings to be fully functional.
35+
36+
[![Deploy to Azure](https://aka.ms/deploytoazurebutton)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2Fazure-quickstart-templates%2Fmaster%2Fquickstarts%2Fmicrosoft.healthcareapis%2Fworkspaces%2Fiotconnectors%2Fazuredeploy.json).
2637

27-
To learn more about using an ARM template with the **Deploy to Azure button**, see [Deploy the MedTech service using an Azure Resource Manager template](deploy-new-arm.md).
38+
To learn more about deploying the MedTech service using an ARM template and the **Deploy to Azure** button, see [Deploy the MedTech service using an Azure Resource Manager template](deploy-new-arm.md).
2839

2940
## ARM template using Azure PowerShell or the Azure CLI
3041

31-
Using an ARM template with Azure PowerShell or the Azure CLI is a more advanced deployment method. This deployment method can be useful for adding automation and repeatability so that you can scale and customize your deployments.
42+
Using an ARM template with Azure PowerShell or the Azure CLI is a more advanced deployment method. This deployment method can be useful for adding automation and repeatability so that you can scale and customize your deployments. The deployed MedTech service will still require conforming and valid device and FHIR destination mappings to be fully functional.
3243

33-
To learn more about using an ARM template with Azure PowerShell or the Azure CLI, see [Deploy the MedTech service using an Azure Resource Manager template and Azure PowerShell or the Azure CLI](deploy-new-powershell-cli.md).
44+
To learn more about deploying the MedTech service using an ARM template and Azure PowerShell or the Azure CLI, see [Deploy the MedTech service using an Azure Resource Manager template and Azure PowerShell or the Azure CLI](deploy-new-powershell-cli.md).
3445

35-
## Azure portal manually
46+
## Manually in the Azure portal
3647

3748
Using the Azure portal manual deployment will allow you to see the details of each deployment step. The manual deployment has many steps, but it provides valuable technical information that may be useful for customizing and troubleshooting your MedTech service.
3849

39-
To learn more about using a manual deployment with the Azure portal, see [Deploy the MedTech service manually using the Azure portal](deploy-new-manual.md).
50+
To learn more about deploying the MedTech service manually using the Azure portal, see [Deploy the MedTech service manually using the Azure portal](deploy-new-manual.md).
4051

4152
## Deployment architecture overview
4253

0 commit comments

Comments
 (0)