Documentation Index
Fetch the complete documentation index at: https://docs.wolfia.com/llms.txt
Use this file to discover all available pages before exploring further.
This guide covers the Service Account (client credentials) setup for SharePoint integration. This method allows Wolfia to access SharePoint data without user interaction and is the recommended approach for production environments.
Overview
The SharePoint integration allows Wolfia to sync documents and files from your SharePoint Online environment. Using client credentials authentication, Wolfia can access your SharePoint site collections to provide rich context when responding to security questionnaires and RFPs.What we sync
- Documents – Files stored in SharePoint document libraries (read-only)
- Site content – Pages and content from SharePoint sites (read-only)
Prerequisites
Before setting up the integration, you’ll need:- Azure account with admin access to Azure Active Directory
- SharePoint Online subscription in your Microsoft 365 tenant
- Ability to grant admin consent for application permissions
Setup instructions
Step 1: Register a new application
First, we’ll create an Azure AD app registration for the Wolfia integration.- Sign in to the Azure Portal
- Navigate to Azure Active Directory → App registrations
- Click + New registration
-
Fill in the registration form:
- Name:
Wolfia-SharePoint-Integration(or your preferred name) - Supported account types: Select Accounts in this organizational directory only (Single tenant)
- Redirect URI: Leave blank (not needed for client credentials)
- Name:
- Click Register
Step 2: Note your application IDs
After registration, you’ll land on the app’s Overview page. Copy these values — you’ll need them later:| Field | Description |
|---|---|
| Application (client) ID | Your Client ID |
| Directory (tenant) ID | Your Tenant ID |
Keep these values handy. You’ll need to provide them to Wolfia to complete the integration setup.
Step 3: Create a client secret
- In your app registration, go to Certificates & secrets in the left sidebar
- Click + New client secret
-
Fill in:
- Description:
Wolfia Integration Secret - Expires: Choose an appropriate expiration (24 months recommended)
- Description:
- Click Add
- Copy the Value immediately — it will only be shown once
| Field | What to copy |
|---|---|
| Value | This is your Client Secret |
Step 4: Configure API permissions
- Go to API permissions in the left sidebar
- Click + Add a permission
- Select Microsoft Graph
- Select Application permissions (not Delegated permissions)
-
Search and select these permissions:
Sites.Read.All– Read items in all site collectionsFiles.Read.All– Read all files in all site collections
- Click Add permissions
| API | Permission | Type |
|---|---|---|
| Microsoft Graph | Sites.Read.All | Application |
| Microsoft Graph | Files.Read.All | Application |
Step 5: Grant admin consent
Application permissions require admin consent to activate:- Still on the API permissions page
- Click Grant admin consent for [Your Organization]
- Click Yes to confirm
- Verify all permissions show a green checkmark under “Status”
If you don’t see the “Grant admin consent” button, you may need to contact your Azure AD administrator to grant consent on your behalf.
Step 6: Provide credentials to Wolfia
You now have three values needed for the integration:| Credential | Where to find |
|---|---|
| Tenant ID | App registration → Overview → Directory (tenant) ID |
| Client ID | App registration → Overview → Application (client) ID |
| Client Secret | The value you copied in Step 3 |
What happens after setup
Once connected, Wolfia will:- Begin syncing documents from your SharePoint site collections
- Index content to provide context for questionnaire responses
- Automatically sync new and updated documents on a regular schedule
Security considerations
- The integration uses read-only permissions — Wolfia cannot modify or delete your SharePoint content
- All data transmission is encrypted using HTTPS
- Client credentials are stored securely and never exposed
Troubleshooting
Common issues
“Insufficient privileges” error- Ensure admin consent was granted (Step 5)
- Verify the green checkmarks appear next to all permissions in API permissions
- Client secrets can only be viewed once when created
- If lost, create a new secret in Certificates & secrets and update the integration
- Verify you’re using the correct Tenant ID
- Ensure the app registration exists in your Azure AD directory
- Verify the app has
Sites.Read.AllandFiles.Read.Allpermissions - Ensure permissions are of type “Application” not “Delegated”
- Confirm admin consent was granted

