[Fleet] Update references to subscription requirements

reference/fleet/agent-policy.md

@@ -100,7 +100,7 @@ To add a new integration to one or more {{agent}} policies:
 6. In Step 2 on the page, you have two options:
 
     1. If you’d like to create a new policy for your {{agent}}s, on the **New hosts** tab specify a name for the new agent policy and choose whether or not to collect system logs and metrics. Collecting logs and metrics will add the System integration to the new agent policy.
-    2. If you already have an {{agent}} policy created, on the **Existing hosts** tab use the drop-down menu to specify one or more agent policies that you’d like to add the integration to. Note that this feature, known as "reusable integration policies" is only available for specific subscription levels. For more information, refer to [{{stack}} subscriptions](https://www.elastic.co/subscriptions).
+    2. If you already have an {{agent}} policy created, on the **Existing hosts** tab use the drop-down menu to specify one or more agent policies that you’d like to add the integration to. Note that this feature, known as **reusable integration policies**, is only available for certain subscription levels. For more information, refer to [{{stack}} subscriptions](https://www.elastic.co/subscriptions).
 
 7. Click **Save and continue** to confirm your settings.
 
@@ -132,7 +132,7 @@ You can apply policies to one or more {{agent}}s. To apply a policy:
     :screenshot:
     :::
 
-    Unable to select multiple agents? Confirm that your subscription level supports selective agent policy reassignment in {{fleet}}. For more information, refer to [{{stack}} subscriptions](https://www.elastic.co/subscriptions).
+    Unable to select multiple agents? Confirm that your subscription level supports **selective agent policy reassignment** in {{fleet}}. For more information, refer to [{{stack}} subscriptions](https://www.elastic.co/subscriptions).
 
 3. Select the {{agent}} policy from the dropdown list, and click **Assign policy**.
 
@@ -272,19 +272,19 @@ stack: ga 9.1.0
 For a high-scale deployment of {{fleet}}, you can configure an automatic, gradual rollout of a new minor or patch version to a percentage of the {{agents}} in your policy. For more information, refer to [Auto-upgrade agents enrolled in a policy](/reference/fleet/upgrade-elastic-agent.md#auto-upgrade-agents).
 
 ::::{note}
-This feature is only available for certain subscription levels. For more information, refer to [{{stack}} subscriptions](https://www.elastic.co/subscriptions).
+This feature is only available for certain subscription levels. For more information, check **Automatic agent binary upgrades** on the [{{stack}} subscriptions](https://www.elastic.co/subscriptions) page.
 ::::
 
 
 ## Change the output of a policy [change-policy-output]
 
-Assuming your [{{stack}} subscription level](https://www.elastic.co/subscriptions) supports per-policy outputs, you can change the output of a policy to send data to a different output.
+Assuming your [{{stack}} subscription level](https://www.elastic.co/subscriptions) supports **per policy output assignment**, you can change the output of a policy to send data to a different output.
 
 1. In {{fleet}}, click **Settings** and view the list of available outputs. If necessary, click **Add output** to add a new output with the settings you require. For more information, refer to [Output settings](/reference/fleet/fleet-settings.md#output-settings).
 2. Click **Agent policies**. Click the name of the policy you want to change, then click **Settings**.
 3. Set **Output for integrations** and (optionally) **Output for agent monitoring** to use a different output, for example, {{ls}}. You might need to scroll down to see these options.
 
-    Unable to select a different output? Confirm that your subscription level supports per-policy outputs in {{fleet}}.
+    Unable to select a different output? Confirm that your subscription level supports **per policy output assignment** in {{fleet}}.
 
     :::{image} images/agent-output-settings.png
     :alt: Screen capture showing the {{ls}} output policy selected in an agent policy

reference/fleet/automatic-integrations-synchronization.md

@@ -17,7 +17,7 @@ products:
 When enabled, this feature keeps integrations and custom assets synchronized between your main {{es}} cluster and one or more remote {{es}} clusters. 
 
 ::::{note}
-Automatic integrations synchronization is only available with certain subscriptions. For more information, refer to [Subscriptions](https://www.elastic.co/subscriptions).
+This feature is only available for certain subscription levels. For more information, check **Fleet Multi-Cluster support** on the [{{stack}} subscriptions](https://www.elastic.co/subscriptions) page.
 ::::
 
 ## Requirements

reference/fleet/data-streams-advanced-features.md

@@ -15,7 +15,7 @@ products:
 * [Time series data streams (TSDS)](/manage-data/data-store/data-streams/time-series-data-stream-tsds.md)
 * [Synthetic `_source`](elasticsearch://reference/elasticsearch/mapping-reference/mapping-source-field.md#synthetic-source)
 
-These features can be enabled and disabled for {{fleet}}-managed data streams by using the index template API and a few key settings. Note that in versions 8.17.0 and later, Synthetic `_source` requires an Enterprise license.
+These features can be enabled and disabled for {{fleet}}-managed data streams by using the index template API and a few key settings. Note that in versions 8.17.0 and later, synthetic `_source` is only available for certain [{{stack}} subscription levels](https://www.elastic.co/subscriptions).
 
 ::::{note}
 If you are already making use of `@custom` component templates for ingest or retention customization (as shown for example in [Tutorial: Customize data retention policies](/reference/fleet/data-streams-ilm-tutorial.md)), exercise care to ensure you don’t overwrite your customizations when making these requests.

reference/fleet/fleet-settings.md

@@ -65,7 +65,7 @@ When a {{fleet-server}} is added or removed from the list, all agent policies ar
 Add or edit output settings to specify where {{agent}}s send data. {{agent}}s use the default output if you don’t select an output in the agent policy.
 
 ::::{tip}
-If you have an `Enterprise` [{{stack}} subscription](https://www.elastic.co/subscriptions), you can configure {{agent}} to [send data to different outputs for different integration policies](/reference/fleet/integration-level-outputs.md).
+If your [{{stack}} subscription level](https://www.elastic.co/subscriptions) supports **per integration output assignment**, you can configure {{agent}} to [send data to different outputs for different integration policies](/reference/fleet/integration-level-outputs.md).
 ::::
 
 

reference/fleet/index.md

@@ -109,7 +109,7 @@ When you're ready to upgrade your {{agent}} binaries or integrations, you can in
 
 Some subscription levels support bulk select operations, including:
 
-* Selective binary updates
+* Selective agent binary updates
 * Selective agent policy reassignment
 * Selective agent unenrollment
 

reference/fleet/integration-level-outputs.md

@@ -8,7 +8,7 @@ products:
 
 # Set integration-level outputs [integration-level-outputs]
 
-If you have an `Enterprise` [{{stack}} subscription](https://www.elastic.co/subscriptions), you can configure {{agent}} data to be sent to different outputs for different integration policies. Note that the output clusters that you send data to must also be on the same subscription level.
+If your [{{stack}} subscription level](https://www.elastic.co/subscriptions) supports **per integration output assignment**, you can configure {{agent}} data to be sent to different outputs for different integration policies. Note that the output clusters that you send data to must also be on the same subscription level.
 
 Integration-level outputs are very useful for certain scenarios. For example:
 

reference/fleet/remote-elasticsearch-output.md

@@ -77,7 +77,7 @@ To prevent unauthorized access, the {{es}} Service Token is stored as a secret v
 Choose whether integrations should be automatically synchronized on the remote {{es}} cluster. To configure this feature, refer to [Automatic integrations synchronization](/reference/fleet/automatic-integrations-synchronization.md).
 
 :::{note}
-Automatic integrations synchronization is only available with certain subscriptions. For more information, refer to [Subscriptions](https://www.elastic.co/subscriptions).
+Automatic integrations synchronization is only available for certain subscription levels. For more information, check **Fleet Multi-Cluster support** on the [{{stack}} subscriptions](https://www.elastic.co/subscriptions) page.
 :::
 ::::
 

reference/fleet/unenroll-elastic-agent.md

@@ -14,7 +14,7 @@ You can unenroll {{agent}}s to invalidate the API key used to connect to {{es}}.
 2. To unenroll a single agent, choose **Unenroll agent** from the **Actions** menu next to the agent you want to unenroll.
 3. To unenroll multiple agents, bulk select the agents and click **Unenroll agents**.
 
-    Unable to select multiple agents? Confirm that your subscription level supports selective agent unenrollment in {{fleet}}. For more information, refer to [{{stack}} subscriptions](https://www.elastic.co/subscriptions).
+    Unable to select multiple agents? Confirm that your subscription level supports **selective agent unenrollment** in {{fleet}}. For more information, refer to [{{stack}} subscriptions](https://www.elastic.co/subscriptions).
 
 
 Unenrolled agents will continue to run, but will not be able to send data. They will show this error instead: `invalid api key to authenticate with fleet`.

reference/fleet/upgrade-elastic-agent.md

@@ -57,7 +57,7 @@ To upgrade your {{agents}}, go to **Management** → **{{fleet}}** → **Agents*
 | [Restart an upgrade for a single agent](#restart-upgrade-single) | Restart an upgrade process that has stalled for a single agent. |
 | [Restart an upgrade for multiple agents](#restart-upgrade-multiple) | Do a bulk restart of the upgrade process for a set of agents. |
 
-With the right [subscription level](https://www.elastic.co/subscriptions), you can also configure an automatic, gradual upgrade of a percentage of the {{agents}} enrolled in an {{agent}} policy. For more information, refer to [Auto-upgrade agents enrolled in a policy](#auto-upgrade-agents). {applies_to}`stack: ga 9.1.0`
+With an [{{stack}} subscription level](https://www.elastic.co/subscriptions) that supports **automatic agent binary upgrades**, you can also configure an automatic upgrade of a percentage of the {{agents}} enrolled in an {{agent}} policy. For more information, refer to [Auto-upgrade agents enrolled in a policy](#auto-upgrade-agents). {applies_to}`stack: ga 9.1.0`
 
 
 ## Upgrade a single {{agent}} [upgrade-an-agent]
@@ -105,6 +105,10 @@ Note that agents in a rollout period have the status `Updating` until the upgrad
 
 ## Schedule an upgrade [schedule-agent-upgrade]
 
+::::{note}
+This feature is only available for certain subscription levels. For more information, check **Scheduled agent binary upgrades** on the [{{stack}} subscriptions](https://www.elastic.co/subscriptions) page.
+::::
+
 1. On the **Agents** tab, select one or more agents, and click **Actions**.
 2. From the **Actions** menu, choose to schedule an upgrade.
 
@@ -113,8 +117,6 @@ Note that agents in a rollout period have the status `Updating` until the upgrad
     :screenshot:
     :::
 
-    If the schedule option is grayed out, it may not be available at your subscription level. For more information, refer to [{{stack}} subscriptions](https://www.elastic.co/subscriptions).
-
 3. In the Upgrade window, select an upgrade version.
 4. Select a maintenance window. For more information, refer to [Do a rolling upgrade of multiple {{agent}}s](#rolling-agent-upgrade).
 5. Set the date and time when you want the upgrade to begin.
@@ -227,7 +229,7 @@ stack: ga 9.1.0
 ```
 
 ::::{note}
-This feature is only available for certain subscription levels. For more information, refer to [{{stack}} subscriptions](https://www.elastic.co/subscriptions).
+This feature is only available for certain subscription levels. For more information, check **Automatic agent binary upgrades** on the [{{stack}} subscriptions](https://www.elastic.co/subscriptions) page.
 ::::
 
 To configure an automatic rollout of a new minor or patch version to a percentage of the agents enrolled in your {{agent}} policy. follow these steps: