Cost API fails if using a Microsoft Sponsored Subscription or Azure Cost API is disabled

Currently if you are using a Microsoft Sponsored Subscription or a CSP based subscription, the cost reporting element of Azure's cost API is locked down and delegated to either the Partner Portal or the CSP provider's cost reporting tool.

There is an expected error that appears on the TRE UI:

However, this error can be ignored and you can press the x on the drop down to dismiss the error.
The dismissing of the error is not cached and every new page of the UI loaded presents the error again, regardless of how many times you have dismissed it.

For the subscriptions hosting these TREs it is unlikely the access to the cost API will be enabled so caching the dismissing of the error would be useful even if it times out after a few hours to prevent a constant red error box appearing.

Perhaps even an option in the config to disable the cost part of the TRE if it is known the cost reporting will not work in certain instances.

No files, tests, or entry points are named. Start by locating the Azure cost API error handling and the TRE UI state behind dismissing the error, then check how subscription configuration is loaded. Done means the expected disabled-API error no longer reappears on every page, with the chosen timeout or configuration behavior covered by tests.