Share via

Can one backup policy be applied to two file shares?

MichaelB-2136 110 Reputation points
2026-03-04T15:14:51.74+00:00

Is it good practice to have separate policies even if you want both to back up at same time with same retention settings?

Azure Backup
Azure Backup

An Azure backup service that provides built-in management at scale.

Answer accepted by question author
  1. Suchitra Suregaunkar 9,270 Reputation points Microsoft External Staff Moderator
    2026-03-04T17:21:28.6233333+00:00

    Hello @MichaelBroadhead-2136,

    Yes, A single Azure Backup policy can be associated with multiple Azure File Shares, and this is fully supported by design.

    • The backup policy only defines rules: schedule (daily/weekly), retention (days/weeks/months/years), and tier (snapshot / vault).
    • Each file share is still backed up independently, even when the same policy is used.
    • When the backup job runs, Azure triggers a separate snapshot per file share, applies the same retention logic, and tracks recovery points individually.

    So, sharing a policy does not merge backups, does not mix data, and does not affect restore granularity.

    1. Use one shared policy when:
    • Both file shares need the same backup time.
    • Both require identical retention settings.
    • Business criticality and compliance requirements are the same.

    This reduces operational overhead and avoids unnecessary policy sprawl.

    If you already have multiple file shares protected with different policies but the requirements are actually identical, the workaround is to:

    • Detach them
    • Re‑protect using a single common policy

    This simplifies management without changing backup behavior.

    1. You must use separate policies if any one of the following differs:
    • Retention duration (e.g., 7 days vs 30 days)
    • Backup frequency or timing
    • Vaulted vs snapshot‑only requirements
    • Compliance / audit retention needs

    This is because Azure Backup does not support per‑file‑share retention overrides inside the same policy. Retention is enforced at policy level, not at resource level.

    Note: “If two file shares use the same policy, will retention collide or override?”

    The answer is No.

    • Retention is evaluated per recovery point per file share
    • Deleting or expiring a recovery point for FileShare‑A has no impact on FileShare‑B
    • Restore operations remain fully isolated.

    You can safely apply one Azure Backup policy to multiple Azure File Shares as long as they require the same backup schedule and retention settings. Each file share is backed up and retained independently, even when the policy is shared. Separate policies are only required when retention, schedule, or compliance requirements differ, since Azure Backup enforces retention at the policy level, not per file share.

    Thanks,
    Suchitra.

    0 comments

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Q&A Assist
    2026-03-04T15:15:00.9033333+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    Yes. A single Azure Backup policy can be applied to multiple file shares, and this is a normal and supported practice.

    For Azure Files:

    • When configuring backup in a Recovery Services vault, one backup policy can be selected and applied to multiple file shares in the same storage account.
    • The policy defines schedule and retention; all file shares using that policy follow the same backup times and retention settings.
    • It’s explicitly supported to protect file shares in the same storage account, in the same vault, with different backup policies if needed. This means using one shared policy for multiple file shares is fine, and separate policies are only necessary when schedule or retention requirements differ.

    From a best-practice perspective:

    • If two file shares truly have identical RPO/RTO, schedule, and retention requirements, using a single shared policy is efficient and recommended (simpler management, fewer objects to maintain).
    • Create separate policies only when there is a real difference in requirements (for example, different backup frequency or longer retention for one of the shares).

    References:

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.