Skip to content

Commit 3de5587

Browse files
Merge pull request #220301 from msjasteppe/quick-fix
Quick fix.
2 parents 076f6c3 + f7c9d70 commit 3de5587

File tree

4 files changed

+19
-20
lines changed

4 files changed

+19
-20
lines changed

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

Lines changed: 6 additions & 4 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: 12/02/2022
8+
ms.date: 12/03/2022
99
ms.author: jasteppe
1010
---
1111

@@ -38,11 +38,13 @@ To begin your deployment and complete the quickstart, you must have the followin
3838

3939
When you have these prerequisites, you're ready to deploy the Bicep file.
4040

41-
## Review the Bicep file - Optional
41+
## Review the Bicep file
4242

43-
The Bicep file that you use to deploy the resources in this quickstart is available at [Azure Quickstart Templates](/samples/azure/azure-quickstart-templates/iotconnectors/) by using the *main.bicep* file on [GitHub](https://github.com/azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.healthcareapis/workspaces/iotconnectors/).
43+
The Bicep file used to deploy the resources in this quickstart is available at [Azure Quickstart Templates](/samples/azure/azure-quickstart-templates/iotconnectors/) by using the *main.bicep* file on [GitHub](https://github.com/azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.healthcareapis/workspaces/iotconnectors/).
4444

45-
1. Save the Bicep file locally as *main.bicep*. You'll need to have the working directory of your Azure PowerShell or the Azure CLI console pointing to the location where this file is saved.
45+
## Save the Bicep file locally
46+
47+
Save the Bicep file locally as *main.bicep*. You'll need to have the working directory of your Azure PowerShell or the Azure CLI console pointing to the location where this file is saved.
4648

4749
## Deploy the MedTech service with the Bicep file and Azure PowerShell
4850

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

Lines changed: 6 additions & 7 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: 12/02/2022
8+
ms.date: 12/03/2022
99
ms.author: jasteppe
1010
---
1111

@@ -17,7 +17,8 @@ In this quickstart, you'll learn how to:
1717

1818
> [!div class="checklist"]
1919
> - Open an ARM template in the Azure portal.
20-
> - Configure the template for your deployment.
20+
> - Configure the ARM template for your deployment.
21+
> - Deploy the ARM template.
2122
2223
> [!TIP]
2324
> To learn more about ARM templates, see [What are ARM templates?](./../../azure-resource-manager/templates/overview.md)
@@ -34,18 +35,16 @@ To begin your deployment and complete the quickstart, you must have the followin
3435

3536
When you have these prerequisites, you're ready to configure the ARM template by using the **Deploy to Azure** button.
3637

37-
## Review the ARM template - Optional
38+
## Review the ARM template
3839

39-
The ARM template that you use to deploy the resources in this quickstart is available at [Azure Quickstart Templates](/samples/azure/azure-quickstart-templates/iotconnectors-with-iothub/) by using the *azuredeploy.json* file on [GitHub](https://github.com/azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.healthcareapis/workspaces/iotconnectors-with-iothub).
40+
The ARM template used to deploy the resources in this quickstart is available at [Azure Quickstart Templates](/samples/azure/azure-quickstart-templates/iotconnectors-with-iothub/) by using the *azuredeploy.json* file on [GitHub](https://github.com/azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.healthcareapis/workspaces/iotconnectors-with-iothub).
4041

4142
## Use the Deploy to Azure button
4243

4344
To begin deployment in the Azure portal, select the **Deploy to Azure** button:
4445

4546
[![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).
4647

47-
The button calls an ARM template from the [Azure Quickstart Templates](/samples/azure/azure-quickstart-templates/iotconnectors/) to get information from your Azure subscription environment and begin deploying the MedTech service by using the Azure portal.
48-
4948
## Configure the deployment
5049

5150
1. In the Azure portal, on the Basics tab of the Azure Quickstart Template, select or enter the following information for your deployment:
@@ -117,7 +116,7 @@ After you've successfully deployed an instance of the MedTech service, you'll st
117116

118117
## Next steps
119118

120-
In this article, you learned how to deploy the MedTech service in the Azure portal using an ARM template with a **Deploy to Azure** button. To learn more about other methods of deployment, see
119+
In this quickstart, you learned how deploy the MedTech service in the Azure portal using an ARM template with a **Deploy to Azure** button. To learn more about other methods of deploying the MedTech service, see
121120

122121
> [!div class="nextstepaction"]
123122
> [Choose a deployment method for the MedTech service](deploy-new-choose.md)

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

Lines changed: 3 additions & 3 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: 12/02/2022
8+
ms.date: 12/03/2022
99
ms.author: jasteppe
1010
---
1111

@@ -35,9 +35,9 @@ To begin your deployment and complete the quickstart, you must have the followin
3535

3636
When you have these prerequisites, you're ready to deploy the ARM template.
3737

38-
## Review the ARM template - Optional
38+
## Review the ARM template
3939

40-
The ARM template that you use to deploy the resources in this quickstart is available at [Azure Quickstart Templates](/samples/azure/azure-quickstart-templates/iotconnectors/) by using the *azuredeploy.json* file on [GitHub](https://github.com/azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.healthcareapis/workspaces/iotconnectors/).
40+
The ARM template used to deploy the resources in this quickstart is available at [Azure Quickstart Templates](/samples/azure/azure-quickstart-templates/iotconnectors/) by using the *azuredeploy.json* file on [GitHub](https://github.com/azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.healthcareapis/workspaces/iotconnectors/).
4141

4242
## Deploy the MedTech service with the Azure Resource Manager template and Azure PowerShell
4343

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

Lines changed: 4 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: msjasteppe
66
ms.service: healthcare-apis
77
ms.subservice: iomt
88
ms.topic: tutorial
9-
ms.date: 12/02/2022
9+
ms.date: 12/03/2022
1010
ms.author: jasteppe
1111
---
1212

@@ -48,18 +48,16 @@ To begin your deployment and complete the tutorial, you must have the following
4848

4949
When you have these prerequisites, you're ready to configure the ARM template by using the **Deploy to Azure** button.
5050

51-
## Review the ARM template - Optional
51+
## Review the ARM template
5252

53-
The ARM template that you use to deploy the resources in this tutorial is available at [Azure Quickstart Templates](/samples/azure/azure-quickstart-templates/iotconnectors-with-iothub/) by using the *azuredeploy.json* file on [GitHub](https://github.com/azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.healthcareapis/workspaces/iotconnectors-with-iothub).
53+
The ARM template used to deploy the resources in this tutorial is available at [Azure Quickstart Templates](/samples/azure/azure-quickstart-templates/iotconnectors-with-iothub/) by using the *azuredeploy.json* file on [GitHub](https://github.com/azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.healthcareapis/workspaces/iotconnectors-with-iothub).
5454

5555
## Use the Deploy to Azure button
5656

5757
To begin deployment in the Azure portal, select the **Deploy to Azure** button:
5858

5959
[![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)
6060

61-
The button calls an ARM template from [Azure Quickstart Templates](https://azure.microsoft.com/resources/templates/iotconnectors-with-iothub/) to get information from your Azure subscription environment and begin deploying the MedTech service and Azure IoT Hub by using the Azure portal.
62-
6361
## Configure the deployment
6462

6563
1. In the Azure portal, on the **Basics** tab of the Azure Quickstart Template, select or enter the following information for your deployment:
@@ -209,7 +207,7 @@ You complete the steps by using Visual Studio Code with the Azure IoT Hub extens
209207

210208
## Review metrics from the test message
211209

212-
Now that you've successfully sent a test message to your IoT hub, review your MedTech service metrics. You review metrics to verify that your MedTech service received, transformed, and persisted the test message to your FHIR service. To learn more, see [How to display the MedTech service monitoring tab metrics](how-to-use-monitoring-tab.md).
210+
Now that you've successfully sent a test message to your IoT hub, review your MedTech service metrics. You review metrics to verify that your MedTech service received, grouped, transformed, and persisted the test message to your FHIR service. To learn more, see [How to display the MedTech service monitoring tab metrics](how-to-use-monitoring-tab.md).
213211

214212
For your MedTech service metrics, you can see that your MedTech service completed the following steps for the test message:
215213

0 commit comments

Comments
 (0)