170
Total Pages
125
Linux-Friendly Pages
45
Pages with Bias
26.5%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

120 issues found
Showing 1-25 of 120 flagged pages
Firewall Deploy and configure Enterprise CA certificates for Azure Firewall Premium .../firewall/premium-deploy-certificates-enterprise-ca.md
High Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First Powershell Heavy
Summary
The documentation is heavily biased towards Windows environments, with instructions and tooling (certtmpl.msc, Internet Explorer, Active Directory Certification Services) that are exclusive to Windows. No Linux or cross-platform alternatives are provided for certificate creation, management, or export, and all examples and screenshots are Windows-centric. This creates significant friction for Linux/macOS users, who cannot follow the documented steps without access to a Windows Server and related tools.
Recommendations
  • Provide equivalent instructions for Linux/macOS environments, such as using OpenSSL for certificate creation and export.
  • Mention cross-platform certificate authorities (e.g., EJBCA, Dogtag, or OpenSSL-based CA) as alternatives to Active Directory Certification Services.
  • Include examples of certificate requests and exports using command-line tools available on Linux/macOS.
  • Clarify which steps are Windows-specific and offer guidance for non-Windows users.
  • Add screenshots and walkthroughs for Linux/macOS workflows where possible.
Firewall Deploy and configure Enterprise CA certificates for Azure Firewall Premium .../firewall/premium-deploy-certificates-enterprise-ca.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First 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 the prerequisites assume Active Directory and AD CS, which are Windows-only. No Linux/macOS alternatives or examples are provided for certificate creation, request, or export, making it difficult for non-Windows users to follow the guide.
Recommendations
  • Provide equivalent steps for Linux/macOS environments, such as using OpenSSL for certificate creation and export.
  • Include instructions for requesting certificates from AD CS using certreq.exe (which can run on Windows clients) and/or via REST APIs, and clarify if/how Linux clients can interact with AD CS.
  • Offer guidance for environments without Active Directory, such as using a non-Microsoft PKI or third-party CA.
  • Add examples for exporting certificates using cross-platform tools (e.g., OpenSSL, certutil on Linux).
  • Reorder examples so that Windows and Linux/macOS instructions are presented with equal prominence.
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exhibits a strong Windows bias, primarily through extensive use of PowerShell scripts and cmdlets for all command-line examples and migration steps. There are no CLI (az), Bash, or Linux/macOS shell examples provided, and PowerShell is referenced as the default automation tool. Windows-specific tooling (Azure PowerShell module) is required for critical migration steps, and troubleshooting guidance is exclusively PowerShell-based. While Terraform is mentioned, no examples are shown, and the main workflow is PowerShell-centric.
Recommendations
  • Add equivalent Azure CLI (az) examples for all PowerShell commands and scripts, ensuring Linux/macOS users can follow along without installing PowerShell.
  • Provide Bash shell script examples for migration and policy validation steps.
  • Explicitly mention cross-platform alternatives and clarify which steps can be completed using Azure CLI, REST API, or Terraform.
  • Reorder sections to present cross-platform methods (CLI, portal, Terraform) before PowerShell, or at least in parallel.
  • Include troubleshooting steps using Azure CLI and portal, not just PowerShell.
Firewall Deploy and configure Enterprise CA certificates for Azure Firewall Premium .../firewall/premium-deploy-certificates-enterprise-ca.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First Powershell Heavy
Summary
The documentation is heavily biased towards Windows environments, specifically Active Directory and Windows Server tools. All certificate management steps use Windows-only tools (certtmpl.msc, Internet Explorer, Windows certificate export wizard), and there are no Linux/macOS equivalents or alternatives provided. The prerequisites assume an Active Directory Forest and AD CS, which are not available on Linux. No cross-platform certificate generation or export instructions are given.
Recommendations
  • Provide instructions for generating and exporting certificates using cross-platform tools such as OpenSSL.
  • Include Linux/macOS alternatives for certificate requests and exports, e.g., using command-line tools or web browsers other than Internet Explorer.
  • Clarify whether Azure Firewall Premium supports certificates from non-AD CS PKI solutions and document the process for those.
  • Reorder examples so that cross-platform or generic methods appear before or alongside Windows-specific instructions.
  • Explicitly state Windows-only requirements and suggest alternatives for organizations using Linux-based PKI.
Firewall Deploy and configure Enterprise CA certificates for Azure Firewall Premium .../firewall/premium-deploy-certificates-enterprise-ca.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First Powershell Heavy
Summary
The documentation is heavily oriented toward Windows environments, specifically Active Directory and Windows Server tools. All certificate management steps rely on Windows-only utilities (certtmpl.msc, Internet Explorer, Windows Certificate Export Wizard), and there are no Linux or cross-platform alternatives provided. The prerequisites assume an Active Directory Forest and AD CS, which are Windows-centric. No guidance is given for Linux/macOS users or for using open-source PKI solutions.
Recommendations
  • Add instructions for generating and managing certificates using open-source PKI tools (e.g., OpenSSL, EJBCA) on Linux/macOS.
  • Provide examples for certificate requests and exports using command-line tools available on Linux (e.g., openssl, certtool).
  • Clarify whether Azure Firewall Premium supports certificates from non-AD CS sources and document the process for those.
  • Include screenshots and walkthroughs for Linux/macOS environments where applicable.
  • Reorder examples so that platform-neutral or Linux/macOS methods appear before or alongside Windows-specific instructions.
Scanned: 2026-01-22 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy
Summary
The documentation is generally cross-platform and focuses on Azure portal, Log Analytics, and Kusto queries, which are accessible from any OS. However, there is a notable Windows bias in the section about enabling Azure Firewall Fat Flow Log (Top flow log), which explicitly states that configuration must be done through Azure PowerShell. There are no Linux/macOS CLI or Azure CLI alternatives provided for this task, and PowerShell is a Windows-centric tool (though it can run on Linux, but is less commonly used there). Additionally, the tip about log converter tools references Visual Studio and C#, which are traditionally Windows development environments, though not strictly Windows-only.
Recommendations
  • Provide Azure CLI or REST API instructions for enabling Fat Flow Log, if available, to ensure Linux/macOS users can perform this configuration without relying on PowerShell.
  • If PowerShell is the only supported method, clarify that PowerShell Core is cross-platform and provide installation guidance for Linux/macOS users.
  • Offer alternative log conversion tools or scripts (e.g., Python, Bash) for users who do not use Visual Studio or C#.
  • Explicitly mention that all log viewing and analysis tasks (JSON, CSV, Kusto queries, Azure portal workbooks) are fully supported on Linux/macOS.
Firewall Deploy Azure Firewall with Availability Zones ...ticles/firewall/deploy-availability-zone-powershell.md
Medium Priority View Details →
Scanned: 2026-01-16 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides only Azure PowerShell examples for deploying Azure Firewall with Availability Zones. There are no examples using cross-platform tools such as Azure CLI, ARM/Bicep templates, or Terraform. The only scripted deployment method shown is PowerShell, which is most familiar and accessible to Windows users, creating friction for Linux/macOS users.
Recommendations
  • Add equivalent Azure CLI examples for deploying Azure Firewall with Availability Zones, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include ARM or Bicep template snippets for infrastructure-as-code deployments, which are platform-agnostic.
  • Mention and link to Terraform or other third-party cross-platform deployment options if available.
  • Explicitly state that Azure PowerShell can be used on all platforms (via PowerShell Core), but still provide CLI examples for parity.
Firewall Quickstart: Create an Azure Firewall with Availability Zones - Resource Manager template ...re-docs/blob/main/articles/firewall/deploy-template.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates bias towards Windows by exclusively deploying Windows Server virtual machines in the example environment, mentioning Windows VMs as the only option, and providing only PowerShell commands for resource cleanup without Linux/macOS alternatives. There are no examples or instructions for deploying Linux VMs or using cross-platform tools like Azure CLI or Bash for resource management.
Recommendations
  • Include options to deploy Linux-based virtual machines alongside or instead of Windows Server VMs in the template and documentation.
  • Provide equivalent cleanup instructions using Azure CLI or Bash scripts for Linux/macOS users.
  • Mention cross-platform tools and patterns (e.g., Azure CLI, Bash) before or alongside Windows/PowerShell examples.
  • Clarify that the template can be customized to deploy different OS types and provide guidance for doing so.
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides a PowerShell example for configuring prescaling, but does not include equivalent examples for Linux/macOS users (e.g., Azure CLI, Bash, or REST API). PowerShell is a Windows-centric tool, and its example is presented before Bicep/ARM template references. There is no mention of Azure CLI or cross-platform scripting options, which may create friction for non-Windows users.
Recommendations
  • Add Azure CLI example for configuring prescaling, as CLI is cross-platform and widely used on Linux/macOS.
  • Include REST API example or reference for users who prefer direct API calls.
  • Present examples in a neutral order (e.g., Portal, CLI, PowerShell, Bicep) or group them by platform.
  • Explicitly state that PowerShell examples can be run on Linux/macOS via PowerShell Core, or clarify platform requirements.
Firewall Quickstart: Create an Azure Firewall and IP Groups - Resource Manager template ...ain/articles/firewall/quick-create-ipgroup-template.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides only a Windows PowerShell example for resource cleanup (Remove-AzResourceGroup) and does not mention or provide equivalent Azure CLI or Bash commands for Linux/macOS users. The use of PowerShell as the sole example and lack of Linux-native tooling or examples creates friction for non-Windows users.
Recommendations
  • Add Azure CLI and/or Bash examples for resource group deletion (e.g., az group delete --name <your resource group name> --yes --no-wait).
  • Where PowerShell is used, explicitly mention cross-platform alternatives and link to relevant documentation.
  • Ensure that all critical operations (deployment, cleanup, management) have both PowerShell and CLI/Bash examples.
  • Consider listing CLI/Bash examples before or alongside PowerShell to avoid implicit Windows-first bias.
Firewall Azure Firewall preview features ...e-docs/blob/main/articles/firewall/firewall-preview.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation mentions Azure PowerShell as a configuration tool for certain features (e.g., redeploying a firewall in a secured hub), but does not mention or provide examples for Linux/macOS equivalents such as Azure CLI or Bash scripting. There are no explicit Linux/macOS instructions or parity in tooling references, and PowerShell is referenced without alternatives.
Recommendations
  • Include Azure CLI examples alongside Azure PowerShell for all configuration steps.
  • Explicitly mention that Azure CLI and Bash can be used from Linux/macOS for all tasks described.
  • Add links or code snippets for Linux/macOS users where PowerShell is referenced.
  • Ensure that tooling references (e.g., 'Azure PowerShell') are not presented as the only option, and clarify cross-platform support.
Firewall Deploy & configure Azure Firewall Basic and policy using the Azure portal ...ticles/firewall/deploy-firewall-basic-portal-policy.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively uses Windows Server as the example operating system for the workload VM and only describes remote desktop (RDP) access and Internet Explorer for testing, with no mention of Linux or macOS alternatives. There are no instructions or examples for deploying a Linux VM, connecting via SSH, or using Linux-native tools to test firewall rules. This creates friction for users who prefer or require Linux workloads.
Recommendations
  • Add parallel instructions for deploying a Linux VM (e.g., Ubuntu) in the workload subnet, including relevant settings.
  • Include examples for connecting to the Linux VM using SSH (with port 22 DNAT rule), alongside the Windows RDP example.
  • Provide testing steps using Linux tools (e.g., curl, wget, dig) to verify firewall rules.
  • Mention browser alternatives (e.g., Firefox, Chrome) for Linux/macOS users instead of only Internet Explorer.
  • Explicitly state that the procedure works for both Windows and Linux VMs, and highlight any OS-specific considerations.
Firewall Tutorial: Deploy and configure Azure Firewall and policy in a hybrid network using the Azure portal ...ain/articles/firewall/tutorial-hybrid-portal-policy.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The tutorial demonstrates a notable Windows bias: all virtual machine examples use Windows Server, IIS installation is shown only via PowerShell, and RDP is the sole remote access method described. There are no Linux VM examples, nor are SSH or Linux-native tools mentioned. The only scripting example is PowerShell, with no Bash or CLI alternatives. This creates friction for Linux/macOS users who may wish to follow the tutorial using Linux VMs or non-Windows management tools.
Recommendations
  • Include parallel instructions for deploying Linux-based VMs (e.g., Ubuntu) in both the spoke and on-premises networks.
  • Provide examples for installing and testing with Apache/Nginx on Linux VMs, alongside IIS on Windows.
  • Offer SSH-based connectivity instructions for Linux VMs, in addition to RDP for Windows.
  • Show how to install web servers and test connectivity using Bash/CLI commands, not just PowerShell.
  • Reference Azure CLI and Bash scripting alternatives for all automation steps, not just PowerShell.
  • Present Linux and Windows examples side-by-side, or at least alternate which is shown first.
Firewall Customer provided public IP address support in secured hubs ...in/articles/firewall/secured-hub-customer-public-ip.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
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 strong Windows bias by exclusively providing Azure PowerShell examples for command-line configuration, with no mention of Linux/macOS alternatives such as Azure CLI or Bash scripts. The PowerShell examples are detailed and presented before any mention of other platforms, and there is no guidance for users who may be working on Linux or macOS systems.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that the configuration steps can be performed on Linux/macOS using Azure CLI or REST API.
  • Provide Bash script samples or links to relevant Azure CLI documentation.
  • Reorder examples so that cross-platform tools (Azure CLI) are presented before or alongside PowerShell examples.
  • Include a note clarifying platform compatibility for each tool.
Medium Priority View Details →
Scanned: 2026-01-12 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 is heavily biased toward Windows and PowerShell. All command-line examples for manual migration and troubleshooting use Azure PowerShell scripts, with no mention of Bash, Azure CLI, or Linux/macOS-specific workflows. PowerShell is referenced as a prerequisite, and module installation instructions are Windows-centric. There are no Linux/macOS shell equivalents, and PowerShell is presented as the primary automation tool. The Azure portal is platform-neutral, but all scripting and automation guidance is Windows/PowerShell-focused.
Recommendations
  • Add equivalent Azure CLI (az) examples for all PowerShell scripts and migration steps.
  • Explicitly mention that Azure PowerShell can be installed and run cross-platform (Windows, Linux, macOS), and provide installation instructions for each OS.
  • Include Bash shell examples for Linux/macOS users where applicable.
  • Reference cross-platform tools (e.g., Azure CLI, Terraform) before or alongside PowerShell.
  • Clarify that all operations can be performed from Linux/macOS environments, not just Windows.
  • Provide troubleshooting steps using Azure CLI for Linux/macOS users.
Firewall Quickstart: Create an Azure Firewall with Availability Zones - Bicep ...azure-docs/blob/main/articles/firewall/deploy-bicep.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exhibits a Windows bias by exclusively deploying Windows Server virtual machines in the example environment and only referencing Windows VMs (jump box and server). There are no Linux VM examples or mentions, and the adminUsername/adminPassword parameters are described only in the context of Windows VM login. While the deployment and management instructions use cross-platform Azure CLI and PowerShell, the resource environment is Windows-centric.
Recommendations
  • Include Linux VM deployment examples alongside Windows Server VMs in the Bicep file and documentation.
  • Clarify that adminUsername/adminPassword can be used for both Windows and Linux VMs, or provide Linux-specific credential guidance.
  • Mention Linux VM options in the description and summary of the test environment.
  • Add notes or examples for connecting to Linux VMs (e.g., SSH) in addition to Windows (RDP).
Firewall Configure customer-controlled maintenance for Azure Firewall ...n/articles/firewall/customer-controlled-maintenance.md
Medium Priority View Details →
Scanned: 2026-01-12 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 moderate Windows bias. The Azure portal is presented as the primary method for configuration, which is most commonly accessed from Windows environments. PowerShell instructions are provided in detail and appear before Azure CLI examples, with PowerShell being a Windows-centric tool. There is no mention of Linux-specific tools or shell environments (e.g., Bash), nor are there any explicit Linux/macOS screenshots or workflow notes. While Azure CLI is included and is cross-platform, the ordering and emphasis favor Windows users.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and more accessible to Linux/macOS users.
  • Include explicit notes or screenshots showing the Azure portal on Linux/macOS browsers to reinforce cross-platform support.
  • Add Bash shell equivalents for any preparatory steps (e.g., environment variable setting) where relevant.
  • Clarify that Azure PowerShell can be used on Linux/macOS, or link to installation instructions for non-Windows platforms.
  • Mention that the Azure portal is accessible from any modern browser, regardless of OS.
Firewall Deploy Azure Firewall with Availability Zones ...ticles/firewall/deploy-availability-zone-powershell.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides a detailed Azure PowerShell example for deploying Azure Firewall with Availability Zones, but does not offer equivalent examples for Linux/macOS users (e.g., Azure CLI, ARM/Bicep templates, or REST API). The only code sample is PowerShell-specific, which is primarily a Windows tool, and there is no mention of Linux-friendly alternatives or parity in deployment instructions.
Recommendations
  • Add equivalent Azure CLI examples for configuring Availability Zones, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include ARM template or Bicep deployment snippets to demonstrate infrastructure-as-code approaches that work across all platforms.
  • Reference REST API methods for advanced users who may prefer scripting deployments in languages/environments other than PowerShell.
  • Explicitly state platform compatibility for each method and recommend cross-platform tools for non-Windows users.
Firewall Deploy and configure Azure Firewall using Azure CLI ...s/azure-docs/blob/main/articles/firewall/deploy-cli.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy
Summary
The documentation demonstrates a notable Windows bias. All VM creation examples use Windows images (win2016datacenter), and testing instructions exclusively reference Windows tools (Remote Desktop, PowerShell, Invoke-WebRequest, nslookup) without mentioning Linux/macOS alternatives. There are no examples for connecting to or testing from Linux VMs, nor are SSH or Linux command-line equivalents provided.
Recommendations
  • Include parallel examples for deploying Linux VMs (e.g., using Ubuntu images) alongside Windows VM creation.
  • Provide instructions for connecting to Linux VMs (e.g., using SSH) and for Linux/macOS users to test firewall rules.
  • Add Linux/macOS command equivalents for PowerShell commands, such as using curl, wget, and dig/nslookup in bash.
  • Mention cross-platform remote access options (SSH, RDP clients for Linux/macOS) and clarify that the procedure is not Windows-specific.
  • Order examples so that Windows and Linux instructions are presented together or Linux is not always secondary.
Firewall Quickstart: Create an Azure Firewall with Availability Zones - Resource Manager template ...re-docs/blob/main/articles/firewall/deploy-template.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias by exclusively deploying Windows Server virtual machines in the example environment, referencing Windows-specific admin credentials, and providing only PowerShell commands for resource cleanup. There are no Linux VM examples, nor are Linux command-line tools (such as Azure CLI or Bash) mentioned for management tasks.
Recommendations
  • Include examples that deploy Linux virtual machines alongside or instead of Windows Server VMs.
  • Provide Linux-specific instructions for admin username/password conventions.
  • Add equivalent Azure CLI or Bash commands for resource cleanup (e.g., 'az group delete --name MyResourceGroup').
  • Ensure that any referenced scripts or management tasks have cross-platform alternatives.
Firewall Quickstart: Create an Azure Firewall with Availability Zones - Terraform ...e-docs/blob/main/articles/firewall/deploy-terraform.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively deploys Windows Server virtual machines as part of the sample environment and does not mention or provide examples for Linux VM deployment. All VM-related instructions and resources are Windows-specific, with no Linux alternatives or parity. This creates a bias toward Windows environments and may exclude users who prefer or require Linux-based infrastructure.
Recommendations
  • Add instructions and Terraform resource examples for deploying Linux virtual machines (e.g., using azurerm_linux_virtual_machine).
  • Mention that the sample environment can be adapted for Linux VMs and provide guidance or links to relevant documentation.
  • Ensure that password generation and other VM setup steps include Linux-compatible options.
  • Present both Windows and Linux VM deployment options side-by-side or in separate sections for clarity.
Firewall Azure Firewall Draft + Deployment (preview) ...azure-docs/blob/main/articles/firewall/draft-deploy.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides detailed examples for Azure Portal, Azure CLI, and Azure PowerShell. While the CLI section is cross-platform, the PowerShell section is Windows-centric and presented as a primary method alongside CLI and Portal. There are no explicit Linux/macOS shell examples (e.g., Bash), and PowerShell is highlighted as a main automation tool, which may create friction for Linux/macOS users unfamiliar with PowerShell. The CLI examples use az, which is cross-platform, but no Linux-specific notes or alternative shell scripting patterns are provided.
Recommendations
  • Add explicit Bash/shell scripting examples for Linux/macOS users, especially for bulk operations or automation.
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows, and provide sample shell scripts.
  • De-emphasize PowerShell as a primary automation method; present it after CLI and note its Windows-centric nature.
  • Include notes or links for installing and using Azure CLI on Linux/macOS.
  • If PowerShell is required for some advanced scenarios, mention PowerShell Core and its cross-platform availability.
Firewall Azure Firewall known issues and limitations ...s/blob/main/articles/firewall/firewall-known-issues.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page references Azure PowerShell cmdlets as the only example for updating firewall policy tags and discusses missing PowerShell and CLI support for ICMP, but does not provide equivalent Linux/macOS command-line examples (such as Azure CLI or Bash). The only explicit tooling example is PowerShell, which is Windows-centric, and there is no mention of Linux/macOS alternatives or parity in command-line instructions.
Recommendations
  • Provide Azure CLI (az) command examples alongside PowerShell for all operations, especially for updating firewall policy tags.
  • Explicitly mention Linux/macOS compatibility for CLI commands and clarify when features are available in Azure CLI vs PowerShell.
  • Where PowerShell is referenced, add Bash or shell script equivalents for Linux/macOS users.
  • Add a section or note on cross-platform tooling support for Azure Firewall management.
Firewall Access a storage account using SFTP over an Azure Firewall static public IP address ...zure-docs/blob/main/articles/firewall/firewall-sftp.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation relies exclusively on Azure PowerShell for all deployment and configuration steps, with no mention of Azure CLI, Bash, or Linux-native tooling. All code samples are PowerShell, and prerequisites reference PowerShell installation and usage. The only SFTP client example is generic, but the workflow assumes a Windows/PowerShell environment throughout.
Recommendations
  • Provide equivalent Azure CLI (az) commands for all deployment and configuration steps.
  • Include Bash shell examples for variable setup and scripting.
  • Add instructions for installing and using Azure CLI on Linux/macOS.
  • Explicitly mention cross-platform compatibility for SFTP clients and provide a Linux/macOS command-line example.
  • Clarify that all steps can be performed from Linux/macOS, not just Windows.
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides deployment and update instructions for enabling Active FTP support on Azure Firewall, but all code examples and walkthroughs are given for Azure PowerShell, Azure CLI, and ARM templates. The PowerShell instructions are shown first and in more detail, with no explicit Linux/macOS shell examples (e.g., Bash), nor any mention of platform-specific considerations for non-Windows users. The CLI section is brief and does not clarify usage on Linux/macOS. There is no guidance for Linux-specific tooling or workflows.
Recommendations
  • Add explicit Bash examples for Azure CLI commands, including full command lines and expected output.
  • Clarify that Azure CLI works cross-platform and provide usage notes for Linux/macOS users.
  • Reorder sections so that CLI and ARM template examples appear before PowerShell, or present all methods in parallel.
  • Include notes on installing and using Azure CLI on Linux/macOS.
  • Mention any platform-specific caveats for Linux/macOS users (e.g., differences in command syntax, authentication, or environment setup).
← Previous Page 1 of 5 Next →