Updates to Sync-PnPSharePointUserProfilesFromAzureActiveDirectory
and Get-PnPAzureADUser
#1559
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Type
Related Issues?
N/A
What is in this Pull Request ?
-UseBeta
parameter toGet-PnPAzureADUser
to force it to use the Microsoft Graph beta endpoint. This can be necessary when i.e. using-Select "PreferredDataLocation"
to query for users with a specific multi geo location as this property is only available through the beta endpoint.Sync-PnPSharePointUserProfilesFromAzureActiveDirectory
to return our own entity instead of the one returned by CSOM to decouple it and also allow for it to return the location where the import file has been uploaded to on SharePoint when using-WhatIf
. This allows for the scenario where you would use-WhatIf
to create the mapping JSON file, but not actually start the import yet because i.e. you want to modify the data in the mapping file first before you trigger the import process to start.-Content
option toAdd-PnPFile
which allows creating a new file on SharePoint Online and directly providing its textual content, i.e. to upload a log file of the executionThis PR is pending PnP Framework PR pnp/pnpframework#586 to be merged first.