This article explains how to securely connect to a Kepion SQL database from SQL Server Management Studio (SSMS) on your local machine.
Before you start
Before connecting to a Kepion SQL database, ensure the following requirements are met:
-
SQL Server Management Studio (SSMS)
Version 18.x or later must be installed.
Alternatively, you may use another SQL client that supports Microsoft Entra ID authentication.
-
Kepion VPN
Azure VPN Client is installed on your machine.
The Kepion VPN profile has been installed or imported into the Azure VPN Client.
Your user account has VPN access to the target Kepion environment.
Refer to Connect to VPN using Azure VPN Client if needed.
Step 1. Connect to the Kepion VPN
Launch the Azure VPN client.
Connect to the Kepion VPN.
Confirm the VPN connection is active.
Important: If the Kepion VPN is not connected, the SQL Server will not be reachable and the connection attempt will fail.
Step 2. Open SQL Server Management Studio
Launch SQL Server Management Studio (SSMS).
Click Connect → Database Engine.
Step 3. Enter connection details
In the Connect to Server dialog, enter the following:
Server type: Database Engine
Server name: Enter the IP address of the Kepion-hosted SQL Server
Authentication: Select Microsoft Entra MFA
User name: Enter your User Principal Name (UPN) — this is typically your work email address (e.g., user@company.com)
Encryption: Mandatory
Check the box for Trust server certificate
Click Connect.
Step 4. Authenticate with Microsoft Entra ID
A browser window will open for authentication.
Select your Microsoft Entra account.
Complete Multi-Factor Authentication (MFA) as prompted.
Close the browser window once authentication is complete.
Step 5. Verify the connection
After successful authentication, the connection will complete and the databases you have access to will appear in Object Explorer.
Troubleshooting tips
Confirm the Kepion VPN is connected before launching SSMS.
Double-check the server name and authentication method.
If the connection fails, disconnect and reconnect the VPN, then try again.
For further assistance, please submit a support request at our Help Center.