Merge pull request #174785 from kengaderdus/address-GHI-80392

[identity][Azure AD][B2C] Addressing GitHub issues #80392

Author: PRMerger19

articles/active-directory-b2c/microsoft-graph-operations.md

@@ -9,7 +9,7 @@ manager: celestedg
 ms.service: active-directory
 ms.workload: identity
 ms.topic: how-to
-ms.date: 06/22/2021
+ms.date: 10/08/2021
 ms.custom: project-no-code
 ms.author: mimart
 ms.subservice: B2C
@@ -134,6 +134,7 @@ The top-level resource for policy keys in the Microsoft Graph API is the [Truste
 ## Application extension properties
 
 - [List extension properties](/graph/api/application-list-extensionproperty)
+- [Delete extension property](/graph/api/application-delete-extensionproperty)
 
 Azure AD B2C provides a directory that can hold 100 custom attributes per user. For user flows, these extension properties are [managed by using the Azure portal](user-flow-custom-attributes.md). For custom policies, Azure AD B2C creates the property for you, the first time the policy writes a value to the extension property.
 

articles/active-directory-b2c/user-flow-custom-attributes.md

@@ -8,7 +8,7 @@ manager: celestedg
 ms.service: active-directory
 ms.workload: identity
 ms.topic: how-to
-ms.date: 09/20/2021
+ms.date: 10/08/2021
 ms.custom: project-no-code
 ms.author: mimart
 ms.subservice: B2C
@@ -44,7 +44,7 @@ Azure AD B2C allows you to extend the set of attributes stored on each user acco
 1. Provide a **Name** for the custom attribute (for example, "ShoeSize")
 1. Choose a **Data Type**. Only **String**, **Boolean**, and **Int** are available.
 1. Optionally, enter a **Description** for informational purposes.
-1. Click **Create**.
+1. Select **Create**.
 
 The custom attribute is now available in the list of **User attributes** and for use in your user flows. A custom attribute is only created the first time it is used in any user flow, and not when you add it to the list of **User attributes**.
 
@@ -54,9 +54,9 @@ The custom attribute is now available in the list of **User attributes** and for
 
 1. In your Azure AD B2C tenant, select **User flows**.
 1. Select your policy (for example, "B2C_1_SignupSignin") to open it.
-1. Select **User attributes** and then select the custom attribute (for example, "ShoeSize"). Click **Save**.
+1. Select **User attributes** and then select the custom attribute (for example, "ShoeSize"). Select **Save**.
 1. Select **Application claims** and then select the custom attribute.
-1. Click **Save**.
+1. Select **Save**.
 
 Once you've created a new user using a user flow, which uses the newly created custom attribute, the object can be queried in [Microsoft Graph Explorer](https://developer.microsoft.com/graph/graph-explorer). Alternatively you can use the [Run user flow](./tutorial-create-user-flows.md) feature on the user flow to verify the customer experience. You should now see **ShoeSize** in the list of attributes collected during the sign-up journey, and see it in the token sent back to your application.
 
@@ -68,7 +68,7 @@ Extension attributes can only be registered on an application object, even thoug
 
 ::: zone pivot="b2c-user-flow"
 
-To get the application ID:
+### Get extensions app's application ID
 
 1. Sign in to the [Azure portal](https://portal.azure.com).
 1. Make sure you're using the directory that contains your Azure AD B2C tenant. Select the **Directories + subscriptions** icon in the portal toolbar.
@@ -82,7 +82,7 @@ To get the application ID:
 
 ::: zone pivot="b2c-custom-policy"
 
-Get the application properties:
+### Get extensions app's application properties
 
 1. Sign in to the [Azure portal](https://portal.azure.com).
 1. Make sure you're using the directory that contains your Azure AD B2C tenant. Select the **Directories + subscriptions** icon in the portal toolbar.
@@ -185,6 +185,36 @@ Microsoft Graph API supports creating and updating a user with extension attribu
 "extension_831374b3bd5041bfaa54263ec9e050fc_loyaltyId": "212342" 
 ``` 
 
+## Remove extension attribute
+
+Unlike built-in attributes, extension/custom attributes can be removed. The extension attributes' values can also be removed. 
+
+> [!Important]
+> Before you remove the extension/custom attribute, for each account in the directory, set the extension attribute value to null.  In this way you explicitly remove the extension attributes’s values. Then continue to remove the extension attribute itself. Extension/custom attribute is queryable using MS Graph API. 
+
+::: zone pivot="b2c-user-flow"
+
+Use the following steps to remove extension/custom attribute from a user flow:
+
+1. Sign in to the [Azure portal](https://portal.azure.com/) as the global administrator of your Azure AD B2C tenant.
+2. Make sure you're using the directory that contains your Azure AD B2C tenant:
+    1.  Select the **Directories + subscriptions** icon in the portal toolbar.
+    1. On the **Portal settings | Directories + subscriptions** page, find your Azure AD B2C directory in the Directory name list, and then select **Switch**
+1. Choose **All services** in the top-left corner of the Azure portal, search for and select **Azure AD B2C**.
+1. Select **User attributes**, and then select the attribute you want to delete.
+1. Select **Delete**
+
+::: zone-end
+
+::: zone pivot="b2c-custom-policy"
+
+To remove a custom attribute, use [MS Graph API](microsoft-graph-operations.md), and use the [Delete](/graph/api/application-delete-extensionproperty) command.
+
+::: zone-end
+
+ 
+
+
 ## Next steps
 
 Follow the guidance for how to [add claims and customize user input using custom policies](configure-user-input.md). This sample uses a built-in claim 'city'. To use a custom attribute, replace 'city' with your own custom attributes.