> For the complete documentation index, see [llms.txt](https://docs.cloudassert.com/azure-stack-billing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cloudassert.com/azure-stack-billing/2005-1/installation/configuration/cost-management.md).

# Cost Management

* Turn off the cost management agent service from ‘Services’
* Navigate to agent service installation path and open CloudAssert.CostManagement.WindowsService.exe.config. By default, it is installed in “C:\Program Files\CloudAssertCostManagement\CloudAssert.CostManagement.WindowsService”
* Make the below changes as needed,
  * Azure Stack Hub Usage Collection: AzsHubUsageProcessorIsEnabled in appSettings should be set to ‘True’
  * Microsoft CSP Usage collection: CspBilledUsageReaderIsEnabled in appSettings should be set to ‘True’
* Save the file and turn on the cost management agent service


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.cloudassert.com/azure-stack-billing/2005-1/installation/configuration/cost-management.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.