Classic vault accounts are created using the existing service management API (the REST API stack, available over the past few years). New storage accounts are created using the new Azure Resource Manager (ARM) API (which is also wrapped in PowerShell and the CLI). In the end, they provide the same resources for your applications, but they are created / managed in different ways, and there are several nuanced differences (for example, the possibility of resource tags created using ARM scripts).
You cannot convert a classic vault account (or any classic resource) to a newer type. You still donβt need to if you are not trying to combine resources from classic and new, for example, adding ARM-based virtual machines to a virtual network based on the classical interface or creating a virtual ARM-based virtual machine from a VHD image while sitting on a classic storage account ( and for this example you can always just copy vhd to a new repository account). Note that for shared storage use (blobs / tables / queues) you just need a URI and a primary (or secondary) key. With their help, you can access your storage resources from anywhere, from any VM / website / etc., regardless of whether you use storage access from classic or new virtual machines, for example.
Check out this link for a general list of differences between classic and new resources.
David Makogon Sep 16 '15 at 23:06 2015-09-16 23:06
source share