Firewall

90
Total Pages
40
Linux-Friendly Pages
50
Pages with Bias
55.6%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

332 issues found
Showing 76-100 of 332 flagged pages
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/customer-controlled-maintenance.md ...n/articles/firewall/customer-controlled-maintenance.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 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by consistently presenting PowerShell examples before Azure CLI, referencing PowerShell as a primary automation tool, and using terminology and patterns familiar to Windows users (e.g., PowerShell cmdlets, references to Windows time zones). The Azure portal instructions also implicitly assume a Windows-centric user base, as the portal experience is most commonly accessed from Windows environments. There is minimal mention of Linux-specific considerations, and no Bash or Linux shell examples are provided.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples to provide parity for Linux/macOS users.
  • Include Bash shell script examples for common tasks, especially for automation scenarios.
  • Reference cross-platform tools and workflows, such as using Azure CLI in Bash or zsh, and clarify that the Azure portal is accessible from any OS.
  • Avoid Windows-centric terminology (e.g., 'Pacific Standard Time') and provide guidance on time zone selection for Linux users.
  • Explicitly mention that all command-line examples work on Linux/macOS as well as Windows, and note any OS-specific caveats.
  • Add a section or note on using these procedures from Linux/macOS environments, including prerequisites and troubleshooting tips.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/deploy-cli.md ...s/azure-docs/blob/main/articles/firewall/deploy-cli.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively using Windows Server images for virtual machines, referencing Remote Desktop for access, and providing only PowerShell-based testing instructions. There are no Linux VM deployment examples, nor are SSH or Linux command-line tools mentioned for testing connectivity or DNS resolution.
Recommendations
  • Include parallel examples for deploying Linux-based VMs (e.g., Ubuntu) alongside Windows VMs.
  • Provide instructions for connecting to Linux VMs using SSH, in addition to Remote Desktop for Windows.
  • Add Linux command-line equivalents for testing, such as using 'dig' or 'nslookup' and 'curl' or 'wget' for connectivity tests.
  • Mention Linux tools and patterns (e.g., SSH, bash) wherever Windows tools (Remote Desktop, PowerShell) are referenced.
  • Ensure that both Windows and Linux scenarios are covered in all steps, including VM creation, access, and firewall rule testing.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/dns-settings.md ...azure-docs/blob/main/articles/firewall/dns-settings.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 provides configuration examples for Azure Firewall DNS settings using the Azure Portal, Azure CLI, and Azure PowerShell. PowerShell examples are given equal prominence to CLI, but there are no Linux-specific shell examples (e.g., Bash scripts) or references to Linux-native tools. The CLI examples use Azure CLI, which is cross-platform, but the lack of explicit Linux/Bash examples and the inclusion of PowerShell (a Windows-centric tool) indicate a Windows bias. Additionally, the documentation does not mention Linux-specific patterns or troubleshooting steps, and PowerShell examples are provided for every scenario, reinforcing the bias.
Recommendations
  • Add explicit Bash examples for all CLI commands, demonstrating usage in a Linux shell environment.
  • Clarify that Azure CLI commands are cross-platform and provide sample shell environments (e.g., Bash, zsh) for Linux users.
  • Include troubleshooting or configuration notes relevant to Linux environments, such as DNS cache flushing or network interface updates.
  • Where PowerShell is mentioned, also mention Linux alternatives (e.g., Bash, Python scripts) for scripting and automation.
  • Review the ordering of examples to avoid giving PowerShell precedence over CLI or Linux-native tools.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/features-by-sku.md ...re-docs/blob/main/articles/firewall/features-by-sku.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation demonstrates Windows bias in several areas: Windows-related tools and patterns (PowerShell, Windows Update) are mentioned explicitly and often first, while Linux equivalents are not referenced. The DevOps integration section lists 'REST/PowerShell/CLI/templates/Terraform', placing PowerShell (a Windows-centric tool) before CLI, and the FQDN tags example uses 'Windows Update' without mentioning any Linux update services. No Linux-specific examples or tools (such as Bash, apt, yum, or Linux update tags) are provided.
Recommendations
  • Include Linux-specific examples and references, such as update services (e.g., Ubuntu, Red Hat, CentOS) alongside Windows Update in FQDN tag examples.
  • List cross-platform tools (e.g., Azure CLI, Terraform, REST) before platform-specific ones like PowerShell in DevOps integration sections.
  • Provide example commands for both PowerShell and Bash/CLI where relevant.
  • Explicitly mention Linux compatibility and use cases in feature descriptions and deployment scenarios.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/firewall-known-issues.md ...s/blob/main/articles/firewall/firewall-known-issues.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 Tools Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily through the exclusive mention of Azure PowerShell cmdlets (e.g., Set-AzFirewallPolicy) as mitigation steps, and references to Windows-centric tools like IIS for FTP configuration. There are no Linux-specific examples, tools, or command-line instructions (such as Bash, Azure CLI for Linux, or Linux FTP server configuration). This may hinder Linux users from finding parity in troubleshooting or configuration guidance.
Recommendations
  • Provide equivalent Azure CLI (cross-platform) examples alongside PowerShell cmdlets for all operations, especially for tasks like updating firewall policy tags.
  • Include references and configuration examples for popular Linux FTP servers (e.g., vsftpd, proftpd) when discussing FTP-related limitations and mitigations.
  • Ensure that troubleshooting steps and mitigation instructions are platform-neutral or explicitly mention both Windows and Linux approaches.
  • Add notes or links to Linux documentation where relevant, such as configuring outbound SMTP or handling SNAT/FTP issues on Linux-based servers.
  • Review all tool references (e.g., IIS) and add Linux alternatives or clarify that the guidance applies to both platforms where possible.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/explicit-proxy.md ...ure-docs/blob/main/articles/firewall/explicit-proxy.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 Windows bias by referencing Azure PowerShell for deployment instructions in the 'Next steps' section, without mentioning or linking to Linux-friendly alternatives such as Azure CLI or ARM templates. There are no examples or guidance for configuring proxy settings on Linux applications or browsers, nor is there mention of Linux-specific tools or workflows. The documentation assumes familiarity with Windows-centric tools and patterns, and omits Linux parity in both configuration and deployment guidance.
Recommendations
  • Include equivalent deployment instructions using Azure CLI and/or ARM templates, which are cross-platform and widely used on Linux.
  • Provide examples or references for configuring proxy settings on popular Linux browsers (e.g., Firefox) and command-line tools (e.g., curl, wget).
  • Mention Linux-specific considerations for PAC file usage and proxy configuration, such as environment variables (http_proxy, https_proxy) and desktop environment settings.
  • Ensure that links in the 'Next steps' section cover both Windows and Linux deployment scenarios.
  • Add screenshots or step-by-step instructions for Linux users where relevant.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/fqdn-tags.md ...cs/azure-docs/blob/main/articles/firewall/fqdn-tags.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Windows Heavy
Summary
The documentation page demonstrates a Windows bias by primarily referencing Windows services (Windows Update, Windows Diagnostics, Windows Virtual Desktop, Windows 365) and providing examples and FQDN tags almost exclusively for Microsoft and Windows-centric products. There are no explicit Linux or cross-platform service examples, nor are Linux-specific endpoints or use cases mentioned. The documentation assumes the reader is managing Windows environments and does not address scenarios relevant to Linux or open-source platforms.
Recommendations
  • Include examples of FQDN tags or application rules for popular Linux-based services (e.g., Ubuntu updates, Red Hat repositories, or other open-source platforms).
  • Add documentation or references for managing outbound traffic for Linux endpoints, such as package repositories, monitoring agents, or configuration management tools.
  • Provide parity in examples by showing how Azure Firewall can be used to allow traffic for both Windows and Linux services.
  • Mention cross-platform scenarios, such as mixed Windows/Linux environments, and how FQDN tags can be leveraged in those contexts.
  • Consider adding a section or table for non-Microsoft services to demonstrate broader applicability.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/ftp-support.md .../azure-docs/blob/main/articles/firewall/ftp-support.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 providing detailed Azure PowerShell instructions and references before Azure CLI and ARM template examples. The PowerShell example is the only one with explicit code, while the CLI and ARM template sections are brief and lack example code blocks. There are no Linux-specific instructions, nor are there references to Linux-native tools or workflows for managing Azure Firewall FTP support.
Recommendations
  • Provide equally detailed Azure CLI examples, including explicit code blocks for enabling Active FTP and updating existing firewalls.
  • Add instructions or examples for using Linux-native tools (e.g., Bash scripts, curl, az CLI from Linux) to configure Azure Firewall FTP support.
  • Ensure that CLI examples are presented before or alongside PowerShell examples to avoid Windows-first ordering.
  • Include notes or tips for Linux users, such as how to install and use the Azure CLI on Linux to perform the same tasks.
  • Where possible, mention cross-platform considerations and clarify that all configuration steps can be performed from Linux, macOS, or Windows environments.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/firewall-sftp.md ...zure-docs/blob/main/articles/firewall/firewall-sftp.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 is heavily biased towards Windows and PowerShell usage. All deployment and configuration steps are provided exclusively using Azure PowerShell cmdlets, with no mention of Azure CLI, Bash, or Linux-native tooling. The initial setup instructions and variable assignments assume PowerShell syntax, and there are no Linux-specific examples or alternative workflows. Even the 'Test the SFTP connection' section, while using a generic 'sftp' command, refers to 'command prompt' (which is ambiguous but often means Windows CMD), and does not clarify usage on Linux or macOS.
Recommendations
  • Provide equivalent Azure CLI (az) commands for all deployment and configuration steps, alongside PowerShell examples.
  • Include Bash shell variable setup and scripting examples for Linux/macOS users.
  • Clarify that the 'sftp' command can be run from Linux/macOS terminals and provide explicit examples for those platforms.
  • Mention cross-platform tools and workflows, and avoid assuming the user is on Windows or using PowerShell.
  • Add notes or sections for Linux users, including package installation steps for Azure CLI and SFTP clients.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/idps-signature-categories.md ...ob/main/articles/firewall/idps-signature-categories.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. Several categories reference Microsoft technologies (ActiveX, Windows exploits, IIS) and mention Windows-specific attack vectors before or without Linux equivalents. The 'Web Server' category lists Microsoft IIS alongside Apache, Tomcat, and NGINX, but the 'ActiveX' and 'Exploit' categories focus on Microsoft technologies. There are no explicit Linux/Powershell command examples, but the overall framing and examples tend to prioritize or exclusively mention Windows-related technologies and threats. Linux-specific threats, tools, or examples are underrepresented or absent.
Recommendations
  • Include equivalent Linux technologies and threats in relevant categories (e.g., mention Linux kernel exploits, Linux web server vulnerabilities).
  • Balance examples by listing Linux and open-source technologies alongside Windows ones (e.g., in 'Exploit' and 'Web Server' categories).
  • Add references to Linux-specific attack vectors and detection signatures where appropriate.
  • Ensure that descriptions do not implicitly prioritize Windows by mentioning cross-platform threats and tools.
  • Consider adding a table or section highlighting parity in coverage between Windows and Linux environments.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/ip-groups.md ...cs/azure-docs/blob/main/articles/firewall/ip-groups.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 Tools Windows First
Summary
The documentation page demonstrates a Windows bias by listing only Azure PowerShell cmdlets for IP Group management in the 'Related Azure PowerShell cmdlets' section, without mentioning equivalent Azure CLI commands or providing Linux-oriented examples. The presence of the 'devx-track-azurepowershell' custom tag and the exclusive focus on PowerShell tools further reinforces the bias. Although the page mentions that IP Groups can be managed via Azure CLI, REST API, and portal, only PowerShell commands are explicitly documented, and no Linux shell or CLI examples are provided.
Recommendations
  • Add equivalent Azure CLI command examples for all PowerShell cmdlets listed, with links to CLI documentation.
  • Include Linux shell usage patterns and examples where relevant, especially for bulk operations or scripting.
  • Balance the 'Related Azure PowerShell cmdlets' section with a 'Related Azure CLI commands' section.
  • Remove or supplement the 'devx-track-azurepowershell' tag with a CLI or cross-platform tag if available.
  • Ensure that step-by-step instructions and code samples are provided for both Windows (PowerShell) and Linux (Bash/CLI) users.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/management-nic.md ...ure-docs/blob/main/articles/firewall/management-nic.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell command examples for firewall management operations, with no equivalent Azure CLI, Bash, or Linux-native instructions. The step-by-step guidance assumes use of PowerShell and Windows-centric tooling, and does not mention or prioritize cross-platform alternatives. This may hinder Linux users or those preferring non-Windows environments from following the procedures easily.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, showing how to perform firewall stop/start and allocation operations using az commands.
  • Include Bash script snippets or instructions for Linux/Mac users where appropriate.
  • Explicitly mention that both PowerShell and CLI methods are supported, and provide links to cross-platform tool documentation.
  • Reorder examples or provide parallel instructions so that Linux-friendly methods are not always secondary to Windows/PowerShell.
  • Clarify any platform-specific requirements or limitations, and ensure parity in guidance for both Windows and Linux environments.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/monitor-firewall-reference.md ...b/main/articles/firewall/monitor-firewall-reference.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 Tools Missing Linux Example Windows First
Summary
The documentation page for Azure Firewall monitoring data exhibits a strong Windows bias. All command-line examples for enabling/disabling logs and features use Azure PowerShell, with no mention of Azure CLI, Bash, or Linux-native workflows. There are no Linux or cross-platform examples for these operations, and PowerShell is presented as the default and only method for scripting and automation. The documentation also refers to Windows-centric tooling and patterns (e.g., PowerShell cmdlets), and does not provide parity for Linux administrators or those using non-Windows environments.
Recommendations
  • Provide equivalent Azure CLI examples for all PowerShell commands, enabling Linux and macOS users to perform the same tasks.
  • Explicitly mention that all operations can be performed from any OS using Azure CLI, Bash, or the Azure portal, not just via PowerShell.
  • Add Bash script snippets for common tasks, such as enabling/disabling logs and checking registration status.
  • Reorder sections to present cross-platform or OS-neutral methods first, or at least in parallel with Windows/PowerShell examples.
  • Clarify which features or commands are available via Azure CLI, REST API, or portal, and link to relevant documentation for those methods.
  • Include troubleshooting and verification steps that do not rely on Windows-only tools.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/premium-deploy.md ...ure-docs/blob/main/articles/firewall/premium-deploy.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing a Windows test VM (WorkerVM) for all deployment and testing steps, including certificate installation and browser-based validation. All example commands and instructions assume a Windows environment (e.g., 'open an administrator command prompt window', browser usage on Windows VM), with no mention of Linux alternatives or parity. There are no examples or guidance for deploying or testing with a Linux VM, nor instructions for certificate installation or browser testing on Linux.
Recommendations
  • Provide parallel instructions for deploying and configuring a Linux test VM, including certificate installation steps for common Linux distributions.
  • Include Linux-specific command-line examples (e.g., using Bash terminal instead of Windows command prompt) for running curl and other tests.
  • Offer guidance for browser-based validation on Linux (e.g., using Firefox or Chrome on Ubuntu), including how to import the Intermediate CA certificate.
  • Explicitly mention that both Windows and Linux VMs can be used for testing, and highlight any differences in setup or troubleshooting.
  • Ensure that references to 'WorkerVM' are generic or clarify that it can be either Windows or Linux, depending on user preference.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/prescaling.md ...s/azure-docs/blob/main/articles/firewall/prescaling.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 provides configuration examples using the Azure portal and Azure PowerShell, both of which are most familiar to Windows users. There is no CLI (az), Bash, or Linux-native example, and PowerShell is presented as the only command-line method. This prioritizes Windows-centric tools and patterns, potentially making it less accessible for Linux users or those who prefer cross-platform automation.
Recommendations
  • Add an Azure CLI (az) example for prescaling configuration, demonstrating equivalent functionality to the PowerShell example.
  • Explicitly mention that Azure CLI and REST API can also be used for configuration, with links or code samples.
  • Ensure that command-line examples are provided for both PowerShell and Bash/CLI, and alternate their order or present them side-by-side to avoid Windows-first bias.
  • Clarify which configuration methods are cross-platform (e.g., Bicep, ARM templates, CLI) and which are Windows-specific.
  • Consider including a table summarizing all supported configuration methods, indicating their platform compatibility.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/monitor-firewall.md ...e-docs/blob/main/articles/firewall/monitor-firewall.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias in several ways. It references Windows-specific tools (Excel, Power BI, Visual Studio, C#) for log analysis and conversion, and explicitly states that enabling certain features (Fat Flow Log) requires Azure PowerShell, with no mention of Bash, CLI, or Linux-native alternatives. Examples and tool recommendations are Windows-centric, and there are no Linux or cross-platform command-line examples or tool suggestions. This can make it harder for Linux users to follow or implement the guidance.
Recommendations
  • Provide equivalent instructions and examples using Azure CLI and Bash scripts for enabling features like Fat Flow Log, alongside PowerShell.
  • Include Linux-native tools (e.g., jq, csvkit, pandas) for processing and visualizing JSON/CSV logs, in addition to Excel and Power BI.
  • Offer sample code snippets in Python or shell scripts for log conversion, not just C# and Visual Studio.
  • Explicitly mention cross-platform compatibility for log analysis tools and workflows.
  • Add screenshots or walkthroughs from Linux environments where applicable.
  • Ensure that external tool recommendations (e.g., log converter tools) have clear instructions for use on Linux and macOS, not just Windows.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/premium-deploy-certificates-enterprise-ca.md .../firewall/premium-deploy-certificates-enterprise-ca.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily biased towards Windows environments. All certificate management steps rely on Windows-specific tools (certtmpl.msc, Internet Explorer, Internet Options, Windows Certificate Export Wizard), and prerequisites assume Active Directory and AD CS. There are no examples or guidance for performing equivalent tasks on Linux, nor mention of Linux-compatible certificate authorities or tools. The workflow is not cross-platform and excludes users who do not have access to Windows infrastructure.
Recommendations
  • Add Linux-based certificate authority options (e.g., OpenSSL, EJBCA, Dogtag) and instructions for generating subordinate CA certificates.
  • Provide examples for certificate request, creation, and export using Linux command-line tools (e.g., openssl, certtool).
  • Include guidance for exporting certificates to .pfx format on Linux.
  • Clarify that the process can be performed on non-Windows platforms and provide parity in steps and screenshots.
  • Mention alternatives to Active Directory and AD CS for organizations using Linux or hybrid environments.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/protect-azure-virtual-desktop.md ...ain/articles/firewall/protect-azure-virtual-desktop.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by focusing exclusively on Azure Virtual Desktop (which is primarily Windows-based), referencing Windows-specific service tags and endpoints, and providing proxy configuration examples only for Microsoft Edge (a Windows-centric browser). There are no examples or guidance for Linux session hosts, Linux tools, or cross-platform proxy/browser configuration. The terminology and examples consistently prioritize Windows environments without mention of Linux alternatives.
Recommendations
  • Include guidance for Linux-based session hosts, if supported by Azure Virtual Desktop, such as required FQDNs/endpoints and firewall rules.
  • Provide proxy configuration examples for popular Linux browsers (e.g., Firefox, Chrome) and command-line tools.
  • Mention whether Azure Virtual Desktop supports Linux hosts and, if not, clarify the scope to avoid confusion.
  • Add references to Linux equivalents for any Windows-specific service tags, endpoints, or configuration steps.
  • Ensure that application and network rule examples are platform-neutral or include both Windows and Linux variants where possible.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/quick-create-multiple-ip-template.md ...articles/firewall/quick-create-multiple-ip-template.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation demonstrates Windows bias by focusing exclusively on Windows Server virtual machines (RDP connections), referencing Azure PowerShell for further deployment steps, and providing only PowerShell-based resource cleanup instructions. There are no Linux VM examples, nor are SSH or Linux command-line tools mentioned. The documentation assumes Windows-centric workflows and tools throughout.
Recommendations
  • Include examples for deploying and connecting to Linux virtual machines (using SSH) alongside Windows examples.
  • Provide instructions for resource cleanup using Azure CLI (cross-platform) and Bash scripts, not just PowerShell.
  • Mention Linux-compatible remote connection tools (e.g., SSH) when discussing firewall NAT rules.
  • Balance references to Windows and Linux in both template resources and validation steps.
  • Add links to documentation for deploying Linux VMs and managing them in Azure.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/quick-create-multiple-ip-bicep.md ...in/articles/firewall/quick-create-multiple-ip-bicep.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation demonstrates a Windows bias by focusing on Windows Server 2019 VMs as deployment targets, referencing RDP (a Windows protocol) for connectivity validation, and providing PowerShell examples and cleanup commands. There is no mention of Linux VM deployment, SSH connectivity, or Linux-specific tools. The Azure CLI is included, but PowerShell is given equal or greater prominence, and the validation steps are Windows-centric.
Recommendations
  • Include examples for deploying Linux VMs alongside Windows VMs in the Bicep template.
  • Add validation steps using SSH to connect to Linux VMs, demonstrating NAT rules for Linux remote access.
  • Provide cleanup commands using Azure CLI, not just PowerShell.
  • Reference Linux tools and patterns (e.g., SSH, Linux VM images) in the documentation.
  • Ensure that both Windows and Linux scenarios are presented in parallel throughout the quickstart.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/service-tags.md ...azure-docs/blob/main/articles/firewall/service-tags.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 demonstrates a Windows bias by providing only Azure PowerShell examples for configuring Azure Firewall service tags, mentioning PowerShell first and exclusively, and omitting any Linux-oriented examples (such as Azure CLI or Bash). The use of PowerShell and Windows-centric tools and patterns is prevalent, with no parity for Linux users.
Recommendations
  • Add equivalent Azure CLI examples for each PowerShell command, using Bash syntax.
  • Explicitly mention that configuration can be performed on Linux/macOS using Azure CLI, and provide step-by-step instructions.
  • Reorder the configuration section to present Azure CLI and PowerShell examples side-by-side or in parallel, rather than PowerShell first.
  • Include notes or links for Linux users regarding tool installation and usage.
  • Avoid exclusive use of Windows-specific tools or terminology unless necessary, and ensure cross-platform parity in all examples.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/sql-fqdn-filtering.md ...docs/blob/main/articles/firewall/sql-fqdn-filtering.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 provides configuration instructions using Azure CLI, Azure PowerShell, and the Azure portal. While Azure CLI is cross-platform, the PowerShell section is Windows-centric, and there are no explicit Linux shell (bash) examples or references to Linux-specific tools or patterns. The PowerShell instructions are detailed and given equal prominence to CLI, but there is no mention of Linux-specific considerations or troubleshooting. The portal instructions reference Azure CLI for deployment, but do not discuss Linux VM scenarios or validation steps using Linux tools.
Recommendations
  • Add explicit bash shell examples for Azure CLI usage to demonstrate Linux parity.
  • Include notes or troubleshooting steps relevant to Linux environments (e.g., validating connectivity from a Linux VM).
  • Clarify that Azure CLI commands work on both Windows and Linux, and provide sample commands for both platforms where appropriate.
  • If PowerShell is mentioned, consider referencing PowerShell Core, which is cross-platform, or clarify the Windows-specific context.
  • Add validation steps using Linux tools (e.g., sqlcmd, netcat, or curl) to show how to test connectivity from Linux VMs.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/secured-hub-customer-public-ip.md ...in/articles/firewall/secured-hub-customer-public-ip.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 demonstrates a clear Windows bias by providing only Azure PowerShell examples for command-line configuration, referencing PowerShell cmdlets exclusively, and omitting any equivalent instructions for Linux users (e.g., Azure CLI or Bash). The use of PowerShell as the sole scripting tool and the absence of cross-platform command-line alternatives may hinder Linux administrators from following the guidance effectively.
Recommendations
  • Add Azure CLI (az) examples alongside PowerShell for all command-line configuration steps.
  • Explicitly mention that both Windows and Linux platforms are supported, and provide platform-agnostic instructions where possible.
  • Include Bash script examples for Linux users, especially for resource management tasks.
  • Reorder sections to present cross-platform or platform-neutral methods first, or in parallel tabs (e.g., Portal, PowerShell, CLI).
  • Reference documentation for both PowerShell and Azure CLI to ensure parity.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/tutorial-hybrid-portal-policy.md ...ain/articles/firewall/tutorial-hybrid-portal-policy.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively using Windows Server virtual machines for both the workload and on-premises examples, providing only PowerShell commands for VM configuration (IIS installation), and omitting any Linux-based VM or CLI/Bash examples. Windows tools and patterns (RDP, Add-WindowsFeature, PowerShell) are referenced without Linux equivalents, and Windows is always presented first or exclusively.
Recommendations
  • Include parallel instructions for deploying Linux-based virtual machines (e.g., Ubuntu) in both the spoke and on-premises networks.
  • Provide examples for installing a web server (e.g., Apache or Nginx) on Linux VMs using Bash/CLI commands.
  • Offer Azure CLI and/or Bash alternatives for VM extension management and configuration, not just PowerShell.
  • Demonstrate SSH connectivity for Linux VMs as an alternative to RDP.
  • Balance screenshots and walkthroughs to show both Windows and Linux scenarios.
  • Explicitly mention that the tutorial applies to both Windows and Linux environments, and link to Linux-specific guides where appropriate.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/tutorial-hybrid-portal.md .../blob/main/articles/firewall/tutorial-hybrid-portal.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias in several ways: all virtual machine creation examples use Windows Server images, and all configuration and testing steps assume Windows-based tools (e.g., RDP, PowerShell, IIS). The only scripting example provided for VM configuration uses Azure PowerShell and installs IIS via Windows PowerShell commands. There are no examples or instructions for deploying or configuring Linux VMs, using SSH, or installing equivalent Linux web servers (e.g., Apache or Nginx). The documentation does not mention Linux tools or patterns, and Windows-centric terminology and procedures are used throughout.
Recommendations
  • Add parallel instructions and screenshots for deploying Linux-based VMs (e.g., Ubuntu) in both the spoke and on-premises networks.
  • Provide examples for installing a web server on Linux VMs (e.g., using apt to install Apache or Nginx) and testing connectivity via SSH.
  • Include sample Azure CLI commands for Linux users, in addition to PowerShell examples.
  • Mention SSH as an alternative to RDP for remote access, and show how to configure firewall rules for SSH (port 22).
  • Ensure that all steps referencing VM creation, configuration, and testing include both Windows and Linux options, with equal prominence.
GitHub Create Pull Request
← Previous Page 4 of 14 Next →