Microsoft SharePoint
Connect Microsoft SharePoint to your company operations. Review required fields, credential setup and how this connector works in Zild.
Connect Microsoft SharePoint to your company operations.
Where to configure
Open Zild Admin → Integrations → Connectors, find the provider and use Configure or Edit. Enter the data from this guide, enable the connector for the workflow and save.
Your company credentials
Customers must obtain and configure their own API keys or the authentication method required by this connector. The Zild subscription is based on company size; external service usage is billed separately by the respective provider. You do not need to configure connectors your operation does not use.
Required fields
These requirements are the data needed by the workflow using the connector. Generic saving may accept empty fields that are only required when an operation runs. Saving does not confirm that the provider accepts the credential.
| Field | Workflow requirement |
|---|---|
OAuth | Delegated Microsoft 365 account connection; no manual API key required. |
How to obtain credentials
- Save the connector and click Connect Microsoft 365 account.
- Sign in with the work account to use and authorize the requested permissions: Files.Read.All, Files.ReadWrite.All, Sites.Read.All and offline_access.
- If consent is blocked, ask your Microsoft 365 administrator to approve it. Reconnect after consent is revoked.
How it works in Zild
The administrator configures the Entra app and its secret on the server. Zild refreshes delegated tokens; the user remains limited to authorized resources.
How to verify the configuration
After saving, use the matching workflow (query, agent, call or processing) to verify access. If it fails, check the credential, permissions and selected provider resource. For limited or legacy types, confirm availability with your administrator before use.
When editing, Zild displays protected credentials as asterisks. Preserve the masked value to keep the current credential or paste a new credential to replace it.
Delegated access scope
The current connector requests Files.Read.All, Files.ReadWrite.All, Sites.Read.All and offline_access. The connected account must have access to documents used by the workflow. Choosing a pilot library does not by itself restrict consent to that library. Review the account, its permissions and enabled agent tools with administrators before connecting project documents.
Microsoft offers Selected permissions with explicit resource assignments. That is not the consent flow implemented by this connector. Do not replace scopes on your own and assume compatibility: a deployment with this requirement needs technical validation.
Test the library before project files
Prepare an authorized test library or folder and obtain its driveId and folder identifier with administrators. Save and enable the connector, complete Connect Microsoft 365 account and verify the connected account. Link the connector to the agent tool. Start with ListItems; id=root represents the drive root. Check returned item names, identifiers and locations.
Next, read a known small file. ReadFile returns contentBase64 and contentType and limits the response to 2 MB in this implementation. It transports content; it does not imply OCR, geometric interpretation or native reading of arbitrary DWG/SKP files. For engineering, begin with authorized structured exports and confirm the format-processing stage. A large project file failing is not proof of a failed login.
Separate reading, writing and monitoring
Enable WriteFile only when the process needs to save an output and approval is defined. The operation takes a folder, filename and contentBase64. Use a unique test filename and verify the resulting file in the expected folder before expanding. After a timeout, check the destination before retrying. Successful listing and reading do not validate writing, classification or technical document approval.
The catalog includes Subscribe and RenewSubscription for library changes. Subscriptions require administrator configuration of DriveId, NotificationUrl and secret state; connecting an account does not automatically enable continuous synchronization. Verify notification receipt, processing and renewal in the deployed environment. If access stops, distinguish revoked consent, account permissions, incorrect identifiers and response limits.
See also: Engineering extraction and evaluation guide.
Microsoft Learn: Graph permissions · Selected permissions. Checked on 28/10/2026.