Merge pull request #313579 from v-thpra/tjp-fresh-azcontapps-004

Q&M Freshness - Azure Container Apps - TJP004

Author: prmerger-automator[bot]

articles/container-apps/authentication-twitter.md

@@ -5,7 +5,7 @@ services: container-apps
 author: craigshoemaker
 ms.service: azure-container-apps
 ms.topic: how-to
-ms.date: 11/18/2024
+ms.date: 03/23/2026
 ms.author: cshoe
 ---
 
@@ -15,7 +15,7 @@ This article shows how to configure Azure Container Apps to use X as an authenti
 
 To complete the procedure in this article, you need an X account that has a verified email address and phone number. To create a new X account, go to [x.com](https://x.com).
 
-## <a name="twitter-register"> </a>Register your application with X
+## Register your application with X
 
 1. Sign in to the [Azure portal] and go to your application. Copy your **URL**, later you use it to configure your X app.
 1. Go to the [X Developers] website, sign in with your X account credentials, and select **Create an app**.
@@ -24,23 +24,24 @@ To complete the procedure in this article, you need an X account that has a veri
 1. Select the **Keys and Access Tokens** tab.
 
    Make a note of these values:
+
    - API key
    - API secret key
 
    > [!IMPORTANT]
-   > The API secret key is an important security credential. Do not share this secret with anyone or distribute it with your app.
+   > The API secret key is an important security credential. Don't share this secret with anyone or distribute it with your app.
 
-## <a name="twitter-secrets"> </a>Add X information to your application
+## Add X information to your application
 
 1. Sign in to the [Azure portal] and navigate to your app.
 1. Select **Authentication** in the menu on the left. Select **Add identity provider**.
 1. Select **Twitter** in the identity provider dropdown. Paste in the `API key` and `API secret key` values that you obtained previously.
 
-    The secret is stored as [secret](manage-secrets.md) in your container app.
+   The secret is stored as [secret](manage-secrets.md) in your container app.
 
 1. If you're configuring the first identity provider for this application, you're prompted with a **Container Apps authentication settings** section. Otherwise, you move on to the next step.
 
-    These options determine how your application responds to unauthenticated requests. The default selections redirect all requests to sign in with this new provider. You can change customize this behavior now or adjust these settings later from the main **Authentication** screen by choosing **Edit** next to **Authentication settings**. To learn more about these options, see [Authentication flow](authentication.md#authentication-flow).
+   These options determine how your application responds to unauthenticated requests. The default selections redirect all requests to sign in with this new provider. You can change customize this behavior now or adjust these settings later from the main **Authentication** screen by choosing **Edit** next to **Authentication settings**. To learn more about these options, see [Authentication flow](authentication.md#authentication-flow).
 
 1. Select **Add**.
 
@@ -50,8 +51,8 @@ You're now ready to use X for authentication in your app. The provider is listed
 
 Use the following guides for details on working with authenticated users.
 
-* [Customize sign-in and sign-out](authentication.md#customize-sign-in-and-sign-out)
-* [Access user claims in application code](authentication.md#access-user-claims-in-application-code)
+- [Customize sign-in and sign out](authentication.md#customize-sign-in-and-sign-out)
+- [Access user claims in application code](authentication.md#access-user-claims-in-application-code)
 
 ## Next steps