Microsoft SharePoint connector

Use your Microsoft SharePoint data for reporting, automation and AI.

Data Panda brings your SharePoint sites, libraries, lists and permissions together with the data from the rest of your business. From one place, we turn it into dashboards, automations, AI workflows and custom apps your IT, compliance and operations teams use every day.

About Microsoft SharePoint

The Microsoft 365 layer that holds the documents.

SharePoint shipped in 2001 as Microsoft's intranet, document-management and team-collaboration platform, and it now sits at the centre of Microsoft 365 alongside Teams, OneDrive and Outlook. Microsoft has reported more than 250 million users on the platform across the M365 estate, with sites covering classic intranets, communication portals, project workspaces, departmental document libraries, and the lightweight lists that act as the database behind countless Power Apps and Power Automate flows.

For most M365 shops SharePoint is no longer a thing people open on its own. Every Microsoft Teams team creates a SharePoint site under the hood for its files. OneDrive for Business is a per-user SharePoint site. Communication sites carry the company intranet. Document libraries hold contracts, policies, drawings and engineering specs. And lists hold the project trackers, request queues and asset registers that small Power Automate flows tick through every night. The Microsoft Graph SharePoint surface exposes sites, lists, listItems, drives, items, columns, contentTypes, pages and permissions. Pulling that into a warehouse is how IT, compliance and the records-management lead see the whole estate at once, instead of clicking through admin centres and tenant search.

What your Microsoft SharePoint data is for

What you get once Microsoft SharePoint is connected.

Site and library reporting

Sites, libraries, lists, permissions and external shares in one place, instead of an admin-centre export nobody re-runs.

Active versus dormant sites per business unit, with the Teams team that created each one
External-share inventory per site, by recipient domain and link type
Library and list growth, with the largest folders and the oldest content in each

Lifecycle and governance automation

Let site and list metadata trigger the housekeeping the M365 admin would otherwise do by hand in PowerShell.

Archive proposals for sites with no edits or visits in 180 days, attached to the team owner
External-share reviews scheduled per site and per recipient domain
Power Automate flow inventory cross-checked against the user that owns the connection

AI workflows

Put your real SharePoint content behind AI that respects the permission model, instead of a generic assistant.

Internal search grounded in the SharePoint sites and libraries a user is allowed to see, with source links back to the document
Auto-classification of newly uploaded documents against your existing sensitivity labels
Long-document summarisation queued into the right reviewer's task list, with explicit retention scope

Custom apps on your data

Small internal tools on SharePoint sites, libraries and lists for people who do not live in the M365 admin centre.

Site-owner dashboard of external shares and stale content per site
List-driven workflow app that replaces a fragile Power Automate chain with a transparent queue
Records-management view of sites in scope for retention, with the responsible team owner

Use cases

Use cases we deliver with Microsoft SharePoint data.

A list of concrete reports, automations and AI features we have built on Microsoft SharePoint data. Pick the one that matches your situation.

Site sprawl overviewTotal sites, active versus dormant, per business unit and per creation source (Teams, manual, template).

Teams-created site mapSharePoint sites created by a Teams team, with last-edit date on the team's files.

External-share auditExternal sharing links per site, ranked by recipient domain, link type and last-access age.

Owner coverageSites with an active owner versus sites whose owner has left the tenant.

Library growthDocument library size, item count and growth per site, with the biggest folders called out.

List inventorySharePoint lists per site, with row count, last-edit date and the Power Automate flows watching them.

Power Automate auditFlows per site and per owner, with the trigger, run frequency and last-failure date.

Sensitivity vs sharingDocuments labelled confidential that have an active external sharing link, by site and recipient domain.

Retention scopeSites and libraries holding regulated content, by retention label and team owner.

Page and news activityModern pages and news posts published per intranet site, with view counts and last-edit author.

Permission inheritanceSites and libraries with broken permission inheritance, ranked by external-member exposure.

Real business questions

Answers you will finally get.

How many of our SharePoint sites are still being used?

Active versus dormant site counts per business unit, joined to the Teams team that created each site (most modern sites come from a Teams channel rather than a manual click). IT sees which sites still get edits, page views and uploads, and which ones are paying for storage and retention coverage without anyone opening them past the day they were spun up.

Where are external guests seeing our documents?

External sharing links per site and per recipient domain, with the file path, the link type (anyone, specific people, organisation) and the last-access date attached. Security and compliance see which suppliers, customers and ex-employees still have a way into which library, so the next access review starts with a list rather than a meeting and a tenant-wide search.

Which Power Automate flows are running on our SharePoint estate?

Flows per site and per owner, with the trigger (on item created, on schedule, on column change), the run frequency and the last-failure date. IT and the records-management lead see which lists are wired into a flow nobody documented, and which flows are silently failing because the user that owned the connection has left the tenant.

Value for everyone in the organisation

Where each function gets value.

For finance leaders

Contract libraries, signed quotes and policy documents reportable next to the deal or supplier record. Finance sees which contracts are missing the signed PDF or the renewal addendum on the canonical SharePoint site, instead of clicking through team folders before period close.

For sales leaders

Customer-facing collateral and proposals stored on account or deal sites joined to the CRM. Sales sees which prospects opened the proposal, which collaborators on their side engaged with the file, and which account sites were never set up against an open opportunity.

For operations

Tenant-wide site, library, list and flow inventory in one view. IT and records-management run lifecycle cleanup, owner reassignment, external-share reviews and Power Automate audits on data that refreshes with the rest of the warehouse, instead of on a one-off PowerShell export from last quarter.

Ideas

What you can automate with Microsoft SharePoint.

Pair with Microsoft Teams

Tie every SharePoint site back to its Teams team

Each Microsoft Teams team creates a SharePoint site for its files, and most modern sites in a tenant arrive that way rather than through a manual click. The pairing joins the SharePoint site id, owners and external-share inventory to the matching Teams team, channel list and last-message date, so IT sees which sites are still alive because the team is still alive, and which sites linger after the team that created them went quiet six months ago.

Pair with Salesforce

Wire Salesforce Files through to the right SharePoint site

Files attached to a Salesforce account, opportunity or case land in the matching SharePoint document library, and the SharePoint item id is written back on the Salesforce record. Sales reps stop maintaining a parallel Files attachment for the deck they already store on the account site, and the next person on the account opens the latest version from either side without guessing whether the canonical copy lives in Salesforce or on SharePoint.

Pair with HubSpot

Link SharePoint sales collateral to the HubSpot deal

Proposals, contracts and onboarding documents on the matching SharePoint site are linked to the HubSpot deal and contact, with last-modified and last-opened metadata kept in sync. Sales sees which prospects opened the proposal stored on the canonical account site, and which collaborators on the buyer side engaged with the file, instead of guessing from a generic email open rate.

Pair with Slack

Post SharePoint document activity to the right Slack channel

Uploads, new external shares and permission changes on flagged SharePoint libraries post a compact update in the Slack channel that owns the topic, with a deep link back to the document on SharePoint. Account and project teams stop relying on someone watching a library, and a lightweight audit trail sits next to the conversation where the work happens day to day.

Your existing tools

Your data lands in a warehouse. Your BI tools read from it.

You keep the reporting tool you already have. We connect it to the warehouse where your Microsoft SharePoint data lives.

Power BI Microsoft

Fabric Microsoft

Snowflake Data warehouse

BigQuery Google

Tableau Visualisation

Excel Sheets & pivots

Three steps

From Microsoft SharePoint to answers in three steps.

Connect securely

OAuth authentication. Read-only by default. We sign a DPA and your admin keeps the keys.

Land in your warehouse

Data flows into your warehouse on your schedule. Near real time or nightly, your call. You own the data.

Reporting, automation, AI

We build the first dashboard, workflow or AI feature with you, then hand over the keys. Or we stay on for ongoing delivery.

Two ways to work with us

Pick the track that fits how you work.

Track 01

Self-serve

We set up the foundation. Your team builds on top.

Microsoft SharePoint connector configured and running
Warehouse set up in your cloud account
Clean access for your Power BI, Fabric or Tableau team
Documentation on what's in the data model
Sync monitoring so you're warned before reports break

Best fit Teams that already have a BI analyst or data engineer and want to own the build.

Track 02

Done for you

We build the whole thing, end to end.

Everything in Self-serve
Dashboards built to the questions your team actually asks
Automations between your systems
AI workflows scoped to real tasks your team runs
Custom apps where a dashboard does not cut it
Ongoing delivery at a pace that fits your team

Best fit Teams without in-house BI or dev capacity. You tell us what you need and we deliver it.

Before you book

Frequently asked questions.

Who owns the data?

You do. It lands in your warehouse, on your cloud account. We don't resell or aggregate it. If you stop working with us, the warehouse stays yours and keeps running.

How fresh is the data?

Near real time for most operational systems. For heavier sources we schedule hourly or nightly. You pick based on what the reports need.

Do I need a warehouse already?

No. If you don't have one, we help you pick one and set it up as part of the first delivery. Common starting points are Snowflake, Microsoft Fabric, or a small Postgres start.

Where does SharePoint stop and OneDrive or Teams begin?

OneDrive for Business is a per-user SharePoint site under the hood, and every Microsoft Teams team creates a standard SharePoint site for its files. The connector uses Microsoft Graph sites, drives and items, so personal OneDrive content, Teams team files and the rest of your SharePoint estate land on the same shape. That's what makes the site-sprawl, Teams-created-site and OneDrive-versus-SharePoint-duplication reports possible: they all join on the same site and item identifiers.

Do SharePoint lists and the Power Automate flows on top of them come along?

Lists are first-class objects on the Graph SharePoint surface, and the connector pulls list definitions, columns, content types and list items so the project trackers, request queues and asset registers land in the warehouse next to the documents. The flows that watch those lists sit on the Power Platform side, and the connector reports the flow inventory (owner, trigger, run frequency, last failure) so the records-management lead sees the lists and the flows in one view rather than two consoles.

Do permissions and external-share links come through, or only the file metadata?

The Graph permissions endpoint exposes the role, the grantee and the link type for each item, plus the inheritance state at site and library level. The connector lands those alongside the documents, which is how the external-share audit, the sensitivity-versus-sharing report and the broken-permission-inheritance report work. Sharing and access show up as joinable rows next to the file, instead of as opaque toggles in the SharePoint admin centre.

GDPR-compliant

Data stays in the EU

You own the warehouse

A first deliverable live in four to six weeks.

We review your Microsoft SharePoint setup and the systems around it. Together we pick the first thing worth building.

Book a call See our other connectors