Azure Arc
465
Total Pages
253
Linux-Friendly Pages
212
Pages with Bias
45.6%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
2334 issues found
Showing 1601-1625 of 2334 flagged pages
Azure Arc
Simplify Network Configuration Requirements with Azure Arc Gateway
...cs/blob/main/articles/azure-arc/servers/arc-gateway.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Minor Windows Tools
Summary
The documentation provides examples for Azure portal, Azure CLI, and Azure PowerShell throughout, with PowerShell examples often shown alongside CLI and portal instructions. Windows-specific paths and tools (e.g., PowerShell, Windows log file locations) are mentioned, but Linux equivalents are also provided. In some sections, Windows log file locations are listed first. There is minor bias in the order and prominence of Windows examples, but Linux parity is generally maintained.
Recommendations
- Ensure Linux and macOS examples are given equal prominence and ordering alongside Windows/PowerShell examples.
- Where file paths or log locations are mentioned, alternate between Windows and Linux order, or list Linux first in some cases.
- Explicitly mention that Azure CLI commands work cross-platform, and clarify any OS-specific prerequisites.
- Add notes for macOS users where relevant (e.g., file paths, script execution).
Create Pull Request
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples for every step, ensuring parity between Linux/macOS and Windows users. However, PowerShell examples are consistently presented after Bash examples, which may indicate a minor 'windows_first' bias in ordering. No Windows-specific tools or patterns are used exclusively, and all commands are cross-platform (using Azure CLI and Helm).
Recommendations
- Maintain the current parity of examples for both Bash and PowerShell.
- Consider alternating the order of Bash and PowerShell tabs in future documentation to avoid perceived bias.
- Explicitly mention that all commands are cross-platform and can be run on Linux, macOS, or Windows, to reassure users.
- If possible, add a note clarifying that Azure CLI and Helm are available on all major platforms.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides installation links for client tools across Windows, Linux, and macOS, but Windows links are often listed first. There is a specific note about using cmd.exe on Windows 10 instead of PowerShell for curl, and a mention that curl in PowerShell is an alias for Invoke-WebRequest, but no equivalent Linux/macOS shell guidance. The Linux installation for curl is referenced generically ('install curl package') without a link or command, and there are no explicit Linux/macOS shell examples or troubleshooting tips.
Recommendations
- List installation links for Linux/macOS before or alongside Windows, rather than Windows first.
- Provide explicit Linux/macOS installation instructions for curl (e.g., 'sudo apt install curl', 'brew install curl').
- Add shell-specific guidance for Linux/macOS users, similar to the PowerShell/cmd.exe notes for Windows.
- Include troubleshooting tips or version checks for Linux/macOS environments as well as Windows.
- Ensure parity in detail and clarity for Linux/macOS instructions compared to Windows.
Azure Arc
Connect to SQL Managed Instance enabled by Azure Arc
...in/articles/azure-arc/data/connect-managed-instance.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation references SQL Server Management Studio (SSMS) as the primary GUI client, which is Windows-only, and mentions it before sqlcmd (which is cross-platform). However, the command-line example for connecting uses sqlcmd and explicitly notes Linux compatibility. No Linux-specific tools (like Azure Data Studio or other SQL clients) are mentioned, and SSMS is referenced first throughout. There are no PowerShell-specific commands, but the focus on SSMS as the main GUI tool creates a mild Windows bias.
Recommendations
- Mention Azure Data Studio as a cross-platform GUI alternative to SSMS for connecting to SQL Managed Instance.
- Provide example connection instructions for Azure Data Studio or other popular Linux/macOS SQL clients.
- List sqlcmd as the first example, or clarify that it works on both Linux and Windows.
- Add a note that SSMS is Windows-only and suggest alternatives for Linux/macOS users.
Azure Arc
Rotate user-provided TLS certificate in indirectly connected SQL Managed Instance enabled by Azure Arc
...articles/azure-arc/data/rotate-user-tls-certificate.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation provides both Linux and Windows approaches for base64 encoding files, but the Windows method (certutil) is described in detail and includes additional steps and commands, while the Linux method is presented as a single command without further explanation. The Windows example is given immediately after the Linux command, and the Windows-specific tool (certutil) is mentioned with a link to Microsoft documentation. There are no PowerShell-heavy examples, and the rest of the guide uses cross-platform tools (openssl, Azure CLI, kubectl). However, the Windows encoding workflow is more verbose and prominent, while Linux users are given minimal guidance.
Recommendations
- Expand the Linux base64 encoding section to include decoding instructions and handling output, similar to the Windows example.
- Provide parity in guidance for Linux users, such as how to remove headers from base64 output if needed.
- Consider mentioning macOS explicitly where Linux is referenced, as the commands are likely compatible.
- Clarify that the base64 command is available on most Unix-like systems and provide troubleshooting tips for installation if missing.
Azure Arc
Simplify network configuration requirements with Azure Arc gateway
...zure-arc/kubernetes/arc-gateway-simplify-networking.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all critical steps, but consistently presents Azure PowerShell (a Windows-centric tool) alongside Azure CLI. In some sections, PowerShell examples are given equal prominence to CLI, and environment variable examples for proxy configuration are shown in both Bash (Linux/macOS) and PowerShell syntax. However, there are no Linux-specific command-line examples (e.g., Bash scripts), and PowerShell is not natively available on most Linux systems. The documentation does not mention Linux tools or patterns (such as systemd, iptables, or Linux-specific networking commands), nor does it reference macOS. Azure CLI is cross-platform, but PowerShell is presented as an alternative throughout, which may create friction for Linux/macOS users unfamiliar with PowerShell.
Recommendations
- Clearly indicate that Azure CLI is the recommended and cross-platform method for Linux/macOS users, and that PowerShell is optional for Windows users.
- Present Azure CLI examples first in each section, followed by PowerShell as an alternative for Windows users.
- Add explicit notes clarifying that Azure PowerShell commands require PowerShell Core on Linux/macOS, and provide installation links if relevant.
- Include Bash script examples or references for common tasks, especially for onboarding and proxy configuration.
- Mention Linux/macOS compatibility in prerequisites and tool installation steps.
Azure Arc
CLI reference for `azcmagent connect`
...b/main/articles/azure-arc/servers/azcmagent-connect.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation for `azcmagent connect` shows minor Windows bias. Windows authentication options are described first, and Windows certificate store usage is detailed before Linux equivalents. The access token example references a PowerShell cmdlet (`Get-AzAccessToken`) without mentioning Linux alternatives. However, Linux authentication methods (device code, Azure CLI) are well covered, and most examples are cross-platform.
Recommendations
- Reorder authentication options so Linux-default methods (device code, Azure CLI) are described before Windows-only methods.
- When referencing access token acquisition, include Linux/macOS methods (e.g., Azure CLI: `az account get-access-token`) alongside PowerShell.
- Clarify certificate handling for Linux (e.g., typical file locations, permissions) in the certificate authentication section.
- Add explicit Linux/macOS example commands where appropriate, especially for authentication and certificate usage.
Azure Arc
Customer intent: "As a network administrator, I want to configure outbound and inbound connectivity settings for the appliance VM and management machine, so that I can ensure smooth communication and functionality for the Arc resource bridge."
...e-arc/resource-bridge/includes/network-requirements.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation includes references to Windows-specific services (e.g., 'time.windows.com' as the NTP server, 'servicebus.windows.net', 'sts.windows.net', 'login.windows.net') and Windows terminology, but also covers Linux-related endpoints (e.g., 'linuxgeneva-microsoft.azurecr.io', 'packages.microsoft.com'). Windows NTP is mentioned explicitly, and Windows endpoints appear before Linux ones in some lists. However, the documentation does not provide OS-specific command examples or configuration steps, and both Linux and Windows endpoints/tools are referenced.
Recommendations
- Clarify that NTP can be configured with Linux NTP servers as well, not just 'time.windows.com'.
- Where Windows-specific endpoints are mentioned (e.g., 'servicebus.windows.net', 'sts.windows.net'), note if Linux equivalents exist or if these are cross-platform.
- Ensure that Linux-related endpoints and tools are given equal prominence and explanation.
- Add explicit notes or examples for Linux users where relevant (e.g., how to configure outbound connectivity for Linux management machines).
Azure Arc
Customer intent: "As a network administrator, I want to configure secure outbound connectivity for the Azure Connected Machine agent so that I can ensure proper communication with Azure Arc while adhering to my organization's security policies."
...les/azure-arc/servers/includes/network-requirements.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation covers both Linux and Windows platforms for the Azure Connected Machine agent, with clear mention of Linux-specific installation sources and TLS requirements. However, there is a mild Windows bias: Windows installation/package URLs are consistently listed before Linux equivalents, and Windows Admin Center is referenced as a management tool without mention of Linux alternatives. Additionally, troubleshooting and cipher suite configuration links are Windows-specific, while Linux guidance is more generic (referencing OpenSSL).
Recommendations
- List Linux and Windows installation package URLs in parallel or alternate order to avoid Windows-first bias.
- Include references to Linux management tools or clarify that Windows Admin Center is Windows-only.
- Provide Linux-specific troubleshooting links or guidance for TLS configuration (e.g., OpenSSL settings, common Linux issues).
- Expand Linux guidance beyond generic OpenSSL references, such as mentioning how to verify TLS settings or cipher suites on common distributions.
Azure Arc
Automatic extension upgrade for Azure Arc-enabled servers
...e-arc/servers/manage-automatic-vm-extension-upgrade.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation covers both Windows and Linux Azure Arc-enabled servers, and provides parity in most sections. However, there is a minor bias in the order of examples: Azure PowerShell is presented after Azure CLI, but PowerShell is referenced heavily and installation instructions are only given for PowerShell (not for Bash or Linux shells). In the 'Manage automatic extension upgrade' section, Azure CLI is described as cross-platform, but PowerShell is presented as a separate tab, which may subtly prioritize Windows users. No critical Linux functionality is missing, and all CLI commands are cross-platform.
Recommendations
- Add explicit instructions for installing Azure CLI on Linux/macOS, similar to the PowerShell module installation tip.
- Clarify that Azure PowerShell can be used on Linux/macOS as well, or link to installation instructions for those platforms.
- Consider mentioning Bash/zsh usage in the PowerShell section, or provide parity tips for Linux users.
- Ensure screenshots and portal navigation are not Windows-centric (current screenshots are neutral).
Azure Arc
VM Extension Management with Azure Arc-Enabled Servers
...ain/articles/azure-arc/servers/manage-vm-extensions.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides parity between Windows and Linux VM extensions, with dedicated tables for each OS. However, Windows extensions are presented first, which may subtly prioritize Windows users. All deployment methods (Azure CLI, PowerShell, portal, templates) are mentioned equally, and partner extensions are shown for both OSes. No critical Linux examples or tools are missing.
Recommendations
- Consider alternating the order of Windows and Linux extension tables, or presenting them side-by-side to reinforce parity.
- Explicitly state that all deployment methods (CLI, PowerShell, portal, templates) are available for both Windows and Linux extensions.
- Add a brief introductory note emphasizing equal support for Windows and Linux Arc-enabled servers.
- Ensure linked deployment guides for CLI and PowerShell include both Windows and Linux examples.
Azure Arc
Access Azure resources with managed identity on Azure Arc-enabled servers
...s/azure-arc/servers/managed-identity-authentication.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Windows (PowerShell) and Linux (Bash) examples for acquiring access tokens using managed identity on Azure Arc-enabled servers. However, the Windows/PowerShell example is presented first, and the PowerShell script is more detailed and visually emphasized (with a screenshot). The Linux/Bash example follows and is also accompanied by a screenshot. The prerequisites and guidance are generally balanced, mentioning both Windows and Linux requirements and linking to platform-specific tutorials. The 'Related content' section lists PowerShell before Azure CLI, which may subtly reinforce Windows-first patterns.
Recommendations
- Present Windows and Linux examples side-by-side, or alternate which platform is shown first to avoid implicit prioritization.
- Ensure equal detail and visual emphasis for both Windows and Linux examples (e.g., screenshots, code comments).
- In 'Related content', list Azure CLI and PowerShell together or alternate their order to avoid Windows-first bias.
- Consider adding a brief note at the start clarifying that both Windows and Linux are fully supported and that examples for both are provided.
Azure Arc
Troubleshoot Azure Connected Machine agent connection issues
...ticles/azure-arc/servers/troubleshoot-agent-onboard.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation provides troubleshooting guidance for both Windows and Linux, with clear parity in error/exit code tables and log file locations. However, in the 'Agent verbose log' section, Windows examples are presented first and use PowerShell syntax, while Linux examples follow. Windows-specific log paths and tools (e.g., PowerShell, Windows environment variables) are mentioned before Linux equivalents. There is minor bias in ordering and tool emphasis, but Linux users are not blocked from completing any task.
Recommendations
- Alternate the order of Windows and Linux examples in sections to avoid implicit prioritization.
- Where possible, provide cross-platform command syntax side-by-side for clarity.
- Ensure Linux log paths and troubleshooting steps are equally prominent and detailed.
- Add explicit notes that all troubleshooting steps apply to both Windows and Linux unless otherwise stated.
Azure Arc
What is Azure Arc-enabled VMware vSphere?
...lob/main/articles/azure-arc/vmware-vsphere/overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides a balanced overview of Azure Arc-enabled VMware vSphere, mentioning both Windows and Linux support in several places. However, there are subtle signs of Windows bias: Windows-related features (such as Windows Server management and Extended Security Updates) are highlighted first in benefit lists, and PowerShell is mentioned before other automation tools in the context of Azure Automation. Some links and examples reference Windows-specific tabs or features before Linux equivalents, even though Linux is supported.
Recommendations
- Ensure Linux examples and references are presented alongside Windows examples, not after or as an afterthought.
- When listing automation tools, mention Bash or Linux shell scripting equally with PowerShell.
- Where links point to Windows-specific documentation (e.g., tabs=windows), also provide links or tabs for Linux guidance.
- In benefit lists, clarify which features are Windows-only and which apply to Linux, to avoid confusion.
- Consider adding explicit Linux-focused scenarios or examples to highlight parity.
Azure Arc
Connect VMware vCenter Server to Azure Arc by using the helper script
...ere/quick-start-connect-vcenter-to-arc-using-script.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Windows (PowerShell) and Linux (Bash) examples for running the onboarding script, but Windows instructions and PowerShell notes are presented first and in greater detail. Windows-specific issues (e.g., PowerShell ISE limitations, Set-ExecutionPolicy) are discussed, while Linux instructions are more concise. The retry command section also presents Windows first. However, Linux parity is generally maintained, and both platforms are supported.
Recommendations
- Present Windows and Linux instructions in parallel or alternate their order to avoid Windows-first bias.
- Add troubleshooting notes for Linux (e.g., common Bash issues, permission requirements) similar to the PowerShell ISE note for Windows.
- Ensure that screenshots and UI references are platform-neutral or clarify if any steps differ for Linux users.
- Consider a table or tabbed layout for OS-specific instructions to improve clarity and parity.
Azure Arc
Delete Resources in Workload Orchestration
...s/azure-arc/workload-orchestration/delete-resources.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples for all CLI commands, but consistently presents Bash examples first. There are no Windows-specific tools or patterns, and Linux parity is maintained throughout. No critical sections are Windows-only, and all tasks can be completed on Linux/macOS using the Azure CLI.
Recommendations
- Continue to provide both Bash and PowerShell examples for cross-platform parity.
- Consider clarifying that Bash examples are suitable for Linux/macOS and PowerShell for Windows, to help users quickly identify their relevant section.
- If possible, add a brief note at the top indicating that all commands are cross-platform via Azure CLI.
Azure Arc
External Validation for Workload Orchestration
...zure-arc/workload-orchestration/external-validation.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples for all CLI operations, ensuring parity for Linux/macOS and Windows users. However, in several sections, PowerShell examples are presented immediately after Bash, rather than alternating or giving equal prominence. There are no Windows-specific tools or patterns, and all instructions are based on the Azure CLI, which is cross-platform. No Linux/macOS examples are missing, and no Windows-only tools are referenced.
Recommendations
- Consider alternating the order of Bash and PowerShell examples to avoid implicit prioritization.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows to reinforce cross-platform support.
- If possible, provide a brief note about using Azure CLI in different environments (e.g., Bash on Linux/macOS, PowerShell on Windows) for clarity.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples for all commands, but the Bash tab is presented first. There are no Windows-specific tools, patterns, or exclusive examples; all instructions use the Azure CLI, which is cross-platform. No Linux examples are missing, and Linux users can follow the Bash instructions without friction.
Recommendations
- Continue to provide both Bash and PowerShell examples for parity.
- Consider alternating the order of Bash and PowerShell tabs or clarifying that Bash is suitable for Linux/macOS and PowerShell for Windows.
- Explicitly state that Azure CLI commands work on all platforms to reassure users.
Azure Arc
Create a Solution with Multiple Dependencies with Workload Orchestration
...quickstart-solution-multiple-shared-adapter-dependency.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples for every CLI operation, ensuring parity for Linux/macOS and Windows users. However, PowerShell examples are consistently shown immediately after Bash, and in some cases, variable syntax in PowerShell is shown with Windows-style conventions. There are no Windows-only tools or patterns, and all commands are cross-platform (Azure CLI, kubectl). No Linux example is missing, and no Windows-specific tools are mentioned.
Recommendations
- Maintain Bash examples as the default or first tab, as currently done.
- Consider clarifying that Azure CLI and kubectl commands are cross-platform and can be run on Linux, macOS, or Windows.
- Add a brief note at the top indicating that both Bash and PowerShell are supported, and users should select the tab matching their environment.
- Ensure that all variable names and file paths are generic and not Windows-specific (e.g., avoid backslashes or Windows drive letters).
Azure Arc
Solution with Multiple Shared Dependencies at Different Hierarchy Levels
...oad-orchestration/tutorial-service-group-scenario-3.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Bash and PowerShell examples for every step, ensuring parity for Linux/macOS and Windows users. However, PowerShell examples are present throughout and sometimes shown immediately after Bash, which may be interpreted as a mild Windows bias. There are no Windows-only tools or patterns; all commands use the Azure CLI and Helm, which are cross-platform. Bash examples are consistently provided first, and there are no missing Linux examples or exclusive Windows tools.
Recommendations
- Maintain Bash examples as the primary tab and ensure Bash is shown first for all code blocks.
- Clarify in the introduction that all steps are cross-platform and that PowerShell is provided for Windows users.
- Consider adding a note that Azure CLI and Helm commands are identical across platforms, except for shell syntax.
- Ensure that any future additions do not introduce Windows-only tools or patterns unless the feature is Windows-specific.
Azure Arc
Connect to SQL Managed Instance enabled by Azure Arc
...in/articles/azure-arc/data/connect-managed-instance.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation mentions SQL Server Management Studio (SSMS) as the primary GUI client, which is Windows-only, and lists it before sqlcmd (which is cross-platform). However, it does provide a sqlcmd example for both Linux and Windows, and does not rely on Windows-only tools or PowerShell. The overall guidance is mostly platform-neutral, but the ordering and emphasis on SSMS may create minor bias.
Recommendations
- Explicitly mention cross-platform GUI clients (such as Azure Data Studio) alongside SSMS.
- Provide example connection instructions for Azure Data Studio or other Linux/macOS-compatible tools.
- Clarify that sqlcmd works on Linux, macOS, and Windows, and show examples for each platform if there are differences.
- Consider listing cross-platform tools first, or at least equally with Windows-only tools.
Azure Arc
VM Extension Management with Azure Arc-Enabled Servers
...ain/articles/azure-arc/servers/manage-vm-extensions.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides parity between Windows and Linux VM extensions, with dedicated tables for each OS and clear links to usage and supported OS information. However, Windows extensions are presented first, which may subtly reinforce a Windows-centric perspective. All deployment methods (Azure CLI, PowerShell, portal, ARM templates) are mentioned together, and partner extensions are shown for both OSes. No critical Linux gaps or missing examples are evident.
Recommendations
- Consider alternating the order of Windows and Linux extension tables, or presenting them side-by-side if possible, to avoid implicit Windows-first bias.
- Explicitly state that all deployment methods (CLI, PowerShell, portal, templates) are available for both Windows and Linux extensions.
- Where possible, provide example links or code snippets for both Windows and Linux in deployment guides (if not already present in linked pages).
Azure Arc
Delete Resources in Workload Orchestration
...s/azure-arc/workload-orchestration/delete-resources.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples for each command, but consistently presents Bash examples first. There are no Windows-specific tools or patterns, and all commands use the cross-platform Azure CLI. No Linux examples are missing, and Linux parity is maintained throughout.
Recommendations
- Maintain Bash examples first, as Bash is the default shell on Linux and macOS.
- Ensure that PowerShell examples are clearly marked as cross-platform (PowerShell Core), if applicable.
- Consider adding a brief note clarifying that Azure CLI commands work on Windows, Linux, and macOS, and that Bash examples are suitable for Linux/macOS users.
Azure Arc
Multiple Solutions with a Single Shared Dependency at Different Levels
...oad-orchestration/tutorial-service-group-scenario-4.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples for every step, but PowerShell examples are consistently shown after Bash. There are no Windows-only tools or patterns, and Linux parity is maintained throughout. The Azure CLI and Helm are cross-platform tools, and no Windows-specific instructions or tools are prioritized. However, the ordering of Bash before PowerShell may be considered a minor bias toward Linux/Unix environments.
Recommendations
- Consider alternating the order of Bash and PowerShell tabs, or explicitly state that both are supported equally.
- Add a note clarifying that all commands are cross-platform and that users should select the tab matching their environment.
- Ensure that any future examples or troubleshooting steps include both Bash and PowerShell variants.
Azure Arc
Release Notes for Workload Orchestration
...cles/azure-arc/workload-orchestration/release-notes.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides CLI examples primarily using Bash syntax, which is cross-platform, but in the May 2025 release, PowerShell syntax is used for CLI examples. There are no Windows-specific tools or patterns mentioned, and the Azure CLI is inherently cross-platform. However, the use of PowerShell syntax in the examples may create minor friction for Linux/macOS users, as Bash is more common on those platforms.
Recommendations
- Provide CLI examples in both Bash and PowerShell syntax, or default to Bash for cross-platform parity.
- Explicitly state that Azure CLI commands work on all platforms and provide guidance for Linux/macOS users if syntax differs.
- Avoid using platform-specific shell syntax unless the feature is Windows-only.