How the Gateway Works

Let’s look at what happens when you interact with an element that is connected to an on-premises data source:

1. The cloud service creates a query and the encrypted credentials for your on-premises Dynamics GP SQL Server. The query and credentials are sent to the gateway queue for processing.
2. The gateway cloud service analyzes the query and pushes the request to Azure Service Bus.
3. Azure Service Bus sends the pending requests to the gateway.
4. The gateway gets the query, decrypts the credentials, and connects to your Dynamics GP SQL Server with those credentials.
5. The gateway sends the query to your Dynamics GP SQL Server to be run.
6. The results are sent from your Dynamics GP SQL Server back to the gateway and then to Power Apps. Power Apps then hands over the results to Power Approvals to let it know that the request was completed.
   • Queries can return large amounts of data. For such queries, data is temporarily stored on the gateway machine.
   • Data storage continues until all data is received from your Dynamics GP SQL Server.
   • The data is then sent back to the cloud service, in a process is called spooling. We recommend you use a solid-state drive (SSD) as the spooling storage.