Connect on premise data to PowerApps/Flow/PowerBI using 'On-premises data gateway' - PART1

Featured image

Based on the repeated requests from customers for connecting on premise data like SharePoint lists or SQL rows to Office 365 applications (PowerApps, Microsoft Flow, Logic Apps, Power BI), Microsoft has introduced on-premises data gateway. The on-premises data gateway acts as a bridge in providing a quick and secure connection between on premise data and Office 365 apps. Currently supported on premise applications are SharePoint 2016 and SQL 2016 (Both Enterprise and Express editions). Moreover, you can use a single gateway to connect multiple on premise applications to multiple Office 365 applications at the same time and it is dependent on the account with which you sign in, which can be either your work or school, or personal Microsoft account.

This is a two-part blog series consisting of followings tasks,

  1. Deployment of On-premises data gateway
  2. Connect on premise data to Office 365 Application

In this blog, we will walk you through the steps involved in “On-premises data gateway” deployment.

Steps to be performed before installation

Hardware Requirements:

Hardware Requirements Value ———————– ——— CPU 8 Cores RAM 8 GB

Software Requirements:

Software Requirements Value ———————– ———————————————- .NET Framework Version - 4.5 Operating System Windows 7 / Windows Server 2008 R2, or later

Deployment of On-premises data gateway:

The deployment of on-premises data gateway is very simple, which includes gateway setup installation and gateway registration. Following are the steps involved in on-premises data gateway deployment,

Note: In each on premise machine, you can deploy only a single gateway.

NOTE: If you are trying to deploy the gateway in a domain controller, then you will receive the following error

Error

“Error generating an asymmetric key. The requested operation cannot be completed. The computer must be trusted for delegation and the current user account must be configured to allow delegation.”

Workaround:

Open Services console, select On-premises data gateway service change the service account .from NT SERVICE\PBIEgwService to Local System, as highlighted in the below screenshot and restart the service.

Proceed with gateway registration: Now click Configure again to proceed with gateway registration.

This concludes the PART1 (Deployment of On-premises data gateway) of our two-part blog series - Connect on premise data to Office 365 using “On-premises data gateway”. In the next part, we will walk you through the steps involved in connecting on premise data to Office 365 Applications using On-premises data gateway.