All tenant users (without dynamic AAD group).To summarize, we needed to have the following flexibilities for adding the app to the launcher. There are other customers who are not using Premium Azure Active Directory (level 2, with Dynamic Groups), but needing it to be available tenant wise. There are customers using the product in trial mode would need the app to be made available only to a limited set of users for testing and evaluation purposes. Given the access sensitivity required for the app, we faced different requirements for adding the app to launcher as was warranted by customer’s IT policy. Directory schema extension attributes – Extend the schema of service principal and user objects to store additional data in Azure AD.OAuth authorization services – Used by Microsoft 365 and other Microsoft applications to authorize access to APIs/resources.Role-based access control – Use the directory to define application roles to perform role-based authorization checks in an application.

Application authentication and authorization.

The formal touch points of services for our Azure AD app can be summarized as follows. In our case, we were dealing with a Governance application (Govern 365) having the ability to provision and monitor various Office 365 workloads such as SP Sites, O365 Groups, MS Teams etc. As you know, an Azure AD app can potentially enjoy different levels of access into your tenant and hence may need to be added into the app launcher carefully. Let me get into the context of adding an Azure AD app into the M365 launcher at the onset.

Information Protection and Compliance (17).

SharePoint On-Prem to SharePoint Online Migration (6).

Microsoft 365 Tenant-to-Tenant Migration (4).

Google Workspace to Microsoft 365 Migration (8).Documentum to Microsoft 365 Migration (2).Cloud Infrastructure and Management (56).

O365 app launcher