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 151-175 of 474 flagged pages
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
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 equivalent. Windows-specific tools (setx, PowerShell) are described first, with Linux/macOS only mentioned afterward. There is no exclusive use of Windows tools, but the ordering and detail favor Windows users.
Recommendations
  • Present Linux/macOS and Windows instructions in parallel or in a neutral order (e.g., Linux/macOS first, or side-by-side).
  • Provide equal detail for Linux/macOS commands and troubleshooting steps.
  • Avoid implying Windows is the default or primary platform by listing all OS options together.
  • Consider using cross-platform environment variable setting instructions (e.g., via .env files or Go code) where possible.
GitHub Create Pull Request
Azure App Configuration Integrate Azure App Configuration with Kubernetes Deployment using Helm ...-configuration/integrate-kubernetes-deployment-helm.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides a PowerShell example for passing secrets to Helm, without a corresponding Linux/bash example. The use of PowerShell syntax and cmdlets (e.g., ConvertFrom-Json, foreach) is Windows-centric and may not be directly usable by Linux or macOS users. This PowerShell example appears before any Linux alternative, and no bash or shell script equivalent is provided.
Recommendations
  • Add a bash/Linux shell example for the 'helm upgrade --set' workflow, using jq or similar tools to process JSON output from Azure CLI.
  • Explicitly mention cross-platform compatibility for CLI commands and provide alternatives for both Windows and Linux/macOS users.
  • Where PowerShell is used, provide a side-by-side bash equivalent to ensure parity.
  • Review other sections for subtle Windows-first language or tool recommendations and ensure Linux tools are equally represented.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation demonstrates minor Windows bias in the section on setting environment variables: Windows Command Prompt and PowerShell instructions are presented before Linux/macOS equivalents. PowerShell is given a dedicated example, while the Linux/macOS example is brief and lacks detail. The rest of the documentation is platform-neutral, focusing on .NET CLI and C# code, which is cross-platform.
Recommendations
  • Present Linux/macOS instructions before or alongside Windows instructions, rather than after.
  • Provide more detailed Linux/macOS instructions, including troubleshooting tips (e.g., how to persist environment variables across sessions).
  • Include a note clarifying that all .NET CLI commands and code samples work identically on Linux, macOS, and Windows.
  • Consider grouping environment variable instructions by platform in a table or side-by-side format for parity.
  • Add links to official documentation for setting environment variables on Linux/macOS.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias in the 'Run the application' section, where Windows command prompt and PowerShell instructions are presented before Linux/macOS equivalents. Windows-specific tools (setx, PowerShell) are mentioned explicitly, while Linux/macOS instructions are grouped together and provided after the Windows examples. The Node.js installation guidance also references Windows and WSL before other platforms.
Recommendations
  • Present platform instructions in parallel tabs or in a consistent order (e.g., alphabetical: Linux/macOS, PowerShell, Windows CMD) to avoid prioritizing Windows.
  • Explicitly mention Linux and macOS tools and patterns where relevant, and ensure parity in detail and clarity.
  • In prerequisite sections, provide installation instructions for Node.js on Linux/macOS with equal prominence as Windows.
  • Consider using generic cross-platform instructions first, or highlight that all platforms are equally supported.
  • Review for any other subtle prioritization of Windows terminology or tooling, and balance with Linux/macOS equivalents.
GitHub Create Pull Request
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 →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page exhibits mild Windows bias in the 'Prerequisites' and environment variable setup sections. The Python installation guidance links only to Windows documentation, and instructions for setting environment variables list Windows Command Prompt and PowerShell before macOS/Linux, with more detailed steps for Windows (e.g., restart prompt for setx). No Linux-specific installation or troubleshooting guidance is provided.
Recommendations
  • In the prerequisites, add links to Python installation guides for Linux and macOS alongside the Windows documentation.
  • When describing environment variable setup, present all platforms in parallel (e.g., a table or side-by-side tabs) or alternate the order to avoid always listing Windows first.
  • Include any platform-specific notes for Linux/macOS users, such as common locations for Python installations, shell differences, or troubleshooting tips.
  • Ensure parity in detail and clarity for Linux/macOS instructions, matching the specificity given to Windows users (e.g., mention shell session persistence for export commands).
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-12 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, especially in the 'Run the application' section, where Windows command prompt and PowerShell instructions are presented before Linux/macOS equivalents. PowerShell and Windows-specific tools (setx) are given prominent placement, while Linux/macOS instructions are listed last. The prerequisite section also references Windows and WSL before Linux. All code samples themselves are cross-platform, but the environment setup guidance prioritizes Windows users.
Recommendations
  • Present environment variable instructions for Linux/macOS first, or in parallel with Windows, to avoid implying Windows is the default platform.
  • In the prerequisites, provide direct links or instructions for installing Node.js on Linux/macOS, not just Windows/WSL.
  • Use tabbed or side-by-side formatting for platform-specific commands to emphasize parity.
  • Explicitly state that all code samples are cross-platform and runnable on Linux/macOS as well as Windows.
  • Consider including a note about differences in environment variable persistence between platforms (e.g., setx vs. export).
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-12 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, Windows tools and patterns are mentioned first and in more detail, which may subtly prioritize Windows users.
Recommendations
  • Present Linux/macOS and Windows instructions side-by-side or in parallel tabs, rather than listing Windows first.
  • Avoid giving Windows-specific tools (e.g., setx, PowerShell) precedence; consider grouping all OS instructions equally.
  • Add clarifying notes about differences in environment variable persistence (e.g., setx vs export), especially for Linux users.
  • Consider providing a cross-platform script or guidance for setting environment variables, or refer to OS documentation for details.
  • Explicitly mention that all Go code and Azure CLI commands are cross-platform, and highlight any OS-specific caveats.
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-12 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, particularly in the 'Configure an environment variable' section. Windows command prompt and PowerShell instructions are listed before Linux/macOS equivalents, and PowerShell is given its own example. The Node.js installation instructions reference Windows and WSL before Linux, and links for getting started with Node.js are Windows-centric. However, Linux/macOS commands are present and correct, and most code samples are platform-agnostic.
Recommendations
  • Present Linux/macOS instructions before or alongside Windows instructions, rather than after.
  • Provide links for installing Node.js on Linux/macOS, not just Windows.
  • Avoid giving Windows-specific tools (PowerShell, setx) precedence over cross-platform or Linux-native methods.
  • Consider grouping environment variable instructions by platform, or using tabs for Windows, macOS, and Linux equally.
  • Explicitly state that all code samples work on Linux/macOS as well as Windows.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation displays 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 code samples are platform-neutral.
Recommendations
  • Provide links for Python installation on Linux and macOS alongside the Windows documentation link in the prerequisites.
  • List environment variable commands for Linux/macOS before or alongside Windows/PowerShell, or present all platforms in a tabbed or side-by-side format for parity.
  • Explicitly state that the instructions and code samples work equally well on Linux/macOS, not just Windows.
  • Consider adding troubleshooting notes or tips for Linux/macOS users, if there are platform-specific caveats.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
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 Windows-first ordering, but the lack of Linux examples may make the documentation less accessible to users running pipelines on Linux agents.
Recommendations
  • Add a Bash example showing how to access pipeline variables as environment variables (e.g., echo "$myBuildSetting").
  • Explicitly mention that the export task works on both Windows and Linux agents, and clarify any platform-specific considerations if relevant.
  • Where PowerShell is referenced, provide equivalent Bash or shell script snippets alongside.
  • Review screenshots and UI instructions to ensure they are not Windows-specific, or add notes for Linux users if differences exist.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation demonstrates a Windows bias in the section about setting environment variables. Windows (cmd) and PowerShell instructions are given before the Linux/macOS equivalent, and both Windows shells are mentioned explicitly. The Linux/macOS example is present, but appears last, suggesting a prioritization of Windows environments.
Recommendations
  • Present environment variable instructions in parallel (side-by-side) for Windows and Linux/macOS, or list Linux/macOS first to balance representation.
  • Explicitly mention cross-platform compatibility throughout, and avoid grouping Windows instructions before Linux/macOS unless there is a technical reason.
  • Consider using tabbed or collapsible sections for OS-specific instructions to improve clarity and parity.
  • Review other sections for similar ordering or emphasis and ensure equal treatment of Linux/macOS and Windows.
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-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 explicit PowerShell examples. While Linux/macOS commands are present, Windows instructions are prioritized and more detailed (e.g., mentioning restart of command prompt for setx). No Linux-specific tools or patterns are discussed, but the ordering and detail favor Windows users.
Recommendations
  • Present Linux/macOS and Windows instructions in parallel or in a tabbed format, rather than listing Windows first.
  • Provide equal detail for Linux/macOS instructions (e.g., mention shell session persistence for export).
  • Consider adding troubleshooting notes relevant to Linux/macOS users (e.g., shell differences, permissions).
  • If mentioning Windows-specific behaviors (like setx requiring restart), also mention any Linux/macOS equivalents (such as session persistence or profile updates).
GitHub Create Pull Request
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 →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias in the 'Prerequisites' and environment variable setup sections. The link for Python setup is Windows-specific, and instructions for setting environment variables present Windows command prompt and PowerShell commands before Linux/macOS equivalents. Windows tools (setx, PowerShell) are mentioned explicitly and given priority in ordering.
Recommendations
  • In the prerequisites, provide links for setting up Python on Linux and macOS alongside the Windows documentation.
  • When presenting environment variable setup instructions, list Linux/macOS commands first or present all platforms in parallel (e.g., in a table or side-by-side tabs).
  • Mention cross-platform tools and patterns (e.g., using .env files, python-dotenv) for environment variable management.
  • Ensure that all examples and instructions are equally accessible to Linux/macOS users, avoiding implicit prioritization of Windows tools.
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-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, primarily in the 'Configure an environment variable' section. Windows command prompt and PowerShell instructions are presented before Linux/macOS equivalents, and PowerShell is called out specifically. The initial Node.js installation guidance references Windows and WSL before mentioning Linux. However, Linux/macOS instructions are present and correct, and the main code samples are platform-agnostic.
Recommendations
  • Present environment variable instructions in a neutral order (e.g., Linux/macOS first, or group all OS instructions together without prioritization).
  • Avoid calling out Windows/PowerShell instructions before Linux equivalents; consider parallel presentation or tabs.
  • Include explicit Linux installation guidance for Node.js, not just referencing WSL.
  • Where possible, use generic shell commands (e.g., 'export') as the primary example, with OS-specific alternatives in expandable sections.
  • Review other sections for subtle prioritization of Windows tools or terminology and ensure parity in Linux/macOS references.
GitHub Create Pull Request
Azure App Configuration Azure App Configuration preview API life cycle ...re-app-configuration/concept-preview-api-life-cycle.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 both Bash and PowerShell examples for checking API versions, but PowerShell is presented as a primary tab alongside Bash, which may indicate a slight Windows-first bias. There are no Linux-specific tools or patterns mentioned, and the CLI examples are generic. No exclusive Windows tools are referenced, but the inclusion of PowerShell may suggest a preference for Windows environments.
Recommendations
  • Ensure Bash examples are presented first, as Bash is more universally available across platforms.
  • Include explicit notes that Bash commands work on Linux/macOS and PowerShell commands work on Windows, to clarify cross-platform usage.
  • Consider adding Linux-specific troubleshooting tips or references to common Linux shells (e.g., zsh, fish) if relevant.
  • If PowerShell is included, mention PowerShell Core compatibility on Linux/macOS to avoid implying Windows exclusivity.
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-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, especially in the 'Build and run the app locally' section. Windows tools (Command Prompt, PowerShell, Visual Studio) are mentioned before Linux/macOS equivalents, and instructions for setting environment variables use Windows commands first, with PowerShell examples given more prominence. The tutorial is centered around .NET Framework, which is primarily a Windows technology, but Linux/macOS instructions are provided for environment variables. Visual Studio is listed as a prerequisite, with no mention of cross-platform alternatives.
Recommendations
  • Present Linux/macOS instructions alongside or before Windows instructions, rather than after.
  • Include cross-platform development tool options (e.g., Visual Studio Code, JetBrains Rider) in prerequisites.
  • Clarify that .NET Framework is Windows-only, and provide links or guidance for .NET (Core/5+) users on Linux/macOS.
  • Where possible, provide parity in screenshots and terminal output for Linux/macOS.
  • Avoid assuming Visual Studio as the only IDE; offer CLI-based project creation and build instructions for users on non-Windows platforms.
GitHub Create Pull Request
Azure App Configuration Use dynamic configuration using push refresh - Java Spring ...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/enable-dynamic-configuration-java-spring-push-refresh.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 detailed Windows-specific commands (setx, PowerShell) alongside bash. There is a slight preference for Windows tools and ordering, but Linux/macOS equivalents are present and not omitted.
Recommendations
  • Present environment variable instructions in a neutral order, or alternate which OS is listed first (e.g., Linux/macOS, then Windows, then PowerShell).
  • Use collapsible tabs or sections for each OS to avoid implying priority.
  • Explicitly state that all steps are cross-platform unless otherwise noted.
  • Where possible, use platform-agnostic commands or highlight cross-platform tools (e.g., recommend using Visual Studio Code, which is already done).
  • Ensure that any screenshots or UI references are not Windows-specific unless necessary.
GitHub Create Pull Request
Azure App Configuration Configuration Provider Overview ...e-app-configuration/configuration-provider-overview.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows/.NET-first bias by listing .NET-based providers (Microsoft.Extensions.Configuration.AzureAppConfiguration, ASP.NET Core, Azure Functions, .NET Framework) before other language providers, and by only providing sample links for .NET Framework that reference Windows-centric technologies (WebDemo). There are no explicit Linux or cross-platform shell examples, nor are Linux-specific tools or patterns mentioned. The documentation does not provide parity in example visibility or ordering for Linux or non-Windows platforms.
Recommendations
  • Add explicit Linux usage examples for each provider, especially for .NET (e.g., running on Ubuntu, using systemd, or configuring with environment variables).
  • Include cross-platform sample links and clarify that .NET Core and .NET Standard providers work on Linux and macOS as well as Windows.
  • Balance the ordering of provider listings so that non-Windows platforms (Java, Python, Go, JavaScript) are not always listed after .NET/Windows-centric options.
  • Where relevant, mention Linux-native configuration patterns (such as environment variables, config files in /etc) alongside Windows patterns.
  • If PowerShell or Windows-specific tools are referenced elsewhere, add equivalent Bash or Linux CLI examples.
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-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 references Visual Studio and Windows-specific tooling (e.g., setx, F5 to run in Visual Studio) without mentioning equivalent Linux workflows (such as VS Code, Azure Functions Core Tools CLI, or dotnet CLI). PowerShell and Windows command prompt examples are given more prominently, and Linux instructions are always listed last.
Recommendations
  • Present Linux/macOS (bash) instructions before or alongside Windows examples, not always after.
  • Include instructions for running and debugging Azure Functions locally using cross-platform tools (e.g., VS Code, Azure Functions Core Tools CLI, dotnet CLI), not only Visual Studio.
  • Mention Linux/macOS-specific considerations for local development, such as file permissions, shell differences, and alternative editors.
  • Add screenshots or terminal output examples from Linux/macOS environments.
  • Ensure parity in troubleshooting and setup steps for Linux/macOS users, including firewall and tool installation guidance.
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-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 Command Prompt and PowerShell before mentioning the macOS/Linux equivalent. Windows-specific tools (setx, PowerShell) are described in detail, while Linux/macOS instructions are given last and more briefly. There are no Linux-specific troubleshooting tips or parity notes.
Recommendations
  • Present environment variable instructions for all platforms together, or start with a neutral (cross-platform) method.
  • Include Linux/macOS instructions before or alongside Windows instructions, not after.
  • Add troubleshooting notes or tips for Linux/macOS users (e.g., persistence of environment variables, shell differences).
  • Consider using platform-agnostic tools or scripts (e.g., .env files, Python-dotenv) for environment variable management.
  • Explicitly state that all platforms are supported and tested, and provide parity in examples and screenshots where relevant.
GitHub Create Pull Request
Azure App Configuration Roll out features to targeted audiences in a Node.js app ...-app-configuration/howto-targetingfilter-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 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, with Linux/macOS presented last and more briefly. No Linux-specific tools or patterns are discussed elsewhere, 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 commands, including notes about shell persistence (e.g., .bashrc/.zshrc).
  • Consider grouping environment variable instructions by OS in a table or side-by-side format for parity.
  • Explicitly mention that all examples and code are cross-platform unless otherwise noted.
  • Add troubleshooting notes for common Linux/macOS issues, such as permissions or shell differences.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides instructions for setting the AZURE_APPCONFIG_ENDPOINT environment variable, listing Windows Command Prompt and PowerShell methods before the Linux/macOS equivalent. Windows-specific tools (setx, PowerShell) are mentioned and shown in detail, with Linux/macOS instructions appearing last and without additional context. No Linux-specific tools or troubleshooting are discussed.
Recommendations
  • Present environment variable instructions in a neutral order (e.g., Linux/macOS first, or grouped together).
  • Provide equal detail for Linux/macOS, such as mentioning shell persistence (e.g., adding to ~/.bashrc or ~/.zshrc).
  • Include troubleshooting tips for all platforms (e.g., how to verify the variable is set).
  • Avoid Windows-centric phrasing such as 'If you use the Windows command prompt...' by using 'On Windows...', 'On Linux/macOS...', etc.
  • Consider adding platform-agnostic instructions (e.g., using cross-env for npm scripts).
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-11 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 all command-line operations, but PowerShell is given equal prominence to CLI, and is presented as a first-class option throughout. This can be interpreted as a Windows bias, since PowerShell is primarily a Windows tool (though it is available cross-platform), and many Linux users would expect Bash or shell scripting examples. There are no explicit Linux-specific instructions, nor is there mention of Linux tools or shell environments. The Azure CLI examples are cross-platform, but the documentation does not clarify this, nor does it provide any Linux-specific guidance or troubleshooting.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and are recommended for cross-platform usage.
  • Add a note clarifying that PowerShell examples are primarily for Windows users, while CLI examples are suitable for Linux/macOS.
  • Consider providing Bash script examples for automation on Linux.
  • Add troubleshooting notes or links for common issues encountered on Linux (e.g., installation of Azure CLI, file permissions).
  • Ensure that any references to command-line tools do not assume a Windows environment by default.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation demonstrates mild Windows bias in the 'Build and run the app' section, where Windows command prompt and PowerShell instructions for setting environment variables are presented before Linux/macOS equivalents. The use of PowerShell and Windows-specific commands is more detailed, while Linux/macOS instructions are brief and placed after Windows examples. The rest of the documentation is platform-neutral, focusing on .NET CLI and C# code, which are cross-platform.
Recommendations
  • Present Linux/macOS instructions before or alongside Windows instructions to avoid implicit prioritization.
  • Provide equal detail and explanation for Linux/macOS commands as given for Windows/PowerShell.
  • Explicitly state that all .NET CLI and code samples work identically on Linux, macOS, and Windows.
  • Consider grouping environment variable instructions in a table or side-by-side format for parity.
  • Add troubleshooting notes for common platform-specific issues (e.g., environment variable persistence on Linux shells).
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-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides platform-specific instructions for setting environment variables, listing Windows Command Prompt and PowerShell methods before the Linux/macOS equivalent. This ordering may suggest a Windows-first bias. Additionally, both Windows and PowerShell commands are given, which can be considered 'powershell_heavy' if Linux alternatives are not equally emphasized. However, the main Go application code and build/run instructions are platform-neutral and use Bash commands, which are standard across Linux and macOS.
Recommendations
  • Present Linux/macOS instructions before or alongside Windows instructions to avoid implicit prioritization.
  • Explicitly state that the Go application and its dependencies work equally well on Linux, macOS, and Windows.
  • Include a note that all commands are cross-platform unless otherwise specified.
  • Provide parity in troubleshooting or environment setup examples for Linux/macOS (e.g., handling environment variables in systemd or .bashrc).
  • Consider grouping platform-specific instructions under clear subheadings (e.g., 'Windows', 'Linux/macOS') for clarity and equal prominence.
GitHub Create Pull Request
← Previous Page 7 of 19 Next →