![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(140.8, 35%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESS%3C/text%3E%3C/svg%3E)
Azure Functions
An Azure service that provides an event-driven serverless compute platform.
4,953 questions
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(256, 32%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMT%3C/text%3E%3C/svg%3E)
That is really dependent upon the plan you're using. See here.
If you're passing the file as a payload to the function app then it won't work because the max reqwest size for an app is 100 MB irrelevant of the plan. If you're downloading the file within the function app then you have between 1 and 4 GB of memory to play with so you should be able to load the file but that relies on having contiguous memory if you're loading it into an array. If you're using a stream then it can be streamed straight to the file share. However note the storage size limits for each plan. This is for all functions running in the same plan. If you have only a single instance running then that would be fine but if you have several function apps running (because of scaling perhaps) then you may reach the limit pretty quickly.
Without more information about your function app configuration and how it is loading those files then it is hard to tell where things might go wrong.