check before: 2025-09-01

Product:

Microsoft 365 admin center, Teams, Windows

Platform:

Android, iOS, Mac, Online, Web, Windows Desktop, World tenant

Status:

Feature Rollout Status Not Supported

Change type:

Admin impact, New feature, Updated message, User impact

Links:

499892

Details:

Summary:
Microsoft Teams will block messages containing weaponizable file types (e.g., executables) in chats and channels starting November 2025, enhancing security by preventing unsafe content sharing. The feature will be on by default at General Availability, with admins able to configure settings via the Teams Admin Center or PowerShell.

Details:
Updated November 17, 2025: The rollout of Weaponizable file type protection in Microsoft Teams is expected to finish before the end of November 2025 for General Availability (Worldwide). The previously announced update to make Weaponizable file protection setting in Messaging settings ON by default has been postponed to early 2026. A separate communication will be issued detailing the roll out schedule for the default-on change in advance.

Thank you for your patience.
Introduction
Microsoft Teams is introducing a new protection feature that blocks messages containing weaponizable file types-such as executables-in chats and channels. This helps reduce the risk of malware and file-based attacks by preventing unsafe content from being shared. This message applies to Teams for Windows desktop, Teams for Mac desktop, Teams for the web, and Teams for iOS/Android.
This message is associated with Roadmap ID 499892.
When this will happen
General Availability begins November 3 and will complete by end of November. At GA, "Scan messages for file types that are not allowed" will default to ON, and protection will apply if any participant in a conversation has it enabled.
To use a different setting, go to Teams admin center → Messaging settings → Scan messages for file types that are not allowed, select your preference, and click Save before GA.
Note: Simply viewing the page without saving will not override the default, but settings already saved during Targeted Release will persist.
Targeted release (Worldwide): Starts early September 2025; expected to complete by mid-September 2025.
General Availability (Worldwide): Starts early November 2025; expected to complete by end of November 2025 (previously mid-November).

Change Category:
XXXXXXX ... free basic plan only

Scope:
XXXXXXX ... free basic plan only

Release Phase:
Standard Release

Created:
2025-09-06

updated:
2025-11-18

Task Type

XXXXXXX ... free basic plan only

Docu to Check

XXXXXXX ... free basic plan only

MS How does it affect me

XXXXXXX ... free basic plan only

MS Preperations

XXXXXXX ... free basic plan only

MS Urgency

XXXXXXX ... free basic plan only

MS workload name

XXXXXXX ... free basic plan only

linked item details

XXXXXXX ... free basic plan only

Pictures

XXXXXXX ... free basic plan only

summary for non-techies**

XXXXXXX ... free basic plan only

Direct effects for Operations**

Blocked Message Delivery
Messages containing weaponizable file types will be blocked, preventing users from accessing important content and potentially disrupting workflows.
   - roles: End Users, Team Leaders
   - references: https://learn.microsoft.com/microsoftteams/weaponizable-file-protection-teams, https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=499892

User Experience Disruption
Users will receive notifications about blocked messages, which may lead to confusion and frustration, impacting overall user satisfaction with Teams.
   - roles: End Users, Support Staff
   - references: https://learn.microsoft.com/microsoftteams/weaponizable-file-protection-teams, https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=499892

Increased Administrative Workload
Admins will need to manage and configure new settings in the Teams Admin Center or PowerShell, increasing their workload and requiring additional training.
   - roles: IT Administrators, Compliance Officers
   - references: https://learn.microsoft.com/microsoftteams/weaponizable-file-protection-teams, https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=499892

Configutation Options**

XXXXXXX ... paid membership only

Opportunities**

Enhanced Security Awareness Training
With the introduction of weaponizable file type protection, there is an opportunity to enhance security awareness training for users. Educating users on the types of files that are blocked and the reasons behind this protection can foster a culture of security and vigilance.
   - next-steps: Develop and implement a training program that includes information on weaponizable file types and best practices for sharing files securely in Teams. Schedule training sessions and create accessible online resources.
   - roles: IT Security Team, Training and Development Team, All Employees
   - references: https://learn.microsoft.com/microsoftteams/weaponizable-file-protection-teams, https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=499892

Policy Review and Update
The new file protection feature necessitates a review of existing IT policies related to file sharing and security. Updating these policies to align with the new protection measures can help ensure compliance and enhance overall security posture.
   - next-steps: Conduct a policy review meeting with key stakeholders to assess current file-sharing policies. Draft updates that incorporate the new protection measures and distribute them for feedback before finalization.
   - roles: Compliance Officer, IT Management, Legal Team
   - references: https://learn.microsoft.com/microsoftteams/weaponizable-file-protection-teams, https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=499892

Integration with Security Tools
Integrating Teams' new file protection capabilities with existing security tools (e.g., SIEM systems) can enhance monitoring and response to potential threats. This integration can provide better visibility into file-sharing activities and alerts for any policy violations.
   - next-steps: Evaluate current security tools and identify integration points with Teams' file protection features. Collaborate with vendors to implement necessary changes and conduct testing to ensure effective monitoring.
   - roles: IT Security Team, Network Administrators, Compliance Officer
   - references: https://learn.microsoft.com/microsoftteams/weaponizable-file-protection-teams, https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=499892

Potentional Risks**

XXXXXXX ... paid membership only

IT Security**

XXXXXXX ... paid membership only

explanation for non-techies**

XXXXXXX ... free basic plan only

** AI generated content. This information must be reviewed before use.

a free basic plan is required to see more details. Sign up here


A cloudsocut.one plan is required to see all the changed details. If you are already a customer, choose login.
If you are new to cloudscout.one please choose a plan.



change history

DatePropertyoldnew
2025-11-18MC Last Updated10/30/2025 18:57:042025-11-17T18:08:15Z
2025-11-18MC MessagesUpdated October 30, 2025: We have updated the content. Thank you for your patience.
Introduction
Microsoft Teams is introducing a new protection feature that blocks messages containing weaponizable file types-such as executables-in chats and channels. This helps reduce the risk of malware and file-based attacks by preventing unsafe content from being shared. This message applies to Teams for Windows desktop, Teams for Mac desktop, Teams for the web, and Teams for iOS/Android.
This message is associated with Roadmap ID 499892.
When this will happen
General Availability begins November 3 and will take 2-3 weeks to complete. At GA, "Scan messages for file types that are not allowed" will default to ON, and protection will apply if any participant in a conversation has it enabled.
To use a different setting, go to Teams admin center → Messaging settings → Scan messages for file types that are not allowed, select your preference, and click Save before GA.
Note: Simply viewing the page without saving will not override the default, but settings already saved during Targeted Release will persist.
Targeted release (Worldwide): Starts early September 2025; expected to complete by mid-September 2025.
General Availability (Worldwide): Starts early November 2025; expected to complete by mid-November 2025.
Updated November 17, 2025: The rollout of Weaponizable file type protection in Microsoft Teams is expected to finish before the end of November 2025 for General Availability (Worldwide). The previously announced update to make Weaponizable file protection setting in Messaging settings ON by default has been postponed to early 2026. A separate communication will be issued detailing the roll out schedule for the default-on change in advance.

Thank you for your patience.
Introduction
Microsoft Teams is introducing a new protection feature that blocks messages containing weaponizable file types-such as executables-in chats and channels. This helps reduce the risk of malware and file-based attacks by preventing unsafe content from being shared. This message applies to Teams for Windows desktop, Teams for Mac desktop, Teams for the web, and Teams for iOS/Android.
This message is associated with Roadmap ID 499892.
When this will happen
General Availability begins November 3 and will complete by end of November. At GA, "Scan messages for file types that are not allowed" will default to ON, and protection will apply if any participant in a conversation has it enabled.
To use a different setting, go to Teams admin center → Messaging settings → Scan messages for file types that are not allowed, select your preference, and click Save before GA.
Note: Simply viewing the page without saving will not override the default, but settings already saved during Targeted Release will persist.
Targeted release (Worldwide): Starts early September 2025; expected to complete by mid-September 2025.
General Availability (Worldwide): Starts early November 2025; expected to complete by end of November 2025 (previously mid-November).
2025-11-18MC End Time12/16/2025 09:00:002025-12-31T09:00:00Z
2025-11-18MC SummaryMicrosoft Teams will block messages containing unsafe, weaponizable file types in chats and channels starting November 3, 2025. This protection, enabled by default at General Availability, notifies senders and recipients when messages are blocked. Admins can configure settings via the Teams Admin Center or PowerShell.Microsoft Teams will block messages containing weaponizable file types (e.g., executables) in chats and channels starting November 2025, enhancing security by preventing unsafe content sharing. The feature will be on by default at General Availability, with admins able to configure settings via the Teams Admin Center or PowerShell.
2025-11-17MC Feature RingStandard Release, Targeted ReleaseStandard Release
2025-11-07MC Feature RingStandard ReleaseStandard Release, Targeted Release
2025-11-07MC Feature StatusFeature Rollout Status Not Supported
2025-11-02MC Feature StatusFeature Rollout Status Not Supported
2025-10-30MC MessagesUpdated September 9, 2025: We have updated the content. Thank you for your patience.
Introduction
Microsoft Teams is introducing a new protection feature that blocks messages containing weaponizable file types-such as executables-in chats and channels. This helps reduce the risk of malware and file-based attacks by preventing unsafe content from being shared. This message applies to Teams for Windows desktop, Teams for Mac desktop, Teams for the web, and Teams for iOS/Android.
This message is associated with Roadmap ID 499892.
When this will happen
Targeted release (Worldwide): Starts early September 2025; expected to complete by mid-September 2025.
General Availability (Worldwide): Starts early November 2025; expected to complete by mid-November 2025.
Updated October 30, 2025: We have updated the content. Thank you for your patience.
Introduction
Microsoft Teams is introducing a new protection feature that blocks messages containing weaponizable file types-such as executables-in chats and channels. This helps reduce the risk of malware and file-based attacks by preventing unsafe content from being shared. This message applies to Teams for Windows desktop, Teams for Mac desktop, Teams for the web, and Teams for iOS/Android.
This message is associated with Roadmap ID 499892.
When this will happen
General Availability begins November 3 and will take 2-3 weeks to complete. At GA, "Scan messages for file types that are not allowed" will default to ON, and protection will apply if any participant in a conversation has it enabled.
To use a different setting, go to Teams admin center → Messaging settings → Scan messages for file types that are not allowed, select your preference, and click Save before GA.
Note: Simply viewing the page without saving will not override the default, but settings already saved during Targeted Release will persist.
Targeted release (Worldwide): Starts early September 2025; expected to complete by mid-September 2025.
General Availability (Worldwide): Starts early November 2025; expected to complete by mid-November 2025.
2025-10-30MC TitleNew file protection in Teams chat and channels blocks unsafe content(Updated) New file protection in Teams chat and channels blocks unsafe content
2025-10-30MC Last Updated09/09/2025 17:19:022025-10-30T18:57:04Z
2025-10-30MC SummaryMicrosoft Teams will block messages containing weaponizable file types (e.g., executables) in chats and channels to reduce malware risks. This feature starts targeted release in September 2025 (off by default) and general availability in November 2025 (on by default). Admins can enable it via Teams Admin Center or PowerShell.Microsoft Teams will block messages containing unsafe, weaponizable file types in chats and channels starting November 3, 2025. This protection, enabled by default at General Availability, notifies senders and recipients when messages are blocked. Admins can configure settings via the Teams Admin Center or PowerShell.
2025-10-16MC Feature RingStandard Release, Targeted ReleaseStandard Release
2025-09-11MC Feature RingTargeted ReleaseStandard Release, Targeted Release
2025-09-10MC preparehttps://learn.microsoft.com/microsoftteams/malicious-url-protection-teams
https://learn.microsoft.com/microsoftteams/security-compliance-overview
https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=499892
https://learn.microsoft.com/microsoftteams/weaponizable-file-protection-teams
https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=499892
2025-09-10MC MessageTagNamesNew feature, User impact, Admin impactUpdated message, New feature, User impact, Admin impact
2025-09-10MC SummaryMicrosoft Teams will block messages containing unsafe, weaponizable file types in chats and channels starting September 2025 (targeted release) and November 2025 (general availability). Admins can enable this protection via Teams Admin Center or PowerShell. Blocked files include executables and other risky formats to reduce malware risks.Microsoft Teams will block messages containing weaponizable file types (e.g., executables) in chats and channels to reduce malware risks. This feature starts targeted release in September 2025 (off by default) and general availability in November 2025 (on by default). Admins can enable it via Teams Admin Center or PowerShell.
2025-09-10MC Last Updated09/06/2025 00:03:472025-09-09T17:19:02Z
2025-09-10MC MessagesIntroduction
Microsoft Teams is introducing a new protection feature that blocks messages containing weaponizable file types-such as executables-in chats and channels. This helps reduce the risk of malware and file-based attacks by preventing unsafe content from being shared. This message applies to Teams for Windows desktop, Teams for Mac desktop, Teams for the web, and Teams for iOS/Android.
This message is associated with Roadmap ID 499892.
When this will happen
Targeted release (Worldwide): Starts early September 2025; expected to complete by mid-September 2025.
General Availability (Worldwide): Starts early November 2025; expected to complete by mid-November 2025.
Updated September 9, 2025: We have updated the content. Thank you for your patience.
Introduction
Microsoft Teams is introducing a new protection feature that blocks messages containing weaponizable file types-such as executables-in chats and channels. This helps reduce the risk of malware and file-based attacks by preventing unsafe content from being shared. This message applies to Teams for Windows desktop, Teams for Mac desktop, Teams for the web, and Teams for iOS/Android.
This message is associated with Roadmap ID 499892.
When this will happen
Targeted release (Worldwide): Starts early September 2025; expected to complete by mid-September 2025.
General Availability (Worldwide): Starts early November 2025; expected to complete by mid-November 2025.
2025-09-10MC How AffectOnce enabled, Teams will automatically block messages that include weaponizable file types. This applies to both internal and external conversations.
Recipients will see a notification that a message was blocked but cannot access the content.
Senders will receive a notification and can edit and resend the message without the unsafe file.

Targeted release vs. General Availability behavior:
Targeted release: Protection is enforced only when all organizations in the conversation have the feature enabled. This feature is off by default and requires admin activation.
General Availability: Protection is enforced if at least one participant has the feature enabled. This feature is on by default. Admin settings saved during Targeted Release will remain unchanged.
What you can do to prepare
Admins can enable this protection in the Teams Admin Center:
Go to the Teams Admin Center
Navigate to Messaging Settings
Turn on the setting: Scan messages for file types that are not allowed


Alternatively, use PowerShell with the -FileTypeCheck parameter.
Once enabled, all users in your tenant will begin seeing file protection applied in their messages.
Blocked file types include:
ace, ani, apk, app, appx, arj, bat, cab, cmd, com, deb, dex, dll, docm, elf, exe, hta, img, iso, jar, jnlp, kext, lha, lib, library, lnk, lzh, macho, msc, msi, msix, msp, mst, pif, ppa, ppam, reg, rev, scf, scr, sct, sys, uif, vb, vbe, vbs, vxd, wsc, wsf, wsh, xll, xz, z
Learn more:
Overview of security and compliance - Microsoft Teams | Microsoft Learn (will be updated before rollout)
Malicious URL Protection in Microsoft Teams
Compliance considerations
Compliance AreaExplanation

Does the change modify how users can access, export, delete, or correct their personal data within Microsoft 365 services?Blocked messages are not delivered, which may affect access to the original message content. Recipients of messages with disallowed file types will not receive the message or its attachments.
Once enabled, Teams will automatically block messages that include weaponizable file types. This applies to both internal and external conversations.
Recipients will see a notification that a message was blocked but cannot access the content.
Senders will receive a notification and can edit and resend the message without the unsafe file.

Targeted release vs. General Availability behavior:
Targeted release: Protection is enforced only when all organizations in the conversation have the feature enabled. This feature is off by default and requires admin activation.
General Availability: Protection is enforced if at least one participant has the feature enabled. This feature is on by default. Admin settings saved during Targeted Release will remain unchanged.
What you can do to prepare
Admins can enable this protection in the Teams Admin Center:
Go to the Teams Admin Center
Navigate to Messaging Settings
Turn on the setting: Scan messages for file types that are not allowed


Alternatively, use PowerShell with the -FileTypeCheck parameter.
Once enabled, all users in your tenant will begin seeing file protection applied in their messages.
Blocked file types include:
ace, ani, apk, app, appx, arj, bat, cab, cmd, com, deb, dex, dll, docm, elf, exe, hta, img, iso, jar, jnlp, kext, lha, lib, library, lnk, lzh, macho, msc, msi, msix, msp, mst, pif, ppa, ppam, reg, rev, scf, scr, sct, sys, uif, vb, vbe, vbs, vxd, wsc, wsf, wsh, xll, xz, z
Learn more:
Weaponizable File Protection in Microsoft Teams
Compliance considerations
Compliance AreaExplanation

Does the change modify how users can access, export, delete, or correct their personal data within Microsoft 365 services?Blocked messages are not delivered, which may affect access to the original message content. Recipients of messages with disallowed file types will not receive the message or its attachments.
2025-09-08MC Feature RingTargeted Release

Last updated 3 weeks ago ago

Leave a Reply

Share to MS Teams

Login to your account

Welcome Back, We Missed You!