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 526-550 of 1281 flagged pages
Azure Resource Manager
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 page provides both Azure CLI and Azure PowerShell examples for obtaining access tokens and making REST API calls. However, PowerShell examples are given equal prominence to CLI, and there are multiple references to PowerShell-specific workflows and tools (e.g., 'Invoke-WebRequest', links to PowerShell deployment guides). There is a reference to Visual Studio Code for template authoring, which is cross-platform, but no mention of Linux-specific tools or shell scripting patterns. The documentation does not provide Linux shell alternatives (e.g., bash, wget) or explicitly address Linux environments, and PowerShell (a Windows-centric tool, though now cross-platform) is presented as a primary option.
Recommendations
- Add explicit bash/sh examples for REST API calls, using native Linux tools like 'curl' and 'wget', with environment variable handling shown in a Linux style.
- Clarify that Azure CLI is cross-platform and highlight its use in Linux environments.
- Include references or links to Linux-specific guides for deploying and managing Azure resources.
- Avoid presenting PowerShell as the default or primary option; instead, alternate or prioritize CLI/bash examples when possible.
- Mention that Visual Studio Code is cross-platform, and suggest other Linux-friendly editors or tools for template authoring.
Create Pull Request
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/deployment-models.md
...azure-resource-manager/management/deployment-models.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows by providing only PowerShell command examples (with no Azure CLI, Bash, or Linux-native equivalents), referencing Windows-specific remote management (Remote Desktop and remote PowerShell) before mentioning SSH for Linux, and linking to Windows VM architecture before any Linux VM equivalent. Linux tools and workflows are underrepresented or omitted.
Recommendations
- Provide Azure CLI and Bash examples alongside PowerShell commands for all resource management tasks.
- When discussing remote management, mention SSH for Linux VMs before or alongside RDP/PowerShell for Windows VMs.
- Include links to both Windows and Linux VM reference architectures, or use a neutral example.
- Ensure migration and deployment instructions reference both PowerShell and CLI methods equally, and provide parity in documentation for Linux and Windows scenarios.
- Add explicit Linux-focused examples and scenarios, especially where differences in deployment or management exist.
Azure Resource Manager
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
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by presenting Azure PowerShell examples and references alongside Azure CLI, but does not provide explicit Linux shell (bash) examples or guidance. PowerShell is highlighted as a primary automation tool, and some CLI examples use syntax that is ambiguous between bash and PowerShell, but do not clarify Linux-specific usage or differences. There is no mention of Linux-specific tools, nor are Linux/Bash examples prioritized or explained separately from PowerShell. The documentation assumes familiarity with PowerShell and Windows-centric workflows, potentially leaving Linux users without clear guidance.
Recommendations
- Clearly distinguish Azure CLI examples for Bash (Linux/macOS) and PowerShell (Windows), providing separate code blocks and explanations for each.
- Add explicit Bash shell examples for Azure CLI commands, including variable assignment and command chaining, to ensure Linux users have clear, tested instructions.
- Include notes or sections on Linux-specific considerations, such as environment setup, authentication, and file path differences.
- Avoid presenting PowerShell examples before or in preference to Bash/Linux equivalents; alternate or parallelize examples for both platforms.
- Reference Linux-native tools or workflows where relevant, and clarify any differences in command syntax or behavior between platforms.
Azure Resource Manager
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 demonstrates Windows bias by listing Azure PowerShell before Azure CLI when describing move operations, and by not providing explicit Linux-specific examples or guidance. The mention of Azure PowerShell (a Windows-centric tool) is prioritized, while Azure CLI (cross-platform) is listed but not elaborated upon. No Linux shell or command-line examples are given, and there is no mention of Linux-specific considerations.
Recommendations
- Provide explicit Linux shell (bash) examples using Azure CLI for moving resources.
- List Azure CLI before Azure PowerShell when describing cross-platform operations.
- Clarify that Azure CLI commands work on Linux, macOS, and Windows.
- Include notes or sections for Linux users, addressing any platform-specific considerations.
- Avoid implying PowerShell is the primary or default tool for resource management.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/manage-private-link-access-commands.md
...ager/management/manage-private-link-access-commands.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides examples for Azure CLI, PowerShell, and REST API. PowerShell, a Windows-centric tool, is given equal prominence to Azure CLI, and is featured in every example. There are no Linux shell (bash) or scripting examples, and no mention of Linux-specific tools or patterns. The login instructions reference PowerShell's Connect-AzAccount, which is Windows-specific, and PowerShell examples are always present, sometimes before REST. There is no explicit Linux bias or parity.
Recommendations
- Add bash shell examples for each operation, showing how to use Azure CLI in a Linux environment.
- Clarify that Azure CLI works cross-platform and provide Linux-specific login instructions (e.g., az login in bash).
- Consider including scripting examples using bash or other Linux-native tools where appropriate.
- Reorder examples so that Azure CLI (cross-platform) is always presented before PowerShell (Windows-centric).
- Explicitly mention platform compatibility for each tool, highlighting Azure CLI's Linux support and PowerShell's Windows focus.
Azure Resource Manager
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 method alongside CLI, and is referenced in links and instructions. PowerShell is a Windows-centric tool, and its inclusion as a main example (rather than, for instance, Bash or shell scripts) reflects a Windows bias. There are no Linux-specific shell examples, and the documentation does not mention Linux-native tools or patterns. The order of examples sometimes places PowerShell before REST, and links to PowerShell-based workflows are prominent.
Recommendations
- Add explicit Bash/shell script examples for Linux users, especially for REST calls (e.g., using curl or wget).
- Clarify that Azure CLI is cross-platform and highlight its use on Linux and macOS.
- Include instructions or links for installing and using Azure CLI on Linux.
- Avoid presenting PowerShell as a default or primary method; balance with Linux-native approaches.
- Add notes or sections for Linux-specific considerations, such as authentication methods or environment setup.
- Where PowerShell is referenced, also provide equivalent Bash or shell commands.
Azure Resource Manager
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 page demonstrates a Windows bias by referencing Windows-specific environment variables (e.g., %HOME%\site), mentioning Kudu (which is more familiar to Windows users), and providing links to PowerShell-based guidance (e.g., 'Azure App Service App Cloning Using PowerShell') as the only explicit next step. References to Azure CLI are present but not emphasized or exemplified, and there are no Linux-specific instructions, examples, or considerations. The use of Windows-style paths and terminology (e.g., 'FTP credentials', '%HOME%\site') further reinforces the Windows-centric approach.
Recommendations
- Add explicit Linux examples and instructions, including bash/CLI commands and Linux environment variable syntax (e.g., $HOME/site).
- Provide parity in tooling references: offer both PowerShell and Azure CLI examples for all operations, and link to both in 'Next steps'.
- Clarify that Kudu and FTP are cross-platform, and provide guidance for Linux-based workflows (e.g., using SCP, SFTP, or rsync for file transfers).
- Avoid Windows-centric terminology and paths; use platform-neutral language or provide both Windows and Linux equivalents.
- Include troubleshooting or configuration notes for Linux-based App Service plans, such as file system permissions, case sensitivity, and deployment methods.
Azure Resource Manager
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
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. It references Windows-specific environment variables (e.g., %HOME%) before mentioning Linux equivalents, and refers to Azure PowerShell scripts alongside Azure CLI, but does not provide Linux-specific shell examples or guidance. There is a lack of explicit Linux command-line examples (such as Bash or shell scripts), and the documentation does not mention Linux-specific deployment tools or patterns. The mention of containers for Linux is brief and not accompanied by practical examples.
Recommendations
- Add explicit Linux shell (Bash) examples alongside PowerShell/CLI instructions for resource creation and deployment.
- Mention Linux environment variables and file paths (e.g., $HOME/site) alongside Windows ones.
- Provide guidance or links for Linux-specific deployment tools (such as az CLI usage in Bash, or using SSH/SCP for code transfer).
- Include examples of deploying to Linux-based Function Apps, such as using containers or mounting file shares, with step-by-step instructions.
- Ensure that references to PowerShell are balanced with references to Bash or other Linux-native scripting environments.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/move-limitations/virtual-machines-move-limitations.md
.../move-limitations/virtual-machines-move-limitations.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides both Azure CLI and PowerShell examples for all operations, but PowerShell (a Windows-centric tool) is consistently presented alongside CLI, and is sometimes referenced first for certain actions (e.g., accepting Marketplace terms). There is a notable emphasis on PowerShell usage, which may implicitly favor Windows users. There are no explicit Linux shell script examples (e.g., Bash), nor are Linux-specific tools or patterns mentioned. The documentation does not address platform-specific nuances, such as differences in scripting environments between Windows and Linux.
Recommendations
- Add explicit Bash script examples for Linux users, especially for multi-step operations.
- Clarify that Azure CLI is cross-platform and can be used natively on Linux, macOS, and Windows.
- Where PowerShell is referenced, note that PowerShell Core is available on Linux and macOS, or provide equivalent Bash commands.
- Avoid language that implies PowerShell is the default or preferred method; present CLI and PowerShell examples in parallel, or alternate which is shown first.
- Include notes or links for installing and using Azure CLI and PowerShell on Linux systems.
- Highlight any platform-specific considerations, such as environment variable syntax differences or file path formats.
Azure Resource Manager
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
Summary
The documentation page demonstrates a bias towards Windows and PowerShell environments. All command-line examples are provided exclusively using Azure PowerShell, with no mention of Azure CLI or Bash alternatives that are more common on Linux and macOS. The PowerShell examples are presented as the only scripting option, and there is no guidance for Linux users on how to perform equivalent steps. The structure and ordering of examples also prioritize PowerShell over cross-platform tools.
Recommendations
- Add equivalent Azure CLI (az) examples for all PowerShell commands, including template export, modification, and deployment.
- Include Bash shell script examples where appropriate, especially for steps involving file manipulation or scripting.
- Explicitly mention that AzCopy is cross-platform and provide example commands for both Windows (cmd/PowerShell) and Linux/macOS (Bash).
- Ensure that instructions for obtaining region codes and other metadata include Azure CLI commands (e.g., az account list-locations).
- Where possible, provide guidance for Linux/macOS users, including installation and usage notes for required tools.
- Reorder examples so that cross-platform or platform-neutral options (Azure CLI, AzCopy) are presented before or alongside PowerShell.
Azure Resource Manager
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 PowerShell as the only example for exporting and importing runbooks, referencing Azure PowerShell modules, and omitting equivalent instructions for Linux users (e.g., Azure CLI or REST API). Windows tools and patterns are mentioned first and exclusively, with no mention of Linux-native approaches or cross-platform alternatives.
Recommendations
- Add Azure CLI examples for exporting/importing runbooks and deploying templates.
- Include instructions for using REST API or Terraform for runbook migration.
- Explicitly mention cross-platform compatibility and provide guidance for Linux/macOS users.
- Balance references to Azure PowerShell with Azure CLI and other platform-neutral tools.
- Where scripts are referenced, clarify if they are PowerShell-specific and offer Bash or Python alternatives.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/relocate-evaluate.md
...azure-resource-manager/management/relocate-evaluate.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits Windows bias by referencing Windows-centric tools and patterns, such as PowerShell and Azure portal features, without providing equivalent Linux or cross-platform command-line examples. The only explicit example for moving public IP configuration links to a PowerShell-based guide, and all tool recommendations are Azure-specific with no mention of Linux CLI or automation alternatives. There are no Linux-specific instructions, examples, or parity in tooling guidance.
Recommendations
- Provide Linux CLI (az CLI) examples alongside or before PowerShell examples for operations such as moving public IP configurations.
- Mention cross-platform automation tools (e.g., Terraform, Ansible) and provide sample scripts for both Windows and Linux environments.
- Include guidance for performing discovery and migration tasks using Linux-native tools and shell scripting.
- Clarify that Azure portal and visualization tools are accessible from any OS, and highlight any OS-specific limitations or alternatives.
- Ensure links to documentation cover both Windows and Linux procedures, or explicitly state platform applicability.
Azure Resource Manager
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 page demonstrates a Windows bias by providing detailed PowerShell examples and referencing PowerShell-specific debugging options before mentioning Azure CLI. There are no Linux shell (bash) or cross-platform scripting examples, and the PowerShell examples are more comprehensive than the Azure CLI ones. No Linux-specific tools or patterns are discussed, and the guidance assumes familiarity with Windows-centric tooling.
Recommendations
- Add equivalent bash (curl, jq) examples for retrieving headers and rate limits, showing how to do this on Linux/macOS.
- Ensure Azure CLI examples are as detailed as PowerShell ones, including debugging and header extraction.
- Present cross-platform examples first, or in parallel, rather than leading with PowerShell.
- Explicitly mention that Azure CLI and REST API calls work on Linux, macOS, and Windows, and provide guidance for those environments.
- Reference Linux-native tools (e.g., wget, curl) for interacting with Azure APIs and extracting headers.
Azure Resource Manager
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 command examples (e.g., Get-AzContainerRegistryRepository, Import-AzContainerImage, Set-AzAksCluster) without equivalent Linux/bash or cross-platform alternatives. In several cases, PowerShell commands are mentioned before or instead of Azure CLI or bash scripts. There are missing Linux/bash examples for key operations, and the scripting patterns assume Windows/PowerShell environments, which may not be familiar or available to Linux users.
Recommendations
- Provide bash/Azure CLI equivalents for all PowerShell commands, especially for repository listing, image import, and AKS integration.
- Ensure that scripting examples use cross-platform tools (Azure CLI, bash) as the primary or at least equally prominent option.
- Explicitly mention both Windows and Linux workflows where relevant, and clarify which commands are platform-specific.
- Review and update documentation to avoid assuming PowerShell as the default scripting environment.
- Add notes or links to platform-specific setup guides for both Windows and Linux users.
Azure Resource Manager
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
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation provides detailed instructions for relocating an Azure NSG using the Azure Portal and PowerShell, with all command-line examples and automation steps exclusively using PowerShell. There are no examples or guidance for Linux users (e.g., Azure CLI, Bash), and the use of Windows-specific tools (like Notepad) is referenced. The PowerShell tab is presented as the sole automation alternative, suggesting a Windows-centric approach and omitting Linux-native workflows.
Recommendations
- Add equivalent Azure CLI (az) examples for all PowerShell commands, including authentication, resource export, template editing, deployment, and cleanup.
- Include instructions for editing JSON files using cross-platform editors (e.g., vim, nano, VS Code) instead of referencing Notepad.
- Explicitly mention that all steps can be performed on Linux, macOS, and Windows, and provide OS-agnostic guidance where possible.
- Reorganize sections so that Azure CLI and PowerShell are presented with equal prominence, or provide a 'Choose your environment' introduction.
- Where region/location codes are referenced, provide Azure CLI alternatives (e.g., az account list-locations) alongside PowerShell.
- Review and update any references to Windows-only tools or terminology to ensure parity for Linux/macOS users.
Azure Resource Manager
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 bias by listing Windows versions and tools first, providing examples and guidance primarily for Windows environments (e.g., .NET Framework, Visual Studio, PowerShell), and omitting equivalent Linux-specific instructions or examples. Tools mentioned (Fiddler, WinHTTP, PowerShell) are Windows-centric, and there is no mention of how to check or configure TLS versions on Linux clients or using Linux-native tools.
Recommendations
- Add Linux-specific guidance for verifying and configuring TLS 1.2 support (e.g., using OpenSSL, curl, wget, or system configuration files).
- Include examples for popular Linux distributions (Ubuntu, CentOS, etc.) showing how to check TLS versions and update libraries.
- Mention Linux equivalents for tools like Fiddler (e.g., Wireshark, ssldump) and provide links or instructions.
- Provide parity in .NET examples by including instructions for .NET Core/.NET 5+ on Linux.
- List Linux and macOS operating systems alongside Windows when discussing default TLS support.
- Add troubleshooting steps for TLS 1.2 compatibility issues on Linux platforms.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/resource-providers-and-types.md
...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. It references 'Windows Azure Service Management API' in the registration section, and the Azure PowerShell examples (a Windows-centric tool) are presented before Azure CLI and Python. The portal instructions are also Windows-oriented, as the Azure portal is most commonly accessed from Windows environments and the screenshots do not mention Linux or cross-platform specifics. There are no explicit Linux shell (bash) examples, nor is there mention of Linux-specific tools or patterns. However, Azure CLI and Python examples are included, which are cross-platform.
Recommendations
- Add explicit bash/shell examples for resource provider management using Azure CLI, demonstrating usage in Linux environments.
- Clarify that Azure CLI and Python examples work equally well on Linux, macOS, and Windows.
- Avoid referring to 'Windows Azure Service Management API' unless necessary; if referenced, explain its cross-platform relevance or alternatives.
- Ensure screenshots and portal instructions do not imply Windows-only usage (e.g., avoid Windows-specific UI elements or terminology).
- Consider listing Azure CLI examples before PowerShell, as CLI is cross-platform and more common in Linux environments.
- Mention Linux-native tools (such as curl for REST API calls) where appropriate.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/tag-resources.md
...les/azure-resource-manager/management/tag-resources.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 Azure PowerShell as a primary tool for tag operations and access, mentioning it before cross-platform alternatives like Azure CLI. There are no explicit Linux or Bash examples, and PowerShell is highlighted as supporting all tag operations, while Azure CLI is only referenced in limitations. The 'Next steps' section lists Azure PowerShell before Azure CLI, reinforcing a Windows-first pattern.
Recommendations
- Provide explicit examples using Azure CLI and Bash for tag operations, especially in sections discussing access and operations.
- Mention Azure CLI alongside Azure PowerShell wherever command-line operations are discussed, and clarify CLI parity.
- In the 'Required access' section, note that Azure CLI supports all tag operations and is available on Linux, macOS, and Windows.
- In the 'Next steps' section, list Azure CLI before Azure PowerShell or present them together to avoid ordering bias.
- Add a note or table comparing PowerShell and CLI capabilities for tagging, highlighting cross-platform support.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/key-vault-parameter.md
...zure-resource-manager/templates/key-vault-parameter.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples are provided alongside Azure CLI, but PowerShell is a Windows-centric tool. References to Windows scenarios (such as installing a certificate on a Windows VM) appear before or instead of Linux equivalents. There is no mention of Linux-specific tools or shell patterns (e.g., Bash), and the examples and guidance assume familiarity with Windows tooling and conventions.
Recommendations
- Add explicit Bash examples for all CLI commands, showing syntax and usage in a Linux shell environment.
- Include references or links to Linux VM scenarios, such as installing certificates on Linux VMs via Key Vault.
- Clarify that Azure CLI commands work cross-platform and provide notes or examples for Linux/macOS users (e.g., file path conventions, environment variables).
- Avoid mentioning Windows scenarios exclusively or first; provide parity by including Linux equivalents in introductory and example sections.
- Where PowerShell is used, note that it is available cross-platform, but also provide native Bash or shell alternatives for Linux users.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/best-practices.md
...les/azure-resource-manager/templates/best-practices.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page exhibits mild Windows bias. Windows-specific tools and patterns (such as PowerShell cmdlets and Windows VM connection methods) are mentioned before their Linux equivalents. The only command-line conflict example is for PowerShell, and Windows connection guides are listed before Linux ones. There is also a focus on Visual Studio Code (a cross-platform tool, but with historical Windows association) and no mention of Linux-native editors or deployment tools.
Recommendations
- Provide equivalent examples for Linux command-line tools (e.g., Azure CLI) alongside PowerShell examples, especially when discussing parameter name conflicts.
- List Linux and Windows VM connection guides in parallel or alternate their order to avoid implicit prioritization.
- Mention Linux-native editors (such as Vim, Emacs, or VS Code on Linux) and deployment tools (e.g., Bash scripts, Azure CLI) when discussing tooling.
- Include references to Linux shell scripting and automation in sections about best practices and test toolkits.
- Ensure that all examples and recommendations are platform-neutral or provide both Windows and Linux variants where relevant.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/deployment-script-template-configure-dev.md
.../templates/deployment-script-template-configure-dev.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows and PowerShell environments. Most code examples for deploying and uploading scripts use Azure PowerShell commands, and the Docker volume mounting instructions use Windows-style drive letters (e.g., d:/docker), which are specific to Windows hosts. There are no equivalent Linux shell or Azure CLI examples for these steps, and the PowerShell approach is presented first in most sections. The documentation assumes familiarity with Windows tooling and patterns, leaving Linux users with less guidance.
Recommendations
- Provide equivalent Azure CLI and Bash examples for all PowerShell commands, especially for resource group deployment and file uploads.
- Include Docker volume mount instructions for Linux hosts (e.g., using /home/user/docker:/data) alongside Windows examples.
- Alternate the order of examples so that CLI/Bash instructions are presented first or equally with PowerShell.
- Clarify which steps are platform-agnostic and which require platform-specific commands, and provide guidance for both Windows and Linux users.
- Add screenshots or terminal outputs from Linux environments where appropriate.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/overview.md
.../articles/azure-resource-manager/templates/overview.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is mentioned as a primary scripting option (for deployment scripts and the ARM Template Toolkit), and the only test kit referenced is a PowerShell script. Authoring tools highlighted are Visual Studio and Visual Studio Code, both of which are strongly associated with Windows (though VS Code is cross-platform). In the list of deployment options, Azure CLI and PowerShell are both mentioned, but PowerShell is listed after Azure CLI. However, Linux-specific tools or workflows are not highlighted, and there are no explicit Linux shell (bash) examples or references to Linux-native tooling.
Recommendations
- Include explicit Bash and/or Azure CLI examples alongside or instead of PowerShell examples, especially for deployment scripts and testing.
- Mention Linux-native authoring tools or editors (such as Vim, Emacs, or JetBrains IDEs) where relevant, or clarify that Visual Studio Code is cross-platform.
- Highlight that the ARM Template Toolkit (arm-ttk) can be run on Linux (if possible), or provide alternative validation tools for Linux users.
- When listing deployment options, alternate the order or explicitly state parity between PowerShell and CLI, and provide example commands for both.
- Add references or links to Linux-specific guidance or quickstarts, ensuring Linux users feel equally supported.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/create-visual-studio-deployment-project.md
...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-first IDE) and PowerShell scripts for deployment. There is no mention of Linux or cross-platform alternatives, nor are there examples for Linux users or CLI-based workflows outside of PowerShell. The use of Windows-specific tools and patterns (Visual Studio, PowerShell, .ps1 scripts) is exclusive and presented as the default and only supported method.
Recommendations
- Add equivalent instructions for using cross-platform tools such as VS Code, Azure CLI, or ARM templates directly from the command line.
- Provide Linux/macOS-specific examples for project creation, template editing, and deployment, including bash scripts or Azure CLI commands.
- Clarify which steps are Windows-specific and offer alternatives for non-Windows environments.
- Mention and link to cross-platform deployment workflows (e.g., using GitHub Actions, Azure CLI, or Terraform) where appropriate.
- Include a note about Visual Studio Code as a cross-platform editor for ARM templates and Azure deployments.
- Provide guidance for users who do not have access to Visual Studio or PowerShell, including how to deploy using the Azure portal or other tools.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/deploy-cli.md
...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 the main examples use Azure CLI, which is cross-platform, there are several instances where Windows-specific shells (CMD, PowerShell) are mentioned before or instead of Linux equivalents. For example, instructions for passing arrays and setting variables provide Windows syntax and escaping guidance, but do not equally detail Linux/Bash alternatives. There is also a lack of explicit Linux/Bash examples in sections discussing variable assignment and parameter passing, and no mention of Linux-specific tooling or patterns. The page does not provide parity in examples for Linux users, and Windows terminology and patterns are often presented first.
Recommendations
- Add explicit Bash/Linux examples wherever Windows CMD/PowerShell syntax is shown, especially for variable assignment and parameter passing.
- When discussing shell-specific syntax, present Linux/Bash examples before or alongside Windows examples to avoid Windows-first ordering.
- Include notes or sections on common Linux patterns and troubleshooting, such as file permissions, path formats, and environment variables.
- Ensure that all CLI commands are tested and shown to work on both Windows and Linux shells, and clarify any differences.
- Where possible, use neutral, cross-platform syntax in examples, or provide side-by-side examples for both platforms.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/quickstart-create-template-specs.md
...-manager/templates/quickstart-create-template-specs.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias in several ways: file paths are exclusively given in Windows format (e.g., C:\Templates\...), and there are no examples or notes for Linux/macOS users regarding file paths or shell differences. The CLI examples use backslashes for line continuation, which is valid in Windows CMD but not in Bash. Additionally, the documentation references PowerShell and Azure PowerShell heavily, with no mention of Bash or Linux-native shells. The only mention of a known issue is for Windows PowerShell, and there is no guidance for Linux users. The documentation does not provide Linux/macOS-specific instructions or highlight cross-platform considerations.
Recommendations
- Provide file path examples in both Windows (C:\Templates\...) and Linux/macOS (/home/user/Templates/...) formats, or use a neutral placeholder (e.g., <path-to-template>).
- Add notes or callouts for Linux/macOS users regarding differences in path separators and shell syntax.
- Use forward slashes (/) in CLI examples or provide both Windows (\) and Bash (\) line continuation examples.
- Mention Bash or other Linux-native shells alongside PowerShell, and clarify that Azure CLI commands work cross-platform.
- Where PowerShell is referenced, also mention Bash or provide equivalent Bash script snippets.
- Include troubleshooting notes or known issues for Linux/macOS users if applicable.
- Ensure screenshots and UI references are not Windows-specific, or clarify if they are the same across platforms.