My Gateway is working however under data - Gateways it is showing no gateways installed.
Can somebody else please confirm as i cant add any connections to my on prem data as no gateways are listed.
Hey! I've been focusing on region setting in gateway. After reading over some comments here, went into Admin center & checked environment. The region for my environment was set to Europe. I set up trial environment & set region to UK (there isn't UK south) & my gateway now shows up.
Two options at this point:
1. Change region on existing environment.
2. Use new environment w/ region that matches Azure/PowerBI regions.
I'm presuming an update was done on the PowerApps side that resulted in different regions producing this outcome? Hard to say b/c my org was going through D365 updates (new CRM, FNO, etc.) around the same time.
im looking all over the place.. where can i change the current environment region? sooooo many admin centres and settings pages
dont think i can:
Once you click Admin Center from power apps, you access the power platform admin center. From here, you can access the environment. I have two listed, the old one had a type of 'Sandbox' & region of 'Europe.' I added a trial environment & set the region to 'United Kingdom.' I now can see my gateways when I select the new environment at the top-right of the main power apps screen.
The official reply from support links me to this
which is the reason why no one is able to see stuff.
Way more detail than https://powerapps.microsoft.com/en-us/blog/on-premises-data-gateway-management-by-region/ which would have helped PowerApps users.
But the point is, this is still an issue, Microsoft took a product that was working properly and broke it with an update.
For our instance, we have our gateway and production Power BI stuff in one region which we have been using for about 3 years now, and our PowerApps/Automate stuff in the default environment which has tons of apps and flows running production solutions.
moving the Power BI/Gateway region or creating a new environment isn't really a viable solution for us as it will require lots of downtime.
If anyone knows if there is a way to change the region of the default environment in PowerApps, please share. 😭
ah.. funny that’s just after it broke.
so my default environment is europe
my gateway was initially installed here and working since the release of PowerApps.
now the gateway software only shows my gateway under Uk South.
probably to do with brexit... however, they should have moved the environment region to uk south as well (according to the support doc you linked).
whatever happens it needs fixing, and fixing fast.
a refund on the service for the downtime as well should be processed since It cannot be used as intended.
Anyone on here is in the North America region? I am in the BC Canada region, which in the PowerApps environment setting is North America so I am not sure if changing my region to something else would help to work?
Has anyone made it work just by changing the region?
I have today received a response from Microsoft that i dont see as fit and is still unresolved.
Apologize for the inconvenience caused.
There is an update from the product team, now you will be able to see the gateway if you have created the gateway in the same region as in which the environment is created.
If you are in the Power Automate or Power Apps portal and are not able to see one (or many) of your gateways listed under the “Gateways” menu item or as an option to select in the dropdown when creating a connection, check to ensure the region where you installed the gateway matches the region of your Power Automate/Power Apps environment. We do not support cross-geo scenarios so if they do not match, you will not be able to view or use that gateway(s) in that environment. You will need to install a new gateway in the region that matches your Power Automate/Power Apps environment region.
For more details, refer to https://flow.microsoft.com/en-us/blog/supporting-on-premises-data-gateways-in-non-default-environmen...
I have since replied to this:
I’m sorry but this is not fixed.
The gateway and the environment were created when powerapps was launched and the regions were automatically set.
Whatever Microsoft has changed has broken this.
The environment is set to Europe (which cannot be changed) and the gateway is now set as UK south (this has never been changed), which cannot be moved due to the amount of apps and flows that depend on it.
This still is not resolved and needs fixing.
This new scenario which recently been introduced, Microsoft need to take care of migrating all of the dependent items to the same region with out any downtime. This is not possible at the client end.
Please resolve this with immediate effect.
I am able to see the Data Gateway in PowerApps through the Admin Center (not too sure if it has always been there). The same issue still exist, PowerBI is connected to the Gateway just fine (has not been a problem at all) but for PowerApps..
Under "Data" --> "Connections" --> "SQL Server" (Connect using on-premises data gateway) --> "Choose a gateway"
I still do not see my gateway in the drop down list.
Please keep it posted regarding to this frustrating issue! Thank you everyone in the community!
Another reply from Microsoft.
Thank you for sharing your concern.
I am so sorry for the inconvenience that caused.
Product update is based on users’ feedback to have on-premises data gateways to be supported in non-default environment, however it has been updated with the changes that caused inconvenience for users.
There are people who are having the same concern and I can completely understand how frustrated it must be.
It is a product update then it can be changed with another update of product, I can suggest that you raise the concern as a feedback to product group as it mentioned at the end of the article then it might be considered to improve users’ experience on using the product.
The last part is very concerning, I don't think this support person really understands their position. This whole time I have been contacting them with concern through PowerApps support, a part of their job is to raise this to the team.
I am worried that they don't care.