Power Platform Community Forum Thread Details

Hi,
I am trying to create a SQL Server connection in Power Apps using an on-premises data gateway, but the gateway is not visible in my DEV environment.
Here is the situation:
The on-premises data gateway is installed and online.
The gateway status shows as Ready.
The gateway network/ports test has passed.
The gateway is visible in the company Power Apps environment.
I am the owner of the gateway.
I am using the same Microsoft account in both environments.
The company environment and DEV environment are both in the same region.
However, when I switch to the DEV environment and try to create a SQL Server connection, the gateway does not appear in the gateway dropdown.
I cannot share the gateway with myself because I am already the owner.
The SQL Server is an on-premises/internal SQL Server, so I need to use the gateway for the cloud flow.
Does anyone know why the gateway would be visible in one environment but not in another environment, even though both environments are in the same region and I am the gateway owner?
Could this be caused by a DLP policy, environment type, connector restriction, or another admin setting?
Any guidance would be appreciated.
Thanks

Categories:

Connector development

Hi KM-04061148-0,

Great that you have already ruled out the obvious checks! The key thing to understand here is that on-premises data gateways are scoped per environment in Power Platform.

Even though you are the gateway owner and it shows in the company environment, each Power Platform environment maintains its own list of available gateways. A gateway is only visible in an environment if it has been made available there.

Most likely causes:

1. Gateway not associated with the DEV environment - Gateways are managed per environment in the Power Platform admin center. The gateway being visible in the company environment does not automatically make it available in the DEV environment.

2. Environment type restriction - Developer environments have certain restrictions. Verify whether the gateway has been explicitly made available in the DEV environment.

3. DLP policies - A Data Loss Prevention policy applied to the DEV environment may block the SQL Server connector. Check Power Platform admin center > Data policies for the DEV environment.

Steps to resolve:

1. Go to Power Platform admin center > Data (preview) > On-premises data gateways

2. Find your gateway and open its Settings

3. Check the Environment field to see which environments the gateway is associated with

4. If the DEV environment is not listed, a Power Platform admin will need to make the gateway available in that environment

References:

- Manage an on-premises data gateway in Power Apps: https://learn.microsoft.com/en-us/power-apps/maker/canvas-apps/gateway-management

- On-premises data gateway management: https://learn.microsoft.com/en-us/power-platform/admin/onpremises-data-gateway-management

Found this helpful? Please mark "Does this answer your question?" so others searching for the same issue can find it quickly. A thumbs up on "Was this reply helpful?" or a Like is also much appreciated!

Raghav Mishra — LinkedIn | PowerAI Labs