SharePoint “Create File” connector returning null values across all agents (previously working)

(2) Share

Report

Posted on by VS-26030531-0

Hi everyone,

I’m facing an issue with the SharePoint “Create File” connector in Copilot Studio, and I’m hoping someone can help or confirm if this is a known issue.

🔹 Problem

The Create File action is returning null values, and the files are not getting created in SharePoint — even though:

Attachments are correctly captured (System.Activity.Attachments)

I can loop through files and see:
- correct file names
- content is present (Has content = Yes)

All configurations (site, folder path, file name, file content) are correctly set

🔹 Additional Context

I have built few agents earlier using the same SharePoint connector, and they worked perfectly

A few of those solutions are already going to PROD

Now this issue is happening across all agents, including previously working ones

No changes were made to:
- connector configuration
- permissions
- flow logic

🔹 Observed Behavior

Loop executes successfully

File metadata is available

But Create File returns null / no output

No visible error, just no file created in SharePoint

🔹 Important Note

This same issue had occurred earlier once, and it resolved automatically after ~24 hours (possibly a platform issue)

However, this time:

It has persisted longer

Still not resolved

🔹 What I’ve Tried

Verified all input mappings (Name & Content)

Rechecked SharePoint connection and permissions

Tested with simpler paths/folders

Rebuilt parts of the flow

Tested across multiple agents

🔹 Questions

Has anyone experienced similar behavior with SharePoint connectors in Copilot Studio?

Is this a known platform issue or outage?

Any recommended troubleshooting steps beyond configuration checks?

Categories:

General topics

Calling actions from Copilot Studio

I have the same question (0)

All responses (5)

Answers (0)

Sort by

Suggested answer

11manish 2,467 on at

Like (1)

Report
Copy link

Link copied!

Based on the behavior described, this appears to be a potential SharePoint connector or Copilot Studio backend issue rather than a configuration problem.

The attachment data is being retrieved correctly, the loop executes successfully, and the Create File action returns null across multiple agents—including

previously functioning solutions.

Since the issue has occurred before and resolved automatically, it may be related to a platform degradation or connector regression.

I would recommend validating the same operation through Power Automate, checking Copilot Studio execution logs for connector responses, and reviewing

Power Platform/Microsoft 365 service health.

If the issue persists, opening a Microsoft support ticket with agent IDs, environment details, and run history logs would be advisable.

Was this reply helpful? Yes No
VS-26030531-0 16 on at

Like (1)

Report
Copy link

Link copied!

Thanks for the suggestion @11manish

I tested the same scenario using Power Automate, and it works fine there, files are created successfully in SharePoint. However, when using the same logic inside Copilot Studio (Create File tool), it consistently returns null and does not create files.

I can't be able to check execution logs, since it's just blank. I will connect with Security Team in my org and then raise a support ticket if the issue persists.

Appreciate the guidance!

Was this reply helpful? Yes No
Suggested answer

Valantis 5,579 on at

Like (2)

Report
Copy link

Link copied!

Hi @VS-26030531-0,

The fact that Power Automate works fine but the direct Copilot Studio connector returns null is the key clue. This is a confirmed known issue with how file content is passed directly to connectors in Copilot Studio.

Microsoft docs and community investigation confirm that passing file content directly to connectors via the Create File action in Copilot Studio can return null because the file content variable handling in the agent topic differs from how Power Automate processes it. The file metadata is available but the actual content byte stream doesn't always pass through correctly to the direct connector action.

The confirmed workaround is to use an Agent Flow instead of a direct connector action. Since Power Automate already works for you, route the file through an Agent Flow:

1. In the topic, after capturing the attachment, pass the file content and name to an Agent Flow
2. In the Agent Flow, use the SharePoint Create File action (same as you tested in Power Automate)
3. The file content passed as a File type input to the Agent Flow preserves the byte stream correctly

Microsoft docs confirm this pattern: use the Set variable value node to retrieve the file record with Name, ContentType, and Content, then pass that to an Agent Flow as a File type parameter.

Ref: https://learn.microsoft.com/en-us/microsoft-copilot-studio/guidance/pass-files-to-connectors

Best regards,

Valantis

✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

🏷️ For follow-ups @Valantis.

📝 https://valantisond365.com/

💼 LinkedIn

▶️ YouTube

Was this reply helpful? Yes No
Nivedipa-MSFT Microsoft Employee on at

Like (1)

Report
Copy link

Link copied!

Hello VS-26030531-0 ,
If SharePoint "Create file" is returning a silent null across every agent — even ones that previously worked — it is usually one of these issues:

1. Connector / service-side regression. This action has had intermittent backend problems where it returns HTTP 200 with an empty body and no file is written. Your prior 24-hour self-heal points to exactly this. Check Power Platform admin → Health → Service health and M365 admin → Service health for SharePoint / Power Automate in your region. If nothing was posted, file a support ticket with a recent run ID.

2. Stale SharePoint connection. A token rotation / MFA prompt can make the connection appear "Connected" while still returning null. Go to Power Automate → Connections and re-authenticate the SharePoint connection even if it shows green. This resolves most "worked yesterday, null today" cases.

3. Variable binding looks fine but isn't. Re-select the site and library from the dropdowns (don't type paths), bind Attachment.Content directly from the variable picker (not through an expression), and make sure the file name includes the extension.

Highest-value step: open the Power Automate run history for the flow Copilot Studio invokes → click the failed Create file action → inspect raw inputs/outputs. The actual SharePoint error code (-2147024891 access denied, 429 throttling, etc.) is there. Copilot Studio swallows it and shows null.

Quickest unblock: re-authenticate the SharePoint connection, then check the run-history raw output. If a standalone test in Power Automate with hardcoded inputs also returns null → service-side, file a ticket. If it works standalone → the issue is in how Copilot Studio passes the variables.

If you found the information above helpful, I would appreciate it if you could share your feedback.
Your feedback is important to us. Please rate us:
🤩 Excellent 🙂 Good 😐 Average 🙁 Needs Improvement 😠 Poor

Was this reply helpful? Yes No
Suggested answer

Haque 3,286 on at

Like (2)

Report
Copy link

Link copied!

Hi @VS-26030531-0,

Seems like you have narrowed down the problems - good news is it's workign from Power Automate!

I think everyone has covered with their points - I would suggest in the first place, please check Microsoft 365 Service Health for any ongoing SharePoint or Power Automate connector issues - as previously happened this and was resolved automatically in 24 hours.

Second - can you please do a refresh of all connections, delete and recreate (Re-authenticate or recreate the SharePoint connection in Copilot Studio).

Third - Please try to remember what changes you made last for tweaking - if you can rollback that. Alos, what about the file size and format? Are you trying with the same file that you succeeded with PowerAutomate? If not, please do so. One thing to remember, confirm the file content passed to the "Create File" tool in Copilot Studio is a base64-encoded string. If not, convert it explicitly before passing.

Fourth - Please test with a simple static base64 string file content in Copilot Studio to isolate if the issue is with dynamic content.

and lastly, please add debugging or logging steps in the agent flow to output the exact content value just before the "Create File" action.

I am sure some clues I tried to give. If these clues help to resolve the issue brought you by here, please don't forget to check the box Does this answer your question? At the same time, I am pretty sure you have liked the response!

Was this reply helpful? Yes No