We have many use cases. We're an MSP that provides security solutions, and we deployed Entra ID for various clients, primarily for authentication to Office 365 or Azure. We also integrate it with on-prem environments using Azure AD Connect, now called Entra Server, to push identities into Azure Active Directory or Entra ID.
Entra allows us and our customers to access workloads on Azure and Office 365 securely. We've integrated it with other applications to provide a single pane of glass for user identification, eliminating the need for multiple IDs.
Our clients trust Entra ID as an identity service. We have deployed it in many places and always push it to our customers. We tell them that if they have a built-in application identity, they should change it to Entra ID and create application registrations and one identity.
MFA can do number matching, and the attacker can't get past it. We have lots of cases like that. Unfortunately, it's really hard to eliminate phishing completely