title: ARM template vs Azure SDK feature compatibility
body: <p>I'm looking for any gaps in the support for operations on Azure resources via the Azure SDK (java) vs. ARM templates. </p>
  
  <p>So far, we've only found that blobs/queues/tables cannot be managed by ARM, while the containing StorageAccount can be. No documentation that calls out the differences either. </p>
  
  <p>I prefer to use ARM templates as they provide atomicity of create and update across resources, provided they support all or most of the functionality. </p>
  
  <p>Resources we're interested in are mostly IAAS-ish resources - Virtual network, security groups, subnets et al, LBs, storage artifacts, VM instances, DNS, etc. </p>
  
  <p>Need this for basic create/delete operations and frequent update operations (e.g. patch VM images, modify DNS entries,  move the ENI from one VM to another, etc). </p>