can you update an existing storage accounts via Bicep?

Hello O, we understand that you're facing issue with updating your storage account to GPv2 using Bicep, especially since you initially modified it manually in the portal. This can indeed cause deployment issues, if there's a mismatch in the kind of storage account.

Based on your description, you're correct that Bicep does not allow for updates on existing storage accounts if there’s a kind mismatch. If you directly updated the storage account to a type that is incompatible with your Bicep code, redeploying will cause errors.

Here are some steps you can try:

1. Check Current Kind: Verify the current kind of your storage account in the Azure portal to confirm it is still set as blobstorage or if it has somehow been changed.
2. Update for GPv2: Since the goal is to switch to GPv2, ensure that in your Bicep template, you set the kind property explicitly to StorageV2 (or storageV2). Ensure no other deployments are overriding this value. Example:

      resource storageAccount 'Microsoft.Storage/storageAccounts@2021-04-01' = {
      name: 'yourStorageAccountName'
      location: 'yourLocation'
      sku: {
        name: 'Standard_LRS'
        tier: 'Standard'
      }
      kind: 'StorageV2' // Change this to StorageV2
      }
   

3. Recreate the Storage Account (if possible): If the above steps don't solve the problem, consider creating a new storage account with the correct settings via your Bicep file, and then migrate your data if needed.
4. Deployment Rollbacks: Unfortunately, if there's an ongoing issue with your current setup, short of restoration from backups or using Azure support, you may need to create a new account and point your resources to it.

reference document : https://learn.microsoft.com/en-us/azure/azure-resource-manager/bicep/quickstart-create-deployment-stacks?tabs=azure-cli%2CCLI#update-the-deployment-stack

Hope this helps, thanks

Hello O, I just wanted to kindly follow up to check if you had a chance to review my earlier response. I hope the information shared was helpful. Please feel free to reach out if you have any additional questions or need further clarification. If the answer addressed your query, it would be great if you could accept it and up-vote. This not only helps us but also makes it easier for other community members who might face the same issue. Thanks