Keep an Advisor alert's storage group separate from its recommendation scope

Source facts

Microsoft’s Advisor alert setup separates the resource group used to save the alert from the recommendation targeting scope. The guide explicitly states that the saved rule’s resource-group selection does not change that target scope. Microsoft Learn.

Applicability

Use this review when creating or relocating an Advisor recommendation alert. Identify the intended subscription and optional target resource-group filter independently from the rule’s own storage location. Confirm that the planned recommendation category is supported by the current source before proceeding.

DSE recommendation

DSE recommends recording both scopes in the alert request with different labels. Have the resource owner confirm the recommendation population and the monitoring owner confirm where the rule will be managed. Review category and impact or recommendation-type conditions separately. Avoid assuming that saving the rule beside a workload automatically limits its notifications to that workload.

Verification

Read back the deployed alert’s target conditions and storage resource group. Compare each with the approved request, then use an authorized test or observed matching event to validate the intended notification route. Check that excluded resources are outside the targeting conditions. Preserve the two scope values with the rule identifier so later organizational moves do not silently change assumptions.

Official references

Microsoft Learn: Create Advisor alerts for new recommendations using Azure portal.