complete adding policy alert

Author: dlepow

articles/api-management/api-management-access-restriction-policies.md

@@ -158,6 +158,8 @@ This policy can be used in the following policy [sections](./api-management-howt
 
 The `rate-limit-by-key` policy prevents API usage spikes on a per key basis by limiting the call rate to a specified number per a specified time period. The key can have an arbitrary string value and is typically provided using a policy expression. Optional increment condition can be added to specify which requests should be counted towards the limit. When this call rate is exceeded, the caller receives a `429 Too Many Requests` response status code.
 
+[!INCLUDE [api-management-policy-form-alert](../../includes/api-management-policy-form-alert.md)]
+
 For more information and examples of this policy, see [Advanced request throttling with Azure API Management](./api-management-sample-flexible-throttling.md).
 
 > [!CAUTION]
@@ -231,6 +233,8 @@ This policy can be used in the following policy [sections](./api-management-howt
 
 The `ip-filter` policy filters (allows/denies) calls from specific IP addresses and/or address ranges.
 
+[!INCLUDE [api-management-policy-form-alert](../../includes/api-management-policy-form-alert.md)]
+
 ### Policy statement
 
 ```xml
@@ -345,6 +349,9 @@ For more information and examples of this policy, see [Advanced request throttli
 > [!NOTE]
 > To understand the difference between rate limits and quotas, [see Rate limits and quotas.](./api-management-sample-flexible-throttling.md#rate-limits-and-quotas)
 
+[!INCLUDE [api-management-policy-form-alert](../../includes/api-management-policy-form-alert.md)]
+
+
 ### Policy statement
 
 ```xml
@@ -410,6 +417,9 @@ The `validate-jwt` policy enforces existence and validity of a JSON web token (J
 > The `validate-jwt` policy supports HS256 and RS256 signing algorithms. For HS256 the key must be provided inline within the policy in the base64 encoded form. For RS256 the key may be provided either via an Open ID configuration endpoint, or by providing the ID of an uploaded certificate that contains the public key or modulus-exponent pair of the public key.
 > The `validate-jwt` policy supports tokens encrypted with symmetric keys using the following encryption algorithms: A128CBC-HS256, A192CBC-HS384, A256CBC-HS512.
 
+[!INCLUDE [api-management-policy-form-alert](../../includes/api-management-policy-form-alert.md)]
+
+
 ### Policy statement
 
 ```xml

articles/api-management/validation-policies.md

@@ -64,6 +64,8 @@ We recommend performing load tests with your expected production workloads to as
 
 The `validate-content` policy validates the size or content of a request or response body against one or more [supported schemas](#schemas-for-content-validation).
 
+[!INCLUDE [api-management-policy-form-alert](../../includes/api-management-policy-form-alert.md)]
+
 The following table shows the schema formats and request or response content types that the policy supports. Content type values are case insensitive.
 
 | Format  | Content types | 
@@ -180,6 +182,8 @@ The `validate-parameters` policy validates the header, query, or path parameters
 > [!IMPORTANT]
 > If you imported an API using a management API version prior to `2021-01-01-preview`, the `validate-parameters` policy might not work. You may need to [reimport your API](/rest/api/apimanagement/current-ga/apis/create-or-update) using management API version `2021-01-01-preview` or later.
 
+[!INCLUDE [api-management-policy-form-alert](../../includes/api-management-policy-form-alert.md)]
+
 
 ### Policy statement
 
@@ -247,6 +251,9 @@ The `validate-headers` policy validates the response headers against the API sch
 > [!IMPORTANT]
 > If you imported an API using a management API version prior to `2021-01-01-preview`, the `validate-headers` policy might not work. You may need to reimport your API using management API version `2021-01-01-preview` or later.
 
+[!INCLUDE [api-management-policy-form-alert](../../includes/api-management-policy-form-alert.md)]
+
+
 ### Policy statement
 
 ```xml
@@ -287,7 +294,9 @@ This policy can be used in the following policy [sections](./api-management-howt
 
 ## Validate status code
 
-The `validate-status-code` policy validates the HTTP status codes in responses against the API schema. This policy may be used to prevent leakage of backend errors, which can contain stack traces. 
+The `validate-status-code` policy validates the HTTP status codes in responses against the API schema. This policy may be used to prevent leakage of backend errors, which can contain stack traces.
+
+[!INCLUDE [api-management-policy-form-alert](../../includes/api-management-policy-form-alert.md)] 
 
 ### Policy statement
 

includes/api-management-policy-form-alert.md

@@ -6,4 +6,4 @@ ms.date: 03/14/2022
 ms.author: danlep
 ---
 > [!TIP]
-> To help configure this policy, the portal provides a guided, form-based editor. Learn more about [policy configuration options](../articles/api-management/set-edit-policies.md#configure-policy-in-the-portal).	
+> To help you configure this policy, the portal provides a guided, form-based editor. Learn more about [policy configuration options](../articles/api-management/set-edit-policies.md#configure-policy-in-the-portal).