:: BLOB STORAGE NO LONGER WORKING

Hola @Jose Contreras Admin Tenant

Gracias por ponerte en contacto con Microsoft Q&A.

Entiendo que hasta ayer podías acceder a los contenedores de Azure Blob Storage tanto desde tu máquina local como desde el portal de Azure. Sin embargo, a partir de hoy, los contenedores ya no son visibles y estás recibiendo un error que dice "La solicitud no está autorizada". También entiendo que tienes privilegios administrativos en la suscripción y que el problema ocurre de manera consistente en diferentes métodos de acceso.

Para ayudar con la investigación, ¿podrías por favor proporcionar la siguiente información?

El mensaje de error exacto y el código de error (si está disponible).

Una captura de pantalla del error desde el portal de Azure.

El ID de la suscripción y el nombre de la cuenta de almacenamiento afectada.

Una vez que tengamos los detalles solicitados, revisaremos la configuración más a fondo y te ayudaremos a identificar la causa raíz.

Agradecemos tu paciencia y esperamos tu respuesta.

Gracias,

Venkat.M

Hi Jose,

Since the storage account was working yesterday and you are now receiving a "Request is not authorized" error and can no longer view containers, the issue is most likely related to an authentication, authorization, or access configuration change.

Even if you are a subscription administrator, Blob Storage access is governed by data-plane permissions and the authentication method being used. I recommend checking the following:

Key Areas to Verify

1. Authentication Method Determine how you're accessing the storage account:

• Azure Portal (Microsoft Entra ID authentication)
• Azure Storage Explorer
• Application/SDK
• Connection string or Shared Key authentication
• SAS token authentication

If storage account keys were regenerated, SAS tokens expired, or client credentials changed, container listing can fail immediately.

2. SAS Token Validation If you're using a SAS token, verify that:

• The token has not expired.
• The required permissions are included (such as Read/List where applicable).
• The token format is correct and has not been modified.

3. Blob Data Permissions Confirm that your identity has the necessary Blob Storage data permissions. Typical roles include:

• Storage Blob Data Contributor
• Storage Blob Data Owner

Subscription-level administrative access alone may not provide the required data-plane permissions.

4. Network and Access Restrictions Check whether any recent changes were made to:

• Storage account firewall settings
• Virtual network restrictions
• Private endpoints
• DNS configuration

A networking change can prevent container enumeration even when authentication appears correct.

5. Service Health and Diagnostics Review Azure service health and storage diagnostics to determine whether a platform-side issue is affecting access before making configuration changes.

Information Needed for Further Troubleshooting

To help identify the exact cause, please provide:

1. The complete error message and error code (for example, AuthorizationFailure, AuthenticationFailed, or another specific code).
2. How you're accessing the storage account (Azure Portal, Storage Explorer, application, etc.).
3. The authentication method being used (Entra ID, Shared Key, connection string, or SAS token).
4. Whether any firewall, networking, or private endpoint changes were made recently.
5. Whether the issue occurs in an InPrivate/Incognito browser session.
6. Whether all containers are affected or only specific containers.

Helpful References

• Azure Blob Storage introduction
• Azure Storage overview

Once you provide the exact error code and authentication method, we can narrow down the root cause and recommend the most relevant troubleshooting steps.

Hello @Jose Contreras Admin Tenant,

the most likely cause is that your public IP changed and is no longer allowed by the storage account firewall. The second most likely is that you were relying on inherited permissions and now need an explicit Storage Blob Data Owner role.

If updating the firewall doesn't resolve it, let me know:

• whether the storage account is set to Enabled from selected virtual networks and IP addresses or All networks,
• and the exact text under Error details (especially the Request ID and any additional error information). That should make it possible to narrow it down further.