Migration

Migration

STAT v2 introduces breaking changes that make it incompatible with STAT v1. The versions however can run in parallel so migrating your v1 based triaged logic apps to v2 can be done over time and do not need to be done immediately upon installation of v2.

Currently, the migration path from STAT v1 to STAT v2 is manual and done in a side by side fashion. Installing STAT v2 does not migrate existing logic apps that are dependant on v1 service.

When STAT v2 is deployed, new logic apps can use either STAT v1 or STAT v2, but you should not mix the use of versions inside a single logic app. For example, you cannot use the STAT v1 Base Module output as an input to the STAT v2 Related Alerts module.

Manual Migration Overview

1. Deploy STAT v2 into a new or existing resource group following the standard deployment guidance
2. Clone an Existing STAT v1 Logic app as a backup
3. In the Logic App Designer, add equivalent STAT v2 steps below each STAT v1 step and mimic the configuration of the STAT v1 step.
4. Once a STAT v2 step has been added for each STAT v1 step update any other Logic app steps that depend on v1 output to depend on the v2 output
5. Remove STAT v1 steps and save the Logic app
6. Test