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 126-150 of 474 flagged pages
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-13 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/macOS shells. This creates friction for users running pipelines on Linux or macOS agents, as they must infer how to access environment variables in their platform's scripting language.
Recommendations
  • Add Bash and/or sh examples alongside the PowerShell example to demonstrate how Linux/macOS users can access pipeline variables (e.g., echo "$myBuildSetting").
  • Explicitly mention that environment variables are available in all supported agent platforms and provide cross-platform guidance.
  • Review other sections for any implicit Windows-first assumptions and clarify when instructions are platform-agnostic.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. Visual Studio is listed as the only IDE in prerequisites, and Windows-specific tools (Command Prompt, PowerShell) are mentioned first when setting environment variables, with Linux/macOS commands provided after. The build/run instructions assume Visual Studio and do not mention cross-platform alternatives. All code examples are platform-neutral, but the workflow and tooling references favor Windows.
Recommendations
  • List cross-platform IDEs (e.g., VS Code, JetBrains Rider) alongside Visual Studio in prerequisites.
  • Present environment variable commands for Linux/macOS before or alongside Windows commands, not after.
  • Include instructions for building and running the app using .NET CLI (dotnet build/run) for Linux/macOS users.
  • Clarify that the .NET Framework app can be run on Windows only, but .NET Core/.NET apps can be run cross-platform, and link to relevant tutorials for those platforms.
  • Add screenshots or terminal output examples for Linux/macOS environments.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides environment variable setup instructions for Windows Command Prompt and PowerShell before mentioning Linux/macOS equivalents. Windows-specific commands (setx, PowerShell syntax) are shown first and in more detail, while Linux/macOS commands are listed after. There is also a curl example shown only with Windows Command Prompt syntax, and no Linux/macOS terminal screenshots or explicit parity in deployment instructions.
Recommendations
  • Present environment variable instructions for Linux/macOS and Windows side-by-side, or in separate tabs, to avoid Windows-first ordering.
  • Include Linux/macOS terminal screenshots or explicit instructions for Maven deployment and curl usage.
  • Ensure all command examples (curl, Maven, etc.) are shown for both Windows and Linux/macOS shells.
  • Add notes or troubleshooting tips specific to Linux/macOS environments, such as file permission issues or path differences.
  • Review all sections for implicit Windows tool references and provide Linux/macOS alternatives where relevant.
GitHub Create Pull Request
Azure App Configuration Use variant feature flags in a Python application ...pp-configuration/howto-variant-feature-flags-python.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page shows a Windows bias in several areas. In the prerequisites, only Windows-specific Python setup documentation is linked, with no mention of Linux or macOS equivalents. When describing how to activate the Python virtual environment, only the Windows command is provided ('.\venv\Scripts\Activate'), omitting the Linux/macOS alternative ('source venv/bin/activate'). In the section on setting environment variables, Windows methods (cmd and PowerShell) are listed before the Linux/macOS method, but all are present. Overall, Linux/macOS users may experience minor friction due to missing or less prominent examples.
Recommendations
  • In the prerequisites, add links or instructions for setting up Python on Linux and macOS.
  • When showing how to activate the virtual environment, provide both Windows ('.\venv\Scripts\Activate') and Linux/macOS ('source venv/bin/activate') commands.
  • Consider presenting environment variable instructions for all platforms together, or listing Linux/macOS first in cross-platform documentation.
  • Review other steps for implicit Windows assumptions and clarify where behavior differs on Linux/macOS.
GitHub Create Pull Request
Azure App Configuration Monitor Azure App Configuration ...s/azure-app-configuration/monitor-app-configuration.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. In several places, Windows-specific tools (PowerShell) are highlighted, and instructions often refer to opening 'Windows PowerShell' or a 'command console application such as Windows PowerShell' before mentioning cross-platform alternatives. There are no explicit Linux/macOS-specific instructions or screenshots, and the PowerShell section assumes a Windows environment. The CLI section does mention 'Azure Cloud Shell' (which is cross-platform), but also references Windows PowerShell as the local example. There are no Linux/macOS terminal examples or notes about differences for those platforms.
Recommendations
  • In CLI instructions, mention Linux/macOS terminal explicitly alongside Windows PowerShell, e.g., 'open a terminal (Windows PowerShell, Command Prompt, or Linux/macOS Terminal)'.
  • For PowerShell, clarify that Azure PowerShell is available on Linux/macOS and provide installation/use instructions or a note.
  • Add screenshots or notes that reflect cross-platform usage, not just Windows.
  • Where possible, provide Bash (or sh) script equivalents for PowerShell commands, or clarify that the Azure CLI commands work identically on all platforms.
  • Avoid using 'Windows PowerShell' as the default term; use 'PowerShell' and clarify cross-platform compatibility.
  • Explicitly state that all Azure CLI commands are cross-platform and can be run on Linux/macOS terminals.
GitHub Create Pull Request
Azure App Configuration Quickstart for Azure App Configuration with .NET Framework ...icles/azure-app-configuration/quickstart-dotnet-app.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation is notably Windows-centric, with prerequisites and instructions focused on Visual Studio and .NET Framework (both Windows-only). Steps for setting environment variables list Windows Command Prompt and PowerShell examples first, with Linux/macOS bash commands mentioned last. The use of Visual Studio as the only development environment further reinforces Windows bias. There are no Linux/macOS-specific development instructions or alternatives for cross-platform .NET development.
Recommendations
  • Add instructions for using cross-platform .NET tools (e.g., .NET Core/SDK, VS Code) for Linux/macOS users.
  • Provide Linux/macOS development environment setup steps, including alternative IDEs and build/run commands.
  • Present environment variable setting examples for bash/zsh first or equally alongside Windows commands.
  • Clarify that .NET Framework is Windows-only and suggest .NET (Core/5+) for cross-platform scenarios.
  • Include troubleshooting notes for Linux/macOS users, especially regarding compatibility and environment setup.
GitHub Create Pull Request
Azure App Configuration Quickstart for Azure App Configuration with Azure Functions | Microsoft Docs ...app-configuration/quickstart-azure-functions-csharp.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific tools (Visual Studio) are required for the main workflow, and Windows environment variable instructions (cmd, PowerShell) are presented before Linux/macOS equivalents. The workflow is tightly coupled to Visual Studio, with little mention of cross-platform alternatives like VS Code or Azure Functions Core Tools CLI. Linux/macOS instructions are present but secondary.
Recommendations
  • Add instructions for creating and running Azure Functions apps using cross-platform tools such as VS Code and Azure Functions Core Tools CLI.
  • Present environment variable setting instructions for Linux/macOS before or alongside Windows examples, not after.
  • Explicitly mention that the workflow can be completed on Linux/macOS, and provide links to relevant setup guides.
  • Include screenshots and debugging steps for non-Windows environments.
  • Clarify any platform-specific limitations or differences in the quickstart.
GitHub Create Pull Request
Azure App Configuration Quickstart for adding feature flags to Azure Functions | Microsoft Docs ...tion/quickstart-feature-flag-azure-functions-csharp.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Visual Studio Heavy Powershell Heavy Missing Linux Editor Example
Summary
The documentation displays a moderate Windows bias. Visual Studio (Windows-centric) is the only development environment mentioned, with no alternatives for Linux/macOS (such as VS Code or CLI workflows). Instructions for setting environment variables list Windows command prompt and PowerShell first, with Linux/macOS bash commands last. All screenshots and workflow steps assume Visual Studio, which is not natively available on Linux. There are no examples or guidance for Linux/macOS users regarding project creation, debugging, or running Azure Functions locally outside Visual Studio.
Recommendations
  • Add instructions for creating and running Azure Functions using VS Code and Azure Functions Core Tools CLI, which are cross-platform.
  • Provide Linux/macOS-specific setup and debugging steps, including terminal commands for starting and debugging the function.
  • Include screenshots or workflow descriptions for non-Visual Studio environments.
  • List Linux/macOS commands before or alongside Windows commands to avoid Windows-first ordering.
  • Explicitly mention cross-platform support and alternatives to Visual Studio for non-Windows users.
GitHub Create Pull Request
Azure App Configuration Quickstart for Adding Feature Flags to .NET/.NET Framework Apps ...re-app-configuration/quickstart-feature-flag-dotnet.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a notable Windows bias. All environment variable setup instructions are provided only for Windows Command Prompt and PowerShell, with no mention of Linux/macOS equivalents (such as bash or zsh). Visual Studio is referenced as the sole development environment, which is primarily a Windows tool, and screenshots show Windows terminals. There are no instructions or examples for Linux or macOS users, making it harder for them to follow the quickstart.
Recommendations
  • Add equivalent environment variable setup commands for Linux/macOS shells (e.g., export Endpoint="..." for bash/zsh).
  • Mention cross-platform IDEs such as Visual Studio Code, and provide instructions for creating and running .NET console apps using the dotnet CLI.
  • Include screenshots or terminal output examples from Linux/macOS environments.
  • Clarify that the .NET SDK and libraries are cross-platform, and provide steps for non-Windows users.
  • Reorder or parallelize instructions so Windows and Linux/macOS users see their relevant commands/examples side-by-side.
GitHub Create Pull Request
Azure App Configuration Create an Azure App Configuration store by using Azure Resource Manager template (ARM template) ...azure-app-configuration/quickstart-resource-manager.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides deployment instructions using PowerShell cmdlets only, with no equivalent examples for Linux/macOS users (e.g., Azure CLI or Bash). The use of PowerShell is a Windows-centric approach, and there is no mention of Linux shell or cross-platform alternatives for deploying the ARM template or cleaning up resources.
Recommendations
  • Add Azure CLI examples for deploying the ARM template and cleaning up resources, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Present Azure CLI and PowerShell examples side-by-side, or at least mention both options, to improve parity.
  • Explicitly state that PowerShell is available cross-platform, but recommend Azure CLI for Linux/macOS users.
  • Include Bash script snippets for common operations where appropriate.
GitHub Create Pull Request
Azure App Configuration Tutorial for using Azure App Configuration Key Vault references in a Java Spring Boot app | Microsoft Docs ...-configuration/use-key-vault-references-spring-boot.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page presents Windows-specific environment variable setup commands (setx, PowerShell) before Linux/macOS equivalents, and uses Windows terminology (command prompt, restart the command prompt) without mentioning Linux shells. The Linux/macOS export command is shown after Windows examples, and lacks details about shell persistence. There are no Linux-specific screenshots or portal instructions, and the cleanup section is not platform-specific. Most CLI examples use Azure CLI, which is cross-platform, but the environment variable setup is Windows-centric.
Recommendations
  • Present Linux/macOS environment variable setup commands before or alongside Windows commands, with equal detail.
  • Clarify shell-specific instructions for Linux/macOS (e.g., mention .bashrc/.zshrc for persistence, restarting the shell).
  • Use neutral terminology like 'terminal' instead of 'command prompt', and clarify instructions for different platforms.
  • Add Linux/macOS screenshots or notes where portal UI may differ.
  • Ensure all steps are equally clear for Linux/macOS users, especially around authentication and environment setup.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation shows a moderate Windows bias. In the prerequisites, it links only to Windows-specific Python installation documentation, omitting Linux/macOS equivalents. When setting environment variables, Windows command prompt and PowerShell instructions are always listed before Linux/macOS, and the Windows 'setx' command is given special mention (including a note about restarting the prompt), while Linux/macOS instructions are more generic. There are no Linux/macOS-specific troubleshooting notes or links to their Python setup guides.
Recommendations
  • Include links to official Python installation/setup documentation for Linux and macOS in the prerequisites section.
  • Alternate the order of environment variable instructions, or present all OS instructions in parallel tabs or a table to avoid prioritizing Windows.
  • Add Linux/macOS-specific notes where relevant (e.g., about persistent environment variables, shell differences).
  • Ensure that all CLI and setup instructions are equally detailed for Linux/macOS users.
  • Consider using OS-neutral language and examples where possible.
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-12 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 Linux shell environments (e.g., Bash). This may make it less accessible for users running pipelines on Linux agents or those more familiar with Bash scripting.
Recommendations
  • Add Bash (Linux shell) examples alongside PowerShell examples to demonstrate how to consume pipeline variables in cross-platform scenarios.
  • Explicitly mention that environment variables are accessible in both Windows and Linux agents, and provide syntax for both.
  • Review other sections for implicit Windows-first language or screenshots, and ensure parity in instructions for Linux users 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-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 (bash), and gives detailed Windows-specific commands (setx, PowerShell) alongside bash equivalents. There is a slight preference for Windows in ordering and detail, but Linux/macOS instructions are present and correct.
Recommendations
  • Present Linux/macOS instructions before Windows instructions, or in parallel, to avoid implicit prioritization.
  • Add notes about differences in environment variable persistence (e.g., setx vs export) and session scope for all platforms.
  • Ensure parity in troubleshooting and tips for both Windows and Linux/macOS users.
  • Consider grouping platform-specific instructions in tabs or collapsible sections for clarity and equal prominence.
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-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 command prompt and PowerShell before mentioning macOS/Linux equivalents. Windows-specific tools (setx, PowerShell) are described in detail, with Linux/macOS commands listed last. However, the .NET CLI is emphasized as cross-platform, and most code examples are platform-neutral.
Recommendations
  • Present environment variable instructions for all platforms in parallel, or list Linux/macOS first in some sections.
  • Explicitly state that all CLI commands work on Windows, macOS, and Linux.
  • Provide brief context for each platform's command, avoiding implicit prioritization of Windows.
  • Consider grouping platform instructions in tabs or side-by-side tables for parity.
  • Mention Linux/macOS terminal options (e.g., bash, zsh) alongside Windows shells.
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-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 (bash), and includes explicit PowerShell examples. While Linux/macOS commands are present, Windows instructions are listed first, which may subtly prioritize Windows users. No Linux-specific tools or patterns are missing, but the ordering and inclusion of PowerShell examples indicate a mild Windows bias.
Recommendations
  • Present Linux/macOS (bash) commands before Windows commands, or group them equally under OS-specific tabs.
  • Ensure parity in command examples for all platforms, including zsh or other common Linux shells if relevant.
  • Add a note clarifying that all platforms are supported equally.
  • Consider using tabbed code blocks for OS-specific instructions to avoid implicit prioritization.
  • Review other sections for subtle prioritization (e.g., screenshots, tool recommendations) and ensure balanced representation.
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-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 (bash), and references Visual Studio and Windows-specific tooling (e.g., setx, F5, firewall exceptions) as the default workflow for local testing. Linux/macOS instructions are present but appear after Windows examples, and there is no mention of Linux-native editors or CLI workflows.
Recommendations
  • Present Linux/macOS and Windows instructions in parallel, or alternate which platform is shown first.
  • Include examples for Linux-native development environments (e.g., VS Code, Azure Functions Core Tools CLI) and workflows.
  • Mention cross-platform tools and clarify that Azure Functions development and testing can be performed on Linux/macOS as well as Windows.
  • Avoid assuming Visual Studio as the default IDE; provide CLI-based testing instructions for parity.
  • Add notes about firewall exceptions and tool installation for Linux/macOS where relevant.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page exhibits a mild Windows bias. Windows tools (Visual Studio, Command Prompt, PowerShell) are mentioned first and in more detail, especially in the prerequisites and environment variable setup sections. PowerShell and Windows Command Prompt commands are given before Linux/macOS equivalents. The workflow assumes Visual Studio, which is primarily a Windows tool, and instructs users to restart Visual Studio after setting environment variables, which is not relevant for Linux users. However, Linux/macOS commands are present and not omitted.
Recommendations
  • Present environment variable setup instructions for Windows, Linux, and macOS in parallel, rather than listing Windows first.
  • Include instructions for building and running the app using cross-platform .NET CLI (dotnet build/run) in addition to Visual Studio.
  • Clarify that Visual Studio is optional and suggest alternatives for Linux/macOS users, such as VS Code or JetBrains Rider.
  • Avoid instructions that are only relevant for Windows (e.g., restarting Visual Studio) or provide Linux/macOS alternatives.
  • Add screenshots or terminal output examples for Linux/macOS environments alongside Windows 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-12 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 and samples before those for other platforms and languages. All sample links for .NET providers point to Windows-centric examples (e.g., DotNetCore, DotNetFramework/WebDemo), with no explicit mention or examples for Linux environments or Linux-specific usage patterns. There is no reference to Linux tools, shell commands, or cross-platform configuration scenarios. The documentation implicitly assumes a Windows development environment, especially in the .NET sections.
Recommendations
  • Add explicit Linux usage examples for .NET providers, such as running .NET Core applications on Linux, using Linux shell commands for configuration, and deploying to Linux containers.
  • Include cross-platform sample projects and instructions, highlighting both Windows and Linux environments.
  • Mention Linux equivalents (e.g., bash, systemd, environment variables) where Windows-specific tools or patterns are referenced.
  • Ensure that documentation for all languages/platforms includes parity in sample environments, not just Windows-centric ones.
  • Consider reordering the provider list or grouping by language rather than platform to avoid implicit prioritization of Windows/.NET.
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-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 (bash), and includes both Windows command prompt and PowerShell commands explicitly, with Linux/macOS instructions coming last. All platforms are covered, but the ordering and explicit mention of Windows tools first indicate a subtle Windows-first bias. There are no missing Linux examples or exclusive use of Windows tools, but the pattern prioritizes Windows users.
Recommendations
  • Present environment variable setup instructions in a platform-neutral order, or alternate the order between sections to avoid always listing Windows first.
  • Group platform-specific instructions in a tabbed or clearly separated format (e.g., tabs for Windows CMD, PowerShell, Linux/macOS Bash) to give equal prominence.
  • Explicitly state that all commands are cross-platform where possible, and avoid implying Windows is the default or primary platform.
  • Consider including screenshots or examples from Linux/macOS environments as well, not just Windows.
  • Review other sections for subtle prioritization of Windows tools or patterns and adjust for parity.
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-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 in Windows (cmd and PowerShell) before mentioning the Linux/macOS equivalent. Windows commands are listed first, and PowerShell is given its own example, which may suggest a bias towards Windows users. However, Linux/macOS instructions are present and correct.
Recommendations
  • Present environment variable instructions for all platforms together, or start with a neutral cross-platform approach (e.g., show Linux/macOS and Windows side by side).
  • Consider using a table or code tabs to allow users to select their OS, improving parity and discoverability.
  • Avoid listing Windows commands first by default; alternate the order or use alphabetical order.
  • Ensure that any platform-specific instructions are equally detailed and prominent for Linux/macOS.
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-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 syntax) are described in detail, while Linux/macOS is only briefly covered. The order and detail of examples favor Windows users.
Recommendations
  • Present Linux/macOS and Windows instructions in parallel, or start with Linux/macOS examples to balance audience expectations.
  • Provide equal detail for Linux/macOS commands (e.g., explain persistence of environment variables, mention .bashrc/.zshrc for permanent changes).
  • Avoid Windows-first ordering; consider grouping OS-specific instructions under clear subheadings.
  • Include troubleshooting notes for common issues on Linux/macOS (e.g., shell differences, permissions).
  • Ensure that all code and command examples are tested and validated on both platforms.
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-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 using Command Prompt and PowerShell before mentioning the equivalent Linux/macOS command. This ordering prioritizes Windows users and may give the impression that Windows is the primary or preferred platform. Additionally, both Windows Command Prompt and PowerShell examples are included, while only a single Linux/macOS example is given.
Recommendations
  • Present platform instructions in parallel (side-by-side or in a table) rather than listing Windows first.
  • Provide equal detail and visibility for Linux/macOS commands and workflows.
  • Explicitly state cross-platform compatibility and mention that all examples work on Linux/macOS unless otherwise noted.
  • Consider including Linux/macOS-specific troubleshooting tips or notes if relevant.
  • Avoid listing multiple Windows shell examples unless also providing equivalent alternatives for Linux/macOS (e.g., bash, zsh).
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-12 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 on setting environment variables: Windows Command Prompt and PowerShell instructions are listed before Linux/macOS, and both Windows shells are given explicit commands. While Linux/macOS instructions are present, Windows approaches are prioritized and described in more detail.
Recommendations
  • Present Linux/macOS instructions before or alongside Windows instructions, rather than after.
  • Use a tabbed or side-by-side format for environment variable setup, so users can easily find instructions for their OS.
  • Provide equal detail for Linux/macOS commands (e.g., mention shell persistence, profile files if relevant).
  • Consider referencing cross-platform tools (like dotenv or npm scripts) for environment variable management.
  • Avoid language that implies Windows is the default or primary platform.
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-12 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, but PowerShell (a Windows-centric tool) is given equal prominence to CLI, and is presented in parallel tabs throughout. There is no explicit mention of Linux or macOS environments, nor are there any platform-specific notes or troubleshooting for non-Windows users. The use of PowerShell may implicitly favor Windows users, as PowerShell is natively available on Windows and less commonly used on Linux/macOS. No Linux-specific tools or shell examples (e.g., Bash) are provided.
Recommendations
  • Add explicit notes clarifying that Azure CLI commands work on Windows, Linux, and macOS, and are recommended for cross-platform usage.
  • Consider listing Azure CLI examples before PowerShell examples, as CLI is more universally available.
  • Include troubleshooting or installation guidance for Azure CLI and PowerShell on Linux/macOS.
  • Add Bash shell examples for common tasks, or clarify that CLI commands can be run in Bash, zsh, etc.
  • Where PowerShell is mentioned, note that PowerShell Core is available cross-platform, but CLI is generally simpler for Linux/macOS users.
GitHub Create Pull Request
← Previous Page 6 of 19 Next →