Feature Request: Validate Storage Account Configuration for Azure Files Mount in Container App Environment

[trylvis]

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

Currently, when adding a Storage Account to a Container App Environment (CAE) and entering invalid information—such as an incorrect Storage Account name or account key—there is no validation in place.

This lack of validation also extends to verifying whether the CAE subnet is whitelisted in the Storage Account's network rules. As a result, misconfigurations are only detected later, when the Storage Account is mounted to a Container App. At that point, replicas fail, requiring users to dig through system logs to identify the issue.

Describe the solution you'd like.

Introduce validation when configuring Storage Accounts, including checks for:

1. Correct credentials (e.g., Storage Account name and key).
2. Network-layer validation to ensure the Container App Environment can reach the Storage Account (e.g., subnet whitelisting).

This would allow users to catch configuration errors upfront, improving usability and reducing debugging effort.

Describe alternatives you've considered.

Currently, there are no viable alternatives to detect these issues before the configuration reaches the Container App mounting stage.