HTTP trigger Function on Private ASE - Code+Test view - 500 Internal Server Error in Portal

**Repo steps:**

1. Create an ASE with a single Windows ASP that has only private VNET access.
2. Deploy an working HTTP-triggered Azure Function (isolated worker, .NET 6, Windows) to it.
3. Navigate to Portal from a **public** computer.
4. Open Function and switch to the Code+Test view and run a Test.
5. Output = "Internal Server Error". No addtional information is displayed or logged to App Insights.

Now, connect to a VM on the Virtual Network the ASE is attached to.

Log into the Azure Portal from a browser on the VM and repeat steps 3-5.

Result = 200 OK, logs sent to App Insights.

**Expected behaviour:**

Both experiences are the same *OR* the public portal shows a message that it is not possible to debug / test from the public Portal due to the private access nature of the underlying ASE.