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

"az ad app permission admin-consent" returns "service unavailable" when logged with a service principal #15967

Closed
G0t-t0 opened this issue Nov 18, 2020 · 2 comments

Comments

@G0t-t0
Copy link

G0t-t0 commented Nov 18, 2020

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Describe the bug
"az ad app permission admin-consent" returns "service unavailable" when logged in with a service principal but works fine with a regular user.

To Reproduce
I guess just launch the following command line while logged in with a service principal :

az ad app permission admin-consent --id {}

Expected behavior
To actually validate the grants in the api permissions section of the app in the active directory

Environment summary

Ubuntu Bullseye - bash for windows
azure-cli versions : {                                 
  "azure-cli": "2.14.0",          
  "azure-cli-core": "2.14.0",     
  "azure-cli-telemetry": "1.0.6", 
  "extensions": {}                
}   

Additional context

  • Both the user used to test and the service principal are global administrator on the Active Directory.
  • it's an active directory B2C
  • the whole app and its apis were created by the same service principal using the graph api
@ghost ghost added needs-triage This is a new issue that needs to be triaged to the appropriate team. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Nov 18, 2020
@yonzhan yonzhan added Graph az ad and removed needs-triage This is a new issue that needs to be triaged to the appropriate team. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Nov 18, 2020
@yonzhan yonzhan added this to the S180 milestone Nov 18, 2020
@yonzhan
Copy link
Collaborator

yonzhan commented Nov 18, 2020

az ad

@yonzhan yonzhan modified the milestones: S180, S181 Dec 5, 2020
@yonzhan yonzhan modified the milestones: S181, S182 Dec 31, 2020
@yonzhan yonzhan modified the milestones: S182, S183 Feb 6, 2021
@yonzhan yonzhan modified the milestones: S183 - For Ignite, S184 Feb 26, 2021
@yonzhan yonzhan modified the milestones: S184, S185 Mar 14, 2021
@yonzhan yonzhan modified the milestones: S185, S186 Apr 2, 2021
@yonzhan yonzhan modified the milestones: S186, S187 Apr 24, 2021
@yonzhan yonzhan modified the milestones: S187, S188 May 19, 2021
@yonzhan yonzhan modified the milestones: S188, S189 Jun 12, 2021
@yonzhan yonzhan modified the milestones: S189, Jul 2021 (2021-08-03) Jul 2, 2021
@jiasli
Copy link
Member

jiasli commented Jul 8, 2021

Please see #12137 (comment) for the explanation and workaround.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants