azure / azurestack-quickstart-templates

Quick start ARM templates that deploy on Microsoft Azure Stack

Microsoft Azure Stack Quickstart Templates

This repository contains Azure Resource Manager deployment templates that have been tested with Microsoft Azure Stack Development Kit.

What repository?

The primary Azure Resource Manager templates repository on GitHub is the azure-quickstart-templates. You can find the repository here https://github.com/Azure/azure-quickstart-templates

Over time many GitHub users have contributed to the repository, resulting in a huge collection of more than 400 deployment templates. This repository is a great starting point to get a better understanding of how you can deploy various kinds of environment to Microsoft Azure. If you scroll through the templates in the azure-quickstart-templates repository, you will notice that there are templates that reference services (resource providers) that are not part of Microsoft Azure Stack Development Kit, such as ExpressRoute or CDN.

To ensure the successful deployment of templates to both Microsoft Azure and Microsoft Azure Stack Development Kit, this temporary GitHub repository AzureStack-quickstart-templates was created. This repository contains samples to test your Microsoft Azure Stack Development Kit environment. Over time, some templates from this temporary repository will be moved to the azure-quickstart-templates repository and this temporary AzureStack-quickstart-templates repository will be depreacated.

If you want to contribute your Azure Resource Manager templates to GitHub, you should make your contribution to the azure-quickstart-templates repository.

Contribution Guide and best practices

The azure-quickstart-templates repository contains a contribution guide and best practices. When you perform a pull-request to the repository, Microsoft will evaluate the code in your pull request based on the guidelines in these documents.

• Contribution-Guide
• Best-Practices

Familiarizing yourself with these documentes, improves the contribution experience.

The contribution guide also explains how to ensure that your deployment template complies with the requirements for it to show up on the gallery in the public Microsoft Azure website.

Azure Resource Manager limitations in Microsoft Azure Stack Development Kit

You can use all kind of template functions within your deployment template. You can find a description of these template functions here: https://azure.microsoft.com/en-us/documentation/articles/resource-group-template-functions/

To ensure that the templates that you create will deploy to both Microsoft Azure and Microsoft Azure Stack Development Kit, you must be aware of a couple of limitations related to Azure Resource Manager in the Microsoft Azure Stack Development Kit. Some functions of Azure Resource Manager are not yet available in this release of Microsoft Azure Stack.

The following template functions are not available in Microsoft Azure Stack Development Kit yet.

• skip
• take

API Versions for Resource Providers

Each resource provider in Microsoft Azure has its own API version. Microsoft Azure Stack Development Kit supports the current API versions for the available resource providers, with some minor exceptions. To ensure your template will succesfully deploy to both Microsoft Azure and Microsoft Azure Stack Development Kit, use the latest API versions that are available in Microsoft Azure Stack Development Kit for all resources in your template. To retrieve a list of the available API versions connect to your Microsoft Azure Stack Development Kit environment by following the Authenticate PowerShell with Microsoft Azure Stack procedure described in this article.

https://azure.microsoft.com/en-us/documentation/articles/azure-stack-deploy-template-powershell/

When you are connected to your environment, you can retrieve a list of the available resource providers and the supported API versions by running the following PowerShell cmdlet

Get-AzureRmResourceProvider | Select ProviderNamespace -Expand ResourceTypes | FT Providernamespace, ResourceTypeName, ApiVersions

This cmdlet can also be used for Microsoft Azure.

Validate existing deployment templates

You can verify if an existing deployment template is valid for a given environment with the Test-AzureRmResourceGroupDeployment PowerShell cmdlet. After connecting to your environment in a PowerShell session run the following PowerShell cmdlet

Test-AzureRmResourceGroupDeployment -ResourceGroupName ExampleGroup -TemplateFile c:\Templates\azuredeploy.json

Please note that this cmdlet does not verify the resource provider specific properties for the resources within the template. This cmdlet can be used for Microsoft Azure and Microsoft Azure Stack Development Kit.

Next steps

Start with creating deployment templates in your own repository. Make sure they deploy to both Microsoft Azure and Microsoft Azure Stack Development Kit, they are in line with the guidelines in the azure-quickstart-templates contribution guide and the guidelines described here. Fork the azure-quickstart-templates repository, add or update and send pull requests to the azure-quickstart-templates. If your templates comply with the requirments they will even show up in the gallery on the public Microsoft Azure website.

azurestack-quickstart-templates's Issues

SQL HA template needs to be updated for SQL 2017

Currently hard-coded for SQL2016SP1

No one is merging PRs

There are 5 PRs and 4 are over 2 weeks old. I have a PR that is 3 weeks old and I had a review but no one is merging.

Support for SharePoint 2019 RTM?

What are the plans to support SharePoint 2019 RTM? Is anyone working on that? If there is a task list please share the details and maybe we can help out. Cheers

FabricVmCreationError

I used a custom template to create a deployment, which succeeded yesterday.
The same template today fails with the following message:

{
"code": "DeploymentFailed",
"message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-debug for usage details.",
"details": [
{
"code": "Conflict",
"message": "{\r\n "status": "Failed",\r\n "error": {\r\n "code": "ResourceDeploymentFailure",\r\n "message": "The resource operation completed with terminal provisioning state 'Failed'.",\r\n "details": [\r\n {\r\n "code": "FabricVmCreationError",\r\n "message": "Failed to create VM 'NetScaler-VPX-Express' "\r\n }\r\n ]\r\n }\r\n}"
}
]
}

Have any idea what may be the cause of this instability in deployments?

sql-2016-alwayson - First SQL-Server throwing communication errors

Hi there,

we're currently trying to deploy sql-2016-alwayson on our lab-system. The deployment as it is, works pretty well but we're currently facing the issue that one of two SQL-Servers is throwing errors that the aoglistener and the aodns seem to be offline.
The other SQL-server doesn't throw errors and sees the aodns and aoglistener online.

Is it intended to work this way or did we missed out on something?

Best regards

ISO - Location

The tempalte sql-2014-standalone, requires an ISO for the SQL installation (version SQLServer2014SP1-FullSlipstream-x64-ENU). This ISO is no longer accessable at this location. http://care.dlservice.microsoft.com/dl/download/2/F/8/2F8F7165-BB21-4D1E-B5D8-3BD3CE73C77D/SQLServer2014SP1-FullSlipstream-x64-ENU.iso. This breaks the installation of SQL and the deployment of this template.

Network Security for WorkersSNG - appservice-fileserver-sqlserver-ha template

Hi after finish deployment you will struggle with ScaleSets of Workes, because Network Security for WorkersNSG block you any network connections to File Server.

When you go into app service management inside one of Controller you will see workers in Starting status, example of error for worker:
Info 5/20/2019 3:09:30 PM Start exercise FileServer at 5/20/2019 3:09:30 PM
Warning 5/20/2019 3:10:00 PM Failed exercise FileServer at 5/20/2019 3:10:00 PM
Info 5/20/2019 3:11:00 PM Start exercise FileServer at 5/20/2019 3:11:00 PM

You have to change in template NSG definition, the rule which block connection is
Outbound_Deny_VNet so you have to add by explicity with low pirority Outbound Allow for File Server Cluster of FIle Server Subnet.

Thanks

Create HA Infrastructure for an AppServices deployment

Hi,

I've successfully deployed this ARM template in our environment, however when trying to provide values from deployment output, I am getting following error:

Do you have any idea what can cause that?

Deployment Template Validation Failed

The two 101 acsengine Docker quickstart templates are producing the following error:
Deployment template validation failed: 'The template resource 'swarmm-master-lb-fx2ooljsdc2gk/SSHPort22-swarmm-master-fx2ooljsdc2gk-0' is not valid. The api-version property at line '1256' and column '9' is not defined. The api-profile '2018-03-01-hybrid' for the template does not match any valid api-version for the resource type 'Microsoft.Network/loadBalancers/inboundNatRules'. Either explicitly specify the api-version for the resource or specify the correct api-profile for the template.

Trying to run the template directly from the Azure Stack portal on a connected stack.

Azure Stack version: 1.1901.0.99 (Yes... I know...)

101-vm-windows-create - Deployment Issue

Json template does'nt work correctly as the VM name is populated with the Json parameter. Let me know if you can find the issue....

I tested the simple deploy to try-out the template feature with azure....

Remove AzureStack-QuickStart-Templates/101-vm-linux-apply-extension-docker/

This extension is no longer supported on Azure and will be removed from Azure Stack.

101-acsengine-docker-swarmmode deployment successfull but swarm not deployed

AzureStack-QuickStart-Templates/101-acsengine-docker-swarmmode/ ran successfull, however, docker swarmmode is not configured. there ius also no output log from configure-swarmmode-cluster.sh
.

Docker has been isnatllerd however with 17.06 but unable to start

Failing ARM Template appservice-fileserver-standalone

when deploying the Template for appservice-fileserver-standalone I receive an error at step
https://raw.githubusercontent.com/Azure/Azure-QuickStart-Templates/master/appservice-fileserver-standalone

New-AzureRmResourceGroupDeployment : 6:19:27 AM - Resource Microsoft.Compute/virtualMachines/extensions 'FileServerVM/Customscript' failed with message '{
  "status": "Failed",
  "error": {
    "code": "ResourceDeploymentFailure",
    "message": "The resource operation completed with terminal provisioning state 'Failed'.",
    "details": [
      {
        "code": "VMExtensionProvisioningError",
        "message": "VM has reported a failure when processing extension 'Customscript'. Error message: Failed to download all specified files. Exiting. Error
Message: The remote server returned an error: (404) Not Found."
      }
    ]
  }
}'

in the parameter file azuredeploy.parameters.json the section vmExtensionScriptLocation redirects to a non existing project.

wrong:

"vmExtensionScriptLocation": {
    "value": "https://raw.githubusercontent.com/Azure/azure-quickstart-templates/master/appservice-fileserver-standalone"
}

how it works:

 "vmExtensionScriptLocation": {
    "value": "https://raw.githubusercontent.com/Azure/azurestack-quickstart-templates/master/appservice-fileserver-standalone"
}

url vmExtensionScriptLocation

Hi MS Team,
What is this URL "https://raw.githubusercontent.com/Azure/azurestack-quickstart-templates/master/appservice-fileserver-standalone" stand for ?

I found that link in vmExtensionScriptLocation section, but I can't directly access that link from browser. Is that URL reachable or is it broken link?

Error Code: ImageNotFound

Thanks for your work.
I got the below error when I try to deploy template [101-simple-linux-vm] via azure stack portal [Microsoft.Template->Error details]

--error detail--

At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-debug for usage details. (Code: DeploymentFailed)
The platform image 'Canonical:UbuntuServer:14.04.3-LTS:latest' is not available. Verify that all fields in the storage profile are correct. (Code: ImageNotFound)

How to fix it?
thanks
-Aaron

ad-no-ha variables not correct

Hello,

in the template for the ad-no-ha (Site) in the azuredeploy.json is a bug on line 53.
The line is:
"dnsPrefix": "[concat('ADDNS',resourceGroup().name)]",
but it must be that:
"dnsPrefix": "[toLower(concat('ADDNS',resourceGroup().name))]",

Good luck to fix it :)

101-vm-linux-create Template has CentOS 7.3 but the latest ISO is 7.2

In the parameters file:

https://github.com/Azure/AzureStack-QuickStart-Templates/blob/master/101-vm-linux-create/centos.7.3.azuredeploy.parameters.json

the SKU is 7.3 but the latest CentOS ISO located here (from docs link):

http://olstacks.cloudapp.net/latest/

is 7.2

SP 2016 deployment failing to deploy, 1805

{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-debug for usage details.","details":[{"code":"Conflict","message":"{\r\n "status": "Failed",\r\n "error": {\r\n "code": "ResourceDeploymentFailure",\r\n "message": "The resource operation completed with terminal provisioning state 'Failed'.",\r\n "details": [\r\n {\r\n "code": "VMExtensionProvisioningError",\r\n "message": "VM has reported a failure when processing extension 'ConfigureSPServer'. Error message: DSC Configuration 'InstallAndConfigureSharePointServer' completed with error(s). Following are the first few: The user does not exist or is not unique. Object reference not set to an instance of an object. Cannot perform security configuration because the configuration database does not exist. You must create or join to a configuration database before doing security configuration."\r\n }\r\n ]\r\n }\r\n}"}]}

Please make download links for SQL as Parameter

Hi guys,

can we put the link for the download source for SQL Server 2014 as a Parameter with Default value.
Here in my demolap for Azure Stack I don't have a big Internet Connection and a deployment takes along time, if I must download the files from the Internet. The template for SharePoint have a optional Source Parameter and I can but the source in my local Blob storage.

UPDATE

Please edit the SharePoint template also, because if I use my custom link on my local blob storage, it want a trusted Connection to the https URL on my blob storage. This means you can't deploy SharePoint if you use your own private blobstorage....
To do this you must for example by the DSC Config for SQL Server 2014 in the file xDownloadISO.psm1 insert a line befor line 50 with this content:
[System.Net.ServicePointManager]::ServerCertificateValidationCallback = {$true}
and after line line 51 a line with this content:
[System.Net.ServicePointManager]::ServerCertificateValidationCallback = null
more Information here
This will ignor the untrusted connection. I think the best way to make the DSC secure also, is to add a parameter that ask if you download source is untrusted.

Sql HA is not enabled for integrated user to login by default

Sql account like sa is not allowed to login after SQL HA deployed.

AzureRM Hybrid Profile discrepancy

Team,

For example the 101-vm-windows-create template located here contains this code:
https://github.com/Azure/AzureStack-QuickStart-Templates/blob/master/101-vm-windows-create/azuredeploy.json

"$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#",
"contentVersion": "1.0.0.0",
"apiProfile": "2018-03-01-hybrid",
"parameters": {

As noted the apiProfile is 2018-03-01-hybrid is stated; however, according to this external MS doc: https://docs.microsoft.com/en-us/azure-stack/operator/azure-stack-powershell-install

it states:
You don't need to install AzureRM.Bootstrapper to install the modules for Azure stack version 1901 or later.
Don't install the 2018-03-01-hybrid profile in addition to using the above AzureRM modules on Azure Stack version 1901 or later.

So which is it - install the 2018-03-01-hybrid profile or not. Because you need this in order to deploy it?

mysql-standalone-server-windows - update to current images

	"5.7": "https://dev.mysql.com/get/Downloads/MySQL-5.7/mysql-5.7.18-winx64.zip",
	"5.6": "https://dev.mysql.com/get/Downloads/MySQL-5.6/mysql-5.6.36-winx64.zip",
	"5.5": "https://dev.mysql.com/get/Downloads/MySQL-5.5/mysql-5.5.56-winx64.zip"

SharePoint deployment, where can I get the needed images.

Hello,

I have a question to the note on this Site.
In the Note section of this site is a descritpion that means, I do Need some images. But where I can get this images? Can I downloaded this from the public Azure and can put in my private Azure Stack?

Update readme files to call out use of the built-in connection to Azure Stack Quickstart

On readmes, it is not necessary to use cut and paste for azure stack instances that are connected to the internet. Instead, use the "Quickstart template" feature to browse this repo and automatically populate the custom template.

mongodb-cluster is duplicate

mongodb-cluster appears to be a copy of hadoop-cluster.

[exchange-2016-non-ha] Failing due to incorrect DNS setting and failing to download required artefact

DNS name resolution is not going to work to resolve external name given above settings.

ad-non-ha fails to deploy due to old schema

Deploying ad-non-ha/adVmTemplate.json fails on Azure because the default schema version 2016-01-01 for Microsoft.Storage/storageAccounts is no longer using the property accountType .
The error message is "The accountType field is missing from the request."

sql-2016-alwayson - Allow all NSG Rule

@JeffGoldner

This resource is added to the NSG which opens up everything.
IMO this does not set a good example, rather leave it default and state something about NSG rules in the readme?

    "resources": [
        {
            "name": "[variables('nsgName')]",
            "location": "[resourceGroup().location]",
            "type": "Microsoft.Network/networkSecurityGroups",
            "apiVersion": "2015-06-15",
            "properties": {
                "securityRules": [
                    {
                        "name": "rule1",
                        "properties": {
                            "protocol": "*",
                            "sourcePortRange": "*",
                            "destinationPortRange": "*",
                            "sourceAddressPrefix": "*",
                            "destinationAddressPrefix": "*",
                            "access": "Allow",
                            "priority": 101,
                            "direction": "Inbound"
                        }
                    }
                ]
            }
        },

sql-2016-alwayson - SqlVmIaasExtension's automated backup is not available to HA's sql VMs.

I'm new to the MS SQL HA stuff so this might be a simple question. But after the deployment of the sql-2016-alwayson, I don't see SqlVmIaasExtension's automated backup settings on both primary and secondary sql VMs, which is available to the sql 2016 standalone deployment (from the marketplace).

Does anybody know the reason why? I'd like to set up automated database backup for the tenant databases.

Or, for HA, do we have to run the script like the one in the link below?
https://docs.microsoft.com/en-us/sql/relational-databases/backup-restore/back-up-multiple-databases-to-azure-blob-storage-powershell?view=sql-server-ver15

Any advise?

The AzS-bgpnat01 VM does not longer exist on the new Azure Stack versions

Please update the page for the ASDK part, the AzS-bgpnat01 VM does not longer exist on the new Azure Stack versions

Download link for SQL 2014 is not valid

Hello,

http://care.dlservice.microsoft.com/dl/download/2/F/8/2F8F7165-BB21-4D1E-B5D8-3BD3CE73C77D/SQLServer2014SP1-FullSlipstream-x64-ENU.iso

is no longer valid all templates runs into an error.

BR
mountainbrother

This repo is missing important files

There are important files that Microsoft projects should all have that are not present in this repository. A pull request has been opened to add the missing file(s). When the pr is merged this issue will be closed automatically.

Microsoft teams can learn more about this effort and share feedback within the open source guidance available internally.

Merge this pull request

Am not getting the domainNameLabel correct

Hope it's okay to post a general question here that is not really an issue, but more my lack of understanding on what is being expected. I'm following this post on the Dell site (https://community.emc.com/docs/DOC-80070) to prepare and run this template. The writer said that the value for the Domain Name Label parameter in the setup script must be used as the CN in the SSL certificate that is created. In his example he has this value as "CN=cseregistry.rack04.cloudapp.azs.mhclabs.com". So in my setup script (and in my certificate) I used the value of "csregistry.local.cloudapp.azurestack.external", as this seemed comparable for my Azure Stack SDK environment. But when I run the deploy script, the deployment fails, complaining that "The domain name label csregistry.local.cloudapp.azurestack.external is invalid. It must conform to the following regular expression:
^[a-z][a-z0-9-]{1,61}[a-z0-9]$." Obviously I am misunderstanding something. Can anyone set me straight on this?

Issue with creating Service SAS for a container with ARM template

Hi,
I am trying to create Service SAS using ARM template for one of the containers with read permission and Jan 2050 as expiry. Runs successfully but I do not see any change in Portal.

Here is the arm template:
"variables": {
"storageAccountName": "test",
"containerName": "testcontainer",
"secondContainerName": "containertwo",
"serviceSasFunctionValues": {
"canonicalizedResource": "[concat('/blob/', variables('storageAccountName'), '/', variables('containerName'))]",
"signedResource": "c",
"signedPermission": "r",
"signedExpiry": "2050-01-01T00:00:00Z"
}
}

"outputs": {
"serviceSas": {
"type": "string",
"value": "[listServiceSas(variables('storageAccountName'), '2018-02-01', variables('serviceSasFunctionValues')).serviceSasToken]"
}
}

Always On Script Update for Managed disk

Hello,
I created the AG with ARM script with success, but i noticed that the script is creating unmanaged disk instead of managed disk which is not recommended by Microsoft .
Is there an update for this script ?

Best regards,
Khouloud.

Failing SharePoint DSC Configuration

I am getting an error when trying to provision the SharePoint 2013 non-Ha template in Azure Stack. Most of the template deploys correctly, but when trying to configure the SharePoint server I am constantly getting this error. Has anyone encountered this error if so how was this error fixed? thanks

Here is the error that Azure Stack is throwing:

{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-debug for usage details.","details":[{"code":"Conflict","message":"{\r\n "status": "Failed",\r\n "error": {\r\n "code": "ResourceDeploymentFailure",\r\n "message": "The resource operation completed with terminal provisioning state 'Failed'.",\r\n "details": [\r\n {\r\n "code": "VMExtensionProvisioningError",\r\n "message": "VM has reported a failure when processing extension 'ConfigureSPServer'. Error message: DSC Configuration 'InstallAndConfigureSharePointServer' completed with error(s). Following are the first few: PowerShell DSC resource MSFT_xSPInstall failed to execute Set-TargetResource functionality with error message: SharePoint install failed, exit code was 30066 The SendConfigurationApply function did not succeed."\r\n }\r\n ]\r\n }\r\n}"}]}

Storage account mismatch with current online version

The version of the template in this repository seems to use a standard storage account standard_LRS whereas deploying in Azure marketplace provisions a premium one -- This cost me my entire monthly budget in three days. Please correct this, or use 72 point red blinking text on the portal provisioning wizard. You say we're only billed for VMs, but my storage account burned up $100 in a few days? I don't even know how that works from a billing and consumption perspective! You're returning to the opaque Azure of old, not to mention this 1999-era return to arcane configuration syntax. Json is even more brain dead than XML is.

HA improvements

One VM (WS2016) configured as Domain Controller for a new forest with a single domain
It provisions single DC. Could be a single point of failure. Shouldn’t we have a backup DC created in availability group to ensure HA?
Reference : https://github.com/Azure/azure-quickstart-templates/tree/master/active-directory-new-domain-ha-2-dc

One VM (WS2016) configured as File Share Witness for the cluster.
This could be point of failure again. Instead we could use cloud witness (which is in theory would be HA)?

Test

Correct paths in _artifactsLocation Template sql-2016-alwayson

Hi these files no longer exist and template validation not pass

--"rdpIPAdressSetupURL": "[concat(parameters('_artifactsLocation'),'/publicip-rdp.json')]",
--"provisioningADVM": "[concat(parameters('_artifactsLocation'),'/provisioningADVM.json')]",
--"configuringBackupADVM": "[concat(parameters('_artifactsLocation'),'/configuringBackupADVM.json')]",
--"adBDCModulesURL": "[concat(parameters('_artifactsLocation'),'/CreateADBDC.ps1.zip')]",

sql-2016-alwayson - VM extension issues

Hi @JeffGoldner,

I seem to have issues with the new SQL always on template. Everything goes fine untill the extention, giving these errors:

One or more VM extension handlers failed to resolve for VM 'priDC-zo'. Please check individual extension status for more details.

{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-debug for usage details.","details":[{"code":"Conflict","message":"{\r\n "status": "Failed",\r\n "error": {\r\n "code": "ResourceDeploymentFailure",\r\n "message": "The resource operation completed with terminal provisioning state 'Failed'.",\r\n "details": [\r\n {\r\n "code": "VMExtensionProvisioningError",\r\n "message": "One or more VM extension handlers failed to resolve for VM 'priDC-zo'. Please check individual extension status for more details."\r\n }\r\n ]\r\n }\r\n}"}]}

When I check extension under the VM in the portal I dont get any info:

Running multinode on 1807.

scripturi for Azure Repos

Hi

I have seen a few examples of the scriptUri variable with a value starting with

"scriptUri": "https://raw.githubusercontent.com

Is it possible to achieve the same thing using a private Azure Repo? We use Azure Devops (foo.visualstudio.com/bar/_git) to host scripts and I would like to deploy them using an ARM template wihtout moving them to a public repo on GitHub

Is there any way to achieve this currently?

Sample-Hybrid-Application template issue

For the sample-hybrid-application, there seems to be an issue with 4.2 "Deploying Template (Azure Stack)". In step #2, there are two commands, the first command has an issue with parameters not referenced in the PowerShell script such as "Location" and "TenantID".

.\Deploy-SolutionAzureStack.ps1 -rg {enterValue} -presharedkey {enterValue} -storageAccountName {enterValue} -targetStorageContainer {enterValue} -location {enterValue} -tenantID {enterValue} -azureStackArmEndpoint {enterValue} -Verbose

The second command works fine.

test Kevin Comment

here's my comment