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 2201-2225 of 2334 flagged pages
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
Powershell Heavy
Summary
The documentation generally provides both Windows and Linux information for each release, including download links and feature parity tables. However, there is a consistent pattern of listing Windows before Linux in download links, tables, and feature descriptions. Some instructions and troubleshooting notes reference Windows-specific tools (e.g., PowerShell, msiexec) without equivalent Linux examples. Occasional improvements or bug fixes are described only for Windows (e.g., installer GUI, PATH variable), and troubleshooting steps for Linux are absent.
Recommendations
- Alternate the order of Windows and Linux in download links and tables, or present them side-by-side to avoid implicit prioritization.
- When referencing Windows-specific tools or commands (e.g., PowerShell, msiexec), provide equivalent Linux commands (e.g., bash, rpm, systemctl) where applicable.
- Include troubleshooting steps and known issues for Linux where relevant, not just for Windows.
- Ensure that Linux-specific improvements or bug fixes are described with the same detail as Windows ones.
- Where features or fixes are Windows-only, clearly label them as such, and do the same for Linux-only items.
Create Pull Request
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
Powershell Heavy
Windows Tools
Summary
The release notes for the Azure Connected Machine agent generally provide parity between Windows and Linux, with most features and fixes listed for both platforms. However, there is a mild Windows bias: Windows download links and version numbers are consistently listed before Linux, and troubleshooting guidance (e.g., installer issues) references Windows tools and patterns (PowerShell, Command Prompt, msiexec) without Linux equivalents. Some improvements and bug fixes are described only for Windows (e.g., GUI accessibility, installer service configuration), and PowerShell scripts are mentioned without Linux shell alternatives.
Recommendations
- Alternate the order of Windows and Linux download links and version numbers, or present them together where possible.
- Where troubleshooting steps are given for Windows (e.g., using msiexec, PowerShell), provide equivalent Linux instructions (e.g., using rpm, dpkg, systemctl, or shell commands).
- When mentioning platform-specific scripts (e.g., ExtensionCleanup.ps1), clarify if there are Linux equivalents or note their absence.
- Explicitly state when a fix or feature is Windows-only or Linux-only, and provide context for platform differences.
- Consider including a summary table at the top showing parity and platform-specific changes for quick reference.
Azure Arc
CLI reference for `azcmagent connect`
...b/main/articles/azure-arc/servers/azcmagent-connect.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation for `azcmagent connect` demonstrates mild Windows bias in several areas. Windows authentication options are described first, and Windows-specific certificate store usage is detailed before Linux equivalents. The only explicit tooling example for obtaining an access token references PowerShell (`Get-AzAccessToken`), with no Linux or cross-platform alternatives given. However, Linux usage is generally supported and described, and most examples are OS-neutral.
Recommendations
- When mentioning authentication options, present Linux and Windows defaults together or alternate which is described first.
- For access token acquisition, provide a cross-platform Azure CLI example (e.g., `az account get-access-token`) alongside the PowerShell example.
- Clarify certificate handling for Linux (e.g., where to store PEM/PFX files, recommended permissions) in parallel with Windows certificate store details.
- Explicitly state that all examples work on both Windows and Linux unless otherwise noted, and highlight any OS-specific flags or behaviors.
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
Powershell Heavy
Windows Tools
Summary
The release notes for the Azure Connected Machine agent generally provide parity between Windows and Linux, listing features and fixes for both platforms. However, there is a mild Windows bias: Windows download links and version numbers are consistently listed before Linux, Windows installer issues and troubleshooting steps (e.g., UAC, PowerShell, msiexec) are described in detail, and Windows tools (PowerShell, Command Prompt) are referenced without Linux equivalents. Some improvements or fixes are Windows-only, but Linux-only changes are also noted. No critical functionality appears to be Windows-exclusive, and Linux users can access all major agent features.
Recommendations
- Alternate the order of Windows and Linux in tables and download links, or present them side-by-side.
- When describing installer troubleshooting, include equivalent Linux installation/upgrade troubleshooting steps (e.g., using rpm, dpkg, systemctl).
- Reference Linux tools (e.g., Bash, systemctl, rpm) alongside Windows tools when discussing installation or configuration.
- Ensure that any platform-specific improvements are clearly labeled as such, and provide parity in detail for both platforms.
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
Powershell Heavy
Windows Tools
Summary
The release notes for the Azure Connected Machine agent generally provide parity between Windows and Linux, listing features, fixes, and improvements for both platforms. However, there is evidence of mild Windows bias: Windows download links and version numbers are consistently listed before Linux, installer troubleshooting focuses on Windows (with PowerShell/Command Prompt instructions), and some improvements reference Windows tools (e.g., .ps1 scripts, msiexec). Linux-specific issues and enhancements are present, but Windows patterns and terminology are more prominent.
Recommendations
- Alternate the order of Windows and Linux download links and version numbers to avoid implicit prioritization.
- Include Linux installer troubleshooting steps and common commands (e.g., rpm, dpkg, systemctl) alongside Windows instructions.
- Where Windows tools/scripts are mentioned (e.g., ExtensionCleanup.ps1), clarify if Linux equivalents exist or note their absence.
- Ensure that bug fixes and improvements for both platforms are described with equal detail and visibility.
Azure Arc
CLI reference for `azcmagent connect`
...b/main/articles/azure-arc/servers/azcmagent-connect.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation exhibits mild Windows bias in several areas. Windows authentication options are described first, and Windows-specific certificate store usage is detailed before Linux equivalents. The only explicit tooling reference for obtaining an access token is the PowerShell Get-AzAccessToken cmdlet, with no Linux/macOS alternative (e.g., Azure CLI) mentioned. However, most examples and instructions are cross-platform, and Linux authentication flows are described.
Recommendations
- In the 'Access token' section, add an example for obtaining an access token using Azure CLI (e.g., 'az account get-access-token') for Linux/macOS users.
- When describing authentication options, avoid listing Windows-only methods first unless they are truly the most common. Consider grouping cross-platform methods together or clarifying platform applicability.
- For certificate-based authentication, provide Linux/macOS instructions (e.g., storing PEM/PFX files in a secure directory) alongside Windows certificate store instructions.
- Where Windows-specific tooling or patterns are mentioned, offer Linux/macOS equivalents in parallel.
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 generally provides parity between Windows and Linux, with separate download links and clear indication of OS-specific changes. However, Windows is often listed first in download links, tables, and feature descriptions. Some installer troubleshooting and feature improvements reference Windows tools (e.g., PowerShell, msiexec) without equivalent Linux guidance. There are a few Windows-only improvements, but these are appropriately marked.
Recommendations
- Alternate the order of Windows and Linux in download links and tables, or list alphabetically to avoid implicit prioritization.
- Where troubleshooting or installation steps reference Windows tools (e.g., PowerShell, msiexec), provide equivalent Linux commands (e.g., shell commands for .rpm/.deb packages) or link to Linux installation guidance.
- Ensure that any OS-specific improvements or bug fixes are clearly labeled, as is already done.
- Consider adding a brief section or link to Linux-specific troubleshooting tips, mirroring the Windows installer guidance.
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
Powershell Heavy
Windows Tools
Summary
The release notes for the Azure Connected Machine agent generally provide parity between Windows and Linux, listing features and fixes for both platforms. However, there is a consistent pattern of Windows being mentioned first in download links, tables, and installer instructions. Windows-specific tools (PowerShell, msiexec, GUI) are referenced directly, while Linux equivalents (shell, RPM, systemctl) are mentioned less frequently or only in the context of Linux-only fixes. Some installation guidance and troubleshooting steps are Windows-centric, with no parallel Linux instructions provided.
Recommendations
- Alternate the order of Windows and Linux in download links and tables, or present them side-by-side.
- Provide Linux-specific installation and troubleshooting instructions (e.g., using rpm, dpkg, systemctl) where Windows instructions are given.
- Include Linux shell command examples for common tasks, such as agent installation, configuration, and troubleshooting.
- Reference Linux tools and patterns (e.g., systemctl, journalctl, shell scripts) alongside Windows tools (PowerShell, msiexec).
- Ensure that all features and fixes are clearly marked as platform-specific when relevant, and provide equivalent detail for both platforms.
Azure Arc
CLI reference for `azcmagent connect`
...b/main/articles/azure-arc/servers/azcmagent-connect.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation for `azcmagent connect` shows mild Windows bias in several areas. The authentication options section lists 'Interactive browser login (Windows only)' first and describes its use on Windows desktop, while Linux is mentioned as the default for device code login. The access token authentication references PowerShell's `Get-AzAccessToken` as the example tool, with no Linux equivalent (such as Azure CLI) mentioned. The service principal with certificate section provides extra detail for Windows certificate stores, including supported store locations and thumbprint usage, but does not offer parity guidance for Linux certificate handling.
Recommendations
- When referencing access token acquisition, include Azure CLI equivalents (e.g., 'az account get-access-token') for Linux/macOS users alongside PowerShell examples.
- In the authentication options, present cross-platform methods first (e.g., device code login, service principal) before Windows-only options.
- For certificate-based authentication, provide Linux/macOS guidance on certificate storage and usage, such as file system paths and permissions.
- Where Windows-specific tooling or stores are mentioned, add Linux/macOS alternatives or clarify platform differences.
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
Powershell Heavy
Windows Tools
Summary
The release notes for the Azure Connected Machine agent generally provide parity between Windows and Linux, listing features and fixes for both platforms. However, there is a mild Windows bias: Windows download links are shown first, installer instructions and troubleshooting focus on Windows tools (MSI, PowerShell, Command Prompt), and some improvements reference Windows-specific scripts (ExtensionCleanup.ps1) or GUI. Linux equivalents (e.g., RPM installer, systemctl) are mentioned but less frequently and often after Windows details. There are no Linux command-line examples or troubleshooting tips, and some sections (Known Issues, installer instructions) are Windows-only.
Recommendations
- Alternate the order of Windows and Linux download links, or present them side-by-side.
- Include Linux-specific troubleshooting guidance and command-line examples (e.g., RPM installer usage, systemctl commands) where Windows instructions are given.
- Where Windows tools/scripts are referenced (e.g., ExtensionCleanup.ps1), mention Linux equivalents or clarify if not applicable.
- Add Linux-focused known issues if any exist, and ensure parity in installer troubleshooting steps.
- Explicitly state when a feature or fix is Windows-only or Linux-only for clarity.
Azure Arc
Use cluster connect to securely connect to Azure Arc-enabled Kubernetes clusters.
.../main/articles/azure-arc/kubernetes/cluster-connect.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Minor Shell Inconsistency
Summary
The documentation provides both Azure CLI (Bash/sh) and Azure PowerShell examples in parallel, but PowerShell examples are shown in full detail, including variable assignment and token extraction, which may be more familiar to Windows users. In some places, PowerShell syntax is used for kubectl commands (e.g., variable assignment and token extraction), and the final kubectl example is shown as a PowerShell command, even though kubectl is cross-platform. There is a slight tendency to show PowerShell examples and syntax, which may create minor friction for Linux/macOS users unfamiliar with PowerShell.
Recommendations
- Ensure all kubectl examples use standard shell syntax (Bash/sh) in CLI sections and PowerShell syntax only in PowerShell sections.
- In the 'Access your cluster from a client device' section, provide both Bash and PowerShell examples for kubectl commands, or default to Bash syntax since kubectl is cross-platform.
- Clarify that Azure CLI and kubectl commands work on Linux/macOS and Windows equally, and provide explicit instructions for Linux/macOS users where variable assignment or token extraction differs.
- Consider listing CLI (Bash/sh) examples before PowerShell examples, or side-by-side, to avoid implicit Windows-first ordering.
Azure Arc
CLI reference for `azcmagent disconnect`
...ain/articles/azure-arc/servers/azcmagent-disconnect.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides authentication options for both Windows and Linux, but the interactive browser login is described as 'Windows only' and presented first, while the Linux-default device code login is described second. All examples and instructions are otherwise platform-neutral, and Linux authentication flows are clearly documented.
Recommendations
- Present authentication options in a platform-neutral order, or explicitly state which options are default for each OS before listing them.
- Consider grouping Windows and Linux authentication flows together, or providing parallel examples for each platform where differences exist.
- Clarify that the 'interactive browser login' is available on Windows desktop, but device code is default on Linux and Windows Server Core, to avoid implying Windows is primary.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Windows and Linux examples for managing Run command access, but the Windows example is presented before the Linux example. There are no missing Linux examples or exclusive references to Windows tools; both platforms are treated with parity in terms of actionable guidance.
Recommendations
- Alternate the order of Windows and Linux examples in documentation, or present them side-by-side to avoid the perception of platform preference.
- Consider clarifying that both Windows and Linux are supported equally in introductory sections.
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 before PowerShell. There are no Windows-specific tools or patterns, and Linux users are fully supported via Bash examples. No Linux parity issues are present, but the ordering could be improved for neutrality.
Recommendations
- Continue providing both Bash and PowerShell examples to support cross-platform usage.
- Consider alternating the order of Bash and PowerShell examples, or explicitly state that both are equally supported.
- Add a brief note clarifying that all commands work on Linux, macOS, and Windows (with Bash or PowerShell), to reassure users.
Azure Arc
Multiple Solutions with a Single Shared Dependency at Different Levels
...oad-orchestration/tutorial-service-group-scenario-4.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples for all steps, but consistently lists Bash examples before PowerShell. There are no Windows-only tools or patterns, and all commands use cross-platform Azure CLI and Helm. No Linux examples are missing, and no Windows-specific tools are mentioned. The only minor bias is the ordering of Bash before PowerShell, which may slightly favor Linux/macOS users rather than Windows.
Recommendations
- Consider clarifying that both Bash and PowerShell examples are equally supported and that users can choose either based on their environment.
- Optionally, alternate the order of Bash and PowerShell tabs in different sections to avoid perceived preference.
- Ensure that any environment setup instructions (linked from prerequisites) also provide parity for both Bash and PowerShell users.
Azure Arc
Create a Solution with Multiple Dependencies with Workload Orchestration
...quickstart-solution-multiple-shared-adapter-dependency.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for every CLI step, but PowerShell examples are consistently shown after Bash. There is no exclusive use of Windows tools or patterns, and Linux parity is maintained throughout. However, the presence of PowerShell examples for every command, even when Bash is sufficient for cross-platform use, can be considered a mild Windows bias.
Recommendations
- Consider listing Bash examples first, as Bash is the default shell on Linux and macOS, and is also available on Windows via WSL and Git Bash.
- Clarify that Bash examples work on Linux, macOS, and Windows (with WSL or Git Bash), while PowerShell is primarily for Windows users.
- Where possible, consolidate examples to Bash unless there is a specific PowerShell-only scenario.
- Add a short note at the top explaining shell compatibility for Linux/macOS/Windows users.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples for every step, but consistently lists Bash examples before PowerShell. There are no Windows-specific tools or patterns, and Linux parity is maintained throughout. No Linux examples are missing, and all commands use cross-platform Azure CLI and Helm tools.
Recommendations
- Consider alternating the order of Bash and PowerShell tabs in different sections to avoid perceived preference.
- Explicitly state that both Bash and PowerShell examples are equivalent and supported on their respective platforms.
- Add a short note at the top clarifying that all examples are cross-platform unless otherwise noted.
Azure Arc
Turn on transparent data encryption in SQL Managed Instance enabled by Azure Arc (preview)
...igure-transparent-data-encryption-sql-managed-instance.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Windows and Linux examples for file operations involving kubectl, but Windows examples are consistently presented before Linux equivalents in several sections. There is no exclusive use of Windows tools, PowerShell, or missing Linux examples; parity is maintained in the instructions themselves.
Recommendations
- Alternate the order of Windows and Linux examples in each section, or present Linux examples first in some sections to avoid implicit prioritization.
- Add a short note at the beginning clarifying that both Windows and Linux are supported and examples for both are provided.
- Consider grouping platform-specific instructions side-by-side or in a tabbed format to emphasize equal support.
Azure Arc
Encrypt a database with transparent data encryption manually in SQL Managed Instance enabled by Azure Arc
...data/configure-transparent-data-encryption-manually.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Windows and Linux examples for all relevant commands, using tabbed sections to distinguish them. However, in each case, the Windows example is presented first, which may subtly signal a Windows-first approach. There is no evidence of missing Linux examples, PowerShell-heavy content, or exclusive mention of Windows tools.
Recommendations
- Alternate the order of Windows and Linux tabs in different sections to avoid consistently prioritizing Windows.
- Consider presenting Linux examples first in some sections, especially since SQL Managed Instance enabled by Azure Arc is often deployed on Linux-based Kubernetes clusters.
- Add a brief note at the top clarifying that both Windows and Linux are supported and that examples for both are provided.
Azure Arc
Quickstart - Deploy Azure Arc-enabled data services - directly connected mode - Azure portal
...ttps://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/create-complete-managed-instance-directly-connected.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation exhibits minor Windows bias, primarily in the ordering and presentation of examples and outputs. The Azure CLI output for 'az aks get-credentials' shows a Windows-style file path (C:<current path>\.kube\config), and the documentation does not mention Linux/macOS equivalents or clarify cross-platform differences. All commands are cross-platform, but the examples and screenshots implicitly assume a Windows environment. No PowerShell-specific commands or Windows-only tools are present, and all core steps are achievable on Linux/macOS.
Recommendations
- Include example outputs for both Windows and Linux/macOS, especially for file paths (e.g., ~/.kube/config for Linux/macOS).
- Add notes clarifying that all CLI commands work on Linux/macOS and highlight any OS-specific considerations.
- Where screenshots or instructions reference Windows-specific UI elements or paths, add Linux/macOS equivalents or clarifications.
- Explicitly state cross-platform compatibility of Azure Data Studio and CLI tools.
Azure Arc
Prerequisites | Direct connect mode
...rc/data/create-data-controller-direct-prerequisites.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for connecting a Kubernetes cluster to Azure Arc, but the PowerShell example is given equal prominence and is presented immediately after the CLI example. There is no explicit Linux/macOS example, and PowerShell is a Windows-centric tool, which may create friction for Linux/macOS users. However, the main workflow (using Azure CLI and Helm) is cross-platform, and Linux users can follow the CLI instructions without issue.
Recommendations
- Clarify that Azure CLI and Helm are cross-platform and recommended for Linux/macOS users.
- Explicitly state that PowerShell is primarily for Windows users, and that Linux/macOS users should use Azure CLI.
- Consider presenting CLI examples first, and PowerShell examples in a separate, clearly marked section for Windows users.
- Add a note or table summarizing tool compatibility across OS platforms.
Azure Arc
Deploy a new SQL Managed Instance enabled by Azure Arc using Kubernetes tools
...ate-sql-managed-instance-using-kubernetes-native-tools.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation generally provides cross-platform guidance, but in the example for creating the SQL managed instance with kubectl, the file path example uses a Windows-style path (C:\arc-data-services\sqlmi.yaml) without also providing a Linux/macOS equivalent. Additionally, the PowerShell example for base64 encoding is shown before the Linux/macOS example, which may subtly prioritize Windows users.
Recommendations
- Provide both Windows and Linux/macOS file path examples when showing kubectl commands (e.g., C:\arc-data-services\sqlmi.yaml and /home/user/arc-data-services/sqlmi.yaml).
- Alternate the order of PowerShell and Linux/macOS CLI examples, or present them side by side to avoid implying priority.
- Explicitly state that the instructions apply equally to Windows, Linux, and macOS, and that users should adapt file paths and commands to their environment.
- Consider including a note or table summarizing equivalent commands for each platform where relevant.
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 Present
Summary
The documentation is generally cross-platform, using OpenSSL, Azure CLI, and kubectl, which are available on Linux, macOS, and Windows. However, in the section about base64 encoding, the Linux method is presented first, and then a Windows-specific alternative using certutil is provided. The Windows instructions require manual header removal or an additional command, which is explained. No Linux/macOS equivalents are missing, and the main workflow is platform-neutral. The only minor bias is the explicit mention of Windows tools and extra steps for Windows users.
Recommendations
- Clarify that the Linux base64 command is also available on macOS.
- For parity, mention that certutil is not available by default on all Windows editions, and suggest using PowerShell's [Convert]::ToBase64String() as an alternative.
- Provide a PowerShell example for base64 encoding/decoding for Windows users who may not have certutil.
- Explicitly state that all other steps (OpenSSL, Azure CLI, kubectl) are cross-platform and provide links to installation guides for each OS.
Azure Arc
Get logs to troubleshoot Azure Arc-enabled data services
...in/articles/azure-arc/data/troubleshooting-get-logs.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides a CLI-based approach for log collection that is cross-platform, but the only explicit example of a target folder uses a Windows-style path (C:\temp\logs). There are no Linux/macOS path examples, and the documentation does not clarify cross-platform usage or show Linux/macOS equivalents. This may cause minor friction for non-Windows users.
Recommendations
- Include Linux/macOS path examples (e.g., /tmp/logs) alongside Windows examples when specifying target folders.
- Add a note clarifying that the az CLI and arcdata extension are cross-platform and work on Windows, Linux, and macOS.
- Show example commands with both Windows and Linux/macOS paths to reinforce parity.
- Explicitly mention any OS-specific considerations, if any, for file permissions or path formats.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides environment variable examples for Windows (CMD), PowerShell, and Linux/macOS, but consistently lists Windows and PowerShell examples before Linux/macOS. It also mentions Windows Task Scheduler before Linux equivalents when discussing automation. However, Linux/macOS examples are present and functional throughout, and the main workflow uses cross-platform Azure CLI and kubectl commands.
Recommendations
- Alternate the order of example tabs so Linux/macOS is shown first in some sections.
- Explicitly mention cron before or alongside Windows Task Scheduler when discussing automation.
- Where possible, provide parity in scripting examples (e.g., show a sample cron job entry).
- Consider grouping environment variable examples together or using a table for parity.