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 1-25 of 37 flagged pages
Networking Azure for Network Engineers ...ain/articles/networking/azure-for-network-engineers.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a Windows bias by mentioning PowerShell as a primary management tool alongside Azure CLI, and by referencing PowerShell cmdlets (e.g., Get-AzEffectiveRouteTable) for verification tasks. There are no explicit Linux shell or Bash examples, nor are Linux-specific tools or patterns discussed. The order of tools presented (Portal, PowerShell, CLI) also subtly prioritizes Windows-centric approaches.
Recommendations
  • Include explicit Bash/Azure CLI examples for all management and verification tasks, especially where PowerShell cmdlets are referenced.
  • When listing management tools, present Azure CLI and PowerShell together, or alternate their order to avoid implicit prioritization.
  • Provide Linux shell command equivalents for tasks such as viewing effective routes and security rules (e.g., az network nic show-effective-route-table).
  • Add notes or sections highlighting cross-platform parity, clarifying that all tasks can be performed from Linux, macOS, and Windows.
  • Reference documentation for both PowerShell and Azure CLI/Bash when linking to further reading or examples.
GitHub Create Pull Request
Networking Check Azure resource usage against limits | Microsoft Docs ...main/articles/networking/check-usage-against-limits.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by presenting PowerShell instructions and tooling before Azure CLI (which is more cross-platform), referencing Windows-specific tools (PowerShell, Get-Module), and providing more detailed setup guidance for PowerShell than for Azure CLI. The PowerShell section is positioned before the Azure CLI section, and Windows-centric terminology and instructions (such as module installation and usage of PowerShell locally) are more prominent. There is no explicit mention of Linux-specific patterns or shell environments beyond the Azure Cloud Shell, and no examples using bash scripting or Linux-native tools.
Recommendations
  • Present Azure CLI instructions before PowerShell to prioritize cross-platform usage.
  • Include Linux-specific setup notes (e.g., bash, zsh, package managers) for Azure CLI.
  • Add bash scripting examples for querying and formatting resource usage.
  • Explicitly mention that Azure CLI works natively on Linux and macOS, and provide installation instructions for those platforms.
  • Balance the detail level between PowerShell and Azure CLI sections, ensuring both have equivalent setup and usage guidance.
  • Avoid Windows-centric terminology (e.g., 'run PowerShell from your computer') and use more neutral language (e.g., 'run PowerShell locally on Windows, Linux, or macOS').
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
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal, but omits explicit Linux shell examples (e.g., Bash, zsh) and does not mention Linux-specific usage patterns. Azure PowerShell is featured as a primary method alongside CLI, which can be perceived as Windows-centric. The ordering of examples consistently places Azure CLI first, but the lack of Linux-native shell scripting or tool references means Linux users may not see their workflows represented.
Recommendations
  • Add explicit Bash/zsh examples for running az graph queries, including guidance on escaping quotes and handling output in Linux shells.
  • Include notes or examples for using jq or other Linux-native tools to process az CLI output.
  • Clarify that Azure CLI is cross-platform and provide shell-specific tips for both Windows and Linux users.
  • Consider adding a 'Linux shell' tab alongside CLI and PowerShell to demonstrate parity.
  • Where PowerShell is referenced, note its availability on Linux and provide installation/use instructions if relevant.
GitHub Create Pull Request
Networking Troubleshoot Azure Microsoft.Network failed Provisioning State .../main/articles/networking/troubleshoot-failed-state.md
High Priority View Details →
Scanned: 2026-01-11 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 examples and instructions, with no mention of Azure CLI, Bash, or cross-platform alternatives. The guidance assumes the use of PowerShell (traditionally a Windows tool), including instructions to open a PowerShell console with elevated privileges. There are no Linux-specific or platform-neutral examples, and PowerShell is presented as the default and only method for restoring provisioning state.
Recommendations
  • Add equivalent Azure CLI examples for each resource type, showing how to perform the same Get/Set (or Update) operations using az commands.
  • Include a section describing how to use Bash or shell scripting for these operations, especially for Linux and macOS users.
  • Clarify that Azure PowerShell is available cross-platform, but also provide explicit instructions for Linux/macOS environments (e.g., using pwsh or az CLI).
  • Present both PowerShell and CLI examples side-by-side, or indicate which method is recommended for each platform.
  • Avoid language that implies PowerShell is the only or preferred tool, and mention alternatives at the beginning of the troubleshooting steps.
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
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal. While Azure CLI is cross-platform, Azure PowerShell is primarily associated with Windows environments, and its inclusion as a primary example can signal Windows bias. There are no explicit Linux shell (bash/zsh) or scripting examples, nor is there mention of Linux-specific patterns or tools. The ordering of examples consistently places Azure PowerShell before the Portal, and there is no discussion of Linux-specific considerations (such as shell escaping or scripting integration).
Recommendations
  • Add explicit bash/zsh shell examples for running az graph queries, including guidance on escaping quotes and handling output in Linux environments.
  • Clarify that Azure CLI is cross-platform and provide Linux-specific usage notes where relevant.
  • Consider reordering examples so that cross-platform tools (Azure CLI) are presented before Windows-centric ones (Azure PowerShell), or provide parity in scripting examples for both platforms.
  • Include troubleshooting notes or tips for common Linux shell issues (e.g., quoting, piping output to jq for JSON parsing).
  • If PowerShell is shown, mention that PowerShell Core is available on Linux, and provide Linux installation/usage links.
GitHub Create Pull Request
Networking Check Azure resource usage against limits | Microsoft Docs ...main/articles/networking/check-usage-against-limits.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is featured prominently and described in detail, including instructions for local installation and usage, which is primarily relevant to Windows users. The PowerShell section appears before the Azure CLI section, and Windows-centric tools and patterns (e.g., PowerShell, Get-Module) are mentioned and explained more thoroughly than their Linux equivalents. While Azure CLI is included and can be used cross-platform, the overall tone and ordering favor Windows users.
Recommendations
  • Provide equal detail for Azure CLI usage, including installation and configuration instructions for Linux and macOS.
  • Include explicit examples or notes for running Azure CLI commands on Linux and macOS, such as using package managers (apt, yum, brew).
  • Consider reordering sections so that cross-platform tools (Azure CLI) are presented before Windows-specific tools (PowerShell).
  • Add troubleshooting tips or environment setup instructions for Linux users, similar to those provided for PowerShell.
  • Avoid assuming PowerShell is the default shell; clarify that Azure CLI is available and fully supported on Linux and macOS.
GitHub Create Pull Request
Networking Azure for Network Engineers ...ain/articles/networking/azure-for-network-engineers.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell as a primary management tool for Azure networking, mentioning it before or alongside Azure CLI, and providing a direct link to a PowerShell-specific cmdlet (Get-AzEffectiveRouteTable) for route verification. There are no explicit Linux or Bash examples, nor are Linux-native tools or workflows discussed. The documentation assumes familiarity with Windows-centric management patterns and omits guidance for Linux users.
Recommendations
  • Include explicit Bash/Azure CLI examples for all management tasks, especially for route and NSG verification.
  • Provide links to equivalent Azure CLI documentation and commands (e.g., az network nic show-effective-route-table).
  • Mention Linux and cross-platform management tools equally and early, rather than defaulting to PowerShell.
  • Add sections or notes for Linux users, highlighting any differences or best practices when managing Azure networking from Linux environments.
  • Ensure that all referenced tools and commands are available and documented for both Windows and Linux platforms.
GitHub Create Pull Request
Networking Troubleshoot Azure Microsoft.Network failed Provisioning State .../main/articles/networking/troubleshoot-failed-state.md
High Priority View Details →
Scanned: 2026-01-10 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 page exclusively uses Azure PowerShell cmdlets for all troubleshooting steps, with no mention or examples of Azure CLI, Bash, or other cross-platform tools. The instructions assume use of PowerShell (which is most commonly associated with Windows), including steps like opening a PowerShell console and installing PowerShell modules. There are no Linux-specific or platform-neutral examples, and PowerShell is presented as the default and only method for resolving provisioning state issues.
Recommendations
  • Add equivalent Azure CLI examples for each resource type, showing how to perform the same Get and Set/Update operations using az commands.
  • Include instructions for using Bash or shell environments, which are common on Linux and macOS.
  • Clarify that PowerShell is available cross-platform, but also provide guidance for users who prefer CLI or REST API methods.
  • Reorder or parallelize examples so that Windows/PowerShell and Linux/CLI approaches are presented together, rather than PowerShell-only.
  • Explicitly mention platform neutrality and provide links to documentation for both PowerShell and CLI troubleshooting.
GitHub Create Pull Request
Networking https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/networking/azure-for-network-engineers.md ...ain/articles/networking/azure-for-network-engineers.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell as a primary tool for network verification (e.g., Get-AzEffectiveRouteTable), mentioning PowerShell before Azure CLI in several places, and failing to provide Linux-specific or cross-platform command examples. No Linux shell commands or tools are shown, and the documentation does not address platform differences or provide parity for Linux users.
Recommendations
  • Provide explicit Linux shell (bash) examples using Azure CLI for all tasks currently demonstrated with PowerShell.
  • Reference Azure CLI before or alongside PowerShell when listing management tools, to avoid implying Windows-first workflows.
  • Include notes or sections highlighting cross-platform usage, clarifying that Azure CLI is available on Linux, macOS, and Windows.
  • Add links to Azure CLI documentation and usage guides for Linux users.
  • Where PowerShell cmdlets are mentioned (e.g., Get-AzEffectiveRouteTable), also show the equivalent Azure CLI command (e.g., az network nic show-effective-route-table) with example usage.
GitHub Create Pull Request
Networking https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/networking/includes/networking.md ...s/blob/main/articles/networking/includes/networking.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal, but does not include explicit Linux shell (bash/zsh) or scripting examples. While Azure CLI is cross-platform, the presence of Azure PowerShell examples (which are more commonly used on Windows) and the lack of Linux-specific shell usage or notes may indicate a subtle Windows bias. Additionally, PowerShell examples are always presented alongside CLI, and there is no mention of Linux-specific considerations (such as escaping quotes in bash, or using jq for output parsing).
Recommendations
  • Add explicit bash/zsh examples for each query, showing how to run az graph query in a Linux shell, including any necessary escaping or output parsing.
  • Include notes about differences in shell quoting and escaping between Windows (PowerShell) and Linux (bash/zsh).
  • If output parsing or further scripting is common, provide examples using Linux tools (e.g., jq, grep, awk) to process results.
  • Clarify that Azure CLI is cross-platform and highlight any platform-specific caveats.
  • Consider reordering examples so that cross-platform tools (Azure CLI) are presented before platform-specific ones (PowerShell), or group them together under a 'Scripting' heading.
GitHub Create Pull Request
Networking https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/networking/troubleshoot-failed-state.md .../main/articles/networking/troubleshoot-failed-state.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exclusively provides troubleshooting instructions and examples using Azure PowerShell cmdlets, which are most commonly used on Windows and in PowerShell environments. There are no examples or guidance for using Azure CLI, Bash, or other Linux-native tools. The instructions assume the use of PowerShell consoles and reference installation of PowerShell modules, further reinforcing a Windows-centric approach. This may hinder Linux users or those who prefer cross-platform tooling.
Recommendations
  • Add equivalent Azure CLI examples for each resource type, demonstrating how to perform the same Get/Set or Update operations using az commands.
  • Include notes or sections on how to perform these operations in Bash or other Linux shells, highlighting any differences or caveats.
  • Reference installation and usage of Azure CLI alongside Azure PowerShell, making it clear that both are supported and cross-platform.
  • Rephrase instructions to be tool-agnostic where possible, or present PowerShell and CLI examples side-by-side.
  • Explicitly mention that Azure PowerShell is available on Linux and macOS, but also highlight CLI as a first-class alternative.
GitHub Create Pull Request
Networking https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/networking/includes/networking.md ...s/blob/main/articles/networking/includes/networking.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal for each query. While Azure CLI is cross-platform, Azure PowerShell is primarily associated with Windows environments, and its inclusion as a separate tab may suggest a Windows-centric approach. There are no explicit Linux shell (bash, zsh) or scripting examples, nor is there mention of Linux-specific tooling or usage patterns. The ordering of examples (CLI, then PowerShell, then Portal) is common, but the lack of Linux-specific context or explicit parity can be seen as subtle Windows bias.
Recommendations
  • Add explicit Linux shell (bash/zsh) usage examples, especially for scenarios where escaping or quoting differs from Windows.
  • Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and provide notes on any platform-specific considerations.
  • Consider including scripting examples using bash or other Linux-native tools for advanced scenarios.
  • If PowerShell is included, mention that PowerShell Core is available cross-platform, or provide guidance for Linux users.
  • Review documentation for any assumptions about the user's operating system and make instructions OS-agnostic where possible.
GitHub Create Pull Request
Networking https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/networking/troubleshoot-failed-state.md .../main/articles/networking/troubleshoot-failed-state.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exclusively uses Azure PowerShell cmdlets for all troubleshooting examples, with instructions to install and use PowerShell. There are no examples or guidance for using Azure CLI, Bash, or other cross-platform tools. This creates a strong Windows and PowerShell bias, making the documentation less accessible for Linux and macOS users who may prefer or require non-PowerShell solutions.
Recommendations
  • Add equivalent Azure CLI examples for each resource type, showing how to perform the same Get and Set/Update operations using az commands.
  • Include a section on using Bash or shell scripting for automation, especially for Linux/macOS users.
  • Clarify that Azure PowerShell is available cross-platform, but also highlight and provide parity for Azure CLI and REST API usage.
  • Reorder or balance examples so that PowerShell and CLI/Bash approaches are presented together, or alternate which is shown first.
  • Add guidance for installing and using Azure CLI on Linux and macOS, similar to the PowerShell installation instructions.
GitHub Create Pull Request
Networking https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/networking/azure-for-network-engineers.md ...ain/articles/networking/azure-for-network-engineers.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a Windows bias by mentioning PowerShell as a primary management tool for Azure, referencing PowerShell cmdlets (e.g., Get-AzEffectiveRouteTable) for verification tasks, and listing PowerShell before CLI in navigation instructions. There are no explicit Linux or Bash examples, nor are Linux-specific tools or patterns discussed. The CLI is mentioned, but not demonstrated, and PowerShell is given prominence in both tooling and example references.
Recommendations
  • Provide explicit Bash/Azure CLI examples alongside or before PowerShell examples for all management and verification tasks.
  • Reference Linux-native tools and workflows where applicable, such as using Azure CLI in Bash shells.
  • Include links to Azure CLI documentation and example commands for tasks currently only demonstrated with PowerShell.
  • Ensure that instructions do not default to Windows/PowerShell unless there is a technical reason, and strive for parity in example coverage.
  • Clarify that both Windows and Linux users can manage Azure networking, and highlight cross-platform tooling.
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
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is presented before Azure CLI, and instructions for running PowerShell locally reference Windows-specific installation and usage patterns. The Azure Cloud Shell is mentioned for both PowerShell and CLI, but PowerShell examples and tooling are described in more detail, including module installation and login steps that are Windows-centric. There is no explicit mention of Linux or macOS environments, nor are there any Linux-specific examples or troubleshooting notes.
Recommendations
  • Add explicit instructions for running Azure CLI and PowerShell on Linux and macOS, including installation and login steps.
  • Provide parity in example detail for Azure CLI, such as filtering output for resources with at least one deployed (as shown in the PowerShell example).
  • Include notes about using Bash or other shells on Linux/macOS, and clarify that Azure CLI is cross-platform.
  • Avoid assuming local PowerShell usage is Windows-only; mention PowerShell Core and its availability on Linux/macOS.
  • Balance the order of examples, sometimes presenting Azure CLI before PowerShell, or interleaving them.
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
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is given a prominent, detailed section before Azure CLI, with explicit instructions for installing and using the Azure PowerShell module (a Windows-centric tool). The PowerShell section is more verbose and includes troubleshooting steps for module installation and versioning, which are specific to Windows environments. Although Azure CLI is covered, there is no mention of Linux-specific usage patterns, and the PowerShell/Windows approach is presented first and in greater detail.
Recommendations
  • Alternate the order of PowerShell and Azure CLI sections, or present Azure CLI first to avoid defaulting to Windows-centric tooling.
  • Provide explicit Linux usage notes, such as mentioning that Azure CLI is pre-installed on many Linux distributions and can be installed via package managers like apt or yum.
  • Include example commands for common Linux shells (e.g., bash, zsh) and clarify that Azure CLI is cross-platform.
  • Reduce the emphasis on PowerShell-specific troubleshooting (e.g., module installation/versioning) unless paralleled with Linux/CLI troubleshooting steps.
  • Add a brief section or note about using Azure CLI and Cloud Shell from Linux/macOS environments, highlighting parity and any differences.
GitHub Create Pull Request
Networking https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/networking/azure-for-network-engineers.md ...ain/articles/networking/azure-for-network-engineers.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell and Windows-centric tools (such as Get-AzEffectiveRouteTable) before or instead of Linux equivalents. While Azure CLI is mentioned, PowerShell is often listed first or exclusively, and there are no explicit Linux shell or command-line examples. The documentation does not provide parity for Linux users in terms of command-line instructions or tool references.
Recommendations
  • Ensure all command-line instructions are provided in both Azure CLI and PowerShell, with Azure CLI (which is cross-platform) listed first.
  • Include explicit Linux shell examples or references where relevant, especially for verification tasks.
  • When referencing tools or commands (e.g., Get-AzEffectiveRouteTable), provide the equivalent Azure CLI command (e.g., az network nic show-effective-route-table) and link to its documentation.
  • Avoid using Windows-specific terminology or tools as the default; instead, use cross-platform tools and clarify when a tool is platform-specific.
  • Add a section or callout for Linux/macOS users to highlight any differences or additional steps.
GitHub Create Pull Request
Networking https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/networking/fundamentals/architecture-guides.md ...rticles/networking/fundamentals/architecture-guides.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page shows evidence of Windows bias, particularly in the 'Connect to Azure resources' section, where connecting on-premises servers to Azure is described exclusively via the Azure Network Adapter deployed through Windows Admin Center—a Windows-only tool. There are no equivalent Linux examples or references to Linux tools for similar connectivity scenarios. Additionally, Windows-specific solutions are mentioned without Linux parity or alternatives, and Windows tools are introduced before any cross-platform or Linux options.
Recommendations
  • For every Windows-specific tool or example (such as Azure Network Adapter via Windows Admin Center), provide equivalent Linux guidance (e.g., using VPN clients, strongSwan, or native Azure CLI commands on Linux).
  • Ensure that connectivity scenarios include both Windows and Linux server examples, with clear instructions for each platform.
  • When listing tools or solutions, present cross-platform or Linux options alongside Windows options, or mention them first to avoid 'windows_first' ordering.
  • Audit referenced articles to ensure Linux parity in scripts, examples, and tooling, and update the main documentation page to highlight cross-platform support.
  • Explicitly state platform compatibility for each solution, and provide links to Linux-specific documentation where available.
GitHub Create Pull Request
Networking https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/networking/connectivity-interoperability-data-plane.md ...networking/connectivity-interoperability-data-plane.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation consistently presents only Windows-based command-line examples (using 'tracert' and 'ping' with Windows prompt syntax), and all sample outputs are from Windows environments. There are no Linux or cross-platform equivalents provided, nor is there mention of Linux tools (such as 'traceroute' or 'ping' on Linux). The use of Windows-specific paths (e.g., 'C:\Users\rb>') and references to Windows command prompts further reinforce a Windows-centric perspective.
Recommendations
  • For every Windows command-line example (e.g., 'tracert', 'ping'), provide the equivalent Linux command (e.g., 'traceroute', 'ping') and sample output.
  • Use neutral prompt symbols (such as '$' or '#') or provide both Windows and Linux prompt examples to avoid implying Windows as the default environment.
  • Mention and briefly describe both Windows and Linux tools for network diagnostics in Azure environments.
  • Where screenshots or output are shown, include Linux output as well, or clarify that the steps are applicable to both platforms.
  • Consider a short section or note at the beginning clarifying that all steps can be performed on both Windows and Linux, with examples for each.
GitHub Create Pull Request
Networking https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/networking/troubleshoot-failed-state.md .../main/articles/networking/troubleshoot-failed-state.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exclusively uses Azure PowerShell cmdlets for all troubleshooting examples, with instructions to install and use PowerShell, and no mention of Azure CLI, Bash, or cross-platform alternatives. This approach assumes the user is on Windows or is comfortable with PowerShell, which is less common on Linux systems. There are no Linux-specific or cross-platform instructions or examples provided.
Recommendations
  • Add equivalent Azure CLI (az) command examples for each resource type, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Include a section on how to install and use Azure CLI, similar to the PowerShell installation instructions.
  • Where possible, provide Bash script examples alongside PowerShell, or at least clarify that PowerShell Core is available cross-platform.
  • Rephrase instructions to be tool-agnostic where possible (e.g., 'Use Azure PowerShell or Azure CLI to...').
  • List both PowerShell and CLI examples side-by-side, or allow users to select their preferred shell in the documentation UI.
  • Explicitly state that the instructions apply to both Windows and Linux, and highlight any differences in behavior or prerequisites.
GitHub Create Pull Request
Networking Azure for Network Engineers ...ain/articles/networking/azure-for-network-engineers.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation references PowerShell and the Get-AzEffectiveRouteTable cmdlet as the primary example for viewing effective routes, with no explicit Linux or cross-platform CLI example provided. Throughout, PowerShell is mentioned before CLI, and there are no Linux/macOS-specific instructions or parity in tooling references.
Recommendations
  • Provide equivalent Azure CLI (az) commands alongside PowerShell examples for all tasks, especially for viewing effective routes and managing network resources.
  • When referencing tools, mention cross-platform options (Azure CLI) before or alongside Windows-specific tools (PowerShell).
  • Include explicit notes or examples for Linux/macOS users, clarifying that Azure CLI is fully supported and showing sample commands.
  • Link to both PowerShell and Azure CLI documentation for all referenced cmdlets or commands.
GitHub Create Pull Request
Networking Check Azure resource usage against limits | Microsoft Docs ...main/articles/networking/check-usage-against-limits.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation presents PowerShell as the primary scripting example before Azure CLI, with detailed setup instructions for PowerShell (including module installation and login) and no equivalent Bash/Linux shell guidance. There is no mention of Linux/macOS-specific considerations or examples, and the PowerShell section is more detailed than the Azure CLI section.
Recommendations
  • Provide equal detail for Azure CLI usage, including setup and login instructions for Linux/macOS users.
  • Explicitly mention that Azure CLI commands work cross-platform and can be run in Bash or other Unix shells.
  • Add Bash-specific examples or notes for Linux/macOS users, especially for common tasks like authentication and environment setup.
  • Consider listing Azure CLI before PowerShell, as it is the more cross-platform tool.
  • Include troubleshooting tips or links for Linux/macOS users where relevant.
GitHub Create Pull Request
Networking Troubleshoot Azure Microsoft.Network failed Provisioning State .../main/articles/networking/troubleshoot-failed-state.md
Medium Priority View Details →
Scanned: 2026-01-14 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 no mention of Azure CLI, Bash, or cross-platform alternatives. Instructions assume use of PowerShell, which is native to Windows and less commonly used on Linux/macOS. There are no Linux/macOS-specific examples or guidance, and Windows tools (PowerShell) are referenced first and exclusively.
Recommendations
  • Add equivalent Azure CLI (az) examples for each resource type, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include a section explaining how to perform the troubleshooting steps using Bash or shell scripting, where appropriate.
  • Clarify that Azure PowerShell can be installed and used on Linux/macOS, and provide installation instructions for those platforms.
  • Present examples for both PowerShell and Azure CLI side-by-side, or alternate which comes first.
  • Explicitly state platform compatibility for all tools mentioned.
GitHub Create Pull Request
Networking Azure for Network Engineers ...ain/articles/networking/azure-for-network-engineers.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias, particularly in the 'Verification' section, where PowerShell is mentioned explicitly and linked as the primary example for checking effective routes (Get-AzEffectiveRouteTable), while Azure CLI is only mentioned generically without specific commands or links. Throughout the page, PowerShell is consistently listed before CLI, and no Linux/macOS-specific instructions or examples are provided. This may create friction for Linux/macOS users who rely on Azure CLI or other cross-platform tools.
Recommendations
  • Provide explicit Azure CLI examples and links alongside PowerShell commands, especially for tasks like viewing effective routes (e.g., include 'az network nic show-effective-route-table').
  • Alternate the order of mentioning PowerShell and CLI, or mention CLI first to avoid implicit Windows-first bias.
  • Clarify that both PowerShell and CLI are cross-platform, and provide guidance for Linux/macOS users where appropriate.
  • Where possible, include screenshots or walkthroughs for both Azure Portal and CLI, not just PowerShell.
  • Add a section or callout for Linux/macOS users to ensure parity in instructions.
GitHub Create Pull Request
Networking Check Azure resource usage against limits | Microsoft Docs ...main/articles/networking/check-usage-against-limits.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation presents PowerShell instructions and context before Azure CLI, assumes PowerShell as a primary scripting tool, and provides setup instructions for PowerShell on Windows but not for Linux/macOS. There are no explicit Linux/macOS-specific instructions or examples, and the CLI section is presented after PowerShell, indicating a Windows-first bias.
Recommendations
  • Present Azure CLI and PowerShell instructions in parallel or in a neutral order, or lead with Azure CLI, which is cross-platform.
  • Explicitly mention that Azure CLI and Cloud Shell work on Linux/macOS, and provide setup instructions for those platforms.
  • Add notes or links for installing and using PowerShell Core on Linux/macOS if PowerShell examples are retained.
  • Where possible, provide bash shell examples alongside PowerShell, especially for filtering and formatting output.
  • Clarify that both PowerShell and Azure CLI are available in Cloud Shell, which is cross-platform.
GitHub Create Pull Request
← Previous Page 1 of 2 Next →