Connect to on-premises data sources from Azure Logic Apps
Before you can access data sources on premises from your logic apps, you need to create an Azure resource after you install the on-premises data gateway on a local computer. Your logic apps then use this Azure gateway resource in the triggers and actions provided by the on-premises connectors that are available for Azure Logic Apps.
To connect to Azure virtual networks, consider creating an integration service environment instead.
For information about how to use the gateway with other services, see these articles:
- Microsoft Power Automate on-premises data gateway
- Microsoft Power BI on-premises data gateway
- Microsoft Power Apps on-premises data gateway
- Azure Analysis Services on-premises data gateway
Supported data sources
In Azure Logic Apps, the on-premises data gateway supports the on-premises connectors for these data sources:
- BizTalk Server 2016
- File System
- IBM DB2
- IBM Informix
- IBM MQ
- Oracle Database
- SharePoint Server
- SQL Server
Azure Logic Apps supports read and write operations through the data gateway. However, these operations have limits on their payload size. Although the gateway itself doesn't incur additional costs, the Logic Apps pricing model applies to these connectors and other operations in Azure Logic Apps.
You're using the same Azure account and subscription that was used when installing that data gateway. This Azure account must belong to a single Azure Active Directory (Azure AD) tenant or directory.
Your gateway installation isn't already registered and claimed by another Azure gateway resource.
When you create a gateway resource in the Azure portal, you select a gateway installation, which links to your gateway resource and only that gateway resource. In Azure Logic Apps, on-premises triggers and actions then use the gateway resource for connecting to on-premises data sources. In these triggers and actions, you select your Azure subscription and the associated gateway resource that you want to use. Each gateway resource links to only one gateway installation, which links to only one Azure account.
Create Azure gateway resource
After you install the gateway on a local computer, create the Azure resource for your gateway.
Sign in to the Azure portal with the same Azure account that was used to install the gateway.
In the Azure portal search box, enter "on-premises data gateway", and select On-premises Data Gateways.
Under On-premises Data Gateways, select Add.
Under Create connection gateway, provide this information for your gateway resource. When you're done, select Create.
Property Description Resource Name Provide a name for your gateway resource that contains only letters, numbers, hyphens (
-), underscores (
_), parentheses (
)), or periods (
Subscription Select the Azure subscription for the Azure account that was used for the gateway installation. The default subscription is based on the Azure account that you used to sign in. Resource group The Azure resource group that you want to use Location The same region or location that was selected for the gateway cloud service during gateway installation. Otherwise, your gateway installation won't appear in the Installation Name list. Your logic app location can differ from your gateway resource location. Installation Name Select a gateway installation, which appears in the list only when these conditions are met:
- The gateway installation uses the same region as the gateway resource that you want to create.
- The gateway installation isn't linked to another Azure gateway resource.
- The gateway installation is linked to the same Azure account that you're using to create the gateway resource.
- Your Azure account belongs to a single Azure Active Directory (Azure AD) tenant or directory and is the same account that was used for the gateway installation.
For more information, see the Frequently asked questions section.
Here is an example that shows a gateway installation that's in the same region as your gateway resource and is linked to the same Azure account:
Connect to on-premises data
After you create your gateway resource and associate your Azure subscription with this resource, you can now create a connection between your logic app and your on-premises data source by using the gateway.
In the Azure portal, create or open your logic app in the Logic App Designer.
Add a connector that supports on-premises connections, for example, SQL Server.
Select Connect via on-premises data gateway.
Under Gateways, from the Subscriptions list, select your Azure subscription that has the gateway resource you want.
From the Connection Gateway list, which shows the available gateway resources in your selected subscription, select the gateway resource that you want. Each gateway resource is linked to a single gateway installation.
The gateways list includes gateway resources in other regions because your logic app's location can differ from your gateway resource's location.
Provide a unique connection name and other required information, which depends on the connection that you want to create.
A unique connection name helps you easily find that connection later, especially if you create multiple connections. If applicable, also include the qualified domain for your username.
Here is an example:
When you're done, select Create.
Your gateway connection is now ready for your logic app to use.
To update the settings for a gateway connection, you can edit your connection.
To find all the API connections for just your logic app, on your logic app's menu, under Development Tools, select API connections.
Select the gateway connection you want, and then select Edit API connection.
If your updates don't take effect, try stopping and restarting the gateway Windows service account for your gateway installation.
To find all API connections associated with your Azure subscription:
- From the Azure portal menu, select All services > Web > API Connections.
- Or, from the Azure portal menu, select All resources. Set the Type filter to API Connection.
Delete gateway resource
To create a different gateway resource, link your gateway installation to a different gateway resource, or remove the gateway resource, you can delete the gateway resource without affecting the gateway installation.
From the Azure portal menu, select All resources, or search for and select All resources from any page. Find and select your gateway resource.
If not already selected, on your gateway resource menu, select On-premises Data Gateway. On the gateway resource toolbar, select Delete.
Frequently asked questions
Q: Why doesn't my gateway installation appear when I create my gateway resource in Azure?
A: This issue can happen for these reasons:
Your Azure account must be the same account that's linked to the gateway installation on the local computer. Check that you're signed in to the Azure portal with the same identity that's linked to the gateway installation. Also, make sure that your Azure account belongs to a single Azure AD tenant or directory and is set to the same Azure AD tenant or directory that was used during gateway installation.
Your gateway resource and gateway installation have to use the same region. However, your logic app location can differ from your gateway resource location.
Your gateway installation is already registered and claimed by another gateway resource. These installations won't appear in the Installation Name list. To review your gateway registrations in the Azure portal, find all your Azure resources that have the On-premises Data Gateways type across all your Azure subscriptions. To unlink the gateway installation from the other gateway resource, see Delete gateway resource.
Q: Why did the location for my existing gateway change?
A: Gateway resources created before May 3, 2017 were moved to the original locations of the Azure AD tenant for the work or school account that created those gateways. However, these changes shouldn't affect currently running logic apps, which should continue working as usual. With the gateway's general availability in May, gateway resource locations can differ from logic app locations.