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 301-325 of 479 flagged pages
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-javascript-provider.md ...re-app-configuration/quickstart-javascript-provider.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a mild Windows bias, particularly in the instructions for setting environment variables. Windows command prompt and PowerShell commands are consistently listed before Linux/macOS equivalents, and explicit references to Windows tools (setx, PowerShell) are made. However, Linux/macOS commands are present and correct, and the main code samples are cross-platform JavaScript.
Recommendations
  • Present Linux/macOS and Windows instructions in parallel or randomize the order to avoid always listing Windows first.
  • Use tabbed or side-by-side formatting for OS-specific instructions, so no platform is prioritized.
  • Where possible, use neutral language (e.g., 'On Windows, use... On Linux/macOS, use...') rather than always listing Windows first.
  • Consider referencing cross-platform tools (e.g., cross-env for setting environment variables in npm scripts) if appropriate.
  • Ensure all platform-specific instructions are equally detailed and visible.
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-07-13 21:37
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 explicit PowerShell examples. While Linux/macOS commands are included, Windows tools and patterns are consistently mentioned first, which may subtly prioritize Windows users.
Recommendations
  • Alternate the order of OS instructions (e.g., show Linux/macOS first in some sections, or group by OS rather than always leading with Windows).
  • Provide all OS instructions in parallel tabbed sections, so no OS is prioritized visually.
  • Avoid giving extra detail or emphasis to Windows-specific tools (e.g., 'setx', PowerShell) unless necessary; ensure parity in explanation for Linux/macOS equivalents.
  • Consider adding a summary table or section that lists all environment variable commands for each OS together for quick reference.
  • Where possible, use cross-platform commands or tools (such as Azure CLI) as the primary example, with OS-specific alternatives as secondary notes.
GitHub Create Pull Request
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/reference-kubernetes-provider.md ...ure-app-configuration/reference-kubernetes-provider.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a subtle Windows bias in the authentication examples for managed identities. Specifically, links and instructions for enabling and assigning managed identities on AKS clusters refer to Azure documentation sections that are explicitly for Windows Virtual Machine Scale Sets (VMSS), even though AKS clusters are typically Linux-based. There are no explicit Linux or cross-platform instructions or references for these steps, and the linked guides use Windows terminology and navigation. However, the rest of the documentation, including all YAML and CLI examples, is platform-neutral and uses standard Kubernetes and Azure CLI tools.
Recommendations
  • Replace or supplement links to Windows VMSS documentation with links to platform-neutral or Linux-focused AKS managed identity guides, as most AKS clusters run on Linux nodes.
  • Explicitly clarify in the authentication sections that the instructions apply to both Linux and Windows node pools, or provide separate guidance for each if there are differences.
  • Where possible, reference Azure documentation that is not specific to Windows (e.g., use AKS managed identity docs rather than Windows VMSS docs).
  • Review all external documentation links to ensure they are not Windows-specific unless necessary, and provide Linux or cross-platform alternatives.
  • Consider adding a note at the beginning of the authentication section to clarify that the provider works with both Linux and Windows AKS clusters, and that the instructions are platform-agnostic unless otherwise stated.
GitHub Create Pull Request
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/enable-dynamic-configuration-azure-functions-csharp.md ...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/enable-dynamic-configuration-azure-functions-csharp.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
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 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 instructions before or alongside Windows instructions, rather than always after.
  • Group all OS instructions together in a table or tabbed format to avoid implicit prioritization.
  • Ensure parity in tool recommendations; for example, mention cross-platform editors or CLI tools where relevant.
  • Where possible, use cross-platform language (e.g., 'terminal' instead of 'command prompt') and clarify that all platforms are equally supported.
  • Consider adding explicit notes that all steps are supported on Linux/macOS, and provide troubleshooting tips for those platforms if needed.
GitHub Create Pull Request
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/howto-import-export-data.md ...es/azure-app-configuration/howto-import-export-data.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently uses Windows-style file paths (e.g., C:/Users/john/Downloads/data.json, D:/abc.json) in all Azure CLI examples, and does not provide any Linux/macOS path examples. There are no explicit Linux or cross-platform command examples, and no mention of Linux-specific considerations. This may lead Linux/macOS users to feel the documentation is Windows-centric and less approachable.
Recommendations
  • Provide both Windows and Linux/macOS path examples in CLI commands (e.g., use ~/Downloads/data.json or /home/user/data.json alongside C:/... examples).
  • Add a note clarifying that file paths should be adapted to the user's operating system.
  • Where relevant, mention any OS-specific considerations for Azure CLI usage (such as path separators or shell differences).
  • Consider including screenshots or terminal snippets from both Windows and Linux environments, or use neutral, cross-platform examples.
  • Explicitly state that Azure CLI is cross-platform and works on Windows, Linux, and macOS.
GitHub Create Pull Request
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/enable-dynamic-configuration-java-spring-app.md ...ration/enable-dynamic-configuration-java-spring-app.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides command-line examples for running the Spring Boot app and testing with curl, but the curl example is given with a Windows command prompt (cmd) code block and no explicit Linux or cross-platform shell example. There are no PowerShell-specific commands or Windows-only tools, but the use of 'cmd' for curl and the lack of explicit Linux/macOS instructions or terminal screenshots suggest a subtle Windows-first bias. All Azure Portal instructions are platform-agnostic.
Recommendations
  • Provide curl examples in both Windows (cmd) and Linux/macOS (bash/sh) formats, or use a generic 'shell' code block.
  • Explicitly mention that the Maven and curl commands work on Linux/macOS as well as Windows.
  • If showing command-line output or screenshots, include both Windows and Linux/macOS terminals.
  • Consider using platform-neutral code blocks (e.g., 'shell' instead of 'cmd') for commands that are cross-platform.
  • Add a note clarifying that all command-line steps are applicable to both Windows and Linux/macOS environments.
GitHub Create Pull Request
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/enable-dynamic-configuration-azure-functions-csharp.md ...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/enable-dynamic-configuration-azure-functions-csharp.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides environment variable setup instructions for Windows Command Prompt and PowerShell before mentioning macOS/Linux (bash), and includes both Windows and PowerShell commands, which may indicate a slight Windows-first and PowerShell-heavy bias. However, Linux/macOS instructions are present and not omitted.
Recommendations
  • Rotate the order of platform instructions so that Linux/macOS (bash) examples are sometimes listed first, or present all three (cmd, PowerShell, bash) in a tabbed or parallel format to avoid implicit prioritization.
  • Where possible, use platform-agnostic language and tools, or clearly indicate parity between platforms.
  • Explicitly mention that all platforms are equally supported and provide links to platform-specific troubleshooting if needed.
  • Consider including screenshots or examples of running/tested workflows on Linux/macOS in addition to Windows/Visual Studio.
GitHub Create Pull Request
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/azure-pipeline-export-task.md .../azure-app-configuration/azure-pipeline-export-task.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides an explicit example of consuming exported variables using PowerShell syntax (echo "$env:myBuildSetting"), but does not provide equivalent examples for Linux shells (such as Bash). There are no references to Linux-specific tools or patterns, and the only code example is Windows/PowerShell-centric. This may make it less accessible for users running pipelines on Linux agents or those more familiar with Bash.
Recommendations
  • Provide equivalent Bash/Linux shell examples alongside the PowerShell example, e.g., echo "$myBuildSetting" or echo "$MYBUILDSETTING".
  • Explicitly mention that exported variables are available as environment variables in both Windows and Linux agents, and show how to access them in both environments.
  • If there are any platform-specific considerations (such as case sensitivity in environment variables), document them.
  • Review screenshots and UI instructions to ensure they are not Windows-only, or add notes if the experience differs on Linux/Mac agents.
GitHub Create Pull Request
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/concept-enable-rbac.md ...rticles/azure-app-configuration/concept-enable-rbac.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exhibits a subtle Windows bias by referencing Visual Studio Credential as the first and only concrete example of a development environment credential, which is primarily a Windows tool. There are no explicit Linux or cross-platform command-line examples (such as Azure CLI or Bash), nor are Linux development environments mentioned. The instructions for role assignment are given exclusively via the Azure Portal UI, with no mention of CLI or scripting alternatives, which are often preferred in Linux environments.
Recommendations
  • Include Azure CLI and/or PowerShell command-line examples for role assignment, ensuring both Windows and Linux users can follow along.
  • Mention cross-platform development environments (e.g., VS Code, JetBrains Rider) and their credential options alongside Visual Studio.
  • Provide explicit Linux/macOS development workflow examples, such as using DefaultAzureCredential with the Azure CLI logged-in user.
  • Clarify that the Azure Portal is accessible from any OS, but also provide automation-friendly alternatives for role assignment.
  • Where possible, avoid listing Windows-centric tools or workflows first; instead, present cross-platform options or alternate between them.
GitHub Create Pull Request
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/enable-dynamic-configuration-dotnet-core.md ...figuration/enable-dynamic-configuration-dotnet-core.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation demonstrates some Windows bias, particularly in the 'Build and run the app locally' section. Windows command prompt and PowerShell instructions are listed before Linux/macOS equivalents, and screenshots and instructions reference 'Command Prompt or PowerShell window' specifically. However, Linux/macOS commands are present, and Visual Studio Code is mentioned as cross-platform. There are no missing Linux examples, but the ordering and language prioritize Windows environments.
Recommendations
  • Present environment variable instructions for Windows, macOS, and Linux in parallel (e.g., in a table or side-by-side), or list Linux/macOS first in some cases.
  • Use neutral language such as 'terminal window' instead of 'Command Prompt or PowerShell window' when referring to where the app is run.
  • Include screenshots or references to Linux/macOS terminals as well as Windows.
  • Ensure that all code and command examples are explicitly tested and confirmed to work on Linux/macOS, and note any platform-specific differences.
  • Where possible, avoid assuming the user is on Windows (e.g., do not say 'restart the command prompt' without also mentioning restarting the terminal on Linux/macOS).
GitHub Create Pull Request
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/enable-dynamic-configuration-dotnet-core-push-refresh.md ...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/enable-dynamic-configuration-dotnet-core-push-refresh.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides environment variable setup instructions with Windows Command Prompt and PowerShell examples before macOS and Linux, indicating a 'windows_first' bias. Additionally, both Windows Command Prompt and PowerShell are given separate, detailed sections, while Unix-like systems (macOS and Linux) are grouped together and presented after Windows, which is a common 'powershell_heavy' and 'windows_first' pattern. However, Linux and macOS instructions are present, and the rest of the tutorial is cross-platform.
Recommendations
  • Present all platform instructions (Windows Command Prompt, PowerShell, macOS, Linux) in a tabbed or parallel format, without prioritizing Windows over others.
  • Group macOS and Linux separately if there are meaningful differences, or clarify when instructions are identical.
  • Consider leading with a neutral, cross-platform example (e.g., using .NET CLI or environment variable setting in code) before platform-specific instructions.
  • Explicitly state that all steps are applicable on Windows, macOS, and Linux, and avoid language that implies Windows is the default or primary platform.
GitHub Create Pull Request
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/enable-dynamic-configuration-java-spring-app.md ...ration/enable-dynamic-configuration-java-spring-app.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides command-line examples for running curl using the Windows (cmd) prompt syntax (```cmd), and does not show equivalent Linux/macOS shell examples. The use of Azure Portal is platform-neutral, but the lack of explicit Linux or cross-platform command-line instructions (e.g., bash) and the use of Windows-first code block markers may cause confusion or suggest a Windows bias.
Recommendations
  • Provide both Windows (cmd/PowerShell) and Linux/macOS (bash/sh) command-line examples for commands such as curl.
  • Use platform-neutral code block markers (e.g., ```shell) for commands that work across platforms, or provide separate blocks for each OS.
  • Explicitly mention that the Maven commands and curl examples work on Linux/macOS as well, or show both variants if there are differences.
  • Consider including screenshots or instructions for using the Azure CLI (which is cross-platform) for resource management tasks, as an alternative to the Azure Portal.
GitHub Create Pull Request
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/enable-dynamic-configuration-python.md ...p-configuration/enable-dynamic-configuration-python.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation shows a mild Windows bias by only linking to Python installation instructions for Windows in the prerequisites, without mentioning or linking to Linux or macOS equivalents. All code and CLI examples are cross-platform, but the setup guidance assumes a Windows-first perspective.
Recommendations
  • In the prerequisites, provide links to Python installation/setup documentation for Linux and macOS, alongside the Windows link.
  • Explicitly state that the code and CLI examples work on all major platforms (Windows, Linux, macOS).
  • If there are any platform-specific considerations (e.g., environment variable syntax differences), mention them or provide examples for both Windows and Linux/macOS.
  • Consider adding a note or section for common Linux/macOS development environments, such as using virtual environments or installing dependencies.
GitHub Create Pull Request
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/enable-dynamic-configuration-java-spring-push-refresh.md ...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/enable-dynamic-configuration-java-spring-push-refresh.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
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 includes both Windows command prompt and PowerShell examples. While Linux/macOS commands are present, Windows instructions are consistently listed first and in greater detail, which may suggest a subtle Windows-first bias. There are no missing Linux examples, but the ordering and emphasis favor Windows users.
Recommendations
  • Alternate the order in which OS-specific instructions are presented, or group them in tabs so no platform is prioritized.
  • Use neutral language such as 'If you use Windows/macOS/Linux...' rather than always listing Windows first.
  • Ensure all command-line examples are equally detailed for all platforms.
  • Consider providing a single cross-platform command (where possible) or a summary table for environment variable setup.
  • Explicitly state that all steps are supported on Windows, Linux, and macOS at the beginning of the relevant sections.
GitHub Create Pull Request
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/howto-chat-completion-config.md ...zure-app-configuration/howto-chat-completion-config.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation page focuses exclusively on the Azure portal and does not provide any command-line examples. Where it does reference the CLI, it does not specify or provide examples for Linux or cross-platform usage. The only implementation link provided is for .NET, which is more commonly associated with Windows environments, and there are no references to Linux-specific tools, shell commands, or alternative platforms.
Recommendations
  • Add explicit CLI examples for both Azure CLI (az) and PowerShell, ensuring parity between Windows and Linux command syntax.
  • Include instructions or links for implementing chat completion configuration in languages and frameworks popular on Linux (e.g., Python, Node.js).
  • When referencing the CLI, clarify that Azure CLI is cross-platform and provide example commands for both Bash (Linux/macOS) and PowerShell (Windows).
  • Expand the 'Continue to the following instructions' section to include quickstarts or guides for Linux-friendly languages and environments.
  • Ensure screenshots and UI instructions are supplemented with equivalent CLI or code-based steps for automation and scripting, which are common on Linux.
GitHub Create Pull Request
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/howto-variant-feature-flags-javascript.md ...onfiguration/howto-variant-feature-flags-javascript.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides environment variable setup instructions for Windows Command Prompt and PowerShell before mentioning the macOS/Linux equivalent. Both Windows shells are described in detail, while the Linux/macOS example is presented last. No Linux-specific tools or patterns are omitted, but the ordering and explicitness favor Windows users.
Recommendations
  • Present environment variable setup instructions for all platforms in parallel (e.g., a table or side-by-side code blocks), or begin with Linux/macOS to avoid implicit prioritization of Windows.
  • Avoid giving two separate Windows shell examples before the Linux/macOS example; consider grouping by platform or using tabs.
  • Explicitly state that the instructions apply equally to all platforms, and ensure Linux/macOS users do not feel like an afterthought.
  • Where possible, provide parity in troubleshooting or platform-specific notes (e.g., how to persist environment variables on Linux shells if set in a terminal session).
GitHub Create Pull Request
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/howto-import-export-data.md ...es/azure-app-configuration/howto-import-export-data.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently uses Windows-style file paths (e.g., C:/Users/john/Downloads/data.json, D:/abc.json) in all Azure CLI examples, and does not provide any Linux/macOS path examples or mention of Linux-specific shell usage. There are no explicit PowerShell or Windows-only tool references, but the file path examples and lack of Linux parity suggest a subtle Windows bias.
Recommendations
  • For every CLI example using a Windows path (e.g., C:/Users/john/Downloads/data.json), add a parallel example using a Linux/macOS path (e.g., /home/alice/data.json).
  • Explicitly state that the Azure CLI commands work cross-platform (Windows, Linux, macOS) and that file paths should be adapted to the user's OS.
  • Where file paths are shown in parameter tables, provide both Windows and Linux/macOS variants.
  • Consider including a note or tabbed examples for Bash and PowerShell if there are any shell-specific considerations.
  • Review screenshots and ensure they do not exclusively show Windows environments if possible.
GitHub Create Pull Request
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-bicep.md ...n/articles/azure-app-configuration/quickstart-bicep.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all deployment, review, and cleanup steps. However, PowerShell is a Windows-centric tool, and its inclusion alongside CLI in every example can be seen as a Windows bias. Additionally, PowerShell examples are always presented immediately after CLI, which is the cross-platform tool, but there is no mention of Linux-specific shell environments or considerations. There are no Linux-only examples or explicit references to Linux tools or patterns.
Recommendations
  • Clearly state that Azure CLI commands work natively on Linux, macOS, and Windows, and are the recommended cross-platform approach.
  • Consider providing Bash shell script examples or mentioning that the CLI commands can be run in Bash or other Linux shells.
  • If PowerShell is included, clarify that it is available cross-platform (PowerShell Core), or note any differences for Windows PowerShell vs. PowerShell Core.
  • Add a note or section for Linux/macOS users highlighting any OS-specific considerations, such as file paths or prerequisites.
  • Ensure that Linux and macOS users are explicitly addressed in the prerequisites and deployment instructions.
GitHub Create Pull Request
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-chat-completion-dotnet.md ...app-configuration/quickstart-chat-completion-dotnet.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides environment variable setup instructions for Windows Command Prompt and PowerShell before mentioning macOS/Linux. The Windows and PowerShell commands are listed first, with the Linux/macOS example last. There are no Linux-specific tools or patterns missing, but the ordering prioritizes Windows environments.
Recommendations
  • Present environment variable setup instructions for all platforms in parallel, or list Linux/macOS first to balance the order.
  • Use tabbed or collapsible sections for platform-specific instructions to give equal prominence to Windows, PowerShell, and Linux/macOS.
  • Ensure that any future troubleshooting or tool references include Linux/macOS equivalents alongside Windows tools.
  • Explicitly state that the .NET SDK and Azure App Configuration are cross-platform, and that the instructions apply equally to all supported operating systems.
GitHub Create Pull Request
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-dotnet-core-app.md .../azure-app-configuration/quickstart-dotnet-core-app.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides environment variable setup instructions for Windows Command Prompt and PowerShell before macOS/Linux, and includes both Windows and Linux/macOS examples. However, Windows-specific tools (setx, PowerShell) are always mentioned first, which may subtly prioritize Windows workflows. There are no missing Linux examples, but the ordering and emphasis could be improved for parity.
Recommendations
  • Present environment variable instructions in a platform-neutral order, or alternate which platform appears first.
  • Consider grouping all OS instructions together in a table or tabbed format to avoid implicit prioritization.
  • Explicitly state that all .NET CLI commands work identically on Windows, Linux, and macOS to reinforce cross-platform parity.
  • Where possible, avoid Windows-specific tools (like setx) as the default, or provide a brief explanation of their Linux/macOS equivalents.
  • Ensure screenshots and terminal output are shown from both Windows and Linux/macOS terminals, or use a neutral terminal style.
GitHub Create Pull Request
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-azure-kubernetes-service.md ...p-configuration/quickstart-azure-kubernetes-service.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias by recommending Docker Desktop as a prerequisite and not mentioning Linux-native alternatives (such as Docker Engine or Podman). All command-line examples are cross-platform (az CLI, dotnet, kubectl, helm), but there are no explicit Linux-specific instructions or troubleshooting notes. The documentation assumes the user will use Docker Desktop, which is primarily a Windows/macOS tool, and does not acknowledge that Linux users typically use Docker Engine or other container runtimes. There are no PowerShell-specific commands or Windows command prompt syntax, but the lack of Linux-specific notes or alternatives for Docker installation is a subtle bias.
Recommendations
  • In the prerequisites, mention Docker Engine (for Linux) as an alternative to Docker Desktop, and provide a link to installation instructions for both.
  • Where Docker Desktop is referenced, clarify that Linux users should use Docker Engine or Podman, and provide relevant links.
  • Add a note or section indicating that all CLI commands are cross-platform and can be run in Bash, PowerShell, or other shells.
  • If any troubleshooting or file path instructions are OS-specific, provide both Windows and Linux/macOS examples.
  • Consider adding a table or callout summarizing installation steps for required tools (Docker, kubectl, helm, etc.) on both Windows and Linux.
GitHub Create Pull Request
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-container-apps.md ...s/azure-app-configuration/quickstart-container-apps.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a bias towards Windows by focusing exclusively on an ASP.NET Core application (commonly associated with Windows development), omitting any Linux-specific instructions or examples, and not mentioning platform differences in Docker or Azure CLI usage. There are no explicit PowerShell or Windows-only commands, but the lack of Linux parity is evident in the absence of alternative examples or notes for Linux users.
Recommendations
  • Include explicit notes or sections clarifying that all CLI and Docker commands work cross-platform, and highlight any differences for Linux/macOS users.
  • Provide at least one example using a non-Windows development stack (e.g., a Node.js or Python app) to illustrate broader applicability.
  • Mention that Docker Desktop is available for Windows, macOS, and Linux, and provide links or instructions for Linux installation.
  • If any commands or steps differ on Linux (such as file path syntax or environment variable conventions), call these out in side notes or tabs.
  • Add troubleshooting tips for common Linux/macOS issues (e.g., Docker permissions, case sensitivity in file names).
GitHub Create Pull Request
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-python-provider.md .../azure-app-configuration/quickstart-python-provider.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
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 Windows-specific guidance (e.g., setx and PowerShell commands). Linux/macOS instructions are present but always listed last. The prerequisites section links only to Windows-specific Python setup documentation, omitting Linux/macOS equivalents.
Recommendations
  • Present environment variable instructions for Windows, macOS, and Linux in parallel (e.g., in a table or side-by-side tabs) rather than always listing Windows first.
  • Include links to official Python installation/setup documentation for Linux and macOS in the prerequisites section, not just Windows.
  • Ensure that Linux/macOS commands and workflows are given equal prominence and clarity as Windows examples.
  • Consider using a neutral, cross-platform approach (e.g., using Python's os.environ in code or referencing platform-agnostic tools) where possible.
GitHub Create Pull Request
Azure App Configuration https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/quickstart-feature-flag-spring-boot.md ...p-configuration/quickstart-feature-flag-spring-boot.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides environment variable setting instructions for Windows Command Prompt and PowerShell before mentioning Linux/macOS equivalents. Windows-specific tools (cmd, PowerShell) are described in detail, with Linux/macOS commands listed last. However, all major steps are covered for both platforms, and there are no missing Linux examples or exclusive use of Windows tools.
Recommendations
  • Present Linux/macOS and Windows instructions in parallel tabbed sections, rather than listing Windows first.
  • Avoid giving Windows-specific instructions (cmd, PowerShell) priority over Linux/macOS; consider alphabetical or usage-based ordering.
  • Where possible, use cross-platform commands or highlight platform differences without bias.
  • Explicitly mention that all steps are supported on Linux/macOS, and provide troubleshooting tips for those environments if 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-07-08 04:23
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 gives detailed PowerShell and Windows Command Prompt examples. Linux/macOS instructions are present but always listed last. There are no missing Linux examples, but the ordering and explicit mention of Windows tools first indicate a subtle Windows-first bias.
Recommendations
  • Present Linux/macOS and Windows instructions in parallel tabs or side-by-side, rather than always listing Windows first.
  • Consider listing Linux/macOS instructions first, or randomizing the order across documentation pages to avoid implicit prioritization.
  • Where possible, use cross-platform commands (e.g., via the Azure CLI) as the primary example, and provide OS-specific instructions only as needed.
  • Explicitly state that all platforms are supported equally, and ensure parity in example detail and placement.
  • Review other documentation pages for similar ordering and adjust for consistency.
GitHub Create Pull Request
← Previous Page 13 of 20 Next →