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:
⚠️ powershell_heavy
⚠️ missing_linux_example
⚠️ windows_first
Summary:
The documentation page demonstrates a Windows bias by providing only Azure PowerShell CLI examples for automation, omitting equivalent Azure CLI (cross-platform) or Bash scripts. Additionally, the validation steps explicitly instruct users to create and use a Windows virtual machine, with no mention of Linux alternatives or parity. This prioritizes Windows tools and environments, leaving Linux users without direct guidance.
Recommendations:
  • Provide equivalent Azure CLI (az) and/or Bash examples alongside the PowerShell automation steps, ensuring Linux and macOS users have clear instructions.
  • In the validation section, offer instructions for creating and using a Linux virtual machine, including relevant command-line examples (e.g., using dig or nslookup on Linux).
  • Where possible, use neutral language and cross-platform tools (e.g., Azure CLI, REST API) as the primary automation example, or present both Windows and Linux options in parallel.
  • Explicitly state that the steps can be performed from any supported OS, and link to both Windows and Linux VM creation guides.
GitHub 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 ❌ Biased
2025-07-12 23:44 #41 in_progress ❌ Biased

Flagged Code Snippets

## Manage private endpoints using Azure portal When you create a private endpoint, the connection must be approved. If the resource for which you're creating a private endpoint is in your directory, you can approve the connection request provided you have sufficient permissions. If you're connecting to an Azure resource in another directory, you must wait for the owner of that resource to approve your connection request. There are four provisioning states: | Service action | Service consumer private endpoint state | Description | |--|--|--| | None | Pending | Connection is created manually and is pending approval from the Private Link resource owner. | | Approve | Approved | Connection was automatically or manually approved and is ready to be used. | | Reject | Rejected | Connection was rejected by the private link resource owner. | | Remove | Disconnected | Connection was removed by the private link resource owner. The private endpoint becomes informative and should be deleted for cleanup. | ### Approve, reject, or remove a private endpoint connection 1. Sign in to the Azure portal. 1. In the search bar, type in **Service Bus**. 1. Select the **namespace** that you want to manage. 1. Select the **Networking** tab. 5. See the appropriate following section based on the operation you want to: approve, reject, or remove. ### Reject a private endpoint connection 1. If there are any private endpoint connections you want to reject, whether it's a pending request or existing connection that was approved earlier, select the endpoint connection and select the **Reject** button. :::image type="content" source="./media/private-link-service/private-endpoint-reject.png" alt-text="Screenshot that shows the Private endpoint connections page with the Reject button highlighted." lightbox="./media/private-link-service/private-endpoint-reject.png"::: 2. On the **Reject connection** page, enter an optional comment, and select **Yes**. If you select **No**, nothing happens. :::image type="content" source="./media/private-link-service/reject-connection-page.png" alt-text="Screenshot that shows the Reject connection page."::: 3. You should see the status of the connection in the list changed **Rejected**. :::image type="content" source="./media/private-link-service/endpoint-rejected.png" alt-text="Screenshot that shows the Private endpoint connections page with endpoint rejected." lightbox="./media/private-link-service/endpoint-rejected.png"::: ### Remove a private endpoint connection 1. To remove a private endpoint connection, select it in the list, and select **Remove** on the toolbar. :::image type="content" source="./media/private-link-service/remove-endpoint.png" alt-text="Screenshot that shows the Private endpoint connections page with the Remove button highlighted." lightbox="./media/private-link-service/remove-endpoint.png"::: 2. On the **Delete connection** page, select **Yes** to confirm the deletion of the private endpoint. If you select **No**, nothing happens. :::image type="content" source="./media/private-link-service/delete-connection-page.png" alt-text="Screenshot that shows the Delete connection page."::: 3. You should see the status changed to **Disconnected**. Then, the endpoint disappears from the list. ### Approve a private endpoint connection 1. If there are any connections that are pending, you see a connection listed with **Pending** in the provisioning state. 2. Select the **private endpoint** you wish to approve 3. Select the **Approve** button on the toolbar. 4. On the **Approve connection** page, enter an optional **comment**, and select **Yes**. If you select **No**, nothing happens. 5. You should see the status of the connection in the list changed to **Approved**. ## Validate that the private link connection works You should validate that resources within the virtual network of the private endpoint are connecting to your Service Bus namespace over a private IP address, and that they have the correct private DNS zone integration. First, create a virtual machine by following the steps in [Create a Windows virtual machine in the Azure portal](/azure/virtual-machines/windows/quick-create-portal) In the **Networking** tab: 1. Specify **Virtual network** and **Subnet**. You must select the Virtual Network on which you deployed the private endpoint. 2. Specify a **public IP** resource. 3. For **NIC network security group**, select **None**. 4. For **Load balancing**, select **No**. Connect to the VM, open the command line, and run the following command: