Microsoft Roadmap, messagecenter en blogs updates van 12-12-2024

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

Users will now have access to a quicker and easier method to search their Outlook Mobile contact list within the app. We are adding a search bar at the top of a user’s in app contact list that will allow users to type the name of a contact to easily find a contact. This search is limited only to the contacts within the Outlook Mobile app, and this feature does not search any device contacts that have not been synced with Outlook. 

This message is associated with Microsoft 365 Roadmap ID 135281

[When this will happen:]

Preview: We will begin rolling out mid-September 2023.

Worldwide: We will begin rolling out mid-October 2023 and expect to complete by late January 2025 (previously late November).

[How this will affect your organization:]

There are no added settings or training needed for you as an admin. This feature will work for all users who have access to and/or use contacts in Outlook Mobile. 

[What you need to do to prepare:]

There is nothing required to prepare.

Updated December 11, 2024: We have updated the rollout timelines below. Thank you for your patience.

Microsoft Teams users will soon be able to control how they get notified in meeting chats through RSVP to their meetings. When they decline a meeting, they will not receive notifications or see the chats in chat list; when they accept a meeting, they will receive notification for all new messages. This release of Microsoft Teams Meeting ID will be rolling out across Microsoft Teams Desktop, Mobile and Web and will provide an additional way for users to control their chat list by selecting which meetings they want to receive message updates from.

This message is associated with Microsoft 365 Roadmap ID 161739

[When this will happen:]

Targeted Release will begin rolling out mid-March 025 (previously mid-January and expect to complete by late March 2025 (previously late January). 

Worldwide will begin rolling out late March 2025 (previously mid-February) and expect to complete by early April 2025 (previously late February). 

GCC will begin rolling out late March 2025 (previously early March) and expect to complete by early April 2025 (previously mid-March). 

GCC High will begin rolling out early April 2025 (previously mid-March) and expect to complete by mid-April 2025 (previously late March). 

DoD will begin rolling out early April 2025 (previously late March) and expect to complete by mid-April 2025 (previously late March).

[How this will affect your organization:]

You will not receive notifications or see chats from meetings you declined. You will be able to set how you want to be notified for meetings you RSVP with Accept or Tentative from Microsoft Teams settings.

[What you need to do to prepare:]

You might want to notify your users about this new capability to control meeting chat notifications by RSVP to meetings. 

December 11, 2024 – Reminder: Users need to update their Webhook URLs by January 31, 2025, to ensure their notifications continue posting to Microsoft Teams. For more information on how to do this, please refer to the October 16th update below.

Updated October 16, 2024: Updated information related to Office 365 Connectors Retirement in Teams – Webhook URL Migration. Thank you for your patience.

 As shared in the last communication, we are publishing guidance for owners of webhook-based connectors to update their URLs with a new structure. To allow ample time for replacing URLs, connector owners will have until January 31, 2025, which is an extension from our previous deadline of December 31, 2024. See below for complete guidance.

Webhook-based connectors within the O365 Connectors service in Teams are transitioning to a new URL structure due to the implementation of further service hardening updates. During this transition, you may receive notifications to update your configured connector to use the new URL. We strongly recommend that you update your connector immediately to prevent any disruption to connector services. URLs for all webhook-based connectors must be updated by January 31, 2025 for the connectors to continue posting messages into Teams. Keep in mind the entire O365 Connectors service in Teams will be retired at the end of 2025, so consider moving your webhooks to the Workflows app within Teams to avoid conducting another migration. Documentation: Create incoming webhooks with Workflows for Microsoft Teams – Microsoft Support

[How this will affect your organization:]

This change is needed only for webhook-based Connectors such as Incoming Webhook and third-party connectors where a URL is provided for posting messages. The change is not required for polling-based connectors such as RSS.

To update webhook URLs for existing O365 Connectors, follow these steps: Manage Microsoft 365 connectors and custom connectors – Microsoft Teams | Microsoft Learn

1. Go to Manage Channel in a Teams channel, select Edit under the Connectors option, and select Configured section. Review the existing connections listed on this page.

2.Do one of the following to generate a new URL:

• For connectors that contain a webhook URL, select Manage and Update URL.
• For other types of connectors, remove the connector and recreate the connector configuration.

3. Replace the old URL with the new URL (or the new connection in the service that triggers the post). You’ll know the new URL is ready for you to copy when the Configure page shows a message that the URL is updated (“Url is up-to-date”).

[What you need to do to prepare:]

The below dates are still unchanged and were communicated in previous updates:

• Entire O365 Connector service in Teams will retire in December 2025.
• Developers will no longer be able to create new Office 365 Connectors from the Developer Portal starting August 15th, 2024.

Additional documentation:

Create incoming webhooks with Workflows for Microsoft Teams – Microsoft Support

Browse and add workflows in Microsoft Teams – Microsoft Support

Note about parity features for the Workflows app

We are currently developing a method for webhooks in the Workflow app to support the following scenarios and will share more details before March 30, 2025.

• Post messageCard formatted message payloads (so you do not have to reformat the payload to adaptive card)
• Post to private channels

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

In new Outlook for Windows and web, when single-clicking on an empty time slot on the calendar surface, the quick compose pop-up will no longer appear. Instead, you will be able to create an appointment by typing directly in the time slot on the calendar grid, just as you can in classic Outlook for Windows. There will be no change to double-click behavior; the full compose form will still open as it does today.

This message is associated with Microsoft 365 Roadmap ID 406948.

[When this will happen:]

Targeted Release: We will begin rolling out early December 2024 (previously early November) and expect to complete by late February 2025 (previously early January).

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

[How this will affect your organization:]

This may affect how users create appointments quickly on the calendar surface. We expect this to be a better experience, especially for those familiar with classic Outlook inline appointment creation.

This update 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.

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

We are rolling out enhanced app discovery for Microsoft Teams. This rollout allows users to easily discover and use apps that they have previously used in group chats, channels, and meetings, enabling users to consent to use the app everywhere in Teams with one click. This message applies to Teams on Windows and Mac desktops and to Teams on the web.

This message is associated with Microsoft 365 Roadmap ID 397089.

[When this will happen:]

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

[How this will affect your organization:]

In Teams, when one user installs an app to a group chat, channel, or meeting, others in the group can use it without installing the app. Before this rollout, it is not easy for others in the group to rediscover these apps for use everywhere in Teams.

After this rollout, users can more easily find and use apps they previously used in Teams, because these apps will appear at the top of the list of apps in Teams menus:

After this rollout, users will be able to find apps they used in a group experience, but did not install themselves. If users click such an app, a consent screen appears. If the user agrees, the app will be installed and be available everywhere in Teams, including group chats, channels, and meetings:

[What you need to do to prepare:]

Admins should ensure that their tenant’s app permission policies are configured to allow users to add and use apps in group experiences. No additional admin configuration is needed for this feature

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.

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

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 early January 2024 (previously late November) and expect to complete by late January (previously mid-December).

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

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

Coming soon to Microsoft Viva Engage (Yammer): We will update the audit log schema to include parameters that uniquely identify both the user performing an action (actor) and the user/object affected by that action (target).

After this rollout:

• The actor will be identified by their unique Microsoft Entra ID ObjectId, stored in the UserKey field.
• The target will be identified by a new parameter TargetObjectId that will also store the target’s Entra ID ObjectId.
• To improve transparency on changes to admin roles and other key scenarios, a new ModifiedProperties parameter will capture both the old and new values of modified fields.

These new parameters will be available for users with an E3 license.

[When this will happen:]

General Availability (Worldwide): We will begin rolling out mid-December 2024 (previously late November) and expected to complete by late December 2024 (previously mid-January 2025).

[How this will affect your organization:]

After this rollout, for admins querying audit logs in the Microsoft Purview compliance portal (Microsoft Purview compliance portal > System > Audit), the UserKey will represent the Entra ID ObjectId of the actor. If you are using Microsoft PowerShell commands or custom scripts, please ensure that you are retrieving the correct value for UserKey to identify the actor. Also, ensure any scripts that need to identify the target are using TargetObjectId.

Before the rollout, UserKey was populated with the target user’s Passport ID, so existing queries using this parameter may need to be updated. No Entra ID ObjectId was available to uniquely identify users (actor and target).

After the rollout: The UserKey will be mapped to the Entra ID ObjectId of the user performing the action. The new TargetObjectId parameter will capture the Entra ID ObjectId of the user affected by the action, and the ModifiedProperties field will hold the old and new values for any modified fields.

Field changes

As we apply these changes to the Viva Engage (Yammer) workload audit logs, the UserKey field will be updated immediately to reflect the Entra ID ObjectId of the actor in all audit logs. The new fields TargetObjectId and ModifiedProperties will only be populated for admin-specific audit logs and events. These include actions such as promoting or demoting users to Corporate Communicator, Network Admin, Verified Admin, Yammer Admin roles, as well as enabling or disabling Leadership Corner and setting or updating custom usage policies.

This change will be on for admins who have already enabled it. For everyone else, this change will be off by default and available for admins to configure.

[What you need to do to prepare:]

To ensure a smooth transition, we recommend notifying your users about this update and updating any relevant documentation to incorporate these changes.

This rollout will happen automatically by the specified date with no admin action required before the rollout. Review your current configuration to determine the impact for your organization.

Learn more: Search the audit log | Microsoft Learn

Track Viva Engage events in the Microsoft 365 audit log and with the Management Activity API | Microsoft Learn

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

Coming soon for Microsoft Teams admin center: For the existing Meeting chat control, we will add two new options that allow admins to disable meeting chat before and after a meeting, In-meeting only for everyone and In-meeting only except anonymous users.

This message applies to Teams for Windows desktops and Mac desktops, Teams on the web, and Teams for iOS/Android.

This message is associated with Microsoft 365 Roadmap ID 422808.

[When this will happen:]

Targeted Release: We will begin rolling out early March 2025 (previously early January) and expect to complete by mid-March 2025 (previously mid-January).

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

General Availability (GCC, GCC High): We will begin rolling out mid-March 2025 (previously early February) and expect to complete by late March 2025 (previously mid-February).

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

[How this will affect your organization:]

After this rollout, admins will find the two new options in the Teams admin center > Meetings > Meeting policies > Meeting engagement > Meeting chat.

Admins can select from five Meeting chat options:

• On for everyone
• On for everyone but anonymous users
• Off
• In-meeting only for everyone (new)
• In-meeting only except anonymous users (new)

Admins can select the In-meeting only options to disable the ability of meeting participants to send messages in the meeting chat before or after the meeting, for meetings organized by specific users in their tenant. When one of the In-meeting only options is selected, participants can read past chat history, but they can only send messages in the meeting chat while the meeting is active.

The new options will be available for admins to configure. This rollout will respect the options selected by admins before the rollout. To use the new options, admins must select one of them.

[What you need to do to prepare:]

This rollout will happen automatically by the specified date with no admin action required before the rollout. Review your current configuration to determine the impact for your organization. You may want to notify your users about this change and update any relevant documentation.

Learn more: Manage chat in Teams meetings – Microsoft Teams | Microsoft Learn (will be updated before rollout)

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

Coming soon to Microsoft Syntex pay-as-you-go service is a new prebuilt model that uses Optical Character Recognition (OCR) and AI to detect the primary language of the file, key-value pairs, tables, selection marks, and barcodes. As with other models, it can be configured to extract this information to specified library columns.

This message is associated with Microsoft 365 Roadmap ID 413430.

[When this will happen:]

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

[How this will affect your organization:]

Users will be able to easily configure and apply a model to detect import elements of information in the document, including the primary language of the file text and barcodes.

This is another prebuilt model, in addition to contracts, receipts, and invoices, and is available via the same service. If the prebuilt service is on, this new model will also appear in the menu.

Once enabled, users will be able to create, configure, and apply this model in the same manner as other prebuilt models.

In addition to extracting detected elements, this model can also detect the primary language of the file. This information can be extracted to a Detected language column when the model is applied to a library, which can then be used for other content processing, like document translation.

[What you need to do to prepare:]

After the feature has rolled out, you can manage its availability to your users in the Microsoft 365 admin center.

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 as appropriate.

Learn more:

Configure Microsoft Syntex for pay-as-you-go billing – Microsoft Syntex | Microsoft Learn 

Use a prebuilt model to extract information from simple documents in Microsoft Syntex | Microsoft Learn

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

Coming soon for Microsoft Teams: New DVR (digital video recording) functionality for all town halls. This new feature will allow town hall attendees on Windows desktop or the web to interact with a live streaming town hall in the same way they would interact with recorded content. DVR functionality in the town hall enables event attendees to pause and move forward or back in a town hall, navigate to any previous timestamp, and other abilities, making it more convenient to interact with a town hall more and easier to digest the content being presented. This feature is available for Teams town halls from all organizers, regardless of the license assigned to the organizer.

This message is associated with Microsoft 365 Roadmap ID 422804.

[When this will happen:]

Targeted Release: We will begin rolling out early February 2025 (previously early January) and expect to complete by mid-February 2025 (previously mid-January).

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

General Availability (GCC): We will begin rolling out late February 2025 (previously late January) and expect to complete by early March 2025 (previously early February)

[How this will affect your organization:]

After this rollout, the DVR controls will appear when attendees hover their mouse over the content being presented in the town hall. Attendees can:

• Pause, play, and skip 10 seconds forward or backward
• Control the volume of the content with the volume control
• Jump to any point in time, starting from the beginning of the event
• Catch up with the content and join the live event by selecting the Watch Live button next to the volume control

The DVR controls are at the bottom of the Teams window when the Q&A page is open on the right side:

We are committed to continuously improving the Microsoft Teams experience and are excited to bring this new capability to our customers.

This feature will be available 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 users about this change and update any relevant documentation.

Learn more: Plan for Teams town halls – Microsoft Teams | Microsoft Learn (will be updated before rollout)

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

Coming soon for Microsoft Purview Insider Risk Management: Admins will be able to increase the CPU and GPU device resource utilization limit for all devices uploading forensic evidence clips in their organization. After this rollout, forensic evidence will allow up to 31% CPU and GPU device resource utilization (compared to the prior maximum limit of 5%). This enhancement will give admins the option to reduce interruption in the recording and uploading of clips.

This message is associated with Microsoft 365 Roadmap ID 420940.

[When this will happen:]

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

[How this will affect your organization:]

In IRM, go to Forensic Evidence to review the new limits:

This change will be available by default for admins to configure if desired.

[What you need to do to prepare:]

This rollout will happen automatically by the specified date with no admin action required before the rollout. After rollout, the setting will default to the previous system defaults, but admins will have an option to adjust as appropriate. Before updating the setting, we recommend you review your current configuration to determine the impact for your organization.

Learn more: Manage insider risk management forensic evidence | Microsoft Learn

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

Coming soon for Microsoft Purview: Data Security Posture Management (DSPM) identifies vulnerable configurations across your critical data assets and allows for quick corrective actions. It combines insights from user and data risk in Purview solutions, offering a comprehensive view of insufficient controls to protect your data. Also, data security and compliance admins can use Microsoft Security Copilot’s summarization and natural language features embedded in DSPM. These capabilities expedite action and help analysts at all levels identify and address data security gaps efficiently.

This message is associated with Microsoft 365 Roadmap ID 420941.

[When this will happen:]

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

We will update this message later to add the plan for General Availability.

[How this will affect your organization:]

After you enable DSPM, it will automate a data security risk assessment of your tenant. The dashboard will be populated with a detailed report on your unprotected sensitive information, including its location and top-line insights into activities involving the data. Also, to help you mitigate the top data security risks in your tenant, we provide policy recommendations for implementing protective controls:

Data security administrators can leverage Security Copilot in DSPM to delve deeper into dashboard insights and conduct critical data security investigations. With Copilot, you can quickly uncover insights across various dimensions such as activities, files, devices, users, departments or regions, enabling you to manage your data security posture more effectively:

[What you need to do to prepare:]

Prerequisites to access Data Security Posture Management (DSPM)

• A Microsoft 365 E5 or Microsoft 365 E5 Compliance license.
• Opt in to DSPM in the Purview portal > Data Security Posture Management (preview). Alternatively, you can 1) enable DLP analytics at the Microsoft Purview portal > Data Loss Prevention > Settings > Data Loss Prevention settings > Analytics and 2) enable IRM analytics in the Purview portal > Insider Risk Management > Settings > Insider Risk Management settings > Analytics, which will then automatically enable DSPM.
  • Enable DLP analytics: Get started with data loss prevention analytics | Microsoft Learn
  • Enable IRM analytics: Enable analytics in insider risk management | Microsoft Learn
• Roles required: Access the DSPM dashboard with one of these roles: Entra compliance admin, Insider Risk Management admin, or Data security viewer.
  • Data security viewer is a view only role. If the DSPM dashboard is opted in, this role has the permission to view all insights.
  • Currently, any user that is configured to a Purview admin unit is not allowed to access the DSPM dashboard.
• To access Security Copilot on DSPM, you must first be onboarded to Security Copilot and have the data security viewer role. Learn more: Get started with Microsoft Copilot for Security | Microsoft Learn
• Enable the Purview plugin in Security Copilot. Learn more: Manage plugins in Security Copilot | Microsoft Learn
• [Optional] Opt in to sharing the prompts with Microsoft to improve this experience. Learn more: Privacy and data security in Microsoft Copilot for Security | Microsoft Learn

DSPM will be available by default to admins who meet the prerequisites.

This rollout will happen automatically by the specified date with no admin action required before the rollout. Review your current configuration to determine the impact for your organization. You may want to notify your users about this change and update any relevant documentation.

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

Coming soon to Microsoft Teams: Links to Microsoft Lists, Lists items, and Lists forms will display richer details such as title and path when shared in Teams chats and channels. This new feature will enhance collaboration by making it easier for users to recognize specific List link types, in addition to viewing the title and path. This message applies to Teams for Windows and Mac desktops.

This message is associated with Microsoft 365 Roadmap ID 419812.

[When this will happen:]

Targeted Release: We will begin rolling out early February 2025 (previously early January) and expect to complete by mid-February 2025 (previously mid-January).

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

[How this will affect your organization:]

With this update, new details will display in a Teams chat or channel for these links:

• For Lists links, a List icon and the name and path of the list will be displayed.
• For Lists item links, a List item icon, the title of a specific list item, and the path of the list will be displayed.
• For Lists form links, a List form icon, the title of the form, and directions for a user to fill out the form will be displayed.

A sender will be able to opt to provide permissions to view or edit the List, List item, or List form.

This feature will improve the efficiency of collaboration by reducing the need to switch between Teams and other applications to view or interact with list data.

This feature will be on by default.

A Lists link, a Lists item link, and a Lists form link in a Teams chat:

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

• Inform your users about this upcoming feature and how it can enhance their workflow.
• Ensure your Teams environment is updated to the latest version to take advantage of this new functionality.
• Review your organization’s policies and permissions related to sharing and accessing List data in Teams.

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

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

Coming soon: Intelligent recap for Microsoft Teams town halls and webinars, just like the intelligent recap for meetings. Event organizers, co-organizers, and presenters will be able to explore the meeting recording by speakers and topics and access AI-generated meeting notes, AI-generated tasks, and name mentions. A Teams Premium license or a Microsoft 365 Copilot license is required to use this feature. This message applies to Teams for Windows and Mac desktops.

This message is associated with Microsoft 365 Roadmap ID 371588.

[When this will happen:]

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

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

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

[How this will affect your organization:]

After this rollout, users in your tenant can turn on the recording or transcription to get intelligent recap for town hall and webinar event instances. After an event ends, the organizer, co-organizers, and presenters can go to the meeting thumbnail in the event chat and select the View recap button to access Recap page. Alternatively, they can go to the Recap tab in the event’s Chat tab or calendar invite.

Note: Additional improvements will be available in future releases, including recap notifications.

This feature will be available by default.

[What you need to do to prepare:]

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

Learn more: Meeting recap in Microsoft Teams – Microsoft Support (will be updated before rollout)

A new feature allows you to schedule messages in Microsoft Teams channels. This feature will help you plan and manage your communications more effectively.

This message is associated with Microsoft 365 Roadmap ID 467447.

[When this will happen:]

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

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

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

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

General Availability (DoD): We will begin rolling out early April 2025 and expect to complete by mid-April 2025.

[How this will affect your organization:]

Users will be able to schedule channels messages in Teams.

Key Features:

• Message Scheduling: Schedule messages to be posted at a specific date and time in any channel.
• Easy Access: Use the scheduling option directly from the message compose box.
• Flexibility: Edit or cancel scheduled messages before they are posted.

Note that this feature already exists for Teams chat and is new for Teams channels.

This update 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.

We are adding a new feature in the Microsoft 365 Copilot usage report to provide insights into the active usage of Microsoft Copilot agents built by your organization. A Microsoft 365 Copilot license is not required to view the reports. For more information, visit Who can view reports. 

This message is associated with Microsoft 365 Roadmap ID 410246.

[When this will happen:]

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

[How this will affect your organization:]

If you use the Microsoft 365 Copilot usage report in Microsoft 365 admin center, you will see new metrics for active agent users on the existing Usage tab, and a new tab called Agents showing the active agents built by your organization, which includes agents that were approved by admin and user-created agents.

The Microsoft 365 Copilot usage report displays the number of unique Microsoft 365 Copilot users in your org, who used agents built by your org, and summary and trend charts:

The Copilot report’s new Agents tab shows adoption and usage of agents built by your organization:

This change will be available 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 any admins that manage agents on the Integrated apps page about this feature and update any relevant documentation.

Learn more

• Microsoft 365 reports in the admin center – Microsoft 365 Copilot usage
• Microsoft 365 reports in the admin center – Microsoft 365 Copilot agent usage
• Declarative Agents for Microsoft 365 Copilot | Microsoft Learn

After this rollout, Microsoft Teams meeting organizers will have a new meeting option to enable and require unverified (aka anonymous) participants joining meetings to verify their email addresses with a one-time password (OTP) verification code before joining the meeting. Tenant admins will have a new meeting policy to manage and control this setting in the Teams admin center. This message applies to Teams on Windows desktop, Teams on Mac desktop, Teams on the web, and Teams for iOS/Android.

This message is associated with Microsoft 365 Roadmap ID 418125.

 [When this will happen:]

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

General Availability (Worldwide): We will begin rolling out late March 2025 and expect to complete by early April 2025.

[How this will affect your organization:]

Tenants where the Anonymous users can join a meeting setting is currently disabled will be affected by this update. In the Teams admin center, a meeting policy controls whether anonymous users can join meetings. If this setting is turned off, users without an MSA (Microsoft Account) or Microsoft Entra account are currently unable to join meetings. With the introduction of this new feature, we are enabling an additional option for unverified (anonymous) users to join meetings without requiring an MSA or Entra account.

This change will be available by default.

Admin controls: Admins will have a new meeting policy called Anonymous users can join a meeting after verifying by email code that complements the existing meeting policy where tenant admins already have the control to enable Anonymous users can join a meeting (unverified): 

When admins choose to turn on both the meeting policies for the users in the organizations, they leave the choice of requiring email verification to the meeting organizers via a new meeting option that will be available for them.

Meeting Organizer Controls: When scheduling meetings, meeting organizers will now have a new meeting option called Require unverified participants to verify their info before joining that will be set to default off if you have enabled unverified joins. Organizers can choose to require participants to verify themselves by turning on this meeting option.

Participant Experience: When organizers choose to require unverified participants from joining meetings, participants will be required to authenticate themselves when attempting to join the meeting. Participants can use credentials from a Microsoft work account, Microsoft school account, or personal Microsoft account for authentication. Participants without any of these Microsoft accounts will need to verify by entering their email address, and then participants will receive a one-time passcode for verification.

Participants who verify the same email address that the meeting invitation was sent to will be allowed to join the meeting directly if the Lobby bypass setting permits invited participants. Conversely, participants verifying with a different email address will be placed in the lobby and labeled as Email verified:

The Email verified tag and the email address participants entered for verification will be shown on the profile card of the participant in the lobby, meeting roster, and meeting chat:

[What you need to do to prepare:]

For tenants where the Anonymous users can join meetings option is disabled, admins should assess the impact of the email OTP verification feature and update the meeting policy settings accordingly to suit their organization’s requirements. This new feature introduces an additional way for unverified (anonymous) users to join meetings without needing an MSA or Entra account.

This rollout will happen automatically by the specified date with no admin action required before the rollout. 

Quickly get an AI summary of Microsoft Word, PPT, and PDF files that were shared in chat and channels on the Teams mobile app without leaving the flow of work. Users can tap the summary icon on the file and get a summary generated by AI. Now users can consume and comprehend the content without reading the entire document on a small mobile screen.

This message is associated with Microsoft 365 Roadmap ID 422318.

[When this will happen:]

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

[How this will affect your organization:]

All Word, PPT, and PDF files shared in chat and channels in the Teams mobile app will have an AI summary icon in the file chiclet. Users can tap the summary icon on the file chiclet to view the summary generated by AI. With this feature, users can consume and comprehend the content without reading the entire document. Users can close the screen once the summary is consumed.

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.

Organizations can use the unified Microsoft Purview portal to connect Purview to their ChatGPT Enterprise workspaces, enabling them to discover, collect, and store user interactions in the scope of Purview capabilities and policies.

With Purview solutions, organizations can effectively discover and govern these interactions. For instance, you can review all AI interactions and sensitive information detected in the Data Security Posture Management (DSPM) for AI solution. Also, you can use eDiscovery, Data Lifecycle Management (DLM), Communication Compliance (CC), and Insider Risk Management (IRM) solutions to govern this data.

This message is associated with Microsoft 365 Roadmap ID 401125.

[When this will happen:]

Public Preview: We will begin rolling out mid-December 2024 and expect to complete by mid-January 2025.

We will communicate the plan for General Availability in a future post. 

[How this will affect your organization:]

When this feature is available in the Purview portal, you can use the new connector in the Purview Data map called ChatGPT Enterprise to connect to your ChatGPT workspace. 

This change is available for configuration by default.

[What you need to do to prepare:]

To get started, you will need a Microsoft Azure account with an active subscription, an active Enterprise Purview account, and a ChatGPT Enterprise plan for your organization. This integration also requires you to have configured single sign-on of Microsoft Entra ID with your ChatGPT Enterprise workspace.

If you haven’t started using it yet, we recommend you familiarize yourself with the Purview Data map.

Learn more:

• Subscriptions, licenses, accounts, and tenants for Microsoft’s cloud offerings – Microsoft 365 Enterprise | Microsoft Learn
• How to upgrade from the free to enterprise version of Microsoft Purview | Microsoft Learn
• Scans and ingestion in Purview Data Map| Microsoft Learn
• Microsoft Purview Data Map supported data sources and file types | Microsoft Learn] 

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