
Microsoft MVP | Microsoft 365 Architect
In a recent YouTube walkthrough, Denis Molodtsov [MVP] introduces viewers to Microsoft 365 Backup, a native backup service for SharePoint, OneDrive, and Exchange that many administrators may not know is available. The video demonstrates how to set up the service, create a backup policy, and run restores, including a faster option called express restore. Denis also contrasts backup with archiving to help admins choose the right tool for recovery and retention scenarios. Overall, the presentation is practical and aimed at IT pros responsible for tenant resilience.
Microsoft 365 Backup provides frequent point-in-time copies of cloud workloads, running backups every ten minutes and retaining data for up to one year by default. Denis highlights that restores themselves do not carry an extra execution fee; instead, organizations pay storage at approximately $0.15 per GB per month for retained backup data. The tool supports full-site recovery and, increasingly, more granular restores such as folders and individual files through public preview features. Consequently, it fills a gap between basic retention policies and full third-party backup platforms.
The video walks viewers through enabling backups in the Microsoft 365 Admin Center and creating a SharePoint-focused policy, showing how simple discovery and enrollment can be from the admin interface. Denis points out a pay-as-you-go billing model where storage charges are the main cost driver, and he mentions options for departmental billing that help allocate expenses across business units. This integrated approach lowers the barrier to entry for organizations that prefer built-in management over adding external services. Still, administrators must plan for ongoing storage costs when deciding on retention windows and scope.
Denis demonstrates both standard restores and express restore, noting that express operations can recover small sites in under 20 minutes, which is valuable during urgent incidents. He explains the choice between restoring to a new site or rolling back changes on the original site, describing scenarios where each approach is preferable to minimize interruption or preserve a safe copy of current data. Additionally, the tool is expanding granular restore capabilities so admins can retrieve individual items without restoring entire sites, which reduces recovery time and scope. Therefore, teams can balance speed against precision depending on the incident.
Importantly, the service keeps backup retention independent of tenant-level deletion or retention policies, creating an isolated copy that helps resist accidental or malicious removal. Denis emphasizes multi-admin notifications and grace periods for risky actions, which give administrators time to intervene before changes propagate widely. The video also notes that the service is moving into more regulated environments, with public preview availability in Government Community Cloud for certain compliance needs. As a result, organizations with strict compliance requirements can evaluate whether native coverage meets their controls or if additional safeguards are required.
While Microsoft 365 Backup integrates tightly with admin centers and simplifies management, Denis discusses the tradeoffs compared with third-party backup providers that offer longer retention, different billing models, or extra analytics. Native backup reduces deployment complexity and keeps data inside the Microsoft 365 boundary, but it may limit options for very long-term archiving or cross-tenant consolidation. Consequently, teams must weigh operational simplicity and integration benefits against specialized features or retention horizons offered by external vendors. In short, the right choice depends on each organization’s compliance, cost tolerance, and recovery objectives.
Denis recommends that IT teams test restores and incorporate them into incident drills to ensure recovery expectations match reality, because speed and success can vary by site size and complexity. He also advises configuring retention and backup scope deliberately, since increasing retention raises storage costs and broadening scope can lengthen restore operations. Proper governance, including role separation and notification rules, reduces the risk of administrative errors and improves response to ransomware or accidental deletions. These operational practices make the native tool more reliable as part of a broader data protection strategy.
The presenter acknowledges limits such as the current one-year retention cap and evolving granular restore features that are in public preview, which may not yet cover every scenario enterprises need. Additionally, administrators may face challenges in cost forecasting because pay-as-you-go storage can grow unpredictably if backups are applied across large tenants without controls. Migration and restore testing for very large or complex SharePoint sites can reveal performance constraints, meaning some organizations will still need third-party solutions for advanced recovery SLAs. Thus, measuring scope and testing early are essential to reduce surprises.
Denis’s guidance centers on enabling Microsoft 365 Backup for high-value SharePoint and OneDrive content quickly, testing express restores for small sites, and tuning retention to balance cost and recovery needs. He also encourages administrators to monitor discovery panels in admin centers to find unprotected resources and to adopt multi-admin safeguards to catch risky operations before they cause data loss. For organizations with longer retention or specialized compliance needs, he suggests evaluating native capabilities alongside third-party options to identify gaps. Following these steps helps teams improve resilience without overcommitting resources prematurely.
The video by Denis Molodtsov [MVP] presents Microsoft 365 Backup as a practical, built-in option for many tenants seeking faster, integrated recovery for SharePoint, OneDrive, and Exchange. While it offers strong advantages like frequent backups, isolated retention, and rapid restores, administrators must consider tradeoffs around retention length, cost, and advanced feature needs. Overall, the native tool is a useful addition to a layered protection approach, and teams should pilot it, test restores, and align retention settings with business and compliance requirements. By doing so, organizations can make informed decisions that balance costs, speed, and data protection.
microsoft backup tool, azure backup, windows server backup, system center dpm, microsoft 365 backup, azure backup server, windows admin center backup, backup tools for admins