Two-way sync
Changes in D2l Brightspace or Microsoft Dynamics 365 instantly reflect in both systems. No stale data, no manual imports.
Keep D2l Brightspace and Microsoft Dynamics 365 in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Each tool in Microsoft Dynamics 365 keeps its own list of who can use it: users, members, or agents, along with the team they sit on and whether they are still active. D2l Brightspace is the authoritative record of the same people as employees, with their department, manager, and employment status. When those two are connected only by manual account admin or a periodic export, the work tools drift: new hires wait days for access, team and manager changes never catch up, and people who have left keep standing accounts.
Stacksync syncs Contacts, Leads, Opportunities, Cases (Incidents) in Microsoft Dynamics 365 with Assignments (Dropbox), Groups and Sections, Users, Enrollments in D2l Brightspace bi-directionally and in real time. A person added, moved, or offboarded in D2l Brightspace creates or updates the matching user in Microsoft Dynamics 365 within seconds, with field-level mapping and conflict resolution in place of spreadsheets and one-off account changes. Where Microsoft Dynamics 365 captures details of its own, such as a corrected contact or a login identity, those can flow back to D2l Brightspace in whichever direction you configure.
Because the sync is field-level, each system keeps its own extras; only the shared facts, who a person is, which team they belong to, and whether their access should be on, are held in agreement.
When someone changes teams or managers in D2l Brightspace, the queues, ownership, or approvals in Microsoft Dynamics 365 update to match, so work reaches whoever holds the role now.
A new hire recorded in D2l Brightspace creates the matching user in Microsoft Dynamics 365 with the right team and manager already set, so people can start working without waiting on a provisioning ticket.
When someone is marked as leaving in D2l Brightspace, the matching account in Microsoft Dynamics 365 is deactivated or flagged, so departures do not leave open access behind.
Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.
| D2l Brightspace objects | Microsoft Dynamics 365 objects | How this pairing syncs | |
|---|---|---|---|
| Enrollments Links between Users and Org Units; enroll/unenroll and batch-enrollment routes let rosters be written from an upstream system and read back for reporting. | Cases (Incidents) Support records shared with ticketing tools and product databases. | Enrollments is specific to D2l Brightspace and Cases (Incidents) to Microsoft Dynamics 365 — each maps to any object or custom field on the other side. | |
| Org Units The org structure — course offerings, sections, departments, and semesters; read for hierarchy and created/updated to provision courses from a database. | Quotes, Orders & Invoices Transaction documents reconciled with the ERP or billing source of truth. | Org Units is specific to D2l Brightspace and Quotes, Orders & Invoices to Microsoft Dynamics 365 — each maps to any object or custom field on the other side. | |
| Grades Grade objects, categories, schemes, and per-user grade values in the Learning Environment (le) component; values can be read out and written back onto the gradebook. | Products Catalog records aligned with ERP item masters. | Grades is specific to D2l Brightspace and Products to Microsoft Dynamics 365 — each maps to any object or custom field on the other side. | |
| Content (Modules, Topics, and User Progress) Course content structure plus per-user completion; progress is read into a warehouse and topics can be created and updated via the API. | Activities Emails, calls, and tasks captured for engagement analytics. | Content (Modules, Topics, and User Progress) is specific to D2l Brightspace and Activities to Microsoft Dynamics 365 — each maps to any object or custom field on the other side. | |
| Quizzes Quiz objects and per-user attempts and results; attempt data is read out for engagement and completion analytics. | Custom Tables Dataverse tables that carry business-specific entities through the same API surface. | Quizzes is specific to D2l Brightspace and Custom Tables to Microsoft Dynamics 365 — each maps to any object or custom field on the other side. | |
| Assignments (Dropbox) Dropbox folders, submissions, and feedback; submission and evaluation data is read into reporting systems and feedback can be written back. | Accounts Company records synced bi-directionally with ERPs, databases, and billing systems. | Assignments (Dropbox) is specific to D2l Brightspace and Accounts to Microsoft Dynamics 365 — each maps to any object or custom field on the other side. |
Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.
DetectionD2l Brightspace notifies Stacksync of record changes through webhook events. Polling Valence endpoints with date/bookmark filters, differential Brightspace Data Sets (BDS) bulk exports for changed rows via the Data Hub, and.
DeliveryEach detected change is written to Microsoft Dynamics 365 through its API, with automatic retries and rate-limit backoff.
DetectionMicrosoft Dynamics 365 pushes changes as they happen — webhook events backed by change data capture. Change data capture (CDC) via the Dynamics 365 Change Tracking feature.
DeliveryEach detected change is written to D2l Brightspace through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every D2l Brightspace–Microsoft Dynamics 365 connection.
Changes in D2l Brightspace or Microsoft Dynamics 365 instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever D2l Brightspace or Microsoft Dynamics 365 data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single D2l Brightspace or Microsoft Dynamics 365 record.
Track your D2l Brightspace ⇄ Microsoft Dynamics 365 sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between D2l Brightspace and Microsoft Dynamics 365.
Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.
Authenticate D2l Brightspace and Microsoft Dynamics 365 with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the D2l Brightspace and Microsoft Dynamics 365 objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between D2l Brightspace and Microsoft Dynamics 365: authenticate both systems, choose the objects to sync (such as D2l Brightspace's Enrollments and Org Units), map fields visually, and changes propagate both ways in milliseconds — no code required.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed D2l Brightspace and Microsoft Dynamics 365 connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom D2l Brightspace–Microsoft Dynamics 365 integration in-house.
Yes — Stacksync ships production-grade connectors for both D2l Brightspace and Microsoft Dynamics 365. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on D2l Brightspace: Polling Valence endpoints with date/bookmark filters, differential Brightspace Data Sets (BDS) bulk exports for changed rows via the Data Hub, and Brightspace Data Streams webhooks (xAPI activity events) for near-real-time signals. On Microsoft Dynamics 365: Change data capture (CDC) via the Dynamics 365 Change Tracking feature; standard entities have change tracking enabled by default, custom entities require enabling "Track Changes" in Power Apps/Dataverse table properties. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Microsoft Dynamics 365 side: Contacts, Leads, Opportunities, Cases (Incidents), plus custom fields where Microsoft Dynamics 365 exposes them. On the D2l Brightspace side: Assignments (Dropbox), Groups and Sections, Users, Enrollments. Stacksync auto-detects both schemas and converts types between the two systems.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 410 integrations available for D2l Brightspace and Microsoft Dynamics 365.