Guys, I followed the steps but I'm finding an error. It tries to log all virtual machines I have created and I'm not able to set a lab.
⚠Não edite esta seção. É necessário para a vinculação do problema do docs.microsoft.com ➟ GitHub.
@cdaniel96 Thanks for the feedback. Would it be possible to provide an error message or some additional detail as to what you are experiencing? In the mean time, we are actively investigating and will get back to you soon.
Hey Mike, how are you doing? Thanks for the answer. That's what i'm finding after going to Https://labs.azure.com/:
As you can see it only shows that no VM is created but also I'm not able to create anything.
The big problem is that my user account already has the appropriate right to create labs as you can see below:
Please, reach me if you need any further information.
@cdaniel96 Perfect, thank you. I do not have sufficient permissions to create lab environments. I am going to assign to the content owner for assistance.
@cdaniel96 - The screen you are seeing is what someone accessing the classroom lab should see: https://docs.microsoft.com/pt-br/azure/lab-services/tutorial-connect-virtual-machine-classroom-lab (You see "My virtual machines" instead of "My labs").
In this case, you are actually trying to create a lab (not access a lab). As per the above image you shared, the user (azdeploy) is a member of the Lab Creator role. Therefore, when you navigate to labs.azure.com and log in to using this account, you see the screen that was in the article with "My labs" and a pop up window to create a new lab.
I will try to get a PM or dev have a look at the issue soon. Thanks.
@jkwon2013
Great! Please, feel free to reach me have you any question :)
I've been trying to access the labs.azure.com site for about a day and it will not connect. It constantly throws a login loop (using Windows 10 and Edge it allows me to select my user name but it will loop me right back to the user screen, while any other browser/OS will just continue to refresh the page until it times out).
@jkwon2013 - could you please look into the issue? Thanks.
@spelluru this happens with me when I try to access using a Microsoft Account. Using a work account I see what you had described, a week ago.
@cdaniel96 and @mjphotopro This is a known issue on our side that happens if you try to sign in with a Microsoft account. If you use a work or school account (AAD account), things should work normally. We're hoping to get this fixed in the next week or so, so I'll update this thread once we fix the MSA issue.
Please let us know if you see another issue when you're not using a MSA.
@jkwon2013, thank you for your answer. My case is something like this. I'm assigned as _subscription owner_ in a partner Directory and I have the "Lab Creator" Role in Azure Lab Services. I'm using a company account and what I see is "My Virtual machines" page, instead of "My Labs" page. Please, reach me if you get any question :)
@jkwon2013 any news about this?
@cdaniel96 sorry for the late response! I've asked someone to look into this issue. we may reach out with more questions soon
@jkwon2013 anything new until now? Thanks!
Guys, only to update you about this issue. What really happens is this:
Let's say you have a tenant contoso.onmicrosoft.com and you grant the Lab Creator Role to mark@contoso.onmicrosoft.com.
If this user signs in at https://labs.azure.com, he will be able to create new labs.
This is the happy path.
The problem starts when you get access to an Azure Subscription by RBAC. As I could understand, Azure Lab Services Page is stuck with the directory associated with the user.
E.g.:
[email protected] receives access to Fabrikam Directory (fabrikam.onmicrosoft.com) and creates an Azure Lab Services resource in that directory. When Mark access https://labs.azure.com and signs in, he is not signed in Fabrikam Directory. Instead, he is redirected back to Contoso Directory (contoso.onmicrosoft.com). Therefore, if there's no Azure Lab Services at Contoso, Mark only sees My Virtual Machines page, instead of My Labs page.
This kind of behavior affects negatively because in some cases as a service provider/partner must manage these labs from different environments, it needs to create more users, each in a different tenant. Then, I would suggest to provide the ability to change directories inside https://labs.azure.com.
I guess that the case is solved, but I would strongly recommend to share with other people this as a known issue.
@cdaniel96 thanks so much for the details! We are currently working on a bug fix that will basically know that you're part of that tenant and take you to the proper lab-creation page. This will be fixed soon.
Product team is tracking this issue in VSTS.
@jkwon2013
This appears to be fixed. I tried logging in a few days ago and was able successfully log in with my other Microsoft accounts and create and access labs. Thanks everyone for getting this fixed. I look forward to trying this out for training lab sessions.
@cdaniel96 We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.
Most helpful comment
This appears to be fixed. I tried logging in a few days ago and was able successfully log in with my other Microsoft accounts and create and access labs. Thanks everyone for getting this fixed. I look forward to trying this out for training lab sessions.