We’re excited to continue our journey with the adaptivecards-templating
package, a more robust and streamlined approach to creating Adaptive Cards. This package offers enhanced features for developers and simplifies the process of creating cards with data payloads.
What’s changing?
To simplify your experience and reduce overlap in the Microsoft 365 Developer ecosystem of SDKs, we’ve decided to deprecate the Adaptive Card Tools package in August 2025. Moving forward, we encourage you to transition to the adaptivecards-templating
package.
Why the change?
We’ve listened to your feedback about the complexity of having too many SDKs and tools. By consolidating our offerings, we aim to provide a more streamlined and efficient development experience.
What this means for you
We believe that the adaptivecards-templating
package will provide an even better experience. Here’s what you need to know:
- For New Projects: If you are starting a new project with Teams Toolkit, you will notice the project template no longer includes the Adaptive Card Tools package. Instead, implementations are shifted to use
adaptivecards-templating
.
- For Existing Projects: If you have an existing project with the Adaptive Card Tools package, you will see a deprecation warning in the next update. We recommend transitioning to
adaptivecards-templating
.
How to transition
Below is an example of how you can make the switch (or follow this PR):
Timeline
Based on our Support Policy, Teams Toolkit CLI and SDKs model after Azure SDK’s lifecycle and support policy:
- August 2024: announcement and warnings added in to annotations of the SDK API.
- August 2024 – August 2025: only the most critical bug fixes and security fixes will be addressed, no further updates will be shipped.
- August 2025: The package will be officially deprecated in NPM registry.
We’re excited about the future and the new solutions we’ll be bringing your way. Thank you for your continued support and feedback!
Should you have any concerns, please send a message to ttkfeedback@microsoft.com
0 comments