-
Notifications
You must be signed in to change notification settings - Fork 399
Description
Reporting an Issue or Missing Feature
While running my integration tests with Microsoft365Dsc, which uses PnP 1.12.0, I noticed that the resource SPOTenantSettings was failing and the error message was about UserVoiceForFeedbackEnabled, but I never saw the error before with that same version of the module installed. So I run manually Set-PnPTenant -UserVoiceForFeedbackEnabled $true/false on that tenant and it also failed the same way, see below, then I also tried the same on 2 other separate tenants with the same result so it seems to be a backend issue, are you aware of this? Is this property being deprecated and it needs to be removed from the module or is it just a matter of waiting until it starts working again?
Please note that this is not only happening in my local machine but also in the containers used in Azure DevOps MSHosted pipelines.
Expected behavior
Setting the property UserVoiceForFeedbackEnabled should change it in the tenant and not result in error
Actual behavior
Trying to change the property UserVoiceForFeedbackEnabled results in the following error message:
Set-PnPTenant : Field or property "UserVoiceForFeedbackEnabled" does not exist.
At line:1 char:1
+ Set-PnPTenant -UserVoiceForFeedbackEnabled $true
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (:) [Set-PnPTenant], PSInvalidOperationException
+ FullyQualifiedErrorId : InvalidOperation,PnP.PowerShell.Commands.Admin.SetTenantSteps to reproduce behavior
Set-PnPTenant -UserVoiceForFeedbackEnabled $true # or $falseWhat is the version of the Cmdlet module you are running?
1.12.0
Which operating system/environment are you running PnP PowerShell on?
- Windows
- Linux
- MacOS
- Azure Cloud Shell
- Azure Functions
- Other : please specify