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!
Wehave a new log in experience integrated with Azure AD, and we stronglyrecommend you log in with your Azure AD (Office 365) account. If yourUserVoice account is the same email address as your Azure AD account, yourprevious 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...
-
Update UserType from portal
Be able to see and change the userType from the portal.
(This is only available in Powershell : example: change from Guest -> member, in order to see the directory as an external user.)Set-MsolUser -UserPrincipalName xxxhotmail.com#EXT#@xxxhotmail.onmicrosoft.com -UserType Member
230 votesUpdating the status to indicate that this is a valid suggestion and in our backlog for the future. Please keep the comments/votes coming, knowing more about how you intend to use this helps us prioritize and design better features.
/Elisabeth
-
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.
217 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
-
Support Azure AD domain join for Windows Server 2016
Microsoft should strongly consider implementing support for Azure AD join in future builds of Windows Server 2016. I how a couple of customers that have nearly finished the transition to all cloud and is left with a couple of servers due to legacy software. They are currently left with the option to deploy Azure AD Domain Services for supporting a couple (2-5) servers.
184 votesCurrently, we are not aware of any plans from Windows Server for this capability. We’ll continue to work with Windows Server to revisit this in the near 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)
163 votesThis is not planned for the next 6 months, but is on the roadmap.
/Parakh
-
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…
140 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.…
128 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.
-
B2B Guest User Expiration
Looking for the functionality where you can schedule Azure B2B users to exist in your tenant for a predetermined period of time. This would operate similarly to the O365 Groups expiration functionality that exist today. Additionally, managers would be allowed to extend these periods of time and automated reminders would be sent to the manager of these users.
120 votesWe do have some capabilities in this space by using either Access Reviews (https://docs.microsoft.com/en-us/azure/active-directory/governance/manage-guest-access-with-access-reviews) or the newly-released-to-preview Entitlement Management feature (https://docs.microsoft.com/en-us/azure/active-directory/governance/entitlement-management-overview).
If neither of those fulfill your requirements, please add a comment with your scenario for the feature to help us prioritize and design it better.
/Elisabeth
-
Enable User Writeback to On Premise AD from Azure AD
We need to be able to sync down from Azure AD - specifically we have External Users that we need to have down on our on premise AD so that we can put them into Distribution Lists...
119 votesWe are aware of this requirement but have no timelines to share at this moment.
-
B2C Roadmap
Deliver a roadmap which shows what functionality is planned and under review.
102 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.
-
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.
90 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).
85 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.
79 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).
74 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.
-
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.
71 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 -
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.
54 votesThis not planned for the next 6 months, but it is on the roadmap.
/Parakh
-
remove b2b user when host account is removed
We use Azure B2B extensively. However where B2B users have been into our directory and the user has left the third party organisation and thus had their account removed does not clean up the guest account records in our directory.
Over time this leaves thousands of 'orphaned' guest accounts in our directory, with no ability for our administrators to identify which accounts are orphaned. and thus numbers of guest users in our our directory expands over time infinity
Azure AD should automatically in the in the event of a user object being removed from the third party directory remove the…
38 votesThis is in our backlog, but votes and comments about how you would expect this to work are very helpful to our planning/designing the feature so please keep them coming.
Also, for some scenarios in this space Access Reviews (https://docs.microsoft.com/en-us/azure/active-directory/governance/manage-guest-access-with-access-reviews) can be a good way of removing users who no longer need access, including those who don’t have accounts anymore. (Thanks Shawn for pointing that out for everyone!)
/Elisabeth
-
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…32 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
29 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.
-
Bring through external user profile fields when using B2B
Currently, when you invite someone from another AzureAD, using the B2B process, only their DisplayName and EmailAddress comes through (both of which are actually provided in the B2B CSV file).
It would be very useful if more profile information could be retrieved, possibly with the user's authorisation.
In particular, details like Firstname, Lastname and Country, would be a useful start, but potentially more profile fields (address, phone numbers, title, etc) would be ideal.
28 votesMarking this as part of our backlog. The votes and comments about how you would use this are really helpful, please keep voting/commenting if this is an interesting scenario for you.
/Elisabeth
-
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
- Don't see your idea?