Azure Resource Manager
504
Total Pages
312
Linux-Friendly Pages
192
Pages with Bias
38.1%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
1281 issues found
Showing 76-100 of 1281 flagged pages
Azure Resource Manager
Relocate Azure HDInsight clusters to another region
...-manager/management/relocation/relocation-hdinsight.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by consistently listing Azure PowerShell as a primary method for exporting and deploying templates, often before or alongside Azure CLI. There are no explicit Linux shell (bash) examples, nor references to Linux-specific tools or workflows. The use of terms like 'Azure PowerShell' and the absence of Linux command-line examples or parity in deployment instructions suggest a preference for Windows-centric tools and patterns.
Recommendations
- Add explicit bash/Linux shell examples for exporting and deploying ARM/Bicep templates, using Azure CLI in a Linux context.
- Clarify that Azure CLI is cross-platform and provide step-by-step instructions for Linux users, including installation and usage in bash.
- Reorder examples so that Azure CLI (which is platform-neutral) appears before Azure PowerShell, or present both equally.
- Mention that Azure Cloud Shell supports both bash and PowerShell, and provide examples for both.
- Include notes or sections on Linux-specific considerations, such as SSH key management, file permissions, and environment setup.
- Avoid implying that PowerShell is the default or preferred method unless there is a technical reason.
Create Pull Request
Azure Resource Manager
Relocate Azure Storage Account to another region
...er/management/relocation/relocation-storage-account.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows and PowerShell environments. All command-line examples are provided exclusively using Azure PowerShell, with no mention of Azure CLI or Bash equivalents, which are more common on Linux and macOS. The structure consistently presents PowerShell instructions before any alternative, and there are no Linux-specific instructions or examples. This may hinder accessibility for users working on Linux or macOS platforms.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell commands, including template export, modification, deployment, and resource deletion.
- Include Bash shell instructions where appropriate, especially for AzCopy usage and scripting.
- Explicitly mention cross-platform compatibility for tools like AzCopy and provide installation and usage notes for Linux/macOS.
- Reorganize sections so that PowerShell and CLI/Bash examples are presented with equal prominence, possibly using tabs for 'Azure PowerShell', 'Azure CLI', and 'Portal'.
- Reference Linux/macOS documentation for any tools or procedures that differ from Windows.
Azure Resource Manager
Relocate Azure NSG to another region
...anagement/relocation/relocation-virtual-network-nsg.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation provides detailed instructions for relocating an Azure NSG using the Azure Portal and PowerShell, both of which are Windows-centric tools. There are no examples or instructions for Linux-native tools such as Azure CLI, Bash, or cross-platform scripting. PowerShell is presented as the only command-line option, and Windows tools (e.g., Notepad) are referenced for editing files. This creates a bias towards Windows users and leaves Linux users without direct guidance.
Recommendations
- Add equivalent step-by-step instructions using Azure CLI (az) commands, which are cross-platform and widely used on Linux and macOS.
- Provide Bash script examples for exporting, modifying, and redeploying NSGs using Azure CLI.
- Replace or supplement references to Notepad with cross-platform editors (e.g., vim, nano, code) or generic instructions for editing JSON files.
- Ensure all command-line steps are available in both PowerShell and Azure CLI tabs, with parity in detail and explanation.
- Mention that Azure CLI can be installed and used on Windows, Linux, and macOS, and provide installation links.
Azure Resource Manager
Understand how Azure Resource Manager throttles requests
...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 page demonstrates a Windows bias in its examples and guidance. PowerShell is featured prominently with multiple code samples and debugging instructions, and it is presented before Azure CLI. There are no Linux-specific shell (e.g., Bash, curl) examples for retrieving headers, nor is there mention of Linux tools or patterns for interacting with Azure Resource Manager APIs. The focus on PowerShell and lack of Linux-native examples may disadvantage users on Linux or macOS platforms.
Recommendations
- Add Linux/Bash/curl examples for retrieving rate limit headers from Azure Resource Manager REST API responses.
- Include examples using common Linux tools (e.g., wget, curl, jq) to demonstrate how to parse response headers.
- Ensure Azure CLI examples are presented before or alongside PowerShell, and clarify that Azure CLI is cross-platform.
- Explicitly mention that all shown operations can be performed on Linux, macOS, and Windows, and provide platform-agnostic instructions where possible.
- Consider adding a section or note about using REST APIs directly from any platform, with sample requests and header parsing.
Azure Resource Manager
Relocate Azure Key Vault to another region
...-manager/management/relocation/relocation-key-vault.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 detailed PowerShell examples for key operations (template export, modification, deployment) without equivalent Azure CLI or Bash examples. PowerShell is a Windows-centric tool, and its use is prioritized over cross-platform alternatives. The Azure CLI is mentioned only in passing and not used in any step-by-step instructions. There are no Linux-specific instructions or examples, and the documentation assumes familiarity with PowerShell commands and patterns.
Recommendations
- Add step-by-step Azure CLI examples for all operations currently covered by PowerShell, including template export, modification, and deployment.
- Include Bash script examples for common tasks to demonstrate Linux parity.
- When listing tools or methods (e.g., Azure portal, CLI, PowerShell), present Azure CLI before or alongside PowerShell to avoid 'windows_first' ordering.
- Explicitly mention that all procedures can be performed on Linux, macOS, and Windows, and provide cross-platform guidance where relevant.
- Ensure troubleshooting tips and references include CLI-based solutions, not just PowerShell.
- Consider adding a table or section comparing PowerShell and CLI commands for each major step.
Azure Resource Manager
Relocate Azure Virtual Network to another region
...er/management/relocation/relocation-virtual-network.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation provides detailed instructions for relocating an Azure Virtual Network using the Azure Portal and PowerShell, but omits examples for Linux-native tools or cross-platform CLI usage. PowerShell is featured as the sole scripting/automation method, and Windows-specific tools (e.g., Notepad) are referenced. There is no mention of Azure CLI, Bash, or other Linux-friendly approaches, and PowerShell is presented before any alternative automation options.
Recommendations
- Add Azure CLI examples for each step alongside PowerShell, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Replace or supplement references to Notepad with platform-neutral editors (e.g., 'edit with your preferred text editor').
- Explicitly mention that PowerShell Core is available on Linux/macOS, or provide Bash scripting alternatives.
- Ensure that automation and scripting sections do not assume a Windows environment; include instructions for Linux and macOS users.
- Consider reordering or parallelizing instructions so that Windows and Linux approaches are presented together, rather than Windows/PowerShell first.
Azure Resource Manager
Azure resource providers and types
...rce-manager/management/resource-providers-and-types.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Summary
The documentation page demonstrates a moderate Windows bias. The Azure portal (a GUI tool most commonly used on Windows) is presented first and in greatest detail, with multiple screenshots and step-by-step instructions. Azure PowerShell, a Windows-centric tool, is given a full section with detailed command examples before Azure CLI and Python. The CLI and Python examples are present and comprehensive, but the ordering and emphasis favor Windows-native tools and patterns. There is no mention of Linux-specific tools, shell patterns, or alternative workflows (e.g., Bash scripting, automation via Linux-native tools). The only explicit reference to 'Windows' is in the context of the 'Windows Azure Service Management API' in an informational note, reinforcing the Windows-centric framing.
Recommendations
- Add Linux-specific instructions or notes, such as using Bash scripts or automation via cron, where relevant.
- Reorder sections so that cross-platform tools (Azure CLI, Python SDK) appear before Windows-centric tools (Azure PowerShell).
- Include screenshots or examples of using the Azure portal on Linux/macOS browsers, or clarify that the portal is cross-platform.
- Mention that Azure CLI and Python SDK are fully supported on Linux and macOS, and provide installation links for those platforms.
- Consider adding a section for automation using Bash or other Linux-native tools, or link to such resources.
- Avoid referring to the 'Windows Azure Service Management API' without clarifying its legacy status and cross-platform alternatives.
Azure Resource Manager
Use tags to organize your Azure resources and management hierarchy
...les/azure-resource-manager/management/tag-resources.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page demonstrates a Windows bias by referencing Azure PowerShell and REST API as primary tools for tag operations, mentioning Azure PowerShell before Azure CLI in the 'Next steps' section, and highlighting PowerShell support for tag operations in the access control discussion. Linux equivalents (Azure CLI) are mentioned but are not given equal prominence or examples. There are no explicit Linux or Bash examples, and Windows-centric tools/patterns are referenced first.
Recommendations
- Present Azure CLI and PowerShell examples side-by-side throughout the documentation, especially in sections discussing tag operations and access.
- Mention Azure CLI before or alongside PowerShell in lists and recommendations to avoid implying a Windows-first workflow.
- Include explicit Linux/Bash usage examples for tag operations, demonstrating parity with PowerShell instructions.
- Clarify that both Azure CLI and PowerShell are cross-platform, and provide guidance for users on Linux and macOS.
- Review and update all tool references to ensure equal visibility and instruction for both Windows and Linux users.
Azure Resource Manager
Migrating to TLS 1.2 for Azure Resource Manager
...icles/azure-resource-manager/management/tls-support.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing Windows versions and tools first, providing examples and troubleshooting steps primarily for Windows environments (e.g., PowerShell, WinHTTP, .NET Framework, Visual Studio, Fiddler), and omitting equivalent guidance or examples for Linux or macOS clients. There are no Linux-specific instructions, tools, or troubleshooting steps mentioned.
Recommendations
- Add explicit guidance for Linux and macOS users, including how to verify and configure TLS 1.2 support on those platforms.
- Include examples for popular Linux tools (e.g., curl, openssl, wget) to check TLS versions.
- Mention how to update or configure TLS settings for common Linux frameworks and runtimes (e.g., Python, Java, Node.js).
- List Linux distributions and their default TLS support, similar to the Windows version notes.
- Provide troubleshooting steps and tools for Linux environments (e.g., using OpenSSL s_client, strace, or system logs).
- Balance the order of examples and recommendations so that Windows and Linux/macOS are treated equally.
Azure Resource Manager
CI/CD with Azure Pipelines and templates
...e-manager/templates/add-template-to-azure-pipelines.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell-based deployment examples, referencing Windows-specific tools and patterns (such as Azure PowerShell and AzureFileCopy tasks), and using Windows-based VM images in YAML samples. There is no mention of Bash, Linux-native scripting, or cross-platform alternatives, and Linux examples are missing even though Azure Pipelines supports Ubuntu and other Linux agents.
Recommendations
- Provide equivalent Bash or cross-platform script examples for ARM template deployment, using the Azure CLI.
- Include YAML samples that use 'ubuntu-latest' or other Linux agents for all deployment scenarios, not just PowerShell.
- Mention and demonstrate Linux-native tools (e.g., AzCopy via CLI, Azure CLI for deployments) alongside Windows tools.
- Clarify which tasks and scripts are cross-platform and which are Windows-specific, and recommend alternatives for Linux users.
- Add a section or callouts for Linux users, including troubleshooting tips and best practices for non-Windows environments.
Azure Resource Manager
Define multiple instances of a variable
...les/azure-resource-manager/templates/copy-variables.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias. In the 'Copy limits' section, Azure PowerShell is mentioned before Azure CLI, and the 'Next steps' section links only to PowerShell deployment instructions, omitting Linux-native or cross-platform CLI deployment guides. There are no explicit Linux or Bash examples, and the deployment tooling references prioritize Windows-centric tools.
Recommendations
- Add explicit examples and instructions for deploying ARM templates using Azure CLI, including Linux and macOS usage.
- In the 'Next steps' section, include links to both PowerShell and Azure CLI deployment guides to ensure parity.
- When listing supported tools or versions, alternate the order or mention Azure CLI first to avoid Windows-first perception.
- Consider including a note or section on cross-platform deployment options, highlighting Bash, CLI, and automation on Linux/macOS.
Azure Resource Manager
Tag support for Azure resources
...icles/azure-resource-manager/management/tag-support.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation page contains evidence of Windows bias. In the 'Microsoft.Compute' section, the note on generalizing a virtual machine lists the PowerShell command (Set-AzVm -Generalized) before the Azure CLI equivalent (az vm generalize). Additionally, the only command-line examples given for updating tags on certain resources (e.g., IP groups) use Azure CLI, but there is a tendency to mention PowerShell or Windows-centric tools first. The documentation also references Windows-specific tools and resource types (e.g., AzureStackHCI, Windows365, DevelopmentWindows365) without equivalent Linux-focused examples or resources. There are no explicit Linux shell (bash) examples, and Windows-centric terminology and tools are mentioned more frequently and/or first.
Recommendations
- Ensure command-line examples are provided for both PowerShell and bash/Azure CLI, and alternate which is listed first.
- Include Linux-focused resource types and examples where relevant, or clarify parity.
- Avoid mentioning Windows tools or patterns exclusively; when referencing a Windows tool, provide the Linux equivalent in parallel.
- Audit documentation for resource types and features that may be Windows-centric and add notes or examples for Linux users.
- Where possible, use cross-platform terminology and avoid assuming a Windows environment.
Azure Resource Manager
Create & deploy Visual Studio resource group projects
...r/templates/create-visual-studio-deployment-project.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is heavily oriented toward Windows and Visual Studio users, with all examples and workflows based on Visual Studio (a Windows-centric IDE) and PowerShell scripts. There are no examples or guidance for Linux or cross-platform users, such as those using VS Code, Azure CLI, or Bash. The only deployment scripts shown are PowerShell-based, and the workflow assumes the use of Windows file paths and tooling. Linux alternatives, such as Bash scripts or Azure CLI commands, are not mentioned or provided.
Recommendations
- Add equivalent instructions for Linux users, such as using VS Code or the Azure CLI to create and deploy resource group templates.
- Provide Bash or shell script examples for deployment, or show how to use Azure CLI (az deployment group create, etc.) instead of only PowerShell scripts.
- Mention and link to cross-platform tools and workflows earlier in the documentation, not just Visual Studio and PowerShell.
- Clarify which steps are Windows-specific and provide alternative steps for macOS/Linux environments.
- Include a section or callout for users who do not use Visual Studio, explaining how to achieve the same results with cross-platform tools.
Azure Resource Manager
Azure deployment templates with Azure CLI – Azure Resource Manager | Microsoft Docs
...rticles/azure-resource-manager/templates/deploy-cli.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. While most examples use Azure CLI (which is cross-platform), there are several places where Windows-specific shells (CMD, PowerShell) are mentioned before or instead of Linux equivalents. Formatting for parameters and variables is explained for Windows shells, but Linux/Bash examples are less detailed or appear after Windows instructions. There are no explicit PowerShell script blocks, but Windows command-line patterns and escaping are described in detail, while Linux/Bash usage is less emphasized.
Recommendations
- Ensure that Bash/Linux examples are provided alongside Windows CMD/PowerShell examples, especially when discussing parameter formatting and variable assignment.
- When describing shell-specific behaviors (such as escaping quotes or passing arrays), present Linux/Bash instructions first or equally with Windows instructions.
- Add explicit Bash and Linux shell examples for all command-line snippets, including variable assignment and parameter passing.
- Clarify which instructions apply to which platforms, and avoid assuming Windows as the default environment.
- Where possible, use platform-neutral syntax and highlight cross-platform compatibility.
Azure Resource Manager
Deploy to Azure button
...e-resource-manager/templates/deploy-to-azure-button.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows First
Summary
The documentation provides a PowerShell-only example for URL encoding, omitting equivalent Linux/macOS command-line examples (e.g., Bash, Python, curl). This prioritizes Windows tooling and patterns, potentially making it less accessible for users on Linux or macOS. No Linux-specific tools or cross-platform alternatives are mentioned, and the PowerShell example appears before any suggestion of online tools.
Recommendations
- Add Linux/macOS command-line examples for URL encoding, such as using Python, Bash, or curl.
- Explicitly mention that PowerShell is available cross-platform, or provide instructions for installing PowerShell on Linux/macOS if retaining the example.
- Present cross-platform solutions first or alongside Windows-specific ones to ensure parity.
- Reference online tools and platform-agnostic methods before platform-specific command-line examples.
Azure Resource Manager
Azure Resource Manager deployment modes
...s/azure-resource-manager/templates/deployment-modes.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is presented first and in detail for deployment mode examples, with a Windows-style file path (c:\MyTemplates\storage.json) used in the PowerShell example. The CLI example follows, but there is no mention of Linux-specific considerations, such as file paths or shell environments. References to deployment with PowerShell are more prominent, and the 'Next steps' section links to PowerShell-specific deployment guidance before more general resources.
Recommendations
- Provide Linux/Unix shell examples alongside or before PowerShell, including file paths using forward slashes (e.g., ./storage.json).
- Clarify that Azure CLI works cross-platform and show examples in Bash or other shells.
- Balance references to PowerShell and CLI in 'Next steps', possibly linking to CLI documentation first or equally.
- Avoid Windows-specific file paths in generic examples; use neutral or platform-agnostic paths.
- Explicitly state that both PowerShell and CLI are available on Windows, Linux, and macOS, and mention any platform-specific considerations.
Azure Resource Manager
Use deployment scripts in Azure Resource Manager templates
...source-manager/templates/deployment-script-template.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell (a Windows-centric tool) is consistently presented first in examples, sample templates, and usage scenarios. Most code samples and walkthroughs use PowerShell, with only a few CLI/bash examples provided later. Windows-specific tools and APIs (e.g., CommandLineToArgvW) are referenced without Linux equivalents. There is a lack of parity in example depth and troubleshooting guidance for Linux/bash users, and some instructions (such as using the Cloud Shell 'Try it' button) default to PowerShell. The documentation does not provide balanced, parallel examples for Linux/bash users, and troubleshooting/development sections are PowerShell-centric.
Recommendations
- Alternate the order of PowerShell and Azure CLI/bash examples throughout the documentation, or present both side-by-side.
- Provide equally detailed sample templates and walkthroughs for Azure CLI/bash, including inline and external script usage.
- Include troubleshooting and development environment guidance specifically for Linux/bash users, not just PowerShell.
- Reference Linux-native tools and APIs where appropriate, or provide Linux equivalents when mentioning Windows-specific tools (e.g., mention how argument parsing works in bash).
- Ensure that all instructions (such as 'Try it' in Cloud Shell) offer both PowerShell and Bash options, with clear guidance for each.
- Expand the 'Work with outputs' and 'Monitor and troubleshoot' sections to include bash/CLI-specific details and examples.
- Review all sample links and ensure there are as many CLI/bash samples as PowerShell samples, with similar complexity.
Azure Resource Manager
Template deployment what-if
...les/azure-resource-manager/templates/deploy-what-if.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page exhibits a moderate Windows bias. PowerShell (a Windows-centric tool) is featured heavily throughout the page, with examples and output shown in PowerShell syntax and formatting. In several sections, PowerShell commands and output are presented before Azure CLI equivalents, and the output samples use PowerShell formatting. The installation instructions and command references give prominence to PowerShell modules and patterns. While Azure CLI examples are provided and REST API is mentioned, the overall structure and examples lean toward Windows/PowerShell usage, with little attention to Linux-specific nuances or shell environments.
Recommendations
- Ensure that CLI examples are presented before or alongside PowerShell examples, especially in introductory and output sections.
- Provide output samples in both PowerShell and Azure CLI formats, and clarify differences in output formatting between Windows and Linux shells.
- Include notes or sections on running Azure CLI commands in Linux/macOS environments, including shell-specific tips (e.g., bash/zsh syntax, color handling, file redirection).
- Mention cross-platform compatibility explicitly when discussing installation and usage of Azure CLI and PowerShell.
- Add troubleshooting or configuration guidance for Linux users, such as handling color output, environment variables, and file paths.
- Consider including SDK usage examples in Linux-friendly languages (e.g., Python) before or alongside .NET/PowerShell.
Azure Resource Manager
Configure development environment for deployment scripts in templates | Microsoft Docs
.../templates/deployment-script-template-configure-dev.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits a Windows bias by providing PowerShell-heavy examples, using Windows-centric tools and patterns (e.g., PowerShell cmdlets, Windows drive letter notation), and presenting PowerShell/Windows workflows before Linux equivalents. Upload and deployment steps rely on PowerShell scripts, with no Bash/Azure CLI alternatives shown for Linux users. Docker volume mapping examples use Windows paths exclusively, omitting Linux/macOS syntax.
Recommendations
- Provide Bash/Azure CLI examples for uploading deployment scripts to Azure Storage, alongside PowerShell.
- Include Docker volume mapping examples using Linux/macOS path syntax (e.g., /home/user/docker:/data), not just Windows drive letters.
- Present Linux/Azure CLI workflows in parallel with PowerShell, or alternate the order to avoid Windows-first presentation.
- Reference cross-platform tools and commands where possible, and clarify OS-specific steps.
- Add notes or sections for Linux/macOS users, especially for file system operations and command-line usage.
Azure Resource Manager
Tutorial - Deploy a linked template
...nager/templates/deployment-tutorial-linked-template.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page demonstrates a bias towards Windows by providing detailed Azure PowerShell scripts for key steps (storage upload, deployment), referencing Windows-centric tools and patterns (PowerShell, Cloud Shell with PowerShell), and presenting PowerShell instructions before Azure CLI equivalents. There is no mention of Linux-specific shell scripting or alternative Linux-native tools for uploading templates to storage. The Azure CLI section is present, but less emphasized and appears after PowerShell. The clean-up instructions reference the Azure portal, which is platform-neutral, but overall, the workflow is oriented towards Windows users.
Recommendations
- Provide Bash shell script examples for uploading templates to Azure Storage, using azcopy or Azure CLI, to complement the PowerShell example.
- Present Azure CLI instructions before or alongside PowerShell to avoid Windows-first ordering.
- Explicitly mention that all steps can be performed on Linux/macOS using Azure CLI and Bash, and provide guidance for Linux users.
- Include troubleshooting notes for common Linux/macOS issues (e.g., file paths, permissions, date command differences) in relevant sections.
- Reference Linux-native tools (such as azcopy) for template upload and management, and provide links to their documentation.
Azure Resource Manager
Create parameter file
...es/azure-resource-manager/templates/parameter-files.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 deploying templates with parameter files, but the PowerShell example uses Windows-style file paths (C:\MyTemplates\...), and the PowerShell section is given equal prominence to CLI. There is also a tip referencing Visual Studio, a Windows-centric tool, and a note about PowerShell-specific parameter name conflicts. No Linux-specific examples (e.g., Bash, Linux file paths) or editor/tooling recommendations are given, and Windows patterns (such as file paths and Visual Studio usage) are mentioned without Linux equivalents.
Recommendations
- Add Linux/Bash examples for deploying with parameter files, using Linux-style file paths (e.g., /home/user/templates/storage.parameters.json).
- Clarify that Azure CLI works cross-platform and show examples with Linux file paths.
- Mention cross-platform editors (e.g., VS Code) alongside Visual Studio, or provide Linux alternatives.
- Add a note about PowerShell Core availability on Linux, or clarify any differences in usage.
- Balance the order of examples so that CLI (cross-platform) is presented before PowerShell, or explicitly state platform applicability.
- If discussing file paths, show both Windows and Linux formats.
Azure Resource Manager
Tutorial - Deploy a local Azure Resource Manager template
...anager/templates/deployment-tutorial-local-template.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation shows mild Windows bias: Windows-specific installation instructions for Azure CLI are listed before Linux/macOS, Azure PowerShell (a Windows-centric tool) is presented as an equal option to Azure CLI, and PowerShell examples are given first in all code tabs. There is no explicit Linux example for shell scripting (e.g., Bash vs. PowerShell), and Visual Studio Code is suggested as the editor, which, while cross-platform, is often associated with Windows. The cleanup instructions use the Azure portal, which is platform-neutral.
Recommendations
- List Azure CLI installation instructions for Linux/macOS before Windows, or group them together to avoid Windows-first ordering.
- Present Azure CLI (which is cross-platform and preferred for Linux) examples before PowerShell, or alternate the order in code tabs.
- Explicitly state that CLI examples are Bash-compatible and provide any necessary notes for Linux/macOS users (e.g., file path conventions, shell differences).
- Mention alternative editors for Linux (e.g., Vim, nano) alongside Visual Studio Code.
- Add a brief note on using the Azure CLI in native Linux environments, and clarify that PowerShell is available cross-platform but is more commonly used on Windows.
Azure Resource Manager
Create and deploy template spec
...-manager/templates/quickstart-create-template-specs.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation exhibits several signs of Windows bias. File paths are consistently given in Windows format (e.g., C:\Templates\...), with no mention of Linux/macOS equivalents. All command-line examples use Windows-style paths, and there are no examples or notes for Linux/macOS users regarding file locations or path syntax. PowerShell is featured prominently, sometimes before Azure CLI, and references to Azure PowerShell are made without equivalent coverage for Bash or other shells. The 'Grant access' section links only to a PowerShell tutorial. There is no mention of Linux-specific tools, nor are there any screenshots or instructions tailored to non-Windows platforms.
Recommendations
- Provide Linux/macOS path examples alongside Windows paths (e.g., ~/Templates/createStorageV1.json).
- Add notes or callouts for Linux/macOS users regarding file system differences and path syntax.
- Ensure Azure CLI examples use cross-platform path syntax or clarify usage on different OSes.
- Include links to equivalent tutorials for Bash or Azure CLI where PowerShell is referenced.
- Balance the order of examples so that Azure CLI and PowerShell are presented equally, or alternate which comes first.
- Add screenshots or instructions for Linux/macOS environments where relevant.
- Explicitly state that the instructions apply to all supported platforms and highlight any platform-specific considerations.
Azure Resource Manager
Develop ARM templates for cloud consistency
...source-manager/templates/template-cloud-consistency.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a Windows bias in several ways: PowerShell is frequently used as the primary or sole scripting example for verifying template functions, resource providers, VM images, VM sizes, and VM extensions. Windows-centric tools and patterns (such as PowerShell DSC and Windows VM images) are referenced and shown in code samples, while Linux equivalents are either omitted or mentioned only in passing. Examples and default values often reference Windows-specific resources (e.g., 'dotnet-core-music-windows', 'MicrosoftWindowsServer'), and there is a lack of Linux-focused examples for VM images, extensions, and scripts.
Recommendations
- Provide Linux-focused examples alongside Windows ones, such as using Bash scripts, Linux VM images, and Linux-specific VM extensions.
- Include Azure CLI examples before or alongside PowerShell examples, as Azure CLI is cross-platform and more commonly used on Linux/macOS.
- Use neutral or Linux-inclusive default values in code samples (e.g., reference both Windows and Linux script repositories, VM images, and artifacts).
- Mention and demonstrate Linux-compatible tools and extensions (e.g., Custom Script Extension for Linux, OMS Agent for Linux) where relevant.
- Balance references to Windows-specific technologies (like PowerShell DSC) with Linux equivalents (such as cloud-init or Ansible).
- Ensure documentation language and examples do not assume a Windows environment by default.
Azure Resource Manager
Deploy a template spec as a linked template
...ger/templates/template-specs-deploy-linked-template.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 consistently using Windows-style file paths (e.g., c:\Templates\deployTS\azuredeploy.json), presenting PowerShell examples before Azure CLI, and referencing Windows-specific issues (e.g., variable assignment in Windows PowerShell). There are no explicit Linux or macOS examples, and no mention of Linux file path conventions or shell environments.
Recommendations
- Provide Linux/macOS equivalents for file paths (e.g., /home/user/Templates/deployTS/azuredeploy.json) alongside Windows paths.
- Alternate the order of PowerShell and CLI examples or present them side-by-side to avoid privileging Windows tools.
- Include notes or examples for running Azure CLI commands in Bash or other Linux shells.
- Address any platform-specific issues for Linux/macOS users, not just Windows PowerShell.
- Explicitly state that the instructions apply to all platforms and highlight any differences where relevant.