Native Dynamics 365 Sales, built on Dataverse Web API.
Cloop syncs Accounts, Leads, Contacts, and Opportunities to Dynamics 365 Sales through the Dataverse Web API, not middleware, not a legacy connector. Authentication via Microsoft Entra ID (Azure AD) with full Conditional Access policy support. Triggers Power Automate flows, advances Business Process Flows, and sends notifications to Microsoft Teams. Common among IT services, financial services, and enterprise B2B firms running Microsoft-centric stacks.
In one sentence
Cloop syncs into Dynamics 365 via Dataverse Web API, Accounts, Leads, Contacts, and Opportunities, Entra ID authentication, Power Automate-ready, included in every plan.
Dataverse Web API · Entra ID auth · Power Automate-ready
A complete Dataverse record. With Business Process Flow context.
Cloop syncs Account, Lead, Contact, Opportunity, and Activity entities, respecting Business Unit hierarchy, Security Roles, and Record Ownership rules.
- 01 Account record
Cloop identifies the visiting company via IP2Company and creates or updates the Dynamics 365 Account, with Industry, Number of Employees, Annual Revenue, Founded Year, Website, and Address. Matches existing Accounts by domain to prevent duplicates. Respects Business Unit ownership.
- 02 Lead or Contact record
Depending on your Dynamics 365 setup, Cloop creates a Lead (for unqualified prospects) or a Contact associated with an existing Account. Custom entities and custom fields populate from the conversation. Record Types and Forms respected.
- 03 Opportunity creation
For qualified deals, Cloop creates an Opportunity in your pipeline, with Sales Stage, Estimated Revenue, Estimated Close Date, and associations to Account and Contact. Sales Process flows (Business Process Flows) are triggered automatically.
- 04 Intent signals as custom fields
Structured intent data flows into custom fields on Lead and Opportunity, pages visited, areas of interest, questions asked, overall intent score (0–100). Turns Dynamics 365 views and dashboards into intent-aware priority queues.
- 05 Conversion page and source
Captured as Lead Source, UTM tracking fields, or custom attributes, which page started the conversation, which campaign drove the visit, which content the visitor engaged with. Campaign attribution flows into Dynamics 365 Marketing reports.
- 06 AI conversation summary as Task or Note
A concise AI-generated summary of the conversation is logged as a Task or Annotation on the Lead and Contact. Your seller prepares for the meeting in 60 seconds by reading the summary, not 15 minutes parsing a raw transcript.
- 07 Session context as custom fields
Full visitor session history, pages browsed before and after the conversation, is captured for context. Your team sees the complete buyer journey within the Dynamics 365 record timeline.
- 08 Next-step recommendations as Tasks
Cloop's AI generates concrete recommendations, which collateral to send, which objections to prepare for, which Sales Stage is realistic, which pricing tier fits. Delivered as Tasks assigned to the Record Owner.
authentication native, Conditional Access fully respected
Cloop authenticates via Microsoft Entra ID (Azure AD) OAuth 2.0 and respects your organization's Conditional Access policies without exception, MFA, device compliance, location rules, risk-based sign-in. Dataverse Web API direct, Power Automate flows fire natively, Business Process Flows advance automatically, Microsoft Teams notifications built in.
The right Dynamics 365 Owner. Every time.
Cloop reads territory, business unit, role-based access, and ownership rules from Dataverse, then assigns each qualified conversation to the rep already accountable. Conditional Access policies and Entra ID groups are honored end-to-end.
- 01 By ICP segment
Enterprise Leads route to named Enterprise sellers. Mid-market Leads to the mid-market team. SMB Leads to inside sales. Each segment finds the right Owner automatically.
- 02 By Business Unit
Dynamics 365 Business Unit hierarchy respected, Finland team handles Finnish Accounts, Nordic team handles Nordic, Enterprise Business Unit handles large Accounts. Owner assignment follows organizational structure.
- 03 By Account ownership
If the visiting company is already an Account with an existing Owner, the Lead or Opportunity routes directly to that Owner, not through round-robin. Existing relationships protected.
- 04 By industry or vertical
Industry values map to specialist Owners. Financial Services to FS team. Manufacturing to industrial. SaaS to the tech practice. Subject-matter expertise matches the opportunity.
- 05 By territory or region
Dynamics 365 Territory Management respected, regional sellers handle their territory, with Out-of-Office fallbacks. Territory hierarchies honored.
- 06 Round-robin fallback
When no specific rule applies, Cloop uses fair round-robin within the configured team. Workload stays balanced and no Lead sits unassigned.
Meetings land on the right calendar. Workflows fire with better data.
Each booked meeting writes back as an Appointment in Dynamics 365 with the conversation transcript, AI summary, and intent score. Hot-lead criteria fire your Power Automate flows and advance Business Process Flow stages the moment the threshold is crossed.
Researching AI sales tools. 85-person consulting firm. Uses HubSpot and Pipedrive. Budget ~€5K/mo. Timeline Q2 2026. Focus on Finnish market.
- Lead Score ≥ 80Notify seller via Teams · Create urgent Task · Advance Business Process Flow
- Enterprise Account detectedRoute to Enterprise seller · Add to ABM program · Trigger Power Automate flow
- Existing Customer conversationNotify Account Manager · Flag as expansion in Dataverse · Update Account health
- Specific product interestRoute to product specialist · Send relevant content · Update Opportunity Product lines
15 minutes via Entra ID. Conditional Access preserved.
Connect via Entra ID with the standard Cloop scopes; your existing Conditional Access policies and Privileged Identity Management rules continue to apply unchanged. No middleware, no custom code, no IT escalation.
- 01 Authorize Dynamics 365
One click in your Cloop dashboard. Microsoft Entra ID (Azure AD) OAuth flow grants Cloop permission to read and write Dataverse entities. Works with Production and Sandbox environments, across all Dynamics 365 Sales licenses.
- 02 Map your entities and fields
Configure which entities Cloop creates (Lead vs Contact, whether to create Opportunities directly), which Business Process Flow to trigger, which custom fields to populate, and how to match existing Accounts by domain or name.
- 03 Configure routing and Ownership
Set Lead assignment rules by ICP, Business Unit, industry, or Account Owner. Respect existing Dynamics 365 Assignment Rules, Territory configuration, and Security Role permissions. Test with live data before going live.
- 04 Activate and monitor
Activate on your site. Watch records flow into Dynamics 365 in real time. Cloop's dashboard shows every sync event, successful creates, updates, field mappings, with full transparency and debugging for your Dynamics 365 admins.
Dynamics 365 integration questions.
Which Dynamics 365 licenses does Cloop support?
Cloop works with Dynamics 365 Sales Professional, Sales Enterprise, and Sales Premium. Core integration uses Dataverse Web API. Advanced features like custom entities and Business Process Flow automation are supported on Sales Enterprise and higher.
Does Cloop work with on-premises Dynamics or only cloud?
Cloop currently supports Dynamics 365 Online (cloud) deployments. On-premises Dynamics CRM (Dynamics 365 Server) is not supported. If you're migrating to the cloud, Cloop integrates with both your existing and new environments during transition.
Does Cloop support custom entities and custom fields?
Yes. During setup, map Cloop data to any combination of standard entities (Lead, Contact, Account, Opportunity) and custom entities you've built in Dataverse. Custom fields for intent score, conversation page, industry enrichment, and AI summary are fully supported.
How does Cloop work with Business Process Flows?
Cloop can create records at any stage of a Business Process Flow. For qualified Leads, Cloop can start them at the 'Qualify' stage with the right attributes populated, letting your existing BPF guide the seller through the rest. Alternatively, Cloop can create Opportunities directly at a later stage if qualification is complete.
Can Cloop use Microsoft Entra ID (Azure AD) for authentication?
Yes. Cloop's Dynamics 365 integration uses OAuth 2.0 via Microsoft Entra ID. This supports Single Sign-On with your organization's existing identity provider, Multi-Factor Authentication, and Conditional Access policies.
Is Cloop listed on Microsoft AppSource?
Cloop uses Dynamics 365's standard Web API directly, no AppSource managed solution required. This avoids the overhead of a managed package and supports faster iteration. AppSource listing is on our roadmap for 2026.
How does Cloop handle data privacy across Dynamics 365 and Cloop?
All customer data stored by Cloop is hosted in Helsinki, Finland (EU). Dynamics 365 data is accessed through Microsoft's official Dataverse Web API under your tenant's permissions. Cloop does not train AI on customer conversation data.
An AI sales agent. Fits natively into Microsoft stacks.
Cloop is not a Microsoft-only product, but for teams running Microsoft-centric stacks, Dynamics 365 Sales, Entra ID, Microsoft Teams, Power Automate, the integration is native by design. Authentication respects your Conditional Access policies. Workflows use Power Automate. Business Process Flows advance automatically. Most IT services and financial services teams running Microsoft stacks find this the path of least resistance.
The Dynamics 365 integration is included in both Cloop plans at no additional cost, no per-contact fees, no volume-based charges.
Your Dynamics 365, populated in 30 minutes.
30 minutes. Your Sandbox environment. Real Leads flowing in real time. You'll see exactly what lands in Dynamics 365, and how it routes through your Business Units, Assignment Rules, and Business Process Flows.