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 551-575 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/management/create-private-link-access-commands.md
...ager/management/create-private-link-access-commands.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides both Azure CLI and PowerShell examples, but PowerShell is featured as a primary scripting example alongside CLI, which can indicate a Windows bias. PowerShell is traditionally associated with Windows environments, and there are no explicit Linux shell (bash) or scripting examples. Additionally, PowerShell is mentioned before REST in each section, and there is no mention of Linux-specific tools or patterns. The documentation assumes familiarity with PowerShell and does not provide parity for Linux-native users beyond the CLI.
Recommendations
- Add explicit bash shell examples for all CLI commands, including sample scripts that demonstrate usage in a Linux environment.
- Clarify that Azure CLI commands work cross-platform and provide notes or tips for Linux/macOS users (e.g., differences in login methods, environment variables).
- Avoid positioning PowerShell as the default or primary scripting language; instead, present CLI and REST as the main cross-platform options, with PowerShell as an additional example.
- Include troubleshooting or environment setup notes for Linux users, such as package installation commands or shell environment considerations.
- Where possible, link to Linux-specific documentation or guides for related tasks.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/devtest-labs/test-app-azure.md
...ocs/blob/main//articles/devtest-labs/test-app-azure.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily oriented toward Windows environments. It assumes the use of Visual Studio (a primarily Windows IDE), requires a Windows-based DevTest Labs VM, and provides only instructions and screenshots for Windows tools and workflows (e.g., File Explorer, RDP). There are no examples or guidance for Linux-based VMs, nor any mention of Linux tools or mounting procedures.
Recommendations
- Add parallel instructions for publishing and testing apps on Linux-based DevTest Labs VMs.
- Include examples for mounting Azure file shares on Linux (e.g., using the 'mount' command or SMB utilities).
- Provide guidance for connecting to Linux VMs (e.g., using SSH instead of RDP).
- Mention and, where possible, provide examples for cross-platform IDEs or CLI-based workflows (such as using VS Code or the .NET CLI).
- Ensure screenshots and step-by-step instructions are available for both Windows and Linux environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/management/move-limitations/cloud-services-extended-support.md
...nt/move-limitations/cloud-services-extended-support.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page references Azure PowerShell before Azure CLI when listing tools for moving resources, which may suggest a Windows-first or PowerShell-heavy bias. There are no explicit Linux-specific examples or mentions of Linux tools, and the documentation does not provide command-line examples for either platform, but the ordering and mention of PowerShell first is a subtle indicator of bias.
Recommendations
- List Azure CLI before Azure PowerShell when mentioning cross-platform tools, as Azure CLI is natively cross-platform.
- Provide explicit command-line examples for both Azure CLI and Azure PowerShell, ensuring parity.
- Mention that Azure CLI is available on Windows, Linux, and macOS to reinforce cross-platform support.
- If referencing the Azure Portal, clarify that it is web-based and platform-agnostic.
- Consider including bash or shell script examples where appropriate to further support Linux users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/management/move-resource-group-and-subscription.md
...ger/management/move-resource-group-and-subscription.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias: PowerShell is presented as a primary automation tool alongside Azure CLI, and in some places, PowerShell examples are given equal or greater prominence than CLI/Bash. The CLI examples reference Bash but do not provide explicit Linux shell guidance or mention cross-platform differences. There is no mention of Linux-specific tools or environments, and the PowerShell examples assume familiarity with Windows-centric scripting. The documentation does not clarify that Azure CLI is cross-platform or provide explicit Linux shell examples, and there is no mention of Linux-native scripting or automation approaches.
Recommendations
- Explicitly state that Azure CLI is cross-platform and works on Linux, macOS, and Windows.
- Provide example commands in both Bash (Linux/macOS) and PowerShell (Windows), especially where scripting or variable assignment is shown.
- Avoid presenting PowerShell examples before or with equal prominence to Bash/CLI unless justified by usage statistics; prioritize Bash for CLI examples.
- Where PowerShell is used, clarify that it is available cross-platform, but also provide native Bash alternatives for Linux users.
- Include notes or sections on running these commands in Linux environments (e.g., Ubuntu, CentOS), and address any OS-specific considerations.
- Mention Linux-native automation tools or scripting (e.g., shell scripts) where relevant.
- Ensure screenshots and UI references do not assume a Windows environment unless unavoidable.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/management/relocation/relocation-key-vault.md
...-manager/management/relocation/relocation-key-vault.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows/PowerShell bias by providing detailed PowerShell instructions and examples, while omitting equivalent Azure CLI (cross-platform) or Bash examples. The PowerShell approach is presented as the only scripting alternative to the Azure Portal, and there are no explicit Linux or macOS command-line instructions. References to obtaining region codes and resource management are given only in PowerShell, not in Azure CLI. This may disadvantage users on Linux or macOS, or those who prefer cross-platform tools.
Recommendations
- Add Azure CLI examples alongside PowerShell for all operations, including exporting and deploying templates, obtaining region codes, and managing resources.
- Include Bash shell snippets where appropriate, especially for file operations or scripting steps.
- When listing options for configuring resources (such as service endpoints), mention Azure CLI before or alongside PowerShell, to avoid 'windows_first' ordering.
- Explicitly state that all steps can be performed on Linux/macOS using Azure CLI, and provide links to relevant CLI documentation.
- Consider adding a tabbed interface for 'Azure CLI', 'PowerShell', and 'Portal' to ensure parity and clarity for all platforms.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/management/microsoft-resources-move-regions.md
...manager/management/microsoft-resources-move-regions.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively using Windows-style paths (e.g., c:\export), omitting Linux/macOS path examples, and referencing deployment steps and tools in a way that assumes a Windows environment. Both Azure PowerShell and Azure CLI examples use Windows file paths, and there is no mention of Linux/macOS equivalents or considerations.
Recommendations
- Provide both Windows and Linux/macOS path examples in all CLI and PowerShell commands (e.g., c:\export and ~/export).
- Explicitly mention that Azure CLI and PowerShell are cross-platform, and show how to use them on Linux/macOS.
- Include notes or sections for Linux/macOS users, highlighting any differences in command usage or environment setup.
- Avoid assuming the use of Windows-only tools or patterns (such as backslashes in paths) in generic documentation.
- Where file system paths are referenced, use environment-agnostic variables or show both styles side by side.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/devtest-labs/personal-data-delete-export.md
...//articles/devtest-labs/personal-data-delete-export.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation provides only Azure PowerShell examples for exporting personal data, with no mention of Linux, Bash, Azure CLI, or cross-platform alternatives. All instructions and code samples are tailored to Windows/PowerShell users, and Windows tooling is referenced exclusively. There is no guidance for users on Linux or macOS platforms.
Recommendations
- Add equivalent Azure CLI (az) examples for exporting personal data, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Explicitly mention that the export process can be performed from Linux/macOS using Azure CLI or Bash scripts.
- Provide Bash script examples or step-by-step instructions for Linux users.
- Structure the documentation so that both PowerShell and CLI/Bash options are presented, or at least reference the availability of cross-platform tools.
- Avoid assuming PowerShell as the default or only method; clarify tool prerequisites for each platform.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/management/relocation/relocation-storage-account.md
...er/management/relocation/relocation-storage-account.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 bias by providing only PowerShell-based CLI examples for exporting, modifying, and deploying Azure Resource Manager templates. There are no Bash, Azure CLI, or Linux-native command examples. The PowerShell approach is presented as the sole scripting method, and region code discovery is shown only via PowerShell commands. While AzCopy is mentioned (which is cross-platform), all automation and scripting guidance is Windows/PowerShell-centric, with no parity for Linux or macOS users.
Recommendations
- Add Azure CLI (az) command examples alongside PowerShell for all template export, modification, and deployment steps. Azure CLI is cross-platform and widely used on Linux and macOS.
- Include Bash shell script examples for common operations, such as deploying templates and managing resources.
- When referencing tools like AzCopy, explicitly mention that it is available for Windows, Linux, and macOS, and provide example commands for each platform.
- For region code discovery, show how to list regions using Azure CLI (e.g., 'az account list-locations') in addition to PowerShell.
- Ensure that all instructions and code snippets are available in both PowerShell and Bash/Azure CLI tabs, so users on any OS can follow the documentation without needing to adapt Windows-centric instructions.
- Consider adding a section or note about cross-platform compatibility and how to choose the right tool for your OS.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/management/manage-resources-rest.md
...e-resource-manager/management/manage-resources-rest.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for obtaining access tokens and making REST API calls, but consistently presents Azure CLI (Linux-friendly) examples before PowerShell (Windows-centric) ones. However, PowerShell is a Windows-native tool, and its inclusion as a primary example (with detailed scripting) may indicate a slight Windows bias. Additionally, references to Visual Studio Code and Azure PowerShell for template deployment reinforce a Windows-oriented workflow, while Linux-native tools or editors are not mentioned. There are no missing Linux examples for the main REST/cURL flows, but the documentation could better highlight Linux parity and alternatives.
Recommendations
- Continue to provide Azure CLI examples first, as it is cross-platform and Linux-friendly.
- When referencing editors or tools (e.g., Visual Studio Code), mention that it is cross-platform, or suggest alternative Linux editors (e.g., Vim, Emacs, nano) for editing templates.
- For PowerShell examples, clarify that PowerShell Core is available on Linux, or provide Bash script alternatives for more complex flows.
- Avoid referencing Windows-specific tools or workflows (such as 'Azure PowerShell' or 'Visual Studio Code') without also mentioning Linux-compatible options.
- Explicitly state that all REST/cURL examples are platform-agnostic and can be run on Linux, macOS, or Windows.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/management/relocation/relocation-virtual-network-nsg.md
...anagement/relocation/relocation-virtual-network-nsg.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation provides detailed instructions for performing the NSG relocation using the Azure Portal and Azure PowerShell. All CLI-based automation examples are exclusively in PowerShell, with no mention of Azure CLI (az) or Bash scripting, which are cross-platform and preferred by many Linux users. Additionally, references to tools like 'notepad' and the use of PowerShell cmdlets reinforce a Windows-centric approach. There are no Linux-specific or cross-platform command-line examples, and PowerShell is presented before any mention of alternatives.
Recommendations
- Add equivalent instructions and examples using Azure CLI (az) commands, which are cross-platform and commonly used on Linux and macOS.
- Include Bash scripting examples for template editing and deployment, or at least mention compatible editors (e.g., vim, nano, code) instead of only 'notepad'.
- Where PowerShell is referenced, clarify that Azure CLI is also supported and provide links or tabs for both.
- Ensure that all automation steps (export, edit, deploy, cleanup) have both PowerShell and Azure CLI/Bash equivalents.
- Avoid assuming the user's environment is Windows; use neutral language and tool references where possible.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/management/relocation/relocation-app-service.md
...anager/management/relocation/relocation-app-service.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific paths (e.g., %HOME%\site), using terminology and tools more familiar to Windows users (such as Kudu and PowerShell), and omitting Linux-specific examples or equivalents. The only explicit scripting example in 'Next steps' is for PowerShell, and there are no CLI/bash/Linux-native instructions or references to Linux file paths. Windows conventions and tools are mentioned before or instead of cross-platform or Linux alternatives.
Recommendations
- Include Linux file path examples (e.g., $HOME/site or /home/site/wwwroot) alongside Windows paths.
- Provide Azure CLI and Bash script examples in addition to or before PowerShell examples, especially in 'Next steps' and automation sections.
- Mention Kudu's cross-platform nature and clarify its usage for both Windows and Linux App Service plans.
- Add explicit guidance for Linux-based App Service plans, including any differences in backup/restore, file access, and deployment.
- Ensure references to tools and configuration (such as FTP, file system, and environment variables) are platform-neutral or provide both Windows and Linux instructions.
- In all code or command snippets, offer both PowerShell and Bash/CLI equivalents.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/management/move-support-resources.md
...-resource-manager/management/move-support-resources.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page is largely platform-neutral, focusing on Azure resource types and their move capabilities. However, there are isolated instances of Windows bias: a reference to a PowerShell script for region moves (Microsoft.Automation), and guidance for SQL virtual machines that links only to Windows-specific instructions for managing the SQL IaaS Agent extension. There are no explicit Linux or cross-platform CLI examples, and the only script-based example is PowerShell, which is Windows-centric.
Recommendations
- Where scripts are referenced (e.g., Microsoft.Automation), provide both PowerShell and Azure CLI (az) examples, with clear instructions for Linux/macOS users.
- For SQL virtual machine move guidance, include links or instructions for both Windows and Linux-based SQL Server VMs, or clarify if the process is identical.
- Audit all linked guidance (e.g., move-limitations/app-service-move-limitations.md, automation-disaster-recovery.md) to ensure Linux parity in examples and tooling.
- Where possible, prefer cross-platform tools (Azure CLI, REST API) in examples and documentation, or present them before Windows-specific tools.
- Explicitly mention if a process or tool is Windows-only, and provide alternatives for Linux users when available.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/management/relocation/relocation-backup.md
...rce-manager/management/relocation/relocation-backup.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias. In several sections, Windows-specific instructions or references are given before Linux equivalents, and in some cases, Linux guidance is generic or deferred to 'distributor guidance' rather than providing concrete steps or examples. The only script example is an Azure PowerShell snippet, with no CLI or Bash equivalent. There are also references to Windows update procedures, but Linux instructions are less explicit. No Linux-specific backup agent or tooling is mentioned for on-premises scenarios.
Recommendations
- Provide explicit Linux examples and commands alongside Windows instructions, especially for certificate updates and agent configuration.
- Include Azure CLI and/or Bash script examples wherever PowerShell is used.
- When referencing OS-specific procedures (like updating certificates), provide step-by-step guidance or link to authoritative Linux documentation, not just 'distributor guidance'.
- Mention Linux backup agents or supported tools for on-premises workloads, not just MARS (which is Windows-only).
- Ensure that in lists or instructions, Linux and Windows are given equal prominence, not always listing Windows first.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/management/relocation/relocation-automation.md
...manager/management/relocation/relocation-automation.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell examples for exporting and importing runbooks, and referencing Azure PowerShell as a primary deployment method. There are no examples or guidance for performing these actions using cross-platform tools such as Azure CLI, REST API, or scripting languages commonly used on Linux. This may hinder Linux users or those working in non-Windows environments.
Recommendations
- Provide equivalent Azure CLI commands for exporting and importing runbooks, as well as for deploying templates.
- Include examples or references for using REST API or ARM/Bicep/Terraform from Linux/macOS environments.
- Explicitly mention that PowerShell Core is cross-platform, if PowerShell must be used, and provide installation guidance for Linux/macOS.
- Add a section or callout for Linux/macOS users, outlining supported tools and workflows.
- Ensure that all steps referencing PowerShell have parallel instructions for Azure CLI or other cross-platform tools.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/management/relocation/relocation-firewall.md
...e-manager/management/relocation/relocation-firewall.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a significant Windows bias. All command-line examples are provided exclusively using Azure PowerShell, with no mention or examples of Azure CLI (which is cross-platform and preferred by many Linux users). The 'PowerShell' tab is used for all scripted instructions, and there are no Bash or Linux shell equivalents. Additionally, the documentation refers to 'PowerShell' and 'Azure portal' as the only two options, omitting Linux-native workflows. The use of Windows-centric tools and patterns is evident, and the ordering of examples always places Windows/PowerShell first or exclusively.
Recommendations
- Add Azure CLI (az) examples alongside PowerShell for all scripted operations, including exporting, modifying, and deploying ARM templates.
- Include Bash/Linux shell command examples where relevant, especially for file operations (e.g., unzipping files, editing JSON).
- Clearly label tabs as 'Azure CLI' and 'PowerShell' to provide parity and make it easier for Linux users to follow.
- Mention that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
- Ensure that references to creating or managing resources via command line include both PowerShell and CLI options, and avoid implying PowerShell is the only or primary method.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/management/relocation/relocation-event-hub.md
...-manager/management/relocation/relocation-event-hub.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing a dedicated PowerShell section for template modification, referencing PowerShell commands (Get-AzLocation) for obtaining region codes, and omitting equivalent Azure CLI or Bash instructions. The PowerShell example is given its own tab, but there is no corresponding Azure CLI or Linux shell example, and the only command-line example is Windows-centric. Additionally, the documentation refers to the Azure portal (web UI) throughout, which is cross-platform, but when it comes to scripting or automation, only PowerShell is highlighted.
Recommendations
- Add an Azure CLI (az) example tab alongside PowerShell and Portal for template deployment and modification steps.
- Provide the equivalent Azure CLI command for obtaining region codes (e.g., 'az account list-locations').
- Ensure all scripting and automation steps are demonstrated using both PowerShell and Azure CLI to support Linux/macOS users.
- Where possible, include Bash shell examples for common tasks, or clarify that the steps are cross-platform.
- Review all references to command-line tooling to ensure parity between Windows and Linux environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/management/relocation/relocation-container-registry.md
...management/relocation/relocation-container-registry.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing PowerShell commands (e.g., Get-AzContainerRegistryRepository, Import-AzContainerImage, Set-AzAksCluster) without equivalent Bash or cross-platform examples. In several cases, PowerShell commands are mentioned before or instead of Azure CLI or Bash alternatives. There is also a lack of explicit Linux/macOS command examples for tasks like enumerating repositories or integrating with AKS, despite Azure CLI being available cross-platform.
Recommendations
- For every PowerShell example, provide an equivalent Azure CLI/Bash example, especially for common tasks like listing repositories, importing images, and integrating with AKS.
- When mentioning both Azure CLI and PowerShell, list Azure CLI (cross-platform) first, or present both options side-by-side.
- Explicitly state when a command is platform-specific, and provide guidance for both Windows and Linux/macOS users.
- Review all command snippets and ensure Linux/macOS users can follow the steps without needing to translate PowerShell commands.
- Where possible, use Azure CLI as the primary example, since it is available on all platforms.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/management/relocation/relocation-functions.md
...-manager/management/relocation/relocation-functions.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates subtle Windows bias by referencing Windows-style paths (e.g., %HOME%\site), mentioning Azure PowerShell alongside Azure CLI (but not Bash or Linux-specific tools), and using Windows terminology and patterns before or instead of Linux equivalents. There are no explicit Linux command-line examples, and the guidance assumes familiarity with Windows conventions. While Linux is mentioned (e.g., Linux containers, explicitly mounted shares), practical Linux-oriented examples or instructions are missing.
Recommendations
- Provide explicit Linux/Bash command examples alongside or before PowerShell examples, especially for common deployment and file management tasks.
- Use platform-neutral environment variables and paths (e.g., $HOME/site for Linux, %HOME%\site for Windows), or clarify both formats when referencing file locations.
- Include references to Linux-native tools (such as Bash scripts, az CLI in Bash, or Linux file system conventions) where appropriate.
- Ensure that instructions and terminology are inclusive of both Windows and Linux users, avoiding Windows-first language or assumptions.
- Add a section or callouts specifically addressing Linux deployment scenarios, including container-based workflows and file system considerations.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/devtest-labs/start-machines-use-automation-runbooks.md
...devtest-labs/start-machines-use-automation-runbooks.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page exclusively uses PowerShell scripts and Azure Automation runbooks, both of which are traditionally Windows-centric. All examples and instructions are provided for PowerShell, with no mention of Bash, Azure CLI, or Linux automation alternatives. The workflow and tooling described (e.g., PowerShell runbooks, PowerShell jobs, Windows environment variables like $env:Temp) are specific to Windows environments, and there are no Linux or cross-platform examples or guidance. The structure and order of the documentation also present Windows/PowerShell approaches first and exclusively.
Recommendations
- Provide equivalent examples using Azure CLI and/or Bash scripts for Linux users.
- Mention and link to Azure Automation support for Python runbooks, which are cross-platform.
- Include guidance for running automation scripts from Linux environments (e.g., using Azure CLI in a cron job).
- Clarify that Azure Automation supports multiple runbook types and provide a comparison or decision guide.
- Avoid using Windows-specific environment variables (like $env:Temp) in examples, or provide Linux equivalents.
- Add a section or callout for Linux/macOS users, summarizing their options for automating VM startup order.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/management/request-limits-and-throttling.md
...ce-manager/management/request-limits-and-throttling.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides detailed PowerShell examples and references, with C# and Azure CLI also mentioned. However, there are no explicit Linux shell (bash/curl) examples, and PowerShell is presented before Azure CLI. This order and the lack of Linux-native command-line examples may disadvantage Linux users or those preferring bash scripting.
Recommendations
- Add bash/curl examples for retrieving HTTP headers, especially for the 'x-ms-ratelimit-remaining-*' headers, to show Linux users how to access this information.
- Present Azure CLI examples before or alongside PowerShell examples, as Azure CLI is cross-platform and more commonly used on Linux.
- Explicitly mention that Azure CLI commands work identically on Linux, macOS, and Windows.
- Where C# is shown, consider adding Python or other cross-platform language examples.
- Review linked resources (such as the referenced PowerShell script) for similar bias and provide Linux alternatives if needed.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/devtest-labs/troubleshoot-vm-deployment-failures.md
...es/devtest-labs/troubleshoot-vm-deployment-failures.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell specifically as the method for deploying VMs with ARM templates, without mentioning or providing examples for Linux/Unix-based alternatives such as Azure CLI, Bash, or Cloud Shell. No Linux-specific tools or command-line examples are provided, and the only scripting example is PowerShell-focused.
Recommendations
- Include equivalent Azure CLI (az) commands and examples alongside PowerShell instructions for deploying VMs with ARM templates.
- Explicitly mention that deployment can be performed from Linux, macOS, or Windows, and provide cross-platform guidance.
- Add Bash or Cloud Shell examples where scripting is discussed, ensuring parity for Linux users.
- Where PowerShell is referenced, provide a parallel section or note for Linux/CLI users.
- Review all troubleshooting steps to ensure they are not written with an implicit assumption of a Windows environment.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/templates/deploy-to-azure-button.md
...e-resource-manager/templates/deploy-to-azure-button.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides a PowerShell example for URL encoding but does not offer equivalent Linux or cross-platform command-line examples (such as Bash or Python). This may disadvantage users on Linux or macOS, as PowerShell is primarily associated with Windows environments. No Linux-native tools or commands are mentioned for this common task.
Recommendations
- Add a Bash example for URL encoding, such as using 'python3 -c "import urllib.parse, sys; print(urllib.parse.quote(sys.argv[1]))" "$url"' or 'jq -sRr @uri <<< "$url"'.
- Mention cross-platform or platform-agnostic tools (e.g., Python, Node.js) for URL encoding.
- Explicitly state that the PowerShell example is one of several possible methods, and provide parity for Linux/macOS users.
- Consider including a table or section listing equivalent commands for Windows (PowerShell), Linux (Bash), and macOS.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/management/tls-support.md
...icles/azure-resource-manager/management/tls-support.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page demonstrates a Windows-centric bias by mentioning Windows versions and tools first, providing .NET and PowerShell-specific guidance, and omitting equivalent Linux or cross-platform examples. Tools and troubleshooting steps are focused on Windows (e.g., Fiddler, WinHTTP, PowerShell), and there is no discussion of how to check or configure TLS versions on Linux or macOS clients.
Recommendations
- Add explicit guidance for Linux and macOS users, such as how to check and configure TLS versions using OpenSSL, curl, or system configuration files.
- Include examples for popular Linux distributions (e.g., Ubuntu, CentOS) and macOS, showing how to verify and enforce TLS 1.2 usage.
- Mention cross-platform tools (e.g., OpenSSL, curl, nmap) alongside or before Windows-specific tools like Fiddler.
- Provide troubleshooting steps and links for non-Windows environments, such as updating OpenSSL or configuring Java applications.
- Balance .NET/PowerShell examples with Python, Java, or other cross-platform language examples.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/devtest-labs/tutorial-use-custom-lab.md
...main//articles/devtest-labs/tutorial-use-custom-lab.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation prioritizes Windows connection methods by listing 'Connect via RDP' for Windows VMs before mentioning Linux connection options. It references Windows-specific tools (RDP) and patterns before Linux equivalents (SSH/Azure CLI). There are no explicit Linux command-line or SSH examples, and the structure implicitly centers Windows workflows.
Recommendations
- Present Linux and Windows connection methods in parallel or in separate, equally detailed sections, rather than listing Windows first.
- Include explicit Linux SSH command-line examples alongside RDP instructions.
- Avoid referring to Windows tools (like RDP) before Linux tools (like SSH); instead, introduce both together or alternate their order.
- Add screenshots and step-by-step instructions for Linux users, matching the detail given for Windows.
- Ensure parity in troubleshooting and prerequisites for both OS types.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/templates/copy-properties.md
...es/azure-resource-manager/templates/copy-properties.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by only providing a Windows VM deployment example (with a link specifically to a 'vm-windows-copy-datadisks' template), mentioning Azure PowerShell before Azure CLI in version requirements, and referencing deployment with Azure PowerShell in the 'Next steps' section. There are no Linux-specific examples or links, and Linux deployment tools or scenarios are not highlighted.
Recommendations
- Add a Linux VM deployment example using property iteration, and link to a Linux-focused quickstart template (e.g., 'vm-linux-copy-datadisks').
- When listing deployment tools (Azure PowerShell, Azure CLI, REST API), alternate or balance the order, or mention Azure CLI first to avoid Windows-first perception.
- In the 'Next steps' section, provide links to both PowerShell and CLI deployment guides, or a unified cross-platform deployment guide.
- Explicitly mention that the property iteration technique applies equally to Linux and Windows resources, and provide at least one Linux resource scenario.
- Where possible, use neutral or cross-platform language and examples, and avoid implying Windows is the default or primary use case.