Unable to register users to Azure Labs VMs

Dan Alexander 0 Reputation points
2024-07-08T17:07:54.9+00:00

We've been using Azure Labs Services to run trainings for over a year now, and this issue is new. The registration link, which I have confirmed is the correct one, spins for several minutes, and returns a generic "Oops, something went wrong" error. The browser console indicates a 500 error on a PUT request in register.js

e {message: 'An internal server error occurred. Please try again later.', id: '<LAB ID REDACTED>', failureOperation: 'RegisterUser', code: 'InternalServerError', policyViolationDefinitionIds: undefined}

Azure Lab Services
Azure Lab Services
An Azure service that is used to set up labs for classrooms, trials, development and testing, and other scenarios.
289 questions
{count} votes

2 answers

Sort by: Most helpful
  1. hossein jalilian 5,095 Reputation points
    2024-07-08T19:40:33.7733333+00:00

    Thanks for posting your question in the Microsoft Q&A forum.

    Here are steps you can follow to troubleshoot and possibly resolve the issue:

    • Verify if there are any ongoing service issues or outages reported by Microsoft for Azure Lab Services. You can check the Azure status page for this information.
    • Check the address range settings in your lab account. As mentioned in the search results, insufficient address range can cause issues with lab creation and potentially with registration.
    • If you're using a direct registration link, try adding users through the Azure portal instead.
    • Ensure that there are no network issues or firewalls blocking access to Azure Lab Services endpoints.

    Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful

    0 comments No comments

  2. Prrudram-MSFT 22,976 Reputation points
    2024-07-16T16:49:24.9933333+00:00

    Hi @Dan Alexander

    Do you still have this issue? I have discussed this issue with the azure dev test labs team, there was an issue reported a week ago in some of the regions and our team has rolled out a fix. If you still have this issue, I would recommend you open an azure support case. If you don't have the ability to open a technical support ticket, please let me know and I can help you further with this.

    Please Accept Answer and hit Yes for "was this answer helpful" if this helps

    0 comments No comments