Skip to content

Instantly share code, notes, and snippets.

@russcam

russcam/Custom-probe-matching-conditions.md

Last active July 17, 2018 02:30
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save russcam/9dae8b88e6238fd069ef3d24308ffbe5 to your computer and use it in GitHub Desktop.
Save russcam/9dae8b88e6238fd069ef3d24308ffbe5 to your computer and use it in GitHub Desktop.
Download ZIP
Azure Portal Custom Probe matching conditions
Raw
Custom-probe-matching-conditions.md

When a custom probe is specified in an Azure Resource Manager template that includes custom matching status codes to consider the backend pool as healthy, the Custom probe matching checkbox in the portal remains unchecked; when checked, the status codes defined in the ARM template do not appear in the portal UI, although it does appear that Application Gateway is using the provided status codes.

Here's an example of the match condition for a probe in a template:

"match": {
    "statusCodes": ["200-399", "401"]
}

Resource Explorer reflects this

"match": {
	"body": "",
	"statusCodes": [
	  "200-399",
	  "401"
	]
},

but the portal UI shows as per attached image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment