Azure Backup Policy

What it is

A backup policy defines when backups are taken (the schedule) and how long they’re kept (the retention). In Azure Backup, every protected workload is governed by a policy, created and stored in a Recovery Services vault.

Why it exists

You want backups to happen automatically on a schedule (not ad-hoc) and old restore points to be purged automatically to control cost/compliance. A policy encodes “back up daily at 22:00, keep 30 daily, 12 weekly, 5 monthly” as a reusable, managed rule.

Key ideas

• Schedule: daily and/or frequency per control (e.g. nightly) plus optional multiple points per day.
• Retention: keep N daily / weekly / monthly / yearly points (older granularities retained longer).
• Applied to protected items; changing a policy re-scopes future backups of those items.
• Can set instant restore retention for the snapshot actually kept locally.
• New policies typically override/retain prior retention for already-created restore points until they expire.

How it fits (diagram)

Diagrams courtesy of Microsoft Learn / Azure docs: backup/backup-architecture

Exam notes

• Policy = schedule + retention; applied from the vault to backup items.
• Retention is tiered: daily/weekly/monthly/yearly counts, with longer tiers kept longest.
• Backups are only as good as the policy — a misconfigured policy means missed/no backups.
• Each protected resource needs a policy to run scheduled backups.

Related

azure-backup · recovery-services-vault · azure-vm · Home

📘 Source: Microsoft Learn — Azure Backup Policy