Add support for removable disk in the MARS agent.

Please add support for Microsoft PowerShell 4.0 or 5.0 instead of 2.0 on Windows 10 operating systems.

Please embed Azure Backup status in the daily Health Reports for Windows Server 2016 Essential servers. This report now issues critical warnings that no backups are being made as I'm not using the local backup feature but Azure Backup instead. This gives my org the idea that no backups are being made and that they are not compliant to the health care regulations. #Compliance

The preview for Azure Backup Reporting only supports exporting data to a storage account in the same tenant. This means that MS partners cannot use the solution - in most cases each managed customer has their own tenant.

The alternative approach, creating multiple instances in Power BI and pinning duplicate reports to a single dashboard will not work.

Please make it possible to export RSV data to a storage account in another tenant, e.g. storage account name + access key.

When using MBS, you probably created storage pools.
However when your system dies, you may have your SQL backed up but lose your storage!
Because that config of the storagepools is lost.
Something like BMR or Windows Config backup would be nice.

Allow us to remove/stop the MARS agent backup and the connection from the agent from the console.

Currently we can set daily or weekly backup schedules but not monthly. There are scenarios where customer only needs monthly backup for certain VMs. Such customers are required to implement powershell scripts or manual operations once a month which to enable backup, take an adhock backup, and disable backup. It would be nice if we have an option to take montly backup in Azure Backup.

We have a clustered file server which we are backing up using Azure Backup. It works, but it isn't perfect, it would be nice if Azure Backup had better support for failover file clusters

Very similar to a point-in-time recovery

Please can you publish a document(s) on how the Azure Backup process works on a technical level from start to finish.

On several occasions I have come across the situation where I have logged onto a server and noticed the Azure backup agent has gone into a stalled state where it is not performing a backup or reporting to the portal. Had I not logged onto the server and noticed this I would have assumed the backup was running fine with no issues.

Can you create a check and alert for agent health?

Now we don't have the way to check the current instance from the portal. it would be better if we could check it from the recovery services section right necxt to backup data size area.

When I receive an email alert that my job has 'completed with warnings' it would be good to see the files\folders it has failed on instead of me having to connect to the server each time.

Currently it's possible to backup VMware VMs to Azure for off-site or long term copy. It would be great if these backups could be restored in Azure as IaaS virtual machines (if the on-premises data center crashes for example).

Backup of large volumes 500TB into Azure cool/cold/archive storage.
Customer who have implemented Hadoop (Cloudera) and ADLS in the large scale need backup solution similar to tape on premise. It could be COLD solution i.e .cheep storage by expensive to retrieve data.

I know network throttling is available when you install the Azure agent on Server 2012 but can something be done for Server 2008?

User want to set an alert for his recovery services when his consumption reaches to 50 TB.

Also wants to setup an alert for money/Bill for this consumption if this reaches beyond a limit.

Allow file-level restores of Encrypted Azure VMs without MARS

Item/file-level restore from vmware snapshot backups is only possible from short-term disk recovery points. Please add the option to restore a single file from a online recovery point instead the need of restoring the whole VM.