Nothing you've suggested has worked so in the end I used a different file storage and that has started working properly. It worries me that we've only just moved to Azure and we're getting these sorts of anomalies where a second setup is configured exactly the same as another and they behave differently and the only way to fix it that I've found is to start again.
Web app path mappings for one app service doesn't work whereas others configured the same do
I have a few app services, each have an Azure File Storage mounted, and then virtual directories mapped to that mount. This is working fine in two UK setups, works on my original Canadian service, but I'm now adding a second app in Canada, pointing to the same file storage and its not working.
I can log into the new app service and navigate to c:\mounts{store} and can see the files fine, but when I try to use a web browser or postman to get one of these files it comes back with 404 "The resource you are looking for has been removed, had its name changed, or is temporarily unavailable."
As far as I can see the config for all apps are the same, they all run the same code.