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-new-bicep-powershell-cli.md
+6-4Lines changed: 6 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ author: msjasteppe
5
5
ms.service: healthcare-apis
6
6
ms.subservice: fhir
7
7
ms.topic: quickstart
8
-
ms.date: 12/02/2022
8
+
ms.date: 12/03/2022
9
9
ms.author: jasteppe
10
10
---
11
11
@@ -38,11 +38,13 @@ To begin your deployment and complete the quickstart, you must have the followin
38
38
39
39
When you have these prerequisites, you're ready to deploy the Bicep file.
40
40
41
-
## Review the Bicep file - Optional
41
+
## Review the Bicep file
42
42
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/).
44
44
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.
46
48
47
49
## Deploy the MedTech service with the Bicep file and Azure PowerShell
Copy file name to clipboardExpand all lines: articles/healthcare-apis/iot/deploy-new-button.md
+6-7Lines changed: 6 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ author: msjasteppe
5
5
ms.service: healthcare-apis
6
6
ms.subservice: fhir
7
7
ms.topic: quickstart
8
-
ms.date: 12/02/2022
8
+
ms.date: 12/03/2022
9
9
ms.author: jasteppe
10
10
---
11
11
@@ -17,7 +17,8 @@ In this quickstart, you'll learn how to:
17
17
18
18
> [!div class="checklist"]
19
19
> - 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.
21
22
22
23
> [!TIP]
23
24
> 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
34
35
35
36
When you have these prerequisites, you're ready to configure the ARM template by using the **Deploy to Azure** button.
36
37
37
-
## Review the ARM template - Optional
38
+
## Review the ARM template
38
39
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).
40
41
41
42
## Use the Deploy to Azure button
42
43
43
44
To begin deployment in the Azure portal, select the **Deploy to Azure** button:
44
45
45
46
[](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).
46
47
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
-
49
48
## Configure the deployment
50
49
51
50
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
117
116
118
117
## Next steps
119
118
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
121
120
122
121
> [!div class="nextstepaction"]
123
122
> [Choose a deployment method for the MedTech service](deploy-new-choose.md)
Copy file name to clipboardExpand all lines: articles/healthcare-apis/iot/deploy-new-powershell-cli.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ author: msjasteppe
5
5
ms.service: healthcare-apis
6
6
ms.subservice: fhir
7
7
ms.topic: quickstart
8
-
ms.date: 12/02/2022
8
+
ms.date: 12/03/2022
9
9
ms.author: jasteppe
10
10
---
11
11
@@ -35,9 +35,9 @@ To begin your deployment and complete the quickstart, you must have the followin
35
35
36
36
When you have these prerequisites, you're ready to deploy the ARM template.
37
37
38
-
## Review the ARM template - Optional
38
+
## Review the ARM template
39
39
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/).
41
41
42
42
## Deploy the MedTech service with the Azure Resource Manager template and Azure PowerShell
Copy file name to clipboardExpand all lines: articles/healthcare-apis/iot/device-data-through-iot-hub.md
+4-6Lines changed: 4 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ author: msjasteppe
6
6
ms.service: healthcare-apis
7
7
ms.subservice: iomt
8
8
ms.topic: tutorial
9
-
ms.date: 12/02/2022
9
+
ms.date: 12/03/2022
10
10
ms.author: jasteppe
11
11
---
12
12
@@ -48,18 +48,16 @@ To begin your deployment and complete the tutorial, you must have the following
48
48
49
49
When you have these prerequisites, you're ready to configure the ARM template by using the **Deploy to Azure** button.
50
50
51
-
## Review the ARM template - Optional
51
+
## Review the ARM template
52
52
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).
54
54
55
55
## Use the Deploy to Azure button
56
56
57
57
To begin deployment in the Azure portal, select the **Deploy to Azure** button:
58
58
59
59
[](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)
60
60
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
-
63
61
## Configure the deployment
64
62
65
63
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
209
207
210
208
## Review metrics from the test message
211
209
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).
213
211
214
212
For your MedTech service metrics, you can see that your MedTech service completed the following steps for the test message:
0 commit comments