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

Lecture pour commercial_account_manager

Qui est concerné : Azure SQL Database

Pourquoi c'est important : Now you can use AES 256 symmetric keys to configure transparent data encryption (TDE) with customer-managed keys in Azure SQL Database.

Urgence : Surveiller

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

Opportunités commerciales

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

Actions techniques

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

Questions à poser au client

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

Risques et objections

• Preview availability may limit readiness for production use.

Points à confirmer

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

Lecture pour sales_manager

Qui est concerné : Microsoft Azure and Azure SQL Database

Pourquoi c'est important : Azure SQL Database now supports AES 256 symmetric keys for configuring transparent data encryption with customer-managed keys.

Urgence : Surveiller

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

Opportunités commerciales

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

Actions techniques

• Validate preview availability and technical prerequisites before recommending adoption.

Questions à poser au client

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

Risques et objections

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

Points à confirmer

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

Lecture pour it_manager_dsi

Qui est concerné : Users configuring transparent data encryption (TDE) with customer-managed keys in Azure SQL Database

Pourquoi c'est important : AES 256 symmetric keys can be used to configure transparent data encryption (TDE) with customer-managed keys in Azure SQL Database.

Urgence : Surveiller

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

Actions techniques

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

Questions à poser au client

• 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?

Risques et objections

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

Points à confirmer

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

Lecture pour partner_channel

Qui est concerné : Azure SQL Database

Pourquoi c'est important : Azure SQL Database can use AES 256 symmetric keys to configure transparent data encryption (TDE) with customer-managed keys.

Urgence : Surveiller

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

Opportunités commerciales

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

Actions techniques

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

Questions à poser au client

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

Risques et objections

• Preview availability may limit production readiness or support expectations.

Points à confirmer

• 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.