← Back to Dashboard
283
Pages Scanned
93
Pages Flagged
283
Changed Pages
32.9%
% Pages Flagged

Live Progress

🔴 Connecting...
100%
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:10 Scan started

Scan Information

Started At: 2026-02-19 00:00:10

Finished At: In Progress

Status: in_progress

Target Repo: Azure Compute

Current Phase: discovery

Files Queued: 283

Files Completed: 283

Problematic Pages

93 issues found
Service Fabric Initializer CodePackages in Service Fabric ...in/articles/service-fabric/initializer-codepackages.md
High 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 examples and guidance exclusively for Windows containers in Service Fabric, using Windows-specific images, paths, and commands (e.g., cmd, C:\ paths). There are no Linux container examples, nor any mention of Linux-compatible patterns or tools. The page assumes familiarity with Windows container development and does not address Linux users or scenarios.
Recommendations
  • Add equivalent examples for Linux containers, using Linux-based images (e.g., Ubuntu, Alpine) and Linux shell commands.
  • Include guidance on specifying Initializer CodePackages for Linux containers, with appropriate path and command syntax.
  • Clarify whether Initializer CodePackages are supported for Linux containers, and if not, explicitly state this limitation.
  • If Linux support exists, provide ApplicationManifest and ServiceManifest examples with Linux volume mounts and container policies.
  • Mention any differences or limitations between Windows and Linux container support in Service Fabric Initializer CodePackages.
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 explicitly states that the Service Fabric reverse proxy is not available for Linux clusters, and all examples, guidance, and configuration instructions are implicitly or explicitly Windows-centric. There are no Linux-specific instructions, examples, or parity guidance, and Linux users are informed that the feature is unavailable.
Recommendations
  • Clearly state at the top of the documentation that the reverse proxy feature is Windows-only, and provide links or guidance for Linux users on alternative approaches for service discovery and communication.
  • Add a section summarizing feature parity and limitations for Linux clusters, including any roadmap or alternatives.
  • If possible, provide guidance on how Linux users can achieve similar functionality (e.g., using third-party reverse proxies or custom service discovery patterns).
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: 2 bias types
Detected Bias Types
⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
Although the introduction claims Service Fabric clusters can run on both Windows Server and Linux, the documentation page is heavily focused on Windows. All security and operating system sections reference only Windows Server versions and Windows-specific authentication methods. There are no Linux-specific examples, instructions, or supported OS listings. The page mentions Linux in the description, but does not provide any Linux guidance or parity.
Recommendations
  • Clarify the current Linux support status for standalone clusters. If Linux is not supported, update the introduction to avoid misleading statements.
  • If Linux support exists or is planned, add Linux-specific instructions, examples, and supported OS listings throughout the documentation.
  • Provide parity in security configuration guidance for Linux clusters, including certificate management and authentication options.
  • Explicitly state any Windows-only limitations or features to avoid confusion for Linux users.
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: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page primarily discusses deploying custom Windows images in Service Fabric Managed Clusters, with Windows terminology and PowerShell examples shown. While Linux custom image creation is referenced, the main focus and examples are Windows-centric, and the PowerShell command is given without a Linux CLI equivalent.
Recommendations
  • Clarify at the top whether Linux node types are supported for custom images in Service Fabric Managed Clusters.
  • Provide equivalent Azure CLI examples for role assignment (e.g., az role assignment create) alongside PowerShell.
  • Include explicit guidance or examples for deploying Linux custom images if supported, such as ARM template snippets for Linux VM images.
  • Balance terminology to refer to both Windows and Linux images where applicable, rather than only 'custom windows images'.
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 ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page for RunToCompletion semantics in Service Fabric presents Windows container examples exclusively, references Windows-specific container images, and uses Windows command syntax (cmd, echo, set, ping). PowerShell is the only CLI example given for querying deployment status, with no mention of Linux or cross-platform alternatives. There is no guidance or example for Linux containers or querying status from Linux/macOS environments.
Recommendations
  • Add Linux container examples (e.g., using Ubuntu or Alpine images) alongside Windows container examples.
  • Provide equivalent shell command examples (bash/sh) for Linux containers, replacing Windows cmd syntax.
  • Include instructions for querying deployment status using Service Fabric CLI (sfctl) or REST API, which are cross-platform.
  • Clarify whether RunToCompletion semantics are supported for Linux containers, and if so, provide relevant guidance.
  • Mention any platform-specific limitations explicitly, so Linux/macOS users know what is and isn't supported.
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 provides several PowerShell-based manual scaling instructions and references Windows-centric tooling (e.g., PowerShell cmdlets like Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState) without offering equivalent Linux CLI or script examples. Windows/PowerShell instructions are presented first and exclusively in critical scaling workflows, creating friction for Linux users. While Service Fabric supports Linux clusters, the manual scaling guidance is not platform-neutral.
Recommendations
  • Add equivalent Linux CLI instructions (e.g., using sfctl or Service Fabric REST API) alongside PowerShell examples for node management.
  • Clearly indicate which steps are platform-specific and provide links or references to Linux documentation where appropriate.
  • Where possible, use platform-neutral language and tooling (e.g., ARM templates, REST API) for examples.
  • Include a section or callout for Linux users detailing how to perform scaling operations using Linux-compatible tools.
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 presents upgrade parameters for Service Fabric applications, but it exhibits Windows bias by prioritizing PowerShell and Visual Studio (Windows tools) in both structure and examples. The PowerShell and Visual Studio sections are detailed and appear first, while Linux-friendly tools (SFCTL CLI) are covered later and with less emphasis. There are no explicit Linux command examples or walkthroughs in the main content, and the parameter tables focus on PowerShell/Visual Studio, with SFCTL parameters separated. Although the 'Next steps' section links to Linux CLI guides, the main article lacks parity in examples and guidance for Linux/macOS users.
Recommendations
  • Add Linux/SFCTL CLI examples alongside PowerShell examples in parameter tables and explanations.
  • Reorganize the page so that SFCTL CLI (cross-platform) is presented equally or before Windows-specific tools.
  • Include explicit notes or guidance for Linux/macOS users in relevant sections.
  • Ensure parameter descriptions reference both Windows and Linux tools where applicable.
  • Consider adding a comparison table showing how to perform upgrades using PowerShell, Visual Studio, SFCTL CLI, and REST, with OS applicability.
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 example code for configuring auto scaling policies in Service Fabric using application manifests, C# APIs, and PowerShell. However, all CLI examples are PowerShell-based, with no equivalent Bash or Linux CLI examples. The PowerShell examples are shown alongside C# and manifest examples, but there is no mention of Linux-specific tools or commands. Additionally, the documentation does not clarify whether the PowerShell commands are usable on Linux (via PowerShell Core), nor does it provide guidance for Linux users who may prefer Bash or other scripting environments.
Recommendations
  • Add Bash or Azure CLI examples for configuring scaling policies, especially for Linux users.
  • Clarify whether PowerShell examples are compatible with PowerShell Core on Linux, or provide alternative instructions for Linux environments.
  • Mention any Linux-specific considerations or limitations when configuring auto scaling policies.
  • If certain features are Windows-only, explicitly state so to avoid confusion.
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 PowerShell example (Get-ServiceFabricPartitionHealth) for querying health reports but does not offer equivalent examples or commands for Linux/macOS environments. There is no mention of cross-platform CLI tools (such as sfctl) or REST API alternatives, which may create friction for non-Windows users.
Recommendations
  • Include equivalent examples using sfctl (Service Fabric CLI), which is cross-platform and works on Linux/macOS.
  • Mention REST API options for querying health reports, with example requests.
  • Clarify that PowerShell examples are for Windows and provide links or code snippets for Linux/macOS users.
  • Consider a table or section summarizing management tool parity across platforms.
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 for specifying parameters during application creation, with PowerShell and Visual Studio mentioned first and in detail. Linux-friendly tools like sfctl are referenced, but not explained as thoroughly, and there is no explicit Linux/macOS workflow example. The use of PowerShell and Visual Studio (Windows-centric tools) is emphasized, while Linux equivalents or cross-platform alternatives are less prominent.
Recommendations
  • Add explicit Linux/macOS workflow examples, such as using sfctl from Bash or install.sh scripts.
  • Provide sample shell commands for parameter passing on Linux/macOS.
  • Clarify which tools are cross-platform and which are Windows-only.
  • Ensure that Linux/macOS users are guided on how to perform equivalent tasks without PowerShell or Visual Studio.
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 ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides only PowerShell-based deployment commands and examples, with no mention of Azure CLI or Bash equivalents. Windows-specific tools (PowerShell, RDP) are referenced exclusively or before alternatives, and even basic connectivity checks use Windows command prompt syntax. There are no Linux/macOS-specific instructions or examples, which creates friction for non-Windows users.
Recommendations
  • Add Azure CLI (az) command examples alongside PowerShell for template deployments and resource creation.
  • Include Bash shell examples for connectivity checks (e.g., using ping from Linux/macOS terminals).
  • Mention SSH as an alternative to RDP for accessing VMs, especially for Linux users.
  • Clarify that Service Fabric clusters can be managed from any OS, and provide cross-platform guidance where applicable.
  • Consider reorganizing examples so that cross-platform tools (Azure CLI, SSH) are presented before or alongside Windows-specific 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 ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page for the Fault Analysis Service overview provides usage instructions primarily for C# and PowerShell, with explicit mention of the Service Fabric SDK and PowerShell module installation. There are no examples or instructions for Linux/macOS users, such as using CLI tools or REST APIs, nor is there mention of cross-platform alternatives. This creates friction for Linux/macOS users who may not have access to PowerShell or Windows-specific SDKs.
Recommendations
  • Add examples for using the Fault Analysis Service via Azure CLI or REST API, which are cross-platform.
  • Clarify whether the Fault Analysis Service APIs can be accessed from Linux/macOS environments and provide relevant instructions.
  • Mention any limitations or prerequisites for Linux/macOS users, and provide guidance for equivalent tooling.
  • If PowerShell is required, note the availability of PowerShell Core on Linux/macOS and provide installation instructions.
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 page provides extensive PowerShell examples and references Windows-specific tools and extensions (e.g., Key Vault VM extension for Windows, S-channel, Windows certificate store concepts). While the core certificate management concepts are cross-platform and Azure-centric, the hands-on automation and scripting guidance is heavily Windows-focused, with PowerShell as the primary scripting language and Windows-specific mechanisms discussed in detail. There is minimal mention of Linux or cross-platform equivalents, and Windows patterns/tools are presented first and exclusively in critical automation sections.
Recommendations
  • Add equivalent Bash/CLI examples for certificate enrollment and management, especially for Key Vault operations.
  • Document how certificate provisioning and autorollover can be achieved on Linux-based Service Fabric clusters, including any differences in VM extensions or certificate store handling.
  • Clarify which steps or tools are Windows-only and provide guidance for Linux/macOS users where possible.
  • Reference or link to Linux-specific documentation for Service Fabric certificate management if available.
  • Where PowerShell is used, offer Azure CLI or REST API alternatives for cross-platform automation.
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: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation provides a thorough conceptual overview of X.509 certificate-based authentication in Service Fabric clusters, but exhibits Windows bias in several ways. Windows-specific terminology (e.g., certificate stores like LocalMachine\My), references to Windows APIs (Win32 CryptoAPI, CertGetCertificateChain), and troubleshooting instructions (event logs, CAPI2 logging) are presented first and in detail. Linux equivalents are mentioned briefly or parenthetically, but not explained or exemplified. No Linux-specific troubleshooting guidance or certificate store management examples are provided.
Recommendations
  • Add explicit Linux examples for certificate store paths and management (e.g., using openssl, Linux certificate directories).
  • Provide troubleshooting guidance for Linux nodes, including log locations and relevant tools.
  • When referencing Windows APIs or tools, also mention Linux equivalents (e.g., OpenSSL, systemd journal, /var/log).
  • Include Linux-specific error codes and remediation steps where applicable.
  • Ensure that all configuration examples (manifest XML, JSON) clarify any OS-specific differences.
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: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides examples for configuring Service Fabric managed cluster node types using the Azure Portal, ARM templates, and PowerShell. PowerShell is the only CLI example provided, and it is presented as the exclusive scripting option for command-line operations. There are no examples or mentions of Linux/macOS-compatible CLI tools (such as Azure CLI or Bash scripts), and PowerShell is shown before any Linux alternatives (which are missing). This creates friction for Linux/macOS users who may not have access to PowerShell or prefer Azure CLI.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all command-line operations (adding, removing, scaling node types, etc.).
  • Explicitly mention that PowerShell examples are Windows-centric and provide guidance for Linux/macOS users.
  • Consider including Bash script samples or references to cross-platform tools where possible.
  • Clarify whether all operations can be performed with Azure CLI or if PowerShell is required for certain advanced scenarios.
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: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides a PowerShell-only example for bypassing Infrastructure Service, and references Service Fabric Explorer (a GUI tool typically used on Windows). No Linux/bash equivalents or cross-platform CLI alternatives are mentioned. Most instructions and tooling references implicitly assume Windows environments, creating friction for Linux/macOS users.
Recommendations
  • Add equivalent bash or Azure CLI examples for cluster operations, especially for bypassing Infrastructure Service.
  • Clarify whether Service Fabric Explorer is available cross-platform or provide alternatives for Linux/macOS users.
  • Mention any prerequisites or limitations for Linux/macOS users explicitly.
  • Where possible, provide links to cross-platform tools or documentation.
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: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page provides examples and links for Azure PowerShell prominently, with PowerShell-based actions mentioned first in the 'Best practices' section. While Azure CLI is listed as an ARM-backed tool, PowerShell is emphasized for operational tasks, and no Linux-specific command examples or shell scripts are provided. The page does not exclusively reference Windows tools, but the focus on PowerShell may create friction for Linux/macOS users.
Recommendations
  • Add explicit Azure CLI examples for key operations (e.g., deleting NodeTypes, restarting/reimaging scale sets) alongside PowerShell examples.
  • Mention cross-platform tools (like Azure CLI and sfctl) earlier and equally in the 'Best practices' section.
  • Clarify that Azure PowerShell is available cross-platform, but provide CLI alternatives for Linux/macOS users.
  • Where possible, provide sample commands for both PowerShell and CLI for parity.
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: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page provides management guidance for Service Fabric Explorer blocking operations. It consistently references Az PowerShell cmdlets (e.g., Remove-AzResource, AzSF PowerShell cmdlets) for resource operations, and only briefly mentions the Azure CLI ('az resource') for deleting applications. There are no explicit Linux/macOS examples or references to cross-platform tools, and PowerShell-based instructions are presented first and most often.
Recommendations
  • Add explicit Azure CLI examples for all operations (e.g., unprovisioning application type versions, creating applications/services, scaling, and deletions), since Azure CLI is cross-platform and works on Linux/macOS.
  • Where PowerShell cmdlets are referenced, provide equivalent Azure CLI commands alongside, and clarify which tools are available on which platforms.
  • Consider reorganizing sections so that cross-platform tools (Azure CLI) are presented before or alongside PowerShell examples.
  • Add notes or guidance for Linux/macOS users, indicating how they can perform the same operations without PowerShell.
GitHub Create Pull Request
Service Fabric Migrate an Azure Service Fabric cluster to availability zone support ...ce-fabric/migrate-service-fabric-availability-zones.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides migration guidance for Azure Service Fabric clusters to availability zone support. While most of the guidance is platform-neutral and focuses on Azure Resource Manager templates, the only explicit command-line examples are PowerShell-based and reference Windows tools (e.g., Service Fabric PowerShell cmdlets, AzureRm modules). The PowerShell examples are given exclusively, with no equivalent Bash, Azure CLI, or Linux-native instructions. Additionally, sample templates referenced are often for Windows (e.g., '15-VM-Windows-Multiple-AZ-Secure'), and Windows paths (e.g., 'D:\\SvcFab') are used in configuration snippets. Linux equivalents are not provided or are mentioned only in passing.
Recommendations
  • Add Azure CLI or Bash examples for all migration steps currently shown only in PowerShell.
  • Reference and link to Linux/Ubuntu sample templates equally alongside Windows templates.
  • When showing configuration snippets, use platform-neutral paths or provide both Windows and Linux examples (e.g., 'D:\\SvcFab' and '/var/svcfab').
  • Explicitly mention that Service Fabric clusters can run on Linux and provide guidance for Linux users where appropriate.
  • Include notes or sections for Linux-specific considerations, such as certificate management or node disabling/removal using cross-platform tools.
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 covers Azure Service Fabric application security in a cross-platform manner, but several sections show Windows bias. Windows-specific features (e.g., AD accounts, gMSA, BitLocker) are mentioned before Linux equivalents or without Linux parity. Some examples and links are Windows-centric (e.g., disk encryption via PowerShell, running services as AD users/groups), and Linux-specific guidance is missing or only briefly referenced. The section on encrypting disks has a TODO for Linux, indicating incomplete Linux coverage.
Recommendations
  • Add explicit Linux examples and guidance for disk encryption, including links to Azure documentation for encrypting disks on Linux VMSS clusters.
  • When mentioning Windows-specific features (e.g., AD accounts, gMSA, BitLocker), clarify Linux alternatives or limitations, and provide links to relevant Linux documentation.
  • Ensure parity in examples for running services under different accounts, showing both Windows and Linux approaches.
  • Review the order of presentation so Linux options are not consistently secondary to Windows options.
  • Complete the TODO for Linux disk encryption and BitLocker alternatives.
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 provides monitoring guidance for Azure Service Fabric clusters on both Windows and Linux, but there are several areas where Windows tools and patterns are mentioned first or exclusively. Windows-specific tools (Event Log, Event Viewer, Diagnostics Agent) are referenced before Linux equivalents, and some example/tutorial links focus on .NET/Windows scenarios. Linux alternatives are sometimes mentioned, but often as secondary or with less detail. There are few explicit Linux-focused examples or walkthroughs, and some features (like EventStore APIs) are noted as Windows-only without Linux alternatives or workarounds.
Recommendations
  • Ensure Linux monitoring tools and patterns are described with equal prominence and detail as Windows equivalents.
  • Add Linux-focused example walkthroughs and tutorials, especially for application monitoring and cluster diagnostics.
  • Where Windows-only features are mentioned (e.g., EventStore APIs), provide clear guidance or links for Linux users to achieve similar outcomes.
  • When referencing tools (e.g., Service Fabric Explorer, logging frameworks), clarify cross-platform compatibility and provide Linux/macOS setup instructions.
  • Avoid listing Windows tools or patterns first unless they are truly more relevant; alternate order or group by OS where appropriate.
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 ⚠ī¸ windows_first
Summary
The documentation page for the Service Fabric application lifecycle consistently references PowerShell cmdlets and Windows-centric tooling throughout all lifecycle phases (deploy, test, upgrade, remove, maintenance). While REST API and .NET methods are also mentioned, PowerShell examples are prominent and often listed before cross-platform alternatives. There is minimal mention of Linux-specific tools or CLI usage (such as sfctl or Azure CLI), and no explicit Linux/macOS examples are provided. The inclusion of PowerShell as the primary automation method and lack of Linux parity creates friction for non-Windows users.
Recommendations
  • Add explicit examples using sfctl (Service Fabric CLI) and Azure CLI for each lifecycle phase, especially for deployment, upgrade, and removal.
  • Ensure that cross-platform tools are mentioned alongside PowerShell cmdlets, not after or instead of them.
  • Provide sample commands and workflows for Linux/macOS environments, including file management and automation.
  • Clarify which methods and tools are available on Linux clusters and which are Windows-only.
  • Consider reordering examples so that REST API, sfctl, and Azure CLI are presented before or alongside PowerShell.
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 for 'Advanced Application Upgrade Topics' in Azure Service Fabric is heavily focused on PowerShell cmdlets and Windows-centric tooling. All command-line examples use PowerShell, and references to Service Fabric management are exclusively via PowerShell commands. There is no mention of Linux/macOS equivalents, such as the Service Fabric CLI (sfctl), nor are cross-platform examples provided. The documentation assumes the reader is using Windows and PowerShell, creating friction for Linux/macOS users who must translate instructions to their environment.
Recommendations
  • Add equivalent examples using the Service Fabric CLI (sfctl), which is cross-platform and supported on Linux/macOS.
  • Mention that PowerShell examples are for Windows and provide links or instructions for Linux/macOS users.
  • Where possible, provide ARM template or REST API examples alongside PowerShell to ensure platform neutrality.
  • Update 'Next steps' to include tutorials for Linux/macOS users, such as upgrading applications using sfctl.
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 links to application upgrade tutorials using Visual Studio and PowerShell, both of which are primarily Windows tools. The PowerShell example is explicitly mentioned, while there is no reference to Linux-native tools or CLI equivalents for application upgrades. The serialization discussion is focused on C# and .NET, but this is appropriate for Service Fabric workloads and does not constitute bias. However, the upgrade guidance leans towards Windows-centric tooling.
Recommendations
  • Add references or links to application upgrade tutorials using Azure CLI or Service Fabric CLI (sfctl), which are cross-platform and commonly used on Linux/macOS.
  • Clarify whether PowerShell Core (pwsh) is supported for Linux/macOS users, or provide alternative instructions for those environments.
  • Consider including examples or guidance for upgrading applications from Linux/macOS environments, if supported by Service Fabric.
  • If Visual Studio is Windows-only, mention cross-platform alternatives such as Visual Studio Code or command-line tools.
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 mentions PowerShell cmdlets as a primary management interface for Service Fabric, without referencing equivalent Linux/macOS tooling (such as Azure CLI or REST APIs). Additionally, Windows security is mentioned alongside X509 certificates in the transport subsystem, with no discussion of Linux authentication patterns. These choices suggest a Windows-first bias, though most architectural concepts are platform-neutral.
Recommendations
  • Add references to Linux/macOS-compatible management tools, such as Azure CLI and REST APIs, alongside PowerShell.
  • Clarify that PowerShell cmdlets are available cross-platform, or provide Linux/macOS-specific examples where relevant.
  • Mention Linux authentication mechanisms (e.g., certificate-based, SSH) in the transport subsystem discussion.
  • Ensure that all platform-neutral concepts are illustrated with examples or notes for both Windows and Linux environments.
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_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page for restoring backups in Azure Service Fabric is heavily biased towards Windows and PowerShell usage. All code examples and instructions rely on PowerShell modules and cmdlets, with no mention of Linux/macOS-compatible tooling or CLI alternatives. The prerequisite section explicitly requires installation of a PowerShell module, and all REST API usage is demonstrated via PowerShell scripts. There are no Bash, Azure CLI, or curl examples, nor any guidance for non-Windows environments.
Recommendations
  • Add equivalent Bash or shell script examples using curl or HTTPie for REST API calls.
  • Document how to use Azure CLI or other cross-platform tools to trigger backup and restore operations.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is supported on PowerShell Core (pwsh) for Linux/macOS, and provide installation instructions if so.
  • Explicitly state any limitations or requirements for Windows-only tooling, and provide workarounds or alternatives for Linux/macOS users.
  • Consider including a section or callout for Linux/macOS users, outlining supported approaches and any differences.
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 for Service Fabric application upgrades demonstrates a notable Windows bias. PowerShell is used exclusively in code examples, and Windows-specific tools (e.g., http.sys) are referenced without Linux equivalents. There are no CLI or Linux-native examples, and PowerShell-based upgrade instructions are presented first and exclusively. This creates friction for Linux/macOS users, who may use Service Fabric clusters on Linux or need cross-platform automation.
Recommendations
  • Add equivalent Azure CLI or Service Fabric CLI (sfctl) examples for all PowerShell commands, especially for application parameter retrieval and upgrade operations.
  • Explicitly mention cross-platform tools and workflows where possible, and clarify any Windows-only limitations.
  • When referencing Windows-specific components (e.g., http.sys), provide Linux equivalents or note if the limitation is Windows-only.
  • Reorder or parallelize examples so that Linux/macOS and Windows instructions are presented together or with equal prominence.
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 and the Microsoft.ServiceFabric.Powershell.Http module, with all command-line examples using PowerShell syntax and cmdlets. There are no equivalent examples for Linux/macOS users (e.g., using Bash, curl, or cross-platform Service Fabric CLI tools). The only alternative mentioned is Service Fabric Explorer (a web UI), but no guidance is provided for Linux command-line users.
Recommendations
  • Provide equivalent examples using Bash and curl for REST API calls, including certificate authentication steps for Linux/macOS.
  • Mention and demonstrate the use of cross-platform Service Fabric CLI tools (if available) for backup operations.
  • Clarify in the prerequisites whether the PowerShell module is supported on PowerShell Core (pwsh) on Linux/macOS, or if it is strictly Windows-only.
  • Add a section or callout for Linux/macOS users explaining how to perform on-demand backups without relying on Windows-specific tools.
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 ⚠ī¸ windows_first
Summary
The documentation page is generally platform-neutral, focusing on Azure Service Fabric's backup configuration concepts and REST APIs. However, in the 'File share' backup storage section, examples and instructions exclusively reference Windows-style file shares (\\StorageServer\BackupStore) and Integrated Windows Authentication, without mentioning or providing Linux-compatible alternatives (such as SMB mounting on Linux or NFS). The documentation also describes Windows authentication patterns first and does not clarify Linux support or provide parity guidance.
Recommendations
  • Add explicit guidance for Linux clusters, including how to configure file share backup storage using SMB or NFS mounts on Linux.
  • Provide examples for mounting and accessing file shares from Linux nodes, including authentication options (e.g., username/password, Kerberos).
  • Clarify whether Integrated Windows Authentication is required or if Linux-compatible authentication methods are supported.
  • Mention any limitations or considerations for Linux clusters regarding file share backup storage.
  • If file share backup is Windows-only, state this clearly to avoid confusion.
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 Resource Manager templates, but PowerShell is featured prominently and used for cluster upgrade operations without Linux shell equivalents. Windows-specific tools and registry keys are mentioned for VM patching, and PowerShell is used exclusively for manual cluster upgrades. Windows configuration properties are shown before Linux equivalents, and Linux-specific guidance is less detailed.
Recommendations
  • Add Bash or Linux shell equivalents for manual cluster upgrade steps (e.g., using deb packages and Linux commands).
  • Provide Linux-specific VM configuration examples, such as disabling automatic updates for Linux VMs.
  • Include Linux registry/configuration guidance where relevant, or clarify when steps are Windows-only.
  • Ensure Linux examples are given equal prominence and detail as Windows examples, especially for upgrade and patching scenarios.
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 page provides a comprehensive reference for Service Fabric cluster settings, but exhibits mild Windows bias in several areas. Windows terminology (e.g., 'Windows Fabric', 'Windows only') is used in parameter descriptions, and Windows certificate store names ('MY', 'LocalMachine') are referenced without Linux equivalents or clarification. Some settings (e.g., NTLM authentication, Windows Update integration, log file settings) are marked as 'Windows only' or default to Windows values, with Linux-specific guidance missing or less prominent. The introductory guidance and links reference Windows standalone clusters before Linux, and Linux-specific settings (like certificate folders or executable paths) are less visible or explained. No explicit Linux examples or parity guidance are provided for settings that differ between platforms.
Recommendations
  • Add Linux-specific examples and guidance for settings where behavior or defaults differ (e.g., certificate stores, log file locations, NTLM authentication).
  • Clarify which parameters are Windows-only and which are cross-platform, and provide Linux equivalents or alternatives where possible.
  • Ensure Linux terminology and paths are shown alongside Windows ones, especially for certificate management and file paths.
  • Add explicit notes or tables summarizing platform-specific differences for key settings.
  • Review introductory guidance and links to ensure Linux clusters are referenced equally and not only after Windows.
  • Where settings are marked 'Windows only', provide Linux alternatives or state if the feature is unavailable.
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
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation provides both Windows and Linux guidance in several areas, but there are notable Windows biases. Windows/PowerShell examples and terminology are often presented first or exclusively (e.g., PowerShell APIs, Windows container networking, ARM template samples for Windows clusters). Some explanations reference Windows-specific tools (e.g., netsh, PowerShell) without Linux equivalents. Linux examples are sometimes missing or less detailed, and Windows-centric scenarios (like patching) are described in more depth.
Recommendations
  • Ensure Linux examples (e.g., CLI commands, Linux container networking) are provided alongside Windows/PowerShell examples.
  • Where PowerShell or Windows tools are mentioned, add equivalent Linux commands (e.g., show dynamic port range on Linux).
  • Balance the order of examples and explanations so Linux is not consistently secondary.
  • Expand Linux-specific best practices, such as patching, monitoring, and application networking.
  • Provide ARM template samples for Linux clusters with NSG setup, not just Windows.
  • Clarify when guidance is Windows-only and provide Linux alternatives where possible.
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 ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation provides both Windows and Linux guidance for key security tasks, but Windows-specific examples (e.g., PowerShell commands, Windows Defender, Windows security baselines) are often presented first or in greater detail. Windows tools and terminology (PowerShell, Windows Defender, DSC) are mentioned exclusively or before Linux equivalents. Some sections (e.g., Windows Defender, Windows security baselines) are Windows-only, but these are clearly marked as such. Linux examples are present for certificate generation and secret encryption, but Windows examples are more prominent and detailed.
Recommendations
  • Ensure Linux examples are presented alongside Windows examples, not after them, and with equal prominence.
  • Where possible, provide Linux equivalents for security baseline guidance (e.g., reference CIS Linux benchmarks or Azure Linux security extensions).
  • Add clarifying notes when a feature or tool is Windows-only, and link to Linux alternatives or best practices.
  • For sections like certificate management and secret encryption, ensure Linux instructions are as detailed as Windows instructions.
  • Consider structuring sections so that Windows and Linux guidance are parallel, rather than Windows-first.
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 ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page provides general information about Azure Service Fabric node types and virtual machine scale sets, but there are subtle signs of Windows bias. While the JSON extension snippet references both 'ServiceFabricLinuxNode' and 'ServiceFabricNode', the example settings (e.g., 'dataPath': 'D:\\SvcFab') use Windows-style paths. Additionally, the 'Next steps' section links to PowerShell scripts for RDP port changes and admin credential updates, which are Windows-centric tasks, without mentioning equivalent Linux guidance or SSH examples.
Recommendations
  • Provide Linux/Unix-style examples for paths (e.g., '/var/svcfab') alongside Windows paths in configuration snippets.
  • Add links or guidance for managing Linux nodes, such as SSH access, changing SSH port ranges, and updating Linux admin credentials.
  • Ensure parity in 'Next steps' by including Linux-focused operational tasks and scripts.
  • Clarify when examples are Windows-specific and offer Linux alternatives where possible.
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 page provides code examples in C# and PowerShell for configuring Service Fabric placement policies, but does not include equivalent Linux/macOS CLI or scripting examples (e.g., Bash, Azure CLI). PowerShell is featured prominently and exclusively for command-line configuration, suggesting a Windows-centric approach. There is no mention of Linux tools or cross-platform alternatives, and PowerShell examples are shown before any Linux equivalents (which are missing).
Recommendations
  • Add Azure CLI examples for configuring placement policies, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include Bash or shell script snippets where applicable, especially for service deployment and configuration.
  • Explicitly mention whether the PowerShell commands can be run on PowerShell Core (cross-platform) or if they are Windows-only.
  • Provide guidance for Linux/macOS users on how to achieve the same configurations, referencing relevant tools or APIs.
  • Clarify any platform-specific limitations or requirements for Service Fabric clusters (e.g., if certain policies are only supported on Windows nodes).
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: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page provides only PowerShell and C# examples for managing Application Groups in Service Fabric clusters. PowerShell is a Windows-centric tool, and no equivalent Linux/macOS CLI or scripting examples (such as Bash, Azure CLI, or REST API) are given. The PowerShell examples are consistently presented before C# code, reinforcing Windows-first patterns. There is no mention of Linux-native tools or cross-platform approaches, creating friction for Linux/macOS users.
Recommendations
  • Add Azure CLI examples for all operations (creation, update, querying, removal) alongside PowerShell.
  • Include REST API sample calls for managing Application Groups, which are platform-agnostic.
  • Explicitly note any limitations or differences for Linux-based Service Fabric clusters, if applicable.
  • Consider Bash scripting examples or references to cross-platform tools where possible.
  • Clarify whether PowerShell examples are usable on PowerShell Core (cross-platform) or only Windows PowerShell.
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 configuration examples for both Windows (ClusterManifest.xml) and cross-platform/standalone (ClusterConfig.json) deployments, but consistently presents Windows-specific XML examples first and includes PowerShell commands for service creation and updates without equivalent Linux CLI or SDK examples. The use of WindowsServer in XML examples and PowerShell for operational tasks may create friction for Linux users, though JSON-based configuration and .NET SDK examples are also present.
Recommendations
  • Present Linux/standalone (ClusterConfig.json) examples before or alongside Windows (ClusterManifest.xml) examples to avoid Windows-first ordering.
  • Add equivalent Linux CLI (e.g., Azure CLI, sfctl) or bash script examples for service creation and updates, alongside PowerShell commands.
  • Clarify when XML examples are Windows-only and when JSON examples are cross-platform, to help users identify relevant sections.
  • Explicitly mention Linux support for standalone Service Fabric clusters and link to Linux-specific operational documentation where relevant.
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 code examples for managing Service Fabric metrics primarily in C# and PowerShell. PowerShell is a Windows-centric tool, and no equivalent Linux/macOS CLI examples (such as Azure CLI or Bash scripts) are provided. The PowerShell examples are given alongside C# code, but there is no mention of cross-platform tools or patterns for Linux users. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other scripting environments.
Recommendations
  • Add Azure CLI examples for service creation and metric management, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Mention Bash scripting or REST API usage for metric configuration and dynamic load reporting, with sample commands.
  • Clarify whether the PowerShell commands can be run in PowerShell Core (which is cross-platform) or if they require Windows PowerShell.
  • Provide guidance or links for Linux/macOS users on how to perform equivalent operations without PowerShell.
  • Consider reordering examples so that cross-platform tools are shown first or alongside Windows-specific tools.
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_first ⚠ī¸ missing_linux_example
Summary
The documentation page on scaling Azure Service Fabric standalone clusters exhibits Windows bias by exclusively referencing PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) and linking to Windows Server-specific guides. There are no Linux-specific examples, tools, or instructions, and the terminology and guidance assume a Windows environment, despite standalone clusters being theoretically cross-platform.
Recommendations
  • Add equivalent Linux instructions, including examples using Bash, CLI, or relevant Linux tools for cluster manifest querying and configuration upgrades.
  • Clarify whether standalone Service Fabric clusters can be managed on Linux, and if so, provide parity in documentation for Linux users.
  • If PowerShell is required on Linux, explicitly state this and provide installation guidance.
  • Link to or create Linux-specific guides for scaling standalone clusters, if supported.
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: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page references Windows-specific upgrade and configuration guides (e.g., service-fabric-cluster-upgrade-windows-server.md, service-fabric-cluster-config-upgrade-windows-server.md) and the Patch Orchestration Application for Windows. There are no explicit Linux examples, tools, or links to Linux-specific upgrade/configuration documentation. The page does not clarify whether Linux clusters are supported or provide guidance for Linux users.
Recommendations
  • Add explicit guidance or links for upgrading Service Fabric standalone clusters running on Linux, if supported.
  • Provide Linux-specific examples or documentation references alongside Windows ones.
  • Clarify in the introduction whether the guidance applies to both Windows and Linux clusters, or is Windows-only.
  • Mention Linux equivalents for patch orchestration or cluster configuration, if available.
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 ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides PowerShell examples for configuring Service Fabric service move cost, but does not offer equivalent Linux CLI or bash examples. PowerShell is primarily a Windows tool, and its exclusive use in examples creates friction for Linux/macOS users. Additionally, PowerShell examples are presented before C# code, reinforcing a Windows-first bias. No Linux-native tools or commands (such as Azure CLI or REST API) are mentioned for these operations.
Recommendations
  • Add equivalent Azure CLI or REST API examples for configuring and updating move cost, which are cross-platform and usable from Linux/macOS.
  • Explicitly mention whether PowerShell commands can be run on Linux/macOS (via PowerShell Core), or clarify if they are Windows-only.
  • Consider providing bash or shell script examples for common operations, or link to relevant cross-platform tooling.
  • Reorder examples so that cross-platform methods (Azure CLI, REST API) are shown before or alongside PowerShell.
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 ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation provides PowerShell examples for managing node tags and service requirements, but does not offer equivalent Linux/macOS command-line examples (such as Azure CLI, Bash, or REST API usage). PowerShell is primarily a Windows tool, and its prominence creates friction for Linux/macOS users. The documentation also references PowerShell before C# APIs and omits mention of cross-platform tools or workflows.
Recommendations
  • Add examples using Azure CLI or REST API for managing node tags and service requirements, as these are cross-platform and accessible to Linux/macOS users.
  • Explicitly state whether PowerShell commands are supported on Linux/macOS (via PowerShell Core), and provide guidance if so.
  • Consider including Bash or shell script examples where appropriate, or reference relevant Service Fabric CLI tools if available.
  • Reorder examples so that cross-platform tools (REST API, CLI) are presented before or alongside PowerShell.
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_tools ⚠ī¸ missing_linux_example
Summary
The documentation provides extensive PowerShell examples for configuring service sensitivity and maximum load in Azure Service Fabric, but does not offer equivalent Linux/macOS CLI examples (such as Bash, sfctl, or REST API). The PowerShell-centric approach and references to Windows tools may create friction for Linux users, even though Service Fabric supports cross-platform management.
Recommendations
  • Add equivalent examples using sfctl (Service Fabric CLI) for Linux/macOS users, especially for service creation and updates.
  • Include REST API examples for configuring sensitivity and maximum load, which are platform-agnostic.
  • Explicitly mention cross-platform support and clarify which tools are available on each OS.
  • Reorder sections so that cross-platform or platform-agnostic methods (e.g., Application Manifest, REST API) are presented before Windows-specific tools like PowerShell.
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 page for securing an Azure Service Fabric cluster consistently presents Windows-specific guidance and links before Linux equivalents, and omits explicit instructions or links for securing standalone Linux clusters. While the concept of certificate-based security is described as applicable to both Windows and Linux, practical setup instructions and references are only provided for Windows standalone clusters, leaving Linux users without clear guidance.
Recommendations
  • Add explicit instructions and links for securing standalone Linux Service Fabric clusters, including certificate setup and client authentication.
  • Ensure that examples and guidance for both Windows and Linux are presented in parallel, or clarify when features are Windows-only.
  • Include references to Linux-compatible certificate management tools and patterns (e.g., OpenSSL, Linux certificate stores) where relevant.
  • If Linux standalone clusters are not supported, state this clearly to avoid confusion.
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 ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page for Azure Service Fabric Events primarily references Windows-centric tools and patterns, such as ETW/Windows Event logs and the Windows Azure diagnostics agent, without mentioning Linux equivalents or providing Linux-specific guidance. The examples and instructions focus on Windows mechanisms for event access and monitoring, and Windows tools are mentioned first and exclusively.
Recommendations
  • Add explicit guidance for accessing Service Fabric events on Linux clusters, including supported logging mechanisms (e.g., stdout, syslog, Azure Monitor integration for Linux).
  • Mention Linux-compatible diagnostics agents or methods, such as Azure Monitor agent for Linux, and clarify any differences in event collection and visualization.
  • Provide examples or links for querying and analyzing Service Fabric events from Linux environments, including REST API usage and integration with cross-platform tools.
  • Clearly state any limitations or differences in event access between Windows and Linux clusters, if applicable.
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: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides general guidance for upgrading Azure Service Fabric clusters, but there are subtle signs of Windows bias. For example, in the 'Upgrading OS images for cluster nodes' section, the only linked guidance is for patching Windows operating systems, with no mention of Linux node patching. Additionally, PowerShell is mentioned as a management tool alongside Azure CLI, but Linux-specific tools or workflows are not highlighted. Windows-related documentation is referenced first or exclusively in some sections, potentially creating friction for Linux users.
Recommendations
  • Add explicit guidance or links for patching/upgrading Linux node OS images in Service Fabric clusters, if supported.
  • Ensure examples for cluster management (certificates, ports, etc.) include both PowerShell and Bash/Azure CLI commands, or clarify parity.
  • Mention Linux support and limitations where relevant, especially in sections referencing Windows-specific features or tools.
  • Provide links to Linux-specific Service Fabric documentation where available.
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 ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page for the Azure Service Fabric application resource model demonstrates notable Windows bias. All deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) without any Azure CLI or Bash equivalents. The packaging step relies on Visual Studio, a Windows-centric tool, and the directory structure uses Windows path conventions. There are no Linux/macOS-specific instructions or alternatives provided, and Windows tools are referenced before any cross-platform options.
Recommendations
  • Add Azure CLI examples for deployment and deletion alongside PowerShell cmdlets.
  • Provide guidance for packaging applications using cross-platform tools (e.g., dotnet CLI, SF SDK, or manual zip commands) instead of only Visual Studio.
  • Include Linux/macOS path conventions and instructions where relevant.
  • Mention that the Azure portal and Resource Manager templates are platform-agnostic, and clarify any steps that are Windows-only.
  • Where screenshots or instructions reference Windows UI/tools, add notes or alternatives for Linux/macOS users.
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_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides code examples and administrative instructions primarily using PowerShell and C#, with no equivalent Linux CLI or scripting examples. Windows tools (PowerShell cmdlets) are referenced exclusively for cluster and service management, and Linux alternatives are not mentioned or demonstrated. The 'Choosing a platform' section does acknowledge Linux, but only in the context of implementation differences, not in operational guidance.
Recommendations
  • Add equivalent Linux CLI examples (e.g., using Azure CLI, Bash scripts, or Service Fabric CLI) alongside PowerShell examples.
  • Reference Linux management tools and workflows where PowerShell cmdlets are mentioned.
  • Explicitly state when a feature or example is Windows-only, and provide Linux alternatives or note limitations.
  • Ensure Linux operational guidance is present for tasks like scaling services, creating/removing instances, and cluster management.
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 is a cross-platform technology. However, there are several areas where Windows-specific tools, services, and patterns are mentioned first or exclusively, such as references to Windows services (FabricHost.exe), PowerShell cmdlets, and standalone cluster creation only for Windows. Linux equivalents are sometimes missing or mentioned later. This creates friction for Linux users, especially in cluster management and lifecycle operations.
Recommendations
  • Ensure that CLI (sfctl) examples and references are given equal prominence to PowerShell, especially in lifecycle and health monitoring sections.
  • Add explicit Linux examples and instructions where only Windows or PowerShell are mentioned, such as cluster creation, management, and scaling.
  • Clarify which features are Windows-only and which are cross-platform, ideally with side-by-side comparison tables.
  • Provide links to Linux-specific documentation and tools in 'Next steps' and throughout the page.
  • Mention Linux container support and Java programming model earlier, alongside Windows/.NET references.
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_first
Summary
The documentation provides a PowerShell-only example for reporting and evaluating application health, with no equivalent example for Linux or cross-platform tools (e.g., Bash, REST, or CLI). PowerShell cmdlets are mentioned before REST APIs, and no Linux-specific guidance or parity is provided for common health reporting tasks.
Recommendations
  • Add equivalent examples using cross-platform tools such as Azure CLI, Bash scripts, or REST API calls for health reporting and querying.
  • Explicitly mention how Linux/macOS users can perform the same health reporting and querying tasks, referencing any required Service Fabric CLI or REST endpoints.
  • Reorder or supplement the 'Health reporting' section to present cross-platform methods (e.g., REST, CLI) before or alongside PowerShell examples.
  • Clarify in the example section that PowerShell is one option, and provide links or code snippets for Linux/macOS users.
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: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides PowerShell examples for setting DNS names, references ApplicationManifest.xml (a Windows-centric deployment artifact), and describes portal-based configuration (which is not supported for Linux clusters). While Linux support is mentioned, Linux-specific instructions, examples, and parity for non-containerized workloads are missing. Windows tools and patterns (PowerShell, Visual Studio, ApplicationManifest.xml) are presented first and exclusively, with no equivalent Linux CLI or YAML-based examples.
Recommendations
  • Add Linux-specific instructions for enabling DNS service, including CLI (az, sfctl) or ARM template workflows.
  • Provide examples for setting DNS names using Linux-compatible tools (e.g., sfctl, az CLI, YAML manifests for containerized workloads).
  • Clarify limitations for Linux clusters and offer guidance/workarounds for Linux users (e.g., how to enable DNS service without portal access).
  • Include sample workflows for Linux containerized services, such as Docker Compose or Kubernetes YAML, to demonstrate DNS integration.
  • Balance the order of examples so Linux approaches are presented alongside or before Windows-specific tools.
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: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits mild Windows bias. It references Windows file paths (e.g., Service Fabric SDK schema location), and the example directory structure uses a Windows-style executable (.exe). There are no explicit Linux/macOS examples or references to cross-platform tools or file paths. Visual Studio (a Windows-centric tool) is mentioned as a primary packaging method, and no Linux packaging or deployment workflow is described.
Recommendations
  • Add examples of packaging and deploying guest executables on Linux/macOS, including relevant file paths and executable formats (e.g., .sh, .out).
  • Mention cross-platform command-line tools or alternatives to Visual Studio for packaging and deploying applications.
  • Clarify if the Service Fabric SDK and schema files are available and usable on Linux/macOS, and provide their respective paths.
  • Include sample directory structures and manifests for Linux/macOS guest executables.
GitHub Create Pull Request
Service Fabric Azure Service Fabric hosting activation and deactivation life cycle ...les/service-fabric/service-fabric-hosting-lifecycle.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation references PowerShell for deployment/removal tasks and links to a PowerShell-specific cmdlet for downloading ServicePackages. There are no equivalent Linux/bash examples or references to cross-platform tools. The 'Next steps' section directs users to PowerShell-based workflows, and the only explicit tooling example is Windows-centric.
Recommendations
  • Add Linux/bash CLI examples for deploying, removing, and downloading ServicePackages, using Azure CLI or Service Fabric CLI where available.
  • Include references to cross-platform tools and documentation, such as sfctl (Service Fabric CLI) for Linux/macOS users.
  • Update 'Next steps' to link to both PowerShell and Linux/bash workflows, or clarify which steps are cross-platform.
  • Where PowerShell cmdlets are mentioned, provide equivalent commands for Linux/macOS environments.
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_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides conceptual information about Azure Service Fabric hosting models, but when it comes to practical examples and management instructions, it heavily features PowerShell commands and references, which are Windows-centric. There are no CLI or Linux/macOS-specific examples for creating or managing services, and PowerShell is mentioned first and most prominently. This creates friction for Linux/macOS users, who may need to use Azure CLI or REST APIs instead.
Recommendations
  • Add Azure CLI examples for creating services with different ServicePackageActivationMode values.
  • Explicitly mention cross-platform management options (e.g., Azure CLI, REST API) alongside PowerShell.
  • Reorder or balance example sections so that Windows and Linux/macOS options are presented equally.
  • Link to documentation for Linux/macOS management tools where relevant.
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 interacting with the Service Fabric cluster manifest and links to a PowerShell-based deployment guide as the next step. While .NET and REST are mentioned, PowerShell is listed first and is the only example explicitly linked. There are no Linux-specific tools or CLI examples provided, and the workflow is described in a way that assumes familiarity with Windows-centric tools.
Recommendations
  • Add Azure CLI or Service Fabric CLI (sfctl) examples for retrieving the cluster manifest and managing the ImageStoreConnectionString, especially for Linux/macOS users.
  • Include links to cross-platform tools and documentation, such as sfctl or REST API guides, alongside PowerShell references.
  • When listing programmatic options (PowerShell, .NET, REST), rotate or randomize the order, or explicitly state that all are supported equally.
  • Provide a 'Next steps' section that includes Linux/macOS-friendly guides, not just PowerShell-based ones.
GitHub Create Pull Request
Service Fabric Azure Service Fabric container application manifest examples ...abric/service-fabric-manifest-example-container-app.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page for Azure Service Fabric container application manifest examples shows a notable Windows bias. The manifest examples are explicitly based on a Windows Server 2016 Container Sample, and several instructions reference Windows-specific tools or patterns (e.g., 'winver' for OS build, Windows file paths like 'c:\VolumeTest\Data'). There is minimal mention of Linux equivalents, and no Linux-specific manifest examples or guidance are provided, despite Service Fabric supporting Linux containers.
Recommendations
  • Add Linux-based manifest examples or provide a parallel Linux section, including differences in file paths, volume mounts, and certificate handling.
  • When referencing OS-specific tools (e.g., 'winver'), also mention Linux equivalents (e.g., 'cat /etc/os-release' or 'uname -r').
  • Clarify which features or manifest elements are Windows-only and which are cross-platform.
  • Update volume mount examples to include Linux path formats (e.g., '/mnt/data') where appropriate.
  • Explicitly state any limitations or differences for Linux container support in Service Fabric.
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_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation page provides Service Fabric manifest examples and explanations. While the manifest XML itself is cross-platform, the narrative and examples show a bias toward Windows patterns: batch scripts (.bat), references to Windows accounts (NetworkService, Administrators), and mentions of ServiceFabric PowerShell module for service creation. There are no Linux-specific examples (e.g., shell scripts, Linux user/group patterns), and Windows tools/scripts are referenced exclusively or first.
Recommendations
  • Add Linux-specific examples alongside Windows ones, such as using shell scripts (.sh) in SetupEntryPoint and EntryPoint.
  • Clarify which user/group patterns are valid for Linux Service Fabric clusters (e.g., use of local users, system groups).
  • Mention Linux equivalents for service creation (e.g., Azure CLI or sfctl) instead of only referencing PowerShell.
  • Explicitly note cross-platform differences in account types and script formats in relevant sections.
  • Provide guidance or links for Linux/macOS users deploying Service Fabric applications, including manifest considerations.
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 covers both Windows-only (HTTP.sys) and cross-platform (Kestrel) web servers for ASP.NET Core in Service Fabric. However, Windows-specific tools and APIs (HTTP.sys, netsh, Windows HTTP Server API) are discussed in detail and often before their Linux equivalents. There are explicit notes about HTTP.sys being Windows-only, but Linux/macOS users are not provided with equivalent examples or troubleshooting guidance for non-Windows environments. The configuration and endpoint setup sections focus heavily on Windows patterns, and Visual Studio debugging is referenced without mention of cross-platform alternatives.
Recommendations
  • Add explicit Linux/macOS guidance and examples for Service Fabric scenarios using Kestrel, including endpoint configuration and troubleshooting.
  • Clarify which sections are Windows-only and which are cross-platform, ideally with clear headings or callouts.
  • Provide links or references to Linux/macOS development tools (e.g., VS Code, CLI debugging) where Visual Studio is mentioned.
  • Ensure troubleshooting and configuration guidance covers Linux/macOS scenarios, especially for port assignment and firewall configuration.
  • Consider including a summary table comparing Windows and Linux/macOS approaches for common tasks.
GitHub Create Pull Request
Service Fabric Reliable Collection object serialization ...c-reliable-services-reliable-collections-serialization.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides examples and references primarily in C#/.NET, which is cross-platform, but the 'Next steps' section lists Windows-centric tools (Visual Studio and PowerShell) before mentioning any alternatives. There are no Linux-specific upgrade tools or examples, and PowerShell is highlighted as a primary automation method, which may create friction for Linux/macOS users who prefer Bash or other native tools.
Recommendations
  • Add examples or links for upgrading applications using Bash or CLI tools on Linux/macOS, such as Azure CLI or Service Fabric CLI.
  • Mention cross-platform alternatives to PowerShell for automation, or clarify that PowerShell Core is available on Linux/macOS.
  • Reorder 'Next steps' to present platform-neutral or Linux-friendly options before Windows-specific ones.
  • Explicitly state if the guidance is applicable to Linux/macOS Service Fabric clusters, and provide any relevant differences.
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: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides a PowerShell example for deploying Service Fabric applications, which is a Windows-centric tool. There is no equivalent Linux CLI example (e.g., using sfctl or Azure CLI), and the PowerShell example is presented as the default method. The documentation references the Service Fabric SDK schema location using a Windows file path first, and only later mentions the Linux certificate store location. Linux-specific deployment commands and patterns are missing.
Recommendations
  • Add equivalent Linux/macOS deployment examples using sfctl or Azure CLI alongside PowerShell.
  • Mention Linux file paths and tools (e.g., sfctl, bash) where relevant, not just Windows paths.
  • Present cross-platform instructions in parallel, or clarify which steps are OS-specific.
  • Include a note about how Linux users can override endpoints and deploy applications, referencing relevant tools and commands.
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: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page for 'Replica soft delete for enhanced data protection in Service Fabric' consistently references PowerShell APIs (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica) and provides examples and links exclusively for PowerShell usage. There is no mention of Linux or cross-platform equivalents, nor are CLI or REST API examples provided. The documentation assumes the use of Windows tooling and patterns, which may create friction for Linux/macOS users managing Service Fabric clusters.
Recommendations
  • Add equivalent examples for Linux/macOS users, such as using Service Fabric CLI (sfctl) or REST APIs where available.
  • Clarify whether the PowerShell APIs are supported on Linux via PowerShell Core, or provide guidance for Linux users.
  • Include links and usage examples for cross-platform tools (e.g., sfctl commands for removing/restoring replicas).
  • Explicitly state any limitations or parity gaps for Linux/macOS users in the feature support section.
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 and cluster connection, but does not offer equivalent Linux/bash or cross-platform CLI examples. Windows/PowerShell tools are mentioned first and exclusively in example sections, creating friction for Linux/macOS users who may not have access to PowerShell or Windows-specific Service Fabric tooling.
Recommendations
  • Add equivalent examples using Azure CLI, bash scripts, or Service Fabric CLI (sfctl) for health reporting and cluster connection.
  • Clarify which tools are cross-platform and which are Windows-only, and provide guidance for Linux/macOS users.
  • Mention REST API as a cross-platform option earlier and provide more detailed REST examples.
  • Where PowerShell is used, note if the commands are available on PowerShell Core (cross-platform) or only on Windows PowerShell.
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: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation is heavily focused on Visual Studio workflows and references features (Build/Rebuild/F5/Ctrl+F5/Publish) that are exclusive to Windows environments. All examples and screenshots are based on Visual Studio, with no mention of Linux/macOS tooling or workflows (such as CLI, VS Code, or cross-platform deployment methods). There are references to PowerShell as an alternative, but no Linux shell or cross-platform CLI examples are provided.
Recommendations
  • Add explicit guidance for Linux/macOS users, including how to manage service configuration and deployment without Visual Studio.
  • Provide examples using Azure CLI, Service Fabric CLI (sfctl), or PowerShell Core (if cross-platform) for creating and deploying applications.
  • Clarify which features are Visual Studio/Windows-only and offer alternative workflows for non-Windows environments.
  • Include screenshots or walkthroughs for cross-platform tools (e.g., VS Code, CLI) where possible.
GitHub Create Pull Request
Service Fabric Configure the upgrade of a Service Fabric application ...abric/service-fabric-visualstudio-configure-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 is heavily focused on Windows tooling, specifically Visual Studio and PowerShell, for configuring and upgrading Service Fabric applications. All examples and upgrade instructions reference Windows tools, with no mention of Linux/macOS equivalents or cross-platform alternatives. There are no CLI or script examples for Linux users, and PowerShell is presented as the primary method for manual upgrades.
Recommendations
  • Add instructions and examples for upgrading Service Fabric applications using Azure CLI or REST API, which are cross-platform.
  • Include guidance for Linux/macOS users, such as how to configure upgrades without Visual Studio or PowerShell.
  • Mention and link to any available cross-platform tooling or SDKs for Service Fabric application management.
  • Clarify if certain features (like Visual Studio integration) are Windows-only, and provide alternative workflows for non-Windows environments.
GitHub Create Pull Request
Virtual Machines Associate a virtual machine to a capacity reservation group .../virtual-machines/capacity-reservation-associate-vm.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ arm_template_windows_only
Summary
The documentation covers both Windows and Linux VMs, and provides cross-platform guidance via Azure CLI, API, Portal, and PowerShell. However, there are signs of Windows bias: PowerShell examples and references are prominent, and ARM template examples are Windows-only (no Linux image or parameter options). Windows-specific parameters (e.g., OSVersion) are shown first and exclusively in ARM templates. The CLI examples do use Ubuntu images, but the ARM template and PowerShell sections focus on Windows. The ordering of examples sometimes puts Windows tools (PowerShell) before Linux-friendly ones (CLI).
Recommendations
  • Add ARM template examples for Linux VMs, including parameters for Linux images and admin SSH keys.
  • In ARM template sections, clarify how to adapt the template for Linux VMs (e.g., show both Windows and Linux imageReference blocks).
  • Balance PowerShell and CLI coverage: ensure CLI examples are as detailed as PowerShell, and consider showing CLI before PowerShell.
  • When referencing admin credentials, provide guidance for both password (Windows) and SSH key (Linux).
  • Review ordering of examples to avoid always showing Windows tools first.
  • Explicitly state that all steps apply to both Windows and Linux VMs, and highlight any differences.
GitHub Create Pull Request
Virtual Machines Create and upload an Ubuntu Linux VHD in Azure ...rticles/virtual-machines/linux/create-upload-ubuntu.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation, while focused on Ubuntu Linux VHDs, repeatedly references Windows-centric tools (Hyper-V, Convert-VHD PowerShell cmdlet) and provides Windows-first guidance for creating and converting VHDs. Linux-native alternatives (such as qemu-img, KVM, VirtualBox, or Linux CLI conversion tools) are not mentioned, leaving Linux/macOS users without clear instructions for critical steps like VHD creation and conversion.
Recommendations
  • Add instructions and examples for creating and converting VHDs using Linux-native tools (e.g., qemu-img, VirtualBox, KVM).
  • Mention Linux/macOS alternatives alongside Windows tools, not after or instead of them.
  • Provide links to Linux-specific guides for disk conversion and virtualization.
  • Clarify that Hyper-V and Convert-VHD are Windows-only and offer parity for Linux/macOS users.
GitHub Create Pull Request
Virtual Machines Run scripts in a Linux VM in Azure using managed Run Commands ...articles/virtual-machines/linux/run-command-managed.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
Although the documentation is focused on Linux VMs, there is notable Windows bias in several areas. PowerShell examples and tools (e.g., Set-AzVMRunCommand, Get-AzVMRunCommand) are heavily featured alongside Azure CLI, and in some cases, Windows-specific instructions or terminology (such as PowerShell script references, Windows VM notes, and SAS token generation with PowerShell) are presented without equivalent Linux-native alternatives. REST and ARM template examples also use Windows-centric script samples (e.g., Write-Host, .ps1 files) instead of Linux shell scripts. The PowerShell section is much more extensive than the Azure CLI section, with more advanced scenarios only covered in PowerShell. Some notes and explanations reference Windows behaviors before Linux, and there are missing Linux-native examples for tasks like SAS token generation and blob management.
Recommendations
  • Expand Azure CLI examples to cover all advanced scenarios currently only shown in PowerShell (e.g., streaming output to blob, running as a different user, passing parameters).
  • Replace or supplement REST and ARM template script samples with Linux shell script examples (e.g., use 'echo Hello World!' or bash scripts instead of 'Write-Host' and .ps1 files).
  • Provide Linux-native instructions for generating SAS tokens and managing blobs (e.g., using Azure CLI or azcopy), not just PowerShell.
  • Ensure notes and explanations reference Linux behaviors first or equally, especially when describing parameter passing or script execution.
  • Clarify when PowerShell commands are cross-platform (e.g., PowerShell Core on Linux) or provide explicit bash/CLI alternatives.
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 is focused on Linux VM time synchronization in Azure and provides extensive Linux-specific guidance, examples, and tooling. However, the introductory section discusses Windows Server 2016 time sync improvements and references Windows documentation before Linux-specific details. There are no PowerShell or Windows-only tools used for Linux configuration, except for a single PowerShell command for base64 encoding cloud-init data, which is contextually appropriate for Azure ARM templates and not for VM time sync itself.
Recommendations
  • Move the Windows Server 2016 discussion and links to a background or context section, making clear it is for Azure host infrastructure and not directly relevant to Linux VM configuration.
  • Add a brief summary at the start clarifying that all configuration steps and examples are Linux-specific.
  • If referencing Windows documentation, ensure Linux documentation is referenced with equal prominence and in the same section.
  • For the PowerShell base64 example, consider providing a Linux equivalent (e.g., `base64 cloud-config.txt`) for users preparing ARM templates from Linux/macOS environments.
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: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page for Azure Service Fabric container image management exhibits minor Windows bias. Windows container base images (microsoft/windowsservercore, microsoft/nanoserver) are mentioned explicitly and prioritized as default exclusions from cleanup. No Linux container base images (such as Ubuntu, Alpine, etc.) are referenced in the default settings or examples. Additionally, there are no explicit examples or guidance for Linux container image management, nor are Linux-specific considerations discussed. The JSON configuration examples and descriptions are generic, but the focus on Windows images and lack of Linux parity creates friction for Linux users.
Recommendations
  • Add examples and explanations for Linux container base images (e.g., Ubuntu, Alpine, CentOS) in the ContainerImagesToSkip setting.
  • Clarify whether the cleanup and management features apply equally to Linux containers and Windows containers.
  • Provide Linux-specific guidance or considerations if there are differences in behavior or requirements.
  • Include sample configurations for skipping common Linux images, similar to the Windows examples.
GitHub Create Pull Request
Service Fabric Describing Azure Service Fabric apps and services ...ic/service-fabric-application-and-service-manifests.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page exhibits mild Windows bias. It references Windows file paths (e.g., 'C:\Program Files\Microsoft SDKs\Service Fabric\schemas\ServiceFabricServiceModel.xsd') and recommends using Visual Studio for schema validation, which is a Windows-centric tool. Additionally, it mentions the ServiceFabric PowerShell module for service creation, but does not provide equivalent Linux CLI examples or mention cross-platform tools. Windows terminology and tools are referenced before any Linux alternatives, and no Linux/macOS-specific guidance is given.
Recommendations
  • Provide Linux/macOS file path equivalents for schema files and instructions on how to validate manifests using cross-platform editors (e.g., VS Code, JetBrains Rider).
  • Mention and provide examples for using Azure CLI or Service Fabric CLI (sfctl) for service creation and management, alongside PowerShell.
  • Clarify that Service Fabric development and deployment can be performed on Linux clusters, and link to relevant Linux-specific documentation.
  • Ensure that all tooling recommendations (e.g., manifest validation, deployment) include cross-platform options.
  • Add notes or examples for Linux/macOS users where Windows-specific instructions are given.
GitHub Create Pull Request
Service Fabric Overview of Azure Service Fabric ...ain/articles/service-fabric/service-fabric-overview.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation mentions both Windows and Linux support for Service Fabric, and provides references to Linux-specific development workflows. However, Windows development (Visual Studio, PowerShell, .NET SDK) is described first, with Linux development (Eclipse, Yeoman, Java SDK) mentioned second. No explicit Linux example is missing, but the ordering and emphasis slightly favor Windows.
Recommendations
  • Present Windows and Linux development options in parallel, rather than listing Windows first.
  • Ensure that quickstart and getting started links are available for both Windows and Linux (the quickstart link currently points to a .NET/Windows page).
  • Where possible, provide equal visibility to Linux tooling and workflows (e.g., highlight Yeoman, Eclipse, Java SDK alongside Visual Studio and PowerShell).
  • Consider linking to Linux quickstart or sample projects directly from the overview.
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 bias toward Windows: Windows container runtimes and tools are described in more detail, and Windows scenarios (such as IIS lift-and-shift) are mentioned first in the 'Scenarios for using containers' section. Windows tutorials and references are often listed before Linux equivalents, and Windows-specific tools (Mirantis Container Runtime, DockerEE) are highlighted, while Linux only mentions Docker.
Recommendations
  • Present Linux and Windows scenarios/examples in parallel or alternate order to avoid Windows-first bias.
  • Expand Linux scenario examples (e.g., highlight common Linux workloads or migration paths, such as Apache or NGINX lift-and-shift).
  • Provide equal detail for Linux container runtimes and tools, mentioning alternatives to Docker if relevant.
  • Ensure Linux tutorials and references are listed alongside Windows ones, not after.
  • Add explicit statements clarifying parity and limitations for Linux and Windows container support.
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. However, PowerShell is presented first and in greater detail, which may suggest a Windows-first approach. The CLI examples (sfctl) are cross-platform, but the initial emphasis on PowerShell may create friction for Linux/macOS users.
Recommendations
  • Present Service Fabric CLI (sfctl) examples before PowerShell, as sfctl is cross-platform and more accessible to Linux/macOS users.
  • Explicitly state that sfctl works on all platforms and is recommended for non-Windows environments.
  • Consider providing Bash or shell script examples where relevant.
  • Clarify in the introduction that both Windows and Linux users are supported, and direct users to the appropriate section for their OS.
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 is generally platform-neutral, but there are a few areas where Windows-specific terminology and tools are mentioned first or exclusively. For example, the description of nodes references an 'auto-start Windows service, FabricHost.exe' and executable files are described as 'EXE/DLL files.' While Linux is mentioned in the context of containers and guest executables, Windows concepts and tools are often presented first or in more detail. However, Linux support is acknowledged, and no critical tasks are Windows-only.
Recommendations
  • Clarify that FabricHost.exe and related executables have Linux equivalents or note differences in Linux deployments.
  • When describing executable files, mention Linux formats (e.g., ELF binaries) alongside EXE/DLL.
  • Ensure examples and terminology are balanced, mentioning Linux and Windows equally where applicable.
  • Add explicit notes or links to Linux-specific documentation or guidance where relevant.
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: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation references Azure CLI, Azure PowerShell, and ARM templates for creating and migrating Virtual Machine Scale Sets, but does not provide explicit Linux/bash shell examples or mention Linux tools. Azure PowerShell is mentioned alongside Azure CLI, but PowerShell is a Windows-centric tool. Some example commands are shown in Azure CLI, which is cross-platform, but there are no explicit bash or Linux-specific instructions. Windows-specific scenarios (activation, updates) are listed before Linux equivalents, and Windows-centric tasks are described in more detail.
Recommendations
  • Provide explicit bash/Linux shell examples for key tasks, such as VM creation and migration.
  • Mention Azure CLI as the primary cross-platform tool, and clarify PowerShell is optional for Windows users.
  • When listing connectivity requirements, mention Linux package manager access before or alongside Windows activation and updates.
  • Add examples or references for Linux-specific migration considerations, such as handling SSH keys or Linux VM extensions.
  • Ensure parity in troubleshooting and operational guidance for both Windows and Linux VMs.
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
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all major operations (attach, detach, move VMs), but the PowerShell examples are always present and sometimes more detailed. Azure PowerShell is a Windows-centric tool, and its inclusion alongside Azure CLI (which is cross-platform) is standard, but the PowerShell examples are shown after CLI, not before. No Windows-only tools or patterns are mentioned, and Linux parity is generally maintained. However, some troubleshooting links reference Windows-specific documentation (e.g., proximity placement groups), and PowerShell examples may be less relevant for Linux/macOS users.
Recommendations
  • Ensure all troubleshooting links reference both Linux and Windows documentation where applicable.
  • Clarify that Azure PowerShell can be used on Linux/macOS (via PowerShell Core), or provide Bash script examples for common tasks.
  • Consider adding a note that Azure CLI is recommended for Linux/macOS users.
  • Review troubleshooting steps to ensure they are not Windows-centric (e.g., disk conversion, proximity placement group removal).
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: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for most tasks, but PowerShell (a Windows-centric tool) is often presented before CLI, and in some cases, PowerShell examples are more detailed. There are no Linux-specific shell examples (e.g., Bash scripts), and PowerShell is listed before CLI in tabbed sections. However, Azure CLI is cross-platform and present for all major tasks, so Linux/macOS users are not blocked.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and more accessible to Linux/macOS users.
  • Where possible, add explicit Bash shell script examples for common tasks, especially for querying or scripting.
  • Clarify in the introduction that Azure CLI is fully supported on Linux/macOS and is recommended for cross-platform automation.
  • Ensure that all PowerShell examples have equivalent Azure CLI examples, and vice versa.
  • Consider adding a short section or note for Linux/macOS users highlighting CLI usage and installation.
GitHub Create Pull Request
Virtual Machine Scale Sets Create an Azure scale set that uses Availability Zones ...s/virtual-machine-scale-sets-use-availability-zones.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for creating and updating scale sets with Availability Zones. However, PowerShell examples are given equal prominence to CLI, and in some sections (such as 'Update scale set to add availability zones'), PowerShell is listed before REST API and after CLI. The CLI examples are cross-platform, but PowerShell is Windows-centric. There is a minor bias in the ordering and prominence of PowerShell, and the documentation does not explicitly mention Linux/macOS compatibility or alternatives for PowerShell users. The ARM template section links to both Linux and Windows getting started articles, which is positive for parity.
Recommendations
  • Explicitly state that Azure CLI is cross-platform and recommended for Linux/macOS users.
  • Consider listing Azure CLI examples before PowerShell in all sections to reinforce cross-platform parity.
  • Add brief notes clarifying that Azure PowerShell is primarily for Windows users, and that CLI is the preferred method for Linux/macOS.
  • Ensure that all critical workflows have CLI examples and that CLI is not omitted in any section.
  • Optionally, add Bash shell script snippets or highlight Linux-specific considerations where 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
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for all operations, but PowerShell is featured equally alongside CLI and is presented as a first-class option. PowerShell is primarily a Windows tool, and its prominence may create friction for Linux/macOS users. However, all critical tasks are covered with Azure CLI examples, which are cross-platform, and no Windows-only tools or patterns are used exclusively. The ordering of examples sometimes puts PowerShell before ARM templates, but not before CLI. No Linux-specific tools or shell examples are missing, but Bash or Linux-native scripting is not referenced.
Recommendations
  • Consider explicitly mentioning that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Add Bash shell scripting examples or clarify that Azure CLI commands can be run in Bash or other Linux shells.
  • Where PowerShell is referenced, note its availability on Linux/macOS, or link to installation instructions for PowerShell Core.
  • Ensure CLI examples are always shown before PowerShell, or provide a clear 'Linux/macOS' and 'Windows' labeling for each section.
GitHub Create Pull Request
Virtual Machine Scale Sets Rolling upgrades with MaxSurge for Virtual Machine Scale Sets ...hine-scale-sets/virtual-machine-scale-sets-maxsurge.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides configuration examples for rolling upgrades with MaxSurge using Azure Portal, Azure CLI, PowerShell, and ARM templates. The PowerShell example is included alongside CLI and Portal, and the CLI example is generic (az CLI, which works cross-platform). However, the PowerShell example is presented as a full script, and the section is labeled explicitly as 'PowerShell', which may signal Windows bias. Additionally, the PowerShell section appears immediately after the CLI section, which is standard but can be perceived as 'windows_first' bias since no Linux/macOS-specific shell examples (e.g., Bash) are provided.
Recommendations
  • Clarify that Azure CLI commands are cross-platform and work on Windows, Linux, and macOS.
  • Consider adding Bash shell examples for Linux/macOS users, especially if there are nuances in scripting or environment variables.
  • Explicitly state that PowerShell is available cross-platform (PowerShell Core), or clarify if the example is Windows PowerShell only.
  • Ensure parity by mentioning that all configuration steps can be performed from any OS using Azure CLI or ARM templates.
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: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation provides both Linux (Bash/Python) and Windows (PowerShell) examples for configuring the application health extension response, as well as Azure CLI, PowerShell, and REST API instructions for extension installation and querying. However, there are several instances where Windows/PowerShell examples are presented before Linux/Bash equivalents, and Windows-specific extension types (ApplicationHealthWindows) are used in sample code. PowerShell examples are detailed and prominent, and Windows tools/patterns (e.g., PowerShell HTTP server) are given equal or greater emphasis compared to Linux. The documentation does not omit Linux examples, but Windows bias is evident in ordering and tool selection.
Recommendations
  • Present Linux/Bash examples before Windows/PowerShell examples, or alternate ordering to avoid implicit prioritization.
  • Ensure all sample code and extension configuration examples clearly show both ApplicationHealthLinux and ApplicationHealthWindows types, or use a neutral placeholder.
  • Expand Linux-specific troubleshooting and verification steps (e.g., using systemd, firewalld, or other common Linux tools for endpoint setup and firewall configuration).
  • Explicitly state that both Linux and Windows VMSS instances are supported, and clarify any OS-specific requirements.
  • Where possible, provide cross-platform scripts or highlight platform differences in a dedicated section.
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: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation provides examples for Azure portal, Azure CLI, PowerShell, and REST API. PowerShell is presented as a distinct example, but it is not prioritized above CLI or REST. However, in the 'Create a private gallery' section, the PowerShell example is shown after the CLI example, and both are given equal prominence. The CLI examples use Bash syntax and variables, which are cross-platform and friendly for Linux/macOS users. There are no Windows-only tools or patterns, and no critical steps are Windows-exclusive. The only minor bias is the inclusion of PowerShell as a separate example, which could be interpreted as slightly favoring Windows users, but this is mitigated by the presence of CLI and REST examples. No Linux/macOS examples are missing, and the CLI is presented before PowerShell.
Recommendations
  • Consider explicitly noting that Azure CLI commands work on Linux, macOS, and Windows.
  • If possible, add a note clarifying that PowerShell examples are for Windows users, while CLI examples are cross-platform.
  • Ensure screenshots and portal instructions do not reference Windows-specific UI elements.
  • Maintain the current order (CLI before PowerShell) to minimize perceived Windows bias.
GitHub Create Pull Request
Virtual Machines Azure VM Extensions and Features for Linux ...articles/virtual-machines/extensions/features-linux.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all major tasks, but consistently presents PowerShell examples immediately after CLI, and sometimes with more detailed output formatting. There is minor bias in mentioning PowerShell as a primary tool alongside Azure CLI, despite the Linux focus. However, all examples and instructions are fully applicable to Linux users, and no Windows-specific tools or patterns are prioritized or required.
Recommendations
  • Consider presenting Azure CLI examples first in all sections, as CLI is the native cross-platform tool and more relevant for Linux users.
  • Where possible, clarify that PowerShell examples are optional for Linux users, and highlight that Azure CLI is the default for Linux environments.
  • Ensure that output examples and troubleshooting steps are equally detailed for CLI and PowerShell.
  • Add explicit notes that Azure PowerShell can be run on Linux, but Azure CLI is typically preferred for Linux workflows.
GitHub Create Pull Request
Virtual Machines Qualys Cloud Agent Extension for Azure VMs ...ob/main/articles/virtual-machines/extensions/qualys.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation generally provides parity between Windows and Linux deployment methods, but there is a subtle bias in the prominence of PowerShell (a Windows-centric tool) as a primary automation method, and in some sections, Windows is mentioned before Linux. However, Linux-specific tools (like Ansible) are also referenced, and Linux deployment links are provided alongside Windows equivalents.
Recommendations
  • When listing deployment methods or examples, alternate the order of Windows and Linux, or present them together to avoid 'Windows first' bias.
  • Clarify that PowerShell Core is cross-platform if recommending it for Linux, or provide Bash/Azure CLI examples for Linux users.
  • Expand on Linux-native automation tools (e.g., Bash scripts, Azure CLI, cloud-init) in addition to PowerShell, especially in sections focused on command-line deployment.
  • Ensure that all external links for deployment steps are equally available and visible for both Windows and Linux.
  • Explicitly mention when a method is equally applicable to both OSes, or provide OS-specific instructions where necessary.
GitHub Create Pull Request
Virtual Machines Instantly access managed disk snapshots ...les/virtual-machines/disks-instant-access-snapshots.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for creating instant access snapshots, but the PowerShell example is given equal prominence and appears before the portal example. There is no explicit Linux/macOS bias, but Windows tools (PowerShell) are featured alongside cross-platform CLI. No Linux-specific shell or tooling is referenced, and the CLI examples use Bash syntax, which is cross-platform but most common on Linux/macOS. The ordering of examples (CLI, PowerShell, Portal, ARM template) is neutral, but PowerShell is still a Windows-centric tool.
Recommendations
  • Clearly indicate that Azure CLI commands are cross-platform and suitable for Linux/macOS users.
  • Consider providing example CLI commands using both Bash and PowerShell syntax, or clarify that Bash is the default for CLI.
  • Add a note that Azure PowerShell is available on Linux/macOS, but CLI is recommended for cross-platform use.
  • Ensure that CLI examples are shown first and are complete, which is already the case.
  • Optionally, add a section for Linux/macOS users highlighting any OS-specific considerations (none appear necessary here).
GitHub Create Pull Request
Virtual Machines What's new in Azure Disk Storage ...blob/main/articles/virtual-machines/disks-whats-new.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation is primarily a changelog and summary of new features for Azure Disk Storage, which is a cross-platform service. Most content is neutral, but there are minor instances of Windows bias: Windows documentation links are sometimes listed before Linux equivalents, and references to Azure PowerShell are made without equal mention of Linux tools. However, Linux links and parity are generally present, and no critical features are Windows-only.
Recommendations
  • When linking to both Windows and Linux documentation, list Linux links first or side-by-side with Windows links to avoid subtle ordering bias.
  • Where Azure PowerShell is mentioned, also reference Azure CLI (which is cross-platform) to ensure Linux/macOS users are equally supported.
  • Review linked documentation to ensure Linux/macOS parity in examples and instructions.
  • Explicitly state cross-platform support in feature descriptions where relevant.
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 Linux, but in several sections (e.g., upgrading, troubleshooting, deployment), Windows/PowerShell examples are presented before their Linux/Azure CLI equivalents. The PowerShell deployment section is more detailed and appears before the Azure CLI section, which may create friction for Linux users. Additionally, troubleshooting commands are shown with PowerShell first, even though Azure CLI is more common on Linux.
Recommendations
  • Present Azure CLI examples before PowerShell examples in all sections, as CLI is the default for Linux users.
  • Ensure troubleshooting commands are shown with Azure CLI first, or provide parity in detail between CLI and PowerShell.
  • Clarify that PowerShell is optional and not required for Linux deployments.
  • Add explicit notes or guidance for Linux users about which tools are recommended (e.g., Azure CLI).
GitHub Create Pull Request
Virtual Machines NVIDIA GPU Driver Extension - Azure Linux VMs ...es/virtual-machines/extensions/hpccompute-gpu-linux.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation is focused on Linux VM GPU driver installation, but includes PowerShell examples alongside Azure CLI and ARM templates. The PowerShell example is presented before the Azure CLI example, which is more relevant for Linux users. There is also mention of a Windows extension, but it is clearly separated and not the main focus. No Windows-specific tools or patterns are prioritized, and Linux-specific commands and troubleshooting are well covered.
Recommendations
  • Move the Azure CLI example before the PowerShell example, as Azure CLI is more commonly used on Linux.
  • Clarify that PowerShell is optional and primarily for users on Windows or those who prefer it.
  • Consider adding Bash scripting examples for deployment, as Bash is native to Linux.
  • Ensure all troubleshooting and operational examples use Linux-native tools and commands where possible.
GitHub Create Pull Request
Virtual Machines HBv3-series virtual machine (VM) overview, architecture, topology - Azure Virtual Machines | Microsoft Docs ...main/articles/virtual-machines/hbv3-series-overview.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ recommended_windows ⚠ī¸ minor_linux_example
Summary
The documentation covers both Linux and Windows, but there is a subtle bias towards Windows in the 'Recommended OS for Performance' row, which lists Windows Server 2019+ as recommended without mentioning a Linux equivalent. Additionally, the order of OS support in some tables lists Windows after Linux, but the explicit recommendation is Windows. Linux-specific tools (e.g., lstopo) are used for topology, but no Windows equivalents or guidance are provided. Overall, Linux is well-represented, but the performance recommendation and lack of Windows-specific examples/tools create minor friction.
Recommendations
  • If Windows Server 2019+ is truly the only recommended OS for performance, clarify why and provide Linux performance guidance or caveats.
  • If Linux is also recommended for performance, add the relevant Linux distributions (e.g., RHEL, Ubuntu, SLES) to the 'Recommended OS for Performance' row.
  • Consider providing Windows equivalents for Linux-specific tools (like lstopo), or note if no equivalent exists.
  • Ensure that both Linux and Windows users are equally guided for performance tuning and topology inspection.
GitHub Create Pull Request
Virtual Machines Create an Azure Image Builder Bicep file or ARM template JSON template .../articles/virtual-machines/linux/image-builder-json.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides both Windows and Linux examples and covers both OSes in detail. However, there is a noticeable Windows bias: PowerShell examples and references are often presented first, Windows-specific tools (e.g., Get-FileHash, PowerShell customizer, WindowsRestart, WindowsUpdate) are described in more detail, and Windows terminology and commands are frequently referenced before Linux equivalents. Some instructions for generating checksums and managing identities use Windows/PowerShell tools as the primary example, with Linux alternatives mentioned but less emphasized. There are also Windows-only customizers (WindowsRestart, WindowsUpdate) without Linux equivalents, but this is explicitly documented.
Recommendations
  • Present Linux and Windows examples in parallel or alternate which is shown first.
  • When referencing tools for tasks (e.g., generating SHA256 checksums), provide Linux/macOS commands (sha256sum) before or alongside Windows/PowerShell commands.
  • Expand Linux-specific guidance (e.g., shell customizer, file paths, troubleshooting) to match the detail provided for Windows.
  • Where Windows-only customizers exist, clearly state Linux alternatives or limitations.
  • Ensure that validation and customization examples for Linux are as detailed as Windows examples.
  • Add links to Linux/macOS documentation for relevant Azure CLI and scripting tasks.
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. However, the PowerShell example is presented as a separate tab, and the CLI example (which is cross-platform) is shown first. There is minor bias in that PowerShell is included, but no Linux-specific shell examples (e.g., Bash scripting) are provided. The CLI example is sufficient for Linux/macOS users, and no Windows-only tools or patterns are prioritized.
Recommendations
  • Consider clarifying that Azure CLI is fully cross-platform and works on Linux/macOS as well as Windows.
  • Optionally, include a brief Bash shell scripting example for automating quota checks on Linux/macOS.
  • Ensure that any references to PowerShell note that it is available cross-platform, not only on Windows.
GitHub Create Pull Request
Virtual Machines Create and upload a Red Hat Enterprise Linux VHD for use in Azure ...les/virtual-machines/linux/redhat-create-upload-vhd.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides comprehensive instructions for preparing and uploading a Red Hat Enterprise Linux VHD for Azure, covering multiple hypervisors (Hyper-V, KVM, VMware, Kickstart). However, in most sections, Windows/Hyper-V tools and workflows are presented first, and Windows-centric terminology (e.g., Hyper-V Manager, VHD format, PowerShell cmdlets) is referenced before Linux alternatives. Linux/KVM/VMware instructions are present and detailed, but the ordering and some tool mentions (e.g., 'convert-vhd' cmdlet, Hyper-V Manager) prioritize Windows approaches.
Recommendations
  • Reorder sections so that Linux/KVM/VMware instructions are presented before or alongside Hyper-V/Windows instructions, especially in introductory or summary areas.
  • When referencing disk conversion tools, mention Linux-native tools (e.g., qemu-img) before or alongside Windows tools (e.g., Hyper-V Manager, convert-vhd).
  • Clarify that Hyper-V/Windows tools are optional and provide parity for Linux users by highlighting Linux-native workflows.
  • Consider adding a summary table or navigation that allows users to quickly jump to their preferred hypervisor/platform.
  • Where possible, avoid referencing Windows/PowerShell tools as the default unless the task is inherently Windows-specific.
GitHub Create Pull Request
Virtual Machines Share VM images in a compute gallery ...in/articles/virtual-machines/shared-image-galleries.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation covers both Windows and Linux VM images, but there are several signs of Windows bias. PowerShell examples are consistently provided alongside Azure CLI, sometimes referenced first. Windows-specific tools (Sysprep) are mentioned before Linux equivalents (waagent). Some links and examples reference Windows paths or documentation before Linux. However, Linux is explicitly supported and mentioned throughout, and most tasks can be completed by Linux users.
Recommendations
  • Ensure CLI and PowerShell examples are presented in parallel, with equal prominence and ordering.
  • When referencing tools for generalizing VMs, mention Linux (waagent) and Windows (Sysprep) in the same sentence or with equal visibility.
  • Provide links to Linux documentation alongside Windows documentation, not after or as a secondary reference.
  • Review FAQ and scenario sections to ensure Linux-specific workflows and links are equally represented.
  • Where possible, add Bash or Linux shell examples in addition to PowerShell, especially for scripting tasks.
GitHub Create Pull Request