Azure Portal

71
Total Pages
65
Linux-Friendly Pages
6
Pages with Bias
8.5%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

18 issues found
Showing 1-18 of 18 flagged pages
Azure Portal Create an Azure portal dashboard by using a Bicep file .../blob/main/articles/azure-portal/quick-create-bicep.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias by exclusively deploying a Windows VM (SimpleWinVM), referencing Windows-specific username/password requirements, and linking only to Windows VM documentation for credential rules. There are no Linux VM deployment options or references, and the example VM is hard-coded as Windows. While both Azure CLI and PowerShell examples are provided, the VM itself is Windows-only, and Linux credential requirements are omitted.
Recommendations
  • Provide an alternative example that deploys a Linux VM (e.g., Ubuntu) alongside or instead of the Windows VM.
  • Include links to Linux VM username and password requirements documentation.
  • Make the VM type configurable in the Bicep file and deployment scripts, allowing users to choose between Windows and Linux.
  • Clarify in the prerequisites and deployment steps that both Windows and Linux VMs are supported, and show how to adapt the scripts for Linux.
  • Add a note or tabbed examples for Linux-specific deployment considerations, such as SSH key authentication.
GitHub Create Pull Request
Azure Portal Use Azure Copilot with the Azure mobile app ...main/articles/azure-portal/mobile-app/azure-copilot.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation mentions generating CLI and PowerShell scripts as a key scenario, listing PowerShell before CLI, and does not specify or provide examples for Linux/macOS users (e.g., Bash, shell scripts). There are no explicit Linux/macOS examples or references to platform-specific tools beyond PowerShell, which is primarily associated with Windows.
Recommendations
  • Explicitly mention Bash/shell scripts as supported output alongside PowerShell and CLI.
  • Provide examples or clarify that generated CLI scripts are cross-platform (e.g., Azure CLI works on Linux/macOS).
  • Add notes or examples for Linux/macOS users, including any platform-specific considerations.
  • Avoid listing PowerShell before CLI unless there is a technical reason; consider listing CLI first or together.
GitHub Create Pull Request
Azure Portal Create an Azure portal dashboard with Azure CLI .../azure-portal/quickstart-portal-dashboard-azure-cli.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
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 exclusively providing a Windows VM creation example (using the 'win2016datacenter' image) and referencing Windows-specific username/password requirements. There are no equivalent Linux VM creation examples or references to Linux-specific requirements, which may cause friction for users intending to deploy Linux VMs.
Recommendations
  • Add a Linux VM creation example using a common image (e.g., UbuntuLTS) alongside the Windows example.
  • Include links to Linux VM username and password requirements.
  • Clarify that the dashboard template and deployment steps are OS-agnostic, and provide guidance for customizing the template for Linux VMs.
  • Present Windows and Linux examples in parallel or alternate their order to avoid implicit prioritization.
GitHub Create Pull Request
Azure Portal Create an Azure portal dashboard by using an Azure Resource Manager template ...ob/main/articles/azure-portal/quick-create-template.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a notable Windows bias. All command-line instructions for creating the required VM use PowerShell, with screenshots and examples referencing PowerShell and Windows-specific resource group and VM naming conventions (e.g., 'SimpleWinVmResourceGroup', 'myVM1'). There are no equivalent instructions or examples for Linux/macOS users (e.g., Bash in Cloud Shell or Azure CLI). Password and username requirements link to Windows VM documentation, and the resource group name implies a Windows VM. While the deployment steps mention Azure CLI as an alternative, no examples or guidance are provided for non-Windows environments.
Recommendations
  • Add parallel instructions and examples using Bash in Cloud Shell and Azure CLI for creating the resource group and VM.
  • Include screenshots of Bash selection in Cloud Shell alongside PowerShell.
  • Provide Linux VM creation examples (e.g., using Ubuntu) and update resource group/VM naming to be OS-neutral.
  • Link to both Windows and Linux VM username/password requirements.
  • Ensure all deployment steps have both PowerShell and CLI code snippets, and clarify that Cloud Shell supports both environments.
GitHub Create Pull Request
Azure Portal Create an Azure portal dashboard by using a Bicep file .../blob/main/articles/azure-portal/quick-create-bicep.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits Windows bias by exclusively using a Windows VM example (SimpleWinVM), referencing Windows-specific username/password requirements, and linking only to Windows VM documentation. There are no Linux VM deployment examples, nor any mention of Linux-specific requirements or alternatives. The deployment scripts use Azure CLI and PowerShell, which are cross-platform, but the VM created is Windows-only, and all guidance is tailored to Windows environments.
Recommendations
  • Add a parallel example for deploying a Linux VM, including links to Linux username/password requirements and best practices.
  • Reference both Windows and Linux VM documentation when discussing prerequisites and password requirements.
  • Use a more neutral VM name (e.g., SimpleVM) and provide parameters or instructions for selecting the OS type.
  • Clarify that the Bicep file and deployment scripts work for both Windows and Linux VMs, or provide separate Bicep files/examples for each.
  • Ensure that dashboard examples can visualize both Windows and Linux VM metrics.
GitHub Create Pull Request
Azure Portal Create an Azure portal dashboard by using an Azure Resource Manager template ...ob/main/articles/azure-portal/quick-create-template.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a notable Windows bias. All command-line examples for creating the required VM use PowerShell, with explicit instructions to select PowerShell in the Azure Cloud Shell. The resource group and VM naming conventions (e.g., 'SimpleWinVmResourceGroup', 'myVM1') and linked requirements reference Windows VM documentation. There are no equivalent Bash or Azure CLI examples for Linux/macOS users, nor any mention of Linux VM creation or requirements. The instructions and screenshots prioritize Windows-centric tools and workflows.
Recommendations
  • Provide parallel instructions and command examples using Bash/Azure CLI in Cloud Shell for Linux/macOS users.
  • Include links to Linux VM documentation and requirements alongside Windows references.
  • Offer guidance for creating a Linux VM (e.g., using Ubuntu) with appropriate naming conventions.
  • Alternate or combine screenshots to show both PowerShell and Bash options in Cloud Shell.
  • Clarify that Cloud Shell supports both Bash and PowerShell, and users can choose based on their environment.
GitHub Create Pull Request
Azure Portal Create an Azure portal dashboard with Azure CLI .../azure-portal/quickstart-portal-dashboard-azure-cli.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by exclusively providing a Windows VM creation example (using the 'win2016datacenter' image) and referencing Windows-specific username/password requirements. There are no Linux VM examples or references to Linux-specific requirements, which may hinder Linux users from following the quickstart without additional research.
Recommendations
  • Include a Linux VM creation example alongside the Windows example, such as using '--image UbuntuLTS' and appropriate authentication options.
  • Reference Linux-specific username and password requirements, or link to the relevant documentation for Linux VMs.
  • Clarify that the dashboard template and Azure CLI commands work equally well for Linux VMs.
  • Present Windows and Linux examples in parallel, or alternate which is shown first to avoid implicit prioritization.
GitHub Create Pull Request
Azure Portal Create an Azure portal dashboard by using an Azure Resource Manager template ...ob/main/articles/azure-portal/quick-create-template.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a notable Windows bias. All example commands for creating the required VM use Azure PowerShell, with explicit instructions to select PowerShell in Cloud Shell. The resource group and VM are named with 'Win' (SimpleWinVmResourceGroup), and the username/password requirements link only to Windows VM documentation. No Bash or Linux CLI examples are provided, and Linux VM creation is not mentioned. The deployment and cleanup steps reference Windows-centric resource names and omit Linux alternatives.
Recommendations
  • Add parallel instructions and examples for creating the VM using Bash in Cloud Shell, with Azure CLI commands.
  • Provide guidance for creating a Linux VM, including appropriate resource group and VM naming (e.g., SimpleLinuxVmResourceGroup).
  • Link to both Windows and Linux VM username/password requirements.
  • Show both PowerShell and Azure CLI options for resource creation and management.
  • Avoid Windows-centric naming conventions in example resources, or provide both Windows and Linux examples.
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 both Azure CLI and Azure PowerShell examples for deploying dashboards, but the PowerShell section is given equal prominence to the CLI section, and PowerShell is mentioned in the overview before the CLI. There are no Linux/macOS-specific instructions or notes, but the CLI examples are cross-platform. The PowerShell section could be perceived as Windows-centric, especially since it is not clarified that Azure PowerShell is available cross-platform. No Linux-specific tools or shell examples are provided, but the CLI coverage mitigates this.
Recommendations
  • Clarify that Azure PowerShell is available on Linux/macOS, or provide a link to installation instructions for non-Windows platforms.
  • Explicitly state that Azure CLI commands work on Windows, Linux, and macOS.
  • Consider listing Azure CLI before PowerShell in the overview to avoid a Windows-first impression.
  • Optionally, provide shell script examples (e.g., Bash) for common deployment scenarios to further improve Linux parity.
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-10 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 programmatically retrieving subscription and tenant IDs. However, PowerShell is consistently mentioned before Azure CLI, and the PowerShell module is linked first. This ordering may subtly prioritize Windows/PowerShell users, even though Azure CLI is fully cross-platform. No Windows-only tools or patterns are used, and Linux/macOS users can complete all tasks described.
Recommendations
  • Alternate the order of PowerShell and CLI mentions, or mention Azure CLI first to emphasize cross-platform support.
  • Explicitly note that Azure CLI works on Windows, Linux, and macOS.
  • Add brief examples for both Azure PowerShell and Azure CLI commands to further clarify parity.
  • Consider linking to Azure CLI documentation before PowerShell where appropriate.
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: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation mentions 'Generating CLI and PowerShell scripts' as a key capability, listing PowerShell alongside CLI. While this is a minor bias, PowerShell is primarily associated with Windows, and its mention before Bash or Linux shell scripting could subtly prioritize Windows users. However, the page does not provide actual script examples or instructions exclusive to Windows/PowerShell, and the overall content is platform-neutral, focusing on the Azure mobile app available for both iOS and Android.
Recommendations
  • When listing scripting capabilities, clarify that Azure Copilot can generate both Bash (for Linux/macOS) and PowerShell scripts, or use 'CLI and shell scripts' instead of 'CLI and PowerShell scripts'.
  • If examples are added in the future, ensure parity by providing both PowerShell and Bash examples.
  • Explicitly state that the Azure mobile app and Copilot features are available and supported on all major mobile platforms.
GitHub Create Pull Request
Azure Portal Programmatically create Azure Dashboards ...tal/azure-portal-dashboards-create-programmatically.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation lists Azure REST API, Azure CLI, and Azure PowerShell as programmatic options, but consistently mentions PowerShell before CLI and provides direct links to PowerShell deployment instructions before CLI equivalents. In the deployment section, PowerShell is listed before CLI, and the 'Next steps' links reference PowerShell before CLI. There are no OS-specific command examples, but the ordering and emphasis suggest a mild Windows bias.
Recommendations
  • Alternate the order of Azure CLI and PowerShell mentions, or list CLI first to reflect its cross-platform nature.
  • Explicitly state that both Azure CLI and PowerShell are available on Windows, Linux, and macOS.
  • Provide example commands for both Azure CLI and PowerShell side-by-side, or clarify that examples apply equally across platforms.
  • Include links to installation and usage guides for Azure CLI and PowerShell on Linux/macOS.
  • Add a note that the Azure portal and REST API are platform-agnostic.
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-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation mentions both Azure PowerShell and Azure CLI for programmatic access, but PowerShell is consistently listed first in tips and next steps. This ordering subtly prioritizes Windows-centric tooling, as PowerShell is native to Windows and less commonly used on Linux/macOS. No explicit Linux/macOS bias or missing examples are present, but the pattern may create a perception of Windows preference.
Recommendations
  • Alternate the order of Azure CLI and PowerShell references, or list Azure CLI first, as it is cross-platform and more commonly used on Linux/macOS.
  • Explicitly state that both Azure CLI and PowerShell are available on all major platforms, and link to installation guides for Linux/macOS users.
  • Provide example commands for both Azure CLI and PowerShell side-by-side, clarifying platform compatibility.
  • Consider adding a note about using the Azure portal from any OS/browser to reinforce cross-platform accessibility.
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-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation mentions generating CLI and PowerShell scripts as a key scenario, listing PowerShell before CLI. There are no explicit Linux/macOS examples, nor is Bash or other Linux shell scripting mentioned. The documentation does not clarify that CLI commands are cross-platform, nor does it provide parity in examples or terminology for Linux/macOS users.
Recommendations
  • Explicitly mention Bash or shell scripting alongside PowerShell when discussing code generation.
  • Clarify that Azure CLI is cross-platform and provide examples or notes for Linux/macOS users.
  • Add sample prompts or screenshots showing Bash/CLI usage, not just PowerShell.
  • Avoid listing PowerShell before CLI unless contextually appropriate; consider alphabetical or platform-neutral ordering.
GitHub Create Pull Request
Azure Portal Programmatically create Azure Dashboards ...tal/azure-portal-dashboards-create-programmatically.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation lists Azure REST API, CLI, and PowerShell as programmatic options, but consistently mentions PowerShell before CLI, and links to PowerShell deployment instructions before CLI equivalents. Example deployment methods always list PowerShell before CLI, and the 'Next steps' section links to PowerShell before CLI. There are no explicit Linux/macOS examples, and no mention of platform-specific considerations, but the CLI is referenced and linked, which is cross-platform.
Recommendations
  • Alternate the order of PowerShell and CLI references, or list CLI first to reflect its cross-platform nature.
  • Explicitly mention that Azure CLI works on Linux/macOS and provide example commands for both CLI and PowerShell where appropriate.
  • Add notes or examples for Linux/macOS users, especially for deployment steps.
  • Ensure that links to CLI and PowerShell quickstarts are presented with equal prominence.
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-01-12 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 mentioned first in tips and links. PowerShell is a Windows-centric tool, and its prominence may signal a Windows-first bias. However, Azure CLI is cross-platform and included in all relevant sections, so Linux/macOS users are not blocked from completing any tasks.
Recommendations
  • Alternate the order of PowerShell and CLI references, or mention CLI first to reflect its cross-platform nature.
  • Explicitly state that Azure CLI works on Linux/macOS and provide installation links for those platforms.
  • Add a brief note clarifying that PowerShell Core is available cross-platform, but CLI is generally preferred for Linux/macOS.
  • Include screenshots or examples from non-Windows environments if possible.
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-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation mentions both Azure PowerShell and Azure CLI for programmatic access to subscription and tenant IDs, but PowerShell is consistently listed first and receives slightly more emphasis. This ordering and phrasing may subtly favor Windows users, as PowerShell is most commonly associated with Windows environments, while Azure CLI is cross-platform. No explicit Windows-only tools or examples are present, and Linux/macOS users can complete all tasks described.
Recommendations
  • Alternate the order of PowerShell and CLI references, or list Azure CLI first to reflect its cross-platform nature.
  • Explicitly state that both Azure CLI and PowerShell are available on Windows, Linux, and macOS.
  • Provide example commands for both Azure CLI and PowerShell side-by-side, ensuring parity.
  • Add a note clarifying that Azure CLI is natively supported 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-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation lists Azure PowerShell before Azure CLI in tool mentions and deployment methods, and provides direct links to PowerShell-specific deployment instructions. While Azure CLI is also referenced, PowerShell is consistently mentioned first, which may subtly signal a Windows-first approach. No examples are exclusive to Windows or PowerShell, and Linux/macOS users can complete all tasks using the CLI or REST API. No Windows-only tools or patterns are present, and Linux is referenced in dashboard links.
Recommendations
  • List Azure CLI before PowerShell in tool mentions and deployment instructions to reflect cross-platform parity.
  • Explicitly state that both Azure CLI and PowerShell are fully supported on Linux, macOS, and Windows.
  • Where possible, provide example commands for both Azure CLI and PowerShell, or default to CLI for cross-platform documentation.
  • Add a note clarifying that all steps can be performed on Linux/macOS using Azure CLI or REST API.
GitHub Create Pull Request