Brett Wilson
Brett Wilson
> Hi @flanakin, it is to install the finops toolkit, but I guess it will be also valid request to setup the exports To confirm - you're having issues installing...
It's possible to use a user assigned MI or a SPN for the installation as long as the identity has the required permissions. No difference to a normal user installing...
You need to add the -scope parameter. Try this: ``` $Scope="/providers/microsoft.Billing/billingAccounts/1234567" Start-FinOpsCostExport -Name ftk-hub-04-monthly -Scope $scope -Backfill 13 ```
If you are using managed exports make sure the scope variable is an array. "scopes": [ { "scope": "/providers/Microsoft.Billing/billingAccounts/1234567" }, { "scope": "/subscriptions/123abc-..." } ] If you're not using managed...
Are you supplying a scope at all with the installation? And what about ADX/ADFS - any chance you could post some screenshots of the inputs from the deployment tab on...
Closing this issue as we support keys, OAuth and SAS. Key rollover in storage is out of scope for FTK.
Related PR #1349 was closed due to CLA requirement. The implementation from that PR can be used as a reference.
Will do. FWIW this doesn't break anything, but supressing the error will be great. Thanks for the updated expression :)
Try this... Works around intermittend 429 messages. Update the export names and scopes as appropriate. ```powershell [CmdletBinding()] param ( [datetime]$startdate = '2024-04-01', [datetime]$enddate = '2025-03-31', $exportsToRun = @( 'ftk-pricesheet', 'ftk-focuscost'...