LinkedDeployments-Contributor assumes that the deployment account only has contributor rights to a specific resource group (or subscription). This is the more common deployment scenario.
LinkedDeployments-Owner assumes that the deployment account has owner rights to a subscription. This is a less common deployment scenario (possibly development environment) as that account will be highly privilaged and have access to all resource groups.
AzureRM.* PowerShell modules have been installed (or AZ.* modules with the Enable-AzureRMAlias command run).
Update each of the
*.parameters.jsonfiles with the appropriate values.
Update-AutomationAzureModulesForAccount.ps1files to a blob storage account with public blob read access (for demo purposes only) granted.
Note: A more secure approach would be to update the templateStorageContainerUriRoot and parametersStorageContainerUriRoot parameters in
helloworldParent.parameters.jsonfile to use a SAS token to the storage account instead of assigning public blob read access. This would require updating the SAS token frequently or using a long lived token.
DeployTemplate-Owner.ps1with the appropriate region, resource group name (only for Contributor scenario), and deployment name.
Login to Azure PowerShell to the subscription desired.
DeployTemplate-Owner.ps1from the context of the folder desired.