A transfer request includes more than a source filename. It needs an intended destination, permitted actions, a time window and a way to verify the result. An object API and a managed file share also offer different workflows, so choose the interface the application needs.
The fictional vendor and operations scenarios ask you to keep access narrow. A temporary object request isn't a reason to expose a whole account or distribute a permanent key. If a credential is exposed, follow the real rotation and incident process rather than relying on a resource rename. These decisions don't create credentials, issue a live SAS, connect a file share or run an external transfer.
Plan a transfer around access scope and verifiable data.