Thank you for your feedback. This feature request work is in progress.
Yes, Please use "Change_Work_Contact_Information" api call for changing the mail address. We also have a lot of validation errors, cause Maintain_Contact_Information is depending on BusinessProcess workflow to be closed. In that is not always realistic for NewHires.
233 votesunder review · 38 comments · Azure Active Directory » Domain Services · Flag idea as inappropriate… · Admin →
We’re looking at how best to implement this, given various service dependencies with the myapp portal. Thank you for the continued feedback.
Hey folks, thanks for the interest in this, and we have some good news to share. Configurable lockout is in development now (mostly done, actually) and we’re aiming for June or July public preview.
For configurable password complexity, length, etc, we hear you. Longer passwords are in planning now, and we’re thinking about our approach to how we want to enable the other configurability features. I don’t have any more details to share on this for now, but we do have interest in building features.
20 votes2 comments · Azure Active Directory » Multi-factor Authentication · Flag idea as inappropriate… · Admin →
3 votes0 comments · Azure Active Directory » Azure AD Connect Health · Flag idea as inappropriate… · Admin →
Thank you for the feedback! Connect Health is planning to provide the configuration fashion to show the notification settings in the top blade.
10 votes5 comments · Azure Active Directory » Azure AD Connect Health · Flag idea as inappropriate… · Admin →
Update the status
4 votes0 comments · Azure Active Directory » Azure AD Connect Health · Flag idea as inappropriate… · Admin →
Thank you for the feedback! We will review the experience and enhance the notification feature.
We’re well aware of the NIST 800-63B guidelines (and it’s my team that wrote that password whitepaper!). We’re currently making some foundational changes that should subsequently let us implement many or most of the password composition guidelines.
As for a password blacklist, today we have a banned password list in place that prevents users from using known-bad words, phrases, and passwords. We also have a custom list feature that lets you define your own words and patterns. That’s in private preview today and we’re working to get it to public preview over the next few months.
Thanks for the feedback, we will review this.
Keep voting to help us prioritize.
We are working to enable this feature. We should have another update by Dec 2018.
Thank 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-logs
Regarding 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.
I do like the idea of free form tagging as at that moment you can decide to either tag by Business or by Type (HR, IT, Finance, Sales).
Another idea, and this maybe a step too far for now, could also be to have an area for suggested apps. And these apps would then be populated by popularity of usage of apps by your peers. Of course all will be security trimmed and you will only see apps which you are allowed to see.
6 votesGhisaidoobe, Rochen shared this idea ·
13 votesstarted · 4 comments · Azure Active Directory » Azure AD Connect · Flag idea as inappropriate… · Admin →
Thanks for the feedback! We are in process of trying to align My Apps with the Office experience to help the experience be more fluid between users. Please share more feedback and ideas around this!
Thanks so much for the feedback! We know how important it is for users to have the ability to customize their app list and make it very easy to find their core applications.
Customizations of the My Apps portal for both end users and admins are top priority on our roadmap. This includes providing the ability to re-arrange and group apps and provide users sets of categorized apps.
Please keep sharing your feedback and ideas around this!
A scenario: a hard requirement for for us is to use Azure MFA with AWS Workspaces. AWS Workspaces only supports Radius Auth as 2FA, not modern authentication (oAuth).
In the existing infrastructure is available: ADFS, AAD Connect, Azure AD Premium. Reading what Antonio has described, theoretically we can utilize Radius (MSCHAPv2) in Azure AD Domain Services if we also start synching the Kerberos hashes to the cloud.
I would love to see this confirmed by Microsoft. I will be a huge benefit for MS also to mention that not only the legacy protocols like NTLM/Kerberos are supported, but also Radius authentication. At that moment there are very less boundaries left with a journey to the cloud...