Michael Flanakin
Michael Flanakin
@AErmie just responded to another post on this. This sounds like a bug in Cost Management. If you're still seeing this in the latest release, I would create a support...
@erose96 Deploy-FinOpsHub downloads the specified release from GitHub, which is why it's using `$env:temp`. According to Copilot, this should be supported 🤔 That said, we could add a property to...
Another option could be to hardcode the template in the PowerShell module. This might work for the latest release, but I don't think we'd want to do that for historical...
Tracking this as a feature request since the "bug" is arguably in how PowerShell works in ADO. Please 👍 vote this up to help prioritize it. I added one to...
Closing due to inactivity. Let me know if you run into any more issues and we can investigate.
Reopening to track for Power BI
Turns out there's a bug in Cost Management exports where the x_OnDemandCost is not being set correctly, which is causing the commitment savings calculation to be wrong. They're aware of...
x_OnDemandCost is in progress. I have a meeting this week to confirm the ETA. I'll see what I can find out regarding the others as well.
Sorry, I forgot to circle back on this one, but the issue in Cost Management should be resolved. Please let me know if anyone runs into something like this again.
The issue here is that 0.2 requires FOCUS exports and 0.1.* uses amortized exports. The Power BI reports will ignore the other exports since they do not apply. This results...