Azure Arc
465
Total Pages
253
Linux-Friendly Pages
212
Pages with Bias
45.6%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
2334 issues found
Showing 1926-1950 of 2334 flagged pages
Azure Arc
Troubleshoot Azure Connected Machine agent connection issues
...ticles/azure-arc/servers/troubleshoot-agent-onboard.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation provides troubleshooting guidance for both Windows and Linux, but there are minor signs of Windows bias. Windows log file paths and PowerShell-style command syntax are mentioned first in some sections. Windows examples are presented before Linux examples in the verbose log section. References to Windows-specific tools (e.g., PowerShell, Windows environment variables) are present, but Linux equivalents are also included. Overall, Linux parity is maintained, but Windows is subtly prioritized in ordering and terminology.
Recommendations
- Present Linux and Windows examples in parallel or alternate order to avoid implicit prioritization.
- Where possible, use neutral language and paths (e.g., mention both `%ProgramData%` and `/var/opt/` together).
- Ensure troubleshooting steps reference both Windows and Linux tools equally (e.g., log locations, commands).
- Add explicit notes clarifying Linux requirements (e.g., root access, sudo usage) where relevant.
- Consider including a summary table of key differences between Windows and Linux troubleshooting steps.
Create Pull Request
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 Linux and Windows in most sections, including explicit mention of Linux and Windows installation URLs and agent support. However, there are minor indications of Windows bias: Windows installation URLs are listed before Linux in tables, and Windows-specific tools (Windows Admin Center) are referenced in service tags and endpoint descriptions, sometimes without Linux equivalents or alternatives. The cryptographic protocol section gives Windows-specific troubleshooting links and registry settings, while Linux is referenced generically via OpenSSL. Overall, Linux users can complete the task without significant friction.
Recommendations
- List Linux installation URLs before or alongside Windows URLs in tables to avoid 'windows_first' bias.
- When referencing Windows Admin Center, clarify Linux alternatives or state if no equivalent exists.
- Provide Linux-specific troubleshooting resources for TLS configuration (e.g., OpenSSL guides) alongside Windows links.
- Ensure that examples and descriptions are balanced between Linux and Windows, especially in sections about agent installation and network configuration.
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
Powershell Heavy
Windows First
Summary
The documentation page presents Azure CLI, PowerShell, and REST API as supported experiences, but PowerShell is mentioned alongside Azure CLI in both metadata and main text, suggesting a Windows-centric approach. There is no explicit Linux shell example or mention of Bash, and PowerShell is listed before REST API and Linux-specific notes are minimal. The page does state Run command supports both Windows and Linux, but the focus on PowerShell and lack of Linux shell examples creates a mild Windows bias.
Recommendations
- Add explicit Bash or Linux shell examples alongside PowerShell examples in the main documentation.
- Mention Linux shell usage (e.g., Bash, sh) in the 'Experiences' section to clarify parity.
- Ensure that Linux-specific limitations (like the name length restriction) are highlighted equally with any Windows-specific notes.
- Consider listing Azure CLI and Bash examples before PowerShell to balance the order.
- Link to Linux-specific usage guides or troubleshooting if available.
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 is generally cross-platform in its descriptions and intent, but there are several instances where Windows-specific tools, examples, or references are mentioned before or more prominently than their Linux equivalents. PowerShell and Windows-centric tools are referenced in automation and configuration scenarios, and some links default to Windows tabs or examples. Linux support is mentioned, but often after Windows, and Linux-specific examples or guidance are less detailed or absent.
Recommendations
- Ensure that all automation and configuration examples (e.g., Azure Automation, onboarding, agent installation) provide both Windows and Linux command-line or script examples, not just PowerShell or Windows-centric instructions.
- When referencing tools or features (such as Azure Automation runbooks or Update Manager), explicitly mention and link to Linux documentation or provide Linux-specific tabs/examples alongside Windows ones.
- In lists or feature descriptions, avoid always listing Windows first; alternate or clarify that features apply equally to Linux and Windows where appropriate.
- Where links default to Windows tabs (e.g., Windows Server management), ensure Linux tabs are equally visible or provide direct links to Linux guidance.
- Add Linux-focused scenarios or callouts where relevant, especially in sections about configuration, monitoring, and agent deployment.
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 a few instances where Windows-related features (such as customizing guest OS settings for Windows VMs and Windows Server Management) are listed before Linux equivalents or Linux-specific enhancements. Additionally, Windows tools like System Center Configuration Manager and Group Policy are mentioned as methods for installing Arc agents at scale, with Linux tools (Ansible) appearing later in the list. However, Linux support is also referenced (e.g., SSH-based agent installation, Ansible playbook), and most features are not OS-specific.
Recommendations
- When listing tools or methods for agent installation, group Windows and Linux options together or alternate their order to avoid implicit prioritization.
- Explicitly mention Linux equivalents for Windows tools where possible (e.g., highlight Ansible, Puppet, Chef alongside SCCM and Group Policy).
- Ensure that Linux-related enhancements (such as guest OS customization) are given equal prominence and detail as Windows features.
- Consider adding links or references to Linux documentation/examples where Windows-specific features are discussed, if Linux alternatives exist.
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 each section, PowerShell examples are consistently shown after Bash, which is a minor 'windows_first' bias. No Windows-specific tools, patterns, or terminology are used, and all instructions are cross-platform via Azure CLI. There are no missing Linux examples or Windows-only tools mentioned.
Recommendations
- Continue to provide both Bash and PowerShell examples for all CLI operations.
- Consider clarifying that Azure CLI commands are fully cross-platform and can be run on Windows, Linux, and macOS.
- Optionally, rotate the order of Bash and PowerShell tabs or explicitly state that Bash is for Linux/macOS and PowerShell for Windows, to reinforce parity.
- Add a brief note at the start indicating that all CLI instructions are compatible with Linux, macOS, and Windows.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples for all commands, but PowerShell examples are presented after Bash. There are no Windows-specific tools or patterns mentioned, and all commands use the cross-platform Azure CLI. No Linux/macOS examples are missing, and the content is not Windows-centric.
Recommendations
- Continue to provide both Bash and PowerShell examples for parity.
- Consider explicitly stating that Bash examples are suitable for Linux/macOS and PowerShell for Windows, to help users choose the right tab.
- Ensure that any future additions (e.g., troubleshooting, environment setup) include Linux/macOS guidance where relevant.
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 between Linux/macOS and Windows users. However, PowerShell examples are consistently presented after Bash examples, indicating a minor 'windows_first' bias. There are no Windows-specific tools or patterns used exclusively, and Linux/macOS users can complete all tasks without friction.
Recommendations
- Continue to provide both Bash and PowerShell examples for all steps.
- Consider alternating the order of Bash and PowerShell tabs in some sections, or clarify that Bash is suitable for Linux/macOS and PowerShell for Windows.
- Explicitly mention that Bash examples are intended for Linux/macOS users and PowerShell for Windows users, to avoid confusion.
- Ensure that any OS-specific nuances (such as file encoding or base64 commands) are clearly explained for both platforms.
Azure Arc
Release Notes for Workload Orchestration
...cles/azure-arc/workload-orchestration/release-notes.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page provides CLI examples primarily in PowerShell syntax, particularly in the May 2025 release section. While most CLI instructions use Bash syntax, the only explicit code samples for setting and downloading configurations are in PowerShell, and Bash equivalents are missing. The overall structure does not mention Windows tools or patterns exclusively, but the ordering and example choice suggest a mild Windows bias.
Recommendations
- Provide Bash equivalents for all PowerShell CLI examples, especially for configuration set and download commands.
- Ensure that CLI instructions are presented in a cross-platform manner, using generic syntax or offering both Windows (PowerShell) and Linux/macOS (Bash) versions.
- Add clarifying notes that Azure CLI commands work on all platforms and highlight any OS-specific differences if present.
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 shown before PowerShell, which is a minor 'windows_first' bias in ordering. No Windows-only tools or patterns are used, and all commands are cross-platform (az 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 Bash is for Linux/macOS and PowerShell is for Windows to clarify intent.
- Ensure that any future additions (e.g., troubleshooting, environment setup) include Linux/macOS guidance if Windows-specific instructions are added.
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 the PowerShell examples are always shown after Bash. There are no Windows-only tools or patterns, and all commands use the Azure CLI and Helm, which are cross-platform. However, the PowerShell examples are present throughout, which may suggest a slight bias toward Windows users, but Linux/macOS users are fully supported. No critical Linux/macOS gaps are present.
Recommendations
- Consider adding a note clarifying that Bash examples are suitable for Linux/macOS and Windows (via WSL or Git Bash), while PowerShell is for Windows users.
- Ensure that Bash and PowerShell tabs are equally prominent and that Bash is not implicitly treated as secondary.
- If possible, provide guidance for running Bash scripts on Windows (e.g., using WSL or Git Bash) for parity.
- Explicitly state that all CLI commands are cross-platform and supported on Linux/macOS.
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.