Microsoft Roadmap, messagecenter and blogs updates from 16-06-2026

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

Coming soon for Microsoft Teams: A new setting that allows users to view incoming calls in a small window in Teams to prevent disruptions. Users will be able to take a call in the small window and continue to see what they were working on before the call.

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

This message is associated with Microsoft 365 Roadmap ID 482747.

[When this will happen:]

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

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

General Availability (GCC): We will begin rolling out early April 2026 (previously early February) and expect to complete by mid-April 2026 (previously mid-February).

General Availability: (GCC High, DoD): We will begin rolling out early May 2026 (previously early February) and expect to complete by end of June 2026 (previously early May).

[How this will affect your organization:]

Before this rollout: Teams users are disrupted by the larger Teams screen when viewing an incoming call.

After this rollout: Teams users can turn on this setting to view calls in a small window. Note that both large and small windows are resizable:

This feature will be on 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. You may want to notify your users about this change and update any relevant documentation.

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

Starting June 2026, we will resume the automatic installation of the Microsoft 365 Copilot app to eligible devices with the Microsoft 365 desktop apps. This change simplifies access to Copilot and ensures users can easily discover and engage with productivity-enhancing features.

When this will happen

• General Availability: Rollout begins in mid-June 2026 and completes by mid-July

How this affects your organization

• The Microsoft 365 Copilot app will be automatically installed on Windows devices that have Microsoft 365 desktop apps, unless administrators opt out.
• On devices where the app is already installed, no visible change will occur.
• The app installation is enabled by default and does not require user interaction.
• This change does not apply to customers in the European Economic Area (EEA).

What you can do to prepare

• Before deploying, inform users about the upcoming change to avoid surprises and improve adoption.
• No compliance considerations identified, review as appropriate for your organization.

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

[Introduction]

Voice tethering builds on the recent introduction of Sign Language Mode in Microsoft Teams. When a sign language interpreter voices on behalf of a Deaf or hard‑of‑hearing (D/HH) participant, Teams will now attribute captions, transcripts, and meeting intelligence—such as Copilot notes, summaries, action items, and insights—to the D/HH participant rather than the interpreter. This update ensures accurate representation in meetings, clarifies who is contributing to the conversation, and improves downstream meeting accuracy and accountability.

This message is associated with Microsoft 365 Roadmap ID 553223.

[When this will happen]

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

[How this affects your organization]

Who is affected

• Organizations with meeting participants who are Deaf or hard‑of‑hearing and use sign language interpreters in Teams meetings.
• Any users who participate in meetings with Sign Language Mode enabled.

What will happen

• Voice contributions made by interpreters will be attributed to the D/HH participant across:
  
  • Live captions
  • Meeting transcripts
  • Copilot notes, summaries, action items, and insights
  • Other Teams meeting intelligence
• Meeting data becomes more accurate by ensuring the correct participant is represented.
• Interpreter identity is no longer conflated with the signer they support.
• Sign Language Mode is already available to all users; voice tethering enhances it automatically.
• The feature is on by default when sign language mode and interpreter assignment are used.
• No admin controls are required to enable or manage the feature.

[What you can do to prepare]

No action is required.

Optional preparation steps:

• Inform D/HH users and interpreters that speech attribution in meetings will change.
• Update internal training or accessibility resources if you document interpreter workflows.
• Notify helpdesk or support teams that captioning and transcript attribution will appear differently for interpreted meetings.

[Compliance considerations]

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

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

[Introduction]

Microsoft Teams is introducing simplified meeting passcodes to reduce friction when joining meetings, especially when participants must manually enter a passcode. This feature is off by default and must be explicitly enabled by a tenant administrator.

This message is associated with Microsoft 365 Roadmap ID 555858.

[When this will happen]

• Targeted Release: We will begin rolling out in early April 2026 (previously early March) and expect to complete by mid-April 2026 (previously mid-March).
• General Availability
  • Worldwide & GCC: We will begin rolling out in mid-April 2026 (previously mid-March) and expect to complete by late April 2026 (previously late March).
  • GCCH & DoD: We will begin rolling out in early May 2026 (previously early April) and expect to complete by mid-July 2026 (previously mid-May).

Note on rollout timing and admin experience:

As part of a phased rollout, some backend capabilities may become available earlier, including PowerShell configuration starting in mid-March, ahead of the Teams Admin Center UI, which will be released following timelines shared above.

The feature remains off by default, and no change to meeting security behavior occurs unless an administrator explicitly enables it.

[How this affects your organization]

Who is affected:

Tenant administrators who manage meeting security settings in Microsoft Teams.

What will happen:

• A new admin setting allows simplified 8‑digit numeric‑only meeting passcodes.
• The feature is off by default; admins must opt in.
• The setting can be applied to:
  • Specific users
  • Groups
  • The entire tenant
• Only newly scheduled meetings use numeric‑only passcodes.
• Existing meetings are not changed.
• If the feature remains off, Teams continues to use the default, more complex passcodes.

Security considerations:

• Numeric‑only passcodes reduce cryptographic strength relative to the default setting.
• The simplified passcode applies whether users join via meeting ID or by clicking a meeting link.
• Admins will see a security warning when enabling the setting.
• All other Teams meeting security controls remain unchanged, including:
  • Lobby and admission controls
  • Organizer and participant policies
  • Tenant authentication and access controls

[What you can do to prepare]

• Review your organization’s meeting security requirements.
• Decide whether simplified passcodes meet your policies.
• If enabling, determine appropriate scope (users, groups, or tenant‑wide).
• If maintaining current behavior, no action is required.
• Consider updating internal documentation and informing helpdesk staff if you enable the feature.

[Compliance considerations]

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

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

[Introduction]

To improve reliability for large-scale live events, Microsoft Teams town halls will soon support a backup Real-Time Messaging Protocol (RTMP) stream. RTMP is a standard live‑streaming protocol used by event organizers to send live video and audio to a streaming service, such as Microsoft Teams. This enhancement helps ensure uninterrupted broadcasts by automatically failing over to a secondary RTMP stream if the primary stream experiences an interruption. This change increases resiliency for high-visibility events without adding complexity for organizers.

This message applies to Teams for Windows desktop, Teams for Mac desktop, and Teams for the web. It is associated with Roadmap ID 554932.

[When this will happen:]

General Availability (Worldwide, GCC): Rollout begins late April 2026 and completes by early July 2026 (previously mid-June)

[How this affects your organization:]

Who is affected:

• Organizers and producers hosting Microsoft Teams town halls using RTMP-based production workflows

What will happen:

• Organizers can configure a backup RTMP stream during event setup using Teams Meeting options in Production tools.
• If the primary RTMP stream fails, Teams will automatically fail over to the backup stream with no manual intervention.
• There’s no change to the attendee experience.
• The feature is available by default; no admin configuration is required.

[What you can do to prepare:]

• No action is required.
• Optionally, update internal event-production documentation and notify event producers of this new resiliency option.

Learn more: Use RTMP-In in Microsoft Teams | Microsoft Support (will be updated before rollout)

[Compliance considerations:]

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

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

[Introduction]

This message is associated with Roadmap ID 558922.

[When this will happen:]

General Availability (Worldwide): Rollout will begin in mid‑May 2026 and is expected to complete by mid-July 2026 (previously mid‑May).

[How this affects your organization:]

Who is affected:

• Organizations hosting Microsoft Teams meetings with participants joining via Direct Guest Join from Zoom, Google Meet, or Cisco devices.

What will happen:

• Meetings joined through Direct Guest Join will support up to 16 participant videos in a 4×4 video grid.
• Simulcast streaming will improve video quality and reliability across heterogeneous meeting platforms.
• The enhancement is enabled by default.
• No changes are required to existing Teams policies or meeting workflows.

[What you can do to prepare:]

• No admin action is required.
• Inform users about upcoming improvements to cross‑platform meeting quality.
• Update internal documentation or helpdesk guidance if applicable.

[Compliance considerations:]

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

[Introduction]

The Queues app on Microsoft Teams mobile (iOS and Android) allows calling representatives and supervisor leads to manage call queues and handle customer calls while away from their desks. This update extends existing Queues functionality to the Teams mobile app, enabling users to manage queue participation and review call activity from a mobile device.

This message is associated with Microsoft 365 Roadmap ID 559386.

[When this will happen:]

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

[How this affects your organization:]

Who is affected:

• Organizations using Microsoft Teams Phone
• Users licensed with Teams Phone and Teams Premium
• Calling representatives and supervisor leads managing call queues
• Teams mobile app users (iOS and Android)

What will happen:

• Calling representatives and supervisor leads will be able to:
  • View the call queues they are assigned to directly from the Teams mobile app.
  • Review queue details, including the full list of queue members.
  • View queue-related call history on mobile devices.
• Calling representatives will be able to:
  • Opt in or opt out of queue call routing while on the go.
• Supervisor leads will be able to:
  • Bulk manage queue participation for their teams from mobile
• The experience:
  • Is enabled by default for eligible users.
  • Respects existing licensing, policies, and administrative controls.
  • Matches the governance model of the desktop Queues app.

This mobile access helps teams respond faster, manage calls more efficiently, and maintain a consistent customer experience regardless of location.

Screenshot 1: Queues home view:

Screenshot 2: Queue details view:

[What you can do to prepare:]

No action is required.

You may optionally:

• Ensure impacted users are licensed with Teams Phone and Teams Premium.
• Inform calling representatives and supervisor leads who rely on mobile-first workflows about this new capability.
• Update internal helpdesk or user documentation to reference mobile queue management.

Learn more: Manage Queues app for Microsoft Teams – Microsoft Teams | Microsoft Learn (will be updated before rollout)

[Compliance considerations:]

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

[Introduction]

We’re enhancing Customer Connect in Microsoft Teams by adding appointment booking, enabling customers to book follow-up meetings directly from your business website. This helps small businesses turn website conversations into scheduled consultations and ensures appointments are automatically managed in Teams and staff calendars.

This message is associated with Microsoft 365 Roadmap ID 557172.

[When this will happen:]

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

[How this affects your organization:]

Who is affected:

• Microsoft 365 tenants using Customer Connect in Microsoft Teams
• Customers licensed for Microsoft 365 Business Basic, Business Standard, or Business Premium
• Teams administrators who manage Customer Connect settings

What will happen:

• Website visitors can schedule appointments directly through the embedded Customer Connect widget.
• Scheduled appointments are automatically:
  • Added to the assigned staff member’s Outlook calendar
  • Posted to the Customer Connect requests channel with appointment details
• No changes occur to the existing Customer Connect experience until an admin enables and configures appointment scheduling.
• Each tenant can assign up to 25 users as Customer Connect support agents.
• Note: Customer Connect was previously released under the name Live Chat in Teams. Documentation may refer to both names while the naming transition is in progress. Refer to MC1287369 for more information.

[What you can do to prepare:]

• Set up Customer Connect in Microsoft Teams if not already configured. Learn more: Set up and manage live chat | Microsoft Learn.
• Enable appointment scheduling from the Teams Admin app.

Screenshot:  Admin enables Customer Connect appointment scheduling and assigns staff availability:



• Configure appointment settings, including:
  • Adding or removing staff eligible for appointments
  • Defining staff availability hours
  • Creating, editing, or removing appointment types offered to customers
• Review internal support processes and update documentation or helpdesk guidance as needed.

[Compliance considerations:]

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

[Introduction]

We are introducing a unified Apps experience for SharePoint Embedded in the SharePoint admin center. This update simplifies app creation, and installation by centralizing the app lifecycle and reducing dependency on Global administrators. SharePoint Embedded administrators can manage apps, ownership, and billing from a single location, streamlining setup and ongoing administration.

With this experience, administrators can create and install SharePoint Embedded apps directly from the SharePoint admin center and then share the Microsoft Entra app ID and SharePoint Embedded app ID (also known as the container type ID) with developers for ongoing development and management.

[When this will happen:]

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

[How this affects your organization:]

Who is affected:

• Administrators responsible for managing SharePoint Embedded in the SharePoint admin center.
• Organizations using or planning to use SharePoint Embedded apps.

What will happen:

• A new Apps page will appear under SharePoint Embedded in the SharePoint admin center.
• Administrators can create and install SharePoint Embedded apps directly from the SharePoint admin center, without requiring Global admin consent.
• Administrators will have a centralized view to manage SharePoint Embedded apps, including:
• Installed apps: SharePoint Embedded apps currently installed in your organization, including apps developed internally or by external organizations.
• Owned apps: All SharePoint Embedded apps created by your organization, regardless of installation status.
• From this experience, administrators can:
• Create a new Microsoft Entra app or attach an existing Entra app during SharePoint Embedded app creation.
• Assign up to three owners to manage app settings and billing.
• Configure billing based on organizational deployment needs.
• When creating an app, administrators must select a billing type. This setting is permanent and cannot be changed after creation:
• User org: Billing is managed by the user organization. An admin in the user organization must configure pay‑as‑you‑go billing for SharePoint Embedded in the Microsoft 365 admin center.
• Owner org: Billing is managed by the app owner’s Microsoft 365 subscription.
• If Owner org billing is selected:
• Billing can be configured immediately by linking a subscription, or it can be set up later.
• Apps remain inactive until billing is configured.

[What you can do to prepare:]

• Ensure administrators responsible for SharePoint Embedded app management have the SharePoint Embedded Administrator role.
• If using Owner org billing, confirm that administrators have access to an appropriate billing subscription.
• Review internal guidance for developers on how to obtain the Microsoft Entra app ID and SharePoint Embedded app ID from admins.

No user action is required.

[Compliance considerations:]

The change introduces a new admin experience in the SharePoint admin center for creating and managing SharePoint Embedded apps.

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

[Introduction]

We’re updating how agents in SharePoint work to provide a simpler experience for agents selected on a site.

As a refresher, Get started with agents in SharePoint – Microsoft Support, there are two types of agents in SharePoint:

• Ready-made agent – Every SharePoint site comes with a “ready-made agent”, automatically scoped to the content on that site. These agents, scoped to the SharePoint site, require no building from site admins or site owners. 
• Custom-built agent – With site editing permissions, you can create custom agents with a specific content scope, identity, and behavior.

With this update, we’re introducing a new Site AI settings to give site owners more control over which agents are highlighted on their sites. Approved agents will no longer appear in the Agent Picker, so these agents should be placed directly on the site page for better discoverability.

[When this will happen]

General Availability (Worldwide): We began rolling out in mid-November 2024 and expect rollout to complete by mid-June 2026 (previously early June).

[How this affects your organization]

Who is affected

• All Microsoft 365 tenants using SharePoint Online
• Site owners and content authors managing how custom agents are discovered on their site

What will happen

• Site owners will manage the site’s “Default” agent through the main agent setting in the new Site AI settings panel in SharePoint site settings.
• For existing sites, the current “Default” agent will automatically become the site’s main agent.
• For new sites, the main agent will be the ready-made agent
• Users no longer access approved agents through the agent picker and overflow menu in the chat pane. All approved agents remain in the Site Assets\Copilots\Approved folder.
• To help users discover agents, site owners and builders should surface agents directly on pages using supported web parts or shared agent links.

This feature is on by default and does not require tenant-level configuration changes.

[What you can do to prepare]

No immediate admin action is required. We recommend the following preparation steps:

• Ask site owners and builders to review the approved agents on their sites in the Site Assets\Copilots\Approved folder.
• Encourage site owners to add or update agent links on pages using supported web parts, such as: Agent Link web part, Editorial Card web part, and adding shared .agent file links in Text web part
• Inform users that agents they recently used can be found in:
• • Build “Owned by me” section by choosing the Agents filter,
  • OneDrive web Home > Recent view (filterable by agent), or
  • Microsoft 365 Copilot agents list

Learn more:

• Use the Agent Link web part | Microsoft Support
• Use the Editorial Card web part | Microsoft Support
• Add text, tables, and images to your page with the Text web part | Microsoft Support 

[Compliance considerations] 

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

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

[Introduction]

Microsoft Teams Rooms on Android (MTR-A) will support joining webinars and structured meetings with a dedicated attendee experience. Structured meetings are meetings where organizers restrict presenter permissions and assign attendee roles. This update enables room devices to join these event types as attendees and use attendee features during the session. This capability requires Teams Rooms Pro.

This message is associated with Microsoft 365 Roadmap ID 547824.

[When this will happen:]

General Availability (Worldwide): Rollout begins in late June 2026 and is expected to complete by mid-July 2026.

GCC: Rollout begins in late June 2026 and is expected to complete by early July 2026.

GCC-H: Rollout begins in late August 2026 and is expected to complete by early September 2026.

DoD: Rollout begins in late September 2026 and is expected to complete by early October 2026.

[How this affects your organization:]

Who is affected:

• Organizations using Microsoft Teams Rooms on Android (MTR-A) with Teams Rooms Pro licenses
• Admins managing Teams Rooms devices and meeting policies
• Users joining webinars or structured meetings from conference rooms

What will happen:

• Microsoft Teams Rooms on Android (MTR-A) devices can join webinars and structured meetings as attendees from the room console.

Screenshot 1: Webinar front-of-room experience:



Screenshot 2: Webinar console view:



• Rooms will use an attendee role-based experience, separate from presenter controls and views.
• When enabled by meeting options, room attendees can use:
  • Chat
  • Reactions
  • Raise hand
  • Captions
  • Participant roster and visibility controls
• Rooms no longer require a separate personal device to participate in these sessions.
• Layouts are optimized for single-screen and dual-screen rooms to emphasize shared content and active speaker or stage view.
• For webinars and structured meetings, the room display (front‑of‑room) can be restricted to curated stage content, using managed or on‑stage view behavior.
• Organizers can include rooms as attendees; attendee identity may not be shown in webinars, depending on event configuration.
• Availability depends on the device running a version of Teams Rooms on Android that supports this feature.
• Rooms can be used for co-viewing webinars and structured meetings, allowing multiple in-room participants to join from a shared device while still accessing attendee features.
• Supports use in large conference rooms and organization-wide events.
• Applicable to scenarios such as training sessions, organization-wide updates, and leadership broadcasts.

[What you can do to prepare:]

• Ensure your Teams Rooms on Android devices are:
  • Enabled and actively managed.
  • Licensed with Teams Rooms Pro (validated at join time)/
• Update Teams Rooms devices to the latest available version.
• Review internal guidance for meeting organizers to:
  • Add rooms as attendees where appropriate.
  • Configure meeting options to allow desired attendee interactions (chat, reactions, etc.).
• Communicate this update to helpdesk and user communities, especially teams that host webinars or large meetings.

Learn more: Host or attend an event from a Microsoft Teams Room (MTR) – Microsoft Support

[Compliance considerations:]

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

• Keep related work together: Use tabs to organize analyses in one workspace, so it’s easier to stay in context as you explore different views or parts of a process.
• Customize your view: Arrange process maps, charts, tables, and metrics in a layout that works best for your analysis and comparisons.
• Choose the insights you need: Work with a range of analysis tiles, including process maps, performance metrics, attribute breakdowns, case lists, and statistical views.
• Filter once, analyze everywhere: Apply a filter one time and use it across your workspace to compare scenarios faster and more consistently.
• Work with complex processes more easily: Object-centric support helps you analyze connected objects, relationships, and cross-object metrics in one experience.

• Year-round HSA/401(k) contribution changes: Allows employees to modify the HSA/401(k) contribution throughout the year. Today, these details can be modified only during the benefits enrollment period.
• Automatic basic life insurance enrollment: All employees are automatically enrolled in a basic life insurance plan, with the option to add supplemental life insurance if desired. Currently, the basic life insurance is assigned but also prompts for a beneficiary, which shouldn’t be required for the basic plan. Additionally, if an employee doesn’t manually check out or select the basic life insurance, it should still be automatically marked as their chosen plan.
• Enablement and configuration: Both features are enabled by admins in Feature management for organizations using the updated Benefits module. HR admins can manage settings in the Benefits management configuration area, where they can choose to allow year-round contribution changes and set rules for automatic life insurance enrollment. Admins can disable either feature from Feature management.

• Continuous, streaming dashboards: Monitor mission-critical KPIs such as queue backlog, service level, abandon rate, and representative presence as they change in seconds, with anomaly detection surfaced through visual alerts.
• Full-screen wallboards for the floor: Display live metrics on high-resolution monitors across the contact center floor, giving the whole team a shared, at-a-glance view of performance.
• Industry-aligned metric definitions: Standardized metric definitions that follow industry conventions, ensuring consistent, comparable numbers across teams and tools.
• Drill-down analytics: Move from a high-level view into queue-level and representative-level detail to assess performance and pinpoint issues.
• Representative-level insight: Review live details such as presence status, available capacity, and conversations answered over time.
• Immediate corrective actions: Address declining performance in the moment by moving representatives between queues and updating presence, skills, and capacity profiles instantly.
• In-context conversation management: View conversation details and assign or transfer directly from the dashboard.

• Start with a redesigned research experience organized around how sellers work—understand the deal, identify priorities, decide next actions, and explore details only when needed.
• Get instant deal context through an enhanced deal header that surfaces key information including opportunity details, sales stage, deal value, close date, overall risk indicators, and freshness of insights.
• Review a concise opportunity summary that explains what is happening in the deal, what is progressing well, what may be blocking momentum, and the recommended next action.
• Quickly identify the highest-priority risks with clear descriptions, supporting evidence, business impact, and a recommended action for each item.
• Discover additional actionable insights presented as easy-to-scan cards that highlight important observations and opportunities to improve deal outcomes.
• Expand detailed research sections including stakeholders, customer pain points, account context, competitive landscape, and opportunity health, only when you need deeper context.
• Understand how insights were generated through transparency indicators that show contributing sources such as CRM data, emails, meetings, and external signals to help build confidence in recommendations.

• Optimize schedules for up to 5 resources directly from the schedule board.
• Optimize schedules for up to 30 resources using an optimization plan.
• Create custom goals and weight objectives.
• Create custom optimization scopes to use with your optimization plans.

• Understand customer, opportunity, and pipeline context without manually gathering information from multiple systems.
• Identify changes, risks, engagement patterns, and areas that require attention.
• Prioritize work across customers, opportunities, leads, and pipeline activities.
• Generate recommendations and next-best actions based on available business context.
• Analyze business performance, pipeline health, and sales execution trends.
• Support decision-making across individual, team, and organizational sales workflows.