Supported Platforms & Feature Matrix
A single reference for what BYOVault backs up, which of your own cloud storage providers it can write into, and which restore and retention features apply to each workload.
Workloads × storage providers
BYOVault backs up four workloads — SharePoint, OneDrive, Exchange, and file servers — into a storage account you own. Support for a given workload does not imply support for every storage provider it can be pointed at.
| Workload | Azure Blob Storage | AWS S3 | Google Cloud Storage |
|---|---|---|---|
| SharePoint | Supported | Supported | Not supported |
| OneDrive | Supported | Supported | Not supported |
| Exchange | Supported | Supported | Not supported |
| File Servers | Supported | Supported | Not supported |
Feature support by workload
Version history, direct download, BYOK, and the retention vault are not uniform across workloads. The table below is the accurate breakdown; the mechanism itself is described in Restore Overview and Retention & Archiving Overview.
| Feature | SharePoint | OneDrive | Exchange | File Servers |
|---|---|---|---|---|
| Version history | Supported | Supported | Supported | Supported |
| Direct download to browser | Supported | Supported | Supported | Supported |
| In-place restore | Supported | Supported | Supported (including cross-mailbox restore) | Supported (via the on-prem agent) |
| BYOK (customer-managed key) | Supported | Supported | Supported | Supported |
| Retention vault (Azure/AWS only) | Supported | Supported | Supported | Supported |
Version history and direct download
Every backed-up version of every file or mail item is retained and browsable regardless of workload — this is not a per-workload option.
Direct download decrypts and streams a blob straight to the browser off its stored path, which is identical in shape across all four workloads, so download has no workload-specific gap either.
See Version History and Download a File.
In-place restore
In-place restore is not a single mechanism; each workload uses a different path back to its source system.
- SharePoint and OneDrive both restore by writing a file back into its original Microsoft Graph drive location.
- Exchange restores by writing a message back into a mailbox folder, and additionally supports restoring into a mailbox other than the one the message was originally backed up from.
- File servers restore through a request that the on-prem agent picks up and writes back to the original file path on the source machine.
See In-Place Restore: SharePoint & OneDrive and In-Place Restore: Exchange.
BYOK
A BYOK configuration is activated per tenant, not per workload. Once active, every file uploaded from any of the four workloads is protected with a per-file, customer-wrapped key rather than the shared derived key, with no separate workload-level opt-in required. See Customer-Managed Keys (BYOK).
Retention vault
Archiving and retention apply to all four workloads under one schedule, though each workload has its own independently configurable eligibility threshold for when an item is considered stale enough to archive.
The vault itself is available only on Azure Blob or AWS S3 primary storage. A tenant configured with Google Cloud Storage as primary storage cannot enable retention-vault archiving at all — the setup request is rejected outright rather than silently accepted.
See Retention & Archiving Overview.