What the troubleshooter can tell you
Microsoft’s Apps on Azure team says v2 discovers dependencies and presents recommended next steps when it finds a problem. The Ignite technical roundup describes a dependency graph that can include Storage, Service Bus, Key Vault, Azure Files, and monitoring endpoints, with failing checks shown first. That’s useful when a timeout leaves you wondering which service to investigate, let alone whether to start with DNS, a firewall rule, or the app’s identity. Microsoft’s examples include a Service Bus dependency and a storage file-volume check, not an exhaustive list of supported scenarios.
- Dedicated, Elastic Premium, and Windows Consumption: Microsoft lists live connectivity testing alongside DNS, TCP, firewall, and role-based access control (RBAC) checks. Those results help distinguish a connection that never reaches its destination from a configuration or permissions issue.
- Flex Consumption: The preview reads Azure Resource Manager and other control-plane settings. It checks the app’s virtual network and DNS configuration, destination firewalls, private endpoints, network security groups, private DNS zone links, and the managed identity’s role assignments. Microsoft says full in-app connectivity testing is planned for a future update. A clean configuration check does not establish that the running app reached the service.
The Windows Consumption detail is worth calling out for teams with older runbooks. Microsoft Learn excludes both Windows and Linux Consumption from its separately documented Network validator tool. That older exclusion doesn’t describe v2: Microsoft explicitly names Windows Consumption among the plans that get live checks in the new preview.
Where to start in the Azure portal
- Open the affected Function App and go to Diagnose and solve problems → Network Troubleshooter. Alternatively, open the app’s Networking page and select Troubleshoot in the top bar.
- Start the analysis and look for the dependency that matches the symptom. Review the failing check and its recommended action before changing a firewall rule or granting a role. A recommendation is a lead to investigate, not confirmation that it’s the only fault.
- On Flex Consumption, pair the configuration results with runtime telemetry if Application Insights is enabled. Microsoft Learn recommends starting there for DNS errors and dependency timeouts. In Logs, look at
dependenciesfor failed outbound calls around the time of the incident, then compare them withexceptionsandtracesfor details the app or host recorded.
V2 is still an evaluation tool, not a generally available replacement for an incident runbook. The practical gain is a shorter route to the right question: did Azure find a configuration problem, or did the app actually fail to reach its dependency? On Flex Consumption, the portal preview helps answer the first question; runtime evidence is still needed for the second.
References
- (In preview) Public Preview: Azure Functions Network Troubleshooter v2 Azure Updates · 2026-11-17T20:00:32Z
- Azure Functions Network Troubleshooter and Connectivity Checks | Microsoft Community Hub techcommunity.microsoft.com
- Troubleshoot Azure Functions app down or reporting errors - Azure | Microsoft Learn learn.microsoft.com