Issuer
An authoritative organisation creates trusted digital evidence.
DiligenceID + Microsoft Entra Verified ID
Already using Verified ID?
Keep the investment.
DiligenceID is designed to work alongside Microsoft Entra Verified ID — extending credential journeys into business processes, trust policy and relying applications without pretending to replace Microsoft’s managed capability.
Interoperability, not replacement
Microsoft operates Verified ID. DiligenceID provides MAITS capability around credential use-case design, integration and trust journeys.
Integration architecture
Keep product responsibilities and business responsibilities clear.
The business system initiates and consumes the journey; DiligenceID connects policy and orchestration; Verified ID provides Microsoft’s managed credential capability.
BUSINESS SYSTEMApplication or serviceStarts the journey and consumes the result
↔INTEGRATION LAYERDiligenceIDJourney · policy · orchestration · relying integration
↔MICROSOFT CAPABILITYMicrosoft Entra Verified IDRequest Service API · Admin API · credential authority
The three-party model
Issuer, holder and verifier each have a different responsibility.
A useful credential architecture makes those roles explicit before selecting APIs, wallets or claims.
Holder / wallet
The person or organisation receives and controls the credential.
Verifier
A relying party requests proof and validates its issuer and status.
Service lifecycle
Design beyond issuance.
Credential operations need ownership from initial policy through status and evidence.
01Design
→02Issue
→03Hold
→04Present
→05Verify
→06Status
→07Audit
Microsoft capability boundary
Use Verified ID precisely.
Request Service API
Create an issuance request, give the holder a supported wallet journey and receive callback events for the application process.
Request and verify evidence
Ask a holder to present a credential and receive a verified outcome through the presentation request and callback pattern.
Admin API
Manage supported service configuration, authorities, contracts and credential administration through protected REST interfaces.
Status and revocation
Apply supported issuer revocation and evaluate credential status in the verification outcome as part of relying policy.
Capabilities and API details should be validated against current Microsoft Entra Verified ID documentation during solution design.
DiligenceID role
Connect credential proof to the decision that matters.
DiligenceID can frame the use case, shape issuer and verifier journeys, express trust policy, coordinate application integration and connect a verified result to the next business step.
The exact implementation depends on the selected Microsoft interfaces, wallet requirements, credential format, claims, lifecycle and the organisation’s retention obligations.
Journey designTrust policyIssuer integrationVerifier integrationStatus handlingAudit evidence
Organisation and authority
Prove who may act for whom.
Digital credentials can carry relationship evidence across boundaries where account federation alone does not express the required authority.
Employment and role
Present evidence of a current relationship, role, training or permission to another service.
Delegated authority
Show that a person is authorised to represent an organisation for a defined interaction.
Trusted participation
Support marketplaces, communities and partner services that need portable evidence, not a shared directory.
Application patterns
Use credentials where they improve a real trust decision.
Verified evidence before account creation
Request defined evidence, evaluate it, then create or link the account using only the data the process needs.
High-value workforce journeys
Use credential evidence within onboarding, partner, contractor or account re-establishment processes without replacing Entra sign-in.
Portable customer evidence
Let a customer present trusted evidence to an external identity journey while normal CIAM continues to manage their account and session.
Participant and authority checks
Verify qualification, membership or authority at the point of interaction across organisational boundaries.
Design horizon
Plan for open, replaceable trust boundaries.
Credential ecosystems are still evolving. A resilient architecture separates business trust policy from a single wallet, credential format or platform-specific interface where practical.
Potential future federation, registry and cross-ecosystem trust patterns should be treated as design considerations until support is confirmed in the selected products and standards profiles.
Frequently asked questions
Verified ID integration, without the ambiguity.
Is DiligenceID part of Microsoft Entra?
No. Microsoft Entra Verified ID is a Microsoft product. DiligenceID is a MAITS capability designed to complement Microsoft identity environments.
Does DiligenceID replace Microsoft Entra Verified ID?
No. Where an organisation has chosen Verified ID, DiligenceID can support the surrounding journeys, trust policy, orchestration and relying-system integration while retaining the Microsoft capability.
What do the Verified ID APIs do?
At a high level, the Request Service API supports issuance and presentation requests. The Admin API supports service administration such as authorities, contracts and supported credential lifecycle operations. The exact interface and licensing should be checked against current Microsoft documentation.
Does Verified ID replace sign-in or MFA?
No. Verifiable credentials provide evidence for a trust decision. Microsoft Entra authentication, MFA and Conditional Access continue to control sign-in and access.
Can a credential represent organisational authority?
A credential design can represent a role, relationship or delegated authority where an authoritative issuer and relying-party trust policy support that meaning.
Can credentials be revoked?
Microsoft Entra Verified ID supports issuer revocation for supported credentials and exposes status in verification outcomes. The lifecycle design must define when and by whom that action occurs.
Start a conversation
Make Verified ID part of a complete identity journey.
Bring the credential use case, Microsoft environment and relying decision. MAITS can help define the architecture and integration path.