Has anyone else been notified that their production Azure Container Apps environments will be automatically migrated to the new Express offering unless they opt out? We received three emails from the Container Apps team about migrating three production environments. The problem is that Express currently appears to lack several features we depend on, including managed-identity-based pulls from Azure Container Registry. An opt-out process buried in an email feels risky for production workloads, especially when the migration could remove functionality. Is this rollout official, and what capabilities are actually supported?
2 Answers
I haven't seen a detailed public announcement beyond the migration emails. The notice we received linked to an opt-out form where each environment had to be identified by its resource ID, along with the general Express documentation. I would want a complete feature comparison and a clear migration timeline before allowing this on production workloads.
Express may support user-assigned managed identities, but system-assigned identities appear to be unsupported. We use user-assigned identities throughout our Azure production setup, so that distinction could matter depending on how your environments are configured.
We also avoid system-assigned identities, but the current documentation seems to indicate that neither identity type is supported for this scenario. It only mentions using a username and password, which is not workable for us.
Announcing a production-impacting change mainly through an email that can easily be missed is understandably concerning. A migration should not proceed until teams can verify that all of their existing features and identity configurations are supported.