[Premium] VNET Integration flaps on new Premium app
- Dominant language
- PowerShell
- Stars
- 1.1k
- Forks
- 215
- Avg merge
- 4h 2m
- Merged PRs (30d)
- 1
Description
We find that on
* a brand-new Premium plan
* running a brand-new V2 functions app
the **VNET Integration flaps between working and not-working**, for several hours.
Availability test pictured below, calls an HttpTrigger which:
* Connects to a Storage Account with ACL grant to the function app's subnet
* Connects to a Cosmos DB with same ACL grant
* Connects to a Event Hub with same ACL grant
My impression is that the tests either all succeed, or all fail. Therefore I am suspecting the VNET Integration rather than the 3 x Service Endpoints or 3 x ACLs.
Do you need a repro or is this already a known issue?
A bit of randomness after creation isn't a total blocker, but if it pops up randomly in production, say on scaleout, that's much more serious.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.