Deployment Environments

37
Total Pages
30
Linux-Friendly Pages
7
Pages with Bias
18.9%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues (11)

https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/deployment-environments/quickstart-create-dev-center-project-azure-resource-manager.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools
Summary:
The documentation page provides only Azure PowerShell examples for deploying the ARM template, with no equivalent Azure CLI (cross-platform) or Bash examples. The code blocks and instructions are PowerShell-specific, which may disadvantage Linux/macOS users or those preferring CLI tools. While the text briefly mentions that Azure CLI and portal are also options, no concrete CLI or Bash examples are given.
Recommendations:
  • Add Azure CLI examples alongside PowerShell for all deployment steps, using Bash syntax where appropriate.
  • Present both PowerShell and CLI examples in parallel, or use tabs to allow users to select their preferred environment.
  • Explicitly mention that the Cloud Shell supports both Bash and PowerShell, and provide instructions for both.
  • Avoid language or steps that assume a Windows-first workflow (e.g., PowerShell-specific commands as the default).
  • Ensure all code blocks are available in both PowerShell and CLI/Bash formats to improve accessibility for Linux and macOS users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/deployment-environments/how-to-create-access-environments.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation page primarily uses Azure CLI examples, which are cross-platform, but it contains a key example for passing parameters that uses PowerShell-style variable assignment ($params = ...) and single quotes in JSON, which is not valid in Bash or Linux shells. There are no equivalent Linux/Bash examples for this scenario, and the only variable assignment shown is in a Windows/PowerShell style. This may confuse or exclude Linux/macOS users.
Recommendations:
  • Provide both PowerShell and Bash/Linux examples for variable assignment and parameter passing, especially for the --parameters argument.
  • Use JSON syntax compatible with both shells, or clearly distinguish between Windows/PowerShell and Linux/Bash usage.
  • Add a note or section clarifying cross-platform differences in CLI usage, particularly for scripting and variable handling.
  • Review all code snippets to ensure they are either shell-agnostic or have equivalents for both major platforms.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/deployment-environments/how-to-create-configure-projects.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias by using PowerShell-style variable assignment (e.g., $VAR = ...) and line continuations (`) in all CLI examples, which are specific to Windows/PowerShell environments. There are no equivalent bash/Linux shell examples, nor any notes on how to adapt the commands for non-Windows platforms. This may confuse or exclude Linux/macOS users who use bash/zsh shells.
Recommendations:
  • Provide parallel bash/zsh examples for all CLI commands, using appropriate variable assignment (e.g., VAR=...) and line continuation (\).
  • Add a note at the top indicating which shell the examples are for, and link to guidance for adapting commands to other shells.
  • Where possible, use shell-agnostic syntax or clearly separate PowerShell and bash examples.
  • Explicitly mention that Azure CLI is cross-platform and provide links to installation/use instructions for Linux/macOS.
  • Review and update all code blocks to ensure Linux/macOS users can follow the steps without confusion.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/deployment-environments/how-to-configure-extensibility-model-custom-image.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation demonstrates a Windows bias in several areas: all quickstart scripting examples for building and pushing custom container images use PowerShell (.ps1) scripts and PowerShell syntax, with no equivalent Bash or shell script examples for Linux/macOS users. The instructions reference 'Docker Desktop', a tool primarily associated with Windows and macOS, and do not mention Docker Engine or Linux-native Docker workflows. There are no explicit Linux/Bash script alternatives or guidance for non-Windows environments, and the PowerShell examples are presented as the default/only option.
Recommendations:
  • Provide equivalent Bash/shell script examples for building and pushing images, alongside PowerShell, to support Linux/macOS users.
  • Explicitly mention and provide instructions for using Docker Engine on Linux, not just Docker Desktop.
  • Where scripts are referenced (e.g., quickstart-image-build.ps1), offer or link to a Bash (.sh) version, or clarify cross-platform compatibility.
  • Instruct users on how to run the scripts on Linux/macOS, or provide guidance for adapting the process to those platforms.
  • Avoid assuming the use of Windows-specific tools or environments; ensure parity in documentation order and detail for both Windows and Linux workflows.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/deployment-environments/how-to-configure-azure-developer-cli-deployment-environments.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias, particularly in the installation instructions for the Azure Developer CLI. The only command-line installation example provided uses PowerShell, with no mention of Bash or Linux/macOS alternatives. This may confuse or exclude Linux/macOS users. Additionally, the PowerShell installation command is presented before any cross-platform or alternative instructions, and there is no explicit guidance for non-Windows environments.
Recommendations:
  • Provide installation instructions for the Azure Developer CLI for all major platforms (Windows, Linux, macOS), including Bash/cURL examples alongside PowerShell.
  • Present platform-specific instructions in parallel tabs or sections (e.g., Windows, Linux, macOS), rather than only or first showing Windows/PowerShell.
  • Explicitly mention platform compatibility and link to official cross-platform installation guides.
  • Ensure all command-line examples are available in both PowerShell and Bash (or note when a command is platform-specific).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/deployment-environments/how-to-configure-extensibility-model-custom-image.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation page demonstrates a Windows bias in several areas: PowerShell scripts are the only provided example for building and pushing custom container images in both the ARM-Bicep and Terraform sections, with no equivalent Bash or Linux shell script examples. The instructions specifically reference 'Docker Desktop', a tool most commonly associated with Windows and Mac, and do not mention Linux-native Docker installations. There is no mention of running the scripts or workflows on Linux, nor are there alternative commands or guidance for Linux users. This may create barriers for users on Linux or those using non-Windows environments.
Recommendations:
  • Provide equivalent Bash (.sh) script examples for building and pushing images, or clarify if the provided scripts are cross-platform.
  • Include explicit instructions or notes for Linux users, such as how to run the scripts on Linux, or how to adapt PowerShell scripts for Bash.
  • Mention Linux-native Docker installation as an alternative to Docker Desktop.
  • Where PowerShell commands are shown, provide a Bash alternative or clarify platform compatibility.
  • Audit all prerequisites and steps to ensure they are not Windows-specific, or clearly indicate platform-specific requirements.
  • Consider adding a platform-agnostic section or table summarizing the steps for both Windows (PowerShell) and Linux (Bash).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/deployment-environments/how-to-configure-managed-identity.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation exclusively uses Azure Portal (GUI) instructions and screenshots, with no command-line examples provided for any platform. While this avoids explicit Windows or PowerShell bias, it also omits parity for Linux users who may prefer or require CLI-based workflows (e.g., Azure CLI, Bash). There are no references to Windows-specific tools, but the absence of CLI instructions constitutes a bias by omission, as many cross-platform users expect or require non-GUI alternatives.
Recommendations:
  • Add equivalent Azure CLI instructions for all major steps (e.g., assigning managed identities, setting role assignments, configuring Key Vault access).
  • Ensure CLI examples are presented in a cross-platform manner (e.g., using Bash syntax, not PowerShell).
  • Where possible, provide both Portal (GUI) and CLI workflows, and indicate that the CLI steps work on Windows, Linux, and macOS.
  • Explicitly mention that all steps can be performed via the Azure CLI, and link to relevant Azure CLI documentation.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/deployment-environments/how-to-create-access-environments.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example
Summary:
The documentation primarily uses Azure CLI examples, which are cross-platform, but includes a parameter example using PowerShell variable assignment ($params = ...), which is not valid in Bash or other Unix shells. There are no equivalent Linux/Bash examples for passing parameters, and the only variable assignment shown is in PowerShell syntax. This may confuse Linux or macOS users.
Recommendations:
  • Provide both PowerShell and Bash examples for variable assignment and parameter passing, e.g., show how to assign and use parameters in Bash: params='{ "name": "firstMsi", "location": "northeurope" }' and then use --parameters "$params".
  • Explicitly note that the Azure CLI commands work on Windows, Linux, and macOS, and clarify any OS-specific syntax differences.
  • Where variable assignment or scripting is shown, always provide both Windows (PowerShell) and Linux/macOS (Bash) variants side by side.
  • Review for any other subtle Windows-centric patterns (such as path separators or environment variable syntax) and ensure parity in examples.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/deployment-environments/how-to-create-configure-dev-center.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation page primarily uses Azure CLI commands, which are cross-platform, but several command-line examples use Windows/PowerShell-specific syntax (e.g., variable assignment with $VAR and Write-Output), and there is no mention of Linux or macOS shell equivalents. This could confuse or exclude Linux/macOS users who expect bash syntax. Additionally, where scripting is shown, the examples default to Windows/PowerShell conventions without offering Linux alternatives.
Recommendations:
  • Provide both PowerShell and bash/zsh equivalents for variable assignment and output (e.g., $VAR=... vs VAR=...).
  • Explicitly mention that the Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
  • Where scripting or environment-specific commands are shown, use neutral syntax or show both Windows and Linux/macOS versions side by side.
  • Add a note or section for Linux/macOS users, clarifying any differences in command usage or syntax.
  • Avoid using Write-Output and PowerShell variable syntax in generic CLI documentation unless paired with bash equivalents.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/deployment-environments/how-to-create-configure-projects.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias by using PowerShell-style variable assignment (e.g., $VAR = ...) and line continuations (`), which are specific to PowerShell and not compatible with Bash or other Linux shells. There are no equivalent Bash/Linux shell examples provided, nor is there any mention of how to adapt the commands for Linux or macOS users. The documentation implicitly assumes a Windows/PowerShell environment throughout.
Recommendations:
  • Provide equivalent Bash/Linux shell examples for all commands that use PowerShell syntax, including variable assignment and line continuation.
  • Clearly indicate which commands are for PowerShell and which are for Bash, or provide side-by-side examples for both environments.
  • Avoid using Windows-specific syntax (such as backtick line continuations and $VAR assignment) in generic Azure CLI documentation, or at least supplement with POSIX-compliant alternatives.
  • Add a note at the beginning of the page clarifying which shell environment the examples target, and link to guidance for running Azure CLI on Linux/macOS.
  • Test all example commands in both Windows (PowerShell) and Linux (Bash) environments to ensure parity and usability.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/deployment-environments/quickstart-create-dev-center-project-azure-resource-manager.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools
Summary:
The documentation page provides only Azure PowerShell examples for deploying the ARM template, with no equivalent Azure CLI (cross-platform) or Bash examples. The code blocks and instructions are tailored to PowerShell, which is more familiar to Windows users. While the text briefly mentions that Azure CLI can be used, it does not provide any CLI or Linux-native command examples, nor does it prioritize cross-platform tooling.
Recommendations:
  • Add equivalent Azure CLI examples for all deployment steps, using Bash syntax where appropriate.
  • Present both PowerShell and CLI/Bash examples side by side, or allow the user to toggle between them.
  • Explicitly mention that the Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Ensure that instructions for opening and using the Cloud Shell clarify that both Bash and PowerShell environments are available.
  • Consider listing Azure CLI examples before or alongside PowerShell to avoid implicit Windows-first bias.