Networking

28
Total Pages
20
Linux-Friendly Pages
8
Pages with Bias
28.6%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

37 issues found
Showing 26-37 of 37 flagged pages
Networking Troubleshoot Azure Microsoft.Network failed Provisioning State .../main/articles/networking/troubleshoot-failed-state.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively uses Azure PowerShell cmdlets for all troubleshooting steps, with instructions to install and use PowerShell. There are no examples or guidance for using Azure CLI, Bash, or other cross-platform tools. The instructions assume access to PowerShell, which is traditionally a Windows tool, and do not mention Linux/macOS alternatives or parity. This creates friction for users on Linux or macOS who may prefer or only have access to Bash/Azure CLI.
Recommendations
  • Add equivalent Azure CLI (az) commands for each resource type alongside PowerShell examples.
  • Include installation and usage instructions for Azure CLI on Linux/macOS.
  • Explicitly state that PowerShell Core is available cross-platform, if PowerShell is required, and provide guidance for Linux/macOS users.
  • Present examples for both PowerShell and CLI in parallel, or allow users to select their preferred shell.
  • Clarify any differences or limitations between PowerShell and CLI approaches.
GitHub Create Pull Request
Networking Accelerated connections network performance optimization on NVAs and VMs ...ain/articles/networking/nva-accelerated-connections.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation lists PowerShell as the first supported enablement method, which may suggest a Windows-centric approach. While other cross-platform tools (ARM templates, Azure CLI, Terraform, SDK) are mentioned, there are no explicit Linux-specific examples or references. The absence of Linux shell examples and the prioritization of PowerShell could make Linux users feel secondary.
Recommendations
  • List cross-platform tools (Azure CLI, Terraform) before PowerShell to avoid Windows-first impression.
  • Provide explicit Linux shell (bash) examples alongside PowerShell, especially for common deployment scenarios.
  • Clarify that Azure CLI, Terraform, and ARM templates are fully supported on Linux and macOS.
  • Include a note or section addressing Linux users and best practices for enabling Accelerated Connections from Linux environments.
GitHub Create Pull Request
Networking Accelerated connections network performance optimization on NVAs and VMs ...ain/articles/networking/nva-accelerated-connections.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation lists PowerShell as the first supported enablement method, which may suggest a Windows-centric approach. There are no explicit Linux-specific examples or tools mentioned, and PowerShell is highlighted before cross-platform tools like Azure CLI and Terraform. No Linux shell or command-line examples are provided.
Recommendations
  • List cross-platform tools (Azure CLI, Terraform) before PowerShell to avoid implying Windows preference.
  • Provide explicit Linux shell (bash) examples for feature enablement alongside PowerShell examples.
  • Clarify that all listed methods (CLI, Terraform, ARM templates) are fully supported on Linux and macOS, not just Windows.
  • Include a note or section about Linux compatibility and best practices for Linux-based NVAs/VMs.
GitHub Create Pull Request
Networking https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/networking/check-usage-against-limits.md ...main/articles/networking/check-usage-against-limits.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents PowerShell examples and instructions before Azure CLI, and provides detailed setup steps for PowerShell (including module installation and login) that are specific to Windows environments. The PowerShell section is more verbose and assumes familiarity with Windows tooling, while the Azure CLI section is less detailed and does not mention Linux-specific considerations. There are no explicit Linux shell examples or references to Linux-specific usage patterns.
Recommendations
  • Provide Linux shell (bash/zsh) examples and usage notes, especially for Azure CLI.
  • Mention installation and login steps for Azure CLI on Linux and macOS, not just Windows.
  • Balance the detail level between PowerShell and Azure CLI sections, ensuring parity in setup and troubleshooting guidance.
  • Consider listing Azure CLI before PowerShell, as it is cross-platform and often preferred on Linux/macOS.
  • Explicitly state that Azure Cloud Shell supports both bash and PowerShell, and clarify which examples are suitable for which environments.
GitHub Create Pull Request
Networking https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/networking/nva-accelerated-connections.md ...ain/articles/networking/nva-accelerated-connections.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation lists PowerShell as the first supported enablement method, which may imply a Windows-first approach. While other cross-platform tools (ARM templates, Azure CLI, Terraform, SDK) are mentioned, there are no explicit Linux or Bash examples, and PowerShell is the only shell called out by name. No Linux-specific tools or usage patterns are referenced.
Recommendations
  • List cross-platform tools (e.g., Azure CLI, Terraform) before PowerShell to avoid implying a Windows-first workflow.
  • Provide explicit Linux/Bash command examples alongside or before PowerShell examples, if any are included.
  • Clarify that all listed tools (except PowerShell) are cross-platform and provide links to Linux installation guides where relevant.
  • If PowerShell is included, consider also mentioning PowerShell Core (pwsh), which is cross-platform, or clarify when Windows-only PowerShell is required.
GitHub Create Pull Request
Networking https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/networking/nva-accelerated-connections.md ...ain/articles/networking/nva-accelerated-connections.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation lists PowerShell as the first supported enablement method, which may indicate a Windows-first or PowerShell-heavy bias. While other cross-platform tools (ARM templates, Azure CLI, Terraform, SDK) are mentioned, there are no explicit Linux-specific examples or references. No command-line examples are provided, so there is no outright omission of Linux, but the ordering and emphasis on PowerShell could suggest a preference for Windows tooling.
Recommendations
  • List cross-platform tools (Azure CLI, Terraform) before or alongside PowerShell to avoid implying a Windows-first approach.
  • Provide explicit Linux and Windows examples for each enablement method, especially for Azure CLI and PowerShell.
  • Clarify that all listed methods (except PowerShell) are fully supported on Linux, and provide links to relevant Linux documentation.
  • If possible, add a section or callout for Linux administrators to ensure parity and inclusivity.
GitHub Create Pull Request
Networking https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/networking/nva-accelerated-connections.md ...ain/articles/networking/nva-accelerated-connections.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation lists PowerShell as the first supported enablement method and does not provide any explicit Linux-specific examples or mention of Linux-native tools. While Azure CLI and Terraform are mentioned, the prominence of PowerShell and the lack of Linux command-line examples or references suggest a subtle Windows bias.
Recommendations
  • Provide explicit Linux command-line examples (e.g., bash scripts) for enabling the feature.
  • List Azure CLI or Terraform before PowerShell to avoid implying Windows-first workflows.
  • Clarify that all enablement methods are cross-platform where applicable, and provide sample commands for both Windows (PowerShell) and Linux (bash/CLI).
  • Include references to Linux-native tools or workflows where relevant.
GitHub Create Pull Request
Networking https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/networking/check-usage-against-limits.md ...main/articles/networking/check-usage-against-limits.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents PowerShell instructions and context before Azure CLI, and provides more detailed setup and troubleshooting guidance for PowerShell users. This ordering and emphasis may favor Windows users, as PowerShell is more commonly associated with Windows environments, even though it is now cross-platform. There is also more detail about PowerShell module installation and versioning than for the Azure CLI, which is more commonly used on Linux.
Recommendations
  • Present Azure CLI instructions before or alongside PowerShell instructions, as the CLI is cross-platform and widely used on Linux.
  • Provide equal detail for Azure CLI setup, including troubleshooting and version checks, similar to what is given for PowerShell.
  • Explicitly mention that both PowerShell and Azure CLI are available on Windows, Linux, and macOS, and provide links to installation guides for all platforms.
  • Include example shell commands for both Bash (Linux/macOS) and PowerShell where appropriate, or clarify that the examples work cross-platform.
  • Avoid assuming PowerShell is the default or primary scripting environment; instead, present both options neutrally.
GitHub Create Pull Request
Networking https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/networking/create-zero-trust-network-web-apps.md ...icles/networking/create-zero-trust-network-web-apps.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by specifying Windows as the operating system for the App Service deployment and omitting any Linux-based deployment options or examples. The runtime stack is set to .NET 6 (LTS), and the OS is explicitly set to Windows, with no mention of Linux alternatives. There are no CLI, PowerShell, or Bash script examples, but the step-by-step instructions are all portal-based and default to Windows where an OS choice is relevant. No Linux tools, patterns, or parity guidance are provided.
Recommendations
  • When specifying App Service deployment, include both Windows and Linux as supported OS options, and provide instructions for both.
  • Where a runtime stack is chosen (e.g., .NET 6), mention that it is available on both Windows and Linux, and show how to select either.
  • Add a note or section for deploying the solution using Azure CLI or ARM/Bicep templates, which are cross-platform and do not assume a Windows environment.
  • Explicitly mention that the steps are applicable to both Windows and Linux App Service plans, and highlight any differences.
  • If Visual Studio Code is recommended, clarify that it is cross-platform and provide links or notes for Linux users.
GitHub Create Pull Request
Networking Accelerated connections network performance optimization on NVAs and VMs ...ain/articles/networking/nva-accelerated-connections.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation lists PowerShell as the first supported enablement method, which may suggest a Windows-first bias. While other cross-platform tools (ARM templates, Azure CLI, Terraform, SDK) are mentioned, there are no explicit Linux/macOS examples or guidance, and PowerShell is highlighted before Azure CLI, which is more commonly used on Linux/macOS.
Recommendations
  • List Azure CLI before PowerShell in enablement methods to reflect cross-platform parity.
  • Provide explicit examples or guidance for Linux/macOS users, especially for Azure CLI and Terraform.
  • Clarify that PowerShell examples are also available on Linux/macOS (if true), or provide equivalent CLI commands.
  • Ensure future documentation includes step-by-step instructions for both Windows and Linux/macOS environments.
GitHub Create Pull Request
Networking Customer intent: As a network administrator, I want to count and list public IP addresses and analyze network security groups, so that I can effectively manage and optimize our cloud networking resources. ...s/blob/main/articles/networking/includes/networking.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal for each scenario. In each case, Azure CLI (cross-platform) is presented first, followed by Azure PowerShell (Windows-centric), and then the Portal. There are no explicit Linux/macOS-specific examples, but the CLI examples are generally applicable. However, PowerShell is always given as a separate tab, which may reinforce a Windows-centric workflow. There are no references to Windows-only tools or patterns, and no critical steps are Windows-exclusive.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux/macOS and Windows.
  • Add example shell commands for Bash/zsh (Linux/macOS) where quoting/escaping differs.
  • Clarify any differences in command usage or output between platforms, especially for shell quoting.
  • Consider adding a 'Linux/macOS' tab or section for parity with the dedicated PowerShell tab.
  • Mention that PowerShell Core is available cross-platform, if relevant.
GitHub Create Pull Request
Networking Accelerated connections network performance optimization on NVAs and VMs ...ain/articles/networking/nva-accelerated-connections.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation lists PowerShell as the first supported enablement method and mentions ARM templates via Azure portal, Azure CLI, Terraform, and SDKs. No explicit Linux/macOS examples or tools are prioritized, and PowerShell (a Windows-centric tool) is given prominence, which may suggest a Windows-first bias.
Recommendations
  • List cross-platform tools (Azure CLI, Terraform, SDKs) before PowerShell to emphasize Linux/macOS parity.
  • Provide explicit Linux/macOS command examples, especially for Azure CLI and Terraform.
  • Clarify that PowerShell Core is available cross-platform if relevant, or recommend Azure CLI for Linux/macOS users.
  • Add a note or section addressing enablement from Linux/macOS environments.
GitHub Create Pull Request
← Previous Page 2 of 2 Next →