Merge pull request #53997 from staleycyn/patch-2

Update blob storage module

Author: v-dirichards

learn-pr/wwl-azure/configure-blob-storage/includes/3-create-blob-containers.md

@@ -31,6 +31,8 @@ In the Azure portal, you configure settings to create a container for an Azure s
    - **Blob**: Allow anonymous public read access for the blobs only.
    - **Container**: Allow anonymous public read and list access to the entire container, including the blobs.
 
+> [!IMPORTANT]
+> The Blob and Container access levels have no effect unless the storage account's **Allow Blob anonymous access** setting is enabled. When disabled, all containers remain private regardless of their individual access level settings. Microsoft recommends keeping anonymous access disabled at the account level unless serving public content scenarios.
 
 
 

learn-pr/wwl-azure/configure-blob-storage/includes/4-create-blob-access-tiers.md

@@ -8,7 +8,7 @@ Let's examine characteristics of the blob access tiers.
 
 #### Hot tier
 
-The Hot tier is optimized for frequent reads and writes of objects in the Azure storage account. A good usage case is data that is actively being processed. An online tier optimized for storing data that is accessed or modified frequently. The hot tier has the highest storage costs, but the lowest access costs.
+The Hot tier is optimized for frequent reads and writes of objects in the Azure storage account. A good usage case is data that is actively being processed. The hot tier has the highest storage costs, but the lowest access costs.
 
 #### Cool tier
 
@@ -22,7 +22,7 @@ The Cold tier is also optimized for storing large amounts of infrequently access
 
 The Archive tier is an offline tier that's optimized for data that can tolerate several hours of retrieval latency. Data must remain in the Archive tier for at least 180 days or be subject to an early deletion charge. Data for the Archive tier includes secondary backups, original raw data, and legally required compliance information. This tier is the most cost-effective option for storing data. Accessing data is more expensive in the Archive tier than accessing data in the other tiers. 
 
-An archive tier doesn't allow you to read or modify the content of a blob directly. However, you do have access to its metadata, including index tags. To access the blob's content, you can assign it to the hot, cool, or cold tier to trigger the process referred to as rehydration.
+To access the blob's content, you can rehydrate it to the hot, cool, or cold tier using two methods: **Copy Blob** (recommended - creates a new blob in an online tier) or **Set Blob Tier** (changes tier in place). Both methods support Standard priority (up to 15 hours) or High priority (within 1 hour for objects under 10 GB, at higher cost). Use High priority for urgent data retrieval in disaster recovery scenarios.
 
 ### Compare access tiers
 

learn-pr/wwl-azure/configure-blob-storage/includes/5-add-blob-lifecycle-management-rules.md

@@ -1,17 +1,19 @@
 Every data set has a unique lifecycle. Early in the lifecycle, users tend to access some of the data in the set, but not all of the data. As the data set ages, access to all of the data in the set tends to dramatically reduce. Some data set stays idle in the cloud and is rarely accessed. Some data expires within a few days or months after creation. Other data is actively read and modified throughout the data set lifetime.
 
-Azure Blob Storage supports [lifecycle management](/azure/storage/blobs/lifecycle-management-policy-configure) for data sets. It offers a rich rule-based policy for GPv2 and Blob Storage accounts. You can use lifecycle policy rules to transition your data to the appropriate access tiers, and set expiration times for the end of a data set's lifecycle.
+Azure Blob Storage supports [lifecycle management](/azure/storage/blobs/lifecycle-management-policy-configure) for data sets. It offers a rich rule-based policy for GPv2 accounts and Premium block blob accounts. Legacy Blob Storage accounts are also supported, but GPv2 is recommended for new deployments. You can use lifecycle policy rules to transition your data to the appropriate access tiers, and set expiration times for the end of a data set's lifecycle.
 
 > [!VIDEO https://learn-video.azurefd.net/vod/player?id=ce48b339-bc3a-412a-bf97-fb8581084431]
 
 ### Things to know about lifecycle management
 
 You can use Azure Blob Storage lifecycle management policy rules to accomplish several tasks.
 
-- Transition blobs to a cooler storage tier (Hot to Cool, Hot to Archive, Cool to Archive) to optimize for performance and cost.
+- Transition blobs to a cooler storage tier (Hot to Cool, Hot to Cold, Hot to Archive, Cool to Cold, Cool to Archive, Cold to Archive) to optimize for performance and cost.
 
 - Delete current versions of a blob, previous versions of a blob, or blob snapshots at the end of their lifecycles.
 
+- Automatically transition blobs from Cool back to Hot when accessed. This setting optimizes for unpredictable access patterns without early deletion charges.
+
 - Apply rules to an entire storage account, to select containers, or to a subset of blobs using name prefixes or blob index tags as filters.
 
 #### Business scenario 

learn-pr/wwl-azure/configure-blob-storage/includes/8-determine-storage-pricing.md

@@ -15,11 +15,11 @@ Review the following billing considerations for an Azure storage account and Blo
 
 - **Performance tiers**. The Blob Storage tier determines the amount of data stored and the cost for storing that data. As the performance tier gets cooler, the per-gigabyte cost decreases.
 
-- **Data access costs**. Data access charges increase as the tier gets cooler. For data in the Cool and Archive tiers, you're billed a per-gigabyte data access charge for reads.
+- **Data access costs**. Data access charges increase as the tier gets cooler. For data in the Cool, Cold, and Archive tiers, you're billed a per-gigabyte data access charge for read actions.
 
 - **Transaction costs**. There's a per-transaction charge for all tiers. The charge increases as the tier gets cooler.
 
-- **Geo-replication data transfer costs**. This charge only applies to accounts that have geo-replication configured, including GRS and RA-GRS. Geo-replication data transfer incurs a per-gigabyte charge.
+- **Geo-replication data transfer costs**. This charge only applies to accounts that have geo-replication configured. Geo-replication data transfer incurs a per-gigabyte charge.
 
 - **Outbound data transfer costs**. Outbound data transfers incur billing for bandwidth usage on a per-gigabyte basis. This billing is consistent with general-purpose Azure storage accounts.
 

learn-pr/wwl-azure/configure-blob-storage/index.yml

@@ -5,7 +5,7 @@ metadata:
   prefetch-feature-rollout: true
   title: Configure Azure Blob Storage
   description: "Learn how to configure Azure Blob Storage, including tiers and object replication."
-  ms.date: 02/19/2026
+  ms.date: 03/23/2026
   author: wwlpublish
   ms.author: cynthist
   ms.topic: module