Azure Backup

Welcome to the Azure Backup feedback forum! This is where we would like to hear your feedback and ideas on how we can improve our product.

How can we improve Azure Backup?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Recover IaaS VM back to on premise

    For regulatory reasons we need access to historic backups. If for any reason we move away from Azure I need to know I can still access them so I would like to be given the option to recover the VM to an on premise location.

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  IaaS VM  ·  Flag idea as inappropriate…  ·  Admin →
  2. Azure VM Level Backup - Shut Down original VM before starting up restored VM

    Azure VM Level Backups (announced March 26th, 2015) include a restore step that starts a VM with the same computer name on the network as the original VM. I recommend adding a checkbox that prompts the user whether they want the original VM shut down or turned off, as this would avoid having two computers on the network with the same computer name. Or in a batch environment, you would not want a batch to be fired off on two systems as this could contaminate data.

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  3 comments  ·  IaaS VM  ·  Flag idea as inappropriate…  ·  Admin →
  3. Install VM Agent when registering a VM for new VM Level Backup Feature

    Since VM Agent is required for the new VM Level Backup feature to work, the recovery services register wizard should either provide a hyperlink to a TechNet article on how to manually install the VM Agent, or it should run the powershell command to set ProvisionGuestAgent value to true using Powershell or a REST call.

    5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  IaaS VM  ·  Flag idea as inappropriate…  ·  Admin →
  4. Azure Recover Service

    I am currently testing the Recover Service to backup Azure based servers and have discovered that the agent has a requirement for the server to not have FIPS encryption setting turned on (HKLM\System\CurrentControlSet\Control\Lsa\FIPSAlgorithmPolicy\Enabled = 1)

    Turning this off reduces the security posture of the server and goes against our standard and security team requirements. Considering this is a show stopper for us is there any consideration to changing the requirement for FIPS to be turned off?

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  IaaS VM  ·  Flag idea as inappropriate…  ·  Admin →
1 2 4 Next →
  • Don't see your idea?

Azure Backup

Feedback and Knowledge Base