Bug when setting "DenyAddAndCustomizePages" on the site properties.

[acmurchison-il]

Category

• Bug

Describe the bug

When setting the "DenyAddAndCustomizePages" on site properties, it's throwing a PnP.Core.CsomServiceException with the message "The requested operation is part of an experimental feature that is not supported in the current environment.". The value is actually set in SharePoint but we shouldn't be getting an exception returned. Potentially is a Microsoft update that is making this occur.

Both settings cause an issue:

Steps to reproduce

When calling the 'Update' method it throws the exception PnP.Core.CsomServiceException

Expected behavior

No Exception is thrown when it successfully sets in SharePoint.

Environment details (development & target environment)

• SDK version: [Pnp.Core 1.14.0]
• OS: Windows 11
• SDK used in: Reproduced in Test Framework (.NET 8.0, Console Application). Also seeing in an Azure Function.
• Framework: .NET8.0
• Browser(s): null
• Tooling: VS2022
• Additional details:

Additional context

Thanks for your contribution! Sharing is caring.

[fzbm]

We had the same issue and switched back to CSOM for this, because there it is still working. Our production environment was affected and we needed a solution for this issue fast. What we also determined is, that even if the error occurred, the state has still been changed. Nevertheless this issue should be looked into and getting fixed.

While PnP Core uses hand crafted CSOM requests for this, it looks like there is still a difference between the requests of the original library and PnP, which then triggers a different path on the server.

[ajcaterino]

We are also seeing the same issues when setting Site Collection properties. We set the StorageMaximumLevel and the value is not saved.

[LutzD-pkb]

Seems like it's just setting any site collection properties. I've tried StorageMaximumLevel, StorageWarningLevel, SharingCapability, DefaultSharingLinkType, and DefaultLinkToExistingAccess.. all produce this error.

[raclettierer]

we have the same problem. @fzbm can you share your workaround ?

[LutzD-pkb]

@raclettierer we worked around the issue using PnP Framework using the interop. The Site Collection Properties property is similar, there's just some extra scaffolding needed to initiate an admin center context, load the properties, and then save them:

//get the admin context from existing site context   
var adminCenterContext = await pnpContext.GetSharePointAdmin().GetTenantAdminCenterContextAsync();

//create a PnP Framework CSOM context from the PnP Core context
using ClientContext csomContext = PnPCoreSdk.Instance.GetClientContext(adminCenterContext);

//get the site properties
var tenant = new Microsoft.Online.SharePoint.TenantAdministration.Tenant(csomContext);
var siteAdminProperties = tenant.GetSitePropertiesByUrl(siteUrl, true);
tenant.Context.Load(siteAdminProperties);
await tenant.Context.ExecuteQueryRetryAsync();

//update site properties
siteAdminProperties.SharingCapability = Microsoft.Online.SharePoint.TenantManagement.SharingCapabilities.Disabled;
siteAdminProperties.Update();

//execute the query (the "Update" method doesn't actually save the change in PnP Framework)
await tenant.Context.ExecuteQueryRetryAsync();

This obviously introduces some tech debt because the PnP Framework is pseudo-deprecated, but it works.

[Gregorly]

We also have this issue, it was working in production the entirety of 2024 until around this issue was created. seriously frustrated. I am reluctant to use the work around because if this issue is fixed, a revert will need to be done.

Thanks for sharing your code @LutzD-pkb

[fzbm]

we have the same problem. @fzbm can you share your workaround ?

Sorry, was not able to answer yesterday, but @LutzD-pkb already posted an example of how we did this.

Instead of using the PnP Core method to get a ClientContext from a PnPContext we already had another way to get one. So if you already have an alternative way to get ClientContext instances, you can remove the dependency to PnP Framework. Also replace ExecuteQueryRetryAsync with ExecuteQueryAsync in that case.