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

Updated June 17, 2026: We have extended the Preview timeline. General Availability will be announced at a later date. Thank you for your patience. 

[Introduction]

Note: You’re receiving this message because you are part of our early access program.

Smart Calendar is the next-generation calendar experience that will be built into Classic Outlook for Microsoft 365 Copilot-licensed users. It combines the familiar Outlook interface with Copilot-powered intelligence and a modern, responsive design, making time management simpler, smarter, and more intuitive. This calendar will be available for users inside Classic Outlook. Once Smart Calendar is released, users will get an information banner in Outlook Calendar to Try the new app.

This update introduces several key benefits:

• Copilot Intelligence: Prepare, schedule, coordinate, and recap meetings with Copilot assistance.
• Effortless Scheduling: Create meetings using natural language, get smart room suggestions, and receive RSVP recommendations.
• Seamless Coordination: Automatically adjust meetings and rebook rooms when conflicts arise.
• Follow Through: Get concise recaps, transcripts, and actionable follow-ups, even for meetings you missed.
• No Learning Curve: Built directly into Classic Outlook, no separate install required. Smart Calendar coexists alongside the classic calendar.

Smart Calendar helps unlock advanced time management capabilities and realize the full value of your Microsoft 365 Copilot investment. It offers effortless activation and minimal change management for IT teams, operating within Microsoft 365’s existing security, compliance, and data protection boundaries.

[When this will happen:]

• Public Preview: Rollout begins in early November 2025 and completes by end of July 2026 (previously late January)
• General Availability: We will announce via Message center when we are ready to proceed. 

[How this affects your organization:]

• Who is affected:
• Users with Microsoft 365 Copilot licenses using Classic Outlook (Win32).
• A Microsoft 365 Copilot license is required to use this feature.
• Some of the features are in early stages of release and may reach you later.

• What will happen:
  • Users will see a banner in Outlook Calendar inviting them to Try the new app.

  

  • Smart Calendar will be available alongside the classic calendar—no replacement or removal.

  

  • Copilot features will assist with scheduling, coordination, and follow-ups.
  • No separate installation is required; Smart Calendar is built into Classic Outlook.
  • Existing admin policies and calendar settings remain unchanged.

Note: You may notice that in some cases the UI currently shows Copilot Calendar instead of Smart Calendar. This is expected during the early rollout phase. The name change to Smart Calendar has already been released and is gradually rolling out to all tenants. Once the update reaches your environment, the UI will reflect the new name. No action is required on your part.

[What you can do to prepare:]

• Communicate the upcoming changes and benefits to users with Copilot licenses.
• Ensure eligible users have Microsoft 365 Copilot licenses to access Smart Calendar.
• Encourage users to share feedback for continuous improvement.
• Update internal documentation if you detail calendar features or workflows.

[Compliance considerations:]

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

[Introduction]

To streamline and modernize reporting experiences across Microsoft 365, we are retiring the Outlook for Windows Usage Report in the Exchange admin center (EAC). Admins can continue accessing Outlook usage information in the Microsoft 365 admin center (MAC), which offers a more complete and up‑to‑date reporting experience across Microsoft 365 apps.

[When this will happen]

• Retirement will begin in mid-August 2026 (previously mid-June).
• Retirement will complete in mid-September 2026 (previously mid-July).

[How this affects your organization]

Who is affected

• Admins who use the Exchange admin center (EAC) to view Outlook for Windows usage data.

What will happen

• The Outlook for Windows Usage Report will be removed from the EAC.
• No replacement Outlook usage reporting will remain in the EAC after this retirement.
• Admins can continue accessing Outlook for Windows usage insights through the Microsoft 365 admin center (MAC): Reports > Usage > M365 Apps > Usage > Outlook for Windows
• MAC provides consolidated usage reporting with charts and tables to help admins understand usage patterns across Outlook and other Microsoft 365 apps.
• No impact to Outlook for Windows functionality for users.
• This report retirement will occur automatically; no opt‑out or admin toggle will be available.

[What you can do to prepare]

• No admin action is required.
• If your organization references the EAC usage report in documentation or internal processes, update those materials before the retirement is complete.

Learn more: Microsoft 365 Reports in the admin center – Microsoft 365 Apps usage | Microsoft 365 | Microsoft Learn

[Compliance considerations]

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

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

[Introduction]

We’re adding the ability to preview content directly within Insider Risk Management (IRM) alerts in Microsoft Purview. This enhancement removes the need to create a case to view potentially risky content, helping investigators quickly evaluate alerts and accelerate triage. This feature aligns with customer feedback requesting faster, more streamlined investigation workflows.

This message is associated with Microsoft 365 Roadmap ID 557189.

[When this will happen:]

• Public Preview: Rolling out in early April 2026 and expected to complete by late April 2026.
• General Availability (Worldwide, GCC, GCC‑High, DoD): Rolling out in early July 2026 (previously mid‑June) and expected to complete by late August 2026 (previously late July).

[How this affects your organization]

Who is affected:

• Organizations using Microsoft Purview Insider Risk Management.
• Only users with Investigator permissions will have access to content preview.

What will happen

• A new Content preview tab will appear within activity details in IRM alerts: 

  

• Investigators will be able to view supported content directly from the alert without creating a case.
• Supported activity types include:
  • Viewing, downloading, syncing, or sending activities involving content from SharePoint, OneDrive, or Exchange.
• Unsupported activity types include:
  • State changes, permissions changes, deletions, and Endpoint activities.
• The feature is enabled by default for tenants licensed for Insider Risk Management.
• No impact on end‑user experience outside of investigators handling alerts.

[What you can do to prepare]

No action is required to enable this feature.

If your organization uses IRM for investigations, you may want to:

• Confirm which users hold Investigator permissions.
• Update internal investigation workflows or playbooks to reflect new alert‑level content preview.
• Inform your security operations or compliance teams of the new capability.
• Review supported content preview scenarios documented here:
• Learn more about investigating alerts in Insider Risk Management.
• To use content preview when available:
  • Navigate to Insider Risk Management.
  • Open Alerts.
  • Select an alert.
  • Open an activity marked as content preview available.
  • View content in the Content preview tab.

Learn more: Investigate Insider Risk Management activities | Microsoft Purview | Microsoft Learn

[Compliance considerations]

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

Updated June 17, 2026: We have decided to pause rollout of this feature at this time. We will communicate via Message center when we are ready to proceed. Thank you for your patience. 

[Introduction]

We’re making a change to the characters allowed in naming and description fields across Microsoft Purview eDiscovery. As part of ongoing security hardening efforts, this update strengthens input validation for eDiscovery cases, holds, searches, and review sets to improve service resilience and reliability.

[When this will happen:]

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

[How this affects your organization:]

Who is affected:

Organizations with users or administrators who create or manage Microsoft Purview eDiscovery:

• Cases
• Holds
• Searches
• Review sets

What will happen:

• Beginning May 15th, 2026, the following special characters will no longer be permitted in naming or description fields when creating or editing:
  • + (plus sign) 
  • = (equals sign) 
  • @ (at sign) 
  • / (forward slash) 
  • * (asterisk) 
• This restriction applies to:
  • Case name and description
  • Hold policy name and description
  • Search name and description
  • Review set name and description
• Existing entities are not affected.
  • Cases, holds, searches, and review sets that already contain these characters will continue to function normally.
• Editing triggers enforcement:
  • If a user edits an existing entity’s name or description (e.g., updating an eDiscovery case name) that contains a restricted character, they will see a validation message prompting them to remove the special character before saving. Note that this does not apply when an existing hold policy is being reapplied or when data sources are added to or removed from hold policies.
  • The original name and description are preserved until the user chooses to make changes.
• New entities are enforced immediately:
  • Any newly created case, hold, search, or review set must not contain restricted characters in name or description fields.

[What you can do to prepare:]

No admin action is required to enable this change. However, we recommend the following:

• Inform your eDiscovery users that the characters + = @ / and * will no longer be accepted in entity names and descriptions.
• Review and update existing naming conventions or templates that include these characters.
• Update internal documentation or guidance for eDiscovery naming standards.
• Communicate this change to helpdesk and compliance teams to prepare for validation messages when editing existing entities.

Learn about eDiscovery (Premium) | Microsoft Learn

No data loss will occur. Existing entities retain their current names and continue to function. Enforcement applies only at the time of creation or editing.

[Compliance considerations:]

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

Updated June 16, 2026: We have updated the content under ‘who is affected’. Thank you for your patience. 

[Introduction]

To balance organizational branding with user flexibility, administrators will be able to control whether users can change the default compose font in Outlook for iOS and Android. When a default font name or size is set using Microsoft Intune app configuration policies, new configuration keys will allow administrators to decide if users can modify those defaults.

[When this will happen]

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

[How this affects your organization]

Who is affected

• Administrators managing Outlook for iOS and Android using Microsoft Intune
  • This release applies to phones, iPad, and tablets
• Users only if administrators enable user changes

What will happen

• Today, when a default compose font name or size is configured through Intune app configuration, users cannot change it.
• With this update, administrators will be able to optionally allow users to change:
  • The default font name
  • The default font size
  • Both
• Two new Intune app configuration keys will be available:
  • com.microsoft.outlook.Settings.defaultFontName.UserChangeAllowed
  • com.microsoft.outlook.Settings.defaultFontSize.UserChangeAllowed
• By default:
  • Both keys will be set to false, preserving existing behavior.
  • No changes will occur unless an administrator enables them.
• The keys will apply only when the corresponding default font setting is already configured.
• If a user changes the font:
  • The administrator-configured default will no longer apply for that user.
  • Future administrator updates will not override the user’s selection.
  • There is no automatic reset to the administrator-defined value.
• This feature will be off by default and requires explicit administrator configuration.

[What you can do to prepare]

No action is required to maintain the current locked-font behavior.

Optional (recommended):

• Review your Intune app configuration policies for Outlook for iOS and Android.
• To allow user changes:
  • Set com.microsoft.outlook.Settings.defaultFontName.UserChangeAllowed to true to allow font name changes.
  • Set com.microsoft.outlook.Settings.defaultFontSize.UserChangeAllowed to true to allow font size changes.
• Update internal documentation or helpdesk guidance as appropriate.

[Compliance considerations]

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

Introduction

With Microsoft Purview enabled in Microsoft Foundry, Purview admins can apply inline data loss prevention (DLP) policies to prompts used in Foundry-built apps and agents. This helps prevent sensitive data from being shared through prompts and supports stronger data protection and compliance for AI-driven workflows.

This message is associated with Microsoft 365 Roadmap ID 558565.

[When this will happen:]

• Public Preview: We will begin rolling out in mid-May 2026 and expect to complete by early June 2026.
• General Availability (Worldwide): Rollout will begin in October 2026 (previously mid-June) and is expected to complete by end of October 2026 (previously late June).

[How this affects your organization:]

Who is affected:

• Admins managing Microsoft Purview and Microsoft Foundry
• Organizations building or using apps and agents in Microsoft Foundry

What will happen:

• When your organization builds AI apps and agents on Microsoft Foundry, Foundry admins can enable Microsoft Purview by configuring the Purview toggle in Foundry, allowing Purview to manage how these apps and agents interact with data.
• Security admins can ensure the data security and compliance posture of how these apps and agents interact with data by setting up DLP policies for prompts in Microsoft Purview Data Loss Prevention (DLP).
• Admins can configure Microsoft Purview DLP policies to evaluate prompts submitted to Foundry apps and agents.
• Policies can detect and help prevent the sharing of sensitive information in prompts to large language models (LLMs)..
• DLP enforcement occurs inline as prompts are submitted.
• This feature supports existing Microsoft Purview DLP capabilities and integrates with current compliance workflows.
• No change occurs unless admins create or enable DLP policies for this scenario (admin configuration required).
• Foundry-based DLP capabilities follow a pay-as-you-go model. Microsoft Purview must be enabled with a pay-as-you-go subscription for this feature to work.

[What you can do to prepare:]

• Review your current Microsoft Purview DLP policies and identify scenarios that should apply to AI prompts.
• Create and use DLP policy simulation mode to understand what data is being exchanged with AI apps and agents before enforcing policies.
• Plan internal guidance for admins and compliance teams on managing prompt-level DLP.
• Update internal documentation to include this capability if you use Microsoft Foundry apps and agents.

Learn more:

• Manage compliance and security in Microsoft Foundry – Microsoft Foundry | Microsoft Learn 
• Use Microsoft Purview to manage data security & compliance for Microsoft Foundry | Microsoft Learn

[Compliance considerations:]

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

[Introduction]

We’re updating the Collect Diagnostics feature name to Get Diagnostics for Outlook Mobile and Outlook for Mac. Along with this rename, diagnostic logs sent during support interactions will now be routed through the Microsoft 365 diagnostics service instead of the legacy PowerLift service. This change aligns Outlook with other Microsoft clients, simplifying support workflows and providing a more consistent diagnostics experience.

[When this will happen:]

General Availability (Worldwide): Rollout will begin in late July 2026 (previously early June) and is expected to complete by mid-August 2026 (previously late June).

How this affects your organization:

Who is affected:

• Organizations using Outlook Mobile (iOS and Android)
• Organizations using Outlook for Mac
• IT admins maintaining documentation referencing Collect Diagnostics

What will happen:

• The feature name changes from Collect Diagnostics to Get Diagnostics in Outlook Mobile and Outlook for Mac.
• Diagnostic logs will be sent to the Microsoft 365 diagnostics service instead of the PowerLift service.
• There is no change to user workflow or behavior beyond the updated name.
• No admin configuration changes are required.
• The feature remains enabled by default.

What you can do to prepare:

• Update internal documentation, training materials, and helpdesk scripts to reflect the new name Get Diagnostics.
• Review network allowlists:
  • Outlook Mobile and Outlook for Mac will no longer use the *.acompli.net endpoint for Get Diagnostics.
  • The *.acompli.net endpoint is still required for:
    • Outlook Contact Support
    • Other Microsoft clients such as Company Portal and Microsoft Authenticator
• No other action is required if *.acompli.net is already allowlisted.

Learn more: Outlook for iOS and Android in Exchange Online: FAQ | Microsoft Learn

Compliance considerations:

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

Expected with Intune’s June (2606) service release, we are making an update to the Microsoft Intune admin center to streamline where admins configure Microsoft 365 Apps policy settings. Currently, the same policy configuration experience is available in both the Microsoft Intune admin center (Apps > Policies for Microsoft 365 apps) and the Microsoft 365 Apps admin center (Customization > Policy management). To provide a more consistent and centralized management experience, we will remove the ability to configure these policies in the Intune admin center. Instead, the page will be updated to provide a direct link to the Microsoft 365 Apps admin center where this functionality will continue to be available.

[How this will affect your organization:]

If you are accustomed to creating or editing Microsoft 365 Apps policies directly within the Intune admin center, you will need to use the Microsoft 365 Apps admin center to perform these tasks.

Important: There is no change to configured policies, functionality, or the configuration experience, the user interface is identical to the existing experience in the Intune admin center. There is no change to the required roles or permissions needed to create or manage policies. Additionally, this change does not affect Microsoft 365 apps policies created through Intune settings catalog.

[What you need to do to prepare:]

Update your IT admin guidance and documentation as needed. No additional action is required to retain existing policy functionality.

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

[What and Why] 

• A Microsoft 365 Copilot license to access the experience.
• Usage-based billing enabled via Copilot Credits

• Worldwide (General Availability – Standard Release): Beginning mid-June 2026 and expected to complete late June 2026
• Worldwide (General Availability – Deferred Release): Beginning mid-June 2026 and expected to complete late June 2026.
• Rollout occurs automatically; visibility depends on eligibility and admin configuration

• Microsoft 365 Admins
• End users who accessed Copilot Cowork via the Frontier program prior to June 16, 2026

• Microsoft 365 Copilot app (web, Windows, macOS, iOS, Android)
• Microsoft 365 admin center
• Microsoft Edge (for browser-based workflows)
• Microsoft Purview
• Copilot plugin ecosystem

• Copilot Cowork becomes generally available
• Updated UI and entry point for Copilot Cowork
• Access to Copilot Cowork requires a Microsoft 365 Copilot license and usage-based billing enabled
• If usage-based billing is not enabled, users won’t be able to access or use Cowork. Admins can control the discoverability of Copilot Cowork and consumptive features (Copilot Settings> AI experiences enabled by usage-based billing)
• Usage is billed via Copilot Credits
• A new Cost Management dashboard in the Microsoft 365 admin center gives admins visibility and control over billing configuration, spending policies, and usage reporting.

• Communicate this change to helpdesk and 6/30 deadline to your end users
• Estimate spend and review which users should have access to Copilot Cowork
• Update internal guidance for Copilot usage and cost governance

• Copilot Credits overview
• Copilot Credit Licensing Guide
• Cowork Estimator
• Cowork documentation

[Compliance considerations]

• This service generates and stores customer data and supports the following capabilities: Purview eDiscovery, Data Retention, Purview Sensitivity Labels, Tenant Restrictions, Token Protection, Audit Logging, Customer Lockbox, Role-Based Access Control, Active-Active Hosting, Third Party Pentest Report, Customer Key, Data Export Capability, Incident Notification, Service Level Agreement.
• This service supports: Data Residency (Data At Rest).
• GPT-5.5 in Copilot Cowork available in Frontier respects EU Data Boundary commitments
• This service provides a method of communication and supports the following capabilities: Information Barriers, Purview Communication Compliance.
• This service provides a method of communicating with generative AI and supports the following capabilities: Purview Communication Compliance.
• Customer administrators can control user access to this service using the following interfaces: Licensing, Admin center UI, PowerShell Cmdlet, Admins have user/group granularity for controlling access to the service, Users have opt-in or opt-out options for use of the service.

[What and Why:]

We’re introducing Extensions monitoring in the Microsoft Edge management service to give administrators greater visibility and control over browser extensions used across their organization. This update supports enterprise-ready security and manageability by helping admins identify installed extensions, evaluate risk, and streamline the process of reviewing and approving extension requests—all from a centralized experience.

This message is associated with Microsoft 365 Roadmap ID 552597.

[Rollout Schedule:]

• Public Preview (Worldwide): Rollout is completing mid-June 2026
• General Availability (Worldwide): We will begin rolling out in mid-June 2026 and expect to complete by mid-June 2026.

[Impact on Your Organization:]

Who is affected:

• Admins who manage Microsoft Edge using the Edge management service
• Organizations using configuration policies for managed users

Platforms/Services:

• Microsoft Edge
• Edge management service (web-based admin experience)
• Configuration policies

What will happen:

• A new page called Extension monitoring will be available in the Edge management service.
• Admins will be able to view a consolidated list of extensions installed across managed users (after enabling the feature).
• Admins will be able to manage extension requests across all configuration policies from a single location.
• The feature is not enabled by default and must be turned on to view extension data.
• No changes will occur to user workflows unless the feature is enabled and actively managed by admins.

[Action Required/Recommendations:]

No action is required before the rollout.

After rollout, we recommend:

• Enable the Extension monitoring feature in the Edge management service to begin using it.
• Review installed extensions across your managed users for security and compliance alignment.
• Establish or update your internal process for handling extension requests.
• Communicate this capability to your security and endpoint management teams.

Learn more:

• Microsoft Edge Extensions Monitoring | Microsoft Learn
• Get started with configuration policies | Microsoft Learn

[Compliance considerations:]

[What and Why:]

Starting July 2026, we’re introducing a new People Skills removal and deletion admin control. This feature enables administrators to permanently remove all People Skills data from their tenant.

This update gives organizations greater control over their Microsoft 365 data by supporting offboarding scenarios for People Skills and helping meet enterprise data governance and compliance needs. People Skills is an AI-powered service that creates and uses skills data across Microsoft 365 experiences such as Copilot, profile cards, and Viva. Learn more about People Skills.

This message is associated with Roadmap ID 565905.

[Rollout Schedule:]

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

[Impact on Your Organization:]

Who is affected: 

Tenants that have already deployed People Skills and those who will deploy it in the future can use this new feature, including those with:

• People Skills Foundation service plan
• People Skills Advanced service plan
• Microsoft 365 Copilot in Productivity Apps

Platforms/Services where skills data appears:

• Microsoft 365 profile card
• Microsoft 365 Copilot
• Viva Insights
• Viva Learning
• Org Explorer and People experiences

What will happen:

• A new People Skills removal and deletion control will be available in admin settings.
• This feature is admin-initiated only.
• When initiated:
• The organization’s skills library and all associated data will be permanently deleted.
• All user skills (confirmed, inferred, imported) will be permanently deleted.
• Skills will no longer appear on profile cards.
• Skills data will no longer be used in Copilot, Viva Insights, or other experiences. For details, refer to: Where does People Skills data appear.
• Deleted data cannot be restored.
• Deletion timing:
  • Most data deleted within 48–72 hours
  • Viva Learning data removed within up to 7 days

[Action Required / Recommendations:]

No immediate action is required.

If your organization needs to remove People Skills (for example, to meet compliance or governance requirements):

• Navigate to: Microsoft Admin Center > People Skills > Manage People Skills for your organization > Settings > People Skills removal and deletion. Refer to our documentation for detailed instructions 
• Review your organization’s data retention and compliance policies before initiating deletion.
• Communicate this change to relevant stakeholders (IT, compliance, helpdesk).
• If you plan to re-enable People Skills later:
  • Reconfiguration is required using Set up People Skills.
  • We recommend you wait at least 7 days before re-enabling to ensure previous data is fully removed.
  • Previously deleted data won’t be restored.

Learn more

• Overview of People Skills | Microsoft Learn
• Manage your skills library in People Skills | Microsoft Learn
• Set up People Skills | Microsoft Learn

[Compliance considerations:]

[What and Why:]

We’re retiring the Send Availability feature in Outlook for iOS and Android. This change aligns with ongoing efforts to simplify mobile email experiences and focus on core productivity workflows. Users can continue to share availability by referencing their calendar and including available times directly in email responses.

[Rollout Schedule:]

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

[Impact on Your Organization:]

Who is affected: All Outlook users on iOS and Android devices

Platforms/Services:

• Outlook for iOS
• Outlook for Android

What will happen:

• The Send Availability feature will be removed from the Outlook mobile compose experience.
• Users will no longer see the Calendar (availability sharing) option while drafting an email.
• There are no changes to calendar functionality itself.
• Users can still check their calendar and manually include available times in email responses.
• This change is enabled by default; there is no admin configuration or override.

[Action Required/Recommendations:]

No admin action is required.

• Inform helpdesk and support teams about this change.
• Update any internal documentation or user training that references the Send Availability feature.
• Advise users to use their calendar to determine availability and share times manually in email replies.

[Compliance considerations:]

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

[What and Why]

We are introducing new administrative controls in Microsoft Teams to help you govern how applications and agents access meeting transcripts through the Microsoft Graph API. These controls provide more granular governance over transcript data, including transcripts with speaker attribution, helping you align access with your organization’s security and compliance requirements.

[Rollout Schedule]

• General Availability (Worldwide):
  •  Rollout of the settings will begin in late June 2026 and is expected to complete quickly.
  •  Enforcement of the controls will begin approximately 30 days after availability (late July 2026).

[Impact on Your Organization]

Who is affected

• Microsoft 365 tenant administrators managing Microsoft Teams and Microsoft Graph API permissions

Platforms/Services

• Microsoft Teams
• Microsoft Graph API

What will happen

New administrative controls will allow you to:

• Allow or block applications and agents from accessing meeting transcripts through Microsoft Graph API
• Apply access controls to transcripts with or without speaker attribution
• Govern access to sensitive transcript data across your tenant

During the 30-day configuration period, existing behavior remains unchanged. After enforcement begins, applications that previously had access via Microsoft Entra Admin Portal permissions will receive access errors if administrators do not explicitly enable transcript access.

[Action Required/Recommendations]

Action is required within 30 days of feature availability to avoid disruption to applications that rely on transcript access.

• Review the new transcript access control settings when they become available.
• Decide whether to enable transcript access for applications and agents with Graph API permissions.
• Configure the settings based on your organization’s security and compliance requirements.
• Administrators can configure these settings in the Teams admin center under:
  • Settings & policies > Meetings (new experience), or
  • Meetings > Meeting settings (classic experience)
• These controls are also available via PowerShell cmdlets.
• Communicate changes to relevant stakeholders, including security and compliance teams.
• Update internal documentation if you track API access policies.

Learn more: 

Documentation for these controls will be available on Microsoft Learn at rollout. Content updates are currently in progress.

• Overview- Recording and transcription for Teams meetings, events, and calls | Microsoft Teams | Microsoft Learn
• Set-CsTeamsMeetingConfiguration | MicrosoftTeams | Microsoft Learn
• Teams settings and policies reference | Microsoft Teams | Microsoft Learn

[Compliance considerations]

[What and Why].

Microsoft is updating the configuration experience for Auto Attendant and Call Queue in the Teams admin center. These improvements streamline key setup steps, improve clarity, and enhance performance to reduce setup time and increase administrator efficiency when managing Voice apps.

[Rollout Schedule]

General Availability

• Worldwide: Rollout began in early June 2026 and is expected to complete by mid-June 2026.
• GCC High and DoD: Rollout will follow after an initial validation period.

[Impact on Your Organization]

Who is affected

•  Admins who configure Auto Attendant and Call Queue in the Teams admin center

Platforms/Services

• Teams admin center (web)

What will happen

• The Voice apps configuration wizard experience in the Teams admin center will be updated.
• Admins will see a revised and streamlined configuration flow with fewer steps, improved navigation, and updated configuration experiences.
• Key experience improvements include.
  • New quick and advanced setup entry points from the list view to reduce clicks and improve discoverability of setup options.
  • A new Call handling hours step that consolidates time zone, business hours, and after-hours configuration into a single experience.
  • Renamed and clearer configuration steps for example Call flow is now Business hours call flow.
  • Simplified resource account configuration now included within General info, removing a separate step.
  • Improved defaults such as standard business hours and clearer configuration controls.
  • Updated UI elements including inline messaging, improved tables, and more consistent visual design.
  • Faster and more responsive performance with reduced page reloads and fewer interruptions during navigation.

Screenshot 1 – Quick and advanced setup entry points:

Screenshot 2 – Call handling hours and navigation flow:

Screenshot 3 – Resource account configuration in General info: 

Screenshot 4 – Business hours configuration experience:

• The previous configuration wizard experience will be replaced.
• There is no option to revert to the previous experience. Rollback, if required, is service controlled.
• The updated experience will be enabled by default.
• Existing configurations, call flows, and policies will not be changed.
• There is no impact to Voice apps behavior or user experience.

[Action Required/Recommendations]

• No action is required.
• Inform your Teams administrators about the updated configuration experience.
• Review Microsoft Teams admin center documentation for Voice apps configuration.
• Update any internal documentation or training materials that reference the previous wizard steps.
• If you provide internal support for Voice apps, ensure helpdesk staff are aware of the updated configuration flow.

[Compliance considerations]

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

[What and Why]

The file selector enables users to quickly find and select the files they want Excel Agent to process, all in one place. This improves the file selection experience by making it easier to locate relevant content and use Excel Agent more efficiently.

[Rollout Schedule]

• General Availability (Worldwide): Rollout began in late May 2026 and is expected to complete by late June 2026.

[Impact on Your Organization]

Who is affected

• Users of Excel Agent

Platforms/Services

• Microsoft Excel

What will happen

• Users will see a new file selector when using Excel Agent: 

  

• Users can browse and select files in a centralized experience.
• The feature simplifies selecting files for processing.
• The feature is available by default.
• Existing file permissions are respected.

[Action Required/Recommendations]

No action is required.

Recommended:

• Inform users about the new file selection experience.
• Update internal documentation if your organization documents.

Learn more: 

• Frequently asked questions about Word, Excel, and PowerPoint Agents: Responsible AI FAQ | Microsoft 365 Copilot | Microsoft 365 | Microsoft Learn
• Get started with Word, Excel, and PowerPoint Agents in Microsoft 365 Copilot | Microsoft 365 Copilot | Microsoft 365 | Microsoft Learn

[Compliance considerations]

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

[What and Why]

We are introducing enterprise search in Excel Agent within Microsoft 365 Copilot. Users can search for enterprise content (file, email, meeting, chat, people, transcript) in Excel Agent and use that content as grounding to generate contextually relevant answers. This helps users quickly find and use organizational knowledge directly in their workflow.

[Rollout Schedule]

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

[Impact on Your Organization]

Who is affected

• Users with Microsoft 365 Copilot using Excel Agent

Platforms and Services

• Microsoft 365 Copilot
• Excel Agent

What will happen

• Users can search enterprise content directly in Excel Agent: 

  

• Supported content includes files, emails, meetings, chats, people, and transcripts.
• Results can be used as grounding for Copilot responses.
• The feature is enabled by default.
• Existing permissions and security trimming are respected.
• No admin configuration changes are required.

[Action Required or Recommendations]

No action is required.

Recommended actions:

• Inform helpdesk and end users about this new capability.
• Update internal documentation if your organization documents Copilot capabilities.

Learn more: 

• Frequently asked questions about Word, Excel, and PowerPoint Agents: Responsible AI FAQ | Microsoft 365 Copilot | Microsoft 365 | Microsoft Learn
• Get started with Word, Excel, and PowerPoint Agents in Microsoft 365 Copilot | Microsoft 365 Copilot | Microsoft 365 | Microsoft Learn

[Compliance considerations]

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

[Introduction]

The OneDrive mobile Shared view is being updated with a streamlined two-tab layout to make it easier to find and manage shared files on mobile devices. The With you tab shows files others have shared with you, while the By you tab shows files you’ve shared with others. This update aligns the mobile experience with the current web experience for greater consistency. The updated experience also adds new sorting options, file type filters, and at-a-glance visibility into recent sharing and editing activity.

[When this will happen:]

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

[How this affects your organization:]

Who is affected:

• All users who access OneDrive on mobile devices, including iOS, Android, and iPad.

What will happen:

• Users will find a new two-tab Shared experience in the OneDrive mobile app:
  • With you: Files others have shared with the user.
  • By you: Files the user has shared with others.
• Users can sort shared files and filter by file type.
• Recent sharing and editing activity is visible at a glance.
• The update is enabled by default.
• Existing sharing permissions and policies are unchanged.

[What you can do to prepare:]

No admin action is required.

• Notify helpdesk teams of the user interface (UI) update.
• Update internal documentation if applicable.

[Compliance considerations:]

The change updates how shared files are displayed in the mobile UI but does not change data storage, permissions, or compliance controls.

[Introduction]

We’re improving the OneDrive iOS mobile experience to make it easier for users to find and access SharePoint document libraries while on the go. Users will be able to search for libraries by name, browse the updated Libraries view with recent libraries, Teams sites, and Favorite Sites information architecture, use alphabetical sorting, and navigate directly to a site’s default document library (with a breadcrumb to switch between libraries). This update aligns the OneDrive mobile experience more closely with how users access SharePoint document libraries on desktop and web.

[When this will happen]

• General Availability (Worldwide): We will begin rolling out this feature in late June 2026 and expect to complete the rollout by late July 2026.

[How this affects your organization]

Who is affected

• All users accessing OneDrive for Business on mobile devices (iOS)
• Microsoft 365 commercial tenants

What will happen

• Users will see an updated Libraries pivot in OneDrive mobile, with:
  • New Recent, My Teams, and Favorite Sites tabs
  • Sorting by Recently modified and Alphabetical
• Upon rollout, search in OneDrive mobile search will include:
  • SharePoint document libraries
• Users will be able to navigate directly to a site’s default document library from mobile by clicking on the document library or site name. Users will be able to switch between libraries via a dropdown in the header.
• This feature will be enabled by default.
• Existing SharePoint permissions and admin policies will continue to be respected.
• There will be no changes to data storage, sharing behavior, or security controls.
• No features will be retired or removed as part of this update.

[What you can do to prepare]

• No admin action is required.
• Consider the following optional steps:
  • Notify helpdesk staff about the updated OneDrive mobile experience.
  • Update internal documentation or training materials for OneDrive mobile users.
  • Share a brief notice with mobile users about the new Libraries view and expanded search results.

[Compliance considerations]