WaitingForGuacamole

That workaround didn't work for me. I had to use a PAT and `az devops login`.

I'm having a difficult time believing this is still an issue, but it is. If there were a way to force a scale set to always generate unique (always increasing)...

So, I've been having similar problems in an SPA, and decided to try to single-step the code that's built in version 2.2.2, and hosted in https://az416426.vo.msecnd.net/scripts/b/ai.2.js, I think I see...

OK. So, I "solved" the problem in reverse in my previous post. I have to play fewer games with squirreling values away, and get better metrics, if I do this:...

And, I'm back. I think this solves the problem "correctly" for my use case. No wall of text. Just the changes. I am hijacking appInsights.properties to track my own "previous...

Just a thought here - deprecation warnings to an end user should primarily target usage _by an end user_. If I don't use that property anywhere in my Terraform code,...

Agreed - I can create the automation account, create the runbook, create the schedule, and even create a job schedule pointing at an existing hybrid worker group, but without this...

Terraform 1.2.5 and AzureRM v3.15.0, still happening. Re-running `plan` and `apply` works for me, but now my workflow has to be run twice. Not ideal if I want to put...

@wuxu92 I'm on PTO this week, but this workaround looks extremely promising - I'll give it a try and get back to you roughly a week from now. Thanks very...

That workflow alone is worth a comment and an upvote.