Please add location information to sign-ins from IPv6 addresses. Currently there is no location information associated with IPv6 so it is circumventing all the Azure AD Identity Protections you have in place.84 votes
Thanks for your feedback, folks. We have been working towards resolving the locations for IPv6 logins. Currently, a subset of such logins are getting resolved for location and the % will gradually go up. Are you seeing some of your IPv6 logins with resolved location?
Please extend Azure AD Identity Protection to the B2C tenant8 votes
Hi all: Just a heads-up that we have announced public preview availability of this capability. Please read more on the blog post here, try it out yourselves, and let us know what you think on this feedback page!
Would like to be able to create a seperate sign-in risk policy for medium and high risk events, medium policy would enforce MFA but let user continue working, high risk policy would block user access and preferably intiate sign out of all existing logins/tokens as this is a confirmed breech/exposure of credentials.5 votes
We’ve started the work on this.
We need a way to export/consult Risky sign in policies.
In general, a feature should be released with its associated API to allow Microsoft customers to perform automation.
Support case 119070422001895 confirmed this was not possible.2 votes
The work to do this has started.
- Don't see your idea?