cannot import name 'blockblobservice' from 'azure.storage.blob'

Not specified by the original author.

TL;DR: BlockBlobService was the v2-track client and v12 deleted it. Either migrate to BlobServiceClient (recommended) or pin azure-storage-blob<3 to keep the old API.

ImportError: cannot import name 'BlockBlobService' from 'azure.storage.blob'

Fix it

1. Decide: migrate or pin. Migrating is better for anything you will maintain.
2. To migrate: pip install -U azure-storage-blob, then replace BlockBlobService(connectionstring=...) usage with BlobServiceClient.fromconnection_string(...), and method calls per the v12 migration guide. Expected: imports succeed.
3. To pin (short-term only): pip install "azure-storage-blob<3". Expected: BlockBlobService imports again.
4. Record the choice in requirements so the next fresh install is deterministic.

When this applies

• The code imports BlockBlobService and pip shows azure-storage-blob 12.x.

When it doesn't

• pip shows 2.x and the import still fails: namespace conflict; see the azure.identity namespace skill.
• You are writing new code: use BlobServiceClient from the start.

Compatibility

• v12: azure-storage-blob >= 12.0. Legacy: azure-storage-blob 2.x.

Why it happens

Major-version SDK rewrites drop old classes. v12 kept the package name but replaced the entire surface, so old imports fail loudly instead of subtly.

Edge cases

• Some third-party libraries still import BlockBlobService internally; pinning may be forced until they migrate.
• Connection strings from the portal work with both tracks, so auth config does not need to change.

Reported in GitHub (gh:wazuh/wazuh#24641): ImportError: cannot import name 'BlockBlobService' from 'azure.storage.blob' (wazuh/wazuh#24641). The verified fix: Asked on Stack Overflow by developers running old Azure samples on new installs. The verified answer: BlockBlobService was removed in v12, so either pin azure-storage-blob to the 2.x track or migrate to BlobServiceClient. Source: the linked Stack Overflow thread. Source: https://github.com/wazuh/wazuh/issues/24641 Thread ref: gh:wazuh/wazuh#24641

Not specified by the original author.

TL;DR: BlobServiceClient only exists in azure-storage-blob v12+. You have the legacy 2.x track installed (it provides BlockBlobService instead). Upgrade with pip install -U azure-storage-blob and the import works.

ImportError: cannot import name 'BlobServiceClient' from 'azure.storage.blob'

Fix it

1. Check the version: pip show azure-storage-blob. Expected: 2.x if you hit this.
2. Upgrade: pip install -U azure-storage-blob. Expected: version 12.x.
3. Verify: python -c "from azure.storage.blob import BlobServiceClient; print('ok')". Expected: ok.
4. Update your code to the v12 API (connection string or credential based client); v2 and v12 APIs are not interchangeable.

When this applies

• pip shows azure-storage-blob 2.x and you want the modern API.

When it doesn't

• pip already shows 12.x: then something else shadows the package (namespace conflict); check azure.path.
• You intentionally target the legacy API: keep 2.x and use BlockBlobService.

Compatibility

• azure-storage-blob >= 12.0. Python 3.8+.

Why it happens

Microsoft rebooted the storage SDK as v12 with a new object model. The 2.x track stayed on PyPI for back-compat, and old pins or tutorials keep installing it.

Edge cases

• The v12 migration guide covers renamed methods (createblobfrompath becomes uploadblob, etc.); budget time for the rewrite, not just the import.
• azure-storage (the old meta-package) pulls in 2.x; remove it.

Reported in Stack Overflow (so:58768443): error importing &#39;BlobServiceClient&#39; from &#39;azure.storage.blob&#39;. The verified fix: Asked on Stack Overflow by developers following current docs whose BlobServiceClient import failed. The verified answer: the installed azure-storage-blob is the legacy 2.x track which has no BlobServiceClient, so upgrade to v12 with pip install -U azure-storage-blob. Source: the linked Stack Overflow thread. Source: https://stackoverflow.com/questions/58768443/error-importing-blobserviceclient-from-azure-storage-blob Thread ref: so:58768443

Not specified by the original author.

TL;DR: Same family as the azure.identity namespace issue: a legacy azure/init.py or a pip/python mismatch hides the namespace. Uninstall legacy azure packages, reinstall azure-storage-blob with python -m pip, and verify the interpreter.

ModuleNotFoundError: No module named 'azure.storage'

Fix it

1. Check alignment: python -m pip show azure-storage-blob and python -c "import sys; print(sys.executable)". Expected: same interpreter both sides.
2. Remove legacy shadowing packages: pip uninstall azure-storage azure-mgmt-storage azure-common. Expected: no more pkgresources-style azure/init_.py.
3. Reinstall: python -m pip install --force-reinstall azure-storage-blob. Expected: from azure.storage.blob import BlobServiceClient works.
4. Verify in a fresh shell, not just the current one, to rule out stale PYTHONPATH.

When this applies

• pip shows azure-storage-blob but azure.storage does not import.
• Old azure-* packages are also installed.

When it doesn't

• pip does not show azure-storage-blob: install it.
• The import works but auth fails: credential problem, not this.

Compatibility

• azure-storage-blob 12.x; Python 3.8+.

Why it happens

All Azure SDK packages share the azure. namespace. One legacy package with a real init.py breaks namespace resolution for every other azure. package.

Edge cases

• The old azure-storage meta-package (2.x track) is the most common culprit; it must go before v12 resolves.
• Editable installs of local azure packages can also shadow; check pip list for -e entries.

Reported in GitHub (gh:azure/azure-sdk-for-python#20981): azure.storage module import failure (azure/azure-sdk-for-python#20981). The verified fix: Asked on Stack Overflow by developers whose azure-storage-blob install did not provide azure.storage. The verified answer: a namespace-package clash with legacy azure packages or a mismatched interpreter, so clean-reinstall and align pip with the running Python. Source: the linked Stack Overflow thread. Source: https://github.com/azure/azure-sdk-for-python/issues/20981 Thread ref: gh:azure/azure-sdk-for-python#20981