Merge pull request #284147 from MicrosoftDocs/main

8/9 11:00 AM IST Publish

Author: PhilKang0704

articles/active-directory-b2c/identity-provider-twitter.md

@@ -1,7 +1,7 @@
 ---
-title: Set up sign-up and sign-in with a Twitter account
+title: Set up sign-up and sign-in with an X account
 titleSuffix: Azure AD B2C
-description: Provide sign-up and sign-in to customers with Twitter accounts in your applications using Azure Active Directory B2C.
+description: Provide sign-up and sign-in to customers with X accounts in your applications using Azure Active Directory B2C.
 author: garrodonnell
 manager: CelesteDG
 ms.service: active-directory
@@ -11,11 +11,11 @@ ms.author: godonnell
 ms.subservice: B2C
 zone_pivot_groups: b2c-policy-type
 
-#Customer Intent: As a developer setting up sign-up and sign-in with a Twitter account using Azure Active Directory B2C, I want to configure Twitter as an identity provider so that I can enable users to sign in with their Twitter accounts.
+#Customer Intent: As a developer setting up sign-up and sign-in with an X account using Azure Active Directory B2C, I want to configure X as an identity provider so that I can enable users to sign in with their X accounts.
 
 ---
 
-# Set up sign-up and sign-in with a Twitter account using Azure Active Directory B2C
+# Set up sign-up and sign-in with an X account using Azure Active Directory B2C
 
 [!INCLUDE [active-directory-b2c-choose-user-flow-or-custom-policy](../../includes/active-directory-b2c-choose-user-flow-or-custom-policy.md)]
 ::: zone pivot="b2c-custom-policy"
@@ -30,10 +30,10 @@ zone_pivot_groups: b2c-policy-type
 
 ## Create an application
 
-To enable sign-in for users with a Twitter account in Azure AD B2C, you need to create a Twitter application. If you don't already have a Twitter account, you can sign up at [`https://twitter.com/signup`](https://twitter.com/signup). You also need to [Apply for a developer account](https://developer.twitter.com/). For more information, see [Apply for access](https://developer.twitter.com/en/apply-for-access).
+To enable sign-in for users with an X account in Azure AD B2C, you need to create an X application. If you don't already have an X account, you can sign up at [`https://x.com/signup`](https://x.com/signup). You also need to [Apply for a developer account](https://developer.x.com/). For more information, see [Apply for access](https://developer.x.com/en/apply-for-access).
 
 ::: zone pivot="b2c-custom-policy"
-1. Sign in to the [Twitter Developer Portal](https://developer.twitter.com/portal/projects-and-apps) with your Twitter account credentials.
+1. Sign in to the [X Developer Portal](https://developer.x.com/portal/projects-and-apps) with your X account credentials.
 1. Select **+ Create Project** button. 
 1. Under **Project name** tab, enter a preferred name of your project, and then select **Next** button.
 1. Under **Use case** tab, select your preferred use case, and then select **Next**. 
@@ -47,7 +47,7 @@ To enable sign-in for users with a Twitter account in Azure AD B2C, you need to
     1. For the **Callback URI/Redirect URL**, enter `https://your-tenant-name.b2clogin.com/your-tenant-name.onmicrosoft.com/your-policy-id/oauth1/authresp`. If you use a [custom domain](custom-domain.md), enter `https://your-domain-name/your-tenant-name.onmicrosoft.com/your-user-flow-Id/oauth1/authresp`. Use all lowercase letters when entering your tenant name and user flow ID even if they are defined with uppercase letters in Azure AD B2C. Replace:
         - `your-tenant-name` with the name of your tenant name.
         - `your-domain-name` with your custom domain.
-        - `your-policy-id` with the identifier of your user flow. For example, `b2c_1a_signup_signin_twitter`.  
+        - `your-policy-id` with the identifier of your user flow. For example, `b2c_1a_signup_signin_x`.  
     1. For the **Website URL**, enter `https://your-tenant.b2clogin.com`. Replace `your-tenant` with the name of your tenant. For example, `https://contosob2c.b2clogin.com`. If you use a [custom domain](custom-domain.md), enter `https://your-domain-name`.
     1. (Optional) Enter a URL for the **Terms of service**, for example `http://www.contoso.com/tos`. The policy URL is a page you maintain to provide terms and conditions for your application.
     1. (Optional) Enter a URL for the **Privacy policy**, for example `http://www.contoso.com/privacy`. The policy URL is a page you maintain to provide privacy information for your application.
@@ -57,21 +57,21 @@ To enable sign-in for users with a Twitter account in Azure AD B2C, you need to
 
 ::: zone pivot="b2c-user-flow"
 
-1. Sign in to the [Twitter Developer Portal](https://developer.twitter.com/portal/projects-and-apps) with your Twitter account credentials.
+1. Sign in to the [X Developer Portal](https://developer.x.com/portal/projects-and-apps) with your X account credentials.
 1. Select **+ Create Project** button. 
 1. Under **Project name** tab, enter a preferred name of your project, and then select **Next** button.
 1. Under **Use case** tab, select your preferred use case, and then select **Next**. 
 1. Under **Project description** tab, enter your project description, and then select **Next** button. 
 1. Under **App name** tab, enter a name for your app, such as *azureadb2c*, and the select **Next** button.
-1. Under **Keys & Tokens** tab, copy the value of **API Key** and **API Key Secret** for later. You use both of them to configure Twitter as an identity provider in your Azure AD B2C tenant. 
+1. Under **Keys & Tokens** tab, copy the value of **API Key** and **API Key Secret** for later. You use both of them to configure X as an identity provider in your Azure AD B2C tenant. 
 1. Select **App settings** to open the app settings. 
 1. At the lower part of the page, under **User authentication settings**, select **Set up**.
 1. Under **Type of app**, select your appropriate app type such as *Web App*. 
 1. Under **App Info**:
     1. For the **Callback URI/Redirect URL**, enter `https://your-tenant.b2clogin.com/your-tenant-name.onmicrosoft.com/your-user-flow-name/oauth1/authresp`. If you use a [custom domain](custom-domain.md), enter `https://your-domain-name/your-tenant-name.onmicrosoft.com/your-user-flow-Id/oauth1/authresp`. Use all lowercase letters when entering your tenant name and user flow ID even if they are defined with uppercase letters in Azure AD B2C. Replace:
         - `your-tenant-name` with the name of your tenant name.
         - `your-domain-name` with your custom domain.
-        - `your-user-flow-name` with the identifier of your user flow. For example, `b2c_1_signup_signin_twitter`. 
+        - `your-user-flow-name` with the identifier of your user flow. For example, `b2c_1_signup_signin_x`. 
     1. For the **Website URL**, enter `https://your-tenant.b2clogin.com`. Replace `your-tenant` with the name of your tenant. For example, `https://contosob2c.b2clogin.com`. If you use a [custom domain](custom-domain.md), enter `https://your-domain-name`.
     1. Enter a URL for the **Terms of service**, for example `http://www.contoso.com/tos`. The policy URL is a page you maintain to provide terms and conditions for your application.
     1. Enter a URL for the **Privacy policy**, for example `http://www.contoso.com/privacy`. The policy URL is a page you maintain to provide privacy information for your application.
@@ -81,23 +81,23 @@ To enable sign-in for users with a Twitter account in Azure AD B2C, you need to
 
 ::: zone pivot="b2c-user-flow"
 
-## Configure Twitter as an identity provider
+## Configure X as an identity provider
 
 1. Sign in to the [Azure portal](https://portal.azure.com/) as the global administrator of your Azure AD B2C tenant.
 1. If you have access to multiple tenants, select the **Settings** icon in the top menu to switch to your Azure AD B2C tenant from the **Directories + subscriptions** menu.
 1. Choose **All services** in the top-left corner of the Azure portal, search for and select **Azure AD B2C**.
 1. Select **Identity providers**, then select **Twitter**.
-1. Enter a **Name**. For example, *Twitter*.
-1. For the **Client ID**, enter the *API Key* of the Twitter application that you created earlier.
+1. Enter a **Name**. For example, *X*.
+1. For the **Client ID**, enter the *API Key* of the X application that you created earlier.
 1. For the **Client secret**, enter the *API key secret* that you recorded.
 1. Select **Save**.
 
-## Add Twitter identity provider to a user flow 
+## Add X identity provider to a user flow 
 
-At this point, the Twitter identity provider has been set up, but it's not yet available in any of the sign-in pages. To add the Twitter identity provider to a user flow:
+At this point, the X identity provider has been set up, but it's not yet available in any of the sign-in pages. To add the X identity provider to a user flow:
 
 1. In your Azure AD B2C tenant, select **User flows**.
-1. Select the user flow that you want to add the Twitter identity provider.
+1. Select the user flow that you want to add the X identity provider.
 1. Under the **Social identity providers**, select **Twitter**.
 1. Select **Save**.
 
@@ -106,44 +106,44 @@ At this point, the Twitter identity provider has been set up, but it's not yet a
 1. To test your policy, select **Run user flow**.
 1. For **Application**, select the web application named *testapp1* that you previously registered. The **Reply URL** should show `https://jwt.ms`.
 1. Select the **Run user flow** button.
-1. From the sign-up or sign-in page, select **Twitter** to sign in with Twitter account.
+1. From the sign-up or sign-in page, select **Twitter** to sign in with X account.
 
 ::: zone-end
 
 ::: zone pivot="b2c-custom-policy"
 
 ## Create a policy key
 
-You need to store the secret key that you previously recorded for Twitter app in your Azure AD B2C tenant.
+You need to store the secret key that you previously recorded for X app in your Azure AD B2C tenant.
 
 1. Sign in to the [Azure portal](https://portal.azure.com/).
 1. If you have access to multiple tenants, select the **Settings** icon in the top menu to switch to your Azure AD B2C tenant from the **Directories + subscriptions** menu.
 1. In the Azure portal, search for and select **Azure AD B2C**.
 1. On the left menu, under **Policies**, select **Identity Experience Framework**.
 1. Select **Policy Keys** and then select **Add**.
 1. For **Options**, choose `Manual`.
-1. Enter a **Name** for the policy key. For example, `TwitterSecret`. The prefix `B2C_1A_` is added automatically to the name of your key.
+1. Enter a **Name** for the policy key. For example, `XSecret`. The prefix `B2C_1A_` is added automatically to the name of your key.
 1. For **Secret**, enter your *API key secret* value that you previously recorded.
 1. For **Key usage**, select `Signature`.
 1. Click **Create**.
 
-## Configure Twitter as an identity provider
+## Configure X as an identity provider
 
-To enable users to sign in using a Twitter account, you need to define the account as a claims provider that Azure AD B2C can communicate with through an endpoint. The endpoint provides a set of claims that are used by Azure AD B2C to verify that a specific user has authenticated.
+To enable users to sign in using an X account, you need to define the account as a claims provider that Azure AD B2C can communicate with through an endpoint. The endpoint provides a set of claims that are used by Azure AD B2C to verify that a specific user has authenticated.
 
-You can define a Twitter account as a claims provider by adding it to the **ClaimsProviders** element in the extension file of your policy. Refer to the custom policy starter pack that you downloaded in the Prerequisites of this article.
+You can define an X account as a claims provider by adding it to the **ClaimsProviders** element in the extension file of your policy. Refer to the custom policy starter pack that you downloaded in the Prerequisites of this article.
 
 1. Open the *TrustFrameworkExtensions.xml*.
 2. Find the **ClaimsProviders** element. If it does not exist, add it under the root element.
 3. Add a new **ClaimsProvider** as follows:
 
     ```xml
     <ClaimsProvider>
-      <Domain>twitter.com</Domain>
-      <DisplayName>Twitter</DisplayName>
+      <Domain>x.com</Domain>
+      <DisplayName>X</DisplayName>
       <TechnicalProfiles>
         <TechnicalProfile Id="Twitter-OAuth1">
-          <DisplayName>Twitter</DisplayName>
+          <DisplayName>X</DisplayName>
           <Protocol Name="OAuth1" />
           <Metadata>
             <Item Key="ProviderName">Twitter</Item>
@@ -152,7 +152,7 @@ You can define a Twitter account as a claims provider by adding it to the **Clai
             <Item Key="request_token_endpoint">https://api.twitter.com/oauth/request_token</Item>
             <Item Key="ClaimsEndpoint">https://api.twitter.com/1.1/account/verify_credentials.json?include_email=true</Item>
             <Item Key="ClaimsResponseFormat">json</Item>
-            <Item Key="client_id">Your Twitter application API key</Item>
+            <Item Key="client_id">Your X application API key</Item>
           </Metadata>
           <CryptographicKeys>
             <Key Id="client_secret" StorageReferenceId="B2C_1A_TwitterSecret" />
@@ -206,10 +206,10 @@ You can define a Twitter account as a claims provider by adding it to the **Clai
 1. Select your relying party policy, for example `B2C_1A_signup_signin`.
 1. For **Application**, select a web application that you [previously registered](tutorial-register-applications.md). The **Reply URL** should show `https://jwt.ms`.
 1. Select the **Run now** button.
-1. From the sign-up or sign-in page, select **Twitter** to sign in with Twitter account.
+1. From the sign-up or sign-in page, select **Twitter** to sign in with X account.
 ::: zone-end
 
 If the sign-in process is successful, your browser is redirected to `https://jwt.ms`, which displays the contents of the token returned by Azure AD B2C.
 
 > [!TIP]
->  If you're facing `unauthorized` error while testing this identity provider, make sure you use the correct Twitter API Key and API Key Secret, or try to apply for [elevated](https://developer.twitter.com/en/portal/products/elevated) access. Also, we recommend you've a look at [Twitter's projects structure](https://developer.twitter.com/en/docs/projects/overview), if you registered your app before the feature was available.
+>  If you're facing `unauthorized` error while testing this identity provider, make sure you use the correct X API Key and API Key Secret, or try to apply for [elevated](https://developer.x.com/en/portal/products/elevated) access. Also, we recommend you've a look at [X's projects structure](https://developer.x.com/en/docs/projects/overview), if you registered your app before the feature was available.

articles/active-directory-b2c/oauth1-technical-profile.md

@@ -14,23 +14,23 @@ ms.author: kengaderdus
 ms.subservice: B2C
 
 
-#Customer intent: As a developer implementing Azure Active Directory B2C custom policies, I want to define an OAuth1 technical profile, so that I can federate with an OAuth1 based identity provider like Twitter and allow users to sign in with their existing social or enterprise identities.
+#Customer intent: As a developer implementing Azure Active Directory B2C custom policies, I want to define an OAuth1 technical profile, so that I can federate with an OAuth1 based identity provider like X and allow users to sign in with their existing social or enterprise identities.
 
 ---
 
 # Define an OAuth1 technical profile in an Azure Active Directory B2C custom policy
 
 [!INCLUDE [active-directory-b2c-advanced-audience-warning](../../includes/active-directory-b2c-advanced-audience-warning.md)]
 
-Azure Active Directory B2C (Azure AD B2C) provides support for the [OAuth 1.0 protocol](https://tools.ietf.org/html/rfc5849) identity provider. This article describes the specifics of a technical profile for interacting with a claims provider that supports this standardized protocol. With an OAuth1 technical profile, you can federate with an OAuth1 based identity provider, such as Twitter. Federating with the identity provider allows users to sign in with their existing social or enterprise identities.
+Azure Active Directory B2C (Azure AD B2C) provides support for the [OAuth 1.0 protocol](https://tools.ietf.org/html/rfc5849) identity provider. This article describes the specifics of a technical profile for interacting with a claims provider that supports this standardized protocol. With an OAuth1 technical profile, you can federate with an OAuth1 based identity provider, such as X. Federating with the identity provider allows users to sign in with their existing social or enterprise identities.
 
 ## Protocol
 
 The **Name** attribute of the **Protocol** element needs to be set to `OAuth1`. For example, the protocol for the **Twitter-OAUTH1** technical profile is `OAuth1`.
 
 ```xml
 <TechnicalProfile Id="Twitter-OAUTH1">
-  <DisplayName>Twitter</DisplayName>
+  <DisplayName>X</DisplayName>
   <Protocol Name="OAuth1" />
   ...
 ```
@@ -45,7 +45,7 @@ The **OutputClaims** element contains a list of claims returned by the OAuth1 id
 
 The **OutputClaimsTransformations** element may contain a collection of **OutputClaimsTransformation** elements that are used to modify the output claims or generate new ones.
 
-The following example shows the claims returned by the Twitter identity provider:
+The following example shows the claims returned by the X identity provider:
 
 - The **user_id** claim that is mapped to the **issuerUserId** claim.
 - The **screen_name** claim that is mapped to the **displayName** claim.
@@ -92,4 +92,4 @@ When you configure the redirect URI of your identity provider, enter `https://{t
 
 Examples:
 
-- [Add Twitter as an OAuth1 identity provider by using custom policies](identity-provider-twitter.md)
+- [Add X as an OAuth1 identity provider by using custom policies](identity-provider-twitter.md)

articles/active-directory-b2c/userjourneys.md

@@ -261,7 +261,7 @@ The **ClaimsProviderSelection** element contains the following attributes:
 
 ### Claims provider selection example
 
-In the following orchestration step, the user can choose to sign in with Facebook, LinkedIn, Twitter, Google, or a local account. If the user selects one of the social identity providers, the second orchestration step executes with the selected claim exchange specified in the `TargetClaimsExchangeId` attribute. The second orchestration step redirects the user to the social identity provider to complete the sign-in process. If the user chooses to sign in with the local account, Azure AD B2C stays on the same orchestration step (the same sign-up page or sign-in page) and skips the second orchestration step.
+In the following orchestration step, the user can choose to sign in with Facebook, LinkedIn, X, Google, or a local account. If the user selects one of the social identity providers, the second orchestration step executes with the selected claim exchange specified in the `TargetClaimsExchangeId` attribute. The second orchestration step redirects the user to the social identity provider to complete the sign-in process. If the user chooses to sign in with the local account, Azure AD B2C stays on the same orchestration step (the same sign-up page or sign-in page) and skips the second orchestration step.
 
 ```xml
 <OrchestrationStep Order="1" Type="CombinedSignInAndSignUp" ContentDefinitionReferenceId="api.signuporsignin">

articles/advisor/index.yml

@@ -6,11 +6,11 @@ summary: Azure Advisor scans your Azure configuration and recommends changes to
 metadata:
   title: Azure Advisor documentation
   description: Azure Advisor is a personalized cloud consultant that helps you follow best practices to optimize your Azure deployments. It analyzes your resource configuration and usage telemetry. It then recommends solutions to help improve the performance, security, and high availability of your resources while looking for opportunities to reduce your overall Azure spend.
+  ms.author: ikhapova
+  author: ikhapova
   ms.topic: landing-page
   ms.service: azure-advisor
-  author: rboucher
-  ms.author: robb
-  ms.date: 10/16/2019
+  ms.date: 08/08/2024
 
 # linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | video | whats-new