Skip to content

Commit 0e29163

Browse files
xuehonggecfan
andauthored
Update articles/logic-apps/single-tenant-overview-compare.md
Co-authored-by: Esther Fan <[email protected]>
1 parent 00587d5 commit 0e29163

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

articles/logic-apps/single-tenant-overview-compare.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -253,6 +253,7 @@ For example, a Standard workflow has both managed connectors and built-in connec
253253
In single-tenant Azure Logic Apps, [built-in connectors with specific attributes are informally known as *service providers*](../connectors/built-in.md#service-provider-interface-implementation). Some built-in connectors support only a single way to authenticate a connection to the underlying service. Other built-in connectors can offer a choice, such as using a connection string, Microsoft Entra ID, or a managed identity. All built-in connectors run in the same process as the redesigned Azure Logic Apps runtime. For more information, review the [built-in connector list for Standard logic app workflows](../connectors/built-in.md#built-in-connectors).
254254

255255
> [!IMPORTANT]
256+
>
256257
> Make sure to configure any service provider trigger correctly and test it thoroughly to confirm it is working. A failed
257258
> service provider trigger may cause additional unnecessary scaling which may dramatically increase your billing cost. A common
258259
> mistake is setting a trigger without providing the logic app permission to the destination such as service bus queue or Azure

0 commit comments

Comments
 (0)