15-April-2026 Below you will find a collection of news published yesterday. This news consists of Microsoft’s Roadmap when it is updated it will be below with items. Then there will be a section with the message center, if there is anything new there, this will be automatically included. And it contains a piece from blogs that I follow myself and would like to share with you. If I miss something in the blogs that do have an RSS feed, please let me know.
This entire post was automated via Microsoft Flow
have fun reading!
Office 365 Roadmap Updated: 2026-04-15
Additions : 12
Updates : 7
More Details At: www.roadmapwatch.com
Items from the MessageCenter in Microsoft 365
| (Updated) Streamline SharePoint publishing with new SharePoint page agentCategory:Microsoft Copilot (Microsoft 365)Nummer:MC1187834Status:stayInformed | Updated April 14, 2026: We have updated the timeline. Thank you for your patience. [Introduction] We’re introducing the SharePoint page agent, a declarative Copilot agent that enables users to create and refine SharePoint pages directly within Microsoft 365 Copilot experiences. Declarative agents respond to user intent expressed in natural language—users describe what they want, and the agent handles how to do it. This update allows users to generate structured content like meeting recaps, announcements, and project updates without switching apps or manually opening SharePoint. Screenshot 1: SharePoint page agent Screenshot 2: SharePoint page agent in Microsoft 365 Copilot Screenshot 3: SharePoint page agent – page card [When this will happen:]
Learn more: [Compliance considerations:]
| ||||||||||
| (Updated) Purview Communication Compliance: Temporary delays in processing due to planned infrastructure migrationCategory:Microsoft PurviewNummer:MC1214183Status:stayInformed | Updated April 14, 2026: We have updated the timing of this change below. Thank you for your patience. [Introduction] Microsoft Purview Communication Compliance is undergoing an infrastructure upgrade from January 5 to April 30, 2026, causing temporary processing delays, intermittent errors, and possible outdated report data. Although this migration is planned outside of normal business hours, some production clusters may experience higher loads, potentially causing brief delays in downstream processing. Brief delays in processing may occur during this migration, but no data will be lost. No action is required, but admins should inform teams about these short-term impacts. [When this will happen:] This migration will begin January 5, 2026, and end April 30, 2026 (previously April 15). [How this affects your organization:] Who is affected: What will happen:
This maintenance is scheduled outside of normal business hours to minimize impact. However, global organizations may experience some overlap with active hours. [What you can do to prepare:]
[Compliance considerations:] No compliance considerations identified; review as appropriate for your organization. | ||||||||||
| (Updated) Microsoft Teams: Organization evaluation score for apps and agentsCategory:Microsoft TeamsNummer:MC1218713Status:stayInformed | Updated April 14, 2026: We have updated the timeline. Thank you for your patience. [Introduction] Today, admins must manually review trust and compliance information for Teams apps and agents to determine whether they meet their organization’s security, privacy, and compliance requirements. To make this process more scalable and consistent, Teams will introduce a centralized evaluation experience. Admins will define their organization’s trust requirements once, and the system will generate a score and detailed evaluation report for each app and agent based on those requirements. This will help organizations make faster, more consistent approval decisions. This message is associated with Microsoft 365 Roadmap ID 532720. [When this will happen] Targeted release/Preview: We will begin rollout in late February 2026 and expect to complete by the end of March 2026. [How this will affect your organization] Who is affected: Admins who manage apps and agents in the Teams admin center. What will happen:
[What you can do to prepare] No action is required. This feature will be available automatically in the Teams admin center. Admins may choose to review their approval workflows once the feature becomes available. [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. | ||||||||||
| (Updated) Simplified Teams app bar to create a cleaner and more focused experienceCategory:Microsoft TeamsNummer:MC1234559Status:planForChange | Updated April 14, 2026: We have updated the timeline. Thank you for your patience. [Introduction] We’re simplifying the Microsoft Teams app bar to create a cleaner, more focused workspace and help users spend less time navigating and more time collaborating. This update reduces visual clutter and gives users more control over how much screen space the app bar uses. Screenshot: The new Teams app bar
This message is associated with Roadmap ID 557169. [When this will happen:]
[How this affects your organization:] Who is affected:
What will happen:
[What you can do to prepare:] No admin action is required.
[Compliance considerations:] No compliance considerations identified, review as appropriate for your organization. | ||||||||||
| (Updated) Always-on diagnostics for Endpoint DLP – Turned on by defaultCategory:Microsoft PurviewNummer:MC1246001Status:planForChange | Updated April 14, 2026: We have updated the timeline. Thank you for your patience. [Introduction] Starting in the last week of April 2026, Always-on diagnostics for Endpoint Data Loss Prevention (DLP) will be turned on by default for onboarded Windows devices in Microsoft Purview. Endpoint DLP diagnostic traces including policy evaluation logs, file classification results, enforcement actions, and error states are stored locally on the device in a secure, compressed proprietary format for up to 90 days. This collection helps eliminate the need to reproduce issues during Microsoft Support investigations. The ability to request that Microsoft collects critical diagnostic data as part of a support case will also be enabled. Endpoint diagnostic logs that you choose can then be securely shared with Microsoft for troubleshooting, reducing investigation effort and accelerating time to resolution for Endpoint DLP issues. [When this will happen:] General Availability (Worldwide): This change will go into effect late April 2026 (previously mid-April) [How this affects your organization:] Who is affected:
What will happen:
Note: Opting out of Always-on diagnostics may hinder your ability to effectively troubleshoot issues that arise in Endpoint Data Loss Prevention scenarios. Without this feature, organizations may experience prolonged investigation times, reduced visibility into policy behavior, and increased difficulty identifying and resolving Endpoint DLP issues. Keeping Always-on diagnostics enabled helps support the security, reliability, and operational stability of your environment. [What you can do to prepare:]
Learn more:
[Compliance considerations:]
| ||||||||||
| (Updated) Microsoft Agent 365 Generally Available May 1, 2026Category:Microsoft 365 suiteNummer:MC1247634Status:planForChange | Updated April 14, 2026: We have updated the content. Thank you for your patience. [Introduction] Microsoft Agent 365 will become Generally Available (GA) on May 1, 2026 for commercial customers. This milestone reflects extensive customer feedback and validation through the Frontier early-access program, where participating organizations have helped improve product quality, readiness, and overall experiences. GA enables broader adoption of Agent 365 while allowing Frontier participants to continue shaping future innovations. [When this will happen:]
[How this affects your organization:] Who is affected:
What will happen:
[What you can do to prepare:]
| ||||||||||
| (Updated) Outlook Mobile: Follow a meeting optionCategory:Exchange OnlineNummer:MC1248393Status:stayInformed | Updated April 14, 2026: We have updated the timeline. Thank you for your patience. [Introduction] We’re introducing a new Follow option for meetings in Outlook Mobile. This feature helps users stay informed when they cannot attend by prompting organizers to record the meeting and by ensuring followers receive key updates and follow‑up items. [When this will happen] General Availability (Worldwide): Rollout will begin in mid-May 2026 (previously mid-April) and is expected to complete by end of May 2026 (previously end of April). [How this affects your organization] Who is affected
What will happen
[What you can do to prepare] No admin action is required. Optional steps:
Learn more: Follow a meeting in Outlook | Microsoft Support [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. | ||||||||||
| (Updated) Microsoft Entra: Passkeys in Microsoft registration campaignsCategory:Microsoft EntraNummer:MC1253746Status:stayInformed | Updated April 14, 2026: After further review, we have decided not to move forward with this change at this time. You can refer to MC1279092 for updates. We apologize for any inconvenience this may cause and appreciate your understanding. [Introduction] As previously announced in MC1221452, Microsoft Registration Campaigns will support Passkeys (FIDO2) as an additional authentication method starting in early April 2026. This update helps organizations accelerate adoption of phishing‑resistant credentials by allowing administrators to opt users into Passkeys and deliver Passkey registration nudges during sign‑in. Please refer to MC1279092 for updates. [When this will happen] General Availability (Worldwide): We will begin rolling out in early April 2026 and expect to complete in late May 2026. [How this affects your organization] Who is affected
What will happen Microsoft‑managed state Your tenant will be impacted when all of the following conditions are met:
When these conditions are met, the following settings will update automatically:
Affected users will receive Passkey registration nudges at sign‑in after completing MFA. We will roll out these changes incrementally over time to in‑scope tenants. Enabled state Passkey (FIDO2) can be selected as the Targeted Authentication Method when Microsoft Registration Campaigns are in the Enabled state. Note: Registration Campaigns support targeting only one authentication method at a time—either Microsoft Authenticator or Passkeys (FIDO2), but not both simultaneously. [What you can do to prepare] Opting into Passkey Registration Nudges: You can opt into Passkeys and switch your users to receive a Passkey registration nudge. However, the nudge will only appear for the user if all of the following conditions are met:
Important Guidance: Microsoft Managed State:We will roll out these changes incrementally to in-scope tenants starting in early April. This rollout will take time, and even if your tenant meets the eligibility criteria, you may not see the changes immediately. Enabled State Over time, we will incrementally refine the logic for Passkeys nudges in Microsoft Registration Campaigns to guide users toward the appropriate passkey registration experience based on their passkey profile scope. Initially, the logic may not account for every edge‑case scenario, but we are actively expanding and improving it on an ongoing basis. When users have passkey profile restrictions (for example, AAGUID restrictions), the registration experience triggered by the nudge may not be optimal. Using Passkeys Despite Restrictions You can still set Passkeys as the target authentication method in Microsoft Registration Campaigns. However, users may encounter a poor or confusing experience if they have passkey profile restrictions. Example: If a user is scoped into specific AAGUID synced passkeys only, they may see a Passkey nudge at sign‑in. If they attempt to register a device‑bound passkey, the registration will fail because they are not in scope for that passkey type. Recommended next steps
| ||||||||||
| Microsoft Copilot Studio – Read only Analytics Viewer roleCategory:Microsoft Copilot (Power Platform)Nummer:MC1255508Status:stayInformed | We are announcing the ability to assign the Analytics Viewer sharing role to an agent, allowing agent owners to share an agent with a user as an analyst, granting limited read-only access to the analytics page in Microsoft Copilot Studio. This feature will reach general availability on April 21, 2026. How does this affect me? This feature introduces a new Analytics Viewer sharing role checkbox option into the Share agent form. When the role is assigned, the system creates a new Dataverse Agent Viewer role and adds the user to the existing agent’s access team, providing scoped read permissions on the relevant agent component. The sharing form enforces role hierarchy automatically. In addition, users assigned the Analyst Viewer sharing role land directly on the Analytics page and can only view Analytics pages in the navigation. All other pages, including Knowledge sources, Topics, Tools, Publish, Settings, and sharing options and test pane, are removed or disabled. What action do I need to take? This message is for awareness, and no action is required. | ||||||||||
| (Updated) Microsoft Teams: New experience when users minimize the meeting windowCategory:Microsoft TeamsNummer:MC1266027Status:stayInformed | Updated April 14, 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:]
[How this affects your organization:] Who is affected:
What will happen:
[What you can do to prepare:]
[Compliance considerations:] No compliance considerations identified, review as appropriate for your organization. | ||||||||||
| (Updated) Outlook for Android: Unified user interface in text, image and zip previewersCategory:Exchange OnlineNummer:MC1267871Status:stayInformed | [Introduction] To provide a more consistent and predictable file viewing experience, we’re updating the user interface for text, image and zip file previewers in Outlook for Android. These changes align text, image and zip previewers with the existing preview experience for Word, Excel, and PowerPoint files. [When this will happen:]
[How this affects your organization:] Who is affected:
What will happen:
[What you can do to prepare:]
[Compliance considerations:] No compliance considerations identified, review as appropriate for your organization. | ||||||||||
| (Updated) Engage events: Broadcast, meetings, and async events with new and improved event engagement featuresCategory:Microsoft VivaNummer:MC1276513Status:stayInformed | Updated April 14, 2026: We have updated the content. Thank you for your patience. [Introduction] We’re enhancing the events experience in Engage to provide a more comprehensive and interactive platform for enterprise events across web and mobile. Engage events will support broadcasts connected to Teams Town halls for one-to-many style events, Meetings for more collaborative sessions powered by Teams webinar, and async events that are best for in-person or text-only discussions like ask-me-anything (AMA). A new events landing page will unify the engagement before, during, and after events. Rollout begins late April 2026 and will be enabled by default for all Engage customers. As a user, you can now create events on your storyline and as a community admin, you can create events within a community you are an admin of. Across both storyline and community you can create three event types:
The new event landing page delivers new engagements features, which are fully customizable by the event organizer across all event types. These include moderated posts that require organizer approval, anonymous posting capabilities, and private replies. Engagement across the event page remains in sync before, during, and after the event across both Engage and Teams. Further, the organizing team has advanced insights and simple update recording flow. Screenshot: Broadcast user interface: This message is associated with Roadmap ID 537280. [When this will happen:] General Availability (Worldwide): Rollout will begin in late April 2026 and is expected to complete by early May 2026. [How this affects your organization:]
[What you can do to prepare:]
[Compliance considerations:] No compliance considerations identified; review as appropriate for your organization. | ||||||||||
| Microsoft Entra: Passkeys in registration campaigns updateCategory:Microsoft EntraNummer:MC1279092Status:stayInformed | [Introduction] We are making an update to Passkeys (FIDO2) support within Microsoft Entra Authentication Methods Registration Campaigns. Based on ongoing improvements to passkey registration nudge logic and user experience behavior, Passkeys (FIDO2) will no longer move forward to General Availability as the targeted authentication method for Registration Campaigns in the Enabled state as previously communicated in MC1253746. Instead, we are continuing to refine the eligibility logic that determines when users receive passkey registration nudges during sign-in. In the interim, Passkey (FIDO2) will move forward as the targeted authentication method for Registration Campaigns in the Microsoft Managed state for tenants that meet our in-scope criteria. [When this will happen]
[How this affects your organization] Who is affected
What will happen Enabled state
Microsoft‑managed state
Tenants are impacted when all of the following conditions are met:
Only users who are enabled for both synced and device‑bound passkeys, with no passkey profile restrictions configured (for example, attestation enforcement or AAGUID restrictions), will receive a passkey registration nudge during sign‑in. For impacted tenants, the following Registration Campaign settings will be automatically updated:
After these changes take effect, targeted users will begin receiving passkey registration nudges during sign‑in after completing multifactor authentication. Rollout will occur incrementally across eligible Microsoft Entra tenants. [What you can do to prepare] No action is required at this time. If you plan to enable passkey registration nudges in the future:
[Compliance considerations]
| ||||||||||
| Microsoft Defender for Office 365: Enhancing how we handle promotional mailCategory:Microsoft Defender XDRNummer:MC1279093Status:planForChange | [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]
[How this affects your organization] Who is affected
What will happen
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: Figure four – User inbox rules using the promotions” tag: [What you can do to prepare]
[Compliance considerations]
| ||||||||||
| The April 2026 Windows security update is now availableCategory:WindowsNummer:MC1279829Status:stayInformed | 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:
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:
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. | ||||||||||
| Second deployment phase for Kerberos RC4 hardening begins with the April 2026 Windows security updateCategory:WindowsNummer:MC1279830Status:stayInformed | 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:
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:
| ||||||||||
| Remote Desktop adds new safeguards for connections opened from RDP filesCategory:WindowsNummer:MC1279831Status:planForChange | 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 | ||||||||||
| Notice: The April 2026 Scan Cab for Microsoft updates is delayedCategory:WindowsNummer:MC1279832Status:stayInformed | 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:
|
