Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Connect-MgGraph -Identity returns Error connecting to MS Graph Invalid JWT access token #3207

Open
deniscooper opened this issue Mar 4, 2025 · 3 comments
Labels
status:duplicate A duplicate issue type:bug A broken experience

Comments

@deniscooper
Copy link

Describe the bug

Running from Azure Automation Account Powershell 7.2 using Graph module version
2.26.1.

When connecting to graph using a system managed identity of the automation account, it throws an error stating invalid JWT access token

Expected behavior

This worked in previous graph module version, but stopped working since upgrading modules.

Expected behaviour is to connect to graph using system managed identity

How to reproduce

  1. From Azure Automation using Powershell 7.2 runtime environment
  2. Run connect-mggraph -identity
  3. error thrown is invalid jwt

SDK Version

2.26.1.

Latest version known to work for scenario above?

Previous version worked, but i didn't make a note of the version number

Known Workarounds

No response

Debug output

Click to expand log ```
</details>


### Configuration

_No response_

### Other information

_No response_
@deniscooper deniscooper added status:waiting-for-triage An issue that is yet to be reviewed or assigned type:bug A broken experience labels Mar 4, 2025
@deniscooper
Copy link
Author

seems to work if running inside powershell 7.4

@gavinbarron
Copy link
Member

This looks to be a duplicate of #3151

@12Knocksinna
Copy link

It is a duplicate of 3151

@timayabi2020 timayabi2020 added status:duplicate A duplicate issue and removed status:waiting-for-triage An issue that is yet to be reviewed or assigned labels Mar 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status:duplicate A duplicate issue type:bug A broken experience
Projects
None yet
Development

No branches or pull requests

4 participants