Microsoft Defender for IoT
Identity protectionProvision OT Sensors for Cloud Management
In brief
The article’s title, metadata, role-prerequisite wording, connectivity-team responsibilities, direct-connection context, and endpoint-download heading were revised.
What Defender admins need to know
Administrators should use the updated wording when following the procedure. No action is required.
Summaries are generated from the documentation change itself.
Documentation change
View on Microsoft LearnThe comparison below shows only the changed extract. Use the full-page view for complete context.
Provision sensors for cloud management
Prerequisites
To perform the steps described in this article, youYou need access to the Azure portal as awith one of these roles: Security Reader, Security Admin, Contributor, or Owner user..
DownloadingYour connectivity teams download endpoint details and configuringconfigure firewall rules is performed by your connectivity teams.rules.
Allow connectivity to Azure
This section describes how to download a list of required endpoints to define in firewall rules, ensuring that your OT sensors can connect to Azure.
This endpoint-download procedure is also used to configure direct connections to Azure. If you're planning to use a proxy configuration instead, you'll configure proxy settings after installing and activating your sensor.
For more information, see Methods for connecting sensors to Azure.
To download required endpoint details:details:
- On the Azure portal, go to Defender for IoT > Sites and sensors.
@@ -1,10 +1,10 @@ ----title: Provision OT sensors for cloud management+title: Provision OT Sensors for Cloud Management description: Learn how to ensure that your OT sensor can connect to Azure by accessing a list of required endpoints to define in your firewalls rules. ms.topic: how-to-ms.date: 06/12/2026+ms.date: 07/03/2026 ai-usage: ai-assisted-ms.custom: msecd-doc-authoring-1014+ms.custom: msecd-doc-authoring-1016 --- # Provision sensors for cloud management@@ -17,19 +17,19 @@ If you're working with air-gapped environment and locally-managed sensors, you c ## Prerequisites -To perform the steps described in this article, you need access to the Azure portal as a [Security Reader](/azure/role-based-access-control/built-in-roles#security-reader), [Security Admin](/azure/role-based-access-control/built-in-roles#security-admin), [Contributor](/azure/role-based-access-control/built-in-roles#contributor), or [Owner](/azure/role-based-access-control/built-in-roles#owner) user.+You need access to the Azure portal with one of these roles: [Security Reader](/azure/role-based-access-control/built-in-roles#security-reader), [Security Admin](/azure/role-based-access-control/built-in-roles#security-admin), [Contributor](/azure/role-based-access-control/built-in-roles#contributor), or [Owner](/azure/role-based-access-control/built-in-roles#owner). -Downloading endpoint details and configuring firewall rules is performed by your connectivity teams.+Your connectivity teams download endpoint details and configure firewall rules. ## Allow connectivity to Azure This section describes how to download a list of required endpoints to define in firewall rules, ensuring that your OT sensors can connect to Azure. -This procedure is also used to configure [direct connections](../architecture-connections.md#direct-connections) to Azure. If you're planning to use a proxy configuration instead, you'll [configure proxy settings](../connect-sensors.md) after installing and activating your sensor.+This endpoint-download procedure is also used to configure [direct connections](../architecture-connections.md#direct-connections) to Azure. If you're planning to use a proxy configuration instead, you'll [configure proxy settings](../connect-sensors.md) after installing and activating your sensor. For more information, see [Methods for connecting sensors to Azure](../architecture-connections.md). -**To download required endpoint details**:+To download required endpoint details: 1. On the Azure portal, go to Defender for IoT > **Sites and sensors**.