Microsoft Roadmap, messagecenter en blogs updates van 24-10-2024

Updated October 22, 2024: We have updated the rollout timeline below. Thank you for your patience.

Coming soon: Admins can configure whether they want to expire insider risk levels in adaptive protection when a user’s alert is dismissed, or their case is resolved.

This message is associated with Microsoft 365 Roadmap ID 388736

[When this will happen:]

Public Preview: We will begin rolling out in early May 2024 and expect to complete by late June 2024.

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

[How this will affect your organization:]

With this new feature, an admin can configure whether they want to expire insider risk levels in adaptive protection when a user’s alert is dismissed, or their case is closed. Today, this expiration happens automatically.

Microsoft Purview Insider Risk Management correlates various signals to identify potential malicious or inadvertent insider risks, such as IP theft, data leakage, and security violations. Insider Risk Management enables customers to create policies based on their own internal policies, governance, and organizational requirements. Built with privacy by design, users are pseudonymized by default, and role-based access controls and audit logs are in place to help ensure user-level privacy. 

[What you need to do to prepare:]

With this update, admins will see a new option in the Risk levels tab for adaptive protection called Risk level expiration options. This setting is enabled by default, and admins can uncheck this box if they would prefer that risk levels do not expire even when a user’s alert is dismissed or their case is closed. 

Additional Resources: 

• Help dynamically mitigate risks with adaptive protection (preview) | Microsoft Learn  

Updated October 23, 2024: We have updated the rollout timeline below. Thank you for your patience.

In Microsoft Viva Learning, the updated Learner Completion Record bulk export is an extension of the existing feature to download Learner Completion records by Microsoft 365 user groups and security groups. Bulk export empowers enterprises to download learner records of multiple users at once using the Microsoft 365 user groups and security groups. 

This message is associated with Microsoft 365 Roadmap ID 334050

[When this will happen:]

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

[How this will affect your organization:]

This updated Learner Completion Record bulk export feature allows you to download learner records for multiple users at once using the Microsoft 365 and security groups.

[What you need to do to prepare:]

This rollout will happen automatically with no admin action required. You may want to update any relevant documentation as appropriate.

Updated October 23, 2024: We have updated the content. Thank you for your patience.

When joining a meeting in Teams Room on Windows or Android 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 late September 2024 (previously mid-September) and expect to complete by mid-November 2024 (previously late September).

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

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

Updated October 22, 2024: We have updated the content. Thank you for your patience.

This feature update expands how Microsoft Outlook for iOS and Android gives external recipient warnings.

[When this will happen:]

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

[How this will affect your organization:]

A new optional administrative setting (InternalDomains) allows your organization to configure a list of internal domains to inform the external recipients warning in Outlook for iOS and Android. If set, this list of domains will be used to make determinations for external recipient warnings rather than the MailTip service

This feature update is available by default.

[What you need to do to prepare:]

Manage the option to provide a list of external domains to provide external recipient MailTip warnings by Outlook for iOS and Android. For more information, see External recipients MailTip domain configuration.

You may want to notify your users about this change and update any relevant documentation as appropriate. 

Updated October 22, 2024: We have updated the rollout timeline below. Thank you for your patience.

Coming soon for Microsoft Outlook for iOS and Android: We will add support for choosing fonts while composing emails. We will also improve support for fonts while reading emails.

This message is associated with Microsoft 365 Roadmap ID 409969.

[When this will happen:]

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

[How this will affect your organization:]

When this update rolls out, users will be able to select fonts to use in emails, signatures, automatic replies, and calendar invitations:

[What you need to do to prepare:]

You might want to notify your users about this new capability and update your training and documentation as appropriate.

Updated October 22, 2024: The rollout of this feature is now complete, and all customers should have access to the new Windows Autopatch experience.

For customers who were previously using Autopatch, please note that the update management experience previously found under Devices > Windows Autopatch section moved to Devices > Windows Updates. Additionally, Autopatch groups can now be found under Tenant admin > Windows Autopatch > Autopatch groups. For more information, please see Windows Autopatch documentation | Microsoft Learn. 

Microsoft is set to make Windows Autopatch the one-stop shop for all things Windows enterprise update management. We’re simplifying the update management experience by unifying Windows Autopatch and Windows Update for Business deployment service (WUfB-DS) into one service so you can automate and deploy updates to devices seamlessly. 

[When this will happen:]

General Availability: The changes will take place beginning on mid-September 2024 and gradually rollout to all tenants by mid-October 2024.

[How this will affect your organization:]

With this change, we’re simplifying the experience to make it easier to find and use the update management features you need. Instead of having multiple tabs and menus within the Microsoft Intune admin center, you’ll see update management capabilities organized into three categories:

1. Windows Updates: Create and assign policies to control how and when Quality updates, Feature updates and Driver Updates are installed on your devices. See the Licensing section below.
2. Tenant Management: Use Autopatch groups to create and assign groups to organize your devices into different update rings, such as pilot, production, or test. You can use the Support requests blade to create tickets with Windows Autopatch if you need more assistance. See the Licensing section below.
3. Windows Autopatch reports: Access various reports to analyze the update performance and reliability of your devices and troubleshoot any issues. See the Licensing section below.

Licensing

• Existing customers will continue to use the same licenses for Windows Autopatch: Microsoft Intune, Entra ID Premium, and Microsoft 365 / Windows 11 Enterprise E3/E5, and Microsoft 365 F3. These rights extend to Windows 365 Enterprise. For more information, see Licensing prerequisites for existing Windows Autopatch customers. Feature(s) available: Windows Updates, Tenant Management, and Windows Autopatch reports.

Organizations with A3, A5, and Microsoft 365 Business Premium subscriptions will retain the license rights to use all Windows Update for Business deployment service (WUfB-DS) capabilities. New subscribers will also have rights to use Windows Update for Business deployment service. Feature(s) available: Windows Updates. We will continue to provide the same great functionality available today with Windows Update for Business under this new unified Windows Autopatch. Our goal is to simplify PC update management without limiting the functionality that exists today.

[What you need to do to prepare:]

You should prepare for these changes in the Microsoft Intune admin center and inform your team. If you have any questions or concerns, or need assistance, file a service request by visiting the Microsoft Intune admin center. Additional Information and details will also be included on (docs.microsoft.com) post feature release.

Updated October 23, 2024: The Microsoft Purview Message Encryption portal will undergo minor design updates to align with Purview branding. Organizations may need to update training and documentation accordingly.

Microsoft will be updating fonts, colors, controls, and more to align with Purview branding. These changes are designed to enhance the user experience without causing any disruptions.

We will be proceeding with the minor design updates on the portal (fonts, colors, controls and more). These changes are to align with Purview branding and should not disrupt users.

[When this will happen:]

General Availability (Worldwide, GCC): We will begin rolling out late October 2024 (previously mid-October) and expect to complete by late December 2024 (previously mid-December).

[How this affects your organization:]

Users will see minor design changes within the UI.

This isn’t the final or complete list, but here are some prominent changes that users will notice:

1. Removed the bottom button bar.

2. Moved the emoji button to the formatting bar.

3. Relocated the toggle formatting option button to the top bar.

4. Updated the insert table control to allow size entry.

[What you need to do to prepare:]

You may consider updating training and documentation as appropriate.

—Summary of original message—

The Microsoft Purview Message Encryption portal provides access to encrypted messages sent from your organization’s users to external recipients. The cloud.microsoft domain was provisioned in early 2023 to provide a unified, trusted, and dedicated DNS domain space to host Microsoft’s first-party authenticated SaaS products and experiences. With this rollout, selected Microsoft products and scenarios will transition to a similar static.microsoft domain, in parallel with the previous domains. As part of this transition, the design of the portal (fonts, colors, controls, and more) will be adjusted to align with Purview branding and domain change.

Updated October 22, 2024: We have updated the content. Thank you for your patience.

As mentioned in MC726113/MC674247, Google has deprecated Android device administrator management, continues to remove management capabilities, and no longer provides fixes or improvements. Due to these changes, Intune will be ending support for Android device administrator management on devices with access to Google Mobile Services (GMS) beginning December 31, 2024. Until that time, we will support device administrator management on devices running Android 14 and earlier. For more details, read the blog: https://aka.ms/Intune-Android-DA-blog.

[How this will affect your organization:]

After Intune ends support for Android device administrator, devices with access to GMS will be impacted in the following ways:

1. Intune will not make changes or updates to Android device administrator management, such as bug fixes, security fixes, or fixes to address changes in new Android versions.
2. Intune technical support will no longer support these devices.

[What you need to do to prepare:]

Stop enrolling devices into Android device administrator and migrate impacted devices to other management methods. You can check your Intune reporting to see which devices or users may be affected. Go to Devices > All devices and filter the OS column to Android (device administrator) to see the list of devices.

Read the blog, Microsoft Intune ending support for Android device administrator on devices with GMS in December 2024, for our recommended alternative Android device management methods and information about the impact to devices without access to GMS.

Updated October 22, 2024: We have updated the rollout timeline below. Thank you for your patience.

Coming soon to the Microsoft Purview compliance portal: To assist you in diagnosing issues encountered while using Microsoft Information Protection (MIP) and Data Loss Prevention (DLP), we will release a new experience where you can run diagnostics to help identify the root cause of issues and provide remediation options. Before this rollout, these diagnostics were only available as Microsoft PowerShell cmdlets.

This message is associated with Microsoft 365 Roadmap ID 418566.

[When this will happen:]

Public Preview: We will begin rolling out early December 2024 (previously late October) and expect to complete by late December 2024 (previously mid-November).

General Availability (Worldwide): We will begin rolling out mid-February 2025 (previously early January) and expect to complete by late February 2025 (previously mid-January).

[How this will affect your organization:]

After this rollout, you can troubleshoot issues at Purview compliance portal > Data Loss Prevention > Run diagnostics.

This new feature will be on by default.

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

Before rollout, we will update this post with revised documentation.

Microsoft Purview compliance portal

Improving interop between the new Microsoft Teams client and Skype for business

Currently when making or receiving a call in the new Microsoft Teams client while an existing Skype for Business (SfB) call is ongoing, the call in Skype for Business does not automatically go on hold. The reverse scenario has the same problem. 

[When this will happen:]

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

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

General Availability (GCC High):  early November 2024 and expect to complete by mid-November 2024.

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

[How this affects your organization:]

We have addressed this issue so that when the user is on a call in SfB and answers a call in Microsoft Teams the SfB call will go on hold. Similarly, if they are on a call in Teams and answer a call in SfB the Teams call will go on hold. The user must be using the new Microsoft Teams client version 24261.1100.3128.2662 or greater.

[What you can do to prepare:]

Once this feature is available it must be enabled following the steps below.

• The group policy registry key “Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\16.0\Lync\Enable21Interop”, DWORDis set to “0x01”
  
• The group policy registry key “Computer\HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Lync\EnableIPCForHoldResume”, DWORDis set to “0x01”

We shared in https://aka.ms/sharepoint/Copilotagents last month that SharePoint would have a new capability for creating and using Copilot agents. Users with M365 Copilot licenses will see a new Copilot action in the Suite Navigation bar where they will see the built-in Copilot scoped to the site they are on. They will also see entry points from the New menu on home and in their document libraries to create Copilot agents. These capabilities are available only if they already have create and edit permissions on the site or document library. They can also share a link to the Copilot agent with other users, and those users (with a Microsoft 365 Copilot license) will be able to chat with it.

This release does not include interacting with the Copilot agent in a Teams chat or meeting chat. It does not include the extension to Copilot Studio for advanced customizations or the Site owner abilities to approve agents and set a default agent for a specific site. These capabilities will be available later this year. 

This message is associated with Microsoft 365 Roadmap ID 416297

[When this will happen:]

Targeted release: We will begin rolling out late-October 2024 and expect to complete by early November 2024.

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

[How this will affect your organization:]

Users will be able to create and use Copilot agents in SharePoint.

[What you need to do to prepare:]

Here is the documentation to learn more about the capabilities.

Copilots in SharePoint Help & Learning https://support.microsoft.com/topic/44e981e7-dcef-4422-977d-967f3dcfe796 

Get started with Copilot agents in SharePoint https://support.microsoft.com/topic/69e2faf9-2c1e-4baa-8305-23e625021bcf 

Create and edit a Copilot agent https://support.microsoft.com/topic/d16c6ca1-a8e3-4096-af49-67e1cfdddd42 

Manage Copilot agents https://support.microsoft.com/topic/bcab837a-835c-4a1a-8ad4-d53a353c369f 

We’re changing the way Outlook for iOS authenticates users with the Authenticator mobile app integration to match Outlook for Android. Currently in Outlook for iOS users are required to tap a button called “Open Authenticator” to initiate the Authenticator app authentication flow. In Outlook for Android this flow opens automatically without requiring the user to tap a button. We will now be matching that behavior in iOS so the user no longer has to tap the “Open Authenticator” button.

[When this will happen:]

General Availability (Worldwide, GCC, GCC High, DoD) We will begin rolling out this change in late November 2024 and expect to complete by mid-December 2024.

[How this will affect your organization:]

You are receiving this message because our reporting indicates your organization may be using Outlook for iOS. To see how many users are currently using Outlook for iOS there are report instructions here: Microsoft 365 Reports in the admin center – Email apps usage

Users will no longer need to tap the “Open Authenticator” button to initiate Authenticator app based mobile authentication, when this change is implemented.

[What you need to do to prepare:]

When this change takes effect, users and admins will not need to do anything for your organization to take advantage of this behavior.

Information about device enrollment with Intune for iOS can be found here: Overview of Apple device enrollment in Microsoft Intune.

We’re making some changes to the ActiveSyncDeviceAccess rule DeviceOS parameters for Outlook on iOS.

Starting in mid-November, we will start supporting the operating system build number in addition to the operating system version number.

[When this will happen:]

General Availability (Worldwide, GCC, GCC High, DoD) We will roll out this change in mid-November 2024

[How this will affect your organization:]

You are receiving this message because users in your organization may be subject to ActiveSyncDeviceAccess rules on their Exchange mailbox.

Administrations will now be able to specify the iOS operating system build number with the DeviceOS parameter as “iOS X.X.X XXXXX” like “iOS 17.5.1 21F09”, when this change is implemented.

Administrations who have pre-existing ActiveSyncDeviceAccess rules will not be affected by this change. If you want to take advantage of this new capability you will need to update any existing rules.

[What you need to do to prepare:]

When this change takes effect, you will not need to do anything. If you want to take advantage of this functionality you need to update your ActiveSyncDeviceAccess rules or set new ones.

Review:

• New-ActiveSyncDeviceAccessRule

• Windows 11, version 24H2 improved update fundamentals
• Windows 11, version 24H2: What’s new for IT pros 
• How to get new experiences for Windows 11 

The Shifts Graph APIs will transition from beta to production. This change brings enhanced stability and reliability to the APIs, ensuring a seamless experience for developers and users.

This message is associated with Microsoft 365 Roadmap ID 422813.

[When this will happen:]

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

[How this will affect your organization:]

You may continue using the API endpoints in beta. However, we recommend migrating to the production endpoints.

To refer to a list of all production (v1.0) APIs, go to the following page and navigate to Teamwork and communications > Shift management: Microsoft Graph REST API v1.0 endpoint reference – Microsoft Graph v1.0 | Microsoft Learn

This update is available by default.

[What you need to do to prepare:]

To update Microsoft Graph APIs from beta to production, change your API calls from the beta endpoint to the v1.0 endpoint and thoroughly test your application to ensure compatibility. Check for any differences between the versions, and update any documentation accordingly.

• Contextual prompt starters at the beginning of a Copilot conversation.
• Follow-up suggested prompts to Copilot responses.
• The ability to discover plugins through suggested prompts.
• The ability to understand cases, conversation, and email context.
• Proactively generated insights.