Microsoft Roadmap, messagecenter en blogs updates van 14-08-2024

Updated August 12, 2024: We have updated the rollout timelines and content below. Thank you for your patience.

App centric management (ACM) is on hold as of August 14, 2024 and will restart in mid-September (previously June). Your experience during this hold will fall under one of the following , with Phases defined in detail below.

• If your tenant has already been migrated to ACM, it will remain on ACM. The rest of this MC post is not applicable to your tenant.
• If your tenant fell under the Phase 1 criteria of using only the Global app permission policy and no custom app permission policies, it will resume auto migration in mid September.
• If you had started the migration wizard in Phase 2 and saved a draft of your progress with the Finish later option, you may continue and complete your migration.
• If you do not have a draft currently saved, you will not be able to access ACM migration until the roll out restarts.

What is in Phase 2?

• Migration wizard: a step-by-step guide to help you migrate the permission policies. You will be able to select which polities to migrate and designate users groups or individuals who should have access to the apps.
• Testing and Validation: before finalizing the migration, you will have the opportunity to test and export your staged changes. You can use this to make side-by-side comparison with your current setup, ensuring everything is perfect before you proceed.
• Duration: The migration process is designed to have no downtime for the end users and can take a few hours to complete. During the migration, your existing permission policies will remain in effect until the transition to app centric management completes.

Detailed documentation for the migration process is available at App centric management to manage user access to Teams apps – Microsoft Teams | Microsoft Learn.

App centric management introduces new admin settings to control who in the tenant can install Teams apps. First, admins can set a default value for new apps that are published to the Teams app store. Second, admins can manage apps for users, groups, or everyone in the organization. This feature replaces the existing app permission policies and provides admins with the ability to manage access to the app individually. The app permission policies for existing customers are migrated to maintain existing app availability in the tenant.

This message is associated with Microsoft 365 Roadmap ID 151829

[When this will happen:]

This feature will gradually roll out across three major phases.

Phase 1 (from late November 2023 to late September 2024 (previously late February) affects the tenants that use only the Global app permission policy and have no custom app permission policies. The app status from the permission policy and tenant settings will be migrated to preserve the admin intent. The migration will not affect the end users and their ability to use the apps. Admins may see the Manage apps page in a read-only mode for a short time.

Phase 2 (from mid to late September 2024 (previously July)) affects the tenants that use both global and custom app permission policies. This phase will let the admin choose to migrate to app centric management by following a migration process that will change the existing app permission policies to app assignments in the new app centric model. The admins will have the choice to modify the apps that are assigned using the custom permission policies to be accessible to groups, if they want.

Phase 3 (early 2025) applies to the tenants that skipped the migration in phase 1 or 2. These tenants will be migrated automatically in this phase. More details to come as a follow up MC post.

[How this will affect your organization:]

Starting with this release, you can:

1. Manage Teams apps for selected set of users, groups or all users in the organization.

2. Set the default value for new apps published to Teams app store for each of the app types: Microsoft, third-party and custom apps.

[What you need to do to prepare:]

No action needed for phase 1 tenants with Global permission policy only. More information will be provided for phase 2 and 3 tenants in a follow-up communication before launch.

Updated August 13, 2024: After further consideration, we have decided to not move forward with the rollout at this time. We will communicate via Message center when we are ready to proceed. We apologize for any inconvenience this may have caused.

Coming soon, Microsoft Purview Insider Risk Management will be rolling out a public preview of policy wizard enhancements.

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.

You can access the Insider Risk Management solution in the Microsoft Purview compliance portal. 

Learn more: Create and manage insider risk management policies | Microsoft Learn 

This message is associated with Microsoft 365 Roadmap ID 368825

[When this will happen:]

We will communicate via Message center when we are ready to proceed.

[How this will affect your organization:]

To enhance the user experience for editing and creating policies, we will be making improvements to the Trigger, Trigger threshold, Indicator threshold, and Summary pages of the policy wizard.

[What you need to do to prepare:]

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

Updated August 13, 2024: This change is being delayed until the first half of 2025 and we will provide an update, via Message center, on when the change will happen 3 months in advance. We apologize for the inconvenience.

We are pleased to announce that the global rollout of Conference mode to optimize Call queues in Microsoft Teams Phone is now complete. This optimization results in faster connection times to the agents. An additional optimization allows agents using the Microsoft Skype for Business client to receive calls from Call queues enabled with Conference mode.

We are in the process now of switching Call queues that use Transfer mode to Conference mode. 

[How this will affect your organization:]

You are receiving this message because our reporting indicates one or more of your Call queues has used transfer mode in the last 30 days.

[What you need to do to prepare:]

To benefit from these improvements if the change has not happened automatically, please modify Call queues to use Conference mode as soon as possible: In the Teams admin center, edit each Call queue by selecting the Call answering step, set the Conference mode switch to On and then submit the changes.

Learn more about Call queue configuration: Create a Call queue in Microsoft Teams – Microsoft Teams | Microsoft Learn

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

Coming soon: Microsoft Teams meeting organizers can make the list of breakout rooms visible to all meeting participants and allow them to choose which room to join. Enabling this setting in breakout rooms allows participants to move freely from one room to another, simplifying breakout room coordination for meeting organizers and participants. This message applies to Teams for Windows, Mac, and the web.

This message is associated with Microsoft 365 Roadmap ID 121269.

[When this will happen:]

Targeted Release: We will begin rolling out early October 2024 (previously late September) and expect to complete by mid-October 2024 (previously late October).

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

General Availability (GCC High, DoD): We will begin rolling out early November 2024 (previously late November) and expect to complete by late November 2024.

[How this will affect your organization:]

Before this rollout: Only the meeting organizer can assign meeting participants to breakout rooms. Participants cannot move between rooms.

After this rollout: Meeting participants can select their breakout rooms of choice if the meeting organizer selects this option during setup.

Organizers can look for the new feature under the breakout rooms panel when setting up breakout rooms:

This feature is on by default and accessible to all meeting participants on the affected platforms if enabled by meeting organizers.

[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 users about this change and update any relevant documentation.

You can now schedule a meeting or event directly from an email thread, using Schedule with Copilot in the new Outlook for Windows and Outlook on the web. 

This message is associated with Microsoft 365 Roadmap ID 372895

[When this will happen:]

General Availability: We will begin rolling out in mid-August 2024 and expect to complete by late August 2024. This applies to enterprise users with Copilot licenses.

[How this will affect your organization:]

Copilot users will be able to schedule events directly from an email thread by clicking on the new Schedule with Copilot button in the Outlook toolbar. Copilot then creates the meeting invitation for you by starting with the participants from the email conversation. It also drafts the meeting title, agenda, and a summary of the conversation so far. The original email thread will be added as an attachment. 

Users can review Copilot’s suggested agenda and summary. Once they insert it, they can edit it to add or change information before sending the invitation. 

Schedule with Copilot is available in the new Outlook for Windows and Outlook on the web. It is not yet available on Outlook for Mac or Outlook mobile apps.

Note: the toolbar may look different per tenant or user settings.

[What you need to do to prepare:]

There is nothing you need to do to prepare for this release. This feature is included for all Copilot licensed users in the new Outlook for Windows and Outlook on the web.

Review:

• Quickly create a meeting invitation from an email discussion in Outlook

Microsoft Outlook for iOS/Android supports two app configuration keys for controlling hyperlink behavior:

• com.microsoft.outlook.Settings.OpenLinks.UseSystemDefaultBrowser
• com.microsoft.outlook.Settings.OpenLinks.UserChangeAllowed

This message clarifies the intent and functionality of these configuration keys. Before rollout, we will update existing documentation to match this message.

[When this will happen:]

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

[How this will affect your organization:]

• com.microsoft.outlook.Settings.OpenLinks.UseSystemDefaultBrowser controls whether links open in the system browser (with Safari and Chrome as defaults for iOS and Android), and whether the user is prompted periodically to optionally install Microsoft Edge
• com.microsoft.outlook.Settings.OpenLinks.UserChangeAllowed controls whether the Open Links row appears in Outlook Settings and determines whether users can choose between the system default browser and Microsoft Edge.

Before this rollout, the interaction of these two keys was not fully documented, with potentially unexpected results. The week of September 15, 2024, we will update Outlook mobile for iOS/Android so the behavior with respect to these two policies match the behavior described in the table below:

Note: Behavior differs depending on whether Microsoft Edge is already installed on the mobile device.

[What you need to do to prepare:]

• If your environment matches row 1 or row 4 in the table, you do not need to prepare for this change except to review your configuration based on your organization’s current requirements.
• If your environment matches row 2 or row 3, we recommend reviewing all options and choosing the configuration that best matches your organization’s requirements before September 15, 2024.

Learn more: Deploying Outlook for iOS and Android app configuration settings in Exchange Online | 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 users about this change and update any relevant documentation.

Two new Microsoft Graph APIs will soon be generally available:

• update admin report settings
• get admin report settings

[When this will happen:]

General Availability (Worldwide, GCC): We began rolling out early August 2024 and expect to complete by mid-August 2024.

[How this will affect your organization:]

These two APIs help Global admins change how usernames, group names, and site names are displayed in the Microsoft 365 admin center based on their organization’s privacy practices without having to manually change the setting in Org settings > Services > Reports. User, group and site names are concealed by default. When this setting is changed, administrative roles and the report reader role will be able to see identifiable user-level information if they have access to user/group/site level information. Changing the setting in Org settings > Reports using the Graph API or Graph user interface is a logged event in the Microsoft 365 Compliance Center Audit log.

The update admin report setting API requires Global admin permissions. Learn more: Working with Microsoft 365 usage reports in Microsoft Graph – Microsoft Graph beta | Microsoft Learn.

This feature is accessible to all Global admins with the appropriate permissions.

The Data privacy control for Microsoft 365 admin center reports at Org settings > Services > Reports:

[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 users about this change and update any relevant documentation.

Learn more: adminReportSettings resource type – Microsoft Graph beta | Microsoft Learn

Coming soon for new Microsoft Outlook for Windows and the web: When focused on the folder pane, users will be able to press Ctrl+Y and the first letter of the folder name to quickly navigate to a folder.

1. If a user enters the same letter multiple times, the selection will jump to the next matching folder.
2. Users can enter all or part of specific folder names. For example: Press Ctrl+Y and enter “dele” to jump to the “Deleted Items” folder.

This message is associated with Microsoft 365 Roadmap ID 403108.

[When this will happen:]

General Availability (Worldwide): We began rolling out late July 2024 and expect to complete by late August 2024.

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

[How this will affect your organization:]

Before this rollout, users scroll to find the desired folders.

This feature is on by default and available to all users of Outlook for Windows and the web.

[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 users about this change and update any relevant documentation.

Learn more: Keyboard shortcuts for Outlook – Microsoft Support

The Manage what attendees see feature in Microsoft Teams helps organizers to easily deliver polished events by simplifying the attendee view and keeping the focus on participants who have been brought onscreen. With this rollout, we are enhancing Manage what attendees see with new intuitive controls to make it even simpler to produce an event and create a professional viewing experience for attendees. This message applies to Teams on Windows desktop and on the web.

[When this will happen:]

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

[How this will affect your organization:]

Before this rollout: The Manage what attendees see feature requires users to bring presenters on or off screen with a two-step process using the presenter’s context menu.

After this rollout: The Manage what attendees see feature enhancements will include new toggles to bring presenters on or off screen, live indicators, pinning, pagination, and a new fit-to-frame presenter layout in Manage screen in the left panel.

Any new meetings or events created after mid-September 2024 will receive the new Manage what attendees see feature.

This feature is on by default.

[What you need to do to prepare:]

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.

We recommend you review the updated Manage what attendees see in Teams meetings – Microsoft Support for a comprehensive overview of the feature and conduct a test session with the feature turned on to get acquainted with the new controls.

• This security update includes improvements that were a part of update KB5040527 (released July 23, 2024). 
• This update addresses an issue that affects BitLocker. A BitLocker recovery screen shows when you start up your device. This occurs after you install the July 9, 2024, update.
• This update addresses CVE-2024-38143. Because of this, the “Use my windows user account” check box is not available on the lock screen to connect to Wi-Fi.
• This update removes the NetJoinLegacyAccountReuse registry key. For more information refer to KB5020276 – Netjoin: Domain join hardening changes.

• Windows 11, version 23H2 and 22H2: KB5041585
• Windows 11, version 21H2: KB5041592
• Windows 10, version 22H2 and 21H2: KB5041580
• Windows 10 Enterprise LTSC 2019 and Windows Server 2019: KB5041578
• Windows 10 LTSB 2016 and Windows Server 2016: KB5041773
• Windows 10 LTSB 2015: KB5041782
• Windows Server 2022: KB5041160
• Windows Server 2012 R2: Monthly Rollup: KB5041828
• Windows Server 2012: Monthly Rollup: KB5041851
• Windows Server 2008 R2 Service Pack 1: Monthly Rollup: KB5041838 / Security Only: KB5041823
• Windows Server 2008 SP2: Monthly Rollup: KB5041850 / Security Only: KB5041847

• Windows Server, version 23H2
• Windows Server 2022
• Windows Server 2019
• Windows Server 2016
• Windows Server 2012 R2
• Windows Server 2012
• Windows Server 2008 R2 Service Pack 1
• Windows Server 2008 SP2

We've released updates to the following update channels for Microsoft 365 Apps:

• Current Channel
• Monthly Enterprise Channel
• Semi-Annual Enterprise Channel (Preview)
• Semi-Annual Enterprise Channel

[When this will happen:]

We'll be gradually rolling out these updates of Microsoft 365 Apps to users on those update channels starting August 13th, 2024 (PST).

[How this will affect your organization:]

If your Microsoft 365 Apps clients are configured to automatically update from the Office Content Delivery Network (CDN), then no action is required.

If you manage updates directly you can now download these latest updates and begin deployment.

[What you need to do to prepare:]

To get more details about these updates view the following release notes:

• Current Channel
• Monthly Enterprise Channel
• Semi-Annual Enterprise Channel (Preview)
• Semi-Annual Enterprise Channel