You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: samples/features/security/always-encrypted-with-secure-enclaves/azure-sql-database-sgx/README.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -118,7 +118,7 @@ Perform the below steps before each demo presentation.
118
118
-`<project name>vault` - a key vault in Azure Key Vault, containing the column master key for Always Encrypted.
119
119
-`ContosoHR` - a database.
120
120
121
-
1. Right-click on the **ContosoHR** database in the resource group and open its **Overview** blade in the new tab. Click on **Compute + storage** under **Settings**. Click **Change configuration**. Note that the database is already configured to use the DC-series hardware configuration that supports confidential computing using secure enclaves. Setting the DC-series hardware configuration for a database is required to use Always Encrypted with secure enclaves in the database. For more information, see [Enable Intel SGX for your Azure SQL Database](https://docs.microsoft.com/azure/azure-sql/database/always-encrypted-enclaves-enable-sgx).
121
+
1. Right-click on the **ContosoHR** database in the resource group and open its **Overview** blade in the new tab. Click on **Compute + storage** under **Settings**. Click **Change configuration**. Note that the database is already configured to use the DC-series hardware configuration that supports confidential computing using secure enclaves. Setting the DC-series hardware configuration for a database is required to use Always Encrypted with secure enclaves in the database. For more information, see [Enable Intel SGX for your Azure SQL Database](https://docs.microsoft.com/azure/azure-sql/database/always-encrypted-enclaves-enable-sgx). In the left ribbon, click on **Data Encryption** and click in the blade on **Always Encrypted**. Confirm that the Secure Enclave is enabled and that the enclave type is **Intel Software Guard Extension (Intel SGX)**
Copy file name to clipboardExpand all lines: samples/features/security/always-encrypted-with-secure-enclaves/azure-sql-database-sgx/setup/azuredeploy.bicep
+31-26Lines changed: 31 additions & 26 deletions
Original file line number
Diff line number
Diff line change
@@ -14,6 +14,7 @@ param userName string
14
14
@description('The username of the Azure SQL database server administrator for SQL authentication.')
15
15
paramsqlAdminUserNamestring
16
16
17
+
@secure()
17
18
@description('The password of the Azure SQL database server administrator for SQL authentication.')
$location=Read-Host-Prompt "Enter a region where you want to deploy the demo environment"
11
11
$sqlAdminUserName=Read-Host-Prompt "Enter the username of the Azure SQL database server administrator for SQL authentication"
12
12
$sqlAdminPasswordSecureString=Read-Host-Prompt "Enter the password of the Azure SQL database server administrator for SQL authentication"-AsSecureString
Copy file name to clipboardExpand all lines: samples/features/security/always-encrypted-with-secure-enclaves/azure-sql-database-vbs/README.md
+5Lines changed: 5 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -128,6 +128,11 @@ Perform the below steps before each demo presentation.
128
128
129
129
2. Click on **Access Policies**. You should see two access policy entries: one for your identity and one for the web app's identity. These policies grant you permissions necessary to perform key management operations and they grant the web app permissions required to decrypt column encryption keys, protecting the data.
130
130
131
+
1. Close the browser tab for the key vault. Right-click on the logical server in your resource group and open its **Overview** blade in a new tab.
132
+
1. Click on **SQL Databases** and select **ContosoHR** database.
133
+
2. In the left ribbon, click on **Data Encryption** and click in the blade on **Always Encrypted**.
134
+
3. Confirm that the Secure Enclave is enabled and that the enclave type is **Virtualization based security (VBS)**
135
+
131
136
1. Switch to SSMS.
132
137
1. In Object Explorer, navigate to the **ContosoHR** database. Then go to **Security** > **Always Encrypted Keys**.
133
138
1. Open the **Column Master Keys** and **Column Encryption Keys** folders. You should see the metadata object, named **CMK1**, for the column master key and the metadata object, named **CEK1**, for the column encryption key.
Copy file name to clipboardExpand all lines: samples/features/security/always-encrypted-with-secure-enclaves/azure-sql-database-vbs/setup/azuredeploy.bicep
+30-25Lines changed: 30 additions & 25 deletions
Original file line number
Diff line number
Diff line change
@@ -15,6 +15,7 @@ param userName string
15
15
paramsqlAdminUserNamestring
16
16
17
17
@description('The password of the Azure SQL database server administrator for SQL authentication.')
18
+
@secure()
18
19
paramsqlAdminPasswordstring
19
20
20
21
@description('The IP address the user will connect from to the logical server in Azure SQL Database.')
0 commit comments