Cannot import name 'AccessTokenInfo' from 'azure.core.credentials'

[miladh]

• Package Name: az-ai-ml
• Package Version: 1.19.0
• Operating System: Linux
• Python Version: 3.11

Describe the bug

Note

Apologies if this issue should have been created in a different repository. Please let me know if I should create this ticket elsewhere.

In this PR, the minimum version of azure-core was updated to include the new SupportTokenInfo protocol and AccessTokenInfo class. However, when attempting to install the Azure ML extension using:

az extension add --name ml

the following error occurs:

cannot import name 'AccessTokenInfo' from 'azure.core.credentials'

As this issue is currently disrupting our CI pipelines, we would be grateful for any guidance you can provide to help us address it promptly.

Possible Cause

This issue seems to arise because the Azure ML extension installs azure_identity-1.18.0, which relies on AccessTokenInfo from azure.core.credentials. However, azure-cli version 2.64.0 still uses an older version of azure-core (1.28.0), and hence the error above is thrown.

For reference, here’s the azure-cli requirements file.

To Reproduce
Steps to reproduce the behavior:

1. Install az cli
2. Run az extension add --name ml

[github-actions]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Azure/azure-ml-sdk @azureml-github.

[levu74]

Yes, same for me. It's now a blocker for my CI pipelines.

[rikwatson]

This is no blocking all my ML pipelines

[MetelStairs]

This is blocking our pipelines also

[dionhaefner]

Thanks for the pointer to azure-identity @miladh – this works for me as a workaround on CI:

$ az extension add --upgrade --name ml -y
$ sudo /opt/az/bin/python3 -m pip install azure-identity==1.17.1

(use at your own risk)

[rikwatson]

Also a blocker for me (muliple training pipelines)

[pimonteiro]

Thanks for the pointer to azure-identity @miladh – this works for me as a workaround on CI:

$ az extension add --upgrade --name ml -y
$ sudo /opt/az/bin/python3 -m pip install azure-identity==1.17.1

(use at your own risk)

This workaround did work on our case.

[pvaneck]

Appears that there is some intermingling of dependencies.

Looking at where CLI extension dependencies are installed for me, (~/.azure/cliextensions/ml), I do see that there are compatible versions of azure-core and azure-identity installed. However, the versions of these packages installed in the azure-cli Python virtual environment (e.g. /opt/az/lib/python3.11/site-packages/) seem to take precedence at runtime causing incompatibilities.

I mentioned this in the linked azure-cli issue, but I think something may need updating in the dependency resolution logic when installing an extension. Ideally, azure-cli extension Python requirements should remain compatible with the base azure-cli requirements when the extension is installed (i.e. azure-identity 1.17.1 should automatically have been installed with the ML extension).

I believe the workaround, as mentioned above, is to install an older version of azure-identity in whatever virtual environment azure-cli is using.

Example workarounds:

Linux:

sudo /opt/az/bin/python3 -m pip install azure-identity==1.17.1

Windows (in elevated/administrator terminal):

C:\"Program Files (x86)"\"Microsoft SDKs"\Azure\CLI2\python.exe -m pip install azure-identity==1.17.1

Not sure about Mac, but probably just need to run the python executable somewhere in /opt/homebrew/Cellar/azure-cli/<version>/libexec/ ?

I think you can glean the location of the environment your azure-cli is using based on the error message:

cannot import name 'AccessTokenInfo' from 'azure.core.credentials' (/opt/az/lib/python3.11/site-packages/azure/core/credentials.py) -> Need to use python executable somewhere in /opt/az

[levu74]

@pvaneck for Linux, the workaround works. On my Windows machine, I ran the command (64-bit version), but it doesn't work.

[toby-coleman]

Same issue here - stopping all of our CI pipelines.

[adtcode216]

@toby-coleman As a temporary solution, you can add the following to your requirements.txt for a quick CI pipelines fix:

azure-identity==1.17.1

[steflommen]

@pvaneck for Linux, the workaround works. On my Windows machine, I ran the command (64-bit version), but it doesn't work.

For our azure pipelines the following command works
C:\"Program Files"\"Microsoft SDKs"\Azure\CLI2\python.exe -m pip install azure-identity==1.17.1

[PratibhaShrivastav18]

This issue has been resolved. Please retry.
az extension add --name ml --version 2.30.0

[ezpzzz19]

please correct me if I am misunderstanding but this solution assumes that we are using / installed the azure-cli package. In our case we are not.
Will there be a fix directly on the newest version of azure-identity to solve the problem ? We would ideally want to stay up to date with the newest version of azure-identity

[pvaneck]

@ezpzzz19 The latest version of azure-identity already requires the version of azure-core which contains the necessary imports. You shouldn't be encountering this issue if you are installing normally through pip as the dependency resolution will ensure you have compatible versions of azure-core and azure-identity.

If you are seeing this issue outside of the context of Azure CLI or the Azure CLI ML extension, then please open another issue.

[JSchoeck]

The mentioned issue #37790 has two fixes that work for me:

1. Pin azure-identity to 1.17.1 and azure-core to <1.31.0 or
2. Disable Application Insights for the web app:
   Application Insights [Preview]
   Collect application monitoring data using Application Insights
   --> Disable

[jeremydvoss]

Deployment has resumed. I will update again when fully deployed. Once fully deployed, you will be able to use the new version of Azure Core even when using Autoinstrumentation (The feature the previous comment says to disable). Until then, using Manual Instrumentation is recommended if you need the latest version of Azure Core.

EDIT: I am talking about customers that get this error on App Service using App Insights Python Autoinstrumentation. For example, see this issue. Some such customers have linked this issue. However, I now see that some customers in this thread are experiencing this in pipelines instead of App Service. This appears to be completely separate.

[achauhan-scc]

@jeremydvoss / @miladh - Are we still facing the similar issue with latest version of CLI extension 2.34.0?

[github-actions]

Hi @miladh. Thank you for opening this issue and giving us the opportunity to assist. To help our team better understand your issue and the details of your scenario please provide a response to the question asked above or the information requested above. This will help us more accurately address your issue.

[miladh]

@jeremydvoss / @miladh - Are we still facing the similar issue with latest version of CLI extension 2.34.0?

Using version 2.33.1 currently and no longer facing the issue.

[jeremydvoss]

For those getting the same error on App Service despite specifying the right version of azure-core==1.32.0, that issue has been fixed.

Since the separate issue of az-ai-ml appears to be solved with version 2.33.1. I recommend closing this issue.

[github-actions]

Hi @miladh. Thank you for opening this issue and giving us the opportunity to assist. We believe that this has been addressed. If you feel that further discussion is needed, please add a comment with the text "/unresolve" to remove the "issue-addressed" label and continue the conversation.

[github-actions]

Hi @miladh, since you haven’t asked that we /unresolve the issue, we’ll close this out. If you believe further discussion is needed, please add a comment /unresolve to reopen the issue.