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

474 issues found
Showing 176-200 of 474 flagged pages
Azure App Configuration Quickstart for Azure App Configuration with .NET | Microsoft Docs .../azure-app-configuration/quickstart-dotnet-core-app.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
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 examples. However, Linux/macOS instructions are present and use the appropriate export command. No Linux-specific tools or patterns are missing, and the .NET CLI is highlighted as cross-platform. There is a slight ordering bias toward Windows instructions.
Recommendations
  • Present environment variable instructions for all platforms in parallel, or start with Linux/macOS to balance the ordering.
  • Explicitly state that all commands work on Windows, macOS, and Linux, and clarify any platform-specific caveats.
  • Consider grouping platform instructions in tabs or side-by-side tables to emphasize parity.
  • Add a note that the .NET CLI commands are identical across platforms, reducing perceived Windows-centricity.
GitHub Create Pull Request
Azure App Configuration Quickstart for adding feature flags to JavaScript apps ...pp-configuration/quickstart-feature-flag-javascript.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation demonstrates a Windows-first bias in its instructions for setting environment variables, listing Windows Command Prompt and PowerShell methods before Linux/macOS equivalents. It also provides explicit PowerShell instructions, reinforcing Windows-centric usage patterns. The only mention of Linux is in the context of installing Node.js, and Linux/macOS commands are listed last in each section. No Linux-specific tools or troubleshooting are discussed.
Recommendations
  • Present Linux/macOS and Windows instructions in parallel or randomize their order to avoid implicit prioritization.
  • Provide Linux/macOS examples first in some sections, or use tabs with equal prominence for each OS.
  • Include troubleshooting tips or notes for Linux/macOS users, such as differences in environment variable persistence.
  • Reference Linux-native tools and patterns (e.g., .bashrc, .profile) for environment variable persistence.
  • Clarify that all platforms are equally supported and tested, and provide links to platform-specific guidance where relevant.
GitHub Create Pull Request
Azure App Configuration Quickstart for using Azure App Configuration with Go web applications ...icles/azure-app-configuration/quickstart-go-web-app.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
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 and correct, Windows tooling and patterns are mentioned first in each relevant section, which may subtly prioritize Windows users.
Recommendations
  • Present Linux/macOS and Windows instructions in parallel (side-by-side tabs or columns) rather than listing Windows first.
  • Avoid language that implies Windows is the default or primary platform (e.g., 'If you use the Windows command prompt...' before 'If you use macOS or Linux...').
  • Consider leading with cross-platform shell commands (e.g., 'export' for environment variables), then provide Windows-specific alternatives.
  • Ensure parity in troubleshooting and tips for both platforms.
  • Where possible, use platform-agnostic instructions or highlight platform differences only when necessary.
GitHub Create Pull Request
Azure App Configuration Quickstart for using Azure App Configuration with Go applications ...s/azure-app-configuration/quickstart-go-console-app.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias in the environment variable setup instructions. Windows command prompt and PowerShell commands are presented first and in more detail, while Linux/macOS instructions appear after. PowerShell and Windows-specific tools (setx) are mentioned explicitly, with no equivalent Linux/macOS tooling details. However, the main Go code samples and CLI usage are cross-platform and do not favor Windows.
Recommendations
  • Present Linux/macOS instructions before or alongside Windows instructions, rather than after.
  • Provide equal detail for Linux/macOS tooling (e.g., mention how to persist environment variables across sessions, such as adding to ~/.bashrc or ~/.zshrc).
  • Consider grouping environment variable setup instructions by OS in a tabbed or side-by-side format for parity.
  • Avoid using Windows-specific tools (like setx) without mentioning Linux/macOS equivalents for persistent environment variables.
  • Explicitly state that all Go code and CLI commands are cross-platform, and highlight any OS-specific caveats if present.
GitHub Create Pull Request
Azure App Configuration Quickstart for using Azure App Configuration with JavaScript apps ...re-app-configuration/quickstart-javascript-provider.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias in the instructions for setting environment variables. Windows command prompt and PowerShell commands are listed before Linux/macOS equivalents, and PowerShell is given its own explicit example. The Node.js installation instructions reference Windows and WSL before Linux, and the link for Node.js setup points to a Windows-focused page. However, all code samples and CLI instructions are cross-platform, and Linux/macOS commands are present where relevant.
Recommendations
  • Present Linux/macOS instructions before or alongside Windows instructions, rather than after.
  • Provide a more balanced introduction to Node.js installation, referencing Linux and macOS equally with Windows.
  • Ensure external links for setup (such as Node.js installation) point to platform-neutral or multi-platform resources.
  • Consider grouping environment variable instructions by platform, or using tabs for each OS to avoid implicit prioritization.
  • Review other sections for similar ordering or tool prioritization to ensure parity.
GitHub 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 →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
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 link for Python setup is for Windows. However, Linux/macOS commands are present and correct, and the main code samples are platform-agnostic.
Recommendations
  • Add links or references for setting up Python on Linux/macOS alongside the Windows documentation link in the prerequisites.
  • Present environment variable instructions in a neutral order (e.g., Linux/macOS first, or group all OSes together without prioritizing Windows).
  • Consider including a note that all examples work equally on Linux/macOS, and highlight any OS-specific caveats if present.
  • Ensure parity in troubleshooting and setup guidance for Linux/macOS users.
GitHub Create Pull Request
Azure App Configuration Roll out features to targeted audiences in a Python app ...re-app-configuration/how-to-targeting-filter-python.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias in the section about setting environment variables, where Windows Command Prompt and PowerShell instructions are presented before Linux/macOS equivalents. PowerShell and Windows-specific commands are explicitly called out, while Linux/macOS instructions are grouped together and presented last. The rest of the documentation is generally cross-platform, with Python and Bash examples, but the ordering and explicit mention of Windows tools indicate a subtle preference for Windows environments.
Recommendations
  • Present environment variable instructions in a neutral or parallel format (e.g., side-by-side table or tabs for Windows, PowerShell, and Linux/macOS) to avoid implying priority.
  • Avoid listing Windows instructions first unless there is a clear audience justification; consider rotating or randomizing order, or using alphabetical order.
  • Explicitly state that all platforms are supported and provide equal detail for each.
  • Where possible, use platform-agnostic commands or highlight cross-platform tools.
  • Add troubleshooting notes for Linux/macOS users if there are platform-specific caveats.
GitHub Create Pull Request
Azure App Configuration Quickstart for using Azure App Configuration with Go web applications ...icles/azure-app-configuration/quickstart-go-web-app.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS equivalents. Windows-specific tools (setx, PowerShell syntax) are described in detail, while Linux/macOS instructions are given after. There is no evidence of missing Linux examples, but the ordering and emphasis favor Windows users.
Recommendations
  • Present environment variable setup instructions for Linux/macOS first or in parallel with Windows instructions.
  • Use tabbed or side-by-side formatting for OS-specific commands to avoid implicit prioritization.
  • Explicitly mention that all steps are cross-platform and provide equal detail for Linux/macOS commands.
  • Consider adding troubleshooting notes for both Windows and Linux/macOS environments.
GitHub Create Pull Request
Azure App Configuration Quickstart for adding feature flags to Python with Azure App Configuration ...re-app-configuration/quickstart-feature-flag-python.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation demonstrates Windows bias by presenting Windows Command Prompt and PowerShell instructions before macOS and Linux equivalents for setting environment variables. The Windows instructions are more detailed (e.g., mentioning restarting the command prompt), and PowerShell is given its own section, while Linux and macOS share a generic 'unix' tab. There is no evidence of missing Linux examples or exclusive use of Windows tools, but the ordering and emphasis favor Windows users.
Recommendations
  • Present environment variable instructions in a neutral order (e.g., Linux/macOS first, or alphabetical), or group all OS instructions together for parity.
  • Provide equally detailed instructions for Linux/macOS, including validation steps and any OS-specific caveats (e.g., persistence of environment variables).
  • Avoid giving Windows-specific tools (PowerShell, Command Prompt) their own sections unless Linux/macOS equivalents are also highlighted.
  • Consider adding troubleshooting notes for Linux/macOS users, similar to those provided for Windows (e.g., about restarting the shell).
GitHub Create Pull Request
Azure App Configuration Quickstart for adding feature flags to Spring Boot with Azure App Configuration ...p-configuration/quickstart-feature-flag-spring-boot.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
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 instructions are present, Windows tools and patterns are mentioned first, which may subtly prioritize Windows users. There are no Linux-specific tool recommendations or examples, but parity is generally maintained in the environment variable section.
Recommendations
  • Present environment variable instructions for Linux/macOS before or alongside Windows examples, rather than after.
  • Explicitly state that all commands work cross-platform and highlight any platform-specific caveats.
  • Include troubleshooting tips or notes for Linux/macOS users (e.g., shell differences, permissions).
  • If using screenshots or portal instructions, ensure they are not Windows-centric (e.g., avoid showing only Windows file paths or UI).
  • Consider adding a table or tabs for environment variable setup, with equal prominence for Linux/macOS and Windows.
GitHub Create Pull Request
Azure App Configuration Quickstart for using Azure App Configuration with Go applications ...s/azure-app-configuration/quickstart-go-console-app.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
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 commands. While Linux/macOS instructions are present, Windows tools and patterns are mentioned first, which may subtly prioritize Windows users.
Recommendations
  • Present environment variable setup instructions for all platforms in parallel (e.g., a table or grouped tabs), rather than listing Windows first.
  • Avoid giving Windows-specific instructions (cmd, PowerShell) priority over Linux/macOS equivalents.
  • Where possible, use cross-platform commands (e.g., 'export' for bash/zsh, with notes for Windows) or provide all options together.
  • Explicitly mention that all steps are equally applicable to Linux/macOS and Windows, and highlight any platform-specific caveats.
  • Consider adding troubleshooting notes for Linux/macOS users if there are Azure CLI or authentication differences.
GitHub Create Pull Request
Azure App Configuration Export settings from App Configuration with Azure Pipelines .../azure-app-configuration/azure-pipeline-export-task.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides an explicit PowerShell example for consuming exported environment variables, but does not offer a Linux shell (e.g., Bash) equivalent. There are no references to Linux tools or patterns, and the only code sample is Windows-centric. This may lead Linux users to feel unsupported or unsure how to use the feature in their environments.
Recommendations
  • Add equivalent Bash (and/or other popular shell) examples for consuming environment variables in subsequent tasks, e.g., `echo "$myBuildSetting"`.
  • Explicitly state that the exported variables are available in all supported agent operating systems, including Linux and macOS.
  • Where screenshots or instructions reference UI elements, clarify that these steps are OS-agnostic unless there are platform-specific differences.
  • If troubleshooting or advanced usage involves command-line tools, provide both Windows (PowerShell) and Linux (Bash) examples.
GitHub Create Pull Request
Azure App Configuration Configuration Provider Overview ...e-app-configuration/configuration-provider-overview.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page lists .NET and ASP.NET Core provider libraries first, with sample links pointing to 'DotNetCore' and '.NET Framework' examples. These frameworks are traditionally associated with Windows environments, and there are no explicit Linux or cross-platform usage examples, nor are Linux-specific tools or patterns mentioned. The ordering and sample emphasis suggest a Windows-first bias, and the lack of Linux-specific examples or instructions further reinforces this.
Recommendations
  • Add explicit Linux usage examples for each provider, especially for .NET and ASP.NET Core, demonstrating configuration on Linux environments (e.g., Ubuntu, containers).
  • Include instructions or samples using Linux-native tools (such as bash scripts, systemd integration, or Docker) alongside any Windows/Powershell examples.
  • Reorder the provider library table to alternate or group by language/platform rather than listing Windows-centric frameworks first.
  • Mention cross-platform compatibility and provide guidance for running .NET Core/ASP.NET Core on Linux.
  • Ensure parity in documentation for Linux and Windows, including troubleshooting, deployment, and environment setup.
GitHub Create Pull Request
Azure App Configuration Tutorial for using Azure App Configuration dynamic configuration in an Azure Functions app ...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/enable-dynamic-configuration-azure-functions-csharp.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS (bash). Visual Studio and Windows-specific tooling (e.g., setx, F5, firewall exception) are mentioned, with screenshots and workflow focused on Windows. Linux/macOS instructions are present but always listed last, and there are no Linux-specific tooling or editor examples.
Recommendations
  • Present Linux/macOS instructions before or alongside Windows instructions, not always after.
  • Include examples for popular Linux/macOS editors and workflows (e.g., VS Code, CLI-only).
  • Add screenshots and guidance for running and debugging Azure Functions on Linux/macOS.
  • Mention cross-platform tools (e.g., Azure Functions Core Tools CLI) as primary, not just Visual Studio.
  • Clarify that all steps can be performed on Linux/macOS and highlight any platform-specific differences.
GitHub Create Pull Request
Azure App Configuration .NET Framework: dynamic configuration in App Configuration ...p-configuration/enable-dynamic-configuration-dotnet.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates a Windows-first bias in several areas. Visual Studio is listed as the only development environment, and instructions for building and running the app reference restarting Visual Studio. When setting environment variables, Windows command prompt and PowerShell instructions are presented before Linux/macOS equivalents. Screenshots and examples focus on Windows terminals (Command Prompt, PowerShell), and there is no mention of cross-platform editors or Linux-specific development workflows.
Recommendations
  • Include instructions for building and running the app using cross-platform editors such as Visual Studio Code or JetBrains Rider.
  • Provide parity in environment variable instructions by listing Linux/macOS commands before or alongside Windows commands, not after.
  • Add Linux/macOS-specific notes for running .NET Framework apps (e.g., using Mono, or clarify .NET Framework limitations on non-Windows platforms).
  • Include screenshots or terminal output examples from Linux/macOS environments.
  • Mention and link to cross-platform .NET development resources, and clarify any platform-specific limitations or requirements.
GitHub Create Pull Request
Azure App Configuration Enable telemetry for feature flags in a Node.js application .../azure-app-configuration/howto-telemetry-javascript.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
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 and PowerShell commands are presented first, which may suggest a Windows-centric approach and could make Linux users feel secondary.
Recommendations
  • Present environment variable setup instructions for all platforms together, or start with a neutral (cross-platform) approach.
  • Consider grouping Windows, PowerShell, and Linux/macOS instructions under clear subheadings for parity.
  • Add notes to clarify that all platforms are equally supported.
  • Review other sections for similar ordering and ensure Linux/macOS examples are not consistently placed last.
GitHub Create Pull Request
Azure App Configuration Enable telemetry for feature flags in a Python application ...cles/azure-app-configuration/howto-telemetry-python.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
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 commands are listed first, and PowerShell is given its own example, while Linux/macOS is grouped together and listed last. All other code and instructions are platform-neutral Python or HTML, with no exclusive Windows tools or patterns elsewhere.
Recommendations
  • List Linux/macOS environment variable instructions before or alongside Windows examples to avoid Windows-first ordering.
  • Present all platform instructions in a table or side-by-side format for parity.
  • Explicitly state that the instructions apply equally to all platforms unless otherwise noted.
  • Consider adding a note that the Python code and Azure services are cross-platform, to reinforce platform neutrality.
GitHub Create Pull Request
Azure App Configuration Use variant feature flags in a Node.js application ...onfiguration/howto-variant-feature-flags-javascript.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates Windows bias in the section on setting environment variables: Windows Command Prompt and PowerShell instructions are presented first and in more detail, while Linux/macOS instructions are listed last. Windows-specific tools (setx, PowerShell syntax) are mentioned explicitly, and the Windows instructions are more verbose (e.g., mentioning restarting the command prompt). There are no Linux-specific tools or troubleshooting tips provided, and the overall flow prioritizes Windows users.
Recommendations
  • Present Linux/macOS instructions before or alongside Windows instructions, rather than after.
  • Provide equal detail for Linux/macOS, such as mentioning shell session persistence for exported variables.
  • Include troubleshooting tips for Linux/macOS users (e.g., how to check if the variable is set, how to persist it across sessions).
  • Avoid Windows-centric language such as 'restart the command prompt' unless equivalent Linux/macOS guidance is given.
  • Consider grouping OS instructions in a table or tabbed format for parity and clarity.
GitHub Create Pull Request
Azure App Configuration Integrate Azure App Configuration using a continuous integration and delivery pipeline ...es/azure-app-configuration/integrate-ci-cd-pipeline.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents Windows command prompt and PowerShell instructions before macOS and Linux equivalents, and provides detailed Windows-specific environment variable setup. While Linux/macOS examples are present, the ordering and emphasis favor Windows users, and the build script uses Windows-style path separators (\) in the MSBuild example, which may not work on Linux/macOS.
Recommendations
  • Present platform instructions in parallel or start with a neutral/default (e.g., .NET CLI) before platform-specific steps.
  • Use cross-platform path separators (e.g., $(OutDir)/azureappconfig.json) in MSBuild scripts or provide separate examples for Windows and Linux/macOS.
  • Explicitly state that all steps are supported on Linux/macOS and provide troubleshooting notes for platform-specific issues.
  • Ensure parity in detail and clarity for Linux/macOS instructions, matching those given for Windows.
  • Consider grouping environment variable setup instructions in a table or tabs that do not prioritize Windows.
GitHub Create Pull Request
Azure App Configuration Quickstart for using chat completion configuration in a Go app ...ure-app-configuration/quickstart-chat-completion-go.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before mentioning Linux/macOS equivalents. Windows-specific tools (setx, PowerShell) are described in detail, while the Linux/macOS method is given last and without additional context. No Linux-specific tools or patterns are mentioned elsewhere, but the Go code and build/run instructions are cross-platform.
Recommendations
  • Present environment variable setup instructions for Linux/macOS first, or in parallel with Windows, to avoid implying Windows is primary.
  • Provide equal detail for Linux/macOS commands (e.g., mention shell profile persistence for export).
  • Add notes clarifying cross-platform compatibility of the Go code and Azure SDKs.
  • Consider grouping OS instructions in a table or collapsible sections to emphasize parity.
  • Avoid using Windows-specific terminology (e.g., 'restart the command prompt') without Linux/macOS equivalents.
GitHub Create Pull Request
Azure App Configuration Create an Azure App Configuration store using Bicep ...n/articles/azure-app-configuration/quickstart-bicep.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
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 (a Windows-centric tool) is given equal prominence to CLI, and is presented in parallel tabs throughout. There is no mention of Linux-specific shell environments (e.g., Bash), nor any explicit guidance for Linux users. The use of PowerShell may implicitly favor Windows users, as PowerShell is less commonly used on Linux compared to Bash or other shells.
Recommendations
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and that Bash is the default shell on most Linux systems.
  • Add example commands using Bash (if any differences exist) or clarify that the CLI commands are cross-platform.
  • Consider listing Azure CLI (cross-platform) examples before PowerShell (Windows-centric) examples, or clarify the order is not indicative of platform preference.
  • Add a note for Linux/macOS users on how to install and use Azure CLI, if not already present.
  • Remove implicit parity between PowerShell and CLI unless PowerShell is equally supported and used on Linux/macOS.
GitHub Create Pull Request
Azure App Configuration Quickstart for using chat completion configuration in a .NET app ...app-configuration/quickstart-chat-completion-dotnet.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias in the 'Build and run the app' section, where Windows command prompt and PowerShell instructions are listed before Linux/macOS equivalents. PowerShell is given its own example, and Windows-specific tools (setx) are mentioned first. However, Linux/macOS instructions are present and the overall guide is cross-platform for .NET.
Recommendations
  • Present environment variable instructions in a neutral order (e.g., Linux/macOS first, or group all OSes together).
  • Explicitly state that all .NET CLI commands work on Windows, Linux, and macOS.
  • Add a table or grouped section for setting environment variables across platforms to avoid implicit prioritization.
  • Where possible, avoid Windows-specific tools (like setx) in favor of cross-platform approaches, or clarify their scope.
  • Consider adding troubleshooting notes for Linux/macOS users (e.g., shell session persistence for environment variables).
GitHub Create Pull Request
Azure App Configuration Quickstart for adding feature flags to JavaScript apps ...pp-configuration/quickstart-feature-flag-javascript.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation demonstrates Windows bias by listing Windows command prompt and PowerShell instructions before Linux/macOS equivalents when setting environment variables. It also provides explicit PowerShell commands, while Linux/macOS instructions are grouped together and presented last. The prerequisites section references installing Node.js 'directly on Windows or using WSL' before mentioning Linux, reinforcing a Windows-centric perspective.
Recommendations
  • Alternate the order of platform instructions so that Linux/macOS examples are sometimes listed first.
  • Provide parity in detail and explanation for Linux/macOS commands, matching the attention given to Windows and PowerShell.
  • In prerequisites, mention Linux/macOS installation options before or alongside Windows, rather than after.
  • Consider adding screenshots or CLI instructions that are platform-neutral or include Linux/macOS visuals.
  • Explicitly state that all steps work equally on Linux/macOS, and highlight any platform-specific caveats if they exist.
GitHub Create Pull Request
Azure App Configuration Using Azure App Configuration in JavaScript apps with the Azure SDK for JavaScript | Microsoft Docs ...icles/azure-app-configuration/quickstart-javascript.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias in the 'Configure an environment variable' section, where Windows command prompt and PowerShell instructions are presented before Linux/macOS equivalents. PowerShell and Windows-specific tools (setx) are explicitly mentioned, while Linux/macOS instructions are grouped last. The Node.js installation prerequisite also references Windows and WSL before Linux, subtly prioritizing Windows environments.
Recommendations
  • Present Linux/macOS and Windows instructions side-by-side or in parallel tabs, rather than listing Windows first.
  • Avoid language that suggests Windows is the default or primary platform (e.g., 'installing Node.js either directly on Windows or using WSL'). Instead, mention all platforms equally.
  • Where possible, use cross-platform commands (e.g., 'export' for environment variables) in main examples, and provide platform-specific notes as needed.
  • Include explicit instructions for Linux package managers (apt, yum, etc.) for Node.js installation, not just links.
  • Consider providing a table or tabbed interface for environment variable setup, with equal prominence for Windows, macOS, and Linux.
GitHub Create Pull Request
Azure App Configuration Quickstart for Azure App Configuration with .NET | Microsoft Docs .../azure-app-configuration/quickstart-dotnet-core-app.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
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 examples, which may suggest a Windows-first and PowerShell-heavy bias. However, Linux/macOS instructions are present and parity is generally good for .NET CLI usage.
Recommendations
  • Present environment variable instructions for Linux/macOS before or alongside Windows examples, rather than after.
  • Consider grouping all environment variable instructions together, using tabs or clear headings for each OS, to avoid implicit prioritization.
  • Add explicit statements highlighting cross-platform compatibility and encourage users on all platforms.
  • Where possible, provide parity in screenshots (e.g., show Linux/macOS terminal output as well as Windows).
GitHub Create Pull Request
← Previous Page 8 of 19 Next →