Document Details
How To Create Transparent Gateway
❌
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
⚠️
windows_tools
⚠️
windows_first
Summary:
The documentation provides both Linux and Windows (specifically IoT Edge for Linux on Windows/EFLOW) instructions, but Windows/PowerShell-specific tooling and workflows are heavily emphasized in the EFLOW sections. PowerShell cmdlets (e.g., Copy-EflowVMFile, Connect-EflowVm, Invoke-EflowVmCommand) are used exclusively for file transfer and port management on EFLOW, with no mention of alternative Linux-native or cross-platform methods. The EFLOW (Windows) instructions are more detailed in terms of Windows-specific tooling, and PowerShell is presented as the primary interface for EFLOW management, which may disadvantage users more familiar with Linux-native workflows. The Linux instructions are present and functional, but the Windows/PowerShell approach is more prominent and sometimes appears first or with more detailed steps.
Recommendations:
- For EFLOW, provide alternative instructions using standard SSH/SCP/SFTP for file transfer and remote command execution, not just PowerShell cmdlets, to support users on non-Windows platforms or those preferring Linux-native tools.
- Where PowerShell is used for port management (e.g., opening ports with Invoke-EflowVmCommand), offer equivalent instructions for users who may access EFLOW via SSH or other means.
- Clarify that PowerShell cmdlets are one option and that standard Linux tools can also be used within the EFLOW VM, making the documentation more inclusive for Linux users.
- Consider presenting Linux-native instructions first or in parallel, rather than defaulting to Windows/PowerShell-centric workflows for EFLOW.
- Explicitly mention cross-platform alternatives and note any limitations or prerequisites for each approach.
Create pull request
Scan History
| Date | Scan ID | Status | Bias Status |
|---|---|---|---|
| 2025-09-16 00:00 | #113 | completed | ✅ Clean |
| 2025-09-15 00:00 | #112 | completed | ✅ Clean |
| 2025-09-14 00:00 | #111 | completed | ✅ Clean |
| 2025-09-13 00:00 | #110 | completed | ✅ Clean |
| 2025-09-12 00:00 | #109 | completed | ✅ Clean |
| 2025-09-11 00:00 | #108 | completed | ✅ Clean |
| 2025-09-10 00:00 | #107 | completed | ✅ Clean |
| 2025-09-09 00:00 | #106 | completed | ✅ Clean |
| 2025-09-08 00:00 | #105 | completed | ✅ Clean |
| 2025-09-07 00:00 | #104 | completed | ✅ Clean |
| 2025-09-06 00:00 | #103 | completed | ✅ Clean |
| 2025-09-05 00:00 | #102 | completed | ✅ Clean |
| 2025-09-04 00:00 | #101 | completed | ✅ Clean |
| 2025-09-03 00:00 | #100 | completed | ✅ Clean |
| 2025-08-29 00:01 | #95 | completed | ✅ Clean |
| 2025-08-27 00:01 | #93 | in_progress | ✅ Clean |
| 2025-08-22 00:01 | #88 | completed | ✅ Clean |
| 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 |
| 2025-07-09 13:09 | #3 | cancelled | ✅ Clean |
| 2025-07-08 04:23 | #2 | cancelled | ❌ Biased |
Flagged Code Snippets
# Copy the Edge CA certificate and key
Copy-EflowVMFile -fromFile <path>\certs\iot-edge-device-ca-<cert name>-full-chain.cert.pem -toFile ~/iot-edge-device-ca-<cert name>-full-chain.cert.pem -pushFile
Copy-EflowVMFile -fromFile <path>\private\iot-edge-device-ca-<cert name>.key.pem -toFile ~/iot-edge-device-ca-<cert name>.key.pem -pushFile
# Copy the root CA certificate
Copy-EflowVMFile -fromFile <path>\certs\azure-iot-test-only.root.ca.cert.pem -toFile ~/azure-iot-test-only.root.ca.cert.pem -pushFile
Connect-EflowVm
# Open MQTT port
Invoke-EflowVmCommand "sudo iptables -A INPUT -p tcp --dport 8883 -j ACCEPT"
# Open AMQP port
Invoke-EflowVmCommand "sudo iptables -A INPUT -p tcp --dport 5671 -j ACCEPT"
# Open HTTPS/MQTT+WS/AMQP+WS port
Invoke-EflowVmCommand "sudo iptables -A INPUT -p tcp --dport 443 -j ACCEPT"
# Save the iptables rules
Invoke-EflowVmCommand "sudo iptables-save | sudo tee /etc/systemd/scripts/ip4save"