Microsoft.storage.storageaccounts.delete remediation

​

Event Information

1. The Microsoft.Storage.storageAccounts.delete event in Azure for Azure Storage indicates that a storage account has been deleted in the Azure environment.
2. This event signifies that all data and resources associated with the storage account, such as blobs, files, tables, and queues, have been permanently removed.
3. It is important to note that this event cannot be reversed, and any data stored in the deleted storage account will be lost unless it has been backed up or replicated to another location.

​

Examples

1. Unauthorized deletion: If security is impacted with Microsoft.Storage.storageAccounts.delete in Azure for Azure Storage, one example could be an unauthorized user gaining access to the Azure Storage account and deleting critical data or resources without proper authorization or authentication.
2. Data loss: Another example could be accidental or malicious deletion of the Azure Storage account, resulting in the loss of important data or backups stored within the account. This can have severe consequences for business continuity and data recovery.
3. Service disruption: Deleting an Azure Storage account can lead to service disruption for applications or services relying on that storage account. This can impact the availability and performance of the applications, causing downtime and potential financial losses for the organization.

​

Remediation

​

Using Console

1. Enable Storage Analytics Logging:
   • Go to the Azure portal and navigate to the Azure Storage account.
   • Select the “Monitoring” section from the left-hand menu.
   • Click on “Storage Analytics” and then select “Logging”.
   • Enable logging by toggling the switch to “On”.
   • Configure the desired retention period for the logs.
   • Save the changes.
2. Enable Storage Analytics Metrics:
   • In the same “Monitoring” section of the Azure Storage account, click on “Storage Analytics” and then select “Metrics”.
   • Enable metrics by toggling the switch to “On”.
   • Configure the desired retention period for the metrics.
   • Save the changes.
3. Enable Soft Delete for Blob Storage:
   • Navigate to the Azure Storage account and select the “Blob service” from the left-hand menu.
   • Click on “Data protection” and then select “Soft delete”.
   • Enable soft delete by toggling the switch to “On”.
   • Configure the desired retention period for the soft deleted blobs.
   • Save the changes.

​

Using CLI

1. Enable soft delete for Azure Blob Storage:
   • Use the following command to enable soft delete for a specific storage account:
     Copy

     Ask AI

     az storage account blob-service-properties update --account-name <storage_account_name> --enable-delete-retention true --delete-retention-days <retention_days>
     

     Replace <storage_account_name> with the name of your storage account and <retention_days> with the number of days you want to retain deleted blobs.
2. Enable logging for Azure Storage:
   • Use the following command to enable logging for a specific storage account:
     Copy

     Ask AI

     az storage logging update --account-name <storage_account_name> --log <log_settings>
     

     Replace <storage_account_name> with the name of your storage account and <log_settings> with the desired logging settings.
3. Enable firewall rules for Azure Storage:
   • Use the following command to add a firewall rule for a specific storage account:
     Copy

     Ask AI

     az storage account network-rule add --account-name <storage_account_name> --ip-address <ip_address>
     

     Replace <storage_account_name> with the name of your storage account and <ip_address> with the IP address you want to allow access from.

​

Using Python

1. Monitor and handle storage exceptions:
   • Implement exception handling in your Python code to catch and handle any storage-related exceptions that may occur.
   • Use the try-except block to catch specific exceptions like azure.core.exceptions.ResourceNotFoundError or azure.core.exceptions.ServiceRequestError.
   • Log the exceptions and take appropriate actions, such as retrying the operation or notifying the appropriate stakeholders.
2. Implement access control and security measures:
   • Use the Azure Identity library to authenticate and authorize access to Azure Storage resources.
   • Implement role-based access control (RBAC) to grant appropriate permissions to users or applications accessing the storage account.
   • Utilize Azure Key Vault to securely store and manage access keys or connection strings used by your Python scripts.
3. Optimize storage performance and cost:
   • Leverage Azure Blob Storage lifecycle management to automatically tier and archive data based on its age or access patterns.
   • Implement client-side parallelism in your Python code to improve upload and download speeds for large files.
   • Utilize Azure Blob Storage’s block blobs for efficient storage and retrieval of large amounts of unstructured data.