Microsoft Entra Workload ID

Configure Workload Identity Sap Successfactors Provisioning

20 August 2026Doc update+1 / −4 lines

In brief

The page no longer lists SAP’s November 20, 2026 basic-authentication deprecation date and removes the note describing current and planned workload identity support scenarios.

What Entra admins need to know

Review the updated guidance when planning SuccessFactors authentication and provisioning configurations.

This editorial summary was generated by AI from the documentation changes. Verify important details in the full Microsoft Learn article.

Documentation change

View full page diff

View on Microsoft Learn

The comparison below shows only the changed extract. Use the full-page view for complete context.

This change helps customers transition to a more secure authentication model in preparation for SAP's plan to deprecate basic authentication for SuccessFactors APIs.

Applies to the following provisioning integrations:

SuccessFactors to Microsoft Entra ID user provisioning
SuccessFactors Writeback

Note
Workload identity authentication is currently enabled for the SuccessFactors Writeback and SuccessFactors to Microsoft Entra ID user provisioning scenarios. Support for the SuccessFactors to on-premises Active Directory user provisioning scenario will be enabled soon.

Why workload identity-based authentication

Workload identity-based authentication strengthens your security posture by removing static credentials and replacing them with tokens that expire in minutes rather than never.
Why workload identity-based authentication
Workload identity-based authentication strengthens your security posture by removing static credentials and replacing them with tokens that expire in minutes rather than never.

@@ -17,7 +17,7 @@ This article shows you how to configure workload identity-based authentication f > [!NOTE] > We make public previews available to our customers under the terms applicable to previews. These terms are outlined in the overall Microsoft product terms for [online services](https://www.microsoft.com/licensing/terms/product/ForOnlineServices/all). -This change helps customers transition to a more secure authentication model in preparation for SAP's plan to [deprecate basic authentication for SuccessFactors APIs by November 20, 2026](https://help.sap.com/docs/successfactors-release-information/8e0d540f96474717bbf18df51e54e522/fcc05a902b4140e585d968c2fe4a96bc.html).+This change helps customers transition to a more secure authentication model in preparation for SAP's plan to [deprecate basic authentication for SuccessFactors APIs](https://help.sap.com/docs/successfactors-release-information/8e0d540f96474717bbf18df51e54e522/fcc05a902b4140e585d968c2fe4a96bc.html).  Applies to the following provisioning integrations: @@ -25,9 +25,6 @@ Applies to the following provisioning integrations: - SuccessFactors to Microsoft Entra ID user provisioning - SuccessFactors Writeback -> [!NOTE]-> Workload identity authentication is currently enabled for the **SuccessFactors Writeback** and **SuccessFactors to Microsoft Entra ID user provisioning** scenarios. Support for the **SuccessFactors to on-premises Active Directory user provisioning** scenario will be enabled soon.- ## Why workload identity-based authentication  Workload identity-based authentication strengthens your security posture by removing static credentials and replacing them with tokens that expire in minutes rather than never.