Workday to AD provisioning app: Attribute mapping and Scoping filter - new version provisioning UI issue

Question

Workday to AD provisioning app: Attribute mapping and Scoping filter - new version provisioning UI issue

VedaPraneetha Edala 5

Using the new version of provisioning user experience, the attribute mapping page is showing an error - “No attribute mappings found” with a warning that “At least one attribute must be configured for matching identities to enable saving". But I did have a default attribute mapping with a matching filter (employeeID) already available.
I tried restoring to default mapping, adding a second matching filter, but no luck so far. Similarly there was an issue updating the scoping filters as well using the new UI(was seeing this for Workday->AD provisioning app, no issues with WorkdayWriteback mappings).
However, when I logged back in today, I'm no longer see this issue (neither the issue nor the new UI).
I'm assuming it could be an issue/bug to be fixed with the new provisioning UI. Is this something in preview and rolled back due to the identified issues?

Rukmini 43,915 Reputation points Microsoft External Staff Moderator

2026-05-28T12:29:37.4166667+00:00

Hello @VedaPraneetha Edala

Based on the details you shared, this is a known issue with the new provisioning UI experience and not related to your configuration.

The provisioning service is correctly returning the attribute mappings (as confirmed from the Graph API response in your HAR trace). However, the new Attribute Mapping page is not recognizing the Workday object type properly, due to which the UI fails to render the mappings and shows “No attribute mappings found.” This is why you see the issue only in the new UI while the legacy experience continues to display mappings correctly.

There is no impact to provisioning behavior—your attribute mappings, matching rules, and scoping filters remain intact, and the sync engine continues to function as expected.

A fix has already been implemented to address this behavior so that Workday-based object types are correctly recognized and mappings are rendered properly in the new UI. This fix is currently being rolled out via service updates.

At this point, no action is required from your end. You can continue with the existing configuration. If you need to validate or update mappings in the interim, please use the legacy Attribute Mapping experience, which works as expected.

Since you mentioned the issue is no longer reproducible and the UI has reverted, this aligns with service-side changes already applied in your tenant.

Please let us know if you encounter the issue again or observe any impact beyond the UI.
Rukmini 43,915 Reputation points Microsoft External Staff Moderator

2026-06-01T17:24:00.6433333+00:00

Hello @VedaPraneetha Edala

Following up to see if the above provided information was helpful. If you have any further queries do let us know.

1 answer

Your answer

Rukmini 43,915 Reputation points Microsoft External Staff Moderator

2026-05-28T12:29:37.4166667+00:00

Hello @VedaPraneetha Edala

Based on the details you shared, this is a known issue with the new provisioning UI experience and not related to your configuration.

The provisioning service is correctly returning the attribute mappings (as confirmed from the Graph API response in your HAR trace). However, the new Attribute Mapping page is not recognizing the Workday object type properly, due to which the UI fails to render the mappings and shows “No attribute mappings found.” This is why you see the issue only in the new UI while the legacy experience continues to display mappings correctly.

There is no impact to provisioning behavior—your attribute mappings, matching rules, and scoping filters remain intact, and the sync engine continues to function as expected.

A fix has already been implemented to address this behavior so that Workday-based object types are correctly recognized and mappings are rendered properly in the new UI. This fix is currently being rolled out via service updates.

At this point, no action is required from your end. You can continue with the existing configuration. If you need to validate or update mappings in the interim, please use the legacy Attribute Mapping experience, which works as expected.

Since you mentioned the issue is no longer reproducible and the UI has reverted, this aligns with service-side changes already applied in your tenant.

Please let us know if you encounter the issue again or observe any impact beyond the UI.
Rukmini 43,915 Reputation points Microsoft External Staff Moderator

2026-06-01T17:24:00.6433333+00:00

Hello @VedaPraneetha Edala

Following up to see if the above provided information was helpful. If you have any further queries do let us know.

Answer 1

The behavior described is not documented as a known or expected change in the provisioning experience, nor is there any documented note that the Workday→AD provisioning UI for attribute mappings and scoping filters is in preview or has been rolled back.

Current guidance for Workday→AD provisioning focuses on:

Using the Attribute mappings section to configure mapping type, source attribute, default value, and target attribute, and to define matching rules (for example, using employeeId).
Using Source Object Scope with scoping filters and on-demand provisioning to test mappings with a small set of users before broad rollout.
Restoring default mappings via Restore default mappings, which resets mappings and scoping filters to the gallery defaults and forces a resynchronization, with the recommendation to set Provisioning status to Off before doing so.

There is also a general set of known issues for provisioning (for example, missing schema extensions in the source attribute dropdown, unsupported scoping filters, and null attributes not being provisioned), but none of these match the transient “No attribute mappings found” error or indicate that the new UI is preview-only or has been rolled back.

Given that the issue disappeared and the new UI is no longer visible, this aligns more with a transient service-side problem or an internal rollout/flight being adjusted, rather than a documented, customer-facing preview feature with published rollback notes.

For ongoing configuration work:

Continue to validate Workday→AD mappings using scoping filters and on-demand provisioning as recommended.
If similar UI issues reappear (e.g., mappings not loading, errors about missing matching attributes), capture timestamps and screenshots and open a support ticket so that the product team can correlate with any backend changes.
Avoid using unsupported attributes in scoping filters (such as userType, manager, or date-type attributes) and be aware that null attributes are skipped during provisioning.

References: