Microsoft Entra ID

Name: Microsoft Entra ID
Brand: Microsoft

Microsoft Entra ID is a cloud identity and access management service that authenticates users, enforces access policies (for example Conditional Access), provides single sign-on to SaaS applications, and manages identities across Microsoft cloud services and third-party apps.

Est 1975|Valuation $2888.5B|Raised $72.9B|58 Ref Customers

LinkedIn 29.0M|Website|Web traffic 1233.4M|FTEs 232,851|HQ Redmond, Washington, US

MarketsIdentity Provider (IdP) & Single Sign-On (SSO)Identity Governance & Administration (IGA)

Platform CoversPrivileged Access Management (PAM)SaaS Management

01Common complaints

- Company sizes or stages where this product is overkill or insufficient - Very small organizations that only need basic MFA for a few apps may prefer lighter-weight MFA vendors or SaaS-native MFA features. - Industries or use cases where competitors are more suitable - Highly heterogeneous SaaS environments seeking a neutral identity provider may find Okta or Ping more appropriate strategically. - Technical requirements that this product cannot meet - If specialized federation/authentication flows or extensive non-Microsoft IAM customization are required, platforms like PingFederate may better match technical needs. - Budget constraints that make alternatives more appropriate - If tens of thousands of intermittent or temporary identities require premium features, per-user pricing can make Entra less cost-effective. - Specific workflows or integrations where the product falls short - Complex provisioning transformations or certain group-based attribute provisioning patterns can be migration pain points when moving from other IDPs. - Red flags in the buying process (e.g., requires annual commitment, no free trial) - Entra ID P1 list pricing shown by Microsoft is billed with annual commitment; this can be a procurement constraint for some buyers. - Current limitations acknowledged by the vendor - SLA performance measurement exists, but buyers must interpret it in the context of their own dependency architecture. - Features on the roadmap (not yet available) - note estimated dates if available - Entra-related preview features continue to appear (example: Entra Agent ID preview). Preview maturity varies. - Scale limitations (at what volume/size does it break down?) - Large enterprises operate Entra at scale, but operational constraints are often related to licensing, governance processes, and integration complexity rather than raw tenant capability. - Security or compliance considerations - Using Entra does not automatically satisfy HIPAA/GDPR/other regulatory requirements; organizations must configure controls and map to compliance obligations. - Technical debt or architectural limitations mentioned in reviews - Identity platforms can include legacy components; buyers should track Microsoft’s patching and disclosure practices and plan compensating controls where necessary. - API limitations or integration constraints - SCIM provisioning has a specific implementation model; some advanced provisioning patterns require design workarounds.

Deal disqualifiers: what makes a POOR fit

Strong requirement for vendor-neutral IAM across many non-Microsoft identity ecosystems
Need for a simpler MFA-only solution without the broader Entra footprint
Very large populations requiring premium licensing where per-user costs are prohibitive (e.g., education/student populations, high-churn directories)

03Field reports

- Review platforms: broad sentiment patterns (high-level) - Gartner Peer Insights - Microsoft Entra ID has a Gartner Peer Insights reviews page. Access to full review text may be gated. - G2 - G2 lists Microsoft Entra ID reviews in high volume. - TrustRadius - TrustRadius lists Microsoft Entra ID reviews in high volume. - Representative community/customer quotes (positive and negative) - Positive / pragmatic value statements (community) - Reddit (cybersecurity): one commenter states “ADFS is legacy, most SaaS has moved to Entra ID” and describes Entra MFA options like Authenticator/FIDO2/Windows Hello, indicating Entra ID is commonly used in Microsoft-leaning environments. - Reddit (IAM): in a thread about whether Okta is still needed alongside Entra ID P2, users discuss that once a company standardizes on Microsoft 365/Intune/Entra licensing, “having Okta made less sense over time” (cost consolidation and platform simplification). - Negative / frustration signals (community) - Reddit (microsoft365): a recent post titled “Microsoft 365 / Entra support is honestly a joke.” While a single post isn’t definitive, it aligns with a broader pattern in Microsoft admin communities: support experiences vary substantially by support tier/contract and issue type. - Reddit (microsoftsucks): confusion and frustration about “What is a Microsoft Entra ID tenant?” and emails about tenant inactivity/purchases show that non-admin users can find Entra terminology confusing. - Common criticisms and complaints (from reviews and community patterns) - Licensing complexity and feature gating (P1/P2) - Admins frequently cite Conditional Access, Identity Protection, PIM, and governance features as valuable but sometimes costly when applied broadly. - Support quality variability - Complaints appear in sysadmin/M365 communities about support responsiveness and effectiveness. - UX / naming and product sprawl - Renaming (Azure AD → Entra ID) and adjacent Entra family products (Internet Access/Private Access/External ID/Governance) can increase buyer confusion. - Why customers chose this product over alternatives - Microsoft ecosystem integration - Organizations using Microsoft 365/Azure/Intune often have Entra ID already provisioned as the identity service, which reduces the need to adopt a separate identity provider. - App gallery and standard protocol support - Organizations use Entra as a SAML/OIDC identity provider for SaaS apps and leverage SCIM provisioning. - Governance/security depth at P2 - PIM and Identity Protection are frequently cited as reasons to upgrade to P2 rather than add separate tools. - Why some customers left for competitors (churn reasons) - Vendor neutrality / desire for a specialized solution - Organizations with diverse non-Microsoft stacks sometimes prefer Okta or Ping for a vendor-neutral posture, broader IDP patterns, or specific integration requirements. - Specialized capabilities - Some competitors are perceived as stronger for certain IAM sub-domains (for example, developer-centric CIAM/API access management in Okta/Auth0 ecosystems, or legacy federation patterns in PingFederate-heavy environments).

Microsoft Customer Story (vendor-published)

- Microsoft Security implemented Entra ID Governance and reports estimated substantial annual savings (vendor-published). - Critical evaluation - This is a vendor-published case study; the methodology behind reported savings and baselines is not independently audited in the public narrative. - The case study can be used as directional evidence for potential ROI drivers (automation, access reviews, reduced manual processes) when governance capabilities are deployed effectively.

Security posture initiatives (vendor-published)

Microsoft’s Secure Future Initiative (SFI) executive summary (late 2025) mentions progress items related to Entra ID security token signing and log retention.
Critical evaluation
- SFI is a corporate security initiative report; it indicates investment and internal prioritization, but it is not a substitute for product-specific third-party assurance for a buyer’s own risk program.

04Best fit

Company sizes

Strong fit: mid-market to large enterprises, particularly organizations standardized on Microsoft 365 E3/E5.
SMB fit: small-to-medium businesses using Microsoft 365 Business Premium and needing Conditional Access.
Note: very small teams can use the free tier, but advanced security features generally require paid licensing.

Industries and verticals where adoption is strongest (with customer examples)

Broad cross-industry adoption, with particularly high penetration in Microsoft-centric sectors (public sector, regulated industries using Microsoft suites, large enterprise IT).
Microsoft’s own internal use is highlighted in vendor-published customer stories for governance.

Roles and personas: decision makers AND end users

Decision makers
- CISO / Security leadership
- IAM program owners
- IT infrastructure leadership
- Microsoft 365/Azure platform owners
End users
- IT admins (identity, endpoint, security operations)
- Helpdesk (password reset, MFA enrollment, account lifecycle)
- Business app owners (SaaS SSO/provisioning)

Pain points and challenges the product addresses

Centralized authentication/SSO
MFA rollout and risk-based access
Access lifecycle automation via provisioning (SCIM)
Privileged access controls (PIM)

Qualification criteria: what makes a GREAT fit

Already standardized on Microsoft 365/Azure/Intune
Desire to consolidate IAM tooling and reduce the number of vendors
Willingness to invest in policy design, governance, and operational maturity

Real customer examples with company names when available

Microsoft (internal) case study for Entra ID Governance adoption (vendor-published customer story).

05The pitch

What the product does (core value proposition in objective terms)

Microsoft Entra ID (formerly Azure Active Directory/Azure AD) is Microsoft’s cloud identity and access management (IAM/IDaaS) service for authenticating users, enforcing access policies (for example Conditional Access), enabling single sign-on (SSO) to SaaS apps, and managing identities across Microsoft cloud services and third-party apps. (The vendor describes the product as a service to secure and manage identities in cloud and on-premises environments.)

Target market and market positioning

Most suitable for organizations standardized on Microsoft 365/Azure, where Entra ID functions as the primary identity service for Microsoft services.
Broad mid-market to enterprise adoption; also commonly used by SMBs via Microsoft 365 bundles.
Often evaluated as a platform IAM product against Okta, Ping Identity, Duo, JumpCloud, and other IDaaS vendors.

01Common complaints

Company sizes or stages where this product is overkill or insufficient
- Very small organizations that only need basic MFA for a few apps may prefer lighter-weight MFA vendors or SaaS-native MFA features.
Industries or use cases where competitors are more suitable
- Highly heterogeneous SaaS environments seeking a neutral identity provider may find Okta or Ping more appropriate strategically.
Technical requirements that this product cannot meet
- If specialized federation/authentication flows or extensive non-Microsoft IAM customization are required, platforms like PingFederate may better match technical needs.
Budget constraints that make alternatives more appropriate
- If tens of thousands of intermittent or temporary identities require premium features, per-user pricing can make Entra less cost-effective.
Specific workflows or integrations where the product falls short
- Complex provisioning transformations or certain group-based attribute provisioning patterns can be migration pain points when moving from other IDPs.
Red flags in the buying process (e.g., requires annual commitment, no free trial)
- Entra ID P1 list pricing shown by Microsoft is billed with annual commitment; this can be a procurement constraint for some buyers.
Current limitations acknowledged by the vendor
- SLA performance measurement exists, but buyers must interpret it in the context of their own dependency architecture.
Features on the roadmap (not yet available) - note estimated dates if available
- Entra-related preview features continue to appear (example: Entra Agent ID preview). Preview maturity varies.
Scale limitations (at what volume/size does it break down?)
- Large enterprises operate Entra at scale, but operational constraints are often related to licensing, governance processes, and integration complexity rather than raw tenant capability.
Security or compliance considerations
- Using Entra does not automatically satisfy HIPAA/GDPR/other regulatory requirements; organizations must configure controls and map to compliance obligations.
Technical debt or architectural limitations mentioned in reviews
- Identity platforms can include legacy components; buyers should track Microsoft’s patching and disclosure practices and plan compensating controls where necessary.
API limitations or integration constraints
- SCIM provisioning has a specific implementation model; some advanced provisioning patterns require design workarounds.

Deal disqualifiers: what makes a POOR fit

Strong requirement for vendor-neutral IAM across many non-Microsoft identity ecosystems
Need for a simpler MFA-only solution without the broader Entra footprint
Very large populations requiring premium licensing where per-user costs are prohibitive (e.g., education/student populations, high-churn directories)

03Field reports

Review platforms: broad sentiment patterns (high-level)
- Gartner Peer Insights
  - Microsoft Entra ID has a Gartner Peer Insights reviews page. Access to full review text may be gated.
- G2
  - G2 lists Microsoft Entra ID reviews in high volume.
- TrustRadius
  - TrustRadius lists Microsoft Entra ID reviews in high volume.
Representative community/customer quotes (positive and negative)
- Positive / pragmatic value statements (community)
  - Reddit (cybersecurity): one commenter states “ADFS is legacy, most SaaS has moved to Entra ID” and describes Entra MFA options like Authenticator/FIDO2/Windows Hello, indicating Entra ID is commonly used in Microsoft-leaning environments.
  - Reddit (IAM): in a thread about whether Okta is still needed alongside Entra ID P2, users discuss that once a company standardizes on Microsoft 365/Intune/Entra licensing, “having Okta made less sense over time” (cost consolidation and platform simplification).
- Negative / frustration signals (community)
  - Reddit (microsoft365): a recent post titled “Microsoft 365 / Entra support is honestly a joke.” While a single post isn’t definitive, it aligns with a broader pattern in Microsoft admin communities: support experiences vary substantially by support tier/contract and issue type.
  - Reddit (microsoftsucks): confusion and frustration about “What is a Microsoft Entra ID tenant?” and emails about tenant inactivity/purchases show that non-admin users can find Entra terminology confusing.
Common criticisms and complaints (from reviews and community patterns)
- Licensing complexity and feature gating (P1/P2)
  - Admins frequently cite Conditional Access, Identity Protection, PIM, and governance features as valuable but sometimes costly when applied broadly.
- Support quality variability
  - Complaints appear in sysadmin/M365 communities about support responsiveness and effectiveness.
- UX / naming and product sprawl
  - Renaming (Azure AD → Entra ID) and adjacent Entra family products (Internet Access/Private Access/External ID/Governance) can increase buyer confusion.
Why customers chose this product over alternatives
- Microsoft ecosystem integration
  - Organizations using Microsoft 365/Azure/Intune often have Entra ID already provisioned as the identity service, which reduces the need to adopt a separate identity provider.
- App gallery and standard protocol support
  - Organizations use Entra as a SAML/OIDC identity provider for SaaS apps and leverage SCIM provisioning.
- Governance/security depth at P2
  - PIM and Identity Protection are frequently cited as reasons to upgrade to P2 rather than add separate tools.
Why some customers left for competitors (churn reasons)
- Vendor neutrality / desire for a specialized solution
  - Organizations with diverse non-Microsoft stacks sometimes prefer Okta or Ping for a vendor-neutral posture, broader IDP patterns, or specific integration requirements.
- Specialized capabilities
  - Some competitors are perceived as stronger for certain IAM sub-domains (for example, developer-centric CIAM/API access management in Okta/Auth0 ecosystems, or legacy federation patterns in PingFederate-heavy environments).

Microsoft Customer Story (vendor-published)

Microsoft Security implemented Entra ID Governance and reports estimated substantial annual savings (vendor-published).
Critical evaluation
- This is a vendor-published case study; the methodology behind reported savings and baselines is not independently audited in the public narrative.
- The case study can be used as directional evidence for potential ROI drivers (automation, access reviews, reduced manual processes) when governance capabilities are deployed effectively.

Security posture initiatives (vendor-published)

Microsoft’s Secure Future Initiative (SFI) executive summary (late 2025) mentions progress items related to Entra ID security token signing and log retention.
Critical evaluation
- SFI is a corporate security initiative report; it indicates investment and internal prioritization, but it is not a substitute for product-specific third-party assurance for a buyer’s own risk program.

04Best fit

Company sizes

Strong fit: mid-market to large enterprises, particularly organizations standardized on Microsoft 365 E3/E5.
SMB fit: small-to-medium businesses using Microsoft 365 Business Premium and needing Conditional Access.
Note: very small teams can use the free tier, but advanced security features generally require paid licensing.

Industries and verticals where adoption is strongest (with customer examples)

Broad cross-industry adoption, with particularly high penetration in Microsoft-centric sectors (public sector, regulated industries using Microsoft suites, large enterprise IT).
Microsoft’s own internal use is highlighted in vendor-published customer stories for governance.

Roles and personas: decision makers AND end users

Decision makers
- CISO / Security leadership
- IAM program owners
- IT infrastructure leadership
- Microsoft 365/Azure platform owners
End users
- IT admins (identity, endpoint, security operations)
- Helpdesk (password reset, MFA enrollment, account lifecycle)
- Business app owners (SaaS SSO/provisioning)

Pain points and challenges the product addresses

Centralized authentication/SSO
MFA rollout and risk-based access
Access lifecycle automation via provisioning (SCIM)
Privileged access controls (PIM)

Qualification criteria: what makes a GREAT fit

Already standardized on Microsoft 365/Azure/Intune
Desire to consolidate IAM tooling and reduce the number of vendors
Willingness to invest in policy design, governance, and operational maturity

Real customer examples with company names when available

Microsoft (internal) case study for Entra ID Governance adoption (vendor-published customer story).

05The pitch

What the product does (core value proposition in objective terms)

Microsoft Entra ID (formerly Azure Active Directory/Azure AD) is Microsoft’s cloud identity and access management (IAM/IDaaS) service for authenticating users, enforcing access policies (for example Conditional Access), enabling single sign-on (SSO) to SaaS apps, and managing identities across Microsoft cloud services and third-party apps. (The vendor describes the product as a service to secure and manage identities in cloud and on-premises environments.)

Target market and market positioning

Most suitable for organizations standardized on Microsoft 365/Azure, where Entra ID functions as the primary identity service for Microsoft services.
Broad mid-market to enterprise adoption; also commonly used by SMBs via Microsoft 365 bundles.
Often evaluated as a platform IAM product against Okta, Ping Identity, Duo, JumpCloud, and other IDaaS vendors.

Microsoft Entra ID

01Common complaints

Deal disqualifiers: what makes a POOR fit

02Why they buy

03Field reports

Microsoft Customer Story (vendor-published)

Security posture initiatives (vendor-published)

04Best fit

Company sizes

Industries and verticals where adoption is strongest (with customer examples)

Roles and personas: decision makers AND end users

Pain points and challenges the product addresses

Qualification criteria: what makes a GREAT fit

Real customer examples with company names when available

05The pitch

What the product does (core value proposition in objective terms)

Target market and market positioning

01Common complaints

Deal disqualifiers: what makes a POOR fit

02Why they buy

03Field reports

Microsoft Customer Story (vendor-published)

Security posture initiatives (vendor-published)

04Best fit

Company sizes

Industries and verticals where adoption is strongest (with customer examples)

Roles and personas: decision makers AND end users

Pain points and challenges the product addresses

Qualification criteria: what makes a GREAT fit

Real customer examples with company names when available

05The pitch

What the product does (core value proposition in objective terms)

Target market and market positioning