AzureWebJobsStorage secured by Network Security Perimeter - Function unable to start

### Description

When you associate the storage account of an Azure Function with a network security perimeter (nsp) and allow the subscription of the function inbound access to the NSP and you set the mode to enforced your function is unable to start

### Steps to reproduce

1. Create an azure storage account for your function storage
2. Create an azure function, linux, consumption plan. (Runtime version: 4.1042.100.2)
3. Configure the storage account to the function
4. Validate the function works.
5. Create a new Network Security Perimeter
6. Add a profile to the NSP
7. Add an inbound rule for the subscription of the function
8. Associcate the storage account with the NSP, set the mode to Enforced
9. Restart the function
10. Function fails to start (The service is unavailable. when browsing to the function)
11. Set the mode to Learning
12. Restart the function
13. The function works again

_All resources, function, nsp, storage are in the same resource group, in the same subscription in the same region_

Doing the same for a key vault that's being accessed from the same function works.

Since Azure Storage is general available this should work?
https://learn.microsoft.com/en-us/azure/private-link/network-security-perimeter-concepts#scale-limitations