> For the complete documentation index, see [llms.txt](https://docs.finops.softwareone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.finops.softwareone.com/system/data-sources/manage-data-sources/disconnect-data-source.md).

# Disconnect data source

The **Disconnect** option on the details page of a data source lets you disconnect and remove a data source from FinOps for Cloud. 

When a data source has been disconnected, you’ll only be charged for the days the data source was connected. Once it’s disconnected, billing will stop, and you won’t receive any further invoices. 

### Disconnect a data source

{% hint style="warning" %}
Disconnecting a data source removes all historical data associated with that source.
{% endhint %}

To disconnect a data source from FinOps for Cloud:

1. In FinOps for Cloud, navigate to the **Data sources** page. 
2. Select the data source you want to disconnect.
3. On the details page of the selected data source, select **Disconnect**.
4. Select **Disconnect** again to confirm the action.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.finops.softwareone.com/system/data-sources/manage-data-sources/disconnect-data-source.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.