Derek Schauland
My feedback
-
2,011 votes
We’re currently evaluating an option that will provide the functionality offered by nested groups, but removes the complexity nested groups adds. We appreciate your patience on this ask and want to ensure we deliver a solution that benefits all of our customers. Below are use cases that we’d like for you to stack rank, with #1 being priority for you. We thank you for the continued comments and feedback.
Use case A: nested group in a cloud security group inherits apps assignment
Use case B: nested group in a cloud security group inherits license assignment
Use case C: nesting groups under Office 365 groupsDerek Schauland
supported this idea
·
-
21 votes
An error occurred while saving the comment Derek Schauland
supported this idea
·
-
12 votesDerek Schauland
supported this idea
·
An error occurred while saving the comment Derek Schauland
commented
This would be a great add
-
82 votes
There is a current configuration to allow users to choose to remember a device for MFA: https://docs.microsoft.com/en-us/azure/multi-factor-authentication/multi-factor-authentication-whats-next#remember-multi-factor-authentication-for-trusted-devices
Additionally, we’re looking at providing more controls for this through conditional access.An error occurred while saving the comment Derek Schauland
commented
Would love to get updates on the status of this feature and when it might land. Planned is great but Ive got projects that could use this immediately
Derek Schauland
supported this idea
·
-
1 voteDerek Schauland
shared this idea
·
-
22 votes0 comments · Azure Monitor-Log Analytics » Extensibility / Partner scenarios · Flag idea as inappropriate… · Admin →Derek Schauland
supported this idea
·
-
6 votesDerek Schauland
supported this idea
·
-
12 votes
Thanks for submitting this request. We are currently investigating how to make this possible. We will update you once it has made to our backlog.
Derek Schauland
supported this idea
·
-
167 votesDerek Schauland
supported this idea
·
-
153 votes
Currently, you can configure all lab VMs to be created in an existing resource group instead of the lab creating a new RG per VM.
For ARM environments, every environment is spun up in its own RG to allow for better cost tracking user and policy management for resources created for that specific environment.Derek Schauland
supported this idea
·
This would be extremely helpful to ensure easily identifiable subnets while allowing the name of the subnet(s) to be uniform