azure_disallowed_regions

Azure Disallowed Regions

What It Does

This policy finds all Azure virtual machines within a user-specified list of disallowed regions or outside of a user-specified list of allowed regions. An incident is raised and a report emailed containing all of the non-compliant instances, with the option to power off or delete offending instances.

Input Parameters

• Email Addresses - Email addresses of the recipients you wish to notify when new incidents are created.
• Azure Endpoint - The endpoint to send Azure API requests to. Recommended to leave this at default unless using this policy with Azure China.
• Exclusion Tags (Key:Value) - Cloud native tags to ignore resources that you don't want to produce recommendations for. Use Key:Value format for specific tag key/value pairs, and Key:* format to match any resource with a particular key, regardless of value. Examples: env:production, DO_NOT_DELETE:*
• Allow/Deny Subscriptions - Determines whether the Allow/Deny Subscriptions List parameter functions as an allow list (only providing results for the listed subscriptions) or a deny list (providing results for all subscriptions except for the listed subscriptions).
• Allow/Deny Subscriptions List - A list of allowed or denied Subscription IDs/names. If empty, no filtering will occur and recommendations will be produced for all subscriptions.
• Disallow/Allow Regions - Whether to allow or disallow the regions specified in the Disallow/Allow Regions List parameter. If set to "Allow", all virtual machines outside of the listed regions will be considered out of compliance. If set to "Disallow", all virtual machines within the listed regions will be considered out of compliance.
• Disallow/Allow Regions List - A list of regions to disallow or allow. Example: eastus
• Automatic Actions - When this value is set, this policy will automatically take the selected action(s).
• Power Off Type - Whether to perform a graceful shutdown or a forced shutdown when powering off idle instances. Only applicable when taking action against instances.

Please note that the "Automatic Actions" parameter contains a list of action(s) that can be performed on the resources. When it is selected, the policy will automatically execute the corresponding action on the data that failed the checks, post incident generation. Please leave it blank for manual action. For example if a user selects the "Delete Instances" action while applying the policy, all the resources that didn't satisfy the policy condition will be deleted.

Policy Actions

• Sends an email notification
• Power off virtual machines after approval
• Delete virtual machines after approval

Prerequisites

This Policy Template uses Credentials for authenticating to datasources -- in order to apply this policy you must have a Credential registered in the system that is compatible with this policy. If there are no Credentials listed when you apply the policy, please contact your Flexera Org Admin and ask them to register a Credential that is compatible with this policy. The information below should be consulted when creating the credential(s).

• Azure Resource Manager Credential (provider=azure_rm) which has the following permissions:

  • Microsoft.Compute/virtualMachines/read
  • Microsoft.Compute/virtualMachines/write*

  * Only required for taking action; the policy will still function in a read-only capacity without these permissions.

• Flexera Credential (provider=flexera) which has the following roles:

  • billing_center_viewer

The Provider-Specific Credentials page in the docs has detailed instructions for setting up Credentials for the most common providers.

Supported Clouds

• Azure

Cost

This policy template does not incur any cloud costs.