Batch
228
Total Pages
164
Linux-Friendly Pages
64
Pages with Bias
28.1%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
156 issues found
Showing 126-150 of 156 flagged pages
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation provides both Windows and Linux information, but there are signs of Windows bias. Windows is often mentioned first in lists and explanations, and Windows-specific details (such as disk paths, ephemeral disk mapping, and VM sizing guidance) are given more prominence. Most code examples use Linux images, but when showing container task command lines, the C# example uses a Windows path and executable, while the Python example uses Linux conventions. There are no explicit PowerShell examples, but Windows tooling and patterns (e.g., C:\ paths, references to Windows container limitations) are present. Linux-specific troubleshooting and advanced configuration are less detailed than their Windows counterparts.
Recommendations
- Alternate the order of Windows and Linux mentions to avoid implicit prioritization.
- Provide parallel examples for both Windows and Linux container tasks, especially in code snippets (e.g., show both Windows and Linux command lines in C# and Python).
- Include Linux-specific troubleshooting steps and advanced configuration guidance, matching the detail provided for Windows.
- Clarify when instructions or limitations apply only to Windows or only to Linux, rather than presenting Windows details as the default.
- Add explicit Linux/macOS shell examples where appropriate, especially for start tasks and custom image setup.
Create Pull Request
Batch
Choose VM sizes and images for pools
...e-docs/blob/main/articles/batch/batch-pool-vm-sizes.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both PowerShell and Azure CLI examples for listing VM sizes and images, but PowerShell (a Windows-centric tool) is consistently mentioned first in lists and tips. There are no explicit Linux/macOS-only examples or tools (such as Bash scripts or references to Linux-specific commands), and the documentation does not address platform-specific nuances beyond mentioning both Windows and Linux VM images are supported.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or list Azure CLI first to reflect its cross-platform nature.
- Include Bash or shell script examples for Linux/macOS users where relevant.
- Explicitly mention that Azure CLI works on Linux/macOS and provide installation/use links.
- Add notes or sections highlighting any platform-specific considerations for Linux/macOS users.
- Consider referencing Linux-native tools or workflows if applicable.
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation generally maintains cross-platform awareness, but there are subtle signs of Windows bias. In the section on specifying the command line for tasks, the Windows example ('cmd /c MyTaskApplication.exe %MY_ENV_VAR%') is listed before the Linux example ('/bin/sh -c MyTaskApplication $MY_ENV_VAR$'). Additionally, the use of 'robocopy' and 'setup.exe' as examples of start task operations are Windows-specific tools, with no Linux equivalents mentioned. These choices may make Linux/macOS users feel secondary or require them to infer their own platform-specific commands.
Recommendations
- Alternate the order of Windows and Linux examples, or present both simultaneously to avoid implicit prioritization.
- When mentioning Windows-specific tools like 'robocopy' or 'setup.exe', also provide Linux/macOS equivalents (e.g., 'cp', 'rsync', 'tar', or '.sh' scripts).
- Explicitly state that all features and examples apply equally to Linux/macOS nodes, and provide links or references to platform-specific guidance where relevant.
- Include more Linux/macOS-centric examples in sections discussing command lines, start tasks, and application installation.
Batch
Plan to manage costs for Azure Batch
...-docs/blob/main/articles/batch/plan-to-manage-costs.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page for managing costs in Azure Batch shows a minor Windows bias by linking to the Windows VM pricing page first when discussing virtual machine costs. However, the content does not provide OS-specific examples, CLI commands, or tooling, and most instructions are platform-neutral, focusing on the Azure portal and general concepts.
Recommendations
- When mentioning virtual machine costs, provide links to both Windows and Linux VM pricing pages, or use a neutral landing page that lets users select their OS.
- Explicitly mention that Batch supports both Windows and Linux VMs, and clarify any cost differences or considerations for each.
- If examples or screenshots reference OS-specific options, ensure both Windows and Linux are represented.
Batch
Manage private endpoint connections with Azure Batch accounts
.../articles/batch/manage-private-endpoint-connections.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure PowerShell and Azure CLI examples, but PowerShell examples are presented before CLI, and the PowerShell module is highlighted with a direct link. This ordering and emphasis may subtly favor Windows users, as PowerShell is more commonly used on Windows, while CLI is cross-platform. However, Linux/macOS users are not blocked from completing the task, as full CLI examples are provided.
Recommendations
- Present Azure CLI examples before PowerShell examples to prioritize cross-platform usage.
- Explicitly mention that both CLI and PowerShell are available on Windows, Linux, and macOS.
- Add notes or links for installing Azure CLI and PowerShell on Linux/macOS.
- Ensure parity in example detail and clarity between CLI and PowerShell sections.
Batch
Associate Azure Batch accounts with network security perimeter
...blob/main/articles/batch/network-security-perimeter.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides step-by-step instructions for associating an Azure Batch account with a network security perimeter using the Azure portal, PowerShell, and Azure CLI. The PowerShell example is given before the Azure CLI example, which may indicate a slight Windows-first bias. The presence of detailed PowerShell instructions (which are most commonly used on Windows) and the ordering of PowerShell before CLI suggest a mild preference for Windows tooling. However, Azure CLI is well-supported on Linux/macOS and is included with full example parity. No critical functionality is missing for Linux/macOS users.
Recommendations
- Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and preferred by many Linux/macOS users.
- Explicitly mention that Azure CLI commands work on Linux/macOS and Windows.
- Add a short note clarifying that PowerShell Core is available on Linux/macOS if users prefer PowerShell.
- Ensure screenshots and UI references are not Windows-centric (e.g., avoid showing Windows-only UI elements if possible).
Batch
Configure node endpoints in Azure Batch pool
...lob/main/articles/batch/pool-endpoint-configuration.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation alternates between Windows (RDP) and Linux (SSH) examples, but consistently presents Windows/RDP examples first in each section. Windows terminology (RDP, port 3389) is introduced before Linux equivalents (SSH, port 22), and C# is used for Windows examples while Python is used for Linux, which may reflect common platform usage but reinforces the Windows-first pattern. No PowerShell-specific or Windows-only tools are used, and Linux parity is maintained in example coverage.
Recommendations
- Alternate the order of examples so Linux/SSH is presented first in some sections.
- Add a summary table comparing RDP (Windows) and SSH (Linux) endpoint configuration side-by-side.
- Explicitly mention that both Windows and Linux pools are equally supported and clarify any platform-specific differences.
- Consider providing both C# and Python examples for each scenario, regardless of OS, to avoid reinforcing language/platform associations.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page generally presents Azure Batch as supporting both Windows and Linux nodes, but there are subtle signs of Windows bias. Windows-specific executable types and tools (e.g., .exe, .cmd, .bat, PowerShell scripts) are listed first and in more detail than Linux equivalents. Container support examples mention Windows Server images before Linux options. Remote access methods list RDP (Windows) before SSH (Linux). There is a tendency to mention Windows patterns and tools prior to Linux ones, and some sections (e.g., container support) focus on Windows images and Docker setup without equal Linux coverage.
Recommendations
- List Linux script types (e.g., shell scripts, Python) before or alongside Windows types when discussing supported executables.
- Provide explicit Linux examples and references in container support sections, such as mentioning Ubuntu or other Linux Marketplace images that support Docker.
- When discussing remote access, alternate or balance the order of RDP and SSH references.
- Ensure that any tooling or configuration examples are provided for both Windows and Linux environments.
- Add links to Linux-specific guides or documentation where appropriate.
Batch
Azure Quickstart - Create a Batch account - Bicep file
...re-docs/blob/main/articles/batch/quick-create-bicep.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying and managing resources. While Azure CLI is cross-platform, Azure PowerShell is primarily used on Windows, and its examples are given equal prominence. In each section, CLI examples are shown first, but PowerShell is always included, which may suggest a slight Windows bias. No Linux-specific tools or workflows are mentioned, but CLI coverage ensures Linux/macOS users are not blocked.
Recommendations
- Explicitly mention that Azure CLI works on Linux/macOS and is recommended for cross-platform use.
- Consider adding a note that Azure PowerShell is available on Linux/macOS, but CLI is more commonly used in those environments.
- Include brief instructions or links for installing Azure CLI on Linux/macOS.
- If possible, add a section or sidebar highlighting cross-platform compatibility.
Batch
Create a simplified node communication pool without public IP addresses
...tch/simplified-node-communication-pool-no-public-ip.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Windows and Linux command examples for network troubleshooting, but Windows (PowerShell) commands are listed first. There is a slight emphasis on Windows tools and patterns in the troubleshooting section, with PowerShell's Test-NetConnection shown before Linux's nc. No other sections show Windows-only bias, and examples for pool creation use platform-neutral tools (REST API, ARM templates, Azure portal).
Recommendations
- Present Linux and Windows troubleshooting commands side-by-side or alternate which is shown first.
- Include explicit instructions or links for Linux/macOS users where platform-specific steps are required.
- Where possible, provide parity in screenshots or UI guidance for both Windows and Linux environments.
- Clarify that all major steps (pool creation, network setup) can be performed from Linux/macOS using Azure CLI or REST API.
Batch
Migrate Azure Batch pools to the simplified compute node communication model
...ified-compute-node-communication-model-migration-guide.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation mentions Windows-specific tools and patterns before Linux equivalents, such as referencing 'Microsoft.BatchClusters.Agent.exe' (Windows) before 'Microsoft.BatchClusters.Agent' (Linux). There are no explicit PowerShell-heavy examples or missing Linux examples, but Windows terminology is presented first in agent naming. No platform-specific commands or configuration steps are given, so the bias is minor.
Recommendations
- List Linux and Windows agent names in parallel or alphabetically, not with Windows first.
- Where platform-specific tools or filenames are mentioned, clarify both Linux and Windows variants together.
- Add explicit examples or notes for both Linux and Windows users if future documentation includes commands or configuration steps.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page generally presents Azure Batch as supporting both Windows and Linux nodes, but there is a subtle Windows bias. Windows-specific executable/script types (e.g., .exe, .cmd, .bat, PowerShell) are listed first and in more detail than Linux equivalents. Remote access methods mention Windows RDP before Linux SSH. Container support examples reference Windows Server images first, and Docker setup instructions focus on Windows images before mentioning custom Linux images. There are no explicit Linux command-line or shell script examples, and Windows tools/patterns are referenced more frequently and earlier.
Recommendations
- List Linux script types (e.g., shell, Python) before or alongside Windows types.
- Provide explicit Linux examples for remote access (e.g., SSH commands) and container setup.
- Mention Linux VM images and Docker support before or alongside Windows Server images.
- Include references to Linux-specific tools and workflows where relevant.
- Balance the order and detail of Windows and Linux information throughout the documentation.
Batch
Create a simplified node communication pool without public IP addresses
...tch/simplified-node-communication-pool-no-public-ip.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Windows and Linux command examples for network troubleshooting, but consistently lists Windows (PowerShell) commands first. The troubleshooting section uses 'Test-NetConnection' (PowerShell) before 'nc' (Linux), and the general language and examples do not show a strong preference for Windows-only tools, but the ordering and emphasis may subtly prioritize Windows users.
Recommendations
- Present Linux and Windows command examples side-by-side or alternate which is shown first.
- Explicitly mention parity between Windows and Linux tools in troubleshooting and setup steps.
- Include more detailed Linux/macOS-specific guidance where appropriate, such as using 'ss', 'telnet', or other native tools.
- Where screenshots or UI steps are shown, clarify any OS-specific differences if relevant.
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Minor Rdp Bias
Summary
The documentation page generally presents APIs and tools in a cross-platform manner, but there is a slight Windows bias in the command-line tools section, where PowerShell cmdlets are listed before Azure CLI, and in the 'Other tools' section, where Remote Desktop (RDP) is mentioned for node access without reference to SSH for Linux nodes. PowerShell is a Windows-centric tool, and RDP is primarily used for Windows environments, while Linux/macOS users typically use Azure CLI and SSH. However, Azure CLI and Batch Explorer are highlighted as cross-platform, and code samples/tutorials are available for multiple languages.
Recommendations
- List Azure CLI before PowerShell in the command-line tools section to emphasize cross-platform support.
- Explicitly mention SSH as the primary method for accessing Linux compute nodes, alongside RDP for Windows nodes.
- Provide examples or links for managing Batch resources using Bash or other Linux-native shells.
- Clarify that PowerShell is available on Linux/macOS, but CLI is often preferred for those platforms.
- Ensure all troubleshooting/download instructions cover both Windows (RDP) and Linux (SSH) scenarios.
Batch
Copy applications and data to pool nodes
...ain/articles/batch/batch-applications-to-pool-nodes.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page exhibits mild Windows bias by referencing Windows-specific installation formats (e.g., .exe and .msi files) and omitting explicit Linux/macOS equivalents or examples. There are no examples of Linux package formats (like .deb, .rpm) or installation commands (such as apt, yum, or shell scripts). The mention of mapping a network share is ambiguous and could be interpreted as a Windows-centric pattern. No Linux/macOS-specific tools or workflows are described.
Recommendations
- Include examples for Linux/macOS application installation, such as using shell scripts, .deb/.rpm packages, or tarballs.
- Mention Linux/macOS equivalents when discussing .exe and .msi files (e.g., .sh, .deb, .rpm).
- Provide sample command lines for both Windows (PowerShell, .msi) and Linux/macOS (bash, apt, yum) in relevant sections.
- Clarify cross-platform approaches for mapping network shares (e.g., SMB for Windows, NFS/CIFS for Linux).
- Explicitly state that the described methods are applicable to both Windows and Linux nodes, and highlight any differences.
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias. Windows tools (cmd.exe) and Windows-style environment variable syntax (%VAR%) are consistently mentioned first in examples, with Linux equivalents provided but second. Windows-specific details (such as drive letters for mounts and environment variable naming conventions) are explained before or in more detail than Linux equivalents. There is no Powershell-specific example, but the overall pattern prioritizes Windows usage and terminology.
Recommendations
- Alternate the order of examples so that Linux and Windows are given equal prominence, or present both side-by-side.
- Provide explicit bash and shell examples for Linux/macOS users, not just /bin/sh.
- Clarify Linux-specific behaviors (such as case sensitivity and path formats) as thoroughly as Windows details.
- Where Windows-specific tools or syntax are mentioned, ensure Linux/macOS equivalents are described with equal detail.
- Include a note at the top stating that all examples apply equally to Linux and Windows, and highlight any platform-specific differences.
Batch
Choose VM sizes and images for pools
...e-docs/blob/main/articles/batch/batch-pool-vm-sizes.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation consistently lists PowerShell (a Windows-centric tool) as the first example for querying supported VM sizes and images, followed by Azure CLI and REST API. While Linux is mentioned as a supported OS and Azure CLI is cross-platform, the ordering and repeated emphasis on PowerShell may signal a subtle Windows bias. All examples use Azure CLI, which is cross-platform, but PowerShell is always listed first and referenced in tips, which may create friction for Linux/macOS users.
Recommendations
- Alternate the order of tool listings so that Azure CLI (cross-platform) is shown before PowerShell.
- Explicitly state that Azure CLI and REST API are fully supported on Linux/macOS.
- Add example commands for querying VM sizes and images using Bash or other Linux-native tools (where applicable).
- Clarify that PowerShell examples are for Windows users, and provide parity for Linux/macOS users in all code samples and tips.
Batch
Use the Azure Compute Gallery to create a custom image pool
...zure-docs/blob/main/articles/batch/batch-sig-images.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. Windows tools (PowerShell, RDP) are mentioned before or more prominently than their Linux equivalents (Azure CLI, SSH). Examples and instructions often reference Windows first, and PowerShell is listed as a primary method for discovering supported images. In some places, Linux-specific guidance is present but less emphasized, and there are no explicit Linux shell command examples for key steps (e.g., preparing a VM, mounting disks).
Recommendations
- Provide Linux shell (bash) examples alongside PowerShell for listing supported images and other key operations.
- Mention Azure CLI before or alongside PowerShell when listing tools for image discovery.
- Add explicit Linux instructions for mounting and formatting attached data disks during VM preparation.
- Ensure parity in login instructions (e.g., SSH for Linux is mentioned, but RDP for Windows is described first; consider equal prominence).
- Where purchase plan information is referenced, ensure Linux and Windows guidance is equally detailed and visible.
- Include troubleshooting or common issues for both Windows and Linux pool nodes.
Batch
Persist job and task output to a data store
...ure-docs/blob/main/articles/batch/batch-task-output.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias by providing a Windows-specific example in the 'Custom file movement solution' section and omitting equivalent Linux/macOS examples. Additionally, the only explicit example command references Windows executables, and there is no mention of Linux shell scripts or cross-platform patterns. The page does not discuss platform-specific tools or provide parity in example scripts for Linux/macOS users.
Recommendations
- Add equivalent Linux/macOS examples in the 'Custom file movement solution' section, such as using shell scripts (e.g., './doMyWork.sh && ./uploadMyFilesToSql.sh').
- Explicitly mention that custom scripts can be written for both Windows (batch, PowerShell) and Linux/macOS (bash, Python, etc.), and provide sample commands for each.
- Clarify that the Batch File Conventions standard and API approaches are platform-agnostic, and provide brief code snippets or references for non-Windows environments.
- Ensure that examples and recommendations are presented in a cross-platform manner, or alternate between Windows and Linux/macOS examples.
Batch
Provision a pool in a virtual network
...docs/blob/main/articles/batch/batch-virtual-network.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation references both Windows and Linux (e.g., mentioning SSH for Linux and RDP for Windows), but examples and instructions are generic and do not provide concrete, platform-specific guidance or commands. However, in the security rules tables and explanatory text, Windows (port 3389) is consistently mentioned before Linux (port 22), and there are no Linux-specific setup examples or CLI commands shown. There is no evidence of PowerShell-heavy bias or exclusive use of Windows tools, but the ordering and lack of Linux-specific examples indicate a mild Windows-first bias.
Recommendations
- Provide explicit Linux/macOS examples alongside Windows ones, such as Azure CLI commands for pool creation and network configuration.
- Alternate the order of mentioning Windows and Linux ports, or present them together to avoid implicit prioritization.
- Include screenshots or instructions for Linux/macOS users where portal or tool usage may differ.
- Clarify any platform-specific requirements or differences in remote access setup (e.g., SSH key configuration for Linux nodes).
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation provides both Linux and Windows examples for creating Batch pools with extensions, and lists supported extensions for both platforms. However, there is a slight Windows bias: Windows-specific extensions (e.g., Antimalware, Diagnostics, HPC GPU for AMD) are more numerous and detailed, and Windows tools/patterns (such as certificateStoreLocation: 'LocalMachine') are referenced. The troubleshooting section refers to logging into the node and checking logs, but does not specify Linux log locations or commands. The Application Health extension section is platform-neutral, but overall, Windows examples and tools are slightly more prominent.
Recommendations
- Ensure equal detail for Linux and Windows extension examples, including troubleshooting steps and log locations for Linux.
- Add explicit Linux command-line or log file references for troubleshooting (e.g., where to find Key Vault extension logs on Linux).
- Where Windows tools or concepts are mentioned (e.g., 'LocalMachine' certificate store), provide Linux equivalents or explanations.
- Balance the order of extension listings and examples so Linux is not always second.
- If possible, add more Linux-specific extension examples or highlight parity in supported features.
Batch
Create a Batch pool with specified public IP addresses
...docs/blob/main/articles/batch/create-pool-public-ip.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Summary
The documentation lists Azure PowerShell as a method for creating public IP addresses alongside Azure CLI and the Azure portal, but PowerShell is mentioned last. However, the inclusion of PowerShell as a primary method and the lack of explicit Linux/macOS shell examples (e.g., Bash) or references to platform-specific nuances may create a subtle Windows bias. No Linux-specific tools or instructions are provided, and the REST API example uses Ubuntu, which helps balance the bias somewhat.
Recommendations
- Explicitly mention that Azure CLI works cross-platform and provide Bash shell examples for Linux/macOS users.
- Clarify that PowerShell is available on Linux/macOS, or provide platform-specific instructions if differences exist.
- Add a note or section highlighting Linux/macOS usage patterns, such as using Bash scripts or native tools.
- Ensure parity in troubleshooting steps or references to platform-specific issues.
Batch
Configure managed identities in Batch pools
...ocs/blob/main/articles/batch/managed-identity-pools.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Windows (PowerShell) and Linux (Bash) examples for obtaining managed identity tokens, but the Windows/PowerShell example is presented first. There is a slight preference for Windows tools and ordering, but Linux parity is generally maintained throughout the page. No critical functionality is missing for Linux/macOS users.
Recommendations
- Present Linux and Windows examples side-by-side or alternate which is shown first to avoid implicit prioritization.
- Explicitly mention that all steps and APIs are cross-platform unless there are exceptions.
- Where possible, include CLI examples (Azure CLI) for pool creation and configuration, as these are platform-neutral.
- Add a note clarifying that the .NET SDK and Azure portal are available on all major platforms.
Batch
Configure node endpoints in Azure Batch pool
...lob/main/articles/batch/pool-endpoint-configuration.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation alternates between Windows (RDP) and Linux (SSH) examples, but consistently presents Windows/RDP examples first and uses C# for Windows pools and Python for Linux pools. There is a slight bias in ordering and language/tool choice, but both platforms are covered with equivalent detail.
Recommendations
- Alternate the order of examples so that Linux/SSH is presented first in some sections.
- Provide both C# and Python code samples for each scenario (RDP and SSH), or clarify that the language choice is not platform-dependent.
- Explicitly mention parity between Windows and Linux pools in introductory sections.
- Include a summary table comparing RDP/SSH configuration steps for both platforms.
Batch
Manage private endpoint connections with Azure Batch accounts
.../articles/batch/manage-private-endpoint-connections.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for managing private endpoint connections. However, PowerShell examples are presented before CLI examples, and the PowerShell module is highlighted with a direct link, which may subtly prioritize Windows users. There is no explicit mention of Linux/macOS compatibility for PowerShell, nor are there Bash-specific notes or Linux/macOS screenshots.
Recommendations
- Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and more commonly used on Linux/macOS.
- Explicitly state that Azure CLI commands work on Windows, Linux, and macOS.
- Add notes or links about using PowerShell Core on Linux/macOS if PowerShell is mentioned.
- Include Linux/macOS-specific screenshots or terminal prompts where appropriate.
- Clarify that all operations can be performed equally on non-Windows platforms using Azure CLI.