Workday to AD Provisioning – Future Hire Employees Skipped (“NotEffectivelyEntitled” / “IsActive: False”)

We have implemented the Workday to Active Directory Provisioning Agent as described in the following Microsoft documentation:
https://learn.microsoft.com/en-us/answers/questions/959791/future-hire-date-employees-provisioning-from-workd

The integration is generally working, but future-dated hires are being skipped during provisioning.

Below is the relevant part of the provisioning log:

Result: Skipped

Description: The Worker 'xxxxx' will be skipped due to the following reasons:

1. This object is not active in the source system.

SkipReason: NotEffectivelyEntitled

IsActive: False

Assigned to the application: True

IsInProvisioningScope: True

According to the Microsoft documentation, the connector should handle future-dated hires by using the As_Of_Effective_Date parameter to query Workday with the worker’s hire date:
https://learn.microsoft.com/en-us/entra/identity/app-provisioning/workday-integration-reference#query-for-future-dated-hires

When I manually run the same Workday API query from Workday Studio with As_Of_Effective_Date set to the employee’s start date, the worker is returned as active — so Workday is responding correctly.

However, when the provisioning job runs in Azure AD, those same users are skipped with IsActive=False.

Questions:

Does the Workday to AD Provisioning App currently support provisioning future-dated hires out-of-the-box, or does it only handle active employees?

How can I verify if the As_Of_Effective_Date parameter is actually being passed from the provisioning agent to Workday?

1. Is there any specific configuration (e.g., in the Provisioning Agent or Workday) required to enable future hire processing?