BYOVault documentation
BYOVault backs up Microsoft 365 (SharePoint, OneDrive, Exchange) and on-prem file servers directly into a cloud storage account you already own — Azure Blob or AWS S3. This section documents exactly what that means in practice: what's captured, how it's encrypted, how retention and restore actually work, and where the current limits are.
How it fits together
A tenant connects Microsoft 365 via a standard Entra OAuth consent grant, and points BYOVault at a storage destination it controls — an Azure Blob container or an S3 bucket. From then on, BYOVault runs scheduled backup jobs that pull data from Microsoft Graph, encrypt it, and write it straight into that destination. BYOVault’s own infrastructure never becomes a second copy of your data — it holds metadata (what was backed up, when, and where in your bucket it lives), not the content itself.
What's covered here
What this documentation won't do
It won’t round up. Where a workload isn’t backed up (Teams), a restore isn’t possible (bulk drive restore), or a security property is narrower than it might sound (per-tenant keys derived from one shared master key, not customer-held keys), that’s stated plainly on the relevant page — not left for you to discover during an actual incident.
New to BYOVault? Start with the Quickstart, which walks through connecting a tenant, attaching storage, and running a first backup end to end.