diff --git a/src/_data/sidenav/main.yml b/src/_data/sidenav/main.yml
index e9e78a13e8..e4d6d4a93a 100644
--- a/src/_data/sidenav/main.yml
+++ b/src/_data/sidenav/main.yml
@@ -81,8 +81,6 @@ sections:
       title: 'Spec: Screen'
     - path: /connections/spec/track
       title: 'Spec: Track'
-    - path: /connections/spec/alias
-      title: 'Spec: Alias'
     - path: /connections/spec/group
       title: 'Spec: Group'
     - path: /connections/spec/identify
diff --git a/src/connections/spec/alias.md b/src/connections/spec/alias.md
index 8a3d00421e..dbe5cfbe09 100644
--- a/src/connections/spec/alias.md
+++ b/src/connections/spec/alias.md
@@ -2,6 +2,8 @@
 title: 'Spec: Alias'
 ---
 
+> note "Alias is an advanced method"
+> The Alias method allows you to explicitly change the ID of a tracked user, however this should only be done when it's required for downstream destination compatibility. See our [Best Practices for Identifying Users](/docs/guides/how-to-guides/best-practices-identify/) for more information. 
 
 The `alias` method is used to merge two user identities, effectively connecting two sets of user data as one. This is an advanced method, but it is required to manage user identities successfully in some of our destinations.