Skip to content

Commit a3e81a0

Browse files
authored
Merge pull request #15442 from MicrosoftDocs/VanMSFT-patch-2
Removing whiltelisted from doc
2 parents eb615a7 + 7096538 commit a3e81a0

1 file changed

Lines changed: 5 additions & 5 deletions

File tree

docs/relational-databases/security/encryption/sql-server-connector-maintenance-troubleshooting.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -141,9 +141,9 @@ If the vault has been lost, you will need to recreate a vault and restore the as
141141
142142
In summary, here are the steps:
143143
144-
* Back up the vault key (using the Backup-AzureKeyVaultKey Powershell cmdlet).
144+
* Back up the vault key (using the Backup-AzureKeyVaultKey PowerShell cmdlet).
145145
* In the case of vault failure, create a new vault in the same geographic region*. The user creating this should be in the same default directory as the service principal setup for SQL Server.
146-
* Restore the key to the new vault (using the Restore-AzureKeyVaultKey Powershell cmdlet - this restores the key using the same name as before). If there is already a key with the same name, the restore will fail.
146+
* Restore the key to the new vault (using the Restore-AzureKeyVaultKey PowerShell cmdlet - this restores the key using the same name as before). If there is already a key with the same name, the restore will fail.
147147
* Grant permissions to the SQL Server service principal to use this new vault.
148148
* Modify the SQL Server credential used by the Database Engine to reflect the new vault name (if needed).
149149
@@ -162,7 +162,7 @@ Key backups can be restored across Azure regions, as long as they remain in the
162162
### On Configuring [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)]
163163
164164
**What are the endpoints that the SQL Server Connector needs access to?**
165-
The Connector talks to two endpoints, which need to be whitelisted. The only port required for outbound communication to these other services is 443 for Https:
165+
The Connector talks to two endpoints, which need to be allowed. The only port required for outbound communication to these other services is 443 for Https:
166166
- login.microsoftonline.com/*:443
167167
- *.vault.azure.net/*:443
168168
@@ -211,7 +211,7 @@ Error code |Symbol |Description
211211
5 | scp_err_AuthFailure | The authentication has failed with EKM provider.
212212
6 | scp_err_InvalidArgument | The provided argument is invalid.
213213
7 | scp_err_ProviderError | There is an unspecified error happened in EKM provider that is caught by SQL engine.
214-
401 | acquireToken | Server responded 401 for the request. Make sure the client Id and secret are correct, and the credential string is a concatenation of AAD client Id and secret without hyphens.
214+
401 | acquireToken | Server responded 401 for the request. Make sure the client ID and secret are correct, and the credential string is a concatenation of AAD client ID and secret without hyphens.
215215
404 | getKeyByName | The server responded 404, because the key name was not found. Please make sure the key name exists in your vault.
216216
2049 | scp_err_KeyNameDoesNotFitThumbprint | The key name is too long to fit into SQL engine's thumbprint. The key name must not exceed 26 characters.
217217
2050 | scp_err_PasswordTooShort | The secret string that is the concatenation of AAD client ID and secret is shorter than 32 characters.
@@ -251,7 +251,7 @@ If you don't see your error code in this table, here are some other reasons the
251251
252252
- If you receive a "Cannot load library" error, make sure you have the appropriate version of the Visual Studio C++ redistributable installed based on the version of SQL Server that you are running. The table below specifies which version to install from the Microsoft Download Center.
253253
254-
The Windows event log also logs errors associated with the SQL Server Connnector, which can help with additional context on why the error is actually happening. The source in the Windows Application Event Log will be "SQL Server Connector for Microsoft Azure Key Vault".
254+
The Windows event log also logs errors associated with the SQL Server Connector, which can help with additional context on why the error is actually happening. The source in the Windows Application Event Log will be "SQL Server Connector for Microsoft Azure Key Vault".
255255
256256
SQL Server Version |Redistributable Install Link
257257
---------|---------

0 commit comments

Comments
 (0)