Microsoft Roadmap, messagecenter and blogs updates from 24-01-2026

Updated September 3, 2025:  the rollout has been postponed for GCC, GCCHigh, and DoD environments to a later date. We apologize for any inconvenience.

In Microsoft Purview | Insider Risk Management (IRM), policy tuning analysis provides admins with a real-time prediction of the number of users in a tenant that could potentially match a given set of policy conditions. After this rollout, policy tuning analysis will support insider risk policies that are scoped for priority content.

This message is associated with Microsoft 365 Roadmap ID 378409.

This message is associated with MC786326 (about the preview for this feature that started in May 2024).

[When this will happen:]

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

General Availability (GCC, GCCHigh, DoD): We will communicate via Message center when we are ready to proceed.

[How this will affect your organization:]

After this rollout, admins can use real-time analytics for policies scoped for priority content to help predict the number of users that could potentially match a given set of policy conditions. This feature enables admins to quickly adjust the selection of indicators and thresholds of activity occurrence so they can efficiently translate their insider risk strategies into pragmatic controls and keep from having too few or too many alerts.

1. In IRM, Navigate to Settings > Insider Risk Management > Analytics, turn on Analytics, and then select Save.

2. Create/edit a policy scoped to all users in the organization.

3. When you get to Content to prioritize in the policy wizard, select the priority content types you want to prioritize:

4. Select the items for each priority content type as applicable.

5. On the scoring page, select Get alerts only for activity that includes priority content:

6. Configure the rest of the policy as applicable and save it.

7. 1-2 days after the policy is saved, edit the policy again and navigate to the indicator thresholds page where insights on user activity containing the scoped priority content for each indicator will be visible under Choose your own thresholds:

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

This change will be available by default for admins to configure. To use this feature, admins will need to enable Analytics in Insider risk management > Settings. After Analytics is enabled and insights are populated, admins will be able to see real-time predictions in policies scoped to all users/groups and scored only for priority content.

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: Configure policy indicators in insider risk management | Microsoft Learn

Updated January 23, 2026: We are no longer moving forward with this feature. We apologize for any inconvenience. 

When creating a presentation in Copilot for Microsoft PowerPoint, users will be able to reference a Microsoft Teams meeting.

A Microsoft 365 Copilot license is required to use this feature.

This message applies to PowerPoint for Windows desktop, PowerPoint for Mac desktop, and PowerPoint on the web.

This message is associated with Microsoft 365 Roadmap ID 492979 (Windows desktop), Roadmap ID 492981 (Mac desktop), and Roadmap ID 492980 (web)

[When this will happen:]

General Availability (Worldwide): We are no longer moving forward with this feature. We apologize for any inconvenience. 

[How this will affect your organization:]

After this rollout, users will be able to reference Teams meetings when searching for files that Copilot can use to create a presentation. Select the Copilot icon from the PowerPoint ribbon and choose Create a presentation with file:

Search for a Teams meeting to reference it:

This feature will be available 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. Review your current configuration to assess the impact on your organization. You may want to notify your users about this change and update any relevant documentation.

Learn more: Create a new presentation with Copilot in PowerPoint – Microsoft Support (will be updated before rollout)

Updated January 23, 2026: We have updated the timeline. Thank you for your patience.

We’re expanding offline capabilities in the new Outlook for Windows. Users will soon be able to create, edit, and delete single calendar events even when not connected to the internet. This enhancement improves productivity and flexibility when working offline.

This change is associated with Microsoft 365 Roadmap ID: 490059

[When this will happen:]

Targeted Release: Rollout will begin in late September 2025 and is expected to complete by late October 2025.

General Availability (Worldwide): Rollout will begin in late October 2025 (previously mid-September) and is expected to complete by early February 2026 (previously mid-December 2025).

[How this will affect your organization:]

Users with offline mode enabled in the new Outlook for Windows will be able to:

• Create new single calendar events while offline.
• Edit or delete existing calendar events that have been previously synchronized within the offline timeframe set in Outlook settings.

Note: Support for recurring (series) events while offline is not currently available.

This functionality is controlled by the existing mailbox policy setting:

OWAMailboxPolicy -OfflineEnabledWin.

If this policy is set to True, offline calendar functionality will be available. If set to False, it will be disabled. This update does not change the default value of the policy.

[What you need to do to prepare:]

Ensure that offline mode is enabled for users who need this functionality. At the user level, this can be verified in the new Outlook under:

Settings > General > Offline

• Enable offline email, calendar, and people

Admins can manage this setting using the Set-OwaMailboxPolicy cmdlet. Learn more here: Set-OwaMailboxPolicy 

For end-user guidance, see: Work offline in Outlook

[Compliance considerations:]

• Does the change alter how existing customer data is processed, stored, or accessed? Yes – calendar data is now accessible and editable offline

Updated January 22, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

The new Designer editor integration in PowerPoint introduces a modern, intuitive image editing experience directly within your slides—eliminating the need to switch apps or interrupt your workflow. Whether you’re refining visuals for a pitch deck, enhancing marketing assets, or simply making your slides more engaging, the Designer editor enables fast, seamless image enhancements powered by AI.

Screenshot 1: Designer editor is now built into PowerPoint, so you can edit pictures without leaving the app. To get started, select a picture and then select Picture Format > Edit Picture, or right-click it and select Edit Picture.

Screenshot 2: Transform your visuals using AI-powered tools like Remove background, Auto enhance, and more—right from the canvas.

This message is associated with Microsoft 365 Roadmap ID 508530.

[When this will happen:]

• General Availability (Worldwide): Rollout will begin in mid-December 2025 (previously early December) and is expected to complete in early March 2026 (previously January).

[How this affects your organization:]

• Who is affected: All users of PowerPoint in Microsoft 365 across commercial and education tenants.
• What will happen:
  • Users will gain access to a new AI-powered image editing experience within PowerPoint.
  • The Designer editor will be available directly in the PowerPoint interface.
  • The following capabilities will be included:
    • Generative Erase:  Remove unwanted elements from images.
    • Generative Move: Reposition objects within an image.
    • Add Text: Insert text directly onto images.
    • Edit Text: Recognize existing text in an image and edit it.
    • Upscale: Improve image resolution for sharper visuals.
    • Background Removal: Remove backgrounds for clean designs.
    • Auto Enhance (Color Adjustment): Automatically improve color balance and vibrancy.
    • Effects: Apply creative filters and styles.
  • This feature cannot be turned off individually.
  • No changes to existing admin policies are required unless your organization chooses to manage availability.
  • AI usage limits for this feature:
    • Commercial users:
      • Copilot users have fair use access to all generative AI features.
      • Starter users have capacity-limited access; in-product messaging will notify users when limits are reached.
    • Consumer users:
      • Free and Basic MSA accounts: 15 credits/month for generative AI features.
      • Personal and Family subscribers: 60 credits/month.
      • Microsoft 365 Premium and Copilot Pro (while supported): fair use access.

[What you can do to prepare:]

• No action is required to enable the feature.
• Review internal documentation if you provide guidance on PowerPoint features.
• Communicate this change to helpdesk and support teams to prepare for potential user questions.
• If your organization wishes to manage availability:
  • Configure access through policy or permissions as needed.
• Be aware:
  • This feature uses AI capabilities to edit and enhance images in PowerPoint.
  • AI usage disclaimers are included within the editor interface for end users.

[Compliance considerations:]

Updated January 23, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

This feature empowers organizations with powerful insights into the adoption and usage of M365 Copilot Chat by users who are not licensed for M365 Copilot. Insights include usage trends, retention and usage intensity insights, app-level breakdowns, and filtering by organizational attributes.

Screenshot: Copilot chat adoption in Copilot Dashboard

This message is associated with Roadmap ID 501581.

[When this will happen:]

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

[How this affects your organization:]

Who is affected:

• Tenants with at least one Microsoft 365 Copilot license assigned.
• Admins and users enabled for Microsoft Copilot Dashboard.

What will happen:

• Feature will be enabled by default; no admin action required.
• New analytics cards and visualizations will appear in the Copilot Dashboard adoption tab.
• Insights will include:
  • Usage Trends Over Time: Visualize how Microsoft 365 Copilot Chat adoption evolves at your organization, by measuring the number of active users over time.
  • Adoption by Group: Compare adoption across organizational attributes, such as organization or job function to uncover where Copilot Chat is gaining traction and where further engagement may be needed.
  • Usage intensity and retention insights: Analyze how consistently users return to Copilot Chat and how many Copilot actions are being taken, with metrics on recurring usage and usage intensity.
  • App-Level Breakdowns: Identify which entry points and applications are driving Copilot Chat adoption.
  • Filtering and drilldown capabilities will be available for both Microsoft 365 Copilot Chat and Microsoft 365 Copilot views on the adoption and impact tabs.
  • Filtering and Drilldown: Filter by org attributes to explore adoption patterns, enabling Copilot Dashboard users to tailor their change management and support approaches for maximum impact.

Administrator Controls:

Global administrators, Viva Insights Administrators, and AI administrators will continue to have the following controls:  

• Create a policy for the Microsoft 365 Copilot Chat in Copilot Dashboard feature through Viva Feature Access Management (VFAM) in Microsoft Admin Center or PowerShell.
• Create a policy for access to the Viva Insights web app through Viva Feature Access Management (VFAM) in Microsoft Admin Center or PowerShell. 
• Exclude certain users or groups of users of Microsoft 365 Copilot chat from being included in the aggregated insights through the exclusion feature. 

Learn more: 

• Manage access to Viva Insights web app for individual users and groups in Microsoft 365 admin center
• Control access to features in Microsoft 365

[What you can do to prepare:]

• Read the Microsoft announcement regarding Microsoft 365 Copilot Chat.
• Review and assess the impact on your organization.
• Update training and documentation as appropriate.
• No additional configuration is required; metrics will be enabled by default.

[Compliance considerations:]

Updated January 23, 2026: We are updating this post as a reminder. Thank you for your patience. 

[Introduction]

We’re retiring the Featured Links capability on the SharePoint Start Page due to low adoption. This change helps streamline SharePoint experiences and reduce complexity for admins and end users. Alternative options, such as global navigation links or Resources in Viva Connections, provide more consistent ways to highlight important content.

Screenshot: The Featured Links option set for retirement appears at the bottom left in this image.

[When this will happen:]

General Availability (Worldwide, GCC, GCC High, DoD): Retirement begins early March 2026 and will complete by late June 2026.

[How this affects your organization:]

Who is affected: All organizations using Featured Links on the SharePoint Start Page or SharePoint mobile app.

What will happen:

• Admins will no longer be able to create, edit, update, or access Featured Links.
• Existing Featured Links will be removed from the SharePoint Start Page and SharePoint mobile app.
• No impact to other SharePoint navigation features or Viva Connections resources.

[What you can do to prepare:]

• Review any existing Featured Links and plan alternative navigation options.
• Consider using global navigation links or Resources in Viva Connections to highlight important sites and content.
• Communicate this change to helpdesk and SharePoint site owners.
• Update internal documentation if it references Featured Links.

Learn more: Add featured links to the SharePoint start page

[Compliance considerations:]

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

Updated January 23, 2026: We have updated the timeline. Thank you for your patience. 

To support broader reporting needs and customer feedback, the Queues app will soon allow users to view up to 45 days of historical data for call queues, auto attendants, and agents. This update expands reporting options without changing how users access or create reports.

This message is associated with Microsoft 365 Roadmap ID 547825.

[When this will happen]

Targeted Release: We will begin rolling out in mid-February 2026 and expect to complete by late February 2026.

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

[How this affects your organization]

Who is affected:

• Users with access to historical reports in the Queues app.

What will happen:

• Users can view up to 45 days of historical data.
• The default 7-day range remains unchanged.
• No changes to report access, permissions, or workflows.

[What you can do to prepare]

• No action is required.
• Optional: Inform users of the expanded range and update internal documentation.
• Learn more about historical reporting: Auto attendant and Call queue historical reports | Microsoft Teams | Microsoft Learn.

[Compliance considerations]

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

[Introduction]

We’re adding a new preconfigured quick policy template in Insider Risk Management to help detect potential data theft from Microsoft Fabric and other non-Microsoft 365 cloud storage services, including Box, Dropbox, Google Drive, Azure, and Amazon Web Services (AWS). This template helps admins create scenario-specific policies with minimal configuration, enabling faster and more consistent onboarding.

This message is associated with Microsoft 365 Roadmap ID 543244.

[When this will happen]

General Availability (Worldwide): We will begin rolling out in late February 2026 and expect to complete by late February 2026.

[How this affects your organization]

Who is affected:

• Insider Risk Management admins with permissions to create and manage policies
• Organizations using Microsoft Fabric or non-Microsoft 365 cloud storage providers (Box, Dropbox, Google Drive, Azure, AWS)

What will happen:

• A new quik policy template will appear in Insider Risk Management under Policies > Create policy.
• Admins can use the template to detect potential data theft activities performed by:
  • Users leaving the organization, or
  • Users whose accounts have been deleted in Microsoft Entra ID
• The template supports monitoring across Microsoft Fabric and multiple third‑party cloud sources.
• Policies created with this template require minimal configuration to get started.
• Additional tuning may be needed after deployment to optimize alert volume for your environment.
• This feature is not enabled by default; admins must opt in by creating the policy.

[What you can do to prepare]

• Review your Insider Risk Management role permissions to ensure appropriate admin access.
• When available, create the new quick policy from Microsoft Purview > Insider Risk Management > Policies > Create policy.
• After deployment, evaluate alert volume and adjust thresholds or settings as needed.
• If your organization uses cloud apps such as Box, Dropbox, Google Drive, Azure, AWS, or Microsoft Fabric, confirm the relevant connectors and integrations are enabled.
• For detailed guidance, review: Create and manage Insider Risk Management policies | Microsoft Learn

[Compliance considerations]

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

[Introduction]

We’re adding a new way for Microsoft Purview administrators to export adaptive scope members using PowerShell. Today, admins can review current and historical membership in adaptive scopes through the Purview portal. Based on customer feedback, we are introducing a PowerShell cmdlet that offers more flexibility—enabling automated exports, offline analysis, and the ability to resume exports if an operation is interrupted.

[When this will happen]

General Availability (Worldwide, GCC, GCCH, and DoD): Rollout began and will be completed within January 2026.

[How this affects your organization]

Who is affected:

• Administrators who manage Microsoft Purview Data Lifecycle Management, Microsoft Purview Communication Compliance
• Organizations that export adaptive scope membership lists for compliance, reporting, or operational review

What will happen:

• A new PowerShell cmdlet will be available to export adaptive scope members.
• Admins can continue using the Microsoft Purview portal; no existing workflows or UI experiences will change.
• The PowerShell cmdlet offers:
  • Granular control over export parameters
  • Ability to automate export scenarios using scripts or scheduled tasks
  • Ability to resume an interrupted export operation
• The feature will be available by default for all tenants.
• There will be no user impact.

[What you can do to prepare]

No action is required to prepare for this change.

If you plan to use the PowerShell option after it becomes available, you may want to:

• Review or update internal scripts that manage adaptive scopes.
• Inform your compliance or security operations teams about the new export method.

Learn more: Get-AdaptiveScopeMembers | policy-and-compliance-retention | Exchange PowerShell | Microsoft Learn

[Compliance considerations]

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

[Introduction]

To help provide additional transparency about what content has been generated or altered by using AI in Microsoft 365, Microsoft is providing you with a policy setting that visually designates when content, such as video or audio content, is generated or altered by using AI. This policy setting controls your organization’s option to add a visual or audio watermark to video and audio content that your users generate or alter by using AI in Microsoft 365.

To turn on watermarks for video and audio content that your users generate or alter by using AI in Microsoft 365, you need to use the “Include a watermark when content from Microsoft 365 is generated or altered by AI” policy. This policy is available only in Cloud Policy service for Microsoft 365. 

Note: Watermarks are not turned on unless you set the policy to Enabled. Your organization is always responsible for following the Microsoft Enterprise AI Services Code of Conduct, including not generating or sharing deceptive AI content. 

This change is associated with Microsoft 365 Roadmap ID: 547831.

[When this will happen]

General Availability (Worldwide): We anticipate that this policy will be available in Cloud Policy by the second half of February 2026.

[How this will affect your organization]

Users that generate or alter video and audio content by using AI in Microsoft 365

What will happen

If you set the “Include a watermark when content from Microsoft 365 is generated or altered by AI” policy to Enabled in Cloud Policy, a visual or audio watermark is added to video and audio content that is generated or altered by using AI in Microsoft 365. Here are two examples:

• A visual watermark is added to a video generated with Clipchamp.
• An audio watermark is added to an audio overview generated by Copilot from a Word document.

• This policy doesn’t affect images generated or altered by using AI in Microsoft 365.
• Instead, your users will be able to turn on watermarks for images by going to Settings & Privacy > Privacy at https://myaccount.microsoft.com. We anticipate this capability will be available in the second half of February 2026. 

[What you need to do to prepare]

[Introduction]

Starting in March 2026, Microsoft Entra ID will introduce passkey profiles and synced passkeys to General Availability (GA). This update allows administrators to opt in to a new passkey profiles experience that supports group-based passkey configurations and introduces a new passkeyType property.

The passkeyType property enables admins to configure:

• Device-bound passkeys
• Synced passkeys
• Both

If a tenant does not opt in to passkey profiles during the initial rollout window, the new schema will be automatically enabled at the date range specified below. When this occurs: 

• Existing Passkey (FIDO2) authentication method configurations will be moved into a Default passkey profile. 
• The passkeyType value will be set based on the tenant’s current attestation settings.
• For tenants that have synced passkeys enabled, Microsoft-managed registration campaigns will update to target passkeys.

[When this will happen]

• General Availability (Worldwide): Rollout begins in early March 2026 and is expected to complete by late March 2026.
  • Automatic enablement for tenants that have not yet opted in (Worldwide): Rollout begins in early April 2026 and is expected to complete by late May 2026.
• General Availability (GCC, GCC High, and DoD): Rollout begins in early April 2026 and is expected to complete by late April 2026.
  • Automatic enablement for tenants that have not yet opted in (GCC, GCC High, and DoD): Rollout begins in early June 2026 and is expected to complete by late June 2026. 

[How this affects your organization]

Who is affected: All Microsoft Entra ID tenants

What will happen:

If you have not opted in to passkey profiles by your automatic enablement period, your tenant will be migrated to passkey profiles.

• Your existing Passkey (FIDO2) configurations will be migrated into a Default passkey profile
• New passkeyType property will be auto-populated
  • If enforce attestation is enabled, then device-bound allowed
  • If enforce attestation is disabled, then device-bound and synced allowed
• Any existing key restrictions will remain intact
• Any existing user targets will be assigned to the Default passkey profile

[Registration Campaign behavior (Microsoft-managed campaigns only)]

• For tenants where synced passkeys are enabled, if your registration campaign is set to Microsoft-managed: 
  • The targeted authentication method will be updated from Microsoft Authenticator to passkeys.
  • The default user targeting will be updated from voice call or text message users to all multifactor authentication (MFA) capable users. 
  • The settings Limited number of snoozes and Days allowed to snooze will no longer be configurable. These will be set to allow unlimited snoozes with a one-day reminder cadence.

[What you can do to prepare]

If you want a configuration different from the migration defaults, review the timeline above and opt in to passkey profiles before your tenant’s automatic enablement window begins. Then configure the Default passkey profile’s passkeyType to your preferred values.

We also recommend:

• Review your registration campaign configuration, especially if its set to Microsoft-managed. If you want synced passkeys enabled in your tenant but do not want registration campaign to target passkeys, you can: 
  • Switch the registration campaign state to Enabled and continue targeting Microsoft Authenticator, or 
  • Set the registration campaign state to Disabled.
• Update runbooks and help content so your help desk and end users understand any changes in passkey availability or behavior. 

Learn more:

• How to Enable Passkey (FIDO2) Profiles in Microsoft Entra ID (preview) – Microsoft Entra ID | Microsoft Learn
• How to Enable Synced Passkeys (FIDO2) in Microsoft Entra ID (preview) – Microsoft Entra ID | Microsoft Learn
• How to run a registration campaign to set up Microsoft Authenticator – Microsoft Entra ID | Microsoft Learn
• Synced passkeys FAQ – Microsoft Entra ID | Microsoft Learn

[Compliance considerations]

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

[Introduction]

We’re introducing the Advanced Review Set Explorer (public preview) for review sets in Microsoft Purview eDiscovery (Premium).

eDiscovery has long supported Keyword Query Language (KeyQL) because it provides a familiar, approachable, and powerful way to search and filter content—while working consistently across both search and review experiences. For many users and workflows, KeyQL remains the recommended and most efficient way to build queries.

At the same time, we understand that power users and advanced reviewers often need greater flexibility to slice, aggregate, and analyze review set data in more sophisticated ways. To meet this need, we’re adding a Kusto Query Language (KQL)–based experience to review sets through the Advanced Review Set Explorer.

With this update, reviewers will have two query options:

• KeyQL, for familiar, streamlined search and filtering experiences
• KQL, for advanced data exploration, aggregation, transformation, and visualization within a review set

The new Advanced review set explorer’s key capabilities include:

• Run advanced review set explorer using Kusto Query Language (KQL)
• Apply complex filters, aggregations, and transformations
• Visualize results with bar, column, and pie charts
• Query across more than 100 metadata properties
• Identify trends, detect patterns, and analyze data distribution

This message is associated with Microsoft 365 Roadmap ID 484086.

[When this will happen]

• Public Preview (Worldwide, excluding government clouds): We will start rolling out in February 2026 and expect to complete in February 2026.
• General Availability (Worldwide, GCC, GCCH, and DoD): We will start rolling out in July 2026 and expect to complete in July 2026.

[How this affects your organization]

Who is affected: Organizations using Microsoft Purview eDiscovery (Premium).

What will happen:

• A new Advanced Review Set Explorer will be available in review sets.
• The feature is enabled by default.
• Users with eDiscovery review permissions can run KQL queries.
• Users can continue using existing KeyQL‑based searching within review set without change.
• No existing queries or workflows are modified.
• Existing admin policies and permissions are unchanged.

[What you can do to prepare]

• Inform eDiscovery teams that both KeyQL and KQL are supported, and users can choose the option that best fits their needs.
• Consider providing KQL training or reference materials.
• Update internal documentation or workflows as needed.
• Inform eDiscovery teams about this new capability.
• Review Microsoft Learn content on eDiscovery solutions.

Learn more: 

• Kusto Query Language overview | Microsoft Learn
• Learn about eDiscovery | Microsoft Purview | Microsoft Learn

[Compliance considerations]

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

[Introduction]

Soon, the Microsoft Edge profile flyout will be updated to deliver a cleaner, more intuitive experience. The refreshed design makes it easier to distinguish between work and personal profiles, manage credentials, and quickly access key settings—all within a polished interface that supports modern browsing needs. With streamlined sign-in, clearer profile types, and organization branding preserved, this update enables a more efficient and trustworthy experience. 

Screenshot 1: Example of the redesigned profile flyout for a managed (work) account.

Screenshot 2: Example of the updated flyout for a profile that is not signed in.

This message is associated with Microsoft 365 Roadmap ID 495833.

[When this will happen:]

General Availability (Worldwide): Rollout will begin mid‑February 2026 and is expected to complete by late February 2026.

[How this affects your organization:]

Who is affected:

All Microsoft Edge users in your organization.

• The Microsoft Edge profile flyout will be redesigned for improved clarity and usability.
• Users will be able to more easily distinguish between work and personal profiles.
• Organization branding will remain visible in the updated interface.
• The update includes streamlined sign-in options and clearer profile types.
• The feature will be enabled by default.
• Existing admin policies will continue to apply.

[What you can do to prepare:]

No admin action is required before rollout.

If desired, you may:

• Review current Microsoft Edge profile and sign‑in policies to understand any potential impact.
• Notify users about this change.
• Update internal help or documentation where you describe the Edge profile experience.

[Compliance considerations:]

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

[Introduction]

We are improving the ServiceNow Tickets Copilot connector to ensure more accurate and timely ticket status updates in Microsoft 365 Copilot. Previously, inactive ServiceNow tickets were not ingested, which could lead to outdated or incomplete status information in Copilot responses. With this enhancement, the connector now ingests both active and inactive tickets by default. Admins can also edit the data query filter in existing connections to include inactive tickets, enabling more accurate insights and higher‑quality Copilot responses based on real ticket data.

This message is associated with Microsoft 365 Roadmap ID 505437.

[When this will happen:]

• Public Preview (Worldwide): Beginning late December 2025 and completing by late January 2026.
• General Availability (Worldwide): Beginning late January 2026 and completing by late February 2026.

[How this affects your organization:]

Who is affected:

• Admins who manage Copilot connectors with the ServiceNow Tickets connector enabled.
• Users who rely on Copilot to retrieve or summarize ServiceNow ticket information.
• A Microsoft 365 Copilot license is required to use this feature.

What will happen:

• Copilot connectors will ingest both active and inactive ServiceNow tickets by default.
• Ticket statuses will refresh more frequently and accurately in Copilot responses.
• Admins can edit existing connections’ query filters to include inactive tickets.
  • When creating or managing a ServiceNow Tickets connection, admins can navigate to the Content tab and modify the Query string to update the ingestion filter. This allows organizations to include both active and inactive tickets for more complete and accurate Copilot responses.

  Screenshot: ServiceNow Tickets connector – Content tab showing the Query string field

  

• The feature is enabled by default for all tenants using the connector.
• No user workflow changes are expected.

[What you can do to prepare:]

• Review the query filter for existing ServiceNow Tickets connections to ensure it includes active and inactive tickets.
• Update internal documentation related to Copilot ticket data ingestion.
• Communicate this change to internal ServiceNow or helpdesk stakeholders.

If no changes are needed to your query filter, no action is required.

[Compliance considerations:]

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

[Introduction]

We are expanding AI-powered audio overview capabilities in Microsoft Viva Connections and SharePoint. This update introduces support for additional languages in the Viva Connections news reader experience and brings AI-generated audio summaries to SharePoint site pages and news posts when the SharePoint Knowledge agent is enabled. These enhancements provide greater accessibility and help users stay informed in the way that best fits their work style.

This message is associated with Microsoft 365 Roadmap ID 535423.

[When this will happen] 

• Targeted Release (Worldwide): We began rolling out in mid-January 2026 and expect to complete by the end of January 2026.
• General Availability (Worldwide, GCC, GCC High, and DoD): We will begin rollout in early Feb 2026 and expect to complete in late February 2026.

[How this affects your organization]

Who is affected: 

• Users licensed for Microsoft 365 Copilot who read News in Viva Connections (Teams desktop or mobile).
• Users viewing SharePoint site pages or news posts when the SharePoint Knowledge agent is enabled on that site.

What will happen: 

• Users in Viva Connections can listen to AI-generated audio briefings of the top 10 personalized news items in their profile or device language.
• Users viewing SharePoint pages or news posts can listen to AI-generated audio summaries of the article in the site or page language when Knowledge agent is enabled.
• The feature is on by default; no admin action or configuration is required.
• Existing SharePoint and Viva Connections admin settings continue to apply.

[What you can do to prepare]

No action is required. This update will automatically apply as part of the standard service rollout.

You may choose to:

• Inform users about the new audio experiences.
• Update internal guidance related to Viva Connections or SharePoint News.

Learn more:

• The Copilot powered news summary | Microsoft Viva | Microsoft Learn
• Generate audio overviews with AI | Microsoft Support

[Compliance considerations]

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

[Introduction]

We’re enhancing the custom dictionary feature in Copilot Settings to add support for more languages, increase per‑language dictionary limits, and streamline dictionary management. These improvements help organizations improve transcript accuracy for Microsoft Teams meetings and support better Copilot and Intelligent Recap experiences. This update also aligns with customer feedback requesting broader language coverage and easier ongoing dictionary maintenance.

A Microsoft 365 Copilot license is required for the meeting organizer or transcription initiator to apply transcript enhancements that rely on custom dictionary entries.

This update applies to Teams meeting transcripts on Teams for Windows, Teams for Mac, Teams for the web, and Teams for iOS and Android.

[When this will happen]

General Availability (Worldwide): Rollout began in mid-January 2026 and is expected to complete by late January 2026.

[How this affects your organization]

Who is affected:

• Organizations that use Teams meeting transcripts.
• Admins who manage custom dictionary entries in Copilot Settings.
• Users relying on Copilot or Intelligent Recap features during or after meetings.

What will happen:

• Expanded language support:  The custom dictionary will support Chinese (Traditional), Dutch, Korean, Thai, and Turkish, in addition to the currently supported Chinese (Simplified), English, French, German, Italian, Japanese, Portuguese, and Spanish. 

  

• Increased entry limits: Per-language maximum increases from 500 to 1,000 entries. 

  

• Simplified dictionary management: Admins can upload incremental CSV files to append new terms. 

  

• This feature will be enabled automatically when rollout completes.

[What you can do to prepare]

No action is required before rollout.

• Notify admins or user groups about the new capabilities.
• Review current dictionaries and consider using the expanded entry limit.
• Determine whether your organization will use newly supported languages.
• Use the new Add entries upload option to update dictionaries incrementally.
• Update internal documentation as needed.

Learn more: Manage custom dictionaries for Microsoft Teams meetings and events | Microsoft Teams | Microsoft Learn

[Compliance considerations]

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

[Introduction]

We’re updating how diagnostic uploads work in Outlook for Android and iOS. Starting February 16, 2026, users will be able to upload diagnostics even if Optional Connected Experiences are disabled. This change ensures that support teams can collect necessary troubleshooting data without requiring additional settings.

[When this will happen:]

Starting February 16, 2026.

[How this affects your organization:]

• Who is affected: Organizations using Outlook for Android and iOS with Optional Connected Experiences disabled.
• What will happen:
  • Users can upload diagnostics to Outlook Support regardless of Optional Connected Experiences settings.
  • No changes to admin policies or user workflows beyond this diagnostic capability.
  • No impact on other features or connected experiences.

[What you can do to prepare:]

• No action is required from admins or users.
• Review Optional Connected Experiences overview for context.
• Communicate this change to helpdesk staff if they handle Outlook mobile troubleshooting.

[Compliance considerations:]

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

[Introduction]

By the end of March 2026, Microsoft Defender for Android will no longer support protection of personal profiles on enrolled devices. This change aligns with our enterprise-first security strategy, ensuring resources are focused on protecting corporate data while maintaining user privacy.

[When will this happen]

Rollout will begin in mid-March 2026 and complete by late March 2026.

[How this affects your organization]

Who is affected: Organizations using Microsoft Defender for Endpoint (MDE) on Android in personal profiles on enrolled devices that are managed through mobile device management (MDM) configuration policies.

What’s changing:

We’re ending support, monitoring, and feature development for protecting personal profiles on enrolled devices (personal profiles managed via MDM configuration policy). Our main objective is to safeguard corporate assets, with emphasis on identity and data contained within the work profile in enrolled environments. We rely on Android’s platform-level separation to ensure robust isolation. Current research indicates that the likelihood of cross-profile attacks compromising enterprise data remains minimal at present.

Current State:

Defender can be enrolled in the personal profile and managed through MDM configuration policies along with controlling work profile configuration (App Configuration policies targeted to managed devices).

Reference link: Deploy Microsoft Defender for Endpoint on Android with Microsoft Intune

New State:

Deploying and managing Defender in personal profile on enrolled devices via MDM policies will be retired by the end of March 2026. Defender in work profile on enrolled devices and unenrolled mobile application management (MAM)-enabled devices remains unchanged. 

Reference link: Configure Microsoft Defender for Endpoint on Android risk signals using App Protection Policies (MAM)

Benefits of the Change:

This update enhances our enterprise-focused strategy by providing more efficient and dependable protection for corporate data. It safeguards user privacy and ensures that Defender exclusively protects corporate assets, maintaining the integrity of personal information in accordance with privacy regulations and platform separation requirements.  

[What you can do to prepare]

• No action is required from admins or users.
• These changes will be applied automatically in the back end and will not impact your work profile or unenrolled experience.

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