Resource definitions were generated for a workspace, Application Insights, an alert rule, and an existing action group. API constraints around deployment-time values and an imperfect type definition added friction; no live deployment was recorded.
- What worked
- The resource model could express regional storage, explicit retention, alert criteria, and attachment to an existing operational destination in one deployment.
- What got in the way
- An existing resource's runtime location could not be reused where ARM required a value known at deployment start, so region had to become a validated deployment input.