Merge pull request #280954 from duongau/afdorigin

Front Door -  Origin (add note about disabled origin)

Author: prmerger-automator[bot]

articles/frontdoor/how-to-configure-origin.md

@@ -6,7 +6,7 @@ services: frontdoor
 author: duongau
 ms.service: frontdoor
 ms.topic: how-to
-ms.date: 06/06/2023
+ms.date: 07/16/2024
 ms.author: duau
 ---
 
@@ -54,8 +54,8 @@ Before you can create an Azure Front Door origin, you must have an Azure Front D
     * **Status** - Select this option to enable the origin.
 
     > [!IMPORTANT]
-    > During configuration, the Azure portal doesn't validate if the origin is accessible from Azure Front Door environments. You need to verify that Azure Front Door can reach your origin.
-    >
+    > * During configuration, the Azure portal doesn't validate if the origin is accessible from Azure Front Door environments. You need to verify that Azure Front Door can reach your origin.
+    > * When an origin is **disabled**, both routing and health probes to the origin are also disabled.
 
 1. Select **Add** once you have completed the origin settings. The origin should now appear in the origin group. 
 

articles/frontdoor/origin.md

@@ -50,6 +50,9 @@ An origin refers to the application deployment that Azure Front Door retrieves c
 
 * **Weight**. Assign weights to your different backends to distribute traffic across a set of backends, either evenly or according to weight coefficients. For more information, see [Weights](routing-methods.md#weighted).
 
+> [!IMPORTANT]
+> When an origin is **disabled**, both routing and health probes to the origin are also disabled.
+
 ### Origin host header
 
 Requests that get forwarded by Azure Front Door to an origin include a host header field that the origin uses to retrieve the targeted resource. The value for this field typically comes from the origin URI that has the host header and port.