Skip to content

Commit 016481a

Browse files
authored
Add note about where to find the resource definition for the on-premises data gateway
1 parent 2fd8ab7 commit 016481a

File tree

1 file changed

+7
-3
lines changed

1 file changed

+7
-3
lines changed

articles/logic-apps/set-up-devops-deployment-single-tenant-azure-logic-apps.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: logic-apps
55
ms.suite: integration
66
ms.reviewer: estfan, azla
77
ms.topic: how-to
8-
ms.date: 01/04/2024
8+
ms.date: 06/12/2024
99

1010
# Customer intent: As a developer, I want to automate deployment for workflows hosted in single-tenant Azure Logic Apps by using DevOps tools and processes.
1111
---
@@ -76,7 +76,6 @@ To set up a build pipeline based on your logic app project type, complete the co
7676
|--------------|-----------------------|
7777
| Nuget-based | The NuGet-based project structure is based on the .NET Framework. To build these projects, make sure to follow the build steps for .NET Standard. For more information, review the documentation for [Create a NuGet package using MSBuild](/nuget/create-packages/creating-a-package-msbuild). |
7878
| Bundle-based | The extension bundle-based project isn't language-specific and doesn't require any language-specific build steps. You can use any method to zip your project files. <br><br>**Important**: Make sure that your .zip file contains the actual build artifacts, including all workflow folders, configuration files such as host.json, connections.json, and any other related files. |
79-
|||
8079

8180
### Before release to Azure
8281

@@ -160,7 +159,12 @@ To find the values that you need to use in the **properties** object for complet
160159

161160
`GET https://management.azure.com/subscriptions/{Azure-subscription-ID}/providers/Microsoft.Web/locations/{Azure-region-location}/managedApis/{connector-name}?api-version=2016-06-01`
162161

163-
In the response, find the **connectionParameters** object, which contains all the information necessary for you to complete resource definition for that specific connector. The following example shows an example resource definition for a SQL managed connection:
162+
> [!NOTE]
163+
>
164+
> If your connection uses an on-premises data gateway resource, this resource definition exists separately from the connector resource definition.
165+
> For more information, see [Microsoft.Web connectionGateways](/azure/templates/microsoft.web/connectiongateways?pivots=deployment-language-arm-template#connectiongatewayreference-1).
166+
167+
In the response, find the **connectionParameters** object, which contains the necessary information to complete the resource definition for that specific connector. The following example shows an example resource definition for a SQL managed connection:
164168

165169
```json
166170
{

0 commit comments

Comments
 (0)