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

Unable to login with my personal account. #2344

Closed
rawwar opened this issue Jun 28, 2021 · 8 comments · Fixed by #2354
Closed

Unable to login with my personal account. #2344

rawwar opened this issue Jun 28, 2021 · 8 comments · Fixed by #2354
Assignees
Labels
Milestone

Comments

@rawwar
Copy link

rawwar commented Jun 28, 2021

I am trying to log in with my personal account. Which is a @live.com email. But, i keep getting the following error -
"You can't sign in here with a personal account. Use your work or school account instead." How do i log in with my personal account?

@dpwatrous
Copy link
Member

Thanks for the report - this looks like a regression when we switched the authentication library to MSAL. We'll look into it!

@zerweck
Copy link

zerweck commented Jul 28, 2021

Any Update? We have the same problem and can't use Batch Explorer for a while now.

@rawwar
Copy link
Author

rawwar commented Jul 29, 2021

I created a temporary user using AAD. That also creates an email that ends with onmicrosoft.com. You can log in using this email id. But, even I am waiting for a fix.

@dpwatrous
Copy link
Member

Not much of an update, but I believe this has to do with the initial scope of management.azure.com that we're using to query tenants, which only supports AAD accounts. Still trying to figure out the right fix, however.

@dpwatrous
Copy link
Member

After a lot of reading, it looks like it's a behavior change with the v2 auth endpoints we're using. Switching to using the /organizations tenant instead of /common seems to have done the trick.

I'll put a PR up and we'll get this into the insiders build right away. Let us know if that solves the issue for you!

@dpwatrous
Copy link
Member

dpwatrous commented Jul 29, 2021

The fix should be live in the latest insiders build now. We'll try to get this released to stable next week.

@zerweck
Copy link

zerweck commented Aug 3, 2021

After a lot of reading, it looks like it's a behavior change with the v2 auth endpoints we're using. Switching to using the /organizations tenant instead of /common seems to have done the trick.

I'll put a PR up and we'll get this into the insiders build right away. Let us know if that solves the issue for you!

Since you asked to let you know: Yes, this solved it for us. Thank you!

@dpwatrous
Copy link
Member

Glad to hear it!

@cRui861 cRui861 added this to the 2.11.0 milestone Aug 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants