Microsoft SharePoint
Connecting DASH to Microsoft SharePoint drops a copy of each submitted certificate into a SharePoint document library through the Microsoft Graph API. You configure it as a Storage channel (CHANNEL-003) with the connector type SharePoint on the Material. Because DASH authenticates as an application (not as a person), your IT team must first register an app in Azure Active Directory and grant it access to the target site.
What you need from your Azure/IT administrator
Section titled “What you need from your Azure/IT administrator”| Detail | Notes |
|---|---|
| Tenant ID | Your Azure Active Directory tenant identifier |
| Client ID | The app registration’s application ID |
| Client secret | The app’s secret value (masked as •••••••• after saving) |
| Site URL | The SharePoint site that holds the library, for example https://contoso.sharepoint.com/sites/… |
| Library | The document library name, for example Documents |
| Folder path (optional) | A sub-path within the library for certificates |
The app registration needs Microsoft Graph permission to write files to the target site. Ask your admin to grant and consent to the appropriate application permissions.
Configure the SharePoint channel
Section titled “Configure the SharePoint channel”- Open the Material and go to the Data channels section.
- Add a channel with direction Storage and connector type SharePoint.
- Name it clearly, for example SharePoint archive.
- Enter the Tenant ID, Client ID and Client secret.
- Enter the site URL and the library name, plus a folder path if you use one.
- Save the channel.
Test the connection
Section titled “Test the connection”Use Test connection. DASH authenticates and checks the site and library:
- Pass — the site and library are reachable with the supplied app credentials.
- Fail — “Missing SharePoint tenant ID, client ID, or client secret.” means a field is blank; “SharePoint connection failed — check credentials and site URL.” means the credentials, permissions or site URL are wrong.
Common pitfalls
Section titled “Common pitfalls”- App permissions not consented. Authentication can succeed while uploads still fail if the app lacks write access to the site. Have your admin confirm the Graph permissions are granted and admin-consented.
- Expired client secret. Azure secrets have an expiry date. If a channel that used to work starts failing, the secret has likely expired — get a new one and update the channel.
- Wrong site URL or library name. Copy these exactly; a mistyped site path fails the site or library check.
- Secret shows as
••••••••when editing. Expected — leave the placeholder to keep the stored secret; only overtype it to change it. - A storage push failing does not fail the submission. Storage pushes are best-effort — the certificate still submits even if the SharePoint copy doesn’t land.