Blob Storage Data Plane Operations Fail with ResourceNotFound Despite Successful Storage Account Creation (PAYG Subscription)

Will 0 Reputation points
2025-11-17T01:52:59.81+00:00

Issue Summary

I'm experiencing a strange issue where all blob storage data plane operations fail with ResourceNotFound errors, despite the storage account being successfully created and accessible via management plane operations.

Environment Details

  - Subscription Type: Pay-As-You-Go (PayAsYouGo__2014-09-01)_

  - Location: East US

  _- SKU: Standard__LRS

  - Kind: StorageV2

  - Creation Date: 2025-11-17

  - Provisioning State: Succeeded

  - Status: Available

  ## What Works

  1. Storage account creation via Azure CLI succeeds

  2. Management plane operations work correctly:

     - az storage account show returns correct information

     - az storage container-rm create successfully creates containers

     - az storage account blob-service-properties show returns properties

  3. Microsoft.Storage provider is registered and active

  4. Network configuration allows all access (no firewall restrictions)

  5. Shared key access is enabled (allowSharedKeyAccess = null/true)

  ## What Fails

  All data plane operations fail with the same error:

  ERROR: The specified resource does not exist.

  ErrorCode: ResourceNotFound

  Failed operations include:

  - az storage container list

  - az storage blob upload

  - az storage blob list

  - Python SDK operations using azure-storage-blob library

  ## Authentication Methods Tested

  All of the following authentication methods fail:

  1. Connection string with account key

  2. --account-key parameter in Azure CLI

  3. --auth-mode login (Azure AD)

  4. Python SDK with connection string

  ## Error Details

 

  Error Response:

  ```xml

  <?xml version="1.0" encoding="utf-8"?>

  <Error>

    <Code>ResourceNotFound</Code>

    <Message>The specified resource does not exist.</Message>

  </Error>

  Diagnostic Results

  Azure Portal's automated diagnostics found:

  - ✅ "No authentication or authorization issues found"

  - Suggested checking if shared key authorization is disabled

  - Verified: allowSharedKeyAccess is not disabled (null = enabled)

  What I've Tried

  1. ✅ Registered Microsoft.Storage provider

  2. ✅ Waited 10+ minutes for propagation

  3. ✅ Verified network settings (default action: Allow, no firewall rules)

  4. ✅ Checked shared key access (enabled)

  5. ✅ Tested with multiple authentication methods

  6. ✅ Verified blob service is enabled and available

  7. ✅ Created container via ARM API (az storage container-rm create)

  8. ✅ Verified storage account provisioning state is "Succeeded"

  Network Configuration

  {

    "bypass": "AzureServices",

    "defaultAction": "Allow",

    "ipRules": [],

    "virtualNetworkRules": []

  }

  Workaround

  I was able to create a storage account in a different subscription in the same tenant, and data

  plane operations work perfectly there. This suggests the issue is specific to the other subscription.

  Questions

  1. Is there a known limitation on blob storage data plane access for certain Pay-As-You-Go subscriptions?

  2. Are there subscription-level policies that could block data plane operations while allowing management plane?

  3. Is this a regional issue specific to East US at the time of creation?

  4. What additional diagnostics can I run to identify the root cause?

This is a standard Pay-As-You-Go subscription (not trial, student, or MSDN), so I would expect full access to blob storage services.

Any insights would be greatly appreciated!

Azure Blob Storage
Azure Blob Storage
An Azure service that stores unstructured data in the cloud as blobs.
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Q&A Assist
    2025-11-17T01:54:15.2866667+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    It appears that you are encountering a ResourceNotFound error for blob storage data plane operations despite successful management plane operations and the creation of the storage account. Here are some insights that may help you troubleshoot this issue:

    1. Check Container Existence: Ensure that the containers you are trying to access actually exist. The ResourceNotFound error can occur if the specified container or blob does not exist. You can verify this by using the Azure Portal or CLI to list the containers.
    2. Propagation Delay: Sometimes, there may be a propagation delay after creating a storage account or containers. Although you mentioned waiting for 10+ minutes, it might be worth waiting a bit longer or retrying the operations after some time.
    3. Subscription Policies: There could be subscription-level policies that restrict certain operations. It's advisable to check if there are any policies applied to your Pay-As-You-Go subscription that might limit data plane access.
    4. Regional Issues: While it seems unlikely, there could be temporary issues specific to the East US region. You might want to check Azure Service Health for any ongoing issues in that region.
    5. Authentication and Permissions: Since you have tested multiple authentication methods and verified that shared key access is enabled, ensure that the permissions associated with the authentication method you are using are sufficient for the operations you are attempting. For example, if using a SAS token, ensure it has the necessary permissions.
    6. Diagnostic Logs: Review diagnostic logs for any additional error messages or clues. Azure provides logs that can help identify issues related to authentication and authorization.
    7. Contact Support: If the issue persists, consider reaching out to Azure Support for further assistance, especially since you mentioned that operations work in a different subscription.

    In summary, verify the existence of the resources, check for any subscription policies, and consider reaching out to support if the problem continues.


    References:

    0 comments No comments

  2. Vallepu Venkateswarlu 1,065 Reputation points Microsoft External Staff Moderator
    2025-11-17T12:51:30.9266667+00:00

    Hi @Will,

    Welcome to Microsoft Q&A Platform. Thank you for reaching out & hope you are doing well.

    As I can see, you are unable to perform the below operations using Azure CLI commands even after creating the Storage Account and container:

    az storage container list

    az storage blob upload

    az storage blob list

    Can you please confirm if you are able to access the container and blobs via the Azure Portal? Double-check the configuration settings for the Blob service in the Azure Portal and ensure nothing is misconfigured that could cause an access issue.

    Note: Make sure to verify access before running the below commands, and ensure you are logged in to the correct subscription.

    Connect-AzAccount
    

    After logging in, verify which subscription you are connected to using the command below, and ensure it matches the subscription where your Storage Account exists:

    Get-AzContext
    

    If you face any errors with Azure CLI commands, please try the below Azure PowerShell Commands.

    Import-Module Az.Storage
    
    $StorageAccountName = "Test"
    $ResourceGroupName  = "venkatrg"
    $ContainerName      = "venkat"
    
    $LocalFilePath      = "C:\temp\sample.txt"   # File you want to upload
    $BlobName           = "sample.txt"           # Blob name inside container
    
    $Context = (Get-AzStorageAccount -AccountName $StorageAccountName -ResourceGroupName $ResourceGroupName).Context
    
    Write-Host "`n=== 1. List Storage Containers ==="
    Get-AzStorageContainer -Context $Context | Select-Object Name
    
    Write-Host "`n=== 2. Upload Blob ==="
    Set-AzStorageBlobContent `
        -File $LocalFilePath `
        -Container $ContainerName `
        -Blob $BlobName `
        -Context $Context `
        -Force
    
    Write-Host "`nBlob uploaded successfully!"
    
    Write-Host "`n=== 3. List Blobs in Container ==="
    Get-AzStorageBlob `
        -Container $ContainerName `
        -Context $Context | Select-Object Name
    

    Kindly let us know if the above helps or you need further assistance on this issue.

    Please Accept if the information was helpful. This will benefit others in the community as well.

    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.