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 601-625 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/templates/template-tutorial-quickstart-template.md
...ger/templates/template-tutorial-quickstart-template.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation shows a mild Windows bias by listing PowerShell deployment instructions before Azure CLI, referencing PowerShell-specific syntax, and mentioning Visual Studio Code (a Microsoft tool) as the recommended editor. While Azure CLI (cross-platform) is included, the ordering and emphasis on PowerShell and Windows-centric tools may give the impression of prioritizing Windows users.
Recommendations
- Alternate the order of deployment instructions, sometimes presenting Azure CLI before PowerShell to avoid implicit prioritization.
- Explicitly mention that both Azure CLI and PowerShell are cross-platform, and provide links or notes about using them on Linux/macOS.
- Include examples or notes for Linux/macOS users, such as shell-specific syntax or environment setup tips.
- Mention alternative editors (such as VS Code, Vim, or Sublime Text) to avoid implying Visual Studio Code is required.
- Ensure that any references to tools or commands are clearly marked as cross-platform or provide platform-specific notes where differences exist.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/templates/template-specs-deploy-linked-template.md
...ger/templates/template-specs-deploy-linked-template.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by using Windows-style file paths (e.g., c:\Templates\deployTS\azuredeploy.json) throughout, and does not provide Linux/macOS equivalents or mention cross-platform considerations. All file path examples and instructions assume a Windows environment. While both Azure PowerShell and Azure CLI examples are provided, the CLI examples also use Windows paths, and there are no explicit Linux shell or path examples. There is also a note about a known issue with Windows PowerShell, but no mention of Linux-specific issues or guidance.
Recommendations
- Provide file path examples for both Windows (e.g., c:\Templates\deployTS\azuredeploy.json) and Linux/macOS (e.g., ~/Templates/deployTS/azuredeploy.json or /home/user/Templates/deployTS/azuredeploy.json) in all relevant code snippets and instructions.
- Explicitly state that the Azure CLI is cross-platform and show examples using both Windows Command Prompt/PowerShell and Linux/macOS shells (e.g., Bash).
- Include notes about any platform-specific issues for both Windows and Linux/macOS, not just Windows.
- Wherever possible, use environment variables or relative paths that are platform-agnostic in CLI examples.
- Consider adding tabs or callouts for 'Windows', 'Linux', and 'macOS' when showing command-line examples to improve clarity for users on different platforms.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/templates/template-tutorial-create-first-template.md
...r/templates/template-tutorial-create-first-template.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Azure PowerShell and Azure CLI (Bash) examples for deployment, but there is a subtle Windows bias. PowerShell is consistently listed first in code tabs and instructions, and there are explicit references to Windows-centric tools and workflows (e.g., Visual Studio Code, Windows file paths, and specific notes about running CLI commands in Windows PowerShell or Command Prompt). Installation instructions for Azure CLI list Windows before Linux and macOS. There are no Linux-specific editor or shell recommendations, and the overall tone assumes familiarity with Windows environments.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI first to reflect its cross-platform nature.
- Add explicit instructions or tips for Linux/macOS users, such as using editors like VS Code, Vim, or Nano, and handling file paths.
- Include notes about running Azure CLI in native Linux/macOS terminals, not just Bash on Windows.
- Provide parity in screenshots and examples (e.g., show both Windows and Linux terminal outputs where relevant).
- Avoid language that assumes a Windows environment (e.g., 'workstation', 'Command Prompt') and use more neutral terms.
- Mention cross-platform alternatives for tools and clarify that all steps work equally on Linux/macOS.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/templates/template-cloud-consistency.md
...source-manager/templates/template-cloud-consistency.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias in several ways: PowerShell is frequently used as the primary or sole scripting example for verifying template functions, listing resource providers, VM images, and VM sizes. Windows-specific tools and patterns (such as .ps1 scripts and Windows file paths) are referenced, and examples for Linux or Bash are absent or appear after Windows/PowerShell examples. There are no Linux shell (Bash) equivalents for key operations, and the sample artifact locations and scripts are Windows-centric.
Recommendations
- Provide equivalent Bash/Azure CLI examples alongside or before PowerShell examples for all operations, including verifying template functions, listing resource providers, VM images, and VM sizes.
- Include Linux-based script examples (e.g., .sh files) and artifact locations in addition to Windows (.ps1) scripts.
- Avoid using Windows-specific terminology or paths exclusively; when referencing scripts or artifacts, show both Windows and Linux variants.
- When demonstrating VM extensions or custom scripts, include both Windows and Linux extension types and usage.
- Ensure that any automation or testing tool recommendations (e.g., Visual Studio Code) are presented as cross-platform, and mention alternatives or usage on Linux where applicable.
- Review all code snippets and ensure parity between PowerShell and Bash/Azure CLI, especially in sections where only PowerShell is currently shown.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/templates/template-tutorial-create-templates-with-dependent-resources.md
...ate-tutorial-create-templates-with-dependent-resources.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by focusing on deploying a Windows VM template, referencing only a Windows-based example from the Quickstart Templates, and instructing users to RDP into the VM (a Windows-specific remote access method). There is no mention of Linux VM templates or SSH access, and the walkthrough does not provide parity for Linux users. Additionally, the use of Visual Studio Code is platform-neutral, but the resource deployment scenario is Windows-centric.
Recommendations
- Include a parallel example using a Linux VM template from the Azure Quickstart Templates repository, such as 'Deploy a simple Linux VM'.
- Demonstrate how to connect to a Linux VM using SSH, in addition to the RDP instructions for Windows VMs.
- Present both Windows and Linux template deployment scenarios side-by-side, or provide a clear choice at the start of the tutorial.
- When referencing remote access, mention both RDP (for Windows) and SSH (for Linux) to ensure inclusivity.
- Ensure that all code snippets and deployment steps are applicable to both Windows and Linux users, or clearly indicate which steps are platform-specific.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/templates/template-tutorial-create-multiple-instances.md
...mplates/template-tutorial-create-multiple-instances.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a mild Windows bias. Visual Studio Code is presented as the only editor, with no mention of Linux-native editors or workflows. The instructions for opening and saving files use Windows-centric UI language (e.g., File > Open File), and the only development environment mentioned is Visual Studio Code with a specific extension. While both PowerShell and Bash (CLI) examples are provided for deployment, the overall flow assumes familiarity with Windows tools and patterns, and Linux-native alternatives (such as vim, nano, or Linux file navigation) are not discussed.
Recommendations
- Include explicit instructions for Linux users, such as using editors like vim, nano, or gedit to open and edit the template file.
- When describing file operations (open, save), provide both GUI (VS Code) and command-line (cp, mv, curl, wget) alternatives.
- Mention that Visual Studio Code is cross-platform, and provide installation links or alternatives for Linux users.
- In the prerequisites, suggest Linux-native tools and extensions, or at least acknowledge their existence.
- Ensure that screenshots and UI instructions are not exclusively Windows-centric; consider including terminal-based workflows.
- Add a note that the Azure Cloud Shell Bash environment is suitable for Linux users, and clarify any differences in file paths or commands.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/templates/template-tutorial-deployment-script.md
...nager/templates/template-tutorial-deployment-script.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a strong Windows and PowerShell bias. All deployment script examples use PowerShell exclusively, and the 'kind' property for deployment scripts is set to 'AzurePowerShell', with explicit mention that only PowerShell scripts are supported. The script content, debugging, and troubleshooting instructions are all PowerShell-centric, with no Bash or Linux shell script equivalents. Even when mentioning the Azure Cloud Shell, PowerShell is presented first, and the detailed walkthroughs and error handling are PowerShell-specific. There is no example or guidance for authoring or deploying scripts using Bash or other Linux-native tools, despite Azure supporting Bash-based deployment scripts.
Recommendations
- Provide equivalent Bash (Azure CLI) deployment script examples alongside PowerShell, especially for the 'deploymentScripts' resource, and clarify when each is supported.
- Explicitly mention and demonstrate how to use 'AzureCLI' as the 'kind' for deployment scripts, including a Bash script to create and add a certificate to Key Vault.
- Ensure all code tabs and walkthroughs include both PowerShell and Bash/CLI options, not just for deployment but also for authoring and debugging scripts.
- When describing script content, include both PowerShell and Bash syntax, and link to documentation for both.
- Clarify in the prerequisites and throughout the tutorial that both Windows and Linux users are supported, and provide parity in instructions and troubleshooting steps.
- Add troubleshooting and debugging instructions for Bash-based deployment scripts, not just PowerShell.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/troubleshooting/create-troubleshooting-template.md
...ger/troubleshooting/create-troubleshooting-template.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing Azure PowerShell as the first deployment method and referencing it explicitly, while only briefly mentioning Azure CLI. There are no explicit Linux or cross-platform shell examples (e.g., Bash), and no mention of running these commands in a Linux environment or using Linux-specific tools. The examples and instructions implicitly assume familiarity with Windows-centric tools and workflows.
Recommendations
- Provide both Azure CLI and Azure PowerShell examples side by side, with CLI (which is cross-platform) listed first.
- Include explicit Bash (Linux/macOS) command-line examples for deploying ARM/Bicep templates.
- Mention that Azure CLI works on Windows, Linux, and macOS, and provide instructions for each platform where relevant.
- Avoid listing Windows/PowerShell tools before cross-platform alternatives unless there is a technical reason.
- Add a section or note about running deployments from Linux/macOS terminals, including any differences or prerequisites.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/templates/template-tutorial-use-parameter-file.md
...ager/templates/template-tutorial-use-parameter-file.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation presents both PowerShell and Azure CLI examples for deploying ARM templates, but PowerShell (a Windows-centric tool) is consistently listed first in each example section. The prerequisites recommend Visual Studio Code and the Resource Manager Tools extension, which are cross-platform, but there is no mention of Linux-native editors or workflows. The troubleshooting note refers to 'verbose' and 'debug' switches without clarifying their usage in both CLI and PowerShell contexts. There are no explicit Linux shell (bash) examples or references to Linux-specific tools or workflows.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or default to Azure CLI first, as it is cross-platform and more common on Linux.
- Explicitly mention that all CLI commands work on Linux, macOS, and Windows, and provide bash/zsh syntax where appropriate.
- Include Linux-native editor options (e.g., vim, nano) in the prerequisites, or clarify that Visual Studio Code is available on Linux.
- Add a note or section on running these commands in a Linux environment, including any differences in file paths or environment setup.
- Clarify the use of 'verbose' and 'debug' switches in both PowerShell and Azure CLI contexts.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/troubleshooting/common-deployment-errors.md
...ce-manager/troubleshooting/common-deployment-errors.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page exhibits mild Windows bias. In the 'ResourceGroupNotFound' error, both Azure CLI and PowerShell are mentioned, but PowerShell is listed after CLI, which is positive. However, throughout the page, there are several instances where Windows-specific links or tools are mentioned either before or more prominently than Linux equivalents. For example, in the 'AllocationFailed' error, the link to Linux troubleshooting is listed before Windows, which is good, but in 'SubnetsNotInSameVnet', the Windows VM link is listed before the Linux VM link. Additionally, PowerShell is referenced as a primary tool for context management, and there are no explicit Linux shell (bash) or cross-platform command examples. There is also a general lack of Linux-specific command-line examples or references to bash/Unix tools, and no mention of cross-platform scripting approaches.
Recommendations
- Ensure that Linux and Windows examples/links are always presented together and alternate which comes first, or use alphabetical order.
- Include bash/Azure CLI examples and references alongside PowerShell, especially for common operations like setting context.
- Where PowerShell is mentioned, clarify that it is available cross-platform, or provide equivalent bash/CLI commands.
- Audit all links to ensure Linux and Windows parity, and avoid listing Windows tools or documentation first by default.
- Add explicit Linux troubleshooting steps or references where only Windows tools or approaches are mentioned.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/troubleshooting/enable-debug-logging.md
...source-manager/troubleshooting/enable-debug-logging.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows/PowerShell bias by exclusively using Azure PowerShell cmdlets for enabling debug logging, with no Linux-native or cross-platform alternatives. All setup and removal examples are provided first and in detail for PowerShell, a Windows-centric tool, while Azure CLI (which is cross-platform and more common on Linux/macOS) is only mentioned as not supporting the feature or for read-only operations. There are no Bash, shell, or Linux-specific workflow examples, and the documentation assumes access to PowerShell for critical functionality.
Recommendations
- Provide parity for enabling debug logging in Azure CLI, or clearly document the lack of feature and suggest workarounds for Linux/macOS users.
- If PowerShell is required, explicitly state that it is available cross-platform (via PowerShell Core) and provide installation instructions for Linux/macOS.
- Include Bash or shell script examples where possible, especially for tasks like querying or deleting deployments.
- Reorder sections or provide Azure CLI examples before PowerShell where CLI is supported, to avoid Windows-first bias.
- Advocate for feature parity in Azure CLI, or link to feature requests/issues so Linux users can track progress.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/templates/template-tutorial-use-conditions.md
...-manager/templates/template-tutorial-use-conditions.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a Windows-first and PowerShell-heavy approach. The main template example is for a Windows VM, and all deployment and cleanup scripts are provided only in PowerShell, with no equivalent Azure CLI (Bash) or Linux-focused examples. The instructions and screenshots reference Windows tools and workflows (e.g., Visual Studio Code, PowerShell), and there is no mention of Linux VM templates or Bash/CLI deployment commands.
Recommendations
- Provide parallel examples for deploying a Linux VM (e.g., link to or use the 'vm-simple-linux' template alongside the Windows one).
- Include Azure CLI (az) commands for template deployment and resource cleanup, and show how to run them in Bash.
- When referencing Cloud Shell, give equal prominence to Bash and PowerShell, and provide code snippets for both.
- Balance the use of Windows-specific tools (like PowerShell) with Linux/Unix equivalents, and mention cross-platform editors (e.g., VS Code is cross-platform, but clarify that it works on Linux/Mac as well).
- Add notes or sections for users on Linux or Mac, clarifying any differences in workflow or commands.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/devtest-labs/quickstarts/create-lab-rest.md
...//articles/devtest-labs/quickstarts/create-lab-rest.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively uses PowerShell scripts and Windows-centric tooling (Az PowerShell module) for all steps, including authentication, request construction, and REST invocation. There are no examples or instructions for Linux or cross-platform environments (e.g., Bash, Azure CLI, curl). This creates a strong Windows and PowerShell bias, potentially alienating users on Linux or macOS.
Recommendations
- Provide equivalent examples using Bash shell with curl or HTTPie for REST API calls.
- Include Azure CLI (az) commands for authentication and token retrieval, which are cross-platform.
- Explicitly mention that the instructions are valid on Windows and provide a parallel section for Linux/macOS users.
- Avoid requiring the Az PowerShell module as the only prerequisite; suggest alternatives like Azure CLI.
- Where file paths are referenced (e.g., path\body.json), use POSIX-style paths or clarify for both Windows and Linux.
- Add a note about cross-platform compatibility and link to relevant Azure REST API usage guides for Linux/macOS.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/troubleshooting/deployment-quota-exceeded.md
...e-manager/troubleshooting/deployment-quota-exceeded.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides both Azure CLI (with Bash scripting) and PowerShell examples for managing deployment history. However, the PowerShell section is presented after the Azure CLI section, but the CLI examples assume a Bash environment without explicitly mentioning Windows Command Prompt or PowerShell Core on Windows. There is no explicit Windows-only tool, but the Bash scripting in the CLI section may not work natively on Windows without WSL or similar. The PowerShell examples are Windows-centric and do not mention cross-platform PowerShell Core usage. There are no Command Prompt (cmd.exe) examples, and Linux users are only supported via Bash scripting, which is not explicitly clarified as Linux/macOS or WSL on Windows.
Recommendations
- Explicitly state that the Azure CLI Bash examples are intended for Linux/macOS or WSL on Windows, and provide equivalent examples for Windows Command Prompt or PowerShell Core if possible.
- Clarify that PowerShell examples can be used on both Windows PowerShell and cross-platform PowerShell Core.
- Consider providing a table or section that summarizes which commands/scripts are suitable for which platforms (Windows, Linux, macOS).
- Add notes or links for users on how to run Bash scripts on Windows (e.g., via WSL, Git Bash, or Cygwin) if they are using Azure CLI.
- Ensure parity by including examples for all major platforms or by clearly indicating platform requirements for each example.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/templates/template-tutorial-use-key-vault.md
...e-manager/templates/template-tutorial-use-key-vault.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong Windows and PowerShell bias. All command-line examples for resource creation, deployment, and validation use Azure PowerShell, with no equivalent Azure CLI (Bash) or Linux-native instructions. The tutorial centers on deploying a Windows VM, and the only VM template referenced is for Windows. The instructions for connecting to the VM use RDP, which is Windows-specific. There is minimal mention of Bash or Linux workflows, and no Linux VM deployment example is provided.
Recommendations
- Provide Azure CLI (az) command examples alongside PowerShell for all resource creation, deployment, and validation steps. Show both PowerShell and Bash syntax where appropriate.
- Include a Linux VM deployment example (e.g., using the 'vm-simple-linux' template) and show how to retrieve secrets for a Linux VM admin password.
- When demonstrating how to connect to the VM, include SSH instructions for Linux VMs, not just RDP for Windows.
- In the 'Deploy the template' section, show both PowerShell and CLI commands for deploying ARM templates.
- Balance the order of presentation: mention Linux/Bash/CLI options at least as prominently as Windows/PowerShell, rather than as an afterthought.
- Reference Linux password requirements and provide links to Linux VM documentation, not just Windows.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/troubleshooting/error-register-resource-provider.md
...er/troubleshooting/error-register-resource-provider.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides detailed examples for both Azure CLI and Azure PowerShell, with the PowerShell section being prominent and comprehensive. PowerShell is a Windows-centric tool, and there are no explicit Linux shell (bash) or cross-platform scripting examples beyond Azure CLI. The ordering of sections places Azure CLI first, but the PowerShell section is equally detailed and assumes familiarity with Windows tooling. There are no bash or Linux-native command examples, and the documentation does not mention or address Linux-specific considerations or tools.
Recommendations
- Add explicit bash/Linux shell examples for all Azure CLI commands, demonstrating usage in a Linux terminal environment.
- Clarify that Azure CLI commands are fully cross-platform and provide any Linux-specific notes if needed (e.g., differences in quoting or output parsing).
- Consider including a section or tab for bash scripting, showing how to automate provider registration in Linux environments.
- Review language to ensure parity, e.g., avoid assuming PowerShell as the default scripting environment.
- If relevant, mention that Azure CLI is available on Windows, macOS, and Linux, and provide installation links for each.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/troubleshooting/error-not-found.md
...re-resource-manager/troubleshooting/error-not-found.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias by referencing PowerShell and Azure CLI together, but listing PowerShell (a Windows-centric tool) first and linking to its documentation before Azure CLI. There are no explicit Linux shell (bash) examples, and the only command-line context is given in terms of PowerShell and Azure CLI, with no mention of Linux-specific tools or workflows. The portal is referenced as a GUI, which is cross-platform, but no parity is provided for Linux-native command-line environments.
Recommendations
- When mentioning command-line tools, alternate the order (e.g., 'Azure CLI or PowerShell') or provide separate, parallel examples for both environments.
- Include explicit bash/Linux shell examples for common operations, such as changing subscriptions or querying resources, to ensure Linux users are equally supported.
- Where possible, provide links to both PowerShell and Azure CLI documentation, and consider referencing Azure CLI (which is cross-platform) before PowerShell.
- Add notes or callouts for Linux/macOS users, especially where command syntax or environment setup may differ.
- Ensure that troubleshooting steps and examples are not Windows-centric by default, and that Linux users are not required to infer how to adapt instructions.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/templates/test-toolkit.md
...icles/azure-resource-manager/templates/test-toolkit.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation is heavily centered around PowerShell, which is a Windows-native tool, and all usage examples (including on Linux and macOS) require PowerShell. The toolkit itself is implemented as PowerShell scripts, and there are no examples or guidance for using the toolkit with native Linux/Unix shells or tools (such as Bash, sh, or Python). The Windows installation section appears first, reinforcing a Windows-first perspective. There is no mention of alternative approaches for Linux users who may not wish to install PowerShell.
Recommendations
- Provide native Bash or shell script examples for Linux and macOS users, or clarify if PowerShell Core is the only supported runtime.
- Consider developing or highlighting any cross-platform wrappers or CLI tools (e.g., a Docker container or a dotnet global tool) that do not require PowerShell.
- Reorder the installation instructions to present Linux and macOS equally or before Windows, or group them together to avoid a Windows-first impression.
- Explicitly state in the introduction that PowerShell Core is required on all platforms, and provide rationale for this dependency.
- If possible, offer guidance for integrating the toolkit into common Linux CI/CD environments (e.g., GitHub Actions, Azure Pipelines with Bash).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-signalr/concept-connection-string.md
...n//articles/azure-signalr/concept-connection-string.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates some Windows bias by referencing Windows-specific tools (such as .NET Secret Manager and environment variable conventions) without providing equivalent Linux examples or clarifying cross-platform usage. The examples for setting environment variables and secrets are tailored to Windows/PowerShell conventions, and there is no mention of Linux shell equivalents or differences. Additionally, the documentation refers to configuration patterns and tools (like dotnet user-secrets) that are more common in Windows development environments, without balancing with Linux-native approaches.
Recommendations
- Provide explicit Linux/bash equivalents for all command-line examples, such as using 'export Azure__SignalR__ConnectionString=...' for environment variables.
- Clarify that .NET Secret Manager and environment variable conventions work cross-platform, and provide instructions for both Windows (cmd/PowerShell) and Linux (bash/zsh) shells.
- Mention Linux-native secret management tools (such as environment files, systemd environment configuration, or integration with Linux keyrings) where appropriate.
- Ensure that any references to file paths or configuration files use cross-platform notation or provide both Windows and Linux path examples.
- Add a section or note highlighting cross-platform considerations for configuring connection strings in different environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/troubleshooting/error-sku-not-available.md
...rce-manager/troubleshooting/error-sku-not-available.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing detailed PowerShell scripts and explanations, referencing Windows-specific tools (PowerShell cmdlets), and using Windows-style file paths in examples. While Azure CLI examples are included (which are cross-platform), the PowerShell section is more extensive and detailed. There are no explicit Linux shell (bash) or macOS-specific examples, and the REST example uses a Windows path for output. The documentation does not mention or show Linux-native command-line patterns (e.g., jq, grep, bash scripting), and the PowerShell section precedes the portal and REST sections, reinforcing a Windows-first approach.
Recommendations
- Add Linux/macOS shell (bash) examples for filtering and processing az vm list-skus output, such as using jq or grep to filter SKUs.
- In REST examples, use cross-platform output paths (e.g., ./sku-list.json instead of .\sku-list.json) or show both Windows and Linux path variants.
- Balance the depth of PowerShell and CLI sections; provide equally detailed CLI (bash) scripts for advanced filtering, not just single commands.
- Explicitly mention that Azure CLI commands work on Windows, Linux, and macOS, and provide sample shell scripts for common Linux workflows.
- Consider reordering sections or providing a note that PowerShell is primarily for Windows users, while CLI/bash examples are for all platforms.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/troubleshooting/quickstart-troubleshoot-bicep-deployment.md
...leshooting/quickstart-troubleshoot-bicep-deployment.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Azure CLI and PowerShell examples for deployment and cleanup tasks. However, PowerShell is featured equally and sometimes with more detail (such as parameter replacement instructions), which may indicate a bias toward Windows users. There is no mention of Linux-specific shell environments, nor are there explicit Bash or Linux terminal examples. The prerequisites mention Visual Studio Code and the Bicep extension, which are cross-platform, but do not mention any Linux-specific editors or tools. The use of PowerShell and its cmdlets, as well as the lack of explicit Linux/Bash guidance, suggests a Windows-centric approach.
Recommendations
- Include explicit Bash/Linux shell examples alongside PowerShell, especially for Azure CLI commands.
- Clarify that Azure CLI examples work on all platforms, and provide sample commands in a Bash-friendly format (e.g., using export for environment variables, or showing Linux-style line continuations).
- If PowerShell is included, also mention cross-platform PowerShell Core, or clarify when Windows-only features are used.
- Add notes or examples for using common Linux editors (e.g., Vim, Nano) for editing Bicep files, or at least acknowledge their use.
- Ensure that instructions for parameter replacement or file handling do not assume Windows conventions (e.g., file paths, quoting).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-signalr/signalr-howto-use.md
...blob/main//articles/azure-signalr/signalr-howto-use.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing installation instructions for the legacy ASP.NET SignalR SDK exclusively via the Package Manager Console (a Windows/Visual Studio tool), and using PowerShell syntax for package installation. There are no Linux or cross-platform alternatives (such as dotnet CLI or NuGet CLI) mentioned for legacy ASP.NET SignalR. The configuration instructions reference 'web.config', which is common in Windows/IIS environments, without mentioning Linux hosting scenarios or equivalents.
Recommendations
- Provide cross-platform installation instructions for the legacy ASP.NET SignalR SDK, such as using the dotnet CLI or NuGet CLI, in addition to the Package Manager Console.
- Include Linux-friendly examples and mention how to configure connection strings and settings when hosting on Linux (e.g., using environment variables or appsettings.json where possible).
- Avoid referencing only Windows-specific tools (like Package Manager Console) or, if necessary, present Linux/cross-platform alternatives first or alongside.
- Clarify that 'web.config' is specific to certain hosting environments and suggest alternatives for Linux or containerized deployments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/digital-twins/concepts-ontologies-convert.md
.../articles/digital-twins/concepts-ontologies-convert.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page focuses exclusively on .NET Core and C# tooling (dotNetRDF, .NET Core CLI), with no mention of Linux or cross-platform usage, nor any examples or instructions for Linux users. Download instructions reference ZIP files and screenshots that are Windows-centric, and there are no alternative examples or guidance for Linux or macOS environments.
Recommendations
- Include explicit instructions for running the sample applications on Linux (and macOS), such as using 'dotnet' CLI commands on Linux terminals.
- Provide code snippets or shell commands (e.g., bash) for Linux users, alongside or instead of Windows/PowerShell examples.
- Mention that .NET Core is cross-platform and provide installation links for Linux and macOS.
- Add guidance for extracting ZIP files on Linux (e.g., using 'unzip' command), and consider including tar.gz archives as an alternative.
- Show screenshots or terminal examples from Linux environments, or at least clarify that the tools and samples work on all major platforms.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-signalr/signalr-overview.md
.../blob/main//articles/azure-signalr/signalr-overview.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Aspnet Core Heavy
Summary
The documentation page demonstrates a bias towards Windows and Microsoft-centric technologies by focusing almost exclusively on ASP.NET Core and ASP.NET for server-side development, without mentioning or providing examples for Linux-based frameworks or non-.NET server environments. There are no Linux-specific instructions, tools, or examples, and the documentation assumes the use of Microsoft technologies as the default approach.
Recommendations
- Include examples and guidance for using Azure SignalR Service with popular Linux-based server frameworks (e.g., Node.js, Python, Java) in addition to ASP.NET Core.
- Explicitly mention and provide sample code for deploying and managing SignalR Service from Linux environments, including CLI commands that work cross-platform.
- Highlight non-Windows development workflows, such as using Visual Studio Code on Linux or Mac, and provide parity in documentation for non-Windows users.
- Clarify that SignalR Service can be integrated with any backend capable of speaking the SignalR protocol, not just ASP.NET Core, and link to relevant cross-platform resources.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/devtest-labs/use-command-line-start-stop-virtual-machines.md
...t-labs/use-command-line-start-stop-virtual-machines.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation demonstrates a Windows bias by providing detailed PowerShell examples and instructions before Azure CLI, emphasizing PowerShell/Windows tooling (e.g., Connect-AzAccount, Set-AzContext), and using Windows command syntax (e.g., REM, set) alongside Bash. While Azure CLI examples are present, the documentation often references Windows environments and tools first or exclusively, and the PowerShell section is more detailed and prominent.
Recommendations
- Ensure equal depth and clarity for both PowerShell and Azure CLI sections, including troubleshooting and context.
- When presenting Azure CLI examples, consistently provide both Bash and Windows CMD syntax side-by-side, and clarify which is preferred for cross-platform use.
- Avoid using Windows-specific comments (e.g., REM) in CLI examples unless also providing the Bash equivalent (e.g., #).
- List Azure CLI and PowerShell options in parallel rather than always leading with PowerShell.
- Explicitly mention Linux/macOS compatibility and provide guidance for those environments where relevant.
- Where possible, use cross-platform terminology (e.g., 'terminal' instead of 'command prompt').