Microsoft Roadmap, messagecenter en blogs updates van 26-06-2024

Coming soon to Microsoft Purview compliance portal: A new compliance boundary cmdlet Invoke-ComplianceSecurityFilterAction will be available as part of the Security & Compliance PowerShell. This cmdlet allows user to check if a given mailbox or site has the compliance boundary property value set. If the property is not set or if the object is in arbitration, compliance admins can use this cmdlet to assign the property value for the mailbox or site for compliance boundary to take effect.

This message is associated with Microsoft 365 Roadmap ID 397091 and 398451

[When this will happen:]

General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out mid-July 2024 and expect to complete by late August 2024.

[How this will affect your organization:]

Before this rollout: Admins had no single solution to check or set mailbox properties and arbitration status, requiring complex steps with Exchange PowerShell for different mailbox types.

After this rollout: This cmdlet will enhance your organization’s ability to manage compliance boundaries. It will be especially beneficial in situations where a Microsoft OneDrive site needs to be brought back into compliance following a user’s departure, or when an inactive mailbox is not correctly assigned. This cmdlet allows for the straightforward setting of the compliance boundary property, based on user input, to address these issues.

This new feature is off by default.

[What you need to do to prepare:]

This rollout will happen automatically by the specified date. To prepare for this update, we recommend reviewing the Compliance boundary cmdlet documentation at New-ComplianceSecurityFilter (ExchangePowerShell) | Microsoft Learn. Additionally, ensure that your compliance admins are informed about the upcoming changes and are ready to incorporate the cmdlet into your organization’s process such as departed employees to ensure compliance boundary stay in effect.

The Resources section on Microsoft Viva Connections mobile will show content from the recently revamped Resources section on Viva Connections desktop. The Resources section in Viva Connections is comprised of navigational links. If these links are created via in-app editing in Viva Connections, they will propagate to the Resources section in mobile as well. If no links have been added via in-app editing and Global Navigation is configured on the Home site, the Resources section on mobile will continue to show the navigational links from Global Navigation.

This message is associated with Microsoft 365 Roadmap ID 388369

[When this will happen:] 

General Availability (Worldwide): We will begin rolling out mid-July 2024 and expect to complete by late July 2024.

[How this will affect your organization:]

Navigational links created via in-app editing in the Viva Connections Resources section will now be consistent across endpoints.

For more information, visit Viva Connections resources.

This feature is available by default. 

[What you need to do to prepare:]

This rollout will happen automatically with no admin action required. You may want to notify your users about this change and update any relevant documentation as appropriate.

Microsoft is updating the default Microsoft Windows email and calendar applications, transitioning from Mail, Calendar, and People to the new Microsoft Outlook for Windows. 

If your accounts are supported in the new Outlook for Windows, you’ll see a toggle in the upper right corner of your application named Try the New Outlook. Selecting this toggle will download the new app and let you switch to new Outlook for Windows. 

This message is associated with Microsoft 365 Roadmap ID 399464

[When this will happen:] 

Public Preview: We will begin rolling out in late July 2024 and expect to complete roll out by early August 2024.

General Availability: We will begin rolling out in early August 2024 and expect to complete by early September 2024.

[How this will affect your organization:]

COM add-ins, which are available in classic Outlook for Windows, aren’t supported in new Outlook for Windows. However, Office web add-ins are supported in new Outlook for Windows. To learn more about COM and web add-ins, see Office Add-ins platform overview and Migrate from COM to web add-ins. 

To help facilitate the migration of users to web add-ins and avoid any disruption to their productivity, we curated a list of COM add-ins that have equivalent web add-ins that are available today. Review the full list of these add-ins.

When a user switches from classic Outlook to new Outlook for Windows, they go through a series of steps to help them get set up. As part of this onboarding process, a user can consent to install equivalent web add-ins from their existing COM add-ins from the curated list. 

If the user has a COM add-in from the curated list and selects Import Settings, the web add-in is installed in new Outlook for Windows. If the user selects Skip, no web add-ins equivalents are installed for the user. 

This feature is available for all users by default, including users blocked from the Store.

[What you need to do to prepare:]

To opt out of this feature, set the following Group Policy Object (GPO) setting to Enabled by mid-July 2024: Disable web add-in installation on migration to new Outlook for Windows. For more information, see Install web add-in counterparts of existing COM add-ins in new Outlook for Windows. 

These equivalent web add-ins are identified as user-installed add-ins. If you’re looking to deploy a web add-in as an admin-installed add-in, you can deploy it through Integrated Apps and hide the COM add-in using the following GPO to avoid duplication: Deactivate Outlook web add-ins whose equivalent COM or VSTO add-in is installed. For more information, see Make your Office Add-in compatible with an existing COM add-in.

The user can also directly install add-ins from the Store once they move to new Outlook for Windows. This feature only helps enable users find their existing add-in easily and avoid disruption to the work if an equivalent add-in is already available. 

Note: Users with EDU licenses assigned will not receive this change.

Coming soon: Microsoft Teams will automatically detect and hide inactive channels you have not interacted with recently. You can review the list of channels and unhide some or all of them. You can opt out of automatic hiding from Teams Settings or initiate the hiding process on demand. This message applies to Microsoft Teams for Desktop, web, and Mac.

This message is associated with Microsoft 365 Roadmap ID 325780.

[When this will happen:]

Targeted Release: We will begin rolling out mid-July 2024 and expect to complete by late July 2024.

General Availability (Worldwide): We will begin rolling out mid-August 2024 and expect to complete by mid-September 2024.

General Availability (GCC): We will begin rolling out late September 2024 and expect to complete by early October 2024.

General Availability (GCC High): We will begin rolling out early October 2024 and expect to complete by mid-October 2024.

General Availability (DoD): We will begin rolling out late October 2024 and expect to complete by late October 2024.

[How this will affect your organization:]

Before this rollout: Users had to manually hide inactive channels.

After this rollout: Teams will hide channels that have been inactive and notify the user with the message, “We’re hiding some inactive channels for you.” The user can select View changes to see the details (second screenshot):

The user can keep the channels hidden or show them again:

To initiate or stop channel hiding, go to Teams > Settings > Chats and channels > Hide inactive channels:

This feature is on by default and all Teams users on the affected platforms will have access to it.

[What you need to do to prepare:]

Admins need to be aware of this feature, but no additional action is needed. This rollout will happen automatically by the specified dates with no admin action required before the rollout. You may want to notify your users about this change and update any relevant documentation as appropriate.

• This update addresses an issue that affects Snipping Tool. When you use it to record videos on some PCs, the audio has distortions.
• This update addresses an issue that affects the touch keyboard. You cannot use it to enter special characters. This occurs when you use the Japanese 106 keyboard.
• This update addresses an issue that affects USB devices. Ejecting them using the Safely Remove Hardware option fails. This occurs when Task Manager is open.
• This update adds a new Game Pass recommendation card on the Settings home page. This home page shows on Home and Pro editions when you sign in to Windows using your Microsoft account.
• The show desktop button is on the taskbar again by default. To change this, right-click the taskbar and choose Taskbar settings. At the lower part of the page, you will find Taskbar behaviors.

• Windows 11, version 23H2: KB5039302
• Windows 11, version 22H2: KB5039302
• Windows 10, version 22H2: KB5039299