Microsoft Roadmap, messagecenter and blogs updates from 02-11-2025

Update 10/28/2025: New information related to Office 365 Connectors Retirement in Teams – Webhook URL Migration (MC808160). We’ve extended the migration deadline to give organizations more time to transition. We’re also making progress on feature parity for Workflows webhooks.

The migration deadline is extended to March 31, 2026. Feature parity improvements will be available by December 2025.

• Who is affected: Organizations using Office 365 Connectors in Microsoft Teams.
• What will happen:
  • Migration deadline extended to March 31, 2026.
  • By December 2025, Workflows webhooks will support:
    • Posting messageCard formatted payloads (no need to reformat to Adaptive Cards).
    • Posting messages and Adaptive Cards to shared or private channels.

• Plan to transition from Office 365 Connectors to Workflows webhooks by March 31, 2026.
• Prepare to use new webhook capabilities starting December 2025.

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

[Introduction:]

We are expanding Microsoft Purview Data Loss Prevention (DLP) to support Microsoft 365 Copilot, helping organizations safeguard prompts that contain sensitive data. This real-time control helps mitigate data leakage and oversharing risks by preventing Microsoft 365 Copilot—including pre-built agents—from returning a response or using sensitive data for grounding in Microsoft 365 or the web.

This message is associated with Microsoft 365 Roadmap ID 515945.

[When this will happen:]

• Public Preview: We will begin rolling out in mid-November 2025 and expect to complete by late December 2025.
• General Availability (Worldwide): We will begin rolling out in late March 2026 and expect to complete by late April 2026.

[How this affects your organization:]

Who is affected:

• Microsoft tenants with access to Microsoft 365 Copilot (free and paid), including E1, E3, and E5 license holders.
• Admins managing Microsoft Purview DLP policies for Microsoft 365 Copilot.

What will happen:

• Admins can configure DLP policies in the Microsoft Purview portal to restrict Copilot from processing prompts containing selected sensitive information types (SITs), including default and custom SITs.
• Prompts containing sensitive data will not receive Copilot responses and will not be used for external web search or internal Microsoft Graph grounding.
• Admins can also view DLP policy recommendations for Microsoft 365 Copilot in Data Security Posture Management:

  Screenshot 1

  

  Screenshot 2

   

  Important: At this time, DLP for Copilot policies do not support enforcement based on sensitive information types (SITs). Hence, no users will be impacted under SIT-based conditions. Admins need to create a new policy to enforce DLP for Copilot prompt based on SIT.

[What you can do to prepare:]

• This feature will be available automatically by the specified date with no admin action required.
• Admins can opt-in to use the feature by setting up a new policy. Review your current configuration to assess the impact on your organization.
• To edit or view a DLP for Microsoft 365 Copilot policy, an admin account needs to be a member of a required role group. Data Security AI admins are also able to edit a DLP for Microsoft 365 Copilot policy.
• You may want to notify your users or admins about this change and update your relevant documentation.

Learn more: 

• Learn about data loss prevention | Microsoft Purview | Microsoft Learn
• Learn about the Microsoft 365 Copilot location | Microsoft Purview | Microsoft Learn

[Introduction]

To simplify meeting coordination, we’re introducing intelligent and native polls directly into the Outlook calendar compose form. This enhancement helps users propose multiple time slots and gather attendee preferences—especially useful when scheduling with external participants or individuals with limited availability.

>

[When this will happen:]

General Availability (Worldwide): Rollout begins in late October 2025 and is expected to complete by early December 2025.

[How this affects your organization:]

• Who is affected: All users of the New Outlook for Win 32 and Outlook on the web who use the calendar compose experience.
• What will happen:
  • Users will see a new option to create scheduling polls directly within the calendar compose form.
  • The feature will be ON by default for all tenants.
  • No changes to existing admin policies are required.
  • Polls will help organizer propose multiple meeting time slots and gather attendee preferences.
  • External attendees can respond to polls on website without needing a Microsoft 365 account.

[What you can do to prepare:]

• No action is required. The feature will be enabled by default. However, you may consider:
• Informing helpdesk staff about the new poll experience.
• Updating internal documentation if you provide guidance on scheduling workflows.
• Reviewing user training materials to include poll creation steps.

[Compliance considerations:]

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

[Introduction]

We’re introducing a new capability in Microsoft Teams that allows users to start a chat with anyone who has an email address—even if they’re not currently using Teams. The recipient will receive an email invitation to join the chat session as a guest, enabling seamless communication and collaboration. This update simplifies external engagement and supports flexible work scenarios.

This feature will be available across Android, Desktop, iOS, Linux, and Mac platforms.

This message is associated with Microsoft 365 Roadmap ID 513271.

[When this will happen:]

• Targeted Release: Rollout will begin in early November 2025 and is expected to complete by mid-November 2025.
• General Availability (Worldwide): Rollout will begin in January 2026.

[How this affects your organization:]

Who is affected:

• All Microsoft Teams users in your organization.

What will happen:

• Users will be able to initiate chats with any external contact using their email address.
• External users will receive an email invitation and can join the chat as guests.
• The chat experience will be governed by your organization’s Entra B2B Guest policy.
• Chats will remain within your organization’s boundary.
• This feature will be enabled by default.

[What you can do to prepare:]

• Update internal documentation to reflect this new capability.
• Inform helpdesk and support teams about the change.
• To disable the feature, set the UseB2BInvitesToAddExternalUsers attribute of TeamsMessagingPolicy to false. Set-CsTeamsMessagingPolicy documentation here.

[Compliance considerations:]

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

Microsoft Purview Data Loss Prevention (DLP) is being extended to the network layer through integration with iboss Zero-Trust SASE Platform or Netskope One SASE Platform. This update will be generally available starting mid-November 2025. It enables organizations to intercept and inspect traffic inline and enforce actions based on Purview DLP policy conditions. This helps prevent sensitive data from being shared with untrusted cloud applications through browsers, apps, APIs, add-ins, and more—including generative AI platforms, cloud storage, and content-sharing services—while managing alerts and incidents through Purview and Microsoft Defender. If configured, these signals also inform user risk indicators in Insider Risk Management.

This message is associated with Microsoft 365 Roadmap ID 522095.

General Availability (Worldwide): Rollout will begin in mid-November 2025 and is expected to complete by mid-December 2025.

• Who is affected: Admins managing Microsoft Purview DLP policies and organizations using iboss Zero-Trust SASE or Netskope One SASE platforms.
• What will happen:
  • A new scenario-focused experience will be available for creating DLP policies.
  • Admins can select the Inline Web Traffic scenario to configure granular rules for detecting and protecting sensitive data.
  • Protection will extend to over 35,000 unmanaged cloud applications.
  • Alerts and incidents will be managed in Microsoft Purview and Microsoft Defender.
  • The feature will be available by default but requires integration setup to function.

• Ensure your global administrator enables and configures integration with iboss Zero-Trust SASE or Netskope One SASE platforms.
• Activate Purview pay-as-you-go to enable this capability. Learn about the Pay-as-you-go billing model.
• Review your current configuration to assess impact.
• Notify helpdesk staff and update internal documentation as needed.
• Learn more: Learn about Microsoft Purview billing models | Microsoft Purview | Microsoft Learn

• Call the export API to programmatically export exact copies of sent emails, including personalization and conditional content.
• Schedule regular exports to ensure up-to-date records.
• Select which emails for contacts or leads you want to export for greater control and relevance.
• Integrate with your existing archiving systems and retain copies for the preferred time.

• Support for Partial Dates: Makers can now specify if a DateTime can be partial.
  • If the Date can be partial, the makers can also specify the exact parts of the Date that are required and the ones that are optional with various combinations of Day, Month and Year.
• Specify past or future Dates: Makers can now specify if the Dates should be defaulted to be in the future or past or let the system disambiguate it as it does currently.

• Authenticate with Microsoft or Authenticate Manually – This allows you to force authentication through Microsoft Entra ID or set up manual authentication.
• No authentication allows anonymous access.