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 351-375 of 492 flagged pages
Azure Resource Manager Bring your own storage to create and publish an Azure Managed Application definition ...ions/publish-service-catalog-bring-your-own-storage.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for all critical steps, ensuring cross-platform compatibility. However, PowerShell (typically associated with Windows) examples are consistently presented first in each section, and PowerShell-specific concepts like 'splatting' are explained in detail, while Bash/Linux-specific nuances are only briefly mentioned (e.g., line continuation with '\' and a Git Bash workaround). There are no steps that are Windows-only, but the ordering and depth of explanation show a mild Windows bias.
Recommendations
  • Alternate the order of PowerShell and CLI examples, or present CLI examples first in some sections to balance visibility for Linux/macOS users.
  • Provide more Bash/Linux-specific tips and troubleshooting, similar to the PowerShell splatting explanation.
  • Explicitly mention that all CLI commands work on Linux/macOS and provide links to Bash scripting resources.
  • Where PowerShell-specific concepts are explained (like splatting), offer equivalent Bash scripting advice for CLI users.
GitHub Create Pull Request
Azure Resource Manager What are the resource providers for Azure services ...anager/management/azure-services-resource-providers.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page is largely platform-neutral, listing Azure resource providers and their associated services. However, there is mild Windows bias in the 'Find resource provider' section: PowerShell is presented as an example alongside Azure CLI and Python, and the registration warning references the 'Windows Azure Service Management API'. There are no Linux/macOS-specific examples or tools mentioned, and PowerShell (traditionally Windows-centric) is included before other Linux-native shells like Bash.
Recommendations
  • Add a Bash shell example for finding resource providers, as Bash is the default on most Linux/macOS systems.
  • Clarify that Azure CLI works cross-platform and is recommended for Linux/macOS users.
  • Reword references to 'Windows Azure Service Management API' to simply 'Azure Service Management API' unless the distinction is necessary.
  • Consider mentioning cross-platform compatibility of PowerShell (PowerShell Core) if retaining the PowerShell example.
  • Ensure that examples do not imply Windows is the primary or default platform.
GitHub Create Pull Request
Azure Resource Manager Manage Azure resources by using Azure CLI ...re-resource-manager/management/manage-resources-cli.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Reference
Summary
The documentation page primarily uses Azure CLI examples in a shell-agnostic style (echo/read/variable assignment), which works on both Linux/macOS and Windows. However, there is a notable reference to a Quickstart guide that specifically mentions Visual Studio Code and PowerShell tabs, suggesting a Windows-first approach for template creation. No Linux/macOS-specific tools or patterns are mentioned, and the only external tooling referenced is Windows-centric.
Recommendations
  • Add explicit notes clarifying that the CLI examples work on Linux, macOS, and Windows.
  • Include links or references to Linux/macOS equivalents for template authoring, such as using VS Code on those platforms or other editors.
  • Where external guides are referenced (e.g., Quickstart with Visual Studio Code), ensure Linux/macOS instructions or tabs are present and linked.
  • Avoid referencing PowerShell tabs or guides exclusively; mention Bash or shell alternatives where appropriate.
GitHub Create Pull Request
Azure Resource Manager Lock your Azure resources to protect your infrastructure ...es/azure-resource-manager/management/lock-resources.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides command-line examples for Azure PowerShell before Azure CLI, and the PowerShell section is more detailed and prominent. This ordering and emphasis can create friction for Linux/macOS users, as PowerShell is a Windows-centric tool, while Azure CLI is cross-platform. However, Azure CLI, Python, and REST API examples are present, so Linux users can complete all tasks.
Recommendations
  • Present Azure CLI examples before Azure PowerShell, as CLI is cross-platform and preferred by many Linux/macOS users.
  • Explicitly note that Azure CLI works on Windows, Linux, and macOS, while PowerShell is most common on Windows.
  • Balance the detail and coverage between PowerShell and CLI sections, ensuring parity in example depth and explanation.
  • Consider adding Bash shell script examples for common tasks, as Bash is native to Linux/macOS.
  • Add a short section at the start clarifying tool/platform compatibility for each method.
GitHub Create Pull Request
Azure Resource Manager Manage resource management private links ...ager/management/manage-private-link-access-commands.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for all operations, with REST API calls as a third option. PowerShell is a Windows-centric tool, and its examples are given equal prominence to Azure CLI, which is cross-platform. In each section, Azure CLI examples are shown before PowerShell, which slightly favors Linux/macOS users. However, there are no Linux-specific shell examples (e.g., Bash scripts), nor is there mention of Linux/macOS authentication nuances. The documentation does not reference any Windows-only tools or patterns, but the inclusion of PowerShell throughout may be unnecessary for Linux/macOS users.
Recommendations
  • Add explicit notes confirming Azure CLI works on Linux/macOS and provide links to installation guides for those platforms.
  • Consider including Bash script examples for common tasks, especially for automation scenarios.
  • Clarify that PowerShell Core is available cross-platform, or note that PowerShell examples are primarily for Windows users.
  • Add troubleshooting notes for authentication on Linux/macOS if relevant (e.g., az login differences).
GitHub Create Pull Request
Azure Resource Manager Manage Azure resources by using the REST API ...e-resource-manager/management/manage-resources-rest.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for authentication and resource listing, but PowerShell examples are given equal prominence and are included in all major sections. There are references to using Visual Studio Code and Azure PowerShell for template deployment, which are more commonly associated with Windows environments. However, Linux/macOS users are not blocked from completing any tasks, as Azure CLI and cURL examples are present and sufficient.
Recommendations
  • Ensure that Azure CLI examples are always shown before PowerShell examples, as CLI is cross-platform.
  • Add explicit notes clarifying that Azure CLI and cURL commands work natively on Linux/macOS.
  • Include Bash script examples for multi-step operations (e.g., authentication + resource listing) to demonstrate Linux workflows.
  • When referencing Visual Studio Code, mention alternative editors or clarify cross-platform support.
  • Provide links to Linux/macOS-specific guidance where relevant (e.g., installing Azure CLI on Linux).
GitHub Create Pull Request
Azure Resource Manager What is Azure Resource Manager? ...articles/azure-resource-manager/management/overview.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation mentions PowerShell before Azure CLI when listing ways to create a resource group, and refers to PowerShell as a primary management tool alongside the portal, REST APIs, and SDKs. However, Linux/macOS equivalents (Azure CLI) are also referenced, and no examples or instructions are provided that are Windows-only. There are no exclusive Windows tools or missing Linux examples, but the ordering and mention of PowerShell first may subtly suggest a Windows-centric perspective.
Recommendations
  • List Azure CLI before or alongside PowerShell when mentioning management tools, as CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly state that both PowerShell and Azure CLI are available on all major platforms (Windows, Linux, macOS).
  • Provide example commands for both Azure CLI and PowerShell in future documentation sections.
  • Avoid ordering that implies Windows tools are primary unless there is a technical reason.
GitHub Create Pull Request
Azure Resource Manager Relocate an Azure Cosmos DB NoSQL account to another region ...-manager/management/relocation/relocation-cosmos-db.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page references Azure PowerShell and the Azure portal as primary management tools, with Azure CLI mentioned as an alternative. Windows-centric tools (PowerShell, portal) are listed before cross-platform options (CLI) in several places. No explicit Linux/macOS examples or guidance are provided, and no mention is made of Linux-specific patterns or considerations.
Recommendations
  • Ensure Azure CLI examples and instructions are provided alongside or before PowerShell/portal references, as CLI is cross-platform.
  • Explicitly state that Azure CLI works on Linux/macOS and provide links to installation and usage guides for those platforms.
  • Include screenshots or command snippets from Linux/macOS environments where relevant.
  • Mention any Linux/macOS-specific considerations (e.g., authentication, environment setup) if applicable.
  • Balance the order of tool references so that cross-platform options are not always listed after Windows-centric ones.
GitHub Create Pull Request
Azure Resource Manager Relocate Azure HDInsight clusters to another region ...-manager/management/relocation/relocation-hdinsight.md
Low 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 mild Windows bias by listing Azure PowerShell and portal methods before Linux-friendly Azure CLI in several key sections, and by referencing PowerShell-specific instructions and tools. While Azure CLI is mentioned and supported, PowerShell and portal examples are often presented first, which may create friction for Linux/macOS users. No critical steps are Windows-only, and Linux users can complete all tasks using CLI or Bicep.
Recommendations
  • Present Azure CLI examples before PowerShell and portal methods, or group them together to avoid implicit prioritization.
  • Explicitly mention that Azure CLI and Bicep are fully supported on Linux/macOS, and provide links to installation guides for these platforms.
  • Add notes clarifying that Azure PowerShell is Windows-centric, and recommend Azure CLI for cross-platform scenarios.
  • Ensure all example commands and instructions are available for both CLI and PowerShell, with equal prominence.
  • Where possible, include screenshots or walkthroughs for Linux/macOS environments, not just Windows/portal.
GitHub Create Pull Request
Azure Resource Manager Outputs in ARM templates ...n/articles/azure-resource-manager/templates/outputs.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides both PowerShell and Azure CLI examples for retrieving output values, but the PowerShell example is presented first, which may subtly prioritize Windows users. No exclusive Windows tools or missing Linux/macOS examples are present; Azure CLI is cross-platform and included.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and more accessible to Linux/macOS users.
  • Explicitly mention that Azure CLI works on Windows, Linux, and macOS.
  • Add a note clarifying that PowerShell Core is available cross-platform, if relevant.
  • Ensure future examples and instructions do not default to Windows-first ordering.
GitHub Create Pull Request
Azure Resource Manager Manage personal data associated with Azure Resource Manager ...e-manager/management/resource-manager-personal-data.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation consistently lists Windows PowerShell cmdlets before cross-platform Azure CLI commands when describing how to manage personal data in deployments, resource groups, and tags. This ordering may subtly prioritize Windows workflows and tools, even though equivalent Azure CLI commands are available and suitable for Linux/macOS users.
Recommendations
  • Alternate the order of examples so Azure CLI commands are listed before or alongside PowerShell cmdlets.
  • Explicitly note that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Add a short section clarifying tool/platform compatibility (e.g., 'Azure CLI works on Windows, Linux, and macOS; PowerShell examples are for Windows users').
  • Consider providing bash shell script examples for common tasks to further support Linux users.
GitHub Create Pull Request
Azure Resource Manager Label mission-critical workloads ...ce-manager/management/tag-mission-critical-workload.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation lists Azure PowerShell (a Windows-centric tool) before Azure CLI in the section on how to apply tags, and includes a direct link to PowerShell guidance. While Azure CLI is also mentioned, PowerShell is given precedence, which may suggest a Windows-first approach. No explicit Linux/macOS examples or references are provided, and no Linux-specific tools or shell examples are shown.
Recommendations
  • List Azure CLI before Azure PowerShell, as CLI is cross-platform and more commonly used on Linux/macOS.
  • Explicitly mention that Azure CLI and Terraform are cross-platform and suitable for Linux/macOS users.
  • Provide example commands for both Azure CLI and PowerShell, or default to CLI for broader compatibility.
  • Include a note clarifying that all tagging approaches (except PowerShell) work on Linux/macOS.
  • Consider adding a section or examples specifically for Linux/macOS users, highlighting CLI and automation options.
GitHub Create Pull Request
Azure Resource Manager Use tags to organize your Azure resources and management hierarchy ...les/azure-resource-manager/management/tag-resources.md
Low 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 demonstrates mild Windows bias by referencing Azure PowerShell and REST API as primary tools for tag operations, and by mentioning Azure PowerShell before Azure CLI in several places. The 'Required access' section specifically highlights Azure PowerShell support, while Linux/macOS-friendly tools like Azure CLI are mentioned only in the 'Next steps' section and not in operational examples or access descriptions. No explicit Linux/macOS examples or parity guidance are provided.
Recommendations
  • Explicitly mention Azure CLI alongside Azure PowerShell in all sections describing tag operations, especially in 'Required access' and operational guidance.
  • Provide example commands for both Azure PowerShell and Azure CLI when describing how to apply, update, or retrieve tags.
  • Clarify that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Ensure that tool references are presented in a neutral or alternating order (e.g., 'Azure CLI and Azure PowerShell') rather than consistently listing Windows-centric tools first.
  • Add a brief note or section highlighting Linux/macOS support and parity for tag management tasks.
GitHub Create Pull Request
Azure Resource Manager Azure resource providers and types ...rce-manager/management/resource-providers-and-types.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page shows a mild Windows bias by referencing 'Windows Azure Service Management API' in an important security note and listing Azure PowerShell (a Windows-centric tool) before Azure CLI and Python. The portal instructions are platform-neutral, but the ordering and mention of Windows-specific APIs/tools may subtly prioritize Windows users.
Recommendations
  • Replace or supplement references to 'Windows Azure Service Management API' with platform-neutral terminology or clarify its relevance for non-Windows users.
  • Present Azure CLI examples before or alongside PowerShell, as CLI is cross-platform.
  • Add explicit notes that Azure PowerShell is available on Linux/macOS, or link to installation guides for those platforms.
  • Ensure all tool references and examples are clearly marked as cross-platform where applicable.
  • Review and update any terminology that could be interpreted as Windows-specific unless strictly necessary.
GitHub Create Pull Request
Azure Resource Manager Tag support for Azure resources ...icles/azure-resource-manager/management/tag-support.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page is primarily a reference table listing Azure resource types and their support for tags. However, in the few places where command-line tooling is mentioned, Windows-centric tools (PowerShell) are referenced first or exclusively, such as 'Set-AzVm -Generalized' before the cross-platform 'az vm generalize'. There are also references to Windows-specific tools and patterns (e.g., PowerShell cmdlets) without equivalent Linux/macOS CLI or scripting examples. No Linux-specific tools or examples are provided, and Windows terminology appears first in notes.
Recommendations
  • When referencing command-line tools, always provide both PowerShell and Azure CLI examples, and consider listing Azure CLI (cross-platform) first.
  • Add explicit Linux/macOS instructions or notes where PowerShell is mentioned.
  • Audit for other sections that may mention Windows tools or patterns and ensure Linux/macOS parity.
  • Where possible, use platform-neutral language and tooling (e.g., Azure CLI, REST API) as the primary example.
GitHub Create Pull Request
Azure Resource Manager Deploy multiple instances of resources ...les/azure-resource-manager/templates/copy-resources.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation mentions Azure PowerShell before Azure CLI when listing supported tools for zero-count deployments, which may subtly prioritize Windows tooling. However, examples and instructions are platform-neutral, and both CLI and PowerShell are referenced. No PowerShell-specific examples or Windows-only tools are present.
Recommendations
  • List Azure CLI before PowerShell when describing supported tools, as CLI is cross-platform and more commonly used on Linux/macOS.
  • Explicitly state that both Azure CLI and PowerShell are available on all major platforms.
  • Provide links to platform-specific instructions for deploying ARM templates using CLI on Linux/macOS and PowerShell on Windows.
  • Add a brief note clarifying that all shown JSON templates are platform-agnostic.
GitHub Create Pull Request
Azure Resource Manager Use Azure Resource Manager templates to deploy resources to resource groups ...resource-manager/templates/deploy-to-resource-group.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment operations. However, in several sections, PowerShell examples are presented before CLI examples, and PowerShell is given its own dedicated tab. This ordering and prominence may subtly favor Windows users, as PowerShell is primarily associated with Windows, despite its cross-platform availability. There are no Linux-specific tools or shell examples (e.g., Bash scripts), but the CLI examples are suitable for Linux/macOS users. No critical functionality is missing for Linux/macOS users.
Recommendations
  • Present Azure CLI examples before PowerShell examples, as CLI is natively cross-platform and more familiar to Linux/macOS users.
  • Explicitly mention that Azure CLI commands work on Linux/macOS/Windows, while PowerShell is available cross-platform but may require additional installation steps on non-Windows systems.
  • Add a brief note or section highlighting Linux/macOS usage, such as running commands in Bash or using Azure Cloud Shell.
  • Ensure parity in example depth and clarity between CLI and PowerShell sections.
GitHub Create Pull Request
Azure Resource Manager Define multiple instances of a variable ...les/azure-resource-manager/templates/copy-variables.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation mentions Azure PowerShell before Azure CLI when listing supported tools for zero-count deployments, and the 'Next steps' section links only to a PowerShell deployment guide, omitting equivalent Linux/macOS-friendly CLI or REST API deployment guides. No explicit PowerShell-only examples are present, but the ordering and linking show a subtle Windows-first bias.
Recommendations
  • List Azure CLI before Azure PowerShell when mentioning supported tools, or present them together without implied priority.
  • In the 'Next steps' section, add links to equivalent guides for deploying ARM templates using Azure CLI and REST API, ensuring Linux/macOS users have clear, direct resources.
  • Wherever deployment tooling is discussed, clarify cross-platform support and provide examples for both CLI and PowerShell.
GitHub Create Pull Request
Azure Resource Manager Azure deployment templates with Azure CLI – Azure Resource Manager | Microsoft Docs ...rticles/azure-resource-manager/templates/deploy-cli.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation generally uses Azure CLI commands, which are cross-platform, but several sections show a Windows-first bias. Examples for setting variables and passing parameters explicitly mention Windows Command Prompt (CMD) and PowerShell formats, often after Bash, but with more detail and escape instructions. There are no Linux-specific tools or patterns missing, but Windows usage is called out more frequently and with more explanation. No critical steps are Windows-only, but Linux/macOS users may need to infer their own equivalents for some variable/parameter handling.
Recommendations
  • Provide explicit Bash and Linux/macOS examples for variable assignment and parameter passing, especially where Windows-specific escaping is discussed.
  • When discussing differences between shells, present Bash/Linux examples first or equally alongside Windows examples.
  • Clarify that Azure CLI is cross-platform and note any OS-specific caveats up front.
  • Add notes or links for Linux/macOS users about common shell differences and troubleshooting tips.
GitHub Create Pull Request
Azure Resource Manager Deploy resources to tenant ...s/azure-resource-manager/templates/deploy-to-tenant.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for key deployment and role assignment tasks, but PowerShell is presented first in the permissions section and is referenced heavily. There are no explicit Linux/macOS-specific instructions or notes, and no mention of platform-specific caveats. The CLI examples are present, but Windows/PowerShell patterns are slightly prioritized.
Recommendations
  • Ensure Azure CLI examples are presented before or alongside PowerShell examples, as CLI is cross-platform.
  • Add explicit notes clarifying that Azure CLI works on Linux/macOS and Windows, and that PowerShell Core is available cross-platform.
  • Include links or references to Linux/macOS setup guides for Azure CLI and PowerShell Core.
  • Where possible, add screenshots or shell prompts that reflect Linux/macOS environments.
  • Avoid using Windows-specific terminology (e.g., backticks for line continuation in PowerShell) without clarifying alternatives for other platforms.
GitHub Create Pull Request
Azure Resource Manager Automatic deletions from deployment history ...urce-manager/templates/deployment-history-deletions.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation consistently presents PowerShell (Windows-centric) examples before Azure CLI (cross-platform) and REST. PowerShell is featured prominently, with detailed command blocks and references, potentially signaling a preference for Windows tooling. However, Azure CLI and REST examples are provided for all major operations, ensuring Linux/macOS users can follow along.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and more widely used outside Windows.
  • Explicitly state that Azure CLI commands work on Linux/macOS and provide any necessary environment setup notes.
  • Balance the depth of explanation for PowerShell and CLI, ensuring both are equally detailed.
  • Consider adding Bash script examples where appropriate, especially for lock deletion and feature registration tasks.
GitHub Create Pull Request
Azure Resource Manager Azure Resource Manager deployment modes ...s/azure-resource-manager/templates/deployment-modes.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides deployment mode examples for both Azure PowerShell and Azure CLI, but PowerShell is presented first and uses a Windows-style file path (c:\MyTemplates\storage.json). There are no explicit Linux/macOS examples or notes about cross-platform usage, and the CLI example is shown after PowerShell. The documentation references Azure PowerShell and CLI together when discussing REST API versions, but does not clarify platform differences or provide parity guidance.
Recommendations
  • Alternate the order of PowerShell and CLI examples, or present CLI examples first to avoid implicit Windows-first bias.
  • Use platform-neutral file paths in examples (e.g., ./MyTemplates/storage.json) or provide both Windows and Linux/macOS variants.
  • Explicitly mention that Azure CLI is cross-platform and provide guidance for Linux/macOS users where relevant.
  • Ensure that links to further deployment documentation include both PowerShell and CLI options, and clarify platform compatibility.
  • Add a note that both PowerShell and CLI commands can be run on Windows, Linux, and macOS, with installation links for each.
GitHub Create Pull Request
Azure Resource Manager Tutorial - Deploy a local Azure Resource Manager template ...anager/templates/deployment-tutorial-local-template.md
Low 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 mild Windows bias: Windows-specific installation instructions are listed before Linux/macOS, and Azure PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, despite CLI being more cross-platform. Visual Studio Code is recommended as the editor, which is cross-platform, but no mention is made of Linux-native editors. The CLI examples are stated to be for Bash, but no explicit Linux/macOS shell commands or troubleshooting tips are provided. The Azure portal instructions are generic and not OS-specific.
Recommendations
  • List installation instructions for Azure CLI on Linux/macOS before Windows, or group them together to avoid Windows-first ordering.
  • Emphasize Azure CLI as the default/cross-platform tool, with PowerShell as an alternative for Windows users.
  • Include explicit Linux/macOS shell commands and troubleshooting tips (e.g., file permissions, path formats).
  • Mention Linux-native editors (e.g., Vim, Nano) as alternatives to Visual Studio Code.
  • Clarify that all CLI examples work on Linux/macOS, and provide any necessary OS-specific notes.
GitHub Create Pull Request
Azure Resource Manager Key Vault secret with template ...zure-resource-manager/templates/key-vault-parameter.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents both Azure CLI and PowerShell examples for all command-line operations, but PowerShell examples are consistently shown immediately after CLI, and the page metadata includes 'devx-track-azurepowershell' before 'devx-track-azurecli'. There is a subtle Windows-first ordering, and PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, which is more cross-platform. No Linux/macOS-specific tools or shell patterns are mentioned, and there are no explicit Linux/macOS examples or troubleshooting notes.
Recommendations
  • Explicitly state that both Azure CLI and PowerShell are cross-platform, and clarify which is recommended for Linux/macOS users.
  • Add notes or links for Linux/macOS users regarding installation and usage of Azure CLI and PowerShell on those platforms.
  • Consider listing Azure CLI examples first, as it is the default tool for cross-platform scenarios.
  • Include troubleshooting or environment setup tips for Linux/macOS users (e.g., file path formats, shell differences).
  • If possible, add bash script examples or highlight differences in command usage on Linux/macOS.
GitHub Create Pull Request
Azure Resource Manager Templates overview .../articles/azure-resource-manager/templates/overview.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools
Summary
The documentation page is generally cross-platform and does not show strong Windows bias in its main content or examples. However, there are two notable areas of mild bias: (1) the ARM template tool kit (arm-ttk) is highlighted as a PowerShell script, with no mention of Linux/macOS alternatives or usage guidance, and (2) authoring tools include Visual Studio (Windows-only) alongside Visual Studio Code, without mentioning Linux/macOS editors or parity. There are no deployment examples that favor Windows or PowerShell, and deployment options include Azure CLI and REST API, which are cross-platform.
Recommendations
  • Clarify that arm-ttk can be run on Linux/macOS via PowerShell Core, or provide alternative validation tools for non-Windows users.
  • When listing authoring tools, mention cross-platform editors (e.g., VS Code, JetBrains IDEs) and clarify Visual Studio is Windows-only.
  • If PowerShell scripts are referenced, note compatibility with PowerShell Core on Linux/macOS.
  • Consider providing explicit Linux/macOS usage notes where Windows-centric tools are mentioned.
GitHub Create Pull Request
← Previous Page 15 of 20 Next →