AADSTS50076 - Using LCS Connector with MFA Enabled in Azure DevOps Pipelines

(1) Share

Report

Posted on by Jakob Becker

Hello everyone,

we have been using Azure DevOps pipelines for some time to automatically supply our D365FO customers with updates.
However, it seems that Microsoft has now enforced MFA for all our user accounts in the tenant, and there appears to be no option to disable this.
As a result, all our releases that attempt to access LCS using the Dynamics Lifecycle Services Connector are failing.

Unfortunately, there seems to be no solution available online for this issue yet.
Does anyone have an idea on how to continue using the LCS Connector with MFA enabled?

I have the same question (0)

All responses (3)

Answers (1)

Suggested answer

Mohamed Amine Mahmoudi 26,390 Super User 2025 Season 2 on at

Like (0)

Report

Hi,

hope the following helps

https://yetanotherdynamicsaxblog.blogspot.com/2019/01/connecting-azure-devops-with-lifecycle.html

Best regards,

Mohamed Amine Mahmoudi

Was this reply helpful? Yes No
Jakob Becker 60 on at

Like (1)

Report

Unfortunately, Mohamed's response is not helpful at all.
The blog post is the first thing that comes up when searching online for the problem.
The solution mentioned in the blog post suggests using a different account or disabling MFA for the account.
As I already mentioned in my initial question, that is not an option for us.

Was this reply helpful? Yes No
Verified answer

Anthony Blake 2,926 Super User 2025 Season 2 on at

Like (1)

Report

Its not supported, and I'm seeing the same question asked by multiple end users at the moment.

The official line is to create a dedicated account with minimum permissions, and put it in an MFA exclusions group.

See here: https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/dev-tools/pipeline-lcs-connection#prerequisites

Note

Dynamics Lifecycle Services doesn't support service-to-service authentication. Therefore, only regular user credentials (that is, a user name and password) can be used. Because the pipelines don't run interactively, multifactor authentication must not be set up for the account that you use. We recommend that you set up a separate user account that has limited access and strong credentials that can regularly be rotated for security purposes.

Was this reply helpful? Yes No