Adaptive Card Can Disable button after Submit

(2) Share

Report

Posted on by PA-22060747-0

Hi, Any suggestion on disabling the button after submission please?

I having also issue on this using MS Teams Apps Agent, the user can still click and submit button on previous cards and or after duplicate submission the card will skip the next and current cards :(

Categories:

Building Copilot Studio chatbots in Microsoft Teams

I have the same question (0)

All responses (4)

Answers (0)

Sort by

Suggested answer

Beyond The Platforms 246 on at

Like
a
(0)

Report
Copy link

Link copied!
Hi,

What you're seeing is a known behavior with Adaptive Cards in Teams and Copilot Studio. After a user submits a card, the original Action.Submit button remains active unless the card is explicitly updated or replaced. As a result, users can click old buttons again, which may trigger duplicate submissions or cause the conversation to skip subsequent cards.

Unfortunately, buttons are not automatically disabled after submission. The recommended approach is to:

Add unique identifiers to each submit action.

Track whether the card has already been processed.

Ignore duplicate submissions in your flow/topic logic.

Update or replace the original card after submission so that no active buttons remain.

For more advanced Teams scenarios, consider using Universal Actions (Action.Execute) and the Adaptive Card refresh model, which provides better control over card state and updates.

Hope this helps!
Paolo

✅ Did this solve your issue? → Accept as Solution
👍 Partially helpful? → Click "Yes" on "Was this reply helpful?" or drop a Like!

Want more tips on Power Platform & AI? Follow me here:

🔗 LinkedIn: https://www.linkedin.com/in/paoloasnaghi/
▶️ YouTube: https://www.youtube.com/@BeyondThePlatforms
📸 Instagram: https://www.instagram.com/beyond_the_platforms/
🌐 Website: https://www.beyondtheplatforms.com/

Was this reply helpful? Yes No
Suggested answer

Haque 3,653 on at

Like
a
(1)

Report
Copy link

Link copied!
Hi @PA-22060747-0,

Thanks for posting the issue here.

While it is true that Adaptive Cards do not feature a literal "disabled": true property, the Adaptive Cards schema natively handles this using the isEnabled property. If you are noticing that isEnabled is not behaving as expected, it is usually because of a specific host application limitation (such as Microsoft Teams) rather than the underlying schema itself.

Basically adaptive Cards schema does not support a disabled property on buttons.

Alternatives:

1. Let's capture the Activity ID and Coversation ID when we send the original Adaptive Card message. On Submit Action (in the bot or agent backend) process the user submission as usual and then create a new Adaptive Card payload that looks the same but with the submit button removed or replaced by a disabled button or text indicating submission is complete.

2. Toggle Visibility: Instead of disabling a button, you can include an Action.ToggleVisibility layer or default the button's "isVisible" property to false based on conditional data variables

Regarding duplicate submission:

Duplicate submissions happens if the bot backend takes too long to respond /user clicks multiple times before the card updates.

To mitigate this, implement server-side logic to ignore duplicate submissions based on user/session metadata.

Update the card immediately after the first submission to remove or disable the button visually.

Consider adding client-side debounce or disable logic if your client supports it.

Reference:

https://learn.microsoft.com/en-us/answers/questions/5856829/why-are-adaptive-cards-not-rendering-correctly-in

https://adaptivecards.io/explorer/Action.Submit.html

I am sure some clues I tried to give. If these clues help to resolve the issue brought you by here, please don't forget to check the box Does this answer your question? At the same time, I am pretty sure you have liked the response!

Was this reply helpful? Yes No
Suggested answer

11manish 3,333 on at

Like
a
(0)

Report
Copy link

Link copied!
For Teams Agents and Copilot Studio, use both:

Server-side validation (Dataverse/SharePoint status flag or transaction ID).

Replace/update the Adaptive Card after submission to remove the buttons.

Never rely on the client UI alone to prevent duplicate clicks. Even if a button appears disabled, users can still generate duplicate submissions due to retries,

delays, or multiple clicks. The safest pattern is to make the backend idempotent and reject already-processed requests.

Was this reply helpful? Yes No
Suggested answer

Valantis 6,735 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @PA-22060747-0,

The replies above cover the right approaches. Here's the most practical implementation for Copilot Studio + Teams specifically.

The cleanest solution is switching from Action.Submit to Action.Execute (Universal Actions). This gives you native card refresh capability built into Teams. When the user submits, the bot returns an updated card with the button removed or replaced by a "Submitted" text label. The card updates in-place without sending a new message.

In Copilot Studio, your flow or agent flow handles the Action.Execute invoke, processes the submission, then returns an updated card payload in the response. Teams renders the updated card over the original, disabling any further interaction automatically.

For duplicate submission prevention on the backend regardless of which action type you use: generate a unique submissionId when you send the card (store it in a SharePoint list or Dataverse row), check for it on every submit action, and reject any request where that ID already exists. This is the only reliable protection since client-side disabling can always be bypassed.

Microsoft's own guidance confirms Universal Actions are the recommended approach for cards that need state management in Teams.

Ref: https://learn.microsoft.com/en-us/microsoftteams/platform/task-modules-and-cards/cards/universal-actions-for-adaptive-cards/overview

Best regards,

Valantis

✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

🏷️ For follow-ups @Valantis.

📝 https://valantisond365.com/

💼 LinkedIn

▶️ YouTube

Was this reply helpful? Yes No