Skip to content
Quick start ARM templates that deploy on Microsoft Azure Stack
Branch: master
Clone or download
Pull request Compare This branch is 218 commits behind Azure:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
100-Blank-Template
101-acsengine-docker-swarm
101-acsengine-docker-swarmmode
101-availabilityset-multiplevm-create
101-create-dnszones
101-create-nsg
101-create-storage-account
101-create-vnet-full
101-create-vnet-nsg-only
101-create-vnet-only
101-mysqladapter-add-hosting-server
101-mysqladapter-create-database
101-sqladapter-add-hosting-server
101-sqladapter-create-database
101-vm-apply-extension-multiple
101-vm-create-from-customimage
101-vm-linux-apply-extension-customscript
101-vm-linux-apply-extension-docker
101-vm-linux-apply-extension-vmaccess
101-vm-linux-create
101-vm-windows-apply-extension-bginfo
101-vm-windows-apply-extension-customscript-cmd
101-vm-windows-apply-extension-customscript-pscmd
101-vm-windows-apply-extension-customscript-sf
101-vm-windows-create-with-extension-diagnostic
101-vm-windows-create
101-vm-windows-createmultiple
101-vm-windowsandlinux-createmultiple
101-vmss-linux-vm
101-vmss-windows-vm
201-vm-linux-comprehensive
201-vm-ubuntu-apply-extension-ospatching
201-vm-windows-comprehensive
201-vmss-linux-existing-vnet
201-vmss-linux-extension
201-vmss-linux-vm-largescale
201-vmss-scalein-scaleout-existing
201-vmss-windows-customimage
201-vmss-windows-extension
201-vmss-windows-vm-largescale
MicrosoftMonitoringAgent-ext-win
ad-join-domain-ext-win
ad-non-ha
anti-malware-ext-win
bootstorm-vm-boot-time
docker-swarm-ubuntu
exchange-2016-non-ha
iostorm-vm-iops-latency
jetstress-2013-exchange-loadtest
mesos-windows-jumpbox
mysql-standalone-server-windows
rds-deployment-existing-ad
sharepoint-2013-non-ha-loadtest
sharepoint-2013-non-ha
sharepoint-2013-sample-loadtest
sql-2014-non-ha
sql-2014-standalone
vmaccess-ext-win
vs2013-tcta
README.md
Sample README.md

README.md

Microsoft Azure Stack Quickstart Templates

This repository contains Azure Resource Manager deployment templates that have been tested on Microsoft Azure Stack TP3 Refresh.

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 TP3 Refresh, such as ExpressRoute or CDN.

To ensure the successful deployment of templates to both Microsoft Azure and Microsoft Azure Stack TP3 Refresh, this temporary GitHub repository AzureStack-quickstart-templates was created. This repository contains samples to test your Microsoft Azure Stack TP3 Refresh 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.

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 TP3 Refresh

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 TP3 Refresh, you must be aware of a couple of limitations related to Azure Resource Manager in the Microsoft Azure Stack TP3 Refresh. Some functions of Azure Resource Manager are not yet available in this Technical Preview release of Microsoft Azure Stack.

The following template functions are not available in Microsoft Azure Stack Technical Preview yet.

  • skip
  • take

API Versions for Resource Providers

Each resource provider in Microsoft Azure has its own API version. Microsoft Azure Stack TP3 Refresh 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 TP3 Refresh, use the latest API versions that are available in Microsoft Azure Stack TP3 Refresh for all resources in your template. To retrieve a list of the available API versions connect to your Microsoft Azure Stack TP3 Refresh 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 TP3 Refresh.

Next steps

Start with creating deployment templates in your own repository. Make sure they deploy to both Microsoft Azure and Microsoft Azure Stack TP3 Refresh, 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.

You can’t perform that action at this time.