You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/active-directory/users-groups-roles/groups-bulk-import-members.md
+9-12Lines changed: 9 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,21 +21,18 @@ Using Azure Active Directory (Azure AD) portal, you can add a large number of me
21
21
22
22
## Understand the bulk upload spreadsheet
23
23
24
-
Use the bulk upload spreadsheet as the template to fill in to successfully create Azure AD users in bulk.
24
+
Use the bulk upload spreadsheet as the template to fill in to successfully add Azure AD group members in bulk. Your spreadsheet might look like this example:
25
25
26
26

27
27
28
-
First two rows must not be removed or modified, needed for processing
29
-
There’s an example row that should be removed/replaced before upload
30
-
Note: Older versions of the template may not have the sample row
31
-
Provide info about Column header format
32
-
Format is <Item> [PropertyName] <Requiredornot>. For example, “Name [displayName] Required”
33
-
NOTE: Older versions of the template may have “Name (example: Chris Green) [displayName]*”
34
-
For groups, format is the same but you have the option to choose which item you use. Ex. “Member object ID or user principal name [memberObjectIdOrUpn] Required”
35
-
Required columns are list first
36
-
Any additional columns included in the uploaded CSV file will be ignored
37
-
create-template-example
38
-
I think we should recommend they download the latest version of the template periodically.
28
+
The first two rows of the upload template must not be removed or modified, or the upload can't be processed. We have included one row of examples of acceptable values. You must remove the examples row and replace it with your entries. Any additional columns you add are ignored and not processed. The required columns are listed first.
29
+
30
+
> [!Note]
31
+
> Older versions of the template might not have the examples row. We recommend that you download the latest version of the template as often as possible.
32
+
33
+
The format of the column headings is <*Item name*>[PropertyName]<*Required or blank*>. For example, `Name [displayName] Required`. Some older versions of the template might have something like `Name (example: Chris Green) [displayName] *`.
34
+
35
+
For groups, format is the same but you have the option to decide which identifier you use. An example of one such column heading is `Member object ID or user principal name [memberObjectIdOrUpn] Required`.
Copy file name to clipboardExpand all lines: articles/active-directory/users-groups-roles/users-bulk-add.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,7 +34,9 @@ The first two rows of the upload template must not be removed or modified, or th
34
34
> [!Note]
35
35
> Older versions of the template might not have the examples row. We recommend that you download the latest version of the template as often as possible.
36
36
37
-
The format of the column headings is <*Item name*>[PropertyName]<*Required or blank*>. For example, `Name [displayName] Required`. Some older versions of the template might have something like `Name (example: Chris Green) [displayName] *`. For groups, format is the same but you have the option to decide which identifier you use. An example of one such column heading is `Member object ID or user principal name [memberObjectIdOrUpn] Required`.
37
+
The format of the column headings is <*Item name*>[PropertyName]<*Required or blank*>. For example, `Name [displayName] Required`. Some older versions of the template might have something like `Name (example: Chris Green) [displayName] *`.
38
+
39
+
For groups, format is the same but you have the option to decide which identifier you use. An example of one such column heading is `Member object ID or user principal name [memberObjectIdOrUpn] Required`.
0 commit comments