diff --git a/content/en/data_observability/quality_monitoring/data_warehouses/snowflake.md b/content/en/data_observability/quality_monitoring/data_warehouses/snowflake.md
index f6995f1258f..1b68d13e59a 100644
--- a/content/en/data_observability/quality_monitoring/data_warehouses/snowflake.md
+++ b/content/en/data_observability/quality_monitoring/data_warehouses/snowflake.md
@@ -161,7 +161,21 @@ To configure the Snowflake integration in Datadog:
 
 3. Follow the flow to enter your account details and upload a private key.
 4. Turn on {{< ui >}}Enable Data Observability for Snowflake tables{{< /ui >}}.
-5. Click {{< ui >}}Save & Test{{< /ui >}}.
+5. (Optional) Under {{< ui >}}Custom alias URLs{{< /ui >}}, register any additional names other tools use to reference this Snowflake account. Examples include the account identifier configured in dbt, the connection string used by a BI tool, or an AWS PrivateLink URL. See [Custom alias URLs](#custom-alias-urls) below for when this is needed.
+6. Click {{< ui >}}Save & Test{{< /ui >}}.
+
+### Custom alias URLs
+
+This field is optional. Use it when the Snowflake account name Datadog connects to does not match how other tools reference the same account.
+
+Lineage events from outside Datadog include OpenLineage emitters, dbt manifests, and query history from other tools. These events identify the warehouse using whatever name the upstream tool was configured with. If those names differ from the canonical account URL Datadog uses, lineage from those sources is not stitched to this Snowflake integration.
+
+Registering each alternative name as a {{< ui >}}Custom alias URL{{< /ui >}} tells Datadog to treat them as references to the same Snowflake account. Cross-tool lineage then resolves correctly. Common cases include:
+
+- The account is reached through an AWS PrivateLink URL.
+- A dbt project, BI tool, or other connector is configured with an account identifier that does not match the canonical URL.
+
+To add an alias, expand {{< ui >}}Configure Data Observability{{< /ui >}} during integration setup and click {{< ui >}}+ Add Alias{{< /ui >}} under {{< ui >}}Custom alias URLs{{< /ui >}}. Add one entry per alternative name. Aliases apply only to the Snowflake account being configured; each Snowflake integration manages its own alias list.
 
 ## Snowflake tasks and Snowpipes