IOT Hub - Subscription move to another tenant

Question

Hello,

I have a practical project to move Azure subscriptions to another Azure AD tenant but I can't find any documentation about IoT Hub support of such move.

I see this question was asked recently but the answer doesn't give me any good arguments why it is not recommended.
"Due to the fact, an IoT Hub has a public endpoint and specific credentials and specific routes to services, it seems complicated to move an IoT Hub to another tenant"
Others Azure services check the same boxes but can be moved. What makes IoT Hub not supported ?

source: https://learn.microsoft.com/en-us/answers/questions/328016/transfer-ownership-of-iothub-to-another-subscripti.html

Thank you,
Teddy

Answer 1

Hello @Ted This is a great question!.

Updated: 5/13/2021:

Move to a different Tenant\Directory[Transferring Ownership]:

Please refer to Transfer an Azure subscription to a different Azure AD directory

All resources in the subscription will move
Keep in mind changing tenant destroys all AAD RBAC assignments + managed identities.
All RBAC role assignments on the IoT hub will be lost, the managed identity will break, and correspondingly routing using managed identity will also break.

That said, Yes, the Referenced Thread in your initial question aligns with the underlying complexities. The referenced thread also gives a workaround solution to the complex situation.

If you need further help in this matter please make sure to contact Microsoft Support Team before you do the ownership transfer or you can also do it by yourself. If you need any help regarding this, then please comment in the below section.

With-In the same Tenant\Directory[Region to Region, Subscription to Subscription]

I hope you have already come across this article on How to clone an Azure IoT hub to another region, which I highly recommend you to go through & provide your feedback.

To clone a hub, you need a subscription with administrative access to the original hub. You can put the new hub in a new resource group and region, in the same subscription as the original hub, or even in a new subscription. You just can't use the same name because the hub name has to be globally unique.

The related post which you have mentioned: Is similar to the below article's step-by-step stages where we re-create the IoT Hub in target region\subscription and re-provision all devices with the help of Azure DPS.

We are happy to help you with additional queries if you have any, please comment in the below section for further in this matter.

If the response is helpful, please click "Accept Answer" and upvote it.