← Back to Dashboard
260
Pages Scanned
85
Pages Flagged
260
Changed Pages
32.7%
% Pages Flagged

Scan Information

Started At: 2026-02-04 00:00:07

Finished At: 2026-02-10 18:44:36

Status: completed

Target Repo: Azure Compute

Current Phase: discovery

Files Queued: 260

Files Completed: 260

Problematic Pages

85 issues found
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 on upgrading Service Fabric applications using Visual Studio and PowerShell, both of which are primarily Windows tools. All examples and instructions are given for Visual Studio (Windows-only) and PowerShell (Windows-centric), with no mention of Linux/macOS alternatives or cross-platform CLI tools. There are no instructions or examples for upgrading Service Fabric applications from Linux/macOS environments, nor is there guidance for using Service Fabric CLI or REST APIs.
Recommendations
  • Add instructions for upgrading Service Fabric applications using Service Fabric CLI (sfctl), which is cross-platform.
  • Include examples for Linux/macOS users, such as using sfctl or REST API calls to perform upgrades.
  • Clarify which steps are Windows-only and provide parity guidance for non-Windows environments.
  • Mention prerequisites or limitations for Linux/macOS users, and link to relevant documentation.
GitHub Create Pull Request
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 page for Azure Service Fabric reverse proxy is Windows-focused, as the reverse proxy feature is explicitly stated to be unavailable for Linux clusters. All examples, configuration details, and usage instructions are implicitly for Windows clusters only, with no Linux equivalents or alternatives provided.
Recommendations
  • Clearly state at the top of the page that reverse proxy is not available for Linux clusters, and link to alternative approaches for Linux users if available.
  • Provide guidance or references for Linux cluster users on how to achieve similar service discovery and communication patterns without the reverse proxy.
  • If/when Linux support is added, update documentation to include Linux-specific setup, configuration, and usage examples.
GitHub Create Pull Request
Service Fabric Standalone Service Fabric clusters overview ...-fabric/service-fabric-standalone-clusters-overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ missing_linux_example ⚠️ windows_tools ⚠️ windows_first
Summary
Although the introduction claims Service Fabric clusters can run on both Windows Server and Linux, the documentation page exclusively lists Windows Server versions as supported operating systems and provides security configuration details only for Windows environments (e.g., Kerberos, Active Directory, group Managed Service Accounts). No Linux-specific instructions, examples, or supported Linux OS versions are mentioned, and Windows tools/patterns are referenced without Linux equivalents.
Recommendations
  • Clarify the current Linux support status: If Linux is not yet supported for standalone clusters, state this clearly at the top and remove references to Linux in the introduction.
  • If Linux support is planned or available elsewhere, add a dedicated section for Linux setup, supported distributions, and security configuration.
  • Provide Linux-specific examples for cluster creation, security (certificate management), and scaling/upgrading operations.
  • Mention Linux tools and patterns (e.g., OpenSSL for certificates, Linux user/group management) alongside Windows equivalents.
  • Ensure that all references to Windows-specific technologies (Kerberos, AD, group Managed Service Accounts) are marked as Windows-only and, where possible, provide Linux alternatives.
GitHub 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: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation predominantly references PowerShell cmdlets (e.g., Remove-AzResource, AzSF PowerShell cmdlet) for managing Service Fabric resources, with no mention of Linux/macOS CLI equivalents or examples. While az resource (Azure CLI) is briefly mentioned for application deletion, most guidance and links focus on PowerShell, which is traditionally Windows-centric. There are no explicit Linux/macOS instructions or examples, which may create friction for non-Windows users.
Recommendations
  • Include Azure CLI examples for all operations (e.g., creating/deleting applications, services, scaling) alongside PowerShell cmdlets.
  • Clarify which commands are cross-platform and which are Windows-specific.
  • Add notes or links for installing and using Azure CLI on Linux/macOS.
  • Where PowerShell is required, mention PowerShell Core's cross-platform support and provide installation guidance for Linux/macOS.
GitHub 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: 4 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation page on X.509 Certificate-based Authentication in a Service Fabric Cluster exhibits a moderate Windows bias. While the conceptual explanations are platform-neutral, practical details, troubleshooting, and examples often reference Windows-specific tools, APIs, and patterns (e.g., certificate stores like LocalMachine\My, Win32 CryptoAPI, CAPI1/CNG providers, and event log paths). Linux equivalents are mentioned only briefly or as afterthoughts, and there are no concrete Linux/macOS command-line or troubleshooting examples. This may create friction for Linux users, especially when diagnosing issues or configuring certificates.
Recommendations
  • Include explicit Linux/macOS equivalents for all Windows-specific instructions, such as certificate store locations, certificate management commands, and log file paths.
  • Provide Linux/macOS command-line examples for common tasks (e.g., using openssl, certutil, or other cross-platform tools to manage certificates).
  • Clarify how Service Fabric on Linux handles certificate discovery, validation, and storage, especially where it differs from Windows (e.g., /var/lib/sfcerts vs. LocalMachine\My).
  • Add troubleshooting steps and error messages relevant to Linux environments, including where to find logs and how to interpret common errors.
  • When referencing Windows APIs or tools (e.g., Win32 CryptoAPI, CAPI1), provide context or alternatives for Linux users, or note if certain features are Windows-only.
GitHub 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 on advanced Service Fabric application upgrade topics demonstrates a notable Windows bias. All command-line examples use PowerShell cmdlets, with no mention of Linux/macOS equivalents (such as Service Fabric CLI or REST API usage). Windows/PowerShell tools are referenced exclusively and repeatedly, and the structure of the documentation assumes familiarity with PowerShell workflows. There are no examples or guidance for users managing Service Fabric clusters from Linux or macOS environments.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • Where PowerShell cmdlets are referenced, include a note or section on how to perform the same operations using sfctl or REST API.
  • Clarify which features or commands are available cross-platform and which are Windows-only, to help users on non-Windows systems.
  • Provide links to Service Fabric CLI documentation alongside PowerShell references.
  • Reorder or balance examples so that Linux/macOS workflows are not consistently presented after Windows/PowerShell ones.
GitHub 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 ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation is heavily focused on PowerShell-based workflows, requiring the Microsoft.ServiceFabric.Powershell.Http module and providing all CLI examples in PowerShell syntax. There are no examples or guidance for performing on-demand backups using cross-platform tools (such as Azure CLI, curl, or bash scripts), nor is there mention of Linux/macOS-compatible alternatives for connecting to Service Fabric clusters or invoking REST APIs. This creates friction for Linux/macOS users who may not have access to PowerShell or the required modules.
Recommendations
  • Provide equivalent examples using cross-platform tools such as Azure CLI, curl, or bash scripts for invoking REST APIs.
  • Document how to authenticate and connect to Service Fabric clusters from Linux/macOS environments, including certificate handling.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is available and supported on PowerShell Core (pwsh) on Linux/macOS, or suggest alternatives if not.
  • Include REST API request examples using curl or HTTPie, with sample JSON payloads and authentication details.
  • Add a note or section specifically addressing Linux/macOS users and their options for performing on-demand backups.
GitHub 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 and Linux configuration examples for standalone Service Fabric clusters (via ClusterManifest.xml and ClusterConfig.json), but consistently presents Windows-specific XML examples first and uses Windows terminology (e.g., <WindowsServer> infrastructure). Additionally, code samples for interacting with Service Fabric services are given in C# and PowerShell, with no Linux-native CLI or Bash examples. PowerShell is a Windows-centric tool, and its exclusive use for scripting examples may create friction for Linux/macOS users.
Recommendations
  • Add explicit Linux configuration examples for Service Fabric clusters, such as using <Linux> infrastructure blocks in ClusterManifest.xml.
  • Provide Bash or Azure CLI examples for service creation and updates, alongside PowerShell, to improve parity for Linux/macOS users.
  • Clarify in configuration sections that both Windows and Linux clusters are supported, and link to platform-specific setup guides if available.
  • When presenting code/configuration samples, alternate or parallelize Windows and Linux examples, rather than always listing Windows first.
GitHub 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 ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation provides command-line examples exclusively using PowerShell, which is primarily a Windows tool. There are no equivalent examples for Linux/macOS users, such as using Bash, Azure CLI, or REST API calls. The PowerShell examples are presented before C# API examples, further reinforcing a Windows-first approach. This creates friction for users managing Service Fabric clusters from non-Windows environments.
Recommendations
  • Add examples using Azure CLI or REST API for managing node tags and service tag requirements, which are cross-platform.
  • Explicitly mention whether PowerShell Core (cross-platform) is supported, and provide Bash or shell script equivalents if possible.
  • Clarify any platform limitations for Service Fabric management tools and link to relevant Linux/macOS documentation.
  • Reorder examples so that cross-platform methods (REST API, Azure CLI) are presented before or alongside PowerShell.
GitHub 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: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation provides a detailed conceptual overview of Service Fabric health monitoring, which is a cross-platform feature. However, the only concrete example for reporting and evaluating health uses PowerShell cmdlets, which are Windows-centric and not available natively on Linux clusters. There are no equivalent examples for Linux/macOS users (e.g., using REST API, Azure CLI, or SDKs). The documentation also references Windows tools (PowerShell) exclusively for practical usage, creating friction for non-Windows users.
Recommendations
  • Add equivalent examples for Linux/macOS users, such as using the Service Fabric REST API, Azure CLI, or SDKs (C#, Python, etc.) to report and query health.
  • Clearly indicate that PowerShell is Windows-only and provide links or guidance for Linux/macOS alternatives.
  • Where possible, show both Windows (PowerShell) and cross-platform (REST/CLI/SDK) examples side-by-side.
  • Reference cross-platform tools and patterns before or alongside Windows-specific ones.
GitHub 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: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation page for Azure Service Fabric DNS service exhibits moderate Windows bias. While it acknowledges Linux support, most operational examples (such as setting DNS names) are provided only for Windows-centric tools like PowerShell and Visual Studio. There are no Linux-specific command-line examples (e.g., using CLI, Bash, or cross-platform tools), and the workflow for Linux clusters is described as more limited, with enabling DNS service not possible via the Azure portal. Windows tools and patterns (PowerShell, ApplicationManifest.xml in Visual Studio) are mentioned first and exclusively, with no parity for Linux-native workflows.
Recommendations
  • Provide Linux-specific examples for setting DNS names, such as using Azure CLI, Bash scripts, or editing manifests with Linux-native editors.
  • Clarify how Linux users can deploy and manage DNS service, especially for process-based services, and explicitly document any workarounds or alternative workflows.
  • Add guidance for enabling DNS service on Linux clusters outside the portal, with step-by-step instructions.
  • Include notes or tables summarizing feature parity and limitations between Windows and Linux clusters.
  • Where PowerShell is used, offer equivalent Azure CLI or REST API examples for cross-platform accessibility.
GitHub 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 detailed examples for configuring auto scaling policies in Azure Service Fabric using application manifests, C# APIs, and PowerShell. However, all CLI/script examples use PowerShell, which is Windows-centric, and there are no equivalent Linux shell (bash/CLI) examples. The documentation does mention that resource monitoring is supported for containerized applications on Linux, but practical guidance for Linux users is missing. The ordering of examples also puts PowerShell before any Linux alternatives (which are absent), reinforcing a Windows-first approach.
Recommendations
  • Add equivalent examples using Azure CLI or bash scripts for Linux users, especially for service creation and scaling policy updates.
  • Explicitly document any differences or limitations for Linux clusters, including how to manage auto scaling policies from Linux environments.
  • Where PowerShell is used, provide a note or link to Linux-compatible tooling (e.g., Azure CLI, REST API) for parity.
  • Consider reordering examples or providing a clear separation between Windows and Linux workflows.
GitHub 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_tools ⚠️ missing_linux_example
Summary
The documentation provides PowerShell-based examples and references for managing Service Fabric services, with no mention of Linux CLI equivalents (such as Azure CLI or Service Fabric CLI), nor any explicit Linux/macOS command-line examples. All command-line instructions and links are PowerShell-focused, which may create friction for Linux/macOS users.
Recommendations
  • Add equivalent Azure CLI (az sf) or Service Fabric CLI (sfctl) examples for creating and managing services, especially for commands currently shown only in PowerShell.
  • Explicitly mention cross-platform management options for Service Fabric clusters, including links to Linux/macOS tooling.
  • Where possible, provide both Windows (PowerShell) and cross-platform (CLI/REST) examples side by side.
  • Clarify in the 'Next steps' and relevant sections that PowerShell is not the only supported management interface, and link to Linux/macOS documentation.
GitHub 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 ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation provides only PowerShell-based deployment instructions and command-line examples, with no mention of Azure CLI, Bash, or Linux/macOS-compatible workflows. It also references Windows-specific tools (e.g., RDP, C: drive paths, and Windows command prompt syntax for ping), and does not offer equivalent Linux/macOS guidance for accessing VMs or running network tests.
Recommendations
  • Add Azure CLI (az) command examples alongside or in place of PowerShell commands for resource group and template deployments.
  • Include Linux/macOS-compatible instructions for accessing VMs (e.g., using SSH instead of RDP) and for running network tests (e.g., using ping from a Bash shell).
  • Use platform-neutral file paths in examples, or provide both Windows and Linux/macOS path formats.
  • Explicitly state that the templates and instructions are cross-platform, and clarify any steps that are Windows-specific.
  • Consider reordering examples or providing tabs for Windows and Linux/macOS workflows to improve parity.
GitHub 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 provides certificate management guidance for Service Fabric clusters on Azure, with a strong emphasis on Windows-centric tooling and patterns. PowerShell is the only scripting language shown for programmatic certificate enrollment, and references to Windows-specific features (such as S-channel, certificate store locations, and Key Vault VM extension for Windows) are prevalent. The documentation does not provide equivalent Linux/bash examples or discuss Linux-specific certificate handling, which may create friction for users deploying Service Fabric clusters on Linux nodes or managing certificates from non-Windows environments.
Recommendations
  • Include bash/CLI examples for certificate enrollment and management alongside PowerShell scripts.
  • Clarify which steps and tooling are applicable to Linux-based Service Fabric clusters, and provide explicit Linux guidance where possible.
  • Reference the Key Vault VM extension for Linux (if available) or alternative mechanisms for Linux VMs, and link to relevant documentation.
  • Discuss certificate store locations and access control for Linux nodes, not just Windows certificate stores.
  • Where Windows-specific features (e.g., S-channel, CERT_RENEWAL_PROP_ID) are discussed, note their applicability and provide Linux alternatives or caveats.
GitHub 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: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation provides a PowerShell-only example for bypassing Infrastructure Service throttling, with no equivalent CLI or Linux/macOS instructions. It references Service Fabric Explorer (a web tool, but often Windows-centric in usage) and omits any mention of Linux-native management tools or cross-platform command-line alternatives.
Recommendations
  • Provide equivalent Azure CLI or REST API examples for bypassing Infrastructure Service, suitable for Linux/macOS users.
  • Clarify whether the PowerShell command is required or if cross-platform alternatives exist.
  • Explicitly mention if Service Fabric Explorer and other tools are accessible and fully functional from non-Windows environments.
  • Add notes or links to Linux/macOS management guidance for Service Fabric clusters.
GitHub 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 ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation page for Initializer CodePackages in Service Fabric provides examples and guidance exclusively for Windows containers, using Windows-specific images, file paths, and commands. There are no Linux container examples or references to Linux-compatible patterns, which creates friction for users deploying Service Fabric on Linux or with Linux containers.
Recommendations
  • Add equivalent examples using Linux containers (e.g., Ubuntu or Alpine images) to demonstrate Initializer CodePackages in a cross-platform manner.
  • Include Linux-compatible file paths and shell commands (e.g., /workspace/log.txt, echo, cat, tail, etc.) in the examples.
  • Clarify in the introduction whether Initializer CodePackages are supported for Linux containers, and if so, provide guidance for Linux users.
  • If there are limitations for Linux containers, explicitly state them and link to relevant documentation.
GitHub 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: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation page on deploying custom images in Azure Service Fabric Managed Clusters demonstrates a Windows bias. The introductory sections and examples refer primarily to 'custom windows images', and the only command-line example provided uses PowerShell (New-AzRoleAssignment), with no equivalent Linux CLI or Bash example. While there are references to Linux custom image creation and Azure CLI usage, these are secondary and not illustrated with concrete examples.
Recommendations
  • Provide equivalent Azure CLI or Bash examples for role assignment and other operations, especially for Linux/macOS users.
  • Clarify that custom images can be Windows or Linux, and show examples for both where applicable.
  • Rephrase sections to avoid implying that custom images are only for Windows, unless a feature is truly Windows-only.
  • Ensure that references to Linux documentation are accompanied by actionable examples, not just links.
GitHub 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 ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation provides detailed PowerShell examples for managing Service Fabric managed cluster node types, but does not offer equivalent CLI (az CLI), Bash, or Linux/macOS shell examples. PowerShell is presented as the only scripting option, which may create friction for users on Linux or macOS who prefer or require cross-platform tools. The documentation also refers to drive letters (e.g., S, C, D), a Windows-centric concept, without clarifying Linux disk mapping. Portal and ARM template methods are platform-neutral, but scripting guidance is Windows-biased.
Recommendations
  • Add Azure CLI (az CLI) examples for all operations currently shown with PowerShell, such as adding, removing, scaling, and configuring node types.
  • Clarify disk mapping for Linux-based node types, or note any differences in how disk letters are handled on Linux VMs.
  • Explicitly state PowerShell Core (pwsh) compatibility and provide cross-platform instructions if PowerShell is required.
  • Where possible, show both PowerShell and CLI examples side-by-side, or link to equivalent CLI documentation.
  • Review and update documentation to ensure Linux/macOS users can complete all tasks without needing Windows-specific tools.
GitHub 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: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page for deny assignment policy in Service Fabric managed clusters shows a moderate Windows/PowerShell bias. PowerShell is referenced first and exclusively in several examples, with direct links to PowerShell cmdlets for key operations (deleting, restarting, reimaging NodeTypes). While Azure CLI and sfctl are mentioned in a utility table, the step-by-step examples and guidance focus on PowerShell, and there are no equivalent CLI or sfctl command examples provided for Linux/macOS users.
Recommendations
  • Add Azure CLI and sfctl command examples alongside PowerShell examples for all major operations (delete, restart, reimage NodeType).
  • In the 'Best practices' section, mention CLI and sfctl as alternatives to PowerShell, and provide links to their documentation.
  • Ensure examples and guidance do not assume PowerShell as the default tool, and present cross-platform options equally.
  • Consider ordering tool references alphabetically or by platform neutrality, rather than listing PowerShell first.
GitHub 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 are several instances where Windows tools and patterns (such as EventStore APIs, Event Log/Event Viewer, Diagnostics Agent) are mentioned first or exclusively, with Linux equivalents referenced later or less prominently. Some examples and tutorials focus on .NET applications, which are often Windows-centric, and there is a lack of explicit Linux-specific step-by-step examples or parity in tool coverage. Linux diagnostics are described as requiring 'different configuration' without detailed guidance or examples in this main page.
Recommendations
  • Ensure Linux-specific monitoring tools and workflows are described with equal detail and prominence as Windows equivalents.
  • Provide explicit Linux examples and step-by-step instructions for configuring diagnostics, collecting logs, and using monitoring agents.
  • When referencing tutorials or sample setups, include links or sections for Linux clusters and applications (e.g., .NET Core on Linux, containerized workloads).
  • Where Windows tools (Event Viewer, Diagnostics Agent) are mentioned, immediately follow with Linux alternatives (Syslog, LTTng, Azure Monitor agent) and provide usage examples.
  • Clarify which features are Windows-only and which are cross-platform, to help users quickly identify relevant guidance.
GitHub 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 ⚠️ missing_linux_example ⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation page for RunToCompletion semantics in Service Fabric demonstrates a notable Windows bias. All code examples use Windows containers (nanoserver), Windows-specific shell commands (cmd, set, exit), and reference Windows container compatibility. Querying deployment status is shown only via PowerShell and C# APIs, with no Linux shell or cross-platform CLI examples. There is no mention of Linux containers, nor examples using Linux images or shell commands.
Recommendations
  • Add equivalent examples using Linux containers (e.g., Ubuntu or Alpine images) and Linux shell commands (bash/sh) in ServiceManifest.xml.
  • Clarify whether RunToCompletion semantics are supported for Linux containers and, if so, provide Linux-specific code samples.
  • Include instructions for querying deployment status using Azure CLI, REST API, or Service Fabric CLI (sfctl), which are cross-platform.
  • Explicitly state any limitations or differences for Linux container support in Service Fabric RunToCompletion semantics.
GitHub 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 generally aims to be cross-platform, referencing both Windows and Linux clusters in several sections. However, there is a notable Windows bias: Windows-specific features (e.g., Active Directory, gMSA, BitLocker) are described in detail, while equivalent Linux guidance is missing or relegated to TODO comments. Examples and links for Windows scenarios (e.g., disk encryption, service accounts) are provided, but Linux alternatives are not, or are mentioned only in passing.
Recommendations
  • Provide explicit Linux examples and instructions for key security tasks, such as disk encryption and service account configuration.
  • Add links to Linux-specific documentation where available (e.g., encrypting disks on Linux clusters, using Linux service accounts).
  • Ensure that for every Windows-specific feature discussed, the Linux equivalent (if available) is described with equal detail, or a clear statement is made if no equivalent exists.
  • Remove or resolve TODO comments regarding Linux features, replacing them with actionable guidance or links.
  • Where examples are given (e.g., PowerShell for disk encryption), provide Bash/CLI equivalents for Linux clusters.
GitHub 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 provides next steps that prioritize Windows-centric tools: Visual Studio and PowerShell, both of which are primarily used on Windows. There are no explicit Linux/macOS CLI or cross-platform examples or references, and the recommended serialization approach (Data Contract serializer) is .NET-specific, but not Windows-only. The main content does not mention Linux/macOS alternatives for application upgrade workflows.
Recommendations
  • Add examples or references for upgrading Service Fabric applications using cross-platform tools such as Azure CLI or Service Fabric CLI (sfctl), which are available on Linux/macOS.
  • Clarify whether the PowerShell and Visual Studio tutorials are Windows-only, and provide links to equivalent Linux/macOS workflows if available.
  • Mention that Service Fabric supports Linux clusters and provide guidance or links for Linux users regarding data serialization and upgrade processes.
  • Include notes or sections for .NET Core/.NET 5+ users, as these runtimes are cross-platform.
GitHub 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: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation page prioritizes Windows-centric tools (PowerShell, Visual Studio) in both structure and example coverage. The PowerShell and Visual Studio sections are presented first and in greater detail, with explicit parameter tables and example formats, while Linux/macOS equivalents (Service Fabric CLI/SFCTL) are covered later and with less depth. There are no explicit Linux shell command examples or walkthroughs in the main content, and parameter explanations often reference PowerShell-specific syntax (e.g., hashtables) without showing equivalent Linux CLI usage.
Recommendations
  • Reorder sections so that cross-platform tools (SFCTL/CLI) are presented alongside or before Windows-specific tools.
  • Provide explicit Linux/macOS shell command examples for SFCTL, including parameter usage and JSON formatting.
  • Clarify which tools are cross-platform and which are Windows-only at the start of the article.
  • Add a comparison table showing how to perform upgrades using PowerShell, Visual Studio, and SFCTL, with example commands for each.
  • Ensure parameter explanations include both PowerShell and SFCTL syntax where applicable.
GitHub 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 the primary example for cluster and application management, and mentions Windows security as a transport option before X509 certificates. There are no Linux-specific management tool examples or mentions of cross-platform CLI alternatives, which may create friction for Linux/macOS users.
Recommendations
  • Include references to cross-platform management tools such as Azure CLI or Service Fabric CLI (sfctl) alongside PowerShell.
  • Clarify that management operations can be performed from Linux/macOS using these tools.
  • Mention Linux security options (such as certificate-based authentication) equally with Windows security in the transport subsystem section.
  • Provide links or brief examples for Linux/macOS management workflows where relevant.
GitHub 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 guidance for authoring and validating manifest XML files. It explicitly recommends opening the Service Fabric XSD schema in Visual Studio using a Windows file path, with no mention of Linux/macOS equivalents or cross-platform tooling. Additionally, PowerShell is referenced before any cross-platform CLI alternatives for service creation, and all example file paths and tooling are Windows-centric.
Recommendations
  • Provide guidance for validating manifest XML files on Linux/macOS, such as using VS Code with the XML extension, xmllint, or other cross-platform editors.
  • Include Linux/macOS file paths and instructions alongside Windows paths when referencing schema files.
  • Mention cross-platform Service Fabric CLI (sfctl) or Azure CLI for service management, not just PowerShell.
  • Clarify when a tool or workflow is Windows-only, and offer alternatives where possible.
GitHub 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: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation page heavily references PowerShell cmdlets and Windows-centric tools for managing the Service Fabric application lifecycle, often without providing equivalent Azure CLI, Service Fabric CLI (sfctl), or Linux-native examples. While REST API and .NET SDK methods are mentioned, practical command-line guidance is almost exclusively PowerShell-focused, which creates friction for Linux/macOS users.
Recommendations
  • For every PowerShell cmdlet mentioned, provide equivalent Azure CLI and/or Service Fabric CLI (sfctl) commands, especially for common lifecycle operations (deploy, upgrade, remove, etc.).
  • Add explicit Linux/macOS command-line examples where possible, or clearly indicate when a tool is cross-platform.
  • In sections describing automation (e.g., automatic cleanup), include CLI or scripting options that work on Linux.
  • Where REST API is referenced, consider providing curl or HTTPie examples for Linux users.
  • Review linked example pages to ensure Linux parity is maintained there as well.
GitHub 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 ⚠️ windows_tools ⚠️ missing_linux_example ⚠️ windows_first
Summary
The documentation page for Service Fabric application upgrades exhibits a notable Windows bias. The only concrete command-line example provided uses PowerShell cmdlets (e.g., Get-ServiceFabricApplication, Start-ServiceFabricApplicationUpgrade), which are Windows-specific tools. There are no equivalent examples for Linux/macOS users (e.g., using sfctl or REST API). Additionally, the documentation references Windows-specific components like http.sys and error messages from the Windows HTTP Server API without clarifying cross-platform implications or alternatives. The 'Next steps' section also prioritizes Visual Studio and PowerShell, both of which are primarily Windows tools, with no mention of Linux/macOS workflows.
Recommendations
  • Add equivalent Linux/macOS command-line examples using sfctl (Service Fabric CLI) or REST API for all PowerShell examples.
  • When referencing Windows-specific tools or APIs (e.g., http.sys, Windows HTTP Server API), clarify their relevance to Linux clusters and provide Linux-specific guidance or caveats.
  • In the 'Next steps' section, include links or references to Linux/macOS upgrade workflows, such as tutorials using sfctl or REST API.
  • Where possible, present cross-platform tools and examples first, or clearly indicate when a tool is Windows-only.
GitHub 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: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example ⚠️ windows_first
Summary
The documentation for restoring backups in Azure Service Fabric is heavily focused on PowerShell-based workflows, with all CLI examples and code snippets using PowerShell cmdlets and scripting. The prerequisite steps require installation of a PowerShell module (Microsoft.ServiceFabric.Powershell.Http), and all REST API usage is demonstrated via PowerShell scripts. There are no examples for Linux/macOS users (e.g., Bash, curl, Azure CLI), nor is there guidance for performing these operations outside of PowerShell. Windows tools and patterns are mentioned exclusively and first, which may create friction for users on non-Windows platforms.
Recommendations
  • Provide equivalent examples using Bash/curl for REST API calls to demonstrate how Linux/macOS users can perform backup and restore operations.
  • Document how to authenticate and interact with Service Fabric REST APIs from non-Windows environments, including certificate handling.
  • Mention Azure CLI or cross-platform tools if available for Service Fabric backup/restore operations.
  • Clarify whether the PowerShell module is required on all platforms, and if so, provide installation and usage instructions for Linux/macOS (if supported).
  • Add a note on platform compatibility and explicitly state if any steps are Windows-only.
GitHub 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 ⚠️ missing_linux_example
Summary
The documentation page provides configuration details for periodic backup in Azure Service Fabric, including examples for Azure Blob storage and file shares. The file share backup examples and instructions are exclusively Windows-centric, referencing Integrated Windows Authentication and UNC paths (\\StorageServer\BackupStore), with no mention of Linux-compatible file share access methods (such as NFS or SMB mounting on Linux). There are no Linux/macOS-specific examples or guidance for configuring backup storage on non-Windows platforms.
Recommendations
  • Add examples for configuring file share backup storage using Linux-compatible protocols (e.g., NFS, SMB via CIFS) and provide sample configuration for Linux clusters.
  • Clarify whether file share backup is supported for Linux Service Fabric clusters and, if so, document authentication and mounting procedures for Linux.
  • Where authentication is discussed, mention Linux alternatives (e.g., Kerberos, username/password via mount.cifs) and provide sample configuration.
  • Explicitly state platform limitations if file share backup is Windows-only, to avoid confusion for Linux users.
GitHub 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 ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page provides detailed instructions for scaling Service Fabric clusters, but the manual scaling steps rely exclusively on PowerShell commands (e.g., Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState) without mentioning Linux equivalents or cross-platform alternatives. Windows/PowerShell tooling is presented first and exclusively in critical operational steps, with no Bash, CLI, or Linux-specific guidance. This creates friction for Linux users, who must infer or research how to perform these actions on non-Windows platforms.
Recommendations
  • Include equivalent Azure CLI or Bash commands for all PowerShell examples, especially for node disablement and removal.
  • Clarify whether the PowerShell commands can be run from Linux/macOS using Azure PowerShell modules, or provide direct Linux-native alternatives.
  • Add explicit instructions or links for performing Service Fabric management tasks on Linux clusters, including cluster scaling and node management.
  • Ensure that cross-platform tooling (e.g., Azure CLI, REST API) is mentioned and demonstrated alongside PowerShell.
  • If certain operations are only possible on Windows, clearly state this limitation.
GitHub 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: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation page for Azure Service Fabric networking best practices shows moderate Windows bias. Several examples and explanations reference Windows-specific tools (e.g., PowerShell), mention Windows scenarios before Linux, and provide more detail for Windows use cases. Linux equivalents are sometimes mentioned but often lack parity in example depth or clarity. Some network port explanations and ARM template samples are Windows-centric, and PowerShell is referenced as the default API client without equal CLI or Linux guidance.
Recommendations
  • Provide Linux CLI (az CLI) examples alongside PowerShell for cluster management and networking tasks.
  • Ensure ARM template samples and references include both Windows and Linux cluster configurations.
  • When describing API endpoints or client tools, mention Linux-friendly options (e.g., Azure CLI, REST API) with equal prominence.
  • Clarify when a recommendation or example is Windows-specific, and offer Linux alternatives where possible.
  • Balance references to Windows and Linux in introductory and summary sections to avoid Windows-first impression.
GitHub 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 ⚠️ windows_tools ⚠️ powershell_heavy
Summary
The documentation generally presents Windows-specific tools and examples (e.g., PowerShell commands, Windows Defender, Windows security baselines) before Linux equivalents, and references Windows tooling (PowerShell, Windows Defender) without always providing Linux alternatives or parity. However, for key security tasks like secret encryption, both Windows and Linux examples are provided. Some sections (Windows Defender, security baselines) are inherently Windows-only, but their placement and prominence may create friction for Linux users.
Recommendations
  • Ensure Linux examples are presented alongside or before Windows examples in sections relevant to both platforms.
  • Clearly label Windows-only sections and, where possible, provide Linux alternatives or explicitly state when no equivalent exists.
  • Add references to Linux security best practices and tools (e.g., SELinux, AppArmor, Linux antivirus solutions) where appropriate.
  • Balance the coverage of platform-specific security guidance to avoid the perception that Windows is the default or preferred platform.
GitHub 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 Service Fabric clusters, but PowerShell is featured prominently and exclusively for some upgrade operations. Windows-specific configuration (e.g., registry keys, Windows Update settings) is described in detail, while Linux equivalents are not mentioned. Some upgrade instructions use PowerShell and MSI packages, which are Windows-centric, with no Linux alternative shown. Windows configuration details are presented before Linux ones in several sections.
Recommendations
  • Provide Linux-specific examples for cluster upgrade operations, including commands for .deb packages and shell scripts.
  • Include guidance for disabling automatic updates and configuring patch management on Linux VMs (e.g., using apt or yum, or systemd timers).
  • When mentioning registry keys or Windows Update settings, add equivalent instructions for Linux systems (such as disabling unattended-upgrades or configuring update policies).
  • Balance PowerShell examples with Bash or shell script equivalents where possible, especially for cluster management tasks.
  • Where possible, present Windows and Linux instructions side-by-side, or clearly separate them to reduce confusion.
GitHub 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 lists Service Fabric cluster settings in a platform-neutral way, but there are signs of Windows bias. Windows terminology and tools (e.g., certificate store names like 'My', references to NTLM, and Windows-specific logging) are prevalent, and Windows-centric configuration patterns (such as X.509 store locations and NTLM authentication) are described without Linux equivalents or with Windows defaults shown first. Some settings mention Windows-only features (e.g., Windows Update integration, Windows log file quotas, NTLM authentication) without clarifying Linux alternatives. Linux-specific settings are present but less visible and often appear after Windows options. There are no explicit Linux configuration examples or guidance for Linux users, and some settings (e.g., certificate management, file store service authentication) are described only in Windows terms.
Recommendations
  • Add explicit Linux configuration examples and guidance, especially for certificate management, authentication, and logging.
  • Clarify which settings are Windows-only and which have Linux equivalents; provide Linux-specific defaults and patterns where appropriate.
  • Where Windows terminology is used (e.g., 'My' certificate store), explain the Linux equivalent or alternative.
  • Ensure Linux-specific features (e.g., LinuxExternalExecutablePath, EnforceLinuxMinTlsVersion) are documented with equal prominence and detail.
  • For authentication and file store service, describe Linux-compatible approaches (e.g., use of PEM files, Linux user accounts) alongside Windows methods.
GitHub 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 consistently provides PowerShell examples for configuring Service Fabric placement policies, with no equivalent examples for Linux/macOS users (e.g., CLI, REST, or YAML). PowerShell is a Windows-centric tool, and its exclusive use may create friction for users managing Service Fabric clusters from Linux or macOS environments. Additionally, PowerShell examples are presented immediately after C# code samples, reinforcing a Windows-first approach.
Recommendations
  • Include Azure CLI examples for each placement policy, as Azure CLI is cross-platform and commonly used on Linux/macOS.
  • Document REST API approaches for configuring placement policies, if available.
  • Clarify whether PowerShell commands are supported on Linux/macOS (via PowerShell Core), and provide guidance for non-Windows users.
  • Add a note or section outlining how Linux/macOS users can perform equivalent operations, or explicitly state if certain management operations are Windows-only.
GitHub 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 page provides only PowerShell and C# examples for managing Service Fabric Application Groups, with no mention of Linux CLI equivalents or cross-platform tooling. PowerShell is a Windows-centric tool, and its exclusive use in examples creates friction for Linux/macOS users who may prefer Azure CLI, REST API, or Service Fabric CLI (sfctl). There is no explicit indication that the Application Groups feature is Windows-only, so the lack of Linux-friendly instructions is a notable bias.
Recommendations
  • Add equivalent examples using Azure CLI, REST API, or Service Fabric CLI (sfctl), which are cross-platform and usable on Linux/macOS.
  • Explicitly mention platform compatibility for PowerShell commands and provide guidance for Linux/macOS users.
  • Include a table or section summarizing all available management tools for Application Groups, indicating which are cross-platform.
  • Where possible, link to documentation for Linux/macOS setup and usage of Service Fabric management tools.
GitHub 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: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation page provides general information about Service Fabric node types and VM scale sets, but several examples and references default to Windows-centric patterns. The JSON extension snippet uses a Windows-style data path (D:\\SvcFab) without a Linux equivalent, and the 'Next steps' section links to PowerShell scripts for RDP port and admin credential changes, which are Windows-specific operations. There are no explicit Linux examples or guidance for Linux users, despite Service Fabric supporting Linux nodes.
Recommendations
  • Provide Linux-specific examples alongside Windows ones, such as using a Linux-style data path (e.g., /var/svcfab) in the extension snippet.
  • Clarify which operations (like RDP port changes) are Windows-only, and offer SSH-based guidance for Linux nodes where appropriate.
  • Include links to Linux-relevant documentation in the 'Next steps' section, such as SSH connection instructions and Linux admin credential management.
  • Explicitly state OS-specific differences in configuration properties, especially where defaults or examples are Windows-centric.
GitHub 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 ⚠️ missing_linux_example
Summary
The documentation provides a detailed conceptual overview of Cluster Resource Manager integration with Service Fabric management. However, the only command-line example shown uses Windows PowerShell (Get-ServiceFabricPartitionHealth), with no equivalent CLI or Linux/macOS example. This may create friction for users managing Service Fabric clusters from non-Windows environments.
Recommendations
  • Include equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • Explicitly mention how Linux/macOS users can retrieve partition health and interact with the Cluster Resource Manager.
  • Where PowerShell is used, add a note or link to cross-platform alternatives.
  • Consider listing both Windows and Linux/macOS command examples side-by-side for parity.
GitHub 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 all command-line examples use PowerShell exclusively, with no mention of Linux equivalents (such as Azure CLI, Bash, or REST API). PowerShell is a Windows-centric tool, and its exclusive use creates friction for Linux/macOS users. Additionally, PowerShell examples are presented before any mention of cross-platform alternatives, and there is no guidance for Linux users on how to perform these operations.
Recommendations
  • Add equivalent Azure CLI or REST API examples for service creation and metric management, which are cross-platform and usable on Linux/macOS.
  • Explicitly mention which tools are available for Linux/macOS users and provide links to relevant documentation.
  • Where PowerShell is used, clarify its platform limitations and suggest alternatives for non-Windows environments.
  • Consider including Bash script examples or instructions for using Service Fabric SDK tools on Linux.
GitHub 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 for scaling Azure Service Fabric standalone clusters demonstrates Windows bias by exclusively referencing PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) and linking to Windows Server-specific guides. There are no Linux or cross-platform examples, nor any mention of Linux-compatible tools or workflows for cluster scaling, despite Service Fabric standalone clusters being deployable on both Windows and Linux.
Recommendations
  • Include equivalent Linux instructions and examples, such as using Service Fabric CLI (sfctl) or REST APIs for cluster management.
  • Reference Linux-compatible tools and workflows for querying and updating cluster configuration.
  • Add links to documentation for scaling Service Fabric standalone clusters on Linux.
  • Clearly indicate which steps or tools are Windows-only, and provide alternatives for Linux users where possible.
GitHub 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 ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation provides PowerShell examples for configuring Service Fabric service move cost, but does not offer equivalent Linux/macOS CLI (e.g., Bash, Azure CLI, or SFCTL) examples. PowerShell is primarily a Windows tool, and its exclusive use creates friction for Linux/macOS users. The absence of cross-platform command-line instructions means Linux users may struggle to perform these operations without additional research.
Recommendations
  • Add equivalent examples using Azure CLI or SFCTL (Service Fabric CLI), which are cross-platform and supported on Linux/macOS.
  • Clearly indicate whether PowerShell commands can be run on Linux/macOS (e.g., via PowerShell Core), or provide links to relevant installation guides.
  • Where possible, show both Windows (PowerShell) and Linux/macOS (Bash/Azure CLI/SFCTL) command examples side-by-side.
  • Reference official documentation for Service Fabric CLI usage for service creation and update tasks.
GitHub 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 configuration examples using XML, JSON, PowerShell, and C# APIs. However, all command-line examples use PowerShell, which is Windows-centric, and there are no equivalent CLI or scripting examples for Linux/macOS users (e.g., Azure CLI, Bash, or REST API). PowerShell examples are presented before C# API examples, reinforcing a Windows-first approach.
Recommendations
  • Add equivalent Azure CLI or REST API examples for configuring service sensitivity and maximum load, suitable for Linux/macOS users.
  • Clarify whether PowerShell commands can be run cross-platform (e.g., with PowerShell Core), or provide Bash scripting alternatives if possible.
  • Explicitly mention Linux/macOS support and provide guidance for users managing Service Fabric clusters from non-Windows environments.
  • Consider reordering examples so that platform-neutral methods (e.g., REST API, JSON manifest edits) are shown before Windows-specific tools.
GitHub 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 provides security guidance for Azure Service Fabric clusters and standalone clusters, but consistently references Windows Server clusters when discussing standalone deployments. All example links for standalone clusters point to Windows-specific guides, and Windows authentication (Kerberos) is discussed without mention of Linux equivalents. There is no explicit guidance or examples for securing standalone Linux clusters, nor are Linux authentication patterns or tools mentioned. The document does state that the concept of secure clusters is the same for Linux or Windows, but does not provide Linux-specific instructions or parity in examples.
Recommendations
  • Add explicit guidance and example links for securing standalone Service Fabric clusters on Linux, including certificate setup and authentication patterns.
  • Include Linux-specific instructions or references for node-to-node and client-to-node security, such as relevant Linux tools for certificate management and authentication.
  • Clarify any differences or limitations for Linux clusters, and provide parity in documentation structure and examples.
  • If standalone Linux clusters are not supported, state this clearly to avoid confusion.
GitHub 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
⚠️ powershell_heavy ⚠️ windows_first ⚠️ windows_tools
Summary
The documentation provides upgrade guidance for Azure Service Fabric clusters and generally presents platform-neutral instructions. However, in sections about managing certificates and opening application ports, PowerShell is mentioned before Azure CLI, and there is no explicit mention of Linux/macOS command-line usage or examples. The link for OS patching refers specifically to Windows ('Patch the Windows operating system in your Service Fabric cluster'), and Patch Orchestration Application (POA) is described only in the context of Windows. There are no Linux-specific upgrade instructions or parity notes for OS patching, which may create friction for Linux cluster operators.
Recommendations
  • Explicitly mention and provide Azure CLI examples alongside PowerShell for all management tasks, especially for certificate and port management.
  • Clarify whether Patch Orchestration Application (POA) and OS image upgrades are available for Linux-based Service Fabric clusters, and provide links or instructions for Linux if supported.
  • Add notes or sections indicating any differences or limitations for Linux clusters, or confirm parity where it exists.
  • Where possible, avoid listing PowerShell before Azure CLI, or alternate the order to avoid implicit Windows-first bias.
GitHub 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 references PowerShell as the primary example for retrieving the cluster manifest and links to a PowerShell-based deployment guide as the next step. While .NET and REST are mentioned as alternatives, PowerShell is presented first and most prominently. There are no explicit Linux/macOS CLI examples or guidance for cross-platform tools, which may create friction for non-Windows users.
Recommendations
  • Add Azure CLI or Service Fabric CLI (sfctl) examples for retrieving the cluster manifest and managing deployments, as these are cross-platform.
  • Include explicit instructions or links for Linux/macOS users where PowerShell is referenced, such as using PowerShell Core or alternative tools.
  • Balance example ordering so that cross-platform options (e.g., REST, CLI) are presented alongside or before Windows-specific tools.
  • Clarify that PowerShell examples can be run on Linux/macOS using PowerShell Core, if applicable.
GitHub 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: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation page for upgrading an Azure Service Fabric standalone cluster exhibits a moderate Windows bias. Key upgrade and configuration instructions link to Windows Server-specific documentation (e.g., service-fabric-cluster-upgrade-windows-server.md, service-fabric-cluster-config-upgrade-windows-server.md). The patch orchestration application is described only for Windows, with no mention of Linux equivalents or guidance. There are no explicit Linux examples, and Windows terminology/tools are referenced without Linux parity.
Recommendations
  • Add or link to equivalent Linux upgrade and configuration documentation if Service Fabric standalone clusters are supported on Linux.
  • Provide Linux-specific examples and instructions for cluster upgrades, configuration changes, and patch orchestration.
  • Clarify in the introduction if Service Fabric standalone clusters are Windows-only, or explicitly state platform support.
  • If Linux is not supported, state this clearly to avoid confusion for non-Windows users.
GitHub 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 for the Azure Service Fabric application resource model demonstrates a notable Windows bias. All command-line deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) without mention of Azure CLI equivalents. The application packaging workflow is shown using Visual Studio, a Windows-centric tool, with no alternative for Linux/macOS users. No Linux/macOS-specific instructions or examples are provided for key steps such as packaging, uploading, or deploying applications.
Recommendations
  • Add Azure CLI examples for deployment and resource management alongside PowerShell examples.
  • Include instructions for packaging Service Fabric applications using cross-platform tools (e.g., dotnet CLI, SF SDK for Linux/macOS) instead of only Visual Studio.
  • Provide guidance or links for Linux/macOS users on how to zip and rename application packages, and upload them to Azure Storage using CLI or portal.
  • Explicitly state which steps are cross-platform and which are Windows-specific, to help users on non-Windows systems navigate the process.
GitHub 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: 3 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page for Azure Service Fabric Events demonstrates a moderate Windows bias. It references Windows-specific event logging mechanisms (ETW/Windows Event logs) and the Windows Azure diagnostics agent as the default method for collecting and forwarding events. There is no mention of Linux equivalents, nor are Linux-specific event collection or monitoring patterns discussed. The examples and instructions assume a Windows environment, potentially creating friction for Linux-based Service Fabric clusters.
Recommendations
  • Add documentation about how Service Fabric events are logged and accessed on Linux clusters, including supported logging mechanisms (e.g., syslog, journald, or custom log files).
  • Provide Linux-specific examples for event collection, forwarding, and integration with Azure Monitor or other monitoring tools.
  • Clarify which features or instructions are Windows-only, and offer alternative guidance for Linux users where possible.
  • Include a comparison table or section outlining differences in diagnostics between Windows and Linux clusters.
GitHub 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_tools ⚠️ windows_first
Summary
The documentation page on Service Fabric scalability provides both C# and PowerShell examples for scaling operations, but exclusively uses PowerShell for command-line examples, which is a Windows-centric tool. References to administrative actions and tooling (e.g., New-ServiceFabricService) are PowerShell-focused, with no mention of Linux-native equivalents (such as Bash, CLI, or REST API usage). Windows tooling is presented first and exclusively, creating friction for Linux users who may not use PowerShell.
Recommendations
  • Add equivalent Linux command-line examples using Azure CLI, Bash scripts, or REST API calls for service and application management.
  • Explicitly mention cross-platform management options and tooling, such as the Service Fabric CLI (sfctl), and provide usage examples.
  • Where PowerShell is referenced, clarify its platform limitations and suggest alternatives for Linux/macOS users.
  • Reorder or balance example order so that Windows and Linux approaches are presented with equal prominence.
GitHub 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 are multiple instances where Windows concepts, tools, and examples are presented first or exclusively. For example, references to cluster nodes mention auto-start Windows services and Windows executables before mentioning Linux support. PowerShell is listed first among management tools, and standalone cluster creation is only described for Windows, with Linux standalone clusters explicitly noted as unsupported. There are few Linux-specific examples or CLI-first instructions, and Windows-centric terminology (e.g., 'Windows service', 'FabricHost.exe') is used throughout, even in general sections.
Recommendations
  • When describing cluster nodes and management, provide parallel Linux details (e.g., systemd services, Linux process names) alongside Windows information.
  • List CLI tools (sfctl) and REST APIs before or alongside PowerShell, especially in cross-platform sections.
  • Add explicit Linux examples or links for cluster creation, management, and application lifecycle wherever possible.
  • Clarify which features are Windows-only and which are cross-platform, and ensure Linux parity is highlighted where available.
  • In sections where Windows executables are mentioned, add Linux equivalents or note differences in process management.
GitHub Create Pull Request
Service Fabric Overview of Azure and standalone Service Fabric clusters ...icles/service-fabric/service-fabric-deploy-anywhere.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation acknowledges both Windows Server and Linux as supported platforms for Service Fabric clusters, but it notes that standalone clusters are not available on Linux. The page does not provide Linux-specific examples or guidance, and Windows is mentioned first throughout. While the page is concept-focused and not a how-to, the lack of Linux parity in standalone cluster support is a notable omission.
Recommendations
  • Clearly state the limitations for Linux users regarding standalone clusters at the beginning of the page.
  • Provide links or guidance for Linux users on alternative deployment strategies or supported scenarios.
  • Ensure that any feature comparison tables or documentation sections explicitly highlight platform differences and offer actionable next steps for Linux users.
GitHub 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: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools
Summary
The documentation page demonstrates a moderate Windows bias. It references Windows file paths for the Service Fabric SDK schema location, mentions Visual Studio as a primary tool, and does not provide Linux/macOS equivalents or examples. The directory structure and packaging concepts are platform-neutral, but the lack of Linux/macOS tooling guidance and examples creates friction for non-Windows users.
Recommendations
  • Include instructions or references for packaging and deploying guest executables using Linux/macOS command-line tools.
  • Mention cross-platform alternatives to Visual Studio, such as Visual Studio Code or CLI-based workflows.
  • Provide Linux/macOS file path examples for SDK schema locations, if applicable.
  • Clarify which steps are platform-agnostic and which require Windows-specific tooling.
GitHub Create Pull Request
Service Fabric Manage apps for multiple environments ...e-fabric-manage-multiple-environment-app-configuration.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 examples and tooling references that prioritize Windows/PowerShell workflows (e.g., PowerShell cmdlets, Visual Studio, Deploy-FabricApplication.ps1) and mentions them before Linux equivalents. While sfctl and Jenkins are referenced, there is a lack of explicit Linux/macOS command-line examples or parity in detail, which may create friction for non-Windows users.
Recommendations
  • Add explicit Linux/macOS command-line examples for creating applications and passing parameters, such as using sfctl with sample JSON.
  • Include step-by-step instructions for parameter substitution using common Linux tools (e.g., sed, envsubst) alongside Jenkins.
  • Clarify which scripts and workflows are cross-platform and provide alternatives where Windows-specific tooling (e.g., PowerShell scripts, Visual Studio) is mentioned.
  • Reorder examples so that cross-platform or Linux/macOS options are presented alongside or before Windows-specific ones.
GitHub 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_tools ⚠️ missing_linux_example
Summary
The documentation page for Replica soft delete in Service Fabric predominantly references PowerShell-based administrative APIs (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica) and provides examples and links only for PowerShell usage. There is no mention of equivalent Linux/macOS command-line tools, nor are there examples using Service Fabric CLI (sfctl) or REST APIs, which are commonly used on non-Windows platforms. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer native tools.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl) for all administrative operations (remove, restore, query replicas).
  • Clarify whether PowerShell APIs are available cross-platform or provide alternative instructions for Linux/macOS users.
  • Include REST API references or examples where applicable.
  • Explicitly state platform requirements for each tool/API mentioned.
  • Add a section or note on how Linux/macOS users can perform these tasks.
GitHub 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, right-click Publish, Visual Studio project templates). It references PowerShell as a deployment method but does not mention or provide examples for Linux/macOS alternatives (such as Azure CLI, Bash, or cross-platform editors). There are no instructions or examples for performing equivalent tasks outside of Visual Studio or on non-Windows platforms.
Recommendations
  • Add explicit notes clarifying that StartupServices.xml is only supported for Visual Studio (Windows) deployments and is not available for Linux/macOS users.
  • Provide alternative guidance or links for Linux/macOS users on how to manage service configuration using ApplicationManifest.xml and ARM templates, Azure CLI, or other cross-platform tools.
  • Include examples or references for deploying Service Fabric applications from Linux/macOS environments, if supported, and clarify any platform limitations.
  • List non-Windows deployment options (e.g., Azure CLI, REST API) alongside PowerShell, and avoid implying PowerShell is the only method.
  • Consider reordering sections so that platform-neutral or cross-platform methods are presented before Windows/Visual Studio-specific workflows.
GitHub 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: 3 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation page for Service Fabric reliable services app manifest examples displays moderate Windows bias. It references Windows-specific tools (e.g., PowerShell module for service creation), uses Windows-centric terminology (e.g., NetworkService, Administrators group), and provides examples using Windows batch scripts (.bat) and .exe files. There is no mention of Linux equivalents (such as shell scripts or Linux service accounts), nor are Linux-specific patterns or recommendations provided. The documentation assumes a Windows environment for service setup and execution.
Recommendations
  • Include Linux-specific examples alongside Windows ones, such as using shell scripts (.sh) for SetupEntryPoint and EntryPoint.
  • Document Linux service account equivalents and how to configure principals and policies for Linux clusters.
  • Clarify which manifest features and patterns are cross-platform and which are Windows-only, especially for RunAsPolicy and system groups.
  • Add notes or links to Linux Service Fabric documentation for users deploying on Linux clusters.
  • When referencing tools (e.g., PowerShell), mention Linux alternatives (such as Azure CLI or Service Fabric CLI).
GitHub Create Pull Request
Service Fabric Overview of Azure Service Fabric ...ain/articles/service-fabric/service-fabric-overview.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 generally presents Azure Service Fabric as cross-platform, mentioning both Windows and Linux support. However, there is a subtle Windows bias: Windows development tools (Visual Studio, PowerShell) are mentioned first and in more detail than Linux equivalents, and the quickstart link points to a .NET (typically Windows-centric) example without highlighting Linux or cross-platform alternatives. Linux development tools (Eclipse, Yeoman) are mentioned, but less prominently and with less detail. No explicit Linux command-line examples or Linux-specific quickstart links are provided.
Recommendations
  • Provide equal prominence and detail for Linux development workflows, including command-line examples and links to Linux-specific quickstarts.
  • Include examples or links for deploying and managing Service Fabric clusters on Linux, using Linux-native tools.
  • Ensure quickstart and getting started sections offer both Windows (.NET/PowerShell/Visual Studio) and Linux (Java/Eclipse/Yeoman/CLI) options side-by-side.
  • Clarify that .NET Core/.NET 5+ workloads are cross-platform and provide examples for both Windows and Linux environments.
GitHub 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 Service Fabric. However, there is a notable Windows bias in several areas: HTTP.sys (a Windows-only technology) receives detailed attention, including configuration and usage examples, while there are no explicit Linux/macOS-specific instructions or examples. Windows-specific tools (e.g., netsh) and APIs are referenced without Linux equivalents. In some sections, Windows/HTTP.sys is discussed before Kestrel, and the documentation does not clarify Linux/macOS limitations or provide parity guidance for those platforms.
Recommendations
  • Clearly indicate at the start of the HTTP.sys sections that it is Windows-only, and suggest Kestrel as the cross-platform alternative for Linux/macOS users.
  • Where Windows-specific tools (e.g., netsh) or APIs are mentioned, provide a note or alternative for Linux/macOS, or clarify that these steps are not required for Kestrel.
  • Add explicit Linux/macOS guidance or examples, especially for common deployment and configuration scenarios (e.g., ServiceManifest.xml for Kestrel on Linux).
  • In summary tables and recommendations, consistently list Kestrel (cross-platform) before HTTP.sys (Windows-only), and clarify platform support.
  • Add a section or callout summarizing platform support and limitations for both web servers.
GitHub 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, with explicit Windows paths and cmdlets, but does not offer equivalent Linux or cross-platform CLI examples. PowerShell is presented before REST, and there is no mention of Service Fabric CLI (sfctl) or Bash scripting, which are common on Linux/macOS. This creates friction for non-Windows users who may not have access to PowerShell or prefer platform-agnostic tools.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • Include Bash or shell script examples for common health reporting tasks.
  • Clarify which tools are available on each platform and recommend REST or CLI for Linux/macOS users.
  • Reorder sections so REST and CLI examples are presented before or alongside PowerShell, to avoid Windows-first impression.
  • Explicitly state PowerShell examples are for Windows, and provide guidance for Linux/macOS users.
GitHub 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: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ windows_first
Summary
The documentation provides PowerShell-based deployment examples and references to Windows file paths and certificate stores before mentioning Linux equivalents. The main deployment example uses PowerShell, and the Service Fabric SDK schema path is given only in Windows format. Linux-specific details (such as certificate store location) are mentioned only briefly and after Windows instructions.
Recommendations
  • Provide equivalent Linux/macOS deployment commands (e.g., using Azure CLI or Bash scripts) alongside PowerShell examples.
  • Mention Linux file paths and certificate store locations in parallel with Windows paths, not only as a note.
  • Clarify any platform-specific differences in endpoint configuration and deployment, and link to Linux/macOS-specific guides where relevant.
  • Add explicit examples for Linux clusters, including how to deploy and manage endpoints using Linux tools.
GitHub 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: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page for Fault Analysis Service overview provides usage examples and tooling references primarily for C# (via .NET and NuGet) and PowerShell, both of which are traditionally Windows-centric. The PowerShell instructions assume use of the Service Fabric SDK and PowerShell module, with no mention of Linux/macOS equivalents (such as Bash, Azure CLI, or REST API usage). There are no examples or guidance for Linux/macOS users, nor is there any indication that the Fault Analysis Service is Windows-only.
Recommendations
  • Add examples for using the Fault Analysis Service from Linux/macOS environments, such as via Azure CLI, Bash, or REST API.
  • Clarify platform support for the Fault Analysis Service (if it is cross-platform, explicitly state so; if not, explain limitations).
  • Provide links or references to documentation for Linux/macOS users, including installation and usage instructions for Service Fabric SDK on those platforms.
  • Include sample commands or code snippets for non-Windows environments to ensure parity.
GitHub Create Pull Request
Virtual Machines Share VM images in a compute gallery ...in/articles/virtual-machines/shared-image-galleries.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 both Windows and Linux applicability and covers general Azure Compute Gallery concepts. However, there is a notable Windows bias in several areas: PowerShell examples and references are frequently shown alongside or before CLI equivalents, and some links and examples (e.g., uploading VHDs, creating specialized images) reference Windows documentation first or exclusively. Linux equivalents are sometimes mentioned, but not always with equal detail or prominence. There are also references to Windows-specific tools (Sysprep) before Linux equivalents (waagent), and some example links default to Windows pages.
Recommendations
  • Ensure that all example commands (especially PowerShell and CLI) are presented with equal prominence, ideally side-by-side or in clearly labeled tabs.
  • Where links are provided for Windows-specific tasks (e.g., uploading VHDs, creating specialized images), ensure Linux equivalents are equally visible and detailed.
  • Avoid referencing Windows tools or documentation before Linux equivalents unless there is a technical reason.
  • Add more Linux-focused examples and links where only Windows examples are currently present.
  • Review FAQ and troubleshooting sections to ensure Linux scenarios are covered as thoroughly as Windows ones.
GitHub Create Pull Request
Virtual Machines Create a VM from a generalized image in a gallery ...icles/virtual-machines/vm-generalized-image-version.md
Medium 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 PowerShell examples for creating VMs from generalized images in a gallery. However, PowerShell examples are consistently shown and detailed, and in several places, the PowerShell code is Windows-centric (e.g., Set-AzVMOperatingSystem -Windows is used by default, and credential prompts assume password authentication). In the PowerShell sections, Windows VM creation is the default, with no explicit Linux VM example or mention of Linux-specific parameters. Additionally, in the full parameter set, network security rules are configured for RDP (port 3389), which is Windows-specific, and Set-AzVMOperatingSystem -Windows is used without showing the Linux equivalent. CLI examples do show Linux VM creation (with SSH keys), but PowerShell examples are Windows-first and lack Linux parity.
Recommendations
  • Add PowerShell examples for creating Linux VMs, including use of Set-AzVMOperatingSystem -Linux and SSH key authentication.
  • In PowerShell sections, clarify how to create Linux VMs and how credential handling differs (e.g., using SSH keys vs. passwords).
  • When showing network security group rules, include both SSH (port 22) and RDP (port 3389) examples, or clarify which is for Linux and which is for Windows.
  • Consider alternating or balancing the order of Windows and Linux examples in PowerShell sections, or explicitly state which OS each example targets.
  • Add notes or links to Linux-specific PowerShell guidance where appropriate.
GitHub Create Pull Request
Virtual Machines Create a VM from a specialized image version ...icles/virtual-machines/vm-specialized-image-version.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 Azure CLI and PowerShell examples for creating VMs from specialized images, but the PowerShell examples are significantly more detailed and complex, including full network setup and VM configuration. The CLI examples are much simpler and do not cover equivalent advanced scenarios. PowerShell is a Windows-centric tool, and the lack of parity in example depth and coverage creates friction for Linux/macOS users. Additionally, PowerShell examples are presented before CLI in some sections, and there are no Bash or Linux-native scripting examples for advanced scenarios.
Recommendations
  • Expand Azure CLI examples to include full VM creation workflows, including network configuration, to match the detail provided in PowerShell examples.
  • Add Bash/Linux shell script examples for advanced scenarios, especially for users who prefer or require Linux-native tooling.
  • Ensure CLI examples are presented before or alongside PowerShell examples to avoid implicit prioritization of Windows tooling.
  • Explicitly note that PowerShell examples are primarily for Windows users, and provide links to equivalent Linux/macOS guidance where possible.
GitHub 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 base images (microsoft/windowsservercore, microsoft/nanoserver) are mentioned as default exclusions in cleanup, and the examples for 'ContainerImagesToSkip' feature Windows images first. There are no Linux-specific examples or mentions of common Linux container images, which may create mild friction for Linux users.
Recommendations
  • Include Linux container image examples (e.g., 'docker.io/library/ubuntu', 'docker.io/library/nginx') in the 'ContainerImagesToSkip' documentation.
  • Clarify that the cleanup features work for both Windows and Linux containers, if applicable.
  • Add a note or section addressing Linux container image management specifics, if any exist.
  • Balance examples by alternating or combining Windows and Linux image references.
GitHub 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 container support for both Linux and Windows. However, there is a slight Windows-first bias in some sections, such as listing Windows container runtimes and IIS scenarios before Linux equivalents. Windows-specific tools and scenarios (e.g., IIS lift-and-shift) are mentioned in detail, while Linux scenarios are less elaborated. Both Linux and Windows quickstarts and tutorials are linked, but Windows examples and tools are sometimes presented first or in more depth.
Recommendations
  • Ensure Linux examples and scenarios are given equal prominence and detail as Windows ones.
  • Where Windows-specific tools (e.g., IIS, Mirantis Container Runtime) are mentioned, provide Linux equivalents or clarify their absence.
  • Alternate the order of presenting Linux and Windows information to avoid implicit prioritization.
  • Expand Linux scenario examples to match the detail given to Windows scenarios (e.g., mention Apache/Nginx lift-and-shift for Linux).
GitHub Create Pull Request
Virtual Machine Scale Sets Spot Placement Score ...les/virtual-machine-scale-sets/spot-placement-score.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides usage instructions for Spot Placement Score via Azure portal, REST API, Azure CLI, and Azure PowerShell. The PowerShell example is given its own section and is presented after the CLI example, but both are included. There is a slight 'Windows-first' bias as PowerShell is highlighted as a primary method, and the Azure portal instructions implicitly assume a graphical interface typical of Windows environments. However, Linux parity is generally maintained via REST API and Azure CLI instructions.
Recommendations
  • Explicitly mention that Azure CLI and REST API are cross-platform and suitable for Linux/macOS users.
  • Consider listing CLI and REST API instructions before PowerShell to avoid implicit prioritization of Windows tooling.
  • Add a note clarifying that PowerShell Core is available on Linux/macOS, or link to cross-platform PowerShell documentation.
  • Where possible, include example shell commands (e.g., Bash/curl) for REST API usage to further support Linux/macOS users.
GitHub 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 Service Fabric CLI (sfctl) examples for deploying Docker Compose files to Azure Service Fabric. PowerShell examples are presented first and in greater detail, which may suggest a Windows-first approach. However, the CLI examples (sfctl) are cross-platform and allow Linux/macOS users to perform the same tasks. No Linux-specific shell examples (e.g., Bash) are given, and there is no mention of Linux-specific patterns or tools.
Recommendations
  • Clarify that sfctl is cross-platform and can be used on Linux/macOS as well as Windows.
  • Consider providing explicit Bash or shell command examples for Linux/macOS users, especially for common deployment workflows.
  • Add a note or section highlighting any platform-specific requirements or limitations (e.g., if certain features only work on Windows clusters).
  • Ensure that CLI examples are as detailed as the PowerShell ones, including upgrade and rollback workflows.
GitHub Create Pull Request
Service Fabric Azure Service Fabric container application manifest examples ...abric/service-fabric-manifest-example-container-app.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools
Summary
The documentation page demonstrates a mild Windows bias. The manifest examples are explicitly based on a Windows Server 2016 Container Sample, and Windows-specific concepts (such as 'winver' and Windows build numbers) are mentioned before or more prominently than Linux equivalents. The only tool referenced for obtaining the OS build version is 'winver', a Windows command. However, the documentation does mention Linux in the context of certificate handling and does not appear to be strictly Windows-only.
Recommendations
  • Provide equivalent Linux-based sample manifests or clarify if the examples are cross-platform.
  • When referencing how to obtain the OS build version, include Linux commands (e.g., 'uname -r' or '/etc/os-release') alongside 'winver'.
  • If features or settings differ between Windows and Linux containers in Service Fabric, explicitly document those differences and provide guidance for both platforms.
  • Consider linking to or referencing Linux container samples if available.
GitHub 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 generally describes Service Fabric concepts in a cross-platform manner, but there are subtle signs of Windows bias. Windows-specific tools and executables (e.g., FabricHost.exe, Fabric.exe, FabricGateway.exe) are mentioned first and in detail, with less emphasis on Linux equivalents or differences. The description of node startup references 'auto-start Windows service' without clarifying the Linux process or service management. Most examples of executable files use Windows-centric terminology (EXE/DLL), and Windows containers are mentioned before Docker containers on Linux.
Recommendations
  • Clarify Linux equivalents for node startup and service management (e.g., systemd, init scripts) alongside Windows services.
  • When describing executables, mention Linux binary formats (e.g., ELF, .so) and provide examples relevant to Linux/macOS.
  • Balance the order of mentioning Windows and Linux container support, or explicitly state parity.
  • Where Windows-specific tools are referenced, add notes or links to Linux-specific documentation or usage patterns.
GitHub 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
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides Azure portal, Azure CLI, and Azure PowerShell instructions for attaching/detaching VMs to/from scale sets. In each code example section, PowerShell is presented as a primary option alongside CLI, and the PowerShell examples use Windows-centric syntax (backticks, cmdlets). The CLI examples are cross-platform, but PowerShell is Windows-first and not natively available on Linux/macOS. Additionally, in troubleshooting, links for disk migration and proximity placement group removal point to Windows VM documentation, even though the feature is not Windows-specific.
Recommendations
  • Clarify that Azure PowerShell can be used cross-platform via PowerShell Core, or provide Bash/shell script equivalents for Linux/macOS users.
  • Where links point to Windows-specific documentation for generic VM features (e.g., managed disk migration, proximity placement group removal), add or reference Linux VM documentation as well.
  • Consider listing CLI examples before PowerShell, as CLI is more universally available across platforms.
  • Explicitly state that all operations can be performed on both Windows and Linux VMs, and provide example commands for both where configuration or parameters differ.
GitHub 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: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation provides both Azure CLI and PowerShell examples for most networking tasks with Azure Virtual Machine Scale Sets, but PowerShell (Windows-centric) examples are often presented before CLI (cross-platform) ones. In some sections, PowerShell is the only example given for querying resources, or CLI examples are less detailed. There are no Linux/macOS-specific shell examples (e.g., Bash scripts), and some verification steps use PowerShell exclusively. However, the majority of configuration is done via Azure CLI, ARM templates, or REST API, which are cross-platform.
Recommendations
  • Present Azure CLI (cross-platform) examples before PowerShell examples to reduce Windows-first perception.
  • Ensure every PowerShell example has an equivalent Azure CLI example, especially for verification and querying tasks.
  • Where possible, include Bash script snippets for Linux/macOS users, especially for tasks that might involve scripting.
  • Clarify that Azure CLI works on Windows, Linux, and macOS, and encourage its use for cross-platform scenarios.
  • Review sections where only PowerShell is used for querying or updating resources and add CLI equivalents.
GitHub 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 page is focused on time synchronization for Linux VMs in Azure and provides thorough Linux-specific guidance and examples. However, the introductory section discusses Windows Server 2016 time sync improvements and references Windows documentation before delving into Linux-specific details. This may create a perception of Windows-first bias, but all configuration instructions, examples, and tools are Linux-centric.
Recommendations
  • Move the Windows Server 2016 time sync discussion and references to a background section or an appendix, making it clear that the main content is Linux-focused.
  • Begin the overview with Linux time sync concepts and Azure-specific Linux features, referencing Windows infrastructure only as necessary for context.
  • Ensure that all example commands and configuration steps remain Linux-specific, as currently provided.
GitHub 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
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation provides a balanced overview of migrating to Flexible orchestration in Virtual Machine Scale Sets, but there are subtle signs of Windows bias. Windows-specific scenarios (such as VM activation and Windows updates) are mentioned before Linux equivalents (e.g., Linux package manager access), and there are no explicit Linux-focused migration examples or CLI commands. All command-line examples use Azure CLI, which is cross-platform, but the documentation does not provide Linux-specific considerations or troubleshooting steps, nor does it mention Linux tools or patterns where relevant.
Recommendations
  • Add explicit Linux migration scenarios, such as handling SSH keys, cloud-init, or Linux-specific VM extensions.
  • When listing outbound connectivity requirements, mention Linux package manager access before or alongside Windows activation and updates.
  • Include troubleshooting steps or references for common Linux VM migration issues (e.g., hostname changes, network configuration, package updates).
  • Provide examples of Linux VM extension usage or configuration in Flexible orchestration mode.
  • Ensure that any references to PowerShell are accompanied by Bash/Azure CLI equivalents, if relevant.
GitHub 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 major tasks, but PowerShell examples are consistently presented after CLI and before ARM template examples. PowerShell is a Windows-centric tool, and its inclusion may suggest a slight Windows bias, especially since Linux/macOS users typically use Azure CLI or ARM templates. However, all CLI examples are cross-platform and presented first, and no Windows-only tools or patterns are used. There are no missing Linux examples, and all instructions are applicable to Linux/macOS users.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux/macOS and Windows, and that PowerShell is primarily for Windows users.
  • Consider adding Bash script examples for common automation scenarios to further demonstrate Linux parity.
  • Clarify in introductory sections that all features described are available regardless of VM OS, unless otherwise noted.
  • If possible, add a short note for each code tab indicating platform compatibility (e.g., 'Azure CLI: Windows, Linux, macOS; PowerShell: Windows').
GitHub 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: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides both Linux (Bash/Python) and Windows (PowerShell) examples for configuring the application health extension response and installation. However, there are several instances where Windows/PowerShell examples are presented before or alongside Linux equivalents, and PowerShell is given equal prominence to Bash, which may create minor friction for Linux/macOS users. The extension installation and querying sections use both Azure CLI and PowerShell, but PowerShell is not relegated to a secondary position, and the REST API is presented last. There are no critical omissions of Linux instructions, and the documentation explicitly supports both ApplicationHealthLinux and ApplicationHealthWindows extension types.
Recommendations
  • Present Linux/Bash/Azure CLI examples before Windows/PowerShell examples in each tabbed section to reflect the majority usage on Azure and avoid implicit prioritization of Windows.
  • Clarify in introductory sections that all steps and features apply equally to both Linux and Windows VMSS instances.
  • Where possible, add explicit macOS notes or examples (e.g., for running the Python HTTP server) to further improve parity.
  • Ensure that REST API examples use ApplicationHealthLinux in at least one snippet to reinforce Linux support.
  • Consider grouping CLI and Bash examples together, and PowerShell separately, to make it easier for Linux/macOS users to follow.
GitHub Create Pull Request
Virtual Machines Create a Gallery for Sharing Resources .../blob/main/articles/virtual-machines/create-gallery.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides examples for Azure Portal, Azure CLI, PowerShell, and REST API. While CLI and REST are cross-platform, PowerShell is Windows-centric, and its inclusion as a primary example may signal a Windows bias. Additionally, PowerShell examples are presented before REST, and CLI examples are not explicitly labeled as Linux/macOS-friendly, though they are cross-platform. There is a slight 'windows_first' bias in the ordering of examples, with PowerShell given prominence alongside CLI and Portal, but no critical functionality is locked to Windows.
Recommendations
  • Clarify that Azure CLI commands work on Windows, Linux, and macOS.
  • Consider labeling PowerShell examples as 'Windows PowerShell' or 'PowerShell (Windows)' to make the distinction clear.
  • If possible, provide Bash or shell script examples for Linux/macOS users, especially for automation scenarios.
  • Reorder examples so that cross-platform tools (CLI, REST) are presented before Windows-specific tools (PowerShell).
  • Add a note for Linux/macOS users confirming that all CLI and REST steps are fully supported on their platforms.
GitHub 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
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation is focused on the Azure Key Vault VM Extension for Linux and provides comprehensive Linux-specific details. However, in several sections, Windows-oriented tools (Azure PowerShell) are presented before Linux-native tools (Azure CLI), and PowerShell examples are given more prominence or detail. This ordering may create friction for Linux users, as PowerShell is not the default or preferred automation tool on Linux. All technical instructions and examples are Linux-appropriate, and there is no use of Windows-only tools or patterns, but the documentation could better prioritize Linux-native workflows.
Recommendations
  • Present Azure CLI examples before Azure PowerShell examples, as CLI is the primary cross-platform tool and preferred on Linux.
  • Explicitly note that PowerShell examples are optional and primarily for users who prefer PowerShell on Linux.
  • Add Bash script examples for common deployment and troubleshooting tasks, as Bash is the default shell on most Linux systems.
  • Clarify in troubleshooting sections that Azure CLI commands are fully supported and provide parity with PowerShell.
  • Where PowerShell-specific warnings are given (e.g., about escaping quotes), add equivalent notes for Azure CLI or Bash if relevant.
GitHub 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 both Linux and Windows guidance and examples for creating image definitions and versions in Azure Compute Gallery. However, in several places, Windows/PowerShell examples are presented before Linux/CLI equivalents, and PowerShell is given equal or greater prominence than CLI. The CLI and REST examples are Linux-first, but the PowerShell examples default to Windows, and the portal instructions do not show OS-specific steps. Overall, Linux users can complete all tasks, but minor friction exists due to ordering and example selection.
Recommendations
  • Ensure that CLI and PowerShell examples alternate or are presented in parallel for both Linux and Windows, rather than defaulting to Windows in PowerShell and Linux in CLI.
  • In PowerShell sections, provide Linux examples first or clarify that the cmdlets work for both OS types.
  • In portal instructions, add explicit notes or screenshots for both Linux and Windows image creation flows if there are differences.
  • Where examples are shown, alternate the OS type (e.g., show a Linux PowerShell example, or a Windows CLI example) to avoid implicit bias.
  • Consider grouping OS-specific instructions together, or clearly labeling them as 'Linux' and 'Windows' for clarity.
GitHub 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, but the PowerShell example is given equal prominence despite being Windows-specific. The CLI example is cross-platform, but the tab order and structure do not clearly prioritize Linux/macOS parity. There is no explicit mention of Linux/macOS-specific considerations, and PowerShell (a Windows-centric tool) is presented as a primary method alongside CLI.
Recommendations
  • Clearly indicate that Azure CLI is the recommended cross-platform method for Linux/macOS users.
  • List the CLI example first, and explicitly note its cross-platform compatibility.
  • Add a brief note clarifying that PowerShell is primarily for Windows users, and that Linux users should use Azure CLI.
  • Consider adding a section or callout for Linux/macOS users to reinforce parity and avoid confusion.
GitHub Create Pull Request
Virtual Machines Deploy a Trusted Launch VM ...ain/articles/virtual-machines/trusted-launch-portal.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation covers both Linux and Windows Trusted Launch VM deployment, but there are some mild Windows biases. PowerShell examples are exclusively for Windows, and in several sections, Windows examples or terminology appear before Linux equivalents. For example, the PowerShell tab for VM creation only shows Windows VM creation, while CLI examples are Linux-focused. In template deployment, Linux and Windows are presented separately but equally. Overall, Linux users can complete all tasks, but Windows is sometimes prioritized in ordering and scripting.
Recommendations
  • Add PowerShell examples for Linux VM deployment (using -Linux parameter and Linux images) alongside Windows examples.
  • Where possible, present Linux and Windows examples in parallel, or alternate which is shown first.
  • Clarify in PowerShell sections which commands are for Windows and which for Linux, and provide both where supported.
  • Ensure terminology and screenshots do not assume Windows by default (e.g., mention SSH for Linux admin setup).
GitHub Create Pull Request
Virtual Machines Enable Trusted launch on existing Gen2 VMs ...rticles/virtual-machines/trusted-launch-existing-vm.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 VMs, explicitly stating applicability to both. However, there is a mild Windows bias in the ordering and tooling: PowerShell examples are included and shown before Linux-native alternatives, and PowerShell is used for ARM template deployment and VM deallocation, which is less common for Linux/macOS users. The CLI examples are cross-platform, but PowerShell is presented as a primary automation tool, which may create friction for Linux/macOS users who prefer Bash or native shell scripting.
Recommendations
  • Add Bash shell script examples for ARM template deployment and VM deallocation, or clarify that Azure CLI commands work natively on Linux/macOS.
  • Explicitly mention that Azure PowerShell is available cross-platform, but provide Bash/CLI alternatives for common operations.
  • Reorder examples so that CLI (cross-platform) instructions appear before PowerShell, or group them by OS preference.
  • Where PowerShell is used for template deployment, add equivalent Azure CLI commands.
GitHub Create Pull Request
Virtual Machines VM vCore Customization ...lob/main/articles/virtual-machines/vm-customization.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 configuring VM vCore customization, but the PowerShell section is given equal prominence to CLI, and the CLI example uses Ubuntu as the image. However, the PowerShell example is Windows-centric, and PowerShell is a Windows-first tool, though it is available cross-platform. The ordering of sections (CLI before PowerShell) is neutral, but the PowerShell example may imply a Windows bias for users who are not aware of PowerShell Core's cross-platform capabilities. No Linux-specific shell (e.g., bash) or Linux-native tools are mentioned, but the CLI example does use a Linux image.
Recommendations
  • Clarify that PowerShell examples work cross-platform with PowerShell Core, or explicitly mention this.
  • Consider adding bash or shell script examples for Linux/macOS users, especially for automation scenarios.
  • Ensure that examples and instructions do not imply that PowerShell is required for Linux/macOS users.
  • Highlight that Azure CLI is fully supported on Linux/macOS and is often the preferred tool for those platforms.
GitHub Create Pull Request