How can I reduce regression issues when adding new features in our web application using Azure DevOps?

Question

We frequently release updates to our web application, but each new feature carries the risk of breaking existing functionality. To address this, we’re looking to implement test automation that covers both API endpoints and frontend workflows.

Our main concerns are:

Keeping automated tests maintainable as features evolve

Detecting regressions before changes reach production

Minimizing the time spent on repetitive manual tests

Integrating tests smoothly into Azure DevOps pipelines for faster feedback

Platforms such as Keploy offer practical solutions for test automation, automatically creating and replaying tests to ensure consistency and minimize maintenance. I want to know if anyone has implemented a similar strategy in Azure DevOps, and how they balanced automation coverage with maintenance overhead.