Azure App Configuration
166
Total Pages
109
Linux-Friendly Pages
57
Pages with Bias
34.3%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
479 issues found
Showing 201-225 of 479 flagged pages
Azure App Configuration
Quickstart for using Azure App Configuration with JavaScript apps
...re-app-configuration/quickstart-javascript-provider.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation demonstrates a subtle Windows bias in the 'Run the application' section, where Windows command prompt and PowerShell instructions are presented before Linux/macOS equivalents. Additionally, Windows-specific tools (setx, PowerShell) are mentioned explicitly, while Linux/macOS only gets a generic 'export' command. The Node.js installation prerequisite links to a Windows-centric page and mentions Windows and WSL before Linux, further reinforcing a Windows-first approach.
Recommendations
- Present platform instructions in parallel tabs or in an order that does not prioritize Windows (e.g., alphabetical: Linux/macOS, PowerShell, Windows CMD).
- Provide equal detail for Linux/macOS, including links to official installation guides and troubleshooting steps.
- Avoid language that implies Windows is the default or primary platform; instead, use neutral phrasing.
- Where possible, use cross-platform commands or clarify platform-specific differences in a balanced way.
- Explicitly mention that all examples work on Linux/macOS unless there are platform-specific caveats.
Create Pull Request
Azure App Configuration
Quickstart for using Azure App Configuration with Python apps | Microsoft Learn
.../azure-app-configuration/quickstart-python-provider.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias in the 'Prerequisites' and 'Run the application' sections. Windows-specific instructions (Windows command prompt and PowerShell) are listed before Linux/macOS equivalents, and the only OS-specific setup link provided is for Windows. However, Linux/macOS instructions are present and correct, and most code samples are OS-agnostic.
Recommendations
- Add links or references for setting up Python on Linux/macOS alongside the Windows documentation link in the prerequisites.
- Present OS instructions in a neutral order (e.g., alphabetical or grouped together), or use tabs for each OS to avoid implicit prioritization.
- Ensure parity in troubleshooting and environment setup guidance for Linux/macOS users.
- Consider mentioning cross-platform editors or tools (e.g., VS Code) if any are referenced for Windows.
Azure App Configuration
Using Azure App Configuration in Python apps with the Azure SDK for Python
.../articles/azure-app-configuration/quickstart-python.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation demonstrates mild Windows bias in the prerequisites and environment variable setup sections. Specifically, the link for Python installation refers only to Windows documentation, and instructions for setting environment variables list Windows command prompt and PowerShell methods before macOS/Linux equivalents. Windows-specific tools (setx, PowerShell) are mentioned explicitly, while Linux/macOS instructions are provided but appear after Windows options.
Recommendations
- In the prerequisites, provide links for setting up Python on Linux and macOS alongside the Windows link.
- When listing environment variable setup commands, present all platforms equally (e.g., group Windows, macOS, and Linux together or alternate the order in different sections).
- Explicitly mention that the instructions apply to all major platforms and ensure parity in detail and order.
- Consider adding a table or tabbed interface for environment variable setup, so users can easily find instructions for their OS without implicit prioritization.
- Review other sections for similar ordering or tool bias and adjust to ensure cross-platform parity.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/configuration-provider-overview.md
...e-app-configuration/configuration-provider-overview.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows/.NET bias by listing .NET-based providers first and providing sample links that are primarily for .NET Core and .NET Framework, which are historically Windows-centric. There are no explicit Linux or cross-platform command-line examples, and no mention of Linux-specific tools or patterns. The documentation does not provide parity in terms of Linux usage scenarios or examples, nor does it mention Linux-first frameworks or configuration patterns.
Recommendations
- Include Linux-specific usage examples, such as configuration for applications running on Linux distributions.
- Provide sample links and walkthroughs for Linux environments (e.g., using bash, systemd, or Linux-native deployment scenarios).
- Add references to cross-platform .NET Core usage on Linux, and clarify platform compatibility for each provider.
- Mention Linux-native configuration management tools (such as environment variables, config files in /etc, etc.) and how Azure App Configuration integrates with them.
- Reorder the provider list or provide a platform-neutral introduction to avoid the perception of Windows/.NET primacy.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/how-to-targeting-filter-python.md
...re-app-configuration/how-to-targeting-filter-python.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation demonstrates a Windows bias in the section on setting environment variables: Windows Command Prompt and PowerShell instructions are presented first and in detail, with Linux/macOS instructions given last. The use of PowerShell is explicitly highlighted, and Windows-specific commands (setx) are described before their Linux equivalents (export). Other parts of the documentation are cross-platform and provide parity for Python development, but the environment variable setup section prioritizes Windows tools and patterns.
Recommendations
- Present environment variable instructions in a neutral or platform-rotating order (e.g., start with Linux/macOS, then Windows, then PowerShell).
- Use a table or side-by-side format for environment variable commands to avoid implicit prioritization.
- Explicitly state that all platforms are supported and provide equal detail for each.
- Consider mentioning cross-platform tools (e.g., direnv, dotenv) for environment management.
- Add a note that the Python code and application steps are platform-agnostic, reinforcing parity.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-feature-flag-spring-boot.md
...p-configuration/quickstart-feature-flag-spring-boot.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides environment variable setup instructions for Windows command prompt and PowerShell before mentioning Linux/macOS equivalents. Windows-specific tools (setx, PowerShell) are described in detail, with Linux/bash instructions given last. No Linux-specific tools or patterns are highlighted, and the overall order and emphasis favor Windows users.
Recommendations
- Present environment variable instructions for Linux/macOS first or in parallel with Windows examples.
- Include Linux-specific notes or troubleshooting tips, such as differences in environment variable persistence between shells.
- Mention cross-platform alternatives (e.g., using .env files, or Maven profiles) for environment configuration.
- Clarify that setx is Windows-only and provide equivalent persistent environment variable setup for Linux/macOS (e.g., editing ~/.bashrc or ~/.profile).
- Where possible, use generic commands or highlight platform differences equally.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-bicep.md
...n/articles/azure-app-configuration/quickstart-bicep.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment, resource review, and cleanup. However, PowerShell examples are given equal prominence to CLI, and PowerShell is a Windows-centric tool. There is no mention of Linux-specific shell patterns (e.g., Bash), nor are there any Linux-specific notes or troubleshooting tips. The ordering of examples sometimes places PowerShell before CLI, and the use of PowerShell tabs may suggest a Windows-first audience. No Linux-exclusive tools or patterns are referenced.
Recommendations
- Clearly indicate that Azure CLI commands work cross-platform (Windows, Linux, macOS) and are preferred for Linux users.
- Add explicit Bash shell examples or notes for Linux users, especially for file operations and environment setup.
- If PowerShell is mentioned, clarify that PowerShell Core is available on Linux, or provide links to installation instructions for Linux users.
- Ensure CLI examples are listed first, or provide a note about platform parity.
- Include troubleshooting tips or common issues for Linux environments (e.g., file permissions, path formats).
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-python-provider.md
.../azure-app-configuration/quickstart-python-provider.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias in the 'Prerequisites' and 'Run the application' sections. Windows-specific instructions (Windows command prompt and PowerShell) are listed before Linux/macOS equivalents, and the only OS-specific setup link provided is for Windows. However, Linux/macOS instructions are present and correct, and the main code samples are platform-agnostic.
Recommendations
- Include links or guidance for setting up Python on Linux/macOS in the prerequisites, not just Windows.
- Present OS-specific environment variable instructions in a neutral order (e.g., group by OS or list Linux/macOS first in some cases).
- Add a note clarifying that all steps work equally on Linux/macOS and Windows unless otherwise stated.
- Consider providing shell-agnostic environment variable setting instructions (e.g., using .env files or cross-platform tools) where possible.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-chat-completion-go.md
...ure-app-configuration/quickstart-chat-completion-go.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides environment variable setup instructions for Windows Command Prompt and PowerShell before mentioning the Linux/macOS equivalent. Windows-specific tools (setx, PowerShell) are described in detail, while Linux/macOS instructions are given last and more briefly. No Linux-specific tools or patterns are highlighted elsewhere, but the Go code itself is cross-platform.
Recommendations
- Present environment variable setup instructions for Linux/macOS first, or group all OS instructions together without prioritizing Windows.
- Provide equal detail for Linux/macOS commands (e.g., mention persistence of environment variables across sessions, as is done for Windows setx).
- Consider adding troubleshooting notes for Linux/macOS users (e.g., how to persist environment variables in .bashrc/.zshrc).
- Avoid Windows-centric phrasing such as 'If you use the Windows command prompt...' and instead use neutral language like 'To set the environment variable on your platform...'.
- Ensure parity in screenshots or portal instructions if applicable (none found in this page, but relevant for future updates).
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-go-console-app.md
...s/azure-app-configuration/quickstart-go-console-app.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias in the 'Run the application' section, where Windows command prompt and PowerShell instructions are presented before Linux/macOS equivalents. PowerShell and Windows command prompt commands are explicitly called out, while Linux/macOS instructions are grouped together and appear after Windows instructions. No Linux-specific tools or patterns are missing, and all major steps are covered for both platforms.
Recommendations
- Present platform instructions in parallel tabs or sections, giving equal prominence to Windows, Linux, and macOS.
- Avoid listing Windows command prompt and PowerShell instructions before Linux/macOS; instead, use a tabbed or side-by-side format.
- Explicitly mention that all platforms are supported and provide troubleshooting tips for Linux/macOS users if applicable.
- Consider adding screenshots or examples for Linux/macOS terminals, not just Windows.
- Ensure that any references to Azure CLI or other tools clarify cross-platform compatibility.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/azure-pipeline-export-task.md
.../azure-app-configuration/azure-pipeline-export-task.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Summary
The documentation provides only a PowerShell example for consuming exported key-values, with no equivalent example for Bash or other Linux shells. There is no mention of Linux-specific tools or patterns, nor any explicit guidance for Linux users. This may make the documentation less accessible for users running pipelines on Linux agents.
Recommendations
- Add Bash (and/or sh) examples for consuming environment variables, e.g., `echo "$myBuildSetting"`.
- Explicitly mention that the exported variables are available in all agent operating systems, including Linux and macOS.
- Include notes or examples for both PowerShell and Bash side-by-side when demonstrating environment variable usage.
- Review screenshots and UI instructions to ensure they are OS-agnostic or clarify any OS-specific differences.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/enable-dynamic-configuration-dotnet.md
...p-configuration/enable-dynamic-configuration-dotnet.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation demonstrates a Windows-first bias in several areas. Visual Studio is listed as the only development environment, and all project creation steps assume its use. Instructions for setting environment variables are presented with Windows Command Prompt and PowerShell examples before Linux/macOS equivalents. The build and run steps reference restarting Visual Studio and using Windows-specific shortcuts. There are no Linux-specific development environment recommendations or guidance for running .NET Framework apps on Linux (which is not natively supported).
Recommendations
- Add guidance for cross-platform development environments, such as JetBrains Rider or VS Code, and clarify .NET Framework's Windows-only support.
- Present environment variable instructions in a neutral order (e.g., Linux/macOS first, or side-by-side).
- Explicitly state that .NET Framework apps are Windows-only, and suggest .NET (Core/5+) for cross-platform scenarios.
- Include instructions for building and running .NET apps on Linux/macOS where applicable, or provide links to equivalent .NET (Core/5+) tutorials.
- Where PowerShell is mentioned, also reference Bash or other common Linux shells for parity.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/enable-dynamic-configuration-dotnet-background-service.md
...enable-dynamic-configuration-dotnet-background-service.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides environment variable setup instructions for Windows (cmd, PowerShell) before Linux/macOS (bash), and includes both Windows command prompt and PowerShell examples, which may suggest a Windows-first or Windows-heavy bias. However, Linux/macOS instructions are present and the .NET CLI is highlighted as cross-platform. No Windows-only tools or patterns are used, and Linux examples are not missing.
Recommendations
- Present environment variable setup instructions for all platforms in parallel or grouped together, rather than listing Windows first.
- Consider rotating the order of platform instructions or presenting Linux/macOS first in some sections to balance visibility.
- Explicitly state cross-platform compatibility in each step where applicable, especially when referencing tools like the .NET CLI.
- Add a note at the beginning clarifying that all steps are applicable to Windows, Linux, and macOS unless otherwise specified.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/enable-dynamic-configuration-java-spring-push-refresh.md
...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/enable-dynamic-configuration-java-spring-push-refresh.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS (bash), and includes explicit PowerShell examples. While Linux/macOS commands are present, Windows instructions are consistently listed first, and Windows-specific tools (setx, PowerShell) are highlighted. There are no Linux-specific tools or patterns mentioned, and the overall flow assumes familiarity with Windows environments.
Recommendations
- Alternate the order of platform instructions, sometimes listing Linux/macOS first.
- Add notes clarifying platform equivalence and any differences in behavior (e.g., setx vs export).
- Include Linux-specific troubleshooting tips or common patterns (e.g., .bashrc/.profile for persistent environment variables).
- Mention cross-platform tools (e.g., VS Code) more prominently and provide parity in screenshots if any are Windows-centric.
- Ensure all command examples are equally detailed for Linux/macOS and Windows, and avoid assuming Windows as the default platform.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/howto-telemetry-javascript.md
.../azure-app-configuration/howto-telemetry-javascript.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before mentioning the Linux/macOS equivalent. Windows-specific tools and patterns (setx, PowerShell syntax) are presented first, indicating a 'windows_first' ordering and a 'powershell_heavy' bias in the environment variable setup section.
Recommendations
- Present Linux/macOS and Windows instructions side-by-side or in parallel lists to avoid implying priority.
- Consider starting with a cross-platform method (e.g., using .env files or npm scripts) before listing OS-specific commands.
- Reduce emphasis on PowerShell unless it is required for a specific scenario; otherwise, provide Bash and PowerShell examples together.
- Explicitly state that all major platforms are supported and tested, and link to platform-specific troubleshooting guides if available.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/howto-targetingfilter-javascript.md
...-app-configuration/howto-targetingfilter-javascript.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias in the section about setting environment variables. Windows Command Prompt and PowerShell instructions are presented before the macOS/Linux equivalent, and both Windows shells are given explicit, separate examples. No other Windows-specific tools or patterns are present, and the rest of the guide uses cross-platform Node.js and Bash commands.
Recommendations
- Present environment variable instructions in a cross-platform or Linux-first order, or group all OS instructions together for parity.
- Consider using a table or collapsible sections for OS-specific instructions to avoid implicit prioritization.
- Ensure that Linux/macOS instructions are as detailed and visible as Windows instructions.
- Where possible, use platform-agnostic commands (e.g., via npm scripts or .env files) to minimize OS-specific steps.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/howto-telemetry-python.md
...cles/azure-app-configuration/howto-telemetry-python.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias by presenting Windows (cmd) and PowerShell commands for setting environment variables before mentioning the Linux/macOS equivalent. The Windows instructions are listed first, and PowerShell is given a dedicated example, while Linux/macOS is grouped together and appears last. No Linux-specific tools or patterns are missing, but the ordering prioritizes Windows users.
Recommendations
- Present environment variable instructions for Linux/macOS first, or list all platforms together in a table for parity.
- Avoid giving Windows (cmd) and PowerShell examples before Linux/macOS; consider alternating the order or grouping all examples equally.
- Explicitly mention that the instructions apply equally to all platforms, and provide clear guidance for Linux users.
- Consider adding a note that the Python code and Azure services are cross-platform, and highlight any platform-specific caveats if they exist.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/howto-variant-feature-flags-javascript.md
...onfiguration/howto-variant-feature-flags-javascript.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides instructions for setting environment variables on Windows (cmd and PowerShell) before mentioning the Linux/macOS method. Windows-specific tools (setx, PowerShell) are described in detail, with Linux/macOS covered last and more briefly. This ordering and emphasis may subtly prioritize Windows users and workflows.
Recommendations
- Present environment variable instructions for all platforms in parallel (e.g., a table or side-by-side code blocks), rather than listing Windows first.
- Give equal detail to Linux/macOS instructions, including notes about shell persistence (e.g., using ~/.bashrc or ~/.zshrc for permanent changes).
- Avoid Windows-centric language such as 'If you use the Windows command prompt...' as the primary instruction; instead, introduce all platforms equally.
- Consider including troubleshooting notes for Linux/macOS users (e.g., how to check environment variables, common shell differences).
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-chat-completion-dotnet.md
...app-configuration/quickstart-chat-completion-dotnet.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before mentioning Linux/macOS, and gives explicit PowerShell and Windows Command Prompt examples. While Linux/macOS is included, the ordering and detail favor Windows users, and there are no Linux-specific troubleshooting or parity notes.
Recommendations
- Present Linux/macOS instructions before or alongside Windows instructions, not after.
- Include Linux/macOS-specific troubleshooting tips (e.g., shell persistence, profile files).
- Add parity notes for Linux users regarding Azure CLI, authentication, and environment variable persistence.
- Ensure all command examples are given equal prominence and detail for both platforms.
- Consider grouping platform-specific instructions under clear headings for each OS.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-dotnet-core-app.md
.../azure-app-configuration/quickstart-dotnet-core-app.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS (bash), and includes PowerShell-specific commands. However, Linux/macOS instructions are present and parity is generally maintained. There is a slight Windows-first ordering and emphasis on Windows tools.
Recommendations
- Present environment variable instructions for all platforms in parallel, or begin with a neutral platform (e.g., bash) before listing Windows-specific methods.
- Avoid listing Windows command prompt and PowerShell instructions before Linux/macOS unless there is a clear user demographic justification.
- Consider grouping platform-specific instructions in tabs or side-by-side for equal visibility.
- Explicitly mention that all .NET CLI commands work identically across Windows, Linux, and macOS to reinforce cross-platform parity.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-javascript-provider.md
...re-app-configuration/quickstart-javascript-provider.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation displays mild Windows bias, especially in the 'Run the application' section. Windows command prompt and PowerShell instructions are presented before Linux/macOS equivalents, and PowerShell is given its own explicit example. The Node.js installation prerequisite links to a Windows-focused page, mentioning Windows and WSL before Linux. However, Linux/macOS instructions are present and correct, and all code samples are cross-platform JavaScript.
Recommendations
- Present Linux/macOS instructions before or alongside Windows instructions, rather than after.
- Provide a neutral Node.js installation link or mention Linux/macOS installation methods first.
- Avoid giving Windows/PowerShell examples more prominence than Linux equivalents.
- Consider grouping environment variable instructions by OS family (Windows, Linux/macOS) rather than by Windows tool (cmd, PowerShell).
- Ensure parity in troubleshooting or advanced setup steps for Linux users if any are present in extended documentation.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-python.md
.../articles/azure-app-configuration/quickstart-python.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation exhibits mild Windows bias in the prerequisites and environment variable setup sections. Windows-specific instructions (Windows command prompt and PowerShell) are presented before Linux/macOS equivalents, and links for Python setup reference only Windows documentation. However, all code samples and most instructions are cross-platform and do include Linux/macOS alternatives.
Recommendations
- Provide links to Python setup documentation for Linux/macOS alongside the Windows link in the prerequisites section.
- Present environment variable instructions for Linux/macOS before or alongside Windows/PowerShell, rather than after.
- Use neutral language such as 'If you use Windows...' and 'If you use Linux/macOS...' in parallel, rather than listing Windows first.
- Consider adding a table or tabbed layout for environment variable setup to equally highlight all platforms.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-feature-flag-javascript.md
...pp-configuration/quickstart-feature-flag-javascript.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias by listing Windows command prompt and PowerShell instructions before Linux/macOS equivalents when setting environment variables. It also provides explicit PowerShell examples, whereas Linux/macOS instructions are more generic. The Node.js installation guidance references Windows and WSL specifically, with no mention of native Linux distributions or package managers.
Recommendations
- Present platform instructions in parallel or rotate the order (e.g., Linux/macOS first in some sections) to avoid Windows-first perception.
- Include explicit Linux distribution examples (e.g., Ubuntu, Fedora) for Node.js installation, referencing native package managers (apt, yum, etc.) alongside Windows/WSL.
- Provide parity in command-line examples, such as showing how to persist environment variables in Linux shells (e.g., adding to ~/.bashrc or ~/.zshrc), similar to the Windows setx command.
- Consider grouping platform-specific instructions in tabs or collapsible sections to make parity and navigation clearer.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-go-web-app.md
...icles/azure-app-configuration/quickstart-go-web-app.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides instructions for setting environment variables on Windows (cmd and PowerShell) before mentioning Linux/macOS equivalents. Windows-specific tools (setx, PowerShell syntax) are described in detail, and Windows instructions are presented first in each authentication section. Linux/macOS instructions are present but always after Windows, and there is no evidence of missing Linux examples or exclusive use of Windows-only tools.
Recommendations
- Present Linux/macOS and Windows instructions in parallel or in a tabbed format, rather than always listing Windows first.
- Consider starting with cross-platform (bash) instructions, as Go developers often use Linux/macOS.
- Add notes about differences in environment variable persistence (e.g., setx vs export) and clarify that setx requires restarting the command prompt.
- Where possible, use platform-agnostic instructions (e.g., recommend using .env files or cross-platform tools for environment variables).
- Ensure that Linux/macOS instructions are as detailed as Windows, including troubleshooting tips if applicable.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-javascript.md
...icles/azure-app-configuration/quickstart-javascript.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias, particularly in the 'Configure an environment variable' section, where Windows command prompt and PowerShell instructions are presented before Linux/macOS equivalents. PowerShell and Windows-specific commands (setx, $Env:) are given explicit examples, while Linux/macOS instructions are grouped together and appear after Windows instructions. The Node.js installation instructions reference Windows and WSL before Linux, suggesting a Windows-centric approach.
Recommendations
- Present Linux/macOS and Windows instructions side-by-side or in parallel tabs, rather than listing Windows first.
- Explicitly mention Linux and macOS as primary platforms for JavaScript development, not just as alternatives.
- Provide links to Linux/macOS setup guides with equal prominence as Windows guides.
- Ensure that CLI examples and environment variable configuration steps are platform-neutral or equally detailed for all platforms.
- Consider using generic cross-platform instructions (e.g., 'export' for environment variables) as the default, with platform-specific notes as needed.