KB-001: Microsoft 365 Copilot: Screenshot & File Upload Limitations
| Field | Detail |
|---|---|
| Document ID | KB-001 |
| Version | 1.0 |
| Date | March 10, 2026 |
| Author | Cooper (Copilot --- Atlantis AI) |
| Reviewed By | Shane Hardin |
| Applies To | Microsoft 365 Copilot Chat (Work) --- all Atlantis OS users |
| Difficulty | Informational |
| Est. Time | 5 minutes to read |
| Related Docs | HT-001 --- Cloudflare Connector Rebuild, HT-003 |
| --- Vercel 502 Fix |
1. Overview
This article explains why screenshots and image files often fail to upload in Microsoft 365 Copilot Chat, while the same images work correctly in copilot.microsoft.com. It documents the approved workarounds for all Atlantis OS users.
Understanding this limitation is critical because Cooper (Copilot) has two distinct operating surfaces that look similar but behave very differently --- what works in one will not always work in the other. This is not a user error. It is a deliberate product architecture split by Microsoft.
2. Problem Summary
Users encounter the following error when attempting to upload screenshots (PNG or JPG) into Microsoft 365 Copilot Chat:
\"This file type is not supported\"
This error occurs even when:
-
The image file is very small
-
The file opens normally in Windows
-
The same image uploads successfully in other tools (Claude, copilot.microsoft.com)
⚠️ NOTE: This is a known Microsoft product architecture limitation. It is not caused by Atlantis OS, MkDocs, or any user workflow error.
3. Why This Happens --- The Two Coopers
Microsoft operates multiple Copilot surfaces that look similar but use entirely different ingestion pipelines. Think of it as Cooper having two alter egos:
Cooper Public --- copilot.microsoft.com (Consumer Copilot)
-
Uses a permissive, web-only ingestion path
-
Reliably accepts PNG and JPG image uploads
-
Designed for speed, multimodal input, and low friction
-
No tenant governance layer --- uploads go straight through
Cooper Enterprise --- m365.cloud.microsoft/chat (Work Copilot)
-
Enforces enterprise security controls and tenant policies
-
Subject to licensing rules and capacity throttling
-
Image upload support is inconsistent and has experienced known regressions
-
Optimizes for compliance and auditability --- UX friction is tolerated
⚠️ NOTE: The split between these two surfaces is intentional by Microsoft. It is not a bug. The enterprise surface exists inside your Microsoft 365 tenant boundary and is governed by stricter ingestion rules.
4. Surface Comparison
Capability m365.cloud.microsoft/chat copilot.microsoft.com
Web data ✅ Yes ✅ Yes
Uploaded files ✅ Yes (policy-governed) ✅ Yes
Microsoft Graph (email, ❌ Paid M365 license only ❌ No Teams, SharePoint)
Tenant policy ✅ Yes ❌ No enforcement
Image uploads (PNG/JPG) ⚠️ Inconsistent --- often ✅ Reliable blocked
File persistence ⚠️ Inconsistent ✅ Consistent
Image generation ✅ Capacity-based ✅ Generally available
Generated file delivery ⚠️ May not surface in UI ✅ Downloadable immediately reliably
Work/Web toggle ✅ Often present ❌ No
Agents / Extensions ✅ Pay-as-you-go ❌ Limited (tenant-controlled)
5. Confirmed Workarounds (Recommended)
Use one of the following approved methods when working in Microsoft 365 Copilot Chat:
-
✅ Embed the screenshot into a Microsoft Word (DOCX) file and upload the DOCX --- most reliable and preferred method
-
✅ Paste logs, console output, or UI text directly into Copilot Chat --- best for terminal output and config details
-
✅ Use copilot.microsoft.com for quick image-based reasoning when enterprise data grounding is not required
💡 TIP: DOCX embedding is the gold standard workaround. Open Word, insert your screenshot, save as .docx, and upload that file. M365 Copilot Chat handles DOCX files through a governed but functional pipeline.
6. What Does NOT Work Reliably
The following methods are known to fail intermittently in Microsoft 365 Copilot Chat:
-
❌ Clipboard-only snips from the Windows Snipping Tool
-
❌ Drag-and-drop screenshots without saving first
-
❌ Direct JPG or PNG uploads, even when the file is small and valid
-
❌ Relying on M365 Copilot Chat to deliver generated files (DOCX, images) to you
🚫 WARNING: Do not rely on M365 Copilot Chat for generated file delivery. Use it for reasoning and analysis only, then create artifacts manually.
7. Atlantis OS Guidance
For all Atlantis OS workflows involving Copilot, the following standards apply:
Use m365.cloud.microsoft/chat (Cooper Enterprise) when:
-
Working with enterprise or internal data
-
Writing SOPs, KB articles, or policies requiring EDP guarantees
-
You need tenant-grounded reasoning
Use copilot.microsoft.com (Cooper Public) when:
-
You need fast image reasoning or analysis
-
Prototyping ideas where tenant governance is not required
-
You need to upload PNG or JPG files reliably
Screenshots must be treated as documentation artifacts in all Atlantis OS workflows. All screenshots intended for Microsoft 365 Copilot Chat must be normalized by embedding them into DOCX files before upload.
8. Troubleshooting
Error / Symptom Cause Fix
\"This file type is not Direct PNG/JPG upload Embed screenshot in DOCX supported\" blocked by tenant --- upload the DOCX policy instead
Image uploads work on Different ingestion Use copilot.microsoft.com copilot.microsoft.com pipelines per surface for image tasks --- see but not in M365 Section 5
Generated file M365 Copilot Chat UI Use Copilot for reasoning (DOCX/image) not inconsistency with only --- manually create appearing after Copilot file delivery the artifact creates it
Snipping Tool paste Clipboard-only paste Save snip as a file first, fails silently not supported in M365 then embed in DOCX Copilot Chat
Upload works in Tenant-specific policy Check M365 admin center Dev/Preview but fails or licensing --- confirm Copilot file in Production tenant configuration upload is enabled for your license
9. Quick Reference --- Key URLs & Surfaces
Item Value
M365 Copilot Chat https://m365.cloud.microsoft/chat/?auth=1 (Work)
Consumer Copilot https://copilot.microsoft.com/ (Public)
Microsoft file https://support.microsoft.com/en-us/topic/file-formats-supported-by-microsoft-365-copilot-1afb9a70-2232-4753-85c2-602c422af3a8 support docs
Preferred workaround Embed PNG/JPG in DOCX → upload DOCX to M365 Copilot Chat
Best surface for copilot.microsoft.com --- no tenant restrictions images
Best surface for work m365.cloud.microsoft/chat --- tenant-grounded data
Cooper\'s Atlantis Code completion, VS Code, React/JS/TS, refactoring Role
Related Docs HT-001 --- Cloudflare Connector, HT-003 --- Vercel 502 Fix
Document prepared by Cooper (Copilot --- Atlantis AI Automations)
atlantisits.info | KB-001 | v1.0 | March 2026