microsoft / microsoft/aspire

Azure System Managed Identity support

Open
#18,515 1 comment 2 reactions 0 assignees View on GitHub
area-integrations triage:bot-seen
Dominant language
C#
Stars
6.3k
Forks
991
Avg merge
2d 12h
Merged PRs (30d)
201

Description

### Is there an existing issue for this?

- [x] I have searched the existing issues

### Is your feature request related to a problem? Please describe the problem.

Aspire automatically sets up user assigned managed identities and creates role assignments so that Container Apps can access the Container Registry, Storage, Log Analytics, etc.

The lifecycle of these identities is (or should be!) closely tied to the resources they're serving. This is the ideal use for system managed identities.

### Describe the solution you'd like

Instead of creating user assigned managed identities, use system managed identities by default.

### Additional context

_No response_

Contributor guide

Open the contributing guide

Research direction

No files or tests are named. Start by tracing where Aspire provisions user-assigned managed identities and role assignments for Container Apps and their dependent resources; compare the requirements for Azure system-managed identities. Done means system-managed identities are used by default while required registry, storage, and Log Analytics access continues to work.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, csharp
Domain
authorization, cloud, infrastructure
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.