Add VM Insights V2 onboarding scenario with ARM and Bicep templates - #304
Open
Austin McCollum (austinmccollum) wants to merge 1 commit into
Open
Conversation
Adds a parameterized ARM template and an equivalent modular Bicep implementation that onboard an existing Azure VM to VM Insights V2 in a single deployment. Covers managed identity, Azure Monitor workspace, Log Analytics workspace, data collection rule and association, the Azure Monitor Agent extension, and optional recommended alert rules. Six parameter files cover the common standard and per-process scenarios in both ARM and Bicep parameter formats. Co-authored-by: Copilot App <[email protected]> Copilot-Session: 4a30eb2e-5701-4a75-bae0-489b7a8fb2b7
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a new scenario with ARM and Bicep templates that onboard an existing Azure VM to VM Insights V2 in a single deployment, instead of running the agent install, DCR creation, and DCR association steps separately.
These templates are long (the ARM template is ~750 lines), so they live here rather than inline in Microsoft Learn. The Azure Monitor VM onboarding article will link to this folder.
What changed
Scenarios/How to onboard VMs to VM Insights V2/.vmi-v2-onboard.jsondeploys at resource group scope and uses nested deployments so resources can land in different resource groups.bicep/main.bicepis the equivalent modular implementation with nine resource modules. It setstargetScope = 'subscription'because its modules span resource groups.README.mddocuments the scenarios, prerequisites, full parameter reference, deployed resources, and the eight recommended alert rules.Scope
Onboards existing Azure virtual machines. Does not create the VM or resource groups, and does not cover scale sets or Arc-enabled servers.
Verified
az bicep buildonbicep/main.bicepsucceeds (Bicep CLI 0.43.8).BCP037warning onscheduledTransferPeriodis a Bicep type-definition gap, not a template defect. The property is valid on the DCR API and appears in the published Azure Monitor DCR samples..bicepparamdeployment requires Azure CLI 2.53.0+ or Azure PowerShell 9.7.1+, per the Bicep parameters file documentation.