Parameterize cross-tenant demo deployment inputs

[johnstel]

Problem statement

Current deployment/setup flow is single-tenant oriented. Customer demo handoff needs explicit, parameterized cross-tenant inputs (subscription/app registration/region/env template) to avoid manual rework and runtime failures.

Priority

P1 — preflight blocker for customer-tenant demo repeatability.

Acceptance criteria

• Deployment path supports customer-provided tenant/subscription/app registration values.
• Environment template includes all required variables with guidance.
• Docs clearly split operator steps vs customer-provided inputs.
• Dry-run validation succeeds with sample tenant parameters.

Checklist

• Define required cross-tenant parameter contract.
• Add/update env template and docs.
• Validate parameterized flow in test tenant.
• Capture known failure modes and remediation notes.

[github-actions]

📋 Assigned to Kaylee (Azure Platform Engineer)

Issue: #9 — Parameterize cross-tenant demo deployment inputs

Kaylee will pick this up in the next Copilot session.

For Copilot coding agent: If enabled, this issue will be worked automatically.
Otherwise, start a Copilot session and say:
Kaylee, work on issue #9

[johnstel]

@copilot please start on this issue and open a draft PR when ready.