Tell me more about how to identify the impact to our environment, after the retirement of NumberOfProbes in Azure Load Balancer.

@Ernest But IT , Abdul kalam azad S , Welcome to the Microsoft Q&A Platform. Thank you for reaching out & I hope you are doing well. I understand that you would like to know about the impact on deprecation of parameter "numberOfProbes" in Azure Load Balancer. May I ask how was this communicated? Is this done via email? If so, can you share the complete email - Mitigation steps should have been shared here Or did you notice this from an Azure Update Blog post? If so, please share the document link. In either case, The value of "numberOfProbes" was not configurable using Portal and would stick to the default value of "1" I can see the support for this in Azure CLI and Azure Powershell az network lb probe Add-AzLoadBalancerProbeConfig It is defined as "The number of probes where if no response, will result in stopping further traffic from being delivered to the endpoint. This values allows endpoints to be taken out of rotation faster or slower than the typical times used in Azure." While "probeThreshold" is defined as "The number of consecutive successful or failed probes in order to allow or deny traffic from being delivered to this endpoint. After failing the number of consecutive probes equal to this value, the endpoint will be taken out of rotation and require the same number of successful consecutive probes to be placed back in rotation. " You can refer to Microsoft.Network loadBalancers . NOTE : From CLI docs, I could see that the "probeThreshold" is in preview and it is recommended to leave this value to the default "1" Cheers, Kapil

Tell me more about NumberOfProbes in Azure Load Balancer

Accepted answer

KapilAnanth-MSFT 47,206 Reputation points Microsoft Employee

2024-10-04T12:02:51.4633333+00:00
@Ernest But IT , Abdul kalam azad S ,

Welcome to the Microsoft Q&A Platform. Thank you for reaching out & I hope you are doing well.

I understand that you would like to know about the impact on deprecation of parameter "numberOfProbes" in Azure Load Balancer.

May I ask how was this communicated?

Is this done via email?

If so, can you share the complete email - Mitigation steps should have been shared here

Or did you notice this from an Azure Update Blog post?

If so, please share the document link.

In either case,

The value of "numberOfProbes" was not configurable using Portal and would stick to the default value of "1"

I can see the support for this in Azure CLI and Azure Powershell

az network lb probe

Add-AzLoadBalancerProbeConfig

It is defined as "The number of probes where if no response, will result in stopping further traffic from being delivered to the endpoint. This values allows endpoints to be taken out of rotation faster or slower than the typical times used in Azure."

While "probeThreshold" is defined as "The number of consecutive successful or failed probes in order to allow or deny traffic from being delivered to this endpoint. After failing the number of consecutive probes equal to this value, the endpoint will be taken out of rotation and require the same number of successful consecutive probes to be placed back in rotation."

You can refer to Microsoft.Network loadBalancers.

NOTE : From CLI docs, I could see that the "probeThreshold" is in preview and it is recommended to leave this value to the default "1"

Cheers,

Kapil
Please sign in to rate this answer.
Philibilly-1999 0 Reputation points

2024-10-04T15:50:55.5833333+00:00

We received the same notification email

@KapilAnanth-MSFT This was an automated info mail with the subject "Action required: End of Support for Microsoft Azure Load Balancer property NumberOfProbes"

When you search through the internet you find out that previously it was possible to configure an "Unhealthy threshold" in the LB health probe settings (source: https://learn.microsoft.com/en-us/azure/application-gateway/application-gateway-create-probe-portal)

Seems like they already removed that property in the Azure GUI and have set this to 1 for everyone, I confirmed this by using this Azure CLI powershell command:

$slb = Get-AzLoadBalancer -Name "MY-LOADBALANCER" -ResourceGroupName "LB-RESSOURCE-GROUP" Get-AzLoadBalancerProbeConfig -Name "HTTPS-PROBE" -LoadBalancer $slb

And you can see that NumberOfProbes as well as ProbeThreshold is set to 1:

So I think no action is required for most customers, Microsoft just checked if NumberOfProbes is set (which they did for all the customers) and then sent out the notification email to not use this property?!

Somebody from Microsoft correct me if I'm wrong.

Ernest But IT 45 Reputation points

2024-10-07T01:22:42.8733333+00:00

@KapilAnanth-MSFT , here is the email announcement I received:

Support for the Azure Load Balancer property NumberOfProbes is ending

You’re receiving this notice because you’re using the property NumberOfProbes in Azure Load Balancer.

We’ll be ending support for the Azure Load Balancer property NumberOfProbes on 1 September 2027. To avoid service disruption, upgrade your apps and start using the Azure Load Balancer property ProbeThreshold before that date.

Required action

Upgrade your apps to API version 2022-05-01 or higher by 1 September 2027 to begin using the ProbeThreshold property__.__ Refer to our documentation to learn more about updating your API.

Alternatively, simply stop using NumberOfProbes.

Help and support

If you have questions, get answers from community experts in Microsoft Q&A. If you have a support plan and need technical help, open the Azure portal and select the question mark icon at the top of the page.

Learn more about service retirements that may impact your resources in the Azure Retirement Workbook. Please note that retirements may not be visible in the workbook for up to two weeks after being announced.

KapilAnanth-MSFT 47,206 Reputation points Microsoft Employee

2024-10-07T05:51:40.54+00:00

@Ernest But IT , Philibilly-1999 - Thanks for the info.

I am currently discussing this with the internal SMEs from Product Team.

I shall update this thread regarding the next actions for customers if any

Cheers,

Kapil

KapilAnanth-MSFT 47,206 Reputation points Microsoft Employee

2024-10-09T05:19:33.61+00:00

@Ernest But IT , Philibilly-1999 , Derek B Moore,

Here is the update on the retirement email.

As mentioned in Known issues, the "numberOfProbes" property isn't respected.

So the value defined in "numberOfProbes" does not take effect.

If you would like to have a property to control the number of successful or failed consecutive probes necessary to mark backend instances as healthy or unhealthy, please leverage the property "probeThreshold" instead.

You should use API version 2022-05-01 or higher if you would like to use this property.

Wrt "numberOfProbes" - no Action is required from the customers (as this property was never in effect)

@Ernest But IT - I would greatly appreciate if you could Accept the answer and close this thread

Original posters help the community find answers faster by identifying the correct answer.

Thanks,

Kapil

Shubham Prajapati 0 Reputation points

2024-10-09T07:08:10.7766667+00:00

@KapilAnanth-MSFT

so, if i ignore that mail about retirement, there will be no effect on my environment right ?

and also if i want to use that property , how to use that API version is do we have any doc. or something ?

KapilAnanth-MSFT 47,206 Reputation points Microsoft Employee

2024-10-09T08:34:08.5633333+00:00

Shubham Prajapati,

Correct.

You can use the property when you follow the API versions for Terraform, Bicep or ARM as mentioned in this doc : Microsoft.Network loadBalancers.

You can use this directly in Azure CLI and Azure Powershell

az network lb probe

Add-AzLoadBalancerProbeConfig

Cheers,

Kapil
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Tell me more about NumberOfProbes in Azure Load Balancer

0 additional answers

Your answer