Merge pull request #276352 from craigshoemaker/swa/issue/fallback

[Static Web Apps] Update: Configuration - add route details on navigationFallback

Author: prmerger-automator[bot]

articles/static-web-apps/configuration.md

@@ -6,7 +6,7 @@ ms.custom: engagement-fy23
 author: craigshoemaker
 ms.service: static-web-apps
 ms.topic: conceptual
-ms.date: 05/17/2024
+ms.date: 05/24/2024
 ms.author: cshoe
 ---
 
@@ -201,6 +201,9 @@ The following example configuration blocks anonymous access and redirects all un
 
 Single Page Applications often rely on client-side routing. These client-side routing rules update the browser's window location without making requests back to the server. If you refresh the page, or go directly to URLs generated by client-side routing rules, a server-side fallback route is required to serve the appropriate HTML page. The fallback page is often designated as _index.html_ for your client-side app.
 
+> [!NOTE]
+> Route rules aren't applied on requests that trigger `navigationFallback`.
+
 You can define a fallback rule by adding a `navigationFallback` section. The following example returns _/index.html_ for all static file requests that don't match a deployed file.
 
 ```json