SharePoint
A SharePoint storage target is one site's document libraries, reachable like any other storage. It is separate from the Microsoft 365 connector: the connector backs up a whole tenant, item by item; a storage target lets a site be a job's source or destination, a drive, or an archive with folder rules.
What you need #
- A Microsoft account with access to the site — sign-in happens in the browser; Caryvane stores a refresh token, never the password.
- The site's URL, or just pick it from the list the site picker shows.
Add it as a storage target #
- Storage → Add → SharePoint.
- Connect Microsoft Account — sign in and consent in the tab that opens.
- Choose the site with the picker (or paste its URL), then Test.
Test on the target's row proves the credentials; a target that fails shows the provider's own message until it is fixed. From then on it can be a job's destination, a cloud-to-cloud source, a cloud drive, or an archive.
What it supports #
| Capability | SharePoint |
|---|---|
| Streams uploads | No — staged through the agent or worker |
| Version history | Sidecar |
| Realtime cloud-copy source | No |
| Cloud-drive mount | Yes |
| Reachable from the Cloud Agent | Yes |
| Browse in the console | Yes, with folder dates and hashes — so archiving rules can be marked here |
Things to know #
Archiving. SharePoint is the first source the Archiving Policy was built for: switch archiving on for the target, browse it, mark Projects for three years and Contracts as never, and an Archiving job moves the old documents to cheap storage with a catalogue entry for each.
Containers. Each document library is a container; the site's root is a container too (an empty container name), and the console browses from there.
Hashes. Graph reports a SHA-256 for most files, which the archive uses to prove a copy before removing the original.