Overview
Azure Documenter supports recurring document generation schedules configured in the Schedule step of the Configure your document wizard. A schedule triggers document generation automatically at the day and time you set, without requiring manual action each cycle.
Business value
Scheduled document generation removes the manual overhead of producing recurring reports. It ensures stakeholders receive up-to-date Azure documentation on a predictable cadence, supports governance processes that require regular compliance or cost snapshots, and frees teams to focus on acting on findings rather than producing them.
How it works
A schedule is configured per document configuration. In the Schedule step, you enable scheduling, set the Frequency (Weekly or Monthly), choose the day, and set the time. You can add multiple schedules to a single configuration using + Add schedule — for example, a weekly schedule for an operational audience and a monthly schedule for an executive audience.
When a scheduled run completes, Azure Documenter publishes the document to the configured publish destination (Azure Storage account or Document360) and sends a notification if notifications are enabled in the Notifications step.
Match frequency to the document type's data change rate
Schedule frequency should reflect how quickly the underlying Azure data changes and how often stakeholders need updated information.
| Document type | Recommended frequency | Rationale |
|---|---|---|
| Executive summary | Monthly | High-level trends change slowly; monthly aligns with reporting cycles |
| Cost comparison, Billing details | Monthly | Billing cycles are monthly; weekly runs produce redundant data mid-cycle |
| Rightsizing recommendations, Reservation recommendations | Monthly or bi-weekly | Recommendations update as usage changes; monthly is sufficient for most environments |
| Security compliance, Access details | Weekly | Security posture changes frequently; weekly catches new issues promptly |
| Resource details, Resource auditing | Weekly or monthly | Depends on how actively the environment changes |
| Network topology diagram, Workload diagram | Monthly | Architecture changes infrequently; monthly captures planned changes |
| Carbon summary, Carbon optimizations | Monthly | Carbon data aligns with billing period |
| License consumption, License optimizations, Service plan matrix | Monthly | License assignments change at onboarding and offboarding cycles |
Schedule generation during off-peak hours
Set generation times outside of peak business hours — early morning or late evening in the subscription's primary time zone. Generation queries Azure resource data and can take several minutes for large environments. Scheduling off-peak reduces contention with other Azure operations and ensures reports are available when the business day starts.
A generation time of 06:00 local time means reports are ready when the team begins work, with no manual action required.
Stagger multiple configurations to avoid concurrent generation
If several configurations share the same schedule frequency, offset their start times by at least 15 minutes. Concurrent generation across multiple large-scope configurations can result in longer generation times and delayed notifications.
Example: three monthly configurations scheduled on the first of the month at 06:00, 06:15, and 06:30, rather than all at 06:00.
Use multiple schedules for tiered reporting audiences
A single configuration can carry more than one schedule. Use this when a report needs to serve both an operational audience on a weekly cadence and an executive audience on a monthly one — without maintaining two separate configurations with identical scope and branding settings.
Example: a Security compliance configuration with a weekly schedule for the security team and a monthly schedule that aligns with the board reporting cycle.
Configure notifications for every scheduled configuration
Enable notifications in the Notifications step for every configuration that has a schedule. Without notifications, a generation failure is invisible until someone manually checks the document configurations list. Configure the recipient email to reach the team responsible for acting on the report — not just the person who created the configuration.
When a scheduled generation fails, the failure notification includes the reason. This reduces mean time to resolution and prevents a stakeholder meeting from being the first signal that a report is missing.
Validate output with an on-demand generation before relying on the schedule
After creating a scheduled configuration, trigger an on-demand generation from the document configurations list to verify that the output is correct. Do not wait for the first scheduled run to discover scope or permission errors. On-demand generation uses the same settings as a scheduled run and produces the same output, so validating it early catches issues before they affect a time-sensitive reporting cycle.