What happens at sign-in
the user is redirected to Entra ID, verifies their identity (including multi-factor authentication, if the company requires it), and the app receives a token with their identity. The password never passes through the app.
Case study
A company app should have no passwords of its own. Users sign in with the account they already have, and the app asks Entra ID who they are and what they may do. When an employee leaves, it is handled in one place — by disabling the account, not by hunting through apps.
the user is redirected to Entra ID, verifies their identity (including multi-factor authentication, if the company requires it), and the app receives a token with their identity. The password never passes through the app.
the app is not published to the whole tenant. Only someone assigned to the app may sign in, and assignment happens through group membership, not per individual.
membership in security groups decides what the user sees in the app. IT manages the groups where it always has; the app only asks. Roles are never set inside the app itself.
permissions stay as narrow as possible. Storage access is granted to one specific place, not to the whole tenant; until an administrator allows it, the app sees nothing.
Microsoft, Azure, Microsoft 365, Entra, Teams, SharePoint, Intune, Defender and Copilot are trademarks of the Microsoft group of companies.
NOVOTNACI is an independent service provider and is not owned by or affiliated with Microsoft. · © 2026 NOVOTNACI ·
Privacy Policy ·
This site uses no cookies and no analytics.