Replies: 1 comment
-
hey @thacold1 , thanks for raising this issue. For the error that you are facing, you need to modify the permissions. ![]() |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Notice
Many bugs reported are actually related to the PnP Framework which is used behind the scenes. Consider carefully where to report an issue:
Invoke-PnPSiteTemplate
orGet-PnPSiteTemplate
? The issue is most likely related to the Provisioning Engine. The Provisioning engine is not located in the PowerShell repo. Please report the issue here: https://github.com/pnp/pnpframework/issues. NoReporting an Issue or Missing Feature
When connection to PNP.Online using an AppID Non-interactively w/ certificate, running a Get-PNPTenant or Set-PNPTenant produces a: Get-PnPTenant: The remote server returned an error: (401) Unauthorized.
Expected behavior
To see or modify Tenant settings for SPO
Actual behavior
Please describe what you see instead. Please provide samples of output or screenshots.
When attempting to Get or Set-PNPTenant we receive a 401 unauthorized error
Steps to reproduce behavior
Please include complete script or code samples in-line or linked from gists
Connect-PNPOnline -clientID $AppID -AzureEnvironment USGovernmentHigh -Url $URL -clientsecret $Secret
also
Connect-PNPOnline -clientID $AppID -AzureEnvironment USGovernmentHigh -Url $URL -tenant $tenantID -certificatePath $certificate -certificatepassword (convertto-secureString -asPlaintext " * " -force)
What is the version of the Cmdlet module you are running?
2.12.0
And we've tested 2.99 nightly same issue.
Which operating system/environment are you running PnP PowerShell on?
Beta Was this translation helpful? Give feedback.
All reactions