Vendor evidence profile
Microsoft Entra ID: what the public record shows
nexalign keeps a continuously updated evidence record on Microsoft Entra ID for identity and access management decisions: 41 items from 6 kinds of source, covering June 2025 to July 2026. Every item on this page links to the source it came from, carrying the date that source states and saying so plainly where it states none.
In one line
This record holds 5 advisories attributed to Microsoft Entra ID products across 41 evidence items in total, none of them in the CISA catalogue of known exploited vulnerabilities. 100 percent of the record comes from sources Microsoft Entra ID cannot edit. Whether Microsoft Entra ID suits your decision is not on this page: that depends on your criteria, your compliance scope and your shortlist, and this record does not know them.
Evidence items
41
in this record
Attributed advisories
5
none known exploited
Authoritative share
68%
government registers
Last checked
Jul 17, 2026
sources re-queried
How independent is this record
Sources are not equal. A vendor can rewrite its own website overnight and optimise it for whatever a language model is likely to quote. It cannot edit a government vulnerability register or a years-old discussion thread. Every item in this record is classified by how much the vendor could influence it, and the score below is the weighted result.
Independence of this record
Objectivity score 87/100
- Authoritative
- 28 items, 68 percent
- Independent
- 13 items, 32 percent
- Vendor-controlled
- 0 items, 0 percent
100 percent of this record comes from sources Microsoft Entra ID does not control. The remainder is Microsoft Entra ID's own material and is marked as such wherever it appears.
Where this record comes from
These are the sources that contributed to the Microsoft Entra ID record, with the body that operates each one. No rating, score or ranking is taken from anywhere, and no vendor pays to appear in this index or to change what it says.
| Source | Operated by | Classification | Items | Latest |
|---|---|---|---|---|
| National Vulnerability Database | NIST, United States Department of Commerce | Authoritative | 21 | Jul 16, 2026 |
| European Vulnerability Database | ENISA, European Union | Authoritative | 5 | Jun 24, 2026 |
| CERT-Bund security advisories | BSI, Federal Republic of Germany | Authoritative | 2 | May 26, 2026 |
| Practitioner discussions | Reddit, public threads | Independent | 5 | Apr 01, 2026 |
| Engineering discussions | Hacker News, public threads | Independent | 4 | Jul 15, 2026 |
| Analyst, review and reference sources | Recognised analysts, review marketplaces and technology press | Independent | 4 | Jul 17, 2026 |
Documented vulnerabilities
Vulnerability registers are searched by keyword, so an advisory about a different product often mentions Microsoft Entra ID in passing. An entry is only listed here when a structural signal ties it to a product of Microsoft Entra ID: an advisory reference on the vendor's own domain, Microsoft Entra ID as the assigning authority, or the affected product list naming it. 5 records passed that test.
- CVE-2026-32208highCVSS 8.8Jun 19, 2026
Improper neutralization of input during web page generation ('cross-site scripting') in Microsoft Entra ID allows an authorized attacker to perform spoofing over a network.
- WID-SEC-2026-1636highCVSS 10.0May 26, 2026
Affected products: Microsoft Entra, Microsoft Azure
- CVE-2026-42901criticalCVSS 10.0May 22, 2026
Origin validation error in Microsoft Entra ID allows an unauthorized attacker to elevate privileges over a network.
- WID-SEC-2026-1273highCVSS 10.0Apr 27, 2026
Affected products: Microsoft Entra
- CVE-2026-35431criticalCVSS 10.0Apr 23, 2026
Server-side request forgery (ssrf) in Microsoft Entra ID Entitlement Management allows an unauthorized attacker to perform spoofing over a network.
What practitioners report
Public threads in which engineers and administrators discuss running this product. Only threads naming Microsoft Entra ID in their own title are listed, so a discussion about someone else's incident cannot end up under this vendor. Not curated for sentiment: 4 threads in the record, most recent first.
- Hacker NewsJul 15, 2026Independent
Microsoft Entra ID Will Retire SMS and Voice Authentication
- r/sysadminMar 19, 2026Independent
Microsoft introduces Backup and Recovery for Microsoft Entra ID!
- Hacker NewsSep 19, 2025Independent
Microsoft Entra ID Vulnerability Could Have Been Catastrophic
- Hacker NewsAug 13, 2025Independent
New downgrade attack can bypass FIDO auth in Microsoft Entra ID
The source ledger counts 5 further threads on these platforms that mention Microsoft Entra ID somewhere in the discussion without naming it in the title. They are searched and counted, and they are not listed as reports about this vendor.
Independent coverage
Recognised analysts, review marketplaces and neutral technology press that name Microsoft Entra ID. This section runs on a fixed list of such outlets rather than on whatever a web search returns for the company name, because that search is dominated by sales-intelligence profiles and directory listings which say nothing about the product. Social networks and press-release wires are excluded outright.
- peerspot.comdate not recordedIndependent
Microsoft Entra ID (Azure AD) reviews, pricing and features 2026
- gartner.comdate not recordedIndependent
Microsoft Entra ID Reviews & Ratings 2026 | Gartner Peer Insights
- gartner.comdate not recordedIndependent
Top Microsoft Entra ID Alternatives & Competitors 2026 | Gartner Peer Insights
- gartner.comdate not recordedIndependent
Microsoft Entra ID Reviews, Ratings & Features 2026 | Gartner Peer Insights
What Microsoft Entra ID publishes about itself
The vendor's own documentation, kept separate from everything above and marked as vendor-controlled. It is useful, and it is a claim until an independent source confirms it.
What this record cannot tell you
A record is only trustworthy if it is explicit about its holes. These are the ones in the Microsoft Entra ID record right now.
A further 23 register entries mention Microsoft Entra ID without naming a product of Microsoft Entra ID as affected. They are excluded rather than counted as vulnerabilities.
Pricing, contract terms, notice periods and support commitments are not part of any public register. They come from the vendor and belong in a negotiation record.
Certification status such as ISO 27001, SOC 2 or BSI C5 has to be checked against the current certificate and its stated scope. A valid certificate can still exclude the product being bought.
Whether Microsoft Entra ID is the right choice is not on this page
A record of what is true about a vendor is one half of a decision. The other half is your context: which criteria matter, how heavily each one weighs, what is a hard no, and who has to sign the result off. No public page can know that, and any page that claims to rank vendors for you is guessing at it.
Typical criteria for this category
Needs your case- SSO / SAML / OIDC Integrationweight
- Privileged Access Managementweight
- Identity Governance & Access Certificationweight
- SCIM Provisioning / Lifecycle Managementweight
- Zero-Trust Architecture Supportweight
Criteria shown as examples for identity and access management. Weighting and fit are properties of your decision, not of the vendor, so they are not published here.
What DecisionOS adds on top of this record
- The vendor scored against your criteria with your weighting, not against a generic ranking
- A dealbreaker check against your hard constraints: data residency, contract terms, existing stack
- A side-by-side view of the alternatives on your shortlist, built from this same evidence pool
- This evidence mapped onto your compliance scope: NIS2, DORA, ISO 27001, SOC 2
- A decision memo your board can read, with the trade-offs and the reasoning on the record
Questions this page answers
Is Microsoft Entra ID a safe choice?
The public record holds 5 advisories attributed to Microsoft Entra ID products and 41 evidence items in total. None of them appears in the CISA catalogue of known exploited vulnerabilities. Whether that is acceptable depends on your risk appetite, your compliance scope and the alternatives on your shortlist, none of which a public page can know. This page reports the record; it does not rate the vendor.
Where does the Microsoft Entra ID data on this page come from?
From 6 kinds of source: National Vulnerability Database, operated by NIST, United States Department of Commerce; European Vulnerability Database, operated by ENISA, European Union; CERT-Bund security advisories, operated by BSI, Federal Republic of Germany; Practitioner discussions, operated by Reddit, public threads; Engineering discussions, operated by Hacker News, public threads; Analyst, review and reference sources, operated by Recognised analysts, review marketplaces and technology press. Every item carries its source URL and, where the source states one, its date.
Does Microsoft Entra ID pay to appear in this index?
No. There is no paid placement, no sponsored profile and no way for a vendor to change what the record says. Vendors are listed because their category comes up in enterprise technology decisions. Corrections to a specific entry can be sent to [email protected] and are checked against the source.
How much of the Microsoft Entra ID record is the vendor's own material?
0 percent. The remaining 100 percent comes from sources Microsoft Entra ID does not control. Vendor-published material stays in the record and is labelled as vendor-controlled rather than counted as independent confirmation.
Why does this page not say whether Microsoft Entra ID is better than the alternatives?
Because better only exists relative to a decision. Which criteria matter, how heavily each one weighs and what counts as a dealbreaker are properties of the buyer, not of the vendor. DecisionOS takes this same evidence pool and scores it against the criteria of an actual decision, which is where a comparison becomes meaningful.
How this record is built
Sources are queried on a schedule, not on request. Findings are stored with the source URL, the event date and a content hash, so the same item is never counted twice and every statement stays traceable to where it came from.
Nothing on this page is written by a language model. Counts are counts, dates are the dates the sources carry, and titles are the sources' own wording. Where a section is empty, that is a finding in itself and is stated as one.
Corrections are welcome. If an entry is wrong or an attribution is off, write to [email protected] and it gets checked against the source.
Citing this page
nexalign GmbH, Microsoft Entra ID: what the public record shows, nexalign vendor evidence index, Jul 17, 2026. Available at nexalign.io/vendors/microsoft-entra-id.
Microsoft Entra ID next to a product it competes with
The same two records side by side, with the reasons their numbers cannot be subtracted from one another stated on the page.
Other vendors in identity and access management
The whole field is on one page: every identity and access management vendor with a published record, with the size of each.
Okta
83 evidence items from 6 sources
Auth0
36 evidence items from 3 sources
Ping Identity
34 evidence items from 5 sources
Omada Identity
28 evidence items from 3 sources
ForgeRock
26 evidence items from 4 sources
OneLogin
22 evidence items from 5 sources
Turn this record into a decision you can defend
DecisionOS takes the same evidence pool this page is built from, weighs it against the criteria of your actual decision, and produces a memo that holds up in front of a board and an auditor.