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/iot-operations/deploy-iot-ops/overview-deploy.md
+2-11Lines changed: 2 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ ms.date: 11/06/2024
12
12
13
13
# Deployment details
14
14
15
-
When you deploy Azure IoT Operations, you install a suite of services on an Azure Arc-enabled Kubernetes cluster. This article provides an overview of the different deployment options to consider for your scenario.
15
+
When you deploy Azure IoT Operations, you install a suite of services on an [Azure Arc-enabled Kubernetes cluster](/azure/azure-arc/kubernetes/overview). This article provides an overview of the different deployment options to consider for your scenario.
16
16
17
17
## Supported environments
18
18
@@ -44,23 +44,14 @@ A deployment with only test settings:
44
44
45
45
* Doesn't configure secrets or user-assigned managed identity capabilities.
46
46
* Is meant to enable the end-to-end quickstart sample for evaluation purposes, so supports the OPC PLC simulator and connects to cloud resources using system-assigned managed identity.
47
-
* Can be upgraded to use secure settings.
48
-
49
-
The quickstart scenario, [Quickstart: Run Azure IoT Operations in GitHub Codespaces](../get-started-end-to-end-sample/quickstart-deploy.md), uses test settings.
50
-
51
-
At any point, you can upgrade an Azure IoT Operations instance to use secure settings by following the steps in [Enable secure settings](howto-enable-secure-settings.md).
47
+
* Can be upgraded to use secure settings by following the steps in [Enable secure settings](howto-enable-secure-settings.md).
52
48
53
49
### Secure settings deployment
54
50
55
51
A deployment with secure settings:
56
52
57
53
* Enables secrets and user-assignment managed identity, both of which are important capabilities for developing a production-ready scenario. Secrets are used whenever Azure IoT Operations components connect to a resource outside of the cluster; for example, an OPC UA server or a dataflow endpoint.
58
54
59
-
To deploy Azure IoT Operations with secure settings, follow these articles:
60
-
61
-
1. Start with [Prepare your Azure Arc-enabled Kubernetes cluster](./howto-prepare-cluster.md) to configure and Arc-enable your cluster.
The following table describes Azure IoT Operations deployment and management tasks that require elevated permissions. For information about assigning roles to users, see [Steps to assign an Azure role](../../role-based-access-control/role-assignments-steps.md).
Copy file name to clipboardExpand all lines: articles/iot-operations/overview-iot-operations.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@ Azure IoT Operations:
19
19
* Is built from ground up by using Kubernetes native applications.
20
20
* Includes an industrial-grade, edge-native MQTT broker that powers event-driven architectures.
21
21
* Is highly extensible, scalable, resilient, and secure.
22
-
* Lets you manage edge services and resources from the cloud by using Azure Arc.
22
+
* Lets you manage edge services and resources from the cloud by using [Azure Arc](/azure/azure-arc/overview).
23
23
* Can integrate customer workloads into the platform to create a unified solution.
24
24
* Supports GitOps configuration as code for deployment and updates.
25
25
* Natively integrates with [Azure Event Hubs](../event-hubs/azure-event-hubs-kafka-overview.md), [Azure Event Grid's MQTT broker](../event-grid/mqtt-overview.md), and [Microsoft Fabric](/fabric/) in the cloud.
0 commit comments