[Hubs] Portal deployment form is missing Data Explorer capacity, scopes to monitor, and tags #2400

📝 Scenario

As a FinOps hub admin deploying from the Azure portal, I need every option that matters for a hub to be available in the portal form in order to avoid being forced to the command line for settings the form omits.

⚠️ Problem

createUiDefinition.json exposes most template parameters (storage and Data Explorer SKU, retention, network access, NAT gateway, address prefix, managed exports, infrastructure encryption, recommendations, tags by resource, Fabric options, remote hub). It does not expose these main.bicep parameters, so portal deployments always use defaults:

• dataExplorerCapacity (cluster node count)
• scopesToMonitor
• tags (only tagsByResource is exposed)
  Retention values left at the default mean "keep current", so the portal also can't set retention back to its default.

💎 Solution

Add the missing options to the form, or document that they require a parameter file or PowerShell (and why). Document the retention reset behavior in the form text (already partly in the retention step).

📋 Tasks

• Add dataExplorerCapacity, scopesToMonitor, and tags to createUiDefinition.json, or document the gap in the deploy and template docs
• Verify the form outputs against main.bicep parameters (test or script) so new template parameters aren't missed

✅ Acceptance

• Every main.bicep parameter is either in the portal form or listed as parameter-file/PowerShell only in the docs.

ℹ️ Additional context

Related: portal upgrade issue. Raised in PR #2394 review.

🤖 Generated with Claude Code