Azure Blob Storage immutability policy: Lock policy confirmation not working in Spanish UI

Adrián Martínez Martín 20 Reputation points
2026-10-26T17:18:37.08+00:00

While working with Azure Blob Storage immutability policies in an official Microsoft certification exam lab, I encountered an issue when attempting to lock an existing time-based retention policy. With the Azure Portal interface configured in Spanish, the confirmation dialog did not allow me to complete the locking operation. I tried entering both "Sí" and "yes", but the policy remained unlocked. After switching the Azure Portal language to English, I was able to complete the same operation successfully. Has anyone experienced similar localization-related behavior when locking immutability policies? Could this be related to the portal's language configuration, confirmation validation, or the exam lab environment?

Solution / Workaround I resolved the issue using the following steps:

Open Azure Portal.

Navigate to Settings → Language + region.

Change the interface language to English and apply the change.

Return to the storage account and locate the affected container.

Open Access policy and select Lock policy for the existing unlocked retention policy.

Enter "Yes" in the confirmation dialog and complete the operation.

Verify that the policy status is now Locked.

Result: The policy was successfully locked after changing the interface language.

Important: This behavior was observed in an official Microsoft certification exam. I have not independently reproduced it in a separate production Azure environment, so I cannot confirm whether this is a general Azure Portal localization issue or something specific to the exam lab environment. I am sharing the workaround in case it helps other users encountering similar confirmation problems during their exams.

Azure Blob Storage
Azure Blob Storage

An Azure service that stores unstructured data in the cloud as blobs.

0 comments No comments

Answer accepted by question author

AI answer

2026-10-26T17:19:40.48+00:00

Changing the Azure portal display language to English and entering Yes is a valid workaround for this exam-lab issue, but the available Microsoft documentation does not establish a general defect in the Spanish portal.

What is documented

For a container-scoped, time-based retention policy, the supported portal workflow is:

  1. Open the container.
  2. Select Access policy.
  3. Under Immutable blob versions, locate the unlocked policy.
  4. Select More → Lock policy.
  5. Confirm the operation.
  6. Verify that the policy is shown as locked. ^1^

The documentation only says to confirm the operation; it does not document whether the confirmation field must accept Sí, Yes, or another localized value. Therefore, the result establishes an effective workaround, but not whether the underlying problem was:

  • Spanish confirmation validation,
  • stale or partially localized portal code, or
  • a constraint in the certification lab environment.

Important consequence of locking

Locking is effectively irreversible: after the policy is locked, it cannot be deleted and its retention period cannot be shortened. The retention interval can only be extended, and protected blobs cannot be deleted until their retention expires. Review the policy duration carefully before selecting Lock policy. ^1^

If this happens in another exam

Use the same non-destructive workaround:

  1. Azure portal → Settings → Language + region.
  2. Change the display language to English and apply it.
  3. Return to the container’s Access policy.
  4. Select Lock policy, enter Yes, and submit.
  5. Confirm that the status changes to Locked.

Also record the approximate time, selected portal language, exact text entered, and screenshots if exam rules permit. Microsoft directs candidates who encounter lab problems to submit them through the Exam item challenge process so the issue can be investigated. ^2^

Outside an exam environment

If the portal confirmation still fails in a normal Azure subscription, the policy can be locked with Azure CLI by retrieving its current ETag and passing it to the lock operation:

etag=$(az storage container immutability-policy show \
  --account-name <storage-account> \
  --container-name <container> \
  --query etag --output tsv)

az storage container immutability-policy lock \
  --resource-group <resource-group> \
  --account-name <storage-account> \
  --container-name <container> \
  --if-match "$etag"

Use this only after confirming the retention settings because the same irreversible locking behavior applies. ^1^


References

  1. Configuración de directivas de inmutabilidad para contenedores - Azure ...
  2. Exam frequently asked questions
AI-generated content may be incorrect. Read our transparency notes for more information.

Was this answer helpful?

1 person found this answer helpful.

1 additional answer

Sort by: Most helpful
  1. Jose Benjamin Solis Nolasco 12,861 Reputation points Volunteer Moderator
    2026-10-26T18:35:27.67+00:00

    Welcome to Microsoft Q&A

    Hello @Adrián Martínez Martín

    Thank you for sharing your findings and workaround.

    Based on the information provided, I am not aware of any documented issue where the Azure Portal Spanish localization prevents locking an Azure Blob Storage immutability policy. The official documentation describes the confirmation step but does not specify language-specific behavior for the confirmation dialog.

    Since:

    • The operation failed in the Spanish portal experience.
    • The same operation succeeded after switching the portal language to English.
    • The issue was observed in a certification lab environment and has not been reproduced in a standard Azure subscription.

    It's difficult to determine whether this was:

    • A localization issue in the Azure Portal,
    • A temporary portal/UI validation issue,
    • Or a condition specific to the exam lab environment.

    Your workaround of switching the portal language to English and entering "Yes" appears to be a reasonable approach if another candidate encounters the same behavior.

    For users outside a certification environment, if the portal UI continues to reject the confirmation, it may be worth testing in another browser, using an InPrivate session, or performing the operation through Azure CLI or PowerShell to determine whether the issue is portal-specific.

    Thank you again for documenting the behavior and workaround, as it may help others who encounter the same issue during training or certification labs.

    Reference

    If my answer helped you resolve your issue, please consider marking it as the correct answer. This helps others in the community find similar solutions.

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.