Azure App Configuration

166
Total Pages
109
Linux-Friendly Pages
57
Pages with Bias
34.3%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

479 issues found
Showing 401-425 of 479 flagged pages
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
Low Priority View Details →
Scanned: 2026-01-14 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 on configuring environment variables, where Windows command prompt and PowerShell instructions are presented before Linux/macOS equivalents. The Linux/macOS instructions are present and correct, but Windows tooling (setx, PowerShell) is mentioned first and in more detail. The Node.js installation prerequisite also references Windows and WSL before Linux/macOS. No critical functionality is Windows-only, and all major steps are cross-platform.
Recommendations
  • Present Linux/macOS instructions before or alongside Windows instructions, especially for environment variable setup.
  • Add explicit parity checks for all CLI and environment variable steps to ensure Linux/macOS users are equally supported.
  • Reference cross-platform Node.js installation guides (not just Windows/WSL).
  • Consider grouping OS-specific instructions in tabs or side-by-side for equal visibility.
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
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation demonstrates mild Windows bias by referencing Windows-specific Python setup documentation in the prerequisites and listing Windows command prompt and PowerShell instructions before Linux/macOS equivalents when setting environment variables. However, all core code samples and instructions are cross-platform and include Linux/macOS guidance.
Recommendations
  • In the prerequisites, add links or instructions for setting up Python on Linux/macOS alongside the Windows link.
  • When presenting environment variable setup commands, consider listing Linux/macOS instructions first or presenting all platforms in parallel (e.g., in a table or side-by-side tabs).
  • Explicitly state that all code samples work on Linux/macOS, and encourage non-Windows users by referencing their platforms equally.
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
Low Priority View Details →
Scanned: 2026-01-14 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. However, Linux/macOS instructions are present and complete, and all other steps are platform-agnostic.
Recommendations
  • Present Linux/macOS (bash) environment variable instructions before or alongside Windows examples to avoid implicit prioritization.
  • Consider grouping all OS instructions in a tabbed format or a table for parity.
  • Add explicit notes that all steps work equally on Linux/macOS and Windows, except for environment variable syntax.
  • Minimize repetition of 'restart the command prompt' which is Windows-specific; clarify equivalent steps for Linux/macOS shells if needed.
GitHub Create Pull Request
Azure App Configuration Quickstart to learn how to use Azure App Configuration .../azure-app-configuration/quickstart-java-spring-app.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Minor Windows Tools
Summary
The documentation page demonstrates mild Windows bias in the 'Build and run the app locally' section, where Windows command examples (setx, PowerShell) are listed before Linux/macOS equivalents. The use of 'cmd' syntax and explicit mention of Windows tools occurs first, with Linux/macOS instructions provided afterwards. However, Linux/macOS users are not blocked from completing the quickstart, as all necessary commands are present.
Recommendations
  • Present environment variable instructions for Linux/macOS before or alongside Windows examples, rather than after.
  • Use neutral code block language tags (e.g., 'bash' or 'shell') for cross-platform commands like Maven and curl.
  • Clearly label each code block with the target OS (Windows CMD, PowerShell, Linux/macOS) for clarity.
  • Consider grouping OS-specific instructions together or using tabs for platform selection.
  • Ensure parity in tool recommendations and avoid defaulting to Windows-centric terminology (e.g., 'command prompt').
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
Low Priority View Details →
Scanned: 2026-01-14 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, and uses Windows-specific commands (setx, PowerShell syntax) with more detailed guidance. Linux/macOS instructions are present but appear after Windows, and lack some context (e.g., restart shell for export). The rest of the tutorial is platform-neutral, using Azure CLI and Java tools.
Recommendations
  • Present Linux/macOS and Windows instructions side-by-side or in parallel tabs, rather than listing Windows first.
  • Provide equal detail for Linux/macOS commands, including notes about shell persistence and session restarts.
  • Consider using cross-platform environment variable setup tools (e.g., .env files) where possible.
  • Clarify that Azure CLI and Maven commands work on all platforms.
  • Avoid implying Windows is the default by listing it first.
GitHub Create Pull Request
Azure App Configuration Use variant feature flags in a Node.js application ...onfiguration/howto-variant-feature-flags-javascript.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides instructions for setting environment variables on Windows (cmd and PowerShell) before mentioning the Linux/macOS equivalent, indicating a 'windows_first' bias. All other code and instructions are cross-platform and do not favor Windows-specific tools or patterns.
Recommendations
  • Present environment variable instructions for Linux/macOS first, or group all OS instructions together without prioritizing Windows.
  • Explicitly state that all commands and code samples work equally on Linux, macOS, and Windows.
  • Add a note clarifying that the Node.js application and its dependencies are cross-platform.
GitHub Create Pull Request
Azure App Configuration Tutorial: Use Dynamic Configuration Using Push Refresh in a .NET App ...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/enable-dynamic-configuration-dotnet-core-push-refresh.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides environment variable setup instructions for Windows Command Prompt and PowerShell before macOS and Linux, but all platforms are covered equally. There are no Windows-only tools, examples, or patterns; the code and build/run steps are cross-platform. Screenshots use Command Prompt, but this does not affect the ability to follow the tutorial on Linux/macOS.
Recommendations
  • Rotate the order of platform-specific instructions so that Linux/macOS examples are shown first in some sections.
  • Include screenshots from Linux/macOS terminals alongside Windows Command Prompt to visually reinforce parity.
  • Explicitly state that all steps work on Linux/macOS and Windows, and highlight any platform-specific caveats if they 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
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides instructions for setting environment variables on Windows (cmd and PowerShell) before mentioning the Linux/macOS equivalent. All platforms are covered, but Windows commands are shown first, which may subtly prioritize Windows users.
Recommendations
  • Present environment variable instructions for all platforms together, or alternate which platform is shown first.
  • Consider grouping platform-specific instructions in a table for parity.
  • Explicitly state that all major platforms are supported to reassure non-Windows users.
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
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents environment variable setup instructions with Windows Command Prompt and PowerShell examples before macOS and Linux, and provides more detailed instructions for Windows users (e.g., using setx and restart guidance). While Linux/macOS instructions are present and correct, Windows is prioritized in ordering and detail.
Recommendations
  • Present environment variable setup instructions in a neutral order (e.g., Linux/macOS first, or alphabetical).
  • Provide equally detailed instructions for Linux/macOS users (e.g., clarify that export only affects the current shell unless added to profile, and how to persist it).
  • Avoid giving Windows-specific restart instructions unless also explained for Linux/macOS (e.g., restarting the terminal).
  • Consider grouping OS instructions together or using tabs with equal prominence.
GitHub Create Pull Request
Azure App Configuration Quickstart for adding feature flags to JavaScript apps ...pp-configuration/quickstart-feature-flag-javascript.md
Low Priority View Details →
Scanned: 2026-01-13 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 'Run the application' section, where Windows command prompt and PowerShell instructions are presented before Linux/macOS equivalents. The prerequisite section also references Windows and WSL specifically for Node.js installation, but does not provide parity guidance for Linux/macOS. However, all critical steps include Linux/macOS instructions, and the main code samples are cross-platform.
Recommendations
  • Present Linux/macOS instructions before or alongside Windows instructions, rather than after.
  • Add explicit Linux/macOS installation guidance for Node.js in the prerequisites, not just a Windows/WSL link.
  • Where multiple OS instructions are given, use tabs or equal prominence for each platform.
  • Avoid referencing Windows-specific tools (e.g., setx, PowerShell) without equal Linux/macOS context.
GitHub Create Pull Request
Azure App Configuration Azure App Configuration REST API - Microsoft Entra authorization ...e-app-configuration/rest-api-authorization-azure-ad.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation mentions PowerShell and the Azure portal as tools for managing role assignments before mentioning Azure CLI. No explicit Linux/macOS examples or instructions are provided, and the order of tool presentation favors Windows-centric options.
Recommendations
  • Explicitly mention Azure CLI as a cross-platform tool before PowerShell and the Azure portal.
  • Provide example commands for both Azure CLI and PowerShell, highlighting CLI as the recommended option for Linux/macOS users.
  • Add a note clarifying that Azure CLI is available on Windows, Linux, and macOS.
  • Include links to Linux/macOS installation guides for Azure CLI.
GitHub Create Pull Request
Azure App Configuration Quickstart for Azure App Configuration with .NET | Microsoft Docs .../azure-app-configuration/quickstart-dotnet-core-app.md
Low Priority View Details →
Scanned: 2026-01-13 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 be unnecessary duplication compared to the single bash example for Linux/macOS. However, all major steps and code samples are cross-platform, and Linux/macOS users are not blocked from completing the quickstart.
Recommendations
  • Present environment variable instructions for Linux/macOS before Windows, or group all OS instructions together for parity.
  • Provide equal detail for Linux/macOS shell usage (e.g., mention zsh if relevant, note persistence differences).
  • Consider reducing duplication by combining Windows cmd and PowerShell instructions if not strictly necessary.
  • Explicitly state that all .NET CLI commands work identically on Linux/macOS.
  • Add a note about how environment variable persistence differs between shells and OSes.
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
Low Priority View Details →
Scanned: 2026-01-13 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 specific Windows command prompt and PowerShell commands. However, Linux/macOS instructions are present and complete, and the rest of the guide is platform-agnostic.
Recommendations
  • Present Linux/macOS (bash) instructions before Windows examples, or group them together for parity.
  • Explicitly state that all steps work equally on Linux/macOS and Windows.
  • Add notes about any platform-specific caveats (e.g., restarting the shell for environment variables).
  • Consider using cross-platform tooling (e.g., using Maven commands only, which are already present).
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
Low Priority View Details →
Scanned: 2026-01-13 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. However, Linux/macOS instructions are present and complete, and all code samples are cross-platform Go code. No Windows-only tools or patterns are used, and Linux users can follow all steps without friction.
Recommendations
  • Present Linux/macOS (bash) instructions before Windows examples to avoid implicit prioritization.
  • Group environment variable setup instructions by OS, or use tabs for each OS to ensure parity.
  • Clarify that all Go code samples are cross-platform and do not depend on OS-specific features.
  • Consider mentioning that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
GitHub Create Pull Request
Azure App Configuration Azure App Configuration preview API life cycle ...re-app-configuration/concept-preview-api-life-cycle.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Bash and PowerShell examples for checking API versions, but PowerShell is given equal prominence, which may indicate a slight Windows bias. No Linux/macOS-specific tools or patterns are mentioned, but Bash examples are present. The order of examples does not strongly favor Windows, but the inclusion of PowerShell may be unnecessary for a cross-platform CLI like Azure CLI.
Recommendations
  • Consider listing Bash examples before PowerShell, as Bash is more universally available across platforms.
  • Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and that PowerShell is optional.
  • Add a note for Linux/macOS users about shell compatibility and any differences in output formatting.
  • If possible, provide examples using native Linux/macOS tools (e.g., jq) for parsing JSON output.
GitHub Create Pull Request
Azure App Configuration Tutorial: Use dynamic configuration in a .NET background service ...enable-dynamic-configuration-dotnet-background-service.md
Low Priority View Details →
Scanned: 2026-01-13 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). Windows command-line tools (setx, PowerShell) are mentioned first and in more detail, with Linux/macOS instructions following. All .NET CLI commands are cross-platform, and the tutorial does not use Windows-only tools for the main workflow, but the ordering and emphasis favor Windows users.
Recommendations
  • Present Linux/macOS and Windows instructions side-by-side or in tabs, rather than listing Windows first.
  • Explicitly state that all .NET CLI commands work equally on Linux/macOS.
  • Add a note highlighting parity and any platform-specific caveats.
  • Ensure screenshots and examples are not Windows-centric if possible.
GitHub Create Pull Request
Azure App Configuration Configuration Provider Overview ...e-app-configuration/configuration-provider-overview.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a mild Windows bias by listing .NET/.NET Framework libraries first, which are primarily associated with Windows development. The sample links for .NET libraries point to .NET Core and .NET Framework examples, which are historically Windows-centric, and there is no explicit mention of Linux or cross-platform usage in these sections. No Linux-specific tools, shell examples, or parity notes are provided. However, the documentation does include libraries for Java, Python, JavaScript, and Go, which are cross-platform, and does not use Windows-only commands or PowerShell.
Recommendations
  • Explicitly mention cross-platform compatibility for .NET Core and .NET Standard libraries, including Linux and macOS support.
  • Add Linux/macOS sample links or usage notes for .NET libraries, clarifying any platform-specific considerations.
  • Ensure that sample code and instructions are not Windows-centric (e.g., avoid referencing Windows-only tools or paths).
  • Consider reordering the table or providing a note that all listed libraries are cross-platform where applicable.
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
Low Priority View Details →
Scanned: 2026-01-13 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, firewall exception prompts) without mentioning equivalent Linux/macOS developer experiences. However, Linux/macOS instructions are present and accurate.
Recommendations
  • Present Linux/macOS and Windows instructions in parallel or in a neutral order (e.g., Linux/macOS first in some sections, or grouped together).
  • Include explicit instructions for running and debugging Azure Functions locally on Linux/macOS (e.g., using VS Code, Azure Functions Core Tools CLI, or other editors).
  • Mention any platform-specific caveats for Linux/macOS users (e.g., how to install Azure Functions Core Tools, handling environment variables in shells, or alternative to Visual Studio).
  • Clarify that firewall exception prompts and Visual Studio-specific dialogs are Windows-specific, and provide Linux/macOS alternatives or notes.
GitHub Create Pull Request
Azure App Configuration Tutorial: Use dynamic configuration in a .NET app ...figuration/enable-dynamic-configuration-dotnet-core.md
Low Priority View Details →
Scanned: 2026-01-13 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 Windows-specific tools (Command Prompt, PowerShell) in its refresh example. However, Linux/macOS instructions are present and accurate, and the main .NET code is cross-platform.
Recommendations
  • Present environment variable instructions for Linux/macOS before or alongside Windows examples, rather than after.
  • Refer to 'terminal' or 'shell' generically instead of 'Command Prompt or PowerShell window' when describing where to run the app or see output.
  • Include screenshots or explicit mentions of Linux/macOS terminals where applicable.
  • Ensure all steps and examples are equally clear for Linux/macOS users, avoiding Windows-centric terminology.
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
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Minor Windows Tools
Summary
The documentation provides environment variable setup instructions for Windows (command prompt and PowerShell) before macOS and Linux, and uses Windows-style path separators in the MSBuild example. However, it does include macOS and Linux instructions and mentions Visual Studio Code as cross-platform. The bias is mostly in ordering and minor tooling details.
Recommendations
  • Present environment variable instructions for all platforms together, or start with Linux/macOS to avoid Windows-first bias.
  • In MSBuild examples, use path separator syntax that works cross-platform (e.g., $(OutDir)/azureappconfig.json or document both Windows and Linux/macOS variants).
  • Explicitly mention that the .NET CLI and Azure CLI commands work on all platforms.
  • Add a note clarifying any platform-specific differences in build scripts or file paths.
  • Consider providing a bash script example for Linux/macOS users for exporting configuration.
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
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before macOS/Linux, but otherwise includes Linux/macOS equivalents for all steps. No critical steps are Windows-only, and Linux users are able to follow the guide without friction.
Recommendations
  • Present macOS/Linux instructions before or alongside Windows instructions for setting environment variables.
  • Consider grouping all OS-specific instructions together, or using tabs for platform selection.
  • Explicitly state that all steps are cross-platform except where noted.
GitHub Create Pull Request
Azure App Configuration Roll out features to targeted audiences in a Node.js app ...-app-configuration/howto-targetingfilter-javascript.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides environment variable setup instructions for Windows Command Prompt and PowerShell before mentioning the Linux/macOS equivalent. All other code and instructions are cross-platform and do not show Windows-specific bias.
Recommendations
  • Present Linux/macOS environment variable instructions before or alongside Windows instructions to avoid implicit prioritization.
  • Consider grouping all OS-specific instructions together and labeling them clearly, or use tabs for platform selection.
  • Explicitly state that all code samples are platform-agnostic except for environment variable setup.
GitHub Create Pull Request
Azure App Configuration Enable telemetry for feature flags in a Python application ...cles/azure-app-configuration/howto-telemetry-python.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before mentioning the Linux/macOS equivalent. All other code and instructions are platform-agnostic, with no exclusive use of Windows tools or missing Linux examples.
Recommendations
  • Present environment variable setup instructions for Linux/macOS first or side-by-side with Windows examples.
  • Explicitly state that all code samples are cross-platform unless otherwise noted.
  • Consider grouping platform-specific instructions together in a table for clarity.
GitHub Create Pull Request
Azure App Configuration Quickstart for Azure App Configuration with Aspire .../articles/azure-app-configuration/quickstart-aspire.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation demonstrates a mild Windows bias by recommending Docker Desktop as the container runtime and showing screenshots of Docker Desktop, which is most commonly used on Windows. While the instructions themselves are cross-platform and do not use Windows-specific commands or PowerShell, the visual and tool recommendations may create friction for Linux/macOS users. No critical steps are Windows-only, and Linux/macOS users can follow the instructions with alternative tools.
Recommendations
  • Explicitly mention that any OCI-compliant container runtime (e.g., Docker Engine, Podman) can be used on Linux/macOS, not just Docker Desktop.
  • Include screenshots or brief instructions for starting containers on Linux/macOS (e.g., using Docker CLI or Podman).
  • Where Docker Desktop is referenced, add a note about alternatives for non-Windows platforms.
  • Ensure that all CLI commands shown work on Linux/macOS and clarify any platform-specific differences if present.
GitHub Create Pull Request
Azure App Configuration Quickstart for using chat completion configuration in a .NET app ...app-configuration/quickstart-chat-completion-dotnet.md
Low Priority View Details →
Scanned: 2026-01-13 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). Windows-specific tools (setx, PowerShell) are mentioned first, with Linux/macOS instructions given later. All code examples are platform-neutral, but the ordering and emphasis favor Windows users.
Recommendations
  • Present environment variable setup instructions for all platforms in parallel, or start with a neutral/universal method (e.g., bash, then Windows).
  • Explicitly state that all .NET CLI commands work on Linux/macOS as well as Windows.
  • Add notes or troubleshooting tips for Linux/macOS users (e.g., environment variable persistence, shell differences).
  • Ensure parity in example ordering and depth for all platforms.
GitHub Create Pull Request
← Previous Page 17 of 20 Next →