Skip to content

Commit 4983e7e

Browse files
committed
Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into acila
2 parents f35dd5a + 3901110 commit 4983e7e

File tree

2,088 files changed

+4483
-5285
lines changed

Some content is hidden

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

2,088 files changed

+4483
-5285
lines changed

.openpublishing.redirection.json

Lines changed: 73 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,10 @@
11
{
22
"redirections": [
3+
{
4+
"source_path": "articles/digital-twins/how-to-use-legacy-aad.md",
5+
"redirect_url": "/azure/digital-twins/quickstart-view-occupancy-dotnet#set-permissions-for-your-app",
6+
"redirect_document_id": false
7+
},
38
{
49
"source_path": "articles/php-download-sdk.md",
510
"redirect_url": "https://github.com/Azure/azure-sdk-for-php",
@@ -515,11 +520,16 @@
515520
"redirect_url": "/azure/machine-learning",
516521
"redirect_document_id": false
517522
},
523+
{
524+
"source_path": "articles/cognitive-services/LUIS/luis-how-to-add-example-utterances.md",
525+
"redirect_url": "/azure/cognitive-services/LUIS/luis-how-to-add-entities",
526+
"redirect_document_id": false
527+
},
518528
{
519529
"source_path": "articles/cognitive-services/LUIS/luis-tutorial-prebuilt-intents-entities.md",
520530
"redirect_url": "/azure/cognitive-services/LUIS/tutorial-machine-learned-entity",
521531
"redirect_document_id": false
522-
},
532+
},
523533
{
524534
"source_path": "articles/cognitive-services/LUIS/luis-quickstart-intents-only.md",
525535
"redirect_url": "/azure/cognitive-services/LUIS/tutorial-intents-only",
@@ -41813,6 +41823,11 @@
4181341823
"redirect_url": "/azure/iot-central/preview/tutorial-define-edge-device-type/",
4181441824
"redirect_document_id": false
4181541825
},
41826+
{
41827+
"source_path": "articles/iot-central/core/tutorial-add-edge-as-leaf-device.md",
41828+
"redirect_url": "/azure/iot-central/preview/tutorial-add-edge-as-leaf-device/",
41829+
"redirect_document_id": false
41830+
},
4181641831
{
4181741832
"source_path": "articles/iot-central/core/tutorial-use-device-groups-pnp.md",
4181841833
"redirect_url": "/azure/iot-central/preview/tutorial-use-device-groups/",
@@ -43587,6 +43602,63 @@
4358743602
"source_path": "articles/active-directory/develop/app-registrations-training-guide.md",
4358843603
"redirect_url": "articles/active-directory/develop/app-registrations-training-guide-for-app-registrations-legacy-users.md",
4358943604
"redirect_document_id": false
43605+
},
43606+
{
43607+
"source_path": "articles/azure-monitor/app/powershell-script-create-resource.md",
43608+
"redirect_url": "/azure/azure-monitor/app/create-new-resource#creating-a-resource-automatically",
43609+
"redirect_document_id": false
43610+
},
43611+
{
43612+
"source_path": "articles/load-balancer/load-balancer-outbound-connections-classic.md",
43613+
"redirect_url": "/previous-versions/azure/load-balancer/load-balancer-outbound-connections-classic",
43614+
"redirect_document_id": false
43615+
},
43616+
{
43617+
"source_path": "articles/load-balancer/load-balancer-multivip.md",
43618+
"redirect_url": "/previous-versions/azure/load-balancer/load-balancer-multivip",
43619+
"redirect_document_id": false
43620+
},
43621+
{
43622+
"source_path": "articles/load-balancer/load-balancer-get-started-ilb-classic-cloud.md",
43623+
"redirect_url": "/previous-versions/azure/load-balancer/load-balancer-get-started-ilb-classic-cloud",
43624+
"redirect_document_id": false
43625+
},
43626+
{
43627+
"source_path": "articles/load-balancer/load-balancer-get-started-ilb-classic-ps.md",
43628+
"redirect_url": "/previous-versions/azure/load-balancer/load-balancer-get-started-ilb-classic-ps",
43629+
"redirect_document_id": false
43630+
},
43631+
{
43632+
"source_path": "articles/load-balancer/load-balancer-get-started-ilb-classic-cli.md",
43633+
"redirect_url": "/previous-versions/azure/load-balancer/load-balancer-get-started-ilb-classic-cli",
43634+
"redirect_document_id": false
43635+
},
43636+
{
43637+
"source_path": "articles/load-balancer/load-balancer-get-started-internet-classic-ps.md",
43638+
"redirect_url": "/previous-versions/azure/load-balancer/load-balancer-get-started-internet-classic-ps",
43639+
"redirect_document_id": false
43640+
},
43641+
{
43642+
"source_path": "articles/load-balancer/load-balancer-get-started-internet-classic-cloud.md",
43643+
"redirect_url": "/previous-versions/azure/load-balancer/load-balancer-get-started-internet-classic-cloud",
43644+
"redirect_document_id": false
43645+
},
43646+
{
43647+
"source_path": "articles/load-balancer/load-balancer-get-started-internet-classic-cli.md",
43648+
"redirect_url": "/previous-versions/azure/load-balancer/load-balancer-get-started-internet-classic-cli",
43649+
"source_path": "articles/cognitive-services/translator/how-to-install-containers.md",
43650+
"redirect_url": "/azure/cognitive-services/translator/translator-info-overview",
43651+
"redirect_document_id": false
43652+
},
43653+
{
43654+
"source_path": "articles/cognitive-services/translator/translator-text-container-config.md",
43655+
"redirect_url": "/azure/cognitive-services/translator/translator-info-overview",
43656+
"redirect_document_id": false
43657+
},
43658+
{
43659+
"source_path": "articles/aks/virtual-kubelet.md",
43660+
"redirect_url": "/azure/aks/concepts-scale#burst-to-azure-container-instances",
43661+
"redirect_document_id": false
4359043662
}
4359143663
]
4359243664
}

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/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)

articles/active-directory/develop/TOC.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -392,9 +392,9 @@
392392
href: active-directory-configurable-token-lifetimes.md
393393
- name: Application configuration
394394
items:
395-
- name: Azure portal app registrations training guide (legacy)
395+
- name: Transitioning from App registrations (Legacy) to the new App registrations experience in the Azure portal
396396
href: app-registrations-training-guide-for-app-registrations-legacy-users.md
397-
- name: Application Registration Portal app registration guide
397+
- name: Transitioning from Application Registration Portal to the new App registrations experience in the Azure portal
398398
href: app-registration-portal-training-guide.md
399399
- name: Convert a single-tenant app to a multi-tenant app
400400
href: howto-convert-app-to-be-multi-tenant.md

articles/active-directory/develop/access-tokens.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -260,9 +260,9 @@ Refresh tokens can be invalidated or revoked at any time, for different reasons.
260260
| [Single sign-out](v1-protocols-openid-connect-code.md#single-sign-out) on web | Revoked | Stays alive | Revoked | Stays alive | Stays alive |
261261

262262
> [!NOTE]
263-
> A "Non-password based" login is one where the user didn't type in a password to get it. For example, using your face with Windows Hello, a FIDO key, or a PIN.
263+
> A "Non-password based" login is one where the user didn't type in a password to get it. For example, using your face with Windows Hello, a FIDO2 key, or a PIN.
264264
>
265-
> A known issue exists with the Windows Primary Refresh Token. If the PRT is obtained via a password, and then the user logs in via Hello, this does not change the origination of the PRT, and it will be revoked if the user changes their password.
265+
> Primary Refresh Tokens (PRT) on Windows 10 are segregated based on the credential. For example, Windows Hello and password have their respective PRTs, isolated from one another. When a user signs-in with a Hello credential (PIN or biometrics) and then changes the password, the password based PRT obtained previously will be revoked. Signing back in with a password invalidates the old PRT and requests a new one.
266266
>
267267
> Refresh tokens aren't invalidated or revoked when used to fetch a new access token and refresh token.
268268

articles/active-directory/develop/app-registration-portal-training-guide.md

Lines changed: 9 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,7 @@
11
---
2-
title: Application Registration Portal app registrations training guide - Microsoft identity platform | Azure
3-
description: App registrations in the Azure portal for users familiar with Application registration portal
2+
title: Transitioning from Application Registration Portal to the new App registrations experience in the Azure portal
3+
titleSuffix: Microsoft identity platform
4+
description: An introduction to the new App registration experience in the Azure portal
45
services: active-directory
56
documentationcenter: ''
67
author: archieag
@@ -20,7 +21,7 @@ ms.custom: aaddev
2021
ms.collection: M365-identity-device-management
2122
---
2223

23-
# Training guide: Using App registrations in the Azure portal instead of Application Registration Portal
24+
# Transitioning from Application Registration Portal to the new App registrations experience in the Azure portal
2425

2526
There are many improvements in the new [App registrations](https://go.microsoft.com/fwlink/?linkid=2083908) experience in the Azure portal. If you're more familiar with the Application registration portal (apps.dev.microsoft.com) experience for registering or managing converged applications, referred to as the old experience, this training guide will get you started using the new experience.
2627

@@ -113,15 +114,15 @@ separate pages. Here's where you can find the equivalent functionality:
113114

114115
- Advanced option - Live SDK support is on the Authentication page.
115116

116-
## Application Secrets/Certificates & secrets
117+
## Application secrets/Certificates & secrets
117118

118119
In the new experience, **Application secrets** have been renamed to
119120
**Certificates & secrets**. In addition, **Public keys** are referred to as
120121
**Certificates** and **Passwords** are referred to as **Client secrets**. We
121122
chose to not bring this functionality along in the new experience for
122123
security reasons, hence, you can no longer generate a new key pair.
123124

124-
## Platforms/Authentication - Reply URLs/Redirect URIs
125+
## Platforms/Authentication: Reply URLs/redirect URIs
125126
In the old experience, an app had Platforms section for Web, native, and
126127
Web API to configure Redirect URLs, Logout URL and Implicit flow.
127128

@@ -138,7 +139,7 @@ Web APIs are configured in Expose an API page.
138139
configure settings for your application based on the platform or device
139140
that you want to target. [Learn more](quickstart-configure-app-access-web-apis.md#configure-platform-settings-for-your-application)
140141

141-
## Microsoft Graph Permissions/API permissions
142+
## Microsoft Graph permissions/API permissions
142143

143144
- When selecting an API in the old experience, you could choose from
144145
Microsoft Graph APIs only. In the new experience, you can choose
@@ -172,7 +173,7 @@ the manifest editor or the API, or didn't exist.
172173

173174
- Implicit grant flow (oauth2AllowImplicitFlow) can be found on the
174175
Authentication page. Unlike the old experience, you can enable
175-
access tokens or id tokens, or both.
176+
access tokens or ID tokens, or both.
176177

177178
- Scopes defined by this API (oauth2Permissions) and Authorized client
178179
applications (preAuthorizedApplications) can be configured through
@@ -202,4 +203,4 @@ The new experience has the following limitations:
202203
between Azure AD single-tenant and multi-tenant.
203204

204205
> [!NOTE]
205-
> If you're a personal Microsoft account user in Azure AD tenant, and the tenant admin has restricted access to Azure portal, you may get an access denied. However, if you come through the shortcut by typing App registrations in the search bar or pinning it, you'll be able to access the new experience.
206+
> If you're a personal Microsoft account user in Azure AD tenant, and the tenant admin has restricted access to Azure portal, you may get an access denied. However, if you come through the shortcut by typing App registrations in the search bar or pinning it, you'll be able to access the new experience.

0 commit comments

Comments
 (0)