Internal Load Balancer Failure Affects All Container App Environments

[StianSaeten]

This issue is a: (mark with an x)

• [x] bug report -> please search issues before submitting
• [ ] documentation issue or request
• [ ] regression (a behavior that used to work and stopped in a new release)

Issue description

It appears that all of our Container App Environments are currently inaccessible, and we've identified a recurring error across all 13 environments. This issue has persisted since last night and affects environments spread across 13 different subscriptions. The containers themselves are operational, but we're unable to access them.

The image below is from resource health on one of the internal LB

No alterations were made to any of the environments transitioning them from a functional to non-functional state.

All environments are running with VNET integration.

Support ticket created with ticket id 2405100050000405 

Steps to reproduce

1. This issue began yesterday and persists unresolved.

Expected behavior [What you expected to happen.] Able to access the containers

Actual behavior [What actually happened.] Unable to connect

Screenshots

Additional context

Ex. Did this issue occur in the CLI or the Portal?

[StianSaeten]

Issue was a new health probe introduced in the latest update, measures taken.