Microsoft Roadmap, messagecenter and blogs updates from 03-05-2026

het nieuws van Microsoft message center roadmap en blogs - KbWorks - SharePoint and Teams Specialist

03-May-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!

The blogs of this day are:

More People Are Defeated by Blisters Than MountainsFrom Linkedin
Ni har redan plattformen – varför lever telefonin kvar vid sidan av?From Linkedin
Updated M365 Copilot Notebook overview page experienceFrom Linkedin
Custom tools and rich UI for app-based conversations are now in Public Previewvan Linkedin
Creating Custom Copilot Cowork Skills That Actually Matter for SMBsFrom Linkedin
CollabTalk Podcast | Episode 186 with Kipp SorensenFrom Linkedin
Account Discovery in Microsoft Entra ID GovernanceFrom Linkedin
Trending Issues: Kerberos Failures in SharePoint and other applications starting April 2026From Linkedin
Building a Second Brain That Actually Works with Copilot Cowork as the LibrarianFrom Linkedin
Adding Custom Pages To A Model Driven App NavigationFrom Linkedin
High Volume Email is Generally Available and Ready to ChargeFrom Linkedin
Use Copilot to explain selected slide content in PowerPoint LiveFrom Linkedin
Copilot’s agentic capabilities in Word, Excel, and PowerPoint are generally availablevan Linkedin
VPN vs Zero Trust: Why Modern Organisations Are Moving OnFrom Linkedin
Page publishing with the SharePoint page agentFrom Linkedin

Items from the MessageCenter in Microsoft 365

What’s new in the Microsoft Intune service update for April 2026
Category:Microsoft Intune
Nummer:MC1297979
Status:stayInformed

Your Microsoft Intune account has been updated to the latest service build.

[How this will affect your organization:]

You will see the service release number updated in the Tenant Status blade of the Intune admin center soon. We have introduced some changes that we are excited for you to try out.

[What you need to do to prepare:]

Review the additional information below to learn more about what’s new in this service release. We will continue to update the What’s new page with any features that are released between now and the next monthly service update. Learn more by reviewing features highlighted in the latest Intune What’s new 2604 (April) blog and how the Intune service updates each month is described in the Microsoft Intune service updates blog.

[Additional Information:]

Intune What’s new

Staying up to date on Intune new features, service changes, and service health

Agent Registry API transition to Agent 365
Category:Microsoft 365 suite
Nummer:MC1297981
Status:stayInformed

[Introduction]

As previously announced in MC1275311, Microsoft is consolidating agent management to simplify how administrators observe, govern, and secure agents, with Agent 365 (A365) as the single source of truth. A new Agent 365–powered agent registration Microsoft Graph API supports this consolidation and replaces the existing agent registry Graph API. This message provides API‑specific details and required actions.

[When this will happen]

  • General Availability (Worldwide): Rollout begins in early May 2026 and is expected to complete by late May 2026.
  • API retirement: The existing agent registry Graph API will begin retirement on June 15, 2026.

[How this affects your organization]

Who is affected

  • Microsoft 365 tenants with agents self‑registered using the existing agent registry Graph API
  • Developers or administrators responsible for custom agent lifecycle management

Note: This change does not apply to agents created through Microsoft agent builder platforms such as Copilot Studio or Foundry.

What will happen

  • A new Agent 365–powered agent registration Graph API is available as of May 1, 2026.
  • The existing agent registry Graph API will no longer be supported starting June 15, 2026.
  • Agents registered only through the existing API and not re‑registered before retirement will stop functioning.
  • Administrators can view all registered agents in the All agents view in the Microsoft 365 admin center (MAC).
  • This message fulfills the API transition previously referenced in MC1275311.

[What you can do to prepare]

  • Identify agent instances registered using the existing agent registry Graph API.
  • Re‑register those agents using the new Agent 365–powered agent registration Graph API before June 15, 2026.
  • Verify agent registrations in the All agents view in MAC.
  • Update internal documentation or automation that references the existing API.
  • Communicate this change to development and platform teams responsible for agent management.

Learn more: 

[Compliance considerations]

QuestionAnswer
Does this change introduce or significantly modify AI/ML or agent capabilities that interact with customer data?Yes. This change introduces a new Agent 365–powered agent registration API that governs how agents are registered and managed within Microsoft 365. It does not change agent behavior or access to customer data.
Does this change alter how admins can monitor, report on, or demonstrate compliance?Yes. Agent inventory and lifecycle visibility are centralized in the Microsoft 365 admin center, providing a unified view aligned with Agent 365.

Use sensitivity labels to block all connected experiences that analyze content in Word, Excel, and PowerPoint
Category:Microsoft 365 suite Microsoft 365 apps
Nummer:MC1297982
Status:planForChange

[Introduction]

Microsoft is updating an existing sensitivity label setting that controls whether certain connected experiences can analyze file content. This change extends support of this label setting to additional platforms and extends coverage of the label setting to include all connected experiences that analyze content in Word, Excel, and PowerPoint, rather than a subset of these experiences.

[When this will happen]

  • Public Preview: We will begin rolling out in mid-May 2026 and expect to complete by late May 2026.
  • General Availability (Worldwide, GCC, GCC High, DoD): 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

  • Organizations using Microsoft Purview sensitivity labels in Word, Excel, and PowerPoint
  • Users opening files that have a sensitivity label configured withPrevent some connected experiences that analyze content

What will happen

  • Files with this label setting will not be sent to any Microsoft connected experiences for content analysis.
  • Previously, this label setting blocked only a subset of connected experiences; enforcement is now expanded in Word, Excel, and PowerPoint.
  • This change applies automatically to existing labels configured with this setting.
  • There is no change to label configuration, and the behavior is enforced by default once the feature rolls out.

[What you can do to prepare]

No action is required if your organization already uses sensitivity labels.

Optional recommended steps:

  • Review sensitivity labels that use the Prevent some connected experiences that analyze content” setting to confirm they align with your organization’s data handling expectations.
  • Inform compliance and helpdesk teams that labeled files may no longer interact with connected experiences that analyze content in Word, Excel, and PowerPoint.
  • Update internal documentation if you describe how sensitivity labels affect Office app functionality.

[Compliance considerations]

QuestionAnswer
Does the change alter how existing customer data is processed, stored, or accessed?Yes. Files with applicable sensitivity labels are now fully blocked from being sent to Microsoft connected experiences for analysis, expanding enforcement beyond a subset of experiences.
Does the change modify Information Protection labels or their enforcement?Yes. Existing sensitivity label settings now enforce broader blocking behavior across all connected experiences that analyze content.
Does the change introduce or modify AI/ML capabilities that interact with customer data?Yes. The change restricts how labeled content can be analyzed by Microsoft connected experiences, including AI‑powered analysis.

Exchange admin dashboard adds provider list export for Actionable Messages
Category:Microsoft 365 apps
Nummer:MC1297983
Status:stayInformed

[Introduction]

We are introducing a new capability in the Outlook Actionable Messages admin dashboard that will help Exchange administrators improve visibility into Actionable Messages providers registered in their organization. This update will support auditing, documentation, and operational readiness by making provider information easier to review and export.

[When this will happen]

General Availability (Worldwide): We will begin rolling out this change in early May 2026 and expect to complete rollout by mid‑May 2026.

[How this affects your organization]

Who is affected

  • Exchange administrators who manage Outlook Actionable Messages
  • Organizations that use organization‑scoped registered providers for Actionable Messages

What will happen

  • Exchange administrators will be able to view a list of organization‑scoped registered Actionable Messages providers in the Outlook Actionable Messages admin dashboard: 

    user settings

  • Administrators will be able to download (export) the provider list for offline review, auditing, or documentation purposes.
  • The feature will be available by default after rollout.
  • No configuration changes will be required.
  • Existing provider registrations will not be modified.
  • There will be no impact to users, and Actionable Messages behavior in Outlook will remain unchanged.

[What you can do to prepare]

No action will be required.

Optionally, after rollout:

  • Review your organization‑scoped Actionable Messages providers using the admin dashboard.
  • Use the downloaded provider list for audit, documentation, or operational readiness purposes.
  • Update internal administrative documentation to reference this new dashboard capability.

Learn more: Actionable messages in Outlook and Office 365 Groups | Outlook | Microsoft Learn

[Compliance considerations]

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

Power Platform – Backup retention of Production environments is changing from 28 to 7 days
Category:Power Platform
Nummer:MC1298714
Status:stayInformed
Starting May 11, 2026, the default backup retention for Power Platform environments will be changed from 28 days to 7.

All environments will continue to be automatically protected with a 7‑day default backup, ensuring reliable recovery for day‑to‑day scenarios. For customers with higher compliance, governance, or operational needs, enabling Managed Environments unlocks the ability to extend backup retention up to 28 days, putting control directly in administrators’ hands. Managed environments will support up to 28 days of backup retention if increased by administrator; otherwise, the default is 7 days.

How does this affect me?
This change impacts the point in time restore window available for active environments and will not impact deleted environments. Currently, when a production environment with Dynamics 365 apps is deleted, the data will continue to be restorable for up to 28 days and when a production environment without Dynamics 365 apps is deleted, the data will continue to be restorable for up to 7 days. These are not changing.

For users with higher compliance, governance, or operational needs, enabling Managed Environments can extend its backup retention up to 28 days.

What action do I need to take?
This message is for awareness, and no action is required.

For environments that you want to extend the backup to 28 days, you will need to enable managed environment and change the backup retention period.
What’s new in the Microsoft Intune service update for April 2026
Category:Microsoft Intune
Nummer:MC1297979
Status:stayInformed

Your Microsoft Intune account has been updated to the latest service build.

[How this will affect your organization:]

You will see the service release number updated in the Tenant Status blade of the Intune admin center soon. We have introduced some changes that we are excited for you to try out.

[What you need to do to prepare:]

Review the additional information below to learn more about what’s new in this service release. We will continue to update the What’s new page with any features that are released between now and the next monthly service update. Learn more by reviewing features highlighted in the latest Intune What’s new 2604 (April) blog and how the Intune service updates each month is described in the Microsoft Intune service updates blog.

[Additional Information:]

Intune What’s new

Staying up to date on Intune new features, service changes, and service health

Agent Registry API transition to Agent 365
Category:Microsoft 365 suite
Nummer:MC1297981
Status:stayInformed

[Introduction]

As previously announced in MC1275311, Microsoft is consolidating agent management to simplify how administrators observe, govern, and secure agents, with Agent 365 (A365) as the single source of truth. A new Agent 365–powered agent registration Microsoft Graph API supports this consolidation and replaces the existing agent registry Graph API. This message provides API‑specific details and required actions.

[When this will happen]

  • General Availability (Worldwide): Rollout begins in early May 2026 and is expected to complete by late May 2026.
  • API retirement: The existing agent registry Graph API will begin retirement on June 15, 2026.

[How this affects your organization]

Who is affected

  • Microsoft 365 tenants with agents self‑registered using the existing agent registry Graph API
  • Developers or administrators responsible for custom agent lifecycle management

Note: This change does not apply to agents created through Microsoft agent builder platforms such as Copilot Studio or Foundry.

What will happen

  • A new Agent 365–powered agent registration Graph API is available as of May 1, 2026.
  • The existing agent registry Graph API will no longer be supported starting June 15, 2026.
  • Agents registered only through the existing API and not re‑registered before retirement will stop functioning.
  • Administrators can view all registered agents in the All agents view in the Microsoft 365 admin center (MAC).
  • This message fulfills the API transition previously referenced in MC1275311.

[What you can do to prepare]

  • Identify agent instances registered using the existing agent registry Graph API.
  • Re‑register those agents using the new Agent 365–powered agent registration Graph API before June 15, 2026.
  • Verify agent registrations in the All agents view in MAC.
  • Update internal documentation or automation that references the existing API.
  • Communicate this change to development and platform teams responsible for agent management.

Learn more: 

[Compliance considerations]

QuestionAnswer
Does this change introduce or significantly modify AI/ML or agent capabilities that interact with customer data?Yes. This change introduces a new Agent 365–powered agent registration API that governs how agents are registered and managed within Microsoft 365. It does not change agent behavior or access to customer data.
Does this change alter how admins can monitor, report on, or demonstrate compliance?Yes. Agent inventory and lifecycle visibility are centralized in the Microsoft 365 admin center, providing a unified view aligned with Agent 365.

Use sensitivity labels to block all connected experiences that analyze content in Word, Excel, and PowerPoint
Category:Microsoft 365 suite Microsoft 365 apps
Nummer:MC1297982
Status:planForChange

[Introduction]

Microsoft is updating an existing sensitivity label setting that controls whether certain connected experiences can analyze file content. This change extends support of this label setting to additional platforms and extends coverage of the label setting to include all connected experiences that analyze content in Word, Excel, and PowerPoint, rather than a subset of these experiences.

[When this will happen]

  • Public Preview: We will begin rolling out in mid-May 2026 and expect to complete by late May 2026.
  • General Availability (Worldwide, GCC, GCC High, DoD): 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

  • Organizations using Microsoft Purview sensitivity labels in Word, Excel, and PowerPoint
  • Users opening files that have a sensitivity label configured withPrevent some connected experiences that analyze content

What will happen

  • Files with this label setting will not be sent to any Microsoft connected experiences for content analysis.
  • Previously, this label setting blocked only a subset of connected experiences; enforcement is now expanded in Word, Excel, and PowerPoint.
  • This change applies automatically to existing labels configured with this setting.
  • There is no change to label configuration, and the behavior is enforced by default once the feature rolls out.

[What you can do to prepare]

No action is required if your organization already uses sensitivity labels.

Optional recommended steps:

  • Review sensitivity labels that use the Prevent some connected experiences that analyze content” setting to confirm they align with your organization’s data handling expectations.
  • Inform compliance and helpdesk teams that labeled files may no longer interact with connected experiences that analyze content in Word, Excel, and PowerPoint.
  • Update internal documentation if you describe how sensitivity labels affect Office app functionality.

[Compliance considerations]

QuestionAnswer
Does the change alter how existing customer data is processed, stored, or accessed?Yes. Files with applicable sensitivity labels are now fully blocked from being sent to Microsoft connected experiences for analysis, expanding enforcement beyond a subset of experiences.
Does the change modify Information Protection labels or their enforcement?Yes. Existing sensitivity label settings now enforce broader blocking behavior across all connected experiences that analyze content.
Does the change introduce or modify AI/ML capabilities that interact with customer data?Yes. The change restricts how labeled content can be analyzed by Microsoft connected experiences, including AI‑powered analysis.

Exchange admin dashboard adds provider list export for Actionable Messages
Category:Microsoft 365 apps
Nummer:MC1297983
Status:stayInformed

[Introduction]

We are introducing a new capability in the Outlook Actionable Messages admin dashboard that will help Exchange administrators improve visibility into Actionable Messages providers registered in their organization. This update will support auditing, documentation, and operational readiness by making provider information easier to review and export.

[When this will happen]

General Availability (Worldwide): We will begin rolling out this change in early May 2026 and expect to complete rollout by mid‑May 2026.

[How this affects your organization]

Who is affected

  • Exchange administrators who manage Outlook Actionable Messages
  • Organizations that use organization‑scoped registered providers for Actionable Messages

What will happen

  • Exchange administrators will be able to view a list of organization‑scoped registered Actionable Messages providers in the Outlook Actionable Messages admin dashboard: 

    user settings

  • Administrators will be able to download (export) the provider list for offline review, auditing, or documentation purposes.
  • The feature will be available by default after rollout.
  • No configuration changes will be required.
  • Existing provider registrations will not be modified.
  • There will be no impact to users, and Actionable Messages behavior in Outlook will remain unchanged.

[What you can do to prepare]

No action will be required.

Optionally, after rollout:

  • Review your organization‑scoped Actionable Messages providers using the admin dashboard.
  • Use the downloaded provider list for audit, documentation, or operational readiness purposes.
  • Update internal administrative documentation to reference this new dashboard capability.

Learn more: Actionable messages in Outlook and Office 365 Groups | Outlook | Microsoft Learn

[Compliance considerations]

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

Power Platform – Backup retention of Production environments is changing from 28 to 7 days
Category:Power Platform
Nummer:MC1298714
Status:stayInformed
Starting May 11, 2026, the default backup retention for Power Platform environments will be changed from 28 days to 7.

All environments will continue to be automatically protected with a 7‑day default backup, ensuring reliable recovery for day‑to‑day scenarios. For customers with higher compliance, governance, or operational needs, enabling Managed Environments unlocks the ability to extend backup retention up to 28 days, putting control directly in administrators’ hands. Managed environments will support up to 28 days of backup retention if increased by administrator; otherwise, the default is 7 days.

How does this affect me?
This change impacts the point in time restore window available for active environments and will not impact deleted environments. Currently, when a production environment with Dynamics 365 apps is deleted, the data will continue to be restorable for up to 28 days and when a production environment without Dynamics 365 apps is deleted, the data will continue to be restorable for up to 7 days. These are not changing.

For users with higher compliance, governance, or operational needs, enabling Managed Environments can extend its backup retention up to 28 days.

What action do I need to take?
This message is for awareness, and no action is required.

For environments that you want to extend the backup to 28 days, you will need to enable managed environment and change the backup retention period.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top