Azure Function App fails with ERROR: Cannot bind argument to parameter 'InputObject' because it is null.

Alright, here is my code:

$AppId = $env:SPappId
$powerbiSP = $env:powerbiSP
$PWord = ConvertTo-SecureString -String $powerbiSP -AsPlainText -Force
$Credential = New-Object -TypeName "System.Management.Automation.PSCredential" -ArgumentList $AppId, $PWord
try { 
    Connect-PowerBIServiceAccount -ServicePrincipal -Credential $Credential -TenantId "xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxx"
    Start-Sleep -s 5
} catch {write-host "Error connecting to Power BI Service."}

$workspace = Get-PowerBIworkspace -name "some-workspace-name"
$dataset = Get-PowerBIDataset -WorkspaceId $workspace.Id
$tablename = "some-table-name"
Remove-PowerBIRow -WorkspaceId $workspace.Id -DataSetId $dataset.Id -TableName $tablename
Add-PowerBIRow -WorkspaceId $workspace.Id -DataSetId $dataset.Id -TableName $tablename -Rows ($report | ConvertTo-Json | ConvertFrom-Json)

This code works perfect locally in powershell core 7.0.3 on my laptop, service principle and all.

But when trying to run it in an Azure Function app, it successfully logs into Power BI using the service principle, and is able to successfully get the workspace specified as well as the dataset. However, once it gets to the Remove-PowerBIRow and Add-PowerBIRow cmdlets, it fails with a generic non descript error:

ERROR: Cannot bind argument to parameter 'InputObject' because it is null. Exception:Type:System.Management.Automation.ParameterBindingValidationExceptionMessage:Cannot bind argument to parameter 'InputObject' because it is null.

Resolve-PowerBIError doesn't give any better information either...

I've tried all different configurations of the commands, explicitly specifying values, pipelining objects in, but it fails the same way every time.

Remove-PowerBIRow -Workspace $workspace -DataSet $dataset -TableName $tablename

$workspace | Remove-PowerBIRow -DataSet $dataset -TableName $tablename

Remove-PowerBIRow -WorkspaceId "xxxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx" -DataSetId "xxxxxx-xxxx-xxxx-xxxx-xxxxxxxxx" -TableName "some-table-name"

How can there be a null parameter if they're explicitly defined in the cmdlet(the 3rd example above) ?????????
all required params for the cmdlet have been defined, it makes no sense.

Every one of the commands above work on my laptop but fail in my Azure Function btw.

I even tried to trace the commands but received no output at all from it in the function app logs:
Trace-Command -Name ParameterBinding -Expression {Remove-PowerBIRow -Workspace $workspace -DataSet $dataset -TableName $tablename} -pshost

I'm lost on this one........

Start with the Remove-PowerBIRow and Add-PowerBIRow calls and reproduce the failure in the Azure Function environment, comparing it with PowerShell Core 7.0.3 locally. Check the parameter-binding and runtime differences around the explicitly supplied workspace, dataset, table, and rows values. Done means identifying the environment-specific null input and confirming the affected cmdlets work in the function app.