Real-time
Two-way sync
Changes in Ceridian Dayforce or Microsoft 365 instantly reflect in both systems. No stale data, no manual imports.
Human resources ⇄ Business productivity
Ceridian Dayforce to Microsoft 365 integration — real-time, two-way sync
Keep Ceridian Dayforce and Microsoft 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.
- SOC 2 and 6 other compliance frameworks
- POC with real engineers in minutes
Adopted by fast-scaling companies moving mission-critical data in real time
Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Ceridian Dayforce and Microsoft 365
Keep the people, teams, and status that Microsoft 365 and Ceridian Dayforce share aligned in real time, so a hire, role change, or departure recorded in one reaches the other within seconds.
Each tool in Microsoft 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. Ceridian Dayforce 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 SharePoint Sites & Lists, Teams, Planner & To Do Tasks, Users in Microsoft 365 with Employee Schedules, Org Units, Departments, Jobs & Positions, Time Away From Work & Balances, Employee (HR / Person Details) in Ceridian Dayforce bi-directionally and in real time. A person added, moved, or offboarded in Ceridian Dayforce creates or updates the matching user in Microsoft 365 within seconds, with field-level mapping and conflict resolution in place of spreadsheets and one-off account changes. Where Microsoft 365 captures details of its own, such as a corrected contact or a login identity, those can flow back to Ceridian Dayforce 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.
Common use cases
- 01 Archive mail and file metadata into a warehouse for compliance and activity analytics.
- 02 Keep CRM contacts and Microsoft 365 contacts aligned in both directions.
- 03 Sync time data by posting raw clock entries from a third-party scheduling tool into Dayforce, or pulling Employee Punches and Schedules into a workforce-analytics database.
- 04 Two-way sync of Employee and Work Assignment data (position, department, location, org unit) into Postgres so provisioning, internal apps, and analytics read current worker and org data in SQL while HR keeps editing in Dayforce.
Common sync patterns
Where Microsoft 365 routes or assigns work by person: assignments follow the org
When someone changes teams or managers in Ceridian Dayforce, the queues, ownership, or approvals in Microsoft 365 update to match, so work reaches whoever holds the role now.
Onboarding: access ready on day one
A new hire recorded in Ceridian Dayforce creates the matching user in Microsoft 365 with the right team and manager already set, so people can start working without waiting on a provisioning ticket.
Offboarding: no standing access after a departure
When someone is marked as leaving in Ceridian Dayforce, the matching account in Microsoft 365 is deactivated or flagged, so departures do not leave open access behind.
What you can sync between Ceridian Dayforce and Microsoft 365
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.
| Ceridian Dayforce objects | Microsoft 365 objects | How this pairing syncs | |
|---|---|---|---|
| Employment Status Effective-dated employment status and type (active, leave, terminated) that drives active/terminated state for downstream provisioning; read, and writable as new dated status records. | Teams Team and membership data provisioned from upstream systems. | Employment Status is specific to Ceridian Dayforce and Teams to Microsoft 365 — each maps to any object or custom field on the other side. | |
| Work Assignments Effective-dated position, department, location, and org-unit assignment; the most-synced record for org charts, provisioning, and analytics. Read and updatable via PATCH. | Planner & To Do Tasks Task items synced with project and work-management tools. | Work Assignments is specific to Ceridian Dayforce and Planner & To Do Tasks to Microsoft 365 — each maps to any object or custom field on the other side. | |
| Compensation Summary & Pay Adjustments Compensation Summary returns pay rate and frequency for reporting; Employee Pay Adjustments are written as effective-dated records via PATCH to post pay changes back to Dayforce. | Users Entra ID user accounts synced with HR and identity systems. | Compensation Summary & Pay Adjustments is specific to Ceridian Dayforce and Users to Microsoft 365 — each maps to any object or custom field on the other side. | |
| Employee Punches & Raw Clock Entries Time-and-attendance punches; raw clock entries are added with POST and punches removed with DELETE, so time data flows both ways between Dayforce and scheduling or workforce tools. | Groups Microsoft 365 and security groups kept aligned with org structure and access rules. | Employee Punches & Raw Clock Entries is specific to Ceridian Dayforce and Groups to Microsoft 365 — each maps to any object or custom field on the other side. | |
| Employee Schedules Shift and schedule assignments; created and updated through POST and PATCH schedule endpoints and paged with pageSize, used to push schedules from a WFM tool or pull them for analytics. | Mail Messages Exchange Online messages read for logging, archiving, or activity capture. | Employee Schedules is specific to Ceridian Dayforce and Mail Messages to Microsoft 365 — each maps to any object or custom field on the other side. | |
| Org Units, Departments, Jobs & Positions Configuration reference data; POST creates org units and departments and PATCH updates job, position, department, and org-unit data. Used to resolve and validate XRefCodes when mapping employee writes. | Calendar Events Events synced with scheduling tools and CRMs for meeting visibility. | Org Units, Departments, Jobs & Positions is specific to Ceridian Dayforce and Calendar Events to Microsoft 365 — each maps to any object or custom field on the other side. |
How changes propagate between Ceridian Dayforce and Microsoft 365
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.
Ceridian Dayforce Microsoft 365 Sub-second propagation
DetectionCeridian Dayforce notifies Stacksync of record changes through webhook events. No CDC stream.
DeliveryEach detected change is written to Microsoft 365 through its API, with automatic retries and rate-limit backoff.
Microsoft 365 Ceridian Dayforce Sub-second propagation
DetectionMicrosoft 365 notifies Stacksync of record changes through webhook events. Graph change notifications (webhooks) plus delta queries for incremental sync.
DeliveryEach detected change is written to Ceridian Dayforce through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Ceridian Dayforce: Dayforce does not publish numeric rate limits; thresholds vary by tenant and exceeding them returns HTTP 429, so large employee reads are paged (pageSize) and throttled with backoff. Employee list calls return XRefCodes only, so each employee needs a follow-up GET.
What ships with Ceridian Dayforce ⇄ Microsoft 365
Connect Ceridian Dayforce and Microsoft 365 for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Ceridian Dayforce–Microsoft 365 connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Ceridian Dayforce or Microsoft 365 data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
At scale
Event queues
Handle millions of events per minute without losing a single Ceridian Dayforce or Microsoft 365 record.
Observability
Monitoring
Track your Ceridian Dayforce ⇄ Microsoft 365 sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Ceridian Dayforce and Microsoft 365.
How the Ceridian Dayforce and Microsoft 365 connectors work
Ceridian Dayforce
- Integration surface
- REST API (Dayforce RESTful Web Services, v1/v2), JSON payloads
- Authentication
- HTTP Basic authentication with a dedicated Web Services user plus the client namespace (Company ID), or an OAuth 2.0 access token from the Dayforce identity endpoint (POST dfid.dayforcehcm.com/connect/token, client_id Dayforce.HCMAnywhere.Client). Token-based auth is recommended, and the Web Services role with the Read Data subfeature must be enabled on the account.
- Change detection
- No CDC stream. Broad change detection uses delta polling on GET Employees with filterUpdatedStartDate/filterUpdatedEndDate and filterUpdatedEntities to pull only records changed in a window. Dayforce also has native Event Notifications (the Notification Publisher) for lifecycle events — hire, rehire, terminate, and workflow validation — delivered by push to a receiver service or by querying unacknowledged notifications; the publisher runs roughly hourly and each notification must be acknowledged.
- Capabilities
- read · write · webhooks
- Rate limits
- Dayforce does not publish numeric rate limits; thresholds vary by tenant and exceeding them returns HTTP 429, so large employee reads are paged (pageSize) and throttled with backoff. Employee list calls return XRefCodes only, so each employee needs a follow-up GET.
Microsoft 365
- Integration surface
- REST API (Microsoft Graph)
- Authentication
- OAuth 2.0 via Microsoft Entra ID, with delegated or application permissions
- Change detection
- Graph change notifications (webhooks) plus delta queries for incremental sync
- Capabilities
- read · write · webhooks
How it works
How to connect Ceridian Dayforce to Microsoft 365 — three steps, no code
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.
- 01
Connect your apps
Authenticate Ceridian Dayforce and Microsoft 365 with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Ceridian Dayforce
connected
Microsoft 365
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Ceridian Dayforce and Microsoft 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.
objects · Ceridian Dayforce ⇄ Microsoft 365Customers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Ceridian Dayforce Microsoft 365Company company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Ceridian Dayforce and Microsoft 365 integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Ceridian Dayforce and Microsoft 365: authenticate both systems, choose the objects to sync (such as Ceridian Dayforce's Employment Status and Work Assignments), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Change detection on Ceridian Dayforce: No CDC stream. Broad change detection uses delta polling on GET Employees with filterUpdatedStartDate/filterUpdatedEndDate and filterUpdatedEntities to pull only records changed in a window. Dayforce also has native Event Notifications (the Notification Publisher) for lifecycle events — hire, rehire, terminate, and workflow validation — delivered by push to a receiver service or by querying unacknowledged notifications; the publisher runs roughly hourly and each notification must be acknowledged. On Microsoft 365: Graph change notifications (webhooks) plus delta queries for incremental sync. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Microsoft 365 side: SharePoint Sites & Lists, Teams, Planner & To Do Tasks, Users, plus custom fields where Microsoft 365 exposes them. On the Ceridian Dayforce side: Employee Schedules, Org Units, Departments, Jobs & Positions, Time Away From Work & Balances, Employee (HR / Person Details). 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.
-
Common patterns for Ceridian Dayforce and Microsoft 365: Where Microsoft 365 routes or assigns work by person: assignments follow the org; Onboarding: access ready on day one; Offboarding: no standing access after a departure. When someone changes teams or managers in Ceridian Dayforce, the queues, ownership, or approvals in Microsoft 365 update to match, so work reaches whoever holds the role now.
-
Ceridian Dayforce: REST API (Dayforce RESTful Web Services, v1/v2), JSON payloads. Authentication: HTTP Basic authentication with a dedicated Web Services user plus the client namespace (Company ID), or an OAuth 2.0 access token from the Dayforce identity endpoint (POST dfid.dayforcehcm.com/connect/token, client_id Dayforce.HCMAnywhere.Client). Token-based auth is recommended, and the Web Services role with the Read Data subfeature must be enabled on the account. Microsoft 365: REST API (Microsoft Graph). Authentication: OAuth 2.0 via Microsoft Entra ID, with delegated or application permissions. Stacksync manages authentication, retries, and rate limits on both sides.
SECURITY
Security teams trust Stacksync
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.
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS
SSO & SCIM
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Alerts
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Secure connection options
Securely connects to your systems with:
Related integrations
Every pair below is a real-time, two-way sync. Search all 455 integrations available for Ceridian Dayforce and Microsoft 365.
Popular · 8 of 455
-
Ceridian Dayforce ⇄ Quip -
Ceridian Dayforce ⇄ Smartsheet -
Ceridian Dayforce ⇄ Sysaid -
Ceridian Dayforce ⇄ Wrike -
Microsoft 365 ⇄ Lever -
Microsoft 365 ⇄ Namely -
Microsoft 365 ⇄ Paylocity -
Microsoft 365 ⇄ Ukg Ready
No integrations match .
