Additional file-related features and issues within Microsoft Teams for business
For a standard-harness agent, add and invoke a Clear variable values node configured for Conversation history for the current session; if Teams still rejects the first attachment afterward, escalate through Power Platform support because public documentation provides no customer-accessible method guaranteed to reset the specific 20-file attachment counter.
1. Apply the documented conversation-history reset
First verify that the agent uses the standard harness, because the relevant Teams lifecycle guidance applies only to that harness. You also need edit and publish access to the agent.
Teams reuses the same conversation ID for every session between a user and an agent. Consequently, Conversation Start runs only the first time the user adds the agent—even after removal and reinstallation. The default Reset Conversation system topic clears variables and loads the latest version, but it does not clear conversation history unless explicitly configured to do so.^1^
In Copilot Studio:
- Open the agent and either:
- Edit its Reset Conversation system topic, or
- Create a dedicated topic triggered by a phrase such as
reset attachment session.
- Add Clear variable values.
- Select Conversation history for the current session.
- End the conversation and mark the session resolved.
- Save and publish the agent.
- In Teams, invoke that topic, wait for it to complete, and then upload one small supported file.
Microsoft specifically documents this history-clear option for accumulated file content: previously uploaded files continue to contribute to the content processed in a conversation, and clearing conversation history releases that accumulated content.^2^
Treat this as the supported first remediation, not as a guaranteed reset of the hard 20-file counter. The documentation does not establish that planner conversation history and the attachment quota use the same backend state.
As an additional standard-harness test, enter:
/debug clearstate
The Teams deployment guidance describes this as a complete conversation-state reset that also removes cached connector information, reauthenticates connectors, and loads the latest agent version. It does not specifically state that the command deletes retained attachments or resets their counter.^3^
2. Escalate if the first attachment remains blocked
Attachments are retained with their conversation for 28 days after its last activity. They are then deleted and can no longer be referenced.^4^ Waiting for retention expiry is not an appropriate operational remedy, and the current public documentation identifies no Microsoft Graph, Power Automate, Power Platform admin, or tenant-retention operation for immediately clearing this particular attachment counter.
An eligible Copilot Studio/Power Platform administrator should open a service request:
- Sign in to Power Platform admin center.
- Select Support → Support requests.
- Select Get support.
- Identify the product as Microsoft Copilot Studio, not Dynamics 365 Customer Service.
- Request escalation to the Copilot Studio–Microsoft Teams channel engineering team.
- Grant advanced diagnostic consent if requested; Microsoft cannot run tenant/environment diagnostics without the required consent.^5^
Creating a support request can require an active support plan and an appropriate administrator role.^6^
Include:
- Environment ID and agent ID
- Confirmation that the agent uses the standard harness
- Teams desktop/web/mobile version and channel configuration
- User/time zone and exact UTC timestamps for at least two failures
- The Teams conversation ID, reference/correlation ID, and full error text
- Whether the same user fails in multiple Teams clients
- Whether another user is affected
- Screenshots with organizational and personal information redacted
- The successful Copilot Studio test result using the same file
- Confirmation that reinstalling, deleting visible history, starting a new chat, and changing file type already failed
- Confirmation that the published history-clear topic and
/debug clearstatewere tested, plus their outcomes - A request to determine whether the rejected “new” Teams chat retained the same backend conversation ID and to clear or repair the attachment state without rebuilding the agent
Conversation IDs and failure timestamps are the key identifiers Microsoft uses to correlate persistent runtime failures with service telemetry.^7^
Do not post IDs, snapshots, or diagnostic archives publicly. Copilot Studio snapshots can contain agent content and other sensitive information; provide them only through the private support case if requested.^8^
References
- Use system topics
- Allow file input from users - Microsoft Copilot Studio
- Deploy agents in Microsoft Teams
- Attach files to a conversation (Microsoft Copilot)
- Get support in the Power Platform admin center
- Find support and give feedback for Copilot Studio
- Error codes reference for agents (Microsoft Copilot)
- Test your agent