`addAzureAppServiceEnvironment` always produces ACR

[sveinung-t]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

When running aspire publish my Azure App Service Environment setup is attempting to create another Azure Container Registry, even if one is provided to it already.

Expected Behavior

addAzureAppServiceEnvironment should not attempt to create an additional Azure Container Registry when one is already provided.

Steps To Reproduce

const acr = await builder.addAzureContainerRegistry('application-acr')
	.publishAsExisting('playgroundoverviewacr', { resourceGroup: 'application' })
const appservice = await builder.addAzureAppServiceEnvironment('application')
	.withAzureContainerRegistry(acr)
	.withAcrPullIdentity(key)
	.publishAsExisting('application', { resourceGroup: 'application' })

1. Add the above code to Typescript file apphost.mts
2. Attempt to run aspire publish

Exceptions (if any)

❌ Capability Error: Cannot add resource of type 'Aspire.Hosting.Azure.AzureContainerRegistryResource' with name 'application-acr' because resource of
type 'Aspire.Hosting.Azure.AzureContainerRegistryResource' with that name already exists. resource names are case-insensitive.
Code: INTERNAL_ERROR
Capability: Aspire.Hosting.Azure.AppService/addAzureAppServiceEnvironment
❌ An unexpected error occurred: The TypeScript (Node.js) apphost failed.

Aspire doctor output

PS C:\path\to\application> aspire doctor 

Aspire Environment Check
========================

Aspire
  ✅ Aspire CLI version 13.4.6 (channel: stable)  

AppHost
  ✅ AppHost version 13.4.6 (aspire-apphost\apphost.mts)  

Container Runtime
  ⚠️ Docker: installed but not running ← active  
       Start Docker Desktop       

Environment
  ✅ TypeScript AppHost tooling found (npm, npx).  
  ✅ HTTPS development certificate is trusted  

Summary: 4 passed, 1 warnings, 0 failed
For detailed prerequisites: https://aka.ms/aspire-prerequisites

Aspire CLI Installations
========================

╭────────────────────────────────────────────────────────────────┬─────────────────────────────────────────────────┬──────────────┬──────────────┬─────────────╮
│ Path                                                           │ Version                                         │ Channel      │ Route        │ PATH status │
├────────────────────────────────────────────────────────────────┼─────────────────────────────────────────────────┼──────────────┼──────────────┼─────────────┤
│ C:\Users\{redacted}\.aspire\npm\13.4.6\win-x64\bin\aspire.exe  │ 13.4.6+87fe259e4fc244c599019a7b1304c85a1488f248 │ stable       │ (unknown)    │ not on PATH │
│ (current)                                                      │                                                 │              │              │             │
│ C:\Users\{redacted}\AppData\Roaming\npm\aspire.CMD             │ (not probed)                                    │ (not probed) │ (not probed) │ active      │
│ C:\Users\{redacted}\AppData\Local\Microsoft\WinGet\Packages\Mic│ (not probed)                                    │ (not probed) │ (not probed) │ shadowed    │
│ rosoft.Aspire_Microsoft.Winget.Source_8wekyb3d8bbwe\aspire.EXE │                                                 │              │              │             │
╰────────────────────────────────────────────────────────────────┴─────────────────────────────────────────────────┴──────────────┴──────────────┴─────────────╯

Anything else?

If the names do not collide no error is generated, but this just means it successfully creates a bicep for another Azure Container Registry.

[joperezr]

🤖 Aspire triage pass — 2026-08-07 10:11 UTC

Area: area-integrations
Kind: bug
Repro: yes-minimal — TypeScript snippet in the "Steps To Reproduce" section of the issue body
Affected version(s): 13.4.6 (per aspire doctor; latest stable: 13.4.6)
Severity: S3 — bring-your-own existing ACR path for addAzureAppServiceEnvironment is broken (duplicate ACR resource added); the default create-ACR path is unaffected, so a workaround exists

Urgency: ⚪ backlog — no milestone
Reason: scenario-specific bug, not a confirmed regression (no evidence the combination worked in a prior 13.x); does not clear the raised 13.5 stabilization bar (regressions / S1–S2 no-workaround only)

Suggested owner(s): David Pine (@IEvangelist) (score 9), backup David Fowler (@davidfowl) (score 6)
Evidence:

• David Pine (@IEvangelist) merged [auto-sec] Consolidate Aspire JavaScript template dependency security remediations #18858, [auto-sec] Consolidate npm security remediations (vite, Angular, undici, hono, protobufjs, and more) #18735, Add ergonomic Azure subnet service-delegation API #18728 touching src/Aspire.Hosting.Azure.AppService (last 30d)
• David Fowler (@davidfowl) merged Fix cross-scope ACR pull identities #18742, Add App Service delegated subnet support #18738 touching src/Aspire.Hosting.Azure.AppService (last 30d)
• CODEOWNERS lists Eric Erhardt (@eerhardt) Mitch Denny (@mitchdenny) for /src/Aspire.Hosting.Azure.AppService

Confidence: medium
Needs human?: no