Azure Resource Manager Deployment vs Classic Deployment of Storage Accounts

Question

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

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

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

1. Use a table storage container as a storage location for Web App diagnostics. This is because I am only able to enable diagnostics through the old portal and it does not appear to recognize the ARM v2 storage account.
2. The ability to create CDN endpoint based on a Storage Accounts origin type. It's the same scenario again; the old portal does not recognize the newer storage account type.

So at least for the moment, these constraints are forcing me to use a (classic) storage account in order to use the above features. Have I understood this correctly or am I missing something?

Answer 1

The new portal does not have a way of doing either of these things right now, but they are in the backlog. Both should be accomplishable using the client libraries (available in .Net, Node, and Java) or the command line tooling available through Powershell or Xplat CLI .

See also: Azure storage non Classic (V2) - How to configure custom domain