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 151-175 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/application-gateway/overview-v2.md
...blob/main//articles/application-gateway/overview-v2.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by primarily referencing Azure PowerShell scripts and cmdlets for migration and preview registration, and by using PowerShell-centric examples in the CLI sections. There are no explicit Linux/bash examples or references to cross-platform command-line usage, and PowerShell is mentioned before Azure CLI or other tools. The documentation does not provide parity for Linux users or those preferring bash scripting.
Recommendations
- Provide equivalent Azure CLI (bash) examples alongside or before PowerShell examples for all script-based instructions, especially for migration and preview registration.
- Clearly indicate that Azure CLI commands can be run on any platform (Windows, Linux, macOS), and provide bash syntax where appropriate.
- Balance references to PowerShell and CLI in the text, ensuring that Linux-friendly tools are not secondary.
- Add explicit Linux/bash usage notes or examples in sections that currently only mention PowerShell.
- Where possible, link to both PowerShell and CLI tutorials or documentation in the 'Next steps' and other guidance sections.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/overview-security.md
...s/blob/main//articles/app-service/overview-security.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a Windows bias, particularly in the 'Static IP restrictions' section, where features and configuration options are described specifically for 'App Service on Windows' with no mention of Linux equivalents or alternatives. Windows-specific tools and patterns (such as web.config and IIS dynamic IP security) are referenced, while Linux-based approaches are omitted. No PowerShell-specific examples are present, but the overall focus and ordering prioritize Windows scenarios and tools.
Recommendations
- For every Windows-specific feature or configuration (such as IP restrictions via web.config), explicitly state whether an equivalent exists for App Service on Linux. If not, provide alternative guidance or a note clarifying the limitation.
- Add Linux-specific examples or configuration instructions where applicable, especially for security features like IP restrictions.
- Avoid referencing Windows tools (e.g., web.config, IIS modules) without mentioning Linux alternatives or noting their absence.
- Where features are only available on Windows, clearly label them as such and provide links or suggestions for Linux users to achieve similar outcomes, if possible.
- Consider reordering sections or examples so that Linux and Windows are given equal prominence, or group OS-specific guidance under clearly marked headings.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/tutorial-connect-msi-azure-database.md
...les/app-service/tutorial-connect-msi-azure-database.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias, especially in the 'Set up your dev environment' section. Visual Studio for Windows is presented first and in more detail, while Visual Studio for Mac is described as lacking integration. Windows-specific tools (Visual Studio, Azure PowerShell) are mentioned before or more prominently than their cross-platform or Linux equivalents. PowerShell is given its own section, and Windows-centric development patterns are emphasized, while Linux-specific workflows, shells, or editors are not mentioned.
Recommendations
- Reorder the 'Set up your dev environment' section to present cross-platform tools (Azure CLI, Visual Studio Code) before Windows-specific ones.
- Include explicit instructions or notes for Linux users, such as using Azure CLI in Bash or Zsh, and mention common Linux editors (e.g., VS Code, Vim, Emacs) for parity.
- Provide examples of signing in and running code on Linux and macOS, not just Windows.
- Clarify that Azure CLI and VS Code are fully supported on Linux and macOS, and provide links to installation instructions for those platforms.
- Avoid language that frames Windows tools as the default or primary option; instead, present all supported platforms equally.
- Consider adding a troubleshooting section or FAQ entries for common Linux/macOS issues.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/tutorial-connect-msi-sql-database.md
...icles/app-service/tutorial-connect-msi-sql-database.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation exhibits a Windows bias by prioritizing Windows and Visual Studio (Windows) workflows, providing PowerShell and SQLCMD (Windows-centric) instructions, and omitting explicit Linux/macOS development environment examples for key steps such as database permission granting and debugging. Linux equivalents, such as using sqlcmd on Linux or cross-platform editors like VS Code, are not given equal prominence or detail.
Recommendations
- Provide explicit Linux/macOS instructions for all command-line steps, especially for connecting to Azure SQL Database (e.g., using sqlcmd on Linux/macOS, or Azure Data Studio).
- Include examples for common Linux development environments (e.g., VS Code on Linux, JetBrains Rider) alongside Windows/Visual Studio.
- Avoid assuming PowerShell or Windows tools as the default; offer Bash and cross-platform CLI alternatives where possible.
- Structure environment setup sections so that Windows and Linux/macOS instructions are presented in parallel tabs or sections, rather than Windows-first.
- Clarify that all Azure CLI commands can be run from Bash on Linux/macOS, and provide troubleshooting notes for any OS-specific differences.
- When referencing file paths or configuration files, use OS-agnostic language or provide both Windows and Linux/macOS path examples.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/application-gateway/configuration-infrastructure.md
...es/application-gateway/configuration-infrastructure.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias. It references Azure PowerShell commands for restarting the Application Gateway but does not provide equivalent Azure CLI (cross-platform) commands or Linux shell examples. The only explicit command-line examples are PowerShell cmdlets, and there is no mention of Bash, Linux, or cross-platform scripting. The documentation also refers to Azure CLI only in passing, without concrete examples, and PowerShell is mentioned first when describing how to change the subnet of an existing Application Gateway instance.
Recommendations
- Provide Azure CLI (az) command examples alongside or before PowerShell examples for all management tasks, especially for restarting and modifying Application Gateway resources.
- Explicitly mention that both Azure CLI and PowerShell are supported, and link to relevant documentation for both.
- Where possible, include Bash/Linux shell command examples or clarify that Azure CLI commands are cross-platform.
- Avoid referencing only PowerShell cmdlets in procedural steps; always offer a CLI alternative.
- Ensure that any links to command references include both PowerShell and CLI documentation.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dev-box/concept-what-are-dev-box-customizations.md
...les/dev-box/concept-what-are-dev-box-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 by exclusively referencing PowerShell scripts and WinGet as the mechanisms for Dev Box customization tasks. There is no mention of Linux shell scripting, Bash, or Linux package managers. The examples, terminology, and tooling are all Windows-centric, and there are no Linux equivalents or cross-platform considerations provided.
Recommendations
- Include examples and instructions for using Bash scripts and Linux package managers (such as apt, yum, or zypper) in customization tasks.
- Clarify whether Dev Box supports Linux-based images and, if so, provide explicit guidance for customizing Linux dev boxes.
- Present both Windows (PowerShell/WinGet) and Linux (Bash/apt/yum) options side-by-side in documentation and examples.
- Avoid language that assumes PowerShell or WinGet are the only supported or recommended tools; instead, use cross-platform terminology where possible.
- Add a section or FAQ addressing cross-platform support and how to achieve parity between Windows and Linux developer environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/overview-vnet-integration.md
...ain//articles/app-service/overview-vnet-integration.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a moderate Windows bias. Windows-specific features (such as Windows Containers and Windows Server Active Directory) are discussed in detail, including subnet/IP calculations and limitations, while Linux-specific scenarios are only briefly mentioned (e.g., a single note about Linux continuous deployment network dependencies). There are no Linux-specific configuration examples, troubleshooting steps, or parity in container/app hosting details. Windows terminology and tools are referenced first or exclusively in several sections.
Recommendations
- Add Linux-specific examples and guidance, especially for App Service on Linux and Linux containers, including subnet/IP calculations and limitations.
- Provide parity in troubleshooting steps for both Windows and Linux hosting environments.
- Include explicit Linux command-line (Bash/CLI) examples where relevant, not just Azure Portal or generic instructions.
- Balance the discussion of Windows-specific features (e.g., Windows Containers) with equivalent Linux container scenarios, or clearly state if a feature is Windows-only.
- Ensure that any references to Windows tools or patterns are matched with Linux equivalents, or clarify platform applicability.
- Consider adding a section or callouts for common Linux-specific networking or integration issues.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/scripts/powershell-deploy-local-git.md
...les/app-service/scripts/powershell-deploy-local-git.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exclusively uses PowerShell for all examples and instructions, which is primarily associated with Windows environments. There are no examples or guidance for Linux or cross-platform command-line tools (such as Bash or Azure CLI). The focus on PowerShell commands and lack of mention of Linux equivalents or alternatives demonstrates a clear Windows bias.
Recommendations
- Provide equivalent examples using Azure CLI (az) commands, which are cross-platform and commonly used on Linux and macOS.
- Include Bash script samples alongside PowerShell to ensure Linux users can follow along.
- Mention that PowerShell Core is available cross-platform, but clarify any differences or limitations when running on Linux/macOS.
- Add a section or links for deploying from local Git using Linux-native tools and workflows.
- Ensure that documentation titles and descriptions reflect cross-platform applicability if relevant.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/application-gateway/mutual-authentication-overview.md
.../application-gateway/mutual-authentication-overview.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing detailed PowerShell examples and references first, with more extensive PowerShell coverage than Azure CLI. There are no Linux-specific command-line examples (such as Bash or OpenSSL), and the 'Next steps' section directs users to a PowerShell-based guide, omitting Linux/CLI-focused guides. The documentation assumes familiarity with Windows tooling and patterns, potentially disadvantaging Linux users.
Recommendations
- Provide equal depth and detail for Azure CLI (cross-platform) commands as for PowerShell, including full configuration workflows.
- Include Linux-native examples for certificate extraction and management (e.g., using OpenSSL commands to extract or inspect certificate chains).
- In the 'Next steps' section, link to both PowerShell and Azure CLI/Linux-based configuration guides.
- When referencing tools or commands, present Azure CLI (cross-platform) examples before or alongside PowerShell to avoid a Windows-first impression.
- Explicitly mention that all configuration steps can be performed on Linux/macOS using Azure CLI, and provide any OS-specific caveats if applicable.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/application-gateway/custom-error.md
...lob/main//articles/application-gateway/custom-error.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides only Azure PowerShell examples for configuring custom error pages, with no mention of Azure CLI, Bash, or other cross-platform/Linux-friendly tools. This creates a bias towards Windows users and may hinder Linux or macOS administrators who prefer or require non-PowerShell workflows.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell commands shown, demonstrating how to configure custom error pages using az network application-gateway commands.
- Explicitly mention that both PowerShell and Azure CLI can be used, and provide links to relevant CLI documentation.
- Where possible, include Bash script snippets or guidance for Linux/macOS users, especially for common tasks like uploading HTML files to Azure Blob Storage.
- Review screenshots and UI instructions to ensure they are not Windows-specific (e.g., avoid showing only Windows file dialogs or PowerShell terminals).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/provision-resource-terraform.md
...//articles/app-service/provision-resource-terraform.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation displays a mild Windows bias, particularly in the prerequisites section, where Windows and PowerShell options are listed alongside (and sometimes before) Linux/Bash equivalents. There is also a focus on Windows-specific tooling (e.g., Visual Studio Code extension) and patterns, though Linux examples are present and reasonably complete.
Recommendations
- List Linux/Bash options before Windows/PowerShell options in the prerequisites to avoid the impression of Windows primacy.
- Ensure parity in instructions for both Linux and Windows, including explicit mention of Linux-native editors (e.g., nano, vim) alongside Visual Studio Code.
- Where PowerShell is mentioned, ensure Bash/Linux shell equivalents are equally described and linked.
- Consider adding a section or callout for running Terraform on macOS or generic Unix systems, not just 'Linux' or 'Windows'.
- Where possible, avoid referring to Windows-specific tools (like Visual Studio Code) as the default or only editor; suggest alternatives or clarify cross-platform support.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/scenario-secure-app-access-storage.md
...cles/app-service/scenario-secure-app-access-storage.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows tools and workflows. It provides installation instructions using the Visual Studio Package Manager Console (a Windows-centric tool) and PowerShell commands, while only briefly mentioning the .NET Core CLI (which is cross-platform) and not providing any Linux- or macOS-specific guidance. There are no explicit Linux or macOS terminal examples, and the workflow assumes the use of Visual Studio, which is primarily a Windows IDE.
Recommendations
- Add explicit Linux/macOS terminal instructions for installing NuGet packages, such as using the dotnet CLI in bash/zsh.
- Reorder the installation instructions to present the cross-platform .NET Core CLI method before the Visual Studio/PowerShell method.
- Clarify that Visual Studio is optional and provide alternative instructions for users on Linux or macOS.
- Include a note or section addressing any OS-specific considerations for running the .NET sample code.
- Where possible, avoid referencing Windows-only tools (like the Package Manager Console) without providing equivalent cross-platform alternatives.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dev-box/how-to-configure-intune-conditional-access-policies.md
...ttps://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dev-box/how-to-configure-intune-conditional-access-policies.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows-centric bias by focusing on Windows-specific tools and terminology (e.g., Microsoft Remote Desktop, Windows 365, Windows Azure Service Management API) without mentioning Linux equivalents or cross-platform alternatives. The examples and app tables reference Windows tools exclusively, and there are no instructions or examples for Linux users or administrators. The documentation assumes the use of Windows environments and does not address how Linux clients or administrators might interact with Dev Boxes or Conditional Access policies.
Recommendations
- Include examples and guidance for Linux users, such as how to access Dev Boxes from Linux clients (e.g., using open-source RDP clients like FreeRDP or Remmina).
- Mention cross-platform tools (such as Azure CLI, which runs on Windows, Linux, and macOS) more prominently, and provide usage examples for non-Windows environments.
- Clarify whether Conditional Access policies and supported apps are compatible with Linux clients, and provide any necessary configuration steps or caveats.
- Add a section or callout specifically addressing Linux/macOS users, including supported workflows and any limitations.
- Review terminology and app tables to ensure non-Windows scenarios are acknowledged and supported where possible.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/scripts/powershell-deploy-staging-environment.md
...rvice/scripts/powershell-deploy-staging-environment.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively uses PowerShell for all examples, commands, and explanations, which is traditionally associated with Windows environments. There are no examples or references to equivalent Linux-native tools (such as Bash, Azure CLI, or shell scripting), nor is there guidance for users on non-Windows platforms. The focus on PowerShell and absence of cross-platform alternatives demonstrates a clear Windows-first and PowerShell-heavy bias.
Recommendations
- Provide equivalent examples using Azure CLI (az commands) and Bash scripts, which are more common on Linux and macOS.
- Include a section or callout noting that all operations can be performed cross-platform, and link to Linux/macOS setup guides.
- Reorder or parallelize examples so that Linux/Bash/Azure CLI instructions are given equal prominence to PowerShell.
- Mention that PowerShell Core is cross-platform, but clarify any differences or prerequisites for Linux/macOS users.
- Add troubleshooting or environment setup notes for non-Windows users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/tutorial-custom-container.md
...ain//articles/app-service/tutorial-custom-container.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation is structured with a clear separation between Windows and Linux via pivots, but the Windows section is presented first and is significantly more prescriptive and tool-specific. The Windows tutorial relies heavily on Visual Studio, Windows Explorer, and PowerShell scripts, with no mention of equivalent Linux workflows or cross-platform alternatives. The Linux section, by contrast, uses generic CLI and Docker commands, but the Windows section lacks any Linux or cross-platform guidance for users who may be developing on non-Windows systems. There is also a lack of parity in the depth of explanation for certain steps (e.g., font installation and orchestration support are only covered for Windows).
Recommendations
- Provide cross-platform alternatives in the Windows section, such as how to build and deploy custom containers using the .NET CLI and Docker commands instead of Visual Studio and Windows Explorer.
- Include Linux-based examples for tasks like font installation (e.g., using RUN commands in the Dockerfile to install fonts on Linux images) to mirror the Windows example.
- Avoid assuming the use of Windows-specific tools (Visual Studio, Windows Explorer, PowerShell) as the only workflow; mention VS Code, JetBrains Rider, or CLI-based approaches where possible.
- Reorder or clarify the pivots so that neither Windows nor Linux is implicitly prioritized, or explicitly state that both are equally supported.
- Where PowerShell scripts are referenced, provide Bash or shell script equivalents for Linux users.
- Ensure that all major steps (such as adding orchestration support, configuring the Dockerfile, and publishing to Azure Container Registry) have both Windows and Linux instructions, or at least cross-references.
- Add a summary table at the top comparing the Windows and Linux workflows, highlighting tool differences and parity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/quickstart-dotnetcore.md
...ob/main//articles/app-service/quickstart-dotnetcore.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a moderate Windows bias. Visual Studio (Windows-only) is presented as the primary IDE in several sections, and PowerShell is given a dedicated section with detailed steps, while Linux-specific command-line or shell examples are less emphasized. In the PowerShell section, Linux deployment is explicitly deferred to other tools, and the file path and compression commands (e.g., Compress-Archive, cd bin\Release\net8.0\publish) are Windows-specific. There are missing or commented-out Linux PowerShell examples, and the overall structure often presents Windows tools and workflows before or instead of their Linux equivalents.
Recommendations
- Ensure parity by providing explicit Linux/macOS shell examples wherever Windows/PowerShell commands are given, especially for tasks like zipping files and navigating directories.
- In PowerShell sections, include working Linux-compatible PowerShell or Bash alternatives, or clearly link to the equivalent Linux instructions.
- Avoid language that recommends Windows tools (e.g., 'We recommend Azure PowerShell for creating apps on the Windows hosting platform') without offering equal guidance for Linux users.
- Where possible, use cross-platform tools (like Azure CLI and .NET CLI) as the primary examples, or present them before Windows-specific tools.
- Uncomment and complete the Linux PowerShell example, or provide a Bash/zsh example for Linux users.
- Review screenshots and instructions to ensure they are not exclusively Windows-centric, and provide Linux/macOS visuals or notes where appropriate.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/application-gateway/application-gateway-websocket.md
...s/application-gateway/application-gateway-websocket.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Azure PowerShell and linking to a PowerShell-based quickstart as the next step, without mentioning or providing equivalent instructions for Linux users (such as Azure CLI or ARM templates). There are no Linux-specific examples or references to cross-platform tools, and the only workflow described for getting started is via PowerShell, which is most commonly associated with Windows environments.
Recommendations
- Include Azure CLI examples alongside or instead of PowerShell examples, as Azure CLI is cross-platform and widely used on Linux.
- Provide links to quickstart guides for both PowerShell and Azure CLI/ARM templates, allowing users to choose their preferred environment.
- Explicitly mention that configuration can be performed from any OS using the Azure Portal, Azure CLI, or ARM templates, not just PowerShell.
- Where PowerShell is referenced, add a parallel note or example for Azure CLI to ensure Linux parity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/tutorial-connect-app-access-sql-database-as-user-dotnet.md
...utorial-connect-app-access-sql-database-as-user-dotnet.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation demonstrates a bias toward Windows environments by exclusively referencing Windows-centric development tools (Visual Studio, SSMS), providing only Windows/PowerShell examples for package management, and omitting Linux-specific guidance or alternatives for key steps such as publishing, database management, and local debugging. There are no examples or instructions tailored for Linux users, and Windows tools are mentioned before or instead of cross-platform or Linux-native options.
Recommendations
- Provide Linux and cross-platform alternatives for all steps involving Visual Studio (e.g., use of Visual Studio Code, dotnet CLI for publishing).
- Include examples for connecting to SQL Database using Linux-native tools (e.g., sqlcmd on Linux, Azure Data Studio) and clarify how to install and use them.
- Offer package management instructions using dotnet CLI (e.g., 'dotnet add package') alongside or instead of PowerShell/Visual Studio Package Manager Console.
- Add explicit notes or sections for Linux/macOS users, especially for local debugging and authentication scenarios.
- Ensure screenshots and walkthroughs are not exclusively tied to Windows UI; include CLI or cross-platform alternatives where possible.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dev-box/how-to-configure-azure-compute-gallery.md
...cles/dev-box/how-to-configure-azure-compute-gallery.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page exhibits a strong Windows bias. All example images are Windows-based (Visual Studio 2019/2022), and the image requirements section only references Windows OS versions. All configuration and optimization steps (e.g., sysprep, DISM, enabling features, defrag/chkdsk) are Windows-specific, with PowerShell and Windows command-line tools used exclusively. There is no mention of Linux images, Linux-compatible steps, or cross-platform considerations. The documentation assumes the user is working with Windows VMs and tools, omitting Linux equivalents or guidance.
Recommendations
- Add explicit guidance for using Linux images in Azure Compute Gallery, including supported distributions and any specific requirements or limitations for Dev Box.
- Provide Linux-based examples alongside Windows examples, such as creating and generalizing a Linux VM image (e.g., using waagent for deprovisioning).
- Include Linux command-line equivalents for steps like enabling features, optimizing images, and verifying settings (e.g., using Azure CLI or SSH).
- Clarify whether Dev Box supports Linux images, and if not, state this limitation clearly at the top of the documentation.
- If Linux is not supported, provide a roadmap or reasoning for Windows-only support to set expectations for cross-platform users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/application-gateway/application-gateway-probe-overview.md
...lication-gateway/application-gateway-probe-overview.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-based examples and cmdlets (e.g., New-AzApplicationGatewayProbeHealthResponseMatch), referencing Azure PowerShell for configuration, and omitting equivalent Azure CLI (cross-platform) or ARM template examples. The 'Next steps' section also lists PowerShell before the Azure portal, with no mention of Linux-friendly tools or workflows. There are no Linux/Unix command-line examples or references to Bash/CLI usage, and Windows-centric tools are mentioned exclusively.
Recommendations
- Add equivalent Azure CLI (az network application-gateway probe ...) examples alongside or before PowerShell examples to ensure cross-platform parity.
- Include ARM/Bicep template snippets for users who prefer declarative infrastructure-as-code approaches.
- In 'Next steps', mention Azure CLI and ARM/Bicep options, not just PowerShell and the portal.
- Wherever a PowerShell cmdlet is referenced, provide the corresponding Azure CLI command.
- Avoid using only Windows-centric terminology (e.g., 'cmdlet') without also referencing cross-platform alternatives.
- Consider including Bash shell examples or notes for Linux users where relevant.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dev-box/how-to-connect-devices-to-dev-box.md
.../articles/dev-box/how-to-connect-devices-to-dev-box.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation exclusively describes steps and tools for Windows environments, such as Device Manager, Local Group Policy Editor, and Windows command-line utilities (cmd, gpedit.msc, gpupdate /force). There are no instructions, examples, or references for performing these tasks on Linux or macOS systems, nor are cross-platform alternatives mentioned. This creates a strong Windows bias and leaves Linux users without guidance.
Recommendations
- Add equivalent instructions for Linux (and optionally macOS) environments, including how to check device connections (e.g., using lsusb, adb devices), manage drivers, and configure USB redirection (e.g., with SPICE, USB/IP, or RDP alternatives).
- Mention cross-platform tools and workflows, such as using adb directly on Linux, and provide troubleshooting steps for common Linux issues.
- If certain features (like Group Policy) are Windows-only, clearly state this and suggest alternative approaches for Linux users.
- Reorganize the documentation to present platform-agnostic steps first, or provide parallel sections for Windows and Linux/macOS users.
- Include links to official Android documentation for Linux USB driver setup and device troubleshooting.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/application-gateway/create-ssl-portal.md
...ain//articles/application-gateway/create-ssl-portal.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits a strong Windows bias. All command-line examples for certificate creation and backend server setup use Windows PowerShell and Windows-specific tools (e.g., New-SelfSignedCertificate, Export-PfxCertificate, Set-AzVMExtension with Windows commands). The tutorial instructs users to create Windows Server VMs and install IIS, with no mention or example of Linux alternatives (such as using OpenSSL for certificates or deploying Linux VMs with Apache/Nginx). Linux tools and workflows are entirely absent, and Windows approaches are presented as the default and only method.
Recommendations
- Provide equivalent Linux examples for creating self-signed certificates (e.g., using OpenSSL) and exporting PFX files.
- Include instructions for deploying Linux-based backend VMs (e.g., Ubuntu Server) and installing a web server such as Apache or Nginx.
- Show how to use Azure CLI or Bash in Cloud Shell for steps that are currently PowerShell-only.
- Mention both Windows and Linux options in all relevant sections, and avoid presenting Windows as the only or default platform.
- Add notes or links to cross-platform documentation where appropriate.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/application-gateway/application-gateway-externally-managed-scheduled-autoscaling.md
...ation-gateway-externally-managed-scheduled-autoscaling.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation exclusively provides PowerShell runbook examples and instructions, which are native to Windows environments. There is no mention of Bash, Python, or other cross-platform scripting options for Azure Automation, nor are there CLI examples or guidance for Linux users. This creates a Windows-centric bias and may hinder Linux administrators from easily following or adapting the instructions.
Recommendations
- Provide equivalent Azure CLI and/or Bash script examples for creating and managing runbooks, as Azure Automation supports Python and Bash runbooks as well.
- Mention and link to documentation on using Python or Bash runbooks in Azure Automation for Linux users.
- Rephrase steps to refer to 'runbooks' generically, and only specify PowerShell as one option among several.
- Include a note or section on cross-platform support, clarifying that Azure Automation is not limited to PowerShell and Windows environments.
- Where possible, show both PowerShell and CLI/Bash/Python code snippets side by side for parity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/webjobs-sdk-get-started.md
.../main//articles/app-service/webjobs-sdk-get-started.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 and Visual Studio users. All command-line examples use PowerShell syntax and the Visual Studio Package Manager Console, which are Windows-specific. There are no instructions or examples for Linux or cross-platform development environments (such as VS Code, .NET CLI, or terminal-based workflows). The tutorial assumes the use of Visual Studio's GUI for project creation, package management, and deployment, with no mention of equivalent Linux tools or workflows. This creates a significant barrier for Linux or macOS users wishing to follow the tutorial.
Recommendations
- Provide .NET CLI (dotnet new, dotnet add package, dotnet run, dotnet publish) equivalents for all Visual Studio and PowerShell/Package Manager Console commands.
- Include instructions for setting up and running the project on Linux and macOS, using cross-platform editors like VS Code or JetBrains Rider.
- Mention and demonstrate how to install and use the Azure CLI for resource creation and management, instead of relying solely on the Azure Portal GUI.
- Add notes or sections clarifying which steps are Windows-specific and provide alternatives for non-Windows users.
- Ensure screenshots and UI references are supplemented with command-line alternatives where possible.
- Explicitly state that the tutorial can be followed on Linux/macOS and provide links to relevant setup guides.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dev-box/how-to-configure-customization-tasks.md
...ticles/dev-box/how-to-configure-customization-tasks.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, with exclusive use of PowerShell scripts and WinGet (a Windows package manager) for task automation. There are no examples or mentions of Linux-compatible scripting (such as Bash or shell scripts), nor are cross-platform tools or patterns discussed. The documentation assumes a Windows-first approach, which may exclude or confuse users working in Linux or cross-platform scenarios.
Recommendations
- Include examples of tasks using Bash or shell scripts alongside PowerShell, and clarify when each is appropriate.
- Mention and provide examples for Linux-compatible package managers (e.g., apt, yum) and scripting environments.
- Explicitly state the platform requirements and limitations for Dev Box customizations, and clarify if Linux-based Dev Boxes are supported.
- If Dev Box is Windows-only, make this clear early in the documentation; if cross-platform support is planned or available, provide parity in examples and tooling.
- Reference cross-platform tools (such as Git, Python, or Node.js) in examples, and show how to automate their installation/configuration on both Windows and Linux.