| (Updated) Smart Calendar available in Classic Outlook for Microsoft 365 Copilot usersCategory:Microsoft Copilot (Microsoft 365)Nummer:MC1181279Status:stayInformed | Updated February 6, 2026: We have updated the timeline. Thank you for your patience. [Introduction]
Note: You’re receiving this message because you are part of our early access program. Smart Calendar is the next-generation calendar experience that will be built into Classic Outlook for Microsoft 365 Copilot-licensed users. It combines the familiar Outlook interface with Copilot-powered intelligence and a modern, responsive design, making time management simpler, smarter, and more intuitive. This calendar will be available for users inside Classic Outlook. Once Smart Calendar is released, users will get an information banner in Outlook Calendar to Try the new app. This update introduces several key benefits:
- Copilot Intelligence: Prepare, schedule, coordinate, and recap meetings with Copilot assistance.
- Effortless Scheduling: Create meetings using natural language, get smart room suggestions, and receive RSVP recommendations.
- Seamless Coordination: Automatically adjust meetings and rebook rooms when conflicts arise.
- Follow Through: Get concise recaps, transcripts, and actionable follow-ups, even for meetings you missed.
- No Learning Curve: Built directly into Classic Outlook, no separate install required. Smart Calendar coexists alongside the classic calendar.
Smart Calendar helps unlock advanced time management capabilities and realize the full value of your Microsoft 365 Copilot investment. It offers effortless activation and minimal change management for IT teams, operating within Microsoft 365’s existing security, compliance, and data protection boundaries. [When this will happen:]
- Public Preview: Rollout begins in early November 2025 and completes by late January 2026
- General Availability: Rollout begins in mid-March 2026 and is expected to complete by end of May 2026
[How this affects your organization:]
- Who is affected:
- Users with Microsoft 365 Copilot licenses using Classic Outlook (Win32).
- A Microsoft 365 Copilot license is required to use this feature.
- Some of the features are in early stages of release and may reach you later.
- What will happen:
- Users will see a banner in Outlook Calendar inviting them to Try the new app.
- Smart Calendar will be available alongside the classic calendar—no replacement or removal.
- Copilot features will assist with scheduling, coordination, and follow-ups.
- No separate installation is required; Smart Calendar is built into Classic Outlook.
- Existing admin policies and calendar settings remain unchanged.
Note: You may notice that in some cases the UI currently shows Copilot Calendar instead of Smart Calendar. This is expected during the early rollout phase. The name change to Smart Calendar has already been released and is gradually rolling out to all tenants. Once the update reaches your environment, the UI will reflect the new name. No action is required on your part.
[What you can do to prepare:]
- Communicate the upcoming changes and benefits to users with Copilot licenses.
- Ensure eligible users have Microsoft 365 Copilot licenses to access Smart Calendar.
- Encourage users to share feedback for continuous improvement.
- Update internal documentation if you detail calendar features or workflows.
[Compliance considerations:]
| Compliance Area | Explanation |
|---|
| AI/ML capabilities interacting with customer data | Smart Calendar introduces Copilot-powered intelligence that processes meeting data to provide scheduling assistance, recaps, and follow-ups. |
| New way of interacting with generative AI | Users can interact with Copilot via Smart Calendar to schedule meetings using natural language and receive intelligent suggestions. |
| Admin control available | Admins can manage Copilot licensing and access through Microsoft 365 admin center and Entra ID group membership. |
| User control available | Users can choose to use Smart Calendar or continue with the classic calendar interface. |
|
| (Updated) Introducing Surveys Agent and Copilot Chat in Microsoft FormsCategory:Microsoft Copilot (Microsoft 365)Nummer:MC1229954Status:stayInformed | Updated May 4, 2026: We have updated the timeline. Thank you for your patience. [Introduction]
Microsoft is introducing Microsoft 365 Copilot Chat within Microsoft Forms, along with a new Forms Agent integration tailored to help creators design, distribute, and analyze forms more effectively. This update streamlines form creation and insights by providing AI-driven suggestions, improvements, and analysis. This message is associated with Roadmap ID 553136.
[When this will happen:] - General Availability (Worldwide): We’ll begin rollout mid-May 2026 (previously early May) and expect to complete by late May 2026 (previously late March).
[How this affects your organization:]
Who is affected: Users with an active Microsoft 365 Copilot license who create or edit forms in Microsoft Forms on the web.
What will happen:
- Users will find a new Copilot icon in Microsoft Forms.
- Forms Agent and Copilot Chat will be available directly in the form-editing experience.
- Users can perform tasks such as:
- Getting AI‑generated suggestions to refine or improve their form or quiz.
Screenshot 1: Select the Copilot button to chat, get suggestions, and effortlessly improve your form 
- Adjusting question clarity and form structure with support from Forms Agent.
- Drafting invitation messages.
- Analyzing survey or quiz results with AI assistance.
Screenshot 2: Unlock quick, actionable insights from your data, and chat to dive deeper 
- This feature will be on by default for Copilot licensed users and can be disabled by admins.
- Existing Copilot policies apply; no new admin controls are required.
[What you can do to prepare:]
No action is required.
Recommended:
- Inform helpdesk staff about new AI capabilities.
- Update internal documentation as needed.
- Review Copilot licensing and policy settings.
Learn more:
[Compliance considerations:]
No compliance considerations identified, review as appropriate for your organization.
|
| (Updated) Viva Engage digest updates: Improvements to weeklyCategory:Microsoft VivaNummer:MC1269207Status:planForChange | Updated May 4, 2026: We have updated the timeline. Thank you for your patience. [Introduction]
We’re improving the overall digests email experience in Viva Engage to reduce email noise and surface more relevant content for users to stay informed. We’re enhancing the weekly digest email to include new, subscribed catch-up content and while no longer sending the daily digest on the same day.
[When this will happen:]
- Some users may begin to see these changes starting early April 2026
- General Availability (Worldwide): Rollout begins in early May 2026 and completes by late May 2026 (previously mid-May).
[How this affects your organization:]
Who is affected:
- Users subscribed to both the daily and weekly Viva Engage digest emails
What will happen:
- Users will no longer receive both daily and weekly digests on the same day.
- On the day the weekly digest is sent, the daily digest will be skipped.
- The weekly digest will now include catch-up (subscribed) content, in addition to discovery content.
- This change respects existing user subscription preferences.
- No changes are made to admin policies or tenant configurations.
[What you can do to prepare:]
- No admin action is required.
- Consider notifying users or helpdesk staff about this change to set expectations.
- Update any internal documentation that describes Viva Engage digest behavior, if applicable.
[Compliance considerations:] | Compliance question | Explanation | | Does the change provide a new way of communicating between users? | Weekly digest emails now include both discovery and catch-up content, changing how existing communications are surfaced to users. | | Does the change allow a user to enable or disable the feature themselves? | Users continue to manage their daily and weekly digest subscriptions through existing Viva Engage notification settings. |
|
| (Updated) Microsoft Defender for Office 365: Enhancing how we handle promotional mailCategory:Microsoft Defender XDRNummer:MC1279093Status:planForChange | Updated May 4, 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 [email protected] 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): We will begin rolling out in early July 2026 and expect to complete by late July 2026.
- General Availability (DoD, GCC, GCC High): We will begin rolling out in early July 2026 and expect to complete by mid-August 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.
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 [email protected] 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. A link will be added to this post when it becomes available.
[Compliance considerations] | Question | Answer | | 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. |
|
| (Updated) Microsoft 365 Apps: Cloud Update adds update health reportingCategory:Microsoft 365 suiteNummer:MC1289720Status:stayInformed | Updated May 4, 2026: We have updated the timeline. Thank you for your patience. [Introduction] Update health builds on existing Cloud Update insights by adding clearer, more actionable diagnostics when an update does not complete successfully. Administrators see descriptive, easy‑to‑understand error messaging aligned with error codes, along with aggregated issue views across Cloud Update‑managed devices. This message is associated with Microsoft 365 Roadmap ID 558249. [When this will happen] - Public Preview: Rollout beginning in April 2026 and is expected to complete by mid-May 2026.
- General Availability (Worldwide): Rollout will begin in mid-May 2026 (previously late May) and is expected to complete by late-May 2026.
[How this affects your organization] Who is affected - Microsoft 365 administrators managing Microsoft 365 Apps updates using Cloud Update
- Tenants with Cloud Update enabled in the Microsoft 365 Apps admin center
What will happen - Admins will see aggregated views of update issues across Cloud Update–managed devices:
- Update failures will surface descriptive error messages aligned with error codes:
Admins can drill into affected devices, review detailed issue information, and export device lists:
- Linked guidance is available to support troubleshooting and resolution.
- The feature is enabled by default for eligible tenants.
- There is no impact to users.
- No changes are made to existing update policies.
[What you can do to prepare] [Compliance considerations] | Question | Answer | | Does the change alter how admins can monitor, report on, or demonstrate compliance activities (for example, admin reporting)? | Yes. Update health introduces new admin-facing reporting and diagnostic views that allow administrators to monitor Microsoft 365 Apps update issues and device update status across Cloud Update–managed devices. |
|
| (Updated) Microsoft Teams: Enhanced cross-platform join via Session Initiation Protocol (SIP) for Teams Rooms on AndroidCategory:Microsoft TeamsNummer:MC1294522Status:planForChange | Updated May 4, 2026: We have updated the timeline. Thank you for your patience. [Introduction]
Microsoft Teams Rooms on Android will soon be able to join third-party meetings using Session Initiation Protocol (SIP). This capability enables seamless cross-platform interoperability, allowing users to connect to external meeting services directly from Teams Rooms on Android devices while maintaining a consistent and reliable meeting experience across diverse meeting platforms.
This message is associated with Microsoft 365 Roadmap ID 558539.
[When this will happen:]
- General Availability (Worldwide): We will begin rolling out in early June 2026 and expect to complete by mid-August 2026 (previously early June).
[How this affects your organization:]
Who is affected:
- Organizations with Microsoft Teams Rooms on Android devices
- Organizations that host or join third-party meetings from shared meeting spaces
- Admins managing Teams Rooms on Android devices licensed with Teams Rooms Pro
What will happen:
- Users will be able to join supported third-party meetings (for example, Zoom or Webex) directly from Teams Rooms on Android devices when the meeting invitation includes a Session Initiation Protocol (SIP) video meeting address.
- This feature is off by default. Availability of this capability depends on Teams Rooms Pro licensing and appropriate device configuration.
[What you can do to prepare:]
- Test the feature with your lower-ring Teams Rooms on Android devices.
- Prepare educational material for users in advance of release.
- Identify users who frequently collaborate with external organizations using third-party meeting platforms and communicate upcoming capabilities.
- Ensure that all Teams Rooms on Android devices that require this functionality are licensed with Teams Rooms Pro.
- Update internal documentation for meeting room usage if applicable.
- Communicate this change to your helpdesk and support teams.
Learn more: SIP and H.323 Dialing with Teams Rooms | Microsoft Learn (will be updated before rollout)
[Compliance considerations:] No compliance considerations identified, review as appropriate for your organization. |
| (Updated) Microsoft 365 Copilot will use private community and event content as grounding sourcesCategory:Microsoft Viva
Microsoft Copilot (Microsoft 365)Nummer:MC1296480Status:stayInformed | Updated May 4, 2026: We have updated the timeline. Thank you for your patience. [Introduction] Microsoft 365 Copilot will begin using content from private communities and private events as grounding sources to generate responses. This change helps Copilot provide more relevant and context-aware answers by incorporating content that users already have access to, while continuing to respect existing permissions and security controls. This message is associated with Microsoft 365 Roadmap ID 515144. [When this will happen] General Availability (Worldwide): We will begin rolling out this feature in late May 2026 and expect to complete the rollout by late June 2026. [How this affects your organization] Who is affected: All Microsoft 365 tenants using Microsoft 365 Copilot What will happen - Microsoft 365 Copilot may reference content from private communities and private events when generating responses.
- Users will only see content they already have permission to access:
 - Sensitivity labels applied to the source content will be displayed alongside Copilot citations, when applicable.
- The feature is enabled by default and cannot be turned off.
[What you can do to prepare] No action is required. You may want to inform administrators, compliance teams, or helpdesk staff that Copilot can now reference private community and event content while continuing to honor existing permissions and sensitivity labels. [Compliance considerations] | Question | Answer | | Does the change alter how existing customer data is processed, stored, or accessed? | Yes. Existing private community and event content may now be accessed by Microsoft 365 Copilot as a grounding source, while respecting current permissions. | | Does the change introduce or significantly modify AI/ML capabilities that interact with customer data? | Yes. Microsoft 365 Copilot expands its grounding sources to include private community and private event content. | | Does the change provide end users a new way of interacting with generative AI? | Yes. Copilot responses may now include insights derived from private community and event content the user can already access. | | Does the change modify or interact with Information Protection labels? | Yes. Sensitivity labels applied to the source content are displayed alongside Copilot citations. |
|
| Power Pages – Use Dynamics 365 websites with Bootstrap 5 and enhanced data modelCategory:Power PlatformNummer:MC1300450Status:stayInformed | We are announcing the ability to use Dynamics 365 websites with Bootstrap 5 and enhanced data model in Power Pages. This feature will reach general availability on May 15, 2026.
How does this affect me?
New sites created using Customer Self-Service, Employee Self-Service, Partner, and Community templates will support the enhanced data model and Bootstrap 5. Users will experience faster site provisioning, improved application lifecycle management with solution awareness, and improved site usability.
What action do I need to take?
To enable this feature, users must take the following steps:
- Go to the Environment tab in the Manage section of the Power Platform admin center.
- Turn on the Switch to enhanced data model toggle.
If you would like more information on this feature, please visit Enhanced data model. |
| Microsoft Entra: App Instance Lock enabled by default for new applicationsCategory:Microsoft EntraNummer:MC1300584Status:planForChange | [Introduction] To improve application security, Microsoft Entra ID will enable App Instance Lock by default for newly created applications. This change prevents sensitive application properties from being modified outside the application’s home tenant, reducing the risk of unauthorized changes that can lead to application compromise. Based on our data analysis, we do not expect this change to cause customer impact. App owners or administrators in the application home tenant can still disable App Instance Lock for specific applications if their scenario requires updates to protected properties in other tenants.
[When this will happen] General Availability (Worldwide): We will begin rolling out in early June 2026 and expect to complete by late June 2026.
[How this affects your organization] Who is affected - Microsoft Entra administrators
- Developers who manage Microsoft Entra applications
- Organizations using automation or scripts to update application credentials or security settings after app creation
What will happen? - App Instance Lock will be enabled by default for all newly created applications.
- Sensitive service principal properties will be protected by default.
- Attempts to modify these protected properties will be blocked unless App Instance Lock is explicitly disabled.
- Blocked update attempts will return a 400 Bad Request error, and the update will not be applied.
- Existing applications are not affected by this change.
Example Microsoft Graph error returned when attempting to update passwordCredentials on a locked application: 
[What you can do to prepare] - Review automation, scripts, or provisioning workflows that modify service principal credentials or related settings.
- Validate that existing workflows do not depend on App Instance Lock being disabled and update them to avoid modifying protected properties unless the lock is intentionally disabled.
- Disable App Instance Lock for specific applications if post‑creation updates are required.
- Test application provisioning and credential management flows prior to rollout in mid-May.
Learn more: How to configure app instance property lock in your applications | Microsoft identity platform | Microsoft Entra | Microsoft Learn [Compliance considerations] | Question | Answer | | Does the change include an admin control? | Yes. Admins can disable App Instance Lock per application when required. |
|
| Microsoft Copilot Studio – Information about the creation of classic style agentsCategory:Microsoft Copilot (Power Platform)Nummer:MC1300773Status:stayInformed | We are announcing that we have enabled Microsoft 365 enterprise license customers to create classic style agents using the Microsoft Copilot Studio web app.
How does this affect me?
Users with the Power Virtual Agents for Office 365 app license enabled can now also use Microsoft Copilot Studio (https://copilotstudio.microsoft.com) to create and manage classic style agents. Previously, these agents could only be made in the Microsoft Copilot Studio app within Microsoft Teams.
Please note that, after June 30, 2026, classic style agent creation in the Microsoft Copilot Studio app within Microsoft Teams will no longer be supported. Users will be provided with a link in the Microsoft Teams app to the Microsoft Copilot Studio web experience.
There are no changes to compliance, security, or data handling as part of this update. Existing policies and controls will continue to apply in Microsoft Copilot Studio.- Agents are still created in Dataverse for Teams environments with access permissions managed by Microsoft Teams.
- Agents created with this user license will still not run with any generative AI.
What action do I need to take?
This message is for awareness, and no immediate action is required. However; we encourage you to take the following actions:- Transition your users to Microsoft Copilot Studio for classic style agent creation prior to June 30, 2026.
- Review and update any of your internal documentation and training materials to reflect the updated agent authoring location.
- Validate any processes or governance policies you have in place that reference the Microsoft Teams app for creating classic style agents.
|
