S3 storage block flow run can't see mapped network drive while local storage flow run

I am running a prefect agent on an internal Windows Server 2016 machine. When running a particular flow that depends on access to a mapped network drive, downloading from local storage on the box itself executes without issue. When I think deploy using an s3 storage block, it suddenly doesn’t seem to be able to access the mapped drive and fails to write files out to the share.

If the code is just downloaded locally to the execution environment and run from there, why would that be?

Is there some way around this issue?