Document Details
Tutorial Private Endpoint Sql Cli
❌
This page contains Windows bias
About This Page
This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.
Bias Analysis
Bias Types:
⚠️
windows_first
⚠️
missing_linux_example
⚠️
windows_tools
⚠️
powershell_heavy
Summary:
The tutorial demonstrates a strong Windows bias in the testing and connectivity sections. The only example for connecting to the test VM uses a Windows Server image, instructs users to open Windows PowerShell, and uses Windows-specific tools like SQL Server Management Studio (SSMS). There are no instructions or examples for Linux-based VMs, nor for using cross-platform tools (e.g., sqlcmd, Azure Data Studio) to connect to the SQL server. The documentation assumes a Windows environment for testing and omits Linux alternatives.
Recommendations:
- Provide parallel instructions for creating a Linux-based VM (e.g., Ubuntu) in the 'Create test virtual machine' section, including the appropriate --image parameter.
- In the 'Test connectivity to private endpoint' section, include Linux shell equivalents for DNS resolution (e.g., using 'nslookup' or 'dig' in bash) and SQL connectivity (e.g., using 'sqlcmd' or Azure Data Studio).
- Mention and demonstrate cross-platform tools (such as Azure Data Studio and sqlcmd) for connecting to Azure SQL, not just Windows-only tools like SSMS.
- Avoid assuming the use of Windows PowerShell; provide bash or shell command alternatives where appropriate.
- Explicitly state that the tutorial can be followed on both Windows and Linux, and provide branching instructions or notes where steps differ.
Create pull request
Scan History
| Date | Scan ID | Status | Bias Status |
|---|---|---|---|
| 2025-08-17 00:01 | #83 | in_progress | ✅ Clean |
| 2025-07-13 21:37 | #48 | completed | ✅ Clean |
| 2025-07-12 23:44 | #41 | in_progress | ❌ Biased |
Flagged Code Snippets
## Test connectivity to private endpoint
In this section, you use the virtual machine you created in the previous step to connect to the SQL server across the private endpoint.
1. Sign in to the [Azure portal](https://portal.azure.com).
2. Select **Resource groups** in the left-hand navigation pane.
3. Select **CreateSQLEndpointTutorial-rg**.
4. Select **myVM**.
5. On the overview page for **myVM**, select **Connect** then **Bastion**.
6. Select the blue **Use Bastion** button.
7. Enter the username and password that you entered during the virtual machine creation.
8. Open Windows PowerShell on the server after you connect.
9. Enter `nslookup <sqlserver-name>.database.windows.net`. Replace **\<sqlserver-name>** with the name of the SQL server you created in the previous steps. You receive a message similar to what is displayed below:
It can take a few minutes for the Azure Bastion host to deploy.
## Create test virtual machine
In this section, you create a virtual machine that is used to test the private endpoint.
Create a VM with [az vm create](/cli/azure/vm#az-vm-create). When prompted, provide a password to be used as the credentials for the VM:
* Named **myVM**.
* In **CreateSQLEndpointTutorial-rg**.
* In network **myVNet**.
* In subnet **myBackendSubnet**.
* Server image **Win2019Datacenter**.
A private IP address of **10.0.0.5** is returned for the SQL server name. This address is in the subnet of the virtual network you created previously.
10. Install [SQL Server Management Studio](/sql/ssms/download-sql-server-management-studio-ssms?preserve-view=true&view=sql-server-2017) on **myVM**.
11. Open **SQL Server Management Studio**.
12. In **Connect to server**, enter or select this information:
| Setting | Value |
| ------- | ----- |
| Server type | Select **Database Engine**.|
| Server name | Enter **\<sql-server-name>.database.windows.net** |
| Authentication | Select **SQL Server Authentication**. |
| User name | Enter the username you entered during server creation |
| Password | Enter the password you entered during server creation |
| Remember password | Select **Yes**. |
13. Select **Connect**.
14. Browse databases from the left menu.
15. (Optionally) Create or query information from **mysqldatabase**.
16. Close the bastion connection to **myVM**.
## Clean up resources
When you're done using the private endpoint, SQL server, and the VM, delete the resource group and all of the resources it contains: