Microsoft Entra ID + Workday integration
Set up Microsoft Entra ID as the identity provider for Workday via SAML — where Entra ID handles authentication for Workday users.
- Entra ID Application Administrator
- Workday Security Administrator
1. Create a new SAML 2.0 application in Entra ID
In the Entra ID admin console, create a new SAML 2.0 application. Choose "Web Application" type. Note the placeholders for ACS URL + Entity ID — you'll get these from Workday in step 3.
2. Get the SAML metadata URL from Entra ID
Entra ID exposes the IdP metadata at a stable URL. Copy this URL — you'll paste it into Workday's SSO configuration. Alternatively, download the metadata XML if Workday doesn't support URL-based metadata.
3. Configure SSO in Workday
In Workday's admin → security → SSO settings, paste the Entra ID metadata URL (or upload the XML). Workday will display the ACS URL + Entity ID it expects — copy these.
4. Return to Entra ID + complete the SAML app config
Paste Workday's ACS URL into the Entra ID app's Single Sign-On URL field. Paste the Entity ID into the Audience URI field. Set the NameID format to EmailAddress (or persistent if Workday expects that).
5. Configure attribute mapping
Map the attributes the SP expects (see the Attribute Mapping section below). At minimum, email is required. Most apps also expect firstName + lastName.
6. Assign users + groups
In Entra ID, assign the SAML app to users or groups that should have access. Test with a pilot group before broad rollout.
7. Test end-to-end
Sign in to Workday via the IdP-initiated link (from Entra ID dashboard) AND via SP-initiated (direct Workday login URL). Both should work. Check the SAML Tracer browser extension or SAML decoder to inspect the assertion if anything fails.
What flows from where.
| Source (Microsoft Entra ID) | Target (Workday) | Note |
|---|---|---|
| user.mail | NameID | — |
| user.employeeId | Workday Account | — |
- Clock skew: Entra ID and Workday clocks must be within ~5 minutes. NTP-sync both. SAML's NotBefore + NotOnOrAfter are strict.
- NameID format mismatches are the most common failure. Workday typically wants EmailAddress; Entra ID defaults vary. Mismatch → cryptic "invalid assertion" errors.
- Just-in-time (JIT) provisioning vs SCIM: many apps support both. SAML JIT creates the user on first SSO; SCIM creates them ahead of time. Pick one — both can cause attribute drift.
- Audience restriction: Workday's expected Audience URI must match exactly what the IdP sends. Trailing slashes + protocol (http vs https) matter.
- Signed Response vs signed Assertion: many SPs require the Assertion to be signed (not just the Response envelope). Check the SP's docs.
- Workday → Entra ID provisioning (HR-driven JML) is a separate integration from SAML SSO. Don't confuse the two — they're both useful, both common, both different.
- Workday's session timeout is stricter than Entra ID's — users may need to re-authenticate within Workday more often than other apps.
- IdP-initiated SSO works (sign in from the IdP dashboard)
- SP-initiated SSO works (visit Workday directly + get redirected to IdP)
- User attributes flow through correctly (email, name, groups)
- Logout (single logout if supported) works as expected
- Step-up MFA fires when policy requires it
- Unauthorized users (not assigned to the app) get a clean denied message
- Capture a successful SAML response and inspect it (use the SAML decoder tool)
For the latest vendor-side configuration changes, refer to:
Entra ID + Workday tutorial →