diff --git a/config/_default/menus/main.en.yaml b/config/_default/menus/main.en.yaml
index 97bb1b1efbf..498a60e4206 100644
--- a/config/_default/menus/main.en.yaml
+++ b/config/_default/menus/main.en.yaml
@@ -560,16 +560,21 @@ menu:
url: agent/fleet_automation/configure_agents
parent: agent_fleet_automation
weight: 802
+ - name: Configure Agent Integrations
+ identifier: configure_integrations
+ url: agent/fleet_automation/configure_integrations
+ parent: agent_fleet_automation
+ weight: 803
- name: Upgrade Agents
identifier: upgrade_agents
url: agent/fleet_automation/upgrade_agents
parent: agent_fleet_automation
- weight: 803
+ weight: 804
- name: Upgrade SDKs
identifier: upgrade_sdks
url: agent/fleet_automation/upgrade_sdks
parent: agent_fleet_automation
- weight: 804
+ weight: 805
- name: Troubleshooting
url: agent/troubleshooting/
parent: agent
diff --git a/content/en/agent/fleet_automation/configure_integrations.md b/content/en/agent/fleet_automation/configure_integrations.md
new file mode 100644
index 00000000000..27422553087
--- /dev/null
+++ b/content/en/agent/fleet_automation/configure_integrations.md
@@ -0,0 +1,81 @@
+---
+title: Configure Agent Integrations
+description: "Remotely configure Datadog Agent integrations at scale with Fleet Automation."
+further_reading:
+- link: "/agent/fleet_automation/"
+ tag: "Documentation"
+ text: "Fleet Automation"
+- link: "/agent/fleet_automation/configure_agents/"
+ tag: "Documentation"
+ text: "Configure Agents"
+- link: "/api/latest/fleet-automation/"
+ tag: "Documentation"
+ text: "Fleet Automation API"
+---
+
+{{< callout btn_hidden="true" header="Join the Preview!" >}}
+Remote integration configuration is in Preview.
+{{< /callout >}}
+
+Fleet Automation can deploy, update, and remove [integration][1] configuration files (`conf.d`) on your Agents remotely. Select target Agents by host or tag, choose an integration, and Fleet Automation pushes the configuration change across your fleet.
+
+## Prerequisites
+
+- [Remote Configuration][2] enabled for your organization
+- Agent version 7.76 or later
+- Linux VMs (installed with the install script or the Ansible Datadog Role) or Windows VMs
+
+
+Configuring integrations on Agents in containerized workloads is not supported.
+
+
+## Compatibility
+
+Fleet Automation supports configuring out-of-the-box integrations that have a `conf.d` configuration file, such as Redis, MySQL, and Windows Certificate Store.
+
+Custom checks are **not** supported.
+
+## Configure integrations across multiple Agents
+
+1. In Fleet Automation, open the [{{< ui >}}Configuration{{< /ui >}}][3] tab and click {{< ui >}}Configure Agents{{< /ui >}}.
+1. Scope the configuration to the target Agents. Filter by host information or tags to target a specific group.
+1. Choose {{< ui >}}Agent integrations{{< /ui >}}.
+1. Select the integration to configure.
+
+ Fleet Automation can detect unconfigured integrations on your hosts. If a process is running on a host that has an available Datadog integration but no active configuration, it appears in the list of Unconfigured integrations detected on your hosts. Use this to identify monitoring gaps across your fleet.
+
+1. Select an operation (see [How configuration changes are applied](#how-configuration-changes-are-applied) for more information about each operation):
+
+ - {{< ui >}}Add New{{< /ui >}}. Specify the filename for the new configuration file, and fill in the configuration as prompted.
+ - {{< ui >}}Edit & Replace{{< /ui >}}. Click {{< ui >}}Select a file{{< /ui >}} and choose the configuration file you want to replace, then fill in the new configuration as prompted.
+ - {{< ui >}}Delete{{< /ui >}}. Click {{< ui >}}Select a File to Delete{{< /ui >}} and (tk).
+
+ Toggle between Visual and YAML mode when filling out the integration configuration. Use YAML mode to paste in YAML directly.
+
+1. Review the deployment plan. Fleet Automation generates a configuration diff for each affected Agent so you can verify the exact changes.
+1. Click {{< ui >}}Deploy Configuration{{< /ui >}} to start the deployment. Track progress from the [Deployments page][4].
+
+## How configuration changes are applied
+
+Each operation applies changes to the integration's `conf.d` configuration file differently:
+
+- {{< ui >}}Add New{{< /ui >}}: Deploys a new integration configuration file. If a configuration file already exists, it is replaced entirely and the YAML you provide becomes the complete new configuration for that integration on the target Agents.
+
+- {{< ui >}}Edit & Replace{{< /ui >}}: Applies a targeted change using JSON Merge Patch ([RFC 7386][5]). Only the fields you specify are modified; unmentioned fields remain unchanged.
+
+
+ Array fields (such as tags) are fully replaced during an Edit & Replace, not merged. Include all desired values in your update. Any values you omit are removed.
+
+
+- {{< ui >}}Delete{{< /ui >}}: Removes the integration configuration file from the target Agents.
+
+
+## Further Reading
+
+{{< partial name="whats-next/whats-next.html" >}}
+
+[1]: /integrations/
+[2]: /agent/guide/setup_remote_config
+[3]: https://app.datadoghq.com/fleet/agent-management
+[4]: https://app.datadoghq.com/fleet/deployments
+[5]: https://www.rfc-editor.org/rfc/rfc7386