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/README.md
+17-14Lines changed: 17 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,18 +30,20 @@ Before you begin, you need an Azure subscription. If you don't already have an A
30
30
You also need to make sure the following software is installed on your machine:
31
31
32
32
1. PowerShell modules:
33
+
33
34
1. Az version 5.6 or later. For details on how to install the Az PowerShell module, see [Install the Azure Az PowerShell module](https://docs.microsoft.com/powershell/azure/install-az-ps). To determine the version of the Az module installed on your machine, run the following command from a PowerShell session.
34
35
35
36
```powershell
36
37
Get-InstalledModule -Name Az
37
38
```
38
-
1. Az.Attestation 0.1.8 or later. For details on how to install the Az.Attestation PowerShell module, see [Install Az.Attestation PowerShell module](https://docs.microsoft.com/azure/attestation/quickstart-powershell#install-azattestation-powershell-module). To determine the version of the Az.Attestation module installed on your machine, run the following command from a PowerShell session.
39
+
40
+
2. Az.Attestation 0.1.8 or later. For details on how to install the Az.Attestation PowerShell module, see [Install Az.Attestation PowerShell module](https://docs.microsoft.com/azure/attestation/quickstart-powershell#install-azattestation-powershell-module). To determine the version of the Az.Attestation module installed on your machine, run the following command from a PowerShell session.
39
41
40
42
```powershell
41
43
Get-InstalledModule -Name Az.Attestation
42
44
```
43
45
44
-
1. SqlServer version 21.1.18245 or later. For details on how to install the SqlServer PowerShell module, see [Installing or updating the SqlServer module](https://docs.microsoft.com/sql/powershell/download-sql-server-ps-module#installing-or-updating-the-sqlserver-module). To determine the version the SqlServer module installed on your machine, run the following command from a PowerShell session.
46
+
3. SqlServer version 21.1.18245 or later. For details on how to install the SqlServer PowerShell module, see [Installing or updating the SqlServer module](https://docs.microsoft.com/sql/powershell/download-sql-server-ps-module#installing-or-updating-the-sqlserver-module). To determine the version the SqlServer module installed on your machine, run the following command from a PowerShell session.
45
47
46
48
```powershell
47
49
Get-InstalledModule -Name SqlServer
@@ -63,7 +65,7 @@ Setup steps:
63
65
64
66
1. Clone/download and unpack the repository.
65
67
1. Open a PowerShell session.
66
-
1. In the PowerShell session, change the directory to the setup folder within this demo's directory. For example, if you've unpacked the downloaded repository on a Windows machine in **C:\**, issue the following command:
68
+
1. In the PowerShell session, change the directory to the setup folder within this demo's directory. For example, if you've unpacked the downloaded repository on a Windows machine in **C:\\**, issue the following command:
67
69
68
70
```powershell
69
71
cd "C:\sql-server-samples\samples\features\security\always-encrypted-with-secure-enclaves\azure-sql-database\setup"
@@ -87,7 +89,7 @@ Setup steps:
87
89
88
90
## Demo 1
89
91
90
-
During this demo, you will take a tour of the demo environment, in which Always Encrypted with secure enclaves is already set up and sensitive data columns in the database are already encrypted.
92
+
In this demo, you will take a tour of the demo environment, in which Always Encrypted with secure enclaves is already set up and sensitive data columns in the database are already encrypted.
91
93
92
94
### Prepare for the demo
93
95
@@ -97,11 +99,11 @@ Perform the below steps before each demo presentation.
97
99
1. Prepare a new instance of SSMS.
98
100
1. Start SSMS.
99
101
1. In the Connect to Server dialog:
100
-
1. In the main page of the dialog, enter your database server name. Set **Authentication** to **Azure Active Directory – Universal with MFA**. In the **User Name** field, enter your Azure AD username. You should enter the same username, you've used to sign in to Azure, when you set up your demo environment.
102
+
1. In the main page of the dialog, enter your database server name. Set **Authentication** to **Azure Active Directory – Universal with MFA**. In the **User Name** field, enter your Azure AD username. You should enter the same username, you used to sign in to Azure, when you set up your demo environment.
101
103
102
104
103
105
104
-
1. Click Connect.
106
+
1. Click **Connect**.
105
107
1. When prompted, sign in to Azure.
106
108
1. Prepare your web browser.
107
109
1. Open a new tab in the browser and point it to Azure Portal: **https://portal.azure.com**.
@@ -117,7 +119,7 @@ Perform the below steps before each demo presentation.
117
119
-`<project name>app`- an app service hosting the Contoso HR web application.
118
120
-`<project name>attest`- an attestation provider in Microsoft Azure Attestation for attesting the secure enclave for the **ContosoHR** database.
119
121
-`<project name>identity` - a user-assigned managed identity that was used to deploy the web application.
120
-
-`<project name>plan` - am app service plan for the web application.
122
+
-`<project name>plan` - an app service plan for the web application.
121
123
-`<project name>server`- a logical server in Azure SQL Database.
122
124
-`<project name>vault` - a key vault in Azure Key Vault, containing the column master key for Always Encrypted.
123
125
-`ContosoHR` - a database.
@@ -132,14 +134,15 @@ Perform the below steps before each demo presentation.
132
134
133
135
1. Close the browser tab for the attestation provider. Right-click on the app service for the Contoso HR web application in your resource group and open its **Overview** blade in a new tab. Click on **Configuration** under **Settings**. In the **Connection strings** section, click **Advanced edit**. This will display the database connection string configured for the web application. There are three important things to call out in the database connection string:
134
136
135
-
-**Column Encryption Setting = Enabled** turns the Always Encrypted on in the client driver, allowing it to transparently encrypt query parameters and decrypt queries results.
137
+
-**Column Encryption Setting = Enabled** turns the Always Encrypted on in the client driver, allowing it to transparently encrypt query parameters and decrypt query results.
136
138
-**Attestation Protocol = AAS** specifies Microsoft Azure Attestation is used for attesting the secure enclave for the **ContosoHR** database.
137
139
-**Enclave Attestation Url** is an attest URI of the attestation provider.
2. Click on **Access Policies** under **Settings**. 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.
@@ -166,7 +169,7 @@ Perform the below steps before you show the demo.
166
169
1. Prepare a new instance of SSMS.
167
170
1. Start SSMS.
168
171
1. In the **Connect to Server** dialog:
169
-
1. In the main page of the dialog, enter your database server name. Set **Authentication** to **Azure Active Directory – Universal with MFA**. In the **User Name** field, enter your Azure AD username. You should enter the same username, you've used to sign in to Azure, when you set up your demo environment.
172
+
1. In the main page of the dialog, enter your database server name. Set **Authentication** to **Azure Active Directory – Universal with MFA**. In the **User Name** field, enter your Azure AD username. You should enter the same username, you used to sign in to Azure, when you set up your demo environment.
170
173
171
174
172
175
@@ -178,7 +181,7 @@ Perform the below steps before you show the demo.
Copy file name to clipboardExpand all lines: samples/features/security/always-encrypted-with-secure-enclaves/sql-server-with-hgs/README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -73,7 +73,7 @@ Perform the below steps before you show the demo.
73
73
1. Start SSMS.
74
74
1. In the **Connect to Server** dialog:
75
75
1. In the main page of the dialog, enter your database server name. For example, enter `.` to connect to the default instance on the local machine. Set your authentication parameters.
76
-
1. Click the **Options >>** button, select the **Connection Properties** tab and enter the database name(**ContosoHR**).
76
+
1. Click the **Options >>** button, select the **Connection Properties** tab and enter the database name(**ContosoHR**).
@@ -97,7 +97,7 @@ Perform the below steps before you show the demo.
97
97
1. Start SSMS.
98
98
1. In the **Connect to Server** dialog:
99
99
1. In the main page of the dialog, enter your database server name. For example, enter `.` to connect to the default instance on the local machine. Set your authentication parameters.
100
-
1. Click the **Options >>** button, select the **Connection Properties** tab and enter the database name(**ContosoHR**).
100
+
1. Click the **Options >>** button, select the **Connection Properties** tab and enter the database name(**ContosoHR**).
0 commit comments