Dear WorkPoint customers and partners,
We are writing to inform you about an upcoming change from Microsoft that affects the way WorkPoint uses SharePoint Online to store important entity information. This change might require some actions from you to ensure that your WorkPoint solution continues to work as expected.
What is changing?
In SharePoint Online, it is possible to store information about sites that are only available through code and not accessible by end-users. This feature is called the property bag, and this has always been used by WorkPoint to link entities and entity sites.
Microsoft is moving away from this feature and will stop supporting it by November 2024. Therefore, we are planning to introduce an alternative solution to this during 2024.
In order to use the property bag, WorkPoint currently sets the "Custom Script" settings for all sites created by WorkPoint. When Microsoft introduces the upcoming change, this setting will be reset every 24 hours. The main impact for WorkPoint solutions is that buffer and bucket sites will fail when creating new entities.
Microsoft will introduce a new setting, "DelayDenyAddAndCustomizePagesEnforcement". The exact time schedule from Microsoft is unknown and will probably be a gradual deployment. This command allows delaying the enforcement of the custom script restriction on the tenant level until mid-November 2024. By then WorkPoint will have mitigated the issue and stopped using the property bag.
If you are an Microsoft 365 administrator with access to the Admin Portal, you can read more about the change from Microsoft in the following
https://admin.microsoft.com/?ref=MessageCenter/:/messages/MC714186
The challenge
In order to prevent an impact of this issue for all solutions the “DelayDenyAddAndCustomizePagesEnforcement” property needs to be set. However, this property is currently not working and thereby impossible to use before an update from Microsoft is released. We are currently in close contact with Microsoft and expect them to resolve the issue before it impacts you – however, this cannot be guaranteed.
Will my solution be impacted by this?
Today, we will release a fix (4.13.5 and 3.26.0), that handles this issue by ensuring the “Custom Script” property is set before writing to the property bag. This fix is expected to address the issue for 90% of WorkPoint customers.
However, in some situations this is not possible. This involves the following scenarios.
- Solutions where full consent has not been granted to WorkPoint. This means that you as a customer/partner manage the provisioning of site collections.
- Solutions running Classic UI (this will only involve solutions older than ~5 years that have not been updated to Modern UI yet).
What do you need to do?
If your solution is impacted by the issue, entity creation can start failing. This can be fixed by setting the DelayDenyAddAndCustomizePagesEnforcement. This can be done by the following PowerShell command
Set-SPOTenant -DelayDenyAddAndCustomizePagesEnforcement $True
Microsoft states it requires the 16.0.24524.12000 version of the SharePoint Online Management Shell. However, this requires an update from Microsoft where the release date is unknown (we are in dialog with Microsoft on this).
Further, you will afterwards need to set the Custom Script property on all active bucket sites (in multi-site business modules).
Further, important information regarding Classic UI
Please note that due to this change from Microsoft, WorkPoint solutions that are still running classic UI will stop working from November this year, as they rely heavily on the Custom Script feature. So please make sure to update all WorkPoint solutions to modern UI before this date.
If you have any questions or concerns about this change, please contact us.
Thank you for your cooperation and understanding.
Sincerely,
The WorkPoint team
Comments
0 comments
Article is closed for comments.