Set-pnpSite -classification doesnot work

[chandan805]

Target SharePoint environment

SharePoint Online

What SharePoint development model, framework, SDK or API is this about?

not applicable

Developer environment

Windows

What browser(s) / client(s) have you tested

• [ ] 💥 Internet Explorer
• [X] 💥 Microsoft Edge
• [X] 💥 Google Chrome
• [ ] 💥 FireFox
• [ ] 💥 Safari
• [ ] mobile (iOS/iPadOS)
• [ ] mobile (Android)
• [ ] not applicable
• [ ] other (enter in the "Additional environment details" area below)

Additional environment details

• browser version
• SPFx version
• Node.js version
• etc

Describe the bug / error

When using Pnp command to update the Classification of the modern site , this is not happening. These are not MIP label these are classic azure Ad directory object.

Steps to reproduce

1.Connect-PnPOnline -Url "SiteUrl" -ClientId $AppID -ClientSecret $AppSecret $a =Get-PnPSite 2.$a.Classification Confidential 3.erro: Set-PnPSite -Classification "Confidential" Set-PnPSite : Specified method is not supported. At line:1 char:1

• Set-PnPSite -Classification "Confidential"

•   + CategoryInfo          : WriteError: (:) [Set-PnPSite], ServerException
    + FullyQualifiedErrorId : EXCEPTION,PnP.PowerShell.Commands.Site.SetSite
  
  
  

Expected behavior

It should set the Confidential as classification for the site.

[chandan805]

I am using module as below 2.5.0 PnP.PowerShell PSGallery Microsoft 365 Patterns and Practices PowerShell Cmdlets

[mkm17]

Hi @chandan805 I guess the PnP PowerShell team be a better target for this question.

[Ashlesha-MSFT]

Hello @chandan805, Thank you for bringing this issue to our attention. We will look into it and get back to you shortly.

[Ashlesha-MSFT]

@mkm17, you are right. This issue should be posted on https://github.com/pnp/powershell/issues repo. @chandan805 You should post the issue on https://github.com/pnp/powershell/issues repo.

[Ashlesha-MSFT]

We are closing this issue for now due to inactivity from the developer. If the problem persists or reappears, feel free to reopen this issue or open a new one.