Forum Discussion
Same gateway multiple tenants
Hi Gabry ,
Only one gateway can be installed on a machine. You can create another gateway in a virtual machine. My suggestion is that you just create a gateway for tenant A and then invite tenant B's users as guest users and share tenant A's gateway to tenant B's users.
Distribute content to external guest users with Microsoft Entra B2B - Power BI | Microsoft Learn
View and manage on-premises data gateways (preview) - Power Platform | Microsoft Learn
Solved: Sharing enterprise gateway or on premises gateway - Microsoft Fabric Community
Best Regards,
Neeko Tang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Connecting an on-premises server to multiple tenants in a scenario like this can be challenging due to the limitations of some integration services and the nature of tenant-based architectures. Here's a general approach you can take to achieve this:
Multiple Gateways: Since you've mentioned that registering a new gateway seems to disable the old one, it's possible that the gateway registration process is designed to work with only one gateway per environment or tenant. In this case, you may need to set up multiple instances of the gateway software, each registered with a different tenant.
Separate Installations: Install and configure separate instances of the gateway software for each tenant. This means you'll have two separate gateway installations, each registered with a different tenant.
Isolation: Ensure that the installations are isolated from each other to avoid conflicts. This could involve using different installation directories, different service accounts, and potentially different physical or virtual machines.
Configuration: When setting up each gateway instance, ensure that you configure it to connect to the appropriate tenant's resources. This may involve specifying different connection details, authentication methods, or other settings specific to each tenant.
Testing: After setting up both gateway instances, thoroughly test connectivity from each tenant's environment to the on-premises server. This will help ensure that each tenant can access the resources they need without interference from the other.
Monitoring and Maintenance: Once everything is set up and working correctly, establish procedures for monitoring and maintaining the gateway instances. This may include monitoring for errors or connectivity issues, applying updates or patches, and performing regular backups.
Vendor Support: If you're using a specific integration or cloud service provider for the gateway software, consider reaching out to their support team for guidance or assistance. They may have additional recommendations or best practices for setting up multiple gateways in this manner.
Did I answer your question? Mark my post as a solution! Appreciate your Kudos !!
Thank you for the assistance, but unfortunately, this doesn't address my issue adequately. It seems like information I could have obtained from ChatGPT.
Could you clarify what "vendor support" entails? Will Microsoft provide assistance in this matter?
I've installed the standard gateway for PowerBI.
Managing different virtual machines isn't feasible for me. I only have one SQL server, and I aim to connect to this SQL server from multiple PowerBI tenants. Is there no straightforward solution to accomplish this?
Simply duplicating the entire database isn't viable as a solution.
What steps should I take to connect to the same SQL server from multiple tenants?