Errors Deploying builds using PowerShell

Hello! My team has been setting up for our build machines to automatically upload builds to the PlayFab server using the Powershell API (https://docs.microsoft.com/en-us/gaming/playfab/features/multiplayer/servers/deploy-using-powershell-api). We have successfully uploaded a build, via Powershell, but have run into an error that we're unsure how to solve.

We often get the following error:

New-PfAsset : Exception calling "GetResult" with "0" argument(s): "Error while copying content to a stream."

+ New-PfAsset -FilePath $filePath -AssetName $fileName

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

	+ CategoryInfo          : NotSpecified: (:) [New-PfAsset], MethodInvocationException

	+ FullyQualifiedErrorId : HttpRequestException,New-PfAsset

First we discovered consistently getting the error when uploading full sized builds (~1GB in size) versus test uploads (~200mb and smaller for iteration speed). We discovered that the Windows firewall is at least partially at fault for this error, disabling it made the error go away and uploads to be successful. Later in the evening, with the firewall still disabled, this was tested again and it failed with the same error which has had one of our engineers float the idea whether there is a daily upload quota because we tried again the next morning and uploaded two builds successfully. I'm more dubious of a quota being in place and have found no documentation suggesting there is one.

Judging by Task Manager's reporting of upload data and how long it takes before this error message appears I would judge that it uploads most of the file before the error is produced. In the game manager on the PlayFab site I can confirm the build was attempted to be uploaded, it lists the file as an asset, but the file is corrupt and unusable: PlayFab won't allow it to be assigned to a build.

Disabling the firewall is not a longterm solution but shows that there is probably something we need to be letting through it but cannot find details specifying what to let through. And since disabling the Windows firewall does not appear to fully solve our issues there's something deeper potentially at play. Any thoughts on why we are getting this error and how we might be able to solve it? Right now uploading via PowerShell is looking far too unreliable.