201-hdinsight-datalake-store-azure-storage

201-hdinsight-datalake-store-azure-storage

### Issue Details
While running the template through the ansible, i am getting the below error:
fatal: [localhost]: FAILED! => {"changed": false, "failed_deployment_operations": [], "msg": "Deployment failed with status code: 400 and message: The request content was invalid and could not be deserialized: 'Error converting value \"https://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#\" to type 'Microsoft.WindowsAzure.ResourceStack.Frontdoor.Data.Definitions.DeploymentParameterDefinition'. Path 'properties.parameters.$schema', line 1, position 125.'."}

fatal: [localhost]: FAILED! => {"changed": false, "failed_deployment_operations": [], "msg": "Deployment failed with status code: 400 and message: The request content was invalid and could not be deserialized: 'Error converting value \"1.0.0.0\" to type 'Microsoft.WindowsAzure.ResourceStack.Frontdoor.Data.Definitions.DeploymentParameterDefinition'. Path 'properties.parameters.contentVersion', line 1, position 5996.'."}

fatal: [localhost]: FAILED! => {"changed": false, "failed_deployment_operations": [], "msg": "Deployment failed with status code: 400 and message: The request content was invalid and could not be deserialized: 'Could not find member 'servicePrincipalObjectId' on object of type 'DeploymentParameterDefinition'. Path 'properties.parameters.parameters.servicePrincipalObjectId', line 1, position 6034.'."}

Start with the 201-hdinsight-datalake-store-azure-storage template and reproduce its deployment through Ansible. Inspect the generated Azure deployment parameters, especially the $schema, contentVersion, and servicePrincipalObjectId entries, against the reported deserialization errors. Done means the template deploys without these 400 errors.

Written by the indexing model from the issue text.