888-682-5765 info@totalsol.com

Are you keeping up with Microsoft updates? The Microsoft Mondays: Microsoft Service Updates series from Total Solutions is here for your needs, and remember that Total Solutions also provides tailored, expert guidance during our consulting process. Microsoft are highlighting a few of the Microsoft announced upcoming updates from February:

Keep an eye out for Microsoft Mondays for your Microsoft updates or speak with our technical team for your Microsoft needs.

* Updates posted here originally posted by Microsoft in the Microsoft 365 Message Center


Remove Custom Script setting in OneDrive and SharePoint web (Updated)

[MC714186 · Published Feb 9, 2024] · Last updated Feb 16, 2024] Updated February 16, 2024: Microsoft has updated the content below with additional information for clarity. Thank you for your feedback.

There are changes happening to Custom script settings in March 2024.

  • The Custom Script setting, which determines if users can execute custom scripts on personal sites and self-service created sites will be removed.

    This setting is currently located in the SharePoint Admin Center, under Settings -> Classic Settings.
Custom Script Setting in OneDrive and SharePoint
Figure 1 – Custom Script Setting in OneDrive and SharePoint
  • 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.

    * 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.
Custom Scripts in SharePoint Admin Center
Figure 2 – Custom Scripts in 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. 

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


Microsoft Exchange admin center: new troubleshooting option

[MC716665 · Published Feb 16, 2024] The Microsoft Exchange admin center (EAC) is launching new troubleshooting workflows to help customers resolve common issues more efficiently.

When this will happen:

Standard Release: Microsoft will begin rolling out mid-February 2024 and expect to complete by late June 2024.

How will this affect your organization:

Admins will be able to access the new Troubleshoot option on the left navigation of the Microsoft Exchange admin center. When common issues arise, admins can run the Quick fixes workflow or Collect logs workflow to investigate. These workflows gather logs and data to provide relevant information, making troubleshooting easier. All logs and data are stored on the admin’s local machine for easy access.

The Quick fixes option includes workflows to resolve known issues. Each workflow provides detailed information about the actions it performs and the specific issue it addresses. In this initial release, admins will be able to quickly reset Outlook on the web (OWA) settings for users, helping to resolve various login and calendar-related issues. The Collect logs workflows can be used to diagnose issues with resource mailboxes functioning in unexpected ways or meetings updating incorrectly for a mailbox. Each workflow executes multiple cmdlets and provides aggregated information, which is then downloaded to the admin’s local machine as logs. These logs can be used to diagnose issues independently or provide additional information before contacting Support.

Microsoft Exchange Admin Center Collect Logs
Figure 3 – Microsoft Exchange Admin Center Collect Logs
Reset OWA Settings
Figure 4 – Reset OWA Settings

What you need to do to prepare:

No action is needed to prepare for this change. You may want to notify your users about this change and update any relevant documentation as appropriate.


Preview enterprise secure AI controls in the Microsoft Edge management service (Updated)

[MC694372 · Published Nov 29, 2023 · Last updated Feb 16, 2024] Updated February 16, 2024: Microsoft have updated the rollout timeline below. Thank you for your patience.

The Microsoft Edge management service is a new, dedicated, and simplified management experience for Microsoft Edge in the Microsoft 365 admin center. Controls for enterprise secure Ai in the Edge management service is rolling out now for preview. This new feature allows IT admins to configure all AI-related policies in one single page, enhancing security for their users and devices.

This message is associated with Microsoft 365 Roadmap ID 186540

When this will happen:

Preview: This is currently rolling out for preview and is expected to be complete by early December 2023.

Standard Release: This will begin rolling out in mid-March 2024 (previously mid-February) and complete rolling out by early April 2024 (previously early March).

How this will affect your organization:

This feature will provide a central location to manage all AI-related policies in the Microsoft Edge browser. Configuration for AI safety is easier without the need to look through all policy documentation and identify those that incorporate the use of AI. The Edge management service, where this feature is located, provides a simple and quick way to manage Microsoft Edge.

What you need to do to prepare:

To manage enterprise secure AI controls in the Edge management service, you will need Global admin or Edge admin access. Go here to learn how to assign admin roles in the Microsoft 365 admin center.

To access the experience, go to the Microsoft 365 admin center > Settings > Microsoft Edge. This feature is currently only available for preview, which can be enable by going to the Microsoft 365 admin center > Settings > Org settings > Organization profile > Release preferences and opting into a targeted release.

Additional information

Help and support


Microsoft Teams: Archive channels (Updated)

[MC696576 · Published Dec 7, 2023 · Last updated Feb 16, 2024]  Updated February 16, 2024: Microsoft has updated the rollout timeline below. Thank you for your patience.

For a paused or completed project where owners want to preserve channel content, but no longer want to keep the channel active, they can archive channels now!

Archiving channels will be available for Teams users. You, as a channel owner or administrator can archive a channel you own. By archiving the channel, it will not be available in your and channel members teams and channels list anymore and no more actions will be allowed on the channel like messaging, reacting, commenting, editing etc. In case, you want, you can unarchive the channel as well, by going to manage teams > channels. Team members can hoist the channel in their left rail even after archival.

This message is associated with Microsoft 365 Roadmap ID 123769

When this will happen:

Targeted Release: Microsoft will begin rolling out early February 2024 (previously early January) and expect to complete by mid-February 2024 (previously early January).

Standard Release: Microsoft will begin rolling out late February 2024 (previously mid-February) and expect to complete by mid-March 2024 (previously late February).

How this will affect your organization:

Channel owners and administrators can now archive channels to avoid any activity on them and can restore if needed. Channel members will not be able to take actions on the channel like messaging, reacting, commenting, editing etc., but they can still access and read through the channel content. 

What you need to do to prepare: Communicate teams and channel owners to utilize archive channel capability to keep the channel in read-only mode. 


Microsoft Teams: Updated labels for external participants in meetings

[MC716008 · Published Feb 14, 2024] Updated February 8, 2024In our continuous drive to increase the security of Microsoft Teams meetings, Microsoft is updating the labels for the participants’ names. To bring in consistency and accuracy to the user labels, we are introducing the term Unverified, which will be seen for all meeting participants who do not have a trusted relationship with the organizer. All participants who are not part of the organizer’s organization but are configured as a trusted relationship with the organizer will continue to be termed as External.

Additionally, Microsoft is ensuring that all areas within Team meetings – lobby, participant roster, meeting chat, and so on – will consistently show accurate user labels.

When this will happen:

Standard Release: Microsoft will begin rolling out mid-February 2024 and expect to complete by early March 2024 for all the in-meeting participant views. Other areas within Teams meetings will soon follow with these updates. This will be announced in a future post.

How this will affect your organization:

Organizers and meeting participants in your organization who attend meetings with users outside of their organization – with or without a Microsoft Entra ID – will see the changes in labels that reflect the trust level of the participant with the organizer (External, Unverified, or no label).

  • No label: All participants who are part of the organizer’s organization.
  • External: All participants who are external to the organizer’s organization but have a trusted relationship with the organizer or their organization.
  • Unverified: All other participants will be seen with this label. This will include Microsoft Entra ID users who belong to organizations that do not have an explicit external access setup with the organizer’s organization, Microsoft Account (personal) users, users who are not using any Microsoft ID while joining meetings, and others.

What you need to do to prepare: To prepare for this change, share this information with the meeting organizers who regularly invite participants outside of their organizations.


Moving admin center controls for Microsoft Search in Bing and Copilot for Microsoft 365 in Bing, Edge, and Windows

[MC716390 · Published Feb 16, 2024] Updated February 7, 2024] To provide additional flexibility in managing Search for your organization, Microsoft Search in Bing and Microsoft Copilot for Microsoft 365 in Bing, Edge, and Windows will no longer be managed by a single control in the Microsoft 365 admin center. Copilot for Microsoft 365 in Bing, Edge, and Windows will be managed using a PowerShell script.

When this will happen:

Standard Release: Microsoft will begin rolling out mid-February 2024 and expect to complete by late February 2024.

How this will affect your organization:

With this change, you can separately manage Microsoft Search in Bing and Copilot for Microsoft 365 in Bing, Edge, and Windows for your organization. Previously, a single control was on the Search & intelligence page for Microsoft Search in Bing and Copilot for Microsoft 365 in Bing, Edge, and Windows.

In the Microsoft admin center, the control for Microsoft Search in Bing will stay on the Search & intelligence page. Your current selection with the single control will be inherited after this release.

Copilot for Microsoft 365 in Bing, Edge, and Windows will no longer have a control in the Microsoft admin center. Instead, a PowerShell script will be available to manage it. If you have Copilot for Microsoft 365, your current selection with the single control will be inherited after this release. If you purchase Copilot for Microsoft 365 later, Copilot for Microsoft 365 in Bing, Edge, and Windows will be enabled and you can manage it with the PowerShell script.

Note: If you have Copilot for Microsoft 365 and would like your users to access it from Bing, Edge, or Windows, you will need to ensure Copilot is turned on with the PowerShell script. This will enable Copilot for Microsoft 365 in Bing.com, copilot.microsoft.com, Edge sidebar, Edge mobile app, Copilot in Windows, and the Copilot app. Microsoft recommends this for your users to get the most value out of Copilot for Microsoft 365.

What you need to do to prepare:

No action is needed to prepare for this change. You may want to notify your users about this change and update any relevant documentation as appropriate.

The PowerShell script to manage Copilot for Microsoft 365 in Bing, Edge, and Windows will be available from the following documentation after this change completes in late February 2024: Manage Microsoft Copilot for Microsoft 365 with the Copilot page | Microsoft Learn To learn more about Microsoft Search in Bing: Overview of Microsoft Search in Bing | Microsoft Learn


Optimize for Video setting for screensharing

[MC715695 · Published Feb 14, 2024] In Microsoft Teams, Microsoft is providing manual settings to optimize screen sharing for video clips by reducing lag and improving the quality of video playback when sharing video clips in Teams meetings.

This message is associated with Microsoft 365 Roadmap ID 93483.

When this will happen:

Targeted Release: Microsoft will begin rolling out early March 2024 and expect to complete by mid-March 2024.

Standard Release: Microsoft will begin rolling out mid-March 2024 and expect to complete by late March 2024.

How this will affect your organization: With the new feature you can manually optimize your screen sharing for video or motion content shared in Teams meetings. With this rollout, if automatic detection fails or is delayed, presenters can go to the Optimize for playing video setting on the Presenter toolbar overflow menu (the three-dot menu) to ensure their content is displayed as smoothly as possible.

Microsoft Teams Sharing Video Clips Improvements
Figure 5 – Microsoft Teams Sharing Video Clips Improvements

What you need to do to prepare:

No action is needed to prepare for this change. You may want to notify your users about this change and update any relevant documentation as appropriate.


Check out previous Microsoft Updates that Total Solutions has posted here -> Microsoft Updates Archives – Total Solutions Inc.