Merge pull request #293116 from vicancy/patch-22

Update howto-integrate-app-gateway.md

Author: prmerger-automator[bot]

articles/azure-web-pubsub/howto-integrate-app-gateway.md

@@ -70,6 +70,7 @@ When the three components are configured, you should see something like the scre
 
 One thing that is worth highlighting is that you configure **non-WebSocket** connections exactly the same way. You can learn more about [Application Gateway's native support for proxying WebSocket connections](../application-gateway/features.md)
 
+The last thing to update is the backend **health probe**. Select **Settings** -> **Health probes** and select the generated health probe settings, update the **Path** to `/api/health` and keep others unchanged.
 
 ### Test and verify Application Gateway is configured properly
 #### Verify that your Web PubSub resource is healthy
@@ -378,4 +379,4 @@ Now, open your web browser and enter the domain name of your Web App. If you ins
 :::image type="content" source="media/howto-integrate-app-gateway/connect-with-web-pubsub-indirect-azure.jpg" alt-text="Screenshot showing successfully established a WebSocket connection through Application Gateway.":::
 
 If you have the Console panel open, you see the broadcasted messages, as well. 
-:::image type="content" source="media/howto-integrate-app-gateway/connect-with-web-pubsub-indirect-azure-messages.jpg" alt-text="Screenshot showing getting messages from Application Gateway, which proxies traffic for Web PubSub.":::
+:::image type="content" source="media/howto-integrate-app-gateway/connect-with-web-pubsub-indirect-azure-messages.jpg" alt-text="Screenshot showing getting messages from Application Gateway, which proxies traffic for Web PubSub.":::