Danny
My feedback
-
581 votes65 comments · Azure Active Directory » Groups/Dynamic groups · Flag idea as inappropriate… · Admin →
Our feature team is looking into options for addressing this scenario, but we do not yet have any timelines to share. For now as a workaround, you can manually trigger the reprocessing by updating the membership rule to add a whitespace at the end. We’ve also added the ability to check the membership processing status, to keep track of the status and know if processing is complete.
Danny supported this idea ·
-
312 votes23 comments · Azure Active Directory » Multi-factor Authentication · Flag idea as inappropriate… · Admin →
We are currently considering updating the Remember MFA settings. You can use Conditional Access Sign-in frequency policy to extend the session lifetime up 365 days.
Danny supported this idea ·
-
549 votes
-
1,180 votes101 comments · Azure Active Directory » Multi-factor Authentication · Flag idea as inappropriate… · Admin →
For requiring additional factors with Windows Hello for Business, please see – https://docs.microsoft.com/en-us/windows/security/identity-protection/hello-for-business/feature-multifactor-unlock
For why PIN is better than a password, please see https://docs.microsoft.com/en-us/windows/security/identity-protection/hello-for-business/hello-why-pin-is-better-than-password
For Authenticator app sign in to Azure AD, please see https://docs.microsoft.com/en-us/azure/active-directory/authentication/howto-authentication-phone-sign-in
As always, other feedback is welcome
/Ravi
Danny supported this idea ·
-
903 votes129 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.
Danny supported this idea ·
-
268 votes
This is in progress, you can see a preview when creating policy thought the Conditional Access API. Coming soon to polices created in the Conditional Access UX.
Danny supported this idea ·
An error occurred while saving the comment -
11 votes
Danny shared this idea ·
-
85 votes11 comments · Azure Active Directory » Multi-factor Authentication · Flag idea as inappropriate… · Admin →
Danny supported this idea ·
-
1 vote
Danny shared this idea ·
-
4 votes
Danny shared this idea ·
-
13 votes
Danny shared this idea ·
-
1 vote
Danny shared this idea ·
-
7 votes
Danny supported this idea ·
-
13 votes2 comments · Azure Monitor-Log Analytics » Agent Management, Data Metering and Usage (Portal) · Flag idea as inappropriate… · Admin →
Our Marketing team is working on updating the pricing models. We will share the details once it will be finalized. Thanks again,
Danny supported this idea ·
An error occurred while saving the comment Danny commented
If the pricing tiers are broken down by solution and are consistent across all solutions this would help to also make the solutions required more cost effective.
E.g. If we are looking at providing a security offering using the Security and Audit solution, I think that the Change Tracking solution fits in with this. However, when I enable Change Tracking I need to add an automation account which adds the automation and control category and I need to change pricing to per node. This makes the cost of adding a single solution very expensive and detracts from our ability to justify/implement Log Analytics. -
37 votes3 comments · Azure Monitor-Log Analytics » Agent Management, Data Metering and Usage (Portal) · Flag idea as inappropriate… · Admin →
We have a public preview of solution targeting available:
Try it out and let us know what you think.
— Richard
Danny supported this idea ·
-
33 votes
An error occurred while saving the comment Danny commented
Either through the Azure Portal or via powershell if the VM running the Configuration Server was deleted before removal through the Azure portal, we should have the capability to clean up the orphaned record of the ASR CS resource without having to delete the entire resource group
Danny supported this idea ·
-
3 votes
Danny shared this idea ·
-
7 votes
Danny shared this idea ·
-
73 votes7 comments · Azure Active Directory » Multi-factor Authentication · Flag idea as inappropriate… · Admin →
We’ll take this in consideration as we plan new features. In the short term, we are working on Graph API‘s that will allow you to change phone numbers in the StrongAuthentication fields.
Richard
Danny supported this idea ·
-
30 votesunder review · 1 comment · System Center Data Protection Manager · Flag idea as inappropriate… · Admin →
Danny supported this idea ·
I can see the status is now planned! As soon as you can please :)