diff --git a/aspnetcore/blazor/security/_static/entra-external-id-logout-exception.png b/aspnetcore/blazor/security/_static/entra-external-id-logout-exception.png
new file mode 100644
index 000000000000..3bd8a8b37d1b
Binary files /dev/null and b/aspnetcore/blazor/security/_static/entra-external-id-logout-exception.png differ
diff --git a/aspnetcore/blazor/security/includes/troubleshoot-server.md b/aspnetcore/blazor/security/includes/troubleshoot-server.md
index 756fd0546453..d7ecef25fc7f 100644
--- a/aspnetcore/blazor/security/includes/troubleshoot-server.md
+++ b/aspnetcore/blazor/security/includes/troubleshoot-server.md
@@ -6,6 +6,16 @@ To enable debug or trace logging for Blazor WebAssembly authentication, see the
 
 ### Common errors
 
+* Debugger breaks on an exception during logout with Microsoft Entra External ID
+
+  The following exception stops the Visual Studio debugger during logout with [Microsoft Entra External ID](/entra/external-id/external-identities-overview):
+
+  > :::no-loc text="Uncaught TypeError TypeError: Failed to execute 'postMessage' on 'Window': The provided value cannot be converted to a sequence.":::
+
+  ![Visual Studio Debugger breaking on JavaScript exception during logout](../_static/entra-external-id-logout-exception.png)
+
+  The exception is thrown from Entra JavaScript code, so this isn't a problem with ASP.NET Core. The exception doesn't impact app functionality in production, so the exception can be ignored during local development testing.
+
 * Misconfiguration of the app or Identity Provider (IP)
 
   The most common errors are caused by incorrect configuration. The following are a few examples: