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 251-275 of 479 flagged pages
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/howto-labels-aspnet-core.md ...es/azure-app-configuration/howto-labels-aspnet-core.md
Medium Priority View Details →
Scanned: 2025-08-22 00:01
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates per-environment configuration using Azure App Configuration in the context of an ASP.NET Core application. It references modifying 'launchSettings.json' and uses .NET CLI commands, but only describes environment setup via 'launchSettings.json', which is a Visual Studio/Windows-centric pattern. There are no examples or instructions for setting environment variables or running the app in Linux or macOS environments, nor is there mention of cross-platform development tools or patterns.
Recommendations
  • Add instructions for setting environment variables in Linux/macOS (e.g., using export in bash or setting variables inline before dotnet run).
  • Mention alternative to 'launchSettings.json' for non-Windows environments, such as using shell environment variables or .env files.
  • Provide explicit examples for running the application in Linux/macOS terminals.
  • Clarify that the .NET CLI is cross-platform, and show parity in environment setup across operating systems.
GitHub Create Pull Request
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/reference-dotnet-provider.md ...s/azure-app-configuration/reference-dotnet-provider.md
Medium Priority View Details →
Scanned: 2025-08-21 00:01
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively provides .NET/C# code samples and instructions, which are platform-neutral at the code level but implicitly favor Windows environments by omitting any Linux-specific guidance, shell commands, or cross-platform considerations. All package installation examples use 'dotnet' CLI, which is available on Linux, but there are no explicit references to Linux environments, shell usage, or alternative patterns for Linux users. There is no mention of Powershell, but the documentation assumes a Windows-centric context by focusing on ASP.NET and .NET Core without acknowledging Linux deployment scenarios.
Recommendations
  • Add explicit notes confirming that all instructions and code samples work on Linux as well as Windows.
  • Include Linux-specific examples, such as using bash/zsh to set environment variables (e.g., 'export AppConfigurationEndpoint=...') alongside Windows examples.
  • Mention Linux deployment scenarios (e.g., running .NET apps on Ubuntu, Docker containers, or Azure App Service for Linux) and provide links to relevant documentation.
  • Clarify that the 'dotnet' CLI commands are cross-platform and provide troubleshooting tips for common Linux issues (e.g., file permissions, environment variable case sensitivity).
  • Where environment variables are referenced, show both Windows (set) and Linux (export) syntax.
GitHub Create Pull Request
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/emulator-overview.md .../articles/azure-app-configuration/emulator-overview.md
Medium Priority View Details →
Scanned: 2025-08-21 00:01
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation generally uses cross-platform tools (Docker, .NET, Git) and console commands, which are not inherently Windows-specific. However, in the Docker run example with persisted data, the bind mount path uses a Windows-style path (C:\aace:/app/.aace) without providing a Linux/macOS equivalent. There are no explicit Linux/macOS examples for bind mounts or file paths, and the only file path example is Windows-specific. This may cause confusion or extra effort for Linux/macOS users.
Recommendations
  • Provide both Windows and Linux/macOS examples for Docker bind mounts. For example, include a Linux example like: -v "$HOME/.aace:/app/.aace".
  • When showing file paths, present both Windows and Unix-style paths side by side or in tabs.
  • Explicitly mention that the console commands work on all platforms, and clarify any platform-specific differences.
  • Consider adding a note or section for Linux/macOS users to ensure parity and clarity.
GitHub Create Pull Request
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/howto-labels-aspnet-core.md ...es/azure-app-configuration/howto-labels-aspnet-core.md
Medium Priority View Details →
Scanned: 2025-08-21 00:01
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation focuses exclusively on ASP.NET Core and .NET tooling, referencing only the 'launchSettings.json' file and environment variable configuration patterns typical of Windows development environments. There are no examples or guidance for setting environment variables or running the application in Linux or cross-platform scenarios, and the workflow assumes Visual Studio or similar Windows-centric tooling.
Recommendations
  • Include instructions for setting environment variables on Linux/macOS (e.g., using 'export ASPNETCORE_ENVIRONMENT=Production' in the shell).
  • Show how to run the application from the command line in Linux/macOS environments, not just via 'dotnet run' with 'launchSettings.json'.
  • Mention that 'launchSettings.json' is primarily used by Visual Studio and may not apply in non-Windows or non-IDE scenarios.
  • Add a section or callout for cross-platform developers, clarifying how to configure and test environment-specific settings outside of Windows.
  • Provide equivalent bash/zsh shell commands alongside any Windows/Visual Studio-specific instructions.
GitHub Create Pull Request
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-go-web-app.md ...icles/azure-app-configuration/quickstart-go-web-app.md
Medium Priority View Details →
Scanned: 2025-08-18 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS, and includes both setx (cmd) and PowerShell examples. Linux/macOS instructions are present but always listed last. There are no missing Linux examples, but the ordering and explicit inclusion of multiple Windows shell types (cmd, PowerShell) before Linux suggests a mild Windows-first bias.
Recommendations
  • Alternate the order of platform instructions (sometimes list Linux/macOS first, or use tabs for OS selection).
  • Use tabbed or dropdown UI for OS-specific instructions to avoid implicit prioritization.
  • Ensure parity in detail and clarity for Linux/macOS instructions (which is already good here).
  • Consider mentioning cross-platform tools (e.g., direnv, dotenv) for environment variable management.
  • Explicitly state that all commands are cross-platform unless otherwise noted.
GitHub Create Pull Request
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-go-web-app.md ...icles/azure-app-configuration/quickstart-go-web-app.md
Medium Priority View Details →
Scanned: 2025-08-12 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS, and includes both setx (cmd) and PowerShell commands, which can be seen as a Windows-first and PowerShell-heavy approach. Linux/macOS instructions are present but always listed after Windows. No Linux-specific tools or patterns are missing, but the ordering and emphasis favor Windows users.
Recommendations
  • Present Linux/macOS and Windows instructions in parallel (side-by-side tabs or columns), or alternate which platform is listed first to avoid implicit prioritization.
  • Avoid giving more detailed or multiple options for Windows (e.g., both cmd and PowerShell) unless parity is provided for Linux/macOS (e.g., bash and zsh).
  • Consider a platform-agnostic approach first (e.g., using cross-platform scripts or highlighting environment variable setup in Go code), then provide platform-specific details as needed.
  • Explicitly state that all platforms are supported and tested, and encourage contributions or feedback from non-Windows users.
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
Medium Priority View Details →
Scanned: 2025-08-12 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS, and includes detailed PowerShell and Windows Command Prompt commands. Linux/macOS instructions are present but listed after Windows, indicating a 'windows_first' ordering and a slight emphasis on Windows tooling.
Recommendations
  • Present Linux/macOS and Windows instructions in parallel (side-by-side tabs or equal prominence), or list Linux/macOS first to reflect Go's cross-platform nature.
  • Avoid giving Windows-specific instructions (cmd, PowerShell) priority over bash equivalents.
  • Consider using tabbed instructions for each OS shell (cmd, PowerShell, bash/zsh) to avoid implicit prioritization.
  • Explicitly mention that all steps are cross-platform unless a step is truly OS-specific.
  • Where possible, use cross-platform commands (e.g., 'env' files, or platform-agnostic tooling) and highlight them.
GitHub Create Pull Request
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-go-web-app.md ...icles/azure-app-configuration/quickstart-go-web-app.md
Medium Priority View Details →
Scanned: 2025-08-11 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS, and provides detailed PowerShell and Windows Command Prompt commands. While Linux/macOS instructions are present, Windows tools and patterns are consistently mentioned first, which may signal a subtle Windows-first bias.
Recommendations
  • Present Linux/macOS and Windows instructions in parallel (side-by-side tabs or equal prominence), or alternate which platform is shown first.
  • Avoid giving Windows (cmd/PowerShell) instructions before Linux/macOS unless there is a technical reason.
  • Where possible, use cross-platform commands (e.g., only bash, or note platform differences in a neutral way).
  • Consider providing a table or tabbed interface for environment variable setup, with equal visibility for all platforms.
  • Review for any other subtle prioritization of Windows tools or patterns, and ensure Linux/macOS users receive equally detailed guidance.
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
Medium Priority View Details →
Scanned: 2025-08-11 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation is focused exclusively on ASP.NET Core and C# usage, with all code samples and instructions tailored to this stack. There are no examples or instructions for Linux environments, non-Windows development, or cross-platform command-line usage. The workflow assumes use of the Azure Portal and .NET tooling, which are available cross-platform, but the absence of explicit Linux or CLI examples and the focus on ASP.NET Core may implicitly prioritize Windows users.
Recommendations
  • Add explicit instructions or notes clarifying that ASP.NET Core and the Azure SDK are cross-platform, and that the steps apply equally on Linux and macOS.
  • Include examples of how to perform relevant steps using the Azure CLI or Azure PowerShell, and clarify that these tools are available on all major platforms.
  • Provide sample code or terminal commands for Linux/macOS environments, such as how to navigate to the project directory, edit files, or run the application.
  • Mention any platform-specific considerations (if any) for Linux users, such as environment variable configuration or certificate handling.
  • Balance the documentation by including at least one Linux/macOS terminal example alongside any Windows-centric instructions.
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
Medium Priority View Details →
Scanned: 2025-08-11 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS, and includes explicit PowerShell and Windows Command Prompt examples. While Linux/macOS examples 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). No Linux tools are omitted, but the ordering and emphasis favor Windows users.
Recommendations
  • Alternate the order of platform instructions so that Linux/macOS examples are sometimes presented first, or group all platform instructions together without prioritizing Windows.
  • Use platform-agnostic language where possible (e.g., 'Set the environment variable using your shell').
  • Add notes about shell session persistence for both Windows and Linux/macOS (e.g., mention that 'export' only affects the current shell session).
  • Consider using tabbed or collapsible sections for platform-specific instructions to avoid implicit prioritization.
  • Ensure parity in detail for all platforms (e.g., if you mention restarting the shell for setx on Windows, mention that 'export' is session-scoped on Linux/macOS).
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
Medium Priority View Details →
Scanned: 2025-08-10 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS, and includes both setx (cmd) and PowerShell commands, which may signal a Windows-first approach. However, Linux/macOS instructions are present and correct. There are no missing Linux examples, and no exclusive use of Windows tools or patterns elsewhere in the guide.
Recommendations
  • Present Linux/macOS instructions before or alongside Windows instructions, rather than after.
  • Consider grouping environment variable instructions by platform with equal prominence, or use tabbed sections for each OS.
  • If possible, provide a single cross-platform command (e.g., using a tool like direnv or dotenv) or clarify that the Go application will work identically on all platforms once the variable is set.
  • Avoid giving more detailed or prominent instructions for Windows than for Linux/macOS.
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
Medium Priority View Details →
Scanned: 2025-08-10 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page assumes the use of ASP.NET Core and provides instructions and code samples exclusively for that environment, which is most commonly associated with Windows development. There are no explicit Linux or cross-platform instructions, nor are there any command-line examples (such as Bash or CLI) for Linux users. The portal navigation and terminology also implicitly assume familiarity with Windows-centric workflows.
Recommendations
  • Include explicit notes or sections on how to perform the same steps on Linux or macOS, especially for developers running ASP.NET Core on non-Windows platforms.
  • Provide command-line examples using Azure CLI or Bash scripts for tasks like adding Key Vault references, in addition to or instead of portal instructions.
  • Clarify that the instructions and code samples are cross-platform where applicable, and mention any platform-specific considerations.
  • Add troubleshooting tips or links for common issues encountered on Linux (e.g., file permissions, environment variables, certificate handling).
GitHub Create Pull Request
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-go-web-app.md ...icles/azure-app-configuration/quickstart-go-web-app.md
Medium Priority View Details →
Scanned: 2025-08-10 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS, and includes both setx (cmd) and PowerShell examples, which can be seen as a 'windows_first' and 'powershell_heavy' bias. Linux/macOS instructions are present but always listed after Windows. No Linux-specific tools or patterns are omitted, but the ordering and prominence of Windows tooling is evident.
Recommendations
  • Present Linux/macOS and Windows instructions in parallel tabs or side-by-side, rather than always listing Windows first.
  • If using sequential instructions, alternate the order (sometimes Linux/macOS first) or clarify that the order does not imply priority.
  • Consider using tabbed content blocks for each platform (Windows cmd, PowerShell, Linux/macOS) to provide equal visibility.
  • Ensure that Linux/macOS users see their instructions as prominently and as early as Windows users.
  • Where possible, use cross-platform commands (e.g., via Azure CLI) as the primary example, with platform-specific notes as needed.
GitHub Create Pull Request
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-go-web-app.md ...icles/azure-app-configuration/quickstart-go-web-app.md
Medium Priority View Details →
Scanned: 2025-08-09 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents environment variable setup instructions for Windows (Command Prompt and PowerShell) before Linux/macOS, and provides both setx (cmd) and PowerShell commands, which are Windows-specific. Linux/macOS instructions are present but always listed last. There are no missing Linux examples, but the ordering and inclusion of multiple Windows shell variants may subtly prioritize Windows users.
Recommendations
  • Alternate the order of platform instructions (sometimes show Linux/macOS first, or group all platforms equally).
  • Consider grouping all environment variable instructions together in a table or tabbed interface, so no platform is visually prioritized.
  • Avoid providing multiple Windows shell variants unless truly necessary, or provide equivalent depth for Linux (e.g., bash, zsh, fish).
  • Explicitly state that all steps are cross-platform except where noted, to reinforce parity.
  • Where possible, use platform-agnostic language and examples (e.g., 'set the environment variable' rather than 'run this Windows command').
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
Medium Priority View Details →
Scanned: 2025-08-09 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS, and includes both setx (cmd) and PowerShell examples, which may give the impression of Windows prioritization. Linux/macOS instructions are present but always listed last. There are no missing Linux examples, but the ordering and inclusion of multiple Windows-specific command shells (cmd, PowerShell) versus a single Linux shell (bash) is evidence of subtle Windows bias.
Recommendations
  • Alternate the order of platform instructions (sometimes list Linux/macOS first, or use tabs for OS selection).
  • Use tabbed or dropdown UI for platform-specific instructions to give equal prominence to Windows and Linux/macOS.
  • Where possible, group all OS instructions together rather than listing Windows (cmd, PowerShell) first.
  • Explicitly mention that all platforms are supported and that the Go code is cross-platform.
  • Consider providing a table summarizing commands for all platforms for quick reference.
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
Medium Priority View Details →
Scanned: 2025-08-09 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation focuses exclusively on ASP.NET Core and C# examples, which are most commonly associated with Windows development. There are no Linux-specific instructions, shell commands, or cross-platform considerations. All steps assume use of the Azure Portal or .NET/C# tooling, with no mention of Linux command-line tools or alternative frameworks. The prerequisites and code samples are tailored to Windows-centric development environments.
Recommendations
  • Include equivalent instructions and code samples for Linux environments, such as using the Azure CLI in Bash to configure Key Vault and App Configuration.
  • Mention that ASP.NET Core is cross-platform and provide explicit guidance for Linux/macOS users, including any differences in environment setup or deployment.
  • Add examples or notes for other programming languages or frameworks commonly used on Linux, if relevant.
  • Clarify that the steps and code samples are applicable on both Windows and Linux, and highlight any OS-specific considerations.
  • Provide shell script (Bash) alternatives for any steps that can be automated, especially for resource creation and configuration.
GitHub Create Pull Request
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-go-web-app.md ...icles/azure-app-configuration/quickstart-go-web-app.md
Medium Priority View Details →
Scanned: 2025-08-08 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides environment variable setup instructions for all major platforms (Windows Command Prompt, PowerShell, macOS/Linux), but consistently lists Windows (cmd and PowerShell) before Linux/macOS. PowerShell and Windows command prompt commands are given equal or greater prominence than bash equivalents, and Windows-specific tools (setx) are mentioned. However, Linux/macOS instructions are present and not omitted.
Recommendations
  • Alternate the order of platform instructions so that Linux/macOS examples are sometimes listed first, especially for Go, which is popular on Linux.
  • Group environment variable instructions by platform or provide tabs for each OS to avoid implicit prioritization.
  • Consider using cross-platform language in introductory text (e.g., 'On Linux, macOS, or Windows...') rather than always leading with Windows.
  • Where possible, avoid Windows-specific tools like 'setx' in favor of universally available commands, or clearly indicate their platform specificity.
  • Ensure parity in troubleshooting and advanced sections, if present, so Linux users are not left out.
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
Medium Priority View Details →
Scanned: 2025-08-08 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS, and includes both setx (cmd) and PowerShell commands, which may suggest a Windows-first perspective. However, Linux/macOS instructions are present and correct. There are no missing Linux examples, and no exclusive mention of Windows-only tools beyond environment variable setup.
Recommendations
  • Present Linux/macOS and Windows instructions in parallel tabs or in a consistent order (e.g., Linux/macOS first, or alphabetical).
  • Consider using tabbed sections for OS-specific instructions to avoid implying priority.
  • Ensure that all CLI examples (such as az login) are clearly marked as cross-platform.
  • If possible, provide a single cross-platform command (e.g., using the Azure CLI or Go itself) for setting environment variables, or explain the differences succinctly.
  • Review future documentation for subtle ordering or emphasis that may suggest Windows is the primary or default platform.
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
Medium Priority View Details →
Scanned: 2025-08-08 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation focuses exclusively on ASP.NET Core and C# in the context of Azure App Configuration and Key Vault, with all code and workflow examples tailored to .NET developers. There are no references to Linux-specific workflows, tools, or cross-platform command-line instructions. The instructions assume use of the Azure Portal and Visual Studio-style project structures, which are more common in Windows environments. No Linux shell, CLI, or cross-platform automation examples are provided.
Recommendations
  • Include equivalent examples for Linux environments, such as using the Azure CLI or Bash scripts to automate certificate and secret management.
  • Provide guidance for developers using non-Windows platforms (e.g., how to set up and run the sample code on Linux or macOS).
  • Mention cross-platform development environments and editors (such as VS Code) and ensure instructions are not tied to Windows-specific tools.
  • Add notes or sections on how to perform App Configuration and Key Vault operations using command-line tools available on Linux.
  • Clarify that the instructions are applicable cross-platform, or explicitly provide parity for Linux users.
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
Medium Priority View Details →
Scanned: 2025-08-07 00:00
Reviewed by: Unknown
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 macOS/Linux (bash), and gives both setx (cmd) and PowerShell examples, which can be seen as a Windows-first and PowerShell-heavy approach. However, Linux/macOS instructions are present and not omitted.
Recommendations
  • Present Linux/macOS (bash) instructions before or alongside Windows instructions to avoid Windows-first ordering.
  • Group all OS-specific instructions in a table or side-by-side tabs for equal visibility.
  • Avoid giving multiple Windows-specific methods (cmd and PowerShell) unless also providing equivalent alternatives for Linux/macOS (e.g., bash and zsh).
  • Explicitly mention that all platforms are supported and tested, and provide troubleshooting tips for Linux/macOS users if relevant.
GitHub Create Pull Request
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-go-web-app.md ...icles/azure-app-configuration/quickstart-go-web-app.md
Medium Priority View Details →
Scanned: 2025-08-07 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS, and includes both Windows Command Prompt and PowerShell commands, which can be seen as a Windows-first and PowerShell-heavy approach. Linux/macOS instructions are present but always listed after Windows instructions. There are no missing Linux examples or exclusive use of Windows tools, but the ordering and emphasis could be improved for parity.
Recommendations
  • Alternate the order of OS instructions, sometimes listing Linux/macOS first to avoid implicit prioritization of Windows.
  • Group OS-specific instructions in tabs or collapsible sections to give equal prominence to all platforms.
  • Explicitly state that all platforms are supported and that the instructions are equivalent, to reinforce parity.
  • Consider reducing the number of separate Windows command examples (cmd and PowerShell) if not strictly necessary, or provide a rationale for their inclusion.
  • Where possible, use cross-platform commands (like 'export' for environment variables) in the main flow, and move OS-specific details to an appendix or footnote.
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
Medium Priority View Details →
Scanned: 2025-08-07 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation page focuses exclusively on ASP.NET Core and Azure services, providing instructions and code samples only for C# and .NET environments. There are no references to Linux-specific workflows, tools, or command-line instructions (e.g., Bash), nor are there cross-platform considerations or examples. The instructions assume use of the Azure Portal (web UI) and .NET, which are available on both Windows and Linux, but the lack of explicit Linux parity (such as CLI examples or Linux-specific notes) may disadvantage Linux users. The structure and language implicitly prioritize Windows-centric development patterns.
Recommendations
  • Add equivalent instructions and examples for Linux environments, such as using the Azure CLI (az) or Bash scripts to perform tasks like adding Key Vault references or managing App Configuration.
  • Include notes or sections that clarify cross-platform compatibility, especially for .NET Core/ASP.NET Core projects that run on Linux.
  • Provide sample commands for both PowerShell (if used) and Bash where relevant.
  • Mention and link to Linux-specific documentation or troubleshooting guides for common issues encountered on Linux.
  • Explicitly state that the steps and code samples are applicable to both Windows and Linux, or highlight any differences.
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
Medium Priority View Details →
Scanned: 2025-08-06 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS, and includes both setx (cmd) and PowerShell examples, which can be seen as a Windows-first and PowerShell-heavy approach. Linux/macOS instructions are present but always listed last. No Linux-specific tools or patterns are missing, but the ordering and emphasis favor Windows.
Recommendations
  • Present Linux/macOS and Windows instructions in parallel tabbed sections, or alternate which platform is shown first to avoid Windows-first bias.
  • Reduce the emphasis on Windows-specific tools (e.g., setx, PowerShell) by giving equal prominence to Linux/macOS commands.
  • Consider providing a single cross-platform example (e.g., using a table or tabs) rather than listing Windows commands first.
  • Explicitly mention that the Go code and Azure CLI commands are cross-platform, reinforcing parity.
  • If possible, add troubleshooting notes for both Windows and Linux/macOS environments to further balance the guidance.
GitHub Create Pull Request
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-go-web-app.md ...icles/azure-app-configuration/quickstart-go-web-app.md
Medium Priority View Details →
Scanned: 2025-08-06 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS, and includes both setx and PowerShell examples for Windows. Linux/macOS instructions are present but always listed last. There are no missing Linux examples, but the ordering and emphasis slightly favor Windows users.
Recommendations
  • Present Linux/macOS and Windows instructions side-by-side or in tabs, rather than always listing Windows first.
  • Consider leading with Linux/macOS examples, especially since Go development is common on those platforms.
  • Reduce duplication of Windows instructions (cmd and PowerShell) unless necessary; clarify which is recommended.
  • Explicitly state that all commands are cross-platform unless otherwise noted, and ensure parity in troubleshooting or advanced sections if added.
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
Medium Priority View Details →
Scanned: 2025-08-06 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation is focused exclusively on ASP.NET Core and assumes a Windows/.NET development environment. There are no examples or instructions for Linux or cross-platform development, and all code and prerequisites are tailored to Windows-centric tools and workflows. There is no mention of Linux command-line tools, shell scripts, or how to achieve the same outcome in a non-Windows environment.
Recommendations
  • Add explicit instructions or notes for Linux and macOS users, including any differences in environment setup or command-line usage.
  • Provide equivalent code samples or configuration steps for cross-platform .NET Core applications running on Linux.
  • Mention and link to documentation for using Azure App Configuration and Key Vault in non-Windows environments.
  • Clarify that the instructions are applicable to any platform supported by .NET Core, and highlight any platform-specific considerations.
  • If any Azure CLI or PowerShell steps are required, provide both Bash (Linux/macOS) and PowerShell (Windows) examples.
GitHub Create Pull Request
← Previous Page 11 of 20 Next →