---
title: "Architecture"
slug: "architecture-1"
updated: 2026-10-30T07:21:05Z
published: 2026-10-30T07:21:05Z
canonical: "docs.turbo360.com/architecture-1"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.turbo360.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Architecture

## 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

Azure Documenter is built around four architectural layers: Azure connectivity, document configuration, document generation, and output and publishing. Each layer plays a distinct role in how data flows from Azure into a finished document.

![azure-documenter-architecture-overview-four-layers.svg](https://cdn.document360.io/a21734f9-5f67-4835-bb81-a488f8191fa8/Images/Documentation/azure-documenter-architecture-overview-four-layers.svg)

### Layer 1: Azure connectivity

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.

![azure-documenter-architecture-layer-1-azure-connectivity.svg](https://cdn.document360.io/a21734f9-5f67-4835-bb81-a488f8191fa8/Images/Documentation/azure-documenter-architecture-layer-1-azure-connectivity.svg)

### Layer 2: 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.

![azure-documenter-architecture-layer-2-document-configuration.svg](https://cdn.document360.io/a21734f9-5f67-4835-bb81-a488f8191fa8/Images/Documentation/azure-documenter-architecture-layer-2-document-configuration.svg)

### Layer 3: 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.

![azure-documenter-architecture-layer-3-document-generation.svg](https://cdn.document360.io/a21734f9-5f67-4835-bb81-a488f8191fa8/Images/Documentation/azure-documenter-architecture-layer-3-document-generation.svg)

### Layer 4: Output and publishing

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.

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.

![azure-documenter-architecture-layer-4-output-and-publishing.svg](https://cdn.document360.io/a21734f9-5f67-4835-bb81-a488f8191fa8/Images/Documentation/azure-documenter-architecture-layer-4-output-and-publishing.svg)

## Related articles

- [What is Azure Documenter?](https://docs.turbo360.com/docs/what-is-azure-documenter)
- [Benefits](https://docs.turbo360.com/docs/benefits)
- [Use cases](https://docs.turbo360.com/docs/use-cases-1)
- [Azure Documenter quick start](https://docs.turbo360.com/docs/azure-documenter-quick-start)