Tento prehliadač už nie je podporovaný.
Inovujte na Microsoft Edge a využívajte najnovšie funkcie, aktualizácie zabezpečenia a technickú podporu.
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.
Microsoft supports the following environments for Azure IoT Operations deployments.
| Environment | Minimum version | Availability |
|---|---|---|
| K3s on Ubuntu 24.04 | K3s version 1.31.1 | General availability |
| Azure Kubernetes Service (AKS) Edge Essentials on Windows 11 IoT Enterprise | AksEdge-K3s-1.29.6-1.8.202.0 | Public preview |
| Azure Kubernetes Service (AKS) on Azure Local | Azure Stack HCI OS, version 23H2, build 2411 | Public preview |
Poznámka
Billing usage records are collected on any environment where Azure IoT Operations is installed, regardless of support or availability levels.
To install Azure IoT Operations, have the following hardware requirements available for Azure IoT Operations. If you're using a multi-node cluster that enables fault tolerance, scale up to the recommended capacity for better performance.
| Spec | Minimum | Recommended |
|---|---|---|
| Hardware memory capacity (RAM) | 16-GB | 32-GB |
| Available memory for Azure IoT Operations (RAM) | 10-GB | Depends on usage |
| CPU | 4 vCPUs | 8 vCPUs |
Azure IoT Operations offers two deployment modes. You can choose to deploy with test settings, a basic subset of features that are simpler to get started with for evaluation scenarios. Or, you can choose to deploy with secure settings, the full feature set.
A deployment with only test settings:
The quickstart scenario, Quickstart: Run Azure IoT Operations in GitHub Codespaces, uses test settings.
At any point, you can upgrade an Azure IoT Operations instance to use secure settings by following the steps in Enable secure settings.
A deployment with secure settings:
To deploy Azure IoT Operations with secure settings, follow these articles:
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.
| Task | Required permission | Comments |
|---|---|---|
| Deploy Azure IoT Operations | Contributor role at the resource group level. | |
| Register resource providers | Microsoft.ExtendedLocation/register/action Microsoft.SecretSyncController/register/action Microsoft.Kubernetes/register/action Microsoft.KubernetesConfiguration/register/action Microsoft.IoTOperations/register/action Microsoft.DeviceRegistry/register/action | Only required to do once per subscription. |
| Create a schema registry. | Microsoft.Authorization/roleAssignments/write permissions at the resource group level. | |
| Create secrets in Key Vault | Key Vault Secrets Officer role at the resource level. | Only required for secure settings deployment. |
| Enable resource sync rules on an Azure IoT Operations instance | Microsoft.Authorization/roleAssignments/write permissions at the resource group level. | Resource sync rules are disabled by default, but can be enabled as part of the az iot ops create command. |
If you use the Azure CLI to assign roles, use the az role assignment create command to give permissions. For example, az role assignment create --assignee sp_name --role "Role Based Access Control Administrator" --scope subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/MyResourceGroup
If you use the Azure portal to assign privileged admin roles to a user or principal, you're prompted to restrict access using conditions. For this scenario, select the Allow user to assign all roles condition in the Add role assignment page.
Azure IoT Operations supports Azure Arc sites for organizing instances. A site is a cluster resource in Azure like a resource group, but sites typically group instances by physical location and make it easier for OT users to locate and manage assets. An IT administrator creates sites and scopes them to a subscription or resource group. Then, any Azure IoT Operations deployed to an Arc-enabled cluster is automatically collected in the site associated with its subscription or resource group
For more information, see What is Azure Arc site manager (preview)?
If you use enterprise firewalls or proxies to manage outbound traffic, configure the following endpoints before deploying Azure IoT Operations.
Endpoints in the Azure Arc-enabled Kubernetes endpoints.
Poznámka
If you use Azure Arc Gateway to connect your cluster to Arc, you can configure a smaller set of endpoints based on the Arc Gateway guidance.
Endpoints in Azure CLI endpoints.
You need graph.windows.net, *.azurecr.io, *.blob.core.windows.net, *.vault.azure.net from this endpoint list.
The following endpoints are required specifically for Azure IoT Operations:
| Endpoints (DNS) | Description |
|---|---|
<customer-specific>.blob.storage.azure.net |
Storage for schema registry. Refer to storage account endpoints for identifying the customer specific subdomain of your endpoint. |
To push data to the cloud, enable the following endpoints based on your choice of data platform.
Prepare your Azure Arc-enabled Kubernetes cluster to configure and Arc-enable a cluster for Azure IoT Operations.
Školenie
Modul
Plan to deploy Microsoft Defender for IoT to monitor operational technology networks - Training
Learn how to plan your deployment of Microsoft Defender for IoT to monitor your OT network.
Certifikácia
Microsoft 365 Certified: Endpoint Administrator Associate - Certifications
Plan and execute an endpoint deployment strategy, using essential elements of modern management, co-management approaches, and Microsoft Intune integration.