Teams is corrupting image-links on cards

Question

Teams is corrupting image-links on cards

Adriano 𝓟etrucci 0

I created a workflow, to show the cards on Teams.

Since 1 week no image is rendered anymore on this cards (also on my old cards).

To show the image on the card, I use a link, example: https://example.com/image.webp

MSTeams changed this link (up to 1 week ago) to:
https://ch-prod.asyncgw.teams.microsoft.com/urlp/v1/url/content?url=https%3a%2f%2fexample.com%2fimage.webp

Since a week, it seems that Microsoft added a version to this link and now the link is:

https://ch-prod.asyncgw.teams.microsoft.com/urlp/v1/url/content?url=https%3a%2f%2fexample.com%2fimage.webp&v=1

Why "&" and not "?" ????

How should a server be able to read a link like: https://example.com/image.webp&v=1 ?

Is there a way to solve it on the cards? I would like to have the images on the old messages too.

Thanks,

Adriano

0 comments

1 answer

Your answer

Answer 1

Dear @Adriano 𝓟etrucci,

I hope you’re having a good day.

Thank you for the detailed explanation.

Based on what you've described, I think your suspicion is reasonable. Since the issue started only about a week ago, affects both new and previously posted cards, and involves URLs being rewritten through the Teams asyncgw proxy service, this appears more likely to be related to a change in Teams' image handling than to a change in your workflow. Teams has long proxied image URLs through this service before rendering them.

Interestingly, there have been similar reports in the past where Teams modified image URLs by appending parameters such as &v=1, resulting in images no longer rendering correctly in Adaptive Cards. In those cases, Microsoft acknowledged the behavior as a bug and later released a fix.

For reference: Image of an Adaptive Card is not visible in the new Teams | Topedia Blog

(This link is shared by community members for your convenience. It points to a third-party site that is not managed or verified by Microsoft. We can’t guarantee the quality, safety, or suitability of any content or software found there. Please review carefully and make sure you understand any potential risks before using it. )

At this point, I would first confirm that:

The original image URL still opens correctly outside Teams.
The issue affects both old and newly generated cards.
The workflow and card payload haven't changed.

If all of those are true, I would consider opening a Microsoft support ticket, as the evidence would suggest a possible Teams-side regression rather than a problem with your workflow implementation.

It would also be helpful to know whether this affects only .webp images or other formats such as .png and .jpg as well.

Looking forward to hearing back from you with any updates or additional details.

Warm regards,

If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in the forum documentation to enable email notifications if you want to receive the related email notification for this thread.

Adriano 𝓟etrucci 0 Reputation points

2026-08-10T12:44:20.9966667+00:00

Hi Liora,
Thank you for the answer.

I modified the configuration of the server to change the request from image.webp&v=1 to image.webp?v=1 but it doesn't change, I still have the same problem.

Probably asyncgw will change this request "on the fly" with the correct link.

I was thinking about the cache, so I tried with the Desktop App, Browser and In-Private browser. The image is never loaded (not on the new generated cards and not on my old cards).

With the last tests:

it works on the Android App.

It doesn't matter if webp or png, the image is not loaded in MS Teams (Desktop app and browser)
Liora 775 Reputation points Independent Advisor

2026-08-11T11:20:58.08+00:00

Hi Adriano,

Thank you for the update. The Android result is particularly helpful.

Since the issue:

Affects both old and new cards,

Occurs in Teams Desktop, Teams Web, and InPrivate sessions,

Happens with both .webp and .png images,

Persists even after your server-side changes,

but the same images still render correctly in the Android Teams app, this makes it less likely that the image source or workflow is the root cause.

At this point, the evidence appears to point more toward a Teams Desktop/Web rendering or image proxy issue than a problem with your cards or server configuration.

Given the troubleshooting you've already completed, I would recommend opening a Microsoft support ticket and sharing these findings, as they provide a strong case for a possible Teams-side regression.

You can raise support ticket from Microsoft 365 Admin Center>Support>Help & Support.

For reference:  Get support | Microsoft Docs  

Thank you again for the detailed testing. It significantly narrows down the area of investigation.

Kind regards.