Hi,
You should check these resources - Security and Ransomware protection Overview. By Azure SQL backups I suspect that you mean backing up SQL Server inside Azure VM rather backing up Azure SQL Database as the latter is not function of Azure Backup. Check also Soft delete feature. You should check also Multi-user authorization using Resource Guard which will protect your recovery vault from critical operations. Azure SQL backups are stored in recovery vault. There is no additional cost associated with these features.
As mentioned you are actually referring to Azure SQL Backup. This backup does not use recovery services vault. The backup is provided by the Azure SQL Database service. With that as stated in the document: "If you delete a database, the system keeps backups in the same way it would for an online database with its specific retention period. You cannot change backup retention period for a deleted database." and "If you delete a server or a managed instance, all databases on that server or managed instance are also deleted and cannot be recovered. You cannot restore a deleted server or managed instance. But if you had configured long-term retention (LTR) for a database or managed instance, long-term retention backups are not deleted, and can be used to restore databases on a different server or managed instance in the same subscription, to a point in time when a long-term retention backup was taken."
With that in mind I would suggest the following things:
- configure long term retention backup. This has additional cost.
- set permissions correctly and restrictively to only the personal who needs to manage the databases/servers or use Azure AD PIM to grant permissions only when needed. Azure AD PIM requires Azure AD licenses.
- Use Azure Policy to configure/audit short and long term backup settings on Azure SQL Database. Azure policy is free to use for native Azure resources.
Update:
Hi MSTechie-7364, I am not sure if I am not explaining something correctly or you are not reading the provided replies completely.
Initially on my first reply I have provided information based on backups for SQL server on Azure VM. Later I have understood that you are talking about Azure SQL Database Backup. In order not to delete the initial reply or remove the previous text I have updated that reply with additional information specifically for Azure SQL Database Backup so it matches your request. As explained there Azure Backup and Azure SQL Backup are different services and not related to each other in any way. Azure SQL Backup is provided by the Azure SQL Database service and it is available once you have SQL Logical servers and SQL Databases created. Later you have asked me some other questions around Azure Backup which really should have been a separate thread but I have answered those in order to help you. Because Azure Backup is different from Azure SQL Backup none of the features for Azure Backup apply to Azure SQL backup and vice versa. So on
-
- soft-delete is Azure Backup feature so it does not apply to Azure SQL Backup. See my initial reply with the document for long term backup. There it says "If you delete a server or a managed instance, all databases on that server or managed instance are also deleted and cannot be recovered. You cannot restore a deleted server or managed instance. But if you had configured long-term retention (LTR) for a database or managed instance, long-term retention backups are not deleted, and can be used to restore databases on a different server or managed instance in the same subscription, to a point in time when a long-term retention backup was taken."
- The alerts mentioned are for Azure Backup as question was specific for Azure Backup and do not apply for Azure SQL Backup. Azure SQL Backups cannot be deleted. Old backups for Azure SQL Backup are deleted automatically according to retention period. If you want again via activity log you can monitor if database or sql logical server gets deleted. You can create instances of those resources and delete them to see what activity logs are generated to create alerts based on those logs. Alternatively you can use Azure Monitor to create alert. When you choose scope subscription and specific resource type on adding condition you will see examples like 'Delete Azure SQL Server (Microsoft.Sql/servers)' that you can select to create such alert.
- What permissions and who has permissions solely depends your requirements and how you manage Azure resources. Here you can see available built-in roles for Azure SQL Databases that are available. You can also create your own custom roles as well if those does not suites you. Let's take a simplest scenario where you have a single team that manages your SQL logical servers and databases in Subscription A. You create two AAD groups - Group A and Group B. On subscription level you give Group A reader access and for Group B you give SQL Server Contributors. All the users of the team are members of Group A and using AAD PIM users are granted access to Group B temporarily only when needed and of course one someone approves. That way they will get access to do any actions on those resources only when it is needed for short period of time. As mentioned this setup very much depends on your requirements and how you want to do it.
- Azure AD pricing is available here. There you have link to see feature comparison between licenses. Particularly you need Azure AD Premium P2 license.
I will once again ask you to accept the reply as answer as I have answered way more than what was initially asked and it is usually best to open new threads on new questions that you have.
Please "Accept the answer" if the information helped you. This will help us and others in the community as well.