<p>Currently have velero up and running and it's working great. The only issue I have is that the snap shots of the volumes are being created in the same region as the originals which kinda defeats the purpose of disaster recovery. This flag</p>
<p><code>--snapshot-location-config</code></p>
<p>doesn't have arg for region. I know there is a config for the default snap shot location</p>
<p><code>volumesnapshotlocations.velero.io &quot;default&quot;</code></p>
<p>Does anyone know how to modify the default so I can get my snap shots into new regions?</p>

<p>Snapshots creation from the main region into a different region is not supported.<br />
Azure zone-redundant snapshots and images for managed disks have a decent 99.9999999999% (12 9's) durability. The availability zones in a region are usually physically separated and even if an outage affects one AZ, you can still access your data from a redundant AZ.</p>
<p>However, if you fear calamities that can affect several square kilometers(multiple zones in a region), you can manually move the snapshots in a different region or even automate the process. <a href="https://thomasthornton.cloud/2020/04/06/copy-azure-virtual-machine-snapshots-to-another-region-and-create-managed-disks-using-powershell/" rel="nofollow noreferrer">Here</a> is a guide to do it.</p>
