On-premise data gateway
There are many situations where you will use the on-premise data from different sources to be presented or modified or added from cloud applications like PowerApp, Power BI or Power Automate. On-premise data could be on SQL instance etc. At present there is no direct possible way to transfer the on-premise data to could directly and securely.
On-premise data gateway allow safe data transfer between on-premise data source locations to cloud services/applications like PowerApp, Power BI or Power Automate. Idea behind using the on-premise gate way to keep the on-premise data on organization network and use online
On-premise data sources could be SQL server, SQL server analysis services, files or SharePoint and other data sources. Similarly Could applications which can use on-premise data could be PowerApp, Power BI, Power Automate, Azure Logic App and analysis services.
Installing and configuring On-premise data gateway
You can click here and visit Microsoft location to get related information like minimum requirement, where to download & how to configure the on-premise data gateway. I will try to cover few topics before planning the on-premise data gateway for your organization.
A) On-premise data gateway naming convention or usage:
You can install on-premise data gateway on your local computer or virtual / dedicated server having consistent network connectivity. You can use same data gateway connecting many data sources. It is good to have generic name used across your organization instead of using gateway name specific to any data source or group if people or team.
B) On-premise data gateway governance:
You can manage permission to gateway as Admin, Can use & Can use and Share. With Can use permission - one can only be able to use the gateway, Can use and share permission - use the gateway as well as share among other team members and Admin can delete gateway and provide access to other team members.
C) Rename or Delete On-premise data gateway:
You can delete the gateway by visiting the Data section in PowerApp online provided you have Admin permission. In addition, We do not see the direct options to rename the on-premise data gateway but deleting the on-premise data gateway and then recreating new one could be one option. If on-premise data gateway has used in many places and you have production usage, it is not advisable to follow this step. Below steps can be considered:
- Take snapshot of permissions provided to users with current gateway. You will have to grant same level of permissions to users with newly created on-premise data gateway
- Take another snapshot of connections where you have used this on-premise data gateway. You can visit PowerApp > Data section > Gateways > select current gateway > go to details > connection section
- Optional step: You can send communication to your users about decommission of current gateway
- Delete on-premise data gateway
- Create new on-premise data gateway using correct naming convention and provide same level of permission to users as per step 1.
- Visit all connections as per step 3 and update the connect with new on-premise data gateway & save it.
- That is it. It take little while to reflect the changes. In my case, it tool 15 to 20 minutes.
D) New version of gateway:
Microsoft will be providing upgrades to on-premise data gateway. You can visit here to see how to upgrade the gateway.