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 276-300 of 479 flagged pages
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 provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS, and includes both Windows Command Prompt and PowerShell commands. Linux/macOS instructions are present but always listed last. There are no missing Linux examples, but the ordering and inclusion of multiple Windows-specific shells (cmd, PowerShell) compared to a single Linux shell (bash) demonstrates a subtle Windows-first and PowerShell-heavy bias.
Recommendations
- Alternate the order of OS instructions (sometimes list Linux/macOS first, or use tabs for OS selection).
- Group all OS instructions under clearly labeled tabs (Windows, Linux/macOS) to avoid implicit prioritization.
- Provide parity in shell instructions: if both cmd and PowerShell are shown for Windows, consider mentioning both bash and zsh for Linux/macOS, or clarify that bash commands work for most shells.
- Explicitly state that all platforms are supported equally at the start of the relevant sections.
- Consider using cross-platform tools (like Azure CLI) for setup steps where possible, and highlight their usage.
Create Pull Request
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 command prompt and PowerShell commands are listed first, and PowerShell is given its own example, which may suggest a Windows-centric approach. However, Linux/macOS instructions are present and correct, and the rest of the guide uses cross-platform Go and Bash commands.
Recommendations
- Present Linux/macOS and Windows instructions in parallel tabs or side-by-side, rather than always listing Windows first.
- Avoid giving Windows (cmd/PowerShell) instructions priority over Linux/macOS, especially for Go developers who may be more likely to use Linux/macOS.
- Consider using tabbed code blocks for 'Set environment variable' steps, with clear labels for each OS/shell.
- Where possible, use cross-platform commands (e.g., Bash) as the default, with Windows-specific instructions as alternatives.
- Ensure parity in detail and clarity between Windows and Linux/macOS instructions.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/reload-key-vault-secrets-dotnet.md
...e-app-configuration/reload-key-vault-secrets-dotnet.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation assumes the use of ASP.NET Core and C#, which are cross-platform, but all instructions and examples are tailored to Visual Studio-style workflows and do not mention Linux or cross-platform development environments. There are no CLI, shell, or Linux-specific instructions or examples, and the Azure Portal UI steps are described without alternatives for command-line or automation scenarios common on Linux. The documentation implicitly assumes a Windows-centric development environment.
Recommendations
- Add equivalent instructions and examples for Linux environments, such as using the Azure CLI or Bash scripts to add Key Vault references and manage App Configuration.
- Explicitly mention that the steps apply to all platforms supported by ASP.NET Core, including Linux and macOS.
- Provide code snippets or instructions for editing files and running commands in a cross-platform way (e.g., using VS Code, nano, or command-line editors instead of assuming Visual Studio).
- Include references to automation and scripting approaches (e.g., az CLI, PowerShell Core, Bash) for managing Azure resources, not just portal-based workflows.
- Clarify that the .NET Core SDK and tools are available on Linux and macOS, and provide links or notes for installing and using them on those platforms.
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 provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS, and includes both setx (cmd) and PowerShell examples, which may be seen as Windows-centric. Linux/macOS instructions are present but listed after Windows ones. No Linux-specific tools or patterns are omitted, but the ordering and emphasis favor Windows users.
Recommendations
- Present Linux/macOS instructions before or alongside Windows instructions, rather than after.
- Use tabbed or parallel formatting to show all OS instructions at once, reducing perceived priority.
- Ensure parity in detail and troubleshooting tips for Linux/macOS environments.
- Consider including a note that all major platforms are supported equally, to reinforce cross-platform intent.
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 environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS, and includes explicit PowerShell examples. While Linux/macOS instructions are present, Windows command-line tools and patterns are consistently mentioned first, which may suggest a subtle Windows-first bias.
Recommendations
- Present Linux/macOS and Windows instructions in parallel tabbed sections, or alternate which platform is shown first.
- Avoid always listing Windows (cmd/PowerShell) before Linux/macOS in step-by-step instructions.
- Where possible, use cross-platform commands or highlight platform-agnostic approaches.
- Ensure that Linux/macOS users are given equal prominence and clarity in all setup and configuration steps.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/reload-key-vault-secrets-dotnet.md
...e-app-configuration/reload-key-vault-secrets-dotnet.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation is focused exclusively on ASP.NET Core applications, which are cross-platform, but all examples and instructions assume a development environment and workflow typical of Windows users. There are no explicit Linux or cross-platform command-line examples, and all configuration steps are described via the Azure Portal UI or C# code, with no mention of CLI or scripting alternatives (such as Azure CLI, Bash, or PowerShell). This can implicitly prioritize Windows-centric workflows and may leave Linux developers without clear guidance.
Recommendations
- Provide equivalent command-line instructions using Azure CLI for adding Key Vault references and managing App Configuration, with examples that work on Linux, macOS, and Windows.
- Explicitly mention that the steps apply to all platforms supported by ASP.NET Core, and clarify any platform-specific considerations if they exist.
- Include sample scripts or terminal commands for common tasks (e.g., adding a Key Vault reference, rotating certificates) that can be run in Bash or other non-Windows shells.
- Add a section or callout for Linux/macOS users, highlighting any differences or confirming parity.
- Ensure that any referenced tutorials or prerequisites also contain Linux/macOS instructions where relevant.
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 environment variable setup instructions for Windows Command Prompt and PowerShell before mentioning Linux/macOS, and gives explicit PowerShell examples. While Linux/macOS commands are included, Windows instructions are consistently presented first, and PowerShell is given equal prominence to Bash, which may suggest a slight Windows bias.
Recommendations
- Alternate the order of platform instructions, sometimes listing Linux/macOS first.
- Group all platform-specific instructions under clearly labeled headings, or use tabs to avoid implicit prioritization.
- Consider reducing the prominence of PowerShell unless there are unique steps required for Windows users.
- Where possible, provide cross-platform commands (e.g., using env files or cross-platform tools) to minimize OS-specific instructions.
- Explicitly state that all steps are supported on Linux/macOS and Windows, to reinforce parity.
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 provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS, and includes both setx (cmd) and PowerShell commands, which may give the impression of Windows being the primary platform. Linux/macOS instructions are present but appear after Windows examples. There are no missing Linux examples, but the ordering and inclusion of multiple Windows-specific shells (cmd, PowerShell) before Linux can be seen as a subtle Windows bias.
Recommendations
- Present Linux/macOS and Windows instructions in parallel (side-by-side tabs or clearly separated sections) rather than listing Windows first.
- Consider listing Linux/macOS first, as Go developers often use these platforms.
- If showing multiple Windows shells (cmd, PowerShell), also mention common Linux shells (bash, zsh) for parity, or consolidate Windows instructions to reduce perceived bias.
- Explicitly state that all commands are cross-platform unless otherwise noted.
- Ensure that any troubleshooting or advanced sections do not assume Windows as the default environment.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/reload-key-vault-secrets-dotnet.md
...e-app-configuration/reload-key-vault-secrets-dotnet.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation is focused exclusively on ASP.NET Core and C# (.NET) development, which is traditionally associated with Windows environments. There are no examples or instructions for Linux or cross-platform scenarios, such as running the app on Linux, using Linux-based tools, or deploying in a non-Windows environment. All code and setup instructions assume a Windows-centric workflow, and there is no mention of Linux-specific considerations or parity.
Recommendations
- Include explicit instructions or notes for running the ASP.NET Core app on Linux (e.g., Ubuntu) and macOS, such as using the dotnet CLI on those platforms.
- Add examples or references for deploying and managing the application in Linux environments, including any differences in environment variables, file paths, or permissions.
- Mention that ASP.NET Core is cross-platform and can be run on Windows, Linux, and macOS, and provide links to relevant documentation for non-Windows users.
- If any Azure CLI or scripting is required, provide both PowerShell (Windows) and Bash (Linux/macOS) examples.
- Clarify that the Azure portal steps are platform-agnostic, but any local development steps should consider cross-platform compatibility.
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 presents environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS, and provides both setx (cmd) and PowerShell commands, which may suggest a Windows-first and PowerShell-heavy approach. However, Linux/macOS instructions are present and correct, and the rest of the guide uses cross-platform Go and Bash commands.
Recommendations
- Present Linux/macOS and Windows instructions in parallel (side-by-side tabs or tables) rather than listing Windows first.
- Avoid giving Windows command prompt and PowerShell commands more prominence than Linux/macOS equivalents.
- Consider leading with Bash/Linux/macOS examples, as Go developers often use cross-platform tools.
- Explicitly state that all commands are cross-platform where possible, and only provide OS-specific instructions when necessary.
- If using tabbed instructions, ensure Linux/macOS is a first-class tab alongside Windows.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/reload-key-vault-secrets-dotnet.md
...e-app-configuration/reload-key-vault-secrets-dotnet.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page assumes usage of ASP.NET Core and provides instructions and code samples only for .NET (C#) applications, which are most commonly associated with Windows development. There are no examples, notes, or instructions for Linux-based environments, nor is there mention of cross-platform considerations (such as running on Linux containers or using Linux command-line tools). The Azure Portal UI steps are platform-agnostic, but the overall context and code focus on Windows-centric development patterns.
Recommendations
- Add explicit notes or examples for running ASP.NET Core apps on Linux (e.g., in Docker containers or on Azure App Service for Linux).
- Include Linux shell (bash) equivalents for any command-line steps, even if minimal.
- Clarify that the code samples work cross-platform and mention any OS-specific considerations (such as file permissions or environment variable handling on Linux).
- Provide links or references to documentation for deploying and managing ASP.NET Core apps on Linux environments.
- If relevant, mention how to perform similar configuration using CLI tools (e.g., Azure CLI) with Linux shell examples.
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 provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS, and includes explicit PowerShell examples. While Linux/macOS instructions are present, Windows command-line and PowerShell commands are consistently listed first, which may signal a Windows-centric approach.
Recommendations
- Alternate the order of platform instructions (e.g., list Linux/macOS first in some sections, or use tabs for OS-specific instructions).
- Use tabbed or collapsible sections for platform-specific commands to give equal prominence to Windows and Linux/macOS.
- Where possible, provide cross-platform commands (e.g., using env files or cross-platform tools) or clarify that the order does not imply priority.
- Explicitly state that all major platforms are supported and tested.
- Consider including screenshots or CLI output from both Windows and Linux/macOS terminals to reinforce parity.
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 environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS, and includes both Windows Command Prompt and PowerShell commands. Linux/macOS instructions are present but come after the Windows examples. There are no missing Linux examples or exclusive use of Windows tools, but the ordering and emphasis show a mild Windows-first bias.
Recommendations
- Present Linux/macOS and Windows instructions in parallel tabs or in the same order throughout the document, rather than listing Windows first.
- Avoid giving Windows instructions (cmd, PowerShell) more prominence than Linux/macOS; consider starting with Linux/macOS or presenting all platforms equally.
- If using tabbed instructions, ensure the default tab is not always Windows.
- Explicitly mention that all commands work cross-platform where applicable, and highlight any platform-specific differences only when necessary.
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 provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS, and includes both Windows command prompt and PowerShell commands. Linux/macOS instructions are present and correct, but are always listed after Windows instructions. There are no missing Linux examples, but the ordering and inclusion of multiple Windows-specific shells (cmd, PowerShell) before Linux suggest a mild Windows-first bias.
Recommendations
- Present Linux/macOS and Windows instructions in parallel tabs or with equal prominence, rather than always listing Windows first.
- Consider listing Linux/macOS instructions first, or randomizing the order to avoid implicit prioritization.
- If including both cmd and PowerShell for Windows, consider also mentioning common Linux shells (bash, zsh) for parity, or simply use a tabbed interface for OS selection.
- Review other sections for subtle Windows-centric language or assumptions, and ensure all CLI examples are cross-platform where possible.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/reload-key-vault-secrets-dotnet.md
...e-app-configuration/reload-key-vault-secrets-dotnet.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation focuses exclusively on ASP.NET Core and C# examples, with no mention of Linux-specific workflows, tools, or command-line instructions. All instructions assume use of the Azure Portal or .NET tooling, which are cross-platform, but the context and language are heavily oriented toward Windows developers. There are no examples or notes for Linux environments, shell commands, or non-Windows development patterns.
Recommendations
- Add explicit notes clarifying that all .NET Core and Azure SDK instructions apply equally to Linux, macOS, and Windows.
- Include example commands for common Linux shells (e.g., bash) where relevant, such as for environment variable setup or CLI usage.
- Mention and link to cross-platform development tools and editors (e.g., Visual Studio Code, dotnet CLI) to reinforce Linux compatibility.
- If any steps require the Azure Portal, note that it is web-based and platform-agnostic.
- Provide troubleshooting tips or references for Linux users, such as permissions or certificate store differences.
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 a PowerShell example for consuming exported environment variables but does not include equivalent examples for Linux shells (e.g., Bash). There are no explicit references to Windows-only tools or patterns, but the lack of Linux/Unix shell examples may create a perception of Windows bias.
Recommendations
- Add equivalent Bash (and/or other popular Linux shell) examples alongside the PowerShell example for accessing environment variables in pipeline tasks.
- Explicitly mention that the exported variables are accessible in all supported agent operating systems and provide cross-platform usage guidance.
- Review screenshots and UI instructions to ensure they are not specific to Windows environments, or clarify when instructions are OS-agnostic.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/howto-chat-completion-config.md
...zure-app-configuration/howto-chat-completion-config.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows-first bias by only referencing the Azure portal and .NET (a Microsoft-centric technology) for implementation, without providing examples or instructions for Linux users or alternative platforms. There are no CLI, Bash, or cross-platform code samples, and no mention of Linux-specific tools or workflows.
Recommendations
- Include Azure CLI and Bash examples for creating and managing chat completion configurations, ensuring Linux and macOS users are supported.
- Provide code samples and implementation guides for additional languages and platforms, such as Python, Java, or Node.js, which are popular in Linux environments.
- Explicitly mention cross-platform compatibility and note any OS-specific considerations.
- Add links or references to documentation for using Azure App Configuration from Linux-based systems.
- Balance .NET examples with equivalent open-source or cross-platform alternatives.
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 Command Prompt and PowerShell before mentioning the Linux/macOS equivalent, and gives more detailed instructions for Windows users. While Linux/macOS is included, the ordering and emphasis favor Windows environments.
Recommendations
- Present environment variable setup instructions for all platforms together, or start with a neutral (cross-platform) example such as bash, then provide Windows-specific instructions.
- Ensure that Linux/macOS instructions are as detailed and prominent as Windows instructions.
- Consider using tabbed or side-by-side formatting for platform-specific commands to avoid implicit prioritization.
- Review other sections for subtle Windows-first language or assumptions, and strive for parity in all platform-specific guidance.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/enable-dynamic-configuration-python.md
...p-configuration/enable-dynamic-configuration-python.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation shows a mild Windows bias by only linking to Python installation instructions for Windows in the prerequisites and not mentioning Linux or macOS setup. No Linux-specific examples or instructions are provided, and the only OS-specific resource is for Windows.
Recommendations
- In the prerequisites, add links to official Python installation/setup documentation for Linux and macOS alongside the Windows link.
- Explicitly mention that the instructions and code samples are cross-platform and can be run on Linux, macOS, and Windows.
- If there are any OS-specific considerations (such as environment variable syntax or CLI usage), provide examples for both Windows and Linux/macOS shells.
- Consider adding a note or section confirming compatibility and any differences in running the samples on Linux/macOS.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-container-apps.md
...s/azure-app-configuration/quickstart-container-apps.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation demonstrates a bias toward Windows environments by focusing exclusively on ASP.NET Core (a Microsoft technology), referencing Docker Desktop (which is primarily a Windows/Mac tool), and omitting any Linux-specific instructions or examples. There are no PowerShell-specific commands, but the absence of Linux shell (bash) examples and the lack of mention of Linux-native Docker workflows or tools (such as Podman or native Docker on Linux) indicate a Windows-first approach. Additionally, the documentation does not address potential differences in environment variable syntax or file system paths between Windows and Linux containers.
Recommendations
- Include explicit instructions and examples for Linux users, such as using native Docker on Linux (not just Docker Desktop).
- Mention and, where appropriate, provide bash shell command equivalents for all CLI instructions.
- Clarify that the Dockerfile and deployment steps are cross-platform, and note any differences in file paths or environment variable syntax between Windows and Linux.
- Add a section or callout for Linux users, highlighting any OS-specific considerations (e.g., file permissions, case sensitivity).
- Consider including a sample using a non-Microsoft stack (e.g., a Python or Node.js app) to broaden applicability.
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 all deployment, review, and cleanup steps. However, PowerShell is featured equally alongside CLI, and there is no mention of Linux-specific shell environments (such as Bash) or explicit Linux tooling. The use of PowerShell, which is traditionally associated with Windows, and the lack of Linux/Bash-specific context or examples, indicates a mild Windows bias. Additionally, the ordering of examples sometimes places PowerShell before or equally with CLI, rather than prioritizing cross-platform-first tools.
Recommendations
- Explicitly mention that Azure CLI commands work identically on Linux, macOS, and Windows, and provide Bash-specific context where appropriate.
- Consider providing Bash script examples or notes for Linux/macOS users, especially for steps like saving files or setting parameters.
- If PowerShell is included, clarify that it is available cross-platform, but note that Bash is the default shell on most Linux distributions.
- Where possible, lead with Azure CLI (which is cross-platform) and present PowerShell as an alternative, rather than as an equal or primary option.
- Add a note in the prerequisites or deployment sections about shell compatibility and how to run the examples on Linux/macOS.
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 in the environment variable setup sections. It also provides explicit PowerShell commands, which may not be as relevant for Linux/macOS users. However, Linux/macOS instructions are present and correct, and the rest of the documentation is generally cross-platform.
Recommendations
- Present environment variable instructions in a neutral or rotating order (e.g., Linux/macOS first in some sections, or group all OSes together).
- Avoid giving Windows command prompt and PowerShell instructions precedence over Linux/macOS unless there is a clear user base justification.
- Consider using tabbed or collapsible sections for each OS to give them equal prominence.
- Where possible, provide cross-platform commands (e.g., using cross-env for npm scripts) or mention tools that work on all platforms.
- Clarify that all examples work equally on Windows, Linux, and macOS, and link to OS-specific setup guides only as needed.
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 way environment variable instructions are presented. Windows Command Prompt and PowerShell commands are listed before Linux/macOS equivalents, and there is a dedicated prerequisite link for setting up Python on Windows but not for Linux. However, Linux/macOS commands are present and correct, and the code samples themselves are cross-platform.
Recommendations
- Present environment variable instructions for Linux/macOS before or alongside Windows instructions, or use tabs to separate platforms equally.
- Add a link or note for setting up Python on Linux/macOS in the prerequisites, not just Windows.
- Ensure parity in all setup and troubleshooting steps for both Windows and Linux/macOS users.
- Consider using platform-agnostic language or grouping instructions by OS in a way that does not prioritize Windows.
Azure App Configuration
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-feature-flag-python.md
...re-app-configuration/quickstart-feature-flag-python.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias by presenting Windows Command Prompt and PowerShell instructions before macOS and Linux equivalents when setting environment variables. The Windows command is described as the default, with extra validation steps, and PowerShell is given a dedicated section. While Linux and macOS commands are present, they appear after the Windows instructions, and there is no explicit parity in validation or troubleshooting steps for non-Windows platforms.
Recommendations
- Present all OS instructions in parallel tabbed sections (Windows CMD, PowerShell, macOS, Linux) without ordering Windows first by default.
- Ensure validation and troubleshooting steps are equally detailed for all platforms, not just Windows.
- Avoid language that implies Windows is the default or primary development environment.
- Where possible, provide cross-platform commands or highlight differences only where necessary.
- Consider including a table summarizing environment variable commands for all platforms at once for quick reference.
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 both Windows command prompt and PowerShell commands, which may suggest a Windows-first and PowerShell-heavy approach. However, Linux/macOS instructions are present and complete. There are no exclusive references to Windows-only tools or missing Linux examples, but the ordering and emphasis may subtly favor Windows users.
Recommendations
- Present environment variable setup instructions in a neutral order, such as listing Linux/macOS (bash) first or grouping all OS instructions together without preference.
- Avoid giving the impression of Windows primacy by using headings like 'On Windows', 'On macOS', 'On Linux' rather than listing Windows first.
- Ensure that all command-line examples are equally detailed for all platforms, and consider providing cross-platform scripts or notes where possible.
- Explicitly state that all steps are cross-platform unless a step is truly OS-specific.
- Where possible, use platform-agnostic tooling or highlight alternatives (e.g., cross-platform editors, deployment tools) to reinforce parity.