Aspire 9.2 - ACA *Possible Breaking Change* #8695
Labels
area-azure-aca
area-deployment
area-meta
azure
Issues associated specifically with scenarios tied to using Azure
Hi folks! Aspire 9.2 ships April 10 and there is one breaking change for anyone deploying Azure SQL Server or Azure PostgreSQL to ACA.
We now support multiple managed identities for your database containers, meaning you will have to either give permission to an existing managed identity or create a new one to do your database operations.
You can find more details and the workaround in the docs issue.
We don't like breaking things on minor versions, but this is both a highly-requested feature and an important step towards more secure defaults. You can track issue #8389 where we're working on a mitigation.
The text was updated successfully, but these errors were encountered: