← Back to Dashboard
284
Pages Scanned
94
Pages Flagged
284
Changed Pages
33.1%
% Pages Flagged

Live Progress

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

Scan Information

Started At: 2026-02-18 00:00:06

Finished At: In Progress

Status: in_progress

Target Repo: Azure Compute

Current Phase: discovery

Files Queued: 284

Files Completed: 284

Problematic Pages

94 issues found
Service Fabric Azure Service Fabric reverse proxy ...articles/service-fabric/service-fabric-reverseproxy.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation explicitly states that the Service Fabric reverse proxy is not available for Linux clusters, and all examples and configuration guidance are Windows-centric. There are no Linux equivalents or workarounds provided, and the feature is unavailable on Linux, creating a significant platform disparity.
Recommendations
  • Clearly highlight at the top of the documentation that reverse proxy is Windows-only, to set expectations for Linux users.
  • Provide links or references to alternative approaches for service discovery and communication on Linux clusters, if available.
  • If possible, include a roadmap or status update regarding Linux support for reverse proxy, or suggest community-supported solutions.
  • Ensure Linux users are directed to relevant documentation for supported features on their platform.
GitHub Create Pull Request
Service Fabric Standalone Service Fabric clusters overview ...-fabric/service-fabric-standalone-clusters-overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
Although the introduction claims Service Fabric clusters can run on Windows Server and Linux, the documentation page only provides details and supported OS lists for Windows. No Linux-specific instructions, examples, or supported distributions are mentioned. Windows authentication and security patterns are described, but Linux equivalents are absent. Windows terminology and recommendations appear first and exclusively.
Recommendations
  • Clarify the current Linux support status for standalone clusters. If Linux is not supported, update the introduction to avoid misleading users.
  • If Linux support exists or is planned, add Linux-specific instructions, supported distributions, and security/authentication guidance.
  • Provide Linux examples alongside Windows examples for cluster creation, security, scaling, and upgrading.
  • Explicitly state any feature limitations or differences between Windows and Linux clusters.
GitHub Create Pull Request
Service Fabric RunToCompletion semantics and specifications ...blob/main/articles/service-fabric/run-to-completion.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page presents RunToCompletion semantics primarily in the context of Windows containers and Windows-specific tools. All code examples reference Windows container images and use Windows command syntax (cmd.exe). Querying deployment status is described using PowerShell and C# APIs, with no mention of Linux equivalents or cross-platform CLI tools. There are no examples or guidance for Linux containers or Linux-based workflows, despite Service Fabric supporting containers in general.
Recommendations
  • Add Linux container examples (e.g., using Ubuntu or Alpine images) alongside Windows container examples.
  • Provide equivalent Linux shell commands (bash/sh) for CodePackage entry points.
  • Mention and demonstrate querying deployment status using Azure CLI or Service Fabric CLI (sfctl), which are cross-platform.
  • Clarify any limitations or differences in RunToCompletion semantics for Linux containers, if applicable.
  • Reorganize examples to show both Windows and Linux scenarios, or explicitly state if RunToCompletion is Windows-only.
GitHub Create Pull Request
Service Fabric Advanced Application Upgrade Topics ...-fabric/service-fabric-application-upgrade-advanced.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page on advanced Service Fabric application upgrade topics consistently uses PowerShell cmdlets for examples and references, with no mention of Linux/macOS equivalents or cross-platform CLI tools. All command-line instructions are given in PowerShell, and there is no guidance for Linux users on how to perform these tasks using Service Fabric CLI (sfctl) or REST APIs. This creates friction for Linux/macOS users, who may not have access to PowerShell or may prefer native tools.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and supported on Linux/macOS.
  • Mention REST API options for relevant operations, with links to documentation.
  • Clarify which PowerShell cmdlets are Windows-only and provide guidance for Linux/macOS users.
  • In 'Next steps', include links to tutorials for Linux/macOS users, such as 'Upgrading your Application Using sfctl'.
  • Where possible, provide ARM template examples alongside PowerShell, and clarify their cross-platform applicability.
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 PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) and linking to a Windows Server-specific guide for scaling standalone clusters. There are no Linux-specific instructions, examples, or mentions of Linux tooling for cluster scaling, despite Service Fabric standalone clusters being theoretically deployable on Linux.
Recommendations
  • Add Linux-specific instructions for scaling standalone clusters, including relevant CLI commands and configuration steps.
  • Provide examples using Linux shell tools (e.g., Bash, sfctl) alongside PowerShell examples.
  • Clarify whether standalone cluster scaling is supported on Linux, and if not, state this explicitly to avoid confusion.
  • Link to Linux documentation or guides if available, or note limitations if Linux support is incomplete.
GitHub Create Pull Request
Service Fabric Restoring backup in Azure Service Fabric ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-backup-restore-service-trigger-restore.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page for restoring backups in Azure Service Fabric is heavily focused on PowerShell-based workflows, specifically using the Microsoft.ServiceFabric.Powershell.Http module and PowerShell scripting for REST API calls. All code examples and instructions are provided exclusively in PowerShell, with no mention of Linux/macOS equivalents (such as Bash, curl, or Azure CLI). The prerequisite section also assumes PowerShell usage and Windows tooling, and there is no guidance for Linux users on how to perform equivalent operations. This creates friction for Linux/macOS users, who may not have access to PowerShell or the required modules.
Recommendations
  • Add equivalent examples using Bash and curl for REST API calls, as Service Fabric REST APIs are platform-agnostic.
  • Document how to authenticate and make REST calls from Linux/macOS, including certificate handling.
  • Mention Azure CLI commands where possible for cross-platform parity.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is required for all scenarios, or if REST calls can be made directly from any OS.
  • Provide guidance for Linux/macOS users on connecting to Service Fabric clusters and restoring backups.
GitHub Create Pull Request
Service Fabric Service sensitivity ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-sensitivity.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides configuration examples using Application Manifest (XML/JSON), PowerShell, and C# APIs. PowerShell examples are prominent and shown before C# API examples, but there are no CLI or Bash examples for Linux/macOS users. The PowerShell API is Windows-centric, and no equivalent Linux-friendly command-line instructions (such as Azure CLI or REST API usage) are provided. This creates friction for Linux/macOS administrators managing Service Fabric clusters.
Recommendations
  • Add Azure CLI or REST API examples for configuring service sensitivity and maximum load, if supported.
  • Clarify whether PowerShell commands can be run cross-platform (PowerShell Core), or specify Windows-only limitations.
  • Provide guidance for Linux/macOS users on how to perform equivalent operations, or explicitly state if certain operations are Windows-only.
  • Consider including Bash shell script examples or references to SDKs/libraries usable on Linux/macOS.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager - Placement Policies ...ce-manager-advanced-placement-rules-placement-policies.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides code examples for configuring Service Fabric placement policies using C# and PowerShell. PowerShell is a Windows-centric tool, and no equivalent Linux/macOS CLI examples (such as Azure CLI or REST API) are provided. All operational examples for service creation and placement policy configuration use PowerShell, which may create friction for Linux/macOS users who do not have access to PowerShell or prefer cross-platform tools. Additionally, PowerShell examples are consistently shown alongside C# code, with no mention of Linux-native alternatives.
Recommendations
  • Add Azure CLI examples for service creation and placement policy configuration, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Document REST API usage for configuring placement policies, providing sample requests and responses.
  • Explicitly mention whether PowerShell is required, and provide guidance for Linux/macOS users on alternative tools.
  • Consider including Bash scripts or references to Service Fabric SDK tools available on Linux.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Events ...es/service-fabric/service-fabric-diagnostics-events.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page for Azure Service Fabric Events primarily references Windows-specific tools and patterns, such as ETW/Windows Event logs and the Windows Azure diagnostics agent, without mentioning Linux equivalents or providing Linux-specific guidance. The examples and instructions focus on Windows channels and tools, and do not address how Linux-based Service Fabric clusters can access or monitor events.
Recommendations
  • Add information about how Service Fabric events are logged and accessed on Linux clusters, including any differences in event channels or monitoring tools.
  • Provide examples or instructions for accessing events using Linux-compatible tools (e.g., syslog, journald, Azure Monitor integration for Linux).
  • Clarify whether the EventStore REST APIs and Service Fabric Client Library are fully cross-platform, and provide usage examples for Linux environments.
  • Explicitly state if certain features or event channels are Windows-only, and offer alternative approaches for Linux users where possible.
GitHub Create Pull Request
Service Fabric Replica soft delete for enhanced data protection in Service Fabric ...s/service-fabric/service-fabric-replica-soft-delete.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page for 'Replica soft delete for enhanced data protection in Service Fabric' demonstrates a notable Windows/PowerShell bias. All command-line/API usage examples reference PowerShell cmdlets (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica, Get-ServiceFabricReplica), with no mention of Linux CLI equivalents, REST APIs, or cross-platform SDK usage. The documentation assumes the use of Windows tooling and does not provide guidance for Linux or macOS users, despite Service Fabric supporting cross-platform clusters.
Recommendations
  • Include equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and supported on Linux/macOS.
  • Document REST API or FabricClient SDK usage for soft delete and restore operations, with code snippets in a cross-platform language (e.g., Python, C# .NET Core).
  • Explicitly state if certain features or APIs are only available via PowerShell or Windows, or clarify cross-platform support.
  • Add a section or callouts for Linux/macOS users, outlining the steps and tools they should use to achieve the same tasks.
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 page provides explicit PowerShell instructions for using the Fault Analysis Service, but does not mention or provide examples for Linux/macOS command-line tools or SDKs. The PowerShell section is prominent, and no equivalent Bash, CLI, or cross-platform scripting guidance is given. This creates friction for Linux/macOS users, though workarounds exist via the C# API or REST endpoints.
Recommendations
  • Add Azure CLI or Bash examples for inducing faults and running test scenarios, if supported.
  • Clarify whether the Fault Analysis Service APIs can be accessed from Linux/macOS environments, and provide guidance for those platforms.
  • Mention or link to any cross-platform SDKs or tools (e.g., .NET Core, REST API) usable from Linux/macOS.
  • If PowerShell is required, note whether PowerShell Core (cross-platform) is supported, and provide installation instructions for Linux/macOS.
GitHub Create Pull Request
Service Fabric Azure Service Fabric hosting model ...rticles/service-fabric/service-fabric-hosting-model.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page for the Azure Service Fabric hosting model provides conceptual information applicable to both Windows and Linux clusters. However, it exhibits Windows bias in several ways: PowerShell is the only CLI example shown for service creation, and all operational links reference PowerShell cmdlets. There are no Linux-specific CLI examples (e.g., Bash, Azure CLI), and PowerShell is presented before REST and .NET API options. This creates friction for Linux users, as Service Fabric supports Linux clusters but the documentation does not demonstrate parity in tooling or examples.
Recommendations
  • Add Azure CLI or Bash examples for service creation and management, especially for commands like New-ServiceFabricService.
  • Include references to Linux-compatible tools and workflows, such as sfctl (Service Fabric CLI) and REST API usage from Bash.
  • Clarify in the introduction that the concepts apply to both Windows and Linux clusters, and provide links to Linux-specific operational documentation.
  • Where PowerShell is referenced, add a note or section for Linux users explaining equivalent commands and tools.
GitHub Create Pull Request
Service Fabric Manage certificates in a Service Fabric cluster ...vice-fabric/cluster-security-certificate-management.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation provides a significant number of PowerShell-based examples for certificate management and provisioning, and references Windows-specific tools and behaviors (such as Key Vault VM extension for Windows, S-channel, and certificate linking). While the overall guidance is Azure-centric and much of the process is cross-platform, the hands-on and troubleshooting sections focus on Windows and PowerShell, with little to no mention of Linux equivalents or alternative scripting approaches. Windows-specific mechanisms (e.g., certificate store locations, S-channel, linking on renewal) are discussed in detail, while Linux/macOS scenarios are not addressed.
Recommendations
  • Add equivalent Linux/bash examples for certificate enrollment, provisioning, and management (e.g., using Azure CLI or REST API instead of PowerShell).
  • Clarify which steps are Windows-specific and provide guidance for Linux/macOS clusters where applicable.
  • Reference Key Vault VM extension for Linux and document any differences in behavior or configuration.
  • Include troubleshooting steps and FAQs relevant to Linux/macOS environments.
  • Where Windows-specific concepts (like S-channel or certificate linking) are discussed, explicitly state their applicability and provide alternatives or note limitations for Linux/macOS.
GitHub Create Pull Request
Service Fabric Custom Image .../articles/service-fabric/how-to-deploy-custom-image.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page primarily discusses deploying custom Windows images in Service Fabric Managed Clusters, with Windows terminology and PowerShell examples shown. While there are references to Linux custom image creation and Azure CLI for browsing Marketplace images, the main focus and examples are Windows-centric, and PowerShell is used for role assignment without a Linux CLI equivalent.
Recommendations
  • Provide explicit Linux-focused examples for deploying custom images, including ARM template snippets for Linux node types.
  • Add Azure CLI or Bash equivalents for role assignment commands alongside PowerShell.
  • Clarify which steps are applicable to both Windows and Linux node types, and highlight any differences.
  • Include links to Linux-specific documentation where relevant, such as custom image creation and deployment.
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, with explicit links to PowerShell cmdlets for cluster operations. While Azure CLI and ARM/Bicep are mentioned in a summary table, PowerShell is emphasized in the narrative and examples, and no Linux/macOS-specific command-line examples (such as Azure CLI usage) are provided. The ordering and focus on PowerShell may create friction for Linux/macOS users.
Recommendations
  • Add Azure CLI examples alongside PowerShell examples for key operations (e.g., deleting NodeTypes, restarting/reimaging scale sets).
  • In the 'Best practices' section, mention Azure CLI as an equally valid cross-platform option, not just in the summary table.
  • Provide sample commands for both Azure CLI and PowerShell where possible.
  • Clarify that PowerShell is available cross-platform, but highlight CLI as the default for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Service Fabric Explorer blocking operations ...ged-cluster-service-fabric-explorer-blocking-operation.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page provides management guidance for Service Fabric Explorer blocking operations, primarily referencing Az PowerShell cmdlets (e.g., Remove-AzResource, AzSF PowerShell cmdlets) for resource operations. While the Azure CLI (az resource) is mentioned once for deleting applications, most examples and instructions favor PowerShell, which is more commonly used on Windows. There is no explicit mention of Linux/macOS alternatives or parity for all operations.
Recommendations
  • Include Azure CLI equivalents for all PowerShell cmdlet examples, especially for provisioning and deleting resources.
  • Clarify that Az PowerShell cmdlets can be used cross-platform (on Linux/macOS via PowerShell Core), or provide links to relevant documentation.
  • Present examples for both PowerShell and Azure CLI side-by-side to ensure Linux/macOS users can follow along easily.
  • Explicitly mention that ARM templates and Azure CLI are fully supported on Linux/macOS.
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 contains evidence of Windows bias. It references Windows file paths (e.g., 'C:\Program Files\Microsoft SDKs\Service Fabric\schemas\ServiceFabricServiceModel.xsd') and recommends using Visual Studio for XML schema validation, which are Windows-centric tools. Additionally, the only mention of command-line tooling is the ServiceFabric PowerShell module, with no equivalent Linux CLI or cross-platform example provided. Windows terminology and tools are mentioned before any Linux alternatives (if any), and there are no explicit Linux/macOS examples or guidance.
Recommendations
  • Add instructions for validating manifest XML schema using cross-platform tools (e.g., VS Code, xmllint, or other editors) and provide Linux/macOS file path equivalents if applicable.
  • Include examples or references for using Service Fabric CLI (sfctl) or Azure CLI for service management, alongside PowerShell examples.
  • Mention cross-platform editors and tooling for authoring manifests, not just Visual Studio.
  • Clarify any platform-specific requirements for Service Fabric manifest authoring and deployment, and provide parity guidance for Linux clusters.
GitHub Create Pull Request
Service Fabric X.509 Certificate-based Authentication in a Service Fabric Cluster ...ticles/service-fabric/cluster-security-certificates.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation provides a thorough conceptual overview of X.509 certificate-based authentication in Service Fabric clusters, but exhibits Windows bias in several areas. Windows-specific terminology and tools (e.g., certificate store paths like LocalMachine\My, references to Win32 CryptoAPI, Windows event logs, and error codes) are mentioned first or exclusively. Troubleshooting sections focus on Windows logs and tools, with only brief or parenthetical references to Linux equivalents. Linux certificate storage paths are mentioned, but Windows patterns dominate the narrative and examples.
Recommendations
  • Provide Linux-specific examples and troubleshooting steps alongside Windows instructions, including log locations, certificate store paths, and relevant commands.
  • Explicitly document Linux/macOS certificate store equivalents and how Service Fabric interacts with them.
  • Include Linux/macOS error codes and remediation steps where applicable.
  • Balance Windows and Linux terminology in examples and explanations.
  • Reference cross-platform tools (e.g., OpenSSL) for certificate management and validation.
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 Azure Portal, ARM templates, and PowerShell. PowerShell is the only CLI example provided, with no mention of Azure CLI or Bash scripting, which are cross-platform and preferred by Linux/macOS users. Additionally, PowerShell examples are presented alongside Portal and ARM template methods, but never alternatives for Linux users. There is no explicit mention that PowerShell Core (pwsh) is supported, nor are Linux-specific instructions or tools referenced.
Recommendations
  • Add Azure CLI examples for all tasks currently demonstrated with PowerShell, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Clarify whether PowerShell Core (pwsh) is supported for Linux/macOS, or recommend Azure CLI for those platforms.
  • Explicitly mention that all operations can be performed from Linux/macOS using Azure CLI or ARM templates.
  • Consider showing Azure CLI examples before or alongside PowerShell to avoid Windows-first bias.
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 the Infrastructure Service, and references Service Fabric Explorer (a Windows-centric tool) without mentioning Linux/macOS alternatives. No Linux-specific commands or cross-platform CLI options are given, and Windows tooling is presented as the default.
Recommendations
  • Add equivalent Linux/macOS command-line examples using Azure CLI or Service Fabric CLI (sfctl), if available.
  • Clarify whether the PowerShell command is required, or if cross-platform alternatives exist.
  • Mention if Service Fabric Explorer is accessible from non-Windows platforms, or provide alternative tools for Linux/macOS users.
  • Explicitly state platform requirements for any commands or tools referenced.
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 ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page for Initializer CodePackages in Service Fabric presents only Windows container examples, exclusively references Windows container images (mcr.microsoft.com/windows/nanoserver:1809), and uses Windows-specific paths and commands (e.g., C:\WorkspaceOnHost, cmd, echo, type, ping). There is no mention of Linux containers, Linux paths, or Linux command equivalents, and the example is explicitly described as a Windows container scenario.
Recommendations
  • Add a parallel example using Linux containers (e.g., mcr.microsoft.com/linux/base image), with Linux file paths and shell commands (e.g., /workspace/log.txt, bash, echo, cat, ping).
  • Clarify whether Initializer CodePackages are supported for Linux container workloads in Service Fabric, and if so, provide guidance and examples.
  • If Initializer CodePackages are Windows-only, explicitly state this limitation at the top of the article to set expectations for Linux/macOS users.
  • Include links or references to Linux container documentation if available.
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 both Windows and Linux clusters, but there are several areas where Windows tools and patterns are mentioned first or exclusively. Windows-specific tools (e.g., Event Log/Event Viewer, Diagnostics Agent) are referenced before Linux equivalents, and some examples/tutorials focus on .NET/Windows. Linux-specific guidance is present but often secondary, and Linux configuration details are sometimes referenced via links rather than described inline. Some features (like EventStore APIs) are Windows-only, but this is clearly stated. Overall, Linux users can complete the tasks, but may experience friction due to Windows-centric ordering and tool emphasis.
Recommendations
  • Ensure Linux examples and tools are given equal prominence and described inline, not just linked.
  • Where Windows tools (e.g., Event Viewer, Diagnostics Agent) are mentioned, immediately follow with Linux equivalents (e.g., Syslog, Linux platform diagnostics) and provide comparable detail.
  • Add Linux-focused tutorials and examples alongside .NET/Windows ones, especially for application monitoring and logging.
  • Clarify when features are Windows-only, and provide alternative approaches for Linux clusters.
  • Review ordering so Linux and Windows guidance is presented in parallel, not Windows-first.
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 context but exhibits some Windows bias. Windows-specific features (e.g., Active Directory, gMSA, BitLocker) are mentioned with more detail and examples, while Linux equivalents are either briefly referenced or omitted. Some sections (e.g., disk encryption, running services under accounts) provide Windows instructions or links first, with Linux options marked as TODO or not explained. PowerShell is referenced for disk encryption, but Linux CLI or disk encryption methods are not provided.
Recommendations
  • Add explicit Linux examples for disk encryption (e.g., using Azure CLI and dm-crypt/LUKS).
  • Provide parity in instructions for running services under Linux user accounts, including relevant manifest configuration and security policies.
  • Ensure that Linux container certificate access is described with equal detail as Windows.
  • Where Windows tools (e.g., BitLocker, PowerShell) are mentioned, add corresponding Linux tools and commands.
  • Remove or resolve TODOs regarding Linux disk encryption and provide links to Linux documentation.
GitHub Create Pull Request
Service Fabric Application upgrade: data serialization ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-application-upgrade-data-serialization.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page primarily references Windows-centric tools and patterns, such as Visual Studio and PowerShell, in its 'Next steps' section. There are no Linux/macOS equivalents or examples provided for application upgrades, and the recommended serialization approach (Data Contract serializer) is tied to .NET Framework/WCF, which is historically Windows-focused. The page assumes C# usage and does not mention cross-platform alternatives or workflows for Linux/macOS users.
Recommendations
  • Add examples or links for upgrading Service Fabric applications using cross-platform tools (e.g., Azure CLI, REST API, or .NET Core CLI).
  • Include guidance for Linux/macOS users, such as using VS Code or other IDEs instead of Visual Studio.
  • Clarify whether the Data Contract serializer recommendation applies to .NET Core/.NET 5+ workloads, which are cross-platform, or only .NET Framework (Windows-only).
  • Provide parity in upgrade instructions for Linux/macOS environments, including PowerShell Core (pwsh) or Bash examples.
  • Explicitly state any Windows-only limitations if applicable, so Linux/macOS users are aware.
GitHub Create Pull Request
Service Fabric Service Fabric application upgrade ...s/service-fabric/service-fabric-application-upgrade.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation for Service Fabric application upgrade demonstrates a notable Windows bias. PowerShell is used exclusively in code examples, and only Windows-specific tools (e.g., PowerShell cmdlets like Get-ServiceFabricApplication and Start-ServiceFabricApplicationUpgrade) are mentioned. There are no equivalent examples or guidance for Linux/macOS users (e.g., using sfctl or REST APIs). Additionally, the documentation references Windows-specific components such as http.sys and error messages from the Windows HTTP Server API, without clarifying platform differences or providing Linux alternatives.
Recommendations
  • Add equivalent Linux/macOS examples using sfctl (Service Fabric CLI) or REST API calls alongside PowerShell examples.
  • Clearly state when a feature or limitation is Windows-specific (e.g., http.sys certificate handling).
  • In sections referencing PowerShell, provide a note or link to Linux/macOS instructions.
  • Reorder or parallelize examples so that Linux/macOS and Windows users are equally supported.
  • Include a table or section summarizing tool equivalence (PowerShell vs sfctl vs REST API) for common upgrade operations.
GitHub Create Pull Request
Service Fabric On-demand backup in Azure Service Fabric ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-backup-restore-service-ondemand-backup.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation is heavily focused on PowerShell and the Microsoft.ServiceFabric.Powershell.Http module for all command-line examples. There are no examples using cross-platform tools (such as Azure CLI, curl, or bash scripting), nor is there any mention of Linux/macOS equivalents for connecting to clusters or triggering backups. All REST API examples are shown via PowerShell, and there is no guidance for Linux users on how to perform these tasks.
Recommendations
  • Add equivalent examples using cross-platform tools such as curl or HTTPie for REST API calls.
  • Provide instructions for connecting to Service Fabric clusters from Linux/macOS environments, including certificate handling.
  • Mention and demonstrate the use of Azure CLI (if supported) for relevant operations.
  • Clearly state if certain features or modules are only available on Windows, and provide alternatives or workarounds for Linux/macOS users.
  • Include bash or shell script examples alongside PowerShell 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 in Service Fabric, but does not include equivalent Linux/bash/CLI examples. PowerShell is a Windows-centric tool, and its exclusive use creates friction for Linux/macOS users. Additionally, PowerShell examples are presented before C# code samples, reinforcing Windows-first bias. There is no mention of Azure CLI, REST API, or bash alternatives for Linux users.
Recommendations
  • Add Azure CLI examples for configuring and updating move cost, if supported.
  • Include bash or shell script equivalents for PowerShell commands.
  • Mention REST API options for cross-platform usage.
  • Present Windows and Linux/macOS examples side-by-side or alternate their order.
  • Clarify if certain operations are only possible via PowerShell, and provide guidance for Linux users if so.
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 frequently references PowerShell cmdlets and Windows-specific tooling (e.g., Remove-ServiceFabricApplicationPackage, Register-ServiceFabricApplicationType) alongside .NET APIs and REST operations. PowerShell examples and cmdlets are consistently mentioned before or alongside REST and .NET methods, but Linux-native CLI equivalents (such as sfctl or Azure CLI) are not directly referenced in the main lifecycle steps. The only explicit cross-platform mention is an include link to 'service-fabric-sfctl.md', but no concrete sfctl or Azure CLI commands are shown in the main sections. This creates friction for Linux/macOS users, who must infer or search for their own equivalents.
Recommendations
  • Add explicit examples and references for sfctl and Azure CLI commands in each lifecycle phase (deploy, upgrade, remove, etc.), not just as a sidebar link.
  • Where PowerShell cmdlets are listed, also list the equivalent sfctl or Azure CLI command immediately alongside.
  • Clarify which tools are cross-platform and which are Windows-only, especially for operators and administrators.
  • Consider providing sample command sequences for Linux/macOS users in critical sections.
  • Review and update the 'Preserving disk space' and 'Cleaning up files' sections to include sfctl/Azure CLI equivalents where possible.
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 gives prominence to Windows-centric tools (PowerShell and Visual Studio) by listing them first and providing detailed parameter tables for these tools before mentioning cross-platform alternatives like SFCTL. The PowerShell and Visual Studio sections are more extensive and appear before SFCTL, which is the primary CLI for Linux/macOS users. Examples and parameter descriptions are often PowerShell-focused, and Linux-specific guidance is less detailed.
Recommendations
  • Reorder the tools section to list SFCTL (Service Fabric CLI) alongside PowerShell and Visual Studio, or even before them, to emphasize cross-platform parity.
  • Expand the SFCTL section to include more detailed parameter tables and usage examples, matching the depth provided for PowerShell and Visual Studio.
  • Add explicit Linux/macOS examples and clarify which tools are recommended for each platform.
  • Where PowerShell-specific syntax is shown (e.g., hashtables), provide equivalent SFCTL JSON examples.
  • Ensure that all parameters described for PowerShell/Visual Studio are also mapped to SFCTL, noting any differences or limitations.
GitHub Create Pull Request
Service Fabric Understanding periodic backup configuration ...-fabric-backuprestoreservice-configure-periodic-backup.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page primarily describes Service Fabric's periodic backup configuration in a platform-neutral manner, but the only example for on-premises backup storage is a Windows-style file share path (\\StorageServer\BackupStore) and references Integrated Windows Authentication. There are no examples or guidance for Linux-based file shares (such as NFS or SMB mounts on Linux), nor is there mention of Linux authentication patterns. This creates friction for Linux users of standalone Service Fabric clusters who wish to use on-premises backup storage.
Recommendations
  • Add examples and guidance for configuring file share backup storage using Linux-based file shares (e.g., NFS or SMB mounts) and authentication methods suitable for Linux environments.
  • Clarify whether Linux-based Service Fabric clusters can use file share backup storage, and if so, provide sample paths and credential usage for Linux.
  • If file share backup storage is Windows-only, explicitly state this limitation to avoid confusion for Linux users.
  • Consider including both Windows and Linux file share path formats and authentication options in the documentation.
GitHub Create Pull Request
Service Fabric Azure Service Fabric infrastructure as Code Best Practices ...tps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-best-practices-infrastructure-as-code.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Resource Manager templates, but PowerShell is featured prominently and exclusively for cluster upgrade operations. Windows-specific registry keys and template properties are discussed for disabling Windows Update, with no equivalent Linux guidance. Upgrade instructions rely on PowerShell, omitting Linux shell or cross-platform alternatives. Windows configuration details are presented before Linux, and some sections lack Linux parity.
Recommendations
  • Add Linux shell (bash) examples for cluster upgrade operations, especially where PowerShell is currently the only option.
  • Include guidance for disabling automatic updates on Linux VMs (e.g., using cloud-init or OS-specific package managers).
  • Provide parity in upgrade instructions for Linux clusters, including references to .deb package handling and relevant commands.
  • Where possible, present cross-platform tools (Azure CLI, REST API) before platform-specific tools like PowerShell.
  • Clarify when instructions are Windows-only and provide links or notes to Linux equivalents.
GitHub Create Pull Request
Service Fabric Capacity planning and scaling for Azure Service Fabric ...bric/service-fabric-best-practices-capacity-scaling.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides numerous PowerShell-based manual scaling instructions and references Windows-centric tooling (e.g., PowerShell cmdlets like Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState) without offering equivalent Linux/bash/CLI examples. Windows/PowerShell instructions are presented first and exclusively in critical workflow sections, creating friction for Linux users. While Service Fabric supports Linux clusters, the guidance for scaling and node management is heavily Windows-biased.
Recommendations
  • Provide equivalent Azure CLI or bash examples for scaling operations, including node disablement/removal and cluster management.
  • Clearly indicate which PowerShell commands are available on Linux (via PowerShell Core) or provide alternative commands/scripts for Linux environments.
  • Add Linux-specific guidance for manual scaling, including references to Service Fabric CLI (sfctl) or REST API usage.
  • Ensure that both Windows and Linux cluster creation and management workflows are equally documented and accessible.
GitHub Create Pull Request
Service Fabric Azure Service Fabric networking best practices ...ice-fabric/service-fabric-best-practices-networking.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation provides several Windows/PowerShell-centric examples and references, such as mentioning PowerShell APIs and Azure DevOps classic PowerShell tasks, and links to Windows-specific ARM templates. Windows terminology and tools are often referenced before Linux equivalents, and some examples (like network port usage and tooling) are Windows-focused. Linux is mentioned, but Linux-specific examples and guidance are less detailed or appear after Windows content.
Recommendations
  • Provide Linux CLI examples alongside PowerShell examples, especially for cluster management and networking tasks.
  • Ensure Linux-specific ARM templates and sample links are included and referenced equally.
  • Clarify when port ranges or tooling differ for Linux clusters (e.g., ephemeral ports, client APIs).
  • Add more Linux-focused guidance for Azure DevOps and application networking scenarios.
  • Balance the order of Windows and Linux references in sections and tables.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager - Application Groups ...ice-fabric-cluster-resource-manager-application-groups.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page provides only PowerShell and C# examples for managing Service Fabric Application Groups. PowerShell is a Windows-centric tool, and no Linux/macOS CLI equivalents (such as Azure CLI, Bash, or REST API examples) are provided. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer cross-platform tools.
Recommendations
  • Add Azure CLI examples for all operations shown (application creation, updating, querying load, removing capacity).
  • Include REST API sample calls for relevant actions, as these are platform-agnostic.
  • Mention if PowerShell cmdlets are available cross-platform (PowerShell Core), or clarify Windows-only limitations.
  • Consider Bash scripting examples if relevant.
  • Explicitly state any limitations or differences for Linux clusters, if applicable.
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 encrypting secrets, but Windows examples (PowerShell) are presented first and in greater detail. Windows-specific tools and features like Windows Defender and Azure Desired State Configuration (DSC) are discussed without Linux equivalents or alternatives. Some sections, such as Windows security baselines and Windows Defender, are inherently Windows-focused, but the overall structure tends to prioritize Windows tools and patterns before Linux ones.
Recommendations
  • Present Linux and Windows examples side-by-side or alternate their order to avoid Windows-first bias.
  • Where Windows-specific tools (e.g., Windows Defender, DSC) are mentioned, provide Linux alternatives or explicitly state their absence and recommend best practices for Linux clusters.
  • Expand Linux-specific guidance where possible, such as referencing common Linux security baselines or antimalware solutions.
  • Ensure parity in detail and clarity between Windows and Linux instructions, especially for certificate and secret management.
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: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides some Windows-centric details, such as using Windows-style file paths (e.g., 'D:\\SvcFab') in JSON configuration examples and referencing RDP port changes and admin username/password updates, which are Windows-specific tasks. There is a lack of explicit Linux/macOS examples or guidance, especially for connecting to nodes or configuring Service Fabric on Linux. The extension configuration does mention 'ServiceFabricLinuxNode', but practical Linux usage is not demonstrated.
Recommendations
  • Add explicit Linux/macOS examples for connecting to cluster nodes (e.g., SSH instructions alongside RDP).
  • Include Linux-style file paths (e.g., '/var/svcfab') in configuration examples or clarify that the path should match the OS.
  • Provide guidance or links for updating Linux admin credentials and port ranges, not just Windows/RDP.
  • Ensure parity in 'Next steps' by referencing Linux-relevant scripts or documentation where available.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Auto Scaling Services and Containers ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-autoscaling.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides detailed examples for configuring auto scaling in Azure Service Fabric using Application Manifest, C# APIs, and PowerShell. All CLI 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-native tools or commands. While Service Fabric supports Linux containers, the documentation does not show how Linux users can perform these tasks, creating friction for non-Windows users.
Recommendations
  • Add equivalent bash/CLI examples for Linux users alongside PowerShell examples.
  • Clarify which steps or commands are cross-platform and which are Windows-only.
  • Mention and link to Linux-specific tooling or documentation where relevant.
  • Explicitly state PowerShell requirements and provide alternatives for Linux environments.
GitHub Create Pull Request
Service Fabric Describe a cluster by using Cluster Resource Manager ...ce-fabric-cluster-resource-manager-cluster-description.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides configuration examples for both Windows (ClusterManifest.xml) and cross-platform/standalone (ClusterConfig.json) deployments. However, code samples for service creation and updates are given in C# and PowerShell only, with PowerShell shown as the only CLI example. The XML configuration is labeled as <WindowsServer>, and PowerShell is a Windows-centric tool, which may create friction for Linux/macOS users who typically use Bash or other CLI tools. There are no explicit Linux-specific examples or references to Linux-native tools or shell commands.
Recommendations
  • Add CLI examples using Azure CLI or Bash scripts for service creation and updates, especially for standalone and Linux clusters.
  • Clarify whether ClusterManifest.xml applies only to Windows or if there is an equivalent for Linux clusters.
  • Include references to Linux/macOS environments where applicable, and note any differences in configuration or tooling.
  • If PowerShell is required for certain operations, mention alternatives or limitations for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Cluster Resource Manager - Management Integration ...fabric-cluster-resource-manager-management-integration.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides a PowerShell example (Get-ServiceFabricPartitionHealth) for querying health reports, but does not include equivalent examples for Linux/macOS users (e.g., using sfctl or REST API). The only command-line example is Windows/PowerShell-specific, and there is no mention of Linux tooling or cross-platform alternatives for cluster management tasks.
Recommendations
  • Add equivalent examples using sfctl (the cross-platform Service Fabric CLI) for querying partition health and other management tasks.
  • Mention REST API options for health queries, which are platform-agnostic.
  • Where PowerShell examples are given, provide Linux/macOS alternatives alongside or immediately after.
  • Clarify in the text that management tasks can be performed from any OS using sfctl or REST APIs, not just via PowerShell.
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 C# and PowerShell, but omits equivalent Linux/macOS CLI examples (e.g., Azure CLI or REST API). PowerShell is presented as the primary scripting interface for service management, which is Windows-centric. There is no mention of Linux-native tools or cross-platform command-line alternatives, and PowerShell examples are given before any discussion of possible Linux approaches.
Recommendations
  • Add Azure CLI examples for service creation and metric configuration, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Mention REST API endpoints for programmatic metric management, providing links or example requests.
  • Clarify whether PowerShell examples are usable on Linux (via PowerShell Core), and if so, provide guidance; otherwise, recommend cross-platform alternatives.
  • Ensure that scripting and automation guidance is not Windows-centric by including Linux/macOS-friendly workflows.
  • Consider including bash or shell script snippets for relevant tasks.
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: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page on securing an Azure Service Fabric cluster exhibits a moderate Windows bias. Windows Server clusters and Windows authentication methods are mentioned frequently and often before Linux equivalents. Several sections (e.g., node-to-node and client-to-node security) provide links and guidance specifically for Windows standalone clusters, but do not offer equivalent Linux standalone cluster instructions or examples. Windows certificate creation tools and Windows Server certificate services are referenced, while Linux certificate management approaches are absent.
Recommendations
  • Add explicit guidance and links for securing standalone Linux Service Fabric clusters, including certificate setup and authentication methods.
  • Provide Linux-focused examples for certificate creation and management (e.g., using OpenSSL or Linux CA tools) alongside Windows examples.
  • Mention Linux authentication options or clarify if only certificate-based security is supported for Linux clusters.
  • Ensure parity in recommendations and best practices for both Windows and Linux environments.
  • Where Windows tools (e.g., MakeCert.exe) are referenced, suggest Linux alternatives or note their applicability.
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) without any Azure CLI or Bash equivalents. Application packaging is described using Visual Studio, a Windows-centric tool, with no mention of cross-platform alternatives. There are no Linux/macOS-specific instructions or examples, and Windows tools and patterns are presented exclusively and first.
Recommendations
  • Add Azure CLI examples for deployment and deletion alongside PowerShell examples.
  • Describe application packaging using cross-platform tools (e.g., dotnet CLI, SF tooling, or manual zip commands) instead of only Visual Studio.
  • Include Bash or shell scripting examples for relevant steps (e.g., uploading to blob storage).
  • Clearly indicate if Visual Studio is optional and provide alternatives for Linux/macOS users.
  • Present Windows and Linux/macOS instructions in parallel or note platform-specific differences.
GitHub Create Pull Request
Service Fabric Azure Service Fabric dynamic node tags ...tps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-node-tagging.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides PowerShell examples for managing node tags and service requirements, but does not include equivalent examples for Linux/macOS users (e.g., Bash, CLI, or REST). PowerShell is presented first and exclusively as the command-line option, which creates friction for non-Windows users.
Recommendations
  • Add Azure CLI or Bash examples for managing node tags and service requirements, if supported.
  • Include REST API usage examples for node tag operations, as REST is cross-platform.
  • Clarify whether PowerShell commands are available on Linux/macOS (via PowerShell Core), and provide guidance if so.
  • Present cross-platform command-line options (CLI, REST) before or alongside PowerShell to ensure parity.
GitHub Create Pull Request
Service Fabric Upgrade an Azure Service Fabric standalone cluster ...ce-fabric/service-fabric-cluster-upgrade-standalone.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page frequently 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 is described only for Windows. There are no Linux-specific examples, tools, or references, and Windows terminology is used exclusively or first throughout the page.
Recommendations
  • Add equivalent Linux upgrade and configuration documentation links where available.
  • Clarify whether Service Fabric standalone clusters are supported on Linux, and if so, provide Linux-specific instructions and examples.
  • Mention Linux patch orchestration options or explicitly state if POA is Windows-only.
  • Ensure that references to configuration files and procedures are platform-neutral or provide both Windows and Linux variants.
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 provides upgrade guidance for Azure Service Fabric clusters and generally avoids platform-specific instructions. However, in the 'Upgrading OS images for cluster nodes' section, it refers only to patching Windows operating systems and links exclusively to Windows-specific guidance. Additionally, throughout the document, PowerShell is mentioned as a tool for managing certificates and ports, but Linux equivalents (such as Bash or Azure CLI usage on Linux/macOS) are not explicitly shown or referenced. There are no Linux-specific examples or clear parity in tool recommendations.
Recommendations
  • Add explicit guidance and links for patching/upgrading Linux-based Service Fabric clusters, if supported.
  • When mentioning PowerShell, also reference Azure CLI usage on Linux/macOS, and provide example commands for both platforms.
  • Clarify if certain features (like Patch Orchestration Application) are Windows-only, or provide Linux alternatives if available.
  • Ensure that all management actions (certificates, ports, node properties) include cross-platform instructions or links.
GitHub Create Pull Request
Service Fabric Scalability of Service Fabric services .../service-fabric/service-fabric-concepts-scalability.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides code examples and administrative instructions primarily using PowerShell, which is a Windows-centric tool. There are no equivalent Linux CLI or bash examples, nor are Linux-native tools or patterns mentioned. PowerShell commands are presented alongside C# code, but Linux users are left without clear guidance for performing equivalent actions. The 'Choosing a platform' section does mention Linux-specific implementation differences, but does not provide Linux-specific operational examples.
Recommendations
  • Add Linux CLI/bash examples for administrative tasks such as creating/updating services and application instances.
  • Mention and link to Linux-native Service Fabric management tools (e.g., sfctl) where PowerShell is referenced.
  • Present examples for both Windows and Linux platforms, or clarify when a command is Windows-only.
  • Where possible, provide parity in documentation structure so Linux users can follow along without friction.
GitHub Create Pull Request
Service Fabric Learn more about Azure Service Fabric ...icles/service-fabric/service-fabric-content-roadmap.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides a broad overview of Azure Service Fabric, which supports both Windows and Linux. However, there is a noticeable Windows bias: Windows-specific tools (e.g., PowerShell, Visual Studio) are mentioned before Linux equivalents, and Windows terminology (e.g., Windows service, FabricHost.exe) is used throughout. Standalone cluster creation is only described for Windows, with Linux standalone clusters explicitly not supported. Examples and instructions often reference Windows tools and patterns, with Linux alternatives sometimes missing or relegated to secondary mentions.
Recommendations
  • Provide Linux-specific examples and instructions alongside Windows ones, especially for cluster creation, management, and health monitoring.
  • Mention Linux CLI tools (e.g., sfctl) and scripting options before or alongside Windows PowerShell.
  • Clarify which features are cross-platform and which are Windows-only, and link to Linux-specific guides where available.
  • Add parity in 'Next steps' and throughout the page by including Linux-focused tutorials and quickstarts.
  • Where Windows tools (e.g., Visual Studio) are referenced, also mention Linux-friendly alternatives (e.g., VS Code, CLI).
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 describes the Service Fabric hosting activation and deactivation lifecycle in a platform-neutral manner, 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 tools, and PowerShell is presented as the primary method for deploying and removing applications.
Recommendations
  • Add Linux/bash CLI examples alongside PowerShell examples for deployment and removal tasks.
  • Update 'Next steps' to include links to Linux-specific documentation or Azure CLI instructions.
  • Where PowerShell is referenced, clarify if equivalent functionality exists on Linux and provide guidance.
  • Ensure that references to tools (such as 'copy-servicefabricservicepackagetonode') mention cross-platform alternatives if available.
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 notable emphasis on Windows/PowerShell tools. PowerShell is mentioned first and in detail, while Linux tools (sfctl) are referenced but with less prominence. Visual Studio and PowerShell scripts are highlighted, both of which are primarily Windows-centric. There are no explicit Linux/macOS examples or equivalent workflows shown for parameter files or deployment scripts.
Recommendations
  • Add explicit Linux/macOS examples, such as using sfctl and shell scripts for parameter passing and deployment.
  • Provide parity in example ordering: mention sfctl (Linux/macOS) before or alongside PowerShell.
  • Include guidance for managing parameter files and deployments from non-Windows environments.
  • Clarify which tools are cross-platform and which are Windows-only, to help users choose appropriate workflows.
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 demonstrates a notable Windows bias. All manifest examples are based on the Windows Server 2016 Container Sample, and several instructions reference Windows-specific tools and patterns (e.g., using 'winver' to get the OS build version, Windows-style file paths, and references to PFX certificates). There is no mention of Linux-based Service Fabric clusters, Linux containers, or Linux-specific manifest considerations. The documentation does not provide Linux-oriented examples or guidance, which may hinder Linux users.
Recommendations
  • Provide parallel examples or guidance for Linux-based Service Fabric clusters and Linux containers, including sample manifests and configuration notes.
  • When referencing OS build versions, include Linux equivalents or clarify how to handle image selection for Linux containers.
  • Use platform-neutral file paths in examples, or show both Windows and Linux path formats where relevant.
  • Clarify which features or manifest elements are Windows-only and which are cross-platform.
  • Link to Linux container documentation or samples where available.
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, but does not offer equivalent Linux CLI (e.g., Bash, Azure CLI) examples. Windows tools and patterns (PowerShell, ApplicationManifest.xml in Visual Studio) are mentioned before or instead of Linux alternatives. While the page notes Linux support is limited, Linux users are left without clear guidance for common tasks, creating friction.
Recommendations
  • Add Azure CLI or Bash examples for setting DNS names and managing Service Fabric services on Linux clusters.
  • Clarify how Linux users can accomplish tasks shown in PowerShell (e.g., using REST API, Azure CLI, or other tools).
  • Mention and link to Linux-specific tooling or workflows where relevant (e.g., Docker Compose, YAML manifests).
  • Explicitly state any limitations or alternative approaches for Linux users in sections where Windows-only tools are referenced.
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: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides a PowerShell-only example for reporting and evaluating application health in Service Fabric, without mentioning or demonstrating equivalent Linux/macOS methods (such as REST API or CLI). The main example uses Windows-specific PowerShell cmdlets, which may create friction for Linux/macOS users. While Service Fabric supports cross-platform management, the documentation does not show parity in examples.
Recommendations
  • Add equivalent examples using the Service Fabric CLI (sfctl) for Linux/macOS users.
  • Include REST API examples for health reporting and querying, which are platform-agnostic.
  • Explicitly mention that PowerShell is Windows-specific, and provide links or guidance for Linux/macOS users.
  • Ensure that all critical tasks demonstrated with PowerShell are also shown with cross-platform tools.
GitHub Create Pull Request
Service Fabric Azure Service Fabric image store connection string ...fabric/service-fabric-image-store-connection-string.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation references PowerShell as the primary example for retrieving the cluster manifest and links to a PowerShell-based deployment guide as the next step. While .NET and REST are also mentioned, PowerShell is consistently listed first, and there are no explicit Linux/bash/CLI examples or guidance. This creates a subtle Windows-first and PowerShell-heavy bias.
Recommendations
  • Add explicit examples or references for retrieving the cluster manifest using Azure CLI or bash scripts, especially for Linux/macOS users.
  • In the 'Next steps' section, provide links to equivalent deployment guides using Azure CLI or REST, not just PowerShell.
  • When listing programmatic options (PowerShell, .NET, REST), alternate the order or clarify that all are equally supported, and consider including Azure CLI.
  • If PowerShell is cross-platform, clarify that it works on Linux/macOS as well.
GitHub Create Pull Request
Service Fabric Reliable services app manifest examples ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-manifest-example-reliable-services-app.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page for Service Fabric application and service manifest examples shows mild Windows bias. The only explicit mention of tooling is the ServiceFabric PowerShell module, with no Linux CLI or cross-platform alternatives referenced. Examples use Windows-centric patterns (e.g., .exe and .bat files), and user/group concepts reference Windows system groups (Administrators, NetworkService). There are no Linux-specific examples or guidance, and Windows terminology is used throughout, even though Service Fabric supports Linux clusters and .NET Core workloads.
Recommendations
  • Add equivalent Linux CLI examples (e.g., using Azure CLI or Service Fabric CLI) alongside or in place of PowerShell references.
  • Show examples using Linux-friendly entry points (e.g., shell scripts like setup.sh, service binaries without .exe extension).
  • Clarify which user/group concepts map to Linux (e.g., using 'root', 'service' users, or custom groups) and how to configure them.
  • Mention cross-platform considerations for endpoint configuration, resource governance, and package sharing.
  • Explicitly note when examples are Windows-specific and provide Linux alternatives where possible.
GitHub Create Pull Request
Service Fabric Networking patterns for Azure Service Fabric ...s/service-fabric/service-fabric-patterns-networking.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides only PowerShell-based deployment examples and references Windows tools (RDP, PowerShell) without offering equivalent Linux/macOS instructions or CLI examples. Windows-centric terminology and examples (e.g., RDP, C:> prompt) are used throughout, and Linux alternatives (such as Azure CLI, SSH, or Bash) are not mentioned. This creates friction for Linux/macOS users who may not use PowerShell or Windows tools.
Recommendations
  • Add Azure CLI (az) command examples alongside PowerShell for all deployment steps.
  • Include SSH instructions for accessing VMs instead of only referencing RDP.
  • Use generic file paths and prompts (e.g., ~/SFSamples/Final/template/_existingvnet.json) in examples, or show both Windows and Linux/macOS paths.
  • Mention cross-platform tools and patterns where possible, and clarify any Windows-specific steps.
  • Explicitly note that PowerShell examples are for Windows users, and provide Linux/macOS equivalents.
GitHub Create Pull Request
Service Fabric Specifying Service Fabric service endpoints ...ce-fabric/service-fabric-service-manifest-resources.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page exhibits moderate Windows bias. PowerShell is the only CLI shown for application deployment, and Windows file paths and certificate store names are mentioned first or exclusively in several places. Linux equivalents are referenced but not demonstrated with examples, and Linux-specific instructions are minimal.
Recommendations
  • Provide equivalent Linux CLI examples (e.g., using Bash with sfctl or Azure CLI) alongside PowerShell commands for deploying applications.
  • When referencing file paths or certificate stores, mention Linux paths (e.g., /var/lib/sfcerts) alongside Windows paths, and do so with equal prominence.
  • Include explicit Linux/macOS examples for common tasks, such as deploying with sfctl or configuring certificates.
  • Clarify any platform-specific behaviors or limitations in endpoint/certificate handling.
  • Where possible, link to Linux/macOS-specific documentation or guides.
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 oriented toward Visual Studio workflows, referencing Windows-specific actions (Build/Rebuild/F5/Ctrl+F5/Publish) and GUI interactions. There are no examples or instructions for Linux/macOS users, nor are cross-platform tools or command-line alternatives discussed. The only mention of non-Visual Studio deployment is a brief reference to ARM and PowerShell cmdlets, but no Linux equivalents or guidance are provided.
Recommendations
  • Add explicit guidance for Linux/macOS users, including how to manage StartupServices.xml outside Visual Studio.
  • Provide examples using Azure CLI or cross-platform tools for deploying Service Fabric applications.
  • Clarify which aspects of StartupServices.xml are Visual Studio/Windows-only and which can be used in cross-platform scenarios.
  • Include instructions for editing and deploying manifests on Linux/macOS, or state limitations clearly.
GitHub Create Pull Request
Service Fabric Service communication with the ASP.NET Core ...vice-fabric-reliable-services-communication-aspnetcore.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides comprehensive coverage of both Kestrel (cross-platform) and HTTP.sys (Windows-only) web servers for ASP.NET Core in Service Fabric. However, Windows-specific tools and patterns (e.g., HTTP.sys, netsh, Windows HTTP Server API) are discussed in detail, often before their Linux equivalents or alternatives. There are explicit notes about HTTP.sys being Windows-only, but Linux-specific guidance and examples are limited. Kestrel is correctly identified as the preferred cross-platform option, but Linux/macOS users may find the documentation less tailored to their needs, especially regarding endpoint configuration, port management, and troubleshooting.
Recommendations
  • Add explicit Linux/macOS guidance for Service Fabric scenarios, including endpoint configuration, port assignment, and firewall considerations.
  • Provide Linux/macOS-specific troubleshooting tips, especially for Kestrel usage and networking.
  • Include example workflows or code snippets for Linux/macOS environments (e.g., using systemd for service management, firewall-cmd for port opening).
  • Clarify any differences in ServiceManifest.xml handling or deployment steps for Linux clusters.
  • Ensure parity in example ordering: present Kestrel (cross-platform) examples before HTTP.sys (Windows-only) examples.
GitHub Create Pull Request
Service Fabric Add custom Service Fabric health reports ...rticles/service-fabric/service-fabric-report-health.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides detailed PowerShell examples for health reporting in Service Fabric, with no equivalent Linux/macOS CLI or scripting examples. Windows tools (PowerShell cmdlets) are mentioned and demonstrated before REST or API approaches. There is no mention of Linux-compatible tooling (such as Azure CLI, Bash, or cross-platform Service Fabric CLI), nor guidance for Linux users to perform equivalent tasks.
Recommendations
  • Add examples using Azure CLI or Service Fabric CLI (sfctl), which are cross-platform and work on Linux/macOS.
  • Include Bash or shell script snippets for health reporting, where applicable.
  • Clarify which PowerShell cmdlets are available cross-platform (PowerShell Core), and provide alternatives if not.
  • Mention REST API usage more prominently, and provide sample curl commands for Linux/macOS users.
  • Reorder sections so that cross-platform methods (REST, CLI) are presented before or alongside Windows-specific tools.
GitHub Create Pull Request
Service Fabric Learn Azure Service Fabric terminology ...es/service-fabric/service-fabric-technical-overview.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 a general overview of Azure Service Fabric terminology and concepts. While Service Fabric is a cross-platform technology, several sections (notably the 'Node' definition) reference Windows-specific tools and patterns first, such as auto-start Windows services and EXE/DLL files. Linux equivalents are not mentioned or are only referenced later. The documentation also uses Windows terminology (e.g., EXE/DLL, Windows service names) without providing Linux-specific details or parity in examples.
Recommendations
  • In the 'Node' section, clarify how Service Fabric nodes operate on Linux (e.g., which processes/services are used, how startup is handled).
  • When referencing executable formats (EXE/DLL), mention Linux equivalents (e.g., ELF binaries, .so files) and note cross-platform support.
  • Provide Linux-specific terminology and examples alongside Windows ones, especially in sections discussing deployment, node management, and code packages.
  • Where Windows services are mentioned, describe the Linux process/service model for Service Fabric nodes.
  • Consider adding a table or section explicitly comparing Windows and Linux operational differences for Service Fabric clusters.
GitHub Create Pull Request
Service Fabric Configure the upgrade of a Service Fabric application ...abric/service-fabric-visualstudio-configure-upgrade.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation is heavily focused on Windows tooling, specifically Visual Studio and PowerShell, for configuring and upgrading Service Fabric applications. All examples and instructions reference Windows tools, with no mention of Linux/macOS equivalents or cross-platform alternatives. Linux users are not provided guidance for performing upgrades or configuring parameters outside of Windows environments.
Recommendations
  • Add instructions and examples for upgrading Service Fabric applications using cross-platform tools such as Azure CLI or REST APIs.
  • Document how to configure upgrade parameters and health policies using methods available on Linux/macOS (e.g., editing manifest files, using sfctl).
  • Include references to Linux-compatible Service Fabric SDKs and tools.
  • Clearly indicate which steps are Windows-only and provide Linux/macOS alternatives where possible.
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: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation provides both CLI and PowerShell examples for associating a VM to a capacity reservation group. However, there is a notable Windows bias: PowerShell (a Windows-centric tool) is always presented as a primary automation option, and ARM template and API examples use Windows Server images by default. There are no explicit Linux-specific examples in ARM templates, and PowerShell is featured equally alongside the cross-platform Azure CLI, despite CLI being more common on Linux/macOS. The ARM template only shows Windows image SKUs, and the 'OSVersion' parameter is Windows-only, with no mention of Linux images or parameters.
Recommendations
  • Add Linux image options and parameters to ARM template examples (e.g., include Ubuntu or other Linux distributions in 'imageReference' and 'OSVersion').
  • Provide a Linux-focused ARM template example or at least a note on how to adapt the template for Linux VMs.
  • Consider presenting Azure CLI examples before PowerShell, as CLI is cross-platform and more familiar to Linux/macOS users.
  • Explicitly mention that PowerShell examples are for users who have PowerShell available, and that Azure CLI is recommended for Linux/macOS.
  • Where possible, clarify that the steps apply to both Windows and Linux VMs, and highlight any OS-specific differences.
GitHub Create Pull Request
Virtual Machines Create and upload an Ubuntu Linux VHD in Azure ...rticles/virtual-machines/linux/create-upload-ubuntu.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation, while focused on Ubuntu Linux VHDs, repeatedly references Windows-centric tools and workflows (Hyper-V, PowerShell's Convert-VHD), and provides Windows/Hyper-V steps before mentioning or omitting Linux-native alternatives. Linux users are left without clear guidance for VHD creation and conversion, and the use of Windows tools is presented as the default or only option.
Recommendations
  • Add instructions for creating and converting VHDs using Linux-native tools (e.g., qemu-img, VBoxManage, dd).
  • Provide Linux-specific examples for extracting and manipulating VHDs, not just referencing Windows/WSL.
  • Mention KVM, VirtualBox, or other Linux virtualization solutions alongside Hyper-V.
  • Clarify which steps are Windows-specific and provide equivalent Linux/macOS workflows.
  • Move Linux-native instructions and tools to the forefront, or at least present them equally with Windows options.
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_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
Although the documentation is focused on Linux VMs, there are several signs of Windows bias: PowerShell examples are provided extensively and often before or alongside Azure CLI examples, even though PowerShell is not the default scripting environment for most Linux users. Windows-specific tools and terminology (e.g., 'ipconfig', 'Write-Host', '.ps1' scripts, 'New-AzStorageBlobSASToken') are referenced without clear Linux alternatives or context. REST and ARM template examples use Windows-style scripts (PowerShell), and some explanations default to Windows patterns. There are missing Linux-specific examples for certain advanced scenarios (e.g., parameter passing, blob SAS token generation, script URI usage).
Recommendations
  • Provide Bash shell script examples in REST and ARM template sections instead of PowerShell (.ps1) scripts.
  • Clarify when a command or tool is Windows-specific and offer Linux equivalents (e.g., use 'ifconfig' or 'ip a' instead of 'ipconfig').
  • Add Linux-native instructions for generating SAS tokens (e.g., using Azure CLI or azcopy) instead of only referencing PowerShell tools.
  • Ensure parameter passing examples show both Windows (argument style) and Linux (environment variable style) clearly.
  • Where PowerShell is used, explain its applicability to Linux (e.g., PowerShell Core) and provide Bash alternatives.
  • Review all sample scripts and outputs to ensure they use Linux conventions (e.g., .sh scripts, echo, id, etc.) and avoid Windows-centric language.
GitHub Create Pull Request
Service Fabric Azure Service Fabric container image management .../articles/service-fabric/container-image-management.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page for Azure Service Fabric container image management shows minor Windows bias. Windows container base images (microsoft/windowsservercore, microsoft/nanoserver) are mentioned as default exclusions in cleanup settings, and Windows examples are referenced before Linux equivalents. However, the documentation does not provide Windows-only instructions or examples, and the configuration applies to both Windows and Linux containers.
Recommendations
  • Explicitly mention Linux container base images (such as Ubuntu, Alpine, etc.) in the 'ContainerImagesToSkip' setting example, or clarify that Linux images can be managed similarly.
  • Provide examples or notes for Linux container image management, including any differences in cleanup behavior or recommended settings.
  • Add a statement clarifying that the described settings and behaviors apply to both Windows and Linux container images, unless otherwise noted.
GitHub Create Pull Request
Service Fabric Architecture of Azure Service Fabric ...articles/service-fabric/service-fabric-architecture.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page describes the architecture of Azure Service Fabric in a platform-neutral manner overall. However, in the Management subsystem section, it specifically mentions 'PowerShell cmdlets' as a primary means of provisioning, deploying, patching, upgrading, and de-provisioning applications, without referencing equivalent Linux/macOS tooling (such as Azure CLI or REST APIs). This creates a mild Windows bias by implying PowerShell is the main or only administrative interface, and by mentioning Windows tooling first.
Recommendations
  • Mention Azure CLI and REST APIs alongside PowerShell cmdlets as supported management tools for Service Fabric clusters, especially for provisioning and lifecycle operations.
  • Clarify that administrative APIs are cross-platform and provide links or examples for Linux/macOS users.
  • Consider including example commands or references for both PowerShell and Azure CLI where relevant.
GitHub Create Pull Request
Service Fabric Overview of Azure Service Fabric ...ain/articles/service-fabric/service-fabric-overview.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation mentions both Windows and Linux support, and provides parity in describing development environments for each. However, in the 'Any OS, any cloud' section, Windows development is described first, with Visual Studio and PowerShell highlighted before Linux development tools (Eclipse, Yeoman). The quickstart link also points to a .NET (likely Windows-focused) guide, with no immediate Linux-specific quickstart linked.
Recommendations
  • Alternate the order in which Windows and Linux development environments are described, or present them together to emphasize parity.
  • Provide quickstart links for both Windows (.NET) and Linux (Java/.NET Core) development paths.
  • Ensure that introductory examples and links are balanced between Windows and Linux, or explicitly state that both are available.
  • Consider mentioning cross-platform tools (e.g., VS Code) alongside Visual Studio and Eclipse.
GitHub Create Pull Request
Virtual Machine Scale Sets Enable Automatic Zone Balance on Virtual Machine Scale Sets (Preview) ...virtual-machine-scale-sets/auto-zone-balance-enable.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation provides both Azure CLI and PowerShell examples for enabling Automatic Zone Balance on Virtual Machine Scale Sets. However, PowerShell examples (which are Windows-centric) are consistently presented alongside or after CLI examples, and the PowerShell extension configuration uses 'ApplicationHealthWindows' as the type, even in contexts where Linux is clearly supported. Portal instructions are platform-neutral, but PowerShell is a Windows tool and its prominence, as well as the lack of explicit Linux/macOS PowerShell guidance, creates a mild Windows bias. The CLI examples use Ubuntu images and 'ApplicationHealthLinux', showing Linux support, but PowerShell examples do not clarify Linux usage.
Recommendations
  • Clarify that Azure PowerShell can be used cross-platform (Windows, Linux, macOS) and provide explicit instructions/examples for Linux/macOS users if relevant.
  • In PowerShell extension examples, show both 'ApplicationHealthWindows' and 'ApplicationHealthLinux' usage, or explain when to use each.
  • Consider presenting CLI (Linux-friendly) examples before PowerShell (Windows-centric) examples, or explicitly state parity.
  • Add a note that both Azure CLI and PowerShell are available on all major platforms, and link to installation guides for Linux/macOS.
  • Ensure that screenshots and portal instructions do not assume Windows-only environments.
GitHub Create Pull Request
Virtual Machine Scale Sets Migrate deployments and resources to Virtual Machine Scale Sets in Flexible orchestration ...lexible-virtual-machine-scale-sets-migration-resources.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation provides a balanced overview of migrating to Flexible orchestration mode in Azure Virtual Machine Scale Sets. However, in the 'Create scalable network connectivity' section, Windows-specific scenarios (Windows VM activation, Windows updates) are mentioned before Linux equivalents (Linux package managers). There are no PowerShell-heavy examples, Windows tools, or missing Linux examples; the CLI and ARM Template are referenced alongside PowerShell, and all migration steps are generic to Azure VMs regardless of OS.
Recommendations
  • When listing common outbound connectivity scenarios, mention Linux package manager access before or alongside Windows activation and updates to avoid subtle Windows-first bias.
  • Ensure that any example commands or scripts (such as az vm create) are shown in both Azure CLI and PowerShell where relevant, and clarify OS-agnostic steps.
  • If referencing troubleshooting or update scenarios, provide links or notes for both Windows and Linux VM activation/update documentation.
GitHub Create Pull Request
Virtual Machines Time sync for Linux VMs in Azure ...blob/main/articles/virtual-machines/linux/time-sync.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation is focused on Linux VM time synchronization in Azure and provides extensive Linux-specific guidance and examples. However, the introductory sections discuss Windows Server 2016 improvements and Windows time sync features before Linux-specific details, and Windows documentation is referenced multiple times. All configuration and command examples are Linux-centric, with only a minor PowerShell snippet shown for base64 encoding a cloud-init file (which is relevant for Azure ARM template usage, not time sync itself). There are no missing Linux examples or Windows-only tools presented for the main task.
Recommendations
  • Move Windows Server 2016 discussion to a background or infrastructure section, clarifying its relevance to Linux VM time sync.
  • Add a Linux shell example for base64 encoding cloud-init files (e.g., 'base64 cloud-config.txt') alongside the PowerShell snippet.
  • Ensure Linux-specific links and resources are presented before or alongside Windows references.
  • Clarify that Windows references are for context about Azure host infrastructure, not for user configuration.
GitHub Create Pull Request
Virtual Machines Create a Gallery for Sharing Resources .../blob/main/articles/virtual-machines/create-gallery.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation provides examples for Azure portal, Azure CLI, PowerShell, and REST API. PowerShell is presented as a separate example, and appears after CLI, but there is no evidence of exclusive Windows tools or patterns. The CLI examples are cross-platform, and REST API is platform-neutral. However, PowerShell is included as a distinct example, which may be seen as a minor Windows-first bias, since there is no equivalent Linux shell example (e.g., Bash scripting) provided. The CLI examples are suitable for Linux/macOS users.
Recommendations
  • Clarify that Azure CLI examples are cross-platform and suitable for Linux/macOS users.
  • Consider providing Bash shell scripting examples for Linux users, or explicitly state that PowerShell is optional and not required for Linux/macOS.
  • Ensure that PowerShell examples are not presented as the primary or only scripting option.
GitHub Create Pull Request
Virtual Machines vCPU quotas ...ute-docs/blob/main/articles/virtual-machines/quotas.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for checking vCPU quotas. However, the PowerShell example is given equal prominence and is presented immediately after the CLI example, which may subtly reinforce Windows/PowerShell as a primary option. There is no explicit Linux bias, but the PowerShell section is unnecessary for Linux users, and no mention is made of Bash or other Linux-native tools. The CLI example is cross-platform, but the documentation could clarify this for Linux/macOS users.
Recommendations
  • Explicitly state that Azure CLI is cross-platform and recommended for Linux/macOS users.
  • Consider labeling the PowerShell section as 'Windows/PowerShell' and the CLI section as 'Linux/macOS/CLI' to clarify audience.
  • Add a note that PowerShell Core is available on Linux/macOS, but Azure CLI is typically preferred in those environments.
  • If possible, provide Bash or shell script examples for Linux users, or clarify that Azure CLI commands work natively in Bash.
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 ⚠ī¸ powershell_heavy
Summary
The documentation page provides a comprehensive reference for Service Fabric cluster settings, but exhibits mild Windows bias in several areas. Windows terminology and tools (e.g., certificate store names like 'My', references to Windows Defender Firewall, NTLM authentication, and Windows-specific log directories) are prevalent. Windows concepts (such as 'LocalMachine', 'MY', and Windows account types) are used as defaults or examples, and Windows-specific settings are sometimes described before Linux equivalents. Some settings and guidance reference Windows APIs or documentation (e.g., CertGetCertificateChain), and Windows-only features (like automatic updates via Windows Update) are mentioned without clear Linux alternatives. However, Linux settings and paths are also present, and most configuration options are applicable to both platforms.
Recommendations
  • Where Windows-specific terminology is used (e.g., certificate store names, account types), clarify Linux equivalents and provide Linux-specific examples.
  • Ensure that Linux paths, tools, and concepts are described alongside Windows ones, not just as secondary notes.
  • For settings referencing Windows APIs or documentation, add links or notes for Linux equivalents (e.g., OpenSSL, Linux certificate management).
  • Explicitly state when a setting is Windows-only, and provide Linux alternatives or guidance where possible.
  • Review default values and examples to ensure Linux parity (e.g., certificate store names, log directories, account types).
GitHub Create Pull Request
Service Fabric Overview of Service Fabric and containers ...s/service-fabric/service-fabric-containers-overview.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides a balanced overview of Service Fabric container support for both Linux and Windows. However, there is a slight bias in the order and emphasis: Windows container runtimes and tools (Mirantis, DockerEE) are listed in detail, and Windows scenarios (IIS lift and shift) are described before Linux equivalents. Windows tutorials and references are often shown alongside Linux, but Windows-specific tools and patterns (IIS, Windows Server containers) are highlighted more prominently.
Recommendations
  • Ensure Linux container runtimes and tools are described with equal detail as Windows (e.g., mention containerd or other Linux runtimes if relevant).
  • Present Linux and Windows scenarios in parallel, rather than listing Windows scenarios first.
  • Add more Linux-specific examples or use cases (e.g., Apache, NGINX, Python apps) to balance the IIS/Windows scenario.
  • Where possible, provide Linux and Windows tutorials/examples side by side, rather than Windows first.
  • Clarify that Service Fabric supports both Linux and Windows containers equally, unless a feature is Windows-only.
GitHub Create Pull Request
Service Fabric Package an existing executable to Azure Service Fabric ...abric/service-fabric-guest-executables-introduction.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation shows a mild Windows bias by referencing the Service Fabric SDK schema file path using a Windows directory (C:\Program Files\...), and by mentioning Visual Studio as a primary tool for packaging and deploying guest executables. There are no explicit Linux/macOS command-line examples, and the documentation does not clarify cross-platform alternatives or paths.
Recommendations
  • Add Linux/macOS equivalents for the Service Fabric SDK schema file path, or clarify if the SDK is only available on Windows.
  • Mention cross-platform tools (such as Azure CLI or Service Fabric CLI) for packaging and deploying guest executables, if available.
  • Include examples or references for using non-Windows development environments.
  • Clarify whether Visual Studio is required or if other IDEs/editors can be used.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Docker Compose Deployment Preview ...ticles/service-fabric/service-fabric-docker-compose.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both PowerShell and Service Fabric CLI (sfctl) examples for deploying Docker Compose files to Azure Service Fabric. PowerShell commands are presented first and in greater detail, which may suggest a Windows-first bias. However, the CLI examples are also included and are cross-platform. There is no evidence of missing Linux examples or exclusive mention of Windows tools, but the ordering and emphasis favor Windows users.
Recommendations
  • Present CLI (sfctl) examples before or alongside PowerShell examples to emphasize cross-platform support.
  • Explicitly state that sfctl is supported on Linux/macOS and provide installation instructions or links for those platforms.
  • Clarify any limitations or differences for Linux/macOS users, if applicable.
  • Consider balancing the depth of examples between PowerShell and CLI sections.
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 is generally platform-neutral, focusing on .NET serialization concepts relevant to Azure Service Fabric Reliable Collections. However, in the 'Next steps' section, Windows-centric tools (Visual Studio and PowerShell) are mentioned before any Linux/macOS alternatives, and there is no reference to Linux-native tools or CLI usage for application upgrades.
Recommendations
  • Add examples or links for upgrading applications using Azure CLI or Service Fabric CLI (sfctl), which are cross-platform and commonly used on Linux/macOS.
  • Mention cross-platform development environments (such as VS Code or JetBrains Rider) alongside Visual Studio.
  • Ensure that PowerShell references are accompanied by Bash or shell script alternatives where applicable.
  • Clarify that the serialization concepts apply equally to Linux-based Service Fabric clusters, and provide any Linux-specific considerations if relevant.
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 operations (attach, detach, move), but consistently presents PowerShell examples alongside CLI and portal instructions. PowerShell is a Windows-centric tool, and its inclusion may suggest a Windows bias, especially since Linux/macOS users typically use Azure CLI or REST APIs. Additionally, PowerShell examples are sometimes more detailed than their CLI counterparts. However, Azure CLI examples are present and use Linux-friendly syntax (e.g., Ubuntu image), mitigating the bias.
Recommendations
  • Clarify that Azure PowerShell is available cross-platform, but is most commonly used on Windows. Consider linking to instructions for installing Azure PowerShell on Linux/macOS.
  • Ensure that Azure CLI examples are as detailed as PowerShell examples, especially for networking and advanced options.
  • Consider adding REST API or ARM template examples for users who prefer those methods, especially on Linux/macOS.
  • Explicitly state that all operations can be performed from Linux/macOS using Azure CLI, and highlight any differences if present.
  • If possible, reorder examples to show Azure CLI before PowerShell, or alternate the order to avoid 'windows_first' bias.
GitHub Create Pull Request
Virtual Machine Scale Sets Networking for Azure Virtual Machine Scale Sets ...ne-scale-sets/virtual-machine-scale-sets-networking.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for most tasks, but PowerShell (a Windows-centric tool) is often presented before CLI, and some sections (such as querying public IPs) give PowerShell examples before CLI or in greater detail. Portal instructions are also present, but Linux/macOS parity is generally good since Azure CLI is cross-platform and included for all major operations. However, the ordering and prominence of PowerShell examples may create minor friction for Linux/macOS users.
Recommendations
  • Present Azure CLI examples before PowerShell examples in each section to prioritize cross-platform tools.
  • Ensure that every PowerShell example is matched with an Azure CLI example, especially for querying and updating resources.
  • Explicitly note that Azure CLI is recommended for Linux/macOS users, and clarify any PowerShell-specific steps.
  • Consider adding Bash script snippets where appropriate, especially for advanced networking scenarios.
  • Review the documentation for any subtle language that implies PowerShell is the default or preferred tool.
GitHub Create Pull Request
Virtual Machine Scale Sets Custom metrics for rolling upgrades on Virtual Machine Scale Sets ...tual-machine-scale-sets-rolling-upgrade-custom-metrics.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation provides both Linux (Bash/Python) and Windows (PowerShell) examples for configuring custom metrics and the application health extension. However, there are several instances where Windows-specific tools, patterns, or terminology are presented first or more prominently. For example, PowerShell examples and Windows extension types are often shown before or alongside Linux equivalents, and the REST/ARM examples default to 'ApplicationHealthWindows'. The PowerShell section is detailed and uses Windows-centric variable names and extension types. The CLI examples are cross-platform, but Windows tools and patterns are mentioned at least as much as Linux ones, sometimes before them.
Recommendations
  • Ensure Linux and Windows extension types are presented equally in all code samples and explanations. For example, REST/ARM examples should show both 'ApplicationHealthLinux' and 'ApplicationHealthWindows' or clarify when to use each.
  • Alternate the order of Bash and PowerShell examples, or present Bash first to avoid implicit Windows-first bias.
  • Clarify which examples are for Linux and which are for Windows, especially in sections where only one is shown.
  • Add explicit Linux-focused troubleshooting and verification steps, such as using systemd or other Linux-native tools for health endpoint management.
  • Where possible, use neutral variable names and avoid Windows-centric naming in generic examples.
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 parity between Azure CLI and PowerShell for all command-line examples, but consistently lists PowerShell examples after CLI and includes detailed PowerShell scripts. While Azure CLI is cross-platform, PowerShell examples are Windows-centric and may not be as relevant for Linux/macOS users. There are no Linux-specific tools or shell examples (e.g., Bash), and the documentation does not mention Linux/macOS explicitly, which may create minor friction for non-Windows users.
Recommendations
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows, and recommend CLI as the preferred cross-platform method.
  • Add Bash shell examples or note that Azure CLI commands can be run in Bash/Terminal on Linux/macOS.
  • Consider reordering tabs so CLI appears first, emphasizing its cross-platform nature.
  • Explicitly state that PowerShell examples are optional and primarily for Windows users.
  • Mention prerequisites for CLI usage on Linux/macOS (e.g., installation links).
GitHub Create Pull Request
Virtual Machine Scale Sets Orchestration modes for Virtual Machine Scale Sets in Azure ...sets/virtual-machine-scale-sets-orchestration-modes.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation provides a conceptual overview and feature comparison for orchestration modes in Azure Virtual Machine Scale Sets. It generally maintains OS neutrality, but there is a minor bias in the order of presenting operating system support: Windows is mentioned before Linux in several places (e.g., 'Mix operating systems | Yes, Linux and Windows can reside in the same Flexible scale set'). Additionally, the only explicit command-line example uses Azure CLI, which is cross-platform, and there are no PowerShell-only or Windows-specific tools referenced. However, in the Backup and Recovery section, Azure Site Recovery is noted as 'Yes (via PowerShell)' for Flexible orchestration, which may imply a Windows-centric approach, but this is a feature limitation rather than a documentation bias.
Recommendations
  • Where OS support is discussed, alternate the order (e.g., 'Linux and Windows' vs 'Windows and Linux') or clarify parity.
  • If Azure Site Recovery is available via CLI or REST for Linux, mention those options; if not, clarify the limitation.
  • Consider adding explicit Linux/macOS usage notes or examples where relevant, especially for extension installation or application health monitoring.
  • Ensure that future command-line examples include both Azure CLI and PowerShell (if applicable), and clarify cross-platform compatibility.
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
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for creating and updating scale sets with Availability Zones. However, PowerShell examples are given equal prominence to CLI, and in some sections (such as updating scale sets), PowerShell is listed before REST API and ARM template methods. There is no explicit Linux shell example (e.g., Bash), and PowerShell is a Windows-centric tool, although it is now cross-platform. The documentation does mention Linux in the ARM template section, but does not provide Linux-specific command-line examples or highlight Linux workflows.
Recommendations
  • Add explicit Bash or Linux shell examples alongside Azure CLI, especially for update operations.
  • Clarify that Azure CLI commands are cross-platform and suitable for Linux/macOS users.
  • Consider listing Azure CLI examples before PowerShell examples, as CLI is more commonly used on Linux/macOS.
  • Add notes or links to Linux-specific quickstart guides where relevant.
  • Ensure parity in example coverage for Linux users, including troubleshooting or known issues sections.
GitHub Create Pull Request
Virtual Machines Azure VM Extensions and Features for Linux ...articles/virtual-machines/extensions/features-linux.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all major operations (discover, run, check, remove extensions), but consistently presents PowerShell examples immediately after CLI and sometimes with more detail. There is no evidence of Windows-only tools or missing Linux examples, but PowerShell is not a native Linux tool and its prominence may create friction for Linux users. The documentation does not use Windows-specific tools or patterns, and all examples are Linux-appropriate. However, PowerShell is featured almost as prominently as CLI, which is more natural for Linux users.
Recommendations
  • Prioritize Azure CLI examples before PowerShell throughout the documentation, as CLI is more native to Linux environments.
  • Clearly indicate that PowerShell is optional and not required for Linux users.
  • Consider grouping CLI and PowerShell examples under separate tabs or sections, with CLI as the default for Linux-focused docs.
  • Add brief notes on how to install and use Azure CLI on Linux, and clarify that PowerShell is available but not necessary.
GitHub Create Pull Request
Virtual Machines Support matrix for VM restore points ...n/articles/virtual-machines/concepts-restore-points.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation presents Windows operating system support details before Linux, but provides parity in listing both OS types and their requirements. No Windows-specific tools, examples, or patterns are prioritized elsewhere. The 'Next steps' section references CLI, Portal, and PowerShell equally, without favoring Windows tools.
Recommendations
  • Consider listing Linux operating system support before or alongside Windows to avoid 'windows_first' ordering bias.
  • Ensure that future examples and walkthroughs (linked from 'Next steps') provide both Windows and Linux command-line instructions.
  • Explicitly mention that CLI and PowerShell instructions are available for both platforms, if applicable.
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 presented immediately after the CLI example and before the portal and ARM template examples. While Azure CLI is cross-platform, PowerShell is primarily associated with Windows, although it is available on Linux and macOS. There are no Linux-specific shell examples (e.g., Bash), and no explicit mention of Linux/macOS compatibility for PowerShell commands. The documentation does not reference Windows-only tools, but the ordering and emphasis may subtly favor Windows users.
Recommendations
  • Explicitly note that Azure CLI commands are cross-platform and suitable for Linux/macOS users.
  • Consider providing Bash shell examples or clarifying that CLI commands are intended for Bash/zsh environments.
  • Add a note that Azure PowerShell is available on Linux/macOS, or link to installation instructions for those platforms.
  • Alternate the order of CLI and PowerShell examples to avoid implicit Windows-first bias.
  • If possible, include sample scripts for Linux users (e.g., Bash) for common tasks.
GitHub Create Pull Request
Virtual Machines NVIDIA GPU Driver Extension - Azure Linux VMs ...es/virtual-machines/extensions/hpccompute-gpu-linux.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation is focused on Linux VM GPU driver installation, but includes PowerShell examples alongside Azure CLI and ARM template examples. In several sections, PowerShell commands are presented before Azure CLI equivalents, which may create friction for Linux users. However, Linux-specific instructions, troubleshooting, and examples are comprehensive and prioritized.
Recommendations
  • Present Azure CLI examples before PowerShell examples, as Azure CLI is more commonly used on Linux.
  • Clearly indicate that PowerShell examples are primarily for users on Windows or those who prefer PowerShell, and provide equivalent Bash/CLI instructions for all tasks.
  • Consider removing or de-emphasizing PowerShell examples unless they are necessary for cross-platform parity.
  • Add Bash script examples where relevant, especially for troubleshooting or manual driver installation.
GitHub Create Pull Request
Virtual Machines Deprovision or generalize a VM before creating an image ...docs/blob/main/articles/virtual-machines/generalize.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides clear, separate instructions for both Linux and Windows VM generalization. However, in the Windows section, PowerShell/Command Prompt examples are given, and the Windows steps include a PowerShell command to mark the VM as generalized, while the Linux section uses Azure CLI. The Windows section also appears after the Linux section, so 'windows_first' bias is minimal. Both OSes are covered, but Windows-specific tooling (PowerShell) is used for Windows, and Linux-specific tooling (waagent, SSH, Azure CLI) is used for Linux.
Recommendations
  • Consider adding Azure CLI equivalents for Windows VM generalization steps, so Windows users can use CLI if preferred.
  • Ensure parity in the depth of examples and explanations for both OSes.
  • Mention that Azure CLI can be used for both Linux and Windows VMs to mark them as generalized, if applicable.
  • If possible, provide cross-platform commands for marking VMs as generalized (e.g., Azure CLI for both).
GitHub Create Pull Request
Virtual Machines HBv3-series virtual machine (VM) overview, architecture, topology - Azure Virtual Machines | Microsoft Docs ...main/articles/virtual-machines/hbv3-series-overview.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation is generally cross-platform and provides information relevant to both Linux and Windows users. However, in the 'Software specifications' table, 'Recommended OS for Performance' lists 'Windows Server 2019+' without mentioning any Linux distributions, which may imply a preference for Windows. Additionally, Windows is mentioned first in some OS support lists, though Linux support is clearly stated elsewhere. No PowerShell-specific commands, Windows-only tools, or missing Linux examples are present.
Recommendations
  • In the 'Recommended OS for Performance' row, include recommended Linux distributions (e.g., 'RHEL 8+, Ubuntu 20.04+, SLES 15 SP4+') if applicable, or clarify if Windows Server 2019+ is recommended only for Windows workloads.
  • When listing supported OSes, alternate or group Linux and Windows examples to avoid the appearance of prioritizing Windows.
  • If performance recommendations are genuinely Windows-specific, explicitly state so to avoid confusion for Linux users.
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 Linux, but deployment and troubleshooting sections present Azure PowerShell examples before Azure CLI, and some warnings are PowerShell-specific. While Azure CLI is covered, PowerShell is emphasized and shown first, which may create friction for Linux users who typically prefer CLI tools. No Windows-only tools or patterns are used, and all technical instructions are Linux-centric.
Recommendations
  • Present Azure CLI examples before Azure PowerShell in deployment and troubleshooting sections, as CLI is more native to Linux environments.
  • Add explicit notes clarifying that Azure PowerShell is optional and not required for Linux users.
  • Highlight Linux-native troubleshooting tools (such as journalctl or systemd commands) for extension status, in addition to Azure CLI.
  • Ensure all JSON and code snippets use Linux path conventions and shell syntax where appropriate.
GitHub Create Pull Request
Virtual Machines Create an image definition and image version ...s/blob/main/articles/virtual-machines/image-version.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Linux and Windows guidance, but there is a subtle Windows bias in the ordering and example emphasis. PowerShell examples are presented with Windows as the default, and Windows terminology (Sysprep) is mentioned before Linux equivalents. CLI and REST examples are neutral, but PowerShell sections use Windows as the primary example and Linux as a secondary note.
Recommendations
  • Alternate the order of Linux and Windows examples in PowerShell and CLI sections, or provide parallel examples for both.
  • Explicitly show Linux-focused PowerShell examples (e.g., using -OsType Linux) alongside Windows examples.
  • Ensure that Linux terminology (waagent -deprovision) is mentioned equally with Windows terminology (Sysprep) in introductory sections.
  • Consider starting example blocks with Linux scenarios, or at least alternating which OS is shown first.
  • Add notes clarifying parity between Linux and Windows wherever relevant.
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: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation covers preparing and uploading a Red Hat Enterprise Linux VHD for Azure using multiple hypervisors (Hyper-V, KVM, VMware, Kickstart). While Linux-centric throughout, the structure and ordering of sections consistently place Hyper-V (a Windows-centric hypervisor) first, with detailed step-by-step instructions. Linux-native hypervisors (KVM, VMware, Kickstart) are covered in depth and parity, but their sections are always listed after Hyper-V. There are references to using Hyper-V Manager and Windows tools for disk conversion, but Linux alternatives (qemu-img, guestfish) are also provided. No critical Linux examples are missing, and Linux users can fully complete the task.
Recommendations
  • Reorder the hypervisor sections so that Linux-native options (KVM, VMware, Kickstart) are presented before Hyper-V, or at least alternate the order to avoid implicit Windows primacy.
  • Add a brief note at the top clarifying that all hypervisor options are equally supported and that users should select the section relevant to their environment.
  • Where disk conversion is discussed, ensure Linux tools (qemu-img, guestfish) are mentioned alongside Windows tools, not only as secondary options.
GitHub Create Pull Request
Virtual Machines Create an Azure Image Builder Bicep file or ARM template JSON template .../articles/virtual-machines/linux/image-builder-json.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation covers both Linux and Windows VM image creation with Azure Image Builder, providing parity in most areas. However, there are several instances where Windows-specific tools (PowerShell, Windows commands) are mentioned first or exclusively, and PowerShell is used for checksum generation and other tasks, while Linux equivalents are sometimes only mentioned later or in passing. Windows examples and customizers (PowerShell, WindowsRestart, WindowsUpdate) are described in more detail, and PowerShell commands are often shown before Azure CLI or Linux shell equivalents.
Recommendations
  • Ensure Linux shell commands (e.g., for checksum generation) are always provided alongside PowerShell equivalents, and shown with equal prominence.
  • Where PowerShell is referenced for validation or customization, provide clear Bash/shell alternatives for Linux users.
  • In sections listing customizer types, avoid listing Windows-specific customizers (PowerShell, WindowsRestart, WindowsUpdate) before Linux equivalents (Shell), or alternate the order.
  • For commands to register features or manage resources, show Azure CLI examples first or equally with PowerShell.
  • Expand Linux-specific troubleshooting and guidance to match the detail provided for Windows (e.g., logs, error messages, customization advice).
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: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation covers both Windows and Linux VM images, but there are signs of Windows bias. PowerShell examples are provided alongside Azure CLI, but PowerShell is a Windows-centric tool. In several places, Windows-related links and examples are listed before Linux equivalents (e.g., uploading VHDs, specialized image creation). References to Azure PowerShell are frequent and sometimes prioritized over CLI. However, Linux-specific information (such as waagent for generalization) is included, and Azure CLI examples are present, which mitigates the bias.
Recommendations
  • Ensure Linux and Azure CLI examples are always provided alongside PowerShell, and shown first or equally.
  • Where possible, use cross-platform tools (Azure CLI, REST API) as the primary example, with PowerShell as an alternative.
  • Explicitly mention that Azure PowerShell is Windows-centric, and recommend Azure CLI for Linux/macOS users.
  • Review all linked pages to ensure Linux parity in walkthroughs and examples.
  • Add more Linux-specific troubleshooting tips and links where relevant.
GitHub Create Pull Request