This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az ad app permission admin-consent
Errors:
Not Found(<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/>
<title>404 - File or directory not found.</title>
<style type="text/css">
<!--
body{margin:0;font-size:.7em;font-family:Verdana, Arial, Helvetica, sans-serif;background:#EEEEEE;}
fieldset{padding:0 15px 10px 15px;}
h1{font-size:2.4em;margin:0;color:#FFF;}
h2{font-size:1.7em;margin:0;color:#CC0000;}
h3{font-size:1.2em;margin:10px 0 0 0;color:#000000;}
#header{width:96%;margin:0 0 0 0;padding:6px 2% 6px 2%;font-family:"trebuchet MS", Verdana, sans-serif;color:#FFF;
background-color:#555555;}
#content{margin:0 0 0 2%;position:relative;}
.content-container{background:#FFF;width:96%;margin-top:8px;padding:10px;position:relative;}
-->
</style>
</head>
<body>
<div id="header"><h1>Server Error</h1></div>
<div id="content">
<div class="content-container"><fieldset>
<h2>404 - File or directory not found.</h2>
<h3>The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable.</h3>
</fieldset></div>
</div>
</body>
</html>
)
To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.
-
Put any pre-requisite steps here...
-
API=00000002-0000-0000-c000-000000000000
-
RWDDR=78c8a3c8-a07e-4b9e-af1b-b5ccab50a175=Scope
-
RWDR=aaff0dfd-0295-48b6-a5cc-9f465bc87928=Role
-
RWDDS=78c8a3c8-a07e-4b9e-af1b-b5ccab50a175=Role
-
az ad app permission add --api $API --id <sp-id> --api-permissions $RWDDS $RWDDR $RWDR
-
az ad app permission admin-consent --id {}
Expected Behavior
Environment Summary
Linux-5.12.1-arch1-1-x86_64-with-glibc2.33
Python 3.9.5
Installer:
azure-cli 2.25.0
Extensions:
azure-devops 0.17.0
aks-preview 0.4.57
log-analytics-solution 0.1.1
vm-repair 0.3.2
log-analytics 0.2.1
Additional Context
Adding graph api directory read write permissions.
Also tried with microsoft graph - same error as above.
Trying across different tenants also yield the same error.
This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az ad app permission admin-consentErrors:
To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.
Put any pre-requisite steps here...
API=00000002-0000-0000-c000-000000000000RWDDR=78c8a3c8-a07e-4b9e-af1b-b5ccab50a175=ScopeRWDR=aaff0dfd-0295-48b6-a5cc-9f465bc87928=RoleRWDDS=78c8a3c8-a07e-4b9e-af1b-b5ccab50a175=Roleaz ad app permission add --api $API --id <sp-id> --api-permissions $RWDDS $RWDDR $RWDRaz ad app permission admin-consent --id {}Expected Behavior
Environment Summary
Additional Context
Adding graph api directory read write permissions.
Also tried with microsoft graph - same error as above.
Trying across different tenants also yield the same error.