We have the following setup:
- Azure as IAM for all employees
- we are building a new portal as an entry point for all the employees since the azure standard portal is not flexible to customize look and feel and UX
- This new portal is website is directly accessible via appLink.company.com
- once you access this "portal A" you have access to plenty of other application AppX AppY AppZ, also these applications are authenticated through Azure
- Normally the users can access all the apps through myapps.microsoft.com, including PortalA AppX AppY AppZ
- Recall that all these users have permissions to the applications
However, now we are deploying incrementally this portal to a set of groups of people so we will have two sets of users:
- set A: Users who will not have access to portalA and still need to go through myapps.microsoft.com to access AppX AppY AppZ
- set B: Users who will have access to portalA and NO NEED go through myapps.microsoft.com to access AppX AppY AppZ
We want to force the set B of users to access PortalA (appLink.company.com), the easiest setting would be to hide all the applications on myapps.microsoft.com, making the only way to access is through PortalA, however, the limitation in Azure is that once you set the visibility of an application to false, it is hidden for all users, and you cannot apply visibility per Groups / Users
Thus we are stuck and cannot proceed with Alpha/Beta testing and piloting with a subset of users with an incremental deployment due to the limitation
Any solution on how to allow the same users to have access to an application but change the application visibility on myapps.microsoft.com per Users/Group?


