Azure Portal

37
Total Pages
29
Linux-Friendly Pages
8
Pages with Bias
21.6%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

109 issues found
Showing 76-100 of 109 flagged pages
Azure Portal Programmatically create Azure Dashboards ...tal/azure-portal-dashboards-create-programmatically.md
Low Priority View Details →
Scanned: 2026-02-18 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides examples for deploying Azure dashboards using Azure CLI and Azure PowerShell. Azure CLI is cross-platform, but Azure PowerShell is primarily associated with Windows, though it is available on Linux/macOS. The PowerShell section is presented after the CLI section, and all command-line examples use Azure CLI (which is Linux-friendly) or PowerShell (which is Windows-centric). No Windows-only tools or patterns are prioritized, and Linux/macOS users are not excluded from any workflow. However, the inclusion of PowerShell may subtly reinforce Windows-centric patterns, though Azure CLI is shown first.
Recommendations
  • Clarify that Azure PowerShell is available cross-platform (Linux/macOS) and provide installation links for non-Windows users.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
  • Consider adding a short note or example showing how to run Azure CLI commands on Linux/macOS (e.g., bash shell).
  • If possible, provide links to Azure CLI and PowerShell installation guides for all platforms.
GitHub Create Pull Request
Azure Portal Use Azure Copilot with the Azure mobile app ...main/articles/azure-portal/mobile-app/azure-copilot.md
Low Priority View Details →
Scanned: 2026-02-18 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation mentions 'Generating CLI and PowerShell scripts' as a key scenario, listing PowerShell (a Windows-centric tool) alongside CLI. While Azure CLI is cross-platform, PowerShell is often associated with Windows, and its mention may subtly prioritize Windows users. However, there are no exclusive Windows examples, tools, or patterns, and the overall guidance is platform-neutral.
Recommendations
  • Clarify that both Azure CLI and PowerShell are cross-platform tools, and provide examples or links for using them on Linux/macOS.
  • Consider mentioning Bash or shell scripting as alternatives for Linux/macOS users, or explicitly state that generated scripts can target multiple platforms.
  • Ensure future examples or screenshots include parity for Linux/macOS environments where applicable.
GitHub Create Pull Request
Azure Portal Use Azure Copilot with the Azure mobile app ...main/articles/azure-portal/mobile-app/azure-copilot.md
Low Priority View Details →
Scanned: 2026-02-17 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation mentions 'Generating CLI and PowerShell scripts' as a key scenario, listing PowerShell alongside CLI. While PowerShell is primarily associated with Windows, CLI (Azure CLI) is cross-platform. However, PowerShell is mentioned before any Linux-specific shell (such as Bash), and there are no explicit Linux/macOS shell examples or references. No actual script examples are given, so the bias is limited to the order and naming.
Recommendations
  • Clarify that Azure Copilot can generate scripts for both PowerShell and Bash (or other Linux shells), not just PowerShell.
  • Explicitly mention Bash or Linux/macOS shell support alongside PowerShell and CLI.
  • If examples are added in the future, ensure parity by providing both PowerShell and Bash examples.
GitHub Create Pull Request
Azure Portal Get subscription and tenant IDs in the Azure portal ...in/articles/azure-portal/get-subscription-tenant-id.md
Low Priority View Details →
Scanned: 2026-02-16 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Azure PowerShell and Azure CLI options for programmatic access to subscription and tenant IDs. However, PowerShell is consistently mentioned first, and the tip sections use Windows-centric terminology (e.g., 'text document'), which may subtly prioritize Windows users. No Linux/macOS-specific examples or screenshots are provided, but the Azure CLI is referenced, which is cross-platform.
Recommendations
  • Alternate the order of PowerShell and Azure CLI mentions to avoid Windows-first bias.
  • Explicitly state that Azure CLI works on Linux and macOS, and consider adding a brief example or screenshot for those platforms.
  • Use more neutral terminology (e.g., 'text editor' instead of 'text document') to avoid Windows-centric language.
  • Ensure parity in programmatic examples, such as showing both PowerShell and CLI commands side-by-side.
GitHub Create Pull Request
Azure Portal Use Azure Copilot with the Azure mobile app ...main/articles/azure-portal/mobile-app/azure-copilot.md
Low Priority View Details →
Scanned: 2026-02-16 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation mentions generating CLI and PowerShell scripts as a key scenario, listing PowerShell before CLI. This ordering subtly prioritizes Windows tooling. No explicit Linux/macOS examples or tools are referenced, and PowerShell is presented as a primary scripting option, which may create friction for Linux/macOS users who typically use Bash or other shells.
Recommendations
  • Explicitly mention Bash or shell script generation alongside PowerShell and CLI.
  • Provide examples or clarify that Azure Copilot can generate scripts for Bash and other Linux/macOS environments.
  • Reorder the list to avoid always listing Windows tools first, or use neutral phrasing (e.g., 'Generating scripts for Azure CLI, Bash, and PowerShell').
GitHub Create Pull Request
Azure Portal Programmatically create Azure Dashboards ...tal/azure-portal-dashboards-create-programmatically.md
Low Priority View Details →
Scanned: 2026-02-16 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides deployment examples for both Azure CLI and Azure PowerShell, but the PowerShell section is given its own heading and is presented after the CLI section. The CLI examples are cross-platform, but the PowerShell section is Windows-centric, as PowerShell is most commonly used on Windows (though available on Linux/macOS). There are no explicit Linux/macOS shell examples (e.g., Bash), but the CLI commands are suitable for all platforms. No Windows-only tools or patterns are used, and the documentation does not omit Linux equivalents.
Recommendations
  • Clarify that Azure CLI commands work on Windows, Linux, and macOS, and consider explicitly stating this in the CLI section.
  • Optionally, add a short Bash shell script example for deploying a dashboard template to reinforce Linux parity.
  • In the PowerShell section, mention that PowerShell Core is available cross-platform, or link to instructions for installing PowerShell on Linux/macOS.
  • Continue to provide Azure CLI examples as the primary cross-platform method, and ensure PowerShell is presented as an alternative, not the default.
GitHub Create Pull Request
Azure Portal Use Azure Copilot with the Azure mobile app ...main/articles/azure-portal/mobile-app/azure-copilot.md
Low Priority View Details →
Scanned: 2026-02-15 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation mentions 'Generating CLI and PowerShell scripts' as a key scenario, listing PowerShell (a Windows-centric tool) alongside CLI, but does not provide explicit Linux/bash examples or clarify parity. PowerShell is mentioned before Linux shell equivalents, which may subtly prioritize Windows users.
Recommendations
  • Clarify that Azure Copilot can generate both PowerShell and Bash/CLI scripts, and provide examples for each.
  • Explicitly mention Linux/macOS compatibility where relevant, especially for script generation.
  • Consider listing Bash/CLI examples before or alongside PowerShell to avoid Windows-first ordering.
  • Add a note about script types supported and any limitations for Linux/macOS users.
GitHub Create Pull Request
Azure Portal Get subscription and tenant IDs in the Azure portal ...in/articles/azure-portal/get-subscription-tenant-id.md
Low Priority View Details →
Scanned: 2026-02-15 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure PowerShell and Azure CLI options for programmatic access, but PowerShell is consistently mentioned first and receives slightly more prominence. There are no Windows-only tools or patterns, and both Windows and Linux users can use the Azure portal and Azure CLI. However, the ordering and phrasing may subtly favor Windows users by listing PowerShell before CLI and referring to 'text document' (which may imply Notepad/Windows).
Recommendations
  • Alternate the order of PowerShell and CLI mentions, or list CLI first to better reflect cross-platform parity.
  • Clarify that Azure CLI is fully cross-platform and can be used on Linux, macOS, and Windows.
  • Use neutral language such as 'text editor' instead of 'text document' to avoid implying Windows tools.
  • Consider adding a brief note that both PowerShell and CLI are available on all major platforms, or link to installation guides for each.
GitHub Create Pull Request
Azure Portal Programmatically create Azure Dashboards ...tal/azure-portal-dashboards-create-programmatically.md
Low Priority View Details →
Scanned: 2026-02-15 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying dashboard templates, but the PowerShell section is given equal prominence to the CLI section, and there is no explicit mention of Linux/macOS compatibility for PowerShell commands. The Azure CLI is cross-platform and shown first, but the PowerShell section could be interpreted as Windows-centric, especially since no Bash or shell-specific guidance is given. All tools referenced (Azure CLI, Azure PowerShell, REST API, Portal) are cross-platform, but the inclusion of PowerShell without clarifying its cross-platform availability may create a mild Windows bias.
Recommendations
  • Clarify that Azure PowerShell is available on Linux and macOS, not just Windows.
  • Explicitly state that Azure CLI commands work on all platforms (Windows, Linux, macOS).
  • Consider adding a short Bash shell script example for deploying the dashboard template using Azure CLI, to reinforce Linux parity.
  • If possible, mention that all deployment methods (Portal, CLI, PowerShell, REST) are supported on all major OSes.
GitHub Create Pull Request
Azure Portal Use Azure Copilot with the Azure mobile app ...main/articles/azure-portal/mobile-app/azure-copilot.md
Low Priority View Details →
Scanned: 2026-02-14 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation mentions 'Generating CLI and PowerShell scripts' as a key scenario, listing PowerShell alongside CLI. PowerShell is primarily associated with Windows, while CLI (Azure CLI) is cross-platform. However, there are no explicit examples or instructions favoring Windows tools, nor are Linux/macOS equivalents omitted. The mention of PowerShell is not exclusive or prioritized above CLI, but its inclusion without clarification may subtly suggest Windows bias.
Recommendations
  • Clarify that Azure Copilot can generate scripts for both Azure CLI (cross-platform) and PowerShell (primarily Windows, but also available on Linux/macOS).
  • Consider mentioning Bash or shell scripts as additional options for Linux/macOS users if supported.
  • Provide examples or links that demonstrate script generation for both CLI and PowerShell, ensuring parity.
  • Explicitly state that Azure CLI is cross-platform and PowerShell is available on multiple OSes, to avoid assumptions of Windows-only usage.
GitHub Create Pull Request
Azure Portal Get subscription and tenant IDs in the Azure portal ...in/articles/azure-portal/get-subscription-tenant-id.md
Low Priority View Details →
Scanned: 2026-02-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Azure PowerShell and Azure CLI options for programmatically retrieving subscription and tenant IDs. However, PowerShell is consistently mentioned first, and the examples reference PowerShell modules and cmdlets before CLI equivalents. There are no Windows-only tools or patterns, but the ordering and emphasis may subtly favor Windows users. All instructions for using the Azure portal are platform-neutral.
Recommendations
  • Alternate the order in which PowerShell and CLI options are presented, or explicitly state that both are cross-platform.
  • Clarify that Azure CLI works on Windows, Linux, and macOS, and provide links or notes to installation guides for non-Windows platforms.
  • Consider including brief example commands for both PowerShell and CLI inline, rather than only linking out.
  • Ensure parity in depth and visibility between PowerShell and CLI guidance.
GitHub Create Pull Request
Azure Portal Use Azure Copilot with the Azure mobile app ...main/articles/azure-portal/mobile-app/azure-copilot.md
Low Priority View Details →
Scanned: 2026-02-13 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation mentions 'Generating CLI and PowerShell scripts' as a key scenario, listing PowerShell alongside CLI. While this is a minor bias, as PowerShell is often associated with Windows, the documentation does not provide examples or instructions that are Windows-specific, nor does it omit Linux/macOS equivalents. The rest of the content is platform-neutral, focusing on the Azure mobile app available for both iOS and Android.
Recommendations
  • Clarify that Azure Copilot can generate both Bash (for Azure CLI) and PowerShell scripts, and that these are useful for Windows, Linux, and macOS users.
  • Consider listing 'CLI and Bash scripts' before 'PowerShell scripts' to avoid implicit Windows-first ordering.
  • If examples are added in the future, ensure both PowerShell and Bash/CLI examples are provided.
GitHub Create Pull Request
Azure Portal Programmatically create Azure Dashboards ...tal/azure-portal-dashboards-create-programmatically.md
Low Priority View Details →
Scanned: 2026-02-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides deployment instructions for Azure dashboards using the Azure portal, Azure CLI, and Azure PowerShell. While the Azure CLI is cross-platform and is presented before PowerShell, the PowerShell section is included as a first-class option, which may be seen as a Windows-centric tool. However, there are no exclusive Windows tools or patterns, and all critical tasks can be completed using the Azure CLI or portal, both of which are cross-platform. The order of presentation (CLI before PowerShell) is appropriate, but the inclusion of PowerShell as a main deployment method may be seen as slightly Windows-biased. All code examples and instructions are otherwise platform-neutral.
Recommendations
  • Clarify that Azure PowerShell is available cross-platform (Windows, macOS, Linux) via PowerShell Core, to reduce perceived Windows bias.
  • Explicitly state that all deployment steps using Azure CLI and the portal are fully supported on Linux and macOS.
  • Consider adding a short note or table summarizing tool/platform compatibility for Azure CLI and PowerShell.
  • If possible, provide Bash or shell script examples for common tasks, or clarify that Azure CLI commands work in Bash and other shells.
GitHub Create Pull Request
Azure Portal Get subscription and tenant IDs in the Azure portal ...in/articles/azure-portal/get-subscription-tenant-id.md
Low Priority View Details →
Scanned: 2026-02-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Azure PowerShell and Azure CLI options for programmatic access, but PowerShell is consistently mentioned first and receives slightly more prominence. There are no explicit Linux/macOS examples or screenshots, and the use of PowerShell as the primary example may subtly favor Windows users, though Azure CLI is cross-platform and included. No Windows-only tools or patterns are used, and Linux users can complete all tasks described.
Recommendations
  • Alternate the order of PowerShell and Azure CLI mentions to avoid Windows-first bias.
  • Explicitly note that Azure CLI works on Linux/macOS and provide links or brief instructions for installation/use on those platforms.
  • Include a screenshot or example showing Azure CLI usage in a terminal (not just PowerShell).
  • Clarify that copying IDs in the portal works identically across platforms.
GitHub Create Pull Request
Azure Portal Programmatically create Azure Dashboards ...tal/azure-portal-dashboards-create-programmatically.md
Low Priority View Details →
Scanned: 2026-02-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides deployment instructions for Azure dashboards using three methods: Azure portal, Azure CLI, and Azure PowerShell. While Azure CLI is cross-platform and shown before PowerShell, the PowerShell section is included and described in detail, which may be seen as Windows-centric. Additionally, PowerShell examples are given after CLI, but no explicit Linux/macOS shell examples (such as Bash or shell scripting) are provided. The documentation mentions Azure PowerShell alongside Azure CLI and REST API in the overview, but does not provide Linux-specific guidance or examples. The order of examples (CLI before PowerShell) reduces bias, but the presence of PowerShell-specific instructions without Linux/macOS shell equivalents is a minor bias.
Recommendations
  • Clarify that Azure CLI commands work equally well on Windows, Linux, and macOS.
  • Add explicit Bash or shell scripting examples for deploying dashboards, or note that Azure CLI commands can be run in Bash or other shells on Linux/macOS.
  • Consider mentioning cross-platform compatibility of Azure PowerShell (it runs on Linux/macOS via .NET Core), or link to installation instructions for non-Windows platforms.
  • Ensure that all instructions are clear for users on Linux/macOS, not just Windows.
GitHub Create Pull Request
Azure Portal Use Azure Copilot with the Azure mobile app ...main/articles/azure-portal/mobile-app/azure-copilot.md
Low Priority View Details →
Scanned: 2026-02-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation mentions 'Generating CLI and PowerShell scripts' as a key scenario, listing PowerShell alongside CLI. While this is not strictly Windows-only, PowerShell is more commonly associated with Windows environments, and its mention before Bash or Linux shell scripting may create a subtle Windows bias. No explicit Linux/macOS examples or tools are referenced, and the documentation does not clarify parity between PowerShell and Bash or other Linux shells.
Recommendations
  • Explicitly mention Bash or Linux shell scripting alongside PowerShell and CLI in the capabilities section.
  • Provide examples or clarify that Azure Copilot can generate scripts for Bash, Linux shells, and macOS environments, not just PowerShell.
  • Consider listing CLI and Bash before PowerShell to avoid subtle Windows-first ordering.
  • Add a note about cross-platform support for generated code snippets and scripts.
GitHub Create Pull Request
Azure Portal Programmatically create Azure Dashboards ...tal/azure-portal-dashboards-create-programmatically.md
Low Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides deployment instructions for Azure dashboards using three methods: Azure portal, Azure CLI, and Azure PowerShell. The Azure CLI section is cross-platform and appears before the PowerShell section, which is Windows-centric. However, PowerShell is presented as a distinct method and includes detailed examples, potentially favoring Windows users. No Linux/macOS-specific tools or shell examples (such as Bash scripting or automation) are provided, and PowerShell is not explicitly flagged as cross-platform (though PowerShell Core is available on Linux/macOS). The documentation does not show Windows tools or patterns exclusively, but PowerShell is highlighted as a primary method alongside CLI, which may create minor friction for Linux/macOS users.
Recommendations
  • Clarify that Azure PowerShell can be used on Linux/macOS via PowerShell Core, or link to instructions for installing PowerShell on non-Windows platforms.
  • Add Bash shell scripting examples for Azure CLI deployment to demonstrate automation parity for Linux/macOS users.
  • Explicitly mention that all Azure CLI commands work on Linux, macOS, and Windows.
  • Consider providing a table or summary comparing deployment methods and their cross-platform compatibility.
GitHub Create Pull Request
Azure Portal Use Azure Copilot with the Azure mobile app ...main/articles/azure-portal/mobile-app/azure-copilot.md
Low Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation mentions generating CLI and PowerShell scripts as a key scenario, listing PowerShell alongside CLI. PowerShell is primarily associated with Windows, and its mention before Bash or Linux shell scripting may indicate a mild Windows bias. However, no exclusive Windows tools or patterns are described, and the page is focused on a cross-platform mobile app.
Recommendations
  • Explicitly mention Bash or Linux shell scripting alongside PowerShell and CLI when listing code generation capabilities.
  • Provide examples or clarify that Azure Copilot can generate scripts for both Windows (PowerShell) and Linux/macOS (Bash, CLI).
  • Ensure parity in documentation by referencing cross-platform scripting options equally.
GitHub Create Pull Request
Azure Portal Use Azure Copilot with the Azure mobile app ...main/articles/azure-portal/mobile-app/azure-copilot.md
Low Priority View Details →
Scanned: 2026-02-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation mentions 'Generating CLI and PowerShell scripts' as a key scenario, listing PowerShell alongside CLI. While this is not strictly Windows-only, PowerShell is more commonly associated with Windows environments, and its mention before Bash or Linux shell scripting may signal a Windows-first bias. No explicit Linux/macOS examples or tools are referenced, and the documentation does not clarify parity for Linux users.
Recommendations
  • Explicitly mention Bash or Linux shell scripting as supported output types for code generation.
  • Provide examples or clarify that Azure Copilot can generate scripts for Bash, Azure CLI, and PowerShell, covering all major platforms.
  • Ensure that references to scripting tools are inclusive, e.g., 'Generating CLI, Bash, and PowerShell scripts.'
  • Add a note about cross-platform compatibility for generated scripts.
GitHub Create Pull Request
Azure Portal Get subscription and tenant IDs in the Azure portal ...in/articles/azure-portal/get-subscription-tenant-id.md
Low Priority View Details →
Scanned: 2026-02-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Azure PowerShell and Azure CLI options for programmatic access, but PowerShell is consistently mentioned first and receives slightly more emphasis. While Azure CLI is cross-platform, the ordering and phrasing may subtly favor Windows users. No Windows-only tools or patterns are used, and Linux/macOS users can complete all tasks without friction.
Recommendations
  • Alternate the order in which Azure PowerShell and Azure CLI are mentioned, or explicitly note that Azure CLI is cross-platform.
  • Add brief clarifications that Azure CLI works on Linux/macOS, and PowerShell is available cross-platform but may be more familiar to Windows users.
  • Consider providing a short example command for both Azure CLI and PowerShell, rather than just linking to external docs.
GitHub Create Pull Request
Azure Portal Programmatically create Azure Dashboards ...tal/azure-portal-dashboards-create-programmatically.md
Low Priority View Details →
Scanned: 2026-02-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides examples for deploying Azure dashboards using Azure CLI and Azure PowerShell. The PowerShell section is presented after the CLI section, but PowerShell is highlighted as a primary method. Both tools are cross-platform, but PowerShell is often associated with Windows, and the documentation does not mention Bash or shell scripting alternatives. There are no explicit Linux/macOS-only examples or references to Linux-native tools. The JSON templates and Azure CLI commands are platform-agnostic, but the inclusion of PowerShell and its detailed example may create a slight Windows bias.
Recommendations
  • Clarify that Azure CLI and PowerShell are both cross-platform and supported on Linux/macOS.
  • Add explicit Bash or shell scripting examples for deploying dashboards, or note that Azure CLI commands can be run in Bash on Linux/macOS.
  • Mention that PowerShell Core (pwsh) is available on Linux/macOS, and provide guidance for Linux/macOS users where relevant.
  • Consider including a short note or section about using Azure CLI in Bash or other Linux shells.
GitHub Create Pull Request
Azure Portal Use Azure Copilot with the Azure mobile app ...main/articles/azure-portal/mobile-app/azure-copilot.md
Low Priority View Details →
Scanned: 2026-02-08 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation mentions 'Generating CLI and PowerShell scripts' as a key scenario, listing PowerShell before CLI. While both are supported, PowerShell is a Windows-centric tool, and listing it first may subtly prioritize Windows users. No explicit Linux/macOS bias or missing examples are present, but minor ordering bias exists.
Recommendations
  • List CLI (cross-platform) before PowerShell to emphasize Linux/macOS parity.
  • Clarify that both Bash (for Linux/macOS) and PowerShell (for Windows) scripts can be generated.
  • Provide examples or links showing script generation for both Bash and PowerShell, if relevant.
GitHub Create Pull Request
Azure Portal Get subscription and tenant IDs in the Azure portal ...in/articles/azure-portal/get-subscription-tenant-id.md
Low Priority View Details →
Scanned: 2026-02-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Azure PowerShell and Azure CLI options for programmatic access, but PowerShell is mentioned first in all cases and receives slightly more prominence. There are no Windows-only tools or patterns, but the ordering and phrasing may subtly favor Windows users. No Linux/macOS-specific examples or guidance are missing, as Azure CLI is cross-platform and included.
Recommendations
  • Alternate the order of PowerShell and Azure CLI mentions, or list Azure CLI first to better reflect cross-platform parity.
  • Explicitly note that Azure CLI works on Linux/macOS and provide links to installation instructions for those platforms.
  • Consider adding a brief example command for both Azure CLI and PowerShell in the main body, not just in tips, to reinforce parity.
  • Use neutral language such as 'You can use Azure CLI or PowerShell...' instead of always leading with PowerShell.
GitHub Create Pull Request
Azure Portal Use Azure Copilot with the Azure mobile app ...main/articles/azure-portal/mobile-app/azure-copilot.md
Low Priority View Details →
Scanned: 2026-02-05 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation mentions 'Generating CLI and PowerShell scripts' as a key scenario, listing PowerShell (Windows-centric) alongside CLI without specifying Linux/macOS equivalents or giving parity to Bash or shell scripting. No explicit Linux/macOS examples or tools are referenced, and PowerShell is mentioned before any Linux-native scripting options.
Recommendations
  • Clarify that Azure Copilot can generate scripts for Bash, Azure CLI, and other Linux/macOS environments, not just PowerShell.
  • Explicitly mention Bash or shell scripting as supported output formats when discussing script generation.
  • Provide examples or scenarios for Linux/macOS users, such as generating Bash scripts or using Azure CLI on non-Windows platforms.
  • Avoid listing PowerShell before CLI or Bash unless there is a technical reason for prioritizing Windows tools.
GitHub Create Pull Request
Azure Portal Programmatically create Azure Dashboards ...tal/azure-portal-dashboards-create-programmatically.md
Low Priority View Details →
Scanned: 2026-02-03 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides deployment instructions for both Azure CLI and Azure PowerShell, but the PowerShell section is given its own dedicated heading and example, while Bash or Linux shell scripting is not mentioned. The Azure CLI section is platform-agnostic, but PowerShell is called out separately, which may suggest a slight Windows bias. However, all critical tasks can be completed using the Azure CLI, which is fully supported on Linux/macOS. The order of presentation (CLI before PowerShell) is appropriate, but the lack of explicit Bash/shell scripting examples or mention of cross-platform scripting in the PowerShell section is a minor bias.
Recommendations
  • Clarify that Azure CLI commands work on Windows, Linux, and macOS, and can be used in Bash or other shells.
  • Consider adding a short Bash script example for deploying dashboards using Azure CLI, to reinforce Linux parity.
  • In the PowerShell section, note that Azure PowerShell is also available cross-platform (via PowerShell Core), or link to installation instructions for Linux/macOS.
  • If possible, add a table summarizing deployment options by platform (Portal, CLI, PowerShell) to make parity explicit.
GitHub Create Pull Request
← Previous Page 4 of 5 Next →