---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Create a cloud policy

# Create a cloud policy {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read

A cloud policy can override a property value set by a user, create an approval task, reserve an IP address, pre-populate or hide form fields, execute custom scripts, call the Cloud API, or start or abort workflows. A cloud policy gives you system-wide control over approvals, resource operations, blueprint operations, or catalog item settings.{#create-cloud-policy__shortdesc-cloud-policy}

## Before you begin

* Optional: Create one or more cloud policy groups.
* Role required: sn_cmp.cloud_governor or admin{#create-cloud-policy__ph-governororadmin-role}
{#create-cloud-policy__ul_ixb_cb5_dz}

## About this task

This procedure describes every policy type except approval policies (on Blueprint provision (approval), on Stack operation (approval), on Stack resource operation (approval), and on Task remediation). See [Create a cloud approval policy](https://servicenow-prod.fluidtopics.net/~U5h1yoiRffyUTchCyMzLg "A cloud approval policy specifies the users who must approve a specified cloud activity before the activity can proceed. Approvers can include the manager of the user making a request, a specified user or group, or users with a specified role. You can specify multiple approvers. Approvals occur in the order that you specify.") for instructions on creating a policy with an approval trigger.

## Procedure

1. In the Cloud Admin Portal, navigate to GovernPolicies.
2. Click New and then fill in the form.  
   Figure 1. Example policy form {#create-cloud-policy__table_zk1_ctq_fz__entry__2}

   | Field | Description |
   |-|-|
   | Policy Name | A descriptive name that includes the word <kbd class="ph userinput">Policy</kbd>. Do not start the name with a number. |
   | Description | A description of the intent of the policy. |
   | Policy Group | A policy group to which the policy belongs. |
   | Policy Trigger | A trigger that specifies when the policy should be applied. For example, the on Lease end trigger applies the policy when the lease for a stack ends. See [Triggers for cloud policies](https://servicenow-prod.fluidtopics.net/2PTRHMz7DhA5yrcIym7RVg "Triggers are events that set the policy engine in motion. For example, the on Catalog item request end trigger fires after a user submits a request form. When the trigger for a policy fires, the policy engine tests the conditions specified in the policy rule and performs the actions specified in the rule, if the conditions are met."). |
   | Resource Block \[appears when the on Resource Operation trigger is selected\] | The resource block that the policy applies to. |
   | Operation \[appears when the on Blueprint provision, on Blueprint provision (approval) or on Resource Operation trigger is selected\] | Select the operation that the policy applies to. For example, a policy can apply to the Deprovision operation only or to all operations on the blueprint or catalog item. Note: If no operation is specified, then the policy applies for every operation. This condition can decrease performance. * All: Any operation executes. * Start: The resource starts. * Stop: The resource stops. * Provision: The resource is provisioned. * Deprovision: The resource is no longer available to users. * Execute Script: A script runs on the resource. {#create-cloud-policy__ul_vsk_nfb_qfb} |
   | Moment \[appears when the on Resource Operation trigger is selected\] | Specify when the policy should be enforced: * Pre-operation: Before the specified operation starts. * Post-operation: After the specified operation finishes. {#create-cloud-policy__ul_dz4_btc_lfb} Note: If you are integrating with Infoblox, use Pre-operation for a vSphere virtual machine. Use Post-operation for AWS and Azure clouds because AWS and Azure control the allocation of IP addresses. You can register the IP address that is provided with Infoblox. |
   | Catalog item \[appears when an on Catalog item launch, on Catalog item request start, or on Catalog item request end trigger is selected\] | Select the catalog item that the policy applies to. |
   | Start Date / End Date | Specify the start date when the policy should be considered and the end date when the policy should no longer be considered. |
   | Order of Execution | Specify a number that represents the order in which the policy is applied. A policy with a lower number runs before a policy with a higher number. For example, a policy with Order of 100 runs before a policy with an Order of 200. Note: The Order of Execution property does not apply for on Blueprint provision (approval), on Stack operation (approval), on Stack resource operation (approval), and on Task remediation policies. See [Create a cloud approval policy](https://servicenow-prod.fluidtopics.net/~U5h1yoiRffyUTchCyMzLg "A cloud approval policy specifies the users who must approve a specified cloud activity before the activity can proceed. Approvers can include the manager of the user making a request, a specified user or group, or users with a specified role. You can specify multiple approvers. Approvals occur in the order that you specify.") for details. |
   | Status | * Published policies are enforced. You cannot edit a policy in the Published state. To edit a policy that is in the Published state, click Draft on the form header. * You can edit Draft policies. Draft policies are not enforced. To enforce a policy, click Publish on the form header. {#create-cloud-policy__ul_x2h_swc_lfb} |
   [ ]

   {#create-cloud-policy__table_zk1_ctq_fz}
3. Right-click in the header and select Save.

## What to do next

[Configure a cloud policy
rule](https://servicenow-prod.fluidtopics.net/qic_pvAYLBJcRcfDVquKmA "A policy rule is a collection of conditions and actions. ​If all conditions evaluate to true, the policy engine performs the actions. If any condition evaluates to false, the policy engine does not perform the actions.") for the policy.
* **[Configure a cloud policy rule](https://servicenow-prod.fluidtopics.net/qic_pvAYLBJcRcfDVquKmA)**   
  A policy rule is a collection of conditions and actions. If all conditions evaluate to true, the policy engine performs the actions. If any condition evaluates to false, the policy engine does not perform the actions.
* **[Using expressions in Cloud Provisioning and Governance](https://servicenow-prod.fluidtopics.net/bDD2kSim8mCSXROFliQ_kw)**   
  Expressions in policy actions can set or override values. Expressions in blueprints can access attributes of resources and can map values to request form fields. Expressions are available in resource blocks, blueprints, policies, and anywhere that Cloud Provisioning and Governance allows scripts.
* **[Create an action for an 'on Blueprint provision' policy](https://servicenow-prod.fluidtopics.net/kpynPE6Hy~6sQhiDy8FMLA)**   
  The on Blueprint provision trigger fires after execution of on Catalog item request start policies. A policy that is triggered by the on Blueprint provision trigger can run a script, override a user-requested attribute value, or abort and send a message about the provision operation.
* **[Create an action for an 'approval' policy](https://servicenow-prod.fluidtopics.net/540yGPA12ygL4Misvt4FSA)**   
  A policy that is triggered by one of the approval triggers can start approval workflows. The approval triggers are ( on Blueprint provision (approval), on Stack operation (approval), on Stack resource operation (approval), and on Task remediation .
* **[Create an action for an 'on Catalog item launch' policy](https://servicenow-prod.fluidtopics.net/vU3X37xLgmPaSHALEWXH9g)**   
  The on Catalog item launch trigger fires when an order form (stack request form) is launched for a catalog item. A policy that is triggered by the on Catalog item launch trigger can run a script or override a user-requested value (text values only).
* **[Create an action for an 'on Catalog item request start/end' policy](https://servicenow-prod.fluidtopics.net/Us2T~OhSx7TINETcyk7Mzw)**   
  The on Catalog item request start trigger fires after the user opens a request form. The on Catalog item request end trigger fires after a user submits a request form. A policy that is triggered by the on Catalog item request start or on Catalog item request end trigger can run a script or execute a workflow.
* **[Create an action for an 'on Lease end' policy](https://servicenow-prod.fluidtopics.net/8uAnuR2mofXYtgmnI14uMw)**   
  A policy that is triggered by the on Lease end trigger can send a notification or perform a Start, Stop, or Deprovision life cycle operation.
* **[Create an action for an 'on Resource operation' policy](https://servicenow-prod.fluidtopics.net/phXj~4FLAOndGewF8yGljA)**   
  The on Resource operation trigger fires during the Orchestration process when a user performs a Start, Stop, or Deprovision life cycle operation on a specific resource. A policy that is triggered by the on Resource operation trigger can override a user-requested attribute value, run a script, call a Cloud API, or perform an IP address management operation.
* **[Create an action for an 'on Resource operation launch' policy](https://servicenow-prod.fluidtopics.net/Bd49PKqU7YbIfVY2nIddNQ)**   
  The on Resource operation launch trigger fires before the catalog for a resource operation is loaded from the Cloud User Portal. A policy that is triggered by the on Resource operation launch trigger can run a script or can override a user-requested value (text values only).
* **[Create an action for an 'on Resource operation request start/end' policy](https://servicenow-prod.fluidtopics.net/QKlTQv_9jsGW3V3wKmw5XA)**   
  A policy that is triggered by the on Resource operation request start or on Resource operation request end trigger can run a script or override a user-requested attribute value.
* **[Create an action for an 'on Resource Limit exceeded' policy](https://servicenow-prod.fluidtopics.net/b~BaC80NfGWOfg23q57z5g)**   
  Set the on Resource limits exceeded policy to automatically run approval workflows or send notifications when an order form is submitted for a template-based catalog item that exceeds the defined resource limit or quota values.
* **[Create an action for an 'on Task Remediation' policy](https://servicenow-prod.fluidtopics.net/nlG~2HsmcRyWq1aALuJucQ)**   
  The on Task remediation trigger fires when a user resubmits a failed request. A policy that is triggered by the on Task Remediation trigger can start approval workflows.
* **[Create a policy action script](https://servicenow-prod.fluidtopics.net/HJokDoCw~8BcEZtW_W13Zw)**   
  Use policy action scripts to get, update, or set values in cloud requests.
* **[Example policy action script that tags resources](https://servicenow-prod.fluidtopics.net/cpwpOqvsWTtrt2TihEgmSw)**   
  Your instance tracks tagged resources for billing and reporting. Policy action scripts can add and modify resource tags. This example tags a storage volume resource.

*[\>]: and then