Using R script and working with multiple developers

[jaryszek]

Hi Guys,

I am using R script and managed to set up the connection for it within personal gateway for specific power bi user.

I logged in second laptop to power bi and i could't use the gateway because my first laptop where i cnfigured R source was turned off, which is obvious behaviour.

After running first laptop with gateway set up I have logged in to the same power bi user account and managed to refresh connection.

If this will work per 1 logged user? 
If i would have more users can i use the same personal gateway to laptop where my R code is set up? 

I know that enterprise gateway will not work with python or R scripts...
Best,
Jacek

[Poojara_D12]

Hi @jaryszek 

You're using a personal gateway to enable Power BI to refresh datasets that rely on R scripts, and you've correctly observed that the gateway must be running on the specific machine where the R environment is configured. When you logged in to Power BI from a second laptop, you couldn't use the gateway because the first laptop—where the personal gateway and R setup exist—was turned off. This behavior is expected because a personal gateway is bound to the specific user profile and machine where it's installed, meaning the R script and its dependencies (libraries, paths, etc.) are tied to that local environment.

Regarding your question on whether the gateway works "per logged-in user"—yes, the personal gateway works only under the context of the specific Power BI user who installed and configured it. However, it's also bound to that user's machine. So even if you log into the same Power BI user account from another device, the R-based refresh won't work unless it's routed through the original machine with the gateway and R environment active.

As for sharing the same personal gateway across multiple users—this is not possible. A personal gateway is single-user, single-machine. It cannot be used by other users or shared across machines. If you have multiple users who need to run R scripts in Power BI, each would need to set up their own R environment and install a personal gateway on their respective machines.

And you're right—the Power BI enterprise (standard) gateway does not support R or Python scripts for scheduled refreshes due to security and sandboxing constraints. So, for scenarios requiring script-based transformations, personal gateway is the only option, but it's inherently limited to the user's local environment. For broader usage across teams, consider moving R logic upstream (e.g., into a dataflow, stored procedure, or external ETL process) and use supported data sources in Power BI.

[v-sgandrathi]

Hi @jaryszek,

Thank you for your question regarding the use of R scripts with Power BI and managing Personal Gateway access for multiple users and machines.

To clarify, the Power BI Personal Gateway is linked to both the specific machine and the user account it was set up with. It operates only when the original machine is on and the configured user is signed in. Logging into the same Power BI account from a different device will not make the gateway available unless the initial machine is running and the gateway service is active.

Add on, sharing access to the dataset or workspace does not provide access to the Personal Gateway. Other users, even with report or workspace access, cannot use the gateway for scheduled refreshes. This limitation makes the Personal Gateway unsuitable for collaborative or team-based development involving R or Python.

As the Enterprise Gateway currently does not support R or Python, alternative solutions are advisable for team environments. One option is to deploy the Personal Gateway and R environment on a dedicated, always-on machine or server, managing all publications and refreshes through a single Power BI user account. However, this approach may not scale effectively for larger teams.

For improved collaboration and maintainability, consider running your R or Python scripts externally and saving the results to a file or database, which Power BI can then access. This setup enables the use of the Enterprise Gateway for refreshes and supports a more robust and collaborative workflow.

While Power BI Dataflows do not natively support R or Python, preprocessing data externally and feeding it into a dataflow can help centralize and share clean data among multiple developers and reports, enhancing reusability and version control.

You may refer to the official Microsoft Fabric documentation links for further information:
Use a personal gateway in Power BI - Power BI | Microsoft Learn
On-premises data gateway FAQ - Power BI | Microsoft Learn

If this solution worked for you, kindly mark it as Accept as Solution and feel free to give a Kudos, it would be much appreciated!

Thank you.

[v-sgandrathi]

Hi @jaryszek,

Thank you! We’re glad to have you in the Microsoft Fabric Community and feel free to drop by anytime you need help or want to share ideas.

Thank you.

[lbendlin]

Technically you can give other users access to your Personal Gateway.  But that only makes the problem worse, in my opinion.

What is the value-add of the R scripts?

[jaryszek]

Technically you can give other users access to your Personal Gateway.

How? 

[jaryszek]

Using environment windows variable. Not having to change parameter every time while opening report.