Skip to content

Commit 50e4aa8

Browse files
committed
Add IMDS note
1 parent ead28ab commit 50e4aa8

4 files changed

Lines changed: 18 additions & 0 deletions

File tree

articles/iot-operations/deploy-iot-ops/concept-production-guidelines.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -45,6 +45,8 @@ Consider the following measures to ensure your cluster setup is secure before de
4545
* Use [user-assigned managed identities](./howto-enable-secure-settings.md#set-up-a-user-assigned-managed-identity-for-cloud-connections) for cloud connections.
4646
* Keep your cluster and Azure IoT Operations deployment up to date with the latest patches and minor releases to get all available security and bug fixes.
4747

48+
[!INCLUDE [aks-imds-restriction](../includes/aks-imds-restriction.md)]
49+
4850
### Networking
4951

5052
If you use enterprise firewalls or proxies, add the [Azure IoT Operations endpoints](./overview-deploy.md#azure-iot-operations-endpoints) to your allow list.

articles/iot-operations/deploy-iot-ops/howto-enable-secure-settings.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -201,3 +201,7 @@ Some Azure IoT Operations components, like data flow endpoints, use a user-assig
201201
```
202202

203203
Now you can use this managed identity in data flow endpoints for cloud connections.
204+
205+
## Block pod access to the Azure Instance Metadata Service
206+
207+
[!INCLUDE [aks-imds-restriction](../includes/aks-imds-restriction.md)]

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

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -65,6 +65,8 @@ To deploy Azure IoT Operations with secure settings, follow these articles:
6565
1. Start with [Prepare your Azure Arc-enabled Kubernetes cluster](./howto-prepare-cluster.md) to configure and Arc-enable your cluster.
6666
1. Then, follow the steps in [Deploy Azure IoT Operations to a production cluster](./howto-deploy-iot-operations.md).
6767

68+
[!INCLUDE [aks-imds-restriction](../includes/aks-imds-restriction.md)]
69+
6870
## Required permissions
6971

7072
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).
Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
---
2+
ms.topic: include
3+
ms.custom: include file
4+
author: dominicbetts
5+
ms.topic: include
6+
ms.date: 01/06/2026
7+
ms.author: dobett
8+
---
9+
10+
When you deploy Azure IoT Operations with secure settings on AKS, Microsoft recommends blocking pod access to the Azure Instance Metadata Service endpoint. To learn how to enable this feature, see [Block pod access to the Azure Instance Metadata Service (IMDS) endpoint](/azure/aks/imds-restriction).

0 commit comments

Comments
 (0)