MicrosoftI wanted to reinforce one of the key points from my previous post, as I believe this warrants serious consideration.
Given the significant impact HTML Pages could have for customers, including the issues, limitations and risks outlined in my previous feedback, we would strongly encourage Microsoft to reconsider enabling HTML Pages by default.
HTML Pages should be OFF by default. Microsoft should introduce a tenant-wide setting for this capability, and importantly, that tenant setting should also default to OFF.
This would allow organizations to choose the approach that best suits their governance requirements:
As a large, global, multilingual organization, we absolutely wouldn't want HTML Pages enabled by default across our environment given the governance, branding, accessibility, multilingual, security and content consistency considerations we've raised.
Based on the current approach, we don't believe Microsoft fully appreciates the potential impact that such a significant change could have on large enterprise customers. This isn't simply another SharePoint feature being introduced. It has the potential to materially change how content is created, governed and managed across potentially very large environments.
The important principle here is that customers should make an explicit decision to enable a capability with this level of potential impact, rather than having to take action to disable it after Microsoft has enabled it by default.
HTML Pages have significant potential, but customers need appropriate control over how they're introduced into their environments. The safest and most customer-focused approach would be a tenant-wide control that Microsoft sets to OFF by default, with organizations and Site Owners opting in when they're ready.
+100 on this ... I feel this must have been an oversight on Microsoft's part to make this a default 'On' unless you switch off at site level - and not have the reverse of that, ie default as 'Off' unless enabled on a site.
While there will be scenarios a HTML page will bring something, it's astonishing that it would be thought a good idea to enable every editor the option to create a completely freestyle HTML page when there is probably zero need for it - and encourage it by placing 'HTML page' as the 2nd option when creating a new page?
