Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Important
This feature is for public preview customers only. Features in preview might not be complete and could undergo changes before becoming available in the broader release.
You can import organizational data into Microsoft 365 with the Workday connector, using the process described below.
Prerequisites
Before you can set up a connection between Workday and Microsoft 365, you'll need the following information about your Workday environment from your Workday admin:
- Workday web services URL
- Token URL
- Username
- ClientID
- Complete steps within Workday described in later section
Steps
1. Set up your Workday connection
Applies to: Microsoft 365 Global Administrator
Start the import from the Select connection type page on the Organizational Data in Microsoft 365 page (Home > Setup > Migration and imports > Organizational Data in Microsoft 365 > Select connection type). Under Workday connector, select Start Workday setup.
Select Get started (if this is the first time you're importing data), or New import (if you've already imported data).
On the Select connection type page, select Start Workday setup.
Under Download your Workday certificate, select Download certificate. A x509 certificate file will download called "publicKey.pem." Open the file in a text editor and copy its contents. Share this with the Workday admin.
Read the acknowledgment note and select Next.
Under Set up Workday connection:
Enter a name for your connection.
Contact your Workday admin to complete the steps in Workday described below.
Enter the Workday Web services URL, Token URL, and ClientID provided by the Workday admin.
For username, enter the name of the ISU created by the Workday admin.
Select how frequently you want Workday to send data to Microsoft 365: weekly or monthly.
Confirm you understand that the data you upload here might be processed by Viva and Microsoft 365, as well as non-Microsoft services that you've granted access to through Microsoft Graph, and select Next.
Review your connection details, then select Confirm.
Note
If you set up periodic exports, your data will be validated for Viva and Microsoft 365 services requirements. Validation takes a few hours; however, it can take up to three days for your complete data upload to be available in the profile store. You can check the validation status on the Organizational data page in the Microsoft 365 admin center. When validation is complete, a message will say your data is in use and managed by Viva and Microsoft 365.
2. Steps within Workday
Applies to: Workday admin
Open Workday. Search for "Create Integration System User" and select it. This is a system user not associated with a real person.
Under Create Integration System User, fill out each field, then select OK.
Create a security group. In Workday, search for "Create Security Group" and select it.
Select Integration System Security Group (Unconstrained).
Add the Integration System User to this group.
Search for "Maintain security group" and select Maintain Permissions for Security Group.
Next to Operation, select Maintain. Next to Source Security Group, select your created security group.
Select the "+" icon to add a new Domain Security Policy Permission.
Leave the Selected checkbox selected.
Next to View/Modify Access, select Get Only.
For Domain Security Policy:
- Add Worker Data: Public Worker Reports
- Add Worker Data: Organization Information
- Add Person Data: Private Work Email Integration
- Add Person Data: Skills
- Add Worker Data: Current Staffing Information
Search for "Activate Pending Security Policy Changes" and select it.
Add a descriptive comment about the change and select OK.
Select Confirm, then select OK. You now have a new system user with the proper permissions they need to get worker data.
3. Register an API Client
Search for "Register API Client" and select it.
Fill out the following fields:
- Give the client an appropriate name, such as "VivaConnectorClient."
- For the client grant type, select Jwt Bearer Grant.
- For x509 certificate:
- Select Create x509 Public Key.
- Give the certificate an appropriate name, such as "VivaX509Certificate."
- Paste the contents of the publicKey.pem file shared by the Global admin from the earlier step.
- Select OK.
- Ensure this certificate is selected for the field x509 Certificate.
- For Integration System User, enter the user you created earlier.
- Leave the access token type as "Bearer."
- Under Scope (Functional Areas), search for and select "Staffing," "Contact Information," "Worker Profile," and "Skills."
- Leave Include Workday Owned Scope cleared.
- Select the default values for the remaining fields.
Select OK.
A few new fields should populate below Restricted to IP Ranges. Save the following information and share it with the Global admin to enter in the Microsoft 365 admin center:
"ClientID"
Your Workday Token URL, such as
https://wd3-impl-services1.workday.com/ccx/oauth2/contoso4/token.Your Workday web services URL, such as
https://wd3-impl-services1.workday.com/ccx/service/contoso4.Note
This isn't the same as the Workday REST API Endpoint. If you're not familiar with your Workday web services URL, you can create it by copying your Token Endpoint, replacing "oauth2" with "service," and removing "/token" from the end.
How Workday sends data to Microsoft 365
When you connect Workday to Microsoft 365, Workday sends over a set of predefined source columns. These columns are mapped to fields in Microsoft 365. You can't change these predefined fields.
Field mapping
The table below shows how Workday fields correspond to Microsoft 365 fields. Learn more about Microsoft 365 fields including data type and formatting requirements.
| Attribute | Workday field |
|---|---|
| Microsoft_PersonEmail | /wd:Worker/wd:Worker_Data/wd:Personal_Data/wd:Contact_Data/wd:Email_Address_Data/wd:Email_Address |
| Microsoft_ManagerEmail | /wd:Worker/wd:Worker_Data/wd:Employment_Data/wd:Worker_Job_Data/wd:Position_Data/wd:Manager_as_of_last_detected_manager_change_Reference/wd:ID[@wd:type="Employee_ID" or @wd:type=\"Contingent_Worker_ID"][1] |
| Microsoft_Organization (Department) | /wd:Worker/wd:Worker_Data/wd:Organization_Data/wd:Worker_Organization_Data[1]/wd:Organization_Data/wd:Organization_Name |
| Microsoft_Layer | No mapping from Workday |
| Microsoft_LevelDesignation | /wd:Worker/wd:Worker_Data/wd:Employment_Data/wd:Worker_Job_Data/wd:Position_Data/wd:Job_Profile_Summary_Data/wd:Management_Level_Reference/wd:ID[@wd:type="Management_Level_ID"] |
| Microsoft_JobDiscipline | /wd:Worker/wd:Worker_Data/wd:Employment_Data/wd:Worker_Job_Data/wd:Position_Data/wd:Job_Profile_Summary_Data/wd:Job_Family_Reference/wd:ID[@wd:type="Job_Family_ID"] |
| Microsoft_CompanyOfficeLocation | /wd:Worker/wd:Worker_Data/wd:Employment_Data/wd:Worker_Job_Data/wd:Position_Data/wd:Business_Site_Summary_Data/wd:Location_Reference/wd:ID[@wd:type="Location_ID"] |
| Microsoft_CompanyOfficeCountryOrRegion | /wd:Worker/wd:Worker_Data/wd:Employment_Data/wd:Worker_Job_Data/wd:Position_Data/wd:Business_Site_Summary_Data/wd:Address_Data/wd:Country_Reference/wd:ID[@wd:type="ISO_3166-1_Alpha-3_Code"] |
| Microsoft_CompanyPostOfficeBox | No mapping from Workday |
| Microsoft_CompanyOfficeStreet | /wd:Worker/wd:Worker_Data/wd:Employment_Data/wd:Worker_Job_Data/wd:Position_Data/wd:Business_Site_Summary_Data/wd:Address_Data/wd:Address_Line_Data |
| Microsoft_CompanyOfficeCity | /wd:Worker/wd:Worker_Data/wd:Employment_Data/wd:Worker_Job_Data/wd:Position_Data/wd:Business_Site_Summary_Data/wd:Address_Data/wd:Municipality |
| Microsoft_CompanyOfficeState | /wd:Worker/wd:Worker_Data/wd:Employment_Data/wd:Worker_Job_Data/wd:Position_Data/wd:Business_Site_Summary_Data/wd:Address_Data/wd:Country_Region_Descriptor |
| Microsoft_CompanyOfficePostalCode | /wd:Worker/wd:Worker_Data/wd:Employment_Data/wd:Worker_Job_Data/wd:Position_Data/wd:Business_Site_Summary_Data/wd:Address_Data/wd:Postal_Code |
| Microsoft_Company | /wd:Worker/wd:Worker_Data/wd:Organization_Data/wd:Worker_Organization_Data[1]/wd:Organization_Data/wd:Organization_Name |
| Microsoft_CompanyCode | No mapping from Workday |
| Microsoft_FirstName | /wd:Worker/wd:Worker_Data/wd:Personal_Data/wd:Name_Data/wd:Legal_Name_Data/wd:Name_Detail_Data/wd:First_Name |
| Microsoft_LastName | /wd:Worker/wd:Worker_Data/wd:Personal_Data/wd:Name_Data/wd:Legal_Name_Data/wd:Name_Detail_Data/wd:Last_Name |
| Microsoft_DisplayName | /wd:Worker/wd:Worker_Data/wd:Personal_Data/wd:Name_Data/wd:Preferred_Name_Data/wd:Name_Detail_Data/@wd:Formatted_Name |
| Microsoft_JobTitle | /wd:Worker/wd:Worker_Data/wd:Employment_Data/wd:Worker_Job_Data/wd:Position_Data/wd:Business_Title |
| Microsoft_SecondaryJobTitle | No mapping from Workday |
| Microsoft_UserSkillNames | /wd:Worker/wd:Worker_Data/wd:Skill_Data/wd:Worker_Skill_Item/wd:Skill_Data[@wd:Inactive="0"]/@wd:Name |
| Microsoft_EmploymentType | /wd:Worker/wd:Worker_Data/wd:Employment_Data/wd:Worker_Job_Data/wd:Position_Data/wd:Worker_Type_Reference/wd:ID[@wd:type="Employee_Type_ID" or @wd:type=\"Contingent_Worker_Type_ID"][1] |