Recent validation has broken the cli for mapping storage account to webapp

[ksaffarian]

Describe the bug

Hi
Recent validation #30990 broken the cli.
Issues that I can think of are:

• The validation assumes the storage account to exist in the same resource group as the webapp. This is not true all the times. The API (and portal) allows for storage account to be in a different resource group. In our case, the storage is not in the same place as the webapp.
• The validation should only run if the StorageType is set to AzureFile. In our case, we use AzureBlob and the validation is not relevant. However, it is stopping us to mount the storage.

This is quite important as the Azure Pipeline task https://learn.microsoft.com/en-us/azure/devops/pipelines/tasks/reference/azure-cli-v2?view=azure-pipelines fetches latest cli and introduces this bug to all customers who are mapping blob containers to webapp.

Related command

az webapp config storage-account add --storage-type AzureBlob .....

Errors

The share '*****' does not exist in the storage account '****'

Issue script & Debug output

N/A

Expected behavior

The command should mount a blob storage or azure file from a different resource group.

Environment Summary

Azure-CLI 2.71.0

Additional context

No response

[yonzhan]

Thank you for opening this issue, we will look into it.

[microsoft-github-policy-service]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @AzureAppServiceCLI, @antcp, @yutanglin16.

[github-actions]

Here are some similar issues that might help you. Please check if they can solve your problem.

• Adding to an AppService a mount to an inexistent Azure FileShare doesn't produce an error (but breaks the appService instance) #21721

---

Possible solution (Extracted from existing issue, might be incorrect; please verify carefully)

Solution 1:

The new validation is not taking the mount type into account. Please revert or publish a fix.

Reference:

• Adding to an AppService a mount to an inexistent Azure FileShare doesn't produce an error (but breaks the appService instance) #21721 (comment)

Solution 2:

The validation assumes the storage account to exist in the same resource group as the webapp. In our case, the storage account is in a different resource group. So, even if I add a dummy file share to bypass the validation, it does not work.

Reference:

• Adding to an AppService a mount to an inexistent Azure FileShare doesn't produce an error (but breaks the appService instance) #21721 (comment)

Powered by issue-sentinel

[microsoft-github-policy-service]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @AzureAppServiceCLI, @antcp, @yutanglin16.

[seligj95]

Closing. Linked PR will remove the validation in the next CLI release which will be available on May 6. Temporary workaround is to downgrade to previous CLI version.