Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!To celebrate FabCon Vienna, we are offering 50% off select exams. Ends October 3rd. Request your discount now.
Hi, I have a case where we are moving tenant under which we operate in Power BI because of company merger.
Previously we were part of PBI tenant 'X' and now we are moving to tenant 'Y'
For 'X' there were a couple of on-premises data gateways configured, and the sources which are accessed through them will still be relevant for 'Y'.
Since it would be nice to avoid setup of a completely new on-prem data gateway, I was wondering, if there is a way to keep using the same installed gateway, but have it be available and show up under tenant 'Y'?
Is this related to the user through which the gateway originally gets configured and part of which tenant that user is?
Or is the gateway's relation to a specific tenant defined when downloading the gateway installation application file?
Regards,
Aivars
Solved! Go to Solution.
Is this related to the user through which the gateway originally gets configured and part of which tenant that user is?
Or is the gateway's relation to a specific tenant defined when downloading the gateway installation application file?
The former. A gateway cannot server two separate tenants. It is always confined to the tenant /AD/Entra ID of the configuring user. Pretty weird as that user has no more meaning after the gateway meta data is created in the Power BI service.
The individual gateway cluster VMs play no role in this. They are mindless zombies and are fully dependent on receiving jobs from the gateway service in Azure.
Hi @Rigensis ,
You can open a ticket with Microsoft support they might be having better option .You can't use a same gateway under two different tenant accounts.
Thanks,
Sai Teja
Is this related to the user through which the gateway originally gets configured and part of which tenant that user is?
Or is the gateway's relation to a specific tenant defined when downloading the gateway installation application file?
The former. A gateway cannot server two separate tenants. It is always confined to the tenant /AD/Entra ID of the configuring user. Pretty weird as that user has no more meaning after the gateway meta data is created in the Power BI service.
The individual gateway cluster VMs play no role in this. They are mindless zombies and are fully dependent on receiving jobs from the gateway service in Azure.