Skip to main content
Prophecy supports integration with Microsoft SharePoint, allowing you to read from and write to SharePoint document libraries as part of your data pipelines. This connection enables you to work directly with files stored in SharePoint for processing, transformation, and reporting.

Prerequisites

To connect Prophecy to SharePoint, your Microsoft administrator must first register Prophecy as an application in Microsoft Entra ID. This registration provides the Client ID and Client Secret needed to authenticate Prophecy with Microsoft APIs. As part of the setup, the registered app must be granted the Sites.Selected application permission, then explicitly given access to each SharePoint site the connection will use. Sites.Selected scopes access to specific site collections only, rather than granting tenant-wide access to every site.
Sites.Selected requires additional setup beyond adding the permission in Entra ID — you must also grant access to each site individually via Microsoft Graph API. See Grant service principal access to SharePoint sites for more details.
Learn more in Permissions for OneDrive and SharePoint API.

Feature support

The table below outlines whether the connection supports certain Prophecy features.

Limitations

Prophecy can only access files stored in the document library of your SharePoint site. Make sure any files you want to import are placed there. Prophecy can only access sites that have been explicitly granted to it via Sites.Selected. If a connection can’t reach a site, confirm the site has been granted access — see Grant service principal access to SharePoint sites.

Connection parameters

To create a connection with SharePoint, enter the following parameters. You can find the Tenant ID, Client ID, and Client Secret in your Microsoft Entra app.
The site entered here must match a site that has been granted access via Sites.Selected. See Grant service principal access to SharePoint sites.

Sharing connections within teams

Connections in Prophecy are stored in fabrics, which are assigned to specific teams. Once you add a SharePoint connection to a fabric, all team members who have access to the fabric can use the connection in their projects. No additional authentication is required: team members inherit access from the stored connection credentials.
Be mindful of the access level granted by the stored credentials. Anyone on the team will have the same permissions, including access to sensitive data if applicable.To manage this securely, consider creating a dedicated fabric and team for high-sensitivity connections. This way, only approved users have access to those credentials.