Document Details
Quick Secure Virtual Hub Bicep
❌
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
Summary:
The documentation demonstrates a Windows bias by exclusively deploying and referencing Windows Server virtual machines for firewall testing, instructing users to use Remote Desktop and Internet Explorer (both Windows-specific tools), and omitting any Linux VM deployment or Linux-based connectivity/browser examples. While the deployment and validation steps use both Azure CLI and PowerShell, the scenario for testing the firewall is entirely Windows-centric.
Recommendations:
- Include Linux virtual machine deployment in the Bicep template or as an alternative testing scenario.
- Provide instructions for connecting to Linux VMs (e.g., using SSH) and testing connectivity (e.g., using curl, wget, or a Linux browser like Firefox).
- Mention Linux tools and workflows alongside Windows ones, such as using SSH instead of RDP and command-line browsers or curl for connectivity tests.
- Balance the documentation by showing both Windows and Linux examples for firewall rule validation.
- Avoid assuming the use of Internet Explorer or Windows-only features; offer cross-platform alternatives.
Create pull request
Scan History
| Date | Scan ID | Status | Bias Status |
|---|---|---|---|
| 2025-07-12 23:44 | #41 | in_progress | ❌ Biased |
| 2025-07-12 00:58 | #8 | cancelled | ✅ Clean |
| 2025-07-10 05:06 | #7 | processing | ✅ Clean |
Flagged Code Snippets
New-AzResourceGroup -Name exampleRG -Location eastus
New-AzResourceGroupDeployment -ResourceGroupName exampleRG -TemplateFile ./main.bicep -adminUsername "<admin-user>"
# [PowerShell](#tab/PowerShell)
---
Now, test the firewall rules to confirm that it works as expected.
1. From the Azure portal, review the network settings for the **Workload-Srv** virtual machine and note the private IP address.
2. Connect a remote desktop to **Jump-Srv** virtual machine, and sign in. From there, open a remote desktop connection to the **Workload-Srv** private IP address.
3. Open Internet Explorer and browse to `www.microsoft.com`.
4. Select **OK** > **Close** on the Internet Explorer security alerts.
You should see the Microsoft home page.
5. Browse to `www.google.com`.
You should be blocked by the firewall.
Now you've verified that the firewall rules are working, you can browse to the one allowed FQDN, but not to any others.
## Clean up resources
When you no longer need the resources that you created with the firewall, use Azure portal, Azure CLI, or Azure PowerShell to delete the resource group. This removes the firewall and all the related resources.
# [CLI](#tab/CLI)
# [PowerShell](#tab/PowerShell)