Azure Resource Manager

1002
Total Pages
808
Linux-Friendly Pages
194
Pages with Bias
19.4%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

492 issues found
Showing 251-275 of 492 flagged pages
Azure Resource Manager Relocate Azure Storage Account to another region ...er/management/relocation/relocation-storage-account.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation consistently provides PowerShell examples for command-line operations, with no mention of Azure CLI, Bash, or Linux/macOS-specific instructions. All scripting and automation guidance is centered on PowerShell, which is natively available only on Windows. The order of examples also places PowerShell before any Linux-friendly alternatives, and no Linux/macOS shell equivalents are given for template export, modification, deployment, or cleanup.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all command-line steps (template export, deployment, resource deletion).
  • Explicitly mention that AzCopy is cross-platform and provide sample commands for Linux/macOS users.
  • Include Bash or shell script equivalents for automation tasks.
  • Reorder examples so that cross-platform tools (Azure CLI, AzCopy) are presented before or alongside PowerShell.
  • Clarify which steps are OS-agnostic and which require platform-specific tooling.
GitHub Create Pull Request
Azure Resource Manager Relocate Azure Virtual Network to another region ...er/management/relocation/relocation-virtual-network.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation provides detailed instructions for relocating an Azure Virtual Network using the Azure Portal and PowerShell, with all CLI examples and automation steps shown exclusively in PowerShell. There are no examples or guidance for Linux/macOS users using the Azure CLI, Bash, or other cross-platform tools. Additionally, file editing instructions reference Notepad, a Windows-specific tool, and PowerShell is presented as the only automation option. The structure presents PowerShell before any mention of cross-platform alternatives, which are absent.
Recommendations
  • Add equivalent Azure CLI (az) examples for all automation steps, including exporting, editing, and redeploying templates.
  • Provide instructions for editing JSON files using cross-platform editors (e.g., vim, nano, VS Code) instead of or in addition to Notepad.
  • Explicitly state that all steps can be performed on Linux/macOS using Azure CLI and cross-platform editors.
  • Consider presenting cross-platform options (Azure CLI) before or alongside PowerShell to avoid Windows-first bias.
GitHub Create Pull Request
Azure Resource Manager Azure resource providers and types ...rce-manager/management/resource-providers-and-types.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. The Azure PowerShell section appears before Azure CLI and Python, and PowerShell is traditionally associated with Windows. The 'Windows Azure Service Management API' is mentioned in an important note, and the portal screenshots and instructions are implicitly Windows-centric (e.g., referencing 'Windows Azure' and using portal UI patterns familiar to Windows users). However, Azure CLI and Python examples are provided, which are cross-platform, and no critical functionality is locked to Windows-only tools.
Recommendations
  • Reorder the command-line sections to present Azure CLI before PowerShell, as CLI is cross-platform and more commonly used on Linux/macOS.
  • Clarify that Azure PowerShell is available cross-platform, and provide explicit instructions or links for Linux/macOS installation.
  • Replace or supplement references to 'Windows Azure Service Management API' with platform-neutral terminology, or explain its relevance to non-Windows users.
  • Include explicit notes or screenshots showing Azure portal usage on Linux/macOS browsers, if UI differences exist.
  • Ensure parity in detail and completeness between PowerShell, CLI, and Python examples.
GitHub Create Pull Request
Azure Resource Manager Best practices for templates ...les/azure-resource-manager/templates/best-practices.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation is generally cross-platform, but there is a notable Windows bias in the section discussing parameter name conflicts with PowerShell deployment commands. Windows/PowerShell tools and patterns are mentioned first and in detail, while Linux equivalents are not referenced. Additionally, in the section about connecting to virtual machines, Windows connection methods (RDP, WinRM) are listed before Linux methods, and the PowerShell cmdlet is the only deployment tool discussed in detail.
Recommendations
  • Include examples and discussion of Azure CLI and Bicep deployment commands alongside PowerShell, especially when discussing parameter name conflicts.
  • Mention Linux/macOS tools and workflows (e.g., az CLI, bash scripts) in relevant sections.
  • When listing connection methods to VMs, alternate the order or provide equal detail for Linux and Windows.
  • Add references to cross-platform editors and tools (e.g., VS Code is good, but mention that it runs on Linux/macOS too).
GitHub Create Pull Request
Azure Resource Manager Define multiple instances of an output value ...icles/azure-resource-manager/templates/copy-outputs.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation mentions Azure PowerShell before Azure CLI when discussing supported versions for zero-count copy loops, and the 'Next steps' section links only to PowerShell deployment instructions, omitting Linux/macOS-friendly alternatives like Azure CLI or portal-based deployment. No Linux-specific tools or examples are provided, and PowerShell is referenced as a primary method, which may create friction for non-Windows users.
Recommendations
  • List Azure CLI before PowerShell when mentioning supported tools, or mention both together to avoid implying preference.
  • Add links to Azure CLI deployment documentation in the 'Next steps' section alongside PowerShell.
  • Explicitly state that both Azure CLI and PowerShell are cross-platform, and provide examples or guidance for Linux/macOS users.
  • Include a brief note or example showing template deployment via Azure CLI.
GitHub Create Pull Request
Azure Resource Manager Deploy to Azure button ...e-resource-manager/templates/deploy-to-azure-button.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation provides a PowerShell example for URL encoding but omits equivalent Linux/macOS command-line examples (e.g., Bash, Python, curl). This creates friction for non-Windows users, as they must find their own solution for a required step. The PowerShell example is presented as the only code solution, and no Linux tools or patterns are mentioned.
Recommendations
  • Add Bash/Linux/macOS examples for URL encoding, such as using Python, curl, or jq.
  • Explicitly mention that any platform can be used and provide cross-platform alternatives.
  • Present examples for both Windows and Linux/macOS side by side, or use platform-neutral tools where possible.
GitHub Create Pull Request
Azure Resource Manager Deploy resources to subscription ...e-resource-manager/templates/deploy-to-subscription.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying ARM templates at the subscription scope. However, PowerShell examples are given equal prominence and detail as Azure CLI, despite PowerShell being primarily a Windows tool. There are no explicit Linux/macOS shell examples (e.g., Bash), and PowerShell is presented as a default option alongside CLI, which may create friction for Linux/macOS users. Additionally, the documentation refers to PowerShell-specific commands and patterns without noting cross-platform alternatives or clarifying that PowerShell Core is available on Linux/macOS.
Recommendations
  • Clarify that Azure CLI is fully cross-platform and highlight it as the recommended option for Linux/macOS users.
  • Add explicit Bash shell examples for Azure CLI commands to demonstrate usage on Linux/macOS.
  • Note that PowerShell Core is available on Linux/macOS, but most Linux users prefer Bash/CLI.
  • Present Azure CLI examples before PowerShell, or group them by platform (Windows vs. Linux/macOS).
  • Avoid implying parity between PowerShell and CLI for all platforms; clarify platform-specific guidance.
GitHub Create Pull Request
Azure Resource Manager Configure development environment for deployment scripts in templates | Microsoft Docs .../templates/deployment-script-template-configure-dev.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page exhibits a moderate Windows bias. While both PowerShell and Azure CLI (bash) examples are provided for container-based development, all deployment and upload instructions use PowerShell cmdlets (New-AzResourceGroup, Set-AzStorageFileContent, etc.) with no equivalent Azure CLI or bash examples. Docker usage instructions and volume mount examples use Windows-style drive letters (e.g., d:/docker), and the PowerShell workflow is presented first in each section. Linux/macOS users must adapt these instructions themselves, which may cause friction.
Recommendations
  • Provide Azure CLI/bash equivalents for all PowerShell deployment and upload commands (e.g., az group create, az deployment group create, az storage file upload).
  • Include Docker volume mount examples using Linux/macOS paths (e.g., /home/user/docker:/data) alongside Windows drive letter examples.
  • Alternate the order of PowerShell and CLI examples, or present them side-by-side, to avoid Windows-first bias.
  • Explicitly mention platform differences and provide guidance for Linux/macOS users where workflows or tooling differ.
GitHub Create Pull Request
Azure Resource Manager Template deployment what-if ...les/azure-resource-manager/templates/deploy-what-if.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page exhibits a moderate Windows bias. PowerShell examples and syntax are shown first in most sections, and the sample outputs are consistently in PowerShell format. References to installing the Azure PowerShell module and using PowerShell-specific commands are given prominence, with CLI examples provided but generally after PowerShell. Output screenshots and text are in PowerShell format, and prompts (such as confirmation dialogs) use Windows/PowerShell conventions. There is no mention of Linux/macOS-specific considerations, such as shell differences, nor are there any examples using Bash, zsh, or other non-Windows shells.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples so that CLI is shown first in some sections.
  • Include explicit notes or examples for Linux/macOS users, such as shell syntax differences (e.g., line continuations, quoting).
  • Provide sample outputs in both PowerShell and Azure CLI formats, or clarify that output is similar across platforms.
  • Mention that Azure CLI works cross-platform and highlight any OS-specific caveats.
  • Add a section addressing Linux/macOS installation and usage, especially for CLI.
  • Where confirmation prompts are shown, note differences between PowerShell and CLI behavior on different OSes.
GitHub Create Pull Request
Azure Resource Manager Use deployment scripts in Azure Resource Manager templates ...source-manager/templates/deployment-script-template.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples and terminology are consistently presented first, with Windows-centric tools (e.g., PowerShell cmdlets, ARMClient in PowerShell) dominating the walkthroughs and sample templates. While Azure CLI and Bash are supported and mentioned, most code samples, inline script examples, and troubleshooting sections focus on PowerShell, with Linux/Bash equivalents appearing later or in less detail. Some sections (e.g., 'Use external scripts', 'Work with outputs from PowerShell scripts') lack parallel Bash/CLI examples, and the 'Try it' instructions are PowerShell-only. The documentation assumes familiarity with Windows/PowerShell conventions, which may create friction for Linux/macOS users.
Recommendations
  • Provide Bash/CLI examples alongside every PowerShell example, especially in sample templates and inline script sections.
  • Alternate the order of examples so that Azure CLI/Bash is shown first in some sections.
  • Include 'Try it' instructions for Azure CLI/Bash in addition to PowerShell, and clarify how to use Cloud Shell in Bash mode.
  • Expand troubleshooting and output handling sections to cover Bash/CLI workflows in equal detail.
  • Explicitly mention cross-platform compatibility and highlight differences or caveats for Linux/macOS users where relevant.
GitHub Create Pull Request
Azure Resource Manager Tutorial - Deploy a linked template ...nager/templates/deployment-tutorial-linked-template.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page exhibits moderate Windows bias. The main workflow for storing templates in Azure Storage is presented only as an Azure PowerShell script, with no equivalent Azure CLI or Bash example for Linux/macOS users. PowerShell is introduced first and in more detail, and instructions reference Windows-centric patterns (e.g., right-click to paste, $home variable, Read-Host prompts). While deployment is covered for both PowerShell and Azure CLI, the initial template upload and setup steps are Windows/PowerShell-only, creating friction for Linux/macOS users.
Recommendations
  • Add an Azure CLI or Bash script example for uploading templates to Azure Storage, covering all steps currently shown only in PowerShell.
  • Present CLI and PowerShell examples side-by-side or in parallel tabs throughout the tutorial, not just for deployment.
  • Avoid Windows-centric instructions (e.g., right-click to paste) or provide platform-specific guidance.
  • Clarify $home usage or replace with cross-platform environment variables (e.g., $HOME for Bash).
GitHub Create Pull Request
Azure Resource Manager Create and deploy template spec ...-manager/templates/quickstart-create-template-specs.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently uses Windows-style file paths (e.g., C:\Templates\...) in all code examples, including Azure CLI, PowerShell, and ARM templates. There are no Linux/macOS path examples (e.g., /home/user/Templates/...), nor any mention of Linux/macOS-specific considerations. This may cause confusion or friction for non-Windows users, especially when copying and pasting commands. Additionally, the documentation references PowerShell and Azure CLI, but does not provide any shell-specific notes for Bash or zsh users.
Recommendations
  • Provide both Windows and Linux/macOS file path examples in all code blocks (e.g., C:\Templates\createStorageV1.json and ~/Templates/createStorageV1.json).
  • Add notes clarifying that file paths should be adapted to the user's operating system.
  • Explicitly mention that Azure CLI commands work cross-platform and provide shell-specific variable assignment examples (e.g., export id=... for Bash/zsh).
  • Where PowerShell is referenced, clarify that Azure PowerShell is available on Linux/macOS, and provide any OS-specific installation or usage notes.
  • Avoid assuming a Windows environment in text and screenshots, or provide alternatives for Linux/macOS users.
GitHub Create Pull Request
Azure Resource Manager Develop ARM templates for cloud consistency ...source-manager/templates/template-cloud-consistency.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. PowerShell examples are frequently provided, often before or alongside Azure CLI commands, but never with Linux shell equivalents. Windows-specific tools and patterns (e.g., PowerShell DSC, .ps1 scripts, Windows VM images) are referenced without Linux alternatives. Examples for VM extensions and scripts focus on Windows, and there are no bash or Linux shell script examples. This creates friction for Linux/macOS users, though most tasks can be completed with Azure CLI or by adapting the instructions.
Recommendations
  • Provide bash/Linux shell equivalents for PowerShell scripts, especially for verifying template functions and resource providers.
  • Include Linux VM image examples alongside Windows ones in ARM template snippets.
  • Show how to use Linux-compatible scripts (e.g., .sh) in Custom Script Extensions.
  • When listing commands, alternate the order or group by platform, rather than listing PowerShell first.
  • Reference cross-platform tools (e.g., VS Code) more explicitly for testing and automation.
  • Clarify which instructions are platform-agnostic and which require adaptation for Linux/macOS.
GitHub Create Pull Request
Azure Resource Manager Template functions - scope ...resource-manager/templates/template-functions-scope.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation is generally platform-neutral in its main content, focusing on ARM template syntax and JSON examples. However, the 'Next steps' section references Azure PowerShell as the primary deployment method, implicitly prioritizing Windows tooling and workflows. There is no mention of Linux/macOS CLI alternatives (such as Azure CLI), nor are deployment instructions for non-Windows platforms provided or linked.
Recommendations
  • Include references and links to Azure CLI deployment guides alongside Azure PowerShell, especially in the 'Next steps' section.
  • Explicitly mention that ARM templates can be deployed from Linux/macOS using Azure CLI, and provide example commands.
  • Ensure parity in deployment instructions for all major platforms (Windows, Linux, macOS) to avoid implicit bias.
  • Consider listing cross-platform tools (e.g., Azure CLI, VS Code) before or alongside Windows-specific tools.
GitHub Create Pull Request
Azure Resource Manager Convert portal template to template spec ...re-resource-manager/templates/template-spec-convert.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation provides only PowerShell-based automation for converting templates, with no mention of Bash, Azure CLI, or Linux/macOS-compatible alternatives. The script referenced is a PowerShell script (.ps1), and all command-line examples use PowerShell syntax. Manual conversion steps are portal-based and platform-neutral, but all automation guidance is Windows-centric.
Recommendations
  • Provide equivalent Azure CLI or Bash scripts for Linux/macOS users.
  • Include examples using Azure CLI commands for template spec creation and migration.
  • Explicitly state platform requirements for the PowerShell script and suggest cross-platform PowerShell Core usage if applicable.
  • Reorder or parallelize sections so that Linux/macOS-friendly methods are presented alongside Windows/PowerShell methods.
GitHub Create Pull Request
Azure Resource Manager Create a template spec with linked templates ...urce-manager/templates/template-specs-create-linked.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. File path examples use Windows-style paths (e.g., c:\Templates\...), and instructions assume a Windows file system. PowerShell examples are shown first in each section, and there is a note about a known issue specific to Windows PowerShell. There are no explicit Linux/macOS file path examples or instructions for creating directories/files on those platforms.
Recommendations
  • Include Linux/macOS file path examples (e.g., /home/user/Templates/linkedTS/azuredeploy.json) alongside Windows paths.
  • Add instructions or notes for creating directories and saving files on Linux/macOS (e.g., using mkdir, touch, or appropriate GUI steps).
  • Alternate the order of CLI and PowerShell examples, or present them side-by-side to avoid implicit prioritization.
  • Clarify that the Azure CLI commands work cross-platform and provide any platform-specific caveats.
  • Add a note about how to handle variable assignment in bash/zsh for Linux/macOS users, especially for the template spec ID retrieval.
GitHub Create Pull Request
Azure Resource Manager Create portal forms for template spec ...anager/templates/template-specs-create-portal-forms.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell (a Windows-centric tool) is mentioned first and in detail for creating and updating template specs, with explicit references to PowerShell cmdlets for obtaining parameters (such as tenantId and objectId). While Azure CLI examples are also provided, PowerShell is consistently presented before CLI, and there are no Linux/macOS-specific instructions or notes. The documentation assumes familiarity with Windows tools and patterns, which may create friction for Linux/macOS users.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI first to balance platform representation.
  • Explicitly mention that Azure CLI works cross-platform and provide links or notes for Linux/macOS installation and usage.
  • For parameter acquisition (e.g., tenantId, objectId), provide Azure CLI equivalents alongside PowerShell cmdlets (e.g., 'az account show' or 'az ad user show').
  • Add a note clarifying that all steps can be performed on Linux/macOS using Azure CLI and VS Code.
  • Where possible, avoid referencing Windows-only tools or provide parity for Linux/macOS users.
GitHub Create Pull Request
Azure Resource Manager Deploy a template spec as a linked template ...ger/templates/template-specs-deploy-linked-template.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently uses Windows-style file paths (e.g., c:\Templates\deployTS\azuredeploy.json) in all examples and instructions, without mentioning Linux/macOS equivalents. While both Azure PowerShell and Azure CLI examples are provided, the file path format and instructions assume a Windows environment, which may cause confusion or friction for Linux/macOS users.
Recommendations
  • Provide Linux/macOS file path examples (e.g., /home/user/Templates/deployTS/azuredeploy.json) alongside Windows paths.
  • Add notes clarifying that file paths should be adapted to the user's operating system.
  • Consider showing CLI examples with Linux-style paths first or in parallel with Windows examples.
  • Explicitly mention that both Azure PowerShell and Azure CLI are cross-platform, and provide guidance for installing and using them on Linux/macOS.
GitHub Create Pull Request
Azure Resource Manager Template with dependent resources ...ate-tutorial-create-templates-with-dependent-resources.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The tutorial focuses on deploying a Windows VM and provides examples for both Azure CLI (Bash) and PowerShell, but the template used is explicitly for Windows. There is no mention of Linux VM templates, nor are there instructions or examples for connecting to a Linux VM (e.g., via SSH). The deployment steps are technically cross-platform, but the resource being deployed is Windows-specific, and RDP is referenced for verification, which is Windows-centric.
Recommendations
  • Include a parallel example or mention of deploying a Linux VM template, such as linking to or referencing the 'vm-simple-linux' template.
  • Provide instructions for verifying a Linux VM deployment (e.g., SSH connection) alongside the RDP instructions for Windows.
  • Clarify that the steps are applicable to both Windows and Linux VMs, and show how to modify the template for Linux.
  • When referencing Quickstart templates, mention both Windows and Linux options.
  • Add a note or section on differences in post-deployment access (RDP vs. SSH) depending on the OS.
GitHub Create Pull Request
Azure Resource Manager Tutorial - Create and deploy template ...r/templates/template-tutorial-create-first-template.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows tools and patterns (PowerShell, Windows paths) are mentioned first or exclusively in several places, and installation instructions for Azure CLI list Windows before Linux/macOS. PowerShell is given equal or slightly more prominence than Bash/Azure CLI, and there are notes about converting Bash commands for Windows users, but no reciprocal guidance for Linux/macOS users regarding PowerShell. There are no explicit Linux/macOS-specific examples for file creation, path handling, or troubleshooting, and the screenshots and instructions are primarily Windows-centric.
Recommendations
  • Alternate the order of Windows and Linux/macOS instructions and links to avoid Windows-first bias.
  • Provide explicit Linux/macOS examples for file creation, path handling, and troubleshooting (e.g., using touch, nano, or vi for file creation).
  • Include notes for Linux/macOS users on how to adapt PowerShell commands if needed, or clarify that Bash/Azure CLI is cross-platform.
  • Add screenshots from Linux/macOS environments (e.g., VS Code on Ubuntu, Azure CLI in Terminal) to balance visual representation.
  • Mention that Visual Studio Code and Azure CLI are cross-platform, and provide parity in installation and usage instructions.
  • Where notes are given for converting Bash commands for Windows, add reciprocal notes for Linux/macOS users regarding PowerShell commands.
GitHub Create Pull Request
Azure Resource Manager Use template deployment scripts | Microsoft Docs ...nager/templates/template-tutorial-deployment-script.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias: all deployment script examples use PowerShell, and the ARM template's deploymentScripts resource only demonstrates the 'AzurePowerShell' kind. There is no example or mention of Bash or Linux shell scripting for deployment scripts, nor are Linux/macOS equivalents for PowerShell commands provided. PowerShell-specific patterns (such as escape characters and cmdlets) are explained in detail, while Linux alternatives are absent or secondary. The CLI examples are present for some steps, but the core scripting and troubleshooting are PowerShell-centric.
Recommendations
  • Add equivalent Bash (Azure CLI) deployment script examples, showing how to create and add certificates using Bash.
  • Document the 'AzureCLI' kind for deploymentScripts, including sample scriptContent in Bash.
  • Clarify platform support for deploymentScripts (e.g., which features are Windows-only, which work cross-platform).
  • Provide troubleshooting steps for Linux/macOS users, including how to access and interpret output files.
  • Ensure all critical steps have both PowerShell and Bash/CLI examples, and alternate which is presented first.
GitHub Create Pull Request
Azure Resource Manager Use ARM template test toolkit ...icles/azure-resource-manager/templates/test-toolkit.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily PowerShell-centric, with all usage and customization examples relying exclusively on PowerShell scripts and cmdlets. While Linux and macOS installation instructions are provided, they require installing PowerShell and do not offer Bash, native shell, or platform-specific alternatives. Windows instructions are presented first, and all code samples use Windows/PowerShell tools and patterns, with no mention of Linux-native equivalents or cross-platform scripting options.
Recommendations
  • Provide Bash or shell script examples for Linux/macOS users where possible, especially for common tasks like extracting archives, navigating directories, and running tests.
  • Clarify whether the toolkit can be used with other shells or scripting languages, or explicitly state PowerShell is required.
  • Consider reordering sections so that Windows, Linux, and macOS instructions are presented in parallel or with Linux/macOS first in relevant contexts.
  • Add troubleshooting notes for common Linux/macOS issues (e.g., file permissions, path formats, execution policy differences).
  • If PowerShell is the only supported method, make this explicit at the top of the documentation and provide rationale.
GitHub Create Pull Request
Azure Resource Manager Overview of deployment troubleshooting for Bicep files and ARM templates ...les/azure-resource-manager/troubleshooting/overview.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation mentions Azure PowerShell before Azure CLI when discussing error details, and provides PowerShell command examples alongside CLI, but does not show Linux-specific troubleshooting tools or workflows. The use of Visual Studio Code is cross-platform, but no explicit Linux/macOS guidance or parity is given for command-line troubleshooting.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell, as CLI is cross-platform and preferred by many Linux/macOS users.
  • Explicitly mention that Azure CLI works on Linux/macOS and provide links to installation guides for those platforms.
  • Include troubleshooting workflows or tools that are native to Linux/macOS environments, such as shell scripting or integration with other editors.
  • Clarify that Visual Studio Code and its extensions are available on Linux/macOS.
  • Avoid implying PowerShell is the primary or default tool for troubleshooting; balance examples and recommendations.
GitHub Create Pull Request
Azure Resource Manager SKU not available errors ...rce-manager/troubleshooting/error-sku-not-available.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides troubleshooting steps for SKU availability errors in Azure, with example commands and scripts for both Azure CLI and Azure PowerShell. However, the PowerShell section is notably more detailed, including advanced scripting and output formatting, while the Azure CLI section is limited to basic usage. The PowerShell examples use Windows-specific tools and patterns, and PowerShell is presented before the portal and REST options. There is no explicit mention of Linux/macOS shell scripting, nor are Bash or cross-platform scripting examples provided. The REST example uses a Windows-style file path ('.\sku-list.json') for output, which may confuse Linux/macOS users.
Recommendations
  • Expand Azure CLI examples to include advanced filtering and output formatting, matching the depth of the PowerShell section.
  • Provide Bash shell scripting examples for Linux/macOS users, demonstrating how to process and filter SKU data using jq or grep.
  • Use cross-platform file path syntax in REST examples (e.g., './sku-list.json') or note the difference for Windows vs. Linux/macOS.
  • Explicitly mention that Azure CLI is available on all platforms and highlight parity between CLI and PowerShell capabilities.
  • Add a note or section for Linux/macOS users, clarifying how to adapt PowerShell scripts or use CLI/Bash alternatives.
GitHub Create Pull Request
Azure Resource Manager Create Bicep files - Visual Studio ...ger/bicep/quickstart-create-bicep-use-visual-studio.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page focuses on using Visual Studio, a Windows-centric IDE, and lists Visual Studio as the primary tool for Bicep file creation. While it mentions Visual Studio Code as an alternative, the main instructions and screenshots are for Visual Studio. In deployment and cleanup sections, both Azure CLI (cross-platform) and Azure PowerShell (Windows-preferred) examples are provided, but PowerShell is given equal prominence. There are no Linux-specific instructions, nor is there mention of Linux-native editors or workflows beyond a brief link to Visual Studio Code.
Recommendations
  • Add explicit instructions and screenshots for Visual Studio Code, which is cross-platform, or link to a Linux-specific quickstart.
  • Include a note about platform compatibility for Visual Studio and Visual Studio Code, clarifying that Visual Studio is Windows-only while VS Code runs on Linux and macOS.
  • Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and more commonly used on Linux.
  • Mention Linux-native editors (e.g., Vim, Emacs) and how Bicep files can be authored and deployed from Linux environments.
  • Provide troubleshooting tips for Linux users, such as installing the Bicep CLI and using it with Azure CLI.
GitHub Create Pull Request
← Previous Page 11 of 20 Next →