Error creating new file asset: 'Invalid OAuth token was presented.'

(1) Share

Report

Posted on by SM-17050844-0

202

Hi guys,

Since last Friday 5/7/2024 our pipeline is failing to upload into asset library.

Error - Error creating new file asset: 'Invalid OAuth token was presented.'

I've changed the user password, renewed the token(was not expired anyway), but still we are facing this issue out of nowhere.

The account does NOT have MFA enabled.

Interesting part is that we are using the same account for fetching environment metadata, but it is failing as well.

Anyone had similar issue recently ?

Thanks.

I have the same question (2)

All responses (10)

Answers (1)

Anthony Blake 3,061 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi,

I've just checked an upload pipeline in case, and the asset ~~uploaded fine~~ had the same issue. Could you hit edit on your connection in DevOps and share the settings? Obviously redact anything sensitive.

Thanks

Was this reply helpful? Yes No
SM-17050844-0 202 on at

Like (1)

Report
Copy link

Link copied!

Hey Anthony,

Editted.
Could be an issue from Microsoft, but this Issue id is not in LCS.

Thanks for reaching out.

Nothing out of the ordinary there.

I changed the password once this was changed in ENTRA ID.

The rest of the setup is the same.

BTW.

What do you have under authentication endpoint and lcs endpoint ?

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

Like (0)

Report
Copy link

Link copied!

Wow, so ignore my earlier post - my pipeline just failed to upload with the exact same issue, I jumped the gun reporting it as successful.

Looks like something changed or is broken their end.

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

Like (0)

Report
Copy link

Link copied!

Looks like a regional issue, lots of reports on Yammer for Europe today:

Viva Engage : Dynamics 365 and Power Platform Preview Programs : View Conversation (yammer.com)

Was this reply helpful? Yes No
SM-17050844-0 202 on at

Like (1)

Report
Copy link

Link copied!

Yes,

I had a quick discussion with Microsoft on this.

It was supposed to be fixed last week but is not...

Chances are that we will wait at least by the end of the day.

Was this reply helpful? Yes No
Krzysztof.Jasek 4 on at

Like (0)

Report
Copy link

Link copied!

Hi ,

we got exactly the same error on our pipelines, when publishing package to asset library and also it started since last Friday 5/7/2024 afternoon.

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

Like (0)

Report
Copy link

Link copied!

Is anyone still getting this issue today or is it now resolved?

Was this reply helpful? Yes No
Verified answer

SM-17050844-0 202 on at

Like (1)

Report
Copy link

Link copied!

For us it is resolved.

Pasting the comments from Microsoft support below - exactly what i have expected...

. as far as the root cause of the issue it was due to a code regression, LCS API was failing to authenticate requests made to it with an Oauth token which uses the URL as the resource rather than the application Id.
Eg. "lcsapi.lcs.dynamics.com rather than ***************************

Generating oauth tokens this way is known to be done by the AzDO pipelines which attempt to call to LCSAPi and thus is causing them to fail with the error message “'Invalid OAuth token was presented” Code regression was known to be present in all public cloud regions of LCS. So, a lot of customers in different regions were impacted.

what has been done to fix it was Traffic manager changes have been made to direct traffic to working versions in all regions, GCC has been disabled in the problem region and the problem version has been disabled in other regions as well. Traffic manager changes have been made to direct traffic to working versions in all regions. Hotfix build has been deployed and was completed.
. as far as the root cause of the issue it was due to a code regression, LCS API was failing to authenticate requests made to it with an Oauth token which uses the URL as the resource rather than the application Id.
Eg. "lcsapi.lcs.dynamics.com rather than 913c6de4-2a4a-4a61-a9ce-945d2b2ce2e0")

Generating oauth tokens this way is known to be done by the AzDO pipelines which attempt to call to LCSAPi and thus is causing them to fail with the error message “'Invalid OAuth token was presented” Code regression was known to be present in all public cloud regions of LCS. So, a lot of customers in different regions were impacted.

what has been done to fix it was Traffic manager changes have been made to direct traffic to working versions in all regions, GCC has been disabled in the problem region and the problem version has been disabled in other regions as well. Traffic manager changes have been made to direct traffic to working versions in all regions. Hotfix build has been deployed and was completed.

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

Like (0)

Report
Copy link

Link copied!

Thanks, I will also retest

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

Like (0)

Report
Copy link

Link copied!

Retested - resolved for my project.

Was this reply helpful? Yes No