Issuer
An authoritative organisation creates trusted digital evidence.
DiligenceID · Portable digital trust
Evidence you can trust.
Only when needed.
Infrastructure and identity expertise for issuing, holding and verifying reusable digital credentials — without turning every interaction into another account, upload or copy of personal information.
IssueHoldPresentVerifyTrustGovern
A different trust pattern
Ask for evidence, not another data collection exercise.
Organisations routinely ask people to create accounts, upload documents and surrender copies of information just to prove one fact.
DiligenceID supports a more focused model: an authoritative source issues trusted digital evidence; the holder keeps it in a supported wallet; and a verifier requests the proof required for a particular interaction.
It is part of a broader identity ecosystem. It does not replace directories, authentication, MFA, application access or identity governance.
Identity attributesEmploymentQualificationsLicencesPermissionsMembershipsEligibilityDelegated authority
Issue → Hold → Verify
A simple model for portable trust.
Three roles separate the source of evidence, the party who holds it, and the organisation making a trust decision.
Holder / wallet
The person or organisation receives and controls the credential.
Verifier
A relying party requests proof and validates its issuer and status.
Know the difference
Sign-in, identity evidence and authority answer different questions.
Treating them as interchangeable creates friction and weakens trust. A well-designed journey uses each control for the decision it is meant to support.
“Can this party sign in?”
Account and authentication
Establishes control of an account or authenticator. MFA and passkeys can strengthen that sign-in, but do not by themselves prove every real-world fact about the person.
“What trusted fact can they prove?”
Verified identity evidence
Connects a claim to an authoritative source — for example a qualification, licence, employment relationship or eligibility decision.
“What are they entitled to represent or do?”
Credential and access decision
Lets a verifier evaluate the presented evidence, issuer and status against policy before granting a service, role or interaction.
From idea to trusted operation
A credential is a governed lifecycle.
Useful digital evidence needs defined authority, journeys, lifecycle, status and evidence — not only a credential format.
01Design
→02Issue
→03Hold
→04Present
→05Verify
→06Status
→07Audit
For business and identity leaders
Reusable evidence can reduce friction without weakening trust.
Reduce repeated collection
Avoid asking people to resubmit the same documents and attributes for every relationship or service.
Make trust decisions clearer
Define which issuer, credential type, status and evidence satisfy a transaction.
Connect organisations
Carry trusted evidence across organisational boundaries without creating a bespoke account federation for every interaction.
DiligenceID + Microsoft Entra Verified ID
Complement your Microsoft identity investment.
Organisations using Microsoft Entra Verified ID do not need to abandon that capability to adopt DiligenceID.
Microsoft describes Verified ID as a managed verifiable credential capability based on open standards. It supports issuing and requesting verifiable credentials, holder-controlled presentation, verification and credential lifecycle scenarios.
DiligenceID is intended to work alongside Microsoft identity environments — connecting credential use cases, journeys, trust policy and integration services around the platforms an organisation already uses.
Explore the integration architectureEXISTING ENVIRONMENTEnterprise identityPeople · directories · source systems
MICROSOFTEntra ID
01Microsoft Entra Verified ID
02Enterprise applications
DILIGENCEIDIntegration, journeys and trust services
- Credential issuance
- Credential verification
- Wallet journeys
- Trust policy
- Credential services
Microsoft Entra Verified ID is a Microsoft product. DiligenceID is a MAITS capability and is not part of, certified by or endorsed by Microsoft.
What Verified ID does
Identity proof, not sign-in.
Microsoft Entra Verified ID can support the issuance and verification of verifiable credentials for onboarding, workforce and partner interactions, high-value access decisions and identity re-establishment scenarios such as account recovery.
Verified ID does not replace normal Microsoft Entra sign-in, MFA or self-service password reset. It provides cryptographic evidence for identity verification and credential-based trust decisions; authentication and access controls still do their existing jobs.
MAITS can help plan where credential evidence belongs in the wider identity and access architecture.
Read Microsoft’s Verified ID documentationPrivacy by design
Request the proof required for the transaction — not a copy of everything.
Consent and holder control
The holder sees a request and chooses whether to present the credential through the supported wallet journey.
Data minimisation
Design the request around the claims required for the decision, reducing unnecessary collection of personal information.
Selective disclosure
Where supported by the credential format and platform, disclose specific claims or derived facts rather than an entire record.
Trust policy
Make accepted issuers, credential types, assurance requirements and decision rules explicit.
Credential status
Check validity, expiry and status when the selected platform and credential design support those capabilities.
Proportionate retention
Separate evidence validation from the decision about what the relying organisation genuinely needs to retain.
A transparent request
The holder should understand the trust decision.
01
Who is asking? Make the verifier and the service they represent clear.
02
What evidence is required? Request the minimum claims needed for the decision.
03
Why is it required? Explain the purpose before the holder chooses to present it.
04
What happens next? State how the result informs access, eligibility or another transaction.
Use cases
Trusted evidence across the moments that matter.
Employees and contractors
Prove employment, training, clearance, role, contractor status or organisational authority across teams and sites.
Learning and qualifications
Issue and verify student identity, qualifications, certifications, completed training and alumni evidence.
Eligibility and standing
Request evidence of eligibility, licence, authority or professional standing for a regulated interaction.
Reusable customer evidence
Reduce repeated document collection and let trusted evidence support a more focused onboarding decision.
Authority to act
Let a person prove that they represent an organisation or hold a defined delegated authority.
Trusted participation
Support verified participants, qualifications, permissions and accountable interactions in digital ecosystems.
Organisation identity
Trust the relationship, not only the person.
Some transactions depend on whether a person is authorised to act for an organisation at that moment.
IAM → digital trust
Extend governed identity across organisational boundaries.
Traditional IAM controls accounts and access inside systems. DiligenceID adds portable evidence, issuer trust and organisational authority to that established foundation.
Diligence Wallet
A place to hold and present credentials.
Diligence Wallet is the wallet experience within the DiligenceID ecosystem. It gives holders a way to receive, store and present supported digital credentials.
It is distinct from Microsoft products. When a scenario specifically uses Microsoft Entra Verified ID, the selected Microsoft-compatible wallet experience and Microsoft’s current product requirements must be considered as part of the design.
Standards and interoperability
Digital credentials should not become another closed identity silo.
Use standards where they create portable, replaceable integration boundaries.
DiligenceID’s integration approach is designed around standards-based issuer and verifier patterns. Depending on the credential ecosystem and platform support, an architecture may use OpenID for Verifiable Credential Issuance, OpenID for Verifiable Presentations, SD-JWT VC and OpenID Connect integration patterns.
The standards profile is selected for the specific deployment. Support should be verified against the chosen wallet, issuer, verifier and credential platform rather than assumed from a protocol label alone.
Technical view
Architecture work considers credential format, issuer authority, wallet compatibility, presentation exchange, trust registry or policy, status checking, key management, subject binding, claims minimisation and how verified evidence is passed to relying applications.
Why MAITS
Identity→Authentication→Access→Governance→Credentials→Trust
DiligenceID is a logical extension of MAITS’ IAM expertise — not an isolated technology experiment.
Frequently asked questions
Digital credentials, in practical terms.
What is a digital credential?
A digital credential is tamper-evident, machine-verifiable evidence issued by an authoritative organisation. It can represent an attribute, qualification, licence, permission, relationship or other trusted claim.
Is DiligenceID a replacement for Microsoft Entra Verified ID?
No. DiligenceID is positioned as complementary. It can support credential journeys and integration around Microsoft Entra Verified ID while allowing an organisation to retain its Microsoft identity investment.
Can DiligenceID work with organisations already using Microsoft Entra?
Yes. DiligenceID is designed to work alongside Microsoft identity environments, including scenarios that use Microsoft Entra ID and Microsoft Entra Verified ID. The exact architecture depends on the organisation’s platforms, credential formats and trust requirements.
Does the organisation need to store another copy of all the holder’s personal information?
Not necessarily. A well-designed credential journey requests only the evidence required for a transaction. What is retained depends on the use case, legal obligations, trust policy and the selected implementation.
What can a digital credential represent?
Examples include employment, training, qualifications, licences, memberships, eligibility, organisational authority, delegated authority and relationships.
Can credentials expire or be revoked?
Credentials can include validity periods and can support status checking, revocation or invalidation when the selected credential platform and design support those controls.
Does DiligenceID replace IAM?
No. IAM still manages identities, authentication, accounts and access within systems. DiligenceID extends trust into credential-based interactions between holders, issuers and verifiers.
Start a conversation
Plan a credential use case that fits your identity ecosystem.
Bring the business decision, evidence and trust relationships. MAITS can help shape the credential journey and the integration around Microsoft Entra Verified ID or another standards-aligned environment.