Expose an `Id` Bicep output reference for Azure Front Door

[eerhardt]

Summary

The Aspire Azure Front Door resource should expose its resource ID as an Id Bicep output reference.

Motivation

While adding Azure Front Door diagnostic settings in dnceng/aspire-msft PR 64797, the deployment needed the provisioned Front Door profile ID. Because the resource does not expose an Id output reference, the application had to add and consume a custom provisioning output.

An official output reference would let consumers pass the Front Door resource ID to diagnostic settings and other dependent infrastructure without duplicating provisioning logic.

Proposed behavior

• Azure Front Door exposes an Id Bicep output reference for the provisioned profile resource ID.
• The output can be consumed by dependent resources through the standard Aspire resource-reference APIs.
• Provisioning tests verify the output name and generated Bicep value.

[joperezr]

🤖 Aspire triage pass — 2026-09-04 23:02 UTC

Area: area-integrations
Kind: feature-request
Repro: none
Affected version(s): not specified (latest: 13.5.3)
Severity: S4 — additive infrastructure API enhancement with a documented workaround

Urgency: ⚪ backlog — no milestone
Reason: valid narrowly scoped enhancement, but not important or actionable enough for 13.6

Suggested owner(s): Sébastien Ros (@sebastienros) (score 34), backup Mitch Denny (@mitchdenny) (score 14)
Evidence:

• sebastienros merged [release/13.5] Mark Radius provider builders experimental #19874, Fix Python callback handle wrapping #19870, [release/13.5] Pin C# API surface #19866 in area-integrations (last 30d)
• sebastienros closed aspire destroy fails to uninstall Helm release for AKS deployments #19206 and Polyglot-Compatible Integration Discovery #15320 as completed in area-integrations
• mitchdenny merged Use supported Cosmos emulator API in consumers #19837, Fix Azure Sandbox deployment principal binding #19801, Add AKS persistent volume support #19226 in area-integrations (last 30d)

Confidence: medium
Needs human?: no