Allow disabling health probes in front door origin group

[AdamJachocki]

Related command
az afd origin-group create

Is your feature request related to a problem? Please describe.
No

Describe the solution you'd like
I would like to have the possibility to create origin group without health probes enabled.

Describe alternatives you've considered
There is no alternative. After I create origin group using azure cli, I eventually need to login to azure portal and then disable health probes manually.

Additional context
When you use a service like ngrok that has limited number of requests per minute, health probes exhaust this limit quite fast. Althought timing is set to 240 seconds, for some reason health probes calls the backend constantly (when backend is not fully functional yet, and that's the big problem).

[yonzhan]

route to CXP team

[navba-MSFT]

@AdamJachocki Thanks for reaching out to us and reporting this issue. Could you please try running the below command instead as a workaround ?

az resource create -g myRG -n myApiApp --resource-type Microsoft.Cdn/profiles/origingroups --is-full-object --properties @jsonConfigFile

You can place the below content within your jsonConfigFile:

{
  "properties": {
    "loadBalancingSettings": {
      "sampleSize": 3,
      "successfulSamplesRequired": 3,
      "additionalLatencyInMilliseconds": 1000
    },
    "trafficRestorationTimeToHealedOrNewEndpointsInMinutes": 5
  }
}

This will not create the probe settings. Hope this helps.

[navba-MSFT]

@AdamJachocki I wanted to do quick follow-up to check if you had a chance to look at my above comment. Please let us know if you had any updates on this. Awaiting your reply.

[AdamJachocki]

Your workaround is for websites, not front door

[navba-MSFT]

@AdamJachocki My Bad. I didn't edit the command. I have edited my above comment and resending it again:

az resource create -g myRG -n myApiApp --resource-type Microsoft.Cdn/profiles/origingroups --is-full-object --properties @jsonConfigFile

You can place the below content within your jsonConfigFile:

{
  "properties": {
    "loadBalancingSettings": {
      "sampleSize": 3,
      "successfulSamplesRequired": 3,
      "additionalLatencyInMilliseconds": 1000
    },
    "trafficRestorationTimeToHealedOrNewEndpointsInMinutes": 5
  }
}

This will not create the probe settings. More info here. Hope this helps.

[navba-MSFT]

@AdamJachocki Please let me know if you had a chance to look into this.

[AdamJachocki]

Now I get the error: "location of the resource is required"

[navba-MSFT]

@AdamJachocki Pass the --location parameter too in the above command. I didn't have to use it because I have set the default configuration for the location in my box.

Parameter: --location -l
Location. Values from: az account list-locations. You can configure the default location using az configure --defaults location=<location>.

[AdamJachocki]

When I do: "--location ukwest" it gives me the same error. Nevermind if the location value is in quotes or not.

[navba-MSFT]

@AdamJachocki Apologies for the late reply. I was able to get this working with the below Az CLI command. Could you please test the same and let me know if that helps ?

az rest --method PUT --url https://management.azure.com/subscriptions/{SUB-id}/resourceGroups/{RgName}/providers/Microsoft.Cdn/profiles/{MyFrontDoorName}/originGroups/{MyOriginName}?api-version=2021-06-01 --body @jsonConfigFile.json --debug

Contents of jsonConfigFile.json

{
   "properties":
    {
      "loadBalancingSettings": {
      "sampleSize": 3,
      "successfulSamplesRequired": 3,
      "additionalLatencyInMilliseconds": 1000
    },
    "trafficRestorationTimeToHealedOrNewEndpointsInMinutes": 5
   }
}

[navba-MSFT]

@AdamJachocki I wanted to do quick follow-up to check if you had a chance to try the above workaround. Please let us know if you had any updates on this. Awaiting your reply.

[navba-MSFT]

@AdamJachocki The action is currently pending on you to try the above suggestion. If you need any further assistance on this issue in future, please feel free to reopen this thread. We would be happy to help.