Skip to content
KiweelyKiweelyKiweely

Why Workday to Microsoft Entra Incremental Sync Misses Changes

After the first full sync, Microsoft Entra asks Workday for manual updates, effective-dated updates and terminations, and future-dated hires. A change that Workday does not put on the worker transaction log is invisible until a later full sync.

  • Checked against Workday on
  • Applies to Workday Extend
  • 6 min read
  • Published
  • By Kiweely
On this page

Microsoft Entra’s incremental Workday sync is a transaction-log query. It is not a fresh copy of every worker. When a value changes on a related object and Workday does not write that change to the worker’s transaction log, Entra keeps the old value until you run a full sync. Microsoft documents that gap, and it is the usual reason a location, a site, or a similar attribute “never arrived.”

The behavior below is Microsoft’s, from the Entra Workday integration reference and the HR provisioning troubleshooting page. The Workday sources in this guide are the objects those queries are about: worker IDs, supervisory organizations, the worker record, and the integration system user Entra uses.

Full sync and incremental sync

Microsoft’s reference describes two cycles: https://learn.microsoft.com/en-us/entra/identity/app-provisioning/workday-integration-reference

Full sync runs when you turn provisioning on and when you restart it from the Microsoft Entra admin center or with Graph. Entra calls Workday Get_Workers for effective-dated worker entries as of that run, applies your attribute mappings, and saves the start time as a watermark.

Incremental sync starts from that watermark (LastExecutionTimestamp) and sends three kinds of Get_Workers queries:

  • Manual updates between the last execution and the current one.
  • Effective-dated updates and terminations.
  • Future-dated hires.

If a future-dated hire comes back, Entra fetches that hire by Workday ID (WID) with the effective date set to the hire date and time. Microsoft’s note on the Active flag is easy to misread. On the future-dated record in Workday, Active is 0 until the hire date, when it becomes 1. The connector asks for the worker as of the hire date, so the profile it receives already has Active 1. That is how an account can be filled in before day one. To keep the account disabled until the start date, Microsoft says to use a DateDiff transformation. The early-account case is pre-hire windows.

The miss

Microsoft’s troubleshooting page states the incremental limitation directly: https://learn.microsoft.com/en-us/entra/identity/app-provisioning/hr-user-update-issues

During incremental sync, the provisioning app queries the Workday transaction log for changes to the primary Worker entity. Only changes that log tracks are processed. The example is LocalReference, mapped with an XPath under Business_Site_Summary_Data. That attribute belongs to the business site summary. Changing it in Workday does not show up on the worker transaction log. Incremental sync therefore returns the new value only when some other attribute on the primary Worker entity also changes in the same interval. Microsoft’s recommendation, when you see this often, is a weekly or monthly full sync.

A restart also forces a full sync, because a restart is one of the two times Microsoft says full sync runs. Restarting to pick up one missed site change also reprocesses the workers in scope. Microsoft’s inbound tutorial says to test mappings on a few users with on-demand provisioning, and to use a source-object scope filter, before you start the full population. The tutorial is https://learn.microsoft.com/en-us/entra/identity/saas-apps/workday-inbound-tutorial

What you are matching

Microsoft’s planning guide says the default matching attribute for Workday is WorkerID, mapped to Active Directory employeeID (and, in the cloud-only tutorial, typically to Employee ID in Microsoft Entra ID). Matching precedence stops at the first hit. Extension attributes extensionAttribute1 through extensionAttribute15 cannot be the matching attribute. Microsoft says the Graph filter does not support them, so a match on extensionAttribute3 fails for creates and updates. Use employee ID. https://learn.microsoft.com/en-us/entra/identity/app-provisioning/plan-cloud-hr-provision

Workday does not define a single “Worker ID” field in the ID setup page. Steps: Set Up Workday IDs gives you separate sequences for employees, contingent workers, and pre-hires, plus an optional universal ID that follows the person across those types. Entra’s WorkerID has to be populated with the sequence you intend to match, and that value has to already be on the directory account before the first full sync if you expect a link rather than a new account. The Okta version of this mix-up is employee ID versus universal ID.

Microsoft also documents contingent-worker conversion. Contractor and employee are different worker profiles. A future-dated conversion can be applied on the day it is entered, because future-dated hires are processed immediately, unless you add the filtering Microsoft describes in that same reference. During the initial full sync, inactive prior profiles can briefly flow to the directory account and are then overwritten by the active profile. Incremental sync, once the job is in steady state, uses the active profile.

Terminations and time zones

Microsoft says the Workday integration system user it uses always operates in Pacific Time. A termination effective at the end of the local day in a zone ahead of Pacific is fetched only after that instant has passed in Pacific, so the disable arrives late. The connector’s mitigation is a termination lookahead query of 24 hours, which surfaces StatusTerminationLastDayOfWork and StatusTerminationDate when the termination day begins in UTC. The setup page is https://learn.microsoft.com/en-us/entra/identity/app-provisioning/configure-workday-termination-lookahead . Confirm the lookahead on one worker with provisioning on demand before you restart the job for the incremental cycle.

That delay is an Entra query rule. It is independent of the transaction-log miss above. A last day of work can be late because of the time zone, or missing because a related attribute never hit the worker log. They have different fixes: lookahead, or a scheduled full sync.

The Workday records under those queries

Set Up Supervisory Organizations says the effective date controls when an organization is visible and when you can assign roles. A manager assignment or a site change that is effective next Monday is not visible as of today. Entra’s effective-dated query is what picks it up when the watermark reaches it. A business-site attribute that is not on the worker transaction log still waits for the full sync, even after the effective date has arrived.

Reference: Workers is Workday’s REST worker resource, secured by Worker Data: Public Worker Reports. The summary includes primarySupervisoryOrganization, businessTitle, and primaryWorkEmail. Microsoft’s connector uses Get_Workers, the SOAP operation named on the Entra reference page, not this REST resource. The REST resource is here so you can see which worker fields Workday treats as part of the worker, and which security domain a reader needs. A field Entra maps from a related object can be absent from both this summary and the transaction log.

Workday Configurable Security says to create one integration system user per integration system and to grant the domains that system needs. Entra’s connector uses an integration system user. An unconstrained user can read all workers. A user missing Worker Data domains produces a short feed and a provisioning run that looks idle. Compare a worker Entra skipped with what that user can open in Workday before you restart provisioning.

Where Roots fits

Kiweely Roots (coming next) includes Microsoft Entra ID with the identity systems it joins on day one and closes on the last. Directory feeds are fixed, tested, and turned back on, with a note to the owner. A missed incremental attribute is that kind of feed, once you have decided the full-sync schedule Microsoft recommends. Payroll, benefits, and tax stay behind an approval after a Sandbox proof. Register interest on the Roots page. Roots does not change Workday’s transaction log, and it does not turn a business-site edit into a worker transaction.

What to do when a worker is stale

One attribute is old and the job title updated.

That matches Microsoft’s transaction-log description. Schedule the weekly or monthly full sync Microsoft recommends, or restart provisioning if you are prepared for a full cycle. Confirm the stale attribute is not on the primary worker entity.

The account enabled a week before the start date.

The future-hire query returns Active 1 because it reads the worker as of the hire date. Add the DateDiff transformation Microsoft documents if the account should stay disabled until day one.

Matching created a second account after a conversion.

WorkerID changed with the new employee profile, or the directory account was linked to the contingent worker’s WID. Read Microsoft’s conversion section before you delete either account, and decide whether the employee ID or the universal ID is the value that should have been on the directory record from the start.

Sources checked

Let Workday check the work.

Kiweely writes WQL and builds orchestrations in your own tenant, and Workday, not Kiweely, says whether they passed.

Get the next guide in your inbox.

One email a month with new guides and one Extend tip. Nothing else.

We’ll email you once to confirm. Unsubscribe in one click from any issue.