Skip to content

Commit 7c9f35f

Browse files
authored
Merge branch 'master' into v-ammark-seo-3
2 parents 1b6c62e + 1c6ad04 commit 7c9f35f

File tree

3,739 files changed

+16699
-14905
lines changed

Some content is hidden

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

3,739 files changed

+16699
-14905
lines changed

.openpublishing.redirection.json

Lines changed: 284 additions & 636 deletions
Large diffs are not rendered by default.

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/authentication/howto-mfa-getstarted.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -206,6 +206,9 @@ function Set-MfaState {
206206
Get-MsolUser -All | Set-MfaState -State Disabled
207207
```
208208

209+
> [!NOTE]
210+
> We recently changed the behavior and PowerShell script above accordingly. Previously, the script saved off the MFA methods, disabled MFA, and restored the methods. This is no longer necessary now that the default behavior for disable doesn't clear the methods.
211+
209212
## Plan Conditional Access policies
210213

211214
To plan your Conditional Access policy strategy, which will determine when MFA and other controls are required, refer to [What is Conditional Access in Azure Active Directory?](../conditional-access/overview.md).

articles/active-directory/authentication/howto-mfa-mfasettings.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -214,6 +214,8 @@ Settings for app passwords, trusted IPs, verification options, and remember mult
214214

215215
![Azure Multi-Factor Authentication service settings](./media/howto-mfa-mfasettings/multi-factor-authentication-settings-service-settings.png)
216216

217+
The trusted IP address ranges can be private or public.
218+
217219
## App passwords
218220

219221
Some applications, like Office 2010 or earlier and Apple Mail before iOS 11, don't support two-step verification. The apps aren't configured to accept a second verification. To use these applications, take advantage of the _app passwords_ feature. You can use an app password in place of your traditional password to allow an app to bypass two-step verification and continue working.

articles/active-directory/authentication/howto-mfa-reporting.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -21,16 +21,16 @@ Azure Multi-Factor Authentication provides several reports that can be used by y
2121

2222
| Report | Location | Description |
2323
|:--- |:--- |:--- |
24-
| Blocked User History | Azure AD > MFA Server > Block/unblock users | Shows the history of requests to block or unblock users. |
24+
| Blocked User History | Azure AD > Security > MFA > Block/unblock users | Shows the history of requests to block or unblock users. |
2525
| Usage and fraud alerts | Azure AD > Sign-ins | Provides information on overall usage, user summary, and user details; as well as a history of fraud alerts submitted during the date range specified. |
26-
| Usage for on-premises components | Azure AD > MFA Server > Activity Report | Provides information on overall usage for MFA through the NPS extension, ADFS, and MFA server. |
27-
| Bypassed User History | Azure AD > MFA Server > One-time bypass | Provides a history of requests to bypass Multi-Factor Authentication for a user. |
28-
| Server status | Azure AD > MFA Server > Server status | Displays the status of Multi-Factor Authentication Servers associated with your account. |
26+
| Usage for on-premises components | Azure AD > Security > MFA > Activity Report | Provides information on overall usage for MFA through the NPS extension, ADFS, and MFA server. |
27+
| Bypassed User History | Azure AD > Security > MFA > One-time bypass | Provides a history of requests to bypass Multi-Factor Authentication for a user. |
28+
| Server status | Azure AD > Security > MFA > Server status | Displays the status of Multi-Factor Authentication Servers associated with your account. |
2929

3030
## View MFA reports
3131

3232
1. Sign in to the [Azure portal](https://portal.azure.com).
33-
2. On the left, select **Azure Active Directory** > **MFA Server**.
33+
2. On the left, select **Azure Active Directory** > **Security** > **MFA**.
3434
3. Select the report that you wish to view.
3535

3636
![MFA Server server status report in the Azure portal](./media/howto-mfa-reporting/report.png)

articles/active-directory/authentication/howto-sspr-writeback.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -96,7 +96,7 @@ To set up the appropriate permissions for password writeback to occur, complete
9696
* **Write pwdLastSet**
9797
9. Select **Apply/OK** to apply the changes and exit any open dialog boxes.
9898

99-
Since the source of authority is on premises, the password complexity policies apply from the same connected data source. Make sure you've changed the existing group policies for "Minimum Password Length". The group policy shouldn't be set to 1, which means password should be at least a day old before it can be updated. You need make sure it's set to 0. These settings can be found in `gpmc.msc` under **Computer Configuration > Policies > Windows Settings > Security Settings > Account Policies**. Run `gpupdate /force` to ensure that the change takes effect.
99+
Since the source of authority is on premises, the password complexity policies apply from the same connected data source. Make sure you've changed the existing group policies for "Minimum password age". The group policy shouldn't be set to 1, which means password should be at least a day old before it can be updated. You need make sure it's set to 0. These settings can be found in `gpmc.msc` under **Computer Configuration > Policies > Windows Settings > Security Settings > Account Policies**. Run `gpupdate /force` to ensure that the change takes effect.
100100

101101
## Next steps
102102

articles/active-directory/b2b/add-users-administrator.md

Lines changed: 9 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ services: active-directory
77
ms.service: active-directory
88
ms.subservice: B2B
99
ms.topic: conceptual
10-
ms.date: 04/11/2019
10+
ms.date: 11/12/2019
1111

1212
ms.author: mimart
1313
author: msmimart
@@ -44,14 +44,18 @@ To add B2B collaboration users to the directory, follow these steps:
4444
> [!NOTE]
4545
> The **New guest user** option is also available on the **Organizational relationships** page. In **Azure Active Directory**, under **Manage**, select **Organizational relationships**.
4646
47-
5. Under **User name**, enter the email address of the external user. Optionally, include a welcome message. For example:
48-
49-
![Shows where New guest user is in the UI](./media/add-users-administrator/InviteGuest.png)
47+
5. On the **New user** page, select **Invite user** and then add the guest user's information.
5048

5149
> [!NOTE]
5250
> Group email addresses aren’t supported; enter the email address for an individual. Also, some email providers allow users to add a plus symbol (+) and additional text to their email addresses to help with things like inbox filtering. However, Azure AD doesn’t currently support plus symbols in email addresses. To avoid delivery issues, omit the plus symbol and any characters following it up to the @ symbol.
5351
54-
6. Select **Invite** to automatically send the invitation to the guest user.
52+
- **Name.** The first and last name of the guest user.
53+
- **Email address (required)**. The email address of the guest user.
54+
- **Personal message (optional)** Include a personal welcome message to the guest user.
55+
- **Groups**: You can add the guest user to one or more existing groups, or you can do it later.
56+
- **Directory role**: If you require Azure AD administrative permissions for the user, you can add them to an Azure AD role.
57+
58+
7. Select **Invite** to automatically send the invitation to the guest user.
5559

5660
After you send the invitation, the user account is automatically added to the directory as a guest.
5761

articles/active-directory/b2b/b2b-quickstart-add-guest-users-portal.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ services: active-directory
66
ms.service: active-directory
77
ms.subservice: B2B
88
ms.topic: quickstart
9-
ms.date: 07/02/2018
9+
ms.date: 11/12/2019
1010

1111
ms.author: mimart
1212
author: msmimart
@@ -44,9 +44,13 @@ To complete the scenario in this tutorial, you need:
4444

4545
![Screenshot showing where to select the New guest user option](media/quickstart-add-users-portal/quickstart-users-portal-user-3.png)
4646

47-
5. Under **User name**, enter the email address of the external user. Under **Include a personal message with the invitation**, type a welcome message.
47+
5. On the **New user** page, select **Invite user** and then add the guest user's information.
4848

49-
![Screenshot showing where to enter the guest user invitation message](media/quickstart-add-users-portal/quickstart-users-portal-user-4.png)
49+
- **Name.** The first and last name of the guest user.
50+
- **Email address (required)**. The email address of the guest user.
51+
- **Personal message (optional)** Include a personal welcome message to the guest user.
52+
- **Groups**: You can add the guest user to one or more existing groups, or you can do it later.
53+
- **Directory role**: If you require Azure AD administrative permissions for the user, you can add them to an Azure AD role.
5054

5155
6. Select **Invite** to automatically send the invitation to the guest user. A notification appears in the upper right with the message **Successfully invited user**.
5256
7. After you send the invitation, the user account is automatically added to the directory as a guest.

articles/active-directory/b2b/troubleshoot.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: active-directory
55
ms.service: active-directory
66
ms.subservice: B2B
77
ms.topic: troubleshooting
8-
ms.date: 05/25/2017
8+
ms.date: 11/12/2019
99
tags: active-directory
1010
ms.author: mimart
1111
author: v-miegge
@@ -90,6 +90,10 @@ To resolve this problem, you must take over the abandoned tenant. Refer to [Tak
9090

9191
If the identity tenant is a just-in-time (JIT) or viral tenant (meaning it's a separate, unmanaged Azure tenant), only the guest user can reset their password. Sometimes an organization will [take over management of viral tenants](https://docs.microsoft.com/azure/active-directory/users-groups-roles/domains-admin-takeover) that are created when employees use their work email addresses to sign up for services. After the organization takes over a viral tenant, only an administrator in that organization can reset the user's password or enable SSPR. If necessary, as the inviting organization, you can remove the guest user account from your directory and resend an invitation.
9292

93+
## A guest user is unable to use the AzureAD PowerShell V1 module
94+
95+
As of November 18, 2019, guest users in your directory (defined as user accounts where the **userType** property equals **Guest**) are blocked from using the AzureAD PowerShell V1 module. Going forward, a user will need to either be a member user (where **userType** equals **Member**) or use the AzureAD PowerShell V2 module.
96+
9397
## Next steps
9498

9599
[Get support for B2B collaboration](get-support.md)

0 commit comments

Comments
 (0)