Azure SQL database without Transparent Data Encryption
Transparent Data Encryption (TDE) encrypts an Azure SQL database, its backups and transaction logs at rest. It's on by default for new databases but can be disabled or missing on older ones.
Why it matters
Without TDE, anyone who obtains the underlying files or a backup can read every row — encryption at rest is a baseline control for regulated data.
Audits (PCI DSS, ISO 27001, SOC 2) expect encryption at rest; a database without TDE is a direct finding.
How to check for it
- Portal → SQL database → Transparent data encryption: it should be On.
- az sql db tde show -g <rg> -s <server> -d <db> --query status.
How to fix it
- Turn TDE on: az sql db tde set -g <rg> -s <server> -d <db> --status Enabled.
- For stricter control, use a customer-managed key in Azure Key Vault (BYOK) rather than the service-managed key.
SkyShield checks this automatically
Connect your AWS, Cloudflare, GitHub, GitLab, Hetzner or DigitalOcean account read-only and SkyShield flags this across every account and region, with the fix in plain words — alongside the agent that watches your servers. Start free.
FAQ
- Does TDE slow the database down?
- The overhead is small (typically a few percent) and encryption happens transparently, so applications need no changes.