How can we improve Azure Networking?

STOP creating random Resource Groups!

Honestly, what are we going to do with you MSFT when it comes to RBAC?

When MSFT puts services into Preview and often months or years after they are so-called GA they still fail to recognize that they are violating Governance, RBAC, rules allowing Azure Services to randomly create Resource Groups in any given Azure Subscription.

The two biggest violators of this right now are Databricks and Network Watcher.

In most cases our clients should be refusing to use these services until they are capable of adhering to Governance and Security rules being enforce by InfoSec and others.

Resource Groups are sacred beasts and must be named and tagged accordingly.

8 votes
Vote
Sign in
(thinking…)
Sign in with: Microsoft
Signed in as (Sign out)
You have left! (?) (thinking…)
Ron Bokleman shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

Thanks for the valid suggestion. Your feedback is now open for the user community to upvote & comment on. This allows us to effectively prioritize your request against our existing feature backlog and also gives us insight into the potential impact of implementing the suggested feature.

0 comments

Sign in
(thinking…)
Sign in with: Microsoft
Signed in as (Sign out)
Submitting...

Feedback and Knowledge Base