Give your HR and IT teams more reasons to cheer with improved integration between Workday & Azure AD

This post has been republished via RSS; it originally appeared at: Azure Active Directory Identity Blog articles.

Howdy folks,


Last year we added inbound user provisioning from Workday to Azure AD, and customers like ASOS and Pernod Ricard are already using it to automate their HR and IT processes. Recently, we announced a strategic partnership with Workday that will bring more integrations for our joint customers. Today, we’d like to highlight three enhancements we’ve recently made in the Azure AD Workday integration.


Specify the version of Workday Web Services API you want Azure AD to use


Workday updates their APIs periodically, and customers want the ability to pick the API version that best meet their business needs. To keep up with the new features delivered by Workday, you can now specify the Workday API version when you setup Workday provisioning in Azure AD.



Outbound provisioning of phone numbers, from Azure AD to Workday


Once a user is provisioned in Azure AD from Workday, organizations normally manage phone numbers in Azure AD. You can now flow this information from Azure AD back to Workday by configuring attribute writeback. This writeback capability is also available for email and username attributes.


Disable Azure AD account when an employment offer is withdrawn


As part of the Workday Inbound provisioning, an Azure AD account is created as soon as the Workday New Hire business process completes. You can now configure the Azure AD user provisioning to handle offer rescind scenarios using a new flag in Workday called wd:Hire_Rescinded. This will cause the user account in Azure AD to be automatically disabled if an employment offer is rescinded, improving the security posture of your environment.


To learn more about these changes, check out our documentation on this topic. We are continuing to make additional enhancements in the Azure AD integration with Workday and we will keep you updated on our progress.


As always, we’d love to hear any feedback or suggestions you may have. Please let us know what you think in the comments below or on the Azure AD feedback forum.


Best regards, 

Alex Simons (Twitter: @Alex_A_Simons)

Corporate Vice President of Program Management

Microsoft Identity Division


REMEMBER: these articles are REPUBLISHED. Your best bet to get a reply is to follow the link at the top of the post to the ORIGINAL post! BUT you're more than welcome to start discussions here:

This site uses Akismet to reduce spam. Learn how your comment data is processed.