Based on this old thread, the product team suggests using Mapping Data Flow instead of Copy Activity to overcome this limitation. Data Flow allows you to move thousands of large Excel files to another data store efficiently. It supports streaming reads with minimal CPU and memory usage. Internal performance tests show that Data Flow can transfer a 1GB Excel file within 5 minutes using Azure Integration Runtime with 32 cores.
If you have specific feedback regarding the limitations of Copy Activity for copying large Excel files, please log your feedback on the Azure feedback forum here: Azure Feedback Forum.
Additionally, you can view and upvote an existing feedback request on this issue here: Existing Feedback. Your input will help prioritize this request.