Managed exports don't work with MCA billing accounts or profiles

[georgeollis]

🐛 Problem

When deploying a new FinOps hub, using an MCA billing account (Not EA), and configuring the settings.json scope correctly, exports are not created due to slashing errors. I've also been able to replicate this using a manual export. The issue is with the format of IDs that represent a billing profile.

For instance, my billing profile configured is: "/providers/Microsoft.Billing/billingAccounts/d72daa4b-365d-5b26-096a-6d60fcc2374e:b70206fd-4bbb-459a-9438-9ed9b524175f_2019-05-31"

My ADF MI has been setup correctly and has the correct RBAC permissions on my MCA billing account.

The error in ADF: {"error":{"code":"BadRequest","message":"Request properties validation failed: Invalid deliveryInfo destination rootFolderPath; providers/Microsoft.Billing/billingAccounts/d72daa4b-365d-5b26-096a-6d60fcc2374e:b70206fd-4bbb-459a-9438-9ed9b524175f_2019-05-31' Value cannot contain any reserved url characters except forward slashes(/)"}}

👣 Repro steps

TODO: Add repro steps below:

1. Configure an export scope in the settings.json file.
2. Wait for the ADF blob creation trigger to start the Export pipeline.
3. See errors

🤔 Expected

ADF should be able to create exports.

[MSBrett]

FTK does not support managed exports for Microsoft Customer Agreement billing accounts.

To configure exports for MCA accounts see configure Cost Management exports manually.

We plan on adding support for MCA accounts to the managed exports feature in the future once some other upstream requirements are ready.

[georgeollis]

@MSBrett - Thanks for letting me know! I'll keep an eye out in the future!

[flanakin]

I'm going to reopen this to track it as an open Cost Management bug. Feel free to submit this as a support request to the Cost Management team to ensure they fix it. I don't know whether they're tracking it or not, but this will at least help raise awareness.

[georgeollis]

@flanakin Will raise with them - it does need to be fixed. Thanks