adaptive-card

To generate Microsoft Teams Adaptive Card JSON, create a new card definition file under the cards/ directory using the Adaptive Cards v1.5 schema, ensuring every Action.Submit includes data.msteams.type for correct botActivityHandler dispatch.

Action.Submit fails to route in the Teams botActivityHandler when the card JSON omits the required data.msteams.type routing property or lacks activityId injection at send/update time. Enforcing these identifiers ensures correct server-side dispatch.

Yes, you can use ChoiceSet and Text inputs when creating Adaptive Cards v1.5. The generated card structure supports these required input components alongside ColumnSet headers, optional ToggleVisibility sections, and ActionSet layouts for bot workflows.

The best way to structure Teams Adaptive Cards for input forms is using the v1.5 envelope with ColumnSet headers and ActionSet layouts. This ensures proper input component rendering and valid Action.Submit routing for bot dispatch.

Yes, you need to manually inject activityId at send/update time when sending Adaptive Cards in Teams. The card generation process handles JSON structure and msteams.type routing, but activityId injection is required to satisfy botActivityHandler dispatch.