Forum Discussion

Hareth's avatar
Hareth
Copper Contributor
Apr 01, 2025

Setup of FinOps Toolkit

OK, so I've deployed the toolkit, setup the exports on an MCA account with 9x billing profiles, created FOCUS + Price Sheet exports for each billing profile followed by reservation details, transactions and recommendations for each billing profile.

Where it's failing for me is that I try to run the msexports_ExecuteETL and msexports_ETL_ingestion and it prompting me for 

msexports_ETL_ingestion: 

blobPath

destinationFile
destinationFolder
ingestionId
schemaFile
exportDatasetType
exportDatasetVersion

 

msexports_ExecuteETL:

folderPath
fileName

 

What should these value be?

 

Also we are currently migrating from EA agreement, to MCA, on the Cost Management Exports I can't see the subscription residing in the MCA agreement and therefore can't select the storage account in there to export to, why might that be?

 

4 Replies

  • jmz07's avatar
    jmz07
    Copper Contributor
    Aug 25, 2026

    To he account id has to match the header and you don't know the correct one yet because it's me

  • dmulder1's avatar
    dmulder1
    Copper Contributor
    Aug 24, 2026

    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)

  • Kidd_Ip's avatar
    Kidd_Ip
    MVP
    Apr 01, 2025

    Are you looking for this:

     

    1. Parameters for msexports_ETL_ingestion
    • blobPath: The path to the blob storage container where the raw export files are located.
    • destinationFile: The name of the output file after processing.
    • destinationFolder: The folder path in the storage account where the processed file will be saved.
    • ingestionId: A unique identifier for the ingestion process (can be auto-generated or specified).
    • schemaFile: The schema file that defines the structure of the data being ingested.
    • exportDatasetType: The type of dataset being processed (e.g., "FOCUS", "PriceSheet").
    • exportDatasetVersion: The version of the dataset schema being used (e.g., "v1").

     

    1. Parameters for msexports_ExecuteETL
    • folderPath: The folder path in the storage account where the raw export files are stored.
    • fileName: The specific file name to process within the folder.