← Back to Dashboard
282
Pages Scanned
95
Pages Flagged
282
Changed Pages
33.7%
% Pages Flagged

Live Progress

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

Scan Information

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

Finished At: In Progress

Status: in_progress

Target Repo: Azure Compute

Current Phase: discovery

Files Queued: 282

Files Completed: 282

Problematic Pages

94 issues found
Service Fabric Configure the upgrade of a Service Fabric application ...abric/service-fabric-visualstudio-configure-upgrade.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation is heavily focused on Windows-centric tools, specifically Visual Studio and PowerShell, for configuring and upgrading Service Fabric applications. All examples and upgrade instructions reference Visual Studio dialogs and PowerShell cmdlets, with no mention of Linux/macOS alternatives or cross-platform CLI tools. There are no examples or guidance for users on Linux or macOS, and the workflow assumes Windows environments.
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 using Service Fabric CLI (sfctl) or other supported tools.
  • Clearly indicate which steps are Windows-only and provide alternative workflows for non-Windows users.
  • Provide parity in examples, showing both Windows (PowerShell/Visual Studio) and Linux/macOS (CLI/terminal) approaches.
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 steps are implicitly Windows-centric. There are no Linux-specific instructions, examples, or workarounds provided, and the feature is unavailable for Linux users.
Recommendations
  • Clearly highlight at the top of the documentation that the reverse proxy feature is Windows-only, to prevent confusion for Linux users.
  • Provide links or references to alternative approaches for service discovery and communication in Linux Service Fabric clusters, if available.
  • Consider adding a roadmap or status update about Linux support for reverse proxy, if planned.
  • Ensure that related documentation (e.g., setup, diagnostics) also clarifies platform limitations.
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
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
Although the page introduction claims Service Fabric clusters can run on Windows Server and Linux, the actual content is Windows-centric. All security and scaling examples reference Windows tools and concepts, and the 'Supported operating systems' section explicitly states that Linux isn't yet supported for standalone clusters. No Linux-specific instructions, examples, or guidance are provided.
Recommendations
  • Clarify in the introduction that standalone clusters are currently Windows-only, despite the general Service Fabric platform supporting Linux.
  • Remove or revise statements suggesting Linux parity unless Linux support is actually available.
  • Add a section outlining the roadmap or alternatives for Linux users, or link to documentation for Service Fabric on Linux if available.
  • Ensure that any future Linux support is accompanied by equivalent examples, instructions, and security guidance.
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 Windows-centric tool) without mentioning Linux/macOS alternatives. No Linux CLI or cross-platform examples are given for critical operations, and Windows tooling is implicitly assumed.
Recommendations
  • Add equivalent Linux/macOS command-line examples (e.g., using sfctl or Azure CLI) for cluster operations.
  • Clarify whether Service Fabric Explorer is available cross-platform or suggest alternatives for Linux/macOS users.
  • Explicitly state platform requirements for commands and tools, and provide guidance for non-Windows users.
  • Where possible, link to cross-platform documentation or tools for Service Fabric management.
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: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page presents Windows/PowerShell and Visual Studio parameters and examples before Linux equivalents (SFCTL). The PowerShell and Visual Studio sections are more detailed and appear first, with SFCTL (the cross-platform CLI) covered later. There are more explicit parameter examples for PowerShell, and Windows tools are referenced more frequently. Linux users may need to scroll or search to find relevant CLI information, and the structure may imply Windows as the default environment.
Recommendations
  • Reorganize the page to present cross-platform tools (SFCTL) before or alongside Windows-specific tools (PowerShell, Visual Studio).
  • Provide equivalent parameter examples for SFCTL, including sample command lines and JSON payloads.
  • Clarify early in the article that SFCTL is the recommended cross-platform tool for Linux/macOS users.
  • Add a summary table mapping parameters across PowerShell, Visual Studio, and SFCTL for easy comparison.
  • Ensure all examples and descriptions are equally detailed for SFCTL as for PowerShell/Visual Studio.
GitHub Create Pull Request
Service Fabric Upgrading Azure Service Fabric clusters ...icles/service-fabric/service-fabric-cluster-upgrade.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page provides general guidance for upgrading Azure Service Fabric clusters, but exhibits Windows bias in several areas. References to PowerShell and Windows-specific patching tools (Patch Orchestration Application) are made without equivalent Linux examples or guidance. The section on OS image upgrades links only to Windows patching documentation, and PowerShell is mentioned as a management tool alongside Azure CLI, but Linux-native tools or workflows are not described. The order of mention and lack of Linux-specific guidance creates friction for Linux/macOS users.
Recommendations
  • Add explicit Linux cluster upgrade guidance, including links to Linux patching documentation and relevant tools.
  • Provide Azure CLI examples for all management tasks, and clarify which commands are cross-platform.
  • Mention Linux support and differences where applicable, especially in sections about OS image upgrades and certificate management.
  • Ensure that references to PowerShell are balanced with Azure CLI or Bash examples.
  • Link to Linux-specific Service Fabric documentation where available.
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 ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page for on-demand backup in Azure Service Fabric is heavily focused on PowerShell-based workflows and commands, with all CLI examples using PowerShell syntax and modules. There are no examples or guidance for Linux/macOS users (e.g., Bash, Azure CLI, curl), and the prerequisite steps assume a Windows environment. The REST API is referenced, but only invoked via PowerShell, not with cross-platform tools.
Recommendations
  • Add equivalent examples using Bash/curl or Azure CLI for REST API calls, so Linux/macOS users can follow along.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is required for all scenarios, or if REST API calls can be made directly from any platform.
  • Provide guidance for connecting to Service Fabric clusters from Linux/macOS, including certificate handling and authentication.
  • Mention any cross-platform tools (such as Azure CLI or Service Fabric CLI) that can be used for backup operations.
  • Explicitly state platform requirements if certain steps are Windows-only, and offer alternatives where possible.
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 information, but does not include equivalent examples for Linux or cross-platform CLI tools. This may create friction for Linux/macOS users who do not use PowerShell or Windows environments.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • Where possible, provide both PowerShell and CLI (sfctl) commands side by side.
  • Clarify in the example sections that the shown PowerShell commands are for Windows, and link to documentation for Linux/macOS management 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, with no reference to Linux or cross-platform CLI equivalents. Windows security is mentioned as a transport option alongside X509 certificates, but Linux alternatives are not discussed. The management subsystem section leads with Windows tooling (PowerShell), suggesting Windows-first bias.
Recommendations
  • Add references to cross-platform management tools, such as Azure CLI or REST APIs, where applicable.
  • Clarify whether PowerShell cmdlets are available on Linux/macOS (via PowerShell Core), or provide Linux-specific examples.
  • Mention Linux-compatible security mechanisms in the transport subsystem (e.g., use of X509 certificates, Kerberos, etc.).
  • Ensure examples and tooling references are balanced between Windows and Linux environments.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager - Application Groups ...ice-fabric-cluster-resource-manager-application-groups.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page provides PowerShell and C# examples exclusively for configuring Service Fabric Application Groups, with no mention of Linux-compatible CLI tools (such as sfctl) or Bash examples. All command-line instructions use PowerShell cmdlets, which are native to Windows, and there is no guidance for Linux/macOS users on how to perform equivalent operations.
Recommendations
  • Add examples using sfctl (Service Fabric CLI), which is cross-platform and works on Linux/macOS, for all PowerShell command scenarios.
  • Explicitly mention that PowerShell commands are Windows-specific and provide alternative instructions for Linux/macOS users.
  • Include Bash or shell script examples where appropriate.
  • Clarify any limitations or differences in feature support between Windows and Linux Service Fabric clusters, if relevant.
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 presents security scenarios for Azure Service Fabric clusters, but consistently references Windows Server clusters and Windows-specific security mechanisms (such as Windows authentication and Windows certificate services) before or instead of Linux equivalents. There are explicit links and instructions for securing standalone clusters on Windows, but no corresponding guidance or links for standalone Linux clusters. The concept of Linux clusters is briefly mentioned, but practical examples, instructions, or references are missing.
Recommendations
  • Add explicit sections or links for securing standalone Linux Service Fabric clusters, including certificate setup and client authentication.
  • Provide Linux-specific examples for certificate generation and management (e.g., using OpenSSL instead of Windows certificate services).
  • Clarify which security mechanisms are available or recommended for Linux clusters, and highlight any differences.
  • Ensure parity in guidance for both Windows and Linux, including references to relevant tools and templates for Linux environments.
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: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page provides Service Fabric manifest examples and explanations. While the XML manifests themselves are cross-platform, there are subtle signs of Windows bias: Windows tools and concepts (such as 'Setup.bat', 'VotingWeb.exe', and references to 'Administrators' and 'NetworkService' accounts) are used in examples, and PowerShell is mentioned as a deployment tool. Linux equivalents (such as shell scripts, Linux user/group concepts, or Linux deployment tools) are not provided or referenced.
Recommendations
  • Add Linux-specific examples alongside Windows ones, such as using shell scripts (.sh) in SetupEntryPoint and EntryPoint.
  • Mention Linux user/group concepts and how Service Fabric handles them on Linux clusters.
  • Reference Linux deployment tools (e.g., Azure CLI or sfctl) in addition to PowerShell.
  • Clarify any platform-specific differences in manifest usage, especially for user accounts and script execution.
  • Consider showing both Windows and Linux file naming conventions and executable formats in example manifests.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Events ...es/service-fabric/service-fabric-diagnostics-events.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page for Azure Service Fabric Events references Windows-specific logging mechanisms (ETW/Windows Event logs) and the Windows Azure diagnostics agent as primary ways to access events. There are no explicit examples or guidance for accessing Service Fabric events on Linux clusters, nor are Linux-native tools or patterns mentioned. The ordering and language suggest Windows as the default environment, creating friction for Linux users.
Recommendations
  • Add explicit guidance and examples for accessing Service Fabric events on Linux clusters, including supported logging mechanisms and monitoring tools.
  • Mention Linux-native equivalents (such as syslog, journald, or Azure Monitor integration for Linux nodes) alongside Windows tools.
  • Clarify which event access methods are cross-platform and which are Windows-only.
  • Provide sample commands or configuration snippets for Linux environments where possible.
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: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides examples for managing application parameters in Azure Service Fabric, with a noticeable preference for Windows/PowerShell tools. PowerShell is mentioned first and in detail, and Visual Studio (a Windows-centric IDE) is referenced for parameter management. Linux tools (sfctl) are mentioned, but not as prominently or with as much detail. There are no explicit Linux/macOS examples or workflows, and the scripting examples (Deploy-FabricApplication.ps1) are Windows-specific.
Recommendations
  • Provide Linux/macOS-specific examples, such as using sfctl and shell scripts for parameter management.
  • Include guidance for managing parameters using cross-platform tools and editors (e.g., VS Code, CLI).
  • Ensure parity in example detail and order: mention sfctl and Linux workflows before or alongside PowerShell.
  • Add sample shell scripts (e.g., install.sh) for Linux users, similar to the PowerShell examples.
  • Clarify which tools are cross-platform and which are Windows-only, to help users choose the right workflow.
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_first ⚠ī¸ windows_tools
Summary
The documentation page provides extensive PowerShell examples and references Windows-specific tools and patterns (such as the Key Vault VM extension for Windows, S-channel, and certificate store locations like 'LocalMachine'). Windows terminology and mechanisms (ACLing, certificate linking, S-channel) are discussed in detail, while Linux/macOS equivalents are not mentioned or are missing. The PowerShell example is the only programmatic enrollment script shown, and Windows-specific features (like certificate linking) are explained without Linux alternatives.
Recommendations
  • Add equivalent Linux/macOS examples for certificate enrollment and management (e.g., using Azure CLI, Bash, or Python SDK).
  • Clarify which mechanisms (such as Key Vault VM extension) are available or not available on Linux, and provide guidance for Linux users.
  • Discuss certificate provisioning and rotation on Linux nodes, including how Service Fabric clusters on Linux VMs handle certificates.
  • Provide troubleshooting steps and FAQs relevant to Linux/macOS environments.
  • Where Windows-specific features are discussed (e.g., S-channel, certificate linking), explicitly note their absence or alternatives on Linux.
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_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page primarily references Windows tools and patterns (e.g., certificate stores like LocalMachine\My, Win32 CryptoAPI, CAPI2 logging, and Windows event logs) when discussing certificate management, troubleshooting, and configuration. Linux equivalents are mentioned only briefly or parenthetically, and there are no concrete Linux/macOS-specific troubleshooting steps or examples. Windows terminology and APIs are presented first and in detail, while Linux is referenced as an aside (e.g., 'or the Linux equivalent path, /var/lib/sfcerts').
Recommendations
  • Provide explicit Linux/macOS examples for certificate storage, retrieval, and troubleshooting (e.g., using OpenSSL, viewing logs, certificate file locations).
  • Document Linux/macOS-specific paths, commands, and log locations alongside Windows examples, not just as parentheticals.
  • Include troubleshooting steps for Linux clusters, such as how to check certificate permissions, validate certificate chains, and interpret relevant logs.
  • Clarify which APIs or behaviors are platform-specific (e.g., Win32 CryptoAPI, CAPI2 logging) and offer Linux/macOS alternatives where possible.
  • Add a table or section summarizing differences and equivalents between Windows and Linux certificate management in Service Fabric.
GitHub Create Pull Request
Service Fabric Custom Image .../articles/service-fabric/how-to-deploy-custom-image.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page primarily focuses on deploying custom Windows images in Azure Service Fabric Managed Clusters. Windows terminology and PowerShell examples are used, and Windows-specific tools and patterns are mentioned first or exclusively. While there is a brief reference to Linux custom image creation, the main guidance, examples, and tooling are Windows-centric, potentially creating friction for Linux/macOS users.
Recommendations
  • Provide Linux/macOS CLI examples alongside PowerShell commands, especially for role assignment and image management.
  • Clarify which steps are OS-agnostic and which are Windows-specific, and add explicit guidance for Linux custom images where relevant.
  • Include links to Linux documentation and examples for creating and managing custom images, and for assigning roles using Azure CLI.
  • Ensure ARM template examples and image references are equally applicable to Linux images, and explicitly mention Linux support where possible.
GitHub Create Pull Request
Service Fabric Azure Service Fabric container image management .../articles/service-fabric/container-image-management.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation references Windows container base images (microsoft/windowsservercore, microsoft/nanoserver) as default exclusions in cleanup settings, but does not mention Linux container base images or provide examples relevant to Linux containers. There are no explicit Linux-specific examples or guidance, and Windows images are referenced first and exclusively.
Recommendations
  • Include examples of Linux container base images (e.g., 'docker.io/library/ubuntu', 'docker.io/library/alpine') in the ContainerImagesToSkip setting.
  • Clarify whether the cleanup features and settings apply equally to Linux containers, and provide guidance or examples for Linux container scenarios.
  • Add a note on cross-platform support, specifying any limitations or differences for Linux vs. Windows containers.
  • Ensure parity in documentation by referencing both Windows and Linux container images in explanations and examples.
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 method shown, with no mention of Azure CLI or Bash scripting alternatives. PowerShell examples are presented for all major operations (add, remove, scale, configure placement properties), and are often listed before or alongside portal and ARM template methods. This creates friction for Linux/macOS users, as PowerShell is less commonly used or installed on those platforms compared to Azure CLI.
Recommendations
  • Add Azure CLI examples for all operations currently demonstrated with PowerShell.
  • Explicitly state that PowerShell examples are cross-platform (if true), or provide guidance for Linux/macOS users on how to use PowerShell Core.
  • Where possible, provide Bash scripting examples or reference Azure CLI documentation for equivalent tasks.
  • Ensure that CLI examples are presented in a platform-neutral way, or alternate the order to avoid Windows-first bias.
GitHub Create Pull Request
Service Fabric Initializer CodePackages in Service Fabric ...in/articles/service-fabric/initializer-codepackages.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page for Initializer CodePackages in Service Fabric provides only Windows-based examples, including Windows container images, Windows file paths, and Windows-specific commands (e.g., cmd, C:\ paths, type, ping). There are no Linux container or cross-platform examples, and the only complete example is explicitly for Windows containers. This creates friction for Linux users and those deploying on Linux-based Service Fabric clusters.
Recommendations
  • Add a parallel example using Linux containers (e.g., using Ubuntu or Alpine images) with Linux shell commands and file paths.
  • Clarify in the introduction whether Initializer CodePackages are supported for Linux containers and, if so, provide guidance or links.
  • If there are limitations for Linux support, explicitly state them and link to relevant documentation.
  • Ensure that examples and file paths are shown for both Windows and Linux where applicable, or note platform-specific differences.
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 frequently references Az PowerShell cmdlets (e.g., Remove-AzResource, AzSF PowerShell cmdlet) for managing Service Fabric resources, and these examples are presented before or instead of Azure CLI equivalents. While Azure CLI is mentioned once (az resource), PowerShell commands dominate, which may create friction for Linux/macOS users who typically use Azure CLI. No Linux-specific tools or examples are provided.
Recommendations
  • Provide Azure CLI command examples alongside PowerShell cmdlets for all operations (e.g., deleting, creating, scaling resources).
  • Clarify which commands are cross-platform and which are Windows-only.
  • Add explicit notes or tables showing parity between PowerShell and Azure CLI for each operation.
  • Consider referencing ARM template usage in a platform-neutral way.
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 demonstrates notable Windows bias. All code examples use Windows containers (nanoserver:1809) and Windows-specific commands (cmd, echo, ping, set, exit). The 'Query deployment status' section only references PowerShell and C# APIs, with no mention of Linux or cross-platform tooling. There are no examples or guidance for Linux containers or Linux-based workflows, despite Service Fabric supporting containers in general.
Recommendations
  • Add equivalent examples using Linux containers (e.g., Ubuntu or Alpine images) and Linux shell commands.
  • Clarify whether RunToCompletion semantics are supported for Linux containers, and if so, provide Linux-specific guidance.
  • Include instructions for querying deployment status using cross-platform CLI tools (e.g., Azure CLI, sfctl) or Linux shell commands.
  • Where possible, present both Windows and Linux examples, or note platform-specific limitations.
  • Update introductory notes to explicitly state if RunToCompletion is Windows-only, or highlight Linux support if available.
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 best practice examples primarily using Azure PowerShell modules, with explicit links to PowerShell commands for cluster management tasks. While Azure CLI and ARM/Bicep are mentioned in a summary table, PowerShell is highlighted first in the best practices section and is the only example given for specific operations (delete, restart, reimage). There are no Linux/macOS-specific command examples or explicit parity for cross-platform tools in the main guidance.
Recommendations
  • Add Azure CLI command examples for deleting, restarting, and reimaging NodeTypes/VMSS, alongside PowerShell examples.
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Consider providing sample scripts or links for ARM/Bicep deployments relevant to the described operations.
  • Reorder examples so that cross-platform tools (Azure CLI, ARM/Bicep) are shown before or alongside PowerShell.
  • Clarify that PowerShell examples are also available on Linux/macOS, or provide alternative CLI syntax.
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: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides detailed PowerShell-based migration steps for Service Fabric clusters, especially in the 'Basic SKU load balancer and IP resources' migration scenario. All imperative command-line examples use PowerShell cmdlets, with no equivalent Azure CLI or bash examples. This may create friction for Linux/macOS users who do not have access to PowerShell or prefer cross-platform tooling.
Recommendations
  • Provide equivalent Azure CLI (az) commands for all PowerShell examples, especially for resource deployment, node disabling, and resource cleanup.
  • Explicitly mention that the migration can be performed from any platform using Azure CLI or ARM templates, not just PowerShell.
  • Where possible, link to ARM/Bicep template documentation and show how to use them from bash or cross-platform environments.
  • Add a note clarifying that PowerShell is not required and that all operations can be performed using cross-platform tools.
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 covers monitoring for both Windows and Linux Service Fabric clusters, but there are several areas where Windows tools and patterns are mentioned first or exclusively, and Linux equivalents are referenced later or less prominently. Some examples and tutorials are Windows/.NET-centric, and certain features (like EventStore APIs) are Windows-only, but this is clearly stated. Linux monitoring is supported, but configuration details and examples are less visible or are referenced via links rather than inline explanations.
Recommendations
  • Ensure Linux monitoring configuration steps and examples are as prominent and detailed as Windows ones, especially for cluster and infrastructure monitoring.
  • Provide Linux-specific tutorials and code samples (e.g., for application logging, cluster diagnostics, and performance counters) alongside Windows/.NET examples.
  • Mention Linux tools and patterns (such as LTTng, Syslog, and relevant logging frameworks) before or alongside Windows tools like ETW and Event Viewer.
  • Clarify which features are Windows-only and provide alternative approaches for Linux users where possible.
  • Add links to Linux-focused monitoring partner integrations and open source tools.
GitHub Create Pull Request
Service Fabric Describing Azure Service Fabric apps and services ...ic/service-fabric-application-and-service-manifests.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page for describing Azure Service Fabric apps and services exhibits mild Windows bias. It references Windows file paths (e.g., 'C:\Program Files\Microsoft SDKs\Service Fabric\schemas\ServiceFabricServiceModel.xsd'), suggests using Visual Studio (a Windows-centric tool) for schema validation, and mentions the ServiceFabric PowerShell module for service creation. No equivalent Linux tooling or examples are provided, and Windows-specific patterns are mentioned first or exclusively. However, the core content (manifest XML) is platform-neutral, and Linux users can complete the tasks with workarounds.
Recommendations
  • Add instructions for validating manifest XML schema on Linux/macOS, such as using 'xmllint' or VS Code with XML extensions.
  • Mention cross-platform alternatives to Visual Studio, like Visual Studio Code or JetBrains Rider.
  • Provide examples of using Service Fabric CLI (sfctl) or REST API for service creation, alongside PowerShell.
  • Clarify that Service Fabric development and deployment can be done on Linux, and link to relevant Linux documentation.
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 pattern), and does not offer equivalent Linux CLI or scripting examples. Enabling DNS service via Azure portal is only possible for Windows clusters, and Linux support is limited and discussed secondarily. There are no Linux-specific deployment or configuration examples, and Windows tools/patterns are mentioned first or exclusively.
Recommendations
  • Add Linux CLI examples (e.g., Bash, Azure CLI) for setting DNS names and managing Service Fabric services.
  • Clarify Linux deployment workflows, including how to set DNS names for containerized services on Linux clusters.
  • Provide guidance for enabling DNS service on Linux clusters using ARM templates or other methods, since portal support is unavailable.
  • Include notes or links to Linux-specific documentation or troubleshooting.
  • Balance the order of Windows and Linux information, mentioning Linux options alongside Windows where applicable.
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 exhibits some Windows bias. Windows-specific tools and patterns (e.g., Active Directory, gMSA, BitLocker, NetworkService account) are mentioned before or more prominently than Linux equivalents. Some sections (e.g., disk encryption, user accounts) provide Windows-focused examples or references, while Linux guidance is missing or relegated to TODO comments.
Recommendations
  • Add Linux-specific examples for disk encryption (e.g., using Azure Disk Encryption with Linux VMSS, or referencing LUKS).
  • Provide guidance on configuring user accounts and security principals for Linux clusters, including how to run services under different Linux users/groups.
  • Ensure parity in certificate management and container security examples for Linux clusters.
  • When mentioning Windows tools or patterns (e.g., BitLocker, gMSA, NetworkService), immediately follow with Linux equivalents or clarify platform applicability.
  • Remove or resolve TODO comments regarding Linux disk encryption and provide actionable documentation.
  • Include sample manifests or scripts for Linux scenarios where possible.
GitHub Create Pull Request
Service Fabric Service Fabric application upgrade ...s/service-fabric/service-fabric-application-upgrade.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page for Service Fabric application upgrade demonstrates notable Windows bias. PowerShell is used exclusively in the main example for upgrading applications and handling application parameters, with no equivalent CLI or Linux-native example. Windows-specific tools (PowerShell, http.sys) are referenced without mention of cross-platform alternatives. The 'Next steps' section prioritizes Visual Studio and PowerShell tutorials, both Windows-centric, with no Linux or cross-platform guidance. This creates friction for Linux/macOS users, who may not have access to PowerShell or Visual Studio.
Recommendations
  • Add equivalent examples using Azure CLI or Service Fabric CLI (sfctl), which are cross-platform and supported on Linux/macOS.
  • Mention Linux/macOS-compatible tools and workflows for application upgrades.
  • Provide links to Linux/macOS-specific documentation or tutorials, if available.
  • Clarify which features are Windows-only and which are cross-platform, especially when referencing http.sys or PowerShell.
  • Ensure that examples and guidance are balanced, showing both Windows and Linux approaches where possible.
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: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation frequently uses PowerShell cmdlets (e.g., Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState) for manual scaling operations without providing equivalent Linux/CLI commands. All step-by-step manual procedures reference PowerShell, and there are no Bash, Azure CLI, or REST API alternatives shown. The documentation also refers to 'PowerShell' generically for cluster management tasks, which may not be directly applicable to Linux/macOS users. Additionally, in several sections, Windows tools and patterns are mentioned first or exclusively, with Linux alternatives only referenced in the 'Next steps' section.
Recommendations
  • For every PowerShell-based example (e.g., Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState), provide equivalent Azure CLI, Bash, or REST API commands where possible.
  • Explicitly state when a command or tool is Windows-only, and link to Linux/macOS alternatives.
  • In step-by-step guides, offer parallel instructions for Linux users, or clarify if the operation must be performed from a Windows environment.
  • When referencing Service Fabric Explorer or other tools, note any cross-platform considerations.
  • Balance the order of 'Next steps' so Linux and Windows cluster creation links are presented equally.
GitHub Create Pull Request
Service Fabric Azure Service Fabric networking best practices ...ice-fabric/service-fabric-best-practices-networking.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ minor_windows_example
Summary
The documentation provides both Windows and Linux guidance for Service Fabric networking, but there are several areas where Windows concepts, tools, and examples are emphasized or presented first. PowerShell and Windows-specific terminology appear more frequently, and some example links and references (such as ARM templates and DevOps tasks) are Windows-centric. Linux equivalents are mentioned but often after Windows, and some explanations assume familiarity with Windows networking tools.
Recommendations
  • Ensure Linux examples and references are given equal prominence and are presented alongside Windows examples, not after.
  • Where PowerShell is mentioned, include corresponding Bash/CLI commands for Linux users.
  • Add links to Linux-focused ARM templates and sample clusters, not just Windows ones.
  • Clarify which features or steps are platform-agnostic and which are Windows-specific.
  • Expand explanations for Linux networking (e.g., dynamic port ranges, firewall configuration) to match Windows detail.
  • Avoid referencing Windows tools (e.g., netsh) without Linux equivalents (e.g., ss, iptables, etc.).
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 frequently references PowerShell cmdlets and Windows-centric tooling for Service Fabric application lifecycle operations, often listing them before or alongside REST API and .NET methods. There is minimal mention of Linux-specific tools or CLI equivalents, and PowerShell is presented as the primary scripting interface. While REST API and .NET methods are included, Linux users may experience friction due to the lack of explicit Linux/CLI examples and guidance.
Recommendations
  • Add explicit examples using Service Fabric CLI (sfctl) and Azure CLI for each lifecycle operation, especially for deployment, upgrade, removal, and cleanup tasks.
  • Where PowerShell cmdlets are mentioned, also provide equivalent sfctl or Azure CLI commands, and clarify their applicability to Linux/macOS environments.
  • Reorder examples so that cross-platform tools (REST API, sfctl, Azure CLI) are listed before or alongside PowerShell cmdlets.
  • Include a section or note clarifying which tools are available and supported on Linux/macOS, and link to relevant Linux documentation.
  • Provide sample shell scripts or command-line workflows for Linux users, especially for automation and cleanup scenarios.
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 provides extensive PowerShell-based examples and references, with no mention of Linux/macOS equivalents (such as Azure CLI, REST API, or cross-platform tooling). Windows/PowerShell tools are referenced exclusively and repeatedly, and all command-line examples are PowerShell-centric. There is no guidance for Linux/macOS users on how to perform the same tasks, despite Service Fabric supporting cross-platform clusters and management.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell cmdlets shown, especially for application upgrades, service creation, and parameter updates.
  • Reference REST API endpoints where applicable, and provide sample payloads for ARM template operations.
  • Explicitly mention cross-platform management options (e.g., Azure CLI, REST API, SDKs) and link to relevant documentation.
  • Where PowerShell is referenced, clarify if the cmdlets are available on Linux/macOS (via PowerShell Core), or provide alternatives if not.
  • Ensure that 'Next steps' and tutorial links include Linux/macOS-compatible workflows (e.g., CLI or SDK-based tutorials).
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: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page for restoring backup in Azure Service Fabric is heavily biased toward Windows and PowerShell usage. All code examples use PowerShell, including REST API calls, and require the Microsoft.ServiceFabric.Powershell.Http module. There are no examples or guidance for Linux/macOS users, such as using Bash, curl, or cross-platform tools. The documentation assumes the reader is using Windows and PowerShell, creating friction for Linux/macOS users.
Recommendations
  • Add equivalent Bash/curl examples for REST API calls, showing how to authenticate and invoke the Service Fabric APIs from Linux/macOS.
  • Document any cross-platform CLI tools (e.g., Azure CLI, Service Fabric CLI) that can be used for backup/restore operations.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is required for REST API calls, or if standard HTTP tools can be used.
  • Mention prerequisites or limitations for Linux/macOS users, and provide links to relevant cross-platform guidance.
  • Consider providing a table or section comparing Windows and Linux/macOS approaches for backup/restore operations.
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 provides a generally platform-neutral overview of periodic backup configuration in Azure Service Fabric. However, in the 'File share' backup storage section, Windows-specific patterns are emphasized: examples use UNC paths (\\StorageServer\BackupStore), and authentication options focus on Integrated Windows Authentication and username/password, which are Windows-centric. There is no mention of Linux-compatible file share options (e.g., SMB/CIFS mounts on Linux, NFS, or Azure Files usage from Linux nodes). The documentation also presents Windows file share options before any discussion of Linux equivalents, and does not clarify cross-platform support or limitations.
Recommendations
  • Add examples and guidance for configuring file share backup storage from Linux-based Service Fabric clusters, including supported protocols (e.g., SMB/CIFS, NFS, Azure Files) and authentication methods.
  • Clarify whether Integrated Windows Authentication is required, or if Linux clusters can use username/password or other mechanisms.
  • Explicitly state any platform limitations for file share backup storage, and provide parity guidance for Linux/macOS users.
  • Consider including a note or section on cross-platform compatibility for all backup storage types.
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 presented as a separate section and is heavily used for cluster upgrade operations. Windows-specific tools and registry keys are mentioned for patch management and update disabling, with no Linux equivalents or guidance. The manual upgrade section only provides PowerShell commands for Windows, omitting Linux (deb) instructions. Windows configuration properties are shown first in VM scale set examples. While Linux is referenced in template samples and cluster creation links, the operational guidance and scripting are notably Windows-centric.
Recommendations
  • Add equivalent Linux shell (bash) examples for cluster upgrade operations, especially for manual upgrades using deb packages.
  • Include guidance on disabling automatic updates for Linux VM scale sets, such as relevant OS profile settings or scripts.
  • Provide Linux-specific instructions or notes where Windows registry keys and PowerShell are referenced.
  • Ensure parity in operational examples by including both Windows and Linux approaches side-by-side.
  • When showing VM scale set configuration, include Linux configuration properties alongside Windows.
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 examples for key security tasks, such as certificate generation and secret encryption. However, Windows-specific tools (PowerShell, Windows Defender, Azure DSC) are often mentioned first or exclusively, and Windows-centric guidance (e.g., security baselines, Defender exclusions) is more detailed. Linux equivalents are present but sometimes less prominent or detailed.
Recommendations
  • Ensure Linux examples are given equal prominence and detail as Windows examples, especially for certificate management and secret encryption.
  • Where Windows tools (e.g., PowerShell, Windows Defender, DSC) are mentioned, provide clear Linux alternatives or note their absence.
  • Add guidance for Linux security baselines and antimalware solutions, or explicitly state if no equivalent exists.
  • Consider alternating the order of Windows and Linux examples to avoid 'windows_first' bias.
  • Expand Linux-specific troubleshooting and best practices sections to match Windows coverage.
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 ⚠ī¸ data_path_windows_pattern ⚠ī¸ powershell_heavy
Summary
The documentation generally covers both Linux and Windows node types for Azure Service Fabric clusters, but there are subtle signs of Windows bias. The 'dataPath' example uses a Windows-style path ('D:\\SvcFab'), and the 'Next steps' section links primarily to PowerShell scripts for Windows-specific tasks (changing RDP port range, admin username/password), without Linux equivalents or Bash/CLI alternatives. Windows patterns and tools are referenced first or exclusively in some places.
Recommendations
  • Provide Linux-style examples for 'dataPath' (e.g., '/var/svcfab') alongside Windows paths.
  • Add links or instructions for performing remote connection, port changes, and admin credential updates on Linux clusters, using Bash or Azure CLI.
  • Ensure parity in 'Next steps' by including Linux-focused guidance and scripts.
  • Clarify when instructions or examples are Windows-only, and offer Linux alternatives where possible.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager: Movement cost ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-movement-cost.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides PowerShell examples for configuring move cost, but does not include equivalent Linux/bash/CLI examples. PowerShell is primarily a Windows tool, and its exclusive use creates friction for Linux/macOS users. The C# examples are cross-platform, but administrative/configuration examples are Windows-centric. There is no mention of Azure CLI, Bash, or Linux-native tools for managing Service Fabric services.
Recommendations
  • Add Azure CLI or Bash examples for creating and updating Service Fabric services with move cost.
  • Explicitly mention whether PowerShell commands are supported on Linux/macOS (via PowerShell Core), and provide guidance for those platforms.
  • If PowerShell is the only supported scripting interface, clarify this in the documentation and link to any Linux/macOS installation instructions.
  • Consider including REST API examples for service management tasks, which are platform-neutral.
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 ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page provides code examples for configuring Service Fabric placement policies using C# and PowerShell only. PowerShell is a Windows-centric tool, and there are no examples or guidance for Linux-based Service Fabric clusters, such as using Azure CLI, REST API, or cross-platform tools. This creates friction for Linux/macOS users who cannot use PowerShell natively.
Recommendations
  • Add equivalent examples using Azure CLI (az sf) for all placement policy configurations.
  • Document how to configure placement policies via ARM templates or REST API for cross-platform automation.
  • Explicitly note any differences or limitations for Linux-based Service Fabric clusters, if applicable.
  • If PowerShell is required, mention how to use PowerShell Core on Linux/macOS, or provide alternatives.
  • Consider including YAML or JSON snippets for ARM/Bicep deployments where relevant.
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 examples for configuring auto scaling in Azure Service Fabric using application manifests, C# APIs, and PowerShell. However, all CLI/script examples are PowerShell-based, with no Linux shell (bash/CLI) equivalents. PowerShell is presented as the only scripting option, and there is no mention of Linux tools or commands for managing scaling policies. The documentation does note that resource monitoring is supported for containerized applications on Linux, but practical Linux usage examples are missing.
Recommendations
  • Add equivalent bash/CLI examples for managing scaling policies on Linux clusters, using Service Fabric CLI (sfctl) or REST APIs.
  • Explicitly mention cross-platform management tools and provide links or references to Linux/macOS documentation.
  • Clarify which PowerShell commands are available on Linux (via PowerShell Core), or provide alternative commands if they are Windows-only.
  • Include a section or note on how Linux users can perform the same operations, especially for containerized workloads.
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 ⚠ī¸ windows_tools
Summary
The documentation provides both Windows-specific (ClusterManifest.xml with <WindowsServer>) and cross-platform (ClusterConfig.json) configuration examples. However, Windows terminology and XML examples are presented first and more prominently, and PowerShell is used for CLI examples, with no Linux shell or cross-platform CLI equivalents. The use of WindowsServer in the XML and PowerShell commands suggests a Windows-first bias, though Linux/standalone parity is addressed via JSON examples.
Recommendations
  • Include Linux-specific or cross-platform CLI examples (e.g., Azure CLI, Bash) alongside PowerShell.
  • Present Linux/standalone configuration examples (ClusterConfig.json) before or equally with Windows XML examples.
  • Clarify which features and configuration patterns are supported on Linux clusters, and note any Windows-only limitations.
  • Add explicit guidance or links for Linux users, such as how to run Service Fabric clusters on Linux and configure fault/upgrade domains.
  • Where PowerShell is used, provide equivalent Azure CLI or Bash script examples.
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 using C# and PowerShell. PowerShell is a Windows-centric tool, and no equivalent Linux/macOS CLI examples (such as Azure CLI or Bash) are provided. The PowerShell examples are prominent and appear before any mention of alternative tooling. There is no discussion of how Linux users can accomplish these tasks, nor is there mention of cross-platform tools or patterns.
Recommendations
  • Add Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention whether the PowerShell commands are supported on Linux (via PowerShell Core), or provide Bash scripts if possible.
  • Clarify any platform-specific limitations for Service Fabric management, and provide guidance for Linux/macOS users.
  • Consider including REST API or SDK usage examples that are platform-agnostic.
  • Reorder examples so that cross-platform options (Azure CLI, REST API) are shown 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_first ⚠ī¸ missing_linux_example
Summary
The documentation provides PowerShell examples for configuring service sensitivity and maximum load, but does not mention or provide equivalent CLI or scripting examples for Linux/macOS users. PowerShell is presented as the primary scripting interface, and there is no reference to Service Fabric CLI (sfctl) or REST API usage, which are cross-platform. This creates friction for Linux/macOS administrators who may not have access to PowerShell or prefer native tools.
Recommendations
  • Add examples using Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • Mention REST API options for configuring service sensitivity and maximum load, with example requests.
  • Clarify which PowerShell commands are available on Linux (via PowerShell Core) and which are Windows-only.
  • Present CLI or REST API examples before or alongside PowerShell examples to avoid Windows-first bias.
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 patterns primarily using PowerShell and C#, with no equivalent Linux CLI or scripting examples. Windows/PowerShell tools are referenced exclusively and first, creating friction for Linux users who may need to perform similar operations using Service Fabric CLI or REST APIs. The section 'Choosing a platform' does acknowledge Linux-specific implementation differences, but the practical guidance and examples remain Windows-centric.
Recommendations
  • Add equivalent Linux command-line examples using Service Fabric CLI (sfctl) or REST API for operations such as updating instance counts, creating services, and managing applications.
  • Mention Linux tools and administrative patterns alongside PowerShell, not just in the 'Choosing a platform' section.
  • Where PowerShell is referenced, provide a note or link to Linux documentation or examples.
  • Ensure that guidance for scaling, service creation, and management is platform-neutral or clearly indicates platform-specific steps.
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 page provides PowerShell examples for managing node tags and service requirements, but does not offer equivalent examples for Linux/macOS users (e.g., Bash, CLI, or REST API usage). PowerShell is a Windows-centric tool, and its exclusive use creates friction for users on other platforms. The page also references PowerShell before C# APIs, and does not mention or demonstrate Azure CLI or REST API commands, which are cross-platform.
Recommendations
  • Add Azure CLI examples for all node tag and service tag operations, as Azure CLI is cross-platform and widely used.
  • Include REST API usage examples for managing node tags and service requirements, since REST APIs are platform-agnostic.
  • Explicitly mention that PowerShell commands can be run on Linux/macOS if supported, or clarify any limitations.
  • Consider providing Bash script examples or guidance for Linux users where applicable.
  • Reorder examples so that cross-platform tools (CLI/REST) are presented before Windows-specific tools like PowerShell.
GitHub Create Pull Request
Service Fabric Azure Service Fabric standalone cluster scaling ...ce-fabric/service-fabric-cluster-scaling-standalone.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page on scaling Azure Service Fabric standalone clusters demonstrates Windows bias by exclusively referencing Windows PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) and linking to a Windows Server-specific scaling guide. There are no Linux-specific examples, tools, or guidance, despite standalone clusters being deployable on both Windows and Linux. This creates friction for Linux users seeking parity.
Recommendations
  • Add equivalent Linux command-line examples (e.g., using sfctl or REST API) for cluster manifest queries and configuration upgrades.
  • Clarify which steps or tools are Windows-only and provide Linux alternatives where possible.
  • Link to Linux-specific scaling documentation or create a dedicated guide for scaling standalone clusters on Linux.
  • Mention cross-platform management options (such as sfctl, REST API, or Azure CLI) alongside PowerShell.
  • Ensure references to Windows Server guides are balanced with Linux guidance.
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 or cross-platform examples, and Linux equivalents are not mentioned or linked. The page does not clarify whether Linux clusters are supported or provide guidance for Linux users.
Recommendations
  • Add links and instructions for upgrading and configuring Service Fabric standalone clusters running on Linux, if supported.
  • Mention Linux-specific patch orchestration options or clarify if POA is Windows-only.
  • Ensure that references to upgrade/configuration guides are not Windows-exclusive, or clearly state platform limitations.
  • Provide parity in examples and guidance for Linux/macOS users where applicable.
GitHub Create Pull Request
Service Fabric Azure Service Fabric application resource model ...ervice-fabric/service-fabric-concept-resource-model.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates notable Windows bias. All deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) with no mention of Azure CLI equivalents or Linux/macOS-friendly workflows. Application packaging is described via Visual Studio, a Windows-centric tool, with no alternative for Linux/macOS users. There are no examples or guidance for Linux/macOS users, and Windows tools are referenced first and exclusively.
Recommendations
  • Add Azure CLI examples for deployment, upgrade, and deletion tasks (e.g., az deployment group create, az resource delete).
  • Provide guidance for packaging Service Fabric applications using cross-platform tools (such as dotnet CLI or manual zip commands) instead of only Visual Studio.
  • Include instructions and screenshots for Linux/macOS environments where applicable.
  • Clearly indicate which steps are Windows-only and offer alternatives for other platforms.
  • Consider referencing cross-platform editors (e.g., VS Code) for editing manifest and template files.
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 service supporting both Windows and Linux. However, there are several areas where Windows-specific tools, terminology, and examples are mentioned first or exclusively. Windows services and executables (e.g., FabricHost.exe, Fabric.exe) are referenced without Linux equivalents or clarifications. PowerShell is often listed before CLI or REST alternatives. Standalone cluster creation is only supported on Windows, but this is clearly stated. There is a lack of explicit Linux command examples or parity in tooling references, and Windows terminology (e.g., 'auto-start Windows service') is used without Linux context.
Recommendations
  • Where possible, provide Linux-specific examples, especially for cluster management, health queries, and application lifecycle tasks.
  • When referencing tools (e.g., PowerShell, Service Fabric Explorer), ensure CLI and REST API alternatives are equally highlighted and described.
  • Clarify when features, tools, or terminology are Windows-only, and provide Linux equivalents or note limitations.
  • Add explicit Linux command-line examples (using sfctl or bash) alongside PowerShell examples.
  • Review the order of tool references to avoid always listing Windows tools first.
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 demonstrates mild Windows bias. It references Windows file paths (e.g., 'C:\Program Files\Microsoft SDKs\Service Fabric\schemas\ServiceFabricServiceModel.xsd'), and does not provide Linux/macOS equivalents or examples. There are no explicit Linux packaging or deployment instructions, and Visual Studio (a Windows-centric tool) is mentioned as a primary method. The directory structure example uses a Windows-style executable (.exe), and there is no mention of Linux binaries or cross-platform packaging considerations.
Recommendations
  • Add Linux/macOS equivalents for SDK schema file locations, or clarify if the SDK is available on those platforms.
  • Include examples for packaging and deploying Linux/macOS executables (e.g., .sh, ELF binaries) alongside Windows (.exe) examples.
  • Mention cross-platform command-line tools (such as Azure CLI or Service Fabric CLI) and provide instructions for Linux/macOS users.
  • Clarify Visual Studio alternatives for Linux/macOS users, or link to relevant cross-platform tooling.
  • Explicitly state platform support and limitations for guest executables in Service Fabric clusters.
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 page provides a conceptual overview of Service Fabric activation and deactivation lifecycle, but the 'Next steps' section and some linked examples reference PowerShell and Windows-centric tools without mentioning Linux equivalents. There are no explicit Linux/bash examples or references to Linux tooling, and PowerShell is presented as the primary method for deployment/removal, which may create friction for Linux/macOS users.
Recommendations
  • Add equivalent Linux/bash examples for deploying and removing applications, referencing the Service Fabric CLI (sfctl) or REST API.
  • In the 'Next steps' section, include links to Linux/macOS deployment/removal documentation alongside PowerShell.
  • Clarify in the text that Service Fabric supports both Windows and Linux clusters, and highlight any platform-specific differences.
  • Where PowerShell is mentioned, add a note or alternative example for Linux users.
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 demonstrates a Windows bias. The manifest examples are based on a Windows Server 2016 container sample, and references to Windows-specific tools (e.g., 'winver' for OS build detection) are present. There are no explicit Linux-based manifest examples or instructions, and the only mention of Linux is in passing (e.g., certificate handling differences), without concrete Linux-focused guidance or samples.
Recommendations
  • Provide parallel manifest examples based on a Linux container sample, or clarify which elements differ for Linux clusters.
  • When referencing OS build detection, include Linux equivalents (e.g., 'cat /etc/os-release' or 'uname -r') alongside Windows instructions.
  • Explicitly state which manifest elements or features are Windows-only, and which are cross-platform, to help Linux users understand applicability.
  • Add links or references to Linux-specific Service Fabric container documentation where relevant.
  • If certain features (like volume drivers or isolation modes) differ on Linux, note these differences and provide Linux-appropriate configuration guidance.
GitHub Create Pull Request
Service Fabric Health monitoring in Service Fabric ...s/service-fabric/service-fabric-health-introduction.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation provides a detailed conceptual overview of Service Fabric health monitoring, with most of the content being platform-neutral. However, the only concrete example of reporting and evaluating health uses PowerShell cmdlets, which are Windows-centric tools. There are no equivalent examples for Linux or cross-platform environments (e.g., using REST API, CLI, or SDKs), and PowerShell is referenced as the primary method for health reporting. This creates friction for Linux/macOS users, who may not have access to these cmdlets or may prefer other tools.
Recommendations
  • Add equivalent examples using the Service Fabric REST API for health reporting and querying, which are cross-platform.
  • Include code snippets using the Service Fabric SDKs (e.g., .NET Core, Java) for reporting health, which work on Linux/macOS.
  • Mention and provide examples using Azure CLI or Bash scripts if available.
  • Clarify in the example section that PowerShell is one option, and link to documentation for other platforms and tools.
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 provides PowerShell examples for creating services and managing Service Fabric hosting models, but does not include equivalent Linux CLI (e.g., sfctl) or bash examples. PowerShell is presented as the primary method, with REST and .NET API alternatives mentioned, but Linux-native tooling is absent. References to PowerShell cmdlets are frequent and appear before REST or .NET options, creating friction for Linux/macOS users.
Recommendations
  • Add equivalent examples using sfctl (Service Fabric CLI) for Linux/macOS users alongside PowerShell examples.
  • Explicitly mention that all operations shown with PowerShell can be performed with sfctl or REST API, and provide links or sample commands.
  • Where PowerShell cmdlets are referenced, include corresponding sfctl commands in the same section or immediately after.
  • Clarify any platform-specific limitations if certain features are not available on Linux clusters.
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: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a bias towards Windows/PowerShell environments. It references PowerShell for retrieving the cluster manifest and links to a PowerShell-based deployment guide as the next step, without providing equivalent Linux/bash or cross-platform CLI examples. The mention of Visual Studio (a primarily Windows tool) for publishing to Azure further reinforces the Windows-centric approach. There are no explicit Linux or macOS instructions or examples for managing the ImageStoreConnectionString.
Recommendations
  • Add Azure CLI or bash examples for retrieving the cluster manifest and managing the ImageStoreConnectionString, ensuring Linux/macOS users have clear guidance.
  • Include references or links to cross-platform tools or documentation (e.g., Azure CLI, REST API usage with curl) alongside or before PowerShell examples.
  • Mention Visual Studio Code as an alternative to Visual Studio for cross-platform development, if applicable.
  • Provide a 'Next steps' link to a cross-platform deployment guide, not just PowerShell.
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 (HTTP.sys) and cross-platform (Kestrel) web servers for ASP.NET Core in Service Fabric. However, Windows-specific tools and APIs (HTTP.sys, Windows HTTP Server API, netsh) are discussed in detail, with explicit notes about Windows-only support. Kestrel, the cross-platform option, is recommended for Linux, but Linux-specific configuration, troubleshooting, or example code is not provided. Windows tools and patterns (e.g., netsh, ServiceManifest.xml endpoint registration) are mentioned before Linux equivalents, and Linux users may lack guidance for certain scenarios.
Recommendations
  • Add explicit Linux/macOS example configurations, especially for ServiceManifest.xml and Kestrel usage.
  • Include troubleshooting tips for Linux deployments (e.g., firewall, port assignment, certificate management for HTTPS).
  • Clarify any OS-specific limitations or differences for Service Fabric on Linux, such as port assignment, endpoint registration, and service discovery.
  • Provide links or references to Linux-specific Service Fabric documentation where relevant.
  • Ensure that all code samples and configuration snippets are annotated with their OS applicability.
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 deployment instructions and examples exclusively using PowerShell commands, with no mention of Azure CLI, Bash, or Linux/macOS-compatible tooling. Windows-centric tools (PowerShell, RDP, Windows-style file paths) are referenced throughout, and Windows command-line examples are shown first or exclusively. There are no Linux/macOS equivalents or guidance for cross-platform users, despite Service Fabric supporting Linux clusters and Azure Resource Manager templates being deployable from any OS.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all deployment steps, including resource group and template deployment.
  • Mention Bash/terminal usage and provide Linux/macOS-friendly file path examples.
  • Clarify that ARM templates can be deployed from any OS, and link to cross-platform deployment documentation.
  • Include SSH instructions for accessing VMs instead of only referencing RDP.
  • Explicitly state Windows-specific steps where relevant, and provide Linux alternatives where possible.
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. Windows file paths and certificate store names (e.g., 'MY') are referenced first, though Linux equivalents are briefly mentioned. There are no Linux CLI or bash examples for deployment, and Windows terminology/tools are presented before Linux alternatives.
Recommendations
  • Add equivalent Linux CLI (e.g., sfctl) or bash examples for deploying applications and passing parameters.
  • Mention Linux file paths and certificate store locations alongside Windows paths, not just as a note.
  • Clarify any differences in endpoint/certificate handling between Windows and Linux clusters.
  • Where PowerShell is used, provide a Linux command alternative or link to relevant Linux tooling documentation.
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 (Build/Rebuild/F5/Ctrl+F5/Publish), which are Windows-centric. All examples and instructions reference Visual Studio and Windows-specific deployment patterns, with no mention of Linux/macOS equivalents or cross-platform tooling. There are references to PowerShell modules for service creation, but no Linux CLI or scripting alternatives are provided. The documentation does not clarify how Linux/macOS users can achieve similar workflows, nor does it mention cross-platform Service Fabric tooling.
Recommendations
  • Add explicit guidance for Linux/macOS users, including how to manage service configuration and deployment without Visual Studio.
  • Provide CLI-based examples (using Azure CLI, sfctl, or other cross-platform tools) for deploying and configuring Service Fabric applications.
  • Clarify which features are Visual Studio/Windows-only and offer alternatives or workarounds for Linux/macOS environments.
  • Mention any limitations or differences for Linux/macOS users upfront, so expectations are clear.
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: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides usage examples for PowerShell and C#, both of which are most commonly associated with Windows environments. There are no Linux-specific CLI or scripting examples (e.g., Bash, Azure CLI), nor is there mention of Linux tooling or patterns. PowerShell is highlighted as the primary scripting interface, and no Linux/macOS equivalents or guidance are given.
Recommendations
  • Add examples for using Fault Analysis Service via Azure CLI or Bash scripts, if supported.
  • Clarify whether the Fault Analysis Service APIs can be accessed from Linux/macOS environments, and provide guidance for those platforms.
  • Mention cross-platform SDKs or tools (e.g., Python, Java) if available, and provide sample usage.
  • If PowerShell Core (cross-platform) is supported, specify this and provide Linux/macOS installation instructions.
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' heavily references PowerShell cmdlets (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica) and administrative APIs without providing equivalent examples or guidance for Linux/macOS users. All command-line examples and API references are Windows-centric, and there is no mention of Linux tooling or cross-platform alternatives. The documentation assumes familiarity with Windows tools and patterns, creating friction for users operating Service Fabric clusters on Linux.
Recommendations
  • Add examples using Service Fabric CLI (sfctl), which is cross-platform and supported on Linux/macOS.
  • Clarify whether the PowerShell APIs are available via REST or other SDKs usable from Linux/macOS.
  • Provide sample commands for querying, removing, and restoring replicas using sfctl or FabricClient APIs in non-Windows environments.
  • Explicitly state platform limitations if certain features are Windows-only, or highlight parity where available.
  • Include screenshots or output examples from Linux terminals where relevant.
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 page provides extensive PowerShell examples and references, with no equivalent Linux 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 or Service Fabric CLI (sfctl), which are cross-platform and supported on Linux/macOS.
  • Explicitly mention that PowerShell commands are Windows-specific and provide guidance for Linux/macOS users.
  • Include REST API examples with curl or similar tools for Linux/macOS users, especially in sections where PowerShell is used.
  • Reorder examples so that cross-platform methods (API, REST, CLI) are presented before or alongside Windows/PowerShell methods.
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
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation references Azure CLI, Azure PowerShell, and ARM templates for creating Virtual Machine Scale Sets, but does not provide explicit Linux/bash examples or clarify parity between PowerShell and bash usage. Azure PowerShell is mentioned alongside Azure CLI, but no Linux-specific guidance or examples are given. Windows activation and Windows updates are mentioned before Linux package managers in network connectivity scenarios. No Linux-specific migration considerations or examples are provided.
Recommendations
  • Add explicit bash/Linux shell examples for key Azure CLI commands (e.g., az vm create) and clarify that Azure CLI works cross-platform.
  • Provide Linux-specific migration considerations, such as handling SSH keys, Linux VM extensions, and package manager updates.
  • When listing network connectivity scenarios, mention Linux package manager access before or alongside Windows activation and updates.
  • Clarify that Azure PowerShell is primarily for Windows users, and recommend Azure CLI for Linux/macOS users.
  • Include links to Linux VM documentation and migration best practices.
GitHub Create Pull Request
Virtual Machine Scale Sets Networking for Azure Virtual Machine Scale Sets ...ne-scale-sets/virtual-machine-scale-sets-networking.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation generally provides parity between Azure CLI and PowerShell, but in some sections, PowerShell (Windows) examples are presented before CLI (cross-platform) equivalents, and some advanced operations are only shown in PowerShell. There are also a few places where PowerShell is mentioned or shown without an immediately adjacent CLI/Linux example, which may cause friction for Linux/macOS users.
Recommendations
  • Ensure that for every PowerShell example, an equivalent Azure CLI example is provided and shown with equal prominence.
  • When presenting tabbed examples, default to showing Azure CLI (cross-platform) first, or alternate the order to avoid Windows-first bias.
  • Where only PowerShell examples are given (e.g., querying public IPs), add equivalent Azure CLI commands.
  • Review all sections for any missing CLI examples, especially for advanced or update scenarios, and add them.
  • Explicitly note when a feature or command is only available in PowerShell, and provide workarounds or alternatives for Linux/macOS users if possible.
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
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 Linux and Windows examples for configuring custom metrics and the application health extension on Azure Virtual Machine Scale Sets. However, there is evidence of Windows bias: PowerShell examples are consistently present and sometimes shown before Bash/Linux equivalents; Windows-specific extension types (ApplicationHealthWindows) are used in several code snippets; and Windows tools (PowerShell cmdlets) are featured prominently alongside Azure CLI and REST. The Bash/Linux example for the health endpoint is present, but the PowerShell example is more elaborate and appears first in some sections. REST API examples use Windows extension types by default, and the PowerShell section is detailed, potentially creating friction for Linux users.
Recommendations
  • Ensure Linux and Bash examples are given equal prominence and detail as PowerShell examples.
  • In code snippets and tables, use both ApplicationHealthLinux and ApplicationHealthWindows types, or clarify when each should be used.
  • Where PowerShell is used, provide equivalent Bash or Python scripts for Linux/macOS users.
  • In REST API examples, alternate between ApplicationHealthLinux and ApplicationHealthWindows, or explain the difference.
  • Consider listing Bash/Linux examples first in relevant sections to balance ordering.
  • Explicitly state that all features are supported on both Linux and Windows VMSS, and clarify any OS-specific requirements.
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
Medium 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 Azure Virtual Machine Scale Sets using MaxSurge via Portal, CLI, PowerShell, and ARM Template. The PowerShell example is included, which is Windows-specific, and is presented after the CLI example. The CLI example uses Azure CLI, which is cross-platform, but there is no explicit mention of Linux/macOS-specific tools or shell syntax. The documentation does not show Linux-specific commands (e.g., Bash scripts) or highlight Linux workflows. However, the PowerShell example is not shown first, and the CLI example is cross-platform, so the bias is moderate.
Recommendations
  • Clarify that Azure CLI commands are cross-platform and can be used on Linux, macOS, and Windows.
  • Add explicit Bash shell examples for Linux users, especially for scripting or automation.
  • Mention that PowerShell is available cross-platform, but highlight Azure CLI as the primary tool for Linux/macOS users.
  • Consider including references to Linux/macOS documentation or guides for managing VM Scale Sets.
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: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_arm_template_example
Summary
The documentation covers both Windows and Linux virtual machines, and provides parity across API, Portal, CLI, and PowerShell examples. However, the ARM template section only demonstrates Windows VM creation, omitting an explicit Linux VM example. Additionally, the ARM template parameters and image references are Windows-centric, and Windows images are listed first. CLI examples do use Ubuntu images, but the ARM template is Windows-only.
Recommendations
  • Add an ARM template example for associating a Linux VM (e.g., Ubuntu) to a capacity reservation group, or extend the existing template to show both Windows and Linux image options.
  • In the ARM template section, clarify that the template can be adapted for Linux VMs and provide guidance or links for doing so.
  • Consider listing both Windows and Linux image options in the ARM template parameters, or provide a note about how to change the image for Linux VMs.
  • When listing image references or parameters, alternate or balance Windows and Linux examples to avoid 'windows_first' bias.
GitHub Create Pull Request
Virtual Machines Restrict managed disks from being imported or exported ...tual-machines/disks-restrict-import-export-overview.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation references both Azure CLI and Azure PowerShell for configuring the NetworkAccessPolicy, but the custom RBAC role creation link points only to a PowerShell-based guide, and PowerShell is mentioned before CLI in the NetworkAccessPolicy section. There is no explicit Linux example for custom role creation, and PowerShell is a Windows-centric tool, creating friction for Linux/macOS users.
Recommendations
  • Add links or instructions for creating custom RBAC roles using Azure CLI or Azure Portal, not just PowerShell.
  • Present Azure CLI and PowerShell examples side-by-side, or mention CLI first to improve parity.
  • Clarify that Azure CLI is cross-platform and provide explicit Linux/macOS guidance where relevant.
GitHub Create Pull Request
Virtual Machines Azure VM Extensions and Features for Linux ...articles/virtual-machines/extensions/features-linux.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell examples throughout, but PowerShell is featured equally or slightly more prominently than Azure CLI. In several sections, PowerShell examples are given immediately after CLI, and the PowerShell commands are Windows-centric (even though PowerShell Core is cross-platform, most Linux administrators use Bash/CLI). The documentation does not provide Bash-only or Linux-native command examples (other than waagent version check), and references to Azure PowerShell are frequent. While the page is focused on Linux VM extensions, the use of PowerShell and Windows-oriented tooling is notable.
Recommendations
  • Prioritize Azure CLI examples and Bash scripts for Linux-focused documentation, as CLI is the primary tool for Linux users.
  • Consider providing Bash-native examples for common operations (e.g., using curl/wget for script download, jq for JSON parsing).
  • Move PowerShell examples to a secondary position or into expandable sections, making CLI the default.
  • Clarify that Azure PowerShell can be used cross-platform, but highlight CLI as the recommended method for Linux users.
  • Add troubleshooting and operational examples using Linux-native tools (e.g., systemctl, journalctl, grep) where relevant.
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: 4 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation, while focused on Ubuntu Linux VHD creation for Azure, frequently references Windows tools (Hyper-V, PowerShell Convert-VHD) as primary methods for VHD creation and conversion. Windows/Hyper-V steps are described first and in detail, with no equivalent Linux-native tooling or workflow provided for critical steps like VHD creation/conversion. Linux users are left to infer or seek external guidance for these tasks, creating friction and potential confusion.
Recommendations
  • Add explicit instructions and examples for creating and converting VHDs on Linux (e.g., using qemu-img, VBoxManage, or other Linux-native tools).
  • Mention Linux-native virtualization solutions (such as KVM, VirtualBox, or QEMU) alongside Hyper-V, and provide links to relevant guides.
  • Provide PowerShell Convert-VHD alternatives for Linux (e.g., qemu-img convert) and clarify disk alignment requirements in Linux context.
  • Ensure that critical steps (such as disk conversion and VM shutdown) are described for both Windows and Linux environments.
  • Reorganize sections so that Linux-native approaches are presented first or equally with Windows methods.
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 are several signs of Windows bias. PowerShell examples and references to Windows tools (e.g., PowerShell cmdlets, Windows-specific notes) are prominent and often precede or outnumber Linux/CLI examples. REST and ARM template examples use Windows-centric scripts (e.g., Write-Host, .ps1 files) without Linux shell script equivalents. Some explanations and notes reference Windows behaviors or tools before Linux, and some features (like SAS token generation) are described only with PowerShell commands. There are missing Linux shell script examples in several sections, especially in REST and ARM template usage.
Recommendations
  • Provide Linux shell script examples alongside PowerShell/.ps1 examples in REST and ARM template sections.
  • Ensure CLI and bash examples are given equal prominence and are not secondary to PowerShell.
  • Clarify when a feature or example is Windows-only, and provide Linux alternatives where possible.
  • Add instructions for generating SAS tokens and managing blobs using Azure CLI or bash, not just PowerShell.
  • Review notes and explanations to ensure Linux behaviors are described first or equally.
GitHub Create Pull Request
Virtual Machines Upload a VHD to Azure or copy a disk across regions - Azure CLI ...machines/linux/disks-upload-vhd-to-managed-disk-cli.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides a Windows-style AzCopy example ('AzCopy.exe copy "c:\somewhere\mydisk.vhd" "sas-URI" --blob-type PageBlob') but does not show a Linux/macOS equivalent. The AzCopy command is presented in Windows syntax and path format, and the explicit example uses a Windows path. There is no Linux/macOS AzCopy example (e.g., using './azcopy' or '/home/user/mydisk.vhd'). The rest of the CLI commands are cross-platform, but the AzCopy section is notably Windows-centric.
Recommendations
  • Add a Linux/macOS AzCopy example (e.g., './azcopy copy "/home/user/mydisk.vhd" "sas-URI" --blob-type PageBlob') alongside the Windows example.
  • Clarify that AzCopy is cross-platform and provide download/install instructions for Linux/macOS.
  • Mention that file paths and command syntax differ between Windows and Linux/macOS.
  • Consider showing both Windows and Linux/macOS examples side-by-side for AzCopy usage.
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
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 coverage for Azure Image Builder, but there are several areas where Windows tools and examples are presented first or more prominently. PowerShell is frequently used for checksum generation and resource management, sometimes before Linux equivalents are mentioned. Windows-specific customizers (PowerShell, WindowsRestart, WindowsUpdate) are described in detail, while Linux equivalents are less emphasized or explicitly noted as unavailable. Some example commands and troubleshooting steps use PowerShell as the primary tool, with Linux alternatives provided but not always equally detailed.
Recommendations
  • Ensure Linux/macOS commands (e.g., sha256sum, Azure CLI) are presented alongside or before Windows/PowerShell equivalents, especially in sections about checksum generation and resource management.
  • Where PowerShell is used for examples (e.g., resource actions, validation), provide equivalent Bash/Azure CLI examples for Linux/macOS users.
  • Expand explanations and examples for Linux-specific customizers and validators, matching the detail given to Windows customizers.
  • Avoid language such as 'there is no Linux restart customizer' without offering Linux workarounds (e.g., using Shell customizer to run 'sudo reboot').
  • In troubleshooting and operational sections, ensure Linux/macOS commands are as prominent as Windows commands.
  • Consider alternating the order of Windows and Linux examples, or grouping them by OS for clarity.
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
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page demonstrates mild Windows bias. It references Visual Studio and PowerShell as primary upgrade tools, both of which are Windows-centric. The 'Next steps' section lists Visual Studio (Windows-only) and PowerShell (Windows-first) tutorials for application upgrades, without mentioning Linux/macOS alternatives or CLI-based approaches. The serialization discussion is focused on C# and .NET, but this is appropriate for Service Fabric workloads and not inherently Windows-biased.
Recommendations
  • Add guidance or links for upgrading Service Fabric applications using cross-platform tools such as Azure CLI or REST APIs.
  • Include examples or tutorials for Linux/macOS users, highlighting how to perform upgrades without Visual Studio or PowerShell.
  • Clarify which steps are Windows-only and provide parity for Linux/macOS where possible.
  • Mention any limitations or differences for Linux/macOS users in the upgrade process.
GitHub Create Pull Request
Service Fabric Reliable Collection object serialization ...c-reliable-services-reliable-collections-serialization.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation provides code examples exclusively in C#, which is cross-platform, but references to upgrade tutorials prioritize Visual Studio (a Windows-centric tool) before PowerShell. There are no explicit Linux/macOS examples or mentions of Linux-specific tools, but the content is generally applicable to all platforms where Service Fabric and .NET Core/.NET 5+ are supported.
Recommendations
  • Add explicit notes clarifying that the serialization APIs and patterns work on both Windows and Linux Service Fabric clusters.
  • Provide links or references to Linux/macOS-compatible tools for application upgrades (e.g., Azure CLI or bash scripts), if available.
  • Balance the order of 'Next steps' links by mentioning cross-platform options (such as Azure CLI) before or alongside Windows-specific tools like Visual Studio and PowerShell.
  • Include a brief section or note on any platform-specific considerations for serialization if they exist.
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 comprehensive Linux-specific guidance, commands, and configuration examples. However, the introductory section discusses Windows Server 2016 time sync improvements and references Windows documentation before Linux-specific information, which may create a perception of Windows-first bias. All technical guidance, tools, and examples are Linux-centric, with only a minor PowerShell snippet for base64 encoding cloud-init (which is not critical and is contextually relevant for Azure users). There are no missing Linux examples, nor are Windows tools or patterns used for Linux configuration.
Recommendations
  • Move or minimize Windows Server 2016 discussion in the introduction, focusing first on Linux-specific time sync mechanisms.
  • Add a brief explanation that Windows infrastructure is mentioned only for context, and all configuration guidance is Linux-focused.
  • Provide a Linux shell command alternative for base64 encoding cloud-init (e.g., `base64 cloud-config.txt`) alongside the PowerShell example.
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
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for checking vCPU quotas. While the CLI example is platform-neutral and suitable for Linux/macOS, the PowerShell example is Windows-specific. The structure presents CLI first, but the PowerShell section is equally prominent and detailed, potentially favoring Windows users. There are no Linux-specific tools or shell examples (e.g., Bash), but the CLI coverage is sufficient for Linux parity.
Recommendations
  • Clarify that Azure CLI works on Linux, macOS, and Windows, and is recommended for cross-platform usage.
  • Explicitly mention that PowerShell is primarily for Windows users, though PowerShell Core is available cross-platform.
  • Add a brief Bash shell example for invoking Azure CLI, or note that Azure CLI commands can be run in any shell.
  • Consider adding a note for Linux/macOS users about installing Azure CLI if not already present.
GitHub Create Pull Request
Service Fabric Change Azure Service Fabric cluster settings ...rvice-fabric/service-fabric-cluster-fabric-settings.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 provides a comprehensive reference for Service Fabric cluster settings, but exhibits mild Windows bias. Windows terminology (e.g., certificate store names like 'MY', 'LocalMachine', NTLM authentication, Windows Defender Firewall) is used throughout, and Windows-specific defaults are often mentioned before Linux equivalents. Some settings reference Windows-only behaviors or tools, and links to standalone cluster configuration upgrades point to Windows Server documentation without Linux parity. Linux-specific settings are present (e.g., 'LinuxExternalExecutablePath', 'EnforceLinuxMinTlsVersion'), but Linux guidance is less prominent and sometimes missing.
Recommendations
  • Add explicit Linux equivalents for certificate store names and authentication mechanisms, clarifying differences in guidance tables.
  • Provide links and examples for Linux standalone cluster configuration upgrades, not just Windows Server.
  • Where Windows tools or terminology are used (e.g., NTLM, Windows Defender Firewall), add notes or alternatives for Linux users.
  • Ensure Linux-specific settings are documented with equal detail and visibility as Windows settings.
  • Consider reordering sections or tables to avoid always listing Windows defaults first.
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 for deploying the extension before Azure CLI examples. PowerShell is primarily a Windows-centric tool, and its inclusion and placement before Azure CLI may create friction for Linux users. However, Linux-specific instructions, examples, and troubleshooting are present throughout, and Azure CLI (cross-platform) is well represented.
Recommendations
  • Move Azure CLI examples before PowerShell examples, as CLI is more commonly used on Linux/macOS.
  • Clarify that PowerShell is optional and primarily for Windows users, while Azure CLI is recommended for Linux/macOS.
  • Add Bash shell script examples for common tasks (e.g., checking extension status, troubleshooting).
  • Ensure all screenshots and instructions are Linux-specific (which is already mostly the case).
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, but there is a slight bias in the ordering and emphasis: Windows container runtimes and tools (Mirantis Container Runtime, DockerEE) are listed in detail, while Linux only mentions Docker. Windows scenarios (IIS lift and shift) and links to Windows container tutorials are presented before or alongside Linux equivalents, sometimes with more detail. However, Linux support and examples are present and referenced throughout.
Recommendations
  • Expand the Linux container runtime section to mention alternative runtimes if applicable (e.g., containerd, Podman), not just Docker.
  • Ensure Linux examples and tutorials are given equal prominence and detail as Windows examples.
  • When listing container runtimes, present Linux and Windows options in parallel rather than Windows-first.
  • Add more Linux-specific scenarios or highlight cross-platform scenarios equally.
  • Review the ordering of links and sections to avoid Windows-first presentation.
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 Docker Compose deployment. However, PowerShell examples are presented first and in greater detail, which may suggest a Windows-first bias. PowerShell is primarily a Windows tool (though available cross-platform, it's most common on Windows), and its prominence may create friction for Linux/macOS users. The CLI (sfctl) examples are provided and are cross-platform, mitigating the bias somewhat.
Recommendations
  • Present the cross-platform Service Fabric CLI (sfctl) examples before the PowerShell examples to avoid a Windows-first impression.
  • Explicitly mention that sfctl is supported on Linux/macOS and is the recommended tool for non-Windows users.
  • Clarify that PowerShell Core is available cross-platform if PowerShell examples are retained, or provide Bash equivalents where possible.
  • Add a short section or note for Linux/macOS users, confirming that all deployment steps are supported via sfctl.
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 acknowledges both Windows and Linux support for Azure Service Fabric, and provides references to Linux-specific development resources. However, Windows development is mentioned first, and the quickstart link points to a .NET/Windows-focused guide, which may create a perception of Windows preference. No critical Linux examples or tools are missing, but Windows is presented before Linux in several sections.
Recommendations
  • Alternate the order of Windows and Linux mentions to avoid Windows-first bias.
  • Provide quickstart links for both Windows (.NET) and Linux (Java/.NET Core) side by side.
  • Explicitly highlight parity in tooling and development experience for Linux users.
  • Ensure that Linux-specific quickstart and development guides are as prominent as Windows ones.
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 subtle signs of Windows bias. Windows-specific terminology (e.g., 'auto-start Windows service', 'EXE/DLL files', 'Windows Server containers') is mentioned first or exclusively in several sections, and Windows tools/processes (such as FabricHost.exe) are referenced without clear Linux equivalents or explanations. However, Linux support is acknowledged in some places, and the page does mention Docker containers on Linux and guest executables running on both platforms.
Recommendations
  • Clarify when references to Windows-specific processes (e.g., FabricHost.exe, EXE/DLL files) are also applicable to Linux, or provide Linux equivalents (such as referencing .so files or Linux service management).
  • When describing node startup and service hosting, explicitly mention Linux service/process equivalents if they exist.
  • Ensure that container support is described equally for Windows and Linux, and avoid listing Windows containers first unless contextually appropriate.
  • Where possible, provide examples or terminology relevant to Linux (e.g., referencing Linux file types, service management, or process orchestration).
  • Review sections for implicit Windows-first ordering and adjust to be platform-neutral or alternate ordering.
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). However, PowerShell examples are always present and are shown alongside CLI, which is cross-platform, but PowerShell is primarily used by Windows users. The CLI examples use Ubuntu images, but the PowerShell examples are more verbose and detailed, potentially giving Windows users more guidance. The order of examples is Azure portal, Azure CLI, then Azure PowerShell, which is a minor 'windows_first' bias. No Windows-only tools or patterns are mentioned, and Linux parity is generally good.
Recommendations
  • Ensure that Azure CLI examples are as detailed as PowerShell examples, especially for networking and advanced options.
  • Add explicit notes that Azure CLI is fully supported on Linux/macOS and is the recommended cross-platform tool.
  • Consider providing Bash shell script examples for common Linux workflows, or clarify that Azure CLI covers all Linux/macOS needs.
  • If PowerShell is used, mention that PowerShell Core is available cross-platform, but most Linux users will prefer Azure CLI.
GitHub Create Pull Request
Virtual Machine Scale Sets Configure rolling upgrades on Virtual Machine Scale Sets ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-configure-rolling-upgrades.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring, monitoring, canceling, and restarting rolling upgrades on Virtual Machine Scale Sets. However, PowerShell examples are given equal prominence to CLI examples, and in some cases, PowerShell is presented immediately after CLI, which may subtly favor Windows users. There are no Linux-specific examples or explicit mentions of Linux tools or shell environments, but the Azure CLI is cross-platform and suitable for Linux/macOS users. The documentation does not use Windows-only tools or patterns, but could improve parity by clarifying CLI usage on Linux/macOS and avoiding implicit Windows-first ordering.
Recommendations
  • Explicitly state that Azure CLI commands are cross-platform and can be used on Linux, macOS, and Windows.
  • Consider mentioning Bash or shell environments for Linux/macOS users when showing CLI examples.
  • Add a note for PowerShell examples indicating they are primarily for Windows users, while CLI is recommended for Linux/macOS.
  • If possible, provide sample Bash scripts or highlight CLI usage in Linux/macOS terminals.
  • Ensure CLI examples are shown before PowerShell, or clarify that both are equally supported.
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. While most content is platform-neutral, there are minor instances of Windows bias: some links and references show Windows documentation or tools first, and in one case, the Azure PowerShell module is mentioned before Azure CLI. However, Linux parity is generally maintained, and critical tasks are not Windows-exclusive.
Recommendations
  • Ensure that links to platform-specific guides (e.g., disk expansion) always include both Windows and Linux versions, ideally with equal prominence.
  • When referencing Azure management tools, mention Azure CLI and PowerShell together, or list CLI first for cross-platform neutrality.
  • Avoid linking to Windows-specific documentation as the primary resource unless the feature is Windows-only; provide Linux/macOS equivalents where applicable.
  • Review and update any examples or links that default to Windows paths or tools to ensure Linux/macOS users are equally supported.
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 'Use Azure PowerShell' and update operations), PowerShell is presented before REST API or ARM template examples. There is minor 'windows_first' bias, as PowerShell is a Windows-centric tool and is featured alongside CLI, but Linux users are not excluded from completing the tasks. All critical operations are covered with cross-platform tools (Azure CLI, ARM templates, REST API), and explicit Linux/Windows ARM template links are provided.
Recommendations
  • Ensure Azure CLI examples are always presented before PowerShell, as CLI is cross-platform and more accessible to Linux/macOS users.
  • Clarify that Azure PowerShell is primarily for Windows users, and recommend Azure CLI for Linux/macOS users.
  • Add explicit notes or links for Linux/macOS users where PowerShell is mentioned, suggesting Azure CLI as the preferred method.
  • Consider including Bash shell script examples where appropriate, especially for automation scenarios.
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 to the CLI example. However, the CLI example (Linux/macOS-friendly) is shown first, and there are no Windows-only tools or patterns mentioned. The documentation avoids Windows-specific terminology and does not reference Windows tools exclusively. Both CLI and PowerShell are cross-platform, but PowerShell is more commonly used on Windows. No Linux-specific commands (e.g., Bash scripts) or explicit Linux/macOS parity notes are present.
Recommendations
  • Add explicit notes clarifying that Azure CLI commands work on Linux, macOS, and Windows.
  • Consider including Bash shell script examples or referencing Linux/macOS environments where appropriate.
  • Mention that PowerShell Core is available cross-platform, but Azure CLI is typically preferred on Linux/macOS.
  • Ensure parity in troubleshooting and monitoring examples for both CLI and PowerShell users.
GitHub Create Pull Request
Virtual Machines Secure Azure Managed Disk Downloads and Uploads ...icles/virtual-machines/disks-secure-upload-download.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both PowerShell and Azure CLI examples for key tasks, but PowerShell (a Windows-centric tool) is presented before Azure CLI in most sections. Portal instructions are also included, but the ordering and prominence of PowerShell may subtly favor Windows users. However, Linux parity is generally maintained, and CLI examples are present. The 'Next steps' section lists Linux and Windows guides separately, showing parity.
Recommendations
  • Present Azure CLI and PowerShell examples side-by-side, or alternate their ordering to avoid implicit prioritization.
  • Explicitly note that Azure CLI works cross-platform and is recommended for Linux/macOS users.
  • Where possible, add Bash or shell script examples for Linux users.
  • Clarify in each section which tools are cross-platform and which are Windows-specific.
  • Consider adding a short statement at the start indicating that all tasks can be completed on Linux/macOS using Azure CLI.
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
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation is focused on the Azure Key Vault VM Extension for Linux and provides comprehensive Linux-specific details. However, there is evidence of Windows bias in the deployment sections: PowerShell examples and instructions are presented first and in greater detail than Azure CLI, despite PowerShell being more associated with Windows environments. Additionally, troubleshooting instructions reference Azure PowerShell before Azure CLI, which may create friction for Linux users who typically use CLI tools.
Recommendations
  • Present Azure CLI examples and instructions before PowerShell, as CLI is more commonly used on Linux.
  • Ensure that all deployment and troubleshooting steps are equally detailed for Azure CLI and PowerShell.
  • Clarify that PowerShell can be used cross-platform, but highlight Azure CLI as the primary tool for Linux users.
  • Add explicit notes or sections for Linux-native shell usage where relevant.
GitHub Create Pull Request
Virtual Machines Create an image definition and image version ...s/blob/main/articles/virtual-machines/image-version.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both Linux and Windows guidance, but there is a slight bias in the PowerShell section, where Windows is used as the default in examples and Linux is only mentioned as an alternative. Additionally, in the PowerShell tab, the example is for Windows, while in the CLI tab, the example is for Linux. Both platforms are covered, but the PowerShell section leans Windows-first, and there is a slight emphasis on Windows in some explanations.
Recommendations
  • In the PowerShell section, provide a Linux example first or present both Linux and Windows examples side by side.
  • Clarify in each code example which OS it is targeting, and ensure parity by showing both Linux and Windows variants where applicable.
  • Consider adding a note at the start of the PowerShell section to explicitly state that the cmdlets work for both Linux and Windows images, and provide explicit Linux-focused PowerShell examples.
  • Review the order of presentation in sections where OS-specific guidance is given to ensure Linux is not always secondary.
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 detailed instructions for preparing and uploading a Red Hat Enterprise Linux VHD for Azure, covering multiple hypervisors (Hyper-V, KVM, VMware, Kickstart). However, the Hyper-V (Windows) workflow is presented first in each major section, and Windows-specific tools (Hyper-V Manager, convert-vhd cmdlet) are mentioned before their Linux equivalents. The Linux/KVM/VMware workflows are present and well-detailed, but Windows tools and patterns are prioritized in ordering and introductory notes.
Recommendations
  • Reorder sections so that Linux-native hypervisors (KVM, VMware) are presented before Hyper-V, or at least provide equal prominence.
  • In introductory notes, mention Linux conversion tools (e.g., qemu-img) alongside or before Windows tools (e.g., convert-vhd, Hyper-V Manager).
  • Where possible, clarify that all workflows are equally supported and highlight Linux-native approaches for users not on Windows.
  • Consider a summary table at the top listing all supported hypervisors and tools, with links to each section, to avoid implicit prioritization.
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 Linux and Windows VM images, but there are signs of Windows bias. PowerShell examples and references are given alongside Azure CLI, but PowerShell is often presented first or with more detail. Windows-specific tools (Sysprep) are mentioned before Linux equivalents (waagent), and links to Windows upload guides are listed before Linux ones. Some references to Windows-specific pages (e.g., Marketplace images) are more prominent. However, Linux parity is generally maintained, and Linux users can complete all tasks.
Recommendations
  • Ensure that Linux and Windows examples are presented with equal prominence, alternating their order where possible.
  • Provide Linux-specific CLI and tool references before or alongside Windows/PowerShell equivalents.
  • Where PowerShell is referenced, ensure Bash/CLI examples are equally detailed and easy to find.
  • Link to Linux upload guides before or alongside Windows guides.
  • Review FAQ answers and ensure Linux scenarios are explicitly addressed, not just Windows.
GitHub Create Pull Request