@Derek Saffie Adding more information to the above response
By design FNS does not have a concept of a "folder". When you create a blob with path "A/B/c.txt" there are no folders "A" and "A/B" that exists in the backend, only a blob with name "A/B/c.txt" exists. But when this is viewed on the portal due to "/" being considered as a path seperator, portal shows "A" and "A/B" as directories. This is just visualization and not physical.
Blobfuse is a file-system driver and using this user can create a new folder (which is empty in nature). FNS account does not support any such concept of empty folder and to overcome that Blobfuse creates a stub file (0 byte blob) with the folder name and has a special meta property set to identify it as a folder. This is an extra file with the same name and 0 byte in size is what you see while the actual folder displayed on the portal is just visualization and does not exists physically. Without the stub file blobfuse can not create directories in FNS.
Please let us know if you have any further queries. I’m happy to assist you further.
Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.