You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/logic-apps/logic-apps-securing-a-logic-app.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1471,7 +1471,7 @@ HTTP and HTTPS endpoints support various kinds of authentication. On some trigge
1471
1471
1472
1472
For HTTP calls, basic authentication uses a base64-encoded string that contains a username and password to make a request. This method transmits credentials without encryption and poses increased security risks unless you use this option with the HTTPS/SSL protocol.
1473
1473
1474
-
[!IMPORTANT]
1474
+
> [!IMPORTANT]
1475
1475
>
1476
1476
> For optimal security, Microsoft recommends using [Microsoft Entra ID](/entra/identity/authentication/overview-authentication)
1477
1477
> with [managed identities](/entra/identity/managed-identities-azure-resources/overview) for authentication when possible.
@@ -1511,7 +1511,7 @@ When you use [secured parameters](#secure-action-parameters) to handle and secur
1511
1511
1512
1512
[Client certificate authentication](/entra/identity/authentication/concept-certificate-based-authentication) allows or requires users to authenticate directly with X.509 certificates against their Microsoft Entra ID for applications and browser sign-in. This capability helps you adopt a phishing resistant authentication and authenticate with an X.509 certificate against your Public Key Infrastructure (PKI).
1513
1513
1514
-
[!IMPORTANT]
1514
+
> [!IMPORTANT]
1515
1515
>
1516
1516
> For optimal security, Microsoft recommends using [Microsoft Entra ID](/entra/identity/authentication/overview-authentication)
1517
1517
> with [managed identities](/entra/identity/managed-identities-azure-resources/overview) for authentication when possible.
@@ -1580,7 +1580,7 @@ For more information about securing services by using client certificate authent
1580
1580
1581
1581
On the **Request** trigger, you can use the [Microsoft Entra platform](/entra/fundamentals/what-is-entra) to authenticate incoming calls after you [set up Microsoft Entra authorization policies](#enable-oauth) for your logic app.
1582
1582
1583
-
[!IMPORTANT]
1583
+
> [!IMPORTANT]
1584
1584
>
1585
1585
> For optimal security, Microsoft recommends using [Microsoft Entra ID](/entra/identity/authentication/overview-authentication)
1586
1586
> with [managed identities](/entra/identity/managed-identities-azure-resources/overview) for authentication when possible.
@@ -1636,7 +1636,7 @@ When you use [secured parameters](#secure-action-parameters) to handle and secur
1636
1636
1637
1637
If the **Raw** option is available, you can use this authentication type when you have to use [authentication schemes](https://iana.org/assignments/http-authschemes/http-authschemes.xhtml) that don't follow the [OAuth 2.0 protocol](https://oauth.net/2/). With this type, you manually create the authorization header value that you send with the outgoing request, and specify that header value in your trigger or action.
1638
1638
1639
-
[!IMPORTANT]
1639
+
> [!IMPORTANT]
1640
1640
>
1641
1641
> For optimal security, Microsoft recommends using [Microsoft Entra ID](/entra/identity/authentication/overview-authentication)
1642
1642
> with [managed identities](/entra/identity/managed-identities-azure-resources/overview) for authentication when possible.
0 commit comments