Dear Microsoft Support Team,
I need your assistance in resolving a persistent file upload issue affecting one of our Copilot Studio agents published to Microsoft Teams.
Issue Description
We have a Copilot Studio agent named Project Assistant Agent_GPT6.1, which we use as part of our regular project management workflow.
One of its functions is to process Microsoft Teams meeting transcript files, mainly .vtt files, generate structured meeting minutes, and save the meeting information for future project use.
The workflow was working correctly until approximately 20 files had been uploaded through Microsoft Teams.
The agent now rejects any new attachment with the following message:
“I couldn't accept one of your attachments because this conversation has reached its 20-file upload limit.”
The critical issue is that creating a new conversation does not reset the limit.
Even the first file uploaded in a completely new conversation is rejected with the same 20-file limit message.
This prevents us from continuing an established business workflow.
Troubleshooting Already Completed
I have performed the following tests:
Started a completely new conversation in Microsoft Teams
- Result: Failed.
- The first file in the new conversation is immediately rejected with the same 20-file limit message.
Deleted previous conversation history
- Result: No change.
**Removed the Agent from Microsoft Teams and reinstalled it**
- Result: No change.
**Tested different supported file types**
- Tested `.vtt` and `.docx`.
- Result: Same issue.
**Attempted to use SharePoint instead of uploading the transcript directly**
- The Agent can locate the SharePoint folder and identify the requested meeting transcript by file name.
- However, it cannot retrieve/read the actual `.vtt` transcript content.
- Even when the direct SharePoint file link is supplied, the Agent asks for the transcript to be downloaded and uploaded directly into the conversation.
- Therefore, SharePoint does not provide a working replacement for the existing attachment workflow.
**Tested the same Project Assistant Agent directly in Copilot Studio**
- Result: **Successful.**
- The same meeting transcript can be uploaded successfully.
- The Agent reads and processes the transcript correctly.
- The `teams-meeting-minutes` skill executes correctly.
- The `SaveMeetingTranscript` tool executes correctly.
- Meeting minutes are successfully generated.
```Therefore, the core Agent configuration and transcript-processing workflow appear to be functioning correctly.
Current Comparison
Copilot Studio Test Chat
- File upload: Successful
- Transcript reading: Successful
- Meeting-minutes skill: Successful
-
SaveMeetingTranscript tool: Successful
- Meeting minutes generation: Successful
Published Agent in Microsoft Teams
- File upload: Failed
- Error: 20-file upload limit
- New conversation: Same error
- First attachment in the new conversation: Rejected
This is particularly important because Microsoft documentation describes attachments as conversation-scoped input, so a completely new conversation immediately inheriting the same exhausted state does not appear consistent with the expected attachment behavior. Attach files to a conversation (Microsoft Copilot) [learn.microsoft.com]
I previously raised this issue through Microsoft Q&A. The response also indicated that because the first file in a new conversation is rejected, this does not appear to be expected behavior and could indicate stale or incorrectly associated attachment state on the server side. Persistent 20-file upload limit in Microsoft Teams after reinstalling published Copilot Studio agent and starting a new conversation [learn.microsoft.com]
Assistance Required from Microsoft
Based on the tests above, I would appreciate Microsoft investigating the Microsoft Teams published-channel attachment/session state for this specific Agent.
Please help us determine:
Why does a completely new Microsoft Teams conversation inherit the 20-file attachment limitation?
Where is the 20-file attachment counter maintained for a published Copilot Studio Agent in Microsoft Teams?
Is there stale or incorrectly associated server-side attachment/session state associated with this Agent or its Microsoft Teams channel?
Can Microsoft clear or reset the server-side attachment state/counter without deleting or rebuilding the Agent?
Is Microsoft Teams reusing the same backend conversation/session ID even when a user starts a new conversation?
Is there a supported administrative function, Microsoft Graph API, Power Platform API, Power Automate connector, or retention mechanism that allows old attachment states to be cleared?
Can the attachment limit be increased, disabled, or configured with a rolling retention mechanism for this type of Agent?
If this is specific to the Microsoft Teams channel, can the Teams channel/backend state be reset or re-provisioned while preserving the existing Agent, instructions, skills, knowledge sources, tools, and configuration?
Business Requirement
Rebuilding the Agent or permanently changing our workflow is not an acceptable long-term workaround.
The Agent itself has been verified to work correctly in Copilot Studio. Therefore, our preferred resolution is:
Restore normal file-upload capability for the existing Project Assistant Agent in Microsoft Teams without rebuilding the Agent or changing the established business workflow.
If the current behavior is caused by stale server-side state, please reset the relevant attachment/session state or advise us of the supported method to do so.
If this cannot be handled through standard Microsoft 365 or Power Platform administration, please escalate this case to the Copilot Studio / Microsoft Teams integration engineering team for investigation.
I can provide the following information upon request:
- Copilot Studio Environment ID
- Agent ID
- Microsoft Teams version
- Publishing/channel configuration
- Exact timestamps of failed uploads
- Screenshots of the 20-file error
- Screenshot showing successful processing of the same transcript in Copilot Studio
- Diagnostic logs or correlation IDs
Please let me know what diagnostic information you require to investigate the server-side attachment/session state.
Thank you,