Azure Docs
14605
Total Pages
12420
Linux-Friendly Pages
2185
Pages with Bias
15.0%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
2185 issues found
Showing 1326-1350 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/expressroute/expressroute-troubleshooting-expressroute-overview.md
...https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/expressroute/expressroute-troubleshooting-expressroute-overview.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively providing Azure PowerShell command examples for all verification and troubleshooting steps, without offering equivalent Azure CLI (cross-platform) or Bash/Linux-native alternatives. Additionally, the only traffic testing tool mentioned is PsPing, a Windows-only utility, with no mention of Linux-compatible tools. There are no Linux or cross-platform command-line examples, and the documentation assumes familiarity with Windows-centric tools and workflows.
Recommendations
- For every PowerShell example, provide an equivalent Azure CLI (az) command example, which is cross-platform and widely used on Linux and macOS.
- When referencing traffic testing tools like PsPing, also mention and provide examples for Linux alternatives such as hping3, nping (from nmap), or standard tools like ping and traceroute.
- Explicitly state that the troubleshooting steps can be performed from any OS, and clarify which tools are available on which platforms.
- Where possible, use neutral terminology (e.g., 'command line' instead of 'PowerShell') and avoid assuming a Windows environment.
- Add a section or callout for Linux/macOS users, summarizing the equivalent steps and tools.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/expressroute/reset-circuit.md
...docs/blob/main//articles/expressroute/reset-circuit.md
High Priority
View Details →
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 examples (which are most commonly used on Windows), referencing PowerShell-specific installation and usage, and omitting any CLI or Bash/Linux-native instructions. There are no Linux or cross-platform command-line examples, and the only automation path described is via PowerShell, which is traditionally a Windows tool.
Recommendations
- Add equivalent Azure CLI (az) command examples, which are cross-platform and commonly used on Linux and macOS.
- Include Bash shell instructions for Linux users, especially for connecting and managing Azure resources.
- Explicitly mention that PowerShell Core is available cross-platform, if relevant, and provide installation links for Linux/macOS.
- Reorder or parallelize the documentation sections so that both PowerShell and CLI/Linux instructions are presented together or in a non-Windows-first order.
- Reference Linux tools and environments where appropriate, and clarify any differences in the process for Linux users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/extended-zones/arc-enabled-workloads-managed-sql.md
...es/extended-zones/arc-enabled-workloads-managed-sql.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias by providing only PowerShell-based automation and CLI examples, with no equivalent Bash or Linux shell scripts. All code snippets and instructions are tailored for PowerShell users, implicitly prioritizing Windows environments. There is no mention of Linux or cross-platform scripting alternatives, which may hinder accessibility for Linux or macOS administrators.
Recommendations
- Provide equivalent Bash shell scripts for all PowerShell examples, ensuring Linux and macOS users can follow the same automation steps.
- Explicitly mention that the Azure CLI commands can be run from any platform, and show cross-platform command-line usage.
- Where PowerShell-specific syntax is used (such as environment variable assignment or error handling), offer a Linux/Bash alternative.
- Include a note or section on platform compatibility, clarifying that both Windows and Linux are supported and providing links to relevant setup guides for each.
- Review tool recommendations (e.g., Azure Data Studio, Azure CLI) to ensure installation and usage instructions are not Windows-centric.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/extended-zones/arc-enabled-workloads-container-apps.md
...extended-zones/arc-enabled-workloads-container-apps.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides only a PowerShell script for deploying Arc-enabled ContainerApps, with no equivalent Bash or Linux shell example. All scripting and automation guidance is Windows-centric, assuming the user is running PowerShell. There is no mention of how to perform these steps on Linux or macOS, nor are cross-platform scripting patterns (such as Bash) provided.
Recommendations
- Provide a Bash (Linux/macOS) equivalent script for all PowerShell examples, ensuring parity in automation guidance.
- Explicitly mention that the Azure CLI commands work cross-platform, and show how to run them in Bash or sh environments.
- Where possible, use cross-platform scripting patterns (e.g., Bash, Python, or plain Azure CLI commands) in examples, or provide both PowerShell and Bash versions side-by-side.
- Add notes or callouts clarifying any OS-specific requirements or differences.
- Ensure that clean-up and resource management examples are shown in both PowerShell and Bash formats.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/extended-zones/arc-enabled-workloads-arc-enabled-aks-cluster.md
...zones/arc-enabled-workloads-arc-enabled-aks-cluster.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing all command-line examples and automation scripts in PowerShell syntax, which is native to Windows. There are no Bash or Linux shell equivalents, and the scripting patterns (such as function definitions and parameter handling) are tailored to PowerShell users. This may disadvantage Linux or macOS users who are more familiar with Bash or sh scripting environments.
Recommendations
- Provide equivalent Bash shell scripts for all PowerShell examples, especially for the main automation function.
- Include notes or sections clarifying that the Azure CLI commands work cross-platform, and show usage in both Windows (PowerShell) and Linux/macOS (Bash).
- When presenting scripts, alternate the order or provide tabs for both PowerShell and Bash to avoid Windows-first bias.
- Ensure that cleanup and setup instructions are shown in both PowerShell and Bash syntax.
- Explicitly mention that the Azure CLI is cross-platform and provide installation or usage tips for Linux/macOS users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/extended-zones/deploy-vm-portal.md
...blob/main//articles/extended-zones/deploy-vm-portal.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively demonstrates deploying a Windows Server VM, with instructions and screenshots focused on RDP (Remote Desktop Protocol) for access, which is specific to Windows environments. There are no examples or guidance for deploying Linux VMs, nor are SSH or Linux-specific access methods mentioned. The only OS image suggested is Windows Server, and the only remote access port discussed is RDP (3389), with no mention of SSH (22) or Linux authentication patterns.
Recommendations
- Include parallel instructions and screenshots for deploying a Linux VM (e.g., Ubuntu or CentOS) alongside the Windows example.
- Add steps for configuring SSH access (port 22) and generating/uploading SSH keys for Linux VMs.
- Mention both RDP (for Windows) and SSH (for Linux) in the 'Connect to virtual machine' section, with clear guidance for each.
- In the 'Image' selection step, show how to choose both Windows and Linux images, or at least mention that Linux images are supported.
- Provide security recommendations for SSH access similar to those given for RDP.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/firewall/integrate-with-nat-gateway.md
.../main//articles/firewall/integrate-with-nat-gateway.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by presenting Azure PowerShell examples first, followed by Azure CLI. There are no explicit Linux shell or Bash examples, nor is there mention of Linux-specific tools or workflows. The PowerShell example is more detailed and appears before the CLI example, which may reinforce a Windows-centric approach.
Recommendations
- Provide Bash or shell script examples for Linux users, especially for common tasks like associating NAT Gateway with subnets.
- Alternate the order of examples, sometimes presenting Azure CLI (which is cross-platform) before PowerShell to avoid reinforcing a Windows-first pattern.
- Explicitly mention that Azure CLI commands can be run on Windows, Linux, and macOS, and provide guidance for Linux users where relevant.
- If PowerShell is used, clarify that PowerShell Core is available cross-platform, or provide equivalent Bash commands where possible.
- Include a section or note highlighting cross-platform compatibility and any differences in workflow for Linux users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/extended-zones/arc-enabled-workloads-postgre-sql.md
...es/extended-zones/arc-enabled-workloads-postgre-sql.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides only a PowerShell script for deploying Arc-enabled PostgreSQL in an Extended Zone, with no equivalent Bash or Linux shell example. The use of PowerShell as the sole scripting language and the absence of Linux/Unix command-line instructions indicate a clear Windows bias. This may hinder accessibility for users working primarily in Linux environments, which are common for Kubernetes and cloud-native workloads.
Recommendations
- Provide a Bash (or generic shell) script example alongside the PowerShell script to ensure Linux parity.
- Explicitly mention that the steps can be performed on both Windows and Linux, and clarify any OS-specific prerequisites.
- Where possible, use cross-platform tools and scripting patterns (e.g., az CLI, kubectl) in examples, and avoid wrapping them exclusively in PowerShell functions.
- Include notes or sections highlighting any differences or additional steps required for Linux users.
- Consider reordering or supplementing examples so that Linux/Bash instructions are presented first or alongside Windows/PowerShell.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/expressroute/use-s2s-vpn-as-backup-for-expressroute-privatepeering.md
...ps://github.com/MicrosoftDocs/azure-docs/blob/main//articles/expressroute/use-s2s-vpn-as-backup-for-expressroute-privatepeering.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing all Azure-side command-line examples exclusively in PowerShell, with no equivalent Azure CLI (cross-platform) or Bash/Linux examples. Additionally, the traceroute example is shown using the Windows 'tracert' command, and the PowerShell commands for ExpressRoute operations are presented without alternatives. There is no mention of Linux-native tools or workflows for managing or validating Azure networking in this context.
Recommendations
- Provide Azure CLI (az) command equivalents for all PowerShell examples, especially for route validation and ExpressRoute circuit management, to support Linux and macOS users.
- Include traceroute examples using the Linux 'traceroute' command alongside the Windows 'tracert' example.
- Explicitly mention that both Windows and Linux clients can be used for validation steps, and provide sample commands for each.
- Where possible, use cross-platform language in instructions (e.g., 'run the following command in your shell or terminal') rather than assuming a Windows environment.
- Add a note or section highlighting tool parity and any differences in experience between Windows and Linux environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/firewall-manager/quick-secure-virtual-hub-bicep.md
...les/firewall-manager/quick-secure-virtual-hub-bicep.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively deploying and referencing Windows Server virtual machines for firewall testing, instructing users to use Remote Desktop and Internet Explorer (both Windows-specific tools), and omitting any Linux VM deployment or Linux-based connectivity/browser examples. While the deployment and validation steps use both Azure CLI and PowerShell, the scenario for testing the firewall is entirely Windows-centric.
Recommendations
- Include Linux virtual machine deployment in the Bicep template or as an alternative testing scenario.
- Provide instructions for connecting to Linux VMs (e.g., using SSH) and testing connectivity (e.g., using curl, wget, or a Linux browser like Firefox).
- Mention Linux tools and workflows alongside Windows ones, such as using SSH instead of RDP and command-line browsers or curl for connectivity tests.
- Balance the documentation by showing both Windows and Linux examples for firewall rule validation.
- Avoid assuming the use of Internet Explorer or Windows-only features; offer cross-platform alternatives.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/firewall-manager/ip-groups.md
...docs/blob/main//articles/firewall-manager/ip-groups.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates a Windows bias by prominently featuring Azure PowerShell cmdlets in a dedicated section, without providing equivalent Azure CLI or Bash examples. The only command-line tooling referenced is PowerShell, which is traditionally associated with Windows environments. While the page mentions that IP Groups can be managed via the Azure portal, Azure CLI, or REST API, only PowerShell commands are explicitly documented, and no Linux-native or cross-platform CLI examples are given.
Recommendations
- Add equivalent Azure CLI command examples (az network ip-group ...) alongside or before PowerShell cmdlets.
- Include Bash or shell scripting examples where appropriate to demonstrate cross-platform usage.
- Ensure that references to tooling are balanced, mentioning Azure CLI and REST API usage with equal prominence as PowerShell.
- Consider reordering sections so that cross-platform tools (Azure CLI, REST API) are mentioned before or alongside Windows-specific tools like PowerShell.
- Provide links to Azure CLI documentation for managing IP Groups, similar to the PowerShell links provided.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/firewall-manager/quick-firewall-policy.md
...in//articles/firewall-manager/quick-firewall-policy.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only a PowerShell example (Remove-AzResourceGroup) for resource cleanup, with no equivalent Bash, Azure CLI, or Linux-native instructions. Additionally, the firewall policy example specifically references Windows Update using the WindowsUpdate FQDN tag, reinforcing a Windows-centric perspective. There are no Linux-specific tools, commands, or examples provided throughout the quickstart.
Recommendations
- Add equivalent Azure CLI (az group delete) and/or Bash examples for resource cleanup alongside the PowerShell example.
- Include references to Linux update endpoints (such as Ubuntu or Red Hat update repositories) in the firewall policy example, or provide a note on how to allow Linux update traffic.
- Ensure that all command-line instructions are presented in both PowerShell and Azure CLI/Bash formats to support cross-platform users.
- Where Windows-specific FQDN tags or features are mentioned, consider mentioning Linux equivalents or clarifying applicability.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/firewall-manager/rule-hierarchy.md
...blob/main//articles/firewall-manager/rule-hierarchy.md
High Priority
View Details →
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 (Windows-centric) command examples, referencing Windows file paths (e.g., C:\CustomRoles\), and omitting any equivalent instructions or examples for Linux users (such as Azure CLI or Bash). There is no mention of Linux tools or cross-platform command alternatives, and PowerShell is presented as the default/only automation method.
Recommendations
- Provide equivalent Azure CLI (az) command examples for all PowerShell commands, ensuring Linux and macOS users can follow along.
- Use cross-platform file paths in examples (e.g., ~/CustomRoles/ or /home/user/CustomRoles/) or note both Windows and Linux path formats.
- Explicitly mention that the steps can be performed on Linux/macOS using Azure CLI or PowerShell Core, and provide links to relevant documentation.
- Add a section or callout highlighting cross-platform support and any differences in command syntax or tooling.
- Where referencing external tutorials (e.g., for custom roles), link to both PowerShell and Azure CLI versions if available.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/firewall-manager/policy-overview.md
...lob/main//articles/firewall-manager/policy-overview.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page shows a subtle Windows bias by listing Azure PowerShell before CLI in several places and referencing Azure PowerShell specifically for migration and deployment scenarios. There are no explicit Linux or Bash examples, and the CLI is always mentioned after PowerShell, which may suggest a preference for Windows tooling. No Linux-specific tools or workflows are discussed.
Recommendations
- Ensure that Azure CLI (cross-platform) is listed before or alongside Azure PowerShell in all lists of supported tools.
- Provide explicit examples or links for both Azure PowerShell and Azure CLI for all operations, especially migration and deployment.
- Avoid referencing only PowerShell for migration; include CLI and/or ARM template examples.
- Add a section or callout highlighting cross-platform support, including Linux and macOS usage.
- Where possible, provide Bash or shell script equivalents for command-line operations.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/firewall-manager/quick-secure-virtual-hub.md
.../articles/firewall-manager/quick-secure-virtual-hub.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation demonstrates a strong Windows bias by exclusively deploying Windows Server virtual machines, instructing users to use Remote Desktop and Internet Explorer, and providing only PowerShell (Windows-centric) cleanup commands. There are no Linux VM deployment options, no SSH or Linux client instructions, and no Bash/Azure CLI examples.
Recommendations
- Include Linux virtual machine deployment options in the ARM template and documentation steps.
- Provide parallel instructions for connecting to Linux VMs (e.g., using SSH) and testing connectivity with Linux tools such as curl or wget.
- Add Azure CLI or Bash commands for resource cleanup alongside PowerShell examples.
- Mention both Windows and Linux clients in validation steps, and avoid assuming the use of Internet Explorer or Remote Desktop exclusively.
- Where possible, use cross-platform tools or note platform-specific differences.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/firewall/deploy-template.md
...e-docs/blob/main//articles/firewall/deploy-template.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively deploying Windows Server virtual machines in the example, mentioning only Windows in the VM descriptions, and providing only PowerShell commands for resource cleanup. There are no references to Linux VMs, Linux administration, or cross-platform command alternatives.
Recommendations
- Include Linux VM deployment options in the ARM template and documentation, or mention that Linux VMs can be used.
- Provide examples for both Windows and Linux virtual machines, or clarify that the template can be adapted for Linux.
- Offer cross-platform cleanup instructions, such as Azure CLI commands (az group delete), in addition to PowerShell.
- Avoid assuming the administrator will use Windows tools by default; mention alternatives for Linux/macOS users.
- Where possible, use neutral language (e.g., 'virtual machines') unless specifically demonstrating Windows-only features.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/firewall-manager/secure-hybrid-network.md
...in//articles/firewall-manager/secure-hybrid-network.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a clear Windows bias: all virtual machine creation steps use Windows Server images, all automation and configuration examples use PowerShell (specifically Azure PowerShell), and there are no Linux VM or CLI (Bash/Azure CLI) examples. The instructions for installing IIS and remote connectivity are Windows-specific, with no mention of Linux alternatives or parity in the workflow.
Recommendations
- Provide parallel instructions for creating Linux-based virtual machines (e.g., Ubuntu) alongside Windows Server VMs.
- Include Azure CLI (Bash) examples for all resource creation and configuration steps, not just Azure PowerShell.
- Demonstrate how to install a web server (e.g., Apache or Nginx) on a Linux VM, with corresponding automation scripts.
- Show how to connect to Linux VMs (e.g., using SSH) in the testing section, in addition to RDP for Windows.
- When referencing tools or commands, present both Windows and Linux equivalents, or at least alternate between them to avoid a 'Windows-first' impression.
- Explicitly mention that the tutorial can be followed with Linux VMs and tools, and link to relevant Linux documentation where appropriate.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/firewall/easy-upgrade.md
...zure-docs/blob/main//articles/firewall/easy-upgrade.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation mentions PowerShell as a supported method for performing upgrade/downgrade operations, but does not mention or provide examples for equivalent Linux-native tools (such as Azure CLI or Bash scripting). The only command-line tool referenced is PowerShell, which is primarily associated with Windows environments. There are no Linux-specific instructions or examples, and the documentation does not clarify if the process is equally supported or documented for Linux users.
Recommendations
- Include Azure CLI examples for upgrade/downgrade operations, as Azure CLI is cross-platform and widely used on Linux.
- Explicitly mention Bash or shell scripting options if available.
- List all supported tools (Azure Portal, PowerShell, Azure CLI, Terraform) together, rather than highlighting PowerShell first or exclusively.
- Provide step-by-step instructions or code snippets for both Windows (PowerShell) and Linux (Azure CLI/Bash) users to ensure parity.
- Clarify if there are any differences or limitations when using Linux tools versus Windows tools.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/firewall/firewall-known-issues.md
.../blob/main//articles/firewall/firewall-known-issues.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Azure PowerShell cmdlets and CLI support, specifically mentioning PowerShell as a workaround for updating tags and highlighting missing ICMP support in both PowerShell and CLI. There are no Linux-specific examples, tools, or command-line instructions, and the only explicit tool-based workaround is PowerShell-centric. The documentation does not provide parity for Linux users or mention Linux-native tools or workflows.
Recommendations
- Provide equivalent Azure CLI (az) command examples alongside PowerShell cmdlets for all operations, especially for updating tags and managing firewall rules.
- Explicitly mention and document Linux-compatible workflows and tools where possible, ensuring that all mitigation steps are accessible from Linux environments.
- Where PowerShell is referenced, add corresponding Bash/CLI examples or REST API calls that can be executed from Linux systems.
- Audit the documentation for other areas where Windows-centric tools or terminology are used and ensure Linux parity in instructions and troubleshooting steps.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/firewall/dns-settings.md
...zure-docs/blob/main//articles/firewall/dns-settings.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring Azure Firewall DNS settings, but the PowerShell examples are prominent and detailed, reflecting a Windows-centric approach. There are no explicit Linux shell or scripting examples, and PowerShell is highlighted as an equivalent to CLI rather than providing Bash or Linux-native commands. The custom metadata includes 'devx-track-azurepowershell', and PowerShell is given its own tab, reinforcing a Windows bias. No Linux-specific tools or guidance are mentioned.
Recommendations
- Add explicit Bash/Linux shell examples alongside PowerShell, especially for scripting and automation scenarios.
- Include notes or sections for Linux administrators, such as how to use Azure CLI from a Linux environment or integrate with Linux-native DNS tools.
- Balance the order of examples so that CLI/Bash examples are presented before or alongside PowerShell, not after.
- Remove or supplement custom metadata that highlights PowerShell exclusively (e.g., 'devx-track-azurepowershell') with Linux/Bash equivalents.
- Where possible, mention cross-platform tools and avoid assuming PowerShell as the default scripting environment.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/firewall/firewall-preview.md
...-docs/blob/main//articles/firewall/firewall-preview.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation references Azure PowerShell as a configuration method for certain features (e.g., associating public IP addresses in secured hubs), but does not mention or provide examples for equivalent Linux/CLI tools such as Azure CLI. There are no Linux-specific instructions or parity in tooling guidance, and the only command-line tool mentioned is PowerShell, which is traditionally associated with Windows environments.
Recommendations
- Include Azure CLI examples alongside or in place of Azure PowerShell instructions, as Azure CLI is cross-platform and widely used on Linux.
- Explicitly mention that all features can be configured using both Azure PowerShell and Azure CLI, and provide links or examples for both.
- Avoid referencing only Windows-centric tools (like PowerShell) without Linux equivalents, or at least present them in parallel.
- Add a section or note clarifying cross-platform support for all configuration steps, ensuring Linux users are not excluded.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/firewall/quick-create-multiple-ip-bicep.md
...n//articles/firewall/quick-create-multiple-ip-bicep.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation demonstrates a Windows bias by focusing on Windows Server VMs as deployment targets, referencing RDP (a Windows-specific protocol), and providing PowerShell examples for deployment and cleanup. There are no Linux VM examples, nor are SSH or Linux-specific instructions mentioned. The only remote access scenario described is for Windows, and the cleanup step uses only PowerShell.
Recommendations
- Include Linux VM deployment examples in the Bicep template and documentation.
- Mention and provide instructions for connecting to Linux VMs using SSH, alongside the RDP/Windows example.
- Provide Azure CLI commands for all steps, including resource cleanup, not just PowerShell.
- Use neutral language when describing remote access (e.g., 'remote desktop or SSH') and avoid assuming Windows as the default.
- Reference both Windows and Linux tools and patterns equally, or in parallel sections/tabs.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/firewall/customer-controlled-maintenance.md
...//articles/firewall/customer-controlled-maintenance.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a Windows bias by presenting PowerShell instructions before Azure CLI, referencing PowerShell as a primary automation tool, and linking to Windows-centric resources (such as .NET TimeZoneInfo documentation). There are no Linux- or Bash-specific examples, and the CLI section is presented after PowerShell, which is traditionally associated with Windows environments.
Recommendations
- Present Azure CLI instructions before or alongside PowerShell, as Azure CLI is cross-platform and more familiar to Linux users.
- Include Bash shell script examples for common tasks, especially for automation scenarios.
- Reference Linux-compatible tools and documentation (e.g., link to IANA time zone database or cross-platform time zone docs, not just .NET/Windows).
- Explicitly state that both PowerShell and Azure CLI are available on Windows, Linux, and macOS, and provide guidance for users on different platforms.
- Where screenshots or UI references are given, clarify that the Azure portal experience is the same across platforms.
Azure Docs
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 →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell examples and references before Azure CLI and ARM template methods. There are no explicit Linux or cross-platform shell examples, and the PowerShell workflow is emphasized for both deployment and updates. The CLI section is brief and lacks example commands, while Linux-specific considerations or examples are absent.
Recommendations
- Provide explicit Azure CLI command examples, including both deployment and update scenarios, with sample commands.
- Include Bash shell examples for Linux users, demonstrating how to use the Azure CLI to configure the relevant settings.
- Reorder sections so that Azure CLI and ARM template methods are presented before or alongside PowerShell, not after.
- Add a note clarifying that all configuration methods are cross-platform, and highlight any differences or prerequisites for Linux/macOS users.
- Where possible, provide screenshots or terminal outputs from both Windows and Linux environments to ensure parity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/firewall/deploy-cli.md
.../azure-docs/blob/main//articles/firewall/deploy-cli.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively using Windows Server images for virtual machines, referencing Remote Desktop (RDP) for connectivity, and providing only PowerShell-based test commands. There are no examples or instructions for deploying or testing with Linux VMs, nor are Linux command-line tools (such as SSH, curl, or dig) mentioned for connectivity or validation.
Recommendations
- Provide parallel examples for deploying Linux-based virtual machines (e.g., using Ubuntu images) alongside Windows VMs.
- Include instructions for connecting to Linux VMs using SSH, and for Windows VMs using RDP, making both options explicit.
- Offer test commands using common Linux tools (e.g., dig or nslookup for DNS, curl or wget for HTTP requests) in addition to PowerShell/Invoke-WebRequest.
- Clarify that the firewall configuration applies to both Windows and Linux workloads, and that either can be used for testing.
- Consider reordering or presenting both Windows and Linux options together, rather than defaulting to Windows-first throughout the article.