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

Updated June 30, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

We’re introducing a private chat feature for organizers, co-organizers, and presenters in structured meetings and webinars in Microsoft Teams. This separate chat enhances collaboration by allowing key participants to communicate privately before, during, and after the event, without involving attendees. Additionally, we are unifying backroom chat behavior in town halls to ensure consistent functionality across all structured meetings. Currently, backroom chat behavior varies depending on whether streaming chat is enabled for town halls and whether the organizer has a Teams Premium license. This update removes that inconsistency.

This message is associated with Roadmap ID 392328 and applies to Teams for Windows desktop, Teams for Mac desktop, Teams for the web, Teams for iOS/Android, MTR-W and MTR-A devices.

[When this will happen:]

• Targeted Release: Rollout begins in mid-August 2026 (previously mid-July) and is expected to complete by late August 2026 (previously late July).
• General Availability (Worldwide and GCC): Rollout begins in mid-September 2026 (previously early August) and is expected to complete by late September 2026 (previously mid-August).

[How this affects your organization:]

Who is affected: Admins managing Microsoft Teams meetings, webinars, and town halls.

What will happen:

• New private chat for organizers, co-organizers, and presenters: This chat is separate from attendee chat and is available before, during, and after the event.
• Unified backroom chat policy for town halls: The default setting will be ON for all town halls, regardless of streaming chat availability or license type.
• Existing town halls will adopt the new policy once meeting options are updated.
• If admins turn the backroom chat policy OFF, previously enabled town halls will lose access after update.
• Non-TPre town halls (those without a Teams Premium license) will have backroom chat ON by default after rollout and update.

Two potential impacts:

• If an admin explicitly turns the new backroom chat policy OFF, any already-scheduled town hall that previously had backroom chat ON will lose access once the meeting options are updated.
• For non-TPre town halls where backroom chat was previously OFF, it will switch to ON by default after the rollout and a meeting options update.

[What you can do to prepare:]

• Review your Teams meeting policies and decide whether to enable private chat for organizers and presenters.
• Communicate this change to helpdesk staff and event organizers.
• Update internal documentation to reflect the new backroom chat behavior.
• If you want to disable backroom chat, adjust the policy in the Teams admin center.

[Compliance considerations:]

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

Updated June 30, 2026: We have updated the content. Thank you for your patience. 

[What and Why]

We are updating how Microsoft Teams sends guest invitation emails to improve clarity and trust in cross-tenant collaboration. Instead of being sent from a Microsoft no-reply address, guest invitation emails will soon appear to come directly from the inviter’s email address.

This change helps recipients easily recognize who invited them, enables direct replies, and reduces confusion, improving the overall collaboration experience.

[Rollout Schedule]

General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out in late June 2026 and expect to complete by late July 2026.

[Impact on Your Organization]

Who is affected

• All Microsoft Teams users who invite external guests
• External recipients of guest invitations
• Microsoft 365 administrators managing guest access and collaboration policies

Platforms/Services

• Microsoft Teams
• Exchange Online (email delivery behavior)

What will happen

• Guest invitation emails will appear to come from the inviting user’s email address instead of a Microsoft no‑reply address: 

  

• Invitees can reply directly to the inviter via email or can redeem the invitation and use Teams.
• There are no changes to guest access permissions or policies.
• No admin configuration required.
• The feature will be enabled by default across all tenants.

[Action Required / Recommendations]

No action is required.

However, we recommend that you:

• Inform users that invitation emails will now appear to come from their own email address.
• Prepare helpdesk/support teams for potential questions about unexpected replies from external guests.
• Review your guest access policies to ensure they align with your organization’s collaboration practices.
• Update internal documentation or training materials if they reference invitation email behavior.

Learn more: 

• Add guests to a team in Microsoft Teams | Microsoft Support
• Guest experience in Teams | Microsoft Teams | Microsoft Learn

[Compliance considerations]

Updated June 30, 2026: We have updated the timeline. Thank you for your patience. 

[What and Why]

Academies in Viva Learning are now available in Microsoft Teams mobile, allowing learners to access organization‑curated learning journeys directly from their mobile devices. This update extends Academy visibility and navigation to mobile, providing a consistent learning experience across desktop, web, and mobile while preserving existing admin controls and permissions.

Rollout Schedule

• General Availability (Worldwide): We will begin rolling out mid-July 2026 (previously end of June) and expect to complete by end of July 2026 (previously early July).

[Impact on Your Organization]

Who is affected

• Users accessing Viva Learning in Microsoft Teams mobile

Platforms / Services

• Microsoft Teams (mobile)
• Viva Learning

What will happen

• Learners will see all Academies they have permission to access under the Academy tab in Teams mobile.

Screenshot 1: Academies visible in Viva Learning on Microsoft Teams mobile:



Screenshot 2: Learners can open an Academy to navigate Sections, Sub-sections, and Learning Paths:



• Learners can:
  • View Academies they are authorized to access.
  • Navigate Sections and Sub‑sections configured by admins.
  • Open Learning Paths and the courses within them.
  • Land directly on the Academy view when opening a shared Academy link.
  • Access the Microsoft Copilot Academy on mobile through notifications.
• Academies on mobile are view‑only.
• All Academy creation, permissions, and curation continue to be managed on Viva Learning web and desktop.
• Updates made by admins on web or desktop automatically appear on mobile.
• This feature is enabled by default and respects existing permissions.
• No policy or configuration changes are required.

[Action Required / Recommendations]

• No action is required.
• Consider notifying helpdesk staff and learners about mobile availability.

[Compliance Considerations]

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

Updated June 30, 2026: We have updated the timeline. Thank you for your patience.  

[What and Why]

Microsoft is expanding the availability of the Legal agent in Microsoft 365 Copilot in Word to Frontier users worldwide in Public Preview.

The Legal agent was previously released in Frontier preview for users located in the United States only. This update expands access globally, enabling more organizations to benefit from this capability.

The Legal agent is a vertical-specific Microsoft 365 Copilot experience designed for legal professionals, built directly into Word. It helps legal teams review and negotiate contracts by identifying risks, comparing clauses to internal playbooks, and proposing edits using Word’s native tracked changes.

This update helps reduce manual review time while keeping legal professionals fully in control of document workflows.

[Rollout Schedule]

• Frontier Preview: Available starting in mid-June 2026.

[Impact on Your Organization] 

Who is affected

• Organizations enrolled in the Microsoft 365 Copilot Frontier program
• Users with Microsoft 365 Copilot licenses, particularly legal professionals (for example, in-house counsel, contract managers, legal ops)

Organizations not enrolled in the Frontier program are not impacted.

Platforms/Services

• Microsoft Word (Copilot) – desktop and web
• Microsoft 365 Copilot (Frontier)

What will happen

• A new Legal agent will be available in Copilot Chat in Word via the “+” (plus) menu.
• Users can:
  • Review contracts to identify risks and non-standard clauses
  • Generate redlines using Word tracked changes
  • Compare clauses against internal legal playbooks
  • Analyze document sections for compliance with internal standards
  • Receive responses grounded in document content with citations
• The feature is enabled by default for tenants enrolled in Frontier.
• No separate installation is required.
• The feature is available immediately after users update to a supported version of Word.
• Availability depends on:
• Frontier program enrollment
• Microsoft 365 Copilot licensing
• There is no dedicated admin or user toggle to disable this feature
• Access is controlled through Frontier enrollment and Copilot license assignment.

[Action Required / Recommendations]

No action is required if you do not plan to use this feature.

If you plan to use this feature:

• Enroll your tenant in the Frontier Public Preview program.
• Ensure Microsoft 365 Copilot licenses are assigned to eligible users.
• Review internal legal workflows that may benefit from:
  • Contract analysis
  • Playbook-based reviews
  • AI-assisted redlining
• Communicate this capability to legal teams.
• Update internal documentation or helpdesk guidance if applicable.

[Compliance considerations]

For more information visit Get Started with Legal agent in Word and Transparency Documentation 

Updated June 30, 2026: We have updated the timeline. Thank you for your patience. 

[What and Why]

We’re introducing automatic recording and transcription for Microsoft Teams Call Queues. This feature enables administrators to automatically record and transcribe calls handled by call queue representatives without manual action, supporting quality assurance and training scenarios.

This message is associated with Roadmap ID 565215.

[Rollout Schedule]

• Targeted Release: We will begin rolling out in early August 2026 (previously mid-July) and expect to complete by mid-August 2026 (previously late July).
• General Availability (Worldwide, GCC): We will begin rolling out in mid-August 2026 (previously early August) and expect to complete by late August 2026 (previously mid-August).

[Impact on Your Organization]

Who is affected:

• Admins managing Microsoft Teams Call Queues
• Call Queue agents in queues where recording is enabled
• Organizations using Teams Phone
• Users requiring access to recordings and transcripts through the Queues app (Teams Premium license required)

What will happen:

• Automatic recording and transcription per call queue: Admins can enable automatic recording and/or transcription on any call queue via Teams admin center or PowerShell. When enabled, all calls answered by agents in that queue are automatically recorded.
• Recordings stored in SharePoint: Recordings are automatically stored in SharePoint and accessible through the Queues app call history.
• Agent access controls: Admins can configure whether agents can view recordings and transcripts in the Queues app call history to support shared customer callback scenarios.
• Configurable recording announcements: Admins can configure the recording and transcription announcements played to callers. Options include the default system announcement, a custom audio file, or text-to-speech.

[Action Required / Recommendations]

Action may be required. Review and prepare before rollout:

• Review your organization’s call recording and transcription policies.
• Determine which Call Queues should enable automatic recording.
• Communicate changes to call queue agents and helpdesk teams.
• Configure agent access permissions for recordings and transcripts.
• Customize the recording announcement if required.
• Ensure Teams Premium licensing is available for users needing Queues app access.

• New-CsAutoRecordingTemplate | PowerShell
• Get-CsAutoRecordingTemplate | PowerShell
• Set-CsCallQueue | PowerShell
• Get-CsCallQueue | PowerShell

[Compliance considerations]

[What and Why:]
Microsoft is enhancing Microsoft 365 Copilot release preferences by adding support for Microsoft Entra ID groups. This update enables admins to assign groups—not just individuals—to Standard or Deferred release audiences, providing more flexible, enterprise-ready control over how Copilot updates are deployed. This improvement supports phased rollouts, targeted validation, and stronger change management practices—helping organizations reduce risk and confidently adopt new Copilot capabilities.

[Rollout Schedule:]
General Availability (Worldwide): Rolling out from late June 2026 through late July 2026

[Impact on Your Organization:]

Who is affected:

• Microsoft 365 administrators configuring Copilot release preferences
• Organizations using Standard or Deferred release options for Microsoft 365 Copilot

Platforms/Services:

• Microsoft 365 admin center (web)
• Microsoft 365 Copilot

What will happen:

• Admins can assign Microsoft Entra ID groups to Standard or Deferred release audiences
• Groups can be used to override the tenant-wide release preference
• Enables targeted rollout scenarios such as:
• Assigning pilot groups to Standard release for early validation
• Assigning sensitive departments to Deferred release for additional review time
• Nested groups are not supported
• Total enrollment (users + group members) is limited to 100 users
• Feature is available through existing release preference controls in the Microsoft 365 admin center
• No change to end-user experience unless they are included in a targeted release group

[Action Required / Recommendations:]
No immediate action is required.

If you plan to use this capability:

• Identify or create Microsoft Entra ID groups for release targeting
• Ensure total enrolled users (including group members) remain within the 100-user limit
• Assign groups in the Microsoft 365 admin center under release preferences
• Regularly review group membership for compliance with limits
• Update internal rollout, pilot, and change management documentation

Additional resources:
Learn more about the modern change management model

[Compliance considerations:]

• This change introduces an admin control that can be configured using Entra ID group membership
• No other compliance considerations identified; review as appropriate for your organization

[What and Why:]

We are enhancing protection for sensitive documents by enforcing the Do Not Allow Screen Capture permission in the OneDrive and SharePoint web PDF viewer when accessed through Microsoft Edge. This update closes a known gap where browser-rendered PDFs did not enforce this Microsoft Purview Information Protection (MIP) control, aligning the web experience with desktop behavior. This improvement strengthens enterprise data protection and helps ensure sensitive content remains secure across access points.

[Rollout Schedule:]

• Targeted Release: Beginning in early August 2026 and expect to complete by mid-August 2026
• General Availability (Worldwide): Beginning in mid-August 2026 and expect to complete by late August 2026

[Impact on Your Organization:]

Who is affected:

• Organizations using Microsoft Purview Information Protection sensitivity labels
• Users opening labeled PDFs in OneDrive or SharePoint via Microsoft Edge

Platforms/Services:

• OneDrive for Business (web)
• SharePoint Online (web)
• Microsoft Edge

What will happen:

• Screen capture will be blocked for PDFs labeled with Do Not Allow Screen Capture.
• Enforcement is on by default where applicable.
• Existing sensitivity labels and policies are respected.
• No impact to unlabeled PDFs or labels without restrictions.
• Other browsers and mobile web are not supported at general availability.
• Users accessing protected PDFs outside Edge may not have consistent enforcement.

[Action Required/Recommendations:]

• Review sensitivity labels that include Do Not Allow Screen Capture to confirm intended usage.
• Update internal helpdesk and user documentation to explain why screenshots may be blocked.
• Communicate this change to users, especially those handling sensitive documents.
• Evaluate Conditional Access or browser management policies to ensure protected PDFs are accessed via Microsoft Edge.
• Enable Microsoft Purview Information Protection support in Edge by following guidance: Configure MIP in Edge

[Compliance considerations:]

Updated June 30, 2026: We have updated the timeline. Thank you for your patience. 

[What and Why]

We are introducing a new Microsoft Teams Facilitator capability that proactively detects and resolves knowledge gaps during meetings. Facilitator can identify when participants ask questions or express uncertainty and retrieve and share relevant answers using web search in the meeting chat. This enhancement helps improve meeting productivity by reducing interruptions and enabling teams to stay focused on goals while accessing needed information. If a participant asks a factual question and no one responds, Facilitator can provide an answer directly in the meeting chat.

This message is associated with Microsoft 365 Roadmap ID 558341.

[Rollout Schedule]

• Targeted Release: Beginning early August 2026 (previously early July) and expected to complete mid-August 2026 (previously late July)
• General Availability (Worldwide): Beginning mid-August 2026 (previously early August) and expected to complete late August 2026

[Impact on Your Organization]

Who is affected

• Users in Microsoft Teams meetings where Facilitator is enabled with Microsoft 365 Copilot (Premium)

Platforms/Services

• Microsoft Teams (meetings)
• Microsoft 365 Copilot

What will happen

• Facilitator will monitor meeting conversations in real time to detect implicit or explicit information needs.
• When a knowledge gap is identified, Facilitator performs a web search and posts a response in the meeting chat: 

  

• Responses are infrequent in practice and typically occur less than once per meeting.
• Responses are limited to questions relevant to the meeting discussion based on agenda signals and conversational context.
• Facilitator must be manually added to the meeting and is not enabled by default.
• A user with a Microsoft 365 Copilot (Premium) license must enable Facilitator for the meeting. Other participants do not need to be licensed to receive responses.
• Admins can disable Facilitator at the tenant level. The feature depends on the Copilot web search setting. If web search is disabled, responses are not generated.
• Users can stop the behavior at any time by removing Facilitator from the meeting.
• The feature is supported in standard Teams meetings only and not supported in calls, webinars, or town halls.
• The experience is supported in meetings that include external or cross-tenant participants.

[Action Required/Recommendations]

No immediate action is required.

Recommended actions:

• Review your organization’s Copilot web search and Facilitator configuration settings to confirm alignment with your policies.
• Inform helpdesk and users about proactive Facilitator responses in meeting chats.
• Update internal documentation or training materials if you reference Teams meeting experiences.

[Compliance considerations]

[What and Why]

As part of ongoing role lifecycle management in Microsoft Entra, we will block new assignments to the Partner Tier1 Support and Partner Tier2 Support roles. These roles are no longer intended for use and are being retired. This change supports improved security and clearer role usage by encouraging the use of least-privilege roles.

[Rollout Schedule]

• Global: Beginning August 3, 2026, and expected to complete by August 24, 2026

[Impact on Your Organization]

Who is affected

•  Admins who manage role assignments in Microsoft Entra, including those using CSP or GDAP delegated access scenarios

Platforms/Services

•  Microsoft Entra ID across portals, APIs, and automation workflows

What will happen

• New assignments to Partner Tier1 Support and Partner Tier2 Support roles will be blocked.
• This change is part of the retirement process for these roles.
• If your organization does not use these roles, this change has no operational impact.
• Attempts to assign these roles will fail with HTTP 400 (Request_BadRequest), indicating that assignments are no longer allowed.
• Existing role assignments will continue to work without changes.
• Removal of existing assignments will continue to work.
• No other roles in Microsoft Entra are affected.

[Action Required/Recommendations]

• No action is required if your organization does not use these roles.
• If you currently use these roles, review and update any scripts, automation, or workflows that assign them.
• For most scenarios, User Administrator is the closest replacement.
• Replace usage with appropriate alternatives such as:
  • User Administrator
  • Helpdesk Administrator
  • Groups Administrator
  • License Administrator
  • Domain Name Administrator
• Consider creating a custom role aligned to least privilege requirements if needed.
• Review CSP or GDAP delegated admin configurations for use of these roles.
• Update internal documentation and admin guidance as appropriate.
• Contact Microsoft Support if you need help identifying a replacement role.

Learn more: 

• Microsoft Entra built-in roles | Role-based access control | Microsoft Entra ID | Microsoft Entra | Microsoft Learn
• Partner Tier1 Support – Microsoft Entra built-in roles | Role-based access control | Microsoft Entra ID | Microsoft Entra | Microsoft Learn
• Partner Tier2 Support – Microsoft Entra built-in roles | Role-based access control | Microsoft Entra ID | Microsoft Entra | Microsoft Learn
• Roles not shown in the portal – Microsoft Entra built-in roles | Role-based access control | Microsoft Entra ID | Microsoft Entra | Microsoft Learn

[Compliance considerations]

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

[What and Why:]

Microsoft Purview Data Loss Prevention (DLP) is introducing user-based aggregation of alerts, enabling related DLP events triggered by the same user to be grouped into a single alert. This enhancement reduces alert noise, streamlines investigation workflows, and provides richer context for security and compliance teams.

This message is associated with Microsoft 365 Roadmap ID 564765.

Rollout Schedule:

• General availability (Worldwide): We will begin rolling out in mid-August 2026 and expect to complete by mid-August 2026.

Impact on Your Organization:

Who is affected: Compliance admins and security admins managing Microsoft Purview DLP

Platforms/Services:

• Microsoft Purview compliance portal (web)
• Data Loss Prevention (DLP)

What will happen:

• A new configuration option will be available for event aggregation into alerts.
• Admins can select user-based aggregation and define an aggregation time window.
• Multiple DLP events triggered by the same user within the defined time window will be consolidated into a single alert.
• Alerts may include events that match different DLP rules.
• The feature is not enabled by default and requires admin configuration.
• No change to DLP policy enforcement.

Once enabled, alerts are aggregated by user, regardless of which DLP rules are matched within the defined aggregation window.

Example: A single alert may include multiple events triggered by the same user, even when those events match different DLP rules.

The following examples illustrate the difference between aggregated and non-aggregated alerts:

Screenshot 1: Aggregated alert — multiple events triggered by the same user are grouped into a single alert, including events that match different DLP rules:

Screenshot 2: Non-aggregated alert — each event generates a separate alert, showing a single event and rule match:

Action Required/Recommendations:

• Review the new setting once available in your tenant.
• To enable:
  1. Go to Settings > DLP settings > Alert settings > Event aggregation into alerts
  2. Select User-based aggregation
  3. Configure the alert aggregation time window
  4. Select Save

  Screenshot 3: Enable user-based aggregation and set the alert aggregation window in DLP Alert settings

  

• Evaluate whether aggregation aligns with your organization’s alert triage and investigation processes.
• Communicate this change to your security operations or compliance teams.
• Update internal documentation or runbooks if you rely on DLP alert workflows.

Compliance considerations:

[What and Why]

To improve productivity and make it easier for users to find and customize keyboard shortcuts, Microsoft Teams is adding search functionality to the Keyboard shortcuts dialog. This enhancement helps users quickly locate shortcuts by action name or key combination, reducing time spent scanning long lists and improving efficiency when navigating and customizing shortcuts.

This feature applies to Teams for Windows desktop, Mac desktop, and the web.

This message is associated with Microsoft 365 Roadmap ID 562413.

[Rollout Schedule]

• Targeted Release: Available now.
• General Availability (Worldwide, GCC, GCCH, and DoD): Available now.

[Impact on Your Organization]

Who is affected

•  All Microsoft Teams users who access the Keyboard shortcuts dialog

Platforms

• Teams for Windows desktop
• Teams for Mac desktop
• Teams for the web

What will happen

• Users can search for keyboard shortcuts using:
  • The name of an action (for example, Mute or Open settings)
  • A keyboard shortcut combination (for example, Ctrl+Shift+M)
• The search capability applies to:
  • Viewing existing keyboard shortcuts
  • Customizing personal keyboard shortcuts
• The feature is enabled by default.
• Existing Teams policies and admin configurations are respected.
• There is no change to existing workflows unless users choose to search or customize shortcuts.

[Action Required/Recommendations]

No action is required.

You may want to:

• Inform helpdesk and support teams about this enhancement.
• Update any internal documentation related to Teams keyboard shortcuts.

[Compliance considerations]

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

• Stage-aware guidance: See insights and next actions prioritized by the current business process flow (BPF) stage and substage signals, so guidance matches the selling motion.
• Delta-first updates: Lead with what changed since the last review, why it matters for this stage, and the next best actions to take.
• Always-visible critical risks: Keep urgent cross-stage risks visible when they require immediate attention.
• Out-of-the-box stage coverage: Get built-in guidance across Qualify, Develop, Propose, and Close, with support for customer variations.

• Appear alongside existing templates in the Agent Builder experience.
• Be identified as personalized recommendations.
• Be refreshed regularly based on current work patterns.
• Avoid recommending agents that have already been published or duplicated.
• Trigger email notifications when new suggestions are available.

1. Define multi-channel playbooks so customer outreach can move across web chat, voice, SMS, and email based on response patterns and business goals.
2. Set channel-specific guidance for tone, message length, and best practices, so communications are appropriate for each channel.
3. Configure consent management for each channel to support compliant outreach and honor customer communication preferences.
4. Enable automatic logging of channel interactions to CRM so teams have complete visibility into customer engagement history.
5. Use cross-channel engagement context to maintain continuity and deliver a consistent customer experience across touchpoints.