

In case of approval is required, the application owner will get the request. This can be done with or without approval. Users can request new applications that are enabled for self-service. So what about the self service Jan? Well, under the ellipsis, the user can request new applications. You have to use in order to see the buttons. Strangely enough, the buttons to create and manage collections are not shown by default. Collections that are created by the user in the MyApps portal, can be edited from the MyApps portal itself, by clicking the Manage button at the top. At the time of writing, the owner can only manage these collections from the Azure Active Directory portal. This means they’ll have full editing rights to this collection. Users are able to create their own collections as well.Īpp collections can be targeted to specific users and groups, and each collection can have multiple owners. By default, it will display all your Azure AD and Office 365 apps, which you can also categorize in different collections. My Apps can be your users’ landing page for day-to-day work. In my opinion, this feature is way undervalued. In this article we take a look at the different portals that offer self service in Microsoft 365: Some of them you might already know, some might be new to you.

What if I told you that you can delegate most of these tasks to your end-users, their managers, or product-and application owners? In this blog post, I will show you the built-in capabilities of self-service in Azure Active Directory, which is underlying to Microsoft 365. The same applies to resetting passwords, handing out licenses, permissions, applications, and privileged roles. Maintaining security groups can be a laborious and cumbersome task to do. One of the great things about Azure Active Directory is the capability of self-service.
