Microsoft Roadmap, messagecenter en blogs updates van 27-03-2024

Updated March 26, 2024: Setting Custom scripts setting for a site in SharePoint tenant admin center will be fully available by early-April (Previously March)

PowerShell command (DelayDenyAddAndCustomizePagesEnforcement) to delay the change will be fully available by mid-April (Previously March)

The enforcement to set NoScriptSite to True for all existing SharePoint sites and OneDrive sites if DelayDenyAddAndCustomizePagesEnforcement is not set to True will start late-April and be completed by early-May (Previously March)

There are changes happening to Custom script settings between April and May 2024 (Previously March).

• The Custom Script setting, which determines if users can execute custom scripts on personal sites and self-service created sites will be removed by early-May (Previously March).

  This setting is currently located in the SharePoint Admin Center, under Settings -> Classic Settings.

  

• A new PowerShell command, “DelayDenyAddAndCustomizePagesEnforcement”, has been introduced. This command is available in the SharePoint Online Management Shell version 16.0.24524.12000, or above which allows delay of the change to custom script set on the Tenant until May 2024.

  
  

  Note: that while this cmdlet is available in the latest management shell, running the cmdlet will result in an error (The requested operation is part of an experimental feature that is not supported in the current environment) until Mid-April 2024 (Previously March) when the settings are shipped.

  * False (default) – for site collections where administrators enabled the ability to add custom script, SharePoint will revoke that ability within 24 hours from the last time this setting was changed.

  * True – All changes performed by administrators to custom script settings are preserved. When the value is set to true, a banner shows in the active sites list of the SharePoint admin center informing that changes to custom scripts are permanent.

  Set-SPOTenant -DelayDenyAddAndCustomizePagesEnforcement $True

  Please be aware that the new PowerShell command will only be accessible until May 2024. Post that period, on SharePoint sites if administrators wish to continue using features that are only available when unmanaged custom scripts are permitted to run, they will need to re-enable the running of custom scripts every 24 hours. This option does not impact existing custom scripts.

• The NoScriptSite setting will be configured to True for all existing SharePoint sites and OneDrive sites except for below mentioned sites templates.

  
  

  BLANKINTERNETCONTAINER#0 = Classic Publishing Portal site

  CMSPUBLISHING#0 = Publishing Site

  BLANKINTERNET#0 = Publishing Site

  GROUP#0 = Team site

  APPCATALOG#0 = App Catalog

  CSPCONTAINER#0 = CSP Container

• The execution of existing scripts in OneDrive and SharePoint sites will remain unaffected.
• There will not be an option to enable custom script on OneDrive sites once the delay set using DelayDenyAddAndCustomizePagesEnforcement ends in May 2024.
• Customers will retain the ability to permit the execution of custom scripts on specific SharePoint sites using the Set-SPOSite <SiteURL> -DenyAddAndCustomizePages PowerShell command or from the Active sites page in the SharePoint Admin Center.

  

  Any modifications made to a site will be automatically reverted to False status within 24 hours, unless the new PowerShell command “DelayDenyAddAndCustomizePagesEnforcement” is used prior to May 2024. After May, the 24 hour reversion will occur regardless of this setting. 

[When this will happen:]

The Custom Script setting from SharePoint admin center will be removed in March 2024. 

The new PowerShell command will be available in March 2024.

[How this will affect your organization:]

When this Custom Script setting is removed, you will no longer be able to add, modify or remove scripts within OneDrive and SharePoint sites unless administrators temporarily allow that by turning the setting on specific sites. This will not impact the ability to execute existing scripts in OneDrive and SharePoint sites. 

[What you need to do to prepare:]

No extensions will be granted beyond the mentioned period.

It may be beneficial to inform all site owners about this modification and make necessary updates to your training materials and documentation accordingly.

Review the following for additional information: Allow or prevent custom script

Beginning in late March, the Microsoft Copilot (formerly Bing Chat Enterprise) user interface (UI) will be updated to simplify the user experience. These UI updates are expected to be completed by mid-April.  

Microsoft Copilot UI updates include:

• Replacing the green “Protected” icon in the UI header with a green shield icon (located next to the user profile image): When a user hovers over the shield (or presses on the icon from within a supported mobile application), they will see a flyout description with a link to more information: “Commercial data protection applies to this chat. Use discretion when sharing personal and organizational data.”
• Adding a persistent legal and data protection disclaimer, along with links for Terms, Privacy, and FAQs, underneath the chat prompt box (bottom of the UI): “Commercial data protection applies to this chat. Terms | Privacy | FAQs”.
  • To simplify the UI, the following duplicative instances of these disclaimers or links will be removed:
    • The green data protection disclaimer above the prompt box (“Your personal and company data are protected”).
    • The light-grey data protection disclaimer within the flow of Copilot chat (“Your personal and company data are protected”).
    • The legal disclaimer and Terms, Privacy, and FAQs links located underneath the sample prompts.
• Adding a new AI accuracy disclaimer to the bottom of each chat: A shield with a lock icon and disclaimer will be added at the bottom of each chat: “AI-generated content may be incorrect.”
• Removing company branding/logo from the UI: Users will no longer see their company’s branding or logo as part of the Microsoft Copilot UI.
• Replacing the chat style selector with a new Copilot settings toggle: Users will be able to choose their preferred chat style, and if they want Bing Search turned on/off, from a new settings toggle located below the sample prompts. Future user settings in Copilot will be added to the settings toggle once available.

The UI will update for the following Microsoft Copilot entry points:

• Copilot.microsoft.com
• Copilot in Bing (bing.com/chat)
• Copilot in Edge (sidebar)
• Copilot in Windows
• Mobile applications:
  • Microsoft Copilot
  • Microsoft Edge
  • Microsoft Bing
  • Microsoft Start

[When this will happen:]

The Microsoft Copilot UI will begin updating in late March 2024. These updates are expected to be completed by mid-April 2024.

[How this will affect your organization:]

These are UI updates only–they do not impact Microsoft Copilot terms, privacy, or commercial data protection.

[What you need to do to prepare:]

Some of the previous commercial data protection visuals cues in Microsoft Copilot will change or be removed with this UI update.

We recommend that you prepare your users by informing them of the UI updates. Users should look for the green shield next to their profile icon, or the persistent disclaimer underneath the prompt box, to recognize when they are using Copilot with commercial data protection.

Microsoft Copilot (formerly Bing Chat Enterprise) adoption materials are available here: Copilot Starter Kit.

Beginning in late March, the Microsoft Copilot for Microsoft 365 user interface (UI) will be updated to create better visual alignment between it and Microsoft Copilot (formerly Bing Chat Enterprise). These UI updates are expected to be completed by mid-April.

Microsoft Copilot for Microsoft 365 UI updates include:

• Adding a green shield icon to the UI header (located next to the user profile image): When a user hovers over the shield (or presses on the icon from within a supported mobile application), they will see a flyout description with a link to more information: “Microsoft’s enterprise compliance standards apply to this chat. Use discretion when sharing personal and organizational data.”
• Adding a persistent legal and data protection disclaimer, along with links for Terms, Privacy, and FAQs, underneath the chat prompt box (bottom of the UI): “Microsoft’s enterprise compliance standards apply to this chat. Terms | Privacy | FAQs”.
  • To simplify the UI, the following duplicative instances of these disclaimers or links will be removed:
    • The blue lock icon with light-grey disclaimer within the flow of Copilot chat (“Work content and chats cannot be seen outside your organization.”).
    • The legal disclaimer and links for Terms, Privacy, and FAQs underneath the Copilot for Microsoft 365 branding.
• Adding a new AI accuracy disclaimer to the bottom of each chat: A shield with a lock icon and disclaimer will be added at the bottom of each chat: “AI-generated content may be incorrect.”
• Removing company branding/logo from the UI: Users will no longer see their company’s branding or logo as part of the Microsoft Copilot for Microsoft 365 UI.

These updates will roll out to the following Microsoft Copilot for Microsoft 365 entry points:

• Copilot.microsoft.com
• Copilot in Bing (bing.com/chat)
• Copilot in Edge (sidebar)
• Copilot in Windows
• Mobile applications:
  • Microsoft Copilot
  • Microsoft Edge

The UI for Copilot for Microsoft 365-specific entry points (such as those within the Microsoft 365 apps) will not update.

The Microsoft Copilot (formerly Bing Chat Enterprise) UI is also updating with similar changes to create better visual alignment between it and Copilot for Microsoft 365. Please refer to MC756004 for details on those UI updates.

[When this will happen:]

General Availability (include all environments here on same schedule): We will begin rolling out late March 2024 and expect to complete by mid-April 2024.

[How this will affect your organization:]

These are UI updates only–they do not impact Microsoft Copilot for Microsoft 365 terms, privacy, or data protections.

[What you need to do to prepare:]

We recommend that you prepare your users by informing them of the UI updates.

Microsoft Copilot for Microsoft 365 adoption materials are available here: Microsoft Adoption: Copilot for Microsoft 365. 

Windows Autopatch is informing all Autopatch customers with configured network restrictions would need to add the new domain name to their allow list.

[When this will happen:]

Effective immediately.

[How this will affect your organization:]

Customers with configured network restrictions will need to follow the instructions on adding the domain to their firewall.

[What you need to do to prepare:]

‘Modern Workplace – Autopatch Client Setup’ script installs the necessary client components in the device to use the Windows Autopatch service. This relies on the Windows 365 Cloud based service to operate. New domain (hm-iot-in-4-prod-prna01.azure-devices.net (443 & 5671 outbound)) has been added to the list of registration end points that is used in provisioning Cloud PCs. Autopatch customers with configured network restrictions would need to add the new domain name to their allow list if required. Complete end point list is provided in:

Network requirements

• Devices run Windows 11. 
• Devices meet the prerequisites for the deployment service. 
• Devices have installed the update described in KB4023057 – Update for Windows 10 Update Service components (or newer). 
• To verify that your devices meet the prerequisites for receiving an expedited update, use the Readiness test for expediting updates. 

• Read the complete article and guidance at Expedite non-security updates in Windows 11.
• For Microsoft Graph guidance, see Deploy an expedited quality update using the Windows Update for Business deployment service. 
• For Microsoft Intune users, follow steps in Expedite Windows quality updates. 
• Review best practices for using this feature: Get the most out of expedited Windows quality updates. 
• Learn more about Device readiness checks for expedited Windows quality updates. 

• This update adds more content to your lock screen. Sports, traffic, and finance content will appear along with weather. To turn on this feature, go to Settings > Personalization > Lockscreen.
• This update addresses an issue that affects the Settings app. It stops responding when you use it to remove Bluetooth devices.
• This update addresses an issue that affects USB audio. It fails on some processors. This occurs after you pause, play, or resume from sleep.
• The Windows share window now supports sharing with WhatsApp in the “Share using” section. 
• This update adds suggestions to Snap Layouts. They help you to instantly snap multiple app windows together.

• Windows 11, version 23H2: KB5035942
• Windows 11, version 22H2: KB5035942
• Windows 10, version 22H2: KB5035941