Baremetal Infrastructure

8
Total Pages
5
Linux-Friendly Pages
3
Pages with Bias
37.5%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

18 issues found
Showing 1-18 of 18 flagged pages
Baremetal Infrastructure About Nutanix Cloud Clusters on Azure ...structure/workloads/nc2-on-azure/about-nc2-on-azure.md
High 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 demonstrates a Windows bias by prioritizing Windows-specific benefits and tooling, such as Azure Hybrid Benefit for Windows and SQL Server, and free Extended Security Updates for Windows Server. These features are described in detail, including step-by-step instructions for requesting ESU keys for Windows VMs, while Linux equivalents are only briefly mentioned or omitted. There are no Linux-specific examples, instructions, or benefits highlighted, and Windows features are discussed first and in greater depth.
Recommendations
  • Include explicit examples and instructions for Linux workloads, such as how to leverage Azure Hybrid Benefit for Linux and supported distributions.
  • Provide parity in describing security update processes for Linux VMs, including how to manage updates and compliance in NC2 on Azure.
  • Add Linux-focused cost-saving opportunities and licensing details, similar to those provided for Windows.
  • Ensure that Linux and open source tooling (e.g., KVM, libvirt) are discussed with equal prominence as Windows tools and benefits.
  • Present Windows and Linux benefits side-by-side, rather than listing Windows features first and in greater detail.
GitHub Create Pull Request
Baremetal Infrastructure About Nutanix Cloud Clusters on Azure ...structure/workloads/nc2-on-azure/about-nc2-on-azure.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 by prioritizing Windows-related benefits, licensing, and tooling. Windows Server and SQL Server are mentioned explicitly and repeatedly in cost and licensing sections, with detailed instructions for obtaining Extended Security Updates (ESUs) for Windows VMs. Linux is mentioned only briefly and generically, with no specific examples, benefits, or instructions provided. There are no Linux-specific scenarios, cost benefits, or operational details, and no parity in examples or guidance for Linux workloads.
Recommendations
  • Add explicit examples and instructions for Linux VMs, such as how to leverage Azure Hybrid Benefit for Linux and supported Linux distributions.
  • Include cost benefits and licensing details for Linux workloads, similar to the Windows ESU section.
  • Provide operational guidance or migration scenarios for Linux workloads, not just Windows.
  • Ensure Linux tools and patterns (e.g., SSH, Linux management consoles) are mentioned alongside or before Windows equivalents.
  • Balance references to Windows and Linux in benefits and feature lists to reflect equal support.
GitHub Create Pull Request
Baremetal Infrastructure About Nutanix Cloud Clusters on Azure ...structure/workloads/nc2-on-azure/about-nc2-on-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 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-specific benefits (such as Azure Hybrid Benefit and Extended Security Updates for Windows Server), providing detailed instructions and links for Windows licensing and support, and omitting equivalent Linux-focused examples or benefits. While Linux is briefly mentioned in the context of Azure Hybrid Benefit, there are no concrete examples, instructions, or links for Linux users. The cost and support sections are heavily focused on Windows scenarios, and the process for obtaining security updates is described only for Windows VMs.
Recommendations
  • Add equivalent instructions and benefits for Linux VMs, such as how to obtain extended support or security updates for Linux distributions on NC2 on Azure.
  • Provide links to Linux product terms and documentation, similar to those given for Windows and SQL Server.
  • Include examples and guidance for Linux licensing reuse and migration under Azure Hybrid Benefit, with step-by-step instructions if applicable.
  • Balance the discussion of cost savings and support to include Linux scenarios, not just Windows.
  • Where Windows-specific tools or processes are described (e.g., ESU keys), offer parallel Linux examples or clarify any differences.
GitHub Create Pull Request
Baremetal Infrastructure https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/baremetal-infrastructure/workloads/nc2-on-azure/about-nc2-on-azure.md ...structure/workloads/nc2-on-azure/about-nc2-on-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 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-specific benefits (such as free Extended Security Updates for Windows Server), referencing Windows licensing and Azure Hybrid Benefit for Windows and SQL Server before mentioning Linux, and providing detailed instructions and processes only for Windows scenarios (e.g., requesting ESU keys for Windows VMs). There are no equivalent examples or instructions for Linux workloads, and the cost/benefit sections focus on Windows features and licensing. Linux is mentioned only briefly and generically, with no concrete examples or parity in guidance.
Recommendations
  • Include explicit examples and instructions for Linux workloads, such as how to leverage Azure Hybrid Benefit for Linux and manage Linux VMs in NC2 on Azure.
  • Provide details on cost savings, licensing, and support processes for Linux environments, similar to those given for Windows.
  • Balance the documentation by listing Linux and Windows benefits together, rather than focusing on Windows first.
  • Add guidance for requesting support or security updates for Linux VMs, if available, to match the Windows ESU process.
  • Highlight open source and cross-platform management tools where relevant, and avoid exclusive focus on Windows-centric features.
GitHub Create Pull Request
Baremetal Infrastructure https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/baremetal-infrastructure/workloads/nc2-on-azure/about-nc2-on-azure.md ...structure/workloads/nc2-on-azure/about-nc2-on-azure.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 by prioritizing Windows-related benefits and tooling. Windows Server and SQL Server licensing, Azure Hybrid Benefit, and Extended Security Updates for Windows are discussed in detail, with explicit instructions and links for Windows scenarios. Linux is mentioned only briefly and generically, without any examples, instructions, or links to equivalent Linux resources. There are no Linux-specific operational or licensing examples, nor any mention of Linux tooling or migration scenarios.
Recommendations
  • Add explicit examples and instructions for Linux workloads, including licensing, migration, and operational scenarios.
  • Include links to Linux product terms and documentation, similar to those provided for Windows Server and SQL Server.
  • Describe how Azure Hybrid Benefit applies to Linux, with concrete steps and references.
  • Provide parity in cost-saving and support information for Linux VMs, including any available extended support or migration benefits.
  • Ensure that Linux and Windows are presented with equal prominence in feature and benefit lists, rather than Windows-first ordering.
GitHub Create Pull Request
Baremetal Infrastructure https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/baremetal-infrastructure/workloads/nc2-on-azure/about-nc2-on-azure.md ...structure/workloads/nc2-on-azure/about-nc2-on-azure.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by emphasizing Windows Server features and benefits (such as Azure Hybrid Benefit and Extended Security Updates) before mentioning Linux, and by providing detailed instructions and processes specifically for Windows workloads (e.g., requesting ESU keys for Windows VMs) without equivalent Linux examples. The documentation also references Windows-specific licensing and support scenarios, while Linux is only briefly mentioned in passing, with no concrete examples or guidance for Linux users.
Recommendations
  • Provide parallel examples and instructions for Linux workloads, such as how to leverage Azure Hybrid Benefit for Linux distributions and how to manage Linux VMs in NC2 on Azure.
  • Include information about Linux-specific support, security update processes, and licensing benefits, similar to the detailed steps provided for Windows Server.
  • Balance the mention of Windows and Linux in benefit and feature lists, ensuring that Linux scenarios are not only acknowledged but also explained with actionable guidance.
  • If certain features (like ESU) are Windows-only, explicitly state this and offer alternative recommendations or resources for Linux users.
  • Add sample use cases or migration scenarios for both Windows and Linux workloads to demonstrate parity and inclusiveness.
GitHub Create Pull Request
Baremetal Infrastructure About Nutanix Cloud Clusters on Azure ...structure/workloads/nc2-on-azure/about-nc2-on-azure.md
Medium Priority View Details →
Scanned: 2026-01-14 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 moderate Windows bias, primarily in the benefits and licensing sections. Windows Server and SQL Server are mentioned first and in detail, with specific references to Windows-only features such as Extended Security Updates (ESU) and Azure Hybrid Benefit for Windows. The process for requesting ESU keys is exclusively for Windows VMs, with no equivalent Linux guidance. While Linux is mentioned briefly as eligible for Azure Hybrid Benefit, there are no concrete examples or instructions for Linux users, and no Linux-specific features or support processes are described.
Recommendations
  • Include explicit examples and instructions for Linux-based workloads, such as how to leverage Azure Hybrid Benefit for Linux and manage Linux VMs in NC2 on Azure.
  • Add details about support and lifecycle management for Linux VMs, including any relevant licensing, migration, or security update processes.
  • Balance the presentation of Windows and Linux benefits, mentioning Linux features and cost savings alongside Windows-specific ones.
  • If there are Linux equivalents to ESU or other Windows-only features, document them or clarify their absence.
  • Provide parity in step-by-step instructions for both Windows and Linux scenarios where applicable.
GitHub Create Pull Request
Baremetal Infrastructure About Nutanix Cloud Clusters on Azure ...structure/workloads/nc2-on-azure/about-nc2-on-azure.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. It emphasizes Windows-specific benefits (such as free Extended Security Updates for Windows Server), details licensing and cost savings for Windows and SQL Server, and provides explicit instructions for requesting Windows ESU keys. Linux is mentioned only briefly in the context of Azure Hybrid Benefit, with no comparable details or examples for Linux workloads, licensing, or security updates. There are no Linux-specific operational instructions, examples, or cost/benefit breakdowns, and Windows scenarios are described first and in greater detail.
Recommendations
  • Include equivalent details for Linux workloads, such as how to manage Linux VMs in NC2 on Azure, licensing options, and security update processes.
  • Provide examples or instructions for Linux-specific scenarios (e.g., migration, support, cost benefits) alongside Windows examples.
  • Balance the order and depth of coverage for Windows and Linux topics, ensuring Linux users can easily find relevant information.
  • Clarify any differences or parity between Windows and Linux support, especially regarding security updates and licensing benefits.
GitHub Create Pull Request
Baremetal Infrastructure Connect BareMetal Infrastructure instances in Azure ...tal-infrastructure/connect-baremetal-infrastructure.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 consistently presents Azure portal (GUI) and Azure CLI examples for managing BareMetal Infrastructure instances, but does not provide any Linux-specific command-line examples or mention Linux tools. The CLI instructions are platform-neutral but lack explicit guidance for Linux users (e.g., shell environment setup, authentication differences). The portal instructions assume a graphical environment, which is more common on Windows. There is no mention of PowerShell, but the absence of Linux-specific context or examples indicates a subtle Windows bias.
Recommendations
  • Add explicit instructions for Linux users, such as how to install and authenticate with Azure CLI on Linux.
  • Include example CLI commands run in a Bash shell, and clarify any differences in command syntax or environment variables between Windows and Linux.
  • Mention Linux desktop environments or alternatives for accessing the Azure portal, or provide guidance for users working in headless/server environments.
  • If relevant, provide examples using native Linux tools (e.g., curl, jq) for interacting with Azure REST APIs.
  • Ensure screenshots and step-by-step instructions are not exclusively tailored to Windows UI conventions.
GitHub Create Pull Request
Baremetal Infrastructure Architecture of BareMetal Infrastructure for NC2 on Azure ...-infrastructure/workloads/nc2-on-azure/architecture.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 consistently references Azure management via the portal, CLI, or PowerShell, but does not mention Linux-native tools or provide Linux-specific examples. There is an implicit Windows-first bias, as PowerShell is highlighted and no Linux command-line equivalents (such as Bash or Azure CLI usage on Linux) are shown. No Linux-specific deployment or management patterns are discussed.
Recommendations
  • Explicitly mention that Azure CLI is cross-platform and provide examples of managing NC2 on Azure from Linux environments using Bash and Azure CLI.
  • Include Linux-specific instructions or examples for common management tasks, such as cluster deployment, monitoring, and connectivity setup.
  • Clarify that PowerShell is available on Linux, but also show parity by providing Bash or shell script examples.
  • Reference Linux tools and patterns (e.g., SSH, scp, Linux-based automation) where relevant, especially for on-premises connectivity and VM management.
  • Ensure that diagrams and workflow descriptions do not assume a Windows-centric environment.
GitHub Create Pull Request
Baremetal Infrastructure Connect BareMetal Infrastructure instances in Azure ...tal-infrastructure/connect-baremetal-infrastructure.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 consistently presents Azure portal (GUI) and Azure CLI examples, but does not provide any Linux-specific command-line patterns, nor does it mention Powershell or Windows-only tools. However, the CLI instructions are platform-agnostic, and there is no explicit mention of Linux shell usage (e.g., Bash), nor are Linux-specific workflows or troubleshooting steps included. The portal instructions assume a graphical environment, which is more common on Windows, and there is no mention of Linux-native tools or integration. The documentation does not address Linux users directly, nor does it provide parity for Linux-specific scenarios.
Recommendations
  • Include explicit Bash shell examples for Azure CLI commands, showing usage in Linux terminals.
  • Add troubleshooting steps or notes for Linux environments (e.g., SSH access, file permissions, environment variables).
  • Mention that Azure CLI is cross-platform and provide links or instructions for installing and using it on Linux.
  • Provide parity for portal actions by describing equivalent command-line or automation workflows that Linux users may prefer.
  • Clarify any differences in experience or limitations when managing BareMetal instances from Linux versus Windows.
GitHub Create Pull Request
Baremetal Infrastructure Architecture of BareMetal Infrastructure for NC2 on Azure ...-infrastructure/workloads/nc2-on-azure/architecture.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 consistently references Azure management via the portal, CLI, or PowerShell, listing PowerShell (a Windows-centric tool) explicitly and omitting mention of Linux-native tools or workflows. No Linux-specific examples, commands, or tooling are provided, and Windows-oriented terminology (e.g., PowerShell) appears before any cross-platform alternatives.
Recommendations
  • Explicitly mention and provide examples for Azure CLI usage on Linux and macOS, not just PowerShell.
  • Include references to Linux-native tools and workflows for managing NC2 on Azure (e.g., bash scripts, SSH, Ansible).
  • Ensure that any command-line instructions are shown for both PowerShell and bash/CLI environments.
  • Add a section or note clarifying cross-platform support and parity, including any differences or limitations for Linux users.
  • Avoid listing Windows-centric tools (like PowerShell) before cross-platform alternatives unless there is a technical reason.
GitHub Create Pull Request
Baremetal Infrastructure Architecture of BareMetal Infrastructure for NC2 on Azure ...-infrastructure/workloads/nc2-on-azure/architecture.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 consistently references Azure management via the portal, CLI, or PowerShell, listing PowerShell (a Windows-centric tool) explicitly while omitting mention of Linux-native tools or workflows. No Linux-specific examples, commands, or integration patterns are provided, and Windows/PowerShell is mentioned before any cross-platform alternatives. This may create the impression that Windows is the primary or preferred environment for managing NC2 on Azure, despite the cross-platform nature of Azure and Nutanix.
Recommendations
  • Explicitly mention cross-platform management tools such as Azure CLI and Bash, and clarify their parity with PowerShell.
  • Provide Linux-specific examples for cluster management, connectivity, and deployment workflows (e.g., Bash scripts, Azure CLI commands run on Linux).
  • Include references to Linux-compatible automation and orchestration tools (such as Ansible, Terraform) where relevant.
  • Ensure that instructions and examples are presented in a platform-neutral order, or provide parallel examples for both Windows and Linux environments.
  • Clarify that all major management operations can be performed from Linux, macOS, and Windows, and link to documentation for Linux users where appropriate.
GitHub Create Pull Request
Baremetal Infrastructure Connect BareMetal Infrastructure instances in Azure ...tal-infrastructure/connect-baremetal-infrastructure.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 consistently provides examples and instructions for interacting with BareMetal Infrastructure instances using the Azure portal and Azure CLI, but does not mention or provide examples for Linux-specific tools, shell environments, or command-line patterns. The Azure CLI instructions are platform-agnostic but lack explicit Linux shell context (e.g., bash, zsh) and do not address Linux-specific nuances. There is no mention of PowerShell, but the portal instructions implicitly assume a Windows-centric workflow (e.g., screenshots, navigation patterns). No Linux desktop tools, shell scripts, or alternative workflows are referenced.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and provide example shell environments (e.g., bash, zsh) where relevant.
  • Include Linux-specific notes or troubleshooting tips (e.g., handling Azure CLI authentication on Linux, using environment variables).
  • Add screenshots or instructions for accessing the Azure portal from Linux browsers or desktop environments.
  • Mention or link to Linux automation options (e.g., shell scripting with Azure CLI, using cron jobs for instance management).
  • If relevant, provide parity for any Windows-specific patterns (such as PowerShell scripts) with equivalent bash/zsh examples.
GitHub Create Pull Request
Baremetal Infrastructure https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/baremetal-infrastructure/connect-baremetal-infrastructure.md ...tal-infrastructure/connect-baremetal-infrastructure.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 consistently presents Azure Portal (a web GUI, typically accessed from Windows environments) instructions before Azure CLI examples. There are no examples or references to Linux-specific tools, shell environments, or command-line patterns (e.g., Bash, SSH, SCP, etc.). All CLI examples use Azure CLI, which is cross-platform, but the documentation does not mention or show usage from Linux terminals, nor does it provide parity for Linux-specific workflows (such as connecting via SSH, using Bash scripting, or referencing Linux authentication patterns). There is a subtle Windows-first bias in ordering and in the lack of explicit Linux context.
Recommendations
  • Add explicit examples of using Azure CLI from Linux terminals (e.g., Bash), including screenshots or terminal output from Linux environments.
  • Mention that Azure CLI is cross-platform and provide instructions for installing and using it on Linux.
  • Include references to Linux-native tools and workflows where relevant (e.g., SSH for connecting to BareMetal instances, Bash scripting for automation).
  • Balance the ordering of examples so that CLI instructions are presented before or alongside portal instructions, emphasizing parity.
  • Where screenshots are shown, include examples from Linux desktops or terminals, not just the Azure Portal web interface.
GitHub Create Pull Request
Baremetal Infrastructure https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/baremetal-infrastructure/workloads/nc2-on-azure/architecture.md ...-infrastructure/workloads/nc2-on-azure/architecture.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 a Windows bias by referencing Azure CLI and PowerShell as management interfaces, but does not mention Linux-specific tools or provide Linux command examples. There are no Linux shell (bash) or cross-platform CLI instructions, and Windows-centric terminology (e.g., PowerShell) is presented without Linux equivalents.
Recommendations
  • Explicitly mention Linux compatibility for management interfaces (e.g., Azure CLI is cross-platform, available on Linux).
  • Provide Linux shell (bash) command examples alongside PowerShell, especially for deployment and management tasks.
  • Reference Linux tools and patterns (such as SSH, cloud-init, or Linux-based automation) where relevant.
  • Clarify that Nutanix Prism and Azure Portal are accessible from Linux systems.
  • Ensure that all instructions and examples are platform-neutral or include both Windows and Linux variants.
GitHub Create Pull Request
Baremetal Infrastructure https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/baremetal-infrastructure/connect-baremetal-infrastructure.md ...tal-infrastructure/connect-baremetal-infrastructure.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 consistently presents Azure portal (web UI) and Azure CLI examples for managing BareMetal Infrastructure instances, but does not provide any OS-specific command-line examples. There is a notable absence of Linux-specific instructions, such as bash scripting, SSH usage, or Linux-native tools. The documentation avoids Windows-specific tools like PowerShell, but the overall pattern is 'portal first' (which is most familiar to Windows users) and CLI second, without explicit Linux parity or examples.
Recommendations
  • Add explicit Linux command-line examples, such as using bash scripts to automate Azure CLI commands, or instructions for installing and using Azure CLI on Linux.
  • Include guidance for connecting to BareMetal instances via SSH from Linux terminals, if applicable.
  • Mention Linux-native tools or patterns (e.g., using environment variables, piping CLI output to jq for JSON parsing) in CLI sections.
  • Clarify that Azure CLI is cross-platform and provide installation instructions for both Windows and Linux.
  • If any OS-level management is required (e.g., logging into the BareMetal instance), provide both Windows (RDP/PowerShell) and Linux (SSH/terminal) examples.
GitHub Create Pull Request
Baremetal Infrastructure https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/baremetal-infrastructure/workloads/nc2-on-azure/architecture.md ...-infrastructure/workloads/nc2-on-azure/architecture.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 Windows bias by referencing the Azure portal, CLI, and PowerShell as management interfaces, but does not mention or provide examples for Linux-native tools or workflows. There are no Linux-specific command-line examples, nor is there mention of Linux shell usage for deployment or management. The documentation assumes familiarity with Windows-centric Azure management paradigms and omits Linux parity in examples and tooling references.
Recommendations
  • Explicitly mention and provide examples for Linux management workflows, such as using Azure CLI from Bash or other Linux shells.
  • Include sample commands for both PowerShell and Bash (or other Linux shells) when describing deployment and management steps.
  • Reference Linux-compatible tools and patterns (e.g., az CLI usage on Linux, SSH-based management) alongside Windows tools.
  • Clarify that the Azure CLI is cross-platform and provide links or instructions for installation and usage on Linux.
  • Ensure that all examples and instructions are presented with equal priority for both Windows and Linux environments.
GitHub Create Pull Request