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

469 issues found
Showing 1-25 of 469 flagged pages
Azure App Configuration Tutorial for using Azure App Configuration dynamic configuration in an ASP.NET web application (.NET Framework) | Microsoft Docs ...iguration/enable-dynamic-configuration-aspnet-netfx.md
High Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily oriented toward Windows development environments, with Visual Studio as the only IDE mentioned and all examples targeting ASP.NET Web Forms (.NET Framework), which is Windows-only. In environment variable setup instructions, Windows command prompt and PowerShell examples are presented before Linux/macOS equivalents. The tutorial assumes use of Visual Studio and does not mention alternatives for Linux/macOS users, nor does it address cross-platform .NET (Core/6+) scenarios.
Recommendations
  • Add guidance for cross-platform development, such as using VS Code or JetBrains Rider on Linux/macOS.
  • Explicitly state that ASP.NET Web Forms (.NET Framework) is Windows-only and suggest .NET (Core/6+) alternatives for Linux/macOS users.
  • Present Linux/macOS shell commands before or alongside Windows commands, rather than after.
  • Include notes or links for Linux/macOS users on how to adapt the workflow, especially regarding IDE, environment setup, and running the application.
  • Clarify that the tutorial is not applicable to Linux/macOS for ASP.NET Web Forms, and provide links to relevant cross-platform tutorials.
GitHub Create Pull Request
Azure App Configuration Tutorial for using Azure App Configuration dynamic configuration in an ASP.NET web application (.NET Framework) | Microsoft Docs ...iguration/enable-dynamic-configuration-aspnet-netfx.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The tutorial is heavily focused on Windows development environments, specifically Visual Studio and ASP.NET Web Forms (.NET Framework), which are Windows-only technologies. Windows command prompt and PowerShell instructions are presented first and in more detail, with Linux/macOS equivalents listed after. The entire workflow assumes use of Visual Studio, which is not available on Linux/macOS, and does not mention alternatives for non-Windows platforms. There are no Linux/macOS-specific development environment recommendations or guidance.
Recommendations
  • Add explicit notes that ASP.NET Web Forms (.NET Framework) development is Windows-only, and suggest .NET Core/ASP.NET Core for cross-platform scenarios.
  • Provide alternative instructions for Linux/macOS users, such as using Visual Studio Code or JetBrains Rider, and clarify which steps are not possible outside Windows.
  • Present environment variable setting commands for Windows, Linux, and macOS together, or alternate the order to avoid Windows-first bias.
  • Include links or references to cross-platform tutorials for similar functionality in ASP.NET Core.
  • Clarify that Visual Studio is required only for Windows, and suggest cross-platform IDEs for .NET Standard/.NET Core development.
GitHub Create Pull Request
Azure App Configuration Tutorial: Use dynamic configuration in a .NET app ...figuration/enable-dynamic-configuration-dotnet-core.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias in several areas: Windows command prompt and PowerShell instructions are presented before Linux/macOS equivalents, and screenshots and refresh instructions reference Windows-specific tools (Command Prompt, PowerShell). While Linux/macOS commands are included, Windows tools and patterns are prioritized and referenced more frequently.
Recommendations
  • Present platform instructions in parallel or start with a neutral, cross-platform approach (e.g., bash first, or all platforms side-by-side).
  • Include screenshots or references for Linux/macOS terminals, not just Windows Command Prompt/PowerShell.
  • Use generic terms like 'terminal window' instead of 'Command Prompt or PowerShell window' when referring to where users interact with the app.
  • Ensure all examples and instructions are equally detailed for Linux/macOS users, not just Windows users.
  • Explicitly mention that all steps work on Linux/macOS and provide troubleshooting notes for non-Windows platforms if needed.
GitHub Create Pull Request
Azure App Configuration Monitor Azure App Configuration ...s/azure-app-configuration/monitor-app-configuration.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias in several ways. Windows tools and terminology (such as Windows PowerShell) are mentioned first or exclusively in several places. For example, when describing how to use the Azure CLI, the documentation suggests opening 'Windows PowerShell' as the example console, even though Azure CLI is cross-platform. The PowerShell section is present and detailed, but there is no equivalent section for Bash or Linux shell scripting. The instructions and examples for command-line usage reference Windows environments before Linux or macOS, and do not provide parity for Linux users.
Recommendations
  • When referencing the Azure CLI, suggest opening a 'terminal' or 'command prompt' generically, and provide examples for Bash or Linux/macOS terminals alongside Windows PowerShell.
  • Add a dedicated section for Bash/Linux shell scripting, including examples for common tasks such as authentication and diagnostic setting creation.
  • Avoid using 'Windows PowerShell' as the default example for cross-platform tools; use 'PowerShell' or 'terminal' and clarify platform compatibility.
  • Ensure that screenshots and instructions are platform-neutral or provide alternatives for Linux/macOS users.
  • Explicitly mention that all CLI commands work on Linux/macOS and provide troubleshooting tips for those platforms if needed.
GitHub Create Pull Request
Azure App Configuration Quickstart for Azure App Configuration with Aspire .../articles/azure-app-configuration/quickstart-aspire.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Docker Desktop (a Windows/macOS tool) as the default container runtime, omitting Linux alternatives. There are no explicit Linux-specific instructions or examples, and the setup steps and screenshots implicitly target Windows environments. The documentation does not mention Linux-native container runtimes (e.g., Podman), nor does it provide guidance for Linux users on installing prerequisites or running the emulator.
Recommendations
  • Mention and provide instructions for installing and using Linux-native container runtimes such as Podman or Docker Engine.
  • Include explicit Linux setup steps and screenshots where relevant, or clarify that the instructions apply equally to Linux.
  • When referencing Docker Desktop, add a note about alternatives for Linux users, such as Docker Engine or Podman.
  • Ensure that CLI commands and file paths are compatible with both Windows and Linux environments, and clarify any differences.
  • Add troubleshooting tips for common Linux-specific issues (e.g., permissions, networking).
GitHub Create Pull Request
Azure App Configuration Quickstart to learn how to use Azure App Configuration .../azure-app-configuration/quickstart-java-spring-app.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias in several ways: Windows command-line instructions (setx, PowerShell) are presented before Linux/macOS equivalents, and Windows-specific tools and patterns (setx, PowerShell) are mentioned explicitly. The Linux/macOS example for setting environment variables is given last and lacks detail compared to the Windows instructions. The build/run/test steps use generic commands but are shown in Windows command prompt syntax. There is no explicit Linux shell or terminal example, and no mention of Linux-specific considerations.
Recommendations
  • Present Linux/macOS and Windows instructions side-by-side or in parallel, rather than listing Windows first.
  • Use generic shell syntax (e.g., $ export VAR=...) for environment variables, and provide both Windows and Linux/macOS examples with equal prominence.
  • Avoid using Windows-specific tools (e.g., setx) without offering Linux/macOS equivalents (e.g., export, or instructions for persistent environment variables).
  • Clarify that build/run commands (mvn) are cross-platform, and show examples in both Windows CMD/PowerShell and Linux/macOS terminal.
  • Add notes or sections for Linux/macOS users, including troubleshooting or environment setup tips specific to those platforms.
GitHub Create Pull Request
Azure App Configuration Tutorial for using Azure App Configuration dynamic configuration in an ASP.NET web application (.NET Framework) | Microsoft Docs ...iguration/enable-dynamic-configuration-aspnet-netfx.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Visual Studio Only Missing Linux Example Powershell Heavy
Summary
The tutorial is strongly oriented toward Windows development, focusing exclusively on ASP.NET (.NET Framework) and Visual Studio, both of which are Windows-only. All project creation and build/run instructions assume Visual Studio, with no mention of Linux-compatible alternatives (e.g., Mono, .NET Core, VS Code). While environment variable setup includes bash commands for macOS/Linux, all code samples and workflow steps are tailored for Windows users, and Windows command-line tools (cmd, PowerShell) are listed before Linux equivalents.
Recommendations
  • Add instructions for setting up and running the application on Linux (e.g., using Mono or .NET Core where possible).
  • Include alternative IDEs such as Visual Studio Code or JetBrains Rider, and provide steps for project creation and management on those platforms.
  • Present Linux/macOS commands before or alongside Windows commands, not after.
  • Clarify platform limitations (e.g., .NET Framework is Windows-only) and link to cross-platform alternatives (e.g., ASP.NET Core tutorials).
  • Provide guidance for building and running the application using command-line tools (dotnet CLI, msbuild) on Linux/macOS.
  • Where possible, offer parity in troubleshooting, resource cleanup, and next steps for non-Windows environments.
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
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by consistently presenting Windows Command Prompt and PowerShell instructions before Linux/macOS equivalents. Screenshots and examples use Windows Command Prompt, and Windows-specific tools (setx, PowerShell) are highlighted. Although Linux/macOS instructions are present, they are secondary and less visually emphasized. No Linux-specific tools or screenshots are provided.
Recommendations
  • Present Linux/macOS instructions before or alongside Windows instructions, rather than always after.
  • Include screenshots of the app running in Linux/macOS terminals to balance visual representation.
  • Highlight cross-platform command-line usage (e.g., bash, sh) and avoid Windows-centric tools like setx where possible.
  • Explicitly mention that all steps are supported equally on Linux/macOS, and provide troubleshooting tips for those platforms.
  • Ensure parity in example code and environment variable setup, possibly using .env files or platform-neutral approaches.
GitHub Create Pull Request
Azure App Configuration Tutorial: Use dynamic configuration in a .NET background service ...enable-dynamic-configuration-dotnet-background-service.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
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 Windows tool usage (cmd, PowerShell) with detailed steps. While Linux/macOS commands are present, Windows instructions are consistently listed first, and there is more detail about Windows-specific behaviors (such as needing to restart the command prompt after setx). There is also a slight emphasis on Windows tools and patterns, such as referencing Visual Studio (though the .NET CLI is recommended for cross-platform use).
Recommendations
  • Present Linux/macOS and Windows instructions in parallel tabs or in the same order to avoid prioritizing Windows.
  • Provide equal detail for Linux/macOS instructions (e.g., mention if a shell restart is needed after export, as is done for Windows setx).
  • Where possible, use cross-platform commands or highlight the .NET CLI as the primary tool, minimizing references to Windows-specific tools or patterns.
  • Consider starting with Linux/macOS examples or alternating the order in which platforms are presented.
  • Explicitly state that all steps are cross-platform unless there are genuine platform-specific differences.
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
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by presenting Windows command prompt and PowerShell instructions before macOS and Linux equivalents, and by referencing Windows-specific tools and patterns (e.g., Visual Studio Code as 'available on Windows, macOS, and Linux' but with a subtle Windows-first tone). The example project is based on ASP.NET Core, which is cross-platform, but the build instructions and environment variable setup are presented in a way that prioritizes Windows users. There is also a reliance on MSBuild and .csproj scripting, which are more familiar to Windows developers.
Recommendations
  • Present Linux and macOS instructions before or alongside Windows instructions, rather than after.
  • Include bash/zsh examples for scripting and environment variable setup, and highlight cross-platform compatibility.
  • Mention cross-platform editors and tools (e.g., VS Code, JetBrains Rider) equally, without a Windows-first tone.
  • Clarify that MSBuild and .csproj scripting can be used on Linux and macOS with .NET Core SDK.
  • Add explicit notes or sections for CI/CD pipelines commonly used on Linux (e.g., GitHub Actions, Jenkins) in addition to Azure DevOps.
  • Ensure all code snippets and commands are tested and presented for all supported platforms.
GitHub Create Pull Request
Azure App Configuration Use variant feature flags in a Python application ...pp-configuration/howto-variant-feature-flags-python.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits Windows bias in several ways: Windows setup instructions and links are given first in the prerequisites, virtual environment activation is shown only with the Windows path, and environment variable setup provides detailed Windows Command Prompt and PowerShell instructions before mentioning the Linux/macOS alternative. There are no Linux-specific examples for virtual environment activation or other common Linux workflows, and no parity in tool recommendations or troubleshooting for non-Windows platforms.
Recommendations
  • Provide Linux/macOS instructions alongside Windows instructions, not after them, and ensure equal detail.
  • Include the Linux/macOS command for activating a Python virtual environment (e.g., `source venv/bin/activate`).
  • Link to Python installation documentation for Linux/macOS, not just Windows.
  • When listing environment variable setup, present all platforms together or alternate the order to avoid Windows-first bias.
  • Add troubleshooting notes or tips for common Linux/macOS issues (e.g., permissions, package managers).
  • Review all code snippets and instructions to ensure they are platform-agnostic or provide alternatives for each major OS.
GitHub Create Pull Request
Azure App Configuration Quickstart for Azure App Configuration with Azure Functions | Microsoft Docs ...app-configuration/quickstart-azure-functions-csharp.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 5 bias types
Detected Bias Types
Windows First Visual Studio Only Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows tools and workflows. Visual Studio is the only development environment mentioned, and instructions for creating and running the function app are centered on Visual Studio. Environment variable setup lists Windows command prompt and PowerShell before Linux/macOS, and screenshots and debugging steps are Visual Studio-specific. There is no mention of cross-platform editors (e.g., VS Code) or Linux-native development workflows, nor are there CLI-based alternatives for creating and running the function app.
Recommendations
  • Add instructions for creating and running Azure Functions apps using cross-platform tools such as Visual Studio Code and Azure Functions Core Tools CLI.
  • Provide Linux/macOS examples and workflows alongside Windows instructions, including screenshots and step-by-step guides.
  • List environment variable setup commands for Linux/macOS before or alongside Windows commands to avoid ordering bias.
  • Include references to platform-agnostic development environments and clarify that Azure Functions development is supported on Linux/macOS.
  • Offer guidance for users who do not use Visual Studio, such as how to debug and run locally using CLI tools.
GitHub Create Pull Request
Azure App Configuration Quickstart for Azure App Configuration with .NET Framework ...icles/azure-app-configuration/quickstart-dotnet-app.md
High Priority View Details →
Scanned: 2026-01-12 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 Windows bias by prioritizing Windows tools and workflows. Visual Studio (Windows-only) is the sole IDE mentioned, and all project creation steps assume its use. Environment variable instructions list Windows Command Prompt and PowerShell before Linux/macOS, and use setx (Windows-specific) as the primary example. There are no Linux-specific development environment instructions, nor any mention of cross-platform .NET development tools (e.g., VS Code, JetBrains Rider, or CLI-only workflows). The configuration file examples and build/run instructions are tailored to Windows conventions, with no guidance for Linux users on compiling or running .NET Framework apps.
Recommendations
  • Include instructions for creating and running the app using cross-platform tools such as Visual Studio Code or JetBrains Rider, and .NET CLI where possible.
  • Provide Linux/macOS-specific steps for project setup, environment variable management, and running the application, including terminal commands and any required dependencies.
  • List Linux/macOS commands before or alongside Windows commands to avoid implicit prioritization.
  • Clarify that .NET Framework is Windows-only, and suggest .NET Core/.NET 6+ for cross-platform scenarios, with links to equivalent quickstarts.
  • Add troubleshooting notes for Linux/macOS users, especially regarding environment variables and compatibility.
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
High Priority View Details →
Scanned: 2026-01-12 00:00
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), referencing Visual Studio as the only IDE, and showing screenshots from Windows Command Prompt. There are no examples or instructions for Linux or macOS users (e.g., Bash, zsh, VS Code, or cross-platform .NET CLI usage). This may hinder Linux developers from following the quickstart without additional research.
Recommendations
  • Add equivalent Linux/macOS instructions for setting environment variables (e.g., export Endpoint="..." in Bash/zsh).
  • Include cross-platform IDE options such as Visual Studio Code and .NET CLI commands for project creation and running.
  • Provide screenshots or terminal output examples from Linux/macOS environments.
  • Explicitly mention that the quickstart applies to non-Windows platforms and provide guidance for those users.
  • Where PowerShell is referenced, also provide Bash/zsh equivalents.
  • Consider a 'platform tabs' approach for steps that differ between Windows, Linux, and macOS.
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
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Visual Studio Only Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows tools and workflows. Visual Studio is listed as the only required IDE, with no mention of cross-platform alternatives like VS Code. Environment variable instructions are given first for Windows Command Prompt and PowerShell, with Linux/macOS examples listed last. The local testing workflow is tightly coupled to Visual Studio, which is primarily a Windows tool, and there are no instructions for running or debugging the function app on Linux (e.g., via Azure Functions Core Tools CLI or VS Code).
Recommendations
  • Add instructions for using VS Code or other cross-platform editors to create and debug Azure Functions apps.
  • Provide parity in environment variable setup instructions, listing Linux/macOS commands before or alongside Windows commands.
  • Include steps for running and debugging the function locally using Azure Functions Core Tools CLI on Linux/macOS.
  • Clarify that Visual Studio is optional and provide alternative workflows for non-Windows users.
  • Ensure screenshots and examples reflect cross-platform usage, not just Visual Studio on Windows.
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
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias in several ways: Windows-specific instructions (Windows command prompt and PowerShell) are presented before macOS and Linux equivalents, with more detailed guidance and validation steps for Windows users. The prerequisite section links to Windows Python setup documentation first, and Windows environment variable tools (setx, PowerShell) are described in greater detail than their Unix counterparts. Linux and macOS instructions are present but appear after Windows and are less emphasized.
Recommendations
  • Present OS instructions in parallel tabs or in a neutral order (e.g., alphabetical: Linux, macOS, Windows) rather than Windows-first.
  • Provide equal detail and validation steps for Linux/macOS as for Windows, including how to check environment variable persistence.
  • Include links to Linux and macOS Python setup documentation in the prerequisites section alongside the Windows link.
  • Avoid using Windows-specific tools (e.g., setx) without mentioning Unix equivalents (e.g., export in .bashrc/.zshrc for persistence).
  • Ensure screenshots and examples do not implicitly favor Windows environments.
  • Explicitly state cross-platform compatibility and highlight any OS-specific caveats.
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
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides deployment instructions using PowerShell cmdlets only, which are primarily associated with Windows environments. There are no examples or guidance for deploying the ARM template using Azure CLI, Bash, or other cross-platform tools. The PowerShell example is given as the sole command-line option, and no Linux/macOS-specific instructions or parity are present.
Recommendations
  • Add equivalent Azure CLI examples for deploying the ARM template, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Clearly mention that both PowerShell and Azure CLI can be used, and provide links to relevant Azure CLI documentation.
  • Consider including Bash script snippets or instructions for users on Linux/macOS.
  • Ensure that references to command-line tools do not assume a Windows environment by default.
GitHub Create Pull Request
Azure App Configuration Azure App Configuration REST API - Microsoft Entra authorization ...e-app-configuration/rest-api-authorization-azure-ad.md
High Priority View Details →
Scanned: 2026-01-12 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 mentions Azure CLI, PowerShell, and the Azure portal as tools for managing role assignments, listing PowerShell before Linux-native alternatives and referencing the portal (which is platform-agnostic but often associated with Windows environments). There are no explicit Linux or bash examples, nor is there mention of Linux-specific tools or patterns. The lack of Linux command-line examples and the ordering of tools suggest a Windows-first and PowerShell-heavy bias.
Recommendations
  • Provide explicit bash/Linux shell examples for managing role assignments using Azure CLI.
  • List Azure CLI (cross-platform) before PowerShell when mentioning command-line tools.
  • Include references or links to Linux-specific documentation or usage patterns.
  • Clarify that Azure CLI is available and supported on Linux, macOS, and Windows.
  • Add examples showing role assignment management from a Linux environment.
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
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias in several ways. Windows-specific instructions and tools (such as setx and PowerShell) are presented before their Linux/macOS equivalents. The environment variable setup section gives Windows Command Prompt and PowerShell examples first, with Linux/macOS instructions following. The use of Windows-centric tools and patterns (setx, PowerShell) is emphasized, while Linux alternatives are less detailed. Screenshots and portal instructions are platform-neutral, but command-line and environment setup favor Windows.
Recommendations
  • Present Linux/macOS and Windows instructions side-by-side or in parallel tabs, rather than listing Windows first.
  • Provide more detailed Linux/macOS instructions, including shell-specific notes (e.g., bash, zsh) and persistence of environment variables.
  • Avoid using Windows-specific tools (like setx) without mentioning cross-platform alternatives (e.g., editing ~/.bashrc or ~/.profile for Linux/macOS).
  • Where possible, use platform-neutral commands and highlight cross-platform editors and tools.
  • Consider adding a table or section summarizing environment variable setup for all major platforms.
GitHub Create Pull Request
Azure App Configuration Tutorial: Use dynamic configuration in a .NET app ...figuration/enable-dynamic-configuration-dotnet-core.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a mild Windows bias. When setting environment variables, Windows command prompt and PowerShell instructions are presented first, followed by macOS/Linux. Screenshots and examples reference Windows tools (Command Prompt, PowerShell) and terminology. There is no explicit omission of Linux/macOS instructions, but Windows-centric patterns and tools are prioritized or highlighted.
Recommendations
  • Present cross-platform instructions in parallel or start with a neutral or alphabetical order (e.g., Linux/macOS, then Windows).
  • Include screenshots or references to Linux/macOS terminals where applicable, not just Windows Command Prompt or PowerShell.
  • Avoid language that assumes Windows as the default environment (e.g., 'Press Enter in the Command Prompt or PowerShell window').
  • Where possible, clarify that all steps apply equally to Linux/macOS and Windows, and mention common Linux/macOS editors (e.g., Vim, nano) alongside Visual Studio Code.
  • Consider adding troubleshooting notes or tips for Linux/macOS users, especially where behavior may differ (e.g., environment variable persistence).
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
High Priority View Details →
Scanned: 2026-01-11 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 demonstrates a Windows-first bias by presenting Windows Command Prompt and PowerShell instructions before Linux/macOS equivalents. Windows-specific tools (Command Prompt, PowerShell) are highlighted, and screenshots show Windows environments. While Linux/macOS commands are included, they are listed after Windows instructions and lack parity in visual aids (e.g., screenshots). There is no explicit Linux-focused example or troubleshooting guidance, and the overall flow assumes familiarity with Windows tooling.
Recommendations
  • Present Linux/macOS instructions before or alongside Windows instructions, not after.
  • Include screenshots or terminal output from Linux/macOS environments to match Windows visuals.
  • Add troubleshooting notes or tips for Linux/macOS users, especially regarding environment variable persistence and shell differences.
  • Explicitly state cross-platform compatibility in each step, and avoid implying Windows is the default or primary environment.
  • Consider providing bash scripts or .sh files for Linux/macOS users, similar to batch files for Windows.
  • Review terminology to ensure Windows-specific terms are not used generically (e.g., 'Command Prompt window' vs. 'terminal').
GitHub Create Pull Request
Azure App Configuration Quickstart to learn how to use Azure App Configuration .../azure-app-configuration/quickstart-java-spring-app.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias in several ways: Windows command-line instructions (setx, PowerShell) are presented before Linux/macOS equivalents, with explicit mention of Windows-specific tools and patterns. The environment variable setup section lists Windows (cmd, PowerShell) commands first, followed by macOS/Linux. The build/run instructions use 'command prompt' terminology, which is Windows-centric, and all command examples use Windows-style prompts. Linux instructions are present but are secondary.
Recommendations
  • Present Linux/macOS and Windows instructions in parallel, or alternate which platform is listed first.
  • Use neutral terminology such as 'terminal' instead of 'command prompt' when referring to the shell.
  • Include Linux/macOS-specific examples and explanations with equal prominence and detail as Windows.
  • Where possible, use cross-platform commands and avoid Windows-only tools (e.g., 'setx').
  • Add a table or tabs for platform-specific instructions to improve clarity and parity.
GitHub Create Pull Request
Azure App Configuration Tutorial for using Azure App Configuration dynamic configuration in an ASP.NET web application (.NET Framework) | Microsoft Docs ...iguration/enable-dynamic-configuration-aspnet-netfx.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily oriented towards Windows development environments. Visual Studio (Windows-only for .NET Framework) is the only IDE mentioned, and all project setup instructions assume use of Windows and Visual Studio. Environment variable setup instructions list Windows Command Prompt and PowerShell before Linux/macOS equivalents, and PowerShell examples are provided for both authentication methods. There are no Linux-specific development instructions, nor is Mono or cross-platform .NET mentioned as alternatives. The tutorial is for ASP.NET Web Forms (.NET Framework), which is not supported on Linux, but this limitation is not explicitly stated.
Recommendations
  • Explicitly state that ASP.NET Web Forms (.NET Framework) is Windows-only and not supported on Linux/macOS.
  • If possible, provide alternative instructions or links for cross-platform ASP.NET development (e.g., ASP.NET Core) and clarify platform limitations.
  • Mention Mono as a possible (though limited) way to run .NET Framework apps on Linux, with caveats.
  • List Linux/macOS environment variable commands before or alongside Windows commands to avoid Windows-first ordering.
  • Reduce reliance on Windows-specific tools (Visual Studio, PowerShell) or provide parity instructions for Linux/macOS (e.g., using VS Code, JetBrains Rider, or CLI tools).
  • Add a section on developing and testing with cross-platform .NET (if applicable), or link to relevant cross-platform tutorials.
GitHub Create Pull Request
Azure App Configuration Tutorial: Use dynamic configuration in a .NET background service ...enable-dynamic-configuration-dotnet-background-service.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
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 gives more detailed guidance for Windows users (e.g., instructing to restart the command prompt after setx). Windows command-line tools (cmd, PowerShell) are mentioned explicitly and before Linux equivalents. However, Linux/macOS examples are present and not omitted, and the .NET CLI is correctly described as cross-platform.
Recommendations
  • Present Linux/macOS and Windows instructions in parallel or in a tabbed format, rather than listing Windows first.
  • Avoid giving extra detail or emphasis to Windows-specific steps (e.g., the note about restarting the command prompt after setx) unless a similar level of detail is provided for Linux/macOS.
  • Where possible, use cross-platform commands or highlight that the .NET CLI works identically on all platforms.
  • Consider leading with Linux/macOS examples or alternating the order to avoid implicit prioritization of Windows.
  • Ensure all screenshots and UI references are either cross-platform or include Linux/macOS variants if relevant.
GitHub Create Pull Request
Azure App Configuration Use variant feature flags in a Python application ...pp-configuration/howto-variant-feature-flags-python.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates Windows bias in several ways. In the prerequisites, it links only to Windows-specific Python setup documentation. When describing how to activate the Python virtual environment, it provides only the Windows command ('.\venv\Scripts\Activate') and omits the Linux/macOS equivalent ('source venv/bin/activate'). In the section on setting environment variables, Windows Command Prompt and PowerShell instructions are given first and in more detail, while the Linux/macOS example is listed last and lacks explanation. There are no Linux-specific troubleshooting tips or references to Linux tools.
Recommendations
  • Provide both Windows and Linux/macOS commands for activating Python virtual environments (e.g., 'source venv/bin/activate' for Linux/macOS).
  • Include links to Python installation/setup documentation for Linux and macOS in the prerequisites.
  • When listing environment variable commands, present Linux/macOS instructions first or alongside Windows instructions, and explain any differences.
  • Add troubleshooting notes or tips for common Linux/macOS issues (e.g., permissions, package installation).
  • Ensure all CLI instructions are cross-platform or clearly marked for each OS.
GitHub Create Pull Request
← Previous Page 1 of 19 Next →