Skip to content
Branch: master
Find file History
Permalink
Type Name Latest commit message Commit time
..
Failed to load latest commit information.
images Update alias readme (#270) Dec 3, 2018
README.md Fixing broken links and examples (#175) Aug 28, 2018
request-alias.md Update alias readme (#270) Dec 3, 2018
useful-tools.md initial commit for new structure Aug 30, 2017

README.md

Azure Policy samples - Contribution guide

This repository contains all currently available Azure Policy samples contributed by the community. The following information is relevant to get started with contributing to this repository.

Create Policy Definitions and Assignments

Each policy will have instructions for how to create definition, and assign to your preferred scope. The examples will include instructions for Azure portal, PowerShell, and AzureCLI

Contribution guide

To make sure your Azure Policy sample is added to this repository, please follow these guidelines. Any Azure Policy sample that is out of compliance will be added to the blacklist and not be merged.

Files, folders and naming conventions

Every Azure Policy sample and its associated files must be contained in its own folder, into the folder representing the relevant Resource Provider (Compute for VM based policies, Storage for storage based policies etc.) Name this folder something that describes what your policy does. Usually this naming pattern looks like deny-vm-storage-account or allowed-network-locations.

Protip - Try to keep the name of your template folder short so that it fits inside the Github folder name column width.

  • Github uses ASCII for ordering files and folder. For consistent ordering create all files and folders in lowercase. The only exception to this guideline is the README.md, that should be in the format UPPERCASE.lowercase.
  • Include a README.md file that explains how the Azure Policy works, and how to assign it at scope.
  • Guidelines on the README.md file below.
  • An Azure Policy needs to include the following files:
    • azurepolicy.json - The JSON that describes the policy, including parameters and the rules.
    • azurepolicy.rules.json - The JSON that describes the policy rules only.
    • azurepolicy.parameters.json - The JSON that describes the parameters only, for the policy.
    • README.md - Documentation and instruction on how to use the Azure Policy, including Azure CLI/PowerShell samples to create definition and assignment. See more information below.
      • This should include link to Azure portal, that will let you create the assignment directly in Azure.
      • PowerShell/CLI example to create the Policy Definition and Assignment, using the azurepolicy.rules.json and azurepolicy.parameters.json
  • Images used in the README.md must be placed in a folder called images.

alt text

README.md

The README.md describes your policy. A good description helps other community members to understand your deployment. The README.md uses Github Flavored Markdown for formatting text. If you want to add images to your README.md file, store the images in the images folder. Reference the images in the README.md with a relative path (e.g. ![alt text](images/namingConvention.png "Files, folders and naming conventions")). This ensures the link will reference the target repository if the source repository is forked. A good README.md contains the following sections

  • Description of what the Azure Policy will do
  • Link to Microsoft Docs sample page for this policy (*once it exists)
  • Links to deploy with Azure and AzureGov
  • SDK examples (Azure PowerShell, Azure CLI) for creating definition, defining parameters (if any), and assigning
  • *Optional: Prerequisites
  • *Optional: Notes

Example README: Approved VM images - README

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

You can’t perform that action at this time.