Azure Storage Not Displaying Fix for Azure Portal Issues

If you're experiencing issues with Azure Storage not displaying, it's likely due to a misconfigured Azure Storage account.

The Azure Storage account must be enabled to display in the Azure portal.

To resolve the issue, check if your Azure Storage account is enabled for the Azure portal.

Ensure that the Azure Storage account is not set to read-only mode, as this can prevent it from displaying in the portal.

If your Azure Storage account is disabled, you can enable it by going to the Azure Storage account settings and clicking on the "Enable" button.

After enabling the account, refresh the Azure portal to see if the Azure Storage account is now displaying.

Troubleshooting Azure Storage issues can be a challenge, but knowing where to look can make all the difference. Azure Monitor records counts of different response types, such as NetworkError, ClientTimeoutError, or AuthorizationError, which can help you identify the issue.

Intermittent errors are normal, so don't be too quick to panic if you see some errors reported by the client application. These could be due to transient network conditions or application errors.

To understand storage-related status and error codes, check out the resources listed in the Azure documentation, including Common REST API error codes and service-specific error codes like Blob Service error codes and Queue Service error codes.

If your client application is receiving HTTP 404 (Not found) messages, it's likely because the object the client was attempting to use doesn't exist in the storage service. This could be due to various reasons, such as the client or another process previously deleting the object, a Shared Access Signature (SAS) authorization issue, or client-side JavaScript code not having permission to access the object.

Here are some possible reasons for an HTTP 404 (Not found) response:

If you're seeing an AuthorizationError in Azure Monitor metrics, it could be a sign of a Shared Access Signature (SAS) authorization issue. This means the client application is attempting to use a SAS key that doesn't include the necessary permissions for the operation.

In this case, investigate why your client application is attempting to perform an operation for which it hasn't been granted permissions.

One of the most common solutions to the Azure Storage not displaying issue is to check the account name and key. Make sure they are correct and match the Azure Storage account settings.

Incorrect account name and key can cause Azure Storage to fail to display, so double-checking these settings is essential. This is a simple yet crucial step that can resolve the issue quickly.

Another solution is to verify the Storage account's permissions. If the permissions are not set correctly, Azure Storage may not display. The article notes that the Storage account must have the "Blob (read, write, delete)" permission enabled.

If the issue persists, check the Azure Storage container's properties. The article mentions that the "Container public access level" should be set to "Public" to allow access to the storage. This setting can be found in the Azure Storage account's properties.

In some cases, Azure Storage may not display due to a mismatch between the Azure Storage account and the Azure subscription. The article notes that the Azure Storage account must be associated with the same Azure subscription as the Azure application.

For your interest: Check Onedrive Storage