Check dashboard identity collisions before copying into Managed Grafana

Source facts

Copy to Managed Grafana replaces an existing destination dashboard with the same identity without a confirmation prompt. A copy normally lands in the destination’s root folder, but an identity match in another folder uses that folder instead. Only user-saved dashboards can be copied directly; an Azure-managed template must first be saved as a user copy. Microsoft Learn.

Applicability

This concerns the portal copy workflow, not a generic dashboard import API. Microsoft requires Grafana Editor or Admin access on an existing destination instance. Microsoft Learn.

DSE recommendation

Inspect the destination for an existing dashboard with the same identity before approving the copy. Have its owner decide whether replacement is intended and preserve an approved recoverable copy of any version that must remain available. Do not rely on the root folder view alone or expect the operation to pause for an overwrite decision. Treat a repeated copy as another replacement review.

Verification

Use a disposable destination to establish the expected identity and folder behavior before applying a production copy. Compare the resulting dashboard with the intended source and confirm that no separately maintained destination was unintentionally replaced. Record the collision check and owner decision alongside the operation result. A successful copy should not be described as proof that every panel can query its destination data; the source separately warns that non-Azure Monitor data sources require configuration.

Official references

Microsoft Learn: Copy to Managed Grafana. Source reviewed September 9, 2026.