225
Pages Scanned
44
Pages Flagged
225
Changed Pages
19.6%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:07
Scan Information
Started At: 2026-03-03 00:00:07
Finished At: In Progress
Status: in_progress
Target Repo: Azure Management
Current Phase: discovery
Files Queued: 225
Files Completed: 225
Problematic Pages
47 issues found
Azure Arc
Onboarding Scripts for Workload Orchestration
...azure-arc/workload-orchestration/onboarding-scripts.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
missing_linux_example
Summary
The documentation page is heavily biased toward Windows environments. All onboarding scripts are provided as PowerShell (.ps1) files, and users are instructed to run them in a PowerShell terminal. Prerequisites reference Windows-specific tools (winget), and no Linux/macOS equivalents or instructions are provided. There are no Bash or shell script examples, and no mention of how to run these scripts or perform equivalent actions on Linux/macOS platforms.
Recommendations
- Provide Bash or shell script equivalents for onboarding tasks, or clarify if cross-platform support is unavailable.
- Include Linux/macOS installation instructions for Azure CLI and kubectl (e.g., using apt, yum, brew).
- Mention how to run PowerShell scripts on Linux/macOS (using PowerShell Core), or provide alternative scripts.
- Add explicit notes about platform compatibility for the onboarding scripts.
- If the scripts are Windows-only, clarify this limitation in the documentation.
Create Pull Request
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
windows_first
Summary
The documentation provides ARM template examples for both Linux and Windows VM extensions, ensuring parity in template content. However, all deployment commands and walkthroughs exclusively use Azure PowerShell, with no Azure CLI or Bash examples. PowerShell is a Windows-centric tool, though it is available cross-platform. Additionally, PowerShell deployment commands are presented first and exclusively, which may create friction for Linux/macOS users who prefer Azure CLI or Bash.
Recommendations
- Add Azure CLI deployment examples alongside PowerShell for template deployment.
- Explicitly note that PowerShell is available cross-platform, but also provide Bash/CLI alternatives for Linux/macOS users.
- Consider showing Azure CLI examples first or in parallel with PowerShell to avoid Windows-first bias.
- Clarify that the templates themselves are OS-agnostic and can be deployed from any platform.
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 recovery instructions and a downloadable script exclusively for Windows (PowerShell), with no mention of Linux or cross-platform alternatives. All examples and tooling are Windows-centric, and there is no guidance for users operating from Linux or macOS environments.
Recommendations
- Provide equivalent recovery instructions and scripts for Linux/macOS environments, using Bash or cross-platform tools where possible.
- Clearly state if recovery is only supported from Windows, and explain why, or document any limitations.
- If possible, offer a platform-agnostic recovery method (e.g., via Azure CLI, REST API, or containerized tooling).
- Add a section addressing Linux/macOS users, even if only to clarify current limitations and suggest workarounds.
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
windows_tools
missing_linux_example
Summary
The documentation page provides almost exclusively PowerShell-based examples and scripts for enabling and managing diagnostics, log collection, and orchestration on Azure Arc-enabled Kubernetes clusters. File paths in JSON templates and scripts are Windows-style, and there are no Bash or Linux/macOS CLI equivalents. The use of PowerShell is pervasive, and Linux users are not given alternative instructions or scripts, creating friction for non-Windows users.
Recommendations
- Provide Bash or shell script equivalents for all PowerShell commands, especially for az CLI operations.
- Use cross-platform file path examples in JSON templates (e.g., /home/user/schema.yaml) or clarify that paths must be adapted for Linux/macOS.
- Explicitly state whether the infra_onboarding.ps1 script is Windows-only, and offer a Linux-compatible onboarding script if possible.
- Add notes or sections for Linux/macOS users, highlighting any differences in setup or command usage.
- Where possible, show az CLI commands in Bash syntax (with line continuations using \) alongside PowerShell examples.
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 and features such as PowerShell scripting support, SQL Server Management Studio (SSMS), SQL Server Data Tools (SSDT), and Windows Authentication. PowerShell scripting is highlighted as a manageability feature, and Windows Authentication is listed as supported, but there is no mention of Linux/macOS equivalents or alternatives. The tools section lists several Windows-only or Windows-preferred tools, with no explicit mention of cross-platform or Linux-native tools (e.g., sqlcmd, Azure Data Studio).
Recommendations
- Add examples or references for Linux/macOS users, such as using sqlcmd or Azure Data Studio.
- Clarify which tools are cross-platform and which are Windows-only.
- Provide guidance for Linux/macOS users on authentication alternatives to Windows Authentication.
- Mention PowerShell Core (pwsh) support if available, or provide Bash scripting examples.
- Explicitly state tool/platform compatibility in the tools table.
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 focused on configuring AKS Edge Essentials on Linux, but uses Windows-centric tools and patterns. Specifically, it relies on the Invoke-AksEdgeNodeCommand PowerShell cmdlet for Linux node configuration, without providing native Linux shell alternatives. Notepad is mentioned as a text editor, and there is no guidance for Linux-native editing or command-line approaches. This creates friction for Linux users who may not have access to PowerShell or Windows tools.
Recommendations
- Provide native Linux shell command examples for checking and setting sysctl parameters (e.g., using 'sysctl' directly in bash).
- Replace or supplement Notepad references with Linux text editors (e.g., 'nano', 'vim', 'gedit').
- Clarify whether PowerShell is required on Linux, and if so, provide installation instructions or alternatives.
- Ensure all steps can be completed using standard Linux tools and commands, not just Windows/PowerShell-based ones.
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 tool recommendations that are Windows-centric, such as using SQL Server Management Studio (SSMS), Visual Studio Code, and specifying Windows file paths (e.g., C:\Backupfiles\test.bak). There are no explicit Linux/macOS equivalents or examples for backup/restore commands, file paths, or tool usage, and Windows paths and tools are presented first or exclusively.
Recommendations
- Add Linux/macOS examples for file paths (e.g., /home/user/Backupfiles/test.bak) alongside Windows examples.
- Mention cross-platform tools such as Azure Data Studio or command-line utilities (sqlcmd) that work on Linux/macOS, not just SSMS and Visual Studio Code.
- Clarify that Azure Storage Explorer and Visual Studio Code are cross-platform, and provide installation/use instructions for Linux/macOS.
- Provide explicit instructions or examples for Linux/macOS users, especially for backup/restore steps and kubectl cp usage.
- Where possible, avoid referencing Windows-only tools or paths exclusively, or provide parity for other platforms.
Azure Arc
Troubleshoot Azure Arc resource bridge issues
...re-arc/resource-bridge/troubleshoot-resource-bridge.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides troubleshooting guidance for Azure Arc resource bridge, which is a cross-platform solution. However, there are several instances of Windows bias: PowerShell is used for network troubleshooting examples (e.g., Invoke-WebRequest, Resolve-DnsName), Windows paths are referenced in error messages, and Windows-specific terminology (e.g., RDP, time.windows.com) appears. Linux equivalents (such as curl, dig, or nslookup) are not consistently provided alongside PowerShell examples. In some sections, Windows tools or patterns are mentioned first or exclusively, creating friction for Linux/macOS users.
Recommendations
- For every PowerShell example, provide a Linux/macOS equivalent (e.g., curl for Invoke-WebRequest, dig/nslookup for Resolve-DnsName).
- When referencing Windows paths or error messages, clarify Linux/macOS equivalents or note differences.
- Mention Linux/macOS troubleshooting steps and tools (e.g., SSH, terminal commands) alongside Windows instructions.
- Ensure that CLI commands (az arcappliance) are shown to work on both Windows and Linux, and note any OS-specific requirements.
- Where possible, avoid using Windows terminology (e.g., RDP) exclusively; mention SSH or console access for Linux/macOS.
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 both Windows and Linux instructions for all major agent lifecycle tasks (install, upgrade, uninstall, proxy configuration). However, Windows examples and tools (PowerShell, Group Policy, Microsoft Update, Control Panel, Registry Editor) are often presented first and in greater detail. Some automation scripts (e.g., stale resource cleanup) are only provided in PowerShell, with no Linux/bash equivalent. Windows-specific tools and patterns are referenced more frequently and with more explanation, while Linux instructions are concise and rely on standard package managers.
Recommendations
- Provide bash or Azure CLI scripts for resource cleanup and automation tasks, not just PowerShell.
- Ensure Linux instructions are as detailed as Windows instructions, including troubleshooting and automation options.
- When listing upgrade/uninstall methods, alternate the order or present Linux and Windows equally (not always Windows first).
- Add examples for managing agent lifecycle at scale on Linux (e.g., using Ansible, shell scripts, cron jobs).
- Where Windows tools (e.g., Group Policy, Control Panel) are described, consider mentioning Linux equivalents (e.g., systemd, configuration management tools) or clarifying their absence.
Azure Arc
How to migrate from legacy Log Analytics agents in non-Azure environments with Azure Arc
...in/articles/azure-arc/servers/migrate-legacy-agents.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation provides both Windows and Linux context, but Windows-specific tools and examples (PowerShell, Windows Admin Center, Windows Server Graphical Installer) are mentioned explicitly and before Linux equivalents. Deployment instructions reference PowerShell and Windows tools, but do not provide explicit Linux-focused examples or mention Linux-native tools (e.g., shell scripts, Linux package managers) in equal detail. Linux users may need to infer their deployment approach or consult external sources for parity.
Recommendations
- Add explicit Linux deployment examples alongside Windows ones, such as Bash scripts or instructions for using Linux package managers.
- Mention Linux-native tools (e.g., Ansible, shell scripting) with equal prominence as Windows tools.
- Provide sample commands for both Windows (PowerShell) and Linux (Bash) when referencing script-based deployment.
- Clarify that Azure Monitor Agent and Azure Arc support both Windows and Linux, and link to OS-specific guidance.
- Ensure that graphical deployment options for Linux (if any) are mentioned, or clarify their absence.
Azure Arc
Run command on Azure Arc-enabled servers (preview)
...cs/blob/main/articles/azure-arc/servers/run-command.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation provides extensive PowerShell examples and references to Windows tools (such as New-NetFirewallRule and New-AzStorageBlobSASToken), with Windows-centric scripting and REST API scenarios. Linux-specific examples are minimal or absent, and Linux scripting patterns (e.g., bash, shell, iptables) are not demonstrated. Windows terminology and tools are mentioned first or exclusively in several sections, especially in REST API and PowerShell tabs.
Recommendations
- Add Linux-specific script examples for Azure PowerShell and Azure CLI, such as using bash or shell scripts (e.g., 'echo Hello World!' or 'sudo apt update').
- Include REST API examples for Linux scenarios, such as configuring firewall rules with iptables or ufw.
- Balance PowerShell and CLI examples by showing both Windows and Linux script usage, and clarify OS-specific parameters or behaviors.
- Mention Linux tools and scripting patterns alongside Windows tools, and avoid referencing Windows tools exclusively unless the feature is Windows-only.
- In parameter explanations, provide Linux equivalents (e.g., for script file paths, show both Windows and Linux formats).
Azure Arc
Clean-Up Script for Workload Orchestration
...es/azure-arc/workload-orchestration/clean-up-script.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation exclusively provides instructions and examples for running a PowerShell script (RGCleanScript.ps1) to clean up Azure Arc workload orchestration resources. There are no examples or guidance for Linux/macOS users, such as using Bash, shell scripts, or cross-platform alternatives. The script appears to require PowerShell, which is traditionally Windows-centric, and no mention is made of running it on PowerShell Core (pwsh) or using Azure CLI directly.
Recommendations
- Clarify whether the script is compatible with PowerShell Core (pwsh) on Linux/macOS, and provide instructions for those platforms if so.
- If the script is Windows-only, explicitly state this limitation and suggest alternative clean-up methods for Linux/macOS users (e.g., using Azure CLI commands or providing a Bash version of the script).
- Add examples for running the script on Linux/macOS, or provide equivalent Bash/shell scripts.
- Mention cross-platform tools (like Azure CLI) and provide sample commands for resource clean-up.
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 guidance and script invocation. There are no equivalent Linux/macOS instructions for running the script, nor is it clarified whether the script can be run on Linux/macOS. Windows instructions are presented first and in greater detail, while Linux users are left without guidance for this critical step.
Recommendations
- Clarify whether the deboarding script can be run on Linux/macOS (e.g., via PowerShell Core or Azure CLI).
- If supported, provide explicit Linux/macOS instructions for downloading and running the script, including any prerequisites (such as PowerShell Core installation, script permissions, etc.).
- If the script is Windows-only, state this clearly and provide alternative manual steps or guidance for Linux/macOS users.
- Present Windows and Linux/macOS instructions in parallel sections or clearly label them to improve parity.
- Consider providing cross-platform script versions or tools if feasible.
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 (.ps1) for automation, without providing Bash or Linux/macOS equivalents. There are no explicit Linux/macOS examples or instructions, and the scripting guidance is Windows-centric, which may create friction for non-Windows users.
Recommendations
- Provide Azure CLI command examples in Bash syntax alongside PowerShell, especially since Azure CLI is cross-platform.
- Offer Bash shell script equivalents for bulk_deployment.ps1 and workflow-delete.ps1, or clarify if the scripts are compatible with Linux/macOS environments.
- Explicitly mention cross-platform compatibility for all CLI commands and scripts, and note any Windows-only limitations.
- Add notes or sections for Linux/macOS users, including any required adaptations or dependencies.
Azure Arc
Prepare the Environment for Workload Orchestration
...rc/workload-orchestration/initial-setup-environment.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation exhibits Windows bias in several areas. The example for installing kubectl uses 'winget', a Windows-only tool, without providing a Linux/macOS alternative. The file extraction example under the Bash tab uses 'Expand-Archive', which is a PowerShell/Windows command, not a Bash/Linux-native tool. There are no Linux/macOS equivalents (e.g., 'apt', 'brew', 'curl', 'unzip', 'tar') for these steps. Bash and PowerShell tabs are provided throughout, but Bash examples sometimes use Windows-specific commands. This creates friction for Linux/macOS users, especially in initial setup steps.
Recommendations
- Provide Linux/macOS installation instructions for kubectl (e.g., using curl, apt, brew).
- Replace 'Expand-Archive' in Bash examples with 'unzip' or 'tar' for Linux/macOS users.
- Ensure Bash examples use cross-platform commands, not Windows-specific ones.
- Add notes or tabs for macOS-specific instructions where relevant.
- Review all Bash sections to confirm they are valid for Linux/macOS environments.
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 alternatives or cross-platform scripting. This creates friction for non-Windows users, as PowerShell is not natively available on Linux/macOS and no Bash or platform-neutral instructions are provided.
Recommendations
- Provide a Bash or cross-platform script equivalent to WOGAMigration.ps1, or clarify if PowerShell Core (pwsh) can be used on Linux/macOS.
- Add explicit instructions for running the migration script on Linux/macOS, including any prerequisites (e.g., installing PowerShell Core).
- Mention whether the migration process is supported on non-Windows platforms, and if not, clarify the limitation.
- Consider offering a platform-neutral migration tool or Azure CLI-based alternative.
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 Windows/PowerShell usage. Most command-line examples are provided only in PowerShell syntax, even for tasks that are cross-platform (e.g., Azure CLI, Docker, kubectl). Bash/Linux equivalents are missing for critical steps, except in the 'service groups' section, which offers both Bash and PowerShell tabs. Windows/PowerShell commands are presented first and exclusively in most sections, creating friction for Linux/macOS users.
Recommendations
- Provide Bash/Linux shell equivalents for all PowerShell command examples, especially for Azure CLI, Docker, and kubectl commands.
- Where possible, use cross-platform syntax (e.g., Azure CLI commands without PowerShell-specific variable syntax).
- Ensure that file manipulation steps (e.g., Base64 encoding, JSON creation) are shown in both PowerShell and Bash.
- Review the order of examples to avoid always presenting Windows/PowerShell first.
- Clarify when a command is Windows-only, and offer alternatives for Linux/macOS users.
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 authentication examples for Azure Container Registry using both Azure CLI and Azure PowerShell, but PowerShell examples are prominent and appear alongside CLI examples throughout. Windows/PowerShell tools are mentioned frequently, and PowerShell is given equal or greater prominence to Azure CLI. There are no explicit Linux/macOS-specific examples or notes, and the CLI examples are generic (not showing Linux/macOS shell usage or nuances). The 'Next steps' section links only to Azure CLI and PowerShell guides, omitting Linux/macOS-specific workflows. While Docker and Podman are mentioned, Linux/macOS users may find the documentation slightly Windows-biased due to the prominence of PowerShell and lack of explicit Linux/macOS guidance.
Recommendations
- Add explicit Linux/macOS shell examples (e.g., bash/zsh) for authentication commands, especially for Azure CLI usage.
- Clarify that Azure CLI commands work cross-platform and provide any OS-specific nuances (such as environment variable syntax differences).
- Include links or sections for Linux/macOS getting started guides, not just Azure CLI and PowerShell.
- Balance PowerShell and CLI examples by showing CLI usage first, or by adding Linux/macOS-specific tabs.
- Mention common Linux tools (e.g., bash, sh) and provide guidance for their use with Azure Container Registry.
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides installation instructions for client tools across platforms, but Windows links are often listed first, and there are several Windows-specific notes (e.g., using cmd.exe instead of PowerShell for curl, and referencing PowerShell's curl alias). Linux installation instructions are less explicit (e.g., 'install curl package' without a link), and Linux/macOS examples are not always equally detailed. This creates minor friction for Linux/macOS users.
Recommendations
- List Linux/macOS installation links before or alongside Windows links to avoid Windows-first bias.
- Provide explicit installation instructions or links for Linux/macOS tools (e.g., for curl, link to official Linux/macOS installation guides).
- Clarify PowerShell-specific notes as Windows-only, and provide equivalent Linux/macOS guidance where relevant.
- Ensure all tool installation instructions are equally detailed for all platforms.
Azure Arc
Access Azure resources with managed identity on Azure Arc-enabled servers
...s/azure-arc/servers/managed-identity-authentication.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Windows (PowerShell) and Linux (Bash) examples for acquiring access tokens using managed identity on Azure Arc-enabled servers. However, the Windows/PowerShell example is presented first and in greater detail, including a screenshot, which may subtly prioritize Windows users. The 'Related content' section also mentions PowerShell before Azure CLI, which is more cross-platform.
Recommendations
- Present Windows and Linux examples in parallel or alternate which is shown first to avoid implicit prioritization.
- Ensure screenshots and example outputs are provided for both Windows and Linux, not just Windows.
- In 'Related content', mention Azure CLI before or alongside PowerShell to emphasize cross-platform tooling.
- Consider providing additional context or troubleshooting tips for Linux users, such as common permission issues.
Azure Arc
Delete Resources in Workload Orchestration
...s/azure-arc/workload-orchestration/delete-resources.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for all commands, but consistently lists Bash examples first. No Windows-specific tools or patterns are mentioned, and the Azure CLI is used throughout, which is cross-platform. There are no missing Linux examples, and no exclusive Windows tools or terminology. The only minor bias is the ordering of examples, with Bash (Linux/macOS) shown before PowerShell (Windows).
Recommendations
- Maintain Bash-first ordering, as it benefits Linux/macOS users and is industry standard.
- Ensure parity in explanations and options for both Bash and PowerShell.
- Consider clarifying that Azure CLI commands work identically on all platforms.
- No further action needed unless future updates introduce Windows-only tools or patterns.
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
windows_first
Summary
The documentation provides both Azure PowerShell and Azure CLI options for programmatic access to subscription and tenant IDs, but PowerShell is consistently mentioned before CLI. PowerShell is more commonly associated with Windows, while Azure CLI is cross-platform and often preferred by Linux/macOS users. No examples or instructions are exclusive to Windows, and both tools are referenced, but the ordering may subtly prioritize Windows users.
Recommendations
- Alternate the order in which Azure PowerShell and Azure CLI are mentioned, or mention Azure CLI first in at least some places to reflect its cross-platform nature.
- Explicitly note that both Azure PowerShell and Azure CLI are available on Windows, Linux, and macOS.
- Where possible, provide direct example commands for both tools, ensuring parity and clarity for all users.
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 is largely cross-platform, focusing on Helm and Azure CLI, which are available on Windows, Linux, and macOS. However, there are subtle signs of Windows bias: the environment variable example uses the Windows-style 'set' command instead of the cross-platform 'export', and the prerequisites list Azure PowerShell as an option before mentioning the Azure portal and Azure CLI. No explicit Linux/macOS-only examples are given, and the initial environment variable setup could confuse Linux/macOS users.
Recommendations
- Replace the 'set' command for environment variables with 'export' or provide both Windows ('set') and Unix ('export') examples.
- Ensure all CLI examples use syntax compatible with Bash/Zsh (e.g., variable assignment, quoting) or provide alternatives for Windows CMD/PowerShell where relevant.
- Clarify that Azure CLI and Helm are cross-platform and provide links or notes for Linux/macOS installation.
- When listing options (e.g., for creating AKS clusters), avoid putting Windows-specific tools (PowerShell) before cross-platform ones (Azure CLI).
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 primarily references SQL Server Management Studio (SSMS), a Windows-only tool, as the first example for connecting to SQL Managed Instance enabled by Azure Arc. While sqlcmd is mentioned and an example is provided for both Linux and Windows, SSMS is listed first and no Linux-native graphical client (such as Azure Data Studio or DBeaver) is mentioned. The documentation does not provide parity in client tool recommendations or examples for Linux/macOS users.
Recommendations
- Mention cross-platform SQL client tools such as Azure Data Studio or DBeaver alongside SSMS.
- Provide explicit examples for connecting using sqlcmd on Linux/macOS, including any authentication or encoding nuances.
- List Linux/macOS tools and examples before or alongside Windows tools, not after.
- Clarify that SSMS is Windows-only and suggest alternatives for Linux/macOS users.
Azure Arc
Rotate user-provided TLS certificate in indirectly connected SQL Managed Instance enabled by Azure Arc
...articles/azure-arc/data/rotate-user-tls-certificate.md
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation provides both Linux and Windows methods for base64 encoding files when creating Kubernetes secrets. The Linux example (using 'base64') is given first, followed by Windows-specific instructions using 'certutil' and 'findstr'. There is a minor bias in mentioning Windows tools and patterns, but Linux parity is maintained throughout the guide. All critical steps are covered for both platforms.
Recommendations
- Explicitly mention macOS compatibility for the 'base64' command, as it works similarly to Linux.
- Provide PowerShell alternatives for Windows users (e.g., using '[Convert]::ToBase64String') to increase accessibility.
- Clarify that all Azure CLI and kubectl commands are cross-platform and can be run on Windows, Linux, and macOS.
- Consider grouping Linux/macOS and Windows instructions separately for clarity.
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 between Windows and Linux for most aspects of Azure Arc-enabled server connectivity. However, Windows-specific tools (Windows Admin Center) and resources are mentioned before their Linux equivalents, and Windows installation/download URLs are listed first in tables. Some sections, such as cryptographic protocol configuration, focus on Windows-specific guidance and troubleshooting, with Linux guidance being less detailed or referenced externally. Overall, Linux users can complete the tasks, but Windows is subtly prioritized.
Recommendations
- Present Windows and Linux examples/resources side-by-side or in parallel, rather than listing Windows first.
- Expand Linux-specific guidance, such as TLS configuration and troubleshooting, to match the detail provided for Windows.
- Where Windows tools (e.g., Windows Admin Center) are mentioned, clarify Linux alternatives or note their applicability.
- Ensure tables and lists alternate or group Windows and Linux resources equally.
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 references Azure CLI installation with a link that defaults to Windows instructions and mentions Azure CLI x64/32-bit requirements, but does not specify Linux/macOS compatibility or provide explicit guidance for those platforms. No Linux/macOS-specific examples or clarifications are given, and the management machine requirements section links to Windows installation first. However, the overall content is not Windows-specific and the Azure CLI is cross-platform.
Recommendations
- Add explicit mention that Azure CLI is supported on Linux and macOS, and provide links to Linux/macOS installation instructions alongside the Windows link.
- Clarify that the management machine can be Windows, Linux, or macOS, and specify any platform-specific requirements if applicable.
- Include example commands or screenshots for Linux/macOS where relevant, especially for CLI usage.
- Ensure parity in documentation structure so Linux/macOS users are not left to infer compatibility.
Azure Arc
Customer intent: "As a network administrator, I want to configure outbound and inbound connectivity settings for the appliance VM and management machine, so that I can ensure smooth communication and functionality for the Arc resource bridge."
...e-arc/resource-bridge/includes/network-requirements.md
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation includes references to Windows-specific tools and services, such as 'time.windows.com' for NTP and 'sts.windows.net' for Custom Location. Windows NTP is mentioned explicitly, and Windows-related endpoints (e.g., 'login.windows.net', 'servicebus.windows.net') are listed. However, Linux-specific endpoints and tools are also referenced, such as 'packages.microsoft.com' for Linux installation packages and 'linuxgeneva-microsoft.azurecr.io' for log collection. The examples and instructions do not exclusively focus on Windows, but Windows endpoints and terminology appear first or more prominently in some cases.
Recommendations
- Clarify that NTP can use either Windows or Linux NTP servers, and provide Linux NTP server examples (e.g., 'pool.ntp.org').
- Ensure parity in endpoint descriptions by mentioning Linux equivalents where relevant (e.g., for authentication or time sync).
- Review the order of endpoint listings to avoid consistently placing Windows-specific endpoints first unless required by technical order.
- Add explicit notes for cross-platform compatibility, especially for management machines that may run Linux or macOS.
- Where possible, provide Linux/macOS command-line examples or references alongside Windows/PowerShell instructions.
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 generally provides parity between Windows and Linux, offering error codes, exit codes, and troubleshooting steps for both platforms. However, there is a mild Windows bias: Windows log file paths and PowerShell command syntax are presented before Linux equivalents in some sections, and Windows-specific tools (e.g., PowerShell, Windows environment variables) are referenced. Linux examples are present and clear, but Windows examples are shown first in the verbose logging section, and Windows-specific troubleshooting details (e.g., PowerShell version requirements, log file locations) are mentioned before Linux equivalents.
Recommendations
- Alternate the order of Windows and Linux examples so Linux is not always second.
- Where possible, present Windows and Linux commands side-by-side for easier comparison.
- Ensure Linux troubleshooting steps and log file locations are given equal prominence and detail.
- Explicitly mention Linux prerequisites and permissions in all relevant sections, not just in notes.
- Consider adding a summary table of key paths and commands for both platforms at the top of the troubleshooting section.
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/PowerShell are mentioned first in several places (e.g., runbooks, onboarding tabs), and some links default to Windows-specific tabs or examples. Azure Automation is described with a PowerShell-first perspective, and some linked guides and features (like Windows Server management, ESUs) are Windows-centric, though this is expected for those features. Linux is supported and mentioned, but often as a secondary consideration.
Recommendations
- When referencing automation (e.g., Azure Automation runbooks), explicitly mention both PowerShell and Bash/Python equally, and provide links/examples for both platforms.
- Where documentation links default to Windows tabs or examples, add parallel links or clarify Linux/macOS support.
- In lists of supported tools or interfaces (e.g., CLI, PowerShell, SDKs), avoid always listing PowerShell before CLI or SDKs; alternate order or clarify cross-platform parity.
- For configuration and monitoring features, ensure Linux-specific capabilities and limitations are clearly documented alongside Windows.
- Add more explicit Linux/macOS examples or callouts where relevant, especially in onboarding and automation scenarios.
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 'Recovering from failed deployments' sections. There are minor Windows-first ordering and a PowerShell-specific troubleshooting note, but Linux parity is maintained throughout.
Recommendations
- Present Windows and Linux instructions in parallel or alternate their order to avoid Windows-first bias.
- Add any Linux-specific troubleshooting notes if relevant (e.g., shell compatibility, permissions).
- Ensure screenshots and UI references are OS-neutral or clarify if they are Windows-specific.
- Explicitly mention macOS support if the Bash script works on macOS, or clarify its limitations.
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. While most features are platform-neutral or explicitly mention both Windows and Linux, there are minor signs of Windows bias: Windows VM customization is mentioned before Linux, Windows Server Management is highlighted, and Windows tools like Azure PowerShell are listed before Linux equivalents (Azure CLI). However, Linux support is also referenced (e.g., Arc agent installation on Linux via SSH, Ansible playbook), and most features are not OS-specific.
Recommendations
- Ensure Linux and Windows examples are presented together or alternate their order.
- When listing tools, consider mentioning cross-platform tools (Azure CLI, Ansible) before Windows-specific ones (PowerShell, Group Policy).
- Add explicit Linux/macOS guidance where only Windows tools are referenced (e.g., System Center Configuration Manager, Group Policy).
- Highlight Linux-specific features or improvements when relevant.
Azure Arc
External Validation for Workload Orchestration
...zure-arc/workload-orchestration/external-validation.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for all CLI operations, ensuring parity for Linux/macOS and Windows users. However, in several sections, PowerShell examples are presented immediately after Bash, rather than alternating or giving equal prominence. There are no Windows-only tools or patterns, and all instructions use the Azure CLI, which is cross-platform. No Linux/macOS-specific examples or troubleshooting are missing.
Recommendations
- Consider alternating the order of Bash and PowerShell examples in each section, or explicitly state that Bash is suitable for Linux/macOS and PowerShell for Windows.
- Add a brief note clarifying that Azure CLI commands work identically on Linux, macOS, and Windows, and that Bash examples are intended for Linux/macOS users.
- If relevant, provide troubleshooting tips for Linux/macOS environments (e.g., shell quoting, file path differences).
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 every CLI operation, ensuring parity for Linux/macOS and Windows users. However, in most sections, Bash examples are presented before PowerShell, which is a minor bias in favor of Linux/macOS users rather than Windows. No Windows-only tools, patterns, or terminology are used, and all instructions are cross-platform. There are no missing Linux examples, nor are Windows tools mentioned exclusively or before their Linux equivalents.
Recommendations
- No action needed for Linux parity. If desired, alternate the order of Bash and PowerShell tabs in different sections to further balance presentation.
- Continue to ensure all CLI instructions are available for both Bash and PowerShell.
- Explicitly mention that the Azure CLI is cross-platform and works on Windows, Linux, and macOS.
Azure Arc
Release Notes for Workload Orchestration
...cles/azure-arc/workload-orchestration/release-notes.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides release notes for Azure Arc Workload Orchestration, with CLI examples predominantly using Bash syntax. However, in the May 2025 release section, PowerShell syntax is used for CLI examples, which may suggest a Windows-first bias. No Windows-specific tools or patterns are mentioned, and Linux equivalents are generally present via Bash examples elsewhere. The overall impact is minor, as the Azure CLI is cross-platform and the examples are mostly generic.
Recommendations
- Ensure all CLI examples are provided in both Bash and PowerShell syntax, or clarify that the Azure CLI commands work identically across Windows, Linux, and macOS.
- Where PowerShell syntax is used, add a Bash equivalent for Linux/macOS users.
- Consider standardizing CLI examples to Bash unless the feature is Windows-specific, or provide both syntaxes side-by-side.
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for every step, but consistently presents Bash examples first. There are no Windows-specific tools or patterns, and all commands use the Azure CLI and Helm, which are cross-platform. No Linux examples are missing, and there is no exclusive mention of Windows tools.
Recommendations
- Consider alternating the order of Bash and PowerShell examples, or explicitly state that Bash is suitable for Linux/macOS and PowerShell for Windows.
- Add a brief note clarifying that Bash examples are intended for Linux/macOS environments and PowerShell for Windows, to help users quickly identify which section is relevant.
- Ensure parity in variable naming and file path conventions between Bash and PowerShell examples (e.g., use forward slashes in Bash, backslashes in PowerShell).
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 most sections, Bash examples are presented before PowerShell, which is a minor bias in favor of Linux/macOS users (not Windows). No evidence of Windows bias such as PowerShell-only examples, Windows tools, or Windows-first ordering was found.
Recommendations
- Maintain the current structure with both Bash and PowerShell examples.
- If desired, alternate the order of Bash and PowerShell tabs in different sections to further balance presentation.
- Explicitly mention that both Linux/macOS and Windows are supported for all steps.
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
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for importing images into Azure Container Registry. The Azure CLI example is presented first, which is cross-platform and suitable for Linux/macOS users. Azure PowerShell, which is Windows-centric, is also included. No Linux-specific tools or shell examples (e.g., Bash scripts, curl, docker CLI) are given, but the Azure CLI is the recommended and primary cross-platform tool. There is a minor bias in listing Azure PowerShell as an equal alternative, but no critical Windows bias is present.
Recommendations
- Clarify that Azure CLI is fully cross-platform and recommended for Linux/macOS users.
- Consider adding a brief Bash shell or Docker CLI example for importing images, if relevant.
- Explicitly state that Azure PowerShell is primarily for Windows users, and that Linux/macOS users should use Azure CLI.
- Add a note that Azure Cloud Shell supports both CLI and PowerShell, but CLI is more universal.
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, PowerShell examples are consistently shown after Bash examples, which is a minor 'windows_first' bias. No Windows-exclusive tools or patterns are used, and all commands are cross-platform (Azure CLI, Helm).
Recommendations
- Continue to provide both Bash and PowerShell examples for all steps.
- Consider alternating the order of Bash and PowerShell tabs, or explicitly state that both are equally supported.
- Add a note clarifying that all examples are cross-platform and can be run on Linux, macOS, or Windows (with Bash or PowerShell).
Azure Arc
Solution with Multiple Shared Dependencies at Different Hierarchy Levels
...oad-orchestration/tutorial-service-group-scenario-3.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Bash and PowerShell examples for every step, ensuring cross-platform parity. However, PowerShell examples are present throughout, which may be unnecessary for Linux/macOS users, and in some sections, PowerShell examples are shown immediately after Bash, potentially giving Windows users slightly more prominence. No Windows-specific tools or patterns are used, and Linux examples are not missing. The Azure CLI and Helm are used, both of which are cross-platform.
Recommendations
- Consider clarifying that PowerShell examples are primarily for Windows users, while Bash is for Linux/macOS.
- If possible, add a note at the top of each code section indicating which OS the example is intended for.
- Ensure Bash examples are always shown first, as is currently the case.
- Optionally, provide a single cross-platform example (Bash) for steps where PowerShell does not add meaningful value.
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 deployment instructions for Azure dashboards using three methods: Azure portal, Azure CLI, and Azure PowerShell. While Azure CLI is cross-platform and presented before PowerShell, the PowerShell section is included and detailed, which may be unnecessary for Linux/macOS users. Additionally, PowerShell is mentioned in the overview alongside Azure CLI and REST API, but no Linux/macOS-specific shell examples (such as Bash scripting) are provided. The order of examples sometimes places Windows/PowerShell content before Linux alternatives, and PowerShell is given its own section, which could be perceived as Windows-first bias.
Recommendations
- Clarify that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
- Consider adding Bash shell scripting examples for template deployment, or explicitly note that Azure CLI commands can be run in Bash, zsh, etc.
- Reorder sections so that cross-platform tools (Azure CLI, REST API) are always presented before Windows-specific tools (PowerShell).
- Explicitly state that PowerShell is primarily for Windows users, and that Linux/macOS users should use Azure CLI or REST API.
Azure Portal
Use Azure Copilot with the Azure mobile app
...main/articles/azure-portal/mobile-app/azure-copilot.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation mentions 'Generating CLI and PowerShell scripts' as a key scenario, listing PowerShell alongside CLI. While Azure CLI is cross-platform, PowerShell is often associated with Windows, and listing it explicitly may suggest a Windows bias. No Linux-specific tools (such as Bash) are mentioned, and PowerShell is referenced before any Linux shell equivalents.
Recommendations
- Clarify that Azure CLI is cross-platform and works on Linux, macOS, and Windows.
- Mention Bash or shell script generation as a capability, if supported by Azure Copilot.
- Ensure examples and scenarios include Linux/macOS tools where relevant, not just PowerShell.
- Consider listing CLI and Bash before PowerShell to avoid Windows-first ordering.
Container Registry
Push & Pull Container Image using Azure Container Registry
...-registry/container-registry-get-started-docker-cli.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell authentication and image removal examples, but PowerShell is given equal prominence to CLI, and Windows-specific PowerShell commands are included throughout. The instructions for stopping containers reference 'Ctrl+C', which is Windows-centric, and PowerShell is mentioned as a recommended method for authentication and image removal, potentially creating friction for Linux/macOS users. However, Docker CLI commands are cross-platform and the page does link to Linux/macOS Docker installation guides.
Recommendations
- Clarify that PowerShell examples are primarily for Windows users and provide Bash or shell equivalents for Linux/macOS where PowerShell is used.
- When referencing keyboard shortcuts, include macOS/Linux equivalents (e.g., 'Ctrl+C or Cmd+C').
- Consider listing Azure CLI (cross-platform) examples before PowerShell, or explicitly state that PowerShell is for Windows environments.
- Add a note that Azure PowerShell is available on Linux/macOS, but Bash/CLI is more common for those platforms.
- Ensure parity by including any Linux/macOS-specific tips or troubleshooting steps, if applicable.
Container Registry
Quickstart - Create Registry - Bicep
...ainer-registry/container-registry-get-started-bicep.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell deployment instructions, but PowerShell is mentioned alongside CLI in the main deployment section and is given its own example. The instructions for opening a terminal reference Visual Studio Code and a Windows-specific keyboard shortcut (ctrl + `), which may not be universal. There are no Linux-specific examples or explicit mentions of Linux/macOS tools, and PowerShell is presented as a primary option, which may create friction for Linux/macOS users.
Recommendations
- Explicitly mention that Azure CLI works cross-platform (Windows, Linux, macOS) and is recommended for Linux/macOS users.
- Provide Linux/macOS-specific instructions for opening a terminal (e.g., Terminal app, bash, zsh) instead of only referencing Visual Studio Code and Windows shortcuts.
- Consider listing Azure CLI instructions before PowerShell, as CLI is more universally available.
- Add a note clarifying that PowerShell examples are for Windows users, and Linux/macOS users should use Azure CLI.
- Include sample commands for bash/zsh where relevant, or clarify that Azure CLI commands are shell-agnostic.
Container Registry
Quickstart - Create Registry in Portal
...iner-registry/container-registry-get-started-portal.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell options for signing in to the registry, but Azure PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI. However, both tools are cross-platform, and Docker installation instructions are provided for Mac, Windows, and Linux. No Windows-only tools or patterns are used, and Linux parity is generally maintained.
Recommendations
- Consider clarifying that Azure PowerShell is available cross-platform, not just on Windows.
- If possible, mention Bash or shell scripting as alternatives for Linux/macOS users, especially in sections where PowerShell is referenced.
- Ensure that any screenshots or portal instructions are not Windows-specific (e.g., avoid referencing Windows UI elements unless necessary).
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 operations 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 cross-platform options. There are no Linux/macOS-specific tools or shell examples (e.g., Bash scripts), and the CLI is not explicitly highlighted as the primary cross-platform method.
Recommendations
- Emphasize Azure CLI as the primary, cross-platform example for command-line operations.
- List Azure CLI examples before PowerShell, and clarify that CLI works on Windows, Linux, and macOS.
- Consider adding Bash or shell script examples where appropriate, or explicitly mention that Azure CLI commands work in Bash, PowerShell, and CMD.
- Where PowerShell is shown, clarify that it is optional and primarily for users who prefer it.
- Ensure REST API examples are presented as a platform-neutral alternative where relevant.
Container Registry
Import Container Images to ACR using Azure APIs
...container-registry/container-registry-import-images.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides parallel examples for both Azure CLI and Azure PowerShell throughout, but PowerShell is featured equally and sometimes before Azure CLI. There are no explicit Windows-only tools or commands, but PowerShell is a Windows-centric shell, and its inclusion as a primary example may create friction for Linux/macOS users. However, Azure CLI is cross-platform and all tasks can be completed using it, with no missing Linux examples.
Recommendations
- Make clear that Azure PowerShell is primarily for Windows users, while Azure CLI is cross-platform.
- Consider listing Azure CLI examples first in each section, as it is more universally accessible.
- Add a note at the top clarifying that all tasks can be completed using Azure CLI on Linux/macOS, and PowerShell is optional.
- If possible, provide Bash shell script examples for common tasks, or clarify that Azure CLI commands can be run in Bash.
- Ensure that troubleshooting and prerequisite sections do not assume PowerShell usage.