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 EFLOW) instructions, but the Windows/PowerShell tooling is emphasized for EFLOW scenarios. Several steps for EFLOW require the use of custom PowerShell cmdlets (e.g., Copy-EflowVMFile, Connect-EflowVm, Invoke-EflowVmCommand), and these tools are referenced before or instead of standard cross-platform alternatives. The Linux path uses standard Bash commands, while the Windows/EFLOW path assumes the user is operating from a Windows host using PowerShell, potentially limiting accessibility for users on non-Windows platforms. There is also a slight 'windows_first' bias in the EFLOW sections, where Windows-specific instructions and tools are introduced before cross-platform or Linux-native alternatives.
Recommendations:
- Where possible, provide cross-platform alternatives to PowerShell cmdlets for EFLOW, such as using SSH/SCP from Linux/macOS hosts to the EFLOW VM.
- Clarify that EFLOW is a Windows-specific scenario, but highlight how similar tasks can be accomplished from non-Windows hosts if possible.
- In the EFLOW sections, mention standard Linux tools (e.g., scp, ssh) as alternatives to PowerShell cmdlets for copying files and executing commands, or explain any limitations.
- Ensure that Linux and Windows instructions are presented with equal prominence and detail, and avoid assuming the user is operating from a Windows host when working with EFLOW.
- Consider adding a table or section summarizing all possible ways (Windows/PowerShell, Linux/SSH, etc.) to interact with the EFLOW VM for certificate management and port configuration.
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
# If the certificate and keys directories don't exist, create, set ownership, and set permissions
sudo mkdir -p /var/aziot/certs
sudo chown aziotcs:aziotcs /var/aziot/certs
sudo chmod 755 /var/aziot/certs
sudo mkdir -p /var/aziot/secrets
sudo chown aziotks:aziotks /var/aziot/secrets
sudo chmod 700 /var/aziot/secrets
# 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"