Closed johanburati closed 4 years ago
Hey @johanburati - are you able to provide any more details on this? This isn't supposed to come up in normal operations but we can dig around our telemetry to see if there are any more details available. Your subscription id, resource group name, VM name and region would be helpful (or just the latter 3 if you don't want to share your subscription id)
Hi @asinn826 just sent you the details by email.
@johanburati based on the email details, looks like your issue is resolved now.
In case others come and read this in the future, the issue was a malformed boot diagnostics url (missing an 's' in "https://").
EDIT: running az vm boot-diagnostics enable
with relevant parameters fixes the problem for me
Hello, where do you configure boot diagnostics url? I am also getting 400 Bad Request
Do you know what could be causing the following error when trying to access the Serial Console ?