Azure AD should provide more parameters to configure as per the users need.
For example as per my organisation's Security policy, the minimum password length required is 12. But there is no way to configure this parameter from 8.
The Azure AD platform should provide the ability for users to configure the below password policy at least.
1. Password history
2. Password complexity of temporary password generated by Azure
3. Password length

I'm blown away by the lack of options once your account gets locked out by the Azure AD Smart Lockout feature. Not having the ability to monitor the account lockout duration or have the option to unlock an account using this feature is insane.

Add customized filtering in the AzureAD user overview like on the new Office365 user overview. Filtering should include AD attributes like department, position, usage location etc.

When adding guest users via Bulk Invite in Azure AD, the name field is populated with the prefix of the email address. Frequently it's not the person's real name. I'll have to go back and modify them all. Please advise when this functionality will be added to Azure AD.

The taskbar settings work with Enterprise State Roaming, they roam between different computers, but not the pinned apps. When users work at different computers, the roaming of pinned apps would be the most valuable part of a roaming taskbar.

It would be great if the connected network printers would also roam between different computers with Enterprise State Roaming.
They roam with UE-V. But if you combine UE-V with Enterprise State Roaming (what is the recommended solution of Microsoft) you loose the possibility of roaming network printers.

We're very happy that with Enterprise State Roaming we've got a solution to roam different settings from Edge browser, specially the favorites. But for a good end user experience it would be necessary that also the possibility to set a specific page as the homepage and other settings like the preferred search engine in the address bar would roam between different computers.

If a users gets locked out of their account in Azure AD Domain services there is no way to unlock it. The user has to wait for 30 minutes.
Try telling the CEO you can't unlock her account?

when we create a group on azure active directory we add members in it but when the number increases and we need to track a user . it becomes a very tedious task as we dont have the option to search the user or sort them .

Putting all Users/Serviceaccounts synched from On-Prem AD in one OU is a little bit confusing...

Allow me to customize the Forgot my password link on the Azure AD sign in page so I can send users to our existing SSPR solution.

It would great to have the ability to allow Mac OS X users with the ability to join Azure AD.

The success registration page should be displayed only once for converge registration . Ideally this should be displayed only once . As per design this page is displayed no of times based on products used by converge registration . IF user is using 100 products for converge registration then as per existing design the page will be displayed each time for each product

Is there a way to organize the members within a hybrid or cloud only group? I have a few groups who have more than one page of users who I would like to view in a chronological order similar to how users populate in Azure Active Directory.

Enable sorting on columns. This is something you have neglected to do in all your web applications for Azure administration.
Some of the results are completely unusable to us unless it is sorted by date, or any other column.
By now, you should have developers that actually know how to program sorting by clicking on column headers.
If not, I can recommend some.

Current UX requires user to scramble find another internet access to find the recovery key(if they know what this is), then you need to enter the device keys and enter the long recovery keys. This UX is extremely painful and aggravating especially you are rushing. Please improve the user experience design by either adding this to Microsoft Authenticator, or some other solutions(QR code?) or eliminate this bitlocker nightmare completely from end user.