updates rest api links

davidsmatlak · davidsmatlak · commit 53f114f778f6 · 2024-08-20T08:14:11.000-07:00
diff --git a/articles/governance/policy/assign-policy-rest-api.md b/articles/governance/policy/assign-policy-rest-api.md
@@ -23,7 +23,7 @@ This guide uses REST API to create a policy assignment and to identify non-compl
 
 ## Review the REST API syntax
 
-There are two elements to run REST API commands: the REST API URI and the request body. For information, go to [Policy Assignments - Create](/rest/api/policy/policy-assignments/create).
+There are two elements to run REST API commands: the REST API URI and the request body. For information, go to [Policy Assignments - Create](/rest/api/policyauthorization/policy-assignments/create).
 
 The following example shows the REST API URI syntax to create a policy definition.
 
@@ -105,7 +105,7 @@ az rest --method put --uri https://management.azure.com/subscriptions/{subscript
 
 In PowerShell, the backtick (``` ` ```) is needed to escape the `at sign` (`@`) to specify a filename. In a Bash shell like Git Bash, omit the backtick.
 
-For information, go to [Policy Assignments - Create](/rest/api/policy/policy-assignments/create).
+For information, go to [Policy Assignments - Create](/rest/api/policyauthorization/policy-assignments/create).
 
 ## Identify non-compliant resources
 
@@ -168,7 +168,7 @@ Your results resemble the following example:
 }
 ```
 
-For more information, go to [Policy States - List Query Results For Resource Group](/rest/api/policy/policy-states/list-query-results-for-resource-group).
+For more information, go to [Policy States - List Query Results For Resource Group](/rest/api/policyinsights/policy-states/list-query-results-for-resource-group).
 
 ## Clean up resources
 
@@ -188,7 +188,7 @@ az rest --method get --uri https://management.azure.com/subscriptions/{subscript
 The policy assignment 'audit-vm-managed-disks' is not found.
 ```
 
-For more information, go to [Policy Assignments - Delete](/rest/api/policy/policy-assignments/delete) and [Policy Assignments - Get](/rest/api/policy/policy-assignments/get).
+For more information, go to [Policy Assignments - Delete](/rest/api/policyauthorization/policy-assignments/delete) and [Policy Assignments - Get](/rest/api/policyauthorization/policy-assignments/get).
 
 ## Next steps
 
diff --git a/articles/governance/policy/concepts/attestation-structure.md b/articles/governance/policy/concepts/attestation-structure.md
@@ -10,7 +10,7 @@ ms.topic: conceptual
 Attestations are used by Azure Policy to set compliance states of resources or scopes targeted by [manual policies](effect-manual.md). They also allow users to provide more metadata or link to evidence that accompanies the attested compliance state.
 
 > [!NOTE]
-> Attestations can be created and managed only through Azure Policy [Azure Resource Manager (ARM) API](/rest/api/policy/attestations), [PowerShell](/powershell/module/az.policyinsights) or [Azure CLI](/cli/azure/policy/attestation).
+> Attestations can be created and managed only through Azure Policy [Azure Resource Manager (ARM) API](/rest/api/policyinsights/attestations), [PowerShell](/powershell/module/az.policyinsights) or [Azure CLI](/cli/azure/policy/attestation).
 
 ## Best practices
 
diff --git a/articles/governance/policy/concepts/initiative-definition-structure.md b/articles/governance/policy/concepts/initiative-definition-structure.md
@@ -113,7 +113,7 @@ there are some _common_ properties used by Azure Policy and in built-ins.
 ### Common metadata properties
 
 - `version` (string): Tracks details about the version of the contents of a policy initiative
-  definition. For built-ins, this metadata version follows the version property of the built-in. It's recommended to use the version property over this metadata version. 
+  definition. For built-ins, this metadata version follows the version property of the built-in. It's recommended to use the version property over this metadata version.
 - `category` (string): Determines under which category in the Azure portal the policy definition is
   displayed.
 
@@ -126,19 +126,19 @@ there are some _common_ properties used by Azure Policy and in built-ins.
   as _deprecated_.
 
 ## Version (preview)
-Built-in policy initiatives can host multiple versions with the same `definitionID`. If no version number is specified, all experiences will show the latest version of the definition. To see a specific version of a built-in, it must be specified in API, SDK or UI. To reference a specific version of a definition within an assignment, see [definition version within assignment](../concepts/assignment-structure.md#policy-definition-id-and-version-preview) 
+Built-in policy initiatives can host multiple versions with the same `definitionID`. If no version number is specified, all experiences will show the latest version of the definition. To see a specific version of a built-in, it must be specified in API, SDK or UI. To reference a specific version of a definition within an assignment, see [definition version within assignment](../concepts/assignment-structure.md#policy-definition-id-and-version-preview)
 
-The Azure Policy service uses `version`, `preview`, and `deprecated` properties to convey the level of change to a built-in policy definition or initiative and state. The format of `version` is: `{Major}.{Minor}.{Patch}`. Specific states, such as _deprecated_ or _preview_, are appended to the `version` property or in another property as a **boolean** as shown in the common metadata properties. 
+The Azure Policy service uses `version`, `preview`, and `deprecated` properties to convey the level of change to a built-in policy definition or initiative and state. The format of `version` is: `{Major}.{Minor}.{Patch}`. Specific states, such as _deprecated_ or _preview_, are appended to the `version` property or in another property as a **boolean** as shown in the common metadata properties.
 
-- Major Version (example: 2.0.0): introduce breaking changes such as major rule logic changes, removing parameters, adding an enforcement effect by default. 
-- Minor Version (example: 2.1.0): introduce changes such as minor rule logic changes, adding new parameter allowed values, change to role definitionIds, adding or removing definitions within an initiative. 
+- Major Version (example: 2.0.0): introduce breaking changes such as major rule logic changes, removing parameters, adding an enforcement effect by default.
+- Minor Version (example: 2.1.0): introduce changes such as minor rule logic changes, adding new parameter allowed values, change to role definitionIds, adding or removing definitions within an initiative.
 - Patch Version (example: 2.1.4): introduce string or metadata changes and break glass security scenarios (rare).
 
 Built-in initiatives are versioned, and specific versions of built-in policy definitions can be referenced within built-in or custom initiatives as well. For more information, see [reference definition and versions](#policy-definition-properties).
 
 > While in preview, when creating an initiative through the portal, you will not be able to specify versions for built-in policy definition references. All built-in policy references in custom initiatives created through the portal will instead default to the latest version of the policy definition.
-> 
-> For more information about 
+>
+> For more information about
 > Azure Policy versions built-ins, see
 > [Built-in versioning](https://github.com/Azure/azure-policy/blob/master/built-in-policies/README.md).
 > To learn more about what it means for a policy to be _deprecated_ or in _preview_, see [Preview and deprecated policies](https://github.com/Azure/azure-policy/blob/master/built-in-policies/README.md#preview-and-deprecated-policies).
@@ -349,7 +349,7 @@ This information is:
 - Displayed in the Azure portal on the overview of a **control** on a Regulatory Compliance
   initiative.
 - Available via REST API. See the `Microsoft.PolicyInsights` resource provider and the
-  [policyMetadata operation group](/rest/api/policy/policymetadata/getresource).
+  [policyMetadata operation group](/rest/api/policyinsights/policy-metadata/get-resource).
 - Available via Azure CLI. See the [az policy metadata](/cli/azure/policy/metadata) command.
 
 > [!IMPORTANT]
@@ -377,7 +377,7 @@ Below is an example of the **policyMetadata** object. This example metadata belo
     "category": "Access Control",
     "title": "Access Control Policy and Procedures",
     "owner": "Shared",
-    "description": "**The organization:**    \na. Develops, documents, and disseminates to [Assignment: organization-defined personnel or roles]:  \n1. An access control policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and  \n2. Procedures to facilitate the implementation of the access control policy and associated access controls; and  \n  
+    "description": "**The organization:**    \na. Develops, documents, and disseminates to [Assignment: organization-defined personnel or roles]:  \n1. An access control policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and  \n2. Procedures to facilitate the implementation of the access control policy and associated access controls; and  \n
 \nb. Reviews and updates the current:  \n1. Access control policy [Assignment: organization-defined frequency]; and  \n2. Access control procedures [Assignment: organization-defined frequency].",
     "requirements": "**a.**  The customer is responsible for developing, documenting, and disseminating access control policies and procedures. The customer access control policies and procedures address access to all customer-deployed resources and customer system access (e.g., access to customer-deployed virtual machines, access to customer-built applications).  \n**b.**  The customer is responsible for reviewing and updating access control policies and procedures in accordance with FedRAMP requirements.",
     "additionalContentUrl": "https://nvd.nist.gov/800-53/Rev4/control/AC-1"
diff --git a/articles/governance/policy/how-to/author-policies-for-arrays.md b/articles/governance/policy/how-to/author-policies-for-arrays.md
@@ -110,7 +110,7 @@ To use this string with each SDK, use the following commands:
   parameter **params**
 - Azure PowerShell: Cmdlet [New-AzPolicyAssignment](/powershell/module/az.resources/New-Azpolicyassignment)
   with parameter **PolicyParameter**
-- REST API: In the _PUT_ [create](/rest/api/policy/policyassignments/create) operation as part of
+- REST API: In the _PUT_ [create](/rest/api/policyauthorization/policy-assignments/create) operation as part of
   the Request Body as the value of the **properties.parameters** property
 
 ## Using arrays in conditions
diff --git a/articles/governance/policy/how-to/get-compliance-data.md b/articles/governance/policy/how-to/get-compliance-data.md
@@ -289,7 +289,7 @@ Use ARMClient or a similar tool to handle authentication to Azure for the REST A
 
 With the REST API, summarization can be performed by container, definition, or assignment. Here's
 an example of summarization at the subscription level using Azure Policy Insight's [Summarize For
-Subscription](/rest/api/policy/policystates/summarizeforsubscription):
+Subscription](/rest/api/policyinsights/policy-states/summarize-for-subscription):
 
 ```http
 POST https://management.azure.com/subscriptions/{subscriptionId}/providers/Microsoft.PolicyInsights/policyStates/latest/summarize?api-version=2019-10-01
@@ -417,7 +417,7 @@ Your results resemble the following example:
 ```
 
 For more information about querying policy events, see the
-[Azure Policy Events](/rest/api/policy/policyevents) reference article.
+[Azure Policy Events](/rest/api/policyinsights/policy-events) reference article.
 
 ### Azure CLI
 
diff --git a/articles/governance/policy/how-to/programmatically-create.md b/articles/governance/policy/how-to/programmatically-create.md
@@ -164,9 +164,9 @@ Use the following procedure to create a policy definition.
    with the ID of your [management group](../../management-groups/overview.md).
 
    For more information about the structure of the query, see
-   [Azure Policy Definitions - Create or Update](/rest/api/policy/policydefinitions/createorupdate)
+   [Azure Policy Definitions - Create or Update](/rest/api/policyauthorization/policy-definitions/create-or-update)
    and
-   [Policy Definitions - Create or Update At Management Group](/rest/api/policy/policydefinitions/createorupdateatmanagementgroup).
+   [Policy Definitions - Create or Update At Management Group](/rest/api/policyauthorization/policy-definitions/create-or-update-at-management-group).
 
 Use the following procedure to create a policy assignment and assign the policy definition at the
 resource group level.
