Microsoft SharePoint Audit Logs
Collects SharePoint audit events covering file access, sharing, and site interactions.
This input also captures OneDrive for Business file activity (uploads, downloads, sharing, and access). Microsoft 365 records OneDrive events under the SharePoint workload (RecordType 7), so there is no separate OneDrive input — use this connector for OneDrive file-access logs.
Sync Type: Incremental
Requirements
Before setting up the input you need to:
-
In Microsoft Purview, turn auditing on.
-
Register an Active Directory (Entra) application:
- Supported account types: Accounts in this organizational directory only.
- Certificates & secrets: create a new client secret and copy its Value immediately — it cannot be retrieved after you leave the page. You will need it to configure the Monad connector.
-
Grant the application access to the Office 365 Management APIs:
- Under API permissions → Add a permission → APIs my organization uses, search for Office 365 Management APIs (this is a different API from Microsoft Graph).
- Add
ActivityFeed.Readas an Application permission. Monad authenticates app-to-app (client credentials), so the permission must be of type Application, not Delegated — a Delegated permission is not present in the token Monad receives, and the connection test will fail. - Click Grant admin consent for <your tenant>. The
ActivityFeed.Readrow must then show a green Granted status — adding the permission alone is not enough.
ActivityFeed.ReadDlpis only needed for the DLP Events input. It is not required for SharePoint Audit Logs.
The input starts the Office 365 Management Activity subscription for its content type itself, so you don't need to start it. Microsoft can take up to 12 hours to make content available after a subscription is first started.
Where to find each value
| Field | Where in the Entra app registration |
|---|---|
| Tenant ID | Overview → Directory (tenant) ID (a GUID) |
| Client ID | Overview → Application (client) ID (a GUID) |
| Client Secret | Certificates & secrets → Client secrets → Value (copied at creation — this is the secret's Value, not its Secret ID) |
Common mistake: the Client ID and the Client Secret Value are easy to swap. The Client ID is always a GUID (e.g.
a1b2c3d4-…); a secret Value is a longer opaque string (often containing~or.). Entering the secret Value in the Client ID field produces anAADSTS700016: Application with identifier '…' was not found in the directoryerror.
Backfill and sync window
- The first sync starts from now — no historical records are fetched — unless you set a Backfill Start Time.
- If you set a Backfill Start Time, the sync fetches from that time forward, but no earlier than 7 days in the past: the Office 365 Management Activity API retains only ~7 days of content, so older start times are clamped to 7 days ago.
- Each sync then continues from the newest content it has collected.
Configuration
Settings
| Setting | Type | Required | Default | Description |
|---|---|---|---|---|
tenant_id | string | Yes | - | The tenant ID of the Entra ID directory associated with your Azure subscription. |
use_synthetic_data | bool | No | false | Generate synthetic data for testing, instead of connecting to a real data source. Defaults to an hourly cron schedule for cron-based inputs. |
backfill_start_time | date | No | - | The date to start fetching data from. If not specified, no past records will be fetched. |
rate_limit | object | No | - | Maximum outbound source-API request rate. A blank or zero value falls back to the connector's default rate-limiting behavior. Maximum 10 requests per second. See API Rate Limiting for the field format. |
Secrets
| Secret | Type | Required | Description |
|---|---|---|---|
client_id | secret | Yes | The client ID of the Entra ID application |
client_secret | secret | Yes | The client secret of the Entra ID application |
Troubleshooting
| Error | Cause | Fix |
|---|---|---|
AADSTS700016: Application with identifier '…' was not found in the directory | The Client ID is incorrect — often the Client Secret Value was entered in the Client ID field, or the app is registered in a different tenant. | Confirm the Client ID is the Application (client) ID GUID from the app's Overview page, and that the Tenant ID matches the tenant where the app is registered. |
401 AF10001: The permission set () sent in the request does not include the expected permission. | The token carries no app roles: ActivityFeed.Read is missing, was added as a Delegated permission instead of Application, or admin consent was not granted. | On the app's API permissions, ensure ActivityFeed.Read under Office 365 Management APIs is of type Application and shows a green Granted admin-consent status. Allow a few minutes for the change to propagate, then re-run the connection test. |
Related Articles
Sync frequency
By default this input polls approximately every 10 seconds, with each sync beginning after the previous one completes. A cron schedule configured on the pipeline overrides this cadence. See Input Sync Frequency for details.