Document Details
How To Configure Multiple Nics
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
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation is heavily oriented towards Windows, with all configuration steps relying exclusively on PowerShell commands and Windows-specific tools. There are no Linux-native examples or alternative instructions for users who may wish to interact with the EFLOW VM or its networking from a Linux environment. The workflow assumes the user is operating from a Windows host, and Linux commands are only mentioned for in-VM inspection, not for configuration.
Recommendations
- Provide equivalent instructions for managing EFLOW networking from a Linux host, if supported, or clarify host OS limitations.
- Include examples using cross-platform tools (e.g., Azure CLI, SSH) where possible, not just PowerShell cmdlets.
- If PowerShell is required, mention PowerShell Core and its availability on Linux/macOS, and provide guidance for those platforms.
- Add a section explicitly addressing Linux/macOS users, outlining what is and isn't possible from those environments.
- Where only Windows is supported, clearly state this limitation at the start of the article.
Create Pull Request
Scan History
| Date | Scan | Status | Result |
|---|---|---|---|
| 2026-01-14 00:00 | #250 | in_progress |
Biased
|
| 2026-01-13 00:00 | #246 | completed |
Biased
|
| 2026-01-11 00:00 | #240 | completed |
Biased
|
| 2026-01-10 00:00 | #237 | completed |
Biased
|
| 2026-01-09 00:34 | #234 | completed |
Biased
|
| 2026-01-08 00:53 | #231 | completed |
Biased
|
| 2026-01-06 18:15 | #225 | cancelled |
 Clean
|
| 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 | cancelled |
Clean
|
| 2025-08-26 00:00 | #92 | cancelled |
Clean
|
| 2025-08-22 00:01 | #88 | completed |
Clean
|
| 2025-08-17 00:01 | #83 | cancelled |
Clean
|
| 2025-07-13 21:37 | #48 | completed |
Biased
|
| 2025-07-12 23:44 | #41 | cancelled |
Biased
|
| 2025-07-09 13:09 | #3 | cancelled |
Clean
|
| 2025-07-08 04:23 | #2 | cancelled |
Biased
|
Flagged Code Snippets
Connect-EflowVm
Get-EflowVmEndpoint
Get-VMSwitch -Name "{switchName}" -SwitchType {switchType}
Add-EflowNetwork -vSwitchName "{switchName}" -vSwitchType {switchType}
Add-EflowNetwork -vSwitchName "OnlineExt" -vSwitchType "External"
Get-EflowNetwork -vSwitchName "{switchName}"
Add-EflowVmEndpoint -vSwitchName "{switchName}" -vEndpointName "{EndpointName}"
Add-EflowVmEndpoint -vSwitchName "{switchName}" -vEndpointName "{EndpointName}" -ip4Address "{staticIp4Address}" -ip4GatewayAddress "{gatewayIp4Address}" -ip4PrefixLength "{prefixLength}"
Add-EflowVmEndpoint -vSwitchName "OnlineExt" -vEndpointName "OnlineEndpoint" -ip4Address "192.168.0.103" -ip4GatewayAddress "192.168.0.1" -ip4PrefixLength "24"