Storage account Table services should have classic logging enabled
This control checks that classic logging is enabled for the Azure Table service. Classic logging provides auditing for read, write, and delete actions by recording them in the associated storage logs.
Classic logging provides auditing for read, write, and delete actions by recording them in the associated storage logs. This is important in legacy scenarios where diagnostic settings are not yet in place.
What this control checks
Azure Table service must have classic logging enabled.
Audit evidence
Evidence that deployed resources meet this control: PowerPipe control azure_compliance.control.storage_account_table_service_classic_logging_enabled.
Framework-specific interpretation
CIS Azure Benchmark v1.3.0: Mapped to 3.11 (Ensure Storage logging is enabled for Table service for read, write, and delete requests).
CIS Azure Benchmark v1.4.0: Mapped to 3.11 (Ensure Storage logging is enabled for Table service for 'Read', 'Write', and 'Delete' requests).
Framework mappings
The clauses this control is mapped to in each framework.
- 3.11 Ensure Storage logging is enabled for Table service for read, write, and delete requests
- 3.11 Ensure Storage logging is enabled for Table service for 'Read', 'Write', and 'Delete' requests
Related controls
Tool mappings
Use these identifiers to cross-reference this control across tools, reports, and evidence.
- Compliance.tf Control:
storage_account_table_service_classic_logging_enabled - Powerpipe Control:
azure_compliance.control.storage_account_table_service_classic_logging_enabled
Last reviewed: 2026-10-15