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

Starting in mid-July, for organizations that use vanity domains and their users are on the following version of clients they will experience functionality diminishing:

• Outlook for iOS versions prior to 4.2411,
• Outlook for Android versions before 4.2342,
• Outlook for Mac versions older than 16.73
• Windows Mail and Calendar applications

We encourage users to switch to the new Outlook for Windows, and update to the newest versions of Outlook on iOS, Android, and Mac. Our ongoing development efforts and advanced security measures will be focused on these updated platforms.

Starting in mid-August, for Outlook on the web and Outlook.com:

• If users are using an old browser, they will receive an error page, and prompt to get the newer version of browser to continue using Outlook on the web.
  • Internet Explorer
  • Microsoft Edge Legacy
  • New Microsoft Edge<=79
  • Chrome<=79
  • Safari <=13.1
  • Mozilla Firefox< =78
  • Opera <=76
• The light version of Outlook on the web will also be retired.

[When this will happen:]

For Outlook iOS, Android, Mac and Windows Mail and Calendar Application, we’ll be gradually rolling this out to customers in mid-July 2024, and the roll out will be completed by late September 2024.

For Outlook on the web, we’ll be gradually rolling this out to customers in mid-August 2024, and the roll out will be completed by late October 2024.

[How this will affect your organization:]

Once this change has rolled out legacy Outlook clients will no longer be supported.

For Outlook iOS, Android, Mac and Windows Mail and Calendar Application, users will no longer be able to send or receive new emails when this change is applied.

For Outlook on the web, IsOptimizedForAccessibility parameter will no longer be supported in Set-CASMailbox Cmdlet for Exchange Online User. Outlook on the Web latest supports all the accessibility features. We will no longer redirect to OWA light via this configuration. If users are still on the older browsers, they will see an error page.

[What you need to do to prepare:]

We recommend you upgrade your clients from legacy Outlook clients to the latest version of Outlook clients for the latest features and security protections.

Learn more

• Outlook on the web: Supported browsers for Outlook on the web and Outlook.com
• Windows Mail and Calendar Application: Outlook for Windows: The Future of Mail, Calendar, and People on Windows 11 – Microsoft Support
• Outlook iOS: Microsoft Outlook on the App Store (apple.com)
• Outlook Android: Microsoft Outlook – Apps on Google Play
• Outlook Mac: Microsoft Outlook on the Mac App Store (apple.com)

Use a new sensitivity label setting or protection with Double Key Encryption to prevent content within Word, Excel, PowerPoint, and Outlook from being sent to Microsoft for content analysis as a privacy control, even when these are stored in Microsoft’s cloud, such as SharePoint or OneDrive.

This helps your organization to optimize your data privacy needs on a per-content basis using the familiar configurations and end-user experiences available with Microsoft Purview. 

This message is associated with Microsoft 365 Roadmap ID 398991

[When this will happen:]

Public Preview: Available early June via Current Channel Preview v2406+

General Availability: Available late June/early July 2024 via Current Channel v2406+ in worldwide environments.

[How this will affect your organization:]

This new label setting is off by default. When a sensitivity label is configured with BlockContentAnalysisServices=True, files and emails with this label will not send content to Microsoft services for analysis.

If you’re already using Double Key Encryption in your organization, files and emails protected with DKE will automatically prevent content in use from being sent to analysis services.

[What you need to do to prepare:]

If your organization does not need to disable some connected experiences that analyze content in use, no action needed.

The sensitivity label configuration is not available in the Microsoft Purview portal or the Microsoft Purview compliance portal. You must use the PowerShell advanced setting BlockContentAnalysisServices with the Set-Label or New-Label cmdlet after you’ve connected to Security & Compliance PowerShell.

The sensitivity label capability requires the built-in labeling client for Microsoft Purview in Office apps; the label setting is not compatible with the legacy Azure Information Protection Add-in.

Learn more: Prevent some connected experiences that analyze content 

Starting July 10, 2024, the Stream (Classic) Tab feature will no longer be available in Teams Chat/Channel. This change is part of the retirement of Stream Classic.

[When this will happen:]

We will gradually roll out this change to customers in mid-July 2024, and we expect to complete by early August 2024.

[How this will affect your organization:]

You are receiving this message because our reporting indicates one or more users in your organization are using the Stream (Classic) Tab on chat/channel.

[What you need to do to prepare:]

This change will happen automatically by the specified date. No admin action is required. Please notify your users about this change, update relevant documentation as appropriate, and share.

Learn more: Stream integration with the Microsoft Teams app