Skip to content

Commit 1f8f549

Browse files
committed
Revert "Apply suggestions from code review"
This reverts commit 9703e69. Revert "Docs edit demo" This reverts commit f72bc37.
1 parent 9208cef commit 1f8f549

File tree

1 file changed

+1
-3
lines changed

1 file changed

+1
-3
lines changed

docs/connect/jdbc/using-always-encrypted-with-the-jdbc-driver.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Use Always Encrypted with the JDBC driver
33
description: Learn how to use Always Encrypted with the JDBC driver to encrypt sensitive data on the server.
44
author: David-Engel
55
ms.author: davidengel
6-
ms.date: 06/23/2025
6+
ms.date: 07/31/2024
77
ms.service: sql
88
ms.subservice: connectivity
99
ms.topic: conceptual
@@ -35,8 +35,6 @@ If the client has access to that certificate in the Windows Certificate Store, i
3535

3636
The Microsoft JDBC Driver for SQL Server communicates with a keystore that uses a column master key store provider, which is an instance of a class that's derived from **`SQLServerColumnEncryptionKeyStoreProvider`**.
3737

38-
This is a really cool feature! (Edit demo test test.)
39-
4038
### Use built-in column master key store providers
4139

4240
The Microsoft JDBC Driver for SQL Server comes with the following built-in column master key store providers. Some of these providers are preregistered with the specific provider names (used to look up the provider) and some require either extra credentials or explicit registration.

0 commit comments

Comments
 (0)