diff --git a/website/source/docs/connect/proxies.html.md b/website/source/docs/connect/proxies.html.md
index cafef535dd..417e8e4efa 100644
--- a/website/source/docs/connect/proxies.html.md
+++ b/website/source/docs/connect/proxies.html.md
@@ -21,6 +21,9 @@ Consul supports both _managed_ and _unmanaged_ proxies. A managed proxy
 is started, configured, and stopped by Consul. An unmanaged proxy is the
 responsibility of the user, like any other Consul service.
 
+~> **Windows Support**: The built-in proxy will not currently run on the Windows platform,
+but compatibility will be added in a future Consul release.
+
 ## Managed Proxies
 
 Managed proxies are started, configured, and stopped by Consul. They are
diff --git a/website/source/intro/getting-started/connect.html.md b/website/source/intro/getting-started/connect.html.md
index a2477b3cfd..3a3ae9e3f8 100644
--- a/website/source/intro/getting-started/connect.html.md
+++ b/website/source/intro/getting-started/connect.html.md
@@ -26,6 +26,9 @@ and focus on ease of use with a dev-mode agent. We will _not setup_ Connect in a
 production-recommended secure way. Please read the Connect reference
 documentation on security best practices to understand the tradeoffs.
 
+~> **Windows Support**: The built-in proxy will not currently run on the Windows platform,
+but compatibility will be added in a future Consul release.
+
 ## Starting a Connect-unaware Service
 
 Let's begin by starting a service that is unaware of Connect all. To