Governance
305
Total Pages
190
Linux-Friendly Pages
115
Pages with Bias
37.7%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
613 issues found
Showing 576-600 of 613 flagged pages
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all queries, but PowerShell is always presented as a distinct tab, and there are no explicit Linux/macOS shell examples (e.g., Bash, zsh). The CLI examples are generic and cross-platform, but the presence of PowerShell-specific instructions and the lack of Linux/macOS-specific guidance or troubleshooting tips indicate a mild Windows bias. The ordering of tabs (CLI first, then PowerShell) is neutral, but the inclusion of PowerShell as a primary method may signal prioritization of Windows users.
Recommendations
- Add explicit Bash/zsh examples for Linux/macOS users, especially for common shell patterns (e.g., quoting, escaping).
- Clarify that Azure CLI commands work identically on Linux/macOS and Windows, and note any OS-specific caveats if present.
- Include troubleshooting tips or notes for Linux/macOS environments (e.g., installation, authentication differences).
- If PowerShell is mentioned, consider also mentioning cross-platform PowerShell Core (pwsh) and its compatibility.
Create Pull Request
Governance
Run Azure Resource Graph query using REST API
...cles/governance/resource-graph/first-query-rest-api.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page shows mild Windows bias: PowerShell is mentioned before Bash in prerequisites, and PowerShell examples are presented first in the command tabs. Visual Studio Code is recommended as the terminal environment, which is more common on Windows. There is a slight emphasis on Windows tools and patterns, but Linux/Bash examples are present and accurate.
Recommendations
- List Bash shell before PowerShell in prerequisites, or mention both equally.
- Present Bash examples first, or alternate the order in code tabs.
- Explicitly mention native Linux/macOS terminal environments (e.g., GNOME Terminal, Terminal.app) as alternatives to Visual Studio Code.
- Clarify that Azure CLI and az rest work equally well on Linux/macOS.
- Add a note that the instructions are cross-platform and highlight any platform-specific differences.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples, with the PowerShell example given its own section. PowerShell is a Windows-centric tool, and its inclusion as a primary example can be seen as a Windows bias. However, the Azure CLI example is present and is cross-platform. The order of examples (CLI first, then PowerShell) slightly favors cross-platform users, but the presence of a dedicated PowerShell section and no mention of Bash or Linux-specific shell usage is a minor bias.
Recommendations
- Explicitly mention that Azure CLI commands work on Windows, Linux, and macOS.
- Consider adding a Bash shell example or clarifying that the CLI example is suitable for Linux/macOS users.
- If possible, provide parity in scripting examples (e.g., Bash script for Linux, PowerShell for Windows) or clarify that PowerShell Core is available cross-platform.
- Add a note about installing Azure CLI and PowerShell on different platforms, linking to relevant guides.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples, but lists PowerShell immediately after CLI and before the portal, which may suggest a slight Windows-first ordering. PowerShell is a Windows-centric tool, though it is available cross-platform. No Linux/macOS-specific tools or shell examples (e.g., Bash) are provided, but the Azure CLI example is cross-platform compatible. No critical Linux omissions are present.
Recommendations
- Explicitly mention that Azure CLI works on Linux/macOS and Windows.
- Add a note clarifying that PowerShell Core is available on Linux/macOS, or link to installation instructions.
- Consider providing a Bash shell example (if applicable) to reinforce Linux parity.
- Rotate the order of examples periodically, or list CLI before PowerShell to emphasize cross-platform support.
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal. While Azure CLI is cross-platform, the inclusion of Azure PowerShell (which is traditionally Windows-centric, though now available on Linux/macOS) and the absence of any Linux/macOS-specific shell examples (such as Bash or scripting patterns) shows a mild Windows bias. No explicit Linux/macOS examples or guidance are given, and PowerShell is presented as a primary automation tool.
Recommendations
- Add explicit Bash or shell script examples for Linux/macOS users, demonstrating how to run the Azure CLI command in those environments.
- Clarify that Azure CLI is fully supported on Linux/macOS and provide installation or usage notes for those platforms.
- If PowerShell is recommended, note that PowerShell Core is cross-platform and provide guidance for Linux/macOS users.
- Consider including a section or tab for Linux/macOS usage patterns, especially for scripting and automation.
Governance
Azure machine configuration agent release notes
...es/governance/machine-configuration/whats-new/agent.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents Windows release notes before Linux, and in the example for updating the Linux extension, PowerShell is shown first, followed by Azure CLI. There is no evidence of Windows-only tools or missing Linux examples, but the ordering and example preference show a mild Windows bias.
Recommendations
- Alternate the order of Windows and Linux sections between releases or present them side-by-side.
- When providing command examples for Linux, show Azure CLI first (as it is cross-platform and more common for Linux users), then PowerShell.
- Explicitly mention Linux-specific tools or workflows where relevant.
- Ensure parity in detail and troubleshooting guidance between Windows and Linux sections.
Low Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation references Azure PowerShell as a management tool for Blueprints, but does not mention or provide examples for Azure CLI, which is cross-platform and commonly used on Linux/macOS. No Linux-specific tools or examples are provided, and the only management tool mentioned is PowerShell, which is traditionally associated with Windows, though it is available cross-platform. There are no explicit OS-specific commands or examples, but the omission of Azure CLI creates a subtle Windows bias.
Recommendations
- Mention Azure CLI as an alternative management tool for Blueprints alongside Azure PowerShell.
- Provide example commands for both Azure PowerShell and Azure CLI where relevant.
- Clarify that both PowerShell and CLI are cross-platform, and link to installation guides for Linux/macOS users.
- Avoid implying PowerShell is the only or primary method for managing Blueprints.
Governance
Deploy Australian Government ISM PROTECTED blueprint sample
.../governance/blueprints/samples/ism-protected/deploy.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page exhibits mild Windows bias, primarily in the artifact parameters table, where Windows-specific parameters (such as users in Windows VM Administrators group and Microsoft IaaSAntimalware extension for Windows servers) are listed before or alongside Linux equivalents. There is also a general tendency to mention Windows VM management tasks and tools (e.g., Administrators group, Antimalware extension) without equivalent detail for Linux (e.g., sudoers, Linux security agents). However, Linux is represented in several artifacts, and there are parameters for Linux VM management and monitoring.
Recommendations
- Ensure Linux-specific management tasks (such as sudoers group management, Linux security agent deployment) are described with parity to Windows examples.
- Where Windows VM parameters are listed (e.g., Administrators group), provide equivalent Linux VM parameters (e.g., sudoers, SSH users) and examples.
- If Windows security extensions (like Antimalware) are mentioned, include Linux alternatives (e.g., Microsoft Defender for Linux, or other supported agents).
- Review ordering in tables and documentation to avoid listing Windows examples or tools before Linux equivalents unless contextually justified.
- Explicitly state when a parameter or artifact applies only to Windows, and provide Linux-specific guidance where possible.
Governance
Deploy ISO 27001 Shared Services blueprint sample
...overnance/blueprints/samples/iso27001-shared/deploy.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Default Windows Values
Summary
The documentation page demonstrates a mild Windows bias, primarily through the use of Windows as the default operating system for jumpbox VMs and the inclusion of Windows-specific artifacts and parameters before their Linux equivalents. Windows VM examples and parameters are listed before Linux ones in the artifact parameters table, and the default value for the jumpbox OS is Windows. There is also a focus on Active Directory Domain Services, which is traditionally a Windows-centric technology. However, Linux options are present for some artifacts, and there are no critical steps that are Windows-only.
Recommendations
- List Linux and Windows examples and parameters in parallel, or alternate their order to avoid implicit prioritization.
- Explicitly mention Linux/macOS compatibility in steps involving VM deployment, jumpbox configuration, and Active Directory integration.
- Provide guidance or links for configuring Linux jumpboxes and integrating Linux VMs with Azure services.
- Set the default value for jumpbox OS to 'None' or prompt the user to choose, rather than defaulting to Windows.
- Include Linux/macOS-specific considerations in the main deployment steps, not just in artifact parameters.
Governance
Understand The Baseline Settings Parameter Format
...ty-baselines/understand-baseline-settings-parameter.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation provides examples and schema explanations for both Windows and Linux baselines, but the Windows Azure Security Baseline section is presented before the Linux equivalent, and Windows-specific scoping patterns (e.g., WindowsServer\<Year>\<Role>) are described in detail. Windows tools and patterns are mentioned explicitly, while Linux equivalents are described more generically and with less detail.
Recommendations
- Present Linux and Windows examples in parallel or alternate their order to avoid Windows-first bias.
- Provide equally detailed explanations of Linux-specific scoping, patterns, or any unique configuration options.
- If Windows-specific patterns are described (such as role/year scoping), clarify whether Linux has analogous mechanisms or explicitly state their absence.
- Ensure that examples for both platforms are equally comprehensive and appear with similar prominence.
- Consider adding a comparison table highlighting similarities and differences in parameter formats between Windows and Linux.
Governance
Azure Machine Configuration prerequisites
...chine-configuration/overview/02-setup-prerequisites.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page shows mild Windows bias. Windows is listed first in the validation tools table, and PowerShell Desired State Configuration (DSC) is emphasized for both Windows and Linux, with no mention of native Linux configuration tools like Ansible or shell scripting. References to configuring managed identities link specifically to Windows VM portal instructions, and PowerShell is mentioned more prominently than Azure CLI. Chef InSpec is listed for Linux, but only as a secondary tool.
Recommendations
- Provide examples and links for configuring managed identities on Linux VMs, not just Windows.
- Mention and, where possible, support native Linux configuration tools (e.g., Ansible, Bash scripts) in addition to PowerShell DSC.
- List Linux validation tools first or equally in tables and explanations.
- Ensure Azure CLI examples are given equal prominence to Azure PowerShell, especially for cross-platform tasks.
- Clarify that PowerShell DSC v3 for Linux is not the only option and provide guidance for users preferring native Linux tools.
Governance
View Machine Configuration Compliance Reporting
...rnance/machine-configuration/how-to/view-compliance.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page provides a cross-platform overview of Azure Machine Configuration compliance reporting, but exhibits mild Windows bias. The only command-line example given for programmatic access is a PowerShell cmdlet (Get-AzGuestConfigurationAssignment), and Power BI (a Windows-centric tool) is mentioned as a dashboard integration option. While CLI and REST API references are included for parity, the PowerShell example is listed before Linux-friendly alternatives, and no explicit Linux/macOS shell examples (e.g., Bash, az CLI usage) are shown. The UI screenshots and workflow descriptions are platform-neutral, but the command-line and automation sections lean toward Windows tools and patterns.
Recommendations
- Add explicit Linux/macOS shell examples (e.g., az CLI commands) for querying compliance data.
- Include sample Bash or shell scripts for common automation tasks alongside PowerShell examples.
- Mention open-source dashboard alternatives (e.g., Grafana) in addition to Power BI.
- Ensure CLI references (az policy, az guestconfig, az graph) are demonstrated with usage examples, not just linked.
- List Linux/macOS-friendly tools and commands before or alongside Windows/PowerShell options.
Governance
Manage your Azure subscriptions at scale with management groups - Azure Governance
...b/main/articles/governance/management-groups/manage.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation consistently presents Azure PowerShell examples before Azure CLI examples, and PowerShell command outputs are shown with Windows-style prompts (PS C:\>). There is a notable emphasis on PowerShell usage and terminology, which is most familiar to Windows users. While Azure CLI examples are provided throughout, PowerShell is often referenced first and in greater detail, including sample outputs and parameter explanations. There are no Linux/macOS-specific instructions, nor are cross-platform shell usage patterns discussed.
Recommendations
- Alternate the order of PowerShell and CLI examples, or present CLI examples first in some sections to balance platform representation.
- Include notes clarifying that both Azure PowerShell and Azure CLI are cross-platform, and provide guidance for installing and using them on Linux/macOS.
- Show sample outputs for CLI commands, not just PowerShell, to help Linux/macOS users.
- Avoid Windows-style prompts (e.g., PS C:\>) in code blocks, or provide equivalent bash/zsh prompts for CLI examples.
- Explicitly mention that all command-line examples work on Linux/macOS, and link to relevant installation guides for those platforms.
Governance
Design Azure Policy as Code workflows
.../articles/governance/policy/concepts/policy-as-code.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation mentions exporting policy and initiative definitions via PowerShell, CLI, or Azure Resource Graph, listing PowerShell first and referencing it as a primary tool. No explicit Linux/macOS shell examples (e.g., Bash, az CLI on Linux) are provided, and there is no mention of platform-specific considerations for Linux or macOS users. The workflow and automation recommendations (GitHub workflows, Azure Pipelines) are platform-neutral, but the lack of Linux/macOS examples and the PowerShell-first pattern create mild friction for non-Windows users.
Recommendations
- Provide explicit examples for Linux/macOS users, such as az CLI commands run in Bash.
- When listing tools, alternate or randomize the order, or mention CLI before PowerShell to avoid Windows-first bias.
- Add notes or links about running Azure CLI and automation on Linux/macOS, including any platform-specific considerations.
- Include sample scripts for both PowerShell and Bash where relevant.
- Clarify that all automation steps can be performed cross-platform and highlight any differences if present.
Governance
Details of the initiative definition structure
...nce/policy/concepts/initiative-definition-structure.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Summary
The documentation is largely platform-neutral, focusing on JSON structures and Azure concepts. However, there is a notable mention of the Windows PowerShell cmdlet 'Get-AzResourceProvider' as the method to determine valid resource types for the 'strongType' property, without referencing an equivalent Azure CLI or REST API method for Linux/macOS users. This creates a minor bias towards Windows/PowerShell users.
Recommendations
- Include Azure CLI equivalents (e.g., 'az provider list') alongside PowerShell examples when referencing resource provider queries.
- Mention REST API alternatives for resource provider discovery.
- Explicitly state that both Azure CLI and PowerShell can be used for these tasks, and provide example commands for each.
Governance
Author policies for array properties on resources
...governance/policy/how-to/author-policies-for-arrays.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions Azure CLI, Azure PowerShell, and REST API as ways to assign policy parameters, listing Azure CLI first, followed by Azure PowerShell (a Windows-centric tool), and then REST API. There are no explicit Linux/macOS-specific examples or references to Linux-native tools. However, Azure CLI is cross-platform and listed first, which mitigates most bias. No examples are provided that are exclusive to Windows or PowerShell, and no Windows-only tools or patterns are described.
Recommendations
- Explicitly state that Azure CLI is cross-platform and suitable for Linux/macOS users.
- Provide a brief example of using Azure CLI on Linux/macOS (e.g., bash shell) to reinforce parity.
- If mentioning PowerShell, clarify that PowerShell Core is available on Linux/macOS, or provide links to installation instructions for non-Windows platforms.
- Consider listing Azure CLI before Azure PowerShell when describing command-line options, or group them together as cross-platform tools.
- Add a note or section highlighting Linux/macOS compatibility for all tools mentioned.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation mentions PowerShell and Azure CLI as ways to assign policies, listing PowerShell first. There is no explicit mention of Linux/macOS-specific tools or workflows, and examples do not clarify cross-platform usage. The documentation refers to 'PowerShell' without specifying that Azure CLI is equally cross-platform, and does not provide parity guidance for Linux/macOS users.
Recommendations
- Explicitly state that Azure CLI is cross-platform and suitable for Linux/macOS users.
- Alternate the order of example links and instructions so that Azure CLI is listed before PowerShell in some places.
- Add notes or sections clarifying that all policy management tasks can be performed from Linux/macOS using Azure CLI.
- Include example commands for both Azure CLI and PowerShell side-by-side, or clarify when a command is platform-specific.
- Mention that Azure portal and Azure CLI are fully supported on Linux/macOS.
Governance
Tutorial: Create a custom policy definition
...ce/policy/tutorials/create-custom-policy-definition.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for discovering policy aliases, but PowerShell is mentioned after CLI and is not given exclusive focus. No explicit Windows-only tools or patterns are present, and the tutorial is generally cross-platform. However, the presence of PowerShell examples and references may create minor friction for Linux/macOS users unfamiliar with PowerShell.
Recommendations
- Ensure Azure CLI examples are always shown before PowerShell, as CLI is natively cross-platform.
- Explicitly note that Azure CLI works on Linux/macOS and provide links to installation instructions for those platforms.
- Where PowerShell is mentioned, clarify that Azure PowerShell Core is available cross-platform, or provide equivalent Bash examples if relevant.
- Consider adding a table or section summarizing which tools are available on which platforms.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents both Azure CLI and PowerShell examples for running queries, but PowerShell (a Windows-centric tool) is always shown alongside or immediately after CLI, and is referenced in prerequisites and notes. There is a slight Windows-first bias in the ordering and prominence of PowerShell instructions, but Azure CLI (cross-platform) is always included. No Linux-specific tools or shell examples (e.g., Bash) are provided, but tasks are achievable on Linux/macOS via Azure CLI. No critical functionality is locked to Windows.
Recommendations
- Explicitly mention that Azure CLI is fully supported on Linux/macOS and provide links to installation guides for those platforms.
- Consider presenting Azure CLI examples before PowerShell, or alternate the order, to avoid Windows-first perception.
- Add brief Bash shell usage examples for running Azure CLI commands to demonstrate Linux parity.
- Clarify that PowerShell Core is available cross-platform, but CLI is the recommended tool for Linux/macOS users.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation consistently provides both Azure CLI and Azure PowerShell examples for each query, but PowerShell examples are always present and sometimes accompanied by detailed PowerShell-specific notes (e.g., ConvertTo-Json depth). The PowerShell examples and notes are given equal prominence to CLI, and the JSON output examples use Windows-centric values (e.g., WindowsServer, osType: Windows). There is a slight Windows-first bias in example ordering and tooling, but Linux users can complete all tasks using Azure CLI. Shell scripting examples for Azure CLI use standard Unix tools (awk, sed, tail, cat), which are Linux/macOS-friendly.
Recommendations
- Explicitly mention that Azure CLI commands work on Linux/macOS and Windows, and clarify any platform-specific differences if present.
- Add notes or examples for macOS/Linux users where file handling or scripting differs (e.g., alternative commands for Windows CMD/PowerShell if needed).
- Consider alternating the order of Azure CLI and PowerShell examples, or grouping them under platform headings to avoid implicit prioritization.
- Provide example output for Linux-based virtual machines in addition to Windows-based ones to show parity.
- Clarify that PowerShell examples are for users who prefer PowerShell, not just Windows users.
Low Priority
View Details →
Detected Bias Types
Windows Shells Listed
Windows Shell Example
Windows First
Summary
The documentation page is largely cross-platform and focuses on KQL and Azure Resource Graph concepts. However, in the 'Escape characters' section, Windows shells (cmd, PowerShell) are listed alongside Bash, with PowerShell given a specific example, and cmd is mentioned before PowerShell. The PowerShell example is provided explicitly, while Bash is also covered. No Linux-specific tools or patterns are omitted, but the shell examples do show a slight Windows-first ordering and explicit PowerShell syntax.
Recommendations
- List Bash examples first to reflect the prevalence of Linux/macOS in cloud automation.
- Add a macOS-specific note if any shell differences exist (e.g., zsh vs. bash).
- Provide explicit Linux CLI examples where relevant (e.g., Azure CLI usage in Linux).
- Consider grouping shell examples by platform (Unix-like vs. Windows) for clarity.
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal. While Azure CLI is cross-platform, the inclusion of Azure PowerShell as a primary tab and the absence of explicit Linux/macOS shell examples (e.g., Bash) or notes about cross-platform compatibility may create a perception of Windows bias. PowerShell is traditionally associated with Windows, and its presence as a main example can signal a preference for Windows tooling. Additionally, the PowerShell example is listed before the Portal, which can reinforce this bias.
Recommendations
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
- Add a Bash shell example or clarify that the Azure CLI example is suitable for Bash and other Unix-like shells.
- Consider reordering tabs or providing a note that PowerShell is available cross-platform, to reduce the perception of Windows-first bias.
- If possible, add a section or note on using these queries in native Linux environments.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples, with the PowerShell example given its own dedicated section. While Azure CLI is cross-platform, the explicit inclusion of Azure PowerShell (which is most commonly used on Windows) and the ordering of examples (CLI first, then PowerShell) show a slight Windows-first and PowerShell-heavy bias. However, there are no examples or instructions that are strictly Windows-only, and the CLI example is fully usable on Linux/macOS.
Recommendations
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
- If possible, provide a Bash shell example (even if it simply repeats the CLI command) to reinforce Linux parity.
- Clarify that PowerShell Core is cross-platform, or note if the PowerShell example requires Windows-specific features.
- Consider adding a note about prerequisites or environment setup for Linux/macOS users (e.g., how to install Azure CLI or PowerShell Core on those platforms).
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all queries, with PowerShell being a Windows-centric tool. The PowerShell examples are given equal prominence to Azure CLI, but are always listed after the CLI examples. There are no Linux-specific shell examples (e.g., Bash), nor is there any mention of Linux/macOS-specific usage patterns or troubleshooting. However, the Azure CLI is cross-platform and the examples given are fully usable on Linux/macOS. No Windows-only tools or patterns are present, and the portal links are platform-agnostic.
Recommendations
- Explicitly state that Azure CLI commands work on Linux/macOS as well as Windows.
- Add example shell commands showing usage in Bash/zsh (e.g., with jq for output parsing).
- Include a brief note about installing and using Azure CLI on Linux/macOS.
- Consider de-emphasizing PowerShell unless there are Windows-specific steps.
- If PowerShell is included, clarify its cross-platform availability (PowerShell Core).
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal. Azure PowerShell is a Windows-centric tool, and its inclusion alongside Azure CLI in every example reflects a bias toward Windows users. The PowerShell example is always present and sometimes listed before the Portal option, which is cross-platform. There are no explicit Linux/macOS shell examples (e.g., Bash), nor is there mention of Linux-specific tools or patterns. However, Azure CLI is cross-platform and is included in every scenario, mitigating the bias somewhat.
Recommendations
- Clarify that Azure CLI is fully supported on Linux/macOS and provide installation or usage notes for those platforms.
- Consider adding Bash or shell script examples for Linux/macOS users where relevant.
- Reorder examples so that cross-platform tools (Azure CLI, Portal) are listed before Windows-centric tools (PowerShell).
- Explicitly mention platform compatibility for each tool, helping users choose the best option for their OS.