Finance | Project Operations, Human Resources, ...

Release pipeline LCS upload: Invalid OAuth token was presented

(2) Share

Report

Posted on by FODev

Release pipeline failing to upload LCS asset task

Log file - 2026-03-19T16:02:06.3283210Z MSAL Authentication against AAD authority https://login.microsoftonline.com/organizations
2026-03-19T16:02:06.8880083Z PowerShellGet Module exists
2026-03-19T16:02:48.7070146Z Required libraries loaded
2026-03-19T16:02:48.7470113Z Fetching token from application
2026-03-19T16:02:51.3809734Z Fetched Result
2026-03-19T16:02:51.3810070Z MSAL.Desktop.4.60.4.0.MsalClientException:
2026-03-19T16:02:51.3810388Z ErrorCode: parsing_wstrust_response_failed
2026-03-19T16:02:51.3810783Z Microsoft.Identity.Client.MsalClientException: There was an error parsing the WS-Trust response from the endpoint.
2026-03-19T16:02:51.3811253Z This may occur if there are issues with your ADFS configuration. See https://aka.ms/msal-net-iwa-troubleshooting for more details.
2026-03-19T16:02:51.3811695Z Enable logging to see more details. See https://aka.ms/msal-net-logging.
2026-03-19T16:02:51.3812097Z at Microsoft.Identity.Client.WsTrust.WsTrustWebRequestManager.<GetWsTrustResponseAsync>d__3.MoveNext()
2026-03-19T16:02:51.3812506Z --- End of stack trace from previous location where exception was thrown ---
2026-03-19T16:02:51.3812875Z at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
2026-03-19T16:02:51.3813299Z at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
2026-03-19T16:02:51.3813734Z at Microsoft.Identity.Client.WsTrust.CommonNonInteractiveHandler.<GetWsTrustResponseAsync>d__6.MoveNext()
2026-03-19T16:02:51.3814180Z --- End of stack trace from previous location where exception was thrown ---

All below points are configured correctly :-

(LCS Project is in Europe)

Categories:

Dynamics 365 Finance

I have the same question (0)

All responses (11)

Answers (0)

Sort by

André Arnaud de Cal... 305,946 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

Moved the question from the Dynamics 365 General to the Dynamics 365 Finance forum.

Was this reply helpful? Yes No
Suggested answer

Diego Mancassola 902 on at

Like
a
(1)

Report
Copy link

Link copied!

Hello, i remember well this error.

The user used to LCS connection must not have MFA.

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

Was this reply helpful? Yes No
FODev 12 on at

Like
a
(0)

Report
Copy link

Link copied!

MFA is already disabled , I am able to login LCS from that account using password only . Still same error

Was this reply helpful? Yes No
Suggested answer

Anton Venter 20,698 Super User 2026 Season 1 on at

Like
a
(1)

Report
Copy link

Link copied!

@FODev

The error message "Invalid OAuth token was presented" relates to the application registration used in the service connection to upload to LCS. Check and confirm that the Application client Id is correct and that it has permission on LCS as per the documentation.

Was this reply helpful? Yes No
FODev 12 on at

Like
a
(1)

Report
Copy link

Link copied!

Client id is correct and Also API is granted on the App registartion page also , Still same issue

Was this reply helpful? Yes No
TalkBull 35 on at

Like
a
(1)

Report
Copy link

Link copied!

@FODev Were you able to solve this?

I'm experiencing exactly the same. LCS project is in EU region, MFA disabled, app registration configured as per the MS docs, etc.

Was this reply helpful? Yes No
Anthony Blake 3,158 Super User 2026 Season 1 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @FODev

Are you using a traditional release pipeline? What do your tasks look like on the release stage, do you have a step to install MSAL like this:

What do the logs look like for the whole run, have the previous steps, e.g. instal MSAL, succeeded?

Thanks,

Anthony

Was this reply helpful? Yes No
Anthony Blake 3,158 Super User 2026 Season 1 on at

Like
a
(1)

Report
Copy link

Link copied!

The other suggestions I would make are:

It may sound obvious would be to replace your username and password in your service connection, validating any typos or spaces added to the password by copy/paste.

Check point 3 on your prerequisites in Azure portal. Did the admin definitely grant consent?

Was this reply helpful? Yes No
TalkBull 35 on at

Like
a
(2)

Report
Copy link

Link copied!

@Anthony Blake

I've granted admin consent and re-typed the password in DevOps but still the same error.

When trying to replicate using PowerShell, I managed to get a token successfully using Get-MsalToken (passing in the client Id, tenant Id, scope, and using -Interactive) and call the Invoke-D365LcsUpload manually, and this works successfully.

I read that the Install MSAL.PS step isn't required anymore in the newer task versions.

https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/dev-tools/pipeline-lcs-connection-update#update-existing-tasks

Was this reply helpful? Yes No
Diego Mancassola 902 on at

Like
a
(1)

Report
Copy link

Link copied!

Hello, have you enabled Allow public client flows?

In the Azure portal, select your app in App registrations, and then select Authentication.
In Advanced settings > Allow public client flows > Enable the following mobile and desktop flows, select Yes.

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

Was this reply helpful? Yes No