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 76-100 of 474 flagged pages
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-feature-flag-dotnet.md ...re-app-configuration/quickstart-feature-flag-dotnet.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively providing environment variable setup instructions for Windows tools (Command Prompt and PowerShell), omitting Linux/macOS equivalents (such as bash or zsh). Visual Studio is listed as the only development environment, with no mention of cross-platform editors like VS Code or CLI alternatives. Screenshots and instructions reference Command Prompt, further reinforcing the Windows-centric approach. No Linux shell commands or guidance for running the app on Linux/macOS are present.
Recommendations
  • Add instructions for setting environment variables on Linux/macOS (e.g., export Endpoint=...) and clarify shell differences.
  • Include examples using bash/zsh and the .NET CLI for project creation, building, and running, alongside Visual Studio steps.
  • Provide screenshots or terminal output examples from Linux/macOS environments.
  • Mention cross-platform editors like Visual Studio Code and provide parity in setup instructions.
  • Explicitly state that the .NET SDK and Azure App Configuration libraries are cross-platform, and highlight any platform-specific considerations.
GitHub Create Pull Request
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-go-console-app.md ...s/azure-app-configuration/quickstart-go-console-app.md
High Priority View Details →
Scanned: 2025-09-05 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS, and includes Windows-specific commands (setx, PowerShell syntax). While Linux/macOS commands are present, Windows instructions are consistently listed first and in more detail, and Windows tools (setx, PowerShell) are explicitly mentioned, which may signal a Windows-centric approach.
Recommendations
  • Alternate the order of platform instructions (sometimes show Linux/macOS first) or group all OS instructions together in a table for parity.
  • Provide equal detail for Linux/macOS and Windows, including any caveats (e.g., persistence of environment variables across shells/sessions).
  • Avoid Windows-specific tools like 'setx' unless a Linux/macOS equivalent is also discussed (e.g., how to persist environment variables in .bashrc/.zshrc).
  • Consider using expandable sections or tabs for each OS to avoid implicit prioritization.
  • Explicitly state that all major OSes are supported and tested, and provide troubleshooting tips for each.
GitHub Create Pull Request
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-go-console-app.md ...s/azure-app-configuration/quickstart-go-console-app.md
High Priority View Details →
Scanned: 2025-09-02 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS, and includes Windows-specific tools (setx, PowerShell syntax) with detailed steps. Linux/macOS instructions are present but consistently listed after Windows, and there are no Linux-specific troubleshooting or parity notes. The CLI example (az login) is cross-platform, but the overall pattern prioritizes Windows users.
Recommendations
  • Alternate the order of platform-specific instructions so that Linux/macOS examples are sometimes listed first, or present all platform instructions in a single table for parity.
  • Provide equal detail for Linux/macOS shell environments (e.g., mention ~/.bashrc or ~/.zshrc for persistent environment variables, not just export).
  • Avoid using Windows-only tools (like setx) without mentioning Linux/macOS equivalents (e.g., export plus adding to shell profile).
  • Where possible, use cross-platform commands or highlight them as such.
  • Add troubleshooting notes for both Windows and Linux/macOS environments to ensure parity.
GitHub Create Pull Request
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-go-console-app.md ...s/azure-app-configuration/quickstart-go-console-app.md
High Priority View Details →
Scanned: 2025-09-01 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides instructions for setting environment variables on Windows (cmd and PowerShell) before Linux/macOS (bash), and includes Windows-specific tools (setx, PowerShell syntax) prominently. Linux/macOS instructions are present but appear after Windows, and there are no Linux-specific troubleshooting tips or parity notes. The overall flow and examples are otherwise cross-platform, but the ordering and prominence of Windows tools may subtly bias toward Windows users.
Recommendations
  • Present Linux/macOS and Windows instructions in parallel tabbed sections, or alternate the order to avoid always listing Windows first.
  • Use neutral, cross-platform language where possible (e.g., 'set the environment variable' with tabs for each OS).
  • Add Linux-specific troubleshooting or tips where relevant (e.g., shell persistence of environment variables).
  • Consider including a note that all Go code and Azure CLI commands are cross-platform.
  • Avoid using Windows-specific tools (like setx) without equivalent Linux/macOS context (e.g., mention ~/.bashrc for persistence).
GitHub Create Pull Request
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-go-console-app.md ...s/azure-app-configuration/quickstart-go-console-app.md
High Priority View Details →
Scanned: 2025-08-31 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS, and includes Windows-specific tools (setx, PowerShell) with detailed usage. While Linux/macOS commands are present, Windows instructions are consistently listed first, and PowerShell is given its own example. No Linux-specific tools or patterns are highlighted.
Recommendations
  • Present Linux/macOS and Windows instructions in parallel tabs or side-by-side, rather than listing Windows first.
  • Avoid giving Windows command prompt and PowerShell separate, prioritized sections unless Linux shells are given equal prominence.
  • Consider leading with cross-platform shell commands (e.g., bash) or providing a neutral default, with OS-specific instructions in expandable sections.
  • If mentioning Windows tools like setx, also mention Linux equivalents (e.g., export, or how to persist environment variables in .bashrc/.zshrc) and provide links to relevant documentation.
  • Ensure that Linux/macOS users are not treated as an afterthought by giving their instructions equal detail and placement.
GitHub Create Pull Request
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-go-console-app.md ...s/azure-app-configuration/quickstart-go-console-app.md
High Priority View Details →
Scanned: 2025-08-30 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation presents environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS, and includes both setx (Windows command prompt) and PowerShell examples, which are Windows-specific tools. Linux/macOS instructions are present but always listed after Windows. There are no missing Linux examples, but the ordering and tool emphasis show a Windows-first bias.
Recommendations
  • Present Linux/macOS and Windows instructions in parallel (side-by-side tabs) or alternate the order to avoid always listing Windows first.
  • Avoid giving more prominence to Windows-specific tools (e.g., setx, PowerShell) by grouping all OS instructions equally or using tabs.
  • Consider providing a brief explanation that environment variable setting methods differ by OS, and link to official OS documentation for details.
  • Ensure that all examples and instructions are equally detailed for both Windows and Linux/macOS.
  • Where possible, use cross-platform tools or commands (e.g., recommend using the Azure CLI for authentication and configuration, which works on all platforms).
GitHub Create Pull Request
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-go-console-app.md ...s/azure-app-configuration/quickstart-go-console-app.md
High Priority View Details →
Scanned: 2025-08-29 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS, and includes Windows-specific tools (setx, PowerShell) with detailed steps. Linux/macOS instructions are present but consistently listed after Windows, and less explanation is given for their environment variable persistence. There are no missing Linux examples, but the ordering and emphasis show a Windows-first bias.
Recommendations
  • Present Linux/macOS and Windows instructions in parallel (side-by-side tabs or equal prominence), or list Linux/macOS first if usage data supports it.
  • Provide equal detail for Linux/macOS environment variable persistence (e.g., mention adding to ~/.bashrc or ~/.zshrc for permanence).
  • Avoid giving Windows tools (setx, PowerShell) more prominence or detail than their Linux/macOS equivalents.
  • Consider using tabbed code blocks for each OS to avoid implicit prioritization.
  • Explicitly state that all major platforms are supported and tested.
GitHub Create Pull Request
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-go-console-app.md ...s/azure-app-configuration/quickstart-go-console-app.md
High Priority View Details →
Scanned: 2025-08-28 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
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. Both 'setx' (Windows tool) and PowerShell are mentioned explicitly, while Linux/macOS only receives a single bash example. There are no missing Linux examples, but the ordering and explicit mention of Windows-specific tools and shells indicate a subtle preference for Windows environments.
Recommendations
  • Present Linux/macOS and Windows instructions in parallel tabbed sections, or alternate which platform appears first to avoid implicit prioritization.
  • Use generic shell commands (e.g., 'export') first, with platform-specific notes as needed.
  • Minimize the use of Windows-specific tools like 'setx' unless absolutely necessary, and provide context for when each method is appropriate.
  • Explicitly state that all examples are cross-platform unless otherwise noted, and ensure parity in detail and explanation for each OS.
  • Consider adding a table or tabs for environment variable setup, with clear labels for 'Windows CMD', 'PowerShell', and 'Linux/macOS Bash' to reinforce equal support.
GitHub Create Pull Request
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-go-console-app.md ...s/azure-app-configuration/quickstart-go-console-app.md
High Priority View Details →
Scanned: 2025-08-27 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS, and includes explicit commands for Windows tools (setx, PowerShell) alongside bash. This ordering and explicit mention of Windows tools, with Linux/macOS instructions always last, demonstrates a Windows-first and Windows-tools bias. However, Linux/macOS instructions are present and complete, and there are no missing Linux examples for the Go code itself.
Recommendations
  • Present environment variable setup instructions for all platforms in parallel (e.g., in a table or side-by-side tabs), or rotate which OS appears first to avoid always privileging Windows.
  • Avoid giving Windows instructions (cmd, PowerShell) first by default; consider starting with bash (Linux/macOS), or presenting all equally.
  • Where possible, use cross-platform commands or note platform-specific differences only when necessary.
  • Explicitly state that all platforms are supported and tested, and provide troubleshooting tips for both Windows and Linux/macOS environments.
  • If using tabs, ensure the default selected tab is not always Windows.
GitHub Create Pull Request
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/reload-key-vault-secrets-dotnet.md ...e-app-configuration/reload-key-vault-secrets-dotnet.md
High Priority View Details →
Scanned: 2025-08-12 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation is focused exclusively on ASP.NET Core and the Azure portal, both of which are cross-platform, but all code and workflow examples are tailored for .NET developers (typically Windows-centric). There are no Linux-specific instructions, CLI examples, or references to non-Windows development environments. The use of the Azure portal and .NET-centric instructions implicitly prioritize Windows users, and there is no mention of equivalent workflows for Linux or cross-platform command-line tools.
Recommendations
  • Provide equivalent examples using Azure CLI and/or Azure PowerShell for all portal-based steps, making it clear these can be run on Linux, macOS, or Windows.
  • Include a section or callout for Linux/macOS users, highlighting any differences or confirming that all steps are cross-platform.
  • Mention that ASP.NET Core and the Azure SDKs are cross-platform, and provide explicit instructions or links for setting up the development environment on Linux.
  • Add sample code or scripts for certificate and secret management using bash scripts or Linux shell commands where appropriate.
  • Ensure that references to tools or workflows (such as Visual Studio) are balanced with alternatives (such as VS Code, JetBrains Rider, or command-line editors) that are popular on Linux.
GitHub Create Pull Request
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-azure-functions-csharp.md ...app-configuration/quickstart-azure-functions-csharp.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a Windows-first bias, particularly in the prerequisites and local testing sections. Visual Studio (a Windows-centric IDE) is the only development environment mentioned, and instructions for setting environment variables list Windows Command Prompt and PowerShell before Linux/macOS equivalents. The workflow assumes Visual Studio usage and references Windows-specific tools and patterns, with Linux parity only addressed as an afterthought.
Recommendations
  • Add explicit instructions and examples for developing and running Azure Functions using cross-platform tools such as Visual Studio Code and the Azure Functions Core Tools CLI.
  • Present environment variable setting commands for Linux/macOS before or alongside Windows commands, rather than after.
  • Include guidance for using .NET CLI and editors available on all platforms, not just Visual Studio.
  • Clarify that the quickstart is applicable to all platforms and provide parity in screenshots and workflow steps for Linux/macOS users.
  • Mention and link to documentation for developing Azure Functions on Linux/macOS environments.
GitHub Create Pull Request
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/integrate-ci-cd-pipeline.md ...es/azure-app-configuration/integrate-ci-cd-pipeline.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a Windows-first bias by presenting Windows command prompt and PowerShell instructions before macOS and Linux equivalents. The use of MSBuild and .csproj scripting is more common in Windows-centric workflows. Visual Studio Code is mentioned as cross-platform, but the primary application example is an ASP.NET Core app, which is historically Windows-centric, though now cross-platform. No Linux-specific tools or patterns are highlighted, and the structure subtly prioritizes Windows users.
Recommendations
  • Present Linux/macOS and Windows instructions in parallel or randomize their order to avoid always listing Windows first.
  • Include examples using Linux-native build tools or scripting (e.g., bash scripts, Makefiles) alongside MSBuild.
  • Highlight cross-platform compatibility explicitly, and provide more context for Linux users (e.g., file path conventions, shell differences).
  • Where possible, use neutral language and tools (e.g., .NET CLI, Azure CLI) that work identically across platforms.
  • Add troubleshooting tips or notes for Linux-specific issues that may arise in CI/CD pipelines.
GitHub Create Pull Request
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-resource-manager.md ...azure-app-configuration/quickstart-resource-manager.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation provides deployment instructions and examples exclusively using PowerShell, a Windows-centric tool, without offering equivalent examples for Linux or cross-platform environments (such as Azure CLI or Bash). The only command-line deployment example is PowerShell, and there is no mention of Linux or macOS workflows. The documentation implicitly assumes a Windows environment by default.
Recommendations
  • Add Azure CLI examples for deploying the ARM template, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Include Bash shell examples for resource group creation and template deployment.
  • Explicitly mention that the instructions apply to all platforms, and provide guidance for both Windows (PowerShell) and Linux/macOS (Bash/Azure CLI) users.
  • Reorder or parallelize examples so that Windows and Linux instructions are presented together, rather than Windows/PowerShell first or exclusively.
  • Where possible, use platform-neutral language and tools in the main flow, relegating platform-specific instructions to separate sections or tabs.
GitHub Create Pull Request
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/monitor-app-configuration.md ...s/azure-app-configuration/monitor-app-configuration.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing Windows tools and workflows. PowerShell is given its own dedicated section, and instructions for command-line usage reference Windows PowerShell and opening a Windows PowerShell command window. There is no mention of Linux-specific shells or tools, and no explicit Linux/Bash examples are provided. The Azure CLI section mentions Windows PowerShell as an example of a command console, but does not mention Bash or other Linux shells. This may make Linux users feel less supported or unsure if the instructions are applicable to their environment.
Recommendations
  • In the Azure CLI section, mention both Windows PowerShell and Bash (or other Linux shells) as valid environments for running Azure CLI commands.
  • Add explicit instructions or notes for Linux/macOS users, such as 'Open a terminal (e.g., Bash, zsh) on Linux/macOS' alongside Windows PowerShell.
  • Where PowerShell is referenced, clarify that Azure PowerShell is available cross-platform, or provide equivalent Bash/Azure CLI examples where possible.
  • Avoid language that assumes a Windows environment (e.g., 'Open a Windows PowerShell command window') unless the instructions are truly Windows-specific.
  • Consider adding a 'Linux/macOS' tab or section for parity with the PowerShell and Portal tabs, especially for command-line operations.
  • Ensure screenshots and UI references are not Windows-specific unless necessary, and clarify when steps are identical across platforms.
GitHub Create Pull Request
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-feature-flag-dotnet.md ...re-app-configuration/quickstart-feature-flag-dotnet.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing only Windows-specific instructions for setting environment variables (Windows Command Prompt and PowerShell), referencing Visual Studio exclusively as the development environment, and omitting Linux/macOS equivalents for key steps such as environment variable setup and project creation. There are no Bash or cross-platform CLI instructions, and the workflow assumes a Windows-centric toolchain.
Recommendations
  • Add instructions for setting environment variables on Linux/macOS using Bash (e.g., export ConnectionString=...).
  • Include cross-platform .NET CLI commands (e.g., dotnet new console) for project creation, in addition to Visual Studio steps.
  • Mention and provide examples for using editors and IDEs available on Linux/macOS (e.g., VS Code, JetBrains Rider).
  • Ensure all code and configuration steps are clearly marked as cross-platform where applicable, and explicitly state any Windows-only requirements.
  • Reorder or parallelize instructions so that Windows and Linux/macOS steps are presented with equal prominence.
GitHub Create Pull Request
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-java-spring-app.md .../azure-app-configuration/quickstart-java-spring-app.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a Windows-first bias in the environment variable setup section, where Windows Command Prompt and PowerShell commands are listed before the Linux/macOS equivalent. The use of 'setx' (a Windows-specific tool) and explicit mention of PowerShell further reinforce this. Additionally, the build/run instructions use 'cmd' syntax highlighting, which may suggest a Windows-centric approach, even though the commands themselves are cross-platform.
Recommendations
  • Present Linux/macOS commands before or alongside Windows commands, rather than after.
  • Use neutral or platform-agnostic syntax highlighting (e.g., 'bash' or no language) for cross-platform commands like Maven and curl.
  • Explicitly mention that the build/run commands work identically on Linux/macOS and Windows, and provide any necessary platform-specific notes.
  • Consider grouping environment variable instructions by platform, or using tabs or collapsible sections for each OS to improve clarity and parity.
  • Avoid using Windows-specific tools (like 'setx') as the primary example; instead, provide platform-appropriate commands for each OS.
GitHub Create Pull Request
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/enable-dynamic-configuration-aspnet-netfx.md ...iguration/enable-dynamic-configuration-aspnet-netfx.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation demonstrates a Windows-first bias by focusing exclusively on ASP.NET Web Forms (.NET Framework), which is only supported on Windows. Visual Studio (Windows-only) is required, and all project setup instructions assume a Windows environment. While environment variable setup commands are provided for Windows Command Prompt, PowerShell, and (last) macOS/Linux, the overall workflow and prerequisites are Windows-centric, with no mention of Linux-compatible alternatives for development or deployment.
Recommendations
  • Add a note at the beginning clarifying that ASP.NET Web Forms (.NET Framework) is Windows-only, and suggest .NET Core/ASP.NET Core for cross-platform scenarios.
  • Provide equivalent instructions for setting up and running a similar dynamic configuration sample using ASP.NET Core, which is cross-platform.
  • Include Linux/macOS-friendly IDE alternatives (e.g., Visual Studio Code, JetBrains Rider) and instructions for using the dotnet CLI where possible.
  • Reorder environment variable instructions to present Linux/macOS commands first or alongside Windows commands, rather than always after.
  • Where possible, highlight any differences or limitations for Linux/macOS users, and link to relevant cross-platform documentation.
GitHub Create Pull Request
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/enable-dynamic-configuration-aspnet-netfx.md ...iguration/enable-dynamic-configuration-aspnet-netfx.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation is heavily oriented toward Windows development environments, specifically Visual Studio and the .NET Framework, which are primarily Windows-based. Windows-specific tools and workflows (e.g., Visual Studio, Windows Command Prompt, PowerShell) are mentioned first and in detail. While Linux/macOS environment variable commands are included, they are always listed last and lack parity in development environment guidance (e.g., no mention of cross-platform .NET Core, VS Code, or Mono). The tutorial assumes the use of Windows throughout, with no Linux-specific or cross-platform development instructions.
Recommendations
  • Provide equivalent instructions for developing and running the sample on Linux and macOS, such as using Visual Studio Code or JetBrains Rider, and .NET Core/Mono where possible.
  • List Linux/macOS commands before or alongside Windows commands to avoid 'windows_first' ordering.
  • Include guidance for setting up and running ASP.NET applications on Linux (e.g., using Mono or .NET Core if applicable), or explicitly state Windows-only limitations.
  • Mention and provide examples for cross-platform CLI tools (e.g., dotnet CLI) instead of or in addition to Visual Studio GUI steps.
  • Clarify any Windows-only requirements up front, and suggest alternatives or workarounds for non-Windows users.
GitHub Create Pull Request
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/enable-dynamic-configuration-dotnet.md ...p-configuration/enable-dynamic-configuration-dotnet.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a Windows-first bias, particularly in the 'Build and run the app locally' section, where Windows command prompt and PowerShell instructions are consistently presented before Linux/macOS equivalents. Visual Studio, a Windows-centric IDE, is the only development environment mentioned. The overall workflow and examples assume a Windows environment, with only brief, secondary mention of Linux/macOS commands. There are no Linux-specific development tools or editors referenced, and the guidance to restart Visual Studio further centers the Windows experience.
Recommendations
  • Present Linux/macOS instructions alongside or before Windows instructions, or group them equally to avoid the perception of Windows primacy.
  • Include alternative development environment options, such as Visual Studio Code or JetBrains Rider, which are cross-platform, and provide relevant instructions for those editors.
  • Explicitly mention that the .NET Framework is Windows-only, but highlight that .NET (Core/5+) is cross-platform and link to equivalent tutorials for those platforms.
  • Provide guidance for building and running the app using the .NET CLI (dotnet), where possible, to support Linux/macOS users.
  • When referencing environment variable setup, ensure parity in detail and order for all platforms.
  • Consider adding a section or callout for Linux/macOS users, outlining any platform-specific caveats or alternative workflows.
GitHub Create Pull Request
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/integrate-ci-cd-pipeline.md ...es/azure-app-configuration/integrate-ci-cd-pipeline.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. Windows command prompt and PowerShell instructions are presented before macOS and Linux equivalents. The example project is based on ASP.NET Core, and the build script uses MSBuild, which is more common on Windows (though cross-platform). Visual Studio Code is mentioned as cross-platform, but the workflow and examples are more familiar to Windows users. There is no explicit omission of Linux/macOS steps, but the ordering and tool choices favor Windows.
Recommendations
  • Present Linux/macOS and Windows instructions in parallel or in a neutral order (alphabetically or grouped by shell type).
  • Include explicit notes about cross-platform compatibility of MSBuild and .NET CLI, and provide alternative scripts if needed for non-Windows environments.
  • Add more context or examples for Linux/macOS users, such as using bash scripts or alternative editors.
  • Highlight that the Azure CLI and .NET CLI are fully cross-platform, and provide troubleshooting tips for common Linux/macOS issues.
  • Consider using generic environment variable setting instructions first, then provide OS-specific tabs if needed.
GitHub Create Pull Request
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/integrate-kubernetes-deployment-helm.md ...-configuration/integrate-kubernetes-deployment-helm.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page generally uses cross-platform tools (Azure CLI, Helm), but in the section on passing literal key-values to Helm, only a PowerShell script is provided, with no Bash/Linux shell equivalent. The PowerShell example is presented as the only method for dynamic key-value injection, which may disadvantage Linux/macOS users. There is no mention or example of how to achieve the same result using Bash or other Unix shells, and the PowerShell example appears before any alternative is discussed.
Recommendations
  • Provide equivalent Bash (or POSIX shell) examples alongside PowerShell scripts for dynamic key-value injection with Helm.
  • Explicitly mention that the PowerShell script is for Windows users and offer a parallel solution for Linux/macOS users.
  • Consider presenting cross-platform (Bash first or both together) examples when scripting is required, to avoid the perception of Windows-first bias.
  • Audit other sections for subtle Windows-centric language or tool recommendations and ensure parity in instructions for Linux environments.
GitHub Create Pull Request
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/monitor-app-configuration.md ...s/azure-app-configuration/monitor-app-configuration.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by prioritizing Windows tools and workflows. In the Azure CLI section, Windows PowerShell is mentioned as the default example for opening a command console, and in the PowerShell section, only Windows PowerShell is referenced. There are no explicit Linux shell (e.g., Bash) or macOS terminal instructions, nor are there screenshots or examples tailored for non-Windows environments. The documentation assumes familiarity with Windows-centric tools and does not provide parity for Linux users.
Recommendations
  • In the Azure CLI section, mention opening a terminal or shell on Linux/macOS, not just Windows PowerShell.
  • Provide explicit Bash/zsh examples or notes for Linux/macOS users alongside PowerShell instructions.
  • Avoid defaulting to Windows PowerShell as the primary example; instead, present cross-platform instructions or alternate between platforms.
  • Include screenshots or references that are not Windows-specific (e.g., avoid showing only Windows UI or PowerShell windows).
  • Clarify that Azure CLI and portal steps are cross-platform and can be performed on any OS.
GitHub Create Pull Request
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/howto-variant-feature-flags-python.md ...pp-configuration/howto-variant-feature-flags-python.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several areas. The prerequisite section links only to Windows-specific Python setup documentation, omitting Linux or macOS equivalents. When describing how to activate a Python virtual environment, only the Windows command ('.\venv\Scripts\Activate') is shown, with no mention of the Linux/macOS alternative ('source venv/bin/activate'). In the section on setting environment variables, Windows Command Prompt and PowerShell instructions are provided before the Linux/macOS example, and the Linux/macOS export command is missing a closing quote, which could cause confusion.
Recommendations
  • Provide links to Python installation/setup documentation for Linux and macOS alongside the Windows link in the prerequisites.
  • When showing how to activate a Python virtual environment, include both Windows ('.\venv\Scripts\Activate') and Linux/macOS ('source venv/bin/activate') commands, clearly labeled.
  • In the environment variable section, present all platform instructions together, or rotate the order (e.g., Linux/macOS first sometimes) to avoid always privileging Windows.
  • Carefully check Linux/macOS command syntax for accuracy (e.g., ensure quotes are closed in export commands).
  • Wherever possible, use cross-platform commands or note platform differences explicitly to ensure parity and clarity for all users.
GitHub Create Pull Request
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-azure-functions-csharp.md ...app-configuration/quickstart-azure-functions-csharp.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a Windows-first bias by recommending Visual Studio as the primary development environment and providing Windows command prompt and PowerShell instructions before Linux/macOS equivalents. The instructions for setting environment variables are detailed for Windows tools (cmd, PowerShell) and only then for bash. The use of Visual Studio and references to its features (such as F5 to run, and screenshots of the Visual Studio UI) further reinforce the Windows-centric approach. There are no explicit Linux development environment recommendations or parity in tooling guidance.
Recommendations
  • Provide equal prominence to cross-platform development tools such as Visual Studio Code and the Azure Functions Core Tools CLI, including setup and usage instructions for Linux/macOS.
  • Present environment variable instructions for Linux/macOS alongside Windows, not after, or use tabbed sections to avoid implicit prioritization.
  • Include screenshots and workflow steps for non-Windows environments (e.g., VS Code on Linux/macOS) where Visual Studio is referenced.
  • Mention and link to cross-platform alternatives for all required tools, not just Visual Studio.
  • Clarify that all steps are supported on Linux/macOS and provide troubleshooting or notes for any platform-specific differences.
GitHub Create Pull Request
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/use-key-vault-references-spring-boot.md ...-configuration/use-key-vault-references-spring-boot.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a Windows-first bias in the environment variable setup section, where Windows Command Prompt and PowerShell commands are presented before the Linux/macOS equivalent. The use of setx and PowerShell-specific syntax is highlighted, while the Linux/macOS export command is listed last. Additionally, the documentation references Visual Studio Code as a cross-platform editor but does not provide any Linux-specific tooling or terminal instructions elsewhere. All Azure CLI commands are cross-platform, but the explicit ordering and detail for Windows tools and patterns indicate a preference for Windows environments.
Recommendations
  • Present environment variable setup instructions for Linux/macOS before or alongside Windows instructions, rather than after.
  • Use neutral, cross-platform shell commands (e.g., export) as the primary example, with OS-specific alternatives in expandable sections or side notes.
  • Include explicit instructions or screenshots for Linux/macOS terminal usage where relevant, not just Windows.
  • Mention and provide examples for popular Linux editors or terminal environments, not just Visual Studio Code.
  • Ensure all code snippets and setup steps are tested and clearly documented for both Windows and Linux/macOS environments.
GitHub Create Pull Request
← Previous Page 4 of 19 Next →