Azure Active Directory
Welcome to the Azure Active Directory suggestions and feedback site! We love hearing from you. If you have suggestions, please submit an idea or vote up an idea. We are monitoring the site actively.
Thank you for joining our community and helping improve Azure AD!
We
have a new log in experience integrated with Azure AD, and we strongly
recommend you log in with your Azure AD (Office 365) account. If your
UserVoice account is the same email address as your Azure AD account, your
previous activities will be automatically mapped to your Azure AD account. You can read more here for details: https://techcommunity.microsoft.com/t5/Azure-Active-Directory-Identity/Putting-customers-first-for-f...
-
Add Japan region to data residency location of Azure AD B2C
Lots of Japanese customers would like to use Azure AD B2C. But they can not decide to adopt B2C because we do not have Japan region as data residency location.
214 votesWe are hoping to support more datacenters in the future, especially in the Asia/Pacific region, but it is not currently planned for the short term.
/Parakh
-
Azure AD B2C Data Residency in Australia
Although Azure AD B2C is available for use in Australia, there is not option to create a directiry for which the user data resides in Australia. We would like to be able to ensure that our Azure AD B2C user data remains in Australia.
162 votesUnfortunately, we have no plans for data residency in Australia. If this is key to your needs please continue voting and we will use this to help us prioritize this in the future.
-
B2C Support for client credential flow.
To enable APIs to use authentication from another application with separate security credentials (clientId+secret). Needed for APIs to make graph calls.
(This is not the same as on-behalf-of flow, which represents the ability to exchange an access token intended for one audience for an access token intended for a different audience)
147 votesThis is not planned for the next 6 months, but is on the roadmap.
/Parakh
-
B2C Roadmap
Deliver a roadmap which shows what functionality is planned and under review.
99 votesHi all, unfortunately we don’t have plans to share out a public roadmap. This is constantly changing as we’re listening to customer requests. We will continue to update feedback.azure items as they come up so feel free to suggest anything you are curious about.
-
group naming policy using extension attributes
Please implement additional functionality to allow the use of Extension Attributes as part of a Group Naming Policy. This is required as the Department name is too large and many organisations have a shortened department code which they apply via an Extension Attribute. Using a long department name in a Group Naming POlicy creates names that are too long to be useful, but using a shortened department code plus group name means that the group can be easily identified and attributed to a department without cluttering the name space.
e.g. Information and Communication Technology has a short code of ICT…
96 votesThank you for your feedback! We have heard you and are considering future implementation options. There is no timeline yet for implementation. If this feature matters to you, keep voting as it will help us prioritize.
-
Enable support for dynamic mail-enabled security groups
Dynamic security groups are great, mail-enabled groups are great too wouldn't it be great to have both. We have a requirement to create security groups (or distribution groups) based on employee attributes (i.e. Active Full-time, Active Parttime, etc...). These attributes live in Azure AD but aren't accessible in Exchange Online so I cannot create a dynamic distribution group. I am able to create a mail-enabled security group but the membership cannot be dynamic. And any dynamic group I create can't be mail-enabled unless it's a unified group but for the purposes we need the groups for Unified groups aren't appropriate.…
83 votesThank you for your feedback! We have heard you and are considering future implementation options. There is no timeline yet for implementation. If this feature matters to you, keep voting as it will help us prioritize.
-
AADB2C: include username in JWT claims
AADB2C supports either email addresses or usernames for accounts. If a directory uses usernames, you don't get that username as a claim in the JWT. This means an extra trip to Azure must be made to retrieve the username. Please consider including the username in the JWT.
81 votesThis is currently not on our roadmap. You can retrieve this value by making a call through the Graph API. If this is needed for your scenarios, please continue voting and we will review at a later date.
-
Add hashed password migration to Azure AD B2C
Currently, I can migrate user accounts from an existing database to Azure AD B2C. However, it only accepts unhashed passwords, which is completely useless for any modern system, which should ONLY be using hashed and salted passwords. What would actually make this feature useful is to include fields for hashed password, hash algorithm (any of several standard ones), salt and salt method (i.e., appended, prepended, etc).
74 votesThis is not planned for the next 6 months. If this is needed for your scenario, please continue voting and we will re-evaluate at a later.
-
Support logout and single logout with SAML 2.0 claims provider
Support for logout and single logout with SAML 2.0 IdP configured as claims provider on B2C.
The logout and single logout os both requested in some customer cases and in relation to the Danish governments IdP called "NemLog-in". In relation to the Danish governments IdP it is a requirement to support logout and single logout to connect to the central federation.
70 votesUnfortunately this is not planned within the next 12 months. If this is needed for your scenarios keep voting on this item and we will review at a later date.
-
Passwordless authentication
Add support for phone- and email-based passwordless authentication - using OTPs (one time passwords).
68 votesThis is a scenario we are looking to support in the future however, it is not on our immediate roadmap for the next 6 months. Please continue voting and we will evaluate at a later date.
-
Spring Security Support
Storm Path is an example of an API/Service that provides all the same functionality as Azure AD B2C, and actually integrates with Spring Security very easily.
https://stormpath.com/
They provide code samples too:
https://docs.stormpath.com/java/It would be fantastic, and ensure a much wider adoption market, if you were to create an open source project that provided the same easy integration and adoption.
52 votesThis not planned for the next 6 months, but it is on the roadmap.
/Parakh
-
All Powershell/BASH/script Azure AD join
For converting BOYD to Azure AD in the field w/o user intervention, we need a way for elevated accounts to be able to perform an Azure AD join of devices via script.... come on, this is the basics...
Think of it as MDM self-enrollment... if not that, then give us a one-click way for users to self-enroll the device.
51 votesThanks for the feedback on this. There are several ways to do Azure AD join (OOBE, bulk enrollment and Autopilot) which provide a richer experience to join devices to Azure AD. We’re continuously working to enhance those, so currently this is unplanned for the near future. Please continue to vote to help us prioritize
—
Ravi -
AADB2C: Password Expiration
Unlike Azure AD, B2C does not allow you to set a password expiration policy. Please allow similar capability in B2C to set both a password expiry as well as the length prior to a notice being sent to the user before their password expires.
42 votesThis is not planned for the next 6 months, however it is on the roadmap.
/Parakh
-
Avoid verification code emails when the user is not registered
Azure B2C is gives a false impression that the user is in the directory when they try to reset their password.
Following is steps in reset password:
1) User clicks the Reset Password link
2) B2C presents a page with “Email Address” field and says “Verification is necessary. Please click Send button.”
3) User enters his email address and clicks “Send Verification Code”
4) B2C sends the verification code this that email address (Even if no user is associated with that email address. This is where the user thinks he is registered with the system)
5) Now the user enters…31 votesNot currently planned for the next 6 months, but it is in our roadmap.
/Parakh
-
Allow Azure AD B2C users to access PowerBI dashboards
Add support for PowerBI Dashboards in Azure B2C
28 votesSorry for the previous confusing status. We are not planning to allow Azure AD B2C users to have access to powerBI. We are however starting work to enable audit data from Azure AD B2C to be surfaced through PowerBI.
-
Pre-populate username field with value from the query string like old Sign-In Policy
You provide policies for Sign-In, Sign-Up and Sign-In or Sign-Up. The "Sign-In" policies do not allow page customization because they are using an older (pre B2C) way of doing things. However, one advantage the Sign-In policy has is that I can add &username=myUsername and it pre-populates the Username field with this value.
In our system, we already know the username before we send them to the "sign-up or sign-in" Policy screen, and we'd like to add the username to the query string so the value is already populated.
28 votesYou can use the login_hint parameter for this.
e.g. https://login.microsoftonline.com/tenantName/...?login_hint=usernameValue
-
Enable Flash SMS for MFA/Multi Factor Authentication
I'd like the possibility to use Flash SMS (http://en.wikipedia.org/wiki/Short_Message_Service#Flash_SMS) when sending one-way OTPs using Azure MFA / Multi-Factor Authentication.
28 votesThis is not currently planned for development. Microsoft encourages the use of push notifications to the authenticator app, which have similar usability to Flash SMS.
-
Azure AD Applications - Needs
- Allow applications in Azure AD to be organised into folders so business units who work in this space can 'claim' applications.
- Provide the ability to rename applications or application instances once created.
- Provide visbility of what user created an application.
- Provide the ability to 'lock' applications from being accidently deleted.
- Deletion of applications requires X global admins to approve, at the moment a rogue admin could destroy an SSO setup for an entire company in minutes...17 votesThank you for your feedback, some of the suggestions are already available:
- Ability to rename applications
- Provide visibility of what users created an application: You can use audit activity reports: https://docs.microsoft.com/en-us/azure/active-directory/active-directory-reporting-activity-audit-logsRegarding the other suggestions, I’ll update this once it’s a planned feature. In the meantime, keep the voting coming so we can prioritize this higher.
/Luis
Program Manager -
Do you know if the connector can update an Employee's Username in Workday?
Our client is planning on using email address as the Username in Workday which also drives the SSO. The issue is - Let's say John Doe is hired in Workday and gets assigned John.doe@xyz.com. the new hire flows across to Active Directory and AD says that email is already in use and it needs to be updated to John.Doe1@xyz.com . We are using the Azure connector where the Azure app is able to update the worker's work contact information. Not sure if the Azure app has the ability to update the Username attribute in Workday account.
9 votesHello,
This scenarios is not currently possible with the Workday writeback connector. We’re evaluating solutions but it’s not planned yet.
Keep voting to help us prioritize.
Thanks,
Luis -
Custom error messages per SaaS App and tenant-wide also
It would be really awesome, if Microsoft would provide developers with an option to provide custom error messages per Azure AD SaaS Apps and Global Admin to define some tenant-wide custom error messages as well. The error messages provided from Microsoft is not especially user-friendly or customer specific yet. This creates some confusions among internal and B2B users.
I hope this would be taken into considerations like the Azure Conditional Access custom error messages.
/Peter Selch Dahl
Azure MVPAlso see these related request:
---------------------------------------------------------------------Fix Error AADSTS50020 when logged in user doesn't have permissions to selected Application:
https://feedback.azure.com/forums/169401-azure-active-directory/suggestions/6795635-fix-error-aadsts50020-when-logged-in-user-doesn-tCustomize…
5 votesWe don’t plan to provide the capability to customize the error message for now. But, we have been working on making the error messages more actionable.
If you have any suggestions for improving an specific error message. Please create another post and the team will improve it.
/Luis
Program Manager
- Don't see your idea?