Skip to content

Commit 39da2d9

Browse files
authored
Merge pull request #95666 from MicrosoftDocs/master
11/12 AM Publish
2 parents 44c2a96 + 1e067c4 commit 39da2d9

File tree

130 files changed

+440
-1199
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

130 files changed

+440
-1199
lines changed

.openpublishing.redirection.json

Lines changed: 16 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -43598,10 +43598,25 @@
4359843598
"redirect_url": "articles/active-directory/develop/app-registrations-training-guide-for-app-registrations-legacy-users.md",
4359943599
"redirect_document_id": false
4360043600
},
43601-
{
43601+
{
4360243602
"source_path": "articles/azure-monitor/app/powershell-script-create-resource.md",
4360343603
"redirect_url": "/azure/azure-monitor/app/create-new-resource#creating-a-resource-automatically",
4360443604
"redirect_document_id": false
43605+
},
43606+
{
43607+
"source_path": "articles/cognitive-services/translator/how-to-install-containers.md",
43608+
"redirect_url": "/azure/cognitive-services/translator/translator-info-overview",
43609+
"redirect_document_id": false
43610+
},
43611+
{
43612+
"source_path": "articles/cognitive-services/translator/translator-text-container-config.md",
43613+
"redirect_url": "/azure/cognitive-services/translator/translator-info-overview",
43614+
"redirect_document_id": false
43615+
},
43616+
{
43617+
"source_path": "articles/aks/virtual-kubelet.md",
43618+
"redirect_url": "/azure/aks/concepts-scale#burst-to-azure-container-instances",
43619+
"redirect_document_id": false
4360543620
}
4360643621
]
4360743622
}

articles/active-directory-b2c/TOC.yml

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -320,6 +320,9 @@
320320
href: active-directory-b2c-devquickstarts-graph-dotnet.md
321321
- name: Audit logs
322322
href: active-directory-b2c-reference-audit-logs.md
323+
- name: Manage users - Azure portal
324+
href: manage-users-portal.md
325+
displayName: create users, add users, delete users
323326
- name: Secure API Management API
324327
href: secure-api-management.md
325328
displayName: apim, api management, migrate, b2clogin.com
Lines changed: 60 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,60 @@
1+
---
2+
title: Create & delete Azure AD B2C consumer user accounts in the Azure portal
3+
description: Learn how to use the Azure portal to create and delete consumer users in your Azure AD B2C directory.
4+
services: active-directory-b2c
5+
author: mmacy
6+
manager: celestedg
7+
8+
ms.service: active-directory
9+
ms.workload: identity
10+
ms.topic: conceptual
11+
ms.date: 11/09/2019
12+
ms.author: marsma
13+
ms.subservice: B2C
14+
---
15+
16+
# Use the Azure portal to create and delete consumer users in Azure AD B2C
17+
18+
There might be scenarios in which you want to manually create consumer accounts in your Azure Active Directory B2C (Azure AD B2C) directory. Although consumer accounts in an Azure AD B2C directory are most commonly created when users sign up to use one of your applications, you can create them programmatically and by using the Azure portal. This article focuses on the Azure portal method of user creation and deletion.
19+
20+
To add or delete users, your account must be assigned the *User administrator* or *Global administrator* role.
21+
22+
[!INCLUDE [active-directory-b2c-public-preview](../../includes/active-directory-b2c-public-preview.md)]
23+
24+
## Types of user accounts
25+
26+
As described in [Overview of user accounts in Azure AD B2C](user-overview.md), there are three types of user accounts that can be created in an Azure AD B2C directory:
27+
28+
* Work
29+
* Guest
30+
* Consumer
31+
32+
This article focuses on working with **consumer accounts** in the Azure portal. For information about creating and deleting Work and Guest accounts, see [Add or delete users using Azure Active Directory](../active-directory/fundamentals/add-users-azure-active-directory.md).
33+
34+
## Create a consumer user
35+
36+
1. Sign in to the [Azure portal](https://portal.azure.com).
37+
1. Select the **Directory + subscription** filter in the top menu, and then select the directory that contains your Azure AD B2C tenant.
38+
1. In the left menu, select **Azure AD B2C**. Or, select **All services** and search for and select **Azure AD B2C**.
39+
1. Under **Manage**, select **Users**.
40+
1. Select **New user**.
41+
1. Select **Create Azure AD B2C user**.
42+
1. Choose a **Sign in method** and enter either an **Email** address or a **Username** for the new user. The sign in method you select here must match the setting you've specified for your Azure AD B2C tenant's *Local account* identity provider (see **Manage** > **Identity providers** in your Azure AD B2C tenant).
43+
1. Enter a **Name** for the user. This is typically the full name (given and surname) of the user.
44+
1. (Optional) You can **Block sign in** if you wish to delay the ability for the user to sign in. You can enable sign in later by editing the user's **Profile** in the Azure portal.
45+
1. Choose **Auto-generate password** or **Let me create password**.
46+
1. Specify the user's **First name** and **Last name**.
47+
1. Select **Create**.
48+
49+
Unless you've selected **Block sign in**, the user can now sign in using the sign in method (email or username) that you specified.
50+
51+
## Delete a consumer user
52+
53+
1. In your Azure AD B2C directory, select **Users**, and then select the user you want to delete.
54+
1. Select **Delete**, and then **Yes** to confirm the deletion.
55+
56+
For details about restoring a user within the first 30 days after deletion, or for permanently deleting a user, see [Restore or remove a recently deleted user using Azure Active Directory](../active-directory/fundamentals/active-directory-users-restore.md).
57+
58+
## Next steps
59+
60+
For automated user management scenarios, for example migrating users from another identity provider to your Azure AD B2C directory, see [Azure AD B2C: User migration](active-directory-b2c-user-migration.md).

articles/active-directory/develop/scenario-web-api-call-api-app-configuration.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -138,6 +138,8 @@ private void AddAccountToCacheFromJwt(IEnumerable<string> scopes, JwtSecurityTok
138138
}
139139
```
140140

141+
You can also see an example of on behalf of flow implementation in [NodeJS and Azure Functions](https://github.com/Azure-Samples/ms-identity-nodejs-webapi-onbehalfof-azurefunctions/blob/master/MiddleTierAPI/MyHttpTrigger/index.js#L61).
142+
141143
## Protocol
142144

143145
For more information about the on-behalf-of protocol, see [Microsoft identity platform and OAuth 2.0 On-Behalf-Of flow](https://docs.microsoft.com/azure/active-directory/develop/v2-oauth2-on-behalf-of-flow).

articles/active-directory/develop/tutorial-v2-ios.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -138,7 +138,7 @@ let kScopes: [String] = ["https://graph.microsoft.com/user.read"] // request per
138138
let kAuthority = "https://login.microsoftonline.com/common" // this authority allows a personal Microsoft account and a work or school account in any organization’s Azure AD tenant to sign in
139139
var accessToken = String()
140140
var applicationContext : MSALPublicClientApplication?
141-
var webViewParamaters : MSALWebviewParameters?
141+
var webViewParameters : MSALWebviewParameters?
142142
```
143143

144144
The only value you need to modify above is the value assigned to `kClientID`to be your [Application ID](https://docs.microsoft.com/azure/active-directory/develop/developer-glossary#application-id-client-id). This value is part of the MSAL Configuration data that you saved during the step at the beginning of this tutorial to register the application in the Azure portal.
@@ -318,16 +318,16 @@ Add the following after `initMSAL` method to the `ViewController` class.
318318

319319
```swift
320320
func initWebViewParams() {
321-
self.webViewParamaters = MSALWebviewParameters(parentViewController: self)
321+
self.webViewParameters = MSALWebviewParameters(parentViewController: self)
322322
}
323323
```
324324

325325
### macOS code:
326326

327327
```swift
328328
func initWebViewParams() {
329-
self.webViewParamaters = MSALWebviewParameters()
330-
self.webViewParamaters?.webviewType = .wkWebView
329+
self.webViewParameters = MSALWebviewParameters()
330+
self.webViewParameters?.webviewType = .wkWebView
331331
}
332332
```
333333

@@ -421,7 +421,7 @@ Add the following code to the `ViewController` class.
421421
func acquireTokenInteractively() {
422422

423423
guard let applicationContext = self.applicationContext else { return }
424-
guard let webViewParameters = self.webViewParamaters else { return }
424+
guard let webViewParameters = self.webViewParameters else { return }
425425

426426
// #1
427427
let parameters = MSALInteractiveTokenParameters(scopes: kScopes, webviewParameters: webViewParameters)

articles/active-directory/manage-apps/application-proxy-configure-native-client-application.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -67,7 +67,7 @@ Now that you've registered your native application, you can give it access to ot
6767
1. Select **Add a permission**. The **Request API permissions** page appears.
6868
1. Under the **Select an API** setting, select **APIs my organization uses**. A list appears, containing the applications in your directory that expose APIs.
6969
1. Type in the search box or scroll to find the proxy application that you published in [Step 1: Publish your proxy application](#step-1-publish-your-proxy-application), and then select the proxy application.
70-
1. In the **What type of permissions does your application require?** heading, select the permission type. If your native application needs to access the proxy application API as the signed-in user, choose **Delegated permissions**. If your native application runs as a background service or daemon without a signed-in user, choose **Application permissions**.
70+
1. In the **What type of permissions does your application require?** heading, select the permission type. If your native application needs to access the proxy application API as the signed-in user, choose **Delegated permissions**.
7171
1. In the **Select permissions** heading, select the desired permission, and select **Add permissions**. The **API permissions** page for your native application now shows the proxy application and permission API that you added.
7272

7373
## Step 4: Edit the Active Directory Authentication Library

articles/active-directory/manage-apps/configure-single-sign-on-non-gallery-applications.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -158,4 +158,4 @@ For more information, see [Debug SAML-based single sign-on to applications in Az
158158
## Next steps
159159

160160
- [Assign users or groups to the application](methods-for-assigning-users-and-groups.md)
161-
- [Configure automatic user account provisioning](configure-automatic-user-provisioning-portal.md)
161+
- [Configure automatic user account provisioning](configure-automatic-user-provisioning-portal.md)

articles/active-directory/reports-monitoring/concept-audit-logs.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,6 @@ This article gives you an overview of the audit report.
3939
## Who can access the data?
4040

4141
* Users in the **Security Administrator**, **Security Reader**, **Report Reader** or **Global Administrator** roles
42-
* In addition, all users (non-administrators) can see their own sign-in activities
4342

4443
## Audit logs
4544

articles/active-directory/users-groups-roles/directory-delete-howto.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -105,7 +105,7 @@ When you begin the deletion of the self-service sign-up product, the action perm
105105

106106
For more information about currently available self-service sign-up products and services, see [Available self-service programs](https://docs.microsoft.com/office365/admin/misc/self-service-sign-up?view=o365-worldwide#available-self-service-programs).
107107

108-
For what to expect when a trial Office 365 subscription expires (not including paid Partner/CSP, Enterprise Agreement, or Volume Licensing), see the following table. For more information on Office 365 data retention and subscription lifecycle, see[What happens to my data and access when my Office 365 for business subscription ends?](https://docs.microsoft.com/office365/admin/subscriptions-and-billing/what-if-my-subscription-expires?view=o365-worldwide).
108+
For what to expect when a trial Office 365 subscription expires (not including paid Partner/CSP, Enterprise Agreement, or Volume Licensing), see the following table. For more information on Office 365 data retention and subscription lifecycle, see [What happens to my data and access when my Office 365 for business subscription ends?](https://docs.microsoft.com/office365/admin/subscriptions-and-billing/what-if-my-subscription-expires?view=o365-worldwide).
109109

110110
Product state | Data | Access to data
111111
------------- | ---- | --------------
@@ -116,13 +116,13 @@ Deleted | Data deleted | Users can’t access self-service sign-up product, file
116116

117117
You can put a self-service sign-up product like Microsoft Power BI or Azure Rights Management Services into a **Delete** state to be immediately deleted in the Azure AD portal.
118118

119-
1. Sign in to the[Azure AD admin center](https://aad.portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/Overview)with an account that is a Global administrator in the organization. If you are trying to delete the “Contoso” directory that has the initial default domain contoso.onmicrosoft.com, sign on with a UPN such as [email protected].
119+
1. Sign in to the [Azure AD admin center](https://aad.portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/Overview) with an account that is a Global administrator in the organization. If you are trying to delete the “Contoso” directory that has the initial default domain contoso.onmicrosoft.com, sign on with a UPN such as [email protected].
120120

121-
2. Select **Licenses**, and then select**Self-service sign-up products**. You can see all the self-service sign-up products separately from the seat-based subscriptions. Choose the product you want to permanently delete. Here's an example in Microsoft Power BI:
121+
2. Select **Licenses**, and then select **Self-service sign-up products**. You can see all the self-service sign-up products separately from the seat-based subscriptions. Choose the product you want to permanently delete. Here's an example in Microsoft Power BI:
122122

123123
![the username is mistyped or not found](./media/directory-delete-howto/licenses-page.png)
124124

125-
3. Select**Delete**to delete the product and accept the terms that data is deleted immediately and irrevocably. This delete action will remove all users and remove organization access to the product. Click Yes to move forward with the deletion.
125+
3. Select **Delete** to delete the product and accept the terms that data is deleted immediately and irrevocably. This delete action will remove all users and remove organization access to the product. Click Yes to move forward with the deletion.
126126

127127
![the username is mistyped or not found](./media/directory-delete-howto/delete-product.png)
128128

articles/aks/TOC.yml

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -128,8 +128,6 @@
128128
href: virtual-nodes-cli.md
129129
- name: Use the Azure portal
130130
href: virtual-nodes-portal.md
131-
- name: Use Virtual Kubelet
132-
href: virtual-kubelet.md
133131
- name: Use Cluster Autoscaler
134132
href: cluster-autoscaler.md
135133
- name: Use Availability Zones

0 commit comments

Comments
 (0)