| Roadmap information for Microsoft Copilot Studio and agents transitioning to the Microsoft 365 RoadmapCategory:Microsoft Copilot (Microsoft 365)Nummer:MC1413298Status:stayInformed | [What and Why:]
Starting July 2, 2026, roadmap updates for Microsoft Copilot Studio and associated agent experiences will be published to the Microsoft 365 Roadmap, giving you a single, consistent place to track upcoming features. Release Planner will no longer be maintained as a source for this roadmap information. This change makes it easier to stay informed and plan for what’s coming—all from one location. This transition also aligns roadmap information with experiences that are easier for AI-powered tools and agents to discover and consume. By consolidating roadmap content within the Microsoft 365 Roadmap, customers benefit from a more consistent and accessible source of information for both human users and AI-assisted workflows. [Rollout Schedule:]
General Availability (Worldwide): We will begin rolling out in early July 2026 and expect to complete by early July 2026.
[Impact on Your Organization:]
Who is affected:
- Admins and users who rely on Release Planner for roadmap visibility into Microsoft Copilot Studio and associated agent experiences
Platforms/Services:
- Microsoft 365 Roadmap (web)
- Microsoft Copilot Studio
- Sales Agent, Finance Agent, Service Agent
What will happen:
- Roadmap content for Microsoft Copilot Studio and associated agent experiences will move from Release Planner to the Microsoft 365 Roadmap.
- All future roadmap updates will be published in the Microsoft 365 public roadmap
- Existing Release Planner links and entry points will automatically redirect to the new location
- Some Release Planner-specific planning capabilities, such as custom release plans, will no longer be available after this transition. The Microsoft 365 Roadmap continues to evolve, providing a more consistent, actionable way to track changes alongside clearer Message Center communications and release timing.
- Customers who previously relied on Release Planner for customized tracking can use Microsoft 365 public roadmap capabilities together with insights powered by MCP (Model Context Protocol) for deeper tracking and analysis. These experiences support more proactive planning with greater clarity and confidence by reducing manual tracking and surfacing more relevant, role-aware insights.
[Action Required / Recommendations:]
No immediate action is required. We recommend the following to ensure a smooth transition: - Update any saved bookmarks to point to the Microsoft 365 Roadmap
- Begin using the Microsoft 365 Roadmap as your primary source for roadmap visibility
- Communicate this update to relevant stakeholders who rely on Release Planner
- Review and update any internal documentation that references Release Planner
Resources: We will continue to share updates through Message Center as needed. [Compliance Considerations:]
No compliance considerations identified, review as appropriate for your organization. |
| Custom templates in Microsoft PlannerCategory:PlannerNummer:MC1413299Status:stayInformed | [What and Why:]
Microsoft is introducing Custom templates in Microsoft Planner, allowing users to convert existing plans into reusable templates that can be shared across Microsoft 365 groups. This capability helps organizations standardize recurring work, reduce setup effort, improve consistency, and accelerate project creation. This message is associated with Microsoft 365 Roadmap ID 512431.
[Rollout Schedule:]
- General Availability (Worldwide): Beginning in early July 2026; expected to complete by late July 2026
[Impact on Your Organization:]
Who is affected:
- Users with Microsoft Planner access
- Members of Microsoft 365 Groups with Planner plans
- Teams using recurring project workflows
Platforms/Services:
- Microsoft Planner
- Microsoft 365 Groups
What will happen:
- Users can publish existing plans as templates using Share > Publish as template.
- Templates can include tasks, buckets, labels, goals, notes, checklists, and attachment links.
- Users can create new plans from Shared and Created by me template galleries.
- Templates are shared at the Microsoft 365 Group level.
- New plans created from templates reset task progress and status.
- Changes to templates do not update previously created plans.
- Any Microsoft 365 Group member can delete a shared template.
- The feature is enabled by default.
- No new admin configuration is required.
- Existing Planner and Microsoft 365 Group permissions continue to apply.
[Action Required/Recommendations:] No administrative action is required. Recommended actions: - Review internal Planner training materials and documentation to include template functionality.
- Notify Planner users and project teams about the new capability.
- Review Microsoft 365 Group governance policies, as group membership determines template visibility and usage.
- Educate users that:
- Templates are shared assets within the Microsoft 365 Group.
- Any group member can delete a template.
- Plans created from templates do not inherit future template updates.
- Consider establishing naming and lifecycle standards for templates used across departments.
Learn more: [Compliance Considerations:]
| Compliance Consideration |
Explanation |
| Does the change alter how existing customer data is processed, stored, or accessed? |
Planner plan content (tasks, buckets, labels, goals, notes, checklists, and attachment links) can be reused through templates, providing a new way to access and replicate existing plan data. |
| Does the change provide a new way of communicating between users, tenants, or subscriptions? |
Templates are shared and discoverable by Microsoft 365 group members, improving collaboration, but they do not introduce a new communication channel. |
| Does the change alter how admins can monitor, report on, or demonstrate compliance activities? |
Shared templates may become additional Planner artifacts that organizations may choose to include in governance, retention, and compliance reviews. |
| Does the change modify how users can access, export, delete, or correct their personal data within Microsoft 365 services? |
Users can create, reuse, and delete shared templates within Microsoft 365 groups, potentially affecting how Planner content is reused and managed. |
|
| New in Catalog Management: Create custom group of sitesCategory:Microsoft 365 suite
SharePoint Online
Microsoft OneDriveNummer:MC1413301Status:stayInformed | [What and Why:]
Microsoft is expanding Catalog Management in SharePoint Advanced Management to help organizations classify and organize SharePoint sites by department, team, business unit, or other custom taxonomies. This release introduces new ways to create and manage catalog categories using CSV uploads, SharePoint site properties, and Microsoft Entra ID extension attributes. These capabilities improve governance, content discovery, reporting, and future administration scenarios.
[Rollout Schedule:]
- General Availability (Worldwide): Began in June 2026; expected to complete by mid-July 2026
[Impact on Your Organization:]
Who is affected:
- SharePoint administrators
- Microsoft 365 administrators
- Organizations using SharePoint Advanced Management
- Governance and information architecture teams
Platforms/Services:
- SharePoint Online
- SharePoint Advanced Management
- Microsoft 365 Admin Center (future integrations)
- SharePoint Admin Center
- Microsoft Entra ID
What will happen:
- Administrators can bulk-create catalog categories from CSV uploads.
- Administrators can organize sites using SharePoint site bag properties.
- Category visibility can be targeted using Microsoft Entra ID extension attributes.
- Organizations can create department, team, or business-based site taxonomies.
- Future integrations that will use Catalog groups include:
- Allowing organizations to define governance boundaries and include them in various SharePoint Advanced Management features
- Pay-as-you-go storage management capabilities that will use Catalog groupings for departmental billing scenarios.
- No user workflow changes are introduced by this release.
- No migration activities are required.
[Action Required/Recommendations:]
No action is required.
Recommended preparation activities:
- Review your current SharePoint information architecture and determine whether departmental or organizational taxonomies would provide governance benefits.
- Identify existing SharePoint site properties that could be used for categorization.
- Review available Microsoft Entra ID extension attributes that may support category visibility targeting.
- Communicate upcoming capabilities to SharePoint governance and administration teams.
Learn more: Catalog management in SharePoint Advanced Management – SharePoint in Microsoft 365 | Microsoft Learn [Compliance Considerations:]
| Area |
Explanation |
| Administrative reporting and governance |
Catalog categories provide new ways to organize sites and support governance-related reporting and management activities. |
| Admin controls and Entra targeting |
Administrators can manage Catalog categories and use Microsoft Entra ID extension attributes to scope visibility. |
|
| Discussion post previews coming to Viva EngageCategory:Microsoft VivaNummer:MC1413302Status:planForChange | [What and Why]
Microsoft is introducing discussion post previews in Viva Engage to help users validate their content before publishing. Users can review formatting, layout, and presentation before posting, helping improve communication quality and confidence when creating organizational communications. This message is associated with Roadmap ID 566699.
[Rollout Schedule]
General Availability (Worldwide): Rollout begins in late July 2026; expected to complete by late August 2026.
[Impact on Your Organization]
Who is affected:
- All Viva Engage users who create discussion posts.
- Corporate communicators, leadership delegates, community managers, and users publishing broad communications.
Platforms/Services:
- Viva Engage (web and Teams).
- Microsoft Viva.
What will happen:
- Users will see a preview option when creating discussion posts.
- Users can review how posts will appear before publishing.
- Users can validate content presentation and readability.
- The feature is available by default when released.
- No admin configuration is required.
- Existing permissions and controls remain unchanged.
[Action Required/Recommendations]
No administrative action is required. We recommend that you:
- Inform users about the new discussion post preview capability.
- Communicate the update to communications teams and leadership delegates.
- Update training materials and internal documentation if applicable.
- Prepare help desk staff for potential user questions.
[Compliance Considerations]
No compliance considerations identified, review as appropriate for your organization. |
| Viva Engage: New Recent feed in HomeCategory:Microsoft VivaNummer:MC1413304Status:stayInformed | [What and Why:]
Microsoft is introducing a new Recent feed in Viva Engage Home, giving users a chronological view of content from followed communities, followed people, and priority communications. This enhancement complements the existing For you feed, which continues to provide personalized content recommendations.
This update improves personal productivity by providing users with a more predictable way to stay current with the content and communications most relevant to them, while preserving the discovery experience offered through personalized recommendations. This message is associated with Microsoft 365 Roadmap ID 559482.
[Rollout Schedule:]
- General Availability (Worldwide): Beginning in late July 2026; expected to complete by mid-August 2026
[Impact on Your Organization:]
Who is affected:
- All Viva Engage users accessing the Home experience.
- Communications teams publishing organizational communications.
- Community managers and leaders who rely on user engagement with community content.
Platforms/Services:
- Viva Engage (Web)
- Viva Engage (Mobile)
- Viva Engage app in Teams (all clients)
What will happen:
- A new Recent feed option will appear in Home. The default For you feed remains unchanged.
- Users can switch between For you and Recent views.
- The Recent feed displays content in a more chronological and predictable order.
- Content surfaced in Recent includes:
- Posts from followed communities.
- Content from followed people.
- Priority communications.
- The existing For you personalized feed remains available.
- User feed preferences are preserved across web and mobile clients.
- The option to use the feature is enabled by default as part of the service update.
- No tenant configuration changes are required.
[Action Required / Recommendations:]
No admin action is required. We recommend that you:
- Review internal Viva Engage adoption materials.
- Inform communications teams about the new feed experience.
- Notify community managers and leaders of the update.
- Prepare help desk teams for user questions.
- Update user documentation where appropriate.
- Monitor feedback after rollout.
[Compliance Considerations:]
No compliance considerations identified, review as appropriate for your organization. |
| Microsoft Purview | Data Lifecycle Management: Insights for Copilot and AI app interactionsCategory:Microsoft Copilot (Microsoft 365)
Microsoft PurviewNummer:MC1413308Status:stayInformed | [What and Why] Microsoft Purview Data Lifecycle Management is introducing new insights to help administrators better understand how Copilot and AI apps are used across their organization. These insights provide actionable recommendations to strengthen retention policies and improve your data security posture. This update supports enterprise-ready AI by helping organizations govern AI interactions with greater visibility and control. This message is associated with Microsoft 365 Roadmap ID 561209. [Rollout Schedule] - Public Preview: Beginning late July 2026 and expected to complete mid-August 2026
- General Availability (Worldwide): Beginning mid-August 2026 and expected to complete late August 2026
[Impact on Your Organization:] Who is affected - Admins managing Microsoft Purview Data Lifecycle Management and Data Security Posture Management
Platforms/Services - Microsoft Purview (web)
- Copilot
- AI apps
What will happen - Admins will gain visibility into Copilot and AI app interactions within the organization.
- Recommendations will help guide retention policy configuration.
- Recommendations will be accessible within the Data Security Posture Management experience in Microsoft Purview.
- Public Preview is opt-in at the tenant level. After enrollment, the feature is enabled by default within the preview environment.
- No changes are made to existing retention policies unless admins take action.
[Action Required/Recommendations] No immediate action is required. Admins can prepare by: - Reviewing insights in the Data Security Posture Management page in Microsoft Purview once available
- Evaluating recommended retention policy updates for Copilot and AI app interactions
- Updating internal governance documentation if needed
- Informing compliance and security stakeholders of new visibility capabilities
[Compliance considerations:] | Question | Answer | | Does the change alter how existing customer data is processed, stored, or accessed (such as documents, emails, chats, etc.), if so how and to what extent? | Yes. The feature analyzes existing Copilot and AI app interaction data to provide insights. | | Does the change introduce or significantly modify AI or machine learning capabilities? | Yes. AI-driven insights evaluate Copilot and AI app interactions. | | Does the change alter how admins can monitor, report on, or demonstrate compliance activities, for example in Microsoft Purview or admin reporting, if so summarize the changes? | Yes. New visibility is available through Data Security Posture Management insights. | | Does the change include an admin control and can it be controlled through Entra ID group membership? | Yes. Admins can take actions and configure policies within Microsoft Purview. |
|
| Microsoft Purview enforcing one capturing group limit for custom sensitive information typesCategory:Microsoft 365 suite
Microsoft PurviewNummer:MC1413309Status:planForChange | [What and Why] Microsoft Purview is enforcing the documented limit of one capturing group per regular expression in custom Sensitive Information Type (SIT) definitions. This change improves consistency, reliability, and predictability in pattern matching for data classification and Data Loss Prevention scenarios. This enforcement applies when custom SITs are created or updated and may block those operations if the limit is exceeded. [Rollout Schedule] General Availability (Worldwide, GCC, GCC High, and DoD): The rollout is expected to complete by early July 2026. [Impact on Your Organization] Who is affected - Admins who create or manage custom SITs in Microsoft Purview
Platforms and services - Microsoft Purview portal
- PowerShell cmdlets (New-DlpSensitiveInformationTypeRulePackage and Set-DlpSensitiveInformationTypeRulePackage)
What will happen - New custom SITs that include more than one capturing group in a regular expression will be blocked during creation.
- Updates to existing SITs will fail validation if the regular expression contains more than one capturing group.
- When editing or re-saving SITs that contain more than one capturing group, admins must update regular expression patterns to include only one capturing group before changes can be saved.
- This enforcement applies across both portal and PowerShell experiences.
- Existing SITs with multiple capturing groups will stop functioning.
[Action Required or Recommendations] Action required. - Review all custom SITs that use regular expressions to identify any with multiple capturing groups. After rollout, updates to these SITs will fail validation until corrected, which may delay policy updates.
- Update regular expression patterns to comply with the one capturing group limit.
- Test updated SITs to ensure they continue to match the intended content before applying them to production policies.
- Review service limits documentation to confirm compliance requirements.
Learn more (and for the full list of SIT limits): Sensitive information type limits | Microsoft Purview | Microsoft Learn [Compliance Considerations] This change enforces existing limits for SITs and may affect how Data Loss Prevention policies behave when custom SITs are modified. Review as appropriate for your organization. |
