anchor.diff:  The documentation below references command output from the [Azure
   CLI](https://azure.microsoft.com/en-us/documentation/articles/xplat-cli-install/).
   
  -## Configuration Reference
  -
  -The following configuration options are available for building Azure images. In
  -addition to the options listed here, a
  -[communicator](/docs/templates/communicator.html) can be configured for this
  -builder.
  -
  -### Required options for authentication:
  +## Authentication:
  +There are three options for Authenticationg to Azure, two of which require certain
  +configuration options in order to properly build an Azure Arm Image.
  +
  +### Managed Identity
  +
   If you're running packer on an Azure VM with a [managed identity](/docs/builders/azure.html#azure-managed-identity)
  -you don't need to specify any additional configuration options.
  -If you would like to use interactive user authentication, you should specify
  -`subscription_id` only. Packer will use cached credentials or redirect you
  -to a website to log in.
  -If you want to use a [service principal](/docs/builders/azure.html#azure-active-directory-service-principal)
  +you don't need to specify any additional configuration options. As Packer will attempt to use the Managed Identity
  +and subscription of the VM that Packer is running on.
  +
  +### Interactive User Authentication
  +To use interactive user authentication, you should specify `subscription_id` only.
  +Packer will use cached credentials or redirect you to a website to log in.
  +
  +### Service Principal
  +To use a [service principal](/docs/builders/azure.html#azure-active-directory-service-principal)
   you should specify `subscription_id`, `client_id` and one of `client_secret`,
   `client_cert_path` or `client_jwt`.
   
  
positive.code:     Directory docs](https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-certificate-credentials)
      for more information.
  
  ### Required:
  
  <%= partial "partials/builder/azure/arm/Config-required" %>
  
  #### VHD or Managed Image
  
  The Azure builder can create either a VHD, or a managed image. If you are
  creating a VHD, you **must** start with a VHD. Likewise, if you want to create
  a managed image you **must** start with a managed image. When creating a VHD
  the following options are required.
  
  -   `capture_container_name` (string) - Destination container name. Essentially
      the "directory" where your VHD will be organized in Azure. The captured
  
negative.code: 
  Providing `temp_resource_group_name` or `location` in combination with
  `build_resource_group_name` is not allowed.
  
  ## Basic Example
  
  