Microsoft Dynamics 365

1Kosmos Achieves DoW IL4 Authorization to Secure Military Identities and Mission Access

Integration type

CRM

What we solve

Dynamics 365 customers need a scalable way to verify identities and enforce higher-assurance authentication inside Sales, Customer Service, and HR workflows without manual document checks or custom, hard-to-maintain integrations. This integration connects Dynamics 365/Dataverse events to 1Kosmos IDV and LiveID enrollment via Power Automate and an Azure Function webhook, writing verification status back into Dynamics so teams can gate sensitive actions (onboarding, account changes, contract execution) with automated IDV and step-up auth.

Attribute	Detail
Market share	~5% global, $8B ARR, strong in enterprises already on Microsoft 365
Marketplace	Microsoft AppSource / Azure Marketplace
Integration complexity	Medium-High (Dataverse custom entities + Power Automate + Azure Functions)
Est. build time	6-8 weeks
Primary use cases	Employee onboarding via HR module, customer KYC in financial services, step-up auth for ERP actions

Technical integration architecture

The Dynamics 365 integration leverages three Microsoft platform components: a Dataverse custom entity (1kosmos_verification), a Power Automate Cloud Flow, and an Azure Function for webhook reception. 1Kosmos already ships a Microsoft Azure Marketplace listing and Entra ID integration, so Dynamics represents a logical extension of the existing Microsoft partnership.

The Power Automate flow triggers on Dataverse record events (contact creation, opportunity stage change). It calls the 1Kosmos session API via an HTTP connector, stores the session reference, and monitors for the webhook callback via an Azure Function that writes results back to Dataverse. A model-driven app component renders IDV status and LiveID enrollment state on entity forms.

The Entra Verified ID integration is particularly relevant here. 1Kosmos already supports Entra Verified ID issuance, so verified credentials produced during Dynamics onboarding can be stored as W3C Verifiable Credentials in both the 1Kosmos blockchain and the user's Microsoft Authenticator wallet. This creates a reusable credential that works across the entire Microsoft ecosystem.

Dynamics-specific integration flow

Power Automate Cloud Flow:
    Trigger: When a row is added (Dataverse: Contact entity)
    │
    ▼
    Action: HTTP POST to https://api.1kosmos.com/v2/verify/sessions
    Headers: { "Authorization": "Bearer @{variables('1kosmos_token')}" }
    Body: {
        "subject_email": "@{triggerOutputs()?['body/emailaddress1']}",
        "subject_phone": "@{triggerOutputs()?['body/telephone1']

Power Automate Cloud Flow:
    Trigger: When a row is added (Dataverse: Contact entity)
    │
    ▼
    Action: HTTP POST to https://api.1kosmos.com/v2/verify/sessions
    Headers: { "Authorization": "Bearer @{variables('1kosmos_token')}" }
    Body: {
        "subject_email": "@{triggerOutputs()?['body/emailaddress1']}",
        "subject_phone": "@{triggerOutputs()?['body/telephone1']

Power Automate Cloud Flow:
    Trigger: When a row is added (Dataverse: Contact entity)
    │
    ▼
    Action: HTTP POST to https://api.1kosmos.com/v2/verify/sessions
    Headers: { "Authorization": "Bearer @{variables('1kosmos_token')}" }
    Body: {
        "subject_email": "@{triggerOutputs()?['body/emailaddress1']}",
        "subject_phone": "@{triggerOutputs()?['body/telephone1']

Dataverse custom entity (1kosmos_verification)

Column	Type	Description
1kosmos_sessionid	Single Line Text	Session identifier
1kosmos_contactid	Lookup (Contact)	Related contact
1kosmos_status	Choice	Pending, Verified, Failed, Expired
1kosmos_iallevel	Choice	IAL1, IAL2
1kosmos_documenttype	Single Line Text	Document type used for proofing
1kosmos_matchconfidence	Decimal	Biometric match score
1kosmos_liveidenrolled	Yes/No	LiveID enrollment status
1kosmos_credentialdid	Single Line Text	W3C DID reference
1kosmos_verifiedat	Date and Time	Verification timestamp
1kosmos_laststepupat	Date and Time	Last step-up authentication

Workflow insertion points

D365 Sales: Verify customer identity during lead qualification, gate contract execution behind LiveID
D365 Customer Service: Step-up auth before processing account changes or refunds via case workflow
D365 Human Resources: Verify new hire identity during onboarding, replacing manual I-9 document review
Power Pages: Embed IDV in external-facing portals for customer self-registration
Copilot for Sales: Plugin action allowing Copilot to trigger and check IDV status conversationally

Transform how you verify and authenticate

Secure onboarding, eliminate passwords, and stop fraud on one platform. Schedule a demo and see it in action.

Request a demo

Talk to sales

Transform how you verify and authenticate

Secure onboarding, eliminate passwords, and stop fraud on one platform. Schedule a demo and see it in action.

Request a demo

Talk to sales

Transform how you verify and authenticate

Secure onboarding, eliminate passwords, and stop fraud on one platform. Schedule a demo and see it in action.

Request a demo

Talk to sales