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 1-25 of 1281 flagged pages
Azure Resource Manager Use template deployment scripts | Microsoft Docs ...nager/templates/template-tutorial-deployment-script.md
High Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias. The core deployment script example is written exclusively in PowerShell, and the only supported script type for deployment scripts is PowerShell. The tutorial and explanations reference PowerShell-specific syntax, escape characters, and troubleshooting steps. While Azure CLI examples are provided for some steps, all scripting and automation focus on PowerShell, with no Bash or Linux shell script equivalents. The documentation does not mention how to author or use deployment scripts with Bash, nor does it provide Linux/macOS-specific guidance for the main scripting workflow.
Recommendations
  • Add Bash deployment script examples and clarify if Bash is supported for deployment scripts.
  • Provide Linux/macOS-specific troubleshooting steps, especially for script debugging and resource cleanup.
  • Explicitly state platform limitations (e.g., if only PowerShell is supported, mention alternatives for Linux users).
  • Reorder examples so that CLI/Bash instructions are presented before or alongside PowerShell, not after.
  • Include notes or links to cross-platform scripting strategies for ARM template deployment scripts.
GitHub Create Pull Request
Azure Resource Manager Create & deploy Visual Studio resource group projects ...r/templates/create-visual-studio-deployment-project.md
High Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily focused on Visual Studio and PowerShell, both of which are primarily Windows-centric tools. All examples and workflow steps assume the use of Visual Studio (Windows-only) and PowerShell scripts for deployment, with no mention of Linux/macOS alternatives or cross-platform tooling. There are no CLI, VS Code, or Bash examples, and no guidance for users on non-Windows platforms.
Recommendations
  • Add equivalent instructions for deploying Azure Resource Manager templates using Azure CLI, which is cross-platform.
  • Provide examples using VS Code (available on Windows, Linux, and macOS) for authoring and deploying templates.
  • Include Bash script examples for deployment, or reference how to use PowerShell Core on Linux/macOS.
  • Clearly state platform requirements and offer alternative workflows for Linux/macOS users.
  • Mention and link to cross-platform tools such as Azure CLI, Bicep, and VS Code extensions for ARM templates.
GitHub Create Pull Request
Azure Resource Manager Deploy VM extensions with template ...er/templates/template-tutorial-deploy-vm-extensions.md
High Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily biased toward Windows. All examples, scripts, and templates target Windows VMs, specifically using PowerShell and Windows-specific tools (e.g., Install-WindowsFeature). There are no Linux VM examples, nor any mention of Linux equivalents (such as Bash scripts or Linux extensions). The tutorial assumes the user is deploying a Windows VM and does not provide guidance for Linux users.
Recommendations
  • Add parallel examples for deploying VM extensions to Linux VMs, using Bash or shell scripts.
  • Include ARM template snippets for Custom Script Extension on Linux, with sample Bash scripts (e.g., installing Apache or Nginx).
  • Provide links to both Windows and Linux extension documentation.
  • Explicitly mention that the tutorial is Windows-specific, or restructure to offer both Windows and Linux paths.
  • Show how to retrieve the public IP address using Azure CLI or Bash for Linux users.
GitHub Create Pull Request
Azure Resource Manager Enable debug logging ...source-manager/troubleshooting/enable-debug-logging.md
High Priority View Details →
Scanned: 2026-01-14 00:00
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 focused on Azure PowerShell for enabling debug logging, which is only available via PowerShell and not Azure CLI. PowerShell is a Windows-centric tool, and there are no Linux/macOS-specific alternatives or workarounds provided for enabling debug logging. Examples and instructions for critical tasks (enabling debug logging) are PowerShell-only, with Azure CLI users explicitly told this functionality is unavailable. The documentation does not mention cross-platform scripting or provide parity for Linux/macOS users.
Recommendations
  • Provide alternative methods for enabling debug logging that work on Linux/macOS, such as REST API calls, ARM template parameters, or other cross-platform tools.
  • Clearly state platform limitations and suggest workarounds for non-Windows users.
  • If PowerShell is required, mention that PowerShell Core is available on Linux/macOS and provide installation guidance.
  • Consider reordering sections so that cross-platform options (if any) are presented first, or at least equally.
  • Add explicit notes about Linux/macOS compatibility and limitations.
GitHub Create Pull Request
Azure Resource Manager Create & deploy Visual Studio resource group projects ...r/templates/create-visual-studio-deployment-project.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation is heavily oriented toward Windows users by requiring Visual Studio (a Windows-centric IDE) and PowerShell scripts for deployment. All examples and screenshots are based on Visual Studio, and deployment instructions use PowerShell scripts without mentioning cross-platform alternatives or Linux/macOS workflows. There are no examples or guidance for Linux or macOS users, nor any mention of equivalent tooling or approaches for those platforms.
Recommendations
  • Add instructions and examples for deploying Azure Resource Manager templates using cross-platform tools such as Azure CLI, VS Code, or GitHub Actions.
  • Include Linux/macOS-specific guidance for project creation, template editing, and deployment.
  • Mention and demonstrate how to use VS Code (which is cross-platform) for ARM template authoring and deployment.
  • Provide equivalent shell (bash) commands for deployment, or reference Azure CLI usage.
  • Clarify platform requirements and suggest alternatives for non-Windows users at the beginning of the article.
GitHub Create Pull Request
Azure Resource Manager Deploy VM extensions with template ...er/templates/template-tutorial-deploy-vm-extensions.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on deploying VM extensions to Windows VMs using PowerShell scripts and Windows-specific tooling (e.g., Install-WindowsFeature, powershell.exe). All examples, templates, and walkthroughs are for Windows VMs, with no mention of Linux VMs, Bash scripts, or Linux-specific extensions. The tutorial title and content do not clarify that it is Windows-only, and Linux users are not provided with equivalent guidance.
Recommendations
  • Add parallel examples for deploying extensions to Linux VMs, such as using the Custom Script Extension to run Bash scripts.
  • Include sample ARM template snippets for Linux VM extensions (e.g., using commandToExecute: 'bash installWebServer.sh').
  • Provide links to documentation about Linux VM extensions and their usage.
  • Clarify in the introduction that the tutorial is Windows-specific, or restructure to cover both platforms.
  • Show both PowerShell and Bash commands for tasks like password generation and public IP retrieval.
  • Mention Linux equivalents for tools and patterns (e.g., apt-get for installing web servers).
GitHub Create Pull Request
Azure Resource Manager Use template deployment scripts | Microsoft Docs ...nager/templates/template-tutorial-deployment-script.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation is heavily biased towards Windows and PowerShell. All deployment script examples use PowerShell, with no Bash or cross-platform alternatives. The deployment script resource only demonstrates 'AzurePowerShell' as the script kind, and the script content is exclusively PowerShell. References to quoting rules and escape characters are PowerShell-specific. While Azure CLI examples are provided for some steps, the core deployment script and debugging instructions assume PowerShell and Windows-centric tools. There is no mention of how to accomplish the same tasks using Bash or Linux-native scripting, nor are Linux/macOS troubleshooting steps included.
Recommendations
  • Add Bash-based deployment script examples using 'AzureCLI' as the script kind.
  • Provide equivalent scriptContent for Bash, showing how to create and add certificates using Azure CLI.
  • Include Linux/macOS-specific troubleshooting steps for accessing deployment script resources and logs.
  • Clarify which steps are cross-platform and which are Windows/PowerShell-only.
  • Present CLI and Bash examples before or alongside PowerShell examples to avoid 'windows_first' ordering.
GitHub Create Pull Request
Azure Resource Manager Enable debug logging ...source-manager/troubleshooting/enable-debug-logging.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily focused on Azure PowerShell for enabling debug logging, which is only available via PowerShell and not Azure CLI. This creates a significant bias toward Windows users, as PowerShell is natively available on Windows and the instructions do not provide Linux/macOS alternatives or workarounds for enabling debug logging. While Azure CLI is covered for retrieving and deleting logs, Linux/macOS users cannot enable debug logging as described.
Recommendations
  • Provide explicit guidance or workarounds for Linux/macOS users, such as installing PowerShell Core (pwsh) on non-Windows platforms and using the same Azure PowerShell cmdlets.
  • Clearly state that PowerShell Core is cross-platform and provide installation instructions for Linux/macOS.
  • Advocate for parity in Azure CLI by requesting or documenting feature gaps (e.g., enabling debug logging via CLI).
  • Add a note or dedicated section for Linux/macOS users outlining steps to enable debug logging using PowerShell Core.
GitHub Create Pull Request
Azure Resource Manager Add module settings in the Bicep config file ...s/azure-resource-manager/bicep/bicep-config-modules.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing Azure PowerShell and Azure CLI as the primary credential sources, listing 'AzurePowerShell' immediately after 'AzureCLI' in credential precedence, and omitting explicit Linux or cross-platform command examples. No Linux-specific tools or authentication patterns are mentioned, and the documentation does not clarify parity or differences for Linux users.
Recommendations
  • Explicitly mention that Azure CLI and Azure PowerShell are available on both Windows and Linux, and clarify any platform-specific differences.
  • Provide Linux-specific examples or notes, such as authentication via environment variables or managed identities, especially for scenarios where Azure PowerShell is not available or commonly used.
  • Include guidance for using Bicep in Linux environments, such as installation instructions, credential management, and troubleshooting tips.
  • List credential types in a neutral order (e.g., alphabetically) to avoid implying Windows-first workflows.
  • Reference cross-platform editors and tools (e.g., VS Code) with installation and usage notes for Linux.
GitHub Create Pull Request
Azure Resource Manager Use deployment scripts in Bicep ...zure-resource-manager/bicep/deployment-script-bicep.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. Azure PowerShell examples and references are presented alongside Azure CLI, but PowerShell is given equal or sometimes greater prominence, and Windows-centric tools and patterns (such as PowerShell scripting and ARMClient usage via PowerShell) are frequently referenced. The deployment and management instructions for Bicep scripts often default to PowerShell, with CLI alternatives provided but not always prioritized. There is little explicit mention of Linux-specific scripting environments or shell usage outside of Azure CLI, and no examples using Bash or other native Linux tools for deployment or management. The documentation does not provide parity for Linux users in terms of deployment workflow examples, troubleshooting, or environment setup.
Recommendations
  • Provide Linux-native deployment and management examples, such as Bash scripts using az CLI for resource group and deployment management.
  • Ensure that CLI (az) examples are presented before or at least equally with PowerShell examples, especially in quickstart and workflow sections.
  • Explicitly mention and demonstrate how to use Linux shell environments for script development, deployment, and troubleshooting.
  • Include instructions for setting up and using Bicep and deployment scripts on Linux, including package installation, environment configuration, and common Linux patterns.
  • Avoid assuming PowerShell as the default scripting environment; clarify when examples are Windows-specific and provide Linux equivalents.
  • Highlight cross-platform compatibility and note any limitations or differences in behavior between Windows and Linux environments.
GitHub Create Pull Request
Azure Resource Manager Develop a deployment script in Bicep ...re-resource-manager/bicep/deployment-script-develop.md
High Priority View Details →
Scanned: 2026-01-12 00:00
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. PowerShell examples and references are consistently presented alongside Azure CLI (Bash) examples, but Windows-centric tools and patterns (such as PowerShell, Connect-AzAccount, CommandLineToArgvW, and Start-Sleep) are mentioned explicitly and sometimes before their Linux equivalents. Windows/PowerShell concepts (like $ErrorActionPreference, Start-Sleep, and Connect-AzAccount) are explained in detail, while Linux/Bash error handling and scripting patterns receive less attention. The documentation references Windows APIs (CommandLineToArgvW) for argument parsing, which may be unfamiliar or irrelevant to Linux users. However, most examples do provide both CLI (Bash) and PowerShell variants, and the underlying deployment scripts run in Ubuntu containers, which helps mitigate bias.
Recommendations
  • Ensure that CLI (Bash) examples and explanations are presented before or alongside PowerShell examples, not after.
  • Provide equivalent Linux/Bash scripting patterns and troubleshooting tips (e.g., explain 'set -e', error trapping, and debugging in Bash as thoroughly as PowerShell's $ErrorActionPreference).
  • Avoid referencing Windows-specific APIs (e.g., CommandLineToArgvW) without also explaining the Linux/Bash equivalent or clarifying cross-platform behavior.
  • When discussing sleep/troubleshooting, mention Bash alternatives (e.g., 'sleep 60') alongside PowerShell's Start-Sleep.
  • Expand explanations of Bash/CLI tools and patterns (e.g., jq usage, output handling, error management) to match the detail given to PowerShell.
  • Review sample links and ensure parity in complexity and coverage between CLI and PowerShell samples.
  • Explicitly state that deployment scripts run in Ubuntu containers and clarify any platform-specific behaviors or limitations.
GitHub Create Pull Request
Azure Resource Manager Bicep What-If: Preview Changes Before Deployment ...rticles/azure-resource-manager/bicep/deploy-what-if.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by consistently presenting PowerShell examples alongside Azure CLI, often giving PowerShell equal or greater prominence. There is no mention of Linux-specific shell environments (e.g., Bash, zsh), nor are there any explicit Linux terminal examples or instructions. The installation and usage instructions for Azure CLI are generic, but all scripting examples are either Azure CLI (which is cross-platform) or PowerShell (which is Windows-centric, though available on Linux, but not the default). No Linux-native tools or shell patterns are shown, and PowerShell examples are provided for every operation, sometimes with more detail than CLI. There are no Bash or Linux shell script equivalents, and no guidance for Linux users on environment setup or command usage nuances.
Recommendations
  • Add explicit Bash examples for all Azure CLI commands, using standard Linux shell syntax (e.g., export, $(...), etc.), and clarify that Azure CLI commands work natively in Bash/zsh/fish on Linux and macOS.
  • Include notes or sections on installing Azure CLI and running Bicep deployments on Linux and macOS, including package manager instructions (apt, yum, brew).
  • Clarify that PowerShell is available cross-platform, but is not the default shell on Linux/macOS, and provide guidance for users who prefer Bash.
  • Where PowerShell is mentioned, add parallel Bash scripting examples for programmatic evaluation (e.g., using jq to parse JSON output from Azure CLI).
  • Ensure that all examples and instructions are presented in a way that does not assume a Windows environment, and avoid giving PowerShell precedence over CLI or Bash.
GitHub Create Pull Request
Azure Resource Manager Linter rule - no location expressions outside of parameter default values ...anager/bicep/linter-rule-no-loc-expr-outside-params.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page provides deployment guidance and examples exclusively using Azure PowerShell commands, which are primarily associated with Windows environments. There is no mention of cross-platform or Linux-native tools such as Azure CLI, nor are Linux shell examples provided. Windows/PowerShell tools are discussed in detail, with no parity for Linux or macOS users.
Recommendations
  • Include equivalent Azure CLI examples for deployment scenarios, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Mention that Azure PowerShell is available on Linux and macOS, but clarify cross-platform alternatives.
  • Provide bash or shell script examples where appropriate.
  • Ensure that references to deployment commands do not assume a Windows-first audience by listing CLI and PowerShell options together or in parallel sections.
  • Add notes or links for Linux/macOS users on how to perform the same actions using their preferred tools.
GitHub Create Pull Request
Azure Resource Manager Tutorial - custom actions & resources ...ns/tutorial-create-managed-app-with-custom-provider.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a bias toward Windows environments by providing a detailed PowerShell script for packaging and uploading the managed application artifacts to Azure Storage, while omitting equivalent instructions for Linux/macOS users (e.g., Bash or Azure CLI). The PowerShell example appears before the Azure CLI deployment steps, and there is no mention of cross-platform alternatives for the artifact upload process. The use of Windows-specific tools and scripting patterns (e.g., $RANDOM, backtick line continuation, PowerShell cmdlets) further reinforces the Windows-centric approach.
Recommendations
  • Provide Bash/Azure CLI examples for packaging and uploading the application artifacts to Azure Storage, suitable for Linux/macOS users.
  • Present cross-platform instructions side-by-side or in tabs, ensuring parity and visibility for both Windows and Linux users.
  • Avoid using Windows-specific scripting features (e.g., backtick line continuation) without offering alternatives.
  • Explicitly mention that both PowerShell and Bash/CLI can be used, and link to relevant cross-platform documentation.
  • Consider including a table or section summarizing equivalent commands for Windows (PowerShell), Linux (Bash), and macOS.
GitHub Create Pull Request
Azure Resource Manager Relocate Azure Automation to another region ...manager/management/relocation/relocation-automation.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by providing only PowerShell-based examples and instructions for exporting and importing runbooks, without mentioning or providing equivalent guidance for Linux users (e.g., Azure CLI, Bash, or REST API). The use of PowerShell is presented as the primary or sole method for key operations, and no Linux-specific tools or workflows are referenced.
Recommendations
  • Include Azure CLI and Bash examples for exporting and importing runbooks, alongside PowerShell instructions.
  • Reference cross-platform tools (e.g., REST API, Terraform) for automation tasks, and provide sample commands/scripts.
  • Explicitly mention Linux-compatible workflows and tools in each step where PowerShell is referenced.
  • Add a section or note clarifying that all steps can be performed on Linux, and link to relevant Linux documentation.
  • Ensure parity in screenshots and diagrams by showing both Windows and Linux environments where applicable.
GitHub Create Pull Request
Azure Resource Manager Relocate an Azure Cosmos DB NoSQL account to another region ...-manager/management/relocation/relocation-cosmos-db.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation frequently lists Windows-centric tools (Azure PowerShell, Azure portal) before cross-platform or Linux-native options (Azure CLI). In several places, PowerShell is mentioned alongside or before CLI, and the Azure portal (which is OS-agnostic but often associated with Windows workflows) is consistently listed first. There are no explicit Linux-only examples or references to Linux-specific workflows, and no command-line examples are provided to illustrate parity.
Recommendations
  • Alternate the order of tool mentions so that Azure CLI is listed before or alongside Azure PowerShell and Azure portal, especially in step-by-step instructions.
  • Explicitly state that Azure CLI is cross-platform and provide CLI examples for each operation, especially for tasks like creating VNets, subnets, and Cosmos DB accounts.
  • Include Linux shell (bash) command examples where possible, not just references to documentation.
  • Add a section or callout highlighting that all operations can be performed from Linux environments using the Azure CLI.
  • Avoid defaulting to PowerShell or portal-first instructions; strive for equal visibility for Linux-friendly tools.
GitHub Create Pull Request
Azure Resource Manager Relocation guidance for Azure Firewall ...e-manager/management/relocation/relocation-firewall.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively providing PowerShell examples for command-line operations, with no mention of Azure CLI, Bash, or Linux shell equivalents. The use of PowerShell is pervasive throughout the export, modification, and redeployment steps, and references to Windows-centric tools and patterns (e.g., PowerShell cmdlets, Read-Host prompts) are present. There are no Linux-specific instructions or cross-platform alternatives, and PowerShell is presented before any other automation or scripting option.
Recommendations
  • Add Azure CLI and Bash examples alongside PowerShell for all command-line steps, ensuring parity for Linux and macOS users.
  • Explicitly mention that PowerShell examples are suitable for Windows, and provide guidance for users on other platforms.
  • Include cross-platform instructions for exporting, modifying, and deploying ARM templates, such as using Azure CLI or REST API.
  • Avoid using Windows-specific patterns (e.g., Read-Host) in examples, or provide equivalent alternatives for Linux shells.
  • Review related links and ensure they reference cross-platform documentation where available.
GitHub Create Pull Request
Azure Resource Manager Define multiple instances of a property ...es/azure-resource-manager/templates/copy-properties.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy
Summary
The documentation page exhibits Windows bias by referencing Windows-specific VM deployment templates, mentioning Azure PowerShell before Azure CLI, and lacking Linux-focused examples or links. The only example template provided is for deploying Windows VMs, and deployment instructions prioritize PowerShell over CLI or other cross-platform tools.
Recommendations
  • Include example templates for Linux VM deployments alongside Windows examples.
  • Provide links to both Windows and Linux quickstart templates in the 'Example templates' section.
  • Mention Azure CLI and REST API equally or before PowerShell when discussing deployment methods.
  • Add explicit Linux-focused deployment instructions and examples to ensure parity.
  • Review and update links to ensure cross-platform coverage (e.g., link to deploy-CLI.md as well as deploy-powershell.md).
GitHub Create Pull Request
Azure Resource Manager Key Vault secret with template ...zure-resource-manager/templates/key-vault-parameter.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page presents both Azure CLI and PowerShell examples for all command-line operations, but PowerShell is consistently given equal prominence and sometimes appears first in code blocks and references. The page also references Windows-specific scenarios (e.g., installing a certificate from Key Vault on a Windows VM) and includes links and examples that are Windows-centric. There is no explicit mention of Linux-specific patterns, nor are there examples using Linux-native tools or shell scripting. The documentation assumes parity between Azure CLI and PowerShell, but PowerShell is a Windows-first tool, and its heavy inclusion may signal a bias toward Windows environments.
Recommendations
  • Add explicit Bash or shell script examples for Linux users, especially for tasks like secret retrieval and deployment.
  • Include references to Linux VM scenarios (e.g., installing certificates on Linux VMs) alongside Windows VM examples.
  • Clarify that Azure CLI is cross-platform and highlight its use on Linux and macOS, possibly with screenshots or terminal output from those platforms.
  • Avoid referencing Windows-specific tools or scenarios without providing Linux equivalents or alternatives.
  • Consider reordering examples to present Azure CLI (cross-platform) before PowerShell (Windows-centric) in each section.
  • Add a note or section on best practices for Linux users when working with Azure Key Vault and ARM templates.
GitHub Create Pull Request
Azure Resource Manager Templates overview .../articles/azure-resource-manager/templates/overview.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page exhibits moderate Windows bias. PowerShell is mentioned as the primary scripting tool for testing ARM templates (arm-ttk), with no equivalent Bash or Linux-native tool referenced. The authoring tools highlighted are Visual Studio and Visual Studio Code, both of which are strongly associated with Windows (though VS Code is cross-platform, Visual Studio is Windows-only). The CI/CD integration section references Azure DevOps and Visual Studio projects, which are more common in Windows environments. While deployment options include Azure CLI and Bash scripts, PowerShell is often mentioned first or exclusively in some contexts.
Recommendations
  • Include explicit Bash and Azure CLI examples for template testing and deployment, especially where PowerShell is referenced.
  • Mention cross-platform alternatives to Visual Studio for authoring templates, such as VS Code (with emphasis on its Linux support) or other editors.
  • Reference Linux-native CI/CD tools (e.g., GitHub Actions, Jenkins) alongside Azure DevOps and Visual Studio projects.
  • When listing deployment options, alternate the order or explicitly state Linux compatibility for each method.
  • Provide links to Linux-specific documentation or tutorials for ARM template authoring, testing, and deployment.
GitHub Create Pull Request
Azure Resource Manager Convert portal template to template spec ...re-resource-manager/templates/template-spec-convert.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell-based migration instructions and examples, referencing a PowerShell script as the primary automation method, and omitting any equivalent instructions or examples for Linux or cross-platform environments (such as Bash, Azure CLI, or REST API). The manual portal steps are platform-neutral, but all automation guidance is Windows-centric.
Recommendations
  • Provide equivalent migration instructions using Azure CLI or Bash scripts for Linux/macOS users.
  • Include REST API or ARM template-based migration options for cross-platform automation.
  • Explicitly mention platform compatibility for the PowerShell script and suggest alternatives for non-Windows environments.
  • Ensure that examples and tooling references are presented in a platform-neutral order, or offer both Windows and Linux options side-by-side.
GitHub Create Pull Request
Azure Resource Manager Use template deployment scripts | Microsoft Docs ...nager/templates/template-tutorial-deployment-script.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias. PowerShell is the only supported scripting language for deployment scripts in the tutorial, and all inline script examples use PowerShell syntax. References to PowerShell escape characters and output handling are prominent. While Azure CLI examples are provided for some steps, the core deployment script resource only supports PowerShell, with no Bash or Linux shell alternatives. Windows tools and patterns (e.g., Visual Studio Code, PowerShell cmdlets) are mentioned first or exclusively, and there is no guidance for Linux-native scripting or troubleshooting.
Recommendations
  • Add support and examples for Bash scripts in deploymentScripts resources, if supported by the platform.
  • Provide equivalent Bash or shell script examples alongside PowerShell for all steps, especially for deployment script content.
  • Include troubleshooting instructions for Linux environments (e.g., file locations, error handling in Bash).
  • Mention Linux-native editors (e.g., Vim, Nano) and workflows in addition to Visual Studio Code.
  • Clarify platform limitations (e.g., if only PowerShell is supported, explicitly state this and provide guidance for Linux users).
  • Ensure CLI examples are as detailed and prominent as PowerShell examples, and avoid assuming Windows as the default environment.
GitHub Create Pull Request
Azure Resource Manager Template functions - scope ...resource-manager/templates/template-functions-scope.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page focuses on ARM template scope functions and provides JSON-based examples that are platform-neutral. However, in the 'Next steps' section, deployment guidance is linked specifically to Azure PowerShell, a Windows-centric tool, without mention of Linux-friendly alternatives like Azure CLI or Bash scripting. There are no explicit Linux or cross-platform deployment examples, and PowerShell is referenced before any Linux-equivalent tooling.
Recommendations
  • Add links and examples for deploying ARM templates using Azure CLI, which is cross-platform and widely used on Linux.
  • In the 'Next steps' section, provide parity by including guidance for Bash and Azure CLI alongside PowerShell.
  • Where deployment tooling is referenced, avoid listing Windows/PowerShell options first; present CLI and PowerShell together, or in alphabetical order.
  • Explicitly state that the JSON templates and functions are platform-agnostic, and clarify that deployment can be performed from Windows, Linux, or macOS.
  • Consider adding a brief section or table comparing deployment commands across PowerShell, Azure CLI, and Bash to help users choose the best fit for their environment.
GitHub Create Pull Request
Azure Resource Manager Roll back on error to successful deployment .../azure-resource-manager/templates/rollback-on-error.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page presents PowerShell examples before Azure CLI examples, and uses Windows-style paths (e.g., c:\MyTemplates\azuredeploy.json) in PowerShell commands. The PowerShell section is detailed and uses Windows-centric tooling, which may suggest a Windows-first approach. There are no explicit Linux shell examples (e.g., Bash), nor are Linux-specific considerations or file path formats mentioned.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples to avoid Windows-first ordering.
  • Include Linux/Bash shell examples, especially for Azure CLI usage, and use Linux-style file paths (e.g., /home/user/templates/azuredeploy.json) in at least one example.
  • Add a note clarifying that both PowerShell and Azure CLI are cross-platform, and provide links to installation/use on Linux and macOS.
  • Where file paths are shown, provide both Windows and Linux formats, or use environment variables to indicate cross-platform compatibility.
  • Consider including troubleshooting or usage notes relevant to Linux environments (e.g., permissions, shell differences).
GitHub Create Pull Request
Azure Resource Manager Use ARM template test toolkit ...icles/azure-resource-manager/templates/test-toolkit.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation is heavily focused on PowerShell as the only supported method for running the ARM template test toolkit, regardless of platform. Windows is presented first in installation instructions, and all examples (including Linux and macOS) require PowerShell rather than native shell commands or tools. There is no mention of Linux-native alternatives, and the toolkit itself is described as a set of PowerShell scripts, which may not be ideal for Linux users who prefer bash or other shell environments.
Recommendations
  • Provide bash or shell script examples for Linux users, or clarify if PowerShell is the only supported method.
  • Consider developing or documenting a cross-platform CLI wrapper or tool that does not require PowerShell.
  • List Linux installation instructions before Windows, or present all platforms together to avoid Windows-first ordering.
  • Explicitly state the lack of Linux-native alternatives if PowerShell is required, and suggest how Linux users can best integrate PowerShell into their workflows.
  • Document any limitations or differences in PowerShell usage on Linux/macOS compared to Windows, including file path conventions and permissions.
GitHub Create Pull Request
← Previous Page 1 of 52 Next →