Skip to content

Commit a6779ba

Browse files
authored
Update availability-azure-functions.md
Similar to URL and standard tests, customers leveraging the Track Availability must follow the minimum recommendation of 5 locations. Ref: SR 2406130040005859, where our Govt customer questioned why this has not been mentioned on our public doc. so adding a small note that this applies to trackavailability as well
1 parent b09993d commit a6779ba

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

articles/azure-monitor/app/availability-azure-functions.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -26,6 +26,7 @@ Start by reviewing the graph on the **Availability** tab of your Application Ins
2626

2727
> [!NOTE]
2828
> Tests created with `TrackAvailability()` will appear with **CUSTOM** next to the test name.
29+
> Similar to standard web tests, we recommended a minimum of five test locations for TrackAvailability() to ensure you can distinguish problems in your website from network issues.
2930
3031
:::image type="content" source="media/availability-azure-functions/availability-custom.png" alt-text="Screenshot that shows the Availability tab with successful results." lightbox="media/availability-azure-functions/availability-custom.png":::
3132

0 commit comments

Comments
 (0)