Azure Docs
14605
Total Pages
12420
Linux-Friendly Pages
2185
Pages with Bias
15.0%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
2185 issues found
Showing 576-600 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/management/relocation/relocation-virtual-network.md
...er/management/relocation/relocation-virtual-network.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides detailed instructions for the Azure Portal (web UI) and Azure PowerShell, but does not include any examples or guidance for Linux users or for the Azure CLI, which is cross-platform. All command-line automation is shown exclusively with PowerShell cmdlets, and file editing is demonstrated with Notepad, a Windows tool. There are no bash, shell, or Azure CLI examples, nor any mention of Linux-native editors or workflows.
Recommendations
- Add equivalent Azure CLI (az) examples for all PowerShell command-line steps, including exporting, editing, and redeploying ARM templates.
- Demonstrate file editing with cross-platform editors (e.g., vim, nano, code) or use generic language (e.g., 'open the file in your preferred editor').
- Explicitly mention that all steps can be performed from Linux, macOS, or Windows, and provide any OS-specific notes if needed.
- Where possible, provide bash/shell script snippets for automation, or at least reference the Azure CLI documentation for Linux/macOS users.
- Ensure that references to tools and commands are not Windows-specific unless absolutely necessary, and always provide alternatives for other platforms.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/templates/copy-outputs.md
...icles/azure-resource-manager/templates/copy-outputs.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation references Azure PowerShell before Azure CLI when discussing tool versions required for zero-count support, and the only deployment tutorial linked in 'Next steps' is for PowerShell. There are no explicit Linux or Bash examples, nor are there links to Linux/Bash deployment guides. This creates a subtle Windows/Powershell bias by prioritizing Windows tooling and omitting Linux-first or cross-platform examples.
Recommendations
- Mention Azure CLI before or alongside Azure PowerShell when listing supported tools.
- Include links to both PowerShell and Azure CLI (Bash) deployment guides in the 'Next steps' section.
- Provide example deployment commands for both PowerShell and Azure CLI/Bash where relevant.
- Ensure parity in documentation by referencing cross-platform tools and workflows, not just Windows-centric ones.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/devtest-labs/how-to-move-labs.md
...s/blob/main//articles/devtest-labs/how-to-move-labs.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a notable Windows bias. PowerShell commands are used exclusively for disk operations, with no Bash or CLI alternatives provided. The instructions for swapping OS disks reference a Windows-specific article. AzCopy is presented as the preferred tool, but only PowerShell usage is shown. Where both Windows (RDP) and Linux (SSH) are mentioned, the Windows example is listed first. There are no explicit Linux shell or cross-platform CLI examples for key steps, and the overall workflow assumes familiarity with Windows-centric tools and patterns.
Recommendations
- Provide equivalent Bash/Azure CLI examples for all PowerShell scripts, especially for disk operations and AzCopy usage.
- Reference both Windows and Linux documentation for tasks like OS disk swapping, not just Windows-specific articles.
- When giving examples for VM network configuration, alternate the order or present both Windows (RDP) and Linux (SSH) examples together, or lead with Linux where appropriate.
- Explicitly mention that AzCopy and other tools can be used from Linux/macOS as well, and provide sample commands.
- Add notes or sections for users working from Linux/macOS environments, including any prerequisites or differences in workflow.
- Ensure that all screenshots and UI instructions are not Windows-specific, or clarify if they are cross-platform.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/templates/data-types.md
...rticles/azure-resource-manager/templates/data-types.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page is generally platform-neutral, but it introduces a Windows bias in the 'Integers' section by referencing PowerShell and its integer limits as the only concrete example of SDK/CLI limitations. No equivalent mention is made of Azure CLI (which is cross-platform and commonly used on Linux/macOS), nor are Linux-specific tools or examples provided. This may give the impression that Windows/PowerShell is the primary or preferred environment for ARM template deployment.
Recommendations
- When discussing SDK or CLI limitations, mention both PowerShell and Azure CLI (e.g., 'when using PowerShell or Azure CLI...') and describe any differences in behavior or limits.
- Provide examples or notes relevant to Linux/macOS users, such as referencing Azure CLI or Bash scripting where appropriate.
- Avoid referencing only Windows-specific tools or environments unless there is a technical reason; strive for parity by including cross-platform or Linux-first alternatives.
- Consider adding a table or section summarizing any differences in behavior between PowerShell, Azure CLI, and other SDKs for ARM template deployment.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/templates/deployment-modes.md
...s/azure-resource-manager/templates/deployment-modes.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is presented first and in more detail when describing how to set deployment mode, with a full PowerShell example using a Windows-style file path (c:\MyTemplates\storage.json). The Azure CLI example follows, but uses a generic filename without a path, missing an explicit Linux-style example. The documentation references PowerShell in the 'Next steps' section and links to a PowerShell-specific deployment guide, with no equivalent emphasis on Bash or Linux shell environments. There are no explicit Linux or cross-platform shell examples, and Windows conventions (such as file paths and PowerShell syntax) are foregrounded.
Recommendations
- Provide both Windows (PowerShell) and Linux/macOS (Bash) examples side by side when demonstrating CLI usage, including file paths appropriate for each OS.
- Avoid using Windows-specific file paths (e.g., c:\MyTemplates\storage.json) in generic examples; instead, use cross-platform or dual examples (e.g., c:\MyTemplates\storage.json and ~/MyTemplates/storage.json).
- In 'Next steps', include links to both PowerShell and Bash/Azure CLI deployment guides to ensure parity.
- When referencing tools or commands, clarify cross-platform compatibility and note any OS-specific considerations.
- Consider adding a short section or note explicitly stating that all examples work on both Windows and Linux/macOS, and provide guidance for users on each platform.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/templates/best-practices.md
...les/azure-resource-manager/templates/best-practices.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias. In the section about parameter naming conflicts, only PowerShell (specifically the New-AzResourceGroupDeployment cmdlet) is discussed, with no mention of equivalent Azure CLI or Linux-native tooling. In the resources section, links to Windows VM connection methods are listed before Linux, and two out of three links are Windows-specific. There are no Linux shell or Azure CLI examples for template deployment or parameter handling, and no mention of Linux tools or workflows.
Recommendations
- Include Azure CLI examples alongside or before PowerShell examples when discussing template deployment and parameter handling.
- Mention Linux-native tools and workflows (e.g., bash, az CLI) in sections that currently only reference PowerShell or Windows tools.
- When listing links for connecting to VMs, alternate the order or group Windows and Linux resources equally, and ensure parity in detail and prominence.
- Add explicit Linux/CLI examples for common tasks such as deploying templates, handling parameters, and resolving naming conflicts.
- Reference cross-platform editors and tools (e.g., Visual Studio Code) in a way that highlights their availability on Linux and macOS, not just Windows.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/templates/add-template-to-azure-pipelines.md
...e-manager/templates/add-template-to-azure-pipelines.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a strong Windows and PowerShell bias. All scripting examples use PowerShell, and the primary script-based deployment method is via PowerShell scripts (.ps1). The 'Azure PowerShell' task is featured exclusively, with no mention of Bash, CLI, or cross-platform scripting alternatives. The file copy and deployment examples use the 'windows-latest' build agent pool, and there are no Linux or macOS-specific instructions or examples. Windows tools and patterns (such as Visual Studio project scripts and PowerShell) are referenced before or instead of Linux equivalents.
Recommendations
- Provide equivalent examples using Azure CLI (az) in Bash scripts, which are cross-platform and commonly used on Linux/macOS.
- Include YAML pipeline examples that use 'ubuntu-latest' or 'macos-latest' build agents for all tasks, not just for PowerShell.
- Mention and demonstrate how to use Bash scripts for ARM template deployment, including sample Bash scripts.
- Reference cross-platform editors and tools (such as VS Code) alongside or instead of Visual Studio.
- Clarify that PowerShell Core is available cross-platform, but also show how to use native shell scripting on Linux.
- Ensure that all tasks (such as file copy) have Linux-compatible alternatives, and provide examples using those alternatives (e.g., using AzCopy in Bash).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/templates/deployment-script-template-configure-dev.md
.../templates/deployment-script-template-configure-dev.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows/PowerShell bias by providing all deployment and upload examples using PowerShell commands, referencing Windows-style file paths and drive letters, and omitting equivalent Linux shell or Bash examples for local operations. While the container instances themselves run Linux, and the ARM templates use Linux containers, the instructions for interacting with Azure resources from the user's local machine are almost exclusively Windows/PowerShell-centric. There is minimal guidance for users on Linux or macOS systems, particularly for uploading files or running Docker containers with Unix-style paths.
Recommendations
- Provide Bash/Azure CLI examples for all PowerShell scripts shown, especially for uploading files to Azure Storage and deploying ARM templates.
- Include Linux/macOS-specific instructions for Docker volume mounting, using forward slashes and typical Unix paths (e.g., /home/user/docker:/data).
- When referencing file paths or drive letters, clarify the syntax for both Windows and Unix-like systems.
- Where PowerShell is used for local scripting, add equivalent Bash scripts or Azure CLI commands to ensure parity.
- Explicitly state that the instructions apply to both Windows and Linux/macOS, and highlight any OS-specific considerations.
- Add screenshots or terminal output examples from Linux/macOS environments where appropriate.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/templates/deploy-cli.md
...rticles/azure-resource-manager/templates/deploy-cli.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation generally uses cross-platform Azure CLI commands and Bash syntax, but there are several instances where Windows-specific shells (CMD, PowerShell) are mentioned first or exclusively. Examples for handling parameters and variables often provide Bash/Linux syntax first, but Windows-specific instructions are included as secondary notes. There is a lack of parity in providing full PowerShell/CMD examples, and the documentation sometimes assumes familiarity with Windows tools and conventions.
Recommendations
- For every example that mentions Windows Command Prompt (CMD) or PowerShell, provide a corresponding, fully worked-out Linux/Bash example, and vice versa.
- When discussing shell-specific syntax (e.g., arrays, variables), present Linux/Bash and Windows/PowerShell examples side by side, rather than mentioning one as a note after the other.
- Avoid phrases like 'If you're using Azure CLI with Windows Command Prompt (CMD) or PowerShell...' without also including 'If you're using Bash or a Linux shell...' for parity.
- Where possible, use neutral, cross-platform examples or explicitly state which shell the example is for, and provide both Linux and Windows variants.
- Add a section or table summarizing differences in command syntax between Bash/Linux and Windows/PowerShell for common deployment scenarios.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/templates/deploy-cloud-shell.md
...azure-resource-manager/templates/deploy-cloud-shell.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation presents both Azure CLI (cross-platform) and PowerShell examples, but PowerShell is given equal prominence to Azure CLI, and is referenced as a primary shell alongside Bash. PowerShell, while available on Linux, is still strongly associated with Windows environments. The documentation also refers to PowerShell-specific commands and patterns, and links to further PowerShell-focused documentation before Linux-specific resources. There is a subtle Windows bias in the parity and prominence given to PowerShell, and in the lack of explicit Linux/Bash-specific guidance or troubleshooting.
Recommendations
- Prioritize Azure CLI/Bash examples and explanations, as these are more universally applicable across platforms, especially for Linux users.
- Clearly indicate that PowerShell is cross-platform, but note its Windows origins and that Bash is the default for many Linux users.
- Add Linux/Bash-specific troubleshooting tips or notes where relevant (e.g., file paths, permissions).
- When linking to further documentation, ensure Linux/Bash resources are listed first or equally with PowerShell/Windows resources.
- Consider including a short section on the differences in experience between Bash and PowerShell in Cloud Shell, especially for users coming from Linux backgrounds.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/templates/create-visual-studio-deployment-project.md
...r/templates/create-visual-studio-deployment-project.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is heavily oriented toward Windows and Visual Studio users, with all instructions and examples assuming a Windows environment. Only PowerShell scripts are provided for deployment, and there is no mention of Linux, macOS, or cross-platform alternatives. Visual Studio (a Windows-centric IDE) is required throughout, and no equivalent CLI or editor-agnostic workflows are described. There are no bash, Azure CLI, or VS Code examples, nor any guidance for non-Windows users.
Recommendations
- Add instructions and examples for deploying resource group projects using Azure CLI and Bash, which are cross-platform.
- Include guidance for using VS Code (which is cross-platform) with ARM/Bicep templates, including editing, validation, and deployment.
- Explicitly mention support (or lack thereof) for Linux and macOS, and provide alternative workflows for those platforms.
- Provide sample scripts and deployment steps that work on Linux/macOS terminals, not just PowerShell.
- Clarify which features are Visual Studio-specific and suggest equivalent tools or approaches for non-Windows users.
- Consider restructuring the documentation to present cross-platform approaches first, or at least in parallel with Windows/Visual Studio-specific instructions.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/templates/deployment-tutorial-linked-template.md
...nager/templates/deployment-tutorial-linked-template.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation demonstrates a Windows bias by providing PowerShell scripts and instructions first, using Windows-centric tools (PowerShell, Invoke-WebRequest), and focusing on PowerShell-based workflows for setup and deployment. While Azure CLI examples are included, the initial and most detailed setup instructions rely on PowerShell, which is more familiar to Windows users. There is also a lack of Linux-native shell scripting or guidance for Linux users in the setup phase, and the 'Try-it' Cloud Shell guidance assumes PowerShell usage.
Recommendations
- Provide equivalent Bash/Azure CLI scripts for all PowerShell examples, especially for setup and template upload steps.
- Present Azure CLI or Bash examples before or alongside PowerShell, not after.
- Include explicit instructions for Linux/macOS users, such as using curl/wget instead of Invoke-WebRequest, and clarify Cloud Shell defaults.
- Avoid assuming PowerShell as the default shell; clarify when instructions are Windows-specific.
- Add notes or callouts for cross-platform differences, especially in file paths and command syntax.
Azure Docs
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 →
Detected Bias Types
Windows First
Windows Tools
Osplatform Windows Heavy
Summary
The documentation is generally neutral and focused on JSON schema and Azure Resource Manager templates, but there is a subtle Windows bias. Several examples specify 'osPlatform': 'Windows' (e.g., for credentials, user name, and VM size selectors), and there are no examples or mentions of 'osPlatform': 'Linux' or Linux-specific configuration. The documentation does not provide parity or guidance for Linux scenarios, nor does it clarify cross-platform behavior for controls that support both Windows and Linux.
Recommendations
- Add examples that use 'osPlatform': 'Linux' for relevant controls (e.g., credentials, user name, VM size selectors) to demonstrate Linux support.
- Explicitly mention when a control or property is cross-platform or Windows-specific, and provide Linux equivalents where applicable.
- Include notes or examples showing how to configure parameters and outputs for Linux virtual machines, especially for controls like Microsoft.Compute.UserNameTextBox and Microsoft.Compute.SizeSelector.
- If certain validation or constraints differ between Windows and Linux (e.g., allowed usernames, password policies), document those differences.
- Review all sample JSON to ensure Linux scenarios are represented equally alongside Windows.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/templates/quickstart-create-template-specs.md
...-manager/templates/quickstart-create-template-specs.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by consistently using Windows-style file paths (e.g., 'c:\Templates\azuredeploy.json') in all CLI and PowerShell examples, without providing Linux/macOS alternatives. There are no explicit Linux/macOS shell examples, and the only variable assignment example for Azure CLI uses Bash syntax but still references Windows paths. Additionally, references to PowerShell and Windows-specific tools are prominent, and Linux equivalents or considerations are not mentioned.
Recommendations
- Provide both Windows and Linux/macOS file path examples (e.g., 'c:\Templates\azuredeploy.json' and '~/Templates/azuredeploy.json') in all CLI and PowerShell code blocks.
- Explicitly mention that the Azure CLI commands work cross-platform and show Bash/zsh and PowerShell syntax where relevant.
- Add notes or tabs for Linux/macOS users, especially for file paths and environment-specific behaviors.
- When referencing PowerShell, clarify that Azure PowerShell is available on Linux/macOS and provide installation links for those platforms.
- Avoid assuming a Windows directory structure in instructions and screenshots; use neutral or dual examples.
- Where possible, provide shell-agnostic variable assignment examples or clarify differences between Bash and PowerShell.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/templates/overview.md
.../articles/azure-resource-manager/templates/overview.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates mild Windows bias. PowerShell is mentioned multiple times (deployment scripts, ARM TTK testing), and the primary authoring tools highlighted are Visual Studio and Visual Studio Code, both of which have strong Windows associations. The ARM TTK testing tool is described as a PowerShell script, with no mention of alternative ways to run it on Linux or cross-platform shells. In the extensibility section, PowerShell is mentioned before Bash. In the CI/CD section, Azure DevOps and Visual Studio are referenced, which are more commonly used on Windows. While Azure CLI and Bash are mentioned, they are not given equal prominence or detail.
Recommendations
- When mentioning deployment scripts, list Bash before or alongside PowerShell, and clarify that both are equally supported.
- For ARM TTK, provide explicit instructions or links for running the tool on Linux/macOS (e.g., using PowerShell Core or alternative test runners).
- Highlight cross-platform authoring tools (e.g., Visual Studio Code) before Windows-only tools (e.g., Visual Studio), and clarify their availability on Linux/macOS.
- In the CI/CD section, mention other popular cross-platform CI/CD tools (e.g., GitHub Actions) alongside Azure DevOps.
- Where possible, provide example commands for both Azure CLI and PowerShell, or clarify that all deployment options are cross-platform.
- Review all tool and workflow recommendations to ensure Linux and macOS users are not implicitly deprioritized.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/templates/parameter-files.md
...es/azure-resource-manager/templates/parameter-files.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying templates with parameter files. However, the PowerShell example uses a Windows-style file path (C:\MyTemplates\...), and the PowerShell section appears before any mention of Linux shell equivalents or cross-platform scripting. Additionally, the 'Parameter name conflicts' section discusses PowerShell-specific behavior without mentioning how this might differ in other environments. The Visual Studio tip is also Windows-centric. There are no explicit Linux shell or scripting examples, and no mention of Linux-specific tools or patterns.
Recommendations
- Include Linux shell (bash) examples alongside PowerShell, especially for file paths and scripting.
- Use cross-platform file paths in examples (e.g., ./MyTemplates/storage.parameters.json) or show both Windows and Linux variants.
- Clarify PowerShell-specific behaviors (such as parameter name conflicts) and note if/how they differ in other environments.
- Add tips or notes for users working on Linux or macOS, especially regarding file system conventions and editor integration.
- Balance the order of examples, sometimes presenting Linux/CLI first or side-by-side with Windows/PowerShell.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/templates/template-expressions.md
...ure-resource-manager/templates/template-expressions.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows and PowerShell by exclusively using Azure PowerShell (New-AzResourceGroupDeployment) for command-line examples and referencing 'AzurePowerShell' as the script kind in ARM template resources. There are no examples using Azure CLI or Bash, and no mention of Linux scripting environments or tools, which may disadvantage users working on Linux or macOS platforms.
Recommendations
- Provide equivalent Azure CLI (az deployment group create) examples alongside PowerShell commands for deploying templates and passing parameters.
- Include examples using 'AzureCLI' as the 'kind' property in deploymentScripts resources, not just 'AzurePowerShell'.
- Explicitly mention that the examples apply to both Windows and Linux, or clarify any platform-specific differences.
- Add Bash or shell command examples where relevant, especially for parameter passing and template deployment.
- Balance the order of examples so that Linux/CLI approaches are presented alongside or before Windows/PowerShell ones.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/templates/deployment-script-template.md
...source-manager/templates/deployment-script-template.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows/PowerShell bias in several ways: PowerShell is consistently presented first and in more detail, with sample templates and inline script examples defaulting to PowerShell. The 'Try it' section and code snippets use PowerShell exclusively, and Windows-specific tools or APIs (such as CommandLineToArgvW) are referenced without Linux equivalents. While Azure CLI and Bash are mentioned, their examples are less prominent or detailed, and Linux/Bash scripting is not given equal, parallel treatment throughout the document.
Recommendations
- Provide parallel examples for both PowerShell and Bash/Azure CLI in all sample templates and code snippets, ensuring that Linux users see their workflow represented equally.
- Alternate the order in which PowerShell and CLI/Bash examples are presented, or present them side-by-side, to avoid always privileging Windows/PowerShell.
- Include 'Try it' sections and walkthroughs for Azure CLI/Bash, not just PowerShell.
- Reference cross-platform or Linux-native tools and APIs where appropriate, and avoid referencing Windows-specific APIs (like CommandLineToArgvW) without also mentioning the Linux equivalent.
- Clarify in all sections that both PowerShell and Bash/CLI are supported, and provide explicit guidance for Linux environments.
- Expand troubleshooting and environment setup guidance to cover both Windows and Linux development environments equally.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/templates/key-vault-parameter.md
...zure-resource-manager/templates/key-vault-parameter.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides both Azure CLI and PowerShell examples throughout, but there is a notable emphasis on PowerShell, which is traditionally associated with Windows environments. In several places, PowerShell examples are listed before Azure CLI, and the documentation references Windows-specific scenarios (such as installing a certificate on a Windows VM). There are no explicit Linux shell (bash) examples, and the PowerShell examples use Windows-style syntax (e.g., backticks for line continuation). Additionally, the documentation references Windows tools and patterns without providing Linux-specific guidance or parity.
Recommendations
- Ensure that Azure CLI examples are always presented first or at least equally with PowerShell, as Azure CLI is cross-platform and more familiar to Linux users.
- Add explicit bash/shell script examples where possible, especially for common deployment scenarios.
- Avoid Windows-specific syntax in examples (such as PowerShell backticks) or provide equivalent Linux shell syntax.
- When referencing VM scenarios, include both Windows and Linux VM examples or clarify when an example is Windows-only.
- Review linked resources and quickstarts to ensure Linux parity and provide links to Linux-focused documentation where available.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/templates/template-tutorial-deploy-vm-extensions.md
...er/templates/template-tutorial-deploy-vm-extensions.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong Windows bias by exclusively using Windows VM examples, PowerShell scripts, and Windows-specific tools (e.g., Install-WindowsFeature, IIS). There are no Linux VM or Bash script examples, and all instructions and templates are tailored to Windows environments. Linux equivalents are not mentioned or provided.
Recommendations
- Include parallel Linux examples throughout the tutorial, such as deploying a Custom Script Extension to install Apache or Nginx on a Linux VM using a Bash script.
- Provide both PowerShell and Bash script samples for the Custom Script Extension.
- Reference and link to Linux-specific quickstart templates (e.g., 'Deploy a simple Linux VM') alongside the Windows template.
- Show how to retrieve the public IP address using both Azure CLI (az) and Azure PowerShell.
- Ensure that all steps (preparation, editing, deployment, cleanup) have Linux alternatives and are presented with equal prominence.
- Mention and link to the Linux VM extensions documentation and features.
Azure Docs
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. PowerShell examples are consistently presented before Azure CLI, and file paths in PowerShell use Windows-style (e.g., c:\Templates\azuredeploy.json) without Linux equivalents. The CLI section mentions Bash but does not provide explicit Linux/Mac file path examples or note cross-platform differences. There is no mention of Linux-specific considerations, and the 'Next steps' section links only to PowerShell-focused resources.
Recommendations
- Alternate the order of PowerShell and CLI examples, or present CLI examples first to avoid implicit prioritization of Windows.
- In PowerShell examples, provide both Windows and Linux/Mac file path formats (e.g., c:\Templates\azuredeploy.json and /home/user/Templates/azuredeploy.json).
- Explicitly mention that Azure CLI commands are cross-platform and provide notes or examples for both Windows (CMD/PowerShell) and Linux/Mac (Bash) environments, especially for environment variable syntax and file paths.
- In the 'Next steps' section, include links to both PowerShell and CLI documentation, as well as any Linux-specific deployment guides if available.
- Add a short section or callout highlighting any differences or considerations when running these commands on Linux or MacOS.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/templates/template-spec-convert.md
...re-resource-manager/templates/template-spec-convert.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a strong bias towards Windows by exclusively providing PowerShell-based automation instructions and scripts for converting templates. There are no examples or guidance for Linux or cross-platform CLI users (e.g., Bash, Azure CLI), and the only automation method relies on a .ps1 script, which is native to Windows environments. Manual steps are portal-based and platform-agnostic, but all scripting and automation content is Windows-centric.
Recommendations
- Provide equivalent automation instructions using Azure CLI (az) commands, which are cross-platform and work on Linux, macOS, and Windows.
- If a migration script is only available in PowerShell, mention this limitation explicitly and provide guidance for Linux/macOS users (e.g., using PowerShell Core or requesting a Bash/Python version).
- Offer Bash or shell script examples for Linux users, or reference community tools/scripts if available.
- Ensure that scripting and automation sections include both Windows (PowerShell) and Linux (Bash/Azure CLI) options, or clearly state platform requirements.
- Consider reordering or parallelizing instructions so that Windows and Linux users see their options presented equally, rather than Windows-first.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/templates/template-specs-create-portal-forms.md
...anager/templates/template-specs-create-portal-forms.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates a mild Windows bias. It references PowerShell cmdlets (Get-AzSubscription, Get-AzADUser, Get-AzADServicePrincipal) in parameter descriptions without mentioning Linux/CLI alternatives. In the 'Create template spec' and 'Improve the form' sections, PowerShell examples are presented before Azure CLI examples. There are no explicit Linux/Unix shell examples or references to Linux-specific tools or workflows.
Recommendations
- When referencing how to obtain values (such as tenantId or objectId), provide both PowerShell and Azure CLI commands (e.g., az account show, az ad user show) in parameter descriptions.
- Alternate the order of PowerShell and Azure CLI examples, or present them side-by-side to avoid always listing PowerShell first.
- Explicitly mention that both Azure CLI and PowerShell are cross-platform, and provide guidance for Linux/macOS users where relevant.
- Consider including bash shell scripting examples or notes for Linux users, especially when instructing users to save files or run commands.
- Where possible, avoid referring to tools as 'Visual Studio Code' only; mention other editors or clarify that any code/text editor may be used.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/templates/template-specs-create-linked.md
...urce-manager/templates/template-specs-create-linked.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a Windows bias by using Windows-style file paths (e.g., c:\Templates\...), referencing PowerShell and Azure CLI as the only scripting environments, and providing Windows-specific notes (such as known issues with Windows PowerShell). Linux or macOS-specific instructions, file path examples, or shell scripting examples are missing, and Windows conventions are presented first throughout.
Recommendations
- Provide Linux/macOS file path examples alongside Windows paths (e.g., /home/user/Templates/linkedTS/azuredeploy.json).
- Include bash shell variable assignment examples for Azure CLI commands (e.g., id=$(az ts show ...)).
- Add notes about cross-platform compatibility for both PowerShell Core (pwsh) and Windows PowerShell, clarifying differences if any.
- Explicitly mention that the Azure CLI and PowerShell examples work on Linux/macOS, and provide any necessary adjustments (such as path separators or environment-specific issues).
- If referencing known issues, specify if they are Windows-only and note if Linux/macOS are unaffected.
- Consider adding a table or section summarizing differences or tips for Linux/macOS users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/templates/template-tutorial-deploy-sql-extensions-bacpac.md
...ates/template-tutorial-deploy-sql-extensions-bacpac.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation demonstrates a strong Windows bias by providing only PowerShell scripts for preparing and deploying the BACPAC file, and by instructing users to select PowerShell in Azure Cloud Shell. There are no equivalent Bash or Linux-native examples, and the workflow assumes familiarity with Windows-centric tools and patterns. While there is a brief mention that Azure Cloud Shell can run PowerShell or Bash, all practical examples and screenshots use PowerShell exclusively.
Recommendations
- Provide equivalent Bash scripts for all PowerShell examples, especially for preparing the BACPAC file and deploying the ARM template. Ensure these scripts work in Azure Cloud Shell (Bash) and on Linux/macOS terminals.
- When instructing users to select a shell in Azure Cloud Shell, present both PowerShell and Bash as equal options, or default to Bash for cross-platform parity.
- Include screenshots and instructions for both PowerShell and Bash environments where relevant.
- Explicitly mention that all steps can be performed on Linux/macOS, and provide any necessary platform-specific notes (e.g., file paths, command differences).
- Where third-party tools are referenced (e.g., openssl), clarify their availability on both Windows and Linux, and provide installation guidance if needed.