Skip to content

Commit bdf31d8

Browse files
authored
Merge pull request #104126 from MicrosoftDocs/master
2/12 AM Publish
2 parents 76bc196 + d04c832 commit bdf31d8

File tree

310 files changed

+3351
-5331
lines changed

Some content is hidden

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

310 files changed

+3351
-5331
lines changed

.openpublishing.redirection.json

Lines changed: 347 additions & 102 deletions
Large diffs are not rendered by default.

articles/active-directory-b2c/custom-policy-developer-notes.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ manager: celestedg
99
ms.service: active-directory
1010
ms.workload: identity
1111
ms.topic: conceptual
12-
ms.date: 03/18/2019
12+
ms.date: 02/12/2020
1313
ms.author: marsma
1414
ms.subservice: B2C
1515
---
@@ -68,7 +68,7 @@ Custom policy/Identity Experience Framework capabilities are under constant and
6868
| Relying Party OAUTH1 | | | | Not supported. |
6969
| Relying Party OAUTH2 | | | X | |
7070
| Relying Party OIDC | | | X | |
71-
| Relying Party SAML | X | | | |
71+
| Relying Party SAML | |X | | |
7272
| Relying Party WSFED | X | | | |
7373
| REST API with basic and certificate auth | | | X | For example, Azure Logic Apps. |
7474

@@ -81,7 +81,7 @@ Custom policy/Identity Experience Framework capabilities are under constant and
8181
| Azure Email subsystem for email verification | | | X | |
8282
| Multi-language support| | | X | |
8383
| Predicate Validations | | | X | For example, password complexity. |
84-
| Using third party email service providers | X | | | |
84+
| Using third party email service providers | |X | | |
8585

8686
### Content Definition
8787

articles/active-directory/authentication/TOC.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -64,7 +64,7 @@
6464
items:
6565
- name: Self-service password reset
6666
items:
67-
- name: Deploy self-service password reset
67+
- name: Deployment guide
6868
href: howto-sspr-deployment.md
6969
- name: Pre-register authentication data
7070
href: howto-sspr-authenticationdata.md
@@ -74,7 +74,7 @@
7474
href: howto-sspr-windows.md
7575
- name: Cloud-based MFA
7676
items:
77-
- name: Deploy cloud-based MFA
77+
- name: Deployment guide
7878
href: howto-mfa-getstarted.md
7979
- name: Per user MFA
8080
href: howto-mfa-userstates.md

articles/active-directory/authentication/index.yml

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ metadata:
1212
ms.topic: landing-page
1313
author: iainfoulds
1414
ms.author: iainfou
15-
ms.date: 08/20/2019
15+
ms.date: 02/11/2020
1616
ms.collection: M365-identity-device-management
1717

1818
# linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | whats-new
@@ -43,16 +43,16 @@ landingContent:
4343
url: concept-sspr-howitworks.md
4444
- text: Password writeback
4545
url: concept-sspr-writeback.md
46-
- linkListType: quickstart
46+
- linkListType: tutorial
4747
links:
48-
- text: Self-service password reset quickstart
49-
url: quickstart-sspr.md
48+
- text: Enable self-service password reset
49+
url: tutorial-enable-sspr.md
50+
- text: Enable password writeback to on-premises
51+
url: tutorial-enable-writeback.md
5052
- linkListType: deploy
5153
links:
52-
- text: Deploy Azure AD self-service password reset
54+
- text: Deployment guide for self-service password reset
5355
url: howto-sspr-deployment.md
54-
- text: Enable password writeback
55-
url: howto-sspr-writeback.md
5656
- text: Enable password reset from the Windows login screen
5757
url: howto-sspr-windows.md
5858

@@ -65,13 +65,13 @@ landingContent:
6565
url: concept-mfa-howitworks.md
6666
- linkListType: tutorial
6767
links:
68-
- text: Pilot Azure MFA for specific applications
69-
url: tutorial-mfa-applications.md
70-
- text: Use risk detections to trigger Multi-Factor Authentication and password changes
68+
- text: Enable Azure Multi-Factor Authentication
69+
url: tutorial-enable-azure-mfa.md
70+
- text: Enable risk-based Azure Multi-Factor Authentication
7171
url: tutorial-risk-based-sspr-mfa.md
7272
- linkListType: deploy
7373
links:
74-
- text: Deploy Azure Multi-Factor Authentication
74+
- text: Deployment guide for Azure Multi-Factor Authentication
7575
url: howto-mfa-getstarted.md
7676
- text: Use NPS extension to integrate on-premises applications
7777
url: howto-mfa-nps-extension.md
Lines changed: 147 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,147 @@
1+
---
2+
3+
title: Tutorial for bulk inviting B2B collaboration users - Azure Active Directory | Microsoft Docs
4+
description: In this tutorial, you learn how to use PowerShell and a CSV file to send bulk invitations to external Azure AD B2B collaboration guest users.
5+
6+
services: active-directory
7+
ms.service: active-directory
8+
ms.subservice: B2B
9+
ms.topic: tutorial
10+
ms.date: 02/11/2020
11+
12+
ms.author: mimart
13+
author: msmimart
14+
manager: celestedg
15+
ms.reviewer: mal
16+
17+
#customer intent: As a tenant administrator, I want to send B2B invitations to multiple external users at the same time so that I can avoid having to send individual invitations to each user.
18+
19+
ms.collection: M365-identity-device-management
20+
---
21+
22+
# Tutorial: Use PowerShell to bulk invite Azure AD B2B collaboration users
23+
24+
If you use Azure Active Directory (Azure AD) B2B collaboration to work with external partners, you can invite multiple guest users to your organization at the same time. In this tutorial, you learn how to use PowerShell to send bulk invitations to external users. Specifically, you do the following:
25+
26+
> [!div class="checklist"]
27+
> * Prepare a comma-separated value (.csv) file with the user information
28+
> * Run a PowerShell script to send invitations
29+
> * Verify the users were added to the directory
30+
31+
If you don’t have an Azure subscription, create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) before you begin.
32+
33+
## Prerequisites
34+
35+
### Install the latest AzureADPreview module
36+
37+
Make sure that you install the latest version of the Azure AD PowerShell for Graph module (AzureADPreview).
38+
39+
First, check which modules you have installed. Open Windows PowerShell as an elevated user (Run as administrator), and run the following command:
40+
41+
```powershell
42+
Get-Module -ListAvailable AzureAD*
43+
```
44+
45+
Based on the output, do one of the following:
46+
47+
- If no results are returned, run the following command to install the AzureADPreview module:
48+
49+
```powershell
50+
Install-Module AzureADPreview
51+
```
52+
53+
- If only the AzureAD module shows up in the results, run the following commands to install the AzureADPreview module:
54+
55+
```powershell
56+
Uninstall-Module AzureAD
57+
Install-Module AzureADPreview
58+
```
59+
60+
- If only the AzureADPreview module shows up in the results, but you receive a message that indicates there's a later version, run the following commands to update the module:
61+
62+
```powershell
63+
Uninstall-Module AzureADPreview
64+
Install-Module AzureADPreview
65+
```
66+
67+
You may receive a prompt that you're installing the module from an untrusted repository. This occurs if you haven't previously set the PSGallery repository as a trusted repository. Press **Y** to install the module.
68+
69+
### Get test email accounts
70+
71+
You need two or more test email accounts that you can send the invitations to. The accounts must be from outside your organization. You can use any type of account, including social accounts such as gmail.com or outlook.com addresses.
72+
73+
## Prepare the CSV file
74+
75+
In Microsoft Excel, create a CSV file with the list of invitee user names and email addresses. Make sure to include the **Name** and **InvitedUserEmailAddress** column headings.
76+
77+
For example, create a worksheet in the following format:
78+
79+
![PowerShell output showing pending user acceptance](media/tutorial-bulk-invite/AddUsersExcel.png)
80+
81+
Save the file as **C:\BulkInvite\Invitations.csv**.
82+
83+
If you don't have Excel, you can create a CSV file in any text editor, such as Notepad. Separate each value with a comma, and each row with a new line.
84+
85+
## Sign in to your tenant
86+
87+
Run the following command to connect to the tenant domain:
88+
89+
```powershell
90+
Connect-AzureAD -TenantDomain "<Tenant_Domain_Name>"
91+
```
92+
93+
For example, `Connect-AzureAD -TenantDomain "contoso.onmicrosoft.com"`.
94+
95+
When prompted, enter your credentials.
96+
97+
## Send bulk invitations
98+
99+
To send the invitations, run the following PowerShell script (where **c:\bulkinvite\invitations.csv** is the path of the CSV file):
100+
101+
```powershell
102+
$invitations = import-csv c:\bulkinvite\invitations.csv
103+
104+
$messageInfo = New-Object Microsoft.Open.MSGraph.Model.InvitedUserMessageInfo
105+
106+
$messageInfo.customizedMessageBody = "Hello. You are invited to the Contoso organization."
107+
108+
foreach ($email in $invitations)
109+
{New-AzureADMSInvitation `
110+
-InvitedUserEmailAddress $email.InvitedUserEmailAddress `
111+
-InvitedUserDisplayName $email.Name `
112+
-InviteRedirectUrl https://myapps.microsoft.com `
113+
-InvitedUserMessageInfo $messageInfo `
114+
-SendInvitationMessage $true
115+
}
116+
```
117+
118+
The script sends an invitation to the email addresses in the Invitations.csv file. You should see output similar to the following for each user:
119+
120+
![PowerShell output showing pending user acceptance](media/tutorial-bulk-invite/B2BBulkImport.png)
121+
122+
## Verify users exist in the directory
123+
124+
To verify that the invited users were added to Azure AD, run the following command:
125+
126+
```powershell
127+
Get-AzureADUser -Filter "UserType eq 'Guest'"
128+
```
129+
130+
You should see the users that you invited listed, with a user principal name (UPN) in the format *emailaddress*#EXT#\@*domain*. For example, *lstokes_fabrikam.com#EXT#\@contoso.onmicrosoft.com*, where contoso.onmicrosoft.com is the organization from which you sent the invitations.
131+
132+
## Clean up resources
133+
134+
When no longer needed, you can delete the test user accounts in the directory. Run the following command to delete a user account:
135+
136+
```powershell
137+
Remove-AzureADUser -ObjectId "<UPN>"
138+
```
139+
140+
For example: `Remove-AzureADUser -ObjectId "lstokes_fabrikam.com#EXT#@contoso.onmicrosoft.com"`
141+
142+
## Next steps
143+
144+
In this tutorial, you sent bulk invitations to guest users outside of your organization. Next, learn how the invitation redemption process works.
145+
146+
> [!div class="nextstepaction"]
147+
> [Learn about the Azure AD B2B collaboration invitation redemption process](redemption-experience.md)

articles/active-directory/b2b/toc.yml

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,9 @@
1515
href: b2b-quickstart-invite-powershell.md
1616
- name: Tutorials
1717
items:
18-
- name: Bulk invite B2B guest users
18+
- name: Bulk invite via PowerShell
19+
href: bulk-invite-powershell.md
20+
- name: Bulk invite via the portal (preview)
1921
href: tutorial-bulk-invite.md
2022
- name: Enforce multi-factor authentication
2123
href: b2b-tutorial-require-mfa.md

articles/active-directory/b2b/tutorial-bulk-invite.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ ms.collection: M365-identity-device-management
2828

2929
> [!NOTE]
3030
> As of 12/22/2019, the Bulk invite users (Preview) feature has been temporarily disabled.
31-
> There is currently no known date for when this feature will be re-enabled in the Azure portal. To invite guest users in bulk using PowerShell, see [B2B code and PowerShell samples](code-samples.md).
31+
> There is currently no known date for when this feature will be re-enabled in the Azure portal. To invite guest users in bulk using PowerShell, see the [B2B bulk invite tutorial](bulk-invite-powershell.md) or the [B2B code and PowerShell samples](code-samples.md).
3232
3333
If you use Azure Active Directory (Azure AD) B2B collaboration to work with external partners, you can invite multiple guest users to your organization at the same time. In this tutorial, you learn how to use the Azure portal to send bulk invitations to external users. Specifically, you do the following:
3434

articles/active-directory/cloud-provisioning/tutorial-pilot-aadc-aadccp.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -63,8 +63,7 @@ Azure AD Connect sync synchronizes changes occurring in your on-premises directo
6363
3. On the **Description** page, enter the following and click **Next**:
6464

6565
**Name:** Give the rule a meaningful name<br>
66-
**Description:** Add a meaningful description<br>
67-
66+
**Description:** Add a meaningful description<br>
6867
**Connected System:** Choose the AD connector that you are writing the custom sync rule for<br>
6968
**Connected System Object Type:** User<br>
7069
**Metaverse Object Type:** Person<br>

articles/active-directory/index.yml

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -72,15 +72,15 @@ conceptualContent:
7272

7373
- title: Authentication
7474
links:
75-
- url: ./authentication/concept-mfa-howitworks.md
75+
- url: ./authentication/overview-authentication.md
7676
itemType: concept
77-
text: "How it works: Azure MFA"
78-
- url: ./authentication/concept-sspr-howitworks.md
79-
itemType: concept
80-
text: Azure AD self-service password reset
81-
- url: ./authentication/concept-password-ban-bad.md
82-
itemType: concept
83-
text: Azure AD password protection
77+
text: What is Azure AD Authentication?
78+
- url: ./authentication/tutorial-enable-sspr.md
79+
itemType: tutorial
80+
text: Enable self-service password reset
81+
- url: ./authentication/tutorial-enable-azure-mfa.md
82+
itemType: tutorial
83+
text: Enable Azure Multi-Factor Authentication
8484
footerLink:
8585
url: ./authentication/index.yml
8686
text: See more

articles/active-directory/manage-apps/application-proxy-secure-api-access.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -8,8 +8,8 @@ ms.service: active-directory
88
ms.subservice: app-mgmt
99
ms.workload: identity
1010
ms.topic: conceptual
11-
ms.date: 10/24/2019
12-
ms.author: celested
11+
ms.date: 02/12/2020
12+
ms.author: mimart
1313
ms.reviewer: japere
1414
---
1515
# Secure access to on-premises APIs with Azure AD Application Proxy
@@ -47,19 +47,19 @@ To publish the SecretAPI web API through Application Proxy:
4747

4848
1. Build and publish the sample SecretAPI project as an ASP.NET web app on your local computer or intranet. Make sure you can access the web app locally.
4949

50-
1. In the [Azure portal](https://portal.azure.com), select **Azure Active Directory** in the left navigation. Then, on the **Overview** page, select **Enterprise applications**.
50+
1. In the [Azure portal](https://portal.azure.com), select **Azure Active Directory**. Then select **Enterprise applications**.
5151

5252
1. At the top of the **Enterprise applications - All applications** page, select **New application**.
5353

54-
1. On the **Browse Azure AD Gallery** page, under **On-premises applications**, select **Add an on-premises application**. The **Add your own on-premises application** page appears.
54+
1. On the **Add an application** page, select **On-premises applications**. The **Add your own on-premises application** page appears.
5555

5656
1. If you don't have an Application Proxy Connector installed, you'll be prompted to install it. Select **Download Application Proxy Connector** to download and install the connector.
5757

5858
1. Once you've installed the Application Proxy Connector, on the **Add your own on-premises application** page:
5959

60-
1. Enter *SecretAPI* next to **Name**.
60+
1. Next to **Name**, enter *SecretAPI*.
6161

62-
1. Enter the URL you use to access the API from within your intranet next to **Internal Url**.
62+
1. Next to **Internal Url**, enter the URL you use to access the API from within your intranet.
6363

6464
1. Make sure **Pre-Authentication** is set to **Azure Active Directory**.
6565

0 commit comments

Comments
 (0)