mundayn

I agree this should be on Platform. I have had clients bypass restrictions in Platform due to this gap.

Same issue here with VSCode and Automation Account. Fix is to: Uninstall-Module Az.Accounts -RequiredVersion 2.13.1 Install-Module Az.Accounts -RequiredVersion 2.12.1 -Force and Az.Resources to 6.6.0 EDIT! does not fix it, now...

> @mundayn I'd recommend working closer with our support team via an [Azure support request](https://docs.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request). Or you can leverage our Q&A forum by posting your issue there so our community,...

Hi @jtracey93 Is there any conclusion / update on the naming convention for the "Azure landing zone accelerator". I know the naming convention is really a client by client decision,...

Hey @jtracey93 Following up on this if there is any comment? Thanks!

> @YY-VV, what news would you be looking for? Are you currently blocked by this? > > Any info, helps us prioritise and triage further, currently this is on our...

Chiming in as I subscribe to the notifications, I would want this to cover all scopes. You don't want users sandboxing insecure designs. But as long as Platform is covered,...

Surprised this has not bit more people. I came across this issue for a rather large company last year, we broke Power BI for everyone for over 24 hours until...

> which are in different regions. As far as I am aware, it is not possible to create the vWAN in one subscription, but the Hubs in other subscriptions and...

Hey @Springstone There is already a long running issue here for naming also fyi - Jack advised it was on the backlog a while back: https://github.com/Azure/Enterprise-Scale/issues/674 But as per this...