Forum Discussion
Store Teams-Uploaded Files in Azure Blob Storage Instead of OneDrive for Copilot Studio
I have developed a custom agent in Copilot Studio and connected it to Microsoft Teams as a channel. When a user uploads a file via Teams during a conversation with the agent, the file is automatically stored in the user’s personal OneDrive.
This creates a limitation because the file content is not directly accessible to the Copilot Studio agent without going through OneDrive APIs, creating dependency on the individual user’s storage. I want these uploaded files to be stored directly in Azure Blob Storage or another centralized storage so the agent can process them without relying on a user’s personal OneDrive. Is there any way to configure this in Teams, Copilot Studio, or Power Automate?
1 Reply
Unfortunately, Teams itself doesn’t let you change where chat-uploaded files are stored — in 1:1 or group chats, they’ll always go into the sender’s OneDrive, and in channels, they go to SharePoint. Copilot Studio just gets a reference to that file, so there’s no setting to make it land straight in Blob Storage. If you want them centralized in Azure Blob, you’ll need to catch them after they’re uploaded and move them. Easiest way is with Power Automate: trigger on “new file in OneDrive/SharePoint,” then push it into Blob Storage and hand the Blob URL back to the bot. If you want it near real-time, you can have your bot or a background service listen to Teams messages via Microsoft Graph, download the file, and push it to Blob directly. Cleanest long-term option is to skip Teams’ native upload altogether and use your own upload control that writes straight to Blob with a SAS token — but that’s a bit more dev work.
