4 votes1 comment · Azure Active Directory » Provisioning to Applications · Flag idea as inappropriate… · Admin →
This is a bug on our side and we will fix it. As a workaround you can use the Microsoft graph to enable the object again. You will need to update schema and set enabled = true and sourceName = “user” or “Group” based on which option you’re trying to bring back. Apologies for having to use the workaround. https://docs.microsoft.com/en-us/graph/api/synchronization-synchronizationschema-update?view=graph-rest-beta&tabs=http
2 votes0 comments · Azure Active Directory » Provisioning to Applications · Flag idea as inappropriate… · Admin →
Thanks for the feedback. We are looking to add more detail to our audit logs. This is good feedback.
3 votesunder review · 1 comment · Azure Active Directory » Azure AD Connect · Flag idea as inappropriate… · Admin →
Thank you for your feedback. This feature request work is in progress.Ghisaidoobe, Rochen commented
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.
Multiple scenarios are still being investigated.
CONFIRMED that NPS and Azure AD Domain Service can work with the Azure MFA NPS extension to enable MFA for RDP to virtual machines. That said, Azure Bastion Host (https://docs.microsoft.com/en-us/azure/bastion/bastion-overview) provides the same value without the additional infrastructure of NPS. We have a doc bug created to add the nuance to our documentation, which is to 1) Skip registering the NPS server and 2) ensure your network policy has “Ignore user account dial-in properties” selected.
Leaving the topic open as we continue to investigate/validate other NPS use cases (e.g. VPN and 802.x scenarios)
Senior Program Manager
IAM Core | Domain Services
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.
41 votes3 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.
11 votes5 comments · Azure Active Directory » Azure AD Connect Health · Flag idea as inappropriate… · Admin →
Update the status
5 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.
Program ManagerGhisaidoobe, Rochen commented
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 ·
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!