dingmeng-xue
commented
3 years ago @skippernl , thanks for reporting. How did you trigger Connect-AzAccount? What parameter is used?
Closed skippernl closed 3 years ago
dingmeng-xue
commented
3 years ago @skippernl , thanks for reporting. How did you trigger Connect-AzAccount? What parameter is used?
skippernl
commented
3 years ago No parameter used. Just connect-azaccount.
Using it with a global admin account on a Tennant goes well.
Using my msp account gives this error. Looking at the log I think logging in to the msp Tennant is fine but an additional domain is not. I do not recognize that domain.
Op ma 11 jan. 2021 12:10 schreef Dingmeng Xue notifications@github.com:
@skippernl https://github.com/skippernl , thanks for reporting. How did you trigger Connect-AzAccount? What parameter is used?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Azure/azure-powershell/issues/13893#issuecomment-757881197, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABIWZN5URJMZFYRUS4WDHLDSZLMCVANCNFSM4VY2GXLA .
erich-wang
commented
3 years ago @skippernl , based on the debug trace, it returns two tenants "cf2a0551-4e21-41aa-84b4-2003d1e444f6" and "92255eb7-c12b-47c0-9229-18b8ded02378" for your account. Could you please check if your account is in "92255eb7-c12b-47c0-9229-18b8ded02378" and has desired permission to subscription?
DEBUG: ============================ HTTP REQUEST ============================
https://management.azure.com/tenants?api-version=2019-06-01
Headers:
x-ms-client-request-id : 960f0233-d45b-47ea-b59a-a71350324606
Accept-Language : en-US
Body:
DEBUG: ============================ HTTP RESPONSE ============================
Status Code:
OK
Headers:
Cache-Control : no-cache
Pragma : no-cache
x-ms-ratelimit-remaining-tenant-reads: 11999
x-ms-request-id : cc91bc73-4b35-41b7-b237-cdbe79de0027
x-ms-correlation-request-id : cc91bc73-4b35-41b7-b237-cdbe79de0027
x-ms-routing-request-id : WESTEUROPE:20210107T104729Z:cc91bc73-4b35-41b7-b237-cdbe79de0027
Strict-Transport-Security : max-age=31536000; includeSubDomains
X-Content-Type-Options : nosniff
Date : Thu, 07 Jan 2021 10:47:28 GMT
Body:
{
"value": [
{
"id": "/tenants/cf2a0551-4e21-41aa-84b4-2003d1e444f6",
"tenantId": "cf2a0551-4e21-41aa-84b4-2003d1e444f6",
"countryCode": "xx",
"displayName": "Name",
"domains": [
"constoso.com"
],
"tenantCategory": "Home"
},
{
"id": "/tenants/92255eb7-c12b-47c0-9229-18b8ded02378",
"tenantId": "92255eb7-c12b-47c0-9229-18b8ded02378",
"countryCode": "NL",
"displayName": "Secure Connection BV",
"domains": [
"secureconnnectionbv.onmicrosoft.com",
"seccon.nl"
],
"tenantCategory": "Home"
}
]
}
cf2a0551-4e21-41aa-84b4-2003d1e444f6 should be my company Tennant
Op vr 15 jan. 2021 10:04 schreef erich-wang notifications@github.com:
@skippernl https://github.com/skippernl , based on the debug trace, it returns two tenants "cf2a0551-4e21-41aa-84b4-2003d1e444f6" and "92255eb7-c12b-47c0-9229-18b8ded02378" for your account. Could you please check if your account is in "92255eb7-c12b-47c0-9229-18b8ded02378" and has desired permission to subscription?
DEBUG: ============================ HTTP REQUEST ============================https://management.azure.com/tenants?api-version=2019-06-01
Headers: x-ms-client-request-id : 960f0233-d45b-47ea-b59a-a71350324606 Accept-Language : en-US
Body:
DEBUG: ============================ HTTP RESPONSE ============================
Status Code: OK
Headers: Cache-Control : no-cache Pragma : no-cache x-ms-ratelimit-remaining-tenant-reads: 11999 x-ms-request-id : cc91bc73-4b35-41b7-b237-cdbe79de0027 x-ms-correlation-request-id : cc91bc73-4b35-41b7-b237-cdbe79de0027 x-ms-routing-request-id : WESTEUROPE:20210107T104729Z:cc91bc73-4b35-41b7-b237-cdbe79de0027 Strict-Transport-Security : max-age=31536000; includeSubDomains X-Content-Type-Options : nosniff Date : Thu, 07 Jan 2021 10:47:28 GMT
Body: { "value": [ { "id": "/tenants/cf2a0551-4e21-41aa-84b4-2003d1e444f6", "tenantId": "cf2a0551-4e21-41aa-84b4-2003d1e444f6", "countryCode": "xx", "displayName": "Name", "domains": [ "constoso.com" ], "tenantCategory": "Home" }, { "id": "/tenants/92255eb7-c12b-47c0-9229-18b8ded02378", "tenantId": "92255eb7-c12b-47c0-9229-18b8ded02378", "countryCode": "NL", "displayName": "Secure Connection BV", "domains": [ "secureconnnectionbv.onmicrosoft.com", "seccon.nl" ], "tenantCategory": "Home" } ] }
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Azure/azure-powershell/issues/13893#issuecomment-760766606, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABIWZN4EGTTPW6QRJX5KCNDS2AAJXANCNFSM4VY2GXLA .
erich-wang
commented
3 years ago There're two suggestions:
Connect-AzAccount -TenantId cf2a0551-4e21-41aa-84b4-2003d1e444f6skippernl
commented
3 years ago For now I am using option 2 (-tennant domain.name) and that is working. Currently looking how I can contact the other organization.
skippernl
commented
3 years ago I have not heard from the other company. will be using the second option for now,
Is there a possiblity for MS to remove the link? If needed I can create a support ticket on our CSP portal
dingmeng-xue
commented
3 years ago @skippernl , my team has no information or process about it. You can raise the ticket and share tenant id to support.
I am closing this ticket and please contact us if you have further question.
arendkolk
commented
3 years ago Can somebody from Microsoft still help us with this issue of not being able to login via Powershell in Docker container
arendkolk
commented
3 years ago I have just deleted the 2 extra Tenants i had created for training purposes.
The issue is now solved for me and i can login again via Powershell from within a Docker container
Updated to latest Az modules removed AzureRmContext.json removed AzureRmContextSettings.json
Steps to reproduce
Connect-Azaccount Authenticate with the browser WARNING: Unable to acquire token for tenant '92255eb7-c12b-47c0-9229-18b8ded02378' This is with a MSP account Running with a Global Admin account is running fine
Debug output
Error output