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 126-150 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/includes/deploy-github-actions/deploy-github-actions-publish-profile.md
...ithub-actions/deploy-github-actions-publish-profile.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation provides cross-platform deployment examples for most stacks, but the ASP.NET (non-Core) section exclusively uses Windows runners and Windows-specific tools (NuGet, MSBuild) without offering Linux alternatives or parity. This creates a Windows-first impression for ASP.NET, and omits Linux-based guidance for that scenario.
Recommendations
- Provide a Linux-based example for ASP.NET (non-Core) deployment, using Mono or .NET SDK on Linux if feasible.
- Explicitly mention platform constraints for ASP.NET (non-Core) and clarify if Windows is required, or provide guidance for cross-platform alternatives.
- For all stacks, ensure that both Windows and Linux runner options are shown where possible, or explain why only one is supported.
- Consider reordering or grouping examples so that Linux and Windows options are presented together, rather than defaulting to Windows for legacy stacks.
- Add notes about tool availability (e.g., MSBuild, NuGet) on Linux and how to install or use them if supported.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/deploy-azure-pipelines.md
...b/main//articles/app-service/deploy-azure-pipelines.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias in several ways: examples and templates are predominantly focused on ASP.NET and .NET (traditionally Windows-centric stacks), Web Deploy (a Windows-only deployment method) is highlighted with explicit instructions and troubleshooting for Windows agents, and there is a lack of equivalent Linux-focused deployment examples or troubleshooting. In sections where OS-specific behavior matters (e.g., Web Deploy), Windows is presented as the default or only supported environment, with no Linux alternatives or parity guidance.
Recommendations
- Provide equivalent Linux examples and troubleshooting for deployment scenarios, especially where Windows-only tools (like Web Deploy) are discussed.
- Include more examples for non-Windows stacks (e.g., Node.js, Java, Python) and clarify when steps or tools are OS-agnostic.
- When mentioning Windows-specific deployment methods, explicitly state the lack of Linux support and suggest alternative approaches for Linux agents (such as using ZIP deploy or FTP).
- Balance the order of presentation so that Linux and cross-platform options are mentioned alongside or before Windows-specific ones.
- Add troubleshooting sections for common Linux agent deployment issues, not just Windows/Web Deploy problems.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/environment/overview-certificates.md
...icles/app-service/environment/overview-certificates.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 creation and management, referencing Windows-specific certificate stores and tools, and explicitly stating that certain features (private client certificates) are only supported in Windows code apps. There are no equivalent Linux or cross-platform instructions or examples, and the use of Windows-centric terminology (e.g., Cert:\LocalMachine\Root) further excludes Linux users.
Recommendations
- Provide equivalent Linux examples for certificate creation (e.g., using OpenSSL) and management.
- Include instructions for accessing and managing certificates on Linux-based App Service apps, or clarify platform limitations.
- Use cross-platform terminology and tools where possible, or clearly separate instructions for Windows and Linux scenarios.
- Explicitly state platform support at the beginning of relevant sections to set user expectations.
- Offer Bash or CLI alternatives to PowerShell commands for parity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/deploy-intelligent-apps-dotnet-to-azure-sql.md
...service/deploy-intelligent-apps-dotnet-to-azure-sql.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific UI actions (such as 'Right click' to add files), omitting explicit Linux or cross-platform command-line instructions for key steps (like file creation or package installation), and mentioning tools like Azure Data Studio and SQL query editors without clarifying their cross-platform availability or suggesting Linux-native alternatives. There are no PowerShell-specific commands, but the overall workflow assumes a Windows GUI environment and does not provide parity for Linux users.
Recommendations
- For every step that references Windows UI actions (e.g., 'Right click'), provide equivalent command-line instructions (e.g., 'Use `touch OpenAI.razor` in the terminal') and clarify that these steps can be performed on Linux and macOS as well.
- Explicitly mention that tools like Azure Data Studio are cross-platform, and provide installation links or alternatives for Linux users (such as using Azure CLI, VS Code with SQL extensions, or sqlcmd).
- When referencing connection string setup or secret management, include CLI-based examples (using Azure CLI or environment variables) that work on Linux.
- For package installation, show both Visual Studio UI and .NET CLI (`dotnet add package ...`) methods.
- Add a section or callouts confirming that all code and deployment steps are cross-platform, and provide troubleshooting tips for Linux environments.
- If any screenshots or UI walkthroughs are included elsewhere, ensure Linux and macOS variants are shown or referenced.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/configure-language-java-data-sources.md
...es/app-service/configure-language-java-data-sources.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides both Linux and Windows instructions for advanced Tomcat configuration, but the Windows section is notably more detailed and relies heavily on PowerShell scripts and Windows-specific patterns (e.g., .cmd, %ENVVAR% notation, Windows paths). The Linux section uses shell scripts and standard Linux tools, but the Windows instructions are longer, more explicit, and introduce more custom scripting. Windows tools and patterns (PowerShell, .cmd, Windows environment variables) are described in detail, while Linux equivalents are less emphasized. The order of presentation sometimes puts Windows instructions before Linux, and the Windows section is more verbose.
Recommendations
- Ensure parity in detail and clarity between Linux and Windows sections. Expand Linux instructions to match the step-by-step guidance given for Windows, including troubleshooting tips and explanations.
- Where possible, provide cross-platform script examples (e.g., both Bash and PowerShell) side by side, or use neutral tools (like Azure CLI) as the primary example.
- Avoid assuming PowerShell or Windows scripting as the default; for each Windows-specific tool or pattern, provide a Linux equivalent (e.g., Bash script for startup, Linux environment variable syntax).
- Present Linux and Windows instructions in parallel or in a consistent order, rather than giving more prominence or detail to Windows.
- Review for any missing Linux-specific troubleshooting, caveats, or best practices that are present for Windows.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/deploy-local-git.md
...cs/blob/main//articles/app-service/deploy-local-git.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions, but PowerShell is given a dedicated section with detailed steps, and references to 'local PowerShell terminal' are made without equivalent explicit references to Linux shells. The troubleshooting section includes error messages and resolutions that mention Windows-specific issues (e.g., native modules lacking Windows binaries). There is no explicit mention or example of using Linux or macOS terminals, and no Bash-specific instructions for creating or configuring the web app, despite Bash being referenced only in the context of cloning the sample repository. The documentation assumes familiarity with PowerShell and Windows tools, and does not offer parity for Linux users in terms of terminal usage or troubleshooting.
Recommendations
- Add explicit Bash/Linux/macOS terminal instructions alongside PowerShell, especially in sections that currently only mention 'local PowerShell terminal'.
- In the troubleshooting section, include Linux/macOS-specific error messages and resolutions, particularly for issues like native module builds and authentication dialogs.
- When referencing tools or commands, avoid assuming PowerShell as the default; instead, provide parallel instructions for Bash or other common Linux shells.
- Ensure that screenshots and UI references are OS-agnostic or provide alternatives for Linux/macOS users.
- In the prerequisites and throughout the guide, clarify that all steps can be performed on Linux/macOS, and provide any OS-specific caveats or tips.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/includes/quickstart-python/remove-resource-group-visual-studio-code-2.md
...t-python/remove-resource-group-visual-studio-code-2.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation describes deleting a resource group using a right-click context menu, which is a GUI pattern most commonly associated with Windows environments. There are no examples or instructions for performing the same action using Linux tools, command-line interfaces, or cross-platform methods.
Recommendations
- Add instructions for deleting a resource group using the Azure CLI, which works on both Windows and Linux.
- Include examples for performing the deletion via terminal/command line, not just through GUI interactions.
- If a GUI is required, clarify if the instructions apply to cross-platform tools (e.g., Azure Portal in a browser) rather than Windows-specific applications.
- Present Linux or cross-platform methods alongside or before Windows-specific instructions to ensure parity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/deployment-environments/how-to-create-configure-projects.md
...yment-environments/how-to-create-configure-projects.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by using PowerShell-style variable assignment (e.g., $VAR = ...) and line continuation (backtick `), which are not compatible with Linux/macOS shells. All CLI examples assume a Windows/PowerShell environment, with no equivalent Bash or cross-platform examples provided. This may confuse or hinder Linux/macOS users attempting to follow the guide.
Recommendations
- Provide parallel Bash (Linux/macOS) examples for all CLI commands, using appropriate syntax (e.g., VAR=..., line continuation with \).
- Clearly indicate which examples are for PowerShell/Windows and which are for Bash/Linux/macOS.
- Consider using cross-platform compatible syntax where possible, or at least link to a section explaining the differences.
- Add a note at the top of the page clarifying the shell environment assumed, and direct users to the appropriate examples for their OS.
- Avoid using Windows-specific command constructs (like Write-Output, backtick for line continuation) without Linux equivalents.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/scripts/powershell-connect-to-sql.md
...icles/app-service/scripts/powershell-connect-to-sql.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively uses PowerShell for all examples, explanations, and cleanup steps, with no mention of Linux, Bash, or cross-platform CLI alternatives. All tooling and guidance are centered on Azure PowerShell, which is most familiar to Windows users. There are no Linux shell or Azure CLI examples, and no guidance for non-Windows environments.
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 demonstrate Linux compatibility.
- Mention that Azure PowerShell is available cross-platform, but clarify when to use Azure CLI vs PowerShell.
- Structure the documentation so that both Windows (PowerShell) and Linux (Bash/Azure CLI) users can follow along with parity.
- Add a section or links for Linux/macOS users, including installation and usage instructions for relevant tools.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/application-gateway/create-url-route-portal.md
...rticles/application-gateway/create-url-route-portal.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a strong Windows bias. It exclusively uses Windows Server virtual machines as backend servers and only provides instructions and scripts for installing IIS via PowerShell. There are no examples or guidance for deploying Linux VMs, using Linux-native web servers (such as Apache or Nginx), or installing software via Linux command-line tools. All scripting and automation is shown with PowerShell, with no mention of Bash, Azure CLI, or Linux VM extensions.
Recommendations
- Provide parallel instructions for creating Linux virtual machines as backend servers, including recommended distributions (e.g., Ubuntu, CentOS).
- Include examples for installing a Linux web server (such as Apache or Nginx) using the Azure Custom Script Extension or cloud-init, with Bash or Azure CLI commands.
- Show how to verify the application gateway using Linux-based web servers, including sample index.html pages.
- Balance PowerShell examples with Azure CLI or Bash equivalents, especially for VM extension installation.
- Explicitly mention that both Windows and Linux VMs are supported as backend pools, and link to relevant Linux documentation.
- Consider reordering or parallelizing instructions so that Windows and Linux options are presented equally, rather than Windows-only or Windows-first.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dev-box/concept-dev-box-deployment-guide.md
...//articles/dev-box/concept-dev-box-deployment-guide.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation for Microsoft Dev Box deployment is heavily oriented toward Windows environments. It consistently references Windows-specific tools (such as Intune, Entra ID, and Windows device management), and all device management and customization examples are Windows-centric. There are no examples or guidance for Linux-based dev boxes, nor are Linux tools or patterns mentioned. The only customization tools referenced (WinGet, Chocolatey, PowerShell scripts) are Windows-specific. The documentation assumes all dev boxes are Windows VMs, with no mention of Linux VM images, Linux device management, or cross-platform developer scenarios.
Recommendations
- Explicitly mention support (or lack thereof) for Linux dev boxes, including any limitations.
- Provide parallel examples for Linux-based dev boxes, such as using Bash scripts, apt/yum package managers, or Linux VM images.
- Reference Linux-compatible configuration and management tools (e.g., Ansible, cloud-init, shell scripts) alongside Windows tools.
- Clarify whether Microsoft Intune and other device management features apply to Linux dev boxes, and if not, suggest alternatives.
- Include guidance for cross-platform development teams, highlighting how to configure and manage both Windows and Linux dev boxes.
- Ensure that any quick start catalogs or setup tasks include Linux-relevant examples (e.g., installing software with apt, running Bash scripts).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/includes/tutorial-microsoft-graph-as-app/introduction.md
...cludes/tutorial-microsoft-graph-as-app/introduction.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides detailed PowerShell instructions and references Visual Studio (a Windows-centric tool) for enabling managed identity, with PowerShell examples presented before Azure CLI. There is no mention of Linux-specific workflows, nor are there examples using Bash or Linux-native tools, which may disadvantage users on non-Windows platforms.
Recommendations
- Provide explicit Bash/Linux shell examples for all command-line instructions, especially for steps involving Azure CLI.
- Mention and demonstrate cross-platform editors and deployment tools (such as VS Code, Azure CLI, or GitHub Actions) alongside or instead of Visual Studio.
- Ensure that all code snippets and instructions are tested and presented in a way that is platform-agnostic, or clearly indicate when a step is Windows-specific.
- Consider reordering examples to present Azure CLI or Bash first, as these are cross-platform, before PowerShell.
- Add a note clarifying that all steps can be performed on Linux, macOS, or Windows, and provide links to relevant setup guides for each OS.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/application-gateway/application-gateway-autoscaling-zone-redundant.md
...eway/application-gateway-autoscaling-zone-redundant.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates a Windows bias by providing a 'Next steps' link specifically to a tutorial using Azure PowerShell, which is primarily a Windows-centric tool. There are no equivalent examples or links for Linux users (such as Azure CLI or ARM templates), and PowerShell is mentioned before any cross-platform alternatives, reinforcing a Windows-first approach.
Recommendations
- Add parallel tutorials and links for Linux users, such as 'Create an autoscaling, zone redundant application gateway using Azure CLI' and/or ARM/Bicep templates.
- In 'Next steps', present cross-platform options (Azure CLI, ARM templates) before or alongside PowerShell to avoid Windows-first ordering.
- Explicitly mention that PowerShell is available cross-platform, but also provide native Linux-friendly instructions.
- Audit the documentation for other sections where only Windows tools or patterns are referenced, and ensure Linux parity throughout.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/operating-system-functionality.md
...articles/app-service/operating-system-functionality.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily focused on Windows-based App Service environments, with all examples, environment variables, and tooling references (e.g., %SystemDrive%, IIS, ASP.NET, registry, COM components, Windows event logs) being Windows-specific. Linux is only mentioned briefly in a note, with no equivalent details, examples, or guidance for Linux-based App Service environments. There are no Linux environment variable examples, file system paths, or references to Linux-native tools or patterns.
Recommendations
- Add parallel sections or callouts describing Linux App Service behavior, including file system layout, environment variables (e.g., $HOME), and storage persistence.
- Provide Linux-specific examples for file access, such as using /home/site/wwwroot or $HOME/site.
- Explain the differences in diagnostic logging and event tracing for Linux (e.g., syslog, application logs) and how to access them.
- Clarify process and code execution capabilities for Linux apps, including shell access (bash/sh), and supported scripting languages.
- Describe the absence of a registry on Linux and what configuration mechanisms are available instead (e.g., environment variables, config files).
- Mention Linux-native tools and patterns (e.g., systemd, journald, Linux permissions) where relevant.
- Ensure that Linux guidance is not relegated to a single note, but is integrated throughout the documentation for parity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dev-box/concept-dev-box-network-requirements.md
...ticles/dev-box/concept-dev-box-network-requirements.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Powershell Heavy
Summary
The documentation demonstrates a Windows-centric bias throughout. It references Windows-specific services (Windows 365, Azure Virtual Desktop, Microsoft Intune), tools (Event Viewer, Group Policy), and troubleshooting steps that are only applicable to Windows environments. There are no Linux-specific instructions, examples, or troubleshooting guidance, and all endpoint and client references assume Windows clients. The documentation also refers to Windows activation endpoints and Windows Desktop clients without mentioning Linux or cross-platform alternatives.
Recommendations
- Include explicit guidance and examples for Linux clients connecting to Dev Box, such as supported RDP clients (e.g., FreeRDP, Remmina) and their network requirements.
- Provide troubleshooting steps for common Linux client issues (e.g., authentication, certificate handling, group policy equivalents, if any).
- Mention cross-platform tools and alternatives where Windows-specific tools are referenced (e.g., suggest Linux log locations or tools instead of only Event Viewer).
- Clarify which features and requirements apply to non-Windows clients and environments, and note any limitations or differences.
- Add references to Linux documentation for remote desktop connectivity, DNS configuration, and firewall rules.
- Balance the order of presentation so that Linux and cross-platform scenarios are not always secondary to Windows.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/includes/webjobs-create/webjob-types.md
...es/app-service/includes/webjobs-create/webjob-types.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing Windows file types and tools (cmd, bat, exe, PowerShell) first and in greater detail, while Linux support is described more generically and with fewer examples. Windows-specific tools and patterns are explicitly mentioned, whereas Linux equivalents (such as Python or Bash) are only briefly referenced, and some common Linux script types (e.g., Python, Perl, Ruby) are not listed alongside their Windows counterparts. The examples for Linux are less comprehensive and less prominent.
Recommendations
- Provide a parallel, detailed list of supported file types for Linux, including common script types such as *.py* (Python), *.pl* (Perl), *.rb* (Ruby), and *.js* (Node.js), not just *.sh*.
- Include Linux-specific examples in the same level of detail as Windows (e.g., show how to use Bash, Python, Node.js, and Java on Linux).
- Avoid listing Windows tools and runtimes first; instead, present Windows and Linux sections with equal prominence and structure.
- Where PowerShell is mentioned for Windows, consider mentioning Bash or other Linux scripting languages for Linux.
- Clarify that the necessary runtimes are also installed for Linux, mirroring the statement made for Windows.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/overview-diagnostics.md
...lob/main//articles/app-service/overview-diagnostics.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-specific features and tools, such as proactive CPU monitoring, proactive auto-healing, and Navigator, which are marked as 'Windows apps only' without Linux equivalents or alternatives. Several advanced diagnostic features are described exclusively for Windows, and Linux support is only mentioned in passing or as a secondary consideration. There are no concrete Linux-specific troubleshooting examples or guidance, and Linux diagnostic capabilities are not explained in equal detail.
Recommendations
- Provide Linux-specific examples and walkthroughs for diagnostics, including screenshots and step-by-step instructions.
- Clearly indicate feature parity or gaps for each diagnostic tool, and offer alternative solutions or workarounds for Linux users where features are Windows-only.
- Include Linux-first or at least Linux-equal sections, especially for advanced diagnostics, to ensure that Linux users are not left out.
- Expand on Linux-specific diagnostic categories (e.g., 'Linux - Number of Running Containers', 'Linux Swap Space Low') with detailed explanations and troubleshooting steps.
- Where a feature is Windows-only, suggest open-source or Azure-native alternatives for Linux, or provide a roadmap for Linux support.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/monitor-instances-health-check.md
...articles/app-service/monitor-instances-health-check.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Several features and tools are described as available only for Windows applications (e.g., Process Explorer, diagnostic information collection with memory dumps). These Windows-specific features are mentioned without Linux equivalents or alternatives. Additionally, in sections discussing features available on both Windows and Linux, Windows is often mentioned first or exclusively, and there are no Linux-specific examples or guidance for comparable tasks.
Recommendations
- Where features are Windows-only (e.g., Process Explorer, diagnostic memory dumps), explicitly state their unavailability on Linux and, if possible, suggest Linux alternatives or workarounds (such as using SSH, Kudu, or custom scripts for diagnostics on Linux).
- Add Linux-specific instructions or screenshots for monitoring, diagnostics, and instance management, or clarify when features are not available on Linux.
- In sections discussing both Windows and Linux, avoid always listing Windows first; instead, present both platforms equally or clarify platform-specific differences in parallel.
- For authentication and security, clarify if the x-ms-auth-internal-token header or related features are available on Linux, and provide Linux-specific guidance if needed.
- Include explicit examples or notes for Linux users where behavior or UI differs, especially in portal screenshots or step-by-step instructions.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/application-gateway/tutorial-protect-application-gateway-ddos.md
...n-gateway/tutorial-protect-application-gateway-ddos.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 and providing only PowerShell-based instructions for configuration (e.g., installing IIS). There are no Linux VM examples, nor are there Bash/Cloud Shell or Linux-native command alternatives. The use of Windows-specific tools (IIS, Add-WindowsFeature) and the absence of Linux equivalents further reinforce this bias.
Recommendations
- Include parallel instructions for creating and configuring Linux virtual machines (e.g., Ubuntu) as backend servers.
- Provide Bash/Azure CLI examples for installing a web server (such as Apache or Nginx) on Linux VMs, alongside the PowerShell/IIS steps.
- Mention both Windows and Linux options when describing backend pool targets, making it clear that either OS is supported.
- Where PowerShell is used, offer equivalent Azure CLI/Bash commands for cross-platform parity.
- Add screenshots or code snippets that demonstrate the Linux workflow, not just Windows.
- Explicitly state that both Windows and Linux VMs are supported as backend targets and provide links to relevant documentation for both.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dev-box/dev-box-roadmap.md
...re-docs/blob/main//articles/dev-box/dev-box-roadmap.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page for Microsoft Dev Box exhibits a Windows-centric bias. It references PowerShell and Winget as primary customization primitives, and mentions RDP and Windows as core parts of the developer experience. There are no explicit examples or mentions of Linux-based workflows, tools, or equivalents (e.g., Bash scripting, Linux package managers, or Linux-first developer environments). While WSL is briefly mentioned, it is only as a feature accessible from a Dev Box, not as a first-class environment or workflow. The documentation assumes Windows as the default platform for both administration and development.
Recommendations
- Provide parallel examples for Linux-based workflows, such as using Bash scripts or Linux package managers (e.g., apt, yum) for customization.
- Mention Linux-native tools and scripting options alongside PowerShell and Winget, and clarify if/when they are supported.
- Include explicit references to Linux-first developer environments and how Dev Box supports them, not just WSL as a Windows feature.
- Balance the documentation by listing Linux options before or alongside Windows options where applicable.
- Clarify the cross-platform capabilities of Dev Box, including any limitations or best practices for Linux users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/application-gateway/application-gateway-troubleshooting-502.md
...ion-gateway/application-gateway-troubleshooting-502.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 providing only Azure PowerShell (Windows-centric) command examples for troubleshooting, referencing Windows tools and patterns (such as IIS and PowerShell cmdlets), and omitting equivalent Azure CLI (cross-platform) or Bash/Linux command examples. There are no Linux-specific troubleshooting steps or examples, and Windows terminology and tools are mentioned exclusively or before any cross-platform alternatives.
Recommendations
- Add Azure CLI (az) command examples alongside PowerShell for all troubleshooting steps, ensuring parity for Linux and macOS users.
- Include Bash shell command examples where appropriate, especially for network and DNS troubleshooting.
- Reference both Windows (IIS) and Linux (Apache/Nginx) web server scenarios in health probe and SSL certificate troubleshooting sections.
- Explicitly mention that all steps can be performed from Linux/macOS using Azure CLI or portal, and provide links to relevant documentation.
- Avoid using Windows-specific terminology or tools exclusively; always provide cross-platform alternatives.
- Where JSON output is shown from PowerShell, show equivalent output from Azure CLI (az network vnet show, etc.).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/overview-local-cache.md
...lob/main//articles/app-service/overview-local-cache.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits a Windows-first bias: all file paths and folder references use Windows-style paths (e.g., D:\home), and there are no Linux-specific examples or equivalents. The documentation references Windows containers before Linux containers and does not provide parity in examples or instructions for Linux-based App Service environments. Additionally, tools and folder structures mentioned (such as Kudu and Azure Web Apps Disk Usage) are described in a way that assumes a Windows environment.
Recommendations
- Include Linux-specific examples and file paths (e.g., /home/site) alongside Windows paths.
- Clarify differences in local cache behavior, folder structure, and environment variables for Linux-based App Service plans.
- Provide instructions and screenshots for enabling and managing local cache on Linux App Service environments.
- List Linux containers before or alongside Windows containers when discussing unsupported scenarios.
- Mention any Linux-specific tools or equivalents to Kudu and Azure Web Apps Disk Usage, or clarify their availability on Linux.
- Add a section or callout explicitly addressing Linux users, summarizing key differences and limitations.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/invoke-openapi-web-app-from-azure-ai-agent-service.md
...https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/invoke-openapi-web-app-from-azure-ai-agent-service.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation demonstrates a bias toward Windows environments and tooling. It exclusively references Azure App Service (which is often associated with Windows hosting, though it does support Linux), .NET/Blazor (primarily Microsoft/Windows-centric technologies), and Azure CLI tools without mentioning Linux-specific workflows, deployment patterns, or alternative environments. There are no examples or notes about running, deploying, or troubleshooting on Linux-based App Service plans, nor is there any mention of Linux shell differences or cross-platform considerations. The documentation assumes the use of the Azure Portal and Azure CLI, both of which are available on Linux, but does not clarify or provide parity for Linux users.
Recommendations
- Explicitly mention that Azure App Service supports both Windows and Linux plans, and clarify which is being used in the tutorial.
- Provide examples or notes for deploying to both Windows and Linux App Service environments, including any differences in configuration or troubleshooting.
- Include Linux shell-specific notes or commands where relevant (e.g., environment variable setting, file path conventions).
- Highlight any .NET/Blazor cross-platform capabilities and, if possible, provide alternative examples for non-Windows stacks (such as Node.js or Python) to broaden applicability.
- Add troubleshooting steps or links specific to Linux App Service plans, such as log file locations or diagnostic tools.
- Clarify that Azure CLI and azd commands work on Linux, macOS, and Windows, and note any OS-specific caveats.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/overview-patch-os-runtime.md
...ain//articles/app-service/overview-patch-os-runtime.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by focusing on Windows-specific tools, examples, and terminology. All runtime and OS version query examples are given for Windows-based App Service environments, with references to Windows registry, Windows-specific files (web.config), and no mention of Linux-based App Service equivalents. There are no Linux shell or file examples, and the guidance assumes a Windows environment throughout.
Recommendations
- Add parallel examples and instructions for Linux-based App Service environments, including how to check OS and runtime versions using Linux shell commands.
- Include Linux-specific configuration file references (e.g., appsettings.json, environment variables) alongside Windows examples like web.config.
- Clarify in each section whether the instructions apply to Windows, Linux, or both, and provide links to Linux-specific documentation where appropriate.
- Provide guidance on using Kudu/SSH for Linux App Service instances, including relevant commands and file paths.
- Avoid referencing Windows registry or Windows-only tools without offering Linux alternatives.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/scenario-secure-app-access-microsoft-graph-as-user.md
...https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/scenario-secure-app-access-microsoft-graph-as-user.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by presenting Visual Studio (a Windows-centric IDE) and its Package Manager Console (PowerShell-based) as the primary GUI tooling and command-line example, with no mention of Linux or cross-platform alternatives. The .NET CLI example is present, but the Package Manager Console (PowerShell) example is given equal or greater prominence, and there are no explicit instructions for Linux users regarding equivalent tooling or workflows.
Recommendations
- Clearly indicate that the Package Manager Console is a Windows/Visual Studio feature, and suggest alternatives for Linux users (e.g., using the .NET CLI exclusively).
- Present the .NET CLI example before the Package Manager Console example to emphasize cross-platform compatibility.
- Add explicit notes or sections for Linux/macOS users, including how to install the required packages using the .NET CLI and how to open a terminal.
- Avoid referencing Windows-specific tools (like Visual Studio's Package Manager Console) without providing Linux/macOS equivalents or clarifications.
- Consider including a table or callout summarizing installation commands for Windows, Linux, and macOS environments.