The 'fix' to (compute the list properly) has now been released to all regions. However, this means that any stacks updated in November or December of 2023 may have an inaccurate list of resources (namely, some resources in templates with an 'existing' tag).
This will prove especially problematic if the next iteration of the stack is deployed in 'delete' mode (rather than detach); if a stack has additional resources listed, it will try to delete them.
We recommend running the next stack deployment in detach mode (either re-run the template from the previous iteration, or a newer version if you prefer), which will preserve all of the resources that would otherwise not be part of the stack.
An issue was found in Nov 2023, where some stacks would incorrectly calculate the list of managed resources.
Specifically, if the template was authored in bicep and leverages symbolic Code Generation, as referenced in the comments below: https://github.com/Azure/deployment-stacks/issues/132#issuecomment-1803317989 https://github.com/Azure/deployment-stacks/issues/147#issuecomment-1911509364
The 'fix' to (compute the list properly) has now been released to all regions. However, this means that any stacks updated in November or December of 2023 may have an inaccurate list of resources (namely, some resources in templates with an 'existing' tag).
This will prove especially problematic if the next iteration of the stack is deployed in 'delete' mode (rather than detach); if a stack has additional resources listed, it will try to delete them.
We recommend running the next stack deployment in detach mode (either re-run the template from the previous iteration, or a newer version if you prefer), which will preserve all of the resources that would otherwise not be part of the stack.