Gateway in non default environments

[Ortwin]

In a non default environment we couldn' use a Gateway to connect to on-premise resources.

It should be posible to reuse/share an existing gateway in non default envrionments to create a connection to an external database (ex. SQL Server on-premise).

[linhtran]

Hi, you still need to raise a ticket to make a gateway available in other environments. 

[Steveo1]

@linhtran, When will this be available without raising a ticket? 

---

---

[thomasgarcia83]

Hi @linhtran ,

Can we still request a whitelist. We very much need this feature as we are trying to move all of our apps out of the default environment.

thanks,

-Tom

[cclenne]

This is really becoming a necessity. We have separate departments, and all have their own Power Platform DEV/ACC/PROD Environment. But because of the current “Only Default Environment” limitation they cannot follow through the ALM procedure as stated by the company…. Now every department has to list their environments to be whitelisted by Microsoft Support… Really frustrating!

[RyderMC]

I really need this for development and test purposes

[mkujalowicz]

Hi 

is there any update on this implementation? It is really important to the App Makers, since it's really hard to test the apps across environments. 

Thank you

[beniwal]

HI @linhtran ,

I have a question!

Can we create a new environment using powerapp plan 1 ? 

If yes, then please tell me if we will be able to connect on-premise SQL server with that newly created environment. (By creating the Support ticket or however)

Thanks,

Mohit

[ZiaUddin]

Hi All

Apologies - I am a late joiner.  I struggled with this issue but have found away, I am guessing what we all want is a connection of some sort to our flow or whatever - the connection being a SQL on Prem ? - if so then I found that you can do it for a non-default environment by doing the following ( I assume you have already installed the on-prem gateway):

1) Go to the Data Integrations area

2) Create a connection to SQL Server or whichever on prem database - when you do this in a non-default environment you should be able make use of an on-prem gateway in the connection setting.

3) Continue with the wizard till the end and select the 'Do Nothing' option at the end of the wizard.

After doing the above identify the data integration project that is created by doing the above and just rename it to something else that you can identify.

Now when you go to your flow and add a SQL action of any kind you should see listed the connection you created above.  This should work from a non-default environment.

Please let me know if this works for you.

[aprilhazel]

This is critical. I was excited recently to find out about the dev environment now I realize it is not really an option I am very frustrated.

[Jraney]

When is this going to be done?  Really long overdue.... Maybe time to go to AWS....