Can't see St Account after rg move

[RobMiller86]

Ticket: 06343753

In short, we migrated a st account to a different rg in the same subscription as part of a migration. Deployed a new rg and new vnet for VBAZ, along with new st accounts with immutability. Normally we add the old st account as a repo so we have access to the old archives. I've done this in the past with no issue. But for this client, after we migrated the st acct to the new rg, Veeam cant' see it no matter how many times we rescan or wait. It's been 5 days since this rg move.

All storage accounts and resources are in the same rg and same vnet.
All vnets are allowed access to the account via the st acct firewall, including the vnet that contains the VBAZ and workers.
There are no private endpoints or anything weird.

This st account was in use by the prior VBAZ 18.04 appliance and was working fine. The only difference is that it was moved to a new rg with the new VBAZ.

So far, I can't add it. Veeam simply never sees it when you scan. It sees the other st accounts in the same rg just fine.

Anyone have any ideas how to get VBAZ to see this st account?

[lyudmila.ezerskaya]

Hi, we'll look into it and get back to you, but our support team might nail it down quicker.

[RobMiller86]

So it turns out that a previous admin had used the autocreated veeam storage account as a backup repo. The st acct that has a name similar to veeamfxfxhsqmc. I'm guessing Veeam allowed this to occur in a previous version and no longer does. So now that I've migrated this deployment to a new VBAZ, it can't import the backups. Can I simply move this container to a new st acct using Azure Storage Explorer and it will work?

[lyudmila.ezerskaya]

Hi! It's correct that storage accounts created by the backup appliance can't be used as repositories.

Moving the data to another storage account should theoretically work, but please note that this scenario hasn't been tested.

To be on the safe side, as a workaround, you can remove the Veeam Backup for Microsoft Azure tag ("Veeam Backup Appliance ID" or "VB for Azure") from the storage account and restart the backup service. In this case, the account will become visible in the repository wizard, and the backup appliance will create a new storage account for service purposes.