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 26-50 of 109 flagged pages
Azure Portal Get subscription and tenant IDs in the Azure portal ...in/articles/azure-portal/get-subscription-tenant-id.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides both Azure PowerShell and Azure CLI options for programmatic access, but PowerShell is consistently mentioned first and given prominence. PowerShell is a Windows-centric tool, and its prioritization may suggest a Windows bias. No explicit Linux-only tools or patterns are mentioned, and examples do not highlight Linux-specific usage or shell environments.
Recommendations
  • Alternate the order of PowerShell and CLI mentions, or mention Azure CLI first, as it is cross-platform and widely used on Linux.
  • Include explicit examples or screenshots showing usage in Linux terminals (e.g., bash), and clarify that Azure CLI works on Linux, macOS, and Windows.
  • Add notes or tips for Linux/macOS users, such as how to install and use Azure CLI in those environments.
  • Avoid implying that copying to clipboard or pasting is a Windows-only workflow; mention equivalent actions in Linux/macOS.
  • Consider referencing Bash scripts or other Linux-native automation approaches where relevant.
GitHub Create Pull Request
Azure Portal https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-portal/azure-portal-dashboards-create-programmatically.md ...tal/azure-portal-dashboards-create-programmatically.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 demonstrates mild Windows bias. In the 'Overview' and deployment sections, Azure PowerShell is mentioned before Azure CLI, and PowerShell is listed as a primary method for deployment alongside REST API and CLI. There are no explicit Linux shell examples, and PowerShell is referenced in both the main text and in links, suggesting a preference for Windows tooling. However, Azure CLI is also mentioned, and the JSON templates themselves are platform-neutral. The dashboard examples do include links to both Linux and Windows VM creation guides, with Linux listed first.
Recommendations
  • Ensure Azure CLI is mentioned before or alongside PowerShell in all lists and instructions, as CLI is cross-platform.
  • Add explicit Bash or shell script examples for deploying templates, to demonstrate Linux parity.
  • Clarify that both Azure CLI and PowerShell are available on all platforms, and provide links to installation guides for Linux users.
  • Avoid listing Windows-specific tools (PowerShell) before cross-platform tools (CLI) unless contextually justified.
  • Consider including a section or callout for Linux/macOS users, highlighting any platform-specific considerations.
GitHub Create Pull Request
Azure Portal https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-portal/get-subscription-tenant-id.md ...in/articles/azure-portal/get-subscription-tenant-id.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 presents both Azure PowerShell and Azure CLI options for programmatic access, but PowerShell is consistently mentioned first and sometimes exclusively (e.g., 'Get-AzSubscription' is referenced before 'az account list'). This ordering and emphasis may subtly favor Windows users, as PowerShell is traditionally associated with Windows environments, while Azure CLI is cross-platform and more commonly used on Linux/macOS. There are no explicit Linux examples or references to Linux-specific tools or workflows.
Recommendations
  • Alternate the order of PowerShell and Azure CLI references, or list Azure CLI first to reflect its cross-platform nature.
  • Explicitly mention that Azure CLI works natively on Linux and macOS, and provide example commands for these platforms.
  • Include screenshots or instructions showing use of Azure CLI in a Linux terminal.
  • Add a note clarifying that both PowerShell and CLI are available on all major platforms, and link to installation guides for Linux/macOS.
  • Where possible, provide parity in examples and tips for both Windows (PowerShell) and Linux/macOS (CLI).
GitHub Create Pull Request
Azure Portal https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-portal/quickstart-portal-dashboard-azure-cli.md .../azure-portal/quickstart-portal-dashboard-azure-cli.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by providing only a Windows VM creation example (using the 'win2016datacenter' image) and referencing Windows-specific username and password requirements. No Linux VM creation example or Linux-specific guidance is provided, despite Azure CLI supporting both platforms equally. The documentation implicitly prioritizes Windows by omitting Linux alternatives.
Recommendations
  • Add a Linux VM creation example alongside the Windows example, using a popular image such as 'UbuntuLTS'.
  • Include links to Linux-specific username and password requirements, similar to the Windows references.
  • Clarify that Azure CLI commands work for both Windows and Linux VMs, and provide guidance for customizing the dashboard template for Linux VMs.
  • Ensure that dashboard template customization instructions mention both Windows and Linux VM resource types and monitoring options.
GitHub Create Pull Request
Azure Portal https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-portal/azure-portal-dashboards-create-programmatically.md ...tal/azure-portal-dashboards-create-programmatically.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias. In the 'Overview' and deployment sections, Azure PowerShell is listed before Azure CLI, and PowerShell is given equal prominence to CLI and REST API, despite CLI being cross-platform and more widely used on Linux. There are no explicit Linux shell examples, and PowerShell is referenced as a primary method for deployment. However, the dashboard JSON and links do reference both Linux and Windows VMs equally, and there are no Windows-only tools or patterns shown.
Recommendations
  • List Azure CLI before PowerShell in tool lists and deployment instructions, as CLI is cross-platform and preferred on Linux.
  • Provide explicit Bash or shell examples for Linux users alongside PowerShell examples.
  • Clarify that both Azure CLI and PowerShell are available on all platforms, but CLI is native to Linux.
  • Add links to Linux-specific quickstarts or documentation where relevant.
  • Consider including a note or section for deploying dashboards from Linux environments, with example commands.
GitHub Create Pull Request
Azure Portal https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-portal/get-subscription-tenant-id.md ...in/articles/azure-portal/get-subscription-tenant-id.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
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 tips and links, and the CLI is often presented as an alternative rather than an equal. There are no explicit Linux-only examples, and PowerShell (historically Windows-centric) is given prominence, which may subtly favor Windows users.
Recommendations
  • Alternate the order of PowerShell and Azure CLI mentions, or mention CLI first in some cases to balance exposure.
  • Explicitly state that Azure CLI works cross-platform (Windows, Linux, macOS) and provide examples of usage on Linux terminals.
  • Include screenshots or instructions for copying IDs using Azure CLI in a Linux shell, not just via the portal.
  • Clarify that PowerShell Core is available cross-platform, if referenced, to reduce Windows association.
  • Add a section or tip for Linux users, e.g., how to install and use Azure CLI on Linux to retrieve subscription and tenant IDs.
GitHub Create Pull Request
Azure Portal https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-portal/mobile-app/microsoft-copilot-in-azure.md .../azure-portal/mobile-app/microsoft-copilot-in-azure.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation mentions 'Generate CLI and PowerShell scripts' as a key capability, listing PowerShell (a Windows-centric tool) alongside CLI. PowerShell is referenced before any Linux-specific shell or scripting language, and there are no explicit examples or mentions of Bash, Linux shell scripts, or Linux-specific tools. This ordering and emphasis may suggest a Windows-first or PowerShell-heavy bias, even though CLI is cross-platform.
Recommendations
  • Explicitly mention Bash or Linux shell script generation as a capability alongside PowerShell and CLI.
  • Provide examples or clarify that generated CLI scripts are compatible with both Windows and Linux environments.
  • Add a note or section highlighting Linux parity, ensuring users know that Azure Copilot supports Linux workflows and tools.
  • When listing script generation capabilities, alternate or randomize the order (e.g., 'Generate Bash, CLI, and PowerShell scripts') to avoid implicit prioritization.
GitHub Create Pull Request
Azure Portal https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-portal/quickstart-portal-dashboard-azure-cli.md .../azure-portal/quickstart-portal-dashboard-azure-cli.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows by providing only a Windows VM creation example (using the 'win2016datacenter' image) and referencing Windows-specific username and password requirements. There are no equivalent Linux VM creation examples or references to Linux-specific requirements, which may hinder Linux users from following the guide effectively.
Recommendations
  • Include a Linux VM creation example alongside the Windows example, such as using '--image UbuntuLTS' and SSH key authentication.
  • Reference Linux-specific username and password/SSH requirements in addition to Windows requirements.
  • Clarify that the dashboard template and Azure CLI commands work equally well for Linux VMs.
  • Ensure that downloadable templates and instructions are not tailored exclusively to Windows environments.
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-03-10 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 mentioned first in all cases, and the CLI is presented as an alternative. There are no Windows-only tools or commands, but the ordering and phrasing subtly favor Windows/PowerShell users. No Linux/macOS-specific examples or considerations are provided.
Recommendations
  • Present Azure CLI and PowerShell options in parallel, or alternate which is listed first.
  • Explicitly note that Azure CLI works cross-platform (Windows, Linux, macOS), while PowerShell is most common on Windows.
  • Consider including example CLI commands for Linux/macOS users, such as showing CLI output in a Bash terminal.
  • Add a brief note that both tools are available on all platforms, but CLI is often preferred on Linux/macOS.
GitHub Create Pull Request
Azure Portal Programmatically create Azure Dashboards ...tal/azure-portal-dashboards-create-programmatically.md
Low Priority View Details →
Scanned: 2026-03-10 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 the Azure portal, Azure CLI, and Azure PowerShell. While the Azure CLI is cross-platform and featured before PowerShell, the PowerShell section is prominent and included as a distinct method. The documentation does not show any Linux/macOS-specific tools or shell examples (e.g., Bash), nor does it clarify that Azure PowerShell is available on Linux/macOS. The ordering of examples (CLI before PowerShell) is positive, but the PowerShell section could be perceived as Windows-centric due to its historical association with Windows.
Recommendations
  • Explicitly state that Azure CLI and Azure PowerShell are both cross-platform and supported on Windows, Linux, and macOS.
  • Add Bash shell examples for Azure CLI usage, demonstrating deployment from a Linux/macOS terminal.
  • Clarify that Azure PowerShell can be used on Linux/macOS, and provide installation links or notes.
  • Consider including REST API examples using curl or similar cross-platform tools.
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-03-10 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 (which typically refers to Azure CLI, a cross-platform tool). PowerShell is traditionally associated with Windows, and its mention before Bash or Linux shell scripting may subtly prioritize Windows users. However, the documentation does not provide actual script examples or instructions that are Windows-specific, nor does it omit Linux/macOS equivalents.
Recommendations
  • Clarify that Azure Copilot can generate scripts for both Azure CLI (cross-platform) and PowerShell, and consider mentioning Bash or Linux shell scripting if supported.
  • If examples are added in the future, ensure parity by providing both PowerShell and Azure CLI/Bash examples.
  • Explicitly state that Azure Copilot supports script generation for users on all platforms (Windows, Linux, macOS).
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-03-09 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 does not exclude Linux/macOS users, PowerShell is a Windows-centric tool and is mentioned before Bash or other Linux-native shells. No explicit Linux/macOS examples or tools are referenced, and no Bash-specific guidance is provided.
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 shells.
  • Ensure parity in script generation examples, showing both PowerShell and Bash where relevant.
GitHub Create Pull Request
Azure Portal Programmatically create Azure Dashboards ...tal/azure-portal-dashboards-create-programmatically.md
Low Priority View Details →
Scanned: 2026-03-09 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 dashboards, but the PowerShell section is given equal prominence to the CLI, and the PowerShell cmdlets are shown immediately after the CLI section. There are no explicit Linux/macOS-specific instructions or notes, and the PowerShell section does not clarify that PowerShell Core is cross-platform. The CLI examples are cross-platform, but the presence of a dedicated PowerShell section may give the impression of a Windows bias, especially since PowerShell is often associated with Windows environments.
Recommendations
  • Clarify that Azure CLI commands are fully cross-platform and recommended for Linux/macOS users.
  • Add a brief note that Azure PowerShell is available on all platforms via PowerShell Core, or clarify if any examples require Windows PowerShell.
  • Consider listing Azure CLI as the primary or default method for automation, with PowerShell as an alternative.
  • If possible, add a short section or note confirming that all steps are supported on Linux/macOS, and that no Windows-specific tools are required.
GitHub Create Pull Request
Azure Portal Programmatically create Azure Dashboards ...tal/azure-portal-dashboards-create-programmatically.md
Low Priority View Details →
Scanned: 2026-03-08 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 dashboards, but the PowerShell section is given equal prominence to the CLI section and is not clearly marked as Windows-specific. PowerShell is cross-platform, but many Linux/macOS users prefer the CLI. The CLI examples are shown before PowerShell, which is good, but the PowerShell section could be more clearly marked as optional for non-Windows users. There are no Linux/macOS-specific shell examples (e.g., bash scripting), but the CLI commands are cross-platform. No Windows-only tools or patterns are used, and the documentation does not omit Linux support.
Recommendations
  • Clarify that Azure PowerShell is available cross-platform, but most Linux/macOS users will prefer the Azure CLI.
  • Optionally, add a brief note at the start of the PowerShell section indicating that PowerShell is available on all platforms, but CLI is the default on Linux/macOS.
  • Consider adding a short bash script example for deploying a dashboard template using the Azure CLI to further improve Linux parity.
  • Ensure that all CLI examples use syntax compatible with bash/zsh (e.g., avoid Windows-style line continuations).
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-03-08 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 capability of Azure Copilot in the mobile app. PowerShell is listed alongside CLI, but is traditionally associated with Windows, and its mention before Bash or Linux shell scripting may subtly prioritize Windows users. No explicit Linux/Bash examples or tools are referenced, and PowerShell is the only scripting language named besides 'CLI'.
Recommendations
  • Explicitly mention Bash or Linux shell scripting as a supported output for code generation.
  • Provide examples or clarify that Azure Copilot can generate scripts for both Windows (PowerShell) and Linux/macOS (Bash, Azure CLI).
  • Ensure parity in documentation by listing Bash/Linux shell scripting alongside PowerShell, not after or omitted.
  • Add a note that Azure Copilot supports cross-platform script generation, including for Linux and macOS users.
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-03-07 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 before Bash or Linux shell scripting may subtly prioritize Windows users. No explicit Linux/macOS examples or tools are referenced, and no Bash or shell script generation is mentioned.
Recommendations
  • Explicitly mention Bash or shell script generation as a capability, if supported.
  • Clarify that Azure CLI is cross-platform and provide examples for both PowerShell and Bash where relevant.
  • Ensure that any code snippet generation examples in future documentation include both PowerShell and Bash/Linux shell variants.
  • Add a note about parity between Windows and Linux/macOS users for script generation, if 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-03-06 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 traditionally associated with Windows, there is no explicit prioritization or omission of Linux/bash examples. The rest of the documentation is platform-neutral, focusing on the Azure mobile app, which is available for both iOS and Android.
Recommendations
  • Clarify that generated scripts can include Bash/CLI examples for Linux/macOS users, not just PowerShell.
  • Explicitly mention Bash or shell script generation alongside PowerShell and CLI to reinforce cross-platform support.
  • If examples are provided in future updates, ensure parity by including both PowerShell and Bash/CLI 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-03-06 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. This ordering may subtly prioritize Windows/PowerShell users, even though Azure CLI is fully cross-platform. No examples or instructions are exclusive to Windows, and all steps are portal-based and platform-agnostic.
Recommendations
  • Alternate the order in which Azure CLI and PowerShell are mentioned, or mention Azure CLI first to reflect its cross-platform nature.
  • Explicitly note that both Azure CLI and PowerShell are available on Windows, Linux, and macOS.
  • Where possible, provide direct example commands for both Azure CLI and PowerShell, ensuring parity and clarity for all users.
GitHub Create Pull Request
Azure Portal Programmatically create Azure Dashboards ...tal/azure-portal-dashboards-create-programmatically.md
Low Priority View Details →
Scanned: 2026-03-05 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 the Azure portal, Azure CLI, and Azure PowerShell. While the Azure CLI is cross-platform and shown before PowerShell, the PowerShell section is present and uses Windows-centric terminology. The PowerShell example is given after the CLI, but no Linux/macOS-specific shell examples (such as Bash scripting or references to Cloud Shell usage on Linux/macOS) are provided. The documentation does not show exclusive Windows tools or patterns, but the inclusion of PowerShell without explicit Linux/macOS parity may create minor friction.
Recommendations
  • Clarify that Azure CLI commands work on Windows, Linux, and macOS, and can be used in Bash or other shells.
  • Add a note or example showing how to use Azure CLI in Bash or Cloud Shell for Linux/macOS users.
  • Mention that Azure PowerShell is available cross-platform, but highlight CLI as the primary cross-platform tool.
  • Consider providing Bash script snippets for automating dashboard deployment, or referencing Cloud Shell 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-03-05 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents both Azure PowerShell and Azure CLI as options for programmatic access, but PowerShell is consistently mentioned first. This subtly prioritizes Windows tooling, even though Azure CLI is fully cross-platform. No Linux/macOS-specific instructions or screenshots are provided, but the content is largely platform-neutral since it focuses on the Azure portal UI.
Recommendations
  • Alternate the order in which Azure PowerShell and Azure CLI are mentioned, or list Azure CLI first to reflect its cross-platform nature.
  • Explicitly state that Azure CLI works on Windows, Linux, and macOS to reassure non-Windows users.
  • Where programmatic examples are given, provide both PowerShell and CLI commands side-by-side, or clarify that both are equally supported.
  • Consider including a note or screenshot showing Azure CLI usage in a non-Windows terminal to reinforce parity.
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-03-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 alongside CLI. While this is not strictly Windows-only, PowerShell is more commonly associated with Windows, and its mention before Bash or Linux shell scripting could be seen as a mild Windows bias. No explicit Linux examples, tools, or patterns are provided, nor are Linux/macOS equivalents mentioned. However, the documentation is generally neutral and focused on the Azure mobile app, which is available on both iOS and Android.
Recommendations
  • Explicitly mention Bash or Linux shell scripting as a supported code generation scenario, alongside PowerShell.
  • Provide examples or clarify that Azure Copilot can generate scripts for Bash, Azure CLI, and PowerShell, covering both Windows and Linux users.
  • Ensure that future documentation includes parity in examples for both Windows (PowerShell) and Linux/macOS (Bash/Azure CLI).
GitHub Create Pull Request
Azure Portal Programmatically create Azure Dashboards ...tal/azure-portal-dashboards-create-programmatically.md
Low Priority View Details →
Scanned: 2026-03-04 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 (cross-platform) is presented before PowerShell, the PowerShell section is included and uses Windows-centric terminology. The PowerShell examples are not flagged as biased since PowerShell Core is available cross-platform, but the documentation refers to 'Azure PowerShell' and the Az.Portal module, which are most commonly used on Windows. The CLI examples are shown first, but there is no explicit mention of Linux/macOS compatibility or shell-specific considerations. No Linux-specific tools or examples are missing, but the ordering and terminology may subtly favor Windows users.
Recommendations
  • Clarify that Azure CLI and PowerShell Core are available on Linux and macOS, and provide links or notes about installation on those platforms.
  • Explicitly state that all CLI and PowerShell commands work cross-platform unless otherwise noted.
  • Consider including a brief example of running Azure CLI commands in Bash or Zsh to reinforce Linux/macOS parity.
  • Avoid using Windows-centric terminology (e.g., 'Azure PowerShell') without clarifying cross-platform support.
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-03-04 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 to subscription and tenant IDs, but PowerShell is consistently mentioned before CLI, and the PowerShell module is referenced with a direct cmdlet example. This ordering and emphasis may subtly prioritize Windows/PowerShell users, though CLI is cross-platform and equally capable. No Windows-only tools or patterns are present, and Linux/macOS users can fully complete all tasks.
Recommendations
  • Alternate the order in which Azure CLI and PowerShell are mentioned, or present CLI first to reflect its cross-platform nature.
  • Provide explicit example commands for both Azure CLI and PowerShell in the main content, not just as links.
  • Clarify that both CLI and PowerShell are available on all major platforms, not just Windows.
  • Where possible, include screenshots or instructions that are platform-neutral (which is already mostly the case here).
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-03-04 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 historically associated with Windows, and its mention before Bash or Linux shell scripting may subtly prioritize Windows users. No explicit Linux/macOS examples or tools are referenced, and no Bash or shell script generation is highlighted.
Recommendations
  • Explicitly mention Bash or shell script generation as a Copilot capability, alongside PowerShell and CLI.
  • Provide examples or clarify that CLI scripts can be used on Linux/macOS, and PowerShell is cross-platform.
  • Consider listing scripting options in a neutral order (e.g., 'Generating CLI, Bash, and PowerShell scripts').
  • Add a note about Azure CLI being available on all platforms, and PowerShell Core being cross-platform.
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-03-03 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides both Azure PowerShell and Azure CLI options for programmatic access to subscription and tenant IDs, but PowerShell is consistently mentioned before CLI. PowerShell is more commonly associated with Windows, while Azure CLI is cross-platform and often preferred by Linux/macOS users. No examples or instructions are exclusive to Windows, and both tools are referenced, but the ordering may subtly prioritize Windows users.
Recommendations
  • Alternate the order in which Azure PowerShell and Azure CLI are mentioned, or mention Azure CLI first in at least some places to reflect its cross-platform nature.
  • Explicitly note that both Azure PowerShell and Azure CLI are available on Windows, Linux, and macOS.
  • Where possible, provide direct example commands for both tools, ensuring parity and clarity for all users.
GitHub Create Pull Request
← Previous Page 2 of 5 Next →