You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Hide azure-environment when all Azure resources use emulators #19617
When every Azure resource in an AppHost is configured to run as a local emulator, the dashboard still shows an azure-environment resource in the Not started state.
This adds noise to the resource list and suggests that part of the application has not started, even though no Azure provisioning environment is needed for the local run.
Expected behavior
azure-environment should be hidden when all Azure resources in the model use emulators and no resource needs Azure provisioning. Alternatively, it could be hidden by default unless it participates in the current run.
Actual behavior
azure-environment appears as a visible, Not started resource alongside otherwise running emulator resources.
Reproduction
Using Aspire CLI/SDK 13.5.2 with a TypeScript AppHost, configure Azure resources exclusively with local emulators, for example:
Azure Cosmos DB with runAsPreviewEmulator
Azure Storage with runAsEmulator
Azure Event Hubs with runAsEmulator
Start the AppHost and open the Resources page in the dashboard. The azure-environment resource remains visible in the Not started state.
Area: area-integrations, area-app-model Kind: bug Repro: yes-minimal — see the Reproduction section (lines ~19–27 of the issue body) Affected version(s): 13.5.2 (latest: 13.5 line, wrapping up) Severity: S4 — cosmetic dashboard noise; the azure-environment resource shows Not started when all Azure resources are emulators. Misleading but non-blocking; obvious workaround (ignore the resource).
Urgency: ⚪ backlog — no milestone
Reason: UX polish, not a regression and not S1/S2. Backlog is the default while 13.5 stabilizes.
Activity
joperezr commentedon Aug 24, 2026
🤖 Aspire triage pass — 2026-08-24 07:22 UTC
Area:
area-integrations,area-app-modelKind: bug
Repro: yes-minimal — see the Reproduction section (lines ~19–27 of the issue body)
Affected version(s): 13.5.2 (latest: 13.5 line, wrapping up)
Severity: S4 — cosmetic dashboard noise; the
azure-environmentresource shows Not started when all Azure resources are emulators. Misleading but non-blocking; obvious workaround (ignore the resource).Urgency: ⚪ backlog — no milestone
Reason: UX polish, not a regression and not S1/S2. Backlog is the default while 13.5 stabilizes.
Suggested owner(s): Sébastien Ros (@sebastienros) (score 39), backup Karol Zadora-Przylecki (@karolz-ms) (Azure specialist)
Evidence:
area-integrations(last 90d) and closed 6area-integrationsissues as completed (last 180d)area-integrationsand 9 inarea-app-model(last 90d)Confidence: medium
Needs human?: no
chore(deps): Bump the nuget-minor-patch group with 4 updates (#905)
Bump the aspire group with 3 updates (#151)
deps: Bump Aspire.Hosting.AppHost and Scalar.AspNetCore (#96)
chore(deps): Bump the dotnet group with 30 updates (#16)
chore(deps): Bump Aspire.Hosting.AppHost from 13.5.3 to 13.5.4 (#835)