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 176-200 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/application-gateway/application-gateway-ilb-arm.md
...les/application-gateway/application-gateway-ilb-arm.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily biased towards Windows by exclusively providing Azure PowerShell examples and instructions, with no mention of Azure CLI, Bash, or Linux-native tooling. All command-line steps use PowerShell cmdlets, and the only installation guidance refers to the Azure PowerShell module. There are no Linux or cross-platform examples, and the workflow assumes a Windows/PowerShell environment throughout.
Recommendations
- Add equivalent Azure CLI (az) command examples for each step, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Include a section or callouts for Bash/shell users, highlighting any differences or prerequisites for running commands on Linux/macOS.
- Update the 'Before you begin' section to mention both Azure PowerShell and Azure CLI as supported options, with links to installation instructions for each.
- Where PowerShell-specific features or syntax are used, provide alternative approaches for Bash or shell environments.
- Ensure that references to 'Using Windows PowerShell' are balanced with references to Azure CLI or Bash usage guides.
- Consider providing downloadable scripts or templates in both PowerShell and Bash/Azure CLI formats.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dev-box/how-to-hibernate-your-dev-box.md
...ain//articles/dev-box/how-to-hibernate-your-dev-box.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing the Windows App for resuming a dev box, mentioning RDP (Remote Desktop Protocol) errors in troubleshooting, and omitting any Linux-specific instructions or examples. There are no examples or guidance for Linux users, such as using Linux remote desktop clients or accessing the dev box from a Linux environment.
Recommendations
- Add instructions or notes for Linux users on how to resume and connect to a dev box, including recommended Linux-compatible remote desktop clients (e.g., Remmina, FreeRDP).
- When mentioning the Windows App, also mention equivalent Linux workflows or clarify cross-platform options.
- In troubleshooting, include error scenarios and solutions relevant to Linux users (e.g., connection issues with Linux RDP clients).
- Ensure that CLI examples and portal instructions are explicitly stated as cross-platform where applicable, or provide Linux-specific screenshots and guidance if there are differences.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/application-gateway/certificates-for-backend-authentication.md
...ion-gateway/certificates-for-backend-authentication.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively provides instructions and screenshots for exporting certificates using Windows tools (Certificate Manager, PowerShell), with no mention or examples for Linux or cross-platform methods. All step-by-step guidance, screenshots, and tool references are Windows-specific, and the only command-line tool mentioned is PowerShell. There are no instructions for performing equivalent tasks on Linux or macOS, nor are any cross-platform tools (like OpenSSL) referenced.
Recommendations
- Add equivalent step-by-step instructions for exporting certificates using OpenSSL or other common Linux tools.
- Include Linux/macOS command-line examples for exporting public keys and root certificates in Base-64 encoded X.509 (.CER) format.
- Mention and provide guidance for using cross-platform tools (e.g., OpenSSL) before or alongside Windows-specific tools.
- Add screenshots or terminal output examples for Linux/macOS environments.
- Update the 'Next steps' section to reference Linux and cross-platform guides, not just PowerShell.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dev-box/how-to-configure-catalog.md
...lob/main//articles/dev-box/how-to-configure-catalog.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates a bias toward Windows and Azure-centric tooling. All instructions are provided exclusively for the Azure Portal (a web GUI), Azure CLI, and Azure Key Vault, with no mention of Linux-native tools, command-line alternatives, or cross-platform scripting. There are no examples or guidance for performing catalog management tasks using Linux shells, open-source tools, or non-Microsoft platforms. The documentation assumes use of the Azure Portal and does not address parity for Linux users or those preferring CLI or automation outside of Azure's ecosystem.
Recommendations
- Provide equivalent CLI-based instructions using cross-platform tools such as Azure CLI and PowerShell Core (which runs on Linux and macOS), and ensure these are presented alongside or before GUI instructions.
- Include Linux shell (bash) examples for tasks such as managing managed identities, configuring Key Vault, and adding catalogs, to support automation and scripting on Linux systems.
- Reference open-source alternatives or compatible tools where possible (e.g., using REST API calls via curl or httpie for catalog operations).
- Explicitly state platform requirements and clarify that all steps can be performed from Linux, macOS, or Windows, if true. If not, provide workarounds or note limitations.
- Add a section or callouts for Linux users, highlighting any differences or additional steps required when using non-Windows environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dev-box/how-to-customizations-connect-resource-repository.md
...x/how-to-customizations-connect-resource-repository.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively provides examples using Windows-centric paths (e.g., C:\Workspaces), Windows images (microsoftwindowsdesktop_windows-ent-cpc_win11-24H2-ent-cpc), and PowerShell tasks. There are no Linux or cross-platform examples, nor any mention of Linux images, shell tasks, or Linux file paths. This creates a strong Windows bias and may alienate users working in Linux environments.
Recommendations
- Provide parallel examples using Linux images (e.g., ubuntu-latest) and Linux file paths (e.g., /home/dev/Workspaces).
- Include examples that use shell tasks (bash or sh) instead of only PowerShell.
- Mention Linux support explicitly if available, or clarify platform limitations if not.
- Ensure that documentation sections and examples alternate or balance between Windows and Linux scenarios.
- Reference cross-platform tools and patterns where possible, rather than only Windows-specific ones.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/application-gateway/create-multiple-sites-portal.md
...es/application-gateway/create-multiple-sites-portal.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a clear Windows bias: it exclusively uses Windows Server as the backend VM OS, provides only PowerShell commands for configuration (specifically for installing IIS), and all hosts file editing and DNS cache instructions are given for Windows. There are no examples or instructions for deploying Linux VMs, using Linux-native web servers (e.g., Apache, Nginx), or editing hosts files and flushing DNS on Linux/macOS systems.
Recommendations
- Provide parallel instructions for creating Linux-based backend VMs (e.g., Ubuntu), including steps for installing a web server such as Apache or Nginx.
- Include Bash/Azure CLI commands for Linux VM configuration and web server installation, alongside the PowerShell examples.
- Add instructions for editing the /etc/hosts file on Linux/macOS, and explain how to flush the DNS cache on those systems (e.g., using 'sudo systemd-resolve --flush-caches' or 'sudo dscacheutil -flushcache').
- Clarify that Application Gateway supports both Windows and Linux backend servers, and provide guidance for both.
- Where possible, use cross-platform Azure CLI examples instead of (or in addition to) PowerShell.
- Update screenshots and sample commands to show both Windows and Linux environments where relevant.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dev-box/how-to-configure-dev-box-hibernation.md
...ticles/dev-box/how-to-configure-dev-box-hibernation.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a strong Windows bias. All configuration steps, compatibility notes, and troubleshooting instructions are written exclusively for Windows environments. Only Windows-specific tools, settings, and images (such as 'Windows Security', 'Turn Windows features on or off', and 'Visual Studio for Dev Box' images) are mentioned. There are no references to Linux-based dev boxes, nor examples or instructions for enabling hibernation on Linux images. The Azure CLI examples all use '--os-type windows', and there is no discussion of Linux compatibility or equivalent settings.
Recommendations
- Explicitly state whether hibernation is supported for Linux-based dev boxes. If not supported, clarify this early in the documentation.
- If Linux support exists, provide parallel instructions and examples for Linux images, including any required settings or compatibility considerations.
- Include troubleshooting steps relevant to Linux environments, or link to Linux-specific resources if available.
- When referencing tools or settings (such as enabling nested virtualization), provide Linux equivalents or note their absence.
- Avoid assuming all users are working with Windows; mention Linux options or limitations where appropriate.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dev-box/how-to-create-dev-boxes-developer-portal.md
...es/dev-box/how-to-create-dev-boxes-developer-portal.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias by recommending and describing Windows-specific tools (Windows App, legacy Remote Desktop client) for connecting to dev boxes, with no mention of Linux-native clients or workflows. While the Windows App is noted as being cross-platform, there are no explicit Linux instructions, screenshots, or examples. Linux users are not given parity in guidance for connecting to or managing dev boxes.
Recommendations
- Explicitly mention and provide instructions for connecting to dev boxes from Linux systems, including recommended RDP clients (e.g., Remmina, FreeRDP, rdesktop) and any required configuration.
- Include Linux-specific screenshots or terminal commands where relevant, especially for connecting via RDP or browser.
- Clarify whether all features (such as multiple monitor support) are available on Linux clients, and provide guidance for any limitations.
- Add a section or callout for Linux users, ensuring they are aware of supported workflows and tools.
- When listing client options, avoid always listing Windows tools first; consider grouping by platform or stating cross-platform options up front.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dev-box/how-to-configure-team-customizations.md
...ticles/dev-box/how-to-configure-team-customizations.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a strong Windows bias. All built-in task examples and references are centered on PowerShell and WinGet, both of which are Windows-specific technologies. Desired State Configuration (DSC), another Windows/PowerShell-centric tool, is presented as the primary configuration-as-code solution. There are no examples or mentions of Linux-based tools, shell scripts, or cross-platform approaches for image customization. The documentation implicitly assumes the dev box environment is Windows, with no guidance for Linux users or teams.
Recommendations
- Add examples and guidance for customizing dev boxes using Linux shell scripts (e.g., Bash) and package managers (e.g., apt, yum, dnf, zypper) where applicable.
- Explicitly state whether Dev Box supports Linux-based dev boxes, and if so, provide parity in documentation for Linux customization workflows.
- Include sample image definition files that use Linux tools and scripting, alongside the PowerShell/WinGet examples.
- Mention and document cross-platform configuration-as-code solutions (e.g., Ansible, cloud-init) if supported.
- Clarify in the prerequisites or introduction if the feature set is Windows-only, or provide a roadmap for Linux support.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/application-gateway/deploy-basic-portal.md
...n//articles/application-gateway/deploy-basic-portal.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a strong Windows and PowerShell bias. All command-line instructions use Azure PowerShell, with no mention of Azure CLI or Bash alternatives. The VM creation example exclusively uses Windows Server, and the backend setup relies on Windows-specific tools (IIS, PowerShell scripts). There are no examples or guidance for deploying or testing with Linux VMs or using Linux-native tools, nor are cross-platform command-line options presented.
Recommendations
- Provide equivalent Azure CLI (az) commands alongside Azure PowerShell for all resource management steps, including preview registration and VM extension installation.
- Include Linux VM creation steps as an alternative to Windows Server, and show how to install a web server (e.g., Apache or Nginx) on Linux using Bash scripts or cloud-init.
- When demonstrating backend pool configuration, offer both Windows and Linux examples, and clarify that Application Gateway supports both.
- For testing, show how to verify backend connectivity using both IIS (Windows) and a Linux web server, including sample curl or wget commands.
- Explicitly mention that the steps are cross-platform where possible, and avoid assuming a Windows-only environment.
- Add notes or callouts highlighting parity and differences between Windows and Linux approaches, especially for VM extensions and scripting.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/application-gateway/classic-to-resource-manager.md
...les/application-gateway/classic-to-resource-manager.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell-based examples and instructions for managing and migrating classic Application Gateway resources. There are no Bash, Azure CLI (Linux shell), or cross-platform examples for key migration or cleanup steps. PowerShell is mentioned and linked before Azure CLI, and the only detailed command-line walkthrough is for PowerShell. References to installing and using the Azure PowerShell Service Management module further reinforce the Windows-centric approach, with no mention of Linux or macOS alternatives.
Recommendations
- Provide equivalent Azure CLI (bash) examples for all PowerShell commands, especially for cleanup and migration steps.
- Include explicit instructions or links for Linux/macOS users, such as how to install and use Azure CLI for these tasks.
- Reorder example listings to present cross-platform tools (Azure CLI, ARM templates) before or alongside PowerShell.
- Where PowerShell modules are referenced, note their platform compatibility and provide alternatives for non-Windows environments.
- Add a section or note clarifying that all migration and management tasks can be performed from Linux/macOS using Azure CLI, and provide sample commands.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dev-box/how-to-configure-user-customizations.md
...ticles/dev-box/how-to-configure-user-customizations.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias by exclusively referencing Windows-specific tools (WinGet), providing configuration examples only for Windows environments, and omitting any mention or examples for Linux-based dev boxes or package managers. The guidance and examples assume a Windows context, with no Linux parity or alternatives offered.
Recommendations
- Include equivalent examples for Linux-based dev boxes, such as using apt, yum, or other Linux package managers in customization files.
- Mention and demonstrate how to configure dev boxes running Linux, if supported, and provide sample YAML customization files for Linux environments.
- If WinGet is only supported on Windows, clarify this limitation and suggest Linux alternatives or note the lack of support.
- Ensure that documentation structure and examples do not assume Windows as the default or only environment; present Linux and Windows options side by side where possible.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/application-gateway/ipv6-application-gateway-arm-template.md
...ation-gateway/ipv6-application-gateway-arm-template.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates bias towards Windows by providing only a PowerShell example (Remove-AzResourceGroup) for resource cleanup, referencing IIS (a Windows web server) as the backend and validation method, and omitting any Linux/CLI/bash examples for deployment, validation, or cleanup. There are no instructions or examples for users who prefer Linux tools or environments.
Recommendations
- Provide equivalent Azure CLI (az group delete) and/or Bash examples for resource cleanup alongside the PowerShell example.
- Include instructions or examples for deploying and validating the application gateway using Linux-based VMs (e.g., using NGINX or Apache instead of IIS).
- Mention and demonstrate Linux-friendly tools and workflows where applicable, ensuring parity in validation and management steps.
- Explicitly state that both Windows and Linux users are supported, and link to relevant Linux/CLI documentation where available.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/application-gateway/application-gateway-key-vault-common-errors.md
...gateway/application-gateway-key-vault-common-errors.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell examples for certificate operations, referencing PowerShell and Azure CLI as alternatives but not providing CLI (cross-platform) examples. All step-by-step instructions for resolving issues are oriented around the Azure Portal UI, which is platform-agnostic but often aligns with Windows user workflows. There is a lack of Linux-specific or cross-platform command-line examples, and PowerShell is presented as the default scripting tool for automation, with no Bash or Azure CLI equivalents shown.
Recommendations
- Provide Azure CLI (az) command examples alongside PowerShell for all certificate and Key Vault operations, ensuring parity for Linux and macOS users.
- Explicitly mention that PowerShell examples are for Windows and offer Bash/Azure CLI alternatives for cross-platform users.
- Where automation is discussed, include both PowerShell and Bash/CLI scripts to cover both Windows and Linux environments.
- Review all troubleshooting steps to ensure that none assume a Windows environment or toolset by default.
- Add a note at the beginning of the page clarifying that both PowerShell and Azure CLI can be used, and link to documentation for both.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/application-gateway/quick-create-portal.md
...n//articles/application-gateway/quick-create-portal.md
High Priority
View Details →
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 as backend examples, providing only PowerShell commands (for IIS installation), and omitting any Linux VM or cross-platform CLI examples for backend setup and testing. The workflow for installing a web server and verifying the Application Gateway is entirely Windows-centric, with no mention of Linux alternatives or parity in instructions.
Recommendations
- Include parallel instructions for creating a Linux VM (e.g., Ubuntu) as a backend server, alongside the Windows example.
- Provide Linux-specific commands (such as using Azure CLI or SSH) to install a web server (e.g., Apache or Nginx) for testing, in addition to the PowerShell/IIS example.
- Show both Windows and Linux options for backend pool configuration and testing, making it clear that Application Gateway supports both.
- Where PowerShell is used, offer equivalent Azure CLI/bash commands for Linux users.
- Update screenshots and step-by-step instructions to reflect both Windows and Linux VM creation and configuration.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/application-gateway/application-gateway-diagnostics.md
...application-gateway/application-gateway-diagnostics.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell examples for enabling diagnostic logging, referencing Windows-centric tools (Excel, Power BI, Visual Studio, C#), and omitting equivalent Linux/CLI/Bash instructions. No Azure CLI, Bash, or Linux-native tooling is mentioned, and the workflow assumes familiarity with Windows environments and tools.
Recommendations
- Add equivalent Azure CLI (az) examples for enabling and configuring diagnostic logging, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Include Bash shell command examples for log retrieval and processing (e.g., using jq, grep, awk, sed) to demonstrate Linux-native workflows.
- Mention Linux-compatible data visualization tools (e.g., LibreOffice Calc, csvkit, or open-source alternatives) alongside Excel and Power BI.
- Reference code samples in Python or other cross-platform languages, not just C# and Visual Studio.
- Reorder examples or provide parallel instructions so that Linux and cross-platform methods are presented equally or before Windows-specific ones.
- Explicitly state that all features are available via both PowerShell and Azure CLI, and provide links to both sets of documentation.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dev-box/how-to-elevate-privilege-dev-box.md
...//articles/dev-box/how-to-elevate-privilege-dev-box.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is exclusively focused on configuring Intune Endpoint Privilege Management for Windows-based dev boxes, with all examples, screenshots, and instructions referencing Windows operating systems, tools, and UI. There is no mention of Linux or cross-platform support, and all procedures assume a Windows environment.
Recommendations
- Explicitly state in the prerequisites and introduction whether Endpoint Privilege Management is supported only on Windows, or clarify the lack of Linux support.
- If Linux support exists or is planned, add equivalent instructions, examples, and screenshots for configuring privilege management on Linux dev boxes.
- Mention Linux (and macOS, if relevant) in the list of supported operating systems, or clarify that only Windows is supported.
- Provide guidance or links to alternative privilege management solutions for Linux users if Intune Endpoint Privilege Management is not available for Linux.
- Ensure that future documentation for cross-platform tools includes parity in examples and instructions for all supported operating systems.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dev-box/how-to-enable-single-sign-on.md
...main//articles/dev-box/how-to-enable-single-sign-on.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by focusing exclusively on Windows-based workflows and terminology. All examples, instructions, and user experiences are described in the context of Windows environments, with no mention of Linux or cross-platform scenarios. The only authentication method discussed is Microsoft Entra (formerly Azure AD), and the related content references Windows 365. There are no Linux-specific instructions, screenshots, or considerations, and the user experience is described solely for Windows users.
Recommendations
- Include explicit statements about Linux support or limitations for Dev Box SSO, clarifying whether Linux-based dev boxes or clients are supported.
- If Linux is supported, provide parallel instructions and screenshots for enabling SSO from a Linux client or for Linux-based dev boxes.
- Describe the SSO user experience for Linux users, including any differences in authentication prompts or workflows.
- Reference relevant Linux tools or authentication mechanisms if applicable (e.g., Kerberos, PAM, or integration with Linux desktop environments).
- Add related content or links for configuring SSO in non-Windows environments, if supported.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/application-gateway/how-to-troubleshoot-application-gateway-session-affinity-issues.md
...oubleshoot-application-gateway-session-affinity-issues.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias by providing PowerShell as the only CLI example for checking Application Gateway settings, exclusively recommending Fiddler (a Windows-centric tool) for network capture, and referencing Windows-specific actions such as 'Run as administrator.' There are no Linux or cross-platform alternatives suggested for command-line or network debugging tasks, and Windows tools are mentioned first and exclusively.
Recommendations
- Provide equivalent Azure CLI or Azure Cloud Shell examples for checking Application Gateway settings, as these are cross-platform and widely used on Linux.
- Include examples using Linux-native tools for network capture and HTTP debugging, such as tcpdump, Wireshark, or curl, alongside Fiddler.
- Mention cross-platform or browser-based alternatives to Fiddler, such as mitmproxy or browser developer tools.
- Avoid instructions that assume a Windows environment (e.g., 'Run as administrator') or provide Linux/macOS equivalents (e.g., 'use sudo').
- Ensure that troubleshooting steps and tool recommendations are inclusive of both Windows and Linux users, ideally presenting cross-platform options first or side-by-side.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dev-box/how-to-generate-visual-studio-caches.md
...ticles/dev-box/how-to-generate-visual-studio-caches.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily oriented toward Windows environments, specifically referencing Visual Studio (a Windows-only IDE), PowerShell commands, and Windows-centric tools and patterns. There are no examples or instructions for Linux or cross-platform environments, and all automation and scripting guidance assumes a Windows context. Linux users or those using cross-platform Dev Box images are not addressed.
Recommendations
- Explicitly state that the instructions are Windows-specific, or clarify platform limitations at the start of the document.
- If possible, provide equivalent steps or guidance for Linux-based dev boxes, or explicitly mention if such functionality is not available.
- Where automation is discussed (e.g., scripting cache generation), offer Bash or cross-platform scripting alternatives if supported.
- Reference cross-platform tools or workflows where possible, or provide links to Linux/macOS documentation for similar scenarios.
- Consider including a table or section comparing Windows and Linux support for Visual Studio caching and Git optimizations in Dev Box images.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/application-gateway/http-response-codes.md
...n//articles/application-gateway/http-response-codes.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias. In the 504 Gateway time-out section, IIS (a Windows web server) is mentioned first, with detailed configuration guidance and a direct link to Microsoft documentation. Nginx (commonly used on Linux) is mentioned second, with less detail and no direct configuration link. There are no Linux/POSIX command-line examples or troubleshooting steps, and the only authentication protocol referenced by name is NTLM, which is Windows-specific. No PowerShell commands are present, but Windows-centric tools and patterns are prioritized.
Recommendations
- Present Linux and Windows backend server examples in parallel, giving equal detail and prominence to both IIS and Nginx/Apache.
- Provide direct links to Nginx and Apache documentation for relevant configuration settings, similar to the IIS link.
- Include troubleshooting steps or examples using Linux command-line tools (e.g., curl, grep, tail) where appropriate.
- Mention Linux authentication protocols (e.g., Kerberos, basic auth) alongside NTLM when discussing authentication-related errors.
- Ensure that any references to Windows-specific tools or protocols are balanced with Linux equivalents.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/application-gateway/configure-web-app.md
...ain//articles/application-gateway/configure-web-app.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a strong Windows/PowerShell bias. All CLI/scripted examples are exclusively provided in PowerShell, with no Bash, Azure CLI, or Linux-native command equivalents. The scripting sections assume the use of PowerShell cmdlets (Get-AzApplicationGateway, Add-AzApplicationGatewayBackendAddressPool, etc.), which are primarily Windows-centric. There are no Linux shell or cross-platform CLI examples, and the only automation path shown is via PowerShell. Additionally, the 'devx-track-azurepowershell' metadata and the ordering of examples (PowerShell before any mention of CLI) reinforce this bias.
Recommendations
- Provide equivalent Azure CLI (az) examples for all PowerShell scripts, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Include Bash shell script examples where appropriate, especially for tasks like DNS configuration, certificate management, and HTTP requests (e.g., using curl).
- Explicitly mention that all PowerShell scripts can be run on PowerShell Core on Linux/macOS, or clarify any Windows-only dependencies.
- Add a 'Linux/macOS' tab alongside 'PowerShell' and 'Azure portal' for each procedural section, ensuring parity in automation and scripting guidance.
- Avoid referencing only Windows tools or patterns (such as 'Invoke-WebRequest' without mentioning 'curl' or 'wget').
- Update metadata and introductory text to reflect support for cross-platform management, not just PowerShell.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dev-box/how-to-connect-dev-box-virtual-switch.md
...icles/dev-box/how-to-connect-dev-box-virtual-switch.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively uses Windows-centric tools and commands (PowerShell cmdlets like New-VMSwitch, New-NetIPAddress, New-NetNat, and Get-NetAdapter) for configuring virtual switches and NAT networks. There are no examples or guidance for performing equivalent tasks on Linux-based dev boxes or with cross-platform virtualization tools. UI instructions reference Windows-specific dialogs, and no Linux alternatives are provided.
Recommendations
- Add equivalent instructions and examples for Linux environments, such as using libvirt/virt-manager, iptables/nftables, and network configuration files.
- Include Linux command-line examples (e.g., using nmcli, ip, brctl, or virsh) for creating virtual switches and NAT networks.
- Provide screenshots or step-by-step guides for configuring network settings on Linux guest VMs.
- Clearly indicate when instructions are Windows-specific and offer cross-platform alternatives where possible.
- Consider a section or callout for macOS users if relevant, or clarify platform support up front.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/application-gateway/key-vault-certs.md
.../main//articles/application-gateway/key-vault-certs.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 only PowerShell-based configuration examples and referencing PowerShell as the primary CLI tool for managing Azure Application Gateway and Key Vault integration. There are no equivalent Azure CLI (cross-platform) or Bash examples, and PowerShell is mentioned before or instead of other tools throughout the page. This may disadvantage Linux or macOS users who prefer or require non-Windows tooling.
Recommendations
- Provide equivalent Azure CLI (az) examples alongside PowerShell commands for all configuration steps, especially for referencing Key Vault secrets and configuring Application Gateway.
- When mentioning scripting or automation, present Azure CLI and PowerShell in parallel, or lead with Azure CLI as the more cross-platform option.
- Include Bash shell snippets for common tasks, or clarify that all steps can be performed on Linux/macOS using Azure CLI.
- Avoid language that assumes PowerShell is the default or only automation tool; explicitly state that both PowerShell and Azure CLI are supported.
- Add a 'Platform considerations' section to clarify tool parity and direct users to appropriate instructions for their OS.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/application-gateway/ipv6-application-gateway-portal.md
...application-gateway/ipv6-application-gateway-portal.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively using Windows Server as the backend VM example and providing only PowerShell commands (specifically for installing IIS) without any Linux/CLI alternatives. There are no examples or instructions for deploying a Linux VM, nor for installing a web server (like Nginx or Apache) on Linux, nor are Bash/Azure CLI commands provided for equivalent tasks. This may hinder Linux users or those preferring cross-platform solutions.
Recommendations
- Provide parallel instructions for deploying a Linux VM (e.g., Ubuntu) as a backend target, including relevant screenshots.
- Include steps to install a web server (such as Nginx or Apache) on the Linux VM for testing, using Bash or Azure CLI commands.
- Offer Azure CLI examples alongside PowerShell for tasks like installing extensions or managing resources.
- Explicitly mention that both Windows and Linux VMs are supported as backend targets, and link to relevant documentation for both.
- Where scripting is shown (e.g., installing IIS), provide equivalent Bash/CLI scripts for Linux.
- Consider alternating the order of Windows and Linux examples, or presenting them side-by-side, to avoid 'windows_first' bias.