Skip to content
Connection Guide

Connect Microsoft SharePoint Without Breaking the Audit Trail

Use this guide to connect Microsoft SharePoint or confirm the export-based path that fits your environment. Aurora keeps source, timestamps, ownership, and collection history attached so the first run becomes reusable proof instead of one-off setup work.

Connector Summary
Connection typeDirect connection
CategoryEvidence
Checklist4 steps
Want help with rollout?
We'll confirm what can be automated, what stays export-based, and how to keep the first evidence record clean.

First-Run Checklist

Use this sequence to connect Microsoft SharePoint and make sure the first collection lands cleanly.

  1. 1
    Create a Microsoft Entra application and grant Sites.Read.All and Files.Read.All application permissions on Microsoft Graph.
  2. 2
    Store base_url, authority_host, tenant_id, client_id, client_secret, site_hostname, and site_path in Aurora.
  3. 3
    Scope the connection to one sanctioned SharePoint Online site per Aurora connection and validate site lookup, drive enumeration, and content download before enabling schedules.
  4. 4
    Treat selected-site permissions as a hardening variant, not the default onboarding contract for this runtime lane.

Credentials and Secrets

The keys, secrets, or tokens Aurora uses to authenticate and collect proof.

client_secret

Recommended Access

Aurora only asks for the minimum read access needed for collection and checks.

Access requirements depend on the collection mode and scope you choose.