Sending multimedia content and documents within chat conversations in Microsoft Teams
Hi @Ahmed,
Thank you for providing the detailed testing results.
Based on the information provided, your understanding aligns with the Microsoft documentation. When external chat file sharing is enabled, users are expected to be able to share files both by uploading a file and by dragging and dropping a file into the message compose area. Microsoft also identifies FileSharingInChatsWithExternalUsers as the required Teams Files policy setting for this capability.
The key detail in your testing is that file sharing itself is already working. Files can be successfully shared using the Attach File button in the same federated conversations, which indicates that external file sharing is not being blocked entirely.
Since:
- Attach File works successfully
- Drag-and-drop fails for multiple file types
- The issue reproduces in both Teams Desktop and Teams Web
- SharePoint and OneDrive external sharing are enabled
the behavior appears to be isolated to the drag-and-drop upload workflow rather than the overall external file-sharing configuration.
One remaining check would be to confirm the effective Teams policies applied to an affected user, since the PowerShell output provided shows the Global policy settings. Microsoft documents that a policy assigned directly to a user or through a group can take precedence over the Global policy.
You can review the policy assignments for an affected user with:
*Get-CsUserPolicyAssignment -Identity *****@domain.com
If the affected user is receiving the expected Teams Files and Messaging policies, then based on the currently published documentation, I am not aware of a separate Teams policy that controls drag-and-drop uploads independently from standard file attachments in external chats.
As this is a user-to-user community forum, I do not have access to tenant-level diagnostics, backend telemetry, or service-side configuration. Given the evidence provided, the next appropriate step would be open a Microsoft 365 support request so that Microsoft can review the service logs and determine whether this is a backend issue, product regression, or another tenant-specific condition.
References: