Adaptive Card images break after toggle or re-render in Microsoft Teams (blob URL invalidation)

[dtiwarATS]

We are experiencing an issue where images in Adaptive Cards break permanently in Microsoft Teams after any toggle or re-render event.

We are storing our images in Azure blob storage and can confirm that URL is accessible. On first load, all images display correctly. However, when a user interacts with the card (e.g., expands a ShowCard or toggles visibility), the images disappear and become broken. The problem occurs consistently across users.

When inspecting the Teams Web client, the image’s src appears as a blob URL such as:

blob:https://teams.microsoft.com/c091bb02-2399-487c-84a9-c3311aa265ad

Initially, this blob URL resolves correctly.
After any toggle or re-render inside Teams, the blob becomes invalid — the image disappears and cannot be reloaded.

If we copy this blob URL and paste it into a browser immediately, it shows the image once, but upon refresh it returns “file not found” — indicating that the blob reference is destroyed after Teams re-renders the Adaptive Card.

Key Observation

In the Teams web client, if we refresh the browser tab or reopen the conversation, the image reloads correctly (because Teams refetches the image from its original URL).
In the Teams desktop or mobile clients, once the image is broken, it stays permanently broken — there is no way for the user to trigger a reload.
The only way to fix it is to send a new Adaptive Card.
Reproduction Steps

Send an Adaptive Card in Teams with an image whose Url points to a public HTTPS image (Azure Blob in our case).
Image loads correctly when the card is first rendered.
Perform an interaction such as:
-> Expanding a nested card (Action.ShowCard), or
-> Using Action.ToggleVisibility to hide/show elements.
After this, the image disappears.
-> DevTools shows the src as a blob: URL that is now invalid.
Refreshing the web client restores the image, but in desktop/mobile clients the image remains broken permanently.

@Nivedipa-MSFT -> this is the continuation of #1812. I have attached the video of the issues.

AB.mp4

The src of these images are a Azure blob storage URL and I can confirm that the URL is working correctly .

[m365-agent-toolkit-assistant]

👋 Hi @dtiwarATS,

Thank you for reporting this issue! We want to let you know that:

⏱️ Our team will personally review your issue
🎯 You can expect a response within 1 business day

✨ This is an AI-generated initial response
🤖 AI-Generated Preliminary Analysis:

This is a known issue tracked in GitHub Issue #1812: Adaptive Card images from Azure Blob Storage break after user interaction and render as a blob: URL, which eventually gets invalidated. The problem occurs on Teams desktop and mobile clients, while web client recovers on refresh.

Actionable next steps:

1. Update Teams Client: Ensure you’re using the latest Teams desktop/mobile version, as Microsoft may have released fixes.
2. Test Again: Retest the image toggling scenario.
3. If Still Broken: Document the exact client version, share your Adaptive Card JSON payload, and reply in the GitHub issue for Microsoft to investigate.
4. Workaround: Currently, resending the card is the only way to restore affected images.

Further details and updates will be posted to the GitHub thread:
👉 #1812

✨We'd love your feedback! Please take a moment to fill out our survey.

---

Note: This is an automated first response generated by AI. A human team member will review your issue and provide a more detailed response soon. We appreciate your patience!

[Nivedipa-MSFT]

@dtiwarATS - Thanks for bringing this issue to our attention. Could you please share your adaptive card Json to test at our end?

[dtiwarATS]

I will share the Json today.

[dtiwarATS]

@Nivedipa-MSFT , please find the requested JSON file.

Sample.json

[dtiwarATS]

@Nivedipa-MSFT any updates on this?

[dtiwarATS]

@Nivedipa-MSFT any updates on this?

[Nivedipa-MSFT]

@dtiwarATS - Apologies for the delay. We have logged this as a bug and informed our engineering team. Our engineering team will look into it.

While we cannot guarantee a fix at this stage, we will keep you updated with any progress or changes. Please note that in some cases, the bug may be by design or deprioritized due to platform updates, but we will continue to monitor the bug closely.

Thank you again for bringing this to our attention!