Navigation section

Granular File and Folder Restore in Microsoft 365 Backup

  • Thread Author
Microsoft is rolling out a long-awaited upgrade to its native backup offering: granular, file- and folder-level restore for Microsoft 365 Backup, a change that promises to shrink recovery times, simplify incident response, and reduce reliance on third‑party recovery workflows for OneDrive and SharePoint data.

Enterprise IT Admin Dashboard: Microsoft 365 Backup Granular Restore with a nested file tree.Background​

Microsoft introduced Microsoft 365 Backup over the past two years as a native, tenant-integrated recovery option for Exchange, OneDrive, and SharePoint data. The service was designed to close the gap between the platform’s high-availability guarantees and the practical needs of IT teams responding to customer-side incidents—ransomware, mass deletions, or accidental overwrites—by providing longer retention, faster restore speed at scale, and an admin-directed restore experience.
Early Microsoft documentation positioned the offering as a complement to the baseline 14‑day native recoverability in Microsoft 365, extending retention to one year for backed-up content and offering high-frequency recovery points for Exchange and short-term, high-frequency restore points for file workloads. Until now, that capability was focused primarily on bulk or site-level restore operations rather than single-file recovery.
At Ignite and in product blog updates, Microsoft signalled a roadmap that included several recovery-focused improvements: departmental billing, GCC availability, and—critically—folder/file-level restore. In the most recent tenant-facing message, Microsoft began inviting admins to public preview for the granular restore experience, with the company outlining a staged rollout to tenants worldwide.

What Microsoft is adding: granular file/folder restore explained​

What “granular restore” means in practice​

The new functionality allows administrators to browse existing Microsoft 365 Backup restore points and search or navigate into a site's snapshot to locate and restore individual files or folders. Instead of restoring an entire SharePoint site collection or OneDrive drive and then extracting the target item, IT staff will be able to select just the objects they need and restore them in place or to an alternate location.
Key aspects of the capability:
  • Browse and search restore points for OneDrive accounts and SharePoint sites.
  • Selective recovery of individual files or entire folders from a chosen point-in-time snapshot.
  • Restores are performed by administrators and respect existing backup policies and retention settings.
  • Restore actions are auditable and gated by role-based permissions; only admins with the appropriate backup role may initiate restores.

Supported workloads and scope​

The granular restore functionality is explicitly scoped to the file workloads: SharePoint and OneDrive. Exchange, while still covered by Microsoft 365 Backup for mailbox and item recovery, continues to follow separate restore flows and role requirements. Microsoft’s product messaging and documentation make the distinction clear: the file-level browse/search/restore workflow targets SharePoint and OneDrive restore points.

Timeline and availability​

Microsoft’s public product messaging and tenant Message Center updates track the timeline for preview and general availability:
  • Roadmap posts and Ignite announcements designated folder/file-level restore as a planned capability and marked it for public preview.
  • Tenant Message Center notifications indicate the feature began rolling into public preview in early March 2026, with Microsoft recommending customers prepare admins and runbooks for the change.
  • Microsoft’s communications forecast a global general availability window in late April to early May 2026, subject to the usual change-control caveats and tenant-stage rollouts.
Because Microsoft has previously adjusted dates for these features as they matured, administrators should treat preview and GA timing as tenant-dependent and monitor their own tenant’s Message Center for the Message ID and rollout specifics. Organizations in regulated clouds (for example, Government Community Cloud) should also track Microsoft’s separate availability timelines for those environments.

Technical specifics and operational details​

Retention, frequency and restore speed context​

Microsoft 365 Backup is built to provide extended retention and fast bulk recovery:
  • The service offers up to one year of retention for backed-up Exchange, OneDrive and SharePoint content—much longer than the platform’s default short window.
  • Backup frequency is high for Exchange (near-continual points every ~10 minutes) and more frequent for OneDrive/SharePoint in the short term, then moving to scheduled weekly snapshots for longer-term retention windows.
  • Microsoft has published performance guidance showing bulk restore at scale can reach multiple terabytes per hour for tenant-sized operations; file-level restores will operate differently (smaller object scope, lower throughput needs) but benefit from the same underlying restore architecture.

Admin roles and access control​

Access to the new file-level restore flow requires specific administrative permissions. Microsoft emphasizes the SharePoint Backup Administrator (or equivalent backup role) as the permission boundary for these operations. That means:
  • End users will not be able to initiate these restores through their personal OneDrive UI.
  • Only administrators who have been granted the backup role can browse restore points and perform file restores.
  • Audit logging and multi-admin notification settings can help surface unusual restore activities and provide necessary governance.

Integration points and workflows​

The granular restore functionality is surfaced through the Microsoft 365 Admin Center Backup experience and can be managed alongside existing Backup and Archive tools. Microsoft’s messaging indicates:
  • Restore operations will respect existing backup policies (no change to how data is stored or to retention).
  • Admins can choose to restore in-place (overwrite or merge) or to alternative locations depending on the scenario.
  • The feature complements multi-admin notifications and the Backup discovery features in SharePoint admin pages to make it easier to find unprotected content and respond quickly.

Practical implications for IT teams​

Faster, less disruptive recovery​

Arguably the most immediate benefit is time and disruption saved. Single-file recovery eliminates the need for a time-consuming site- or drive-level restoration, which often requires:
  • Restoring an entire site or drive to a recovery location.
  • Exporting or copying the target object back into production.
  • Reconciling permissions and metadata.
Granular restore collapses that multi-step effort into a direct restore of the object, which shortens recovery windows and reduces administrative overhead.

Reduced reliance on third-party tools (and what that means)​

For years, many organizations relied on third-party backup vendors to get true file-level recovery in Microsoft 365. Native granular restore reduces that dependency for a growing set of recovery scenarios. That does not eliminate the third-party backup market—ISVs still provide broader coverage (e.g., additional workload support, different retention models, cross-tenant tools, or specialized legal hold integrations)—but this change can reduce the number of routine restores handled via external tooling.

Operational and governance changes​

Administrators should plan for:
  • Role reviews to ensure only the right staff have SharePoint Backup Administrator privileges.
  • Runbook updates so the new restore steps are correctly documented and tested.
  • Training for backup admins to use the browsing/search UI and understand restore behaviors (merge vs overwrite, metadata/permission handling).
  • Testing of restore-to-location and in-place restore flows in a controlled environment before relying on them during incidents.

Security, compliance, and risk considerations​

Privilege management and insider risk​

A powerful, easy-to-use restore feature raises the stakes for privileged admin accounts. Organizations must:
  • Enforce strict least-privilege assignments and use privileged access workstations or Just-In-Time elevation for high-risk restore roles.
  • Enable multi-admin notifications and monitoring to detect suspicious restore activity quickly.
  • Leverage advanced auditing and retention of audit logs (Purview/Audit Premium where required) if the organization needs long-term forensic trails.

Ransomware and reintroduction risk​

File-level restores are efficient, but they can also reintroduce compromised files if the restore source contains malware. Best practices to mitigate this risk:
  • Scan restored content with enterprise anti‑malware solutions post-restore.
  • Use quarantined restore locations (restore to a holding library) to validate files before reintroducing them into production.
  • Couple restore procedures with incident-response playbooks that include forensic review and malware scanning.

Data residency and regulatory constraints​

Microsoft has designed Microsoft 365 Backup with residency and compliance in mind, and the Archive/Backup architecture claims immutable storage and audit trails for governance. Nevertheless, regulated entities should:
  • Confirm Backup and Archive availability for their specific cloud instance (commercial vs GCC vs GCC‑High) and understand any differences in feature timelines.
  • Validate that role-based access, retention policies, and audit logs meet their regulatory requirements before depending on the native restore flow for compliance-related recoveries.

Limitations and caveats administrators should know​

  • The granular restore functionality is available only to tenants that have Microsoft 365 Backup enabled. Tenants relying solely on the underlying platform’s native 14‑day recoverability will not have access to the one‑year, point-in-time restore snapshots Microsoft 365 Backup provides.
  • Restore operations are admin‑driven. End users cannot self-serve file-level restores through their standard OneDrive UI; this remains an administrator responsibility.
  • Exchange item-level workflows continue to be distinct. While Exchange is covered by Microsoft 365 Backup, mailbox and message-level recovery paths remain tied to mailbox restore tooling and Exchange-specific restore semantics.
  • Microsoft’s staged rollout means not every tenant receives the capability on the same day. The public preview and GA windows are tenant‑phased, so planning and testing should account for the possibility of delayed availability in some environments.

How this affects the backup vendor ecosystem​

Third-party backup vendors have long marketed deep, feature-rich granular recovery for Microsoft 365 workloads as a core differentiator. Native file-level restore narrows that gap for many common recovery scenarios, but the market implications are nuanced:
  • Vendors that focus on extended retention, cross‑platform portability, and specialized compliance features will still hold value for customers with those requirements.
  • ISVs that offer platform-agnostic snapshots, exportable archives, or flexible storage targets (S3, local vaults) will continue to differentiate on storage choice and mobility.
  • Backup vendors can pivot to complementary value propositions: ransomware detection, immutable storage across clouds, eDiscovery integrations, advanced retention policies, and stronger recovery automation.
For many organizations, the natural evolution will be a hybrid posture: use native Microsoft 365 Backup for routine and rapid recovery, and maintain an ISV or secondary archive for long-term retention, cross-tenant mobility, or specialized legal requirements.

Recommended action checklist for administrators​

  • Confirm whether your tenant has Microsoft 365 Backup enabled and check eligibility for the public preview. If you do not have the service enabled, evaluate the protection gap versus your recovery SLAs.
  • Monitor the Message Center for your tenant for the specific Message ID referenced in Microsoft’s rollout (the message outlines preview and GA timing and tenant-specific rollout instructions).
  • Conduct a role audit:
  • Identify who currently holds SharePoint and Backup admin roles.
  • Apply least-privilege principles and require a separation of duties for restore operations where possible.
  • Update recovery runbooks to include the granular restore steps, decision trees (in-place vs. restore-to-holding location), and malware scanning checkpoints.
  • Run a restore test:
  • Use a non-production site or test tenant to exercise file- and folder-level restores.
  • Validate permissions, metadata preservation, and post-restore behavior in target locations.
  • Enable multi-admin notifications and retention of audit logs so that all restore activities are recorded and surfaced to security teams.
  • Coordinate with legal/compliance teams to confirm that the new restore flows meet regulatory obligations around data preservation, auditability, and data residency.
  • Re-assess third-party vendor contracts in light of the native capability—identify scenarios where ISV capabilities are still required and where they can be reduced.

A balanced assessment: strengths and potential risks​

Strengths​

  • Efficiency: Administrators gain a far faster path to recover individual items, lowering mean time to recovery.
  • Simplicity: A built-in option reduces process complexity and the number of tools required in routine incident responses.
  • Integration and governance: Restores happen inside the tenant boundary, preserving Microsoft’s audit, RBAC and data-residency guarantees.
  • Scale-ready: Backed by Microsoft’s restore architecture, the feature aligns with the platform’s large-scale bulk restore performance while optimizing for small-object restores.

Risks and limitations​

  • Privileged access risk: Powerful restore capabilities make proper role and privilege hygiene imperative.
  • Malware reintroduction: Restoring from a point-in-time snapshot without pre-restore scanning can reintroduce compromised content.
  • Feature cadence variability: Microsoft’s staged rollout model means not all tenants will receive the preview or GA at the same time; reliance on the feature should consider availability windows.
  • Not a full replacement for all third-party capabilities: ISVs still offer differentiated features—cross-tenant portability, specialized retention models, or coverage for services beyond Microsoft’s native scope.

What to watch next​

  • Adoption metrics and admin feedback during the preview will be telling: look for concrete data on restore success rates, time-to-restore for single files, and any unexpected behavior around metadata and permissions.
  • Protection of shared libraries and Teams‑backed channels. Microsoft’s roadmap suggests continued improvements across Backup and Archive—admins should watch for expanders that simplify Teams, Groups, and shared channel recoveries.
  • Security integrations: tighter coupling between backup restores and Defender/Microsoft Purview scanning would materially reduce the malware reintroduction risk. Any announcement that embeds post‑restore scanning or quarantine workflows would be a significant win.
  • Billing and policy controls: Microsoft has signalled departmental billing and more policy granularity in its roadmap; those items will affect cost allocation and operational governance later in the year.

Conclusion​

Microsoft’s introduction of granular file and folder restore to Microsoft 365 Backup is a practical, long-needed enhancement for enterprise recovery operations. For administrators, it promises to speed up recoveries, simplify playbooks, and reduce some of the friction that has led many organizations to lean on third-party tools for routine file recoveries.
That said, the feature is not a silver bullet: it requires careful role management, updated runbooks, and an integration of security checks to avoid accidental reinjection of compromised content. Organizations should treat the preview as an opportunity to test workflows, tighten privileged access, and align compliance requirements before moving critical recovery responsibilities to the native toolset.
For everyday incidents—accidental deletions, small-scale corruption, or targeted file recoveries—this capability will change the calculus for many IT teams. For complex legal, archival, or cross-tenant retention needs, third‑party solutions will continue to play an important role. The practical course for most organizations will be hybrid: embrace Microsoft 365 Backup’s new granular restore for routine recoveries while retaining ISV options for specialized retention and compliance scenarios.
Administrators should begin preparing now: confirm tenant eligibility, train backup operators, update runbooks, and enable monitoring to ensure that this shift improves not only mean time to recovery, but also the safety and auditability of every restore action.
Source: Windows Report https://windowsreport.com/microsoft-to-add-granular-file-restore-to-microsoft-365-backup/
 

Click to expand...
Microsoft’s upcoming granular restore for Microsoft 365 Backup promises to end an era of heavy-handed rollbacks by letting administrators search, browse, and recover individual files and folders from SharePoint and OneDrive backups — not entire sites or accounts — cutting recovery time, reducing user disruption, and simplifying incident response workflows. om]

Person at a desk uses a monitor showing Microsoft 365 Backup with a restore timeline.Background​

Microsoft 365 Backup launched as a tenant‑integrated, cloud‑native data protection service that captures point‑in‑time snapshots for Exchange mailboxes, OneDrive accounts, and SharePoint sites. The service was positioned to give organizations a faster path to recover from accidental deletions, content corruption, and ransomware events without exporting or relying on slower external storage systems. Over the last year Microsoft has signaled a roadmap to expand recovery granularity and governance features for enterprise customers.
The root complaint from IT teams has been straightforward: when a single document disappears or a folder is damaged, the only available option was often a full site restore or drive rollback. Those broad restorations carry real operational costs — overwritced user downtime, and the logistical complexity of merging restored site states back into production. The new granular restore capability directly addresses this operational inefficiency.

What Microsoft is changing — the essentials​

Microsoft’s update adds a file‑ and folder‑level restore workflow to Microsoft 365 Backup that will allow administrators to:
  • Browse backup restore points for a site or user drive and view files and folders contained in those points.
  • Search and filter across restore points to find specific items.
  • Restore a single file or folder to the original location (overwriting current content) or to a different location (creating a copy) to avoid overwriting newer work.
Microsoft began rolling the feature into public preview in early March 2026 and expects general availability in the April–May 2026 timeframe, with several reports and message center notifications pointing to early May 2026 as the GA target. AdministratorrePoint Backup Administrator** role to perform these restores; the role’s permissions explicitly cover backup and granular restore actions for SharePoint and OneDrive.

How the granular restore workflow works​

Search and browse across restore points​

The new tools provide a file‑level index of content preserved in each daily restore point. Administrators can:
  • Scope to a SharePoint site or an individual OneDrive.
  • Browse the folder hierarchy and view file metadata recorded in the backup point (dates, sizes, versions).
  • Use filters and full‑text search to narrow results to a specific document, folder, or file type.
This approach mirrors what third‑party backup vendors have long offered, but now it’s native and integrated with the Microsoft tenant model and admin roles. Early public preview notes indicate the UI will surface restore points by date and let admins preview items before initiating a restore.

Two restore targets: overwrite or copy​

Administrators will be given two core restore options:
  • Restore to the original location, which overwrites the existing item (useful when the production copy is corrupted or missing).
  • Restore to a new location, which creates a copy so the restored version can be validated before replacing anything.
This dual‑target model reduces risk by allowing conservative workflows (restore to a sandbox or admin‑approved library) before committing changes in production. Documentation and early coverage emphasize both modes.

Permissions and role scoping​

Only accounts assigned the SharePoint Backup Administrator role will be able to access these granular restore tools; the role’s definition includes actions to read and manage restore sessions and restore artifacts for both SharePoint and OneDrive. That separation is intended to minimize over‑privileged admin access and provide a clear separation between backup operators and other tenant admins. Organizations using custom role models will need to map that role into their governance plans.

Why this matters to enterprise IT​

The addition of file‑ and folder‑level restore is more than a convenience: it changes how restoration strategies scale in large organizations.
  • Reduced blast radius: Restores can be surgical, avoiding wholesale site rollbacks that rip out changes made since the last backup snapshot.
  • Faster time to recovery (MTTR): Finding and restoring a single item is quicker than spinning up a full site recovery and reconciling differences.
  • Less operational friction: Fewer change windows, fewer support tickets, and fewer user impacts mean continuity for knowledge workers.
  • Native audit and role integration: Built‑in role scoping and the Microsoft admin model simplify controls compared with third‑party access patterns.
For organizations that have relied on external backup providers to get granular restores, a native option can shorten incident response playbooks and reduce license complexity — but it’s not an automatic replacement. Third‑party vendors still offer advanced features such as cross‑tenant restores, longer retention tiers, immutable storage options, or specialized eDiscovery workflows that some enterprises still require. IT leaders should view the Microsoft feature as a material bet toward faster, less disruptive recoveries while still evaluating third‑party value add if their compliance or retention needs exceed native functionality.

Practical implications and recommended admin actions​

Organizations should treat this rollout as both an opportunity and a change management project. Here are pragmatic steps to prepare:
  • Review backup coverage: Confirm which SharePoint sites and OneDrive accounts are protected by Microsoft 365 Backup and ensure critical business data icrosoft.com]
  • Assign and audit roles: Map the SharePoint Backup Administrator role to specific individuals or automation principals and enforce least privilege. Verify who can create restore sessions and who can execute restores.
  • Update runbooks: Add file‑level restore steps to incident response playbooks, including when to choose overwrite vs. copy restores and how to validate restored content before returning it to users.
  • Train recovery operators: Run tabletop exercises that include file‑level recoveries to ensure operators are comfortable with the search, filter, and restore workflow in preview and GA.
  • Review retention and recovery point objectives (RPOs): File‑level restore is useful only if restore points exist within the RPO window. Align retention with business needs and regulatory obligations.
  • Identify critical content and map it to backup policies.
  • Test restores regularly, including both overwriting and copy‑back scenarios.
  • Incorporate the new workflow into change management approvals to avoid unintended overwrites.

Technical verification and cross‑references​

Multiple independent sources confirm the practical details reported in early previews:
  • Microsoft documentation covering Microsoft 365 Backup and storage/restore APIs details restore point selection and drive/site restore semantics, and it shows the platform’s architected capability to support file‑level operations.
  • Product roadmap notes from Microsoft Ignite and the Tech Community blog referenced the break‑out of granular restore as a preview feature and linked it to wider resilience work for Microsoft 365 Backup and Archive.
  • Coverage from independent news outlets that follow Microsoft admin‑center message center updates report that the feature entered public preview in early March 2026 with GA targeted for late April–early May 2026. That timing appears in multiple outlets and message center references. Administrators should treat dates in public reporting as guidance and enant rollout via Message Center notifications in their environment.
Caution: Some early reports and community posts are paraphrasing message center items. While the core capability — file/folder restore — is consistently represented across sources, exact rollout dates and feature scope in preview can vary by tenant region and license. Always confirm feature availability in your own tenant before changing production recovery policies.

Strengths: what Microsoft gets right​

  • Native integration: Because Microsoft 365 Backup is tenant‑aware, restored content retains the platform’s metadata and service context (permissions, drive/site associations), which makes the restored object more seamless to reintroduce.
  • Role‑based control: Tying granular restore to a purpose‑built Entra role reduces the temptation to over‑privilege general admins and helps enforce separation of duties. ([learn.microsoft.com](Microsoft Entra built-in roles - Microsoft Entra ID modes: Offering overwrite and copy options supports conservative recovery patterns and minimizes accidental data loss from hasty restores.
  • Reduced reliance on third parties: For many organizations, native file returns will eliminate the need to coordinate with third‑party vendors for common restore scenarios, shortening SLAs and lowering operational overhead.

Limitations and risks — what to watch for​

No single cloud offering is a silver bullet. The new feature reduces friction for many restores but introduces caveats IT teams must consider:
  • Scope of retention and compliance: Native backup retention windows may not match industry‑mandated archival retention. Organizations with long‑tail eDiscovery needs may still require dedicated archiving systems. Verify retention policies before assuming native backup meets all legal obligations.
  • Regional rollout and tenant variability: Microsoft often staggers previews by region and tenant type; the public preview noted in March 2026 may not appear in every tenant simultaneously. Always consult Message Center and the Microsoft 365 admin center for tenant‑specific timelines.
  • Operational risk of overwriting: The overwrite option is powerful but can be misused. Without tight change controls and verification steps, operators could unintentionally replace newer, correct content. That makes runbook updates and role controls critical.
  • Feature parity with third‑party vendors: While Microsoft’s native tool handles common restore scenarios, some advanced features (e.g., multi‑tenant cross restore, ransomware‑hardened immutable vaults, or specialized legal hold integrations) remain strengths for third‑party specialists. Plan for a hybrid model if your organization depends on those capabilities.

Recommended runbook updates (practical steps)​

Below are recommended, sequential actions for teams adopting the new tools. These steps are designed to be practical and to reduce accidental data loss.
  • Inventory protection scope.
  • Map which sites, libraries, and OneDrive accounts are in Microsoft 365 Backup.
  • Flag high‑value or regulated content.
  • Enforce roles and access controls.
  • Assign the SharePoint Backup Administrator role to a small, vetted group.
  • Enable privileged access management or time‑limited elevation where your Entra setup supports it.
  • Test in preview environments.
  • Use the public preview to practice search, filter, and both restore modes.
  • Validate metadata, permissions, and file integrity after restore.
  • Add guardrails to overwrite restores.
  • Require a second‑operator approval or automated backup of the target folder before overwriting.
  • Document roll overwrite introduced regressions.
  • Communicate to stakeholders.
  • Update support teams, business owners, and legal/compliance about the new capability and the scenarios it covers.
  • Gather feedback after the first wave of restores to refine the runbook.
  • Reassess third‑party contracts.
  • If you maintain third‑party backup vendors primarily for granular restores, reevaluate whether those contracts still deliver unique value or whether you can rationalize tooling.

Governance, compliance, and auditability​

Granular restores reduce friction but also shift where audit trails must be maintained. Ensure the following:
  • Logging: Confirm that restore actions are logged to the Unified Audit Log or your SIEM so you can trace who executed a restore, which restore point was used, and whether the restore overwrote production content. Microsoft’s restore APIs and admin logs capture these actions when enabled.
  • Retention alignment: Coordinate backup retention with legal holds; Microsoft 365 Backup is distinct from retention/archival holdings, so retention policies and backup retention may interact in complex ways. Legal and compliance teams should be consulted before retiring archival solutions.
  • Change control: Treat important overwrites as change requests in the same way you would for any production‑impacting content update to preserve accountability.

Where this fits in a broader data protection strategy​

Think of Microsoft’s granular restore as a change in the recovery tiering model:
  • Tier 1 — version history: End users and SharePoint versioning still provide the fastest, lowest‑impact recoveries for recent edits.
  • Tier 2 — Native file/folder restores via Microsoft 365 Backup: Faster and less disruptive than site/drive rollbacks, suitable for missing or corrupted files that exceed local version windows.
  • Tier 3 — Full site or drive recovery: Reserved for large‑scale incidents or complex corruption scenarios that require rehydration of the entire content set.
  • Tier 4 — Third‑party or immutable vault recovery: For long‑term retention, complex eDiscovery, and heightened ransomware protections, external vendors may still be necessary.
This tiering preserves the role of Microsoft’s new capability as an operational accelerator while recognizing that compliance and extreme recovery scenarios can still require specialized tooling.

Closing analysis: balanced view and what to expect next​

Microsoft’s file‑ and folder‑level restore for Microsoft 365 Backup is a pragmatic, overdue enhancement that will materially improve day‑to‑day recoverability for many organizations. The feature aligns with the broader trend of embedding essential data protection into SaaS platforms, reducing the time and complexity of restores while leveraging platform‑native semantics such as permissions and metadata.
Strengths include native integration, role‑scoped access, and dual restore modes — all built to reduce MTTR and administrative friction. The most significant residual challenges are governance (preventing inadvertent overwrites), retention alignment with legal/compliance needs, and verifying that preview behavior matches GA behavior in each tenant.
For IT leaders, the sensible path is to treat the preview as a controlled change project: test, document, and update runbooks, then scale the approach into production after validating logs, permission models, and business owner expectations. Organizations with specialized archival or immutable retention needs should continue evaluating third‑party solutions for those specific requirements.
Finally, administrators should watch Message Center notifications and the Microsoft 365 admin center for tenant‑specific availability. Public previews can vary by region and license, and Microsoft’s official documentation and Message Center remain the authoritative source for the precise rollout schedule and feature disclaimers.
Microsoft’s move is incremental but meaningful: by enabling targeted restores, it turns a formerly disruptive process into one that can be surgical, faster, and far less painful for users and IT teams alike.
Source: Petri IT Knowledgebase Microsoft 365 Backup to Add Granular Restore Option
 

You must log in or register to reply here.
Back
Top