Microsoft 365
Message Center
Updates and announcements for your Microsoft 365 tenant, ordered by most recently updated.
Posts by product
Based on the services listed in these 686 posts. Posts covering multiple products are counted for each product. Select a product to filter the posts; select it again to show all posts.
686 posts
-
(Updated) Microsoft Entra: Updated passkey registration experience in My Sign-ins
MC1545694 · stayInformed · normal · Updated 11/20/2026 17:59
Services: Microsoft Entra
Read message
Updated November 20, 2026: We have updated the timeline. Thank you for your patience. [What and why] We’re updating the passkey registration experience in My Sign-ins for users registering a passkey in Microsoft Authenticator. Users will see an additional checkbox and updated link text, along with steps to guide users to open Microsoft Authenticator and select the + button to begin registration. If users can’t complete registration directly in Authenticator, the updated link text will help them find the WebAuthn registration flow. [Rollout schedule] General Availability (Worldwide): Beginning in early December 2026 (previously mid-November) and expected to complete by end of December 2026 (previously end-November 2027) [Impact on your organization] Who is affected Users who are guided through My Sign-ins to register a passkey in Microsoft Authenticator Platforms and services Microsoft Entra My Sign-ins and Microsoft Authenticator What will happen Users will see an additional checkbox and updated link text during passkey registration. Users will see steps to open Microsoft Authenticator and select the + button to begin registration: If users can’t complete registration directly in Authenticator, the updated link text will help them find the WebAuthn registration flow. [Action required and recommendations] Inform users about the updated UI and update your internal user guidance to reflect these changes. [Compliance considerations] No compliance considerations were identified. Review as appropriate for your organization. -
(Updated) Clipchamp/ Copilot 'Create a video' experience is going to have an admin control available
MC1518034 · planForChange · normal · Updated 11/20/2026 00:50
Services: Microsoft Clipchamp
Read message
Updated November 19, 2026: We have updated the content. Thank you for your patience. [What and Why:] Microsoft Clipchamp is introducing an admin policy control for the Clipchamp AI video creation experience, also known as Clipchamp 'Generate a video' or 'Create a video' in Copilot Create. This control helps organizations manage which users can access the AI-powered video creation capability. This admin policy will roll-out with default access disabled. Note: As of 19 Nov 2026, the AI video creation feature has been updated to be only available from Clipchamp Home, and removed from Copilot Create & the Clipchamp Editor app. [Rollout Schedule:] General Availability (Worldwide): We will begin rolling out in late November 2026 and expect to complete by early December 2026. [Impact on Your Organization:] Who is affected: Users who have access to Clipchamp Create a video / Generate a video experiences. Admins who manage Microsoft 365 app policies. Platforms/Services: Microsoft Clipchamp Microsoft 365 admin center policy management What will happen: Admins will be able to use policy management to control access to Clipchamp AI video project creation. If your organization wants to disable access, no further action required. If your organization wishes to enable employee access to this feature, the organization admin will have to disable the ‘Turn off Clipchamp AI video project’ policy [Action Required/Recommendations:] No action is required if your organization would like to disable access to the Clipchamp Create a video / Generate a video feature. To enable access after rollout, admins can follow the steps in this support article How to enable or disable features in Clipchamp for users in your organization | Microsoft Support and disable the policy ‘Turn off Clipchamp AI video project’. [Compliance considerations:] QuestionAnswer Does this change include an admin control?Yes. Admins can use policy management to control access to Clipchamp AI video project creation. Does the change provide end users a new way of interacting with generative AI?No. This is not a new generative AI feature. The Create a video experience is an existing feature; this update adds admin control for managing user access. ----------------------------For Processing Do Not Delete------------------------------ Do you need to update your Service description: No Post Publish Date: 10/14/2026 Change type: Feature Product marketing manager: vivnguyen@microsoft.com Major Update: No -
Microsoft Teams: Tenant policy controls who can record and transcribe
MC1560924 · planForChange · normal · Updated 11/20/2026 00:04
Services: Microsoft Teams
Read message
[What and Why:] Teams administrators can use a policy to configure who may start recording and transcription. The policy supports two participant scopes: organizers and co-organizers, or organizers, co-organizers, and presenters. For each scope, administrators can specify whether meeting organizers can or cannot change the setting. This provides a centrally managed default or enforced restriction for meetings organized by users assigned the policy, reducing the need for per-meeting configuration. [Rollout Schedule:] Targeted Release (Worldwide): We will begin rolling out in mid-December 2026 and expect to complete by mid-December 2026. General Availability (Worldwide): We will begin rolling out in late December 2026 and expect to complete by late December 2026. General Availability (GCC): We will begin rolling out in late December 2026 and expect to complete by late January 2027. General Availability (GCC High): We will begin rolling out in mid-February 2027 and expect to complete by late February 2027. General Availability (DoD): We will begin rolling out in mid-February 2027 and expect to complete by early March 2027. [Impact on Your Organization:] A new Who can record and transcribe policy control will be available in the Recording & transcription section of the applicable Teams meeting policy in the Teams admin center. The default value is Organizers, co-organizers, and presenters. Organizers can change, which preserves the current behavior. Administrators can select one of the following four options in a single dropdown: Who can record and transcribe - policy optionBehavior Organizers and co-organizers. Organizers can changeDefaults to organizers and co-organizers. Organizers can also allow presenters through the existing meeting option. Organizers and co-organizers. Organizers can't changeLocks the policy value. Presenters and attendees cannot start recording or transcription. Organizers, co-organizers, and presenters. Organizers can changeDefaults to organizers, co-organizers, and presenters. Organizers can restrict the roles through the existing meeting option. Organizers, co-organizers, and presenters. Organizers can't changeLocks the policy value. The organizer cannot change the role selection. These configurations remain subject to existing recording and transcription availability controls and any sensitivity label that configures this option. Enforcement: When organizer changes are blocked, Meeting options shows the policy value as read-only with a notice that it is locked by meeting policy. The effective role restriction is also enforced when a participant tries to start recording or transcription. Sensitivity labels and templates: A sensitivity label that configures this option takes precedence over the meeting policy. A locked meeting policy takes precedence over a meeting template. An unlocked policy supplies a default. Related meeting options: The existing Who can record and transcribe meeting option remains a Teams Premium or Microsoft 365 Copilot feature. [Action Required/Recommendations:] No action is required. If you do not configure the new policy, existing recording and transcription behavior remains unchanged. If your organization needs to prevent presenters from starting recording or transcription, consider using the new Who can record and transcribe policy. Review policy assignments, sensitivity labels, and meeting templates to confirm the effective behavior. Notify meeting organizers and helpdesk teams of any changes and update internal guidance. [Compliance considerations:] No compliance considerations identified. Review as appropriate for your organization. -
Enhanced prompt categories for Microsoft 365 Copilot in Microsoft Copilot Dashboard and Agent 365 Business Analytics
MC1560923 · stayInformed · normal · Updated 11/20/2026 00:04
Services: Microsoft Viva
Read message
[What and Why:] Enhanced prompt categories for Microsoft 365 Copilot provide a detailed view into Copilot Chat usage by users with a Microsoft 365 Copilot license. Copilot Chat prompts are classified into 13 categories and 41 subcategories, which show how users apply Copilot Chat in their work. The enhanced categories replace the four legacy prompt categories in the Microsoft Copilot Dashboard: "Ask and find," "Catch up," "Draft and brainstorm" and "Other." With this update, leaders and adoption teams can: See how users with a Microsoft 365 Copilot license use Copilot Chat across categories such as finding information, analyzing content, writing and creating content, summarizing content, and more. Break down active users and prompts by category for groups, organizations and job functions, using your existing Copilot Dashboard and Agent 365 business analytics filters. [Rollout Schedule:] General Availability (Worldwide): We will begin rolling out on mid December 2026 and expect to complete by end of December 2026. [Impact on Your Organization:] The four legacy categories are being retired. "Ask and find," "Catch up," "Draft and brainstorm" and "Other" will be removed from the Copilot Dashboard and replaced by the enhanced categories. Enhanced prompt categories apply to Copilot Chat usage by users with a Microsoft 365 Copilot license. Usage of Microsoft 365 Copilot Chat by users without a Microsoft 365 Copilot license isn't included. You'll find the new categories in these places: Microsoft Copilot Dashboard Adoption tab: Shows the number and percentage of Copilot Chat users in each category. Impact tab: Shows the number and percentage of prompts in each category. Agent 365 Business Analytics Use cases page: Treemap view of categories and subcategories, breakdown table by prompt category, heatmap by job function, organization, or group. The dashboard uses the same prompt category names across tenants; no user input prompt text is shown. Anyone who already has Copilot Dashboard or Agent 365 business analytics can view the enhanced prompt categories. There's no separate setting to configure. This change is on by default. [Action Required/Recommendations:] We recommend that you update guidance and training materials that refer to the legacy categories. No admin action is required. [Compliance considerations:] No compliance considerations identified, review as appropriate for your organization. -
Copilot video creation in Clipchamp Video Hub is now live in Frontier Public
MC1560920 · planForChange · normal · Updated 11/20/2026 00:01
Services: Microsoft Clipchamp
Read message
[What and Why:] Copilot video creation is coming to the Clipchamp Video Hub. It turns documents, ideas and work content into videos that make complex information easier to understand and act on. Users start with a prompt, a document from OneDrive, or relevant work context, then preview the video in chat and refine it through conversation until they’re happy with it. This is a usage-based billing (UBB) feature. Each video and subsequent refinements use Copilot Credits, billed through Copilot Credits usage-based billing in the Microsoft 365 admin center. To enable access, admins must enable Anthropic models and configure Copilot Credits spending policies for intended users. Key features: Create from a prompt. Describe the topic, audience, tone and length, or pick a starter prompt. Create in your language. Describe the video in your preferred language and make localized content for audiences worldwide. Base videos on your content. Add a Word document, PowerPoint presentation, images, video or PDF from OneDrive, or draw on relevant work context through Work IQ. Refine through conversation. Ask for changes like "Use a more formal tone", "Make it shorter", "Localize this into Japanese" or "Update the title." Preview in chat. Watch each version without leaving the experience. Export and share. Save the finished video as an MP4. How to get started: Admins first turn on Copilot video creation in a spending policy that includes the right users, in Copilot > Cost management in the Microsoft 365 admin center. Users can then: Open Clipchamp Video Hub [CompanyName].sharepoint.com/_layouts/15/videohub.aspx?vhnav=video-agent-home Go to Create video in the left menu Describe the video, and add files if needed. Preview the video, refine it. Select Export to save it as an MP4. [Rollout Schedule:] Public Preview (Frontier public): available as of November 17, 2026. General Availability (Worldwide): Expected February (timing subject to final confirmation). [Impact on Your Organization:] Users included in eligible spending policies can create and refine videos from work content in Clipchamp Video Hub. Video creation and refinements consume Copilot Credits and appear in Copilot cost management reporting. Governance: Exported videos carry a "Made with AI" watermark, which admins can turn off. Videos only draw on work content the user already has access to. Known limitations at preview: Sensitivity labels: Videos created from documents with a sensitivity label above General can't be downloaded yet but can be viewed. Availability: Anthropic models must be enabled for your organization. If they're turned off, video creation isn't available. Generation: Creating and changing videos can take some time. Requests may sometimes fail or time out, and preview or playback may not work as expected. Editing: Changes happen through conversation, and videos export as MP4. Editing individual scenes or elements in Clipchamp isn't supported yet. Source material: WorkIQ, Web search, Word, PowerPoint, images (up to 3 per prompt), Videos (under 50mb) and PDF are supported. More file types and multiple sources will come in future releases. Sessions: Keep the browser tab open while a video is being created. Only one session at a time is supported. [Action Required/Recommendations:] If you plan to enable this capability, confirm Anthropic models are enabled and update Copilot Credits spending policies to include Copilot video creation with Clipchamp for intended users. Review internal readiness guidance for admins and support teams before broader enablement. [Compliance considerations:] No compliance considerations identified, review as appropriate for your organization. -
Microsoft Teams mobile: Updated app bar and More menu on iOS and iPadOS
MC1560919 · stayInformed · normal · Updated 11/20/2026 00:00
Services: Microsoft Teams
Read message
[What and Why:] To align with Apple's updated design guidance for tab bars in iOS and iPadOS 26, we're updating the app bar and More menu in Microsoft Teams for iOS and iPadOS. [Rollout Schedule:] General Availability (Worldwide): We will begin rolling out on December 10, 2026 and expect to complete by December 16, 2026. General Availability (GCC): We will begin rolling out on December 10, 2026 and expect to complete by December 16, 2026. General Availability (GCC High): We will begin rolling out on December 10, 2026 and expect to complete by December 16, 2026. [Impact on Your Organization:] The app bar will show up to four apps plus More (previously up to five). The More menu will become a list with two sections: Pinned, for the apps users pin, and All, for every other app, sorted by most recently used. Nothing is removed. The first time the updated app bar loads, any app that no longer fits in the four slots, including apps pinned by an admin, moves automatically to the top of the Pinned section in its existing order. Users can reorder apps on the app bar and in Pinned, pin or unpin apps from More, and uninstall apps and agents they no longer need. This change applies to devices running iOS/iPadOS 26 or later. Devices on earlier versions will continue to see the current experience. [Action Required/Recommendations:] No action is required. If your organization pins apps through app setup policies, consider reviewing their order so the four most important apps appear first on mobile. You may also want to update internal help documentation and let your users know about the change. [Compliance considerations:] No compliance considerations identified, review as appropriate for your organization. -
(Updated) Enhanced Copilot and AI controls for meetings
MC1532253 · planForChange · normal · Updated 11/19/2026 22:31
Services: Microsoft Teams
Read message
Updated November 19, 2026: We have updated the content. Thank you for your patience. [What and Why:] Microsoft Teams is updating how administrators and meeting organizers configure AI for Teams meetings. The existing Copilot meeting policy is being replaced by two more specific policies: MeetingAI - controls whether Copilot, Facilitator, Intelligent Recap, and other AI features are available in meetings. TranscriptionWithMeetingAI - controls whether transcription starts automatically when meeting AI is turned on. This gives administrators clearer, more predictable control over whether AI is available and whether it requires (or works without) transcription, including the ability to enforce Copilot off. Organizers also gain more visibility into, and in some cases control over, these settings directly from the meeting options. Meeting options are also being updated to make AI controls easier to understand and to provide more granular control over who can enable, manage, and use AI capabilities, including a new who can manage option that replaces the existing Allow Copilot and Facilitator meeting option: Who can manage AI - replaces the existing Allow Copilot and Facilitator option and determines who can turn Copilot and other AI features on or off during a meeting. If an admin turns Meeting AI off, this option is set to No one. Who can use AI - provides more granular control over which meeting participants can use Copilot and other AI capabilities. Start Transcription with AI - lets organizers choose whether transcription starts with AI. Administrators can also control this option through Teams admin center. Intelligent Recap controls - lets organizers decide whether an Intelligent Recap is created when Copilot is turned on, including for meetings where a transcript is not created. [Rollout Schedule:] Targeted Release (Worldwide): We will begin rolling out in early December 2026 (previously mid-November) and expect to complete by mid-December 2026 (previously early December). General Availability (Worldwide): We will begin rolling out in early January 2027 (previously late November 2026) and expect to complete by mid-January 2027 (previously early December 2026). [Impact on Your Organization:] Today, the Copilot policy combines whether AI is available in a meeting with whether a saved transcript is required. After this update, these behaviors are represented by two separate settings: Allow AI in meetings: On / Off, but organizers can change / Off, and organizers cannot change Start transcription when AI is turned on: On, but organizers can change / On, and organizers cannot change / Off To keep the experience predictable and avoid invalid combinations: if MeetingAI is set to enforced off, transcription will also be turned off; if transcription is then turned back on, MeetingAI will no longer be enforced off. In PowerShell, administrators will use MeetingAI and TranscriptionWithMeetingAI instead of the existing Copilot policy. Once the new controls are enabled, the Copilot policy can no longer be updated directly - attempts will return guidance to use the new policies. What happens to existing configurations: Microsoft will perform a one-time update mapping each existing Copilot value to the corresponding MeetingAI and TranscriptionWithMeetingAI values, preserving the current effective behavior for your organization. Administrators do not need to recreate their policies. Examples include: Existing configurationMeetingAITranscriptionWithMeetingAI Copilot is on and uses a saved transcript by defaultOnOn, but organizers can change Copilot is on and a saved transcript is requiredOnOn, and organizers cannot change Copilot is available without transcriptionOnOff Copilot is off, but organizers can enable itOff, but organizers can changeBased on the existing transcription configuration Copilot is enforced offOff, and organizers cannot changeOff The Transcription policy remains available and continues to control whether transcription is allowed. The new TranscriptionWithMeetingAI policy controls whether transcription starts when meeting AI is turned on. The new settings will appear in the Teams admin center meeting policy under Recording and transcription and Copilot and other AI: Screenshot 1 - Teams Admin Center: Meeting Policies Screenshot 2 - Meeting options: Recording & Transcription Screenshot 3 - Meeting options: Copilot and other AI Screenshot 4 - Teams Admin Center: Meeting Templates These screenshots show the new Start transcription when AI is turned on control and Allow AI in all meetings control, including the Teams Admin Center options administrators can use to set defaults or prevent organizers from changing the configured behavior. [Action Required/Recommendations:] No admin action is required to migrate existing configurations. Before rollout, we recommend admins: Review any automation or scripts that read or update the Copilot meeting policy, and update them to use MeetingAI and TranscriptionWithMeetingAI. Review custom tooling, runbooks, or documentation referencing the Copilot policy. Inform Teams administrators that existing behavior will now be represented by two settings in Teams admin center. Confirm the mapped configuration reflects intended behavior once the new controls are available. If you do not use PowerShell or custom automation to manage Teams meeting policies, no action is required. Existing configurations will be mapped automatically. [Compliance considerations:] This change affects administrative controls over AI and transcription availability in meetings but does not alter how existing customer data is processed or stored. Review AI and transcription governance policies for your organization as appropriate. -
(Updated) Microsoft Entra ID: Risk-based anti-bot verification (CAPTCHA) for SMS and voice multi-factor authentication
MC1551151 · preventOrFixIssue · normal · Updated 11/19/2026 21:12
Services: Microsoft Entra
Read message
Updated November 19, 2026: We have updated the content. Thank you for your patience. [What and why] Microsoft Entra ID is adding safeguards to protect telephony-based multifactor authentication (MFA) from automated fraudulent activity. Some users who use SMS or voice for MFA may be asked to complete a risk-based anti-bot verification step (CAPTCHA) before Microsoft sends an SMS verification code or initiates a verification call. If your organization has restrictive network or firewall settings, make sure to follow the guidance covered in this documentation (Risk-based anti-bot verification (CAPTCHA) for telephony-based sign-in - Microsoft Entra ID | Microsoft Learn) to prepare for this change. This change is separate from the planned retirement of SMS and voice authentication and does not affect the retirement timeline. [Rollout schedule] Worldwide: Beginning in mid-November 2026. [Impact on your organization] Who is affected Users who use SMS or voice for Microsoft Entra ID multifactor authentication Platforms and services Microsoft Entra ID SMS and voice authentication methods What will happen Some users may be prompted to complete a risk-based anti-bot verification step (CAPTCHA) before Microsoft sends an SMS verification code or initiates a verification call. The verification step will appear only for authentication attempts that meet sufficiently high-risk thresholds. Users with restrictive network or firewall settings may be unable to complete SMS or voice MFA if the verification experience cannot load. [Action required and recommendations] We recommend that administrators take the following actions: Prepare your help desk and notify users that some SMS and voice MFA attempts may require an additional CAPTCHA verification step. Review the risk-based anti-bot verification documentation for network-readiness guidance. If your organization uses restrictive firewalls, proxies, or web filtering, ensure that the required resources can load during authentication. Continue moving users to phishing-resistant authentication methods, such as passkeys, where possible. Learn more Risk-based anti-bot verification (CAPTCHA) for telephony-based sign-in - Microsoft Entra ID | Microsoft Learn Understanding telephony fraud risk for Microsoft Entra multifactor authentication - Microsoft Entra ID | Microsoft Learn Passkeys by default and retirement of Microsoft-provided SMS and voice authentication - Microsoft Entra ID | Microsoft Learn [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
The November 2026 Windows non-security preview update is now available
MC1560705 · stayInformed · normal · Updated 11/19/2026 18:05
Services: Windows
Read message
The November 2026 non-security preview update is now available for Windows 11, versions 26H2, 26H1, and 25H2. Information about the contents of this update is available in the release notes, which are accessible from the Windows 11 update history page. To learn more about the different types of monthly quality updates, see Understanding Windows monthly updates. Highlights for the Windows 11, version 26H2 update: Windows Search has a streamlined design with a single results list, file previews, and inline actions that let you change settings or arrange windows directly from search. Windows Hello facial recognition can now temporarily brighten your screen to help you sign in when you're in a dark or dimly lit room. Search from This PC in File Explorer is now indexer-based, making it much faster and consistent with search from File Explorer Home. Gaming Task View in XBOX mode adds access to the full set of taskbar Quick settings without leaving XBOX mode. A new Pointer indicator makes it easier to locate and use the mouse pointer. The Run dialog has a more modern design and improved usability, available by turning on New Run dialog in Settings > System > Advanced. For instructions on how to install this update, see the KB article for your operating system listed below: Windows 11, versions 26H2 and 25H2: KB5132057 Windows 11, version 26H1: KB5132265 IMPORTANT: Because of minimal operations during the Western holidays and the upcoming new year, there will be no December 2026 non-security preview update in the second part of the month. Normal monthly servicing for both security and non-security preview updates will resume in January 2027. Note: With recent and upcoming Windows updates over the next few months, a limited number of consumer and business devices might experience one additional restart during installation. This one‑time restart occurs after a Secure Boot certificate update is applied as part of the Secure Boot update process. -
(Updated) Microsoft Defender for Cloud Apps: Permission changes for select App Governance Entra roles
MC1479503 · planForChange · normal · Updated 11/19/2026 17:17
Services: Microsoft Defender XDR
Read message
Updated November 19, 2026: We have updated the timeline. Thank you for your patience. [What and Why:] We are introducing Microsoft Defender XDR Unified role-based access control (Unified RBAC) support for App Governance. As part of this rollout, App Governance permissions associated with select Microsoft Entra roles will change. This update helps align App Governance access with Defender XDR role management and provides more consistent permission handling for organizations using Microsoft Defender for Cloud Apps. [Rollout Schedule:] General Availability (Worldwide): We will begin rolling out in early December 2026 (previously mid-November) and expect to complete by late December 2026 (previously late November). [Impact on Your Organization:] Who is affected: Admins who manage App Governance in Microsoft Defender for Cloud Apps. Users assigned Cloud App Security Administrator, Compliance Administrator, Compliance Data Administrator, or custom Microsoft Defender XDR Unified RBAC roles for Microsoft Defender for Cloud Apps. Platforms/Services: Microsoft Defender XDR. Microsoft Defender for Cloud Apps. App Governance. What will happen: Cloud App Security Administrator: Users with this Microsoft Entra role will gain permission to view and manage App Governance policies. Compliance Administrator: Users with this Microsoft Entra role will no longer be able to manage App Governance policies or enable and disable App Governance in Settings. Compliance Data Administrator: Users with this Microsoft Entra role will no longer be able to enable and disable App Governance in Settings. Custom Defender XDR Unified RBAC roles: Users assigned a custom role in Defender XDR Unified RBAC for Microsoft Defender for Cloud Apps will also get access to App Governance features. [Action Required/Recommendations:] Before the enforcement date, we recommend that admins: Review users who access App Governance through the Compliance Administrator, Compliance Data Administrator, or Cloud App Security Administrator role. Review custom roles in Microsoft Defender XDR Unified RBAC for Microsoft Defender for Cloud Apps. Assign another supported Microsoft Entra role or a custom Defender XDR Unified RBAC role to affected users, following least-privilege principles. Update internal role assignment guidance and administrator documentation as needed. [Compliance considerations:] Does the change include an admin control, and can it be controlled through Entra ID group membership?This change affects App Governance permissions for selected Microsoft Entra roles and custom Microsoft Defender XDR Unified RBAC roles. Admins should review affected role assignments and update them as needed. Does the change alter how admins can monitor, report on, or demonstrate compliance activities?The change affects which admin roles can access and manage App Governance policies and settings. -
Microsoft Teams: Retirement of Translate slides in PowerPoint Live
MC1532259 · planForChange · normal · Updated 11/19/2026 00:56
Services: Microsoft 365 apps
Read message
[What and why] Starting November 30, 2026, attendees in Microsoft Teams meetings will no longer be able to translate slides into another language in PowerPoint Live by using Change view > Translate slides. Other PowerPoint Live features for presenters and attendees are not affected. [Rollout schedule] Retirement (Worldwide): Beginning and completing in late November 2026 Translate slides will be removed for all attendees on November 30, 2026 [Impact on your organization] Who is affected Attendees who use Translate slides in PowerPoint Live during Microsoft Teams meetings Platforms and services Microsoft Teams meetings PowerPoint Live What will happen Attendees will no longer see the Translate slides option in PowerPoint Live under Change view > Translate slides. Attendees will see slides in the language in which they were created. Presenting with PowerPoint Live and other attendee viewing options are not affected. There is no admin setting to manage this change. No admin action is required. Most organizations will see little impact because only a very small share of PowerPoint Live sessions use this option. [Action required and recommendations] No action is required to prepare for this change. Translate slides will be removed automatically for all attendees on November 30, 2026. We recommend that you: Notify presenters and users in your organization about this change, especially teams that present to audiences who speak different languages. Ask presenters to share slides in the languages their audiences need ahead of time. Update internal training or help content that mentions Translate slides in PowerPoint Live. [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
(Updated) Microsoft Teams: Onboarding workflow for new team members
MC1518033 · stayInformed · normal · Updated 11/19/2026 00:33
Services: Microsoft Teams
Read message
Updated November 18, 2026: We have clarified the supported channel types and updated the rollout timeline. Thank you for your patience. [What and Why:] Microsoft Teams is introducing an onboarding workflow that helps new team members get started faster by automatically connecting them to relevant channels when they join a team. This can improve engagement, accelerate onboarding, and make important information easier to find from the start. This message is associated with Microsoft 365 Roadmap ID 573452. [Rollout Schedule:] Targeted Release (R3.6): Rollout will proceed gradually from November 2026 through January 2027. General Availability (Worldwide): We will begin rolling out in mid-March 2027 (previously early December 2026) and expect to complete by end of March 2027 (previously mid-December 2026). [Impact on Your Organization:] Today, new team members may need to manually discover and join the channels that are most relevant to their work. With this update, team owners can automatically add new members to relevant channels through the onboarding workflow when they are added to a team. [Action Required/Recommendations:] No admin action is required. You may want to inform team owners about this upcoming improvement so they understand how to connect new members to relevant channels more efficiently during onboarding. [Compliance considerations:] No compliance considerations identified. Review as appropriate for your organization. -
(Updated) Microsoft Teams: Automatically add tag members to channels with Workflows
MC1540351 · stayInformed · normal · Updated 11/19/2026 00:30
Services: Microsoft Teams
Read message
Updated November 18, 2026: We have clarified the supported channel types and updated the rollout timeline. Thank you for your patience. [What and why] We are introducing the Join member to channel when user is added to tag template in the Workflows app to automatically add users to selected channels when they are added to a team tag. Once configured, the workflow runs whenever a user is added to the tag, eliminating the need to add members to each channel manually. This is especially useful for location-based or project-based groups where tags correspond to specific sites, regions, or projects, helping new members access relevant channels promptly. This applies to channels that all team members can access by default: standard channels and shared channels that are shared with everyone on the team. [Rollout schedule] Targeted Release (R3.6): Rollout will proceed gradually from November 2026 through January 2027. General Availability (Worldwide): Rollout will begin in mid-March 2027 (previously mid-December 2026) and is expected to complete by end of March 2027 (previously mid-December 2026). [Impact on your organization] Who is affected Microsoft Teams users who are added to team tags associated with configured workflows. Team owners who choose to configure the workflow. Platforms and services Microsoft Teams Workflows app Power Automate What will happen The Join member to channel when user is added to tag template will be available in the Workflows app. When configured, the workflow will automatically add users to selected channels when they are added to a team tag. Nothing changes by default. The template is optional and does not run until someone in a team configures it. Joining new tag members to channels [Action required and recommendations] No action is required. If your organization plans to use this template, we recommend reviewing your Power Automate and Workflows policies to confirm that it is permitted. Team owners can configure the workflow at any time if desired. [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
(Updated) Unified management of app and agent availability and installation in Teams, Outlook, and the Microsoft 365 app
MC796790 · planForChange · normal · Updated 11/19/2026 00:24
Services: Microsoft Teams, Microsoft 365 apps
Read message
Updated November 18, 2026: Unified app and agent installation management is now generally available. For any tenant that unifies app/agent availability through Phase 1, Phase 2, or Phase 3, app and agent installations are also unified across the Microsoft 365 admin center (MAC) and Teams admin center (TAC) within 24–48 hours of completing availability unification. What it is Microsoft is rolling out a new feature to streamline how app and agent availability and installation is managed across Teams, Outlook, and Microsoft 365 Copilot. Until now, IT admins configured availability and installation settings separately in both the Microsoft 365 Admin Center (MAC) and the Teams Admin Center (TAC), which led to mismatches. With this update, you’ll be able to unify availability and installation policies for apps and agents across both portals, making app management more consistent and efficient. This message is associated with Microsoft 365 Roadmap ID 393931, 485712 and 503105. When this will happen: App and agent availability unification (Section A): Rollout began in late September 2025. The Phase 3 timeline will be announced separately, at least 60 days before that phase begins. App and agent installation unification (Section B): Released. Installation unification completes within 24–48 hours after a tenant completes app availability unification(Section A) in Phase 1, 2, or 3 A: Unify app availability across admin centers 1. Phase 1 – Default Tenant Unification of App/Agent Availability We will begin rolling out this feature at the end of September 2025. This initial phase targets tenants that have never modified their organization-wide defaults, app availability, or block/unblock in either the Microsoft 365 admin center or the Teams admin center. At the end of this phase, agent and app manageability will be unified across both Microsoft 365 admin center and Teams admin center ensuring agent and Microsoft 365 apps availability policies are in alignment for all future administrative changes. This message is associated with Microsoft 365 Roadmap ID 393931. 2.Phase 2 – Modified Tenants Unification of App/Agent Availability This phase targets tenants that have previously modified their organization-wide defaults, app availability, or block/unblock settings in either admin center. These tenants will be transitioned to a unified management experience across both Microsoft 365 and Teams admin centers. For tenants with no agent or app availability differences across both admin centers, guidance will be provided to help maintain unified availability policy for all future changes. For tenants with agent or app availability differences across both admin centers, a wizard in the Teams admin center will help identify affected agents and apps and guide through resolving discrepancies. As part of this phase we will also enable administrators to manage Microsoft 365 certified SaaS applications within their tenant through org-wide settings for third-party apps. This has been rolled out completely for all tenants. This message is associated with Microsoft 365 Roadmap ID 485712 & 503105. This phase has been fully rolled out to all tenants. Tenants can choose to align through the wizard experience available in Teams admin center. Note: In this phase, no changes will be applied to org-wide settings or app-level settings without administrator action. 3. Phase 3 – Automatic Unification (Future) Tenants that have not taken action to unify availability through the wizard experience released in Phase 1 and Phase 2 will have their availability automatically unified across MAC and TAC as part of this phase. We will inform customers of the timeline and additional details at least 60 days in advance before this phase begins. B: Unified app and agent installation management This capability unifies installation management across the Teams admin center and Microsoft 365 admin center. Administrators can manage supported app and agent installations from either portal, with changes synchronized across both admin centers. Who receives this capability? Tenants whose app and agent availability has been unified through any of the phases described in section A are eligible. Once rollout begins, this capability will be automatically enabled for tenants whose availability is already unified as part of Section A. Tenants that unify their availability later will receive this capability automatically once unified. Note: This capability is separate from availability unification described in section A . It does not automatically unify app or agent availability. When will it roll out? Rollout will begin at the end of September 2026 for eligible tenants. This date applies only to installation management (section B). Is administrator action required? No additional action is required to enable installation unification for eligible tenants. Existing installation assignments for supported apps and agents will be synchronized across both admin centers. Important: App installation is no longer managed through Teams app setup policies. Installations previously made through those policies are not unified as part of this change. -
Continuous interpreter visibility with pop out video in Teams
MC1559642 · stayInformed · normal · Updated 11/18/2026 23:41
Services: Microsoft Teams
Read message
[What and Why:] Users who work with sign language interpreters in Microsoft Teams meetings will be able to pop out their paired interpreters' video into a separate window. The window can be resized and moved anywhere on the screen, including to another monitor. Interpreters stay in view while users multitask, share content, or change meeting layouts. This is designed for Deaf and hard-of-hearing (D/HH) users, for whom losing sight of an interpreter means losing access to the conversation. [Rollout Schedule:] Targeted Release (Worldwide): We will begin rolling out on early December 2026 and expect to complete by late December 2026. General Availability (Worldwide): We will begin rolling out on mid January 2027 and expect to complete by late January 2027. [Impact on Your Organization:] This applies to Teams desktop on Windows and Mac. After this rollout, users can: Pop out their paired sign language interpreters' video into a dedicated window that stays on top of other apps. Resize the window and move it anywhere on their screen or to another monitor. Keep interpreters in view while presenting, viewing shared content, using chat or captions, or with the main meeting window minimized. The pop-out window only changes the user's own view, and interpreters stay in the main meeting gallery for everyone else. The window isn't visible to other participants when the user shares their screen. [Action Required/Recommendations:] You don't need to do anything to prepare. Consider telling D/HH users and the interpreters who support them about this feature, and update your training and accessibility documentation as needed. To use the feature: In Teams Accessibility settings, turn on Sign language mode and select I am a Signer. Select Manage interpreters and add the people who interpret for you. Select View > Pop out interpreters during a meeting. Users open the pop-out window in each meeting. For faster access, they can pin the Pop out interpreters button to the meeting toolbar. There is no admin policy for this feature. [Compliance considerations:] No compliance considerations identified. Review as appropriate for your organization. -
New Copilot experience in OneNote
MC1559641 · planForChange · normal · Updated 11/18/2026 23:41
Services: Microsoft 365 apps
Read message
[What and Why:] We are introducing a refreshed Copilot experience in OneNote with expanded edit and reasoning capabilities across notebook content, including ink, annotations, and embedded files. This update helps users find and synthesize information across notes, reorganize content, and create related documents directly from OneNote with Copilot. [Rollout Schedule:] Frontier Public: began in November 2026. General Availability (Worldwide): we expect rollout to begin in January 2027. [Impact on Your Organization:] Eligible users will have broader Copilot capabilities in OneNote on supported app versions on Windows and iPad, including richer cross-note reasoning and content creation workflows. OneNote on Mac, iPhone, Android, and web is not included in this rollout and will receive this update later. [Action Required/Recommendations:] No immediate admin action is required. We recommend informing impacted users and updating internal OneNote + Copilot guidance and training materials. [Compliance considerations:] No compliance considerations identified, review as appropriate for your organization. -
Microsoft Teams: Real-time queue metrics in the Queues app on Mobile
MC1559637 · stayInformed · normal · Updated 11/18/2026 23:35
Services: Microsoft Teams
Read message
[What and Why:] For calling representatives and supervisors, staying informed about call queue activity is important to managing incoming calls and maintaining timely customer service. However, when working away from their desks, they may not have visibility into current queue conditions, such as how many calls are waiting or how effectively calls are being handled. Without this information, it becomes harder to respond to changing call volumes and make informed decisions about queue participation. We're introducing real-time call queue metrics in the Queues app on Microsoft Teams Mobile. Calling representatives and supervisor leads can now monitor key operational metrics directly from their mobile devices, giving them greater visibility into queue activity and performance while on the go. Users can quickly understand the state of their queues, monitor incoming call demand, and make informed decisions about their availability and queue participation without needing to switch to desktop. [Rollout Schedule:] General Availability (Worldwide): We will begin rolling out in early December 2026 and expect to complete by mid-December 2026. [Impact on Your Organization:] Once available, eligible calling representatives and supervisor leads will be able to view real-time call queue metrics directly from the Queues app on Mobile. Users will be able to: Monitor queue activity: View real-time metrics to understand current call volumes and queue conditions. Track incoming call demand: See key metrics such as calls waiting, calls presented, and calls answered. Stay informed about queue performance: Access operational metrics for their assigned call queues without switching to desktop. Make informed decisions: Use real-time queue information to better understand call demand and manage their availability and queue participation. The metrics available to users will depend on their role and existing permissions. Calling representatives will have visibility into the metrics available to them, while supervisor leads will have access to additional queue information based on their permissions. This feature extends the existing real-time queue metrics experience to Mobile and does not change how call queues are configured or managed. [Action Required/Recommendations:] No new admin action is required before rollout. We recommend that you: Review the license assignments for users who need access to the Queues app on Mobile. Ensure that calling representatives and supervisor leads have the appropriate permissions to view queue metrics. Inform your help desk and users about the availability of real-time queue metrics on Mobile, and update internal training and support materials as needed. [Compliance considerations:] No compliance considerations identified. Review as appropriate for your organization. -
Microsoft SharePoint: Agent Chat web part to bring Copilot agents into SharePoint pages
MC1559633 · stayInformed · normal · Updated 11/18/2026 23:34
Services: SharePoint Online
Read message
[What and Why:] We're introducing the Agent Chat web part in SharePoint, allowing organizations to embed their existing Microsoft 365 Copilot agents directly into SharePoint pages. This helps organizations make agents easier to discover and use by bringing conversational AI into familiar intranet experiences, alongside relevant information, instructions, and resources. [Rollout Schedule:] Public Preview (Worldwide): We will begin rolling out in mid-November 2026 and expect to complete by late January 2027. General Availability (Worldwide): We will begin rolling out in mid-January 2027 and expect to complete by late March 2027. General Availability (GCC): We will begin rolling out in mid-January 2027 and expect to complete by late March 2027. General Availability (GCC High): We will begin rolling out in mid-January 2027 and expect to complete by late March 2027. General Availability (DoD): We will begin rolling out in mid-January 2027 and expect to complete by late March 2027. [Impact on Your Organization:] Who is affected: SharePoint page authors who want to embed Copilot agents. Users with a Microsoft 365 Copilot license and access to the configured agent. Platforms/Services: SharePoint Online, Microsoft 365 Copilot, Microsoft Copilot Studio. What will happen: SharePoint page authors can add the Agent Chat web part to pages using the standard page editing experience. Authors can select published agents already available to them in Microsoft 365 Copilot. Users can interact with agents directly from SharePoint pages and continue conversations in a full-screen chat experience. Organizations can place agents alongside relevant SharePoint content to help users discover and engage with them. Existing SharePoint page permissions and agent access permissions remain independent. Adding an agent to a page does not automatically grant users access to that agent. SharePoint page content is not automatically passed to the agent. [Action Required/Recommendations:] No admin action is required before rollout. The Agent Chat web part becomes available as part of the rollout.We recommend informing SharePoint page authors and support teams about this capability and reviewing the documentation: Use Agent Chat web part in SharePoint. [Compliance considerations:] No compliance impact is expected for this change. SharePoint does not store Copilot agent chat data or change how agent data is processed. -
Choose how your presenter view is laid out in PowerPoint Live in Microsoft Teams
MC1559628 · stayInformed · normal · Updated 11/18/2026 23:29
Services: Microsoft Teams
Read message
[What and Why:] Presenters using PowerPoint Live in Microsoft Teams can now choose a layout for their presenter view. They can pick the one that best fits how they like to present, whether that's focusing on speaker notes, moving between slides quickly, looking ahead to what's next, or keeping the view simple. [Rollout Schedule:] General Availability (Worldwide): We will begin rolling out on mid November 2026 and expect to complete by late November 2026. [Impact on Your Organization:] Presenters can switch between these layouts while they present: Notes and thumbnails (default): Speaker notes and slide thumbnails, the same view presenters have today. Thumbnails on the left: Slide thumbnails along the left side for quick navigation. Next slide preview: A preview of the next slide or animation, so presenters can see what's coming. Slides only: A simpler view focused on the current slide. To change the layout, the presenter selects "Change layout" while presenting. Layouts only change what the presenter sees. Attendees' view of the presentation isn't affected. This feature is available in Teams on Windows, Mac and the web. This feature is on by default. [Action Required/Recommendations:] No admin action is required. You may want to let presenters in your organization know about the new layout options and update any internal training or documentation as needed. [Compliance considerations:] No compliance considerations identified, review as appropriate for your organization. -
(Updated) Microsoft 365 Backup: Full workload backup for SharePoint, OneDrive, and Exchange
MC1387526 · planForChange · normal · Updated 11/18/2026 22:42
Services: Microsoft 365 suite
Read message
Updated November 18, 2026: We have updated the timeline. Thank you for your patience. [What and Why:] We are introducing Full Workload Backup for Microsoft 365 Backup, a new capability that allows admins to quickly protect an entire workload (SharePoint, OneDrive, or Exchange) with a single policy. This feature automatically includes all existing and newly created artifacts that are not already covered by custom policies, helping organizations improve data protection coverage, reduce administrative overhead, and ensure continuous backup for critical business data at scale. This enhancement supports enterprise-ready data protection and automation, enabling organizations to safeguard content more efficiently while maintaining control through existing policy configurations. This message is associated with Microsoft 365 Roadmap ID 464990. [Rollout Schedule:] Public Preview (Worldwide): We will begin rolling out in early July 2026 and expect to complete by mid-July 2026. General Availability: We will begin rolling out in January 2027 (previously mid-September 2026) and expect to complete by end of February 2027 (previously mid-October 2026). [Impact on Your Organization:] Who is affected: Admins managing Microsoft 365 Backup policies Organizations currently using or planning to use Microsoft 365 Backup Platforms/Services: Microsoft 365 Backup SharePoint Online OneDrive Exchange Online What will happen: A new option to back up all artifacts within a selected workload will be available. Admins can enable Full Workload Backup per workload (SharePoint, OneDrive, Exchange). All eligible artifacts not covered by existing custom backup policies will be automatically protected. Newly created artifacts will be included in backup coverage automatically on subsequent runs. Existing custom backup policies will continue to take precedence and remain unchanged. Admins can upload a CSV file to exclude specific artifacts. The feature is available by default but requires admin configuration to enable. [Action Required/Recommendations:] No immediate action is required before rollout. After rollout, we recommend that you: Review your current Microsoft 365 Backup policies and coverage. Evaluate whether Full Workload Backup aligns with your data protection strategy. Inform backup administrators about this new capability. Update internal documentation if you manage backup procedures. To enable the feature: Go to the Microsoft 365 Backup dashboard in the Microsoft 365 admin center. Select the workload you want to protect and choose the option to back up all artifacts. (Optional) Upload a CSV file on the Exclude sites step to exclude specific sites from the scope of the policy. Review the coverage summary and confirm to create the Full Workload Backup policy. Learn more: Create, view, and edit backup policies in Microsoft 365 Backup | Microsoft Learn (will be updated before rollout begins) Overview of Microsoft 365 Backup | Microsoft Learn (will be updated before rollout begins) [Compliance considerations:] No compliance considerations identified, review as appropriate for your organization. -
(Updated) Microsoft Teams: External presenter support for event group chat
MC1528011 · stayInformed · normal · Updated 11/18/2026 18:57
Services: Microsoft Teams
Read message
Updated November 18, 2026: We have updated the timeline. Thank you for your patience. [What and why] We are adding support for external presenters in event group chat, the private chat used by organizers, co-organizers, and presenters for coordination during an event or structured meeting. This change enables presenters who are outside the tenant hosting the meeting or event to participate in the event group chat. [Rollout schedule] General Availability (Worldwide): Rollout will begin in late March 2027 (previously early December 2026) and is expected to complete by mid-April 2027 (previously early January). [Impact on your organization] Who is affected Organizers, co-organizers, and presenters using event group chat in meetings or events, including external presenters. Platforms and services Microsoft Teams Event group chat Meetings and events with the Enable Green room Teams meeting option enabled What will happen External presenters will be able to join the event group chat used for coordination during a meeting or event. The meeting or event must have the Enable Green room Teams meeting option enabled to use event group chat. External user collaboration must be enabled for external presenters to use this functionality. [Action required and recommendations] If your organization wants external presenters to use event group chat, ensure external user collaboration is enabled in Teams admin center > External collaboration. [Compliance considerations] Does the change store new customer data? No. Expected changes on the client will only correct the tenantId to the external federated presenter's own tenant. Does the change alter how existing customer data is processed, stored, or accessed (e.g., documents, emails, chats, etc.)? Yes. External federated presenters can now read and post in the event group chat. That includes messages written before they joined, if the thread shows history. The presenter's stored tenantId also changes from the organizer's tenant to the presenter's own tenant. Does the change provide a new way of communicating between users, tenants, or subscriptions? Yes. We are adding a new cross-tenant chat path between the organizer's tenant and external presenters. Both tenants must allow external access. Does the change modify how users can access, export, delete, or correct their personal data within Microsoft 365 services (GDPR Data Subject Rights)? No. External presenters' messages fall under existing federated-chat handling. -
Microsoft Teams: End of support for iOS 17 and iPadOS 17
MC1556088 · planForChange · normal · Updated 11/18/2026 15:58
Services: Microsoft Teams
Action required by: 01/02/2027 08:00
Read message
[What and Why:] Microsoft Teams is ending support for upcoming builds on iOS 17 and iPadOS 17. As this change rolls out, new Teams releases will require iOS 18 or later on iPhone and iPadOS 18 or later on iPad. [Rollout Schedule:] General Availability (Worldwide): We will begin rolling out in mid-December 2026 and expect to complete by early January 2027. [Impact on Your Organization:] Users whose devices remain on iOS 17 or iPadOS 17 will not be able to install newer Teams releases that require a newer operating system. Teams versions already installed on these devices will continue functioning without official support. This change does not introduce a block on opening or signing in to those existing installations. [Action Required/Recommendations:] Identify devices running iOS 17 or iPadOS 17 and notify affected users. Advise users to upgrade to a supported operating system, then update Teams through the Apple App Store, to continue receiving supported Teams releases. Review any mobile device management (MDM) or app deployment policies that pin or require specific iOS/iPadOS versions, and update them to allow iOS 18/iPadOS 18 so affected devices are not blocked from upgrading. Update internal support documentation and helpdesk guidance. Learn more: Hardware requirements for Microsoft Teams. [Compliance considerations:] No compliance considerations identified. Review as appropriate for your organization. -
Updates available for Microsoft 365 Apps for Current Channel
MC1558155 · stayInformed · normal · Updated 11/18/2026 01:15
Services: Microsoft 365 apps
Read message
We've released updates to the following update channel for Microsoft 365 Apps: Current Channel [When this will happen:] We'll be gradually rolling out this update of Microsoft 365 Apps to users on that update channel starting November 17th, 2026 (PST). [How this will affect your organization:] If your Microsoft 365 Apps clients are configured to automatically update from the Office Content Delivery Network (CDN), then no action is required. If you manage updates directly you can now download this latest update and begin deployment. [What you need to do to prepare:] To get more details about this update view the following release notes: Current Channel -
Microsoft Defender for Cloud Apps: Unified RBAC support for App Governance to manage NHIs
MC1558114 · stayInformed · normal · Updated 11/18/2026 00:21
Services: Microsoft Defender XDR
Read message
[What and Why:] App Governance in Defender for Cloud Apps will now support Microsoft Defender XDR unified role-based access control (RBAC) in public preview. This capability lets your organization delegate access to App Governance through Defender XDR custom roles, for supported App Governance capabilities. You can align access with administrators' responsibilities and apply least-privilege permissions when managing Non-Human Identities, including Microsoft Entra applications. [Rollout Schedule:] Public Preview (Worldwide): We will begin rolling out in late November 2026 and expect to complete by mid-December 2026. General Availability (Worldwide): We will begin rolling out in mid-December 2026 and expect to complete by mid-January 2027. [Impact on Your Organization:] Administrators will be able to configure and assign Defender XDR unified RBAC custom roles to users or groups for the following capabilities: Read access: View App Governance inventory, insights, risk signals, and policies. Policy management: Create and edit App Governance policies. Service management: Turn the App Governance service on or off. Users with existing Defender for Cloud Apps unified RBAC roles may also gain App Governance access, depending on their assigned permissions and data sources. Review these assignments to ensure access remains appropriate. Supported Microsoft Entra roles will continue to provide App Governance access, subject to documented role changes. Microsoft Entra application enable and disable actions continue to require the Application Administrator role; this preview does not replace that requirement. [Action Required/Recommendations:] Review existing Defender XDR unified RBAC assignments, particularly roles used for Defender for Cloud Apps. To delegate App Governance access, create or update a custom role in the Microsoft Defender portal under Setup & Configuration > Permissions > Microsoft Defender XDR > Roles. Configure the permissions appropriate to each administrator's responsibilities. Select the applicable data sources as described in the updated configuration guidance. [Compliance considerations:] No compliance considerations identified. Review as appropriate for your organization. -
(Updated) Microsoft Copilot: GPT 6.1 Sol and Claude Sonnet 5.5 beginning to roll out today
MC1483844 · planForChange · normal · Updated 11/17/2026 23:30
Services: Microsoft 365 apps
Read message
Updated November 17, 2026: GPT-6.1 Sol is rolling out worldwide on Microsoft Azure for Copilot Cowork customers who have not enabled OpenAI as a subprocessor. GPT-6.1 Sol will be generally available and replace GPT-5.5 for these customers, with GPT-5.5 being retired and no longer available for Cowork in the Frontier program. No admin action is required. [What and Why:] To give users more choice and flexibility when working with AI in Microsoft Copilot, we're expanding the set of AI models available in Microsoft Copilot. Starting today, GPT-6.1 Sol and Claude Sonnet 5.5 begin rolling out with usage-based billing in Cowork and Microsoft Copilot Studio. GPT-6.1 Sol and Claude Sonnet 5.5 will also begin rolling out in phases across Word, Excel, PowerPoint, and Chat in the coming week as part of the Microsoft 365 Copilot user subscription license (USL). Limits apply to these models, but they are designed to support broad day-to-day AI usage across organizations and are implemented in such a way that the vast majority of users are not expected to reach them. Users approaching a limit will receive in-product notifications and can continue their work by switching to Auto mode or selecting another available model. [Rollout Schedule:] General Availability: Cowork and Copilot Studio: Rollout begins today, September 30, 2026. Word, Excel, PowerPoint and Chat: Phased rollout begins in the coming week. [Impact on Your Organization: Who is affected: Cowork and Copilot Studio: Users assigned a user subscription license (USL) with usage-based billing (UBB) enabled. Word, Excel, PowerPoint, and Chat: Users assigned a user subscription license (USL). Access to Claude Sonnet 5.5 additionally requires the Anthropic subprocessor to be enabled in your organization. Access to GPT-6.1 Sol in select surfaces requires the OpenAI subprocessor to be enabled. Learn more: OpenAI as a subprocessor in Microsoft Online Services | Microsoft Learn. As a reminder, this setting controls only whether OpenAI models operated by OpenAI (provided by OpenAI as a subprocessor) can be used. OpenAI models operated by Microsoft (Azure OpenAI) aren't affected and remain available in Copilot regardless of this setting. Platforms/Services: (USL) Microsoft 365 Copilot Chat (USL) Microsoft Word (USL) Microsoft Excel (USL) Microsoft PowerPoint (UBB) Copilot Cowork (UBB) Microsoft Copilot Studio What will happen: Users will be able to select GPT-6.1 Sol and Claude Sonnet 5.5 using the model selector from supported Microsoft Copilot experiences. The feature is enabled by default for eligible licensed users who meet the applicable configuration requirements. [Action Required / Recommendations:] No action is required for organizations that want users to access these models. Recommended actions: Review whether the Anthropic subprocessor is enabled if you plan to make Claude Sonnet 5.5 available to users. Review whether the OpenAI subprocessor is enabled if you plan to make GPT-6.1 Sol broadly available to users. If disabled, GPT-6.1 Sol may not be available from all supported Copilot surfaces. Review your organization's AI usage guidance and communicate model availability to end users. Inform helpdesk and support teams that users may encounter usage-limit notifications and can continue working using Auto mode or another available model. Review the announcement blog for additional details: Available today: OpenAI's GPT-6.1 Sol and Claude Sonnet 5.5 in Microsoft Copilot | Microsoft Community Hub. Update internal user documentation and training materials, as appropriate. [Compliance Considerations:] Consideration Explanation Does the change introduce or significantly modify AI/ML or agent capabilities that interact with or provide access to customer data? GPT-6.1 Sol and Claude Sonnet 5.5 are additional AI models that users can select within Microsoft 365 Copilot experiences to generate responses based on content and context available to the user through Copilot. Does the change provide end users any new way of interacting with generative AI? Users gain access to new model choices, GPT-6.1 Sol and Claude Sonnet 5.5, in supported Microsoft 365 Copilot experiences. Does the change include an admin control and can it be controlled through Entra ID group membership? Access to Claude Sonnet 5.5 depends on administrative configuration of the Anthropic subprocessor. -
Microsoft OneDrive for iPad: Presentation mode for PDFs
MC1558041 · stayInformed · normal · Updated 11/17/2026 23:03
Services: Microsoft OneDrive
Read message
[What and why] We are introducing presentation mode in the Microsoft OneDrive app for iPad. Users can select a new Presentation button in the PDF viewer to enter a focused, view-only experience that prevents free gesture scrolling between pages, reducing accidental page changes while presenting without requiring users to move the file to another app. This update is based on customer feedback requesting a presentation experience directly in the OneDrive PDF viewer. This feature is not available on iPhone. [Rollout schedule] General Availability (Worldwide): Rollout will begin in early December 2026 and is expected to complete by late December 2026. [Impact on your organization] Who is affected Users who open and present PDF files in the OneDrive app for iPad. Platforms and services Microsoft OneDrive for iPad What will happen Users can select the Presentation button in the OneDrive PDF viewer to enter presentation mode. Presentation mode supports all PDFs, displays them in a view-only experience without editing controls, and does not intentionally change them or create a new copy. Free scrolling or swiping between pages is disabled in presentation mode, preventing accidental page changes. Users can switch pages only by selecting the on-screen navigation buttons. The feature is enabled by default for all OneDrive for Business customers. No admin control or tenant configuration is available for this feature. Presentation mode changes how a PDF is displayed during a presentation and does not intentionally change file storage, permissions, sharing, retention, or audit behavior. Existing OneDrive access permissions and protections applied to the PDF continue to apply. [Action required and recommendations] No administrative action is required before rollout. We recommend that you inform helpdesk and support teams about the new presentation experience and update internal user guidance for presenting PDFs from the OneDrive app for iPad. [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
Microsoft 365 Copilot: Copilot Managed Runtime expands app building at general availability
MC1558033 · stayInformed · normal · Updated 11/17/2026 23:01
Services: Microsoft 365 suite
Read message
[What and why] Microsoft Copilot Managed Runtime is an IT-governed platform for running code within the Microsoft 365 tenant boundary. It supports app creation in Copilot Cowork, Copilot Studio, Copilot Code, and the Copilot Managed Runtime CLI. Apps can use organizational data through connectors permitted by your organization's policies, and admins can manage apps through the Microsoft 365 admin center. Microsoft Copilot Managed Runtime, introduced in public preview in September 2026 (MC1469329), will become generally available. App building in Copilot Cowork will no longer be limited to the Microsoft Copilot Frontier Program. [Rollout schedule] Public Preview: Rollout began in September 2026 and is expected to be complete by mid-November 2026. General Availability (Worldwide): Rollout will begin in mid-November 2026 and is expected to be complete by mid-December 2026. [Impact on your organization] Who is affected Licensed users who build or run apps hosted on Microsoft Copilot Managed Runtime and admins who manage those apps, environments, governance policies, and Copilot Credits Platforms and services Microsoft 365 admin center Microsoft Copilot Cowork Microsoft Copilot Studio Microsoft Copilot Code (Frontier) Copilot Managed Runtime CLI Power Platform environments What will happen Copilot Managed Runtime will no longer be a preview feature. Licensed users can build apps in Copilot Cowork without participating in the Microsoft Copilot Frontier Program. Makers will continue to build in personal environments that are created when first needed and reused afterward. Environment routing is enabled for Copilot Managed Runtime. If your tenant has no routing rules, users are routed to personal environments in the default environment group. Existing routing rules aren't changed. Personal environments inherit the default environment group's connector, content security, and sharing policies. Makers can't override these policies. Admins can manage them under Apps > Settings in the Microsoft 365 admin center. Sharing an app provides access to the app but doesn't provide access to its underlying data. Draft and published apps appear under Apps > All apps, where admins can review app information and perform lifecycle operations such as blocking and deleting apps. [Action required and recommendations] Before general availability: Set up Copilot Credits: In the Microsoft 365 admin center, go to Copilot > Cost management and create a spending policy that covers all users and includes Copilot Managed Runtime. Note: A small per-user monthly limit, such as 100 Copilot Credits (US$1), covers typical use. Add policies with higher limits for groups that use apps more frequently. Users with a Power Apps Premium license can run apps without a spending policy. Enable makers: For Copilot Cowork and Copilot Code, include makers in an applicable spending policy. For Copilot Studio, allocate credits to the environments where makers build. Review governance: Review policies for personal environments, connectors, content security, and app sharing, as well as apps built during public preview. Communicate the change: Let your organization and maker community know that app building in Copilot Cowork and Copilot Code is expanding beyond the Microsoft Copilot Frontier Program. Learn more (PDF) Copilot Credits Guides Licensing and billing Environment routing for Microsoft Copilot Managed Runtime - Power Platform | Microsoft Learn FAQ about Microsoft Copilot Managed Runtime - Microsoft 365 admin | Microsoft Learn What is Microsoft Copilot Managed Runtime | Microsoft Learn [Compliance considerations] ConsiderationExplanation Does the change introduce or significantly modify AI/ML or agent capabilities that interact with or provide access to customer data?Yes. Apps can use organizational data through connectors permitted by your organization's policies. Does the change provide end users any new way of interacting with generative AI?Yes. App building in Copilot Cowork and Copilot Code is expanding beyond the Microsoft Copilot Frontier Program. Does the change include an admin control, and can it be controlled through Entra ID group membership?Yes. Admins can manage governance policies, environment routing, spending policies, and app lifecycle operations. Spending policies can be assigned to security groups. -
Microsoft OneDrive for Windows and Mac: node_modules folders will be excluded from sync by default
MC1558030 · planForChange · normal · Updated 11/17/2026 23:01
Services: Microsoft OneDrive
Action required by: 12/14/2026 08:00
Read message
[What and why] We are updating the OneDrive sync app for Windows and Mac to exclude new folders named node_modules from syncing by default, beginning December 14, 2026. This change extends OneDrive's existing default exclusion list, which includes .db-wal files, as mentioned in MC1457838 on October 5, 2026. JavaScript and Node.js projects can generate tens of thousands of small dependency files in node_modules folders. This change is intended to improve sync performance and reduce unnecessary storage and bandwidth usage. Developers can rebuild these folders using their package manager. [Rollout schedule] General Availability (Worldwide): Rollout will begin on December 14, 2026, and is expected to complete by mid-January 2027. [Impact on your organization] Who is affected Users with work or school accounts who create node_modules folders in OneDrive-synced locations, including Desktop and Documents folders managed through Known Folder Move. Platforms and services OneDrive for Windows OneDrive for Mac What will happen New node_modules folders: OneDrive will exclude newly created folders named node_modules from syncing by default. These folders will remain on the device and will not upload to OneDrive. Folder name matching: The exclusion applies to folders named exactly node_modules, regardless of capitalization. Existing node_modules folders: Folders that are already syncing will continue to sync. OneDrive will not remove existing content from the cloud or devices. User experience: Users will not receive prompts. Excluded folders will continue to function locally but will not be available through OneDrive on the web or other devices. Administrative controls: Administrators can use existing OneDrive sync policies to turn off the default exclusion list if their organization needs these folders to sync. [Action required and recommendations] No action is required if your organization wants to use the new default behavior. If your organization needs node_modules folders to continue syncing, configure the appropriate OneDrive sync policies before December 14, 2026. We recommend that you update your helpdesk and developer guidance to reflect the new default behavior and notify developers who maintain code projects in OneDrive-synced locations. [Learn more] Deploy and configure the OneDrive sync app for Mac - SharePoint in Microsoft 365 | Microsoft Learn IT Admins - Use OneDrive policies to control sync settings - SharePoint in Microsoft 365 | Microsoft Learn [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
Microsoft Teams: Intelligent call recap for call queues in the Queues app on mobile
MC1558032 · stayInformed · normal · Updated 11/17/2026 23:00
Services: Microsoft Teams
Read message
[What and why] We're introducing intelligent call recap for call queue calls in the Queues app on Microsoft Teams mobile. This update extends the experience already available on desktop, allowing calling representatives and supervisors to review AI-generated notes, key discussion points, and recommended follow-up tasks without replaying recordings or reading full transcripts. [Rollout schedule] General Availability (Worldwide): Beginning in early December 2026 and expected to complete by mid-December 2026 [Impact on your organization] Who is affected Calling representatives and supervisors who use the Queues app on Microsoft Teams mobile and have access to recorded and transcribed call queue calls Platforms and services Microsoft Teams mobile Queues app What will happen After rollout: Users can open a recorded call from shared call history and select View recap to review AI-generated notes, key discussion points, and recommended follow-up tasks. Screenshot 1: Screenshot 2: Screenshot 3: Recap is available only for recorded and transcribed call queue calls and to users who already have access to the recording. The feature does not change how call recordings are created, stored, or accessed. [Action required and recommendations] No admin action is required before rollout. We recommend that you: Confirm that recording and transcription are enabled for call queues where you want users to access intelligent call recap. Review license assignments for users who will use the feature. Learn more Intelligent recap for Teams calls, meetings, and events - Microsoft Teams | Microsoft Learn [Compliance considerations] Organizations should review their existing recording, transcription, and AI-related compliance requirements as appropriate. -
Microsoft 365 admin center: New multi-tenant management experiences
MC1558024 · stayInformed · normal · Updated 11/17/2026 22:58
Services: Microsoft 365 suite
Read message
[What and why] Microsoft is introducing new multi-tenant management experiences in the Microsoft 365 admin center to help organizations centrally manage Microsoft 365 Copilot, agents, costs, and Microsoft 365 services across multiple tenants. These capabilities provide administrators with a unified experience to view tenant information, review key insights, and manage AI costs, agents, and tenant configurations without having to navigate to each tenant individually. This provides a more scalable and consistent way for organizations to administer multiple Microsoft 365 tenants. [Rollout schedule] Public Preview: Beginning in mid-November 2026 and expected to complete by early December 2026 [Impact on your organization] Who is affected Organizations that manage multiple Microsoft 365 tenants and administrators responsible for managing those tenants Platforms and services Microsoft 365 admin center, Microsoft 365 Copilot, agents, and Microsoft 365 services What will happen With the new multi-tenant management experiences, administrators will be able to: Link multiple tenants and manage them through a unified interface in the Microsoft 365 admin center. View information and insights across linked tenants. Manage AI costs and agents across tenants. Perform tenant configuration management actions without navigating to each tenant individually. [Action required and recommendations] Organizations that want to use the new multi-tenant management capabilities must first link their tenants using Microsoft Entra tenant governance. Review the setup and licensing requirements for Microsoft Entra tenant governance. Link the tenants you want to manage through the unified experience. Learn more Add Tenants to Your Partner Center Account - Partner Center | Microsoft Learn Governance relationships in Tenant Governance - Microsoft Entra ID Governance | Microsoft Learn Manage agents across multiple tenants in the Microsoft 365 admin center | Microsoft Learn Manage configurations across multiple tenants in the Microsoft 365 admin center - Microsoft 365 admin | Microsoft Learn Manage costs across multiple tenants in the Microsoft 365 admin center - Microsoft 365 admin | Microsoft Learn Microsoft 365 admin center [Compliance considerations] This change introduces multi-tenant administrative capabilities, including centralized visibility and management of AI costs, agents, and tenant configurations. Review these capabilities against your organization's existing administrative access and compliance requirements. -
Microsoft Copilot in PowerPoint for Windows, Mac, and the web: Introducing new sales-focused skills
MC1558023 · stayInformed · normal · Updated 11/17/2026 22:58
Services: Microsoft 365 apps
Read message
[What and why] In late October 2026, we began rolling out sales-focused Copilot skills in PowerPoint to help sellers, account teams, and sales leaders prepare customer materials, work with sales data, and refine presentations for sales conversations. Beginning in mid-November 2026, we will introduce additional skills that support tasks such as: Preparing customer-facing presentations, including sales pitches, customer business reviews, client portfolio reviews, and proposal or RFP responses. Working with sales data, including preparing internal sales reviews for leadership, reviewing pipelines and forecasts, and visualizing sales data. Preparing for sales conversations, including creating account briefs, battle cards, and responses to customer objections. Refining existing presentations, including adapting pitches for new audiences and reimagining slides. These examples illustrate the sales skills experience and are not a complete list. Skill names and availability may change as the experience evolves. [Rollout schedule] General Availability (Worldwide): These additional skills will begin rolling out in mid-November 2026, with rollout expected to complete by late November 2026. [Impact on your organization] Who is affected Users with an appropriate Copilot license, including sellers, account teams, and sales leaders. Platforms and services Microsoft Copilot in PowerPoint for Windows, Mac, and the web Microsoft Copilot Cowork What will happen Users will be able to use sales-specific skills to create and refine sales presentation drafts in Copilot in PowerPoint. These skills can help sales teams prepare customer and leadership materials more quickly, with content tailored to the audience, opportunity, and next steps. Users can continue creating presentations with Copilot in PowerPoint as they do today. Initially, users can access these skills under the Sales category in Manage Plugins from the Add sources, skills, and more menu in Copilot. When rollout completes, users can enable the Sales plugin from Choose plugins > Discover plugins in the Copilot menu or from Plugins in the left navigation in Copilot Cowork. [Action required and recommendations] No admin action is required for sales skills in PowerPoint. Admins can manage plugins for Copilot Cowork in the Microsoft 365 admin center and Microsoft 365 App Store. We recommend that you inform sellers, account teams, and sales leaders about the availability of these skills in PowerPoint for Windows, Mac, and web, and that you update internal training materials and documentation as needed. [Learn more] Use sales skills in PowerPoint and Cowork | Microsoft Support [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
New and upcoming Windows security and management capabilities
MC1557973 · stayInformed · normal · Updated 11/17/2026 22:10
Services: Windows
Read message
What and why At Microsoft Ignite 2026, Microsoft announced new and upcoming Windows capabilities across security, device and application management, recovery, and agent management. The announcements include developments in four key areas: Windows management: Updates to Windows Autopatch, application management, device health monitoring, and recovery. Additional developments include server management coming to Microsoft Intune with Windows Server 2028, the evolution of Windows declarative management, and controls for AI agents. Windows baseline protection: A new approach to establishing, maintaining, and verifying foundational Windows security configurations. Endpoint security and reliability: The latest updates to the Windows endpoint security platform and Driver Quality Initiative designed to improve system resilience and reduce disruptions associated with security software and drivers. Passwordless authentication: Expanded Windows Hello, web sign-in, and security key capabilities to support passwordless authentication across more scenarios. Rollout schedule Availability varies by capability. Refer to the linked articles for current availability, rollout timelines, prerequisites, and supported configurations. Impact on your organization These investments focus on helping your organization maintain secure, reliable, and up-to-date Windows environments while reducing administrative complexity. Action required/recommendations No immediate action is required. Today’s announcements can be used to identify capabilities of interest, review prerequisites and supported configurations, and plan for availability. For more context on the Windows announcements, see: Microsoft Ignite 2026: Building Windows for the next era of work Windows security at Ignite 2026: Start secure, protect what matters, prepare for AI Compliance considerations No specific compliance considerations are associated with these announcements. We recommend that you evaluate individual capabilities against your existing security and compliance requirements. -
(Updated) OneDrive transitions to the cloud.microsoft domain
MC1392563 · stayInformed · normal · Updated 11/17/2026 21:51
Services: Microsoft OneDrive
Read message
Updated November 17, 2026: We have updated the timeline. Thank you for your patience. [What and Why:] OneDrive is transitioning to the cloud.microsoft domain. Users will start seeing new URLs shown in the examples below as a part of their OneDrive experiences. Existing links continue to work — both domains will operate side by side indefinitely. As part of this transition, OneDrive URLs will change: Previous domain: contoso-my.sharepoint.com/ Unified domain: onedrive.cloud.microsoft/ This change aligns OneDrive with the broader Microsoft cloud domain strategy, creating a more consistent and recognizable experience across Microsoft 365 services. This update simplifies how users identify trusted Microsoft endpoints while maintaining compatibility with existing URLs and integrations. [Rollout Schedule:] General Availability (Worldwide): We began rolling out in early September 2026 (previously end of July) and expect to complete by end of September 2027 (previously early August 2026). We began enabling the early production tenants in early September, with the broader worldwide rollout continuing gradually over approximately one year. As a result, customers should not expect to see this change immediately in their tenants once GA is announced. [Impact on Your Organization:] Who is affected: All users accessing OneDrive Admins managing Microsoft 365 environments, network configurations, and custom solutions Platforms/Services: OneDrive(web primarily) What will happen: For users: Users will start seeing the cloud.microsoft domain in their OneDrive experiences (e.g., onedrive.cloud.microsoft instead of contoso-my.sharepoint.com). When users access content from geos different than their own, they will see a globe icon. No changes to file access, sharing, or collaboration functionality. The previous domain and unified domain will continue to exist side by side. Existing links will continue to work. For admins: No changes to admin functionality. The SharePoint URLs used for file storage and APIs remain unchanged (e.g., contoso-my.sharepoint.com continues to work for API calls). Important: Organizations with custom solutions that rely on OneDrive URL patterns should review those dependencies. Official Microsoft APIs (Microsoft Graph) will continue to function without changes. Custom solutions that parse or hardcode browser URLs may require updates. What is NOT changing: Existing links and bookmarks will continue to work. Links to previous domains are backwards compatible and will remain supported. There are no forced redirects from legacy URLs. Both domains will work side-by-side during and after the transition. SharePoint site URLs (e.g., contoso.sharepoint.com) are not affected by this change. Microsoft Graph APIs and other official APIs are not changing. File ownership, permissions, and sharing settings are unchanged. Consumer OneDrive URLs are not changing at this time and remain on live.com domain [Action Required/Recommendations:] No immediate action is required, but we recommend the following: Review any custom solutions that depend on OneDrive URL patterns. Ensure network rules allow traffic to *.cloud.microsoft. Update internal documentation and training materials with the new URL format. Prepare helpdesk teams for user questions about URL changes. Educate users to recognize the cloud.microsoft domain as trusted Optional administrative considerations: Review tenant allow list settings for external sharing Evaluate Tenant Restrictions v2 if applicable to your organization Consider upcoming capabilities such as anonymous link controls Learn more: Configure Tenant Restrictions - Microsoft Entra ID - Microsoft Entra External ID | Microsoft Learn [Compliance considerations:] No compliance considerations identified, review as appropriate for your organization. -
Microsoft Viva: Introducing Interactive Insights in the A365 Business Analytics app
MC1557766 · stayInformed · normal · Updated 11/17/2026 19:15
Services: Microsoft Viva
Read message
[What and why] We are introducing Interactive insights, an AI-powered feature in Agent 365 Business Analytics, to make it easier for users to understand AI adoption, engagement, and consumption data without manually building queries or reports. Using natural-language questions, users can curate summaries and generate visualizations and reports to identify patterns, understand usage and cost drivers, and inform decisions about AI adoption and investment. Responses are grounded in available data within each user's authorized scope. [Rollout schedule] Frontier Preview: Rollout will begin in mid-November 2026 and is expected to complete by late November 2026. General Availability (Worldwide): Rollout will begin in late March 2027 and is expected to complete by late April 2027. [Impact on your organization] Who is affected Tenants enrolled in the Frontier program. Eligible users with the following Agent 365 Business Analytics / Viva Insights / Microsoft 365 roles:Chief Officer Group Manager Analyst with global partition access Global Admin AI Admin Platforms and services Agent 365 Business Analytics Viva Feature Access Management (VFAM) What will happen Eligible users will see a new Interactive Insights tab in Agent 365 Business Analytics. Users can ask questions and follow-ups to explore trends, compare groups, and better understand AI usage and spending without manually building queries or reports. Access remains limited to each user's approved data scope. The feature does not expand users' data permissions. Interactive Insights will be enabled automatically for tenants enrolled in the Frontier program. Interactive Insights home screen [Action required and recommendations] We recommend that you review eligible users in your organization and communicate the new experience to them. If needed, you can disable Interactive Insights at the tenant, group, or user level by using admin controls. [Compliance considerations] Does the change store new customer data? No. Interactive insights analyzes customer data already available in Agent 365 Business Analytics and generates summaries and insights for users authorized to access that data. Optional contextual file uploads are user-initiated and subject to administrator configuration. Does the change alter how existing customer data is processed, stored, or accessed (e.g., documents, emails, chats, etc.)? No. Interactive insights does not change how existing customer documents, emails, chats, or other source content are processed, stored, or accessed. It provides a new way for authorized users to explore computed insights already available in Agent 365 Business Analytics, within their existing data permissions. Does the change introduce or significantly modify AI/ML or agent capabilities that interact with or provide access to customer data? Yes. Interactive insights introduces AI-powered analysis and content generation grounded in data within each user’s authorized scope. It does not modify source records or automatically carry out recommendations. Does the change provide end users any new way of interacting with generative AI? Yes. Eligible users can ask natural-language questions, refine analyses through follow-up requests, and generate summaries, visualizations, reports, and presentations. Does the change modify how users can access, export, delete, or correct their personal data within Microsoft 365 services (GDPR Data Subject Rights)? No. Interactive insights does not modify underlying personal records or replace existing access, export, correction, or deletion workflows. Users can delete their analysis sessions, and administrators can delete sessions for users, subject to applicable retention and hold requirements. -
Microsoft Agent 365 Business Analytics: Introducing Access Management
MC1557764 · stayInformed · normal · Updated 11/17/2026 19:14
Services: Microsoft Viva
Read message
[What and why] We are introducing Access Management for Agent 365 Business Analytics, previously Copilot Analytics, so admins can manage who has access and what they can do directly in the product. The new Access Management experience brings role assignment and permissions into one place for Global administrators, AI administrators, and Viva Insights administrators. This simplifies the previous experience that involved managing access across Viva Feature Access Management (VFAM) settings in the Microsoft 365 admin center and in-product Manager Settings. At the core of the new model are Access Policies, rules that define the capabilities users can access and the data they can see. Each policy combines two components: Permission Set: Defines what users can do, such as access dashboards and reports, export data, customize reports and publish them. Partition: Defines the population and datasets users can access, determining whose data they can see and which insights are available. Admins can assign access policies to individual users, Microsoft Entra security groups, Group Managers, or define users based on organizational attributes. Existing role assignments such as Chief officers, Managers, and Analysts will continue to work, with users automatically transitioned to the corresponding system-defined access policies. The existing Viva Insights Web App Delegation VFAM will continue to control who can use delegation. With the new access model, delegation within a custom partition will mirror the leader’s effective access for that partition. A delegate will never receive more access than the leader and, as the leader receives new access or permissions within that partition, the delegate’s access will automatically stay in sync without requiring the delegation to be updated. [Rollout schedule] General Availability (Worldwide): Rollout will begin in early January 2027 and is expected to complete by late January 2027. [Impact on your organization] Who is affected Global administrators, AI administrators, and Viva Insights administrators who manage access to Agent 365 Business Analytics. Users whose access is managed through access policies. Platforms and services Agent 365 Business Analytics Microsoft 365 admin center Microsoft Entra security groups Viva Feature Access Management (VFAM) What will happen Global administrators, AI administrators, and Viva Insights administrators will assign roles and permissions directly in Agent 365 Business Analytics. Global administrators, AI administrators, and Viva Insights administrators will receive Identification and export features automatically. Access policies will combine a permission set, which determines what users can do, with a partition, which determines which people and datasets users can see. Policies can be assigned to individual users, Microsoft Entra security groups, or, for group managers, organizational attributes. Existing role assignments will continue to work, and users will automatically move to system-defined access policies. Explicit grants in new access policies can override tenant-level VFAM restrictions. The IdentifiableOutput, Analyst Report Publish, CopilotDashboard Export, Report Customization and Agent Metrics Export VFAM settings will be controlled via permission sets. The existing Viva Insights Web App Delegation VFAM will continue to control who can use delegation. [Action required and recommendations] For tenants with the default state of the IdentifiableOutput, Analyst Report Publish, CopilotDashboard Export, Report Customization and Agent Metrics Export VFAM settings, we recommend that you: Review your current VFAM settings in the Microsoft 365 admin center and check who has the Copilot dashboard, Agent dashboard, export, identifiability, and publish enabled or restricted. Confirm who holds the Global administrator, AI administrator, and Viva Insights administrator roles. These admins will manage Access Management. Review access lists for leaders, group managers, and analysts against your organization's privacy requirements. Review your partitions and identification, minimum group size, user-level export, and insights settings. Chief officers can now view and export company-wide Cost insights. Select Edit for the Chief Officer access policy in the Access management page, and enable the toggle. This gives chief officers and their delegates access to all of the spend and billing measures for usage-based billing services. Managers can view and export team-wide Cost insights by default. To disable Cost insights for managers, you can turn off the toggle by clicking on 'Edit policy' for the Manager access policy. Important notice for tenants who have modified the default state any of the previously mentioned VFAM settings by creating custom policies: In addition to the above, we also recommend that you set up matching access policies within 30 days of availability of the new access management. [Learn more] We will update this post with new documentation prior to rollout. [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
Microsoft Teams: Registration capacity for town halls and webinars increases to 20,000
MC1557760 · stayInformed · normal · Updated 11/17/2026 19:13
Services: Microsoft Teams
Read message
[What and why] Starting in December, registration capacity for Microsoft Teams town halls and webinars scales with the event's attendee capacity, up to 20,000 registrations per event. Organizers with Teams Enterprise can allow up to 3,000 registrations. Organizers with Attendee Capacity Packs can allow up to 20,000. Organizers can use this to plan large-scale events with registration. [Rollout schedule] General Availability (Worldwide): We will begin rolling out in early December 2026 and expect to complete by late December 2026. [Impact on your organization] Who is affected Organizers of Teams town halls and webinars that use registration Admins who manage Teams events policies and Attendee Capacity Pack licenses Platforms and services Microsoft Teams (town halls and webinars) What will happen Registration capacity scales with attendee capacity, up to 20,000 registrations per event. Organizers with Teams Enterprise can allow up to 3,000 registrations. Organizers with Attendee Capacity Packs can allow up to 20,000 registrations. Large webinars with registration don't support broadcast-style streaming, which is available with town halls. Organizers still need the right events policy. No new policy access is needed, only the right Attendee Capacity Pack where applicable. Existing Teams events policies and admin controls don't change. We plan to support more registrations per event in future releases. [Action required and recommendations] No action is required. To prepare, you can: Tell organizers about the higher registration limits. Make sure organizers who need more than 3,000 registrations per event have an Attendee Capacity Pack of the right size. Assign packs in the Teams admin center (Add-on Licenses > Teams Events). Update internal training and documentation that mention a 1,000-registration limit. Review your Teams events policies in the Teams admin center (Meetings > Events policies) to confirm they meet your organization's needs. [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
Dynamics 365 Apps - Upgrade in-queue overflow to Conversation orchestration
MC1557671 · stayInformed · normal · Updated 11/17/2026 17:47
Services: Dynamics 365 Apps
Read message
We are announcing the ability to upgrade in-queue overflow to Conversation orchestration in Dynamics 365 Apps. This feature reached general availability on November 13, 2026. How does this affect me? This feature enables you to upgrade your existing in-queue overflow settings to a Conversation orchestration (CO) playbook, for one queue or many at once. Key functionality of this feature includes: Increased flexibility, with advanced options: Conversation orchestration offers capabilities that in-queue overflow doesn’t, including a wider range of conditions, actions tailored to different customer scenarios, and a single playbook that can be reused across multiple queues. Review before you confirm: See how your settings carry over to the playbook. Nothing changes until you confirm. One place for new overflow: New in-queue overflow configurations are now created in Conversation orchestration. Playbooks that match your current in-queue overflow setup are free. Playbooks with additional conditions, branches or context variables use Copilot credits. Your existing in-queue overflow keeps working and remains editable until you choose to upgrade. What action do I need to take? This message is for awareness, and no action is required. If you would like more information on this feature, please visit Upgrade legacy in-queue overflow to a conversation orchestration playbook. -
(Updated) Microsoft Teams: External presenters can manage event production controls
MC1443517 · stayInformed · normal · Updated 11/17/2026 17:39
Services: Microsoft Teams
Read message
Updated November 17, 2026: We have updated the timeline. Thank you for your patience. [What and why] Organizations can now allow trusted external presenters to manage Microsoft Teams event production controls. Federated (B2B) users and guest users can be assigned through the Who has control of production tools setting, enabling them to manage the attendee viewing experience during Teams events. This feature helps organizations that work with external event producers, agencies, and third-party event management partners by allowing authorized external presenters to perform production tasks without requiring internal staff to manage the event. This message is associated with Microsoft 365 Roadmap ID 567298. [Rollout schedule] Targeted Release: Beginning in early August 2026 and expected to complete by early October 2026 (previously early September) (previously mid-August) General Availability (Worldwide, GCC, GCC High, DoD): Beginning early August 2026 and expected to complete by late November 2026 (previously early November) [Impact on your organization] Who is affected Organizations that use Microsoft Teams events Event organizers who work with external presenters, production vendors, agencies, or trusted partners Federated (B2B) users and guest users who are invited to participate in Teams events Platforms and services Microsoft Teams Teams events What will happen Event organizers can grant production control permissions to federated (B2B) users and guest users. Authorized external presenters can manage production controls and determine what attendees see during an event. The feature is available only when an organizer explicitly assigns production control access. Existing events and configurations will not be modified automatically. [Action required and recommendations] No admin action is required before rollout. We recommend that you: Review internal guidance and governance policies for Teams events that include external participants. Inform event organizers about this new capability. Determine which external presenters, vendors, or partners should be authorized to receive production control permissions. Update any training or documentation used by event organizers, if applicable. Organizers can use the Who has control of production tools setting when configuring a Teams event to grant production access to trusted external users. [Compliance considerations] QuestionAnswer Does this change provide a new way for users, tenants, or subscriptions to communicate?Yes. This feature enables organizations to include federated (B2B) and guest users in Teams event production workflows, expanding collaboration and communication capabilities with trusted external participants. Does this change include an admin or organizer control?Yes. Event organizers can use the Who has control of production tools setting to grant or restrict production control access for trusted external users when configuring a Teams event. Can users enable or disable this capability themselves?Yes. Event organizers can choose whether to grant production control permissions to federated (B2B) and guest users when setting up an event. -
(Updated) Microsoft Teams Town halls: Upload custom backgrounds in Manage what attendees see
MC1307982 · stayInformed · normal · Updated 11/17/2026 17:37
Services: Microsoft Teams
Read message
Updated November 17, 2026: We have updated the timeline. Thank you for your patience. [Introduction] To help organizations deliver more polished and branded town hall events, Microsoft Teams is introducing the ability for organizers and presenters to upload custom background images in the Manage what attendees see experience. This enhancement allows teams to replace default backgrounds with branded visuals—such as company logos or event-specific designs—so presenters and shared content appear consistently on brand for attendees. This feature is available for Teams events organizers with a Teams Enterprise license. This update applies to Teams for Windows desktop and Mac desktop. This message is associated with Microsoft 365 Roadmap ID 561493. [When this will happen] Targeted Release: Rollout begins in early June 2026 (previously late May) and is expected to complete by early June 2026 (previously late May). General Availability (Worldwide): Rollout begins in early June 2026 and is expected to complete by late November 2026 (previously early November). [How this affects your organization] Who is affected Organizers and presenters of Teams town hall events Users assigned a Teams Premium license Tenants using Manage what attendees see in town halls What will happen Organizers and presenters can upload custom background images directly within the Manage what attendees see experience. Uploaded backgrounds appear behind presenters and shared content in supported town hall layouts. JPEG and PNG image formats are supported, with recommended resolution guidance shown during upload. Custom backgrounds appear alongside existing default background options in the background picker. The feature is enabled by default for eligible users and applies only to town hall events where Manage what attendees see is enabled. There is no change to standard Teams meetings or webinars. [What you can do to prepare] No admin action is required before rollout. Consider notifying users who organize or present town halls about this new capability. Prepare branded background images that align with your organization’s visual identity guidelines. Update internal documentation or event playbooks if you provide guidance on hosting town halls. Optionally, run a test town hall event to familiarize presenters with the upload flow and attendee experience. Learn more: Customize the event screen - Manage what attendees see in Microsoft Teams | Microsoft Support [Compliance considerations] QuestionAnswer Does the change store new customer data?Yes. Uploaded custom background images are stored as part of the Teams town hall event configuration. Does the change alter how existing customer data is processed or accessed?Yes. Background images are rendered behind presenters and shared content during the live event for attendees. -
(Updated) Microsoft Teams: Report guest invitations for security concerns
MC1530615 · stayInformed · normal · Updated 11/17/2026 17:34
Services: Microsoft Teams
Read message
Updated November 17, 2026: We have updated the timeline. Thank you for your patience. [What and Why:] Microsoft Teams will enable users to report guest invitations for security concerns directly from Teams. When users receive an unexpected or potentially malicious invitation to join another organization as a guest, they can report it to their IT admin for review, helping identify and mitigate phishing and other abuse through guest invitations. [Rollout Schedule:] General Availability (Worldwide): We will begin rolling out in late November 2026 (previously mid-November) and expect to complete by late November 2026 (previously mid-November). [Impact on Your Organization:] Users can report suspicious guest invitations when declining them in Teams. Reports are shared with their IT admin through the User reported security submissions report in the Teams admin center and with Microsoft for review. [Action Required/Recommendations:] No action is required for organizations that already have Report a security concern enabled in their Teams messaging policy. Admins can manage this capability through Teams admin center > Messaging policies > Report a security concern. [Compliance considerations:] QuestionAnswer Does the change include an admin control?Yes. The capability is controlled through the Teams messaging policy setting for Report a security concern. -
(Updated) Microsoft Teams: Third-party synthetic audio and video detection in meetings
MC1509787 · planForChange · normal · Updated 11/17/2026 17:34
Services: Microsoft Teams
Read message
Updated November 17, 2026: We have updated the timeline. Thank you for your patience. [What and Why:] Organizations can enhance meeting security with synthetic audio and video detection solutions provided by certified third-party providers. Third-party detection solutions analyze meeting media for signs of synthetic or manipulated audio and video and send detection signals to Teams, enabling integrated in-meeting experiences and controls. Important: Synthetic media detection is performed by the third-party provider. Microsoft Teams provides the platform integration and experiences for surfacing and acting on detection signals from supported providers. This message is associated with Microsoft 365 Roadmap ID 573451. [Rollout Schedule:] Targeted Release (Worldwide): We will begin rolling out in late November 2026 (previously mid-November) and expect to complete by late November 2026. General Availability (Worldwide): We will communicate via Message center when we are ready to proceed. [Impact on Your Organization:] Organizations can choose and integrate certified third-party deepfake detection solutions into Microsoft Teams meetings, helping protect users from emerging AI-generated voice and video threats. This gives customers more flexibility to meet security and compliance needs while enabling users to make more informed trust decisions during meetings. [Action Required/Recommendations:] To use third-party Synthetic Audio and Video Detection in Microsoft Teams, administrators should evaluate and select a supported detection provider, deploy the provider app through Manage apps in the Teams admin center, grant required permissions, and configure applicable Teams meeting policies. [Compliance considerations:] QuestionAnswer Does the change introduce or significantly modify AI/ML capabilities that interact with customer data?Yes. Certified third-party providers may analyze meeting audio/video signals for synthetic media detection. Review provider terms, data handling, and compliance documentation before enabling. Does the change include an admin control?Yes. Admins manage provider app deployment, permissions, and Teams meeting policy configuration. -
(Updated) Microsoft Defender for Office 365: Enhancing how we handle promotional mail
MC1279093 · planForChange · normal · Updated 11/17/2026 17:19
Services: Microsoft Defender XDR
Read message
Updated November 17, 2026: We have updated the timeline. Thank you for your patience. [Introduction] We are enhancing how Microsoft Defender for Office 365 identifies and manages promotional email. Promotional messages will be tagged as “promotions” (previously “Bulk” in preview) and can be moved automatically to a new Promotions folder. The system learns from user actions, such as moving messages into or out of the Promotions folder and applies those preferences to future messages. These improvements reduce inbox clutter and help users stay focused while still receiving promotional content they want. [When this will happen] Public Preview (Limited): We will begin rolling out in mid-April 2026 and expect to complete by mid-May 2026 (previously end of April). To be included in the public preview program, send an email to BulkMailPreviews@microsoft.com indicating: Organization name, Tenant ID and your onmicrosoft.com domain (e.g contoso.onmicrosoft.com). Slots are limited and will close on May 15th, 2026. General Availability (Worldwide): Rollout begins in late July 2026 (previously early July) and is expected to complete by mid-February 2027 (previously late November 2026). General Availability (DoD, GCC, GCC High): We will begin rolling out in late July 2026 (previously early July) and expect to complete by end of March 2027 (previously late November 2026). [How this affects your organization] Who is affected All organizations that use Microsoft Defender for Office 365 across Worldwide, GCC, GCC High, and DoD clouds What will happen Incoming promotional messages will be tagged as “promotions.” (previously “Bulk” in private and public preview) If the Bulk Moves Enabled setting is turned on, tagged messages will automatically move to a Promotions folder created in user mailboxes. The system will learn from user actions when they move messages into or out of the Promotions folder. Future messages will follow the learned behavior. Users will be able to create inbox rules that reference the promotions tag.During the Public Preview: Tagging will be opt-in and configured using Exchange transport rules. Folder routing will be enabled through anti-spam policy settings (“Bulk moves enabled”). Both features will be able to be scoped to pilot security groups for a staged rollout. At Worldwide General Availability, tagging will be enabled by default for all tenants and will always remain that way. For the tagging experience, supported outlooks clients are Outlook on the web and outlook for Windows. Other client such as Outlook for IOS/Android and classic outlook will follow subsequently For the promotions folder experiences, Outlook on the web, outlook for Windows, Outlook for IOS/Android and classic outlook are all supported. Figure one - Admin configuration for tagging using exchange transport rule (required for public preview opt-In): Figure two - Admin configuration for Bulk moves enabled to provision the promotions folder: Figure three - System tagging of “Promotions” in outlook client and promotions folder (previously tagged as “Bulk” in private and public preview): Figure four - User inbox rules using the promotions” tag: [What you can do to prepare] To be included in the public preview program, send an email to BulkMailPreviews@microsoft.com indicating: Organization name, Tenant ID and your onmicrosoft.com domain (e.g contoso.onmicrosoft.com). Slots are limited and will close on April 30th, 2026. Review your internal mailbox and message handling guidance and update training materials if needed. If you plan to participate in the Public Preview, review your Exchange transport rule and anti-spam policy configurations to determine if you want to opt-in. Monitor the product documentation. You can review the following: Bulk email detection and bulk complaint level (BCL) in cloud organizations [Compliance considerations] QuestionAnswer Does the change alter how existing customer data is processed, stored, or accessed?Yes. Incoming email will receive the promotions classification and may be moved automatically to the Promotions folder depending on admin configuration. Does the change introduce or significantly modify AI or ML that interacts with customer data?Yes. The system learns from user actions when they move messages and applies that learning to future similar messages. Does the change include an admin control, and can it be controlled through Entra ID group membership?Yes. Admins can enable or disable Bulk Moves Enabled and can opt in to tagging during Public Preview. These controls can be scoped using existing admin delegation models. Does the change allow a user to enable or disable the feature themselves?Yes. Users can override tagging behavior by moving messages in or out of the Promotions folder, which trains the ML model and adjusts future message handling. -
Dynamics 365 Contact Center - Set wait times as short as 5 seconds in Orchestration playbooks
MC1557570 · stayInformed · normal · Updated 11/17/2026 17:13
Services: Dynamics 365 Apps
Read message
We are increasing the maximum frequency of orchestration playbook re-evaluations by reducing the wait time from 30 seconds down to 5 seconds in Dynamics 365 Contact Center. This change reached general availability today, November 17, 2026. How does this affect me? With this shorter interval, you get finer control over priority escalation and Bullseye pool expansion. As a result, conversations reach the right queue or specialist sooner when wait times or queue status change. Once available, you can update existing playbooks and reduce the wait time to as low as 5 seconds. What action do I need to take? This message is for awareness, and no action is required. -
(Updated) Outlook: Insert Symbols
MC1479513 · planForChange · normal · Updated 11/16/2026 23:54
Services: Exchange Online
Read message
Updated November 16, 2026: We have updated the timeline. Thank you for your patience. [What and Why:] A variety of symbols can be added to an email message that you are composing. On the Insert tab, select Symbols. [Rollout Schedule:] General Availability (Worldwide): We will begin rolling out early January 2027 (previously late November 2026) and expect to complete by late January 2027 (previously late December 2026). Targeted Release (Worldwide): We will begin rolling out on mid-October 2026 and expect to complete by mid-November 2026 (previously early November). General Availability (GCC): We will begin rolling out on early January 2027 (previously late November 2026) and expect to complete by late January 2027 (previously late December 2026). General Availability (GCC High): We will begin rolling out on early January 2027 (previously late November 2026) and expect to complete by late January 2027 (previously late December 2026). General Availability (DoD): We will begin rolling out on early January 2027 (previously late November 2026) and expect to complete by late January 2027 (previously late December 2026). [Impact on Your Organization:] Who is affected: Users composing emails in new Outlook for Windows and Outlook on the web. Help desk and training teams that support Outlook message composition experiences. Platforms/Services: Exchange Online. New Outlook for Windows and Outlook on the web. What will happen: Users will be able to insert symbols into email messages from the Insert tab. This adds a built-in way to include special characters and symbols while composing messages. The capability will roll out automatically during the scheduled rollout window. [Action Required/Recommendations:] No admin action is required. Inform users that symbols can be inserted from the Insert tab when composing email. Update internal Outlook training or help desk guidance if it references how users add special characters to messages. [Compliance considerations:] No compliance considerations identified. Review as appropriate for your organization. ----------------------------For Processing Do Not Delete------------------------------ Do you need to update your Service description: No Post Publish Date: 9/16/2026 Change type: Feature Product marketing manager: sarahspieler@microsoft.com Major Update: No -
(Updated) Microsoft Viva Engage: Reducing reply notification volume in email
MC1466754 · stayInformed · normal · Updated 11/16/2026 23:50
Services: Microsoft Viva
Read message
Updated November 16, 2026: We have updated the timeline. Thank you for your patience. [What and why] Microsoft Viva Engage is updating email reply notifications to make them more relevant and intent-driven. With this change, users will continue to receive email notifications for interactions that directly involve them, such as direct replies and @mentions, while notification emails generated from broader participation in conversations will be reduced. This update is designed to help users focus on the conversations most relevant to them and reduce unnecessary email volume. Existing community subscription settings and other notification controls will remain unchanged. [Rollout schedule] General Availability (Worldwide): Beginning in early September 2026 and expected to complete by end of November 2026 (previously late October) [Impact on your organization] Who is affected Users who receive Microsoft Viva Engage notifications through email Organizations that use Viva Engage communities or storylines Users who participate in Viva Engage conversations Platforms and services Microsoft Viva Engage Viva Engage email notifications What will happen After this rollout: Users will continue to receive email notifications when: They start a conversation. Someone directly replies to their post or comment. They are @mentioned. Users will no longer be automatically subscribed to all future replies in a conversation because they: Read the conversation. Commented on the conversation. Community subscribers will continue to receive notifications for new posts and announcements. Storyline followers will continue to receive notifications for new posts and announcements. Existing user notification preferences and tenant-level controls will remain unchanged. No new admin settings, policies, or controls will be introduced. The change will be enabled automatically as part of the service update. [Action required and recommendations] No action is required. You may want to: Review and update internal documentation that describes Viva Engage email notifications. Update training and support materials that reference reply notification behavior. Inform support and help desk teams that users may notice a reduction in email notifications from active conversations. Gather user feedback after rollout is complete. [Compliance considerations] No compliance considerations identified, review as appropriate for your organization. -
Microsoft Defender: Similar cases comes to the unified security operations platform
MC1556107 · stayInformed · normal · Updated 11/16/2026 22:30
Services: Microsoft Defender XDR
Read message
[What and why] A new Similar cases tab appears on the incident page in the Microsoft Defender portal. The tab lists up to 20 incidents that share alert titles or entities with the current incident, helping security analysts identify recurring patterns and see how similar cases were handled. The Similarity reason column shows why each incident appears in the list. This update brings the Similar incidents experience from Microsoft Sentinel in the Azure portal to the unified security operations platform. As part of this update, the Associated incidents card on the Summary tab will be renamed Recommended correlations. Similar cases show separate cases that share alert titles or entities, while Recommended correlations identifies cases that are likely part of the same attack. The content of the renamed card will not change. [Rollout schedule] Public Preview: Available now. General Availability (Worldwide): We will begin and complete rollout in early December 2026. [Impact on your organization] Who is affected Security analysts who investigate cases in the Microsoft Defender portal, including Microsoft Sentinel customers who use the Defender portal Platforms and services Microsoft Defender portal Microsoft Defender XDR Microsoft Sentinel in the Defender portal What will happen A new Similar cases tab will appear on the case page: The tab will list up to 20 cases that share alert titles or entities with the current incident. The Similarity reason column will show why an incident appears in the list. Analysts can hover over the info icon to view the items the cases have in common: The Associated incidents card on the incident Summary tab will be renamed Recommended correlations. The content of the renamed card will not change. [Action required and recommendations] No action is required to prepare for this change. Learn more Alert correlation and incident merging in the Microsoft Defender portal - Microsoft Defender XDR | Microsoft Learn Investigate incident cases in the Microsoft Defender portal - Microsoft Defender XDR | Microsoft Learn Investigate incidents in the Microsoft Defender portal (Legacy) - Microsoft Defender XDR | Microsoft Learn [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
Microsoft SharePoint: Enhanced data access governance reports and site access reviews
MC1556106 · stayInformed · normal · Updated 11/16/2026 22:29
Services: SharePoint Online
Read message
[What and why] Microsoft SharePoint is enhancing data access governance reports and site access reviews to give SharePoint admins more control, flexibility, and transparency when identifying and addressing potential data exposure. These updates help admins prioritize sites that may present the greatest data risk, direct review requests to the appropriate recipients, and track whether notifications were delivered. [Rollout schedule] General Availability (Worldwide, GCC, GCC High, and DoD): We will begin rolling out in late November 2026 and expect to complete by early December 2026 [Impact on your organization] Who is affected SharePoint admins who use data access governance reports and initiate site access reviews Platforms and services SharePoint Online SharePoint admin center Data access governance reports Site access reviews What will happen The Site permissions across your organization report will show the number of files flagged by sensitive information types, such as credit card numbers, Social Security numbers, and custom-defined patterns. SharePoint admins will be able to use this information to prioritize sites that may present greater data risk. Admins will be able to direct site access review requests to site owners or site admins. Admins will be able to send either one consolidated review email to all recipients or separate emails to individual recipients. Admins will be able to view email delivery status and the complete recipient list for review requests. [Action required and recommendations] No action is required before rollout. We recommend that SharePoint admins: Review current site permissions and data access governance processes. Inform relevant SharePoint admins about the enhanced reporting and site access review capabilities. Update internal documentation and workflows as appropriate. Confirm that site owners and site admins are prepared to receive and complete site access review requests. Learn more Data access governance reports for SharePoint sites - SharePoint in Microsoft 365 | Microsoft Learn Initiate site access reviews for Data access governance reports - SharePoint in Microsoft 365 | Microsoft Learn [Compliance considerations] ConsiderationExplanation Does the change alter how existing customer data is accessed or processed?Yes. The Site permissions across your organization report will display counts of files flagged by sensitive information types. Does the change alter how admins can monitor, report on, or demonstrate compliance activities?Yes. SharePoint admins will receive additional reporting information about files flagged by sensitive information types and greater visibility into site access review recipients and email delivery status. Does the change include an admin control?Yes. SharePoint admins will be able to select review recipients and choose between consolidated and individual review emails. -
Microsoft PowerPoint: Introducing plugins for Microsoft 365 Copilot
MC1556104 · stayInformed · normal · Updated 11/16/2026 22:28
Services: Microsoft 365 apps
Read message
[What and why] We are introducing plugins for Microsoft 365 Copilot in PowerPoint to extend Copilot's capabilities with new skills and connectors. Plugins bring specialized capabilities and information from connected services into presentation workflows, helping users create and refine presentations with content relevant to their work. [Rollout schedule] Frontier (Worldwide): Rollout is anticipated to begin in mid-November 2026 and complete by late November 2026. General Availability (Worldwide): Rollout is anticipated to begin in late November 2026 and complete by the end of November 2026. Note: This rollout schedule is subject to change. We will update this post with a confirmed rollout schedule. [Impact on your organization] Who is affected Users of Microsoft 365 Copilot in PowerPoint who have access to plugins. Platforms and services PowerPoint for Windows PowerPoint for Mac PowerPoint for the web Microsoft 365 Copilot What will happen Users will be able to discover and use plugins available to them in Copilot within PowerPoint. Plugins will extend Copilot's capabilities with specialized skills and connectors. Users will be able to incorporate capabilities and information from connected services into their presentation workflows. [Action required and recommendations] We recommend that you review available plugins and manage access for your organization in the Microsoft 365 admin center. [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
Microsoft Teams Mobile: Introducing shared call history in the Queues app
MC1556098 · stayInformed · normal · Updated 11/16/2026 22:28
Services: Microsoft Teams
Read message
[What and why] We are introducing shared call history in the Queues app on Microsoft Teams mobile, allowing authorized call queue representatives to view calls handled across their queue. This includes missed, answered, outgoing, and voicemail calls. By extending the existing desktop experience to mobile, we are helping teams coordinate customer follow-ups, avoid duplicate callbacks, and manage calls more efficiently while working away from their desks. [Rollout schedule] General Availability (Worldwide): Rollout will begin in early December 2026 and is expected to complete by mid-December 2026. [Impact on your organization] Who is affected Representatives and supervisors with access to shared call history in the Queues app, which is included with a Teams Premium license. Platforms and services Microsoft Teams mobile, Queues app What will happen Authorized representatives can view shared call history across their call queue, including missed, answered, outgoing, and voicemail calls. Shared call history on mobile uses the same administrative settings as the desktop experience. Users can filter call history by resolution status to identify calls that need attention. Users can tap a call to view details, including the caller, call type, time, voicemail or forwarding information, and a timeline of the call's progression through the queue. The system automatically marks missed calls as Unresolved, allowing representatives to identify customers who need follow-up. Users can change missed call statuses to In progress or Resolved. All queue members with access to shared call history can see the updated status, who made the change, and when. Users without shared call history enabled will continue to see only their personal call history. [Action required and recommendations] No new administrative action is required for this rollout. We recommend that you inform call queue representatives about the new mobile experience, particularly how to update missed call statuses to avoid duplicate follow-ups. If your organization already uses shared call history, eligible users will automatically receive the mobile experience. If shared call history is not enabled, you can enable it in the Teams admin center by creating a Shared Call History template and assigning it to your call queues. You can grant access to all queue members or restrict access to authorized users. [Learn more] Planning - Shared Call History for voice applications - Microsoft Teams | Microsoft Learn [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
Microsoft Teams: Audio announcement for Recording and Transcription
MC1556096 · stayInformed · normal · Updated 11/16/2026 22:27
Services: Microsoft Teams
Read message
[What and Why:] The recording feature in Microsoft Teams now supports an audio announcement for Teams meetings and calls. With this new functionality, admins can enable a policy that plays an audio announcement when recording or transcription starts. This can be applied tenant-wide or to specific groups. The announcement helps ensure allowed participants who are permitted by policy are informed and improves accessibility awareness. This setting is available in both Meeting Policy and Calling Policy. [Rollout Schedule:] Public Preview (Worldwide): We began rolling out on early May 2026 and expect to complete by mid-December 2026. General Availability (Worldwide): We will begin rolling out on mid-December 2026 and expect to complete by early January 2027. General Availability (GCC): We will begin rolling out on mid-December 2026 and expect to complete by late January 2027. General Availability (GCC High, DoD): We will begin rolling out on mid-December 2026 and expect to complete by late January 2027. [Impact on Your Organization:] None. [Action Required/Recommendations:] No admin action is required. The default audio announcement policy is OFF; it can be turned on as needed. [Compliance considerations:] Confirmed that compliance recording is not supported with this feature. Review as appropriate for your organization. -
Plugins in PowerPoint for Microsoft 365 Copilot [Mac]
MC1556095 · stayInformed · normal · Updated 11/16/2026 22:26
Services: Microsoft 365 apps
Read message
[What and Why:] Plugins are coming to PowerPoint for Mac, adding new skills and connectors that extend what Copilot can do. Plugins bring specialized capabilities and information from connected services into presentation workflows. [Rollout Schedule:] General Availability (Worldwide): We will begin rolling out mid-November 2026 and expect to complete by early December 2026. [Impact on Your Organization:] Users will be able to discover and use plugins available to them in Copilot within PowerPoint for Mac, helping them create and refine presentations with capabilities and content relevant to their work. [Action Required/Recommendations:] Admins can review available plugins and manage access for their organization in the Microsoft 365 admin center. [Compliance considerations:] No compliance considerations identified. Review as appropriate for your organization. -
Changes to site logo URL metadata in SharePoint search results
MC1556092 · planForChange · normal · Updated 11/16/2026 22:24
Services: Microsoft 365 suite
Read message
[What and Why:] We are making a change to how SharePoint site logo URLs are maintained in search metadata to improve search indexing efficiency and reliability. Going forward, changes to a SharePoint site's logo URL will no longer automatically update the SiteLogoUrl property on individual files and other items within that site. [Rollout Schedule:] General Availability (Worldwide): We will begin rolling out in early December 2026 and expect to complete by early March 2027. [Impact on Your Organization:] The SiteLogoUrl property will continue to be maintained for SharePoint sites. Individual items may retain a previously indexed SiteLogoUrl value, even after the site's logo changes. Applications or custom solutions that retrieve this property from individual items through search APIs may receive an outdated value. [Action Required/Recommendations:] In the unlikely case that your organization uses the SiteLogoUrl property from individual search results, we recommend retrieving the current site logo directly from the associated SharePoint site instead. No action is required if your organization does not rely on this property. [Compliance considerations:] No compliance considerations identified. Review as appropriate for your organization. -
Plugins in PowerPoint for Microsoft 365 Copilot [Win32]
MC1556090 · stayInformed · normal · Updated 11/16/2026 22:21
Services: Microsoft 365 apps
Read message
[What and Why:] Plugins are coming to PowerPoint for Windows, adding new skills and connectors that extend what Copilot can do. Plugins bring specialized capabilities and information from connected services into presentation workflows. [Rollout Schedule:] General Availability (Worldwide): We will begin rolling out mid-November 2026 and expect to complete by early December 2026. [Impact on Your Organization:] Users will be able to discover and use plugins available to them in Copilot within PowerPoint for Windows, helping them create and refine presentations with capabilities and content relevant to their work. [Action Required/Recommendations:] Admins can review available plugins and manage access for their organization in the Microsoft 365 admin center. [Compliance considerations:] No compliance considerations identified. Review as appropriate for your organization. -
Microsoft 365 admin center: Unified release preferences for Standard, Deferred, and Frontier
MC1556082 · planForChange · normal · Updated 11/16/2026 22:15
Services: Microsoft 365 suite
Read message
[What and Why:] We're introducing a unified release preferences experience in the Microsoft 365 admin center. This brings together Standard release, Deferred release, and Frontier settings, making it easier to manage when users receive eligible generally available features and who participates in eligible preview experiences. [Rollout Schedule:] General Availability (Worldwide): We will begin rolling out in mid-November 2026 and expect to complete by end of November 2026. [Impact on Your Organization:] Who is affected: Administrators managing release preferences for their organization. Platforms/Services: Microsoft 365 admin center (Settings > Org settings > Release preferences); Microsoft 365 Copilot release preferences; Targeted Release. What will happen: Administrators will manage these settings in the unified Release preferences panel under Settings > Org settings > Release preferences. Standard or Deferred release determines when users receive eligible generally available features. Standard users receive features as they roll out to the Standard audience. Deferred users receive eligible major features approximately 30 days after the start of their Standard rollout, allowing additional preparation time. Frontier provides optional participation in eligible public preview experiences, independent of the Standard or Deferred preference. For example, users can participate in Frontier previews while remaining on Deferred release for eligible generally available features. Organizations can set Standard or Deferred as their organization's release preference and assign selected users to the opposite preference through individual assignments or Microsoft Entra ID security groups. Existing Standard/Deferred selections and exception assignments configured under Copilot release preferences: General availability will carry forward into the unified experience. The existing Copilot Frontier entry point will remain available and open the unified panel with Frontier settings in focus. Existing Targeted Release settings will remain visible in the unified experience, but administrators will not be able to modify them or enroll new users or organizations in Targeted Release. Existing configurations will continue to apply to features delivered through that model until retirement. This update does not change the separately communicated Targeted Release retirement schedule. [Action Required/Recommendations:] No action is required to receive the unified experience or to carry forward your existing Standard/Deferred configuration. Review your organization's release preference, exception assignments, and Frontier participation. Update internal administrator guidance to reflect the unified experience. Organizations currently using Targeted Release should also review the separately communicated retirement guidance. [Compliance considerations:] No compliance considerations identified. Review as appropriate for your organization. -
(Updated) Microsoft Defender for Office 365: New MessageContents table in Advanced Hunting for Microsoft Teams messages
MC1474106 · stayInformed · normal · Updated 11/16/2026 17:16
Services: Microsoft Defender XDR
Read message
Updated November 16, 2026: We have updated the timeline. Thank you for your patience. [What and why] We're introducing a new MessageContents table in Advanced Hunting for Microsoft Teams messages. This new table helps security operations teams investigate threats in Teams by providing access to Teams message snippets and associated message metadata during threat investigations. This capability enhances security investigations by allowing authorized analysts to correlate Teams message activity with other security signals available in Advanced Hunting, helping organizations detect, investigate, and respond to threats more effectively. [Rollout schedule] General Availability (Worldwide): Beginning in late September 2026 and expected to complete by late November 2026 (previously mid-November) [Impact on your organization] Who is affected Security administrators and security analysts who use Microsoft Defender XDR Advanced Hunting Organizations that investigate security incidents involving Microsoft Teams communications Platforms and services Microsoft Defender XDR Microsoft Defender for Office 365 Microsoft Teams Advanced Hunting What will happen A new MessageContents table will become available in Advanced Hunting. Authorized users will be able to query Teams message snippets and related message metadata. Analysts can correlate Teams message information with other Advanced Hunting data sources during investigations. The table can contain Teams message content, so access is permission controlled. Users must have the required Advanced Hunting and message preview permissions to access and query the table. Users without the required permissions will not have access to the table. Users without the required permissions will not have access to the table. The table currently supports Teams messages available through the underlying Teams message metadata source, including messages containing URLs and federated messages. [Action required and recommendations] No action is required if your organization does not plan to use this capability. If you plan to use this feature: Review existing role assignments and determine which security administrators and analysts should have access to Teams message content for security investigations. Review the required Advanced Hunting and message preview permissions before providing access. Consider updating internal security investigation procedures and documentation. Learn more Advanced hunting overview in Microsoft Defender XDR - Microsoft Defender XDR | Microsoft Learn [Compliance considerations] QuestionAnswer Does the change alter how existing customer data is processed, stored, or accessed?Yes. Authorized users with the required permissions can access Teams message snippets and associated message metadata through the new MessageContents table in Advanced Hunting. -
(Updated) Microsoft Viva Insights: New Power BI report publishing capabilities for leaders
MC1489942 · planForChange · normal · Updated 11/16/2026 17:14
Services: Microsoft Viva
Read message
Updated November 16, 2026: We have updated the timeline. Thank you for your patience. [What and why] We are expanding report publishing capabilities in Microsoft Viva Insights to include leaders, such as chief officers, managers, and their delegates. As part of this update, in Viva Feature Access Management, the Analyst report publish setting will be renamed to Report publish. This setting, which is on by default, will continue to be managed by Global Admins and Insights Admins, and will govern publishing for both analysts and leaders. This update enables leaders to directly publish and distribute curated Power BI reports available in Viva Insights without requiring an analyst to publish on their behalf. [Rollout schedule] General Availability (Worldwide and GCC): Rollout begins in mid-December 2026 (previously early November) and is expected to complete by end of December 2026 (previously late November). [Impact on your organization] Who is affected Organizations using Microsoft Viva Insights report publishing capabilities. Analysts, chief officers, managers, delegates, Insights Admins, and Global Admins. Users who receive published Viva Insights reports. Platforms and services Microsoft Viva Insights Power BI reports available through the Viva Insights Reports tab What will happen All analysts and leaders will be able to publish Power BI reports that are available to them in the Reports tab. Users can publish either default or customized reports available to them. Publishers can define the audience, report title, description, and publication end date. Recipients will receive an email notification when a report is published to them, and can access published reports from the Viva Insights Reports tab. Published reports can be shared using either: Unfiltered publish, where recipients view the report using the full data scope available for that report. Manager-hierarchy publish, where recipients view the report based on the applicable manager hierarchy. If a published report is configured to refresh weekly or monthly, the underlying query will continue to refresh until the publication end date. Analysts and leaders will be able to manage published reports through the Manage publishes option. Recipients can view and interact with published reports but cannot download reports, access row-level data, modify or manage publications, extend access, or republish reports. If a publisher loses the qualifying role used to publish the report, recipients will retain access until the publication expires. The existing Analyst report publish feature access control will be renamed to Report publish. This control will govern report publishing for analysts and leader personas, remains managed by Global Admins and Insights Admins, and is on by default. Insights Admins will have visibility into published reports through the Admin Publish Reports experience, including the ability to view and remove publications and publish reports on behalf of users. Setting up report properties prior to publishing View and manage published reports [Action required and recommendations] No action is required. We recommend that you review your organization's report publishing governance and processes prior to rollout. [Learn more] Publish reports | Microsoft Learn [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
(Updated) Microsoft Teams: Distinguish invites among Attendee, Presenter, and Co-organizer emails
MC1009930 · stayInformed · normal · Updated 11/16/2026 17:06
Services: Microsoft Teams
Read message
Updated November 16, 2026: We have updated the timeline. Thank you for your patience. Microsoft Teams Events invite emails will be separated based on the role of the participant. Event organizers will get an email explaining the specific roles of participants in the event. Similarly, each presenter will get a separate calendar invite, allowing the organizers of town halls to maintain separate invites for attendees. This message is associated with Microsoft 365 Roadmap ID 476488. [When this will happen:] Targeted Release: We will begin rolling out early January 2027 (previously early December 2026) and expect to complete by mid-January 2027 (previously mid-December 2026) General Availability (Worldwide, GCC, GCC High): We will begin rolling out mid-January 2027 (previously mid-December 2026) and expect to complete by late January 2027 (previously mid-January) [How this will affect your organization:] This feature update allows the organizers of town halls to maintain separate invites for attendees. [What you need to do to prepare:] This rollout will happen automatically with no admin action required. You may want to notify your users about this change and update any relevant documentation as appropriate. -
Dynamics 365 Field Service - Preserve actual booking End Time when completion is recorded later
MC1552365 · stayInformed · normal · Updated 11/14/2026 03:40
Services: Dynamics 365 Apps
Read message
We are announcing the ability to Preserve actual booking End Time when completion is recorded later in Dynamics 365 Field Service. This feature will reach public preview on November 22, 2026. How does this affect me? This feature allows Field Service administrators to choose whether completion by the booked resource automatically changes the booking End Time. Admins complete bookings later can preserve the existing or explicitly supplied work end, helping booking duration and downstream time and cost records remain aligned with when the work occurred. Use the organization-level Set End Time on booked resource completion setting in Field Service settings to control the automatic End Time update. With the setting set to Yes, which is the default, current behavior is preserved. When the booked resource completes a booking without supplying End Time, Field Service sets End Time to the completion time and recalculates Duration. With the setting set to No, Field Service preserves End Time and Duration when the booked resource completes the booking unless the completion request explicitly supplies a different End Time. Completion by another user or an integration continues to preserve End Time for either setting value. When the setting is No and the booked resource completes the booking, Field Service uses the retained or supplied End Time as the effective Completed booking timestamp. This keeps timestamp-derived booking journals and automatic time entries aligned with the recorded work end. Dataverse audit fields continue to show when the completion was submitted. The setting applies to future completion transitions and does not rewrite historical bookings. It does not change the booking-status lifecycle, invoice generation, or the existing Work Order Completed On calculation, which continues to use the latest eligible booking End Time. What action do I need to take? This message is for awareness, and no action is required. -
Release Planner Retirement: D365, Power Platform, and Dataverse Move to AI at Work
MC1461529 · planForChange · normal · Updated 11/14/2026 01:05
Services: Dynamics 365 Apps, Power Apps, Microsoft Power Automate
Read message
Release Planner is now retired. To stay informed about upcoming capabilities and prepare your organization for feature rollout and adoption, use the resources shared below. To view product availability for Dynamics 365, Power Platform and Copilot Studio, visit the new Learn page at https://aka.ms/d365-product-availability. Starting this fall, Dynamics 365, Power Platform, and Dataverse roadmap content is joining the AI at Work roadmap, giving customers a single destination to discover upcoming capabilities, track rollout progress, and plan adoption across Microsoft's business applications, productivity, and AI portfolio. As part of this transition, Release Planner will retire on November 15, 2026. Microsoft is also retiring the twice-yearly release wave communication model in favor of continuous roadmap disclosure and change communications. New capabilities will be published to the AI at Work roadmap as they become committed and ready to share, providing a more current and comprehensive view of upcoming innovation. When this will happen September 2026: New Dynamics 365, Power Platform, and Dataverse roadmap items begin publishing directly to the AI at Work roadmap. Fall 2026: Existing roadmap items with Public Preview or General Availability dates on or after June 1, 2026 transition from Release Planner to the AI at Work roadmap. By November 15, 2026: Release Planner retires. The AI at Work roadmap becomes Microsoft's primary destination for public roadmap information. How this affects your organization If your organization uses Release Planner, Release Plans on Microsoft Learn, or release wave announcements for roadmap planning, you will need to transition to the AI at Work roadmap. Key changes include: Release Planner will retire on November 15, 2026. New Release Plans will no longer be published on Microsoft Learn beginning in September 2026. Existing Release Plans will remain available for historical reference. The September 2026 Release Wave 2 announcement will not occur because release wave communications are being retired. Roadmap information will be published continuously rather than grouped into twice-yearly release wave announcements. Roadmap content will be available through filtering, CSV export, RSS subscriptions, and the Release Communications MCP Server pulls roadmap information directly into your own AI tools and workflows. Personalized saved views from My Release Plans will not migrate to the AI at Work roadmap. What is not changing This transition changes how Microsoft communicates roadmap information. It does not change how products are built, released, or deployed. The following remain unchanged: Product release schedules Deployment and rollout processes Upgrade planning and support lifecycles Preview and testing programs Message Center notifications, which remain the authoritative source for tenant-specific communications Microsoft Learn as the home for product documentation and implementation guidance What you can do to prepare In September, begin using the AI at Work roadmap as your primary destination for roadmap planning. Review internal processes, documentation, bookmarks, and communications that currently reference Release Planner, Release Plans, or release wave announcements. Configure roadmap filters, RSS subscriptions, and CSV exports to support your organization's planning processes. Evaluate the Release Communications MCP Server if your organization integrates roadmap data into planning workflows or AI tools. Continue using Message Center for tenant-specific change notifications and deployment communications. Additional information The AI at Work roadmap provides a single destination for roadmap information across Microsoft business applications, productivity experiences, Copilot, agents, and AI solutions. Organizations are encouraged to familiarize themselves with the roadmap's filtering, export, RSS, and MCP capabilities before September 2026 publishing begins. -
(Updated) Microsoft Purview: Adaptive scopes add lifecycle status evaluation controls for recipients and site owners
MC1450128 · stayInformed · normal · Updated 11/14/2026 00:35
Services: Microsoft Purview
Read message
Updated November 13, 2026: We have updated the timeline. Thank you for your patience. [What and why] Microsoft Purview is introducing lifecycle status evaluation controls for adaptive scopes. This update gives administrators explicit control over whether active, inactive, and soft-deleted recipients and site owners are included in adaptive scope membership. With this change, newly created adaptive scopes will evaluate only active recipients and site owners by default. Administrators can configure adaptive scopes to include inactive and/or soft-deleted recipients and site owners when needed. This update also adds support for ISO 8601 duration values for selected date attributes in the adaptive scope advanced query builder. This message is associated with Microsoft 365 Roadmap ID 568785. [Rollout schedule] Public Preview: Beginning in December 2026 (previously mid-September) and expected to complete in December 2026 (previously early October) General Availability (Worldwide): Beginning in April 2027 (previously mid-October 2026) and expected to complete in April 2027 (previously mid-November 2026) [Impact on your organization] Who is affected Microsoft Purview administrators who create or manage adaptive scopes. Organizations that use adaptive scopes for Microsoft Purview policy targeting. Platforms and services Microsoft Purview Adaptive Scopes What will happen Existing adaptive scopes will continue to function as they do today and will not be automatically modified as part of this rollout. For newly created adaptive scopes: Active recipients and site owners will be evaluated by default. Inactive and soft-deleted recipients or site owners will not be included unless explicitly configured by an administrator. Administrators will also have the option to update existing adaptive scopes to use explicit lifecycle status evaluation criteria for recipients and site owners. Additionally, adaptive scopes will support ISO 8601 duration values for certain date-based attributes in the advanced query builder. [Action required and recommendations] No action is required before rollout. We recommend that administrators: Review current adaptive scope configurations and governance requirements. Determine whether inactive or soft-deleted recipients and site owners should be included in future adaptive scope definitions. Update adaptive scope creation processes and documentation, if applicable, to account for the new lifecycle status settings. Learn more (to be updated closer to general availability): Adaptive scopes | Microsoft Purview | Microsoft Learn [Compliance considerations] No compliance considerations have been identified. -
(Updated) Microsoft Teams: Video sharing from OneDrive in Teams events
MC1506734 · planForChange · normal · Updated 11/14/2026 00:13
Services: Microsoft Teams
Read message
Updated November 13, 2026: We have updated the content. If you are a tenant in a GCCH or DoD environment, you can safely ignore this message as you are not impacted. Thank you for your patience. [What and why] Microsoft Teams will soon support sharing video directly from OneDrive during Teams events that are optimized for scale (previously called town halls). Organizers and producers using Manage what attendees see can load videos from OneDrive and present them on stage without screen sharing a local media player or embedding videos in PowerPoint. This improvement provides smoother, higher-quality video playback for attendees and simplifies event production through built-in video playback controls. [Rollout schedule] Targeted Release (Worldwide): Rollout will begin in mid-November 2026 (previously early November) and end in early December 2026. General Availability (Worldwide, GCC): Rollout will begin in early December 2026 and is expected to complete by early December 2026. [Impact on your organization] Who is affected Teams event organizers and producers using events configured with Manage what attendees see. Platforms and services Microsoft Teams OneDrive Teams events What will happen Organizers and producers will be able to select and share videos stored in OneDrive directly within Teams events configured with Manage what attendees see and will have access to built-in controls to start and pause video playback during events. Videos can be presented on stage without screen sharing a local media player or embedding videos into a PowerPoint presentation. Attendees will experience smoother and higher-quality video playback. [Action required and recommendations] No action is required. We recommend that you: Inform Teams event organizers and producers that they can share videos directly from OneDrive in Teams events configured with Manage what attendees see. Ensure that organizers and producers store videos in OneDrive with the appropriate permissions before using them in events. Review and update internal event production guidance that recommends screen sharing locally played videos or embedding videos in PowerPoint. [Learn more] We will update this post with new documentation. [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
Microsoft SharePoint: Resources web part and Announcements capabilities expand to all sites
MC1552397 · stayInformed · normal · Updated 11/13/2026 23:49
Services: SharePoint Online
Read message
[What and why] We are expanding the Resources web part and Announcements capabilities to all SharePoint sites, making it easier for organizations to share important links and updates with employees. Site owners will have more flexibility to curate relevant resources and communicate important information. [Rollout schedule] General Availability (Worldwide): Rollout will begin in mid-November 2026 and is expected to complete by late November 2026. General Availability (GCC, DoD): Rollout will begin in mid-December 2026 and is expected to complete by late December 2026. [Impact on your organization] Who is affected SharePoint site owners and users. Platforms and services Microsoft SharePoint What will happen Resources web part: Site owners can curate important links on any SharePoint site and use audience targeting to display relevant resources to specific groups of users. Announcements: Site owners can create announcements on any SharePoint site, not just home sites. Announcements created on organizational news sites will trigger notifications. [Action required and recommendations] No admin action is required. These capabilities will roll out automatically to all customers. [Learn more] Resources web part | Microsoft Support Use the Announcements web part in the SharePoint app in Teams - SharePoint in Microsoft 365 | Microsoft Learn [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
Microsoft Viva Engage: Retirement of Teams town hall event creation
MC1552394 · planForChange · normal · Updated 11/13/2026 23:48
Services: Microsoft Viva
Action required by: 12/07/2026 08:00
Read message
[What and why] We are retiring the option to create Microsoft Teams town hall events from Viva Engage. Starting December 7, 2026, users will no longer be able to create new Teams town hall events from Engage. Organizers should use the new Events experience in Viva Engage or Microsoft Teams to create events. [Rollout schedule] December 7, 2026: Users will no longer be able to create Teams town hall events from Viva Engage. Previously scheduled events will run as planned. [Impact on your organization] Who is affected Event organizers who create Teams town hall events from Viva Engage. Communications teams responsible for organizing events. Platforms and services Microsoft Viva Engage Microsoft Teams What will happen Users will no longer be able to create new Teams town hall events from Viva Engage. Previously scheduled events will continue to run as planned. Organizers will need to use the new Events experience to create events:In Viva Engage: Create town hall, community town hall, or AMA events using Engage events. In Microsoft Teams: Create town hall events directly in Teams. [Action required and recommendations] We recommend that you: Inform event organizers and communications teams about this change before December 7, 2026. Create new and upcoming events using the new Events experience in Viva Engage or Microsoft Teams. Update internal documentation, training materials, and guidance that reference creating Teams town hall events from Viva Engage. [Learn more] Microsoft Teams events: A new unified experience makes it easier to discover, create, and manage events | Microsoft Community Hub Organize an Engage event | Microsoft Support -
Microsoft Teams: Automatic recording indicator for call queue calls on Mobile
MC1552392 · stayInformed · normal · Updated 11/13/2026 23:47
Services: Microsoft Teams
Read message
[What and Why:] When an organization automatically records its call queue calls, calling reps need to know at a glance that the call is being recorded and that this is controlled by the organization. For call queue calls that are automatically recorded by the organization, Microsoft Teams on Mobile will clearly indicate that recording and transcription have started automatically and cannot be stopped. This gives calling reps a clear and accurate picture of the call and provides a consistent experience across desktop and Mobile. [Rollout Schedule:] General Availability (Worldwide): We will begin rolling out on early December 2026 and expect to complete by mid-December 2026. [Impact on Your Organization:] Once available, calling reps who answer call queue calls that are automatically recorded by your organization will see the updated message in the recording banner in Teams on Mobile. What will change: The banner will state that recording started automatically and cannot be stopped. The previous wording, which implied the user had started the recording, will no longer appear on these calls. This change updates only the banner text. It applies to call queue calls that your organization records automatically. Other calls and recordings started manually by users are not affected. Existing consent text, the privacy link, and the AI notice in the banner stay the same. This feature does not change how recordings are started, stored, or accessed. Automatic recording for call queues is already available on desktop and is configured by admins in Teams admin center. Mobile now shows the same recording state. [Action Required/Recommendations:] No admin action is required before rollout. We recommend informing your calling reps about the updated banner, particularly those who answer queue calls on their mobile devices, so they know automatic recording is controlled by the organization and cannot be stopped by the rep. [Compliance considerations:] No compliance considerations identified. Review as appropriate for your organization. -
Microsoft Teams: Copilot in the Queues app on Mobile
MC1552391 · stayInformed · normal · Updated 11/13/2026 23:46
Services: Microsoft Teams
Read message
[What and Why:] After a customer call, calling reps or supervisor leads often need to know what was discussed. They might be following up on a missed call, picking up a conversation a colleague handled, or checking how a call went. Getting those details usually means going through the call itself, which takes time, especially on Mobile. We're introducing Copilot in the Queues app on Microsoft Teams Mobile. From shared call history, calling reps and supervisor leads can ask Copilot questions about a past call and quickly surface relevant information and insights from the conversation. This helps them get up to speed and take the next step without having to review the entire call. [Rollout Schedule:] General Availability (Worldwide): We will begin rolling out on early December 2026 and expect to complete by mid December 2026. Targeted Release (Worldwide): We will begin rolling out on late November 2026 and expect to complete by early December 2026. [Impact on Your Organization:] Once available, eligible users will be able to use Copilot on calls in shared call history in the Queues app on Mobile. Users will be able to: Open Copilot from a recorded call in shared call history. Ask questions about the call and get relevant information and insights from the conversation. Understand a customer conversation and decide on a follow-up without reviewing the full call. Copilot is available for recorded call queue calls, as it is on desktop. Users need a Teams Premium license to use the Queues app and a Microsoft 365 Copilot license to use Copilot. This feature does not change how call recordings are created, stored, or accessed. Copilot in the Queues app is already available on desktop, and Mobile brings the same capability to the phone. [Action Required/Recommendations:] No admin action is required before rollout. We recommend that you: Confirm that automatic recording is turned on for the call queues where you want users to use Copilot. Review Microsoft 365 Copilot and Teams Premium license assignments for the users who will use the feature. [Compliance considerations:] No compliance considerations identified. Review as appropriate for your organization. -
Microsoft Teams: Manage call groups on Mobile
MC1552390 · stayInformed · normal · Updated 11/13/2026 23:45
Services: Microsoft Teams
Read message
[What and Why:] Call groups let colleagues answer calls on a user's behalf, but changing one today means going to the desktop. When availability changes, for example when a backup contact is out or a new teammate needs to cover, users often notice while they are away from their desks and cannot update their call group from the phone where they take their calls. We're introducing the ability to create and manage a call group directly from Microsoft Teams on Mobile. Users can add or remove members, configure how the group should ring, and choose to forward or simultaneously ring incoming calls to their call group. This makes it easier for on the go users to manage how their calls are handled without needing to reach desktop. From Settings, users can open Calling and select Manage call group to view their current call group or create a new one. Once the call group is set up, users can forward their calls to the group or ring the group at the same time as their own devices, using the call handling options in Calling settings. [Rollout Schedule:] General Availability (Worldwide): We will begin rolling out on early December 2026 and expect to complete by mid December 2026. [Impact on Your Organization:] Once available, eligible users will see Manage call group in the Calling settings of Teams on Mobile. Users will be able to: View their current call group and its members. Create a call group if they don't have one. Add or remove members. Choose how the group rings: Everyone at once or In the order below. Reorder members when the ring order matters. Forward calls to the call group or have the group ring alongside their own devices. Changes made on Mobile apply to the same call group settings that users manage on desktop. Mobile adds a new way to manage them and does not introduce a separate call group. This feature is available to users with a Teams Phone license and uses the existing calling policy that controls call groups. If call groups are turned off for a user in their calling policy, they won't be able to use the feature on Mobile. [Action Required/Recommendations:] No admin action is required before rollout. Manage call groups on Mobile uses the same controls as the desktop experience. We recommend that you: Review the calling policy assigned to the users who should be able to manage call groups, and confirm that call groups are allowed. Confirm that those users have a Teams Phone license. Inform your users, particularly those who rely on call groups for backup coverage and often work away from their desk uses Mobile. [Compliance considerations:] No compliance considerations identified. Review as appropriate for your organization. -
Retired: Microsoft Defender for Identity classic alerts (Remote code execution attempt and pass-the-hash)
MC1552387 · planForChange · normal · Updated 11/13/2026 23:43
Services: Microsoft Defender XDR
Action required by: 11/30/2026 08:00
Read message
[What and Why:] Microsoft Defender for Identity (MDI) is retiring two classic alerts at the end of November 2026: Remote code execution attempt (RCE) and Suspected identity theft (pass-the-hash). This update aligns detection workflows with current Microsoft Defender XDR and endpoint monitoring capabilities. [Rollout Schedule:] General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out in late November 2026 and expect to complete by late November 2026. [Impact on Your Organization:] Who is affected: - Security teams using classic MDI alert workflows for RCE and pass-the-hash scenarios. Platforms/Services: - Microsoft Defender for Identity - Microsoft Defender XDR services What will happen: - The two classic alerts will no longer be available after rollout completes. - RCE activity can continue to be monitored with a custom detection rule in Advanced Hunting. - Pass-the-hash monitoring should continue through Microsoft Defender for Endpoint on onboarded devices. [Action Required/Recommendations:] Before the end of November 2026: - Create an Advanced Hunting custom detection rule for RCE scenarios using the published query. - Confirm pass-the-hash detection coverage through Defender for Endpoint on onboarded devices. - Review guidance: MDI classic alerts documentation. - Use the published query: RCE custom detection query. [Compliance considerations:] No compliance considerations identified. Review as appropriate for your organization. -
Out-of-band update released to address Windows licensing and activation errors
MC1551898 · stayInformed · normal · Updated 11/13/2026 18:08
Services: Windows
Read message
Microsoft has released a new Windows out-of-band (OOB) update today, November 13, 2026, to address an issue that affects a limited number of enterprise devices after installing the November 2026 Windows security update. Certain Windows licensing and activation operations using the Software Licensing Management Tool (SLMGR) might fail with error 0x80041008 (Invalid parameter). This primarily affects organizations using slmgr.vbs commands or automated processes to configure Key Management Service (KMS) activation, install product keys, or manage Windows licensing. Devices that are already activated remain activated. This cumulative update includes the improvements from the November 2026 Windows security update. For Windows Server 2025, Windows Server 2022, Windows Server 2019, and the Windows 10 editions listed below, the optional non-security OOB update is available only from the Microsoft Update Catalog. For Windows 11, version 23H2, the optional non-security OOB update is available from the Microsoft Update Catalog and through Windows Update. Go to Settings > Windows Update > Advanced options > Optional updates to download and install it. For complete guidance and installation instructions, see the relevant KB articles: Windows Server 2025: KB5136489 Windows Server 2022: KB5136487 Windows Server 2019 and Windows 10 Enterprise LTSC 2019: KB5136490 Windows 11, version 23H2: KB5136483 Windows 10, version 22H2 ESU and Windows 10 Enterprise LTSC 2021: KB5136493 -
60-Day Reminder: Windows 10 Enterprise LTSC 2021 will reach end of updates on January 13, 2027
MC1551897 · stayInformed · normal · Updated 11/13/2026 18:07
Services: Windows
Read message
On January 13, 2027, Windows 10 Enterprise LTSC 2021 will reach the end of mainstream support. The January 2027 Windows security update will be the last update provided during mainstream support. After that date, monthly security updates will continue only for Windows 10 Enterprise LTSC 2021 devices enrolled in Extended Security Updates (ESU). To help keep your devices protected and supported, we recommend updating to the latest Long-Term Servicing Channel release, Windows 11 Enterprise LTSC 2024. If your organization cannot complete its transition before January 13, 2027, ESU options are available for up to three years to help keep eligible devices protected while you complete your transition. Learn more at Plan for Windows 10 Enterprise LTSC 2021 end of support. For detailed lifecycle dates, see the Windows 10 Enterprise LTSC 2021 lifecycle page. For servicing and lifecycle resources, see Windows 10 release information, Lifecycle FAQ - Windows, and the Microsoft Lifecycle Policy search tool. -
60-Day Reminder: Windows Server 2016 reaches the end of extended support on January 13, 2027
MC1551896 · stayInformed · normal · Updated 11/13/2026 18:07
Services: Windows
Read message
On January 13, 2027, all editions of Windows Server 2016 will reach the end of extended support. The January 2027 Windows security update will be the last update provided during extended support. After that date, monthly security updates will continue only for Windows Server 2016 devices enrolled in Extended Security Updates (ESU). Support for Windows Server 2016 Essentials features, including Remote Web Access and related Essentials-specific functionality, also ends on January 13, 2027. Any Windows Server 2016 Essentials capability that continues to function after support ends should be treated as unsupported. To help keep your environment protected and supported, plan to upgrade to Windows Server 2025. To download a free 180-day evaluation, visit the Microsoft Evaluation Center. For detailed lifecycle dates, see the Windows Server 2016 lifecycle page. For servicing timelines and related resources, see Windows Server release information, Lifecycle FAQ - Windows Server, and the Microsoft Lifecycle Policy search tool. -
[Outlook for iOS and Android] Copilot Chat in Outlook UX improvements
MC1551148 · stayInformed · normal · Updated 11/13/2026 01:39
Services: Exchange Online
Read message
[What and Why:] Copilot Chat in Outlook on iOS and Android is getting updated! We are refreshing the Microsoft 365 Copilot Chat experience in Outlook mobile to deliver a more consistent and intuitive experience across Microsoft 365 apps, with improvements to the chat interface, suggested prompts, response presentation, and navigation between chat views - making it easier for users to interact with Copilot while staying in the context of their work in Outlook. [Rollout Schedule:] General Availability (Worldwide): We will begin rolling out on mid December 2026 and expect to complete by late January 2027. [Impact on Your Organization:] After this update, users accessing Copilot Chat in Outlook on iOS or Android will notice: Refreshed chat experience: A more consistent One Copilot design across Microsoft 365 apps, including updated suggested prompts, input box, and side navigation. Temporary Chat: Moved from the top-right corner to the (...) More options menu. Users can continue using Copilot for general conversations or within supported Outlook workflows. Existing Copilot capabilities and access controls remain unchanged. [Action Required/Recommendations:] No admin action is required. [Compliance considerations:] No compliance considerations identified. Review as appropriate for your organization. -
Microsoft Word: Retirement of legacy compatibility settings
MC1551147 · planForChange · normal · Updated 11/13/2026 01:38
Services: Microsoft 365 apps
Read message
[What and Why:] We are retiring a set of compatibility options in Microsoft Word (desktop app) for documents in Compatibility Mode. These settings help preserve how documents were laid out in older versions of Word. We are introducing this change in phases to simplify how Word handles document layout and provide a more consistent experience across platforms. Learn more. Rollout schedule: Word for Windows starting December 2026; Word for Mac starting early 2027. [Rollout Schedule:] We will begin rolling out on early December 2026 and expect to complete by late December 2026. General Availability (GCC): We will begin rolling out on late December 2026 and expect to complete by early January 2027. General Availability (GCC High): We will begin rolling out on late December 2026 and expect to complete by early January 2027. General Availability (DoD): We will begin rolling out on late December 2026 and expect to complete by early January 2027. [Impact on Your Organization:] Who is affected: Organizations with documents created or last saved in Word 2010 or earlier that use the affected legacy compatibility settings. Platforms and services: Microsoft Word. What will happen: Some legacy compatibility options will be retired. Affected documents may show layout differences, such as text reflow, changes in spacing or page count, or images and shapes moving to another page. [Action Required/Recommendations:] No action is required for the change to take effect. If exact page layout matters for your organization, consider reviewing important older documents before the change reaches your users. To preserve a copy of a document's current appearance, consider exporting it to PDF before the change. [Compliance considerations:] No compliance considerations identified. Review as appropriate for your organization. -
Prevent issues with NetApp SMB shares: Learn about new Windows Server security requirements
MC1551001 · stayInformed · normal · Updated 11/12/2026 22:55
Services: Windows
Read message
What and why: Microsoft introduced additional security requirements for LDAP authentication on Active Directory domain controllers starting with the October 13, 2026, Windows security updates. These changes require Kerberos service tickets used for LDAP authentication to match the LDAP service principal name SPNSPN registered on the target domain controller. This helps strengthen authentication security by preventing tickets intended for other services from being used to authenticate to LDAP. Rollout schedule: This change was introduced with Windows security updates released on October 13, 2026, and is included in subsequent updates. Impact on your organization: Following this security change, affected NetApp configurations might experience: Issues accessing SMB shares and disruptions to applications that depend on these shares. "Invalid credentials" errors when creating new SMB volumes or performing certain LDAP operations. Who is affected by these issues: Azure NetApp Files and NetApp ONTAP configurations that connect to Active Directory LDAP with LDAP client session security set to none. Platforms/services: Windows Server 2025, 2022, 2019, 2016, 2012 ESU and 2012 R2 ESU; Azure NetApp Files and NetApp ONTAP. Action required / recommendations: If you use affected NetApp configurations, review KB5134907 Access to NetApp SMB shares might fail after installing the October 2026 Windows security update, for full guidance. Temporary mitigation guidance is available there for affected Azure NetApp Files environments. For self-managed NetApp ONTAP environments, address the issue by configuring LDAP session security to use sign or seal. NetApp is working to provide a resolution that will allow you to install Windows security updates without disrupting access to affected Azure NetApp Files resources. Consult the NetApp Knowledge Base for the latest information. Additional information: See KB5134907 Access to NetApp SMB shares might fail after installing the October 2026 Windows security update for complete guidance Learn about Azure NetApp Files at Microsoft Learn Consult NetApp support for the guidance and information from NetApp See the NetApp Knowledge Base for information on additional resolution Compliance considerations: The change strengthens LDAP authentication requirements but can affect access to SMB shares in certain configurations. Review additional security requirements as appropriate for your organization. -
(UPDATED) Take action to prevent RD Web Access rendering failures
MC1491832 · planForChange · normal · Updated 11/12/2026 22:55
Services: Windows
Read message
Updated November 12, 2026: We are informing regarding November updates for Windows Server which address this change. What and why: The Remote Desktop Web Access (RD Web Access) experience included with Windows Server relies on Extensible Stylesheet Language Transformations (XSLT) to render its web interface. Across the industry, browsers are moving away from XSLT, with Chromium-based and other browsers disabling XSLT support in the short term. As browsers disable XSLT, the RD Web Access experience included with Windows Server will no longer render as expected. To address this, the November 2026 Windows security update for supported versions of Windows Server provides an updated RD Web Access experience. Rollout schedule: The November 2026 Windows security update was released November 10, 2026. It is available now for supported versions of Windows Server. This change is also included in subsequent updates. Impact on your organization: Organizations that have deployed the RD Web Access experience included with Windows Server are affected. After XSLT support is disabled in a browser, users who open RD Web Access with that browser might encounter a page that fails to render as expected. As a result, users might be unable to access remote resources. Action required/recommendations: Install the latest Windows security update for Windows Server to continue using the RD Web Access experience included in Windows Server. You can review details at KB5130994: RD Web Access fails to load when XSLT is disabled in Microsoft Edge or Google Chrome. If you have customizations applied, please also follow additional guidance here: RD Web Access customizations. Compliance considerations: No compliance considerations are identified. Review as appropriate for your organization. -
60-day reminder: Hardening changes for ReFS volumes on removable media
MC1550797 · planForChange · normal · Updated 11/12/2026 18:01
Services: Windows
Read message
What and why: Microsoft is making hardening changes to the Resilient File System (ReFS). The changes improve the security posture of Windows by adding visibility into unsupported external ReFS configurations and by providing controls to block affected volumes. The changes apply to all supported Windows platforms in phases to allow your organization to review audit data and address dependencies. Rollout schedule: October 2026 Windows security update (Audit phase; began October 13, 2026) January 2027 Windows security update (Enforcement phase) Impact on your organization: The changes improve the security posture of Windows but require admin action. Action required/recommendations: UPDATE: Install the applicable Windows security update released on or after October 13, 2026 on supported devices. MONITOR: Review the ReFS audit events generated for removable media. ASSESS: Identify workflows that rely on ReFS volumes in unsupported external media configurations and migrate required data or workloads to a supported storage configuration. TEST: Enable blocking in a controlled environment and confirm that required devices and applications continue to operate as expected. ENFORCE: Enable blocking when your environment is ready. If you configure no override, blocking becomes the default with the January 2027 security update. Learn more at Hardening changes for ReFS volumes on removable media. Compliance considerations: Hardening changes affect Windows security. Review as appropriate for your organization. -
Windows Office Hours: November 19, 2026
MC1550796 · stayInformed · normal · Updated 11/12/2026 18:01
Services: Windows
Read message
If you are an IT admin with questions about managing and updating Windows, we want to help. Every third Thursday of the month, we host a live chat-based event on the Tech Community called Windows Office Hours. Members of the Windows, Microsoft Intune, Windows Autopilot, Windows Autopatch, and Windows 365 engineering teams will be standing by to answer your questions. Want to attend the November 19 session of Office Hours? Add it to your calendar and select Attend on the event page to let us know you're coming. There is no video or live meeting component. Simply visit the event page, sign in to the Tech Community, and leave your questions in the Comments section. You can also bookmark https://aka.ms/Windows/OfficeHours for upcoming dates (and the ability to add this event to your calendar). We look forward to helping you. -
(Updated) Microsoft Defender for Office 365: Localized default mark and notify email template
MC1387578 · stayInformed · normal · Updated 11/12/2026 17:30
Services: Microsoft Defender XDR
Read message
Updated November 12, 2026: We have updated the timeline. Thank you for your patience. [What and Why] Microsoft Defender for Office 365 is introducing localization support for the default “Mark and notify” email template used in admin review and automated notification flows for user-reported messages. This update ensures that users receive notification emails in their preferred language based on their Outlook settings, improving clarity and understanding of review outcomes. This helps improve engagement and supports stronger security practices. This message is associated with Microsoft 365 Roadmap ID 557558. [Rollout Schedule] General Availability Worldwide: Rollout begins in June 2026 and is expected to complete by end of September 2026 (previously late July). GCC, GCC High, DoD: Rollout begins in late November 2026 (previously mid-July) and is expected to complete by end of December 2026 (previously end of October). [Impact on Your Organization] Who is affected Organizations using Microsoft Defender for Office 365 Admins and users participating in user-reported message workflows Applies only when the default notification template is used Platforms/Services Microsoft Defender for Office 365 Microsoft 365 Defender portal (web) Exchange Online What will happen Default “Mark and notify” email templates will be localized. Notifications will be delivered in the user’s preferred language based on Outlook settings. Feature is enabled by default when auto-notification is turned on. Notifications will have consistent formatting and messaging across supported languages. No changes to message verdicts or classification logic. No changes to automated investigation behavior. No changes to custom notification templates configured by admins in the user reported settings page. Default 'safe' message template will also use softer, clearer wording while continuing to advise users to exercise caution:This email doesn’t appear harmful. But you should always handle suspicious emails with caution. The safe-message template will also advise users to:Contact the sender through another channel to confirm the message’s validity. Avoid links and attachments in unsolicited emails from unfamiliar senders. Screenshot 1 - Before localization view: Screenshot 1 - Localized template view: Screenshot 2 - Default safe message: [Action Required/Recommendations] No action is required. You may consider the following: Inform users that notification emails may now appear in their preferred language. Review notification settings in Microsoft Defender: Settings > Email and collaboration > User reported settings. Update internal documentation or helpdesk guidance if this workflow is documented. Learn more: Notify users about admin submitted messages to Microsoft - Use the Submissions page to submit suspected spam, phish, URLs, legitimate email getting blocked, and email attachments to Microsoft | Microsoft Defender for Office 365 | Microsoft Defender | Microsoft Learn [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
(Updated) Microsoft Teams: Enhanced channel meeting experience
MC1509796 · stayInformed · normal · Updated 11/12/2026 17:25
Services: Microsoft Teams
Read message
Updated November 12, 2026: We have updated the timeline. Thank you for your patience. [What and Why:] Microsoft Teams is introducing enhancements for channel meetings to make it easier to schedule meetings in the right context and help teams discover relevant meetings across their channels. Users will be able to create channel meetings directly from the Teams calendar and create and manage channel meetings from classic Outlook for Windows. Channel members will be able to more easily discover meetings associated with their channels, helping teams stay informed about upcoming discussions and participate in relevant conversations. Administrative assistants and delegates will also be able to schedule channel meetings on behalf of others while keeping meetings connected to the appropriate team and channel. [Rollout Schedule:] Public Preview (Worldwide): We will begin rolling out in mid-November 2026 (previously early November) and expect to complete by late November 2026. General Availability (Worldwide): We will begin rolling out in late January 2027 (previously mid-December 2026) and expect to complete by late January 2027. General Availability (GCC): We will begin rolling out in mid-December 2026 and expect to complete by late July 2027. General Availability (GCC High): We will begin rolling out in mid-December 2026 and expect to complete by late August 2027. General Availability (DoD): We will begin rolling out in mid-December 2026 and expect to complete by late September 2027. [Impact on Your Organization:] Users will have additional ways to create, manage, and discover channel meetings in Teams and classic Outlook for Windows. This can help meetings stay connected to the relevant team and channel context. [Action Required/Recommendations:] No admin action is required. You may want to inform users, meeting organizers, administrative assistants, and delegates about the enhanced channel meeting experience. [Compliance considerations:] No compliance considerations identified. Review as appropriate for your organization. -
(Updated) Microsoft Teams: Facilitator proactively detects and resolves knowledge gaps in meetings
MC1409304 · planForChange · normal · Updated 11/12/2026 17:21
Services: Microsoft Teams
Read message
Updated November 12, 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 February 2027 (previously early December) and expected to complete mid-February 2027 (previously mid-December) General Availability (Worldwide): Beginning mid-February 2027 (previously mid-December) and expected to complete early March 2027 (previously mid-January) [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] QuestionAnswer Does the change alter how existing customer data is processed, stored, or accessed (for example, meeting conversations)?Yes. The feature processes meeting conversations in real time to detect knowledge gaps and generate responses. Does the change introduce or significantly modify AI or machine learning capabilities that interact with customer data?Yes. Facilitator uses AI to interpret meeting content and generate contextual responses during meetings. Does the change provide end users with a new way of interacting with generative AI?Yes. Users receive proactive, AI-generated responses within the Teams meeting chat without needing to prompt the system. Does the change include an admin control, and can it be controlled through configuration settings?Yes. The feature depends on the Copilot web search setting, which admins can enable or disable to control functionality. Does the change allow a user to enable or disable the feature themselves?Yes. Users can stop the behavior by removing Facilitator from the meeting. -
Microsoft 365 Copilot: Copilot Workspaces is replacing standalone agent selection with agentic chat
MC1550540 · planForChange · normal · Updated 11/12/2026 16:19
Services: Microsoft 365 apps
Read message
[What and why] Microsoft 365 Copilot Workspaces (formerly Copilot Notebooks) is moving to an agentic chat experience. As part of this change, Researcher, Analyst, and Designer will no longer be available as standalone agent options within Copilot Workspaces. Instead of selecting or switching between agents, users can describe what they need in plain language. Copilot will automatically apply the appropriate research, analysis, or design skills based on the request and the workspace content. This change simplifies the user experience while preserving existing capabilities. Researcher, Analyst, and Designer will remain available as separate agents in the Microsoft 365 Copilot app for users who prefer working with a specific agent. [Rollout schedule] Frontier preview: Rollout is planned to begin in December 2026. The completion date has not yet been determined. Rollout dates for general availability are still being finalized. We will provide additional information when available. [Impact on your organization] Who is affected Users of Microsoft 365 Copilot Workspaces who have access to the Frontier preview Platforms and services Microsoft 365 Copilot Workspaces (formerly Copilot Notebooks) Microsoft 365 Copilot app What will happen Standalone agent selection: Researcher, Analyst, and Designer will no longer appear as separate agent options within Copilot Workspaces. Agentic chat: Users can describe research, analysis, and design tasks in natural language. Copilot will automatically apply the appropriate skills based on the request and workspace content. No loss of capabilities: Research, analysis, and design capabilities will remain available within Copilot Workspaces. Simplified workflow: Users will no longer need to select or switch between agents when performing different tasks. Continued access to individual agents: Researcher, Analyst, and Designer will remain available as separate agents in the Microsoft 365 Copilot app. Default behavior: This change will apply automatically when it rolls out to your organization. [Action required and recommendations] No admin action is required. We recommend that you: Inform users that Researcher, Analyst, and Designer will no longer appear as separate agent options in Copilot Workspaces. Explain that users can describe their tasks directly in chat, and Copilot will apply the appropriate capabilities. Update internal training and support materials that instruct users to select specific agents within Copilot Workspaces. Direct users who prefer working with individual agents to Researcher, Analyst, and Designer in the Microsoft 365 Copilot app. Monitor Message center for additional rollout information. [Compliance considerations] This change introduces an agentic chat experience in Copilot Workspaces, allowing users to interact with research, analysis, and design capabilities through natural language rather than selecting individual agents. Organizations should review this change as appropriate for their compliance requirements. -
Microsoft Teams: Updated recording and transcript access setting behavior for town halls and webinars
MC1550542 · preventOrFixIssue · normal · Updated 11/12/2026 16:19
Services: Microsoft Teams
Read message
[What and why] We are updating how the Who has access to the recording or transcript option appears for Microsoft Teams Events scheduling through the Events App including town halls and webinars. Currently, when AllowCloudRecording is set to false, this option does not appear for these events. After this change, the option will appear only when the applicable RecordingForTownhall or RecordingForWebinar setting in CsTeamsEventsPolicy is enabled. [Rollout schedule] General Availability (Worldwide, GCC, GCC High, DoD): Beginning in early-November 2026 and expected to complete by mid-November 2026 [Impact on your organization] Who is affected Microsoft Teams organizers of Events created via the Events App including town halls and webinars Platforms and services Microsoft TeamsEvents created via the Events App including town halls and webinars What will happen The Who has access to the recording or transcript option will be based on the applicable RecordingForTownhall or RecordingForWebinar setting. It will no longer be based on the AllowCloudRecording setting. [Action required and recommendations] No action is required to enable this change. We recommend updating your internal documentation to reflect this change. [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
(Updated) M365 Copilot: Tell Copilot what you need directly from the Copilot button in Word, Excel, and PowerPoint
MC1470885 · planForChange · normal · Updated 11/11/2026 21:51
Services: Microsoft 365 apps, Microsoft 365 Copilot Chat
Read message
Updated November 11, 2026: We have updated the content. Thank you for your patience. [What and Why:] Microsoft is making Copilot more accessible within Word, Excel, and PowerPoint by adding a new prompt input directly to the Copilot button and providing contextual prompt experiences when users select content. This update helps users engage with Microsoft 365 Copilot without leaving their workflow, enabling faster content creation, editing, and task completion. This change supports personal and team productivity by bringing Copilot assistance directly into the document experience. [Rollout Schedule:] General Availability (Worldwide): Rollout begins September 2026 and is expected to complete by the end of December 2026. Available in Word, Excel, and PowerPoint on Windows desktop, macOS, and web. Rollout may occur on different platforms at different times. [Impact on Your Organization:] Who is affected: Microsoft 365 users eligible for Microsoft 365 Copilot using Word, Excel, or PowerPoint on Windows desktop, macOS, or web. Platforms/Services: Microsoft 365 Copilot Word Excel PowerPoint Windows desktop macOS desktop Web What will happen: Users will see a new button and prompt in the top right (by default). Users can type or dictate prompts without opening the Copilot pane. Users can reference Microsoft 365 content directly from the prompt input experience. When content is selected in Word or PowerPoint, a contextual Copilot input will appear. Suggested actions such as Rewrite and Shorten will be shown when appropriate. Windows shortcut: Alt + C. Mac shortcut: Command + Control + I. The feature is enabled by default for eligible users. Existing Copilot administration controls continue to apply. No separate admin control is available for the prompt input experience. [Action Required / Recommendations:] No admin action is required. Update user training and adoption materials. Update help desk documentation. Review the Pin Microsoft 365 Copilot Chat setting. Communicate the change to end users. Review Manage Microsoft 365 Copilot Chat documentation. Review Pin Microsoft 365 Copilot Chat in Microsoft 365 apps documentation. Review The Copilot Dynamic Action Button in Word, Excel, and PowerPoint documentation. [Compliance Considerations:] New generative AI interaction entry points are introduced. The update expands how users invoke existing Copilot capabilities. Existing admin controls remain available through the Pin Microsoft 365 Copilot Chat setting. -
(Updated) Microsoft Windows: Updates to address compromised eMudhra certificate authority keys
MC1529467 · planForChange · normal · Updated 11/11/2026 18:41
Services: Microsoft 365 suite
Read message
Updated November 11, 2026: On November 16, 2026, an update will be released for Microsoft Edge and WebView2, delivered via the PKI Metadata component, which will fully remove default trust for the remaining roots (emSign Root CA - G1, emSign Root CA - C1, emSign ECC Root CA, and emSign Root TLS CA - G1). Devices check for PKI Metadata updates every 10 hours and shortly after each new app launch. For more information, see Microsoft Response to eMudhra Certificate Authority Key Compromise. [What and why] Microsoft is responding to an issue involving eight eMudhra intermediate certificate authority (CA) private keys, six associated with TLS and two with code signing. Because these keys could be recovered, they could potentially be used to create certificates or sign content that appeared to come from a trusted CA. The issue arose in eMudhra's certificate hierarchy and was not a compromise of Microsoft systems. Microsoft is updating certificate trust to block affected certificate authorities and remove certificates associated with the affected hierarchies. [Rollout schedule] General Availability (Worldwide, GCC, GCC High, DoD): Beginning in late October 2026 and expected to complete by late October 2026 [Impact on your organization] Who is affected Organizations using Windows, Microsoft Edge, or WebView2, particularly organizations with certificates that chain to one of the eight certificates being removed Organizations managing disconnected Windows devices or disconnected Azure devices may need to take additional action Platforms and services Windows Microsoft Edge WebView2 Azure virtual machines What will happen Microsoft has published an update to the Windows Disallowed Certificate Trust List to block the affected certificate authorities. Microsoft has deployed a separate CRLSet update for Microsoft Edge and WebView2 to block affected TLS certificates signed by the affected certificate authorities. The Microsoft Edge and WebView2 update is delivered automatically through the component update mechanism. Customers do not need to install a new browser version. Microsoft has released updates to Windows and Microsoft Edge to remove certificates associated with the affected hierarchies from their trust lists. After these updates reach a device, the affected certificates will no longer be trusted by default through the respective trust lists. [Action required and recommendations] Keep updates flowing. Allow automatic Windows certificate trust updates and Microsoft Edge component updates to reach your devices. Check disconnected Windows devices. If you manage Windows devices that do not receive automatic updates, make sure your update process delivers the updated Disallowed Certificate Trust List and upcoming trust-list changes. See the Microsoft Learn guidance in Learn more for information about distributing certificate trust lists in disconnected environments. Review disconnected Azure devices. Review disconnected Azure devices running on Virtual Machine Scale Sets (VMSS) or single-instance VMs. Updated images are available in Azure Marketplace, and customers can deploy them to protect against this vulnerability. Replace dependent certificates. If any of your certificates chain to one of the seven certificates being removed, identify those dependencies and obtain replacement certificates or an alternative trusted chain before the changes reach your devices. Learn more Microsoft’s response to compromised eMudhra certificate authority keys Configure trusted roots and disallowed certificates in Windows | Microsoft Learn [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
(Updated) 'Add explainer video' Skill in PPT Copilot
MC1546430 · stayInformed · normal · Updated 11/11/2026 18:37
Services: Microsoft 365 apps
Read message
Updated November 11, 2026: Rollout is currently paused. We will communicate via Message center when we are ready to proceed. We apologize for any inconvenience. [What and Why:] Use the "Add explainer video" skill in Copilot for PowerPoint. This is a built-in skill rolling out as an experimental skill to Frontier users. Available on desktop, Mac, and web. [Rollout Schedule:] Frontier/Insider (Worldwide): We will communicate via Message center when we are ready to proceed. [Impact on Your Organization:] Ability to convert a static slide into an animated explainer video. [Action Required/Recommendations:] No admin action is required. [Compliance considerations:] No compliance considerations identified. Review as appropriate for your organization. -
NTLM signing security improvements in Windows
MC1549242 · stayInformed · normal · Updated 11/11/2026 18:03
Services: Windows
Read message
What and why: New NTLM signing security improvements address CVE-2026-118737. Starting November 2026, Windows updates enable clients to offer NTLM message signing by default for non-anonymous connections. This change helps reduce exposure to NTLM relay attacks and provides auditing to identify connections that aren’t using signing. To learn more and prepare for the next phase coming in May of 2027, see NTLM signing security improvements in Windows. Rollout schedule: Phase 1 (November 2026): Windows client devices begin offering NTLM signing on all connections by default. Servers accept both signed and unsigned clients. Auditing events identify clients not using signing. Phase 2 (May 2027): Windows servers begin requiring NTLM signing by default. Clients that do not offer signing will be rejected by secure servers. Impact on your organization: These security improvements address the CVE-2026-118737 vulnerability. All supported Windows Server versions are capable of NTLM signing. This rollout simply helps ensure that signing is negotiated and eventually required by default. By May 2027, clients that don’t offer signing will be rejected by secure servers. Action required/recommendations: Install the November 2026 Windows updates or later to reduce exposure to NTLM relay attacks. Audit to identify connections that aren’t using signing. Follow auditing and remediation instructions in NTLM signing security improvements in Windows. Require NTLM signing before it’s enabled by default in May 2027. Compliance considerations: Consider enforcing signing ahead of May 2027, once auditing confirms readiness, reducing exposure to NTLM relay attacks. Review as appropriate for your organization. -
Updates available for Microsoft 365 Apps for all channels
MC1548054 · stayInformed · normal · Updated 11/11/2026 01:00
Services: Microsoft 365 apps
Read message
We've released updates to the following update channels for Microsoft 365 Apps: Current Channel Monthly Enterprise Channel Semi-Annual Enterprise Channel [When this will happen:] We'll be gradually rolling out these updates of Microsoft 365 Apps to users on those update channels starting November 10th, 2026 (PST). [How this will affect your organization:] If your Microsoft 365 Apps clients are configured to automatically update from the Office Content Delivery Network (CDN), then no action is required. If you manage updates directly you can now download these latest updates and begin deployment. [What you need to do to prepare:] To get more details about these updates view the following release notes: Current Channel Monthly Enterprise Channel Semi-Annual Enterprise Channel -
(Updated) Microsoft Outlook: Update to default blocked file types in OwaMailboxPolicy
MC1488841 · planForChange · normal · Updated 11/10/2026 22:16
Services: Exchange Online
Read message
Updated November 10, 2026: We have updated the timeline. Thank you for your patience. [What and why] To enhance security in Outlook on the web and new Outlook for Windows, we are updating the default list of blocked file types in OwaMailboxPolicy. As part of this update, the .msix and .msixbundle file types will be added to the BlockedFileTypes list in the default OWA Mailbox policy and any custom policies created in your tenant. Most organizations are not expected to be affected by this update because these file types are infrequently used. This update is part of our ongoing efforts to strengthen security and help protect organizations from potentially unsafe file attachments. [Rollout schedule] General Availability (Worldwide, GCC, GCC High, DoD): Rollout begins in early December 2026 (previously early November) and is expected to complete by mid-December 2026 (previously mid-November). [Impact on your organization] Who is affected Exchange Online administrators who manage OWA mailbox policies Users who send or receive .msix or .msixbundle attachments in Outlook on the web or new Outlook for Windows Platforms and services Outlook for the web New Outlook for Windows Exchange Online What will happen The .msix and .msixbundle file types will be added to the BlockedFileTypes list in all OWA Mailbox policies in your organization, including the default policy and any custom policies created in your tenant. Users who send or receive .msix or .msixbundle attachments in Outlook on the web or new Outlook for Windows will no longer be able to open or download them. [Action required and recommendations] No action is required if your organization does not rely on the .msix or .msixbundle file types. If your organization relies on these file types, we recommend that you add them to the AllowedFileTypes property of your users' OwaMailboxPolicy objects prior to rollout. [Learn more] Blocked attachments in Outlook | Microsoft Support Set-OwaMailboxPolicy -AllowedFileTypes | Microsoft Learn Set-OwaMailboxPolicy -BlockedFileTypes | Microsoft Learn [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
(Updated) Office in Copilot brings the full power of Office into the Microsoft Copilot app
MC1530611 · stayInformed · normal · Updated 11/10/2026 19:22
Services: Microsoft 365 Copilot Chat
Read message
Updated November 10, 2026: We have updated the timeline. Thank you for your patience. [What and Why:] Now users have the full power of Office in Microsoft Copilot app, so users can create, edit and collaborate on Word, Excel and PowerPoint files, without leaving the app. [Rollout Schedule:] General Availability (Worldwide): We have begun rolling out and expect to complete by mid-November 2026. Deferred release will start early December 2026 [Impact on Your Organization:] Now with the full value of Office in Copilot, Word, Excel, and PowerPoint is brought in directly into the Copilot experience, allowing users to create, review, edit, and collaborate on Office files without leaving their flow of work. This reduces context switching and makes it easier to move from an idea or conversation to a finished, shareable Office artifact. [Action Required/Recommendations:] No admin action is required. Admins may want to inform users about the new experience and review their existing Microsoft 365 Copilot configuration and policies. [Compliance considerations:] QuestionAnswer Does the change alter how existing customer data is processed, stored, or accessed?Yes. Users can now access and edit Office file content through the Copilot experience, with changes synced back to the regular Office apps. Does the change introduce or significantly modify AI/ML or agent capabilities that interact with or provide access to customer data?Yes. Copilot gains expanded capability to read and edit Office document content as part of this feature. Does the change provide end users any new way of interacting with generative AI?Yes. Users can create and edit Word, Excel, and PowerPoint content directly within the Copilot app. Does the change include an admin control and can it be controlled through Entra ID group membership?Yes. This feature is subject to existing Microsoft 365 Copilot configuration and policies, which admins can manage via Entra ID group-based assignment. -
Windows 11, version 23H2 Enterprise and Education editions have reached end of updates
MC1547649 · stayInformed · normal · Updated 11/10/2026 18:32
Services: Windows
Read message
Today, November 10, 2026, Windows 11, version 23H2 Enterprise and Education editions have reached end of updates. The November 2026 Windows security update is the last update available for these editions. After this date, devices running these editions will no longer receive monthly security updates containing protections from the latest security threats. We recommend updating eligible devices running Windows 11, version 23H2 Enterprise and Education editions to Windows 11, version 26H2 to continue receiving monthly security and quality updates. To check whether an update is available for your eligible device, select Settings > Windows Update, then select Check for updates. If the update is available for your device, select Download and install. For more information about product lifecycle dates, see Windows 11 release information and Lifecycle FAQ - Windows. -
The November 2026 Windows security update is now available
MC1547648 · stayInformed · normal · Updated 11/10/2026 18:32
Services: Windows
Read message
The November 2026 security update is now available for all supported versions of Windows. We recommend that you install these updates promptly. For more information about the contents of this update, see the release notes, which are accessible from the Windows 11 update history page. To learn more about the different types of monthly quality updates, see Understanding Windows monthly updates. Highlights for the Windows 11, version 26H2 update: This security update includes improvements that were part of update KB5127648 (released October 13, 2026). This update provides security improvements to help protect Windows devices against the latest threats. Secure Boot certificate deployment expands to more eligible devices through additional high-confidence device targeting data. This update fixes an issue that prevented some USB Audio 1.0 devices from starting and displayed error code 10 in Device Manager. Short on time? Watch the Windows 11 release notes video for this month’s tips. For instructions on how to install this update, see the KB article for your operating system listed below: Windows 11, versions 26H2, 25H2, and 24H2: KB5132061 Windows 11, version 26H1: KB5132059 Windows 11, version 23H2: KB5131087 Windows 11 Enterprise LTSC 2024: Hotpatch KB5132043 Windows 10, versions 22H2 and 21H2: KB5131096 Windows 10 Enterprise LTSC 2019 and Windows Server 2019: KB5131085 Windows Server 2016: KB5131291 Windows Server 2025: KB5131080 Windows Server 2025 Datacenter: Azure Edition: Hotpatch KB5131077 Windows Server 2022: KB5131090 Windows Server 2022 Datacenter: Azure Edition: Baseline KB5131090 Note: As part of the November 2026 Windows security release, standalone security updates are available for devices enrolled in hotpatch updates. These updates address security vulnerabilities in Windows PowerShell involving web requests, PowerShell workflows, and the Desired State Configuration (DSC) Archive Resource. They are offered after the November 2026 hotpatch update is installed. A restart might be required after installing these updates if any of the updated files are in use. For more information, see the applicable KB article: Windows 11, versions 26H2, 25H2, and 24H2: KB5135385 Windows Server 2025: KB5135386 IMPORTANT: Because of minimal operations during the Western holidays and the upcoming new year, there will be no December 2026 non-security preview update in the second part of the month. Normal monthly servicing for both security and non-security preview updates will resume in January 2027. -
(Updated) Microsoft Teams: Users can temporarily pause all notifications
MC1465768 · stayInformed · normal · Updated 11/10/2026 17:39
Services: Microsoft Teams
Read message
Updated November 10, 2026: We have updated the timeline. Thank you for your patience. [What and Why:] Microsoft Teams will introduce a new capability that allows users to temporarily pause notifications for a selected period of time. This feature gives users greater control over interruptions, helps reduce notification overload, and enables focused work, meetings, and other activities without requiring changes to existing notification settings. [Rollout Schedule:] Targeted Release (Worldwide): Rollout begins in mid-September 2026 and is expected to complete by early October 2026. General Availability (Worldwide, GCC, GCC High, DoD): Rollout begins in early October 2026 and is expected to complete by end November 2026 (previously late October). [Impact on Your Organization:] Who is affected: All Microsoft Teams users. Platforms: Microsoft Teams desktop, web, and mobile. What will happen: Users will be able to temporarily pause Teams notifications for a selected duration. The feature helps users focus on important work and meetings without modifying their existing notification settings. Users can access this capability from the profile menu in the upper-right corner of the Teams application. Once the selected pause period ends, notifications will automatically resume using the user's existing notification preferences. [Action Required/Recommendations:] No admin action is required. Consider informing users about this new capability so they can take advantage of improved notification management and reduced distractions while maintaining their existing notification preferences. [Compliance Considerations:] No compliance considerations identified, review as appropriate for your organization. -
(Updated) Microsoft Teams: Malicious QR code detection in messages
MC1526651 · stayInformed · normal · Updated 11/10/2026 17:37
Services: Microsoft Teams
Read message
Updated November 10, 2026: We have updated the timeline. Thank you for your patience. [What and why] Microsoft Teams is extending malicious URL protection to provide near-real-time detection of malicious destinations embedded in QR codes shared in messages. Teams will analyze QR code destinations to identify potential phishing and fraud threats and display an additional warning when malicious content is detected. [Rollout schedule] General Availability (Worldwide): Beginning in mid-November 2026 (previously early November) and expected to complete by late November 2026 (previously mid-November) [Impact on your organization] Who is affected Users who use Microsoft Teams messaging Platforms and services Microsoft Teams chats, meeting chats, and channels What will happen Teams will decode and evaluate QR code destinations in inline images shared in 1:1 chats, group chats, meeting chats, and channels. Detection applies to internal and external communications. Images containing QR codes from external senders are already blurred by default. When Teams identifies a malicious QR code, users will also see the warning, “This message contains a link that might be harmful,” and a “Learn about file and link safety” link. QR code images from internal senders are not blurred by default. The same warning will appear when Teams detects a malicious QR code. For users on Teams mobile in China, QR code images are blurred by default regardless of whether the sender is internal or external, and any messages containing malicious QR code will be blocked. Malicious QR code detection is managed by the existing Malicious URL protection setting. The setting is enabled by default. Organizations with Malicious URL protection enabled will automatically receive malicious QR code detection as the feature rolls out. No separate configuration is available or required for malicious QR code detection. [Action required and recommendations] No admin action is required. Admins can review or change the existing Malicious URL protection setting in Teams admin center > Settings and policies > Messaging Safety. We recommend that you: Inform users and help desk staff about the additional warning for detected malicious QR codes. Clarify that QR code blurring is a separate precautionary experience and does not mean that Teams has identified a QR code as malicious. Review internal documentation about Teams messaging security and update it if necessary. Learn more (Both to be updated closer to rollout.) Make sure chats, links, and files are secure in Microsoft Teams | Microsoft Support Malicious URL protection in Microsoft Teams - Microsoft Teams | Microsoft Learn [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
(Updated) Microsoft Teams: Invite attendees to register
MC1537353 · stayInformed · normal · Updated 11/10/2026 17:35
Services: Microsoft Teams
Read message
Updated November 10, 2026: We have updated the timeline. Thank you for your patience. [What and Why:] Microsoft Teams is expanding the Invite to register experience for Teams events with registration enabled. Organizers can select people to receive an email invitation with a link to register for the event. [Rollout Schedule:] General Availability (Worldwide, GCC): We will begin rolling out in late November 2026 (previously mid-November) and expect to complete by late November 2026. [Impact on Your Organization:] Invite to register will be available across event access types, including public, organization-wide, and events limited to specific people and groups. For public and organization-wide events, sending an invitation does not change who is eligible to register. For events limited to specific people and groups, the selected audience continues to determine registration eligibility. This update gives organizers a consistent way to proactively invite their intended audience to register for an event. [Action Required/Recommendations:] No special preparation is required. However, if your tenant does not have a custom domain configured for M365 notifications, this capability will be restricted due to spam concerns. Admins should configure their custom domain for M365 notifications to allow full use of this feature. [Compliance considerations:] No compliance considerations identified. Review as appropriate for your organization. -
(Updated) Microsoft Teams: Automatic recording and transcription options align with admin policies
MC1508234 · stayInformed · normal · Updated 11/10/2026 17:33
Services: Microsoft Teams
Read message
Updated November 10, 2026: We have updated the timeline. Thank you for your patience. [What and why] Microsoft Teams is updating the Record and transcribe automatically setting in Meeting options, so meeting organizers see only the automatic recording and transcription options permitted by their assigned Teams meeting policies. This change reduces confusion, improves policy compliance, and helps ensure organizers cannot select options that are unavailable based on organizational settings. As part of this update, Teams will introduce a new Record only option that automatically starts meeting recording without starting transcription. [Rollout schedule] Targeted Release: Beginning in mid-November 2026 (previously early November) and expected to complete by end of November 2026 (previously mid-November) General Availability (Worldwide): Beginning in early December 2026 and expected to complete by mid-December 2026 [Impact on your organization] Who is affected Teams administrators who manage meeting recording and transcription policies Meeting organizers who configure automatic recording or transcription settings in Meeting options Platforms and services Teams desktop, web, and mobile clients that support Meeting Options. What will happen Meeting organizers will only see automatic recording and transcription options allowed by their effective Teams meeting policy. Policy evaluation respects policies assigned directly to a user, inherited through group assignment, or applied through the global policy. A new Record only option will be available when recording is permitted by policy. The available automatic options for each policy combination are shown below: Recording policyTranscription policyAutomatic options available in Meeting Options AllowedAllowedRecord and transcribe; Transcribe only; Record only; Off AllowedBlockedRecord only; Off BlockedAllowedTranscribe only; Off BlockedBlockedThe automatic setting is not shown [Action required and recommendations] No admin action is required; the feature is enabled automatically as part of the service update. We recommend that: Inform meeting organizers about the new Record only option. Communicate that available automatic recording and transcription options are now determined by the organizer's assigned Teams meeting policies. Review recording and transcription policies if you want to understand which options organizers in your organization will see. [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
Action may be required: Claude models in Copilot are coming into the EU Data Boundary and will be enabled by default
MC1546438 · planForChange · normal · Updated 11/10/2026 01:07
Services: Microsoft 365 Copilot Chat
Action required by: 12/09/2026 08:00
Read message
[What and why:] Claude models from Anthropic in Microsoft Copilot are coming into the EU Data Boundary. Starting in early December 2026, eligible organizations in the European Union (EU) and the European Free Trade Association (EFTA) will be able to use Claude models in Copilot with processing within the EU Data Boundary. Claude models are currently disabled by default for tenants in the EU and EFTA. On December 9, 2026, Microsoft will enable Claude models for tenants that haven't made a selection for Anthropic under AI providers operating as Microsoft subprocessors in the Microsoft 365 admin center. With Claude models coming into the EU Data Boundary, we’re also simplifying the controls we provide admins by retiring the option to allow Claude models only in Copilot in Microsoft 365 apps. Tenants using this option will move to All users on December 9. Other selections you've already made will be respected. If you're already using Claude models, no action is needed, and processing moves into the EU Data Boundary automatically once available. If you don't want Claude models enabled by default, an admin can opt out before December 9, 2026. After December 9, admins can also disable the use of Claude models at any time. Claude models in Copilot are covered by Microsoft's enterprise data protection, and the Microsoft Product Terms and Data Protection Addendum apply, except as otherwise disclosed in Microsoft Learn documentation. [Rollout schedule:] Early December 2026: Processing for Claude models in Copilot moves into the EU Data Boundary. December 9, 2026: Microsoft enables Claude models for tenants that haven't made a selection, and the option to allow them only in Copilot in Microsoft 365 apps will be retired. Admins can disable Claude models or limit access at any time. [Impact on your organization:] Who is affected: Admins of EU Data Boundary-eligible tenants in the EU and EFTA who manage access to AI models in Microsoft Copilot. Users in these tenants who will have access to Claude models across Microsoft Copilot experiences and in Microsoft Copilot Studio. What will happen: If you haven't made a selection: Claude models will be enabled for all users on December 9, 2026. If you've already enabled Claude models: Your user and group assignments don't change, and processing for these models moves into the EU Data Boundary automatically once available. If you've allowed Claude models only in Copilot in Microsoft 365 apps: On December 9, 2026, this option will be retired and your selection will move to All users. To turn Claude models off or limit access instead, select No users or Specific users and groups before that date. If you've disabled Claude models: Your selection will be respected. Until early December 2026, Claude models aren’t covered by the EU Data Boundary processing commitment. Anthropic models with Data Retention are governed by a separate setting and aren’t part of this change. [Action required / Recommendations:] No action is required if you haven't made a selection and want Claude models enabled for all users on December 9, 2026. To opt out or limit access: Before December 9, 2026, go to the Microsoft 365 admin center > Copilot > Settings > View all > AI providers operating as Microsoft subprocessors > Anthropic. Select No users to opt out, or Specific users and groups to limit access to the people you choose. Then select Save. You need the AI Administrator or Global Administrator role to change this setting. Let your helpdesk and compliance teams know about this change. [Compliance considerations:] Admin controlsTenants that haven't made an Anthropic selection, or that allow Claude models only in Copilot in Microsoft 365 apps, move to All users, and that option is retired. Other selections (All users, No users, or Specific users and groups) are respected. Data processingAnthropic continues to operate as a Microsoft subprocessor. For eligible tenants, processing for Claude models in Copilot moves into the EU Data Boundary once available. AI/ML capabilitiesClaude models become available across Copilot experiences for users in tenants that haven't made a selection or that allow them only in Copilot in Microsoft 365 apps. [Learn more:] Bringing Claude models in Microsoft Copilot into the EU Data Boundary Claude models from Anthropic in Microsoft Online Services EU Data Boundary Overview of AI subprocessors -
Microsoft Defender for Office 365: Updated recipient inclusion logic for threat protection policies
MC1546447 · stayInformed · normal · Updated 11/10/2026 00:50
Services: Microsoft Defender XDR
Read message
[What and why] Microsoft Defender for Office 365 is updating how recipient inclusion conditions are evaluated when targeting threat protection policies. When a policy includes multiple recipient condition types, such as users, groups, and domains, policies will use Match any (OR) logic instead of Match all (AND) logic. This change simplifies policy targeting and reduces the risk that intended recipients are excluded because they do not satisfy every configured recipient condition. [Rollout schedule] General Availability (Worldwide): We will begin rolling out in early December 2026 and expect to complete by early December 2026. [Impact on your organization] Who is affected Administrators who create or modify Microsoft Defender for Office 365 threat protection policies that use recipient inclusion conditions Platforms and services Microsoft Defender for Office 365, including policy changes made through the Microsoft Defender portal or Exchange Online PowerShell What will happen New policies created after rollout will use Match any (OR) logic by default. Existing policies will not be automatically converted during rollout. When an administrator modifies an existing policy, that policy will transition to the new recipient inclusion logic. The transition from Match all (AND) to Match any (OR) can expand the population to which the policy applies. The Microsoft Defender portal will provide warning and confirmation messaging during the transition. For changes made through Exchange Online PowerShell, administrators will receive a warning when importing the PowerShell module. Existing policies remain unchanged until they are modified, allowing organizations to transition progressively rather than through an automatic tenant-wide conversion. [Action required and recommendations] Before modifying an existing policy that uses recipient inclusion conditions: Review the configured users, groups, and domains. Review the resulting policy scope because transitioning from Match all (AND) to Match any (OR) can expand the population to which the policy applies. Review the warning and confirmation messaging provided in the Microsoft Defender portal or Exchange Online PowerShell before completing the change. No action is required for existing policies that you do not modify. [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
Power BI retiring standalone Copilot experiences (preview)
MC1546429 · planForChange · normal · Updated 11/10/2026 00:22
Services: Power BI
Action required by: 12/08/2026 08:00
Read message
[What and Why:] Power BI will retire the preview standalone Copilot experience in early January 2027. This includes access from the Power BI Home page, Power BI mobile apps, Microsoft Teams, and app-scoped Copilot. Microsoft has announced Microsoft 365 Copilot in Power BI and Microsoft Fabric (preview), which brings Microsoft 365 Copilot into these products. Beginning December 8, 2026, Microsoft 365 Copilot in Power BI will be enabled by default. [Rollout Schedule:] Microsoft 365 Copilot default-on (Worldwide): December 8, 2026. Retirement (Worldwide): Standalone Copilot will be retired in mid-January 2027. [Impact on Your Organization:] Standalone Copilot will no longer be available from the Power BI Home page, Power BI mobile apps, Microsoft Teams, or within Power BI workspace apps. The associated navigation entry points and settings will be removed, including the standalone Copilot tenant setting and the "Show Copilot in app navigation" setting. Beginning December 8, 2026, Microsoft 365 Copilot in Power BI will be enabled by default, providing an alternative for continued AI-assisted analysis of Power BI data. [Action Required/Recommendations:] Notify affected people in your organization about the retirement. Review Microsoft 365 Copilot in Power BI and Microsoft Fabric (preview), including its availability and requirements for your organization, ahead of the December 8 default-on date, and plan the transition from standalone Copilot as appropriate. [Compliance considerations:] No compliance considerations identified. Review as appropriate for your organization. -
Retirement of Viva Insights (personal insights) and Viva Learning usage reports
MC1546411 · planForChange · normal · Updated 11/10/2026 00:04
Services: Microsoft 365 suite
Read message
[What and Why:] The Viva Learning usage report and The Viva Insights personal insights active-user trend chart will be retired from the Microsoft 365 admin center. For Viva Learning, admins can continue to access usage metrics in the Viva Learning app directly. [Rollout Schedule:] General Availability (Worldwide): We will begin rolling out on early November 2026 and expect to complete by mid-November 2026. [Impact on Your Organization:] Who is affected: Microsoft 365 tenant administrators Organizations using Microsoft Viva Insights, or Viva Learning usage reports Platforms/Services: Microsoft 365 admin center Viva Insights Viva Learning What will happen: The Viva Insights personal insights active-user trend chart will be retired. The Viva Learning usage report will be removed from the Microsoft 365 admin center Viva Learning analytics will continue through the Viva Learning reporting experience. [Action Required/Recommendations:] Update documentation referencing retired Viva reports. Communicate the reporting location change to reporting administrators. Use Viva Learning reporting within Viva Learning going forward [Compliance considerations:] Does the change include an admin control and, can it be controlled through Entra ID group membership?Yes. The feature includes or affects admin controls, policies, permissions, roles, authentication, or management settings as described in this message. Review the linked documentation or admin center controls for group-based configuration support. -
Microsoft Teams: Retirement of off-network invitations to Teams Free
MC1546409 · planForChange · normal · Updated 11/10/2026 00:03
Services: Microsoft Teams
Read message
[What and Why:] Microsoft Teams will retire the invitation flow that allows work or school users to invite people who cannot be found in Teams to create a Teams Free account and join a chat. This change retires the off-network invitation flow (via email or sharing a link to chat) only — not federation with Teams Free. [Rollout Schedule:] Worldwide: We will begin rolling out in early December 2026 and expect to complete by late December 2026. [Impact on Your Organization:] Who is affected: Users who use the off-network email invitation flow to invite external people to create a Teams Free account and join a chat. Users who user share a link to chat flow to invite external people to create a Teams Free account and join a chat. Platforms/Services: Microsoft Teams desktop, web and mobile apps What will happen: Users will no longer be able to send these onboarding invitations from Teams chats. People who need a Teams Free account will need to create one independently or collaborate through another supported method. Collaboration with existing Teams Free users remains available, subject to your organization's external-access policies. This change will take effect automatically. No admin action is required to enable the retirement. [Action Required/Recommendations:] No admin action is required for this change to take effect. However, we recommend updating user guidance and helpdesk documentation before December 6, 2026, to reflect the following alternatives: For ongoing chat: If recipients do not have a Teams account, they can create a Teams Free account independently or get invited as guests to an existing team. Once their account is discoverable, users can search for their registered email address and start a conversation. For team and channel collaboration: No change. For meetings: No change. [Compliance considerations:] No compliance considerations identified. Review as appropriate for your organization. -
(Updated) Classic Outlook for Windows: Upcoming visual improvements and a more consistent Outlook experience
MC1506730 · planForChange · normal · Updated 11/09/2026 22:05
Services: Exchange Online
Read message
Updated November 9, 2026: We’ve heard your feedback that you’d like more information about what’s changing in classic Outlook. To help end-users understand recent changes, we’re bringing back the What’s New in-app dialog. The dialog is designed to be nonintrusive and will appear automatically at most once per month in Production on Current Channel. Users can dismiss it at any time and reopen it later by selecting the What’s New button on the ribbon. Administrators can turn off the automated dialog and hide its ribbon button. For more information and configuration instructions, see What’s New in classic Outlook for Windows. [What and why] We’re making updates across Microsoft Outlook experiences to improve clarity and consistency across endpoints. The first updates focus on visual details such as icons, spacing, and alignment, while maintaining familiar ways of working. These updates are part of an ongoing series of improvements across Outlook experiences and are not a replacement for the classic Outlook experience. [Rollout schedule] General Availability (Worldwide): Beginning in mid-November 2026 (previously early November) and expected to complete by late November 2026 The initial visual updates will roll out to classic Outlook Current Channel. Users may receive individual improvements at different times as the rollout progresses. We will provide additional advance notice before larger changes that might affect navigation or workflows, including timing and any preparation required. [Impact on your organization] Who is affected Users of classic Outlook for Windows Current Channel Platforms and services The initial visual updates apply to classic Outlook for Windows Current Channel. We are also improving Outlook on the web, new Outlook for Windows, and Outlook for macOS to reduce unnecessary differences and make familiar capabilities easier to recognize across devices. What will happen Users will begin seeing visual refinements to familiar mail and calendar surfaces, including updates to icons, spacing, and alignment. These initial updates are intended to improve clarity and consistency without changing how users perform their tasks. This change does not replace the classic Outlook experience. No admin configuration changes are required for these initial visual updates. [Action required and recommendations] No admin action is required. We recommend that you: Inform your help desk that the appearance of some Outlook controls may change as updates roll out. Inform users as appropriate. Continue to direct users to Outlook’s existing feedback options to share feedback. [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
(Updated) Pay-as-you-go consumption-based meter for your extra SharePoint storage needs
MC1330893 · stayInformed · normal · Updated 11/09/2026 18:42
Services: SharePoint Online
Read message
Updated November 9, 2026: We have updated the timeline. Thank you for your patience. [Introduction] To help organizations manage SharePoint storage more flexibly and avoid over-provisioning, Microsoft is introducing a pay-as-you-go, consumption-based billing model for SharePoint storage overages. This option allows you to pay only for the additional storage you actually use, rather than pre-purchasing extra capacity. The experience integrates with Microsoft 365 Archive and helps align storage costs with real usage. This change is associated with Microsoft 365 Roadmap ID 506743. [When this will happen:] Public Preview (Worldwide): We completed rollout in June 2026. General Availability (WW): We expect to begin rolling out in early January 2027 (previously early November) and to complete rolling by late January 2027 (previously end of November). [How this affects your organization:] Who is affected: Microsoft 365 administrators managing SharePoint Online storage Note: This feature isn’t currently available to education tenants. Let us know if you’d like it to be supported in the future. What will happen: Admins can enable pay-as-you-go SharePoint storage billing in the Microsoft 365 admin center. Storage used above the included tenant quota will be automatically billed based on consumption. There is no impact to users. The existing Office 365 Extra File Storage add‑on remains available if you prefer to manually increase your storage quota instead. The feature is opt-in and off by default. [What you can do to prepare:] No immediate action is required. However, we recommend the following: Review your tenant’s current SharePoint storage usage in the SharePoint admin center > Active sites. Evaluate whether a consumption‑based model or manually purchased storage best fits your organization’s cost and governance preferences. If you plan to enable pay‑as‑you‑go billing:Ensure the appropriate Azure subscription and billing permissions are in place. Update internal documentation or cost‑management processes as needed. Share this information with finance or procurement teams if they track usage‑based charges. Learn more: Add more SharePoint storage to your subscription | Microsoft Learn [Compliance considerations] Compliance areaImpact and explanation Admin monitoring and reportingSharePoint storage usage above the included tenant quota will be reflected in consumption-based billing and usage reports, which may affect how admins monitor and track storage consumption and costs. Admin controlAdministrators must explicitly enable -
(Updated) Microsoft Purview: permissions audit log improvements
MC1473155 · stayInformed · normal · Updated 11/09/2026 18:00
Services: Microsoft Purview
Read message
Updated November 9, 2026: We have updated the timeline. Thank you for your patience. [What and why] To improve transparency and troubleshooting for Microsoft Purview role-based access control (RBAC), we are enhancing audit logging for permission checks performed in the Microsoft Purview portal. These new audit records will provide administrators with clearer visibility into role and scoped-role authorization decisions, helping them investigate access issues and better understand how access evaluations are performed. This message is associated with Microsoft 365 Roadmap ID 569363. [Rollout schedule] General Availability (Worldwide): Beginning in late September 2026 and expected to complete by mid-November 2026 (previously late October) [Impact on your organization] Who is affected Microsoft Purview administrators and compliance administrators who review audit logs for access investigations and troubleshooting Platforms and services Microsoft Purview portal Microsoft Purview Audit What will happen New audit records will be generated when access checks are performed in the Microsoft Purview portal. Two new audit operations will be available:CheckUsersInRoles CheckUserInRolesWithScopes Administrators will be able to review these audit records as part of SecurityComplianceRBAC audit activities. The enhancement is enabled by default and requires no configuration. Audit records will only be generated for access checks that occur after the feature is deployed. No historical or retroactive audit records will be created for prior access checks. There is no impact for organizations. Supported permission-assignment and role-group change audit records will include the ClientPortal field within PreExecutionMessage, helping administrators distinguish changes initiated from Microsoft Purview and Microsoft Defender. Supported activities for portal attribution Permission assignments: Granting, updating, or removing permission assignments. Role groups: Creating, updating, or deleting role groups. Expected ClientPortal values: Microsoft Purview portal: "ClientPortal": "Microsoft Purview" Microsoft Defender portal: "ClientPortal": "Microsoft Defender" RBAC audit-CheckUserInRolesWithScopes: RBAC audit-checkusersinroles: [Action required and recommendations] No action is required. We recommend that administrators: Review internal monitoring and audit procedures to determine whether the new audit activities should be included in access investigations. Inform compliance and security teams about the availability of the new audit operations. Update any internal documentation or reporting processes that reference Microsoft Purview RBAC audit data. Learn more Permissions in the Microsoft Purview portal | Microsoft Learn [Compliance considerations] QuestionAnswer Does the change modify, interrupt, or disable audit logging capabilities?Yes. The change enhances audit logging capabilities by adding two new audit operations. Does the change alter how admins can monitor, report on, or demonstrate compliance activities?Yes. Administrators gain additional audit visibility into RBAC access evaluation outcomes, improving monitoring and troubleshooting capabilities. -
(Updated) Microsoft 365 Copilot: Use Microsoft Agent 365 agents as connected agents in declarative agents
MC1478975 · stayInformed · normal · Updated 11/09/2026 17:50
Services: Microsoft 365 Copilot Chat
Read message
Updated November 9, 2026: We have updated the timeline. Thank you for your patience. [What and why] Microsoft is introducing support for Microsoft Agent 365 agents that implement the Agent2Agent (A2A) protocol, allowing them to be used as connected agents in declarative agents built with Microsoft 365 Agents Toolkit. This enhancement expands the types of external agent services that declarative agents can connect to. In addition to existing support for OpenAPI and Model Context Protocol (MCP) servers, declarative agents can now connect to Agent2Agent-enabled agents, enabling natural language interactions and support for more complex workflows. This feature gives developers greater flexibility when building declarative agents while providing administrators centralized management and governance through the Microsoft 365 admin center. [Rollout schedule] General Availability (Worldwide): Began in late August 2026 and is expected to complete by end of December 2026. [Impact on your organization] Who is affected Microsoft 365 administrators who manage agents in the Microsoft 365 admin center Developers building declarative agents with Microsoft 365 Agents Toolkit Users who are assigned access to approved Microsoft Agent 365 agents Platforms and services Microsoft 365 Copilot Microsoft 365 admin center Microsoft 365 Agents Toolkit Declarative agents What will happen Administrators can install Microsoft Agent 365 agents that support the Agent2Agent protocol from the All agents page in the Microsoft 365 admin center. Declarative agents can use approved Agent2Agent-enabled agents as connected agents. Agent2Agent support is added alongside existing support for OpenAPI and MCP server connections. Users cannot install Agent2Agent-enabled Microsoft Agent 365 agents themselves. Administrators can review Agent2Agent-connected agents from the Connected agents tab in the declarative agent details page before approving their use. [Action required and recommendations] Action may be required. Before rollout: Review Microsoft Agent 365 agents available in the All agents page of the Microsoft 365 admin center. Determine which Agent2Agent-enabled agents should be made available to users in your organization. Review connected agents associated with declarative agents from the Connected agents tab before approving their use. Update any internal governance, agent approval, or deployment processes as appropriate. Consider notifying administrators and developers in your organization about the availability of Agent2Agent-connected agents and the associated review and approval process. [Compliance considerations] Compliance considerationAnswer Does this change introduce or significantly modify AI, machine learning, or agent capabilities that interact with or provide access to customer data?Yes. This update introduces support for Agent2Agent-enabled Microsoft Agent 365 agents as connected agents within declarative agents. Organizations should review how these connected agents interact with customer data before approving them for use. Does this change provide end users with a new way to interact with generative AI?Yes. Users can interact with declarative agents that are connected to Agent2Agent-enabled agents, enabling new AI-powered experiences and workflows. Does this change include an admin control?Yes. Administrators can install, review, and approve Agent2Agent-enabled Microsoft Agent 365 agents through the Microsoft 365 admin center before they are available for use. -
Microsoft 365 Copilot: Legal plugins in Word and Cowork
MC1509799 · planForChange · normal · Updated 11/09/2026 17:47
Services: Microsoft 365 apps
Read message
[What and why] Microsoft 365 Copilot is introducing legal plugins in Word and Cowork. These plugins provide purpose-built skills to help legal professionals summarize, draft, review, and redline legal documents. They can use work context from Microsoft 365 and connect to supported third-party legal sources, helping legal professionals complete legal work in the Microsoft 365 experiences they already use. [Rollout schedule] Public Preview (Worldwide): Rollout began in late April 2026 and is expected to complete by mid-December 2026 General Availability (Worldwide): We will begin rolling out in mid-October 2026 and expect to complete by mid-December 2026 [Impact on your organization] Who is affected Users with Microsoft 365 Copilot commercial licenses Platforms and services Microsoft 365 Copilot Word desktop Cowork What will happen Legal plugins in Copilot provide purpose-built skills to help legal professionals summarize, draft, review, and redline legal documents. The plugins can use work context from Microsoft 365 and connect to supported third-party legal sources. The legal capabilities include more than 20 purpose-built legal skills. In Word desktop, the legal plugin is enabled by default. When enabled, Copilot can use legal skills to complete legal tasks in Word. In Cowork, users must add the legal plugin before Copilot can use legal skills to complete legal tasks. The legal skills can help users review contracts against playbooks, draft contracts using templates and precedent agreements, compare contracts with precedents, templates, and policies, and explain tracked changes. The Legal Agent is being retired. Existing Legal Agent users will lose access to the product. [Action required and recommendations] No admin setup is required. If your organization plans to use the legal plugins: Ensure Microsoft 365 Copilot licenses are assigned to eligible users. Review internal legal workflows that may benefit from these capabilities. Communicate these capabilities to your legal teams. Update internal documentation or help desk guidance as appropriate. Instruct legal team users to add the legal plugin in Cowork. Instruct legal team users to use legal skills in Copilot in Word desktop. If your organization does not plan to use the legal plugins: Turn off Legal Skills in M365 Copilot in Word in the Microsoft 365 Apps admin center to disable the legal plugin in Word for all users. Turn off the Cowork for Legal plugin in the Microsoft 365 admin center to disable the plugin in Cowork for all users. Learn more Manage Copilot for legal - Microsoft 365 admin | Microsoft Learn [Compliance considerations] QuestionAnswer Does the change alter how existing customer data is processed, stored, or accessed?Yes. The legal plugins can use work context from Microsoft 365 to support legal tasks. The supplied source does not specify changes to data storage or caching. Does the change introduce or significantly modify AI/ML or agent capabilities that interact with or provide access to customer data?Yes. Legal capabilities previously released as the Legal Agent are being made available as legal plugins in Word and Cowork. They provide purpose-built legal skills and can use work context from Microsoft 365. Does the change provide users a new way of interacting with generative AI?Yes. Users can use purpose-built legal skills in Copilot in Word and Cowork to summarize, draft, review, and redline legal documents. Does the change add integration with third-party software products?Yes. The legal plugins can connect to supported third-party legal sources. The supplied sources do not identify specific third-party products. Does the change include an admin control?Yes. Admins can turn off Legal Skills in M365 Copilot in Word in the Microsoft 365 Apps admin center and turn off the Cowork for Legal plugin in the Microsoft 365 admin center. The supplied source does not specify whether these controls support Entra ID group membership. Does the change allow a user to enable or disable the feature themselves?Yes. In Cowork, users must add the legal plugin before using its legal skills. The supplied source does not state that users can independently disable the Word legal plugin. -
(Updated) Microsoft Copilot Feedback UX update
MC1530595 · stayInformed · normal · Updated 11/09/2026 17:41
Services: Microsoft 365 Copilot Chat
Read message
Updated November 3, 2026: We have updated the timeline. Thank you for your patience. [What and Why:] We’re updating the thumbs-down feedback experience in Microsoft Copilot to make it easier for users to provide specific, actionable feedback. Today, many thumbs-down responses are submitted without comments, providing sentiment but limited information about the issue. When users select thumbs down, they’ll be able to select one or more feedback categories and optionally provide additional comments, giving each categorized response a signal that can be routed to the appropriate team or issue type. [Rollout Schedule:] General Availability (Worldwide): We will begin rolling out in mid-November 2026 (previously late October) and expect to complete by mid-November 2026 (previously late October). [Impact on Your Organization:] Users who can submit feedback in supported Microsoft Copilot experiences may see the updated thumbs-down feedback form. The planned audience includes users signed in with Microsoft Entra ID organizational accounts, users signed in with consumer Microsoft accounts, and users in Education tenants. The feature isn’t currently planned for Mobile, GCC, GCC High, DoD, or other sovereign cloud environments. The updated feedback experience is planned for Microsoft Copilot, Copilot in Microsoft Edge, Copilot in Microsoft Outlook, and Copilot in Microsoft Teams, across web browsers, Windows, and macOS. The WXPN/Catalyst experience isn’t currently included. When a user selects thumbs down on a Copilot response, they may see selectable categories describing the issue, can select more than one category, and can optionally enter additional feedback in a free-text field. The thumbs-up feedback experience isn’t changing. This update applies only to the existing “Allow users to submit feedback to Microsoft” admin policy; all other feedback policy experiences remain unchanged. During the controlled rollout, some users will continue to see the existing feedback experience. [Action Required/Recommendations:] No admin action is required for this change. It will be visible to users who are already allowed to submit feedback under the existing policy. [Compliance considerations:] QuestionAnswer Does the change store new customer data?Yes. When a user chooses to submit thumbs-down feedback, the selected categories, optional free-text comment, and optional screenshot are new data captured as part of that submission. Does the change include an admin control and can it be controlled through Entra ID group membership?Yes. This UX change applies to the existing "Allow users to submit feedback to Microsoft" admin policy; all other feedback policy experiences remain unchanged. -
(Updated) Rewrite with Microsoft 365 Copilot Chat coming soon to Edge for Business users
MC1146821 · stayInformed · normal · Updated 11/09/2026 17:27
Services: Microsoft 365 Copilot Chat
Read message
Updated November 9, 2026: We have updated the timeline. Thank you for your patience. Introduction Microsoft Edge for Business will soon support Writing Assistance, a new feature powered by Microsoft 365 Copilot Chat. This capability helps users draft and rephrase editable text directly within Edge, enhancing productivity and writing quality. Users can access Writing Assistance by highlighting editable text and right-clicking to open the context menu. This message is associated with Microsoft 365 Roadmap ID 420335. When this will happen General Availability (Worldwide): We will begin rolling late January 2027 (previously end of October 2026) and expect to complete rollout by late January 2027 (previously late October). How this affects your organization Writing Assistance will be enabled by default for Edge for Business users. Users can access Writing Assistance by highlighting editable text and right-clicking to open the context menu. If Microsoft 365 Copilot is restricted from accessing page content due to Data Loss Prevention (DLP) policies, Writing Assistance will not function on that content. Admins can manage this feature using the InlineComposeEnabled policy setting. What you can do to prepare No admin action is required before rollout. We recommend: Reviewing your current DLP configurations to understand how they may impact Writing Assistance functionality. Notifying users about this new capability. Updating internal documentation to reflect this change. Learn more about how DLP affects Copilot access to page content: Microsoft 365 Copilot Chat in Edge and Access to Page Content | Microsoft Edge | Microsoft Learn Compliance considerations Does the change introduce or significantly modify AI/ML or agent capabilities that interact with or provide access to customer data?Yes. This change introduces a new generative AI capability through Microsoft 365 Copilot Chat, allowing users to rewrite or draft text directly in Edge for Business. Does the change provide end users any new way of interacting with generative AI?Yes. Users can interact with Copilot Chat by highlighting editable text and using the right-click context menu to access Writing Assistance, enabling AI-assisted drafting and rephrasing. Does the change modify Data Loss Prevention (DLP) policies or enforcement?Yes. If DLP policies restrict Copilot from accessing page content, the Writing Assistance feature will not function on that content. Does the change include an admin control and can it be controlled through Entra ID group membership?Yes. Admins can manage the availability of this feature using the InlineComposeEnabled policy setting. Does the change allow a user to enable and disable the feature themselves?Yes. Users can choose to use the Writing Assistance feature by manually invoking it through the right-click context menu in Edge. -
(Updated) Migrate Free/Busy, MailTips, and Calendar Sharing before EWS deprecation
MC1446796 · planForChange · normal · Updated 11/09/2026 17:10
Services: Exchange Online
Action required by: 10/01/2026 07:00
Read message
Updated November 9, 2026: We have updated the timeline. Gov rollout of this feature is still paused at this time. We will communicate via Message center when we are ready to proceed. We apologize for any inconvenience. [What and Why:] Exchange Web Services (EWS) deprecation begins October 1, 2026. Cross-tenant collaboration features — Free/Busy, MailTips, and Calendar Sharing — currently rely on EWS. Cross-tenant Free/Busy, MailTips will be available by September 2026 and Calendar Sharing will be available by late November 2026 (previously early November) via Microsoft 365 Cross-Tenant Access Policy, which replaces EWS-based cross-tenant collaboration. [Rollout Schedule:] Worldwide: We will begin rolling out in August 2026 and expect to complete by September 15, 2026 for Free/Busy, Mailtips and November 23, 2026 (previously November 3) for Calendar Sharing. GCC, GCC High, DoD: We will communicate via Message center when we are ready to proceed. [Impact on your organization:] Sharing Free/Busy, Calendars, and MailTips (e.g., out of office message) with another Microsoft 365 organization via Organization Relationship or Sharing Policy relies on Exchange Web Services (EWS), which is being deprecated. To preserve these cross-tenant collaboration scenarios, you will need to start migrating to Microsoft 365 Cross Tenant Access Policy. Your tenant is affected if it uses any of the following Exchange Online configurations: Organization Relationships — sharing Free/Busy or MailTips with other Microsoft 365 tenants Sharing Policies — sharing calendars externally, either via invitations sent to recipients in other Microsoft 365 organizations or calendars published for anonymous access via an internet URL Run these commands in Exchange Online PowerShell to check if your tenant is affected: Get-OrganizationRelationship | Format-List Name, DomainNames, Enabled, FreeBusyAccessEnabled, FreeBusyAccessLevel, FreeBusyAccessScope, MailTipsAccessEnabled, MailTipsAccessLevel, MailTipsAccessScopeIf results show (1) Enabled: True, and (2) either FreeBusyAccessEnabled: True or MailtipsAccessEnabled: True, and (3) the external organization is hosted in Microsoft 365, your tenant is affected and in scope to migrate. Else, no action is needed. Get-SharingPolicy | Format-List Name, Domains, Enabled, DefaultIf results show (1) Enabled: True, and (2) the Domains property contains at least one rule with a CalendarSharingFreeBusy access level (Simple, Detail, or Reviewer), and (3) the targeted external organization is hosted in Microsoft 365, and (4) the policy is assigned to one or more mailboxes, your tenant is affected and in scope to migrate. Else, no action is needed. Note: rules that begin with Anonymous: represent calendar publishing to anonymous internet recipients via a published URL - these also appear in this output. What happens if I do nothing: Starting October 1, 2026, Exchange Web Services (EWS) will be gradually disabled in line with previous communications linked to this message. As this rollout reaches your tenant, cross-tenant Free/Busy, MailTips, and Calendar Sharing that rely on EWS will be affected — recipients in partner organizations may no longer see Free/Busy, MailTips, or shared calendars from your tenant. If your organization is not ready to migrate, you can retain EWS access by following the guidance of the latest blog we published: ExchangeOnline EWS, Your Time is Almost Up (EWSEnabled set to True) while you prepare and execute the migration steps attached to this message. EWS access through this extension will remain available until the final EWS shutdown on April 1, 2027. [Action Required/Recommendations:] Follow this Message center post for updates to the rollout schedule. To avoid impact, plan to migrate after the rollout reaches your tenant and before EWS deprecation. Review the migration guide linked below for step-by-step instructions to understand your current configurations, set up new Microsoft 365 Cross Tenant Access Policies, validate the new configurations, and remove unused configurations. Check the blog post linked below for additional information and answers to frequently asked questions. Hybrid and on-premises scenarios are not in scope. This update applies to fully cloud-hosted (Exchange Online ↔ Exchange Online) cross-tenant and cross-cloud configurations only. For organizations running on-premises Exchange and Exchange Online in a Hybrid Deployment, migrate to Dedicated Hybrid App. For organizations hosted in Exchange Online sharing with another organization running Exchange on-premises, kindly monitor future Message Center posts for guidance on migration paths as they become available. [Additional information:] Migration guide: Migrating to Microsoft 365 Cross-Tenant Access Policy for sharing Free/Busy, Calendars, and MailTips. Microsoft 365 Cross-Tenant Access Policy Microsoft Graph API Overview Exchange Online EWS, Your Time is Almost Up Deprecation of EWS in Exchange Online Enhancing Microsoft 365 security by eliminating high-privilege access Blog Post: Cross-tenant Free/Busy, MailTips, and Calendar Sharing are moving to Cross-Tenant Access Policy -
Microsoft OneDrive and SharePoint: Annotate sensitivity-label protected PDFs on the web
MC1545696 · stayInformed · normal · Updated 11/09/2026 14:41
Services: SharePoint Online, Microsoft OneDrive
Read message
[What and why] Microsoft OneDrive and SharePoint on the web will support annotation for PDFs encrypted with Microsoft Purview sensitivity labels. Users who have the appropriate editing usage rights will be able to annotate protected PDFs in their browser without removing the sensitivity label. The file's sensitivity label, encryption, and usage rights will be preserved when changes are saved. [Rollout schedule] General Availability (Worldwide, GCC, GCC High, DoD): Beginning in late January 2027 and expected to complete in late January 2027 [Impact on your organization] Who is affected OneDrive for Business and SharePoint customers This feature does not apply to OneDrive Consumer. Platforms and services OneDrive for Business and SharePoint on the web All browsers are supported. What will happen Users who have editing usage rights can annotate sensitivity label-protected, encrypted PDFs in the OneDrive or SharePoint web PDF viewer. Available annotation tools include ink, highlight, free text, notes, signatures, image/shape/date stamps, bookmarks, and form fields. Users can save annotations without removing the sensitivity label. The sensitivity label, encryption, and usage rights are preserved when the annotated PDF is saved. Users with view-only rights will continue to see the PDF as read-only and cannot annotate. This change does not grant users additional access or editing rights. No feature-specific admin control or configuration is required. Existing sensitivity label and usage-rights settings determine who can view or edit protected PDFs. [Action required and recommendations] No feature-specific admin action is required to enable this update. We recommend that you: Inform users who routinely review labeled or regulated documents that they can annotate protected PDFs in place. Confirm that your sensitivity label and usage-rights configuration reflects who should be able to edit or view protected PDFs. Update internal documentation and helpdesk guidance as appropriate. [Compliance considerations] QuestionAnswer Does the change alter how existing customer data is accessed or modified?Yes. Users with existing editing usage rights gain a new way to modify protected PDFs by adding annotations in the OneDrive or SharePoint web PDF viewer. Does the change preserve Information Protection label behavior?Yes. Users can annotate PDFs protected by sensitivity labels without removing the label. The sensitivity label, encryption, and usage rights are preserved when the file is saved. -
App Blocks in M365 Copilot
MC1545695 · stayInformed · normal · Updated 11/09/2026 14:41
Services: Microsoft 365 Copilot Chat
Read message
[What and Why:] App Blocks enables M365 Copilot Chat users to turn their requests and data into rich, interactive experiences directly within the conversation, including calculators, dashboards, forms, planners, visualizations, simulations, comparison tools, and other interactive apps. It helps users move beyond static responses to explore data, adjust inputs, visualize outcomes, and simulate workflows in place, while supporting grounded scenarios where current information can be retrieved and then rendered into an interactive experience. [Rollout Schedule:] General Availability (Worldwide): We will begin rolling out in late October 2026 and expect to complete by early November 2026. [Impact on Your Organization:] Who is affected: Users of Microsoft 365 Copilot (Premium) and Copilot Chat (Basic). Platforms/Services: Microsoft 365 Copilot Chat What will happen: App Blocks will render directly within Copilot conversations. Users can preview apps without opening a separate app canvas. The update streamlines the Copilot experience by keeping generated content and previews within the conversation flow. Existing Copilot workflows and prompts continue to work as expected. [Action Required/Recommendations:] No action is required. You may want to notify your users about this experience update and update any internal training or adoption materials that reference the side-by-side app canvas experience. [Compliance considerations:] No compliance considerations identified. Review as appropriate for your organization. -
Microsoft Purview: Retirement of select DSPM partner integrations
MC1545691 · planForChange · normal · Updated 11/09/2026 14:39
Services: Microsoft Purview
Read message
[What and why] Effective December 7, 2026, we will retire the public preview experience for select non-Microsoft data sources in Microsoft Purview Data Security Posture Management (DSPM) through partner integrations. The affected partner integrations are Varonis for Salesforce data, BigID for Databricks, Cyera for Snowflake, and OneTrust for Google Cloud Platform (GCP). We are evolving Microsoft Purview and rethinking how we bring non-Microsoft signals into the Purview experience. This change applies only to the partner integrations listed above. Other Microsoft Purview DSPM capabilities are not affected. [Rollout schedule] The affected partner integrations will no longer be available beginning December 7, 2026. This change applies to: Worldwide GCC GCC High DoD [Impact on your organization] Who is affected Organizations participating in the public preview for connecting supported non-Microsoft data sources to Microsoft Purview DSPM through the affected partner integrations Platforms and services Microsoft Purview Data Security Posture Management (DSPM) What will happen Beginning December 7, 2026: Organizations will no longer be able to connect the supported non-Microsoft data sources to Microsoft Purview DSPM through the affected partner integrations. Data from those sources will no longer be ingested, processed, or displayed in Microsoft Purview DSPM through these integrations. Other Microsoft Purview DSPM capabilities are not affected. [Action required and recommendations] No action is required. If your organization currently uses these integrations, we recommend reviewing related internal processes or dependencies and updating them as needed before December 7, 2026. Learn more Learn about Microsoft Purview Data Security Posture Management (DSPM) | Microsoft Learn [Compliance considerations] QuestionAnswer Does the change alter how existing customer data is processed, stored, or accessed?Yes. After retirement, data from the affected non-Microsoft sources will no longer be ingested, processed, or displayed in DSPM through these integrations. -
(Updated) Microsoft 365 settings enabled by default for newly created Engage communities
MC1480869 · stayInformed · normal · Updated 11/07/2026 00:00
Services: Microsoft Viva
Read message
Updated October 21, 2026: We have updated the timeline. Thank you for your patience. [What and Why:] Microsoft Viva Engage is updating newly created Engage communities so Microsoft 365 group settings for community member calendar and email subscriptions are enabled by default. This change helps community members receive community emails and calendar invitations by default for newly created communities, supporting awareness and participation in new Engage communities. [Rollout Schedule:] Rollout will complete by end of November 2026 (previously mid-October). [Impact on Your Organization:] Who is affected: Viva Engage community owners and members. Admins who support Viva Engage and Microsoft 365 group-backed communities. Platforms/Services: Microsoft Viva Engage. Microsoft 365 groups. My Account portal. What will happen: Newly created Engage communities will have Microsoft 365 group settings enabled by default. Community members will be subscribed to receive community emails and calendar invitations by default. Community owners can adjust these settings in the My Account portal. Existing Engage communities will receive these updates later this fall; Microsoft will share additional timing before that rollout begins. [Action Required/Recommendations:] No admin action is required. Community owners should review and adjust these settings in the My Account portal as needed: https://myaccount.microsoft.com/groups/groups-i-own. Inform community owners and support teams that newly created communities may subscribe members to community emails and calendar invitations by default. [Compliance considerations:] Does the change provide a new way to communicate between users, tenants, or subscriptions?Yes. Newly created Engage communities will subscribe community members to receive community emails and calendar invitations by default, affecting how community communications are delivered to members. Does the change include an admin control and, can it be controlled through Entra ID group membership?Yes. Community owners can adjust the Microsoft 365 group settings for communities in the My Account portal. The request does not specify Entra ID group-based control for this setting. -
(Updated) Microsoft Outlook: New event duplication capability
MC1492166 · stayInformed · normal · Updated 11/06/2026 22:11
Services: Exchange Online
Read message
Updated November 6, 2026: We have updated the timeline. Thank you for your patience. [What and why] We are adding the ability to duplicate an event in Microsoft Outlook. From the event details, users can select Duplicate event to quickly create a new event based on an existing event without re-entering the same details. [Rollout schedule] General Availability (Worldwide, GCC, GCC High): Rollout began in late September 2026 and is expected to complete by early December 2026 (previously late October). [Impact on your organization] Who is affected Users who create events in Microsoft Outlook Platforms and services Microsoft Outlook What will happen A new Duplicate event option will appear in Microsoft Outlook event details. Users can quickly create a new event based on an existing event without re-entering the same details. [Action required and recommendations] No action is required. [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
Microsoft 365 Copilot: Changes to custom organizational data in MODS for Workforce Insights
MC1542066 · planForChange · normal · Updated 11/06/2026 21:34
Services: Microsoft 365 suite
Action required by: 11/18/2026 08:00
Read message
[What and why] We're changing how the Workforce Insights agent receives custom organizational data from Microsoft 365 Organizational Data Service (MODS). The separate Workforce Insights endpoint in MODS will be retired. Going forward, organizational data will reach the Workforce Insights agent through the Microsoft 365 profile endpoint. The Workforce Insights agent is part of the Microsoft Frontier program and is currently in preview. Ingestion of custom public attributes through Microsoft 365 profile is already generally available. For custom non-public attributes, customers who currently use the Workforce Insights endpoint in MODS or wish to enable this capability for the first time, must join the private preview. [Rollout schedule] Workforce Insights endpoint retirement (Frontier preview) in MODS: Starting November 18, 2026 [Impact on your organization] Who is affected Organizational Data Source Administrators in organizations that send custom attributes to the Workforce Insights endpoint in MODS Organizations that plan to use custom attributes in Copilot experiences and the Workforce Insights Agent If your organization doesn't send custom attributes to the Workforce Insights endpoint today, no immediate action is required Platforms and services Microsoft 365 Organizational Data Service Microsoft 365 profile Microsoft 365 Copilot Workforce Insights agent What will happen After November 18, 2026, the Workforce Insights endpoint will no longer be available as a destination in MODS. To ingest custom public attributes, use the Microsoft 365 profile endpoint in MODS. To bring custom non-public attributes (such as job level) into Copilot experiences and the Workforce Insights Agent, your organization must join the private preview. Your current Workforce Insights endpoint selection won’t carry over. You must explicitly select the Microsoft 365 profile endpoint in MODS. Data previously uploaded to the Workforce Insights endpoint will remain stale and continue to serve the Workforce Insights Agent and organizational queries in Copilot. You won't be able to upload subsequent data through the retired endpoint. See how to manage your data in MODS documentation in the Learn more section below. [Action required and recommendations] If your organization currently sends custom non-public attributes to the Workforce Insights endpoint in MODS, complete these actions before November 18, 2026: Identify what attributes you ingest to Workforce Insights endpoint today. Ingest updated public attributes using Microsoft 365 profile endpoint in MODS. For non-public attributes, request to join the private preview by contacting wficomm@microsoft.com. Work with privacy and data governance stakeholders to determine the access policy and then ingest data to the Microsoft 365 profile endpoint. Keep in mind that these attributes will also be available to Copilot experiences as capabilities continue to roll out, not only the Workforce Insights Agent. Don't select the Workforce Insights endpoint for new uploads, even if it's still available when your preview starts. Complete the switch before November 18, 2026. Learn more Overview of Workforce Insights Agent Introduction to Microsoft 365 Organizational Data Service Import and manage your organizational data with a .csv file - Microsoft 365 Apps | Microsoft Learn [Compliance considerations] QuestionAnswer Does the change alter how existing customer data is processed, stored, or accessed?Yes. For existing customers who has ingested custom attributes through Workforce Insights endpoint in MODS, the uploaded data will be made available to Microsoft 365 profile, Copilot experiences and Workforce Insights agent. Does the change introduce or significantly modify AI/ML or agent capabilities that interact with or provide access to customer data?Yes. The change modifies how custom organizational attributes are made available to the Workforce Insights agent and Copilot experiences. -
(Updated) New Outlook for Windows: All Accounts view brings email into a single inbox view
MC1519843 · stayInformed · normal · Updated 11/06/2026 21:05
Services: Exchange Online
Read message
Updated November 6, 2026: Admin controls for All Accounts view (Unified Inbox) are now available. We have added policy configuration guidance below. Thank you for your patience. [What and Why:] The All Accounts view, also known as Unified Inbox, lets users see email from multiple connected accounts in a single inbox view in the new Outlook for Windows without merging their mailboxes. Each account's inbox stays separate, and All Accounts view brings messages together so users can triage mail from one place. Users can read, delete, search, move, archive, and mark messages across accounts without switching between mailboxes. The experience integrates with Copilot for AI-assisted email workflows and supports Search with Copilot for finding messages across the user's primary account. [Rollout Schedule:] General Availability (Worldwide): We began rolling out in late September 2026 and expect to complete by late November 2026 (previously late October). [Impact on Your Organization:] Users with more than one connected account in the new Outlook for Windows will be able to triage email across accounts from a single All Accounts view. This does not merge mailboxes or move messages between accounts. Each account remains separate, and All Accounts view provides a unified view only. All Accounts view is enabled by default for eligible users. Users can change this setting unless their organization enforces a configuration through the admin policy described below. [Action Required/Recommendations:] No admin action is required unless you want to manage this experience for your users. The policy “Show All Accounts view for users with multiple accounts in Outlook for Windows” is now available through the Microsoft 365 Apps admin center at config.office.com. Admins can configure whether All Accounts view is enabled or disabled by default and whether users can change that setting. The policy can be applied to selected groups. If the policy is not configured, All Accounts view remains enabled by default, and users can turn it off or back on. Admins who want to disable it and prevent users from enabling it must set “Configure the unified inbox view” to Disabled and “Allow user to override this setting” to Disabled. To configure the policy: Go to config.office.com and open Customization > Policy Management. Create or edit a policy configuration and scope it to the group you want to manage. Find “Show All Accounts view for users with multiple accounts in Outlook for Windows” and set Configuration setting to Enabled. Under “Configure the unified inbox view,” select Enabled to show All Accounts view by default, or Disabled to keep account inboxes separate by default. Under “Allow user to override this setting,” select Enabled to let users change the configured behavior, or Disabled to prevent changes. Review and publish the policy configuration. [Compliance considerations:] This feature provides a unified view across connected accounts in the new Outlook for Windows but does not merge mailboxes or move messages between accounts. Review your organization's Outlook account and automated-assistance policies as appropriate. -
(Updated) Microsoft 365: Enrich profile cards with custom properties from third-party systems
MC1193692 · stayInformed · normal · Updated 11/06/2026 18:23
Services: Exchange Online
Read message
Updated November 6, 2026: We have updated the timeline. Thank you for your patience. We’re introducing the ability for organizations to customize Microsoft 365 profile cards by adding up to 10 custom properties sourced from external systems such as HR platforms. This enhancement helps enrich user profiles with relevant organizational details, improving discoverability and context for collaboration. This message is associated with Microsoft 365 Roadmap ID 529851. When this will happen: General Availability (Worldwide): We will begin rolling out in January 2027 (previously November 2026) and expect to complete in January 2027 (previously November 2026). How this affects your organization Who is affected: Microsoft 365 tenant admins managing user profile cards What will happen: You can add up to 10 custom properties to profile cards using Microsoft Graph People connectors. Properties can be sourced from external systems (such as HR platforms). This feature is OFF by default and requires admin configuration to enable. Admins can configure visibility, display name, and icon for each property in Microsoft 365 admin center under: Settings > Org settings > People settings > Profile > Person info on profile cards Once enabled, properties appear in the Contact Information section of profile cards in Outlook Web: Changes may take up to 24 hours to propagate across profile cards. Future updates will include direct ingestion from SAP SuccessFactors and Workday connectors. What you can do to prepare Review external systems for properties you want displayed on profile cards. Ingest these properties using a Microsoft Graph People connector. Configure visibility and enable properties in the Microsoft 365 admin center. Communicate this change to helpdesk staff and update internal documentation if needed. Learn more: Microsoft 365 Copilot connectors for people data | Microsoft Learn Compliance considerations No compliance considerations identified. Review as appropriate for your organization. -
(Updated) Outlook for Windows report retirement in the Exchange admin center
MC1230889 · planForChange · normal · Updated 11/06/2026 17:17
Services: Microsoft 365 apps
Action required by: 11/02/2026 07:00
Read message
Updated November 6, 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 early April 2027 (previously early November 2026). Retirement will complete in early April 2027 (previously early November 2026). [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) Microsoft OneNote: Multimodal recording in Copilot Notebooks on Windows
MC1405506 · planForChange · normal · Updated 11/06/2026 17:12
Services: Microsoft 365 apps
Read message
Updated November 6, 2026: We have updated the timeline. Thank you for your patience. [What and why] We are introducing multimodal capture in Copilot Notebooks on Windows. This feature enables users to capture audio, images, and notes in a single experience and use Microsoft 365 Copilot to generate structured insights such as summaries, decisions, and action items. This helps users turn meetings, conversations, and offline work into actionable outputs within Copilot Notebooks. This message is associated with Microsoft 365 Roadmap ID 566322. [Rollout schedule] General Availability (Worldwide): Beginning end of November 2026 (previously end of October) and expected to complete end of November 2026 (previously end of October) [Impact on Your Organization] Who is affected Users with access to Copilot Notebooks in OneNote Requires a Microsoft 365 Copilot license Available to commercial Microsoft 365 users with work or school (Entra ID) accounts Users must have the Microsoft 365 desktop apps installed on Windows (including OneNote) Platforms/Services OneNote (desktop app on Windows) Copilot Notebooks Microsoft 365 Copilot What will happen Users can capture audio, images, and notes directly into Copilot Notebooks. Capture can be suggested or initiated when supported browser-based meetings are detected (Zoom, Webex, Google Meet). Users can also manually start capture from the OneNote system tray icon. Copilot generates a structured Copilot Page with insights, decisions, and action items based on captured content. Captured content is saved to the selected Copilot Notebook and is available across endpoints. The feature is available by default for eligible users. [Action Required or Recommendations] No action is required. Admins can disable this feature using a policy setting. Review available policy settings if you want to disable the feature. Inform users about organizational policies related to transcription and consent. Organizations should ensure users follow applicable consent and recording policies before capturing or transcribing conversations. Learn more: Data, Privacy, and Security for Microsoft 365 Copilot | Microsoft 365 Copilot | Microsoft 365 | Microsoft Learn Security for Microsoft 365 Copilot | Microsoft 365 Copilot | Microsoft 365 | Microsoft Learn [Compliance considerations] QuestionAnswer Does the change store new customer data?Yes. Captured audio, images, and notes are stored in the user’s selected Copilot Notebook (SharePoint or OneDrive). Does the change alter how customer data is processed?Yes. Content is transcribed and processed by Microsoft 365 Copilot to generate structured insights. Does the change introduce AI capabilities interacting with data?Yes. Copilot analyzes captured content to generate summaries, decisions, and action items. Does the change provide new interaction with generative AI?Yes. Users interact with Copilot-generated outputs based on captured multimodal data. Does the change add a third party integration?Yes. Supports capture from browser-based meetings including Zoom, Webex, and Google Meet. Does the change include admin control?Yes. Admins can disable the feature using a policy setting. -
(Updated) Microsoft 365 Copilot: Copilot chat pane and Summary feature in OneNote Mobile (iPhone)
MC1307979 · stayInformed · normal · Updated 11/06/2026 17:09
Services: Microsoft 365 apps
Read message
Updated November 6, 2026: We have updated the timeline. Thank you for your patience. [Introduction] Microsoft is introducing a new Copilot chat pane in OneNote Mobile (iPhone) for users licensed with Microsoft 365 Copilot (Premium). This update adds a new Summary feature that allows users to generate concise summaries of longer OneNote pages, as well as ask questions about their notes, directly within the OneNote mobile app. This helps users review and interact with note content more efficiently while on the go. This message is associated with Microsoft 365 Roadmap ID 422324. [When this will happen] General Availability (Worldwide): We will begin rolling out end of November 2026 (previously end of October) and expect to complete end of November 2026 (previously end of October) . [How this affects your organization] Who is affected Users with Microsoft 365 Copilot (Premium) licenses Users accessing OneNote on iPhone All Microsoft 365 tenants What will happen Users with a Microsoft 365 Copilot (Premium) license will see a Copilot chat pane in the OneNote mobile app on iPhone: The Copilot chat pane allows users to generate concise summaries of longer OneNote pages and ask questions about their notes: Existing Microsoft 365 Copilot controls, permissions, and policies continue to apply. Users without a Microsoft 365 Copilot (Premium) license are not impacted. [What you can do to prepare] No admin action is required before rollout. Ensure that users who should access this feature are assigned a Microsoft 365 Copilot (Premium) license. Consider informing helpdesk staff and users about the availability of Copilot chat and the Summary feature in OneNote mobile. Review existing Microsoft 365 Copilot governance, compliance, and usage policies to ensure they align with your organization’s requirements. [Compliance considerations] Question Answer Does the change alter how existing customer data is processed, stored, or accessed?Yes. Copilot chat processes OneNote content that users already have access to in order to generate summaries and answer questions, in accordance with existing Microsoft 365 Copilot data handling, permissions, and security controls. Does the change introduce or significantly modify AI or ML capabilities that interact with customer data? Yes. This update introduces Copilot chat capabilities within OneNote Mobile, allowing generative AI to analyze note content that the user has permission to access. Does the change provide end users a new way of interacting with generative AI? Yes. Users can interact with generative AI through the Copilot chat pane in OneNote Mobile to summarize content and ask questions about their notes. -
(Updated) Microsoft 365 Copilot: Copilot chat pane and Summary feature in OneNote Mobile (Android)
MC1309746 · stayInformed · normal · Updated 11/06/2026 17:06
Services: Microsoft 365 apps
Read message
Updated November 6, 2026: We have updated the timeline. Thank you for your patience. [Introduction] Microsoft is introducing a new Copilot chat pane in OneNote Mobile (Android) for users licensed with Microsoft 365 Copilot (Premium). This update adds a new Summary feature that allows users to generate concise summaries of longer OneNote pages, as well as ask questions about their notes, directly within the OneNote mobile app. This helps users review and interact with note content more efficiently while on the go. This message is associated with Microsoft 365 Roadmap ID 422323. [When this will happen] General Availability (Worldwide): We will begin rolling out end of November 2026 (previously end of October) and expect to complete end of November 2026 (previously end of October). [How this affects your organization] Who is affected Users with Microsoft 365 Copilot (Premium) licenses Users accessing OneNote on Android All Microsoft 365 tenants What will happen Users with a Microsoft 365 Copilot (Premium) license will see a Copilot chat pane in the OneNote mobile app on Android: The Copilot chat pane allows users to generate concise summaries of longer OneNote pages and ask questions about their notes: Existing Microsoft 365 Copilot controls, permissions, and policies continue to apply. Users without a Microsoft 365 Copilot (Premium) license are not impacted. [What you can do to prepare] No admin action is required before rollout. Ensure that users who should access this feature are assigned a Microsoft 365 Copilot (Premium) license. Consider informing helpdesk staff and users about the availability of Copilot chat and the Summary feature in OneNote mobile. Review existing Microsoft 365 Copilot governance, compliance, and usage policies to ensure they align with your organization’s requirements. [Compliance considerations] QuestionAnswer Does the change alter how existing customer data is processed, stored, or accessed?Yes. Copilot chat processes OneNote content that users already have access to in order to generate summaries and answer questions, in accordance with existing Microsoft 365 Copilot data handling, permissions, and security controls. Does the change introduce or significantly modify AI or ML capabilities that interact with customer data?Yes. This update introduces Copilot chat capabilities within OneNote Mobile, allowing generative AI to analyze note content that the user has permission to access. Does the change provide end users a new way of interacting with generative AI?Yes. Users can interact with generative AI through the Copilot chat pane in OneNote Mobile to summarize content and ask questions about their notes. -
(Updated) Create sales pitches with Copilot in PowerPoint
MC1521609 · stayInformed · normal · Updated 11/06/2026 16:54
Services: Microsoft 365 apps
Read message
Updated November 3, 2026: We have updated the timeline. Thank you for your patience. [What and Why:] We are introducing a new Copilot skill in PowerPoint that helps users create customer-facing sales pitch presentations. Users can use this skill for scenarios such as a first customer meeting, warm-lead product introduction, industry-specific pitch, or internal sales enablement. The skill helps users shape a commercial story around the audience, opportunity, key messages, supporting evidence, and recommended next step. [Rollout Schedule:] General Availability (Worldwide): We began rolling in late October 2026 and expect to complete by late November 2026 (previously late October). [Impact on Your Organization:] Who is affected: Users with access to Copilot in PowerPoint. Platforms/Services: Microsoft 365 apps (PowerPoint on Win32, Mac, and Web) What will happen: Users will be able to use a scenario-specific skill to create more structured sales pitch presentation drafts. This can help sales and customer-facing teams reduce the manual work needed to organize customer context, key messages, proof points, and next steps. [Action Required/Recommendations:] No admin action is required. You may want to inform users that this new Copilot skill is becoming available in PowerPoint on Win32, Mac, and Web. [Compliance considerations:] No compliance considerations identified. Review as appropriate for your organization. -
Microsoft Online Services Subprocessor Disclosure Update
MC1540526 · stayInformed · normal · Updated 11/06/2026 02:59
Services: Microsoft 365 suite
Read message
A Data Privacy message regarding your organization is available within Message Center. The contents of this message can be accessed within Message Center by a Global Administrator or someone designated as a Message Center Privacy Reader. Please sign in to Admin Center to view the details of this message in the M365 Message center. -
Microsoft SharePoint Online and OneDrive for the web: Updated search experience with Copilot Search
MC1540513 · planForChange · normal · Updated 11/05/2026 23:11
Services: SharePoint Online, Microsoft OneDrive
Action required by: 01/18/2027 08:00
Read message
[What and why] We are updating the search experience in SharePoint Online and OneDrive on the web to align with the Copilot Search experience across Microsoft 365. This updated experience allows users to search using natural-language prompts and combines relevant search results, AI-generated summaries with source references, and filters. By bringing SharePoint and OneDrive onto a common search interface, we are providing a more consistent and familiar search experience across Microsoft 365. [Rollout schedule] Frontier Preview (Worldwide): Rollout began in mid-October 2026 and is expected to complete by mid-January 2027. General Availability (Worldwide): Rollout begins in mid-January 2027 and is expected to complete by mid-April 2027. [Impact on your organization] Who is affected Users who search for content in SharePoint Online and OneDrive on the web Platforms and services SharePoint Online OneDrive on the web What will happen Users will see a modernized search experience aligned with Copilot Search across Microsoft 365. Please note that, while the core experience is shared, some AI-powered capabilities are available based on licensing. SharePoint Online and OneDrive on the web will use a common search interface, providing a more consistent experience regardless of where users begin their search. During the Frontier Preview period, SharePoint Online and OneDrive on the web will provide an opt-out option if users determine a critical search feature they rely on is unavailable. Modernized search experiences in SharePoint and OneDrive [Action required and recommendations] No significant deployment work is required. We recommend that you test any custom search experiences or integrations that may be affected by the updated search experience. If your organization needs more time to prepare for this change, options are available to defer the new experience at the tenant and individual site level. [Learn more] We will publish new documentation prior to General Availability release. [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
(Updated) Microsoft Teams: New chat sections for muted and meeting chats
MC1269864 · planForChange · normal · Updated 11/05/2026 21:51
Services: Microsoft Teams
Read message
Updated November 5, 2026: We have updated the timeline. Thank you for your patience. [Introduction] Microsoft Teams is introducing two new system chat sections called Muted chats and Meeting chats. These sections allow users to organize their chat and channels list by grouping muted conversations and meeting chats into dedicated sections that users can turn on or off. The new Meeting chats section will replace the Meeting chats filter, that was previously available at the top of the chat and channel list. This message is associated with Microsoft 365 Roadmap ID 559605. [When this will happen] General Availability (Worldwide, GCC, GCC High, DoD): Rollout begins in early January 2027 (previously early November 2026) (previously mid-October) and is expected to complete by late January 2027 (previously mid-November 2026). [How this affects your organization] Who is affected All Microsoft Teams users in Microsoft 365 tenants, including Worldwide, GCC, GCC High, and DoD What will happen Users may see up to two new system sections in their Teams chat and channels list: Muted chats sectionEnabled by default. Muted chats that are not in Favorites or user‑created sections automatically move to this section. The section appears at the bottom of the chat list. Unread chats continue to appear bold. Meeting chats sectionDisabled by default. When enabled by the user, meeting chats that are not in Favorites or user‑created sections automatically move to this section. The section appears below the main chats list. Unread chats continue to appear bold and contribute to badge counts. Chats in Favorites or user‑created sections are not moved. Users can drag and drop these sections to reorder them. There are no admin controls for these sections. [What you can do to prepare] No admin action is required. You may want to: Inform users that new chat sections are available and that they can turn them on or off. Notify helpdesk staff that muted chats may appear in a separate section by default. Direct users to Settings > Chats and channels to manage these sections. [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
Microsoft Teams: Decline incoming mobile calls with a message
MC1540349 · stayInformed · normal · Updated 11/05/2026 21:22
Services: Microsoft Teams
Read message
[What and why] Microsoft Teams mobile users will be able to decline an incoming Teams call and send a message to the caller at the same time. This gives users a faster way to communicate their availability without answering the call or separately navigating to chat. From the incoming call screen, users can select Message and choose a predefined response or select Custom to compose a personalized response in the relevant Teams chat. [Rollout schedule] General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out in early December 2026 and expect to complete by mid-December 2026. [Impact on your organization] Who is affected Microsoft Teams mobile users who receive eligible Teams-to-Teams calls and have an associated Teams chat available for the response Platforms and services Microsoft Teams mobile What will happen Once this feature is available: Users will see a new Message option on the incoming call screen. Users can choose a predefined response, such as “Can I call you later?”, “I’m on my way.”, or “Sorry, I can’t talk right now.” Selecting a predefined response will decline the call and immediately send the selected message to the caller in Teams chat. Users can select Custom to decline the call and open the relevant Teams chat to compose a personalized response. The response will appear in Teams chat so users can continue the conversation after the call is declined. This capability will not apply to PSTN, anonymous, or interoperability calls where there is no corresponding Teams chat to receive the message. Existing options to accept or decline an incoming call will not change. The feature will become available automatically as it rolls out to eligible users. iOS experience Screenshot 1 - IOS view 1: Screenshot 2 - IOS view 2: Screenshot 3 - IOS view 3: Android experience Screenshot 4 - Android view 1: Screenshot 5 - Android view 2: Screenshot 6 - Android view 3: [Action required and recommendations] No admin action is required before rollout. We recommend informing your help desk and users about the new Message option, particularly users who frequently handle Teams calls from their mobile devices. [Compliance considerations] This change provides a new way for users to communicate by allowing a user declining an eligible Teams call to send a predefined or custom message to the caller through Teams chat. Review this change as appropriate for your organization. -
Microsoft SharePoint: Data access governance report for group permissions
MC1540348 · stayInformed · normal · Updated 11/05/2026 21:21
Services: SharePoint Online
Read message
[What and why] We are introducing a new Data access governance report in the SharePoint admin center that allows SharePoint administrators to identify all sites accessible to a given group and the extent of that access. Groups with broad membership, including groups created for vendors, can expose sensitive content to unintended recipients. This report helps administrators investigate potential exposure and verify group permissions. [Rollout schedule] General Availability (Worldwide, GCC, GCC High, DoD): Rollout will begin in late November 2026 and is expected to complete by early December 2026. [Impact on your organization] Who is affected SharePoint administrators responsible for managing and reviewing site permissions. Platforms and services Microsoft SharePoint admin center Data access governance What will happen SharePoint administrators will be able to use the new report to identify all sites accessible to a given group. The report will show the extent of the group's access to those sites. Administrators can use the report to investigate potential exposure of sensitive content and to review group permissions before assigning Copilot licenses. Data access governance page [Action required and recommendations] We recommend that you: Review your current SharePoint site permissions configuration to identify potential exposure. Notify your SharePoint administrators about the new reporting capability in the SharePoint admin center. Update your internal documentation and workflows to reflect this change. [Learn more] Data access governance reports - get site permission report for given users - SharePoint in Microsoft 365 | Microsoft Learn [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
Action required: Update permissions for Exchange Online Admin API
MC1540345 · planForChange · normal · Updated 11/05/2026 21:20
Services: Exchange Online
Read message
[What and Why:] Microsoft is updating the authorization model for Exchange Online Admin API v2.0 by introducing dedicated API permissions. This change provides a clearer permission model for applications accessing Exchange Online administrative endpoints and supports the ongoing modernization of Exchange Online administration, including migration from Exchange Web Services (EWS). The Exchange Online Admin API v2.0 endpoints are not being retired. Only the permissions used to access them are changing: Exchange.ManageV2 is being replaced by Exchange.AdminAPI.Manage. Exchange.ManageAsAppV2 is being replaced by Exchange.AdminAPI.ManageAsApp. Applications using the affected permissions must transition to the corresponding new permissions to maintain uninterrupted access. [Rollout Schedule:] Worldwide: New permissions become available November 1, 2026. Complete migration by November 30, 2026. Existing permissions are deprecated December 1, 2026. GCC, GCC High, DoD: Rollout begins in November 2026, with existing permissions deprecated January 1, 2027. [Impact on Your Organization:] Who is affected: This change affects organizations that develop, own, or manage applications accessing Exchange Online Admin API v2.0 using Exchange.ManageV2 for delegated access or Exchange.ManageAsAppV2 for application-only access. If your organization does not use either permission, no action is required. Platforms/Services: Exchange Online Exchange Online Admin API v2.0 Microsoft Entra application permission and consent configuration What will happen: Applications must transition to Exchange.AdminAPI.Manage or Exchange.AdminAPI.ManageAsApp, as applicable. Administrators must grant consent to the new permissions where required. Existing Exchange Online RBAC requirements continue to apply. Exchange Online Admin API v2.0 endpoint URLs, API version, and supported operations are not changing as a result of this update. Applications relying exclusively on the retired permissions after the applicable deprecation date will no longer be able to access the APIs. Action Required/Recommendations: Identify affected applications. Review applications using Exchange.ManageV2 or Exchange.ManageAsAppV2. Configure the new permissions. Add the corresponding Exchange.AdminAPI.Manage or Exchange.AdminAPI.ManageAsApp permission. Grant administrator consent. Ensure the required new permissions are approved. Verify Exchange RBAC assignments. Confirm that the application or delegated user has the necessary Exchange roles. Validate API functionality. Test affected workflows using the new permissions before removing the existing permissions. Remove the retired permissions. After successful validation, remove the old permissions from the application configuration. Update explicit permission references. Update configurations, scripts, or consent workflows that reference the existing permission names. Check third-party applications. Contact your application provider to determine whether an update is required. For more information, see Authentication and authorization for the Exchange Online Admin API. [Compliance considerations:] No compliance considerations identified, review as appropriate for your organization. -
Action required: Exchange Online Admin API MailboxFolderPermission response update
MC1540342 · planForChange · normal · Updated 11/05/2026 21:18
Services: Exchange Online
Read message
[What and why:] Microsoft is updating the Exchange Online Admin API v2.0 MailboxFolderPermission endpoint to return the User property as a structured object instead of a display-name string. The new response includes DisplayName, Name, and PrimarySmtpAddress, helping applications more reliably identify users with similar or identical display names and supporting mailbox folder permission management and EWS migration scenarios. [Rollout schedule:] Rollout will begin and is expected to complete in early November 2026. [Impact on your organization:] Who is affected: Organizations with applications or third-party solutions that use the Exchange Online Admin API v2.0 MailboxFolderPermission endpoint and process the User property. Platforms/Services: Exchange Online Admin API v2.0, specifically the MailboxFolderPermission endpoint. What will happen: The User property will change from a string to a structured object. The object will contain DisplayName, Name, and PrimarySmtpAddress. The endpoint URL and API version will not change. Applications that expect User to be a string may experience parsing errors or unexpected behavior after the change. Applications can use PrimarySmtpAddress to more reliably distinguish between users with similar display names. Current response: { "User": "<display name>" } New response: { "User": { "DisplayName": "...", "Name": "...", "PrimarySmtpAddress": "..." } } [Action required/recommendations:] Action is required if your organization uses the MailboxFolderPermission endpoint and processes the User property. Before rollout: Review applications that read or process the User property. Update response handling to process User as a structured object instead of a string. Where appropriate, use PrimarySmtpAddress to identify the user associated with a mailbox folder permission. Test permission retrieval, user identification, and mailbox folder permission management workflows. Update dependent integrations that store, consume, or forward the User property. If you use a third-party solution that manages mailbox folder permissions, contact the solution provider to determine whether an update is required. For more information, see Exchange Online Admin API overview. [Compliance considerations:] No compliance considerations identified, review as appropriate for your organization. -
Microsoft Planner: Planner capabilities in Copilot Cowork through the Planner Plugin
MC1540339 · stayInformed · normal · Updated 11/05/2026 21:16
Services: Planner
Read message
[What and why] The Planner Plugin connects Microsoft Planner to Copilot Cowork, helping users understand their priorities, get help completing tasks, and keep their plans current. Cowork can use Planner task notes, checklists, and attachments to research, draft, analyze, and create deliverables. It can also turn existing content into plans, generate visual status reports, and use Planner context for work across Microsoft 365. Users review and approve changes before Cowork updates Planner. [Rollout schedule] General Availability (Worldwide): We began rolling out in late October 2026 and expect to complete by late November 2026. The experience is available now in Frontier, with general availability targeted for November 2026. [Impact on your organization] Who is affected Users with an active Microsoft 365 Copilot license, access to Copilot Cowork and Microsoft Planner, and permission to use the Planner Plugin Platforms and services Microsoft 365 Copilot Copilot Cowork Microsoft Planner What will happen Users can find the Planner Plugin, published by Microsoft Corporation, in Microsoft Copilot under Plugins > Cowork. After the plugin is available and any required account connection is completed, users can: Prioritize work: See assigned tasks across plans, identify overdue and upcoming work, and get recommendations about what to focus on. Get help completing tasks: Use task instructions, checklists, and attachments to research, draft, analyze, or create files. After approval, Cowork can update progress, complete checklist items, add deliverable links, and mark tasks complete. Create plans and tasks from existing content: Turn spreadsheets, documents, presentations, meeting notes, or goals into proposed plans and tasks for review and approval. Generate visual plan reports: Summarize progress, upcoming and overdue tasks, work by owner and bucket, progress toward goals, blockers, and recommended next steps. Work across Microsoft 365: Use Planner context to draft and send emails, schedule meetings, post Teams updates, and create documents, presentations, or spreadsheets. Users review and approve actions before Cowork takes them. Automate recurring work: Schedule task summaries and plan reports, or trigger requests from events such as emails and Teams messages. Changes to Planner still require approval. Administrators control plugin availability for their organization or for selected users and groups. Admin-deployed plugins are automatically acquired for targeted users. Users can enable or disable acquired plugins for their own Cowork conversations.The plugin acts within the signed-in user's existing Planner permissions and does not grant additional access. Screenshot 1 - Add the Planner Plugin: Screenshot 2 - Assigned tasks view: Screenshot 3 - Task execution view: [Action required and recommendations] To prepare: Confirm that intended users have Microsoft 365 Copilot licenses and access to Copilot Cowork and Microsoft Planner. In the Microsoft 365 admin center, go to Agents > Tools or Agents > All agents, find the Planner Plugin, and install it for the intended users or groups. Alternatively, configure availability so eligible users can acquire it themselves. Direct users to complete any required connector sign-in or consent. Administrators cannot sign in on their behalf. Consider updating your helpdesk and internal user guidance if you plan to make the plugin available. If the plugin is already deployed to the intended users, no additional deployment action is needed. Learn more Manage plugins for Copilot Cowork | Microsoft Learn Use plugins with Copilot Cowork | Microsoft Learn What you can do with Planner in Cowork | Microsoft Support [Compliance considerations] QuestionAnswer Does the change alter how existing customer data is processed, stored, or accessed?Yes. Copilot Cowork can use existing Planner data, including task notes, checklists, attachments, owners, and due dates, as context for completing work across Microsoft 365. Users review and approve actions before Cowork takes them. Does the change introduce or significantly modify AI/ML or agent capabilities that interact with or provide access to customer data?Yes. The Planner Plugin enables Copilot Cowork to use Planner context to research, draft, analyze, create deliverables, generate reports, and perform Planner-related actions. Does the change provide end users any new way of interacting with generative AI?Yes. Users can use Copilot Cowork with the Planner Plugin to prioritize work, complete tasks, create plans and reports, and perform work across Microsoft 365 using Planner context. Does the change include an admin control, and can it be controlled through Entra ID group membership?Yes. Administrators can control availability of the Planner Plugin for the organization or for specific users and groups through the Microsoft 365 admin center. Does the change allow a user to enable and disable the feature themselves?Yes. Users can enable or disable an acquired plugin for their own Copilot Cowork conversations through the Sources & Skills panel. -
Dynamics 365 Contact Center - Use role-based enforcement for recording and transcription downloads
MC1485169 · stayInformed · normal · Updated 11/05/2026 20:31
Services: Dynamics 365 Apps
Read message
Update: Release of this feature has been postponed; we will announce a new date in the future. We are announcing the ability to use role-based enforcement for recording and transcription downloads in Dynamics 365 Contact Center. How does this affect me? This feature helps organizations better protect sensitive customer communications by separating permissions to view recordings and transcripts from permissions to download them. Admins can assign new Dataverse security roles to prevent selected users from downloading recordings or transcripts while still allowing them to view and play back content as permitted by existing access. The two new Dataverse security roles that will be available are:Deny Recording Download Deny Transcription Download When either role is assigned to a user:The user can continue to view and play back recordings and transcripts as permitted by existing access. The user is blocked from downloading the corresponding artifact. Enforcement of these models is applied server-side across the Dynamics 365 Contact Center UI, public and internal APIs, and direct download URLs or integrations. Download requests will also be denied regardless of how they are initiated. Access control is driven entirely by Dataverse role assignment. The deny roles override implicit download behavior without affecting recording, transcription, or playback functionality. These controls help reduce the risk of unauthorized data export, support compliance and data governance requirements, and allow organizations to maintain operational visibility without allowing data removal. What action do I need to take? This message is for awareness, and no action is required. -
Power Automate - Information regarding the end of support for Copilot in the designer for cloud flows or agent flows.
MC1540258 · stayInformed · normal · Updated 11/05/2026 19:58
Services: Microsoft Power Automate
Read message
On November 30, 2026, Copilot in the designer for cloud flows or agent flows will have reached end of support. How does this affect me? Makers will no longer be able to use Copilot in the designer for cloud flows or agent flows. This deprecation doesn't delete, move, or change existing cloud flows or agent flows, including flows created or edited with Copilot. Makers will still be able to create, edit, test, and run cloud flows and agent flows in the designer, including starting from templates. Flows may also be edited directly in the designer, using the expression editor to write expressions, and using the flow checker and run history to troubleshoot. What action do I need to take? Please communicate as appropriate with your Power Automate and Copilot Studio users. To keep building and editing flows in natural language, please use the Power Automate plugin in a supported AI assistant, such as GitHub Copilot, or Connect to Microsoft Copilot Studio with MCP. -
Power Apps - Information regarding the end of support for AI-generated descriptions for model driven apps
MC1540110 · stayInformed · normal · Updated 11/05/2026 18:19
Services: Power Apps
Read message
Starting on November 30, 2026, AI-generated descriptions for model driven apps will have reached end of support. How does this affect me? The Create descriptions using AI option will no longer be available in the Publish dialog or the app designer Settings panel. Existing descriptions aren't affected, and you can continue to add or edit descriptions manually. For an AI-assisted option, the model app-builder skill outside Power Apps is available. What action do I need to take? This message is for awareness, and no action is required. -
Strengthen protection with timely Windows security updates
MC1540093 · stayInformed · normal · Updated 11/05/2026 18:00
Services: Windows
Read message
What and why AI is accelerating vulnerability discovery and analysis, increasing the importance of timely protection. Windows is expanding the use of AI-assisted capabilities across vulnerability discovery, remediation, validation, and post-release monitoring, while keeping human judgment and accountability central to engineering decisions. Once a security update and associated guidance are publicly available, attackers may be able to analyze the fix to better understand the underlying vulnerability and develop an exploit. Reducing the time between update release and deployment therefore helps reduce the period during which devices remain exposed to known, unpatched vulnerabilities. Rollout schedule There is no product rollout associated with this announcement. The guidance applies to the ongoing management and deployment of Windows security updates. Impact on your organization Keeping devices on supported Windows versions and shortening the time from release to deployment can help increase your secure posture. Modern servicing capabilities, including Windows Autopatch and hotpatch updates, can help you accelerate deployment while managing restart and operational requirements. Action required/recommendations Review your organization’s vulnerability management and Windows update practices, with particular attention to: Keeping devices on supported Windows versions and installing security updates promptly. Reducing unnecessary exposure and applying recommended security baselines. Maintaining endpoint detection and available mitigations. Establishing effective response and recovery practices. Reviewing update policies and deployment processes for opportunities to shorten the time between update release and deployment. Learn more: A new standard for vulnerability management in the AI era Compliance considerations No compliance considerations are identified. Review as appropriate for your organization. -
(Updated) Microsoft Defender for Office 365: Move email messages to quarantine with a new remediation action
MC1523084 · planForChange · normal · Updated 11/05/2026 17:48
Services: Microsoft Defender XDR
Read message
Updated November 5, 2026: We have updated the timeline. Thank you for your patience. [What and why] We are introducing Move to Quarantine, a new remediation action in Microsoft Defender for Office 365. It enables security teams to move potentially malicious email messages from users' mailboxes directly to Microsoft Defender quarantine. This provides a safer and more flexible way to contain suspicious messages that bypassed initial detection while preserving the ability to investigate, release, or permanently delete them later. This capability is available with Microsoft Defender for Office 365 Plan 2, including eligible Microsoft 365 subscriptions that include Plan 2. [Rollout schedule] General Availability (Worldwide): Beginning in late November 2026 (previously early November) and expected to complete by mid-January 2027 (previously mid-December) [Impact on your organization] Who is affected Organizations with Microsoft Defender for Office 365 Plan 2 Authorized security administrators who remediate email threats Platforms and services Microsoft Defender for Office 365, including: Threat Explorer Advanced Hunting Custom detection rules for email results Email entity and email summary experiences Unified Action Center What will happen Authorized administrators will see a new Move to Quarantine remediation action. When an administrator selects Move to Quarantine: Selected email messages are removed from user-accessible mailbox locations and placed in Microsoft Defender quarantine. Supported source locations include Inbox, Junk Email, Deleted Items, and recoverable soft-deleted locations. Admins can select the quarantine policy when using the Move to quarantine action. The selected policy determines how end users can interact with the quarantined messages. By default, quarantined messages are accessible only to admins. The remediation action and status are tracked in the Unified Action Center and related investigation experiences. Quarantined messages are identified with the quarantine reason Admin triggered. Authorized users can preview, release, or permanently delete quarantined messages according to the applicable quarantine policy. Releasing a message from quarantine delivers the message to the user's Inbox. The Search and Purge role is required to approve remediation actions. If one or more messages cannot be moved, eligible messages continue processing and administrators can review the results for partial failures. Screenshot 1 - Move to Quarantine option in the Take Action wizard: Screenshot 2 - Admin-triggered message and action details displayed in Advanced Hunting: The following existing functionality is unchanged: Existing remediation actions, including Move to Junk, Move to Deleted Items, Soft delete, and Hard delete Threat verdict assignments Existing remediation approval workflows and permissions Automated Investigation and Response (AIR) actions Microsoft Graph API capabilities Messages in unsupported locations, including hard-deleted messages and messages hosted in on-premises or external mailboxes [Action required and recommendations] No action is required to enable this capability. We recommend that you: Review your organization's quarantine policies. Verify that appropriate administrators have the required Search and Purge role. Update incident response playbooks and security operations procedures to include Move to Quarantine as a remediation option. Update internal training and operational documentation as appropriate. Inform security analysts and responders about the new containment action. Learn more (To be updated during rollout) Remediate malicious email that was delivered in Office 365 - Microsoft Defender for Office 365 | Microsoft Learn [Compliance considerations] QuestionAnswer Does the change alter how existing customer data is processed, stored, or accessed?Yes. Authorized administrators can move selected email messages from supported user mailbox locations into Microsoft Defender quarantine. Does the change modify how users can access, export, delete, or correct their personal data within Microsoft 365 services?Yes. Selected messages can be removed from user-accessible mailbox locations. Authorized users can later preview, release, or permanently delete quarantined messages according to the applicable quarantine policy. -
Microsoft Viva Engage: Improved shared message experience
MC1539003 · stayInformed · normal · Updated 11/05/2026 00:12
Services: Microsoft Viva
Read message
[What and why] We are improving the shared message experience in Microsoft Viva Engage to make it easier for users to discover, read, and participate in conversations shared by their colleagues. Shared messages will display richer previews of the original post, including formatted text, images, videos, and attachments. On Viva Engage web surfaces, users will be able to open and interact with the full conversation without losing their place in the feed. [Rollout schedule] General Availability (Worldwide): Rollout will begin in mid-November 2026 and is expected to complete by late November 2026. [Impact on your organization] Who is affected Users who view and interact with shared messages in Microsoft Viva Engage. Platforms and services Microsoft Viva Engage, with the conversation dialog experience available on web surfaces. What will happen Shared messages will display more of the original content, including formatted text, images, videos, and attachments. Users can select a shared message or View full conversation to open the original conversation in a dialog, including replies and reactions. Users can react, reply, and share from the conversation dialog without losing their place in the feed. Shared message previews will reflect changes to the original post, including edits. Users will continue to discover and share messages as they do today. This update focuses on improving how recipients experience shared content. Updated Viva Engage feed experience [Action required and recommendations] No changes to existing sharing workflows are required. We recommend informing users about the improved shared message experience and updating any existing training or support materials that demonstrate how shared messages appear in Viva Engage. [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
Microsoft Copilot Chat: Planner Agent task assignment, catch-up, and Copilot memory integration
MC1539002 · planForChange · normal · Updated 11/05/2026 00:11
Services: Planner
Action required by: 12/04/2026 08:00
Read message
[What and why] We are expanding Planner Agent in Microsoft Copilot Chat with task assignment, scheduled task catch-up, and Copilot memory integration. These improvements help users manage tasks and shared plans, identify outstanding work, and receive personalized responses. We are also improving support for larger plans, response quality, speed, and reliability. [Rollout schedule] General Availability (Worldwide): Rollout will begin in early December 2026 and is expected to complete by early December 2026. [Impact on your organization] Who is affected Users with an active Microsoft Copilot license who have access to Planner Agent. Administrators can manage Planner Agent availability through the Microsoft 365 admin center. Platforms and services Microsoft Copilot on the web Microsoft Copilot in Microsoft Teams Microsoft Planner What will happen Task assignment Users can assign tasks to one or more people in shared basic plans, including assigning multiple tasks at once. Users can reassign or remove assignees, view tasks grouped by person, and review proposed changes before saving them. Scheduled task catch-up Users can identify outstanding work, commitments, and items awaiting their input based on recent emails, chats, and meetings. Users can generate suggestions on demand or configure recurring schedules with optional email notifications when suggestions are ready for review. Suggested tasks include their sources and remain editable drafts until users save them to Planner. Users can modify, pause, or delete their schedules. Copilot memory Planner Agent can personalize responses using saved memories and preferences inferred from previous Copilot chats. Users can save, update, or delete memories through Planner Agent and review, delete, or turn off memories in Copilot personalization settings. Additional improvements Users can create plans without the previous 30-task limit and receive more complete responses for complex plans. Model selection, improved grounding in Microsoft 365 content, and performance enhancements provide more flexible, reliable responses. Users can find Planner Agent under Agents & Skills, pin it, or invoke it using @Planner Agent in Copilot chats. Limitations and default behavior Planner Agent supports personal tasks and shared basic plans, but not premium plans. It cannot delete tasks or undo changes. These improvements are enabled by default for users with access to Planner Agent. Users can run task catch-up on demand or configure recurring schedules. No recurring schedule is created automatically. AI-generated tasks, plans, and updates, including task assignments, remain drafts until users review and confirm them. Planner Agent uses only content that the signed-in user already has permission to access in Microsoft 365. [Action required and recommendations] No admin action is required. We recommend that you: Confirm that users have an active Microsoft Copilot license. Review Planner Agent access settings in the Microsoft 365 admin center. Inform users about the new capabilities, including optional scheduled task catch-up. Update internal documentation and training materials. Pin Planner Agent for easier access through Agents > All agents > Manage pinned agents in the Microsoft 365 admin center. Pinning requires the AI Administrator role and can take up to six hours to appear. [Learn more] How to access Planner Agent in Copilot? | Microsoft Support Planner Agent Capabilities and Limitations | Frequently Asked Questions | Microsoft Support Manage agents in the Microsoft 365 admin center | Microsoft Learn What is Planner Agent in Copilot? | Microsoft Support What's new in Microsoft Planner | September 2026 | Microsoft Community Hub [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
Microsoft 365 admin center: Project usage report retirement
MC1539001 · planForChange · normal · Updated 11/05/2026 00:10
Services: Project for the web
Action required by: 12/04/2026 08:00
Read message
[What and why] We are retiring the Project usage report (Project activity) from Reports > Usage in the Microsoft 365 admin center. Currently, the report shows how many users are active in the Project desktop client, Project Online, and Project for the web. Because Project Online and Project for the web have been retired, the Project usage report is also being retired. Starting December 4, 2026, the Project usage report will no longer be available in the Microsoft 365 admin center, and its historical data will no longer be accessible there. [Rollout schedule] General Availability (Worldwide, GCC): Rollout will begin in early December 2026 and is expected to complete by early December 2026. [Impact on your organization] Who is affected Administrators who use the Project usage report in the Microsoft 365 admin center. Platforms and services Microsoft 365 admin center Project usage report (Project activity) Project desktop client What will happen Administrators will no longer see the Project usage report under Reports > Usage. This change applies only to the Project usage report. The Project desktop client remains supported under its published lifecycle. Its features, support, and project files are not affected. Planner usage data will continue to be available through the Planner usage report. [Action required and recommendations] Export any Project usage data you want to keep before November 20, 2026, if you rely on this report. Use the Planner usage report in the Microsoft 365 admin center to view Planner and Planner premium activity. Update internal documentation or processes that refer to the Project usage report. [Learn more] Microsoft 365 Reports in the admin center: Planner activity -
Microsoft Outlook: Search within a selected folder
MC1539000 · stayInformed · normal · Updated 11/05/2026 00:09
Services: Exchange Online
Read message
[What and why] Users can now select a mail folder and scope Outlook search results to that folder. This update gives users more control over their searches by helping them narrow results to a specific folder. [Rollout schedule] General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out in mid-November 2026 and expect to complete in mid-November 2026. [Impact on your organization] Who is affected Users who use Outlook search Platforms and services Outlook What will happen Users will have folder selection options in Outlook search. Users can select a mail folder and scope search results to that folder. [Action required and recommendations] No action is required. [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
Microsoft 365 Copilot: Copilot connectors in Work IQ APIs
MC1538999 · stayInformed · normal · Updated 11/05/2026 00:08
Services: Microsoft 365 suite
Read message
[What and why] Copilot connectors will extend Work IQ beyond Microsoft 365 by making data and tools from connected enterprise systems available to AI agents through Work IQ APIs. Organizations can use their existing Copilot connector investments to build richer, more context-aware agentic experiences across Microsoft 365 and enterprise systems without requiring separate connector setup or management. Existing administrator controls, permissions, and governance policies for Copilot connectors will continue to apply. [Rollout schedule] General Availability (Worldwide): We will begin rolling out in late November 2026 and expect to complete by late December 2026 [Impact on your organization] Who is affected Organizations using Work IQ APIs and Copilot connectors Platforms and services Microsoft 365 Copilot, Work IQ APIs, and Copilot connectors What will happen Work IQ APIs will be able to use data and tools from connected enterprise systems through Copilot connectors. Organizations can use existing Copilot connector investments without separate connector setup or management. Existing administrator controls, permissions, and governance policies for Copilot connectors will continue to apply. [Action required and recommendations] No additional administrator action is required. Data sources already connected by users in Copilot Chat will automatically become available through Work IQ APIs, subject to existing permissions and administrator controls. Learn more Microsoft Work IQ API | Microsoft Learn [Compliance considerations] This change introduces or modifies AI or agent capabilities that can access customer data through Work IQ APIs using Copilot connectors to access connected enterprise systems. Existing permissions and governance controls continue to apply. -
Dynamics 365 Contact Center - Orchestrate conversation distribution with natural language playbooks
MC1538980 · stayInformed · normal · Updated 11/04/2026 23:42
Services: Dynamics 365 Apps
Read message
We are announcing the ability to orchestrate conversation distribution with natural language playbooks in Dynamics 365 Contact Center. This feature will be generally available by November 30, 2026. How does this affect me? Users will be able to configure natural-language playbooks to automatically manage conversation priority, overflow handling, representative assignment, and routing as conditions change throughout the conversation lifecycle. Key capabilities will include: Dynamic priority escalation: Adjust priority based on wait time, queue transfers, customer tier, and other conditions. Overflow handling: Trigger callbacks, route conversations to alternate queues, expand assignment eligibility, notify supervisors, or send contextual customer messages when defined conditions occur, including for direct inward dial calls. Preferred representative assignment: Reconnect customers with previously engaged or preferred representatives when available and within capacity, with fallback to another qualified representative. Bullseye routing: Expand the pool of eligible representatives over time based on skills, proficiency, teams, or other criteria. Users will configure playbooks through guided templates with built-in validation to identify conflicts before publication. Publishing a playbook will consume Copilot credits. No Copilot credits will be consumed during runtime when playbooks process conversations. Existing customers can continue using their current conversation orchestration playbooks, and new customers can create playbooks. What action do I need to take? Users will need to enable the conversation orchestration toggle to use this capability. Enabling the toggle will not consume Copilot credits. If you would like more information on this feature, please visit Orchestrate conversation distribution with natural language playbooks. -
Dynamics 365 Contact Center - Use bullseye routing with user groups to orchestrate conversations
MC1538962 · stayInformed · normal · Updated 11/04/2026 23:10
Services: Dynamics 365 Apps
Read message
We are announcing the ability to Use bullseye routing with user groups to orchestrate conversations in Dynamics 365 Contact Center. This feature will reach general availability by November 6, 2026. How does this affect me? This feature introduces a tiered assignment strategy that automatically expands the pool of eligible customer service representatives as conversation wait times increase. Admins can configure a bullseye routing playbook, allowing them to associate user groups with a queue and define wait time thresholds for each tier they add to that queue. Once configured, conversation orchestration monitors each conversation's wait time and automatically expands the eligible pool when thresholds are reached. What action do I need to take? Admins can enable bullseye routing under conversation orchestration to start configuring bullseye playbooks. If you’re already using bullseye routing under conversation orchestration, you can continue using your existing configurations without additional action. Copilot credits are used only when an admin publishes a playbook, which makes the configured orchestration logic active for use. Once published, the playbook can process any number of customer conversations without consuming additional Copilot credits. Saving a playbook as a draft or simply enabling Conversation Orchestration does not consume Copilot credits. If you would like more information on this feature, please visit Use bullseye routing with user groups to orchestrate conversations. -
(Updated) Microsoft Purview | eDiscovery: In-product diagnostics to troubleshoot common challenges
MC1515937 · stayInformed · normal · Updated 11/04/2026 22:12
Services: Microsoft Purview
Read message
Updated November 4, 2026: We have updated the timeline. Thank you for your patience. [What and Why:] Microsoft Purview eDiscovery is introducing three read-only diagnostic checks for case access, security filters, and hold-policy distribution. These checks help admins understand and troubleshoot common access, search-scoping, and hold-distribution issues directly in the product. This message is associated with Microsoft 365 Roadmap ID 565222 [Rollout Schedule:] Public Preview (Worldwide): We will begin rolling out in early December 2026 (previously late October) and expect to complete by mid-December 2026 (previously mid-November). General Availability (Worldwide): We will begin rolling out in late December 2026 (previously early December) and expect to complete by early January 2027 (previously mid-December 2026). General Availability (GCC): We will begin rolling out in late December 2026 (previously early December) and expect to complete by mid-January 2027. General Availability (GCC High): We will begin rolling out in late December 2026 (previously early December) and expect to complete by early February 2027. General Availability (DoD): We will begin rolling out in late December 2026 (previously early December) and expect to complete by late February 2027. [Impact on Your Organization:] Who is affected: eDiscovery admins. What will happen: Admins can use three read-only diagnostics to understand common issues with case access, search scoping, and hold-policy distribution. The diagnostics provide guidance without changing your organization's existing configuration. [Action Required/Recommendations:] No admin action is required at this time. Review your eDiscovery workflows and internal guidance if your organization uses the related Microsoft Purview capabilities. Learn about access and permission settings in eDiscovery cases (role/permission troubleshooting) Security-filter diagnostic Hold-distribution diagnostic [Compliance considerations:] No compliance considerations identified. Review as appropriate for your organization. -
(Updated) Outlook: Share Word, Excel and PowerPoint local files via the new Outlook for Windows
MC1245222 · stayInformed · normal · Updated 11/04/2026 17:31
Services: Exchange Online
Read message
Updated November 4, 2026: We have updated the timeline. Thank you for your patience. [Introduction] We’re adding support for sending locally stored Word, Excel, and PowerPoint files as email attachments directly through the new Outlook for Windows. This update streamlines the sharing experience and aligns with ongoing efforts to bring feature parity between classic Outlook for Windows and the new Outlook. This message is associated with Microsoft 365 Roadmap ID 557675. [When this will happen] General Availability (Worldwide): We will begin rolling out in mid-January 2027 (previously early November 2026) and expect to complete by mid-February 2027 (previously early December 2026). General Availability (GCC): We will begin rolling out in late February 2027 (previously mid-January) and expect to complete by late March 2027 (previously mid-February). [How this affects your organization] Who is affected Users working with locally stored Word, Excel, or PowerPoint files (not stored in OneDrive). Organizations adopting or transitioning to the new Outlook for Windows. What will happen Users can now share local Office files as email attachments directly through the new Outlook for Windows. Users will no longer need to rely on the classic Outlook for Windows to send local file attachments. This feature is ON by default. There is no change to existing admin controls or policies, and all existing Outlook/Exchange policies continue to apply. [What you can do to prepare] No admin action is required. To prepare your organization, you may: Inform help desk staff about this update to reduce support inquiries. Update your internal documentation if it references classic Outlook workflows. Encourage users to adopt the new Outlook for Windows if your organization is transitioning away from classic Outlook. [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
Microsoft Teams Rooms: Refreshed Analytics
MC1537497 · stayInformed · normal · Updated 11/03/2026 23:04
Services: Microsoft Teams
Read message
[What and why] We are refreshing the Analytics & Reports experience in the Microsoft Teams Rooms Pro Management portal with an updated design and simplified navigation. New Room analytics and Desk analytics navigation options will make it easier for admins to access workplace data and insights to help optimize spaces, improve operations, and make informed decisions. [Rollout schedule] General Availability (Worldwide): Rollout will begin in early December 2026 and is expected to complete by late January 2027. [Impact on your organization] Who is affected Admins using the Microsoft Teams Rooms Pro Management portal. Platforms and services Microsoft Teams Rooms Pro Management portal What will happen The Analytics & Reports experience will receive a refreshed design and simplified navigation. New Room analytics and Desk analytics entry points will appear in the left navigation. Existing reports will move to their respective Room analytics or Desk analytics pages. Recommended Actions will be renamed to Recommendations. [Action required and recommendations] No action is required. Admins can begin using the refreshed experience in the Microsoft Teams Rooms Pro Management portal when it becomes available. [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
Microsoft 365 Copilot: Discover featured AI Skills Navigator playlists in Learning Agent
MC1537495 · stayInformed · normal · Updated 11/03/2026 23:04
Services: Microsoft 365 Copilot Chat
Read message
[What and why] Microsoft is bringing featured playlists from AI Skills Navigator into Learning Agent in Microsoft 365 Copilot. Featured playlists bring related learning resources together around a role, product, or skill. Users can discover these structured collections through natural language conversations in Learning Agent, helping them spend less time searching individual learning resources and more time building practical AI skills. Users can discover featured playlists with prompts such as: What playlists can help me build AI skills for sales? Find a playlist that helps me create better marketing campaigns with AI. Recommend some playlists to help me do code reviews faster using AI. Find me some playlists that help me manage my company's AI costs better. Show me some playlists on how I can get more done at work using agents. [Rollout schedule] General Availability (Worldwide): Beginning in mid-November 2026 and expected to complete by mid-November 2026 [Impact on your organization] Who is affected Users in organizations where AI Skills Navigator is enabled Platforms and services Microsoft 365 Copilot Copilot Chat Learning Agent AI Skills Navigator What will happen Users can ask Learning Agent for featured playlist recommendations through natural language conversations: Featured playlists provide curated sequences of related learning content aligned with a role, product, or skill Featured playlists are included in Learning Agent when AI Skills Navigator is enabled for your organization Playlist recommendations won't appear if either Credentials or Microsoft YouTube videos is turned off in your AI Skills Navigator settings [Action required and recommendations] No action is required. If your organization uses AI Skills Navigator, review your AI Skills Navigator settings. Playlist recommendations won't appear if either Credentials or Microsoft YouTube videos is turned off. [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
Attention needed: Your tenant will be auto enabled for the new Microsoft Defender RBAC model
MC1537494 · planForChange · normal · Updated 11/03/2026 23:03
Services: Microsoft Defender XDR
Action required by: 12/02/2026 08:00
Read message
[What and Why:] Microsoft Defender role-based access control (Defender RBAC), the unified permissions model for Defender, is becoming the single access model for all Defender and Sentinel portal experiences. This will happen in a phased roll-out. First, your existing roles will be imported into the new RBAC model, giving you time to review and adjust them during the notification period. Following this period, the new Defender RBAC will be activated automatically for the in-scope workload(s), approximately 30 days after the in-portal notification date. The new Defender RBAC offers more extended access management capabilities, including: A single access management system to manage all roles and permissions across all workloads. Scoping capabilities across device groups, cloud, identity, and Sentinel. Future-proof assignments that will allow you to include future permissions and workloads. A prerequisite for newly introduced offerings, such as Perception. This change applies to Microsoft Defender and Microsoft Sentinel. Permissions for Microsoft Purview, Exchange Online, Microsoft Entra directory roles, Privileged Identity Management, and Azure resources (not related to Microsoft Sentinel) remain unchanged. In addition, if you are using PowerShell with Microsoft Defender for Office 365, this will continue to work as is. Workloads: The portal will identify which workloads will be enabled automatically and their activation dates. How you will be notified: Notification banner: A notification will be displayed in the Microsoft Defender portal informing customers that the specified workload(s) will transition to the new RBAC model. Legacy roles are automatically imported. The notification banner and role import mark the beginning of the customer notification period before automatic activation. Activation date: Beginning approximately 30 days after the notification date, the new Defender RBAC will be enabled automatically for the specified workload(s). Customers can review imported role assignments and prepare for the transition during this period. The in-portal banner in the Microsoft Defender portal (‘Permissions and roles’ page) will confirm activation. [Rollout Schedule:] Global: We will begin rolling out early December 2026 and expect to complete by late January 2027. [Impact on Your Organization:] Your existing roles, if applicable, will be automatically imported into the new Defender RBAC. Because the new RBAC is not yet active on your tenant for the workloads indicated, this import has no operational impact until activation. You may review and adjust the imported roles at any time from the Microsoft Defender portal. You may also re-run the import manually. Existing roles and permissions are automatically mapped. For more information on mapping, please see here. At the end of the notification period, the new Defender RBAC will be activated automatically for the in-scope workload(s). After activation, authorization for Defender/Sentinel portal experiences defaults to the new RBAC roles; legacy role assignments are no longer required to operate those portal experiences. Opt-out: Self-service opt-out is available after activation. Go to the ‘workload settings’ control in Defender RBAC to instantly revert to your legacy system if needed. If you are using APIs to configure your roles and permissions, please transfer to using the new Defender RBAC API Delegated access (B2B/GDAP) or Multi-Tenant Management: remains unchanged. Roles that had assignments to B2B/GDAP users/groups will be included in the automatic import. Entra directory roles are unchanged. Global Administrator, Security Administrator, Security Operator, and Security Reader continue to grant access to the Microsoft Defender portal as they do today. These roles will now map to Defender RBAC permissions as per the mapping referenced earlier. For more information on this mapping, please see here. https://learn.microsoft.com/en-us/defender-xdr/compare-rbac-roles Azure RBAC continues to govern Azure resources, including Logic Apps and Workbooks. Microsoft Sentinel specific workspace permissions (Sentinel Reader, Responder, Contributor roles) do get enabled automatically to Defender RBAC. Email and Collaboration permissions and Exchange Online permissions continue to govern Exchange Online and Microsoft Purview scenarios. They are no longer required to operate Microsoft Defender for Office 365 portal experiences once Defender RBAC is active. Applicability for Microsoft Defender for Office 365: This update applies to organizations with Microsoft Defender for Office 365 Plan 2, whether licensed separately or included in an eligible subscription, such as Microsoft 365 E5. [Action Required/Recommendations:] From the moment of the in-portal notification, review the auto-imported RBAC role assignments in the Microsoft Defender portal (Permissions -> Roles). Validate that each user has the expected RBAC role and scope. Adjust assignments as needed. If any role assignments need to be updated, you can do so directly in the role assignment, even if Defender RBAC is not yet activated for that workload. When using scoping: device groups continue to work as they do today. In addition, Defender RBAC allows you to use Cloud Scopes, Sentinel Scopes, and Identity Scopes. Update internal documentation and runbooks to reflect the new RBAC model. Additional information: Microsoft Defender RBAC overview Review and manage imported RBAC roles [Compliance considerations:] This update changes the permissions/access-control model for Microsoft Defender and Microsoft Sentinel only; Microsoft Purview, Exchange Online, Microsoft Entra directory roles, Privileged Identity Management, and Azure resource permissions are unchanged. Review imported role assignments against your organization change-management and access-governance requirements before activation. -
Intelligent call delegation is planned to change from Frontier public to public preview (Ring 3.6) as early as Nov 17th
MC1537490 · planForChange · normal · Updated 11/03/2026 22:58
Services: Microsoft Teams
Read message
[What and Why:] Intelligent call delegation is moving from Frontier public preview to public preview (Ring 3.6) beginning as early as November 17, 2026. This capability uses AI to screen incoming calls, gather context, and help users decide when to engage. It can also schedule follow-up appointments via Microsoft Bookings. [Rollout Schedule:] Public Preview (Worldwide): Mid-Nov 2026 to Mid Dec 2026. General Availability (Worldwide): Mid-January 2027 to late January 2027. (Dates are subject to change) [Impact on Your Organization:] Who is affected: Tenants that used Intelligent call delegation during Frontier preview and tenants planning to use it in Ring 3.6 public preview. Platforms/Services: Microsoft Teams Microsoft 365 Copilot (Premium) Microsoft Bookings integration What will happen: Intelligent call delegation remains available as an AI-powered call screening and context assistant. Public preview uses usage-based billing (UBB) with Copilot Credits. Billing does not begin until an admin configures spending in the Microsoft 365 admin center. If spending is not configured, tenants coming from Frontier preview will no longer have incoming calls screened by this feature. [Action Required/Recommendations:] If your organization plans to continue using Intelligent call delegation in public preview, complete the following: Create a spending policy in Microsoft 365 admin center using guidance in Managing AI experiences enabled by usage-based billing. Under agents and services, select Intelligent call delegation and clear other selections. Choose the intended user/group scope before assigning the policy. Confirm users are licensed with Microsoft 365 Copilot USL where required. [Compliance considerations:] Does the change introduce or significantly modify AI/ML or agent capabilities that interact with or provide access to customer data?Yes. Intelligent call delegation is an AI-powered capability that screens calls and gathers context to assist users. Does the change include an admin control, and can it be controlled through Entra ID group membership?Yes. Admins must configure usage-based billing policy scope in MAC and can target users/groups through existing admin policy controls. -
(Updated) Private tasks now stored in your private plan in Planner
MC1488845 · planForChange · normal · Updated 11/03/2026 21:52
Services: Planner
Read message
Updated November 3, 2026: We have updated the timeline. Thank you for your patience. [What and Why:] Microsoft is updating how private tasks are stored in Microsoft Planner. Beginning in December 2026, private tasks created in Planner and Planner-powered experiences will be stored in a user's own private Planner plan instead of the Microsoft To Do task store. This enables richer Planner capabilities, such as labels and task history, while maintaining the same private experience. Private tasks remain visible only to the task owner and cannot be shared or assigned to others. This change aligns private task management with the Planner platform while preserving enterprise compliance and security protections. [Rollout Schedule:] General Availability (Worldwide): Rollout begins in early December 2026 (previously November). Expected completion: late December 2026 (previously November). [Impact on Your Organization:] Who is affected: Users who create and manage private tasks in Planner and Planner-powered experiences. Platforms/Services: Microsoft Planner Planner on the web Planner-powered experiences Microsoft To Do What will happen: New private tasks will be stored in a private Planner plan. Users will continue to see existing private tasks in Planner My Tasks. Private tasks remain private to the task owner. Private tasks cannot be shared or assigned to others. Additional Planner task capabilities, such as labels, will become available. New private tasks created in Planner will no longer appear in Microsoft To Do. Existing compliance and security protections continue to apply. The feature is enabled automatically. No administrator action is required for deployment. [Action Required/Recommendations:] No action is required. You may want to: Inform support and help desk teams of the change. Review any internal documentation that references Planner private tasks appearing in Microsoft To Do. Review the Microsoft Planner service description and admin documentation. Communicate the updated experience to affected users. [Compliance considerations:] Does the change store new customer data, if so, where, and is the data cached or permanently stored?Yes. New private tasks will be stored in a user's private Planner plan instead of the Microsoft To Do task store. Does the change alter how existing customer data is processed, stored, or accessed?Yes. Private task storage changes from Microsoft To Do to Planner for new private tasks. Existing private tasks remain visible in Planner My Tasks. Does the change modify retention policies, holds, or deletion workflows?Yes. Organizations should validate any retention, discovery, reporting, or governance processes that depend on Microsoft To Do storage. Does the change alter how admins can monitor, report on, or demonstrate compliance activities?Yes. Admins may need to account for the storage change from To Do to Planner in reporting or governance processes. Does the change provide end users any new way of interacting with generative AI?No. This is a Planner task storage and experience update, not a generative AI capability. -
(Updated) Updated My Task experience in Planner
MC1488844 · planForChange · normal · Updated 11/03/2026 21:49
Services: Planner
Read message
Updated November 3, 2026: We have updated the timeline. Thank you for your patience. [What and Why:] Microsoft is introducing a redesigned My Tasks experience in Planner to help users more easily identify, prioritize, and manage their work. The updated experience provides clearer navigation, improved task organization, and streamlined task creation workflows, enabling users to create and manage tasks more efficiently without leaving their current context. This supports improved personal productivity by helping users focus on the work that requires their attention and reducing friction in everyday task management. [Rollout Schedule:] General Availability (Worldwide): Rollout will occur from early through late December 2026 (previously November). [Impact on Your Organization:] Who is affected: All users who access Microsoft Planner and use the My Tasks experience. Platforms/Services: Microsoft Planner Planner on the web Planner task management experiences What will happen: Users will see an updated My Tasks interface in Planner. Navigation within My Tasks will be simplified and easier to understand. Task organization and prioritization experiences will be updated. Users will be able to create tasks through streamlined workflows without leaving their current context. Existing tasks and task data will remain available. No migration or user data movement is required. The feature will be enabled automatically as part of the service rollout. No changes to existing admin policies or configurations are required. [Action Required/Recommendations:] No action is required. You may want to: Inform helpdesk and support teams of the upcoming user interface changes. Communicate the updated Planner experience to end users who regularly use My Tasks. Review any internal training materials or screenshots that reference the current experience and update them as needed. Monitor user feedback during rollout and adoption. [Compliance considerations:] No compliance considerations identified. Review as appropriate for your organization. -
Power Automate - Information regarding the end of support for Describe it to design it
MC1537406 · stayInformed · normal · Updated 11/03/2026 21:24
Services: Microsoft Power Automate
Read message
On November 30, 2026, Describe it to design it in Power Automate will have reached end of support. How does this affect me? Makers in your organization will no longer be able to create new cloud flows using Describe it to design it. This retirement doesn't delete or move existing flows. Makers can still create and edit flows in the visual designer and start from templates. What action do I need to take? For makers who want to create flows from descriptions, please use the Power Automate plugin in an organization-approved coding assistant, such as GitHub Copilot CLI. For perquisites and installation instructions please visit, Get started with the Power Automate plugin for GitHub Copilot CLI and Claude Code. Makers may also manually create flows or create flows from a template. -
(Updated) Microsoft Teams: QR code protection for messages from external users
MC1470410 · stayInformed · normal · Updated 11/03/2026 18:24
Services: Microsoft Teams
Read message
Updated November 3, 2026: We have updated the timeline. Thank you for your patience. [What and why] Microsoft Teams is introducing additional protection for QR codes shared by external users in Teams messages. To help reduce the risk of phishing and fraud, images containing QR codes from external senders will be obscured by default. Users can choose to reveal the image before viewing or scanning the QR code. This security enhancement promotes safer interactions with content received from external users while maintaining flexibility for trusted communications. [Rollout schedule] Targeted Release: Beginning in mid-October 2026 (previously early October) and expected to complete in mid-October 2026 (previously early October) General Availability (Worldwide): Beginning in late October 2026 (previously mid-October) and expected to complete by end of November 2026 (previously late October) [Impact on your organization] Who is affected Organizations that allow communication with external users in Microsoft Teams. Users who receive Teams messages from external senders. Teams administrators and support teams that manage external collaboration policies. Platforms and services Microsoft Teams Teams desktop Teams web Teams mobile What will happen Images containing QR codes sent by external users will be blurred by default in Teams messages. Users can reveal the image if they trust the sender and want to view or scan the QR code. The blurred image does not indicate that Microsoft Teams has determined the QR code to be malicious. The protection is applied automatically to QR code images received from external senders. No administrator configuration or policy changes are required. The feature will be enabled by default as part of the rollout. [Action required and recommendations] No admin action is required before rollout. We recommend that administrators: Inform users that QR code images from external senders may appear blurred by default. Remind users to verify the sender before revealing or scanning QR codes. Review existing user education materials related to phishing awareness, QR code safety, and external collaboration. Update internal help desk documentation to reflect the new user experience. Learn more: QR code obscuring in Microsoft Teams - Microsoft Teams | Microsoft Learn Make sure chats, links, and files are secure in Microsoft Teams | Microsoft Support [Compliance considerations] No compliance considerations identified, review as appropriate for your organization. -
(Updated) Microsoft Teams: Updated header and dashboard for chats and channels on mobile
MC1467357 · stayInformed · normal · Updated 11/03/2026 17:57
Services: Microsoft Teams
Read message
Updated November 3, 2026: We have updated the timeline. Thank you for your patience. [What and why] We're updating the Microsoft Teams mobile experience with a redesigned header and lightweight dashboard for chats and channels. This update brings key channel details, people, and pinned content into a single, intuitive experience, helping users find information and take action more quickly. The updated experience creates a more consistent navigation model across desktop and mobile, making it easier for users to move between chats and channels. [Rollout schedule] Targeted Release: Beginning in late September 2026 General Availability (Worldwide, GCC, GCC High, DoD): Beginning in early October 2026 and expected to complete by end of November 2026 [Impact on your organization] Who is affected Users who access Microsoft Teams on mobile devices. Platforms and services Microsoft Teams for mobile What will happen Users will see a redesigned header experience in chats and channels on mobile. A new lightweight dashboard will provide easier access to channel details, people, and pinned content. Navigation across chats and channels will become more consistent with the Teams desktop experience. The update is intended to help users get oriented and complete common tasks more quickly while using Teams on mobile. Screenshot 1 - Chat view: Screenshot 2 - Channel view: [Action required and recommendations] No action is required. You may want to: Notify users about the updated mobile experience. Review and update internal training or support documentation that references the current mobile navigation experience. Inform help desk and support teams of the upcoming change. [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
(Updated) Microsoft Teams: Admin policy to automatically block identified external meeting bots from joining meetings
MC1459141 · stayInformed · normal · Updated 11/03/2026 17:56
Services: Microsoft Teams
Read message
Updated November 3, 2026: We have updated the timeline. Thank you for your patience. [What and why] Microsoft Teams is introducing a new meeting protection policy that allows administrators to automatically block identified external meeting bots from joining Teams meetings. Today, Teams can identify meeting bots and provide visibility to organizers and administrators. With this update, organizations can strengthen meeting security by configuring Teams policies to automatically block detected external meeting bots from joining meetings. This gives administrators additional control over how identified bots are handled and can help reduce organizational risk. This message is associated with Roadmap ID 566201. [Rollout schedule] Targeted Release: Beginning in mid-September 2026 (previously early August) and expected to complete by late September 2026 (previously late August) General Availability (Worldwide): Beginning in early October 2026 (previously late August) and expected to complete by end of November 2026 (previously late October) [Impact on your organization] Who is affected Teams administrators who manage meeting policies and security controls. Meeting organizers and participants in organizations that choose to enable this policy. Platforms and services Microsoft Teams Teams admin center Teams meeting policies What will happen A new policy option will be added to the existing Manage bots meeting protection settings in the Teams admin center. Administrators will be able to configure Teams meeting policies to automatically block identified external meeting bots from joining meetings. When the setting is enabled: Identified external meeting bots will be prevented from joining meetings governed by the assigned policy. Existing bot detection and visibility experiences for organizers and administrators will continue to be available. The policy can be assigned to specific users or groups through existing Teams meeting policy management. Organizations that do not enable this setting will continue to use the current bot detection experience with no change to meeting participation behavior. Default state: Off. No changes occur unless an administrator enables the policy. [Action required and recommendations] No action is required unless you plan to use this capability. If you intend to enable automatic blocking of identified external meeting bots, we recommend that you: Review your organization's use of meeting bots and automated meeting applications. Evaluate the feature with a pilot group before broader deployment. Review existing Teams meeting policies and determine which users or groups should receive the policy. Update internal documentation and help desk guidance as appropriate. Communicate the change to meeting organizers and users who rely on automated meeting bots in their workflows. [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
(Updated) Microsoft Teams: Enhanced live captions settings and right-side panel view
MC1447682 · planForChange · normal · Updated 11/03/2026 17:54
Services: Microsoft Teams
Read message
Updated November 3, 2026: We have updated the timeline. thank you for your patience. [What and why] We're improving the live captions experience in Microsoft Teams to give users more flexibility when viewing captions and to simplify caption configuration during meetings. This update introduces a new right-side panel layout for live captions and consolidates caption settings into a single menu. This message is associated with Microsoft 365 Roadmap ID 567462. [Rollout schedule] Targeted Release: Beginning mid-August 2026 and expected to complete by late August 2026 General Availability (Worldwide): Beginning mid-September 2026 and expected to complete by end of November 2026 (previously end of October) General Availability (GCC, GCC High, DoD): Beginning mid-September 2026 and expected to complete by end of November 2026 (previously end of October) [Impact on your organization] Who is affected Teams meeting participants who use live captions, translated captions Organizations that have live captions, translated captions enabled through existing Teams policies and licensing Platforms and services Microsoft Teams calls, meetings, and events Windows, Mac, and web clients where live captions are supported What will happen After rollout, users will be able to: Display live captions in a new right-side panel: Continue using existing top, bottom, and pop-out caption layouts. Manage caption settings from a consolidated settings menu within the captions pane: Configure live captions to turn on automatically when they join meetings. Submit feedback on the live captions experience using thumbs-up and thumbs-down controls. The consolidated settings menu will include: Spoken language Translation language Caption display styles Profanity filtering Automatically turn on live captions The right-side panel provides an additional way to keep captions visible without overlapping meeting video or shared content. The synchronized translation language setting reduces the need for users to configure Interpreter and translated captions separately. The option to automatically turn on live captions is a user-level preference. When enabled, live captions will start automatically for that user in future meetings, subject to the meeting policies and feature availability configured by their organization. This update does not change existing administrator controls or policies for live captions, translated captions, or Interpreter. Users will only be able to access features permitted by their organization's licensing, service availability, and Teams policy configuration. [Action required and recommendations] No administrative action is required. We recommend that administrators: Notify support and help desk teams about the updated captions experience. Update internal documentation related to Teams meetings, accessibility features, and multilingual meetings. Review existing Teams meeting policies for live captions, translated captions, and Interpreter. Inform users that translation language selections will be shared across Interpreter and translated captions. Update support guidance for users who choose to automatically enable live captions for future meetings. The feature will be enabled automatically as rollout reaches your organization. Learn more Use live captions in Microsoft Teams meetings | Microsoft Support [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
(Updated) Microsoft Teams: Expanded presenter visibility in Manage what attendees see
MC1443518 · stayInformed · normal · Updated 11/03/2026 17:52
Services: Microsoft Teams
Read message
Updated November 3, 2026: We have updated the timeline. Thank you for your patience. [What and why] Microsoft Teams is expanding presenter visibility in Manage what attendees see for Teams events. Event organizers and producers can now drag and resize the presenter panel, allowing them to view more presenters simultaneously during event production. This improvement helps producers more easily monitor available presenters, streamline presenter transitions, and manage large events with greater efficiency. This message is associated with Microsoft 365 Roadmap ID 567467. [Rollout schedule] Targeted Release: Beginning mid-August 2026 and expected to complete by late August 2026 General Availability (Worldwide, GCC, GCC High, DoD): Beginning late August 2026 and expected to complete by end of November 2026 (previously end of October) [Impact on your organization] Who is affected Teams event organizers Teams event producers Users who manage live event production experiences in Microsoft Teams Platforms and services Microsoft Teams Teams events What will happen Users will be able to drag and resize the presenter panel in Manage what attendees see. The larger presenter panel can display more presenters at one time. Users can view more presenters at once, reducing the need to switch between pages when managing large events. Producers will have improved visibility into presenter availability during events. Presenter transitions can be managed more efficiently, particularly during large events with many presenters. This change is enabled automatically and does not require configuration. [Action required and recommendations] No admin action is required. You may want to: Inform event organizers and producers about the updated presenter management experience. Update internal training materials and event production guidance, if applicable. [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
(Updated) Microsoft Teams: Centralized notification settings for channels
MC1466307 · stayInformed · normal · Updated 11/03/2026 17:50
Services: Microsoft Teams
Read message
Updated November 3, 2026: We have updated the timeline. Thank you for your patience. [What and why] We are introducing centralized notification settings for channels in Microsoft Teams. Users will have a single location to view and manage notification preferences across their channels instead of configuring settings individually for each channel. This simplifies notification management and reduces the effort required to review and update settings. [Rollout schedule] Targeted Release: Beginning early October 2026 and expected to complete by early October 2026 General Availability (Worldwide): Beginning early October 2026 and expected to complete by late November 2026 (previously late October) [Impact on your organization] Who is affected All Microsoft Teams users Platforms/Services Microsoft Teams desktop and web What will happen Users will be able to access centralized channel notification settings in Microsoft Teams settings at Settings > Notifications and activity > Manage channel notifications. Notification settings will be organized in a team-to-channel hierarchy. Users will be able to review and update notification preferences for individual channels from a single location. Users will be able to filter channels to identify those with customized notification settings. The feature will be enabled by default. Existing channel notification settings will be preserved. No changes will be made to existing admin policies or tenant configurations. [Action Required/Recommendations] No admin action is required. We recommend: Informing users about this new capability. Updating internal Teams guidance or training materials if they include instructions for managing channel notifications. [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
(Updated) Microsoft Teams: Unblock users to send message while file is uploading in the background
MC1317836 · stayInformed · normal · Updated 11/03/2026 17:46
Services: Microsoft Teams
Read message
Updated November 3, 2026: We have updated the timeline. Thank you for your patience. [What and Why] Users are currently blocked from sending messages in Microsoft Teams while a file upload is in progress, which can disrupt real-time collaboration. With this update, file uploads will occur asynchronously in the background, allowing users to continue sending messages without interruption. This message is associated with Microsoft 365 Roadmap ID 560813. [Rollout Schedule] Targeted Release: Rollout will begin in early August 2026 (previously early July) and is expected to complete by mid-August 2026 (previously mid-July). General Availability (Worldwide): Rollout will begin in mid-August 2026 (previously mid-July) and is expected to complete by end of November 2026 (previously end of October). [Impact on Your Organization] Who is affected All Microsoft Teams users who send files in chats or channels Platforms/Services Microsoft Teams Desktop (Windows, Mac) Web Mobile (iOS, Android) What will happen Users will be able to send chat messages while files are uploading. File uploads will occur asynchronously in the background. The message input box will no longer be blocked during uploads. There are no changes to how files are stored or shared. Existing compliance, retention, and security policies remain unchanged. This feature will be enabled by default for all tenants. [Action Required / Recommendations] No action is required. Consider informing your users about improved file upload behavior in Teams chats. Update internal training or support documentation if you reference file-sharing workflows. [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
(Updated) Microsoft Teams: Breakout rooms now supported in meetings with up to 1,000 attendees
MC1330891 · stayInformed · normal · Updated 11/03/2026 17:45
Services: Microsoft Teams
Read message
Updated November 3, 2026: We have updated the timeline. Thank you for your patience. [Introduction] Microsoft Teams is expanding breakout room capacity to support larger meetings. With this update, breakout rooms can be used in meetings with up to 1,000 attendees, allowing organizers to run large meetings while still enabling smaller group collaboration. This change removes the need to limit meeting size in order to use breakout rooms. This message is associated with Microsoft 365 Roadmap ID 560320. [When this will happen] Targeted Release: Rollout begins in early July 2026 and is expected to complete by late July 2026. General Availability (Worldwide, GCC, GCCH, and DoD): Rollout begins in mid-August 2026 (previously July) and is expected to complete by end of November 2026 (previously end of October). [How this affects your organization] Who is affected Meeting organizers and participants using Microsoft Teams Microsoft 365 tenants What will happen Breakout rooms will be supported in meetings with up to 1,000 attendees. Organizers can create up to 100 breakout rooms per meeting. Organizers no longer need to limit meeting size to enable breakout rooms. The feature is enabled by default and respects existing Teams meeting policies. There is no change to the breakout room experience for meetings under the previous 300‑attendee limit. [What you can do to prepare] No action is required. Consider informing meeting organizers and training owners about the expanded breakout room capacity. Update any internal guidance or training materials that reference breakout room attendee limits. [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
(Updated) Microsoft Teams: Secure Reliable Transport (SRT) support for Teams meetings and events
MC1323270 · stayInformed · normal · Updated 11/03/2026 17:43
Services: Microsoft Teams
Read message
Updated November 3, 2026: We have updated the timeline. Thank you for your patience. [Introduction] Microsoft Teams town halls and live events will soon support Secure Reliable Transport (SRT), a secure and resilient video streaming protocol designed to deliver high‑quality, low‑latency video over the public internet. SRT will be available alongside Real‑Time Messaging Protocol (RTMP), the existing inbound streaming protocol commonly used with external encoders. Adding SRT provides event organizers with improved reliability and flexibility, including support for backup streams with automatic failover, to help ensure smoother delivery for high‑visibility broadcast events without increasing setup complexity. This message applies to Teams for Windows desktop and Teams for Mac desktop and is associated with Roadmap ID 554931. [When this will happen:] Targeted Release: Rollout begins in early June 2026 and is expected to complete by mid-June 2026 General Availability (Worldwide, GCC): Rollout begins in late June 2026 (previously mid-June) and is expected to complete by end of November 2026 (previously end of October) [How this affects your organization:] Who is affected: Organizations that host Microsoft Teams town halls or live events using external encoders Event producers and administrators responsible for configuring broadcast streams What will happen: Organizers can use SRT as an alternative to RTMP for inbound streaming Events can be configured with a primary and backup SRT stream with automatic failover Existing RTMP workflows remain supported and unchanged The feature is available by default; no admin policy changes are required No impact to users attending events [What you can do to prepare:]. Review encoder capabilities to confirm SRT support Ensure you have access to port 49891 and the domain *.rtmpingest.mcr.teams.cloud.microsoft. Update internal event‑production documentation to include SRT as a supported option Inform event production teams that a backup stream with automatic failover is now available for Teams town halls We’ve introduced an additional policy control for SRT-In in Teams Events. To enable users to access and use SRT-In, IT admins must explicitly allow the “SRT” setting in the AllowedStreamingMediaInput parameter within CsTeamsMeetingPolicy. Learn more: Manage RTMP-In for Teams meetings, webinars, and town halls - Microsoft Teams | Microsoft Learn (will be updated before Targeted Release begins) [Compliance considerations:] No compliance considerations identified, review as appropriate for your organization. -
(Updated) Microsoft Teams: New experience when users minimize the meeting window
MC1266027 · stayInformed · normal · Updated 11/03/2026 17:42
Services: Microsoft Teams
Read message
Updated November 3, 2026: We have updated the timeline. Thank you for your patience. [Introduction] We are improving the Microsoft Teams meeting experience when the active meeting window is minimized. This update helps users stay engaged in meetings while multitasking across other apps. With this change, users can perform key in-meeting actions—such as raising their hand and sending reactions—without restoring the full Teams meeting window. Users can also choose between two different minimized views, depending on how much meeting context they want to keep visible while they work. This change does not affect the experience when users are sharing their screen in a Teams meeting. This message applies to Teams for Windows desktop and Teams for Mac desktop. It is associated with Microsoft 365 Roadmap ID 557179. [When this will happen:] Targeted Release: Rollout begins mid-May 2026 (previously early May) and is expected to complete by late May 2026 (previously early May). General Availability (Worldwide): We expect to complete rollout by end of November 2026 (previously end of October). [How this affects your organization:] Who is affected: All users who join and participate in Microsoft Teams meetings. What will happen: When users minimize a Teams meeting window, a new minimized meeting experience appears automatically. Users can raise their hand and send reactions without restoring the full Microsoft Teams meeting window. Users can choose between two minimized views:Expanded view: Displays up to four participant videos. Compact view: Does not display participant video and takes up less screen space. The feature is enabled by default and does not require any admin configuration. There is no change to the meeting experience while screen sharing. [What you can do to prepare:] No action is required. Consider notifying users and helpdesk staff about the new minimized meeting views in Microsoft Teams. Update internal training or support documentation if it references Teams meeting window behavior. [Compliance considerations:] No compliance considerations identified, review as appropriate for your organization. -
(Updated) Microsoft Teams: Streaming switchboard for NDI sources in meetings and events
MC1521613 · stayInformed · normal · Updated 11/03/2026 17:40
Services: Microsoft Teams
Read message
Updated November 3, 2026: We have updated the timeline. Thank you for your patience. [What and why] A new streaming switchboard in Microsoft Teams will allow event producers to more easily manage and send NDI® sources to production software during Teams meetings and events. Event producers can individually select and stream up to eight NDI sources directly from a Teams meeting or event. [Rollout schedule] General Availability (Worldwide): Beginning in mid-November 2026 (previously early November) and expected to complete by mid-November 2026 [Impact on your organization] Who is affected Event producers who use NDI streaming in Microsoft Teams meetings and events Platforms and services Microsoft Teams What will happen Event producers will be able to individually select and stream up to eight NDI sources from a Teams meeting or event. To access the feature during a meeting or event, select More actions, then Streaming > Streaming switchboard. Admins must enable NDI streaming before users can use the feature. Users must turn on production capabilities in Teams before using NDI broadcast production. [Action required and recommendations] To prepare: Enable AllowNDIStreaming for the appropriate users through the CsTeamsMeetingPolicy cmdlet. Instruct affected users to turn on production capabilities in Teams. Learn more Allow broadcast production in Teams meetings with NDI and SDI hardware - Microsoft Teams | Microsoft Learn [Compliance considerations] QuestionAnswer Does the change add any integration to third-party software products, and if so, what?Yes. NDI® enables Microsoft Teams meeting content to be sent to production software. Does the change include an admin control, and can it be controlled through Entra ID group membership?Yes. Admins can control NDI® streaming through the AllowNDIStreaming setting in CsTeamsMeetingPolicy. The provided source does not specify whether the control can be managed through Entra ID group membership. Does the change allow a user to enable and disable the feature themselves?Yes. After an admin enables NDI streaming, users must turn on production capabilities in Teams. -
(Updated) Microsoft Teams: Two presenters can share their screens or windows simultaneously in meetings
MC1528014 · stayInformed · normal · Updated 11/03/2026 17:39
Services: Microsoft Teams
Read message
Updated November 3, 2026: We have updated the timeline. Thank you for your patience. [What and Why:] Two presenters can share a screen or window at the same time in a Teams meeting. Participants can see both shared content streams simultaneously, making it easier to compare and discuss content from different presenters. This message is associated with Microsoft 365 Roadmap ID 80239. [Rollout Schedule:] General Availability (Worldwide): We will begin rolling out in early December 2026 (previously late November) and expect to complete by mid-December 2026. [Impact on Your Organization:] This capability will be enabled for all meetings by default, allowing a second presenter to start sharing without requiring the first presenter to stop. When enabled, participants can see both shared content streams at the same time, creating a more seamless experience for scenarios such as comparing documents, presenting complementary information, or collaborating across multiple sources. Meeting organizers will also have a meeting option to control whether multiple presenters can share simultaneously in an individual meeting. [Action Required/Recommendations:] Organizations will have tenant-level admin control to determine whether simultaneous sharing is available to their users. Review your organization's sharing policies and inform users and support teams about the new experience. [Compliance considerations:] No compliance considerations identified. Review as appropriate for your organization. -
(Updated) Microsoft Teams: Personal message reminders for chat and channels
MC1470887 · planForChange · normal · Updated 11/03/2026 17:32
Services: Microsoft Teams
Read message
Updated November 3, 2026: We have updated the timeline. Thank you for your patience. [What and Why] Microsoft Teams is introducing personal message reminders for chat and channel messages to help users track follow-ups and stay organized. Users can turn messages into actionable reminders, improving productivity and ensuring important conversations are not missed. [Rollout Schedule] Targeted Release: Beginning mid-November 2026 (previously early November) and expected to complete in mid-November 2026 (previously early October) General Availability (Worldwide, GCC, GCC High, and DoD): Beginning mid-November 2026 (previously October) and completing in December 2026 (previously October) [Impact on Your Organization] Who is affected All Microsoft Teams users in your organization Platforms/Services Microsoft Teams Desktop (Windows, Mac) Mobile (iOS, Android) What will happen Users will be able to set reminders on chat and channel messages. Users can create, update, complete, and delete reminders. Reminders will appear in a dedicated Reminders view with upcoming, active, and completed items. Users will receive toast notifications when reminders are due, along with badge counts on the Teams chat icon. Reminders are private to each user and include message context for quick follow-up. The feature will be enabled by default and will respect existing Teams notification settings. No admin controls or configuration are required. Message Reminder menu item: Message Reminder slice: [Action Required/Recommendations] No action is required. You may consider the following: Inform users about this new capability. Update internal training materials or documentation. [Compliance considerations] QuestionAnswer Does the change store new customer data?Yes. User-created reminders are stored to support the feature and associated with message context. Does the change alter how existing customer data is processed, stored, or accessed?Yes. Messages can now be associated with user-defined reminders, providing another way to access message content. Does the change allow a user to enable and disable the feature themselves?Yes. Users can create, manage, and delete their own reminders. -
(Updated) Microsoft PowerPoint: Prepare internal sales review Copilot skill
MC1529481 · stayInformed · normal · Updated 11/03/2026 17:20
Services: Microsoft 365 apps
Read message
Updated November 3, 2026: We have updated the timeline and content. Thank you for your patience. [What and why] We are introducing a new Copilot skill in PowerPoint, Prepare internal sales review, that helps users create senior-leadership presentations summarizing sales performance, outlook, risks, and decisions. [Rollout schedule] General Availability (Worldwide): Rollout began late October 2026 and is expected to complete by late November 2026 (previously early November). [Impact on your organization] Who is affected Users with access to Copilot in PowerPoint. Platforms and services PowerPoint on Windows (Win32), Mac, and web Copilot in PowerPoint What will happen Users will be able to use a scenario-specific Copilot skill to create executive sales summary presentation drafts. The skill can help sales teams prepare leadership updates more quickly. The skill focuses presentations on sales performance, outlook, risks, and decisions. [Action required and recommendations] No admin action is required. We recommend that you inform sales leaders and PowerPoint Copilot users that this new skill is becoming available in PowerPoint on Windows (Win32), Mac, and web. [Compliance considerations] Does the change alter how existing customer data is processed, stored, or accessed (e.g., documents, emails, chats, etc.)? No. This update adds a scenario-specific authoring skill in PowerPoint and does not introduce new customer data storage or change existing Microsoft 365 data handling pipelines. Does the change introduce or significantly modify AI/ML or agent capabilities that interact with or provide access to customer data? No. The change does not introduce a new AI system-of-record; it provides a new entry point/experience within existing Copilot in PowerPoint capabilities. Does the change provide end users any new way of interacting with generative AI? No. Users continue to interact through existing Copilot in PowerPoint experiences. -
(Updated) Microsoft PowerPoint: Review sales pipeline Copilot skill
MC1529477 · stayInformed · normal · Updated 11/03/2026 17:16
Services: Microsoft 365 apps
Read message
Updated November 3, 2026: We have updated the timeline. Thank you for your patience. [What and why] We are introducing a new Copilot skill in PowerPoint, Review sales pipeline, that helps users create or refresh internal pipeline and forecast review presentations focused on opportunity movement, risks, and next actions. [Rollout schedule] General Availability (Worldwide): Rollout began late October 2026 and is expected to complete by late November 2026 (previously early November). [Impact on your organization] Who is affected Users with access to Copilot in PowerPoint. Platforms and services Microsoft PowerPoint for Windows (Win32), Mac, and web. Copilot in PowerPoint. What will happen Users will be able to use a scenario-specific Copilot skill to create or refresh internal pipeline and forecast review presentation drafts. The skill helps users review opportunities, pipeline movement, risks, and next actions for recurring sales management discussions. [Action required and recommendations] No admin action is required. We recommend that you inform sales managers and PowerPoint Copilot users that this new skill is becoming available in PowerPoint on Windows (Win32), Mac, and web. [Compliance considerations] Does the change alter how existing customer data is processed, stored, or accessed (e.g., documents, emails, chats, etc.)? No. This update adds a scenario-specific authoring skill in PowerPoint and does not introduce new customer data storage or change existing Microsoft 365 data handling pipelines. Does the change introduce or significantly modify AI/ML or agent capabilities that interact with or provide access to customer data? No. The change does not introduce a new AI system-of-record; it provides a new entry point/experience within existing Copilot in PowerPoint capabilities. Does the change provide end users any new way of interacting with generative AI? No. Users continue to interact through existing Copilot in PowerPoint experiences. -
(Updated) Microsoft PowerPoint: Draft proposal response Copilot skill
MC1529476 · stayInformed · normal · Updated 11/03/2026 17:15
Services: Microsoft 365 apps
Read message
Updated November 3, 2026: We have updated the timeline. Thank you for your patience. [What and why] We are introducing a new Copilot skill in PowerPoint, Draft proposal response, that helps users create customer-specific proposal or bid presentation drafts in response to explicit requirements or RFPs. [Rollout schedule] General Availability (Worldwide): Rollout began late October 2026 and is expected to complete by late November 2026 (previously early November). [Impact on your organization] Who is affected Users with access to Copilot in PowerPoint. Platforms and services Microsoft PowerPoint for Windows (Win32), Mac, and web Copilot in PowerPoint What will happen Users will be able to use a scenario-specific Copilot skill to create proposal or bid response presentation drafts. The skill can help users respond more quickly to formal customer requirements and organize response content around evaluation priorities, solution coverage, proof points, delivery details, commercial inputs, and compliance information. [Action required and recommendations] No admin action is required. We recommend that you inform sales and proposal teams that this new skill is becoming available in PowerPoint for Windows (Win32), Mac, and web. [Compliance considerations] Does the change alter how existing customer data is processed, stored, or accessed (e.g., documents, emails, chats, etc.)? No. This update adds a scenario-specific authoring skill in PowerPoint and does not introduce new customer data storage or change existing Microsoft 365 data handling pipelines. Does the change introduce or significantly modify AI/ML or agent capabilities that interact with or provide access to customer data? No. The change does not introduce a new AI system-of-record; it provides a new entry point/experience within existing Copilot in PowerPoint capabilities. Does the change provide end users any new way of interacting with generative AI? No. Users continue to interact through existing Copilot in PowerPoint experiences. -
(Updated) Microsoft PowerPoint: Prepare customer review deck Copilot skill
MC1529480 · stayInformed · normal · Updated 11/03/2026 17:12
Services: Microsoft 365 apps
Read message
Updated November 3, 2026: We have updated the timeline. Thank you for your patience. [What and why] We are introducing a new Copilot skill in PowerPoint, Prepare customer review deck, that helps users create recurring customer-facing business review (QBR) presentations focused on goals, outcomes, adoption, risks, commitments, and next steps. [Rollout schedule] General Availability (Worldwide): Rollout began in late October 2026 and is expected to complete by late November 2026 (previously early November). [Impact on your organization] Who is affected Users with access to Copilot in PowerPoint. Platforms and services PowerPoint for Windows (Win32), Mac, and web. Copilot in PowerPoint. What will happen Users will be able to use a scenario-specific Copilot skill to create customer business review presentation drafts. The skill can help customer-facing teams prepare QBR-style materials faster. The skill can help teams align discussions around customer goals, outcomes, adoption, risks, commitments, and priorities. [Action required and recommendations] No admin action is required. We recommend that you inform sales and customer-facing teams that this new skill is becoming available in PowerPoint for Windows (Win32), Mac, and web. [Compliance considerations] Does the change alter how existing customer data is processed, stored, or accessed (e.g., documents, emails, chats, etc.)? No. This update adds a scenario-specific authoring skill in PowerPoint and does not introduce new customer data storage or change existing Microsoft 365 data handling pipelines. Does the change introduce or significantly modify AI/ML or agent capabilities that interact with or provide access to customer data? No. The change does not introduce a new AI system-of-record; it provides a new entry point/experience within existing Copilot in PowerPoint capabilities. Does the change provide end users any new way of interacting with generative AI? No. Users continue to interact through existing Copilot in PowerPoint experiences. -
(Updated) Microsoft Teams: Teams Events Attendance and Engagement Report Policy
MC1455014 · stayInformed · normal · Updated 11/03/2026 17:05
Services: Microsoft Teams
Read message
Updated November 3, 2026: We have updated the timeline. Thank you for your patience. [What and Why:] We are introducing a new policy that separates Teams Events attendance and engagement report controls from Teams Meetings attendance and engagement report controls. With this change, administrators can independently manage organizer access to attendance and engagement reports for Teams Events through CsTeamsEventsPolicy, without affecting attendance and engagement report settings for Teams Meetings managed through CsTeamsMeetingPolicy. This update provides greater administrative flexibility by allowing separate configuration of attendance and engagement reporting for Teams Events and Teams Meetings. [Rollout schedule:] General Availability (Worldwide, GCC): Rollout will begin in mid-December 2026 (previously early November) and is expected to complete by early January 2027 (previously early December 2026) [Impact on your organization:] Teams Events attendance and engagement report controls will be managed separately from Teams Meetings. A new attendance and engagement report setting will be available in CsTeamsEventsPolicy. Administrators can configure one of the following policy values:OnOrganizers can view and download attendance and engagement reports for all events. Organizers cannot disable attendance and engagement reporting. OffOrganizers cannot view or download attendance and engagement reports for any events. On, organizers can turn it off (default)Organizers can view and download attendance and engagement reports for events and can disable attendance and engagement reporting in event options. Off, organizers can turn it onAttendance and engagement reporting is disabled by default. Organizers can enable attendance and engagement reporting in event options for individual events. [Action Required / Recommendations:] Review your current attendance and engagement reporting requirements for Teams Events. Configure the appropriate setting in the new Teams Events attendance and engagement report policy based on your organizational needs. Do not assume Teams Events will continue to inherit attendance and engagement report settings from CsTeamsMeetingPolicy. Update internal administrative documentation and guidance if you currently manage attendance reporting through Teams meeting policies. No immediate action is required before rollout. However, we recommend reviewing and validating policy settings after the feature becomes available to ensure Teams Events reporting behavior aligns with your organization's requirements. -
Limits in Copilot Chat
MC1536158 · stayInformed · normal · Updated 11/03/2026 02:27
Services: Microsoft 365 Copilot Chat
Read message
Microsoft uses fair use limits for some Copilot features for users without a Microsoft 365 Copilot license. Features, such as image generation, already use limits, as previously communicated in MC1064749. We are applying this approach to additional Copilot Chat features and capabilities. Users will be notified in-product if the capacity or feature is not available. Rollout Schedule Limits are currently used for some Copilot Chat capabilities and may expand to additional capabilities over time. New Copilot Chat limits are currently rolling out. Impact on Your Organization Who is affected: Users without a Microsoft 365 Copilot license in commercial tenants. Platforms/Services: When using Copilot Chat in apps (web, desktop, and mobile). What will happen: Fair use provides users with access to a feature with limits and can vary throughout the day. For either type of limit, the user can try the feature or capability again later. Microsoft will be clear on the timeframe in product. Responses already in progress will not be interrupted. Microsoft sets and manages these limits. Admins can't view or adjust the limits. Action Required/Recommendations No action is required. We recommend that admins: Inform help desk staff that some Copilot Chat capabilities will be limited for users without a Microsoft 365 Copilot license. Review Limits for features and capabilities in Microsoft Copilot Chat | Microsoft Support for more information about how access may vary. Review Manage self-service license requests in the Microsoft 365 admin center to understand how your organization can manage self-service license requests. Compliance considerations No compliance considerations identified, review as appropriate for your organization. -
Microsoft 365 Copilot: Conversation orchestration expands routing and overflow capabilities
MC1536059 · stayInformed · normal · Updated 11/03/2026 00:12
Services: Dynamics 365 Apps
Read message
[What and why] Conversation orchestration in Microsoft Dynamics 365 Contact center actively manages conversations throughout their lifecycle, from initiation through resolution. As conditions change, such as increasing wait times, queues filling quickly, or representatives going offline, conversation orchestration can automatically take actions defined in natural-language playbooks configured by administrators. Administrators can configure playbooks for specific scenarios using guided templates. Built-in validation identifies conflicts before playbooks are published. These capabilities help organizations automate contact center processes while improving routing, continuity, and responsiveness. [Rollout schedule] General Availability (Worldwide): Beginning in late October 2026 and expected to complete by late November 2026 [Impact on your organization] Who is affected Organizations using or planning to use Conversation Orchestration in Dynamics 365 Contact center Platforms and services Microsoft Dynamics 365 Contact center Microsoft 365 Copilot (Premium) What will happen Dynamic priority escalation: Conversation priority can be reevaluated as a conversation progresses based on conditions such as wait-time thresholds, queue transfers, customer tier, or other context. Overflow handling across multiple conditions: Administrators can configure actions for conditions such as queues being outside operating hours, representatives being signed out or unavailable, queue wait times exceeding a threshold, or the number of waiting conversations exceeding a specified limit. Actions can include offering callbacks, routing to alternate queues, expanding assignment eligibility, notifying supervisors, or providing contextual customer messages. Overflow handling can also be configured for direct inward dial calls when representatives are unavailable or do not accept calls. Assignment to a previously engaged or preferred representative: Conversation orchestration can reconnect customers with previously engaged or preferred representatives based on factors including previous interactions, queue membership, availability, and workload capacity. For asynchronous conversations, organizations can choose to consider representative presence status and active conversation limits before reconnecting customers. If that representative is unavailable, the conversation can fall back to the next qualified representative. Bullseye routing: Administrators can progressively expand the pool of eligible representatives when a conversation is not assigned within a defined timeframe. Routing rings can use skills, proficiency levels, teams, or other business criteria. Existing customers using Conversation Orchestration can continue using their existing configurations without additional action. New customers can enable Conversation Orchestration and configure playbooks. Copilot credits are consumed when administrators publish playbooks. The feature does not consume Copilot credits during runtime execution. Screenshot 1 - Conversation orchestration - Get Started view: Screenshot 2 - Conversation orchestration - Escalate priority view: [Action required and recommendations] No additional preparation is required for existing customers. For new customers: Review the prerequisites for Conversation Orchestration. Enable Conversation Orchestration. Configure playbooks appropriate for your organization. [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
Microsoft Teams: What's happening across your organization in Activity notifications
MC1536058 · stayInformed · normal · Updated 11/03/2026 00:12
Services: Microsoft Viva
Read message
[What and why] We are adding a new What's happening across your organization section beneath community and storyline notifications in the Microsoft Teams Activity feed. The section helps users discover relevant content beyond their immediate communities, including posts from leaders and official communities, and provides ways to join communities or follow colleagues directly from the notification experience. [Rollout schedule] Public Preview (Worldwide): Rollout will begin in early November 2026 and is expected to complete by early December 2026. General Availability (Worldwide): Rollout will begin in early December 2026 and is expected to complete by mid-December 2026. [Impact on your organization] Who is affected All users licensed for Microsoft Teams and Viva Engage. Platforms and services Microsoft Teams Teams Activity feed Communities and storylines What will happen When users open the Teams Activity feed, they will see a new What's happening across your organization section beneath community and storyline notifications. Each notification can surface up to five relevant posts in a scrollable view. Users can discover relevant community and storyline posts beyond the communities they already belong to. Posts from leaders and official communities can appear in this section. Users can join communities, including official communities, from the notification experience. Users can follow colleagues and leaders from the notification experience. Updated Teams activity feed experience [Action required and recommendations] If this is an experience that your network might benefit from, we recommend that you verify that Communities and Storylines are enabled in the Teams admin center. To enable Communities in Teams: Go to the Teams admin center. Select Settings & policies. Choose Global (Org-wide default) or a custom policy. Open Messaging settings. Set Communities to On. Save your changes. To enable Storylines in Teams: Go to the Teams admin center. Select Settings & policies. Choose Global (Org-wide default) or a custom policy. Open Messaging settings. Set Storylines to On. Save your changes. [Learn more] Getting started with Viva Engage Communities in Microsoft Teams | Microsoft Support Manage Viva Engage experiences in Microsoft Teams - Microsoft Teams | Microsoft Learn [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
Increasing user exception limit to 10,000 for Standard-Deferred release preferences
MC1536057 · stayInformed · normal · Updated 11/03/2026 00:11
Services: Microsoft 365 suite
Read message
[What and Why:] We heard your feedback that the 100-user exception limit was too small to support meaningful pilot and validation audiences, particularly in larger organizations. We previously introduced Microsoft Entra ID group support to simplify audience management. We are now increasing the exception limit from 100 to 10,000 users per tenant, giving administrators more flexibility to manage release readiness at scale. This update lets you assign a larger audience to a release preference different from your tenant-wide selection - for example, keeping a larger validation group on Standard release while the rest of your organization uses Deferred release. [Rollout Schedule:] General Availability (Worldwide): We will begin rolling out in late October 2026 and expect to complete by mid-November 2026. [Impact on Your Organization:] Who is affected: Administrators managing Standard and Deferred release preferences in the Microsoft 365 admin center. What is changing: The maximum exception audience increases to 10,000 users per tenant, counting users assigned individually and members of assigned groups together. This is not a per-group allowance or a limit on your organization total users. You can continue using Microsoft Entra ID security groups to manage exceptions. Nested groups remain unsupported. If your tenant uses Deferred release, you can assign a larger group of IT staff, help desk personnel, and business representatives to Standard release to evaluate eligible updates earlier. If your tenant uses Standard release, you can assign a larger audience to Deferred release when those users need additional preparation time. If a customer adds a group with more than 10,000 users, they will receive a message, during addition, notifying them of the limit. If they add a group that later exceeds the limit, only the first 10,000 users will be included. The Release preferences in MAC will display a message asking them to remove the users who exceed the limit. What is not changing: This update increases audience capacity; it does not change which features are eligible for Deferred release or how the deferred period works. Deferred release continues to delay eligible major features by approximately 30 days after their rollout to Standard release begins, not after rollout completes or after an individual pilot user receives the feature. [Action Required/Recommendations:] No action is required unless you want to expand your exception audience. Once the increased limit is available in your tenant, review your pilot and validation needs and update your assignments in the Microsoft 365 admin center under: Copilot > Settings > View all > Copilot Release Preferences: General Availability. Keep the combined exception audience within 10,000 users, review group membership regularly, and update your internal rollout and readiness documentation as needed. [Compliance considerations:] When expanding your exception audience, review its membership against your organization change-management, validation, and governance requirements. -
Microsoft Teams: Facilitator Protection skill helps identify suspected social-engineering attempts
MC1536056 · stayInformed · normal · Updated 11/03/2026 00:10
Services: Microsoft Teams
Read message
[What and why] Facilitator can help users identify suspected social-engineering attempts by people outside their organization during a meeting. When Facilitator is present, its Protection skill uses AI to check the meeting transcript for signs that someone may be attempting to trick users into sharing sensitive information. If a suspected attempt is detected, users will see a warning with options to end the meeting or temporarily restrict information sharing. This feature can help organizations reduce the risk of sensitive information being disclosed through social engineering during meetings with external participants. [Rollout schedule] General Availability (Worldwide): Beginning in late January 2027 and expected to complete by mid-February 2027 [Impact on your organization] Who is affected Users who use Facilitator in meetings with participants outside their organization Platforms and services Microsoft Teams Facilitator What will happen When Facilitator is present in a meeting with participants outside your organization, the Protection skill is invoked automatically. The Protection skill uses AI to check the meeting transcript for signs of suspected social-engineering attempts. If a suspected attempt is detected, users will receive a warning. Users will have options to end the meeting or temporarily restrict information sharing. No action is required to enable the Protection skill. [Action required and recommendations] No action is required to enable the Protection skill. We recommend that you: Inform users that they may receive warnings about suspected social-engineering attempts during meetings with external participants. Help users understand the available options if a warning appears. Review the Facilitator documentation to familiarize yourself with the feature. [Compliance considerations] This change introduces an AI capability that interacts with customer data. When Facilitator is present, the Protection skill uses AI to check the meeting transcript for signs of suspected social-engineering attempts. -
Microsoft 365 Copilot: New accounting capabilities in Excel and Cowork
MC1536053 · stayInformed · normal · Updated 11/03/2026 00:08
Services: Microsoft 365 apps
Read message
[What and why] New accounting capabilities in Copilot in Excel and Cowork help finance professionals complete common accounting tasks in the tools they already use. Users can reconcile accounts, prepare journal entries, analyze financial performance and variances, and prepare financial reports. Additional capabilities support budgeting, forecasting, audit, tax, compliance, and training. Copilot prepares the work while users retain control of review, approval, and posting. Nothing is posted automatically to an ERP or system of record without approval. [Rollout schedule] Public Preview: We will begin rolling out in late October 2026 and expect to complete by mid-November 2026 General Availability (Worldwide): We will begin rolling out on November 13, 2026, and expect to complete by late November 2026 [Impact on your organization] Who is affected Accountants, AP/AR specialists, controllers, and other finance professionals with a Microsoft Copilot licenses Platforms and services Microsoft Copilot Microsoft Excel Cowork What will happen Users can reconcile accounts by comparing balances and transactions, identifying discrepancies, and preparing reconciling items for review. Users can draft journal entries, including accruals, reclassifications, allocations, reversals, and recurring entries, with checks for required inputs and balanced entries. Users can analyze financial performance against plan, identify key drivers, and prepare financial reporting and variance analysis. Additional capabilities support budgeting, forecasting, audit, tax, compliance, and training. In Excel and Cowork, finance professionals can choose to capture an audit trail when they invoke an accounting capability. When selected, a record of what Copilot changed and why is created in their chat history. Audit trails are currently available in Excel and are planned for Cowork. Copilot works only with content each user can access, respects existing permissions and sensitivity labels, and stays within the Microsoft 365 service boundary. Nothing is posted automatically to an ERP or system of record without user approval. Accounting capabilities can use connectors as separate sources, including sources used to read from or write to ERP systems. The accounting capabilities do not depend on these connectors. Third-party accounting connectors may require separate licensing or admin enablement. [Action required and recommendations] Action required: During Public Preview, accounting capabilities in Excel and Cowork are available to users who have a Microsoft Copilot license and are enrolled in Microsoft Copilot Frontier. Beginning with General Availability on November 13, 2026, Frontier enrollment will not be required. To provide access during Public Preview: Assign Microsoft Copilot licenses to finance users who need access. In the Microsoft 365 admin center, go to Copilot > Settings > Frontier, turn on Frontier, and choose whether to provide access to all eligible users or specific users or groups, such as your finance team. Enroll your admin account in Frontier if you need to see and manage Frontier features such as Cowork in the admin center. Consider notifying your finance teams about the new accounting capabilities. Learn more Available plugins for Copilot Cowork | Microsoft Learn Microsoft Copilot for finance: Purpose-built for the way finance teams work | Microsoft Copilot Blog Use built-in skills and skills created by Microsoft with Copilot in Excel | Microsoft Support Explore AI Early Access in Microsoft 365 | Microsoft Frontier Get Started with Frontier for IT Admins | Microsoft Frontier [Compliance considerations] QuestionAnswer Does the change introduce or significantly modify AI/ML or agent capabilities that interact with or provide access to customer data?Yes. The new accounting capabilities use Microsoft Copilot to perform accounting-related work using content the user can access. Does the change provide end users a new way of interacting with generative AI?Yes. Finance users can use Copilot accounting capabilities in Excel and Cowork for reconciliation, journal entries, analysis, and reporting. -
Microsoft Entra ID: Microsoft-provided SMS and voice authentication to retire for self-service password reset (SSPR)
MC1536049 · planForChange · normal · Updated 11/03/2026 00:07
Services: Microsoft Entra
Action required by: 03/22/2027 07:00
Read message
[What and why] As Microsoft-provided SMS and voice authentication retire in Microsoft Entra ID, these methods will also become unavailable for SSPR. Organizations have 50 days after the applicable sign-in retirement rollout reaches their tenant to prepare alternative recovery methods. Users may still be able to sign in but lose the ability to reset forgotten passwords. Passkeys and other sign-in methods don't automatically satisfy SSPR requirements. Admins should identify affected users and ensure they have enough eligible recovery methods to prevent disruptions and increased helpdesk requests. [Rollout schedule] General Availability (Worldwide, GCC): We expect rollout to begin and complete in February 2027 User populationSign-in retirement rollout beginsSSPR transition ends Users other than Global Administrators and external usersFebruary 1, 202750 days after this rollout reaches your tenant Global Administrators and external usersJuly 1, 202750 days after this separate rollout reaches your tenant These are phased rollout start dates, not a single SSPR cutoff for every organization. Each population's 50-day period begins when its applicable rollout reaches your tenant. [Impact on your organization] Who is affected Organizations with users who rely on Microsoft-provided SMS/voice to meet their password-reset verification requirements. This includes users who have another sign-in method but still depend on SMS/voice for password recovery. Platforms and services Microsoft Entra ID SSPR What will happen When the applicable sign-in retirement rollout reaches your tenant: 50-day transition: Existing SMS and voice registrations remain usable for SSPR under your current recovery policy. Registration changes: SMS/voice SSPR registration and refresh prompts stop, but prompts for other eligible methods continue. My Sign-Ins: Users can no longer add SMS/voice methods or edit authentication phone numbers. Existing phone registrations appear disabled, even while usable for SSPR during the transition. Customer-managed telephony (CYOT): Recovery through supported providers remains available. After the 50-day transition period: Microsoft-provided SMS and voice are no longer available as SSPR recovery options. User's remaining eligible recovery methodsPassword-reset experience Enough methods to meet the applicable SSPR requirementUser can continue resetting their password with those methods Not enough methods to meet the applicable SSPR requirementUser cannot complete SSPR and is directed to contact their administrator The applicable one/two method requirement still applies. To retain SMS/voice for recovery, your organization must configure a supported CYOT. Microsoft will not automatically change your SSPR policy or enable Allow password change after secure sign-in for your tenant. [Action required and recommendations] Prepare affected users before their applicable 50-day transition period ends: Identify affected users. Find users relying on SMS/voice for SSPR, even if they have other sign-in methods registered. Use the SMS and voice retirement and migration guidance. Prepare alternative recovery methods. Ensure users have enough eligible methods to meet SSPR policy requirements without Microsoft-provided SMS/voice. Passkeys alone don't satisfy SSPR requirements. If phone recovery is needed, configure and test a supported telephony provider before the transition ends. Test and communicate. Verify password recovery works with your SSPR policies and Conditional Access settings. Inform users and helpdesk staff about deadlines, registration steps, and support options. Recommended: Let passkey users change a forgotten password Where available, administrators can enable Allow password change after secure sign-in for eligible users. Users can then sign in with their passkey and change their password in My Sign-Ins without knowing/entering their current password. Learn more SMS and voice retirement and migration guidance How Microsoft Entra self-service password reset works Choose a telephony provider for SMS and voice authentication [Compliance considerations] If your organization needs phone-based recovery for regulatory or operational reasons, plan and validate a supported customer-managed provider before the applicable SSPR cutoff. -
Microsoft Defender: Expanded URBAC permission support for email content access
MC1536045 · stayInformed · normal · Updated 11/03/2026 00:04
Services: Microsoft Defender XDR
Read message
[What and why] We’re expanding Unified role-based access control (URBAC) permission support for Email & collaboration content: Emails associated with alerts in Microsoft Defender. This change provides more consistent email content access across alert investigation scenarios based on a user’s assigned permissions. Previously, this permission applied to: Email reported by user as malware or phish Email reported by user as junk With this rollout, the permission will also apply to: A potentially malicious URL click was detected A user clicked through to a potentially malicious URL [Rollout schedule] General Availability (Worldwide): Available now [Impact on your organization] Who is affected Security analysts who preview or download emails associated with the affected alerts Platforms and services Microsoft Defender What will happen Security analysts with the required permission will be able to preview and download emails associated with these four alerts: Email reported by user as malware or phish Email reported by user as junk A potentially malicious URL click was detected A user clicked through to a potentially malicious URL Access is based on the user’s assigned Email & collaboration content: Emails associated with alerts permission. [Action required and recommendations] Ensure that users who need to preview and download emails associated with these four alerts have the required Email & collaboration content: Emails associated with alerts permission. Learn more Permissions in Microsoft Defender unified role-based access control (RBAC) - Microsoft Defender XDR | Microsoft Learn [Compliance considerations] No compliance considerations identified. Review as usual for your organization. -
(Updated) Microsoft Copilot (Microsoft 365): Power BI reports as references in Copilot Notebooks
MC1474458 · stayInformed · normal · Updated 11/02/2026 23:04
Services: Microsoft 365 apps
Read message
Updated November 2, 2026: We have updated the timeline. Thank you for your patience. [What and why:] Copilot Notebooks now lets users add Power BI reports as references, bringing report data directly into their notebooks alongside files. Copilot uses this information to help generate more relevant summaries, presentations, and briefs grounded in the organization's data. [Rollout schedule:] Public Preview (Worldwide): We will began rolling out late September 2026 and expect to complete by mid-October 2026. General Availability (Worldwide): We will begin rolling out end of November 2026 (previously late October) and expect to complete by mid-December 2026 (previously mid-November). [Impact on your organization:] Customers who use Power BI can bring their reports into Copilot Notebooks as a knowledge source, so Copilot's outputs reflect real business data, not just documents. Organizations that don't use Power BI won't see any change. [Action required / Recommendations:] No additional setup is required beyond having Power BI and Copilot already available to users. If your organization already uses Power BI and has Copilot enabled, this capability will become available automatically. -
(Updated) Microsoft Viva Engage: Flexible targeting of Storyline Announcements
MC1183013 · stayInformed · normal · Updated 11/02/2026 23:00
Services: Microsoft Viva
Read message
Updated November 2, 2026: We have updated the timeline. Thank you for your patience. We’re introducing My Team audiences and expanded targeting capabilities in Viva Engage to help leaders communicate with the employees in their organization and tailor messages to relevant teams, departments, locations, or groups. My Team provides a ready-to-use, automatically maintained audience based on the organizational hierarchy, so leaders can reach the employees who report up to them, including both direct and indirect reports. This audience helps unlock and improve leadership experiences across Viva Engage, making Storyline Announcements, audience analytics, Leadership Corner, and feed and digest distribution more relevant with less setup. Leaders and delegates can use My Team as-is, review its membership, or further customize and save it as a reusable audience across leader communication experiences. For Storyline Announcements, they can also define recipients at the time of publish, choosing My Team, a saved audience, or a custom audience built using organizational attributes such as department, job title, or country; existing groups like M365 Groups, distribution lists, or security groups; and individual users by name. Together, My Team and flexible targeting make leader communications more relevant, scalable, and easier to manage - with a dynamic default audience and precise targeting for relevant employee groups. This message is associated with Microsoft 365 Roadmap ID 499895. [When this will happen:] Public Preview (Worldwide): Begins mid-November 2025 and completes by mid-March 2026 (previously early February). General Availability (Worldwide): Begins mid-January 2027 (previously early November 2026) and completes by late February 2027 (previously late November 2026). [How this affects your organization:] Who is affected: Leaders and delegates using Viva Engage Storyline Announcements in tenants enrolled in public preview. What will happen: This capability is being introduced as part of the public preview for Viva Engage. During this phase, leaders and their delegates can actively experiment with flexible audience targeting for Storyline Announcements—defining a custom audience at the time of posting, rather than relying solely on pre‑configured Leader Audiences. Audiences can include organizational attributes (such as reporting structure, country, department, job title), existing groups (Microsoft 365 Groups, DLs, SGs), or individual users. Notifications and delivery channels (Teams, email, Viva Engage Inbox) remain unchanged for recipients. No dependency on IT or advance audience setup—leaders can act immediately when communication needs arise. Available only in public preview; functionality and targeting options may evolve before general availability. Admins should ensure organizational attributes in Entra ID or Organizational Data in Microsoft are accurate to support successful targeting. Available platforms: Desktop and web. Licensing requirements: This feature requires a premium license available through Viva or Communications and Communities (C&C). Availability may vary depending on your organization's Microsoft 365 licensing agreement. [What you can do to prepare:] No admin action is required for rollout. To prepare, you may want to: Validate organizational attributes (reporting structure, country, department, role, job title) in Microsoft Entra ID or Organizational Data in Microsoft. Confirm leader and delegate assignments to ensure the right people can use Storyline Announcements and the new targeting control. Learn more: Use your organizational data in Microsoft 365 and Microsoft Viva | Microsoft Viva | Microsoft Learn [Compliance considerations:] No compliance considerations identified, review as appropriate for your organization. -
(Updated) Microsoft Teams: Breakout room support for Teams Rooms on Android
MC1488847 · stayInformed · normal · Updated 11/02/2026 18:38
Services: Microsoft Teams
Read message
Updated November 2, 2026: We have updated the timeline. Thank you for your patience. [What and why] We're introducing breakout room support for Microsoft Teams Rooms on Android. This update allows Teams Rooms on Android devices to be assigned to breakout rooms and moved between breakout rooms and the main meeting room by meeting organizers. This feature improves coordination during breakout sessions and brings Microsoft Teams Rooms on Android closer to feature parity with Microsoft Teams Rooms on Windows. This enhancement is based on customer feedback and helps organizations deliver a more consistent meeting experience across Teams Rooms devices. [Rollout schedule] General Availability (Worldwide): Beginning in early December 2026 (previously mid-November) and expected to be complete by mid-December 2026 (previously late November) [Impact on your organization] Who is affected Organizations using Microsoft Teams Rooms on Android devices Meeting organizers who use breakout rooms in Microsoft Teams meetings Platforms and services Microsoft Teams Microsoft Teams Rooms on Android What will happen Meeting organizers will be able to assign Microsoft Teams Rooms on Android devices to breakout rooms. Teams Rooms on Android devices can be moved into and out of breakout rooms during a meeting. The feature will be available by default when rollout is complete. [Action required and recommendations] No action is required. We recommend that you: Inform meeting organizers and room administrators about this new capability. Update any internal documentation or training materials that reference breakout room functionality for Teams Rooms devices. [Compliance considerations] No compliance considerations identified, review as appropriate for your organization. -
Building a risk-based patching response for Windows Server
MC1535667 · stayInformed · normal · Updated 11/02/2026 18:01
Services: Windows
Read message
What and why: Microsoft recommends adopting a risk-based approach to Windows Server patching. It helps organizations respond faster to critical vulnerabilities while minimizing operational disruption. Rather than relying on fixed patching schedules, prioritize updates based on exploit activity, system exposure, workload criticality, and business impact. Rollout schedule: This guidance is available now. Impact on your organization: Organizations managing Windows Server workloads across on-premises, hybrid, and cloud environments can benefit from a risk-based patching strategy. The approach helps IT teams reduce security exposure, prioritize critical updates, and maintain service availability through appropriate testing and validation. Action required/recommendations: Assess risk: Maintain an inventory of servers, workloads, dependencies, and security exposure. Define patching priorities: Establish routine, accelerated, and emergency response paths based on vulnerability risk. Prepare for emergencies: Document and test deployment, validation, and rollback procedures. Explore management tools: Use Azure Update Manager, Azure Arc, and supported Windows Server hotpatching capabilities to streamline updates. Learn more: Building a risk-based patching response for Windows Server. Compliance considerations: Review your organization’s patching policies against applicable security and compliance requirements. Consider documenting risk-based patching timelines, approval processes, exceptions, compensating controls, and evidence of successful updates to support compliance and audit readiness. -
Introducing restore summary in Windows settings backup and restore
MC1535666 · stayInformed · normal · Updated 11/02/2026 18:01
Services: Windows
Read message
What and why Starting with Windows 11, version 24H2 and later, Windows settings backup and restore introduces restore summary. It’s a new on-device experience that helps users understand what was restored to their PC after setup. Users can view a summary of restored personalization settings and the Microsoft Store app list, having greater visibility into restore outcomes and getting productive faster on a new device. Rollout schedule Generally available with the October 2026 non-security update for Windows 11, version 24H2 or later. Impact on your organization Who is affected? Organizations using Windows settings backup and restore can help users transition to new devices, recover from device replacement scenarios, or complete device refreshes. What will happen? With the new restore summary, users can gain immediate visibility into their restored experience after setup. This new capability helps accelerate time to productivity by making restore outcomes clear and easy to understand. For more information about Windows settings backup and restore, see Windows settings backup and restore Overview. Action required/recommendations No action is required. Organizations might want to: Review the Windows settings backup and restore documentation to understand how backup and restore experiences work for their users. Inform help desk and support teams that users will see a new restore summary experience following a successful restore process. Compliance considerations No compliance considerations are identified. Review as appropriate for your organization. -
(Updated) Microsoft Copilot Word: Document summarization experience moving
MC1454113 · planForChange · normal · Updated 11/02/2026 17:44
Services: Microsoft 365 apps
Read message
Updated November 2, 2026: We have updated the timeline. Thank you for your patience. [What and Why:] We are updating how users access document summarization in Microsoft Word. Beginning in September 2026, the current Top of Doc summarization experience will transition to other Copilot in Word surfaces. This change creates a more unified Copilot experience in Word while preserving users’ ability to quickly understand document content. The document summarization capability is not being removed and will continue to be available through Copilot in Word. [Rollout Schedule:] General Availability (Worldwide, GCC, GCCH, DoD): Rollout will begin early September 2026 and is expected to complete by end of November 2026. [Impact on Your Organization:] Who is affected Users licensed for and able to access Copilot in Word. Platforms and services Microsoft Word Microsoft 365 Copilot in Word What will happen The existing Top of Doc summarization experience will move to other Copilot surfaces in Word. In supported scenarios, users may see a proactive “Summarize this document” suggestion within the Copilot experience. Selecting the suggestion will generate a summary of the current document in Copilot. Users can open Copilot in Word and request a summary using natural language prompts, such as “Summarize this document.” The underlying document summarization capability will remain available; only the access experience is changing. [Action Required/Recommendations:] No admin action is required. We recommend that you: Inform users that document summarization is moving from the Top of Doc experience to other Copilot surfaces in Word. Update internal training materials, adoption content, and help desk documentation that reference Top of Doc summarization. Encourage users to access summaries through Copilot in Word by using the “Summarize this document” suggestion or a natural language prompt. Suggested user communication Document summaries in Word will continue to be available through Copilot, but the existing Top of Doc summary experience is being retired. To generate a summary, open Copilot in Word and ask Copilot to summarize the current document. [Compliance Considerations:] End users have a new way to interact with generative AI: The summarization capability remains AI-powered and will be accessed through Copilot interactions and prompts. User workflow change: Users will access the same summarization capability through different Copilot entry points, which may require user awareness and updated training materials. No other compliance considerations identified based on the information provided. Review as appropriate for your organization. -
(Updated) Microsoft Teams: Customize file extensions blocked by Weaponizable File Protection
MC1509801 · stayInformed · normal · Updated 11/02/2026 17:28
Services: Microsoft Teams
Read message
Updated November 2, 2026: We have updated the timeline. Thank you for your patience. [What and why] Microsoft Teams is expanding admin controls for Weaponizable File Protection. Admins will be able to customize which file extensions are blocked in Teams based on their organization’s security needs or continue using the Microsoft-recommended default list. This change provides greater flexibility to tailor file protection policies while maintaining a secure collaboration experience. [Rollout schedule] General Availability (Worldwide): Beginning in early December 2026 (previously early November) and expected to complete by mid-December 2026 (previously mid-November) [Impact on your organization] Who is affected Organizations that use Weaponizable File Protection in Microsoft Teams Platforms and services Microsoft Teams What will happen Before this rollout, Microsoft defines the file extensions blocked by Weaponizable File Protection, and admins cannot customize the list. After this rollout, admins can define which file extensions are blocked for their organization or continue using the Microsoft-recommended default list. Organizations with Weaponizable File Protection enabled will continue using the Microsoft-recommended list by default. Organizations that continue using the Microsoft-recommended list will automatically receive future updates to that list. If an admin customizes the list, the organization will use the customized list and will no longer automatically receive future updates to the Microsoft-recommended list. The user experience will not change. Files with blocked extensions will continue to be blocked in Teams as they are today. Screenshot 1 Customize file type view: Screenshot 2 Customize file type add view: [Action required and recommendations] No action is required. Organizations with Weaponizable File Protection enabled will continue using the Microsoft-recommended list by default. If your organization wants to customize Weaponizable File Protection: Admins can add or remove file extensions based on their organization’s security needs. Admins can reset the configuration to the Microsoft-recommended default list at any time to resume receiving automatic updates. [Compliance considerations] QuestionAnswer Does the change include an admin control?Yes. Admins will be able to customize the file extensions blocked by Weaponizable File Protection or use the Microsoft-recommended default list. -
Dynamics 365 apps and Dataverse – Information about the 2026 time zone changes in Canada
MC1526697 · planForChange · normal · Updated 10/31/2026 04:46
Services: Dynamics 365 Apps
Read message
Dynamics 365 apps and Dataverse are being updated to add the new Canadian time zone definitions in support of the 2026 time zone changes in Manitoba, Alberta, and British Columbia. This is a general awareness message to support the changes and complements MC1510951 — Windows updates are available for 2026 time zone changes in Canada. Rollout schedule The Dataverse update is being deployed through the regular release schedule and is scheduled to reach the Canada region by October 31, 2026. How does this affect me? The new time zones will become available across Dynamics 365 apps and within the Dataverse service. What action do I need to take? After the Dataverse update is available, affected users must select the appropriate new region-specific time zone. The update does not automatically change their existing selection. Review the application-specific guidance below and validate business processes that depend on local times in the affected regions. Dynamics 365 Field Service: Impact: Schedule Board may display times that are incorrect by one hour. Some mobile scenarios may also display incorrect dates or times when the new Canadian time zones are selected. The new time zones may also appear at the bottom of the time-zone lists in Bookable Resource and working hours forms rather than in their expected positions. Action: If not already applied, install the available Field Service app update through Power Platform admin center to address the Schedule Board issue. Mobile fixes remain in progress, with published workarounds available. For affected scenarios, follow the applicable Known Issue instructions to temporarily select an alternative time zone with the same UTC offset. Review the following Known Issues for details and workarounds: Schedule Board may display incorrect times for Western Canadian regions starting November 1, 2026 Newly added Western Canadian time zones not correctly sorted in Bookable Resource time zone dropdown Newly added Western Canadian time zones are not correctly positioned in working hours form NativeExperience syncs wrong time zone QuickNote displays incorrect timestamp with new Canadian time zones -
Power Apps - Information regarding the retirement for the Proactive control rename feature in canvas apps
MC1532426 · stayInformed · normal · Updated 10/31/2026 04:03
Services: Power Apps
Read message
On December 11, 2026, the Proactive control rename feature for canvas apps in Power Apps will be no longer available. How does this affect me? After December 11, 2026, makers and tenant administrators will no longer have access to Copilot (AI-powered assistant) suggestions for renaming similar controls or applying multiple suggested renames in canvas apps. Existing app control names and formulas will remain unchanged. Once this feature is retired:Copilot (AI-powered assistant) will no longer suggest names for similar controls or offer to apply multiple suggested renames when a supported control is manually renamed. This change is enforced and cannot be opted out. Existing app control names and formulas will not be affected. What action do I need to take? There is no action required by makers. Tenant administrators should inform makers about this retirement. -
Power Apps - Formula assistance features in canvas apps are being retired
MC1532421 · stayInformed · normal · Updated 10/31/2026 03:56
Services: Power Apps
Read message
Starting on December 11, 2026, the Use Copilot to create and edit Power Fx formulas and Power Apps Ideas formula assistance features in Power Apps will be no longer available. How does this affect me? The affected features will no longer be available to makers who use them to generate or transform Power Fx formulas after December 11, 2026. This will not impact existing formulas in published apps. What action do I need to take? There is no action required by makers. Tenant administrators should inform makers about this retirement. -
(Updated) General Availability: Microsoft Entra passkeys on Windows
MC1282568 · stayInformed · normal · Updated 10/30/2026 23:22
Services: Microsoft Entra
Read message
Updated October 30, 2026: We have updated the timeline. Thank you for your patience. [Introduction] Microsoft Entra passkeys on Windows will soon be Generally Available, enabling phishing‑resistant, passwordless sign‑in to Microsoft Entra‑protected resources from Windows devices. The Public Preview of this capability was previously announced in MC1247893. Users can create device‑bound passkeys stored in the Windows Hello container and authenticate using Windows Hello methods (face, fingerprint, or PIN). This expands passwordless authentication support to Windows devices that aren’t Microsoft Entra‑joined or registered, helping organizations strengthen security and reduce reliance on passwords across corporate‑managed, personal, and shared device scenarios. [When this will happen:] General Availability (Worldwide, GCC): We will begin rolling out in late April 2026 and expect to complete by mid‑June 2026. General Availability (GCC High, DoD): We will begin rolling out in early February 2027 (previously early October 2026) and expect to complete by late February 2027 (previously late October 2026) For Airgap: We will begin rolling out in early May 2027 and expect to complete by late May 2027. How this affects your organization: Who is affected: Organizations using Microsoft Entra ID with passkeys enabled in the Authentication Methods policy whose users sign in from Windows devices, including: Corporate‑managed PCs Personal devices Shared devices What will happen: With this General Availability release: Microsoft Entra passkeys on Windows will no longer require explicit opt‑in through Windows Hello AAGUID allow‑listing in a passkey (FIDO2) profile. This represents a change from Public Preview behavior, where administrators were required to explicitly allow Windows Hello AAGUIDs in a passkey profile for Microsoft Entra passkeys on Windows to function. If your passkey profile allows device‑bound, non‑attested passkeys:Users scoped to that profile will now be able to register and use Microsoft Entra passkeys on Windows by default without additional administrator configuration. As a result:Users in scope of passkey profiles that allow device‑bound, non‑attested passkeys may begin registering and using passkeys on Windows devices. If Conditional Access policies allow:Passkeys can be created and used on Windows devices that are not Microsoft Entra‑joined or registered, including personal or shared PCs. Each Windows device requires separate passkey registration per Entra account. Windows Hello for Business remains recommended for managed, Microsoft Entra‑joined or registered devices. Passkeys on Windows supplement unmanaged or shared device scenarios and do not support device sign‑in. Attestation is not currently supported for Microsoft Entra passkeys on Windows but is planned for a future update. What you can do to prepare: No action is required for most organizations. If you do not want users to register or use Microsoft Entra passkeys on Windows: Update the relevant passkey (FIDO2) profile to block Windows Hello AAGUIDs. Review existing passkey profiles that allow device‑bound, non‑attested passkeys. Add Windows Hello AAGUIDs to the block list in passkey profiles where passkey usage on Windows devices should not be permitted. Learn more: Enable Microsoft Entra passkey on Windows | Microsoft Learn (will be updated before GA rollout) [Compliance considerations:] Compliance areaExplanation Does the change modify, interrupt, or disable Conditional Access policies?Existing Conditional Access policies continue to govern whether passkeys can be created or used on unmanaged Windows devices. Does the change include an admin control and can it be controlled through Entra ID group membership?Admins can control passkey availability through Authentication Methods policies and FIDO2 passkey profiles scoped to Microsoft Entra ID groups. Does the change allow a user to enable and disable the feature themselves?Users may register Microsoft Entra passkeys on Windows devices if permitted by administrator policy configuration. -
(Update)Microsoft Entra ID: General Availability of passkey profiles and migration for existing Passkeys (FIDO2) tenants
MC1221452 · planForChange · normal · Updated 10/30/2026 23:17
Services: Microsoft Entra
Read message
Updated October 30, 2026: We have updated the timeline. Thank you for your patience. [Introduction] Starting in March 2026, Microsoft Entra ID will introduce passkey profiles and synced passkeys to General Availability (GA). This update allows administrators to opt in to a new passkey profiles experience that supports group-based passkey configurations and introduces a new passkeyType property. Important: Only tenants that already have Passkeys (FIDO2) enabled are affected by this update. The passkeyType property enables admins to configure: Device-bound passkeys Synced passkeys Both If your tenant already has Passkeys (FIDO2) enabled and you do not opt in to passkey profiles during the initial rollout window, your tenant will be automatically migrated to the passkey profiles schema at the date range specified below. When this occurs: Existing Passkey (FIDO2) authentication method configurations will be moved into a Default passkey profile. The passkeyType value will be set based on the tenant’s current attestation settings. Synced passkeys will be enabled for tenants with attestation enforcement disabled. No new authentication methods are enabled as part of this migration. This migration also impacts Authentication methods registration campaign set to “Microsoft managed” state, which uses passkey configuration settings to determine which registration prompts are shown to users. Authentication Methods Registration Campaign changes (Microsoft-Managed Only) Tenants are impacted when all the following conditions are met: The Passkeys (FIDO2) authentication method policy is Enabled Authentication methods registration campaign is set to “Microsoft managed” state Allow self-service setup is Enabled Target specific AAGUIDs is not selected (no AAGUID restrictions configured) The Authentication Methods Registration Campaign state is set to Microsoft-managed The tenant has at least one user enabled for both synced passkeys and device‑bound passkeysOnly users who are enabled for both synced passkeys and device‑bound passkeys, with no passkey profile restrictions configured (i.e. attestation enforcement, AAGUID restrictions), will receive a passkey registration nudge during sign‑in. For these tenants, Microsoft-managed registration campaign settings will be updated after passkey profile automatic migration is complete. We will roll out changes incrementally to in-scope tenants according to the timeline outlined below. [When this will happen] Passkey profile and Synced passkeys General Availability Public cloud Worldwide, GCC: Rollout begins in early March 2026 and is expected to complete by late March 2026 GCC High, DoD clouds: Rollout begins in early May 2026 and is expected to complete by late May 2026 USNat, USSec: Rollout begins in early April 2027 (previously early October 2026) and is expected to complete by late April 2027 (previously late October 2026) Automatic migration for existing passkeys (FIDO2) enabled tenants Public cloud Worldwide, GCC: Rollout begins in early May 2026 and is expected to complete by late June 2026 GCC High, DoD clouds: Rollout begins in early February 2027 (previously early October 2026) and is expected to complete by late February 2027 (previously late October 2026) USNat, USSec: Rollout begins in early May 2027 (previously early October 2026) and is expected to complete by late May 2027 (previously late October 2026) Authentication Methods registration campaign changes in Microsoft-Managed state (for in-scope tenants): Public cloud Worldwide, GCC: Rollout begins in early May 2026 and is expected to complete by late June 2026 [How this affects your organization] Automatic migration for existing passkeys (FIDO2) enabled tenants What will happen: If you have not opted in to passkey profiles by your automatic enablement period, your tenant will be migrated to passkey profiles. Your existing Passkey (FIDO2) configurations will be migrated into a Default passkey profile New passkeyType property will be auto-populatedIf enforce attestation is enabled, then device-bound allowed If enforce attestation is disabled, then device-bound and synced allowed Any existing key restrictions will remain intact Any existing user targets will be assigned to the Default passkey profile Authentication Methods registration campaign changes in Microsoft-Managed state (for in-scope tenants) What will happen: Microsoft-managed registration campaign settings will be updated: "Targeted authentication method” will change from Microsoft Authenticator to “passkeys (FIDO2)”. “Days allowed to snooze” setting will change from 3days to “1 day”. This setting will no longer be configurable. “Limited number of snoozes” setting will change from Enabled to "Disabled”. This setting will no longer be configurable. The default user targeting will be updated from voice call or text message users to all multifactor authentication (MFA) capable users. What is the end user impact: Once the above changes have taken effect, users targeted in the registration campaign will begin to receive passkey registration nudges during sign-in flows after they have completed multifactor authentication. [What you can do to prepare] If you want a configuration different from the migration defaults, review the timeline above and opt in to passkey profiles before your tenant’s automatic enablement window begins. Then configure the Default passkey profile’s passkeyType to your preferred values. We also recommend: Review your registration campaign configuration, especially if its set to Microsoft-managed. If you do not want registration campaign to target passkeys, you can:Switch the registration campaign state to Enabled and continue targeting Microsoft Authenticator, or Set the registration campaign state to Disabled. Update runbooks and help content so your help desk and end users understand any changes in passkey availability or behavior. Learn more: Enable passkeys for your organization - Microsoft Entra ID | Microsoft Learn How to Enable Passkey (FIDO2) Profiles in Microsoft Entra ID (preview) - Microsoft Entra ID | Microsoft Learn How to Enable Synced Passkeys (FIDO2) in Microsoft Entra ID (preview) - Microsoft Entra ID | Microsoft Learn Synced passkeys FAQ - Microsoft Entra ID | Microsoft Learn [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
Microsoft Teams: Granular Conditional Access for Teams meetings
MC1532256 · planForChange · normal · Updated 10/30/2026 22:09
Services: Microsoft Teams
Read message
[What and Why:] Granular Conditional Access for Teams meetings enables organizations to apply more targeted access controls to help protect sensitive meetings. Administrators can use Conditional Access policies to enforce specific access requirements for selected meetings, helping ensure that participants meet organizational security requirements before joining. [Rollout Schedule:] Public Preview (Worldwide): We will begin rolling out in late November 2026 and expect to complete by late November 2026. General Availability (Worldwide): We will begin rolling out in early January 2027 and expect to complete by late January 2027. [Impact on Your Organization:] Administrators can make approved authentication requirements available for specific meetings, allowing organizers to require additional verification such as multifactor authentication, device compliance, or location-based controls. Participants must satisfy the applicable Conditional Access policy before joining the protected meeting. [Action Required/Recommendations:] To prepare, administrators should configure required authentication contexts and associated Conditional Access policies in Microsoft Entra, publish authentication contexts to Microsoft Teams, and enable meeting authentication requirements through Teams meeting policies. [Compliance considerations:] QuestionAnswer Does the change include an admin control?Yes. Admins configure authentication contexts, Conditional Access policies, and Teams meeting policies. -
Activity in other accounts and orgs panel improvements
MC1532248 · stayInformed · normal · Updated 10/30/2026 22:06
Services: Microsoft Teams
Read message
[What and Why:] Stay up-to-date with what's happening in your other accounts and organizations with the 'Activity in Other Accounts and Orgs' panel. Preview and open chats, channels, and other activity in other accounts and orgs from your main Teams window - no tenant switching required. [Rollout Schedule:] Public Preview (Worldwide): We will begin rolling out in mid-November 2026 and expect to complete by late November 2026. General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out in late January 2027 and expect to complete by early February 2027. [Impact on Your Organization:] Customers who are signed in to multiple Teams accounts or have accepted an invitation to join another organization as a guest with Teams will see an updated 'Activity in Other Accounts and Orgs' panel on the bottom left of their Teams client. Previously, users could only see new activity (e.g. reactions, @mentions) in the panel. With the new enhancements, users can preview content and filter across familiar categories, allowing for faster triage and streamlined external collaboration. There is no change to any security posture or admin policy. Teams is simply allowing users to navigate to chats and channels from other accounts and organizations faster and without tenant switching. Users who only have one Teams account and organization are not impacted by this change. [Action Required/Recommendations:] No preparation by admins is needed. If desirable, admins can encourage people in their organization who do a lot of external collaboration to try this feature out, as it will relieve one of the biggest pain points we've heard from customers about external collaboration: tenant switching. [Compliance considerations:] No compliance considerations identified. Review as appropriate for your organization. -
Microsoft Teams: Pinch to zoom in on shared screens
MC1532242 · stayInformed · normal · Updated 10/30/2026 21:59
Services: Microsoft Teams
Read message
[What and Why:] Get a closer look at shared content in Teams calls and meetings with pinch-to-zoom using your touchpad. Quickly zoom in to make small text and detailed visuals easier to see, then zoom back out for the full view. Existing zoom controls remain available. [Rollout Schedule:] General Availability (Worldwide): We will begin rolling out on late November 2026 and expect to complete by late November 2026. Targeted Release (Worldwide): We will begin rolling out on mid November 2026 and expect to complete by mid November 2026. [Impact on Your Organization:] This capability will be enabled for all meetings by default, as an improvement to additional zooming controls. [Action Required/Recommendations:] Review your organization’s sharing policies and inform users and support teams about the addition to existing sharing experience. [Compliance considerations:] No compliance considerations identified. Review as appropriate for your organization. -
Microsoft Defender XDR: Investigate suspicious Microsoft Teams calls and meetings with advanced hunting
MC1532241 · stayInformed · normal · Updated 10/30/2026 21:58
Services: Microsoft Defender XDR
Read message
[What and why] When investigating a suspicious Microsoft Teams call or meeting, your security team needs to understand what happened, who initiated the activity, and the organization associated with the initiator. The CallActivityEvents table in Microsoft Defender XDR advanced hunting provides visibility into activities performed during Teams calls and meetings in your organization. Security teams can use this information to investigate suspicious activity, review related messages, and correlate findings with other security signals. This capability is available to organizations with Microsoft Defender for Office 365 Plan 2. [Rollout schedule] General Availability (Worldwide): Beginning in early November 2026 and expected to complete by mid-November 2026 [Impact on your organization] Who is affected Security operations and threat hunting teams in organizations with Microsoft Defender for Office 365 Plan 2 Platforms and services Microsoft Defender XDR advanced hunting Microsoft Teams What will happen Your security team can use the CallActivityEvents table on the Advanced hunting page in the Microsoft Defender portal to: Understand what happened by reviewing activities performed during Teams calls and meetings, including whether an activity succeeded or failed and whether it was performed on the initiator or another participant. Investigate who initiated an activity by reviewing the initiator's identity, account and membership types, organization, tenant region, and Teams client platform. Identify the organizer by reviewing the identity and tenant of the user who organized the call or meeting. Review related messages by joining CallActivityEvents with the MessageEvents table using ThreadId to examine recorded messages exchanged in the associated call or meeting chat. Broaden investigations by correlating call and meeting activity with other available advanced hunting data. Call and meeting activity data will also be available through the event streaming API and Microsoft Sentinel API, allowing security teams to incorporate the data into existing security monitoring and investigation workflows. [Action required and recommendations] Share this update with your security operations and threat hunting teams. We recommend that you: Review the CallActivityEvents schema and identify how call and meeting activity can support your existing Teams investigation workflows. Ensure analysts who will use this capability have appropriate advanced hunting access. Microsoft documents that permissions are required to run advanced hunting queries. If your organization uses the event streaming API or Microsoft Sentinel API, review your data ingestion configuration and plan to incorporate call and meeting activity into your existing workflows. Learn more Advanced hunting - Microsoft Defender Advanced hunting overview in Microsoft Defender XDR - Microsoft Defender XDR | Microsoft Learn CallActivityEvents table in the advanced hunting schema - Microsoft Defender | Microsoft Learn MessageEvents table in the advanced hunting schema - Microsoft Defender XDR | Microsoft Learn Security Operations Guide for Teams protection - Microsoft Defender for Office 365 | Microsoft Learn [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
Power Apps - Information regarding the end of support for record-level copresence in model-driven apps
MC1532182 · stayInformed · normal · Updated 10/30/2026 20:23
Services: Power Apps
Read message
On November 30, 2026, record-level copresence in model-driven apps will have reached end of support. How does this affect me? Users will no longer see who else is working on the record or have access to a presence card. This change does not affect record sharing, user pictures, or status in grids and lookups. The underlying behavior when multiple users edit the same record hasn't changed: if two users save changes to the same record, the most recent save still overwrites any previous changes. What's changing is visibility — without copresence, users won't see that someone else may be viewing or editing the record at the same time. What action do I need to take? Admins should inform their users that copresence in model-driven apps will no longer be available after November 30, 2026. Users can continue to reach other users they collaborate with directly using existing entry points in the app, or through supporting apps like Outlook and Teams. -
(Updated) Microsoft Edge: Microsoft 365 Copilot will support summarization and contextual grounding
MC1187682 · stayInformed · normal · Updated 10/30/2026 20:15
Services: Microsoft 365 suite
Read message
Updated October 30, 2026: We have updated the content. Thank you for your patience. [Introduction:] Microsoft Edge for Business will soon support summarization and contextual grounding with Microsoft 365 Copilot Chat. This enhancement enables users to ask Copilot questions about multiple open browser tabs, and YouTube videos directly from the Edge side pane. This message is associated with Microsoft 365 Roadmap ID 496364, 499423, and 499424. [When this will happen:] General Availability (Multiple browser tabs and YouTube videos): Currently Available [How this affects your organization:] Who is affected: Users signed in to Microsoft Edge for Business with their Entra ID and who have access to Microsoft 365 Copilot. What will happen: Users will be able to ask Copilot questions about open browser tabs, and YouTube videos. The feature will be off by default. If Copilot is restricted from accessing page content via Data Loss Prevention (DLP) or the EdgeEntraCopilotPageContext policy, it will be suppressed to maintain DLP integrity. Existing DLP and policy configurations will be respected. [What you can do to prepare:] This rollout will happen automatically by the specified date; no admin action is required before rollout. Ensure users who need this capability have access to Microsoft 365 Copilot. Ensure your tenant is configured to support Microsoft 365 Copilot and that eligible users meet all licensing prerequisites, including Entra ID sign-in and applicable Microsoft 365 service plans. Review your current DLP and Edge policy configurations to determine potential impact. Notify users about this upcoming capability. Update internal documentation if needed. Learn more: Microsoft 365 Copilot Chat in Edge and Access to Page Content | Microsoft Edge | Microsoft Learn Microsoft Edge - Policies | Microsoft Edge | Microsoft Learn [Compliance considerations:] QuestionAnswer Does the change introduce or significantly modify AI/ML or agent capabilities that interact with or provide access to customer data?Yes. Microsoft 365 Copilot introduces contextual grounding and summarization using generative AI across browser tabs, and YouTube videos. Does the change provide end users any new way of interacting with generative AI?Yes. Users can now ask Copilot questions about open browser tabs and documents directly from the Edge sidepane, enabling real-time summarization and contextual responses. Does the change modify Data Loss Prevention (DLP) policies or enforcement?Yes. If DLP or the EdgeEntraCopilotPageContext policy restricts access, Copilot will be suppressed from accessing page content to maintain DLP integrity. Does the change include an admin control, and can it be controlled through Entra ID group membership?Yes. Admins can manage access to Copilot’s contextual grounding capabilities via DLP settings and Edge policy configurations, which can be scoped using Entra ID group membership. -
(Updated) Microsoft Entra: Choose your own telephony provider now generally available
MC1519855 · stayInformed · normal · Updated 10/30/2026 19:34
Services: Microsoft Entra
Read message
Updated October 30, 2026: We have updated this post with additional information as the feature is now generally available. Thank you for your patience. [What and why] Choose Your Own Telephony Provider (CYOT) is now generally available in Microsoft Entra ID. With CYOT, your organization can deliver SMS and voice authentication through a supported telecom provider of its choice. You purchase the provider's offer in Microsoft Security Store and manage the commercial relationship directly with the provider. Microsoft-provided SMS and voice authentication begins retiring on February 1, 2027. To keep SMS and voice authentication available for users who need it, set up CYOT before that date. Microsoft recommends phishing-resistant authentication methods, such as passkeys, instead of SMS or voice. Use telephony-based authentication only for users who have a business, regulatory, or technical need for it. [What you need to do] If your organization plans to use CYOT: Identify users who need SMS or voice. Confirm which users have a requirement that phishing-resistant methods can't meet. Choose a provider. Compare the supported telecom providers on coverage, channels, pricing, support, and compliance. Check purchasing requirements. Confirm that you have a paid Azure subscription that is eligible for Security Store purchases, and that you have the Owner role, or Contributor plus Role Based Access Control Administrator. Estimate costs. Review provider pricing and Azure hosting costs. Set up and roll out. Follow Set up SMS and voice. Start in evaluation mode, then increase traffic to your provider in stages. Complete your transition before February 1, 2027. Review the guidance for the retirement of Microsoft-provided SMS and voice authentication. Learn more Choose your own telephony provider for SMS and voice authentication Set up SMS and voice with your own telecom provider Troubleshoot SMS and voice Protect against telephony fraud Plan for resiliency and high availability Frequently asked questions Passkeys by default and retirement of Microsoft-provided SMS and voice authentication -
(Updated) Microsoft Teams: Meeting memory file generation
MC1429018 · planForChange · normal · Updated 10/30/2026 18:24
Services: Microsoft Teams
Read message
Updated October 30, 2026: We have updated the timeline. Thank you for your patience. [What and Why] Microsoft Teams is introducing AI generated meeting memory files that capture key insights from meetings (formerly archive files). These files help Microsoft 365 Copilot and Facilitator deliver more accurate context aware responses while maintaining strong privacy controls by not storing raw meeting content. This capability supports enterprise ready AI by improving knowledge grounding while keeping data secure and manageable. This message is associated with Microsoft 365 Roadmap ID 558933. [Rollout Schedule] Targeted Release: Beginning early January 2027 (previously early November 2026) and expected to complete mid-January 2027 (previously mid-November 2026) General Availability (Worldwide): Beginning mid-January 2027 (previously early December 2026) and expected to complete late January 2027 (previously early January) Teams admin center controls for this feature will be available approximately four weeks before memory file generation begins. The dates above reflect when admin controls become available. [Impact on Your Organization:] Who is affected Microsoft Teams administrators Users with Microsoft 365 Copilot or Facilitator capabilities enabled Platforms/Services Microsoft Teams Microsoft 365 Copilot SharePoint Embedded What will happen AI meeting memory files (.meeting files) will be generated for meetings where Intelligent Recap is turned on. The feature is enabled by default in your organization. Memory files are stored in a tenant-owned SharePoint Embedded container, not in user storage. You can control the default expiration time for these files within your organization. Users cannot directly view or access memory files. When the feature is released, Facilitator will use the memory to answer questions about meetings and responses include citations linking to meeting recaps or invites. In the future, Copilot will also use the memory to answer questions about meetings. Memory files cannot be modified, renamed, or moved. All content in memory files is AI-generated. No raw transcript snippets are stored. Memory generation requires all of the following:Meeting memory is enabled for your organization. Intelligent Recap is enabled for the meeting. Memory files are not created for:Meetings with sensitivity labels that include encryption End-to-end encrypted meetings Meetings with restricted copying or forwarding Access and data protection:Only users with access to the meeting can receive responses grounded in its memory and AI tools do not surface insights to users who do not have meeting access. Memory knowledge is only shared with users who are in the same tenant as the meeting organizer. [Action Required / Recommendations] No immediate action is required. However, administrators should review configuration settings and consider organizational policy alignment. Admins can enable or disable this feature in the Teams admin center. Recommended actions: Review the AI archive setting in Teams admin center before rollout. Setting path: Meeting Policies > Meeting Memory". Evaluate the default expiration period, which is set to five years (1,825 days), and adjust retention settings as needed to align with compliance policies. Communicate this capability to helpdesk teams and compliance stakeholders. Monitor availability of the memory setting in Teams admin center and review or update settings when they become available. Memory file generation will begin 4 weeks after the setting is released to your organization. Learn more: AI Archives for Microsoft Teams Meetings | Microsoft Teams | Microsoft Learn [Compliance considerations] QuestionAnswer Does the change store new customer data, and if so, where, and is the data cached or permanently stored?Yes. The change introduces AI-generated meeting memory files that are stored in a tenant-owned SharePoint Embedded container and retained according to a configurable retention period. Does the change alter how existing customer data is processed, stored, or accessed?Yes. Meeting transcripts and metadata are processed into structured AI memory files that enable downstream AI systems such as Copilot and Facilitator to reason over meeting content. Does the change introduce or significantly modify AI or machine learning capabilities that interact with or provide access to customer data?Yes. Copilot and Facilitator use AI meeting memory files to generate context-aware responses grounded in prior meeting content. Does the change provide users any new way of interacting with generative AI?Yes. Users can interact with Copilot and Facilitator, which leverage meeting memory data to answer questions and provide insights about meetings. Does the change modify retention policies, holds, or deletion workflows?Yes. AI meeting memory files are governed by a default retention period of five years and are automatically deleted upon expiration. Does the change include an admin control, and can it be controlled through Entra ID group membership?Yes. Administrators can enable or disable AI meeting memory generation and configure retention settings in the Teams Admin Center. -
Microsoft Purview: Retirement of Data Security Posture Management (DSPM) classic and DSPM for AI classic experiences
MC1481315 · planForChange · normal · Updated 10/30/2026 18:20
Services: Microsoft Purview
Read message
Updated October 30, 2026: We have updated the timeline. Thank you for your patience. [What and why] Beginning mid-March 2027, Microsoft will start retiring the Microsoft Purview Data Security Posture Management (DSPM) classic and DSPM for AI classic experiences. Retirement will be completed by end of March 2027. As part of our continued investment in Microsoft Purview Data Security Posture Management, we have unified DSPM capabilities into a single experience that helps organizations discover, protect, and investigate data risks across traditional data sources and AI applications and agents. [Rollout schedule] Retirement (Worldwide, GCC, GCC High, and DoD): Beginning in mid-March 2027 (previously late January) and expected to complete in late March 2027 (previously late January) [Impact on your organization] Who is affected Organizations currently using DSPM classic or DSPM for AI classic in the Microsoft Purview portal Microsoft Purview administrators Security administrators and compliance administrators responsible for monitoring and managing data security posture Platforms and services Microsoft Purview portal Microsoft Purview Data Security Posture Management (DSPM) Microsoft Purview DSPM for AI (classic) Microsoft Purview DSPM (classic) What will happen DSPM classic and DSPM for AI classic experiences will no longer be available after retirement. Organizations must use the current Microsoft Purview DSPM experience for posture management and investigation workflows. The current DSPM experience provides centralized access to posture metrics, recommendations, reports, investigations, and data security objectives. Most new DSPM capabilities and innovations are delivered through the current DSPM experience. Organizations that have already transitioned to the current DSPM experience and no longer rely on DSPM classic or DSPM for AI classic do not need to take action. [Action required and recommendations] Action is required only if your organization currently uses DSPM classic or DSPM for AI classic. Recommended actions: Review your current DSPM workflows and identify any processes that depend on DSPM classic or DSPM for AI classic. Confirm access to the current DSPM experience by navigating to Microsoft Purview portal > Solutions > DSPM. Transition any remaining workflows that rely on DSPM classic or DSPM for AI classic to the current DSPM experience before retirement. Notify Microsoft Purview administrators, security teams, and compliance teams about this retirement. Update internal documentation, training materials, operational procedures, and help desk guidance. Learn more Learn about Microsoft Purview Data Security Posture Management (DSPM) | Microsoft Learn Map tasks that you used to do in Microsoft Purview Data Security Posture Management (DSPM) for AI | Microsoft Learn [Compliance considerations] QuestionAnswer Does the change alter how admins can monitor, report on, or demonstrate compliance activities?Yes. Administrators will no longer use DSPM classic or DSPM for AI classic experiences and will instead use the current unified DSPM experience for posture monitoring, reporting, recommendations, investigations, and objectives. The capability remains available but through a different experience. -
Interim guidance for Cuba’s 2026 daylight saving time change
MC1531085 · stayInformed · normal · Updated 10/30/2026 03:15
Services: Windows
Read message
What and why On October 27, 2026, the government of the Republic of Cuba announced that the country will remain on daylight saving time instead of ending it as scheduled on November 1, 2026. Clocks will not be set back one hour at 2:00 a.m. on November 1. Cuba will remain at UTC-04:00 without interruption until November 7, 2027. Microsoft plans to release an update to support this time zone change as part of the November 2026 security update. Until then, devices will display an incorrect local time. Affected organizations should use the temporary guidance below until they can install the update. Rollout schedule October 27, 2026: The government of Cuba announced the daylight saving time change. November 1, 2026: Cuba’s time change takes effect. Affected Windows devices might display an incorrect local time until the November 2026 security update is installed or the temporary workaround is applied. November 2026: A Windows update to support the time zone change is planned for the following supported platforms: Windows 11, versions 26H2, 26H1, 25H2, and 24H2 Windows 10 Enterprise LTSC 2021 Windows Server 2025, Windows Server 2022, Windows Server 2019, and Windows Server 2016 November 7, 2027: Cuba is scheduled to end the extended daylight saving time period. Impact on your organization Beginning November 1, 2026, affected devices using the (UTC-05:00) Havana time zone will display an incorrect local time until the November 2026 security update is installed, or the temporary workaround is applied. As a temporary workaround, affected devices can use (UTC-04:00) Georgetown, La Paz, Manaus, San Juan. This option provides the required UTC-4 offset but has different geographic and display information. It should not be treated as a permanent replacement for the Havana time zone. Action required/recommendations Beginning November 1, 2026, affected devices in Cuba should use this temporary fixed-offset workaround until the November 2026 security update is installed: Go to Settings > Time & language > Date & time, turn off Set time zone automatically, and change the time zone from (UTC-05:00) Havana to (UTC-04:00) Georgetown, La Paz, Manaus, San Juan. Install the November 2026 security update when it becomes available. After installing the update, turn Set time zone automatically back on. If automatic time-zone selection is enabled and location services are available, Windows will select the appropriate time zone based on the device’s location. Otherwise, manually select (UTC-04:00) Havana. Verify that the device displays the correct local date and time. Don’t continue using the fixed-offset alternative as a permanent replacement. Compliance considerations No compliance considerations are identified. Review as appropriate for your organization. Additional information Daylight Saving Time & Time Zone Blog Interim guidance for Cuba DST 2026 How Windows manages time zone changes Daylight saving time help and support -
An updated version of the October 2026 Scan Cab is available
MC1531060 · preventOrFixIssue · normal · Updated 10/30/2026 02:01
Services: Windows
Read message
IMPORTANT: This notice is only relevant for environments where: Visual Studio 2026, Visual Studio 2022, Visual Studio 2019, or Visual Studio 2017 is installed. Excel 2016 is installed. Scan Cab is used to check for update compliance The October 2026 Scan Cab was deployed before 7:00 PM PDT on October 29, 2026. What and why: An updated version of the October 2026 Scan Cab was made available at 7:00 PM PDT on October 29, 2026. It includes new metadata for these out-of-band security updates: Visual Studio 2026 18.11, Visual Studio 2022 17.14, Visual Studio 2019 16.11, and Visual Studio 2017 15.9 Excel 2016 (KB5002934) These updates address security vulnerabilities across Visual Studio, and Excel 2016. See the Additional information section for vulnerability details. Rollout schedule: The updated October 2026 Scan Cab was made available at 7:00 PM PDT on October 29, 2026. Who is affected: IT administrators who downloaded the Scan Cab before 7:00 PM PDT on October 29, 2026, should re-acquire and re-deploy it if the Scan Cab is used to assess updates for environments with the affected Visual Studio or Excel versions listed above. No action is required if Scan Cab isn’t used to assess updates for these products. Because non-Microsoft applications may also use Scan Cab, review the documentation for your organization’s software and update-deployment tools to determine whether this applies to your environment. What will happen: Administrators can re-deploy the updated Scan Cab via their usual processes. For detailed guidance, see the Additional information section below. Additional information: Updated Scan Cab: Download the new Scan Cab CVE-2026-92392: HTTP/2 upload Use-After-Free CVE-2026-111497: Google: CVE-2026-111497 Buffer overflow vulnerability in the Brotli decoder Visual Studio Security Updates: Visual Studio 2026, Visual Studio 2022, Visual Studio 2019, and Visual Studio 2017 Excel 2016 Security Update (KB5002934): Download Center Announcing a smaller WSUS Scan Cab - Microsoft Tech Community: Learn more about WSUS and the Scan Cab process Using WUA to Scan for Updates Offline - Win32 apps: Windows Update Agent (WUA) can be used to scan computers for security updates without connecting to Windows Update WSUS and the Catalog Site: The Catalog Site used by WSUS to import updates and drivers -
Microsoft Teams: Threads will become the default layout for new channels created with Microsoft Graph
MC1530957 · planForChange · normal · Updated 10/29/2026 23:11
Services: Microsoft Teams
Read message
[What and why] We're updating the default message layout for new Microsoft Teams channels created through the Microsoft Graph v1.0 Create channel API (POST /v1.0/teams/{team-id}/channels). When a channel creation request doesn't specify the layoutType property, the new channel will use the Threads layout instead of the Posts layout. This change applies only to newly created channels. Existing channels won't change. [Rollout schedule] General Availability (Worldwide, GCC, GCC High, DoD): Beginning in late November 2026 and expected to complete by late November 2026 [Impact on your organization] Who is affected Organizations with applications, scripts, or automated provisioning workflows that create Microsoft Teams channels through Microsoft Graph without specifying the layoutType property Platforms and services Microsoft Teams and Microsoft Graph v1.0 Create channel API What will happen If layoutType is omitted, new channels will use the Threads layout instead of the Posts layout. If "layoutType": "post" is specified, new channels will use the Posts layout. If "layoutType": "chat" is specified, new channels will use the Threads layout. The API value for the Threads layout is "chat", not "threads". Existing channels won't change. Channel creation requests that explicitly specify a supported layout aren't affected. [Action required and recommendations] Notify developers and owners of applications or automation that create Teams channels through Microsoft Graph. If your organization requires new channels to continue using the Posts layout, update channel creation requests to explicitly include "layoutType": "post" before rollout begins. For third-party solutions, contact the provider to confirm how the solution specifies the channel layout. If Threads is your desired layout, no request changes are required to adopt the new default. Review and test dependent workflows for compatibility with Threads. Learn more Create channel - Microsoft Graph v1.0 | Microsoft Learn [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
(Updated) Viva Engage: Community feeds improvements
MC1187781 · stayInformed · normal · Updated 10/29/2026 23:10
Services: Microsoft Viva
Read message
Updated October 29, 2026: We have updated the timeline. Thank you for your patience. [Introduction:] We’re introducing a simpler way to view conversations in Viva Engage communities, organized by recent posts rather than recent activity. This new view is designed to make it easier for users to follow discussions and will be available as an option, alongside the current system, for those who prefer sorting by recent activity and filtering to new conversations only. This message is associated with Microsoft 365 Roadmap ID 513275. [When this will happen:] General Availability (Worldwide): We will begin rolling out in November 2026 (previously October) and expect to complete by the end of November 2026 (previously end of October). [How this will affect your organization:] This change should align better with how people expect to browse and engage with content in their communities, while still preserving the triage flow for those who prefer it. Who is affected: All Viva Engage users in your organization. Current experience: Communities default to “new” and “recent activity” if there’s any new content (posts or replies). If there’s no new content, the feed falls back to “all.” Unread indicators on content only exist in the “new” feed. New experience: The feature will be ON by default. Communities will default to “all” and “recent posts”: Unread indicators will exist in both the “new” and “all” feeds. A sticky user preference will be introduced:If someone changes the feed (new/all) or sort order (recent posts/recent activity), we will maintain that setting across their communities. If someone picks “new” and there’s no new content in the next community, we will fall back to “all” for that community visit, but “new” will remain the preference for that user. [What you can do to prepare:] No action is required. [Compliance considerations:] No compliance considerations identified, review as appropriate -
Microsoft 365 apps: Draft mode for official Brand Kits
MC1530954 · stayInformed · normal · Updated 10/29/2026 23:10
Services: Microsoft 365 apps
Read message
[What and why] We’re introducing Draft Mode for official Brand Kits. Draft Mode gives Brand Managers a workspace to make and review changes before publishing them. Changes remain in draft and do not affect the current live Brand Kit until the updated kit is published. [Rollout schedule] General Availability (Worldwide): Beginning in late October 2026 and expected to complete by early November 2026 [Impact on your organization] Who is affected Brand Managers who manage official Brand Kits and viewers who access them Platforms and services Microsoft 365 apps What will happen Brand Managers can create, review, and refine changes before publishing an updated official Brand Kit. Changes made in Draft Mode do not affect the current live Brand Kit until the updated kit is published. Viewers will continue to have access to the current live Brand Kit while changes are being prepared. Organizations can maintain a consistent brand experience while Brand Kit updates are in progress. [Action required and recommendations] No action is required to prepare for this feature. We recommend informing Brand Managers about Draft mode and aligning on your organization’s internal review and publishing process for official Brand Kit updates. Learn more Create and Manage Official Brand Kits in Microsoft Copilot | Microsoft Support [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
Microsoft Teams: Explicit consent for PSTN participants in one-to-one calls
MC1530950 · stayInformed · normal · Updated 10/29/2026 23:09
Services: Microsoft Teams
Read message
[What and why] Microsoft Teams will support explicit consent for participants connected through the public switched telephone network (PSTN) in one-to-one Teams calls. When explicit consent is required, PSTN participants will hear an audio prompt when recording or transcription starts and can use their phone keypad to consent or decline. Participants who decline can remain in the call but stay muted. This capability extends the existing Teams calling policy for explicit consent to one-to-one PSTN calls. [Rollout schedule] General Availability (Worldwide): Beginning in early December 2026 [Impact on your organization] Who is affected PSTN participants in applicable one-to-one Teams calls where explicit consent for recording or transcription is required What will happen PSTN participants will hear an audio prompt requesting consent when recording or transcription starts. Participants can press 1 to consent or 2 to decline. The PSTN participant's audio will not be included in the recording or transcript before consent is provided. PSTN participants who decline can remain in the call but stay muted. This capability uses the existing explicit consent setting in Teams calling policies. It does not introduce a new admin policy setting. The existing explicit consent setting is disabled by default. This update applies to one-to-one PSTN calls. It does not change compliance recording or the existing consent experience for meetings and group calls. [Action required and recommendations] No new policy configuration is required if your existing explicit consent configuration meets your organization's requirements. Review your organization's Teams calling policies and explicit consent requirements. In the Teams admin center, go to Voice > Calling policies and review Require participant agreement for recording and transcription for applicable policies. If explicit consent is already enabled, prepare users and support teams for the new PSTN keypad consent experience. If your organization wants to require explicit consent, enable the existing setting in the appropriate calling policies. Update internal guidance so users understand that PSTN participants who decline consent remain muted while the consent requirement applies. Learn more Configure call recording, transcription, and captions in Teams - Microsoft Teams | Microsoft Learn Set-CsTeamsCallingPolicy (MicrosoftTeams) | Microsoft Learn [Compliance considerations] QuestionAnswer Does the change include an admin control?Yes. The capability uses the existing Teams calling policy for explicit recording consent rather than introducing a new policy setting. Microsoft Learn documents management through Teams calling policy and the -ExplicitRecordingConsent parameter. -
(Updated) Microsoft Authenticator: Usability improvements for iOS and Android
MC1521604 · stayInformed · normal · Updated 10/29/2026 20:51
Services: Microsoft Entra
Read message
Updated October 29, 2026: We have updated the timeline. Thank you for your patience. [What and why] We’re updating Microsoft Authenticator with several usability improvements across iOS and Android. These updates include a refreshed home experience, clearer guidance for accounts that need to be restored, improvements to restoration and sign-in flows, and additional prompts designed to help keep Authenticator working reliably. Availability and timing vary by platform. [Rollout schedule] General Availability (Worldwide, GCC, GCC High, and DoD): Beginning in early November 2026 (previously October) and expected to complete in late November 2026 The improved restoration experience for push notifications and passwordless sign-in will be available on iOS first, with Android planned to follow in January 2027. [Impact on your organization] Who is affected Users of Microsoft Authenticator on iOS and Android Platforms and services Microsoft Authenticator for iOS and Android What will happen Improved Authenticator home experience, iOS and Android: The Authenticator home page is being updated to improve the experience when users view and manage their accounts. On Android, this update will be available in November 2026. iOs: Android: Clearer notification for accounts that haven’t been restored, iOS and Android: Users with accounts that have not yet been restored will see a banner informing them that those accounts require attention . Improved first-run guidance for account restoration, iOS and Android: The first-run experience will more clearly show which accounts need to be restored, giving users additional context during Authenticator setup. App rating prompt during sign-in, iOS only: Users may see an option to rate Microsoft Authenticator as part of the sign-in experience, giving them an opportunity to provide feedback about the app. Improved restoration experience for push notifications and passwordless sign-in: The restoration flow is being improved for users who use push notifications and passwordless sign-in. This improvement will be available on iOS first, with Android planned for January 2027. Prompt to exclude Authenticator from battery optimization, Android only: After successfully completing an interactive authentication, users may see a non-blocking prompt to exclude Authenticator from Android battery optimization. Excluding the app from battery optimization helps users stay signed in and continue receiving work or school notifications. The prompt will not block authentication. [Action required and recommendations] No configuration action is specified in this request. Inform your help desk and security operations teams about the updated Authenticator experiences. Update internal user guidance and screenshots that show the previous Authenticator experiences. [Compliance considerations] No compliance considerations identified. -
(Updated) Microsoft Teams: Initiate side conversations within the meeting chat window
MC1523090 · stayInformed · normal · Updated 10/29/2026 20:40
Services: Microsoft Teams
Read message
Updated October 29, 2026: We have updated the timeline. Thank you for your patience. [What and Why:] Microsoft Teams will enable meeting participants to start and continue one-to-one or small-group conversations directly from the meeting chat experience. Users can create a side conversation without leaving the meeting context, helping them coordinate, ask questions, share information, and collaborate in parallel while keeping the main meeting discussion focused. [Rollout Schedule:] General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out in early December 2026 (previously early January 2027) and expect to complete in mid-January 2027 (previously late January). [Impact on Your Organization:] Users will be able to start or continue private 1:1 and group chats directly from the meeting chat experience, without leaving the meeting window. Existing chat history is preserved, so conversations remain part of the user’s regular Teams chat history. [Action Required/Recommendations:] No admin action is required. This feature does not introduce a new chat surface, admin policy, or meeting option. Users can turn off the side-chat tab experience if they prefer not to use it. [Compliance considerations:] No compliance considerations identified. Review as appropriate for your organization. -
Power Apps - Information regarding the end of availability for copresence in Plan Designer
MC1530697 · stayInformed · normal · Updated 10/29/2026 19:50
Services: Power Apps
Read message
Starting November 30, 2026, copresence in Plan Designer will no longer be available. How does this affect me? Multiple users can still open the same plan, but Plan Designer will no longer allow simultaneous edits. If multiple users make changes to the same plan, one user's changes may overwrite another user's unsaved changes. What action do I need to take? Please coordinate with other users who edit plans to communicate when saving changes and handing off editing responsibilities to prevent unsaved work from being overwritten. -
(Updated) Transitioning Teams Android Device Management from Teams admin Center to the Teams Rooms Pro Management portal
MC1227622 · planForChange · normal · Updated 10/29/2026 18:46
Services: Microsoft Teams, Microsoft 365 for the web
Read message
Updated October 28, 2026: We have updated the timeline. Thank you for your patience. [Introduction] As part of our ongoing mission to deliver a modern, secure, and scalable one-stop management portal for admins, we are transitioning Teams Android device management from the Teams admin center (TAC) to the Teams Rooms Pro Management portal (PMP). This move consolidates management of all Teams devices, including Teams Rooms on Windows, Teams Rooms on Android, Teams phones, and Teams panels, into a single unified portal, providing IT admins a consistent and seamless experience for managing devices at scale. This message is associated with Roadmap ID 555235. [When this will happen:] General Availability (Worldwide): Effective July 2, 2026, the rollout is 100% complete across all regions in the Public cloud. General Availability (GCC): We expect to start the rollout by Nov 2026 and complete by late-Nov 2026 (previously late-Oct). General Availability (GCC High and DoD): Effective October 8, 2026, the rollout is 100% complete across GCCH and DoD clouds. Device management deprecation in TAC: The deprecation of Teams device management capabilities in TAC will begin in November 2026 and will roll out in phases based on device type and feature readiness. For public clouds - SIP, MTR-A and Panels devices administration experience in TAC will start deprecating by Mid-November and will complete by end of November. Phones devices administration experience in TAC will start deprecating by early December and complete by December 15th. For Gov clouds ( GCC, GCC-H and DoD) For GCC-H and DoD, device administration experience in TAC will start deprecating by early December and will be completed by December 15th. For GCC, devices administration experience in TAC will start deprecating by early January and will be completed by January 30th. Phones devices administration experience for all Sovereign cloud (GCC, GCC-H, DoD) customers will start deprecating by early January and will be completed by January 30th. [How this affects your organization:] Who is affected: Admins who manage Teams Rooms on Android, Teams phones, Teams panels, and SIP Phones. What will happen: Android device management capabilities, including inventory, updates, health monitoring, and settings will transition from TAC to PMP for the device types, Teams Rooms on Android, Teams phones, Teams panels and SIP Phones. The following capabilities will be available and enhanced in PMP:Device inventories for Android-based Teams Rooms, phones, and panels, including metadata and app information Remote device actions (restart, log collection, sign-in/out, provisioning, and more) Update management Device settings management Device health monitoring SIP device management PMP will become the primary portal for all Teams device management. By January 2027, overlapping TAC capabilities (updates, settings, restart, sign-in/out, log collection, provisioning) will be deprecated in TAC. The article below serves as the main information source for this transition. It has been updated with the latest timelines, milestones, migration guidance, and readiness steps. We will keep updating it as the rollout progresses.Transitioning Teams Android Device Management from Teams Admin Center to the Teams Rooms Pro Management Portal - Microsoft Teams | Microsoft Learn [What you need to do to prepare:] Monitor the below article for any feature specific updates and timelines. This article also provides migration guidance and pre-requisites for successful transition to PMP.Transitioning Teams Android Device Management from Teams Admin Center to the Teams Rooms Pro Management Portal - Microsoft Teams | Microsoft Learn Learn more about Pro Management portal features with these Teams Rooms Pro Management short YouTube videos. Update internal helpdesk and IT documentation to reference PMP as the new management portal. [Compliance considerations] No compliance considerations identified, review as appropriate for your organization. -
Microsoft Teams: Impersonation protection for Teams meetings
MC1530613 · planForChange · normal · Updated 10/29/2026 18:34
Services: Microsoft Teams
Read message
[What and Why:] Impersonation protection for Teams meetings helps users identify potentially deceptive participants and meeting organizers. When Teams detects a potential impersonation attempt, it surfaces warnings and risk indicators to help users recognize suspicious identities and make more informed decisions when joining or participating in a meeting. [Rollout Schedule:] General Availability (Worldwide): We will begin rolling out in mid-December 2026 and expect to complete by late December 2026. [Impact on Your Organization:] Meeting Impersonation Protection provides users with additional context to determine whether the people they interact with in Microsoft Teams meetings are who they claim to be. By surfacing warnings and risk indicators when potential impersonation is detected, Teams helps users recognize suspicious identities earlier and make safer decisions. [Action Required/Recommendations:] No immediate admin action is required. Admins should familiarize themselves with the new protection experience and communicate the change to users and security teams as appropriate. [Compliance considerations:] QuestionAnswer Does the change introduce or modify security controls?Yes. The feature surfaces meeting impersonation warnings and risk indicators to help users make safer meeting decisions. -
SharePoint Lists: Refreshed user experience
MC1530610 · stayInformed · normal · Updated 10/29/2026 18:32
Services: SharePoint Online
Read message
[What and Why:] Microsoft is introducing a refreshed user experience for SharePoint Lists to make common actions easier to find, improve navigation, and provide greater visibility into views and active filters. The refreshed experience includes a reorganized command bar, clearer breadcrumb navigation for lists that use folders, more prominent view selection and creation, visible filter pills, and consolidated view customization options. These updates are intended to make everyday list tasks more intuitive and help users better understand and manage the information displayed in their views. [Rollout Schedule:] General Availability (Worldwide): We will begin rolling out in mid-December 2026 and expect to complete by late December 2026. [Impact on Your Organization:] The refreshed experience includes: Existing SPFx extensions, column formatting, and view formatting are not expected to be affected beyond the command bar placement behavior described above. [Action Required/Recommendations:] No action is required to enable the refreshed experience. Organizations that use custom command bar formatters should review the updated command placement behavior and the SharePoint command bar formatting documentation. [Compliance considerations:] No compliance considerations have been identified. Review as appropriate for your organization. -
Engage plugin for Copilot Cowork and Autopilot: General availability
MC1530609 · stayInformed · normal · Updated 10/29/2026 18:31
Services: Microsoft Viva
Read message
[What and Why:] We are introducing the Engage plugin for Copilot Cowork and Autopilot, with general availability targeted for November 16, 2026. The plugin brings Engage conversations and actions into Copilot workflows. Users can catch up on community discussions, find relevant information, understand employee questions and feedback, and draft or publish updates without switching to Engage. [Rollout Schedule:] General Availability (Worldwide): We will begin rolling out in mid-November 2026 and expect to complete by mid-November 2026. [Impact on Your Organization:] Users can bring Engage into workflows alongside information from other connected sources. For example, they can use recent meetings and Teams discussions to prepare an update and publish it to an Engage community. The plugin supports finding and summarizing conversations, reviewing replies and reactions, creating posts, replying to discussions, and adding reactions. It operates using the signed-in user’s existing Engage permissions and does not grant additional access to content or actions. The plugin is off by default. Administrators control its availability to their organization or selected users and groups. [Action Required/Recommendations:] No action is required unless you want to make it available to your organization. Consider updating your helpdesk and internal user guidance if you plan to enable the plugin. Administrators should review Manage plugins for Copilot Cowork for licensing requirements, deployment options, and access controls. For user setup and usage instructions, see Use plugins with Copilot Cowork. [Compliance considerations:] No compliance considerations identified. Review as appropriate for your organization. -
Policy-based in-box app removal extended to multi-session environments
MC1530443 · stayInformed · normal · Updated 10/29/2026 17:10
Services: Windows
Read message
What and why: Policy-based app removal now supports multi-session environments. Use it to manage the removal of supported in-box apps on devices running Windows 11 Enterprise and Education, version 24H2 and later. This capability applies to preinstalled Microsoft Store apps and other MSIX/APPX-packaged apps. Rollout schedule: October 2025: The policy "Remove default Microsoft Store packages from the system" became available. April 2026: The policy began including a dynamic app removal list. October 2026: The policy is available for use in multi-session environments. Impact on your organization: This change is helpful if your organization runs Windows 11, versions 26H2, 25H2, or 24H2 Enterprise and Education editions in multi-session environments. It helps provide fewer unwanted apps, simpler provisioning, and a more tailored desktop for your users. Action required/recommendations: Just use a standard, policy-based approach to remove select apps, using Microsoft Intune integrated with Group Policy. Learn more in: Policy-based in-box app removal documentation Dynamically remove apps from managed Windows 11 devices Policy-based removal of pre-installed Microsoft Store apps Compliance considerations: No compliance considerations are identified. Review as appropriate for your organization. -
Microsoft Entra ID: Risk-based anti-bot verification (CAPTCHA) for SMS and voice authentication
MC1518029 · preventOrFixIssue · normal · Updated 10/29/2026 16:27
Services: Microsoft Entra
Read message
Updated October 26, 2026: We have updated the timeline. Thank you for your patience. [What and why] Microsoft Entra ID is adding safeguards to reduce automated abuse of telephony-based authentication. SMS and voice authentication options are not being removed. Some users who use SMS or voice for first-factor sign-in may be asked to complete a risk-based anti-bot verification step (CAPTCHA) before a code is sent. [Rollout schedule] Rollout began in mid-October 2026 and is ongoing. Users may see an anti-bot verification step for first-factor telephony-based authentications. [Impact on your organization] Who is affected Some users who use SMS or voice as a first-factor sign-in method Platforms and services Microsoft Entra ID telephony-based authentication using SMS or voice for first-factor sign-in What will happen Some users might see an additional risk-based anti-bot verification step (CAPTCHA) before Microsoft sends the telephony code. The experience is determined based on client behaviors, so not every user or sign-in attempt will be affected. If the verification experience does not load because of restrictive network or firewall settings, affected users might not be able to complete the flow until required endpoints are allowed. Endpoint guidance is included in the linked documentation below. [Action required and recommendations] Prepare your help desk and user communications for the possibility of an anti-bot verification step before a telephony code is sent. Review the linked documentation for network-readiness guidance, including any approved endpoint or allowlist requirements. Continue moving users to phishing-resistant authentication methods, such as passkeys, where possible. Learn more Understanding telephony fraud risk for Microsoft Entra multifactor authentication - Microsoft Entra ID | Microsoft Learn Risk-based anti-bot verification (CAPTCHA) for telephony-based sign-in - Microsoft Entra ID | Microsoft Learn Passkeys by default and retirement of Microsoft-provided SMS and voice authentication - Microsoft Entra ID | Microsoft Learn [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
(Updated) Microsoft Defender for Office 365: New email submissions data in Advanced Hunting
MC1484009 · stayInformed · normal · Updated 10/28/2026 23:39
Services: Microsoft Defender XDR
Read message
Updated October 28, 2026: We have updated the timeline. Thank you for your patience. [What and Why:] Microsoft Defender for Office 365 is introducing new email submissions data in Advanced Hunting in Microsoft Defender. The new submissions tables provide security operations teams with greater visibility into email submission activity and results, enabling analysts to query submission activity alongside other Defender data and build hunting and detection workflows tailored to their organization. [Rollout Schedule:] Public Preview (Worldwide): We will begin rolling out in mid-November 2026 (previously early October 2026 and expect to complete by early December 2026 (previously early October). General Availability (Worldwide): We will begin rolling out late November 2026 (previously late October) and expect to complete by mid-December 2026 (previously mid-November). [Impact on Your Organization:] Who is affected: - Security operations teams that use Advanced Hunting in Microsoft Defender. - Admins and analysts who investigate email submissions and submission results. Platforms/Services: - Microsoft Defender for Office 365 - Microsoft Defender XDR - Advanced Hunting What will happen: - Two new Advanced Hunting tables will be available: SubmissionEvents and SubmissionResults. - SubmissionEvents provides information about email submission events. - SubmissionResults provides information about the results associated with those submissions. - Security teams can query submission information directly and correlate it with other Microsoft Defender XDR data. - The tables can be used with Advanced Hunting custom detections, allowing organizations to create detections based on submission activity that is important to their SOC workflows. [Action Required/Recommendations:] No immediate action is required. Additional documentation for the new tables will be provided as part of the release. [Compliance considerations:] No compliance considerations identified. Review as appropriate for your organization. -
Frontier expands to include public previews in Microsoft Teams, new Outlook for Windows, OneDrive, and SharePoint
MC1529472 · stayInformed · normal · Updated 10/28/2026 23:01
Services: Microsoft 365 suite
Read message
[What and Why:] Frontier now covers more of Microsoft 365. Starting in November 2026, users enrolled in Frontier will start getting eligible public preview features in Microsoft Teams, new Outlook for Windows, OneDrive, and SharePoint, in addition to Copilot. Instead of looking in different places for previews, admins use one program and one setting to give the users they choose early access across Microsoft 365. Frontier is optional and controlled by your admins. It is separate from each user's Standard release or Deferred release preference, which still decides when users receive features once they're generally available. If you already have users enrolled in Frontier, they don't need to re-enroll. Release options in the Microsoft 365 admin center: Frontier (preview access): Opt in specific users and groups, or all users, to get eligible public preview features before general availability. Standard release (general availability): Receive updates as soon as they're generally available. This is the default. Deferred release (general availability): Receive eligible major updates approximately 30 days after Standard release begins, allowing more time for validation and readiness. Learn more: Get started with the Microsoft Frontier Program [Rollout Schedule:] November 2026: Users enrolled in Frontier will start getting eligible public preview features in Microsoft Teams, new Outlook for Windows, OneDrive, and SharePoint, in addition to Copilot. [Impact on Your Organization:] Frontier makes early access to Microsoft 365 previews simpler and more predictable. Instead of looking in different places for previews, your organization gets eligible public preview features for Microsoft Teams, new Outlook for Windows, OneDrive, SharePoint, and Copilot through one program, managed from one admin setting. Admins choose which users and groups take part, and everyone else stays on their Standard release or Deferred release schedule, so it's clear who gets what and when. In November 2026, admins can also manage Frontier, Standard release, and Deferred release together in one place in the Microsoft 365 admin center. Early access gives you time to prepare guidance and support teams, and a way to share feedback before features are broadly released. [Action Required/Recommendations:] Users enrolled in Frontier will start seeing eligible preview features in Microsoft Teams, new Outlook for Windows, OneDrive, and SharePoint, in addition to the Copilot preview features they get today. If your Frontier setting is All users, every user with the right licenses will get these preview features. Users not enrolled in Frontier see no change. They keep getting features based on their Standard release or Deferred release preference. A Microsoft Copilot license is no longer required to enroll users in Frontier. Users need licenses for the products they want to preview. For example, to use Frontier features for Teams, users need a license that includes Microsoft Teams. Enrolled users without that license aren't shown that product's Frontier features. Users in Targeted release aren't automatically enrolled in Frontier. Preview features may change before general availability. Future additions to Frontier will be announced in Message center. We recommend that administrators: Review your current Frontier enrollment. In the Microsoft 365 admin center, go to Copilot > Settings > View all > Copilot Frontier. You can choose No access (default), All users, or Specific users and groups. If Frontier is set to All users, decide whether everyone should get preview features. If not, switch to Specific users and groups. If you're new to Frontier, consider starting with a pilot group and expanding over time. A pilot group could be IT staff, an innovation team, or employees who want to test the latest features. If you use Targeted release, enroll the users you want to get preview features in Frontier. Targeted release users aren't enrolled automatically, and Targeted release retires in January 2027. Make sure enrolled users have licenses for the products they will preview. If you use the Microsoft 365 Insider (for business) program to validate production builds, keep doing so. To try eligible preview features offered through Frontier, enroll the users who will participate. Let your helpdesk, change management teams, and pilot groups know that enrolled users will start seeing preview features. Until the unified release preferences experience is available, admins can continue to manage Frontier enrollment through Copilot settings in the Microsoft 365 admin center. In November 2026, you can manage Frontier, Standard release, and Deferred release together in the unified release preferences experience, or continue to manage Frontier through Copilot settings. For details, see MC1490899. [Compliance considerations:] Does the change include an admin control?Yes. Admins manage Frontier enrollment (No access, All users, or Specific users and groups) through Copilot Settings in the Microsoft 365 admin center. [Additional Resources:] Frontier expands to more Microsoft 365 public previews | Microsoft Community Hub Get started with the Microsoft Frontier Program Explore AI Early Access in Microsoft 365 | Microsoft Frontier -
Microsoft 365 admin center: Usage reports to manage metered consumption costs for Microsoft 365 Copilot Chat (preview)
MC1069563 · stayInformed · normal · Updated 10/28/2026 18:20
Services: Microsoft 365 suite
Read message
Updated October 28, 2026: We have updated the timeline below. Thank you for your patience. To help you manage metered consumption costs for Microsoft 365 Copilot Chat, we will introduce a new Message consumption usage report in the Microsoft 365 admin center. The new report will give you visibility into billed messages associated with your Microsoft 365 Copilot pay-as-you-go billing policies and includes total messages consumed, cumulative and daily time series, and messages per user, per billing policy, per agent, and per agent-user pair. The new report will roll out in preview. During the preview stage, the report will display a maximum of 30 days of message consumption history. Usage information from prior to May 3, 2025, will not be available in the report. This message refers to Microsoft Copilot in a pay-as-you-go model. A Microsoft Copilot license is not required. This message is associated with Microsoft 365 Roadmap ID 490738. [When this will happen:] Public Preview: Available now. General Availability (Worldwide): We will begin rolling out in end of April 2027 (previously early January) and expect to complete by end of May 2027 (previously end of January). [How this will affect your organization:] After you have set up pay-as-you-go billing for Microsoft 365 Copilot, either in the Microsoft 365 admin center or the Microsoft Power Platform admin center, and you have enabled agent usage in your organization, you will see a new report including metrics for messages consumed at the levels of tenant, users, agents, and agent-user. To help you mitigate overspending, you will see alerts when users have consumed more than 2000 billed messages. This new report will be on by default and will be available in the Microsoft admin center at Reporting > Usage > Microsoft 365 Copilot > Message consumption: [What you need to do to prepare:] This rollout will happen automatically by the specified date with no admin action required before the rollout. You may want to notify any admins that manage agents on the integrated apps page about this feature. Learn more: Microsoft 365 reports in the admin center - Message consumption -
The October 2026 Windows non-security preview update is now available
MC1529014 · stayInformed · normal · Updated 10/28/2026 17:05
Services: Windows
Read message
The October 2026 non-security preview update is now available for Windows 11, versions 26H2, 26H1, and 25H2. Information about the contents of this update is available in the release notes, which are accessible from the Windows 11 update history page. To learn more about the different types of monthly quality updates, see Understanding Windows monthly updates. Highlights for the Windows 11, version 26H2 update: File Explorer’s context menu is faster and easier to customize, with options to choose which commands and app extensions appear and how they’re organized. XBOX mode now has a refreshed Gaming Task View with quick access to Exit to Desktop and Power Options, making key system actions easier to access while gaming. Magnifier now supports per-monitor zoom, a contrast theme to reduce glare, and viewport locking to keep a display’s magnified view in place. Phone Link now lets you preview recent messages and notifications in Start by hovering over them, without opening the item. Cloud rebuild can reinstall Windows using an image and drivers downloaded from Windows Update, including when Windows can’t start; no USB media or custom image is required. For instructions on how to install this update, see the KB article for your operating system listed below: Windows 11, versions 26H2 and 25H2: KB5127936 Windows 11, version 26H1: KB5127653 Note: With recent and upcoming Windows updates over the next few months, a limited number of consumer and business devices might experience one additional restart during installation. This one‑time restart occurs after a Secure Boot certificate update is applied as part of the Secure Boot update process. -
(Updated) Microsoft Viva: Targeted audience surveys in the Copilot dashboard
MC1446805 · stayInformed · normal · Updated 10/28/2026 16:48
Services: Microsoft Viva
Read message
Updated October 28, 2026: We have updated the timeline. Thank you for your patience. [What and why] We're introducing targeted audience surveys in the Copilot dashboard. This feature enables authorized users to launch Microsoft Viva Pulse surveys for predefined Copilot user populations without creating or maintaining recipient lists. Survey audiences are dynamically based on Copilot dashboard data and can be scoped using existing dashboard filters. This helps organizations gather feedback from Copilot users while reducing administrative effort associated with audience management. This message is associated with Microsoft 365 Roadmap ID 568072. [Rollout schedule] Public Preview: Beginning mid-August 2026 and expected to complete by late September 2026 General Availability (Worldwide): Beginning late November 2026 (previously late October) and expected to complete by mid-December 2026 (previously mid-November) [Impact on your organization] Who is affected Organizations with 50 or more Copilot licenses Users assigned the CxO or CxO-delegate role in the Copilot dashboard Organizations using Microsoft Viva Pulse and the Copilot dashboard Platforms and services Microsoft Viva Pulse Copilot dashboard Microsoft Viva Insights What will happen The feature will be enabled by default for eligible organizations. Survey results appear in your existing Pulse and dashboard surfaces. Authorized users with the CxO or CxO-delegate role can send Viva Pulse surveys to predefined Copilot user cohorts from the Copilot dashboard. Available survey audiences include:All Copilot Licensed Users All Copilot Active Users Survey audiences will be generated using Copilot dashboard data and respect supported dashboard filters. Individual employee identities are not exposed through audience selection. Viva Insights exclusion lists continue to be honored for survey distribution. [Action required and recommendations] No action is required to enable this feature. We recommend that administrators: Review who has been assigned the CxO or CxO-delegate role in the Copilot dashboard. Inform change leaders that targeted audience surveys are available. Verify that Viva Insights exclusion lists are current and accurately reflect users who should be excluded from surveys. Administrators can disable this feature in the Microsoft 365 admin center by navigating to Setup > Microsoft Viva > Feature access management > Viva Pulse and turning off Targeted Audience Surveys. [Compliance considerations] QuestionAnswer Does this change include an admin control?Yes. Administrators can disable the feature through Feature access management in Microsoft Viva Pulse. Does this change affect how users communicate or provide feedback within Microsoft 365?Yes. This feature provides a new method for authorized users to collect employee feedback by sending Viva Pulse surveys to predefined Copilot user audiences from Copilot dashboard. Does this change process customer or organizational data in a new way?Yes. Survey audiences are generated using Copilot dashboard data and existing audience filters to identify eligible recipients for Viva Pulse surveys. Can users be assigned access to this feature through role-based permissions?Yes. Only users assigned the CxO or CxO-delegate role in Copilot dashboard can create surveys for the predefined Copilot audiences. -
(Updated) Microsoft Teams: Analytics for desk utilization in Teams Pro Management portal
MC1490906 · stayInformed · normal · Updated 10/28/2026 16:37
Services: Microsoft Teams
Read message
Updated October 28, 2026: We have updated the timeline. Thank you for your patience. [What and Why:] We’re expanding analytics in the Microsoft Teams Pro Management portal to include utilization insights for bookable desks. IT admins will be able to better understand how desk spaces are being used across their organization, with insights into desk utilization, reservations, occupancy, and peak usage patterns. Desk-specific filters, including location and desk mode, will help admins analyze usage across their workplace and make more informed space planning decisions. For utilization analytics to be enabled, a desk needs to have one or more peripheral device associated, and the desk needs to be licensed with Microsoft Teams Shared Space license or Microsoft Teams Shared Space - Single Space license. This message is associated with Microsoft 365 Roadmap ID 570648 [Rollout Schedule:] General Availability (Worldwide): We will begin rolling out on early December 2026 (previously early November) and expect to complete by mid-January 2027 (previously mid-December 2026). [Impact on Your Organization:] These insights can help organizations better understand how bookable desks are being used and inform workplace and space planning decisions. [Action Required/Recommendations:] To enable utilization analytics, a desk must have one or more associated peripheral devices and be licensed with a Microsoft Teams Shared Space or Microsoft Teams Shared Space - Single Space license. [Compliance considerations:] No compliance considerations identified. Review as appropriate for your organization. -
Dynamics 365 Contact Center – Boost contact center efficiency with Real Time Streaming Analytics
MC1528937 · stayInformed · normal · Updated 10/28/2026 15:31
Services: Dynamics 365 Apps
Read message
We are introducing Real-Time Streaming Analytics in the new Contact Center supervisor workspace application, providing supervisors with near real-time visibility into Dynamics 365 Contact Center performance without requiring dashboard refreshes. This feature will be generally available starting Oct 30th with a phased rollout across all regions through November 9, 2026. How does this affect me? This feature enables supervisors to monitor contact center performance and take action from a single experience. Key capabilities include:Monitor performance in near real-time:Track key metrics such as queue backlog, service level, abandon rate, representative presence, available capacity, and conversations handled over time without refreshing the dashboard. Display live performance on wallboards: View continuously updated metrics in full-screen mode to provide a shared view of contact center performance. Analyze queue and representative performance: Drill down from high-level summaries to queue-level and representative-level views to identify performance changes and potential issues. Take action directly from the dashboard: Adjust representative queues, presence, skills, and capacity profiles within the supervisor experience. Configure performance thresholds: Set thresholds for key metrics and use color-coded indicators to identify At Risk and Critical conditions. Supervisors and contact center administrators can access the Contact Center Supervisor Workspace through the Supervisor Dashboard URL and connect to their organization to begin monitoring real-time contact center performance. What do I need to do to prepare? This message is for awareness, and no action is required. If you would like more information on this feature, please visit Boost contact center efficiency with real-time streaming analytics. -
Microsoft SharePoint: SharePoint Server access through the mobile apps will be retired
MC1528013 · planForChange · normal · Updated 10/27/2026 23:26
Services: SharePoint Online
Read message
[What and why] Microsoft is retiring SharePoint Server access through the standalone SharePoint mobile apps for iOS and Android. After this change, these apps will support SharePoint Online only. [Rollout schedule] Retirement (Worldwide, GCC, GCC High, DoD): Beginning November 27, 2026 [Impact on your organization] Who is affected Organizations with users who access SharePoint Server through the SharePoint mobile apps for iOS or Android Platforms and services SharePoint mobile apps for iOS and Android SharePoint Server What will happen Users will no longer be able to access SharePoint Server through the standalone SharePoint mobile apps for iOS or Android. The SharePoint mobile apps will support SharePoint Online only. [Action required and recommendations] Before this change takes effect: Notify users who access SharePoint Server through the SharePoint mobile apps that this access is being retired. Update your internal documentation and support materials as appropriate. Learn more About SharePoint mobile app | Microsoft Support SharePoint mobile app for Android | Microsoft Support [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
Microsoft 365 admin center: Retirement of selected Search Analytics capabilities
MC1528009 · planForChange · normal · Updated 10/27/2026 23:24
Services: Microsoft 365 suite
Read message
[What and why] We are retiring selected Search Analytics capabilities for the following search experiences: Microsoft/Bing Search, including Work Search Teams Search Outlook/WXP Search, including Word, Excel, and PowerPoint Windows Search Work results Microsoft365.com This retirement applies to Summary, User/Query, and Answer Analytics associated with these search experiences within Search & intelligence > Insights in the Microsoft 365 admin center. This change is limited to the analytics capabilities listed above. It does not: Retire the Search & intelligence > Insights experience as a whole Affect SharePoint Search Analytics Affect Connector Analytics Change users' ability to search in any of the affected applications [Rollout schedule] Worldwide, GCC: Rollout will begin in late November 2026 and is expected to complete by mid-December 2026. [Impact on your organization] Who is affected Administrators who use Summary, User/Query, or Answer Analytics for the affected search experiences. Platforms and services Microsoft 365 admin center, Search & intelligence > Insights Microsoft/Bing Search, including Work Search Teams Search Outlook/WXP Search, including Word, Excel, and PowerPoint Windows Search Work results Microsoft365.com What will happen After the retirement reaches your tenant, administrators will no longer be able to access Summary, User/Query, or Answer Analytics for the affected search experiences. Other Search Analytics capabilities not listed in this notice remain outside the scope of this retirement. SharePoint Search Analytics and Connector Analytics are not affected. Users' ability to search in the affected applications will not change. [Action required and recommendations] No action is required if your organization does not use these analytics capabilities. Otherwise, we recommend that you: Review whether your organization relies on the affected Summary, User/Query, or Answer Analytics reports. Identify administrators or reporting stakeholders who use these reports, filters, exports, or related reporting integrations. Export or retain any required analytics data before retirement, subject to the confirmed historical-data availability. Update any reporting processes or integrations that depend on the affected analytics capabilities. -
Join button will require HTTPS meeting links
MC1528007 · planForChange · normal · Updated 10/27/2026 23:22
Services: Exchange Online
Read message
[What and Why:] We're updating the Join button experience in Outlook to use HTTPS meeting join URLs. Beginning the week of November 30, 2026, the Join button will no longer appear for meetings that contain only an HTTP join URL. [Rollout Schedule:] General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out in late November 2026 and expect to complete by late December 2026. [Impact on Your Organization:] Meetings with HTTPS join URLs will continue to display the Join button. Organizations using online meeting providers, add-ins, or custom integrations that generate HTTP-only join URLs may find that the button no longer appears for those meetings. Most organizations are not expected to be affected. [Action Required/Recommendations:] No action is needed if your meeting providers and integrations already generate HTTPS join URLs. If you use third-party online meeting providers, add-ins, or custom integrations, confirm that they generate HTTPS join URLs. Work with the provider or integration owner to update HTTP URLs and validate newly created meeting invitations before the change takes effect. [Compliance considerations:] No compliance considerations identified. Review as appropriate for your organization. -
Microsoft Authenticator: Improved backup and restore experience for Android
MC1528006 · stayInformed · normal · Updated 10/27/2026 23:21
Services: Microsoft Entra
Read message
[What and why] We’re improving the backup and restore experience in Microsoft Authenticator for Android. When setting up Authenticator on a new device, users will receive guidance tailored to whether they still have access to their previous device. They will also receive guidance on using Authenticator passkeys for cross-device sign-in. This experience is already available on iOS. To use backup and restore on a new Android device, users must enable Google One backup and screen lock. [Rollout schedule] General Availability (Worldwide, GCC, GCC High, and DoD): Beginning in mid-January 2027 and expected to complete in mid-January 2027 [Impact on your organization] Who is affected Users of Microsoft Authenticator on Android Platforms and services Microsoft Authenticator for Android What will happen When setting up Authenticator on a new Android device, users will see clearer guidance based on whether they still have access to their previous device. Users will receive guidance for using Authenticator passkeys for cross-device sign-in. Work or school accounts are not backed up. This is not changing. Backup will continue to support TOTP credentials for Microsoft personal accounts and third-party accounts. Users must enable Google One backup and screen lock to use this backup and restore experience. Backup and restore is supported only when Microsoft Authenticator is installed in the Android personal profile. It is not supported when Authenticator is installed in an Android work profile. [Action required and recommendations] No admin action is required. Organizations may choose to inform users about the updated restore experience on Android devices. [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
Microsoft Excel: Edit with Copilot in Excel on iPhone
MC1528003 · stayInformed · normal · Updated 10/27/2026 23:21
Services: Microsoft 365 apps
Read message
[What and Why:] Edit with Copilot makes it easier to edit and transform your Excel workbooks on your phone using natural language. Copilot can continue working on your task even when you move away from the app, so you can come back when the work is ready. Chat mode also remains available when you want to ask questions and get insights without making changes to your workbook. [Rollout Schedule:] General Availability (Worldwide): We will begin rolling out late October 2026 and expect to complete by late November 2026. [Impact on Your Organization:] This feature helps customers move beyond viewing spreadsheets on their phones and complete meaningful Excel work when a laptop is not readily available. Users can get quick answers from workbook data, make targeted updates, generate or modify formulas and visualizations, and review workbook changes from their iPhone. For organizations, the feature can help employees respond more quickly while travelling, between meetings, or working away from their primary device. It uses existing Microsoft 365 authentication, licensing, permissions, metering, and tenant-level Copilot controls. Enterprise grounding continues to respect the user’s existing permissions to Microsoft 365 content, including SharePoint, OneDrive, and Teams. Users remain responsible for reviewing AI-generated content and workbook changes before relying on them. Changes saved to a shared workbook are visible to other people who have access to that file, and users can use available review, undo, or version-history capabilities when needed. [Action Required/Recommendations:] None [Compliance considerations:] No compliance considerations identified. Review as appropriate for your organization. -
Microsoft Entra ID: Reminder to migrate from Microsoft-provided SMS and voice authentication
MC1528000 · planForChange · normal · Updated 10/27/2026 23:17
Services: Microsoft Entra
Action required by: 02/01/2027 08:00
Read message
[What and why] This is a reminder of the upcoming retirement of Microsoft-provided SMS and voice authentication in Microsoft Entra ID, previously announced in MC1426371 (July 13, 2026) and MC1434201 (GCC, July 20, 2026). Microsoft-provided SMS and voice authentication will retire starting February 1, 2027. Complete your migration before rollout begins to avoid interrupting users' sign-in experience. SMS and voice are vulnerable to phishing and SIM-swap attacks. Microsoft recommends passkeys for stronger, phishing-resistant protection. You can also migrate to another supported authentication method or retain SMS and voice by configuring a customer-managed telecom provider (CYOT) through the Microsoft Security Store. [Rollout schedule] Retirement (Worldwide and GCC): Beginning February 1, 2027, and expected to complete in early February 2027. Complete migration or configure CYOT before February 1, 2027, rather than waiting for the rollout to reach your tenant. [Impact on your organization] Who is affected Organizations and users that rely on Microsoft-provided SMS or voice authentication Customer-managed telecom providers configured through the Microsoft Security Store are not affected. Platforms and services Microsoft Entra ID authentication What will happen Users with another registered sign-in method will use that method. They will not be required to register a passkey to continue signing in. Users whose only registered sign-in method is SMS or voice can use SMS or voice one final time to verify their identity. They must then register a passkey before continuing sign-in. [Action required and recommendations] If your organization uses Microsoft-provided SMS or voice, complete these steps before February 1, 2027: Identify affected users. Review who relies on SMS or voice, especially users with no other registered sign-in method. Complete migration. Help affected users register and start using passkeys or another supported authentication method before rollout begins. Configure CYOT if you need to retain SMS or voice. Configure a customer-managed telecom provider through the Microsoft Security Store before rollout begins. Notify users and your helpdesk. Explain the deadline, required actions, and the passkey-registration requirement for users who only have SMS or voice registered. If your organization does not use Microsoft-provided SMS or voice, no action is required for this retirement. Learn more Migration guidance Passkeys in Microsoft Entra ID Choose a telephony provider for SMS and voice authentication - Microsoft Entra ID | Microsoft Learn [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
(Updated) Microsoft Entra: Windows Hello for Business and macOS Platform SSO as standalone MFA factors
MC1450134 · planForChange · normal · Updated 10/27/2026 22:54
Services: Microsoft Entra
Read message
Updated October 27, 2026: We have updated the timeline. Thank you for your patience. [What and why] Microsoft Entra will soon recognize Windows Hello for Business (WHfB) and macOS Platform Single Sign-On (PSSO) as standalone multifactor authentication (MFA) factors in supported authentication scenarios. Today, WHfB and macOS PSSO can satisfy MFA requirements during primary sign-in, but users may still be required to register and use an additional passkey or authentication method for certain step-up authentication prompts, Authentication Strength policies, and sign-in frequency checks. After this rollout, users who authenticate with WHfB or macOS PSSO will be able to satisfy supported MFA requirements without registering an additional passkey. This change helps organizations expand the use of phishing-resistant authentication methods and reduce reliance on less secure authentication methods. As part of this change, a user's WHfB and macOS PSSO credentials will be displayed in My Security Info as auto-registered passkeys. [Rollout schedule] General Availability (Worldwide, GCC): Beginning in early November 2026 (previously early October) and expected to complete in late December 2026 (previously mid-December) [Impact on your organization] Who is affected Organizations using Microsoft Entra ID Users who authenticate with Windows Hello for Business Users who authenticate with macOS Platform SSO Organizations using Conditional Access Authentication Strength policies Platforms and services Microsoft Entra ID Windows Hello for Business macOS Platform SSO Conditional Access Authentication Strength policies What will happen After rollout: Users signing in with WHfB or macOS PSSO can complete supported MFA challenges without requiring a separate passkey. WHfB and macOS PSSO will satisfy supported MFA requirements for step-up authentication scenarios. WHfB and macOS PSSO can be used during 2FA to satisfy supported Authentication Strength policy requirements. WHfB and macOS PSSO can be used during 2FA to satisfy supported sign-in frequency challenge requirements. Users whose only MFA method is WHfB or macOS PSSO will be considered MFA-capable. Users who sign in with only a password will no longer be automatically prompted to register an additional MFA method if WHfB or macOS PSSO is their only registered MFA credential. Users with WHfB or macOS PSSO credentials, will be able to see them listed in My Security Info as auto-registered passkeys. [Action required and recommendations] No configuration changes are required. We recommend reviewing user onboarding and MFA registration processes before rollout. Because WHfB and macOS PSSO credentials are device-bound, users may not be able to complete MFA challenges from devices where those credentials are not available. Recommended actions: Update onboarding guidance to ensure users register at least one portable MFA method. Consider requiring users to register a synced passkey or Microsoft Authenticator passkey in addition to WHfB or macOS PSSO. Review custom Authentication Strength policies to confirm WHfB and macOS PSSO are allowed where appropriate. Update user documentation because users with only WHfB or macOS PSSO registered will no longer be automatically guided to register an additional MFA method. Learn more (To be updated closer to GA rollout.) Plan a Windows Hello for Business deployment | Security | Windows | Microsoft Learn Prepare users to provision and use Windows Hello for Business | Security | Windows | Microsoft Learn [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
The November and December 2026 security updates require a restart for hotpatch-enabled Windows Server 2022 devices
MC1527979 · stayInformed · normal · Updated 10/27/2026 22:35
Services: Windows
Read message
What and why The November and December 2026 security updates for Windows Server 2022 will be released as standard updates rather than hotpatch updates. Some of the security improvements in these updates change components that cannot be updated without a restart. As a result, Windows Server 2022 devices enrolled in hotpatching will need to restart to complete installation in each month. This change does not affect hotpatch updates for Windows Server 2025 or Windows 11, which remain scheduled for November and December. Rollout schedule November 2026: Standard update with restart required for all Windows Server 2022 devices including those that are hotpatch-enabled. December 2026: Standard update with restart required for all Windows Server 2022 devices including those that are hotpatch-enabled. January 2027: Planned baseline update month with restart required. February 2027: Next hotpatch update expected. Impact on your organization Hotpatch-enabled Windows Server 2022 devices will require a restart to complete installation of each month’s security update. These devices will remain enrolled in hotpatch updates. No change for Windows Server 2022 devices not using hotpatch updates; standard updates already require a restart. Note: Hotpatch-enabled Windows Server 2025 and Windows 11 devices are not affected by this change. Action required / recommendations Plan for device restarts when deploying the November and December 2026 security updates for Windows Server 2022. No additional configuration is required to stay enrolled in hotpatch updates. Compliance considerations No additional compliance action is required. Update installation and restart behavior will be reflected in update history and compliance reports as usual. Additional information You can track the hotpatch update calendar on the Windows Server release information page. -
(Updated) OneDrive for Business: Improved Windows Desktop sync error messages for max path length
MC1422063 · stayInformed · normal · Updated 10/27/2026 22:07
Services: Microsoft OneDrive
Read message
Updated October 27, 2026: We have updated the timeline. Thank you for your patience. [What and why] We are improving the OneDrive sync experience on Windows desktop to provide clearer, more actionable guidance when file and folder paths exceed the supported 520-character limit. The updated experience will show exactly how many characters a path exceeds the limit and will provide a guided flow to rename or move affected items so they can sync successfully. This improvement addresses a common OneDrive sync issue by reducing user confusion, minimizing workflow disruption, and helping users resolve errors faster. This update is associated with Microsoft 365 Roadmap ID 557563. [Rollout schedule] General Availability (Worldwide): Beginning January 2027 (previously end of October 2026) and expected to complete by end of January 2027 (previously end of November 2026) [Impact on your organization] Who is affected All users of the OneDrive sync client on Windows desktop Platforms and services OneDrive for Business (Windows desktop sync client) What will happen Max path errors are one of the most commonly reported issues by OneDrive sync users. Currently, when a file or folder path exceeds the 520-character sync limit, the error message only states how many characters the path exceeds the limit and asks users to shorten it. In addition, File Explorer limitations may prevent users from renaming paths over 260 characters, and the sync client may stop syncing until the issue is resolved. As part of this improved error experience, when users encounter max path errors, the sync client will continue running and users will be guided through a custom rename and move experience. With this update: The sync client will continue running when users encounter max path errors Users will be guided through a custom rename and move experience to resolve issues directly The rename experience will: Show the number of over-limit characters Highlight which items in the path can be renamed Allow renames even when the path exceeds 260 characters Screenshot - Custom rename dialog The move experience will: Show over-limit character counts in a guided interface Display warning dialogs for over-limit shared items in OneDrive Display warning dialogs for over-limit items in shortcuts Screenshot - Example warning dialog for overlimit items in shortcuts These enhancements are designed to reduce troubleshooting time and improve the overall sync experience. [Action required and recommendations] No admin action is required. This update will be automatically available through the OneDrive sync client. You may want to: Inform your helpdesk and support teams about the improved error messages, as this update should reduce max-path-related support tickets. Update internal documentation for resolving OneDrive sync issues if applicable. Learn more Fix paths that are too long to sync in OneDrive | Microsoft Support Restrictions and limitations in OneDrive and SharePoint | Microsoft Support [Compliance considerations] No compliance considerations identified. This update does not change how customer data is stored, processed, or accessed. -
(Updated) Windows updates are available for 2026 time zone changes in Canada
MC1510951 · preventOrFixIssue · normal · Updated 10/27/2026 21:03
Services: Exchange Online, Microsoft 365 suite, Dynamics 365 Apps, Power BI, Windows
Read message
(Updated October 16, 2026: Added guidance for managing the Alberta and British Columbia time zone changes in Outlook Time Zone Changes for Alberta and British Columbia.) (Updated October 27, 2026: Included reference and link to more guidance published in the Message center post MC1526468.) [What and why:] Windows updates are now available to support the 2026 time zone changes in Manitoba, Alberta, and British Columbia. On November 1, 2026, clocks in affected regions will not be set back by one hour. Manitoba will permanently stay on UTC-5, Alberta and affected locations will permanently stay on UTC-6, and most of British Columbia will permanently stay on UTC-7. The new Windows updates add region-specific time zones to support these changes. [Rollout schedule:] September 22, 2026: The Alberta and British Columbia changes became available in the September 2026 non-security preview update for Windows 11, versions 25H2 and 24H2. October 13, 2026: The Manitoba change became available for all supported versions of Windows. The Alberta and British Columbia changes became available for all other supported versions of Windows, including Windows Server. These changes are included in the October 2026 security update. November 1, 2026: The time zone transitions take effect at 2:00 a.m. local time. Clocks in affected areas will not be set back by one hour. [Impact on your organization:] Devices in affected regions will display an incorrect local time after the November 1, 2026 transition if the applicable Windows update is not installed or the appropriate time zone is not selected. The updates add the following region-specific time zones: (UTC-05:00) Manitoba (UTC-06:00) Mountain Time (Alberta) (UTC-07:00) Pacific Time (British Columbia) The Alberta time zone change also applies to Yellowknife and Inuvik in the Northwest Territories and locations in southeastern British Columbia that align with Alberta. Devices configured to set the time zone automatically will select the appropriate new time zone. On other devices, the new region-specific time zone must be selected manually. [Action required/recommendations:] Install the applicable Windows update on affected devices before November 1, 2026. Confirm that affected devices use the appropriate region-specific time zone after installing the update. If a device cannot receive the update before November 1, 2026, read and follow the interim guidance for each affected region detailed in the Daylight Saving Time & Time Zone Blog and move the device to the appropriate region-specific time zone as soon as possible. Note: To manage this change in Outlook, please follow the guidance in the article Outlook Time Zone Changes for Alberta and British Columbia. For guidance on how to manage Outlook and Exchange Online calendar events, Microsoft Teams Rooms on Windows, and other potentially impacted Microsoft 365 experiences, see MC1526468. [Compliance considerations:] No compliance considerations are identified. Review as appropriate for your organization and region-specific time zone. [Additional information:] Daylight Saving Time & Time Zone Blog Alberta 2026 time zone update available now British Columbia 2026 time zone update available now Manitoba 2026 time zone update available now Outlook Time Zone Changes for Alberta and British Columbia | Microsoft Support Daylight saving time help and support -
An updated version of the October 2026 Scan Cab is available
MC1525374 · preventOrFixIssue · normal · Updated 10/27/2026 18:36
Services: Windows
Read message
IMPORTANT: This notice applies only to environments where: .NET 8.0, 9.0, 10.0, or 11.0 RC3 is installed. Visual Studio 2019, 2022, or 2026 is installed. PowerShell 7.4 or 7.6 is installed. Scan Cab is used to assess update compliance. The October 2026 Scan Cab was deployed before 7:00 PM PDT on October 25, 2026. What and why: An updated version of the October 2026 Scan Cab was made available at 7:00 PM PDT on October 25, 2026. It includes new metadata for these out-of-band security updates: .NET 8.0 (KB5133964), .NET 9.0 (KB5133965), .NET 10.0 (KB5133966), and .NET 11.0 RC3 (Release notes) Visual Studio 2026, Visual Studio 2022, and Visual Studio 2019 PowerShell 7.6 and PowerShell LTS 7.4 These updates address security vulnerabilities across .NET, Visual Studio, and PowerShell. See the Additional information section for vulnerability details. Rollout schedule: The updated October 2026 Scan Cab was made available at 7:00 PM PDT on October 25, 2026. Who is affected: IT administrators who downloaded the Scan Cab before 7:00 PM PDT on October 25, 2026, should reacquire and redeploy it if they use Scan Cab to assess updates for environments with the affected .NET, Visual Studio, or PowerShell versions listed above. No action is required if Scan Cab isn’t used to assess updates for these products. Because non-Microsoft applications may also use Scan Cab, review the documentation for your organization’s software and update-deployment tools to determine whether this applies to your environment. What will happen: Administrators can re-deploy the updated Scan Cab via their usual processes. For detailed guidance, see the Additional information section below. Additional information: Updated Scan Cab: Download the new Scan Cab CVE-2026-70197: .NET Remote Code Execution Vulnerability CVE-2026-102870: ASP.NET Core Remote Code Execution Vulnerability CVE-2026-114148: ASP.NET Core Elevation of Privilege Vulnerability CVE-2026-111497: Google: CVE-2026-111497 Buffer overflow vulnerability in the Brotli decoder .NET Security Updates: .NET 8.0 (KB5133964), .NET 9.0 (KB5133965), .NET 10.0 (KB5133966), and .NET 11.0 RC3 (Release notes) Visual Studio Security Updates: Visual Studio 2026, Visual Studio 2022, and Visual Studio 2019 PowerShell Security Updates: PowerShell 7.6 and PowerShell LTS 7.4 Announcing a smaller WSUS Scan Cab - Microsoft Tech Community: Learn more about WSUS and the Scan Cab process Using WUA to Scan for Updates Offline - Win32 apps: Windows Update Agent (WUA) can be used to scan computers for security updates without connecting to Windows Update WSUS and the Catalog Site: The Catalog Site used by WSUS to import updates and drivers -
New MSRC blog: Microsoft’s response to compromised eMudhra certificate authority keys
MC1526780 · preventOrFixIssue · normal · Updated 10/27/2026 02:08
Services: Windows
Read message
Microsoft has published a new blog post outlining our response to the compromise of eMudhra intermediate certificate authority keys, including changes to the Windows and Microsoft Edge trust lists. The Windows out-of-band updates are now available in the Microsoft Update Catalog. Administrators managing disconnected devices, or devices that don’t receive automatic certificate trust updates, can find more context and recommended steps in Microsoft’s response to compromised eMudhra certificate authority keys. The following Windows updates are now available: Windows 11, version 26H1: KB5134134 Windows 11, versions 26H2, 25H2, and 24H2: KB5134133 Windows 11, version 23H2: KB5134130 Windows Server 2025: KB5134137 Windows Server 2022: KB5134140 Windows 10, version 22H2 and Windows 10 Enterprise LTSC 2021: KB5134125 Windows 10 Enterprise LTSC 2019 and Windows Server 2019: KB5134124 Windows Server 2016: KB5134123 -
Microsoft Teams Default meeting template
MC1526679 · planForChange · normal · Updated 10/26/2026 23:05
Services: Microsoft Teams
Read message
[What and Why:] Default Meeting Templates enable IT admins to automatically apply their organization’s preferred meeting options whenever users schedule a Teams meeting through Outlook or Teams calendar. This helps organizations apply meeting options (including protection meeting options) at scale, and reduce the need for organizers to manually configure meeting options. [Rollout Schedule:] General Availability (Worldwide): We will begin rolling out in early November 2026 and expect to complete by mid November 2026. [Impact on Your Organization:] For meeting organizers and co-organizers with a default meeting template applied, their meetings will use the meeting options defined in that template, including protection meeting options. Participants joining those meetings will experience the configured meeting options. Please note that only organizers and co-organizers with a Teams Premium license can use the default meeting template. [Action Required/Recommendations:] Default meeting templates help IT admins provide a consistent meeting experience by automatically applying the configured meeting options, including protection meeting options, to scheduled meetings through Outlook or Teams Calendar. Meet Now, Channel Meetings, and Events are out of scope for default meeting template. IT admins first create a custom meeting template and then assign it as the default meeting template. Instructions to create a default meeting template: Create a custom meeting template in Microsoft Teams. Configuration considerations: When configuring the template, admins should review the restrictions and platform limitations associated with the features they enable. Some settings may result in a degraded experience on unsupported platforms. If the default meeting template is removed, meetings will no longer use the meeting options defined by that template. Instead, the meeting options currently applicable to the organizer will take effect. Recommendation: Do not configure the Copilot meeting policy to “On with saved transcript required.” With this configuration, users may encounter errors with default meeting template. We recommend using an alternative Copilot meeting policy configuration. [Compliance considerations:] No compliance considerations identified. Review as appropriate for your organization. -
Microsoft 365 admin center: Manage authoritative sources for Microsoft 365 Copilot Search
MC1526676 · stayInformed · normal · Updated 10/26/2026 23:02
Services: Microsoft 365 suite
Read message
[What and Why:] This new capability enables admins the capability to manage Authoritative sources within the Copilot Search experience in the Microsoft 365 Admin Center. As part of current change admins will be able manage SharePoint Online (SPO) sites that can be deemed as authoritative content per their organization. Available only to Global admin and Global reader role. [Rollout Schedule:] Public Preview (Worldwide): We will begin rolling out on late September 2026 and expect to complete by late September 2026. General Availability (Worldwide): We will begin rolling out on late September 2026 and expect to complete by late September 2026. [Impact on Your Organization:] This will help enhance relevance and ranking of these SharePoint sites. The feature introduces a centralized governance layer in Copilot Control Systems, allowing admins to: View, add, delete the authoritative SharePoint sites via the UX. Will be able to bulk import or export these sources. The admins can add only up to 100 sites as authoritative. [Action Required/Recommendations:] This feature is available to Global admin and Global reader roles. [Compliance considerations:] Does the change introduce or significantly modify AI/ML or agent capabilities that interact with or provide access to customer data?Yes. The feature uses AI/ML or agent capabilities with Microsoft 365 content, prompts, or service data as described in this message. Does the change provide end users any new way of interacting with generative AI?Yes. The feature introduces or updates a user-facing AI or Copilot experience as described in this message. Does the change include an admin control and, can it be controlled through Entra ID group membership?Yes. The feature includes or affects admin controls, policies, permissions, roles, authentication, or management settings as described in this message. Review the linked documentation or admin center controls for group-based configuration support. -
Change Optics Report
MC1526668 · stayInformed · normal · Updated 10/26/2026 22:57
Services: Exchange Online
Read message
[What and Why:] Following the public preview announced in MC1301802, the Change Optics report for Exchange Online is now generally available for worldwide tenants. The report helps Exchange administrators identify email traffic that may be affected by upcoming service changes so they can investigate and remediate potential issues before enforcement occurs. Learn more: The Change Optics report is now generally available in Exchange Online [Rollout Schedule:] General Availability (Worldwide): The report is available now. [Impact on Your Organization:] The Change Optics report is available in the Exchange Admin Center under Reports > Mail flow > Change Optics Report. The report displays a sample set of messages matching characteristics expected to be affected by Exchange Online transport changes. At GA, the report includes: OMC (Onmicrosoft.com external traffic): Identifies onmicrosoft.com traffic sent externally so organizations can investigate and reduce usage affected by onmicrosoft.com throttling. DRS (Direct Send traffic): Identifies Direct Send traffic received by your tenant, helping administrators identify legitimate senders before enabling Reject Direct Send. Since Public Preview, we've made improvements to the report thanks to the feedback received. [Action Required/Recommendations:] No action is required. Exchange administrators may want to: Review the Change Optics Report when future Message Center communications reference a Change Optics scenario. Use the OMC scenario to identify and reduce onmicrosoft.com external email usage. Use the DRS scenario to identify Direct Send traffic and prepare for enabling Reject Direct Send where appropriate. Update internal mail flow operational guidance to incorporate Change Optics as part of change preparation. [Compliance considerations:] No compliance considerations identified. Review as appropriate for your organization. -
(Updated) Microsoft Copilot for Outlook: New Copilot entry point in Classic Outlook
MC1441784 · planForChange · normal · Updated 10/26/2026 22:56
Services: Exchange Online
Read message
Updated October 26, 2026: We have updated the timeline. Thank you for your patience. [What and why] We are updating the entry point for Copilot in Outlook to be more visually appealing and consistent. Located next to the Outlook ribbon, the Copilot entry point makes it easier for users to discover and use Copilot as they work. In addition to chat, it also surfaces contextual, AI-powered recommendations based on the task at hand, such as reading email, composing messages, or managing a calendar. With a single click, users can act on these suggestions to quickly summarize content, draft responses, organize information, and accomplish tasks more efficiently. The experience is designed to bring relevant Copilot capabilities closer to the user's workflow while providing a consistent Copilot experience across Microsoft 365 applications. This update is associated with Microsoft 365 Roadmap ID 567007. [Rollout schedule] General Availability Worldwide: Beginning mid-November 2026 (previously late October) and expected to complete by late November 2026 (previously mid-November) GCC and GCC High: Beginning early December 2026 (previously mid-November) and expected to complete by late December 2026 (previously early December) DoD: Beginning early December 2026 (previously mid-November) and expected to complete by late December 2026 (previously early December) [Impact on your organization] Who is affected All users with Copilot license and enterprise license users (with or without Copilot license) will see the new DAB. Platforms and services Classic Outlook for Windows Microsoft 365 Copilot What will happen The entry point for Copilot in classic Outlook will be updated and located next to the Outlook ribbon: Users will continue to have access to the Copilot side pane. This new entry point will surface contextual, AI-powered recommendations based on the task at hand. The feature will be available by default for eligible users with the required Microsoft 365 Copilot license. No existing Copilot licensing requirements or admin settings are changing as part of this update. [Action required and recommendations] No action is required. We recommend that you: Inform users that the Copilot entry point in classic Outlook is moving to a new location. Update any internal documentation or training materials that reference the current location of the Copilot button. Communicate the change to help desk and support teams so they can assist users when the new experience becomes available. [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
(Updated) Outlook: Change the organizer of meetings
MC1472028 · stayInformed · normal · Updated 10/26/2026 22:51
Services: Exchange Online, Microsoft 365 suite
Read message
Updated October 26, 2026: We have updated the content and timeline. Thank you for your patience. [What and Why:] Microsoft is introducing Change organizer for eligible Outlook meetings and recurring meeting series. Users can ask another person in their organization to become the organizer, and the selected person must accept before ownership changes. This supports personal and team productivity by maintaining meeting continuity during role changes, leave, and offboarding. [Rollout Schedule:] This phase supports non-online meetings: Worldwide: Early November through early December 2026 GCC: Late November through late December 2026 GCC High: Early December through late December 2026 DoD: Early December through late December 2026 Phase 2 will add eligible online meetings. For Teams meetings, the transfer will generate a new Teams meeting link owned by the new organizer. Phase 2 will also be rolled out along with phase 1 with the same schedule. Phase 3 will add transfer support for eligible Teams meeting artifacts, including chat, meeting options, transcripts, recordings, agenda, notes, and attendance reports. Its timing will be announced separately. [Impact on Your Organization:] Who is affected: Users who organize eligible meetings or recurring series. Users selected to become a new organizer. Delegates with permission to edit meetings on another user's primary calendar. Help desk teams supporting meeting ownership transitions. Platforms/Services: Outlook on the web New Outlook for Windows Teams Microsoft 365 Calendar Exchange Online Classic Outlook for Windows is not supported. What will happen: The current organizer can select one person in the same organization or tenant and send an organizer change request. The meeting remains with the current organizer until the selected person accepts. The organizer or an authorized delegate can cancel a pending request. For recurring series, future instances move to the new organizer's calendar. Earlier instances remain with the previous organizer. Internal Exchange Online attendees receive a silent update and do not need to respond again. Their Reminder, Category, Show As, and Private settings are preserved. External and on-premises attendees receive a cancellation and a new invitation, which requires a response. The meeting body, attachments, and sensitivity labels are preserved. The new organizer might require separate access to OneDrive attachments or links. If the meeting has a Teams meeting, a new Teams meeting link will be generated upon transfer which will be owned by the new organizer. This feature is enabled by default and requires no tenant configuration. There is no admin setting to control the availability of this feature. The meeting must be in the future, use a work or school account, and be stored on the organizer's primary calendar. Draft, canceled, encrypted, group calendar, group mailbox, and shared mailbox meetings are not eligible. [Action Required/Recommendations:] No administrative action is required. Review meeting ownership processes for role changes, leave, and offboarding. Update internal meeting management and offboarding documentation. Tell users that the new organizer must accept the request and that the previous organizer is not automatically retained as an attendee. Advise users that external attendees must respond to a replacement invitation. Ask users to confirm that the new organizer can access linked OneDrive content. Review the Microsoft Support article, Change the organizer of a meeting in Outlook. [Compliance Considerations:] ConsiderationImpactExplanation Does the change alter how existing customer data is processed, stored, or accessed?YesFuture meeting instances move to the new organizer's calendar and can be managed by that organizer. Earlier recurring instances remain with the previous organizer. Meeting content is preserved, but linked OneDrive content might require separate access. Does the change provide a new way of communicating between users, tenants, or subscriptions?YesThe feature adds organizer transfer requests within an organization. Internal attendees receive silent updates, while external and on-premises attendees receive a cancellation and replacement invitation. -
Microsoft 365 Apps: Cloud Update - Export Improvements
MC1526661 · planForChange · normal · Updated 10/26/2026 22:48
Services: Microsoft 365 suite, Microsoft 365 apps
Read message
[What and Why:] New export improvements are coming to Cloud Update, making it easier for organizations to access and analyze device data. These enhancements will expand export capabilities across Inventory and Cloud Update device views, include additional device and update information, and allow admins to export filtered results so they can focus on the devices most relevant to their needs. [Rollout Schedule:] General Availability (Worldwide): We will begin rolling out on early November 2026 and expect to complete by late November 2026. [Impact on Your Organization:] We are enhancing export capabilities in Inventory and Cloud Update to make it easier to get the device data you need for reporting, troubleshooting, and sharing with stakeholders. With this update: Inventory export: Export from the Inventory > All devices view will include the Cloud Update Status column, which indicates whether each device is managed, onboarding, excluded, or not eligible for Cloud Update. Cloud Update device export: You can export device data directly from the Current > Devices and Monthly Enterprise > Devices views. Exports include all table columns, such as rollout wave, update status, and errors. Filtered export: You can apply filters to a device view and export only the matching results, such as devices that are not up to date. This change does not affect which devices appear in Inventory or Cloud Update, or how those devices are managed. [Action Required/Recommendations:] No preparation or configuration is required. Admins can begin using the new export capabilities as they become available. [Compliance considerations:] No compliance considerations identified. Review as appropriate for your organization. -
AI Builder credits retirement: Prepare to use Copilot Credits
MC1526652 · planForChange · normal · Updated 10/26/2026 22:31
Services: Power Apps, Microsoft Power Automate
Read message
[What and Why:] Microsoft is retiring AI Builder credits and replacing them with Copilot Credits. Organizations using AI Builder must arrange Copilot Credit capacity before their existing AI Builder credit entitlements expire, or sooner if those credits are exhausted, to avoid interruptions. AI Builder features are not being retired. They will continue to be supported using Copilot Credits, bringing AI Builder and Microsoft Copilot Studio capabilities onto a common credit-based licensing model. When this will happen: November 1, 2025: Sales of AI Builder capacity add-ons ended for new customers. November 1, 2026: AI Builder capacity add-ons reach end of life. Credits from active add-on contracts remain usable until those contracts expire. November 1, 2026: New or renewed eligible Power Platform and Dynamics 365 licenses will no longer include seeded AI Builder credits. Seeded credits included with eligible licenses purchased or renewed before this date remain available through the end of the applicable contract term. November 1, 2026, is not a universal cutoff for existing credits. Your transition deadline depends on when your applicable contracts expire. [Rollout Schedule:] General Availability (Worldwide, GCC): We will begin rolling out on early November 2026 and expect to complete by early November 2026. [Impact on Your Organization:] This change affects organizations that use AI Builder credits from capacity add-ons or credits included with eligible Power Platform and Dynamics 365 licenses to run AI Builder features in Power Apps and Power Automate. AI Builder features in Power Apps and Power Automate consume available AI Builder credits first. When those credits are unavailable or exhausted, usage automatically falls back to available Copilot Credits. If neither credit type is available, affected AI Builder runs are blocked, which can interrupt apps, flows, and business processes. AI Builder credits will not automatically convert to Copilot Credits. Consumption rates differ by capability; there is no single conversion ratio. AI Builder features in Copilot Studio already consume Copilot Credits. This change affects licensing, not feature availability. Administrators must ensure sufficient capacity to continue running AI Builder features. [Action Required/Recommendations:] Admin action is required before November 1, 2026, for organizations with AI Builder capacity add-ons, and before existing credit entitlements expire to prevent disruption. Review your contracts. Identify when your AI Builder capacity add-ons and licenses providing seeded credits expire. For AI Builder capacity add-ons, turn off automatic renewal in the Microsoft 365 admin center or work with your partner to do so in Partner Center. Review credit consumption across environments. In the Power Platform admin center, go to Licensing > Capacity add-ons > Download reports > + New > AI Builder. Generate and download the report to review credits consumed by date, user, and environment during the 30 days preceding the selected target date. 3.** Identify affected workloads.** In the Power Automate portal, select the environment, then go to Automation Center > Monitor > AI Builder activity. Makers can review their own activity for models they can access; users with the System Administrator or System Customizer role can review all activity in the environment. Activity data is also available in the AI Event table in Dataverse. Plan replacement capacity. Use the AI Builder capability rate table to estimate Copilot Credit requirements. Purchase and make sufficient Copilot Credits available to affected environments before existing AI Builder credit entitlements expire. Do not assume that the same number of Copilot Credits will cover your current AI Builder credit usage. Notify makers and support teams. Update internal licensing guidance and identify business-critical apps and flows that could be interrupted by insufficient capacity. Learn more End of AI Builder credits AI Builder licensing overview AI Builder consumption report Monitor AI Builder activity [Compliance considerations:] No compliance considerations identified. Review as appropriate for your organization. -
(Updated) Audio Overview Updates
MC1492959 · stayInformed · normal · Updated 10/26/2026 22:18
Services: Microsoft 365 suite, Microsoft 365 apps
Read message
Updated October 26, 2026: We have updated the timeline. Thank you for your patience. [What and Why:] Microsoft is rolling out new capabilities in Audio Overview to make it easier to navigate longer content, support enterprise information protection, and create audio overviews from more types of content. Episodes For longer and more content-rich notebooks, Audio Overview can organize the discussion into topic-based episodes. This makes it easier for users to navigate the audio and focus on different parts of the content. Sensitivity labels when saving to OneDrive Audio Overviews now support Microsoft Purview sensitivity labels when saved to OneDrive. If the source content includes sensitivity labels, the saved Audio Overview inherits the most restrictive label from its sources. Sensitivity labels apply to the saved file in OneDrive. Audio Overviews within the notebook are not yet sensitivity labeled. More supported content types Audio Overview can now understand and ground its discussion in additional types of content added to a notebook, including: OneNote pages Loop pages Plain text (.txt) files Emails Teams meetings Teams chats [Rollout Schedule:] General Availability (Worldwide): We will begin rolling out in early November 2026 (previously late October) and expect to complete by late November 2026. [Impact on Your Organization:] Who is affected: Users who create and consume Audio Overviews. Organizations that use Audio Overview with Microsoft 365 content stored or saved in OneDrive. Platforms/Services: Microsoft 365 Copilot Audio Overview OneDrive Microsoft Purview sensitivity labels What will happen: Users can navigate longer Audio Overviews through topic-based episodes. Users can create Audio Overviews grounded in additional content types, including OneNote pages, Loop pages, .txt files, emails, Teams meetings, and Teams chats. Audio Overviews saved to OneDrive from labeled source content will inherit the most restrictive sensitivity label from the sources. This release does not introduce sensitivity labeling for Audio Overviews while they remain within the notebook. [Action Required/Recommendations:] No admin action is required to prepare for this update. These Audio Overview improvements will roll out automatically to eligible users. For sensitivity labels, when an Audio Overview is saved to OneDrive from labeled source content, the saved file will automatically inherit the most restrictive sensitivity label from its sources. No additional configuration is required as part of this feature rollout. [Compliance considerations:] Does the change introduce or significantly modify AI/ML or agent capabilities that interact with or provide access to customer data?Yes. Audio Overview uses AI capabilities to generate audio grounded in Microsoft 365 content, including additional supported content types. Does the change provide end users any new way of interacting with generative AI?Yes. Users can create and navigate Audio Overviews from more supported Microsoft 365 content sources. Does the change modify, interrupt, or disable Purview capabilities such as Information Protection labels?Yes. Audio Overviews saved to OneDrive from labeled source content inherit the most restrictive sensitivity label from the sources. -
Microsoft Entra: Users can register a passkey or passwordless sign-in as their first multifactor authentication method
MC1450133 · stayInformed · normal · Updated 10/26/2026 20:51
Services: Microsoft Entra
Read message
Updated October 26, 2026: We have updated the timeline. Thank you for your patience. [What and why] Users will soon be able to register a passkey as their first multifactor authentication method. Previously, people had to set up an alternate MFA method like SMS or Voice before they could add a passkey (FIDO2), Windows Hello for Business, macOS Platform SSO. That extra step pushed users toward weaker methods and slowed the move to phishing-resistant sign-in. Now password-only users can go straight to a passkey, making it easier to adopt strong authentication from day one. As part of this work, we will also be enabling Authenticator App passwordless sign-in to be a user's first registered MFA method. [Rollout schedule] This feature will roll out in phases: Phase 1: Support for synced passkeys, Microsoft Entra passkeys on Windows, and FIDO2 security keys. General Availability (Worldwide, GCC): We will begin rolling out in early November 2026 (previously late October) and expect to complete by early January 2027 (previously late November 2026). Phase 2: Support for Windows Hello for Business, macOS Platform SSO, Authenticator App passkey, and Authenticator App passwordless sign-in. General Availability (Worldwide, GCC): We will begin rolling out in early January 2026 and expect to complete by late February 2027. [Impact on your organization] Who is affected Users who have not yet registered a multifactor authentication method Identity and security administrators responsible for authentication onboarding and registration policies Platforms and services Microsoft Entra ID Passkeys (FIDO2) Windows Hello for Business macOS Platform SSO Microsoft Authenticator passwordless sign-in What will happen Password-only users will be able to register passkeys or passwordless sign-in as their first MFA method. Users will no longer need to register a method such as SMS or voice before registering a passkey (FIDO2), Windows Hello for Business, macOS Platform SSO, or Authenticator passwordless sign-in. Organizations may see reduced registration friction and increased adoption of phishing-resistant authentication methods. Users who are enabled for passkeys will be prompted to register a passkey by default when completing applicable registration experiences, including those triggered by multifactor authentication (MFA) enforcement and Conditional Access authentication strengths. Security Defaults MFA registration prompts will adopt this experience in January–February 2027. [Action required and recommendations] No action is required for this change. We recommend that administrators: Review Conditional Access policies related to security information registration. Consider requiring MFA to register security information if additional verification is required by your organization. Review your user onboarding and registration guidance and update it as needed to reflect that eligible users may be prompted to register a passkey by default. Learn more (To be updated closer to rollout) Register a synced passkey (FIDO2) | Authentication | Microsoft Entra ID | Microsoft Learn [Compliance considerations] QuestionAnswer Does the change include an admin control?Yes. Administrators can control which authentication methods users are allowed to register through existing Microsoft Entra authentication method policies and Conditional Access policies. Does the change affect access or authentication controls?Yes. The update changes how users register multifactor authentication methods by allowing eligible users to register supported passkeys or passwordless authentication methods as their first MFA method. Can administrators govern the feature through existing Microsoft Entra controls?Yes. Administrators retain control over the feature through Microsoft Entra authentication method policies and Conditional Access configurations. -
Update to MC1510951: Canada 2026 time zone changes — Microsoft 365 impact and required admin actions
MC1526468 · preventOrFixIssue · high · Updated 10/26/2026 20:00
Services: Microsoft 365 suite
Action required by: 11/01/2026 07:00
Read message
This post updates MC1510951 ((Updated) Windows updates are available for 2026 time zone changes in Canada, posted October 16, 2026). On November 1, 2026, affected locations in British Columbia, Alberta, and Manitoba will not move clocks back and will remain on UTC-07:00, UTC-06:00, and UTC-05:00 respectively. Affected locations in the Northwest Territories (including Yellowknife and Inuvik) align with the Alberta change, and Northwestern Ontario aligns with the Manitoba change. Windows and Microsoft 365 services depend on updated time zone definitions for correct scheduling and display behavior. How this affects your organization Confirmed impact Outlook and Exchange Online (calendar): Users must move to the new time zone. Existing events do not migrate automatically. Recurring meetings require additional review. Microsoft Teams Rooms on Windows: Some devices may display time one hour behind Windows until Edge/WebView2 is updated. Potential impact (under validation) Microsoft Teams (desktop, web, mobile) and other Teams devices Outlook for iOS, Android, and Mac Microsoft Bookings Shifts SharePoint Online OneDrive What you need to do Ensure Windows devices in affected regions have the latest Windows updates (including October 2026 updates). Ask users in affected regions to select the new time zone in Outlook and review meetings scheduled after November 1, especially recurring series. Plan to run the Exchange Online PowerShell remediation cmdlet for non-recurring meetings once released (target: October 28, 2026). Update Microsoft Edge and WebView2 on Teams Rooms on Windows and confirm room time display matches Windows. Keep Teams, Outlook (including iOS/Android/Mac), and other Microsoft 365 apps current. Test key scenarios before November 1: recurring meetings, free/busy, Bookings appointments, Shifts schedules, and SharePoint regional settings. If issues occur, open a support case in the Microsoft 365 admin center and include #Canada Time-Zone in the title. Additional information Outlook Time Zone Changes for British Columbia, Alberta, and Manitoba (Microsoft Support) Interim guidance for British Columbia time zone changes 2026 (DST Blog) Interim guidance for Alberta time zone changes 2026 (DST Blog) Manitoba 2026 time zone update available now (Daylight Saving Time and Time Zone Blog) We will continue updating this post as product teams confirm impact, publish mitigations, and release additional guidance. -
(Updated) Outlook: Reply With a Template in Rules
MC1505607 · stayInformed · normal · Updated 10/26/2026 17:14
Services: Exchange Online
Read message
Updated October 26, 2026: We have updated the timeline. Thank you for your patience. [What and Why:] Users of new Outlook for Windows and Outlook on the web will be able to create inbox rules that automatically reply to incoming messages using a saved template. This helps users reduce repetitive work while providing faster, more consistent responses. This change supports personal and team productivity by automating routine email responses. This message is associated with Microsoft 365 Roadmap ID 567318. [Rollout Schedule:] Targeted Release (Worldwide): We will begin rolling out in mid-October 2026 and expect to complete by early November 2026. General Availability (Worldwide): We will begin rolling out in early December 2026 and expect to complete by late December 2026. [Impact on Your Organization:] Who is affected: Users of new Outlook for Windows and Outlook on the web who use inbox rules and want to automatically reply to incoming messages using saved templates. Platforms/Services: New Outlook for Windows and Outlook on the web Outlook inbox rules What will happen: Users can create an inbox rule with conditions for incoming messages. Users can select a saved template as the automatic reply. When an incoming message meets the rule conditions, Outlook automatically sends the configured template response. This provides users with a way to automate repetitive, consistent responses. The capability will roll out automatically during the scheduled rollout window. [Action Required/Recommendations:] No admin action is required before rollout. Inform your help desk about this new inbox-rule capability. Update internal Outlook guidance if your organization documents inbox rules or automated responses. Consider whether your organization has policies or guidance governing automated email responses. Review Microsoft Outlook documentation as it is updated for this capability. [Compliance considerations:] No compliance considerations identified. Review as appropriate for your organization. -
(Updated) Retirement notice: MDE and XDR Advanced Hunting APIs retiring; migrate to Microsoft Graph Security API
MC1220762 · planForChange · normal · Updated 10/26/2026 16:20
Services: Microsoft Defender XDR
Action required by: 01/31/2027 08:00
Read message
Updated October 26, 2026: We have updated this post as a reminder. Thank you for your patience. [Introduction] We’re retiring the Microsoft Defender for Endpoint (MDE) Advanced Hunting API and Microsoft Defender XDR Advanced Hunting API and transitioning customers to the Microsoft Graph Security API. This update aligns our security integrations with a unified interface and schema across Microsoft Defender products. The Microsoft Graph Security API provides broader data coverage, improved consistency, and better scalability for automation and security workflows. [When this will happen] Retirement start: February 6, 2026 Full retirement: February 1, 2027 After February 1, 2027, the MDE and XDR APIs will no longer function. [How this affects your organization] Who is affected: Organizations using the MDE or XDR Advanced Hunting API for automation, integration, or custom workflows. You are receiving this message because our reporting indicates your organization may be using these APIs. What will happen: The MDE and XDR Advanced Hunting APIs will stop functioning after February 1, 2027. Existing scripts, automations, and workflows that rely on these APIs will fail if not updated. The Microsoft Graph Security API will be the supported API for accessing Microsoft security data. No automatic migration will occur; manual updates will be required. [What you can do to prepare] Migrate all existing API workflows to the Microsoft Graph Security API by January 31, 2027. Update internal documentation, automation scripts, and integration endpoints to use the Microsoft Graph Security API. Communicate these changes to your security operations, engineering, and development teams. Review Microsoft documentation to plan your migration: Use the Microsoft Graph security API. If your organization uses custom solutions, validate that new queries and response schemas work as expected before the retirement date. Learn more: Advanced hunting - Use the Microsoft Graph security API | Microsoft Graph | Microsoft Learn Migrate from the older APIs - Use the Microsoft Graph security API | Microsoft Graph | Microsoft Learn (to be retired) Advanced Hunting API - Microsoft Defender for Endpoint | Microsoft Learn (to be retired) Microsoft Defender XDR advanced hunting API - Microsoft Defender XDR | Microsoft Learn [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
Dynamics 365 and Power Platform– Information about storage validation for Dataverse-only tenants
MC1483524 · planForChange · normal · Updated 10/26/2026 15:38
Services: Dynamics 365 Apps
Read message
Beginning November 9, 2026, we are introducing staged storage validation for supported Dynamics 365 applications. The change gives administrators clearer visibility into storage use, advance notice of potential restrictions, and several ways to remain within capacity, including removing unneeded data, adding capacity, or enabling pay-as-you-go for sandbox environments. If no corrective action is initiated after repeated notifications, when a tenant exceeds its entitled Database, File, or Log capacity, environment creation, copy, restore, and recover operations will be restricted immediately. If the overage remains unresolved, sandbox environments that do not have pay-as-you-go billing enabled will enter Administration mode after 30 days of remaining over capacity, allowing access only to administrators. After 90 days from the date the tenant exceeds capacity, affected sandbox environments will be disabled and will no longer be accessible to users. During this phase customers can contact Microsoft Support for the sole purpose of directing data export options, if needed. Production environments are not subject to administration mode and disabled stage restrictions and will remain accessible. However, environment creation, copy, restore, and recover operations for sandbox or production type environments will remain blocked while the tenant is over capacity. Deployment Timeline: Rollout begins: November 9, 2026 Rollout completion: December 14, 2026 How does this affect me? The Dataverse storage validation applies only to Dataverse-only tenants without Dynamics 365 Finance and Operations environment(s) or consumption. The following products are included in the storage validation rollout: Microsoft Dynamics 365 Sales Microsoft Dynamics 365 Customer Service Microsoft Dynamics 365 Field Service Microsoft Dynamics 365 Customer Insights Microsoft Dynamics 365 Customer Voice Microsoft Dynamics 365 Contact Center Microsoft Dynamics 365 Project Operations (Dataverse deployments) If your tenant exceeds its entitled storage capacity, the following lifecycle applies: Stage Timing Impact 1. Restricted When the tenant first exceeds its entitled storage capacity, known as time zero (T0) Environment creation, copy, restore, and recover operations for sandbox and production type environments are blocked immediately when the tenant exceeds its entitled capacity. 2. Administration mode After 30 unresolved days from T0 Only administrators can sign in to *affected sandbox environments. All other users are blocked from accessing the environment. 3. Disabled After 90 unresolved days from T0 All users, including administrators, are blocked from accessing *affected sandbox environments; the environment data is retained and remains available for recovery after remediation. During this phase, customers can contact Microsoft Support for the sole purpose of directing data export options, if needed. All other mechanisms designed to resolve overage are also available to customers at this phase. Sandbox environments with active pay-as-you-go billing do not progress through the storage overage lifecycle even if the tenant remains over storage capacity. Other *affected sandbox environments in the tenant may still be affected with restrictions. We will provide notifications that include the tenant’s current storage status, the date it first exceeded capacity, its current lifecycle stage, future restrictions, and recommended remediation actions. Admins can exit Administration Mode at any time; however, the overage lifecycle continues as long as the tenant remains over its entitled storage capacity. Once the tenant returns below 100%, no further restrictions are applied. Environments do not automatically return to their previous state; admins must manually exit Administration Mode or re-enable them, as applicable. Processing time may vary depending on the remediation method used. Sandbox environments with active pay-as-you-go billing are excluded from the overage lifecycle even if the tenant remains over storage capacity. What action do I need to take? Review your environment(s) and perform the following actions before November 9, 2026: Review Database, File, and Log capacity in the Power Platform admin center. Remove or archive data that is no longer needed. Establish data governance policies in your environment to help prevent future storage overages. Purchase additional capacity or configure pay-as-you-go. Invite makers and users to become aware of these potential restrictions and to notify administrators about possible areas of adjustment. Review your release activities that depend on sandbox availability, and plan accordingly. For additional information, please visit the following articles: What happens when my organization exceeds storage capacity? Dataverse capacity-based storage details Manage data with Dataverse governance policies Free up storage space Add more Dataverse capacity Configure pay-as-you-go in your environment What environments consume tenant capacity Power Platform licensing guidance *Affected environments: Sandbox environments that do not have pay-as-you-go enabled. Any references to affected environments in this message apply exclusively to those sandbox environments -
Microsoft Teams Mobile: Ask Copilot from Search
MC1523087 · stayInformed · normal · Updated 10/23/2026 23:09
Services: Microsoft Teams
Read message
[What and Why:] Users can now start a Copilot conversation directly from Teams search on iOS and Android. Microsoft Teams mobile is adding two ways to ask Copilot from search: As users type two or more words in the search box, a suggestion to ask Copilot appears alongside usual search suggestions. After users press Enter, an Ask Copilot button remains available at the top of the search results page. Selecting either option opens Copilot with the user's query, so users can get an answer and ask follow-up questions without leaving search. [Rollout Schedule:] General Availability (Worldwide): We will begin rolling out in mid-November 2026 and expect to complete by late November 2026. [Impact on Your Organization:] Users can ask Copilot without leaving the Teams mobile search flow. They no longer need to exit search, open Copilot separately, and type their question again. Users can also ask follow-up questions in the same flow, retaining the context of what they searched for. [Action Required/Recommendations:] No admin action is required. The feature turns on automatically when rollout reaches your organization and follows existing Copilot licensing and admin controls. Admins may want to inform users and update internal Teams mobile search guidance. [Compliance considerations:] No compliance considerations identified. Review as appropriate for your organization. -
Alternate text parameter for ODSP attached images in Teams
MC1523086 · stayInformed · normal · Updated 10/23/2026 23:09
Services: Microsoft Teams
Read message
[What and Why:] Adds support for alternate text on OneDrive/SharePoint-hosted images shared in Microsoft Teams, improving accessibility for users who rely on screen reader functionality. [Rollout Schedule:] General Availability (Worldwide): We will begin rolling out in early December 2026 and expect to complete by mid-December 2026. [Impact on Your Organization:] Who is affected: Microsoft 365 users who share or receive image attachments stored in OneDrive and SharePoint through Microsoft Teams. Platforms/Services: Microsoft Teams (Windows, Mac, and web) What will happen: Users can add alt text to an image attachment while composing a message, and can add or update the description later by editing their sent message. Screen readers can announce the saved description when users encounter the image in the Teams message. The description is associated with the image in that Teams message; it does not modify the original image file in OneDrive or SharePoint. [Action Required/Recommendations:] No admin action is required. You may want to: Notify help desk staff and end users about the change. Update your organization's accessibility guidance to encourage concise, meaningful descriptions when sharing images in Microsoft Teams. [Compliance considerations:] No compliance considerations identified. Review as appropriate for your organization. -
Viva Insights: GitHub Copilot metrics will be on by default, and the public preview opt-in setting is being retired
MC1523085 · planForChange · normal · Updated 10/23/2026 23:08
Services: Microsoft Viva
Read message
[What and why] We’re retiring the public preview opt-in setting for GitHub Copilot on the Viva Insights app settings page. After this change, GitHub Copilot metrics will be available by default in the Viva Insights Consumption dashboard for eligible tenants. This change provides a unified view of GitHub Copilot and Microsoft 365 Copilot adoption and usage across developers and knowledge workers. [Rollout schedule] General Availability (Worldwide): Beginning in mid-November 2026 and expected to complete by mid-December 2026 [Impact on your organization] Who is affected Microsoft 365 Global Administrators, Insights Analysts with global partition access, and managers who have access to consumption insights Insights Administrators who manage access to consumption insights Platforms and services Microsoft Viva Insights Consumption dashboard GitHub Copilot What will happen The GitHub Copilot public preview opt-in setting will be removed from the Viva Insights app settings page. After rollout, admins will no longer be able to use this setting to enable or withhold GitHub Copilot metrics. GitHub Copilot metrics will be available by default in Viva Insights for eligible tenants. Admins do not need to take action to enable them. Organizations that previously opted in will continue to see GitHub Copilot metrics. In organizations that did not opt in, users who already have access to the relevant reports may begin seeing GitHub Copilot metrics after rollout. Existing roles, report access, and privacy settings will continue to determine who can view GitHub Copilot data. [Action required and recommendations] No action is required. This change will happen automatically. We recommend that you: Review who in your organization can access consumption insights and related Copilot reports in Viva Insights. Inform your helpdesk, analysts, managers, and business leaders that GitHub Copilot metrics may begin appearing. Update internal documentation that refers to the GitHub Copilot public preview opt-in setting. Learn more How to use the Consumption Dashboard in Insights | Microsoft Learn [Compliance considerations] QuestionAnswer Does the change alter how existing customer data is accessed?Yes. GitHub Copilot metrics will be on by default in Viva Insights for eligible tenants. Organizations that did not previously opt in will begin exposing these metrics to users who already have access to the relevant reports. Existing roles, permissions, and privacy settings continue to determine who can view the data. Does the change include an admin control?Yes. The existing public preview opt-in setting in Viva Insights web app for GitHub Copilot will be retired. After rollout, admins will no longer need to use this setting to enable GitHub Copilot metrics. -
Teams admin center - Intelligent insights for meeting quality
MC1523077 · stayInformed · normal · Updated 10/23/2026 23:04
Services: Microsoft Teams
Read message
[What and Why:] Gain proactive visibility into meeting quality across your organization with AI-powered insights in Teams admin center that identify emerging patterns, highlight impacted users and locations, and surface likely causes with recommended actions. This helps IT administrators detect and address issues earlier, improve meeting quality, and stay ahead of potential disruptions. [Rollout Schedule:] General Availability (Worldwide): We will begin rolling out in mid-November 2026 and expect to complete by early December 2026. General Availability (GCC): We will begin rolling out in mid-November 2026 and expect to complete by mid-December 2026. [Impact on Your Organization:] Administrators will find new enhancements to the meeting and call troubleshooting flow in Teams admin center. Administrators can find these insights in Teams admin center > Meetings > Meetings. The experience evaluates historical meeting-quality data across the organization and highlights locations or public IPs where meeting quality is behaving unusually. When an anomaly is detected, administrators will be able to: Identify meeting-quality hotspots across locations and public IPs and see how many users are affected. Review quality trends to understand how meeting quality has changed over time. Understand likely root causes across network factors such as bandwidth, Wi-Fi, VPN and proxy; compute factors such as CPU, memory and client; and devices such as microphones, cameras and speakers. Take recommended actions based on the likely cause and severity of the issue. Review affected users and supporting evidence to better understand the scope and impact of the anomaly. Insights are refreshed daily and use machine learning to dynamically evaluate what constitutes anomalous behavior, so administrators don’t need to configure thresholds. The insights use meeting data across the tenant and supported clients and platforms. They do not include meeting telemetry from SIP phones or telemetry from PSTN and peer-to-peer calls. [Action Required/Recommendations:] No configuration is required. Once available in your tenant, navigate to Teams admin center > Meetings > Meetings to start reviewing insights. The experience is available to Global Administrators, Teams Administrators, Teams Communications Administrators, Teams Communications Support Engineers, and Teams Communications Support Specialists. [Compliance considerations:] This feature uses AI/machine learning to analyze historical meeting-quality data and surface insights to admins; it does not alter how customer data is stored or processed. Review your organization’s data and AI governance policies as appropriate. -
Microsoft Teams: Loop meeting notes stored in the meeting organizer's OneDrive
MC1523076 · stayInformed · normal · Updated 10/23/2026 23:04
Services: Microsoft Teams
Read message
[What and Why:] For non-channel Microsoft Teams meetings, collaborative meeting notes, including Loop-powered meeting notes and Facilitator notes, will be stored in the meeting organizer’s OneDrive for Business instead of the OneDrive of the person who starts notes. This update provides more consistent ownership and management of meeting content while preserving the existing note-taking and collaboration experience for meeting participants. [Rollout Schedule:] General Availability (Worldwide): We will begin rolling out in mid-November 2026 and expect to complete by late November 2026. [Impact on Your Organization:] For non-channel meetings, newly created collaborative meeting notes will be stored in the meeting organizer’s OneDrive for Business, in the Meetings folder. The organizer will own the notes file even when another participant starts notes or Facilitator. Participants can continue to open and collaborate on notes in Teams, subject to your organization’s existing sharing policies. Notes created before this change will remain in their current location; they will not be moved to the organizer’s OneDrive. Storage for channel meeting notes is not changing. [Action Required/Recommendations:] No configuration change is required for this storage update. Review any internal guidance or governance processes that assume meeting notes are stored in the OneDrive of the person who starts them, and update those processes to account for organizer-owned storage for newly created non-channel meeting notes. [Compliance considerations:] This update changes where newly created meeting notes are stored (from the note-starter’s OneDrive to the organizer’s OneDrive). Review your organization’s data location and retention policies as appropriate. -
(Updated) Teams Phone Agent is rolling out to general availability on Sept 30, 2026
MC1482800 · stayInformed · normal · Updated 10/23/2026 22:47
Services: Microsoft Teams
Read message
Updated October 23, 2026: We have updated the content. Thank you for your patience. [What and why] Microsoft Teams Phone Agent is planned to begin rolling out to general availability (GA) on Sept 30, 2026. [Rollout schedule] General Availability (Worldwide): Beginning in late September 2026 [Impact on your organization] Who is affected Participants interested in using Teams Phone Agent Platforms and services Microsoft Teams What will happen Teams Phone Agent is an AI-powered calling solution that answers incoming calls, assists with supported customer questions and appointment-booking scenarios, and routes callers to an appropriate human contact along with AI-generated conversation notes when additional assistance is needed. The GA solution will be delivered through usage-based billing with Copilot Credits. Usage-based charges begin after an administrator completes the required spending configuration and sets up an agent for use. Teams Phone Agent usage-based charges do not begin until proactive steps are taken to configure spending in M365 admin center. If no action is taken, the Teams Phone line associated with your Teams Phone Agent instance reverts to the auto attendant settings you configured when setting up the experience in Teams admin center. Extensibility of Microsoft Copilot Studio custom voice agents for Teams Phone Agent and Teams Phone remains available in Frontier public. The Teams Phone Agent dashboard in Queues app for Teams Phone, which includes real-time metrics such as the count of incoming callers that Teams Phone Agent is servicing, is currently rolling out to public preview (Ring 3.6). [Action required and recommendations] If you plan to continue using Teams Phone Agent at GA, your admin needs to take proactive steps in the Microsoft 365 admin center: Create a Security Group: Follow these steps to set up a security group: Create, edit, or delete a security group in the Microsoft 365 admin center Add your Teams Phone Agent resource accounts to the security group:To apply the same spending limits to all resource accounts, add them to the same security group. To apply different spending limits, create a separate security group and spending policy for each resource account. Create a Spending Policy: Follow these steps to set up a spending policy: Managing AI experiences enabled by usage-based billingUnder agents and services, select Teams Phone Agent and clear all other selections. When selecting users and groups, choose the security group you created for your Teams Phone Agent resource accounts. Learn more Create, edit, or delete a security group in the Microsoft 365 admin center Managing AI experiences enabled by usage-based billing [Compliance considerations] No compliance considerations identified. Review as usual for your organization. -
Updated Photos experience on Windows 11
MC1518030 · stayInformed · normal · Updated 10/23/2026 21:04
Services: Microsoft OneDrive
Read message
[What and Why:] We're introducing an updated Photos experience on Windows 11 to help people browse, organize, and find photos and videos across their PC and OneDrive. The experience is coming to consumer and commercial devices and will continue to respect existing controls for app installation, updates, and OneDrive access. Starting October 15, 2026, the updated experience is expected to roll out to Windows Insiders over the next few days. We expect to start expanding to Windows 11 Retail users on October 26. This message is associated with Microsoft 365 Roadmap ID 568931 [Rollout Schedule:] General Availability (Worldwide): We will begin rolling out mid-October 2026 and expect to complete by mid-December 2026. [Impact on Your Organization:] Users will continue to find Photos in Start. The updated experience includes a refreshed photo library, a native Photo Viewer for images opened from File Explorer or elsewhere in Windows, and an updated native photo editor. People can use Photos with local content without signing in to OneDrive. Users who sign in with a work or school account can see their OneDrive photos alongside local content. Existing management controls continue to apply: If your organization disables or removes Store-originated apps using DisableStoreApps, the update will not be installed on affected devices. If you use AppLocker packaged-app rules to block Microsoft Photos, update those rules to include the package Microsoft.OneDrive.Photos if you intend to keep blocking it. DisablePersonalSync prevents personal OneDrive account sign-in in Photos. DisableNucleusSync prevents the use of any OneDrive account in Photos. These policies restrict OneDrive functionality in Photos; they do not prevent people from using the app with local content. [Action Required/Recommendations:] For most organizations, no new or immediate configuration is required. Review your existing Windows app-management and OneDrive policies, especially rules that intentionally block or remove Photos. If you use AppLocker to block Photos, account for the updated package name. Share this change with your help desk if users may have questions about the updated experience. [Compliance considerations:] No compliance considerations identified. Review as appropriate for your organization. -
(Updated) Plan for Change: New device page experience will become the default view
MC1456780 · planForChange · normal · Updated 10/23/2026 19:43
Services: Microsoft Intune
Read message
Updated October 23, 2026: The content has been updated to provide additional clarity on admin permissions for the new device experience. Earlier this year, we released the new single device experience that provides a single, consolidated view for device management, making it easier to access device information, monitor activity, use management tools, and perform device actions The new single device page is turned on by default. You can use the "Preview new device toggle" to turn it off and return to the original device page. Starting with Intune’s September (2609) release, the new device page will become the default experience for all administrators, and the previous device page experience will no longer be available. [How this will affect your organization:] Admins who navigate to Devices > All devices and select a device will automatically see the new device page experience. The legacy device page will no longer be available after this change. All existing device management capabilities remain available. This update focuses on improving discoverability, usability, and navigation without removing existing management functionality. With the new device experience, administrators must have the Managed devices/Update permission in addition to any permissions required for the specific device action they want to perform. For example, to change or remove a device’s primary user, an administrator must have both Managed devices/Update and Managed devices/Set primary user. Administrators who do not have Managed devices/Update may also be unable to perform actions such as renaming a device. [What you need to do to prepare:] Update your documentation and review your admin permissions for device management actions as needed. We recommend becoming familiar with the updated interface before it becomes the default view. To preview the new experience today: In the Microsoft Intune admin center, navigate to Devices > All devices. Select a device to view device-specific information, such as device properties, device activity, tools, and reports. -
Microsoft OneDrive: Updated placement of the Create or upload button in OneDrive for the web
MC1521617 · stayInformed · normal · Updated 10/22/2026 23:20
Services: Microsoft OneDrive
Read message
[What and why] We are updating the Microsoft OneDrive web experience. As part of this update, the Create or upload button will move from the left navigation pane to the right side of the page, aligning the experience with SharePoint document libraries. The Create or upload button will also no longer appear in Libraries, Recycle Bin, Meetings, or Media. The available options for creating files and folders or uploading content will remain unchanged. Note: Some users may receive this update sooner than others within your organization. [Rollout schedule] General Availability (Worldwide): Rollout will begin in late October 2026 and is expected to complete by early December 2026. [Impact on your organization] Who is affected Users of Microsoft OneDrive for the web Platforms and services Microsoft OneDrive for the web What will happen The Create or upload button will be moved from the left navigation pane to the right side of the page, and will no longer appear in Libraries, Recycle Bin, Meetings, or Media. Options for creating files and folders or uploading content are unaffected by this update. Some users may see this change before others within your organization. Updated button placement [Action required and recommendations] No administrative configuration or action is required. We recommend that you update internal training materials that reference the previous Create or upload button placement and inform help desk, support teams, and users who regularly use OneDrive for the web about this change. [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
Microsoft Graph APIs for Copilot cost management
MC1521616 · stayInformed · normal · Updated 10/22/2026 23:19
Services: Microsoft 365 suite
Read message
[What and Why:] Microsoft is introducing Microsoft Graph APIs for Copilot cost management, giving organizations a programmatic way to manage Copilot credit spending policies, monitor credit balances, and handle end-user requests for additional credits. Administrators and developers can use the APIs to retrieve tenant, user, and per-service credit balances; create, update, and delete spending policies; assign security groups to policies; configure service-specific settings; and set up email threshold alerts. They can also retrieve, approve, or reject credit requests. These APIs integrate Copilot cost management with existing administration and FinOps processes. This initial release, available through the Microsoft Graph beta surface, focuses on spending-policy administration and balance information; detailed consumption reporting is not included. [Rollout Schedule:] Public Preview (Worldwide): We will begin rolling out to the beta endpoint in mid-October 2026. [Impact on Your Organization:] Who is affected: Administrators and developers who manage Copilot credit spending policies via Microsoft Graph. What will happen: Organizations gain a new programmatic way to integrate Copilot credit cost management with existing administration and FinOps processes. There is no change to the end-user experience, and no action is required for organizations that do not plan to use these APIs. Detailed consumption reporting is not included in this release. [Action Required/Recommendations:] No action is required if your organization does not plan to use these APIs. If you do plan to use them, we recommend you: Review the Microsoft Graph documentation for available beta endpoints and current limitations. Determine the Microsoft Graph permissions and authentication requirements for the operations you plan to automate. Identify which existing administration or FinOps processes you want to integrate with Copilot cost management. Determine which security groups should be assigned to Copilot spending policies, where applicable. Review requirements for configuring credit threshold email alerts and alert recipients. A General Availability date is not currently available. [Compliance considerations:] No compliance considerations identified. Review as appropriate for your organization. -
Microsoft Teams: Retirement of the Turn off IntelliFrame option for online participants
MC1521614 · planForChange · normal · Updated 10/22/2026 23:18
Services: Microsoft Teams
Read message
[What and why] We are retiring the ability for online participants to turn off IntelliFrame for their own view in meetings with a Microsoft Teams Room that has Cloud IntelliFrame enabled. This change provides all online participants with the same view of the room, as configured on the Teams Rooms device. Currently, online participants using Microsoft Teams desktop on Windows and Mac can right-click the video tile of a Teams Room using Cloud IntelliFrame and select Turn off IntelliFrame. This switches to the standard room view only on their own Teams client. [Rollout schedule] General Availability (Worldwide): Rollout will begin in late November 2026 and is expected to complete by early January 2027. General Availability (GCC, GCC High): Rollout will begin in mid-December 2026 and is expected to complete by late January 2027. [Impact on your organization] Who is affected Online participants using Microsoft Teams desktop on Windows and Mac who join meetings with a Microsoft Teams Room using Cloud IntelliFrame. Platforms and services Microsoft Teams for Windows Microsoft Teams for Mac Microsoft Teams Rooms using Cloud IntelliFrame What will happen The Turn off IntelliFrame option will be removed for online participants. If Cloud IntelliFrame is enabled for the room, online participants will see the IntelliFrame view sent by the Teams Room. If Cloud IntelliFrame is not enabled for the room, online participants will see the standard room view. This change does not affect how Cloud IntelliFrame is enabled or configured on Teams Rooms devices or any admin policies. In-room participants can continue to turn off IntelliFrame from the room console settings. [Action required and recommendations] No admin action is required. We recommend that you notify users who join meetings with IntelliFrame-enabled rooms about this change and update internal documentation that references the Turn off IntelliFrame option. [Learn more] Cloud IntelliFrame - Microsoft Teams | Microsoft Learn -
Create project kickoff presentations with Copilot in PowerPoint
MC1521606 · stayInformed · normal · Updated 10/22/2026 23:13
Services: Microsoft 365 apps
Read message
[What and Why:] We are introducing a new Copilot skill in PowerPoint that helps users create formal project kickoff presentations for kickoff meetings, project launches, and new-project alignment. The skill helps teams align on project goals, roles, milestones, scope, risks, schedule, success measures, and next steps. [Rollout Schedule:] General Availability (Worldwide): We will begin rolling out in mid October 2026 and expect to complete by late October 2026. [Impact on Your Organization:] Who is affected: Users with access to Copilot in PowerPoint. Platforms/Services: Microsoft 365 apps (PowerPoint on Win32, Mac, and Web) What will happen: Users will be able to use a scenario-specific skill to create project kickoff presentation drafts. This can help project teams prepare alignment materials faster and create a shared starting point for project execution. [Action Required/Recommendations:] No admin action is required. You may want to inform users that this new Copilot skill is becoming available in PowerPoint on Win32, Mac, and Web. [Compliance considerations:] No compliance considerations identified. Review as appropriate for your organization. -
Insights Agent V2 Frontier
MC1520901 · planForChange · normal · Updated 10/22/2026 17:34
Services: Microsoft 365 suite
Read message
[What and Why:] Insights Agent V2 is now available in Frontier Insights Agent V2 gives M365 admins tenant-level visibility into agent adoption. M365 admins retain control over whether user feedback is shared with agent owners. Learn more: Explore user feedback with Microsoft 365 Insights Agent [Rollout Schedule:] Public Preview (Worldwide): Roll out is completed. [Impact on Your Organization:] If you enable feedback sharing, agent owners can use Insights Agent to review user ratings, comments, and feedback themes for agents they own. Shared feedback is limited to your tenant, and submitter identities are not shown to agent owners. You control whether feedback is shared for all agents, selected agents, or no agents. [Action Required/Recommendations:] No action is required by default. Feedback sharing is off (“No agents”). To enable it, go to Agents > Settings > Agent feedback sharing in the Microsoft 365 admin center and select All agents or Selected agents. [Compliance considerations:] No compliance considerations identified. Review as appropriate for your organization. -
(Updated) Outlook: Copilot Prioritize feature will be retired
MC1519861 · planForChange · normal · Updated 10/22/2026 16:54
Services: Exchange Online
Read message
Updated October 22, 2026: We have updated the timeline and content. Thank you for your patience. [What and Why:] We're retiring the Copilot Prioritize feature in Outlook. Starting October 26, 2026, we'll begin to roll back the feature and remove the corresponding user experience from all Outlook clients as part of the cleanup effort. This change allows us to simplify the Outlook Copilot experience and focus our ongoing investments. [Rollout Schedule:] We will begin this change on October 26, 2026, and expect to complete by end of March 2027. [Impact on Your Organization:] Who is affected: Users who currently have access to Copilot Prioritize in Outlook. Platforms/Services: All Outlook clients Microsoft 365 Copilot What will happen: Copilot Prioritize will be retired, with the rollback beginning October 26, 2026, and expected to be completed by end of March 2027. The Prioritize user experience will be removed from all Outlook clients as part of the retirement and cleanup effort. Users will no longer be able to use the feature after retirement. No opt-in is required because this change removes an existing feature. [Action Required/Recommendations:] No administrative action is required. We recommend that you: Notify affected users of the retirement. Prepare your help desk and support teams for the change. Remove references to Copilot Prioritize from internal documentation, training, and support materials. [Compliance considerations:] No compliance considerations identified. Review as appropriate for your organization. -
(Updated) New SharePoint Mobile Experience on iOS and Android
MC1480870 · planForChange · normal · Updated 10/22/2026 16:42
Services: SharePoint Online
Read message
Updated October 22, 2026: We have updated the timeline. Thank you for your patience. [What and Why:] The SharePoint mobile app for iOS and Android is redesigned around the personalized SharePoint Discover experience, bringing your most relevant files, sites, people, and news together in one place, with improved site browsing, in-app file previews, refreshed news and search, dark mode, and better performance. [Rollout Schedule:] General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late October 2026 (previously mid-October) and expect to complete by end of November 2026 (previously mid-October). [Impact on Your Organization:] After this rollout, the SharePoint mobile app on iOS and Android will open to a redesigned home built around the personalized SharePoint Discover experience. Users who update the app will see a new home screen that brings together the files, sites, news, and updates from the people they work with that are most relevant to them, so they can get to what they need without navigating deep into SharePoint. Additionally, the app will reflect SharePoint branding and not that taken from the M365 admin centre. Users will be able to: Browse recent, favorite, and suggested sites with full site and hub navigation, and jump straight into a site's document libraries, lists, and news. Preview Word, Excel, PowerPoint, PDF, image, and video files in the app, with the option to open them in the dedicated app. Read news in a refreshed reading experience, including a filter for unread posts. Search SharePoint from a redesigned search experience and share files using the familiar Microsoft 365 sharing experience. Open SharePoint links directly in the app through deep linking, and use the app in dark mode. Your organization's home site, company news, document libraries, and lists remain available in the app. The Following option is now called Favorites, and news posts are saved for later by adding them to Favorites. The new experience replaces the current app design, includes performance and reliability improvements, and rolls out to the iOS app first, followed by the Android app. [Action Required/Recommendations:] No actions needed from the admin [Compliance considerations:] No compliance considerations identified. Review as appropriate for your organization. -
(Updated) Viva Engage: Email updates for users without a routable mailbox
MC1309743 · stayInformed · normal · Updated 10/22/2026 16:36
Services: Microsoft Viva
Read message
Updated September 30, 2026: We have updated the content timeline. Thank you for your patience. [Introduction] Viva Engage will stop sending email notifications to users who do not have a valid mailbox or routable email destination. Previously, email notifications could still be attempted for these users, resulting in repeated delivery retries, increased load on email systems, and, in some cases, delays to important business communications. This change reduces unnecessary email traffic, improves delivery efficiency, and helps ensure important communications are delivered reliably and on time. Users with supported mailbox configurations, including cloud mailboxes, on-premises mailboxes, shared mailboxes, and other routable email destinations, will continue to receive Viva Engage email notifications as expected. Notifications delivered through supported channels such as Microsoft Teams remain unaffected. [When this will happen:] General Availability (Worldwide): Rollout begins mid-October 2026 (previously end of September) and is expected to complete by end of December 2026 (previously end of October). [How this affects your organization:] Who is affected: Users who do not have a valid mailbox or routable email destination. Microsoft 365 admins managing Viva Engage users and mailbox configurations. What will happen: Viva Engage will no longer attempt to send email notifications to users who do not have a valid mailbox or routable email destination. Users with cloud, on-premises, shared, or other supported mailbox configurations will continue to receive email notifications as expected. This change does not affect the existing email notification experience for users with a valid mailbox or routable email destination. Notifications delivered through Microsoft Teams or other supported channels are not impacted. The change is enabled by default and applies automatically. Organizations may see:Reduced load on email systems and gateways. Fewer retry attempts for undeliverable messages. Improved email delivery efficiency and reliability. [What you can do to prepare:] No action is required. Review your Exchange Online licensing configuration to identify users without mailbox access. Evaluate your notification strategy (e.g., Teams vs. Email) for frontline workers. Inform helpdesk and user support teams of the expected behavior change. Update internal documentation if email notifications are referenced for frontline users. [Compliance considerations:] Alters how existing customer data is processed: Email notifications to users without mailboxes are no longer attempted, reducing unnecessary processing of undeliverable messages. No other compliance impacts identified. -
Microsoft Teams: Phishing detection for messaging
MC1519866 · stayInformed · normal · Updated 10/21/2026 23:32
Services: Microsoft Teams
Read message
[What and why] Microsoft Teams is introducing AI-powered, context-aware phishing detection to help identify phishing, social engineering, impersonation attempts, and deceptive intent. The capability analyzes conversation context to identify suspicious behavior that may not include traditional indicators such as malicious links or files. [Rollout schedule] Targeted Release: Beginning in early November 2026 and expected to complete by mid-November 2026 General Availability (Worldwide): Beginning in early December 2026 and expected to complete by mid-December 2026 [Impact on your organization] Who is affected For most users, detection focuses on external first-contact chats. Teams mobile users in China may also receive additional phishing and fraud protection for in-tenant conversations. Platforms and services Microsoft Teams What will happen Teams will use AI-powered, context-aware detection to identify potential phishing and related suspicious behavior. During initial quality validation, detection may run in the background without showing warnings to users. After validation, users may see a warning when potential phishing is detected: For Teams mobile users in China, additional protection may also apply to in-tenant conversations to address fraud patterns observed in the region. This capability is used only for security protection and not for productivity, summarization, advertising, user monitoring, or other non-security purposes. Customer message content is not retained by the detection system for model training or other secondary uses. No new admin configuration is required. [Action required and recommendations] No admin action is required to enable this protection. We recommend that admins review organizational guidance for interacting with unfamiliar external contacts and remind users to report suspicious activity or incorrect detections through available Teams reporting experiences. Learn more Phishing content detection in Microsoft Teams | Microsoft Support [Compliance considerations] QuestionAnswer Does the change alter how existing customer data is processed, stored, or accessed?Yes. Teams analyzes conversation context to detect suspicious behavior. The request states that customer message content is not retained by the detection system for model training or other secondary uses. Does the change introduce or significantly modify AI/ML capabilities that interact with customer data?Yes. The change introduces AI-powered, context-aware detection that analyzes conversation context for phishing, social engineering, impersonation attempts, and deceptive intent. -
Intelligent Call Delegation in Teams
MC1519860 · stayInformed · normal · Updated 10/21/2026 23:28
Services: Microsoft Teams
Read message
[What and Why:] Incoming Teams calls don't wait for a break in your day. Intelligent call delegation provides AI-powered calling assistance so you can focus on the conversations that matter most. It answers calls and gathers context, helping you decide whether to pick up and engage the caller. It can also schedule follow-up appointments through an integration with Microsoft Bookings so you can reconnect with callers at a more convenient time. This message is associated with Microsoft 365 Roadmap ID 565216 [Rollout Schedule:] Public Preview (Worldwide): We will begin rolling out in mid-November 2026 and expect to complete by late November 2026. General Availability (Worldwide): We will begin rolling out in January 2027 and expect to complete by late January 2027. [Impact on Your Organization:] Who is affected: Users provisioned with the appropriate Teams licensing for Intelligent call delegation. Platforms/Services: Microsoft Teams Calling Microsoft Bookings (for follow-up appointment scheduling) What will happen: Once a user is provisioned with the appropriate licensing, users will be enabled to configure Intelligent call delegation under Call Settings. Depending on admin configuration, users will have configuration options to personalize their intelligent delegate. [Action Required/Recommendations:] Admins will be enabled with Personal attendant policies that allow them to configure Intelligent call delegation settings for their users. [Compliance considerations:] No compliance considerations identified. Review as appropriate for your organization. -
Microsoft Teams: Chat for organizers and presenters in structured meetings and webinars on Teams Rooms on Android
MC1519857 · stayInformed · normal · Updated 10/21/2026 23:27
Services: Microsoft Teams
Read message
[What and Why:] When a Teams meeting or event has green room enabled and a Teams Rooms on Android joins the meeting/event as an organizer, people in the room will have access to the private chat for presenters that appears as a separate chat tab on the meeting chat pane. The chat tab is labelled "Event group" for events and "Planning group" for meetings. Presenters can use this private chat for backstage coordination. Users in the room can also switch to a separate chat that is shared by both presenters and attendees. This feature is available in Teams Rooms Pro licensed rooms. [Rollout Schedule:] Public Preview (Worldwide): We will begin rolling out in late August 2025 and expect to complete by mid November 2026. General Availability (Worldwide): We will begin rolling out in mid November 2026 and expect to complete by late November 2026. [Impact on Your Organization:] Who is affected: Organizations using Teams Rooms on Android, specifically Teams Rooms Pro licensed rooms. Platforms/Services: Microsoft Teams Rooms on Android Microsoft Teams meetings and events (green room enabled) What will happen: When a Teams Room on Android is joined to a meeting or event as an organizer, people in the room will have access to the private chat for presenters if the meeting or event has green room enabled. [Action Required/Recommendations:] No Teams Admin Center or Teams Pro Management Portal configuration changes are required to enable this feature. [Compliance considerations:] No compliance considerations identified. Review as appropriate for your organization. -
Microsoft 365 apps: Updated Brand Kit management experience
MC1519846 · stayInformed · normal · Updated 10/21/2026 23:17
Services: Microsoft 365 apps
Read message
[What and why] Microsoft is updating the Brand Kit management experience to make it easier for Brand Managers to set up and maintain their organization’s Brand Kits. The updated experience provides clearer setup guidance, streamlined management of brand assets, and improved workflows as an organization’s brand evolves. This reduces the time and effort required to bring approved brand assets together and helps organizations scale on-brand content creation with Copilot. [Rollout schedule] General Availability (Worldwide): Available now [Impact on your organization] Who is affected Organizations that use Brand Kits and Brand Managers who create or manage them Platforms and services Microsoft 365 apps Brand Kits What will happen Brand Managers will see a simplified experience for creating and configuring Brand Kits, with clearer setup and preparation guidance. Asset management will be streamlined for adding and managing templates, logos, images, icons, colors, and fonts. Brand Managers will have improved workflows for maintaining Brand Kits as their organization’s brand evolves. Existing Brand Kits and their configured assets will remain available. Brand Managers can continue to create and manage Brand Kits using their existing permissions and workflows. [Action required and recommendations] No action is required to prepare for this update. We recommend that you: Inform Brand Managers in your organization about the updated experience. If your organization has not configured Brand Managers, consider identifying the appropriate individuals responsible for managing your organization’s brand and Brand Kits. Learn more Configure access and governance for Brand Kits | Microsoft Support Create and Manage Official Brand Kits in Microsoft Copilot | Microsoft Support [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
Microsoft OneNote: JPG and PNG references in Copilot Notebooks
MC1519842 · stayInformed · normal · Updated 10/21/2026 23:15
Services: Microsoft 365 apps
Read message
[What and why] We are introducing support for using JPG and PNG files as knowledge sources in Microsoft Copilot Notebooks. This enhancement allows users to add images directly to notebooks alongside supported document types. Copilot can use content contained within these images, including text, charts, diagrams, and other visual elements, as grounding context to generate more relevant presentations, reports, briefs, and other outputs. This update helps users incorporate information stored in images into their Copilot Notebook workflows without additional processing steps. [Rollout schedule] Public Preview (Worldwide): Rollout has completed. General Availability (Worldwide): Rollout began in early October 2026 and is expected to complete by late October 2026. [Impact on your organization] Who is affected Users with access to Copilot Notebooks who can use JPG and PNG files as Copilot grounding sources. Platforms and services Microsoft OneNote Copilot Notebooks What will happen Users will be able to add JPG and PNG files as knowledge sources in Copilot Notebooks. Copilot will be able to use information contained in supported images, including text, charts, diagrams, and other visual content, as grounding context. Organizations that already allow Copilot to reason over JPG and PNG files will receive this capability automatically. No new admin controls or configuration changes are introduced with this rollout. [Action required and recommendations] No action is required. We recommend that you notify users that image files can be used as knowledge sources in Copilot Notebooks once the feature becomes available in your organization. [Compliance considerations] No compliance considerations identified, review as appropriate for your organization. -
Microsoft OneNote: CSV and TSV references in Copilot Notebooks
MC1519841 · stayInformed · normal · Updated 10/21/2026 23:14
Services: Microsoft 365 apps
Read message
[What and why] We are introducing support for using CSV and TSV files as knowledge sources in Microsoft Copilot Notebooks. This enhancement allows users to add structured lists and tabular data directly to notebooks alongside existing document types. By including CSV and TSV content as reference material, Copilot can generate more relevant and informed outputs such as presentations, reports, briefs, and other content grounded in both structured and unstructured data. [Rollout schedule] Public Preview (Worldwide): Rollout has completed. General Availability (Worldwide): Rollout began in mid-October 2026 and is expected to complete by late October 2026. [Impact on your organization] Who is affected Organizations with Microsoft 365 Copilot and access to Copilot Notebooks in OneNote. Users who work with CSV and TSV files as part of their Copilot workflows. Platforms and services Microsoft OneNote Microsoft 365 Copilot Copilot Notebooks What will happen Users will be able to add CSV and TSV files as knowledge sources in Copilot Notebooks. Copilot will use data contained in these files alongside other referenced content when generating responses and content. The feature will be enabled automatically for tenants that already allow Copilot to reason over CSV and TSV files. No additional configuration will be required. [Action required and recommendations] No action is required. We recommend that you notify users who work with structured data that they can reference CSV and TSV files directly within Copilot Notebooks once the feature becomes available. [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
Microsoft Publisher: Reminder that support ends in October 2026
MC1469564 · planForChange · normal · Updated 10/21/2026 16:33
Services: Microsoft 365 apps
Action required by: 10/01/2026 07:00
Read message
Updated October 21, 2026: Publisher removal is rolling out through Office updates. Microsoft Publisher reached end of support in October 2026 and is being removed from Microsoft 365 Apps. The removal reaches each device through regular Office updates, so the timing depends on the update channel your organization uses. Each channel receives new builds on its own schedule. Devices on Current Channel get updates first, and devices on Monthly Enterprise Channel get them later. What this means for your users: Some users may keep access to Publisher for a period after October 1, 2026, until their channel's update rolls out. This is not an extension and does not mean Publisher is still supported. Treat any remaining access as a temporary window to open and convert impacted .pub files. Rollout timing: Removal starts with Version 2611 (Build 16.0.20625.xxxxx): Current Channel: starting mid-November 2026 Monthly Enterprise Channel: starting early December 2026 Until a device receives this update, Publisher may continue to open. We recommend converting any .pub files you need to keep before your devices receive the update. For build numbers and expected timing for your organization, contact Microsoft Support. [What and why] This post is a reminder that Microsoft Publisher will reach end of life in October 2026. After October 1, 2026, Publisher will no longer be included with Microsoft 365 subscriptions, and Microsoft 365 subscribers will no longer be able to open or edit Publisher (.pub) files using Publisher. To focus on delivering new value across Microsoft 365, Microsoft periodically retires products and features. Many common Publisher scenarios are already supported in Microsoft Word and Microsoft PowerPoint, and customers can also access a broad library of templates through Microsoft Create. For additional background, refer to MC716267. [Rollout schedule] This is a retirement reminder. No feature rollout is associated with this announcement. Key dates: October 1, 2026: Publisher will no longer be available to Microsoft 365 subscribers. October 13, 2026: Support for the perpetual version of Publisher will end when Office LTSC 2021 reaches end of support. [Impact on your organization] Who is affected Organizations with users who currently use Microsoft Publisher Organizations that store or maintain Publisher (.pub) files that may need to be accessed after October 1, 2026 Platforms and services Microsoft Publisher Microsoft 365 Apps Microsoft Word Microsoft PowerPoint Microsoft Create What will happen Users can continue using Publisher with its current functionality until October 1, 2026. Microsoft 365 subscribers will no longer be able to open or edit Publisher (.pub) files in Microsoft Publisher. Common Publisher use cases such as creating branded materials, labels, envelopes, calendars, business cards, flyers, and similar content can be completed using Word, PowerPoint, and templates available through Microsoft Create. Organizations that need continued access to Publisher content should migrate or convert their files before October 1, 2026. [Action required and recommendations] Action recommended: Identify Publisher files that need to be preserved and convert them to a supported format before October 1, 2026. To prepare for Publisher retirement: Save Publisher files as PDF if they only need to be viewed, shared, or printed after Publisher is retired. For files that require continued editing, convert or migrate content to Microsoft Word or Microsoft PowerPoint before October 1, 2026. Review existing Publisher-based business processes and transition them to Word, PowerPoint, or Microsoft Create templates where appropriate. Search for existing Publisher (.pub) files across local storage, OneDrive, and SharePoint to identify content requiring migration. Learn more For migration guidance, file conversion recommendations, supported alternatives, and answers to frequently asked questions, see: Microsoft Publisher will no longer be supported after October 2026 | Microsoft Support [Compliance considerations] No compliance considerations identified, review as appropriate for your organization. -
Microsoft 365 apps: Introducing Update Repair in Inventory
MC1518032 · stayInformed · normal · Updated 10/20/2026 23:00
Services: Microsoft 365 suite, Microsoft 365 apps
Read message
[What and why] We are introducing Update Repair in Inventory to help admins identify and remediate Windows devices with Microsoft 365 apps that are out of date or experiencing update issues. In the Microsoft 365 apps admin center, admins can review device status and recommended actions, remotely start Online Repair for eligible devices, and follow manual remediation guidance for devices that need attention. Repair reinstalls Microsoft 365 apps using the latest available build for the device's configured update channel. [Rollout schedule] Public Preview (Worldwide): Rollout began in mid-October 2026 and is expected to complete by late October 2026. General Availability (Worldwide): Rollout will begin in mid-November 2026 and is expected to complete by late November 2026. [Impact on your organization] Who is affected Admins managing Windows devices with Microsoft 365 apps installed. Platforms and services Windows devices with Microsoft 365 apps Microsoft 365 apps admin center What will happen Admins can more easily identify devices with Microsoft 365 apps update issues and decide how to remediate them. Eligible devices can be repaired remotely, reducing the need for hands-on intervention. Repair closes open Office apps and reinstalls Microsoft 365 apps. Devices that need attention still require administrator review and manual remediation. [Action required and recommendations] Go to the Microsoft 365 apps admin center and make sure Inventory is enabled. Update Repair uses Inventory data from Windows devices with Microsoft 365 apps installed to identify devices that need attention or repair. For the Repair action, devices must be running build 16.0.20326.20000 or later. Before starting a repair, notify affected users, ask them to save their work and close Office apps, and schedule the action to minimize disruption. Keep devices powered on, signed in, and connected so they can receive the action at their next Inventory check-in. [Learn more] Use Update Repair to identify and remediate Microsoft 365 Apps update issues - Microsoft 365 Apps | Microsoft Learn [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
(Updated) Microsoft 365 Copilot: Intelligent Summaries in Copilot Dashboard
MC1266912 · stayInformed · normal · Updated 10/20/2026 22:37
Services: Microsoft Viva
Read message
Updated October 20, 2026: We have updated the timeline. Thank you for your patience. [Introduction] Intelligent summaries in Copilot Dashboard help you quickly understand what’s driving Copilot adoption in your organization. These AI‑generated insights highlight key usage trends, areas of success, and opportunities where focused attention can accelerate value. Suggested prompts guide deeper exploration of underlying drivers and adoption patterns. This message is associated with Microsoft 365 Roadmap ID 557681. [When this will happen] General Availability (Worldwide): Rollout will begin in November 2026 (previously mid-August) and is expected to complete by end of November 2026 (previously late September). [How this will affect your organization] Who is affected Admins using the Microsoft 365 Copilot Dashboard in Microsoft Viva and Microsoft 365 What will happen Intelligent summaries will appear automatically in the Copilot Dashboard: Admins will see AI‑generated insights that highlight adoption trends and key usage patterns. Suggested prompts will be available to help admins drill into specific drivers and areas of opportunity. No configuration changes are required; the feature is on by default for eligible tenants. Existing admin controls and permissions remain unchanged. There is no user workflow impact. [What you can do to prepare] No action is required before rollout. If helpful for your organization, you may: Notify helpdesk or training teams about the new summaries. Update internal documentation that references the Copilot Dashboard. Review updated online documentation, which will be refreshed as rollout begins in late April. If you choose not to use this feature, you can roll back by disabling intelligent summaries using available admin controls. [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
Microsoft OneDrive: OneDrive sync supports up to 1 million items on macOS
MC1477187 · stayInformed · normal · Updated 10/20/2026 18:14
Services: Microsoft OneDrive
Read message
[What and why] In MC1294528, we announced an increase to the item sync limit for OneDrive on Windows. We are now increasing the same item sync limit for OneDrive on macOS: from 300,000 items to 1 million items per sync instance, per device. This increase is designed to help organizations with large OneDrive and SharePoint libraries sync more content reliably across devices. The capability will be available first in Public Preview for devices enrolled in the Insiders ring, and later in General Availability. Devices that do not meet the minimum hardware and configuration requirements will continue to sync at the existing supported limit of 300,000 items without disruption. [Rollout schedule] Public Preview (Worldwide): Rollout will begin in mid-October 2026 and is expected to complete by late October 2026. [Impact on your organization] Who is affected Users syncing OneDrive, OneDrive for Business, or SharePoint document libraries on macOS. Users with libraries that approach or exceed the current supported sync limit of 300,000 items. Preview participants using the Insiders ring. Platforms and services macOS OneDrive OneDrive for Business SharePoint document libraries What will happen macOS devices that meet the minimum hardware and configuration requirements can sync up to 1 million items per sync instance. Devices that do not meet these requirements will see no change in behavior. No disruption to existing sync configurations is expected. Note: Performance is not yet optimized for syncing a high volume of read-only files or for accounts under legal hold. We are actively working to improve performance and reliability for these scenarios. [Action required and recommendations] No action is required if you do not plan to participate in Public Preview. If you plan to evaluate this capability: Identify users and devices with large OneDrive or SharePoint libraries that may benefit from the increased sync limit. Ensure devices meet the minimum hardware and configuration requirements (i.e., supported operating system, memory, storage, and processor). Review the recommended sync configuration for OneDrive and SharePoint sync reliability. Inform helpdesk staff and affected users that Public Preview requires the Insiders ring and that devices that do not meet the minimum hardware and configuration requirements will remain at the current supported limit. [Learn more] Recommended sync app configuration - SharePoint in Microsoft 365 | Microsoft Learn Restrictions and limitations in OneDrive and SharePoint | Microsoft Support The OneDrive sync app update process - SharePoint in Microsoft 365 | Microsoft Learn [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
Microsoft OneDrive: Copilot actions in the File Explorer context menu are being retired
MC1515940 · planForChange · normal · Updated 10/20/2026 17:35
Services: Microsoft OneDrive
Read message
[What and why] We're simplifying how people use Copilot with their OneDrive files in File Explorer. As part of this change, we're retiring the OneDrive Copilot Summarize, Create FAQ, Compare Files, Ask a question, Explain image, Explain images, Compare images, Extract text actions from the File Explorer context menu. Users can continue to work with their OneDrive files in Copilot from one central place by right-clicking a file and selecting Ask Copilot, or by hovering over a file in File Explorer Home and selecting the Copilot icon. The OneDrive Copilot actions will also remain available in the OneDrive activity center. [Rollout schedule] General Availability (Worldwide): Retirement will begin in mid-November 2026 and is expected to complete by early December 2026. [Impact on your organization] Who is affected Users who use Copilot with OneDrive files in File Explorer. Platforms and services OneDrive Copilot File Explorer What will happen The OneDrive Copilot Summarize, Create FAQ, Compare Files, Ask a question, Explain image, Explain images, Compare images, and Extract text actions will be retired from the File Explorer context menu. The OneDrive Copilot actions will remain available in the OneDrive activity center. Users can either right-click a OneDrive file and select Ask Copilot or hover over a file in File Explorer Home and select the Copilot icon to open a new Copilot conversation with the file attached. Files are attached by reference, so their existing permissions and protections continue to apply. Simplified Copilot experience for OneDrive files in File Explorer Retired context menu actions for OneDrive files in File Explorer [Action required and recommendations] No administrative action is required. We recommend that you notify users about this change and update any training or help desk documentation that references the retiring File Explorer context menu actions. -
(Updated) Microsoft OneDrive: Refreshed file browsing and filtering experience in OneDrive Web
MC1457226 · planForChange · normal · Updated 10/20/2026 16:57
Services: Microsoft OneDrive
Read message
Updated October 20, 2026: We have updated the timeline. Thank you for your patience. [What and why] We're updating OneDrive for the web to align its file browsing experience with the modern SharePoint document library experience. This update introduces improved navigation and expanded filtering capabilities to help users find, organize, and manage files more efficiently across Microsoft 365. The changes also provide a more consistent experience between OneDrive and SharePoint. This message is associated with Microsoft 365 Roadmap ID 566316. [Rollout schedule] Targeted Release: Beginning in mid-August 2026 and expected to complete by late August 2026 General Availability (Worldwide): Beginning in late August 2026 and expected to complete by late October 2026 (previously mid-September) [Impact on your organization] Who is affected All users of OneDrive Web Platforms and services OneDrive for the web SharePoint Online What will happen Users will see a refreshed file browsing and filtering experience in OneDrive for the web. Key changes include: OneDrive for the web will use the modern SharePoint document library experience for file browsing and management. Updated navigation and layout will provide a more consistent file management experience across Microsoft 365. Enhanced filtering capabilities will be available in folder-based views such as My files and Shared. Users can filter content by file type. Filters can be applied using filter pills and the filter pane. Improved filtering across OneDrive views. Users can apply multiple filters simultaneously. Enhanced filtering will be available in Home, Shared, People, Meetings, and Favorites views. Navigation, filtering, and file management behaviors will be more closely aligned between OneDrive and SharePoint. The feature will be enabled by default. Existing permissions, sharing settings, and policies are unchanged. [Action required and recommendations] No action is required. We recommend that you: Review and update internal training materials that reference the current OneDrive experience. Inform help desk and support teams about the updated navigation and filtering experience. Communicate the upcoming changes to users who regularly use OneDrive for the web. [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
(Updated) Microsoft Viva - Copilot Analytics: Export agent data from the Agent Dashboard
MC1288531 · planForChange · normal · Updated 10/20/2026 16:54
Services: Microsoft Viva
Read message
Updated October 20, 2026: We have updated the timeline. Thank you for your patience. [Introduction] To support deeper analysis of Copilot agent adoption and usage across your organization, Microsoft will introduce a new export capability in the Agent Dashboard. This feature will allow eligible users to download de‑identified Copilot agent usage data for analysis, helping organizations track adoption trends, optimize licensing, and support AI transformation strategies, while maintaining existing privacy and access controls. User identifiers are removed from the output. This feature will require at least 50 Microsoft 365 Copilot licenses and will apply to the Viva Insights web app. This message is related to Roadmap ID 560538. [When this will happen] Public Preview: We will begin rolling out in late May 2026 and expect to complete rollout by early June 2026. General Availability (Worldwide): We will begin rolling out in mid-November 2026 (previously late October) and expect to complete rollout by end of November 2026 (previously early November). [How this affects your organization] Who is affected Agent Dashboard users with full company‑level data access, including:Senior leaders (as identified in Microsoft Entra ID) Admin‑assigned company‑level users Delegates with company‑level access Global analysts and admins Note: Group managers with data access limited to their own teams will not have access to this feature. What will happen Eligible users will be able to export de‑identified, user‑level Copilot agent metrics and agent attributes aggregated by user and week, for up to the past six months. User identifiers are removed from the output. The export will include multiple data tables, such as:Copilot agent metadataincluding agent name, creator type, and publishing source Copilot agent usage metrics, including the number of responses generated Copilot agent credit usage and user retention metrics People metadata, including organization and function type By default, this feature will be ON for all eligible users. Admins will be able to manage or disable the feature at the tenant or group level at any time using Viva Feature Access Management (VFAM):Module: Viva Insights Feature: Agent Metrics Export There will be no impact to user workflows unless the feature is accessed by eligible users. Screenshot - View of the Agent Dashboard: [What you can do to prepare] No action is required to enable this feature. If you do not want this feature enabled by default, you can disable it at the tenant or group level using Viva Feature Access Management (VFAM). Review which users have full company‑level access to the Agent Dashboard. Communicate the upcoming change to eligible users so they understand the new export capability and its intended use. Learn more: Connect to the Agent Dashboard | Viva Insights | Microsoft Viva | Microsoft Learn Delegate access to the Copilot Dashboard, Agent Dashboard, and Copilot insights | Viva Insights | Microsoft Viva | Microsoft Learn Manage settings for the Microsoft Copilot Dashboard, Agent Dashboard, and Viva Insights web app | Viva Insights | Microsoft Viva | Microsoft Learn Using Entra ID data - Connect to the Microsoft Copilot Dashboard for Microsoft 365 customers | Viva Insights | Microsoft Viva | Microsoft Learn Viva features management - Control access to features in Microsoft 365 | Microsoft Viva | Microsoft Learn [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
(Updated) Microsoft Teams: Facilitator can join channel meetings
MC1461165 · stayInformed · normal · Updated 10/20/2026 16:36
Services: Microsoft Teams
Read message
Updated October 20, 2026: We have updated the timeline. Thank you for your patience. [What and why] We’re expanding Facilitator support in Microsoft Teams channel meetings. Users will be able to add Facilitator to channel meetings to take notes, manage the agenda, answer questions, and manage tasks. This message is associated with Microsoft 365 Roadmap ID 568936. [Rollout schedule] Targeted Release: Beginning in early February 2027 (previously early November 2026) and expected to complete by mid-February 2027 (previously mid-November 2026) General Availability (Worldwide): Beginning in mid-February 2027 (previously mid-November 2026) and expected to complete by early March 2027 (previously early December 2026) [Impact on your organization] Who is affected Organizations that have enabled Facilitator in Microsoft Teams Users licensed for Facilitator Platforms and services Microsoft Teams Teams channel meetings What will happen Users will be able to add Facilitator to channel meetings. Facilitator can take notes, manage the agenda, answer questions, and manage tasks. [Action required and recommendations] No action is required to prepare for this update. [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
Dynamics 365 Contact Center - Let representatives set next presence to handle routing of work items
MC1483419 · stayInformed · normal · Updated 10/20/2026 14:45
Services: Dynamics 365 Apps
Read message
We are announcing the ability to allow representatives to set next presence to indicate their future availability in Dynamics 365 Contact Center. This feature will reach general availability on October 30, 2026. How does this affect me? Next presence allows service representatives to queue their next availability status and stop receiving new assignments while the next presence status is pending. After all active conversations and work items are completed, the system automatically updates the representative's presence to the selected status. This setting allows representatives to transition smoothly to breaks or other availability states without interrupting customer engagements or requiring manual status changes. What action do I need to take? This message is for awareness, and no action is required. If you would like more information on this feature, please visit Enable and update next presence. -
Sending from Aliases
MC1515939 · planForChange · normal · Updated 10/19/2026 23:31
Services: Exchange Online
Read message
[What and Why:] We're pleased to announce that Sending from Aliases is now generally available for Exchange Online. We are continuing to investigate additional capabilities, including per-alias display names, further filtering and default controls, and calendar support post GA. For more details on the feature, review the blog post below. [Rollout Schedule:] Available now. [Impact on Your Organization:] Who is affected: Users and admins in organizations using Exchange Online. What will happen: This feature allows users to send emails from any alias configured on their mailbox, improving flexibility and reducing the need for workarounds. [Action Required/Recommendations:] Admins can enable this feature via PowerShell or the Exchange Admin Center Settings. Learn more: Sending from Aliases is now generally available [Compliance considerations:] No compliance considerations identified. Review as appropriate for your organization. -
External Recipients Banner on Outlook Mobile
MC1515932 · stayInformed · normal · Updated 10/19/2026 23:19
Services: Exchange Online
Read message
[What and Why:] When you add an attendee outside your organization to a meeting, Outlook will display a banner warning you that external recipients are included. [Rollout Schedule:] General Availability (Worldwide): We will begin rolling out on late October 2026 and expect to complete by late November 2026. [Impact on Your Organization:] Helps users avoid accidentally inviting external attendees to meetings by clearly identifying recipients outside their organization, reducing the risk of unintentionally sharing sensitive information. [Action Required/Recommendations:] No action is required [Compliance considerations:] No compliance considerations identified. Review as appropriate for your organization. -
Microsoft Teams: Simplified app enablement experience in Teams admin center
MC1515931 · stayInformed · normal · Updated 10/19/2026 23:18
Services: Microsoft Teams
Read message
[What and why] Microsoft is introducing a simplified app enablement experience in Teams admin center. The new guided flow brings together key app management actions, including setting who can access an app, choosing who should have the app installed, reviewing and accepting required permissions, and allowing or blocking the app. The flow adapts to the app’s current state and highlights steps that require attention, reducing the steps and navigation needed to manage app enablement. [Rollout schedule] General Availability (Worldwide): Beginning in mid-October 2026 and is expected to complete by mid-November 2026 [Impact on your organization] Who is affected Admins who manage agents and apps in Microsoft Teams admin center Platforms and services Microsoft Teams admin center What will happen Admins can use the new guided experience in Teams admin center under Teams apps > Manage apps > Manage access. The experience shows admins the actions needed to control access to the agent in Teams. Admins can review app availability, installation, and permission changes before applying them. Note: Existing tenant app settings will not change as a result of this rollout. Changes are applied only after an admin reviews the configuration and selects Apply. [Action required and recommendations] No action is required before this rollout. We recommend that you: Update internal app management documentation or training materials as appropriate. Continue to follow your organization's existing processes for app approval and permission consent. [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
Cowork browser use setting renamed to Browser use in Microsoft Copilot
MC1515930 · stayInformed · normal · Updated 10/19/2026 23:18
Services: Microsoft 365 suite
Read message
[Introduction] We’re renaming the Cowork settings panel in Copilot Settings to Browser use in Microsoft Copilot. This panel contains the setting that lets admins manage whether Copilot apps can use the Microsoft Edge browser to perform tasks on behalf of users. This change makes the browser use setting easier for admins to find and manage as we organize Cowork-related controls into more discoverable, capability-specific settings. There is no change to the setting’s functionality or existing configuration as part of this rename. [When this will happen:] General Availability (Worldwide): We will begin rolling out on mid October 2026 and expect to complete by mid October 2026. [How this will affect your organization:] The Cowork settings panel will be renamed to Browser use in Microsoft Copilot. The new name makes it easier for admins to identify and discover the setting that controls whether Copilot apps can use the Microsoft Edge browser to perform tasks on behalf of users. There is no change to the functionality or existing configuration of the setting as a result of this rename. [What you need to do to prepare:] No action is required. Existing configurations will remain unchanged. Admins should be aware that the setting previously found under Cowork will now appear as Browser use in Microsoft Copilot in Copilot Settings. -
Microsoft Teams: GitHub app consolidation and legacy GitHub app deprecation
MC1515929 · planForChange · normal · Updated 10/19/2026 23:17
Services: Microsoft Teams
Read message
[What and Why:] We are consolidating GitHub Notifications and GitHub Copilot capabilities into a single GitHub app in Microsoft Teams. The new app brings repository updates and GitHub Copilot coding capabilities together, so users can follow GitHub activity and act on it within Teams. As part of this consolidation, the legacy GitHub app will be deprecated by November 16, 2026 and displayed as GitHub (deprecated) until it is retired. Users of the legacy app should remove it from their Teams conversations and add the new app, named GitHub, to those conversations before this date. Users of the existing GitHub Notifications app need to update the app to the latest version. This app is being renamed GitHub and brings GitHub Copilot capabilities to users with an eligible GitHub Copilot license. [Rollout Schedule:] General Availability (Worldwide): We will begin rolling out in mid-October 2026 and expect to complete by mid-November 2026. Legacy GitHub app deprecation: The legacy app will be deprecated on November 16, 2026. [Impact on Your Organization:] Users of the legacy GitHub app: The app will appear as GitHub (deprecated). Users should remove it from their Teams conversations and add the new GitHub app to those conversations before November 16, 2026. Users of GitHub Notifications: The app must be manually updated to the latest version. The app is being renamed GitHub, with GitHub Copilot capabilities available to users with an eligible GitHub Copilot license. [Action Required/Recommendations:] Notify affected users to remove the legacy GitHub app from Teams conversations and add the new GitHub app before November 16, 2026. Review your organization's Teams app access policies to ensure the new GitHub app is available to users who need it. Ask existing users of the GitHub Notifications app to update the app to the latest version. Ask users to confirm that the new GitHub app delivers notifications for the repositories and event types they follow to the intended Teams conversations. If your organization restricts resource-specific consent (RSC), configure the applicable team and chat consent policies to allow the GitHub app’s required RSC permissions so GitHub Copilot can use chat and thread history as context. Learn how to configure RSC permissions here. Update internal guidance to identify the updated app and distinguish it from GitHub (deprecated). [Compliance considerations:] QuestionAnswer Does the change include an admin control and can it be controlled through Entra ID group membership?Yes. Admins can use Teams app access policies and app management controls to manage app availability for users. Review your organization's Teams app governance policies as appropriate. Does the change provide a new way of communicating between users, tenants, or subscriptions?No. The change consolidates existing GitHub app capabilities into a single Teams app and deprecates the legacy app. -
Database Hub in Fabric: Default enablement and admin opt-out
MC1515917 · planForChange · normal · Updated 10/19/2026 23:09
Services: Power BI
Action required by: 11/17/2026 08:00
Read message
[What and Why:] Microsoft Fabric is updating the Database Hub tenant setting so Database Hub is enabled by default on November 17, 2026. Database Hub is currently in preview and gives database teams a central place in Microsoft Fabric to discover supported databases across Azure, Fabric, on-premises, and supported multicloud environments. Database Hub helps teams review available performance, security, utilization, and best-practice findings, investigate issues, and take action through guided experiences and database tools. This change makes Database Hub available without requiring admins to enable it manually. Default enablement adds no cost, and does not move databases into Fabric or change underlying database resources. Database Hub uses users’ existing Azure role-based access control (RBAC) permissions for Azure resources and existing Fabric permissions for Fabric resources. Users can view only the resources and insights their permissions allow. Enabling Database Hub does not grant additional access or change these permissions. Available capabilities depend on permissions, supported resources, configuration, and region. Resources or services customers choose to use through linked experiences remain subject to their own pricing and licensing requirements. [Rollout Schedule:] General Availability (Worldwide): Database Hub tenant setting default enablement will begin on November 17, 2026 and is expected to complete on November 17, 2026. [Impact on Your Organization:] Who is affected: Admins who manage Microsoft Fabric tenant settings. Database teams and users who are authorized to view supported database resources and related insights. Platforms/Services: Microsoft Fabric Database Hub Fabric admin portal What will happen: The Database Hub tenant setting will be enabled by default on November 17, 2026. Users with appropriate permissions will be able to access Database Hub without an admin first enabling the tenant setting. Admins can disable the Database Hub tenant setting in the Fabric admin portal if Database Hub does not meet their organization’s needs. No databases are moved or changed, and no additional permissions are granted by this default enablement. [Action Required/Recommendations:] No action is required if your organization wants Database Hub to be available by default. If your organization does not want Database Hub enabled, admins can go to the Fabric admin portal, open Tenant settings, search for Database Hub, and disable the setting after it is enabled on November 17, 2026. Admins may also review Database Hub documentation and assess the capability against their organization’s governance and operational needs. [Compliance considerations:] QuestionAnswer Does the change include an admin control?Yes. Admins can manage the Database Hub tenant setting in the Fabric admin portal and can disable Database Hub if it does not meet their organization’s needs. Does the change alter how admins can monitor, report on, or demonstrate compliance activities?Yes. Database Hub can surface available performance, security, utilization, and best-practice findings for supported databases, based on existing permissions and supported resource configuration. -
Microsoft Purview | Data Lifecycle Management - Graph API Support for archive mailboxes
MC1469565 · planForChange · normal · Updated 10/19/2026 21:02
Services: Microsoft Purview
Action required by: 10/01/2026 07:00
Read message
[What and why] As part of the retirement of Exchange Web Services (EWS) in Exchange Online, Microsoft is expanding support for archive mailbox scenarios through Microsoft Graph APIs. Organizations that currently use EWS to access archive mailbox data should begin migrating to Microsoft Graph APIs before EWS is disabled. Microsoft Graph now provides API support for importing and exporting mailbox data and for managing archive mailbox folders, including support for auto-expanding archives. This change helps ensure continued access to archive mailbox data after EWS is retired and provides a supported path forward for compliance, data lifecycle management, eDiscovery, backup, and related archive mailbox solutions. [Rollout schedule] General Availability (Worldwide): Beginning in late October 2026 and expected to complete by early November 2026 Important: Exchange Web Services (EWS) in Exchange Online will begin to be disabled globally in October 2026 and is expected to be fully disabled by April 2027 [Impact on your organization] Who is affected Organizations that use applications, scripts, or third-party solutions that rely on EWS to access archive mailbox content. Examples include: eDiscovery solutions Compliance and records management workflows Data lifecycle management solutions Backup and export tools Custom applications that access archive mailboxes Platforms and services Microsoft Purview Exchange Online Microsoft Graph What will happen Applications and scripts that continue to use EWS for archive mailbox operations will stop functioning after EWS is disabled. Organizations using auto-expanding archive mailboxes must update applications to support Microsoft Graph archive mailbox behaviors. Microsoft Graph APIs support archive mailbox scenarios through:Mailbox import and export APIs MailboxFolder APIs for folder management operations Applications may need to handle redirect responses when archive content resides in auxiliary archive mailboxes. [Action required and recommendations] Action required: Yes Before October 2026, we recommend that administrators and developers: Identify applications and scripts that use EWS to access archive mailboxes.Review EWS Usage Reports: https://learn.microsoft.com/microsoft-365/admin/activity-reports/ews-usage Review Microsoft Graph archive mailbox guidance.Review Archive mailbox redirects: https://learn.microsoft.com/graph/handle-archive-mailbox-redirects Update applications to use Microsoft Graph APIs for archive mailbox operations.Review Mailbox import and export overview: https://learn.microsoft.com/graph/mailbox-import-export-concept-overview Use available migration resources to assess and update existing code.EWS Analyzer and migration tools: https://aka.ms/ewsTools AI-assisted migration tutorial: https://aka.ms/ewsToolsAITutorial EWS-to-Microsoft Graph API mappings: https://aka.ms/ews2graphMap Contact third-party vendors to confirm their plans and timelines for migrating from EWS to Microsoft Graph. Learn more Deprecation of EWS in Exchange Online EWS migration tools Exchange Web Services (EWS) to Microsoft Graph API mappings Handle archive mailbox redirects in Microsoft Graph Overview of the mailbox import and export APIs in Microsoft Graph https://learn.microsoft.com/graph/mailbox-import-export-concept-overview Tutorial - Migrating from EWS to Microsoft Graph API with GitHub Copilot [Compliance considerations] QuestionAnswer Does this change modify, interrupt, or disable Purview-related capabilities, including retention, eDiscovery, export, or data lifecycle management workflows?Yes. Organizations using EWS-based integrations for eDiscovery, compliance exports, retention-related processes, or data lifecycle management that access archive mailboxes must migrate to Microsoft Graph APIs before EWS is disabled. Does this change alter how users or applications access, export, or manage Microsoft 365 data?Yes. Applications that access or export archive mailbox data through EWS must be updated to use Microsoft Graph APIs to maintain functionality after EWS retirement. Does this change add or affect third-party integrations?Yes. Third-party applications and services that use EWS to access archive mailbox content may require vendor-provided updates or migration to Microsoft Graph APIs. Does this change affect how organizations demonstrate or maintain compliance processes?Yes. Organizations that rely on EWS-based compliance, auditing, export, or records management workflows for archive mailbox data should review and update their integrations to ensure continuity of compliance operations. -
(Updated) Microsoft Teams: New centralized experience for organizing important resources in chats and channels
MC1473153 · stayInformed · normal · Updated 10/19/2026 17:25
Services: Microsoft Teams
Read message
Updated October 19, 2026: We have updated the timeline. Thank you for your patience. [What and why] We are introducing a more consistent way for users to access and manage important resources in Microsoft Teams chats and channels. Users will be able to pin frequently used resources directly below the chat or channel header, pin multiple messages alongside other resources, and organize them into folders. On Microsoft Teams mobile, users will be able to access shared resources and folders by tapping the chat or channel header. This change will help users stay organized and provide them with a centralized location to quickly find, access, and manage important resources. As part of this update, the In this chat and In this channel panes will be removed. Existing resources within these panes will be accessible through the new resource management experience. [Rollout schedule] Targeted Release (Worldwide): Rollout begins in late September 2026 and is expected to complete by early October 2026. General Availability (Worldwide, GCC, GCC High, and DoD): Rollout begins in early November 2026 (previously early October) and is expected to complete by mid-November 2026 (previously mid-October). [Impact on your organization] Who is affected Users who access or manage resources in Microsoft Teams chats and channels. Platforms and services Microsoft Teams Microsoft Teams mobile What will happen Users will have a centralized location to find, access, and manage important resources. Users will be able to pin frequently used resources directly below the chat or channel header, pin multiple messages alongside other resources, and organize them into folders. On mobile devices, users will be able to access shared resources and folders by tapping the chat or channel header. The In this chat and In this channel panes will be removed; existing resources within these panes will be accessed and managed through the updated experience. Screenshot - Comparison before and after [Action required and recommendations] No administrative action is required. We recommend that you: Inform users about the updated resource pinning and management experience. Update any internal training or support documentation that references the In this chat and In this channel panes. [Learn more] We will update this post with new documentation. [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
(Updated) Microsoft Teams: Granular channel notification settings
MC1388719 · planForChange · normal · Updated 10/19/2026 16:54
Services: Microsoft Teams
Read message
Updated October 19, 2026: We have updated the timeline. Thank you for your patience. [What and why] Users will now be able to control their channel notification settings using three presets: All new messages, Mentions and replies, and Mute. Users can further customize the selected preset to manage notifications for unfollowed threads, tag mentions, channel mentions, and team mentions within each channel, as well as control banner notifications for the channel This gives users more control over what is important in each channel, leading to an improved triaging experience and reduced noise. This message is associated with Microsoft 365 Roadmap ID 565132. [Rollout schedule] General AvailabilityTargeted release: Rollout will begin in early October 2026 (previously late September) and is expected to complete in early October 2026 (previously mid-August). Worldwide: Rollout will begin in early November 2026 (previously early October) and is expected to complete in mid-November 2026 (previously mid-October). GCC and GCC High: Rollout will begin in mid-November 2026 (previously mid-October) and is expected to complete in late November 2026 (previously late October). DoD: Rollout will begin in late November 2026 (previously late October) and is expected to complete by mid-December 2026 (previously mid-November). [Impact on your organization] Who is affected Users in GCC, GCC High, and DoD environments using Microsoft Teams channels Platforms and services Microsoft Teams across desktop, web, and mobile Windows, Mac, iOS, Android What will happen Users will see new preset channel notification options:All new messages Mentions and replies Mute Users can customize each preset to manage:Unfollowed threads Tag mentions Channel mentions Team mentions Existing notification behavior remains unchanged unless users modify their settings. The feature is enabled by default for all users. No changes are required to existing admin settings or policies. [Action required] No action is required. Recommendations: Inform helpdesk teams about this change, as users may have questions about updated notification behavior. Update internal documentation or training materials if you reference Teams notifications. [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
Microsoft Agent 365: Expanded access to Microsoft agent usage and activity insights in Microsoft 365 admin center
MC1506727 · stayInformed · normal · Updated 10/19/2026 16:40
Services: Microsoft 365 suite
Read message
Updated October 19, 2026: We have updated the content. Thank you for your patience. [What and why] Starting in late October 2026, Microsoft is expanding access to Agent 365 usage and activity insights in the Microsoft Admin Center for Microsoft pre-built agents and agents built on Microsoft platforms. This change expands access to the agent overview, active users, advanced usage (activity, sessions, exception rate, run time), regardless of Agent 365 licensing status, regardless of Agent 365 licensing status, giving administrators foundational visibility into agent usage and activity and helping them understand where additional management, governance, and security capabilities may be needed. This change is limited to some management metrics for agents built by Microsoft or built on Microsoft Platforms, not inclusive of agents built on 3rd party platforms. Agent 365 or ME7 licensing continues to provide access to the broader set of Agent 365 management, governance, security, and business value capabilities, enabling organizations to go beyond foundational visibility to more deeply manage and protect their agent environment. [Rollout schedule] General Availability (Worldwide): Beginning in late October 2026 and expected to complete by late November 2026 [Impact on your organization] Who is affected Organizations using supported agents built by Microsoft or built on Microsoft platforms Platforms and services Microsoft 365 admin center Agent 365 management What will happen Administrators will have expanded access to Agent 365 usage and activity insights for supported agents built by Microsoft or on Microsoft platforms, including agent overview, active users, activity, sessions, exception rate, and run time. In Registry, the affected usage and activity columns are Active users, Total sessions, Exception rate, and Run Time. In Agent overview, affected cards and charts include Active users, Active users over time, and Trending agents by active users. These views may already be visible in organizations without an Agent 365 license. Reported values and trends may change temporarily as activity data accumulates during rollout. In Agent details > Activity, affected metrics include the Active users, Sessions, Exceptions, and Agent run-time cards, and the Active users over time and Sessions over time charts. The change applies to both existing and new agents. As this change reaches your organization, some metrics or trends may initially appear incomplete while activity data accumulates. Allow up to 30 days after data collection begins for a full 30-day reporting view. Lower displayed values during this period do not necessarily indicate a decline in agent usage Data availability continues to depend on the agent or platform sending activity data and on applicable observability settings. Existing licensing and access requirements for the full value of observability metrics, including risk-related features will continue to require a paid A365 or ME7 license. Action required and recommendations Review the expanded usage and activity insights in Microsoft 365 admin center to better understand agent usage and activity across your organization. When comparing usage before and after rollout, account for the time required to collect a full reporting window. Lower displayed values during rollout may reflect incomplete activity history rather than a decline in usage. -
Quick machine recovery is now supported on Windows Server 2025
MC1515270 · stayInformed · normal · Updated 10/19/2026 14:21
Services: Windows
Read message
What and why: With the October 2026 Windows security update, Quick machine recovery is now available for Windows Server 2025. Quick machine recovery can help servers recover from critical boot failures by using Windows Recovery Environment (WinRE) to search Windows Update for an applicable remediation. Recovery is dependent on an applicable remediation being available. On Windows Server 2025, quick machine recovery is disabled by default. Administrators can use Group Policy to enable and configure the capability for servers in their environment. Rollout schedule Quick machine recovery is available for Windows Server 2025 editions with the October 2026 security update or later installed. Impact on your organization There is no change to the default recovery behavior for Windows Server 2025 after installing the update because Quick machine recovery is disabled by default. If you choose to enable this feature, you can then use cloud remediation to retrieve and apply targeted remediations through Windows Update when a server encounters a critical boot failure. Administrators can also configure automatic remediation, which allows the server to check for an available cloud-based remediation without user interaction. Action required/recommendations No immediate action is required. If your organization manages Windows Server 2025, we recommend that you: Learn more about Quick machine recovery to understand if this experience is right for your organization. If you choose to enable the capability, review Configure quick machine recovery by using Group Policy. You will find the relevant settings under Computer Configuration > Administrative Templates > System > Quick Machine Recovery. Confirm that applicable servers have a working WinRE configuration and that the recovery environment has the network connectivity required for cloud remediation. Compliance considerations No compliance considerations are identified. Review as appropriate for your organization. -
(Updated) Copilot Notebooks: Suggested artifacts for faster content creation
MC1411727 · planForChange · normal · Updated 10/16/2026 20:34
Services: Microsoft 365 apps
Read message
Updated October 16, 2026: We have updated the timeline. Thank you for your patience. [What and Why:] Copilot Notebooks will intelligently recommend relevant artifacts based on your Microsoft 365 knowledge and the content in your notebook, helping you move work forward faster without leaving the notebook experience. By automatically leveraging existing context and background information, Copilot reduces the need to repeatedly write prompts containing the same details when creating new content from notebook materials. Supported artifact types include Word documents, Excel workbooks, and PowerPoint presentations. Support for additional artifact types, including PDFs and Pages, will be introduced in a future release. This message is associated with Roadmap ID 566870. [Rollout Schedule:] Public Preview (Worldwide): Beginning in early July 2026; expected to complete by late August 2026. General Availability (Worldwide): Beginning in late August 2026; (previously late July) expected to complete by early November 2026 (previously late September). [Impact on Your Organization:] Who is affected: Users who can currently create artifacts within Copilot Notebooks. Organizations licensed for Microsoft 365 Copilot (Premium) with access to Copilot Notebooks. Platforms/Services: Microsoft 365 Copilot Copilot Notebooks Word Excel PowerPoint What will happen: Users will see proactive artifact recommendations within Copilot Notebooks. Suggestions are generated using notebook references, pages, and Microsoft 365 context. Supported artifact types include Word, Excel, and PowerPoint. Future releases are expected to add support for PDFs and Pages. The feature is available by default for eligible users. No admin configuration is required. Screenshot - Copilot Notebooks screen with recommended artifacts [Action Required/Recommendations:] No action is required. We recommend that you: Review user-facing communications regarding Copilot Notebooks. Inform help desk teams about the new recommendation experience. Update internal training and adoption materials as appropriate. Monitor roadmap communications for future artifact type support. [Compliance Considerations:] Compliance considerationExplanation Does the change alter how existing customer data is processed, stored, or accessed?Artifact suggestions are generated using content already available in Copilot Notebooks, including notebook references, pages, and the user's Microsoft 365 context. This introduces additional AI-driven processing of existing customer data to determine relevant artifact recommendations. Does the change introduce or significantly modify AI/ML or agent capabilities that interact with or provide access to customer data?The feature adds proactive AI-generated artifact recommendations that analyze notebook content and Microsoft 365 context to suggest next-step deliverables such as Word documents, Excel workbooks, and PowerPoint presentations. Does the change provide end users any new way of interacting with generative AI?Users can receive contextual artifact recommendations directly within Copilot Notebooks and generate content from pre-populated prompts that incorporate relevant notebook information. Does the change alter how admins can monitor, report on, or demonstrate compliance activities?The announcement does not specify whether recommendation activity will be surfaced in existing audit, reporting, or compliance experiences. Organizations may wish to review future documentation for additional compliance-related details. Does the change include an admin control and can it be controlled through Entra ID group membership?No new administrative controls are described. The feature appears to be available to users who already have permission to create artifacts in Copilot Notebooks, but Microsoft has not explicitly documented control mechanisms. Does the change allow a user to enable and disable the feature themselves?The announcement states that users remain in control of whether they use suggested artifacts, but it does not specify whether the recommendation experience itself can be enabled or disabled by individual users. -
Microsoft Teams: Upcoming change to voicemail message delivery by email
MC1511072 · planForChange · normal · Updated 10/16/2026 20:28
Services: Exchange Online, Microsoft Teams
Read message
[What and why] We’re changing how Microsoft Teams voicemail messages are delivered by email to improve security and give organizations more control over sender identity. Organizations will be able to send voicemail notifications from their own domain and apply existing SPF, DKIM, DMARC, and domain-protection policies to help prevent spoofing and impersonation. Supporting organization-owned sending domains requires a new voicemail email delivery solution. Caller information will move from the email From field to the Subject line and remain in the message body. [Rollout schedule] General Availability (Worldwide): Rollout is currently estimated to begin in early March 2027 and complete by late June 2027.Note: This schedule is subject to change. We will publish an updated Message center communication with the confirmed rollout timeline and required customer actions. [Impact on your organization] Who is affected Organizations that are using Teams Calling. Platforms and services Microsoft Teams Voicemail Exchange Online What will happen The From field in voicemail email messages will no longer contain the caller’s name, phone number, or email address. The sender address will support Bring Your Own Domain (BYOD), allowing organizations to use their own domain for voicemail email delivery. Caller information will move to the Subject line and remain in the message body. Organizations should review and prepare to update mail-flow rules, allowlists, filtering, routing, or automation based on the current voicemail sender identity or domain. Caller information will continue to appear in Teams as it does today, while the underlying email delivery and sender domain will change. ComponentTodayAfter the change E-mail From fieldIdentified caller: John Smith "jsmith@contoso.com" or unidentified caller: "+19371817273" noreply@skype.voicemail.microsoft.com"Microsoft Teams" no-reply@<default tenant domain> or "Microsoft Teams" <custom tenant domain> when configured E-mail Subjectfield (personal voicemail)Voice mail (22 seconds)Identified: John Smith (+19371817273) - Voicemail (00:22) Unidentified: +19371817273 - Voicemail (00:22) E-mail domain“skype.voicemail.microsoft.com” for PSTN calls or tenant owned domain for Teams-to-Teams calls<default tenant domain> or <custom tenant domain> when configured E-mail From field (Call queue shared voicemail)Shared Voicemail (<CQ name>)Teams-to-Teams: John Smith - Shared voicemail in <CQ name> (00:05). PSTN, contact found in Entra: John Smith (+37251223123) - Shared voicemail in <CQ name> (00:05) or contact not found in Entra +3751223123 - Shared voicemail in <CQ name> (00:05) E-mail From field (Auto Attendant shared voicemail)Shared Voicemail (<AA name>)Teams-to-Teams: John Smith - Shared voicemail in <AA name> (00:11). PSTN, contact found in Entra: John Smith (+3725122312) - Shared voicemail in <AA name> (00:11) or contact not found in Entra: +3725122312 - Shared voicemail in <AA name> (00:11) [Action required and recommendations] We recommend that you review any mail-flow rules, allowlists or automation that depend on the current voicemail sender identity or domain and prepare to update them as needed. [Compliance considerations] No compliance concerns or additional compliance requirements have been identified as part of this change. -
Action required: Review property changes for Exchange Online scenarios
MC1511071 · planForChange · normal · Updated 10/16/2026 20:24
Services: Exchange Online
Action required by: 11/15/2026 08:00
Read message
[What and why:] As part of our ongoing Exchange Online management and directory modernization efforts, we're simplifying legacy management scenarios and removing properties. We are deprecating selected properties returned or used with the following Exchange Online PowerShell scenarios: Get-Mailbox -Migration New-Mailbox -Migration If your scripts, applications, or automation use these scenarios, review the affected properties and determine whether your workflows depend on them. The change will be introduced in two phases: Beginning November 15, 2026: Selected properties will no longer be returned in applicable Get-Mailbox -Migration and New-Mailbox -Migration responses. Beginning December 15, 2026: The affected properties will be blocked from being configured through applicable New-Mailbox -Migration scenarios. [Rollout schedule:] We will begin rolling out mid-November 2026 and expect to complete by mid-November 2026. [Impact on your organization:] Your organization may be affected if you have scripts, applications, third-party solutions, or operational workflows that use the affected properties with -Migration scenarios. For example, a script using: Get-Mailbox -Migration will no longer receive the affected properties in the returned object beginning November 10, 2026. This may affect automation that depends on those properties being present or expects a fixed set of properties in the response. If your workflows don't use any of the affected properties, no action is required. [Action required / Recommendations:] Before November 15, 2026: Review scripts, applications, and integrations that use Get-Mailbox -Migration, New-Mailbox -Migration, or Set-Mailbox -Migration. Review the published list of affected properties. Identify whether your workflows depend on any affected property. Update and test affected workflows to remove the dependency. For the complete list of affected properties and additional guidance, see: Changes to Get-Mailbox and New-Mailbox specifically with the Migration parameter | Microsoft Learn. Required Actions Review your -Migration workflows and make any required changes before November 15, 2026. If an affected property is required for your scenario and you can't remove the dependency, contact Microsoft Support and provide the property name, cmdlet, usage scenario, and expected impact. -
Microsoft Copilot Studio – Teams app retirement
MC1511056 · planForChange · normal · Updated 10/16/2026 20:04
Services: Microsoft Teams
Read message
[What and Why:] Microsoft is continuing the transition of Copilot Studio experiences from the Microsoft Teams app to the Copilot Studio web app at https://copilotstudio.microsoft.com/. Users can continue to create, edit, publish, and manage classic-style chatbot agents in the Copilot Studio web app. Agent creation in the Teams app is already no longer supported. Beginning in January 2027, editing agents in the Teams app will no longer be supported. Beginning in February 2027, the Copilot Studio app will no longer be available in Microsoft Teams. [Rollout Schedule:] We will begin rolling out in early January 2027 and expect to complete by early February 2027. [Impact on Your Organization:] Who is affected: Users who currently use the Copilot Studio app in Microsoft Teams to create, edit, publish, or manage classic-style chatbot agents. Admins and support teams who provide guidance for Copilot Studio agent management. Platforms/Services: Microsoft Copilot Studio Microsoft Teams Microsoft 365 Copilot What will happen: Users can continue to manage supported classic-style agents in the Copilot Studio web app. Starting in January 2027, editing existing agents in the Copilot Studio app within Microsoft Teams will no longer be supported. Starting in February 2027, the Copilot Studio app will be removed from Microsoft Teams and will no longer be available. Users should use the Copilot Studio web app for supported agent creation, editing, publishing, and management experiences. [Action Required/Recommendations:] Inform affected users that Copilot Studio agent management should move to the Copilot Studio web app. Update internal documentation, training, and support guidance that references the Copilot Studio app in Microsoft Teams. Review any bookmarks, user communications, or helpdesk scripts that direct users to manage agents from Teams. Direct users to https://copilotstudio.microsoft.com/ for supported Copilot Studio web experiences. [Compliance considerations:] No compliance considerations identified. Review as appropriate for your organization. -
Upcoming changes to Agents in SharePoint and OneDrive
MC1511052 · planForChange · normal · Updated 10/16/2026 19:59
Services: SharePoint Online
Read message
[What and Why:] We are upgrading the agent experience in SharePoint and OneDrive to better align with the Microsoft Copilot extensibility ecosystem, specifically to ensure that these agents are part of Copilot app home experiences (MC1479277) and the Microsoft plugin registry (MC1484008), the shared catalog for discovering, publishing, and governing organization-approved and custom-built plugins across Microsoft Copilot experiences (Chat, Cowork, Code, Autopilot) and Microsoft 365 apps (Word, PowerPoint, Excel), OneDrive and SharePoint. Agents using .agent file format will continue to work across SharePoint, Teams, and Copilot app until the end of March 2027. With upcoming updates, agent owners can start upgrading each experience. The right path depends on what each agent helps users accomplish today: Use Copilot in SharePoint for site-level questions and answers. Convert the .agent file to a skill for Copilot in SharePoint when it supports a focused task or business outcome specific to the site. Upgrade to a declarative agent or update your custom engine agent that was published to the SharePoint channel, when users need a content-grounded, conversational experience across Microsoft 365. Changes to agent creation and building experiences in OneDrive and SharePoint will support this transition: Creating agents will use the Microsoft Copilot Agent Builder An Upgrade button will appear in the SharePoint builder so you can upgrade the agent to use the Microsoft Copilot Agent Builder. A convert-agent-file-to-skill skill will be available in Copilot in SharePoint Changes to the user experience of the site will support this transition: The Agent Chat web part is coming soon to allow any agent from the Plugin store to appear on the SharePoint site with more intention and control for greater reach and impact Copilot in SharePoint is already available worldwide and is coming soon to Government clouds. [Rollout Schedule:] General Availability (Worldwide and Government clouds): This change consists of two rollouts: Agent creation and upgrade: Rollout begins mid-November and is expected to complete by early December 2026 Agents in SharePoint and OneDrive using .agent file format stop working in SharePoint, Teams and Copilot app: Rollout begins early April and is expected to complete mid-April 2027 [Impact on Your Organization:] Who is affected: Organizations using agents in SharePoint and OneDrive. SharePoint site owners and members who create or manage agents in the .agent file format. Admins responsible for agent governance, adoption, licensing, and support. Platforms/Services: SharePoint OneDrive Copilot in SharePoint Microsoft 365 agents Microsoft Copilot Agent Builder Microsoft Plugin store What will happen: Beginning mid-November, users no longer create agents in the .agent file format, and features to support upgrading .agent files will be available. Creating agents will use the Microsoft Copilot Agent Builder and appear in Plugin store. An Upgrade button appears in the SharePoint builder. A convert-agent-file-to-skill skill is available in Copilot in SharePoint Upgraded agents must be re-added to Teams Chat/Channel With Agent Chat web part, site owners/page authors can add any agent from the Plugin store into SharePoint. After March 2027, agents using .agent file format will stop working in SharePoint, Teams and Copilot app; including Agent Link web part, immersive experience, chat pane in SharePoint. [Action Required/Recommendations:] Begin preparing for the transition away from SharePoint and OneDrive .agent files now. Identify the teams that own or manage agents, share the March 2027 deadline, and ensure that site and agent owners understand the upgrade paths. Administrators should become familiar with Copilot in SharePoint, Microsoft Copilot Agent Builder, Agent 365 and the governance and management capabilities that will apply to upgraded experiences. You don’t need to change any .agent file format agents today, but the following changes will help you transition: “Create an agent”/“New agent” in SharePoint/OneDrive open Microsoft Copilot Agent Builder for creation. These agents are added to the Plugin store and will not create .agent files. You can continue to edit existing .agent files during the transition period. When you are ready to upgrade, use the Upgrade to M365 Agent button in the SharePoint agent builder or convert-agent-file-to-skill skill in Copilot in SharePoint. Use the Agent Chat web part to add the agent to a SharePoint page. Review the guidance on finding and upgrading existing agents. [Compliance considerations:] Does the change store new customer data, if so, where, and is the data cached or permanently stored?Yes. Upgraded and new agents managed through the Agent Builder, Plugin store, Agent 365 and Microsoft Admin Center, and may use SharePoint content and site context for conversational experiences. Does the change alter how existing customer data is processed, stored, or accessed?Yes. .agent file experiences transitioning to Agent Builder continue to use SharePoint content and site context with Microsoft 365 integration and centralized controls. Does the change introduce or significantly modify AI/ML or agent capabilities that interact with or provide access to customer data?Upgrade path dependent. No changes for upgrading to Agent Builder. Converting to a skill enables it to be used with the capabilities of Copilot in SharePoint. Does the change alter how admins can monitor, report on, or demonstrate compliance activities?Yes. Agent Builder, Microsoft Admin Center and Agent 365 are the places where governance, management, and usage analysis are available for these new and upgraded agents. Does the change include an admin control and can it be controlled through Entra ID group membership?Yes. Agent 365 provides centralized controls. Review applicable platform controls for your organization. -
Microsoft Outlook for Android: Multi-select and bulk actions in search results
MC1509800 · stayInformed · normal · Updated 10/15/2026 23:10
Services: Exchange Online
Read message
[What and why] We’re introducing multi-select and bulk mail actions in Outlook search results on Android. Users can select multiple email results and take supported actions on those messages in one step, making it faster to organize and manage email found through search. This capability is already available in Outlook for iOS and is now coming to Android. [Rollout schedule] General Availability (Worldwide): We will begin rolling out in mid-October 2026 and expect to complete by late October 2026. [Impact on your organization] Who is affected Outlook for Android users Platforms and services Microsoft Outlook for Android. This capability is already available in Outlook for iOS. What will happen Users can select multiple email results and take supported actions on those messages in one step. Supported actions include organizing, moving, archiving, deleting, or reporting applicable messages. The change reduces the time required to manage several messages found through search. The Android search experience will more closely align with the existing Outlook for iOS experience. [Action required and recommendations] No administrator action is required. We recommend that you: Inform your help desk and users about the new multi-select experience. Update internal Outlook mobile documentation if it includes instructions for managing search results. Encourage users to keep Outlook for Android updated through the Google Play Store. [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
Support for Office LTSC 2021 and additional apps ended on October 13, 2026
MC1509797 · planForChange · high · Updated 10/15/2026 23:09
Services: Microsoft 365 suite, Microsoft 365 apps, Project for the web
Read message
[What and Why:] As previously communicated, support for Office LTSC 2021 ended on October 13, 2026. Microsoft no longer provides security updates, bug fixes, or technical support for this version of Office. Although the applications may continue to function, using unsupported software could expose your organization to potential security and compliance risks, system incompatibilities, and other issues. Support for Visio LTSC 2021, Project LTSC 2021, and several other products also ended on October 13, 2026. Organizations that continue to use these products should transition to a supported version as soon as possible to receive ongoing security updates, bug fixes, and technical support. [Rollout Schedule:] General Availability (Worldwide): Support for Office LTSC 2021, Visio LTSC 2021, Project LTSC 2021, and other affected products ended on October 13, 2026. [Impact on Your Organization:] Devices running Office LTSC 2021 or another affected product no longer receive security updates, bug fixes, or technical assistance. The applications do not automatically stop working, but continued use of unsupported software may increase your organization's exposure to security and compliance risks and could result in compatibility or reliability issues. [Action Required/Recommendations:] Identify any devices in your organization that are still running Office LTSC 2021 or another affected product and move them to a supported solution. For most organizations, we recommend upgrading devices to a Microsoft 365 or Office 365 suite that includes Microsoft 365 Apps for enterprise or Microsoft 365 Apps for business. Microsoft 365 Apps provides always-up-to-date versions of familiar apps like Word, Excel, and PowerPoint for desktop, mobile, and web with continuous support under the Modern Lifecycle Policy, and is eligible for use with Microsoft Copilot. Enterprises should review Microsoft 365 E3, Office 365 E3, or Microsoft 365 Apps for enterprise. Organizations with fewer than 300 users should review Microsoft 365 Business Premium, Microsoft 365 Business Standard, or Microsoft 365 Apps for business. For scenarios that require a fully disconnected solution, we recommend upgrading to Office LTSC 2024. Office LTSC 2024 is Microsoft's current supported on-premises version of Office for commercial customers and is supported until October 2029 under the Fixed Lifecycle Policy. Resources: Read the upgrade guidance for an overview of how to move from Office LTSC 2021 to Microsoft 365 Apps. Consider engaging Microsoft FastTrack, a Microsoft support service, for moving to Microsoft 365. Take action now to help maintain security, compliance, and access to supported Office apps. [Compliance considerations:] QuestionAnswer Does the change modify, interrupt, or disable any Microsoft 365 service capability?Yes. Support for Office LTSC 2021 and other affected products ended on October 13, 2026. Organizations should move to supported versions to receive ongoing updates and support. Does the change require admin action?Yes. Admins should identify affected devices and move them to a supported Microsoft 365 Apps, Office, Visio, or Project version as appropriate. -
Microsoft Edge: Browser-native XSLT will be disabled by default
MC1509789 · planForChange · normal · Updated 10/15/2026 23:04
Services: Microsoft 365 suite
Read message
[What and Why:] Microsoft Edge is deprecating browser-native Extensible Stylesheet Language Transformations (XSLT). Edge will disable the XSLTProcessor JavaScript API and XML processing instructions that reference XSLT stylesheets by default. XML processing instructions that reference CSS stylesheets are not affected. The native XSLT implementation depends on an aging native codebase that processes untrusted XML and XSLT content. Removing this functionality reduces the browser attack surface. XSLT also has low modern web usage, and safer migration alternatives are available. [Rollout Schedule:] General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out in mid-December 2026 and expect to complete by mid-December 2026. [Impact on Your Organization:] Organizations may be affected if internal websites, public websites, embedded-device interfaces, or third-party web applications depend on browser-native XSLT. In Microsoft Edge 159, browser-native XSLT will be off by default in Stable. The temporary XSLTEnabled policy is planned for removal in Microsoft Edge 176 in Summer 2027. [Action Required/Recommendations:] Before Microsoft Edge Stable 159, identify applications that use the XSLTProcessor JavaScript API or XML processing instructions that reference XSL stylesheets. To check for browser-native XSLT usage with Lighthouse in Microsoft Edge: Open the application in a current version of Microsoft Edge. Sign in and navigate to the application page you want to test. Open Edge DevTools with F12 or Ctrl+Shift+I. Select the Lighthouse tool. If it isn't visible, select More tools (+) > Lighthouse. Select:Mode: Navigation Category: Best Practices For authenticated applications: In Lighthouse Settings, turn off Clear storage so the audit preserves your signed-in session. Leave it enabled for public pages that don't require stored application state. Select Analyze page load. In the report:Search for XSLT, deprecated, or XSLTProcessor. Check for Uses deprecated APIs. Expand Issues were logged in the DevTools Issues panel. Check the DevTools Issues and Console tools for XSLT deprecation warnings. Repeat the audit for each relevant page and exercise important application workflows. Migrate affected applications to supported alternatives or contact the developers/vendor responsible for the affected site to update the application and remove its dependency on browser-native XSLT. If more time is needed, configure the temporary XSLTEnabled policy while application owners complete migration. [Compliance considerations:] QuestionAnswer Does the change include an admin control?Yes. Admins can temporarily use the XSLTEnabled policy to manage XSLT behavior while migrating affected applications. Does the change modify or disable a capability?Yes. Browser-native XSLT will be disabled by default and the temporary policy is planned for removal in a future Edge release. -
Intune ending support for Windows MDM-only enrollment CNAME auto-discovery
MC1509780 · planForChange · normal · Updated 10/15/2026 22:54
Services: Microsoft Intune
Action required by: 01/15/2027 08:00
Read message
Starting January 15, 2027, or soon after, Intune will no longer support domain name server (DNS) CNAME-based auto-discovery for Windows MDM-only enrollment scenarios. Enrollments managed through Microsoft Entra ID or other identity platforms are not affected by this change. Organizations that currently rely on an EnterpriseEnrollment DNS CNAME record for Windows MDM-only enrollment will need users to provide the Microsoft enrollment server URL when prompted. For more information, review the blog: Preparing for end of support for CNAME auto-discovery in Windows MDM-only enrollment [How this will affect your organization:] This change only affects organizations that use Windows MDM-only enrollment and rely on DNS CNAME auto-discovery to locate the enrollment service. After this change: Automatic discovery through EnterpriseEnrollment CNAME records will no longer be supported for Windows MDM-only enrollment. Users will need to enter the Microsoft enrollment server URL during enrollment if it is not already provided by the enrollment experience: https://enrollment.manage.microsoft.com/enrollmentserver/discovery.svc Existing enrolled devices are not affected. Windows MDM-only enrollment remains supported. Only CNAME-based auto-discovery is affected. [What you need to do to prepare:] If your organization uses Windows MDM-only enrollment with CNAME auto-discovery, review and update your enrollment guidance, documentation, provisioning instructions, or help desk procedures before this change. For more details, review the blog: Preparing for end of support for CNAME auto-discovery in Windows MDM-only enrollment -
(Updated) Microsoft Teams Rooms: Identify in-room participants with IntelliFrame people labels
MC1419798 · planForChange · normal · Updated 10/15/2026 22:03
Services: Microsoft Teams
Read message
Updated October 15, 2026: We have updated the timeline. Thank you for your patience. [What and Why:] We're introducing IntelliFrame people labels in Microsoft Teams Rooms on Windows to improve meeting clarity and inclusivity for remote participants. When enabled, this feature identifies in-room participants by name and displays a contact card, helping remote attendees easily recognize speakers and follow conversations. This enhancement supports better hybrid meeting experiences by connecting in-room and remote participants more effectively, improving collaboration and productivity. This message is associated with Microsoft 365 Roadmap ID 566700. [Rollout Schedule:] General Availability (Worldwide, GCC): Beginning late January 2027 (previously mid-November 2026) expected to complete by early February 2027 (previously mid-December 2026) [Impact on Your Organization:] Who is affected: Organizations using Microsoft Teams Rooms on Windows with Teams Rooms Pro licenses In-room participants who have enrolled in voice and face recognition (People Recognition) Platforms/Services: Microsoft Teams Teams Rooms on Windows devices Supported intelligent camera hardware What will happen: IntelliFrame will display name labels under identified in-room participants’ video feeds. Remote participants can select a label to view a contact card with organizational details. The feature is enabled automatically when prerequisites are met. Existing Teams meeting policies for voice and face enrollment are honored. Participants without enrolled profiles will appear without labels. No change occurs if voice and face enrollment is disabled in your organization. Screenshot - IntelliFrame people labels identify enrolled in-room participants by name, helping remote attendees recognize who's speaking; selecting a label opens the person's contact card [Action Required/Recommendations:] No action is required to enable this feature. To maximize value, administrators may: Review and confirm Teams Rooms devices:Ensure devices are licensed with Teams Rooms Pro. Verify use of supported intelligent cameras. Review and update meeting policies:Allow enrollment: Set-CsTeamsMeetingPolicy -EnrollUserOverride Enabled. Enable name display in rooms: Set-CsTeamsMeetingPolicy -RoomPeopleNameUserOverride On. Encourage users to enroll in voice and face recognition: Teams > Settings > Recognition. Update internal documentation and helpdesk guidance. Notify users about this capability to drive awareness and adoption. To disable IntelliFrame people labels, administrators can: Turn off in-room name display (labels stop; other IntelliFrame framing unaffected): Set-CsTeamsMeetingPolicy -RoomPeopleNameUserOverride Off Block voice and face enrollment entirely (no one can be identified by name): Set-CsTeamsMeetingPolicy -EnrollUserOverride Disabled Individual users can opt out anytime by removing their profile in Teams > Settings > Recognition. Learn more: What is Microsoft Multi-Stream IntelliFrame and Intelligent Camera? | Microsoft Learn (will be updated before rollout) Enable People Recognition on Teams Rooms (voice & face policies) | Microsoft Learn (will be updated before rollout) Overview and configuration of voice and face enrollment | Microsoft Learn (will be updated before rollout) [Compliance considerations:] Compliance AreaImpact Introduces or modifies AI/ML capabilitiesUses AI-based biometric identification (voice and face profiles) to identify in-room participants. Identification occurs only for users who have consented and completed People Recognition enrollment. Stores new customer dataThis feature does not create new data; it relies on existing voice and face profiles from People Recognition enrollment, governed by the organization’s current configuration. Alters processing of existing customer dataParticipant identity data is processed differently when recognition is enabled. Provides new way of communicating between usersLabels and contact cards enhance visibility of in-room participants for remote users. Adds or changes admin controlsControlled via Teams meeting policies (EnrollUserOverride and RoomPeopleNameUserOverride). Allows users to enable/disable the featureUsers can enroll or opt out of voice and face profiles in Teams settings. -
(Updated) Microsoft Planner: Capacity view
MC1474110 · stayInformed · normal · Updated 10/15/2026 19:21
Services: Planner
Read message
Updated October 15, 2026: We have updated the timeline. Thank you for your patience. [What and why] Capacity view is a new view in Planner that presents a live staffing matrix built from existing Planner task data. It shows a timeline of who is working on what, so team leads can see how work is distributed across the team and spot overallocation or open capacity at a glance, without exporting data or building a separate report. This keeps resource decisions in the same tool where the work is already tracked. [Rollout schedule] Targeted Release: Beginning in late October 2026 (previously early October) and expected to complete late October 2026 (previously mid-October) General availability (Worldwide): Beginning in late October 2026 (previously mid-October) and expected to complete by early November 2026 (previously late October) [Impact on your organization] Who is affected Users with a Planner Plan 3 license in Worldwide (Standard Multi-Tenant) environments Users without a Plan 3 license will not see Capacity view Platforms and services Planner in Teams (web and desktop) Planner in Outlook (web and desktop) Capacity view is not included on mobile What will happen Capacity view appears as a new view on existing plans, alongside Board, Grid, and Schedule. The view is populated entirely from existing Planner task data. No new data is created. Accuracy depends on tasks having assignees and start and finish dates. Tasks missing either will not be represented reliably in the timeline. The view is on by default for eligible users and there is no admin control to disable it. [Action required and recommendations] No admin action is required to enable or prepare for this change. To get value from the view, consider the following: Notify Planner users that a new Capacity view will appear on their plans in early October 2026. Update internal training material and Planner guidance to include the new view. Encourage plan owners and team leads to keep assignees and start and finish dates current so the view reflects actual workload. [Compliance considerations] No compliance considerations identified, review as appropriate for your organization. -
(Updated) Microsoft Planner: Planner Agent chat in basic plans
MC1443514 · stayInformed · normal · Updated 10/15/2026 19:17
Services: Planner
Read message
Updated October 15, 2026: We have updated the timeline. Thank you for your patience. [What and why] Planner Agent chat is coming to Microsoft Planner basic plans. This feature brings Planner Agent directly into the Planner experience, allowing users to ask questions about their plans, understand priorities, and take action without leaving Planner. Planner Agent chat helps users stay organized by providing quick access to plan status, work that requires attention, and actionable insights. It can also help users create and manage plans using information from Microsoft 365 resources. This message is associated with Microsoft 365 Roadmap ID 567671. [Rollout schedule] Targeted Release: Beginning in early September 2026 (previously late August) and expected to complete by mid-September 2026 (previously early September) General Availability (Worldwide): Beginning in mid-September 2026 (previously late August) and expected to complete by end of October 2026 (previously late September) [Impact on your organization] Who is affected Users with an active Microsoft 365 Copilot license Organizations that allow access to Planner Agent Platforms and services Microsoft Planner Microsoft 365 Copilot Web What will happen Eligible users will be able to access Planner Agent chat directly within Planner while working in basic plans. Users will be able to: Ask questions about plan status, priorities, and upcoming work. Apply AI-generated filters to identify important work more quickly. Use interactive task cards to draft updates, review tasks, and track progress. Receive insights about high-priority work, upcoming deadlines, and at-risk tasks. Create new Planner plans organized by goals and buckets. Use information from Microsoft 365 resources such as emails, meetings, and files when working with Planner Agent. Use natural language prompts such as: "Show me my recent high-priority tasks and what is due this week." [Action required and recommendations] Review whether your organization wants users to have access to Planner Agent. Confirm that users who should use this feature have an active Microsoft 365 Copilot license. Review Planner Agent settings in the Microsoft 365 admin center. If Planner Agent is blocked, users will not have access to this capability. Update internal documentation and user guidance as appropriate. No additional action is required before rollout. Learn more Chat with Planner Agent in basic plans | Microsoft Support Manage agents in the Microsoft 365 admin center | Microsoft 365 admin center | Microsoft 365 | Microsoft Learn [Compliance considerations] QuestionAnswer Does this change introduce or significantly modify AI, machine learning, or agent capabilities that interact with customer data?Yes. This feature introduces Planner Agent chat, an AI-powered experience that interacts with Planner data and can use existing Microsoft 365 resources, including emails, meetings, and files, to provide insights, answer questions, and help users take action. Does this change provide end users with a new way to interact with generative AI?Yes. Users can interact with Planner Agent chat using natural language prompts to analyze plans, identify priorities, create plans, manage tasks, and receive AI-generated insights directly within Planner. Does this change alter how existing customer data is accessed or processed?Yes. Planner Agent chat can access and process existing Planner data and Microsoft 365 content that users already have permission to access in order to generate responses, recommendations, and insights. Is there an administrative control available for this feature?Yes. Administrators can control access to this capability through agent settings. Blocking the Planner Agent removes access to the feature. Can this feature be enabled or disabled by administrators?Yes. Administrators can manage availability of the feature through Planner Agent configuration and access controls. Does this change affect how users access information within Microsoft 365?Yes. Users gain a new conversational interface that enables them to access and interact with Planner information and related Microsoft 365 content through natural language requests. -
(Updated) Viva Engage: Agents in Viva Engage communities Public Preview
MC1155311 · planForChange · normal · Updated 10/15/2026 17:39
Services: Microsoft Viva
Read message
Updated October 15, 2026: We have refreshed the public preview details, knowledge-source configuration, and analytics information. The general availability date will be announced in a future update. We apologize for any inconvenience. [Introduction] Agent in Viva Engage communities are now available in Public Preview. Community admins can add agents to communities to help draft answers to questions without best or verified answers based on community content and add context to posts by answering follow up questions using the community's conversations and SharePoint site and library. We’re now adding the option for community admins to specify additional SharePoint sites outside the community as grounding sources. The agent will only use sites that community admins select, and it drafts answers from items that community members can view (Read). We are also adding a new capability: tagging by community members. Tagging by community members enables Microsoft 365 copilot-licensed users to @-mention the community agent in the comments and replies of threads with follow up questions and requests to add context to posts. When tagged, the community agent will reply in the post. Tagging by community members will be enabled by default, but can be disabled by community admins in the agent settings. Public preview updates Community Agent public preview now includes: Community and network analytics: Community admins can view question coverage, answers generated and posted, review time, people helped, and estimated time saved. Network admins can view agent activity across communities, including agent status and posting mode. Time-period filters help admins understand activity over time. Additional knowledge sources: Community admins can add public websites and enable content from other public communities in their Engage network. Admins can also turn on Only use expert and verified content to limit the community conversations used to best answers, verified answers, and content written or created by community admins and experts. [When this will happen:] Community Agent remains available in public preview. The general availability date will be announced in a future update. At general availability, a new network-wide Community Agent setting will replace the public preview toggle. We’ll provide at least 30 days’ notice and make the new setting available at the start of that notice period, so admins can set their network’s preference before general availability. Before general availability, review the new network-wide Community Agent setting when it becomes available and set your network’s preference. [How this affects your organization:]Who is affected: Viva Engage community admins and members with Microsoft 365 Copilot licenses; Global and Engage admins managing Viva Engage networks What will happen: During Public Preview:Admins can opt their network into the preview via the Engage admin center: Engage admin center > Tenant Settings > Enable Community Agent Public Preview. Once enabled, admins can add agents to any community they manage. Figure i. Add agent to community The agent will proactively draft answers to unanswered questions using past conversations. By default, the agent posts answers automatically. Admins can configure whether the agent posts answers automatically or only after approval and if tagging by community members is enabled. Figure ii. Configure the agent's capabilities and knowledge sources [Grounding on SharePoint sites outside the community] Community admins can add SharePoint sites and libraries outside the community as additional grounding sources (for sites/libraries they administer). When an admin adds a site or library, they’ll be prompted to grant the community’s Microsoft 365 group Read access if it doesn’t already have permission. The agent only drafts answers using content that all community members can view (Read). By default, the agent uses the community’s SharePoint site and library. Any sites outside the community are optional and add to (not replace) the default grounding. If Require review is enabled, admins and designated experts will be notified when the agent drafts an answer. They can approve, edit, or dismiss the response. Figure iii. Community admins and experts can review agent suggestions If tagging by community members is enabled, then community members can @-mention the agent in messages. Coming soon (General Availability): The agent will only use content that all community members can access. Admins must be owners of the SharePoint sites they wish to configure. Admins can add additional SharePoint sites to expand the agent’s grounding knowledge. The agent will be grounded by default on the community’s SharePoint site. Community members can tag the community agent in community posts. All Microsoft 365 Copilot licensed users will have access to the Community Agent by default. The Community Agent Public Preview toggle will be retired. [What you can do to prepare:] If participating in preview: Opt your network into the preview via the Engage admin center Communicate this change to helpdesk staff. Update internal documentation that references Viva Engage Community Agent behavior or setup. No action is required at GA; the feature will be on by default. Learn more: Set up and manage agents in Viva Engage communities | Microsoft Learn [Compliance considerations:] ConsiderationExplanation Uses customer dataThe agent accesses SharePoint content to generate answers. Only content accessible to all community members is used. Introduces AI/ML agent capabilitiesThe agent uses generative AI to draft responses based on SharePoint content. Admin control available(Optional) Community admins can configure which SharePoint sites are used for grounding. Admin must be site owner. User interaction with generative AIEnd users receive AI-generated answers grounded in community conversations and SharePoint content Can be controlled through Entra ID group membershipAdmin access and site ownership can be managed via Entra ID group membership. -
(Updated) Calls popout into a new window on the browser to support multi-tasking and collaboration during a meeting
MC1462921 · planForChange · normal · Updated 10/15/2026 17:27
Services: Microsoft Teams
Read message
Updated October 15, 2026: We have updated the content. Thank you for your patience. [What and Why:] We are introducing a new Call Monitor experience in Microsoft Teams for Web that helps users stay connected to meetings while working in other browser tabs. When users move away from an active meeting tab, Teams can display key meeting controls in a separate Picture-in-Picture (PiP) window, making it easier to manage calls and meetings without returning to the meeting tab. This enhancement improves multitasking during meetings and helps users remain engaged while working elsewhere in their browser. [Rollout Schedule:] Targeted Release (Worldwide): Rollout will begin in mid-October 2026 (previously early October) and is expected to complete by mid-October 2026 (previously early October). General Availability (Worldwide): Rollout will begin in mid-October 2026 (previously early October) and is expected to complete by late October 2026. [Impact on Your Organization:] Who is affected: Users of Microsoft Teams for Web who join meetings in supported browsers. Platforms: Teams for Web. Supported browsers include Microsoft Edge and Google Chrome. What will happen: Users will receive the new Picture-in-Picture (PiP) Call Monitor experience during Teams meetings. When users navigate away from the active meeting tab, Teams can display meeting controls in a separate PiP window. The PiP Call Monitor helps users remain connected to meetings while working elsewhere in their browser. The experience is available only in browsers that support the required browser capabilities. No changes are required to existing meeting or calling workflows. [Action Required / Recommendations:] No admin action is required before rollout. Ensure helpdesk and support staff are aware of the upcoming user experience change. Review internal training and support materials as needed. Confirm that users are running supported browser versions for Teams for Web. Review Teams for Web prerequisites and supported browsers in Microsoft Learn. [Compliance Considerations:] No compliance considerations identified, review as appropriate for your organization. -
(Updated) Microsoft Teams: Improved file sharing experience in external chats
MC1479514 · planForChange · normal · Updated 10/15/2026 17:07
Services: Microsoft Teams
Read message
Updated October 15, 2026: We are still finalizing rollout dates. Please update your settings by the first week of November to avoid any interruption. We will announce via Message center when we are ready to proceed. We apologize for the inconvenience. [What and why] We’re improving the file-sharing experience in Microsoft Teams external (federated) chats by making the Attach file (paperclip) and drag-and-drop experiences available by default. This change only impacts tenants who have not adjusted the policy that controls file attachment in an external Teams chat. To opt out of this change, disable the capability using the Teams PowerShell setting provided in the “Action required and recommendations” section below. This can be done before the rollout and your policy setting will be respected. This update does not change your OneDrive or SharePoint external-sharing settings or override existing access restrictions. Prior to this change, when existing OneDrive and SharePoint policies allow, users can already share files in external chats by sharing a link to the file. This update makes that flow easier by adding the Attach file (paperclip) and drag-and-drop experiences directly in Teams. Files uploaded from the user’s device are stored in the sender’s OneDrive, while cloud files remain stored in their existing location. Teams then assigns permissions to chat participants, subject to existing OneDrive and SharePoint sharing policies. Senders can still review, modify, or remove file access before sending the message. This reduces the need to assign permissions manually, while allowing senders to stay in control. More info: Share files and Loop in external chats - Microsoft Teams | Microsoft Learn [Rollout schedule] Targeted Release: We will announce via Message center when we are ready to proceed. General Availability (Worldwide, GCC, GCC High, DoD): We will announce via Message center when we are ready to proceed. [Impact on your organization] Who is affected Organizations using Microsoft Teams external access (federation) This change applies only to organizations where the setting has not been explicitly configured. Any customers who have left the configuration in the default state will be impacted. Users participating in external 1:1 chats, external group chats, and meeting chats Platforms and services Microsoft Teams External (federated) 1:1 chats External (federated) group chats Meeting chats Teams desktop app Teams web app What will happen The ability for users to attach and share files in external chats will be enabled for all Microsoft 365 tenants, unless your organization has previously explicitly disabled this setting in Teams. Any customers who have left the configuration in the default state will be impacted. Users can already paste file links into external chants. This ability is unchanged. With this change, users will also have the ability to attach and share files using the paperclip option or drag and drop in external (federated) chats. Files shared through these experiences continue to be stored and shared through OneDrive or SharePoint. Files uploaded from a user’s device are stored in the sender’s OneDrive, while existing cloud files remain in their current location. When automatic permission assignment is enabled, Teams assigns permissions to participants in the external chat for files uploaded using paperclip or drag-and-drop, subject to existing OneDrive and SharePoint policies. Senders can review, modify, or remove sharing permissions before sending a file. Senders can continue to modify or revoke access after a file has been shared. Automatic permission assignment applies only to files shared through the paperclip or drag-and-drop experience. The files will be shared as hyperlinks after send. Existing OneDrive and SharePoint sharing controls continue to govern access. Existing sensitivity labels, domain restrictions, and security protections continue to apply. [Action required and recommendations] No action is required to preserve external-sharing restrictions already configured in OneDrive and SharePoint; this update does not change those restrictions. To review or change these controls, see Manage sharing settings for SharePoint and OneDrive in Microsoft 365. [To disable file attachments in external chats] To opt out of this change, apply the following Teams PowerShell setting if you have not already explicitly configured this setting: Set-CsTeamsFilesPolicy -Identity Global -FileSharingInChatsWithExternalUsers Disabled Verify the setting: Get-CsTeamsFilesPolicy | Select Identity, FileSharingInChatsWithExternalUsers Recommended actions: Review your SharePoint, OneDrive, and Microsoft Entra external sharing configuration because these settings continue to govern what external recipients can access. Inform helpdesk and support teams about the updated attachment experience and the distinction between Teams attachment controls and OneDrive/SharePoint access controls. Update user training and internal documentation as needed. Communicate to users that:They can attach files directly in chats with people outside the organization. When automatic permission assignment is enabled, Teams assigns chat participants access to files shared via paperclip icon, subject to existing OneDrive and SharePoint policies. Senders can review, modify, or remove access before sending. Pasted file links retain their existing permissions. Files uploaded to external chats are stored in the sender's OneDrive and display. Optional configuration to allow attachments without automatic permission assignment: To disable automatic permission assignment while continuing to allow file attachments in external chats: Set-CsTeamsMessagingPolicy -Identity Global -AutoShareFilesInExternalChats Disabled If automatic permission assignment is disabled, users may need to manually grant access to shared files before external recipients can open them. Allow several hours for policy changes to propagate before users see the updated experience. Learn more: Share files and Loop in external chats - Microsoft Teams | Microsoft Learn [Compliance considerations] QuestionAnswer Does the change alter how existing customer data is processed, stored, or accessed?Yes. Uploaded files shared through Attach or drag-and-drop can automatically receive permissions for participants in external chats. Existing OneDrive and SharePoint controls continue to govern access. Uploaded files are stored in the sender’s OneDrive. Does the change provide a new way of communicating between users, tenants, or subscriptions?Yes. The direct file-attachment experience in external (federated) chats becomes available by default; the existing ability to paste file links remains unchanged. Does the change include an admin control, and can it be controlled through Entra ID group membership?Yes. Admins can separately control Teams file attachments and automatic permission assignment through Teams PowerShell policies. OneDrive and SharePoint sharing settings continue to govern external file access. -
App-V server support extended through October 9, 2029
MC1509128 · stayInformed · normal · Updated 10/15/2026 17:00
Services: Windows
Read message
What and why: Microsoft is returning Application Virtualization (App-V) server to extended support (as part of the Fixed Lifecycle policy) for an additional three years, through October 9, 2029. This extension gives your organization additional time to continue operating your existing App-V server deployments while evaluating a longer-term application delivery strategy. The long-term plan is to adopt Azure Virtual Desktop App Attach and migrate to the modern Windows app packaging format, MSIX. Rollout schedule: April 2026: App-V server originally reached end of support. October 2026: App-V server remains in fixed extended support. October 9, 2029: App-V server extended support will end. Impact on your organization: Only App-V server remains in extended support. App-V client and sequencer follow the lifecycle of their corresponding Windows version. Action required/recommendations: Since App-V server is no longer in active development, start migrating toward supported alternatives. Learn more in App-V server support extended through October 9, 2029 and App-V in Windows support policy. Compliance considerations: No compliance considerations are identified. Review as appropriate for your organization. -
(Updated) Microsoft Copilot Analytics: Data export public preview for Copilot metrics in the Copilot dashboard
MC1173208 · stayInformed · normal · Updated 10/15/2026 16:41
Services: Microsoft Viva
Read message
Updated October 15, 2026: We have updated the timeline. This post has also been updated to remind customers that this feature is default-on for Copilot Dashboard users with full company-level data access. The export output remains de-identified, with each user represented by a hashed ID. Please review and take any actions as appropriate for your organization. Thank you for your patience. This MC post is associated with Roadmap ID 500872. [Introduction:] To support deeper analysis of Copilot adoption, Microsoft is introducing a new export capability in the Copilot Dashboard. This feature allows dashboard users with company-level access to download de-identified Copilot usage metrics, aggregated by user and week, from the past six months. Organizations can use this data to track adoption trends, optimize licensing, and support AI transformation strategies. This feature requires at least 50 Microsoft 365 Copilot licenses and applies to the Viva Insights web app. [When this will happen:] Public Preview: Begins in early October 2026 (previously early December 2025), completes by late October 2026 (previously late December 2025). General Availability (Worldwide): Begins in mid-November 2026 (previously mid-October), completes by end of November 2026 (previously end of October). [How this affects your organization:] Who is affected: Copilot Dashboard users with full company-level data access, including senior leaders (as identified in Entra ID), admin-assigned company-level users, delegates with company-level access, as well as global analysts and admins. Note: Group managers with data access limited to their own teams will not have access to this feature. What will happen: Users will be able to export de-identified, row-level Copilot usage metrics from the dashboard. The dataset includes weekly, user-level metrics from the past six months. The export supports Copilot usage analysis across apps (such as Word, Excel, Teams), and includes two attributes: Organization, and Job function. Organizations can use the data to track usage patterns, generate insights to inform adoption strategies, optimize licensing, and measure ROI. The feature is enabled by default for eligible users. Admins can manage access via Viva Feature Access Management (VFAM) settings, under Module: Viva Insights; Feature: Copilot Metrics Export. No impact to user workflow unless accessed by eligible users. Screenshot 1 - View of the new Microsoft Copilot dashboard: Screenshot 2 - Example of output: [What you can do to prepare:] Review the assignment of the Copilot dashboard users with full company-wide data access and adjust VFAM policies as needed. Communicate the upcoming feature to eligible users so they know what to expect. No admin setup is required to start using the export. Admins can disable the feature at the tenant or group level at any time using VFAM settings. Learn more: Microsoft Viva Feature access management | Microsoft Learn Connect to the Microsoft Copilot Dashboard for Microsoft 365 customers | Microsoft Learn [Compliance considerations:] No compliance considerations identified, review as appropriate for your organization. -
Take action: NTLMv1 hardening changes might affect network connections on devices without Credential Guard
MC1508562 · planForChange · normal · Updated 10/15/2026 06:55
Services: Windows
Read message
Beginning with the October 2026 security update, Windows 11, versions 26H2, 25H2, and 24H2, along with Windows Server 2025 enforce restrictions on generating NTLMv1-derived credentials for Single Sign-On by default. This planned security-hardening change is part of the boarder Microsoft effort to phase out NTLM. Microsoft originally documented the change in August 2025. This change applies only on devices with Credential Guard disabled, and might cause issues with Wi-Fi, Ethernet, and VPN connections that use MS-CHAPv2 authentication, resulting in possible failure to connect via Single Sign-On pathways. Windows uses a registry configuration to control whether requests for NTLMv1-derived credentials are audited or blocked. The configuration includes a registry key named BlockNtlmv1SSO. Beginning with the October 2026 security update, Windows uses Enforce mode as the internal default behavior instead of Audit mode, if the registry key BlockNtlmv1SSO has not been previously configured. If the registry key BlockNtlmv1SSO has not been previously configured. Please note this is a planned change in Windows which supports evolving security needs. It is not a known issue with the October 2026 security update. To learn about changes to NTLMv1 in Windows, see KB5066470. Rollout schedule Microsoft enabled auditing of NTLMv1-derived credential use on Windows 11, version 24H2 and later versions, starting in late August 2025. The rollout to Windows Server 2025 began in November 2025. Beginning with the October 2026 security update, the default system behavior changes from audit of NTLMv1 connections to enforcing security by restricting NTLMv1 connections. This default change applies only when administrators have not already configured the BlockNtlmv1SSO registry value on the device. Impact on your organization Devices running Windows 11, version 24H2 and later versions, or Windows Server 2025, might be affected when Credential Guard is disabled and network authentication depends on NTLMv1-derived credentials. In Enforce mode, Windows blocks requests to generate NTLMv1-derived credentials. Wi-Fi, Ethernet, and VPN connections that use MS-CHAPv2 authentication, including PEAP-MSCHAPv2 and EAP-MSCHAPv2, for Single Sign-On might consequently fail to connect automatically. Manually entering credentials can continue to work, but credentials cannot be saved for future use in these scenarios. As a result, workflows that previously established connections without user interaction might no longer function as expected. Devices with Credential Guard enabled already block the affected NTLMv1-derived Single Sign-On behavior and are not subject to the October 2026 default change. Action required/recommendations Organizations should identify affected authentication configurations and select one of the following approaches: Recommended: Remove dependencies on MS-CHAPv2. Migrate Wi-Fi and VPN connections from MS-CHAPv2-based authentication, such as PEAP-MSCHAPv2 and EAP-MSCHAPv2, to certificate-based authentication, such as PEAP-TLS or EAP-TLS. MS-CHAPv2-based endpoints are subject to risks similar to those affecting NTLMv1. Temporary compatibility option: Return affected devices to Audit mode. Open the Windows registry and navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0.Here, create or configure the BlockNtlmv1SSO value as type REG_DWORD and set its data to 0. Windows will audit requests for NTLMv1-derived credentials and allow them to succeed, temporarily restoring compatibility. Note that warning Event ID 4024 will appear in the Microsoft-Windows-NTLM/Operational log, allowing the audit of connection events. Guidance in KB5066470 can be used to identify and remove remaining dependencies on NTLMv1-derived credentials. After removing these dependencies, return to the Enforce mode by setting BlockNtlmv1SSO to 1. Windows then blocks affected requests and records error Event ID 4025. As this change affects the security level of the device, it should be evaluated carefully and not used long-term. Carefully review KB5066470 for complete rollout, auditing, and registry configuration guidance. Compliance considerations Organizations that temporarily use Audit mode should assess the continued generation of NTLMv1-derived credentials against their security and compliance requirements. Organizations should document the exception, limit its duration, monitor Event ID 4024, and establish a plan to return affected devices to Enforce mode. Additional information: KB5066470 is the source for important rollout, auditing, and registry configuration guidance Advancing Windows security: Disabling NTLM by default - Windows IT Pro Blog Retiring NTLM: Frequently asked questions - Windows IT Pro Blog The Wi-fi and VPN considerations section of Considerations and known issues when using Credential Guard -
Microsoft Excel: Changes to Get Data from Web (Legacy) experience
MC1508229 · planForChange · normal · Updated 10/14/2026 23:11
Services: Microsoft 365 apps
Read message
[What and Why:] To import data from the web with Power Query, use the newer Get Data from Web experience. The existing Get Data from Web (Legacy) functionality will be reduced. The newer experience provides modern authentication, table detection, data transformation, and refresh capabilities. Existing queries that use the legacy experience will continue to refresh. [Rollout Schedule:] General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out in mid-January 2027 and expect to complete by early April 2027. [Impact on Your Organization:] After this change: Users will no longer be able to create new legacy web queries with the dialog accessed through Get Data > Legacy Wizards > From Web (Legacy) or edit existing ones. Existing legacy web queries in workbooks will continue to refresh, and users can continue to edit refresh properties through Queries & Connections > Properties > Refresh control UI. Programmatic attempts to open the legacy New Web Query dialog will return an error. Programmatic attempts to create legacy Web Query connections will continue to work. Creating legacy Web Query connections through an .iqy file will continue to work. Other legacy data import wizards are not affected by this change. [Action Required/Recommendations:] You may want to update internal training and documentation because users will receive this change automatically as it progresses through deployment rings. Consider migrating web queries to the newer Get Data from Web experience: Right-click the section of imported data that you want to migrate. Select Edit query. Copy the URL from the address bar. From the Data tab, select From Web in the Get & Transform Data section. Paste the URL into the address bar and follow the steps to create the new web query. [Compliance considerations:] No compliance considerations identified. Review as appropriate for your organization. -
90-Day Reminder: Windows 10 Enterprise LTSC 2021 will reach end of updates on January 12, 2027
MC1507706 · stayInformed · normal · Updated 10/14/2026 17:01
Services: Windows
Read message
On January 12, 2027, Windows 10 Enterprise LTSC 2021 will reach end of updates. The January 2027 Windows security update will be the last update available for this version. After this date, devices running Windows 10 Enterprise LTSC 2021 will no longer receive monthly security updates containing protections from the latest security threats. To help keep your devices protected and supported, we recommend updating to the latest Long-Term Servicing Channel release, Windows 11 Enterprise LTSC 2024. If your organization cannot complete its transition before January 12, 2027, Extended Security Updates (ESU) options are available to help keep eligible devices protected while you complete your transition. Learn more at Plan for Windows 10 Enterprise LTSC 2021 end of support. For detailed lifecycle dates, see the Windows 10 Enterprise LTSC 2021 lifecycle page. For servicing and lifecycle resources, see Windows 10 release information, Lifecycle FAQ - Windows, and the Microsoft Lifecycle Policy search tool. -
90-Day Reminder: Windows Server 2016 will reach end of updates on January 12, 2027
MC1507705 · stayInformed · normal · Updated 10/14/2026 17:00
Services: Windows
Read message
On January 12, 2027, Windows Server 2016 will reach end of updates. The January 2027 Windows security update will be the last update available for this version. After this date, devices running Windows Server 2016 will no longer receive monthly security updates containing protections from the latest security threats. This end of updates in 2027 applies to all editions of Windows Server 2016: Datacenter, Essentials, MultiPoint Premium and Standard. Also, note that Microsoft support for Windows Server 2016 Essentials features, including Remote Web Access and related Essentials-specific functionality, ends on the same date. Any Windows Server 2016 Essentials capability that continues to function after end of support should be treated as unsupported. To help keep your environment protected and supported, plan to upgrade to Windows Server 2025. To download a free 180-day evaluation, visit the Microsoft Evaluation Center. Extended Security Updates (ESU) are available for Windows Server 2016 Standard and Datacenter editions for organizations that need additional time to complete their transition. For detailed lifecycle dates, see the Windows Server 2016 lifecycle page. For servicing timelines and related resources, see Windows Server release information, Lifecycle FAQ - Windows Server, and the Microsoft Lifecycle Policy search tool. -
Windows Server 2022 has reached end of mainstream support
MC1507704 · stayInformed · normal · Updated 10/14/2026 17:00
Services: Windows
Read message
As of October 13, 2026, Windows Server 2022 has reached end of mainstream support and transitioned to extended support. The October 2026 security update is the last mainstream support update available for this version. Extended support includes security updates at no additional cost, and Windows Server 2022 will continue to receive monthly security updates through October 14, 2031. For more information, see the Fixed Lifecycle Policy. Hotpatch update support for Windows Server 2022 Datacenter: Azure Edition has been extended through October 2027. Devices enrolled in hotpatch updates will continue to receive monthly security updates without requiring a restart. To learn more, see the Windows Server 2022 lifecycle page. Windows Server 2025 is the latest Long-Term Servicing Channel (LTSC) release for Windows Server. To help keep your environment protected and supported, plan your upgrade path to Windows Server 2025 for full mainstream support. To download a free 180-day evaluation, visit the Microsoft Evaluation Center. For detailed lifecycle dates, see the Windows Server 2022 lifecycle page. For servicing timelines and related resources, see Windows Server release information, Lifecycle FAQ - Windows Server, and Microsoft Lifecycle Policy search tool. -
(Updated) The October 2026 Scan Cab is available
MC1507520 · stayInformed · normal · Updated 10/14/2026 14:42
Services: Windows
Read message
(Updated October 14, 2026: The availability time in this message was updated.) IMPORTANT: This notice only affects environments where Scan Cab is used to check for update compliance. What and why: The October 2026 Scan Cab was made available at 3:30 AM PT today, October 14, 2026. The Scan Cab can help determine whether a Windows device needs to install necessary security updates released by Microsoft without first connecting to the Windows Update service. Rollout schedule: The October 2026 Scan Cab was made available at 3:30 AM PT today, October 14, 2026. Who is affected: The Wsusscn2.cab file is a cabinet file that is signed by Microsoft and contains information about Microsoft security-related updates. Devices that aren't connected to the Internet can be scanned to see whether these security-related updates are present or required. The Wsusscn2.cab file doesn't contain the security updates themselves so you must obtain and install any needed security-related updates through other means. What will happen: You can download and deploy the October 2026 Scan Cab via the usual processes. For detailed guidance, see the Additional information section below. No action is required on environments where Scan Cab is not employed. However, please note that there might be non-Microsoft applications which utilize Scan Cab. Review the documentation for any software and update deployment tools used in your organization to understand if this is applicable in your environment. Additional information: Updated Scan Cab: Download the new Scan Cab here Announcing a smaller WSUS Scan Cab: Learn more about WSUS and the Scan Cab process Using WUA to Scan for Updates Offline: Windows Update Agent (WUA) can be used to scan computers for security updates without connecting to Windows Update WSUS and the Catalog Site: The Catalog Site used by WSUS to import updates and drivers -
Microsoft Planner: AI-generated status reports in Planner Agent
MC1506735 · stayInformed · normal · Updated 10/13/2026 22:15
Services: Planner
Read message
[What and why] We are introducing AI-generated status reports in Planner Agent. This feature uses Planner plan data to generate a status report that summarizes overall status, progress, risks, and next steps. Users can customize reports by specifying items such as audience, tone, length, reporting period, and report sections before reviewing and refining the generated content. [Rollout schedule] Public Preview (Worldwide): Rollout has completed. General Availability (Worldwide): Rollout begins in late October 2026 and is expected to complete by mid-November 2026. [Impact on your organization] Who is affected Organizations who have Planner agent enabled as part of the Microsoft 365 Copilot app. Within those organizations, users with an active Microsoft 365 Copilot license who use Planner Agent.Note: Users who view or edit reports do not require a Microsoft 365 Copilot license; a Copilot license is required only to generate reports. Platforms and services Microsoft Planner Microsoft 365 Copilot What will happen Planner Agent will be able to generate AI-powered status reports from Planner plan data within Microsoft 365 Copilot app. Reports will be generated only from Planner content that users already have permission to access. Existing Planner sharing permissions, Copilot policies, and agent controls continue to apply. Reports will synthesize plan information, including tasks, owners, due dates, status, buckets, and recent activity, into sections such as executive summary, progress, risks and blockers, achievements, milestones, and next steps. Users can customize reports by reporting period, sections, tone, length, audience, and additional instructions before reviewing and refining the generated content. Reports can be exported to a Copilot Page and shared by link or exported to Word and PDF. This feature adds new functionality and does not replace existing Planner capabilities. Copilot-generated status report [Action required and recommendations] No action is required. We recommend that you: Confirm that intended users have an active Microsoft 365 Copilot license. Review Planner Agent and Copilot agent availability and settings in the Microsoft 365 admin center. If needed, the agent can be blocked tenant-wide. Inform support teams and users about the new status report generating capability, which can be accessed via the Planner Agent in Copilot or the Reports tab in Planner.Note that generating a report requires a plan that is shared with a Microsoft 365 Group and contains sufficient task data. Update internal documentation, training, and change management materials as appropriate. [Compliance considerations] To assist our customers with identifying compliance concerns, review the questions below and provide details for impact if appropriate: Does the change store new customer data?[Answer] Yes. A status report generated from your plan appears in the Microsoft 365 Copilot conversation. If a user chooses to export it, the report is also saved as a copilot page or a word document. Does the change alter how existing customer data is processed, stored, or accessed (e.g., documents, emails, chats, etc.)?[Answer] Yes. When an authorized user requests a report, Planner Agent uses information from a plan they can access to create a status report. If the user attaches a file as a template, that file will also be used for the request. This change does not edit the source plan or its tasks. Does the change introduce or significantly modify AI/ML or agent capabilities that interact with or provide access to customer data?[Answer] Yes. It adds the ability to generate and refine a status report through Planner Agent chat using accessible plan information. It does not grant the agent access to plans the requesting user cannot access. -
Action may be required: Review who can create agents in Microsoft Entra
MC1506733 · planForChange · normal · Updated 10/13/2026 22:14
Services: Microsoft Entra
Read message
[What and why] Microsoft Entra is changing who can create agent blueprints by default. Starting November 4, default users will be able to create new agent blueprints unless an administrator turns off Users can create agent blueprints. This means that users without built-in or custom Entra roles will be able to create new agent blueprints in their organization. From now until rollout begins, you can set your tenant preferences to prepare for this rollout. If you do not want users in your organization to create new agent blueprints and their identities, follow the instructions below. [Rollout schedule] Worldwide: Beginning in early November 2026 and expected to complete by late November 2026 [Impact on your organization] Who is affected Organizations using Microsoft Entra Default users who don't have a built-in or custom Microsoft Entra role Platforms and services Microsoft Entra What will happen Default users will be able to create agent blueprints unless an administrator turns off Users can create agent blueprints. If you set the toggle to No, default users will not be able to create new agents. Supported administrators and users assigned the Agent ID Developer role can continue to create them. If you change this toggle now, your tenant won't change right away. Your setting takes effect when the rollout begins in early November. [Action required and recommendations] If default users should be allowed to create agents in your organization, no action is required. Choosing to allow users to create agent blueprints will not begin until the functionality is available in your tenant. To restrict creation: Sign in to the Microsoft Entra admin center using this link. Go to Entra ID > Users > User settings. Under Default user role permissions, find Users can create agent blueprints. Set the toggle to No, then save the change. For more information and instructions on setting the toggle for your organization, see Manage who can create agent blueprints here. This change affects new agent blueprint creation by default users. It does not: Change or remove existing agent blueprints. Change who can create agent identities from existing blueprints. Block an app or an agent from creating identities Affect creation requirements within platforms such as Microsoft Foundry or Security Copilot, such as requiring licenses and Azure subscriptions. The new setting is independent of Users can register applications. Review both settings separately. Learn more Delegate application management administrator permissions - Microsoft Entra ID | Microsoft Learn [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
Microsoft Entra: Changes to AgentIdentity.CreateAsManager permission for agent identities
MC1506728 · planForChange · normal · Updated 10/13/2026 22:12
Services: Microsoft Entra
Read message
[What and why] Microsoft Entra Agent ID is enforcing tighter restrictions for autonomous creation of an agent’s own identities. Currently, all agents are granted AgentIdentity.CreateAsManager upon creation without administrator approval. Starting November 4, Microsoft Entra will no longer automatically grant AgentIdentity.CreateAsManager to agent blueprint principals, and creation of identities will need an admin to grant consent. Agents that use app-only authentication to create their own agent identities must be explicitly granted the AgentIdentity.CreateAsManager Microsoft Graph application permission or move to another supported authorization model before enforcement reaches their tenant. [Rollout schedule] General Availability (Worldwide): Beginning in early November 2026 and expected to complete by late November 2026 [Impact on your organization] Who is affected Organizations using Microsoft Entra No action is required if your organization doesn't have an agent that depends on the automatic AgentIdentity.CreateAsManager grant. Platforms and services Microsoft Entra What will happen Today, an agent blueprint principal is granted AgentIdentity.CreateAsManager automatically. This implicit grant allows the principal to create agent identities without a tenant-admin granting an app-role assignment. After enforcement, an administrator must grant the Microsoft Graph application permission AgentIdentity.CreateAsManager to agents that needs this authority. This change: Makes app-only agent identity creation authority visible, auditable, and revocable. Makes AgentIdentity.CreateAsManager revocable if consented Affects existing and future agents. Doesn't remove existing agent identities or agent blueprints. Doesn't remove the ability for agent identity blueprints to create agent identities, when AgentIdentity.CreateAsManager is explicitly granted by an administrator Doesn't affect an agent that uses a directory role to authorize creation of agent identities. [Action required and recommendations] No action is required if your organization doesn't have an agent that depends on the automatic AgentIdentity.CreateAsManager grant. Identify agents that create agent identities without a signed-in user. Sign in to the Microsoft Entra admin center. Go to Entra ID>Audit Logs. Set the Category to "ApplicationManagement" Set the Activity filter to "Add Service Principal" Find events where the Initiated By (actor) Type is Application and the Target is an agent identity. For each affected agent: Sign in to the Microsoft Entra admin center. Go to Entra ID>Agent blueprints>Search for your agent blueprint>Granted permissions Review if the Agent has any other granted permissions that may allow for creation of agent identities. If there are no other permissions allowing for creation, this agent relies on AgentIdentity.CreateAsManager. Starting October 16, you may grant the explicit AgentIdentity.CreateAsManager Microsoft Graph application permission through tenant-wide admin consent or manual app-role creation. Granting it earlier will cause an error. A successful grant appears in the Granted Permissions table with “An administrator” in the Granted By column. Test app-only agent identity creation before enforcement begins. Update operational guidance for a failed request after enforcement. If an app-only request relies only on the automatic grant after enforcement reaches your tenant, the request will fail with a 403 authorization error. Learn more For more about how to grant your agents access to resources, visit Grant agents access to Microsoft 365 resources | Microsoft Learn. For the Microsoft Graph permission reference on AgentIdentity.CreateAsManager, visit Microsoft Graph permissions reference - Microsoft Graph | Microsoft Learn. [Compliance considerations] No specific compliance impacts have been identified for this configuration update. -
(Updated) Microsoft Edge: Upgraded Copilot new tab page
MC1440972 · stayInformed · normal · Updated 10/13/2026 20:46
Services: Microsoft 365 suite
Read message
Updated October 13, 2026: We have updated the timeline. Thank you for your patience. [What and why] Microsoft Edge is introducing an upgraded Copilot new tab page that brings Microsoft 365 Copilot chat, web search, and work content into a single experience. Users can search the web, navigate to websites, interact with Microsoft 365 Copilot, and access relevant work content from a single experience. The updated experience includes enhanced Copilot chat integration, compose capabilities, suggested actions, curated work content, and a refreshed design to help users complete tasks more efficiently. This message is associated with Microsoft 365 Roadmap ID 566703. [Rollout schedule] Public Preview: Beginning in late September 2026 (previously early September) and expected to complete by mid-October 2026 (previously mid-September) General Availability (Worldwide): Beginning in early November 2026 (previously mid-October) [Impact on your organization] Who is affected Users in your organization who have the Copilot new tab page enabled in Microsoft Edge. Users who do not have the Copilot new tab page enabled will continue to see the existing new tab page experience. To access this experience, users must have a Microsoft 365 Copilot license. Platforms and services Microsoft Edge Microsoft 365 Copilot What will happen The Copilot new tab page is off by default. When enabled, users will see: An updated search box for navigating to websites, searching the web, or sending a query to Microsoft 365 Copilot. Enhanced Copilot chat and compose capabilities. Suggested actions and work content to help users begin and complete tasks. Work cards that may surface organizational content such as files and calendar events. A refreshed design, app launcher, pinned quick links, and updated theme settings. Starting in September 2026, Discover feed and feed toggle functionality will be limited. We plan to continue improving and expanding these capabilities as the Copilot new tab page evolves A Discover feed with curated news and content where supported. Admins can enable the Copilot new tab page through the Microsoft Edge management service using the CopilotNewTabPageEnabled policy and assign the configuration to all users or selected Microsoft Entra groups. Depending on organizational policy settings, users may be able to disable the experience after it has been enabled. Users who are not enabled will continue to see the existing Microsoft Edge new tab page. [Action required and recommendations] The Copilot new tab page is off by default. No admin action required before rollout as this change applies only to organizations that enabled the Copilot new tab page via CopilotNewTabPageEnabled. If your organization has enabled this policy, users will automatically see the upgraded Copilot new tab page. If the policy is not configured or is disabled, there is no change to your users' new tab page experience. If your organization plans to enable the experience, we recommend that you: Review your current Microsoft Edge and Copilot new tab page configuration. Determine which users or Microsoft Entra groups should receive the experience. Verify that affected users have a Microsoft 365 Copilot license. Evaluate the effect of surfacing organizational files and calendar events through work cards. Review applicable AI governance and compliance requirements before enabling the experience. Notify affected users about the updated new tab page. Update relevant user guidance, training, and support documentation. Learn more Configure the Copilot new tab page | Microsoft Edge | Microsoft Learn [Compliance considerations] QuestionAnswer Does this change introduce or significantly modify AI, ML, or agent capabilities that interact with or provide access to customer data?Yes. The upgraded Copilot new tab page integrates Microsoft 365 Copilot chat and can surface organizational content, including files and calendar events, through work cards and suggested prompts. Does this change provide end users with a new way to interact with generative AI?Yes. Users can send queries directly to Microsoft 365 Copilot from the new tab page search box and access integrated Copilot chat functionality within the Microsoft Edge new tab experience. Does this change include an admin control?Yes. Administrators can enable the Copilot new tab page through the Microsoft Edge management service and assign the configuration to all users or selected Microsoft Entra groups. Can users enable or disable the feature themselves?Yes. Depending on organizational settings, users may be able to turn off the Copilot new tab page experience and switch between Work cards and Chat chips. Can the feature be controlled through Microsoft Entra ID group membership?Yes. Administrators can assign the Copilot new tab page configuration to one or more Microsoft Entra groups. -
Manage Administrator protection within Windows 11 security baseline
MC1506291 · stayInformed · normal · Updated 10/13/2026 19:00
Services: Windows
Read message
What and why: If your organization uses Windows security baselines, Administrator protection becomes enabled by default with the October 2026 Windows security update. The security baselines for Windows 11 that enable Administrator protection by default apply to versions 26H2, 25H2, and 24H2. Use Microsoft Intune or Group Policy to manage Administrator protection enablement as part of the security baseline. The following policies are part of the security baseline: User Account Control: Configure type of Admin Approval Mode User Account Control: Behavior of the elevation prompt for administrators running with Administrator protection Rollout schedule: Administrator protection is generally available (disabled by default). Starting with the October 2026 Windows security update, it’s enabled by default within the Windows 11 security baselines. Impact on your organization: This change only affects IT admin roles in commercial organizations that use Administrator protection and Windows security baselines on supported devices. Administrator protection becomes enabled by default, helping protect organizations from unauthorized elevated privileges. If the new default doesn’t align with your organizational strategy, enable or disable Administrator protection via policy. Action required/recommendations: Review and test your security baseline configuration and adjust it as appropriate for your environment. Use Microsoft Intune or Group Policy to manage Administrator protection enablement as part of the security baseline. Learn more in Administrator protection. Compliance considerations: No compliance considerations are identified. Review as appropriate for your organization. -
Hardening changes for ReFS volumes on removable media
MC1506290 · stayInformed · normal · Updated 10/13/2026 19:00
Services: Windows
Read message
What and why: Microsoft is making hardening changes to the Resilient File System (ReFS). The changes improve the security posture of Windows by adding visibility into unsupported external ReFS configurations and by providing controls to block affected volumes. The changes apply to all supported Windows platforms in phases to allow your organization to review audit data and address dependencies. Rollout schedule: October 2026 Windows security update (Audit phase) January 2027 Windows security update (Enforcement phase) Impact on your organization: The changes improve the security posture of Windows but require admin action. Action required/recommendations: UPDATE: Install the applicable Windows security update released on or after October 13, 2026 on supported devices. MONITOR: Review the ReFS audit events generated for removable media. ASSESS: Identify workflows that rely on ReFS volumes in unsupported external media configurations and migrate required data or workloads to a supported storage configuration. TEST: Enable blocking in a controlled environment and confirm that required devices and applications continue to operate as expected. ENFORCE: Enable blocking when your environment is ready. If you configure no override, blocking becomes the default with the January 2027 security update. Learn more at Hardening changes for ReFS volumes on removable media. Compliance considerations: Hardening changes affect Windows security. Review as appropriate for your organization. -
Windows 11, version 24H2 (Home and Pro) and Windows 10 LTSB 2016 have reached end of updates
MC1506289 · stayInformed · normal · Updated 10/13/2026 19:00
Services: Windows
Read message
Today, October 13, 2026, Windows 11, version 24H2 Home and Pro, and Windows 10 Enterprise LTSB 2016 have reached end of updates. The October 2026 monthly security update is the last update available for these editions. Devices running these editions will no longer receive monthly security and non-security preview updates containing protections from the latest security threats. We recommend updating devices running Windows 11, version 24H2 Home and Pro editions to Windows 11, version 26H2 or Windows 11, version 25H2 to continue receiving monthly security and quality updates. Windows 11, version 24H2 Enterprise and Education remain supported until October 12, 2027. For more information, see the How to get the Windows 11 2026 Update video. For devices running Windows 10 Enterprise LTSB 2016, we recommend updating to the latest Long-Term Servicing Channel (LTSC) release, Windows 11 Enterprise LTSC 2024. Extended Security Updates (ESU) are also available for organizations that need additional time to complete their transition. For more information about product lifecycle dates, see Windows 11 release information, Windows 10 release information, and Lifecycle FAQ - Windows. -
The October 2026 Windows security update is now available
MC1506288 · stayInformed · normal · Updated 10/13/2026 19:00
Services: Windows
Read message
The October 2026 Windows security update is now available for all supported versions of Windows. We recommend that you install these updates promptly. For more information about the contents of this update, see the release notes, which are accessible from the Windows 11 update history page. To learn more about the different types of monthly quality updates, see Understanding Windows monthly updates. Highlights for the Windows 11, version 26H2 update: This security update includes improvements that were part of update KB5124008 (released September 8, 2026). This update addresses an issue that could cause Always On VPN connections to become stuck in a connecting state or fail to reconnect when automatic protocol selection or fallback was configured. This update fixes an issue in Azure Virtual Desktop and FSLogix environments where Windows Explorer could fail to start after sign-in, resulting in a black screen. This update adds auditing and optional policy controls for ReFS volumes on externally attached storage devices to help organizations prepare for future security hardening changes. This update fixes an issue that could prevent some tiered Storage Spaces Direct virtual disks from coming online after installing certain security updates, affecting clustered workloads. Short on time? Watch the Windows 11 release notes video for this month’s tips. For instructions on how to install this update, see the KB article for your operating system listed below: Windows 11, versions 26H2, 25H2, and 24H2: KB5127648 Windows 11, version 26H1: KB5127646 Windows 11, version 23H2: KB5126653 Windows 10, versions 22H2 and 21H2: KB5126657 Windows 11 Enterprise LTSC 2024: Baseline KB5131362 Windows 10 Enterprise LTSC 2019 and Windows Server 2019: KB5126651 Windows 10 LTSB 2016 and Windows Server 2016: KB5126868 Windows Server 2025: KB5126646 Windows Server 2025 Datacenter: Azure Edition: Baseline KB5131334 Windows Server 2022: KB5126655 Windows Server 2022 Datacenter: Azure Edition: Baseline KB5126655 Windows Server 2012 R2: KB5126836 Windows Server 2012: KB5126835 Note: With recent and upcoming Windows updates over the next few months, a limited number of consumer and business devices might experience one additional restart during installation. This one‑time restart occurs after a Secure Boot certificate update is applied as part of the Secure Boot update process. -
AD FS Distributed Key Manager (DKM) container ACL hardening begins today
MC1506287 · stayInformed · normal · Updated 10/13/2026 19:00
Services: Windows
Read message
What and why Beginning with the October 2026 Windows security update, AD FS Distributed Key Manager (DKM) container access control list (ACL) hardening enters Enforcement mode. These protections address the elevation of privilege vulnerability described in CVE-2026-56155 by automatically remediating insecure DKM container ACL configurations on supported versions of Windows Server. Rollout schedule Enforcement mode starts with the October 2026 Windows security update. Impact on your organization After you install the October 2026 Windows security update, supported Windows Server versions apply remediation by default unless administrators explicitly opt out. This remediation can modify DKM container permissions in AD FS environments. Windows Server 2012 and Windows Server 2012 R2 require manual remediation and don’t receive automatic remediation. Action required/recommendations Organizations using AD FS should: Install the July 14, 2026 Windows security update or a later Windows update on AD FS servers. Review AD FS Admin event logs for Event ID 1132, which indicates that DKM container permissions need attention. Resolve any outstanding DKM container permission or compatibility issues identified during Audit mode. Verify that your environment is prepared for default remediation or explicitly opt out if necessary. See the guidance in: CVE-2026-56155: AD FS Distributed Key Manager container ACL hardening. Compliance considerations No compliance considerations are identified. Review as appropriate for your organization. -
Notice: The October 2026 Scan Cab for Microsoft updates is delayed
MC1506286 · stayInformed · normal · Updated 10/13/2026 19:00
Services: Windows
Read message
Note: This notice only affects environments where Scan Cab is used to check for Microsoft update compliance. What and why: The Scan Cab for the October 2026 Microsoft security updates is currently delayed and has not yet been released. Rollout schedule: The Scan Cab for the October 2026 Microsoft security updates is currently delayed and has not yet been released. We will communicate an update on Scan Cab availability as more information becomes available. Thank you for your patience. Who is affected: IT administrators who rely on Scan Cab to check for update compliance can monitor our communications for updates. What will happen: Updates on the availability of this month's Scan Cab will be communicated as new information becomes available. Additional information: Learn more about the Scan Cab process: Announcing a smaller WSUS Scan Cab Use Windows Update Agent (WUA) to scan computers for security updates without connecting to Windows Update: Using WUA to Scan for Updates Offline - Win32 apps Documentation on the Catalog Site used to import updates and drivers: WSUS and the Catalog Site -
Build apps in Microsoft Copilot Studio and Copilot Cowork
MC1469329 · planForChange · normal · Updated 10/13/2026 18:25
Services: Microsoft 365 Copilot Chat
Read message
Updated October 13, 2026: Following our earlier announcement, Apps in Copilot Studio has started its public preview rollout. Availability will expand gradually by region. Makers building apps in Copilot Studio will use the Copilot Credits available in the environment they're building in. Copilot Credits for app building are allocated, monitored, and billed through the same Power Platform admin center experience you already use for agents in Copilot Studio — no separate setup is required. Admins can review the credit allocation documentation in PPAC to learn more: https://learn.microsoft.com/en-us/power-platform/admin/manage-copilot-studio-copilot-credits-capacity [What and why:] We are announcing a preview of the new app-building experience in Microsoft Copilot Cowork. A corresponding experience in Microsoft Copilot Studio will follow within the next couple of weeks. These experiences make it easier for people to turn ideas into apps using natural-language guidance and generative AI. Makers can create a working first draft through natural-language conversation, refine it, preview and test it, and then publish and share it. Apps can use organizational data through connectors permitted by your organization’s policies. Apps built in Cowork can be opened and further edited in Copilot Studio. Apps created through these experiences will be visible to administrators in the new Apps experience in the Microsoft 365 admin center, providing consistent governance and organization-wide visibility. [Rollout schedule:] Rollout for Copilot Cowork will begin on September 8, 2026, and is expected to complete by September 14, 2026. The corresponding experience in Microsoft Copilot Studio is expected to become available within the next weeks. [Impact on your organization:] The app-building experience in Copilot Cowork is available in preview through the Frontier Program to users who have a Microsoft 365 Copilot license and access to Cowork. When the app-building experience in Copilot Studio becomes available, it will be enabled by default for eligible makers. During preview, administrators can turn the experience on or off in the Microsoft 365 admin center and scope access to specific security groups. Eligible users will be able to create and refine apps through conversation, preview and test them, and publish and share them with people or groups permitted by organizational policies. Apps use Microsoft Entra authentication and follow your organization's existing connector, environment, data, security, compliance, and sharing policies. Published apps are visible in Apps > All apps in the Microsoft 365 admin center. Based on the organization’s governance policies, makers who create apps through these experiences are automatically routed to an isolated personal developer environment instead of the shared environment. The personal developer environment is protected from the start by secure defaults that administrators can adjust to meet organizational requirements. Applicable policies are enforced when each app is created, helping keep apps within the organization’s governance boundaries. For organizations that have not enabled environment routing, routing will be automatically applied to apps created through these experiences. This change does not affect other resources created in Power Platform or Copilot Studio. [Action required / Recommendations:] Complete Frontier Program onboarding for your organization and enable eligible app creators in the Microsoft 365 admin center under Apps > Overview. Review the default configuration and adjust the policies to match your requirements in Microsoft 365 admin center > Apps > Settings. Inform your maker community when each experience becomes available and share your organization’s requirements for building and sharing apps. Review the Copilot Credits requirements for building and running apps and configure usage-based billing as needed. Learn more Get started with the Microsoft Copilot Frontier Program Build apps in Copilot Cowork documentation link Manage apps in the Microsoft 365 admin center Manage Copilot Cowork for your organization Copilot Credits Guide Understand usage-based billing and cost management for Copilot Credits -
Dynamics 365 Apps - Add users without licenses to activity recipient fields (preview)
MC1506229 · stayInformed · normal · Updated 10/13/2026 17:46
Services: Dynamics 365 Apps
Read message
We are announcing the ability to enable active Microsoft Entra users without Dataverse or Power Apps licenses as activity recipients. Created user records remain disabled and do not grant Dynamics 365 app access. This feature will reach public preview on October 15, 2026. How does this affect me? With this feature enabled, active Entra ID users who do not have a valid Dynamics 365 or Power Apps license can be selected in fields such as: Email: To, Cc, and Bcc Appointment: Owner, Required Attendees, and Optional Attendees Phone call: Owner, Call From, and Call To Task: Owner (co-owner) What action do I need to take? This message is for awareness, and no action is required. If you would like more information on this feature, please visit Add users without licenses to activity recipient fields (preview). -
Microsoft Teams: Hide organizer names in calendar view on Teams Panels
MC1484010 · stayInformed · normal · Updated 10/13/2026 16:48
Services: Microsoft Teams
Read message
[What and why] Microsoft Teams Panels will introduce a new administrator setting that allows administrators to choose whether organizer names are shown in Calendar View on Teams Panels. Admins can toggle the Show organizer name setting ON or OFF in the Teams Rooms Pro Management portal or on the panel device. When organizer names are hidden, the organizer name is not shown in Calendar View on the panel device. This feature is available with Teams Rooms Pro and Teams Shared Spaces licenses. [Rollout schedule] General Availability (Worldwide): Beginning in early October 2026 and expected to complete by early October 2026 [Impact on your organization] Who is affected Administrators who manage Microsoft Teams Panels Organizations using Teams Rooms Pro licenses Organizations using Teams Shared Spaces licenses Users who view meeting information on Teams panel devices Platforms and services Microsoft Teams Panels Teams Rooms Pro Management portal What will happen A new setting, Show organizer name, will be available for Teams panel devices. Administrators can choose whether organizer names are displayed in Calendar View. The setting can be configured from the Teams Rooms Pro Management portal or directly on a Teams panel device. By default, organizer names will continue to be displayed in Calendar View. [Action required and recommendations] No action is required if you want organizer names to continue appearing in Calendar View on Teams panel devices. If you want to hide organizer names: Review your room privacy and display requirements. Update the Show organizer name setting in the Teams Rooms Pro Management portal or on individual Teams panel devices. Learn more Release notes for devices in Microsoft Teams - Microsoft Teams | Microsoft Learn [Compliance considerations] QuestionAnswer Does the change include an admin control, and can it be controlled through Entra ID group membership?Yes. Administrators can enable or disable the display of organizer names on Teams Panels. The available information does not indicate support for management through Entra ID group membership. -
(Updated) Microsoft Entra: Allow password change after secure sign-in with My Sign-Ins
MC1437671 · stayInformed · normal · Updated 10/13/2026 16:45
Services: Microsoft Entra
Read message
Updated October 9, 2026: We have updated the content. Thank you for your patience. [What and Why] We're introducing a new Microsoft Entra capability that allows password change after secure sign-in directly from My Sign-Ins using an existing strong credential, such as a passkey, FIDO2 security key, or Windows Hello for Business. Users can complete this action even if they don't know their current password and without using self-service password reset (SSPR) or contacting the helpdesk. Many organizations are adopting allowed password changes after secure sign-ins but still maintain passwords for legacy applications and services. This update helps reduce password-related support requests and removes a common barrier to adoption. The feature is disabled by default and requires administrator enablement before users can access it. [Rollout Schedule] General Availability (Worldwide and GCC): Beginning end of October 2026 (previously mid-October) and expected to complete by end of November 2026 (previously late October) [Impact on Your Organization] Who is affected Microsoft Entra administrators who manage password change settings Users who have a registered allowed password change after secure sign-in method (passkey, FIDO2 security key, or Windows Hello for Business) and also maintain a password Organizations that choose to enable the feature Platforms/Services Microsoft Entra My Sign-Ins (mysignins.microsoft.com) What will happen Because this feature is off by default, there is no change to your users' experience unless you turn it on. After the feature is enabled, eligible users will see a new Change password option in My Sign-Ins. Users can authenticate set a new password without knowing their existing password. Users are not required to enroll in or use SSPR to complete this action. Administrators can choose to enable or disable the capability through Microsoft Entra management interfaces available at release. Authentication continues to require a strong password change method, such as a passkey, FIDO2 security key, or Windows Hello for Business. The setting is tenant-wide: you can turn it on for your entire tenant or leave it off for everyone. There is no per-user or per-group scoping. [Action Required/Recommendations] No action is required. If your organization plans to support allowed password changes after secure sign-in: Review your password management and allowed password changes after secure sign-in strategy. Evaluate whether enabling this capability aligns with your organization's security and support requirements. Communicate the new self-service capability to helpdesk and support teams. Update internal user guidance and documentation as needed. If your organization chooses to offer allowed password changes after secure sign-in, enable the feature through the Microsoft Entra admin experience or supported APIs when it becomes available in October 2026. Learn more Microsoft Learn documentation will be available when the feature releases in October. [Compliance Considerations] QuestionAnswer Does the change include an admin control?Yes. The feature is disabled by default and requires explicit administrator enablement. Does the change modify how users can access or correct their personal data?Yes. Users gain a new self-service method to update their password using an existing allowed password change after secure sign-in. -
Public CDN is becoming optional during Brand Center setup
MC1505610 · stayInformed · normal · Updated 10/12/2026 23:06
Services: Microsoft 365 suite, SharePoint Online
Read message
[What and Why:] We are updating the Brand Center setup experience so that administrators can set up Brand Center without enabling Public CDN. Today, Public CDN is enabled as part of Brand Center setup, even when an organization only wants to use branding governance capabilities that do not require it. With this update, organizations can begin using Brand Center while deferring Public CDN until they need capabilities that depend on it, such as organizational fonts. [Rollout Schedule:] General Availability (Worldwide): We will begin rolling out in mid-October 2026 and expect to complete by late October 2026. [Impact on Your Organization:] When an administrator sets up Brand Center in the Microsoft 365 admin center: Public CDN will be unselected by default. Brand Center setup can be completed without Public CDN. Public CDN will only be enabled after an administrator explicitly selects the option and confirms the change. Font-related capabilities will remain unavailable until Public CDN is enabled. If Public CDN is already enabled for the tenant, this update will not disable or change it. This change separates Brand Center setup from Public CDN activation. It does not remove the Public CDN requirement for organizational fonts. Why we are making this change Some organizations want to begin using Brand Center for branding governance without introducing an external or public content-delivery dependency. Making Public CDN optional provides a more incremental adoption path: organizations can establish Brand Center first and enable font capabilities only when they are ready. [Action Required/Recommendations:] No action is required. If your organization plans to use organizational fonts, an administrator must explicitly enable Public CDN during setup or later from the applicable settings experience. Set up the SharePoint Brand Center Use organizational fonts in SharePoint Learn more about Microsoft 365 Public CDN [Compliance considerations:] QuestionAnswer Does the change include an admin control and can it be controlled through Entra ID group membership?Yes. The feature includes or affects admin controls, policies, permissions, roles, authentication, or management settings as described in this message. Review the linked documentation or admin center controls for group-based configuration support. -
Microsoft 365 Copilot and Power Apps: Retirement of App Builder agent and vibe.powerapps.com
MC1505609 · planForChange · normal · Updated 10/12/2026 23:05
Services: Power Apps in Microsoft 365
Action required by: 11/30/2026 08:00
Read message
[What and why] Apps in Copilot Cowork are now available through the Frontier program, and Apps in Microsoft Copilot Studio are rolling out in public preview.To provide a unified experience for building apps with natural language, Microsoft is retiring the App Builder agent in Microsoft 365 Copilot and vibe.powerapps.com. Copilot Cowork and Microsoft Copilot Studio will become the primary experiences for creating apps using natural language. This retirement helps consolidate app creation experiences and provides makers with a consistent path forward for building and managing apps. [Rollout schedule] MilestoneEvent Apps in Copilot Cowork available through the Frontier programSeptember 8, 2026 Public preview rollout of Apps in Microsoft Copilot Studio beginsEarly October 2026 In-product migration becomes available. Creation of new apps in App Builder agent and vibe.powerapps.com is no longer supported.Mid-October 2026 App Builder agent and vibe.powerapps.com are retired.November 30, 2026 [Impact on your organization] Who is affected Makers who have built apps using the App Builder agent in Microsoft 365 Copilot Makers who have built apps using vibe.powerapps.com Administrators responsible for supporting these makers and applications Platforms and services Microsoft 365 Copilot Power Apps Microsoft Copilot Studio Copilot Cowork What will happen Starting in mid-October 2026, makers will no longer be able to create new apps using the App Builder agent. Starting in mid-October 2026, makers will no longer be able to create new apps using vibe.powerapps.com. Existing App Builder and Vibe apps can be opened to begin the migration process once in-product migration becomes available. On November 30, 2026, the App Builder agent and vibe.powerapps.com will be retired. Apps that are not successfully migrated before November 30, 2026, will no longer be accessible through these retired experiences. Makers should build new apps in Copilot Cowork or Microsoft Copilot Studio. [Action required and recommendations] Action is required if your organization has apps created using the App Builder agent or vibe.powerapps.com. Identify makers and teams currently using the App Builder agent or vibe.powerapps.com. Communicate this retirement timeline to affected makers. Direct makers to use Copilot Cowork or Microsoft Copilot Studio for new app development. Review migration documentation and begin manual migration of existing apps once in-product migration becomes available. Use the in-product migration experience when it becomes available sometime around mid-October 2026. Complete migration of any apps your organization wants to retain before November 30, 2026. Learn more Build apps with Microsoft Copilot (Frontier) | Microsoft Support Overview of the new Power Apps vibe experience - Power Apps | Microsoft Learn [Compliance considerations] No compliance considerations identified, review as appropriate for your organization. -
Microsoft Purview Audit: AuditLogQuery API generally available and Search-UnifiedAuditLog retiring
MC1505599 · planForChange · normal · Updated 10/12/2026 23:04
Services: Microsoft Purview
Read message
[What and why] The Microsoft Graph AuditLogQuery API is generally available for programmatic access to Microsoft Purview Audit activity logs. We are also announcing the planned retirement of the Search-UnifiedAuditLog PowerShell cmdlet on October 15, 2027. The AuditLogQuery API provides improved scalability and reliability, more granular workload-level permissions, and support for exporting up to 1 million audit records per query. As audit data volumes and automation scenarios have grown, Search-UnifiedAuditLog has reached scalability limitations that can affect reliability and performance for large-volume searches. Future investments and enhancements for audit search will focus on the AuditLogQuery API. [Rollout schedule] Microsoft Graph AuditLogQuery API general availability (Worldwide): Beginning in early October 2026 Search-UnifiedAuditLog retirement: Search-UnifiedAuditLog will continue to function unchanged until October 15, 2027. On October 15, 2027, Search-UnifiedAuditLog will be retired and will no longer provide access to the audit log. Organizations using Search-UnifiedAuditLog should migrate to the Microsoft Graph AuditLogQuery API before October 15, 2027. [Impact on your organization] Who is affected Organizations that use Search-UnifiedAuditLog for audit data retrieval, reporting, investigations, compliance workflows, or automation are affected. Organizations that do not use Search-UnifiedAuditLog are not required to take action for this retirement. Platforms and services Microsoft Purview Audit Microsoft Graph AuditLogQuery API Exchange PowerShell Search-UnifiedAuditLog cmdlet What will happen Admins with the required permissions will be able to programmatically access audit logs through the Microsoft Graph AuditLogQuery API. Existing PowerShell scripts, applications, and automation workflows that call Search-UnifiedAuditLog will need to be updated to use the AuditLogQuery API. Search-UnifiedAuditLog will continue to function unchanged until October 15, 2027. On October 15, 2027, Search-UnifiedAuditLog will no longer provide access to the audit log. There is no tenant setting to prevent the retirement. Organizations that do not complete migration before October 15, 2027, may experience disruptions to audit retrieval processes that depend on Search-UnifiedAuditLog. Future investments and enhancements for audit search will focus on the AuditLogQuery API rather than Search-UnifiedAuditLog. The AuditLogQuery API supports exporting up to 1 million audit records per query. The AuditLogQuery API uses tenant-level throttling limits. Each tenant has a baseline of 200 search submissions per rolling 24-hour period and can have up to 50 searches queued or running at one time. Larger tenants may receive higher allocations based on eligible license counts. When a limit is reached, the API returns an HTTP 429 Too Many Requests response with retry guidance. [Action required and recommendations] If your organization uses Search-UnifiedAuditLog, begin migration planning and complete the migration before October 15, 2027. Identify scripts, applications, automation workflows, and operational processes that currently use Search-UnifiedAuditLog. Evaluate the Microsoft Graph AuditLogQuery API and validate that it meets your audit retrieval requirements. Register your application with Microsoft Graph and add the required Microsoft Graph permissions. Update and test existing integrations to use the AuditLogQuery API. Complete migration before October 15, 2027, to avoid service disruption. No action is required if your organization does not use Search-UnifiedAuditLog. Learn more auditLogQuery resource type - Microsoft Graph v1.0 | Microsoft Learn Examples - List auditLogQueries - Microsoft Graph | Microsoft Learn Get started with auditing solutions | Microsoft Learn Learn about auditing solutions in Microsoft Purview | Microsoft Learn Microsoft Graph service-specific throttling limits - Microsoft Graph | Microsoft Learn Permissions - List auditLogQueries - Microsoft Graph | Microsoft Learn Search-UnifiedAuditLog (ExchangePowerShell) | Microsoft Learn Security audit log query service limits - Microsoft Graph service-specific throttling limits - Microsoft Graph | Microsoft Learn Use the Microsoft Graph API - Microsoft Graph | Microsoft Learn [Compliance considerations] QuestionAnswer Does the change modify, interrupt, or disable Audit logging capabilities?Search-UnifiedAuditLog will no longer provide access to the Audit log effective October 15, 2027. Does the change alter how admins can monitor, report on, or demonstrate compliance activities?Programmatic retrieval of Microsoft Purview Audit activity logs is moving from Search-UnifiedAuditLog to the Microsoft Graph AuditLogQuery API for organizations using the retiring cmdlet. Does the change include an admin control?Access to the AuditLogQuery API requires applicable Microsoft Graph permissions. The retirement itself cannot be prevented through a tenant setting. The source does not state that the change can be controlled through Entra ID group membership. -
(Updated) Connect Teams meeting to existing Planner Plans
MC1392571 · planForChange · normal · Updated 10/12/2026 16:46
Services: Planner, Microsoft Teams
Read message
Updated October 12, 2026: We have updated the timeline. Thank you for your patience. [Introduction] We are introducing a new capability that allows users to connect Microsoft Teams meetings to existing Microsoft Planner plans. Currently, Teams meetings automatically create separate Planner plans for meeting-related tasks, which can result in tasks for the same initiative being spread across multiple plans. This update enables users to link meetings to an existing plan so tasks can be tracked in a single location, improving organization and continuity across ongoing work. This message is associated with Roadmap ID 561490. [When this will happen:] Targeted Release (Worldwide): We will begin rolling out in late December 2026 (previously late September) and expect to complete by end of January 2027 (previously end of September 2026). General Availability (Worldwide): We will announce via Message center when we are ready to proceed. [How this affects your organization:] Who is affected: Users who create or participate in Microsoft Teams meetings and use Microsoft Planner Organizations with Teams, Planner, and Loop enabled What will happen: Users will be able to link a Teams meeting to an existing Planner plan. Tasks created during meetings can be added to the selected existing plan. If no plan is selected, meetings will continue to create a new Planner plan. This feature will be available by default. Facilitator (the meeting task automation capability) can create tasks in the selected plan. Users can manually create tasks if Facilitator is disabled. No changes to existing plans or previously created plans. Learn more: Facilitator in Microsoft Teams meetings | Microsoft Support [What you can do to prepare:] No action is required. You may want to:Ensure that Teams, Planner, and Loop are enabled in your tenant. Review whether Facilitator should be enabled for automated task creation scenarios. Update internal documentation or task management guidance if applicable. Inform helpdesk staff and users about this new option for organizing meeting tasks. [Compliance considerations:] QuestionExplanation Does the change alter how existing customer data is processed, stored, or accessed (e.g. documents, emails, chats, etc.), if so how and to what extent?Tasks created in Teams meetings can now be stored in an existing Planner plan instead of a new auto-generated plan, changing how task data is organized across plans. Does the change introduce or significantly modify AI/ML or agent capabilities that interact with or provide access to customer data, if so summarize changes?Facilitator can create and associate tasks with user selected Planner plans when enabled. Does the change include an admin control and, can it be controlled through Entra ID group membership?Availability depends on enabling Teams, Planner, Loop, and optionally Facilitator in the tenant. Does the change allow a user to enable and disable the feature themselves?Users can choose whether to link a meeting to an existing plan or continue using the default behavior. -
Microsoft Graph: New tenant controls for retirement of non-standard file API tokens
MC1492958 · planForChange · normal · Updated 10/09/2026 20:43
Services: SharePoint Online
Action required by: 04/01/2027 07:00
Read message
[What and why] Microsoft is retiring pre-authenticated URLs, also known as tempauth URLs, from SharePoint Online and OneDrive. Beginning April 1, 2027, selected Microsoft Graph file APIs will no longer return URLs that contain embedded authentication information and will no longer issue HTTP 302 redirects to those URLs. To help organizations prepare, new SharePoint Online tenant controls are coming soon in a future release of Microsoft SharePoint Online PowerShell. These controls will allow administrators to enable updated Microsoft Graph URL behavior for specific applications before the retirement date. This gives organizations time to validate application compatibility, improve security posture, and transition to standard Microsoft Entra ID authentication before the change takes effect. [Rollout schedule] Service change (Worldwide, GCC, GCC High, DoD): Beginning in early April 2027 and expected to complete in late April 2027 [Impact on your organization] Who is affected Administrators responsible for Microsoft Graph, SharePoint Online, OneDrive, application integrations, and tenant security Owners of third-party applications, line-of-business applications, custom applications, and automation solutions that use affected Microsoft Graph file APIs Organizations using applications that follow redirects or rely on URLs containing embedded authentication information Platforms and services Microsoft Graph SharePoint Online OneDrive Microsoft Entra ID Third-party and custom applications that consume Microsoft Graph file APIs What will happen Applications using affected Microsoft Graph APIs may currently receive: SharePoint Online download, upload, monitor, preview, version, or similar URLs that contain temporary authentication information. Media service URLs that contain temporary authentication information. HTTP 302 redirects to URLs containing embedded authentication information. After the change: Applications configured to use supported Microsoft Graph URL alternatives will receive Microsoft Graph URLs and continue authenticating with Microsoft Graph access tokens. APIs that currently return HTTP 302 redirects to temporary authentication URLs will instead return content directly. SharePoint Online URLs returned by affected APIs will no longer contain embedded temporary authentication information. Applications accessing SharePoint Online URLs directly will need a valid Microsoft Entra ID access token for the SharePoint Online resource. Requests made directly to SharePoint APIs rather than through Microsoft Graph are not affected by the tenant control setting. Applications that store, inspect, or redeem URLs containing embedded authentication tokens may stop functioning if not updated before April 1, 2027. The change is not enabled by default through tenant controls. Administrators must choose which application IDs participate in testing and validation. Affected API families include: File download and content APIs createUploadSession APIs Copy APIs and long-running action monitors Preview APIs Thumbnail APIs Version APIs Format conversion APIs [Action required and recommendations] Administrators should begin validation before April 1, 2027. Recommended actions: Identify applications that obtain file, version, thumbnail, preview, upload-session, or copy-operation URLs through Microsoft Graph. Review whether applications inspect, store, or redeem URLs containing embedded authentication information. Verify that applications can process direct content responses instead of relying on HTTP 302 redirects. Confirm applications can obtain and send the appropriate Microsoft Entra ID access token when calling Microsoft Graph or SharePoint Online endpoints. Enable the new tenant setting for a limited set of application IDs and validate application behavior. Monitor application errors, authentication failures, and sign-in activity during testing. Expand the configuration to additional applications after successful validation. Contact application vendors and internal application owners to confirm support plans and timelines for affected applications. Communicate this upcoming change to development and application support teams. No action is required if: Your organization does not use the affected APIs. Applications already use direct Microsoft Graph content endpoints and standard Microsoft Entra ID authentication. Learn more Clear-SPOTenantPreAuthSettings (Microsoft.Online.SharePoint.PowerShell) | Microsoft Learn Get-SPOTenantPreAuthSettings (Microsoft.Online.SharePoint.PowerShell) | Microsoft Learn Get started with the SharePoint Online Management Shell | Microsoft Learn OAuth 2.0 and OpenID Connect protocols - Microsoft identity platform | Microsoft Learn Pre-authenticated (tempauth) URLs are retiring: move to Microsoft Entra ID tokens before April 1, 2027 - Microsoft 365 Developer Blog [Compliance considerations] QuestionAnswer Does the change include an admin control, and can it be controlled through Entra ID group membership?Yes. New SharePoint Online tenant controls are being introduced to allow administrators to opt specific application IDs into the updated authentication behavior before the retirement date. Customers should review documentation to determine available scoping and configuration options. Regarding controlled by EntraID Group membership, I do not think that applies. These are SharePoint Online PowerShell cmdlets. -
Microsoft Planner: Introducing Local Custom Fields
MC1492955 · planForChange · normal · Updated 10/09/2026 20:41
Services: Planner
Read message
[What and why] We are introducing Custom Fields in Microsoft Planner, enabling users to tailor plans to match the way their teams work. Users can add Text, Number, Date, Yes/No, and Choice fields to capture information that matters to their workflows and manage that information across Board, Grid, and Task details. [Rollout schedule] General Availability (Worldwide): Rollout begins in late October 2026 and is expected to complete by early November 2026. [Impact on your organization] Who is affected Users with a Planner Premium P1, P3, or P5 license Users with a Microsoft 365 license Platforms and services Microsoft Planner What will happen Users with a Planner Premium P1, P3, or P5 license will be able to create, edit, and manage Custom Fields and their values. Users with a Microsoft 365 license can view Custom Fields and values as read-only and export them but cannot create or edit them. Users can add up to 10 custom fields with 255 characters each to tasks in a plan for information beyond Planner's built-in fields. Available types are Text, Number, Date, Yes/No, and Choice, and field names can be up to 255 characters. Choice fields are single-select and can contain 2 to 25 colored options. Field values can be viewed and updated across Board, Grid, and Task details and used for sorting, filtering, grouping, and bulk editing. This feature is optional. Existing plans are not affected unless users add Custom Fields. Existing compliance capabilities cover custom field data, including Unified Audit Log, eDiscovery, Microsoft Information Protection through inherited plan-level labels, and Data Lifecycle Management. [Action required and recommendations] No tenant-level configuration or admin setup is required to enable Custom Fields. We recommend that you: Ensure users who need to create or edit Custom Fields have a Planner Premium P1, P3, or P5 license. Microsoft 365 users will have read-only access. Inform users about the supported field types, the limit of 10 fields per plan, and that Choice fields are single-select with 2 to 25 options. Advise users that deleting a custom field or choice option is permanent and cannot be undone, and that deleting a choice option clears affected values. Remind users to follow your organization's data-handling policies. Custom field data is included in audit, eDiscovery, Microsoft Information Protection, and data lifecycle processes. [Learn more] We will update this post with new documentation. [Compliance considerations] Does the change store new customer data? Yes. Custom field names and values that users create on tasks (up to 10 fields per plan) are stored as part of plan/task data. Does the change alter how existing customer data is processed, stored, or accessed (e.g., documents, emails, chats, etc.)? No. Existing task and plan data is unchanged. Custom fields are additive metadata on tasks. Does the change modify, interrupt, or disable any of the following Microsoft Purview capabilities? Data Loss Prevention (DLP) policies or enforcementNo. Information Protection labels or sensitive information typesNo. Conditional Access policiesNo. Audit logging capabilitiesNo. Custom field edits are logged in Task History and flow to the Unified Audit Log. eDiscovery or Content SearchNo. Encryption methods or key managementNo. Data uses existing service encryption. Retention policies, holds, or deletion workflowsNo. Custom field data follows the existing task/plan lifecycle (deleted when the task/plan is deleted). Does the change alter how admins can monitor, report on, or demonstrate compliance activities (e.g., Purview or admin reporting)? No. Existing Purview and admin reporting continue to work; custom field activity appears in audit logs like other task edits. Does the change modify how users can access, export, delete, or correct their personal data within Microsoft 365 services (GDPR Data Subject Rights)? No. Users can view, edit, and export custom field values (Export to Excel), and the data is deleted along with the task or plan it belongs to. -
Microsoft Outlook: Themes by Copilot retirement
MC1492954 · planForChange · normal · Updated 10/09/2026 20:40
Services: Exchange Online
Read message
[What and why] We are retiring Themes by Copilot in Microsoft Outlook. Themes by Copilot currently allows users with a Copilot license to create and apply a Copilot-generated theme in Settings. As part of this change, Themes by Copilot will be removed from Settings, and users will no longer be able to select or return to a Theme by Copilot after changing to a different theme. [Rollout schedule] General Availability (Worldwide): Retirement begins in mid-October 2026 and is expected to complete by late October 2026. [Impact on your organization] Who is affected Users with a Copilot license. Platforms and services New Outlook for Windows Outlook for Android Outlook for iOS Outlook for Mac Outlook on the web What will happen Themes by Copilot will be removed from Settings. Users who are currently using a Theme by Copilot will retain their current theme until they change it. Themes by Copilot configured to automatically refresh will remain applied but will stop refreshing. Users will retain the current theme imagery until they change their theme. Users can change from their existing Theme by Copilot to a non-Copilot theme but cannot return to a Theme by Copilot after doing so. [Action required and recommendations] No action is required. -
(Updated) Microsoft Teams: PowerPoint Live introduces light mode for presenters
MC1462473 · stayInformed · normal · Updated 10/09/2026 19:24
Services: Microsoft Teams
Read message
Updated October 9, 2026: We have updated the timeline. Thank you for your patience. [What and why] We're improving the PowerPoint Live presenting experience in Microsoft Teams by introducing a new light mode option. With this update, presenters can choose from light, dark, classic, or high contrast modes while presenting. This enhancement provides greater flexibility, accessibility, and personalization, allowing presenters to use the display mode that best matches their preferences and working environment. This message is associated with Microsoft 365 Roadmap ID 567469. [Rollout schedule] Targeted release: Beginning in early September 2026 and expected to complete by late October 2026 (previously early September) General Availability (Worldwide, GCC, GCC High, DoD): Beginning in early September 2026 and expected to complete by late November 2026 (previously late October) [Impact on your organization] Who is affected Users who present PowerPoint content using PowerPoint Live in Microsoft Teams. Platforms and services Microsoft Teams PowerPoint Live What will happen Presenters will be able to select from the following display modes when using PowerPoint Live: Light mode Dark mode Classic mode High contrast mode Users can choose the mode that best aligns with their preferences and accessibility needs. This change enhances the presenting experience and does not alter presentation content or attendee viewing experiences. [Action required and recommendations] No admin action is required. Consider informing users who regularly present in Teams meetings about the new display mode options. [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
30-Day Reminder: Windows 11, version 23H2 Enterprise and Education editions reach end of updates on November 10, 2026
MC1492825 · stayInformed · normal · Updated 10/09/2026 17:07
Services: Windows
Read message
On November 10, 2026, Windows 11, version 23H2 Enterprise and Education editions will reach end of updates. The November 2026 Windows security update will be the last update available for these editions. After this date, devices running these editions will no longer receive monthly security updates containing protections from the latest security threats. We recommend updating eligible devices running Windows 11, version 23H2 to a supported version of Windows 11. If you have an eligible device, you can check if an update to a supported version of Windows is available by selecting Settings > Windows Update and selecting Check for updates. If your device is ready for the update, you’ll see the option to Download and install. For more information about product lifecycle dates, see Windows 11 release information and Lifecycle FAQ - Windows. -
Dynamics 365 Contact Center - Improved feature discoverability within Contact Center Admin Center
MC1492276 · stayInformed · normal · Updated 10/09/2026 04:05
Services: Dynamics 365 Apps
Read message
We are announcing improvements for discovering the latest features and news about capabilities in Dynamics 365 Contact Center. This feature will reach public preview on October 23, 2026. How does this affect me? With these discoverability improvements, administrators can more easily discover what's new, understand the value of key capabilities, and take the next step toward adoption. This feature connects administrators to relevant learning and adoption resources with two new experiences: A What's New section will showcase new features in Copilot Service admin center. A Did You Know section will highlight timely product updates, announcements, events, and other relevant information. What action do I need to take? This message is for awareness, and no action is required. -
Microsoft API Hub: Zendesk OAuth tokens will require expiration and automatic refresh
MC1492163 · stayInformed · normal · Updated 10/08/2026 23:12
Services: Power Apps in Microsoft 365, Microsoft Power Automate in Microsoft 365
Read message
[What and why] To align with updated Zendesk security requirements, Microsoft API Hub is changing how OAuth tokens are issued and managed for Zendesk connections. New Zendesk connections and existing connections that are reauthorized after rollout will receive access tokens that expire after 48 hours, refresh tokens that expire after 90 days, and automatic token refresh support. [Rollout schedule] General Availability (Worldwide): Beginning in early October 2026 and expected to complete by late January 2027 [Impact on your organization] Who is affected Organizations using Zendesk OAuth connections in Microsoft API Hub Developers who manage Zendesk connections and affected flows Platforms and services Microsoft API Hub Zendesk integrations and connected workflows What will happen New Zendesk connections will receive access tokens with a 48-hour lifetime, refresh tokens with a 90-day lifetime, and automatic token refresh support. Existing Zendesk connections created before this change cannot be automatically migrated to the new token model. Existing connections must be reauthorized to receive expiring tokens and automatic refresh support. Active new or reauthorized connections should refresh automatically. Connections that remain unused for 90 days may lose refresh capability and require reauthorization when they are used again. Flows that rely on existing Zendesk connections may fail until those connections are reauthorized. [Action required and recommendations] Action is required for existing Zendesk connections created before this change. Identify existing Zendesk connections that require reauthorization. Reauthorize those connections to receive expiring tokens and automatic refresh support. Inform developers who manage Zendesk connections and affected workflows about this change. Review affected flows that depend on existing Zendesk connections. Learn more Zendesk - Connectors | Microsoft Learn [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
Microsoft PowerPoint for Windows: Smarter Keep Source Formatting slide pasting experience
MC1492156 · stayInformed · normal · Updated 10/08/2026 23:09
Services: Microsoft 365 apps
Read message
[What and why] We're improving the PowerPoint Keep Source Formatting paste experience. When users paste slides using Keep Source Formatting, PowerPoint will now import only the slide masters and layouts required for the pasted slides instead of importing all slide masters and layouts from the source presentation. This change helps reduce presentation file size, improve performance when opening large presentations, and enhance collaboration experiences such as co-authoring by minimizing unnecessary design content in presentations. Users who prefer the previous behavior can continue using it through a setting that allows them to choose their preferred slide paste experience. [Rollout schedule] General Availability (Worldwide): Rollout began in late September 2026 and is expected to complete by late October 2026. [Impact on your organization] Who is affected Users of Microsoft PowerPoint for Windows who paste slides using the Keep Source Formatting option. Platforms and services Microsoft PowerPoint for Windows What will happen When users paste slides with Keep Source Formatting, PowerPoint will import only the slide masters and layouts required by the pasted slides. Presentation file sizes may be reduced because unnecessary slide masters and layouts will no longer be imported by default. By minimizing unnecessary design content, smaller presentations may open faster and perform better during collaboration and co-authoring scenarios. Users who prefer the previous behavior can continue using it through a setting that allows them to bring over all slide masters and layouts from the source presentation. [Action required and recommendations] No action is required. [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
Microsoft PowerPoint for Mac: Smarter Keep Source Formatting slide pasting experience
MC1492155 · stayInformed · normal · Updated 10/08/2026 23:08
Services: Microsoft 365 apps
Read message
[What and why] We're improving the PowerPoint Keep Source Formatting paste experience. When users paste slides using Keep Source Formatting, PowerPoint will now import only the slide masters and layouts required for the pasted slides instead of importing all slide masters and layouts from the source presentation. This change helps reduce presentation file size, improve performance when opening large presentations, and enhance collaboration experiences such as co-authoring by minimizing unnecessary design content in presentations. Users who prefer the previous behavior can continue using it through a setting that allows them to choose their preferred slide paste experience. [Rollout schedule] General Availability (Worldwide): Rollout began in late September 2026 and is expected to complete by late October 2026. [Impact on your organization] Who is affected Users of Microsoft PowerPoint for Mac who paste slides using the Keep Source Formatting option. Platforms and services Microsoft PowerPoint for Mac What will happen When users paste slides with Keep Source Formatting, PowerPoint will import only the slide masters and layouts required by the pasted slides. Presentation file sizes may be reduced because unnecessary slide masters and layouts will no longer be imported by default. By minimizing unnecessary design content, smaller presentations may open faster and perform better during collaboration and co-authoring scenarios. Users who prefer the previous behavior can continue using it through a setting that allows them to bring over all slide masters and layouts from the source presentation. [Action required and recommendations] No action is required. [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
(Updated) Allow connections to copilot.cloud.microsoft before the Copilot URL redirect
MC1462915 · planForChange · normal · Updated 10/08/2026 18:57
Services: Microsoft 365 Copilot Chat
Read message
Updated October 8, 2026: We have updated the content. thank you for your patience. [What and why:] As communicated in MC1454108, beginning in early September, 2026, Microsoft will start redirecting users from m365.cloud.microsoft to copilot.cloud.microsoft in organizations where access to copilot.cloud.microsoft is available. Organizations who may have blocked connection to copilot.cloud.microsoft will be redirected in October. Backend services and Copilot in Edge will require connection to *.cloud.microsoft. To avoid disruption to Copilot access across the web app, desktop app, and Edge experience, review your organization's network and security controls to confirm that users can connect to *.cloud.microsoft. [Rollout schedule:] In early September, 2026, Microsoft will redirect users from m365.cloud.microsoft to copilot.cloud.microsoft in organizations where access to copilot.cloud.microsoft is available. In early November, 2026 Microsoft will redirect the remaining users who had not been redirected in early September. If your organization cannot complete the required configuration before the redirect, contact your Microsoft account representative to discuss available options. [Impact on your organization:] When the Copilot web app transitions from m365.cloud.microsoft to copilot.cloud.microsoft, users will be automatically redirected. If device, network, proxy, firewall, security gateway, or similar controls block URLs within *.cloud.microsoft, affected users may be unable to use Copilot in the web app, desktop app, and Microsoft Edge experience. Review these controls and allow the required domain before the redirect begins. The redirect remains within the *.cloud.microsoft domain and retains its security, compliance, and enterprise allow-listing properties. Organizations that follow the recommendednetwork configurations for Microsoft 365 Copilot do not need additional network changes. [Action required / Recommendations:] You can validate connectivity to the *.cloud.microsoft domain by using the Microsoft 365 Connectivity Test tool. Use the connectivity tool to validate connectivity to *.cloud.microsoft and confirm that your network and security controls allow access before the redirect applies to your organization. If you find out your organization blocks connection to *.cloud.microsoft, contact your Microsoft account representative before September 10, 2026 to discuss available options. Confirm that copilot.cloud.microsoft is not blocked in your environment. Review legacy filtering rules, URL category restrictions, proxy policies, firewall rules, tenant restrictions, Conditional Access policies, and app control policies, and update them if needed. Add *.cloud.microsoft to your organization’s allow lists. If you have questions about tenant-specific network configurations and allow list requirements, you can contact your Microsoft support team for guidance based on your specific environment. Note: Microsoft does not support allowing partial or only selected Microsoft 365 application URLs within the *.cloud.microsoft domain. Allow the entire *.cloud.microsoft domain to maintain service reliability and avoid disruptions. Confirm that your environment aligns with the recommended network requirements for Microsoft 365 Copilot. Coordinate with teams that manage network security, proxy services, firewalls, secure web gateways, SSE/SASE platforms, or third-party filtering solutions to ensure traffic to *.cloud.microsoft is permitted. If preventing personal Microsoft account sign-ins is the reason your organization blocks copilot.cloud.microsoft, consider using TenantRestrictions as the targeted control. This control allows your organization to restrict authentication with personal Microsoft accounts on managed networks or devices, while still permitting access to the Copilot service URL. -
Prepare for Windows Update certificate rotation in 2027
MC1491763 · stayInformed · normal · Updated 10/08/2026 17:15
Services: Windows
Read message
What and why Certificates that help devices establish trusted connections to Windows Update will expire on May 17, 2027, and June 19, 2027. Devices must contain the replacement certificates to continue connecting to Windows Update and receiving updates after the applicable expiration date. Microsoft has delivered the replacement certificates through Windows security updates. Most devices running an in-support version of Windows require no additional action if they are current with monthly Windows updates. Rollout schedule The applicable certificates expire on May 17, 2027, and June 19, 2027. Required actions vary by Windows version. Impact on your organization Supported and updated devices will continue receiving updates without interruption. Supported devices need to be up to date to continue accessing Windows Update services after the applicable expiration date. Devices running unsupported versions of Windows will lose access to Windows Update services and will not receive updates as a result. This change does not apply to devices receiving updates from Windows Server Update Services (WSUS). Action required/recommendations Identify devices that require action and update or upgrade them before the relevant expiration date: Windows 11, version 25H2 and later: No action is required. Windows 11, version 24H2 and Windows Server 2025: Install the September 2025 security update or a later update before June 19, 2027. Other in-support versions of Windows 11 and Windows Server 2022: Install the July 2026 security update or a later update before June 19, 2027. In-support versions of Windows 10: Install the July 2026 security update or a later update before June 19, 2027. Windows 10 Enterprise 2019 LTSC, Windows Server 2019, and Windows Server 2016: Install the July 2026 security update or a later update before May 17, 2027. Other Windows versions: Upgrade devices to a supported version of Windows client or Windows Server. If a supported device is not current after the applicable expiration date, obtain the required update from the Microsoft Update Catalog or distribute it through your regular management tools. Review the following resources: Prepare for Windows Update certificate rotation in 2027. Share your feedback in this discussion board. Windows release health for release notes. Supported versions of Windows client and Windows Server release information for support status. Microsoft Update Catalog for guidance on obtaining required updates directly. Compliance considerations No compliance considerations are identified. Review as appropriate for your organization. -
Windows Office Hours: October 15, 2026
MC1491762 · stayInformed · normal · Updated 10/08/2026 17:15
Services: Windows
Read message
If you are an IT admin with questions about managing and updating Windows, we want to help. Every third Thursday of the month, we host a live chat-based event on the Tech Community called Windows Office Hours. Members of the Windows, Microsoft Intune, Windows Autopilot, Windows Autopatch, and Windows 365 engineering teams will be standing by to answer your questions. Want to attend the October 15 session of Office Hours? Add it to your calendar and select Attend on the event page to let us know you're coming. There is no video or live meeting component. Simply visit the event page, sign in to the Tech Community, and leave your questions in the Comments section. You can also bookmark https://aka.ms/Windows/OfficeHours for upcoming dates (and the ability to add this event to your calendar). We look forward to helping you. -
(Updated) Microsoft Entra ID: Passkey support for B2B users
MC1459133 · stayInformed · normal · Updated 10/08/2026 16:15
Services: Microsoft Entra
Read message
Updated October 8, 2026: We have updated the timeline. Thank you for your patience. [What and why] Microsoft Entra ID will support passkey registration and sign-in for B2B users, including internal guest users and external users. Eligible B2B users will be able to register and use passkeys issued by the resource tenant to satisfy that tenant's multifactor authentication (MFA) requirements. Passkeys are already supported for member users in their home tenant. Until now, B2B users could not use a resource tenant passkey when that tenant required MFA and did not trust the home tenant's MFA. This update closes that gap and gives guest and external users a phishing-resistant way to satisfy MFA requirements in the resource tenant. B2B users can register a resource tenant passkey from the resource tenant's My Security Info page, during a proof-up prompt, or through a passkey registration campaign. Once registered, the passkey can satisfy the resource tenant's MFA requirements during sign-in. Microsoft Authenticator app passkeys will be supported for internal guest users but not for external users. Important: This rollout intersects with the previously announced retirement of SMS and voice authentication. As described in Message Center posts MC1426371 and MC1434201, any user enabled for SMS or voice in the Authentication methods policy or legacy MFA policies will be automatically enabled for all passkey types. This will include eligible B2B users when B2B passkey support becomes available. [Rollout schedule] General Availability (GCC, Worldwide): Beginning in late October 2026, with a phased rollout as outlined below: Internal guest users: Beginning in late October 2026 (previously early October) and is expected to complete by late November 2026 (previously late October) External users (excluding Microsoft Authenticator app passkeys): Rollout timing will be communicated in a future Message center post update. [Impact on your organization] Who is affected Microsoft Entra administrators managing Authentication methods policies Organizations that use Microsoft Entra B2B collaboration Internal guest users and external users who are in scope for passkey authentication Internal guest users and external users who are enabled for SMS or voice in the Authentication methods policy or legacy MFA policies Platforms and services Microsoft Entra ID My Security Info Authentication methods policy Conditional Access What will happen The feature will be enabled by default. B2B users who are already in scope for passkeys in your Authentication methods policy will automatically be able to register and sign in with resource tenant passkeys. Eligible B2B users may receive prompts to register a passkey during sign-in through proof-up experiences or passkey registration campaigns, if those experiences are configured in your tenant. Users can also register a passkey from the resource tenant's My Security Info page. If your organization has excluded B2B users from passkeys in the Authentication methods policy, and those users are not separately subject to automatic passkey enablement through the SMS and voice retirement changes, they will not be prompted and will not be able to register or sign in with a resource tenant passkey. Under the SMS and voice retirement changes described in MC1426371 and MC1434201, B2B users who are enabled for SMS or voice in the Authentication methods policy or legacy MFA policies will be automatically enabled for all passkey types. Excluding these users from the passkey policy alone will not prevent this automatic enablement if they remain enabled for SMS or voice. This change gives guest and external users a phishing-resistant sign-in option and helps organizations extend strong authentication requirements to their B2B population. [Action required and recommendations] No action is required. We recommend that administrators review current passkey and MFA configurations before rollout: Review your Authentication methods policy. Confirm which users are in scope for passkeys, including guest and external users. B2B users who are in scope will be enabled automatically. Exclude them from the policy if that is not the intended behavior. Review Message Center posts MC1426371 and MC1434201 for details about the SMS and voice retirement changes. Review SMS and voice assignments in both the Authentication methods policy and legacy MFA policies. If you do not want specific B2B users to be automatically enabled for all passkey types, move those users off SMS and voice in all applicable policies. Excluding them only from the passkey policy is not sufficient while they remain enabled for SMS or voice. Review your passkey registration campaign. Confirm that the campaign's user scope includes the intended users. Review your Conditional Access policies. Confirm that MFA and authentication strength requirements will apply as intended for B2B users when resource tenant passkeys become available. Confirm user scoping across authentication-related policies. Make sure the groups and user types targeted by each policy align with your organization's requirements for guest and external users. Consider notifying your help desk and identity support teams that eligible B2B users may begin receiving passkey registration prompts after rollout. [Compliance considerations] QuestionAnswer Does the change store new customer data?Passkey credential registration data may be stored as part of Microsoft Entra authentication management. Does the change alter how existing customer data is processed, stored, or accessed?The change introduces an additional authentication method for B2B users accessing resource tenant resources. -
(Updated) Outlook for iOS and Android: Automatically apply email sensitivity labels from labeled attachments
MC1465780 · stayInformed · normal · Updated 10/07/2026 23:31
Services: Exchange Online, Microsoft Purview
Read message
Updated October 7, 2026: We have updated the timeline. Thank you for your patience. [What and Why:] We're introducing support for Microsoft Purview sensitivity label inheritance from attachments in Outlook for iOS and Android. When users attach files that have Microsoft Purview sensitivity labels applied, Outlook can automatically apply or recommend an email sensitivity label based on your organization's configured labeling policies. This enhancement helps organizations maintain consistent data classification and protection, reduces manual labeling effort for users, and supports compliance objectives across Outlook clients. [Rollout Schedule:] General Availability (Worldwide, GCC, GCC High, DoD): Mid-November 2026 (previously late September) [Impact on Your Organization:] Who is affected Organizations using Microsoft Purview sensitivity labels. Users of Outlook for iOS and Android. Platforms/Services Outlook for iOS Outlook for Android Microsoft Purview Information Protection What will happen When a user attaches one or more files that have sensitivity labels applied, Outlook may automatically apply or recommend an email sensitivity label. The applied or recommended label is determined by your organization's Microsoft Purview sensitivity labeling policies. This behavior helps align email classification with the classification of attached content. Users may experience fewer manual labeling steps when composing messages that contain labeled content. Organizations can benefit from more consistent application of information protection policies across mobile Outlook clients. [Action Required / Recommendations:] No admin action is required. Organizations currently using Microsoft Purview sensitivity labels should: Review existing label publishing policies. Review sensitivity label inheritance and protection configurations. Validate that attachment-based label inheritance aligns with compliance, regulatory, and information protection requirements. Update internal user guidance if your organization provides sensitivity labeling training or documentation. [Compliance Considerations:] IssueExplanation Microsoft Purview sensitivity labelsThis update extends sensitivity label behavior to Outlook for iOS and Android by enabling email labeling based on labeled attachments. Organizations should verify that existing labeling and protection policies produce the desired outcomes for email communications. For organizations already using Microsoft Purview sensitivity labels, this change helps improve consistency in classification and protection while reducing the risk of emails being sent with a lower sensitivity level than their attachments. -
(Updated) Create interactive slides in PowerPoint with Copilot skill (Windows and Mac)
MC1461152 · stayInformed · normal · Updated 10/07/2026 23:26
Services: Microsoft 365 apps
Read message
Updated October 7, 2026: We have updated the content and timeline. Thank you for your patience. [What and why:] We’re introducing the Copilot skill "Create interactive slide" in PowerPoint for Windows, Mac and web. This capability helps users create interactive, full-slide visuals that explain complex concepts, timelines, comparisons, systems, and data. Users can start creating interactive slides from the PowerPoint ribbon, on the Home and Insert tabs with the "Interactive Slide" button, and in Copilot chat in PowerPoint with the "Create Interactive Slide" skill. Attendees will be able to interact with slides created by the skill when viewing the slide in PowerPoint Live for Microsoft Teams. By making sophisticated visual communication easier to create directly in PowerPoint, this experience can help users communicate ideas more clearly and create engaging presentations with less manual effort. PowerPoint Live in Microsoft Teams: Each meeting participant can interact independently with slides created using the Create Interactive Slide skill. Interactions are not shared; attendees will see their own interactions, but not the presenter’s or other attendees’ interactions. Support for synchronizing presenter interactions across the meeting is planned as a future improvement. [Rollout schedule:] Frontier and Microsoft 365 Insider Beta channel Skill now available in PowerPoint for Windows, Mac and web. Ribbon Button in PowerPoint for Windows and Mac: By late September 2026 Skill and Ribbon Button in PowerPoint for the web: By early October 2026 Current channel (Preview) Skill and Ribbon Button in PowerPoint for Windows and Mac: By early October 2026 Worldwide Skill and ribbon button in PowerPoint for Windows, Mac and web: rollout will start in mid-October 2026 and is expected to complete by end of October 2026. Attendee interaction now available in PowerPoint Live in Microsoft Teams. [Impact on your organization:] Who is affected: PowerPoint for Windows, Mac and web users who have access to this capability. Platforms: PowerPoint for Windows, Mac and web. Interactive slides are interactive in PowerPoint for iPad and will appear as non-interactive images in PowerPoint for iPhone and Android. After the feature becomes available, eligible users will be able to use the Create interactive slide skill to produce or update full-slide visual experiences for scenarios such as: Explaining complex concepts. Presenting timelines. Comparing options or information. Illustrating systems and relationships. Communicating data visually. Organizations participating in the Microsoft Copilot Frontier program can evaluate the preview experience before general availability. Frontier capabilities are pre-release experiences and may change before reaching general availability. [Action required / recommendations:] No action is required before rollout. There are no admin settings for this capability. A Copilot license is required. We recommend that administrators: Review this information with presentation support, adoption, training, and help desk teams. Consider identifying Frontier participants who can evaluate the capability and provide feedback before general availability. Update internal PowerPoint guidance or training materials if your organization maintains standardized presentation-creation processes. Review the Microsoft Copilot Frontier program documentation: Get started with the Microsoft Copilot Frontier Program. -
Microsoft Teams: Call quality feedback surveys for Teams Rooms on Android
MC1490912 · stayInformed · normal · Updated 10/07/2026 22:37
Services: Microsoft Teams
Read message
[What and why] To help improve meeting experiences and provide organizations with insights into call quality, Microsoft Teams is introducing call quality feedback (CQF) surveys for Microsoft Teams Rooms on Android. These surveys allow users to rate the quality of calls and meetings and provide feedback about audio, video, and screen-sharing experiences. Customer feedback collected through these surveys helps Microsoft improve Teams meeting quality and reliability across devices and services. This message is associated with Microsoft 365 Roadmap ID 543713. [Rollout schedule] General Availability (Worldwide): Beginning in November 2026 [Impact on your organization] Who is affected Organizations using Microsoft Teams Rooms on Android devices. Users who participate in meetings on Teams Rooms on Android devices. Platforms/Services Microsoft Teams Microsoft Teams Rooms on Android Teams admin center (for device app updates) What will happen Users will periodically see a call quality feedback survey after meetings end on Teams Rooms on Android devices. Users can provide feedback on call quality, video quality, audio quality, and screen-sharing experiences. Feedback will be used by Microsoft to improve Teams products and services. The experience aligns with existing call quality surveys already available in Teams Rooms on Windows and other Teams clients. The feature becomes available after eligible Teams Rooms on Android devices are updated to the required app version. The feature is enabled by default once available. [Action required/Recommendations] No admin action is required before rollout. Recommended actions: Review how this change may affect meeting room experiences in your organization. Update Teams Rooms on Android devices to the latest supported application version through the Teams admin center. Inform users that they may be prompted to provide call quality feedback after meetings. Update internal training materials and support documentation as appropriate. Learn more Manage user feedback in Microsoft Teams - Microsoft Teams | Microsoft Learn [Compliance considerations] QuestionAnswer Does the change store new customer data?Yes. Users can submit call quality feedback through post-meeting surveys. The post does not specify storage location, retention, or storage duration. -
Microsoft Edge: Retiring legacy sign-in implementation on Windows
MC1490911 · planForChange · normal · Updated 10/07/2026 22:37
Services: Microsoft 365 suite
Read message
[What and Why:] Microsoft Edge is retiring its legacy direct-WAM sign-in implementation on Windows starting with Microsoft Edge version 157, completing the consolidation onto the OneAuth authentication library. This change standardizes authentication flows across Microsoft 365 client applications, simplifies platform supportability, eliminates dual-stack authentication code paths, and provides improved diagnostic and recovery mechanisms. Windows Web Account Manager (WAM) itself is not being deprecated; OneAuth continues to use Windows WAM. [Rollout Schedule:] General Availability (Worldwide, GCC): Rollout begins in early November 2026 and is expected to complete in early November 2026. [Impact on Your Organization:] Who is affected: Organizations using Microsoft Edge on Windows. Users with Edge profiles that have not yet automatically migrated to OneAuth. Organizations that explicitly disabled OneAuth WAM using --disable-features=msOneAuthWAM. Platforms/Services: Microsoft Edge on Windows Browser sign-in, identity, token fetch, Single Sign-On, and account synchronization experiences What will happen: Starting with Microsoft Edge version 157, all remaining profiles will transition directly to OneAuth authentication. The fallback legacy WAM path will default off under all circumstances. Most users will transition transparently. In rare cases, users may need to sign in to Microsoft Edge again. [Action Required/Recommendations:] We recommend that admins identify unmigrated profiles and test the transition before Microsoft Edge version 157 reaches their environment. Navigate to edge://signin-internals in Microsoft Edge. Under Edge Auth Library Information > Library, confirm whether the profile shows OneAuth or WAM. If OneAuth is displayed, the profile is already using the modern path and no action is required. If WAM is displayed, the profile is still using the legacy path. On pilot test devices running Microsoft Edge version 155 or later, admins can test the transition before version 157 by launching Edge with this force flag: msedge.exe --enable-features=msForceOneAuthWAM Verify that edge://signin-internals reflects OneAuth, and confirm that browser sign-in, Single Sign-On, and account synchronization work as expected. Inform support teams that a small number of users might see a sign-in action on the profile menu after updating to Edge version 157. If users experience sign-in issues, collect OneAuth logs with: msedge.exe --enable-features=msForceOneAuthWAM --enable-logging -v=1 --oneauth-log-level=5 Default log location: %LOCALAPPDATA%\Microsoft\Edge\User Data\chrome_debug.log [Compliance considerations:] Does the change include an admin control, and can it be controlled through Entra ID group membership?Admins can validate and manage the transition through Microsoft Edge configuration and feature flags. Review your Microsoft Edge deployment and policy management practices for group-based rollout controls. -
Microsoft Defender Vulnerability Management: Private preview for selected developer package vulnerability coverage
MC1490909 · planForChange · normal · Updated 10/07/2026 22:28
Services: Microsoft Defender XDR
Read message
[What and Why:] Microsoft Defender Vulnerability Management is expanding vulnerability coverage to selected Node.js, Python, and Java packages on supported Microsoft Defender for Endpoint-managed Windows devices. During this private preview, participating customers can identify supported vulnerable packages, affected devices, and detected versions through existing vulnerability investigation and recommendation workflows. Package data may also become available through supported API, export, and Advanced Hunting experiences as those preview paths are enabled. The expanded coverage can increase the number of records returned through assessment APIs and complete-file exports. For JSON assessment exports, customers can use supported server-side filters to limit the returned population. Complete-file exports include the full enabled population, so customers can filter the downloaded files by ProductCategory or use the Microsoft-provided legacy component support list to preserve their previous processing scope where needed. This preview provides curated coverage rather than a complete package inventory. Coverage varies by package, platform, collector, and product experience. It does not provide SBOM, dependency graphs, reachability analysis, package ownership, or complete ecosystem coverage. Participants will receive enablement guidance, known limitations, test scenarios, and a dedicated feedback channel. [Rollout Schedule:] General Availability (Worldwide): We will begin rolling out on late November 2026 and expect to complete by late December 2026. Public Preview (Worldwide): We will begin rolling out on late October 2026 and expect to complete by late November 2026. Targeted Release (Worldwide): We will begin rolling out on late September 2026 and expect to complete by late October 2026. [Impact on Your Organization:] This feature expands vulnerability management coverage in Microsoft Security Exposure Management (MSEM) to include CVE exposure for a curated set of Node.js, Python, and Java packages on supported Windows devices onboarded to Microsoft Defender for Endpoint. These package findings will appear within existing experiences for software components, vulnerabilities, affected devices, and security recommendations, helping security teams identify developer-package exposure alongside the software and vulnerability information they already use. For organizations that consume vulnerability data outside the portal, the expanded coverage may also affect assessment exports and downstream integrations. The preview introduces ProductCategory to help distinguish Applications, Components, and BIOS/firmware records, while JSON integrations can explicitly include the expanded component population. Complete-file exports for enabled tenants receive the full package population, so organizations should evaluate potential changes to file volume, ingestion, and downstream processing. The initial preview has defined coverage boundaries. It is limited to Windows, and areas such as package-native identity, dependency relationships, ownership, SBOM, VEX, reachability, and affectedness are not included. Advanced Hunting remains available, but ProductCategory support in the relevant tables may not be enabled during the initial preview phase. [Action Required/Recommendations:] Before enablement, admins should identify the people, integrations, and workflows that may be affected by the expanded package population. This includes JSON and complete-file assessment exports, Delta integrations, Advanced Hunting queries and custom detections where applicable, as well as API-based extraction, dashboards, BI, SIEM, ITSM, and data-lake ingestion. Organizations should also capture a baseline of relevant workflows, including current file sizes, ingestion and processing times, so they can compare behavior before and after activation. Admins should review each integration before opting in and validate that existing applications, components, queries, and downstream processes continue to behave as expected after enablement. For Delta integrations, a new baseline should be established when the included population changes. For complete-file exports, organizations that need to preserve their previous component population can use the Microsoft-provided Legacy Components Support List during ingestion. Finally, organizations participating in the preview need an approved environment and enablement window, along with named practitioner, integration, and rollback contacts. Microsoft enables the bounded package population for the approved environment, after which the organization should run its assigned scenarios and report unexpected endpoint, data, query, or processing behavior. [Compliance considerations:] No compliance considerations identified. Review as appropriate for your organization. -
Microsoft Defender for Office 365: Post-delivery protection for malicious QR codes in Microsoft Teams
MC1490905 · stayInformed · normal · Updated 10/07/2026 22:26
Services: Microsoft Defender XDR
Read message
[What and why] We're extending Microsoft Teams URL protection in Microsoft Defender for Office 365 to detect and respond to malicious URLs embedded in QR codes. As attackers increasingly use QR codes to conceal malicious destinations, this update helps protect users by analyzing URLs extracted from QR codes after message delivery and applying post-delivery protections when malicious content is identified. For organizations using Microsoft Defender for Office 365, this enhancement builds on existing Teams URL protection capabilities and improves visibility for security operations teams investigating QR-code-based threats. Security teams will also be able to identify QR code URL detections in Advanced Hunting through the MessageUrlInfo table. [Rollout schedule] General Availability (Worldwide): Beginning in early October 2026 and expected to complete by early November 2026 [Impact on your organization] Who is affected Organizations using Microsoft Teams with Microsoft Defender for Office 365 Organizations using Microsoft Teams Organizations licensed for Microsoft Defender for Office 365 Security operations teams that use Microsoft Defender XDR Advanced Hunting Organizations that have Zero-hour Auto Purge (ZAP) for Teams enabled can receive additional protection for eligible internal messages Platforms and services Microsoft Teams Microsoft Defender for Office 365 Microsoft Defender XDR Advanced Hunting What will happen Teams messages containing QR codes will be analyzed after message delivery. URLs extracted from QR codes will be evaluated for malicious content. When a malicious URL is identified in an external conversation, users will see a warning on the affected Teams message. When a malicious URL is identified in an internal conversation, users will see a warning on the affected Teams message. Organizations with Microsoft Defender for Office 365 Plan 1 or Plan 2 and Teams ZAP enabled may have eligible malicious internal messages blocked through existing post-delivery protection mechanisms. Security teams will gain visibility into QR code URL detections through Advanced Hunting. URLs extracted from QR codes will appear with QRCode in the UrlLocation column of the MessageUrlInfo table. The feature is enabled as part of existing Teams URL protection capabilities. No separate end-user configuration is required. Screenshot 1 - QR-code-blocking: Screenshot 2 - QR-warning-protection: Screenshot 3 - QR-Code Advanced Hunting: [Action required and recommendations] No action is required. We recommend that administrators: Review existing Microsoft Defender for Office 365 Teams protection settings and Teams ZAP configuration to understand how blocking behavior applies in your organization. Inform security operations teams that QR code URL detections will become available in Advanced Hunting. Review your incident investigation and threat hunting processes to incorporate QR code detections where applicable. Learn more Configure ZAP for Teams protection in Defender for Office 365 - Microsoft Defender for Office 365 | Microsoft Learn Zero-hour auto purge (ZAP) in Microsoft Teams - Zero-hour auto purge (ZAP) in Microsoft Defender for Office 365 - Microsoft Defender for Office 365 | Microsoft Learn [Compliance considerations] No compliance considerations identified, review as appropriate for your organization. -
Microsoft 365: Targeted Release retirement
MC1490899 · planForChange · normal · Updated 10/07/2026 22:22
Services: Exchange Online, Microsoft 365 suite, SharePoint Online, Microsoft OneDrive, Microsoft Teams
Action required by: 10/31/2026 07:00
Read message
[What and Why:] Targeted release for Microsoft 365 services will be retiring in January 2027 as Microsoft 365 transitions to three release options: Frontier, Standard release, and Deferred release. To prepare for this change, review users currently enrolled in Targeted release and configure the release preference that best meets your organization's needs. Choose your preferred release preference in the Microsoft 365 admin center: Preview accessFrontier: Opt in to preview eligible AI and non-AI features before general availability. General availability accessStandard release: Receive updates at general availability. Deferred release: Receive eligible major updates approximately 30 days after Standard release begins, allowing additional time for validation and readiness activities. In November 2026, administrators will no longer be able to add users to, remove users from, or modify Targeted release enrollments. Additional information about the related admin experience changes will be shared in a future Message center post. [Rollout Schedule:] Now: Review current release preferences and enroll users in Frontier, Standard release, or Deferred release if needed. November 2026: Targeted release enrollment changes are disabled. November 2026: Unified release preferences experience becomes available. Update your release preferences (Frontier, Standard release, Deferred release) in the unified release preferences experience. January 2027: Targeted release retires. Targeted release assignments are no longer used for Microsoft 365 feature delivery. [Impact on Your Organization:] Who is affected: Organizations with users or tenants enrolled in Microsoft 365 Targeted release. Administrators who manage Microsoft 365 release preferences. Platforms/Services: Microsoft 365 admin center Microsoft Teams Outlook (New) Outlook on the web Office for the Web Microsoft OneDrive SharePoint Online Some components of Exchange Online What will happen: In November 2026, administrators can no longer add, remove, or modify Targeted release assignments. In November 2026, administrators can configure Frontier, Standard release, and Deferred release preferences from a single unified release preferences experience in the Microsoft 365 admin center. Users currently assigned to Targeted release will continue receiving eligible Microsoft 365 features through existing Targeted release assignments until Targeted release is retired. Targeted Release retires in January 2027, and Targeted release will no longer used for Microsoft 365 feature delivery. After retirement, feature rollout timing follows your configured Frontier, Standard release, or Deferred release preference. [Action Required/Recommendations:] Before November 2026, administrators should complete the following actions: Identify and update users currently assigned to Targeted release before enrollment changes are disabled. In the Microsoft 365 admin center, go to Settings > Org settings > Organization profile > Release preferences. Evaluate and select the appropriate Standard release or Deferred release preference for your organization under Copilot > Settings > View all > Copilot Release preferences: General availability. Evaluate Frontier and, where appropriate, enroll eligible users who require early access to preview experiences under Copilot > Settings > View all > Copilot Frontier. Review the Learn documentation on Targeted release retirement for detailed transition guidance. Notify change management teams, support teams, security and compliance teams, pilot groups, and key IT stakeholders about the upcoming retirement and required transition actions. In November 2026, release preferences for Frontier, Standard release, and Deferred release can be managed through the unified release preferences experience in the Microsoft 365 admin center. Also, the current experience for managing Standard release and Deferred release preferences will be retired when the unified release preferences experience becomes available. Additional details about related admin experience changes will be shared in a future Message center post. [Additional Resources:] Configure new Standard and Deferred release options for Microsoft 365 Plan for the Retirement of Targeted Release in Microsoft 365 [Compliance considerations:] Does the change include an admin control, and can it be controlled through Entra ID group membership? Administrators will manage release preferences through the Microsoft 365 admin center and should evaluate user/group assignment needs for Frontier, Standard release, and Deferred release. Does the change alter how admins can monitor, report on, or demonstrate compliance activities? Organizations should update internal release-management and readiness processes because Targeted release assignments will no longer be used after retirement. -
(Updated) Microsoft 365: The Next Generation of File & Folder Sharing
MC1454378 · planForChange · normal · Updated 10/07/2026 22:11
Services: Microsoft 365 suite, SharePoint Online, Microsoft OneDrive, Microsoft 365 apps
Read message
Updated October 7, 2026: We have updated the timeline. Thank you for your patience. [What and why:] We're introducing the third-generation Microsoft 365 sharing experience to make collaboration simpler, smarter, and more secure by default. At the center of this update is a new hero link—a single sharing link that controls access to a file or folder. Users will see one consistent sharing experience whether they copy a link, share through email, or use the browser URL. The hero link consolidates sharing controls into a single link that can be updated after it has been shared, reducing the need to create and resend new links when access requirements change. [Rollout schedule:] General Availability (Worldwide, GCC, GCC High, DoD): Rolling out early October 2026 (previously mid-September) through end of November 2026 (previously late October) [Impact on your organization:] Who is affected: All users who share or manage files and folders in Microsoft 365. Platforms and services: SharePoint, OneDrive, and Microsoft 365 file-sharing experiences. What will happen: Every file and folder will have a single primary sharing link, called the hero link, displayed in the sharing dialog. The hero link settings determine who can access the item beyond people who are explicitly granted access. Adding people directly to a file or folder remains unchanged and continues to be the simplest way to share content. Screenshot - Add people screen when sharing By default, the hero link is set to Only people added to the file, meaning the link itself does not grant access to anyone. Screenshot - Share file view with hero link Users can broaden access to people in the organization with the link or, where permitted by organizational policy, to anyone with the link. Users can choose whether recipients can view, edit, or view without downloading, depending on available permissions. Changing the audience for the hero link updates the existing link rather than creating a new one. If recipients cannot open a previously shared file, the sender can expand access on the same hero link without redistributing a new URL. Existing sharing links will continue to function and will appear under Other links in the sharing dialog. Effective access remains the most permissive combination of direct permissions, inherited permissions, group-based permissions, and link-based permissions. Users will see a tutorial experience upon opening the new share dialog for the first time. [Action required/Recommendations:] No action is required before rollout. Organizations should consider the following preparation activities: Review internal sharing guidance and end-user documentation to reflect the new single-link sharing model. Communicate the updated sharing experience to users who regularly collaborate across teams and organizations. Evaluate site-level default sharing settings where different sharing behaviors are required. Learn more: Walkthrough Video: https://www.youtube.com/watch?v=3RpE0KrQmcA&t=4s Announcement Blog: https://techcommunity.microsoft.com/blog/onedriveblog/simple-smart-and-secure-the-next-step-in-sharing-files-in-microsoft-365/4411655 Admin controls Administrators can configure the default audience for the hero link at the SharePoint site collection or OneDrive level by using the DefaultMainLinkScope parameter in SharePoint PowerShell. Supported values are:OnlyPeopleAdded (default) Organization There is currently no tenant-wide equivalent setting for the hero link audience. DefaultMainLinkScope controls only the default audience and does not prevent users from broadening access when allowed by policy. Hero links start with view permissions by default. Existing default sharing link settings and link expiration policies continue to apply to legacy links and do not govern hero links. [Compliance considerations:] No compliance considerations identified, review as appropriate for your organization. -
Interim guidance for Manitoba time zone changes
MC1490598 · stayInformed · normal · Updated 10/07/2026 18:10
Services: Windows
Read message
What and why: A time zone change affects Windows devices in Manitoba, with Windows releasing a fix in October 2026. Manitoba is permanently moving to UTC-5 and will not set its clocks back on November 1, 2026. Microsoft recommends a temporary workaround for devices that can't be updated in time. For the workaround steps and full guidance, visit the Daylight Saving Time & Time Zone Blog. Rollout schedule: October 2026 – The Manitoba time zone will be included with the October 2026 Windows security update for all supported versions of Windows, including Windows Server. November 1, 2026 – The Manitoba time zone transition takes effect. Impact on your organization: In Manitoba, existing time zones remain correct until November 1, 2026; after that date, devices will show an incorrect time until the update is installed. The update adds a new time zone, (UTC-05:00) Manitoba. Devices that set their time zone automatically will select the new time zone on their own; on other devices, users must select it manually. Action required/recommendations: Install the update on affected devices in Manitoba before November 1, 2026. If you can't install it in time, read and follow the interim guidance, listed in Additional information. Compliance considerations: No compliance considerations are identified. Review as appropriate for your organization. Additional information: Daylight Saving Time & Time Zone Blog Interim guidance for Manitoba permanent DST 2026 How Windows manages time zone changes Daylight saving time help and support -
(Updated) Spell check before sending emails in new Outlook
MC1479509 · planForChange · normal · Updated 10/06/2026 23:44
Services: Exchange Online
Read message
Updated October 6, 2026: We have updated the content. Thank you for your patience. [What and Why:] If you don’t want to check spelling manually for every message—or you’re worried you might forget!—you can set Outlook to check spelling for you every time before sending emails. [Rollout Schedule:] General Availability (Worldwide): We will begin rolling out on mid-November 2026 and expect to complete by early December 2026. Targeted Release (Worldwide): We will begin rolling out on mid-October 2026 and expect to complete by late October 2026. General Availability (GCC, GCC High, DoD): We will begin rolling out on mid-November 2026 and expect to complete by mid-December 2026. [Impact on Your Organization:] Who is affected: Users of new Outlook for Windows and Outlook on the web. Help desk and training teams that support Outlook messaging experiences. Platforms/Services: Exchange Online. New Outlook for Windows and Outlook on the web. What will happen: Users can configure Outlook to check spelling automatically before sending email. This can help reduce spelling mistakes in sent messages without requiring users to manually start spell check for each message. The capability will roll out automatically during the scheduled rollout window. This feature requires Connected Experiences to be enabled. Users who have Connected Experiences disabled will not be able to use automatic spell checking before sending email. [Action Required/Recommendations:] Confirm that your organization’s privacy policies allow the use of connected experiences in Office. Inform users that they can enable spell check before sending if they want Outlook to review spelling automatically. Update internal Outlook training or help desk guidance if it describes message composition settings. [Compliance considerations:] This feature requires Connected Experiences in Office. Review as appropriate for your organization. -
(Updated) Microsoft OneDrive: New pay-as-you-go storage billing option
MC1477185 · planForChange · normal · Updated 10/06/2026 22:11
Services: Microsoft OneDrive
Read message
Updated October 6, 2026: We are no longer releasing to gov clouds at this time. We will communicate via a separate Message center post at a later date once we are ready to proceed with gov cloud release. If you are in a gov cloud, you can safely disregard this message. Thank you for your patience. [What and why] We are introducing a pay-as-you-go, consumption-based billing option for additional OneDrive storage. This capability gives administrators more flexibility to manage storage growth by allowing selected OneDrive accounts to exceed their licensed storage quotas when needed, while helping organizations control which users can consume additional storage beyond their licensed storage quotas. Pay-as-you-go storage is currently in public preview for commercial tenants. [Rollout schedule] Public Preview (Worldwide): The public preview of this feature is available now to all commercial tenants. General Availability (Worldwide): Rollout begins in early November 2026 and is expected to complete by early December 2026. [Impact on your organization] Who is affected Microsoft 365 commercial tenant administrators who manage OneDrive storage. Organizations with OneDrive users approaching or exceeding their licensed storage quotas. Platforms and services OneDrive Microsoft 365 admin and storage management experiences What will happen Administrators will be able to control which accounts are enabled to use a pay-as-you-go model to provide additional OneDrive storage beyond their licensed storage quotas. Accounts enabled for storage consumption above their licensed storage quotas will be billed automatically based on usage. [Action required and recommendations] No action is required if you do not wish to use pay-as-you-go storage for your organization. We recommend that you: Identify OneDrive accounts approaching or exceeding their licensed storage quotas. Evaluate whether pay-as-you-go storage is appropriate for your organization. [Learn more] Buy More OneDrive and SharePoint Storage Capacity | Microsoft Learn [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
(Updated) Connected Platforms - Agent 365 extends observability to third-party agents
MC1480873 · planForChange · normal · Updated 10/06/2026 19:56
Services: Microsoft 365 suite
Read message
Updated October 6, 2026: We have updated the timeline and content. Thank you for your patience. [What and Why:] Microsoft will roll out third-party agent observability in Microsoft Agent 365 to tenants. This lets you monitor the agents you sync from Amazon Bedrock, Google Vertex AI, and Anthropic Claude through Connected platforms in the same place as your Microsoft agents. Administrators can see runs, sessions, tool calls, and exceptions on each agent’s Activity tab. The result: a more consistent way to understand agent usage and investigate issues across supported platforms without treating every environment as a separate monitoring exercise. [Rollout Schedule:] Public Preview (Worldwide): We will begin rolling out on late October 2026 (previously late September) and expect to complete by late October 2026 (previously late September). General Availability (Worldwide): We will begin rolling out late November 2026 (previously late October) and expect to complete by late November 2026. [Impact on Your Organization:] Who is affected Administrators using Microsoft Agent 365 and Connected platforms Organizations synchronizing agents from Amazon Bedrock Classic, Amazon Bedrock AgentCore, Google Vertex AI, or Anthropic Claude Managed Agents (preview) Platforms/Services Microsoft Agent 365 Connected platforms Amazon Bedrock Classic Amazon Bedrock AgentCore Google Vertex AI Anthropic Claude Managed Agents (preview) What will happen Agent 365 can collect observability data from supported third-party agent platforms. Collected activity appears on each synchronized agent's Activity tab. Runs, sessions, tool calls, and exceptions are mapped to the Agent 365 observability model. Existing connections continue syncing agents as they do today. Collection remains disabled for existing connections until an administrator enables it. A new Collect agent observability data setting is available when creating or editing a supported connection. The setting is enabled by default for new connections. Agent 365 reads activity using existing connection credentials and does not execute agents. Third-party providers may charge for tracing, storage, logging, or query services. The Users metric is unavailable for synchronized third-party agents because Microsoft Entra identities are not provided by supported platforms. [Action Required/Recommendations:] No action is required for existing connections. Enable Collect agent observability data on existing connections if observability is desired. Validate source platform permissions and telemetry configuration. Clear the Collect agent observability data option during setup if collection is not desired for a new connection. Platform Requirements Amazon Bedrock Classic: Enable trace capture to Amazon S3 and grant read access to the activity bucket. Amazon Bedrock AgentCore: Enable CloudWatch Transaction Search and grant access to query CloudWatch log groups. Google Vertex AI: Assign required BigQuery, Monitoring, and Cloud Trace roles; enable APIs; enable telemetry collection and Trace Analytics BigQuery export. Anthropic Claude Managed Agents (preview): No additional setup required. [Compliance considerations:] Does the change introduce or significantly modify AI/ML or agent capabilities that interact with or provide access to customer data?Yes. The feature uses AI/ML or agent capabilities with Microsoft 365 content, prompts, or service data as described in this message. Does the change introduce or significantly modify any capability that enables users to automate workflows through AI or bot agents?Yes. The feature introduces or updates agent-related AI capabilities as described in this message. Does the change include an admin control and, can it be controlled through Entra ID group membership?Yes. The feature includes or affects admin controls, policies, permissions, roles, authentication, or management settings as described in this message. Review the linked documentation or admin center controls for group-based configuration support. -
(Updated) [Outlook Mac] Purview Data Loss Prevention support for Calendar Events
MC1472022 · stayInformed · normal · Updated 10/06/2026 17:09
Services: Exchange Online, Microsoft Purview
Read message
Updated October 6, 2026: We have updated the timeline. Thank you for your patience. [What and why:] Outlook for Mac will support Microsoft Purview Data Loss Prevention \(DLP\) policies for calendar events. Organizations can detect and help prevent the sharing of sensitive information in meeting subjects, descriptions, and invite content through policy tips, user remediation, and policy enforcement. This provides consistent compliance protection across email and calendar experiences on Mac devices. [Rollout schedule:] General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out mid-November 2026 (previously late September) and expect to complete by mid-November 2026 (previously late September). [Impact on your organization:] This feature helps organizations extend Microsoft Purview Data Loss Prevention protections to calendar events created in Outlook for Mac. Users receive policy guidance before sending meeting invitations that contain sensitive information, helping reduce accidental data exposure and improve compliance. Organizations benefit from more consistent protection across email and calendar workflows while supporting regulatory and corporate data protection requirements. [Action required, Recommendations:] No administrator action is required to prepare for this feature. Existing Microsoft Purview Data Loss Prevention policies will automatically apply to supported calendar events in Outlook for Mac. Organizations with DLP policies already configured can benefit from expanded protection of calendar content without additional policy creation or client configuration. Administrators may choose to review existing DLP policies to ensure they align with their organization's compliance requirements. -
(Updated) [Outlook Mobile] Purview Data Loss Prevention support for Calendar Events
MC1472023 · stayInformed · normal · Updated 10/06/2026 17:06
Services: Exchange Online, Microsoft Purview
Read message
Updated October 6, 2026: We have updated the timeline. Thank you for your patience. [What and why:] Outlook for iOS and Android will support Microsoft Purview Data Loss Prevention \(DLP\) policies for calendar events. Organizations can detect and help prevent the sharing of sensitive information in meeting subjects, descriptions, and invite content through policy tips, user remediation, and policy enforcement. This provides consistent compliance protection across email and calendar experiences on mobile devices. [Rollout schedule:] General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out mid-November 2026 (previously late September) and expect to complete by mid-November 2026 (previously late September). [Impact on your organization:] This feature helps organizations extend Microsoft Purview Data Loss Prevention protections to calendar events created from Outlook for iOS and Android. Users receive policy guidance before sending meeting invitations that contain sensitive information, helping reduce accidental data exposure and improve compliance. Organizations benefit from more consistent protection across email and calendar workflows while supporting regulatory and corporate data protection requirements. [Action required / Recommendations:] No administrator action is required to prepare for this feature. Existing Microsoft Purview Data Loss Prevention policies will automatically apply to supported calendar events in Outlook for iOS and Android. Organizations with DLP policies already configured can benefit from expanded protection of calendar content without additional policy creation or client configuration. Administrators may choose to review existing DLP policies to ensure they align with their organization's compliance requirements. -
(Updated) [Outlook Mac] Purview DLP Wait-on-Send Support
MC1472019 · stayInformed · normal · Updated 10/06/2026 17:03
Services: Exchange Online, Microsoft Purview
Read message
Updated October 6, 2026: We have updated the timeline. Thank you for your patience. [What and why:] Outlook for Mac will support Microsoft Purview Data Loss Prevention \(DLP\) wait\-on\-send policies. Organizations can require a DLP evaluation before an email is sent and configure how long users must wait for policy evaluation to complete. This helps ensure sensitive information is inspected against organizational policies before messages leave the organization while providing administrators with flexible control over the user experience. [Rollout schedule:] General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out mid-November 2026 (previously late September) and expect to complete by mid-November 2026 (previously late September). [Impact on your organization:] This feature helps organizations reduce the risk of sensitive information being sent before Microsoft Purview DLP policies can be evaluated. Administrators can require users to wait for policy inspection and configure the maximum wait time based on organizational requirements. This improves policy enforcement and compliance while allowing organizations to balance security, performance, and user productivity. [Action required / Recommendations:] Administrators can review their existing Microsoft Purview Data Loss Prevention policies and determine whether wait-on-send enforcement is appropriate for their organization. To take advantage of this feature, administrators may enable and configure the desired wait period within supported DLP policies. No changes are required for organizations that do not plan to use wait-on-send enforcement. -
(Updated) [Outlook Mobile] Purview DLP Wait-on-Send Support
MC1472021 · stayInformed · normal · Updated 10/06/2026 17:01
Services: Exchange Online, Microsoft Purview
Read message
Updated October 6, 2026: We have updated the timeline. Thank you for your patience. [What and why:] Outlook for iOS and Android will support Microsoft Purview Data Loss Prevention \(DLP\) wait\-on\-send policies. Organizations can require a DLP evaluation before an email is sent and configure how long users must wait for policy evaluation to complete. This helps ensure sensitive information is inspected against organizational policies before messages leave the organization while providing administrators with flexible control over the user experience. [Rollout schedule:] General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out in mid-November 2026 (previously late September) and expect to complete by mid-November 2026 (previously late September). [Impact on your organization:] This feature helps organizations reduce the risk of sensitive information being sent before Microsoft Purview DLP policies can be evaluated. Administrators can require users to wait for policy inspection and configure the maximum wait time based on organizational requirements. This improves policy enforcement and compliance while allowing organizations to balance security, performance, and user productivity. [Action required / Recommendations:] Administrators can review their existing Microsoft Purview Data Loss Prevention policies and determine whether wait-on-send enforcement is appropriate for their organization. To take advantage of this feature, administrators may enable and configure the desired wait period within supported DLP policies. No changes are required for organizations that do not plan to use wait-on-send enforcement. -
(Updated) Outlook for Mac: Sensitivity label recommendations and auto-labeling from attachments
MC1465779 · stayInformed · normal · Updated 10/06/2026 16:58
Services: Exchange Online, Microsoft Purview
Read message
Updated October 6, 2026: We have updated the timeline. Thank you for your patience. [What and Why:] We're introducing support in Outlook for Mac that can automatically apply or recommend Microsoft Purview sensitivity labels based on the sensitivity labels assigned to attached files. This enhancement helps organizations apply more consistent information protection by aligning email sensitivity labels with the classification of attached content. By reducing the need for manual labeling, organizations can help lower the risk of misclassified communications and support compliance and data protection objectives. [Rollout Schedule:] General Availability (Worldwide, GCC, GCC High, DoD): Rollout will begin in mid-November 2026 (previously late September) and is expected to complete in mid-November 2026 (previously late September). [Impact on Your Organization:] Who is affected: Users who compose email messages in Outlook for Mac. Organizations that use Microsoft Purview sensitivity labels. Platforms and Services: Outlook for Mac Microsoft Purview Information Protection What will happen: When users attach files that already have Microsoft Purview sensitivity labels, Outlook for Mac can automatically apply or recommend an appropriate sensitivity label for the email message. Email classification can better align with the sensitivity of attached content. Depending on your organization's label policies, users may see sensitivity label recommendations or automatic label application while composing messages. This capability helps reduce manual labeling effort and promotes a more consistent information protection experience across Outlook clients. [Action Required / Recommendations:] No admin action is required. We recommend that organizations using Microsoft Purview sensitivity labels: Review existing sensitivity label publishing and protection policies. Validate that attachment-based label inheritance behavior aligns with organizational compliance and information protection requirements. Inform compliance, security, and support teams of the upcoming change so they can address user questions. [Compliance Considerations:] IssueExplanation Microsoft Purview labeling behaviorThis change affects how Microsoft Purview sensitivity labels may be applied or recommended for email messages based on the sensitivity labels of attached files. Information protection and compliance workflowsOrganizations should verify that automatic or recommended label inheritance aligns with their existing classification and protection requirements. -
(Updated) Microsoft Teams: Multi-line call history tabs in the Calls app
MC1484013 · stayInformed · normal · Updated 10/06/2026 16:27
Services: Microsoft Teams
Read message
Updated October 6, 2026: We have updated the timeline. Thank you for your patience. [What and why] Microsoft Teams is introducing a redesigned call history experience for Teams Phone users who have multi-line calling enabled. Call activity, including call history, voicemails, and recordings, will be organized by phone line in dedicated tabs within the Calls app. This change simplifies navigation for users who manage multiple phone lines. [Rollout schedule] Targeted Release: Beginning in early November 2026 (previously early October) and expected to complete by early November 2026 (previously early October) General Availability (Worldwide, GCC, GCC High, DoD): Beginning in early November 2026 and expected to complete by end of November 2026 (previously mid-November) [Impact on your organization] Who is affected Teams Phone users with multi-line calling enabled and multiple phone numbers assigned Users without multi-line calling enabled are not affected Platforms and services Microsoft Teams desktop for Windows Microsoft Teams desktop for Mac Microsoft Teams on the web Teams Phone What will happen A dedicated tab will be created in the Calls app for each assigned phone line. Call history will be displayed under the phone line associated with the activity. Voicemails will appear under the phone line where they were received. Call recordings will appear under the phone line associated with the call. Users will be able to view and manage activity separately for each phone line. The feature will be enabled automatically for eligible users with multi-line calling configured. No changes will occur for users who do not use multi-line calling. [Action required and recommendations] No action is required. We recommend that you: Notify your help desk and support teams about the updated Calls app experience. Inform affected users who manage multiple phone lines. Update internal documentation, training materials, and support content that references call history, voicemail, or recordings in the Teams Calls app. [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
Microsoft Excel: Excel canvas
MC1485411 · planForChange · normal · Updated 10/06/2026 16:02
Services: Microsoft 365 apps
Read message
[What and why] We are introducing Excel canvas, a new Copilot capability for Microsoft Excel. Excel canvas transforms workbook data into a polished report containing visualizations, metrics, and insights. Reports automatically refresh as the underlying workbook data changes, reflecting the latest information. Users can further refine and customize reports by interacting with Copilot using natural language. [Rollout schedule] General Availability (Worldwide): Rollout begins in mid-October 2026 and is expected to complete by the end of October 2026. [Impact on your organization] Who is affected Users with access to Copilot in Microsoft Excel. Platforms and services Microsoft Excel for Windows Microsoft Excel Online Microsoft 365 Copilot What will happen Users will be able to generate an interactive Copilot-created report from workbook data. Reports will combine key visualizations, metrics, and insights in a single view. Report content will automatically update when the underlying workbook data changes. Users will be able to modify and refine reports by interacting with Copilot using natural language. [Action required and recommendations] No action is required to prepare for this change. We recommend that you notify users about this new capability and update any internal training or adoption materials related to Copilot in Microsoft Excel. [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
(Updated) New Outlook for Windows becomes available for GCC High and DoD
MC1338816 · planForChange · normal · Updated 10/05/2026 23:46
Services: Exchange Online
Read message
Updated October 5, 2026: We are updating this post as a notification that this is now available. Thank you for your patience. [What and Why:] New Outlook for Windows will be available for U.S. Government clouds (GCC High and DoD sovereign environments). This milestone helps organizations move forward with adoption planning while maintaining administrative control. [Rollout Schedule:] Public Preview (GCC High and DoD): New Outlook will begin Public Preview July 30, 2026. General Availability (GCC High, DoD): We will begin rolling out on September 30, 2026 and expect to complete by late December 2026. General Availability (DoD): We will begin rolling out on September 30, 2026 and expect to complete by late December 2026. [Impact on Your Organization:] Who is affected: GCC High and DoD tenants Exchange and Outlook admins Platforms/Services: New Outlook for Windows What will happen: Existing users who continue to use classic Outlook for Windows are not affected. New Outlook for Windows becomes available for GCC High and DoD sovereign environments but remains OFF by default. New Outlook continues to be an opt-in experience. Users can choose to switch to the new experience and can revert back to classic Outlook at any time. This update does not change organization settings and will not automatically switch users from classic Outlook for Windows. Microsoft will provide at least 12 months’ notice before initiating any Microsoft-driven migration steps in managed environments. Learn more about how we are approaching our migration timeline: New Outlook for Windows: A Guide to Product Availability. General Availability status enables organizations to begin evaluating and planning adoption timelines for the new Outlook experience. A future announcement will provide General Availability details for additional sovereign cloud environments. [Action Required / Recommendations:] Administrative action is required to enable new Outlook for Windows in supported sovereign environments. The experience remains off by default. To enable new Outlook for Windows when it becomes available, set the appropriate registry key: Enable availability when ready: GCC High: HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\16.0\Outlook "NewOutlookForWindowsCloudType"=dword:00000003 DoD: HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\16.0\Outlook "NewOutlookForWindowsCloudType"=dword:00000004 Recommended actions: Control availability: Organizations retain control over new Outlook’s availability. Policies can be used to hide the toggle in classic Outlook for Windows, block new mailboxes from being added, or remove new Outlook from certain Windows builds. Refer to: Control the installation and use of new Outlook. Learn about policy management: Policies for new Outlook are managed through mailbox policies on the primary account, consistent with Outlook on the web. IT admins may choose to preconfigure an organization account as the primary account. Learn more: Policy Management – Deploy Office and Map Classic Outlook Policies to New Outlook. Prepare to manage updates: New Outlook introduces features through service-based flighting rather than build updates. Track new functionality using the Microsoft 365 Roadmap. Public Preview: Public Preview begins in July 2026 and provides an early look at new Outlook in U.S. Government environments. Set one of the registry keys listed above to access the Preview. Transition from COM to web add-ins: COM add-ins are not supported in new Outlook. Organizations should begin transitioning to web add-ins. Learn more: Migrate from COM to web add-ins. Plan for user migration: Microsoft will provide at least 12 months’ advance notice before Microsoft-driven migrations. Organizations are encouraged to plan and manage their own adoption timelines using the following resources: Adoption and migration resources: New Microsoft Outlook for Windows User training: Getting started with the new Outlook for Windows; Discover New Outlook for Windows – Training Admin documentation: Overview of the new Outlook for Windows We understand that some organizations may have specific requirements that prevent them from transitioning from classic Outlook at this time. New Outlook team welcomes feedback through the following channels: The Help tab in new Outlook for Windows (feedback must be enabled by tenant admin) Dialog boxes shown when a user reverts to classic Outlook Your Microsoft account team (for larger organizations) For detailed guidance: Please refer to: How to enable new Outlook for Windows Public Preview in DoD and GCC High Learn more: Feature comparison of the classic and new Outlook: New and classic Outlook for Windows feature comparison Resources to help with change management and enterprise adoption: New Microsoft Outlook for Windows [Compliance considerations:] Area Explanation Alteration of existing customer data processing New Outlook uses a service-based architecture aligned with Outlook on the web, which may change how policies are evaluated and applied compared to classic Outlook. Admin controls available Availability is controlled by registry keys and admin policies; the experience remains opt-in and OFF by default. User self-enable/disable Users can opt in to new Outlook when enabled by admin and revert back to classic Outlook at any time. -
(Updated) Microsoft Teams: Modernized Gallery view in Teams Rooms on Android
MC1446797 · stayInformed · normal · Updated 10/05/2026 22:03
Services: Microsoft Teams
Read message
Updated October 5, 2026: We have updated the timeline. Thank you for your patience. [What and why] We're introducing a modernized Gallery view experience for Microsoft Teams Rooms on Android. This update aligns the experience more closely with Teams Rooms on Windows by improving participant visibility, creating more consistent layouts, and providing additional meeting display controls for users and administrators. This message is associated with Microsoft 365 Roadmap ID 567468. [Rollout schedule] General Availability (Worldwide, GCC): Beginning in mid-August 2026 and is expected to complete by late October 2026 (previously mid-August) General Availability (GCC High and DoD): Beginning in early September 2026 and expected to complete in late October 2026 (previously late September) [Impact on your organization] Who is affected Organizations using Microsoft Teams Rooms on Android devices. Platforms and services Microsoft Teams Teams Rooms on Android What will happen Today, Teams Rooms on Android devices may display participants using a mix of aspect ratios and provide a different gallery experience than Teams Rooms on Windows. After this rollout: Gallery view will prioritize video participants on the meeting stage by default: Participant tiles will be displayed using more consistent aspect ratios, including 16:9, 4:3, and 1:1 layouts. Audio participants will be deprioritized when video participant prioritization is enabled, helping display more video participants on screen. Meeting participants will be able to:Hide the room self-preview video for a meeting. Display audio and video participants equally instead of prioritizing video participants. Gallery updates will be more stable, with reduced tile movement when active speakers are promoted to the meeting stage. Admin controls will be available through device settings and the Pro Management portal. [Action required and recommendations] No action is required before the rollout. Administrators can configure the default Gallery view behavior through local device settings and the Teams Rooms Pro Management portal. Communicate these visual changes to Teams Rooms users if your organization provides end-user training or adoption materials. Learn more Microsoft Teams Rooms (Android) | Microsoft Support [Compliance considerations] No compliance considerations identified. -
(Updated) Microsoft Teams: Emoji shortcuts expand to iOS and Android
MC1404321 · stayInformed · normal · Updated 10/05/2026 22:01
Services: Microsoft Teams
Read message
Updated October 5, 2026: We have updated the timeline. Thank you for your patience. [What and Why] We are bringing desktop-style emoji shortcuts to Microsoft Teams on iOS and Android. Users can insert emojis directly in the compose box by typing a keyword between colons (for example, :smile: → 😊). This update improves consistency across platforms and enhances user productivity by making emoji input faster and more intuitive on mobile devices. This message is associated with Microsoft 365 Roadmap ID 565370. [Rollout Schedule] Targeted Release (Worldwide): We began rolling out in early August 2026 (previously late March) and expect to complete by mid-August 2026 (previously early July). General Availability (Worldwide): We will begin rolling out in mid-August 2026 (previously early July) and expect to complete by early November 2026 (previously late August). General Availability (GCC): We will begin rolling out in mid-August 2026 (previously mid-July) and expect to complete by early November 2026 (previously early September). General Availability (GCC High): We will begin rolling out in late August 2026 (previously late July) and expect to complete by early November 2026 (previously mid-September). General Availability (DoD): We will begin rolling out in early September 2026 (previously early August) and expect to complete by early November 2026 (previously late September). [Impact on Your Organization] Who is affected: All Microsoft Teams users on iOS and Android devices Platforms/Services: Microsoft Teams (iOS and Android) What will happen: Users can open the emoji suggestion menu by typing : followed by at least two characters (e.g., :sm) Users can insert emojis by typing a full name between colons (e.g., :smile: → 🙂) Common emoticons such as :), :D, and :P automatically convert into emojis Lowercase emoticons (e.g., :d, :p) are also supported Emoji search supports fuzzy matching and mid-string search Custom emojis are supported Parenthesis () shortcuts continue to work and will be retired later in alignment with desktop The feature is enabled by default with no admin controls [Action Required / Recommendations] No action is required. To prepare your organization: Notify your help desk about the updated emoji shortcut experience. Update internal training or adoption materials to include emoji shortcuts triggered with :. Consider sharing a brief user communication highlighting the new mobile parity experience. Learn more: Send an emoji or GIF in Microsoft Teams Free | Microsoft Support Send an emoji, GIF, or sticker in Microsoft Teams | Microsoft Support [Compliance considerations] No compliance considerations identified, review as appropriate for your organization. -
(Updated) Outlook (new): Right-click to customize the classic ribbon
MC1485120 · stayInformed · normal · Updated 10/05/2026 19:11
Services: Exchange Online
Read message
Updated October 5, 2026: We have updated the content. Thank you for your patience. [What and why] We are updating the classic ribbon customization experience in New Outlook for Windows and Outlook on the Web. Users can now customize the classic ribbon by right-clicking the ribbon on the Home or View tab and selecting the Customize button. Users can then choose which commands and groups appear on the Home and View tabs and arrange them in their preferred order. [Rollout schedule] General Availability (Worldwide): Rollout began in late September 2026 and is expected to complete by mid-November 2026. [Impact on your organization] Who is affected Microsoft Outlook users Platforms and services New Outlook for Windows Microsoft Outlook on the web What will happen Users can customize the classic ribbon by right-clicking on the ribbon, selecting which commands and groups to display on the Home and View tabs, and arranging them as desired. Classic ribbon customization entry point Classic ribbon customization menu [Action required and recommendations] No action is required. [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
An updated version of the September 2026 Scan Cab is available
MC1486397 · preventOrFixIssue · normal · Updated 10/03/2026 01:32
Services: Windows
Read message
IMPORTANT: This notice is only relevant for environments where: Exchange Server Subscription Edition (SE) is used Scan Cab is used to check for update compliance The September 2026 Scan Cab was deployed before 6:30 PM PDT on October 2, 2026. What and why: An updated version of the September 2026 Scan Cab was made available at 6:30 PM PDT on October 2, 2026. This Scan Cab includes new metadata corresponding to new updates for Exchange Server. The new Microsoft update for Exchange Server released October 2, 2026, included additional protections to address CVE-2026-96940: Exchange Server Elevation of Privilege Vulnerability. See the additional information section of this message for details. Rollout schedule: The updated September 2026 Scan Cab was made available at 6:30 PM PDT on October 2, 2026. Who is affected: IT administrators who downloaded the Scan Cab before 6:30 PM PDT on October 2, 2026, should re-acquire and re-deploy it if the Scan Cab is used to assess updates for environments where Exchange Server is used. No action is required on environments where Scan Cab is not employed and do not have Exchange Server. However, please note that there might be non-Microsoft applications that utilize Scan Cab. Review the documentation for any software and update deployment tools that might be in use for your organization, to understand if this is applicable in your environment. What will happen: Administrators can re-deploy the updated Scan Cab via their usual processes. For detailed guidance, see the Additional information section below. Additional information: Updated Scan Cab: Download the new Scan Cab here CVE-2026-96940 - Microsoft Exchange Server Elevation of Privilege Vulnerability Exchange Team Blog: September 2026 V2 Exchange Server Security Updates KB5129955: Security update for Microsoft Exchange Server Subscription Edition Announcing a smaller WSUS Scan Cab - Microsoft Tech Community: Learn more about WSUS and the Scan Cab process Using WUA to Scan for Updates Offline - Win32 apps: Windows Update Agent (WUA) can be used to scan computers for security updates without connecting to Windows Update WSUS and the Catalog Site: The Catalog Site used by WSUS to import updates and drivers -
(Updated) Microsoft Viva Copilot Analytics launches new agent dashboard
MC1166852 · planForChange · normal · Updated 10/02/2026 23:35
Services: Microsoft Viva
Read message
Updated October 2, 2026: We have updated the timeline. Thank you for your patience. [Introduction] We’re introducing the Agent Dashboard, a new dashboard available as part of Copilot Analytics in Microsoft Viva. This dashboard provides visibility into key agent adoption trends and associated Copilot credit usage. It supports insights into agents used within Microsoft 365 Copilot, which may be: Built using Microsoft Copilot Studio, SharePoint, or the Microsoft 365 Agents Toolkit Built by employees, your organization, Microsoft, or Microsoft partners This release also enhances the Adoption tab of the Copilot Dashboard, allowing users to view agent insights directly and access the Agent Dashboard for deeper analysis. [When this will happen:] Public Preview (Worldwide): Begins rolling out in early February 2026 (previously January), expected to complete by mid-February 2026 (previously end of January). General Availability (Worldwide): Begins rolling out in February 2026 (previously late October), expected to complete February 2026 (previously early November). [How this affects your organization:] Who is affected: Leaders, delegates, adoption specialists, and administrators using Microsoft Viva Insights Tenants with at least 50 Microsoft 365 Copilot licenses assigned What will happen: A new Agent Dashboard will be available in Viva Insights under Copilot Analytics Users will find:Key adoption metrics with historical trends (up to 6 months):Number of active agents Number of active agent users Number of agent responses Copilot credits used Number of users using Copilot credits Percentage of Copilot users using agents Screenshot 1: Key adoption metrics with historical trends, including active agents, active users, agent responses, and Copilot credit usage. Monthly and weekly user retention trends, with comparison across groups Screenshot 2: Monthly and weekly user retention trends, with comparison across groups.Top agents based on the following, with the ability to dive deeper into specific agents:Active user count Agent responses Copilot credits consumed Screenshot 3: Agent highlights along with a table of top agents, each with active usage metrics and the ability to dive deeper. Screenshot 4: Individual agent deep dive page with key adoption metrics and trends over time. Minimum group size threshold must be met for agent activity insights. Learn more: Configure manager settings The Adoption tab of the Copilot Dashboard will also include:Contextual insights on how Copilot users are leveraging agents and credits Direct entry points to the Agent Dashboard Screenshot 5: Entry points to the Agent Dashboard from the Copilot Dashboard Adoption tab, including agent usage and Copilot credit usage insights. [What you can do to prepare:]Review and assess the impact for your organization Manage access to the Agent Dashboard using VFAM controls at user, group, and tenant levels (nested under Viva Insights Web app VFAM controls) Consider reviewing with your works council Update training and documentation as needed Additional details will be available on MS Learn once this functionality is released, in a separate Agent Dashboard section: Copilot Analytics introduction [Compliance considerations:] No compliance considerations identified, review as appropriate for your organization. -
Microsoft Purview |Unified Classification Management Experience
MC1486289 · stayInformed · normal · Updated 10/02/2026 22:20
Services: Microsoft Purview
Read message
[What and Why:] Microsoft Purview is introducing a unified Classification Management experience that brings classifier management into one consistent experience, helping admins discover and manage their organization's classifiers. This message is associated with Microsoft 365 Roadmap ID 570844 [Rollout Schedule:] General Availability (Worldwide): We will begin rolling out on mid November 2026 and expect to complete by late November 2026. Public Preview (Worldwide): We will begin rolling out on early October 2026 and expect to complete by mid October 2026. [Impact on Your Organization:] Admins will have a unified experience for discovering and managing classifiers in the Microsoft Purview portal, bringing sensitive information types, Exact Data Match classifiers, trainable classifiers, and document fingerprinting together in a consistent management experience. [Action Required/Recommendations:] Plan to review the unified Classifiers experience in the Microsoft Purview portal when it becomes available. Use the product tour and teaching bubbles to learn about the experience, then explore search, filters, and classifier details to find and understand the classifiers your organization uses. When creating a classifier, use the guidance in the creation experience to choose between sensitive information types (SITs), Exact Data Match (EDM), trainable classifiers, and document fingerprinting based on your scenario. [Picture1] [Compliance considerations:] Does the change include an admin control and, can it be controlled through Entra ID group membership?Yes. The feature includes or affects admin controls, policies, permissions, roles, authentication, or management settings as described in this message. Review the linked documentation or admin center controls for group-based configuration support. -
(Updated) Teams admin center device state rules and health alerts retire; use Teams Rooms Pro Management portal
MC1469551 · planForChange · normal · Updated 10/02/2026 16:19
Services: Microsoft Teams
Read message
Updated October 2, 2026: We have updated the timeline. Thank you for your patience. [What and why:] As part of the ongoing transition of Teams device management from the Microsoft Teams admin center (TAC) to the Teams Rooms Pro Management portal (PMP), we are retiring device health monitoring capabilities in TAC — specifically the Device state rule (Teams admin center > Notifications & alerts > Rules) and the device health alerts it generates. Going forward, device health monitoring for all Teams devices (MTR-A, Phones, Panels etc.) is delivered through the Teams Rooms Pro Management portal, which provides device health signals, monitoring, and incident management in a single unified portal. This is a continuation of the change previously communicated in MC1227622, where Android device management capabilities including inventory, updates, health monitoring, and settings transitioned from TAC to PMP. [Rollout schedule:] General Availability (Worldwide, GCC): We will begin rolling out late October 2026 (previously late September) and expect to complete by late October 2026 (previously late September). [Impact on your organization:] Who is affected: Admins who currently use the Device state rule in the Teams admin center to monitor Teams device health, and anyone who receives the resulting offline-device alerts in Teams or via webhook. What will happen: The Device state rule page under Notifications & alerts > Rules in the Teams admin center will no longer be available, and existing rule configurations will stop being evaluated. Device offline / health alerts will stop being delivered to the Admin Alerts and Notifications team's MonitoringAlerts channel. Any webhook integrations configured against the Device state rule will stop receiving the alert payload. Existing rule configurations and historical alerts in TAC will not be migrated to the Pro Management portal. What replaces it: Device health signals, monitoring, and incident management are available for all Teams device types in the Teams Rooms Pro Management portal, with alerting and notification configured in the portal. There is no change to the health data collected from devices — only to where it is surfaced and how alerts needs to be configured by admins. There is no change to end users. This affects admin monitoring workflows only. [Action required / Recommendations:] Review your existing Device state rule configuration in the Teams admin center (Notifications & alerts > Rules > Device state rule) and record which devices and device users are currently monitored. Identify any webhook integrations. If you send the Device state rule payload to an external system (ITSM, ticketing, monitoring dashboard, custom workflow), plan the equivalent integration from the Pro Management portal before the retirement date. Set up health monitoring and alert notifications in the Pro Management portal for your device fleet, and validate you're receiving alerts for same. Monitor the transition article for feature-specific updates and timelines: Transitioning Teams Android Device Management from Teams Admin Center to the Teams Rooms Pro Management Portal [Compliance considerations:] No compliance considerations identified; review as appropriate for your organization. -
Microsoft Exchange Online: Exchange Web Services (EWS) enforcement update for EWSAllowedAppIDs
MC1485116 · stayInformed · normal · Updated 10/01/2026 22:54
Services: Exchange Online
Read message
[What and why] As previously communicated in MC1466860 and MC1447678, Microsoft is continuing the retirement of Exchange Web Services (EWS) in Exchange Online. Beginning October 10, 2026, setting EWSEnabled=True will no longer be sufficient to allow EWS access for affected Worldwide tenants. Organizations that require EWS must configure EWSAllowedAppIDs to specify which applications are permitted to access EWS. This change is part of the final phase of EWS retirement and is intended to help organizations identify EWS dependencies, reduce service disruption, and support migration planning. [Rollout schedule] Worldwide, GCC, GCC High, DoD: Beginning in early October 2026 and expected to complete by early July 2027 Key milestones for Worldwide tenants with EWSEnabled=True and no configured EWSAllowedAppIDs list: DateMilestone October 2, 2026Microsoft identifies affected Worldwide tenants. After this date, tenants that enable EWS must configure EWSAllowedAppIDs themselves. October 8-9, 2026Microsoft creates and populates EWSAllowedAppIDs for qualifying Worldwide tenants based on EWS activity observed during the previous 60 days. October 10, 2026EWSAllowedAPPIDs becomes required when EWSEnabled=True. Applications note included in the allow list may lose access to EWS. [Impact on your organization] Who is affected Exchange Online administrators Organizations that continue to use applications or services that depend on EWS Tenants with EWSEnabled=True Platforms and services Exchange Online Exchange Web Services (EWS) What will happen Beginning October 10, 2026, affected Worldwide tenants with EWSEnabled=True must have a configured EWSAllowedAppIDs allow list. Applications not included in the allow list may lose access to EWS. For identified Worldwide tenants with EWSEnabled=True and no configured EWSAllowedAppIDs list on October 3 2026, Microsoft creates and populates an allow list using EWS activity observed during the previous 60 days. Infrequently used applications may not be identified. Cross-tenant organization relationships are not affected by the EWSAllowedAppIDs requirement. Organizations remain responsible for reviewing, validating, and maintaining EWSAllowedAppIDs. EWSAllowedAppIDs is a replacement list. Ensure all required AppIDs are included whenever the configuration is updated. Microsoft applications and scenarios that may generate EWS traffic include Outlook for Windows, Classic Outlook for Mac, Excel Power Query, Power BI, and Exchange Server hybrid scenarios. Outlook for Windows customers should be on August 2026 build 16.0.20430.20092 or later. If EWS-related issues continue after disabling EWS, the cause may be customer-forced configuration. Test whether blocking EWS for the Office client AppID is possible without impact. New Outlook for Mac is not affected. If your organization continues to use Classic Outlook for Mac, ensure the Microsoft Office AppID is included in EWSAllowedAppIDs. Tenants with EWSEnabled not configured (Null) remain subject to Microsoft's phased EWS retirement process and will have EWS disabled as part of that rollout. Organizations with EWSEnabled=True and a configured EWSAllowedAppIDs allow list will not have their EWSEnabled setting modified by Microsoft before April 2027. [Action required and recommendations] If your organization relies on EWS: Review EWS usage reports and identify applications and services that require continued EWS access. Configure and validate an EWSAllowedAppIDs allow list before October 10, 2026. Include Microsoft first-party applications that continue to rely on EWS if they appear in your usage reporting. Ensure all required AppIDs are included whenever EWSAllowedAppIDs is updated. Keep the allow list current as applications are added, removed, or migrated away from EWS. Enable EWS only when required for approved applications. Continue planning migration from EWS to Microsoft Graph where possible. To verify the configured allow list: Get-OrganizationConfig -RetrieveEwsOperationAccessPolicy | Format-List EwsAllowedAppIDs Allow up to 24 hours for EWSAllowedAppIDs changes to take effect and approximately one hour for EWSEnabled changes. Important: EWSAllowList is unrelated to EWS retirement and does not replace EWSAllowedAppIDs. Learn more Exchange Online EWS, Your Time is Almost Up | Microsoft Community Hub How to revert the Outlook Desktop WebView based Room Finder to the legacy Room Finder | Microsoft Support Impact of Exchange Online EWS Deprecation on Hybrid Rich Coexistence and Cross-org Sharing | Microsoft Community Hub Notes from the field: testing EWSAllowedAppIDs safely | Microsoft Community Hub [Compliance considerations] QuestionAnswer Does this change include an admin control?Yes. EWSAllowedAppIDs introduces a tenant-level administrative control that allows Exchange Online administrators to explicitly define which applications are permitted to access EWS. Does this change alter how existing customer data is accessed?Yes. The change modifies how applications are authorized to access Exchange Online data through EWS by requiring administrators to explicitly allow approved application IDs as retirement enforcement begins. Does this change alter how admins monitor, manage, or demonstrate compliance-related activities?Yes. Administrators must identify EWS dependencies, configure and maintain an EWSAllowedAppIDs allow list, and validate application access as part of preparing for EWS retirement. -
Upgraded call history in Teams Calls app
MC1485056 · stayInformed · normal · Updated 10/01/2026 21:42
Services: Microsoft Teams
Read message
[What and Why:] Call history in the Teams Calls app is being upgraded to make it easier to find and act on past call activity. Missed calls and associated voicemails will be consolidated into a single call history entry, reducing clutter and simplifying follow-up. Call history will also expand from 100 records to up to 3,000 records or 6 months of history, whichever limit is reached first, giving users more context when they need it. This message is associated with Microsoft 365 Roadmap ID 570843. [Rollout Schedule:] Targeted Release (Worldwide): We will begin rolling out in mid-November 2026 and expect to complete by mid-November 2026. General Availability (Worldwide): We will begin rolling out in early November 2026 and expect to complete by late November 2026. [Impact on Your Organization:] Who is affected: Users of the Microsoft Teams Calls app. Platforms/Services: Microsoft Teams Teams Calls app What will happen: Missed calls and associated voicemails will be consolidated into a single call history entry. Call history will expand from 100 records to up to 3,000 records or 6 months of history, whichever limit is reached first. Users will have a more complete and easier-to-navigate call history experience. [Action Required/Recommendations:] No admin action is required before rollout. You may want to inform users about the upcoming changes and update internal support guidance as appropriate. [Compliance considerations:] No compliance considerations identified. Review as appropriate for your organization. -
Microsoft Entra App Gallery: Self-service onboarding for new applications
MC1485054 · stayInformed · normal · Updated 10/01/2026 21:40
Services: Microsoft Entra
Read message
[What and why] We are introducing a self-service onboarding experience for new applications submitted to the Microsoft Entra App Gallery. This experience helps independent software vendors (ISVs) validate supported single sign-on (SSO) and user provisioning integrations before submission, identify and resolve common configuration issues earlier in the process, and track submission status through a guided workflow in the Microsoft Entra admin center. By enabling publishers to validate integrations and manage submissions directly, this experience streamlines the publishing process. [Rollout schedule] Public Preview: Available now General Availability (Worldwide): Beginning in mid-November 2026 and expected to complete by late December 2026 [Impact on your organization] Who is affected Independent software vendors (ISVs) and developers submitting new applications to the Microsoft Entra App Gallery Administrators responsible for publishing applications to the Microsoft Entra App Gallery Platforms and services Microsoft Entra admin center Microsoft Entra App Gallery What will happen Publishers can validate supported OpenID Connect (OIDC), SAML, and user provisioning integrations before application submission. Publishers can create and manage App Gallery submissions through a guided workflow in the Microsoft Entra admin center. Validation results can be associated with application submissions. Publishers can provide required application information and supporting documentation during onboarding. Applications can be submitted directly to Microsoft for review. Publishers can track submission status and respond to reviewer feedback. Public Preview currently supports new Microsoft Entra App Gallery application submissions only. Existing applications already published in the Microsoft Entra App Gallery will continue to use the current update and removal process. No impact is expected for organizations that do not publish applications to the Microsoft Entra App Gallery. This experience does not change how users access applications. [Action Required and recommendations] No action is required. Organizations that publish applications to the Microsoft Entra App Gallery should review the new onboarding experience and prepare application publishing teams for the updated submission workflow. Learn more Microsoft Entra Blog: Public preview of self-service onboarding for new Microsoft Entra App Gallery applications Microsoft Learn documentation for validating and publishing applications to the Microsoft Entra App Gallery: Prerequisites to validate and publish your app - Microsoft Entra ID | Microsoft Learn SSO requirements for Microsoft Entra App Gallery - Microsoft Entra ID | Microsoft Learn User provisioning requirements for Microsoft Entra App Gallery - Microsoft Entra ID | Microsoft Learn Publish your app to Microsoft Entra App Gallery - Microsoft Entra ID | Microsoft Learn Update or remove your app from the Microsoft Entra App Gallery - Microsoft Entra ID | Microsoft Learn [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
(Updated) Retirement of SharePoint One-Time Passcode (SPO OTP) and transition to Microsoft Entra B2B
MC1243549 · planForChange · normal · Updated 10/01/2026 20:55
Services: SharePoint Online, Microsoft OneDrive
Read message
Updated October 1, 2026: Phase 1, which enables Entra B2B for new external sharing, is now fully rolled out for Production environments. To ensure a smooth transition, Phase 2, the retirement of SharePoint Online OTP, has been rescheduled to begin in mid-October 2026 and is expected to complete by end of November 2026 for Production environments. Both Phase 1 and Phase 2 roll outs exclude GCC, GCCH & DoD. New dates for these environments will be communicated via Message center when we are ready to proceed. Thank you for your patience. [Introduction] We are retiring SharePoint One‑Time Passcode (SPO OTP) authentication in OneDrive and SharePoint starting mid-October 2026. Beginning in May 2026, new external sharing invitations and authentication will start using Microsoft Entra B2B instead of SPO OTP. This transition simplifies external collaboration, aligns authentication with Microsoft identity standards, and enables consistent guest lifecycle management, governance, and Conditional Access coverage across Microsoft 365. [When this will happen] May & June 2026: Invitation and authentication for new external sharing transitions to Microsoft Entra B2B. Users who previously authenticated via SPO OTP will continue to have access to specific people links even without a B2B guest account yet. Mid-October 2026: Retirement of SPO OTP authentication begins. External users without a guest account get access denied on previously shared specific people links. To restore access, a guest account must be created in Entra B2B, or an allowed user must share/re-share at least one file/folder/site. Retirement is expected to complete by end of November 2026. [How this affects your organization] Who is affected All Microsoft 365 tenants (commercial, government, sovereign). All external users who access OneDrive or SharePoint files, folders, or sites. What will happen The EnableAzureADB2BIntegration setting will no longer control external sharing behavior beginning May 2026. SPO OTP authentication will retire beginning mid-October 2026. The option to disable Entra B2B integration will be removed. Impact on external users External users who already have an Entra B2B guest account in your directory:No change in behavior. External users without a B2B guest account:Specific people links shared after changes rolled out to your tenant: A guest account will be automatically created via the Entra B2B Invitation Manager and authentication will use Entra B2B. The email one-time passcode feature is now turned on by default for all new tenants and for any existing tenants where you haven’t explicitly turned it off. Please refer to this article to learn more. Specific people links shared before changes rolled out to your tenant: SPO OTP authentication continues until the retirement reaches the tenant. After the retirement, these users will receive access denied until a matching B2B guest account exists. Restoring access after retirement Admins can manually create a guest account for the external user at any time. Alternatively, an internal user with permissions needs to share or re-share at least one file, folder, or site, which will automatically create the guest account and restore access to all previously shared content. [What you need to do to prepare] To ensure a smooth transition: Review external sharing policies and conditional access settings for guests in SharePoint and Entra admin centers. Ensure that Microsoft Entra is configured to allow guest invitations for the appropriate users. For example, assign the Guest Inviter role to users who need external sharing or are responsible for creating guest accounts. Inform users that, beginning in mid-October 2026, some external collaborators may see an access denied message when opening older links that were previously authenticated with SharePoint Online OTP. This can occur if a matching B2B guest account was not created for the email address used with the original sharing link.To restore access, users can share or reshare at least one file with the external collaborator. This creates the required B2B guest account, after which the collaborator can continue accessing previously shared links. If your organization relies on email OTP authentication via Entra, ensure it is not disabled in Entra External ID settings. See Email OTP for B2B guests. Optionally, identify external collaborators without guest accounts via external sharing reports. Proactively create guest accounts to retain access. Update internal documentation. Learn more: Add and manage B2B collaboration users in the Microsoft Entra admin center | External ID | Microsoft Entra | Microsoft Learn Email one-time passcode authentication for B2B guest users | External ID | Microsoft Entra | Microsoft Learn Frequently Asked Questions: Improvements to external sharing in OneDrive & SharePoint | SharePoint in Microsoft 365 | Microsoft Learn Overview: B2B collaboration with external guests for your workforce | External ID | Microsoft Entra | Microsoft Learn Quickstart: Add a guest user and send an invitation | External ID | Microsoft Entra | Microsoft Learn SharePoint and OneDrive integration with Microsoft Entra B2B | SharePoint in Microsoft 365 | Microsoft Learn Configure external collaboration - Microsoft Entra External ID | Microsoft Learn [Compliance considerations] Compliance QuestionAnswer Does the change alter how existing customer data is accessed, processed, or stored?Yes. This change retires SPO OTP authentication and requires all external users to authenticate using Microsoft Entra B2B guest accounts, which alters the authentication method used to access existing SharePoint and OneDrive content. Does the change modify Conditional Access policies or enforcement?Yes. After retirement, all external users will authenticate through Entra B2B and become fully subject to Microsoft Entra Conditional Access, Identity Protection, and guest governance policies. Does the change provide a new way of communicating between users, tenants, or subscriptions?Yes. External sharing invitations will be routed through Microsoft Entra B2B Invitation Manager instead of SharePoint’s OTP invitation flow. Does the change alter how admins monitor, report on, or demonstrate compliance activities?Yes. Authentication events and guest lifecycle actions will be logged through Entra audit logs rather than SPO OTP logs, changing where admins review authentication and guest access activity. -
Action Required: Upgrade ExchangeOnlineManagement PowerShell Module to Version 3.10.1 or Later
MC1483974 · planForChange · normal · Updated 09/30/2026 22:53
Services: Exchange Online
Action required by: 03/26/2027 07:00
Read message
[What and Why:] Microsoft introduced security enhancements to Exchange Online PowerShell authentication in ExchangeOnlineManagement module version 3.10.1. These enhancements strengthen the authentication flow and provide protection against emerging threats. Customers using a version earlier than 3.10.1 should upgrade to version 3.10.1 or later. Customers already using version 3.10.1 or later do not need to take additional action beyond keeping the module up to date. [Rollout Schedule:] Enforcement of strict logon requirements is scheduled to begin on March 31, 2027. The rollout is scheduled to begin in late March 2027 and be completed by late April 2027. [Impact on Your Organization:] Who is affected: Customers using ExchangeOnlineManagement module versions earlier than 3.10.1 What will happen: ExchangeOnlineManagement versions earlier than 3.10.1 may experience authentication failures in certain interactive authentication scenarios after enforcement begins. The scenario is particularly relevant when PowerShell 7 is used with Web Account Manager (WAM) disabled. You may not be affected if you are using:ExchangeOnlineManagement version 3.10.1 or later Certificate-based authentication WAM-based authentication Windows PowerShell 5.x [Action Required/Recommendations:] Identify systems running ExchangeOnlineManagement versions earlier than 3.10.1. Upgrade affected installations to version 3.10.1 or later before enforcement begins. Validate administrative scripts, automation solutions, and operational procedures before enforcement. You can verify installed module versions by running: Get-Module ExchangeOnlineManagement -ListAvailable Review the ExchangeOnlineManagement module information and available versions in the PowerShell Gallery. [Compliance considerations:] No compliance considerations identified, review as appropriate for your organization. -
Windows settings backup is now enabled by default for eligible devices
MC1483538 · stayInformed · normal · Updated 09/30/2026 16:57
Services: Windows
Read message
What and why With the release of Windows 11, version 26H2, the Windows settings backup policy is now enabled by default for eligible devices (see the Impact section). The new default applies only if admins haven’t explicitly configured the policy. We honor any existing explicit enable or disable setting. This update makes settings backup a baseline resiliency capability. If user devices ever enter recovery, you don't have to guess whether their Windows settings have a backup. With this feature on by default, users are more likely to have their settings and Microsoft Store app list available to restore after a device reset, replacement, or upgrade. Admins can continue to manage Windows settings backup through Microsoft Intune, Group Policy, or other mobile device management (MDM) solutions. Rollout schedule Windows settings backup default-on is generally available as of September 29, 2026, with the release of Windows 11, version 26H2. Devices originally running Windows 11, version 26H1 will receive the same default-on treatment when they update to a later supported feature release. Learn more in What to know about Windows 11, version 26H1 - Windows IT Pro Blog. Impact on your organization Default-on applies only to devices that meet all of the following criteria: Running Windows 11, version 26H2 or later Not in privacy sensitive countries or regions Not hosted in a sovereign or restricted cloud environment Have the Windows settings backup policy set to Not Configured Devices with an explicitly configured backup policy, whether enabled or disabled, are unaffected. Restore behavior remains admin-controlled and isn’t enabled by default. Users can still turn off backup through the Windows Backup app or the Windows settings page. Action required Review the current backup policy state for eligible devices running Windows 11, version 26H2 or later, and adjust the configuration if needed. To use default-on backup (recommended): No action is required. The default-on behavior applies automatically to eligible devices when the backup policy is set to Not Configured. To opt out: Explicitly disable the backup policy through Microsoft Intune, Group Policy, or your MDM provider. Explicit policy settings take precedence over the default. To enable restore: Configure the restore policy separately. Default-on backup doesn’t enable restore behavior. No action is required if your organization is in a privacy sensitive country or region, in a sovereign or restricted cloud environment, or if you have already explicitly configured the backup policy. Additional information Windows settings backup becoming a new resilience baseline Windows settings backup and restore overview How to configure settings backup and restore policies in Microsoft Intune Compliance considerations: No compliance considerations are identified. Review as appropriate for your organization. -
(Updated) Enhanced security and access controls for Outlook attachments
MC1472591 · stayInformed · normal · Updated 09/29/2026 20:13
Services: Exchange Online
Read message
Updated September 29, 2026: We have updated the content. Thank you for your patience. [What and why:] As part of our overall security initiatives, we’ve created a separate internal application configuration for Outlook attachments, therefore, all standard security and authentication flows will be handled separately. Moreover, Conditional Access policies are now enforced for Outlook attachment operations. Users who don’t meet company policies won’t be able to download, preview, or upload classic attachments (this includes inline images). Policies assigned to Exchange and Office cloud applications will be inherited by the attachment application by default. Continuous Access Evaluation is not included in the initial rollout but will follow up soon. Scope: This change is only applicable to Outlook web (OWA) and New Outlook. [Rollout schedule:] Available now. [Impact on your organization:] Your existing policies now cover attachments. Conditional Access policies you have already scoped to Exchange and Office cloud applications will be enforced for attachment scenarios as well. No new policies need to be created. Users out of compliance will be blocked from attachments. If a user's session no longer satisfies a Conditional Access policy — for example, a non-compliant device, a blocked location, or a network change that triggers CAE re-evaluation — attachment operations will be blocked. These are separate follow-up changes we expect to land in the upcoming weeks. We’ll keep you updated on the readiness and rollout of these enhancements:User sign in prompt for remediation. We're currently working on a solution to prompt the user for sign in to recover functionalities when possible. This will depend on the policy configuration; if the user is not compliant, they won’t be able to use attachment-related tasks. We’ll provide an update to customers once we start rolling out this enhancement. Enable Continuous Access Evaluation (CAE). CAE isn’t supported for this new application configuration yet. We’ll update this message with additional content when it becomes available. [Action required / Recommendations:] Review how your Office and Exchange policies apply to attachments.Attachment operations are now handled by their own application, which by default inherits the Conditional Access policies you've assigned to Office and Exchange. Confirm those conditions are what you intend to enforce for attachments. If you’ve intentionally excluded Exchange online from a policy, that exclusion doesn't carry over to attachments, so users in scope can reach their mail but will be blocked from downloading, previewing, or uploading attachments. To manage attachment policies separate from mail, you can either exclude the attachment application from a policy or target it in a policy of its own. Both require a one-time setup step in your tenant — see Appendix: Excluding attachments from a policy. Update your help desk documentation. Support staff should know that attachment access failures may now result from a Conditional Access policy, and that the remediation is the same as for Outlook — return to a compliant device or network and re-authenticate. Notify users if you enforce strict Conditional Access policies, so they understand attachment actions may now be blocked under the same conditions that already block access to their mailbox. [Appendix:] Excluding attachments from a policy Attachment operations are handled by an application named OwaDownloadAttachments (application Id: e4f2bb2d-a4d0-4eab-aac6-a8b83471cf64 ). Before you can exclude it from a Conditional Access policy, a service principal for it must exist in your tenant. This is a one-time step you'll need to complete first. Step 1: Create the service principal You'll need the Cloud Application Administrator or Global Administrator role. Open Graph Explorer and sign in as an administrator of your tenant. Run: POST https://graph.microsoft.com/v1.0/servicePrincipals Request body: { "appId": "e4f2bb2d-a4d0-4eab-aac6-a8b83471cf64" } Consent to Application.ReadWrite.All scope is required. A successful request returns 201 Created with a display name of OwaDownloadAttachments. If the request reports that the service principal already exists, continue to Step 2. Step 2: Exclude it from the policy Click on View or Edit on the Conditional Access Policy you want to update. Under Target resources, select the Exclude tab. Choose Select resources, search for OwaDownloadAttachments, and select it. Save the policy. Repeat Step 2 for each policy you want attachment operations exempted from. -
(Updated) Microsoft 365 admin center: Agent Registry consolidates duplicate agent entries and adds version history
MC1477184 · preventOrFixIssue · normal · Updated 09/29/2026 18:06
Services: Microsoft 365 suite
Read message
Updated September 29, 2026: We have updated the timeline. Thank you for your patience. [What and why] We're improving the Agent Registry experience in the Microsoft 365 admin center by consolidating duplicate entries for the same agent into a single record. Previously, the same agent could appear multiple times when published across different scopes or when multiple published versions existed. This update simplifies agent governance, provides a clearer inventory of deployed agents, and makes it easier for admins to manage agent lifecycle and version history from a single location. All versions of an agent will be accessible from the agent details flyout while governance actions continue to apply across the entire agent. [Rollout schedule] Worldwide: Beginning in mid-September 2026 and expected to complete in mid-October 2026 (previously late September) [Impact on your organization] Who is affected Global Administrators Global Readers AI Administrators Organizations using the Agent Registry Platforms and services Microsoft 365 admin center Agent Registry What will happen Each agent will appear only once in the Agent Registry. Agents that previously appeared as multiple entries due to different publishing scopes or published versions will be consolidated into a single entry. The Registry list will display the most recently published organizational version by default. Selecting an agent will open an agent details flyout that includes a version selector. The version selector will display available published versions and any in-progress draft versions where applicable. Selecting a version will update the agent details shown in the flyout. Governance actions, such as Block, will continue to apply to the entire agent across all versions. Total agent counts in the Agent Registry may decrease because duplicate entries are being consolidated. No agents are being removed. Reports, dashboards, exports, and custom processes that relied on previous per-entry counts may show different totals after rollout. Registry exports will include options for exporting agents and their associated versions. This change is enabled by default and requires no configuration. [Action required and recommendations] No action is required. We recommend that administrators: Inform governance and operations teams that Agent Registry counts may decrease as duplicate entries are consolidated. Review internal reports, dashboards, scripts, and processes that depend on Agent Registry counts or export data. Update internal documentation and training materials to reflect the new version selector experience in the agent details flyout. Validate any downstream reporting that uses Agent Registry export data after rollout is complete. [Compliance considerations] QuestionAnswer Does the change alter how admins can monitor, report on, or demonstrate compliance activities?Yes. Agent Registry counts will change because duplicate entries are consolidated. Reports, dashboards, exports, and other administrative reporting based on prior count logic may show different totals after rollout. -
How to get the Windows 11 2026 Update
MC1482225 · stayInformed · normal · Updated 09/29/2026 17:12
Services: Windows
Read message
What and why: Windows 11, version 26H2, also referred to as the Windows 11 2026 Update, is now generally available. This annual feature update for Windows 11 includes features and enhancements delivered to version 25H2 over the past year in the areas of security, management, accessibility, and user experience. Rollout schedule: Windows 11, version 26H2 is available now for eligible devices running Windows 11, versions 25H2 and 24H2. For commercial and education customers, it is available through existing Windows update management tools, including Windows Autopatch and the Microsoft 365 admin center. (Downloads in the Microsoft 365 admin center and similar channels might be delayed.) Availability will expand in the coming weeks. Microsoft might apply safeguard holds to devices where a known compatibility issue could affect the update experience. Rollout status, known issues, and safeguard information will be published through Windows release health. For more details about the rollout of Windows 11, version 26H2, see How to get the Windows 11 2026 Update. Impact on your organization: Installing Windows 11, version 26H2 resets the support lifecycle for supported editions. Enterprise and Education editions receive 36 months of support, while Home and Pro editions receive 24 months of support. If your organization has eligible devices running Windows 11, version 25H2 or 24H2, you can use your existing tools, update rings, policies, and deployment practices to validate and deploy version 26H2. Because Windows 11, versions 26H2, 25H2, and 24H2 share the same servicing branch and underlying code base, version 26H2 can be delivered via enablement package to eligible devices running Windows 11, versions 25H2 and 24H2. A full OS swap is not needed. Some features that were behind temporary commercial control in Windows 11, version 25H2 are enabled by default in version 26H2. These include Windows settings backup, app-specific taskbar actions, and File Explorer improvements. Existing administrator-configured policies for Windows settings backup continue to be honored. Some features have additional eligibility requirements. Action required/recommendations: No immediate action is required. When you are ready to begin deployment, we recommend that you: Validate Windows 11, version 26H2 with a targeted set of devices before broad deployment. Test business-critical applications, representative hardware, and workflows. Review features that are enabled by default in version 26H2 and determine whether any existing policies or configurations should be adjusted. Expand deployment using your existing update rings and deployment processes after validation. Monitor deployment health, known issues, and safeguard holds through Windows release health. Review your organization's security and compliance requirements and prepare support personnel for changes introduced with Windows 11, version 26H2. Compliance considerations: Before broad deployment, review your organization's security and compliance requirements and validate Windows 11, version 26H2 against your existing policies, business-critical applications, representative hardware, and workflows. Microsoft has also published an updated Windows 11, version 26H2 security baseline and refreshed deployment and management resources, including Administrative Templates (ADMX) and the Group Policy Settings Reference for version 26H2. For a list of updated tools and resources, see An IT pro’s guide to Windows 11, version 26H2. -
(Updated) Simplified Copilot experience in Microsoft Teams
MC1458472 · stayInformed · normal · Updated 09/29/2026 16:35
Services: Microsoft Teams
Read message
Updated September 29, 2026: We have updated the timeline. Thank you for your patience. [What and Why:] Continuing our efforts to streamline the user experience in the Copilot app as shared in MC1325422, we are introducing updates to the Copilot experiences in Microsoft Teams that deliver a similar, chat-centered experience. These updates simplify navigation, improve the chat experience, and provide new ways for users to organize work—helping them stay focused, maintain context, and move work forward efficiently. The refreshed design will be available in both the full-page Copilot experience in Teams and the Copilot side pane experience throughout Teams. The full-screen Copilot experience will closely mirror the recent updates in the Copilot app, while the side pane experience will receive a refreshed design optimized for contextual Copilot interactions within Teams. [Rollout Schedule:] Generally available: October 2026 (previously September). [Impact on your organization:] Users will see a refreshed Copilot experience in Microsoft Teams that aligns with the updated, chat-centered experience available in the Copilot app. The update applies to both the full-page Copilot experience in Teams and the Copilot side pane experience. The refreshed experience includes simplified navigation, an updated chat layout, improved agent discovery and interaction, and the introduction of Work IQ controls. Users of the full-screen Copilot experience in Teams will also see the new Tasks view, which provides visibility into long-running Copilot activities such as agent activity and scheduled chats. The side pane experience will receive the updated design and chat experience but will not include the Tasks view. This change is enabled by default as part of the service update and does not require user or administrator action. There are no changes to licensing, permissions, or existing compliance controls. [Action Required / Recommendations:] No action is required to enable this change. To prepare for the rollout, administrators should: Inform users of the updated Copilot experience in Teams and the visual and navigation changes they may encounter. Update internal documentation, training materials, and adoption guidance that reference the current Copilot experience in Teams. Review and communicate the new Work IQ experience so users understand how work and web grounding are presented in the refreshed interface. Update any help desk or support documentation that includes screenshots or navigation guidance for Copilot in Teams. This update will be enabled automatically and will not require configuration changes by administrators. -
(Updated) Simplified Copilot experience in Microsoft Outlook
MC1458470 · stayInformed · normal · Updated 09/29/2026 16:33
Services: Exchange Online
Read message
Updated September 29, 2026: We have updated the timeline. Thank you for your patience. [What and Why:] Continuing our efforts to streamline the user experience in the Copilot app as shared in MC1325422, we are introducing updates to the Copilot experiences in Microsoft Outlook that deliver a similar, chat-centered experience. These updates simplify navigation, improve the chat experience, and provide new ways for users to organize work—helping them stay focused, maintain context, and move work forward efficiently. The refreshed design will be available in both the full-page Copilot experience in Outlook and the Copilot side pane experience throughout Outlook. The full-screen Copilot experience will closely mirror the recent updates in the Copilot app, while the side pane experience will receive a refreshed design optimized for contextual Copilot interactions within Outlook. [Rollout Schedule:] Generally available: October 2026 (previously September). [Impact on your organization:] Users will see a refreshed Copilot experience in Microsoft Outlook that aligns with the updated, chat-centered experience available in the Copilot app. The update applies to both the full-page Copilot experience in Outlook and the Copilot side pane experience. The refreshed experience includes simplified navigation, an updated chat layout, improved agent discovery and interaction, and the introduction of Work IQ controls. Users of the full-screen Copilot experience in Outlook will also see the new Tasks view, which provides visibility into long-running Copilot activities such as agent activity and scheduled chats. The side pane experience will receive the updated design and chat experience but will not include the Tasks view. This change is enabled by default as part of the service update and does not require user or administrator action. There are no changes to licensing, permissions, or existing compliance controls. [Action Required / Recommendations:] No action is required to enable this change. To prepare for the rollout, administrators should: Inform users of the updated Copilot experience in Outlook and the visual and navigation changes they may encounter. Update internal documentation, training materials, and adoption guidance that reference the current Copilot experience in Outlook. Review and communicate the new Work IQ experience so users understand how work and web grounding are presented in the refreshed interface. Update any help desk or support documentation that includes screenshots or navigation guidance for Copilot in Outlook. This update will be enabled automatically and will not require configuration changes by administrators. -
(Updated) Updates to Tenant External Recipient Rate Limit (TERRL) Quotas for New, Trial, and Education Tenants
MC1454397 · stayInformed · normal · Updated 09/29/2026 16:28
Services: Microsoft 365 suite
Read message
Updated September 29, 2026: We have updated the timeline. Thank you for your patience. [What and Why:] To strengthen protection against abuse and ensure fair use of Exchange Online resources, we are updating how the Tenant External Recipient Rate Limit (TERRL) quota is calculated for certain tenants. These changes improve how quotas account for tenant age (how long the tenant has existed since creation), trial subscriptions, and educational organizations using free Education (EDU) licenses. [Rollout Schedule:] General Availability (Worldwide): Rolling out beginning mid-September 2026 and expected to complete by end of November 2026. [Impact on Your Organization:] Who is affected: Newly created tenants (first 60 days) Trial tenants Educational organizations with free EDU licenses Platforms/Services: Exchange Online Exchange admin center (EAC) What will happen: TERRL quota calculations will change based on tenant status and licensing. New tenant quotas (based on tenant age):Less than 31 days: 10% of standard calculated quota 31–60 days: 25% of standard calculated quota More than 60 days: 100% of standard calculated quota Trial tenants:Daily TERRL quota reduced from 5,000 to 500 external recipients Tenants with free EDU licenses (e.g. A1 licenses):New formula applied: 500 × (Purchased Email Licenses^0.7 + Free EDU Licenses^0.3) + 9500 Free EDU licenses contribute to the quota at a lower weighting than purchased licenses Tenants without free EDU licenses:Existing formula remains unchanged: 500 × (Purchased Email Licenses^0.7) + 9500 If a tenant exceeds its quota: Additional outbound messages to external recipients will be blocked until usage falls below the rolling 24-hour limit Senders will receive one of the following Non-Delivery Reports (NDRs):Trial tenants: 550 5.7.232 — Message blocked due to trial tenant external recipient limit Non-trial tenants: 550 5.7.233 — Message blocked due to tenant external recipient limit [Action Required / Recommendations:] No immediate action is required. Recommended actions: Review the Tenant Outbound External Recipients Rate report in the Exchange admin center: EAC > Reports > Mail flow > Tenant Outbound External Recipients Rate. Monitor:Current TERRL quota Outbound recipient volume Percentage of quota consumed Blocked recipients (if any) TERRL enforcement status If your organization regularly operates near or above quota consider migrating high-volume, application-driven outbound email to a third-party bulk email service or purchasing more licenses to cover your volume needs. Learn more: Introducing Exchange Online Tenant Outbound Email Limits [Compliance considerations:] No compliance considerations identified, review as appropriate for your organization. -
Microsoft SharePoint: Retirement of SharePoint Page Agent (Frontier)
MC1481325 · planForChange · normal · Updated 09/29/2026 00:03
Services: SharePoint Online
Read message
[What and why] Microsoft will retire the SharePoint Page Agent (Frontier) for SharePoint Online. This early access experience enabled users to turn content from Microsoft 365 Copilot conversations into draft SharePoint pages and news posts. As Microsoft continues to invest in AI-powered content creation experiences, page and news authoring capabilities are now available directly within SharePoint through Copilot in SharePoint. Users can create and refine content directly within the SharePoint authoring experience. [Rollout schedule] Retirement (Frontier preview): Beginning in mid-October 2026 and expected to complete in mid-November 2026 [Impact on your organization] Who is affected Organizations that have users creating SharePoint pages or news posts through the SharePoint Page Agent (Frontier) in Microsoft 365 Copilot SharePoint authors who currently initiate page creation from Microsoft 365 Copilot conversations Platforms and services Microsoft 365 Copilot SharePoint Online Copilot in SharePoint What will happen The SharePoint Page Agent (Frontier) will no longer be available in Microsoft 365 Copilot after retirement is complete. Users will no longer be able to start new page or news-post authoring interactions through the SharePoint Page Agent. Existing SharePoint pages and news posts previously created through the SharePoint Page Agent will remain available in their SharePoint sites. Existing SharePoint permissions and lifecycle policies for previously created content will continue to apply. Eligible users can continue creating and refining SharePoint pages and news posts using Copilot in SharePoint. No migration of existing content is required. [Action required and recommendations] To prepare for this retirement: Notify SharePoint authors that the SharePoint Page Agent will be retired beginning in mid-October 2026. Direct users to create and refine SharePoint pages and news posts using Copilot in SharePoint. Update internal documentation, training materials, support content, and bookmarks that reference the SharePoint Page Agent or its Microsoft Marketplace listing. Review internal publishing workflows and guidance to ensure they reference the supported authoring experience. Remind authors to review AI-generated content for accuracy, completeness, and compliance with your organization's publishing standards before publishing. Learn more SharePoint AI page authoring: Select, describe, and refine | Microsoft Community Hub [Compliance considerations] No compliance considerations identified. Review as usual for your organization. -
Microsoft Defender XDR: Detection source support in alert tuning rules
MC1481318 · stayInformed · normal · Updated 09/28/2026 23:56
Services: Microsoft Defender XDR
Read message
[What and why] We are introducing detection source selection for alert tuning rules in Microsoft Defender XDR. This update enables alert tuning rules to be scoped to specific detection sources, providing more granular control over how alert tuning rules are applied. As part of this update, alert tuning rules will apply to the detection sources selected for each rule. Existing rules that are not updated will apply to all detection sources under their selected service sources, including custom detections. [Rollout schedule] Public Preview (Worldwide): Rollout begins in mid-October 2026 and is expected to complete in early November 2026.Note: Detection source selection will become available in mid-October 2026, and configured detection source selections will take effect in early November 2026. General Availability (Worldwide): Rollout begins in mid-November 2026 and is expected to complete in early December 2026.Note: Detection source selection will become available in mid-November 2026, and configured detection source selections will take effect in early December 2026. [Impact on your organization] Who is affected Organizations that use alert tuning rules in Microsoft Defender XDR. Platforms and services Microsoft Defender XDR What will happen Alert tuning rules will be configurable to apply to specific detection sources and apply only to the detection sources selected for each rule. If not updated, existing alert tuning rules will apply to all detection sources under their selected service sources, including custom detections. Detection source selection [Action required and recommendations] No action is required if existing rules should apply to all detection sources under their selected service sources, including custom detections. Otherwise, we recommend that you review existing alert tuning rules and update the detection source selections as needed. [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
Microsoft Teams: Enable Teams apps and agents for existing applications in your organization
MC1481316 · stayInformed · normal · Updated 09/28/2026 23:52
Services: Microsoft Teams
Read message
[What and why] Organizations often use third-party applications such as ServiceNow, Workday, Jira, and others, but the corresponding Microsoft Teams apps and agents may not be enabled for users. As a result, users may switch between Teams and other applications even when an integrated Teams experience is available. With this feature, admins can discover Teams apps and agents that correspond to applications already being used in their organization. Recommendations are prioritized using usage signals, helping admins identify opportunities to make those Teams experiences available to users already using the application, specific users and groups, or the entire organization. This helps bring existing business applications into the flow of work in Teams, reducing context switching and helping organizations realize more value from their software investments. [Rollout schedule] Targeted Release: Beginning in early November 2026 and expected to complete by mid-November 2026 General Availability (Worldwide, GCC): Beginning in early November 2026 and expected to complete by mid-November 2026 [Impact on your organization] Who is affected Microsoft Teams administrators managing app and agent deployment Organizations using supported third-party applications that have corresponding Teams apps or agents Platforms and services Microsoft Teams Teams admin center Teams apps Teams agents What will happen Admins will see recommendations in the Teams admin center for Teams apps and agents associated with applications already being used in their organization: Recommendations will include usage signals to help admins identify where a Teams app or agent may provide the greatest value. Admins can choose to make a recommended app or agent available to users already using the corresponding application, specific users and groups, or everyone in the organization. Admins can choose to install the app or agent for applicable users. No Teams apps or agents will be enabled automatically. Existing app availability and installation settings will not change unless an administrator takes action. Users may gain access to applications they already use directly within Teams, reducing the need to switch between applications. [Action required and recommendations] No action is required unless you want to use this feature. Review this feature before rollout and determine whether you want to enable it in the Teams admin center. If enabled, Microsoft will use signals indicating that users have signed in to applications within your organization to identify relevant Teams apps and agents and provide recommendations. Review recommendations in the Teams admin center and determine which apps or agents should be made available or installed for users. Communicate the change to Teams administrators responsible for app governance and deployment. Update any internal documentation related to Teams app management, if applicable. [Compliance considerations] QuestionAnswer Does the change alter how existing customer data is processed, stored, or accessed?Microsoft uses application sign-in signals to identify relevant Teams apps and agents and generate recommendations. Does the change introduce or significantly modify AI/ML or agent capabilities that interact with or provide access to customer data?The feature introduces agent-related capabilities and uses signals to recommend Teams apps and agents. Does the change add any integration to third-party software products?Recommendations are based on applications already in use, including third-party applications such as ServiceNow, Workday, and Jira. Does the change include an admin control, and can it be controlled through Entra ID group membership?Admins must enable the feature and can target specific users or groups when enabling apps or agents. -
Microsoft Entra ID: Enhance protection of the authentication experience by blocking external script injection
MC1481309 · planForChange · normal · Updated 09/28/2026 23:44
Services: Microsoft Entra, Microsoft 365 suite
Action required by: 10/19/2026 07:00
Read message
[What and why] As part of Microsoft's Secure Future Initiative, we are strengthening the security of the Microsoft Entra ID sign-in experience by introducing additional Content Security Policy (CSP) protections. This change helps protect users from threats such as cross-site scripting (XSS) by allowing only trusted Microsoft-hosted scripts to run during authentication and blocking unauthorized or externally injected code. This post is a reminder of our previous announcement (MC1191924), which communicated this upcoming security change and the actions organizations may need to take before rollout. [Rollout schedule] General Availability (Worldwide): Beginning in mid-October 2026 and expected to complete by late October 2026 [Impact on your organization] Who is affected Organizations whose users authenticate through Microsoft Entra ID sign-in pages hosted on login.microsoftonline.com Organizations using browser extensions, monitoring tools, customization tools, or other solutions that inject scripts into the sign-in experience Microsoft Entra External ID tenants are not affected Platforms and services Microsoft Entra ID Web-based authentication experiences using login.microsoftonline.com Browser-based sign-in experiences across supported browsers What will happen A new Content Security Policy (CSP) header will be added to Microsoft Entra ID sign-in pages. Scripts will be permitted only from trusted Microsoft content delivery network (CDN) domains. Inline script execution will be restricted to trusted Microsoft-authorized sources. Browser extensions and tools that inject scripts into Microsoft Entra ID sign-in pages may stop functioning. Users will continue to be able to sign in even if unsupported script injection tools no longer function. This change is enabled by default as part of the service update and does not require tenant configuration. Microsoft Authentication Library (MSAL) and API-based authentication flows are not affected because CSP enforcement applies only to browser-based sign-in experiences using login.microsoftonline.com. [Action required and recommendations] If your organization does not use tools or extensions that inject code into Microsoft Entra ID sign-in pages, no action is required. If your organization uses tools that inject code into the sign-in experience: Review the CSP guidance and assess whether any tools, browser extensions, or custom solutions rely on script injection. Test affected authentication workflows ahead of rollout. Replace or update any solutions that depend on script injection into Microsoft Entra sign-in pages. Communicate potential impacts to help desk and identity administration teams. Update internal documentation if it references affected authentication customizations. Learn more Content Security Policy (CSP) rollout in Microsoft Entra ID - Microsoft identity platform | Microsoft Learn CSP ⟶ script-src Guide CSP Nonce ⟶ Script & Style Attribute Enhance protection of Microsoft Entra ID authentication by blocking external script injection | Microsoft Community Hub Secure Future Initiative – Secure by Design | Microsoft why-xss-still-matters-msrcs-perspective-on-a-25-year-old-threat [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
(Updated) Microsoft Teams: Local Pan-tilt-zoom (PTZ) controls for Microsoft Teams Rooms on Windows
MC1459138 · stayInformed · normal · Updated 09/28/2026 22:38
Services: Microsoft Teams
Read message
Updated September 28, 2026: We have updated the timeline. Thank you for your patience. [What and why:] Microsoft Teams Rooms on Windows will introduce native Pan-Tilt-Zoom (PTZ) camera controls directly from the in-room console for compatible cameras. This enhancement enables room users to manually pan, tilt, and zoom supported cameras during meetings without requiring a separate remote control or vendor-specific application. This feature works with cameras that support pan, tilt, and zoom, whether the camera moves a physical lens or adjusts the image digitally. Controls are available when Teams Rooms can confirm the camera isn't independently framing the room. This is an additive feature and does not change or remove existing camera functionality. [Rollout Schedule:] Public Preview (Worldwide): Rollout begins in early September 2026 and is expected to complete by mid-October 2026. General Availability (Worldwide): Rollout begins in early October 2026 (previously late September) and is expected to complete by late October 2026 (previously mid-October). General Availability (GCC): Rollout begins in mid-October 2026 (previously mid-September) and is expected to complete by early November 2026 (previously mid-October). [Impact on Your Organization:] Who is affected Organizations using Microsoft Teams Rooms on Windows devices. Meeting participants using rooms equipped with compatible PTZ-capable cameras. Support staff and room administrators responsible for Teams Rooms devices. Platforms and Services Microsoft Teams Rooms on Windows Compatible PTZ cameras connected to Teams Rooms systems What will happen Users will be able to manually control camera pan, tilt, and zoom functions directly from the Teams Rooms console during meetings. The feature provides local camera framing adjustments without requiring a physical remote control or camera vendor application. Support includes cameras with mechanical, optical, or digital PTZ. Teams Rooms shows the controls when it can confirm the camera isn't independently framing the room. The feature will be enabled automatically on eligible Teams Rooms on Windows devices with compatible PTZ cameras. Rooms without PTZ-capable cameras will not be affected. [Action Required / Recommendations:] No action is required to enable the feature. We recommend that administrators: Confirm which Teams Rooms on Windows devices are paired with PTZ-capable cameras. Cameras with mechanical, optical, or digital PTZ are all eligible. Inform room users that PTZ camera controls will be available directly from the room console. Update internal support documentation and room usage guidance, if applicable, to reflect the new camera control experience. Prepare help desk and support teams for potential user questions regarding the new controls. [Compliance Considerations:] No compliance considerations identified, review as appropriate for your organization. -
SharePoint: HTML pages
MC1479517 · planForChange · normal · Updated 09/25/2026 21:40
Services: SharePoint Online
Read message
[What and Why:] SharePoint is adding support for HTML pages. Users will be able to create HTML pages with Copilot in SharePoint or upload HTML from another source. After an HTML page is stored in the Site Pages library, users can render it as a page in SharePoint, make additional edits, publish it, and share it with their audience. This gives organizations another way to present content alongside existing ASPX pages and helps users create polished web content more efficiently in SharePoint. [Rollout Schedule:] Public Preview: Rollout will begin in early October 2026 and is expected to complete in early October 2026. General Availability (Worldwide): Rollout will begin in mid-November 2026 and is expected to complete by late December 2026. [Impact on Your Organization:] Who is affected: SharePoint authors who create, upload, edit, publish, or share pages. Users with access to Copilot in SharePoint for HTML page creation and editing. Admins and support teams responsible for SharePoint authoring guidance and Copilot adoption. Platforms/Services: SharePoint Online Copilot in SharePoint Site Pages library What will happen: Users can create HTML pages in SharePoint by selecting + New on a SharePoint site and then selecting HTML page. Users can create an HTML page with Copilot from the floating Copilot button on a SharePoint site. Users can create an HTML page from the Publish landing page by selecting + Create and then HTML page. Users can describe the page they want in the prompt box and attach relevant files for additional context. Copilot can create a draft HTML page and open it in edit mode. Users can upload an existing .html file from the HTML page creation screen. Users can upload HTML pages or folders from the Site Pages library. Users can edit text directly on the page or use the Copilot chat pane for broader content and design changes. Published pages are visible to users who already have permission to view the page; publishing does not grant new permissions. The site-scoped Agent creation entry point will be removed from the + New menu on site pages. New agent creation remains available from the command bar of a document library or list and from the context menu of selected files in a document library. [Action Required/Recommendations:] No admin action is required before rollout. Before rollout, you may want to: Inform SharePoint authors about the new HTML page creation, upload, edit, publish, and sharing capabilities. Update internal SharePoint or Copilot guidance if your organization documents page authoring workflows. Review Copilot licensing assignments to confirm which users will have access to Copilot-assisted HTML page creation. Remind users that publishing an HTML page does not grant new permissions. Review: Create, upload, edit, and publish HTML pages in SharePoint. [Compliance considerations:] Does the change store new customer data, if so, where, and is the data cached or permanently stored?Yes. HTML pages created or uploaded by users are stored in the SharePoint Site Pages library according to existing SharePoint storage and retention behavior. Does the change alter how existing customer data is processed, stored, or accessed?Yes. Users can create, upload, edit, publish, and share HTML content as SharePoint pages. Existing SharePoint permissions determine who can access published pages. Does the change introduce or significantly modify AI/ML or agent capabilities that interact with or provide access to customer data?Yes. Copilot in SharePoint can generate or edit HTML page content based on user prompts and attached files that the user provides or is authorized to access. Does the change provide end users any new way of interacting with generative AI?Yes. Users can use Copilot in SharePoint to create and edit HTML pages through prompts. Does the change include an admin control and can it be controlled through Entra ID group membership?Yes. Access to Copilot-assisted HTML page creation depends on existing Copilot licensing, SharePoint permissions, and organizational controls for Copilot experiences. -
Video recap in Microsoft Teams supports more languages
MC1479506 · planForChange · normal · Updated 09/25/2026 21:35
Services: Microsoft Teams
Read message
[What and Why:] Video recap in Microsoft Teams uses AI to create a narrated highlight video from a recorded and transcribed meeting. It combines key meeting content with short video clips, helping users catch up without watching the full recording. With this update, Video recap is expanding support to 23 languages across 31 locale variants The first set of supported languages includes: English, Chinese, French, German, Italian, Japanese, Portuguese,Spanish. Arabic, Czech, Danish, Dutch, Finnish, Hebrew, Hungarian, Korean, Norwegian, Polish, Russian, Swedish, Thai, Turkish, and Ukrainian. Regional variants are supported for English, Chinese, French, Portuguese, and Spanish. [Rollout Schedule:] General Availability (WW): We will begin rolling out on late September 2026 and expect to complete by late September 2026. [Impact on Your Organization:] Users with a Microsoft 365 Copilot license will be able to access Video recap for eligible meetings in the supported languages. For a Video recap to be available, the meeting must: Be between 10 and 90 minutes long. Be recorded and transcribed with cloud recording enabled. Meet the existing Microsoft 365 Copilot eligibility requirements. After a meeting, users can open the meeting chat, select **Recap**, and then select **Video recap**. They can also open a past meeting from the Teams calendar and select **View recap**. No separate Video recap file is created. Video recap data is stored with the original Teams recording in SharePoint or OneDrive. Video recaps are AI-generated. Users should review the content for accuracy. [Action Required/Recommendations:] No user action is required before this rollout. You may want to: Inform your help desk about the expanded language support. Update internal training and documentation for Video recap. Confirm that eligible users have a Microsoft 365 Copilot license and that your existing meeting recording and transcription policies meet the Video recap requirements. [Compliance considerations:] Does the change introduce or significantly modify AI/ML or agent capabilities that interact with or provide access to customer data?The feature uses AI/ML or agent capabilities with Microsoft 365 content, prompts, or service data as described in this message. Does the change provide end users any new way of interacting with generative AI?The feature introduces or updates a user-facing AI or Copilot experience as described in this message. Does the change include an admin control and, can it be controlled through Entra ID group membership?The feature includes or affects admin controls, policies, permissions, roles, authentication, or management settings as described in this message. Review the linked documentation or admin center controls for group-based configuration support. -
Interim time zone guidance for Alberta, British Columbia, and Morocco
MC1479468 · planForChange · normal · Updated 09/25/2026 20:01
Services: Windows
Read message
What and why: Three time zone changes affect Windows devices in Alberta, British Columbia, and Morocco, with Windows releasing fixes across September and October 2026. Alberta and affected Northwest Territories locations are permanently moving to UTC-6 on November 1, 2026. Most of British Columbia is permanently moving to UTC-7 on the same date. Morocco turned its clocks back one hour to UTC+0 on September 20, 2026. Microsoft recommends temporary workarounds for devices that can't be updated in time. For the workaround steps and full guidance for each region, visit the Daylight Saving Time & Time Zone Blog. Rollout schedule: September 2026 – The Morocco change was included with the September 2026 Windows security update for all supported platforms. The Alberta and British Columbia time zones were included with the September 2026 Windows non-security preview update for Windows 11, versions 26H2, 26H1, 25H2, and 24H2. October 2026 – The Alberta and British Columbia time zones will be included with the October 2026 Windows security update for all remaining supported versions of Windows, including Windows Server. November 1, 2026 – The Alberta and British Columbia transitions take effect. Impact on your organization: In Morocco, devices will show an incorrect time until the update is installed. In Alberta and British Columbia, existing time zones remain correct until November 1, 2026; after that date, devices will show an incorrect time until the update is installed. For those two regions, the update adds a new time zone, (UTC-06:00) Mountain Time (Alberta) and (UTC-07:00) Pacific Time (British Columbia). Devices that set their time zone automatically will select the new time zone on their own; on other devices, users must select it manually. Action required/recommendations: Install the update on affected devices in Morocco now, and on devices in Alberta and British Columbia before November 1, 2026. If you can't install it in time, read and follow the interim guidance for each affected region, listed in Additional information. Compliance considerations: No compliance considerations are identified. Review as appropriate for your organization. Additional information: Daylight Saving Time & Time Zone Blog Interim guidance for Alberta time zone changes 2026 Interim guidance for British Columbia time zone changes 2026 Interim guidance for Morocco DST change 2026 Daylight saving time help and support -
(Updated) Microsoft Teams: Proximity join support for attendees in Teams events from Teams Rooms on Windows and Android
MC1461157 · stayInformed · normal · Updated 09/25/2026 18:58
Services: Microsoft Teams
Read message
Updated September 25, 2026: We have updated the timeline. Thank you for your patience. [What and Why:] We are introducing attendee proximity join for Microsoft Teams Rooms on Windows and Android, enabling users to quickly and effortlessly connect to a nearby room system when joining Microsoft Teams events, including town halls, webinars, and structured meetings. This enhancement simplifies the meeting join experience and helps users connect to the appropriate room device with fewer steps. This message is associated with Roadmap ID 568781. [Rollout Schedule:] Targeted Release: Rollout will begin in early November 2026 (previously early October) and is expected to complete by mid-November 2026 (previously late October). General Availability (Worldwide, GCC, GCC High): Rollout will begin in mid-November 2026 (previously late October) and is expected to complete by early December 2026 (previously mid-November). [Impact on Your Organization:] Who is affected: Users who leverage Microsoft Teams Rooms on Windows or Android to join Teams events. Platforms and Services: Microsoft Teams Rooms on Windows Microsoft Teams Rooms on Android Microsoft Teams events, including town halls and webinars What will happen: Users will be able to use proximity join to connect to nearby Microsoft Teams Rooms when joining Teams events. The feature provides a faster and more seamless method for joining supported Teams events from room systems. This functionality will be available by default as part of the Microsoft Teams Rooms experience. [Action Required / Recommendations:] No action is required to enable this feature. It will become available automatically during the rollout. We recommend informing users who regularly participate in Teams events that they can use proximity join with nearby Microsoft Teams Rooms to simplify the room join experience. [Compliance Considerations:] No compliance considerations identified, review as appropriate for your organization. -
Microsoft Defender for Office 365: Teams user reporting enabled by default
MC1478463 · planForChange · normal · Updated 09/25/2026 16:53
Services: Microsoft Defender XDR
Read message
[What and why] To help organizations identify and respond to security threats in Microsoft Teams, Microsoft Defender for Office 365 will enable Teams user reporting by default. Users can report suspicious messages, calls, and meetings, helping organizations improve detection of phishing, spam, impersonation, malicious content, and other threats. This capability is available for organizations licensed for Microsoft Defender for Office 365 Plan 1 or Plan 2, Microsoft 365 E5, or Office 365 E5. [Rollout schedule] General Availability (Worldwide): Beginning in late October 2026 and expected to complete by late October 2026 [Impact on your organization] Who is affected Organizations licensed for Microsoft Defender for Office 365 Plan 1 or Plan 2, Microsoft 365 E5, or Office 365 E5 Microsoft Teams and security administrators Teams users in affected organizations Platforms/Services Microsoft Teams Microsoft Defender portal Microsoft Defender for Office 365 What will happen Users can report suspicious messages, calls, and meetings directly from Teams. Reported content is submitted per your configured reported destination for security analysis. Security risk items can include phishing, spam, impersonation, malicious content, and phishing URLs. Beginning October 7, 2026, Teams user-reported settings will be managed on a dedicated page in the Microsoft Defender portal. If you have already configured Teams user-reported settings, your existing settings will be carried over. Changes made after migration may not be reflected until the week of October 15, 2026. If you have not already configured Teams user-reported settings, Teams user reporting will be enabled by default beginning October 25, 2026, unless you opt out. Image 1 - Teams user reported settings view: Image 2 - Email user reported settings view: [Action required/Recommendations] Review your Teams user-reported settings before October 25, 2026, if you do not want Teams user reporting enabled by default or want reported content sent to a destination other than Microsoft. Recommended actions: Review Teams user-reported settings in the Microsoft Defender portal. Decide whether user-reported Teams content should be submitted to Microsoft for security analysis. Opt out before October 25, 2026, if desired. Inform security administrators and help desk staff about this change. Learn More Email user-reported settings: security.microsoft.com/securitysettings/userSubmission Teams user-reported settings: security.microsoft.com/securitysettings/teamsUserSubmission User reported settings in Teams - Microsoft Defender for Office 365 | Microsoft Learn [Compliance considerations] QuestionAnswer Does the change alter how admins can monitor, report on, or demonstrate compliance activities?Teams user-reported settings will move to a dedicated configuration page in the Defender portal. Does the change include an admin control, and can it be controlled through Entra ID group membership?Administrators can opt out by configuring Teams user-reported settings in the Defender portal. Group-based controls are not specified. -
(Updated) Microsoft Teams: Enhanced IntelliFrame with AI data channel for intelligent cameras
MC1442614 · stayInformed · normal · Updated 09/25/2026 16:35
Services: Microsoft Teams
Read message
Updated September 25, 2026: We have updated the timeline. Thank you for your patience. [What and Why] We are introducing enhanced IntelliFrame capabilities for Teams Rooms on Windows using an expanded AI data channel on certified intelligent cameras. This update enables faster active speaker framing, improved in-room participant recognition and labeling, and more responsive meeting views. By processing AI metadata directly on the device and sending it through a dedicated data channel rather than relying only on cloud processing, this feature reduces dependency on network conditions and improves performance in bandwidth-constrained environments. This helps deliver a more consistent and intelligent meeting experience for both in-room and remote participants. This message is associated with Microsoft 365 Roadmap ID 564969. [Rollout Schedule] General Availability (Worldwide): Beginning mid-January 2027 (previously mid-October 2026) and expected to complete by early February 2027 (previously mid-November 2026) [Impact on Your Organization:] Who is affected Organizations using Teams Rooms on Windows with certified AI-capable cameras and Teams Rooms Pro licenses Platforms/Services Microsoft Teams Teams Rooms on Windows Certified intelligent (IC 2.0) cameras What will happen Meetings in supported Teams Rooms will automatically use enhanced IntelliFrame capabilities. Active speaker framing will respond faster. In-room participants will be individually recognized and labeled. Meeting views will adjust more smoothly, including in low-bandwidth conditions. Improvements will be visible to both in-room and remote meeting participants. AI processing occurs on the device, with metadata sent through a dedicated data channel. The feature is enabled by default. There are no changes to existing meeting workflows. Remote and in-room participants will simply see improved framing and labeling. Rooms without supported hardware or licensing are not affected and will continue with the current experience. [Action Required/Recommendations] No admin action is required to enable this feature. To take advantage of the enhanced experience, we recommend the following: Ensure Teams Rooms devices are licensed with Teams Rooms Pro. Verify rooms are equipped with certified AI-capable (IC 2.0) cameras. Ensure devices are running a supported Teams Rooms on Windows app version. Review and update internal device procurement guidance to prioritize certified cameras. Inform AV or meeting room support teams about this enhancement. Learn more about supported devices: aka.ms/teamsdevices [Compliance considerations] This feature uses on-device AI processing to improve meeting experiences. Metadata is transmitted through a dedicated data channel. Review based on your organization’s policies. -
Deprecation of Citrix mVPN Support in Microsoft Edge for Android
MC1478969 · planForChange · normal · Updated 09/24/2026 23:49
Services: Microsoft 365 suite
Read message
If your organization does not use Citrix Mobile VPN (mVPN) integration support in Microsoft Edge for Android, you can safely disregard this message. [What and Why:] Microsoft is retiring Citrix Mobile VPN (mVPN) integration support in Microsoft Edge for Android, beginning with Edge version 153. Citrix mVPN integration in Edge for Android depends on legacy third-party components that present ongoing compatibility and maintenance challenges as Android platform requirements continue to evolve. To help ensure a secure, reliable, and supportable experience for Microsoft Edge users, Microsoft will retire Citrix mVPN integration support in Edge for Android. [Rollout Schedule:] Retirement begins in mid-September 2026. [Impact on Your Organization:] Who is affected: Organizations that currently use Citrix Mobile VPN (mVPN) integration with Microsoft Edge for Android. Users who rely on Citrix mVPN to access internal corporate resources through Microsoft Edge for Android. Admins responsible for mobile access, Android device support, or Edge for Android configuration. Platforms/Services: Microsoft Edge for Android Citrix Mobile VPN (mVPN) Android devices What will happen: Microsoft Edge for Android will no longer integrate with Citrix Mobile VPN (mVPN). Users who rely on Citrix mVPN to access internal corporate resources through Edge for Android may need to migrate to an alternative supported mobile access solution. Existing workflows that depend specifically on Citrix mVPN integration in Edge for Android may no longer function as expected. This change affects only Citrix mVPN integration and does not impact other Microsoft Edge for Android capabilities. [Action Required/Recommendations:] Administrators should take the following actions: Identify affected users: Determine whether your organization currently uses Citrix Mobile VPN (mVPN) with Microsoft Edge for Android. Review dependencies: Assess business workflows, applications, and internal sites that depend on Citrix mVPN integration in Edge for Android. Plan a migration strategy: Evaluate and validate alternative supported mobile access solutions that meet your organization's requirements. Communicate with impacted users: Inform users of the upcoming change and provide guidance on approved replacement solutions. Complete migration before retirement: Ensure affected users transition away from Citrix mVPN-dependent workflows before support is removed. [Compliance considerations:] No compliance considerations identified. Review as appropriate for your organization. -
SharePoint: Improved site metadata size reporting
MC1478966 · preventOrFixIssue · normal · Updated 09/24/2026 23:47
Services: SharePoint Online
Read message
[What and Why:] Microsoft is improving how site metadata size is reported in SharePoint. The calculation will include document library field data, giving admins a more complete view of a site’s metadata usage. Nothing about your content changes. No content is added, moved, or removed, and the site metadata size limit remains 1 TB per site. Because the calculation is more complete, reported metadata size may be higher for some sites. For most sites, the difference will be small and nothing else will change. Some sites may show a size at or above the 1 TB limit once the updated calculation is applied. [Rollout Schedule:] General Availability, Worldwide: We will begin rolling out on October 20, 2026. Sites already identified as expected to reach or exceed the 1 TB metadata limit will be excluded from the initial rollout to provide additional time to reduce their metadata usage before the correction is applied. [Impact on Your Organization:] Who is affected: SharePoint admins who monitor site storage and metadata usage. Organizations with SharePoint sites that are close to or above the 1 TB site metadata limit. Site owners and users of sites that receive metadata warnings or enforcement messages. Platforms/Services: SharePoint Online. SharePoint Storage Metrics. SharePoint document libraries and lists. What will happen: Most organizations will see no change in behavior. The visible difference is that reported site metadata size may be higher than before because document library field data is included in the calculation. For sites that cross the 1 TB metadata limit after the correction, the site is blocked from adding new metadata until usage is brought back under the limit. Existing content stays in place and remains accessible. SharePoint shows a warning or error message when the site is close to, or has reached, the metadata limit. For sites that reach 80% of the metadata limit, admins can review the metadata size breakdown on the Storage Metrics page. [Action Required/Recommendations:] No action is needed for most organizations. If you see a metadata warning for a site, review its metadata usage and take steps to reduce it: Check the Storage Metrics page for the site. For sites at or above 80% of the metadata limit, the metadata size breakdown is available on this page. Delete unneeded items from your lists and document libraries. Delete older file versions in your document libraries. Remove duplicate files across lists and libraries. Follow the steps provided in the in-product warning message. Re-check the Storage Metrics page after making changes. If a site remains over the 1 TB metadata limit after the correction is applied, the site will be blocked from adding new metadata until usage is reduced below the limit. Existing content will remain accessible. [Compliance considerations:] Does the change alter how existing customer data is processed, stored, or accessed?Yes. SharePoint metadata size reporting will include document library field data, giving admins a more complete view of site metadata usage. Content is not added, moved, or removed. Does the change modify, interrupt, or disable retention policies, holds, or deletion workflows?Yes. Sites that exceed the 1 TB metadata limit can be blocked from adding new metadata until usage is reduced below the limit, which may affect creation or update actions that add metadata. Does the change alter how admins can monitor, report on, or demonstrate compliance activities?Yes. Admins will see a more complete metadata size calculation on the Storage Metrics page and may see warning or error messages when a site is close to or over the limit. -
Microsoft 365 profile card: View dotted-line managers in the organization panel
MC1478957 · stayInformed · normal · Updated 09/24/2026 23:36
Services: Microsoft 365 suite
Read message
[What and why] We're introducing an additive user interface update to the organization panel in the Microsoft 365 profile card that can display a person's dotted-line manager relationship, in addition to their direct manager, when that data is available. This update helps employees better understand organizational structures in companies where reporting relationships span projects, business units, regions, or functions. [Rollout schedule] General Availability (Worldwide): Rollout begins in early October 2026 and is expected to complete by late October 2026. [Impact on your organization] Who is affected Users in organizations that provide dotted-line manager relationship data. Platforms and services Microsoft 365 profile card What will happen Users may see an additional manager relationship in the organization panel representing a dotted-line manager. Organizations may use different labels for this relationship, such as People Lead or Capability Manager. Users can open the dotted-line manager's profile directly from the profile card to learn more about that person's role and organizational context. This is an additive update to the user interface. If dotted-line manager data is not available, no additional manager relationship will be shown. [Action required and recommendations] No action is required. If your organization wants dotted-line manager relationships to appear in the Microsoft 365 profile card: Ensure dotted-line manager attributes exist in your HR system and are available for ingestion. Confirm your HR integration is configured through supported organizational data integrations, such as SAP SuccessFactors or Workday. Review internal help desk guidance and documentation so support teams understand why users may see an additional manager relationship label in the organization panel. The displayed relationship name depends on your HR system's role labels. [Learn more] Overview of people relationships in Microsoft 365 - Microsoft 365 admin | Microsoft Learn Use your organizational data in Microsoft 365 and Microsoft Viva - Microsoft 365 Apps | Microsoft Learn [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
Final reminder: Microsoft Project Online retires on September 30, 2026
MC1478955 · planForChange · normal · Updated 09/24/2026 23:32
Services: Project for the web
Read message
[What and why:] Microsoft Project Online will retire on September 30, 2026. If users are still using Project Online, they will see an in-app banner announcing the retirement. If your organization will not be fully migrated by September 30, 2026, we highly recommend you contact a Microsoft partner immediately to make a migration plan and let your Microsoft account team know your plans. At Microsoft, we are committed to empowering every organization with a unified, AI-powered and collaborative work management experience that brings together tasks, plans, and projects in one seamless platform. As part of this commitment, we announced the retirement of Project Online last September. The decision reflects our focus on delivering solutions that are modern, scalable, and future-ready—enabling organizations to benefit from the latest innovations in AI, automation, and collaboration. Moving to our next-generation platforms brings enhanced productivity, deeper integration with Microsoft 365, and new capabilities designed for the way people work today and tomorrow. This update is exclusive to Project Online and does not affect Project desktop/Project Online desktop, Project Server, or Planner. We recognize that every organization is unique, with different project management needs and technical requirements. To ensure a smooth transition and continued success, Microsoft is providing three clear paths forward. Microsoft Planner: For organizations seeking a modern, cloud-first, and AI-powered project management experience, Planner is designed for flexibility, collaboration, and scalability—empowering teams to manage everything from simple tasks to complex projects in one unified platform. The premium features of Planner included in our Planner and Project Plan 3 license, offer advanced features such as portfolios, baselines, dependencies, and Gantt charts. Project Server Subscription Edition: For organizations with advanced project and portfolio management (PPM) requirements, or those needing a short-term solution before moving to the cloud, Project Server Subscription Edition offers comprehensive tools for planning, scheduling, and resource management—built on the latest SharePoint Server technology. Project Operations: For Dynamics ERP customers, especially those focused on timesheets and resource scheduling. [Rollout schedule:] Worldwide, GCC, GCC High, DoD: September 30, 2026. [Impact on your organization:] After Project Online is retired, you will no longer be able to access your projects or any associated data within the service. To avoid disruption and potential data loss, it's essential that you complete your transition to any of the alternatives before the retirement date. You can get details about your organization's Project Online usage by following the Export user data from Project Online documentation. [Action required / Recommendations:] Identify a Microsoft Partner immediately to help you move off Project Online by month end. To find a partner, contact your Microsoft Sales Representative for a list of recommended partners in your region. Evaluate the alternatives proposed above and plan the transition immediately. Migrate your data, if needed, before the retirement date. This retirement will happen automatically on the specified dates with no admin action required. You may want to notify your users and update any internal documentation to reflect the above changes. Review documentation to learn more about how to Prepare for Project Online retirement. -
Microsoft 365 Apps: Cloud Update - Extended rollback support for Monthly Enterprise Channel
MC1478946 · stayInformed · normal · Updated 09/24/2026 23:19
Services: Microsoft 365 suite, Microsoft 365 apps
Read message
[What and Why:] Cloud Update is expanding rollback options for devices on Monthly Enterprise Channel. Administrators will be able to roll back devices to a release from two versions prior, with the latest available security updates for that release, and keep devices in the rolled-back state across subsequent releases until they are ready to resume updates. This provides additional time to investigate and resolve compatibility issues while maintaining security coverage and centralized control through the Microsoft 365 Apps admin center. [Rollout Schedule:] General Availability (Worldwide): We will begin rolling out in September 2026 and expect to complete by late September 2026. [Impact on Your Organization:] This feature gives administrators an additional recovery option for Monthly Enterprise Channel devices managed by Cloud Update. If an update causes a compatibility or operational issue, administrators can roll back affected devices to a release from two versions prior, with the latest available security updates for that release. Devices can remain on the selected version across subsequent releases until the administrator chooses to resume updates. Existing update profiles and devices will not be changed or rolled back automatically. [Action Required/Recommendations:] No action is required before rollout. The additional rollback option will become available automatically in the Microsoft 365 Apps admin center. Administrators should review their rollback and recovery procedures, identify who is authorized to initiate a rollback, and update internal support documentation as needed. Before using the feature, assess the affected devices or groups and establish a plan to resume updates after the underlying issue is resolved. [Compliance considerations:] Does the change include an admin control and, can it be controlled through Entra ID group membership?Yes. The feature includes or affects admin controls, policies, permissions, roles, authentication, or management settings as described in this message. Review the linked documentation or admin center controls for group-based configuration support. -
Windows Deployment Services (WDS) deprecation in the next Windows Server release
MC1478819 · stayInformed · normal · Updated 09/24/2026 22:03
Services: Windows
Read message
What and why: Microsoft plans to deprecate the Windows Deployment Services (WDS) server role beginning with the next release of Windows Server. This includes the inbox WDS role, WDS services, management tools, and interfaces, and WDS-provided Preboot Execution Environment (PXE) boot functionality. Begin planning your migration to alternatives. For example, Microsoft Configuration Manager provides a better, more flexible, and feature-rich experience for deploying Windows images. Rollout schedule: 2021: Windows Setup workflows that use boot.wim from installation media in WDS mode were deprecated for Windows 11 and later Windows releases. Custom-image PXE scenarios remained available. April 2026: WDS hands-free deployment scenarios were disabled by default and became unsupported after installation of Windows updates released on or after April 14, 2026. Next Windows Server release: The WDS server role and associated inbox WDS functionality are planned for deprecation. Impact on your organization: If your organization uses WDS, there’s no immediate functionality change. WDS remains available on currently supported Windows Server releases according to their published servicing lifecycles. However, deprecation period is designed to begin migration to newer and better alternatives before eventual removal. Action required/recommendations: To start planning your migration: Inventory WDS deployments. Identify indirect dependencies. Validate alternatives. Plan capacity changes. Retain supported systems during transition. For detailed guidance and special migration considerations, see Windows Deployment Services (WDS) deprecation in the next Windows Server release. If you have a scenario not covered here, please post your question on the Windows Server for IT Pro discussion board. Compliance considerations: No compliance considerations are identified. Review as appropriate for your organization. -
(Updated) Microsoft Teams: AI-powered notes for in-person meetings with Facilitator in Teams Rooms on Android
MC1307888 · stayInformed · normal · Updated 09/24/2026 15:59
Services: Microsoft Teams
Read message
Updated September 24, 2026: We have updated the timeline. Thank you for your patience. [Introduction] To support more effective in-person collaboration, Microsoft Teams is expanding AI-powered meeting notes with the Facilitator agent to Teams Rooms on Android. This enhancement allows teams meeting in a physical room to capture real-time notes, decisions, and action items—without requiring a scheduled or hybrid meeting. The experience is designed to ensure notes are securely stored in your tenant while no data remains on the room device after the meeting ends. This message is associated with Microsoft 365 Roadmap ID 56700. [When this will happen] General Availability Worldwide and GCC: We will begin rolling out in early November 2026 (previously late October) expect to complete by early December 2026 (previously mid-November). [How this affects your organization] Who is affected Organizations using Teams Rooms on Android Rooms licensed with Teams Rooms Pro What will happen During an in-person meeting, users can start AI-powered notes by selecting the Take notes button on the Teams Rooms console. Notes appear on the front-of-room display or touch board during the meeting: Notes are stored in tenant-owned SharePoint embedded storage. Access to notes requires adding your work account using the Access notes button on the Teams Rooms console. After the meeting, notes can be viewed and edited by participants with access via the meeting recap in the meeting chat on the Teams desktop client. If no participant was added during the note-taking session via Access notes, notes are deleted automatically. Default state: The feature is available automatically once licensing and prerequisite configurations are met. No additional admin enablement is required beyond existing settings. [What you can do to prepare] No immediate action is required if your organization already meets the prerequisites. To prepare: Confirm Teams Rooms Pro licenses are assigned to applicable rooms. Ensure Facilitator is enabled in your tenant. Verify Loop components are enabled:IsLoopEnabled IsCollabMeetingNotesFluidEnabled Ensure meeting transcription is enabled in Teams meeting policies. Consider notifying helpdesk staff and users about:How to start notes in an in-person meeting Where notes are stored and accessed after the meeting Learn more: Allow Facilitator in the Teams admin center - Set up Facilitator in Microsoft Teams | Microsoft Teams | Microsoft Learn Meetings - Admins- Manage transcription and captions for Teams meetings | Microsoft Teams | Microsoft Learn Settings management for Loop functionality in Teams - Admin policies for Loop components and Loop workspaces | Microsoft 365 | Microsoft Learn [Compliance considerations] QuestionAnswer Does the change store new customer data, and if so, where, and is the data cached or permanently stored?Yes. Meeting notes generated by Facilitator are stored in tenant‑owned SharePoint Embedded storage. No meeting data is stored or cached on the Teams Rooms device after the meeting ends. Does the change alter how existing customer data is processed, stored, or accessed (for example, documents, emails, or chats)?Yes. Meeting audio and transcription data are processed to generate AI‑powered meeting notes, including summaries, decisions, and action items. Access to the notes occurs through the meeting recap in the meeting chat on Teams desktop client. Does the change introduce or significantly modify AI/ML or agent capabilities that interact with or provide access to customer data?Yes. The Facilitator agent uses AI to generate real‑time meeting notes, summaries, decisions, and action items based on in‑person meeting content. Does the change provide users a new way of interacting with generative AI, and if so, how?Yes. Users can initiate AI‑generated meeting notes during an in‑person meeting by selecting “Take notes” on the Teams Rooms console. Does the change include an admin control, and can it be controlled through tenant configuration?Yes. Availability of the feature depends on existing tenant settings, including Teams Rooms Pro licensing, Facilitator enablement, Loop component settings, and meeting transcription policies. -
Microsoft Defender for Endpoint: Support for Amazon Linux 2 (ARM64) retiring October 31, 2026
MC1392568 · planForChange · normal · Updated 09/23/2026 23:45
Services: Microsoft Defender XDR
Action required by: 10/31/2026 07:00
Read message
Updated September 23, 2026: We have updated this post as a reminder. Thank you for your patience. [What and Why] We are retiring support for Microsoft Defender for Endpoint (MDE) on Amazon Linux 2 (AL2) running on ARM64 architecture, effective October 31, 2026. [Schedule] Retirement effective: October 31, 2026 After this date, support and updates will no longer be available. [Impact on Your Organization] Who is affected Organizations using Microsoft Defender for Endpoint on Amazon Linux 2 (ARM64) Organizations using AL2 on AMD64/x86_64 are not affected Platforms/Services Microsoft Defender for Endpoint Amazon Linux 2 (ARM64) What will happen Defender versions released after this build will not install on AL2 (ARM64) due to platform incompatibility. Version 101.25122.0004 is the last supported version for this platform. After October 31, 2026:No security updates No bug fixes No technical support Devices remaining on this platform may:Miss new features, detection improvements, and protection enhancements Be exposed to increased security and stability risks over time [Action Required / Recommendations] Action required by October 31, 2026. Admins should: Identify devices running Amazon Linux 2 (ARM64) with Defender for Endpoint. Prevent upgrades beyond version 101.25122.0004 on those devices. Plan migration to a supported Linux distribution for MDE. Complete migration before October 31, 2026. No action is required for devices running Amazon Linux 2 on AMD64/x86_64 architectures. Learn more: Prerequisites for Microsoft Defender for Endpoint on Linux | Microsoft Defender for Endpoint | Microsoft Defender | Microsoft Learn [Compliance Considerations] No compliance considerations identified. Review as appropriate for your organization. -
Microsoft Word for the web: Retirement of the "@" entity insertion experience on the document canvas
MC1478006 · planForChange · normal · Updated 09/23/2026 21:52
Services: Microsoft 365 apps
Read message
[What and why] Microsoft is retiring the CIQ-based "@" entity insertion experience on the document canvas in Word for the web. This retirement aligns Word for the web with the experience available in other Microsoft 365 applications, including Word desktop, Excel, and PowerPoint, where this entry point is no longer available. As part of this change, users will no longer be able to invoke the CIQ menu from the document canvas by typing "@". This retirement does not affect @mentions in comments. [Rollout schedule] Retirement (Worldwide, GCC, GCC High, and DoD): Beginning in late October 2026 and expected to complete by late October 2026 [Impact on your organization] Who is affected Users who currently use the CIQ "@" menu in Word for the web to search for and insert entities into documents Platforms and services Word for the web What will happen The CIQ-based "@" entry point on the document canvas will be removed from Word for the web. Users will no longer be able to use the legacy CIQ menu to search for and insert entities from the document canvas. No replacement experience is included as part of this retirement. @mentions in comments are not affected and will continue to work as before. This change aligns Word for the web with Word desktop, Excel, and PowerPoint, where this entry point is no longer available. No admin controls are available to enable, disable, or postpone this change. [Action required and recommendations] No admin action is required. We recommend that administrators: Inform affected users about the retirement of this feature. Review and update internal documentation, training materials, and support content that reference the CIQ "@" insertion experience. Remove any internal guidance or workflows that depend on the CIQ entity insertion menu. [Compliance considerations] No compliance considerations identified, review as appropriate for your organization. -
Microsoft Teams: Admins can control profanity filtering in meeting transcripts
MC1478003 · stayInformed · normal · Updated 09/23/2026 21:49
Services: Microsoft Teams
Read message
[What and why:] Microsoft Teams is adding a meeting policy that lets administrators control whether profane words are masked in live transcription and saved meeting transcripts. This gives organizations a policy-controlled option for workflows in which words that are currently masked need to remain visible in the transcript. Filtering remains on by default. If an administrator turns filtering off for the policy assigned to a meeting organizer, words that would otherwise be masked can appear in both the live and saved transcript for that organizer's scheduled meetings. This change does not add an organizer-level control and does not change each participant's live-caption profanity preference. [Rollout schedule:] Targeted Release (Worldwide): We will begin rolling out on early October 2026 and expect to complete by mid-October 2026. General Availability (Worldwide, GCC): We will begin rolling out on mid-October 2026 and expect to complete by late October 2026. [Impact on your organization:] Who is affected Teams administrators who manage meeting policies. Meeting organizers whose assigned policy has transcript profanity filtering turned off. Users who view live or saved transcripts for affected scheduled meetings. Who is not affected Users whose meeting organizer is assigned a policy that keeps filtering on. Each participant's live-caption profanity preference; live captions continue to use the participant's existing setting. What will happen A new Filter out profane words in live transcription setting will be available in the applicable Teams meeting policy under Meeting settings > Recording and transcription. The setting will be on by default, preserving the current transcript-masking behavior unless an administrator changes the assigned policy. When the setting is on, profane words are masked in live transcription and in the saved transcript. When the setting is off, words that would otherwise be masked can appear in live transcription and in the saved transcript. The meeting organizer's assigned policy determines the behavior for the meeting. Organizers and co-organizers do not receive a per-meeting override. [Action required / Recommendations:] No action is required to preserve current behavior. Before turning filtering off, confirm the business need and review whether the change aligns with your organization's compliance policies and transcript requirements. Notify compliance, legal, and helpdesk teams that saved transcripts may contain profane words that were previously masked. Update internal transcript guidance if your organization changes the default policy behavior. -
Retirement of Viva Insights (personal insights) and Viva Learning usage reports
MC1477996 · planForChange · normal · Updated 09/23/2026 21:44
Services: Microsoft 365 suite
Read message
[What and why:] The Viva Learning usage report and The Viva Insights personal insights active-user trend chart will be retired from the Microsoft 365 admin center. For Viva Learning, admins can continue to access usage metrics in the Viva Learning app directly. [Rollout schedule:] General Availability (Worldwide): We will begin rolling out on early October 2026 and expect to complete by mid-November 2026. [Impact on your organization:] Who is affected: Microsoft 365 tenant administrators Organizations using Microsoft Viva Insights, or Viva Learning usage reports Platforms/Services: Microsoft 365 admin center Viva Insights Viva Learning What will happen: The Viva Insights personal insights active-user trend chart will be retired. The Viva Learning usage report will be removed from the Microsoft 365 admin center Viva Learning analytics will continue through the Viva Learning reporting experience. [Action required / Recommendations:] Update documentation referencing retired Viva reports. Communicate the reporting location change to reporting administrators. Use Viva Learning reporting within Viva Learning going forward. Review: Reporting in Viva Learning | Microsoft Learn -
Case Management in Microsoft Defender
MC1477993 · stayInformed · normal · Updated 09/23/2026 21:43
Services: Microsoft Defender XDR
Read message
[What and why:] Microsoft Defender is introducing native Case Management to help security teams investigate and resolve threats faster while reducing tool sprawl. Teams can manage investigations, assign analysts, monitor resolution SLAs, and capture investigation notes in a unified case experience. Security teams often coordinate investigations across multiple tools, making it harder to maintain context, track ownership, and drive timely resolution. Case Management brings these activities into Microsoft Defender, helping teams streamline investigations and manage response work in one place. Beginning with Incident Cases, the experience combines alerts, attack stories, affected assets, and evidence with the workflows teams use to assign work, collaborate, and track progress through resolution. [Rollout schedule:] Public preview begins: September 23, 2026. Public preview rollout completion: early October 2026. [How this will affect your organization:] Who is affected Microsoft Defender customers with Microsoft 365 E5, E7, Defender Suite and all standalone SKUs (MDE P2, MDO P2, MDA, MDI, MDB) and Microsoft Sentinel Security administrators, SOC analysts, incident responders, and SOC leads using Microsoft Defender for investigation and response. Services affected Microsoft Defender and existing Microsoft Sentinel incident workflows and integrations used with Incident Cases. Case Management enables your organization to: Manage investigations in one place: Bring together Microsoft Defender XDR signals and, when enabled, third-party data in a native Defender case workspace. Establish clear ownership: Assign analysts and keep investigation notes with the case. Track timely resolution: Monitor resolution SLAs and progress. Preserve existing workflows: Existing incident-based workbooks, automation, playbooks, and integrations continue to function with Incident Cases. Retain existing access controls: Incident permissions and access scoping carry over to Incident Cases. For example, a SOC team investigating ransomware can use the case experience to track active investigations, assign analysts, monitor resolution SLAs, and keep relevant investigation notes with each case. [Action required / Recommendations:] No manual migration or reconfiguration of existing incident workflows is required to begin using the Case experience. Each Incident Case maps one-to-one to an Incident during this phase. To prepare: Review how your SOC assigns investigations, captures notes, and tracks resolution targets. Familiarize analysts with the Cases experience and update internal operating guidance. Evaluate existing workflows and integrations as part of your preview adoption. Additional Considerations Initial scope: This launch begins with Incident Cases for incident response, with a one-to-one relationship between an Incident Case and an Incident. Blog: Reimagining Case Management in Microsoft Defender | Microsoft Community Hub Demo video: https://aka.ms/casedemovideo Learning docs: Case management in the Microsoft Defender portal - Microsoft Defender XDR | Microsoft Learn -
(Updated) Microsoft Teams: A refreshed in-meeting experience with simpler controls and a smarter share panel
MC1317197 · planForChange · normal · Updated 09/23/2026 19:36
Services: Microsoft Teams
Read message
Updated September 23, 2026: We have updated the timeline. Thank you for your patience. [What and Why] As Microsoft Teams has added meeting capabilities over time, the meeting controls and share panel have grown crowded, contributing to mis-clicks between high‑impact actions like Share, Leave, and Raise hand, and to accidental shares of unintended content. Drawing on extensive customer feedback and telemetry, we’re introducing two coordinated updates: redesigned meeting and sharing controls. Together, they make core actions easier to find, reduce accidental clicks, and give users more confidence when sharing content. This update supports personal and team productivity by reducing friction in everyday meetings and improving confidence when presenting or sharing content. This message is associated with Microsoft 365 Roadmap ID 560321 and 502520. It applies to Teams for Windows desktop, Teams for Mac desktop, and Teams for the web. [Rollout Schedule] Targeted Release: We will begin rolling out redesigned meeting controls in late July 2026 (previously early July) and expect to complete by mid-August 2026 (previously late July). Redesigned Sharing controls will begin rolling out in September 2026. General Availability (Worldwide): We will begin rolling out in mid-October 2026 (previously late September) and expect to complete by late October 2026 (previously late September). General Availability (GCC, GCC High): We will begin rolling out in late October 2026 (previously late September) and expect to complete by mid-December 2026 (previously late November). General Availability (DoD): We will begin rolling out in mid-December 2026 (previously late November) and expect to complete by early January 2027 (previously late December 2026). [Impact on Your Organization] Who is affected: All Teams work and school users joining meetings Platforms: Teams for Windows desktop Teams for Mac desktop Teams for the web Not in scope: Teams (consumer), iOS, Android, Teams Rooms, Linux What will happen: Meeting controls will be center‑aligned, with microphone, camera, and share grouped together. The Leave button will be separated to reduce accidental exits. Less‑used actions will move into a reorganized More menu. Users can personalize meeting controls by pinning, unpinning, and rearranging controls using drag and drop. Screenshot: New More options menu Users can personalize meeting controls by pinning, unpinning, and rearranging controls using drag and drop. The redesigned share panel may include:Live previews of screens and windows. A tabbed layout A two‑step share confirmation to reduce accidental sharing. Screenshot: Reorganized share panel - not final UI The new experience is enabled by default and cannot be disabled at the tenant level. During rollout, users may opt in early and can temporarily return to the previous experience from Teams settings. Existing meeting app pinning policies will continue to be honored. New meeting app pinning policies will support up to two apps pinned to the main meeting controls, with additional apps available in the More menu. Known limitations: Meeting controls customization preferences (such as pinned controls) do not sync across devices at launch. Preferences persist across meetings on the same client. Cross‑device sync is planned for a future release. The opt‑out toggle for the new meeting experience is controlled by individual users and cannot be managed at the tenant level. This opt‑out is a temporary adoption aid and will be retired in a future release. Microsoft will provide advance notice via a separate Message Center post before removal. [Action Required / Recommendations] No immediate action is required. We recommend that you: Review existing Teams meeting app pinning policies and plan future policies around the two‑app limit. Communicate the redesiged meeting control changes to users, helpdesk, and internal support teams ahead of the July 2026 rollout. Detailed change management guidance for IT Pros/admins, along with an end user visual guide will be published on July 9th 2026: https://adoption.microsoft.com/microsoft-teams/new-meeting-controls-experience. Update internal documentation and training materials to reflect:The new meeting controls layout. User customization options. The updated share panel experience. [Compliance Considerations] No compliance considerations identified, review as appropriate for your organization. -
(Updated) Microsoft Viva Engage: New left navigation controls for collapsing, resizing, and managing favorites
MC1470424 · stayInformed · normal · Updated 09/23/2026 16:42
Services: Microsoft Viva
Read message
Updated September 23, 2026: We have updated the timeline. Thank you for your patience. [What and why] We're introducing enhancements to the Viva Engage left navigation experience that give users more control over how they organize and use the navigation pane. Based on customer feedback, these improvements help users work more efficiently by allowing them to customize navigation, manage larger numbers of favorite communities, and optimize screen space while maintaining the same navigation structure and destinations. [Rollout Schedule] General Availability (Worldwide): We have started rolling out and expect to complete by end of October 2026. [Impact on your organization] Who is affected All Viva Engage users who access Viva Engage on the web, including Viva Engage experiences within Microsoft Teams and Microsoft Outlook. Platforms/Services Viva Engage on the web Viva Engage app in Microsoft Teams Viva Engage app in Microsoft Outlook What will happen The following capabilities will be available in Viva Engage: Collapse the left navigation pane. Resize the width of the left navigation pane. Favorite an unlimited number of communities, increased from the previous limit of 10. Reorder communities in the Favorites section. Additional details: Preferences persist across browsers and devices. Keyboard and screen reader support are included. No changes are being made to navigation destinations or community membership. No admin configuration is required. These capabilities are user initiated and no visible changes occur unless users choose to use them. Collapsible left navigation menu: Collapsed left navigation menu: Resizable left navigation menu: Drag-and-drop to reorder favorites: Unlimited number of favorites: [Action required/Recommendations] No admin action is required. Recommended actions: Inform support and helpdesk teams about the updated navigation experience. Notify community managers and power users who work with large numbers of communities that the favorites limit has been removed. Review and update internal training materials or documentation that reference the Viva Engage left navigation experience. Consider communicating the new capabilities to users so they can take advantage of the improved navigation controls. [Compliance considerations] No compliance considerations identified, review as appropriate for your organization. -
(Updated) The September 2026 Windows non-security preview update is now available
MC1477005 · stayInformed · normal · Updated 09/22/2026 21:31
Services: Windows
Read message
(Updated 9-22-2026: Added a note indicating the September 2026 non-security preview update is the final preview update for Windows 11, version 24H2.) The September 2026 non-security preview update is now available for Windows 11, versions 26H1, 25H2, and 24H2. Information about the contents of this update is available in the release notes, which are accessible from the Windows 11 update history page. To learn more about the different types of monthly quality updates, see Understanding Windows monthly updates. Looking to explore upcoming features and improvements in Windows 11? Check the Windows roadmap. It includes what’s coming to the Windows Insider Program, what's gradually rolling out, and what's generally available. Highlights for the Windows 11, version 25H2 update: You can now remap the Copilot key to function as the Right Ctrl or Context Menu key, helping preserve familiar keyboard shortcuts and accessibility workflows. Camera roll backup in Settings helps eligible users protect their photos with OneDrive. You can turn on the feature from the Settings Home or Accounts page and finish setup on your phone using a QR code. Windows now supports Emoji 17.0, adding new emoji such as distorted face, fight cloud, and hairy creature, and refreshing several existing designs including saluting face, goose, and lotus for better consistency across platforms. To insert them, press Windows key + Period (.) to open the emoji panel. File Explorer now handles downloaded files more flexibly, with a new Preview anyway button for HTML files and automatic previews for non-HTML files such as PDFs, while Home remembers whether each section is expanded or collapsed and the reorganized Details pane shows cloud file thumbnails more reliably. A new Open apps maximized setting automatically maximizes app windows as they open, whether you use a screen reader or magnification, work in tablet mode, or simply prefer a consistent full-screen workspace. For instructions on how to install this update, see the KB article for your operating system listed below: Windows 11, version 26H1: KB5124006 Windows 11, versions 25H2 and 24H2: KB5124010 Note: The September 2026 non-security preview update (KB5124010) is the final preview update for Windows 11, version 24H2. Supported editions of version 24H2 will continue to receive monthly security updates in accordance with their servicing lifecycle. To continue receiving non-security preview updates, please update to a newer version of Windows 11. As a reminder, Windows 11, version 24H2 Home and Pro editions reach end of support in October 2026. Note: With recent and upcoming Windows updates over the next few months, a limited number of consumer and business devices might experience one additional restart during installation. This one‑time restart occurs after a Secure Boot certificate update is applied as part of the Secure Boot update process. -
(Updated) Microsoft Teams: Specify who has control of production tools in meetings and webinars
MC1443520 · stayInformed · normal · Updated 09/22/2026 20:31
Services: Microsoft Teams
Read message
Updated September 22, 2026: We have updated the timeline. Thank you for your patience. [What and why] Microsoft Teams is introducing a new meeting option for meetings with presenters and webinars that allows organizers to specify who has control of production tools during an event. This helps organizers assign production responsibilities to designated individuals, improving event management and reducing the risk of unintended changes during live events. This message is associated with Microsoft 365 Roadmap ID 567305. [Rollout schedule] Targeted Release: Beginning in mid-August 2026 and expect to complete by late August 2026 General Availability (Worldwide, GCC, GCC High, DoD): Beginning in late August 2026 and expect to complete by end of October 2026 (previously mid-September) [Impact on your organization] Who is affected Organizers of meetings with presenters and webinars in Microsoft Teams Designated production staff who support live events Platforms/Services Microsoft Teams Teams desktop app Teams web app What will happen Organizers will see a new meeting option called Who has control of production tools: This option will be enabled by default for eligible meetings with presenters and webinars. Organizers can designate specific users to manage production experiences during an event. Designated users will have access to controls in Manage what attendees see. Designated users will have access to Green Room controls. Event organizers can separate production responsibilities from presenter responsibilities when needed. [Action required and recommendations] No admin action is required. This capability will be available by default once rolled out. We recommend that you: Inform users who organize webinars and presenter-led meetings about this new capability. Update internal training or event-production documentation, if applicable. Review planned live event workflows to determine whether dedicated production staff should be assigned using this new option. Learn more Control town hall production tools in Microsoft Teams | Microsoft Support [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
(Updated) Microsoft Teams: Enhanced delegated calling with delegate call access restrictions and join notifications
MC1429012 · planForChange · normal · Updated 09/22/2026 20:29
Services: Microsoft Teams
Read message
Updated September 22, 2026: We have updated the timeline. Thank you for your patience. [What and Why:] Microsoft is enhancing Microsoft Teams call delegation with new controls that provide greater privacy, transparency, and control during active calls. Delegators will be able to lock active calls to prevent delegate participation and optionally enable warning tones that notify participants whenever a delegate joins or resumes a call. These enhancements help users manage sensitive conversations more effectively while improving awareness during delegated call handling. This message is associated with Roadmap ID 567306. [Rollout Schedule:] Targeted Release (Worldwide): We will begin rolling out in early August 2026 and expect to complete by mid-August 2026. General Availability (Worldwide): We will begin rolling out in mid-August 2026 and expect to complete by mid-August 2026. General Availability (GCC, GCC High): We will begin rolling out in mid-August 2026 and expect to complete by late August 2026. General Availability (DoD): We will begin rolling out in mid-August 2026 and expect to complete by end of October 2026 (previously mid-September). [Impact on Your Organization:] Who is affected: Users with Microsoft Teams call delegation configured. Executives, administrative assistants, managers, and support personnel who use delegated calling. Platforms/Services: Microsoft Teams Teams Calling Teams desktop Teams web What will happen: A new Lock an Ongoing Call capability will be available to delegators. Screenshot 1: During an active call, delegators can use the new Lock call control from the meeting toolbar to restrict delegate participation in sensitive conversations: Screenshot 2: Delegators can lock an active Teams call directly from the Calls experience, preventing delegates from joining or resuming the call until it is unlocked: Delegators can lock an active call to prevent delegates from: Resuming a call that has been placed on hold. Joining an ongoing active call. Delegates will continue to see locked calls in their call history. Delegates will be unable to participate in locked calls until the delegator unlocks the call. A new optional Warning Tone for Delegate Participation setting will be available. Screenshot 3: New call delegation settings allow users to enable an audible notification that alerts participants whenever a delegate joins or resumes a delegated call: When enabled, all call participants will hear an audible notification when a delegate: Joins an active call. Resumes a held call. The feature increases transparency regarding delegate participation in live calls. This change will be available by default to users with call delegation configured. No existing call delegation workflows are removed. [Action Required/Recommendations:] No immediate administrative action is required. Recommended actions: Review how call delegation is used within your organization. Inform users who utilize delegated calling about the new lock and notification capabilities. Update internal Teams calling documentation and training materials. Notify help desk and support teams of the new user experience to prepare for potential questions. Evaluate whether the delegate participation warning tone should be recommended for users handling confidential or sensitive conversations. Monitor Microsoft's official documentation for feature configuration details as rollout approaches. Learn more: Share a phone line with a delegate in Microsoft Teams | Microsoft Support (will be updated for GA rollout) [Compliance Considerations:] Compliance Question Explanation Does the change provide a new way of communicating between users, tenants, or subscriptions? The feature introduces new delegated calling controls that affect how delegates can participate in ongoing calls. It also adds an optional audible notification that informs all call participants when a delegate joins or resumes a delegated call, increasing transparency during communications. Does the change allow a user to enable and disable the feature themselves? Delegators can lock and unlock ongoing calls and can enable or disable the warning tone notification setting for delegate participation. -
(Updated) Scoped SharePoint search in Teams (SharePoint app, also called Viva Connections)
MC1332816 · stayInformed · normal · Updated 09/22/2026 20:27
Services: SharePoint Online, Microsoft Teams
Read message
Updated September 22, 2026: We have updated the timeline. Thank you for your patience. [What and Why:] We’re improving search behavior when users use the SharePoint app inside Microsoft Teams. When users search from Teams while they’re in the SharePoint app (also known as Viva Connections), search results and suggestions will be scoped to SharePoint content, helping users find relevant information faster without leaving Teams. This message is associated with Microsoft 365 Roadmap ID 562015. [Rollout Schedule:] General Availability (Worldwide): We will begin rolling out end of June 2026 (previously mid-June) and expect to complete by mid-July 2026. General Availability (GCC, GCC High): We will begin rolling out in end of June 2026 (previously mid-June) and expect to complete by mid-August 2026. General Availability (DoD): We will begin rolling out in end of June 2026 (previously mid-June) and expect to complete by end of October 2026 (previously mid-September). [Impact on Your Organization:] Who is affected: Users of the SharePoint app in Teams (Viva Connections) across all clouds Platforms/Services: Microsoft Teams SharePoint Online Viva Connections What will happen: When users select the Search icon in Teams while inside the SharePoint app (Viva Connections), search results are scoped to SharePoint global search. SharePoint search suggestions will appear directly in Teams. Pressing Enter opens the SharePoint search results page in SharePoint. The feature is enabled by default. Existing SharePoint permissions and search security trimming are respected. No changes are required to existing admin configurations or policies. Screenshot: Search results are scoped to SharePoint when search is initiated from within the SharePoint app in Teams: Learn more: Viva Connections on mobile devices | Microsoft Support (will be updated before rollout) [Action Required / Recommendations:] No action is required from administrators. Consider the following recommendations: Inform helpdesk and end users that search behavior within the SharePoint app in Teams is becoming more targeted and SharePoint‑specific. Update internal documentation or training materials that reference Teams or SharePoint search behavior. Review SharePoint search configuration and content hygiene (optional) to ensure optimal results quality. [Compliance considerations:] No compliance considerations identified, review as appropriate for your organization. -
(Updated) Assign open shifts in Microsoft Teams Shifts
MC1324280 · stayInformed · normal · Updated 09/22/2026 20:26
Services: Microsoft Teams
Read message
Updated September 22, 2026: We have updated the timeline. Thank you for your patience. [What and Why:] Assign open shifts is a new Microsoft Teams Shifts capability that helps managers build schedules more efficiently. Managers can enter shifts that need coverage as open shifts, then use Assign open shifts to automatically assign those shifts within a schedule group based on employee availability, approved time off, historical scheduling patterns, and configured scheduling rules. Managers can review and adjust assignments before publishing the schedule. This message is associated with Microsoft 365 Roadmap ID 562535. [Rollout Schedule:] General Availability (Worldwide): Rollout begins in mid-June 2026 and is expected to complete by end of October 2026 (previously mid-September). [Impact on Your Organization:] Who is affected: Frontline managers who create or manage schedules using Microsoft Teams Shifts. Platforms/Services: Microsoft Teams (Shifts) on web and desktop. What will happen: A new “Assign open shifts” button appears for users with scheduling permissions. Open shifts can be automatically assigned based on availability, time off, historical patterns, and scheduling rules. Managers can review and edit assignments before publishing. Using the feature is optional. Screenshot 1: Select a schedule group and review constraints from the Assign Open Shifts dialog: Screenshot 2: A schedule has been successfully generated: [Action Required / Recommendations:] No action is required. Admins may choose to share documentation and update internal guidance for scheduling managers. Learn more: Auto-assign open shifts - Microsoft 365 for frontline workers | Microsoft Learn [Compliance considerations:] AreaExplanation Does the change alter how existing customer data is processed?The feature uses existing Shifts data (availability, time off, scheduling rules, historical patterns) to generate suggested assignments, without introducing new data types. Does the change include an admin control and can it be controlled through Entra ID group membership?Visibility of the feature is governed by existing Shifts scheduling permissions, which can be managed through role and group-based access. Does the change allow a user to enable or disable the feature themselves?Managers can choose whether or not to use Assign Open Shifts during scheduling. -
(Updated) Microsoft Teams: Front-of-room view control for Webinars and structured meetings in Teams Rooms on Android
MC1316231 · planForChange · normal · Updated 09/22/2026 20:23
Services: Microsoft Teams
Read message
Updated September 22, 2026: We have updated the timeline. Thank you for your patience. [Introduction] We're introducing an update to how front-of-room (FoR) displays behave in Microsoft Teams Rooms on Android during webinars and structured meetings. This change ensures that when a Teams Room joins as a presenter, the in-room display defaults to the attendee view—creating a clearer and more professional experience for in-room participants, especially in hybrid scenarios where presenters and attendees are co-located. This message is associated with Roadmap ID 559602. [When this will happen:] General Availability (Worldwide): We will begin rolling out in mid-June 2026 (previously early June) and expect to complete by end of October 2026 (previously mid-September). General Availability (GCC, GCC High, DoD): We will begin rolling out in mid-June 2026 and expect to complete by end of October 2026 (previously mid-September). [How this affects your organization:] Who is affected: Organizations using Microsoft Teams Rooms on Android Meeting organizers and presenters running webinars or structured meetings In-room participants viewing front-of-room displays A Teams Rooms Pro license is needed to use this feature What will happen: The front-of-room display will default to attendee view when joining webinars or structured meetings. In-room audiences will not see presenter tools such as Green Room or backstage controls. Presenters will retain full control from the Teams Rooms console, including: Managing Green Room and off-stage participants. Switching display modes (e.g., to presenter view when needed). The feature is enabled by default and requires no configuration. There is no impact to remote attendees or their experience. Existing Teams Rooms functionality and policies remain unchanged. Screenshot 1: Front-of-room webinar experience with Manage screen mode on and the user in presenter view: Screenshot 2: Console view in presenter view: Screenshot 3: Front-of-room webinar experience with the user in attendee view: Screenshot 4: Console view with the user in attendee view: [What you can do to prepare:] No action is required to enable this feature. Verify device readiness: Ensure Teams Rooms on Android devices are updated. Validate meeting room setup: Confirm displays and consoles function as expected. Educate organizers and presenters on the updated experience. Update internal documentation. [Compliance considerations:] No compliance considerations identified, review as appropriate for your organization. -
(Updated) Microsoft Teams: Identify external bots joining your Teams meetings
MC1251206 · stayInformed · normal · Updated 09/22/2026 20:19
Services: Microsoft Teams
Read message
Updated September 22, 2026: We have updated the timeline. Thank you for your patience. [Introduction] AI‑powered meeting assistant bots—such as transcription and summarization services—are increasingly used to enhance productivity in online meetings. While these tools can be valuable, some bots may access meetings without the knowledge or consent of the meeting organizer or the hosting tenant, which can create data security, privacy, and compliance risks. To help organizations protect meeting content and increase visibility into automated participants, Microsoft Teams is introducing a new capability that detects external meeting assistant bots as they attempt to join meetings. This update gives organizers greater awareness and control and provides administrators with clear controls to manage how detected bots are handled in meetings hosted across the organization. This message is associated with Microsoft 365 Roadmap ID 558107. [When this will happen] Targeted Release: We will begin rolling out in mid-May 2026 and expect to complete by early June 2026. General Availability (Worldwide): We will begin rolling out in early June 2026 and expect to complete by end of October 2026 (previously mid-September). General Availability (GCC): We will begin rolling out in early June 2026 and expect to complete by end of October 2026 (previously mid-September). [How this will affect your organization] Who is affected All organizations using Microsoft Teams meetings, including GCC tenants Meeting organizers and Teams administrators What will happen Teams will detect external meeting bots as they attempt to join meetings hosted by your organization. When detected, bots will be clearly labeled in the meeting lobby experience. Note: There might still be bots that are undetected by the system due to their intrinsic behavior. Please inform your users to report them out directly from the app/meeting. This will help us improve our detection system. Organizers will be able to: approve or deny detected bots from the meeting lobby. see clearly which participants have been identified as bots. remove detected bots during the meeting if necessary. These organizer controls are designed to help ensure that bot participation in meetings is an intentional and informed decision. A new meeting policy will be available in the Teams admin center that allows admins to configure how detected bots are handled (do not detect bots, require approval). In the future, we intend to provide more granular controls to admins, as appropriate. Bot detection will be enabled by default for all tenants. Teams will continue improving detection accuracy; however, some bots may not be detected in all scenarios. [What you can do to prepare] No action is required at this time. However, we recommend that Teams admins: Review the new meeting policy in the Teams admin center once it becomes available. Keep the default setting, which requires organizers to approve detected bots before they join meetings (recommended). Choose a stricter or more permissive option based on your organization’s collaboration and compliance requirements. Inform meeting organizers that they may see new indicators and approval prompts when detected bots attempt to join meetings. Update internal helpdesk or governance documentation if your organization documents meeting join or lobby controls behavior. Monitor future Message center updates for expanded administrative controls. [Compliance considerations] QuestionAnswer Does the change introduce or significantly modify AI/ML or agent capabilities that interact with or provide access to your data?Yes. This change introduces detection logic that analyzes meeting join metadata to identify external automated bots attempting to join meetings. Does the change provide a new way of communicating between users, tenants, or subscriptions?No. The feature only changes how external meeting assistant bots are surfaced to organizers during the meeting join process, increasing visibility of automated external participants. There is no change in the way participants can communicate with these bots or vice versa. Does the change include an admin control, and can it be controlled through Entra ID group membership?Yes. The change introduces a new meeting policy in the Teams admin center that allows admins to define how detected bots are handled. It cannot be controlled through Entra ID group membership at this time. -
(Updated) Microsoft Teams: Building‑level insights on the Teams Rooms Pro Management portal recommended actions page
MC1257308 · stayInformed · normal · Updated 09/22/2026 20:15
Services: Microsoft Teams
Read message
Updated September 22, 2026: We have updated the timeline. Thank you for your patience. [Introduction] We’re adding new building‑level insights to the recommended actions page in the Teams Rooms Pro Management portal. This update helps IT admins identify buildings with high Microsoft Teams Rooms (MTR) utilization that still have bring-your-own-device (BYOD) rooms in them, creating an inconsistent user experience from room to room. These insights support more consistent meeting experiences across buildings and help organizations optimize room‑technology investments. Available with a Teams Rooms Pro or Shared Space license. This message is associated with Microsoft 365 Roadmap ID 553591. [When this will happen] General availability (Worldwide): We will begin rolling out mid-June 2026 (previously early June) and expect to complete by end of October 2026 (previously mid-September). [How this affects your organization] Who is affected Organizations using the Teams Rooms Pro Management portal with Teams Rooms Pro or Shared Device licenses What will happen A new building‑level insights view will appear on the portal’s Recommended actions page: Insights will highlight buildings with high MTR usage and remaining BYOD meeting rooms: These insights are designed to help IT create more consistent room to room experiences for users within a building. No changes will occur to existing configurations, policies, or settings. The feature will be enabled by default for tenants with eligible licenses. [What you can do to prepare] No action is required. If relevant to your organization’s deployment planning, you may: Review your current MTR and BYOD room distribution in the Teams Rooms Pro Management portal. Update internal documentation or planning guidance as needed. Share this update with teams responsible for meeting room technology decisions. [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
(Updated) Microsoft Teams town halls now support backup Real-Time Messaging Protocol (RTMP) streams
MC1261595 · stayInformed · normal · Updated 09/22/2026 20:12
Services: Microsoft Teams
Read message
Updated September 22, 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 end of October 2026 (previously mid-September) [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) Microsoft Teams: Recently used emojis sync across devices
MC1256307 · stayInformed · normal · Updated 09/22/2026 20:10
Services: Microsoft Teams
Read message
Updated September 22, 2026: We have updated the timeline. Thank you for your patience. [Introduction] We’re releasing an improvement to Microsoft Teams that syncs your recently used emojis and reactions across devices. With this update, users will see the same set of “recently used” emojis when using Teams on Android, iOS, Mac, Windows desktop, and Teams for the web, creating a more consistent and seamless experience when communicating across chats and channels. This enhancement aligns with customer feedback requesting a unified emoji experience across platforms. This message is associated with Microsoft 365 Roadmap ID 554927. [When this will happen] Targeted Release: We expect to complete rollout by mid-July 2026 (previously mid-June). General Availability (Worldwide): We will begin rolling out in mid-July 2026 (previously mid-June) and expect to complete in late July 2026 (previously late June). General Availability (GCC and GCCH): We will begin rolling out in mid-July 2026 (previously mid-June) and expect to complete by end of October 2026 (previously mid-September). General Availability (DoD): We will begin rolling out in mid-August 2026 (previously mid-July) and expect to complete by end of October 2026 (previously mid-September). [How this affects your organization] Who is affected All Microsoft Teams users across supported clients. What will happen Recently used emojis and reactions will sync across devices. Users will see the same “recently used” list regardless of which Teams client they use. The feature will be enabled by default; no configuration is required for rollout. Existing Teams admin settings and messaging policies will continue to apply. There is no impact to message flow, data storage, compliance boundaries, or customer data pathways. [What you can do to prepare] No action is required. This update will roll out automatically. Admins may optionally: Inform helpdesk or support teams about this user experience update. Update internal documentation if you reference emoji behavior or Teams UI details. Review your Messaging settings and Messaging policies if you manage custom emoji usage. Learn more about emoji and reaction usage in Microsoft Teams: Send an emoji, GIF, or sticker in Microsoft Teams | Microsoft Support [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. This feature does not introduce new data storage, processing changes, AI/ML capabilities, communication pathways, admin reporting changes, or modifications to Purview‑governed workflows. -
(Updated) Microsoft Teams: New user setting to view incoming calls in a small window
MC1045221 · stayInformed · normal · Updated 09/22/2026 20:07
Services: Microsoft Teams
Read message
Updated September 22, 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 October 2026 (previously mid-September). [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. -
Microsoft SharePoint: Changes to the FAQ web part authoring experience
MC1476319 · planForChange · normal · Updated 09/21/2026 22:20
Services: SharePoint Online
Read message
[What and why] We are updating the SharePoint FAQ web part authoring experience. The FAQ web part will provide a standard, non-AI experience for manually creating, editing, and managing FAQ content. AI-assisted FAQ creation and import capabilities will move to the Copilot in SharePoint authoring experience, where authors can use natural language prompts and selected grounding sources to generate FAQ content that is saved to the compatible FAQ web part. Existing FAQ web parts and their content will continue to render; no content migration is necessary. [Rollout schedule] General Availability (Worldwide and GCC): Rollout begins in late October 2026 and is expected to complete in early November 2026. [Impact on your organization] Who is affected SharePoint authors who create or edit FAQs on SharePoint Pages and News posts. Users who use AI-assisted authoring to generate or import FAQ content. Platforms and services SharePoint Online SharePoint News posts SharePoint FAQ web part Copilot in SharePoint What will happen Authors can continue to manually create and manage FAQ content directly in the FAQ web part without using AI. AI-assisted FAQ creation and import capabilities will move from the FAQ web part to the Copilot in SharePoint authoring experience. Authors will be able to use natural language prompts and selected grounding sources in Copilot in SharePoint to generate FAQ content. Generated FAQ content will be saved to the compatible FAQ web part. Existing FAQ web parts and their content will continue to render as they do currently; no content migration is required. Add an FAQ web part to a page or news post: Manually input FAQ content: [Action required and recommendations] No administrative action is required. We recommend that you: Inform SharePoint authors and site owners about this change to the FAQ authoring experience. Review and update internal training materials, support documentation, and governance guidance that reference the current AI-assisted FAQ authoring workflow. [Learn more] Authoring with Copilot in SharePoint: An overview | Microsoft Support [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
Dynamics 365 Field Service – Automate optimizations with Scheduling Operations Agent (Preview)
MC1476008 · stayInformed · normal · Updated 09/21/2026 18:58
Services: Dynamics 365 Apps
Read message
We are announcing the ability to automatically schedule and run recurring optimizations through the Scheduling Operations Agent in Dynamics 365 Field Service. This feature will reach public preview on September 30, 2026. How does this affect me? This feature enables the following capabilities:Configure recurring optimization schedules: Create optimization plans that automatically run on a defined schedule, eliminating the need to manually start each optimization run. Customize optimization goals: Add and weigh optimization objectives to better reflect organizational priorities and desired scheduling outcomes. Automatically apply optimized schedules: The Scheduling Operations Agent evaluates resource availability, existing schedules, and unscheduled requirements, then optimizes and applies schedules based on configured constraints and goals. What do I need to do to prepare? This message is for awareness, and no action is required. If you would like more information on this feature, please visit Scheduling Operations Agent overview. -
(Updated) Surveys agent retirement and transition to Copilot in Microsoft Forms
MC1421920 · planForChange · normal · Updated 09/21/2026 17:22
Services: Microsoft Forms
Read message
Updated September 21, 2026: We have updated the timeline. Thank you for your patience. [What and Why:] Microsoft is retiring the Surveys agent and transitioning customers to a unified, Copilot-powered experience within Microsoft Forms. This change streamlines form creation, data collection, and analysis into a single, integrated experience—improving productivity and providing more advanced AI-driven capabilities without requiring additional licensing. Users can continue their workflows seamlessly while benefiting from enhanced Copilot features built directly into Forms. [Rollout Schedule:] Retirement completion: Surveys agent is no longer available for new users as of August 31, 2026 (removed from Agent Store) Existing users who have already acquired Surveys Agent are expected to lose access by end of December 2026 [Impact on Your Organization:] Who is affected: All users who currently use the Surveys agent in Microsoft 365 Copilot Platforms/Services: Microsoft 365 Copilot Microsoft Forms (Web) What will happen: The Surveys agent will be retired and removed from the Agent Store. Users will be redirected to Microsoft Forms when accessing Surveys agent. Screenshot - Survey Agent home screen for existing users Copilot capabilities for surveys will continue within Microsoft Forms via the dynamic action button. Existing forms created through Surveys agent will remain accessible in Microsoft Forms. Users will retain access to their past Surveys agent conversation history in Microsoft 365 Copilot. Screenshot - Survey Agent chat screen for existing users No changes to licensing or permissions are required. The new experience is enabled by default; no admin configuration is needed. [Action Required/Recommendations:] No action is required. Inform users about the transition to avoid confusion when redirects occur. Update internal documentation referencing the Surveys agent. Prepare helpdesk teams for potential user questions during the transition period. Learn more: Evolving the Copilot experience in Microsoft Forms Message Center post MC1229954 [Compliance considerations:] No compliance considerations identified, review as appropriate for your organization. -
(Updated) eSignature for Microsoft 365 - Recipient groups
MC1290821 · stayInformed · normal · Updated 09/21/2026 17:07
Services: Microsoft 365 suite, SharePoint Online
Read message
Updated September 21, 2026: We have updated the timeline. Thank you for your patience. [Introduction] We are introducing recipient groups for eSignature in Microsoft 365. Recipient groups allow a single recipient slot to be assigned to multiple people, where the first person to sign fulfills the signing requirement. This update helps make signature workflows more reliable by reducing delays when a specific signer is unavailable, without changing existing tenant policies. This message is associated with Microsoft 365 Roadmap ID 560822. [When this will happen] Public Preview: Rollout is expected to complete by late September 2026 General Availability (Worldwide): Rollout will begin in early December 2026 (previously early September) and is expected to complete by mid-December 2026 (previously late October). [How this affects your organization] Who is affected Users who create eSignature requests in Microsoft Word Microsoft 365 tenants that use eSignature for Microsoft 365 What will happen Users can assign up to 10 people to a single recipient slot: The first person in the recipient group to sign fulfills the signing requirement for the group. Signature workflows are less likely to stall due to individual signer availability. The feature is enabled by default and respects existing tenant policies. [What you can do to prepare] No action is required from admins. Consider informing users who rely on eSignature workflows about this improvement. [Compliance considerations] QuestionAnswer Does the change alter how existing customer data is processed or accessed?Yes. Signature completion logic is updated so that one signer in a recipient group can fulfill the signing requirement for the group. -
Dynamics 365 Contact Center – Enable AI-assisted time-off and swap requests
MC1475801 · stayInformed · normal · Updated 09/21/2026 16:25
Services: Dynamics 365 Apps
Read message
We are announcing the ability to enable AI-assisted time-off and swap requests in Dynamics 365 Contact Center. This feature will reach general availability on October 1, 2026. How does this affect me? This feature enables an AI-assisted solution that provides automation for workforce schedules and approvals, governance across time‑off requests, shift bidding, and shift swapping. Supervisor oversight is supported throughout, along with configurable approval rules, and agent-driven decisions with transparent reasoning to ensure operational continuity and fairness. Key capabilities of this feature include: Time-off requests: Evaluated against configurable constraints such as available leave balance, maximum consecutive days, allowed time‑off windows, shift coverage thresholds (over‑ or understaffed percentages), first‑come, first‑served rules, and seniority or tenure. Shift bidding: Governed by constraints including shift capacity, skill or proficiency matching, bid order or first‑come, first‑served logic, bidding windows, seniority, and schedule conflict checks such as overlaps or locked schedules. Shift swapping: Validated using constraints that assess coverage impact before and after the swap, detect schedule conflicts, and enforce swap eligibility rules such as allowed swap types and limits per period. What action do I need to take? This message is for awareness, and no action is required. -
In-app browsing in Copilot app
MC1474455 · planForChange · normal · Updated 09/21/2026 15:33
Services: Microsoft 365 suite
Read message
[What and why:] We are adding support to the Microsoft Copilot app, in Windows and Mac, to allow websites that Copilot shares in chat to open inside of the desktop app side by side with the Copilot chat conversation. This is available now but not available by default; administrators can opt-in selected Windows and Mac devices to test this. [Rollout schedule:] Opt-in availability: Available now. [Impact on your organization:] Administrators can manage early access by opting-in selected devices and deploying the updates via instructions linked below. This early access allows you to: Test in-app browsing at your organization before the broader rollout. This allows users to open links within the Copilot desktop app. Validate deployed and in-app browsing behavior in your organization's managed environment. Prepare support teams and users for the updated experience that applies to Copilot Windows and Mac endpoints. What users will see When a user clicks a link within the Copilot desktop app, the website opens in a side pane to the right of the Copilot chat. Users can open multiple links, each appearing as a separate tab within the side pane and can switch between tabs as needed. Once the websites are no longer needed, users can close the side pane. Users can adjust the in-app browser side pane to be smaller or larger. They can also enter full-screen mode to view the website in a full-screen experience and can toggle in and out of this mode using the button in the side pane header. Users can still open a link in an external browser, by: Selecting the "External browser" option from the three-dot menu on the link within Copilot Chat OR Selecting “Copy the URL” and pasting it into an external browser OR Right clicking a tab in the side pane within the Copilot app and selecting "External browser" (coming 9/21) [Action required / Recommendations:] To enable in-app browsing, you can turn on the 'BrowsingEnabled' policy through your device management system.Microsoft Edge Browser Policy Documentation | Microsoft Learn Configure Microsoft Edge for Windows with policy settings | Microsoft Learn Configure Microsoft Copilot policies Review the in-app browsing associated policies that can be adjusted and changed. [Compliance Considerations:] Does the change store new customer data? Yes. Browsing history, cookies, autofill information are stored on the local device. This follows the same storage mechanisms as Microsoft Edge storing data in the user Data profile directory at “%localappdata%\Microsoft\Copilot\User Data”. Does the change provide end users with a new way of interacting with generative AI? This feature does not add any new way to create or steer generative AI, it only lets you view websites, whether those are website on the internet or html files created generatively with copilot via other features. -
(Updated) Microsoft Exchange Online: Review and configure EWSAllowedAppIDs before Exchange Web Services access changes
MC1469960 · preventOrFixIssue · normal · Updated 09/18/2026 17:01
Services: Exchange Online
Read message
Updated September 18, 2026: We have updated the content. Thank you for your patience. [What and why] As part of the final phase of Exchange Web Services (EWS) retirement, Microsoft is updating how the EWSAllowedAppIDs setting is applied in Exchange Online. This change is designed to help organizations identify and manage applications that still require EWS access while reducing the risk of unexpected service disruption. Organizations that continue to use EWS should review and maintain their own EWSAllowedAppIDs list. If a tenant administrator has already configured this list, Microsoft will not overwrite or modify it. Beginning on October 1, 2026, Microsoft will start enabling this updated behavior by cloud as part of the EWS retirement rollout. [Rollout schedule] Worldwide, GCC, GCC High, DoD: Beginning in early October 2026 and expected to complete by late April 2027 The updated behavior will apply when the rollout reaches your cloud. [Impact on your organization] Who is affected Organizations that continue to use Exchange Web Services (EWS) Exchange Online administrators responsible for managing EWS access Tenants with EWSEnabled set to True or Null Platforms and services Exchange Online Exchange Web Services (EWS) What will happen After the updated behavior is enabled in a cloud: EWS will require a configured EWSAllowedAppIDs list when EWSEnabled is set to True. Before enabling the change, Microsoft will ensure that tenants with EWSEnabled already set to True have an EWSAllowedAppIDs list. If a customer-managed list does not exist, Microsoft will generate a list based on EWS application usage observed during the previous 60 days to help reduce the risk of service interruption. Microsoft-generated lists may omit applications that run infrequently and may include applications that no longer require EWS access. If EWSEnabled remains Null, Microsoft will populate EWSAllowedAppIDs only when a customer-managed list does not already exist. This will occur shortly before Microsoft updates EWSEnabled to False as part of the retirement rollout. Microsoft will not modify an EWSAllowedAppIDs list that has already been configured by a tenant administrator. [Action required and recommendations] If your organization still relies on EWS, we recommend taking the following actions as soon as possible: Review EWS usage from the previous 60 days and identify all applications that require continued EWS access, including applications with infrequent usage patterns. Configure and validate your EWSAllowedAppIDs list before the rollout reaches your cloud. Ensure EWSEnabled is set to True if continued EWS access is required. Keep the EWSAllowedAppIDs list current as applications are added, removed, or migrated away from EWS. Plan for up to a 24-hour propagation delay after changes are made to the EWSAllowedAppIDs list. Microsoft's safeguard helps reduce the risk of service disruption but does not replace customer review and validation of EWSAllowedAppIDs. We also recommend continuing plans to migrate applications from EWS to Microsoft Graph before EWS retirement is completed. Learn more Deprecation of Exchange Web Services in Exchange Online | Microsoft Learn Introducing EWSAllowedAppIDs: Preparing for the Final Phase of EWS Retirement [Compliance considerations] No compliance considerations identified, review as appropriate for your organization. -
Retirement of Microsoft 365 Companion apps
MC1474111 · planForChange · normal · Updated 09/18/2026 15:35
Services: Microsoft 365 suite
Read message
[What and why:] The Microsoft 365 companion apps—Calendar, People, and Files — are taskbar-integrated apps designed to streamline everyday workflows, helping users stay focused, reduce context switching, and complete tasks faster. We are retiring the companion apps, and they will no longer function or be supported after 16. December 2026. We advise admins remove the apps from devices in their tenant by this date. Detailed admin guidance is in Microsoft 365 companion app retirement. [Rollout schedule:] Microsoft 365 companion apps will reach end of life on December 16, 2026. As of the publication of this message, Microsoft will begin phasing out automatic installation of the companion apps. Updates and fixes, including security fixes, are no longer being provided. Existing installations can continue to function during the retirement window. December 16, 2026: Remaining companion apps will stop functioning and will no longer be supported. [Impact on your organization:] This retirement affects worldwide enterprise customers that installed the apps. Microsoft will stop the automatic installation of companion apps through Microsoft 365 Apps updates. Admins must prevent new installations through other deployment methods and should remove existing installations from managed devices. Users of unmanaged devices should uninstall the apps themselves. The companion apps were an additional way to find calendar information, people, and files so removing them will not delete or impact any existing capabilities or Microsoft 365 data. Users can continue finding calendar information, people, and files using existing Microsoft 365 and Windows experiences such as Outlook, Teams, Windows Search Box, File Explorer, SharePoint, OneDrive, and more. [Action required / Recommendations:] Admins will need to take steps such as letting users know the companion apps are being retired, stopping deployment of new installations, removing existing installations, and removing references from all internal documentation, guides, communications, and training materials. Review the retirement article linked above for all the steps you need to take. If you encounter an issue that may require an update or fix during the retirement period, see the guidance in the Troubleshooting section in the retirement article. -
Microsoft Entra ID: Follow-up on SMS first-factor sign-in retirement and upcoming changes
MC1474104 · planForChange · normal · Updated 09/18/2026 15:13
Services: Microsoft Entra
Action required by: 02/01/2027 08:00
Read message
[What and why] To improve security and reduce reliance on vulnerable authentication methods, Microsoft is continuing the retirement of SMS first-factor sign-in in Microsoft Entra ID. Microsoft recommends phishing-resistant authentication methods, such as passkeys, as the preferred sign-in experience because they help reduce the risk of phishing, fraud, and account compromise associated with phone-based authentication. Microsoft previously retired SMS first-factor sign-in for Microsoft Entra ID Free tenants and stopped enabling SMS sign-in for newly created tenants. This communication provides an update on the next phase of the retirement effort and actions organizations should take to prepare. Microsoft has announced previous retirement actions in Message Center posts MC1426371, MC1448374, and MC1449181. This retirement applies only to Microsoft Entra ID workforce tenant authentication scenarios. It does not apply to Azure AD B2C or Microsoft Entra External ID customer identity scenarios. [Rollout schedule] Worldwide and GCC: Beginning February 1, 2027, SMS first-factor sign-in will be retired for Microsoft Entra ID tenants. [Impact on your organization] Who is affected Organizations that: Allow users to sign in using SMS first-factor authentication. Rely on SMS first-factor sign-in as a primary authentication method. Platforms and services Microsoft Entra ID SMS first-factor passwordless sign-in (SignInNoPassword) What will happen After February 1, 2027: Users will no longer be able to authenticate by using their phone number and an SMS one-time passcode as a primary sign-in method. Existing SMS first-factor sign-in configurations will no longer be honored. Management and configuration experiences for SMS first-factor sign-in will be removed from Microsoft administration experiences. Attempts to sign in by using a registered phone number and SMS one-time passcode will be blocked. Users who have another registered authentication method can continue signing in. Organizations that do not migrate affected users before the retirement date may experience sign-in disruptions. [Action required and recommendations] If your organization uses SMS first-factor sign-in, complete the following actions before February 1, 2027: Identify users currently using SMS first-factor sign-in. Ensure affected users register an alternative authentication method before February 1, 2027. Communicate this change to affected users to prevent sign-in disruptions. Migrate users to passkeys or other phishing-resistant authentication methods. Review authentication method policies and remove dependencies on SMS first-factor sign-in. Review available authentication alternatives and migration guidance. The retirement of SMS sign-in as a first-factor authentication method applies even when you use Choose Your Own Telephony Provider to continue using SMS or voice as multifactor authentication method. If your organization currently uses SMS sign-in for first-factor authentication, migrate users to supported alternatives based on their scenarios. Alternatives include passkeys, QR code authentication, FIDO2 security keys, and other authentication methods supported by Microsoft Entra ID. Learn more SMS-based user sign-in for Microsoft Entra ID - Microsoft Entra ID | Microsoft Learn [Compliance considerations] QuestionAnswer Does this change modify how users access Microsoft 365 resources or services?Users who currently rely on SMS first-factor authentication must use another registered authentication method after February 1, 2027. Does this change require admin action to maintain user access?Administrators should identify affected users and ensure alternative authentication methods are registered before the retirement date. Does this change affect Conditional Access policies?Organizations may need to review authentication-related policies and dependencies that currently rely on SMS first-factor sign-in. Does this change alter how admins can monitor, report on, or demonstrate compliance activities?Management and configuration experiences for SMS first-factor sign-in will be removed from Microsoft Entra administration experiences. Does the change include an admin control and can it be controlled through Entra ID group membership?Existing SMS first-factor sign-in configurations will no longer be honored after the retirement date, requiring administrators to transition users to supported authentication methods. -
Microsoft Edge: IE mode is supported through at least the end of 2029, plan your migration
MC1473151 · planForChange · normal · Updated 09/17/2026 20:58
Services: Microsoft 365 suite
Read message
[What and why] Internet Explorer (IE) mode in Microsoft Edge remains supported through at least the end of 2029, as first announced in 2021. Microsoft is sharing this reminder so admins can plan migrations for legacy websites and applications that still depend on IE mode. Application modernization projects can take years to complete depending on the number and complexity of dependencies, so early planning reduces the risk of disruption later. [Rollout schedule] This is a reminder, not a rollout of a new feature or capability. IE mode support continues through at least the end of 2029 across Worldwide, GCC, GCC High, and DoD environments. Microsoft will provide at least one year of notice before retiring IE mode. [Impact on your organization] Who is affected Organizations that use IE mode in Microsoft Edge for legacy websites or applications Organizations that do not use IE mode are not affected. Platforms and services Microsoft Edge What will happen If your organization does not use IE mode, there is no impact and no action is required. If your organization uses IE mode, you can continue using it while you modernize affected websites and applications. Support for IE mode continues through at least the end of 2029, but modernization projects may take years to complete. This message does not change your current IE mode configuration or require you to disable IE mode immediately. It is intended to help you identify dependencies and plan migration work before the end of the current support period. [Action required and recommendations] If your organization no longer uses IE mode in Microsoft Edge, no action is required. If your organization still depends on IE mode: Inventory your IE mode dependencies. Identify the business-critical websites and applications that still require IE mode. Review your existing Enterprise Mode Site List and current usage to build your inventory. Assess modernization options. Determine whether each application should be updated, rehosted, replaced, or rebuilt using modern technologies and services. Request assistance if needed. Microsoft App Assure provides no cost assistance for eligible customers experiencing application compatibility issues with Microsoft Edge and IE mode. Planning early can help your organization identify migration risks and reduce the likelihood of disruption as you move away from IE mode dependencies. Learn more Microsoft App Assure: App Compatibility Support | Microsoft 365 Lifecycle FAQ - Internet Explorer and Microsoft Edge | Microsoft Learn [Compliance considerations] No compliance considerations identified, review as appropriate for your organization. -
Dynamics 365 Project Operations - Improve NTE reliability and validation coverage
MC1473656 · stayInformed · normal · Updated 09/17/2026 20:13
Services: Dynamics 365 Apps
Read message
We are announcing the ability to improve Not-To-Exceed (NTE) reliability and validation coverage in Dynamics 365 Project Operations. This feature will reach public preview on September 30, 2026. How does this affect me? This feature provides consistent control over NTE limits across every billable type, so users avoid over-billing, and protect revenue. The core capabilities of this feature include: Extends NTE validation beyond time entries to include expense, material, and fixed-price components. Enhances the Invoice Confirmation Service to block confirmation when Total Billed + Unbilled Committed > NTE Amount. Fixes bugs where NTE status fails to update on approval records due to custom plugin conflicts, ensuring deterministic results. What action do I need to take? This message is for awareness, and no action is required. If you would like more information on this feature, please visit Improve NTE reliability and validation coverage. -
Intune: Windows Health Attestation Migration to Microsoft Azure Attestation
MC1473600 · planForChange · normal · Updated 09/17/2026 18:25
Services: Windows
Read message
What and why: Microsoft Intune will migrate Windows Health Attestation compliance evaluation from the current Device Health Attestation (DHA) service to Microsoft Azure Attestation (MAA). This is an Intune service-side change that will happen automatically. Rollout schedule: We are targeting this migration at the end of Q1 in 2027. Impact on your organization: This change affects evaluation of Windows compliance policies that rely on Health Attestation signals. Action is required to avoid interruption. Organizations that don’t allow access to the required Azure Attestation endpoints will experience issues with Health Attestation-based compliance evaluation after the migration is completed. Action required/recommendations: Review your network, firewall, proxy, and endpoint access configurations. Specifically, verify that your environment allows devices to access the required Microsoft Azure Attestation endpoints. For detailed guidance, including the required endpoints and configuration recommendations, consult Configure endpoints for Azure Attestation migration. Compliance considerations: If unaddressed, Windows 11 devices with assigned compliance policies using any of the device health settings (BitLocker, Secure Boot, Code Integrity) will fall out of compliance. -
(Updated) Microsoft Edge: Security Update Alerts in the Edge management service
MC1458480 · stayInformed · normal · Updated 09/17/2026 16:37
Services: Microsoft 365 suite
Read message
Updated September 17, 2026: We have updated the timeline. Thank you for your patience. [What and Why:] Administrators can now choose a severity threshold and receive alerts when a new Edge update includes security fixes that meet or exceed that threshold, including zero-day fixes. This helps organizations quickly identify updates that may require attention, while avoiding unnecessary notifications for routine releases. This message is associated with Microsoft 365 Roadmap ID 558435 [Rollout schedule:] General Availability (Worldwide): We will begin rolling out mid-October 2026 (previously mid-September) and expect to complete by end of October 2026 (previously end of September). [Impact on your organization:] No action will be taken on behalf of the administrator. By default, the existing experience that notifies admins of all new Edge updates will remain. Admins can now choose to specify when they would like to receive new update notifications. [Action required / Recommendations:] This rollout will happen automatically by the specified date with no admin action required before the rollout. For more information, see Monitoring dashboard | Microsoft Learn -
Brand Skill support now available in PPT Copilot [Desktop]
MC1473166 · planForChange · normal · Updated 09/16/2026 22:47
Services: Microsoft 365 apps
Read message
[What and why:] Brand managers will be able to upload custom presentation skills as Markdown (.md) files to Brand Kit and share them across their organization for use with Copilot in PowerPoint. This capability helps organizations provide reusable, organization-approved instructions that guide presentation creation, supporting more consistent and efficient content development. This change advances personal and team productivity by embedding reusable presentation guidance into the tools employees use to create presentations. [Rollout schedule:] Frontier: We will begin rolling out mid-September 2026 and expect to complete by late September 2026. General Availability, Worldwide: We will begin rolling out in late September 2026 and expect to complete by the end of September 2026. [Impact on your organization:] Who is affected: Brand managers who create, manage, and publish organizational Brand Kits. Users in organizations where a Brand Kit containing a custom presentation skill has been published and who have access to Copilot in PowerPoint. The product team should confirm applicable licensing and whether additional eligibility requirements apply. Platforms and services: Microsoft 365 Brand Kit Microsoft Copilot Microsoft PowerPoint - Desktop What will happen: Brand managers will be able to upload a custom presentation skill as a Markdown (.md) or .zip file to Brand Kit. Brand managers will be able to publish the skill for use by people in their organization. Eligible users will be able to use the published skill with Copilot in PowerPoint. The skill can provide reusable instructions to guide how Copilot creates presentations. The feature requires a Brand manager to upload and publish a skill. It is not automatically activated merely because the capability becomes available. [Action required and recommendations:] Review who is assigned as a Brand manager through the Enterprise Brand Manager policy. Identify the people responsible for writing, reviewing, approving, and maintaining presentation skills. Establish governance for security, privacy, accessibility, legal, and brand review. Test skills with representative presentation scenarios before publishing them broadly. Communicate the availability of published skills to users of Copilot in PowerPoint. Update internal Brand Kit and Copilot documentation. Review published skills periodically and remove or replace outdated instructions. Review Microsoft documentation: Brand Skill support for Copilot in PowerPoint. [Compliance considerations:] This change provides eligible users with a new way to interact with generative AI by using organization-published instructions with Copilot in PowerPoint. This change introduces organization-published instructions that can guide Copilot when users create presentations. Brand Kit publishing is governed through the Enterprise Brand Manager policy and a mail-enabled security group. Confirm that presentation skills use the same controls without additional configuration. Confirm storage, retention, audit logging, Purview behavior, user-level disablement, third-party integration, and GDPR data-subject-request implications before publication. -
Brand Skill support now available in PPT Copilot [Web]
MC1473165 · planForChange · normal · Updated 09/16/2026 22:46
Services: Microsoft 365 apps
Read message
[What and why:] Brand managers will be able to upload custom presentation skills as Markdown (.md) files to Brand Kit and share them across their organization for use with Copilot in PowerPoint. This capability helps organizations provide reusable, organization-approved instructions that guide presentation creation, supporting more consistent and efficient content development. This change advances personal and team productivity by embedding reusable presentation guidance into the tools employees use to create presentations. [Rollout schedule:] Frontier: We will begin rolling out mid-September 2026 and expect to complete by late September 2026. General Availability, Worldwide: We will begin rolling out in late September 2026 and expect to complete the rollout by the end of September 2026. [Impact on your organization:] Who is affected: Brand managers who create, manage, and publish organizational Brand Kits. Users in organizations where a Brand Kit containing a custom presentation skill has been published and who have access to Copilot in PowerPoint. The product team should confirm applicable licensing and whether additional eligibility requirements apply. Platforms and services: Microsoft 365 Brand Kit Microsoft Copilot Microsoft PowerPoint - Web What will happen: Brand managers will be able to upload a custom presentation skill as a Markdown (.md) or .zip file to Brand Kit. Brand managers will be able to publish the skill for use by people in their organization. Eligible users will be able to use the published skill with Copilot in PowerPoint. The skill can provide reusable instructions to guide how Copilot creates presentations. The feature requires a Brand manager to upload and publish a skill. It is not automatically activated merely because the capability becomes available. [Action required and recommendations:] Review who is assigned as a Brand manager through the Enterprise Brand Manager policy. Identify the people responsible for writing, reviewing, approving, and maintaining presentation skills. Establish governance for security, privacy, accessibility, legal, and brand review. Test skills with representative presentation scenarios before publishing them broadly. Communicate the availability of published skills to users of Copilot in PowerPoint. Update internal Brand Kit and Copilot documentation. Review published skills periodically and remove or replace outdated instructions. Review Microsoft documentation: Brand Skill support for Copilot in PowerPoint. [Compliance considerations:] This change provides eligible users with a new way to interact with generative AI by using organization-published instructions with Copilot in PowerPoint. This change introduces organization-published instructions that can guide Copilot when users create presentations. Brand Kit publishing is governed through the Enterprise Brand Manager policy and a mail-enabled security group. Confirm that presentation skills use the same controls without additional configuration. Confirm storage, retention, audit logging, Purview behavior, user-level disablement, third-party integration, and GDPR data-subject-request implications before publication. -
Brand Skill support now available in PPT Copilot [Mac]
MC1473163 · planForChange · normal · Updated 09/16/2026 22:43
Services: Microsoft 365 apps
Read message
[What and why:] Brand managers will be able to upload custom presentation skills as Markdown (.md) files to Brand Kit and share them across their organization for use with Copilot in PowerPoint. This capability helps organizations provide reusable, organization-approved instructions that guide presentation creation, supporting more consistent and efficient content development. This change advances personal and team productivity by embedding reusable presentation guidance into the tools employees use to create presentations. [Rollout schedule:] Frontier: We will begin rolling out mid-September 2026 and expect to complete by late September 2026. General Availability, Worldwide: We will begin rolling out in late September 2026 and expect to complete the rollout by the end of September 2026. [Impact on your organization:] Who is affected: Brand managers who create, manage, and publish organizational Brand Kits. Users in organizations where a Brand Kit containing a custom presentation skill has been published and who have access to Copilot in PowerPoint. The product team should confirm applicable licensing and whether additional eligibility requirements apply. Platforms and services: Microsoft 365 Brand Kit Microsoft Copilot Microsoft PowerPoint - Mac What will happen: Brand managers will be able to upload a custom presentation skill as a Markdown (.md) or .zip file to Brand Kit. Brand managers will be able to publish the skill for use by people in their organization. Eligible users will be able to use the published skill with Copilot in PowerPoint. The skill can provide reusable instructions to guide how Copilot creates presentations. The feature requires a Brand manager to upload and publish a skill. It is not automatically activated merely because the capability becomes available. [Action required and recommendations:] Review who is assigned as a Brand manager through the Enterprise Brand Manager policy. Identify the people responsible for writing, reviewing, approving, and maintaining presentation skills. Establish governance for security, privacy, accessibility, legal, and brand review. Test skills with representative presentation scenarios before publishing them broadly. Communicate the availability of published skills to users of Copilot in PowerPoint. Update internal Brand Kit and Copilot documentation. Review published skills periodically and remove or replace outdated instructions. Review Microsoft documentation: Brand Skill support for Copilot in PowerPoint. [Compliance considerations:] This change provides eligible users with a new way to interact with generative AI by using organization-published instructions with Copilot in PowerPoint. This change introduces organization-published instructions that can guide Copilot when users create presentations. Brand Kit publishing is governed through the Enterprise Brand Manager policy and a mail-enabled security group. Confirm that presentation skills use the same controls without additional configuration. Confirm storage, retention, audit logging, Purview behavior, user-level disablement, third-party integration, and GDPR data-subject-request implications before publication. -
Plan for Change: Intune migration for Windows Health Attestation to Microsoft Azure Attestation for Windows 11 devices
MC1473156 · planForChange · normal · Updated 09/16/2026 22:29
Services: Microsoft Intune
Read message
[What and why:] Microsoft Intune will migrate Windows Health Attestation compliance evaluation from the current Device Health Attestation (DHA) service to Microsoft Azure Attestation (MAA). This is an Intune service-side change that will happen automatically. [Rollout schedule:] This migration is expected at the end of the first quarter in calendar year 2027. [Impact on your organization:] This change affects evaluation of Windows compliance policies that rely on Health Attestation signals. Action is required to avoid interruption. Organizations that do not allow access to the required Azure Attestation endpoints will experience issues with Health Attestation-based compliance evaluation after the migration is completed. [Action required/recommendations:] Review your network, firewall, proxy, and endpoint access configurations. Specifically, verify that your environment allows devices to access the required Microsoft Azure Attestation endpoints. For detailed guidance, including the required endpoints and configuration recommendations, refer to: Configure endpoints for Azure Attestation migration. [Compliance considerations:] If unaddressed, Windows 11 devices with assigned compliance policies using any of the device health settings (BitLocker, Secure Boot, Code Integrity) will fall out of compliance. -
Loading Power Query data to Python in Excel Web: Retirement
MC1473149 · planForChange · normal · Updated 09/16/2026 22:20
Services: Microsoft 365 apps
Read message
[What and why:] Microsoft is retiring support for loading Power Query data into the Python runtime in Excel for the web. After this change, users will no longer be able to use Power Query as a data source for Python in Excel when working in Excel for the web. This retirement aligns investments in Python in Excel with supported experiences and does not affect Excel for Windows desktop. [Rollout Schedule:] Retirement date: October 16, 2026 [Impact on Your Organization:] Who is affected: Users who use Python in Excel with Power Query data sources in Excel for the web. Platforms affected: Excel for the web What will happen: Beginning October 16, 2026, users will no longer be able to load Power Query data into the Python runtime in Excel for the web. Workflows that depend on combining Power Query and Python in Excel for the web will no longer function as expected. No changes are being made to Python in Excel experiences in Excel for Windows desktop. Users can continue to import external data by using Power Query and analyze data with Python in Excel on supported desktop experiences. [Action Required / Recommendations:] No administrative action is required. Identify users and business processes that rely on Power Query data being loaded into Python in Excel for the web. Notify affected users of the retirement and expected workflow impact. Review affected solutions and consider transitioning those workflows to Excel for Windows desktop where this capability remains available. Update internal training, documentation, and support materials as needed. -
Microsoft 365 Usage Reporting Updates (Microsoft Browser and Visio)
MC1473148 · planForChange · normal · Updated 09/16/2026 22:19
Services: Microsoft 365 suite
Read message
[What and Why:] Microsoft is updating several Microsoft 365 usage reports to improve reporting accuracy and streamline analytics experiences. Microsoft Browser and Visio usage reports will receive metric calculation improvements. These changes help administrators access more accurate and workload-specific analytics. [Rollout Schedule:] Microsoft Browser usage report updates: September 21, 2026 Visio usage report updates: September 21, 2026 [Impact on Your Organization:] Who is affected: Microsoft 365 tenant administrators Organizations using Microsoft Browser and Visio Organizations consuming Microsoft Graph Reports API browser usage metrics Platforms/Services: Microsoft 365 admin center Microsoft Browser reporting Microsoft Edge Microsoft Graph Reports API (beta) Microsoft Visio What will happen: Microsoft Browser reporting will include additional Microsoft 365 applications such as Microsoft 365 Copilot App, OneNote, and Outlook. Microsoft Browser active-user counts may increase after September 21, 2026. Microsoft Visio active-user counts may increase after September 21, 2026. Visio Desktop and Web usage classifications will be updated. Historical reporting data will not be recalculated. [Action Required / Recommendations:] Review reporting and dashboards that depend on Microsoft Browser or Visio metrics. Record September 21, 2026 as a reporting baseline change date. Validate any Microsoft Graph Reports API integrations. -
Microsoft 365: Find more actions in the suite header menu
MC1472598 · planForChange · normal · Updated 09/15/2026 23:08
Services: Exchange Online
Read message
[What and why] To keep the Microsoft 365 suite header organized and reduce visual clutter, some actions currently displayed directly in the suite header will move to the More (...) menu. This update improves discoverability of additional actions while preserving existing functionality. The Settings and My Day actions will continue to be available and can be accessed from the More (...) menu. We are also adding the Sync button to that menu. This change does not remove any capabilities. It only changes where certain actions are accessed. [Rollout schedule] Targeted Release (Worldwide): Began in early September 2026 and expected to complete by mid-September 2026 General Availability (Worldwide, GCC High, DoD): Beginning in early October 2026 and expected to complete by late October 2026 General Availability (GCC): Beginning in early October 2026 and expected to complete by early November 2026 [Impact on your organization] Who is affected Users who access Microsoft 365 applications and services that display the suite header Platforms and services Microsoft 365 Web experiences that include the Microsoft 365 suite header What will happen Some actions currently displayed directly in the suite header will move to the More (...) menu. The Settings and My Day actions will be available from the More (...) menu. Users will continue to have access to the same functionality. The change will be enabled automatically as part of a service update. No admin configuration is required. This update simplifies the suite header and provides a consistent location for accessing additional actions. Before: After: [Action required and recommendations] No action is required. We recommend that you: Inform support and helpdesk teams that some suite header actions are changing location. Update any internal documentation or user training materials that reference the previous location of these actions. Communicate the change to users who may rely on direct access to actions in the suite header. [Compliance considerations] No compliance considerations identified, review as appropriate for your organization. -
(Updated) Microsoft Entra: Passkeys by default and retirement of Microsoft-provided SMS and voice authentication
MC1426371 · planForChange · normal · Updated 09/15/2026 22:26
Services: Microsoft Entra
Read message
Updated September 15, 2026: We have updated the content and timeline. Thank you for your patience. [What and why] Passkeys became the default authentication experience in Microsoft Entra on September 1, 2026. Telecom-based methods (SMS and voice) will transition to customer-configured providers through the Microsoft Security Store. The AI era demands stronger, phishing-resistant authentication. We are making passkeys the default authentication experience in Microsoft Entra to help customers securely adopt AI at scale. As part of this transition, SMS and voice will no longer be available as multifactor authentication methods starting February 1, 2027. SMS and voice do not offer sufficient levels of security in comparison to passkeys. Traditional authentication methods including passwords, SMS one-time passcodes, and voice-based verification remain vulnerable to phishing, interception, and social engineering attacks. We strongly recommend moving away from telephony-based authentication methods to improve security and prevent identity attacks. Passkeys are included in all Microsoft Entra plans, so making this critical security change comes at no additional cost for you. While we recommend adopting passkeys for phishing-resistant authentication as quickly as possible, we also recognize that some customers may have business needs that make an immediate transition impractical. In such cases, customers may continue to use SMS and voice by selecting a telecom provider in the Microsoft Security Store. [Rollout schedule] September 1, 2026: Rollout began. Changes may take time to reach all tenants and will be deployed gradually. Passkeys will be automatically enabled for users currently enabled for SMS or voice. Registration Campaign will be set to Microsoft-Managed targeting passkeys for all users in eligible tenants. Users will be prompted to register a passkey during MFA sign-in; users will be able to skip. September 18th, 2026: Review the telecom providers and related information available through the Microsoft Security Store to evaluate which option best meets your regional and compliance requirements. October 30, 2026: Customers who need to continue to use SMS or voice will be able to choose from a list of telecom providers available through the Microsoft Security Store. February 1, 2027: Microsoft-provided SMS and voice authentication will be retired. Only customer-configured telecom providers will support SMS and voice going forward. Passkeys become the default, recommended authentication method. July 1, 2027: Microsoft-provided SMS and voice authentication will be retired for Global Admins and external users Only customer-configured telecom providers will support SMS and voice for these users going forward If no action is taken, tenants relying only on Microsoft-provided SMS or voice may experience sign-in disruptions after February 1, 2027. [Impact on your organization] Who is affected All Microsoft Entra ID tenants enabled for SMS or voice authentication Users enabled for SMS or voice Platforms and services Microsoft Entra ID Multifactor authentication Microsoft Security Store What will happen Passkeys will be automatically enabled for eligible users and Registration Campaign for passkeys will be set to Microsoft Managed state starting September 1, 2026. Users will be prompted during MFA sign-in to register a passkey; users can skip the prompt. Microsoft-provided SMS and voice authentication will be retired for most users on February 1, 2027, and for Global Administrators and external users on July 1, 2027. Organizations that still require telephony methods must configure a telecom provider in the Microsoft Security Store. Tenants that do not configure a provider and continue relying on Microsoft telephony will face SMS and voice authentication disruptions after retirement. [Action required and recommendations] Admins should take the following steps: Prepare for passkeys Plan to transition users to passkeys and communicate upcoming registration prompts. Decide if SMS or voice is still required If SMS or voice is still needed, you must configure a customer-managed telecom provider. We recommend completing setup at least 4 weeks before the February 1 enforcement to allow sufficient time for testing and a cautious transition. Set up a telecom provider before February 1, 2027 SMS and voice will only work after this date if a customer-configured telecom provider is enabled. Use temporary opt-out if needed A temporary opt-out will be available for the September 1, 2026 through February 1, 2027 changes. This allows you to delay passkey and Registration Campaign enablement while you complete transition activities, such as configuring customer-managed telecom providers or migrating to other authentication methods. After February 1, 2027, passkey enablement will be enforced for all users in scope. Additional documentation and more information will be available on Microsoft Learn and the Tech Community. For more information please visit: https://learn.microsoft.com/entra/identity/authentication/concept-sms-voice-retirement more Learn more: Deploy passkey adoption campaigns with the Conditional Access Optimization Agent | Microsoft Entra | Microsoft Learn Get started with phishing-resistant passwordless authentication deployment in Microsoft Entra ID | Authentication | Microsoft Entra ID | Microsoft Entra | Microsoft Learn It's Time to Hang Up on Phone Transports for Authentication | Microsoft Entra Blog Passkeys by default and retirement of Microsoft-provided SMS and voice authentication | Microsoft Entra | Microsoft Learn [Compliance considerations] Review as appropriate for your organization. -
[Whiteboard] Legacy Whiteboard migration to OneDrive
MC1469957 · planForChange · normal · Updated 09/15/2026 17:39
Services: Microsoft OneDrive, Microsoft Teams, Microsoft 365 apps
Read message
Updated September 15, 2026: This message does not apply to Government customers. We apologize for the confusion, and you can safely disregard this message. [What and why:] Microsoft Whiteboard is completing its transition from legacy Azure-backed storage to OneDrive-backed Whiteboards. Organizations that still have legacy Azure-based Whiteboards must migrate them to OneDrive-backed storage before migration tooling is retired - September 25, 2026. After September 25, 2026, remaining legacy Azure-based Whiteboards become read-only and can no longer be migrated and can be only exported until October 16, 2026. After October 16, 2026, any remaining legacy Azure-based Whiteboards will be permanently deleted and cannot be recovered. Key dates Before September 25, 2026: Users can still trigger migration, retry failed migrations, and export important content. September 25, 2026: Migration tooling is retired. Remaining legacy Azure-based Whiteboards become read-only and can no longer be migrated, but can still be viewed and exported until October 16, 2026. October 16, 2026: Remaining legacy Azure-based Whiteboards are permanently deleted and cannot be recovered. November 30, 2026: Legacy Azure Whiteboard service shuts down. [Rollout schedule:] Worldwide: We will begin rolling out on late September 2026 and expect to complete by mid-October 2026. [Impact on your organization:] This change impacts organizations that still have legacy Azure-based Microsoft Whiteboards that have not yet been migrated to OneDrive-backed storage. After September 25, 2026: Users will no longer be able to migrate remaining legacy Azure-based Whiteboards. Remaining legacy Azure-based Whiteboards become read-only and can no longer be migrated, but can still be viewed and exported until October 16, 2026. Organizations that have not completed migration risk losing access to business content stored in legacy Whiteboards. After October 16, 2026: Any remaining legacy Azure-based Whiteboards will be permanently deleted and cannot be recovered. Enterprise users should access Microsoft Whiteboard through Teams and supported web experiences. Organizations that have already completed migration to OneDrive-backed Whiteboards will not experience changes to existing OneDrive-backed content. New Whiteboards are already created in OneDrive-backed storage. [Action required / Recommendations:] Admins should take the following actions immediately: Inventory remaining legacy Whiteboards: Use the WhiteboardAdmin PowerShell module to identify Azure-based Whiteboards that still require migration. Communicate with affected users: Notify Whiteboard owners of the migration deadline (September 25, 2026) and deletion deadline (October 16, 2026). Encourage users to migrate, export, or preserve any business-critical content before the deadlines. Validate migration completion: Review migration status and confirm that important Whiteboards, permissions, and user access have been successfully migrated and remain accessible in OneDrive-backed storage. Plan for large-scale migrations: For inactive users, orphaned Whiteboards, or large migration volumes, consider using the administrator-driven migration approach documented by Microsoft Whiteboard engineering. Update internal guidance: Update user training materials, help documentation, and support procedures to direct users to Microsoft Whiteboard in Teams and supported web experiences rather than standalone applications. Act before migration tooling is retired: After September 25, 2026, migration tooling will no longer be available, and no further migration path will exist for remaining legacy Whiteboards. -
60-Day Reminder: Windows 11, version 23H2 Enterprise and Education editions reach end of updates on November 10, 2026
MC1472443 · stayInformed · normal · Updated 09/15/2026 17:00
Services: Windows
Read message
On November 10, 2026, Windows 11, version 23H2 Enterprise and Education editions will reach end of updates. The November 2026 Windows security update will be the last update available for these editions. After this date, devices running these editions will no longer receive monthly security and non-security preview updates containing protections from the latest security threats. To continue receiving monthly security and quality updates, we recommend updating eligible devices running Windows 11, version 23H2 Enterprise and Education editions to Windows 11, version 25H2. Windows 11, version 25H2 Enterprise and Education editions will continue to receive updates until October 11, 2028. For more information about product lifecycle dates, see Windows 11 release information and Lifecycle FAQ - Windows. -
Support for Office LTSC 2021, and additional apps will end on October 13, 2026
MC1472429 · planForChange · normal · Updated 09/15/2026 16:49
Services: Microsoft 365 suite
Action required by: 10/13/2026 07:00
Read message
[What and why:] As previously communicated, support for Office LTSC 2021 will end on October 13, 2026. After that date, no further updates, security fixes, or technical support will be available for this version of Office. While the applications may continue to function, using unsupported software could lead to potential security risks, compliance risks, system incompatibilities, and other issues. Support for Visio LTSC 2021, Microsoft Project LTSC 2021 and several other products will also end on October 13, 2026. Organizations using these products should upgrade as soon as possible to maintain security, compliance, and performance. [Rollout schedule:] We will begin rolling out mid-October 2026 and expect to complete by mid-October 2026. [Impact on your organization:] After end of support, Office LTSC 2021 suites and standalones will no longer receive security updates or other fixes, and no technical assistance will be available for devices still running them. Continuing to use unsupported software can expose your organization to security and compliance risks and may impact service reliability and performance. [Action required / Recommendations:] To mitigate these risks while maintaining access to desktop Office apps, we recommend upgrading devices to a Microsoft 365 or Office 365 suite that includes Microsoft 365 Apps (for enterprise or for business). Microsoft 365 Apps provides always-up-to-date versions of familiar apps like Word, Excel, and PowerPoint for desktop, mobile, and web with continuous support under the Modern Lifecycle Policy, and is eligible for use with the Microsoft 365 Copilot add-on. Enterprises should look to Microsoft 365 E3, Office 365 E3, or Microsoft 365 Apps for enterprise. Organizations with fewer than 300 users should look to Microsoft 365 Business Premium, Microsoft 365 Business Standard, or Microsoft 365 Apps for business. For scenarios that require a fully disconnected solution, we recommend upgrading to Office LTSC 2024. Office LTSC 2024 is Microsoft’s current supported on-premises version of Office for commercial customers and will be supported until October 2029 under the Fixed Lifecycle Policy. Take steps to prepare for this transition with the following resources: Read the upgrade guidance for an overview of how to move from Office LTSC 2021 to Microsoft 365 Apps. Consider engaging Microsoft FastTrack, a Microsoft support service, for moving to Microsoft 365. Take action before October 13, 2026, to help maintain security, compliance, and access to supported Office apps. -
(Updated) Microsoft SharePoint : Dashboard Card Visibility on Mobile
MC1462471 · stayInformed · normal · Updated 09/15/2026 16:28
Services: SharePoint Online, Microsoft Viva
Read message
Updated September 15, 2026: We have updated the timeline. Thank you for your patience. [What and Why:] Dashboard authors can now control whether individual dashboard cards are visible on mobile devices. This enhancement provides greater flexibility when designing dashboards, allowing organizations to tailor the mobile experience and ensure users see the most relevant information on smaller form factors. [Rollout Schedule:] General Availability (Worldwide, GCC, GCC High, DoD): Rollout will begin in mid-September 2026 (previously late August) and is expected to complete by end of September 2026 (previously early September). [Impact on Your Organization:] Who is affected: Dashboard authors and users who access dashboards on mobile devices. Platforms: Mobile form factors. After this rollout: Dashboard authors will be able to configure the visibility of individual dashboard cards on mobile devices. Organizations can choose which dashboard cards are displayed to users on mobile form factors. Existing dashboard configurations will remain unchanged unless updated by a dashboard author. [Action Required / Recommendations:] No action is required. The mobile card visibility setting will be available automatically as part of the rollout. We recommend informing dashboard authors of this new capability so they can review and optimize dashboard experiences for mobile users if desired. [Compliance Considerations:] No compliance considerations identified, review as appropriate for your organization. -
Microsoft SharePoint: PowerShell support for brand fonts deletion
MC1472025 · stayInformed · normal · Updated 09/14/2026 23:20
Services: SharePoint Online
Read message
[What and why:] Microsoft SharePoint is introducing PowerShell support for deleting brand font files from the Brand Fonts library used by the SharePoint Brand Center. With the new Remove-SPOFontFile cmdlet, SharePoint administrators can remove brand font files that are no longer approved, licensed, or needed across their organization in SharePoint. This cmdlet is the supported deletion path for brand fonts for SharePoint. It is designed to help admins manage font lifecycle and avoid cross-geo inconsistencies by removing font copies across the primary geo and satellite geos. When a deleted font is referenced by existing SharePoint sites or pages, the content will continue to be rendered using a Microsoft-defined fallback font. Font packages that reference deleted fonts are not automatically deleted. They remain available for use, but a warning message is displayed when required fonts are unavailable. [Rollout schedule:] General Availability (Worldwide): We will begin rolling out on late September 2026 and expect to complete by mid-October 2026. [Impact on your organization:] Note: Brand font management in Brand Center currently depends on the SharePoint Public CDN and is available only to customers who have Public CDN enabled. SharePoint administrators can manage brand font deletion via PowerShell, helping organizations govern SharePoint brand fonts lifecycle, licensing, and compliance. The cmdlet removes font copies across the primary geo and satellite geos, helping avoid cross-geo inconsistencies. End-user content remains readable. If a deleted font is referenced by an existing site or page, SharePoint will use the Microsoft-defined fallback fonts. Font packages that reference deleted fonts remain available, with status shown to indicate unavailable font references. Example results of running the cmdlet Before deleting the font After deleting the font [Action required / Recommendations:] Review the official documentation for PowerShell branding governance:Remove-SPOFontFile (Microsoft.Online.SharePoint.PowerShell) | Microsoft Learn Brand fonts - SharePoint in Microsoft 365 | Microsoft Learn After rollout is complete, upgrade your PowerShell module to the required version before using these new features. Review the current fonts in the Brand Center and identify fonts that are no longer approved, licensed, or needed. Coordinate with brand managers and SharePoint site owners before deleting fonts that may affect site branding. Update internal documentation and admin procedures for managing brand fonts with PowerShell. -
Take Action: Out-of-band update released to address issues from the September 2026 Windows security update
MC1471876 · stayInformed · normal · Updated 09/14/2026 21:37
Services: Windows
Read message
Microsoft has identified issues that affect some devices after installing the September 2026 Windows security update, released September 8, 2026. On affected devices, host folder shares might be unavailable in Hyper-V-based Linux virtual machines, Remote Desktop Services might stop responding, which can prevent new sessions from being created and can prevent local and remote sign-in, and some USB Audio Class 1.0 devices might fail in multichannel audio modes. An out-of-band (OOB) update was released today, September 14, 2026, to address these issues. For most versions of Windows, these are cumulative updates that include all improvements from the September 2026 Windows security update released September 8, 2026, so you do not need to install any previous update first, except as noted below for hotpatch updates. For Windows 11, versions 26H1, 25H2, and 24H2, this OOB update is a security update. It downloads and installs automatically from Windows Update and from Windows Update for Business in accordance with configured policies. It is also available from the Microsoft Update Catalog and syncs automatically with Windows Server Update Services (WSUS). A corresponding hotpatch update is available from Windows Update for Windows 11, versions 25H2 and 24H2 for devices enrolled in hotpatch updates. Devices must have the September 2026 security update installed to receive this hotpatch update automatically. The update for Windows 11, versions 26H1, 25H2, and 24H2 includes a security fix to address CVE-2026-62721. The update for Windows 11, version 26H1 also includes a security fix to address CVE-2026-85921. For Windows 11, version 23H2, and Windows 10, version 22H2 (ESU), this update is an optional non-security update. To install it, go to Settings > Windows Update, select Check for updates, and then select Download and install. It is also available from the Microsoft Update Catalog. For complete guidance and installation instructions, see the relevant KB articles: Windows 11, version 26H1: KB5129194 Windows 11, versions 25H2 and 24H2: KB5129195 Windows 11, versions 25H2 and 24H2 (hotpatch): KB5129241 Windows 11, version 23H2: KB5129242 Windows Server 2025: KB5129235 Windows Server 2022: KB5129237 Windows 10, version 22H2 and Windows 10 Enterprise LTSC 2021: KB5129236 Windows 10 Enterprise LTSC 2019 and Windows Server 2019: KB5129238 Windows 10 Enterprise LTSB 2016 and Windows Server 2016: KB5129239 Windows Server 2012 R2: KB5129243 Windows Server 2012: KB5129244 -
30-Day Reminder: Windows 11, version 24H2 and Windows 10 LTSB 2016 reaching end of updates on October 13, 2026
MC1471964 · stayInformed · normal · Updated 09/14/2026 20:56
Services: Windows
Read message
On October 13, 2026, Windows 11, version 24H2 Home and Pro editions, and Windows 10 Enterprise LTSB 2016 will reach end of updates. After this date, devices running these editions will no longer receive monthly security and non-security preview updates containing protections from the latest security threats. We recommend updating devices running Windows 11, version 24H2 Home and Pro editions to Windows 11, version 25H2 to continue receiving monthly security and quality updates. Enterprise and Education editions remain supported until October 12, 2027. For more information, see the How to get the Windows 11 2025 Update video. For devices running Windows 10 Enterprise LTSB 2016, we recommend updating to the latest Long-Term Servicing Channel (LTSC) release, Windows 11 Enterprise LTSC 2024. Extended Security Updates (ESU) are also available for organizations that need additional time to complete their transition. For more information about product lifecycle dates, see Windows 11 release information, Windows 10 release information, and Lifecycle FAQ - Windows. -
30-Day Reminder: AD FS DKM container ACL hardening begins in October 2026
MC1471963 · stayInformed · normal · Updated 09/14/2026 20:56
Services: Windows
Read message
What and why In October 2026, Windows updates will begin Enforcement mode for AD FS Distributed Key Manager (DKM) container ACL hardening. This hardening change is designed to address the elevation of privilege vulnerability documented in CVE-2026-56155 by automatically remediating insecure DKM container ACL configurations on supported Windows Server versions. If your organization uses Active Directory Federation Services (AD FS), use the remaining Audit mode period to validate DKM container permissions, identify compatibility issues, and complete preparation before Enforcement mode begins. Rollout schedule Enforcement mode begins with the October 2026 Windows security update. Impact on your organization Organizations using AD FS might see changes to DKM container permissions when remediation is applied during Enforcement mode. During the October 2026 update, supported Windows Server versions will run remediation by default unless administrators explicitly opt out. Windows Server 2012 and Windows Server 2012 R2 still require manual remediation and will not be automatically remediated. Action required/recommendations Organizations using AD FS should: Install the July 14, 2026 Windows security update or a later Windows update on AD FS servers. Review AD FS Admin event logs for Event ID 1132, which indicates that DKM container permissions require attention. Test remediation during the current Audit mode phase and address findings before Enforcement mode begins in October 2026. See the guidance in: CVE-2026-56155: AD FS Distributed Key Manager container ACL hardening. -
An updated version of the September 2026 Scan Cab is available
MC1471885 · stayInformed · normal · Updated 09/14/2026 17:50
Services: Windows
Read message
IMPORTANT: This notice is only relevant for environments where: Windows 11, version 26H1, 25H2, or 24H2 is deployed Scan Cab is used to check for update compliance The September 2026 Scan Cab was deployed before 10:00 AM PDT on September 14, 2026 What and why: An updated version of the September 2026 Scan Cab was made available at 10:00 AM PDT on September 14, 2026. This Scan Cab includes new metadata corresponding to new updates for Windows 11, versions 26H1, 25H2 and 24H2. The new Microsoft update for Windows 11, versions 26H1, 25H2 and 24H2 released on September 14, 2026, included additional security protections to address CVE-2026-62721: Windows User-Mode Power Service (UMPS) Elevation of Privilege Vulnerability. The update for Windows 11, version 26H1 also addressed CVE-2026-85921: Windows Secure Kernel Mode Elevation of Privilege Vulnerability. See the additional information section of this message for details. Rollout schedule: The updated September 2026 Scan Cab was made available at 10:00 AM PDT on September 14, 2026. Who is affected: IT administrators who downloaded the Scan Cab before 10:00 AM PDT on September 14, 2026, should re-acquire and re-deploy it if the Scan Cab is used to assess updates for environments running Windows 11, versions 26H1, 25H2 or 24H2. No action is required on environments where Scan Cab is not employed and that do not run Windows 11, versions 26H1, 25H2 or 24H2. However, please note that there might be non-Microsoft applications that utilize Scan Cab. Review the documentation for any software and update deployment tools that might be in use for your organization, to understand if this is applicable in your environment. What will happen: Administrators can re-deploy the updated Scan Cab via their usual processes. For detailed guidance, see the Additional information section below. Additional information: Updated Scan Cab: Download the new Scan Cab here Announcing a smaller WSUS Scan Cab - Microsoft Tech Community: Learn more about WSUS and the Scan Cab process CVE-2026-62721: Windows User-Mode Power Service (UMPS) Elevation of Privilege Vulnerability CVE-2026-85921: Windows Secure Kernel Mode Elevation of Privilege Vulnerability Using WUA to Scan for Updates Offline - Win32 apps: Windows Update Agent (WUA) can be used to scan computers for security updates without connecting to Windows Update WSUS and the Catalog Site: The Catalog Site used by WSUS to import updates and drivers -
(Updated) Microsoft Outlook for iOS/Android: Improved Contacts with profile enrichment and duplicate management
MC1093912 · stayInformed · normal · Updated 09/14/2026 16:45
Services: Exchange Online, Microsoft 365 apps
Read message
Updated September 14, 2026: We have updated the timeline. Thank you for your patience. We’re enhancing the contact experience in Microsoft Outlook Mobile (iOS and Android) by introducing profile-enriched contacts and automatic duplicate contact management. These improvements aim to streamline contact views and provide richer organizational context. This message is associated with Microsoft 365 Roadmap ID 493753. This feature has previously been released to the People Hub in new Outlook for Windows. More details in MC927963 (Updated) New Microsoft Outlook for Windows: People Hub improvements (published November 2024, updated April 2025). [When this will happen:] General Availability (Worldwide): We will begin rolling out mid-July 2025 (previously late June) and expect to complete by mid-November 2026 (previously end of September). [How this will affect your organization:] Before this rollout, Outlook Mobile may have displayed multiple entries for the same contact and lacked organizational profile context. After this rollout: Contacts will be unified into a single enriched view, displaying additional profile information from your organization’s directory (where available). Identical duplicate contacts will be automatically hidden. These enhancements will be on by default and apply to both iOS and Android versions of Outlook Mobile. No admin controls exist. Users can access their contact list by selecting Contacts from the Apps section in the Outlook Mobile app. [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 internal documentation. After the feature is rolled out, please ensure that users have updated to the latest version of Outlook for iOS or Outlook for Android. Learn more: Manage Outlook contacts in your organization - Microsoft Support -
Microsoft Purview: Integration with Entra GSA Internet Access to enable sensitive file filtering at the network layer
MC1181769 · stayInformed · normal · Updated 09/11/2026 20:33
Services: Microsoft Purview
Read message
Updated September 11, 2026: We have updated the timeline. Thank you for your patience. [Introduction] To help organizations better protect sensitive files in transit, we're introducing a public preview for extending Microsoft Purview Data Loss Prevention (DLP) policies to the network through integration with Entra Global Secure Access Internet Access. Through this integration, organizations can intercept and inspect file traffic at the network layer and enforce actions based on DLP policy conditions. It helps prevent sensitive files from being shared with untrusted cloud applications through browsers, apps, APIs, add-ins, and more—including generative AI platforms, cloud storage, and content-sharing services—while managing alerts and incidents through Purview and Microsoft Defender. This message is associated with Roadmap ID 522096. [When this will happen:] Public preview: Rollout begins mid-November 2025 and completes by mid-December 2025. General availability: Rollout begins end of September and completes by end of October 2026 (previously end of September). [How this affects your organization:] Who is affected: Microsoft 365 tenants with E3 or E5 licenses; Admins managing Microsoft Purview DLP and Entra Global Secure Access. What will happen: A new “Inline Web Traffic” scenario will be available in Purview DLP policy creation. Admins can configure granular policies and rules to detect and protect sensitive files transmitted to over 35,000 unmanaged cloud applications. Policy matches, alerts, and incidents will be managed centrally in Microsoft Purview and Microsoft Defender. The feature will be available by default but requires configuration to activate. [What you can do to prepare:] Ensure your GSA administrator configures the following in Entra Global Secure Access: Enabled the internet access traffic profile and ensure the correct user assignments apply. Configure TLS inspection and configure a TLS inspection policy. Create a file policy and add a rule that specifies the action "Scan with Purview". Configure a security profile with the above policies and link it to a conditional access policy. Your global admin must activate Purview pay-as-you-go to enable this capability. No charges will apply during public preview. Review your current DLP and network configurations to assess impact. Communicate this change to helpdesk and security teams. Update internal documentation to reflect new policy options. For more details, refer to: Learn about data loss prevention [Compliance considerations:] Compliance Area Explanation Alters how existing customer data is processed Sensitive file traffic is inspected at the network layer before reaching unmanaged cloud apps. Introduces AI/ML capabilitiesDLP policies may interact with generative AI platforms to prevent data leakage. Modifies DLP enforcementAdds network-layer enforcement to existing Purview DLP capabilities. Adds integration to extend Purview DLP controls Integrates with Entra Global Secure Access Internet Access. Includes admin controlControlled via Purview and Entra admin portals. Can be controlled through Entra ID group membership Policy scoping can leverage Entra ID groups. -
Data Privacy: Microsoft Online Services Subprocessor Disclosure
MC1470426 · stayInformed · normal · Updated 09/11/2026 19:52
Services: Microsoft 365 suite
Read message
A Data Privacy message regarding your organization is available within Message Center. The contents of this message can be accessed within Message Center by a Global Administrator or someone designated as a Message Center Privacy Reader. Please sign in to Admin Center to view the details of this message in the M365 Message center. -
(Updated) Viva Engage: New post creation experience
MC1411432 · stayInformed · normal · Updated 09/11/2026 18:29
Services: Microsoft Viva
Read message
Updated September 11, 2026: We have updated the timeline. Thank you for your patience. [What and Why:] We are updating the post creation experience in Viva Engage with a simpler, more intuitive layout. This change helps users create and publish posts with fewer distractions, clearer organization of tools, and improved accessibility. The update supports personal and team productivity by making it easier for employees to share updates, start conversations, and engage with their communities in Viva Engage. This message is associated with Microsoft 365 Roadmap ID 558935. [Rollout Schedule:] General Availability (Worldwide): Rollout will begin in mid-July 2026 and is expected to complete by mid-October 2026 (previously mid-August). [Impact on Your Organization:] Who is affected: Users who create posts in Viva Engage. Platforms/Services: Viva Engage What will happen: Users will see a refreshed post creation experience in Viva Engage. The layout for creating posts will be updated to make publishing clearer and easier. Tools used to create posts will be organized more intuitively. Accessibility improvements will be included in the updated experience. Existing post creation capabilities will remain the same. No admin configuration is required. This experience will be available by default as it rolls out. The following screenshots highlight the updated experience: Screenshot 1: Post on behalf of selection is now at the top of the Publisher: Screenshot 2: Destination (Storyline and Community) selection is at the top of the Publisher: Screenshot 3: Simplified toolbar at the bottom of the Publisher shows the most used options by default. Additional options can be accessed by selecting the + (plus) icon: Screenshot 4: You can change the post type using the menu at the top of the Publisher [Action Required/Recommendations:] No admin action is required. We recommend that you: Inform users that the Viva Engage post creation experience is being updated. Update internal training or support materials that show the current post creation layout. Notify help desk or support teams so they can answer questions about the new layout. [Compliance considerations:] No compliance considerations identified, review as appropriate for your organization. -
30-Day Reminder: Windows Server 2022 will reach end of mainstream support on October 13, 2026
MC1470756 · stayInformed · normal · Updated 09/11/2026 17:00
Services: Windows
Read message
On October 13, 2026, Windows Server 2022 will reach end of mainstream support. The October 2026 security update will be the last mainstream support update available for this version. After this date, Windows Server 2022 will transition to extended support, which includes security updates at no additional cost, and will continue to receive monthly security updates through October 14, 2031. For more information, see the Fixed Lifecycle Policy. Hotpatch update support for Windows Server 2022 Datacenter: Azure Edition has been extended through October 2027. Devices enrolled in Hotpatch updates will continue to receive monthly security updates without requiring a restart. To learn more, see the Windows Server 2022 lifecycle page. Windows Server 2025 is now the latest Long-Term Servicing Channel (LTSC) release for Windows Server. To help keep your environment protected and supported, plan to upgrade to Windows Server 2025 for full mainstream support. To download a free 180-day evaluation, visit the Microsoft Evaluation Center. Evaluate upgrade options and begin deployment testing early to help ensure a smooth transition. For detailed lifecycle dates, see the Windows Server 2022 lifecycle page. For servicing timelines and related resources, see Windows Server release information, Lifecycle FAQ - Windows Server, and Microsoft Lifecycle Policy search tool. -
Microsoft Copilot Cost Management: September Updates
MC1470425 · stayInformed · normal · Updated 09/10/2026 23:05
Services: Microsoft 365 Copilot Chat
Read message
[What and why:] We're rolling out several enhancements to Cost Management and Copilot Credits governance to simplify policy administration, improve consumption visibility, and provide more flexible spending controls. [Rollout schedule:] These updates will begin rolling out in early September 2026. [Impact on your organization:] Auto-apply new services to spending policies Spending policies can now automatically apply to newly released UBB Copilot services and agents. The Auto-apply new services setting is enabled by default for all policies, helping ensure governance remains in place as new services become available. Important: The Auto-apply new services setting is enabled by default for all spending policies. As new services and agents become available, they will automatically inherit policy coverage. Admin action: Review existing policies and disable the setting where future services should not automatically inherit policy coverage. User limit threshold email alerts Administrators can now configure email notifications that alert admins as users approach their spending limits Admin action: Configure threshold percentages and enable notifications for applicable policies Expanded access to consumption reporting Consumption dashboards are now available to additional read-only roles, including AI Reader, Global Reader, and License Administrator, providing broader visibility into spending and usage trends. No Admin action needed. Enhanced consumption reporting New reporting capabilities provide:Consumption visibility across Prepaid (P3) and Pay-as-you-Go (PayG) credit usage. Capacity pack consumption breakdowns across Microsoft Admin Center (MAC) and Power Platform Admin Center (PPAC). Admin action: Review updated dashboards and reporting processes. Policy-level reporting Consumption dashboards now include a dedicated policy view, enabling administrators to analyze usage and spending by spending policy. No Admin action needed. Custom approval policies for Cowork credit requests Administrators can create custom request policies to route Cowork credit requests, and future supported service requests, to alternate approval workflows. Admin action: If desired, configure approval routing through the new Request Policies tab in the Credit Requests experience. User spending follows users across policies User consumption now carries forward when users move between spending policies. For example, a user who has already consumed 500 credits under one policy will retain that 500-credit usage history after being assigned to another policy. This prevents spending limit resets and improves policy enforcement consistency. Admin action: No action required. Review any internal processes that rely on moving users between policies. Healthy spending policy improvements New guidance and management experiences help administrators maintain effective and sustainable spending policies. Organizations may receive recommendations when policies are identified as potentially unhealthy or misconfigured with respect to limits and cost guardrails. Admin action: Review and update policies when prompted. [Action required / Recommendations:] Review spending policies and Auto-apply settings. Configure user threshold notifications. Familiarize reporting stakeholders with the new consumption views. Review policy-level reporting capabilities. Configure custom request approval routing as needed. [Compliance Considerations:] Does the change alter how admins can monitor, report on, or demonstrate compliance activities?Enhanced reporting introduces policy-level consumption views, expanded reporting access, P3 vs. PayG reporting, and additional attribution data for administrative oversight and governance. Does the change include an admin control and can it be controlled through Entra ID group membership?Administrators can configure spending policies, threshold notifications, custom approval workflows, and automatic policy coverage for future services. Does the change introduce or significantly modify AI/ML or agent capabilities that interact with or provide access to customer data?Governance controls are being extended to future Copilot services and agents through automatic policy coverage. -
Microsoft OneDrive and SharePoint: Anchored comments in the PDF viewer
MC1470416 · stayInformed · normal · Updated 09/10/2026 22:47
Services: SharePoint Online, Microsoft OneDrive
Read message
[What and why:] Microsoft is adding anchored comments to the PDF viewer in OneDrive and SharePoint on the web. Users can attach a comment to a specific spot on a page, or to selected text, and collaborate through replies and @mentions — bringing PDF review to parity with commenting in Office documents. This feature will be on by default and requires no admin action. [Rollout schedule:] General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out mid-October 2026 and expect to complete by mid-November 2026. Note: This is a gradual rollout, so not all users will see the feature at the same time. [Impact on your organization:] Anchored comments appear in the Microsoft 365 file viewer when a PDF is opened in OneDrive or SharePoint on the web. Users will be able to: Comment anywhere — click a spot on a page to add a comment anchored to that location. Comment on text — select text and attach a comment to it. Collaborate — reply, @mention, see visual anchor indicators, and navigate between a comment and its anchored content; full keyboard and screen-reader support. Who is affected: Users viewing PDFs in OneDrive and SharePoint on the web. Default state: On by default for eligible users; no new anchored-comments-specific admin control is introduced. Admin control: No new anchored-comments-specific control is introduced. Existing protections apply — sensitivity labels, Purview DLP, and Information Rights Management (IRM) on rights-managed libraries. [Action required / Recommendations:] No admin action is required before rollout. You may want to: Inform your PDF users and helpdesk/support teams about the new commenting experience. Update internal collaboration guidance (commenting on a spot, text, or annotation; replies and @mentions; downloading with or without comments). -
(Updated) Create and edit SharePoint pages with Copilot-powered AI
MC1282683 · stayInformed · normal · Updated 09/10/2026 21:48
Services: SharePoint Online
Read message
Updated September 10, 2026: We have have updated the timeline. Thank you for your patience. [Introduction] We are introducing Create and edit SharePoint pages with Copilot-powered AI, a new authoring experience that helps page editors plan, create, and refine SharePoint pages using natural language prompts. This feature reduces the time and effort required to build high-quality pages by allowing authors to generate and edit content, layouts, and web parts directly through an AI-assisted editing panel, grounded in their organization’s existing Microsoft 365 content. [When this will happen] Targeted Release: We began rolling out in early April 2026 and expect to complete by mid-April 2026. General Availability (Worldwide): We have begun rollout and expect to complete by late September 2026. [How this affects your organization] Who is affected SharePoint page editors in Microsoft 365 tenants Only users assigned a Microsoft 365 Copilot license Production tenants (not GCC or Gallatin) What will happen Page editors with a Copilot license will see a new AI authoring panel automatically open when editing SharePoint pages: Users can:Generate new page sections using natural language prompts: Edit existing text, layouts, and web parts through chat-based instructions. Attach Microsoft 365 files as grounding context for better AI-generated results: AI-generated changes are inserted directly into the page and visually highlighted: Users can switch between AI-assisted editing and standard manual editing at any time: Chat history persists for the duration of the editing session unless manually cleared: This feature is enabled by default for eligible users with Copilot licenses. [What you can do to prepare] No action is required to prepare for this change. Recommended actions: Inform SharePoint page authors about the new AI-assisted editing experience. Update internal documentation or training materials if you provide guidance on SharePoint authoring. Ensure Copilot license assignments align with who should have access to AI-powered page creation. [Compliance considerations] QuestionAnswer Does the change alter how existing customer data is processed, stored, or accessed (for example, documents or page content)?Yes. Copilot uses existing SharePoint page content and user-selected Microsoft 365 files (such as documents) as grounding context to generate or edit page sections. Content is processed at the time of generation to produce suggestions and changes directly in the page editor. Does the change introduce or significantly modify AI or agent capabilities that interact with customer data?Yes. This change introduces a Copilot-powered AI authoring experience in SharePoint. The AI assists users by generating and editing page content, layouts, and web parts based on prompts and selected Microsoft 365 content. Does the change provide users a new way of interacting with generative AI?Yes. Page editors with a Copilot license can interact with generative AI directly within the SharePoint page editing experience using natural language chat prompts to plan, create, and modify content. Does the change include an admin control, and can it be controlled through Entra ID group membership?Yes. Access to the feature is governed by Microsoft Copilot license assignment. Only users assigned a Copilot license can access the AI authoring panel. There is no additional tenant-level toggle specific to this feature. Does the change allow users to enable or disable the feature themselves?Yes. While the feature is available by default for Copilot-licensed users, users can choose when to use AI during page editing and can switch between AI-assisted editing and standard manual editing at any time. -
(Updated) Microsoft Word: Similarity Checker retirement
MC1466753 · planForChange · normal · Updated 09/10/2026 21:43
Services: Microsoft 365 apps
Read message
Updated September 10, 2026: We have updated the timeline. Thank you for your patience. [What and why] We are retiring Similarity Checker in Microsoft Word on October 3, 2027. After the retirement date, Similarity Checker will no longer be available as part of the Microsoft Editor experience in Word. This change allows us to focus on experiences and capabilities that are more broadly used across Microsoft Word. [Rollout schedule] Worldwide, GCC, and DoD: Beginning early October 2027 [Impact on your organization] Who is affected Organizations and users that currently use Similarity Checker in Microsoft Word Platforms and services Microsoft Word Microsoft Editor What will happen Similarity Checker will be removed from Microsoft Word. After retirement, users will no longer be able to access Similarity Checker through the Editor experience in Word. Other Microsoft Word writing, editing, and citation capabilities will not be affected. Microsoft Editor will continue to provide spelling, grammar, clarity, and style suggestions. Microsoft 365 Copilot capabilities in Word are not affected by this change. Note: Copilot is not intended to serve as a formal similarity, plagiarism, or originality validation tool. [Action required and recommendations] No action is required. If your organization currently uses Similarity Checker: Review workflows that depend on Similarity Checker. Inform users who rely on the feature about the upcoming retirement. Evaluate alternative solutions if formal similarity or originality validation is required. Update internal documentation or training materials that reference Similarity Checker. [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
(Updated) The September 2026 Scan Cab is available
MC1469525 · preventOrFixIssue · normal · Updated 09/10/2026 21:35
Services: Windows
Read message
Updated September 10, 2026: The September 2026 Scan Cab includes metadata for Microsoft Office update (KB5002923). An earlier version of this notice incorrectly stated that it did not and that an additional Scan Cab would follow soon — no additional Scan Cab will be released. Deploy the September 2026 Scan Cab as normal; no further action is required. IMPORTANT: This notice only affects environments where Scan Cab is used to check for update compliance. What and why: The September 2026 Scan Cab was made available at 2:00 PM PDT, September 8, 2026. It helps determine whether a Windows device needs security updates without connecting to the Windows Update service. Rollout schedule: The September 2026 Scan Cab is available now. Who is affected: The Wsusscn2.cab file is a cabinet file that is signed by Microsoft and contains information about Microsoft security-related updates. Devices that aren't connected to the Internet can be scanned to see whether these security-related updates are present or required. The Wsusscn2.cab file doesn't contain the security updates themselves so you must obtain and install any needed security-related updates through other means. What will happen: You can download and deploy the September 2026 Scan Cab via the usual processes. For detailed guidance, see the Additional information section below. No action is required on environments where Scan Cab is not employed. However, please note that there might be non-Microsoft applications which utilize Scan Cab. Review the documentation for any software and update deployment tools used in your organization to understand if this is applicable in your environment. Additional information: Updated Scan Cab: Download the new Scan Cab here Announcing a smaller WSUS Scan Cab: Learn more about WSUS and the Scan Cab process Using WUA to Scan for Updates Offline: Windows Update Agent (WUA) can be used to scan computers for security updates without connecting to Windows Update WSUS and the Catalog Site: The Catalog Site used by WSUS to import updates and drivers -
Windows Office Hours: September 17, 2026
MC1470296 · stayInformed · normal · Updated 09/10/2026 17:00
Services: Windows
Read message
If you are an IT admin with questions about managing and updating Windows, we want to help. Every third Thursday of the month, we host a live chat-based event on the Tech Community called Windows Office Hours. Members of the Windows, Microsoft Intune, Windows Autopilot, Windows Autopatch, and Windows 365 engineering teams will be standing by to answer your questions. Want to attend the September 17 session of Office Hours? Add it to your calendar and select Attend on the event page to let us know you're coming. There is no video or live meeting component. Simply visit the event page, sign in to the Tech Community, and leave your questions in the Comments section. You can also bookmark https://aka.ms/Windows/OfficeHours for upcoming dates (and the ability to add this event to your calendar). We look forward to helping you. -
Change in sender email address for Copilot emails
MC1469962 · stayInformed · normal · Updated 09/09/2026 22:32
Services: Microsoft 365 suite, Microsoft 365 Copilot Chat
Read message
[What and Why:] To align with the Microsoft 365 Copilot transition to Microsoft Copilot, we are updating the sender identity for Microsoft Copilot educational and product enablement emails. These emails help users learn about Microsoft Copilot capabilities included in their subscriptions, discover new features, and improve productivity with the tools available to them. This change provides consistent branding across Microsoft Copilot experiences while ensuring users continue to receive guidance, tips, and service updates. Rollout Schedule: General Availability (Worldwide): Mid-September 2026 [Impact on Your Organization:] Who is affected: Organizations that have opted in to receive Microsoft product and service communications for users with Microsoft Copilot features enabled. Microsoft 365 administrators who manage mail flow rules, allow lists, or safe sender configurations. Users who are newly enabled for Microsoft Copilot services and capabilities and/or users previously enabled who are already receiving emails. Platforms/Services: Microsoft Copilot Exchange Online Microsoft Defender for Office 365 Microsoft 365 end-user communications What will happen: Users continue to receive transactional service-enablement emails when they are granted access to Microsoft Copilot capabilities. Sender address will be updated to Microsoft Copilot (microsoftcopilotupdates@microsoft.com). Users continue to receive educational and product enablement emails. Sender address will be updated to Microsoft Copilot (microsoftcopilotupdates@microsoft.com). Emails will no longer be sent from Microsoft 365 Copilot (m365copilotupdates@microsoft.com). The content and purpose of these emails remain unchanged. Existing mail flow rules, safe sender entries, and allow lists that reference the previous sender address may need to be updated. This change is enabled automatically and does not require tenant configuration to take effect. [Action Required/Recommendations:] Review mail flow rules, transport rules, safe sender configurations, and allow/block lists that reference m365copilotupdates@microsoft.com. Update those configurations to use microsoftcopilotupdates@microsoft.com. Add microsoftcopilotupdates@microsoft.com to your organization's safe sender or allow list to help ensure delivery. Review internal documentation or help desk guidance that references the previous sender address. Communicate this change to support teams if they assist users with email filtering or message delivery issues. Configure allow entries in Microsoft Defender for Office 365 Ensure users receive Microsoft Copilot educational emails [Compliance Considerations:] No compliance considerations identified, review as appropriate for your organization. -
(Updated) Microsoft Teams Rooms on Android: room users can change the app language
MC1461164 · stayInformed · normal · Updated 09/09/2026 17:29
Services: Microsoft Teams
Read message
Updated September 9, 2026: We have updated the timeline. Thank you for your patience. [What and why:] Teams Rooms on Android users will soon be able to temporarily change the display language of the Teams app directly from the room console, without requiring administrator involvement. This update brings Teams Rooms on Android in line with the existing Teams Rooms on Windows experience and supports organizations that operate in multilingual environments or have regional language requirements. The language selection applies only to the current session. When the Teams Rooms app restarts, it automatically returns to the room's configured default language, ensuring the device is not left in an unexpected language for the next user. [Rollout schedule:] Targeted Release (Worldwide): Rollout begins in late June 2026 and is expected to complete by late September 2026. General Availability (Worldwide): Rollout begins in late September 2026 (previously early September) and is expected to complete by late October 2026. [Impact on your organization:] This feature will be available by default for Teams Rooms on Android devices running Teams Rooms app version 2.12.0 or later. A new Language option will appear on the Teams Rooms console home screen. Selecting the option opens a list of available Teams app languages. After a language is selected, the Teams Rooms app reloads and briefly displays the Teams curtain before returning in the chosen language. The language choice is session-scoped and automatically resets to the room's configured default language the next time the Teams Rooms app restarts. User language selections do not permanently override administrator-configured language settings. The change applies only to the Teams Rooms app and does not affect the device operating system, peripherals, keyboard language, or administrative settings. [Action required / Recommendations:] No admin action is required. The feature will be enabled automatically when eligible devices update to Teams Rooms on Android app version 2.12.0 or later. We recommend that administrators: Confirm that Teams Rooms on Android devices are running a supported operating system version and are configured to receive the Teams Rooms app version 2.12.0 update. Verify that the default Teams app language is configured appropriately for each room, since rooms will revert to this language after each app restart. Update room guidance, signage, and user documentation to explain that language selection is temporary and applies only to the current session. [Compliance considerations:] No compliance considerations identified, review as appropriate for your organization. -
IT resources to plan, prepare, and deploy Windows
MC1469811 · stayInformed · normal · Updated 09/09/2026 16:57
Services: Windows
Read message
What and why: New and updated resources are available whether you’re a seasoned IT pro or earlier in your career. Learn how to effectively roll out feature updates to Windows devices and Microsoft 365 Apps in advance of the upcoming Windows 11, version 26H2. Rollout schedule: All these resources are freely available now. The Windows 11, version 26H2 annual feature update is coming soon. Impact on your organization: You can deploy updates faster and support your remote workforce by following a three-phase process: plan > prepare > deploy. Action required/recommendations: Complete a redesigned Microsoft learning path for free. It consists of three learning modules: Plan to deploy updates for Windows clients and Microsoft 365 apps (23 mins) Prepare to Deploy Updates for Windows Client and Microsoft 365 Apps (44 mins) Deploy Updates For Windows Client And Microsoft 365 Apps (48 mins) Additionally, watch a fresh podcast series: Touchstone Podcast Series: Cloud Native Management — Part One: “Plan” (37 mins) Touchstone Podcast Series: Cloud Native Management — Part Two: “Plan" (32 mins) Touchstone Podcast Series: Cloud Native Management — Part Three: "Prepare" (45 mins) Touchstone Podcast Series: Cloud Native Management — Part Four: "Deploy" (45 mins) Compliance considerations: No compliance considerations are identified. Review as appropriate for your organization. -
[Whiteboard] Standalone app deprecation (Windows, Mobile)
MC1469557 · planForChange · normal · Updated 09/09/2026 00:47
Services: Microsoft OneDrive, Microsoft Teams, Microsoft 365 apps
Read message
[What and why:] Microsoft Whiteboard is retiring the standalone Whiteboard applications for Windows, iOS, and Android. Beginning October 16, 2026, the standalone Microsoft Whiteboard apps will no longer be supported for work or school accounts and personal Microsoft accounts. Users should access Whiteboard through Microsoft Teams and supported web experiences going forward. After the retirement date, already-installed standalone apps will display a retirement experience and will no longer provide access to Whiteboard galleries or existing Whiteboard content. This post is a follow-up reminder to MC1441775 (Microsoft Whiteboard: Retirement of legacy whiteboards and transition to OneDrive-backed whiteboards) and focuses on the upcoming retirement of the standalone Microsoft Whiteboard applications. Find more details: Whiteboard Standalone App Retirement | Microsoft Support [Rollout schedule:] Worldwide, GCC, GCC High, DoD: We will begin rolling out on mid-October 2026 and expect to complete by mid-October 2026. [Impact on your organization:] Organizations and users who currently rely on the standalone Microsoft Whiteboard apps for Windows, iOS, or Android will be affected. Beginning October 16, 2026, the standalone apps will no longer be supported and users will need to access Whiteboard through Microsoft Teams or supported web experiences. This change only affects the standalone applications. Whiteboard functionality available through Microsoft Teams continues to be supported. Organizations that have already adopted Teams-based Whiteboard experiences will experience minimal impact. [Action required / Recommendations:] Admins should prepare their organizations for the retirement of the standalone Whiteboard apps by: Communicating the retirement date (October 16, 2026) to affected users. Encouraging users to transition to Microsoft Whiteboard in Microsoft Teams and supported web experiences before the retirement date. Updating internal documentation, training materials, onboarding content, and support resources that reference the standalone Whiteboard applications. Validating that users know how to access and collaborate on Whiteboards through Teams and supported web experiences before the standalone apps are retired. No additional administrative configuration is required. However, organizations should ensure users are prepared to use the supported Teams-based Whiteboard experience before the retirement date. -
(Updated) Cross-post SharePoint News to Engage
MC1466762 · stayInformed · normal · Updated 09/08/2026 18:01
Services: SharePoint Online, Microsoft Viva
Read message
Updated September 8, 2026: We have updated the content. Thank you for your patience. [What and why:] This feature allows SharePoint authors to distribute news posts to an Engage community or storyline with full fidelity rendering and a unified conversation experience. SharePoint News post will appear in full fidelity in Engage across feeds, digests, Outlook, Teams, desktop, web and mobile apps. When distributed, the SharePoint News comments module is replaced with the richer Engage conversation module, ensuring a single, shared discussion thread across surfaces. [Rollout schedule:] General Availability (Worldwide): We will begin rolling out on late September 2026 and expect to complete by late October 2026. [Impact on your organization:] SharePoint helps communicators create rich, engaging stories, announcements or news posts for their organizations. Viva Engage helps those stories travel through the communities and conversations where people connect every day. With SharePoint News and Viva Engage cross-posting, authors can now bring these experiences together. The new experience lets you distribute a SharePoint news post to a Viva Engage storyline or community in full fidelity, while comments, replies, and reactions made in SharePoint or across Engage surfaces remain synchronized as one conversation. Readers get the same experience whether they use Engage on the web or mobile app or the Engage apps in Microsoft Teams and Outlook. Authors can reach these audiences without recreating content or managing separate discussions. [Action required / Recommendations:] Admins may want to let users know about this change or refresh any training on distributing content from SharePoint to Engage. Review the following documentation: Introducing SharePoint News and Viva Engage cross-posting -
Notice: The September 2026 Scan Cab for Microsoft updates is delayed
MC1469328 · stayInformed · normal · Updated 09/08/2026 17:41
Services: Windows
Read message
Note: This notice only affects environments where Scan Cab is used to check for Microsoft update compliance. What and why: The Scan Cab for the September 2026 Microsoft security updates is currently delayed and has not yet been released. Rollout schedule: We expect to release it as soon as possible and will provide an update as more information becomes available. Thank you for your patience. Who is affected: IT administrators who rely on Scan Cab to check for update compliance can monitor our communications for updates. What will happen: Updates on the availability of this month's Scan Cab will be communicated as new information becomes available. Additional information: Learn more about the Scan Cab process: Announcing a smaller WSUS Scan Cab Use Windows Update Agent (WUA) to scan computers for security updates without connecting to Windows Update: Using WUA to Scan for Updates Offline - Win32 apps Documentation on the Catalog Site used to import updates and drivers: WSUS and the Catalog Site -
The September 2026 Windows security update is now available
MC1469327 · stayInformed · normal · Updated 09/08/2026 17:41
Services: Windows
Read message
The September 2026 security update is now available for all supported versions of Windows. We recommend that you install these updates promptly. For more information about the contents of this update, see the release notes, which are accessible from the Windows 11 update history page. To learn more about the different types of monthly quality updates, see Understanding Windows monthly updates. Highlights for the Windows 11, version 25H2 update: This security update includes improvements that were part of update KB5120998 (released August 27, 2026). This update expands high confidence device targeting data, increasing coverage of devices eligible to automatically receive new Secure Boot certificates. Devices receive the new certificates only after demonstrating sufficient successful update signals, maintaining a controlled and phased rollout. This update makes quality improvements to the servicing stack, which is the component that installs Windows updates. Short on time? Watch the Windows 11 release notes video for this month’s tips. For instructions on how to install this update, see the KB article for your operating system listed below: Windows 11, version 26H1: KB5124012 Windows 11, versions 25H2 and 24H2: KB5124008 Windows 11, version 23H2: KB5122880 Windows 11 Enterprise LTSC 2024: Baseline KB5124008 Windows 10, versions 22H2 and 21H2: KB5122878 Windows 10 Enterprise LTSC 2019 and Windows Server 2019: KB5122876 Windows 10 LTSB 2016 and Windows Server 2016: KB5123099 Windows Server 2025: KB5122871 Windows Server 2025 Datacenter: Azure Edition: Baseline KB5122871 Windows Server 2022: KB5122882 Windows Server 2022 Datacenter: Azure Edition: Baseline KB5122882 Windows Server 2012 R2: KB5123066 Windows Server 2012: KB5123065 Note: With recent and upcoming Windows updates over the next few months, a limited number of consumer and business devices might experience one additional restart during installation. This one‑time restart occurs after a Secure Boot certificate update is applied as part of the Secure Boot update process. -
Deprecation for Manifest V2 (MV2) browser extensions support in Microsoft Edge
MC1467356 · planForChange · normal · Updated 09/04/2026 22:42
Services: Microsoft 365 suite
Read message
[What and why:] Microsoft Edge is retiring support for Manifest V2 (MV2) browser extensions and is moving fully to Manifest V3 (MV3). MV2 will no longer run in Microsoft Edge after enterprise deprecation completes. Enterprise deprecation is currently planned for early 2027. This change delivers customer value by pinging performance and security improvements. MV3 enforces stricter permissions, blocks remotely hosted code, and reduces the attack surface associated with legacy MV2 extensions. To minimize disruption on the customers, better MV3 replacements are available on Edge Add-ons store. [Rollout schedule:] Worldwide, GCC, GCC High, DoD: We will begin rolling out on early January 2027 and expect to complete by late April 2027. [Impact on your organization:] Who is affected All tenants and users of Microsoft Edge (consumer and enterprise) who have Manifest V2 extensions installed. Enterprise administrators who deploy or allow-list MV2 extensions via Microsoft Edge policies (for example, ExtensionInstallForcelist, ExtensionInstallAllowlist, or ExtensionManifestV2Availability). Extension developers who publish MV2 extensions to Microsoft Edge Add-ons through Microsoft Partner Center. Managed devices are unaffected during the consumer rollout. A policy ExtensionManifestV2Availability will be provided to continue maintaining MV2 support. Managed devices are affected once enterprise deprecation begins. Platforms / Services Microsoft Edge (desktop) on Windows, macOS, and Linux — all channels: Canary, Dev, Beta, and Stable. Microsoft Edge Add-ons store — MV2 extension discovery, install, and updates. Microsoft Partner Center — Microsoft Edge Add-ons extension submissions and updates. Microsoft Edge policies — the ExtensionManifestV2Availability policy is removed at enterprise deprecation. What will happen MV2 extensions will begin showing deprecation warnings on the Manage Extensions page (edge://extensions) and on Microsoft Edge Add-ons product detail pages. MV2 extensions will no longer appear in Add-ons search. MV2 extensions will be disabled by default for consumer users; users will initially be able to re-enable them, and this option will phase out over time. New installs of MV2 extensions from Microsoft Edge Add-ons will be blocked. After enterprise deprecation, the ExtensionManifestV2Availability policy will be removed and MV2 extensions will stop working on all devices, including managed devices with the policy previously set. Existing MV2 configurations relying on the ExtensionManifestV2Availability policy will no longer take effect after enterprise deprecation. Microsoft Partner Center will stop accepting updates to MV2 extensions; updates that migrate an extension from MV2 to MV3 will still be accepted. No new extensions can be published as MV2 on Microsoft Edge Add-ons (already in effect since July 2022). [Action required / Recommendations:] Migration steps (a replacement exists — Manifest V3) Inventory MV2 extensions in your environment using Microsoft Edge management reporting or the Edge management service. Identify which MV2 extensions have an MV3 version on Microsoft Edge Add-ons and plan the update through your normal deployment process. For internal (line-of-business) MV2 extensions, migrate them to Manifest V3 using the Microsoft Edge migration guide and resubmit through Microsoft Partner Center. Update ExtensionInstallForcelist and ExtensionInstallAllowlist entries to reference the MV3 versions of the extensions you deploy. Configure ExtensionManifestV2Availability intentionally: keep MV2 available for your users during the consumer rollout only if needed, and plan to remove the dependency before enterprise deprecation. Deadline All migration off MV2 must be complete before the enterprise GA. After that date, MV2 extensions will not function in Microsoft Edge, and the ExtensionManifestV2Availability policy will be removed. Communication guidance Notify affected end users in advance, especially where an MV2 extension will not have a direct MV3 replacement. Update internal documentation and knowledge base articles that reference MV2 extensions or the ExtensionManifestV2Availability policy. Inform your helpdesk about the change so they can support users whose extensions are disabled or replaced, and share the MV3 alternatives being recommended. Engage extension vendors (third-party and internal) to confirm their MV3 timeline and align it to your enterprise deadline. -
Power BI subscriptions: Changes to notification delivery and sender experience
MC1467355 · planForChange · normal · Updated 09/04/2026 22:40
Services: Power BI
Read message
[What and why:] Power BI is making changes to how subscription notifications are delivered as part of ongoing efforts to improve notification delivery reliability, sender reputation, and long-term service health. As part of this change, customers may notice updates to sender identity, email formatting, notification presentation, and Copilot-generated summary formatting for some subscription scenarios. This change will roll out in phases as Power BI subscription scenarios are transitioned to the updated notification delivery experience. [Rollout schedule:] General Availability (Worldwide): Rollout is expected to begin in late September 2026 and continue in phases through early January 2027. [Impact on your organization:] Customers may notice changes in the way Power BI subscription emails are delivered and presented. Depending on tenant configuration and subscription scenario, customers may notice changes to sender identity used for Power BI subscription emails. Customers may also observe differences in: Email formatting Notification presentation Copilot-generated summary formatting No interruption to subscription delivery is expected. Existing subscriptions do not need to be recreated, and no changes to subscription schedules or recipient lists are expected. [Action required / Recommendations:] No tenant administrator action is required. Organizations that have configured mail-processing rules, routing rules, allow lists, inbox rules, safe-sender configurations, or automated workflows that depend on the historical sender identity (no-reply-powerbi@microsoft.com) should review those configurations and update them as needed following migration. Existing subscriptions do not need to be recreated. For additional information, including scenarios that may behave differently based on tenant configuration, please visit: https://aka.ms/subs-update-message-more-info -
(Updated) Microsoft Teams: RTMP-In port and domain changes required
MC1387814 · preventOrFixIssue · normal · Updated 09/04/2026 16:28
Services: Microsoft Teams
Action required by: 09/01/2026 07:00
Read message
Updated September 4, 2026: We have updated the content; the release of this required change is still paused at this time. We will announce via Message center when we are ready to proceed. We apologize for any inconvenience. [What and Why] Microsoft Teams is updating the port and domain requirements for Real-Time Messaging Protocol (RTMP)-In, which enables organizers to stream content into meetings, webinars, and town halls using external hardware or software encoders. This change improves reliability and scalability for Teams streaming scenarios. [Rollout Schedule] General Availability (Worldwide): We will announce via Message center when we are ready to proceed. [Impact on Your Organization] Who is affected Admins managing Microsoft Teams meetings, webinars, and town halls Event organizers who use RTMP-In with external encoders Platforms/Services Microsoft Teams (meetings, webinars, and town halls) What will happen New meetings, webinars, and town halls that use RTMP-In will require updated network access. Admins must allow the required ports and domain endpoints for RTMP-In streaming. Existing meetings, webinars, and town halls already configured with RTMP-In will continue to function through the end of 2026. RTMP-In continues to allow organizers to stream content into Teams from external hardware or software encoders. Without these updates, organizers may be unable to create or stream RTMP-In events, and newly created events may fail after December 31, 2026. Required network endpoints: Ports: 50118 and 50119 (RTMP/RTMPS) Domain: *.rtmpingest.mcr.teams.cloud.microsoft [Action Required/Recommendations] Action required by January 31, 2027. Review your organization’s firewall and network configuration. Allow outbound access to: Ports 50118 and 50119 (RTMP/RTMPS) Domain: *.rtmpingest.mcr.teams.cloud.microsoft Validate connectivity against official Microsoft 365 endpoint and firewall guidance. Communicate this change to your networking and IT teams. Update internal documentation if you support RTMP-In streaming scenarios. Learn more: Manage RTMP-In for Teams meetings, webinars, and town halls | Microsoft Teams | Microsoft Learn [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
Call Quality Dashboard Custom Detailed Reports
MC1466864 · stayInformed · normal · Updated 09/04/2026 03:32
Services: Microsoft Teams
Read message
[What and why:] Using Call Quality Dashboard (CQD) you can create customized charts and reports with rich diagnostic data on Teams calls and meetings in your organization. This existing feature is now available with an updated user interface with enhanced accessibility features and a fresh new look. [Rollout schedule:] General Availability (Worldwide): We will begin rolling out on early September 2026 and expect to complete by late September 2026. Public Preview (Worldwide): We will begin rolling out on mid August 2026 and expect to complete by late August 2026. [Impact on your organization:] Teams administrators who use CQD to create custom reports will now have a refreshed user interface when creating and viewing their own custom reports. These enhancements provide a more accessible experience, such as improved support for screen readers and keyboard navigation, as well as quality of life improvements like dark mode. [Action required / Recommendations:] No preparation is needed. Users will start seeing the new experience as the feature rolls out and all existing reports will remain available. Should it be necessary, users will have the ability to return to the previous experience during the rollout period. -
Microsoft Teams: Collect information with List Form in Workflows
MC1466757 · stayInformed · normal · Updated 09/03/2026 22:59
Services: Microsoft Teams
Read message
[What and Why:] We are introducing a new trigger in the Microsoft Teams Workflows app: A form is submitted. This trigger enables organizations to automate actions when users submit responses to forms built on SharePoint lists. Individual form responses can be used as workflow variables, enabling creators to post selected responses to a Teams channel and include additional details as threaded replies. Forms created with this experience are backed by SharePoint lists, providing organizations with familiar data management, governance, compliance, and export capabilities. [Rollout Schedule:] Targeted Release (Worldwide): Rollout begins in early September 2026 and is expected to complete by late September 2026. General Availability (Worldwide): Rollout begins in late September 2026 and is expected to complete by late October 2026. [Impact on Your Organization:] Who is affected: Users who can create workflows in Teams. Platforms and services: Microsoft Teams, Teams Workflows, SharePoint Lists. Users will see a new trigger, A form is submitted, when creating workflows from scratch in the Teams Workflows app. Forms are built on SharePoint lists, and each submitted response is stored as a SharePoint list item. The backing SharePoint list can be pinned as a tab in a Teams channel for visibility, tracking, and data export. Individual answers from form responses are available as workflow variables and can be used in workflow actions. Creators can post one response value as a parent Teams channel message and publish the remainder of the response as threaded replies. Existing workflows that use the equivalent trigger in Power Automate are not affected and will continue to operate as they do today. Access to form responses follows existing SharePoint site and list permissions. Form responses are governed by existing SharePoint retention, compliance, and information governance policies. Workflow executions use the connections and permissions of the workflow creator. The feature is enabled automatically and follows existing administrative controls and restrictions. If your organization restricts SharePoint site or list creation, limits access to the Workflows app, or uses Power Automate Data Loss Prevention (DLP) policies that block the trigger, those controls will continue to apply. [Action Required / Recommendations:] No admin action is required. The feature will roll out automatically according to the schedule above. We recommend that administrators: Notify users about the new workflow trigger and associated capabilities. Review and update internal documentation related to Teams Workflows and form-based business processes. Provide guidance on where users should create forms and backing SharePoint lists so that responses are stored in locations already governed by organizational policies. Review existing SharePoint permissions, site provisioning processes, and Power Automate DLP policies to ensure they align with organizational governance requirements. [Compliance Considerations:] Form responses are stored as SharePoint list items in a SharePoint site. Access to responses is governed by existing SharePoint site and list permissions. Responses are subject to existing SharePoint retention, compliance, and information governance policies. No new administrative controls are introduced. Existing SharePoint governance controls, Teams Workflows permissions, and Power Automate DLP policies continue to apply. Users can only build and run workflows if they already have permission to create workflows and access the underlying SharePoint resources. -
Project Online Essentials reaches End of Life on October 1, 2026: Action required
MC1466302 · planForChange · normal · Updated 09/02/2026 23:16
Services: Project for the web
Action required by: 10/01/2026 07:00
Read message
[What and Why:] Project Online Essentials has not been available for purchase since October 1, 2025. On October 1, 2026, Project Online Essentials will reach end of life. Project Online Essentials currently provides licensing rights for Project Online and Project Server through Client Access Licenses (CALs). Organizations should transition affected users to supported replacement licenses before October 1, 2026, to ensure they retain the required access and licensing rights. Project and Planner Plan 1 and Project and Planner Plan 3 provide broader capabilities than Project Online Essentials, including Planner Premium experiences, while continuing to provide applicable licensing rights for supported Project scenarios. [Impact on Your Organization:] Who is affected: Organizations with users who are currently assigned Project Online Essentials licenses. Platforms and services: Project Online Project Server Microsoft Planner What will happen: Project Online Essentials will reach end of life on October 1, 2026. After October 1, 2026, users assigned Project Online Essentials will no longer have access through that license. Users who require Planner Premium capabilities or applicable Project Server access rights must be assigned a supported replacement license. Organizations using Project Server should review their licensing requirements and ensure affected users have the appropriate access rights after the retirement date. [Action Required / Recommendations:] Complete the following actions before October 1, 2026: Review users who are currently assigned Project Online Essentials licenses. Determine whether those users require Planner Premium capabilities, Project Server access rights, or both. For users who require Planner Premium capabilities or Project Server CALs, assign Project and Planner Plan 1 or Project and Planner Plan 3. For users who require only Project Server Subscription Edition access rights, acquire the appropriate Project Server CALs. Complete all licensing transitions before October 1, 2026, to avoid disruption to user access. We recommend notifying affected project managers, resource managers, and Project Server users about the retirement and any licensing changes that may affect their access or available capabilities. [Compliance Considerations:] No compliance considerations identified, review as appropriate for your organization. -
Microsoft Teams: Report security concerns in meetings
MC1466296 · stayInformed · normal · Updated 09/02/2026 23:09
Services: Microsoft Teams
Read message
[What and why] We're introducing a new security reporting capability in Microsoft Teams meetings that allows meeting participants to report suspicious, malicious, or potentially fraudulent behavior during or after a meeting. This capability helps organizations identify and investigate threats such as phishing attempts, impersonation, scams, social engineering, and other suspicious activity. Submitted reports provide additional security signals that can be reviewed by administrators in Microsoft security and administration tools to support investigation and response workflows. This message is associated with Microsoft 365 Roadmap ID 569207. [Rollout schedule] Targeted Release: Beginning in late September 2026 and expected to complete by late September 2026 General Availability (Worldwide): Beginning in mid-October 2026 and expected to complete by late October 2026 [Impact on your organization] Who is affected Users participating in Microsoft Teams meetings on Windows, Mac, and web Platforms and services Microsoft Teams Microsoft Defender portal Teams admin center What will happen Users will see a new Report a concern option in the participant tile and participant pane during Teams meetings: Users will be able to report suspected phishing attempts, impersonation, scams, social engineering activity, and other security concerns directly from Teams meetings: Users will also be able to mark a previously reported participant as Not a concern. Relevant meeting metadata and limited contextual information will be collected to support security investigations and remediation activities. Information associated with reported meetings will be available for administrator review and investigation. Organizations with Microsoft Defender for Office 365 Plan 1, Microsoft Defender for Office 365 Plan 2, or Microsoft Defender XDR will be able to review detailed reported meeting submissions in the Microsoft Defender portal. Report information will also be available in the Teams admin center under Protection reports > User-reported security submissions. Administrators can investigate reported meetings and take actions according to their organization's security processes and policies. This capability will be enabled by default. [Action required and recommendations] Review your organization's security investigation and incident response processes before rollout. Recommended actions: Review Microsoft Defender user reporting settings and ensure reporting workflows align with organizational requirements. If your organization uses Microsoft Defender for Office 365 or Microsoft Defender XDR, verify that Teams meeting reporting is configured appropriately so detailed submissions are available to security investigators. Inform users about the new Report a concern capability and when it should be used. Inform users about the Not a concern option and when it should be used. Update security awareness training, incident response documentation, and internal guidance as needed. Verify that security administrators responsible for reviewing reports have the appropriate access to the Microsoft Defender portal or Teams admin center. [Compliance considerations] QuestionAnswer Does this change provide a new way for users to communicate security concerns to their organization?Yes. Users will be able to report suspected phishing attempts, impersonation, scams, social engineering activity, and other security concerns directly from Microsoft Teams meetings. Does this change collect new customer or user data for investigation purposes?Yes. Relevant meeting metadata and limited contextual information will be collected and made available to support security investigation and remediation activities. Does this change alter how administrators monitor, investigate, or report on security-related activities?Yes. Administrators will be able to review and investigate reported meetings through the Microsoft Defender portal and the Teams admin center. Does this change introduce new reporting or compliance-related records that administrators can review?Yes. User-submitted meeting security reports will be available in the Teams admin center under Protection reports > User-reported security submissions and, where licensed, in the Microsoft Defender portal. -
(Updated) Microsoft Teams: Prepare custom apps for private and shared channel compatibility
MC1459131 · stayInformed · normal · Updated 09/02/2026 18:25
Services: Microsoft Teams
Read message
Updated September 2, 2026: We have updated the timeline. Thank you for your patience. [What and Why:] Microsoft will begin rolling out a new feature in Teams admin center that helps admins identify custom line-of-business (LOB) apps that need updates to work in private and shared channels. Taking action now will help organizations ensure apps are available in these channels and work smoothly across evolving channel experiences. This message is associated with Microsoft 365 Roadmap ID 569019 [Rollout Schedule:] General Availability (Worldwide): We will begin rolling out mid-September 2026 (previously early September) and expect to complete by late September 2026. [Impact on your organization:] If apps are not updated to support private and shared channels, users may be unable to access those app experiences in these channels until the required updates are completed. Why this is important: Business continuity: As organizations adopt private and shared channels, updating LOB apps helps reduce the risk of app access gaps across channels. Lower operational overhead: Completing these updates early can help reduce admin escalations, helpdesk tickets, and reactive fixes. What you can expect Admins will be able to view a list of custom LOB apps that are not compatible with private and shared channels in the Teams admin center under Teams apps > Manage apps. Guidance is available now, enabling organizations to work with custom LOB app developers to plan and complete the required updates. Developers can review the documented requirements, update their apps, and validate supported scenarios. [Action Required / Recommendations:] Review custom apps used in team and channel scenarios across your organization. Ask your app developers to complete the required updates for private/shared channel scenarios. Validate that updated apps continue to support the scenarios your users rely on. Learn more: Teams connects shared and private channels - Teams | Microsoft Learn -
(Updated) Microsoft 365 Copilot app update: Simpler Copilot access
MC1454108 · planForChange · normal · Updated 09/02/2026 17:35
Services: Microsoft 365 Copilot Chat
Read message
Updated August 21, 2026: We have updated the timing below for the URL redirect to ensure customers have time to take action as appropriate. [What and Why:] As part of our ongoing efforts to simplify the Copilot experience for customers, we are beginning to roll out additional updates in the coming weeks. Like other Microsoft 365 apps, Copilot is moving to a single app experience across personal and work accounts. As part of this update, users will see clearer visual indicators in the app to help distinguish which account they are logged into, the app will adopt a simpler name and icon, and the web app URL will align more closely to Copilot. Security, compliance, privacy, and enterprise controls remain unchanged. [Rollout Schedule:] Starting mid-August 2026, worldwide rollout begins for the mobile and web apps. Opt-in early access begins for Windows and Mac apps. The copilot.cloud.microsoft URL will also be available in Frontier for testing. Starting early September 2026, standard rollout of URL redirect begins. Starting mid-September 2026, worldwide rollout begins for Windows and Mac apps. Starting late September 2026, deferred rollout of URL redirect begins for the web app. [Impact on your organization:] Who is affected All users accessing the Microsoft 365 Copilot app on web, desktop, or mobile. Applies to Microsoft 365 Copilot and Copilot Chat users. What's changing Users will see updated visual cues in the app that help identify whether they are in the Microsoft Entra ID (work or school) experience or the Microsoft account (personal) experience. These include a different background color for each account type and “Work” label under the user profile in the navigation pane (available in the web and desktop apps). Note: users will continue to see existing visual cues like the green data protection shield in their Microsoft Entra ID experience. The Microsoft 365 Copilot app will adopt a simpler name ("Microsoft Copilot app") and icon. If using the web app, the browser URL will transition from m365.cloud.microsoft to copilot.cloud.microsoft, and users will be automatically redirected. The Windows and Mac desktop apps will receive an updated architecture, which will support future enhancements in the app. Additionally, if your organization allows users to log into the app with their Microsoft accounts (personal), the following change will be relevant: Users can sign into the app with their Apple or Google credentials to access their Microsoft account (personal). [Action Required/Recommendations:] We recommend that administrators: If you would like to test the updated Windows and Mac apps before their general availability in September, you will be able to deploy the updated desktop app to a test group of devices in your organization. We will share opt-in instructions later this month when available. Note: Early access through opt-in is not available for organizations in special cloud environments. We will provide an update when early access becomes available for these environments. If you applied a group policy that filters the former Microsoft Copilot app from being saved in snapshots for Recall, this policy will not automatically carry over to the new Microsoft Copilot app. Review instructions here to set up Recall filters for the new Microsoft Copilot app. When available later this month, consider adding a branded footer in the Microsoft Copilot app to help users more easily recognize when they are signed in with their work or school account. The branded footer is only displayed in the Microsoft Entra ID (work or school) experience. Review MC1238432 for updated rollout timing and setup instructions for this feature. Inform users that they may begin seeing updated Microsoft Copilot URL, app name, and icon beginning mid-August, 2026. Review and update internal user communications, training, and help materials that reference the Microsoft 365 Copilot app name and icon or m365.cloud.microsoft URL. Please note that the following experiences in the app will not change: The Web URL change of the enterprise Copilot experience from m365.cloud.microsoft to copilot.cloud.microsoft remains under the *.cloud.microsoft domain continuing to inherit its security, compliance and enterprise allow-listing properties. Customers who followed recommended network configurations for Microsoft 365 Copilot do not need to make additional network changes. Admins can continue to limit Microsoft account (personal) access to the Copilot app using Tenant Restrictions. Users will continue to switch between their Microsoft account (personal) and Microsoft Entra ID (work or school) accounts using the account switcher in the navigation pane, like today's experience. Application ID is not changing. Existing policies will continue to function. Learn more. No changes to enterprise security, compliance, and government controls. Data entered into the Microsoft account (personal) experience does not flow into the Microsoft Entra ID (work or school) experience, and data entered into the Microsoft Entra ID (work or school) experience does not flow into the Microsoft account (personal) experience. -
Microsoft Defender XDR: DLP alerts will be set as behaviors by default
MC1465771 · planForChange · normal · Updated 09/01/2026 22:23
Services: Microsoft Defender XDR, Microsoft Purview
Read message
[What and why:] Microsoft Defender XDR is introducing a new built-in alert tuning rule that sets Microsoft Purview Data Loss Prevention (DLP) alerts as behaviors. This change is designed to reduce alert volume in Microsoft Defender XDR while preserving DLP investigation data in Advanced Hunting and the Microsoft Purview portal. Administrators can disable the rule if they prefer DLP events to continue generating standard alerts and appearing in the incident queues in Microsoft Defender XDR portal. [Rollout Schedule:] The alert tuning rule is available for review today in Microsoft Defender XDR. The rule will be enabled by default beginning October 12, 2026. [Impact on Your Organization:] Who is affected: Security administrators and analysts who use Microsoft Defender XDR and Microsoft Purview DLP. Services affected: Microsoft Defender XDR, Microsoft Purview Data Loss Prevention (DLP), Advanced Hunting. After the change takes effect: DLP alerts will no longer appear in the Microsoft Defender XDR incident queue by default. DLP signals will remain available for investigation through the BehaviorInfo and BehaviorEntities tables in Advanced Hunting. DLP alerts will continue to be available in the Microsoft Purview portal. This change is controlled by the built-in alert tuning rule: Set-As-Behavior - Data Loss Prevention (DLP) Alerts. [Action Required / Recommendations:] No action is required if you want to use the new default experience. If your organization relies on DLP alerts appearing in the Microsoft Defender XDR incident queue, disable the rule before October 12, 2026, to keep the current experience. The rule can also be disabled at any time after it takes effect. To continue receiving DLP alerts in the Microsoft Defender XDR incident queue: Go to Settings > Microsoft Defender XDR > Alert tuning. Locate the rule Set-As-Behavior - Data Loss Prevention (DLP) Alerts. Disable the rule. Additional Considerations Organizations that use Microsoft Defender XDR incidents and alerts as part of their Security Operations Center (SOC) processes should evaluate any downstream integrations, automation, reporting, monitoring, and alert triage workflows that depend on DLP alerts being present in the Defender XDR incident queue. If your organization accesses DLP alerts programmatically through Graph Alerts V2, note that once the rule takes effect, the data will instead be available through the Microsoft Graph security runHuntingQuery API. -
General Availability of Power BI developer mode
MC1465770 · stayInformed · normal · Updated 09/01/2026 22:22
Services: Power BI
Read message
[What and Why:] We are announcing the General Availability (GA) of developer mode and the Power BI Project (PBIP) file format in Power BI Desktop. PBIP is the code-based format for Power BI development and includes: Power BI Report (PBIR) for report definitions Tabular Model Definition Language (TMDL) for semantic models This update expands support for source control, CI/CD workflows, and programmatic development scenarios outside of Power BI authoring tools. As part of GA, PBIR becomes the default report format across Power BI Desktop and the Power BI service. PBIR-Legacy remains supported; however, reports edited in Power BI tools will automatically be upgraded to PBIR. Note: PBIR is not replacing PBIX. PBIX remains the primary file format for Power BI developers. Internally, PBIX files will now store report metadata using PBIR instead of PBIR-Legacy. For more information, see: Power BI Desktop projects (PBIP) - Power BI | Microsoft Learn. [Rollout Schedule:] Worldwide, GCC, GCC High, DoD: Mid-September 2026 through late September 2026 Who is affected Power BI developers using the PBIP file format Organizations leveraging source control, DevOps, or CI/CD processes for Power BI development Power BI Desktop and Power BI service environments Platforms/Services Power BI Desktop Power BI service Power BI Project (PBIP) Power BI Report (PBIR) What will happen PBIR becomes the default report format for Power BI reports. Reports currently using PBIR-Legacy will automatically convert to PBIR when edited in Power BI tools. Existing PBIX workflows remain supported and unchanged. Report functionality and end-user experiences are unaffected. Report consumers will not see any changes to report behavior or functionality. The tenant setting "Automatically convert and store reports using Power BI enhanced metadata format (PBIR)" will be removed because PBIR will no longer be an opt-in experience. [Action Required / Recommendations:] No action is required. We recommend that Power BI administrators: Review internal documentation that references PBIR-Legacy or report metadata formats. Update governance, development, and CI/CD guidance to reflect PBIR as the default format. Communicate this change to Power BI developers and development teams as appropriate. Additional Information For more information, review the Power BI Desktop projects (PBIP) documentation on Microsoft Learn. -
Teams web client users will be redirected to teams.cloud.microsoft
MC1465764 · planForChange · normal · Updated 09/01/2026 22:16
Services: Microsoft Teams
Read message
[What and why:] Microsoft is continuing the transition of Microsoft 365 experiences to cloud.microsoft, a unified, trusted, and dedicated domain for Microsoft first-party authenticated products and services. As part of this transition, Microsoft Teams web client users in your organization will be automatically redirected from teams.microsoft.com to teams.cloud.microsoft. This is a domain change only. Teams features and functionality are not changing, and no action is required from end users. Existing links and bookmarks that use teams.microsoft.com will continue to be supported. The rollout that started per previous communication (MC116227) will continue in controlled stages through September 2026. By the end of September 2026, Microsoft plans to complete the redirect for the remaining tenants and remove the remaining rollout exception list. We continue to monitor signals across both domains to ensure continued reliability and performance. Target timing Customer-facing milestone By September 30, 2026 Redirect all enterprise tenants – exception possible via admin control Beginning January 1, 2027 Temporary tenant admin control is retired and the redirect can no longer be disabled [Rollout schedule:] Rollout will continue in controlled stages through September 2026, with plans to complete the redirect for the remaining tenants and remove the remaining rollout exception list by the end of September. [Impact on your organization:] How this will affect your organization Users who open teams.microsoft.com will be redirected automatically to teams.cloud.microsoft. Existing links and bookmarks remain supported and redirect appropriately. Teams consumer experiences at teams.live.com are not affected by this change. Users may notice that the new address ends in .microsoft rather than .com. This is expected; .microsoft is a top-level domain operated exclusively by Microsoft. Organizations following standard Microsoft 365 network guidance should generally experience no impact. Some Teams web apps may not render or launch correctly if they use an older Teams JavaScript SDK or restrictive domain, X-Frame-Options, Content Security Policy (CSP), authentication, or redirect settings. The Teams desktop client can be used if an app has a web-specific domain compatibility issue. Temporary tenant admin control - Available through December 31, 2026 If your organization needs additional time to address an application compatibility issue, a Teams tenant administrator can temporarily disable the automatic OCDI redirect. When disabled, users will continue to be directed to teams.microsoft.com. This control is intended as a time-limited troubleshooting mechanism and will be retired after December 31, 2026. Beginning January 1, 2027, the redirect to teams.cloud.microsoft can no longer be disabled. Before using the control, identify the affected app and work with the app owner to update its domain configuration. Disabling the redirect should be temporary and should not replace the required application remediation [Action required / Recommendations:] Ensure that connections to *.cloud.microsoft are not blocked by client devices, proxies, firewalls, secure web gateways, or other enterprise network controls. Update internal documentation and user education that explicitly references teams.microsoft.com. Existing links remain compatible, but updated material can reduce confusion. Inform help-desk/support that teams.cloud.microsoft is an expected Microsoft domain. If you use the temporary tenant admin control, complete the required app remediation and re-enable the redirect before December 31, 2026. Application owners should validate the complete application experience under teams.cloud.microsoft. If an issue occurs, capture the tenant ID, affected app and app ID, user impact, timestamp, browser, affected URL, reproduction steps, and relevant network or browser-console details. If the issue is specific to the Teams web domain, users can use the Teams desktop client while the application owner completes the required update. Contact Microsoft Support if you require assistance. Developer readiness guidance: https://aka.ms/teams-newdomain-blog-devs The cloud.microsoft domain has been part of standard Microsoft network guidance for Microsoft 365 domains and service endpoints since April 2023. -
(Updated) Classic Outlook for Windows: User-initiated insights with Copilot
MC1311978 · planForChange · normal · Updated 09/01/2026 21:43
Services: Microsoft 365 Copilot Chat
Read message
Updated September 1, 2026: We have updated the timeline. Thank you for your patience. [Introduction] We're introducing User Initiated Insights in Copilot for classic Outlook for Windows, enabling users to manually select text within an email and prompt Copilot to provide contextual insights. This enhancement gives users greater control over when and how Copilot assists them, improving productivity, clarity, and decision-making directly within their workflow. This message is associated with Roadmap ID 508524. [When this will happen:] Public Preview (Worldwide): We began rolling out in early May 2026 and expect to complete by late May 2026. General Availability (Worldwide): We will begin rolling out in early October 2026 (previously early September) and expect to complete by end of October 2026 (previously end of September). [How this affects your organization:] Who is affected: Users with Microsoft 365 Copilot capabilities Organizations using classic Outlook for Windows What will happen: Users will be able to highlight text in emails and invoke Copilot to generate insights. Screenshot: When text is highlighted in an email, an Explain This button appears to provide additional context: Functionality is built into the Outlook experience and does not require a separate add-in. The feature will be on by default for eligible users. Existing Microsoft 365 security, compliance, and data protection policies continue to apply. [What you can do to prepare:] If you do not want users to access this feature, remove or restrict Copilot capabilities. Verify users are running the latest version of classic Outlook for Windows. Inform helpdesk and support staff about this new Copilot interaction model. Communicate to users how to select text and invoke Copilot for contextual insights. Learn more: How do I enable or disable Microsoft Copilot on MS 365 Premium | Microsoft Learn Instructions to turn off Copilot | Microsoft Support [Compliance considerations:] Compliance areaExplanation Introduces AI/ML capabilities interacting with customer data.The feature enables Copilot to process user-selected email content to generate insights. Provides a new way for users to interact with generative AI.Users can invoke Copilot directly by selecting text within emails. Allows users to enable or disable the feature at use time.Users control invocation by choosing when to select text and engage Copilot. -
More control for Windows Autopatch updates: quality updates, .NET Framework, and quick machine recovery
MC1465692 · stayInformed · normal · Updated 09/01/2026 18:01
Services: Windows
Read message
What and why: Windows Autopatch is expanding to provide a streamlined experience for managing Windows quality updates, supported .NET Framework updates, and quick machine recovery updates. These capabilities give you more control over update approvals and rollout timing, along with device-level reporting to monitor approved releases, deployments, and remediation status. Rollout schedule: Rollout begins September 1, 2026, and is expected to reach all tenants by October 15, 2026. Impact on your organization: With this change, you can use Windows Autopatch quality update policies to manage approvals for Windows OS quality updates, supported .NET Framework updates, and quick machine recovery updates. The updated experience includes the following capabilities: Configure automatic or manual approval by update type for monthly security updates, monthly non-security preview updates, out-of-band security updates, and out-of-band non-security updates. Approval settings for each category apply to both Windows OS quality updates and supported .NET Framework releases. Use automatic approvals with a configured deferral period to support gradual deployments or require manual review before an update is offered. Windows Autopatch recommends automatic approval for security updates and manual approval for optional updates. Configure quick machine recovery approval and deferral settings in the same quality update policy. Quick machine recovery helps restore applicable Windows devices that become unbootable after a critical large-scale issue. You can automatically approve fixes or review and approve them manually. Review, approve, and pause individual Windows quality updates, supported .NET Framework, and quick machine recovery updates from the Manage quality updates experience. Pausing a release prevents new devices from receiving it but does not roll back devices that have already installed it. Use the quality update status report for a per-device view, target compliance, target and installed updates, assigned policies, readiness, alerts, and hotpatch update information. Use the new quick machine recovery update status report to view affected devices, remediation status, applicable fix version, release date, assigned quality update policy, and OS version. Action required/recommendations: Learn more about these new capabilities in the Microsoft Intune admin center and review your current update management processes. Windows quality updates overview Quality update status report Quick machine recovery updates Quick machine recovery update status report Determine which update types you desire to approve automatically or manually. Then plan a gradual rollout cadence for your tenant using approval settings and appropriate deferral periods. -
Expanding memory integrity protection across Windows devices
MC1465669 · stayInformed · normal · Updated 09/01/2026 17:20
Services: Windows
Read message
What and why Beginning in October 2026, Windows quality updates will start enabling memory integrity on more eligible Windows devices. On some devices, this change will also enable virtualization-based security (VBS). Memory integrity helps protect critical parts of Windows from tampering by allowing only trusted kernel-mode code and drivers to run. Before enabling the protection, Windows evaluates device readiness based on hardware capabilities, compatibility, performance considerations, Windows 11 system requirements, and recommended built-in protections. Rollout schedule The gradual rollout begins in October 2026. It might not reach all eligible devices at the same time. Impact on your organization Eligible devices might have memory integrity, and in some cases VBS enabled, automatically through Windows quality updates. Existing administrator and user choices and policies remain in effect. This rollout won't automatically change devices on which you explicitly disable memory integrity. Action required/recommendations Organizations should: • Review existing memory integrity and VBS policies and device configurations. • Review Expanding memory integrity protection across Windows devices for information about the rollout. • See Enable memory integrity for configuration and management guidance. Compliance considerations No compliance considerations are identified. Review as appropriate for your organization. -
(Updated) Microsoft 365 Copilot: Updates to memory and personalization
MC1158329 · stayInformed · normal · Updated 09/01/2026 16:52
Services: Microsoft 365 Copilot Chat
Read message
Updated September 1, 2026: We have updated the timeline. Thank you for your patience. [Introduction:] We’re updating Memory in Microsoft 365 Copilot to improve personalization and enhance the user experience. With this update, Copilot will personalize responses using chat history, helping users receive more relevant and contextual replies. We’re also introducing refreshed user controls in Copilot settings to make it easier to view and manage Saved Memory. This will be available to all Copilot Chat users. Control over personalization using chat history is also available, with details for users via the settings screen. [When this will happen:] Public Preview (Frontier): Begins rolling out mid-November 2025. General Availability: Begins mid-September 2026 (previously early January) and is expected to complete by late October 2026 (previously late July). [How this affects your organization:] All users of Microsoft 365 Copilot in tenants where Memory is enabled. What will happen: Copilot will use chat history to personalize responses, making interactions more tailored and helpful: Users will see a redesigned Memory settings page that improves visibility and control over what Copilot remembers. Existing admin and user-level Memory settings are respected. If Memory is toggled off, it will remain off. No changes to admin controls or policy enforcement. [What you can do to prepare:] Review the updated Memory settings experience with your users once available. No admin action is required unless you wish to update internal documentation or training materials. Learn more: Enhanced personalization control overview | Microsoft Graph | Microsoft Learn enhancedPersonalizationSetting resource type | Microsoft Graph | Microsoft Learn [Compliance considerations:] Does the change alter how existing customer data is processed, stored, or accessed (e.g. documents, emails, chats, etc.)?Yes. Copilot will now use chat history to personalize responses, which changes how existing customer data is processed to generate contextual replies. Does the change introduce or significantly modify AI/ML or agent capabilities that interact with or provide access to customer data?Yes. This update enhances Copilot’s personalization model by incorporating chat history, allowing it to generate more tailored responses. Does the change provide end users any new way of interacting with generative AI?Yes. Users will receive more personalized and contextual responses from Copilot based on their prior chat interactions. Does the change allow a user to enable and disable the feature themselves?Yes. Users can manage what Copilot remembers through the updated Memory settings page in Copilot settings. -
(Updated) Microsoft Teams: Private chat for organizers and presenters in structured meetings, webinars, and town halls
MC1188222 · planForChange · normal · Updated 09/01/2026 16:39
Services: Microsoft Teams
Read message
Updated September 1, 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-October 2026 (previously late September) and is expected to complete by late October 2026 (previously late August). General Availability (Worldwide and GCC): Rollout begins in late October 2026 (previously mid-September) and is expected to complete by late November 2026 (previously early November). [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. -
Reminder: Configure firewall and proxies for smooth Windows updates
MC1465017 · stayInformed · normal · Updated 08/31/2026 17:10
Services: Windows
Read message
What and why By design, Windows Update doesn't trust servers that don't have TLS certificates issued by an actual Windows Update trust anchor. We published guidance in May 2026 to help you diagnose and fix connection issues that result from this design. Rollout schedule This guidance was published in May to help with ongoing troubleshooting. Connection issues might be ongoing until you apply the existing solution. Impact on your organization Your firewalls and proxies might block access to the trustworthy and necessary Windows Update service if your configuration is either intercepting TLS connections or isn't passing TLS requests through for the necessary DNS subdomains. The published guide helps you diagnose and fix related issues. Action required/recommendations Diagnose connection issues by checking the Windows Update audit log. Our detailed guidance lists the recommended PowerShell command and four error codes that can confirm the issue. To remedy the situation, trust all the DNS hosts and subdomains related to wildcard FQDN for the connection to work properly. For example, a recommended DNS host name *.update.microsoft.com represents all the following hosts and subdomains: update.microsoft.com sls.update.microsoft.com tas02.sls.update.microsoft.com Update your proxy and firewall configurations if any of these subdomains are missing. If your devices connect to an IT-managed Windows Server Update Services (WSUS) server, these exceptions aren't necessary. Compliance considerations Devices that cannot reach the Windows Update service will stop receiving security updates. Additional information Configuring firewall and proxies for smooth Windows updates Windows Update security Transport Layer Security protocol Connection endpoints for Windows 11 Enterprise Scan changes and certificates add security for Windows devices using WSUS for updates -
Upcoming changes to classic publishing sites, classic user-created pages and custom scripting in SharePoint Online
MC1464926 · planForChange · normal · Updated 08/31/2026 15:49
Services: SharePoint Online
Read message
[What and why:] Microsoft SharePoint continues to evolve to help organizations create and manage content more securely, easily, and intelligently. As part of this evolution, we’re introducing upcoming changes to classic publishing sites, classic user-created pages, and custom scripting in SharePoint Online, with a two-phase rollout designed to give organizations time to assess usage, plan modernization, and move to modern SharePoint experiences. Beginning March 1, 2027, classic publishing site creation and publishing feature activation will be disabled for all existing tenants. For new tenants created on or after that date, no new classic pages can be created by default; adding or updating custom scripts and related changes will be disabled. Beginning October 1, 2028, all existing classic user-created pages will be set to read-only and custom scripting enforcement will extend to all tenants. Affected classic user-created page types include wiki pages, web part pages, blog pages, publishing pages, and custom ASPX pages created using SharePoint Designer or third-party solutions. None of these changes affect classic page content; existing pages will remain accessible for viewing. [Rollout schedule:] Worldwide: We will begin rolling out early March 2027 and expect to complete by early April 2027. GCC: We will begin rolling out early May 2026 and expect to complete by late May 2027. GCC High: We will begin rolling out early May 2027 and expect to complete by late May 2027. DoD: We will begin rolling out mid-June 2027 and expect to complete by early July 2027. [Impact on your organization:] 1. Creation of new classic publishing sites, and activation of the classic publishing feature, will be turned off for site collections and subsites. Below is the list of affected site templates, and classic templates aren't affected. Site template ID Site template BLANKINTERNETCONTAINER#0 Publishing Portal Site CMSPUBLISHING#0 Publishing Site BLANKINTERNET#0 Publishing Site Blank ENTERWIKI#0 Enterprise Wiki SRCHCEN#0 Enterprise Search Center SPSSITES#0 Site Directory SPSNHOME#0 News Home Site PRODUCTCATALOG#0 Product Catalog SPSREPORTCENTER#0 Report Center SPSTOPIC#0 Topic Area Template 2. Classic user-created pages — wiki pages, web part pages, blog pages, publishing pages, and custom ASPX pages — will become read-only. For existing tenants, users can still open and view these pages, but can no longer create or edit them. 3. The ability to add or update custom scripts and related settings will be disabled. Existing scripts will continue to function. [Action required / Recommendations:] Discover and assess your classic environment Identify usage of classic sites and pages across your tenant. Use the Standard Purview Audit log category (SharePoint Classic Activities) and events (ClassicPageCreated, ClassicPageEdited, and ClassicPageViewed) to identify active classic page usage, and leverage the Microsoft 365 Assessment Tool to understand the overall classic scope and modernization feasibility. Prioritize based on business importance and usage If your assessment finds no classic content, none of these changes apply to you — no action needed. Otherwise, focus first on high-value or frequently updated classic sites and pages, and identify where modernization will have the greatest impact. Classifying content by business criticality can help guide a phased migration plan. Transform to modern SharePoint experiences Use modernization tools such as SharePoint PnP Modernization and SharePoint PnP Page Modernization Agent to convert classic pages where applicable. Microsoft will continue enhancing the tooling to accelerate page modernization with best-effort fidelity reservation, but it may not fully automate complex scenarios; modernization is a project that typically requires planning, resourcing, and highly customized pages often need redesign or manual rebuilding. Adopt a phased migration strategy Combine centralized IT-led planning and prioritization with distributed execution by site owners over time. Most organizations find success by modernizing in waves rather than attempting a single large-scale migration. [Learn more:] Deprecation of Classic SharePoint Online Pages | Microsoft Learn Modernize your classic SharePoint sites | Microsoft Learn Transform classic pages to modern pages | Microsoft Learn Microsoft 365 Assessment Tool SharePoint Page Modernization Agent -
External messaging limits for onmicrosoft.com-only organizations in Microsoft Teams
MC1463510 · planForChange · normal · Updated 08/28/2026 21:41
Services: Microsoft Teams
Read message
[What and Why:] To help protect Microsoft Teams users from spam, phishing, and other abusive activity, Microsoft is introducing outbound external messaging limits for organizations that use only the default Microsoft Online Email Routing Address (MOERA) domain, such as contoso.onmicrosoft.com. These limits are designed to reduce large-scale abuse while preserving normal collaboration scenarios. Most organizations using Teams for standard business communications are not expected to reach these limits. [Rollout Schedule:] General Availability (Worldwide): Rollout begins in mid-September 2026 and is expected to complete by mid-September 2026. [Impact on Your Organization:] Who is affected Organizations that use only the default onmicrosoft.com domain and have not configured a custom domain. Platforms/Services Microsoft Teams External chat and messaging What will happen Outbound Teams messages sent to external users will be subject to messaging limits intended to reduce abusive or high-volume activity. When an applicable limit is reached, users may be temporarily unable to send messages to external users. Users will see an in-product notification indicating that outbound external messaging has been temporarily limited. Internal Teams messaging and collaboration within your organization will not be affected. External messaging capabilities will automatically resume when activity falls below the applicable threshold. The protection is enabled by default and does not require administrator configuration. An optional administrator alert for throttling events will become available after the initial rollout. This post will be updated when information about enabling the alert is available. [Action Required / Recommendations:] If your organization relies on the default onmicrosoft.com domain for production use, review your domain configuration before rollout. Verify whether your organization uses only the default onmicrosoft.com domain. If appropriate, add and configure a custom domain for your Microsoft 365 organization. Inform help desk personnel and Teams administrators that users may encounter temporary outbound external messaging restrictions if applicable limits are reached. Review the Teams limits and specifications documentation for additional guidance. No action is required for organizations that already have a custom domain configured. Additional Information This change helps reduce spam and other abusive activity originating from tenants that use only the default onmicrosoft.com domain while maintaining normal collaboration experiences for legitimate users. -
Organization skills support in Copilot for PowerPoint (Frontier release)
MC1463509 · stayInformed · normal · Updated 08/28/2026 21:40
Services: Microsoft 365 apps
Read message
[What and why:] Microsoft is introducing organizational skills support for Copilot in PowerPoint. These reusable skills can help users apply organization-specific guidance when working with Copilot in PowerPoint for the web, PowerPoint desktop for Windows, and PowerPoint for Mac. Tenant admins will be able to add and share organizational skills through the Microsoft 365 admin center. [Rollout schedule:] Frontier: We will begin rolling out in end of August 2026 and expect to complete by early September 2026. [Impact on your organization:] Who is affected: M365 admins and eligible users of Copilot in PowerPoint. Platforms: PowerPoint for the web PowerPoint desktop for Windows PowerPoint for Mac After this rollout: Tenant admins will be able to add and share organizational skills for Copilot in PowerPoint. Shared skills will provide users with reusable, organization-specific guidance when they use Copilot in supported PowerPoint experiences. Tenant admins will manage these skills through the Microsoft 365 admin center. Users will be able to access shared organizational skills in PowerPoint for the web, PowerPoint desktop for Windows, and PowerPoint for Mac. [Action Required / Recommendations:] No action is required before the rollout. If your organization plans to use shared organizational skills: Identify the tenant admins who will manage the skills. Determine which organizational skills should be available to PowerPoint users. Establish an internal process for creating, reviewing, approving, publishing, and maintaining shared skills. Update your internal user guidance and support materials for Copilot in PowerPoint as appropriate. Ensure eligible users have access to supported PowerPoint experiences and meet the applicable Microsoft 365 Copilot requirements. Review Deploy Organization skills for Copilot in PowerPoint -
(Updated) Microsoft Outlook for iOS and Android: Insert signature images from OneDrive
MC1437668 · stayInformed · normal · Updated 08/28/2026 16:36
Services: Exchange Online
Read message
Updated August 28, 2026: We have updated the timeline. Thank you for your patience. [What and why] Microsoft is enhancing the signature editing experience in Outlook for iOS and Android by allowing users to insert images into email signatures directly from OneDrive, in addition to selecting images from their device photo library. This improvement makes it easier for users to access and use signature images stored in OneDrive while maintaining existing organizational data-sharing policies. [Rollout schedule] General Availability (Worldwide, GCC, GCC High, and DoD): Beginning in late September 2026 (previously late August) and expected to complete by late October 2026 (previously late September) [Impact on your organization] Who is affected Users of Outlook for iOS and Android who create or edit email signatures Platforms and services Outlook for iOS Outlook for Android What will happen Users will see a new option when inserting an image into an email signature: Selecting Insert image in the signature editor will present:Choose from files to browse and select image files that are stored in OneDrive. Choose from photo library to select an image from the device, which remains the existing behavior. This change is only visible in Outlook for iOS and Android when editing email signatures. Users can select images stored in OneDrive, but there are no changes to the OneDrive application experience. Available OneDrive accounts are determined by your organization's existing cross-account data-sharing policies. The file picker displays only image files. Users can switch between grid and list views while browsing images. Selected images are downloaded and embedded into the signature, consistent with the current behavior for locally stored images. Existing signatures are not modified. The feature is enabled by default and does not require administrator configuration. [Action required and recommendations] No action is required. The update is enabled automatically. We recommend that you: Inform helpdesk and support staff about the updated signature image selection experience. Update internal training materials or screenshots if they reference the signature editor workflow. [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
(Updated) Improved OneDrive experience in Apple Files app
MC1458481 · stayInformed · normal · Updated 08/28/2026 16:31
Services: Microsoft OneDrive
Read message
Updated August 28, 2026: We have updated the timeline. Thank you for your patience. [What and Why:] We're improving the OneDrive integration with the Apple Files app on iOS to provide a more reliable file experience, including clearer upload status and progress indicators. As part of this update, OneDrive Shared and SharePoint Libraries locations that users can access only with read-only permissions will no longer appear in the Apple Files app. Users will continue to have access to this content through the OneDrive mobile app. Users who want to access shared content and libraries in the Apple Files app can use Add to OneDrive. Content added to OneDrive will continue to appear in the Apple Files app and can be edited when users have the appropriate permissions. [Rollout Schedule:] General Availability (Worldwide): Rollout will begin in mid-August 2026 and is expected to complete by early November 2026 (previously mid-September). [Impact on Your Organization:] Who is affected Users who access OneDrive shared content or SharePoint libraries through the Apple Files app on iOS devices. Platforms and Services OneDrive for iOS Apple Files app on iOS SharePoint Online libraries What will happen Read-only shared locations and library locations will no longer appear in the Apple Files app. Users will continue to be able to access this content in the OneDrive mobile app. Users can use Add to OneDrive to continue accessing shared content and libraries from the Apple Files app. Content added to OneDrive will remain available through the Apple Files app. Users with the required permissions will continue to be able to edit content added to OneDrive. [Action Required / Recommendations:] No admin action is required. We recommend informing users who access shared content or SharePoint libraries through the Apple Files app on iOS that: Read-only shared and library locations will no longer appear in the Apple Files app after this rollout. They can continue accessing this content through the OneDrive mobile app. They can use Add to OneDrive if they want content to appear in the Apple Files app. [Compliance Considerations:] No compliance considerations identified, review as appropriate for your organization. -
Badges on profile cards in Teams
MC1462467 · stayInformed · normal · Updated 08/28/2026 16:22
Services: Microsoft Teams
Read message
[What and why:] We are updating profile cards in Microsoft Teams to display existing Awards and Certifications profile properties from the Microsoft 365 profile schema. This feature previously rolled out to Outlook and the Microsoft 365 Copilot app in April 2026 and will now be available in Teams profile cards. [Rollout schedule:] Targeted Release (Worldwide): Rollout begins in early October 2026 and is expected to complete by early October 2026. General Availability (Worldwide): Rollout begins in early-October 2026 and is expected to complete by mid-October 2026. [Impact on your organization:] Who is affected: All users in organizations that populate the Awards and Certifications properties in Microsoft 365 profiles. What will happen: A new Awards and Certifications section will be added to profile cards in Teams in the Overview and Contact tabs, below the Skills section. Each award or certification entry will display the title and issuer by default. Selecting a badge will reveal additional details, including the description and award date. If your organization does not currently populate these profile properties, no changes will be visible and the new section will not appear on profile cards. Platforms and services: Microsoft Teams Microsoft Outlook Microsoft 365 Copilot app Microsoft 365 profile cards [Action required / Recommendations:] Review your organization's Microsoft 365 profile data and determine whether the Awards and Certifications properties are populated for users. Values stored in these fields will become visible on profile cards in Teams, Outlook, and the Microsoft 365 Copilot app. If your organization already uses the Awards and Certifications fields in the Microsoft 365 profile schema, no action is required. Note that the profile card experience is read-only. Users cannot create, edit, or manage awards and certifications directly from the profile card. Review the support documentation: View awards and certification badges on your profile card. [Compliance considerations:] No compliance considerations identified, review as appropriate for your organization. -
Outlook for iOS: Minimum system requirements updated to iOS 26 and above
MC1462923 · planForChange · normal · Updated 08/27/2026 22:18
Services: Exchange Online
Read message
[What and Why:] To help ensure optimal performance, reliability, and security, Outlook for iOS is updating its minimum supported operating system requirements. Following the release of iOS 27, Outlook for iOS will support only the two most recent versions of iOS, iPadOS, and watchOS. This change aligns with Microsoft’s commitment to supporting the latest Apple platforms. [Rollout schedule:] Worldwide, GCC, GCC High, DoD: We will begin rolling out in mid-September 2026 and expect to complete by late September 2026. [Impact on your organization:] Who is affected Users accessing Outlook on iPhone, iPad, or Apple Watch devices running operating system versions that will no longer be supported. Platforms and services Outlook for iOS iOS iPadOS watchOS What will happen After iOS 27 becomes generally available: Outlook for iOS will no longer receive updates on devices running iOS 18 or earlier. Users on iOS 18 can continue using the last supported version of Outlook. However, over time, the app may stop syncing email and calendar data. Support for iPadOS 18 and watchOS 11 will also end. Supported versions will include iOS 26 and iOS 27, iPadOS 26 and iPadOS 27, and watchOS 26 and watchOS 27. This change does not affect users running iOS 26 or later. [Action required / Recommendations:] Review your mobile device inventory and identify devices running operating system versions that will no longer be supported. Notify affected users of the upcoming operating system requirement changes. Encourage users to upgrade eligible devices to iOS 26 or later before the rollout begins. This will help users continue receiving Outlook updates and avoid potential service interruptions. Review options for devices that cannot be upgraded to a supported operating system version. Update your internal support documentation and user communications as appropriate. No Microsoft 365 admin configuration changes are required for this update. -
Admin app retiring in Teams, Outlook and Microsoft365.com
MC1462922 · planForChange · normal · Updated 08/27/2026 22:17
Services: Exchange Online, Microsoft 365 suite, Microsoft Teams
Read message
[What and why:] The Admin app is an application built to help very small businesses manage administrative tasks directly in Teams, Outlook and Microsoft365.com. Starting in October 2026, the Admin app will no longer be supported or available. [Rollout schedule:] We will begin rolling out mid-August 2026 and expect to complete by mid-October 2026. [Impact on your organization:] Who is affected? Admins using the Admin app in Teams, Outlook or Microsoft365.com What will happen? Starting in August 2026 the Admin app will no longer be pre-pinned or pre-installed in Teams for new very small business admins. Admins will still be able to access the application if it is installed in Teams. Starting in October 2026 the Admin app will no longer be supported or available to customers in Teams, Outlook, or Microsoft365.com. [Required Action / Recommendations:] Admins can continue to use Microsoft Admin Center and Teams Admin Center to manage their Teams environments. Admins can also use the Microsoft 365 Admin Agent to assist them with administrative tasks -
The September 2026 Windows security update requires a restart for hotpatch‑enabled devices
MC1461574 · stayInformed · normal · Updated 08/27/2026 22:05
Services: Windows
Read message
What and why The September 2026 Windows security update will be released as a standard update rather than a hotpatch update. Some of the security improvements in this update change components that cannot be updated without a restart. As a result, devices enrolled in hotpatching will need to restart to complete installation. Rollout schedule September 2026: Standard update with restart required for all devices including those that are hotpatch-enabled. October 2026: Planned baseline update month with restart required. November 2026: Next hotpatch update expected. Impact on your organization Hotpatch-enabled devices will require a restart to complete installation of the September 2026 security update. Hotpatch-enabled devices will remain enrolled in hotpatch updates. No change for devices not using hotpatch updates (standard updates already require restart). Action required / recommendations No additional configuration is required to stay enrolled in hotpatch updates. Compliance considerations No compliance action is required. Update installation and restart behavior will be reflected in update history and compliance reports as usual. Additional information You can track the hotpatch update calendars on the Windows release health site for both Windows 11 and Windows Server. -
Prepare for the removal of WMIC from Windows 11
MC1462813 · stayInformed · normal · Updated 08/27/2026 17:25
Services: Windows
Read message
What and why: The Windows Management Instrumentation command-line (WMIC) utility has been removed from Windows 11, version 24H2 and later. It’s no longer available as a Feature on Demand on these versions. WMI itself remains supported and unaffected. Rollout schedule: 2016: WMIC utility was deprecated in Windows Server 2012. 2021: WMIC utility was deprecated in Windows 10, version 21H2. 2022: WMIC utility was available in Windows 11, version 22H2 as a Feature on Demand (FoD), which was preinstalled and enabled by default. 2024: WMIC utility was disabled by default in Windows 11, versions 23H2 and 24H2. It was still available as a Feature on Demand (FoD). 2025: WMIC utility was removed, if already installed, when upgrading to Windows 11, version 25H2. However, you could previously add it back as a Feature on Demand (FoD). 2026: The WMIC utility has been removed from Windows 11. The removal is reflected in Windows Insider Preview builds and is part of the August 2026 preview update for Windows 11, versions 24H2 and 25H2. WMIC is also removed from Windows 11, version 26H1. It is no longer available as a Feature on Demand (FoD). Impact on your organization: Organizations with automated deployment or monitoring systems that rely on WMIC should validate and update their tooling to avoid disruptions. Action required/recommendations: Organizations should identify applications, scripts, deployment tools, and monitoring systems that use WMIC and migrate them to PowerShell or supported WMI programming interfaces. Learn more at Windows Management Instrumentation command-line (WMIC) removal from Windows. Compliance considerations: No compliance considerations are identified. Review as appropriate for your organization. -
The August 2026 Windows non-security preview update is now available
MC1462812 · stayInformed · normal · Updated 08/27/2026 17:25
Services: Windows
Read message
The August 2026 non-security preview update is now available for Windows 11, versions 26H1, 25H2, and 24H2. Information about the contents of this update is available in the release notes, which are accessible from the Windows 11 update history page. To learn more about the different types of monthly quality updates, see Understanding Windows monthly updates. Looking to explore upcoming features and improvements in Windows 11? Check the Windows roadmap. It includes what’s coming to the Windows Insider Program, what's gradually rolling out, and what's generally available. Highlights for the Windows 11, version 25H2 update: You can now choose whether the taskbar appears at the bottom, top, left, or right side of your screen, with tooltips, flyouts, and most customization settings, such as never combining taskbar icons, working in every position. A new smaller taskbar option reduces the size of taskbar icons and taskbar height to maximize screen space on smaller devices, while keeping quick access to Start, Search, and the system tray. The Start menu is now more personal, letting you choose a small or large menu size, independently show or hide the Pinned, Recommended, and All sections, and hide your name and profile picture. Windows Search now makes results easier to scan by showing where each result comes from—app, setting, file, web, or Store—and can automatically index your most used folders so those files show up in your searches. Launching File Explorer Home is now faster and more responsive, and the Recommended section supports touch scrolling for easier browsing. Administrator protection helps reduce the risk of elevation-of-privilege attacks by using profile separation and just-in-time administrative privileges. It is off by default and can be enabled through Microsoft Intune (OMA-URI) or Group Policy. For instructions on how to install this update, see the KB article for your operating system listed below: Windows 11, version 26H1: KB5120996 Windows 11, versions 25H2 and 24H2: KB5120998 Note: With recent and upcoming Windows updates over the next few months, a limited number of consumer and business devices might experience one additional restart during installation. This one‑time restart occurs after a Secure Boot certificate update is applied as part of the Secure Boot update process. -
(Updated) Microsoft Teams: AI-powered notes for in-person meetings with Facilitator in Teams Rooms on Windows
MC1307512 · stayInformed · normal · Updated 08/27/2026 16:55
Services: Microsoft Teams
Read message
Updated August 27, 2026: We have updated the timeline. Thank you for your patience. [Introduction] To support more effective in-person collaboration, Microsoft Teams is expanding AI-powered meeting notes with the Facilitator agent to Teams Rooms on Windows. This enhancement allows teams meeting in a physical room to capture real-time notes, decisions, and action items—without requiring a scheduled or hybrid meeting. The experience is designed to ensure notes are securely stored in your tenant while no data remains on the room device after the meeting ends. This feature is associated with Microsoft 365 Roadmap ID 560318. [When this will happen] General Availability Worldwide and GCC: We will begin rolling out in late October 2026 (previously early September) and expect to complete by mid-November 2026 (previously late September). [How this affects your organization] Who is affected Organizations using Teams Rooms on Windows Rooms licensed with Teams Rooms Pro What will happen During an in-person meeting, users can start AI-powered notes by selecting the Take notes button on the Teams Rooms console. Notes appear on the front-of-room display or touch board during the meeting: Notes are stored in tenant-owned SharePoint embedded storage. Access to notes requires adding your work account using the Access notes button on the Teams Rooms console: After the meeting, notes can be viewed and edited by participants with access via the meeting recap in the meeting chat on the Teams desktop client.: If no participant was added during the note-taking session via Access notes, notes are deleted automatically. Default state: The feature is available automatically once licensing and prerequisite configurations are met. No additional admin enablement is required beyond existing settings. [What you can do to prepare] No immediate action is required if your organization already meets the prerequisites. To prepare: Confirm Teams Rooms Pro licenses are assigned to applicable rooms. Ensure Facilitator is enabled in your tenant. Verify Loop components are enabled:IsLoopEnabled IsCollabMeetingNotesFluidEnabled Ensure meeting transcription is enabled in Teams meeting policies. Consider notifying helpdesk staff and users about:How to start notes in an in-person meeting Where notes are stored and accessed after the meeting Learn more: Allow Facilitator in the Teams admin center - Set up Facilitator in Microsoft Teams | Microsoft Teams | Microsoft Learn Meetings - Admins- Manage transcription and captions for Teams meetings | Microsoft Teams | Microsoft Learn Settings management for Loop functionality in Teams - Admin policies for Loop components and Loop workspaces | Microsoft 365 | Microsoft Learn [Compliance considerations] QuestionAnswer Does the change store new customer data, and if so, where, and is the data cached or permanently stored?Yes. Meeting notes generated by Facilitator are stored in tenant‑owned SharePoint Embedded storage. No meeting data is stored or cached on the Teams Rooms device after the meeting ends. Does the change alter how existing customer data is processed, stored, or accessed (for example, documents, emails, or chats)?Yes. Meeting audio and transcription data are processed to generate AI‑powered meeting notes, including summaries, decisions, and action items. Access to the notes occurs through the meeting recap in the meeting chat on Teams desktop client. Does the change introduce or significantly modify AI/ML or agent capabilities that interact with or provide access to customer data?Yes. The Facilitator agent uses AI to generate real‑time meeting notes, summaries, decisions, and action items based on in‑person meeting content. Does the change provide users a new way of interacting with generative AI, and if so, how?Yes. Users can initiate AI‑generated meeting notes during an in‑person meeting by selecting “Take notes” on the Teams Rooms console. Does the change include an admin control, and can it be controlled through tenant configuration?Yes. Availability of the feature depends on existing tenant settings, including Teams Rooms Pro licensing, Facilitator enablement, Loop component settings, and meeting transcription policies. -
Microsoft Teams: Clearer text highlighting in dark mode and high contrast mode
MC1462470 · stayInformed · normal · Updated 08/26/2026 22:35
Services: Microsoft Teams
Read message
[What and why:] Microsoft is improving the appearance of highlighted text while users compose messages in dark mode and high contrast mode. This update provides a more consistent and accessible editing experience by improving the visual presentation of highlighted content across supported themes. [Rollout schedule:] Targeted Release (Worldwide): Rollout will begin in mid-September 2026 and is expected to be complete by late September 2026. General Availability (Worldwide, GCC, GCC High, DoD): Rollout will begin in late September 2026 and is expected to be complete by early October 2026. [Impact on your organization:] Who is affected: Users who compose messages using dark mode or high contrast mode. Platforms and services: Microsoft 365 message-composition experiences that support text highlighting. After this update: Highlighted text will display more consistently in dark mode and high contrast mode. Users may notice improved readability and a more uniform editing experience when working with highlighted content. This is a visual enhancement only. It does not change existing text-highlighting functionality or user workflows. [Action required / Recommendations:] No action is required. You may want to inform users about this visual improvement if your organization communicates Microsoft 365 experience updates to end users. [Compliance Considerations:] No compliance considerations identified, review as appropriate for your organization. -
Teams Admin Center - Single pane for monitoring
MC1462463 · planForChange · normal · Updated 08/26/2026 22:30
Services: Microsoft Teams
Read message
[What and Why:] We're excited to introduce an org-wide single pane for monitoring and troubleshooting meetings and calls in the Teams admin center. IT administrators will be able to find all the meetings and calls in one place, get quick insights, and get started with troubleshooting right away. The new experience helps administrators: View in-progress and completed meetings across the organization from a single location. Quickly identify meetings that may require attention. Search for meetings using meeting identifiers and other filters. [Rollout Schedule:] General Availability (Worldwide): Rollout will begin in late September 2026 and is expected to complete by mid October 2026. General Availability (GCC): Rollout will begin in late September 2026 and is expected to complete by mid October 2026. [Impact on Your Organization:] Who is affected Teams administrators responsible for monitoring and troubleshooting meeting and call quality across their organization. Platforms and services Microsoft Teams Teams admin center What will happen After rollout, administrators will see a new Meetings experience in the Teams admin center under Meetings & Calls. Navigate to Teams admin center > Meetings & Calls > Meetings or Calls to access the updated troubleshooting experience. View and monitor meetings across the organization from a centralized Meetings experience. Review both in-progress and completed meetings, search for specific meetings, apply filters, and open meeting details for troubleshooting. Review completed calls across the organization to identify and troubleshoot call quality issues. Available capabilities include: In-progress meetings: View meetings, town halls, and webinars currently occurring in the organization when at least one participant has a Teams Premium license or Teams Rooms Pro license. Completed meetings: View meetings that occurred across the organization during the previous 30 days. Completed calls: Review completed calls across the organization to investigate call quality issues. Issue details: Quickly identify issues experienced by participants and access additional details. Detailed diagnostics: Drill down into telemetry and diagnostic information to support root cause analysis and troubleshooting. Microsoft 365 Copilot for Admins: Use Copilot to investigate individual meetings or analyze trends across the organization. Filtering and search: Refine results using filters such as: Time range (last 7 days, 15 days, 30 days, or a custom date range) Meetings with issues Organizer Meeting type Additional meeting and participant attributes Export: Export meeting and call data for offline analysis, reporting, and investigation. [Action Required / Recommendations:] No action is required. The updated experience will be available automatically after rollout. Once available, administrators can begin using the new capabilities to monitor and troubleshoot meetings and calls across their organization. [Compliance Considerations:] No compliance considerations identified, review as appropriate for your organization. -
Microsoft Entra: Domain update for My Account and identity self-service experiences
MC1462460 · planForChange · normal · Updated 08/26/2026 22:28
Services: Microsoft Entra
Read message
[What and why] We're updating the domain used for Microsoft Entra identity and access management self-service experiences. As part of this change, myaccount.microsoft.com will move to myaccount.cloud.microsoft. Experiences currently hosted on separate domains will also be consolidated under the myaccount.cloud.microsoft domain. The following experiences are included in this update: myaccount.microsoft.com myapps.microsoft.com myaccess.microsoft.com mystaff.microsoft.com This change provides a more consistent and unified access point for identity and access management self-service experiences while supporting ongoing improvements to our service infrastructure. [Rollout schedule] General Availability (Worldwide): Beginning in late November 2026 and expected to complete in late November 2026 [Impact on your organization] Who is affected Users who access Microsoft Entra self-service identity and access management experiences Administrators who manage network, proxy, firewall, or endpoint allowlists Platforms and services Microsoft Entra Web What will happen For users No action is required. Users accessing supported experiences will be automatically redirected to the new domain. Core functionality and existing workflows will remain unchanged. Over time, self-service identity and access management experiences will be available through a unified domain experience. For administrators Most organizations are not expected to require configuration changes. Organizations that manage network, proxy, firewall, or endpoint allowlists should verify that required cloud.microsoft domains are accessible. Failure to allow required domains may result in users being unable to access these experiences after the rollout. [Action required and recommendations] Recommended actions for administrators Before rollout begins: Review network, proxy, firewall, and endpoint policies that restrict access to Microsoft services. Verify that *.cloud.microsoft is included in required allowlists where applicable. Confirm that access to myaccount.cloud.microsoft is not blocked within your environment. Review internal documentation or user guidance that references the existing URLs and update as needed. No action is required for users. Learn more Unified cloud.microsoft domain for Microsoft 365 apps | Microsoft 365 for enterprise | Microsoft 365 | Microsoft Learn [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
Simplified access to Copilot Chat on the Microsoft 365 Copilot mobile app
MC1454386 · planForChange · normal · Updated 08/26/2026 21:42
Services: Microsoft 365 Copilot Chat
Read message
[What and Why:] We’re simplifying access to Copilot Chat in the Microsoft 365 Copilot mobile app (iOS and Android). With this update, two legacy mobile-only controls will no longer restrict Copilot Chat access in the mobile app: the Intune policy "com.microsoft.office.officemobile.BingChatEnterprise.IsAllowed" and Privacy control "Analyze content". This change helps provide a more consistent Copilot Chat experience across mobile, web, and desktop for users who are already allowed to access Copilot Chat. [Rollout Schedule:] General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out on mid-August 2026 and expect to complete by late September 2026. [Impact on your organization:] The following controls will no longer restrict Copilot Chat access in the Microsoft 365 Copilot mobile app: The Intune policy “com.microsoft.office.officemobile.BingChatEnterprise.IsAllowed”. The “Analyze content” privacy control. With this, affected users will regain access to Copilot Chat in the Microsoft 365 Copilot mobile app, consistent with their access on web and desktop apps. This change is on by default. No action is required from users. [Action Required/Recommendations:] No admin action is required for this change. You may want to: Review whether your organization currently relies on the Intune app configuration key com.microsoft.office.officemobile.BingChatEnterprise.IsAllowed or the “Analyze content” privacy control to restrict Copilot Chat on the Microsoft 365 Copilot mobile app. Review the updated Learn article to learn more about these controls. Inform your helpdesk or support teams so they can respond to questions from users who regain access to Copilot Chat on the Microsoft 365 Copilot mobile app. Update internal documentation that references these controls as a way to restrict Copilot Chat access on mobile. If your organization needs to restrict Copilot Chat on the Microsoft 365 Copilot mobile app, review available administrative options, including using Integrated Apps settings to block Copilot across web, desktop, and mobile, or blocking the Microsoft 365 Copilot mobile app to restrict mobile access. Documentation links: Manage Microsoft 365 Copilot Chat | Microsoft Learn -
Microsoft Defender XDR: Unified identity timeline on the Identity page
MC1461705 · planForChange · normal · Updated 08/25/2026 22:22
Services: Microsoft Defender XDR
Read message
[What and Why:] We are enhancing the Timeline tab on the Identity page in Microsoft Defender to provide security teams with a single chronological view of activity and alerts associated with an identity and its linked accounts. This enhancement helps security operations center (SOC) analysts, incident responders, and security administrators investigate identities more efficiently by consolidating relevant events from multiple Microsoft security data sources into one investigation experience. The updated timeline normalizes activity from integrated Microsoft security products, including Microsoft Entra sign-ins, Microsoft Graph audit events, SaaS cloud activity, and device logons. Additional investigation context, filtering capabilities, and event details will help analysts more quickly understand identity-related activity and security risks. [Rollout schedule:] Worldwide, GCC, GCC High, DoD: Rollout begins mid-September 2026 and is expected to complete by mid-October 2026. [Impact on your organization:] This update affects SOC analysts, incident responders, and security administrators who investigate identities in the Microsoft Defender portal. After rollout: The Timeline tab on the Identity page will display a consolidated sequence of activity and alerts for an identity and its linked accounts. Microsoft Entra sign-ins and Microsoft Graph audit events will include relevant risk and Conditional Access information when available. New filtering and investigation fields will be available, including: Source table Session ID Unique token identifier Conditional Access Target Additional information Expanded event context will help analysts investigate identity-related activity without pivoting across multiple data sources. The timeline will automatically refresh when linked accounts change. This update does not modify existing security policies, user accounts, permissions, or configurations. [Action required / Recommendations:] No action is required to enable the core timeline experience. To help your organization take advantage of this enhancement, we recommend that you: Inform SOC and incident response teams about the updated Timeline experience. Review investigation runbooks that require analysts to pivot between multiple Advanced Hunting tables. If you use supported SaaS cloud accounts, enable Identity inventory integration in Microsoft Defender for Cloud Apps by navigating to Settings > Cloud Apps. Confirm that analysts have the appropriate permissions to access identity investigation data in the Microsoft Defender portal. Learn more Investigate an identity Enable Identity inventory integration -
Microsoft Defender XDR: Unified response actions across identity accounts
MC1461704 · planForChange · normal · Updated 08/25/2026 22:21
Services: Microsoft Defender XDR
Read message
[What and why:] Microsoft Defender XDR is expanding identity response actions into a unified experience across linked accounts. Security teams will be able to apply supported response actions to all supported accounts associated with an identity, or to selected accounts, from a single workflow. Available actions depend on the identity system or connector managing the account and may include: Disable account Enable account Revoke session Mark as compromised Force password change Supported identity systems and applications include: Active Directory Microsoft Entra ID Okta CyberArk Identity SailPoint Identity Security Cloud Google Workspace Salesforce Box This enhancement helps security operations teams respond more quickly and consistently to compromised identities across connected identity providers and SaaS applications. [Rollout schedule:] Worldwide, GCC, GCC High, DoD: Rollout begins mid-October 2026 and is expected to complete by mid-October 2026. Who is affected Security Operations Center (SOC) analysts Incident responders Identity administrators Administrators managing Microsoft Defender-connected identity systems Platforms and services Microsoft Defender XDR Microsoft Defender for Identity Microsoft Defender for Cloud Apps Microsoft Entra ID Supported third-party identity provider and SaaS application connectors What will happen Authorized analysts can initiate supported response actions from the Identity page, Identity side panel, Advanced Hunting, or Action center. Available response actions vary based on the identity system or connector managing each account. Administrators can review action status in Action center and in audit records generated by the target system. No account changes occur unless an authorized analyst initiates a response action or Microsoft Defender Automatic Attack Disruption applies a supported automated response action. [Action required / Recommendations:] No action is required to enable this capability. However, we recommend that administrators: Review and assign the required Microsoft Defender Unified RBAC permissions and Microsoft Entra roles. Verify Microsoft Defender for Identity action account configuration for Active Directory response actions. If using Microsoft Defender for Identity sensor version 3.x, ensure the sensor is running under the Local System account. Verify that supported identity provider and SaaS application connectors are configured with credentials that allow the intended response actions. Enable Identity Inventory integration in Microsoft Defender for Cloud Apps if SaaS cloud accounts are included in response workflows. Update incident response runbooks and train analysts to verify selected accounts before confirming response actions. Learn more Microsoft Defender for Identity remediation actions Investigate identities and take identity actions in Microsoft Defender XDR Microsoft Defender XDR custom permissions -
(Updated) Microsoft Whiteboard: Retirement of legacy whiteboards and transition to OneDrive-backed whiteboards
MC1441775 · planForChange · normal · Updated 08/25/2026 16:23
Services: Microsoft Teams
Read message
Updated August 25, 2026: We have updated the timeline. Thank you for your patience. Microsoft Whiteboard: Retirement of legacy whiteboards and standalone Whiteboard app Microsoft Whiteboard is completing its transition to OneDrive-backed whiteboards. Enterprise customers must migrate any remaining legacy whiteboards before the migration tooling is retired. After the retirement dates, legacy whiteboards that are not migrated or exported will be permanently deleted and cannot be recovered. Key dates September 25, 2026 Migration tooling for legacy enterprise whiteboards is retired. Users with personal Microsoft accounts can no longer create or edit whiteboards. October 16, 2026 - Legacy whiteboards are permanently deleted. November 30, 2026 - The standalone Microsoft Whiteboard app is deprecated. Impact on your organization This change affects: Enterprise customers with legacy Microsoft Whiteboard content that has not been migrated to OneDrive-backed whiteboards. Users with personal Microsoft accounts who use Microsoft Whiteboard. Organizations that use the standalone Microsoft Whiteboard app. After September 25, 2026: The migration tool for legacy enterprise whiteboards will no longer be available. Remaining legacy whiteboards cannot be migrated. Users with personal Microsoft accounts can no longer create or edit whiteboards. After October 16, 2026: Any remaining legacy whiteboards will be permanently deleted and cannot be recovered. After November 30, 2026: The standalone Microsoft Whiteboard app (Desktop, Mobile) will no longer be supported. Enterprise users will access Microsoft Whiteboard through Microsoft Teams. Action required Migrate all remaining legacy whiteboards to OneDrive-backed whiteboards before September 25, 2026. Verify that required whiteboards have been migrated successfully. Notify affected users of migration and deletion deadlines. Update internal documentation and training materials to direct users to Microsoft Whiteboard in Microsoft Teams. Inform users with personal Microsoft accounts to export any whiteboards they want to retain before October 16, 2026. There will be no recovery or migration option for legacy whiteboards after they are permanently deleted. -
Microsoft 365 Roadmap is becoming the AI at Work Roadmap
MC1461528 · stayInformed · normal · Updated 08/25/2026 15:17
Services: Microsoft 365 suite
Read message
[What and why:] On August 25, 2026, the Microsoft 365 Roadmap will be renamed the AI at Work Roadmap. The AI at Work Roadmap provides a single destination to discover upcoming innovations across Microsoft 365, Copilot, agents, and related AI-powered experiences. Beginning in September 2026, roadmap information for Dynamics 365, Power Platform, and Dataverse will also begin publishing to the AI at Work Roadmap, making it easier to track innovation across Microsoft's business applications, productivity, and AI portfolio. The roadmap continues to support planning and readiness activities by providing visibility into upcoming features and changes. [Rollout Schedule:] August 25, 2026: Microsoft 365 Roadmap is renamed to AI at Work Roadmap September 2026: New Dynamics 365, Power Platform, and Dataverse capabilities begin publishing to the AI at Work Roadmap [Impact on your organization:] Who is affected Microsoft 365 administrators IT professionals Change management teams Technology decision makers who use roadmap information for planning and readiness activities Platforms/Services AI at Work Roadmap (formerly Microsoft 365 Roadmap) What will happen The Microsoft 365 Roadmap will be renamed to AI at Work Roadmap on August 25, 2026. Beginning in September 2026, new roadmap content for Dynamics 365, Power Platform, and Dataverse will begin publishing to the AI at Work Roadmap. Customers will be able to discover roadmap information across Microsoft's business applications, productivity experiences, Copilot, agents, and AI-powered solutions in a single location. Organizations are encouraged to take advantage of roadmap capabilities including filtering, export, RSS, and MCP integration. There are no changes to how customers access, use, or consume roadmap information. Existing roadmap planning and tracking workflows can continue without modification. [Action required / Recommendations:] No immediate action is required. We recommend: Reviewing the AI at Work Roadmap once the new panding becomes available. Familiarizing your organization with roadmap capabilities such as filtering, CSV export, RSS subscriptions, and roadmap management best practices using the AI at Work Roadmap Guide. Exploring the Release Communications MCP Server documentation if your organization uses AI-powered workflows or planning tools that consume roadmap data. Updating any internal documentation, bookmarks, training materials, or references that use the Microsoft 365 Roadmap name, as appropriate. Reviewing and updating any existing links to Release Planner or release wave materials as your organization transitions to the AI at Work Roadmap. [Compliance Considerations:] No compliance considerations identified. Review as appropriate for your organization. -
(Updated) OneDrive macOS Native Sync Engine
MC1458483 · planForChange · normal · Updated 08/24/2026 22:35
Services: Microsoft OneDrive
Read message
Updated August 24, 2026: We have updated the timeline. Thank you for your patience. [What and why:] We're introducing a new Native Sync Engine for OneDrive on macOS. The redesigned engine integrates more closely with macOS to improve synchronization performance, reliability, responsiveness, and resource efficiency. This update modernizes the OneDrive sync experience on Mac devices by reducing resource consumption, improving reliability, and making synced content more accessible in Finder. [Rollout schedule:] General Availability (Worldwide, GCC, GCC-High, DoD): Rollout will begin in early September 2026 (previously late August) and is expected to complete by late November 2026. [Impact on your organization:] Who is affected: Organizations with eligible macOS devices using the OneDrive sync app. Platforms: OneDrive for macOS, SharePoint Online document library sync. Eligible macOS devices will automatically upgrade to the Native Sync Engine when they receive an updated version of the OneDrive sync app. Users can continue working in OneDrive while the upgrade completes. The Native Sync Engine provides the following improvements: Faster initial synchronization and processing of file changes. Reduced CPU, memory, and battery usage. Improved reliability through a simplified architecture that eliminates several classes of sync issues. Files and folders are immediately visible and browsable in Finder without waiting for folder contents to load. Improved support for storing OneDrive content on eligible external drives. There is no change to Files On-Demand behavior. Online-only files remain online-only until users open them or select Always Keep on This Device. Organizations that sync SharePoint document libraries will notice a change in Finder. Each synced SharePoint library will appear as a separate location in the Finder sidebar instead of being grouped under a single organization entry. Add shortcut to OneDrive remains the recommended method for accessing shared content. [Action required / Recommendations:] No administrative action is required. We recommend that administrators: Notify help desk teams and macOS users about the Finder sidebar change for synced SharePoint libraries. Review and update any internal documentation or training materials that reference the current Finder navigation experience. Consider using Add shortcut to OneDrive instead of the SharePoint Sync command for shared folders and document libraries. If your organization has broadly adopted folder shortcuts, consider hiding the SharePoint Sync button. To determine whether a device is using the Native Sync Engine, open OneDrive Settings and review the version shown on the About tab. Versions that include an alphabetic suffix, such as (26K), are using the Native Sync Engine. For more information: Making Mac OneDrive Faster and More Reliable Add shortcuts to shared folders in OneDrive -
Prepare for upcoming changes to the Excel Exchange connector
MC1461158 · planForChange · normal · Updated 08/24/2026 22:20
Services: Microsoft 365 apps
Read message
[What and Why:] We're introducing new Exchange Mail and Exchange Calendar connectors for Excel Power Query. These connectors are being developed to support scenarios that are currently served by the existing Microsoft Exchange connector. The first release wave will include support for: Exchange Mail Exchange Calendar Guidance for Contacts and Tasks scenarios will be shared separately. Existing workbooks will not automatically transition to the new connectors. Once the new connectors become available, workbook owners will need to reconnect Exchange Mail and Calendar data using the new connector experience. [Rollout Schedule:] August 2026: Microsoft plans to begin customer validation of the new Exchange Mail and Exchange Calendar connectors with selected customers and early adopters. October 2026: Exchange Online begins the final phase of Exchange Web Services (EWS) retirement enforcement. April 2027: The current Microsoft Exchange connector in Excel Power Query is planned for retirement. The new connector experience will be available in Microsoft 365 Apps and Office 2024. Versions earlier than Office 2024 will not receive the new connector experience. Customers using earlier Office versions will need to upgrade to Microsoft 365 Apps or Office 2024 to use the new Exchange Mail and Exchange Calendar connectors. [Impact on Your Organization:] Who is affected: Admins and users who use Excel Power Query workbooks connected to Exchange Online data. Organizations that use the Microsoft Exchange connector to access Exchange Mail or Calendar data from Excel. Platforms and services: Excel Power Query Exchange Online Microsoft 365 Apps Office 2024 What will happen: Existing workbooks will continue to use the current Microsoft Exchange connector until it is retired. Existing workbooks will not automatically migrate to the new Exchange Mail and Exchange Calendar connectors. Workbook owners will need to move their Exchange Mail and Calendar connections to the new connector experience when it becomes available. Workbooks running on Office versions earlier than Office 2024 will require an upgrade to Microsoft 365 Apps or Office 2024 to use the new connector experience. [Action Required / Recommendations:] We recommend that administrators begin preparing for this transition now. Identify users and Excel workbooks that connect to Exchange Mail or Calendar data and prepare workbook owners for migration to the new connector experience. Review EWS usage and determine whether any applications should be added to the EWSAllowedAppIDs allow list during the transition period. Identify users who actively use Exchange-connected workbooks and may be interested in participating in validation of the new Exchange Mail and Exchange Calendar connectors. Preview and Validation Microsoft is seeking customers who use Exchange Mail or Calendar data in Excel and would like to validate the new connectors before broad rollout. To participate, please reach out to excelexchangemigration@microsoft.com. Additional Resources Introducing EWSAllowedAppIDs for the Final Phase of EWS Retirement Contact to validate new connectors. -
(Updated) Microsoft Exchange Online: Prepare for Exchange Web Services retirement with EWSAllowedAppIDs
MC1447678 · planForChange · normal · Updated 08/24/2026 20:19
Services: Exchange Online
Action required by: 09/30/2026 07:00
Read message
Updated August 24, 2026: We have updated the content. Thank you for your patience. [What and why] Exchange Web Services (EWS) in Exchange Online will begin retirement on October 1, 2026, with full retirement beginning April 1, 2027. To help organizations prepare, Microsoft has released EWSAllowedAppIDs, a new Exchange Online configuration that allows administrators to create an allow list of application IDs that are permitted to use EWS. This capability helps administrators identify remaining EWS dependencies, limit EWS access to approved applications, and reduce the risk of service disruption as EWS retirement enforcement begins. This feature is available today. [Rollout schedule] General Availability (Worldwide): Available as of late July 2026 General Availability (GCC): Available as of late July 2026 Retirement milestones: October 1, 2026: Retirement enforcement begins in Exchange Online April 1, 2027: Full retirement begins [Impact on your organization] Who is affected Exchange Online administrators Organizations that continue to use applications or services that depend on EWS Platforms and services Exchange Online Exchange Web Services (EWS) What will happen EWSAllowedAppIDs is a tenant-level allow list that enables administrators to explicitly specify which applications can continue using EWS. Prior to October 2026: If EWSEnabled is not configured (Null), all EWS traffic is allowed. If EWSEnabled=True and no allow list is configured, all EWS traffic is allowed. If EWSEnabled=True and an allow list is configured, only applications included in the allow list and Cross-tenant org relationships can use EWS. If the allow list has no entries, all application can use EWS. If EWSEnabled=False, all EWS traffic is blocked. Beginning in October 2026: If EWSEnabled=True and no allow list is configured, all EWS traffic except Cross-tenant org relationships will be blocked. If EWSEnabled=False, all EWS traffic will be blocked. Tenants with EWSEnabled not configured (Null) remain subject to Microsoft's phased retirement process and will have EWS disabled as part of that rollout. The most important change administrators should understand is that, beginning with retirement enforcement, setting EWSEnabled=True without configuring EWSAllowedAppIDs will no longer permit unrestricted EWS access. Organizations that require EWS after October 2026 should ensure an EWSAllowedAppIDs allow list is configured and validated before enforcement begins. Organizations that have EWSEnabled=True and a configured EWSAllowedAppIDs allow list will not have their EWSEnabled setting modified by Microsoft before April 2027. [Action required and recommendations] We strongly recommend that Exchange Online administrators begin preparation immediately. 1. Inventory EWS usage Identify applications and services currently using EWS in your organization. Review EWS usage reports in your tenant. Review Message center communications related to EWS usage and retirement. Use the guidance in the article Notes From the Field: Finding and Remediating EWS App Usage Before Retirement. 2. Create and validate an allow list Create an EWSAllowedAppIDs allow list containing applications that must continue using EWS. Important considerations: Applications appearing in EWS usage reports that you intend to continue using should be included in the allow list. Microsoft first-party applications that continue to rely on EWS must also be included if they appear in your usage reporting. Setting EWSAllowedAppIDs replaces the existing list. Ensure all required App IDs are included when updating the configuration. Verify the configured allow list: Get-OrganizationConfig -RetrieveEwsOperationAccessPolicy | Format-List EwsAllowedAppIDs The use of RetrieveEwsOperationAccessPolicy is required for performance reasons. The EWSAllowedAppIDs list is only retrieved when explicitly requested. Changes to EWSAllowedAppIDs can take up to 24 hours to take effect. Allow sufficient time after updating the allow list before validating application access or troubleshooting connectivity issues. 3. Prepare for retirement enforcement Before October 2026: Validate your EWS dependencies. Confirm required applications are included in EWSAllowedAppIDs. Enable EWS only if required for approved applications. Organizations that complete this work before retirement enforcement begins are less likely to experience service disruption. Learn more Exchange Online EWS, Your Time is Almost Up | Exchange Team Blog Introducing EWSAllowedAppIDs: Preparing for the Final Phase of EWS Retirement | Exchange Team Blog Notes From the Field: Finding and Remediating EWS App Usage Before Retirement [Compliance considerations] QuestionAnswer Does this change include an admin control?Yes. EWSAllowedAppIDs introduces a new tenant-level administrative control that allows Exchange Online administrators to explicitly define which applications are permitted to access Exchange Web Services (EWS). Does this change alter how customer data is accessed?Yes. The change modifies how applications are authorized to access Exchange Online data through EWS by requiring administrators to explicitly allow approved application IDs as retirement enforcement begins. Does this change alter how admins monitor, manage, or demonstrate compliance-related activities?Yes. Administrators must identify EWS dependencies, configure and maintain an EWSAllowedAppIDs allow list, and validate application access as part of preparing for EWS retirement. -
Improved capabilities for files with Copilot in OneDrive Web
MC1459130 · planForChange · normal · Updated 08/21/2026 22:36
Services: Microsoft OneDrive
Read message
[What and why:] Copilot experiences that have been available in SharePoint expanded preview are now becoming available directly in OneDrive. Users will be able to find, understand, analyze, create, and act on content using natural language, all without leaving their OneDrive experience. With extended file capabilities in Copilot in OneDrive, users can work across their files without opening each one, manually searching through folders, or stitching together insights on their own. These capabilities are designed to help users move faster from files to finished work while respecting the permissions, policies, and governance controls already in place across Microsoft 365. Beginning on August 24 2026, these capabilities will roll out to eligible tenants as an opt-out preview. As part of this rollout, Copilot in OneDrive and Copilot in SharePoint will use the same tenant-level preview controls. [Rollout schedule:] Public Preview (Worldwide): We will begin rolling out on late August 2026 and expect to complete by late September 2026. General Availability (Worldwide): We will begin rolling out on late December 2026 and expect to complete by late December 2026. [Impact on your organization:] Who is affected OneDrive Web users with a Microsoft 365 Copilot license Admins managing OneDrive What will happen Users with a Microsoft 365 Copilot license will automatically see the updated Copilot entry point in OneDrive Web. This includes OneDrive Home, My Files, views such as Shared, People, and Meetings, and supported file preview experiences, including PDFs. From these entry points, users can prompt Copilot in natural language to act on their files and folders. Depending on the context, users can ask Copilot to summarize files, answer questions about documents, compare content, analyze spreadsheets, create new content from existing files, or help find relevant information across their Microsoft 365 context. This rollout extends Copilot file experiences across both SharePoint and OneDrive, giving users a more consistent way to work with content wherever their files are stored. For example, users can ask Copilot to create summaries, FAQs, project overviews, reports, presentations, Office documents, or HTML dashboards based on selected files, folders, or relevant work content. Copilot in OneDrive works within each user’s existing permissions. Users can only access, summarize, analyze, or act on content they are already authorized to view or edit. Updated capabilities in Copilot in OneDrive can help users: Find the right files faster Users can ask Copilot to find files related to a project, topic, meeting, person, or recent activity. This reduces the need to remember exact file names, folder locations, or where a piece of work was last shared. Understand files without opening each one Users can summarize documents, presentations, PDFs, images, meeting recordings, and other supported content types so they can quickly understand what a file contains and decide what to do next. Get answers from file content Users can ask questions about their files, such as “What are the main action items in this deck?” or “What changed between these versions?” Copilot can help extract key information from content users already have access to across supported Microsoft 365 locations, including OneDrive, SharePoint, Teams, and Outlook. Analyze files and folders Users can ask Copilot to analyze supported files, including spreadsheets and collections of documents, to identify trends, compare information, generate insights, or summarize what matters most. Create new content from existing files Users can ask Copilot to create drafts, summaries, FAQs, project overviews, reports, presentations, Office documents, or dynamic HTML dashboards based on selected files, folders, or relevant Microsoft 365 context. Share with more context Users can use Copilot to help share files and folders, check permissions, or update sharing settings, while staying in control of what is shared and with whom. [Action required / Recommendations:] No action is required to receive this update. Copilot in OneDrive will update automatically for users with a Microsoft 365 Copilot license. Optional steps to prepare: Inform users about the new Copilot capabilities and confirm they have a Microsoft 365 Copilot license. Configuration controls available Preview opt-in/opt-out: Admins can use PowerShell cmdlets to opt the entire tenant out of the preview. Find instructions and troubleshooting guidelines. Important: Copilot in OneDrive and Copilot in SharePoint use the same tenant-level preview controls. Organizations that opt out of the preview will disable both Copilot in OneDrive and Copilot in SharePoint. Separate controls for each product are not available. Licensing controls Copilot in OneDrive is available to users with a Microsoft 365 Copilot license. Users without the required license will not have access to Copilot in OneDrive capabilities. Permission and access controls Copilot in OneDrive respects existing file and folder permissions. Users can only use Copilot with content they are already authorized to access. Copilot does not grant new access to files, folders, li paries, sites, or other Microsoft 365 content. Content governance controls Existing governance controls, including sensitivity labels, retention policies, sharing controls, and access restrictions, continue to apply. Copilot-generated responses are grounded in content the user has permission to access. User action and confirmation controls For actions that modify content, such as creating, moving, renaming, sharing, or deleting files, Copilot will require user review or confirmation before completing the action. This helps ensure users remain in control of changes to their files and folders. Additional information Get started with Copilot in OneDrive | Microsoft Support [Compliance considerations:] This feature provides a method of communicating with generative AI and supports the following capabilities: Purview Communication Compliance. This feature generates and stores customer data and supports the following capabilities: Purview eDiscovery, Data Retention, Purview Sensitivity Labels, Customer Lockbox. This feature supports Customer Key for encryption at rest. This feature follows its parent service's data residency and processing commitments. This feature supports role based access control (RBAC). Customer administrators can control user access to this feature using the following interfaces: Licensing, PowerShell Cmdlet. The newly created objects appear in the following inventories: Agent 365 Registry. This product supports Microsoft Purview Data Loss Prevention (DLP) policies. -
Preparing the Windows ecosystem for next-generation code signing
MC1458947 · planForChange · normal · Updated 08/21/2026 17:00
Services: Windows
Read message
What and why: Microsoft is preparing the Windows ecosystem for next-generation code signing to strengthen software supply chain security and improve trust in signed software. As cryptographic standards evolve, Microsoft is introducing newer signing technologies and guidance to help ensure the continued security and compatibility of Windows applications and drivers. Rollout schedule: Microsoft guidance is already available. October 19, 2026: Microsoft Windows Production PCA 2011 expires. End of 2026: Windows is moving toward stronger signing configurations, including RSA-3072 and SHA-384. 2027: Windows signing will transition to post-quantum signing. Impact on your organization: Who is affected Software developers and publishers Organizations that develop and distribute internal applications IT and security administrators responsible for code-signing infrastructure What will happen Future Windows code-signing requirements will adopt stronger cryptographic protections. Organizations using existing code-signing certificates or signing workflows should review their environments and assess readiness. Software publishers might need to update certificates, tooling, or signing processes to remain aligned with future requirements. Action required/recommendations: Review your code-signing certificates, tooling, and signing workflows to understand any potential impact from future code-signing changes. Learn more at Preparing the Windows ecosystem for next-generation code signing. Compliance considerations: Stronger signing supports evolving security and compliance requirements. Review as appropriate for your organization. -
SharePoint Page and News Post: Content Update flow in the FAQ web part will be retired
MC1458479 · planForChange · normal · Updated 08/21/2026 00:41
Services: SharePoint Online
Read message
[What and Why:] The Content Update flow helps SharePoint page authors compare existing FAQ answers with their selected grounding sources and review suggested answer updates. Suggestions are never published automatically; authors choose whether to accept or dismiss each suggestion. As part of our ongoing work to simplify the FAQ authoring experience and focus on its core creation and editing capabilities, we will retire this optional flow. There is no direct replacement for the Content Update check; authors can continue maintaining their FAQs by editing questions and answers directly. [Rollout Schedule:] Worldwide, GCC: We will begin rolling out mid-September 2026 and expect to complete by late September 2026. [Impact on your organization:] Who is affected: SharePoint page authors who use the Content Update flow in the FAQ web part. SharePoint administrators and support teams who maintain guidance for FAQ authors. What will happen: Authors will no longer see or be able to start the Content Update check. Authors will no longer receive AI-generated answer-update suggestions through this flow. Existing FAQ web parts and published content will continue to display normally. Suggestions accepted before retirement are already stored as FAQ content and will remain unchanged. FAQ generation, FAQ import, manual editing, and other FAQ web part capabilities will remain available. No new admin controls are introduced. [Action Required / Recommendations:] No admin action is required, and there is no SharePoint admin center setting or PowerShell action to configure. We recommend that you: Inform SharePoint page authors who use the FAQ web part about this change. Update internal training, support content, or documentation that refers to the Content Update flow. Encourage authors to maintain FAQ questions and answers through the existing manual editing experience. -
Microsoft Entra ID: Retirement of custom CSS layout and positioning properties in company branding
MC1458474 · planForChange · normal · Updated 08/21/2026 00:38
Services: Microsoft Entra
Action required by: 10/26/2026 07:00
Read message
[What and why] Action required only for organizations that use custom CSS layout and positioning properties. Organizations that were not using Custom CSS as of July 21, 2026, are not affected and cannot begin using it going forward. Microsoft Entra External ID tenants are not affected by this change. You're receiving this notification because you're associated with one or more Azure subscriptions that currently use Microsoft Entra ID. As previously communicated in MC1435782, Microsoft is updating Microsoft Entra ID company branding to enhance the security of branded sign-in experiences. To support Microsoft's Secure Future Initiative (SFI) and strengthen protection against phishing attacks, Microsoft Entra ID will retire support for custom CSS layout and positioning properties used in company branding beginning late October 2026. This change helps deliver more secure, reliable, and consistent sign-in experiences while continuing to support branding customization. By limiting the use of layout and positioning modifications that can alter the appearance of sign-in pages, Microsoft is reducing opportunities for deceptive or misleading sign-in experiences. Note that since the previous update in MC1435782, we are retiring an additional set of properties to further secure your branded sign-in experience and harden against phishing risk. These properties will be retired by late October 2026 and may require you to take action if they are used in your configuration. [Rollout schedule] July 21, 2026: Organizations that are not already using these custom CSS properties can no longer begin using them in Microsoft Entra ID custom branding configurations. Late October 2026: Microsoft Entra ID will retire custom CSS layout and positioning properties globally. Later in 2027: Microsoft Entra plans to move towards full custom CSS retirement, with advance notice provided. [Impact on your organization] Who is affected Administrators who manage Microsoft Entra ID custom branding (including Company branding and Branding themes) Organizations that currently use custom CSS layout and positioning properties in custom branding configurations Platforms and services Microsoft Entra ID Company branding Branding themes Web-based branded sign-in experiences What will happen Beginning July 21, 2026, Microsoft Entra ID will no longer allow new use of custom CSS in custom branding configurations. Existing branding customizations that use the retired properties will continue to work until October 26, 2026. After late October 2026, Microsoft Entra ID will no longer honor the retired CSS layout and positioning properties. Branding elements will remain visible but will revert to their default placement and presentation. Branding configurations that depend on the retired properties may display differently after the retirement takes effect. The following CSS properties are being retired: offset offset-path offset-distance margin-block margin-block-start margin-block-end margin-inline margin-inline-start margin-inline-end order grid-area grid-column grid-column-start grid-column-end grid-row grid-row-start grid-row-end isolation overflow-x overflow-y overflow-block overflow-inline content-visibility clip mask mask-image -webkit-mask -webkit-mask-image [Action required and recommendations] If your organization uses any of the retired CSS properties listed above, action is required before October 26, 2026. Recommended actions: Review Microsoft Entra ID company branding configurations. To download your existing custom CSS file, navigate to the Custom branding blade in the Entra Admin Center. Then, click Edit > Layout > Custom CSS > Download. Identify any branding customizations that rely on the retired CSS properties. Remove or redesign customizations that depend on these properties. Test branded sign-in experiences to ensure they display as expected after the retirement date. Communicate any planned branding updates to internal stakeholders as needed. Learn more Deprecation of custom CSS positioning properties - CSS template reference guide | Fundamentals | Microsoft Entra | Microsoft Learn Configure your company branding | Fundamentals | Microsoft Entra | Microsoft Learn Customize the sign-in experience for your application with branding themes | Fundamentals | Microsoft Entra | Microsoft Learn Microsoft Entra ID enhances security of branded sign-ins | Microsoft Entra Blog Microsoft Secure Future Initiative (SFI) [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
New PowerShell scripts to manage Windows settings backup data
MC1458268 · stayInformed · normal · Updated 08/20/2026 17:01
Services: Windows
Read message
What and why: You can now use PowerShell scripts to manage Windows settings backup data and profiles. View and export backup data and device profiles or delete a user’s backup data for governance, retention, and support scenarios. Note: Deleting a user’s backup data is permanent and irreversible. The scripts provide a simpler alternative to working directly with Microsoft Graph beta APIs. The scripts are intended for authorized IT, helpdesk, security, and compliance administrators. Appropriate Microsoft 365 administrator permissions and admin consent are required. Rollout schedule: The scripts are already available on GitHub and the PowerShell Gallery. Impact on your organization: Windows settings backup and restore (formerly known as Windows Backup for Organizations) is an enterprise-grade feature designed to streamline device transitions by securely deleting backup data or profiles or preserving user settings and Microsoft Store app configurations. The scripts provide a simpler alternative to working directly with Microsoft Graph beta APIs. Action required/recommendations: Before using the scripts, review your organization’s backup governance, retention, export, and deletion procedures. Access the scripts on GitHub or using the PowerShell Gallery. Compliance considerations: The scripts can export and delete organizational backup information. Before using them, review administrator permissions, consent, data handling, retention, deletion, audit, and least-privilege requirements as appropriate for your organization. -
Viva Connections multi-home site management moving to SharePoint admin center
MC1457839 · stayInformed · normal · Updated 08/19/2026 22:24
Services: SharePoint Online
Read message
[What and Why:] We are updating Viva Connections multi-home site management by moving administration from the Microsoft 365 admin center (MAC) to the SharePoint admin center (SPAC). This change consolidates Viva Connections administration into SharePoint Home site management and establishes the SharePoint admin center as the primary location for managing Viva Connections experiences. As part of this transition, legacy Viva Connections instances and their associated draft/enabled management concepts are being deprecated. Existing Viva Connections experiences will be automatically upgraded to full Home sites, providing a unified and streamlined management experience. [Rollout Schedule:] General Availability (Worldwide): Rollout will begin early September. Expected completion: Mid September 2026. [Impact on Your Organization:] Who is affected: SharePoint and Viva Connections administrators who manage Viva Connections experiences. Platforms/Services: Viva Connections SharePoint Online Microsoft 365 admin center SharePoint admin center What will happen: Administrators will manage Viva Connections multi-home site functionality through the SharePoint admin center. Administrators can create and manage multiple Home sites from SharePoint admin center. Audience targeting configuration for Home sites will be managed in SharePoint admin center. Administrators can manage Home site priority order and remove Home sites through the SharePoint admin center experience. Existing Microsoft 365 admin center entry points will redirect administrators to the new SharePoint admin center management experience. Existing legacy Viva Connections experiences will be automatically upgraded to full Home sites. Legacy Viva Connections management concepts, including draft and enabled states, will be retired. [Action Required / Recommendations:] No action is required before rollout. Review internal documentation that references Viva Connections management in the Microsoft 365 admin center. Update administrator training materials to reference the SharePoint admin center experience. Inform SharePoint and Viva Connections administrators about the new centralized management location. Validate internal operational procedures after rollout to ensure they reference the SharePoint admin center. [Compliance Considerations:] No compliance considerations identified, review as appropriate for your organization. -
Tenant will be auto-enabled into Microsoft Defender Unified RBAC
MC1457836 · planForChange · normal · Updated 08/19/2026 22:22
Services: Microsoft Defender XDR
Read message
[What and why:] Microsoft Defender Unified RBAC (URBAC) is becoming the single access model for all Defender and Sentinel portal experiences. Your tenant will be auto enabled to URBAC. Unified RBAC will be activated automatically for the in-scope workload(s) on your tenant following a notification period that begins when you receive the in-portal notification, and your roles are imported into Unified RBAC. Activation is expected to occur approximately 30 days after that notification date. Unified RBAC offer more extended access management capabilities, including: A single access management system to manage all roles and permissions across all workloads Scoping capabilities such as Cloud, Sentinel, Identity, and Device Groups. Future-proof assignments that will allow you to include future permissions and workloads This change applies exclusively to Microsoft Defender. Permissions for Microsoft Purview, Exchange Online, Microsoft Entra directory roles, Privileged Identity Management, and Azure resources (not related to Microsoft Sentinel) remain unchanged. In addition, if you are using Powershell with Microsoft Defender for Office 365, this will continue to work as is. [Rollout Schedule:] Global: We will begin rolling out on late September 2026 and expect to complete by late December 2026. [Impact on your organization:] What you will see: Notification banner: A notification will be displayed in the Microsoft Defender portal informing customers that the specified workload(s) will transition to Unified RBAC. Legacy RBAC roles are automatically imported into Unified RBAC. This date marks the beginning of the customer notification period before automatic activation Activation date: Beginning approximately 30 days after the notification date, Unified RBAC will be automatically enabled for the specified workload(s). Customers can review imported role assignments and prepare for the transition during this period. The in-portal banner in the Microsoft Defender portal (‘Permissions and roles’ page) will confirm activation. How this will affect your organization: Your existing roles, if applicable, will be auto-imported into Unified RBAC. Because Unified RBAC is not yet active on your tenant for the workloads indicated, this import has no operational impact until activation. You may review and adjust the imported roles at any time from the Microsoft Defender portal. You may also re-run the import manually. Existing roles and permissions are mapped to Unified RBAC using a mapping logic. For more information on this mapping, please see here. At the end of the notification period, Unified RBAC will be activated automatically for the in-scope workload(s). After activation, authorization for Defender/Sentinel portal experiences defaults to Unified RBAC roles; legacy RBAC assignments are no longer required to operate those portal experiences. Opt-out: Self-service opt-out is available after activation. Go to the ‘workload settings’ control in Unified RBAC to instantly revert to your legacy RBAC system if needed. If you are using APIs to configure your roles and permissions, please transfer to using the new Unified RBAC API Delegated access (B2B/GDAP) or Multi-Tenant Management: remains unchanged. Roles that had assignments to B2B/GDAP users/groups will be included in the automatic import. Entra directory roles are unchanged. Global Administrator, Security Administrator, Security Operator, and Security Reader continue to grant access to the Microsoft Defender portal as they do today. These roles will now map to Unified RBAC permissions as per the mapping referenced earlier. For more information on this mapping, please see here. Azure RBAC continues to govern Azure resources, including Logic Apps and Workbooks. Microsoft Sentinel specific workspace permissions (Sentinel Reader, Responder, Contributor roles) do get auto-enabled to Unified RBAC. Email and Collaboration permissions and Exchange Online permissions continue to govern Exchange Online and Microsoft Purview scenarios. They are no longer required to operate Microsoft Defender for Office 365 portal experiences once Unified RBAC is active. [Action Required / Recommendations:] From the moment of the in-portal notification, review the auto-imported Unified RBAC role assignments in the Microsoft Defender portal (Permissions -> Roles). Validate that each user has the expected URBAC role and scope. Adjust assignments as needed. If any role assignments need to be updated, you can do so directly in the role assignment, even if Unified RBAC is not yet activated for that workload. When using scoping: device groups continue to work as they do today. In addition, Unified RBAC allows you to use Cloud Scopes, Sentinel Scopes, and Identity Scopes. Update internal documentation and runbooks to reflect the new Unified RBAC model. Microsoft Defender Unified RBAC overview: Microsoft Defender unified role-based access control (RBAC) Review and manage imported Unified RBAC roles: Map existing RBAC permissions to Microsoft Defender unified RBAC permissions -
Task Manager features for visibility into AI workloads
MC1457685 · stayInformed · normal · Updated 08/19/2026 17:13
Services: Windows
Read message
What and why: You can use Windows Task Manager for deeper visibility into AI workloads running on a device. Specifically, per-process activity for the neural processing unit (NPU) and graphics processing unit (GPU) neural engine now appear on the Processes and Performance tabs, alongside other familiar data. Rollout schedule: These Task Manager enhancements became available on some newer devices in the May and June 2026 non-security updates. A new blog article is now available to illustrate different use cases for IT professionals, developers, and power users. Impact on your organization: As AI workloads become more common on Windows devices, visibility into NPU and GPU neural engine utilization can help you make better informed decisions. This data can help as follows: For IT professionals: Troubleshoot and report on performance. For developers: Validate whether AI models are landing on the intended NPU or GPU neural engine instead of CPU or standard GPU compute. For power users: Understand and improve performance and battery life. Action required/recommendations: Explore the new metrics in Task Manager to evaluate application performance, troubleshoot resource bottlenecks, and better understand how your devices use AI-capable hardware. Read Task Manager features for visibility into AI workloads. Compliance considerations: No compliance considerations are identified. Review as appropriate for your organization. -
Windows device recovery in 2026: A guide for IT pros
MC1457106 · stayInformed · normal · Updated 08/18/2026 17:00
Services: Windows
Read message
What and why: Over the past year, more tools became available to help you restore user productivity quickly. A new scenario-based guide can help you identify and choose the right recovery approach. Scenarios and solutions range from more to less common. Whether you're defending against the next widespread outage or helping a single user get back to work, these capabilities work together to reduce downtime, minimize data loss, and keep your organization productive. Rollout schedule: The new guide is already available. All solutions and tools are already available as well. Impact on your organization: Windows recovery requires a comprehensive framework matching the right solution to every scenario. From more to less common, the guide includes the following scenarios: Individual device issues after an update A single malfunctioning component A recent isolated issue or widespread device issue Persistent device issues after recovery attempts Deep OS corruption Hardware failure or device unavailability Mass-scale outages affecting startup Each recovery scenario has at least one tool that you can use to remediate the device. The newer solutions include detailed walkthroughs to help you get started. Action required/recommendations: Read Windows device recovery in 2026: A guide for IT pros to learn and prepare for these recovery scenarios and available solutions. Compliance considerations: No compliance considerations are identified. Review as appropriate for your organization. -
(Updated) Microsoft Purview | Data Security Triage Agent Summaries for DLP Alerts in Microsoft Defender XDR
MC1255406 · planForChange · normal · Updated 08/17/2026 22:48
Services: Microsoft Defender XDR, Microsoft Purview
Read message
Updated August 17, 2026: We have updated the timeline. Thank you for your patience. [Introduction] We’re introducing Data Security Triage Agent summaries and categorizations for Data Loss Prevention (DLP) alerts directly within the Microsoft Defender XDR portal. This update helps security analysts triage DLP alerts more efficiently by surfacing AI-generated summaries and categorizations created by the Microsoft Purview Data Security Triage Agent. Screenshot 1: Data Security Triage Agent outputs and summaries now available in DLP alerts in Microsoft Defender XDR This message is associated with Roadmap ID 558860. [When this will happen:] Public Preview: We will begin rolling out early April 2026 and expect to complete by mid-April 2026. General Availability (Worldwide): We will begin rolling out August 2027 (previously August 2026). [How this affects your organization:] Who is affected: Security analysts and admins triaging DLP alerts in Microsoft Defender XDR Organizations using Microsoft Purview Data Security Triage Agent What will happen: DLP alerts in Defender XDR will display AI-generated summaries and categorizations when the Agent is deployed. Screenshot 2: Security Analysts and Admins triaging DLP alerts in Defenders will be able to deploy the Data Security Triage Agent from the Microsoft Defender XDR portal If the Agent is not deployed, eligible analysts can deploy it from the DLP alert page in Defender XDR. Agent management (instructions, pause/deactivate, usage monitoring) remains in Microsoft Purview. Existing DLP policies and enforcement are not changed. There is no impact to users. [What you can do to prepare:] Deploy the Data Security Triage Agent in Microsoft Purview to enable summaries in Defender XDR. Review role assignments to ensure analysts who triage DLP alerts have the appropriate permissions. Update internal security operations documentation to reflect the new triage experience. Familiarize security teams with where Agent deployment can occur (Defender XDR) and where ongoing management is performed (Purview). Learn more: Before rollout, we will update this post with new documentation. [Compliance considerations:] Compliance area Explanation AI/ML or agent capabilities interacting with customer data This change introduces AI-generated summaries and categorizations for DLP alerts using the Microsoft Purview Data Security Triage Agent, which processes existing DLP alert data to assist analysts during triage. Admin controls Admins can deploy the Data Security Triage Agent from the Microsoft Defender XDR portal. Ongoing agent management, including custom instructions, pausing or deactivating the agent, and monitoring usage, remains available in the Microsoft Purview portal. Admin monitoring and compliance reporting The update enhances DLP alert investigations by adding AI-generated context, improving how admins monitor and assess data security incidents without changing underlying DLP policy enforcement or audit logging. -
60-Day Reminder: AD FS DKM container ACL hardening begins in October 2026
MC1456735 · stayInformed · normal · Updated 08/17/2026 21:01
Services: Windows
Read message
What and why Windows updates released in October 2026 will begin Enforcement mode for AD FS Distributed Key Manager (DKM) container ACL hardening. This hardening change is designed to address the elevation of privilege vulnerability documented in CVE-2026-56155 by automatically remediating insecure DKM container ACL configurations on supported Windows Server versions. Organizations using Active Directory Federation Services (AD FS) should use the remaining Audit mode period to review DKM container permissions, identify compatibility issues, and complete preparation before Enforcement mode begins. Rollout schedule Enforcement mode begins with the October 2026 Windows security update. Impact on your organization Organizations using AD FS might experience changes to DKM container permissions when remediation is applied during Enforcement mode. With the October 2026 Windows security update, supported Windows Server versions will run remediation by default unless administrators explicitly opt out. Windows Server 2012 and Windows Server 2012 R2 still require manual remediation and will not be automatically remediated. Action required/recommendations Organizations using AD FS should: Install the July 2026 Windows security update or a later Windows update on AD FS servers. Review AD FS Admin event logs for Event ID 1132, which indicates that DKM container permissions require attention. Review and test remediation during the current Audit mode phase before Enforcement mode begins in October 2026. See the guidance in: CVE-2026-56155: AD FS Distributed Key Manager container ACL hardening. Compliance considerations No compliance considerations are identified. Review as appropriate for your organization. -
Microsoft 365 Copilot: Planner capabilities in Copilot chat
MC1443523 · stayInformed · normal · Updated 08/14/2026 21:37
Services: Planner, Microsoft 365 Copilot Chat
Read message
[What and why] We are introducing Planner capabilities in Microsoft 365 Copilot Chat. Users will be able to create, update, QnA Planner tasks and plans using natural language within Copilot Chat, helping them manage work without switching between applications. This message is associated with Microsoft 365 Roadmap ID 516577. [Rollout schedule] General Availability (Worldwide): Beginning in early September 2026 [Impact on your organization] Who is affected Users of Microsoft 365 Copilot Chat Users of Microsoft Planner Platforms/Services Desktop, Web What will happen Users will be able to: Create Planner tasks and plans from Microsoft 365 Copilot Chat using natural language prompts. View Planner task and plan details directly in Microsoft 365 Copilot Chat: (this version is text-only, the next version will have interactive task card as shown below) Manage and update Planner tasks and plans across Copilot and Planner without switching between applications. Existing Planner permissions and access controls continue to apply. No changes to existing Planner data storage or permissions are expected. The feature will become available through standard service rollout for eligible users. [Action required/recommendations] No action is required. We recommend that you: Review and update internal training and adoption materials for Microsoft 365 Copilot and Microsoft Planner. Notify help desk and support teams about the new Planner task management capabilities available in Microsoft 365 Copilot Chat. [Compliance considerations] QuestionAnswer Does the change introduce or significantly modify AI/ML or agent capabilities that interact with or provide access to customer data?Yes. Microsoft 365 Copilot Chat will use natural language interactions to create and retrieve Planner task information that users already have permission to access. Does the change provide users a new way of interacting with generative AI?Yes. Users can create, manage, and retrieve Planner task information through conversational prompts in Microsoft 365 Copilot Chat. -
60-Day Reminder: Windows Server 2022 will reach end of mainstream support on October 13, 2026
MC1454978 · stayInformed · normal · Updated 08/14/2026 21:01
Services: Windows
Read message
On October 13, 2026, Windows Server 2022 will reach end of mainstream support. The October 2026 security update will be the last mainstream support update available for this version. After this date, Windows Server 2022 will transition to extended support, which includes security updates at no additional cost, and will continue to receive monthly security updates through October 14, 2031. For more information, see the Fixed Lifecycle Policy. Windows Server 2025 is now the latest Long-Term Servicing Channel (LTSC) release for Windows Server. To help keep your environment protected and supported, plan to upgrade to Windows Server 2025 for full mainstream support. To download a free 180-day evaluation, visit the Microsoft Evaluation Center. Evaluate upgrade options and begin deployment testing early to help ensure a smooth transition. For detailed lifecycle dates, see the Windows Server 2022 lifecycle page. For servicing timelines and related resources, see Windows Server release information, Lifecycle FAQ - Windows Server, and Microsoft Lifecycle Policy search tool. -
60-Day Reminder: Windows 11, version 24H2 and Windows 10 LTSB 2016 reaching end of updates on October 13, 2026
MC1454882 · stayInformed · normal · Updated 08/14/2026 17:02
Services: Windows
Read message
On October 13, 2026, Windows 11, version 24H2 Home and Pro editions, and Windows 10 Enterprise LTSB 2016 will reach end of updates. After this date, devices running these editions will no longer receive monthly security and non-security preview updates containing protections from the latest security threats. We recommend updating devices running Windows 11, version 24H2 Home and Pro editions to Windows 11, version 25H2 to continue receiving monthly security and quality updates. Enterprise and Education editions remain supported until October 12, 2027. For more information, see the How to get the Windows 11 2025 Update video. For devices running Windows 10 Enterprise LTSB 2016, we recommend updating to the latest Long-Term Servicing Channel (LTSC) release, Windows 11 Enterprise LTSC 2024. Extended Security Updates (ESU) are also available for organizations that need additional time to complete their transition. For more information about product lifecycle dates, see Windows 11 release information, Windows 10 release information, and Lifecycle FAQ - Windows. -
Dynamics 365 Customer Service - Validate knowledge and process adherence with evaluations
MC1454352 · stayInformed · normal · Updated 08/13/2026 23:34
Services: Dynamics 365 Apps
Read message
We are announcing the ability to validate knowledge and process adherence with Quality Evaluation Agent knowledge source in Dynamics 365 Customer Service. This feature will reach public preview on October 30, 2026. How does this affect me? This feature allows you to evaluate agent interactions against approved knowledge and business processes. With Quality Evaluation Agent knowledge source adherence, supervisors can create evaluation criteria that reference specific knowledge articles or sources. They define targeted questions that verify whether agents follow required steps, use accurate information, and adhere to documented guidance during customer interactions. Knowledge-based questions can be scored or treated as compliance checks, making it easy to identify gaps, reinforce standards, and drive continuous improvement. This capability integrates seamlessly with Quality Evaluation Agent’s evaluation framework, supporting versioning and simulations so supervisors can validate knowledge-adherence criteria before publishing them for live quality evaluations. What action do I need to take? This message is for awareness, and no action is required. -
Windows Office Hours: August 20, 2026
MC1454205 · stayInformed · normal · Updated 08/13/2026 17:05
Services: Windows
Read message
If you are an IT admin with questions about managing and updating Windows, we want to help. Every third Thursday of the month, we host a live chat-based event on the Tech Community called Windows Office Hours. Members of the Windows, Microsoft Intune, Windows Autopilot, Windows Autopatch, and Windows 365 engineering teams will be standing by to answer your questions. Want to attend the August 20 session of Office Hours? Add it to your calendar and select Attend on the event page to let us know you're coming. There is no video or live meeting component. Simply visit the event page, sign in to the Tech Community, and leave your questions in the Comments section. You can also bookmark https://aka.ms/Windows/OfficeHours for upcoming dates (and the ability to add this event to your calendar). We look forward to helping you. -
Microsoft Teams: Configure mandatory participant consent before joining meetings
MC1454114 · planForChange · normal · Updated 08/13/2026 13:41
Services: Microsoft Teams
Read message
[What and Why] Microsoft Teams is introducing a new capability that allows admins to configure mandatory pre-meeting consent for participants. This feature helps organizations meet compliance and regulatory requirements by ensuring attendees acknowledge custom terms or disclaimers before joining meetings, such as recording notices or responsible AI usage guidelines. Consent acknowledgments are recorded in audit logs to support governance, investigations, and transparency. This message is associated with Microsoft 365 Roadmap ID 561914. [Rollout Schedule] General Availability Targeted Release: Beginning in September 2026 Worldwide and GCC: Beginning in mid-October 2026 and expected to complete by mid-November 2026 GCC High, and DoD: Beginning in mid-November 2026 and expected to complete by mid-December 2026 [Impact on Your Organization] Who is affected Admins managing Microsoft Teams policies and all meeting participants, including organizers, in organizations that enable this feature Platforms/Services Microsoft Teams Teams Admin Center Audit logs What will happen Admins can configure a mandatory pre-meeting consent experience in Teams admin center: Custom content such as disclaimers, terms and conditions, or compliance notices can be defined: Admins can preview how consent content will appear to participants before enabling: All meeting participants—including organizers, internal users, external users, and anonymous attendees—must accept the configured consent before joining meetings where the policy is enabled. Meeting organizers are not exempt from the policy and must also accept the consent experience when joining meetings governed by the configured policy. The feature is disabled by default and requires admin configuration: Admins can configure one default language and up to four additional languages: Participants see consent content based on their device language settings; if unavailable, the default language is shown. User consent is recorded in audit logs for compliance and reporting purposes. No impact to users or meetings unless the feature is enabled by admins. [Action Required/Recommendations] No action is required if you do not plan to use this feature. If you plan to enable this capability: Review compliance and legal requirements for your organization. Configure pre-meeting consent policies in Teams admin center. Define, validate, and preview consent messaging across supported languages. Communicate this change to users so that they understand the new meeting join requirement. Update internal documentation and helpdesk guidance as needed. Learn more Supporting Learn documentation is expected closer to General Availability rollout. [Compliance considerations] QuestionAnswer Does the change store new customer data?Yes. Participant consent acknowledgments are stored in audit logs for compliance and auditing purposes. Does the change alter admin monitoring or reporting?Yes. Adds visibility into participant consent via audit logs, enhancing compliance monitoring. Does the change include an admin control?Yes. Admins can enable and configure the feature in Teams admin center. -
Introduction of Macro Region Geography-Based Environment Provisioning
MC1444064 · stayInformed · normal · Updated 08/13/2026 01:20
Services: Dynamics 365 Apps
Read message
Macro region geography enablement affects environment provisioning and enables customers to select a macro region geography during environment creation. How does this affect me? With this change: Customers will select a macro region geography (e.g., North America, Europe & UK, Asia-Pacific) instead of a specific datacenter region. The platform will automatically assign the optimal datacenter region within the selected Macro region geography based on capacity, availability, scale, and performance considerations. This approach helps ensure a more scalable, resilient, and performant experience for all customers while continuing to respect data residency commitments. As we begin rolling out Macro region globally and make it generally available: If customers need the ability to select a specific datacenter region during creation of new environments for Dynamics 365 & Power Platform, they need to enable advanced data residency for 100% of Microsoft 365 seats on that tenant. Continuity for existing environments: As of the date of the announcement, Microsoft does not anticipate impact on existing environments, which continue to retain the selected datacenter region. This is subject to future adjustments due to technical (capacity, performance, compute) constraints and changing circumstances beyond reasonable control. Customers will be able to see their macro region geography and datacenter region in the environment properties and in the environment list. See the list of macro region geographies here. Data Residency & Compliance Data will always reside within the selected macro region geography boundary. If a customer needs EUDB, they must select macro region geography 'European Union (EU) and European Free Trade Association (EFTA)'. This ensures their data at rest is in EUDB boundary. Learn more about EUDB here. Note: Australia and India geographies have tax restrictions and need data residency alignment and accountability for compliance with local tax reporting rules and for auditability within jurisdiction. Customers needing their data at rest to stay in Australia and India will need advanced data residency (ADR). The platform does not expand residency guarantees beyond contractual commitments. For customers with ADR criteria met, D365 and Power Platform customer data is stored at rest within the customer’s selected datacenter region. Customer Experience Example If the customer does not have advanced data residency (ADR): The customer selects “Europe & UK” as their Macro Region. The platform assigns a datacenter region (e.g., Germany, or Italy) based on capacity and availability. The customer can view the assigned datacenter region within the macro region geography after provisioning. If the customer has ADR enabled for 100% of their M365 seats in that tenant: They qualify for datacenter region selection for D365 and power Platform and will see list of Power Platform and Dynamics 365 datacenter regions to select from, during environment creation. This ensures customer data is stored at rest within the selected datacenter region. If the customer does not have ADR and requires datacenter region selection (e.g., France), they will need to get the ADR SKU. Please learn more here. -
90-Day Reminder: Windows 11, version 23H2 Enterprise and Education editions reach end of updates on November 10, 2026
MC1453772 · stayInformed · normal · Updated 08/12/2026 21:15
Services: Windows
Read message
On November 10, 2026, Windows 11, version 23H2 Enterprise and Education editions will reach end of updates. The November 2026 Windows security update will be the last update available for these editions. After this date, devices running these editions will no longer receive monthly security and non-security preview updates containing protections from the latest security threats. To continue receiving monthly security and quality updates, we recommend updating eligible devices running Windows 11, version 23H2 Enterprise and Education editions to Windows 11, version 25H2. Windows 11, version 25H2 Enterprise and Education editions will continue to receive updates until October 11, 2028. For more information about product lifecycle dates, see Windows 11 release information and Lifecycle FAQ - Windows. -
The August 2026 Windows security update is now available
MC1452953 · stayInformed · normal · Updated 08/11/2026 17:27
Services: Windows
Read message
The August 2026 security update is now available for all supported versions of Windows. We recommend that you install these updates promptly. For more information about the contents of this update, see the release notes, which are accessible from the Windows 11 update history page. To learn more about the different types of monthly quality updates, see Understanding Windows monthly updates. Highlights for the Windows 11, version 25H2 update: This security update includes improvements that were part of update KB5101684 (released July 28, 2026). This update expands high confidence device targeting data, increasing coverage of devices eligible to automatically receive new Secure Boot certificates. Devices receive the new certificates only after demonstrating sufficient successful update signals, maintaining a controlled and phased rollout. This update makes quality improvements to the servicing stack, which is the component that installs Windows updates. Short on time? Watch the Windows 11 release notes video for this month’s tips. For instructions on how to install this update, see the KB article for your operating system listed below: Windows 11, version 26H1: KB5121000 Windows 11, versions 25H2 and 24H2: KB5121003 Windows 11, version 23H2: KB5120240 Windows 11 Enterprise LTSC 2024: Hotpatch KB5120994 Windows 10, versions 22H2 and 21H2: KB5120249 Windows 10 Enterprise LTSC 2019 and Windows Server 2019: KB5120238 Windows 10 LTSB 2016 and Windows Server 2016: KB5120418 Windows Server 2025: KB5120233 Windows Server 2025 Datacenter: Azure Edition: Hotpatch KB5120228 Windows Server 2022: KB5120242 Windows Server 2022 Datacenter: Azure Edition: Hotpatch KB5120229 Windows Server 2012 R2: KB5120385 Windows Server 2012: KB5120386 Note: With recent and upcoming Windows updates over the next few months, a limited number of consumer and business devices might experience one additional restart during installation. This one‑time restart occurs after a Secure Boot certificate update is applied as part of the Secure Boot update process. IMPORTANT: As part of the August 2026 Windows security release, separate standalone security updates are available for a limited number of devices enrolled in hotpatch updates. Affected devices will automatically install the August 2026 hotpatch update first, followed by the applicable standalone update. Installing a standalone update does not remove a device from hotpatch updates, and no re-enrollment or policy change is required. On some devices, a restart is required to complete installation, as noted below. No action is required from IT administrators and enterprise end-users as this update process will happen automatically on hotpatch-enabled devices. For more information, see the applicable KB article: Windows 11 Enterprise, versions 25H2 and 24H2: Standalone update KB5123607 Windows 11 Enterprise, versions 25H2 and 24H2 — Additional update for devices where the Pluton security processor has been configured as the TPM: KB5123273 (restart required) Windows Server 2022: KB5123303 (restart required) -
Microsoft Exchange Online: Retirement of the Other features page in Exchange admin center
MC1452374 · planForChange · normal · Updated 08/11/2026 00:20
Services: Exchange Online
Read message
[What and why] We are retiring the Other Features page in the Exchange admin center (EAC) as part of our ongoing efforts to simplify and modernize the Exchange administration experience. The Other Features page primarily provides links to administrative experiences hosted in other Microsoft admin portals and does not contain unique Exchange Online administration functionality. After this change, administrators can continue to access those experiences directly through their respective admin portals. No Exchange Online workloads, settings, policies, or administrative capabilities are being removed. [Rollout schedule] Worldwide: Beginning in early September 2026 and expected to complete in February 2027 [Impact on your organization] Who is affected Exchange Online administrators who use the Exchange admin center Organizations with internal documentation, bookmarks, or operational processes that reference the Other Features page Platforms and services Exchange Online Exchange admin center (web) What will happen The Other Features page will be removed from the Exchange admin center. Administrative experiences previously linked from the page will remain available through their respective Microsoft admin portals. No Exchange Online workloads, configurations, policies, or management capabilities will be removed. This change is intended to reduce legacy navigation elements and provide a more streamlined Exchange administration experience. [Action required and recommendations] While no technical action is required, we recommend that administrators: Review and update any documentation that references the Other Features page. Update any saved bookmarks that point to the Other Features page. Review operational procedures and training materials that instruct administrators to use the Other Features page. Ensure administrators access the associated Microsoft administrative experiences directly through their dedicated portals. [Compliance considerations] No compliance considerations identified, review as appropriate for your organization. -
Microsoft Edge: Retirement of default unload event support
MC1449170 · planForChange · normal · Updated 08/06/2026 22:48
Services: Microsoft 365 suite
Action required by: 09/05/2026 07:00
Read message
If your websites or applications do not use unload event handlers (unload), the impact described below does not apply and no action is required. [What and why] Microsoft Edge is changing the default behavior of the web platform unload event as part of the ongoing retirement of unload event handlers. Today, unload event handlers are allowed by default. As this change rolls out, pages will no longer run unload event handlers unless the site explicitly permits them through Permissions Policy. Organizations should work with application owners to migrate their applications to modern lifecycle events and APIs designed for these scenarios. The unload event is not a reliable way to save data, perform cleanup operations, or indicate that a user session has ended because browsers and operating systems can suspend or terminate pages without firing it. It can also prevent pages from using the back/forward cache, which may affect navigation performance. [Rollout schedule] Worldwide, GCC, GCC High, DoD: Beginning in early September 2026 and expected to complete in October 2026 [Impact on your organization] Who is affected Organizations may be affected if internal websites, public websites, or third-party web applications that users depend on use unload event handlers to provide required functionality. Users are affected only when a website or application depends on unload event handlers and does not provide an alternative implementation. Platforms and services Microsoft Edge Websites and web applications opened in Microsoft Edge WebView2-based applications Managed Microsoft Edge environments What will happen Websites and applications that rely on unload event handlers may experience functional changes when the handlers no longer run by default. Common scenarios include applications that use unload handlers to: Save user data Release resources Send analytics or telemetry Notify services that a session has ended Organizations can temporarily preserve the current behavior while applications are updated by enabling the ForcePermissionPolicyUnloadDefaultEnabled Microsoft Edge policy. This policy is intended only as a migration aid while application owners update affected applications. A website can still apply a more restrictive Permissions Policy configuration. [Action required and recommendations] Complete the following actions by September 6,2026: Identify internal and business-critical web applications that register unload event handlers, including handlers introduced through third-party libraries. Validate application behavior without relying on unload event handlers. Use Microsoft Edge DevTools to identify pages that are blocked from using the back/forward cache because of unload listeners. Migrate data-saving scenarios to the visibilitychange event and use transitions to the hidden state as the final reliable opportunity to preserve application state. Use the pagehide event when code must respond to navigation away from a page while remaining compatible with the back/forward cache. Update internal development standards, support documentation, and testing guidance. Notify application owners, support teams, and affected users of any application-specific changes. If an application cannot be updated before rollout completion, site owners can temporarily enable unload support through Permissions Policy. Administrators can also use the ForcePermissionPolicyUnloadDefaultEnabled Microsoft Edge policy to retain the previous default behavior while migration work is completed. These controls are intended to provide migration time and should not be considered permanent solutions. A website can still apply a more restrictive Permissions Policy configuration. Learn more ForcePermissionPolicyUnloadDefaultEnabled | Microsoft Edge | Microsoft Learn Document: visibilitychange event | Mozilla Window: pagehide event | Mozilla [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
Plan for Windows 10 Enterprise LTSC 2021 end of support
MC1448328 · stayInformed · normal · Updated 08/05/2026 20:57
Services: Windows
Read message
What and why: Windows 10 Enterprise LTSC 2021 reaches end of support on January 12, 2027. As you plan to upgrade these devices to a supported version, you can purchase Extended Security Updates (ESU). Rollout schedule: September 1, 2026: Extended Security Updates (ESU) will be available for purchase. January 12, 2027: Windows 10 Enterprise LTSC 2021 will reach end of support. Impact on your organization: Devices running Windows 10 Enterprise LTSC 2021 will receive a final monthly security update on January 12, 2027. After that, they will no longer receive Windows security updates, non-security updates, bug fixes, technical support, or online technical content updates. Action required/recommendations: Upgrade these devices to Windows 11 Enterprise LTSC 2024 for the latest security capabilities. If your organization needs additional time to complete your migration, consider purchasing Extended Security Updates (ESU). Learn more at Plan for Windows 10 Enterprise LTSC 2021 end of support. Compliance considerations: No compliance considerations are identified. Review as appropriate for your organization. -
Microsoft Teams: Report security concerns in Teams meetings
MC1446794 · planForChange · normal · Updated 08/05/2026 17:04
Services: Microsoft Teams, Microsoft Defender XDR
Read message
[What and why] Microsoft Teams is introducing a new Report a meeting capability that allows meeting participants to report suspicious, malicious, or potentially fraudulent activity directly from Teams meetings. This feature helps organizations identify and investigate threats such as phishing, impersonation, scams, and other suspicious behavior. Reported meeting information can help security teams assess potential threats and take appropriate action. [Rollout schedule] Targeted Release: Beginning in early August 2026 General Availability (Worldwide): Beginning in early October 2026 [Impact on your organization] Who is affected Users who participate in Microsoft Teams meetings on Windows, Mac, and web Platforms and services Microsoft Teams Microsoft Defender portal Teams admin center What will happen A new Report a meeting option will be available from:The More actions (...) menu during an active meeting: The meeting chat header for scheduled and ad hoc meetings: Users can report suspected phishing attempts, impersonation, social engineering activity, scams, or other security concerns directly from Teams. Relevant meeting metadata and limited contextual information will be collected to support investigation and remediation activities. Information associated with reported meetings will be available for investigation by administrators. Organizations with Microsoft Defender for Office 365 Plan 1, Plan 2, or Microsoft Defender XDR can review detailed reported meeting submissions in the Microsoft Defender portal. Information about user-submitted reports will also be available in the Teams admin center under Protection reports > User-reported security submissions. Administrators can investigate reported meetings and take actions according to their organization's security processes and policies. The Report a meeting capability is enabled by default. [Action required and recommendations] Review your organization's security investigation and response processes before rollout. Recommended actions: Review Microsoft Defender user reporting settings and ensure your reporting workflows align with organizational requirements. If your organization uses Microsoft Defender for Office 365 or Microsoft Defender XDR, verify that Teams meeting reporting is configured appropriately so detailed reported meeting submissions are available to security investigators in the Microsoft Defender portal. Inform users about the new Report a meeting capability and when it should be used. Update internal security awareness materials and incident response procedures, as needed. Verify that security administrators responsible for reviewing reports have appropriate access to the Microsoft Defender portal or Teams admin center. [Compliance considerations] QuestionAnswer Does this change store new customer data?Yes. When users submit a meeting security report, relevant meeting metadata and limited contextual information are collected and stored to support investigation and remediation activities. Does this change alter how existing customer data is processed, stored, or accessed?Yes. Reported meeting information is processed and made available through Microsoft Defender and Teams admin experiences to support security investigations. Does this change provide a new way for users, tenants, or subscriptions to communicate?Yes. Users can submit security reports directly from Teams meetings and meeting chats, creating a new reporting channel between users and organizational security administrators. Does this change alter how admins monitor, report on, or demonstrate compliance activities?Yes. Administrators can review and investigate user-submitted meeting security reports in the Microsoft Defender portal and Teams admin center, providing additional visibility into security-related events. Does this change include an admin control?Yes. Administrators can configure reporting and investigation settings in the Microsoft Defender portal to enable access to detailed meeting security reports. Does this change allow users to enable or disable the feature themselves?Yes. Users can choose whether to submit a security report for a meeting by using the new Report a meeting option in Teams. -
Microsoft Teams: Users can report security concerns in group calls
MC1447673 · planForChange · normal · Updated 08/05/2026 17:03
Services: Microsoft Teams, Microsoft Defender XDR
Read message
[What and why] We're introducing a new security reporting capability in Microsoft Teams that allows users to report suspicious group calls directly from their call history. This feature helps organizations identify and investigate potential scams, impersonation attempts, unwanted external calls, and other security concerns that occur during group calling experiences. Reported call information can be reviewed by administrators in Microsoft Teams admin center and, when configured, in Microsoft Defender. [Rollout schedule] Targeted Release: Beginning in early August 2026 General Availability (Worldwide): Beginning in early October 2026 [Impact on your organization] Who is affected Users who make or receive group calls in Microsoft Teams Teams administrators and security administrators responsible for investigating reported security concerns Platforms and services Microsoft Teams for Windows Microsoft Teams for Mac Microsoft Teams for web Microsoft Teams admin center Microsoft Defender portal (when licensed and configured) What will happen A new Report a call option will be available for group calls in Teams call history: Users can select More options (...) next to a group call and choose Report a call. Relevant call metadata and limited contextual information will be securely submitted to the organization and Microsoft for analysis. Security teams can review detailed reported call submissions in the Microsoft Defender portal when the organization has Microsoft Defender for Office 365 Plan 1, Microsoft Defender for Office 365 Plan 2, or Microsoft Defender XDR. Administrators can review user-reported security submissions in Teams admin center under Analytics & reports > Protection reports > User-reported security submissions. Administrators can investigate reported calls and take appropriate action based on organizational security processes. This feature is enabled by default in Teams clients. [Action required and recommendations] Review whether your organization wants to use Microsoft Defender for enhanced investigation capabilities. Recommended actions: Verify that user reporting is enabled in the Microsoft Defender portal if you want detailed reported call submissions to appear there. Without this, detailed reported calls will not appear in the Defender portal. Review access permissions for security teams that will investigate reported submissions. Inform users about the new Report a call option and provide guidance on when it should be used, such as:Suspected scams Impersonation attempts Unwanted external calls Other suspicious calling activity Review reporting data in Teams admin center if your organization does not use Microsoft Defender. Learn more End user reporting for Security | Microsoft Teams | Microsoft Learn [Compliance considerations] QuestionAnswer Does this change provide a new way for users, tenants, or subscriptions to communicate?Yes. This change introduces a new user reporting capability within Microsoft Teams group call history, enabling users to submit security concern reports for group calls directly from the Teams client. Does this change alter how existing customer data is processed, stored, or accessed?Yes. When a user reports a group call, relevant call metadata and limited contextual information are shared with the organization and Microsoft for security investigation and analysis. Does this change store new customer data?Yes. User-submitted call reports, including associated metadata and contextual information, are stored and made available through the Microsoft Defender portal and Teams admin center reporting experiences. Does this change alter how admins monitor, report on, or demonstrate compliance activities?Yes. Administrators gain new reporting and investigation capabilities through the Microsoft Defender portal and Teams admin center, where user-reported security submissions can be reviewed and analyzed. Does this change include an admin control?Yes. Administrators can configure whether detailed Teams call reports are received and available in the Microsoft Defender portal by managing the Teams call reporting setting. Can users enable or disable the feature themselves?Yes. Users can choose whether to submit a report for a specific call by using the new Report a Call option in Teams call history. -
(Updated) Clearer RSVP selection in Outlook Mobile
MC1269211 · stayInformed · normal · Updated 08/04/2026 19:04
Services: Exchange Online
Read message
Updated August 4, 2026: We have updated the timeline. Thank you for your patience. [Introduction] We’re improving the RSVP experience in Outlook Mobile by visually highlighting the response a user has selected (Yes, Maybe, or No). This makes it easier for users to quickly see how they’ve responded to a meeting invitation. [When this will happen:] General Availability (Worldwide, GCC, GCC High): Rollout begins mid-September 2026 (previously August) and is expected to complete by mid-October 2026 (previously end of August). [How this affects your organization:] Who is affected: All users who access Outlook Mobile on iOS or Android Applies to Worldwide, GCC, and GCC High tenants What will happen: The selected RSVP option (Yes, Maybe, or No) will be visually highlighted Users can quickly confirm how they responded to a meeting invitation and edit as needed The feature is enabled by default No changes to existing meeting workflows or policies No impact to Outlook on the web or Outlook desktop clients [What you can do to prepare:] No admin action is required; the update will roll out automatically Consider notifying helpdesk staff of the visual change Update internal documentation if needed [Compliance considerations:] No compliance considerations identified, review as appropriate for your organization. -
(Updated) Microsoft Entra ID SSPR will require registered authentication methods starting November 9, 2026
MC1325414 · planForChange · normal · Updated 08/04/2026 16:34
Services: Microsoft Entra
Action required by: 11/06/2026 07:00
Read message
Updated August 4, 2026: We have updated the timeline. Thank you for your patience. [What and Why] You’re receiving this message because your organization uses Microsoft Entra ID Self-Service Password Reset (SSPR). Currently, SSPR may allow users to verify their identity using contact information stored in directory attributes such as mobile phone, business phone, and alternate email, even if those values were never explicitly registered as authentication methods. To strengthen identity security, SSPR will require explicitly registered authentication methods for verification. This change is part of Microsoft’s Secure Future Initiative and ensures password reset verification is based on trusted, user-validated methods rather than directory-sourced attributes. [Rollout Schedule] October 5, 2026: SSPR registration campaign begins prompting users and administrators to register authentication methods if SSPR setting requires registration and users do not have enough methods. November 7, 2026: Enforcement begins. SSPR will no longer accept directory-sourced contact information for verification. General Availability (Worldwide, GCC, GCC High): Early November 2026 (previously Early September) through mid-November 2026 (previously mid-September) [Impact on Your Organization] Who is affected All users (including administrators) in tenants with SSPR enabled Applies to Public cloud and US Government clouds (GCC, GCC High, DoD) Platforms/Services Microsoft Entra ID Self-Service Password Reset (SSPR) Web and admin portal experiences What will happen Only explicitly registered authentication methods will be accepted for SSPR verification. Directory attributes (such as mobilePhone, businessPhone, otherMails) will no longer be valid unless registered. Approximately 86% of SSPR verifications already use registered methods today. Users without registered methods at enforcement will be:Unable to complete password resets Prompted to register methods or contact an administrator The registration campaign will proactively prompt affected users starting October 5, 2026. [Action Required / Recommendations] Action is required before November 9, 2026. Review authentication method registration coverage:Go to Microsoft Entra admin center → Authentication methods → User registration details Ensure all users (including admins) have at least one registered authentication method that satisfies your SSPR policy. Allow or enable the SSPR registration campaign to prompt users automatically. Plan fallback processes:Helpdesk-assisted registration Alternative onboarding scenarios for users unable to self-register Communicate this change to:IT admins and helpdesk teams Users (encourage registration via My Security Info) Learn more: Manage user authentication methods | Entra admin center Microsoft Q&A for Entra ID | Microsoft Security | Microsoft Entra | Microsoft Entra ID | Microsoft Learn Password policies and account restrictions in Microsoft Entra ID | Authentication | Microsoft Entra ID | Microsoft Entra | Microsoft Learn Prepopulate user authentication contact information for Microsoft Entra self-service password reset (SSPR) | Authentication | Microsoft Entra ID | Microsoft Entra | Microsoft Learn Register security information (My Security Info) Secure Future Initiative | Microsoft [Compliance Considerations] QuestionAnswer Does the change alter how existing customer data is processed, stored, or accessed?Yes. Directory attributes (such as phone/email) will no longer be used for SSPR unless explicitly registered as authentication methods. Does the change alter admin monitoring/reporting?Yes. Admins can monitor registration coverage via updated reporting in the Entra admin center. Does the change include admin controls?Yes. Admins control SSPR policies and registration requirements. -
UPDATED: Catalog search functionality might be unavailable or return incomplete results
MC1444442 · stayInformed · normal · Updated 08/03/2026 22:00
Services: Windows
Read message
UPDATED August 3, 2026, 2:56 PM PST: Resolution efforts for this issue were completed during the weekend of August 1, 2026, and search functionality in the Microsoft Update Catalog was returned to normal. July 31, 2026, 6:42 PM PST: We are working to restore search functionality in the Microsoft Update Catalog following an issue affecting Catalog search operations. Users might be unable to successfully search for software updates, drivers, and hotfixes. Users might also experience search failures, slower-than-expected response times, timeouts, or incomplete search results when using the Catalog website. Mitigation and recovery actions are currently in progress, and service availability is expected to improve as additional recovery efforts are completed. Customers experiencing this issue are advised to retry Catalog search operations later. We will provide more information as it becomes available. -
Microsoft Entra ID: Retirement of custom CSS positioning properties in custom branding
MC1435782 · planForChange · normal · Updated 07/31/2026 17:35
Services: Microsoft Entra
Read message
[What and Why] To align with Microsoft's Secure Future Initiative (SFI) and its focus on identity security and phishing resistance, Microsoft is enhancing Microsoft Entra custom branding to support more secure, reliable, and consistent sign in experiences. Beginning in October 2026, Microsoft Entra ID will retire support for custom CSS positioning properties used in custom branding. Full retirement of all custom CSS is planned for a future date, and additional notice will be provided before that change occurs. This update helps further reduce opportunities for deceptive or misleading sign in page layouts and supports trusted sign in experiences that better protect users from phishing attacks while maintaining brand customization capabilities. General Availability (Worldwide and GCC): Beginning in October 2026 and expected to complete by late November 2026 [Impact on Your Organization] Who is affected Administrators managing Microsoft Entra ID company branding Organizations currently using custom CSS positioning properties in company branding Organizations that do not use custom CSS positioning properties as of July 21, 2026, are not affected and will not be able to use these properties going forward Microsoft Entra External ID tenants are not affected Platforms/Services Microsoft Entra ID Custom branding for sign-in experiences (including company branding and branding themes) Web-based branded sign-in pages What will happen Existing tenants that currently use custom CSS positioning properties can continue using them until October 2026. Beginning on October 26, 2026, the affected positioning properties will no longer be honored and will stop functioning. Branding elements on branded sign-in pages such as logos, images, and text will remain visible but may revert to their default placement and appearance. There is no supported migration path or replacement for the retired positioning properties. Organizations that do not already use custom CSS positioning properties cannot create new dependencies on these properties. New Microsoft Entra ID tenants created after January 5, 2026, do not have custom CSS available for company branding. Microsoft will notify impacted customers directly in advance of the retirement. The following CSS properties are being retired: position (including top, right, bottom, left, and z-index) margin (including margin-top, margin-bottom, margin-left, and margin-right) transform opacity overflow filter pointer-events clip-path mix-blend-mode translate [Action Required/Recommendations] Action is required if your organization uses any of the retired positioning properties listed above. Recommended actions: Review your Microsoft Entra ID company branding configurations before October 26, 2026. Identify any usage of the retired CSS positioning properties. Remove or redesign branding customizations that depend on these properties. Validate your branded sign in experience after changes are made to ensure the layout remains acceptable. Communicate this upcoming change to identity administrators and support teams. To determine whether your tenant is using retired positioning properties: Sign in using a Global Administrator or Branding Administrator account. Use Microsoft Graph Explorer to retrieve your organization branding configuration. Review all configured branding localizations. Identify any references to the retired CSS positioning properties. Remove those properties before October 2026. Learn more: Configure your company branding | Fundamentals | Microsoft Entra | Microsoft Learn CSS template reference guide | Fundamentals | Microsoft Entra | Microsoft Learn Customize the sign-in experience for your application with branding themes | Fundamentals | Microsoft Entra | Microsoft Learn Microsoft Entra ID enhances security of branded sign-ins | Microsoft Entra Blog Science Future Initiative (SFI) | Microsoft [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
Updates to the Windows Insider Program web experience
MC1444160 · stayInformed · normal · Updated 07/31/2026 17:00
Services: Windows
Read message
When will this happen: The new Windows Insider experience rollout began in April 2026 and has recently fully reached all Windows Insider channels. Retail versions of Windows now also see the new WIP channel options. How this will affect your organization: The Windows Insider and Windows Insider Program documentation sites now have a redesigned web experience and updated content structure. Organizational environments that rely on Windows Insider builds for testing, validation, or early feature evaluation might experience changes in where and how to access related documentation, announcements, and guidance. This includes updates related to new preview builds, feature introductions, and deprecations. Use this information to start testing the recently announced Windows 11, version 26H2 via the Windows Insider Program. What you need to do to prepare: Review internal processes for monitoring WIP updates. Ensure awareness of the new web experience and updated documentation content locations. Update processes that depend on tracking feature lifecycle events to reflect the new blog-driven and documentation-based communication approach. Additional information See Our commitment to Windows quality for an overview of recent Windows Insider improvements and ongoing Microsoft quality initiatives. Windows Insider Blog Getting started with the Windows Insider Program Windows Insider Program documentation Windows Insider Program for Business documentation Windows Insider Program for Developers documentation -
(Updated) Microsoft Teams: Update the Teams mobile app to maintain Calendar functionality
MC1440980 · planForChange · normal · Updated 07/31/2026 16:34
Services: Microsoft Teams
Action required by: 10/01/2026 07:00
Read message
Updated July 31, 2026: We have updated the timeline and content. Thank you for your patience. [What and why] To ensure continued access to Calendar functionality in Microsoft Teams mobile, users must update the Teams mobile app to the latest version. This change helps maintain a reliable calendar experience on iOS and Android devices and ensures compatibility with ongoing Teams service updates. Teams admins can make some policy changes (see below) and extend EWS until April 2027. EWS will no longer work after that date. Refer to this link for guidance on updating the policy - Exchange Online EWS [Rollout schedule] Worldwide, GCC, GCC High, and DoD: Beginning early October 2026 (previously late October) and expected to complete early October 2026 (previously late October) [Impact on your organization] Who is affected All users who access Microsoft Teams from iOS or Android mobile devices Platforms and services Microsoft Teams Teams mobile app for iOS Teams mobile app for Android What will happen Users who are not running the latest version of the Microsoft Teams mobile app will not be able to access Calendar functionality in Teams mobile. Users must update to the latest Teams mobile app version available in the Apple App Store or Google Play Store to continue using Calendar functionality in Teams mobile. This change applies only to the Teams mobile app. No changes are being made to Teams Calendar functionality on web or desktop clients. [Action required and recommendations] Action required. Complete the following before October 2026: Confirm that users are running the latest Microsoft Teams mobile app version available in the Apple App Store or Google Play Store. Inform users that Calendar functionality in Teams mobile requires the latest app version and may not be available on older app versions. Encourage users to enable automatic app updates on their mobile devices. For managed devices, verify that mobile application management solutions are configured to deploy the latest Teams mobile app version. Communicate this change to mobile users and support teams. Ensure these minimum versions are in place before October 2026: For iOS - Please update to version 8.9.0 (build 8.9.77.2026092302) or higher. For Android - Please update to version 1416/1.0.0.2026122504 or higher Learn more Deprecation of Exchange Web Services in Exchange Online | Clients and mobile in Exchange Online | Exchange Online | Microsoft Learn Exchange Online EWS [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
Microsoft SharePoint Embedded: Update to driveItem.webUrl behavior
MC1442608 · planForChange · normal · Updated 07/29/2026 23:06
Services: SharePoint Online
Read message
[What and why] We are updating the behavior of the Microsoft Graph driveItem.webUrl property for content stored in SharePoint Embedded. After this change, driveItem.webUrl will return the URL used to open a file in a browser rather than being treated as a stable file location or identifier. Depending on the file type and your SharePoint Embedded configuration, the returned URL may be: A Microsoft 365 web viewer URL A SharePoint Embedded PDF viewer URL A redirect URL generated from your configured urlTemplate A Microsoft help page URL This update aligns driveItem.webUrl with its intended purpose as a browser launch URL. Applications that require a stable identifier for a file should use driveItemId, which remains the only unique and stable identifier for an item within a drive. The SharePoint Embedded documentation describes driveItem.webUrl as the URL used to launch supported files in Microsoft 365 experiences. [Rollout schedule] Targeted Release: Beginning in mid-August 2026 General Availability (Worldwide): Beginning in mid-February 2027 Temporary opt-out available until: August 17, 2026 Customers who opt out before August 17, 2026, will have an additional six months to transition to the new behavior. Temporary opt-out support ends February 22, 2027 After February 22, 2027, all customers will receive the updated driveItem.webUrl behavior. [Impact on your organization] Who is affected Organizations that develop, manage, or use SharePoint Embedded applications that rely on driveItem.webUrl as a permanent file location, stable URL, or file identifier Platforms and services SharePoint Embedded Microsoft Graph Microsoft 365 web viewers SharePoint Embedded PDF viewer What will happen After this change: Word, Excel, PowerPoint, and other supported Microsoft 365 file types will return a Microsoft 365 viewer URL. PDF files will return a SharePoint Embedded PDF viewer URL. Unsupported file types with a configured urlTemplate will return a redirect URL generated from that template. Unsupported file types without a configured urlTemplate will return a Microsoft help page URL. Applications are not expected to require changes if driveItem.webUrl is used only to open files in a browser. Your application may require updates if it: Stores driveItem.webUrl as a permanent file location. Uses driveItem.webUrl as a file identifier. Compares driveItem.webUrl values over time to determine file identity or location. Passes driveItem.webUrl to services that require a stable storage URL. Assumes driveItem.webUrl remains unchanged across file types, viewer support scenarios, or redirect configurations. [Action required and recommendations] Review how your SharePoint Embedded applications use driveItem.webUrl. No action is required if driveItem.webUrl is used only to open files in a browser. We recommend: Identify any application dependencies on driveItem.webUrl as a stable identifier or permanent URL. Update applications to use driveItemId when a stable item identifier is required. Review redirect behavior for unsupported file types. Configure urlTemplate if users should be redirected back to your application. Review: Configure redirect behavior Validate application behavior against the updated driveItem.webUrl experience before enforcement begins. Remove dependencies on the legacy driveItem.webUrl behavior before temporary opt-out support ends. Use driveItem.webUrl when your application needs a URL that opens the file in a browser. Use the driveItemId when you need a stable, unique reference to an item. Organizations that need additional migration time can temporarily retain the current behavior for a SharePoint Embedded container type by setting UseLegacyItemWebUrl to true. Review: Set-SPOContainerTypeConfiguration The temporary opt-out is intended only as a migration aid and will no longer be honored after February 22, 2027. Learn more Configure redirect behavior - Open Office files from your app | SharePoint | Microsoft Learn Set-SPOContainerTypeConfiguration | Microsoft.OnlineSharePoint.PowerShell | PowerShell | Microsoft Learn [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
90-Day Reminder: AD FS DKM container ACL hardening begins in October 2026
MC1442510 · stayInformed · normal · Updated 07/29/2026 21:03
Services: Windows
Read message
What and why Windows updates released in October 2026 will begin Enforcement mode for AD FS Distributed Key Manager (DKM) container ACL hardening. This change is designed to address the elevation of privilege vulnerability documented in CVE-2026-56155 by automatically remediating insecure DKM container ACL configurations on supported Windows Server versions. Organizations using Active Directory Federation Services (AD FS) should use the current Audit mode period to review DKM container permissions and identify potential compatibility issues before enforcement begins. Rollout schedule Enforcement mode begins with the October 2026 Windows security update. Impact on your organization Organizations using AD FS might experience changes to DKM container permissions when remediation is applied during Enforcement mode. Starting with the October 2026 update, remediation will run by default on supported Windows Server versions unless administrators explicitly opt out. Windows Server 2012 and Windows Server 2012 R2 require manual remediation and are not automatically remediated. Action required/recommendations Organizations using AD FS should: Install the July 2026 Windows security update or a later Windows update on AD FS servers. Review AD FS Admin event logs for Event ID 1132, which indicates that DKM container permissions require attention. Review and test remediation during the current Audit mode phase before Enforcement mode begins in October 2026. Review the guidance in: CVE-2026-56155: AD FS Distributed Key Manager container ACL hardening. Compliance considerations No compliance considerations are identified. Review as appropriate for your organization. -
The July 2026 Windows non-security preview update is now available
MC1441670 · stayInformed · normal · Updated 07/28/2026 21:20
Services: Windows
Read message
The July 2026 non-security preview update is now available for Windows 11, versions 26H1, 25H2, and 24H2. Information about the contents of this update is available in the release notes, which are accessible from the Windows 11 update history page. To learn more about the different types of monthly quality updates, see Understanding Windows monthly updates. Looking to explore upcoming features and improvements in Windows 11? Check the Windows roadmap. It includes what’s coming to the Windows Insider Program, what's gradually rolling out, and what's generally available. Highlights for the Windows 11, version 25H2 update: This update adds Voice Isolation to Voice Access, helping it better recognize your voice by reducing interference from other speakers and background noise. Windows Hello Enhanced Sign-in Security (ESS) now supports peripheral fingerprint sensors. Taskbar notification badges for Widgets now use your Windows accent color instead of appearing red, helping reduce unnecessary attention-grabbing alerts. File sizes in the Details view now display using appropriate units (KB, MB, GB) instead of KB-only, making them easier to understand at a glance. New touchpad gesture controls let you adjust scroll and zoom speed, and enable accelerated scrolling for faster navigation through long documents. For instructions on how to install this update, see the KB article for your operating system listed below: Windows 11, version 26H1: KB5101681 Windows 11, versions 25H2 and 24H2: KB5101684 Note: With recent and upcoming Windows updates over the next few months, a limited number of consumer and business devices might experience one additional restart during installation. This one‑time restart occurs after a Secure Boot certificate update is applied as part of the Secure Boot update process. -
(Updated) Microsoft Teams: AI meeting recap without transcript to meet compliance policies
MC1275312 · planForChange · normal · Updated 07/27/2026 17:04
Services: Microsoft Teams
Read message
Updated July 27, 2026: We have updated the timeline. Thank you for your patience. [Introduction] Recap without saving transcript provides an alternative now for Copilot users to generate a meeting summary using live meeting context, in case where saving a meeting transcript or recording is not preferred or allowed. This capability is intended for scenarios where organizations want AI‑generated recaps but have policies that limit or prohibit the retention of transcripts or recordings. When disabled, no AI recap is generated. Existing Copilot licensing and tenant‑level AI controls continue to apply. This feature will be available to users with an M365 Copilot (Premium) license across platforms, including desktop (Windows and Mac), web, and mobile. This message is associated with Microsoft 365 Roadmap ID 558286. [When this will happen:] Targeted Release: We will begin rolling out early October 2026 (previously mid-August) and expect to complete by mid-October 2026 (previously late August). General Availability (Worldwide): We will begin rolling out mid-October 2026 (previously late August) and expect to complete by late October 2026 (previously late September). [How this affects your organization:] Who is affected: Microsoft Teams meeting organizers and participants with an M365 Copilot (Premium) license Microsoft 365 administrators managing Copilot and AI controls What will happen: Teams admin center - Tenant admins will have control to opt in or out for AI features (e.g. Copilot, Intelligent Recap) for the meeting under the tenant. This feature is controlled by AI toggle/setting in the admin center. If AI is disabled at the tenant level, this experience is not available. Meeting options (before meeting) - Meeting organizers with a Copilot license can enable or disable Recap without saving transcript in meeting options under Copilot and other AI before the meeting In-Meeting controls (during meeting) – Meeting organizers with a Copilot license can enable or disable Recap without saving transcript anytime during the meeting via the AI toggle (appears at top-left). Participants can see whether AI is being turned on/off, while participants cannot change this setting. Post-meeting AI summary - When enabled, Intelligent Recap will generate an AI summary even if recording and transcription are not turned on. Meeting attendees with Copilot license can view the AI summary after the meeting. No transcript or recording is saved as part of this experience. Storage – When enabled, a doc will be stored in organizer’s OneDrive for default 120days, and it will be configurable in admin center for longer/shorter days as needed. Deletion – For post-meeting AI summary, organizer can choose to delete the content from the Recap page, and it will result in the deletion of the doc in organizer’s OneDrive, and vice versa. [What you can do to prepare:] Review your organization’s AI and Copilot governance policies to determine whether this experience aligns with your compliance posture. If you want to opt out, disable the AI toggle in your tenant settings to prevent Recap without saving transcript from being used. Update internal guidance and helpdesk documentation to reflect that meeting recaps may be generated without recordings or transcripts. Communicate this change to meeting organizers, especially in regulated environments. [Compliance considerations:] Compliance area Explanation AI/ML interaction with customer data Copilot generates AI-based meeting recaps using live meeting context even when recording and transcription are not enabled. No meeting transcript or recording is saved. New way for users to interact with generative AI Users can receive AI-generated Intelligent Recap without starting or saving a meeting recording or transcript. Admin controls availableThis capability is governed by the existing tenant-level AI toggle. Disabling AI prevents Recap without saving transcript from being used. User enable/disable capability Meeting organizers can enable or disable the feature before the meeting, and organizers or participants with Copilot licenses can toggle it during the meeting. -
MDO Encrypted email attachment protection
MC1440701 · planForChange · normal · Updated 07/27/2026 16:31
Services: Microsoft Defender XDR
Read message
What and Why: Organizations commonly use encrypted or password-protected attachments to securely share sensitive information through email. However, when Microsoft Defender for Office 365 cannot obtain the attachment password during scanning or detonation, the content cannot be fully analyzed for threats. To help organizations reduce risk from unscanned content, Microsoft is introducing a new opt-in setting in Safe Attachments policies. This setting allows administrators to automatically quarantine email messages that contain password-protected attachments when Microsoft Defender for Office 365 cannot complete scanning or detonation. This enhancement provides administrators with greater control over potentially risky content while preserving business workflows through controlled release options. Rollout Schedule: Worldwide: Early August 2026 through Late August 2026 GCC: Late August 2026 through Late September 2026 GCC High: Late August 2026 through Late October 2026 DoD: Late August 2026 through Late October 2026 Impact on Your Organization: Who is affected: Administrators managing Safe Attachments policies. Security operations teams responsible for quarantine management. Users who receive password-protected email attachments. Platforms/Services: Microsoft Defender for Office 365 Safe Attachments Quarantine Advanced Hunting Exchange Online What will happen: This feature is off by default and requires administrator opt-in. Administrators can configure Safe Attachments policies to quarantine messages when password-protected content cannot be scanned or detonated. Organizations can pilot the feature using a separate scoped Safe Attachments policy. Users can self-release eligible messages by providing the attachment password. A just-in-time detonation is performed before release. Security administrators can release quarantined messages without requiring the attachment password. Supported file categories include ZIP, GZIP, 7z, RAR, PDF, and Microsoft Office file formats. Selected file categories can be excluded from protection. Important: Users should only enter the attachment password. Users should never enter account credentials, banking passwords, or unrelated passwords. Users should only release expected messages from validated senders. Unexpected protected email messages should be escalated to SecOps. SecOps teams: EmailAttachmentInfo | where AdditionalFields contains "IsPasswordProtectedItem" Action Required/Recommendations: No action is required unless you want to use this capability. Review Safe Attachments policies. Consider a pilot deployment. Review quarantine release procedures. Update internal documentation. Communicate the change to support and helpdesk teams. Educate users on appropriate use of attachment passwords during message release. Review Microsoft Defender for Office 365 documentation. Microsoft Defender for Office 365 overview | Microsoft Learn Safe Attachments - Microsoft Defender for Office 365 | Microsoft Learn Set up Safe Attachments policies in Microsoft Defender for Office 365 - Microsoft Defender for Office 365 | Microsoft Learn Manage quarantined messages and files as an admin | Microsoft Defender for Office 365 | Microsoft Learn Compliance considerations: The change modifies how password-protected email attachments may be processed and accessed when organizations enable the feature. Administrators gain new controls through Safe Attachments policies and can identify affected content using Advanced Hunting. No other compliance considerations were identified. -
Admin control for single sign-on prompts in Windows
MC1438491 · stayInformed · normal · Updated 07/24/2026 21:05
Services: Windows
Read message
What and why Microsoft has introduced a new administrative control for single sign-on (SSO) prompts on Windows. A new registry-based policy now allows IT admins to automatically accept SSO permissions on managed devices, removing this prompt for users. This control applies only to managed devices with Microsoft Entra ID accounts running Windows 11, version 24H2 or 25H2. Rollout schedule Available now. Impact on your organization Organizations that manage Windows devices should review whether this control aligns with existing authentication policies and sign-in experiences. Depending on configuration choices, SSO prompt behavior might differ from the current experience on managed devices. Action required/recommendations No immediate action is required. Organizations that want to adopt this control should: Review the announcement: Now available: Admin control for SSO prompts in Windows. Evaluate whether to adopt the new control in your environment. Test the configuration on a representative set of managed devices before broader deployment. Compliance considerations No compliance considerations are identified. Review as appropriate for your organization. -
UPDATED: Azure outage affecting Windows Updates and related services
MC1437457 · stayInformed · normal · Updated 07/23/2026 21:03
Services: Windows
Read message
UPDATED 1:45 PM PST: Resolution efforts are complete at this time, and Windows services are expected to be back to normal. Notices related to this issue have been moved to history sections across Azure status pages. At this time, Windows Update is expected to update and download as normal, and functionality has been restored across Microsoft Update Catalog, Microsoft Store, and Windows Server Update Services (WSUS). 11:15 AM PST: An Azure outage is presently affecting several Windows services. Impacted services include Windows Update and the Microsoft Update Catalog. Users might also experience issues accessing or downloading content from the Microsoft Store and Windows Server Update Services (WSUS). Users might encounter delays, failures, or timeouts with downloads or access to these services. Additional related services might also be affected. Recovery efforts are underway, and some traffic is being successfully redirected. Service availability is expected to improve as additional recovery actions are completed. Customers experiencing this issue are advised to retry Windows Update and related service operations later. We will provide more information as it becomes available. You can also monitor status updates at Microsoft 365 service health status. -
Out-of-band update to address Windows update issue affecting some devices with Intel IPF driver
MC1432461 · stayInformed · normal · Updated 07/18/2026 19:20
Services: Windows
Read message
Microsoft has released an out-of-band (OOB) update today to address an issue affecting a limited number of Dell devices with an Intel Innovation Platform Framework (Intel IPF) driver that could cause changes in performance, power consumption, or system behavior after installing recent Windows updates. This OOB update is a cumulative update, so you do not need to apply any previous updates before installing it. Devices affected by this issue and that were temporarily prevented from receiving the July 2026 security update (KB5101650) can now install this OOB update, which includes all improvements from previous security and non-security updates, along with this additional fix. This OOB update is only recommended for devices affected by this issue. If your device is not affected, no action is required. For complete guidance and installation instructions, see the relevant KB articles: Windows 11, versions 25H2 and 24H2: KB5121767 Windows 11 Enterprise LTSC 2024: Hotpatch KB5121768 IT administrators using Microsoft Intune can expedite deployment of this update. For guidance, see Expedite Windows quality updates in Microsoft Intune. Devices managed by Windows Autopatch with hotpatch updates enabled (default) will receive this update automatically. -
90-Day Reminder: Windows Server 2022 will reach end of mainstream support on October 13, 2026
MC1429856 · stayInformed · normal · Updated 07/16/2026 16:58
Services: Windows
Read message
On October 13, 2026, Windows Server 2022 will reach end of mainstream support. The October 2026 security update will be the last mainstream support update available for this version. After this date, Windows Server 2022 will transition to extended support, which includes security updates at no additional cost, and will continue to receive monthly security updates through October 14, 2031. For more information, see the Fixed Lifecycle Policy. Windows Server 2025 is now the latest Long-Term Servicing Channel (LTSC) release for Windows Server. To help keep your environment protected and supported, plan to upgrade to Windows Server 2025 for full mainstream support. To download a free 180-day evaluation, visit the Microsoft Evaluation Center. Evaluate upgrade options and begin deployment testing early to help ensure a smooth transition. For detailed information, see the Windows Server 2022 lifecycle page. For information about servicing timelines and lifecycle, see Windows Server release information, Lifecycle FAQ - Windows Server, and Microsoft Lifecycle Policy search tool. -
(Updated) Retirement of -Credential parameter when connecting to Exchange Online PowerShell
MC1248389 · planForChange · normal · Updated 07/15/2026 21:15
Services: Exchange Online
Read message
Updated July 15, 2026: We have updated the timeline. Thank you for your patience. [Introduction] Microsoft is retiring the -Credential parameter used when connecting to Exchange Online PowerShell. Starting with module versions released in December 2026 and later, the -Credential parameter will be removed from both Connect-ExchangeOnline and Connect-IppsSession cmdlets. Organizations using this parameter in automation scripts must migrate to a supported authentication method before that date. This change improves security by moving away from legacy authentication methods that do not support modern protections such as multifactor authentication (MFA). [When this will happen:] The -Credential parameter will be removed from Connect-ExchangeOnline and Connect-IppsSession cmdlets in Exchange Online PowerShell module versions released beginning end of year 2026 (previously July). A separate server-side retirement of the underlying authentication flow is planned for a later date and will be communicated in advance. [How this affects your organization:] Who is affected: Microsoft 365 administrators using Exchange Online or Security & Compliance PowerShell Organizations with automation scripts that use the -Credential parameter What will happen: If your organization uses the -Credential parameter in PowerShell scripts or automation workflows connecting to Exchange Online or Security & Compliance PowerShell, those scripts will break when you update to an Exchange Online PowerShell module version released beginning December 2026. No impact if your organization does not use the -Credential parameter What you can do to prepare: If you are using the -Credential parameter, begin migrating your scripts now. Do not wait until December 2026. Choose the appropriate alternative based on your scenario: Interactive admin access: Switch to modern authentication with MFA. Learn more: Connect to Exchange Online PowerShell. Automation outside Azure: Use app-only authentication (certificate-based). Learn more: App-only authentication for unattended scripts in Exchange Online PowerShell and Security & Compliance PowerShell. Automation within Azure: Use managed identity authentication (no secrets required). Learn more: Use Azure managed identities to connect to Exchange Online PowerShell. Review internal documentation and communicate changes to admins If you are not using the -Credential parameter, no action is required. Additional information This change is currently client-side only and will not take effect automatically. Your existing scripts will continue to work if you continue using an Exchange Online PowerShell module version released before December 2026. The -Credential parameter will only be removed when you upgrade to a module version released in December 2026 and later. A separate server-side retirement of the Credential parameter authentication flow is planned for a later date. When that occurs, the -Credential parameter will stop functioning even on older module versions. Microsoft will communicate that timeline separately and provide advance notice before any service-side changes take effect. We strongly recommend migrating proactively rather than waiting, to avoid disruption when either change occurs. If you have questions or concerns, contact Microsoft Support or leave a comment on the Exchange Team Blog post. [Compliance considerations:] Compliance area Impact Conditional Access policies Retiring the -Credential parameter removes use of the ROPC authentication flow and enables enforcement of Conditional Access and multifactor authentication for Exchange Online PowerShell connections. -
90-Day Reminder: Windows 11, version 24H2 and Windows 10 LTSB 2016 reaching end of updates on October 13, 2026
MC1428757 · stayInformed · normal · Updated 07/15/2026 16:58
Services: Windows
Read message
On October 13, 2026, Windows 11, version 24H2 Home and Pro editions, and Windows 10 Enterprise LTSB 2016 will reach end of updates. After this date, devices running these editions will no longer receive monthly security and non-security preview updates containing protections from the latest security threats. We recommend updating devices running Windows 11, version 24H2 Home and Pro editions to Windows 11, version 25H2 to continue receiving monthly security and quality updates. Enterprise and Education editions remain supported until October 12, 2027. For more information, see the How to get the Windows 11 2025 Update video. For devices running Windows 10 Enterprise LTSB 2016, we recommend updating to the latest LTSC release, Windows 11 Enterprise LTSC 2024. Extended Security Updates (ESU) are also available for organizations that need additional time to complete their transition. For more information about product lifecycle dates, see Windows 11 release information, Windows 10 release information, and Lifecycle FAQ - Windows. -
The July 2026 Windows security update is now available
MC1427603 · stayInformed · normal · Updated 07/14/2026 22:00
Services: Windows
Read message
The July 2026 security update is now available for all supported versions of Windows. We recommend that you install these updates promptly. For more information about the contents of this update, see the release notes, which are accessible from the Windows 11 update history page. To learn more about the different types of monthly quality updates, see Understanding Windows monthly updates. Highlights for the Windows 11, version 25H2 update: This security update includes improvements that were part of update KB5095093 (released June 23, 2026). This update addresses an issue that affects certain third-party apps that use OLE Automation to interact with Microsoft Office. This update changes hotkey unregister and cleanup behavior. This update introduces a security hardening change that enforces TDI transport registration requirements. This update upgrades the curl tool in Windows to version 8.21.0 and includes security improvements that help protect your device. Note: The July 2026 security update for Windows 11, version 25H2 and Windows 11, version 24H2 (KB5101650) is not available for a limited number of Dell devices with Intel processors due to an incompatibility reported by Dell that can potentially cause unexpected shutdowns, poor performance, increased heat, and battery drain. We are working together with Dell to prevent the affected models from experiencing the issue and plan to release a resolution for affected devices in the coming days. Short on time? Watch the Windows 11 release notes video for this month’s tips. For instructions on how to install this update, see the KB article for your operating system listed below: Windows 11, version 26H1: KB5101649 Windows 11, versions 25H2 and 24H2: KB5101650 Windows 11, version 23H2: KB5099414 Windows 11 Enterprise LTSC 2024: Baseline KB5101650 Windows 10, versions 22H2 and 21H2: KB5099539 Windows 10 Enterprise LTSC 2019 and Windows Server 2019: KB5099538 Windows 10 LTSB 2016 and Windows Server 2016: KB5099535 Windows Server 2025: KB5099536 Windows Server 2025 Datacenter: Azure Edition: Baseline KB5099536 Windows Server 2022: KB5099540 Windows Server 2022 Datacenter: Azure Edition: Baseline KB5099540 Windows Server 2012 R2: KB5099444 Windows Server 2012: KB5099445 Note: With recent and upcoming Windows updates over the next few months, a limited number of consumer and business devices might experience one additional restart during installation. This one‑time restart occurs after a Secure Boot certificate update is applied as part of the Secure Boot update process. -
The July 2026 Scan Cab is available
MC1427862 · stayInformed · normal · Updated 07/14/2026 21:20
Services: Windows
Read message
IMPORTANT: This notice only affects environments where Scan Cab is used to check for update compliance. What and why: The July 2026 Scan Cab was made available at 2:00 PM PDT today, July 14, 2026. The Scan Cab can help determine whether a Windows device needs to install necessary security updates released by Microsoft without first connecting to the Windows Update service. Rollout schedule: The July 2026 Scan Cab was made available at 2:00 PM PDT today, July 14, 2026. Who is affected: The Wsusscn2.cab file is a cabinet file that is signed by Microsoft and contains information about Microsoft security-related updates. Devices that aren't connected to the Internet can be scanned to see whether these security-related updates are present or required. The Wsusscn2.cab file doesn't contain the security updates themselves so you must obtain and install any needed security-related updates through other means. What will happen: You can download and deploy the July 2026 Scan Cab via the usual processes. For detailed guidance, see the Additional information section below. No action is required on environments where Scan Cab is not employed. However, please note that there might be non-Microsoft applications which utilize Scan Cab. Review the documentation for any software and update deployment tools used in your organization to understand if this is applicable in your environment. Additional information: Updated Scan Cab: Download the new Scan Cab here Announcing a smaller WSUS Scan Cab: Learn more about WSUS and the Scan Cab process Using WUA to Scan for Updates Offline: Windows Update Agent (WUA) can be used to scan computers for security updates without connecting to Windows Update WSUS and the Catalog Site: The Catalog Site used by WSUS to import updates and drivers -
(Updated) Notice: The July 2026 Scan Cab for Microsoft updates is delayed
MC1427626 · stayInformed · normal · Updated 07/14/2026 21:20
Services: Windows
Read message
Updated July 14, 2026: The July 2026 Scan Cab is now available as of 2:00 PM PDT. Note: This notice only affects environments where Scan Cab is used to check for Microsoft update compliance. What and why: The Scan Cab for the July 2026 Microsoft security updates is currently delayed and has not yet been released. Rollout schedule: We estimate it will be released later today, and we will communicate an update as more information becomes available. Thank you for your patience. Who is affected: IT administrators who rely on Scan Cab to check for update compliance can monitor our communications for updates. What will happen: Updates on the availability of this month's Scan Cab will be communicated as new information becomes available. Additional information: Learn more about the Scan Cab process: Announcing a smaller WSUS Scan Cab Use Windows Update Agent (WUA) to scan computers for security updates without connecting to Windows Update: Using WUA to Scan for Updates Offline - Win32 apps Documentation on the Catalog Site used to import updates and drivers: WSUS and the Catalog Site -
Microsoft Purview compliance portal: Purview Information Protection | Classifier Simulation Mode (Health Monitoring)
MC1185445 · stayInformed · normal · Updated 07/14/2026 19:24
Services: Microsoft Purview
Read message
Updated July 14, 2026: We have updated the timeline. Thank you for your patience. [Introduction] Microsoft Purview is introducing Classifier Simulation Mode, the first phase of the broader Classifier Health Monitoring Platform. This new capability allows admins to test and validate custom classifiers on production data before publishing. Simulation Mode enables admins to optimize classifier logic before deployment, helping in reducing false positives, scanning latency, and noisy matches. Admins will access simulation controls and classifier health insights directly in the Microsoft Purview compliance portal, making it easier to monitor and improve classifier performance in one centralized location. This message is associated with Roadmap ID 523201. [When this will happen:] Public Preview: Rollout begins mid-October 2026 (previously late June), completes by early November 2026 (previously end of July). General Availability (Worldwide): Rollout begins late November 2026 (previously end of July), completes late November 2026 (previously end of August). [How this affects your organization:] Who is affected: Admins managing Microsoft Purview Information Protection and custom sensitive information types (SITs). What will happen: By default, the feature will be available to all tenants. Admins will see a new option to simulate a custom classifier before publishing. Simulation is optional — admins can choose to simulate or publish directly. Classifiers published without simulation will still be monitored for performance and flagged if unhealthy. Classifier health insights will be available in the Microsoft Purview compliance portal, helping admins identify and remediate inefficient classifiers. Inefficient classifiers may be automatically disabled to maintain system performance. [What you can do to prepare:] Admins can begin using Simulation Mode once available; no onboarding or training is required. Once the feature is available:Review classifier health insights in the compliance portal. Monitor any SITs flagged as unhealthy and adjust logic as needed. Consider simulating classifiers before publishing to reduce risk of false positives or performance issues. [Compliance considerations:] QuestionExplanation Does the change alter how existing customer data is processed, stored, or accessed?Classifiers will be simulated on production data, but not published, allowing analysis without altering data classification outcomes. Does the change introduce or significantly modify AI/ML or agent capabilities that interact with or provide access to customer data?Introduces classifier health monitoring logic that evaluates classifier performance and flags inefficiencies. Does the change modify how admins can monitor, report on, or demonstrate compliance activities?Adds new health insights and monitoring capabilities for custom classifiers in the compliance portal. Does the change include an admin control and, can it be controlled through Entra ID group membership?Simulation and publishing options are available to admins; access can be managed via role-based permissions. -
Enforcement phase for Kerberos RC4 protections begins with the July 2026 Windows security update
MC1427604 · planForChange · normal · Updated 07/14/2026 17:12
Services: Windows
Read message
What and why Windows updates released in July 2026 introduce the enforcement phase of protections designed to address a Kerberos information disclosure vulnerability (CVE‑2026‑20833). This phase completes the transition away from RC4-based Kerberos tickets by removing Audit mode and leaving Enforcement mode as the only supported behavior for Kerberos RC4 usage on Windows domain controllers. With the July 2026 security update installed, domain controllers enforce updated behavior for service account ticket issuance. RC4-based Kerberos tickets are restricted under this enforcement model, and AES-based encryption is expected for supported configurations. This change helps reduce reliance on legacy encryption methods and aligns Kerberos authentication with current security standards. Rollout schedule This change is effective beginning with the July 2026 security update. Impact on your organization Organizational environments that still depend on RC4-based Kerberos service tickets might experience authentication failures when requesting service tickets after installing the July 2026 security update. Applications, services, or devices that rely on legacy encryption configurations or explicitly defined RC4 usage are most likely to be affected. Environments previously operating in Audit mode no longer have the ability to revert to that mode once enforcement is in place. Workloads that previously completed Kerberos authentication without updated encryption configurations might no longer function as expected. Action required/recommendations Confirm that all service accounts and dependent applications support AES-based Kerberos encryption. Review and remediate any remaining RC4 dependencies identified during prior audit phases. Monitor the System event log for Kerberos-related events to identify authentication failures or misconfigured accounts. Validate interoperability with non-Windows Kerberos implementations and services. Review How to manage Kerberos KDC usage of RC4 for service account ticket issuance changes related to CVE‑2026‑20833. Audit mode and the RC4DefaultDisablementPhase rollback setting are removed beginning with the July 2026 security update. If RC4 must be retained for specific services, explicit configuration is still possible, but it leaves those scenarios vulnerable to CVE‑2026‑20833 and should be used only as a temporary measure. Compliance considerations No compliance considerations are identified. Review as appropriate for your organization. -
Microsoft Entra ID: Retirement of Custom Controls in Conditional Access and migration to External MFA
MC1422061 · planForChange · normal · Updated 07/09/2026 21:50
Services: Microsoft Entra
Action required by: 04/30/2027 07:00
Read message
[What and Why] Microsoft Entra ID is retiring Custom Controls in Conditional Access and replacing them with External MFA, a generally available, standards-based integration for third-party multifactor authentication (MFA) providers. External MFA provides a more modern, supported, and standardized authentication experience while enabling organizations to continue using approved third-party MFA solutions with Conditional Access policies. This change helps improve long-term supportability, security, and interoperability. [Rollout Schedule] Key dates: September 2026: Administrators will no longer be able to create new Custom Controls or modify existing Custom Controls in Conditional Access policies. May 2027: Custom Controls will be fully retired and no longer supported. [Impact on Your Organization] Who is affected Organizations currently using Custom Controls in Microsoft Entra Conditional Access policies. Administrators responsible for Microsoft Entra ID and Conditional Access management. Organizations not using Custom Controls are not affected and do not need to take action. Platforms/Services Microsoft Entra ID Conditional Access Third-party MFA providers integrated with Microsoft Entra ID What will happen Existing Custom Controls will continue to function until retirement in May 2027. Beginning in September 2026, administrators will no longer be able to create new Custom Controls or modify existing Custom Controls. After retirement in May 2027, Custom Controls will no longer be supported. Organizations using Custom Controls must migrate affected Conditional Access policies to External MFA before retirement. No impact is expected for organizations that do not use Custom Controls. [Action Required] If your organization uses Custom Controls, action is required before May 2027. Recommended actions: Review your Conditional Access policies and identify any policies that use Custom Controls. Configure your third-party MFA provider as an External Authentication Method. Update affected Conditional Access policies to use the standard Require multifactor authentication grant control. Validate authentication flows and confirm successful migration to External MFA. Remove all Custom Control references after migration is complete. Review the migration guidance: Migrate from custom controls to external multifactor authentication Consider communicating this change to your identity, security, and help desk teams to ensure migration activities are completed before the retirement date. Learn more: Migrate from custom controls to external multifactor authentication | Conditional Access | Microsoft Entra ID | Microsoft Entra | Microsoft Learn [Compliance Considerations] QuestionAnswer Does the change modify, interrupt, or disable Conditional Access policies?Yes. Organizations currently using Custom Controls must update affected Conditional Access policies to use External MFA before Custom Controls are retired. Does the change add any integration to third-party software products?Yes. External MFA provides a standards-based integration model for third-party MFA providers. Does the change include an admin control and can it be controlled through Entra ID group membership?Yes. The configuration and migration are managed by administrators through Microsoft Entra ID and Conditional Access policy management. -
Windows Office Hours: July 16, 2026
MC1421755 · stayInformed · normal · Updated 07/09/2026 17:03
Services: Windows
Read message
If you are an IT admin with questions about managing and updating Windows, we want to help. Every third Thursday of the month, we host a live chat-based event on the Tech Community called Windows Office Hours. Members of the Windows, Microsoft Intune, Windows Autopilot, Windows Autopatch, and Windows 365 engineering teams will be standing by to answer your questions. Want to attend the July 16 session of Office Hours? Add it to your calendar and select Attend on the event page to let us know you're coming. There is no video or live meeting component. Simply visit the event page, sign in to the Tech Community, and leave your questions in the Comments section. You can also bookmark https://aka.ms/Windows/OfficeHours for upcoming dates (and the ability to add this event to your calendar). We look forward to helping you. -
(Updated) Exchange Online: Retirement of legacy TLS versions for POP and IMAP connections
MC1293480 · planForChange · normal · Updated 07/07/2026 20:14
Services: Exchange Online
Action required by: 07/31/2026 07:00
Read message
Updated July 7, 2026: We have updated the timeline. Thank you for your patience. [Introduction] We are retiring support for legacy Transport Layer Security (TLS) versions for POP3 and IMAP4 connections to Exchange Online. This change improves security and aligns with current industry standards. TLS 1.0 and TLS 1.1 are no longer considered secure. Most modern email clients already use TLS 1.2 or later. [When this will happen] Rollout start: August 1, 2026 Rollout end: December 31, 2026 The rollout will occur gradually worldwide. [How this affects your organization] Who is affected Microsoft 365 tenants using POP3 or IMAP4 with Exchange Online Admins managing email clients, applications, or devices that use POP or IMAP What will happen POP3 and IMAP4 connections will require TLS 1.2 or later. Connections using TLS 1.0 or TLS 1.1 will fail. Modern email clients are not expected to be affected. Legacy applications or devices may stop connecting. Custom or embedded systems may require updates. [What you can do to prepare] If you use POP or IMAP with Exchange Online, ensure email clients, applications, and libraries support TLS 1.2 or later and do not use legacy TLS endpoints. Review all POP and IMAP clients in your organization. Confirm support for TLS 1.2 or later. Update or replace clients that rely on legacy TLS. Validate TLS support with third‑party vendors. Inform helpdesk and operations teams. No action is required if all connections already use TLS 1.2 or later. [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
Windows settings backup policy is becoming a new default
MC1418203 · stayInformed · normal · Updated 07/06/2026 21:05
Services: Windows
Read message
What and why Starting with Windows 11, version 26H2, the default behavior of the Windows settings backup policy will shift from disabled to enabled. Default-on applies only to eligible devices and only when you haven't explicitly set the policy. Explicit enablement and disablement settings are always honored. Restore behavior is unchanged: it remains admin-controlled and isn’t enabled by default. This change makes backup a baseline resilience capability, so you can restore users' apps, settings, and Microsoft Store app list easier after a device reset, replacement, or upgrade. You keep full control through Microsoft Intune, Group Policy, or other MDM solutions. Rollout schedule This change is currently available for preview via Windows Insider Program (Experimental channel). The default-on behavior takes effect when Windows 11, version 26H2 reaches general availability in the second half of 2026. Devices originally running Windows 11, version 26H1 will receive the same default-on treatment starting with the following feature update. Impact on your organization Default-on applies only to devices that meet all of the following criteria: Running Windows 11, version 26H2 or later In countries or regions not regulated by the EU Digital Markets Act (DMA) With the backup policy in a Not Configured state under Windows settings backup and restore Devices with an explicitly configured backup policy—enabled or disabled—are unaffected. Restore behavior remains admin-controlled and isn’t enabled by default. Users can still turn off backup through the Windows Backup app or Windows settings page. Action required Review your current backup policy state ahead of Windows 11, version 26H2 deployment and decide your intended behavior: To use backup (recommended): No action required. The default takes effect for eligible devices. To opt out: Explicitly disable the backup policy through Microsoft Intune, Group Policy, or your mobile device management (MDM) provider. If you explicitly disable the policy, your setting takes precedence over the default. To enable the restore behavior: Configure the restore policy separately. Default-on for backup doesn’t enable the restore behavior. No action is required if your organization is in a DMA region, in a sovereign or restricted cloud environment, or if you have already explicitly configured the backup policy. Additional information Windows settings backup becoming a new resilience baseline Windows Backup for Organizations overview (Microsoft Learn) How to configure backup and restore policies in Microsoft Intune Windows Insider Blog Windows Insider release notes -
Secure Boot Office Hours in July for virtualized and OEM environments
MC1418035 · stayInformed · normal · Updated 07/06/2026 17:01
Services: Windows
Read message
What and why If you are an IT admin working with Secure Boot, join two upcoming Office Hours sessions focused on virtualized environments and OEM scenarios to help you prepare for certificate updates. Microsoft engineering teams will be available to answer your questions and provide guidance. Add the sessions to your calendar and attend via the event pages. Can’t attend live? Post your questions in advance and review responses afterward. Rollout schedule July 8: Secure Boot Office Hours for virtualized environments July 15: OEM Secure Boot Office Hours Impact on your organization These sessions can help you better understand how Secure Boot certificate updates apply to your environment and what steps to take to maintain trusted boot integrity and avoid potential disruption. Action required We encourage you to join one or both sessions to get answers to your questions and plan for Secure Boot certificate updates. See the links above to attend the events and participate in the discussion with Microsoft experts. -
Customize the Start menu with updated policies
MC1412655 · stayInformed · normal · Updated 07/02/2026 17:05
Services: Windows
Read message
What and why The updated Start menu is now rolling out to organizations using Windows 11. It brings the “All \[apps\]” section to the top level of the Start menu with new views (category and grid). The size of the Start menu is dynamic to the user's device. Additionally, updated policies now make it easier for you to configure Start. Rollout schedule Start menu began gradual rollout in October 2025 to general audiences. The rollout to organizations began in June 2026. Impact on your organization Windows 11 devices began updating to show the new Start menu. In addition to the existing policies, the following policies give you more control: HideCategoryView: This is a net new policy that you can apply to the updated Start menu design. Turn off the new category view in the "All \[apps\]" section, so devices show the grid view by default. Note: If you already have HideAppList enabled, you don't need to enable HideCategoryView since devices won't have the "All \[apps\]" section. ConfigureStartPins: You can apply this policy to all versions of Start. It only includes an update. When the optional applyOnce flag is set, the pinned layout is applied only during initial provisioning. After that, users can customize their Start menu without losing those changes during routine policy refreshes. This addresses a previous issue where users’ pinned sections could be unexpectedly refreshed. Action required/recommendations Review the new policies and make changes accordingly: Review policies in Start Policy CSP. Learn more at Start policy settings. Learn more about HideCategoryView Start Policy CSP. Learn more about ConfigureStartPins Start Policy CSP. Compliance considerations No compliance considerations are identified. Review as appropriate for your organization. -
Remote Event Receivers in SharePoint Online will be retired
MC1411726 · planForChange · normal · Updated 07/01/2026 23:14
Services: SharePoint Online
Read message
[What and Why:] Microsoft is retiring Remote Event Receivers (RERs) in SharePoint Online as part of the Azure ACS retirement and ongoing modernization of the SharePoint extensibility platform. Remote Event Receivers registered using Azure ACS stopped functioning correctly on April 2, 2026. Remote Event Receivers registered using Microsoft Entra applications will continue to function until July 1, 2027, after which all Remote Event Receivers will stop working. Microsoft recommends migrating affected solutions to SharePoint webhooks or Microsoft Graph change notifications. [Rollout Schedule:] April 2, 2026: Azure ACS-registered Remote Event Receivers stopped functioning correctly. July 1, 2027: All remote event receivers, including those registered using a Microsoft Entra application, will stop working. No RER will fire events after this date. [Impact on Your Organization:] Who is affected: Organizations using SharePoint Online Remote Event Receivers. Developers, solution owners, and third-party vendors supporting SharePoint customizations. Platforms/Services: SharePoint Online Microsoft Entra ID applications SharePoint Add-ins SharePoint webhooks Microsoft Graph change notifications What will happen: Azure ACS-based Remote Event Receivers have already stopped functioning correctly. All remaining Remote Event Receivers will stop firing events after July 1, 2027. Applications and workflows that depend on Remote Event Receivers will no longer receive SharePoint event notifications. Business processes that rely on those events may stop working unless migrated. SharePoint webhooks and Microsoft Graph change notifications are the recommended replacement technologies. SharePoint webhooks are asynchronous. Solutions that depend on synchronously blocking or cancelling actions will need to be redesigned. There will not be an option to extend Remote Event Receivers beyond July 1, 2027. Microsoft currently does not provide a tenant-wide method for administrators to discover Remote Event Receiver usage. We will update this Message Center post, and the associated developer blog post, as soon as a discovery capability is available. [Action Required / Recommendations:] Identify any in-house applications or solutions that use Remote Event Receivers. Work with developers to determine whether Remote Event Receivers are in use. Contact third-party vendors to determine whether their solutions rely on Remote Event Receivers. Request updated webhook-based versions of affected third-party solutions. Plan migration to SharePoint webhooks or Microsoft Graph change notifications before July 1, 2027. Review internal documentation and operational procedures that reference Remote Event Receivers. Communicate this retirement to application owners, developers, support teams, and help desk personnel. Monitor future Message Center updates for Microsoft’s planned Remote Event Receiver discovery capability. Review Overview of SharePoint webhooks. Review Microsoft Graph change notifications guidance. Review the Azure ACS retirement FAQ. Review guidance for using Remote Event Receivers without an Azure ACS dependency. Review the SharePoint team retirement update blog. Learn more: Overview of SharePoint webhooks | Microsoft Learn Microsoft Graph change notifications | Microsoft Learn Will remote event receivers also be retired? — Azure ACS retirement FAQ | Microsoft Learn Remote event receivers retirement update in SharePoint Online Use remote event receivers without an Azure ACS dependency | Microsoft Learn Remote Event Receivers are retiring: move to SharePoint webhooks before July 1, 2027 [Compliance Considerations:] Area Explanation Does the change alter how existing customer data is processed, stored, or accessed? Organizations migrating from Remote Event Receivers to SharePoint webhooks or Microsoft Graph change notifications may need to redesign how SharePoint event data is retrieved and processed. Does the change modify, interrupt, or disable capabilities? Remote Event Receivers are being retired. Applications, workflows, and integrations that depend on them will stop receiving SharePoint events after July 1, 2027 unless migrated. Does the change alter how admins can monitor, report on, or demonstrate compliance activities? Microsoft currently does not provide a tenant-wide discovery capability for identifying Remote Event Receiver usage. Administrators must work with developers and solution vendors to assess exposure until a discovery capability becomes available. Does the change add any integration to 3rd party software products? Organizations using third-party solutions built on Remote Event Receivers may require updated vendor versions that use supported technologies such as SharePoint webhooks or Microsoft Graph change notifications. -
ESR management completed the transition to Windows Backup for Organizations
MC1411499 · stayInformed · normal · Updated 07/01/2026 16:57
Services: Windows
Read message
What and why If your IT department relies on Enterprise State Roaming (ESR) to synchronize user settings, its management has moved. Previously, IT admins were able to access it from the Microsoft Entra portal. Starting July 1, 2026, please access the new default experience through Windows Backup for Organizations policies. Windows Backup for Organizations is the enterprise‑grade solution for backing up and restoring Windows user settings and Microsoft Store app list. It’s designed to support device refresh, replacement, and feature updates (for example, moving to the latest version of Windows 11). ESR settings remain the same in scope. The only change is in how you manage these settings. Rollout schedule July 1, 2026: ESR management finished transitioning to Windows Backup for Organizations. This is now the only management option. May-June 2026: During this transition, you could manage ESR settings through both the Microsoft Entra portal and Windows Backup for Organizations policies. Impact on your organization If you currently rely on ESR to synchronize user settings, start managing ESR settings through Windows Backup for Organizations policies. Windows Backup for Organizations supports a broader set of Windows settings and is optimized for backup and restore scenarios. These scenarios include device replacement, reimaging, and OS feature updates. Users can pick up where they left off on a new or refreshed device, and you get clearer policy control and visibility. Action required/recommendations No action is required if your organization doesn’t use ESR or doesn’t require backup and restore of user settings and Microsoft Store app list. To continue syncing users’ settings, configure the Windows Backup for Organizations backup policy in Microsoft Intune or another mobile device management (MDM) provider. If you take no action, Windows will honor both ESR and Group Policy (GPO) or MDM roaming controls for one year (prioritizing GPO/MDM). After that, ESR will no longer work, and you’ll have to manage roaming through Windows Backup for Organizations policies. For more details, review the Windows Backup for Organizations official documentation to understand supported settings, storage behavior, and restore experiences. Additionally, see: Differences between Enterprise State Roaming and Windows Backup for Organizations How to configure backup and restore policies in Microsoft Intune Compliance considerations No compliance considerations are identified. Review as appropriate for your organization. -
(Updated) Automatic recording and transcription for Teams Call Queues
MC1401299 · stayInformed · normal · Updated 06/30/2026 16:16
Services: Microsoft Teams
Read message
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. To configure via PowerShell, review: New-CsAutoRecordingTemplate | PowerShell Get-CsAutoRecordingTemplate | PowerShell Set-CsCallQueue | PowerShell Get-CsCallQueue | PowerShell [Compliance considerations] Consideration Explanation Stores new customer data Call recordings and transcripts are generated and stored in SharePoint when the feature is enabled. Alters how existing customer data is processed, stored, or accessed Customer call interactions that were previously ephemeral are now captured as recordings and transcripts and stored for later access, if feature is enabled. Modifies Purview capabilities (eDiscovery, audit, retention) Recorded calls and transcripts may become subject to eDiscovery, retention, and audit policies depending on organization configuration. Includes admin control Admins can enable or disable recording and transcription per Call Queue and configure agent access. Allows user enable/disable (partial) Agents do not control recording, but admins can control whether agents can access recordings and transcripts. May impact data subject rights (GDPR) Recorded calls may contain personal data, which could require handling for export, deletion, or access requests depending on organizational processes. -
Windows Server 2022 hotpatch update support extended through October 2027
MC1405556 · stayInformed · normal · Updated 06/26/2026 21:25
Services: Windows
Read message
What and why Hotpatch update support for Windows Server 2022 Datacenter: Azure Edition is being extended beyond its original end date. Previously aligned to end of Mainstream Support in October 2026, hotpatch updates will now continue through October 2027. Hotpatching is designed to deliver protections against security threats without requiring a device restart. By applying updates directly to running processes, hotpatching helps maintain uptime, reduces servicing disruptions, and shortens the time it takes to respond to vulnerabilities. This extension allows organizations to continue benefiting from these capabilities for an additional year while maintaining the same update experience. Rollout schedule This change is effective immediately. Hotpatch update support, previously scheduled to end in October 2026, will now continue through October 2027. The existing monthly hotpatch update cadence remains unchanged. Impact on your organization This change applies to devices running Windows Server 2022 Datacenter: Azure Edition that are enrolled in hotpatch updates. Devices receiving hotpatch updates continue to get monthly security updates without requiring a restart between baseline months, helping maintain availability for critical workloads. There are no changes to how hotpatch updates are delivered or applied. Action required/recommendations No action is required. Compliance considerations No compliance considerations are identified. Review as appropriate for your organization. -
Best practices for deploying Secure Boot certificate updates
MC1403212 · stayInformed · normal · Updated 06/24/2026 16:58
Services: Windows
Read message
What and why: Many individuals and organizations have already successfully updated certificates for client devices, servers, and virtual machines, with others close behind. However close you are, finishing Secure Boot certificate deployment remains important. If you're still on this path, stay the course. Read about the proven best practices and the resources already available to you, as well as a few more opportunities to ask questions. Rollout schedule: June 24, 2026 – Secure Boot certificates start expiring, beginning with Microsoft Corporation KEK CA 2011 certificate. July 1 – Windows Server Secure Boot AMA July 8 – Secure Boot Office Hours for virtualized environments July 15 – OEM Secure Boot Office Hours Impact on your organization: If you are still in the process of updating Secure Boot certificates or validating updates in your organization, there are resources that can help. Focus on progress over perfection. Each step forward helps strengthen your environment’s platform root of trust. Devices with older certificates will continue to function and receive updates, giving you time to complete deployment. Completing this transition helps ensure that your devices stay current with evolving Secure Boot protections. Action required/recommendations: What we’ve seen consistently is that success comes from staying the course: Keep your devices up to date with the latest Windows updates. Check that the latest firmware version is installed. You can visit your OEM’s support page or use their official support channels. Continue with your phased rollout. Gradual deployment of certificates, boot managers, and updated OEM firmware, along with validation, remains the most reliable approach. Use the tools available to you. Whether built into Windows, such as the Windows Security app, or designed for IT-managed environments, these tools help you monitor progress and make informed decisions. Read Best practices for deploying Secure Boot certificate updates for a list of resources to support your next steps. Compliance considerations: No compliance considerations are identified. Review as appropriate for your organization. -
Power Query tenant setting supports ODBC to ADBC transition
MC1402304 · stayInformed · normal · Updated 06/23/2026 22:04
Services: Power BI
Read message
[What and Why:] Microsoft is introducing a new tenant-level setting to support the transition from ODBC (Open Database Connectivity) to ADBC (Arrow Database Connectivity) in Power Query. This change is part of Microsoft’s ongoing investment in improving data connectivity performance, reliability, and scalability. ADBC aligns with modern data access standards and helps deliver faster, more efficient data operations across your organization. [Rollout Schedule:] General Availability (Worldwide): Rollout begins late June 2026 and is expected to complete by late December 2026 [Impact on Your Organization:] Who is affected: Admins managing Power Query settings and data connectivity within the tenant Users leveraging ODBC-based connections in Power Query (e.g., Excel, Power BI) Platforms/Services: Power Query (across Excel, Power BI, and other integrated Microsoft data experiences) What will happen: A new tenant setting for ODBC-to-ADBC transition will be visible in your tenant. The setting is disabled by default at rollout. Microsoft plans to enable this setting by default at a later date. There is no immediate impact to users or existing workflows while the setting remains disabled. Future enablement may transition eligible connections from ODBC to ADBC. [Action Required / Recommendations:] No immediate action is required. We recommend that you: Review the new tenant setting once it becomes available. Evaluate existing ODBC-based data connections. Test ADBC compatibility in non-production environments. Communicate upcoming changes to data and analytics teams. Learn more: Transition to ADBC in Power Query [Compliance considerations:] No compliance considerations identified, review as appropriate for your organization. -
Point-in-time restore for Windows is generally available
MC1402092 · stayInformed · normal · Updated 06/23/2026 17:01
Services: Windows
Read message
What and why Point-in-time restore is a built-in Windows recovery feature. It lets users roll a PC back to a previous state in minutes, from the Windows Recovery Environment (WinRE). Restore points are stored locally. They include: Windows OS Installed applications System and app configurations Settings Local user files on the OS volume The feature helps organizations reduce downtime and recover from issues without a full reset, reimage, or rebuild. Relevant issues include problematic updates, driver issues, misconfigurations, or app installations. Rollout schedule Starting with the June 2026 Windows non-security update, Point-in-time restore is generally available for supported Windows 11 devices. On managed devices, the feature is off by default until Windows 11, version 26H2. However, you can enable it via policy today. Impact on your organization Once enabled, Windows captures local restore points on a configurable schedule. By default: Restore points are captured daily. Restore points remain available for up to 72 hours. Restore points use up to 2% of disk space. Restore points use reserved storage to reduce impact on storage space. Restore points are not pre-allocated. They might be removed earlier under storage pressure. Volumes outside of Windows OS location aren’t affected. You or any user can initiate restoration locally from WinRE with the required BitLocker recovery key. Microsoft Intune doesn’t yet support remote restore initiation. You can configure the feature using the Point-in-time restore CSP, via OMA-URI policy. Action required/recommendations Review your managed Windows device population and decide where to enable point-in-time restore. Managed devices won’t begin taking restore points unless you enable the feature before Windows 11, version 26H2. Recommended actions: Enable point-in-time restore for targeted managed device groups using the associated CSP. Configure settings such as restore point frequency, retention, and maximum disk usage. Ensure that devices have enough free space for restore points and the restore process. Ensure that users and helpdesk teams can access required BitLocker recovery keys. Update recovery playbooks, so support teams know when to use point-in-time restore before reset or reimage workflows. Communicate that restore reverts the OS volume to its state at the time of the restore point, including local user files. Reinforce storing user data in OneDrive or another cloud-backed location. Compliance considerations Organizations should review whether restoring data to an earlier state affects: Retention requirements Audit workflows Endpoint compliance Security monitoring After restoration, validate that required security tools, management agents, compliance policies, and configuration baselines are present and functioning as expected. Additional information Point-in-time restore for Windows Volume Shadow Copy Service (VSS) -
The June 2026 Windows non-security preview update is now available
MC1402091 · stayInformed · normal · Updated 06/23/2026 17:01
Services: Windows
Read message
The June 2026 non-security preview update is now available for Windows 11, versions 26H1, 25H2, and 24H2. Information about the contents of this update is available from the release notes, which are accessible from the Windows 11 update history page. To learn more about the different types of monthly quality updates, see Windows monthly updates explained. Looking to explore upcoming features and improvements in Windows 11? Check out the Windows roadmap. It includes what's coming to the Windows Insider Program, what's gradually rolling out, and what's generally available. Highlights for the Windows 11, version 25H2 update: The redesigned Start menu is available on commercial and managed Windows devices. For an overview of the feature, see Configure the Windows Start menu. IT administrators can use new customization policies: HideCategoryView and ConfigureStartPins. Learn more at Start Policy CSP and Start policy settings. A calendar experience in Windows Update Settings (Settings > Windows Update) lets you pause updates by choosing an end date for up to 35 days. You can extend the pause by selecting a different end date and re‑pause updates as needed. Point-in-time restore for Windows helps you quickly roll back your PC, including apps, settings, and personal files, to a recent automatic restore point. It helps reduce downtime and simplifies troubleshooting when issues occur. Windows now keeps the microphone mute state in sync between the audio mixer and the Hands-Free Profile (HFP) for a more consistent experience with Bluetooth headphones with mute buttons or indicators. You can now customize the size of the right-click zone in Settings > Bluetooth & devices > Touchpad. Choose from default, small, medium, or large to control how much of the bottom-right corner responds to a single-finger right-click. This setting is only available on touchpads with a pressable surface. For instructions on how to install this update, see the KB for your operating system listed below: Windows 11, version 26H1: KB5095091 Windows 11, versions 25H2 and 24H2: KB5095093 Note: With recent and upcoming Windows updates over the next few months, a limited number of consumer and business devices might experience one additional restart during installation. This one‑time restart occurs after a Secure Boot certificate update is applied as part of the Secure Boot update process. -
Secure Boot certificate updates for Linux on Azure virtual machines
MC1401337 · preventOrFixIssue · normal · Updated 06/23/2026 00:27
Services: Windows
Read message
What and why Microsoft has published new guidance for managing Secure Boot certificate updates for Linux on Azure virtual machines, including Trusted Launch and Confidential VMs with Secure Boot enabled. These updates help maintain trusted boot integrity and help ensure continued access to platform updates and functionality. Rollout schedule This new guidance is available now. Impact on your organization Linux-based Azure virtual machines with Secure Boot enabled might encounter startup validation issues if you don’t apply certificates on time. Organizations managing these devices should review and plan for certificate updates to avoid potential disruption and help maintain a secure boot process. Who is affected IT admins managing Linux Azure virtual machines with Secure Boot enabled. Action required / recommendations Review Linux-based Azure virtual machines with Secure Boot enabled to help ensure continued startup reliability and avoid potential disruptions. Review the published guidance and plan for Secure Boot certificate updates where applicable. Compliance considerations Review the updated guidance and help ensure Linux-based Azure virtual machines are up to date and prepared for updated Secure Boot certificates. -
Microsoft Teams: Location-Based Routing update blocks OS default location for Operator Connect in India
MC1401300 · preventOrFixIssue · normal · Updated 06/22/2026 22:55
Services: Microsoft Teams
Read message
[What and Why:] We’ve updated Location-Based Routing (LBR) behavior for Operator Connect in India to ensure compliance with India toll bypass regulations. Microsoft Teams now blocks the use of a manually set Windows location (“OS default location”) for LBR-enforced users. If a user’s location is derived from OS default settings instead of network-based detection, geo-coordinates are stripped and cannot be used for routing decisions. This helps prevent toll bypass and location spoofing. This change reached General Availability on April 30, 2026. We acknowledge this change was not communicated in advance and are sharing this post to provide guidance. [Rollout Schedule:] This change has completed rollout (Worldwide and GCC). [Impact on Your Organization:] Who is affected: Tenants using Operator Connect in India with Location Based Routing enabled, especially: Users on corporate networks or VPNs (especially Zscaler configurations) Users on virtual machines or remote desktop environments Environments where Windows Location Services URLs are routed through VPN or proxy instead of split tunneling Platforms/Services: Microsoft Teams (desktop) Windows Location Services Operator Connect (India) What will happen: Teams will no longer accept manually set OS default location as a valid source for LBR enforcement When network-based location detection fails:Geo-coordinates are stripped LBR cannot validate user location PSTN calling may be disabled Users may experience:Intermittent dial pad or PSTN calling availability Calling working outside the corporate network but failing inside Corporate environments may increase impact due to:VPNs or proxies (including Zscaler configurations) Virtual machines or remote desktop environments Windows Location Services traffic routed through VPN instead of split tunneling This behavior is by design. LBR in India requires verified network-based location detection for regulatory compliance. [Action Required / Recommendations:] Update VPN split-tunnel configurations to ensure Windows Location Services URLs are routed directly (not through VPN or proxy) Do not rely on manually set OS default location for LBR-enforced users Validate that network-based location detection is functioning correctly, especially for users reporting intermittent calling issues If users report a disabled dial pad:Verify whether their device is falling back to OS default location Check network routing configuration Learn more: Plan Operator Connect for India | Microsoft Learn [Compliance considerations:] ConsiderationExplanation Does the change alter how existing customer data is processed, stored, or accessed?The change modifies how location data is validated and processed by enforcing network-based detection and rejecting OS-derived location sources for LBR decisions. Does the change modify, interrupt, or disable any Purview-related capabilities?Calling functionality may be disabled when compliant location data is unavailable, which could indirectly impact user activity and communication patterns. -
Retirement of Turnitin Similarity integration in Microsoft Teams Assignments
MC1401298 · planForChange · normal · Updated 06/22/2026 22:54
Services: Microsoft Teams
Read message
[What and Why:] Microsoft is retiring the Turnitin Similarity integration in Microsoft Teams Assignments and encouraging institutions to transition to Turnitin Feedback Studio for Microsoft Teams. Turnitin Feedback Studio provides similarity checking, grading, feedback, and assignment management within Teams. For sustainability and fairness in its partner ecosystem, Microsoft Education is phasing out non-standard integrations with third party products such as the Similarity integration in Teams Assignments. Turnitin's Feedback Studio integration is built for the long-term, using standard platform extensibility features. [Rollout Schedule:] Retirement date: December 31, 2026 [Impact on Your Organization:] Who is affected: Organizations currently using the Turnitin Similarity integration in Microsoft Teams Assignments Educators and administrators managing assignments with Turnitin Platforms/Services: Microsoft Teams (Assignments feature) Turnitin integrations (Similarity and Feedback Studio) What will happen: The legacy Turnitin Similarity integration will be removed from Teams Assignments on December 31, 2026. Organizations that want to continue using Turnitin capabilities in Teams Assignments should transition to Turnitin Feedback Studio for Microsoft Teams. Microsoft is encouraging customers to complete this transition before the retirement date to avoid interruptions to similarity-checking and related assignment workflows. Customers that do not migrate before December 31, 2026, could experience disruption to plagiarism-checking and other assignment-related processes that depend on the legacy integration. The Turnitin team will contact customers directly from msteamsmigration@turnitin.com with migration details, training, and support resources. [Action Required / Recommendations:] Review whether your institution is currently using the legacy Turnitin Similarity integration in Teams Assignments. Plan and complete your transition to Turnitin Feedback Studio for Microsoft Teams before December 31, 2026. Watch for migration guidance from msteamsmigration@turnitin.com and review the training and support resources that Turnitin provides. Inform educators, support staff, and administrators about the retirement of the legacy integration and the required migration timeline. Update any internal documentation, training materials, or help desk guidance that references the legacy Turnitin Similarity integration. [Compliance considerations:] This change adds or modifies a third-party integration because it retires the legacy Turnitin Similarity integration and directs customers to Turnitin Feedback Studio for Microsoft Teams. -
Get ready for Windows 11, version 26H2
MC1397393 · stayInformed · normal · Updated 06/19/2026 17:10
Services: Windows
Read message
The next feature update for Windows 11 will be version 26H2. This version continues our focus on delivering a predictable, low-disruption update experience for organizations and IT professionals. Rollout schedule: June 19, 2026: Windows 11, version 26H2 is available to preview through the Windows Insiders Program. Second half of 2026: Windows 11, version 26H2 will be generally available. Impact on your organization: Windows 11, version 26H2 builds on the same platform and servicing approach introduced in prior releases. Therefore, the transition should be easy. For devices running Windows 11, versions 24H2 or 25H2, the update will be offered as a small enablement package instead of a full OS replacement. Remember that devices running Windows 11, version 26H1 won’t be able to update to version 26H2 due to its different Windows core. There will be a path to update those devices to a future Windows release. Action required/recommendations: To prepare, you can validate the update today, use your existing deployment tools and standard deployment rings, as well as stay up to date with monthly updates. You can start previewing Windows 11, version 26H2 today through the Windows Insider Program’s Experimental channel. Learn more and Get ready for Windows 11, version 26H2. Compliance considerations: No compliance considerations are identified. Review as appropriate for your organization. -
Microsoft SharePoint Online: Retirement of Restricted SharePoint Search
MC1395311 · planForChange · normal · Updated 06/18/2026 05:03
Services: SharePoint Online
Read message
[What and Why] Restricted SharePoint Search (RSS) is being retired in Microsoft SharePoint Online. RSS was used to limit how SharePoint content appears in Microsoft Search and Microsoft 365 Copilot during permissions and governance reviews. Microsoft 365 now provides more granular and scalable controls. Restricted Content Discovery (RCD) offers improved security and governance and supports Microsoft 365 Copilot scenarios. Microsoft recommends transitioning to RCD or other appropriate controls to manage content discoverability. This change simplifies content discovery management and aligns with current controls. [Retirement Schedule] July 31, 2026: New RSS enablement will be blocked. July 2026 – January 2027: Retirement period. January 31, 2027: RSS will be fully retired (no extensions or exceptions). February 28, 2027: RSS PowerShell cmdlets will be retired. [Impact on Your Organization] Who is affected Organizations currently using Restricted SharePoint Search (RSS) in Worldwide, GCC, GCC High and DoD SharePoint and Microsoft 365 administrators managing search visibility and governance Platforms/Services SharePoint Online Microsoft Search Microsoft 365 Copilot What will happen New RSS enablement will be blocked after July 31, 2026. RSS will stop functioning after January 31, 2027 (no extensions). RSS PowerShell cmdlets will stop working after February 28, 2027. Microsoft will not automatically migrate RSS configurations to Restricted Content Discovery (RCD). Administrators must transition to RCD or other governance controls to manage content discoverability. If no action is taken, restricted content may become discoverable after RSS retirement. [Action Required/Recommendations] If you are not using RSS, no action is required. If your organization uses RSS: Check if RSS is enabled in your tenant. Get the current mode of Restricted Search Identify sites configured with RSS and review allowed site lists. Get the existing list of URLs in the allowed list Plan transition to Restricted Content Discovery (RCD) or other governance controls. Optionally disable RSS ahead of retirement if no longer needed. Enable or disable Restricted Search Apply RCD where needed and validate behavior. Disable RSS after migration is complete. Update internal documentation and notify admin/support teams. Learn more: Restrict discovery of SharePoint sites and content | SharePoint in Microsoft 365 | SharePoint | Microsoft Learn Use PowerShell Scripts for Restricted SharePoint Search | SharePoint in Microsoft 365 | SharePoint | Microsoft Learn [Compliance considerations] No compliance considerations have been identified. Review as appropriate for your organization. -
30-Day Reminder: Final deployment phase for Kerberos RC4 hardening begins with the July 2026 Windows security update
MC1388721 · stayInformed · normal · Updated 06/12/2026 16:56
Services: Windows
Read message
What and Why Windows updates released in July 2026 will complete the final deployment phase of protections for a Kerberos information disclosure vulnerability (CVE‑2026‑20833). Beginning with this phase, Audit mode is removed, leaving Enforcement mode as the only available option for Kerberos RC4 usage on Windows domain controllers. Environments with remaining RC4 dependencies might experience authentication issues unless those dependencies are remediated or explicitly configured before the July 2026 Windows security update is installed. Rollout Schedule April 2026 - Enforcement Phase with manual rollback: With installation of the April 2026 Windows security update, default Kerberos behavior changes so domain controllers use AES‑SHA1-only encryption for accounts without explicit encryption type settings, and Enforcement mode is enabled by default on Windows domain controllers. Audit mode remains available as a manual rollback option until July 2026. July 2026 – Enforcement Phase: With installation of the July 2026 Windows security update, Audit mode is removed, and Enforcement mode becomes the only available behavior for supported Windows domain controllers. Impact on Your Organization With installation of the July 2026 Windows security update, Windows domain controllers will no longer support Audit mode rollback behavior for Kerberos RC4 hardening. Environments with service accounts, applications, appliances, or devices that still rely on RC4-based Kerberos tickets may experience authentication failures unless those dependencies have been remediated or explicitly configured to support continued RC4 usage where required. Devices using non-Windows Kerberos implementations might also require additional interoperability testing to ensure continued authentication functionality after the July 2026 Enforcement phase begins. Azure Files note: For devices using Azure Files SMB with Active Directory-based authentication, address any RC4 dependencies before installation of the July 2026 Windows security update to reduce the risk of access disruption once Audit mode is removed. Follow the steps in the official documentation to help maintain uninterrupted access to Azure Files and dependent workloads such as Azure Virtual Desktop. Action Required/Recommendations Continue monitoring the System event log for Kerberos-related events indicating RC4 dependencies or insecure encryption configurations. If event log data shows RC4 reliance, remediate by moving to AES‑based encryption or explicitly configuring the account’s msds-SupportedEncryptionTypes attribute where RC4 is still required. Before deploying the July 2026 Windows security update, validate that service accounts, applications, and non-Windows Kerberos implementations can successfully authenticate without requiring RC4-based Kerberos authentication. Compliance Considerations Audit events related to this change are only generated when Active Directory is unable to issue AES‑SHA1 service tickets or session keys. The absence of audit events does not guarantee that all non-Windows devices will successfully accept Kerberos authentication after the July 2026 Enforcement phase begins. Validate interoperability through testing before broadly deploying the July 2026 Windows security update. -
Windows Office Hours: June 18, 2026
MC1388720 · stayInformed · normal · Updated 06/12/2026 16:56
Services: Windows
Read message
If you are an IT admin with questions about managing and updating Windows, we want to help. Every third Thursday of the month, we host a live chat-based event on the Tech Community called Windows Office Hours. Members of the Windows, Microsoft Intune, Windows Autopilot, Windows Autopatch, and Windows 365 engineering teams will be standing by to answer your questions. Want to attend the June 18 session of Office Hours? Add it to your calendar and select Attend on the event page to let us know you're coming. There is no video or live meeting component. Simply visit the event page, log in to the Tech Community, and leave your questions in the Comments section. You can also bookmark https://aka.ms/Windows/OfficeHours for upcoming dates (and the ability to add this event to your calendar). We look forward to helping you. -
The June 2026 Windows security update is now available
MC1385471 · stayInformed · normal · Updated 06/09/2026 17:28
Services: Windows
Read message
The June 2026 security update is now available for all supported versions of Windows. We recommend that you install these updates promptly. For more information about the contents of this update, see the release notes, which are easily accessible from the Windows 11 update history page. To learn more about the different types of monthly quality updates, see Windows monthly updates explained. Highlights for the Windows 11, version 25H2 update: This security update includes improvements that were a part of update KB5089573 (released May 26, 2026). This update expands high confidence device targeting data, increasing coverage of devices eligible to automatically receive new Secure Boot certificates. Devices receive the new certificates only after demonstrating sufficient successful update signals, maintaining a controlled and phased rollout. This update includes a resolution for CVE‑2026‑45585 (BitLocker security feature bypass). The mitigation script remains part of the guidance and does not need to be reverted. Short on time? Watch our Windows 11 release notes video for this month's tips. For instructions on how to install this update, see the KB for your operating system listed below: • Windows 11, version 26H1: KB5095051 • Windows 11, versions 25H2 and 24H2: KB5094126 • Windows 11, version 23H2: KB5093998 • Windows 11 Enterprise LTSC 2024: Baseline KB5094126 • Windows 10, versions 22H2 and 21H2: KB5094127 • Windows 10 Enterprise LTSC 2019 and Windows Server 2019: KB5094123 • Windows 10 LTSB 2016 and Windows Server 2016: KB5094122 • Windows Server 2025: KB5094125 • Windows Server 2025 Datacenter: Azure Edition: Baseline KB5094125 • Windows Server 2022: KB5094128 • Windows Server 2022 Datacenter: Azure Edition: Baseline KB5094128 • Windows Server 2012 R2: KB5094041 • Windows Server 2012: KB5094042 Note: With recent and upcoming Windows updates over the next few months, a limited number of consumer and business devices might experience one additional restart during installation. This one‑time restart occurs after a Secure Boot certificate update is applied as part of the Secure Boot update process. -
(Updated) Take action: Mitigation guidance updated with a new script for CVE-2026-45585
MC1318295 · preventOrFixIssue · normal · Updated 06/09/2026 17:28
Services: Windows
Read message
Updated June 9, 2026: This message has been updated to reflect the availability of the June 2026 security update, which addresses CVE‑2026‑45585. If you have applied the temporary mitigations documented prior to this update’s release, you do not need to revert it once you install the update. Microsoft has updated the mitigation guidance in CVE-2026-45585, a Windows BitLocker security feature bypass vulnerability. The June 2026 security update that addresses this vulnerability is now available. Note that a limited set of Windows versions are affected: Windows 11, versions 26H1, 25H2, and 24H2, and Windows Server 2025. When will this happen: The June 2026 security update and the updated mitigation guidance are available now. How this will affect your organization: Microsoft recommends applying the June 2026 security update to address this vulnerability. Windows devices that use BitLocker may be exposed if mitigations are not applied. Organizational environments that previously implemented the manual mitigation steps or the mitigation script do not need to take additional action, and the previously applied mitigation does not need to be reverted. What you need to do to prepare: Organizational environments using BitLocker on affected Windows versions should review the updated guidance in the Microsoft Security Update Guide to determine the appropriate action for their environment. Additional information: CVE-2026-45585: Windows BitLocker Security Feature Bypass Vulnerability -
Microsoft Viva Glint: Custom confidentiality statements
MC1318856 · stayInformed · normal · Updated 06/05/2026 23:21
Services: Microsoft Viva
Read message
[What and Why:] We're introducing the ability for Viva Glint Company Admins to replace the default Microsoft confidentiality statement with custom messaging. This update helps organizations align employee survey experiences with internal confidentiality policies, legal requirements, and regional expectations—while maintaining a consistent, trusted experience across Viva Glint. This feature is associated with Microsoft 365 Roadmap ID 557982. [Rollout Schedule:] General Availability (Worldwide): Rollout begins in early June 2026. [Impact on Your Organization:] Who is affected: Viva Glint Company Admins Users participating in Viva Glint surveys (if custom messaging is configured) Platforms/Services: Microsoft Viva Glint (web) What will happen: Admins can disable the default Microsoft Viva Glint confidentiality statement. Admins can configure custom confidentiality statements, including support for multiple languages. Custom statements are displayed to users during the survey experience. The feature is not enabled by default; configuration is optional and admin-controlled. If no changes are made, the existing default confidentiality statement remains in place. [Action Required / Recommendations:] No action is required. Admins may optionally configure custom confidentiality statements in Viva Glint > General Settings > Company Information. Review internal legal or HR guidance before publishing custom messaging. Learn more: Manage General Settings in Viva Glint | Microsoft Learn (will be updated on June 1, 2026) How Viva Glint protects your privacy | Microsoft Learn (will be updated on June 1, 2026) [Compliance considerations:] Compliance areaExplanation Does the change alter how existing customer data is processed, stored, or accessed?Admin-defined confidentiality statements modify the messaging presented to users but do not change how survey response data is processed or stored. Does the change include an admin control?Company Admins can enable, disable, and manage custom confidentiality statements in Viva Glint settings. -
The May 2026 Windows non-security preview update is now available
MC1323218 · stayInformed · normal · Updated 05/26/2026 21:00
Services: Windows
Read message
The May 2026 non-security preview update is now available for Windows 11, versions 26H1, 25H2, and 24H2. Information about the contents of this update is available from the release notes, which are accessible from the Windows 11 update history page. To learn more about the different types of monthly quality updates, see Windows monthly updates explained. Looking to explore upcoming features and improvements in Windows 11? Check out the Windows roadmap. It includes what's coming to the Windows Insider Program, what's gradually rolling out, and what's generally available. Highlights for the Windows 11, version 25H2 update: Shared audio enables two people to listen to the same audio from a single Windows 11 PC at the same time. Task Manager now provides enhanced visibility into NPU usage, including new metrics and AI activity insights. Multi‑App Camera allows multiple apps to access the camera simultaneously. Basic Camera mode enables simplified camera functionality, useful for troubleshooting when your camera is not working correctly You can now choose a custom name for your user folder on the Device Name page during Windows setup. User folder names must follow standard Windows naming requirements. For instructions on how to install this update, see the KB for your operating system listed below: • Windows 11, version 26H1: KB5089570 • Windows 11, versions 25H2 and 24H2: KB5089573 Note: With recent and upcoming Windows updates over the next few months, a limited number of consumer and business devices might experience one additional restart during installation. This one‑time restart occurs after a Secure Boot certificate update is applied as part of the Secure Boot update process. -
Updated Secure Boot status report in Windows Autopatch
MC1315905 · stayInformed · normal · Updated 05/19/2026 17:01
Services: Windows
Read message
The Secure Boot status report in Windows Autopatch has been updated to offer deeper, device-level insights into Secure Boot certificate status, trust configuration, and readiness. New insights—such as confidence level, alerts, and detailed certificate reporting—can help you make more informed, targeted decisions about rolling out and monitoring certificate updates. When will this happen: These updates are now live in Windows Autopatch. What you need to do to prepare: No immediate action is required. We recommend reviewing the updated report in the Intune admin center and using the new signals to guide your Secure Boot certificate rollout strategy. They can also help you identify devices that need updates and plan targeted remediations. Additional information: You can learn more about the Secure Boot status report by consulting the Windows Autopatch documentation. For continued guidance and updates on Secure Boot in general, we recommend that you bookmark aka.ms/GetSecureBoot. -
(Updated) Consult and merge into a meeting or group call via Dual-Tone Multi-Frequency (DTMF)
MC1183611 · stayInformed · normal · Updated 05/18/2026 16:26
Services: Microsoft Teams
Read message
Updated May 18, 2026: We have updated the timeline. Thank you for your patience. [Introduction] To improve collaboration and streamline meeting workflows, Microsoft Teams is introducing the ability to consult and merge Public Switched Telephone Network (PSTN) callers into active meetings—even when those callers are behind auto-attendants or Interactive Voice Response (IVR) systems that require Dual-Tone Multi-Frequency (DTMF) navigation. This enhancement allows users to reach subject matter experts via dial-in and seamlessly bring them into the broader conversation. This message is associated with Microsoft 365 Roadmap ID 518218. [When this will happen:] Targeted Release: Rolling out early April 2026 (previously early March), expected to complete by mid-April 2026 (previously mid-March). General Availability: Rolling out mid-April 2026 (previously late March), expected to complete by mid-June 2026 (previously late April). [How this affects your organization:] Who is affected: All Microsoft Teams users who initiate or manage meetings with PSTN participants. Administrators overseeing Teams meeting policies and call configurations. What will happen: Users can consult with PSTN or Voice over Internet Protocol (VoIP) participants via the Participants panel. A new interface will allow users to access a dialpad to navigate IVR systems and auto-attendants using DTMF tones. Once the external party is reached, users can merge them into the ongoing meeting. No changes to existing administrator policies; feature is enabled by default. [What you can do to prepare:] No administrator action is required for this rollout. If your organization uses custom training or helpdesk documentation, consider updating it to reflect this new capability. Before rollout, we will update this post with new documentation. [Compliance considerations:] No compliance considerations identified, review as appropriate for your organization. -
PowerPoint for Windows: Create a presentation with Copilot directly from PowerPoint Home
MC1311974 · stayInformed · normal · Updated 05/15/2026 23:12
Services: Microsoft 365 apps
Read message
[Introduction] We’re improving how users get started with Copilot in PowerPoint for Windows by enabling presentation creation powered by Copilot directly from PowerPoint Home in the File menu. This update reduces friction at the start of the workflow, helping users move from idea to first draft faster without needing to open a new file. This message is associated with Microsoft 365 Roadmap ID 560694. [When this will happen:] General Availability (Worldwide): Rollout begins in late May 2026. [How this affects your organization:] Who is affected: Users on PowerPoint for Windows Users who are assigned a Microsoft Copilot license What will happen: Users will find a new option on PowerPoint Home (File menu) to create a presentation using Copilot. The experience is available immediately when PowerPoint is opened. The feature is enabled by default for eligible users. Existing Microsoft 365 and Copilot policies are respected; no admin configuration changes are required. [What you can do to prepare:] No action is required. Consider informing users about this new Copilot capability. [Compliance considerations:] No compliance considerations identified, review as appropriate for your organization. -
PowerPoint for Mac: Create a presentation with Copilot directly from PowerPoint Home
MC1311973 · stayInformed · normal · Updated 05/15/2026 23:12
Services: Microsoft 365 apps
Read message
[Introduction] We’re improving how users get started with Copilot in PowerPoint for Windows by enabling presentation creation powered by Copilot directly from PowerPoint Home in the File menu. This update reduces friction at the start of the workflow, helping users move from idea to first draft faster without needing to open a new file. This message is associated with Microsoft 365 Roadmap ID 560536. [When this will happen:] General Availability (Worldwide): Rollout begins in late May 2026. [How this affects your organization:] Who is affected: Users on PowerPoint for Mac Users who are assigned a Microsoft Copilot license What will happen: Users will find a new option on PowerPoint Home (File menu) to create a presentation using Copilot. The experience is available immediately when PowerPoint is opened. The feature is enabled by default for eligible users. Existing Microsoft 365 and Copilot policies are respected; no admin configuration changes are required. [What you can do to prepare:] No action is required. Consider informing users about this new Copilot capability. [Compliance considerations:] No compliance considerations identified, review as appropriate for your organization. -
Windows Office Hours: May 21, 2026
MC1310552 · stayInformed · normal · Updated 05/14/2026 17:10
Services: Windows
Read message
If you are an IT admin with questions about managing and updating Windows, we want to help. Every third Thursday of the month, we host a live chat-based event on the Tech Community called Windows Office Hours. Members of the Windows, Microsoft Intune, Windows Autopilot, Windows Autopatch, and Windows 365 engineering teams will be standing by to answer your questions. Want to attend the May 21 session of Office Hours? Add it to your calendar and select Attend on the event page to let us know you’re coming. There is no video or live meeting component. Simply visit the event page, log in to the Tech Community, and leave your questions in the Comments section. You can also bookmark https://aka.ms/Windows/OfficeHours for upcoming dates (and the ability to add this event to your calendar). We look forward to helping you. -
Broader Windows Autopatch availability to Microsoft 365 Government Community Cloud (GCC)
MC1309692 · stayInformed · normal · Updated 05/13/2026 20:55
Services: Windows
Read message
Windows Autopatch is now broadly available in Government Community Cloud (GCC). The $0 Windows Enterprise (OLS) activation SKU is no longer required for Microsoft 365 G3 and G5 SKUs in GCC. Windows Autopatch is now included with eligible Microsoft 365 GCC subscriptions. Eligible subscriptions include Microsoft 365 G3 GCC, Microsoft 365 GCC G5, and Microsoft 365 GCC G5 without WDATP/CAS Unified. When will this happen: This change is now available. How this will affect your organization: The Windows Enterprise (OLS) activation SKU is no longer required to access Windows Autopatch features in Microsoft Intune. These features include update policies for feature, quality, and driver updates, plus enhanced reporting. What you need to do to prepare: No action is required. Windows Autopatch capabilities are now available automatically in Microsoft Intune for eligible Microsoft 365 GCC subscriptions. Additional information: Learn more about using Windows Autopatch and managing Windows updates in Microsoft Intune. -
Tune in May 18 to ask Microsoft anything about Secure Boot
MC1309552 · stayInformed · normal · Updated 05/13/2026 17:05
Services: Windows
Read message
Secure Boot certificates start expiring in June of 2026. Whether you’re actively deploying or just starting to plan, an ongoing series of AMAs is here to provide you with clear, practical answers directly from Microsoft experts. When will this happen: The next Secure Boot AMA will take place on the Microsoft Tech Community at 8:00 AM PDT on May 18, 2026. What you need to do to prepare: Visit https://aka.ms/AMA/SecureBoot and sign in to the Tech Community to post your questions in advance or in real time during the event. You’ll also find options to add the event to your calendar. Additional information: For continued guidance and updates, bookmark the Secure Boot playbook and https://aka.ms/GetSecureBoot. -
The May 2026 Windows security update is now available
MC1308634 · stayInformed · normal · Updated 05/12/2026 17:12
Services: Windows
Read message
The May 2026 security update is now available for all supported versions of Windows. We recommend that you install these updates promptly. For more information about the contents of this update, see the release notes, which are easily accessible from the Windows 11 update history page. To learn more about the different types of monthly quality updates, see Windows monthly updates explained. Highlights for the Windows 11, version 25H2 update: This security update includes improvements that were a part of update KB5083631 (released April 30, 2026). This update makes quality improvements to the servicing stack, which is the component that installs Windows updates. This update expands high confidence device targeting data, increasing coverage of devices eligible to automatically receive new Secure Boot certificates. Devices receive the new certificates only after demonstrating sufficient successful update signals, maintaining a controlled and phased rollout. This update improves startup reliability after boot file updates, so devices start normally without entering BitLocker recovery. This update improves the reliability of Simple Service Discovery Protocol (SSDP) notifications to help prevent the service from becoming unresponsive. Short on time? Watch our Windows 11 release notes video for this month's tips. For instructions on how to install this update, see the KB for your operating system listed below: Windows 11, version 26H1: KB5089548 Windows 11, versions 25H2 and 24H2: KB5089549 Windows 11, version 23H2: KB5087420 Windows 11 Enterprise LTSC 2024: Hotpatch KB5089466 Windows 10, versions 22H2 and 21H2: KB5087544 Windows 10 Enterprise LTSC 2019 and Windows Server 2019: KB5087538 Windows 10 LTSB 2016 and Windows Server 2016: KB5087537 Windows Server 2025: KB5087539 Windows Server 2025 Datacenter: Azure Edition: Hotpatch KB5087423 Windows Server 2022: KB5087545 Windows Server 2022 Datacenter: Azure Edition: Hotpatch KB5087424 Windows Server 2012 R2: KB5087471 Windows Server 2012: KB5087470 Note: With recent and upcoming Windows updates, a limited number of consumer and business devices might experience one additional restart during installation. This one‑time restart occurs after a Secure Boot certificate update is applied as part of the Secure Boot update process. -
Configuring firewall and proxies for smooth Windows updates
MC1307636 · stayInformed · normal · Updated 05/11/2026 17:05
Services: Windows
Read message
A new guide is here to help you troubleshoot connection issues with the Windows Update service. Some of these issues have to do with the embedded network security design. The key is in the configuration of your network endpoints for firewalls and proxies. When will this happen: While the solution isn’t new, new guidance is now published to help with ongoing troubleshooting. How this will affect your organization: By design, Windows Update doesn’t trust servers that don’t have TLS certificates issued by an actual Windows Update trust anchor. Your firewalls and proxies might block access to the trustworthy and necessary Windows Update service if your configuration is either intercepting TLS connections or isn’t passing TLS requests through for the necessary DNS subdomains. The new guide helps you diagnose and fix related issues. What you need to do to prepare: Diagnose connection issues by checking the Windows Update audit log. The article lists the recommended PowerShell command and four error codes that can confirm the issue. To remedy the situation, trust all the DNS hosts and subdomains related to wildcard FQDN for the connection to work properly. For example, a recommended DNS host name *.update.microsoft.com represents all the following hosts and subdomains: update.microsoft.com sls.update.microsoft.com tas02.sls.update.microsoft.com Update your proxy and firewall configurations if any of these subdomains are missing. If your devices connect to an IT-managed Windows Server Update Services (WSUS) server, these exceptions aren’t necessary. Additional information: Configuring firewall and proxies for smooth Windows updates Windows Update security Transport Layer Security protocol Connection endpoints for Windows 11 Enterprise Scan changes and certificates add security for Windows devices using WSUS for updates -
Upgrade to Windows Server 2025, now via Windows Update
MC1301827 · stayInformed · normal · Updated 05/05/2026 23:07
Services: Windows
Read message
Windows Update can be used to perform an in-place upgrade of Windows Server without installation media. This Windows Server feature update can help move Windows Server 2022 or Windows Server 2019 installations to Windows Server 2025, following the same process used to download monthly updates through Windows Update. Upgrading helps keep your servers secure, supported, and able to use the latest features and performance improvements. Plan your installation and learn about the in-place upgrade paths by version, prerequisites, and restrictions, at Opt-In Windows Server 2025 Feature Update from the WS 2022 and WS 2019 Settings Dialog. When will this happen: This feature update path is available now. To see the Windows Server 2025 offer in Settings > Windows Update, servers must meet these update baselines: Windows Server 2022: March 2026 Cumulative Update (KB5078766) or later. Windows Server 2019: March 2026 Cumulative Update (KB5078752) or later. As always, we recommend you install the latest security update for your device as it contains important improvements and issue resolutions. Please note that additional steps are required to display the upgrade offer. See the resources in the Additional Information section. How this will affect your organization: In-place upgrade is ideal for when you want the fastest path to a newer version on the same hardware. It keeps you on the same hardware, and you can avoid re-installing applications and services after only a device restart. Once the manual steps to enable this upgrade path have been completed, an upgrade banner appears in Windows Update. An administrator must manually click Download and Install to trigger the upgrade. What you need to do to prepare: If you're considering the in-place upgrade for your organization, note that there are also prerequisites and restrictions to consider. Ensure you have a valid product key and activation method for the target version. Also, note that not all roles support in-place upgrade. Additionally, an opt-in registry key must be added to enable this upgrade path on qualifying devices. Study the information in the Additional Information links for complete details. Additional information: Opt-In Windows Server 2025 Feature Update from the WS 2022 and WS 2019 Settings Dialog Plan your Windows Server upgrade Perform an in-place upgrade of Windows Server -
The April 2026 Windows non-security preview update is now available
MC1296868 · stayInformed · normal · Updated 04/30/2026 23:07
Services: Windows
Read message
The April 2026 non-security preview update is now available for Windows 11, versions 26H1, 25H2, and 24H2. Information about the contents of this update is available from the release notes, which are accessible from the Windows 11 update history page. To learn more about the different types of monthly quality updates, see Windows monthly updates explained. Looking to explore upcoming features and improvements in Windows 11? Check out the Windows roadmap. It includes what’s coming to the Windows Insider Program, what’s gradually rolling out, and what’s generally available. Highlights for the Windows 11, version 25H2 update: Xbox mode is now available on Windows 11 PCs, including laptops, desktops, and tablets. Xbox mode provides a streamlined, full-screen interface that places games front and center while minimizing background activity. You can enter Xbox mode from the Xbox app, Game Bar settings, or by pressing the Windows logo key + F11. You can now experience haptic feedback on supported input devices when performing certain actions, such as aligning objects in PowerPoint, snapping or resizing windows. Haptic feedback can be managed in Settings > Bluetooth & devices > Mouse, Touchpad, or Pen > Haptic signals. Enterprise State Roaming (ESR) can now be managed through Windows Backup for Organizations policies, simplifying configuration for IT administrators. To learn more, see Enterprise State Roaming. This update adds support for a dynamic app removal list to the “Remove Default Microsoft Store Packages” policy for Windows Enterprise and Education. Administrators can remove additional MSIX/APPX apps by specifying package family names using Group Policy. For more information, see Policy-based in-box app removal. This update improves the performance of launching startup apps after starting your device (apps listed under Settings > Apps > Startup). For instructions on how to install this update, see the KB for your operating system listed below: Windows 11, version 26H1: KB5083806 Windows 11, versions 25H2 and 24H2: KB5083631 Note: With recent and upcoming Windows updates over the next few months, a limited number of consumer and business devices might experience one additional restart during installation. This one‑time restart occurs after a Secure Boot certificate update is applied as part of the Secure Boot update process. -
Dynamically remove apps from managed Windows 11 devices
MC1296576 · stayInformed · normal · Updated 04/30/2026 18:46
Services: Windows
Read message
Simplify Microsoft Store app management with dynamic removal on more devices across your enterprise. Use policy to remove any preinstalled MSIX/APPX app by referencing its Package Family Name (PFN). It's available to Enterprise and Education devices running Windows 11, versions 25H2 and 24H2. Starting with the April 2026 Windows non-security update, you can use Group Policy or custom OMA-URI for mobile device management (MDM). Additional Microsoft Intune capabilities are coming later. When will this happen: October 2025: The policy, “Remove default Microsoft Store packages from the system”, first became available. March 13, 2026: The expanded policy became available to Windows Insiders in the Dev and Beta channels. April 2026 Windows non-security update: The expanded policy is broadly available for use with Group Policy and custom OMA-URI. Future releases: Additional Intune capabilities are coming. How this will affect your organization: The expanded policy offers the benefit of fewer unwanted apps, simpler provisioning, and a more tailored desktop for users at your organization. This capability is now expanded to Windows 11, version 24H2 and later, on Enterprise and Education devices only. What you need to do to prepare: Ensure that your devices have the latest cumulative updates installed to receive these improvements. Notify users in advance if they need to save local data, since removing an app also removes associated on-disk app data. Find complete instructions for available methods and upcoming Intune capabilities under Additional information. Additional information: Dynamically remove apps from managed Windows 11 devices Policy-based removal of pre-installed Microsoft Store apps Policy-based in-box app removal ApplicationManagement Policy CSP -
An updated version of the April 2026 Scan Cab is available
MC1294316 · preventOrFixIssue · normal · Updated 04/28/2026 17:38
Services: Windows
Read message
IMPORTANT: This notice is only relevant for environments where: Visual Studio 2026 with .NET version 10.0.6 is used Scan Cab is used to check for update compliance The April 2026 Scan Cab was deployed before 10:30 AM PT on April 28, 2026 An updated version of the April 2026 Scan Cab was made available at 10:30 AM PT on April 28, 2026. This Scan Cab includes new metadata corresponding to updates for Visual Studio 2026. The Microsoft update for Visual Studio 2026 released on April 28, 2026, includes additional protections to address CVE-2026-40372: ASP.NET Core Elevation of Privilege Vulnerability. See the Additional information section of this message for details. How this affects your organization: IT administrators who downloaded the Scan Cab before 10:30 AM PT on April 28, 2026, should re-acquire and re-deploy it if the Scan Cab is used to assess updates for environments where Visual Studio 2026 is used. No action is required for environments where Scan Cab is not employed, or Visual Studio 2026 is not used. However, please note that there might be non-Microsoft applications that utilize Scan Cab. Review the documentation for any software and update deployment tools used in your organization to determine whether this applies to your environment. What you need to do to prepare: Administrators can download and deploy the updated Scan Cab using their usual processes. For more information, see the Additional information section below. Additional information: Updated Scan Cab: Download the new Scan Cab here CVE-2026-40372: ASP.NET Core Elevation of Privilege Vulnerability .NET 10.0.7 Out-of-Band Security Update: .NET Blog Visual Studio 2026 release notes Announcing a smaller WSUS Scan Cab - Microsoft Tech Community: Learn more about WSUS and the Scan Cab process Using WUA to Scan for Updates Offline - Win32 apps | Microsoft Docs: Windows Update Agent (WUA) can be used to scan computers for security updates without connecting to Windows Update WSUS and the Catalog Site | Microsoft Docs: The Catalog Site used by WSUS to import updates and drivers -
Assess Secure Boot certificate status with Microsoft Defender
MC1293341 · stayInformed · normal · Updated 04/27/2026 20:01
Services: Windows
Read message
Microsoft Defender now provides IT teams centralized visibility into Secure Boot 2023 certificate readiness across your device fleet. A new assessment categorizes your devices automatically as exposed, compliant, and not applicable. In the Defender portal, go to Exposure Management > Recommendations > Devices > Misconfigurations. For exposed devices, remediation guidance is directly available through the recommendation. When will this happen: The new Secure Boot 2023 certificate assessment is now available in Microsoft Defender. June 2026: Secure Boot 2011 certificates begin expiring and need to be replaced. How this will affect your organization: When certificates expire in June 2026, devices that haven't transitioned to the newer Windows UEFI CA 2023 certificates will no longer be able to receive new security protections for the early boot process. To help organizations prepare, Microsoft Defender introduced a new recommendation that provides centralized visibility into Secure Boot 2023 certificate readiness across your device fleet. What you need to do to prepare: From the Microsoft Defender portal, go to Exposure Management > Recommendations > Devices > Misconfigurations. Find the new recommendation “Ensure devices are updated to Secure Boot 2023 certificates and boot manager”. From the recommendation view, you can: Drill down into exposed devices and identify exactly which systems require attention. Filter by OS platform and device context to prioritize remediation efforts. Export device data to share with infrastructure and platform teams. Track rollout progress across your organization. Integrate findings into existing security posture workflows. Additional information: Learn more at Preparing for Secure Boot 2023 with Microsoft Defender. Learn more about Microsoft Secure Score for Devices - Microsoft Defender Vulnerability Management. Visit the comprehensive Secure Boot guidance at https://aka.ms/GetSecureBoot. -
New IT admin policy: Remove Microsoft Copilot app
MC1289507 · stayInformed · normal · Updated 04/23/2026 17:33
Services: Windows
Read message
Improve user experience with a single Microsoft Copilot app to use on any given device. The new RemoveMicrosoftCopilotApp policy setting allows you to uninstall Copilot from devices in your organization in a non-disruptive way. It only applies to devices and users that meet the following conditions: Microsoft 365 Copilot is also installed. Copilot wasn’t installed by the user. Copilot wasn’t launched in the last 28 days. It’s available as a Policy CSP and Group Policy. When will this happen: The policy is broadly available as of April 14, 2026. It’s part of the April 2026 Windows security update and later. How this will affect your organization: This policy simplifies the user experience by providing a single Copilot app to use on any given device. What you need to do to prepare: No action is needed if your organization prefers the default experience and allows users to use Copilot by choice. For scenarios that meet the conditions and require you to remove Copilot from organizational devices, set this policy as described in Additional information. You’ll need at least the April 2026 Windows security update to get this policy. Users will still have the option to reinstall Copilot if they choose to. Additional information: Learn more at WindowsAI Policy CSP. Get the April 14, 2026—KB5083769 (OS Builds 26200.8246 and 26100.8246) security update. -
Ask Microsoft Anything about Secure Boot certificate updates
MC1288264 · stayInformed · normal · Updated 04/22/2026 18:43
Services: Windows
Read message
Microsoft is hosting two upcoming Ask Microsoft Anything (AMA) events focused on updating Secure Boot certificate updates across your Windows estate before certificate expirations begin in June 2026. These AMAs are designed to help you get clarity on what’s changing and how to plan for deployment across your environment. Bring your questions and get practical guidance directly from Microsoft experts. When will this happen: Secure Boot certificates on Windows devices begin expiring in June 2026. The upcoming AMAs will take place on April 23, 2026 and May 18, 2026. What you need to do to prepare: Review the Secure Boot playbook to understand requirements, affected scenarios, and available tooling, then add one or both upcoming AMAs to your calendar: Secure Boot AMA – April 23, 2026, 8:00 AM PDT Secure Boot AMA – May 18, 2026, 8:00 AM PDT Post your questions in the comments section of each page early and often. If you don’t see the ability to post a comment, make sure you are signed in to the Microsoft Tech Community. Additional information: For continued guidance and updates, bookmark the Secure Boot playbook and https://aka.ms/GetSecureBoot. -
An updated version of the April 2026 Scan Cab is available
MC1287681 · stayInformed · normal · Updated 04/22/2026 05:08
Services: Windows
Read message
IMPORTANT: This notice is only relevant for environments where: ASP.NET Core is used Scan Cab is used to check for update compliance The April 2026 Scan Cab was deployed before 10:00 PM PT on April 21, 2026 An updated version of the April 2026 Scan Cab was made available at 10:00 PM PT on April 21, 2026. This Scan Cab includes new metadata corresponding to updates for ASP.NET Core. The Microsoft update for ASP.NET Core released on April 21, 2026, includes additional protections to address CVE-2026-40372: ASP.NET Core Elevation of Privilege Vulnerability. See the Additional information section of this message for details. How this affects your organization: IT administrators who downloaded the Scan Cab before 10:00 PM PT on April 21, 2026, should re-acquire and re-deploy it if the Scan Cab is used to assess updates for environments where ASP.NET Core is used. No action is required for environments where Scan Cab is not employed or ASP.NET Core is not used. However, please note that there might be non-Microsoft applications that utilize Scan Cab. Review the documentation for any software and update deployment tools used in your organization to determine whether this applies to your environment. What you need to do to prepare: Administrators can download and deploy the updated Scan Cab using their usual processes. For more information, see the Additional information section below. Additional information: Updated Scan Cab: Download the new Scan Cab here CVE-2026-40372: ASP.NET Core Elevation of Privilege Vulnerability Announcing a smaller WSUS Scan Cab - Microsoft Tech Community: Learn more about WSUS and the Scan Cab process Using WUA to Scan for Updates Offline - Win32 apps | Microsoft Docs: Windows Update Agent (WUA) can be used to scan computers for security updates without connecting to Windows Update WSUS and the Catalog Site | Microsoft Docs: The Catalog Site used by WSUS to import updates and drivers -
Take action: Out-of-band updates released for Windows Server to address two issues
MC1285472 · preventOrFixIssue · normal · Updated 04/19/2026 21:13
Services: Windows
Read message
Microsoft has released out-of-band (OOB) updates today, April 19, 2026, to address issues introduced by the April 2026 Windows security update. A limited number of Windows Server 2025 devices might experience failures installing the April 2026 security update (KB5082063). In addition, some versions of Windows Server may experience domain controllers restarting repeatedly after installing the April 2026 security update. To address these issues, Microsoft has released OOB updates for the Windows Server versions listed below. Note: The Windows Server 2025 OOB update (KB5091157) addresses both the installation failure issue and the domain controller restart issue. OOB updates released for other supported Windows Server versions address only the domain controller restart issue. For complete guidance and installation instructions, see the relevant KB articles: Standard Windows updates Windows Server 2025: KB5091157 (OS Build 26100.32698) Out-of-band Windows Server, version 23H2: KB5091571 (OS Build 25398.2276) Out-of-band Windows Server 2022: KB5091575 (OS Build 20348.5024) Out-of-band Windows Server 2019: KB5091573 (OS Build 17763.8647) Out-of-band Windows Server 2016: KB5091572 (OS Build 14393.9062) Out-of-band Windows hotpatch updates Windows Server 2025 Datacenter: Azure Edition: Hotpatch KB5091470 (OS Build 26100.32704) Out-of-band Windows Server 2022 Datacenter: Azure Edition: Hotpatch KB5091576 (OS Build 20348.5029) Out-of-band -
Interim guidance for Egypt DST changes 2026
MC1283618 · preventOrFixIssue · normal · Updated 04/17/2026 18:25
Services: Windows
Read message
For Windows devices in Egypt, a workaround is available for an issue affecting Daylight Saving Time (DST). Between April 24 and April 30, 2026, calendar events and meeting times in Egypt will appear off by one hour only for Windows Server 2016. This is due to a calendar edge case: a five-week April in 2026. Clocks will be correctly set to Egypt DST time zone on May 1, 2026, without any further intervention. If needed, a temporary workaround is available for the affected week. When will this happen: The workaround is available today. April 24-30, 2026: Affected devices might see calendar events off by an hour. May 1, 2026: Clocks will be correctly set to Egypt DST time zone without any further intervention, whether you use the workaround or not. How this will affect your organization: If your organization has devices affected by this issue and you don’t apply the workaround, the impact is as follows: Clocks will not be advanced by an hour at 12:00 a.m. on April 24, 2026, for the Egypt time zone until 12:00 a.m. on May 1, 2026. Clocks will be automatically advanced by an hour at 12:00 a.m. on May 01, 2026, for the Egypt time zone. If you apply the workaround, you can avoid this issue during the last week of April 2026. What you need to do to prepare: No action is needed if you don’t use Windows Server 2016, and all other devices use in-support versions of Windows. If your devices are affected, you can use a temporary registry setting workaround. No action is needed after May 1, 2026. On that date, all in-support systems will show the correct Egypt DST time automatically. Additional information: See complete guidance in Interim guidance for Egypt DST changes 2026. Visit the official policy page at Daylight saving time help and support. Learn How Windows manages time zone changes. -
Copilot entry point changes in Excel
MC1282571 · stayInformed · normal · Updated 04/16/2026 21:20
Services: Microsoft 365 apps, Microsoft 365 Copilot Chat
Read message
[Introduction] We’re updating how users access Copilot in Excel to provide a clearer, more consistent, and more intuitive experience across Microsoft 365 apps. These changes consolidate multiple Copilot entry points into a single, predictable location and establish Excel Edit Mode in the right-side chat pane as the primary Copilot interface. This update improves discoverability, simplifies user workflows, and aligns the Excel Copilot experience with other Microsoft 365 applications. [When this will happen:] General Availability (Worldwide): Rollout begins in late April 2026 and is expected to complete by early June 2026. General Availability (GCC, GCC High, and DoD): Rollout begins in early October 2026 and is expected to complete by late October 2026. [How this affects your organization:] Who is affected: All users of Microsoft 365 apps for Excel on Windows, macOS, and the web with Copilot enabled. A Microsoft 365 Copilot (Premium) license is required to use this feature. What will happen: Some Copilot entry points that appear when selecting a cell or opening the right-click menu will be removed. A single, consolidated Copilot entry point will appear in a consistent corner location within Excel. Screenshot: Updated Excel entry point: The Excel Agent in the right-side chat pane becomes the primary interface for Copilot prompts and responses. Copilot availability, licensing, and existing admin policies remain unchanged. The feature is on by default for users who already have Copilot access. [What you can do to prepare:] No action is required. You may optionally: Inform users about the updated Copilot entry points and chat-based experience in Excel. Update internal documentation or training materials if you reference specific Copilot buttons or menus. Notify helpdesk teams to prepare for user questions during rollout. [Compliance considerations:] Compliance area Explanation Does the change provide end users a new way of interacting with generative AI? Users will primarily interact with Copilot through the right-side chat pane instead of multiple in-context entry points within Excel. -
Microsoft Entra ID Governance: Azure subscription required to continue using guest governance features
MC1225192 · planForChange · normal · Updated 04/16/2026 17:18
Services: Microsoft Entra
Read message
Introduction Beginning January 30, 2026, Microsoft Entra ID Governance will require all tenants to have a linked Azure subscription to continue using Identity Governance features for guest users. This change ensures accurate billing for governance actions performed by guests and supports continued access to advanced governance capabilities. When this will happen: General availability and enforcement begin on January 30, 2026. How this will affect your organization: Who is affected: Organizations using Microsoft Entra ID Governance features for guest users (userType = Guest). Admins managing lifecycle workflows or Entra ID Governance features in entitlement management for external or guest identities. Access reviews will be included by March 31, 2026. What will happen: If your tenant does not have a linked Azure subscription, creation or updates of policies scoped to guest users using premium Entra ID Governance capabilities will be blocked. The following actions will be unavailable: Creating access reviews scoped to guest users (inactive user reviews, user-to-group affiliation helper) Creating or updating entitlement management policies involving guests, sponsor approvers, custom extensions, Verified ID, or auto-assignment rules Marking a guest as governed in entitlement management Directly assigning a guest user to an access package in entitlement management Creating or updating lifecycle workflows scoped to guest users. Existing policies will continue to run, but no new guest-governance actions can be authored without billing enabled. Once a subscription is linked, normal guest governance usage and billing will begin under the Monthly Active User (MAU) model. What you can do to prepare: Before January 30, 2026, link a valid Azure subscription to your tenant: Navigate to Entra ID → ID Governance → Dashboard In the Guest Access Governance panel, select Get Started Choose a subscription and resource group, then select Turn on Confirm your account has at least the Contributor role to enable subscription linking. Review any guest-scoped workflows, reviews, or entitlement policies that may require updates after subscription linking. Communicate this change to support teams or internal governance admins. Update internal documentation regarding: Guest governance prerequisites Subscription dependency Billing behavior for governance actions Learn more: Microsoft Entra ID Governance licensing for guest users | Microsoft Learn Compliance considerations: Question Explanation Does the change alter how existing customer data is processed, stored, or accessed? Guest-governance actions require a linked Azure subscription; creating or updating guest-scoped governance actions is blocked without subscription linkage. Does the change modify admin controls? Admins must link an Azure subscription to enable guest governance billing and can turn guest governance on or off in the Entra ID Governance dashboard. Does the change allow a user or admin to enable or disable the feature? Guest governance features can be enabled or disabled through the Guest Governance panel in the Entra ID Governance dashboard. -
The April 2026 Scan Cab is available
MC1280144 · stayInformed · normal · Updated 04/14/2026 23:41
Services: Windows
Read message
IMPORTANT: This notice only affects environments where Scan Cab is used to check for update compliance. The April 2026 Scan Cab was made available at 4:30 PM PT today, April 14, 2026. The Scan Cab can help determine whether a Windows device needs to install necessary security updates released by Microsoft without first connecting to the Windows Update service. How this affects your organization: The Wsusscn2.cab file is a cabinet file that is signed by Microsoft and contains information about Microsoft security-related updates. Devices that aren't connected to the Internet can be scanned to see whether these security-related updates are present or required. The Wsusscn2.cab file doesn't contain the security updates themselves so you must obtain and install any needed security-related updates through other means. What you need to do to prepare: You can download and deploy the April 2026 Scan Cab via the usual processes. For detailed guidance, see the Additional information section below. No action is required on environments where Scan Cab is not employed. However, please note that there might be non-Microsoft applications which utilize Scan Cab. Review the documentation for any software and update deployment tools used in your organization to understand if this is applicable in your environment. Additional information: Updated Scan Cab: Download the new Scan Cab here Announcing a smaller WSUS Scan Cab: Learn more about WSUS and the Scan Cab process Using WUA to Scan for Updates Offline: Windows Update Agent (WUA) can be used to scan computers for security updates without connecting to Windows Update WSUS and the Catalog Site: The Catalog Site used by WSUS to import updates and drivers -
Remote Desktop adds new safeguards for connections opened from RDP files
MC1279831 · planForChange · normal · Updated 04/14/2026 18:07
Services: Windows
Read message
Starting with the April 2026 Windows security update, Remote Desktop adds new safeguards to help reduce phishing attacks that misuse Remote Desktop (.rdp) files. These attacks attempt to trick devices into connecting to attacker‑controlled systems and sharing local resources without clear visibility. To address this, a new security dialog appears before any connection is made, showing the remote computer address, publisher information (when available), and any requested access to local resources. All requested settings are disabled by default and must be explicitly enabled. A one‑time security warning also appears the first time an RDP file is opened. When will this happen: This change takes effect with the April 2026 Windows security update. How this will affect your organization: Devices that open Remote Desktop (.rdp) files will see a new security dialog before a connection is established. The dialog shows the remote computer address, publisher information (when available), and any requested access to local device resources. All requested settings are turned off by default and must be explicitly enabled. In addition, a one‑time security warning appears the first time an RDP file is opened on a device after installing the update. This experience is intended to make potentially risky connections more visible and intentional. Connections that are started manually by entering a computer name directly in the Remote Desktop app are not affected. Note: On devices running Windows Server 2012 and Windows Server 2012 R2, the new dialog text is displayed in English only and is not localized. This does not affect functionality. What you need to do to prepare: Review any workflows, scripts, or automation that rely on launching Remote Desktop sessions by opening RDP files. Automated scenarios that previously launched connections without user interaction may require updates. Organizations that develop or use software built on Remote Desktop client components, including custom Remote Desktop clients, should review how those applications handle RDP file–based connections. Administrator and developer options are available for scenarios that require temporary compatibility adjustments, but doing so bypasses the enhanced security provided by this update and should be evaluated carefully. IT admins and support teams should be aware of the new dialogs so they can help explain the change if questions arise. Additional information Understanding security warnings when opening Remote Desktop (RDP) files Remote Desktop ActiveX control IMsRdpExtendedSettings Property property - Win32 apps | Microsoft Learn -
Notice: The April 2026 Scan Cab for Microsoft updates is delayed
MC1279832 · stayInformed · normal · Updated 04/14/2026 17:03
Services: Windows
Read message
Note: This notice only affects environments where Scan Cab is used to check for Microsoft update compliance. The Scan Cab for the April 2026 Microsoft security updates is currently delayed and has not yet been released. We will communicate an update on Scan Cab availability as more information becomes available. Thank you for your patience. How this affects your organization: IT administrators who rely on Scan Cab to check for update compliance can track our communications. Progress on the availability of this month's Scan Cab will be communicated when new information is available. Additional information: Learn more about the Scan Cab process: Announcing a smaller WSUS Scan Cab Use Windows Update Agent (WUA) to scan computers for security updates without connecting to Windows Update: Using WUA to Scan for Updates Offline - Win32 apps Documentation on the Catalog Site used to import updates and drivers: WSUS and the Catalog Site -
Second deployment phase for Kerberos RC4 hardening begins with the April 2026 Windows security update
MC1279830 · stayInformed · normal · Updated 04/14/2026 17:03
Services: Windows
Read message
Windows updates released April 2026 and later begin the second deployment phase of protections for a Kerberos information disclosure vulnerability (CVE‑2026‑20833). In this phase, domain controllers change default Kerberos ticket behavior for accounts that do not have an explicit Kerberos encryption configuration, shifting to AES‑SHA1-only by default. Environments with remaining RC4 dependencies may experience authentication issues unless those dependencies are remediated or explicitly configured. When this will happen: April 2026 - Enforcement Phase with manual rollback: With installation of the April 2026 Windows security update, default Kerberos behavior changes so domain controllers use AES‑SHA1-only encryption for accounts without explicit encryption type settings, and Enforcement mode is enabled by default on Windows domain controllers. Audit mode remains available as a manual rollback option until July 2026. July 2026 - Enforcement Phase: Audit mode is removed, leaving Enforcement mode as the only option. How this will affect your organization: With installation of the April 2026 Windows security update, domain controllers will default to issuing AES‑SHA1-encrypted tickets for accounts that do not explicitly define supported encryption types. Environments with service accounts, applications, or devices that still require RC4-based Kerberos tickets may see authentication or connection failures unless those dependencies are addressed. Kerberos-related events in the System event log can help identify and address misconfigurations or remaining dependencies that are likely to become incompatible as enforcement progresses. Note: For devices using Azure Files SMB with Active Directory–based authentication, address any RC4 dependencies before the Enforcement phase begins to reduce the risk of access disruption as Audit mode is removed in July 2026. Follow the steps in the official documentation to help maintain uninterrupted access to Azure Files and Azure Virtual Desktop. What you need to do to prepare: Monitor the System event log for Kerberos-related events indicating RC4 dependencies or insecure encryption configurations. If event log data shows RC4 reliance, remediate by moving to stronger encryption or explicitly configuring the account’s msds-SupportedEncryptionTypes attribute where RC4 is still required. Complete remediation before July 2026, when Audit mode is removed and Enforcement mode becomes the only available option. Note: Audit events related to this change are only generated when Active Directory is unable to issue AES‑SHA1 service tickets or session keys. The absence of audit events does not guarantee that all non-Windows devices will successfully accept Kerberos authentication after the April 2026 Enforcement phase begins. Validate non-Windows interoperability through testing before broadly enabling this behavior. Additional information: Read the full hardening guidance: How to manage Kerberos KDC usage of RC4 for service account ticket issuance changes related to CVE-2026-20833. Learn about RC4 usage in Windows and its risks: Detect and remediate RC4 usage in Kerberos. Learn more about the related vulnerability: CVE-2026-20833. -
The April 2026 Windows security update is now available
MC1279829 · stayInformed · normal · Updated 04/14/2026 17:03
Services: Windows
Read message
The April 2026 security update is now available for all supported versions of Windows. We recommend that you install these updates promptly. For more information about the contents of this update, see the release notes, which are easily accessible from the Windows 11 update history page. To learn more about the different types of monthly quality updates, see Windows monthly updates explained. Highlights for the Windows 11, version 25H2 update: This security update includes fixes and quality improvements from KB5079391 (released March 26, 2026 - no longer offered) and KB5086672 (released March 31, 2026). This update makes quality improvements to the servicing stack, which is the component that installs Windows updates. This update expands high confidence device targeting data, increasing coverage of devices eligible to automatically receive new Secure Boot certificates. Devices receive the new certificates only after demonstrating sufficient successful update signals, maintaining a controlled and phased rollout. This update improves reliability for SMB compression over QUIC, reducing timeouts and enabling more consistent and dependable performance. This update enhances protection against phishing attacks that use Remote Desktop (.rdp) files by showing all requested connection settings before connecting, with settings turned off by default and a one‑time security warning on first use. Short on time? Watch our Windows 11 release notes video for this month's tips. For instructions on how to install this update, see the KB for your operating system listed below: Windows 11, version 26H1: KB5083768 Windows 11, versions 25H2 and 24H2: KB5083769 Windows 11, version 23H2: KB5082052 Windows 11 Enterprise LTSC 2024: Baseline KB5083769 Windows 10, versions 22H2 and 21H2: KB5082200 Windows 10 Enterprise LTSC 2019 and Windows Server 2019: KB5082123 Windows 10 LTSB 2016 and Windows Server 2016: KB5082198 Windows Server 2025: KB5082063 Windows Server 2025 Datacenter: Azure Edition: Baseline KB5082063 Windows Server 2022: KB5082142 Windows Server 2022 Datacenter: Azure Edition: Baseline KB5082142 Windows Server 2012 R2: KB5082126 Windows Server 2012: KB5082127 Note: With the April 2026 Windows security update and upcoming Windows updates over the next few months, a limited number of consumer and business devices may experience one additional restart during installation. This one‑time restart occurs after a Secure Boot certificate update is applied as part of the Secure Boot update process. -
Broader Windows Autopatch availability to Microsoft 365 Government Community Cloud (GCC)
MC1278941 · stayInformed · normal · Updated 04/13/2026 17:47
Services: Windows
Read message
Next month, Windows Autopatch will become more broadly available in Government Community Cloud (GCC). Previously, Windows Autopatch was not automatically available for Microsoft 365 G3 and G5 SKUs in GCC. It required the $0 Windows Enterprise (OLS) activation SKU. Now, the OLS SKU is no longer needed. Windows Autopatch is included automatically with: Microsoft 365 G3 GCC Microsoft 365 GCC G5 Microsoft 365 GCC G5 without WDATP/CAS Unified When will this happen: Expected date of launch: May 13, 2026 How this will affect your organization: If you don't use the $0 Windows Enterprise (OLS) activation SKU, you’ll see new Windows Autopatch features in Microsoft Intune next month. These features include update policies for feature, quality, and driver updates, plus enhanced reporting. What you need to do to prepare: No action is needed. New capabilities will be available automatically in Microsoft Intune to help manage Windows updates. Learn more about using Windows Autopatch. Additional information: None -
Support for Office LTSC 2021, and additional apps will end on October 13, 2026
MC1278920 · planForChange · normal · Updated 04/13/2026 16:19
Services: Microsoft 365 suite
Read message
As previously communicated, support for Office LTSC 2021 will end on October 13, 2026. After that date, no further updates, security fixes, or technical support will be available for this version of Office. While the applications may continue to function, using unsupported software could lead to potential security risks, compliance risks, system incompatibilities, and other issues. Support for Visio LTSC 2021 and Microsoft Project LTSC 2021 and several other products will also end on October 13, 2026. Organizations using these products should upgrade as soon as possible to maintain security, compliance, and performance. [How this will affect your organization:] After end of support, Office LTSC 2021 suites and standalones will no longer receive security updates or other fixes, and no technical assistance will be available for devices still running them. Continuing to use unsupported software can expose your organization to security and compliance risks and may impact service reliability and performance. [What you need to do to prepare:] To mitigate these risks while maintaining access to desktop Office apps, we recommend upgrading devices to a Microsoft 365 or Office 365 suite that includes Microsoft 365 Apps (for enterprise or for business). Microsoft 365 Apps provides always-up-to-date versions of familiar apps like Word, Excel, and PowerPoint for desktop, mobile, and web with continuous support under the Modern Lifecycle Policy and is eligible for use with the Microsoft 365 Copilot add-on. Enterprises should look to Microsoft 365 E3, Office 365 E3, or Microsoft 365 Apps for enterprise. Organizations with fewer than 300 users should look to Microsoft 365 Business Premium, Microsoft 365 Business Standard, or Microsoft 365 Apps for business. For scenarios that require a fully disconnected solution, we recommend upgrading to Office LTSC 2024. Office LTSC 2024 includes a subset of the value in Microsoft 365 Apps and will be supported until October 2029 under the Fixed Lifecycle Policy. Take steps to prepare for this transition with the following resources: Read the upgrade guidance for an overview of how to move from Office LTSC 2021 to Microsoft 365 Apps. Consider engaging Microsoft FastTrack, a Microsoft support service, for moving to Microsoft 365. Plan ahead to avoid potential disruptions and keep your organization’s software environment secure and up to date. -
Windows Deployment Services (WDS): Hands-free deployment hardening (Phase 2)
MC1276259 · stayInformed · normal · Updated 04/10/2026 17:13
Services: Windows
Read message
As announced in January 2026, the unattend.xml file used in hands‑free deployment poses a vulnerability when transmitted over an unauthenticated RPC channel. Beginning with the April 2026 security update, the second phase of hardening for CVE-2026-0386 is now in effect. These changes make hands‑free deployment disabled by default to enforce secure behavior. After this update, hands‑free deployment no longer works unless explicitly overridden with registry settings. When will this happen: Starting with the April 2026 security update, Windows Deployment Services (WDS) enforces secure‑by‑default behavior by automatically disabling hands‑free deployment. How this will affect your organization: After installing the April 2026 security update, hands‑free deployment is blocked to prevent unauthenticated access to unattend.xml, enforcing the hardening requirements for CVE-2026-0386. Any workflows that rely on unattend.xml‑based deployment will no longer function unless overridden with registry settings. What you need to do to prepare: Organizations that still require hands‑free deployment after installing the April 2026 security update must explicitly override the secure default by setting the AllowHandsFreeFunctionality registry value to 1, which keeps unattend.xml‑based deployments operational but reintroduces the security risks associated with CVE-2026-0386. When this override is used, devices will log diagnostic messages indicating that they are operating in an insecure mode. Because this configuration is not recommended for long‑term use, IT admins should plan to migrate to alternate deployment solutions and return to secure‑by‑default behavior. Additional information: Read the full hardening guidance: Windows Deployment Services (WDS) Hands-Free Deployment Hardening Guidance related to CVE-2026-0386. Learn more about the related vulnerability: CVE-2026-0386. See deployment alternatives: Windows Deployment Services (WDS) boot.wim support. Explore cloud-based solutions: Windows Autopilot and Windows Autopilot device preparation documentation. -
Hardening administrative actions: Windows imaging, cloning, and auth workflows
MC1275343 · stayInformed · normal · Updated 04/09/2026 17:01
Services: Windows
Read message
Administrative actions are undergoing hardening changes that might require operational change to support your organization’s security posture. With the August 2025 Windows non-security update, devices were hardened against unauthorized attempts to bypass loopback detection. However, if you’ve cloned machines without Sysprep, you might see Kerberos and NTLM authentication failures. This is by design. The recommended solution is to rebuild affected devices using supported imaging methods. A temporary workaround is also available. When will this happen: September 2025 and later: Windows security updates include hardening changes that strengthen the trust boundary between identity, authentication, and User Account Control (UAC). April 2026 and later: Windows security updates include a temporary workaround for machines cloned without Sysprep. This registry-based compatibility option isn’t recommended. It reduces security protections introduced by recent updates. End of 2027: The temporary workaround expires. How this will affect your organization: This affects your organization if: You manage devices on Windows 11, version 24H2 and later or Windows Server 2025. You installed the August 2025 non-security update or September 2025 security update (or later) on these devices. You notice Kerberos or NTLM authentication failures. These failures surface as LsaSrv Event ID 6167 in the System event log of the target machine. You need to adjust your strategy to clone Windows images. What you need to do to prepare: Take the following actions: Stop any automation that clones devices without Sysprep. If not addressed, devices end up with duplicate security IDs (SIDs). Rebuild all devices with duplicate SIDs from scratch, then run Sysprep. It's not sufficient to unjoin devices and run Sysprep. If needed for transition only, temporarily roll back the hardening change with a registry-based option. Please contact Microsoft Commercial Customer Service and Support (CSS) to get information about this registry value. For details and instructions, review Hardening administrative actions: What IT pros need to know. Additional information: Hardening administrative actions: What IT pros need to know KB5070568: Kerberos and NTLM authentication failures due to duplicate SIDs KB5068222: Strengthening administrator protection and Kerberos authentication The Microsoft policy for disk duplication of Windows installations Sysprep -
Windows Office Hours: April 16, 2026
MC1275342 · stayInformed · normal · Updated 04/09/2026 17:01
Services: Windows
Read message
If you are an IT admin with questions about managing and updating Windows, we want to help. Every third Thursday of the month, we host a live chat-based event on the Tech Community called Windows Office Hours. Members of the Windows, Microsoft Intune, Windows Autopilot, Windows Autopatch, and Windows 365 engineering teams will be standing by to answer your questions. Want to attend the April 16 session of Office Hours? Add it to your calendar and select Attend on the event page to let us know you’re coming. There is no video or live meeting component. Simply visit the event page, log in to the Tech Community, and leave your questions in the Comments section. You can also bookmark https://aka.ms/Windows/OfficeHours for upcoming dates (and the ability to add this event to your calendar). We look forward to helping you. -
Extended Security Updates (ESU) available for Windows 10 Enterprise LTSB 2016
MC1274396 · stayInformed · normal · Updated 04/08/2026 19:58
Services: Windows
Read message
If your organization relies on Windows 10 Enterprise LTSB 2016, you know it’s nearing end of support on October 13, 2026. While the long-term solution is upgrading to a newer LTSC release, another temporary solution is available as of April 1, 2026. Extended Security Updates (ESU) are now available for purchase through Volume Licensing or a Microsoft Cloud Solution Provider (CSP). When will this happen: October 13, 2026: Devices on Windows 10 Enterprise LTSB 2016 will receive a final monthly security update. This date marks end of support (EOS) for this product. April 1, 2026: Extended Security Updates (ESU) are available as a temporary bridge to your next step. How this will affect your organization: After October 13, 2026, these devices will no longer receive Windows security updates, non-security updates, bug fixes, technical support, or online technical content updates. If your organization needs additional time to transition to a supported LTSC release, ESUs are available for up to three years. What you need to do to prepare: Read additional information to consider your options. Plan to upgrade these devices to a newer LTSC release as a long-term solution. Additional information: Plan for Windows Server 2016 and Windows 10 2016 LTSB end of support What's new in Windows 10 Enterprise LTSC 2016 Windows 10 2016 LTSB - Microsoft Lifecycle -
ESR management is moving to Windows Backup for Organizations
MC1274349 · stayInformed · normal · Updated 04/08/2026 17:16
Services: Windows
Read message
Starting May 2026, Enterprise State Roaming (ESR) management will transition to Windows Backup for Organizations. Windows Backup for Organizations is the enterprise‑grade solution for backing up and restoring Windows user settings and Microsoft Store app list. It’s designed to support device refresh, replacement, and upgrade scenarios (for example, moving to the latest version of Windows 11). ESR settings remain the same in scope. The only change is in how you manage these settings. This change aligns ESR‑managed settings with Windows Backup for Organizations policies. You can now manage and synchronize user settings with a policy‑based experience through Microsoft Intune or other mobile device management (MDM) providers. When will this happen: This change begins May 2026. You can manage ESR settings through both the Microsoft Entra portal and Windows Backup for Organizations policies for two months, until the end of June 2026. After that point, policies will be the only management option. How this will affect your organization: If you currently rely on ESR to synchronize user settings, plan to start managing ESR settings through Windows Backup for Organizations policies. Windows Backup for Organizations supports a broader set of Windows settings and is optimized for backup and restore scenarios. These scenarios include device replacement, reimaging, and OS upgrades. Users can pick up where they left off on a new or refreshed device, and you get clearer policy control and visibility. What you need to do to prepare: Review your current use of Enterprise State Roaming. Understand how to configure and manage Windows Backup for Organizations through Microsoft Intune or other MDM providers. To continue syncing users’ settings, configure the Windows Backup for Organizations backup policy in Microsoft Intune or another MDM provider. If you take no action, Windows will honor both ESR and Group Policy (GPO) or MDM roaming controls for one year (prioritizing GPO/MDM). After that, ESR will no longer work, and you’ll have to manage roaming through Windows Backup for Organizations policies. No action is required if your organization doesn’t use ESR or doesn’t require backup and restore of user settings and Microsoft Store app list. Additional information: For more details, review the Windows Backup for Organizations official documentation to understand supported settings, storage behavior, and restore experiences. Additionally, see: Differences between Enterprise State Roaming and Windows Backup for Organizations How to configure backup and restore policies in Microsoft Intune -
Replacement of the Microsoft SaRA command-line utility in Windows
MC1269727 · stayInformed · normal · Updated 04/03/2026 17:00
Services: Windows
Read message
Migrate away from the Microsoft Support and Recovery Assistant utility (SaRA). This command-line utility is deprecated to help secure and harden your environment. The Get Help command-line tool has similar capabilities and is recommended as a replacement for the SaRA utility. You’ll need to download it and use GetHelpCmd.exe to run your scenarios. When will this happen: March 10, 2026: Microsoft has officially removed the SaRA utility from all in-support versions of Windows. The Get Help command-line tool has been available for some time now. How this will affect your organization: The infrastructure powering GetHelpCmdLine includes improved security. The core functionality of GetHelpCmdLine and SaraCmdLine remains the same. All the scenarios supported in SaRACmdLine tool are supported as-is in GetHelpCmdLine. All SaRA scripts are migrated to GetHelpCmdLine. These scripts no longer work in the SaRACmdLine environment. What you need to do to prepare: As your next steps, Download the Get Help command-line tool. Use GetHelpCmd.exe to run your scenarios. Additional information: Read the announcement in Microsoft Support and Recovery Assistant (SaRA) command-line utility removal from Windows. Command line version of Get Help. Download the Get Help command-line tool. -
Enable Secure Boot certificate update status in the Windows Security app
MC1268714 · stayInformed · normal · Updated 04/02/2026 17:05
Services: Windows
Read message
Starting April 2026, the Windows Security app can show users the status of their Secure Boot certificate updates. This experience is disabled by default on enterprise-managed Windows 10 and Windows 11 client devices and Windows Server. If you want to enable this experience for devices in your organization, see the complete guidance at IT admin guide: Secure Boot certificate update status in the Windows Security app. When will this happen: In April 2026, this enhancement brings green, yellow, and red-color badges to Device security > Secure Boot. In May 2026, notifications will appear outside the app (such as system alerts). In late June 2026, the 2011 Secure Boot certificates begin expiring. Devices need updated 2023 certificates by this date to remain protected and productive. How this will affect your organization: This feature is available in Windows 11, Windows 10, Windows Server 2025, Windows Server 2022, and Windows Server 2019. It’s disabled by default on enterprise IT-managed devices. If enabled, visual indicators and warnings can help users know their Secure Boot certificate update status. If action is required, notifications will guide users to take appropriate steps. This isn’t a replacement but a complement to the IT monitoring and deployment guidance in Secure Boot playbook for certificates expiring in 2026. What you need to do to prepare: If you don’t wish to enable this feature for users at your organization, no action is required. On the contrary, please use the registry key guidance in IT admin guide: Secure Boot certificate update status in the Windows Security app. See additional information for more helpful resources. Additional information: See complete information at IT admin guide: Secure Boot certificate update status in the Windows Security app. If you enable this feature, share this user-focused KB article with them: Secure Boot certificate update status in the Windows Security app. For comprehensive review of Secure Boot certificate updates, visit https://aka.ms/GetSecureBoot. For devices that don’t have these certificates applied, use the specific monitoring and deployment methods described in the Secure Boot playbook. For Windows Server, see Windows Server Secure Boot playbook for certificates expiring in 2026. -
Take Action: Out-of-band update to address an issue affecting installation of the March 2026 non-security preview update
MC1266857 · stayInformed · normal · Updated 03/31/2026 21:02
Services: Windows
Read message
Microsoft has identified an issue affecting installation of the March 2026 Windows non-security preview update on some devices running Windows 11, versions 25H2 and 24H2. While installing the update, the following error might occur: “Some update files are missing or have problems. We’ll try to download the update again later. Error code: (0x80073712)” An out-of-band (OOB) update was released today, March 31, 2026, to address this installation issue. This cumulative OOB update for Windows 11, versions 25H2 and 24H2 (KB5086672) supersedes all previous updates and includes all protections and improvements from the March 2026 Windows security and non-security preview updates, as well as this installation fix. Devices running Windows 11, versions 25H2 and 24H2 with Get the latest updates as soon as they’re available turned on may see this update offered automatically through Windows Update when it becomes available for their device. If this setting is turned off, you can install the update manually by going to Settings > Windows Update and selecting Download & install. It is also available for manual download from the Microsoft Update Catalog. For more information, refer to KB5086672 (OS Builds 26200.8117 and 26100.8117) Out-of-band. -
(Updated) The March 2026 Windows non-security preview update is now available
MC1262522 · stayInformed · normal · Updated 03/31/2026 21:02
Services: Windows
Read message
(Updated 3-31-2026: The March 2026 Windows non-security preview update has been replaced with out-of-band update KB5086672 for Windows 11, versions 25H2 and 24H2. The Windows 11 links in this message have been updated to reflect this change.) The March 2026 non-security preview update is now available for Windows 11, versions 26H1, 25H2, and 24H2. Information about the contents of this update is available from the release notes, which are accessible from the Windows 11 update history page. To learn more about the different types of monthly quality updates, see Windows monthly updates explained. Looking to explore upcoming features and improvements in Windows 11? Check out the Windows roadmap. It includes what’s coming to the Windows Insider Program, what’s gradually rolling out, and what’s generally available. Highlights for the Windows 11, version 25H2 update: Narrator now provides rich image descriptions on Copilot+ PCs and works with Copilot on all Windows 11 devices, allowing users to get instant on‑device descriptions or ask Copilot for more detail. This update improves the design of the dialog boxes in Settings > Accounts > Other users to match the modern Windows look and support dark mode. The visibility of the dialog box option depends on whether the device has a domain joined work or school account. This update improves the File Explorer experience, including more reliable unblocking of downloaded files and support for Voice Typing when renaming files. This update delivers several display improvements, including support for refresh rates above 1000 Hz, improved auto‑rotation and HDR reliability, and better power efficiency for USB4‑connected monitors during sleep. For instructions on how to install this update, see the KB for your operating system listed below: Windows 11, version 26H1: KB5079489 Windows 11, versions 25H2 and 24H2: KB5086672 -
(Updated) Copilot entry point changes in Word and handoff to Agent in chat
MC1240704 · planForChange · normal · Updated 03/27/2026 21:52
Services: Microsoft 365 apps
Read message
Updated March 27, 2026: We have updated the timeline. Thank you for your patience. [Introduction] We are updating the entry points for Copilot in Word to provide a clearer, more consistent, and more intuitive experience. These changes unify how users access Copilot and introduce Word Agent in the chat pane as the primary Copilot interface. This update improves discoverability, simplifies the user workflow, and creates consistency with other Microsoft 365 apps. [When this will happen] General Availability (Worldwide): We will begin rolling out in early April 2026 (previously late March) and expect to complete by June 2026 (previously late April). General Availability (GCC, GCCH and DoD): We will begin rolling out in October 2026 (previously late March) and expect to complete by late October 2026 (previously late April). [How this affects your organization] Who is affected All users of Microsoft 365 apps for Word on Windows, macOS, and Web. What will happen The existing Copilot entry point in the left margin will be replaced by a consolidated entry point positioned in a consistent corner location. Users will see contextual Copilot entry points when selecting content:Windows and Web: inside the selection floatie Mac: in the right‑click context menu Word Agent in the right-side chat pane becomes the primary Copilot experience for prompts and responses. All Copilot entry points—consolidated and contextual—will connect to Word Agent to ensure a unified experience. There is no change to admin configuration, policy behavior, or Copilot availability settings. [What you can do to prepare] No action is required. You may optionally: Inform your users about the new Copilot access points and updated experience in Word. Update internal help content or training materials if you document Copilot entry points. [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
New resources to help organizations prepare for Secure Boot certificate expirations
MC1262523 · stayInformed · normal · Updated 03/26/2026 21:06
Services: Windows
Read message
Secure Boot certificates begin expiring in June 2026, and IT admins should take action now to help ensure devices remain secure. Timely deployment of updated certificates is essential to preserving device startup integrity and avoiding servicing (i.e., updates) disruptions. New guidance has recently been published to support a range of deployment scenarios. Whether your organization manages certificates through Microsoft Intune, Group Policy, or manual processes, the resources below provide detailed steps, recommended practices, and troubleshooting guidance to help you plan your updates: Updates and announcements – This page consolidates ongoing updates, milestones, and rollout status changes for the deployment of new Secure Boot certificates across Windows devices. Use it to stay current on important servicing communications as the deployment progresses. Sample Secure Boot E2E Automation Guide – This guide provides an end-to-end view of the PowerShell‑based automation system for deploying Secure Boot certificate updates using Group Policy to domain-joined machines in a controlled, graduated manner. It includes details, examples, and operational guidance for domain‑joined environments. A Closer Look at the High Confidence Database – This article explains how Secure Boot confidence levels are calculated, how data is evaluated and published, and how Windows servicing uses this information to determine certificate deployment readiness. It’s designed for IT pros, security teams, and support engineers who need deeper insights into certificate evaluation. When will this happen: These resources are available now. IT admins should begin reviewing the new guidance and complete certificate update planning and deployment activities as soon as possible to ensure devices remain protected and to avoid servicing or startup disruptions. Secure Boot certificate expiration begins in June 2026. How will this affect your organization: Devices that do not receive the updated Secure Boot certificates before expiration may encounter startup integrity issues or Windows servicing interruptions. The new resources provide guidance for organizations using Microsoft Intune, Group Policy, or manual processes and help ensure devices are fully prepared for upcoming certificate changes. What you need to do to prepare: Begin developing and executing your Secure Boot certificate update strategy as soon as possible. Review the newly published resources to determine the best approach for your organization. These new resources provide detailed steps, recommended practices, and insights to support planning, automation, and certificate update readiness. Additional Information: Updates and announcements Sample Secure Boot E2E Automation Guide A Closer Look at the High Confidence Database -
(Updated) [Reminder] Microsoft Teams Premium Self-Service Trials (Originally announced in MC670435)
MC1181209 · stayInformed · normal · Updated 03/25/2026 19:21
Services: Microsoft Teams
Read message
Updated March 25, 2026: We have updated the content. Thank you for your patience. [Introduction] We are resurfacing MC670435, published September 2023 to remind admins of the Microsoft Teams Premium self-service trial capability. This message serves as a reminder as we begin a broader rollout of the feature announced in 2023. As we expand rollout and introduce additional entry points for this feature, we want to ensure continued awareness and readiness. [When this will happen:] Ongoing rollout. [How this will affect your organization:] When rolled out, users within your organization will be able to directly initiate a Teams Premium trial. These self-service trial licenses will be a part of your Microsoft organizational tenant, and you will be able to manage these licenses like other Microsoft subscriptions. You will be able to cancel these trial licenses at any time. If you choose to disable the self-serve trials, please refer to self-service trial controls. After disabling the policy, it may take between 24-72 hours for the trial entry point to be removed from Teams. We also recommend fully restarting the app (quit and relaunch) to ensure the change is reflected. You will also be able to fully control whether trials are converted to paid subscriptions. Users will not need to input payment information when signing up. If a user would like to convert to a paid license, they must work with you directly to do so as there is no auto-renew functionality for these trials. If a user isn’t upgraded to a paid subscription, all services included in their Microsoft Teams Premium will end, and the user may lose read only access to data generated by Teams Premium, stored in Microsoft Teams, OneDrive, and SharePoint. Users in tenants where self-service trials are disabled may still see the “Get Premium” prompt when accessing features that require a premium license. This is expected behavior and helps signal user interest to admins. It can also help identify which users in your organization may need a Teams Premium license, allowing you to better manage and allocate your available licenses. To reduce confusion and prevent users from submitting license requests, admins can customize the license request flow. Instead of showing the default request form, they can configure a custom message explaining that license requests are not supported in their organization. For setup instructions, see Use your own request process – Microsoft Learn. Microsoft Teams Premium helps make your Teams meetings more intelligent, protected, and engaging. Unlike other meeting and collaboration tools, Teams Premium brings advanced capabilities for meetings, virtual appointments, and webinars together for one low cost. You can learn more about Teams Premium here. The customer data for all services associated with the Microsoft Teams Premium trial will be handled in accordance with the Microsoft Online Subscription Agreement and the Product Terms. [What you need to do to prepare:] Global or billing admins can use the same self-service purchase controls to disable self-service trials while making use of subscription management capabilities to oversee and manage trial licenses on the Your Products page in the Billing section of Microsoft 365 admin center. Note: This is a new Teams Premium trial and is enabled or disabled independently of past trial offerings. Review our updated self-service purchase and trial documentation here. We’ve added important information about the way trials work, the data that is collected, and the terms that apply. -
Take Action: Out-of-band update released to address an issue signing in to apps with a Microsoft account
MC1258087 · preventOrFixIssue · normal · Updated 03/21/2026 21:07
Services: Windows
Read message
Microsoft has identified an issue affecting signing in to apps using a Microsoft account. After installing the March 2026 Windows security update, some users might be unable to sign in to Microsoft apps and services. During sign‑in, users might see a “no internet” error even when the device has a working internet connection. This issue affects only Microsoft account sign‑in scenarios; organizations using Microsoft Entra ID for app authentication are not affected. An out-of-band (OOB) update was released today, March 21, 2026, to address this issue. This cumulative update includes all protections and improvements from the March 2026 Windows security update released March 10, 2026. This OOB update is available for Windows 11, versions 25H2 and 24H2 devices that receive standard Windows updates. It can be installed through Windows Update or the Microsoft Update Catalog. For more information, refer to the KB article KB5085516 (OS Builds 26200.8039 and 26100.8039) Out-of-band. -
(Updated) Second deployment phase for Kerberos RC4 hardening begins with the April 2026 Windows security update
MC1254512 · preventOrFixIssue · normal · Updated 03/20/2026 19:58
Services: Windows
Read message
Updated March 20, 2026: Added additional guidance for devices using Azure Files SMB with Active Directory–based authentication and Azure Virtual Desktop. Windows updates released April 2026 and later introduce the second deployment phase of protections for a Kerberos information disclosure vulnerability (CVE‑2026‑20833). In this phase, domain controllers change default Kerberos ticket behavior for accounts that do not have an explicit Kerberos encryption configuration, shifting to AES‑SHA1-only by default. Environments with remaining RC4 dependencies may experience authentication issues unless those dependencies are remediated or explicitly configured. When this will happen: April 2026 - Enforcement Phase with manual rollback: Default Kerberos behavior changes so domain controllers use AES‑SHA1-only encryption for accounts without explicit encryption type settings, and Enforcement mode is enabled by default on Windows domain controllers. Audit mode remains available as a manual rollback option until July 2026. July 2026 - Enforcement Phase: Audit mode is removed, leaving Enforcement mode as the only option. How this will affect your organization: Beginning with the April 2026 Windows security update, domain controllers will default to issuing AES‑SHA1-encrypted tickets for accounts that do not explicitly define supported encryption types. Environments with service accounts, applications, or devices that still require RC4-based Kerberos tickets may see authentication or connection failures unless those dependencies are addressed. Kerberos-related events in the System event log can help identify and address misconfigurations or remaining dependencies that are likely to become incompatible as enforcement progresses. Note: For devices using Azure Files SMB with Active Directory–based authentication, address any RC4 dependencies before the Enforcement phase begins to reduce the risk of access disruption as Audit mode is removed in July 2026. Follow the steps in the official documentation to help maintain uninterrupted access to Azure Files and Azure Virtual Desktop. What you need to do to prepare: Monitor the System event log for Kerberos-related events indicating RC4 dependencies or insecure encryption configurations. If event log data shows RC4 reliance, remediate by moving to stronger encryption or explicitly configuring the account’s msds-SupportedEncryptionTypes attribute where RC4 is still required. Complete these actions before July 2026, when Audit mode is removed and Enforcement mode becomes the only available option. Note: Audit events related to this change are only generated when Active Directory is unable to issue AES‑SHA1 service tickets or session keys. The absence of audit events does not guarantee that all non-Windows devices will successfully accept Kerberos authentication after the April 2026 Enforcement phase begins. Validate non-Windows interoperability through testing before broadly enabling this behavior. Additional information: Read the full hardening guidance: How to manage Kerberos KDC usage of RC4 for service account ticket issuance changes related to CVE-2026-20833. Learn about RC4 usage in Windows and its risks: Detect and remediate RC4 usage in Kerberos. Learn more about the related vulnerability: CVE-2026-20833. -
Microsoft Teams: Manage multiple phone numbers within one Teams account
MC1253752 · planForChange · normal · Updated 03/16/2026 22:32
Services: Microsoft Teams
Read message
[Introduction] Teams Phone user multi-line provides greater flexibility for organizations whose users manage multiple business numbers. This capability allows administrators to assign up to 10 telephone numbers to a single Teams Phone user, all within one Teams account. Users can make and receive calls from multiple numbers across Teams desktop, Teams mobile, and Teams devices without switching accounts or hardware. This enhancement supports a familiar and localized calling experience for users who work across regions, roles, or business lines. This capability supports scenarios such as: Establishing local presence across multiple regions Supporting users with multiple roles or responsibilities Allowing executives, assistants, or support teams to manage multiple business lines within one Teams account This message applies to Teams for Windows desktop, Teams for Mac desktop, and Teams for the web. It is associated with Microsoft 365 Roadmap ID 557716. [When this will happen:] Targeted Release: We will begin rolling out in early April 2026 and expect to complete by late April 2026. General Availability (Worldwide): We will begin rolling out in late April 2026 and expect to complete by mid-May 2026. [How this will affect your organization:] Who is affected: Organizations using Microsoft Teams Phone Teams administrators who manage phone number assignments Users assigned more than one business telephone number A Teams Phone license is required to use this feature What will happen: Admins can assign up to 10 telephone numbers to a single Teams Phone user. Assigned numbers appear as separate lines in the Calls app in Microsoft Teams. Additional numbers automatically appear for users after assignment; no user configuration is required. This feature is Off by default. Admin must configure for it to be available to users. [What you can do to prepare:] No action is required before this feature rolls out. After the feature becomes available, administrators can: Review which users may benefit from having multiple phone numbers. Assign and manage additional telephone numbers in the Microsoft Teams admin center. Confirm that each telephone number has a valid emergency address configured. Ensure assigned numbers comply with regional telecommunications regulations and existing Teams Phone requirements. Managing multi-line number assignments requires the Teams Administrator role (or equivalent permissions). Before rollout, we will update this post with new documentation. [Compliance considerations:] No compliance considerations identified, review as appropriate for your organization. -
Out-of-band hotpatch update released to address an issue affecting Bluetooth device visibility
MC1253720 · stayInformed · normal · Updated 03/16/2026 21:03
Services: Windows
Read message
Microsoft has identified an issue affecting hotpatch-enabled Enterprise editions of Windows where Bluetooth devices may not appear on the Bluetooth & devices page in Windows Settings or in Quick Settings, even though the devices are connected and functioning as expected. In addition, users might be unable to add Bluetooth devices because available devices do not appear in the connection list. This issue was identified in Microsoft’s internal environment and is expected to affect a limited set of Enterprise devices running Windows hotpatch updates. An out-of-band (OOB) hotpatch update (KB5084897) was released today, March 16, 2026, to address this issue. This cumulative update includes all protections and improvements from the March 2026 Windows hotpatch updates released on March 10 and March 13, 2026. This OOB hotpatch update is offered only to hotpatch‑enabled Windows 11, versions 25H2 and 24H2 Enterprise devices, and installs automatically without requiring a device restart. This update will not be offered to Enterprise devices that receive standard Windows updates. For more information, refer to the KB article March 16, 2026—Hotpatch KB5084897 (OS Builds 26200.7984 and 26100.7984) Out-of-band. -
Out-of-band update released for Windows Enterprise client devices running hotpatch updates
MC1250975 · preventOrFixIssue · normal · Updated 03/13/2026 18:59
Services: Windows
Read message
Microsoft has identified a security issue in the Windows Routing and Remote Access Service (RRAS) management tool that could allow remote code execution when connecting to a malicious server. This issue only applies to a limited set of scenarios involving Enterprise client devices running hotpatch updates and being used for remote server management. An out-of-band (OOB) hotpatch update (KB5084597) was released today, March 13, 2026, to address this issue. This cumulative update includes all protections and improvements from the March 2026 Windows security update released March 10, 2026. No action is required if: Your devices receive standard Windows updates. If you are not using the RRAS management tool on Windows devices running versions 25H2 or 24H2. This OOB hotpatch update is available for Windows 11, versions 25H2 and 24H2 devices enrolled in hotpatch updates and managed by Windows Autopatch. This update will install automatically through Windows Update and take effect without requiring you to restart your device. Learn more about Hotpatch updates. For more information, refer to the KB article March 13, 2026—Hotpatch KB5084597 (OS Builds 26200.7979 and 26100.7979) Out-of-band. -
Windows Deployment Services (WDS): Hands-free deployment hardening (Phase 2)
MC1250927 · stayInformed · normal · Updated 03/13/2026 17:09
Services: Windows
Read message
As announced in January 2026, the unattend.xml file used in hands‑free deployment poses a vulnerability when transmitted over an unauthenticated RPC channel. Beginning with the April 2026 security update, IT admins should prepare for the second phase of hardening for CVE-2026-0386. These changes will make hands‑free deployment disabled by default to enforce secure behavior. After this update, hands‑free deployment will no longer work unless explicitly overridden with registry settings. When will this happen: Starting with the April 2026 security update, Windows Deployment Services (WDS) will enforce secure‑by‑default behavior by automatically disabling hands‑free deployment. How this will affect your organization: After installing the April 2026 security update, hands‑free deployment will be blocked to prevent unauthenticated access to unattend.xml, enforcing the hardening requirements for CVE-2026-0386. Any workflows that rely on unattend.xml‑based deployment will no longer function unless overridden with registry settings. What you need to do to prepare: Organizations that still require hands‑free deployment after installing the April 2026 security update must explicitly override the secure default by setting the AllowHandsFreeFunctionality registry value to 1, which keeps unattend.xml‑based deployments operational but reintroduces the security risks associated with CVE-2026-0386. When this override is used, devices will log diagnostic messages indicating that they are operating in an insecure mode. Because this configuration is not recommended for long‑term use, IT admins should plan to migrate to alternate deployment solutions and return to secure‑by‑default behavior. Additional information: Read the full hardening guidance: Windows Deployment Services (WDS) Hands-Free Deployment Hardening Guidance related to CVE-2026-0386. Learn more about the related vulnerability: CVE-2026-0386. See deployment alternatives: Windows Deployment Services (WDS) boot.wim support. Explore cloud-based solutions: Windows Autopilot and Windows Autopilot device preparation documentation. -
Windows Office Hours: March 19, 2026
MC1250021 · stayInformed · normal · Updated 03/12/2026 17:55
Services: Windows
Read message
If you are an IT admin with questions about managing and updating Windows, we want to help. Every third Thursday of the month, we host a live chat-based event on the Tech Community called Windows Office Hours. Members of the Windows, Microsoft Intune, Windows Autopilot, Windows Autopatch, and Windows 365 engineering teams will be standing by to answer your questions. We also have experts from FastTrack, the Customer Acceleration Team, and Microsoft public sector teams. Want to attend the March 19 session of Office Hours? Add it to your calendar and select Attend on the event page to let us know you’re coming. There is no video or live meeting component. Simply visit the event page, log in to the Tech Community, and leave your questions in the Comments section. You can also bookmark https://aka.ms/Windows/OfficeHours for upcoming dates (and the ability to add this event to your calendar). We look forward to helping you. -
RSAT capabilities arrive on Arm-based Windows 11 PCs
MC1248343 · stayInformed · normal · Updated 03/10/2026 20:01
Services: Windows
Read message
You can now use familiar Remote Server Administration Tools (RSAT) on Arm-based Windows 11 devices. With the February 2026 non-security preview update, five of the most widely used RSAT components are available for everyday system administrator tasks. Add users to Active Directory, edit GPOs, configure NDS and DHCP servers, and more. When will this happen: Starting with the February 2026 non-security preview update How this will affect your organization: For the past several years, if you’ve used Windows on Arm, you had to rely on alternative management methods (such as Windows Admin Center) or switch to an x64 device for certain tasks. Similarly, testing newer Arm-powered laptops for your enterprise highlighted the pressing need for RSAT support on Arm64 devices. With RSAT support, Windows 11 on Arm becomes a more viable platform for enterprise IT management. What you need to do to prepare: This improvement comes to Windows 11, versions 25H2 and 24H2 on Arm, as well as Windows 11, version 26H1. Please install the February 2026 non-security preview update or later. Additional information: Learn why RSAT on Arm64 matters and how to enable it in RSAT capabilities arrive on Arm-based Windows 11 PCs. -
The March 2026 Windows security update is now available
MC1248239 · stayInformed · normal · Updated 03/10/2026 17:09
Services: Windows
Read message
The March 2026 security update is now available for all supported versions of Windows. We recommend that you install these updates promptly. For more information about the contents of this update, see the release notes, which are easily accessible from the Windows 11 update history page. To learn more about the different types of monthly quality updates, see Windows monthly updates explained. Highlights for the Windows 11, version 25H2 update: This security update includes improvements that were a part of update KB5077181 (released February 10, 2026). This update makes quality improvements to the servicing stack, which is the component that installs Windows updates. This update adds high‑confidence device targeting, expanding coverage for automatic Secure Boot certificate delivery. This update improves File Explorer search reliability when searching across multiple drives or "This PC". This update improves the reliability of choosing trusted catalog files. It adds a warning dialog that helps you confirm that the file you select comes from a trusted source. Short on time? Watch our Windows 11 release notes video for this month's tips. For instructions on how to install this update, see the KB for your operating system listed below: Windows 11, version 26H1: KB5079466 Windows 11, versions 25H2 and 24H2: KB5079473 Windows 11, version 23H2: KB5078883 Windows 11 Enterprise LTSC 2024: Hotpatch KB5079420 Windows 10, versions 22H2 and 21H2: KB5078885 Windows 10 Enterprise LTSC 2019 and Windows Server 2019: KB5078752 Windows 10 LTSB 2016 and Windows Server 2016: KB5078938 Windows Server 2025: KB5078740 Windows Server 2025 Datacenter: Azure Edition: Hotpatch KB5078736 Windows Server 2022: KB5078766 Windows Server 2022 Datacenter: Azure Edition: Hotpatch KB5078737 Windows Server 2012 R2: KB5078774 Windows Server 2012: KB5078775 -
Windows Autopatch is enabling hotpatch updates by default
MC1247859 · stayInformed · normal · Updated 03/09/2026 21:24
Services: Windows
Read message
Starting with the May 2026 Windows security update, Windows Autopatch is enabling hotpatch security updates by default because they are the quickest way to get secure. This change in default behavior will impact all eligible Microsoft Intune devices. Additional IT controls are coming in April. When will this happen: Devices will start receiving hotpatch updates by default with the May 2026 Windows security update. The tenant setting to opt out of hotpatch updates is scheduled to go live on April 1, 2026. How this will affect your organization: Devices that meet hotpatch prerequisites will get secure faster because full Windows security updates are applied without waiting for a restart. Devices are secured as soon as the update is installed. You don’t need to wait for devices to restart, saving on average three to five days. Devices will restart during baseline months, which are January, April, July, and October. What you need to do to prepare: If you already use Windows Autopatch, no action is needed to get hotpatch updates enabled by default. We recommend keeping hotpatch updates enabled for your devices. To maximize the number of devices receiving hotpatch updates, ensure they meet prerequisites. Most commonly, this means enabling Virtualization-based Security (VBS) for x86 devices. If you’re not ready for this change, you can opt out groups of devices using Quality Update policies or the whole tenant. Additional information: Read the announcement in Securing devices faster with hotpatch updates on by default. Learn more about hotpatch updates with the following resources: Hotpatch updates Hotpatch for Windows client now available Hotpatching now available for 64-bit Arm architecture Hotpatch for client: Frequently asked questions Transforming security and compliance at Microsoft Hotpatch efficiency unlocked: Smaller update size Inside hotpatch updates for Windows (YouTube video) Hotpatching 101: Enable virtualization-based security (VBS) (YouTube video) -
Upcoming events to help with Secure Boot updates
MC1245992 · stayInformed · normal · Updated 03/06/2026 21:04
Services: Windows
Read message
Do you need to update Secure Boot certificates across your organization before they start expiring in June 2026? Two events next week can help you with best practices and answers to your questions in real time. When will this happen: On March 9 at 7:30 AM PT (2:30 PM UTC) is Secure Boot certificate updates explained. This will be a fast-paced walkthrough of essential guidance - including how to test firmware, monitor device readiness, deploy updated certificates, and diagnose issues. Then, on March 12 at 8:00 AM PT (3:00 PM UTC), you can ask any questions you might have at the Secure Boot AMA. Members of the engineering team will be on camera and in the comments working to help with answers. What you need to do to prepare: Both events will take place on the Tech Community. Registration is not required, but you will need to sign in to the Tech Community with a Microsoft account in order to participate in the Q&A. Questions can be posted in advance or during the live streams. Visit the session pages for the option to “Add to calendar” and click “Attend” to receive event reminders. Additional information: To keep up with new Windows-related events for IT professionals, follow Windows Events on Tech Community. -
Windows news you can use: February 2026 recap
MC1244299 · stayInformed · normal · Updated 03/04/2026 22:04
Services: Windows
Read message
Catch up on important changes across Windows update management, Windows 365, security, and productivity with Windows news you can use for February 2026. Key announcements include general availability of the first sign‑in restore experience in Windows Backup for Organizations, new Start menu customization policies, expanded Windows 365 capabilities and regional availability, and guidance around Windows 11, version 26H1. On the security front, you’ll find a helpful list of new tools and resources to help you manage upcoming Secure Boot certificate expirations plus details on strengthened protections such as DPAPI key rotation and native Sysmon functionality in Windows. When will this happen: Some improvements summarized in this monthly recap are already available, while others are rolling out gradually. What you need to do to prepare: Read February's recap, which includes links to resources to help you start benefiting from the latest improvements. Additional information: To keep up with new capabilities and features as they are announced, follow the Windows IT Pro Blog, Microsoft Security Blog, and Windows 11 update history. -
Microsoft Teams Rooms on Android: License-based management updates for DM-synced devices
MC1242781 · stayInformed · normal · Updated 03/03/2026 00:02
Services: Microsoft Teams
Read message
Introduction We are introducing license-based management updates for Microsoft Teams Rooms on Android (MTRA) and other Android-based Teams devices that are synced to the Teams Rooms Pro Management Portal through Device Management (DM) services. This update aligns management portal capabilities with existing Teams Rooms license entitlements (Basic, Standard, and Pro). By enforcing license boundaries in the portal, this change provides clearer expectations for inventory visibility versus advanced monitoring and management features, while maintaining the current in-room meeting experience. These changes apply only to Android devices currently synced from DM services. Internet of Things (IoT)–based Android management convergence is still in progress and is not yet Generally Available. When this will happen General Availability (Worldwide, GCC, GCC High, DoD): Rollout will begin in early March 2026 and is expected to complete by late March 2026. How this affects your organization Who is affected Admins managing Microsoft Teams Rooms on Android or other Android-based Teams devices Devices synced to the Teams Rooms Pro Management Portal via DM services Tenants using Teams Rooms Basic, Standard, or Pro licenses for Android devices What will happen There is no change to the in-room Teams meeting experience. The update affects only the admin experience in the Teams Rooms Pro Management Portal. Portal features will reflect the license assigned to each Android device: Teams Rooms Pro (Android) Full advanced monitoring and management capabilities remain available. Teams Rooms Standard (Android)Device inventory metadata (such as firmware and app versions) remains visible. Advanced management and diagnostic features are restricted and may display upgrade prompts where applicable. Teams Rooms Basic (Android)Devices remain visible in Rooms and Inventory views Advanced monitoring and configuration features are not available What you can do to prepare Review license assignments for Android-based Teams Rooms devices Ensure devices requiring advanced management are licensed with Teams Rooms Pro No action is required unless you plan to upgrade licenses Compliance considerations No compliance considerations identified; review as appropriate for your organization. -
Prepare devices for successful updates with Windows Autopatch update readiness
MC1242687 · stayInformed · normal · Updated 03/02/2026 18:00
Services: Windows
Read message
Enhance your organization’s Windows update reliability with Windows Autopatch update readiness. Designed to help IT teams proactively prepare devices for upcoming Windows updates, update readiness surfaces risks and blockers before updates are deployed, reducing failures, downtime, and reactive troubleshooting. Built into Windows Autopatch, it provides actionable insights that help ensure that devices are in a healthy, update-ready state across your fleet. With update readiness insights, you gain early visibility into configuration gaps, policy conflicts, and device conditions that commonly prevent updates from successful installation. This shifts update management from a reactive model to a proactive, insight-driven approach helping keep devices secure, compliant, and productive. When will this happen: Windows Autopatch update readiness is available to those using Windows Autopatch and is included as part of your existing Windows Autopatch experience. Capabilities light up within the Windows Autopatch blade in the Microsoft Intune admin portal starting March 2, 2026. How this will affect your organization: Windows Autopatch update readiness helps IT teams identify and address update blockers ahead of time, improving update success rates and fleet resilience. Key benefits include: Early detection of issues that could block quality or feature updates Improved visibility into device readiness and update health Reduced manual troubleshooting and post-deployment firefighting Stronger security posture through timely and reliable updates What you need to do to prepare: If you already use Windows Autopatch, no additional action is required to access this feature. Review update readiness insights and address any identified readiness risks prior to deploying updates. To access these reports and tools: Go to the Microsoft Intune admin center. Select Devices > Windows updates. Depending on the insights you need: Select Feature updates or Quality updates, then a specific update to access update readiness checker. Select Feature updates or Quality updates > Alerts and remediations. Select Feature updates > Devices managed for feature updates, then a required target release to see device update journey. Select Overview > Autopatch Management Report. Read additional information for more details. Additional information: Windows Autopatch prerequisites Windows Autopatch update readiness overview Windows Autopatch update readiness brings insights to IT -
New Secure Boot update resources for Azure Virtual Desktop, Windows 365, and Microsoft Intune
MC1239883 · stayInformed · normal · Updated 02/26/2026 22:01
Services: Windows
Read message
New documentation is now available to help IT administrators prepare for Secure Boot certificate updates and manage update readiness across virtual and cloud‑managed Windows environments. The documentation covers Secure Boot certificate updates for Azure Virtual Desktop and Windows 365 Cloud PCs, as well as monitoring Secure Boot certificate status using Microsoft Intune remediations to provide visibility into readiness across managed devices. Together, these resources help ensure virtual and cloud‑managed Windows environments remain secure and continue to receive updates after June 2026. When will this happen: This documentation is available now. Secure Boot certificates begin expiring in June 2026. How this will affect your organization: Organizations managing virtual or cloud‑managed Windows environments may need to review Secure Boot certificate update planning and readiness. The documentation provides guidance for updating Secure Boot certificates in Azure Virtual Desktop and Windows 365 environments and describes how Microsoft Intune can be used to monitor Secure Boot certificate status across managed devices. In addition, the Secure Boot status report in Windows Autopatch is available again after being temporarily disabled, restoring visibility into Secure Boot readiness for devices enrolled in Windows Autopatch. What you need to do to prepare: Review the new documentation to help plan Secure Boot certificate updates and assess readiness across your virtual and cloud‑managed Windows environments. Where applicable, use Microsoft Intune and Windows Autopatch reporting to monitor Secure Boot certificate status and support update planning. Additional information: Secure Boot Certificate Updates for Azure Virtual Desktop Secure Boot Certificate Updates for Windows 365 Monitoring Secure Boot certificate status with Microsoft Intune remediations Secure Boot status report in Windows Autopatch Secure Boot playbook for certificates expiring in 2026 Secure Boot Certificate updates: Guidance for IT professionals and organizations -
Windows first sign-in restore experience now available
MC1238409 · stayInformed · normal · Updated 02/25/2026 00:01
Services: Windows
Read message
Windows first sign-in restore experience is now generally available as part of Windows Backup for Organizations. Users signing in for the first time on an eligible device will see a restore experience at first sign-in, even if it was missed the first time the device was turned on (Windows out of box experience). This allows users to restore Windows settings, restore their Microsoft Store app list, or choose to configure the device as new. This update extends restore capabilities beyond Microsoft Entra-joined devices to support hybrid-managed environments, improving readiness for new or reimaged Windows 11 devices. For more information, see Windows first sign-in restore experience now available When this will happen: General availability begins with devices that have installed Windows updates released February 24, 2026, and later. How this affects your organization: This feature is available to IT admins managing Windows 11 devices using Windows Backup for Organizations, as well as eligible devices where sign-in occurs with a Microsoft Entra ID, including Microsoft Entra hybrid-joined devices and Windows 365 Cloud PCs. The experience is controlled by admins and governed by existing Windows Backup for Organizations policies. Note that it is not enabled unless allowed by admin policy, and no changes are made to existing user data beyond what is already supported by Windows Backup for Organizations. No action is required if you do not want to offer restore at first sign-in, as existing policies remain in effect. What you can do to prepare: If you already use Windows Backup for Organizations, you can enable the first sign-in restore experience using your existing management tools, such as the Microsoft Intune settings. Group Policy options also exist. Make sure to validate device eligibility and deployment scenarios against system requirements. Additional information: Windows first sign-in restore experience now available Windows Backup for Organizations What is Microsoft Entra? -
The February 2026 Windows non-security preview update is now available
MC1238323 · stayInformed · normal · Updated 02/24/2026 18:05
Services: Windows
Read message
The February 2026 non-security preview update is now available for Windows 11, versions 26H1, 25H2, and 24H2. Information about the contents of this update is available from the release notes, which are accessible from the Windows 11 update history page. To learn more about the different types of monthly quality updates, see Windows monthly updates explained. Looking to explore upcoming features and improvements in Windows 11? Check out the Windows roadmap. It includes what’s coming to the Windows Insider Program, what’s gradually rolling out, and what’s generally available. Highlights for the Windows 11, version 25H2 update: The Emoji 16.0 release introduces a small, thoughtfully curated set of new emojis, one from each major category. Each emoji carries timeless symbolism and practical versatility. These new emojis now appear in the emoji panel. A built‑in network speed test is now available from the taskbar. You can open it from the Wi‑Fi or Cellular Quick Settings, or by right-clicking the network icon in the system tray. The speed test opens in the default browser and measures Ethernet, Wi‑Fi, and cellular connections. You can now control pan and tilt for supported cameras in the Settings app. The controls appear under Settings > Bluetooth & devices > Cameras, in the “Basic settings” section for your selected camera. Windows now brings System Monitor (Sysmon) functionality natively to Windows. Sysmon helps you capture system events for threat detection, and you can use custom configuration files to filter the events you want to monitor. Windows writes captured events to Windows Event Log, which allows security tools and other applications to use them. For instructions on how to install this update, see the KB for your operating system listed below: Windows 11, version 26H1: KB5077239 Windows 11, versions 25H2 and 24H2: KB5077241 -
Windows Server Secure Boot playbook for certificates expiring in 2026
MC1237599 · stayInformed · normal · Updated 02/24/2026 01:12
Services: Windows
Read message
Learn about tools and options available to organizations to update Secure Boot certificates on Windows Server. Certificates begin expiring in June 2026. You must update them before that date to help keep your security posture. Many recent platforms already include the supported 2023 certificates in firmware. However, for the ones that need to be updated, you need to manage this process manually. When will this happen: The tools are already available to help you to proactively inventory, monitor, and apply updated certificates to your Windows Server devices. June 2026: The 2011 Secure Boot certificate authorities (CAs) begin expiring. How this will affect your organization: Systems on the 2011 CAs after June 2026 are at risk of running on degraded security posture. To update these systems, please be proactive and follow our recommended approach. What you need to do to prepare: Read complete guidance in Additional information for details on how to: Inventory and prepare your environment. Monitor and check your devices for Secure Boot status. Apply any needed OEM firmware updates before updating certificates. Plan and pilot Secure Boot certificate deployments. Troubleshoot issues. Additional information: Get started today with the recommended approach in Windows Server Secure Boot playbook for certificates expiring in 2026. Prepare your servers for Secure Boot certificate updates. Join the online event Secure Boot certificate updates explained - Microsoft Technical Takeoff on March 9, 2026. To manage Secure Boot certificate updates on Windows client, see Secure Boot playbook for certificates expiring in 2026. For the latest information, bookmark https://aka.ms/GetSecureBoot as your landing page for resources to help you with Windows Secure Boot certificate updates. -
Plan for Windows Server 2016 and Windows 10 2016 LTSB end of support
MC1235720 · stayInformed · normal · Updated 02/20/2026 22:50
Services: Windows
Read message
Three Windows products first released in 2016 are close to reaching end of support. If your organization has devices running Windows 10 Enterprise LTSB 2016, Windows 10 IoT Enterprise 2016 LTSB, and Windows Server 2016, plan to migrate devices to a newer, supported version. If you cannot move to a newer, supported version in time, the Extended Security Updates (ESU) program offers a temporary solution to help keep devices protected in the meantime. When will this happen: Here are the upcoming end-of-support dates to note: Windows 10 Enterprise LTSB 2016: October 13, 2026 Windows 10 IoT Enterprise 2016 LTSB: October 13, 2026 Windows Server 2016: January 12, 2027 On these dates, devices running these versions will receive a final monthly security update. After that, devices will no longer receive Windows security updates, non-security updates, bug fixes, technical support, or online technical content updates. What you need to do to prepare: Plan to upgrade devices to a newer version of Windows or Windows Server before the end of support dates listed above. For devices that cannot be upgraded in time, you will be able to purchase Extended Security Updates (ESUs) for up to three years. The ESU program, however, should be a temporary solution. More details on pricing and availability for the ESU program will be available in the next few months. Additional information: To learn more about your options, see Plan for Windows Server 2016 and Windows 10 2016 LTSB end of support. -
(Updated) Toggle to new Outlook
MC949965 · planForChange · normal · Updated 02/20/2026 20:05
Services: Microsoft 365 apps
Action required by: 03/01/2027 07:00
Read message
Updated February 20, 2026: We have updated the timeline. Thank you for your patience. [Introduction] Microsoft is updating the opt‑out phase start date for new Outlook for Windows in Enterprise environments from April 2026 to March 2027. [When this will happen:] The opt‑out phase for Enterprise environments will now begin in March 2027 (previously April 2026), providing organizations with 12 months of lead time to prepare. GCC High and DoD timelines will be communicated separately at a later date. Why is there a change to the timeline? We’re seeing strong and accelerating adoption of new Outlook as organizations progress on timelines that match their readiness. At the same time, we continue to invest heavily in expanding capabilities and addressing feedback from customers who want to go further with new Outlook. To ensure organizations have the time they need to prepare—and to fully realize the value of ongoing innovation—we’re extending the opt-out timeline and providing 12 months of lead time as we continue delivering key features and improvements. [How this affects your organization:] Who is affected: Microsoft 365 administrators managing Outlook for Windows. Users of classic Outlook for Windows. Organizations that previously disabled the new Outlook toggle or have not yet begun migration planning. What will happen: Migrated users will receive in‑app onboarding prompts and can switch back to classic Outlook if needed. Existing policies that disable or limit access to new Outlook will remain in effect. Admins can continue using Admin‑controlled migration to move users in a staged, reversible manner ahead of time. Users will not be migrated if one or more of the following is true:You have opted out users using the Policy of automatic migration New Outlook toggle is hidden via policy Perpetual license is in use On premise account [What you can do to prepare:] Prepare your organization for the opt-out phase that will begin March 2027. Evaluate and use the Admin-controlled migration policy to the stage and schedule that is right for your organization. Take preparatory steps to: Assess feature and web add-in readiness. Conduct any needed pilots. Build a timeline that works for your organization. Re-enable the toggle if previously disabled and enable the Admin-controlled migration policy to move forward. Be sure to communicate with your users about what to expect, and leverage Microsoft’s adoption resources to make the experience smooth. Resources and Support: Microsoft is committed to helping you manage this transition effectively. Refer to the following resources for detailed guidance and tools: Adoption Kit: A downloadable kit with checklists, project planning templates, user communication examples, and FAQs to support your rollout. New Microsoft Outlook for Windows – Microsoft Adoption. Tips for new users: Start new users in new Outlook | Microsoft Learn. Control installation and use: If you have previously disabled the new Outlook toggle via policy and now want to roll out new Outlook. Control installation and use of new Outlook | Microsoft Learn. Policy for Admin-controlled migration: This policy allows you to toggle users into new Outlook in a controlled manner, with in-app prompts that ease users into the new experience over successive Outlook launches. Users who are moved by policy will be presented with a user-friendly onboarding experience and will have the option to switch back to classic Outlook. Microsoft recommends starting with new users in your organizations and those piloting and using Copilot as early target audiences. Policy for Admin-Controlled Migration to new Outlook for Windows | Microsoft Learn; User-facing article. [Compliance considerations] Question Explanation Does the change include an admin control? Admins can manage the change using the policy for automatic migration and existing Outlook policies. Can the change be controlled through Entra ID group membership? Migration can be scoped to specific users or groups using Entra ID group targeting. Does the change allow a user to enable and disable the feature themselves? Users moved to new Outlook can switch back to classic Outlook during the transition period. -
Personalize your Message center feed
MC1235087 · stayInformed · normal · Updated 02/19/2026 21:59
Services: Windows
Read message
The Microsoft 365 admin center Message center includes personalization features that help you focus on Windows-related updates and reduce information overload. By configuring service preferences, filters, and columns, you can prioritize Windows feature updates, security updates, hardening changes, and lifecycle announcements that are most relevant to your environments. Additional tools such as Planner syncing, search, and email notifications can help track actionable messages and support effective change management across Windows devices and environments. When will this happen: This capability is already available in the Microsoft 365 admin center. How will this affect your organization: By tailoring the Message center to focus on Windows content, you can more easily identify feature updates, security and out‑of‑band updates, hardening changes, and lifecycle announcements that require awareness or action. What you need to do to prepare: Review the filtering and customization options available in the Message center to tailor your feed to your management needs. Using service filters, tags, and relevance indicators can help narrow the view to Windows‑specific messages when needed, while column sorting and customization can identify updates that require planning or action, such as major updates or messages with an "Act by" date. See Personalize your Message center feed to learn about how small adjustments can make the Message center more focused and actionable. Additional information: Personalize your Message center feed Microsoft 365 admin center email preferences Track message center tasks in Planner Message center in the Microsoft 365 admin center Windows Tech Community -
(Updated) Retirement of several Microsoft Planner features in early 2026 as part of a Planner update
MC1193421 · planForChange · normal · Updated 02/19/2026 20:35
Services: Planner
Read message
Updated February 19, 2026: Performance may be slower on some browsers for large basic plans with more than 300 tasks. For best results, please use the latest versions of Edge (144 or higher) or Chrome (144 or higher). Meanwhile, we're also working on an update that we expect to improve performance. [Introduction] In early 2026, a major update of Planner will begin rolling out. This update will introduce several new capabilities. In addition, several features will be retired from Microsoft Planner. These changes will begin rolling out between mid-January 2026 and mid-February 2026. [When this will happen:] Refer to the sections below for details on timing. [How this affects your organization:] Who is affected: All users of Microsoft Planner in your organization, including those using Planner components in Loop, integrations with Viva Goals, and premium Planner plans. What will happen: In early 2026, we will begin rolling out a new major update of the Planner app in Teams desktop and web as well as Planner on the web. This update will come with several new enhancements, and we will also be retiring several features at this time. See each section below for more detail on the timing. New features in the upcoming Planner update: These changes will be available with the new update, which we expect to begin rolling in mid-February 2026. Tasks chats in basic plans will allow team members to collaborate directly on tasks using rich text formatting and @mentions, making it easier to discuss work and notify teammates about what needs attention. Goals in basic plans for users with a Microsoft 365 Copilot license or a Planner premium license. Goals will allow teams to set clear, well-defined objectives to help prioritize work. By connecting tasks to shared goals, teams achieve greater alignment, gain clarity on priorities, and track progress and outcomes—driving the plan forward together. New features coming in subsequent Planner updates: Project manager agent will be available in all plans for M365 Copilot licensed users, including basic plans. The Project Manager agent can help teams get work done faster by executing on tasks and can help drive alignment by writing comprehensive status reports based on plan updates. Custom templates will allow you to create reusable, pre-designed plan layouts tailored to your organization’s needs, ensuring consistency and saving time. They provide the ability to standardize content while allowing easy customization for specific scenarios. Features in Planner that will be retired: We expect this rollout to begin between mid-January 2026 and mid-February 2026. The following changes will take effect as this build rolls out to your organization: A new Task chat experience will replace the prior comments experience for basic plan tasks: As noted above, the previous task comments experience will be replaced by a new task chat feature that supports messages about the task that can include @mentions and rich text formatting, in response to a longstanding top customer request. Due to customer feedback on our notifications experience, the new chat feature only sends an email/Teams notification to a colleague that’s been @mentioned in the message. The task chat experience will be available on Planner in Teams web/desktop and the Planner web experience, and the old experience for viewing comments will no longer be directly visible on a task. Instead, the task details pane will show a link to open a page in Outlook where task comments can be seen. Users can continue to use and see the previous task comments experience in the iOS Planner app, Android Planner app, and Planner in Teams mobile. New task chat messages will not be visible in the mobile experience at this time. There are no changes to email notifications for the existing task comments experience, meaning that an email notification will be sent to all group members associated with the plan when a task comment is added. There is no change to the premium plan conversations feature at this time. The whiteboard tab for premium plans will be retired. This feature automatically created a whiteboard for premium plans in Planner and allowed users to create tasks in Planner from that whiteboard's sticky notes. The whiteboard tab will be unavailable on the premium plan after retirement of this feature. Users will be unable to create tasks from a whiteboard as a result. Any existing whiteboard content will remain available via the Whiteboard app. There is no replacement for this feature at this time. Features in Planner that will be temporarily unavailable: We expect this rollout to begin between mid-January 2026 and mid-February 2026. Convert a basic plan to a premium plan will be temporarily unavailable. The ability to convert an existing basic plan to a premium plan will be unavailable. We plan to make similar functionality available again in the future. In the meantime, users will need to create a new premium plan and manually copy the tasks into the new plan. Features that will be retired as we pursue a long‑term plan to bring equivalent capabilities: Planner component in Loop pages.This control, which could previously be inserted by typing /planner in a Loop workspace or pasting the link to a Plan, was one of the available options. This control will be retired between mid-January 2026 and mid-February 2026. Loop pages support various options for capturing task information. We recommend the Task List Control in Loop to capture tasks. After the retirement of this control, which is expected to begin in January 2026 and will roll out independent of the Planner update rollout, it will no longer be possible to add a new component of this type in a Loop workspace. Workspaces where these components were already present will display the Planner plan URL where the component was previously located. Tasks previously entered in these components will remain available in Planner. While the Planner component in Loop is being retired currently, we recognize the user need around a component like this for their planning needs. We have a longer-term goal to bring a similar Planner component across our M365 suite, including Loop. Considering these discussions are still in an early stage, we do not have an ETA to share currently. Features outside of Planner that will be retired without replacement: Planner integration in Viva Goals.Viva Goals will be retired on December 31, 2025, as previously announced. Refer to Viva Goals retirement for more information. When Viva Goals is retired, the entry point in Viva Goals for use with Planner will no longer be available. iCalendar feed integration retirement.This feature will be retired between mid-January 2026 and mid-February 2026. This feature allowed users to subscribe to their Planner tasks as an iCalendar feed that could be viewed in iCalendar-compatible applications like Outlook. After this feature is retired, users will not be able to create new iCalendar feeds for their tasks or plans, and they will stop seeing their tasks in the iCalendar feeds they previous created. There is no replacement for this feature at this time. [What you can do to prepare:] These changes will happen automatically by the specified dates. No admin action is required. Notify users about this change.Update relevant documentation as appropriate. Share the recommended alternate options where appropriate, as described above. [Compliance considerations:] No compliance considerations identified, review as appropriate for your organization. -
Coming soon to organizations: Customize the Start menu with updated policies
MC1234094 · stayInformed · normal · Updated 02/17/2026 19:20
Services: Windows
Read message
The updated Start menu is gradually rolling out. It brings the “All \[apps\]” section to the top level of the Start menu with new views (category and grid). The size of the Start menu is dynamic to the user's device. Additionally, updated policies now make it easier for you to configure Start. When will this happen: Start menu began gradual rollout in October 2025 to general audiences. The rollout of Start menu to organizations will begin in the second quarter of the calendar year 2026. How this will affect your organization: Devices will begin updating to show the new Start menu. In addition to the existing policies, the following policies give you more control: HideCategoryView: This is a net new policy that can be applied to the updated Start menu design. Turn off the new category view in the "All \[apps\]" section, so devices show the grid view by default. Note: If you already have HideAppList enabled, you don't need to enable HideCategoryView since devices won't have the "All \[apps\]" section. ConfigureStartPins: This policy can be applied to all versions of Start and only includes an update. When the optional applyOnce flag is set, the pinned layout is applied only during initial provisioning. After that, users can customize their Start menu without those changes being reset during routine policy refreshes. This addresses a previous issue where users’ pinned sections could be unexpectedly refreshed. What you need to do to prepare: Review the new policies above and make changes accordingly. See additional information. Additional information: Review policies in Start Policy CSP. Learn more at Start policy settings. Learn more about HideCategoryView Start Policy CSP. Learn more about ConfigureStartPins Start Policy CSP. -
Windows Office Hours: February 19, 2026
MC1231206 · stayInformed · normal · Updated 02/12/2026 18:04
Services: Windows
Read message
If you are an IT admin with questions about managing and updating Windows, we want to help. Every third Thursday of the month, we host a live chat-based event on the Tech Community called Windows Office Hours. Members of the Windows, Microsoft Intune, Windows Autopilot, Windows Autopatch, and Windows 365 engineering teams will be standing by to answer your questions. We also have experts from FastTrack, the Customer Acceleration Team, and Microsoft public sector teams. Want to attend the February 19 session of Office Hours? Add it to your calendar and select Attend on the event page to let us know you’re coming. There is no video or live meeting component. Simply visit the event page, log in to the Tech Community, and leave your questions in the Comments section. You can also bookmark https://aka.ms/Windows/OfficeHours for upcoming dates (and the ability to add this event to your calendar). We look forward to helping you. -
Windows 11, version 26H1 coming to select new devices in early 2026
MC1230371 · stayInformed · normal · Updated 02/10/2026 18:13
Services: Windows
Read message
Windows 11, version 26H1 is a hardware‑optimized release designed to enable next‑generation silicon developed in partnership with device manufacturers and silicon partners. This release will be available exclusively as a preinstalled experience on select new devices beginning in early 2026. It is not intended as a feature update for existing Windows 11 devices and will not be offered through Windows Update. When will this happen: The first devices with Windows 11, version 26H1 preinstalled will start shipping in early 2026. This release is limited to select new devices only and is not offered as an in‑place update for devices running Windows 11, versions 25H2 or 24H2. How this will affect your organization: Windows 11, version 26H1 is scoped specifically for select new hardware platforms, so it will not be offered through Windows Update for existing devices and will not impact ongoing rollout processes. Organizations evaluating specialized new hardware platforms may adopt version 26H1 selectively without affecting the rest of their environment. Devices running Windows 11, versions 25H2 and 24H2 will continue receiving monthly security and quality updates, as well as new features, and remain supported according to servicing timelines and Microsoft lifecycle policies. What you need to do to prepare: No preparation or changes are required for existing deployments. While Windows 11, version 26H1 is not intended for broad deployment across existing Windows 11 environments, organizations evaluating new hardware platforms may adopt it selectively without affecting their broader environment. Devices running Windows 11, versions 25H2 and 24H2 remain the recommended choice for enterprise deployment and continue to be supported according to established servicing timelines and Microsoft lifecycle policies. Additional information What to know about Windows 11, version 26H1 Windows 11 release information Windows Lifecycle FAQ Microsoft Lifecycle Policy search tool -
Secure Boot certificate updates: actions required ahead of June 2026 expiration
MC1230373 · stayInformed · normal · Updated 02/10/2026 18:04
Services: Windows
Read message
Secure Boot is a foundational Windows security feature that runs at startup, before Windows load, and helps ensure that only trusted, digitally signed software can execute. After more than 15 years of continuous service, the original Secure Boot certificates are reaching the end of their planned lifecycle and begin expiring in late June 2026. To learn more about Microsoft’s effort to update these certificates, see the blog post Refreshing the root of trust: industry collaboration on Secure Boot certificate updates. To prevent disruption and maintain secure startup across Windows environments, plan for these certificates update following the guidance in the Secure Boot playbook. When this will happen: The 2011 Secure Boot certificates begin expiring in June 2026. What you need to do to prepare: Review the Secure Boot playbook for certificates expiring in 2026 to understand requirements, timelines, and supported scenarios. Additionally, bookmark https://aka.ms/GetSecureBoot for more information about this change, OEMs guidance, and answers to frequently asked questions. Additional technical resources: If you use Microsoft Intune, read Microsoft Intune method of Secure Boot for Windows devices with IT-managed updates. Compare this method to Registry key updates for Secure Boot: Windows devices with IT-managed updates. Check out the option Group Policy Objects (GPO) method of Secure Boot for Windows devices with IT-managed updates. See how these methods work together in Secure Boot playbook for certificates expiring in 2026. -
The February 2026 Windows security update is now available
MC1230372 · stayInformed · normal · Updated 02/10/2026 18:04
Services: Windows
Read message
The February 2026 security update is now available for all supported versions of Windows. We recommend that you install these updates promptly. For more information about the contents of this update, see the release notes, which are easily accessible from the Windows 11 update history page. To learn more about the different types of monthly quality updates, see Windows monthly updates explained. Highlights for the Windows 11, version 25H2 update: This security update includes improvements that were a part of update KB5074109 (released January 13, 2026), KB5077744 (released January 17, 2026), and KB5078127 (released January 24, 2026). This update makes quality improvements to the servicing stack, which is the component that installs Windows updates. This update addresses an issue that determines device eligibility for the full-screen gaming experience. This update addresses an issue that prevented some devices from connecting to certain WPA3‑Personal Wi‑Fi networks. Short on time? Watch our Windows 11 release notes video for this month's tips. For instructions on how to install this update, see the KB for your operating system listed below: Windows 11, version 26H1: KB5077179 Windows 11, versions 25H2 and 24H2: KB5077181 Windows 11, version 23H2: KB5075941 Windows 11 Enterprise LTSC 2024: Hotpatch KB5077212 Windows 10, versions 22H2 and 21H2: KB5075912 Windows 10 Enterprise LTSC 2019 and Windows Server 2019: KB5075904 Windows 10 LTSB 2016 and Windows Server 2016: KB5075999 Windows Server 2025: KB5075899 Windows Server 2025 Datacenter: Azure Edition: Hotpatch KB5075942 Windows Server 2022: KB5075906 Windows Server 2022 Datacenter: Azure Edition: Hotpatch KB5075943 Windows Server 2012 R2: KB5075970 Windows Server 2012: KB5075971 Note: Starting with the January 2026 security update, Windows Server 2025 has its own KB identifiers and build numbers, separate from Windows 11, versions 24H2 and 25H2. This change improves clarity for administrators. Installation and management processes remain the same. -
(Updated) Resolved: Power outage affecting Microsoft Store app installs and Windows update delivery
MC1229029 · stayInformed · normal · Updated 02/08/2026 02:21
Services: Windows
Read message
11:30 am PT update: Microsoft Store and Windows Update services have been restored. Some IT administrators may continue to experience residual latency affecting Windows Server update operations, including the Windows Server sync API. This Server‑specific issue is being addressed separately. If you experience this latency, please contact Microsoft Support for business. 8:34 am PT post: A power outage at a datacenter is impacting customers’ ability to complete operations in the Microsoft Store and Windows Update. As a result, some users may experience failures or timeouts when installing or updating Microsoft Store apps, or when downloading Windows updates. Although power has been restored, service recovery is still in progress. Storage services are gradually returning online, and some customer impact may continue while recovery completes. Microsoft is actively working to restore full-service reliability. Customers who are affected are advised to retry Microsoft Store and Windows Update operations later. We will provide more information as it becomes available. -
Advancing Windows security: Disabling NTLM by default
MC1227478 · stayInformed · normal · Updated 02/05/2026 18:00
Services: Windows
Read message
Windows is moving toward a more secure authentication model by phasing out New Technology LAN Manager (NTLM) in favor of stronger, Kerberos‑based alternatives. This transition is taking a three-phased approach, leading toward disabling NTLM by default in upcoming Windows releases. With each phase come new capabilities so that your organization has the tools, visibility, and compatibility support needed. When will this happen: NTLM has been deprecated since June 2024. Today, enhanced auditing is available as part of Phase 1 toward NTLM disablement. In the second half of 2026, new tools will be available to Windows Server 2025 and Windows 11, version 24H2 and later: IAKerb, Local KDC, upgrade to negotiate Kerberos. With the next version of Windows Server and its corresponding client version, NTLM will be disabled by default. Additional support for handling NTLM-only cases will be built in. How this will affect your organization: Disabling NTLM represents a major evolution in Windows authentication, and a critical step toward a passwordless, phishing resistant future. A phased strategy enables you to mitigate NTLM-related risks in a secure and predictable manner, without disrupting your organization. What you need to do to prepare: If your organization is beginning or accelerating its NTLM reduction efforts, now is the right time to engage your identity, security, and application owners to take concrete steps: Deploy enhanced NTLM auditing to identify where NTLM is still used. Map dependencies across applications and services and prioritize remediation. This may include reaching out to application developers to update critical applications. Migrate and validate that critical workloads succeed with Kerberos. The capabilities that will be released in the second half of 2026 will significantly expand the scenarios where you can use Kerberos successfully. Begin testing NTLM-off configurations in non-production environments. Enable Kerberos upgrades as they become available through the Windows Insider Program, and then more broadly later this calendar year. Additional information: Advancing Windows security: Disabling NTLM by default Overview of NTLM auditing enhancements in Windows 11, version 24H2 and Windows Server 2025 Active Directory Hardening Series - Part 8 – Disabling NTLM NTLM overview in Windows Server -
Exchange Web Services (EWS) retirement update
MC1227454 · planForChange · normal · Updated 02/05/2026 16:58
Services: Exchange Online
Read message
[Introduction] We're updating the timeline and process for the retirement of Exchange Web Services (EWS) in Exchange Online. As previously announced, EWS will be retired in favor of Microsoft Graph, which offers improved security, modern authentication, and broader capability support. A phased disablement begins October 1, 2026, with permanent shutdown starting April 1, 2027. [When this will happen:] Phased EWS disablement begins: October 1, 2026 Full and permanent EWS retirement: April 1, 2027 EWS App AllowList feature availability: Coming soon (before retirement milestones) [How this affects your organization:] Who is affected: Organizations using custom or vendor applications that rely on EWS Workflows involving mail, calendar, or integrations that use EWS This change only impacts Exchange Online; Exchange Server (on-premises) is not affected What will happen: Beginning October 1, 2026, EWS will be blocked unless the tenant configures an AppID AllowList and sets EWSEnabled=True. Without admin action, Microsoft will set EWSEnabled=False and EWS apps will stop working. Tenant admins will be able to re-enable EWS if necessary. Temporary “scream tests” may occur before October 2026 to help identify dependencies. After April 1, 2027, EWS access will be permanently removed with no re-enablement. No changes are being made to EWS in Exchange Server (on-premises). [What you can do to prepare:] Review EWS usage in the Microsoft 365 admin center or using published scripts to identify dependent applications. Begin migrating any remaining EWS-based workflows to Microsoft Graph, which provides near-complete API parity. If EWS is required after October 2026, configure an AppID AllowList and set EWSEnabled=True before end of August 2026. Communicate these changes internally and update documentation. Learn more: Deprecation of Exchange Web Services in Exchange Online EWS Retirement Process overview [Compliance considerations:] No compliance considerations identified, review as appropriate for your organization. -
Windows news you can use: January 2026 recap
MC1226925 · stayInformed · normal · Updated 02/04/2026 18:04
Services: Windows
Read message
Catch up on important changes and evolving standards that will help strengthen the security of the Windows ecosystem across client, cloud, and server with Windows news you can use for January 2026. Learn about new tools to help with Secure Boot certificate updates and a new command-line tool for Windows app developers. Explore features and enhancements that will start gradually rolling out in February, which include improvements to Cross-Device Resume, Narrator, Voice Access, MIDI support, and the Settings home page. When will this happen: Some improvements summarized in this monthly recap are already available, while others are rolling out gradually. What you need to do to prepare: Read January’s recap, which includes links to resources to help you start benefiting from the latest improvements. Additional information: To keep up with new capabilities and features as they are announced, follow the Windows IT Pro Blog, Microsoft Security Blog, and Windows 11 update history. -
Skill up on Windows at Technical Takeoff
MC1226571 · stayInformed · normal · Updated 02/03/2026 23:00
Services: Windows
Read message
If you’re looking for prescriptive guidance help you confidently configure, manage, and support Windows across your organization, mark your calendars for Microsoft Technical Takeoff 2026. Taking place on the first four Mondays in March, this free event offers technical deep dives, AMAs, and feedback sessions—all supported by live Q&A with the teams behind the features. Sessions will cover the latest Windows 11 security features, Windows 365 business‑continuity improvements, Secure Boot certificate updates, Windows Autopatch reporting, and onboarding experiences that help users get productive faster. You’ll also see deep dives on NTLM removal, hotpatch updates, resiliency, and other real‑world scenarios designed to help you deploy, secure, troubleshoot, and optimize Windows at scale. When will this happen: Sessions will take place from 7:00 AM to 12:00 PM Pacific Time on March 2, 9, 16, and 23. All sessions will be recorded and available on demand on the Microsoft Tech Community. Note: Because of Daylight Saving Time in the U.S., sessions on March 2 will start at 3:00 PM UTC while sessions on March 9, 16, and 23 will start at 2:00 PM UTC. What you need to do to prepare: Registration is not required. On each session page, you’ll find the ability to “Add to Calendar” or click “Attend” to save your spot and receive reminders. If you have questions in advance, sign in to the Tech Community and post them in the comments. Additional information: See what’s in store for Windows or browse the full agenda to see all the sessions across Windows, Windows in the cloud, and Microsoft Intune. -
Microsoft Teams: Teams Live Events is retiring
MC1226495 · planForChange · normal · Updated 02/03/2026 18:07
Services: Microsoft Teams
Action required by: 06/29/2026 07:00
Read message
[Introduction] Microsoft is retiring Teams Live Events and the Microsoft Graph APIs used to create them on June 30, 2026. Existing events scheduled before that date will continue to function through February 28, 2027. We encourage customers to migrate to Teams town halls, which offer an enhanced, end-to-end experience for large-scale events. This retirement supports Microsoft’s investment in Teams town halls, which provide an improved experience for digital and hybrid events and include comparable Graph APIs for programmatic creation, management, and integration. [When this will happen] Teams Live Events and associated Microsoft Graph APIs will retire on June 30, 2026. Existing Teams Live Events will continue to function through February 28, 2027. Customers will no longer be able to schedule Teams Live Events past June 30, 2026, beginning February 3, 2026. Customers scheduling through Dynamics 365 will not be able to schedule events past June 30, 2026, beginning February 3, 2026. The isBroadcast property within the onlineMeetingGraph resource will remain available until June 30, 2026. [How this affects your organization] You are receiving this message because our reporting indicates your organization may be using or has access to Teams Live Events. Who is affected: Organizations using Teams Live Events. Organizations using Microsoft Graph APIs to create Teams Live Events. Organizations scheduling Teams Live Events through Viva Engage or Microsoft Dynamics 365. What will happen: Teams Live Events and the associated Microsoft Graph APIs will no longer be available after retirement. Teams town hall is now the recommended option for large scale events. New scheduling of Teams Live Events will become limited as the retirement date approaches. Existing scheduled events will remain supported through the end of the service window. Workflows or applications that depend on the isBroadcast property will need to transition. Teams town halls and Teams meeting Graph APIs will serve as replacements for large-scale broadcast scenarios. Customers should migrate to Teams town halls or Teams meeting Graph APIs. [What you can do to prepare] No admin configuration changes are required. We recommend the following: Assess dependencies Identify where your organization uses Teams Live Events, including events scheduled through Viva Engage, Dynamics 365, or custom Graph-based solutions. Plan your transition Move large-scale broadcast and virtual event scenarios to Teams town halls or Teams meetings. Update or replace workflows that rely on the retiring Graph API functionality. Prepare users Inform event organizers and producers about the retirement and their transition path. Update internal training, documentation, and support materials. Use these resources Plan for Teams town halls | Microsoft Teams | Microsoft Learn Get started with town hall in Microsoft Teams | Meetings | Microsoft Teams | Microsoft Support Retiring Teams live events: The next chapter for events at scale in Microsoft Teams | Microsoft Teams Blog Virtual events town hall API use cases | Microsoft Graph | Microsoft Learn Customer Hub events readiness sessions - recommended for Teams Live Events users transitioning to Teams town halls: What’s new in Microsoft Teams town halls and webinars Migrating from Teams Live Events to town halls Tips, tricks, and traps for town halls and webinars in Microsoft Teams [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. -
Secure Boot status report in Windows Autopatch
MC1226170 · stayInformed · normal · Updated 02/02/2026 23:00
Services: Windows
Read message
If you’re an IT admin using Windows Autopatch, a new report is now available to monitor the status of Secure Boot across your organization. As the 2011 Secure Boot certificates start expiring in June 2026, this report helps you start by identifying devices that have Secure Boot enabled. Out of those, see which devices are fully up to date and which ones still need updated certificates. When will this happen: The Secure Boot status report is now available in Windows Autopatch. The 2011 Secure Boot certificates (or CAs) start expiring in June 2026. How this will affect your organization: The Secure Boot status report in Windows Autopatch is designed to help you understand the Secure Boot posture of your fleet. It can help you identify devices that may require attention—before issues occur. What you need to do to prepare: If you don’t yet use Windows Autopatch, consider how it can help you manage Windows across your organization. If none of your devices have Secure Boot enabled, no action is required. Devices that use Secure Boot to prevent boot-level malware at startup need updated certificates. The new report can help with the inventory and monitoring of the Secure Boot certificate status. See Additional information to learn more. Additional information: Secure Boot status report in Windows Autopatch Secure Boot playbook for certificates expiring in 2026 Windows Secure Boot certificate expiration and CA updates -
The January 2026 Windows non-security preview update is now available
MC1224532 · stayInformed · normal · Updated 01/29/2026 22:02
Services: Windows
Read message
The January 2026 non-security preview update is now available for Windows 11, versions 25H2 and 24H2. Information about the contents of this update is available from the release notes, which are accessible from the Windows 11 update history page. To learn more about the different types of monthly quality updates, see Windows monthly updates explained. Looking to explore upcoming features and improvements in Windows 11? Check out the Windows roadmap. It includes what’s coming to the Windows Insider Program, what’s gradually rolling out, and what’s generally available. Highlights for the Windows 11, version 25H2 update: The Settings Agent now supports more languages, with expanded support for German, Portuguese, Spanish, Korean, Japanese, Hindi, Italian, and Chinese (Simplified).* This update expands the functionality of Cross‑Device Resume. You can continue activities from your Android phone on your PC based on the apps and services you use, including resuming Spotify playback, working in Word, Excel, or PowerPoint, or continuing a browsing session. This update improves MIDI on Windows with enhanced support for MIDI 1.0 and MIDI 2.0, including full WinMM and WinRT MIDI 1.0 support with built-in translation, shared MIDI ports across apps, custom port names, loopback and app-to-app MIDI, plus performance improvements and bug fixes—delivering a better experience for musicians. Narrator now gives you more control over how it announces on‑screen controls. You can choose which details are spoken and adjust their order to match how you navigate apps. These settings apply throughout the app to help reduce extra speech and make Narrator easier to follow. Windows Hello Enhanced Sign-in Security (ESS) now supports peripheral fingerprint sensors. This update extends this more secure sign-in option beyond devices with built-in fingerprint sensors to include desktops and other Windows 11 PCs, including Copilot+ PCs. * Experiences for Copilot+ PCs only For instructions on how to install this update, see the KB for your operating system listed below: Windows 11, versions 25H2 and 24H2: KB5074105 Note: Starting with the January 2026 security update, Windows Server 2025 has its own KB identifiers and build numbers, separate from Windows 11, versions 24H2 and 25H2. This change improves clarity for administrators. Installation and management processes remain the same. -
An updated version of the January 2026 Scan Cab is available
MC1223281 · stayInformed · normal · Updated 01/28/2026 01:44
Services: Windows
Read message
IMPORTANT: This notice is only relevant for environments where: Microsoft Office is used Scan Cab is used to check for update compliance The January 2026 Scan Cab was deployed before 2:30 PM PT on January 27, 2026. An updated version of the January 2026 Scan Cab was made available at 2:30 PM PT on January 27, 2026. This Scan Cab includes new metadata corresponding to new updates for Microsoft Office 2016. The new security updates for Microsoft Office released January 26, 2026, included additional protections to address CVE-2026-21509. Reliance on untrusted inputs in a security decision in Microsoft Office allows an unauthorized attacker to bypass a security feature locally. See the additional information section of this message for details. How this affects your organization: IT administrators who downloaded the Scan Cab before 2:30 PM PT on January 27, 2026, should re-acquire and re-deploy it if the Scan Cab is used to assess updates for environments where Microsoft Office is used. No action is required on environments where Scan Cab is not employed and do not have Microsoft Office installed. However, please note that there might be non-Microsoft applications that utilize Scan Cab. Review the documentation for any software and update deployment tools that might be in use for your organization, to understand if this is applicable in your environment. What you need to do to prepare: Administrators can download the updated Scan Cab here. Visit CVE-2026-21509 to find download links, release notes, and appropriate action for affected versions of Microsoft Office. For detailed guidance, see the Additional information section below. Additional information: Updated Scan Cab: Download the new Scan Cab here CVE-2026-21509: Microsoft Office Security Feature Bypass Vulnerability Security Update for Microsoft Office 2016 (KB5002713) Announcing a smaller WSUS Scan Cab - Microsoft Tech Community: Learn more about WSUS and the Scan Cab process Using WUA to Scan for Updates Offline - Win32 apps | Microsoft Docs: Windows Update Agent (WUA) can be used to scan computers for security updates without connecting to Windows Update WSUS and the Catalog Site | Microsoft Docs: The Catalog Site used by WSUS to import updates and drivers -
(Updated) Take Action: Out-of-band update to address cloud‑backed storage application issues
MC1222123 · preventOrFixIssue · normal · Updated 01/26/2026 18:54
Services: Windows
Read message
(Updated 1/26 to adjust Windows Server entries and links) Microsoft released today a resolution for an issue observed after installing the January 2026 Windows security update. This issue may cause applications that open or save files stored in cloud‑backed locations to become unresponsive or display errors. Some installations of Outlook may also become unresponsive and fail to open when PST files are stored in cloud‑backed storage such as OneDrive. An out-of-band (OOB) update was released today, January 24, 2026, to address this issue. This cumulative update includes all protections and improvements from the January 2026 Windows security update released January 13, 2026, as well as from the OOB update released on January 17, 2026 (which introduced fixes for two known issues: remote desktop connections and hibernation failures). This OOB update is available through Windows Update for Windows 11 devices running the updates released this month. To install it, open Settings > Windows Update, and select Download and install. Note that this update will show up in Windows Update only if you have installed one of the updates released in January that caused this issue. Some devices may install the update automatically. For supported versions of Windows Server and Windows 10, the OOB update is available from the Microsoft Update Catalog. Refer to the KB articles below for detailed information and installation steps. Windows 11, versions 25H2 and 24H2: KB5078127 Windows 11 Enterprise versions 25H2 and 24H2: Hotpatch KB5078167 Windows 11, version 23H2: KB5078132 Windows 10 ESU (22H2) and Windows 10 Enterprise LTSC 2021: KB5078129 Windows Server 2025: KB5078135 Windows Server, version 23H2: KB5078133 Windows Server 2022: KB5078136 Windows Server 2022 Datacenter: Azure Edition: Hotpatch KB5078238 Windows Server 2019 and Windows 10 Enterprise LTSC 2019: KB5078131 IT administrators using Microsoft Intune or Windows Autopatch should follow the guidance below for installing the OOB update via Windows Update. Expedite Windows quality updates in Microsoft Intune Deploy an expedited quality update using Windows Autopatch -
Ask Microsoft Anything: Secure Boot - February 5
MC1219801 · stayInformed · normal · Updated 01/21/2026 00:45
Services: Windows
Read message
Mark your calendars for February 5, 2026. Windows engineering teams will be hosting a second Ask Microsoft Anything (AMA) on the Microsoft Tech Community to help you get the information you need about updating Secure Boot certificates on your Windows devices before they start expiring in June 2026. Experts will be on camera and in the chat to help you with update scenarios, inventorying your estate, formulating the right deployment plan for your organization, and more. When will this happen: This one-hour AMA event will start at 8:00 AM PST (3:00 PM UTC) on February 5, 2026. What you need to do to prepare: Visit the event page, then select Add to Calendar. Want an event reminder? Log in to the Tech Community and select Attend. Can’t attend at that time? Scroll to the bottom of the event page, then post your questions early where it says “Comment.” The event will be recorded so you can catch up on demand anytime after the live stream concludes. Additional information: Visit https://aka.ms/AMA/SecureBoot to save the date and get a head start with the steps and resources outlined in the Secure Boot playbook. -
Take Action: Out-of-band update to address issues observed with the January 2026 Windows security update
MC1218934 · preventOrFixIssue · normal · Updated 01/17/2026 22:22
Services: Windows
Read message
Microsoft has identified issues upon installing the January 2026 Windows security update. To address these issues, an out-of-band (OOB) update was released today, January 17, 2026. Connection and authentication failures in remote connection applications: This issue affects multiple platforms including Windows 11, version 25H2; Windows 10, version 22H2 ESU; and Windows Server 2025. See the bottom of this message for the complete list of affected products. Devices with Secure Launch might fail to shut down or hibernate: This issue only affects Windows 11, version 23H2. The out-of-band (OOB) update was released today, January 17, 2026, in the Microsoft Update Catalog. If you have not yet deployed the January 2026 Windows security update and your IT environment includes the affected applications and features, we recommend applying this OOB update instead. For more information and installation instructions, refer to the appropriate KB article for each affected version of Windows listed below. For additional guidance, see How to download updates from the Microsoft Update Catalog. Windows 11, versions 25H2 and 24H2 (KB5077744) Windows 11, version 23H2 (KB5077797) Windows 10, version 22H2 ESU and Windows 10 Enterprise LTSC 2021 (KB5077796) Windows Server 2025 (KB5077793) Windows Server 2022 (KB5077800) Windows Server 2019 and Enterprise LTSC 2019 (KB5077795) -
Initial deployment phase for Kerberos RC4 hardening begins with the January 2026 Windows security update
MC1218691 · stayInformed · normal · Updated 01/16/2026 20:05
Services: Windows
Read message
Windows updates released on and after January 13, 2026, introduce the first phase of protections addressing a Kerberos information disclosure vulnerability (CVE‑2026‑20833). These updates introduce new auditing and optional registry controls that devices can use to begin reducing reliance on RC4 encryption. They also help prepare domain controllers for a future shift to AES‑SHA1 as the default Kerberos encryption method for accounts without explicit encryption settings. The initial deployment phase focuses on identifying misconfigurations or dependencies before the second deployment phase begins in April 2026. When this will happen: The initial deployment phase starts January 13, 2026, and introduces new Kerberos audit events that help identify any remaining RC4 dependencies across your environment. This phase also adds the temporary RC4DefaultDisablementPhase registry value, which organizations can use to optionally enable the upcoming behavior changes early; however, this key will no longer be read after Audit mode is removed in July 2026. Together, these updates provide early diagnostics to help assess readiness before the second deployment phase in April 2026, when the default domain controller behavior for Kerberos encryption will change to use AES‑SHA1 only for accounts without explicit encryption settings. Starting in April 2026, Enforcement mode will be enabled on all Windows domain controllers by default, and in July 2026 Audit mode will be removed, leaving Enforcement mode as the only option. How this will affect your organization: Domain controllers will begin logging new Kerberos audit events, KDCSVC (ID 201–209), that highlight where devices or service accounts still rely on RC4 encryption. Certain RC4‑dependent configurations will appear in the new Kerberos audit events, highlighting scenarios that will become incompatible once enforcement begins. These events provide early visibility into configurations that may fail as Enforcement mode is enabled by default starting in April 2026 and Audit mode is removed in July 2026. As the deployment phases progress, beginning with the April 2026 Windows security update, Kerberos operations will shift to using AES‑SHA1 by default for accounts without explicit encryption settings. Environments that do not address RC4 dependencies may experience authentication issues as Enforcement mode is enabled by default starting in April 2026 and Audit mode is removed in July 2026. Organizations with secure configurations or without RC4 usage should see minimal impact aside from routine audit visibility during the transition period. What you need to do to prepare: Begin by installing Windows updates released on or after January 13, 2026, on all Active Directory domain controllers. After updating, monitor the System event logs for the new Kerberos audit events that indicate whether any devices or service accounts still rely on RC4-based encryption. If no events appear, you can proactively move your domain controllers to Enforcement mode by using the Registry settings. If events do appear, you will need to address or explicitly configure any remaining RC4 dependencies before enforcement takes effect. Additional information: Read the full hardening guidance: How to manage Kerberos KDC usage of RC4 for service account ticket issuance changes related to CVE-2026-20833. Learn about RC4 usage in Windows and its risks: Detect and remediate RC4 usage in Kerberos. Learn more about the related vulnerability: CVE-2026-20833. -
Retirement of Power BI Q&A
MC1218421 · planForChange · normal · Updated 01/16/2026 00:15
Services: Power BI
Read message
Introduction We are announcing the retirement of Q&A, Power BI’s legacy natural language tool. Starting December 2026, Q&A experiences will be retired. Moving forward, users can leverage Power BI Copilot, which offers a more advanced and integrated solution for querying data using generative AI. This change reduces feature overlap, accelerates innovation, and provides a consistent experience across Power BI. When this will happen: Q&A experiences and Q&A Setup will be fully retired by the end of December 2026. How this affects your organization: Who is affected: All organizations using Q&A experiences in Power BI reports, dashboards, mobile, or embedded analytics. What will happen: Creation of new Q&A visuals or experiences will no longer be permitted after December 2026. Existing Q&A visuals in reports, dashboards, mobile, and embedded scenarios will stop working and will be removed. Q&A Setup tools (synonyms, linguistic relationships, teach Q&A, etc.) will be retired. Users should transition to Power BI Copilot for natural language queries and insights. What you can do to prepare: Review reports and dashboards for Q&A visuals and plan to replace them with Copilot experiences. Learn more: Microsoft Power BI Updates Blog: Deprecating Power BI Q&A. Familiarize yourself with Power BI Copilot and Prep Data for AI as alternatives to Q&A and Q&A Setup. Update internal documentation and helpdesk guidance to reflect this change. Compliance considerations: No compliance considerations identified, review as appropriate for your organization. -
Windows Backup for Organizations expands to first sign-in restore
MC1217951 · stayInformed · normal · Updated 01/14/2026 20:44
Services: Windows
Read message
Preview the expanded Windows Backup for Organizations experience! In early 2026, if users miss the restore option during the out-of-box experience (OOBE) by accident or due to a technical issue, they can still restore at first sign-in. Windows Backup for Organizations helps preserve Windows settings, the list of installed Microsoft Store apps, and the Start menu pins. And now, even more devices can take advantage of this capability, including Microsoft Entra hybrid joined, multi-user setups, and Windows 365 Cloud PCs. When will this happen: The opportunity to sign up for private preview is open now and until February 13, 2026. First sign-in restore will become generally available in early 2026. How this will affect your organization: Windows Backup for Organizations helps your organization upgrade, migrate, or refresh Windows devices. First sign-in restore experience expands its benefits to: Those users who miss the OOBE restore option Microsoft Entra hybrid joined, multi-user setups, and Windows 365 Cloud PCs What you need to do to prepare: Sign up for the private preview now through February 13, 2026. You must be part of the Microsoft Management Customer Connection Program to be considered. Follow links to the official announcement and details under Additional information. Additional information: Read the blog article: Windows Backup for Organizations expands to first sign-in restore. Sign up for the private preview: https://forms.office.com/r/UbE2AeP1yP. -
Windows Deployment Services (WDS): Hands-free deployment hardening (Phase 1)
MC1217584 · stayInformed · normal · Updated 01/13/2026 23:29
Services: Windows
Read message
Prepare for a two-phase hardening change related to CVE-2026-0386. The Unattend.xml file that underlies the hands-free deployment feature of Windows Deployment Services (WDS) poses a vulnerability when it’s transmitted over an unauthenticated RPC channel. Starting with the January 2026 security update, you can explicitly disable it with the help of new Event Log alerts and registry key options. In April 2026, hands-free deployment will be disabled by default. After that date, it will no longer work unless explicitly overridden with registry settings. When will this happen: January 2026 security update: Phase 1 of hardening begins. Hands-free deployment continues to be supported and can be explicitly disabled to enhance security. Use the new Event Log alerts and registry key options. April 2026 security update: Phase 2 of hardening follows. Hands-free deployment will be disabled by default but can be re-enabled, if necessary, with an understanding of the associated security risks. How this will affect your organization: These hardening measures are meant to enhance security. If no action is taken (no registry key added) between January-April 2026, hands-free deployment will be blocked after the April 2026 security update. What you need to do to prepare: Apply the Windows update released on or after January 13, 2026 to enable the mitigation and ensure that devices are secure. When ready to disable hands-free deployment, apply the following registry setting: Registry location: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WdsServer\Providers\WdsImgSrv\Unattend DWORD name: AllowHandsFreeFunctionality Value data: 00000000 Additional information: Read the full hardening guidance: Windows Deployment Services (WDS) Hands-Free Deployment Hardening Guidance related to CVE-2026-0386. Learn more about the related vulnerability: CVE-2026-0386. See deployment alternatives: Windows Deployment Services (WDS) boot.wim support. Explore cloud-based solutions: Windows Autopilot and Windows Autopilot device preparation documentation. -
The January 2026 Windows security update is now available
MC1217507 · stayInformed · normal · Updated 01/13/2026 22:06
Services: Windows
Read message
The January 2026 security update is now available for all supported versions of Windows. We recommend that you install these updates promptly. For more information about the contents of this update, see the release notes, which are easily accessible from the Windows 11 update history page. To learn more about the different types of monthly quality updates, see Windows monthly updates explained. Highlights for the Windows 11, version 25H2 update: This security update includes improvements that were a part of update KB5072033 (released December 9, 2025). This update makes quality improvements to the servicing stack, which is the component that installs Windows updates. This update addresses an issue where you might experience RemoteApp connection failures in Azure Virtual Desktop environments. This might occur after installing KB5070311. This update addresses an issue where devices with a Neural Processing Unit (NPU) might stay powered on when idle. Short on time? Watch our Windows 11 release notes video for this month's tips. Note: Starting with the January 2026 security update, Windows Server 2025 will have its own KB identifiers and build numbers, separate from Windows 11, versions 24H2 and 25H2. This change improves clarity for administrators. Installation and management processes remain the same. For instructions on how to install this update, see the KB for your operating system listed below: Windows 11, versions 25H2 and 24H2: KB5074109 Windows 11, version 23H2: KB5073455 Windows 11 Enterprise LTSC 2024: Hotpatch Baseline Windows 10, versions 22H2 and 21H2: KB5073724 Windows 10 Enterprise LTSC 2019 and Windows Server 2019: KB5073723 Windows 10 LTSB 2016 and Windows Server 2016: KB5073722 Windows Server 2025: KB5073379 Windows Server 2025 Datacenter: Azure Edition: Hotpatch Baseline Windows Server 2022: KB5073457 Windows Server 2022 Datacenter: Azure Edition: Hotpatch Baseline Windows Server 2012 R2: Monthly Rollup: KB5073696 Windows Server 2012: Monthly Rollup: KB5073698 Windows Server 2008 R2 Service Pack 1: Monthly Rollup: KB5073695 / Security Only: KB5073699 Windows Server 2008 SP2: Monthly Rollup: KB5073697 / Security Only: KB5073700 -
Hardening changes coming to Common Log File System (CLFS) authentication
MC1216196 · stayInformed · normal · Updated 01/09/2026 19:04
Services: Windows
Read message
A new hardening authentication mitigation has been introduced for the Common Log File System (CLFS) driver. Windows updates that include this new version of CLFS will initiate a 90 day "learning mode" period during which authentication codes will be added to log files automatically. Device behavior will change after this period. For more information, see Common Log File System (CLFS) Authentication Mitigation. When will this happen: Windows 11, version 25H2 and Windows Server 2025 updates released on or after October 28, 2025 include this change. A mitigation adoption period, referred to as "learning mode" will be in place for 90 days following installation of updates. During this time, authentication codes are automatically added to existing logfiles when they are opened. After this period ends, the CLFS driver will enter enforcement mode, requiring all logfiles to contain valid authentication codes. How this will affect your organization: The authentication mitigation for the CLFS driver adds a hash-based message authentication code (HMAC) to the underlying files of a CLFS logfile. With this, CLFS logfiles include authentication codes generated by combining file data with a system-unique cryptographic key stored in the registry, accessible only to administrators and SYSTEM accounts. Once enforcement mode begins, any logfile without a valid authentication code will fail to open. Logfiles not updated during the 90-day learning mode period must be manually authenticated by an Administrator using the fsutil clfs authenticate command line utility. What you need to do to prepare: Review systems that use CLFS logfiles and ensure they are opened during the 90-day learning mode period, so authentication codes are applied automatically. For logfiles that remain untouched during this time, plan for manual authentication before enforcement mode begins. See the Additional information section below for detailed guidance. Additional information: Common Log File System (CLFS) Authentication Mitigation CLFS Authentication Mitigation - Frequently asked questions (FAQ) -
Windows Office Hours: January 15, 2026
MC1215830 · stayInformed · normal · Updated 01/08/2026 19:04
Services: Windows
Read message
If you are an IT admin with questions about managing and updating Windows, we want to help. Every third Thursday of the month, we host a live chat-based event on the Tech Community called Windows Office Hours. Members of the Windows, Microsoft Intune, Windows Autopilot, Windows Autopatch, and Windows 365 engineering teams will be standing by to answer your questions. We also have experts from FastTrack, the Customer Acceleration Team, and Microsoft public sector teams. Want to attend the January 15 session of Office Hours? Add it to your calendar and select Attend on the event page to let us know you’re coming. There is no video or live meeting component. Simply visit the event page, log in to the Tech Community, and leave your questions in the Comments section. You can also bookmark https://aka.ms/Windows/OfficeHours for upcoming dates (and the ability to add this event to your calendar). We look forward to helping you. -
Microsoft 365 admin center multifactor authentication enforcement
MC1215070 · planForChange · normal · Updated 01/08/2026 01:19
Services: Microsoft 365 suite
Read message
If you have already set up multi-factor authentication, thank you. No further action is needed at this time. If you have not, please read on. As part of our ongoing commitment to advancing cybersecurity across our company and products, last year, starting February 2025, Microsoft began requiring all users to use multi-factor authentication (MFA) when signing into the Microsoft 365 admin center. Starting February 9th 2026, Microsoft will continue to ramp up enforcement, and users will be unable to sign in to the Microsoft 365 admin center without successfully completing MFA. Implementing MFA in the Microsoft 365 admin center significantly reduces the risk of account compromise, prevents unauthorized access, and safeguards sensitive data. By adding an extra layer of protection beyond standard username and password authentication, MFA makes it harder for attackers to steal data and prevents unauthorized access from phishing, credential stuffing, brute force, or password reuse attacks. Take action now Global admins: To set up MFA in your organization now, visit the MFA setup guide at aka.ms/MFAWizard or refer to Set up multifactor authentication for Microsoft 365 Users accessing the Microsoft 365 admin center: Check your verification methods and add one if needed by going to aka.ms/mfasetup. How this will affect your organization MFA will need to be enabled for your tenant to ensure admins are able to sign-in to the Microsoft 365 admin center. Note that the following Microsoft 365 admin center URLs are impacted by this change: https://portal.office.com/adminportal/home https://admin.cloud.microsoft https://admin.microsoft.com What to do to prepare If you have not already, set up MFA as soon as possible to avoid sign-in issues once mandatory MFA enforcement is rolled out to your organization. If you have already set up MFA, no action is required. It is recommended that you verify that all users accessing the Microsoft 365 admin center have added a verification method to their account (such as a Microsoft Authenticator). Global admins: To set up MFA in your organization now, visit the MFA setup guide at aka.ms/MFAWizard or refer to Set up multifactor authentication for Microsoft 365. Users accessing the Microsoft 365 admin center: Check your verification methods and add one if needed by going to aka.ms/mfasetup. For more information, refer to the FAQs in the blog post here. Additional info URL (i.e., link to relevant support doc): https://aka.ms/mfasetup Multifactor authentication for Microsoft 365 - Microsoft 365 admin | Microsoft Learn Set up multifactor authentication for users - Microsoft 365 admin | Microsoft Learn -
Get started with December 2025 improvements in Windows 11
MC1214913 · stayInformed · normal · Updated 01/07/2026 18:00
Services: Windows
Read message
Start using the newest Windows 11 capabilities with helpful tips and actionable steps summarized in one place. Discover resources to prepare for Secure Boot certificate update, track and remediate CVEs in Windows Autopatch, opt in to native NVMe support in Windows Server 2025, and much more to help keep your organization protected and productive. When will this happen: Improvements summarized in this monthly recap are already available. Note that some of them are rolling out gradually. How this will affect your organization: You can start seeing improvements across various workflows in your organization with: Common Vulnerabilities and Exposures (CVEs) report in Windows Autopatch Microsoft Intune Suite capabilities included in Microsoft 365 plans Hardware-accelerated BitLocker Secure Boot certificate update resources Optimized multimedia call redirection on Azure Virtual Desktop and Windows 365 Native NVMe support in Windows Server 2025 Additional improvements released in December What you need to do to prepare: Read the new monthly recap and additional information to start benefiting from the latest improvements. Additional information: Read the monthly recap at Windows news you can use: December 2025. It includes highlights from the following channels: Windows IT Pro Blog Microsoft Intune Blog Microsoft Intune Customer Success Blog Microsoft Security Blog Windows 11 update history Windows Server update history -
Take Action: Out-of-band update to address MSMQ service issues leading to queue operations and resource-related errors
MC1199746 · stayInformed · normal · Updated 12/18/2025 22:14
Services: Windows
Read message
Microsoft has identified an issue affecting Message Queuing (MSMQ) functionality in some enterprise environments after installing the December 2025 Windows security update (released December 9, 2025). Individuals using Windows Home or Pro editions on personal devices are very unlikely to experience this issue, as it primarily affects enterprise or managed IT environments. To address this issue, an out-of-band (OOB) update has been released, today, December 18, 2025, on the Microsoft Update Catalog. For more information and installation instructions, refer to the appropriate KB article for each affected version of Windows listed below. For additional guidance, see How to download updates from the Microsoft Update Catalog. Windows 10, version 22H2 ESU and Windows 10 Enterprise LTSC 2021 (KB5074976) Windows Server 2019 and Enterprise LTSC 2019 (KB5074975) Windows Server 2016 and Windows 10 LTSB 2016 (KB5074974) Windows Server 2012 R2 (KB5074978) Windows Server 2012 (KB5074980) Windows Server 2008 R2 (KB5074977) Windows Server 2008 (KB5074979) -
(Updated) Please update Microsoft 365 Office apps to a version higher than 16.0.18827.20202
MC1127222 · planForChange · normal · Updated 12/12/2025 17:32
Services: Microsoft 365 apps
Read message
Updated December 12, 2025: We have updated the timeline. Thank you for your patience. To ensure continued high-quality performance of the Read Aloud, Transcription, and Dictation features in Microsoft 365 Office apps, we’re upgrading the backend service that powers these capabilities. As a result, these features will no longer function on Office clients running versions earlier than 16.0.18827.20202 after September 2026. We are extending the supporting period for customers to prepare and upgrade to the supported version. Here is the updated timeline: General Availability (Worldwide): End of September 2026 (previously end of January) General Availability (GCC, GCC High, DoD): End of November 2026 (previously end of March) How this affects your organization If your organization is using Microsoft 365 Office apps with version numbers lower than 16.0.18827.20202, users will lose access to Read Aloud, Transcription, and Dictation features after the dates listed above. There is no change to the user experience for clients on supported versions. What you can do to prepare To avoid service disruption, ensure that all Office clients are updated to version 16.0.18827.20202 or later before the applicable deadline. You can learn more about these features using the following resources: Listen to your Word documents Transcribe your recordings Dictate your documents in Word Compliance considerations No compliance considerations identified, review as appropriate for your organization. -
Windows Office Hours: December 18, 2025
MC1194479 · stayInformed · normal · Updated 12/11/2025 18:02
Services: Windows
Read message
If you are an IT admin with questions about managing and updating Windows, we want to help. Every third Thursday of the month, we host a live chat-based event on the Tech Community called Windows Office Hours. Members of the Windows, Microsoft Intune, Windows Autopilot, Windows Autopatch, and Windows 365 engineering teams will be standing by to answer your questions. We also have experts from FastTrack, the Customer Acceleration Team, and Microsoft public sector teams. Want to attend the December 18 session of Office Hours? Add it to your calendar and select Attend on the event page to let us know you’re coming. There is no video or live meeting component. Simply visit the event page, log in to the Tech Community, and leave your questions in the Comments section. You can also bookmark https://aka.ms/Windows/OfficeHours for upcoming dates (and the ability to add this event to your calendar). We look forward to helping you. -
Latest on Windows quality updates out of the box – now disabled by default
MC1194065 · stayInformed · normal · Updated 12/10/2025 23:29
Services: Windows
Read message
Starting with the January 2026 security update, the AllowOOBEUpdates CSP policy will be available and disabled by default. It shows up as a new setting on the Windows Autopilot Enrollment Status Page (ESP). This policy allows you to install the latest Windows quality updates during the out-of-box experience (OOBE) on eligible devices. Devices must be Microsoft Entra joined or Microsoft Entra hybrid joined and running Windows 11, version 22H2 or later. The original announcement and documentation are updated to reflect this change and to clarify device targeting. When will this happen: January 2026: The AllowOOBEUpdates CSP policy will be available and disabled by default. August 2025: The original announcement introduced this new capability. How this will affect your organization: With Windows Autopilot and Microsoft Intune (or alternative management solutions), you can maintain seamless control over quality update behavior during provisioning, while ensuring alignment with organizational security and compliance requirements. What you need to do to prepare: Review the prerequisite criteria in additional information. Make sure that your devices are imaged with the November 2025 Windows non-security update or later or are automatically updated with the November 2025 OOBE zero-day patch (ZDP) update. Learn more about these updates and the capability under additional information. Additional information: Get ready for Windows quality updates out of the box AllowOOBEUpdates System Policy CSP KB5071430: Out of Box Experience update for Windows 11, version 24H2 and 25H2, and Windows Server 2025: November 21, 2025 KB5071892: Out of Box Experience update for Windows 11, version 22H2 and 23H2: November 20, 2025 Windows Autopilot Enrollment Status Page -
The December 2025 Windows security update is now available
MC1193628 · stayInformed · normal · Updated 12/09/2025 19:44
Services: Windows
Read message
The December 2025 security update is now available for all supported versions of Windows. We recommend that you install these updates promptly. For more information about the contents of this update, see the release notes, which are easily accessible from the Windows 11 update history page. To learn more about the different types of monthly quality updates, see Windows monthly updates explained. Highlights for the Windows 11, version 25H2 update: This security update includes improvements that were a part of update KB5070311 (released December 1, 2025). This update addresses security issues for your Windows operating system. This update addresses an issue where Ask Copilot didn’t activate the Click to Do* window as expected. The window now appears in the foreground when you share data with Copilot. This update addresses an issue where File Explorer briefly flashes white when you navigate between pages. This issue might occur after you install KB5070311. This update fixes an issue where external virtual switches lose their physical network adapter (NIC) bindings after a host restart. * Experiences for Copilot+ PCs only Short on time? Watch our Windows 11 release notes video for this month's tips. For instructions on how to install this update, see the KB for your operating system listed below: Windows 11, versions 25H2 and 24H2: KB5072033 Windows 11, version 23H2: KB5071417 Windows 11 Enterprise LTSC 2024: Hotpatch KB5072014 Windows 10, versions 22H2 and 21H2: KB5071546 Windows 10 Enterprise LTSC 2019 and Windows Server 2019: KB5071544 Windows 10 LTSB 2016 and Windows Server 2016: KB5071543 Windows Server 2025: KB5072033 Windows Server 2025 Datacenter: Azure Edition: Hotpatch KB5072014 Windows Server 2022: KB5071547 Windows Server 2022 Datacenter: Azure Edition: Hotpatch KB5071413 Windows Server 2012 R2: Monthly Rollup: KB5071503 Windows Server 2012: Monthly Rollup: KB5071505 Windows Server 2008 R2 Service Pack 1: Monthly Rollup: KB5071501 / Security Only: KB5071506 Windows Server 2008 SP2: Monthly Rollup: KB5071504 / Security Only: KB5071507 Note A separate standalone PowerShell update is available for the versions of Windows listed below and will be offered for devices using hotpatch updates. If any PowerShell components are active during installation, a system restart will be required to complete the update. Windows 11, versions 24H2 and 25H2: KB5074204 Windows Server 2025: KB5074204 Windows Server 2022: KB5074353 IMPORTANT Because of minimal operations during the Western holidays and the upcoming new year, there will be no December 2025 non-security preview update in the second part of the month. Normal monthly servicing for both security and non-security preview updates will resume in January 2026. -
How to use Microsoft Intune to update expiring Secure Boot certificates
MC1193371 · stayInformed · normal · Updated 12/08/2025 21:59
Services: Windows
Read message
You can now deploy, manage, and monitor Secure Boot certificate updates. This method represents an alternative to setting registry keys and using Group Policy. You can use Intune to deploy on all domain-joined Windows clients, opt out of high-confidence buckets, and opt in to Microsoft managing these updates. When will this happen: The following settings are now available in the Intune settings catalog: Configure Microsoft Update Managed Opt-In Configure High-Confidence Opt-Out Enable SecureBoot Certificate Updates How this will affect your organization: As the 2011 Secure Boot certificates will start expiring in June 2026, it is essential that organizations start planning for and updating to 2023 certificates. You can now use Microsoft Intune, in addition to registry keys and Group Policy, to deploy, manage, and monitor this update process. The three new settings are disabled by default. Enable them to start taking advantage of the desired capabilities. What you need to do to prepare: To manage Secure Boot certificate updates in Intune, enable the new settings by navigating to the Microsoft Intune admin center: Under Devices > Manage devices, select Configuration. Select Create and select New Policy. Select Create a profile in the right-hand pane. Fill in Platform with Windows 10 and later. Select the Settings Catalog under the Profile Type. Begin creating a profile by giving the profile a name. Press Next. Under Configuration settings, select Add settings. In the Settings picker, search for Secure Boot. There should be three settings in the Secure Boot category. Select the desired settings for your organization: Configure Microsoft Update Managed Opt-In, Configure High-Confidence Opt-Out, and Enable SecureBoot Certificate Updates (preselected for you). Finish the profile for the devices that will use these settings. Additional information: Read complete guidance at Microsoft Intune method of Secure Boot for Windows devices with IT-managed updates. Compare this method to Registry key updates for Secure Boot: Windows devices with IT-managed updates. Compare this method to Group Policy Objects (GPO) method of Secure Boot for Windows devices with IT-managed updates. See how these methods work together in Secure Boot playbook for certificates expiring in 2026. -
Workspaces in Edge: Upcoming migration to improved architecture
MC1192661 · planForChange · normal · Updated 12/06/2025 00:17
Services: Microsoft 365 suite
Read message
[Introduction] We’re improving the reliability and performance of Microsoft Edge Workspaces by migrating to a new architecture. Workspaces, introduced in 2022, lets users create durable sets of tabs that can be saved and shared. As part of this update, we will migrate saved Workspace data from OneDrive/SharePoint to the Edge Sync service and remove the collaboration/share functionality. [When this will happen:] General Availability (Production, GCC, GCCH, DoD): Rollout begins mid-February 2026. [How this affects your organization:] Who is affected: All organizations using Microsoft Edge Workspaces. What will happen: Saved Workspace data will migrate from OneDrive/SharePoint to Edge Sync service. Collaboration and sharing functionality will be removed. Organizations that have disabled Workspaces via EdgeWorkspacesEnabled policy will not have data migrated. If Sync is disabled through policy, existing Workspaces created under the current architecture will still migrate. However, new Workspaces created after migration will not sync across devices and will remain local to each device. [What you can do to prepare:] No admin action is required; migration will occur automatically during rollout. If you wish to opt out, contact Microsoft CSS before rollout begins. If your organization has significant Workspace usage, notify users and update internal documentation. Learn more: Workspaces in Microsoft Edge [Compliance considerations:] No compliance considerations identified, review as appropriate for your organization. -
Secure Boot AMA: Ask Microsoft Anything on December 10
MC1192217 · stayInformed · normal · Updated 12/04/2025 22:00
Services: Windows
Read message
Join us December 10, 2025, at 8:00 AM PST for a live Ask Microsoft Anything (AMA) session focused on updating Secure Boot certificates on your Windows devices before they expire in June 2026. This event gives IT admins the chance to ask questions and get expert guidance on Secure Boot configuration, update scenarios, inventorying and preparing your environment, and formulating the right deployment plan for your organization. Members of the Windows team will be available to answer your questions, share tips, and provide insights to help you prepare devices for Secure Boot certificate deployment. Visit the AMA: Secure Boot event page, log in to Tech Community, and post your questions in advance or during the live broadcast in the comments section. Save the date and start posting your questions early. -
New Windows Autopatch reports on CVEs
MC1192178 · stayInformed · normal · Updated 12/04/2025 18:02
Services: Windows
Read message
A new Windows Autopatch report empowers your organization to prioritize update deployment, demonstrate compliance, and maintain a robust security posture. The Common Vulnerabilities and Exposures (CVEs) report joins your other Windows quality update reports right in the Microsoft Intune admin center. Use it to view Windows CVEs addressed by recent quality updates and follow links to remediation documentation and device-level vulnerability status. When will this happen: The new report is already available. How this will affect your organization: This report can help simplify how you track which vulnerabilities have been remediated and which devices remain at risk. It can also help strengthen your vulnerability response strategy by identifying and linking to specific Windows updates that address each vulnerability. What you need to do to prepare: Read Additional information to learn how to get started with this new report in Windows Autopatch. If you don’t use Windows Autopatch yet, you can get familiar with it through Windows Autopatch documentation. Additional information: New Windows Autopatch reports on CVEs Common Vulnerabilities and Exposures (CVEs) report Windows Autopatch update readiness MSRC Security Update Guide: Vulnerabilities Security Copilot Vulnerability Remediation Agent in Microsoft Intune -
Microsoft Entra ID: Enhance protection of the authentication experience by blocking external script injection
MC1191924 · stayInformed · normal · Updated 12/03/2025 21:44
Services: Microsoft Entra
Read message
Introduction As part of Microsoft’s Secure Future Initiative, we’re updating our Content Security Policy for the Microsoft Entra ID sign-in experience. This change adds an extra layer of protection by allowing only scripts from trusted Microsoft domains to run during authentication, blocking unauthorized or injected external code. This proactive measure helps safeguard users against threats like cross-site scripting (XSS), further strengthening security for your organization. When this will happen General Availability (Production/Worldwide only): Rollout begins mid-October 2026 Expected completion by late October 2026 Periodic communications will be sent closer to release. How this affects your organization Who is affected: Organizations using browser-based sign-in experiences on URLs starting with login.microsoftonline.com. No impact to Microsoft Entra External ID tenants. What will happen: A new Content Security Policy header will be added to Microsoft Entra sign-in pages. Scripts will only be allowed from Microsoft trusted CDN domains. Inline script execution will only be allowed from trusted Microsoft sources. Browser extensions or tools that inject code into the sign-in page will stop working, though users can still sign in. What you can do to prepare If you do not use tools or extensions that inject code into the sign-in experience, no action is required. If you do use such tools, switch to alternatives that don’t inject code. Test your sign-in flows thoroughly before rollout to identify and resolve any issues early. Testing instructions can be found on our CSP Guide for Microsoft Entra ID. Learn more: Content Security Policy Overview for Microsoft Entra ID Microsoft Entra ID Content Security Policy Public Blog Post on Techcommunity Microsoft Secure Future Initiative The CSP nonce guide | Content Security Policy (CSP) quick reference guide The CSP script-src directive guide | Content Security Policy (CSP) quick reference guide Why XSS still matters: MSRC’s perspective on a 25-year-old threat | Microsoft Blog Compliance considerations No compliance considerations identified; review as appropriate for your organization. -
Windows news you can use: November 2025
MC1191556 · stayInformed · normal · Updated 12/02/2025 18:09
Services: Windows
Read message
November’s edition of Windows news you can use recaps the new Windows capabilities announced at Microsoft Ignite so your organization and IT team can catch up and dive deeper into the details. Discover upcoming events to help you keep your deployment and device management projects moving. Find a summary of important lifecycle reminders for Windows 10, Windows 11, Windows Server, and Microsoft Configuration Manager. Learn about new tools and guidance. When will this happen: Some of the features described in this monthly recap are now available, either broadly or in public preview. Others are planned for 2026. Note that some capabilities roll out gradually and may not yet be available for your market. What you need to do to prepare: Read the November 2025 edition of Windows news you can use so you can plan for these new capabilities and utilize them in your organization as they are released. Additional information: Follow the Windows IT Pro Blog for regular updates and take advantage of monthly Windows Office Hours for questions and feedback. -
The November 2025 Windows non-security preview update is now available
MC1191307 · stayInformed · normal · Updated 12/01/2025 22:04
Services: Windows
Read message
The November 2025 non-security preview update is now available for Windows 11, versions 25H2 and 24H2. Information about the contents of this update is available from the release notes, which are accessible from the Windows 11 update history page. To learn more about the different types of monthly quality updates, see Windows monthly updates explained. Looking to explore upcoming features and improvements in Windows 11? Check out the Windows roadmap. It includes what’s coming to the Windows Insider Program, what’s gradually rolling out, and what’s generally available. Highlights for the Windows 11, version 25H2 update: The search results menu displays more available results, making it easier to quickly find and modify your settings. A scroll bar lets you view all search results.* You can use Windows Studio Effects, which provides AI-powered camera enhancements, on an additional camera such as a USB webcam or your laptop’s built-in rear camera.* When Windows Spotlight is set as your desktop background, the context menu now includes two options: Learn more about this background and Next desktop background. File Explorer now offers a more consistent dark mode experience. * Experiences for Copilot+ PCs only For instructions on how to install this update, see the KB for your operating system listed below: Windows 11, versions 25H2 and 24H2: KB5070311 IMPORTANT Because of minimal operations during the Western holidays and the upcoming new year, there will be no December 2025 non-security preview update. There will be a monthly security update for December 2025. Normal monthly servicing for both security and non-security preview updates will resume in January 2026. -
Ask the Windows experts at Tech Community Live
MC1190119 · stayInformed · normal · Updated 11/26/2025 18:09
Services: Windows
Read message
On December 2, Tech Community Live presents three hours of live, Windows-focused Ask Microsoft Anything (AMA) sessions. This is a free online event. Members of the Windows engineering team will be answering questions, offering tips, and providing additional insights on the announcements made at Microsoft Ignite. Topics will include: managing Windows updates, managing AI and agents in Windows, Windows backup and restore options, and Windows accessibility in the enterprise. When will this happen: The live streams will begin at 8:00 AM PST (3:00 PM UTC) and conclude at 11:00 AM PST (6:00 PM UTC). All sessions will be recorded and available on demand. The ability to post questions on the Tech Community will be open until Friday, December 5. Closed captions will be AI-generated during the live event. Human-generated closed captions and text-based transcripts will be available later in the week. What you need to do to prepare: Save the date for the full event and add individual sessions to your calendar. Questions can be posted in advance. To post a question, sign in to the Tech Community, scroll to the bottom of the session page, and select Comment. We encourage you to post each question as a separate comment to ensure they are each seen and addressed. Additional information: Visit https://aka.ms/TCL/Windows to add this event to your calendar, see the hour-by-hour agenda, and find details on how to participate. -
WINS removal: Moving forward with modern name resolution
MC1188937 · stayInformed · normal · Updated 11/21/2025 21:56
Services: Windows
Read message
If you manage Windows Servers, plan for removal of Windows Internet Name Service (WINS). WINS was officially deprecated since Windows Server 2022 and will be removed from all Windows Server releases following Windows Server 2025. Standard support will continue through the lifecycle of Windows Server 2025, until November 2034. We encourage you to migrate to modern Domain Name System (DNS)-based name resolution solutions before then. When will this happen: WINS deprecation was announced in Windows Server 2022. Deprecation means the feature remains supported and maintained, but there is no further active development or new functionality planned. November 2034 is the end of the lifecycle for Windows Server 2025, which also marks the end of support for WINS. How this will affect your organization: Once removal takes effect, the following components will no longer be part of Windows Server: WINS Server role and associated binaries WINS Microsoft Management Console (MMC) snap-in WINS automation APIs and related management interfaces Please prepare, evaluate, and migrate to modern Domain Name System (DNS)-based name resolution solutions. What you need to do to prepare: Take proactive steps now to ensure a smooth migration: Audit dependencies: Inventory applications and services that rely on NetBIOS name resolution to understand impact. Migrate to DNS: Implement conditional forwarders, split-brain DNS, or search suffix lists to replace WINS functionality with scalable, modern DNS solutions. Update applications: Modernize or retire legacy applications that depend on WINS to avoid future compatibility issues. Avoid temporary workarounds: Solutions like static host files do not scale and are not sustainable for long-term environments. Consult additional resources for compete details and guidance. Additional information: WINS removal: Moving forward with modern name resolution Features Removed or No Longer Developed in Windows Server Windows Internet Name Service (WINS) Domain Name System (DNS) in Windows and Windows Server -
Take Action: Out-of-band update to address November 2025 hotpatch update being reoffered after Windows update scan
MC1188558 · stayInformed · normal · Updated 11/20/2025 22:15
Services: Windows
Read message
Microsoft has identified an issue affecting some organizations using hotpatch updates on devices running Windows 11 Enterprise, version 25H2. After installing the hotpatch update KB5068966 released November 11, 2025, affected devices repeatedly download and install the same update when a Windows Update scan is run. This behavior does not impact device functionality; only the update history will reflect the latest installation timestamp. An out-of-band (OOB) update was released today, November 20, 2025, to address this issue. This is a cumulative update, so you do not need to apply any previous updates before installing this update, as it supersedes all previous updates for affected versions. If you have not yet deployed the November 2025 hotpatch update (KB5068966) on Windows 11, version 25H2 devices in your environment, we recommend you apply this OOB update (KB5072753) instead. -
The November 2025 Windows non-security preview update is now available for Windows 11, version 23H2
MC1188557 · stayInformed · normal · Updated 11/20/2025 22:15
Services: Windows
Read message
The November 2025 non-security preview update is now available for all supported editions of Windows 11, version 23H2. The non-security preview update for Windows 11, versions 25H2 and 24H2 will be available soon. Information about the contents of this update is available from the release notes, which are accessible from the Windows 11 update history page. To learn more about the different types of monthly quality updates, see Windows monthly updates explained. Looking to explore upcoming features and improvements in Windows 11? Check out the Windows roadmap. It includes what’s coming to the Windows Insider Program, what’s gradually rolling out, and what’s generally available. Highlights for the Windows 11, version 23H2 update: This update makes quality improvements to the servicing stack, which is the component that installs Windows updates. This update addresses an issue where File Explorer sometimes didn’t respond to mouse clicks until you closed and reopened it. This update addresses an issue with extracting .tar files when file or folder names contain more than 34 commonly used Chinese characters. This update addresses an issue where the HideRecommendedSection policy didn’t work in Windows 11 Enterprise multi-session environments, such as Azure Virtual Desktop (AVD). For instructions on how to install this update, see the KB for your operating system listed below: Windows 11, version 23H2: KB5070312 IMPORTANT Because of minimal operations during the Western holidays and the upcoming new year, there will be no December 2025 non-security preview update. There will be a monthly security update for December 2025. Normal monthly servicing for both security and non-security preview updates will resume in January 2026. -
Microsoft Entra ID: Retirement of duplicative properties in passkey (FIDO2) authentication methods policy
MC1188230 · planForChange · normal · Updated 11/19/2025 23:34
Services: Microsoft Entra
Action required by: 10/14/2027 07:00
Read message
Introduction Starting October 2027 and ending November 2027, we will retire the isAttestationEnforced and keyRestrictionsproperties from the existing fido2AuthenticationMethodConfiguration API schema. This change aligns with the latest update to the passkey policy API schema, which introduces support for granular group-based configurations with passkey profiles. During the retirement period, isAttestationEnforced and keyRestrictions will remain in sync with their counterparts attestationEnforcement and keyRestrictions within the Default passkey profile. When this will happen Retirement begins in mid-October 2027 and is expected to complete by early November 2027. How this affects your organization: You are receiving this message because our reporting indicates your organization may be using this feature. Who is affected: Admins managing FIDO2 authentication configurations and any custom automations or third-party integrations using these properties. What will happen isAttestationEnforced and keyRestrictions properties will be retired. New properties are available in the updated passkey policy API schema. Existing properties will sync with new ones during the transition period. Automations or integrations using retired properties will stop working after the change. What you can do to prepare Review your current configuration. Update any custom automations and third-party integrations to support the new schema. Notify your admins and update internal documentation. Screenshot - The read arrows indicate the properties to be retired: Learn more: fido2AuthenticationMethodConfiguration resource type | Microsoft Graph | Microsoft Learn Compliance considerations: No compliance considerations identified, review as appropriate for your organization. -
(Updated) Microsoft Publisher will no longer be supported after October 2026
MC716267 · planForChange · normal · Updated 11/11/2025 21:18
Services: Microsoft 365 apps
Read message
Updated November 11, 2025: We are updating this post to serve as a reminder of this change. We are dedicated to providing our customers with the tools they need to achieve what matters, in their work and life. In order to focus on new benefits, we occasionally remove features and products. In October 2026, Microsoft Publisher will reach its end of life. After that time, it will no longer be included in Microsoft 365 and existing on-premises suites will no longer be supported. Until then, support for Publisher will continue and users can expect the same experience as today. As we look ahead to the retirement of Microsoft Publisher, we are exploring modern ways to achieve other common Publisher scenarios across applications like Microsoft Word, PowerPoint, and Designer. We will update as we have more to share. [When this will happen:] October 13, 2026 [How this will affect your organization:] You can continue to use Publisher with its current functionality until October 2026. Support for the perpetual version of Publisher will end in October 2026, when Office LTSC 2021 reaches end of support. Microsoft 365 customers will not be able to access Publisher from that date forward. [What you need to do to prepare:] No action is required at this time. This notice is to allow you sufficient time to plan. We will share additional updates as the date approaches. -
Microsoft Defender: Application Guard for Office is being removed
MC1182696 · planForChange · normal · Updated 11/04/2025 00:41
Services: Microsoft 365 suite
Read message
Microsoft Defender Application Guard for Office was retired in April 2024 and is now being removed from Office. This change aligns with the end of support for Windows 11 version 23H2 and helps streamline the security experience for users. Documents that previously opened in Application Guard will now open in Protected View, maintaining strong protection against threats. When this will happen: Phase 1: Removal begins with Office version 2602 Current Channel: early February 2026 Monthly Enterprise Channel: April 2026 Semi-Annual Enterprise Channel: July 2026 Phase 2: Full removal with Office version 2612 Current Channel: early December 2026 Monthly Enterprise Channel: February 2027 Semi-Annual Enterprise Channel: July 2027 How this affects your organization: Who is affected: All Win32 users who previously used Microsoft Defender Application Guard for Office. What will happen: Files that previously opened in Application Guard will now open in Protected View. Application Guard for Office will be disabled in Phase 1; support exceptions may be available until Phase 2. Application Guard for Office will be fully removed in Phase 2 with no workaround. Admins are encouraged to enable Microsoft Defender for Endpoint Attack Surface Reduction (ASR) rules and Windows Defender Application Control (WDAC). What you can do to prepare: No admin action is required for the removal itself. However, to maintain strong protection, we recommend: Enable Microsoft Defender for Endpoint ASR rules to block risky behaviors in Office files. Enable Windows Defender Application Control (WDAC) to ensure only trusted, signed code runs on devices. Review internal documentation and helpdesk guidance if your organization previously relied on Application Guard for Office. For instructions on verifying if users are using Application Guard for Office, refer to Confirm that Application Guard for Office is enabled and working - Application Guard for Office for admins | Microsoft Learn. Compliance considerations: No compliance considerations identified, review as appropriate for your organization. -
(Updated) Introducing Knowledge Agent (preview): AI-powered content optimization for SharePoint and Copilot
MC1155312 · stayInformed · normal · Updated 10/22/2025 16:36
Services: SharePoint Online
Read message
Updated October 22, 2025: We have updated the content below. Thank you for your patience. [Introduction] We’re introducing Knowledge Agent, a built-in SharePoint capability that helps organizations prepare content for AI at scale. It unifies fragmented AI features into a single, context-aware interface that adapts to user roles and surfaces intelligent actions directly in the flow of work. This enhancement supports high-quality, trustworthy responses from Microsoft 365 Copilot and custom agents. [When this will happen:] Public Preview (Worldwide): Begins mid-September 2025; completes by late February 2026. [How this affects your organization:] Who is affected: Users with a Microsoft 365 Copilot license on tenants opted into Knowledge Agent preview. Admins managing SharePoint content and agents. What will happen: A floating button will appear in the lower-right corner of SharePoint surfaces, launching a context-aware menu with intelligent actions. Role-based capabilities include: Content managers can structure, tag, and enrich content using smart metadata and AI recommendations. Site owners can identify stale pages, broken links, and content gaps. Content creators can generate pages and documents using natural language prompts. Collaborators and viewers can surface grounded insights via natural language chat. Impact to SharePoint agents users: Ready-made SharePoint site agents are now exclusively available to customers with Microsoft 365 Copilot licenses. These agents are no longer accessible through the Microsoft 365 Pay-As-You-Go (PAYG) billing model under the SharePoint agents meter. PAYG customers can still create custom-built, no-code SharePoint agents using the same SharePoint agents meter, but they will not have access to the ready-made site agents unless they are Microsoft 365 Copilot licensed. The SharePoint ribbon icon has changed from the Copilot logo to a hexagon to indicate Knowledge Agent-enabled sites. Agent creation remains available via: Site homepage Agent chat pane AI actions menu in the command bar of a document library Content menu of selected file(s) in a document library [What you can do to prepare:] Knowledge Agent Public Preview begins September 18, 2025 on a tenant opt-in basis to users with a Microsoft 365 Copilot license. Learn more about opting into the preview: Get started with Knowledge Agent (preview). If you receive a command not recognized error running the commands , please review this article for additional troubleshooting. For tenants who have opted in, it is possible to opt out for specific sites.The ability to opt-in for certain types is coming in mid-to-late November. No setup is required for individual features. Learn more via the Knowledge Agent blog. [Compliance considerations:] ConsiderationExplanation Introduces or modifies AI/ML capabilitiesKnowledge Agent introduces new AI-driven features that interact with customer content to provide intelligent actions and insights. Provides new user interaction with generative AIUsers can interact with SharePoint content using natural language prompts and chat. Modifies access to existing featuresChanges availability of ready-made SharePoint agents based on licensing. Includes admin controlAdmins can opt in/out of preview and manage site-level availability. -
(Updated) Microsoft Defender: Changes to Defender for Cloud Apps alerts
MC992217 · planForChange · normal · Updated 06/05/2025 14:56
Services: Microsoft Defender XDR
Read message
Updated June 5, 2025: We have updated the timeline below. Thank you for your patience. Coming soon for Microsoft Defender for Cloud Apps: A change to alerts generated by events originating from Defender for Cloud Apps that are generated in the Microsoft Defender XDR detection engine This rollout aims to provide more accurate and precise information on the origin of these alerts, enabling customers to identify, manage, and respond to alerts more effectively. [When this will happen:] General Availability (GCC, GCC High, DoD, Production, DoD): We will begin rolling out early March 2025 and expect to complete by late June 2025 (previously late May). [How this will affect your organization:] We will change the field indicating the alert source in the alert data itself. Note: The rollout will only affect new alerts generated after the rollout and will not alter existing alerts. This rollout will be reflected in all experiences where alerts are represented, including Incidents & alerts queues in the XDR portal, Advanced hunting, and the correlating APIs and SIEM systems. In the Defender XDR portal, the change will be reflected in the Service sources field, replacing the current Microsoft Defender XDR values with the new value Defender for Cloud Apps. The detection sources will remain unchanged and will continue to indicate the detections are generated in the XDR detection engine. The alert ID prepended characters of some of the alerts will also be changed to comply with the Defender XDR mapping. Learn more about the different alert sources in Defender XDR in the Alert sources section of Investigate alerts in Microsoft Defender XDR - Microsoft Defender XDR | Microsoft Learn In the Microsoft Graph API, Microsoft Defender for Endpoint streaming API, and the Microsoft Azure Events Hub, the change will be reflected in the alert resource type under the property serviceSource, and the previous values of microsoft365Defender will change to microsoftDefenderForCloudApps. Learn more about the Graph API alert resource: alert resource type - Microsoft Graph v1.0 | Microsoft Learn Learn more about Streaming API: Stream Microsoft Defender XDR events - Microsoft Defender XDR | Microsoft Learn [What you need to do to prepare:] This rollout will happen automatically by the specified date with no admin action required before the rollout. Administrators should review and update any custom alert rules, playbooks, or automations involving the alerts mentioned above (Service sources = Microsoft Defender XDR and Detection sources = Defender XDR, to ensure they reflect the new value. You may also want to notify your users about this change and update any relevant documentation. As a reminder, detection sources will remain unchanged, so if you only filter on detection sources, everything should continue to function as normal. -
(Updated) Retirement of Exchange Web Services in Exchange Online
MC676299 · planForChange · normal · Updated 04/18/2025 18:33
Services: Exchange Online
Read message
Updated April 18, 2025: We have updated the content. Thank you for your patience. In 2018, we announced that we were no longer making feature updates to Exchange Web Services (EWS) in Exchange Online, and we advised developers to move to Microsoft Graph. In September 2023, we announced that on October 1, 2026, we will start blocking EWS requests to Exchange Online. We are now less than 18 months from October 1, 2026. We have made progress on closing several parity gaps with more changes in development to be released in the coming quarters. Please refer to Deprecation of Exchange Web Services in Exchange Online for up-to-date guidance and roadmap information. If you haven't already, start the process of working with your application development organization and your application vendors to migrate active EWS applications on your tenant to the Graph API. [When this will happen:] October 1, 2026 [How this affects your organization:] While the EWS components of the service will continue to receive security updates and certain non-security updates, product design and features will remain unchanged. This change also applies to the EWS SDKs for Java and .NET, as well. Despite this announcement, EWS is still available and supported for use in production environments. But we strongly suggest migrating to Microsoft Graph to access Exchange Online data and gain access to the latest features and functionality. Today’s update and the retirement of EWS apply only to Microsoft 365 and Exchange Online (all environments); there are no changes to EWS in Exchange Server. Further, the changes in Exchange Online do not affect Outlook for Windows or Mac, Teams, or any other Microsoft product. In our original blog post, we said this change would affect only third-party (non-Microsoft) applications. We have expanded our effort and are now also removing EWS dependencies from Microsoft apps and services, and we’re going to complete that work well before October 2026. We intend to do this as quickly as possible without affecting the quality of service or product. There may be applications running on your tenant created by your organization or 3rd parties that use EWS. We recommend reviewing your application portfolio now to get an understanding of which apps need to be updated by your organization and which applications require updates from vendors. It is important to get started with this effort as soon as possible as the Graph API patterns are quite different from EWS. Equivalent Graph API operations may exhibit subtle differences that affect your use cases and application designs in unanticipated ways. Migrating Applications to Microsoft Graph We know there are several feature gaps between EWS and Microsoft Graph, and though the list below is not exhaustive, these are the gaps most frequently reported to us by developers: Access to Archive Mailboxes – We are working on delivering access to archive mailboxes via Microsoft Graph and will provide an updated timeline in the coming months. Folder Associated Information / User Configuration – We are working on these features and will provide an updated timeline in the coming months. Exchange Online Management – We are investigating solutions for this and will provide an updated timeline in the coming months. Access to Public Folders – After evaluating the usage of public folders, we have decided to restrict programmatic access to public folders to supported Outlook clients only, and for bulk import/export purposes. We will not provide APIs for programmatically creating, reading, updating and deleting public folders after October 2026 (also see Security Related Updates in Exchange Online). We know there are other gaps not listed above, and we continue to work on closing them, but it’s possible some functionality will not make it to Microsoft Graph. We encourage you to refer to Deprecation of Exchange Web Services in Exchange Online for up-to-date guidance and roadmap information. Next Steps The retirement of these APIs follows our Modern Lifecycle Policy. We understand changes like this may cause some inconvenience, but we are confident it will ensure more secure, reliable, and performant experiences. We will publish regular communications as we progress towards this deadline to aid affected tenants in identifying EWS usage. We encourage all customers to monitor Message Center and the Exchange Blog and Deprecation of Exchange Web Services in Exchange Online for related content. Thank you in advance for updating and opening your apps to a wider range of useful and intelligent features on Microsoft Graph. We are extremely excited about the growing opportunities that Microsoft Graph offers to developers, and we remain fully committed to our journey to empower developers to access Microsoft 365 data with the most modern features and tools. -
Microsoft Graph: New default passcode in the Create Meeting API
MC985483 · planForChange · normal · Updated 01/22/2025 02:05
Services: Microsoft 365 suite
Read message
Before this retirement, when creating an online meeting using the Microsoft Graph API, admins or users can choose whether to require a passcode. If no value is specified, the default behavior does not require a passcode. After this update: For enhanced security, users will still have the option to specify whether a passcode is required when creating a meeting. If no value is specified, the default behavior will require a passcode for the meeting. Effective February 24, 2025, the default value of the isPasscodeRequired property will change from false to true. Update your applications Review and update any applications that use the Create onlineMeeting API and passcode to ensure they account for the new default behavior. Looking ahead In October 2027, we will remove the option to specify the need for passcodes. This change will ensure that all meetings are consistently secured with passcodes. This final step will simplify the meeting creation process and provide an additional layer of protection for users. We will remove the isPasscodeRequired property on the joinMeetingIdSettings resource of the Microsoft Graph online meetings API.