Skip to content

Commit bfd8b20

Browse files
authored
Update troubleshoot-tde.md
1 parent 4cb0452 commit bfd8b20

1 file changed

Lines changed: 28 additions & 44 deletions

File tree

docs/relational-databases/security/encryption/troubleshoot-tde.md

Lines changed: 28 additions & 44 deletions
Original file line numberDiff line numberDiff line change
@@ -159,7 +159,10 @@ Confirm that the server has permissions to the key vault and the correct permiss
159159

160160
## Getting TDE status from the Activity log
161161

162-
To allow for monitoring of the database status due to Azure Key Vault key access issues, the following events will be logged to the [Activity Log](/azure/service-health/alerts-activity-log-service-notifications) for the resource ID based on the Azure Resource Manager URL and Subscription+ResourceGroup+ServerName+DatabaseName:
162+
To allow for monitoring of the database status due to Azure Key Vault key access issues, the following events will be logged to the [Activity Log](/azure/service-health/alerts-activity-log-service-notifications) for the resource ID based on the Azure Resource Manager URL.
163+
164+
> [!NOTE]
165+
> Events may take at least 15-30 mins to appear in the Activity Log from the time key vault access issue occurs.
163166
164167
**Event when the service loses access to the Azure Key Vault key**
165168

@@ -169,36 +172,17 @@ EventName: MakeDatabaseInaccessible
169172

170173
Status: Started
171174

172-
Description: Database has lost access to Azure key vault key and is now inaccessible.
175+
Description: Database {database_name} on Server {server_name} has lost access to Azure Key Vault Key and is now transitioning to inaccessible state.
173176

174177
**Azure SQL Managed Instance**
175178

176-
EventName: MakeManagedDbInaccessible
179+
EventName: MakeManagedDatabaseInaccessible
177180

178181
Status: Started
179182

180-
Description: Database on managed server has lost access to Azure Key Vault Key and is now transitioning to inaccessible state.
181-
182-
183-
**Event when the database has automatically come back online**
184-
185-
**Azure SQL Database**
186-
187-
EventName: MakeDatabaseAccessible
188-
189-
Status: Succeeded
190-
191-
Description: Database access to Azure key vault key has been reestablished and database is now online.
192-
193-
**Azure SQL Managed Instance**
194-
195-
EventName: MakeManagedDbAccessible
183+
Description: Database { database_name} on managed server {server_name} has lost access to Azure Key Vault Key and is now transitioning to inaccessible state.
196184

197-
Status: Succeeded
198185

199-
Description: Access to Azure Key Vault Key has been re-established and all managed databases in server is now online.
200-
201-
202186
**Event when the issue wasn’t resolved within 30 minutes and Azure Key Vault key access has to be validated manually**
203187

204188
**Azure SQL Database**
@@ -211,49 +195,49 @@ Description: Database is inaccessible and requires user to resolve Azure key vau
211195

212196
**Azure SQL Managed Instance**
213197

214-
EventName: MakeManagedDbInaccessible
198+
EventName: MakeManagedDatabaseInaccessible
215199

216200
Status: Succeeded
217201

218-
Description: Database on managed server is inaccessible and requires user to re-establish access to Azure Key Vault Key.
219-
220-
221-
**Event when db comes online after manual key re-validation**
202+
Description: Database { database_name} on managed server {server_name} is inaccessible and requires user to re-establish access to Azure Key Vault Key.
203+
204+
205+
**Event when re-validation of Azure Key Vault key access has succeeded and the db is coming back online**
222206

223207
**Azure SQL Database**
224208

225209
EventName: MakeDatabaseAccessible
226210

227-
Status: Succeeded
211+
Status: Started
228212

229-
Description: Database access to Azure key vault key has been reestablished and database is now online.
213+
Description: Access to Azure Key Vault Key has been re-established, operation to make database {database_name} on server {server_name} accessible started.
230214

231215
**Azure SQL Managed Instance**
232216

233-
EventName: MakeManagedDbAccessible
217+
EventName: MakeManagedDatabaseAccessible
234218

235-
Status: Succeeded
219+
Status: Started
236220

237-
Description: Access to Azure Key Vault Key has been re-established and all managed databases in server is now online.
238-
221+
Description: Access to Azure Key Vault Key has been re-established, operation to make database {database_name} on managed server {server_name} accessible started.
239222

240-
**Event when re-validation of Azure Key Vault key access has succeeded and the db is coming back online**
223+
224+
**Event when the database has successfully come back online**
241225

242226
**Azure SQL Database**
243227

244-
EventName: MakeDatabaseAccessible
228+
EventName: MakeDatabaseAccessible
245229

246-
Status: Started
230+
Status: Succeeded
247231

248-
Description: Restoring database access to Azure key vault key has started.
232+
Description: Access to Azure Key Vault Key has been re-established and database {database_name} on server {server_name} is now online.
249233

250234
**Azure SQL Managed Instance**
251235

252-
EventName: MakeManagedDbAccessible
236+
EventName: MakeManagedDatabaseAccessible
253237

254-
Status: Started
238+
Status: Succeeded
255239

256-
Description: Access to Azure Key Vault Key has been re-established, operation to make all databases accessible in managed server started
240+
Description: Access to Azure Key Vault Key has been re-established and database {database_name} on managed server {server_name} is now online.
257241

258242

259243
**Event when re-validation of Azure Key Vault key access has failed**
@@ -264,15 +248,15 @@ EventName: MakeDatabaseAccessible
264248

265249
Status: Failed
266250

267-
Description: Restoring database access to Azure key vault key has failed.
251+
Description: Access to Azure Key Vault Key has been re-established, operation to make database {database_name} accessible on server {server_name} failed
268252

269253
**Azure SQL Managed Instance**
270254

271-
EventName: MakeManagedDbAccessible
255+
EventName: MakeManagedDatabaseAccessible
272256

273257
Status: Failed
274258

275-
Description: Restoring database access to Azure key vault key has failed.
259+
Description: Access to Azure Key Vault Key has been re-established, operation to make database {database_name} accessible on managed server {server_name} failed
276260

277261

278262
## Next steps

0 commit comments

Comments
 (0)