Copilot

39
Total Pages
34
Linux-Friendly Pages
5
Pages with Bias
12.8%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

26 issues found
Showing 1-25 of 26 flagged pages
Copilot Azure Copilot capabilities ...gement-docs/blob/main/articles/copilot/capabilities.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates mild Windows bias. Script generation examples mention Azure CLI, PowerShell, Terraform, and Bicep, but PowerShell is listed before Terraform/Bicep and is called out specifically. Troubleshooting examples reference Power BI (a Windows-centric tool), and there is no explicit mention of Linux shell (bash) or Linux-native tools. There are no Linux-specific examples, and Windows tools/patterns (PowerShell, Power BI) are referenced without Linux equivalents.
Recommendations
  • Add explicit Linux/bash script generation examples alongside PowerShell.
  • Mention Linux-native tools (e.g., Bash, curl, jq) when discussing automation and troubleshooting.
  • Ensure parity in examples by including both Windows and Linux scenarios (e.g., troubleshooting from Linux clients, using Linux monitoring tools).
  • When listing script generation capabilities, alternate or randomize the order of PowerShell and Linux tools, or group them together as 'scripting languages' to avoid Windows-first impression.
  • Reference cross-platform tools (e.g., Azure CLI, Terraform) before platform-specific ones.
  • Include troubleshooting examples relevant to Linux environments (e.g., SSH connectivity, Linux VM diagnostics).
GitHub Create Pull Request
Copilot Use Azure Copilot with AI Shell ...t-docs/blob/main/articles/copilot/ai-shell-overview.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exhibits a strong Windows bias by focusing on PowerShell and its module (AIShell), referencing only PowerShell-based installation and usage, and omitting explicit Linux shell (bash/zsh) examples or instructions. The links and repository references are PowerShell-centric, and there is no mention of Linux-specific tools, installation steps, or command-line environments. Azure CLI is mentioned, but only in conjunction with PowerShell, and no Linux-first or cross-platform parity is demonstrated.
Recommendations
  • Add explicit bash/zsh examples alongside PowerShell examples for command generation and troubleshooting.
  • Include installation instructions for AI Shell on Linux and macOS, detailing any differences or requirements.
  • Reference Linux shell environments (e.g., bash, zsh) and provide parity in usage scenarios.
  • Link to cross-platform documentation, not just PowerShell-specific pages and repositories.
  • Clarify that AI Shell works in multiple terminal environments and provide guidance for non-Windows users.
GitHub Create Pull Request
Copilot Example prompts for Azure Copilot ...ent-docs/blob/main/articles/copilot/example-prompts.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides example prompts for both Azure CLI and PowerShell, but PowerShell is presented as a distinct scenario, and there are multiple PowerShell-specific examples. The CLI examples do not specify Linux or Bash, and PowerShell is a Windows-centric tool, which may suggest a Windows-first approach. There are no explicit Linux shell (bash) or cross-platform scripting examples, and Windows tools (PowerShell) are mentioned separately and in detail. The only explicit Linux reference is in the prompt about creating a Linux VM and SSHing into it, but there are no Linux shell scripting or management examples.
Recommendations
  • Add example prompts for managing Azure resources using Bash or other Linux-native tools.
  • Clarify that Azure CLI is cross-platform and provide prompts/examples for both Windows (PowerShell) and Linux (Bash) environments.
  • Include Linux-specific scenarios, such as using SSH, managing resources with Bash scripts, or troubleshooting with Linux tools.
  • Ensure parity by providing equivalent examples for both PowerShell and Bash where applicable.
  • Avoid presenting Windows tools (PowerShell) before or in isolation from Linux equivalents.
GitHub Create Pull Request
Copilot Optimization agent capabilities in Agents (preview) in Azure Copilot ...-docs/blob/main/articles/copilot/optimization-agent.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by explicitly mentioning PowerShell script generation for optimization tasks and listing PowerShell before Azure CLI. There are no examples or references to Linux-specific tools, shell environments, or script formats (e.g., Bash). The sample prompts and instructions focus on PowerShell and CLI, with PowerShell mentioned first and no Linux-specific guidance provided.
Recommendations
  • Provide explicit Bash script examples alongside PowerShell, especially for optimization tasks.
  • Mention Linux shell environments (e.g., Bash, Zsh) when discussing script generation and execution.
  • Ensure sample prompts include requests for Bash scripts, not just PowerShell and generic CLI.
  • Clarify that Azure CLI is cross-platform and provide usage notes for Linux users.
  • Avoid listing PowerShell before CLI or Bash unless contextually justified; alternate order or group together.
  • Add a note or section for Linux users on how to apply recommendations and run scripts in their environment.
GitHub Create Pull Request
Copilot Example prompts for Azure Copilot ...ent-docs/blob/main/articles/copilot/example-prompts.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page includes several examples that reference Windows-specific tools and patterns, such as PowerShell and Azure PowerShell scripts, with no equivalent examples for Linux shell environments (e.g., Bash). PowerShell examples are presented alongside Azure CLI, but there is no parity for Linux-native scripting or command-line environments. The documentation mentions Windows-centric tools first (PowerShell) and does not provide Linux shell alternatives, which may disadvantage Linux users or those working in cross-platform environments.
Recommendations
  • Add example prompts for Bash or Linux shell scripting, especially for resource management tasks currently shown only with PowerShell.
  • Ensure parity between PowerShell and CLI examples by providing both Windows and Linux command-line alternatives for each scenario.
  • Explicitly mention cross-platform compatibility for Azure CLI and clarify when PowerShell examples are Windows-specific.
  • Consider reordering examples so that CLI (cross-platform) appears before PowerShell (Windows-centric) to reduce perceived Windows-first bias.
  • Include prompts that demonstrate Linux administration tasks (e.g., using SSH, Bash scripts) in addition to Windows/PowerShell tasks.
GitHub Create Pull Request
Copilot Manage and migrate storage accounts using Azure Copilot ...blob/main/articles/copilot/improve-storage-accounts.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily through its focus on Azure File Sync, a Windows-centric tool, and error codes that are relevant only to Windows environments. There are no Linux-specific troubleshooting examples, tools, or migration scenarios highlighted. While migration prompts mention SMB and NFS, the detailed troubleshooting and operational guidance centers on Windows technologies, with no parity for Linux equivalents (e.g., NFS troubleshooting, Linux-based sync agents). All examples and screenshots are generic or Windows-oriented, and there is no mention of Linux command-line tools, scripts, or platform-specific considerations.
Recommendations
  • Add troubleshooting examples and guidance for Linux-based storage scenarios, such as NFS shares and Linux sync agents.
  • Include sample prompts and screenshots for Linux environments, e.g., resolving NFS mount issues or permissions errors on Linux file shares.
  • Reference Linux-native migration tools (such as rsync, azcopy for Linux, or third-party Linux migration solutions) alongside Windows tools.
  • Provide parity in error code documentation for Linux-based storage solutions and common issues encountered in Linux environments.
  • Ensure that migration, security, and resiliency sections explicitly address both Windows and Linux use cases, with examples for each.
GitHub Create Pull Request
Copilot Use Azure Copilot with AI Shell ...t-docs/blob/main/articles/copilot/ai-shell-overview.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by focusing on PowerShell and its module (AIShell), referencing only PowerShell-specific installation and documentation links, and omitting explicit Linux shell (e.g., Bash) examples or instructions. The examples and instructions prioritize PowerShell and Windows-centric tools, with no mention of Linux equivalents or cross-platform usage patterns.
Recommendations
  • Include explicit Bash or Linux shell examples alongside PowerShell examples to demonstrate parity.
  • Reference installation instructions and system requirements for both Windows (PowerShell) and Linux/macOS (Bash, Zsh, etc.).
  • Provide links to cross-platform documentation, not just PowerShell-specific resources.
  • Clarify that AI Shell works in multiple terminal environments and describe any platform-specific differences.
  • Mention how Linux users can install and use AI Shell, including any required dependencies or alternative modules.
GitHub Create Pull Request
Copilot Optimization agent capabilities in Agents (preview) in Azure Copilot ...-docs/blob/main/articles/copilot/optimization-agent.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by explicitly mentioning PowerShell script generation for optimization tasks and listing PowerShell before Azure CLI. There are no examples or references to Linux-specific tools, shell environments, or script formats (e.g., Bash). All sample prompts and instructions focus on PowerShell and CLI, with PowerShell mentioned first and no Linux/Bash script examples provided.
Recommendations
  • Include explicit examples of Bash scripts for Linux users alongside PowerShell and Azure CLI.
  • Mention Linux shell environments (e.g., Bash, zsh) when discussing script generation and execution.
  • Alternate the order of script type mentions (e.g., say 'Azure CLI or PowerShell' instead of always listing PowerShell first).
  • Clarify that generated CLI scripts are cross-platform and provide guidance for running them on Linux/macOS.
  • Add sample prompts requesting Bash scripts for optimization tasks.
  • Reference Linux tools and patterns where relevant, and ensure parity in instructions for both Windows and Linux users.
GitHub Create Pull Request
Copilot https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/copilot/ai-shell-overview.md ...t-docs/blob/main/articles/copilot/ai-shell-overview.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows/Powershell bias by emphasizing PowerShell usage, requiring the installation of a PowerShell module (AIShell), and referencing PowerShell-specific documentation and repositories. There are no explicit Linux or Bash examples, and the installation instructions point to PowerShell-centric resources, which may alienate Linux or macOS users who prefer Bash or other shells.
Recommendations
  • Provide explicit examples for Bash or other common Linux shells alongside PowerShell examples.
  • Include installation instructions and requirements for Linux/macOS environments, not just PowerShell.
  • Reference documentation and repositories that are not exclusively PowerShell-focused, or clarify cross-platform compatibility.
  • Mention and demonstrate the use of AI Shell in non-Windows terminals (e.g., bash, zsh, fish) to ensure Linux users feel equally supported.
  • Clarify whether the AIShell module is required for all platforms or only for PowerShell users, and provide alternatives if available.
GitHub Create Pull Request
Copilot https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/copilot/example-prompts.md ...ent-docs/blob/main/articles/copilot/example-prompts.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides dedicated sections and example prompts for both Azure CLI and PowerShell, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, despite CLI being cross-platform. There are multiple PowerShell-specific examples, and no Bash or Linux shell scripting examples are provided. The documentation mentions creating and SSH-ing into Linux VMs, but does not provide Linux-specific command-line or scripting examples. Windows tools (PowerShell) are featured, but Linux equivalents (Bash, shell scripts) are missing.
Recommendations
  • Add example prompts for Bash or Linux shell scripting to match PowerShell coverage.
  • Include references to Linux-native tools (e.g., Bash, SSH, scp) in scenarios where PowerShell is mentioned.
  • Ensure that CLI examples clarify cross-platform compatibility and, where relevant, provide both Windows and Linux command-line patterns.
  • Consider adding a table or section that explicitly compares PowerShell and Bash usage for common Azure tasks.
  • Review prompt examples to ensure Linux users see their workflows represented equally alongside Windows/PowerShell.
GitHub Create Pull Request
Copilot https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/copilot/improve-storage-accounts.md ...blob/main/articles/copilot/improve-storage-accounts.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily through its focus on Azure File Sync, which is a Windows-only tool, and the absence of Linux-specific migration or troubleshooting examples. Migration scenarios mention SMB (Windows) and NFS (Linux/UNIX), but do not provide parity in examples or troubleshooting for Linux environments. There are no references to Linux-native tools, commands, or issues, and troubleshooting is centered on Windows-centric error codes and patterns.
Recommendations
  • Include Linux-specific migration scenarios and troubleshooting examples, such as issues with NFS mounts, permissions, or SELinux/AppArmor.
  • Provide sample prompts and screenshots for Linux environments, e.g., migrating data from Linux servers or handling Linux file system errors.
  • Mention Linux-native tools (rsync, scp, azcopy on Linux, etc.) alongside Windows tools like Azure File Sync.
  • Balance coverage by adding sections or examples for Linux administrators, ensuring that both Windows and Linux use cases are equally represented.
  • Reference common Linux error codes or troubleshooting steps when discussing migration and sync issues.
GitHub Create Pull Request
Copilot https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/copilot/optimization-agent.md ...-docs/blob/main/articles/copilot/optimization-agent.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by explicitly mentioning PowerShell script generation before Azure CLI, using a sample prompt that requests a PowerShell script, and lacking any Linux-specific examples or references. There is no mention of Bash, Linux shell environments, or cross-platform script compatibility. The language and examples assume familiarity with Windows tooling and do not provide parity for Linux users.
Recommendations
  • Provide explicit examples of both PowerShell and Bash/Azure CLI scripts for optimization tasks.
  • Mention Linux environments and clarify that Azure CLI is cross-platform, including usage notes for Bash or other shells.
  • Balance sample prompts to include requests for Bash scripts or Linux-compatible automation.
  • Add a section highlighting cross-platform support and any differences in script execution between Windows and Linux environments.
  • Ensure that references to scripting tools do not default to Windows-first (e.g., list Azure CLI before PowerShell or present both together).
GitHub Create Pull Request
Copilot https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/copilot/ai-shell-overview.md ...t-docs/blob/main/articles/copilot/ai-shell-overview.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows and PowerShell environments. It repeatedly references PowerShell and the AIShell PowerShell module, with no mention of Bash, Linux, or cross-platform installation instructions. All examples and guidance focus on Azure CLI and PowerShell, omitting Linux-native shells and tools. The installation instructions specifically require a PowerShell module, and all documentation links point to PowerShell-centric resources.
Recommendations
  • Include explicit instructions and examples for using AI Shell with Bash or other Linux shells, not just PowerShell.
  • Provide installation steps for Linux and macOS environments, ensuring parity with Windows instructions.
  • Reference and link to cross-platform or Linux-specific documentation, not only PowerShell resources.
  • Show example workflows and troubleshooting steps using Bash or zsh, alongside PowerShell examples.
  • Clarify whether the AIShell module is available for non-Windows platforms, and if so, provide guidance for those users.
GitHub Create Pull Request
Copilot https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/copilot/capabilities.md ...gement-docs/blob/main/articles/copilot/capabilities.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. Script generation examples specifically mention PowerShell before Linux equivalents (Azure CLI, Terraform, Bicep), and troubleshooting scenarios reference Windows-centric tools (Power BI, Arc server extension) without explicit mention of Linux alternatives. The ordering and selection of examples tend to prioritize Windows-native tools and workflows, with Linux-specific tools and patterns either mentioned later or omitted.
Recommendations
  • Ensure Linux equivalents (e.g., Bash, shell scripting) are mentioned alongside PowerShell in script generation sections.
  • Provide troubleshooting examples that reference common Linux tools and scenarios (e.g., SSH, systemd, journalctl, Linux VM diagnostics).
  • When listing script generation capabilities, alternate or balance the order between Windows and Linux tools (e.g., mention Azure CLI and Bash scripts before or alongside PowerShell).
  • Explicitly state that Azure Copilot supports both Windows and Linux environments, and provide examples for both.
  • Include references to Linux-specific deployment and management workflows (e.g., Ansible, cloud-init) where relevant.
GitHub Create Pull Request
Copilot https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/copilot/optimization-agent.md ...-docs/blob/main/articles/copilot/optimization-agent.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by explicitly mentioning PowerShell script generation for optimization tasks and listing PowerShell before Azure CLI. No Linux-specific examples or shell scripts (e.g., Bash) are provided, and the sample prompts focus on PowerShell and CLI without clarifying cross-platform usage or parity.
Recommendations
  • Include explicit Bash/Linux shell script examples alongside PowerShell and Azure CLI.
  • Clarify that Azure CLI is cross-platform and provide usage notes for Linux/macOS users.
  • Add sample prompts requesting Bash scripts for optimization tasks.
  • Ensure that references to script generation do not prioritize PowerShell over CLI or other cross-platform tools.
  • Mention Linux tools or workflows where relevant, and provide guidance for non-Windows environments.
GitHub Create Pull Request
Copilot https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/copilot/example-prompts.md ...ent-docs/blob/main/articles/copilot/example-prompts.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page provides example prompts for Azure Copilot, with dedicated sections for both Azure CLI and PowerShell. However, PowerShell is highlighted as a primary scripting tool, which is traditionally associated with Windows environments. PowerShell examples are given equal prominence to Azure CLI, but there is no mention of Bash, Linux shell scripting, or Linux-specific tools. Additionally, the order of examples places PowerShell immediately after Azure CLI, reinforcing a Windows-centric workflow. There are no explicit Linux command-line or shell script examples, and no references to Linux-native management tools.
Recommendations
  • Add example prompts for Bash or Linux shell scripting to demonstrate parity with PowerShell.
  • Include references to Linux-native tools (such as SSH, scp, or systemctl) where relevant.
  • Alternate the order of CLI and PowerShell examples, or group them together under 'Scripting' to avoid implying a Windows-first approach.
  • Explicitly mention that Azure CLI is cross-platform and can be used on both Windows and Linux.
  • Provide prompts for common Linux administration tasks in Azure environments (e.g., managing Linux VMs, configuring SSH keys, using cloud-init).
GitHub Create Pull Request
Copilot Use Azure Copilot with AI Shell ...t-docs/blob/main/articles/copilot/ai-shell-overview.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page for 'Use Azure Copilot with AI Shell' demonstrates a notable bias toward Windows and PowerShell. It emphasizes PowerShell usage (including requiring the AIShell PowerShell module), references PowerShell-specific resources, and does not provide explicit examples or guidance for Linux/macOS users or alternative shells. There are no Linux/macOS installation instructions or examples, and the documentation links point to PowerShell-centric resources.
Recommendations
  • Provide explicit instructions and examples for installing and using AI Shell on Linux and macOS terminals (e.g., bash, zsh).
  • Clarify whether the AIShell module is available or necessary for non-Windows platforms, or provide alternative modules/tools if needed.
  • Include examples of AI Shell generating Azure CLI commands in Linux/macOS environments, not just PowerShell.
  • Reference cross-platform documentation and repositories, not only PowerShell-specific ones.
  • Add a section addressing platform compatibility and any limitations for non-Windows users.
GitHub Create Pull Request
Copilot Optimization agent capabilities in Agents (preview) in Azure Copilot ...-docs/blob/main/articles/copilot/optimization-agent.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation mentions both Azure CLI and PowerShell script generation, but the sample prompts explicitly show PowerShell first and only mention CLI generically, without specifying Bash or Linux-specific usage. There are no Linux/macOS-specific examples or references to shell environments other than PowerShell, and PowerShell is presented as the default scripting option in the sample prompts.
Recommendations
  • Provide explicit examples of both PowerShell and Bash/Azure CLI scripts in sample prompts, ensuring parity for Linux/macOS users.
  • Clarify that Azure CLI scripts can be used in Bash or other shell environments on Linux/macOS.
  • Include a note or section on running optimization scripts on Linux/macOS, with links to relevant Azure CLI documentation.
  • Alternate the order of PowerShell and CLI examples, or present them side-by-side, to avoid Windows-first bias.
GitHub Create Pull Request
Copilot Use Azure Copilot with AI Shell ...t-docs/blob/main/articles/copilot/ai-shell-overview.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. It repeatedly references PowerShell and its module (AIShell), links to PowerShell-specific documentation, and provides no explicit examples or instructions for Linux or macOS users. The installation section only mentions the PowerShell module, and all external links point to PowerShell resources. There are no Bash or Linux-native command examples, nor any mention of platform-specific differences or requirements for non-Windows environments.
Recommendations
  • Include explicit instructions and examples for Linux/macOS users, such as Bash shell usage.
  • Clarify whether AI Shell can be used outside PowerShell (e.g., in Bash, zsh, etc.), and provide installation steps for those environments.
  • Add links to cross-platform or Linux/macOS-specific documentation.
  • Ensure command examples alternate between Azure CLI (cross-platform) and PowerShell, or show both side-by-side.
  • Mention any platform-specific requirements or limitations.
GitHub Create Pull Request
Copilot Optimization agent capabilities in Agents (preview) in Azure Copilot ...-docs/blob/main/articles/copilot/optimization-agent.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page shows a moderate Windows bias. PowerShell is explicitly mentioned in sample prompts before Azure CLI, and the example prompt specifically asks for a PowerShell script, with CLI mentioned only generically. No Linux/macOS-specific instructions, examples, or considerations are provided, and there is no mention of Bash or shell scripting. The documentation assumes familiarity with PowerShell, which is primarily a Windows tool, and does not provide parity for Linux/macOS users.
Recommendations
  • Add explicit Bash or shell script examples alongside PowerShell and Azure CLI.
  • When listing script generation options, mention Azure CLI and Bash equally with PowerShell.
  • Provide sample prompts that request Bash or CLI scripts, not just PowerShell.
  • Clarify that Azure CLI works cross-platform and provide guidance for Linux/macOS users.
  • Consider the order of examples: alternate or randomize PowerShell and CLI/Bash to avoid Windows-first bias.
GitHub Create Pull Request
Copilot Azure Copilot capabilities ...gement-docs/blob/main/articles/copilot/capabilities.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias by listing 'Generate PowerShell scripts' before Linux-oriented scripting options (such as Azure CLI and Terraform), and by referencing PowerShell specifically as a supported automation example. There are no explicit Linux shell (bash) or Linux tool examples, and Windows-centric tools (PowerShell) are mentioned by name, while Linux equivalents are not. No Linux-specific troubleshooting or usage patterns are described.
Recommendations
  • Add explicit examples and references for Linux users, such as bash scripting and Linux command-line tools.
  • Mention Linux shell script generation alongside PowerShell and Azure CLI, and provide parity in example coverage.
  • Include troubleshooting scenarios and examples relevant to Linux environments, such as SSH, systemd, or Linux-specific error messages.
  • Ensure that references to scripting and automation tools are balanced, listing Azure CLI, bash, and PowerShell together rather than prioritizing Windows-centric tools.
  • Where possible, provide links to documentation or guides for both Windows and Linux workflows.
GitHub Create Pull Request
Copilot https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/copilot/capabilities.md ...gement-docs/blob/main/articles/copilot/capabilities.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page exhibits mild Windows bias by listing PowerShell script generation before Linux-oriented equivalents and referencing Windows-centric tools (PowerShell) in the 'Write and optimize code' section. While Azure CLI and Terraform/Bicep are mentioned, PowerShell is given equal or greater prominence, and there are no explicit Linux shell (bash) or Linux-specific troubleshooting examples. No Linux-first examples or tools are highlighted, and the troubleshooting scenarios reference Windows-centric products (Power BI) without Linux alternatives.
Recommendations
  • Add explicit Linux/bash shell script generation examples alongside PowerShell.
  • Ensure Linux tools (e.g., bash, SSH, Linux VM management) are mentioned with parity to Windows/PowerShell.
  • Provide troubleshooting examples relevant to Linux environments (e.g., issues with Linux VMs, SSH connectivity, Linux containers).
  • When listing script generation capabilities, alternate or randomize the order of Windows and Linux tools, or group them together to avoid implicit prioritization.
  • Reference Linux-native tools and workflows (e.g., systemd, journalctl, Linux package management) where appropriate.
GitHub Create Pull Request
Copilot Example prompts for Azure Copilot ...ent-docs/blob/main/articles/copilot/example-prompts.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides example prompts for Azure Copilot across a wide range of Azure services. While most examples are platform-neutral or reference cross-platform tools (such as Azure CLI), there is a mild Windows bias in the ordering and representation of scripting tools: PowerShell examples are given their own section and appear immediately after Azure CLI, with no equivalent section for Bash or Linux shell scripting. No Linux/macOS-specific tools or examples (such as Bash scripts or SSH commands) are provided alongside PowerShell, and PowerShell is presented as a primary automation tool, which may create friction for Linux/macOS users who prefer Bash or other shells.
Recommendations
  • Add example prompts for Bash or Linux shell scripting alongside PowerShell and Azure CLI, such as 'How do I create a resource group using Bash?' or 'Generate a Bash script to list all VMs.'
  • Explicitly mention that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
  • Consider reordering or grouping scripting examples to avoid implying PowerShell is the default or preferred option for all users.
  • Include prompts relevant to Linux/macOS workflows, such as SSH commands, Bash automation, or integration with Linux tools.
GitHub Create Pull Request
Copilot Azure Copilot capabilities ...gement-docs/blob/main/articles/copilot/capabilities.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation lists 'Generate PowerShell scripts' as a primary example of Azure Copilot's code generation capabilities, and PowerShell is mentioned before Linux-native equivalents such as Bash or Azure CLI. While the page also references Azure CLI and Terraform, the ordering and explicit PowerShell mention may subtly prioritize Windows tooling. No explicit Linux examples or tools (e.g., Bash scripts) are given, and PowerShell is not contextualized as cross-platform.
Recommendations
  • Add explicit examples or references to Linux-native scripting (e.g., Bash) alongside PowerShell.
  • Clarify that PowerShell is cross-platform, or provide guidance for Linux/macOS users on using PowerShell Core.
  • Ensure that Azure CLI examples are given equal prominence and ordering to PowerShell.
  • Consider including links or references to Linux/macOS-specific workflows where relevant.
GitHub Create Pull Request
Copilot Azure Copilot capabilities ...gement-docs/blob/main/articles/copilot/capabilities.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page lists both Azure CLI and PowerShell script generation as Copilot capabilities, but PowerShell is mentioned directly after CLI and before other Linux-native tools. No Linux/macOS-specific tools or shell examples (e.g., Bash) are referenced, and PowerShell (a Windows-centric tool, though cross-platform) is highlighted as a primary scripting option. There are no explicit Linux/macOS examples, nor are Linux-specific patterns or tools (such as Bash, zsh, or Linux package managers) mentioned. The ordering and emphasis suggest a mild Windows-first bias.
Recommendations
  • Include explicit examples or references for Linux/macOS users, such as Bash shell scripts or zsh.
  • Mention that Azure CLI and PowerShell are both cross-platform, and clarify usage on Linux/macOS.
  • Add links or examples for Linux-native tools and workflows where relevant.
  • Ensure that script generation capabilities highlight parity between PowerShell and Bash, and show examples for both.
GitHub Create Pull Request
← Previous Page 1 of 2 Next →