Power Platform Community Forum Thread Details

Can the null-comment-allowed functionality be returned to the "post a choice of options as the flow bot to a user" Teams action/connector?

Is there a workaround within - or planned reversal to - the 4/1/2026 change to the "post a choice of options as the flow bot to a user" Teams action/connector that now newly requires a non-null value in the comments field before Teams will return the selected option (and any entered comment) back to the flow?

Prior to 4/1/2026 a comment was optional but not required.

The Teams action/connector also does not have any new adjustability in PowerAutomate that could allow the flow owner to either (a) show/hide the comments field nor (b) let a null comment be allowable or not.

Solutions I am not interested in:

* "Just enter something random into the comments each time" - why should I need to do that when the action/connector functioned fully without gibberish placeholder comments before 4/1/2026?

* "Use the "post adaptive card and wait for a response" action/connector instead' - why do I need to be forced to rebuild my flow with a new action when the previous action worked 100% of the time prior to this unnecessary & disruptive change

Issue - Connector - post a choice of options as the flow bot to a user.jpg

Categories:

Connector development

Confirming the behavior with a fresh test flow: the comment field in Post a choice of options as the flow bot to a user (SubscribeUserMessageWithOptions) is now mandatory in the rendered Teams card - the Submit button does not fire until something is typed.

No flow-side workaround exists. The action only accepts messageTitle, messageBody, options, and recipient. There is no parameter for commentRequired, defaultComment, commentPlaceholder, or hideComment. The card template is rendered server-side by Microsoft's Teams connector, so nothing in the flow definition can override it. Pinning an older connector version isn't possible either - the Teams connector is centrally versioned.

Microsoft has been quietly degrading the "flow bot" surface in Teams in favor of pushing people to Adaptive Cards, which is why every workaround thread ends up there unfortunately to your scenario.