Sign in Get started

DiligenceID + Microsoft Entra Verified ID

Keep Microsoft identity responsibilities clear.

DiligenceID can work alongside Microsoft Entra Verified ID—connecting managed credential capability to issuer operations, holder journeys, trust policy and relying applications.

Open DiligenceID See the architecture

Integration boundary

Complement, do not duplicate.

Existing authentication remains responsible for accounts and access. Verified ID provides Microsoft’s managed credential capability. DiligenceID connects that capability to the broader operational journey.

How DiligenceID works with Microsoft Entra Verified IDMicrosoft Entra ID continues authentication and access. Microsoft Entra Verified ID provides supported credential capability. DiligenceID coordinates issuer, verification, status, organisational context and API workflows for an organisation or application.MICROSOFT IDENTITYMicrosoft Entra IDAUTHENTICATIONMFA · ACCESS POLICYMICROSOFT CREDENTIAL CAPABILITYEntra Verified IDSUPPORTED ISSUANCEPRESENTATIONMICROSOFT-MANAGED INFRASTRUCTUREORGANISATIONApps + workflowsISSUER SYSTEMSRELYING SERVICESDILIGENCEID PRODUCT LAYERIntegration and lifecycleISSUER WORKFLOW · VERIFICATION · STATUS / REVOCATION · AUTHORITY · APIsTRUSTED EVIDENCE IN CONTEXTMicrosoft and DiligenceID responsibility boundariesMicrosoft identity and credential capabilities connect to the DiligenceID product layer, which connects configured workflows to an organisation or application.MICROSOFT IDENTITYMicrosoft Entra IDAUTHENTICATION · MFA · ACCESSMICROSOFT CREDENTIAL CAPABILITYEntra Verified IDISSUANCE · PRESENTATIONDILIGENCEID PRODUCT LAYERIntegration + lifecycleISSUER · VERIFY · STATUSAUTHORITY · APIsORGANISATIONApplications + workflowsISSUER + RELYING SERVICESTRUSTED EVIDENCE
DiligenceID complements Microsoft identity services; it does not replace authentication, MFA or Conditional Access, and it does not own Microsoft infrastructure.

Responsibilities

Three roles, kept deliberately distinct.

Clear ownership prevents a credential integration from being mistaken for authentication—or for a claim of Microsoft endorsement.

MICROSOFT PROVIDES

Verified ID capability

  • Managed verifiable credential capability
  • Supported issuance and presentation infrastructure
  • Integration within Microsoft identity environments
DILIGENCEID ADDS

Operational product layer

  • API orchestration and product journeys
  • Issuer, verifier and lifecycle workflows
  • Trust context and organisational authority
  • Status, revocation and audit integration
MAITS PROVIDES

Implementation services

  • Architecture and use-case design
  • Onboarding and integration
  • Microsoft identity and security advisory

DiligenceID is developed by MAITS Limited. This integration positioning does not imply Microsoft endorsement or partnership.

Microsoft capability

Use Verified ID precisely.

ISSUANCE

Credential issuance requests

Use Microsoft-supported interfaces to initiate a credential issuance journey and process the resulting application events.

PRESENTATION

Request and verify evidence

Ask a holder to present defined evidence and receive the verified outcome through supported request and callback patterns.

ADMINISTRATION

Service configuration

Manage supported authorities, contracts and service configuration through protected Microsoft administration interfaces.

LIFECYCLE

Status and revocation

Apply supported issuer revocation and evaluate credential status as part of relying-party policy.

Microsoft capability and interface details should be validated against current Microsoft Entra Verified ID documentation during solution design.

DiligenceID role

Connect verified evidence to the decision that matters.

DiligenceID can coordinate credential use-case design, issuer and verifier journeys, trust policy, lifecycle operations and relying-system integration.

The implementation boundary depends on Microsoft’s current interfaces, selected wallet, credential format, claims, status handling and the organisation’s privacy and retention obligations.

Journey designIssuer integrationVerifier integrationTrust policyOrganisation authorityAudit evidence

What remains unchanged

Credentials add evidence. IAM still controls access.

SIGN-IN

Microsoft Entra ID

Accounts, federation, authentication and sessions remain within the identity platform.

ASSURANCE

MFA and authentication strength

Credential presentation does not remove the need for proportionate authentication and recovery controls.

ACCESS

Conditional Access and authorisation

Applications and platforms continue to enforce their own access and business permission policies.

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 developed by MAITS Limited and is designed to complement Microsoft identity environments.

Does it replace Verified ID?

No. Where Verified ID is selected, DiligenceID can support the surrounding journeys, policy, lifecycle and application integration.

Does Verified ID replace sign-in or MFA?

No. Credentials provide evidence for a trust decision. Microsoft Entra authentication, MFA and Conditional Access continue to control sign-in and access.

Can credentials represent organisational authority?

A credential can represent a role, relationship or delegated authority where an authoritative issuer and relying-party policy support that meaning.

Put trusted evidence to work

Make Verified ID part of a complete trust journey.

Bring the credential use case, Microsoft environment and relying decision. Define the product boundaries before building the integration.

Get started Discuss Verified ID integration