Azure生命周期管理区域问题：北欧存储账户无法迁移冷Blob至归档层

Hey there, let's break down why your lifecycle rule is failing and how to get this sorted out.

The Root Cause #

The error message spells it out clearly: your North Europe region currently doesn't support directly moving base blobs from the Cool storage tier to the Archive tier. This isn't an issue with your blob data or rule setup—it's a regional feature limitation from Azure. Even though all your blobs are already in the Cool tier, the platform doesn't allow this direct tier transition in North Europe right now.

Solutions to Try #

• Route through the Hot Tier first
  This is the most straightforward workaround:

  1. Create a lifecycle rule to move your Cool-tier blobs to the Hot tier first (use the tierToHot action for baseBlob).
  2. Wait for this rule to execute—you can track its status in the Azure Portal under your storage account's Data management > Lifecycle management section.
  3. Once all blobs are in the Hot tier, create a new lifecycle rule to move them to the Archive tier using the tierToArchive action.

• Verify if Regional Support Has Updated
  Azure rolls out features gradually across regions. Double-check if North Europe has since enabled Cool-to-Archive transitions for base blobs:

  • Navigate to your storage account in the Azure Portal → Data management → Lifecycle management.
  • Try creating a rule with tierToArchive for Cool blobs—if the option is now available, the limitation was temporary.

• Cross-Region Copy (If Cost Makes Sense)
  If you want to avoid using the Hot tier (due to higher storage costs), you can:

  1. Copy your Cool-tier blobs to a storage account in a region that supports Cool-to-Archive transitions (like West Europe).
  2. Set up a lifecycle rule in that new account to move the blobs to the Archive tier.
     Note: This will incur data transfer costs, so weigh this against Hot tier storage expenses before moving forward.

Quick Confirmation #

You already verified all blobs are in the Cool tier, so we can rule out invalid blob tiers as the cause. The core issue here is working around the regional limitation until Azure enables this feature in North Europe.

内容的提问来源于stack exchange，提问作者bater