Skip to content

Commit be23a2e

Browse files
author
ecfan
committed
Fix note formatting issues
1 parent a755968 commit be23a2e

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/logic-apps/logic-apps-securing-a-logic-app.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1471,7 +1471,7 @@ HTTP and HTTPS endpoints support various kinds of authentication. On some trigge
14711471

14721472
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.
14731473

1474-
[!IMPORTANT]
1474+
> [!IMPORTANT]
14751475
>
14761476
> For optimal security, Microsoft recommends using [Microsoft Entra ID](/entra/identity/authentication/overview-authentication)
14771477
> 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
15111511

15121512
[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).
15131513

1514-
[!IMPORTANT]
1514+
> [!IMPORTANT]
15151515
>
15161516
> For optimal security, Microsoft recommends using [Microsoft Entra ID](/entra/identity/authentication/overview-authentication)
15171517
> 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
15801580

15811581
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.
15821582

1583-
[!IMPORTANT]
1583+
> [!IMPORTANT]
15841584
>
15851585
> For optimal security, Microsoft recommends using [Microsoft Entra ID](/entra/identity/authentication/overview-authentication)
15861586
> 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
16361636

16371637
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.
16381638

1639-
[!IMPORTANT]
1639+
> [!IMPORTANT]
16401640
>
16411641
> For optimal security, Microsoft recommends using [Microsoft Entra ID](/entra/identity/authentication/overview-authentication)
16421642
> with [managed identities](/entra/identity/managed-identities-azure-resources/overview) for authentication when possible.

0 commit comments

Comments
 (0)