Upcoming Change on DenyAddAndCustomizePages

I did try to understand this change in respect of WebProperties in PNP-Templates:
https://admin.microsoft.com/AdminPortal/home?#/MessageCenter/:/messages/MC714186

Thinking about how to handle this in PnP-Framework as i currently see no alternative to Indexed WebProperties in order to promote additional Data about a Site to search. As the article does not mention WebProperties but they have been affected by the DenyAddAndCustomizePages setting i would think we have to handle this change in pnpframework.

My suggested fix would be to check on BaseSiteTemplate and existance of PropertyBagEntries in Template. If the Site Type is affected by the change and Entries exist i would set DenyAddAndCustomizePages to false. The way i understand the change MC714186 this setting will be reverted within 24 hours.

@jansenbe Before i start implement this change, i would like to know what are your thoughts on this?

Start by reviewing the linked MC714186 announcement and the PnP-Templates handling of BaseSiteTemplate and PropertyBagEntries. Confirm which site types are affected and how DenyAddAndCustomizePages is currently applied; the change is done when the agreed behavior for templates with property bag entries is implemented and verified.