This site is scheduled for a small content update on Tuesday, January 22nd, between the hours of 5:00pm and 8:00pm Pacific Time (Jan 23 01:00 – Jan 23 4:00 UTC). Access to this site may be slightly delayed during that time.

Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.
  • London
  • Kingston
  • Jakarta
  • Istanbul
  • Helsinki
  • Geneva
  • Store

Configure snapshots to execute on a schedule

Log in to subscribe to topics and get notified when content changes.

Configure snapshots to execute on a schedule

An Azure snapshot is a read-only copy of a specified virtual hard disk (VHD). You can schedule snapshots to ensure that you regularly make a copy of a virtual resource so you can recover from errors.

Before you begin

Role required: cloud_user, cloud_operator, or cloud_admin

About this task

If the VM is running at the start of the snapshot process, the VM is shut down and then restarted when the process finishes.


  1. Open the list of VMs by navigating to Cloud Management > Cloud Resources and clicking the Compute tab.
  2. Click the VM name.
  3. lick Schedule Snapshot related link.
    Table 1. Take Snapshot form
    Field Description
    Name Name for the scheduled snapshot job that you are configuring.
    Active Select the check box to cause the scheduled snapshot job to run on the specified schedule.
    Run Schedule to follow to run the scheduled snapshot job.
    Application Read-only. Application scope that the eviction policy was created in.
    Conditional Select the check box to specify the conditions that must be met to take a snapshot. When you check the box, the system opens a standard condition builder.
    Snapshot limit Maximum number of snapshots that are saved for VMs that meet the specified conditions. The system runs the eviction policy script to delete a snapshot.
    • When the Limit value is reached, the scheduled job attempts to delete the oldest snapshot before it creates a new snapshot.
    • The scheduled snapshot job will not delete a snapshot that was created by an on-demand request.
    • On the first run of the scheduled job, if the total number of snapshots for the VM is equal to the global limit, then the job deletes the oldest snapshot before it creates a new snapshot.
    Snapshot name Unique name that will be used as the label for the snapshots. The system appends timestamp text.
    Snapshot short description Single sentence or phrase that describes this snapshot.
    VM instance Virtual machine that is associated with the VHD to take a snapshot of.
    Volume Virtual hard disk to take a snapshot of.
    Snapshot eviction policy Name of the script to run when deleting a snapshot.
    Send success notification Select the check box to send an email when the snapshot is successfully created. See Recipient's email.
    Recipient's email Email address to send the success notification to. See Send success notification.
    Skip next run Select the check box to skip the first scheduled snapshot.

    This is useful when you create a recurring time that will occur too soon to be useful. For example, if you create the schedule at noon on a Monday and the snapshot recurs each Monday at 5:00 PM, then check the box to skip the first snapshot (5 hours after you create the schedule). Instead, the first snapshot will run next Monday at 5:00 PM.

    If approval is not required, the system immediately takes the snapshot. If approval is required, there may be a delay while an admin approves the change. You receive email when the admin approves. After the admin approves, return to the VM Instance form and click the Proceed with Change related link.