How to fix azure login?

Hossam Amer 0 Reputation points Microsoft Employee
2023-10-29T21:09:19.43+00:00
During handling of the above exception, another exception occurred:
 
Traceback (most recent call last):
  File "/home/hossamamer/.local/share/virtualenvs/pika-KPhqXolf/bin/pika", line 33, in <module>
    sys.exit(load_entry_point('pika', 'console_scripts', 'pika')())
  File "/home/hossamamer/workspace/Pika_workspace/pika/pika/main.py", line 191, in main
    ado_cli.schedule_pikapipelines_job(
  File "/home/hossamamer/workspace/Pika_workspace/pika/pika/ado_cli.py", line 92, in schedule_pikapipelines_job
    raise ValueError(f'Failed to schedule ADO job:\n{e}')
ValueError: Failed to schedule ADO job:
ERROR: TF401444: Please sign-in at least once as 60241f7b-a00b-4a02-92bd-975bf6ab4b6d\hossamamer@microsoft.com in a web browser to enable access to the service.


I do azure login with success but still facing this error

Not Monitored
Not Monitored
Tag not monitored by Microsoft.
36,974 questions
0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. Dr. S. Gomathi 650 Reputation points MVP
    2023-10-30T11:39:09.3666667+00:00

    Oh, I see you're having a bit of trouble with Azure login there. That error message is pointing towards an authentication issue, even though you've mentioned that you've logged in successfully through Azure CLI.

    First things first, let’s make sure you’re actually logged into the right account. You can run az login and then az account show to double-check that. Sometimes, it’s the simplest things that trip us up!

    Now, the error is also hinting at a possible issue with Azure DevOps (ADO). If you’re using a Personal Access Token (PAT) in your script, you might want to make sure that it’s still valid and has the right permissions. You can manage and check your PATs on your Azure DevOps account settings.

    The error message is pretty clear about trying to sign in through a web browser. So, give that a shot! Go to Azure DevOps, log in with your account (60241f7b-a00b-4a02-92bd-975bf6ab4b6d[hossamamer@microsoft.com](hossamamer@microsoft.com)), and see if that clears things up.

    Also, don’t forget to check your network and VPN settings. Sometimes they can interfere with authentication processes.

    And lastly, it might be a good idea to make sure that your Azure CLI and any extensions you’re using are up to date. Outdated tools can sometimes cause unexpected issues.

    If you’ve tried all of this and it’s still not working, it might be time to reach out to Microsoft Support. They should be able to help you sort this out.

    Hope this helps, and you get back on track soon!

    0 comments No comments

  2. Hossam Amer 0 Reputation points Microsoft Employee
    2023-10-30T11:55:33.19+00:00
    az account show shows the necessary accounts
    
    

    Now, the error is also hinting at a possible issue with Azure DevOps (ADO). If you’re using a Personal Access Token (PAT) in your script, you might want to make sure that it’s still valid and has the right permissions. You can manage and check your PATs on your Azure DevOps account settings.

    How to check this?

    The error message is pretty clear about trying to sign in through a web browser. So, give that a shot! Go to Azure DevOps, log in with your account (60241f7b-a00b-4a02-92bd-975bf6ab4b6dhossamamer@microsoft.com), and see if that clears things up.

    How to do this?

    I tried to be on MSFT VPN and it is the same thing.

    I use az 2.0

    0 comments No comments

  3. Hossam Amer 0 Reputation points Microsoft Employee
    2023-10-30T12:52:34.8866667+00:00

    Now, the error is also hinting at a possible issue with Azure DevOps (ADO). If you’re using a Personal Access Token (PAT) in your script, you might want to make sure that it’s still valid and has the right permissions. You can manage and check your PATs on your Azure DevOps account settings.

    I use a PAT that has full access.. But do you know the link to check that?

    The error message is pretty clear about trying to sign in through a web browser. So, give that a shot! Go to Azure DevOps, log in with your account (60241f7b-a00b-4a02-92bd-975bf6ab4b6dhossamamer@microsoft.com), and see if that clears things up.

    Still cannot check?

    0 comments No comments