Skip to content

Commit 4311552

Browse files
authored
Merge pull request #192326 from nimengan/patch-2
Document limitation of User Assigned Identity on Iot Hub
2 parents 4fb3f29 + d39a0b9 commit 4311552

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/iot-hub/iot-hub-managed-identity.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -226,7 +226,7 @@ az resource show --resource-type Microsoft.Devices/IotHubs --name <iot-hub-resou
226226
Managed identities can be used for egress connectivity from IoT Hub to other Azure services for [message routing](iot-hub-devguide-messages-d2c.md), [file upload](iot-hub-devguide-file-upload.md), and [bulk device import/export](iot-hub-bulk-identity-mgmt.md). You can choose which managed identity to use for each IoT Hub egress connectivity to customer-owned endpoints including storage accounts, event hubs, and service bus endpoints.
227227

228228
> [!NOTE]
229-
> Use a system-assigned managed identity to access private resources.
229+
> Only system-assigned managed identity gives IoT Hub access to private resources. If you want to use user-assigned managed identity, then the public access on those private resources needs to be enabled in order to allow connectivity.
230230
231231
## Configure message routing with managed identities
232232

0 commit comments

Comments
 (0)