Overview
Azure Documenter connects to your Azure subscriptions through a Service Principal to pull resource, cost, compliance, and security data. It compiles this into a document and stores or publishes it to a destination you choose.
Business value
- Understand how data flows from Azure into a finished document, to troubleshoot access or output issues confidently
- Plan service principal and storage setup correctly the first time, reducing rework
- Choose the right publish destination based on how the document needs to be shared
How it works
Data source
Azure Documenter authenticates to your Azure subscription using a Service Principal in Microsoft Entra ID with Reader access. It uses this connection to retrieve resource, billing, access, and compliance data for the subscriptions you configure.
Document configuration
A document configuration ties together the subscription(s), document type, notification channels, and publish platform for a given report. You can edit configurations later to update any of these settings and reuse them to regenerate documents on demand or on a schedule.
Document generation
When you generate a document, manually or on a schedule, Azure Documenter compiles the relevant Azure data into a single output. Processing time varies by document type. A Network topology diagram, for example, processes resource topology. A Billing details document processes cost data for a selected date range and currency.
Output and storage
Azure Documenter produces documents as PDF, Word, or Excel files. By default, Turbo360 stores them in a built-in storage account. To use your own Azure Storage account, provide a connection string.
Publishing
Beyond file-based output, you can publish documents online to a Document360 project. This requires an API token scoped with full request-method access (GET/POST/PUT/DELETE). The generated content routes directly into a knowledge base instead of a static file.