[docs] Document Azure Front Door origin naming change

[aspire-repo-bot]

Documents changes from microsoft/aspire#20035

@eerhardt

Targeting release/13.6 based on the source PR milestone 13.6.

Why

microsoft/aspire#20035 changes how the Aspire Azure Front Door hosting
integration derives generated origin names: origin names now combine the
resource-group ID with the origin's backend hostname, instead of hashing the
resource-group ID alone. This is called out in the source PR as a breaking
deployment change (the PR carries the breaking-change label) — upgrading
changes origin resource names even when the backend hostname hasn't changed,
and incremental ARM deployments can leave old and new origins coexisting in
the same origin group.

What changed

• src/frontend/src/content/docs/integrations/cloud/azure/azure-front-door.mdx
  • Updated the single-origin generated Bicep sample to show the new
    uniqueString(resourceGroup().id, my_api_host) origin name.
  • Added a new <Aside type="caution"> describing the 13.6 breaking change,
    alongside the existing 13.4 upgrade caution.
  • Added a "Preserve origin names from before Aspire 13.6" subsection under
    "Customize provisioning infrastructure" with the ConfigureInfrastructure
    override (taken from the source PR body) that restores the pre-13.6
    default origin names.
• src/frontend/src/content/docs/whats-new/aspire-13-6.mdx
  • Updated the intro bullet list from "One breaking change" to "Two breaking
    changes" to include the Front Door change.
  • Added a "Front Door origin identity" bullet to the Integration updates
    section, linking to the breaking-changes section.
  • Added a new "Front Door origin names now include the backend hostname"
    breaking-change entry (with the ConfigureInfrastructure override
    example and a LearnMore link back to the source PR and the Front Door
    integration doc).

Both pages were updated in place; no new pages were created.

Generated by PR Documentation Check for #20035 · auto · 96.7 AIC · ⌖ 15.9 AIC · ⊞ 18.3K · ◷

[aspire-repo-bot]

Frontend HTML artifact ready

The latest frontend build uploaded the frontend-dist artifact for PR #1646. Use the VS Code button below to open this PR with GitHub Artifacts Explorer and browse the built HTML locally.

This comment updates automatically when a new frontend build artifact is uploaded.

[Copilot]

🟢 Approval recommended

The documentation updates are consistent with the described breaking change and the samples/guidance align with the stated new naming behavior.

Pull request overview

This PR updates the Aspire 13.6 documentation to reflect a breaking change in the Azure Front Door hosting integration: generated origin names now incorporate the backend hostname (in addition to the resource group ID), affecting upgrade/deployment behavior.

Changes:

• Update the Azure Front Door integration doc’s generated Bicep example to use uniqueString(resourceGroup().id, <backendHost>) for origin names.
• Add/expand upgrade guidance warning that incremental ARM deployments can leave old and new origins coexisting after upgrading to 13.6.
• Add a breaking-change entry to the Aspire 13.6 “What’s new” page, including a ConfigureInfrastructure fallback snippet to preserve pre-13.6 origin naming.

File summaries

File	Description
src/frontend/src/content/docs/whats-new/aspire-13-6.mdx	Adds a new breaking-change entry and highlights the Front Door origin naming behavior change in 13.6.
src/frontend/src/content/docs/integrations/cloud/azure/azure-front-door.mdx	Updates the generated Bicep example and adds an upgrade caution specific to the 13.6 origin naming change.

Review details

• Files reviewed: 2/2 changed files
• Comments generated: 0
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.