Skip to content

Commit dd61a9f

Browse files
committed
Deploy touchups
1 parent 20fae60 commit dd61a9f

File tree

3 files changed

+3
-12
lines changed

3 files changed

+3
-12
lines changed
-9.68 KB
Loading

articles/iot-operations/deploy-iot-ops/overview-deploy.md

Lines changed: 2 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.date: 11/06/2024
1212

1313
# Deployment details
1414

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.
1616

1717
## Supported environments
1818

@@ -44,23 +44,14 @@ A deployment with only test settings:
4444

4545
* Doesn't configure secrets or user-assigned managed identity capabilities.
4646
* 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).
5248

5349
### Secure settings deployment
5450

5551
A deployment with secure settings:
5652

5753
* 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.
5854

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.
62-
1. Then, [Deploy Azure IoT Operations](./howto-deploy-iot-operations.md).
63-
6455
## Required permissions
6556

6657
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).

articles/iot-operations/overview-iot-operations.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ Azure IoT Operations:
1919
* Is built from ground up by using Kubernetes native applications.
2020
* Includes an industrial-grade, edge-native MQTT broker that powers event-driven architectures.
2121
* 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).
2323
* Can integrate customer workloads into the platform to create a unified solution.
2424
* Supports GitOps configuration as code for deployment and updates.
2525
* 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

Comments
 (0)