Skip to content

Commit ff1bc53

Browse files
authored
Update Bulk-user-profile-update-api-for-sharepoint-online.md
Fixed dead links, updated help on PnP PowerShell, added notice on backslashes needing to be escaped with a backslash
1 parent 589f0a9 commit ff1bc53

File tree

1 file changed

+6
-30
lines changed

1 file changed

+6
-30
lines changed

docs/solution-guidance/Bulk-user-profile-update-api-for-sharepoint-online.md

Lines changed: 6 additions & 30 deletions
Original file line numberDiff line numberDiff line change
@@ -113,7 +113,8 @@ The following are restrictions on individual source data files:
113113

114114
- Maximum file size: 2 GB
115115
- Maximum number of properties: 500,000
116-
- The source file must be uploaded to the same SharePoint Online tenant where the process is started.
116+
- Backslashes (\) in property values need escaping by prepending with another backslash
117+
- The source file must be uploaded to the same SharePoint Online tenant where the process is started
117118

118119
> [!NOTE]
119120
> The update file must have the Byte Order Mark (BOM) specified if any characters are not part of the Western European encoding (iso-8859-1) which is the default. International characters may not be interpreted correctly with the default encoding, so it is recommended to use the UTF-8 encoding. This encoding has a BOM of 'EF BB BF' in hex. This would be placed at the beginning of the byte array of the file when creating the file stream. If using a text editor, select the endoding type as UTF-8 before saving.
@@ -357,38 +358,13 @@ $context.ExecuteQuery();
357358
Write-Host "Import job created with the following identifier:" $workItemId.Value
358359
```
359360

360-
### Sample PowerShell script using PnP PowerShell
361+
### Updating the SharePoint Online User Profile using PnP PowerShell
361362

362-
To initiate a bulk import using [PnP PowerShell](https://aka.ms/pnp-powershell), you can use:
363+
To synchronize user profile properties from Azure Active Directory to SharePoint Online user profiles, you can leverage the [PnP PowerShell](https://pnp.github.io/powershell) cmdlet [Sync-PnPSharePointUserProfilesFromAzureActiveDirectory](https://pnp.github.io/powershell/cmdlets/Sync-PnPSharePointUserProfilesFromAzureActiveDirectory.html).
363364

364-
```powershell
365-
@"
366-
{
367-
"value": [
368-
{
369-
"IdName": "[email protected]",
370-
"Department": "PnP",
371-
},
372-
{
373-
"IdName": "[email protected]",
374-
"Department": "PnP",
375-
}
376-
]
377-
}
378-
"@ > profiles.json
379-
380-
New-PnPUPABulkImportJob -Folder "Shared Documents" -Path profiles.json -IdProperty "IdName" -UserProfilePropertyMapping @{"Department"="Department"}
381-
```
382-
383-
For more information, see [New-PnPUPABulkImportJob](/powershell/module/sharepoint-pnp/new-pnpupabulkimportjob)
384-
385-
To check on the processing status of a bulk import job, you can use:
386-
387-
```powershell
388-
Get-PnPUPABulkImportStatus
389-
```
365+
Alternatively, if you want to synchronize user profile properties from another source, you can use [New-PnPUPABulkImportJob](https://pnp.github.io/powershell/cmdlets/New-PnPUPABulkImportJob.html).
390366

391-
For more information, see [Get-PnPUPABulkImportStatus](/powershell/module/sharepoint-pnp/get-pnpupabulkimportstatus)
367+
To check on the processing status of a bulk import job, you can use [Get-PnPUPABulkImportStatus](https://pnp.github.io/powershell/cmdlets/Get-PnPUPABulkImportStatus.html).
392368

393369
[!INCLUDE [pnp-powershell](../../includes/snippets/open-source/pnp-powershell.md)]
394370

0 commit comments

Comments
 (0)