Azure SQL Database
An Azure relational database service.
6,045 questions
Secure enclaves enabled but SSMS didn't allow
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(99.2, 39%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJW%3C/text%3E%3C/svg%3E)
John Woo
0
Reputation points
in Azure portal, I created the database with Secure enclaves enabled - type was Virtualization based security (VBS).
the command below return 1,1; however when using SSMS trying to connect with Enable secure enclaves, and protocol None, got error:
You have specified the attestation protocol in the connection string, but the SQL Server in use does not support enclave based computations - see https://go.microsoft.com/fwlink/?linkid=2157649 for more details. (Microsoft.Data.SqlClient)
Program Location:
at Microsoft.Data.SqlClient.TdsParser.TryProcessFeatureExtAck(TdsParserStateObject stateObj)
at Microsoft.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
....
select name, value, value_in_use from sys.configurations where name = 'column encryption enclave type'
{count} votes
-
John Woo 0 Reputation points
2025-02-27T14:29:51.8966667+00:00 even created the attestation url and filled in, still got error
TITLE: Connect to Server
Cannot connect to hot1.database.windows.net.
ADDITIONAL INFORMATION:
You have specified the enclave attestation URL and attestation protocol in the connection string, but the SQL Server in use does not support enclave based computations - see https://go.microsoft.com/fwlink/?linkid=2157649 for more details. (Microsoft.Data.SqlClient)
BUTTONS:
OK
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(35.2, 49%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EVK%3C/text%3E%3C/svg%3E)
Vijayalaxmi Kattimani 1,485 Reputation points Microsoft Vendor2025-02-28T02:53:55.62+00:00 Hi @John Woo,
Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.
Could you please confirm whether you are encountering this error in the on-premises SQL database or in the Azure SQL Database?
-
John Woo 0 Reputation points
2025-02-28T08:30:55.7466667+00:00 I'm using azure portal to create the azure sql (cloud version), my company (a big bank) uses azure portal as well - we never use the on prem nor VM version of SQL the past 3 years. It was confusion compared with the traditional SQL, the way to config and test changed. now we have challenges doing migration.
-
Vijayalaxmi Kattimani 1,485 Reputation points Microsoft Vendor
2025-02-28T10:35:28.7533333+00:00 Hi John Woo,
Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.
As we understand that, you are encountering an issue with enabling secure enclaves in your Azure SQL Database using Virtualization Based Security (VBS). This error typically occurs when the SQL Server instance does not support enclave-based computations, even though the database was created with secure enclaves enabled.
To resolve this issue, ensure that you are using the latest version of SQL Server Management Studio (SSMS) and that the correct attestation protocol is specified.
Here are some steps you can follow:
- Verify Enclave Configuration: Ensure that the database is correctly configured with a VBS enclave. You can do this by checking the database properties in the Azure portal or using Azure PowerShell commands.
- SMS Configuration: When connecting to the database using SSMS, make sure to enable secure enclaves and specify the correct attestation protocol. In SSMS, go to the "Connect to Server" dialog, select "Options," and then the "Always Encrypted" tab. Ensure that "Enable secure enclaves" is checked and the correct protocol is selected.
- Supported Enclave Technologies: Always Encrypted supports different enclave technologies, including VBS enclaves. Ensure that your SQL Server instance supports the enclave type you are using.
Additionally, you can refer to the following links for more detailed guidance:
If you continue to experience issues, please let us know here. We will respond with more details and try to help you.
I hope this information helps. Please do let us know if you have any further queries.
Sign in to comment
Sign in to answer