Geek Answers Handbook

Deploying Azure vs Classic Resource Manager Deploying warehouse accounts

I am trying to understand the differences between Azure Resource Manager Deployment and Classic Deployment of Azure Storage Accounts:

https://azure.microsoft.com/en-us/documentation/articles/resource-manager-deployment-model/

So, from what I can collect, if I use the Azure Resource Manager (ARM) deployment method to deploy the storage account (v2), I would lose the ability:

  • Use the table storage container as the storage location for the web diagnostic application. This is because I can only enable diagnostics through the old portal, and it does not seem to recognize ARM v2.
  • Ability to create a CDN endpoint based on the source type of Storage Accounts . This is the same scenario again; old portal do not recognize the new type of storage account.

So, at least at the moment, these restrictions force me to use the (classic) repository account to use the above functions. Did I understand this correctly or is something missing?

+5
source share
1 answer

The new portal has no way to do any of these things right now, but they are lagging behind. Both should be implemented using client libraries (available in .Net, Node, and Java) or command line tools available through the Powershell or Xplat CLI .

See also: Azure storage non Classic (V2) - custom domain setup

+1
source

More articles:


All Articles