Deployment Environments
39
Total Pages
28
Linux-Friendly Pages
11
Pages with Bias
28.2%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
47 issues found
Showing 1-25 of 47 flagged pages
Deployment Environments
Create a Dev Center and Project for Deployment Environments by Using an ARM Template
...start-create-dev-center-project-azure-resource-manager.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows by exclusively providing Azure PowerShell examples for deploying ARM templates, with no equivalent Bash or Azure CLI examples. The instructions direct users to select PowerShell in Cloud Shell and do not mention or show Linux-friendly alternatives first or at all. This may disadvantage users on Linux or those who prefer Bash/CLI workflows.
Recommendations
- Add equivalent Azure CLI (az deployment) examples alongside PowerShell, preferably before or in parallel with PowerShell instructions.
- Explicitly mention that Cloud Shell supports both Bash and PowerShell, and provide Bash instructions for Linux/macOS users.
- Ensure all code blocks have both PowerShell and Bash/CLI versions, and clarify which platforms each is suitable for.
- Review the page for other Windows-centric terminology or tool references and add Linux/macOS alternatives where applicable.
Create Pull Request
Deployment Environments
Create an environment with Azure Developer CLI
...-configure-azure-developer-cli-deployment-environments.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation shows a Windows bias in the CLI installation instructions, providing only a PowerShell-based install command for the Azure Developer CLI and omitting Linux/macOS alternatives. The use of PowerShell is presented as the default CLI installation method, and there are no bash/curl/wget examples for non-Windows users. While the rest of the guide is generally cross-platform (focusing on Visual Studio Code and the azd CLI), the initial setup steps may confuse or exclude Linux/macOS users.
Recommendations
- Provide explicit installation instructions for Linux and macOS, using bash/curl/wget commands alongside the PowerShell example.
- Use tabbed sections for installation steps, e.g., [Windows], [Linux], [macOS], to ensure parity and clarity for all platforms.
- Avoid presenting Windows/PowerShell commands as the default or only CLI method; always include cross-platform alternatives.
- Add a note clarifying that azd is cross-platform and link to the official installation guide for all supported operating systems.
Deployment Environments
ADE extensibility model for custom container images
...s/how-to-configure-extensibility-model-custom-image.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several areas. Script-based workflows for building and pushing custom container images are presented exclusively using PowerShell (.ps1) scripts, with invocation examples shown only for Windows/PowerShell environments. There is no mention of equivalent Bash or shell scripts for Linux/macOS users, nor are cross-platform alternatives provided. The prerequisites and instructions reference Docker Desktop (primarily a Windows/Mac tool) and Azure CLI, but do not clarify Linux compatibility or provide Linux-specific guidance. The order of presentation and examples implicitly prioritize Windows tooling and patterns, leaving Linux users to infer or adapt steps themselves.
Recommendations
- Provide equivalent Bash/shell script examples for Linux/macOS users alongside PowerShell examples.
- Explicitly mention Linux/macOS compatibility for all scripts and tools, and clarify any platform-specific requirements.
- Offer cross-platform instructions for installing prerequisites (e.g., Docker, Azure CLI) on Linux, not just Docker Desktop.
- Where scripts are referenced, indicate if both .ps1 and .sh versions are available, or provide guidance for adapting PowerShell scripts to Bash.
- Ensure that example commands (e.g., for building/pushing images) are shown for both Windows (PowerShell) and Linux/macOS (Bash/CLI) environments.
- Avoid using Windows-specific terminology (e.g., PATH variables, PowerShell invocation) without also referencing Linux equivalents.
Deployment Environments
ADE extensibility model for custom container images
...s/how-to-configure-extensibility-model-custom-image.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a Windows bias in several areas. Script-based workflows for building and pushing custom container images are exclusively demonstrated using PowerShell (.ps1) scripts, with invocation examples given in PowerShell syntax. There are no equivalent Bash or shell script examples for Linux/macOS users, nor are cross-platform alternatives mentioned. The prerequisites and instructions repeatedly reference Docker Desktop (a tool most commonly used on Windows and macOS, less so on Linux) and do not mention Docker Engine or Linux-native workflows. The order of presentation and examples consistently favor Windows tooling and patterns, with Linux alternatives missing or relegated to manual steps. This may hinder accessibility and parity for Linux users.
Recommendations
- Provide Bash/shell script equivalents for all PowerShell (.ps1) scripts, and include invocation examples for Linux/macOS terminals.
- Explicitly mention Docker Engine as an alternative to Docker Desktop, and clarify platform-specific installation instructions.
- Where scripts are referenced, indicate cross-platform compatibility or provide separate instructions for Windows (PowerShell) and Linux/macOS (Bash).
- Ensure that all steps (including prerequisites and environment setup) are documented for both Windows and Linux users.
- Add notes or tabs indicating which instructions are platform-specific, and present Linux/macOS examples alongside Windows examples.
- Review referenced repositories and scripts to ensure they include Linux-compatible options and documentation.
Deployment Environments
Create an environment with Azure Developer CLI
...-configure-azure-developer-cli-deployment-environments.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily in the installation instructions for the Azure Developer CLI, where only a PowerShell-based command is provided and no Linux/macOS installation example is shown. The use of PowerShell as the default shell in CLI examples and the absence of explicit Linux or cross-platform shell commands further reinforce this bias. While the rest of the documentation is generally platform-agnostic (using azd CLI commands that work cross-platform), the initial setup experience is skewed toward Windows users.
Recommendations
- Provide explicit installation instructions for Linux and macOS, including bash/curl-based commands alongside the PowerShell example.
- Clearly label installation commands by platform (e.g., Windows, Linux, macOS) using tabs or headings.
- Ensure all CLI examples use cross-platform shell syntax where possible, or provide both PowerShell and bash/zsh equivalents.
- Mention any platform-specific prerequisites or differences in behavior, if applicable.
- Consider including screenshots or terminal output from Linux/macOS environments in addition to Windows/PowerShell.
Deployment Environments
Create a Dev Center and Project for Deployment Environments by Using an ARM Template
...start-create-dev-center-project-azure-resource-manager.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively providing Azure PowerShell examples for deploying the ARM template, with no equivalent Bash or Azure CLI examples for Linux/macOS users. The instructions explicitly direct users to select PowerShell in the Azure Cloud Shell, and all code samples use PowerShell syntax. Although there is a brief mention that Azure CLI and portal can also be used, no concrete examples or guidance are provided for those methods.
Recommendations
- Add equivalent Azure CLI (bash) examples for deploying the ARM template, with step-by-step instructions and code blocks.
- In the 'Deploy the template' section, present both PowerShell and CLI examples side-by-side, or clearly indicate how to switch shells in Azure Cloud Shell.
- Avoid instructing users to select PowerShell exclusively; mention that both Bash and PowerShell are available in Cloud Shell.
- Explicitly reference Linux/macOS usage where appropriate, and ensure all instructions are platform-neutral or provide alternatives.
- Link directly to documentation for deploying ARM templates using Azure CLI and Bash, not just PowerShell.
Deployment Environments
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/deployment-environments/how-to-configure-azure-developer-cli-deployment-environments.md
...-configure-azure-developer-cli-deployment-environments.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily in the installation instructions for the Azure Developer CLI, where only a PowerShell-based command is provided and no Linux/macOS equivalent is shown. The use of PowerShell as the default CLI installation method implicitly prioritizes Windows users. There are no explicit Linux or macOS installation commands or references to platform-specific differences, and the documentation does not mention alternative shell environments or package managers commonly used on Linux/macOS. All other CLI commands are cross-platform, but the initial setup is Windows-centric.
Recommendations
- Provide installation instructions for Linux and macOS, including shell commands (e.g., curl/bash, Homebrew, apt, etc.) alongside the PowerShell command.
- Add a platform selection tab or section for installation steps, so users can easily find instructions for their OS.
- Explicitly mention that azd is cross-platform and provide links to official installation guides for all supported operating systems.
- Include troubleshooting notes or tips for non-Windows environments, such as permissions or dependency requirements.
Deployment Environments
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/deployment-environments/how-to-configure-extensibility-model-custom-image.md
...s/how-to-configure-extensibility-model-custom-image.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several areas. Scripted examples for building and pushing custom container images are provided exclusively as PowerShell (.ps1) scripts, with invocation instructions using PowerShell syntax. There are repeated references to 'Docker Desktop', which is primarily a Windows/Mac tool, and no mention of Docker Engine or Linux-native workflows. There are no equivalent Bash or shell script examples, nor instructions for Linux users. The order of presentation and examples consistently favors Windows tooling and workflows, leaving Linux users without clear guidance.
Recommendations
- Provide equivalent Bash/shell script examples for building and pushing images, including invocation instructions for Linux/macOS users.
- Mention Docker Engine as an alternative to Docker Desktop, and clarify platform requirements for each.
- Add explicit instructions for running the quickstart scripts on Linux, including prerequisites and command syntax.
- Ensure all CLI examples (Azure CLI, Docker) are shown in both Windows (PowerShell) and Linux (Bash) formats where appropriate.
- Review all references to tools and workflows to ensure Linux parity and avoid assuming a Windows-first environment.
Deployment Environments
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/deployment-environments/quickstart-create-dev-center-project-azure-resource-manager.md
...start-create-dev-center-project-azure-resource-manager.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively providing Azure PowerShell examples for deploying the ARM template, with no equivalent Azure CLI or Bash examples for Linux/macOS users. The instructions focus on using PowerShell in the Cloud Shell, and do not mention or illustrate Linux-friendly workflows or commands. Although the page briefly notes that Azure CLI is an alternative, it does not provide any CLI code samples or step-by-step guidance for non-Windows platforms.
Recommendations
- Add Azure CLI examples alongside the PowerShell examples for deploying the ARM template, including both default and custom parameter scenarios.
- Explicitly mention that Cloud Shell supports Bash and provide instructions/code blocks for users who prefer Bash or are on Linux/macOS.
- Reorder or parallelize instructions so that Windows and Linux/macOS workflows are presented with equal prominence.
- Include notes or tips for Linux/macOS users regarding authentication and environment setup in Cloud Shell.
- Where possible, use cross-platform commands or highlight platform-specific differences to ensure parity.
Deployment Environments
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/deployment-environments/how-to-configure-extensibility-model-custom-image.md
...s/how-to-configure-extensibility-model-custom-image.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several areas. Script-based image creation instructions for both Bicep and Terraform exclusively use PowerShell (.ps1) scripts and provide only PowerShell command examples, with no equivalent Bash or shell script examples for Linux/macOS users. The prerequisites and instructions repeatedly mention Docker Desktop (a Windows-centric tool) and Azure CLI, but do not clarify Linux alternatives or usage. The documentation refers to PATH variable configuration in a way typical of Windows environments. There are no explicit Linux or macOS script examples, nor any mention of cross-platform script support, leaving Linux users to infer or adapt steps themselves.
Recommendations
- Provide equivalent Bash/shell script examples for Linux/macOS users alongside PowerShell examples.
- Explicitly mention cross-platform compatibility for scripts, or provide separate instructions for Linux/macOS environments.
- Include instructions for installing and using Docker (not just Docker Desktop) on Linux.
- Clarify PATH variable configuration for both Windows and Linux/macOS.
- Where PowerShell is referenced, add a note or link to Linux/macOS alternatives.
- Ensure that all quickstart scripts and automation tools are available in both PowerShell and Bash/shell formats, or document how to use them on non-Windows platforms.
Deployment Environments
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/deployment-environments/how-to-configure-azure-developer-cli-deployment-environments.md
...-configure-azure-developer-cli-deployment-environments.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways. The only explicit OS-specific installation command provided for the Azure Developer CLI uses PowerShell, which is native to Windows. There are no Linux or macOS installation commands or instructions, nor is there any mention of platform-specific differences or alternatives. The use of PowerShell is presented before any mention of cross-platform shell commands, and no Linux tools or patterns are referenced. This may make it less accessible or clear for Linux or macOS users.
Recommendations
- Add explicit installation instructions for Linux and macOS, including shell commands (e.g., curl/bash) and package manager options where available.
- Include notes or tabs for platform-specific differences in setup, especially for CLI installation and usage.
- Provide examples using bash/zsh for Linux/macOS users alongside PowerShell for Windows.
- Reference Linux tools and patterns where relevant, such as using apt, yum, or Homebrew for installation.
- Ensure screenshots and instructions are balanced between Windows and Linux/macOS environments.
Deployment Environments
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/deployment-environments/quickstart-create-dev-center-project-azure-resource-manager.md
...start-create-dev-center-project-azure-resource-manager.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows by providing only Azure PowerShell examples for deploying the ARM template, with no equivalent Azure CLI or Bash examples. The instructions explicitly direct users to select the PowerShell shell in Cloud Shell, and all code samples use PowerShell syntax. While the page briefly mentions that Azure CLI can be used, it does not provide any CLI or Bash examples, nor does it mention Linux or macOS workflows.
Recommendations
- Add equivalent Azure CLI examples for deploying the ARM template, using Bash syntax.
- Update instructions to mention both PowerShell and Bash shells in Azure Cloud Shell, and provide guidance for users on Linux/macOS.
- Present deployment options in a neutral order (e.g., 'You can use Azure PowerShell or Azure CLI'), rather than prioritizing PowerShell.
- Include notes or links to platform-specific instructions for Linux/macOS users, ensuring parity in tooling and workflow.
Deployment Environments
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/deployment-environments/quickstart-create-dev-center-project-azure-resource-manager.md
...start-create-dev-center-project-azure-resource-manager.md
High Priority
View Details →
Detected Bias Types
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.
Deployment Environments
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/deployment-environments/how-to-create-access-environments.md
...ment-environments/how-to-create-access-environments.md
High Priority
View Details →
Detected Bias Types
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.
Deployment Environments
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/deployment-environments/how-to-create-configure-projects.md
...yment-environments/how-to-create-configure-projects.md
High Priority
View Details →
Detected Bias Types
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.
Deployment Environments
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/deployment-environments/how-to-configure-extensibility-model-custom-image.md
...s/how-to-configure-extensibility-model-custom-image.md
High Priority
View Details →
Detected Bias Types
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.
Deployment Environments
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/deployment-environments/how-to-configure-azure-developer-cli-deployment-environments.md
...-configure-azure-developer-cli-deployment-environments.md
High Priority
View Details →
Detected Bias Types
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).
Deployment Environments
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/deployment-environments/how-to-configure-extensibility-model-custom-image.md
...s/how-to-configure-extensibility-model-custom-image.md
High Priority
View Details →
Detected Bias Types
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).
Deployment Environments
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/deployment-environments/how-to-create-configure-dev-center.md
...ent-environments/how-to-create-configure-dev-center.md
High Priority
View Details →
Detected Bias Types
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.
Deployment Environments
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/deployment-environments/how-to-create-configure-projects.md
...yment-environments/how-to-create-configure-projects.md
High Priority
View Details →
Detected Bias Types
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.
Deployment Environments
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/deployment-environments/quickstart-create-dev-center-project-azure-resource-manager.md
...start-create-dev-center-project-azure-resource-manager.md
High Priority
View Details →
Detected Bias Types
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.
Deployment Environments
Create an environment with Azure Developer CLI
...-configure-azure-developer-cli-deployment-environments.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily in the installation instructions for the Azure Developer CLI, where only a PowerShell command is provided and no Linux/macOS installation method is mentioned. The use of PowerShell as the default CLI example and the absence of Linux/macOS-specific guidance may create friction for non-Windows users. Other CLI commands are cross-platform, but the initial setup is Windows-centric.
Recommendations
- Add explicit installation instructions for Linux and macOS, including shell commands (e.g., curl/bash, Homebrew).
- Provide a tabbed or side-by-side example for Windows (PowerShell), Linux (bash), and macOS (bash/zsh) for CLI installation.
- Clarify that azd is cross-platform and link to official installation docs for all OSes.
- Ensure screenshots and workflow steps do not assume Windows-only environments.
Deployment Environments
Configure a managed identity for Azure Deployment Environments
...ment-environments/how-to-configure-managed-identity.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively uses Azure Portal (GUI) instructions and screenshots, which are platform-agnostic but implicitly favor Windows users due to the prominence of Windows in Azure Portal usage and lack of CLI examples. There are no command-line instructions (e.g., Azure CLI, PowerShell, Bash) provided, which are essential for Linux/macOS users or those working in headless/server environments. No Linux-specific tools, patterns, or examples are mentioned.
Recommendations
- Add Azure CLI command examples for all major steps (creating managed identities, assigning roles, configuring key vault access), ensuring commands work on Linux/macOS and Windows.
- Include PowerShell examples only if CLI parity is maintained; otherwise, prioritize cross-platform CLI.
- Explicitly mention that all steps can be performed via CLI and provide links to relevant CLI documentation.
- Add notes or sections for automation scenarios (e.g., using Bash scripts, cloud shell) to support Linux/macOS users.
Deployment Environments
ADE extensibility model for custom container images
...s/how-to-configure-extensibility-model-custom-image.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a notable Windows bias in its scripting and tooling instructions. The only explicit examples for running the provided quickstart scripts are given in PowerShell syntax (e.g., .\quickstart-image-build.ps1), with no Bash, shell, or Linux/macOS alternatives. The requirement for Docker Desktop is stated, which is a Windows-centric tool, while alternatives like Docker Engine for Linux are not mentioned. There are no Linux/macOS script invocation examples, and the PowerShell examples are presented first and exclusively. This creates friction for Linux/macOS users who may need to adapt or rewrite scripts and commands.
Recommendations
- Provide equivalent Bash/shell script examples for Linux/macOS users, or clarify if the scripts are cross-platform.
- Explicitly mention Docker Engine as an alternative to Docker Desktop for Linux users.
- If the provided scripts are PowerShell-only, offer Bash versions or guidance for Linux/macOS users.
- List Linux/macOS instructions alongside Windows/PowerShell instructions, not after or omitted.
- Indicate platform compatibility for all scripts and tools mentioned.
- Consider using cross-platform scripting languages (e.g., Python, Bash) for automation examples.
Deployment Environments
Grant access to Azure Deployment Environments
...nments/how-to-manage-deployment-environments-access.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively describes role assignment and access management using the Azure portal GUI, which is most commonly accessed from Windows environments. There are no examples or instructions for performing these tasks via CLI tools (such as Azure CLI or Azure PowerShell), which are cross-platform and preferred by many Linux/macOS users. No mention is made of Linux/macOS-specific workflows, nor are command-line alternatives provided.
Recommendations
- Add equivalent instructions for assigning roles using Azure CLI (az role assignment create) and Azure PowerShell, both of which are cross-platform.
- Include example commands for listing, assigning, and removing roles via CLI, with notes on authentication and environment setup for Linux/macOS users.
- Explicitly mention that the Azure portal is accessible from any OS/browser, but provide parity for users who prefer or require command-line automation.
- Where screenshots are used, clarify that the portal UI is OS-agnostic, or supplement with CLI output examples.