Context

Follow-up from PR #7053 review. Parent tracking issue: #7112

PR Conversations

• Bicep snapshot approach and partial evaluator tradeoffs (@tg-msft, @vhvb1989)
• Struct vs map for snapshot resources (@tg-msft, @vhvb1989)

What needs to change

1. Evaluate whether the parsed SnapshotResource struct or a simple map[string]any is the better approach for representing snapshot resources.
2. Concern: providing multiple ways of exposing data (struct + raw JSON) may make it harder to add helpful features later.
3. Consider implications for provider-agnostic snapshots discussion.
4. Also consider whether metadata (e.g., expected quota decorations on params) survives through bicep snapshot — this may drive need for alternative approaches in the future.

Note: Keep current approach for now. Revisit after adding more validation rules to gain experience on what works well.

Files to update

• cli/azd/pkg/infra/provisioning/bicep/local_preflight.go (SnapshotResource type)