Document Details
Create Private Endpoint 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
Detected Bias Types
windows_first
missing_linux_example
powershell_heavy
windows_tools
Summary
The documentation demonstrates a Windows bias in several ways: the VM creation example uses a Windows image (Win2022Datacenter) without mentioning or providing a Linux alternative; the connectivity test instructs users to open PowerShell and does not mention Linux shells or commands; and the overall flow assumes a Windows environment for testing and interaction. There are no Linux-specific instructions or parity in examples, and Windows tools (PowerShell) are referenced exclusively.
Recommendations
- Provide parallel Linux examples throughout, such as creating a VM with a popular Linux image (e.g., UbuntuLTS) alongside the Windows example.
- In the connectivity test section, include Linux shell commands (e.g., using bash and nslookup or dig) and clarify that the steps apply to both Windows and Linux VMs.
- Explicitly mention that the Azure CLI commands work cross-platform and that users can choose either Windows or Linux VMs for testing.
- Where PowerShell is referenced, also mention the equivalent Linux shell (bash) and provide command syntax for both.
- Consider alternating the order of Windows and Linux examples or presenting them side-by-side to avoid a 'windows_first' impression.
Create Pull Request
Scan History
| Date | Scan | Status | Result |
|---|---|---|---|
| 2026-01-14 00:00 | #250 | in_progress |
Biased
|
| 2026-01-13 00:00 | #246 | completed |
Biased
|
| 2026-01-11 00:00 | #240 | completed |
Biased
|
| 2026-01-10 00:00 | #237 | completed |
Biased
|
| 2026-01-09 00:34 | #234 | completed |
Biased
|
| 2026-01-08 00:53 | #231 | completed |
Biased
|
| 2026-01-06 18:15 | #225 | cancelled |
 Clean
|
| 2025-08-17 00:01 | #83 | cancelled |
Clean
|
| 2025-07-13 21:37 | #48 | completed |
Clean
|
| 2025-07-12 23:44 | #41 | cancelled |
Biased
|
Flagged Code Snippets
>[!NOTE]
>Virtual machines in a virtual network with a bastion host don't need public IP addresses. Bastion provides the public IP, and the VMs use private IPs to communicate within the network. You can remove the public IPs from any VMs in bastion hosted virtual networks. For more information, see [Dissociate a public IP address from an Azure VM](../virtual-network/ip-services/remove-public-ip-address-vm.md).
[!INCLUDE [ephemeral-ip-note.md](~/reusable-content/ce-skilling/azure/includes/ephemeral-ip-note.md)]
## Test connectivity to the private endpoint
Use the virtual machine that you created earlier to connect to the web app across the private endpoint.
1. In the search box at the top of the portal, enter **Virtual machine**. Select **Virtual machines**.
1. Select **vm-1**.
1. On the overview page for **vm-1**, select **Connect**, and then select the **Bastion** tab.
1. Select **Use Bastion**.
1. Enter the username and password that you used when you created the VM.
1. Select **Connect**.
1. After you've connected, open PowerShell on the server.
1. Enter `nslookup webapp-1.azurewebsites.net`. You receive a message that's similar to the following example: