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-iot-connector-in-azure.md
+5-5Lines changed: 5 additions & 5 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: v-smcevoy
11
11
12
12
# Choose a deployment method
13
13
14
-
MedTech service provides multiple methods for deploying it into an Azure Platform as a service (PaaS) configuration. Each method has different advantages that allow you to customize your development environment to suit your needs.
14
+
MedTech service provides multiple methods for deploying it into an Azure Platform as a service (PaaS) configuration. Each method has different advantages that will allow you to customize your development environment to suit your needs.
15
15
16
16
The different deployment methods are:
17
17
@@ -21,25 +21,25 @@ The different deployment methods are:
21
21
22
22
## Azure ARM QuickStart template with Deploy to Azure button
23
23
24
-
Using a Quickstart template with Azure portal is the easiest and fastest method because it automates most of your configuration with the touch of a **Deploy to Azure** button. This button automatically generates the following configurations and resources: managed identity RBAC roles, a provisioned workspace and namespace, an Event Hubs instance, a FHIR service instance, and a MedTech service instance. All you need to add are post-deployment device mapping, destination mapping, and a shared access policy key. This method simplifies your deployment but does not allow for much customization.
24
+
Using a Quickstart template with Azure portal is the easiest and fastest deployment method because it automates most of your configuration with the touch of a **Deploy to Azure** button. This button automatically generates the following configurations and resources: managed identity RBAC roles, a provisioned workspace and namespace, an Event Hubs instance, a FHIR service instance, and a MedTech service instance. All you need to add are post-deployment device mapping, destination mapping, and a shared access policy key. This method simplifies your deployment, but does not allow for much customization.
25
25
26
26
For more information about the Quickstart template and the Deploy to Azure button, see [Deploy the MedTech service with a QuickStart template](deploy-02-new-button.md).
27
27
28
28
## Azure PowerShell and Azure CLI automation
29
29
30
-
Deploying MedTech service with Azure PowerShell or Azure CLI can be useful for adding automation to scale your deployment to a large number of developers. Azure provides Azure PowerShell and Azure CLI to speed up your configurations when used in enterprise environments. This method is more detailed but provides extra speed and efficiency because it allows you to add automation.
30
+
Azure provides Azure PowerShell and Azure CLI to speed up your configurations when used in enterprise environments. Deploying MedTech service with Azure PowerShell or Azure CLI can be useful for adding automation so that you can scale your deployment for a large number of developers. This method is more detailed but provides extra speed and efficiency because it allows you to add automation.
31
31
32
32
For more information about Using an ARM template with Azure PowerShell and Azure CLI, see [Using Azure PowerShell and Azure CLI to deploy the MedTech service using Azure Resource Manager templates](/deploy-08-new-ps-cli.md).
33
33
34
34
## Manual deployment
35
35
36
-
This method used Azure portal to implement deployment task individually. This procedure can be beneficial if you need to customize or troubleshoot your deployment process, because you will be able to see all the details of how to complete the sequence of each task. This is the most complex method but it provides valuable information and options that will enable you to fine-tune your deployment very precisely.
36
+
The manual deployment method uses Azure portal to implement each deployment task individually. There are no shortcuts. Because you will be able to see all the details of how to complete the sequence of each task, this procedure can be beneficial if you need to customize or troubleshoot your deployment process. This is the most complex method, but it provides valuable technical information and developmental options that will enable you to fine-tune your deployment very precisely.
37
37
38
38
For more information about manual deployment with portal, see [Overview of how to manually deploy the MedTech service using the Azure portal](/deploy-03-new-manual.md).
39
39
40
40
## Deployment architecture overview
41
41
42
-
The following diagram outlines the basic steps of MedTech service deployment and shows how these steps fit together with its data processing. This may help you analyze the data flow of which method is best for you.
42
+
The following data-flow diagram outlines the basic steps of MedTech service deployment and shows how these steps fit together with its data processing procedures. This may help you analyze the options and determine which deployment method is best for you.
43
43
44
44
:::image type="content" source="media/iot-get-started/get-started-with-iot.png" alt-text="Diagram showing MedTech service architecture overview." lightbox="media/iot-get-started/get-started-with-iot.png":::
0 commit comments