@Shawn Thanks for reaching out. You can leverage the standard logic app with Build in file system connector/file system for your requirement. To setup the virtual network integration on your standard logic app you can refer to this document.
does the Subnet only affect the inbound traffic or also outbound traffic
Can you please clarify more do you mean inbound and outbound rule or the NSG here?
For your 2nd query I will suggest either to create a new thread with the Azure network tag so it would be easier for others facing the similar issue. I will check internally with the network team if they can share any insights on this.
what should be the subnet address range?
Ideally you should select the max address space that your resource would be scaled up.
Create a standard logic app Select the ASE created in step 3 as a Region when creating the Logic App Trigger - 'when a HTTP request is received' Action - Create a built-in filesystem action (!not a Azure file system connector)
Yes, you need to use the build in action as inbuild connectors can access your resources on the same network.