OOTB SharePoint connector support for SP Server SE on-prem via Data Gateway — Copilot Studio agent

(1) Share

Report

Posted on by CU10060508-0

Hi community,

I am building a Copilot Studio agent backed by Power Automate cloud flows that need to interact with SharePoint Server Subscription Edition (SE) running on-premises, connected via the On-Premises Data Gateway using the standard OOTB Power Platform SharePoint connector. I am aware that Microsoft's official connector documentation lists supported actions for SharePoint 2013, 2016, and 2019 on-premises — but SharePoint Server SE is not explicitly listed as a tested version. Since SE is the architectural successor to SP 2019, I am treating the SP 2019 support matrix as the closest applicable reference, but I want to validate this assumption with the community before committing to a full build.

Has anyone successfully used the OOTB Power Platform SharePoint connector (via gateway) against SharePoint Server SE specifically? Any known regressions or compatibility issues vs SP 2019?
Is "Update file properties" (writing to custom site columns) supported via the OOTB connector on-prem, or must this go through the HTTP Request action with a REST MERGE call?
Does the "Send an HTTP request to SharePoint" action handle request digest / OAuth token management automatically when pointed at an on-premises SP SE site, or does the flow need to fetch a digest token explicitly via POST /_api/contextinfo?
Are there any known issues with large file reads (PDFs 10–50 MB) through the gateway using "Get file content"? We need to pass these to AI Builder for document processing.
Any gotchas with the When a file is created or modified (properties only) trigger reliability on SP SE on-prem — specifically for an overnight batch scenario where many files are uploaded in a short window?

Categories:

Autonomous agents

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Suggested answer

Valantis 6,290 on at

Like (1)

Report
Copy link

Link copied!

Hi @CU10060508-0,

Answers to your five questions based on Microsoft docs and confirmed community experience.

1. SP SE support: Microsoft docs explicitly list only SharePoint 2016 and 2019 as supported on-prem versions. SE is not listed. Since SE is architecturally the successor to 2019 with the same REST API foundation, most actions work in practice, but it is formally unsupported. Treat your SP 2019 reference as valid but expect some actions to require manual configuration (library names entered manually rather than discovered via dropdown).

2. Update file properties: confirmed available via the OOTB connector. Microsoft docs note: "Updates the properties stored in columns in a library for the item specified by the item id." For on-prem via gateway, the library name may need to be entered manually. No confirmed requirement for a raw HTTP MERGE call unless you need to update fields the connector doesn't expose.

3. Send HTTP request to SharePoint on-prem: the connector handles credentials via the gateway connection, but request digest management for on-prem is NOT automatic the way it is for SharePoint Online. For write operations against on-prem REST endpoints you should explicitly fetch the digest via POST /_api/contextinfo and pass X-RequestDigest in your headers. Don't assume it's handled.

4. Large file reads (10-50MB): the connector docs confirm a 90MB attachment limit. However for large files via Get file content through the gateway, expect timeouts and reliability issues. The gateway has its own timeout limits and large binary transfers can fail intermittently. Passing 50MB PDFs to AI Builder through this path is risky test thoroughly before committing.

5. Trigger reliability for batch uploads: on-prem triggers are polling-based (typically every 2-5 minutes), not event-driven. For an overnight batch scenario with many files in a short window, missed triggers are a confirmed known issue. Use a scheduled flow that queries the library for files modified since the last run as a more reliable alternative.

Ref: https://learn.microsoft.com/en-us/connectors/sharepoint/

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
Suggested answer

11manish 2,837 on at

Like (0)

Report
Copy link

Link copied!
Yes, many organizations have successfully used the standard SharePoint connector through the On-Premises Data Gateway against SharePoint SE because SE is

the direct successor of SharePoint 2019 and largely maintains API compatibility.

However:

SharePoint SE is not always explicitly listed in connector documentation.

Some actions and triggers may not be officially certified/tested.

You should perform a Proof of Concept (POC) before committing to production.

our assumption that SharePoint Server Subscription Edition behaves similarly to SharePoint 2019 for Power Platform gateway-based integrations is generally

sound and aligns with how most organizations are implementing it today. The areas that deserve the most validation during your POC are large-file throughput

(10–50 MB PDFs), trigger reliability under burst uploads, and complex metadata updates. For a production-grade Copilot Studio + AI Builder solution,

I would favor a scheduled ingestion pattern with explicit processing status tracking rather than relying exclusively on the When a file is created or modified trigger.

This approach is typically more resilient and scalable for enterprise document-processing workloads.

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

Like (0)

Report
Copy link

Link copied!
1) SharePoint Server SE compatibility

Not officially listed yet, but in practice it behaves like SharePoint 2019

OOTB SharePoint connector works fine via gateway in most scenarios

No SE-specific issues seen so far

2) “Update file properties” (custom columns)

Yes, supported via OOTB connector on-prem

Works for standard metadata updates including custom columns

Use HTTP (MERGE) only for advanced fields or edge cases

3) “Send an HTTP request to SharePoint”

No manual /_api/contextinfo needed

Request digest/auth handled automatically by connector + gateway

REST calls work as-is (GET/POST/MERGE)

4) Large file handling (10–50 MB PDFs)

Generally works via “Get file content”

Limits depend more on Power Automate + gateway + AI Builder than SharePoint SE

Watch for timeouts under heavy volume

5) “When a file is created or modified (properties only)”

Works, but it’s polling-based

Can lag or batch-deliver under high load (overnight uploads)

For reliability at scale, prefer scheduled polling/delta checks over triggers

Was this reply helpful? Yes No