Skip to content
Collection of Azure Resource Manager (ARM) templates and resources to get started with developing custom resource providers
Branch: master
Clone or download
raosuhas Merge pull request #3 from raosuhas/master
removing artifacts from gitignore
Latest commit 0abd194 May 4, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
CustomRPWithFunction Fix incorrect link in files May 3, 2019
CustomRPWithSwagger removing artifacts from gitignore May 3, 2019
SampleFunctions removing artifacts from gitignore May 3, 2019
.gitignore removing artifacts from gitignore May 3, 2019
LICENSE Initial commit May 3, 2019 Import repo from private May 3, 2019

Developing Custom Providers

Collection of ARM templates and resources to get started with developing custom resource providers in ARM

About Custom Providers

Custom Providers gives publishers in Azure a way to extend azure and azure resources. They allow users to define resources and actions and have them behave as ARM resources and actions allowing features such as ARM template deployment of non-Azure resources, Integration of 3rd party tools and features as part of the template deployment and RBAC on these resources.

The customProviders resource providers also enables users to add actions and resources to managed apps to enable functionality on the managed apps to run programmatic commands on them.


Deploy To Azure

Each template file has an option to deploy to azure in the file present at the the root of the folder

Getting Started

Deploy a custom provider with a simple user resource and a ping action :

The above Custom resource provider is backed by an azure function app. You can read about how to create this function and update it in the following sample. Deploy the function app and understand the requirements for the api that backs the custom provider :

Please check out the othe examples of how you can use custom providers in the Sample functions folder:

It is recommended to supply a swagger spec for custom providers when deploying them. To learm more about swagger and how to incorporate validation for custom providers:


This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact with any additional questions or comments.

You can’t perform that action at this time.