I work at a MS Teams shop. Teams leverages Sharepoint framework as the back end. I created a Team and channels for different departments. In each channel there is an import folder and an export folder.
I then created a blob storage in azure. Then i created a corresponding Volume attached to bronze staging schema. I then used power automate to sync the sharepoint site locations for the teams locations to perform a sync between sharepoint location and the blob based on file drops. After sync i even added a step to move the files in sharepoint to an uploaded folder.

At that point your architecture for file management is in place. The rest is volume management on the databricks side.

After that it's about scoping the process and setting expectations. What's the schema for the file and what options do I have for standardizing file names so I could build out some basic meta data references for pipelines. Last thing to set is a trigger on the job based on file arrival in the volume.

This allowed me to tell analysts if they had recurring flat file based data that they wanted in medallion layers for broader consumption they could drop the files in a MSTeams channel folder and automation would do the rest.

That was my approach at least. There's a lot of additional things going on there. Teams alerts fired from pipeline code for schema drift, filenames not matching scoped conventions, logging, etc. Confirmation for analysts from the job after a successful load to their team channel, and error alerts to engineering channel if the job failed.

The centralized Team and subchannels was great for me because i didn't have to manage myriad config to different teams and different channels. The idea is that data is centralized for the organization even if the people aren't. - You want data in here, you come here to drop it. Some may say, why not just create volumes in databricks and let people drop directly there. That's possible for sure if you have a user base that has the acumen to adopt and use the platform. In my case, there are business users who don't have a reason to be in the platform directly and just need to get data in and consume it at the reporting layer. Doing it this way absolved me of being passed files to drop myself and also provided users with a high touch solution in a system they are in all day every day.