Setup of FinOps Toolkit

Those fields look like internal pipeline payloads, so I would not guess values and invoke the functions manually. First confirm the FinOps hub deployment completed cleanly, then inspect the Logic App or Function run history to find the orchestrator, failed upstream step and exact payload. The blob path, schema and dataset version need to match the export that triggered the run.

Reduce the test to one MCA billing profile and one FOCUS export. Verify that its files arrive in the expected container, then follow that single dataset through ingestion before enabling the other eight profiles. This also limits duplicate exports, repeated ETL runs and storage or processing waste while you troubleshoot, a pattern I watch closely in Azure Cloud Waste Busting work.

For the storage-account issue, validate that the subscription is under the intended MCA billing scope and tenant. Then check the deployment identity's access to both the billing profile and storage account, along with the required provider registration. Preserve the failed run details rather than repeatedly launching jobs with guessed parameters.

Are msexports_ExecuteETL and msexports_ETL_ingestion being called by the deployed orchestration, or are you starting them directly in the portal?

If you are looking for a product that helps you reduce your bill, check out Full Circle IT DEBT in the Azure Marketplace, it gives you your savings potential for free. 

Dennis Mulder (Full Circle IT, ex-CTO of Microsoft NL, 18 years of Azure experience)