Microsoft Entra Verified ID-supported standards

Note

Azure Active Directory Verifiable Credentials is now Microsoft Entra Verified ID and part of the Microsoft Entra family of products. Learn more about the Microsoft Entra family of identity solutions and get started in the unified Microsoft Entra admin center.

Microsoft is actively collaborating with members of the Decentralized Identity Foundation (DIF), the W3C Credentials Community Group, and the wider identity community. We’re working with these groups to identify and develop critical standards, and we've implemented the open standards in our services.

In this article, you'll find the currently supported open standards for Microsoft Entra Verified ID.

Standards bodies

Supported standards

Entra Verified ID supports the following open standards:

Technology stack component Open standard Standard body
Data model Verifiable Credentials Data Model v1.1 W3C VC WG
Credential format JSON Web Token VC (JWT-VC) - encoded as JSON and signed as a JWS (RFC7515) W3C VC WG /IETF
Entity identifier (issuer, verifier) did:web W3C CCG
Entity identifier (issuer, verifier, user) did:ion DIF
User authentication Self-Issued OpenID Provider v2 OIDF
Presentation OpenID for Verifiable Credentials OIDF
Query language Presentation Exchange v1.0 DIF
User authentication Self-Issued OpenID Provider v2 OIDF
Trust in DID (decentralized identifier) owner Well Known DID Configuration DIF
Revocation Verifiable Credential Status List 2021 W3C CCG

Supported algorithms

Microsoft Entra Verified ID supports the following key types for the JSON Web Signature (JWS) signature verification:

Key type JWT algorithm
secp256k1 ES256K
Ed25519 EdDSA

Interoperability

Microsoft is collaborating with organization members of Decentralized Identity Foundation (DIF), the W3C Credentials Community Group, and the wider identity community. Our collaboration efforts aim to build a Verifiable Credentials Interoperability profile to support standards-based issuance, revocation, presentation, and wallet portability.

Today, we have a working JWT verifiable credentials presentation profile that supports the interoperable presentation of verifiable credentials between wallets and verifiers/resource providers. Join us at the DIF Claims and Credentials working group, aka.ms/vcinterop.

Next steps