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 426-450 of 613 flagged pages
Governance
Details of the policy definition structure aliases
...vernance/policy/concepts/definition-structure-alias.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents Windows-centric tools and examples before Linux-friendly alternatives. The Azure PowerShell method is described and shown before Azure CLI, and PowerShell-specific notes and commands are highlighted. The Visual Studio Code extension is recommended first, which is cross-platform but often associated with Windows workflows. There are no explicit Linux-only examples or mentions of Linux-specific tooling.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples, as CLI is natively cross-platform and preferred by many Linux users.
- Add explicit notes clarifying that both PowerShell and CLI are available on Linux and macOS, not just Windows.
- Include Bash or shell script examples where appropriate, especially for command-line operations.
- Avoid PowerShell-specific notes unless a CLI equivalent is also provided.
- Highlight cross-platform compatibility of Visual Studio Code and its extensions.
- Consider adding a section or callout for Linux users, summarizing recommended tools and workflows.
Create Pull Request
Governance
Details of the policy definition structure parameters
...nce/policy/concepts/definition-structure-parameters.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page exhibits mild Windows bias by referencing the Windows-specific PowerShell cmdlet 'Get-AzResourceProvider' as the primary method to determine valid resource types for the 'strongType' property. No equivalent CLI or Linux-native tooling is mentioned, and the PowerShell approach is presented without alternatives or parity for Linux/macOS users.
Recommendations
- Include Azure CLI equivalents (e.g., 'az provider list') alongside PowerShell examples to ensure cross-platform accessibility.
- Explicitly mention that 'Get-AzResourceProvider' is a PowerShell cmdlet and provide instructions for using it on non-Windows platforms, or suggest alternatives.
- Add a note or section listing both PowerShell and Azure CLI commands for common resource provider queries.
- Review other sections for implicit Windows-first assumptions and ensure examples and tooling references are balanced between Windows and Linux environments.
Governance
Tutorial: Disallow resource types in your cloud environment
...es/governance/policy/tutorials/disallowed-resources.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively describes using the Azure portal (a web UI) for all steps and mentions Azure PowerShell and Azure CLI only in passing, without providing any command-line examples. There are no Linux-specific instructions, nor are cross-platform command-line workflows (such as Azure CLI commands) demonstrated. The only explicit mention of command-line tools is in a note, which lists Azure CLI and Azure PowerShell together, but does not provide usage details or parity. The documentation implicitly assumes users are working in a graphical environment, which is more common on Windows, and does not address Linux workflows or headless environments.
Recommendations
- Add step-by-step instructions for assigning and managing policies using Azure CLI, with example commands.
- Include equivalent Azure PowerShell commands for users who prefer scripting, and clarify cross-platform compatibility.
- Explicitly mention that Azure CLI is available on Linux, macOS, and Windows, and provide examples for Linux users.
- Add a section comparing portal-based and command-line workflows, highlighting when each is appropriate.
- Ensure screenshots and UI references are supplemented with text-based instructions for headless or non-GUI environments.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page exhibits mild Windows bias by consistently listing PowerShell before Azure CLI when mentioning tooling for policy assignment and management. There is a tendency to mention PowerShell examples and workflows before their cross-platform equivalents, and no explicit Linux-specific guidance or parity assurance is provided. However, the page does mention Azure CLI alongside PowerShell, which is cross-platform, and does not reference any Windows-only tools or patterns.
Recommendations
- Alternate the order of PowerShell and Azure CLI mentions, or list Azure CLI first in some sections to avoid implicit prioritization of Windows tooling.
- Explicitly state that Azure CLI is cross-platform and provide assurance that all examples and workflows are equally supported on Linux and macOS.
- Add a short section or note highlighting Linux/macOS compatibility and any platform-specific considerations for Azure Policy management.
- Ensure that all example links (e.g., assignment via CLI/PowerShell) are equally detailed and accessible for both platforms.
- Consider including Bash or shell script examples where relevant, especially in 'Policy as Code' workflows.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal. While Azure CLI is cross-platform, Azure PowerShell is primarily associated with Windows environments and is presented alongside CLI in all examples. There are no explicit Linux shell (e.g., Bash) or scripting examples, nor is there mention of Linux-specific usage patterns. The ordering of examples does not prioritize Linux-native tools, and the inclusion of PowerShell may imply a Windows-centric approach.
Recommendations
- Add explicit Bash shell examples for running Azure CLI commands to demonstrate Linux usage.
- Clarify that Azure CLI is fully cross-platform and can be used on Linux, macOS, and Windows.
- Consider including example scripts or usage patterns for Linux environments (e.g., using az graph query in a Bash script).
- If PowerShell is included, mention that PowerShell Core is available cross-platform, or provide guidance for Linux users.
- Review the ordering of examples to avoid implicit prioritization of Windows tools over Linux equivalents.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal. While Azure CLI is cross-platform, Azure PowerShell is Windows-centric and is presented as a primary tab. There are no explicit Linux shell (bash) examples, nor is there mention of Linux-specific tools or usage patterns. The PowerShell example is given equal prominence to the CLI, which may suggest a Windows bias, especially for users seeking Linux-native instructions.
Recommendations
- Add explicit bash shell examples using Azure CLI to demonstrate usage in Linux environments.
- Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
- Consider reordering tabs to present Azure CLI before PowerShell, emphasizing cross-platform compatibility.
- Mention installation or usage notes for Azure CLI on Linux systems.
- If PowerShell is included, note that PowerShell Core is available on Linux, or provide instructions for both Windows PowerShell and PowerShell Core.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal for each query. While Azure CLI is cross-platform, the inclusion of Azure PowerShell examples (which are primarily used on Windows, though available on Linux/macOS) and the explicit labeling of 'Azure PowerShell' tabs suggests a Windows-centric approach. Additionally, PowerShell examples are always present and given equal prominence to CLI, but there are no Linux-specific shell examples (e.g., Bash, zsh), nor are there any references to Linux-native tools or patterns. The documentation does not mention or demonstrate usage in Linux environments, nor does it clarify cross-platform compatibility for PowerShell or CLI. The ordering of tabs sometimes places PowerShell before Portal, which can reinforce a Windows-first mindset.
Recommendations
- Add explicit Bash or zsh shell examples for Linux users, showing how to run the Azure CLI queries in a typical Linux terminal.
- Clarify that Azure CLI is fully cross-platform and provide guidance for Linux/macOS installation and usage.
- Note that Azure PowerShell is available on Linux/macOS, and provide installation instructions or links for those platforms.
- Consider reordering tabs so that Azure CLI (the most cross-platform tool) is listed first, followed by PowerShell and Portal.
- Include a brief section discussing cross-platform support and any differences in experience between Windows and Linux/macOS.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal. While Azure CLI is cross-platform, Azure PowerShell is Windows-centric and is always presented as a primary tab alongside CLI and Portal. There are no Linux-specific shell examples (e.g., Bash, zsh), nor is there mention of Linux-native tools or scripting patterns. The ordering of tabs consistently places PowerShell before Portal, which may reinforce Windows-centric workflows.
Recommendations
- Explicitly state that Azure CLI commands work natively on Linux, macOS, and Windows.
- Add example invocations using Bash/zsh, including piping and output parsing (e.g., using jq).
- Clarify that Azure PowerShell is available cross-platform, but recommend CLI for Linux users.
- Consider reordering tabs to place Azure CLI before PowerShell, or add a 'Linux shell' tab with Bash examples.
- Mention installation instructions or prerequisites for Linux users where relevant.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation consistently provides both Azure CLI and Azure PowerShell examples for each query, but PowerShell is highlighted as a primary scripting interface alongside CLI. PowerShell is a Windows-centric tool, and its inclusion in every example may suggest a bias toward Windows users. There are no Linux-specific shell examples (e.g., Bash scripts, shell pipelines), nor is there mention of Linux-native tools or patterns. The ordering of examples is Azure CLI first (cross-platform), then PowerShell (Windows-centric), but the lack of Linux-specific scripting examples means Linux parity is not fully addressed.
Recommendations
- Add Bash shell examples for each query, demonstrating usage in Linux environments.
- Clarify that Azure CLI is fully supported on Linux and macOS, and provide installation/usage notes for those platforms.
- Include notes or examples for using the queries in automation scripts on Linux (e.g., with curl, jq, or shell pipelines).
- Consider referencing cross-platform scripting approaches (e.g., Python, REST API usage) for broader parity.
- Explicitly mention platform compatibility for each tool, helping users choose the best option for their OS.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation consistently presents Azure PowerShell examples alongside Azure CLI and Portal, but PowerShell is a Windows-centric tool. The tab order always lists Azure CLI first, then PowerShell, then Portal, which is good for parity, but the inclusion of PowerShell as a primary example may signal a Windows bias. There are no explicit Linux-only examples or references to Linux-specific shell environments (e.g., Bash, zsh), nor is there mention of cross-platform scripting patterns. However, the Azure CLI is cross-platform and is presented first, which helps mitigate bias.
Recommendations
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
- Add example usage in Bash or zsh, especially for scenarios where output parsing or scripting is relevant.
- Clarify that PowerShell Core is cross-platform, but note that many users associate PowerShell with Windows.
- Consider including links or notes about installing and using Azure CLI on Linux.
- If relevant, provide troubleshooting or environment setup notes for Linux users (e.g., authentication, shell integration).
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation consistently presents Azure PowerShell examples alongside Azure CLI and Portal, with PowerShell given its own dedicated tab. While Azure CLI is cross-platform, the inclusion of PowerShell (a Windows-centric tool, despite recent cross-platform support) and the absence of Linux-specific shell examples (such as Bash scripts or direct curl/REST usage) indicate a mild Windows bias. Additionally, PowerShell examples are always present, but there are no examples for Linux-native tools or workflows.
Recommendations
- Add explicit Bash or shell script examples for Linux users, especially for common scenarios.
- Include curl or REST API examples where applicable to demonstrate platform-agnostic access.
- Clarify that Azure CLI commands work equally on Linux, macOS, and Windows, and consider showing CLI output in a Linux terminal context.
- If PowerShell is shown, note its cross-platform availability and provide guidance for installation/use on Linux.
- Consider adding a 'Linux shell' or 'Bash' tab alongside CLI and PowerShell for parity.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal, but the PowerShell example is given equal prominence to the CLI and appears before the portal example. There is no explicit Linux shell (bash, zsh) example, nor is there mention of Linux-specific tools or usage patterns. The CLI example is cross-platform, but PowerShell is traditionally associated with Windows, and its inclusion without a corresponding Linux shell example suggests a mild Windows bias.
Recommendations
- Add a Bash or shell example using az graph query for Linux users.
- Clarify that Azure CLI works on both Windows and Linux, and provide usage notes for each platform if relevant.
- Consider reordering examples so that cross-platform tools (CLI) appear before Windows-specific tools (PowerShell).
- Explicitly mention Linux compatibility and provide troubleshooting or environment setup notes for Linux users.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal. Azure PowerShell is highlighted as a primary method, which is predominantly used on Windows. The ordering places Azure CLI first, which is cross-platform, but the inclusion of PowerShell as a separate tab and the lack of explicit Linux shell (bash/zsh) examples or notes about cross-platform compatibility for PowerShell may suggest a subtle Windows bias.
Recommendations
- Add explicit bash/zsh shell examples for Linux users, especially for Azure CLI usage.
- Clarify that Azure CLI works natively on Linux, macOS, and Windows.
- Note that PowerShell Core is available cross-platform, and provide guidance or examples for running PowerShell commands on Linux/macOS.
- Consider including a section or tab for Linux-specific usage patterns or troubleshooting.
- Ensure that tool ordering does not imply Windows preference (e.g., alternate the order or clarify cross-platform support).
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples, but the inclusion of PowerShell (a Windows-centric tool) as a primary tab and the lack of explicit Linux shell or bash examples may indicate a slight Windows bias. The CLI example is cross-platform, but PowerShell is still highlighted, and there is no mention of Linux-specific shell usage or alternative Linux-native tools.
Recommendations
- Add explicit Bash or Linux shell examples, even if they mirror the Azure CLI usage, to demonstrate parity and acknowledge Linux users.
- Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and provide sample shell prompts (e.g., $ for bash, PS> for PowerShell) to reinforce cross-platform support.
- If PowerShell is included, consider also referencing PowerShell Core (pwsh), which is cross-platform, and clarify its compatibility.
- Ensure that documentation does not assume PowerShell as the default scripting environment, especially for cross-platform audiences.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal. While Azure CLI is cross-platform, Azure PowerShell is primarily associated with Windows environments, and its example is given equal prominence. There is no explicit mention of Linux-specific tools, nor are there any Linux shell (bash) examples. The ordering places Azure CLI first, which is positive for parity, but the inclusion of PowerShell without a corresponding bash or Linux shell example may suggest a slight Windows bias.
Recommendations
- Add explicit bash shell examples using Azure CLI to demonstrate usage in Linux environments.
- Clarify that Azure CLI commands work identically on Linux, macOS, and Windows.
- Consider adding a note or section highlighting cross-platform compatibility and any OS-specific considerations.
- If PowerShell is shown, also show equivalent bash usage for parity.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for running Resource Graph queries, but PowerShell is given equal prominence to CLI, despite being a Windows-centric tool. There are no explicit Linux shell (bash) or scripting examples, nor is there mention of Linux-specific usage patterns. The tabs are ordered as Azure CLI, then PowerShell, but PowerShell is featured as a primary method, which may imply Windows bias. No Linux-specific tools or instructions are provided.
Recommendations
- Add explicit bash shell examples for running Azure CLI commands, demonstrating usage in Linux environments.
- Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows, while PowerShell is primarily Windows-centric (though available on Linux, but less common).
- Include notes or links to installing and using Azure CLI on Linux systems.
- Consider providing examples of using the queries in automation scripts (e.g., bash scripts) for Linux users.
- If PowerShell is mentioned, also mention pwsh (PowerShell Core) and clarify its cross-platform availability, but note that CLI is the default for Linux.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal. While Azure CLI is cross-platform, the PowerShell example is Windows-centric and is presented before any mention of Linux-specific shell usage (such as Bash). There are no explicit Linux shell (Bash) examples, nor is there any mention of running the CLI commands in a Linux environment. The order of tabs and examples (CLI, PowerShell, Portal) tends to favor Windows tools and patterns, with PowerShell given equal prominence to CLI, despite CLI being more universal.
Recommendations
- Add explicit Bash/Linux shell examples for the Azure CLI command, showing usage in a Linux terminal.
- Clarify that Azure CLI commands work on both Windows and Linux, and provide sample outputs or notes for both environments.
- Consider reordering tabs or examples to lead with cross-platform tools (Azure CLI/Bash) before Windows-specific tools (PowerShell).
- If PowerShell is included, note that PowerShell Core is available on Linux and macOS, and provide guidance for those platforms.
- Avoid presenting Windows-centric tools (PowerShell) as the default or primary method unless the audience is specifically Windows-only.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples, but the PowerShell example is given equal prominence to the CLI example, despite PowerShell being primarily a Windows-centric tool (even though it is now cross-platform, its usage is still heavily associated with Windows). There are no Linux-specific shell examples (e.g., Bash), nor is there mention of Linux-native tools or patterns. The CLI example is generic, but the presence of PowerShell as a primary tab can be interpreted as a Windows-first bias.
Recommendations
- Add explicit Bash shell examples for running the Azure CLI command, including syntax for Linux environments.
- Clarify that Azure CLI works natively on Linux/macOS and provide installation or usage notes for those platforms.
- Consider reordering tabs so that CLI (cross-platform) appears before PowerShell (Windows-centric), or add a note about platform compatibility.
- If PowerShell is shown, mention that it is available on Linux/macOS, but provide a Bash alternative for Linux users.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples, but lists PowerShell as a primary tab, which is more commonly used on Windows. There is no explicit Linux shell example (e.g., Bash), and PowerShell is highlighted as a separate usage pattern, which may suggest a Windows-centric approach.
Recommendations
- Add explicit Bash/Linux shell examples for Azure CLI usage, showing command execution in a typical Linux environment.
- Clarify that Azure CLI works cross-platform and provide sample output or usage in both Windows (CMD/PowerShell) and Linux (Bash/zsh) shells.
- Ensure that PowerShell is not presented as the default or primary method unless justified by user data; consider listing CLI/Bash examples first.
- Add notes or sections highlighting any platform-specific differences or considerations for Linux users.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation consistently presents Azure CLI and Azure PowerShell examples side-by-side, but PowerShell (a Windows-centric tool) is always given equal prominence and is listed immediately after Azure CLI. There are no explicit Linux shell (bash) examples, nor any mention of Linux-specific tools or usage patterns. The documentation does not acknowledge platform differences or provide guidance for Linux users beyond Azure CLI, which is cross-platform but often used differently on Linux.
Recommendations
- Add explicit bash shell examples for each query, demonstrating usage in a typical Linux environment.
- Clarify that Azure CLI is cross-platform and provide platform-specific notes where relevant (e.g., differences in quoting or escaping characters).
- Consider listing Azure CLI (Linux-friendly) examples before PowerShell, or grouping PowerShell as a Windows-specific tab.
- Include troubleshooting or environment setup notes for Linux users, such as installation instructions for Azure CLI on Linux.
- Avoid assuming PowerShell is universally available; mention alternatives for Linux users where PowerShell functionality is referenced.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation consistently provides both Azure CLI and Azure PowerShell examples for each query, but PowerShell is featured as a first-class option throughout, with variable assignment and usage examples that are distinctly PowerShell-centric (e.g., $subid = (Get-AzContext).Subscription.Id). There is no explicit mention of Linux-specific shell environments (such as bash, zsh, etc.), nor are there examples tailored to Linux users (e.g., using bash scripting, environment variables, or shell-specific quoting/escaping guidance). The documentation assumes parity between CLI and PowerShell, but the variable assignment and scripting examples are Windows/PowerShell-oriented, and PowerShell is listed before CLI in some places, suggesting a Windows-first approach.
Recommendations
- Add explicit Linux/bash examples for variable assignment and scripting (e.g., show how to use export, $(), and quoting/escaping in bash/zsh).
- Include notes or examples for common Linux shell environments, such as bash, zsh, or fish, especially where quoting or escaping is required.
- Ensure Azure CLI examples are as detailed as PowerShell ones, including variable usage and scripting patterns.
- Where PowerShell-specific patterns are shown, provide equivalent bash/Linux shell patterns side-by-side.
- Review ordering of examples to avoid listing PowerShell before CLI by default; consider listing CLI first or alternating order.
- Add troubleshooting notes for Linux users regarding shell differences, quoting, and environment setup.
Governance
Azure machine configuration agent release notes
...es/governance/machine-configuration/whats-new/agent.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides separate release notes for Windows and Linux extensions, generally maintaining parity in feature descriptions and fixes. However, in the Linux section, instructions for updating the extension include PowerShell examples before Azure CLI, which may be less familiar or relevant to Linux users. Additionally, PowerShell is mentioned as being upgraded on Linux, which may not reflect typical Linux management patterns. There are no Linux shell (bash) examples, and Windows tools/patterns (PowerShell) are referenced for Linux scenarios.
Recommendations
- Provide bash or shell script examples for Linux extension management alongside or instead of PowerShell.
- Prioritize Azure CLI or native Linux commands in Linux documentation sections, placing PowerShell examples after or in a separate tab.
- Clarify the role of PowerShell on Linux and offer alternatives where appropriate.
- Ensure that Linux-specific tools and patterns are highlighted in Linux documentation, not Windows-centric ones.
Governance
Quickstart: Create a management group with .NET Core
...ce/management-groups/create-management-group-dotnet.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows by providing only Windows-style execution instructions (using mgCreate.exe with backticks for line continuation), and omitting Linux-specific guidance such as using mgCreate.dll or mgCreate with mono/dotnet, and Linux shell syntax. There are no examples or notes for running the application on Linux or macOS, despite .NET Core being cross-platform.
Recommendations
- Add explicit instructions and examples for running the .NET Core application on Linux and macOS, including the correct executable (e.g., mgCreate.dll with dotnet, or mgCreate without .exe if published as a self-contained app).
- Provide both Windows (PowerShell/CMD) and Linux (bash/zsh) command syntax for running the application, including line continuation differences.
- Clarify any platform-specific requirements or differences in the build and publish steps, such as file extensions and permissions.
- Mention that .NET Core is cross-platform and encourage users on Linux/macOS to follow the equivalent steps.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal. While Azure CLI is cross-platform, Azure PowerShell is primarily associated with Windows environments and is listed before any mention of Linux-specific tools or shells. There are no explicit Linux shell (bash) examples, nor is there mention of Linux-specific usage patterns. The ordering and inclusion of PowerShell may suggest a Windows-centric approach.
Recommendations
- Add explicit bash shell examples for running Azure CLI commands on Linux/macOS.
- Clarify that Azure CLI works natively on Linux/macOS and provide sample commands in a Linux shell context.
- Consider reordering examples to present cross-platform tools (Azure CLI) before Windows-specific tools (PowerShell).
- Mention installation or usage notes for Linux users where relevant.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents 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. The inclusion of PowerShell as a primary example can be seen as Windows-centric, given its historical association with Windows, although it is now cross-platform. No explicit Linux-only tools or shell examples (e.g., Bash) are provided, but the Azure CLI example is cross-platform. There are no examples that are exclusive to Windows tools, and no Linux-specific examples are missing for the core functionality.
Recommendations
- Explicitly mention that Azure CLI works on Linux, macOS, and Windows.
- Consider providing a Bash shell example to demonstrate usage on Linux/macOS.
- Clarify that PowerShell is now cross-platform, if included, to avoid perceived Windows bias.
- Ensure ordering of examples does not imply platform preference (e.g., alternate order or group by platform).