234
Pages Scanned
51
Pages Flagged
234
Changed Pages
21.8%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:07
Scan Information
Started At: 2026-02-20 00:00:07
Finished At: In Progress
Status: in_progress
Target Repo: Azure Management
Current Phase: discovery
Files Queued: 234
Files Completed: 234
Problematic Pages
51 issues found
Azure Arc
Clean-Up Script for Workload Orchestration
...es/azure-arc/workload-orchestration/clean-up-script.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation exclusively provides a PowerShell script (RGCleanScript.ps1) for resource clean-up, with all examples and instructions tailored to Windows/PowerShell environments. There are no Bash, shell, or cross-platform alternatives, nor any mention of how Linux or macOS users can perform the same task.
Recommendations
- Provide a Bash or cross-platform shell script equivalent to RGCleanScript.ps1, or document how Linux/macOS users can perform the same clean-up operations using Azure CLI or other tools.
- Add explicit instructions or examples for running the clean-up process on Linux/macOS, including any prerequisites or dependencies.
- If the script is inherently Windows-only, clearly state this limitation at the top of the documentation and suggest alternative manual steps for non-Windows users.
Create Pull Request
Azure Arc
Onboarding Scripts for Workload Orchestration
...azure-arc/workload-orchestration/onboarding-scripts.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page is heavily biased toward Windows, with all onboarding scripts and examples provided exclusively in PowerShell. Windows-specific tools like 'winget' are used for installation steps, and there are no Linux/macOS equivalents or instructions. The page assumes the use of PowerShell terminals and does not mention Bash or other shells, nor does it provide cross-platform script alternatives.
Recommendations
- Provide Bash or shell script equivalents for onboarding tasks, or clarify if the scripts are cross-platform.
- Replace or supplement 'winget' installation instructions with platform-agnostic alternatives (e.g., 'apt', 'brew', or manual download commands for Azure CLI and kubectl).
- Explicitly state platform requirements and limitations for the onboarding scripts.
- Add Linux/macOS-specific instructions and examples, including how to run the scripts and prerequisites for those environments.
- If PowerShell is required, mention that PowerShell Core (pwsh) is available cross-platform and provide guidance for Linux/macOS users.
Azure Arc
Migrate Existing Target Resources to General Availability
...s/azure-arc/workload-orchestration/migration-script.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation provides only a PowerShell migration script (WOGAMigration.ps1) and instructs users to run it in PowerShell, with no mention of Linux/macOS-compatible alternatives or instructions. This creates friction for non-Windows users who may not have access to PowerShell or may prefer Bash or other native tools.
Recommendations
- Provide a Bash or cross-platform script for Linux/macOS users, or document how to run the PowerShell script using PowerShell Core on Linux/macOS.
- Explicitly state PowerShell Core compatibility if applicable, and provide installation instructions for Linux/macOS.
- Offer example commands for Linux/macOS environments alongside Windows/PowerShell instructions.
Azure Arc
Release Notes for Workload Orchestration
...cles/azure-arc/workload-orchestration/release-notes.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page provides CLI examples primarily in PowerShell syntax, especially in the May 2025 release section. Bash examples are used elsewhere, but PowerShell is shown in some critical configuration scenarios. There is no explicit mention of Linux/macOS equivalents or alternative shell usage, and PowerShell examples appear before Bash in the release chronology.
Recommendations
- Provide CLI examples in both Bash and PowerShell syntax, or use Bash as the default for cross-platform parity.
- Explicitly state that Azure CLI commands work on Linux/macOS and Windows, and clarify any OS-specific differences.
- Where PowerShell syntax is used, add a Bash equivalent immediately after.
- Review all CLI examples to ensure they are not using Windows-specific shell features (e.g., backticks, variable syntax) unless necessary.
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides SQL connectivity examples using PowerShell syntax (e.g., kubectl exec ... -- /opt/mssql-tools/bin/sqlcmd ...), which is typically associated with Windows environments. The examples are labeled as 'powershell', and no equivalent Linux/macOS shell examples (e.g., bash) are provided. Additionally, the PowerShell examples appear before any mention of Linux alternatives, creating a Windows-first impression.
Recommendations
- Provide Linux/macOS shell (bash) examples alongside PowerShell examples for commands involving kubectl and sqlcmd.
- Remove or clarify the 'powershell' label on code blocks where the command is cross-platform and not specific to PowerShell.
- Explicitly state that the commands can be run from any OS with kubectl and sqlcmd installed, and provide guidance for Linux/macOS users.
- Consider showing bash examples first or in parallel to avoid Windows-first bias.
Azure Arc
Customer intent: As a system administrator, I want to configure a single-node Kubernetes cluster with adequate resources and storage provisions, so that I can deploy and manage applications effectively using Azure IoT Operations and Azure Container Storage.
...tainer-storage/includes/single-node-edge-essentials.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation is mostly Linux-focused but introduces Windows-centric tools (Invoke-AksEdgeNodeCommand) for Linux node configuration, without providing native Linux shell alternatives. This creates friction for Linux users who may not have access to PowerShell or Windows-specific Azure tools.
Recommendations
- Provide native Linux shell (bash) command examples for sysctl configuration, such as 'sysctl fs.inotify.max_user_instances' and 'echo "fs.inotify.max_user_instances = 1024" | sudo tee -a /etc/sysctl.conf && sudo sysctl -p'.
- Clarify whether Invoke-AksEdgeNodeCommand is required or optional, and if so, explain how Linux users can install or use it, or provide alternatives.
- Ensure all critical configuration steps have Linux-native command examples alongside any Windows/PowerShell/Invoke-AksEdgeNodeCommand usage.
Medium 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 and some instructions (e.g., for curl and kubectl) reference Windows-specific behaviors or PowerShell. Linux installation instructions are less explicit, sometimes just referencing 'install curl package' without a link or detailed guidance. There is also a note about using cmd.exe on Windows, but no equivalent Linux/macOS guidance.
Recommendations
- Provide explicit installation links or commands for Linux and macOS, not just Windows.
- Ensure Linux/macOS instructions are as detailed as Windows instructions (e.g., for curl, kubectl).
- Avoid referencing Windows-specific behaviors (like PowerShell curl alias) without mentioning Linux/macOS equivalents.
- List installation options in a neutral order or group by OS, rather than Windows first.
- Add sample commands for Linux/macOS where Windows-specific notes are given.
Azure Arc
Features and Capabilities of SQL Managed Instance enabled by Azure Arc
...n/articles/azure-arc/data/managed-instance-features.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_authentication
Summary
The documentation references Windows-centric tools (SSMS, SQL Server Data Tools, SQL Server PowerShell, SQL Server Profiler) and mentions Windows Authentication as a supported feature. PowerShell scripting support is highlighted in the manageability section. However, Azure PowerShell is marked as unsupported, and Azure CLI is listed as supported. There are no explicit Linux/macOS examples or tool recommendations, but the page does not present critical tasks as Windows-only.
Recommendations
- Add explicit mention of cross-platform tools (e.g., Azure Data Studio, Azure CLI, Visual Studio Code) and clarify their Linux/macOS compatibility.
- Provide examples or links for using SQL Managed Instance enabled by Azure Arc from Linux/macOS environments.
- Clarify that Windows Authentication is only relevant for Windows environments and suggest alternatives for Linux/macOS users (e.g., SQL Server Authentication, Microsoft Entra authentication when available).
- Highlight PowerShell alternatives (such as Bash or Azure CLI) for scripting and automation on Linux/macOS.
Azure Arc
Migrate a database from SQL Server to SQL Managed Instance enabled by Azure Arc
...articles/azure-arc/data/migrate-to-managed-instance.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides several examples and instructions that are Windows-centric, such as using Windows file paths (e.g., C:\Backupfiles\test.bak) and referencing tools like SQL Server Management Studio (SSMS) without mentioning cross-platform alternatives. There are no explicit Linux/macOS examples for performing backups, and Windows paths are used exclusively in key steps, which may confuse or hinder Linux/macOS users.
Recommendations
- Include Linux/macOS equivalents for file paths in backup examples (e.g., /home/user/backup/test.bak).
- Mention cross-platform tools such as Azure Data Studio alongside SSMS, especially for backup/restore operations.
- When referencing tools like Azure Storage Explorer and Visual Studio Code, clarify their cross-platform availability.
- Provide example commands for both Windows and Linux/macOS environments where file operations are involved.
- Explicitly state that the instructions apply to all supported platforms, or call out any platform-specific differences.
Azure Arc
Troubleshoot Azure Arc resource bridge issues
...re-arc/resource-bridge/troubleshoot-resource-bridge.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation includes several examples and troubleshooting steps that reference Windows tools and patterns, such as PowerShell commands and Windows-specific error messages (e.g., 'connectex', 'wsarecv'). PowerShell is used for network troubleshooting and DNS resolution, but equivalent Linux commands are not provided. Windows terminology and error codes are often shown first or exclusively, while Linux alternatives are mentioned less frequently or only in passing. There are also sections where only Windows-based troubleshooting steps are given, such as using PowerShell for HTTP/2 troubleshooting, and no Linux/macOS equivalents are offered.
Recommendations
- Provide Linux/macOS equivalents for all PowerShell examples (e.g., use curl, wget, or openssl for HTTP/2 troubleshooting).
- Include Linux/macOS commands for DNS resolution (e.g., dig, nslookup, host) alongside Windows/PowerShell examples.
- When referencing Windows-specific error codes (e.g., 'connectex', 'wsarecv'), also mention typical Linux/macOS error messages for similar scenarios.
- Ensure that troubleshooting steps and CLI instructions are platform-neutral or clearly indicate if a step is Windows-only.
- Add explicit guidance for Linux/macOS users where file paths, permissions, or CLI usage may differ.
Azure Arc
CLI reference for `azcmagent connect`
...b/main/articles/azure-arc/servers/azcmagent-connect.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides authentication options and examples for connecting servers to Azure Arc using the azcmagent CLI. While the overall content is cross-platform, there is evidence of Windows bias: Windows authentication methods are described first, Windows certificate store options are detailed, and PowerShell tools (Get-AzAccessToken) are referenced for access token retrieval without mentioning Linux/macOS equivalents. Linux authentication methods are present but not prioritized, and Linux-specific tooling is not referenced.
Recommendations
- Present authentication options in a platform-neutral order, or explicitly state platform applicability for each method.
- For access token retrieval, provide Linux/macOS alternatives (such as Azure CLI commands like 'az account get-access-token') alongside PowerShell examples.
- When describing certificate-based authentication, clarify Linux/macOS certificate storage and retrieval methods, not just Windows certificate stores.
- Add explicit Linux/macOS examples where relevant, such as shell commands for hostname retrieval or certificate handling.
- Ensure that all examples and instructions are equally applicable to Linux/macOS, or provide platform-specific sections as needed.
Azure Arc
Manage and maintain the Azure Connected Machine agent
...s/blob/main/articles/azure-arc/servers/manage-agent.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides comprehensive coverage for both Windows and Linux platforms, including installation, upgrade, uninstall, and proxy configuration. However, there are mild signs of Windows bias: Windows examples and sections are often presented first, PowerShell scripts are used for cleanup and automation tasks without equivalent Bash scripts, and Windows-specific tools (e.g., Group Policy, WSUS, Configuration Manager) are described in detail, while Linux equivalents (such as package management automation or systemd integration) are not. The cleanup script for stale resources is only provided in PowerShell, with no Bash or CLI equivalent for Linux users.
Recommendations
- Present Linux and Windows examples in parallel or alternate order, rather than always Windows first.
- Provide Bash or Azure CLI scripts for automation tasks (e.g., stale resource cleanup) alongside PowerShell scripts.
- Include guidance for automating agent upgrades and removals on Linux (e.g., using cron, systemd, or Ansible), similar to the detail given for Windows tools like Group Policy and WSUS.
- Expand Linux sections to mention log locations, package management automation, and integration with Linux-native monitoring/configuration tools.
- Where PowerShell is used for Azure resource management, offer Azure CLI equivalents for cross-platform parity.
Azure Arc
Enable VM Extensions Using Azure Resource Manager Template
...les/azure-arc/servers/manage-vm-extensions-template.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_first
Summary
The documentation provides ARM template examples for both Linux and Windows VM extensions, but all deployment instructions and commands are exclusively shown using Azure PowerShell. There are no Azure CLI or Bash examples, and PowerShell is presented as the only method for deploying templates, which may create friction for Linux/macOS users. Additionally, PowerShell commands and Windows-style file paths are shown first and exclusively in deployment sections.
Recommendations
- Add Azure CLI examples for deploying ARM templates (e.g., using 'az deployment group create') alongside PowerShell commands.
- Include Bash shell command examples where appropriate, especially for Linux users.
- Mention that Azure PowerShell can be used cross-platform, but provide explicit guidance for Linux/macOS users who may prefer Azure CLI.
- Show both Windows and Linux file path conventions in examples (e.g., 'D:\Azure\Templates\...' and '/home/user/Azure/Templates/...').
- Consider presenting CLI and PowerShell deployment options side-by-side, or at least clarify that both are supported.
Azure Arc
Recover from accidental deletion of resource bridge VM
...em-center-virtual-machine-manager/disaster-recovery.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation provides only Windows/PowerShell-based recovery instructions and scripts for the Azure Arc resource bridge VM. There are no Linux/macOS examples, nor is there mention of equivalent tools or scripts for non-Windows platforms. The recovery script is explicitly designed for Windows, and Linux users are not given guidance or alternatives.
Recommendations
- Provide equivalent recovery instructions and scripts for Linux/macOS users, using Bash or Python.
- Explicitly state platform requirements and limitations, clarifying if recovery is only supported from Windows.
- If possible, offer a cross-platform script or containerized solution.
- Add a section explaining why Linux/macOS support is unavailable if this is a technical limitation.
Azure Arc
Install Arc agent at scale for your VMware VMs
...arc/vmware-vsphere/enable-guest-management-at-scale.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation page provides multiple methods for installing Arc agents at scale for VMware VMs. However, the 'Auto Arc-enablement script' section is heavily PowerShell-centric, with instructions and examples exclusively for Windows (PowerShell terminal, Set-ExecutionPolicy, Windows Task Scheduler). The script is not described for Linux/macOS users, and there are no Bash or cron examples. Windows tools and patterns (PowerShell, Task Scheduler) are mentioned before Linux equivalents. While there is a brief note about sudo configuration for Linux, the main automation example is Windows-only.
Recommendations
- Provide equivalent Bash or shell script examples for Linux/macOS users.
- Include instructions for running the automation script on Linux (e.g., using cron instead of Windows Task Scheduler).
- Clarify if the helper script is cross-platform or provide a Linux version.
- Show both PowerShell and Bash usage examples side-by-side.
- Mention Linux tools (e.g., cron, systemd timers) alongside Windows Task Scheduler.
- Ensure out-of-band methods (like Ansible) are highlighted for Linux users.
Azure Arc
Upgrade the Azure Arc resource bridge
...l-machine-manager/upgrade-azure-arc-resource-bridge.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation assumes the user is operating from a Windows/SCVMM environment, referencing the SCVMM server as the location to run commands and does not provide Linux/macOS equivalents or clarify cross-platform support for the Azure CLI steps. All examples and instructions are Windows-centric, with no mention of Linux or macOS environments.
Recommendations
- Clarify whether the Azure CLI commands (az arcappliance) can be run from Linux/macOS workstations, and if so, provide explicit instructions or examples for those platforms.
- If the upgrade process is supported only from Windows/SCVMM environments, state this explicitly at the beginning of the article.
- If Linux/macOS are supported, add notes about any required tools or configuration differences (e.g., file paths, shell syntax).
- Where possible, provide cross-platform command examples or note any platform-specific limitations.
Azure Arc
Perform disaster recovery operations
...mware-vsphere/recover-from-resource-bridge-deletion.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_first
Summary
The documentation page for disaster recovery operations of the Azure Arc resource bridge VM is heavily focused on PowerShell scripts and commands, with no mention of Linux/macOS equivalents or cross-platform alternatives. All script examples and instructions are given in PowerShell syntax, and there is no guidance for users who may be operating from Linux or macOS environments. The onboarding script is referenced as a .ps1 file, implying Windows/PowerShell usage, and no Bash or shell alternatives are provided.
Recommendations
- Provide equivalent Bash or shell script examples for Linux/macOS users, or clarify if the onboarding script is cross-platform.
- Explicitly state the platform requirements for running the onboarding script (e.g., Windows/PowerShell only, or if PowerShell Core is supported on Linux/macOS).
- If the onboarding script can be run using PowerShell Core on Linux/macOS, add instructions for installation and usage on those platforms.
- Mention any prerequisites or limitations for Linux/macOS users, and offer guidance for completing the recovery process from those environments.
Azure Arc
Remove your VMware vCenter environment from Azure Arc
...e-arc/vmware-vsphere/remove-vcenter-from-arc-vmware.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides detailed Windows/PowerShell instructions for running the deboarding script, including execution policy steps and script invocation. There are no equivalent instructions or examples for running the script on Linux or macOS, nor is it clarified whether the script can be run cross-platform. Windows instructions are presented first and exclusively, creating friction for Linux users.
Recommendations
- Clarify whether the deboarding script can be run on Linux/macOS (e.g., with PowerShell Core or Azure CLI).
- Provide explicit Linux/macOS instructions for downloading and running the script, including any prerequisites (such as PowerShell Core or bash).
- If the script is Windows-only, state this clearly and offer alternative manual steps for Linux/macOS users.
- Present both Windows and Linux/macOS instructions in parallel or note platform-specific differences.
- Consider providing a bash or cross-platform version of the deboarding script if feasible.
Azure Arc
Diagnostics of Edge-Related Logs and Errors in Workload Orchestration
.../azure-arc/workload-orchestration/diagnose-problems.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation page provides almost exclusively PowerShell-based examples and scripts for enabling diagnostics, onboarding, and log collection. All CLI/script instructions are given in PowerShell syntax, with no Bash or Linux/macOS shell equivalents. Paths in JSON templates use Windows-style backslashes and drive letters. There is no mention of Linux/macOS alternatives or cross-platform compatibility for the scripts, and Windows tools (PowerShell, Windows file paths) are referenced before any Linux equivalents, which are missing.
Recommendations
- Provide Bash or shell script equivalents for all PowerShell commands, especially for az CLI usage.
- Clarify whether the infra_onboarding.ps1 script is cross-platform or provide a Linux/macOS version (e.g., infra_onboarding.sh).
- Use platform-neutral file paths in JSON templates, or provide examples for both Windows and Linux/macOS.
- Mention prerequisites for Linux/macOS users, including any required tools or environment setup.
- Add notes or sections explicitly addressing Linux/macOS usage and troubleshooting.
Azure Arc
Bulk Review, Publish, and Deploy with Workload Orchestration
...es/azure-arc/workload-orchestration/bulk-deployment.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation consistently uses PowerShell syntax for Azure CLI commands and references PowerShell scripts (e.g., bulk_deployment.ps1, workflow-delete.ps1) without providing equivalent Bash or shell script examples. There are no explicit Linux/macOS instructions or examples, and the PowerShell syntax is shown for all CLI commands, which may create friction for Linux/macOS users who typically use Bash. The documentation does not mention Linux tools or patterns, nor does it clarify cross-platform usage for the scripts.
Recommendations
- Provide CLI command examples in Bash syntax as well as PowerShell, or use generic CLI syntax that works across platforms.
- Offer equivalent Bash shell scripts for bulk_deployment.ps1 and workflow-delete.ps1, or clarify if the PowerShell scripts are cross-platform (e.g., PowerShell Core).
- Add notes or sections explaining how Linux/macOS users can run the Azure CLI commands and scripts, including any prerequisites or differences.
- Explicitly state whether the scripts are compatible with PowerShell Core on Linux/macOS, or provide alternatives.
- Consider showing Bash examples first or side-by-side with PowerShell to improve parity.
Azure Arc
Prepare the Environment for Workload Orchestration
...rc/workload-orchestration/initial-setup-environment.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation exhibits Windows bias primarily in the 'kubectl' installation instructions, where only the Windows-specific 'winget' command is provided and no Linux/macOS installation method is mentioned. Additionally, the file extraction example under the Bash tab uses the Windows-native 'Expand-Archive' command with Windows-style paths, which is not available on Linux/macOS Bash shells. Throughout the page, examples and variable naming conventions often use Windows paths and tools first, and Linux/macOS equivalents are missing or unclear.
Recommendations
- Provide Linux/macOS installation instructions for 'kubectl', such as using 'apt', 'brew', or downloading from the official Kubernetes site.
- For file extraction, include cross-platform Bash examples (e.g., 'unzip archive.zip -d /path/to/dir') and clarify which commands are Windows-only.
- Use generic or platform-neutral path examples in Bash sections, or provide separate examples for Windows and Linux/macOS.
- Review all Bash examples to ensure they are valid for Linux/macOS environments, not just Windows.
- Add a note clarifying when a command or tool is Windows-specific and provide alternatives for other platforms.
Azure Arc
Troubleshooting for Workload Orchestration
...es/azure-arc/workload-orchestration/troubleshooting.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The troubleshooting guidance for workload orchestration is heavily biased toward PowerShell and Windows-style command syntax. Most examples use PowerShell, even for tasks that are cross-platform (e.g., Azure CLI, Docker, kubectl), and do not provide equivalent Bash or Linux shell examples. Windows-specific patterns (e.g., PowerShell variable syntax, ConvertTo-Json, Out-File) are used without Linux alternatives. Only in the 'Troubleshoot service groups' section are Bash examples provided alongside PowerShell, but elsewhere Linux users must adapt Windows-centric instructions.
Recommendations
- Provide Bash/Linux shell equivalents for all PowerShell examples, especially for Azure CLI, Docker, and kubectl commands.
- Avoid using Windows-specific PowerShell constructs (e.g., Out-File, ConvertTo-Json) without showing cross-platform alternatives (e.g., jq, echo, cat, >).
- When referencing file encoding, clarify how to check and convert encoding on Linux/macOS (e.g., using iconv or file command).
- Show both Bash and PowerShell tabs for all command sections, not just service group queries.
- Use cross-platform variable syntax in Azure CLI examples (e.g., $var for PowerShell, $var or ${var} for Bash).
Container Registry
Azure Container Registry Authentication Options Explained
...ontainer-registry/container-registry-authentication.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for authentication, but PowerShell is featured equally alongside CLI, which is less relevant for Linux/macOS users. In several sections, PowerShell is presented as a primary method, and there are no explicit Linux/macOS-specific instructions or terminal examples. While the CLI examples are cross-platform, the PowerShell focus and lack of Linux/macOS context may create friction for non-Windows users.
Recommendations
- Clearly indicate that Azure CLI examples are cross-platform and preferred for Linux/macOS users.
- De-emphasize PowerShell as a primary authentication method, or clarify its relevance for Windows users only.
- Add explicit Linux/macOS terminal examples (e.g., bash/zsh) for common authentication flows, especially for scripting scenarios.
- Where PowerShell is shown, consider providing a parallel bash example or a note for Linux/macOS users.
- In 'Next steps', add links to Linux/macOS-focused getting started guides if available.
Azure Arc
What's new with Azure Connected Machine agent
...main/articles/azure-arc/servers/agent-release-notes.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation consistently presents Windows download links and version numbers before Linux equivalents, and references Windows-specific tools (e.g., PowerShell, msiexec, GUI installer) in troubleshooting and improvements. While Linux parity is generally maintained in features and bug fixes, Windows examples and terminology are prioritized, and some Windows installer instructions lack Linux analogs.
Recommendations
- Present Windows and Linux download links and version numbers side-by-side or alternate their order to avoid implicit prioritization.
- Include Linux-specific troubleshooting steps and installer guidance where Windows instructions are given (e.g., for installer failures, privilege elevation).
- Where Windows tools (PowerShell, msiexec) are mentioned, provide equivalent Linux commands (e.g., shell scripts, sudo usage) for parity.
- Explicitly note when a fix or feature is Windows-only or Linux-only, and provide context or alternatives for the other platform.
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 provides parity for both Windows and Linux platforms, mentioning both installation sources and agent support. However, Windows-specific tools and features (such as Windows Admin Center and Windows-specific cipher suite configuration) are mentioned first or exclusively in some sections. Windows installation package URLs are listed before Linux, and Windows Admin Center is referenced as a service tag and endpoint, with Linux equivalents (such as SSH) mentioned but not elaborated. The cryptographic protocol section gives detailed Windows guidance and links, while Linux is referenced more generally.
Recommendations
- Alternate the order of Windows and Linux installation package URLs to avoid 'windows_first' bias.
- Provide more explicit Linux examples and guidance, such as referencing SSH management for Linux in parity with Windows Admin Center.
- Expand Linux-specific troubleshooting and configuration guidance, especially for TLS and OpenSSL, similar to the Windows section.
- Where Windows tools (like Windows Admin Center) are mentioned, clarify Linux alternatives or state if none exist.
- Ensure that Linux-specific URLs, tools, and patterns are given equal prominence and detail.
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for setting up workload orchestration, but the PowerShell section is presented after Bash and is equally detailed. There are no Windows-specific tools or patterns used, and all commands rely on the Azure CLI, which is cross-platform. However, the presence of PowerShell examples may suggest a slight bias toward Windows users, and Bash is shown first, which is positive for Linux parity.
Recommendations
- Ensure that Bash and PowerShell examples are equally maintained and updated.
- Consider clarifying that both Bash and PowerShell examples are supported on Windows, Linux, and macOS (since Azure CLI works everywhere).
- If possible, add a note that Bash examples are suitable for Linux/macOS users and PowerShell for Windows users, but both can be used cross-platform.
- Continue to avoid Windows-only tools or patterns unless the feature is Windows-specific.
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 notes are presented first in the 'Run the script' and 'Retry command' sections. There is a minor bias in ordering, but Linux parity is maintained throughout with clear Bash instructions.
Recommendations
- Alternate the order of Windows and Linux instructions in sections, or present both 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 are OS-neutral or provide alternatives if any step is OS-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 page references SQL Server Management Studio (SSMS) as the primary GUI tool for connecting to SQL Managed Instance enabled by Azure Arc, which is Windows-only. While it also mentions sqlcmd (available cross-platform), SSMS is listed first and no Linux-native GUI alternatives (such as Azure Data Studio or DBeaver) are suggested. The examples for connecting use sqlcmd, which is cross-platform, but the overall narrative and tool recommendations are Windows-centric. No Linux-specific connection guidance or troubleshooting is provided.
Recommendations
- Mention Azure Data Studio as a cross-platform GUI alternative to SSMS for Linux/macOS users.
- Provide explicit examples or troubleshooting tips for connecting from Linux/macOS, including any differences in authentication or network configuration.
- List sqlcmd before SSMS in tool recommendations to emphasize cross-platform parity.
- Include a note about installing sqlcmd on Linux/macOS, with a link to relevant documentation.
- Consider referencing other popular cross-platform SQL clients (e.g., DBeaver, TablePlus) for broader user support.
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 major tasks, but consistently lists Azure PowerShell examples after Azure CLI. There is no explicit Windows bias in terms of missing Linux examples, as Azure CLI commands and environment variable instructions are shown, which are cross-platform. However, Azure PowerShell is included throughout, which is primarily used on Windows, and its examples use Windows-style environment variable syntax. No Linux-specific tools or patterns (such as Bash scripting or Linux package managers) are mentioned, but the CLI instructions are suitable for Linux/macOS users.
Recommendations
- Clarify that Azure CLI commands are cross-platform and preferred for Linux/macOS users.
- Explicitly state that Azure PowerShell is primarily for Windows environments, and that Linux/macOS users should use Azure CLI.
- Consider adding a brief note or section for Linux/macOS users, confirming that all steps can be completed using Azure CLI and kubectl.
- Where environment variables are set, show both Bash (export) and PowerShell ($Env:) syntax side-by-side for parity.
- If possible, add a 'Linux/macOS' tab for commands where there are subtle differences (e.g., environment variable setting).
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 page lists both Windows and Linux-related endpoints, but there is evidence of Windows bias: Windows NTP server ('time.windows.com') is mentioned as the default, and Windows-specific endpoints (e.g., 'login.windows.net', 'sts.windows.net', 'servicebus.windows.net') appear before Linux equivalents. The notes reference Windows NTP as the default for Hyper-V, but do not mention Linux NTP alternatives. There are no explicit Linux examples or references to Linux tools/patterns for network configuration. However, Linux endpoints (e.g., 'packages.microsoft.com', 'linuxgeneva-microsoft.azurecr.io') are included, and SSH is listed as a connectivity requirement, which is cross-platform.
Recommendations
- Mention Linux NTP server options (e.g., 'pool.ntp.org') alongside Windows NTP.
- Clarify that management machines and appliance VMs can be Linux or Windows, and provide guidance/examples for both.
- Add references to Linux network configuration tools (e.g., iptables, firewalld) and how to allowlist URLs/ports.
- Ensure Linux endpoints and requirements are given equal prominence and explanation.
- If PowerShell or Windows-specific configuration steps are referenced elsewhere, add Bash/Linux equivalents.
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_example
linux_first
Summary
The documentation provides both Linux and Windows methods for base64 encoding files, mentioning Linux (base64) first and then Windows (certutil). However, the Windows example is more verbose, including additional steps for header removal. No PowerShell-specific commands or Windows-first ordering are present. The rest of the guide uses cross-platform tools (OpenSSL, Azure CLI, kubectl) and examples are generic or Linux-oriented. There is minor bias in the Windows section being more detailed, but Linux parity is generally maintained.
Recommendations
- Clarify that certutil is available on Windows by default, while base64 is standard on Linux/macOS.
- Provide a macOS-specific example for base64 encoding, if relevant.
- Add a note about removing headers from base64 output on Linux/macOS, if needed, for parity with the Windows example.
- Ensure all steps for both OSes are equally detailed, including header removal for Linux/macOS if applicable.
Azure Arc
Azure RBAC on Azure Arc-enabled Kubernetes clusters
.../blob/main/articles/azure-arc/kubernetes/azure-rbac.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page provides Azure CLI and kubectl examples, which are cross-platform. However, in the section about installing Azure kubelogin, Windows and Mac instructions are mentioned first, followed by Linux/Ubuntu instructions. Additionally, Azure CLI is referenced throughout, which is available on all platforms but is often associated with Windows environments. There are no PowerShell-specific examples, but Windows tools and patterns are referenced before Linux equivalents in some places. Overall, the bias is minor and does not prevent Linux/macOS users from completing the tasks.
Recommendations
- When listing installation instructions for tools like Azure kubelogin, present Linux, macOS, and Windows options together or in a neutral order.
- Explicitly state that Azure CLI and kubectl commands work on Linux, macOS, and Windows.
- Where possible, provide links to platform-specific installation guides for Azure CLI, kubectl, and kubelogin.
- Avoid referencing Windows or macOS first unless there is a technical reason.
Azure Arc
Azure Arc resource bridge system requirements
...icles/azure-arc/resource-bridge/system-requirements.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation consistently refers to Azure CLI installation links and requirements, but in several places, the Windows installation link is shown first or exclusively (e.g., 'Azure CLI x64' links to the Windows install page). There are no explicit Linux/macOS examples or links, and the management machine requirements do not clarify cross-platform support. However, the CLI tools themselves are cross-platform, and no critical steps are Windows-only.
Recommendations
- Add explicit links and instructions for installing Azure CLI on Linux and macOS, not just Windows.
- Clarify that the management machine can be Windows, Linux, or macOS, and provide parity in examples.
- When referencing Azure CLI installation, use the generic cross-platform install page or provide tabs for each OS.
- Mention any OS-specific caveats or requirements if they exist (e.g., file path conventions, dependencies).
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 both Windows and Linux examples for key operations (such as log locations and agent commands), but there is a mild Windows bias. PowerShell examples are consistently given alongside Azure CLI, and in some sections, Windows-specific instructions or notes (e.g., PowerShell command syntax, log file locations) are presented first or in more detail. The CLI examples use backticks for line continuation, which is a Windows PowerShell convention, potentially confusing for Linux/macOS users. References to downloading Windows installation packages are present, but Linux equivalents are also mentioned.
Recommendations
- Ensure CLI examples use standard Bash line continuation (\) for Linux/macOS, or clarify which shell is assumed.
- Alternate the order of Windows and Linux instructions/examples to avoid always presenting Windows first.
- Explicitly mention Linux/macOS support in introductory sections to reinforce parity.
- Where PowerShell is referenced, provide Bash equivalents or clarify that PowerShell is cross-platform.
- Add notes about differences in CLI usage between Windows (PowerShell) and Linux/macOS (Bash).
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 clear parity between Windows and Linux VM extensions for Azure Arc-enabled servers, with dedicated tables for each OS and partner extensions. However, Windows extensions are listed first, which is a minor 'windows_first' bias. All deployment methods (Azure CLI, PowerShell, portal, ARM templates) are mentioned equally for both OSes, and Linux-specific extensions and links are present throughout.
Recommendations
- Consider alternating the order of Windows and Linux extension sections, or explicitly stating that both OSes are equally supported.
- Add a brief introductory note clarifying that all extension management methods and most extensions are available for both Windows and Linux, to reinforce parity.
- Ensure that future updates maintain equal detail and visibility for Linux extensions and deployment methods.
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 with managed identity on Azure Arc-enabled servers. However, the Windows/PowerShell example is presented first, and the PowerShell script is more detailed, including error handling and output formatting. The Linux/Bash example is given after, with less explanation and detail. The 'Related content' section mentions PowerShell before Azure CLI, which may reinforce Windows-first patterns.
Recommendations
- Present Windows and Linux examples side-by-side or alternate which comes first to avoid implicit prioritization.
- Ensure both PowerShell and Bash examples are equally detailed, including error handling and output formatting.
- In 'Related content', list Azure CLI before or alongside PowerShell to improve parity.
- Add clarifying notes that both Windows and Linux are fully supported and that users should select the example appropriate for their environment.
Azure Arc
Run command on Azure Arc-enabled servers (Preview)
...cs/blob/main/articles/azure-arc/servers/run-command.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation mentions Azure CLI, PowerShell, and REST API as supported experiences, listing PowerShell (a Windows-centric tool) alongside Azure CLI and REST API. However, it does state that both Windows and Linux operating systems are supported. There are no explicit examples or instructions favoring Windows, but PowerShell is mentioned before Linux-native tools or scripting languages. The 'Next steps' section links to PowerShell guidance before REST API, which may subtly reinforce Windows-first patterns.
Recommendations
- Ensure that Linux-specific scripting examples and tools (such as Bash or shell scripts) are equally represented alongside PowerShell.
- In 'Next steps', consider listing Azure CLI (cross-platform) and REST API before PowerShell, or clarify that PowerShell is available on Linux/macOS as well.
- Add explicit statements or links highlighting Linux support and any Linux-specific considerations (e.g., shell script examples, file path conventions).
- Where PowerShell is mentioned, note its cross-platform availability to avoid implying Windows exclusivity.
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 covers troubleshooting for both Windows and Linux Azure Arc-enabled servers. However, there is some evidence of Windows bias: Windows log file paths and PowerShell/Windows command syntax are mentioned first in several sections, and Windows-specific tools (e.g., PowerShell, Windows environment variables) are referenced before Linux equivalents. Linux examples and paths are provided, but often after Windows, and some remediation steps reference Windows tools or concepts (e.g., `%TEMP%`, `%ProgramData%`) before Linux ones.
Recommendations
- Present Windows and Linux examples side-by-side, or alternate which OS is shown first in each section.
- When referencing log file locations or configuration paths, list both Windows and Linux paths together, rather than Windows first.
- Ensure remediation steps mention Linux equivalents (e.g., `/tmp` for `%TEMP%`) where applicable.
- Where PowerShell or Windows-specific commands are given, provide equivalent Bash/Linux commands.
- Consider adding a summary table or section highlighting OS-specific troubleshooting steps for quick reference.
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
windows_tools
Summary
The documentation generally presents Azure Arc-enabled VMware vSphere as a cross-platform solution, supporting both Windows and Linux VMs. However, there are subtle biases: Windows tools and technologies (such as PowerShell, Windows Server management, and Windows registry/files) are mentioned first or more prominently in several sections. Some links and examples default to Windows tabs or scenarios, and PowerShell is highlighted as a primary automation tool. Linux support is present but often listed after Windows, and Linux-specific examples or tools are less emphasized.
Recommendations
- Ensure that all automation and configuration examples (such as runbooks, onboarding, and VM extensions) explicitly mention and provide parity for Linux alongside Windows.
- When referencing Azure Automation or runbooks, highlight Bash or Python examples equally with PowerShell, and provide links or tabs for both Windows and Linux where applicable.
- In sections discussing configuration, monitoring, and management, balance the order of presentation between Windows and Linux (e.g., 'Windows and Linux servers' instead of 'Windows servers and Linux servers').
- Where links default to Windows-specific tabs or content, ensure Linux tabs or documentation are equally visible and accessible.
- Add Linux-specific scenarios or callouts where unique steps or considerations exist, to help Linux users feel equally supported.
Container Registry
Store Helm Charts in Azure Container Registry
...es/container-registry/container-registry-helm-repos.md
Low Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page primarily uses generic shell commands (bash-like syntax) for Helm and Azure CLI operations, which are cross-platform. However, in the 'Set the following environment variables' section, the command 'set ACR_NAME=<container-registry-name>' is given, which is a Windows Command Prompt syntax. No equivalent Linux/macOS example ('export ACR_NAME=...') is provided. Additionally, in the prerequisites for creating an AKS cluster, Azure CLI is mentioned first, but Azure PowerShell is also referenced, and the Azure portal is included. Overall, the bias is minor and limited to a single environment variable example.
Recommendations
- Provide both Windows (set) and Linux/macOS (export) examples for setting environment variables.
- Clarify that all CLI commands are cross-platform unless otherwise noted.
- Consider showing Linux/macOS syntax first, or side-by-side with Windows equivalents.
Azure Arc
Whats new in Azure Arc-enabled VMware vSphere
...ob/main/articles/azure-arc/vmware-vsphere/whats-new.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation page provides a chronological list of new features for Azure Arc-enabled VMware vSphere. Windows-specific features (such as customizing guest OS settings for Windows VMs and Windows Server Management) are mentioned, but Linux features (like SSH-based agent installation) are also included. However, in several instances, Windows tools and patterns (e.g., System Center Configuration Manager, Group Policy, Azure PowerShell) are listed before or more prominently than their Linux equivalents (e.g., Ansible, Azure CLI). Windows examples and tools tend to appear first in lists, and Windows-specific enhancements are sometimes highlighted without equal Linux coverage.
Recommendations
- When listing tools or methods for agent installation or VM management, alternate the order so Linux tools (e.g., Ansible, Azure CLI) are not always last.
- Where Windows-specific features are described, ensure Linux equivalents (if available) are also mentioned or linked.
- Add explicit Linux/macOS examples or references alongside Windows/PowerShell ones, especially for common tasks (e.g., agent installation, VM management).
- Clarify when features are Windows-only to avoid confusion for Linux users.
- Consider a dedicated section for Linux enhancements or parity features.
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, PowerShell examples are consistently presented immediately after Bash examples, which could be interpreted as a minor 'windows_first' bias. No Windows-specific tools, patterns, or terminology are used, and all instructions are cross-platform via Azure CLI. No Linux/macOS examples are missing.
Recommendations
- Consider alternating the order of Bash and PowerShell examples in some sections, or explicitly state that Bash examples are suitable for Linux/macOS and PowerShell for Windows.
- Add a brief note at the start clarifying that all CLI commands are cross-platform and Bash examples are intended for Linux/macOS users.
- Ensure screenshots and portal instructions do not reference Windows-only features or UI elements (none detected here).
Azure Arc
Staging Resources Before Deployment
...icles/azure-arc/workload-orchestration/how-to-stage.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for all major steps, ensuring parity for Linux/macOS and Windows users. However, in some sections, PowerShell examples are presented immediately after Bash, and occasionally Windows-specific encoding instructions are given (e.g., removing carriage returns in PowerShell). The order of examples is consistently Bash first, then PowerShell, which is a minor bias but does not impact functionality or clarity for Linux/macOS users.
Recommendations
- Maintain Bash-first ordering, but clarify that Bash examples are suitable for Linux/macOS and PowerShell for Windows.
- Explicitly state at the top which platforms each example is for, to help users quickly identify their relevant section.
- Ensure that any platform-specific instructions (such as encoding or file handling) are clearly labeled as Windows or Linux/macOS.
- Consider adding a brief note that all CLI commands (az, kubectl, docker) are cross-platform, and users can use Bash or PowerShell as appropriate for their OS.
Azure Arc
Create a Solution with Shared Adapter Dependency with Workload Orchestration
...ation/quickstart-solution-shared-adapter-dependency.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for all CLI commands and variable definitions, ensuring parity for Linux/macOS and Windows users. However, in most sections, Bash examples are presented before PowerShell, which is a minor bias ('windows_first') as Windows users may expect PowerShell examples first. No exclusive Windows tools, patterns, or terminology are used, and Linux/macOS users can fully follow the tutorial.
Recommendations
- Consider alternating the order of Bash and PowerShell examples in each section, or explicitly state that Bash is for Linux/macOS and PowerShell for Windows at the top of the page.
- Add a brief note clarifying that all CLI commands are cross-platform and that Bash and PowerShell are provided for user convenience.
- Ensure that any future additions (e.g., troubleshooting, file manipulation) include both Bash and PowerShell examples.
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, ensuring parity for Linux/macOS and Windows users. However, in each section, Bash examples are consistently presented before PowerShell examples, which is a minor 'windows_first' bias in ordering. There are no Windows-only tools, patterns, or missing Linux examples. All commands use cross-platform Azure CLI and Helm tools.
Recommendations
- Consider alternating the order of Bash and PowerShell tabs in some sections, or clarify that Bash is shown first for consistency, not platform preference.
- Explicitly state that both Bash and PowerShell are fully supported and that the Azure CLI commands work on all platforms.
- If possible, add a short note at the top indicating Linux/macOS and Windows parity is maintained throughout.
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for all steps, ensuring parity for Linux/macOS and Windows users. However, in each section, Bash examples are presented first, followed by PowerShell, which is a minor bias in favor of Linux/macOS users (not Windows). No Windows-specific tools, patterns, or exclusive instructions are present. All commands use the Azure CLI, which is cross-platform.
Recommendations
- No action needed. The documentation already provides full parity for Linux/macOS and Windows users.
- If desired, alternate the order of Bash and PowerShell tabs in different sections, or clarify that both are equally supported.
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 provides both Bash and PowerShell examples for every step, but consistently presents Bash examples first, followed by PowerShell. There is no exclusive use of Windows tools or patterns, and all commands are cross-platform (using Azure CLI and Helm). However, the PowerShell examples are present throughout, which may suggest a slight Windows bias, but Linux/macOS users are fully supported.
Recommendations
- Maintain Bash examples as the primary example for cross-platform parity.
- Consider clarifying that all commands are cross-platform and can be run on Linux, macOS, or Windows (with Bash or PowerShell).
- Optionally, add a note that PowerShell Core is available on Linux/macOS for users preferring PowerShell.
- Ensure that any references to file paths or shell-specific syntax are correct for both platforms (e.g., use ./file for Bash, .\file for PowerShell).
Azure Portal
Programmatically create Azure Dashboards
...tal/azure-portal-dashboards-create-programmatically.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides examples for deploying Azure dashboards using Azure CLI and Azure PowerShell. While Azure CLI is cross-platform and suitable for Linux/macOS, the PowerShell section is presented after the CLI section but is still prominent. There are no Windows-only tools or patterns, but PowerShell is mentioned as a primary method alongside CLI. The examples and instructions are generally platform-neutral, but PowerShell is emphasized, which may create minor friction for Linux/macOS users who may not use PowerShell.
Recommendations
- Clarify that Azure PowerShell is available cross-platform, and link to installation instructions for Linux/macOS.
- Explicitly note that Azure CLI is recommended for Linux/macOS users.
- Consider adding Bash shell scripting examples for Azure CLI usage.
- Mention that all JSON template operations can be performed on any OS, and highlight cross-platform compatibility.
- If possible, provide a short table comparing CLI and PowerShell usage for dashboard deployment, indicating OS compatibility.
Azure Portal
Get subscription and tenant IDs in the Azure portal
...in/articles/azure-portal/get-subscription-tenant-id.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Azure PowerShell and Azure CLI options for programmatic access, but PowerShell is consistently mentioned first and receives slightly more emphasis. There are no Windows-only tools or patterns, but the ordering and phrasing may subtly favor Windows users. All instructions for the Azure portal are platform-neutral.
Recommendations
- Present Azure CLI and PowerShell options in a neutral order, or alternate which is listed first.
- Clarify that Azure CLI works cross-platform (Windows, Linux, macOS) and is often preferred for Linux/macOS users.
- Consider providing explicit example commands for both Azure CLI and PowerShell in the main content, not just in tips.
- Add a brief note indicating that both tools are available on all major platforms, with links to installation guides for each.
Container Registry
Manage Public Content in Private Container Registry
...icles/container-registry/buffer-gate-public-content.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for importing images to Azure Container Registry, but the PowerShell example is given equal prominence and appears immediately after the CLI example. There are no Linux/macOS-specific examples or explicit mentions of Linux tools or shell patterns. The documentation does not show Linux/macOS-specific workflows or highlight cross-platform differences, and the PowerShell example may be less relevant for Linux/macOS users.
Recommendations
- Add explicit Linux/macOS shell examples (e.g., Bash) for relevant steps, especially for authentication and image import.
- Clarify that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
- Consider mentioning Docker CLI usage for local image management as a common Linux/macOS workflow.
- Add a note that Azure PowerShell is primarily for Windows users, while Azure CLI is recommended for Linux/macOS.
- Provide links or references to Linux/macOS-specific documentation or tutorials where applicable.
Container Registry
Azure Container Registry SKU Features and Limits
...articles/container-registry/container-registry-skus.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for key tasks such as viewing usage and changing SKUs. However, PowerShell (a Windows-centric tool) is consistently mentioned alongside or immediately after the CLI, and is sometimes referenced before REST API or other platform-neutral options. There are no Linux/macOS-specific examples, but the CLI is cross-platform. The order of examples and explicit mention of PowerShell may give the impression of a Windows-first bias.
Recommendations
- Explicitly state that Azure CLI is cross-platform and recommended for Linux/macOS users.
- Where PowerShell is mentioned, clarify that it is available on Linux/macOS as well (if true), or provide Bash scripting examples for Linux users.
- Consider listing Azure CLI examples before PowerShell, as CLI is more universally available.
- Add a brief note or section for Linux/macOS users, confirming that all features are accessible via the CLI and REST API.
- If possible, provide Bash or shell script snippets for common tasks, or link to such resources.