Azure Docs
14605
Total Pages
12420
Linux-Friendly Pages
2185
Pages with Bias
15.0%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
2185 issues found
Showing 1501-1525 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automanage/quick-go-sdk.md
...re-docs/blob/main//articles/automanage/quick-go-sdk.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias by linking exclusively to the Windows virtual machine quick-create guide in the prerequisites, without mentioning or linking to the equivalent Linux VM documentation. There are no Linux-specific examples or references, and the only VM creation link is for Windows, which may suggest to users that the process is intended primarily for Windows VMs.
Recommendations
- Add a link to the Linux virtual machine quick-create documentation alongside the Windows link in the prerequisites section.
- Clarify in the introduction and throughout the guide that the process applies to both Windows and Linux virtual machines, if that is the case.
- Where relevant, provide examples or notes for both Windows and Linux VM scenarios, especially if there are any differences in Automanage support or configuration.
- Review all references to ensure Linux users are equally supported and informed.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automanage/quick-java-sdk.md
...-docs/blob/main//articles/automanage/quick-java-sdk.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by linking only to the Windows virtual machine quick-create guide in the prerequisites, without mentioning or providing a link to the equivalent Linux VM documentation. There are no Linux-specific instructions or examples, and the only VM example referenced is for Windows.
Recommendations
- Include links to both Windows and Linux virtual machine quick-create guides in the prerequisites section.
- Explicitly state that the instructions apply to both Windows and Linux VMs, or provide separate examples if there are differences.
- Add a note or section clarifying any platform-specific considerations for Linux users.
- Ensure that future documentation consistently presents both Windows and Linux options where applicable.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-fluid-relay/concepts/customer-managed-keys.md
...es/azure-fluid-relay/concepts/customer-managed-keys.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation contains subtle Windows bias, primarily in the prerequisites section where the tutorial link for creating a user-assigned managed identity points to a Windows VM-specific guide. There are no explicit PowerShell or Windows-only command examples, but there is also a lack of Linux-specific or cross-platform CLI examples and guidance. This may make it less accessible for Linux users.
Recommendations
- Replace or supplement the prerequisite link (currently pointing to a Windows VM tutorial) with a cross-platform or Linux-specific guide for creating and assigning user-assigned managed identities.
- Include Azure CLI examples for all resource creation and configuration steps, as Azure CLI is cross-platform.
- Explicitly mention that the API calls and procedures are platform-agnostic, and provide example commands for both Windows (PowerShell) and Linux (Bash/Azure CLI) where relevant.
- Add a note clarifying that the instructions apply equally to Linux and Windows unless otherwise stated.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automanage/overview-vm-status.md
...s/blob/main//articles/automanage/overview-vm-status.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page focuses exclusively on using the Azure portal UI to check Automanaged VM status, without providing any command-line examples or references. There is no mention of how to check status using CLI tools such as Azure CLI, PowerShell, or Bash, nor are there any examples or notes about differences between Windows and Linux VMs. While the page does not explicitly mention Windows tools, the lack of Linux-specific guidance or parity in troubleshooting and status checking constitutes a subtle bias, especially since Azure supports both Windows and Linux VMs.
Recommendations
- Add examples for checking Automanaged VM status using Azure CLI (az) commands, which are cross-platform and can be run on both Windows and Linux.
- If PowerShell examples are provided, ensure equivalent Bash or shell script examples are also included for Linux users.
- Include notes or troubleshooting steps that address both Windows and Linux VM scenarios, such as differences in VM agent installation or permissions issues.
- Explicitly mention that the instructions apply to both Windows and Linux VMs, or clarify any differences where relevant.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automanage/quick-javascript-sdk.md
...blob/main//articles/automanage/quick-javascript-sdk.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias by linking exclusively to the Windows virtual machine quick-create guide in the prerequisites, without mentioning or providing equivalent guidance for Linux virtual machines. There are no Linux-specific instructions, examples, or references, which may lead Linux users to feel unsupported or unclear about compatibility.
Recommendations
- Add a link to the Linux virtual machine quick-create guide alongside the Windows VM link in the prerequisites section.
- Explicitly state that the JavaScript SDK and Automanage support both Windows and Linux virtual machines, if applicable.
- Include examples or notes relevant to Linux VM users, such as any differences in configuration or supported features.
- Review all referenced documentation to ensure Linux parity and avoid the impression that only Windows VMs are supported.
Azure Docs
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 →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Summary
The documentation provides a PowerShell-specific example for consuming exported environment variables, but does not include equivalent examples for Linux/macOS shells (such as Bash). There are no explicit references to Windows-only tools or patterns, but the lack of cross-platform scripting examples may hinder Linux users.
Recommendations
- Add equivalent Bash (and optionally, macOS/zsh) examples for accessing environment variables, e.g., `echo "$myBuildSetting"`.
- Wherever scripting examples are provided, include both PowerShell and Bash versions side by side.
- Explicitly state that the Azure Pipelines agent and tasks are cross-platform, and clarify any OS-specific considerations if they exist.
- Review screenshots and UI instructions to ensure they are not Windows-specific, or note any differences for Linux/macOS users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/automation-faq.md
...-docs/blob/main//articles/automation/automation-faq.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides more detailed, step-by-step environment variable resolution for Python on Windows Hybrid Runbook Workers, including explicit file paths and variable names (e.g., C:\Python2\python.exe). In contrast, the Linux equivalent is only mentioned in passing, with no comparable detail or examples. There are no Linux-specific commands, file paths, or troubleshooting steps provided, and the pattern of explanation is Windows-first.
Recommendations
- Add explicit Linux examples for environment variable resolution, such as specifying typical Linux paths (e.g., /usr/bin/python3) and environment variable usage.
- Include step-by-step details for how the Linux Hybrid Runbook Worker locates the Python interpreter, mirroring the Windows explanation.
- Provide Linux-specific troubleshooting tips or common issues, similar to the Windows focus.
- Ensure that when both platforms are discussed, Linux is given equal prominence and detail, not just a brief mention.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-sql-edge/overview.md
...re-docs/blob/main//articles/azure-sql-edge/overview.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page demonstrates a mild Windows bias by listing Windows-centric tools (SQL Server Management Studio, SQL Server Data Tools in Visual Studio) before mentioning cross-platform or Linux-friendly tools. The ordering and emphasis on Windows tools may suggest to readers that Windows is the primary or preferred development environment, even though Azure SQL Edge is cross-platform and often deployed on Linux-based IoT devices.
Recommendations
- Reorder the list of development tools to highlight cross-platform tools (e.g., Azure Data Studio, Visual Studio Code) before Windows-only tools.
- Explicitly mention Linux command-line tools or workflows where relevant, such as using sqlcmd or Azure CLI on Linux.
- Where Windows-only tools are listed, clearly indicate their platform limitations and suggest Linux/macOS alternatives.
- Include example workflows or screenshots from Linux environments to reinforce parity.
- Ensure that deployment and management instructions are equally detailed for both Windows and Linux environments in linked documentation.
Azure Docs
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 →
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 are Windows-specific shells. Linux/macOS instructions are present but always listed last. There are no Linux-specific tools or patterns mentioned, but the ordering and prominence of Windows examples indicate a mild Windows-first bias.
Recommendations
- Present Linux/macOS and Windows instructions in parallel tabs or in the same order of prominence.
- Consider listing Linux/macOS examples before or alongside Windows examples to balance visibility.
- Explicitly mention cross-platform compatibility of tools (such as Azure Functions Core Tools) and provide installation/testing instructions for Linux/macOS environments.
- Where possible, avoid assuming Visual Studio as the default development environment; mention VS Code or CLI alternatives for Linux/macOS users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/change-tracking/manage-change-tracking-monitoring-agent.md
...ge-tracking/manage-change-tracking-monitoring-agent.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation generally presents Windows examples and terminology before Linux equivalents, such as listing 'Windows Files' before 'Linux Files' and referencing Windows-specific concepts (e.g., Windows Registry, environment variables like %winDir%) without parallel Linux examples. Windows-centric paths and patterns are often mentioned first or exclusively, and Windows tools/patterns (like environment variables in paths) are highlighted more than their Linux counterparts.
Recommendations
- Alternate the order of Windows and Linux examples or present them side-by-side to avoid always listing Windows first.
- When referencing environment variables or system paths, provide both Windows and Linux equivalents (e.g., %winDir% for Windows, $HOME or $PATH for Linux).
- Include Linux-specific tools or patterns where Windows tools are mentioned (e.g., mention Linux configuration files or environment variable usage).
- Ensure that all features and steps described for Windows (such as registry or file tracking) clearly state Linux equivalents or note if not applicable.
- Where possible, provide screenshots or command-line examples for both platforms, not just Windows.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/delete-run-as-account.md
...lob/main//articles/automation/delete-run-as-account.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation page focuses on deleting Azure Automation Run As accounts using PowerShell or the Azure portal, both of which are Windows-centric tools. There are no examples or instructions for performing the task using Linux-native tools or command-line interfaces such as Azure CLI, and the only scripting example mentioned is PowerShell.
Recommendations
- Add equivalent instructions and examples using Azure CLI, which is cross-platform and commonly used on Linux.
- Explicitly mention that the Azure portal and PowerShell are not the only options, and provide parity for Linux users.
- Include bash shell script examples where appropriate.
- Clarify that Azure CLI commands can be run on Windows, Linux, and macOS, and provide links to relevant documentation.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/python-packages.md
...docs/blob/main//articles/automation/python-packages.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates Windows bias by providing explicit instructions and command-line examples only for Windows (e.g., using pip on a Windows 64-bit machine with a Windows path), without mentioning or providing equivalent steps for Linux or macOS environments. There are no Linux or cross-platform examples for downloading packages with dependencies.
Recommendations
- Include Linux and macOS equivalents for all command-line instructions, such as showing how to use pip on those platforms (e.g., 'pip2.7 download -d <output dir> <package name>').
- Avoid specifying only 'Windows 64-bit machine'—instead, mention that the process can be performed on any OS with Python 2.7 and pip installed.
- Provide example commands and file paths for both Windows and Linux/macOS (e.g., C:\... vs /usr/bin/pip2.7).
- Explicitly state that the instructions are cross-platform where applicable, or call out any platform-specific limitations.
- Add screenshots or terminal output from Linux/macOS environments where relevant.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/enforce-job-execution-hybrid-worker.md
...cles/automation/enforce-job-execution-hybrid-worker.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for policy creation and assignment, but PowerShell (a Windows-centric tool) is given equal or greater prominence, including full command blocks and parameter explanations. There are no explicit Linux shell (bash) examples, and PowerShell is referenced as a primary method for retrieving resource IDs and performing assignments. This may create a perception of Windows/PowerShell preference, especially for users on Linux or macOS.
Recommendations
- Add explicit bash shell examples for all Azure CLI commands, demonstrating usage in a Linux environment.
- Clarify that Azure CLI commands are cross-platform and can be run in bash, zsh, or other Linux shells, not just Windows Command Prompt or PowerShell.
- Where PowerShell is used to retrieve resource IDs or manipulate output, provide equivalent bash/CLI pipelines (e.g., using jq or grep/awk) for Linux users.
- Consider reordering examples to present Azure CLI (which is cross-platform) before PowerShell, or clearly label both as equally supported.
- Add a brief section or note highlighting that all operations can be performed from Linux/macOS using Azure CLI, and link to relevant setup guides.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/quickstart-create-automation-account-template.md
...ation/quickstart-create-automation-account-template.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page demonstrates a mild Windows bias by referencing PowerShell before Azure CLI when discussing template deployment, and by providing explicit PowerShell parameter usage examples. While Azure CLI is mentioned, PowerShell is consistently listed first and receives more detailed treatment. There are no Linux-specific tools or shell examples, and the documentation does not provide parity in example depth for Linux users.
Recommendations
- Ensure that Azure CLI examples are presented before or alongside PowerShell examples, especially since Azure CLI is cross-platform.
- Provide explicit, step-by-step Azure CLI command examples for deploying the ARM template, not just parameter references.
- Include Bash shell (Linux/macOS) command examples where appropriate, especially for common deployment scenarios.
- Avoid language that implies PowerShell is the default or preferred method; instead, present both PowerShell and CLI as equal options.
- Add a section or callout for Linux/macOS users, highlighting any platform-specific considerations or tips.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/how-to/runbook-authoring-extension-for-vscode.md
...ation/how-to/runbook-authoring-extension-for-vscode.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Summary
The documentation implicitly assumes a PowerShell-centric workflow, which is most commonly associated with Windows environments. It mentions PowerShell modules as a prerequisite and does not provide any Linux-specific guidance, troubleshooting, or examples. There are no references to Linux shell environments, nor are there clarifications on cross-platform compatibility for local runbook testing or debugging.
Recommendations
- Explicitly state that the Azure Automation extension for VS Code is cross-platform and works on Windows, macOS, and Linux.
- Provide examples or notes for Linux users, such as how to install required PowerShell modules or Python packages on Linux.
- Clarify whether local runbook execution and debugging is supported on Linux, and if there are any limitations or additional steps required.
- Include troubleshooting tips or common issues for Linux environments (e.g., permissions, path differences, dependency installation).
- Mention any differences in experience or prerequisites for macOS/Linux users compared to Windows users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-app-configuration/enable-dynamic-configuration-dotnet.md
...p-configuration/enable-dynamic-configuration-dotnet.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation is generally cross-platform in its environment variable instructions, providing commands for Windows Command Prompt, PowerShell, and macOS/Linux. However, there is a subtle Windows bias: Windows tools (Visual Studio, Command Prompt, PowerShell) are mentioned first and more prominently, and the tutorial is centered around .NET Framework, which is primarily a Windows technology. Linux/macOS commands are included but always listed last. There are no Linux-specific development environment suggestions (e.g., VS Code, JetBrains Rider), and the workflow assumes Visual Studio on Windows.
Recommendations
- Present environment variable commands in a neutral or rotating order (not always Windows first).
- Explicitly mention and provide guidance for cross-platform .NET development environments (e.g., Visual Studio Code, JetBrains Rider) where possible.
- Clarify that .NET Framework is Windows-only, and provide links or notes for .NET (Core/5+/6+) cross-platform equivalents.
- Where possible, include Linux/macOS screenshots or terminal output, not just Windows Command Prompt/PowerShell.
- Consider a parallel tutorial or notes for .NET (Core/5+/6+) apps that can run natively on Linux/macOS.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/quickstarts/create-azure-automation-account-terraform.md
...ickstarts/create-azure-automation-account-terraform.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for verifying results, but consistently lists Azure CLI (cross-platform) first, which is positive. However, the 'Next steps' section exclusively links to a PowerShell runbook tutorial, and there is a general emphasis on PowerShell in the Automation context. There are no Linux-specific tools or shell examples, but the CLI examples are cross-platform. No explicit Windows-only tools or instructions are present, but the Automation account's PowerShell focus and next steps could be seen as Windows-centric.
Recommendations
- Include links to tutorials for creating Automation Python runbooks or Bash scripts, not just PowerShell.
- In 'Next steps', provide parity by suggesting both PowerShell and Python/Bash runbook tutorials.
- Explicitly mention that Azure CLI examples work on Linux, macOS, and Windows.
- If possible, add a troubleshooting or verification section using Bash or Linux-native tools, or clarify that the CLI commands are suitable for Linux users.
Azure Docs
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 →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides command-line examples using the 'cmd' code block and Windows-style curl commands, without offering equivalent Linux/macOS shell examples. This may lead Linux users to feel unsupported or confused, especially since the rest of the tutorial is cross-platform (Java, Maven). No Linux-specific tools or shell commands are mentioned.
Recommendations
- Provide both Windows (cmd/PowerShell) and Linux/macOS (bash/sh) command-line examples for commands like curl.
- Use generic 'shell' code blocks for commands that are cross-platform (e.g., Maven commands), and clarify if any command is OS-specific.
- Add a note clarifying that the Azure Portal steps are the same across platforms.
- When showing curl examples, use syntax that works on both Windows and Linux, or provide both variants side by side.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/avere-vfxt/avere-vfxt-demo-links.md
...lob/main//articles/avere-vfxt/avere-vfxt-demo-links.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page lists a client setup guide specifically for Windows 10 workstations, with no equivalent example or mention of Linux or macOS client setup. This suggests a bias towards Windows environments, especially in the 'Client setup' section. Additionally, Windows is the only client OS explicitly mentioned, and no Linux tools or setup patterns are referenced.
Recommendations
- Add a parallel client setup guide for Linux workstations, demonstrating how to mount and use Avere vFXT from a Linux client.
- Explicitly mention support for non-Windows clients where applicable, and provide links or references to relevant documentation.
- Ensure that future examples and tutorials include both Windows and Linux (and optionally macOS) workflows where possible to provide parity.
Azure Docs
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 →
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 commands (setx, PowerShell) alongside bash. While Linux/macOS commands are present, the ordering and emphasis favor Windows. There are no Linux-specific deployment or tooling examples, but the bias is mainly in the order and detail of environment variable instructions.
Recommendations
- Present environment variable instructions for all platforms in parallel tables or grouped tabs, rather than listing Windows first.
- Avoid giving extra detail (such as 'restart the command prompt') only for Windows; provide parity for Linux/macOS (e.g., 'restart your terminal').
- Where possible, use cross-platform instructions or highlight platform differences equally.
- Consider including Linux/macOS-specific deployment or troubleshooting tips if Windows-specific ones are present.
- If referencing editors or tools, ensure Linux/macOS options are mentioned with equal prominence.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/avere-vfxt/avere-vfxt-prereqs.md
...s/blob/main//articles/avere-vfxt/avere-vfxt-prereqs.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation consistently presents Azure Portal (web UI) and Azure CLI examples, but does not provide any Linux- or macOS-specific guidance or examples. All command-line instructions use Azure CLI, which is cross-platform, but there are no mentions of Linux shell environments, nor are there any examples or notes for Linux users. The documentation implicitly assumes a Windows-centric workflow by referencing the Azure Portal UI and not acknowledging Linux-specific considerations.
Recommendations
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide example shell prompts for Linux/macOS (e.g., $ instead of >).
- Include notes or sections for Linux users, especially regarding prerequisites such as installing Azure CLI on Linux, or using bash/zsh.
- If screenshots are provided, consider including at least one from a Linux environment (e.g., Azure Cloud Shell in a browser, or a terminal window on Linux).
- Mention that the Azure Portal is web-based and platform-agnostic, to clarify that it is not Windows-specific.
- If there are any platform-specific caveats (such as file path formats, authentication methods, or dependencies), call them out for Linux users.
Azure Docs
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 →
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) in a tabbed format, but Windows instructions (Command Prompt and PowerShell) are presented before macOS and Linux. There are no Linux- or macOS-specific code examples, troubleshooting, or tooling references beyond the environment variable setup. The rest of the tutorial is platform-agnostic, focusing on .NET code and Azure services.
Recommendations
- Rotate the order of platform-specific instructions periodically or default to a neutral order (e.g., Linux/macOS first, then Windows) to avoid implicit prioritization.
- Explicitly mention that all .NET code and Azure SDK instructions apply equally to Linux and macOS, not just Windows.
- Include a brief troubleshooting section for common Linux/macOS issues (e.g., permissions, environment variable persistence) to demonstrate parity.
- Where possible, provide shell-agnostic commands (e.g., using cross-platform .NET CLI for all steps) and clarify any platform-specific differences.
- Highlight that Visual Studio Code is cross-platform and recommend it equally for all OSes, not just as an aside.
Azure Docs
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 →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias by referencing only Windows-specific setup documentation for Python in the prerequisites and omitting explicit Linux (or macOS) setup instructions or links. All code and CLI examples are cross-platform, but the initial guidance assumes a Windows environment.
Recommendations
- In the prerequisites section, provide links or references for setting up Python on Linux and macOS, such as official Python installation guides for those platforms.
- Mention that the CLI and code examples work on Windows, Linux, and macOS, to reassure non-Windows users.
- Where platform-specific setup is referenced (e.g., Python installation), ensure parity by listing all major platforms or linking to a cross-platform installation guide.
- If mentioning the Azure CLI, clarify that it is available and works on all major platforms.
Azure Docs
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 →
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 for setting environment variables are presented before the Linux/macOS equivalent. Additionally, PowerShell is mentioned explicitly, and screenshots reference Command Prompt or PowerShell windows. However, Linux/macOS instructions are present and not omitted.
Recommendations
- Present environment variable instructions for all platforms in parallel, or start with a neutral (cross-platform) option such as bash, then provide Windows-specific alternatives.
- Avoid referencing only Command Prompt or PowerShell windows in screenshots and instructions; mention terminal or shell generically, or provide Linux/macOS screenshots as well.
- Ensure that all CLI commands and tooling are described in a platform-neutral way, and avoid implying Windows is the default or primary development environment.
- Where possible, use cross-platform tools and terminology first, and mention platform-specific tools as alternatives.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-app-configuration/howto-recover-deleted-stores-in-azure-app-configuration.md
...owto-recover-deleted-stores-in-azure-app-configuration.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation exclusively describes using the Azure Portal (a web GUI) for all operations and does not provide any command-line examples. There are no references to cross-platform CLI tools (such as Azure CLI or Azure PowerShell), nor are there any examples for Linux or macOS users. The only implicit tooling mentioned is the Azure Portal, which is platform-agnostic but GUI-centric. However, the absence of CLI instructions or examples (which are especially important for Linux users and automation) results in a bias towards Windows/GUI workflows.
Recommendations
- Add step-by-step instructions for performing all operations (create, recover, purge, enable purge protection) using Azure CLI, which is cross-platform and widely used on Linux.
- If relevant, provide Azure PowerShell examples, but always present Azure CLI examples first or alongside them to ensure Linux parity.
- Explicitly mention that all operations can be performed via CLI and provide links to relevant CLI documentation.
- Include notes or sections for automation and scripting, which are common on Linux, to ensure the documentation is inclusive of non-GUI workflows.