Pirmin Felber
My feedback
-
67 votesunder review · 4 comments · Azure Active Directory » Privileged Identity Management · Flag idea as inappropriate… · Admin →Pirmin Felber
supported this idea
·
-
110 votes18 comments · Azure Active Directory » Multi-factor Authentication · Flag idea as inappropriate… · Admin →Pirmin Felber
supported this idea
·
-
7 votes
An error occurred while saving the comment Pirmin Felber
supported this idea
·
-
3 votesPirmin Felber
shared this idea
·
-
84 votesPirmin Felber
supported this idea
·
-
1 votePirmin Felber
shared this idea
·
-
921 votes130 comments · Azure Active Directory » Multi-factor Authentication · Flag idea as inappropriate… · Admin →
We’re really pleased to let you know that we’ve released the first authentication method APIs to public preview:
https://docs.microsoft.com/graph/api/resources/authenticationmethods-overview
So far there are APIs for managing phone numbers and password resets. When phone numbers are set with the API, the user can use that number for MFA and SSPR (as allowed by your tenant’s policy).
The team is hard at work at building out APIs for all of the other authentication methods, and we’ll update the response here as they’re released.
Pirmin Felber
supported this idea
·
-
35 votes
We have created a backlog item to track this request.
Pirmin Felber
supported this idea
·
-
29 votes
This is similar to cluster-aware updates but slightly different. We will keep an eye on this to gauge interest and prioritize accordingly.
An error occurred while saving the comment Pirmin Felber
commented
An ability to model update sequences would help us a lot. Currently we're considering to build this ourselves by either
- Have a dedicated runbook that automatically schedule deployments (schedule update wave 2 after update wave 1 has been completed).
- Or use a Pre-Script that pauses update of wave 2 as long as wave 2 has not been completed.However both implementations makes it hard to narrow down update windows (espcially if there are three or groups in update sequence).
Pirmin Felber
supported this idea
·
-
20 votesPirmin Felber
shared this idea
·
-
1 votePirmin Felber
shared this idea
·
-
1 votePirmin Felber
shared this idea
·
-
12 votes
An error occurred while saving the comment Pirmin Felber
commented
Totally agree. A Log Analytics Integration would give us the flexibility we need. Technically we *could* do this by using export and upload exports using Log Analytics Data Collector API. However, a direct Log Stream of costs will be much more efficient.
Pirmin Felber
supported this idea
·
-
11 votes0 comments · Azure Monitor-Log Analytics » Search UI and Language · 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.
Pirmin Felber
shared this idea
·
-
2 votesPirmin Felber
shared this idea
·
-
116 votesPirmin Felber
supported this idea
·
-
76 votesPirmin Felber
shared this idea
·
-
11 votesPirmin Felber
shared this idea
·
-
123 votesPirmin Felber
shared this idea
·
-
2,650 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 groupsPirmin Felber
supported this idea
·
Applying some blocking policies (especially regarding Client Apps / Locations) would be useful for us as well.