-
Notifications
You must be signed in to change notification settings - Fork 527
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
issue with SPOUserProfileProperty | SPN | Cannot bind argument to parameter 'Properties' because it is null. #2798
Comments
Please have a look at this thread. Within SharePoint you need to assign additional permissions to the app. |
Hi, |
Hello, I'm attempting to export only, no writing. I have https://microsoft.sharepoint-df.com/Sites.Read.All. Ah! Looks like my app needs full control to read? Should this be necessary? Thank you |
@NikCharlebois Application has SharePoint:Sites.fullControl.all. |
@jeffreykarlan Sites.FullControl.All is a requirement of the SPO APIs even if you are just doing an export. |
Looks like we were missing a permission for the SPOUserProfileProperty. You will also need to grant: SharePoint: In order of it to work. A fix is in the work to properly document this. Thanks |
Details of the scenario you tried and the problem that is occurring
run the command with
Verbose logs showing the problem
[2023-01-18 03.25.27]
{InvalidData}
System.Management.Automation.ParameterBindingValidationException: Cannot bind argument to parameter 'Properties' because it is null.
at System.Management.Automation.ExceptionHandlingOps.CheckActionPreference(FunctionContext funcContext, Exception exception)
at System.Management.Automation.Interpreter.ActionCallInstruction`2.Run(InterpretedFrame frame)
at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
"Error during Export:"
at Export-TargetResource, C:\Program Files\WindowsPowerShell\Modules\Microsoft365DSC\1.23.111.1\DSCResources\MSFT_SPOUserProfileProperty\MSFT_SPOUserProfileProperty.psm1: line 324
at Start-M365DSCConfigurationExtract, C:\Program Files\WindowsPowerShell\Modules\Microsoft365DSC\1.23.111.1\modules\M365DSCReverse.psm1: line 615
at Export-M365DSCConfiguration, C:\Program Files\WindowsPowerShell\Modules\Microsoft365DSC\1.23.111.1\modules\M365DSCUtil.psm1: line 1190
at , : line 1
TenantId: maheshms365.onmicrosoft.com
Suggested solution to the issue
The DSC configuration that is used to reproduce the issue (as detailed as possible)
# insert configuration here
The operating system the target node is running
OsName : Microsoft Windows 10 Home Single Language
OsOperatingSystemSKU : 100
OsArchitecture : 64-bit
WindowsVersion : 2009
WindowsBuildLabEx : 19041.1.amd64fre.vb_release.191206-1406
OsLanguage : en-US
OsMuiLanguages : {en-US}
Version of the DSC module that was used ('dev' if using current dev branch)
The text was updated successfully, but these errors were encountered: