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 Windows Server 2019 virtual machines for testing, instructing users to use Remote Desktop and Internet Explorer (both Windows-specific tools), and omitting any Linux VM deployment or Linux-based testing workflow. While the deployment and validation steps use both Azure CLI and PowerShell (which are cross-platform), all VM interaction and firewall testing instructions assume a Windows environment.
Recommendations:
- Include Linux virtual machine deployment in the Bicep template and documentation, or provide an alternative Linux-based workflow.
- Add instructions for connecting to Linux VMs (e.g., using SSH) and testing firewall rules with Linux tools (such as curl or wget) instead of only using Remote Desktop and Internet Explorer.
- Present both Windows and Linux examples side-by-side when describing how to test connectivity and firewall rules.
- Avoid referencing Windows-specific tools (like Internet Explorer) as the only method for testing, or provide Linux browser/command-line alternatives.
- Clarify that the scenario can be tested with either Windows or Linux VMs, and provide guidance for both.
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-09 13:09 | #3 | cancelled | ✅ Clean |
| 2025-07-08 04:23 | #2 | cancelled | ❌ Biased |
Flagged Code Snippets
---
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)