[In preview] Public Preview: Azure SQL updates for early-June

Reading for commercial_account_manager

Who is affected: Azure SQL Database

Why it matters: Now you can use AES 256 symmetric keys to configure transparent data encryption (TDE) with customer-managed keys in Azure SQL Database.

Urgency: Monitor

Next action: Confirm whether the account uses Azure SQL Database with customer-managed keys for TDE.

Commercial opportunities

• Discuss whether AES 256 symmetric keys for TDE with customer-managed keys addresses the account’s requirements.

Technical actions

• Review the preview documentation before advising on configuration or adoption.

Questions to ask the customer

• Would configuring TDE with AES 256 symmetric keys and customer-managed keys address a current requirement?

Risks and objections

• Preview availability may limit readiness for production use.

Points to confirm

• The effective date is unknown because the payload does not provide one.

Reading for it_manager_dsi

Who is affected: Users configuring transparent data encryption (TDE) with customer-managed keys in Azure SQL Database

Why it matters: AES 256 symmetric keys can be used to configure transparent data encryption (TDE) with customer-managed keys in Azure SQL Database.

Urgency: Monitor

Next action: Review whether Azure SQL Database encryption configurations should use AES 256 symmetric keys in the public preview.

Technical actions

• Assess compatibility, security requirements, and operational procedures before testing the preview capability.

Questions to ask the customer

• Are you configuring transparent data encryption with customer-managed keys in Azure SQL Database?
• Would you like to evaluate AES 256 symmetric keys in the public preview?

Risks and objections

• The capability is in public preview, so production readiness and support expectations should be validated before adoption.

Points to confirm

• The effective date is unknown because the source provides only an early June 2026 timeframe and the payload lists effective_date_unknown.

Reading for partner_channel

Who is affected: Azure SQL Database

Why it matters: Azure SQL Database can use AES 256 symmetric keys to configure transparent data encryption (TDE) with customer-managed keys.

Urgency: Monitor

Next action: Review the preview capability with relevant Azure SQL Database stakeholders and assess whether it fits current encryption requirements.

Commercial opportunities

• Discuss partner-led guidance or implementation support for configuring TDE with customer-managed keys.

Technical actions

• Validate AES 256 symmetric key configuration and TDE behavior in an appropriate preview environment.

Questions to ask the customer

• Would configuring TDE with customer-managed keys address a current Azure SQL Database requirement?
• Is preview functionality acceptable for the intended use case?

Risks and objections

• Preview availability may limit production readiness or support expectations.

Points to confirm

• The effective date is unknown from the supplied source.
• The capability may remain subject to preview limitations; the supplied source does not specify those limitations.

Reading for sales_manager

Who is affected: Microsoft Azure and Azure SQL Database

Why it matters: Azure SQL Database now supports AES 256 symmetric keys for configuring transparent data encryption with customer-managed keys.

Urgency: Monitor

Next action: Assess whether this preview capability is relevant to accounts using Azure SQL Database and customer-managed keys.

Commercial opportunities

• Discuss the preview capability with accounts that require customer-managed encryption keys.

Technical actions

• Validate preview availability and technical prerequisites before recommending adoption.

Questions to ask the customer

• Do you use Azure SQL Database with customer-managed keys for transparent data encryption?
• Would AES 256 symmetric keys address an existing encryption requirement?

Risks and objections

• The update is in public preview, so production readiness and support expectations should be confirmed.

Points to confirm

• The effective date is unknown; the source only states that the update was made in early June 2026.