Microsoft Roadmap, messagecenter and blogs updates from 06-12-2025

Updated December 5, 2025: We have updated the timeline. Thank you for your patience.

We’re introducing several enhancements to the modernized eDiscovery interface in Microsoft Purview to streamline workflows, improve usability, and provide greater administrative control. These updates include:

• Ability to delete searches
• Ability to delete exports created from searches
• Auto-population of the custodian field in review sets and exports
• Advanced indexing improvements, including indexing all Exchange items with attachments in scope
• A new tenant-level premium feature toggle to control eDiscovery case license toggle value during case creation.
• A new analytics process report for deeper insights into review set analytics (e.g., deduplication)
• Expanded search condition builder with support for logical operators (AND, OR, NEAR) in the keywords field
• Export packages to include user input export name for easier association with the export process
• Bulk import of data sources
• Ability to configure the maximum export package size, along with an updated default value.

These updates are designed to enhance the eDiscovery experience by offering more flexible, powerful tools and reducing administrative overhead.

This change is associated with Microsoft 365 Roadmap ID: 494160 

[When this will happen:]

General Availability (Worldwide/GCC/GCCH/DoD): Rollout will begin in late June 2025 and is expected to complete by late December 2025 (previously late November).

[How this will affect your organization:]

• The tenant-level premium toggle sets the default value for newly created cases, giving admins centralized control over premium settings without affecting existing cases.
• The ability to delete searches and direct exports introduces a change in lifecycle management, which may impact audit trails or collaboration workflows.
• Logical operators in the search condition builder will enhance query precision but may require updates to search strategies.
• Advanced indexing improvements will improve content discoverability, especially in complex or high-volume cases.

[What you can do to prepare:]

• Review and update internal documentation, training materials, and workflows to reflect these changes.
• Ensure your teams are aware of the new search and direct export deletion capability and its implications for audit and collaboration.
• Update search guidance to incorporate logical operators for more effective query construction.
• Evaluate how the new analytics report and indexing enhancements can support your review and prioritization processes.

[Compliance considerations:]

• Alters how existing customer data is processed, stored, or accessed: Yes – Advanced indexing improvement may affect how data is processed and accessed within eDiscovery.
• Modifies or disables Purview capabilities (eDiscovery, audit logging, etc.): Yes – The ability to delete searches and direct exports directly impact eDiscovery workflows and may affect audit logging.
• Alters how admins monitor/report on compliance activities: Yes – The new tenant level license toggle affects how admin control the use of eDiscovery premium features in their eDiscovery workflow. 
• Modifies how users access/export/delete/correct personal data (GDPR DSR): Maybe – The ability to delete searches and direct exports could affect how personal data is retained or accessed, depending on organizational policies and configurations.

Updated December 5, 2025: Task management and document creation capabilities, previously in public preview, are now generally available. This is associated with Roadmap ID 500701.

Microsoft Purview compliance roadmap for these skills:

• eDiscovery for tasks captured in Teams Meetings will begin rolling out in January 2026, and Data Lifecycle Management (DLM) support for tasks will be introduced in the first half of 2026.
• Admins can turn off these capabilities by setting the AllowRosterCreation flag to false. Set-PlannerConfiguration -AllowRosterCreation$:$false

Introduction

Meetings should be more productive—not more work. The Facilitator agent is now generally available for Microsoft 365 Copilot-licensed users. This AI-powered agent helps keep meetings focused, organized, and action-oriented by surfacing agendas, tracking progress, and capturing key highlights in real time. It supports collaboration through a conversational interface and integrates with tools like Planner, Word, Loop, and Teams Rooms.

This rollout includes general availability for core meeting skills and public preview for task management and document creation capabilities.

This message applies to Teams for Windows desktop, Mac desktop, the web, iOS, Android, and Microsoft Teams Rooms (MTR) devices and is associated with Roadmap IDs 478611, 499891, and 500701.

• Preview: Began in March 2025 
• General availability: We will begin rolling out late September and expect to complete by early October.

Who is affected: Microsoft 365 users with Copilot licenses. Facilitator is included with a Microsoft 365 Copilot subscription license and subject to available capacity.

What will happen:

• Facilitator agent will be available for scheduled meetings and ad-hoc discussions
• The Facilitator option is available by default in the Teams meeting experience for licensed users, meaning it appears in the meeting interface if the app is allowed in your tenant. However, it is not added to meetings automatically—meeting organizers or participants must choose to enable it before or during each meeting.
• Facilitator is shipped as an app and is allowed by default, respecting existing app permission policies
• If the Facilitator app is allowed in your tenant, it will appear in the meeting UX automatically
• Users can enable Facilitator before or during meetings

Screenshot 1: Copilot License User can turn on Facilitator in meeting


Screenshot 2: Users can see messages from Facilitator and new agenda tracker on the meeting window



• Facilitator does not require recording and can be used with or without transcription
• Visual timeline markers to track topics and time, with reminders at midway and wrap-up
• Collaborative, real-time notes editable by all participants via the Notes tab
• AI-powered Q&A from meeting and web content
• Task tracking integrated with Planner
• Instant document drafting in Word or Loop
• Enhanced Teams Rooms experience with chat, notes, and timers
• Mobile capture of ad-hoc discussions and action items
• Licensed users can interact with the agent by mentioning it in the chat, for example “@Facilitator add these topics to the agenda…”
  What you can do to prepare:
• No admin action is required
• Notify Copilot-licensed users about Facilitator availability
• Update internal documentation as needed
• Review meeting options to configure Facilitator without transcription:
  • Set Allow Copilot to Only during the meeting in Meeting Options
• Public documentation will be available at launch

Updated December 5, 2025: We have updated the timeline. Thank you for your patience.

[Introduction]

Microsoft is introducing new customization options for Microsoft 365 profile cards to help organizations enrich user profiles with relevant business information. This update enables the addition of properties such as Role, Division, Employee ID, Employee Number, and Cost Center, sourced from Microsoft Entra ID or external HR systems via Microsoft Graph connectors.

This update is associated with Microsoft 365 Roadmap ID 503111.

[When this will happen:]

[How this affects your organization:]

• Who is affected:
  • Admins managing Microsoft 365 user profiles and organizations using Outlook Web, New Outlook for Windows, Microsoft 365 Copilot app, or People Companion app.
  • Users who find the new properties once they are enabled.
• What will happen:
  • You can now add the following properties to profile cards:
    • Role
    • Division
    • Employee ID
    • Employee Number
    • Cost Center

    Screenshot 1: Profile card with new properties added

    

• Properties can be sourced from:
  • External systems via Microsoft Graph connectors
  • Microsoft Entra ID
• Properties are hidden by default and must be enabled in the Microsoft 365 admin center. Path: Settings > Org settings > People settings > Profile card > Contact info.
  • Screenshot 2: Settings for enabling the properties in M365 admin center

    

• Once enabled, properties will appear in the Contact Information tab of profile cards.
• Changes may take up to 24 hours to reflect across profile cards.

[What you can do to prepare:]

• Review which properties you want to display on profile cards.
• Ensure these properties are available in Microsoft Entra ID or your external HR system.
• Configure visibility in the Microsoft 365 admin center.
• Refer to the Microsoft Learn documentation for setup guidance.

Coming soon:

• Support for direct ingestion from SAP SuccessFactors and Workday.
• Future support for custom properties from third-party systems.

[Compliance considerations:]

Updated December 5, 2025: We have updated the timeline. Thank you for your patience.

Introduction

We’re introducing enhancements to OneDrive that simplify the process of managing files when employees leave your organization. These updates improve visibility, streamline bulk transfers, and help ensure important content remains accessible and shared appropriately.

This feature is associated with Microsoft 365 Roadmap ID 493946.

When this will happen

General Availability (Worldwide, GCC, GCCH, DoD): We will begin rolling out in mid-October and expect to complete by end of January 2026 (previously early December 2025).

How this affects your organization

Managing OneDrive content for departing employees is now more efficient. Key improvements include:

• Redesigned notifications: Account cleanup emails are now more prominent, reducing the chance of being overlooked.
• Improved filtering: New filters help managers quickly locate shared or important files.
• Bulk file transfer with preserved sharing: The “Move and keep sharing” feature allows multiple files to be transferred while retaining existing sharing permissions.
• Consolidated alerts: When six or more files are moved, collaborators receive a single streamlined notification.

These updates help ensure a smooth handover and reduce the risk of losing critical files.

When a user account is deleted, OneDrive access is automatically granted to the manager or designated secondary owner. The recipient receives an email notification with access details and information about the OneDrive retention period. Seven days before the retention period ends, a second reminder email is sent, stating that the OneDrive will be permanently deleted in seven days.

Steps to transfer files:

1. From the email, click View files to access the departing user’s OneDrive.
   
2. Use the Shared filter to view only shared files, or All to see everything.
3. Select files using the checkbox in the table header.
   
4. Click Move to, choose a destination, and check Keep sharing with the same people.



5. Click Move to again to complete the transfer.

Collaborators will receive a single notification once the move is complete:

What you can do to prepare

No admin action is required before rollout. You may want to:

• Inform managers and secondary owners about the new experience.
• Update internal documentation to reflect the new transfer process.
• Watch this guided walkthrough: Simplified file transfer for departing employees

Learn more: OneDrive retention and deletion – SharePoint in Microsoft 365 | Microsoft Learn

Compliance considerations

No compliance considerations identified, review as appropriate for your organization.

Updated December 4, 2025: We have updated the timeline. Thank you for your patience. 

[Introduction]

The Rate My Call survey is a feedback screen that the Teams client will occasionally present to users after their Teams call or meeting has completed. Currently, the rating presents 1-5 stars on the first page and a list of potential issues (called problem tokens) on the second page.

We will be rolling out a new streamlined feedback experience for Teams on Windows, Mac, and Web that presents the feedback on a single screen with a thumbs up / thumbs down rating system and problem tokens for the user to select, plus an area to provide details. In testing, we found higher feedback returns with this new design, and clearer insights into call quality issues.

Screenshot 1: New Rate My Call User Interface

[When this will happen:]

• Targeted Release: Rollout begins late January 2026 (previously early December 2025), completes by late January 2026 (previously mid-December 2025).

Who is affected: Users of Microsoft Teams on Windows desktop, Mac, and Web clients

What will happen:

• Users will see a new Rate My Call screen after calls and meetings
• The new screen includes:
  • Thumbs up / thumbs down rating
  • Optional problem tokens
  • Optional free-text field for additional details
• Feedback Rating values in Call Quality Dashboard (CQD) will change:
  • 5: Thumbs up / Good
  • 1: Thumbs down / Had issues
  • 0: Survey shown but not submitted
  • Null: Survey not shown
• Problem tokens will still be recorded even if a rating (thumbs up or down) is not submitted
• Admins may notice an increase in poor feedback metrics due to the new rating method; this does not reflect a decline in service quality

• Communicate this change to helpdesk and support staff
• Update internal documentation to reflect the new feedback format
• Monitor PCR (Poor Call Rate) telemetry until it stabilizes, then set your own threshold

[Compliance considerations:]

No compliance considerations identified, review as appropriate for your organization.

Q: Will a higher PCR mean calls are worse?
A: No. The new design captures more dissatisfied users by reporting a higher willingness to report poor calls. The increase is a measurement effect, not a quality regression.

Q: What is the new PCR target or threshold for your workstreams?
A: We cannot provide a fixed PCR threshold. Your action is to monitor your own PCR telemetry until it stabilizes (both volume and value relatively flat), then set your threshold. Stabilization may take weeks and once the data converges, you can then set your own.

Updated December 4, 2025: We have updated the content. Thank you for your patience. 

[Introduction]

Researcher and Analyst are part of the core default experience for M365 Copilot Chat and will now continue to be available to all users with a Copilot license—even when the ability to use Copilot agents is disabled for some or all users in the organization. This change reflects customer feedback and ensures uninterrupted access to foundational productivity tools.

Screenshot 1: Agents Settings for who can access agents in the organization

[When this will happen:]

General Availability begins December 15, 2025 and will begin to rollout over the next few weeks.

[How this affects your organization:]

• Who is affected: IT Admins that manage Copilot agent access in M365 Copilot Chat and M365 Copilot licensed users.
• What will happen:
• Researcher and Analyst will remain accessible in M365 Copilot Chat via tools, even when Copilot agents are disabled in Agents Settings for some or all users.
• When No users or Specific users/groups is selected in Agents Settings, Researcher and Analyst will not appear in the left navigation of M365 Copilot Chat for those users or @mention.
• Existing admin controls to block Researcher and Analyst agents will continue to function as expected as set by the admin in the Agent inventory.

Screenshot 2: Agent inventory

[What you can do to prepare:]

• Review who can access Copilot agents in your organization before December 15, 2025.
• Communicate this change to helpdesk and support teams to reduce confusion.
• Update internal documentation if you reference agent visibility or access controls.
• Refer to updated admin guidance here: Manage Microsoft 365 Copilot Agents – Microsoft 365 admin | Microsoft Learn

[Compliance considerations:]

No compliance considerations identified, review as appropriate for your organization.

Updated December 5, 2025: We have updated the timeline. Thank you for your patience. 

[Introduction:]

We’re updating how you manage user exclusions in Viva Insights and Copilot Analytics. Starting early December 2025, exclusions will be controlled through Viva Feature Access Management (VFAM) policies instead of the current list-based method in the Microsoft 365 admin center. This new approach lets admins create user-, group-, or tenant-level policies to exclude users from all Viva Insights measurement (Copilot Dashboard, Advanced Insights, Organizational Insights), using the same scalable policy framework as other Viva features.

[When this will happen:]

The VFAM-based exclusion feature will begin rolling out in early January 2026 (previously early December 2025). Exact rollout dates may vary by region.

[How this affects your organization:]

Who is affected: Admins managing Viva Insights and Copilot Analytics exclusions.

What will happen:

• Existing exclusion lists will be automatically migrated to VFAM; no admin action is required.
• Users already excluded will remain excluded across all Viva Insights experiences.
• VFAM will become the default and only method for managing exclusions.
• Admins will use VFAM policies to configure new exclusions at the user, group, or tenant level.
• The exclusion behavior remains unchanged; only the configuration method is updated.

Screenshot – Viva Feature Access Management feature for Exclusion management:

[What you can do to prepare:]

• No immediate action is required.
• Inform your Viva admins about the upcoming change.
• Once VFAM is live, review your exclusion settings in the Microsoft 365 admin center (under Viva Insights).
• Use the VFAM policy interface for any future updates.

Learn more about VFAM access: Control access to features in Microsoft 365 | Microsoft Viva | Microsoft Learn

[Compliance considerations:]

No compliance considerations identified, review as appropriate for your organization.

Autocorrect is coming to Microsoft Teams compose. Commonly misspelled words will now be automatically corrected while composing messages.

This message is associated with Roadmap ID 534487 and applies to Teams for Windows desktop and Teams for Mac desktop.

• Targeted Release: We will begin rolling out early December 2025 and expect to complete by mid-December 2025.
• General Availability (Worldwide): We will begin rolling out mid-January 2026 and expect to complete by late January 2026.
• General Availability (GCC High): We will begin rolling out mid-January 2026 and expect to complete by early February 2026.
• General Availability (DoD): We will begin rolling out early February 2026 and expect to complete by mid-February 2026.

Who is affected: All Microsoft Teams users composing messages in chat or channels.

What will happen:

• Commonly misspelled words will be automatically corrected during message composition.
• The feature is enabled by default; no admin configuration is required.
• Users can disable this feature by going to Settings > General > Editor spellcheck, then switching off the Correct words while typing toggle.
  

• No action is required to enable this feature.
• Consider updating internal documentation to reflect this new capability.
• Communicate this change to helpdesk staff to reduce potential support inquiries.

[Compliance considerations:]

No compliance considerations identified, review as appropriate for your organization.

Introduction

We’re updating the Public Preview of External Authentication Methods (EAM) to improve security, strengthen configuration validation, and prepare for General Availability planned for the end of March 2026. Tenants currently using EAM in Public Preview should review the changes below.

[When this will happen]

Registration enforcement begins December 8, 2025.

[How this affects your organization]

Who is affected: Tenants currently using External Authentication Methods (EAM) in Public Preview.

What will happen:

• Registration enforcement: Users must have an external authentication method registered to use EAM.
• In-line registration for new users:
• Existing users have been registered by Microsoft – which means there’s no action required.
• New users (any user joining your tenant after December 2, 2026) will be prompted during sign-in to complete in-line setup with your external provider.
• IT admins can register users on their behalf if needed.

[What you can do to prepare]

• Communicate to users that starting December 8, 2025, they may be prompted to configure an external method during sign-in if they don’t already have one.
• Review your external authentication method configurations to ensure they meet validation requirements.
• Update internal documentation, training materials, and helpdesk guidance.

Learn more:

Microsoft Entra multifactor authentication external method provider reference (Preview)

Manage an external authentication method in Microsoft Entra ID (Preview)

[Compliance considerations]

No compliance considerations identified, review as appropriate for your organization.

[Introduction]

We’re introducing automatic installation and updates for the Network Device Interface (NDI) in Microsoft Teams on macOS devices. NDI allows organizations to broadcast audio and video streams from Teams meetings to local networks, enabling advanced production scenarios such as live streaming or integrating with professional video systems. This enhancement eliminates manual steps, making it easier to use NDI in Teams.

[When this will happen:]

General Availability (Worldwide, GCC, GCCH, DoD): Rollout will begin early January 2026 and is expected to complete by mid-January 2026.

[How this affects your organization:]

• Who is affected: All Microsoft Teams users on macOS devices.
• What will happen:
  • NDI binaries will now install and update automatically on macOS devices.
  • No manual intervention is required for setup or updates.
  • This feature is enabled by default and respects existing Teams policies.
  • Users can broadcast audio and video streams from Teams to their local network without additional configuration.

[What you can do to prepare:]

• No action is required from admins or users.

[Compliance considerations:]

No compliance considerations identified, review as appropriate for your organization.

We’re introducing new Microsoft Secure Score recommendations for Microsoft Defender for Endpoint (MDE) to help organizations strengthen their security posture. These recommendations are designed to proactively block common attack techniques and improve endpoint protection.

Public Preview: Rollout will begin at the end of December 2025 and is expected to complete by the end of December 2025.

Who is affected: Admins managing Microsoft Defender for Endpoint and Microsoft Secure Score.

What will happen

• Customers in Public Preview will see new recommendations in Microsoft Secure Score.
• One example recommendation is: Disable NTLM authentication for Windows workstations.
• Secure Score will update based on the implementation of these recommendations.

• Review the new recommendations in Microsoft Secure Score once available.
• Complete the recommended actions to improve your organization’s security posture.
• Communicate these changes to your security and endpoint management teams.

Compliance considerations

No compliance considerations identified. Review as appropriate for your organization.

[Introduction]

We’re adding support for assigning Microsoft SharePoint Online sites to existing administrative units in Microsoft Purview Data Loss Prevention (DLP). When you assign a DLP policy for SharePoint to an administrative unit, the policy will apply only to sites within that unit. This enhancement helps organizations manage policies more granularly and align with administrative boundaries.

Learn more about Admin units: Administrative units in Microsoft Purview portal | Microsoft Learn

This message is associated with Microsoft 365 Roadmap ID 526797.

[When this will happen:]

General Availability (GCC, GCC High, DoD): Rollout begins mid-December 2025 and is expected to complete by late December 2025.

[How this affects your organization:]

• Who is affected: Admins managing DLP policies for SharePoint Online.
• What will happen:
  • You can assign SharePoint sites to administrative units and scope DLP policies accordingly.
  • This feature will be available by default; no opt-in required.
  • No impact to end-user workflows unless admins configure policies for specific units.

[What you can do to prepare:]

• No action is required before rollout; the feature will be enabled automatically.
• Review your current DLP configuration to determine if scoping policies by administrative unit is beneficial.
• To configure, go to Microsoft Purview compliance portal > Data loss prevention > Create policy > Assign Admin Units.



• Learn more: Support for adding SharePoint sites to Administrative Units

[Compliance considerations:]

No compliance considerations identified; review as appropriate for your organization.

Updated December 5, 2025: We have updated the timeline. Thank you for your patience. 

[Introduction]

Microsoft Defender Threat Intelligence (MDTI) is converging with Microsoft Defender and Microsoft Sentinel to deliver integrated threat intelligence capabilities directly within your SecOps environment. This change simplifies access to threat insights, improves detection and response workflows, and aligns with customer feedback for a unified experience.

[When this will happen]

Full convergence will be completed by August 1, 2026. New capabilities are available now, and as of August 2025, all MDTI data has been published via the free connector, with new Threat Analytics APIs replacing retired MDTI APIs.

[How this affects your organization]

Who is affected: Organizations using Microsoft Defender Threat Intelligence, Microsoft Defender, or Microsoft Sentinel.

What will happen:

• Threat Intelligence Library will be accessible via the Microsoft Defender portal, including exclusive threat reports, intel profiles, and Indicators of Compromise (IoCs) integrated into Threat Analytics.
• Enhanced Threat Analytics reports will include:
  • Indicators of Compromise (IoCs) embedded in reports.
  • MITRE ATT&CK mapping for tactics, techniques, and procedures.
  • Insights on targeted industries and actor origins.
  • Related intelligence and aliases for cross-referencing.
• IoCs will be linked to cases for Sentinel customers.
• After August 1, 2026, MDTI capabilities will require an active Microsoft Defender or Microsoft Sentinel license.

[What you can do to prepare]

• Plan your transition to Microsoft Defender or Microsoft Sentinel before August 1, 2026, to maintain uninterrupted access.
• Review licensing requirements for MDTI capabilities.
• Update internal documentation to reflect new Threat Analytics APIs and connector availability.

[Compliance considerations]

No compliance considerations identified, review as appropriate for your organization.

We’re introducing a new capability in Microsoft 365 Copilot chat that allows users to RSVP to meetings directly within the chat experience. This enhancement simplifies meeting management by enabling quick responses such as Accept, Decline, Tentative, Follow, or Remove canceled meetings—all without leaving Copilot chat.

General Availability (Worldwide, GCC and DoD): Rollout will begin early December 2025 and is expected to complete by late December 2025.

• Who is affected: Users with a Microsoft 365 Copilot license.
• What will happen:
  • Users can RSVP to meetings directly from Copilot chat:

  

  • Supported actions include Accept, Decline, Tentative, Follow, and Remove canceled meetings: 

  

  • This feature will be ON by default for all tenants.
  • No admin configuration is required; existing policies remain unchanged.

• No action is required from admins.
• Communicate this new capability to your helpdesk or end users if needed.

No compliance considerations identified, review as appropriate for your organization.

[Introduction]

To help organizations streamline compliance efforts across multi-cloud environments, Microsoft Purview Compliance Manager is introducing AI Powered Regulatory Templates. This feature enables customers to convert complex regulatory PDF documents into actionable controls, making it easier to create assessments, identify compliance gaps, and implement controls. This enhancement aligns with customer feedback requesting simplified regulatory mapping and automation.

This message is associated with Roadmap ID 523209.

[When this will happen:]

• Public Preview: Rollout begins mid-November 2025; expected to complete by end of November 2025.
• General Availability (Worldwide): Rollout begins mid-January 2026; expected to complete by late January 2026.

[How this affects your organization:]

• Who is affected:
  • Admins using Microsoft Purview Compliance Manager to manage regulatory compliance.
  • Organizations operating in multi-cloud environments seeking to automate compliance assessments.
• What will happen:
  • A new option will be available to convert regulatory PDF documents into templates.
  • These templates can be used to create assessments within Compliance Manager.
  • There is no impact to existing workflows or data processing.
  • The feature is additive and does not require changes to current configurations.
  • The feature will be available by default once rolled out.

[What you can do to prepare:]

• No action is required to enable this feature.
• Once available, you may:
  • Use the new template creation option to streamline assessment setup.
  • Review internal documentation if you maintain guidance on regulatory assessments.
  • Share this update with compliance teams to explore its benefits.

Learn more: Microsoft Purview Compliance Manager

[Compliance considerations:]

No compliance considerations identified, review as appropriate for your organization.

Updated December 5, 2025: We have paused GA release for this feature. Thank you for your patience.

Extend your sensitivity labels to specific or all subscriptions within Azure Storage, Azure SQL, Azure Cosmos DB, Azure Data Explorer, Azure Database for MySQL, Azure Database for PostgreSQL, Azure Databricks Unity Catalog, Azure SQL Managed Instance, Azure Synapse Analytics, Snowflake, Dataverse, and SQL Server via auto-labeling policy. Clearly define labeling conditions for data sources beyond M365 without fear of it interfering with existing M365 files configurations. 

This message is associated with Microsoft 365 Roadmap ID 429876.

[When this will happen:]

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

General Availability (Worldwide): We will announce via Message center when we are ready to proceed. 

[How this will affect your organization:]

You can create new auto-labeling policies for non-m365 workloads Server that allow you to specify specific data assets or ALL assets to be automatically labeled when the out-of-the-box sensitive information types are detected in a column or asset. After the auto-labeling policy is turned on, wait 15 minutes, and then rescan the scoped data assets. The assets will be labeled automatically.

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

After the rollout, these capabilities will no longer be available:

• The ability to extend labeling to assets in the Microsoft Purview Data Map (opt in)
  • Instead, you can select where to extend these assets in an auto-labeling policy
• Schematized data assets as an applicable label scope
  • You can select any label with the scope Files & other data assets for labeling in non-Microsoft 365 workloads
• Auto-labeling for schematized data assets in label definition
  • If you have configured Auto-labeling for schematized data assets in the label definition, you will need to reconfigure those conditions in an auto-labeling policy.

Tip: After you apply labeling to data assets, you can use protection policies to add access control settings associated with the label.

You will be able to select non-m365 workloads in the auto-labeling policy:

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

• Sensitivity Labels in the Microsoft Purview Data Map FAQ
• Learn about Microsoft Purview billing models | Microsoft Learn
• Data sources that connect to Microsoft Purview Data Map | Microsoft Learn