Scan Details - Linux-first Docs for Azure

281

Pages Scanned

100

Pages Flagged

281

Changed Pages

35.6%

% Pages Flagged

Live Progress

🔴 Connecting...

100%

Phase: discovery

Processing: Initializing...

Activity Feed

00:00:08 Scan started

Scan Information

Started At: 2026-02-25 00:00:08

Finished At: In Progress

Status: in_progress

Target Repo: Azure Compute

Current Phase: discovery

Files Queued: 281

Files Completed: 281

Problematic Pages

100 issues found

Service Fabric Azure Service Fabric reverse proxy ...articles/service-fabric/service-fabric-reverseproxy.md

High Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ missing_linux_example

Summary

The documentation explicitly states that the Service Fabric reverse proxy is not available for Linux clusters, and all examples and configuration guidance are Windows-centric. There are no Linux-specific instructions, examples, or parity guidance, and the feature is unavailable on Linux clusters.

Recommendations

Clearly indicate at the top of the page that the reverse proxy feature is Windows-only, to prevent confusion for Linux users.
Add a section outlining alternatives or workarounds for Linux clusters, such as using custom service discovery or external proxies.
Link to relevant Linux documentation or guidance for similar scenarios, if available.
If/when Linux support is added, provide Linux-specific examples and configuration instructions.

Create Pull Request

Service Fabric Configure the upgrade of a Service Fabric application ...abric/service-fabric-visualstudio-configure-upgrade.md

High Priority View Details →

Reviewed by: LLM Analysis

Issues: 4 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example ⚠️ windows_first

Summary

The documentation focuses exclusively on upgrading Service Fabric applications using Visual Studio and PowerShell, both Windows-centric tools. All examples and instructions assume the use of Visual Studio (Windows-only) and PowerShell (primarily Windows, though available on Linux, but not referenced here). There are no examples or guidance for Linux/macOS users, such as using CLI tools or cross-platform workflows. The page does not mention Linux equivalents or alternatives, and Windows tools are presented first and exclusively.

Recommendations

Add instructions and examples for upgrading Service Fabric applications using Azure CLI or REST API, which are cross-platform.
Mention and provide guidance for using PowerShell Core on Linux/macOS, if applicable.
Clarify whether Visual Studio Code or other cross-platform editors can be used for Service Fabric application upgrades.
Provide links or references to Linux/macOS workflows for Service Fabric application management.
Explicitly state if the Visual Studio workflow is Windows-only, and direct Linux/macOS users to alternative upgrade methods.

Create Pull Request

Service Fabric Initializer CodePackages in Service Fabric ...in/articles/service-fabric/initializer-codepackages.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example

Summary

The documentation page for Initializer CodePackages in Service Fabric is heavily focused on Windows containers. All examples use Windows container images (mcr.microsoft.com/windows/nanoserver:1809), Windows paths (C:\...), and Windows commands (cmd, echo, type, ping). There are no examples or guidance for Linux containers or Linux-based workloads, and the page explicitly references Windows container compatibility. This creates friction for Linux users and does not demonstrate Linux parity.

Recommendations

Add examples using Linux container images (e.g., mcr.microsoft.com/ubuntu or other Linux distros) and Linux commands (bash, echo, cat, etc.).
Show how Initializer CodePackages can be used in Linux container scenarios, including volume mounts with Linux paths (/workspace/log.txt).
Clarify whether Initializer CodePackages are supported for Linux containers and, if so, provide equivalent Linux-focused guidance.
If Initializer CodePackages are Windows-only, state this clearly at the top of the article to set expectations.

Create Pull Request

Service Fabric RunToCompletion semantics and specifications ...blob/main/articles/service-fabric/run-to-completion.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 4 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools

Summary

The documentation page demonstrates notable Windows bias. All code examples use Windows containers (nanoserver), Windows-specific commands (cmd, echo, ping, set, exit), and Windows-centric naming. The 'Query deployment status' section only provides PowerShell and C# examples, with no mention of Linux CLI or Bash alternatives. There is no guidance or example for Linux containers or cross-platform usage, despite Service Fabric supporting containers in general.

Recommendations

Add examples using Linux containers (e.g., Ubuntu or Alpine images) and Linux shell commands.
Provide equivalent Bash or Linux CLI instructions for querying deployment status, such as using sfctl or REST APIs.
Clarify whether RunToCompletion semantics are supported for Linux containers, and if so, provide relevant guidance.
Balance Windows and Linux examples, or explicitly state if Windows containers are required for this feature.

Create Pull Request

Service Fabric Service Fabric application upgrade ...s/service-fabric/service-fabric-application-upgrade.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 4 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools ⚠️ windows_first

Summary

The documentation page provides PowerShell-only examples and references to Windows-specific tools (e.g., http.sys), with no equivalent CLI or Linux/macOS instructions. The only code sample is in PowerShell, and the upgrade process is described using Windows-centric tooling and APIs. Linux users are not provided with alternative commands or guidance, which may cause confusion or block them from following the documented procedures.

Recommendations

Add equivalent Azure CLI or Service Fabric CLI (sfctl) examples for application upgrades, especially for retrieving and passing application parameters.
Clearly indicate when a feature or limitation (such as http.sys or certificate handling) is Windows-specific, and provide Linux/macOS alternatives or workarounds if available.
Include Linux/macOS-specific instructions or notes where behavior or commands differ.
Reorder or supplement sections so that cross-platform tools (e.g., Azure CLI, REST API, sfctl) are mentioned alongside or before Windows-specific tools like PowerShell.

Create Pull Request

Service Fabric Architecture of Azure Service Fabric ...articles/service-fabric/service-fabric-architecture.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation references PowerShell cmdlets as primary management tools and mentions Windows security as a transport option. There are no explicit Linux or cross-platform management tool examples (such as CLI or REST API), and PowerShell is presented as the default for provisioning and lifecycle management, which may create friction for Linux/macOS users.

Recommendations

Mention and provide examples for cross-platform management tools such as Azure CLI or REST APIs alongside PowerShell.
Clarify whether PowerShell cmdlets are required or if equivalent functionality is available via other tools on Linux/macOS.
Add notes or links to Linux/macOS-specific guidance for managing Service Fabric clusters.
Explicitly state platform support for each subsystem/tool where relevant.

Create Pull Request

Service Fabric Service Fabric Cluster Resource Manager - Application Groups ...ice-fabric-cluster-resource-manager-application-groups.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools

Summary

The documentation provides only PowerShell and C# examples for managing Service Fabric Application Groups. PowerShell is a Windows-centric tool, and no Linux/macOS CLI or scripting examples (such as Bash, Azure CLI, or REST API) are included. This creates friction for Linux/macOS users, as Service Fabric supports cross-platform management but the documentation does not reflect this.

Recommendations

Add Azure CLI examples for all operations shown (application creation, updating, querying load, removing capacity).
Include REST API sample requests for relevant actions.
Mention cross-platform tools and clarify which commands are available on Linux/macOS.
If PowerShell is required, note whether PowerShell Core is supported and provide installation guidance for non-Windows users.
Consider adding Bash scripts or references to SDKs usable on Linux/macOS.

Create Pull Request

Service Fabric Azure Service Fabric security best practices ...rvice-fabric/service-fabric-best-practices-security.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools

Summary

The documentation provides both Windows and Linux guidance for most security best practices, but Windows-specific tools and examples (such as PowerShell commands and Windows Defender) are often presented first or exclusively. Windows-centric features like Windows Defender and security baselines are discussed without Linux equivalents or alternatives. The encryption workflow gives Windows (PowerShell) and Linux (openssl) examples, but Windows instructions are presented first. Some sections reference Windows tools (e.g., Azure Desired State Configuration, Windows Defender) without mentioning Linux alternatives.

Recommendations

Present Windows and Linux examples side-by-side or alternate their order to avoid Windows-first bias.
Where Windows-specific tools are discussed (e.g., Windows Defender, DSC), add notes or links to Linux security alternatives (such as common Linux antivirus solutions or configuration management tools).
Clarify when a feature or recommendation is Windows-only, and provide Linux-specific guidance where possible.
Expand Linux-focused sections to match the detail and prominence of Windows-focused sections.
Ensure all critical workflows (certificate management, secret encryption, endpoint configuration) have clear Linux instructions, not just links.

Create Pull Request

Service Fabric Azure Service Fabric dynamic node tags ...tps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-node-tagging.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools

Summary

The documentation page provides PowerShell examples for managing node tags and service requirements, but does not include equivalent Linux/macOS CLI examples (such as Azure CLI or bash). PowerShell is primarily a Windows tool, and its use here creates friction for Linux/macOS users. There is no mention of cross-platform tools or commands, and the documentation does not clarify if PowerShell Core (cross-platform) is supported or required.

Recommendations

Add Azure CLI or REST API examples for managing node tags and service requirements, as these are cross-platform and accessible from Linux/macOS.
Clarify whether PowerShell Core (cross-platform) is supported, and provide instructions for Linux/macOS users if so.
Mention any limitations or alternative workflows for Linux/macOS users, especially if certain commands are Windows-only.
Consider including bash script examples or references to relevant Service Fabric CLI tools if available.

Create Pull Request

Service Fabric Upgrade an Azure Service Fabric standalone cluster ...ce-fabric/service-fabric-cluster-upgrade-standalone.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ missing_linux_example

Summary

The documentation page primarily references Windows Server-specific upgrade and configuration guides, and the Patch Orchestration Application is described only for Windows. There is no mention of Linux-specific upgrade procedures, configuration files, or patch orchestration, nor are Linux examples or links provided. The linked guides and instructions are Windows-focused, creating friction for Linux users managing Service Fabric standalone clusters.

Recommendations

Add explicit guidance or links for upgrading Service Fabric standalone clusters on Linux, if supported.
Provide Linux-specific examples for cluster configuration, node properties, and capacity metrics.
Clarify whether Patch Orchestration Application or similar solutions exist for Linux nodes, and provide relevant documentation.
Ensure that references to upgrade/configuration guides include both Windows and Linux versions, or clearly state platform limitations.

Create Pull Request

Service Fabric Azure Service Fabric hosting activation and deactivation life cycle ...les/service-fabric/service-fabric-hosting-lifecycle.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation is generally OS-neutral in its explanations of the Service Fabric hosting lifecycle. However, the 'Next steps' section only links to PowerShell-based deployment/removal guidance, and the only explicit example of downloading a ServicePackage in advance references a PowerShell cmdlet. There are no Linux CLI or cross-platform examples or links, which may create friction for Linux users.

Recommendations

Provide equivalent Linux/Bash/CLI examples or links alongside PowerShell references, especially for common tasks like deploying or removing applications.
In the 'Next steps' section, add links to documentation for deploying/removing applications using Azure CLI, REST API, or Service Fabric CLI (sfctl), which are cross-platform.
When referencing commands or tools (such as in [download the ServicePackage in advance on the node]), clarify if the method is Windows-only and suggest Linux alternatives if available.

Create Pull Request

Service Fabric Specifying Service Fabric service endpoints ...ce-fabric/service-fabric-service-manifest-resources.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation provides a PowerShell example for deploying Service Fabric applications, which is a Windows-centric tool. While Linux clusters are mentioned (e.g., certificate store location), the deployment example uses PowerShell exclusively, and there are no equivalent Linux CLI (e.g., sfctl) or bash examples. Windows file paths and tools are referenced first or exclusively in some sections.

Recommendations

Add equivalent Linux deployment examples using sfctl or Azure CLI.
Mention Linux/macOS file paths and tools alongside Windows paths (e.g., schema location).
Provide bash or shell script examples where PowerShell is used.
Clarify any platform-specific differences in endpoint configuration and deployment.

Create Pull Request

Virtual Machines Upload a VHD to Azure or copy a disk across regions - Azure CLI ...machines/linux/disks-upload-vhd-to-managed-disk-cli.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example

Summary

The documentation provides a Windows-centric AzCopy example (using AzCopy.exe and Windows file paths) for uploading a VHD, without showing a Linux/macOS equivalent. The only explicit upload command uses Windows syntax, and there is no mention of how to run AzCopy on Linux/macOS or what the command would look like. The rest of the CLI instructions are cross-platform, but the upload step is critical and lacks Linux parity.

Recommendations

Add a Linux/macOS AzCopy example (using ./azcopy and POSIX file paths, e.g., /home/user/mydisk.vhd).
Clarify that AzCopy is cross-platform and provide download/install instructions for Linux/macOS.
Mention any OS-specific considerations (such as file permissions or path formats) for AzCopy usage.
Consider showing both Windows and Linux/macOS examples side-by-side for key steps.

Create Pull Request

Service Fabric Custom Image .../articles/service-fabric/how-to-deploy-custom-image.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy

Summary

The documentation page primarily discusses deploying custom Windows images on Azure Service Fabric Managed Clusters, with Windows terminology and PowerShell examples appearing before Linux equivalents. While Linux custom image creation is referenced, Windows is emphasized throughout, and the only CLI example is PowerShell.

Recommendations

Provide explicit Linux/macOS examples for role assignment (e.g., using Azure CLI or Bash).
Clarify that custom images can be Linux-based and show ARM template examples for Linux node types.
Balance the order of Windows and Linux references, ensuring Linux is not secondary.
Add links to Linux-specific documentation for Service Fabric Managed Clusters where relevant.

Create Pull Request

Service Fabric Manage certificates in a Service Fabric cluster ...vice-fabric/cluster-security-certificate-management.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_tools ⚠️ windows_first

Summary

The documentation page provides a comprehensive overview of certificate management in Azure Service Fabric clusters, but exhibits Windows bias in several areas. PowerShell is the only scripting example provided for certificate enrollment, and references to Key Vault VM extension are explicitly for Windows. The documentation frequently refers to Windows-specific behaviors (such as certificate linking and S-channel), and the Key Vault VM extension is described in a Windows-centric manner. Linux equivalents (such as the Key Vault VM extension for Linux or CLI/bash scripting) are not mentioned, and Windows tools and patterns are presented first or exclusively.

Recommendations

Add Linux-specific guidance and examples, such as using the Key Vault VM extension for Linux (if supported), or alternative certificate provisioning mechanisms for Linux nodes.
Provide Bash/Azure CLI examples alongside PowerShell for certificate enrollment and management.
Clarify which steps or mechanisms are Windows-only and which are cross-platform, especially for VM extensions and certificate linking.
Reference Linux documentation or tools where applicable, and indicate parity or gaps.
Consider including troubleshooting or FAQ entries for Linux-based Service Fabric clusters.

Create Pull Request

Service Fabric X.509 Certificate-based Authentication in a Service Fabric Cluster ...ticles/service-fabric/cluster-security-certificates.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_first ⚠️ windows_tools ⚠️ powershell_heavy

Summary

The documentation page covers X.509 certificate-based authentication in Service Fabric clusters and is generally cross-platform, referencing both Windows and Linux certificate storage paths. However, there is a notable Windows bias in several areas: Windows certificate store terminology and paths are mentioned first and more frequently; troubleshooting sections reference Windows event logs and tools (such as CAPI2 logging) without Linux equivalents; and configuration flags are described in terms of Windows CryptoAPI and Win32 APIs, with Linux behaviors only briefly mentioned or implied.

Recommendations

Provide Linux-specific troubleshooting guidance, such as log file locations, relevant systemd services, and certificate store paths (e.g., /var/lib/sfcerts).
Include examples of certificate management and validation using Linux tools (e.g., openssl, certutil) alongside Windows/PowerShell examples.
Clarify how configuration flags and certificate validation behaviors map to Linux environments, including any differences in API calls or error codes.
Ensure that references to certificate stores and paths always mention both Windows and Linux equivalents, not just Windows first.
Add explicit guidance for Linux/macOS users on how to provision, rotate, and troubleshoot certificates in Service Fabric clusters.

Create Pull Request

Service Fabric Configure or modify a Service Fabric managed cluster node type ...vice-fabric/how-to-managed-cluster-modify-node-type.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools

Summary

The documentation consistently provides PowerShell examples for command-line operations (add, remove, scale, configure node types), with no mention of Linux/macOS equivalents such as Azure CLI, Bash, or cross-platform scripting. PowerShell is a Windows-first tool (despite cross-platform support, the Azure PowerShell module is most commonly used on Windows), and no Azure CLI or Bash examples are given. This creates friction for Linux/macOS users who may not have or want to use PowerShell.

Recommendations

Add Azure CLI examples for all operations currently shown with PowerShell (e.g., az sf managed-node-type create, update, delete, etc.).
Explicitly mention that PowerShell examples can be run cross-platform (if true), or provide installation guidance for non-Windows users.
Where possible, provide Bash or shell-agnostic examples, or clarify that ARM templates can be deployed using Azure CLI or the portal.
Consider listing Azure CLI examples before or alongside PowerShell to improve parity.

Create Pull Request

Service Fabric Introduction to the Service Fabric Infrastructure Service .../articles/service-fabric/infrastructure-service-faq.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation provides a PowerShell-only example for bypassing Infrastructure Service, without offering equivalent Linux/bash/CLI guidance. The use of PowerShell cmdlets and the absence of Linux-native commands or cross-platform alternatives suggest a Windows-first bias, especially in operational guidance.

Recommendations

Add Azure CLI or bash examples for cluster operations where possible.
Clarify whether the PowerShell command is supported on Linux/macOS (via PowerShell Core), or provide alternative instructions for those platforms.
Mention any limitations or requirements for Linux/macOS users in relevant sections.
Where Service Fabric Explorer is referenced, note its accessibility from non-Windows platforms.

Create Pull Request

Service Fabric Service Fabric Explorer blocking operations ...ged-cluster-service-fabric-explorer-blocking-operation.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation page frequently references Az PowerShell cmdlets for managing Service Fabric resources, such as Remove-AzResource and AzSF PowerShell cmdlets, and provides links to PowerShell documentation. While az CLI is mentioned for deleting applications, PowerShell examples and terminology are more prominent and appear first, potentially creating friction for Linux/macOS users who typically use az CLI or Bash scripts.

Recommendations

Provide equivalent az CLI examples for all operations (e.g., unprovisioning application type versions, creating applications/services).
Mention az CLI commands before or alongside PowerShell cmdlets to ensure Linux/macOS users can easily follow the documentation.
Clarify that both PowerShell and az CLI are supported and provide links to az CLI documentation.
Add Bash script examples where relevant.

Create Pull Request

Service Fabric Deny assignment policy for Service Fabric managed clusters ...cles/service-fabric/managed-cluster-deny-assignment.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation page provides best practice examples and links primarily for Azure PowerShell, with PowerShell-based tools mentioned before Azure CLI and sfctl. While Azure CLI and ARM/Bicep are referenced, PowerShell is emphasized, and Linux-native tools (like sfctl) are listed last and marked as 'No' for ARM-backed support. There are no explicit Linux/macOS examples or command snippets, and the guidance assumes familiarity with PowerShell.

Recommendations

Provide equivalent Azure CLI command examples alongside PowerShell examples for managing NodeTypes and VMSS actions.
Mention sfctl and its usage more prominently, including its Linux/macOS compatibility.
Clarify that Azure CLI and sfctl are cross-platform and suitable for Linux/macOS users.
Consider reordering tool lists to avoid always listing PowerShell first.
Add explicit notes or examples for Linux/macOS users where relevant.

Create Pull Request

Service Fabric Monitor Azure Service Fabric ...main/articles/service-fabric/monitor-service-fabric.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example

Summary

The documentation generally covers both Windows and Linux clusters, but there is a tendency to mention Windows-specific tools (such as Event Log/Event Viewer, ETW, Diagnostics Agent) first or in more detail, and some examples/tutorials are focused on Windows or .NET applications. Linux equivalents (such as LTTng, Syslog, and Linux-specific configuration) are referenced but often after Windows tools and sometimes with less detail or fewer examples. Some sections lack explicit Linux example links or walkthroughs.

Recommendations

Ensure Linux-specific monitoring tools and workflows (e.g., Syslog, LTTng) are described with equal detail and prominence as Windows tools.
Add Linux-focused tutorials and examples, especially for application monitoring and cluster diagnostics.
Where Windows tools are mentioned (e.g., Event Viewer, Diagnostics Agent), immediately provide the Linux equivalent and link to relevant guides.
Review example code and walkthroughs to ensure parity for Linux (e.g., instrumenting applications, configuring monitoring agents).
Consider alternating the order of Windows and Linux mentions, or grouping by OS, to avoid 'Windows-first' bias.

Create Pull Request

Service Fabric Learn about Azure Service Fabric application security ...ric/service-fabric-application-and-service-security.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_first ⚠️ missing_linux_example ⚠️ windows_tools

Summary

The documentation provides a general overview of Service Fabric application security, but several sections display Windows bias. Windows-specific features (such as running services under AD domain accounts or gMSA) are described in detail, while Linux equivalents are missing or only briefly mentioned. Examples and links for disk encryption reference Windows/PowerShell, with Linux disk encryption marked as a 'TO DO'. Windows terminology (e.g., NetworkService) is used in code snippets without Linux alternatives. Linux-specific guidance is often absent or deferred.

Recommendations

Add explicit Linux examples and instructions for disk encryption, including supported tools and configuration steps.
Provide Linux equivalents for user accounts and security principals, clarifying how to configure service identities and permissions on Linux clusters.
Include code snippets and manifest examples that demonstrate Linux-specific settings and terminology.
Ensure parity in coverage for container security features on Linux, not just Windows (e.g., gMSA is Windows-only, but clarify Linux alternatives).
Review all sections for Windows-centric language and add Linux guidance where applicable.

Create Pull Request

Service Fabric Advanced Application Upgrade Topics ...-fabric/service-fabric-application-upgrade-advanced.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example

Summary

The documentation page provides numerous PowerShell-based examples and references, with no mention of Linux/macOS equivalents (such as Azure CLI, REST API, or cross-platform tools). Windows/PowerShell commands are used exclusively for critical upgrade operations, and the PowerShell module is referenced throughout. There is no guidance for Linux/macOS users on how to perform these tasks, creating friction for non-Windows users.

Recommendations

Add Azure CLI examples for all upgrade operations, including creating/updating services and application upgrades.
Reference REST API endpoints for Service Fabric management tasks, with example requests.
Clarify which operations can be performed using cross-platform tools and provide links to relevant documentation.
Explicitly state if certain operations are only possible via PowerShell, and provide alternatives or workarounds for Linux/macOS users.
Include a section summarizing cross-platform support and tool parity for Service Fabric application upgrades.

Create Pull Request

Service Fabric Application upgrade: data serialization ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-application-upgrade-data-serialization.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation page primarily discusses data serialization in the context of Azure Service Fabric, focusing on C# and .NET Data Contract serialization. In the 'Next steps' section, Windows-centric tools (Visual Studio and PowerShell) are highlighted for application upgrades, with no mention of Linux/macOS equivalents or cross-platform CLI tools. This creates a moderate Windows bias, especially in upgrade guidance.

Recommendations

Add examples or links for upgrading Service Fabric applications using cross-platform tools such as Azure CLI or Service Fabric CLI (sfctl), which are available on Linux and macOS.
Clarify whether the upgrade process can be performed on Linux/macOS, and provide relevant instructions if so.
Include guidance for developers using non-Windows environments, such as VS Code or command-line workflows.
Explicitly state any limitations if certain upgrade steps are Windows-only, to help Linux/macOS users understand their options.

Create Pull Request

Service Fabric Migrate an Azure Service Fabric cluster to availability zone support ...ce-fabric/migrate-service-fabric-availability-zones.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation provides migration steps for Azure Service Fabric clusters to availability zone support. While most of the guidance is platform-neutral and focuses on Azure Resource Manager templates and cluster configuration, the step-by-step migration for clusters with Basic SKU load balancer and IP resources relies heavily on PowerShell commands. These commands are presented exclusively, with no equivalent Bash, Azure CLI, or Linux-native examples. Additionally, the PowerShell examples are shown first and only, which may create friction for Linux/macOS users.

Recommendations

Provide Azure CLI equivalents for all PowerShell migration steps, especially for resource deployment, node disabling, and removal.
Include Bash script examples or instructions for Linux/macOS users where applicable.
Clarify in the documentation that PowerShell steps can be performed using Azure CLI or REST API, and link to relevant cross-platform guides.
Consider adding a section or callout for Linux/macOS users, summarizing alternative approaches.

Create Pull Request

Service Fabric Describing Azure Service Fabric apps and services ...ic/service-fabric-application-and-service-manifests.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_tools ⚠️ windows_first

Summary

The documentation contains a notable Windows bias in its tooling recommendations and example paths. Specifically, it recommends using Visual Studio (a Windows-centric tool) to author and validate manifest XML files, referencing a Windows file path (C:\Program Files\Microsoft SDKs\Service Fabric\schemas\ServiceFabricServiceModel.xsd). Additionally, it mentions the ServiceFabric PowerShell module for service creation, which is primarily a Windows tool, without mentioning cross-platform alternatives or Linux/macOS equivalents. However, the core content and examples are platform-neutral XML, and the documentation does not restrict Service Fabric usage to Windows.

Recommendations

Add instructions or recommendations for validating manifest XML files using cross-platform editors (such as VS Code, JetBrains Rider, or command-line XML validators) and provide Linux/macOS file path equivalents if available.
Mention cross-platform tools or CLI alternatives (such as Azure CLI or Service Fabric CLI) for service creation and management, alongside PowerShell.
Clarify when tooling or examples are Windows-specific and provide Linux/macOS alternatives where possible.
Consider referencing documentation or guides for Linux-based Service Fabric clusters if relevant.

Create Pull Request

Service Fabric Application lifecycle in Service Fabric ...service-fabric/service-fabric-application-lifecycle.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 4 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example ⚠️ windows_first

Summary

The documentation page for the Service Fabric application lifecycle consistently references PowerShell cmdlets and Windows-centric tooling for operational tasks (deploy, upgrade, remove, cleanup), often without equivalent Linux/CLI examples or explicit mention of cross-platform alternatives. While REST API and .NET methods are sometimes listed, PowerShell cmdlets are always present and frequently appear first, and there is little guidance for Linux/macOS users on using sfctl or Azure CLI for these tasks.

Recommendations

Add explicit sfctl (Service Fabric CLI) and Azure CLI examples for each operational task (deploy, upgrade, remove, cleanup), alongside PowerShell.
Where PowerShell cmdlets are referenced, also mention the equivalent sfctl command and REST API, and clarify their platform compatibility.
Provide guidance or links for Linux/macOS users on installing and using sfctl and Azure CLI for Service Fabric management.
Reorder examples so that cross-platform tools (sfctl, REST API, Azure CLI) are listed before or alongside PowerShell, not after.
Include notes about platform support for each tool, so users know which options are available on their OS.

Create Pull Request

Service Fabric Application upgrade: upgrade parameters ...abric/service-fabric-application-upgrade-parameters.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy

Summary

The documentation page presents Windows/PowerShell and Visual Studio parameters and examples before Linux equivalents (SFCTL), and provides more detailed parameter tables and explanations for PowerShell and Visual Studio. SFCTL (the cross-platform CLI) is covered later and less extensively. There are no Linux-specific examples or patterns in the main parameter sections, and Windows tools are mentioned first throughout.

Recommendations

Reorganize the page so that cross-platform tools (SFCTL) are presented before or alongside Windows-specific tools (PowerShell, Visual Studio).
Provide equally detailed parameter tables and explanations for SFCTL, matching the depth given to PowerShell/Visual Studio.
Add explicit Linux/macOS usage examples for SFCTL, including sample commands and parameter usage.
Clarify which tools are cross-platform and which are Windows-only at the start of the article.
Consider adding a summary table comparing upgrade methods (PowerShell, Visual Studio, SFCTL, REST) and their platform support.

Create Pull Request

Service Fabric Cluster Resource Manager - Management Integration ...fabric-cluster-resource-manager-management-integration.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation provides a PowerShell example for querying partition health, using Windows-specific syntax and paths (e.g., 'PS C:\Users\User'). No equivalent Linux/macOS CLI example (such as using sfctl or REST API) is given. The only command-line example is Windows-centric, and Windows tools are implicitly prioritized.

Recommendations

Add equivalent Linux/macOS examples using sfctl (Service Fabric CLI) or REST API for querying partition health.
Mention cross-platform tools and approaches alongside Windows/PowerShell examples.
Clarify that PowerShell is one option, and provide guidance for Linux/macOS users.
Consider showing Linux/macOS examples first or equally alongside Windows examples.

Create Pull Request

Service Fabric Restoring backup in Azure Service Fabric ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-backup-restore-service-trigger-restore.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools

Summary

The documentation page for restoring backup in Azure Service Fabric is heavily biased towards Windows/PowerShell usage. All code examples, module installation instructions, and REST API invocation are provided exclusively via PowerShell, with no mention of Linux/macOS-compatible tools or CLI alternatives. The Microsoft.ServiceFabric.Powershell.Http module is a Windows/PowerShell-specific tool, and there are no Bash, Azure CLI, or cross-platform REST invocation examples. This creates friction for Linux/macOS users who may need to restore backups but cannot follow the provided instructions directly.

Recommendations

Add equivalent examples using Bash (curl), Azure CLI, or cross-platform tools for REST API calls.
Document how to authenticate and invoke Service Fabric REST APIs from Linux/macOS environments.
Mention any Linux/macOS-compatible Service Fabric management tools, if available.
Clarify if the PowerShell module is required or if REST API calls can be made directly from any platform.
Provide guidance for certificate handling and authentication on Linux/macOS.

Create Pull Request

Service Fabric Understanding periodic backup configuration ...-fabric-backuprestoreservice-configure-periodic-backup.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_tools ⚠️ windows_first

Summary

The documentation page is generally platform-neutral, focusing on Service Fabric's backup configuration concepts and REST APIs. However, the 'File share' backup storage section exclusively describes Windows-style file shares (UNC paths, Integrated Windows Authentication), with no mention of Linux-compatible alternatives (such as NFS, SMB on Linux, or Azure Files usage from Linux). Additionally, the file share examples and authentication patterns are Windows-centric and presented before any Linux-compatible guidance.

Recommendations

Add guidance for configuring backup storage using Linux-compatible file shares (e.g., NFS, SMB mounts on Linux, or Azure Files accessed from Linux nodes).
Clarify whether Linux Service Fabric clusters can use file share backup storage and provide relevant examples or limitations.
If only Windows file shares are supported, explicitly state this limitation to avoid confusion for Linux users.
Consider including example paths and authentication methods for Linux environments where applicable.

Create Pull Request

Service Fabric Capacity planning and scaling for Azure Service Fabric ...bric/service-fabric-best-practices-capacity-scaling.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_first

Summary

The documentation provides detailed PowerShell-based instructions for scaling operations, but does not offer equivalent Linux/bash examples or mention cross-platform CLI alternatives. Windows/PowerShell tools are referenced exclusively for manual node operations, creating friction for Linux users. Additionally, Windows-centric instructions (e.g., PowerShell commands) are presented before any mention of Linux clusters, and Linux-specific guidance is only linked in the 'Next steps' section without integration into the main content.

Recommendations

Add Azure CLI or bash script examples for scaling and node management operations alongside PowerShell instructions.
Explicitly mention that Service Fabric management commands can be performed from Linux/macOS using Azure CLI or REST API, and provide links or examples.
Include cross-platform guidance in the main scaling sections, not just in 'Next steps'.
Clarify which commands are Windows-only and provide alternatives for Linux clusters where possible.

Create Pull Request

Service Fabric Service Fabric Cluster Resource Manager: Movement cost ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-movement-cost.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example

Summary

The documentation page provides PowerShell examples for configuring move cost in Service Fabric, but does not include equivalent Linux/CLI (e.g., Azure CLI, Bash) examples. PowerShell is primarily a Windows tool, and its exclusive use creates friction for Linux/macOS users. Additionally, PowerShell examples are presented before C# code, reinforcing a Windows-first bias. No Linux-specific tools or commands are mentioned, and there is no guidance for Linux users on how to perform these tasks.

Recommendations

Add Azure CLI or Bash examples for creating and updating Service Fabric services with move cost settings.
Clearly indicate whether PowerShell commands are cross-platform or provide alternatives for Linux/macOS users.
Present CLI or cross-platform examples alongside PowerShell, or list CLI examples first to avoid Windows-first bias.
Include notes or links to Linux/macOS documentation for Service Fabric management.

Create Pull Request

Service Fabric On-demand backup in Azure Service Fabric ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-backup-restore-service-ondemand-backup.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example

Summary

The documentation page for on-demand backup in Azure Service Fabric exclusively provides PowerShell-based examples and instructions, including module installation and REST API invocation via PowerShell. There are no examples or guidance for Linux/macOS users (e.g., Bash, curl, Azure CLI), and the prerequisite steps assume a Windows environment. This creates friction for non-Windows users, as Service Fabric clusters can be managed from Linux/macOS but the documentation does not address their needs.

Recommendations

Add equivalent Bash/curl examples for REST API calls, showing how to trigger backups and track progress from Linux/macOS.
Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is required for all scenarios, or if REST API calls can be made directly from any platform.
Provide Azure CLI examples if possible, or note limitations if PowerShell is required.
Explicitly state platform requirements and alternatives for Linux/macOS users.
Reorder examples so that REST API usage (platform-agnostic) is shown before PowerShell-specific instructions.

Create Pull Request

Service Fabric Azure Service Fabric infrastructure as Code Best Practices ...tps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-best-practices-infrastructure-as-code.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_tools ⚠️ windows_first

Summary

The documentation provides both Azure CLI and PowerShell examples for deploying Resource Manager templates, but PowerShell is featured prominently and exclusively for certain operations (e.g., cluster upgrade). Windows-specific tools and registry keys are mentioned without Linux equivalents. Windows configuration details (such as disabling Windows Update via registry and template properties) are given, while Linux-specific guidance is missing or less emphasized. PowerShell is used for manual upgrades, with no Linux command-line alternatives shown.

Recommendations

Add Linux-specific examples for manual cluster upgrades, such as using Bash or relevant Linux tools.
Include guidance for disabling automatic updates on Linux VM scale sets (e.g., using cloud-init or OS-specific methods).
When mentioning registry keys or Windows configuration, provide Linux equivalents or clarify if not applicable.
Balance PowerShell and Azure CLI examples, and consider including Bash scripts where appropriate.
Ensure that for every Windows-specific operation, a Linux equivalent is either provided or explicitly noted as not required/applicable.

Create Pull Request

Service Fabric Azure Service Fabric networking best practices ...ice-fabric/service-fabric-best-practices-networking.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first ⚠️ windows_tools

Summary

The documentation provides networking best practices for Azure Service Fabric clusters and covers both Windows and Linux scenarios. However, there is a noticeable Windows bias: PowerShell is referenced as the primary API client, Windows-specific tools and tasks (e.g., RDP, Windows Update patching, Windows container networking) are discussed in detail, and Windows examples or terminology often appear before Linux equivalents. Linux is mentioned, but examples and guidance are less detailed or are referenced second. Some sample links and ARM templates are Windows-focused, and PowerShell is highlighted as the main client API, even though CLI and REST are also supported.

Recommendations

Provide Linux CLI (az) and Bash examples alongside PowerShell, especially for cluster management and networking tasks.
Ensure Linux-specific networking scenarios (e.g., SSH, Linux container networking) are described with equal detail as Windows scenarios.
Add links to Linux-focused ARM templates and sample clusters, not just Windows ones.
Mention Linux tools and patterns (e.g., iptables, netstat, systemd) where relevant, especially for troubleshooting.
Clarify when guidance is Windows-only and provide Linux alternatives where possible.

Create Pull Request

Service Fabric Change Azure Service Fabric cluster settings ...rvice-fabric/service-fabric-cluster-fabric-settings.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example

Summary

The documentation page lists Service Fabric cluster settings in a platform-neutral way, but there are several subtle signs of Windows bias. Windows-specific terminology (e.g., 'MY' certificate store, 'LocalMachine', NTLM authentication, Windows Defender Firewall) is used throughout, often without Linux equivalents or clarification. Windows-centric settings (e.g., log file locations, container network setup defaults, Docker npipe usage, firewall configuration) are described without always mentioning Linux alternatives. Some parameters reference Windows-only behaviors or tools, and Windows terminology is used as the default or primary example. Linux-specific settings are present but less prominent and sometimes only mentioned as exceptions.

Recommendations

For parameters referencing Windows-specific concepts (e.g., certificate stores, NTLM, firewall), explicitly note Linux equivalents or clarify if the setting is not applicable on Linux.
Where Windows terminology is used as the default (e.g., 'MY' store, 'LocalMachine'), add Linux examples or clarify Linux paths and behaviors.
For settings with platform-specific defaults (e.g., ContainerNetworkSetup), make both Windows and Linux defaults equally prominent.
Add explicit Linux-focused guidance or examples for settings that are ambiguous or Windows-centric.
Review descriptions for references to Windows tools or patterns and ensure Linux alternatives are mentioned where relevant.

Create Pull Request

Service Fabric Node types and virtual machine scale sets ...les/service-fabric/service-fabric-cluster-nodetypes.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 4 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example

Summary

The documentation page provides general information about Azure Service Fabric node types and VM scale sets, but several sections and examples show Windows bias. The JSON snippet uses a Windows-style file path (D:\\SvcFab) as the default for 'dataPath', and the 'Next steps' section links primarily to Windows/PowerShell-based scripts (changing RDP port range, admin username/password) without Linux equivalents or guidance. There is no mention of Linux-specific remote access methods (e.g., SSH), and Windows tools/patterns (RDP, PowerShell) are referenced before or instead of Linux alternatives.

Recommendations

Add Linux-specific examples for 'dataPath' (e.g., /var/svcfab) and clarify OS-specific path requirements.
Include guidance or links for Linux remote access (SSH) to cluster nodes, not just Windows RDP.
Provide parity in 'Next steps' by linking to Linux/SSH-based scripts or documentation for managing cluster VMs.
Where PowerShell is referenced, also mention Bash/CLI alternatives for Linux users.
Clarify when instructions are OS-specific and provide separate guidance for Windows and Linux clusters.

Create Pull Request

Service Fabric Service Fabric Cluster Resource Manager - Placement Policies ...ce-manager-advanced-placement-rules-placement-policies.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example

Summary

The documentation page provides code examples primarily in C# and PowerShell for configuring Service Fabric placement policies. PowerShell is a Windows-centric tool, and there are no equivalent examples for Linux/macOS users (e.g., Bash CLI, REST API, or Azure CLI). All command-line examples are PowerShell, and no Linux-native tools or patterns are mentioned. This creates friction for Linux users who may not have access to PowerShell or prefer other scripting environments.

Recommendations

Add Azure CLI examples for each placement policy configuration, as Azure CLI is cross-platform and widely used on Linux/macOS.
Include REST API or ARM template snippets for configuring placement policies, which are platform-agnostic.
Explicitly mention whether these policies can be configured using Service Fabric CLI (sfctl) or other Linux-compatible tools, and provide examples if possible.
Clarify any limitations or differences for Linux-based Service Fabric clusters, if applicable.

Create Pull Request

Service Fabric Azure Service Fabric Auto Scaling Services and Containers ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-autoscaling.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example

Summary

The documentation provides code examples for configuring auto scaling policies in Azure Service Fabric using application manifests, C# APIs, and PowerShell. All PowerShell examples are Windows-specific, and no Linux shell (e.g., Bash, CLI) equivalents are provided. The PowerShell examples are presented alongside C# and manifest examples, but there is no mention of Linux-native tooling or cross-platform CLI usage. Additionally, the documentation does not clarify which steps or tools are available on Linux, nor does it provide guidance for Linux users on how to perform equivalent operations.

Recommendations

Add Azure CLI examples for configuring auto scaling policies, as Azure CLI is cross-platform and widely used on Linux/macOS.
Explicitly state which PowerShell commands are Windows-only and provide alternative instructions for Linux users.
Include Bash or shell script examples where possible, or reference Service Fabric REST APIs for cross-platform automation.
Clarify in each section whether the described approach is supported on Linux, macOS, or only Windows.
Mention any limitations or differences for Linux clusters (e.g., resource monitor service support, containerized vs non-containerized workloads).

Create Pull Request

Service Fabric Describe a cluster by using Cluster Resource Manager ...ce-fabric-cluster-resource-manager-cluster-description.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy

Summary

The documentation provides both Windows (ClusterManifest.xml, PowerShell) and cross-platform (ClusterConfig.json, Template.json) configuration examples. However, Windows-specific configuration (ClusterManifest.xml with <WindowsServer>) is presented first and in more detail, and PowerShell commands are used for service creation and updates, with no equivalent Linux CLI or REST API examples. There is no explicit mention of Linux tools or patterns, and the documentation does not clarify Linux/macOS parity for standalone Service Fabric clusters.

Recommendations

Add explicit Linux/macOS configuration examples, such as using ClusterManifest.xml for Linux clusters (<Linux> element) or referencing Linux node setup.
Provide CLI or REST API examples for service creation and updates, not just PowerShell and C#.
Clarify which configuration files and approaches are supported on Linux/macOS and how they differ from Windows.
Mention any Linux-specific constraints or considerations for Service Fabric standalone clusters.
Ensure that cross-platform configuration examples (ClusterConfig.json, Template.json) are given equal prominence and detail as Windows examples.

Create Pull Request

Service Fabric Manage Azure Service Fabric app load using metrics ...ric/service-fabric-cluster-resource-manager-metrics.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example

Summary

The documentation provides both C# and PowerShell examples for managing Service Fabric metrics, but does not include equivalent Linux/macOS CLI examples (such as Azure CLI or Bash). PowerShell commands are shown prominently, and no Linux-native tooling or cross-platform instructions are provided. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other tools.

Recommendations

Add Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used.
Explicitly mention if PowerShell commands are available on Linux/macOS (via PowerShell Core), or provide Bash script equivalents.
Clarify which management operations can be performed via REST API, Azure CLI, or SDKs on Linux/macOS.
Consider including a table comparing management options across platforms (Windows, Linux, macOS) for Service Fabric clusters.

Create Pull Request

Service Fabric Service sensitivity ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-sensitivity.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example

Summary

The documentation provides PowerShell examples for configuring service sensitivity and maximum load, but does not include equivalent Linux/macOS CLI examples (such as Bash or Azure CLI). PowerShell is presented as the primary scripting interface, and no mention is made of cross-platform alternatives or how Linux users can perform these tasks. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other tools.

Recommendations

Add Azure CLI or Bash script examples for all PowerShell commands shown, highlighting cross-platform compatibility.
Explicitly mention whether PowerShell Core (pwsh) is supported on Linux/macOS and provide instructions if so.
Document any REST API endpoints or SDK methods that can be used from Linux/macOS environments.
Clarify if certain operations are Windows-only, or provide guidance for Linux/macOS users where parity exists.

Create Pull Request

Service Fabric Secure an Azure Service Fabric cluster ...cles/service-fabric/service-fabric-cluster-security.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ missing_linux_example

Summary

The documentation page provides security guidance for Azure Service Fabric clusters, mentioning both Azure-hosted and standalone Windows clusters. However, it consistently references Windows Server clusters for standalone scenarios, with no mention of standalone Linux clusters or Linux-specific security setup. Windows security (Kerberos) is discussed, but there is no equivalent section for Linux authentication or Linux-specific certificate management. Examples and links for standalone clusters are exclusively for Windows, and Windows tools (e.g., Windows Server certificate service) are referenced for certificate creation, with no Linux alternatives provided.

Recommendations

Add explicit guidance for securing standalone Linux Service Fabric clusters, including certificate setup and authentication options.
Provide links or references to Linux-compatible certificate management tools (e.g., OpenSSL) and instructions for generating certificates on Linux.
Clarify whether standalone Linux clusters are supported, and if not, state this explicitly to avoid confusion.
Ensure parity in example scenarios, showing both Windows and Linux approaches where applicable.

Create Pull Request

Service Fabric Azure Service Fabric application resource model ...ervice-fabric/service-fabric-concept-resource-model.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 4 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example ⚠️ windows_first

Summary

The documentation page demonstrates notable Windows bias. All deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) without any mention of Azure CLI equivalents or Bash scripting. Application packaging is described via Visual Studio, a Windows-centric tool, with no alternative for Linux/macOS users. No Linux-specific instructions or cross-platform tooling are referenced, and Windows tools are presented first and exclusively.

Recommendations

Add Azure CLI examples for deployment, upgrade, and deletion tasks alongside PowerShell.
Provide instructions for packaging Service Fabric applications using cross-platform tools (e.g., dotnet CLI, sfctl, or manual zip commands) instead of only Visual Studio.
Mention that the Resource Manager template workflow is platform-agnostic and can be executed from any OS.
Include Bash or shell script examples for relevant steps.
Clarify which steps are Windows-only and provide Linux/macOS alternatives where possible.

Create Pull Request

Service Fabric Azure Service Fabric standalone cluster scaling ...ce-fabric/service-fabric-cluster-scaling-standalone.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example

Summary

The documentation page on scaling Azure Service Fabric standalone clusters demonstrates Windows bias by referencing PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) and linking to Windows Server-specific guides. There are no Linux-specific examples, tools, or guidance, even though Service Fabric standalone clusters can be deployed on both Windows and Linux. The documentation assumes Windows tooling and does not mention Linux equivalents or cross-platform approaches.

Recommendations

Add Linux-specific examples and guidance for scaling standalone clusters, including references to relevant CLI tools or scripts.
Mention cross-platform tools (e.g., Service Fabric CLI, REST APIs) where possible, and provide both Windows and Linux workflows.
Clarify when instructions are Windows-only and provide links or notes for Linux users.
Include sample commands for Linux environments, such as using sfctl or bash scripts, alongside PowerShell examples.

Create Pull Request

Service Fabric Upgrading Azure Service Fabric clusters ...icles/service-fabric/service-fabric-cluster-upgrade.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example

Summary

The documentation provides upgrade guidance for Azure Service Fabric clusters, but several sections reference Windows-specific tools and patterns (e.g., Patch Orchestration Application for Windows, NTLM settings, and a link to patching Windows OS images) without mentioning Linux equivalents or clarifying Linux support. Examples for certificate management and port opening mention PowerShell/Azure CLI, but do not provide explicit Linux guidance or parity. The documentation tends to mention Windows-related actions and tools first, and omits Linux-specific upgrade scenarios or tools.

Recommendations

Clarify which upgrade and maintenance procedures apply to Linux-based Service Fabric clusters, and which are Windows-only.
Provide explicit examples for Linux users (e.g., using Bash/Azure CLI, Linux certificate management, port opening on Linux clusters).
Add links or sections for patching Linux OS images in Service Fabric clusters, if supported.
Clearly distinguish Windows-only features (such as NTLM/FileStoreService and Patch Orchestration Application) from cross-platform features.
Where PowerShell is mentioned, ensure Azure CLI/Bash examples are also provided and labeled for Linux/macOS users.

Create Pull Request

Service Fabric Scalability of Service Fabric services .../service-fabric/service-fabric-concepts-scalability.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example

Summary

The documentation page provides code examples and administrative instructions primarily using PowerShell, which is a Windows-centric tool. There are no equivalent Linux CLI or script examples (e.g., Bash, Azure CLI) for scaling operations. Windows tools and patterns (PowerShell cmdlets) are mentioned exclusively and before any Linux alternatives, and Linux users are not given parity in actionable examples. The only explicit Linux mention is in a platform comparison section, but it does not provide Linux-specific operational guidance.

Recommendations

Add Linux-friendly examples for scaling operations, such as using Azure CLI or Bash scripts.
Include instructions or references for Linux users to perform equivalent tasks (e.g., scaling services, updating instance counts) via REST API, Azure CLI, or Service Fabric CLI (sfctl).
Present examples for both Windows and Linux platforms side-by-side, or clarify which examples are platform-specific.
Mention Linux tools (e.g., sfctl, Bash) where PowerShell is referenced, and provide links to relevant documentation.

Create Pull Request

Service Fabric Learn more about Azure Service Fabric ...icles/service-fabric/service-fabric-content-roadmap.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 4 bias types

Detected Bias Types

⚠️ windows_first ⚠️ windows_tools ⚠️ powershell_heavy ⚠️ missing_linux_example

Summary

The documentation provides a broad overview of Azure Service Fabric, which supports both Windows and Linux. However, there is a notable Windows bias: Windows-specific tools (e.g., PowerShell, Visual Studio) are mentioned before Linux equivalents, and Windows terminology (e.g., Windows service, .exe files) is used throughout. Standalone cluster creation and upgrade instructions are Windows-only, with Linux standalone clusters explicitly unsupported. Examples and tool references (e.g., PowerShell cmdlets) are often Windows-first or Windows-only, and Linux-specific workflows or tools are rarely detailed.

Recommendations

Where possible, provide Linux-specific examples and workflows alongside Windows ones (e.g., CLI commands, shell scripts, Linux service management).
Mention cross-platform tools (e.g., sfctl CLI) before or alongside Windows tools like PowerShell.
Clarify which features are Windows-only and which are cross-platform, ideally linking to Linux documentation when available.
Add guidance for Linux users on cluster management, health monitoring, and application lifecycle, using Linux-native tools.
Update 'Next steps' to include Linux cluster creation and management, or clearly state Linux limitations.

Create Pull Request

Service Fabric Health monitoring in Service Fabric ...s/service-fabric/service-fabric-health-introduction.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ missing_linux_example

Summary

The documentation provides a PowerShell-only example for reporting and evaluating application health in Service Fabric, without offering equivalent Linux/macOS CLI or REST API examples. While Service Fabric is cross-platform, the exclusive use of PowerShell in the example creates friction for Linux/macOS users.

Recommendations

Add equivalent examples using Azure CLI, Service Fabric CLI (sfctl), or REST API for health reporting and querying.
Clearly indicate which tools are available on Linux/macOS and provide links to their documentation.
Consider showing Linux/macOS examples alongside Windows/PowerShell examples, or at least referencing them in the 'Example' section.

Create Pull Request

Service Fabric Azure Service Fabric Events ...es/service-fabric/service-fabric-diagnostics-events.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_tools ⚠️ windows_first

Summary

The documentation page primarily references Windows-specific logging mechanisms (ETW/Windows Event logs) and the Windows Azure diagnostics agent as default channels for Service Fabric event access. Windows tools and patterns are mentioned first and exclusively in the 'How to access events' section, with no equivalent Linux examples or guidance. There is no mention of Linux-native logging (e.g., journald, syslog) or cross-platform diagnostic agents, which may create friction for Linux cluster administrators.

Recommendations

Add explicit guidance for accessing Service Fabric events on Linux clusters, including supported logging channels (e.g., Azure Monitor, journald, syslog) and any differences in default diagnostics configuration.
Mention whether the Azure diagnostics agent is available for Linux clusters, or provide alternatives if not.
Provide Linux-specific examples or clarify which instructions are cross-platform.
Ensure parity in tool recommendations and order of presentation (e.g., mention cross-platform REST APIs before Windows-specific tools).

Create Pull Request

Service Fabric Azure Service Fabric DNS service ...n/articles/service-fabric/service-fabric-dnsservice.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example

Summary

The documentation provides PowerShell examples for setting DNS names but does not offer equivalent Linux CLI or scripting examples. Windows tools and patterns (such as ApplicationManifest.xml and Visual Studio) are mentioned, while Linux alternatives are not. The limitations section notes Linux support is restricted, but the overall documentation assumes Windows as the default, with Linux-specific instructions and caveats appearing later or being omitted.

Recommendations

Add Linux CLI examples (e.g., Azure CLI, Bash scripts) for setting DNS names and managing services.
Mention Linux-compatible editors and deployment workflows alongside Visual Studio/ApplicationManifest.xml.
Clarify Linux-specific steps earlier in the documentation, not only in the limitations section.
Provide guidance for enabling DNS service on Linux clusters using ARM templates, including any required settings or workarounds.
Include explicit examples for containerized services on Linux, since Linux support is limited to these.

Create Pull Request

Service Fabric Package an existing executable to Azure Service Fabric ...abric/service-fabric-guest-executables-introduction.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example

Summary

The documentation page demonstrates mild Windows bias. It references Windows directory paths (e.g., C:\Program Files\Microsoft SDKs\Service Fabric\schemas\ServiceFabricServiceModel.xsd) and does not provide equivalent Linux/macOS paths or instructions. The examples and directory structures use Windows conventions (e.g., .exe file extension, backslashes), and there are no explicit Linux/macOS examples or guidance. Visual Studio is mentioned as a packaging tool, which is primarily a Windows application, without mentioning cross-platform alternatives.

Recommendations

Add Linux/macOS equivalent paths for Service Fabric SDK schema files.
Provide examples using Linux/macOS directory conventions (forward slashes, .out or no extension for executables).
Mention cross-platform tools for packaging and deploying guest executables (such as Azure CLI, Service Fabric CLI, or VS Code).
Clarify whether the process is supported on Linux/macOS clusters and, if so, provide relevant instructions.
Include sample manifests and directory structures for Linux/macOS users.

Create Pull Request

Service Fabric Azure Service Fabric container application manifest examples ...abric/service-fabric-manifest-example-container-app.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example

Summary

The documentation page for Azure Service Fabric container application manifest examples exhibits a Windows bias. The manifest examples are explicitly based on a Windows Server 2016 container sample, and several instructions and comments reference Windows-specific tools (e.g., 'winver' to get the OS build version). There are no Linux-specific examples, nor is there guidance for Linux container scenarios, even though Service Fabric supports Linux containers. The documentation also references Windows paths (e.g., 'c:\VolumeTest\Data') and does not provide Linux path equivalents.

Recommendations

Provide parallel examples or notes for Linux container scenarios, including sample manifests based on Linux container images.
When referencing OS build versions, include instructions for obtaining the build/version on Linux (e.g., 'uname -r' or '/etc/os-release').
Use platform-agnostic paths in examples, or show both Windows and Linux path formats where relevant.
Clarify in the introduction whether the examples are Windows-only, or add a section for Linux users if both are supported.
Where features differ between Windows and Linux, explicitly call out the differences and provide guidance for both.

Create Pull Request

Service Fabric Azure Service Fabric hosting model ...rticles/service-fabric/service-fabric-hosting-model.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example

Summary

The documentation page for Azure Service Fabric hosting model demonstrates a moderate Windows bias. PowerShell is the only CLI example provided for service creation, and PowerShell-based links are referenced throughout for management tasks. There are no Linux CLI (e.g., Bash, Azure CLI) or cross-platform examples, and Windows tooling (PowerShell) is mentioned first and exclusively. This creates friction for Linux/macOS users, as Service Fabric supports cross-platform development and deployment, but the documentation does not reflect this parity.

Recommendations

Add Azure CLI examples for service creation and management tasks, alongside PowerShell.
Explicitly mention cross-platform support and provide guidance for Linux/macOS users.
Include Bash or shell script examples where relevant.
Reference REST API usage with curl or other Linux-friendly tools, not just .NET or PowerShell.
Clarify which management tasks can be performed from Linux/macOS and provide links to relevant tools.

Create Pull Request

Service Fabric Azure Service Fabric image store connection string ...fabric/service-fabric-image-store-connection-string.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation page references PowerShell as the primary example for interacting with Service Fabric clusters and retrieving the cluster manifest. It also links to a PowerShell-focused deployment guide as the main 'Next steps'. While Service Fabric is cross-platform, the documentation does not provide equivalent Linux/macOS CLI or scripting examples (e.g., Azure CLI, Bash), nor does it mention Linux tooling or patterns for these operations. Windows tools and workflows are mentioned first and most prominently.

Recommendations

Add Azure CLI or Bash examples for retrieving the cluster manifest and deploying/removing applications, alongside PowerShell.
Include links to Linux/macOS-specific documentation or workflows where relevant.
Mention cross-platform tools and clarify which steps are applicable to Linux/macOS users.
Balance the order of examples so Windows and Linux approaches are presented equally.

Create Pull Request

Service Fabric Reliable services app manifest examples ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-manifest-example-reliable-services-app.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ missing_linux_example

Summary

The documentation page provides manifest examples for Service Fabric applications, but the examples and descriptions are implicitly Windows-centric. Batch scripts (.bat), EXE files, and references to Windows user/group concepts (Administrators, NetworkService) are used throughout, with no mention of Linux equivalents (e.g., shell scripts, Linux user/group patterns). There are no examples or guidance for Linux deployments, even though Service Fabric supports Linux nodes.

Recommendations

Add parallel examples for Linux deployments, such as using shell scripts (.sh) instead of .bat files in SetupEntryPoint.
Clarify which user/group concepts map to Linux equivalents, or provide guidance for configuring principals and RunAsPolicy on Linux clusters.
Include notes or sections indicating which manifest settings are cross-platform and which are Windows-specific.
Show how to configure service manifests for Linux containers or processes, including file permissions and user/group management.
Where EXE files are referenced, mention that on Linux, these would be ELF binaries or scripts, and provide Linux-specific examples.

Create Pull Request

Service Fabric Networking patterns for Azure Service Fabric ...s/service-fabric/service-fabric-patterns-networking.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example

Summary

The documentation consistently uses PowerShell for deployment examples and command-line instructions, with no mention of Azure CLI or Bash equivalents. Windows-centric tools and patterns (e.g., RDP, PowerShell, Windows file paths) are referenced throughout, and Windows examples are presented first or exclusively. There are no Linux/macOS-specific instructions or parity for deployment or cluster management.

Recommendations

Add Azure CLI examples alongside PowerShell for all deployment steps.
Include Bash shell command examples for Linux/macOS users.
Mention SSH as an alternative to RDP for accessing VMs in the cluster.
Use platform-neutral file paths or clarify when Windows paths are used.
Explicitly state if templates and instructions are cross-platform, or provide guidance for Linux/macOS users where differences exist.

Create Pull Request

Service Fabric Service communication with the ASP.NET Core ...vice-fabric-reliable-services-communication-aspnetcore.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_tools ⚠️ windows_first ⚠️ missing_linux_example

Summary

The documentation provides comprehensive coverage of both Kestrel (cross-platform) and HTTP.sys (Windows-only) web servers for ASP.NET Core in Azure Service Fabric. However, there is a notable Windows bias: HTTP.sys (Windows-only) is discussed in detail, including endpoint configuration and port sharing, with explicit mention of Windows tools (netsh) and Windows kernel drivers. Windows-specific features are described before their Linux equivalents, and Linux/macOS-specific guidance is largely absent. While Kestrel is recommended for cross-platform scenarios, Linux/macOS users may find the documentation less clear regarding platform-specific setup, troubleshooting, and limitations. There are no explicit Linux/macOS examples, and some sections (such as endpoint configuration and port assignment) reference Windows patterns/tools without Linux alternatives.

Recommendations

Add explicit Linux/macOS examples for Service Fabric Reliable Services using Kestrel, including platform-specific configuration and troubleshooting.
Clarify which sections and features are Windows-only and which are cross-platform, especially when discussing endpoint configuration and port assignment.
Provide Linux/macOS-specific guidance for firewall configuration, port assignment, and service debugging, avoiding exclusive reference to Windows tools (e.g., netsh).
Include a summary table or section highlighting platform support for each web server and feature.
Ensure parity in example ordering: present cross-platform (Kestrel) examples first, or side-by-side with Windows-only (HTTP.sys) examples.

Create Pull Request

Service Fabric Reliable Collection object serialization ...c-reliable-services-reliable-collections-serialization.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 1 bias type

Detected Bias Types

⚠️ windows_first

Summary

The documentation provides .NET/C# examples exclusively, which is expected for Azure Service Fabric Reliable Collections, as they are primarily used with .NET. However, in the 'Next steps' section, Windows-centric tools (Visual Studio and PowerShell) are mentioned before any Linux-agnostic alternatives, and there is no mention of Linux/macOS tooling or CLI options for application upgrades. There are no explicit Linux examples or references to Linux development environments.

Recommendations

Add references to cross-platform tools such as Azure CLI or Service Fabric CLI (sfctl) for application upgrades.
Include guidance or links for Linux/macOS users on how to develop, deploy, and upgrade Service Fabric applications.
Ensure that PowerShell and Visual Studio are not presented as the only upgrade options; mention alternatives for non-Windows environments.
Clarify that Service Fabric Reliable Collections can be used in Linux node pools (if applicable) and provide relevant links.

Create Pull Request

Service Fabric Replica soft delete for enhanced data protection in Service Fabric ...s/service-fabric/service-fabric-replica-soft-delete.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example

Summary

The documentation page for 'Replica soft delete for enhanced data protection in Service Fabric' demonstrates a notable Windows bias. All command-line/API examples reference PowerShell cmdlets (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica), and no Linux or cross-platform equivalents (such as CLI, REST, or SDK usage from Linux/macOS) are provided. The documentation repeatedly mentions administrative PowerShell APIs as the primary interface, and Windows-centric tooling is referenced first and exclusively. There is no guidance for Linux users on how to perform equivalent operations, nor any mention of Linux-compatible tools or workflows.

Recommendations

Add examples using Service Fabric CLI (sfctl) or REST APIs for replica management, where available.
Clarify whether the PowerShell cmdlets have cross-platform equivalents or if the FabricClient API can be used from Linux/macOS.
Provide sample commands or code snippets for Linux/macOS users, including relevant SDK usage (e.g., Python, Java, .NET Core).
Explicitly state any limitations or parity gaps for Linux clusters, if applicable.
Mention Service Fabric Explorer (SFX) as a cross-platform tool and provide usage instructions for Linux/macOS users.

Create Pull Request

Service Fabric Add custom Service Fabric health reports ...rticles/service-fabric/service-fabric-report-health.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example

Summary

The documentation provides detailed PowerShell examples for health reporting in Service Fabric, with no equivalent Linux/macOS CLI examples (such as Bash or Azure CLI). Windows/PowerShell commands are shown first and exclusively, which may create friction for Linux/macOS users who do not have access to PowerShell or prefer other tools.

Recommendations

Add equivalent examples using Azure CLI or Bash scripts for health reporting tasks.
Clarify which PowerShell commands are cross-platform (PowerShell Core) and which are Windows-only.
Mention any Linux/macOS-compatible tools or APIs for interacting with Service Fabric health reports.
Provide guidance for Linux users on how to install and use PowerShell Core if it is required, or offer alternative approaches.

Create Pull Request

Service Fabric Standalone Service Fabric clusters overview ...-fabric/service-fabric-standalone-clusters-overview.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ missing_linux_example

Summary

The documentation initially describes Service Fabric clusters as supporting both Windows Server and Linux, but later clarifies that Linux isn't yet supported for standalone clusters. Most examples and security guidance focus on Windows-specific features (Kerberos, Windows authentication, Windows Server versions), with no Linux-specific instructions or examples. This creates confusion and friction for Linux users seeking parity.

Recommendations

Clarify at the top of the page that standalone clusters are currently Windows-only, despite initial mention of Linux.
Remove or rephrase statements implying Linux support where it does not exist.
If/when Linux support is added, provide Linux-specific examples, instructions, and security guidance.
Consider linking to documentation for Service Fabric on Linux (if available) or clearly state where Linux is supported (e.g., Azure clusters, not standalone).

Create Pull Request

Service Fabric Define Service Configuration in StartupServices.xml for a Service Fabric Application ...service-fabric/service-fabric-startupservices-model.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_first ⚠️ missing_linux_example ⚠️ windows_tools

Summary

The documentation is heavily focused on Visual Studio workflows and Windows-centric tooling (e.g., F5/Ctrl+F5/Publish, Visual Studio UI, PowerShell references). There are no examples or guidance for Linux/macOS users or cross-platform tooling. The page assumes deployment and development are done via Visual Studio, which is Windows-only, and does not mention alternatives for Linux/macOS users.

Recommendations

Add explicit guidance for Linux/macOS users, including how to manage service configuration and deployment without Visual Studio.
Include examples using cross-platform tools such as Azure CLI, Service Fabric CLI (sfctl), or ARM templates.
Clarify whether StartupServices.xml is strictly a Windows/Visual Studio feature, and if so, provide links or references to Linux/macOS-compatible workflows.
Mention PowerShell alternatives (e.g., Bash scripts, sfctl) for service creation and deployment.
If the feature is Windows-only, state this clearly at the top of the documentation.

Create Pull Request

Virtual Machine Scale Sets Migrate deployments and resources to Virtual Machine Scale Sets in Flexible orchestration ...lexible-virtual-machine-scale-sets-migration-resources.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example

Summary

The documentation references Azure CLI, Azure PowerShell, and ARM templates for creating and migrating scale sets, but does not provide explicit Linux/bash examples or parity for PowerShell commands. Windows-specific scenarios (activation, updates) are mentioned before Linux equivalents, and PowerShell is listed alongside CLI without clear Linux guidance. There are no explicit Linux/macOS command examples or references to Linux tools, creating friction for non-Windows users.

Recommendations

Provide explicit bash/Linux command examples alongside PowerShell, especially for Azure CLI usage.
Mention Linux package manager update scenarios before or alongside Windows update scenarios.
Clarify that Azure CLI is cross-platform and provide guidance for Linux/macOS users where PowerShell is referenced.
Ensure migration steps and tooling are equally described for Linux and Windows environments.
Add examples for Linux VM activation and troubleshooting, not just Windows.
Where PowerShell is referenced, add equivalent bash/CLI instructions.

Create Pull Request

Service Fabric Fault Analysis Service overview .../service-fabric/service-fabric-testability-overview.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation provides usage instructions for C# (via the Microsoft.ServiceFabric NuGet package) and PowerShell (via the Service Fabric SDK and PowerShell module). PowerShell is a Windows-centric tool, and no equivalent Linux/macOS CLI or scripting examples (such as Bash or Azure CLI) are provided. The PowerShell section appears before any mention of Linux tooling, and there is no guidance for Linux users on how to interact with the Fault Analysis Service.

Recommendations

Add examples for using the Fault Analysis Service from Linux/macOS environments, such as with Bash scripts, Azure CLI, or REST API calls.
Clarify whether the Fault Analysis Service APIs can be accessed from non-Windows platforms, and provide guidance for cross-platform usage.
If PowerShell is the only supported scripting interface, explicitly state this limitation and suggest alternatives or workarounds for Linux/macOS users.
Consider including sample code or command-line instructions for Linux users, or linking to relevant cross-platform documentation.

Create Pull Request

Virtual Machines Associate a virtual machine to a capacity reservation group .../virtual-machines/capacity-reservation-associate-vm.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 4 bias types

Detected Bias Types

⚠️ windows_first ⚠️ windows_tools ⚠️ powershell_heavy ⚠️ arm_template_windows

Summary

The documentation provides parity for both Windows and Linux VMs, as indicated in the 'Applies to' section and CLI examples (with Ubuntu image). However, there are signs of Windows bias: PowerShell examples are always present, ARM template examples are Windows-centric (only Windows images and OS versions), and Windows-specific parameters are used in templates. The ARM template section lacks Linux image examples or parameters. Additionally, Windows terminology and tools (PowerShell) are referenced throughout, and in some sections (ARM template), Windows is the default or only option.

Recommendations

Add Linux image options and parameters to ARM template examples (e.g., Ubuntu, CentOS, etc.).
Include Linux-specific OSVersion values and imageReference blocks in ARM templates.
Clarify that PowerShell examples are for Windows users and provide Bash or shell script equivalents for Linux/macOS users where relevant.
Ensure that CLI and API examples consistently use both Windows and Linux VM images, or alternate between them.
Consider providing a sample ARM template for a Linux VM alongside the Windows example.

Create Pull Request

Virtual Machines Create and upload an Ubuntu Linux VHD in Azure ...rticles/virtual-machines/linux/create-upload-ubuntu.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 4 bias types

Detected Bias Types

⚠️ windows_tools ⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example

Summary

The documentation page, while focused on Ubuntu Linux, repeatedly references Windows-specific tools and workflows (notably Hyper-V and PowerShell's Convert-VHD) as primary methods for creating and converting VHDs. Windows/Hyper-V steps are described first and in detail, with no equivalent Linux-native tooling or workflows provided for critical steps like VHD creation and conversion. This creates friction for Linux users, who may not have access to Hyper-V or PowerShell.

Recommendations

Add instructions for creating and converting VHDs using Linux-native tools (e.g., qemu-img, VBoxManage, or dd).
Provide example workflows for preparing and converting disks on Linux hosts, including alignment and format conversion.
Mention Linux virtualization solutions (e.g., KVM, VirtualBox) alongside Hyper-V, and link to relevant guides.
Ensure that all critical steps (such as VHD conversion to fixed size) have Linux alternatives documented.
Clarify that Hyper-V and PowerShell are optional, not required, and highlight cross-platform approaches.

Create Pull Request

Virtual Machines Run scripts in a Linux VM in Azure using managed Run Commands ...articles/virtual-machines/linux/run-command-managed.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_tools ⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation is primarily focused on Linux VMs, but there is notable Windows bias in several areas. PowerShell examples and tools (e.g., Set-AzVMRunCommand, Get-AzVMRunCommand, New-AzStorageBlobSASToken) are heavily featured, sometimes with Windows-specific notes and terminology. REST and ARM template examples occasionally use Windows-centric script syntax (e.g., Write-Host, .ps1 files) and refer to Windows behaviors. In some sections, Windows tools and patterns (PowerShell, SAS token generation) are mentioned before or instead of Linux-native alternatives. However, the Azure CLI section is well-represented for Linux users, and most examples are applicable to Linux VMs.

Recommendations

Ensure REST and ARM template examples use Linux shell script syntax (e.g., 'echo Hello World!' or .sh files) rather than PowerShell/Windows scripts.
Clarify when PowerShell examples are cross-platform (usable on macOS/Linux) and when they are Windows-only.
Add explicit bash or Linux-native command-line examples for SAS token generation and blob management (e.g., using Azure CLI or azcopy), not just PowerShell.
Review notes and parameter descriptions to avoid Windows-centric language (e.g., referencing 'myscript.ps1' or 'Write-Host') when the context is Linux.
Where possible, show Linux examples first or equally alongside Windows/PowerShell examples.

Create Pull Request

Service Fabric Azure Service Fabric Docker Compose Deployment Preview ...ticles/service-fabric/service-fabric-docker-compose.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation provides both PowerShell and cross-platform CLI (sfctl) examples for deploying Docker Compose files to Azure Service Fabric. However, PowerShell examples are presented first and in greater detail, which may suggest a Windows-first bias. There is no explicit mention of Linux/macOS-specific issues or guidance, and the CLI section is less emphasized.

Recommendations

Present CLI (sfctl) examples before PowerShell, as sfctl is cross-platform and more accessible to Linux/macOS users.
Explicitly state that sfctl works on all major platforms and is recommended for non-Windows environments.
Balance the level of detail between PowerShell and CLI sections, ensuring both have equivalent explanations and troubleshooting notes.
Add a brief note clarifying that PowerShell commands require Windows, and recommend sfctl for Linux/macOS users.

Create Pull Request

Service Fabric Manage apps for multiple environments ...e-fabric-manage-multiple-environment-app-configuration.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation provides examples for managing Service Fabric application parameters using PowerShell, sfctl, and Visual Studio. PowerShell and Visual Studio (Windows-centric tools) are mentioned first and in more detail, while Linux-friendly tools (sfctl, install.sh) are referenced but not emphasized. There is a mild bias toward Windows tools and workflows, with limited Linux/macOS-specific guidance.

Recommendations

Add explicit Linux/macOS examples for parameter passing, such as using sfctl from Bash or install.sh.
Clarify which tools are cross-platform and which are Windows-only.
Provide sample scripts or workflows for Linux/macOS users, e.g., using Bash or shell scripts for parameter substitution.
Ensure parity in detail and order between Windows and Linux/macOS tools/examples.

Create Pull Request

Virtual Machine Scale Sets Custom metrics for rolling upgrades on Virtual Machine Scale Sets ...tual-machine-scale-sets-rolling-upgrade-custom-metrics.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools

Summary

The documentation provides both Linux (Bash/Python) and Windows (PowerShell) examples for configuring custom metrics and the application health extension. However, in several sections, Windows/PowerShell examples are presented before Linux/Bash equivalents, and Windows-specific extension types (ApplicationHealthWindows) are used in sample code. PowerShell scripts are detailed and prominent, and Windows tools/terminology (e.g., PowerShell, Windows extension type) are mentioned alongside or before Linux options. REST and Azure CLI examples are cross-platform, but the ordering and emphasis slightly favor Windows/PowerShell.

Recommendations

Ensure Linux/Bash examples are presented before or alongside Windows/PowerShell examples, especially in critical configuration sections.
Explicitly clarify that both ApplicationHealthLinux and ApplicationHealthWindows extension types are supported, and provide sample code for both.
Where possible, use neutral terminology (e.g., 'application health extension for Linux/Windows') and avoid defaulting to Windows-specific names in generic examples.
Balance the depth and detail of Bash/Python and PowerShell sample scripts.
Add troubleshooting examples for Linux (e.g., systemd, firewall rules) alongside Windows troubleshooting steps.

Create Pull Request

Virtual Machines Share VM images in a compute gallery ...in/articles/virtual-machines/shared-image-galleries.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first ⚠️ windows_tools

Summary

The documentation provides both Windows and Linux coverage, but there are signs of Windows bias. PowerShell examples are frequently given alongside Azure CLI, sometimes with more detail. Windows-specific tools (e.g., Sysprep) are mentioned before Linux equivalents (waagent). Windows upload instructions are listed before Linux. References to Windows-specific pages and terminology (e.g., 'Computer name', 'WinRM') are more prominent. Some links and examples default to Windows paths or PowerShell tabs first.

Recommendations

Ensure Linux and CLI examples are given equal prominence and detail as PowerShell/Windows examples.
When mentioning tools for generalizing images, list Linux (waagent) and Windows (Sysprep) together, or alternate order.
Where possible, provide Linux-specific troubleshooting and links alongside Windows ones.
In FAQ and instructional sections, alternate the order of Windows and Linux instructions or present them in parallel.
Review linked pages to ensure Linux parity in referenced content.

Create Pull Request

Service Fabric Azure Service Fabric container image management .../articles/service-fabric/container-image-management.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ windows_tools

Summary

The documentation page for Azure Service Fabric container image management shows minor Windows bias. Windows container base images (microsoft/windowsservercore, microsoft/nanoserver) are referenced as default exclusions in cleanup settings, and Windows image examples are given before Linux equivalents. However, the configuration and cleanup logic appear to be platform-agnostic, and Linux container images are referenced in example regular expressions (e.g., docker.io/library/alpine:latest). No PowerShell or Windows-only tooling is mentioned.

Recommendations

Include explicit Linux container image examples (e.g., Ubuntu, Alpine, etc.) in the 'ContainerImagesToSkip' documentation.
Clarify that the cleanup settings apply to both Windows and Linux containers, if applicable.
Add a note or section about managing Linux container images, including any platform-specific considerations.
Ensure parity in examples and descriptions for both Windows and Linux container scenarios.

Create Pull Request

Service Fabric Overview of Service Fabric and containers ...s/service-fabric/service-fabric-containers-overview.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ windows_tools

Summary

The documentation provides a balanced overview of Service Fabric's container support for both Linux and Windows. However, there is a slight bias toward Windows: Windows container runtimes are listed in more detail, Windows-specific tools (Mirantis Container Runtime, DockerEE) are mentioned, and Windows scenarios (IIS lift and shift) are described first in the 'Scenarios for using containers' section. Linux examples and tutorials are present, but Windows tools and scenarios are often mentioned before their Linux equivalents.

Recommendations

Ensure Linux scenarios are described with equal prominence and detail as Windows scenarios.
List Linux container runtimes and tools with the same specificity as Windows (e.g., mention Docker CE, Podman, or other relevant Linux container runtimes if supported).
Alternate the order of Linux and Windows examples/tutorials to avoid always listing Windows first.
Expand Linux-specific use cases in the 'Scenarios for using containers' section, such as using Apache, NGINX, or other Linux-native workloads.

Create Pull Request

Service Fabric Overview of Azure Service Fabric ...ain/articles/service-fabric/service-fabric-overview.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 1 bias type

Detected Bias Types

⚠️ windows_first

Summary

The documentation mentions both Windows and Linux support for Azure Service Fabric, and provides parity in describing development environments and cluster deployment. However, in the 'Any OS, any cloud' section, Windows development (with Visual Studio and PowerShell) is described before Linux development (with Eclipse and Yeoman), and the quickstart link points to a .NET/Windows-focused guide. No Linux-specific examples or quickstart links are provided, and Windows tools are mentioned first.

Recommendations

Provide Linux quickstart links alongside Windows/.NET quickstart.
Alternate the order of Windows and Linux development environment descriptions, or present them in parallel.
Include examples or references for Linux development and deployment in the 'Next steps' section.
Ensure that Linux tools (Eclipse, Yeoman, Java SDK) are given equal prominence to Windows tools (Visual Studio, PowerShell).

Create Pull Request

Service Fabric Learn Azure Service Fabric terminology ...es/service-fabric/service-fabric-technical-overview.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ windows_tools

Summary

The documentation page is mostly platform-neutral, but there are subtle signs of Windows bias. Windows-specific terminology and tools (such as references to 'auto-start Windows service', 'FabricHost.exe', and EXE/DLL files) are mentioned first or exclusively in some sections, even though Service Fabric supports Linux. Linux equivalents or clarifications are not always provided alongside Windows examples. However, the page does acknowledge Linux support and mentions Docker containers on Linux.

Recommendations

Where Windows-specific tools or executables are mentioned (e.g., 'FabricHost.exe', EXE/DLL), clarify Linux equivalents or note if they are not applicable.
Add explicit references to Linux service/process management where Windows services are discussed.
When describing code packages, mention typical Linux executable formats (e.g., ELF binaries) alongside EXE/DLL.
Ensure that examples and descriptions consistently mention both Windows and Linux environments, especially in sections discussing node setup and service hosting.
Consider reordering or balancing platform mentions so Linux is not always secondary to Windows.

Create Pull Request

Virtual Machine Scale Sets Enable Automatic Zone Balance on Virtual Machine Scale Sets (Preview) ...virtual-machine-scale-sets/auto-zone-balance-enable.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools

Summary

The documentation provides both Azure CLI and PowerShell examples for enabling Automatic Zone Balance on Virtual Machine Scale Sets, but PowerShell (a Windows-centric tool) is consistently presented alongside CLI, and in some sections, PowerShell examples reference Windows-specific extension types (e.g., ApplicationHealthWindows). Portal instructions are platform-neutral, but PowerShell is a Windows tool and is shown as a primary option. Azure CLI examples are present and use Linux images, but PowerShell examples reference Windows extension types, and the PowerShell section is not clearly marked as Windows-only. REST API examples are platform-neutral.

Recommendations

Clarify that Azure PowerShell is available cross-platform, but highlight that it is most commonly used on Windows.
In PowerShell examples, use both ApplicationHealthLinux and ApplicationHealthWindows extension types, or explain when to use each.
Ensure that Linux/macOS users are aware that Azure CLI is fully supported and often preferred for cross-platform scenarios.
Consider showing Azure CLI examples before PowerShell, or explicitly state that PowerShell is a Windows-centric tool.
Add a note in PowerShell sections about compatibility on Linux/macOS (via PowerShell Core), and clarify any Windows-specific limitations.
Where possible, provide Linux-specific guidance or highlight parity between Windows and Linux VMSS configurations.

Create Pull Request

Virtual Machine Scale Sets Attach or detach a virtual machine to or from a Virtual Machine Scale Set ...le-sets/virtual-machine-scale-sets-attach-detach-vm.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation provides both Azure CLI and Azure PowerShell examples for all operations (attach, detach, move), but consistently includes PowerShell examples alongside CLI and portal instructions. PowerShell is a Windows-centric tool, and its inclusion may signal a Windows bias. Additionally, PowerShell examples are shown after CLI, but their presence may create friction for Linux/macOS users who do not use PowerShell. However, Azure CLI examples are present and use Linux-friendly syntax (e.g., Ubuntu image), mitigating the impact.

Recommendations

Clarify that Azure PowerShell is cross-platform, or note that Linux/macOS users should use Azure CLI.
Consider providing Bash shell script examples for common operations, or explicitly state that Azure CLI is recommended for Linux/macOS users.
If PowerShell is included, add a note that it is available on Linux/macOS, or link to installation instructions.
Ensure that all examples are equally accessible to Linux/macOS users, and avoid implying PowerShell is required.

Create Pull Request

Virtual Machine Scale Sets Rolling upgrades with MaxSurge for Virtual Machine Scale Sets ...hine-scale-sets/virtual-machine-scale-sets-maxsurge.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation provides configuration examples for rolling upgrades with MaxSurge using Azure Portal, Azure CLI, PowerShell, and ARM templates. While the CLI and ARM template examples are cross-platform, the PowerShell example is Windows-specific and is given equal prominence. There is mild Windows bias in the inclusion of PowerShell as a primary example, and PowerShell is listed after CLI but before ARM templates. However, Linux/macOS users can use the Azure CLI and ARM templates without issue, and no critical steps are Windows-only.

Recommendations

Clarify that Azure CLI and ARM template methods are fully cross-platform and suitable for Linux/macOS users.
Consider adding Bash shell scripting examples for Azure CLI to reinforce Linux parity.
Explicitly note that PowerShell is Windows-centric and suggest CLI/ARM template for non-Windows environments.
Ensure ordering of examples does not imply Windows preference (e.g., list CLI first, then PowerShell).

Create Pull Request

Virtual Machine Scale Sets Create an Azure scale set that uses Availability Zones ...s/virtual-machine-scale-sets-use-availability-zones.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy

Summary

The documentation provides both Azure CLI and Azure PowerShell examples for creating and updating scale sets with Availability Zones. However, PowerShell examples are given equal prominence to CLI, and in some sections (such as updating scale sets), PowerShell is listed before REST API and after CLI. There is a slight 'windows_first' bias in the ordering of example methods, as PowerShell is mentioned before ARM templates and REST API, and the PowerShell section is detailed. There are no missing Linux examples, as Azure CLI and ARM templates are cross-platform and the documentation references Linux-specific template guides. No Windows-only tools or patterns are used, and the page is not Windows-specific.

Recommendations

Consider listing Azure CLI examples before PowerShell in all sections, as CLI is more universally available across platforms.
Explicitly note that Azure CLI and ARM templates are cross-platform and suitable for Linux/macOS users.
Where PowerShell is shown, clarify that it is primarily for Windows users and suggest CLI for Linux/macOS.
Ensure that all example scripts and commands are available in CLI and ARM template formats, and reference Linux/macOS compatibility where relevant.

Create Pull Request

Virtual Machine Scale Sets Configure rolling upgrades on Virtual Machine Scale Sets ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-configure-rolling-upgrades.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy

Summary

The documentation provides both Azure CLI and PowerShell examples for all operations, but PowerShell examples are consistently presented alongside CLI and portal options, sometimes immediately after CLI. While Azure CLI is cross-platform, PowerShell is primarily used on Windows, and its inclusion may suggest a Windows-centric approach. However, Linux/macOS users can fully use the Azure CLI examples, and there are no Windows-only tools or commands required. The order of examples sometimes puts PowerShell before ARM templates, but not before CLI.

Recommendations

Explicitly note that Azure CLI is cross-platform and recommended for Linux/macOS users.
Consider adding Bash shell script examples or clarifying that CLI commands work on all OSes.
If possible, mention that PowerShell Core is available on Linux/macOS, but CLI is preferred for cross-platform compatibility.
Ensure that CLI examples are always presented before PowerShell, and clarify OS compatibility for each tool.

Create Pull Request

Virtual Machine Scale Sets Networking for Azure Virtual Machine Scale Sets ...ne-scale-sets/virtual-machine-scale-sets-networking.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy

Summary

The documentation provides both Azure CLI and PowerShell examples for most tasks, but PowerShell examples are often presented before CLI examples. In some sections, PowerShell is the only example given (e.g., querying public IPs), or CLI and PowerShell are both offered but PowerShell is listed first. There are no Linux-specific shell examples (e.g., Bash), but CLI commands are cross-platform. No Windows-only tools or patterns are used, and Linux parity is generally maintained, though minor ordering bias exists.

Recommendations

Present CLI examples before PowerShell examples, as CLI is cross-platform and more accessible to Linux/macOS users.
Where PowerShell is used exclusively, ensure a CLI equivalent is provided.
Explicitly note that Azure CLI commands work on Linux/macOS and Windows.
Consider adding Bash script examples for advanced scenarios, if relevant.
Review tab ordering to ensure CLI is the default or first tab.

Create Pull Request

Virtual Machine Scale Sets Orchestration modes for Virtual Machine Scale Sets in Azure ...sets/virtual-machine-scale-sets-orchestration-modes.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 1 bias type

Detected Bias Types

⚠️ windows_first

Summary

The documentation provides a comprehensive overview of orchestration modes for Azure Virtual Machine Scale Sets and is generally platform-neutral. However, in the 'Managed Identity' row of the comparison table, the link for configuring User Assigned Identity points to a Windows VMSS-specific guide, and the section does not mention Linux explicitly. Additionally, the Azure Site Recovery feature is noted as supported 'via PowerShell' for Flexible orchestration, which may imply a Windows-centric tool, though PowerShell is cross-platform. No explicit Linux/macOS examples or tools are provided, but the overall content is not strongly biased toward Windows.

Recommendations

Add links and examples for configuring Managed Identity on Linux VMSS, not just Windows.
Clarify that Azure Site Recovery can be managed via Azure CLI or portal in addition to PowerShell, and provide Linux-friendly instructions.
Where PowerShell is mentioned, note its cross-platform availability and provide Azure CLI equivalents where possible.
Ensure that all example commands (e.g., az vm create) are platform-neutral and clarify their applicability to both Linux and Windows VMSS.

Create Pull Request

Virtual Machines Instantly access managed disk snapshots ...les/virtual-machines/disks-instant-access-snapshots.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy

Summary

The documentation provides both Azure CLI (cross-platform) and Azure PowerShell (Windows-centric) examples for creating instant access snapshots. However, the PowerShell example is given equal prominence and appears before the portal instructions, which may subtly prioritize Windows tooling. There are no Linux-specific shell examples (e.g., Bash), but Azure CLI is inherently cross-platform. No Windows-only tools or patterns are mentioned, and the documentation does not exclusively reference Windows tools. The ordering of examples (CLI, PowerShell, Portal, ARM template) is slightly Windows-first, but not critically so.

Recommendations

Ensure Azure CLI examples are clearly marked as cross-platform and, if possible, provide explicit Bash shell examples for Linux/macOS users.
Consider listing Azure CLI examples before PowerShell to reinforce cross-platform parity.
Add a note clarifying that Azure PowerShell is primarily for Windows users, while Azure CLI works on Linux/macOS/Windows.
If relevant, provide troubleshooting or tips for Linux/macOS environments (e.g., installing Azure CLI).

Create Pull Request

Virtual Machines Secure Azure Managed Disk Downloads and Uploads ...icles/virtual-machines/disks-secure-upload-download.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy

Summary

The documentation provides both PowerShell and Azure CLI examples for securing managed disk uploads/downloads, but PowerShell (a Windows-centric tool) is presented before Azure CLI in several sections. References to role assignment and policy assignment include both PowerShell and CLI, but PowerShell is consistently listed first. The 'Next steps' section offers parity between Linux and Windows, linking to both OS-specific guides. No critical Linux gaps are present, but the ordering and emphasis slightly favor Windows/PowerShell users.

Recommendations

Alternate the order of PowerShell and Azure CLI examples so Linux users see CLI options first in some sections.
Explicitly note that Azure CLI works cross-platform and is recommended for Linux/macOS users.
Where possible, provide Bash shell script examples alongside PowerShell, especially for disk operations.
Consider grouping examples by platform (Windows, Linux/macOS) or labeling tabs more clearly to help users find relevant instructions.

Create Pull Request

Virtual Machines Restrict managed disks from being imported or exported ...tual-machines/disks-restrict-import-export-overview.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation provides links and examples for both Azure PowerShell and Azure CLI, but the custom RBAC role section links only to a PowerShell-based guide, and PowerShell is mentioned before CLI in the Network access policy section. This creates a slight Windows bias, as Linux users may prefer CLI or other methods.

Recommendations

Add a link to a custom RBAC role creation guide using Azure CLI, not just PowerShell.
Ensure CLI examples and links are presented alongside or before PowerShell equivalents.
Where possible, provide explicit Linux/macOS instructions or clarify cross-platform compatibility.

Create Pull Request

Virtual Machines Azure VM Extensions and Features for Linux ...articles/virtual-machines/extensions/features-linux.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy

Summary

The documentation is focused on Linux VM extensions, but consistently presents both Azure CLI and Azure PowerShell examples for nearly every task. PowerShell examples are always present, even though PowerShell is primarily a Windows-centric tool (though available on Linux). In several sections, PowerShell examples are shown immediately after CLI, and the introductory text mentions PowerShell alongside CLI, ARM templates, and portal. However, all actual extension usage and scripting examples are Linux-focused, and there are no Windows-only tools or commands. The documentation does not omit Linux examples, but the presence and prominence of PowerShell may create friction for Linux users who do not use PowerShell.

Recommendations

Consider clarifying that Azure PowerShell is cross-platform, but that Azure CLI is the primary tool for Linux users.
Present Azure CLI examples first in all sections, and consider making PowerShell examples secondary or optional (e.g., in expandable tabs).
Explicitly mention Bash or shell scripting as the default for Linux, and highlight Linux-native tools where relevant.
Where possible, provide Bash script examples for common extension management tasks (e.g., using az CLI in shell scripts).

Create Pull Request

Virtual Machines NVIDIA GPU Driver Extension - Azure Linux VMs ...es/virtual-machines/extensions/hpccompute-gpu-linux.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation is focused on Azure Linux VMs and the NVIDIA GPU Driver Extension for Linux, with nearly all examples, instructions, and troubleshooting steps tailored for Linux environments. However, PowerShell examples are provided alongside Azure CLI and ARM template examples for deploying the extension, and PowerShell is mentioned before Azure CLI in some sections. There is a brief reference to a Windows extension, but it is clearly separated and not the focus. No Linux examples are missing, and Linux tools and patterns are well represented.

Recommendations

Consider moving Azure CLI examples before PowerShell examples, as CLI is more cross-platform and native to Linux.
Clarify that PowerShell examples are for users on Windows or using Azure PowerShell on Linux/macOS, to avoid confusion.
Optionally, provide Bash script examples for common tasks (e.g., checking extension status) to further enhance Linux parity.
Ensure that troubleshooting and deployment sections consistently prioritize Linux-native tools and commands.

Create Pull Request

Virtual Machines Azure Key Vault VM Extension for Linux ...rticles/virtual-machines/extensions/key-vault-linux.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation is focused on the Azure Key Vault VM Extension for Linux and provides comprehensive Linux-specific guidance. However, in deployment and troubleshooting sections, PowerShell examples are presented first and in greater detail, with Azure CLI examples following. Troubleshooting instructions reference Azure PowerShell before Azure CLI. There are no missing Linux examples or exclusive Windows tools, but the ordering and emphasis on PowerShell may create friction for Linux users who typically use Azure CLI or shell scripting.

Recommendations

Present Azure CLI examples before PowerShell in deployment and troubleshooting sections, as CLI is more commonly used on Linux.
Expand CLI troubleshooting instructions to match the detail provided for PowerShell.
Add a brief note clarifying that PowerShell is optional and Azure CLI is fully supported for Linux users.
Consider adding Bash or shell script snippets for common Linux automation scenarios.

Create Pull Request

Virtual Machines Azure Disk Encryption scenarios on Linux VMs ...ticles/virtual-machines/linux/disk-encryption-linux.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy

Summary

The documentation provides both Azure CLI and Azure PowerShell examples for all major operations, but PowerShell (a Windows-centric tool) is often mentioned first or in more detail, and some instructions reference using PowerShell sessions even when working with the Azure CLI. There are minor instances of Windows-first ordering and PowerShell-heavy explanations, but Linux parity is generally maintained through CLI examples and explicit Linux context.

Recommendations

Ensure Azure CLI examples are always presented before or alongside PowerShell examples, especially since CLI is cross-platform and preferred for Linux users.
Remove references to using Azure CLI 'in any PowerShell session'—clarify that CLI can be used in Bash or other Linux-native shells.
Where possible, add Bash shell scripting examples for Azure CLI usage to further reinforce Linux-native workflows.
Consider adding explicit notes about CLI and PowerShell parity, and clarify which tool is recommended for Linux users.

Create Pull Request

Virtual Machines Deprovision or generalize a VM before creating an image ...docs/blob/main/articles/virtual-machines/generalize.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy

Summary

The documentation provides clear, separate instructions for both Linux and Windows VM generalization. However, in the Windows section, PowerShell and Command Prompt examples are used, and the Windows steps are presented after the Linux steps. There is no evidence of missing Linux examples or Windows tools being mentioned exclusively. Both OSes are covered with parity, but Windows-specific tooling (PowerShell) is used for Windows steps, which is appropriate. The Linux section uses waagent and Azure CLI, which are cross-platform. The order of sections (Linux first) avoids 'windows_first' bias.

Recommendations

Ensure that Azure CLI commands for marking a VM as generalized are shown for Windows VMs, not just PowerShell.
Consider adding a note that Azure CLI can be used on Windows as well, for cross-platform parity.
Where possible, provide both Azure CLI and PowerShell examples for Windows VM generalization.

Create Pull Request

Virtual Machines Create an image definition and image version ...s/blob/main/articles/virtual-machines/image-version.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy

Summary

The documentation provides parity for both Linux and Windows users in most sections, including CLI, REST, and portal instructions. However, there is a mild Windows bias in the PowerShell examples, which default to Windows OS in their sample code, and in the ordering of OS-specific guidance, where Windows is often mentioned after Linux but PowerShell examples are more Windows-centric. Additionally, PowerShell is presented as a primary scripting option, which is more common for Windows users.

Recommendations

In PowerShell examples, provide Linux-focused sample code (e.g., use -OsType Linux in the main example, not just as a note).
Ensure that both Linux and Windows are equally represented in sample code and explanations, especially in scripting sections.
Consider adding Bash or shell scripting examples for Linux users, or clarify that CLI is cross-platform.
Explicitly state that PowerShell can be used on Linux/macOS, and provide guidance for those environments if relevant.

Create Pull Request

Virtual Machines Enable Azure Disk Encryption for Linux VMs ...les/virtual-machines/linux/disk-encryption-overview.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 1 bias type

Detected Bias Types

⚠️ windows_first

Summary

The documentation is focused on enabling Azure Disk Encryption for Linux VMs and is generally Linux-centric. However, in several places, Azure PowerShell is mentioned alongside Azure CLI as a tool for managing Linux VM disk encryption, and PowerShell examples/scripts are referenced equally with CLI ones. In the 'Next steps' and introductory sections, PowerShell is listed immediately after CLI, rather than after Bash or Linux-native tools, which may create a minor perception of Windows bias. There are no Windows-only tools, patterns, or examples given, and all technical instructions and examples are Linux-specific.

Recommendations

Consider listing Azure CLI examples and scripts before PowerShell in all sections, as CLI is more commonly used on Linux.
Clarify that PowerShell can be used cross-platform, but Azure CLI is the primary Linux-native tool.
Add explicit mention that both Azure CLI and PowerShell are available on Linux, and provide guidance for users who may prefer Bash scripting or native Linux tools.
If possible, provide Bash script examples or highlight CLI usage in Bash shells to reinforce Linux parity.

Create Pull Request

Virtual Machines Verify encryption status for Linux - Azure Disk Encryption ...tual-machines/linux/how-to-verify-encryption-status.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation provides both Azure PowerShell and Azure CLI examples for verifying disk encryption status on Linux VMs. However, PowerShell examples are presented before Azure CLI, and the PowerShell section is more detailed and prominent, despite Linux users typically preferring Azure CLI or Bash. There are no missing Linux examples, and the OS-level section uses Linux-native commands (lsblk, cryptsetup).

Recommendations

Present Azure CLI examples before PowerShell, as CLI is more relevant for Linux users.
Ensure Azure CLI and Bash examples are as detailed and comprehensive as PowerShell examples.
Consider reducing PowerShell prominence or clarifying its use for cross-platform scenarios.
Add a brief note explaining PowerShell's cross-platform support, but emphasize CLI/Bash for Linux.
Review and balance the depth of CLI and PowerShell sections to avoid perceived bias.

Create Pull Request

Virtual Machines Create and upload a Red Hat Enterprise Linux VHD for use in Azure ...les/virtual-machines/linux/redhat-create-upload-vhd.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ windows_tools

Summary

The documentation provides comprehensive instructions for preparing and uploading a Red Hat Enterprise Linux VHD for Azure, covering multiple hypervisors (Hyper-V, KVM, VMware, Kickstart). However, there is a notable Windows bias: Hyper-V (a Windows-only tool) is consistently presented first in each major section, and Windows-centric terminology (e.g., 'Hyper-V Manager', 'Connect', 'Action > Shut Down') is used throughout. The instructions for KVM, VMware, and Kickstart are present and detailed, but Windows/Hyper-V steps are prioritized and referenced as the default workflow. Additionally, some conversion steps reference Windows tools (e.g., 'convert-vhd' cmdlet) before Linux alternatives.

Recommendations

Reorder sections so that Linux-native hypervisors (KVM, VMware, Kickstart) are presented before or alongside Hyper-V, rather than always after.
Where possible, use neutral terminology for actions (e.g., 'Shut down the VM' instead of 'Action > Shut Down in Hyper-V Manager').
When mentioning disk conversion tools, provide Linux-native options (e.g., qemu-img) before or alongside Windows tools (e.g., Hyper-V Manager, convert-vhd).
Add a summary table or flowchart at the top to help users quickly identify the relevant workflow for their platform.
Ensure that all references to Windows tools are matched with equivalent Linux/macOS alternatives, and avoid implying that Windows/Hyper-V is the default or preferred method.

Create Pull Request

Virtual Machines Create an Azure Image Builder Bicep file or ARM template JSON template .../articles/virtual-machines/linux/image-builder-json.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools

Summary

The documentation provides both Windows and Linux coverage for Azure Image Builder, but there are several areas where Windows-specific examples, tools, and terminology are presented first or more prominently. PowerShell is often referenced for checksum generation and resource actions, sometimes before or instead of Linux equivalents. Windows customizers (PowerShell, WindowsRestart, WindowsUpdate) are described in detail, while Linux customizers (Shell) are covered but with less depth. Windows-specific tools (Get-FileHash, PowerShell commands) are mentioned more frequently than Linux alternatives (sha256sum).

Recommendations

Ensure Linux/macOS commands (e.g., sha256sum, Azure CLI) are presented alongside or before Windows/PowerShell equivalents, especially in sections about checksum generation and resource actions.
Balance the order and depth of customizer descriptions: provide equal detail for Shell customizer as for PowerShell/Windows customizers.
Where PowerShell is referenced for operations (e.g., invoking actions, generating checksums), always include the Linux/macOS CLI equivalent and make it equally prominent.
Add explicit notes or examples for Linux-specific scenarios where only Windows examples are given (e.g., restart customizer, validator examples).
Review the order of examples and ensure Linux and Windows are treated equally in introductory and summary sections.

Create Pull Request

Virtual Machines Time sync for Linux VMs in Azure ...blob/main/articles/virtual-machines/linux/time-sync.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 1 bias type

Detected Bias Types

⚠️ windows_first

Summary

The documentation is focused on Linux VM time sync in Azure and provides comprehensive Linux-specific guidance, including tools, commands, and configuration examples for chrony, ntpd, systemd-timesyncd, and cloud-init. However, the 'Overview' section and opening paragraphs spend several sentences discussing Windows Server 2016 time sync improvements and Windows host infrastructure before describing Linux-specific mechanisms. Windows references are presented first and in detail, even though the page is Linux-focused. All technical examples and instructions are Linux-centric, and there are no PowerShell or Windows tool examples except for a single PowerShell command for base64 encoding cloud-init, which is contextually relevant for Azure ARM templates.

Recommendations

Move the Windows Server 2016 time sync discussion to a background or context section, or summarize it briefly before focusing on Linux-specific details.
Begin the page with Linux time sync mechanisms and Azure-specific integration, referencing Windows infrastructure only as necessary for context.
Clarify that Windows host improvements are relevant only insofar as they affect Linux VM time sync via VMICTimeSync.
Consider providing the base64 encoding example for cloud-init in Linux (e.g., using 'base64 cloud-config.txt') alongside the PowerShell example for parity.

Create Pull Request

Virtual Machines vCPU quotas ...ute-docs/blob/main/articles/virtual-machines/quotas.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy

Summary

The documentation provides both Azure CLI and PowerShell examples for checking vCPU quotas. However, the PowerShell example is given equal prominence and detail, despite PowerShell being primarily a Windows tool. The CLI example is shown first, which is positive, but the presence of PowerShell may create friction for Linux/macOS users, as PowerShell is less commonly used on those platforms.

Recommendations

Clarify that PowerShell is primarily for Windows users, and recommend Azure CLI for Linux/macOS.
Consider adding Bash or shell script examples for Linux users, if applicable.
Explicitly note cross-platform compatibility of Azure CLI.
If PowerShell is supported on Linux/macOS, mention installation instructions or link to relevant docs.

Create Pull Request

Virtual Machines Customer intent: "As an IT administrator managing Azure IaaS virtual machines, I want to implement a backup and disaster recovery plan for unmanaged disks, so that I can ensure data durability and high availability in the event of localized or regional failures." ...al-machines/page-blobs-backup-and-disaster-recovery.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy ⚠️ minor_windows_tools

Summary

The documentation covers backup and disaster recovery for Azure unmanaged disks on both Linux and Windows VMs. While most guidance is platform-neutral, there are several instances where Windows tools (PowerShell, Volume Shadow Service) are mentioned first or exclusively, and PowerShell is referenced more often than Linux equivalents. Linux-specific tools (fsfreeze, Azure CLI) are mentioned, but often after Windows tools or in less detail. Some links and examples (e.g., incremental snapshots) point to Windows pages first, though Linux equivalents are referenced in the 'Next steps' section.

Recommendations

Ensure Linux and Azure CLI examples are presented alongside or before PowerShell examples, especially in automation and recovery sections.
Where Windows tools (e.g., Volume Shadow Service) are discussed, provide equal detail for Linux alternatives (e.g., fsfreeze, application-consistent backup guidance).
In tables and lists, avoid defaulting to Windows-centric terminology or links; ensure Linux documentation is equally prominent.
Add explicit Linux CLI commands and scripts for snapshot, backup, and restore operations.
Review cross-references to ensure Linux incremental snapshot documentation is linked as prominently as Windows versions.

Create Pull Request