Azure Arc
926
Total Pages
755
Linux-Friendly Pages
171
Pages with Bias
18.5%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
432 issues found
Showing 351-375 of 432 flagged pages
Azure Arc
Create a Basic Solution with Workload Orchestration
...on/quickstart-solution-without-common-configuration.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for every step, but consistently lists Bash examples before PowerShell. There is no evidence of exclusive use of Windows tools or missing Linux examples; all CLI commands are cross-platform (Azure CLI). However, the PowerShell examples are given equal detail and prominence, which may slightly favor Windows users, especially as PowerShell is more common on Windows. No Windows-specific tools or patterns are mentioned, and Linux/macOS users can follow all steps without friction.
Recommendations
- Explicitly mention that all CLI commands work on Linux, macOS, and Windows.
- Add a note clarifying that Bash examples are for Linux/macOS and PowerShell for Windows, and that Azure CLI is cross-platform.
- Consider including a short section on running PowerShell on Linux/macOS, or link to relevant documentation.
- Ensure that any future troubleshooting or advanced sections do not introduce Windows-only tools or patterns.
Create Pull Request
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
Windows First
Powershell Heavy
Summary
The documentation consistently presents both Bash and PowerShell examples for all command-line steps, but PowerShell examples are always shown after Bash. There is no evidence of exclusive Windows tools or missing Linux examples; all commands use the cross-platform Azure CLI and Helm. However, the presence of PowerShell examples throughout and their explicit inclusion may suggest a slight Windows bias, especially for users who expect Linux/macOS parity.
Recommendations
- Explicitly state that all commands are cross-platform and that Bash examples work on Linux/macOS and Windows (via WSL or Git Bash).
- Consider including a note at the top clarifying that PowerShell examples are for Windows users, while Bash is for Linux/macOS (and also available on Windows).
- If possible, provide guidance for macOS users regarding prerequisites (e.g., installation of Azure CLI and Helm).
- Ensure that any file path examples use forward slashes for Bash and backslashes for PowerShell, and clarify differences if relevant.
- If the audience is primarily cross-platform, consider alternating the order of Bash and PowerShell tabs in different sections.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for all command-line steps, but PowerShell examples are consistently shown after Bash. There is no evidence of exclusive Windows tools or patterns, nor are there missing Linux examples. The use of PowerShell tabs and examples throughout the document indicates a notable Windows focus, but Linux parity is maintained via Bash examples.
Recommendations
- Consider alternating the order of Bash and PowerShell tabs in different sections to avoid implicit prioritization.
- Add a brief note at the top clarifying that all commands are cross-platform and that Bash examples apply to Linux/macOS and PowerShell to Windows.
- Explicitly mention that the Azure CLI and Helm commands work identically on Linux, macOS, and Windows, and highlight any platform-specific caveats if they exist.
- If possible, add a short section on running these commands in WSL or macOS Terminal for completeness.
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
Powershell Heavy
Windows First
Summary
The documentation provides both Bash and PowerShell examples for all command-line steps, ensuring Linux and Windows users are supported. However, PowerShell examples are present throughout, and in some sections (such as solution template creation), PowerShell code is shown immediately after Bash, which may suggest a slight Windows-first ordering. There are no Windows-only tools or patterns, and Linux parity is maintained via Bash examples. No Linux/macOS examples are missing, and all tooling is cross-platform (az CLI, Helm).
Recommendations
- Ensure Bash examples are always shown first, as Bash is the default shell for most Linux/macOS users.
- Explicitly mention that all commands are supported on Linux/macOS and Windows, and clarify any platform-specific nuances if present.
- Consider adding a note at the top stating that az CLI and Helm are cross-platform and that both Bash and PowerShell examples are provided for user convenience.
- If possible, add a macOS-specific note or example for any steps that might differ on macOS (none detected here, but good practice).
Azure Arc
Azure Arc-enabled data services - Automated validation testing
...ticles/azure-arc/data/automated-integration-testing.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation displays mild Windows bias, primarily in the order and emphasis of tooling and examples. Windows-specific issues (CRLF line endings) are highlighted with screenshots of VSCode on Windows, and Azure CLI examples are shown in PowerShell terminals. The process for generating environment files is described as identical across OSes, but troubleshooting and visuals focus on Windows. There is no explicit Linux/macOS example or troubleshooting, and Windows tools (VSCode, PowerShell) are mentioned before alternatives.
Recommendations
- Add explicit Linux/macOS troubleshooting steps for line endings (e.g., using 'dos2unix' or 'sed').
- Include screenshots or terminal examples from Linux/macOS environments alongside Windows.
- Clarify that Azure CLI and kubectl commands are cross-platform, and show examples in bash/zsh as well as PowerShell.
- Mention alternative editors for Linux/macOS when discussing line ending conversions.
- Ensure that any OS-specific issues (like CRLF/LF) are explained for all platforms, not just Windows.
Azure Arc
Connect to AD-integrated SQL Managed Instance enabled by Azure Arc
.../data/connect-active-directory-sql-managed-instance.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias. Windows-based tools (SSMS, ADS) are mentioned and illustrated, and the Windows connection example is presented before the Linux/Mac OS example. The Linux section is present and functional, but lacks parity in graphical tool instructions and screenshots.
Recommendations
- Add screenshots or step-by-step instructions for connecting from Azure Data Studio (ADS) on Linux/macOS.
- Clarify that ADS is cross-platform and provide explicit Linux/macOS usage notes.
- Present Linux/Mac OS examples before or alongside Windows examples to avoid ordering bias.
- Mention alternative Linux-native SQL clients if relevant.
- Ensure parity in troubleshooting steps for both platforms.
Azure Arc
Encrypt a database with transparent data encryption manually in SQL Managed Instance enabled by Azure Arc
...data/configure-transparent-data-encryption-manually.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation provides both Windows and Linux examples for key operations, but Windows examples are consistently shown first in each step. Windows-specific tools and patterns (e.g., 'type' command, Windows path syntax) are used, and there are multiple notes about Windows-specific issues (e.g., kubectl cp path problems). There is a slight emphasis on Windows workflows, but Linux parity is maintained with equivalent commands and examples.
Recommendations
- Alternate the order of Windows and Linux examples, or present Linux examples first in some sections.
- Add more explicit notes for Linux/macOS users where relevant, not just Windows-specific caveats.
- Where possible, use cross-platform commands or highlight platform-agnostic approaches.
- Consider grouping platform-specific instructions together, rather than interleaving them, to reduce perceived bias.
- Clarify that both Windows and Linux/macOS are fully supported and tested for these operations.
Azure Arc
Turn on transparent data encryption in SQL Managed Instance enabled by Azure Arc (preview)
...igure-transparent-data-encryption-sql-managed-instance.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Path Notes
Summary
The documentation provides both Windows and Linux examples for file operations (copying certificates and keys), but Windows examples are consistently shown first. There are explicit notes about Windows path issues, and Windows-specific commands (e.g., 'type' for file concatenation) are included. However, Linux parity is maintained with equivalent examples and instructions for both platforms.
Recommendations
- Alternate the order of Windows and Linux examples, or present them side-by-side to avoid implicit prioritization.
- Add a brief statement at the start of relevant sections clarifying that both Windows and Linux are equally supported.
- Where possible, use platform-neutral commands or highlight cross-platform tools (e.g., PowerShell Core, WSL) for Windows users.
- Ensure all notes about platform-specific issues (such as path handling) are balanced with Linux/macOS caveats if any exist.
Azure Arc
Connectivity modes and requirements
...docs/blob/main/articles/azure-arc/data/connectivity.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation generally avoids explicit Windows-only tools, but there is a subtle bias in listing Azure CLI and Azure portal as primary management options, which are more familiar to Windows users. Linux-native tools (kubectl, Helm, oc) are mentioned, but often as secondary options or grouped together. No explicit Linux/Powershell examples are given, and there is no mention of Linux-specific patterns or shell commands. The documentation does not provide platform-specific guidance or parity in examples, which may create friction for Linux/macOS users.
Recommendations
- Provide explicit Linux/macOS command-line examples alongside Azure CLI and portal instructions.
- Clarify that Azure CLI, Azure Data Studio, and Kubernetes tools are cross-platform and provide installation links for Linux/macOS.
- List Linux-native tools (kubectl, Helm, oc) first or equally when describing provisioning and management options.
- Include examples or workflows using bash/zsh and Linux package managers where relevant.
- Add a section on platform compatibility for all mentioned tools.
Azure Arc
Prerequisites | Direct connect mode
...rc/data/create-data-controller-direct-prerequisites.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for connecting a Kubernetes cluster to Azure Arc, but lists PowerShell as a primary alternative to CLI, with no mention of Linux/macOS shell equivalents (e.g., Bash). The PowerShell example is given equal prominence to CLI, which may create friction for Linux/macOS users unfamiliar with PowerShell. There are no Windows-only tools, but the presence and parity of PowerShell examples suggest a mild Windows bias.
Recommendations
- Clarify that Azure CLI commands work on Linux, macOS, and Windows, while PowerShell is primarily for Windows users.
- Consider listing CLI (Bash/shell) examples first, as they are cross-platform.
- Add explicit notes or examples for Linux/macOS users, confirming that all steps can be performed in Bash or other shells.
- If PowerShell is not required for Linux/macOS, de-emphasize its use or move it to a separate section for Windows users.
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
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias by prioritizing Windows-centric tools (SQL Server Management Studio) and mentioning them before Linux alternatives. While Azure Data Studio and SQLCMD are cross-platform, the examples and instructions reference Windows tools first and do not provide explicit Linux/macOS-specific guidance (e.g., package installation, command-line nuances, or alternative client tools). There are no PowerShell-only instructions, but the lack of Linux/macOS-specific connection examples and troubleshooting steps may create friction for non-Windows users.
Recommendations
- Explicitly mention and provide examples for connecting from Linux/macOS clients, including installation instructions for SQLCMD and Azure Data Studio on those platforms.
- List cross-platform tools (Azure Data Studio, SQLCMD) before Windows-only tools (SQL Server Management Studio) to avoid Windows-first bias.
- Include troubleshooting steps or notes relevant to Linux/macOS environments, such as firewall configuration or network tool usage.
- Add examples using native Linux/macOS tools (e.g., isql, DBeaver, or unixODBC) where appropriate.
Azure Arc
Deploy a new SQL Managed Instance enabled by Azure Arc using Kubernetes tools
...ate-sql-managed-instance-using-kubernetes-native-tools.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation displays mild Windows bias by presenting PowerShell as the first CLI example for base64 encoding credentials, followed by Linux/macOS. Additionally, the example file path for 'kubectl create' uses Windows-style paths (C:\arc-data-services\sqlmi.yaml) without showing a Linux/macOS equivalent. However, most instructions are cross-platform and focus on Kubernetes-native tools.
Recommendations
- Present Linux/macOS and Windows CLI examples side-by-side, or alternate which is shown first.
- Include Linux/macOS file path examples (e.g., /home/user/arc-data-services/sqlmi.yaml) alongside Windows paths.
- Clarify that all commands work on any OS with kubectl installed, and provide explicit notes where platform differences exist.
- Consider mentioning Linux-native editors (e.g., nano, vim) in addition to VS Code.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. Installation links for tools like kubectl and curl list Windows first, and explanations reference Windows-specific behaviors (e.g., using cmd.exe instead of PowerShell, PowerShell's curl alias). Linux installation instructions are less detailed or are mentioned second. There is no explicit Linux command-line example for checking tool versions or installing tools, and Windows-specific caveats are highlighted without Linux/macOS equivalents.
Recommendations
- Present installation options for all platforms (Windows, Linux, macOS) in parallel or alphabetical order, rather than listing Windows first.
- Include Linux/macOS-specific notes and caveats where relevant, not just Windows/PowerShell ones.
- Provide explicit Linux/macOS command-line examples for checking versions and installing tools (e.g., 'az --version', 'curl --version', installation via apt/yum/brew).
- Clarify that PowerShell's curl alias is a Windows-specific issue and provide Linux/macOS alternatives or warnings if needed.
- Ensure all critical instructions (such as running curl commands) are equally clear for Linux/macOS users.
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
Summary
The documentation provides both Windows (PowerShell) and Linux (Bash) examples for running the onboarding script, but Windows instructions and examples are consistently presented before Linux equivalents. There is a minor bias in ordering, but Linux users are given full parity in instructions and tooling.
Recommendations
- Alternate the order of Windows and Linux instructions in sections, or present them side-by-side to avoid implicit prioritization.
- Explicitly mention macOS compatibility if the Bash script works on macOS, or clarify any limitations.
- Ensure screenshots and UI references do not assume a Windows environment unless necessary.
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
Windows First
Summary
The documentation page is generally cross-platform, with most examples using OpenSSL, Azure CLI, and kubectl, which are available on Linux, macOS, and Windows. However, in the section on base64 encoding, the Linux command is presented first, but Windows users are directed to use certutil, a Windows-specific tool, with additional manual steps and Windows command-line syntax. No PowerShell examples are given, but the only OS-specific tool mentioned is for Windows, and it is described after the Linux method.
Recommendations
- Provide PowerShell examples for base64 encoding on Windows, as PowerShell is available on both Windows and Linux.
- Mention cross-platform alternatives to certutil, such as using OpenSSL or PowerShell's [Convert]::ToBase64String(), to avoid reliance on Windows-only tools.
- Clarify that the Azure CLI and kubectl commands work identically on Linux, macOS, and Windows.
- Consider listing both Linux and Windows methods side-by-side for encoding, rather than presenting Linux first and Windows as an afterthought.
Azure Arc
Get logs to troubleshoot Azure Arc-enabled data services
...in/articles/azure-arc/data/troubleshooting-get-logs.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides CLI commands that are cross-platform, but the only explicit example of a target folder uses a Windows-style path (C:\temp\logs), and there are no Linux/macOS path examples. This may cause confusion for non-Windows users and suggests a subtle Windows-first bias.
Recommendations
- Include Linux/macOS path examples (e.g., /tmp/logs) alongside Windows paths when showing command usage.
- Add a note clarifying that the az CLI and arcdata extension work on Linux/macOS as well as Windows.
- Consider alternating the order of examples or providing OS-specific tabs for commands where file paths differ.
Azure Arc
Upload usage data, metrics, and logs to Azure
...e-arc/data/upload-metrics-and-logs-to-azure-monitor.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Windows and Linux/macOS examples for environment variable setting and role assignment, but Windows examples (including PowerShell) are consistently presented first. PowerShell-specific instructions are included as a separate tab, which may reinforce a Windows-centric approach. There is no evidence of missing Linux examples or exclusive use of Windows tools; all commands use Azure CLI, which is cross-platform.
Recommendations
- Alternate the order of example tabs so Linux/macOS is sometimes shown first.
- Add explicit notes confirming full parity and support for Linux/macOS environments.
- Consider merging PowerShell and Windows tabs if the commands are identical, or clarify when PowerShell is required.
- Reference Linux/macOS documentation in related content, not just PowerShell.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides environment variable examples for Windows (cmd), PowerShell, and Linux/macOS, but consistently lists Windows examples first in each section. All major CLI instructions use Azure CLI, which is cross-platform, and Linux/macOS instructions are present and correct. There are no sections that are Windows-only, nor are there Windows-specific tools or patterns used exclusively.
Recommendations
- Rotate the order of example tabs so that Linux/macOS is shown first in some sections, or randomize the order to avoid implicit prioritization.
- Explicitly state that all CLI commands work on Linux/macOS as well as Windows.
- Consider adding more Linux/macOS-specific automation examples (e.g., cron job setup) alongside Windows Task Scheduler.
- Where scripting is discussed, provide equal detail for both Linux/macOS and Windows approaches.
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation provides examples for PowerShell, macOS & Linux, and Windows in several sections, but PowerShell (Windows-centric) examples are consistently presented first. Some commands and scripting guidance are PowerShell-heavy, and Windows tools like Task Scheduler are mentioned alongside Linux equivalents. However, Linux/macOS examples are present for most critical steps, and automation is illustrated with a Linux shell script. There are minor gaps, such as the lack of a full Windows batch script example for automation, and PowerShell is used as the default for environment variable manipulation.
Recommendations
- Alternate the order of examples so Linux/macOS commands are shown first in some sections.
- Provide full Windows batch (.bat/.cmd) script examples for automation, not just mention Task Scheduler.
- Include more explicit Linux/macOS tool recommendations (e.g., cron) before or alongside Windows tools.
- Balance PowerShell and Bash usage for environment variable manipulation and scripting.
- Ensure all critical steps have both Windows and Linux/macOS examples, especially for automation.
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation provides automation examples primarily for Linux/macOS (shell script), but when mentioning script file types, it lists Windows formats (.cmd, .bat, .ps1) before Linux/Mac (.sh). It also references Windows Task Scheduler as a job scheduler alongside cron, and does not provide explicit PowerShell or Windows batch script examples, but implies their use. The overall flow and examples are cross-platform, but subtle Windows-first ordering and tool mentions are present.
Recommendations
- List Linux/Mac script file types (.sh) before Windows types (.cmd, .bat, .ps1) to avoid Windows-first ordering.
- Provide explicit Linux/macOS automation examples (e.g., cron job setup) before or alongside Windows equivalents.
- Include a PowerShell or Windows batch script example if Windows automation is mentioned, and ensure Linux/macOS examples are equally detailed.
- Reference Linux tools (cron, systemd timers) before Windows Task Scheduler when discussing job scheduling.
- Clarify that all az CLI commands work identically on Linux, macOS, and Windows.
Azure Arc
Azure Arc-enabled data services validation
...lob/main/articles/azure-arc/data/validation-program.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page demonstrates mild Windows bias by referencing Windows-centric solutions (e.g., Azure Stack HCI, AKS-HCI) and listing Windows-based partner solutions (DataON, Dell, Hitachi with AKS-HCI, Lenovo ThinkAgile MX) before Linux-focused ones. The prerequisites mention Azure Data Studio and azdata CLI, which are cross-platform, but do not provide explicit Linux/macOS installation or usage guidance. No PowerShell-specific examples or commands are present, and Linux distributions (Red Hat OpenShift, Kublr, Wind River, VMware) are included, but Windows-based solutions are often listed first.
Recommendations
- Add explicit Linux/macOS installation instructions for tools like azdata and Azure Data Studio.
- Ensure partner solutions are grouped or ordered to avoid Windows-first perception (e.g., alternate listing order or group by OS type).
- Include examples or notes for Linux/macOS users where platform-specific steps may differ (e.g., Kubernetes config file location, CLI usage).
- Highlight Linux-native Kubernetes distributions and their validation status more prominently.
Azure Arc
Upload billing data to Azure and view it in the Azure portal
.../articles/azure-arc/data/view-billing-data-in-azure.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by referencing Excel as the default tool for opening CSV files and omitting any mention of Linux/macOS alternatives. There are no command-line examples or instructions for Linux/macOS users, nor are cross-platform tools suggested for viewing or processing billing data. The workflow assumes GUI-based interaction with the Azure portal, which is accessible from any OS, but the file handling instructions are Windows-centric.
Recommendations
- Mention cross-platform tools for opening CSV files, such as LibreOffice Calc, Numbers (macOS), or command-line utilities like 'cat', 'less', or 'csvkit'.
- Provide examples or references for automating billing data uploads using Linux/macOS shell scripts (e.g., bash, curl, az CLI).
- Clarify that the Azure portal and storage account access are OS-agnostic and can be performed from any modern browser.
- Include a note or section for Linux/macOS users with relevant tips or alternative workflows.
Azure Arc
Configure Authentication for Edge RAG Preview Enabled by Azure Arc
.../articles/azure-arc/edge-rag/prepare-authentication.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias by referencing Windows Notepad as the suggested tool for storing IDs, and by omitting any mention of Linux/macOS equivalents or cross-platform alternatives. All examples and screenshots are based on the Azure Portal GUI, which is platform-agnostic, but there are no CLI or Powershell examples (which could introduce further bias if present). The reference to Windows Notepad is minor but does signal a default assumption of Windows usage.
Recommendations
- Replace 'Windows Notepad' with 'a text editor of your choice (e.g., Notepad, TextEdit, gedit, nano, etc.)' to be inclusive of all platforms.
- Add a note that the Azure Portal is accessible from any OS with a web browser.
- If CLI instructions are added in future, ensure both Azure CLI (cross-platform) and Powershell (Windows/macOS/Linux) examples are provided.
- Avoid referencing platform-specific tools unless alternatives are listed.
Azure Arc
Requirements for Edge RAG Preview, Enabled by Azure Arc
.../blob/main/articles/azure-arc/edge-rag/requirements.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. Windows Server is mentioned first in NFS setup guides, and a Windows machine is suggested as a management host, with references to Windows-specific documentation. Linux is supported and required for VM OS, but Linux examples and guides are less prominent or secondary. There is no explicit PowerShell usage or exclusive Windows-only steps, but Windows tools and patterns are referenced before or alongside Linux equivalents.
Recommendations
- List Linux setup guides before or alongside Windows Server guides for NFS.
- Provide explicit Linux management host instructions and examples, not just Windows.
- Clarify that management tools (Azure CLI, kubectl, Helm) can be installed and used on Linux/macOS, and link to cross-platform installation guides.
- Avoid suggesting Windows as the default or preferred management host; present Linux/macOS as equal options.
- Ensure all referenced configuration and setup articles include Linux/macOS instructions where applicable.
Azure Arc
Customer intent: "As a cloud administrator, I want to understand how to get the region segment of regional endpoints , so that I can configure Azure services in specific regions without errors."
...ob/main/articles/azure-arc/includes/arc-region-note.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for listing regions, but the PowerShell example is shown immediately after the CLI example and uses Windows-centric tooling. There is no explicit Linux shell example (e.g., Bash), and PowerShell is primarily a Windows tool, though it is now cross-platform. The ordering and inclusion of PowerShell may subtly favor Windows users.
Recommendations
- Add a Bash example for listing regions, such as using 'az account list-locations --output table' in a Linux shell context.
- Clarify that Azure CLI works on all platforms and is the recommended cross-platform tool.
- If PowerShell is included, note its cross-platform availability or provide equivalent Bash commands.
- Consider listing examples in the order: Azure CLI (cross-platform), Bash (Linux/macOS), then PowerShell (Windows).