Azure Resource Manger - Microsoft.Storage/storageAccounts vs microsoft.classicstorage / storageAccounts
What is the difference between microsoft.classicstorage/storageAccounts
and Microsoft.Storage/storageAccounts
?
Executing the following commands
> Switch-AzureMode -Name AzureResourceManager
> Get-AzureLocation
Results in:
Microsoft.Storage/storageAccounts
- Eastern USA
- East US 2
- Western USA
- Western Europe
- East Asia
- Southeast Asia
- Japan East
- Japan West
- North Central America
- South Central America
- Central America
- Northern Europe
microsoft.classicstorage / storageAccounts
- East Asia
- Southeast Asia
- Eastern USA
- East US 2
- Western USA
- North Central America
- South Central America
- Central America
- Northern Europe
- Western Europe
- Japan East
- Japan West
- Brazil South
- Australia East
- Australia Southeast
You can see that is Microsoft.Storage/storageAccounts
not available in any of the Australian data centers.
Should I use an microsoft.classicstorage/storageAccounts
azure resource manager in my template so that I can target the Australian region, or will this type of storage end up being deprecated, so I'm better off going with Microsoft.Storage/storageAccounts
elsewhere?
source to share
Currently, the new Azure Resource Manager (ARM) stack (Microsoft.Storage/storageAccounts) does not support Australia East and South East (or South Brazil). Thus, you cannot create a storage account in these regions through the ARM stack.
The portal is based on the old Azure Service Management (ASM) stack (microsoft.classicstorage / storageAccounts), and these locations are maintained through this stack. That is why you can create them through the portal. The same thing happens with PowerShell if you use Service Management PowerShell cmdlets.
We recommend that users move to the ARM stack if possible, as this will eventually lead to the removal of the ASM stack.
source to share