Microsoft Roadmap, messagecenter and blogs updates from 15-02-2026

Updated February 13, 2026: We have updated the timeline. Thank you for your patience. 

Coming soon to Microsoft Purview | Information Protection: To help improve label usability and configuration, the sensitivity labeling scheme will be simplified to only consist of labels and label groupings.

This move to a dynamic architecture will make it easier to move a child label into label groups, out of label groups, and between label groups without losing referential integrity, allowing customers to better scale and reorganize their labels across their entire data estate.

Tenants in scope for manual migration to the new label scheme will see a message on the Sensitivity labels page in the Purview portal, where the tenant admin can access a simple manual migration wizard to opt in to the migration, which should complete in less than a few minutes or even seconds, depending on the label configuration.

If you do not see this message, your tenant does not meet the criteria for manual migration (your tenant lacks applicable parent labels). This new label scheme will be rolled out to your tenant in the coming months. (and we will send a separate MC post in advance).

This message is associated with Microsoft 365 Roadmap ID 386900.

[When this will happen:]

Public Preview (Worldwide): Modern labels have been in Public Preview since July 7th 2025. This post announces the rollout of modern label scheme to new tenants and tenants with applicable parents.

General Availability (Worldwide): We will being rolling out early December 2025 and expect to be completed by mid-March 2026 (previously end of January). As part of GA, customers with non-applicable parents will be auto migrated to the modern label scheme while migration for customers with applicable parents will continue to be opt-in for 12 months post-GA. We will auto-migrate customers with applicable parents to the modern label scheme once the 12-month extension ends. 

[How this will affect your organization:]

During migration, to ensure label scoping integrity, any applicable parent label will be converted to a child label under a new label group, and then both parent and child label will have the same display name as the original parent label. Non-applicable parent labels will automatically be converted to label groups.

A parent label is deemed applicable if it has a different scope from any of its children, has label actions, or is published separately from its children.

The manual migration wizard provides a preview of the migrated scheme so admins can better understand how their sensitivity label scheme will change after the migration.

After migration, admins are free to make changes to their migrated label scheme, including unpublishing applicable parent labels that were converted to children during migration.

Users will not notice any change in how labels are viewed or applied. This change will be on by default.

Example of a migrated label scheme:

[What you need to do to prepare:]

This rollout will happen automatically by the specified dates with no admin action required before the rollout. Review your tenant’s label scheme to ensure it is up to date. You may want to notify your admins about this change and update any relevant documentation.

Optionally, before you migrate your production tenant, consider migrating a test tenant configured with a label scheme that is representative of your production tenant, to become familiar with the migration process and the modern label scheme.

Learn more: Learn about sensitivity labels | Microsoft Learn

Updated February 13, 2026: We have updated the content. Thank you for your patience.

Agents in OneDrive lets you group files and folders together, so you can ask questions, get summaries, and find key details across your project—without having to reselect items each time. Agents are saved in your OneDrive and can be shared with your team, making collaboration and staying up to date easier. This new capability helps users work more efficiently by turning OneDrive into a workspace for AI-powered project assistance.

This message is associated with Microsoft 365 Roadmap ID 469503.

General Availability (Worldwide): This is now generally available.

Who is affected: Users with a Microsoft 365 Copilot license assigned to either work or school accounts (Microsoft 365 commercial or education tenants). 

What will happen:

Users will see a new agent option in OneDrive.

How to use Agents in OneDrive:

• Create your Agent: When users first select the Copilot button in OneDrive or the +Create or upload button, a guided experience will introduce agents and walk users through how to create and use them. From there, users can create an agent from their OneDrive using the +Create or upload option and then select the Agent option (screenshot 1):

 

• Alternatively, users can select the files to include in an agent, then choose Create an agent from the Copilot toolbar dropdown menu (screenshot 2):

 

• Access your agent as a file in OneDrive (.agent extension), filter by file type “agent” (screenshot 3):

 

• Open the agent to ask questions and get answers from your documents.
• Edit or update your agent anytime to change its sources, name, or instructions (screenshot 4):

 

• Share your agent with your team to collaborate and keep everyone informed (screenshots 5 & 6):

 

No admin action is required at this time.

You may wish to:

• Communicate this change to helpdesk staff.
• Update internal documentation to reflect the new agent capabilities in OneDrive.
• Encourage users to explore agents to improve project efficiency using AI.
• Review this Blog: Meet Agents in OneDrive: Your AI assistant built with your own content | Microsoft Community Hub 
• Watch this video: Bring insights of your OneDrive files into Microsoft 365 Copilot
• Review documentation at the following links:
  • Get started with OneDrive agents
  • Create and use an agent in OneDrive
  • Find your agent files in OneDrive
  • Share an AI agent in OneDrive

[Introduction]

Microsoft Teams is introducing simplified meeting passcodes to reduce friction when joining meetings, especially when participants must manually enter a passcode. This feature is off by default and must be explicitly enabled by a tenant administrator.

This message is associated with Microsoft 365 Roadmap ID 555858.

[When this will happen]

• Targeted Release: We will begin rolling out in early March 2026 and expect to complete by mid-March 2026.
• General Availability
  • Worldwide & GCC: We will begin rolling out in mid-March 2026 and expect to complete by late March 2026.
  • GCCH & DoD: We will begin rolling out in early April 2026 and expect to complete by mid-April 2026.

[How this affects your organization]

Who is affected:

Tenant administrators who manage meeting security settings in Microsoft Teams.

What will happen:

• A new admin setting allows simplified 8‑digit numeric‑only meeting passcodes.
• The feature is off by default; admins must opt in.
• The setting can be applied to:
  • Specific users
  • Groups
  • The entire tenant
• Only newly scheduled meetings use numeric‑only passcodes.
• Existing meetings are not changed.
• If the feature remains off, Teams continues to use the default, more complex passcodes.

Security considerations:

• Numeric‑only passcodes reduce cryptographic strength relative to the default setting.
• The simplified passcode applies whether users join via meeting ID or by clicking a meeting link.
• Admins will see a security warning when enabling the setting.
• All other Teams meeting security controls remain unchanged, including:
  • Lobby and admission controls
  • Organizer and participant policies
  • Tenant authentication and access controls

[What you can do to prepare]

• Review your organization’s meeting security requirements.
• Decide whether simplified passcodes meet your policies.
• If enabling, determine appropriate scope (users, groups, or tenant‑wide).
• If maintaining current behavior, no action is required.
• Consider updating internal documentation and informing helpdesk staff if you enable the feature.

[Compliance considerations]

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

The In development for Microsoft Intune page in our documentation has been updated.

[How this will affect your organization:]

The In development page provides a list of features in upcoming releases of Microsoft Intune to assist in your readiness and planning. The list has now been updated. You will start seeing these changes in the next month or in a subsequent release.

[What you need to do to prepare:]

You can inform your IT staff and helpdesk of the upcoming changes listed on this page. Plan to update your user guidance, if you feel any of these features would be important to your users.

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 2601 (January) 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