Data protection by resource type

The following table summarizes the Azure Storage data protection options according to the resources they protect.

Data protection optionProtects an account from deletionProtects a container from deletionProtects an object from deletionProtects an object from overwrites
Azure Resource Manager lockYesNoNoNo
Immutability policy on a blob versionYesYesYesYes
Immutability policy on a containerYesYesYesYes
Container soft deleteNoYesNoNo
Blob versioningNoNoYesYes
Blob soft deleteNoNoYesYes
Point-in-time restoreNoNoYesYes
Blob snapshotNoNoNoYes
Roll-your-own solution for copying data to a second accountNoYesYesYes

Understanding the nuances of data protection in Azure Storage reveals several operational insights and restrictions:

  • An Azure Resource Manager lock doesn't protect a container from deletion.
  • Storage account deletion fails if there is at least one container with version-level immutable storage enabled.
  • Container deletion fails if at least one blob exists in the container, regardless of whether policy is locked or unlocked.
  • Overwriting the contents of the current version of the blob creates a new version. An immutability policy protects a version's metadata from being overwritten.
  • While a legal hold or a locked time-based retention policy is in effect at container scope, the storage account is also protected from deletion.
  • Not currently supported for Data Lake Storage workloads.
  • AzCopy and Azure Data Factory are options that are supported for both Blob Storage and Data Lake Storage workloads. Object replication is supported for Blob Storage workloads only.

Comments

Post a Comment

Popular posts from this blog

Azure built-in roles for tables

Azure RBAC provides built-in roles for authorizing access to table data using Microsoft Entra ID and OAuth. Built-in roles that provide permissions to tables in Azure Storage include: Storage Table Data Contributor: Use to grant read/write/delete permissions to Table storage resources. Storage Table Data Reader: Use to grant read-only permissions to Table storage resources. To learn how to assign an Azure built-in role to a security principal, see Assign an Azure role for access to table data. To learn how to list Azure RBAC roles and their permissions, see List Azure role definitions. For more information about how built-in roles are defined for Azure Storage, see Understand role definitions. For information about creating Azure custom roles, see Azure custom roles. Only roles explicitly defined for data access permit a security principal to access table data. Built-in roles such as Owner, Contributor, and Storage Account Contributor permit a security principal to manage a storage acc...
Read more

Explore Dataflows Gen2 in Microsoft Fabric

  In Microsoft Fabric, you can create a Dataflow Gen2 in the Data Factory workload or Power BI workspace, or directly in the lakehouse. Since our scenario is focused on data ingestion, let's look at the  Data Factory  workload experience. Dataflows Gen2 use Power Query Online to visualize transformations.  1. Power Query ribbon Dataflows Gen2 support a wide variety of data source connectors. Common sources include cloud and on-premises relational databases, Excel or flat files, SharePoint, SalesForce, Spark, and Fabric lakehouses. Then there are numerous data transformations possible, such as: Filter and Sort rows Pivot and Unpivot Merge and Append queries Split and Conditional split Replace values and Remove duplicates Add, Rename, Reorder, or Delete columns Rank and Percentage calculator Choose Top N and Bottom N You can also create and manage data source connections, manage parameters, and configure the default data destination in this ribbon. 2. Queries pane The ...
Read more

Select and configure an appropriate method for access to Azure Blobs

Azure Storage supports using Microsoft Entra ID to authorize requests to blob data. With Microsoft Entra ID, you can use Azure role-based access control (Azure RBAC) to grant permissions to a security principal, which may be a user, group, or application service principal. The security principal is authenticated by Microsoft Entra ID to return an OAuth 2.0 token. The token can then be used to authorize a request against the Blob service. Authorization with Microsoft Entra ID is available for all general-purpose and Blob storage accounts in all public regions and national clouds. Only storage accounts created with the Azure Resource Manager deployment model support Microsoft Entra authorization. For optimal security, Microsoft recommends using Microsoft Entra ID with managed identities to authorize requests against blob, queue, and table data, whenever possible. Authorization with Microsoft Entra ID and managed identities provides superior security and ease of use over Shared Key author...
Read more