Microsoft Roadmap, messagecenter en blogs updates van 17-07-2024

As mentioned in MC715413, in October 2024 Intune will be moving to support Android 10 and later for user-based management methods which includes:

• Android Enterprise personally-owned work profile
• Android Enterprise corporate owned work profile
• Android Enterprise fully managed
• Android Open Source Project (AOSP) user-based
• Android device administrator
• App protection policies (APP)
• App configuration policies (ACP) for managed apps

Moving forward, we will end support for one or two versions annually in October until we only support the latest four major versions of Android. You can learn more about this change by reading the blog: Intune moving to support Android 10 and later for user-based management methods in October 2024

Important: Userless methods of Android device management (Dedicated and AOSP userless) and Microsoft Teams certified Android devices will not be impacted by this change.

[How this will affect your organization:]

For user-based management methods (as listed above), Android devices running Android 9 or earlier will no longer be supported. For devices on unsupported Android OS versions:

• Intune technical support will no longer be provided.
• Intune will no longer make changes to address bugs or issues.
• New and existing features are not guaranteed to work. 

While Intune will not prevent enrollment or management of devices on unsupported Android OS versions, functionality is not guaranteed, and use is not recommended.

[What you need to do to prepare:]

Notify your helpdesk, if applicable, about this updated support statement. The following admin options are available to help warn or block users:

• Configure a conditional launch setting for APP with a minimum OS version requirement to warn and/or block users.
• Use a device compliance policy and set the action for noncompliance to send a message to users before marking them as noncompliant.
• Set enrollment restrictions to prevent enrollment on devices running older versions.

For more details, read the blog: Intune moving to support Android 10 and later for user-based management methods in October 2024

Starting on July 15 or soon after, we will begin migrating device configuration policies to the new, unified settings platform. Specifically, these are the profiles created by navigating to Devices > Configuration > Create new policy > Windows 10 and later > Templates in the Intune admin center.

The unified settings platform is the foundation of the settings catalog, which provides quick access to policy and settings. Additionally, it provides consistency across naming, tooltips, available values, and standardizes the “not configured” value for policy settings regardless of where you interact with the policy. 

More details on each template’s migration experience are highlighted in the blog: Support tip: Windows device configuration policies migrating to unified settings platform in Intune.

[How this will affect your organization:]

Our telemetry indicates you have device configuration profiles created. This migration will not impact your profiles, the configured settings and values will be brought over as they are currently saved. This will not impact the state of enforcement of policy on users’ devices.

Following the migration, you will observe a revised placement of some templates within the user interface. Certain templates will become exclusively configurable within the Settings catalog moving forward. For other templates, the next time the upgraded policy is edited, you will also notice a new policy editing experience, improved reporting and handling of setting values to “not configured.”

If you are interacting with device configuration profiles via the deviceManagement/deviceConfigurations Microsoft Graph API, you will be able to continue creating new policies, but they will later be migrated. Once migrated, the new policies will have new PolicyIDs and are created on the deviceManagement/configurationPolicies API. We recommend switching to the new graph endpoints for policy creation as soon as possible. 

Note: You may see a slight change in reporting numbers when these policies are migrated. Similar to when a policy is edited, reporting records of devices that have previously applied policy and reported the results but are no longer managed or checking in, will not appear in the new reports until they check in again.

[What you need to do to prepare:]

If you are using Microsoft Graph API for device configuration policies, we recommend updating to the new graph endpoints. Otherwise, no action is required, only awareness. You can learn more about each template’s migration experience in the blog: Support tip: Windows device configuration policies migrating to unified settings platform in Intune. 

Before this rollout, compliance admins can place Microsoft Purview eDiscovery legal holds on Microsoft Teams webinar and town hall data using Team’s ability to target SharePoint locations where Teams content is housed. Due to heightened security requirements and the need for specialized compliance support, we are moving legal holds in Teams from the SharePoint integration to a more direct integration with Purview.

[When this will happen:]

The more direct integration of Teams legal holds with Purview will begin July 31, 2024. Legal holds through SharePoint will not apply to any new Teams webinars or town hall meetings created after July 31, 2024, because newly created Teams town hall and webinar data will not reside in SharePoint. Legal holds on events created before July 31, 2024 will continue to work through SharePoint. Full support for Purview eDiscovery legal holds is anticipated by early 2025. Purview eDiscovery will continue to work for all events, even after July 31, 2025. Only eDiscovery legal hold will be affected by this integration.

[How this will affect your organization:]

after this rollout, legal hold through Microsoft Purview will be on by default and accessible to all admins with appropriate permissions.

[What you need to do to prepare:]

Learn more

Articles will be updated when legal hold and eDiscovery are available through Purview in early 2025:

• Learn about Microsoft Purview | Microsoft Learn
• Microsoft Purview eDiscovery solutions | Microsoft Learn

This rollout will happen automatically by the specified date with no admin action required before the rollout. You may want to notify your admins about this change and update any relevant documentation.

When joining a meeting in Teams Room on Windows with a companion device (laptop or mobile), in-room participants will be grouped under the room node. Participants must join through Proximity Join. This update includes additional UI elements to create visual clarity of the in-room participants who are together.

This message is associated with Microsoft 365 Roadmap ID 400702

[When this will happen:]

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

General Availability (GCC, GCC High, DoD): We will begin rolling out mid-September 2024 and expect to complete roll-out by end of September 2024. 

[How this will affect your organization:]

This update is available by default if the companion device has enabled the Bluetooth setting and the Teams Room device has any one of the following XML <SkypeSettings> configuration settings enabled:

• <BluetoothAdvertisementEnabled>true</BluetoothAdvertisementEnabled>
• <UltrasoundAdvertisementEnabled>true</UltrasoundAdvertisementEnabled>
• <RoomQRcodeEnabled>true</RoomQRcodeEnabled>

On the roster, in-room participants will automatically be grouped under the room node. The two scenarios in which in-room participants can be ungrouped from the room node are:

• Raised hand: For raised hand, we continue to follow the sequential order of raised hands. Therefore, in-room participants who use their companion device to raise their hand will be broken up and ordered accordingly.
• Role assignment: For changes in roles (Presenters/Attendees), in-room participants can be broken up and placed in the appropriate category on the roster.

In both scenarios, the room information will be listed below the participant’s name.

[What you need to do to prepare:]

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

You will now be able to select from additional file types to filter your lists of files in Microsoft OneDrive on the web.

[When this will happen:]

Targeted Release: We began rolling out early July 2024 and expect to complete by mid-July 2024.

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

[How this will affect your organization:]

You will see a new dropdown menu next to the filter pills in Home, Shared, People, Meetings, and Favorites views. You’ll be able to select from the following file types:

• OneNote
• Microsoft Lists
• Videos
• Loop
• Photos
• Whiteboard
• PowerBI

[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.

Coming soon to Experience insights (preview) in the Microsoft 365 admin center: The new Actions feature will enable you to track the actions you take to drive user engagement and success for Microsoft 365. You can measure the impact of your actions, providing insights into how each action correlates with changes in usage, NPS (Net Promoter Score), feedback, and help article views. This empowers you to make data-driven decisions and continuously improve your strategies for user engagement and satisfaction. Later this year, Actions will also support goal setting and goal progress tracking.

[When this will happen:]

Public Preview: We will begin rolling out late July 2024 and expect to complete by late September 2024.

[How this will affect your organization:]

Before the rollout: Admins were unable to automatically track user engagement actions and success for Microsoft 365.

After the rollout

Experience insights (preview) will be accessible by Global admin, Global reader, Reports reader, and User experience success manager roles.

For Global admin and Global readers: To access the new feature, go to the Microsoft 365 admin home page, and select Dashboard view and switch to Experience Insights (preview). Select Actions.

If you’re a member of the Reports reader or User experience success manager roles, after you sign in to the Microsoft 365 admin center, you will automatically go to the Experience insights (preview) dashboard page. Switch to Experience Insights (preview) and select Actions.

This feature is on by default and accessible to all users with the appropriate permissions.

Learn more about Experience insights: Microsoft 365 Experience insights dashboard – Microsoft 365 admin | Microsoft Learn

Access Actions from Experience insights:

Track and view your impact with Actions:

[What you need to do to prepare:]

This rollout will happen automatically by the specified date with no admin action required before the rollout. You may want to notify your admins about this change and update any relevant documentation as appropriate.

Additional resources

• Democratizing usage data in Microsoft 365 Admin Center 
• Insights that influence technology adoption

Based on customer feedback, we are introducing the ability to provide a meaningful name to the General channel in a new or existing team. The General channel can be renamed by the team owners to show up in the teams’ and channels’ list of all members in alphabetical order. 

This message is associated with Microsoft 365 Roadmap ID 395931

[When this will happen:]

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

General Availability

• Worldwide: We will begin rolling out mid-August 2024 and expect to complete by late August 2024.
• GCC: We will begin rolling out early September 2024 and expect to complete by mid-September 2024.
• GCC High: We will begin rolling out mid-September 2024 and expect to complete by late September 2024.
• DoD: We will begin rolling out mid-September 2024 and expect to complete by late September 2024.

[How this will affect your organization:]

You can encourage your users to provide a meaningful name to General channels in their teams. 

[What you need to do to prepare:]

You may consider updating your internal documentation to inform your users that this feature is now available. 

In Gallery view for Microsoft Teams meetings, a room video is optimized and larger in size to increase visibility of participants that are in a Teams Room. With this update, the room video tile will dynamically re-size based on people count to ensure adequate and equitable space is allocated in Gallery view. If there is only one participant in the room, the video tile will be the same size as another remote participant tile. If there is more than one participant in the room, the room video tile will remain optimized, at 4x the size of a remote participant. To determine the people count in rooms, Cloud IntelliFrame must be enabled or there must be a room camera that is capable of sending people count via Accessory Signaling Protocol (ASP).

This message is associated with Microsoft 365 Roadmap ID 400706.

[When this will happen:]

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

[How this will affect your organization:]

The updated Gallery view will provide remote participants a better experience with the room video participants. The below image exemplifies two room participants in a Teams meeting. Conf Room Ruby remains larger in size, as there are more than two participants in the room, while Conf Room Emerald has one participant in the room and is the same size as other remote participants.

This update is enabled by default, and admins have the ability to turn this off via the EnableRoomPeopleCount XML setting for Microsoft Teams Room. Turning this off will not send people count information for room video tile re-sizing.

[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.