Contoso configures an Azure Front Door origin group containing two origins in different regions. They want Front Door to fail over an origin after two consecutive health probe failures. Which health probe settings should they modify in the origin group to meet this requirement?

Azure Front Door uses health probes to monitor the availability of origins. To achieve failover after two consecutive failures, the 'Unhealthy Threshold' setting in the origin group's health probe configuration must be set to 2. This value dictates how many consecutive failed health probes Front Door must receive before marking an origin as unhealthy and initiating failover. The probe interval determines how frequently probes are sent, and the probe path and host ensure the probe targets the correct endpoint. Increasing the probe interval or setting a 'Failover threshold' in the frontend host configuration are incorrect as these settings do not directly control the number of consecutive failures before an origin is marked unhealthy. Custom application-level multicast probes are not an Azure Front Door feature. Relying on weighted routing with two identical origins does not guarantee failover after two consecutive failures without proper health probe configuration.