Using custom security policies

To help secure your systems and environment, Azure Security Center generates security recommendations. These recommendations are based on industry best practices, which are incorporated into the generic, default security policy supplied to all customers. They can also come from Security Center's knowledge of industry and regulatory standards.

With this feature, you can add your own custom initiatives. You'll then receive recommendations if your environment doesn't follow the policies you create. Any custom initiatives you create will appear alongside the built-in initiatives in the regulatory compliance dashboard, as described in the tutorial Improve your regulatory compliance.

As discussed in the Azure Policy documentation, when you specify a location for your custom initiative, it must be a management group or a subscription.

To add a custom initiative to your subscription

  1. From Security Center's sidebar, open the Security policy page.

  2. Select a subscription or Management Group to which you would like to add a custom initiative.

    Selecting a subscription for which you'll create your custom policy


    You must add custom standards at the subscription level (or higher) for them to be evaluated and displayed in Security Center.

    When you add a custom standard, it assigns an initiative to that scope. We therefore recommend that you select the widest scope required for that assignment.

  3. In the Security policy page, under Your custom initiatives, click Add a custom initiative.

    Click Add a custom initiative

    The following page appears:

    Create or add a policy

  4. In the Add custom initiatives page, review the list of custom policies already created in your organization. If you see one you want to assign to your subscription, click Add. If there isn't an initiative in the list that meets your needs, skip this step.

  5. To create a new custom initiative:

    1. Click Create new.
    2. Enter the definition's location and name.
    3. Select the policies to include and click Add.
    4. Enter any desired parameters.
    5. Click Save.
    6. In the Add custom initiatives page, click refresh. Your new initiative will be shown as available.
    7. Click Add and assign it to your subscription.


    Creating new initiatives requires subscription owner credentials. For more information about Azure roles, see Permissions in Azure Security Center.

    Your new initiative takes effect and you can see the impact in the following two ways:

    • From the Security Center sidebar, under Policy & Compliance, select Regulatory compliance. The compliance dashboard opens to show your new custom initiative alongside the built-in initiatives.

    • You'll begin to receive recommendations if your environment doesn't follow the policies you've defined.

  6. To see the resulting recommendations for your policy, click Recommendations from the sidebar to open the recommendations page. The recommendations will appear with a "Custom" label and be available within approximately one hour.

    Custom recommendations

Enhancing your custom recommendations with detailed information

The built-in recommendations supplied with Azure Security Center include details such as severity levels and remediation instructions. If you want to add this type of information to your custom recommendations so that it appears in the Azure portal or wherever you access your recommendations, you'll need to use the REST API.

The two types of information you can add are:

  • RemediationDescription – String
  • Severity – Enum [Low, Medium, High]

The metadata should be added to the policy definition for a policy that is part of the custom initiative. It should be in the ‘securityCenter’ property, as shown:

 "metadata": {
	"securityCenter": {
		"RemediationDescription": "Custom description goes here",
		"Severity": "High",

Below is an example of a custom policy including the metadata/securityCenter property:

"properties": {
	"displayName": "Security - ERvNet - AuditRGLock",
	"policyType": "Custom",
	"mode": "All",
	"description": "Audit required resource groups lock",
	"metadata": {
		"securityCenter": {
			"remediationDescription": "Resource Group locks can be set via Azure Portal -> Resource Group -> Locks",
			"severity": "High"
	"parameters": {
		"expressRouteLockLevel": {
			"type": "String",
			"metadata": {
				"displayName": "Lock level",
				"description": "Required lock level for ExpressRoute resource groups."
			"allowedValues": [
	"policyRule": {
		"if": {
			"field": "type",
			"equals": "Microsoft.Resources/subscriptions/resourceGroups"
		"then": {
			"effect": "auditIfNotExists",
			"details": {
				"type": "Microsoft.Authorization/locks",
				"existenceCondition": {
					"field": "Microsoft.Authorization/locks/level",
					"equals": "[parameters('expressRouteLockLevel')]"

For another example of using the securityCenter property, see this section of the REST API documentation.

Next steps

In this article, you learned how to create custom security policies.

For other related material, see the following articles: