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 576-600 of 1281 flagged pages
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/secure-template-with-sas-token.md ...ce-manager/templates/secure-template-with-sas-token.md
High Priority View Details →
Scanned: 2025-08-19 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation consistently presents PowerShell (typically used on Windows) examples before Azure CLI (cross-platform) examples. File paths in PowerShell examples use Windows-style paths (e.g., c:\Templates\azuredeploy.json), and there is no explicit mention or example of uploading templates from a Linux or macOS environment (e.g., using Unix-style paths). The Azure CLI section references Bash in Cloud Shell but does not provide parity for local Linux/macOS environments or address differences in shell syntax. There are no Linux-specific troubleshooting notes or examples.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI (cross-platform) first.
  • In upload examples, provide both Windows (c:\...) and Linux/macOS (~/Templates/...) file path examples.
  • Explicitly mention that Azure CLI commands work on Linux/macOS and provide any necessary syntax adjustments (e.g., for date/time formatting).
  • Add notes or tabs for Linux/macOS users where shell syntax or environment variables may differ.
  • In 'Next steps', include links to documentation for deploying templates using Azure CLI on Linux/macOS.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/install.md .../main/articles/azure-resource-manager/bicep/install.md
High Priority View Details →
Scanned: 2025-08-11 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific tools (Visual Studio, PowerShell, Chocolatey, Winget) are prominently featured, and Windows installation methods are often listed before or in more detail than Linux/macOS equivalents. PowerShell is used for manual installation examples, and Visual Studio (Windows-only) is given equal or greater prominence than cross-platform editors. While Linux and macOS instructions are present and reasonably detailed, Windows tools and patterns are more heavily emphasized.
Recommendations
  • Ensure that Linux and macOS installation instructions are always presented before or alongside Windows instructions, not after.
  • Provide Bash or shell-based manual installation examples before PowerShell examples, and ensure parity in detail and troubleshooting.
  • Balance the prominence of Visual Studio (Windows-only) with Visual Studio Code (cross-platform) in authoring recommendations.
  • List cross-platform package managers (e.g., Homebrew for macOS/Linux) with equal visibility to Windows package managers (Chocolatey, Winget).
  • Where possible, use cross-platform commands and terminology (e.g., 'terminal' instead of 'command shell') and avoid assuming Windows as the default environment.
  • Explicitly mention any differences or limitations for Linux/macOS users in relevant sections, not just in notes or warnings.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/bicep-functions-files.md .../azure-resource-manager/bicep/bicep-functions-files.md
High Priority View Details →
Scanned: 2025-08-11 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page provides an example that loads and deploys a PowerShell script (myscript.ps1) using the 'AzurePowerShell' deployment script kind, but does not provide equivalent examples for Linux shell scripts or Bash. There is a focus on Windows tooling (PowerShell) without mention of Linux-native alternatives, and no Linux/Bash script examples are given.
Recommendations
  • Add parallel examples that demonstrate loading and deploying Bash or shell scripts (e.g., myscript.sh) using the 'AzureCLI' deployment script kind.
  • Explicitly mention that the file loading functions are cross-platform and can be used with both Windows (PowerShell) and Linux (Bash) scripts.
  • Where PowerShell is referenced, provide Linux/Bash alternatives either alongside or before the Windows example to ensure parity.
  • Clarify in remarks or examples that file paths and encodings are compatible with both Windows and Linux environments.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/deployment-script-bicep.md ...zure-resource-manager/bicep/deployment-script-bicep.md
High Priority View Details →
Scanned: 2025-08-11 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. While it claims support for both Azure CLI (Linux) and Azure PowerShell (Windows), there is a consistent pattern of presenting PowerShell examples and tooling either before or alongside CLI/Linux equivalents, sometimes with more detail. Script deployment and management examples are often shown with Azure PowerShell commands, and there is no explicit example of running a native Linux shell script outside of Azure CLI context. Additionally, the deployment instructions for running Bicep files use Azure PowerShell exclusively, with no Bash or cross-platform CLI alternative provided. The documentation also references Windows-centric tools and patterns (e.g., PowerShell, Connect-AzAccount) more prominently than Linux-native equivalents.
Recommendations
  • Provide Bash or shell script examples for deploying Bicep files, not just Azure PowerShell.
  • When listing management commands (e.g., for deploying, monitoring, or troubleshooting), present Azure CLI (Linux/cross-platform) examples before or alongside PowerShell, not after.
  • Include explicit Linux-native script examples (e.g., Bash scripts) outside of the Azure CLI context, demonstrating how to interact with the deployment script resource from a Linux environment.
  • Balance the use of PowerShell and CLI examples throughout the documentation, ensuring that Linux users see their workflows represented equally.
  • Reference Linux-native authentication patterns (e.g., az login) with equal prominence as Connect-AzAccount.
  • Where possible, clarify that both Windows and Linux environments are supported, and provide parity in troubleshooting and development environment setup instructions.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/migrate-blueprint.md ...cles/azure-resource-manager/bicep/migrate-blueprint.md
High Priority View Details →
Scanned: 2025-08-11 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell-specific instructions and links (such as the export process), mentioning Azure PowerShell before Azure CLI, and omitting explicit Linux or cross-platform command examples. There are no CLI or Bash examples, and the export instructions point to a PowerShell-centric guide.
Recommendations
  • Provide Azure CLI examples alongside or before PowerShell instructions for exporting blueprint definitions and configuring deployment stacks.
  • Update links and references to include both PowerShell and CLI documentation, or provide a cross-platform export workflow.
  • Explicitly mention that all steps can be performed on Linux/macOS using Azure CLI, and provide relevant command examples.
  • Ensure that tool and workflow recommendations are platform-neutral unless a feature is truly Windows-only.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/deployment-script-vnet-private-endpoint.md ...nager/bicep/deployment-script-vnet-private-endpoint.md
High Priority View Details →
Scanned: 2025-08-11 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation exclusively demonstrates the use of Azure PowerShell (via 'kind: AzurePowerShell', 'azPowerShellVersion', and a PowerShell scriptContent) for deployment scripts, with no mention or example of Bash or Linux-native scripting. There are no Linux/Bash equivalents or cross-platform guidance, and the PowerShell approach is presented as the default/only method.
Recommendations
  • Provide parallel examples using 'kind: AzureCLI' and Bash scripting in the deployment script resource.
  • Explicitly mention that both PowerShell and Bash are supported, and link to documentation for both.
  • Show how to set 'azCliVersion' and provide a sample Bash scriptContent for Linux users.
  • Consider a section comparing PowerShell and Bash usage, and when to use each.
  • Ensure that any references to tooling or scripting are balanced between Windows and Linux environments.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/createuidefinition-test-cases.md ...rce-manager/templates/createuidefinition-test-cases.md
High Priority View Details →
Scanned: 2025-08-11 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Osplatform Windows Only
Summary
The documentation page is generally neutral regarding platform-specific instructions, as it focuses on JSON schema and ARM template validation. However, there is a subtle Windows bias in the examples: several JSON snippets specify "osPlatform": "Windows" without mentioning Linux or providing Linux examples. Controls such as Microsoft.Compute.CredentialsCombo, Microsoft.Compute.UserNameTextBox, and Microsoft.Compute.SizeSelector are shown only with Windows as the osPlatform. No Linux or cross-platform examples are provided, and there is no discussion of Linux-specific considerations or parity.
Recommendations
  • Include examples where "osPlatform" is set to "Linux" or both "Windows" and "Linux" to demonstrate cross-platform support.
  • Add notes or examples that highlight any differences or considerations when targeting Linux VMs in createUiDefinition.json.
  • Where possible, provide parallel examples for both Windows and Linux, especially for controls like credentials, username, and VM size selectors.
  • Clarify in the documentation whether the test toolkit and controls are equally applicable to Linux, and if not, specify any limitations.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/deployment-script-develop.md ...re-resource-manager/bicep/deployment-script-develop.md
High Priority View Details →
Scanned: 2025-08-11 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Azure CLI (Bash) and Azure PowerShell examples throughout, but there is a subtle Windows bias. PowerShell is consistently presented as an equal alternative to Bash/CLI, and in some cases, Windows-specific tools and APIs (such as Connect-AzAccount and CommandLineToArgvW) are referenced without Linux equivalents or context. The documentation also references Windows-centric patterns (e.g., PowerShell error handling, Start-Sleep) and APIs before or more prominently than their Linux/Bash counterparts. There are no explicit Linux-only examples or guidance, and the documentation assumes familiarity with PowerShell and Windows scripting conventions.
Recommendations
  • Where Windows-specific APIs or tools are mentioned (e.g., Connect-AzAccount, CommandLineToArgvW), provide equivalent Linux/Bash context or explain their relevance for cross-platform users.
  • When discussing error handling, provide Bash/Linux best practices (e.g., set -e, trap) alongside PowerShell's $ErrorActionPreference.
  • Clarify that both Bash (for Azure CLI) and PowerShell (for Azure PowerShell) are supported equally, and avoid implying that PowerShell is the default or preferred scripting environment.
  • Include explicit notes or examples for Linux users where behaviors may differ (e.g., file paths, environment variable access, script extensions).
  • Consider adding a section or callout for cross-platform scripting tips, highlighting any differences or caveats for Linux vs. Windows users.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/install.md .../main/articles/azure-resource-manager/bicep/install.md
High Priority View Details →
Scanned: 2025-08-07 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates some Windows bias, particularly in the ordering and emphasis of installation instructions and tooling. Windows-specific tools (Visual Studio, PowerShell, Chocolatey, Winget) are highlighted, and Windows instructions often appear before or more prominently than Linux/macOS equivalents. PowerShell is used heavily in Windows manual install examples, and Visual Studio (a Windows-only IDE) is given a dedicated section before cross-platform alternatives. However, Linux and macOS installation steps are present and reasonably detailed.
Recommendations
  • Ensure that cross-platform and Linux/macOS instructions are presented with equal prominence and ordering as Windows instructions.
  • Avoid presenting Windows-specific tools (e.g., Visual Studio, PowerShell, Chocolatey, Winget) before cross-platform or Linux-native alternatives unless there is a clear user base justification.
  • Provide CLI examples using Bash (or sh) for Linux/macOS wherever PowerShell is used for Windows, and vice versa.
  • Consider adding a summary table at the top that clearly indicates cross-platform support and links to OS-specific sections, rather than leading with Windows-centric tools.
  • Where possible, recommend cross-platform editors (e.g., VS Code) before Windows-only editors (e.g., Visual Studio), or present them in parallel.
  • Balance the depth and detail of installation steps across all platforms to avoid the perception of Windows as the 'default' environment.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/migrate-blueprint.md ...cles/azure-resource-manager/bicep/migrate-blueprint.md
High Priority View Details →
Scanned: 2025-08-07 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation references Azure PowerShell and links to a PowerShell-specific guide for exporting blueprint definitions, without mentioning or providing equivalent Azure CLI (cross-platform) instructions. The mention of Azure CLI comes only later and is not accompanied by examples or links. No Linux- or cross-platform-specific guidance or examples are provided.
Recommendations
  • Provide Azure CLI commands and examples alongside or before PowerShell instructions for all steps, especially for exporting blueprint definitions.
  • Link to both PowerShell and Azure CLI documentation for relevant tasks, ensuring parity.
  • Explicitly mention that all steps can be performed on Linux, macOS, and Windows, and clarify any platform-specific considerations.
  • Include sample commands or scripts using Azure CLI for key migration steps.
  • Avoid linking exclusively to PowerShell guides; offer a balanced set of resources for both Windows and Linux users.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/createuidefinition-test-cases.md ...rce-manager/templates/createuidefinition-test-cases.md
High Priority View Details →
Scanned: 2025-08-07 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Osplatform Windows Only
Summary
The documentation page is largely neutral in terms of platform-specific instructions, as it focuses on JSON templates and UI definition files for Azure Resource Manager, which are platform-agnostic. However, there is a subtle Windows bias in the use of the 'osPlatform' property, which is always set to 'Windows' in all provided examples, and in the use of Windows-centric control types (e.g., Microsoft.Compute.UserNameTextBox with osPlatform: Windows, and VM size selectors with osPlatform: Windows). There are no examples or mentions of Linux or cross-platform scenarios, nor are Linux-specific values or guidance provided.
Recommendations
  • Include examples where the 'osPlatform' property is set to 'Linux' or 'cross-platform', especially for controls like user name, password, and VM size selectors.
  • Add notes or examples that show how to handle Linux-specific requirements or differences in createUiDefinition.json files.
  • Where appropriate, mention that the controls and templates can be used for both Windows and Linux VMs, and provide parity in documentation.
  • If there are differences in validation, constraints, or default values between Windows and Linux, document these explicitly.
  • Ensure that references to control types or properties do not imply Windows is the only or primary supported platform.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/deployment-script-develop.md ...re-resource-manager/bicep/deployment-script-develop.md
High Priority View Details →
Scanned: 2025-08-07 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is featured as a first-class scripting option alongside Azure CLI throughout, and several explanations and code comments reference Windows-specific tools, APIs, or conventions. For example, the documentation references the Windows API CommandLineToArgvW for argument parsing, and the use of Connect-AzAccount is described in a way that assumes PowerShell familiarity. The PowerShell examples are as prominent as the CLI (Bash) ones, but some explanations (such as error handling and identity management) are more detailed for PowerShell. There is also a tendency to mention PowerShell or Windows-related tools before their Linux/Bash equivalents, and some terminology (e.g., 'cmdlet', 'Connect-AzAccount') is Windows-centric.
Recommendations
  • Wherever PowerShell-specific tools or APIs are mentioned (e.g., Connect-AzAccount, CommandLineToArgvW), provide equivalent Linux/Bash or cross-platform alternatives or explanations.
  • Ensure that CLI (Bash) and PowerShell examples are equally detailed, especially in sections about error handling, identity management, and output handling.
  • When referencing system calls or APIs (such as CommandLineToArgvW), clarify their relevance in a cross-platform context and, if possible, describe the behavior in platform-neutral terms.
  • Review the order of presentation so that Linux/Bash/CLI examples are not consistently secondary to PowerShell/Windows ones.
  • Avoid Windows-centric terminology (like 'cmdlet') without also referencing the equivalent Bash/CLI concepts.
  • Explicitly state that both Bash and PowerShell scripts are supported on Linux-based containers, and clarify any platform-specific behaviors or limitations.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/createuidefinition-test-cases.md ...rce-manager/templates/createuidefinition-test-cases.md
High Priority View Details →
Scanned: 2025-08-04 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias. Several JSON examples for UI controls specify the 'osPlatform' property as 'Windows', and controls such as 'Microsoft.Compute.CredentialsCombo', 'Microsoft.Compute.UserNameTextBox', and 'Microsoft.Compute.SizeSelector' are repeatedly shown with 'osPlatform': 'Windows'. There are no examples or mentions of Linux or cross-platform scenarios, nor are Linux-specific values or considerations discussed. This may give the impression that the toolkit or UI definitions are primarily intended for Windows environments.
Recommendations
  • Include examples where 'osPlatform' is set to 'Linux' or both 'Windows' and 'Linux', especially for controls like user name, credentials, and VM size selectors.
  • Discuss any differences or considerations for Linux-based deployments in the test cases, such as username restrictions or password requirements.
  • Add at least one example for each relevant test case that demonstrates a Linux scenario, or explicitly state if the toolkit is Windows-only.
  • Where 'osPlatform' is used, clarify that it can accept 'Linux' and provide guidance for Linux-specific values.
  • Review the documentation for implicit assumptions about Windows and update language to be more platform-neutral where possible.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/install.md .../main/articles/azure-resource-manager/bicep/install.md
High Priority View Details →
Scanned: 2025-08-04 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. Windows tools and patterns (such as PowerShell, Chocolatey, and Winget) are described in more detail and appear before or more prominently than Linux equivalents. PowerShell is used for manual installation on Windows, and the Visual Studio (Windows-only) workflow is given equal prominence to the cross-platform Visual Studio Code workflow. In some sections, Windows installation methods are listed last, but the Windows-specific tools and scripting (PowerShell) are more detailed and varied than for Linux/macOS. Linux and macOS instructions are present and technically complete, but Windows-specific tooling and patterns are more deeply integrated.
Recommendations
  • Ensure that Linux and macOS installation instructions are as detailed and varied as Windows (e.g., mention package managers like apt, yum, or snap if available, not just manual download).
  • Where multiple installation methods are listed, present Linux/macOS options before or alongside Windows options, rather than after.
  • Provide Bash or shell script examples for Linux/macOS with the same level of detail as PowerShell for Windows.
  • Highlight cross-platform tools (like Visual Studio Code and Azure CLI) before platform-specific tools (like Visual Studio or PowerShell).
  • Where possible, avoid assuming PowerShell as the default scripting environment for manual installation; provide equivalent Bash scripts for Linux/macOS.
  • Consider adding a summary table that clearly indicates which methods are cross-platform and which are Windows-only.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/migrate-blueprint.md ...cles/azure-resource-manager/bicep/migrate-blueprint.md
High Priority View Details →
Scanned: 2025-08-04 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing PowerShell-specific instructions and links (e.g., 'import-export-ps.md'), mentioning Azure PowerShell before Azure CLI, and omitting explicit Linux or cross-platform command-line examples. There are no CLI or Bash examples, and PowerShell is implicitly prioritized.
Recommendations
  • Provide parallel Azure CLI (cross-platform) instructions and links wherever PowerShell is mentioned.
  • Update references such as 'import-export-ps.md' to include or point to CLI/Bash/Linux-friendly guides.
  • Explicitly mention that both Azure CLI and PowerShell can be used for migration tasks, and provide examples for both.
  • Ensure that all steps referencing command-line tools include both Windows and Linux/macOS compatible commands.
  • Review sample code and instructions to ensure they are platform-neutral or include notes for both environments.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/deployment-script-develop.md ...re-resource-manager/bicep/deployment-script-develop.md
High Priority View Details →
Scanned: 2025-08-03 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI (Bash) and Azure PowerShell examples for all major scenarios, which is positive for cross-platform parity. However, there are subtle signs of Windows bias: (1) Windows/PowerShell tools and patterns are mentioned first in several places, such as the use of CommandLineToArgvW (a Windows API) for argument parsing and Connect-AzAccount for authentication; (2) PowerShell is given equal or greater prominence than Bash/CLI, despite Bash being more common on Linux; (3) Some explanations and troubleshooting tips reference PowerShell-specific constructs (like $ErrorActionPreference and Start-Sleep) before or instead of Bash equivalents; (4) The documentation references Windows-specific APIs and tools (e.g., CommandLineToArgvW) without always providing Linux context.
Recommendations
  • When describing argument parsing, mention both Windows (CommandLineToArgvW) and the equivalent Linux/Bash parsing mechanisms, or clarify that the underlying container is Linux-based and explain how arguments are parsed in that context.
  • When referencing authentication (e.g., Connect-AzAccount), provide equivalent CLI/Bash commands for Linux users, such as 'az login --identity'.
  • For error handling and troubleshooting, provide Bash equivalents to PowerShell constructs (e.g., explain 'set -e' and 'trap' in Bash alongside $ErrorActionPreference in PowerShell).
  • When listing system environment variables or output handling, clarify any differences in behavior between Linux (Bash) and Windows (PowerShell) shells.
  • Wherever possible, present CLI/Bash examples before PowerShell, or alternate the order, to avoid reinforcing a Windows-first perspective.
  • Review all references to Windows-specific APIs or tools and ensure Linux users are not left without context or alternatives.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/install.md .../main/articles/azure-resource-manager/bicep/install.md
High Priority View Details →
Scanned: 2025-08-03 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific tools (Visual Studio, PowerShell, Chocolatey, Winget) are prominently featured, and Windows installation instructions are often more detailed or appear before Linux/macOS equivalents. PowerShell is used for manual installation on Windows, and the Visual Studio workflow is described in detail, while Linux and macOS workflows are less emphasized. However, Linux and macOS installation steps are present and reasonably complete.
Recommendations
  • Ensure parity in detail and order: Present Linux, macOS, and Windows installation instructions in the same level of detail and in a consistent order (e.g., always Linux, macOS, then Windows, or vice versa, but consistently).
  • Add Linux/macOS equivalents for Windows tools: Where Windows-specific tools like Chocolatey or Winget are mentioned, consider mentioning Homebrew for macOS and common package managers for Linux (e.g., apt, yum, or snap) if available.
  • Balance editor recommendations: Visual Studio is Windows-only; consider highlighting cross-platform editors (e.g., Visual Studio Code) more prominently and clarify platform limitations of Visual Studio.
  • Provide shell examples for all platforms: Where PowerShell is used for Windows, ensure Bash or shell equivalents are provided for Linux/macOS where relevant.
  • Avoid Windows-first ordering: When listing installation options or steps, avoid always listing Windows first unless there is a strong user base justification; consider rotating or alphabetizing.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/migrate-blueprint.md ...cles/azure-resource-manager/bicep/migrate-blueprint.md
High Priority View Details →
Scanned: 2025-08-03 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing PowerShell-specific instructions and links (such as 'import-export-ps.md'), and by mentioning Azure PowerShell before Azure CLI when discussing configuration. There are no explicit Linux or cross-platform CLI examples or references, and no mention of Bash or Linux-specific workflows.
Recommendations
  • Provide equivalent Azure CLI (cross-platform) instructions and links alongside or before PowerShell references.
  • Update references such as 'import-export-ps.md' to include or point to CLI-based export/import documentation.
  • Explicitly mention that all steps can be performed on Linux, macOS, and Windows, and provide sample commands for each where applicable.
  • Ensure that tool-agnostic language is used when possible, and avoid defaulting to Windows/PowerShell-centric terminology.
  • Add a section or callout for Linux/macOS users, highlighting any differences or confirming parity.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/move-resource-group-and-subscription.md ...ger/management/move-resource-group-and-subscription.md
High Priority View Details →
Scanned: 2025-08-01 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Azure PowerShell is given equal or greater prominence compared to Azure CLI, and PowerShell-specific tooling and syntax are used throughout. There are no explicit Linux/Bash examples or notes about cross-platform usage, and PowerShell is presented as a primary automation tool. In some cases, PowerShell appears before or alongside CLI, but Linux/Bash scripting is not addressed. The examples for scripting (outside of Python) assume a Windows/PowerShell environment, and there is no mention of Linux-specific considerations or terminal environments.
Recommendations
  • Explicitly state that Azure CLI commands work cross-platform (Windows, macOS, Linux) and provide Bash-specific examples where appropriate.
  • When showing scripting examples, provide both PowerShell and Bash shell script versions, especially for automation scenarios.
  • Clarify when a command or script is intended for PowerShell (Windows/macOS/Linux) versus Bash (Linux/macOS/Windows with WSL).
  • Avoid using PowerShell variable assignment syntax ($var=...) in Azure CLI examples; instead, show Bash-compatible syntax (e.g., var=$(...) ) for Linux users.
  • Add a section or note about running Azure CLI in different environments (Windows Command Prompt, PowerShell, Bash, Cloud Shell, etc.).
  • Where PowerShell modules or cmdlets are referenced, mention cross-platform support or provide alternatives for Linux users if available.
  • Ensure that all automation and scripting guidance is accessible to both Windows and Linux users, with clear, parallel examples.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/deployment-script-develop.md ...re-resource-manager/bicep/deployment-script-develop.md
High Priority View Details →
Scanned: 2025-08-01 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI (Bash) and PowerShell examples side by side, but there are subtle signs of Windows bias. Windows/PowerShell tools and patterns are sometimes referenced first or exclusively (e.g., references to Connect-AzAccount, CommandLineToArgvW, and PowerShell-specific error handling). The documentation assumes familiarity with Windows/PowerShell concepts and tools, and some explanations (like argument parsing) reference Windows APIs. However, Linux/Bash examples are present throughout, and the CLI examples use Bash syntax. There are no outright missing Linux examples, but the documentation could better balance the presentation order and tool references.
Recommendations
  • Where possible, avoid referencing Windows-specific APIs (e.g., CommandLineToArgvW) in general explanations, or provide equivalent Linux context.
  • Alternate the order of CLI (Bash) and PowerShell examples, or present them in parallel, to avoid always listing PowerShell second.
  • When discussing authentication (e.g., Connect-AzAccount), mention cross-platform alternatives or clarify that PowerShell Core is available on Linux.
  • In sections about argument parsing or environment variables, provide both Windows and Linux/Bash perspectives if system-level details are discussed.
  • Audit for any subtle language that assumes a Windows-first audience and revise to be OS-neutral where possible.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/install.md .../main/articles/azure-resource-manager/bicep/install.md
High Priority View Details →
Scanned: 2025-08-01 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation displays a moderate Windows bias. Windows-specific tools (Visual Studio, PowerShell, Chocolatey, Winget) are given prominent and detailed coverage, and Windows installation instructions are often listed before or with more detail than Linux/macOS equivalents. PowerShell is used as the default scripting language for manual installation on Windows, and Windows-centric package managers are highlighted. Linux and macOS instructions are present and generally complete, but Windows tools and patterns are more heavily emphasized.
Recommendations
  • Ensure Linux and macOS installation instructions are as detailed and prominent as Windows instructions, including troubleshooting tips and validation steps.
  • When listing installation options or tools, rotate or randomize the order, or explicitly avoid always listing Windows first.
  • Provide Bash or cross-platform shell examples alongside PowerShell for manual installation steps.
  • Highlight cross-platform editors (like VS Code) before Windows-only tools (like Visual Studio) to reinforce parity.
  • Where Windows-specific package managers (Chocolatey, Winget) are mentioned, also mention Linux/macOS equivalents (e.g., apt, yum, Homebrew) with equal detail.
  • Add a summary table or section explicitly comparing platform support and installation nuances to help users quickly find their path.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/migrate-blueprint.md ...cles/azure-resource-manager/bicep/migrate-blueprint.md
High Priority View Details →
Scanned: 2025-08-01 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell-specific instructions and links (e.g., 'import-export-ps.md'), mentioning Azure PowerShell before Azure CLI, and not providing explicit Linux or cross-platform command-line examples. There is no mention of Linux-specific tools or workflows, and the sample focuses on Bicep/ARM templates without showing how to execute migration steps using cross-platform tools.
Recommendations
  • Provide Azure CLI examples alongside or before Azure PowerShell instructions, as Azure CLI is cross-platform and widely used on Linux.
  • Update links and references to include both PowerShell and CLI documentation, or use neutral phrasing such as 'see Export your blueprint definition using Azure CLI or PowerShell'.
  • Explicitly mention that all migration steps can be performed on Linux, macOS, and Windows, and provide command-line examples for each where relevant.
  • Avoid using '-ps' (PowerShell) documentation links exclusively; link to general or CLI documentation where possible.
  • Add a section or note on how to perform the migration steps in a Linux environment, including any prerequisites or differences.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/createuidefinition-test-cases.md ...rce-manager/templates/createuidefinition-test-cases.md
High Priority View Details →
Scanned: 2025-08-01 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation contains a subtle Windows bias, primarily in the use of the 'osPlatform' property set to 'Windows' in several JSON examples (e.g., credentials, user name, VM size selectors), and the absence of equivalent Linux or cross-platform examples. There are no explicit Linux examples or mentions of Linux-specific patterns, and the documentation does not clarify cross-platform support or differences. No PowerShell or Windows command-line examples are present, but the repeated use of Windows as the default or sole platform in UI control examples suggests a Windows-first perspective.
Recommendations
  • Include examples where 'osPlatform' is set to 'Linux' or provide dual examples for both Windows and Linux where relevant (e.g., credentials, VM size selectors, user name controls).
  • Clarify in the documentation whether the controls and patterns shown are applicable to both Windows and Linux, or specify any differences in behavior or requirements.
  • Add a section or note discussing cross-platform considerations, especially for managed applications that may target Linux VMs.
  • Ensure that any platform-specific properties or behaviors are documented for both Windows and Linux, and provide guidance for users deploying to Linux environments.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/msbuild-bicep-file.md ...les/azure-resource-manager/bicep/msbuild-bicep-file.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a strong Windows bias: all command-line examples use PowerShell syntax and Windows-style paths, with no Linux/macOS shell equivalents. Directory and file paths are shown in Windows format (e.g., C:\msBuildDemo), and project file examples reference the Windows-specific Bicep CLI package by default. Instructions for creating and cleaning up directories, as well as running MSBuild, are provided only for Windows/PowerShell, with no bash or cross-platform alternatives. Linux and macOS are mentioned in package lists, but practical usage guidance is missing.
Recommendations
  • Provide equivalent bash/zsh command-line examples for Linux/macOS, including directory creation, navigation, and cleanup (e.g., mkdir, cd, rm -rf).
  • Show both Windows (\) and Unix-style (/) path separators in file and directory paths, or use cross-platform variables.
  • In project file examples, demonstrate referencing the appropriate Azure.Bicep.CommandLine package for each OS, or show how to use environment variables for BicepPath in a cross-platform way.
  • Include explicit instructions for running MSBuild and dotnet CLI commands on Linux/macOS, noting any differences (such as using 'msbuild' instead of 'MSBuild.exe').
  • Add tabs or callouts for Linux/macOS alongside Windows in all step-by-step instructions.
  • Ensure that all prerequisite and setup steps (such as installing PowerShell or using a shell) are clearly cross-platform, or provide alternatives for each OS.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-tutorial-add-tags.md ...source-manager/templates/template-tutorial-add-tags.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation presents deployment instructions with PowerShell first, followed by Azure CLI. While Azure CLI is cross-platform, the explicit mention of PowerShell and the ordering may suggest a Windows-first approach. There are no explicit Linux/macOS-specific instructions or examples, and the verification and cleanup steps rely on the Azure portal, which is platform-agnostic but does not offer command-line parity for Linux users. The prerequisites mention Visual Studio Code and extensions, which are cross-platform, but do not highlight any Linux-specific tools or workflows.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or default to Azure CLI first, as it is cross-platform.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
  • Provide bash/zsh shell variable examples for Linux/macOS users (e.g., export templateFile=...).
  • Include instructions for verifying and cleaning up resources using Azure CLI commands, not just the Azure portal.
  • Add a note or section highlighting Linux/macOS compatibility and any platform-specific considerations.
GitHub Create Pull Request
← Previous Page 24 of 52 Next →