Check resource-level authority when an Azure Advisor dismissal fails

Source facts

Microsoft’s Advisor permission guide says an error when postponing or dismissing a recommendation can indicate insufficient permission. Its prescribed check is the permission level on the resource associated with that recommendation, including whether the operator has Contributor or higher access there. Microsoft Learn.

Applicability

Use this review for a specific Advisor recommendation that the operator is authorized to manage. Identify its associated resource and the reason for the proposed disposition. Access to a recommendation screen should not be used as evidence that every action on every resource is authorized.

DSE recommendation

DSE recommends asking the resource owner to review both the requested disposition and the required action permission. Prefer having an already authorized owner perform the approved action where appropriate, rather than granting broad additional access for convenience. Preserve the recommendation identifier, original status and rationale in the work record before changing it.

Verification

Inspect effective permissions at the associated resource and document the authorized route chosen. After the approved action, confirm the recommendation’s resulting state and ensure that the rationale remains accessible to the responsible team. Record any unresolved permission error without treating the attempted dismissal as complete. Include the recommendation in the owner’s ordinary review process.

Official references

Microsoft Learn: Roles and permissions.