I have the same problem, created similar question here. As a workaround until they fix this problem (or not), you can just ignore this Learn Sandbox and once it shows you the message: "Sandbox activated! Time remaining: 59 min", you can simply go to portal.azure.com and open the Cloud shell there. I have verified that it works, and all required resources are being created. This is how I've finished a couple of exercises already. Also once Learn created a new subscription for you, you can use UI to create resources, not only the Cloud shell. Hope that helps someone.
Unable to activate the Azure Learn Sandbox
Hello,
I am unable to activate the Azure Learn Sandbox for the module: "Exercise - Explore the Learn sandbox".
When attempting to activate the sandbox I receive the following error:
AADSTS500200: User account '******@pm.me' is a personal Microsoft account. Personal Microsoft accounts are not supported for this application unless explicitly invited to an organization. Try signing out and signing back in with an organizational account.
Request Id: 693386b2-d208-4de4-871d-7dfa55532800
Correlation Id: 185d640a-4938-458e-b50b-29b6fd217d37
Timestamp: 2025-01-27T09:37:09Z
Message: AADSTS500200: User account '******@pm.me' is a personal Microsoft account. Personal Microsoft accounts are not supported for this application unless explicitly invited to an organization. Try signing out and signing back in with an organizational account.
Please advise.
Thanks,
Dave Ziegler
This question is related to the following Learning Module
4 answers
Sort by: Most helpful
-
-
Manu Philip 19,271 Reputation points MVP
2025-01-27T10:47:17.6066667+00:00 Hi Dave Ziegler
Your organization's Azure administrator can invite the email address '******@pm.me' as a Guest user. Once you accept the invite, you should be able to able to access the resources
Hope this helps.
--please don't forget to
upvote
andAccept as answer
if the reply is helpful-- -
Jendy Jasper 0 Reputation points
2025-01-31T10:20:41.3366667+00:00 I also faced this challenge. I think the problem is when you use your Microsoft account created from outlook or office 365 - it makes it to belong to a different directory. I resolved the issue by creating an account directly on azure portal, and it works fine now
-
Krum Bagashev 0 Reputation points
2025-02-07T15:53:50.2166667+00:00 To add more detail to the issue is that it worked previously with your personal account. Of course, the best option is to continue to use your personal account for sandbox environments. And that is the idea of the sandbox, to create temporarily access to the resource in an isolated(sandbox) environment. It's either a bug in Azure, or if it's a policy change, it has not been publicly announced. @RNareddy is there any progress on the internal investigation?