Merge pull request #308208 from shanhix1/shannon/removeversionpreview

prmerger-automator[bot] · web-flow · commit 7d02d0af9f62 · 2026-01-08T17:48:22.000Z
Removing areas in docs that refer to versioning as preview
diff --git a/articles/governance/policy/assign-policy-portal.md b/articles/governance/policy/assign-policy-portal.md
@@ -40,7 +40,7 @@ In this quickstart, you create a policy assignment with a built-in policy defini
    | **Resource selectors** | Skip resource selectors for this example. Resource selectors let you refine the resources affected by the policy assignment. |
    | **Policy definition** | Select the ellipsis (`...`) to open the list of available definitions. |
    | **Available Definitions** | Search the policy definitions list for _Audit VMs that do not use managed disks_ definition, select the policy, and select **Add**. There's a column that shows the latest version of the definition. |
-   | **Version (preview)** | Accept the version in format `1.*.*` to ingest major, minor, and patch versions. <br/><br/> Select the ellipsis (`...`) to view available versions and the options to enroll in minor version updates or preview versions. You must select a version to change the options. For more information, go to [definition version within assignment](./concepts/assignment-structure.md#policy-definition-id-and-version-preview). |
+   | **Version (preview)** | Accept the version in format `1.*.*` to ingest major, minor, and patch versions. <br/><br/> Select the ellipsis (`...`) to view available versions and the options to enroll in minor version updates or preview versions. You must select a version to change the options. For more information, go to [definition version within assignment](./concepts/assignment-structure.md#policy-definition-id-and-version). |
    | **Assignment name** | By default uses the name of the selected policy. You can change it but for this example, use the default name. |
    | **Description** | Optional to provide details about this policy assignment. |
    | **Policy enforcement** | Defaults to _Enabled_. For more information, go to [enforcement mode](./concepts/assignment-structure.md#enforcement-mode). |
diff --git a/articles/governance/policy/concepts/assignment-structure.md b/articles/governance/policy/concepts/assignment-structure.md
@@ -12,7 +12,7 @@ Policy assignments define which resources are evaluated by a policy definition o
 You use JavaScript Object Notation (JSON) to create a policy assignment. The policy assignment contains elements for:
 
 - [scope](#scope)
-- [policy definition ID and version](#policy-definition-id-and-version-preview)
+- [policy definition ID and version](#policy-definition-id-and-version)
 - [display name](#display-name-and-description)
 - [description](#display-name-and-description)
 - [metadata](#metadata)
@@ -68,7 +68,7 @@ For example, the following JSON shows a sample policy assignment request in _DoN
 
 The scope used for assignment resource creation time is the primary driver of resource applicability. For more information on assignment scope, see [Understand scope in Azure Policy](./scope.md#assignment-scopes).
 
-## Policy definition ID and version (preview)
+## Policy definition ID and version
 
 This field must be the full path name of either a policy definition or an initiative definition. The `policyDefinitionId` is a string and not an array. The latest content of the assigned policy definition or initiative is retrieved each time the policy assignment is evaluated. The recommendation is that if multiple policies are often assigned together, to use an [initiative](./initiative-definition-structure.md) instead.
 
diff --git a/articles/governance/policy/concepts/definition-structure-basics.md b/articles/governance/policy/concepts/definition-structure-basics.md
@@ -124,9 +124,9 @@ When Azure Policy versioning is released, the following Resource Provider modes
 - `Microsoft.MachineLearningServices.v2.Data`
 - `Microsoft.ManagedHSM.Data`
 
-## Version (preview)
+## Version
 
-Built-in policy definitions 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 definitions 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)
 
 The Azure Policy service uses `version`, `preview`, and `deprecated` properties to convey state and level of change to a built-in policy definition or initiative. The format of `version` is: `{Major}.{Minor}.{Patch}`. When a policy definition is in preview state, the suffix _preview_ is appended to the `version` property and treated as a **boolean**. When a policy definition is deprecated, the deprecation is captured as a boolean in the definition's metadata using `"deprecated": "true"`.
 
diff --git a/articles/governance/policy/concepts/initiative-definition-structure.md b/articles/governance/policy/concepts/initiative-definition-structure.md
@@ -125,8 +125,8 @@ there are some _common_ properties used by Azure Policy and in built-ins.
 - `deprecated` (boolean): True or false flag for if the policy initiative definition has been marked
   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)
+## Version
+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)
 
 The Azure Policy service uses `version`, `preview`, and `deprecated` properties to convey state and level of change to a built-in policy definition or initiative. The format of `version` is: `{Major}.{Minor}.{Patch}`. When a policy definition is in preview state, the suffix _preview_ is appended to the `version` property and treated as a **boolean**. When a policy definition is deprecated, the deprecation is captured as a boolean in the definition's metadata using `"deprecated": "true"`.
 
@@ -136,12 +136,7 @@ The Azure Policy service uses `version`, `preview`, and `deprecated` properties
 
 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
-> 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).
+For more information about Azure Policy versions for 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).
 
 ## Parameters
 
@@ -272,7 +267,7 @@ Each _array_ element that represents a policy definition has the following prope
 - `parameters`: (Optional) The name/value pairs for passing an initiative parameter to the
   included policy definition as a property in that policy definition. For more information, see
   [Parameters](#parameters).
-- `definitionVersion` : (Optional) The version of the built-in definition to refer to. If none is specified, it refers to the latest major version at assignment time and autoingest any minor updates. For more information, see [definition version](./definition-structure-basics.md#version-preview)
+- `definitionVersion` : (Optional) The version of the built-in definition to refer to. If none is specified, it refers to the latest major version at assignment time and autoingest any minor updates. For more information, see [definition version](./definition-structure-basics.md#version)
 - `groupNames` (array of strings): (Optional) The group the policy definition is a member of. For
   more information, see [Policy groups](#policy-definition-groups).
 
diff --git a/articles/governance/policy/how-to/extension-for-vscode.md b/articles/governance/policy/how-to/extension-for-vscode.md
@@ -188,7 +188,7 @@ schema.
 
 > [!NOTE]
 > The VS Code extension will only show the latest version of the policy definition. For more
-> information about the versions of definitions, see the [definitions](../concepts/definition-structure-basics.md#version-preview).
+> information about the versions of definitions, see the [definitions](../concepts/definition-structure-basics.md#version).
 
 ### Export objects
 
diff --git a/articles/governance/policy/policy-glossary.md b/articles/governance/policy/policy-glossary.md
@@ -131,7 +131,7 @@ Describes the aggregated compliance state of a policy assignment.
 
 ## Policy versioning
 
-Built-in policy definitions can host multiple versions with the same `definitionID`. For more information, see [Version](./concepts/definition-structure-basics.md#version-preview).
+Built-in policy definitions can host multiple versions with the same `definitionID`. For more information, see [Version](./concepts/definition-structure-basics.md#version).
 
 ## Regulatory Compliance
 
