issue in schema of default-azuredeploy-sandbox.json

[ahughes257]

default-azuredeploy-sandbox.json validation error

getting a PS error on deployment "invalid template" -

    New-AzResourceGroupDeployment : 09:04:04 - Error: Code=InvalidTemplate; Message=Deployment template validation failed: 'The template resource 
  'iomtfhir/Microsoft.Authorization/xxxx-xxx-xxx-xxxx-xxxxx' for type 'Microsoft.Authorization/roleAssignments' at line '331' and column '59' has incorrect segment lengths. A 
  nested resource type must have identical number of segments as its resource name. A root resource type must have segment length one greater than its resource name. Please see 
  https://aka.ms/arm-template/#resources for usage details.'.
  At C:\Users\xxxx\iomt-fhir-master\deploy\scripts\Create-IomtFhirSandboxEnvironment.ps1:101 char:1
  + New-AzResourceGroupDeployment -TemplateFile $sandboxTemplate -Resourc ...
  + 
      + CategoryInfo          : NotSpecified: (:) [New-AzResourceGroupDeployment], Exception
      + FullyQualifiedErrorId : Microsoft.Azure.Commands.ResourceManager.Cmdlets.Implementation.NewAzureResourceGroupDeploymentCmdlet
   
  New-AzResourceGroupDeployment : The deployment validation failed
  At C:\Users\xxxx\iomt-fhir-master\deploy\scripts\Create-IomtFhirSandboxEnvironment.ps1:101 char:1
  + New-AzResourceGroupDeployment -TemplateFile $sandboxTemplate -Resourc ...
  + 
      + CategoryInfo          : CloseError: (:) [New-AzResourceGroupDeployment], InvalidOperationException
      + FullyQualifiedErrorId : Microsoft.Azure.Commands.ResourceManager.Cmdlets.Implementation.NewAzureResourceGroupDeploymentCmdlet

[pallar-ms]

@ahughes257 - I'm unable to repro this with the latest sandbox deployment script and templates. I've also verified that the segment lengths for the role assignments are actually valid, and given the nature of the error I'd expect it to be a consistent reproducible issue if it wasn't valid.
Could you provide us more information on what version of the script you ran? Were there any local template changes by any chance when you had run this? Alternatively, could you try again with the latest and see if it occurs again?