> For the complete documentation index, see [llms.txt](https://docs.tonic.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tonic.ai/textual/textual-integrations/microsoft-fabric-integration.md). # Microsoft Fabric integration Use the Textual workload in Fabric to detect and replace sensitive values in OneLake files.
About the integration

Overview of the integration and its workflow.		About the Textual integration with Fabric
Add the workload

How to add the Textual workload to your Fabric environment.		Adding the Textual workload to your environment
Create a Textual workload item

Adding the workload to your Fabric workspace.		Creating a Textual workload item in a Fabric workspace
Select the source files and output destination

Identifying the files to redact and indicating where to write the redacted files.		Selecting the source files and output destination
Configure redaction

Indicating how to replace the detected entities for each entity type.		Identifying and configuring replacement of entity types
Push redacted files

Generating the redacted files to the configured output location.		Pushing redacted files to the destination location
--- # 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.tonic.ai/textual/textual-integrations/microsoft-fabric-integration.md?ask=&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.