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 1-25 of 109 flagged pages
Azure Portal Create an Azure portal dashboard by using an Azure Resource Manager template ...ob/main/articles/azure-portal/quick-create-template.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 First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. All example commands for creating the required VM use PowerShell and Windows-centric resource group/VM naming ('SimpleWinVmResourceGroup', 'myVM1'). There are no Linux or Bash examples for VM creation, nor are Linux VM options mentioned. Username/password requirements link only to Windows VM documentation. The instructions and screenshots focus exclusively on Windows tools and patterns, with no parity for Linux users.
Recommendations
  • Provide equivalent Bash/Azure CLI examples for VM creation in Cloud Shell, including Linux VM creation steps.
  • Include links to Linux VM username/password requirements and documentation.
  • Use more neutral resource group and VM names (e.g., 'SimpleVmResourceGroup', 'myVM1' or 'myLinuxVM1').
  • Add a note or section explaining how to perform all steps using Linux tools and workflows.
  • Ensure screenshots and instructions reflect both PowerShell and Bash options in Cloud Shell.
GitHub Create Pull Request
Azure Portal How to create an Azure support request .../supportability/how-to-create-azure-support-request.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily in the 'Memory dump collection' section, which exclusively describes Windows memory dump formats and Hyper-V save state mechanisms, without mentioning Linux VM equivalents. Additionally, the advanced diagnostic logs section links to Windows VM logs first and does not provide parity for Linux VM troubleshooting. There are no CLI or shell examples for Linux users, and the documentation does not mention Linux-specific support scenarios or tools.
Recommendations
  • Include information about memory dump collection for Linux VMs, such as how Linux crash dumps are handled and what diagnostic data is collected.
  • Add links to Linux VM troubleshooting guides and diagnostic log collection procedures alongside Windows examples.
  • Ensure that references to VM logs and support data collection cover both Windows and Linux environments equally.
  • Provide CLI or shell command examples for creating and managing support requests, demonstrating usage on both Windows and Linux platforms.
  • Explicitly mention any differences in support request handling or diagnostic data collection between Windows and Linux VMs.
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
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits Windows bias by exclusively deploying a Windows VM ('SimpleWinVM'), referencing Windows-specific username/password requirements, and linking only to Windows VM documentation. There are no examples or guidance for deploying a Linux VM, nor are Linux-specific requirements or dashboard scenarios mentioned. While both Azure CLI and PowerShell are shown, the VM and supporting documentation are Windows-centric.
Recommendations
  • Provide equivalent examples for deploying a Linux VM (e.g., Ubuntu) and update the Bicep/ARM template to allow choosing between Windows and Linux.
  • Include links to Linux VM documentation for username and password requirements.
  • Add a section or tab showing how to visualize Linux VM performance in the dashboard.
  • Ensure that variable names and resource group names are OS-neutral (e.g., 'SimpleVmResourceGroup' instead of 'SimpleWinVmResourceGroup').
  • Clarify in the prerequisites and deployment steps that both Windows and Linux VMs are supported, and provide parameter options for each.
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
High 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 strong Windows bias. All example commands for creating the required VM use PowerShell, with no Bash or Azure CLI equivalents shown. The resource group and VM names (SimpleWinVmResourceGroup, myVM1) and referenced documentation (Windows username/password requirements) further reinforce a Windows-centric approach. There are no instructions or examples for Linux users, nor are Linux VM creation patterns mentioned. The use of PowerShell in Cloud Shell is presented as the default, with no mention of Bash.
Recommendations
  • Provide equivalent Azure CLI or Bash examples for VM and resource group creation, especially in Cloud Shell.
  • Include instructions for creating a Linux VM, with appropriate references to Linux username/password requirements.
  • Use more neutral resource group and VM names (e.g., 'SimpleVmResourceGroup', 'myVM1') or provide parallel examples for Windows and Linux.
  • Explicitly mention that Cloud Shell supports both PowerShell and Bash, and show how to select Bash.
  • Add links to Linux VM documentation and best practices alongside Windows references.
  • Ensure that deployment and cleanup instructions are platform-agnostic or provide both Windows and Linux command examples.
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
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
This documentation page exhibits Windows bias in several ways: the example VM deployed is hard-coded as 'SimpleWinVM', with references to Windows-specific username and password requirements. The prerequisites and deployment instructions mention Azure PowerShell and Azure CLI, but the VM template and guidance are tailored for a Windows VM only, with no mention of Linux VM options or Linux-specific requirements. There are no examples or instructions for deploying a Linux VM or managing Linux credentials, and the documentation links for username/password requirements point to Windows VM documentation.
Recommendations
  • Provide parallel examples for deploying a Linux VM (e.g., 'SimpleLinuxVM'), including Linux-specific username and password requirements.
  • Include links to Linux VM documentation for credential requirements.
  • Make it clear that the dashboard can visualize both Windows and Linux VMs, and provide sample Bicep/ARM templates for each.
  • Ensure that CLI and PowerShell examples use variables and resource names that are not Windows-specific.
  • Add a note or section explaining how to adapt the process for Linux VMs, including any differences in deployment parameters or dashboard configuration.
GitHub Create Pull Request
Azure Portal Use Azure Copilot with the Azure mobile app .../azure-portal/mobile-app/microsoft-copilot-in-azure.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation mentions generating both CLI and PowerShell scripts, but lists PowerShell before CLI, which may suggest a Windows-first approach. There are no explicit Linux-specific examples, tools, or references, and PowerShell (traditionally a Windows tool) is highlighted without equal emphasis on Bash or other Linux-native shells. No Linux command-line examples or patterns are provided.
Recommendations
  • List CLI (az CLI) before PowerShell when mentioning script generation, or present them together to avoid perceived prioritization.
  • Explicitly mention Bash and Linux shell script generation capabilities if supported by Azure Copilot.
  • Provide examples or references for Linux users, such as how to use generated scripts in Bash or other Linux environments.
  • Clarify that PowerShell is cross-platform, or provide links to documentation for using PowerShell on Linux and macOS.
  • Ensure parity in documentation by including Linux-specific scenarios or tips for mobile users who manage Azure resources from Linux devices.
GitHub Create Pull Request
Azure Portal How to create an Azure support request .../supportability/how-to-create-azure-support-request.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page displays a Windows bias in several ways. The 'Advanced diagnostic information logs' and 'Memory dump collection' sections focus on Windows-specific logs and memory dump formats, referencing Windows VM logs and Windows kernel-mode dumps without mentioning Linux equivalents. The memory dump process is described exclusively in terms of Windows (Hyper-V, Windows memory), with no discussion of Linux VM diagnostics or dump collection. There are no examples or guidance for Linux users, and Windows terminology and tools are presented first and exclusively.
Recommendations
  • Include information and examples for Linux VM diagnostics, such as collecting logs and memory dumps from Linux-based Azure VMs.
  • Add references to Linux-specific troubleshooting guides and support data collection procedures.
  • When listing diagnostic logs or support packages, explicitly mention both Windows and Linux options, and provide parity in instructions.
  • Describe memory dump collection for Linux VMs, including any differences in process, impact, and data collected.
  • Ensure that examples and terminology are platform-neutral or provide both Windows and Linux variants side-by-side.
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
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 Missing Linux Example
Summary
The documentation page mentions generating both CLI and PowerShell scripts as a key capability of Azure Copilot, but lists PowerShell before CLI and does not specify or provide examples for Linux shells (such as Bash). There is no mention of Linux-specific tools or patterns, nor are Linux/Bash examples provided. The focus on PowerShell and the ordering implies a Windows-first perspective.
Recommendations
  • Explicitly mention Bash and Linux shell script generation as a capability alongside PowerShell and CLI.
  • Provide example prompts or outputs for both PowerShell and Bash/Linux CLI to demonstrate parity.
  • Clarify that Azure Copilot can generate scripts for multiple platforms, including Linux, and link to documentation on using Azure CLI and Bash on Linux.
  • Avoid listing PowerShell before CLI or Linux tools unless there is a technical reason; consider alphabetical or platform-neutral ordering.
GitHub Create Pull Request
Azure Portal https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-portal/quick-create-bicep.md .../blob/main/articles/azure-portal/quick-create-bicep.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows by exclusively deploying a Windows VM ('SimpleWinVM'), referencing Windows-specific username/password requirements, and linking only to Windows VM documentation. There are no examples or guidance for deploying a Linux VM, nor are Linux username/password requirements mentioned. The deployment scripts are generic (Azure CLI and PowerShell), but the resource and supporting information are Windows-centric.
Recommendations
  • Provide parallel examples for deploying a Linux VM (e.g., 'SimpleLinuxVM') alongside the Windows VM, including relevant ARM templates and Bicep parameters.
  • Reference Linux VM documentation for username and password requirements, and link to Linux security best practices.
  • Clarify that the dashboard can visualize both Windows and Linux VMs, and offer sample dashboards for each.
  • Ensure that both Windows and Linux options are presented equally in prerequisites and deployment steps.
GitHub Create Pull Request
Azure Portal https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-portal/supportability/how-to-create-azure-support-request.md .../supportability/how-to-create-azure-support-request.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways. The advanced diagnostic information and memory dump collection sections focus exclusively on Windows VM logs and Windows-specific memory dump formats, with no mention of Linux VM equivalents. The examples and references for diagnostic data collection and troubleshooting are centered on Windows tools and patterns, and there are no Linux-specific instructions, examples, or links provided for support scenarios involving Linux VMs.
Recommendations
  • Add explicit instructions and references for collecting diagnostic logs and memory dumps from Linux VMs, including links to relevant documentation.
  • Include examples and troubleshooting steps for Linux-based environments alongside Windows examples, ensuring parity in guidance.
  • Reference Linux tools (such as syslog, dmesg, journalctl, etc.) and provide guidance for uploading Linux log files when creating support requests.
  • Clarify which steps or data collection procedures differ for Linux VMs and provide links to Azure documentation for Linux VM support.
  • Review all sections for OS-specific terminology and ensure that Linux is mentioned wherever Windows is referenced, especially in advanced diagnostic and memory dump collection contexts.
GitHub Create Pull Request
Azure Portal https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-portal/quick-create-template.md ...ob/main/articles/azure-portal/quick-create-template.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 First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a strong Windows bias. All command-line examples for creating the prerequisite VM use PowerShell, with no mention of Bash or Azure CLI alternatives. The resource group and VM names (SimpleWinVmResourceGroup, myVM1) and referenced documentation (Windows username/password requirements) reinforce a Windows-centric approach. There are no Linux VM creation examples, nor is there guidance for users who prefer Bash or Linux tools in Cloud Shell. The documentation mentions Azure CLI as a deployment option, but does not provide CLI examples or parity in the quickstart steps.
Recommendations
  • Add equivalent Azure CLI and Bash examples for VM and resource group creation, especially for users accessing Cloud Shell from Linux or macOS.
  • Include instructions for creating a Linux VM (e.g., Ubuntu) alongside the Windows VM example, with appropriate username/password requirements links.
  • Use more neutral resource group and VM names (e.g., 'SimpleVmResourceGroup', 'myVM1') to avoid implying Windows-only usage.
  • Present both PowerShell and CLI/Bash options side-by-side, or allow users to select their preferred shell in the documentation.
  • Reference both Windows and Linux documentation for username/password requirements when creating VMs.
GitHub Create Pull Request
Azure Portal https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-portal/supportability/how-to-create-azure-support-request.md .../supportability/how-to-create-azure-support-request.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways. In the 'Advanced diagnostic information logs' and 'Memory dump collection' sections, Windows-specific terminology and tools (e.g., kernel-mode dump, Hyper-V save state) are referenced exclusively, with no mention of Linux VM equivalents or diagnostic procedures. The examples and instructions for memory dump collection focus solely on Windows, omitting guidance for Linux-based Azure VMs. Additionally, the order and selection of referenced diagnostic logs and procedures prioritize Windows environments, with Linux support not addressed.
Recommendations
  • Add explicit instructions and examples for collecting diagnostic information and memory dumps from Linux-based Azure VMs, including references to Linux tools (e.g., kdump, crash, syslog).
  • Include links to troubleshooting guides for Linux VM support cases alongside Windows references.
  • Ensure that any mention of VM diagnostics, logs, or support procedures covers both Windows and Linux environments, or clearly states platform-specific differences.
  • Review and update the order of examples and references so that Linux and Windows are presented with equal prominence.
GitHub Create Pull Request
Azure Portal https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-portal/quick-create-template.md ...ob/main/articles/azure-portal/quick-create-template.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 Windows bias by exclusively providing PowerShell commands for VM creation, referencing Windows-specific username/password requirements, and naming the resource group 'SimpleWinVmResourceGroup'. There are no examples or instructions for Linux users (e.g., Bash in Cloud Shell, Azure CLI commands for Linux VMs), and Windows tools and patterns are presented first and exclusively.
Recommendations
  • Add parallel instructions and examples for creating a Linux VM, including Azure CLI and Bash commands.
  • Rename resource groups and VM names to be OS-neutral (e.g., 'SimpleVmResourceGroup').
  • Include links to both Windows and Linux VM username/password requirements.
  • Show how to use Bash in Cloud Shell and provide equivalent commands for Linux users.
  • Present both PowerShell and CLI/Bash options side-by-side, or clearly indicate OS-specific sections.
  • Explicitly mention that the dashboard can visualize both Windows and Linux VM performance.
GitHub Create Pull Request
Azure Portal https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-portal/quick-create-bicep.md .../blob/main/articles/azure-portal/quick-create-bicep.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 virtual machine (SimpleWinVM), referencing Windows-specific username and password requirements, and linking only to Windows VM documentation. There are no Linux VM examples or references, and the deployment scripts do not demonstrate how to use a Linux VM. The resource group and VM naming conventions also reinforce a Windows-centric approach.
Recommendations
  • Provide parallel examples for deploying a Linux VM, including a Linux-focused ARM template and Bicep file.
  • Include links to Linux VM documentation for username/password requirements and best practices.
  • Use neutral resource names (e.g., 'SimpleVmResourceGroup', 'SimpleVM') instead of Windows-specific names.
  • Add a tabbed example for Linux VM deployment in both Azure CLI and PowerShell sections.
  • Clarify that the dashboard can visualize both Windows and Linux VMs, and show how to adapt the Bicep file for Linux scenarios.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides deployment instructions using both Azure CLI and Azure PowerShell, but the example VM is hard-coded as a Windows VM ('SimpleWinVM'), and all username/password requirements link to Windows VM documentation. There are no examples or guidance for deploying a Linux VM or adapting the dashboard for Linux workloads. The PowerShell example is given equal prominence to CLI, but the overall workflow is Windows-centric.
Recommendations
  • Add instructions and examples for deploying a Linux VM (e.g., Ubuntu) as the dashboard target, including links to Linux VM username/password requirements.
  • Clarify that the dashboard can be adapted for Linux VMs and provide sample Bicep/ARM templates for Linux VM scenarios.
  • Ensure that CLI examples do not assume Windows-specific VM names or parameters, and provide alternative values for Linux users.
  • Mention that Azure CLI is cross-platform and highlight its use for Linux/macOS users.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation page demonstrates a notable Windows bias in its instructions for creating the prerequisite VM. Only PowerShell commands are provided, with explicit selection of PowerShell in Azure Cloud Shell, and references to Windows-specific username/password requirements. There are no Bash or Azure CLI examples, nor guidance for Linux users, even though the Azure Cloud Shell supports Bash and Linux VMs are common in Azure. The resource group and VM names also use 'Win' and imply a Windows VM, but the dashboard creation itself is not inherently Windows-specific.
Recommendations
  • Provide equivalent Bash/Azure CLI instructions for creating the resource group and VM, including examples for Linux VM creation.
  • Clarify that users may use either PowerShell or Bash in Cloud Shell, and link to documentation for both.
  • Use more neutral resource group and VM names (e.g., 'SimpleVmResourceGroup', 'myVM1') unless the dashboard template is strictly Windows VM-specific.
  • Include notes or links for Linux VM username/password requirements if relevant.
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-14 00:00
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 and referencing Windows-specific username/password requirements. There are no examples or guidance for creating Linux VMs, which are equally supported in Azure and commonly used. This may cause friction for Linux users attempting to follow the quickstart.
Recommendations
  • Add a Linux VM creation example alongside the Windows example, using an appropriate image (e.g., UbuntuLTS) and Linux authentication options (e.g., SSH keys).
  • Include notes or links to Linux VM username/password requirements and best practices.
  • Clarify that the dashboard template and Azure CLI commands work for both Windows and Linux VMs.
  • Present both Windows and Linux examples in parallel, or indicate how to adapt the instructions for Linux users.
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 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. The only example for creating the required VM uses Azure PowerShell commands, with explicit instructions to select PowerShell in Cloud Shell. The resource group and VM naming conventions (e.g., 'SimpleWinVmResourceGroup', 'myVM1') and referenced documentation (Windows username/password requirements) further reinforce a Windows-centric approach. No Bash/Azure CLI examples are provided for Linux/macOS users, and the VM creation steps are tailored to Windows environments.
Recommendations
  • Provide equivalent Azure CLI (Bash) commands for VM and resource group creation, suitable for Linux/macOS users.
  • Mention that Cloud Shell supports both PowerShell and Bash, and offer users a choice.
  • Reference Linux VM documentation and requirements alongside Windows, especially for username/password guidance.
  • Use more neutral resource group and VM names (e.g., 'SimpleVmResourceGroup') to avoid implying Windows-only scenarios.
  • Ensure all critical steps (e.g., VM creation) have cross-platform instructions.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows by exclusively deploying a Windows VM ('SimpleWinVM'), referencing Windows-specific username/password requirements, and linking only to Windows VM documentation. The examples and scripts use Azure CLI and PowerShell, which are cross-platform, but the VM deployment and supporting links are Windows-centric. There are no examples or notes for deploying a Linux VM, nor are Linux username/password requirements or Linux VM documentation referenced.
Recommendations
  • Provide an alternative example that deploys a Linux VM (e.g., Ubuntu) alongside the Windows VM example.
  • Include links to Linux VM documentation for username and password requirements.
  • Clarify that the Azure CLI and PowerShell examples work on Linux/macOS, and show any OS-specific differences if relevant.
  • Use a more neutral VM name (e.g., 'SimpleVM') and parameterize the OS type in the Bicep/ARM template.
  • Add a note explaining how Linux users can adapt the example for their preferred OS.
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 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 VM creation example using a Windows image ('win2016datacenter') and referencing Windows-specific username/password requirements. There are no examples or guidance for creating Linux VMs, nor are Linux-specific requirements or considerations mentioned. All CLI commands themselves are cross-platform, but the resource examples and supporting notes focus solely on Windows.
Recommendations
  • Add a parallel example for creating a Linux VM (e.g., using '--image UbuntuLTS'), including Linux-specific username and password requirements.
  • Reference both Windows and Linux VM documentation for further information.
  • Clarify that the dashboard template and Azure CLI commands work with both Windows and Linux VMs.
  • Consider alternating or balancing examples so that Linux users see their platform represented equally.
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-11 00:00
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 VM creation example using a Windows image ('win2016datacenter') and referencing Windows-specific username and password requirements. There are no examples or guidance for creating a Linux VM, nor are Linux-specific considerations mentioned. The documentation does not offer parity for Linux users in its examples or instructions.
Recommendations
  • Add a parallel example for creating a Linux VM (e.g., using '--image UbuntuLTS') with appropriate username and SSH key/password requirements.
  • Include links to both Windows and Linux VM documentation for username/password/SSH requirements.
  • Explicitly mention that the dashboard template and Azure CLI commands work for both Windows and Linux VMs.
  • Ensure that template customization instructions include Linux VM naming conventions and authentication options.
  • Review and update notes and references to avoid implying Windows is the default or only supported 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
Medium Priority View Details →
Scanned: 2026-01-11 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 with more detail. This ordering and emphasis may suggest a Windows-centric bias, as PowerShell is traditionally a Windows tool, even though it is now cross-platform. There are no explicit Linux-only examples or mentions of Linux-specific tools or workflows, and the copy/paste instructions reference generic text documents rather than platform-specific editors.
Recommendations
  • Alternate the order of PowerShell and CLI examples, or list CLI first to avoid implicit Windows-first bias.
  • Explicitly mention that both Azure PowerShell and Azure CLI are cross-platform and available on Windows, Linux, and macOS.
  • Provide example commands for both PowerShell and CLI side-by-side, with notes on platform compatibility.
  • Include a brief note or link about installing and using Azure CLI and PowerShell on Linux.
  • Reference Linux-specific workflows or tools where appropriate, such as using the terminal or text editors like nano/vim for copying IDs.
GitHub Create Pull Request
Azure Portal Programmatically create Azure Dashboards ...tal/azure-portal-dashboards-create-programmatically.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page exhibits mild Windows bias. In several places, Azure PowerShell is mentioned before Azure CLI, and PowerShell is listed as a primary deployment method alongside REST API and CLI. There are no explicit Linux shell examples, and the ordering of links and instructions tends to favor Windows/PowerShell tools. However, Azure CLI is also referenced, and links to both Linux and Windows VM creation guides are provided in dashboard content.
Recommendations
  • Ensure Azure CLI is listed before or alongside PowerShell in tool recommendations, as CLI is cross-platform and preferred by many Linux users.
  • Add explicit Linux shell (bash) examples for deploying dashboards using Azure CLI, demonstrating parity with PowerShell examples.
  • When listing deployment options, alternate the order or clarify that both CLI and PowerShell are fully supported and cross-platform.
  • Include links to Linux-specific documentation (e.g., Azure CLI installation on Linux) in the 'Next steps' or relevant sections.
  • Review dashboard JSON examples to ensure resource group and VM names do not imply Windows-only usage (e.g., avoid 'SimpleWinVMResourceGroup').
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-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows by exclusively providing a VM creation example using a Windows image ('win2016datacenter') and referencing Windows-specific username and password requirements. There are no Linux VM examples, nor are Linux-specific requirements or images mentioned. The documentation does not offer parity for users who may prefer or require Linux-based VMs.
Recommendations
  • Include a Linux VM creation example alongside the Windows example, using a popular image such as 'UbuntuLTS'.
  • Add a note or section describing Linux username and password requirements, linking to the relevant Azure documentation.
  • Ensure that dashboard template customization instructions reference both Windows and Linux VM names and resource types.
  • Where possible, present Windows and Linux options together, or alternate which is shown first to avoid implicit prioritization.
GitHub Create Pull Request
Azure Portal Programmatically create Azure Dashboards ...tal/azure-portal-dashboards-create-programmatically.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 exhibits mild Windows bias. In several sections, Azure PowerShell is mentioned before Azure CLI, and PowerShell is listed as a primary deployment method alongside REST API and CLI. There are no explicit Linux shell examples, and PowerShell is referenced with dedicated links and instructions, while Linux-specific tooling or shell commands are not present. However, the page does mention Azure CLI, which is cross-platform, and includes links to both Linux and Windows VM creation guides in dashboard content.
Recommendations
  • Ensure Azure CLI is mentioned before or alongside PowerShell when listing deployment methods, as CLI is cross-platform.
  • Provide explicit Bash or Linux shell examples for template deployment, not just PowerShell.
  • Add links to Linux-specific documentation (e.g., deploying with Bash, using Linux tools) where appropriate.
  • Clarify that Azure CLI works on Windows, Linux, and macOS, and encourage its use for cross-platform scenarios.
  • Balance references to PowerShell and CLI in instructions and examples to avoid implying PowerShell is the default or preferred method.
GitHub Create Pull Request
← Previous Page 1 of 5 Next →