Many of you are using the new experience regularly – in fact, over half a million of you are using it, from almost every country in the world, with usage increasing by about 25% each month. We appreciate all your positive feedback, and love the constructive feedback that’s helped us make an even stronger product. But there are still a LOT of you using the old portal.

Late last week we turned on the another set of feature updates, and the new experience now has all of the features identity admins frequently use. With that update, we’ve entered our final push to GA the UX in the next ~60 days.

And that’s where we need your help: We need everyone to move over to using the new portal for production tasks so we can uncover any last minute lingering issues."

Please, do read Alex` blog post for more details and send us your feedback in the ‘Admin Portal’ section of our feedback forum. Let us know what you think!

Just tried it, Looks good and works fine. Some great "new" features to. Like adding licenses to a Dynamics azure AD group.

* just one little bug (i think) when you add a simple rule for instance it gives an error because the variable you set is not set between quotes. When you go to the advanced and you set the quotes manual it works fine. (see attachments).

Click Licenses, choose a Product, Click assign, find a group, select it, then try to add another group, the first one goes away. Similar thing happens with Users. We should be able to keep adding users and groups until we are ready to Assign the license

It would be helpful it the Licensed User page had better search/filtering capabilities. for example, i want to find the users with a SharePoint license. Doing a search for SharePoint returns no results. Ideally, i could create a filter to easily find the users or groups that did or did not have specific license within a SKU.

@Nasos Kladakis one of the most common complaints/comments around the Azure AD blade is the fact that "regular" users get access to it. Now, I know you honor the UsersPermissionToReadOtherUsersEnabled setting, however other potentially sensitive information can be found there. Have you considered anything in this regard?

Granted, the same is true for the PowerShell modules, but the argument people make there is that PowerShell requires additional steps/install, and using the portal is just easy. I know some big changes are coming there that might address this (and I still hate you guys for not including O365 MVPs :p), but still.

Hey Vasil - we got this request a fair bit, so we added a setting. If you go to "User settings", there's a setting that says "Restrict access to Azure AD administration portal" which controls non-admin access. This just governs the portal experience - Graph/Powershell continue to have the same access.