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

Live Progress

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

Scan Information

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

Finished At: In Progress

Status: in_progress

Target Repo: Azure Compute

Current Phase: discovery

Files Queued: 283

Files Completed: 283

Problematic Pages

92 issues found
Service Fabric Initializer CodePackages in Service Fabric ...in/articles/service-fabric/initializer-codepackages.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page for Initializer CodePackages in Service Fabric is heavily focused on Windows containers. All examples reference Windows container images, Windows paths, and Windows command syntax (cmd.exe). There are no examples or guidance for Linux containers or Linux-based workloads, despite Service Fabric supporting both Windows and Linux containers. Windows-specific tools and patterns (e.g., cmd, Windows paths, Windows container images) are mentioned exclusively, and Linux equivalents are not provided.
Recommendations
  • Add examples using Linux container images (e.g., Ubuntu, Alpine) to demonstrate Initializer CodePackages for Linux workloads.
  • Provide Linux command syntax (e.g., bash, sh) in the CodePackage examples.
  • Show how to specify Linux volume mounts (e.g., /workspace-on-host:/workspace-on-container) in ApplicationManifest.xml.
  • Clarify in the introduction whether Initializer CodePackages are supported for Linux containers, and if so, provide parity in documentation.
  • If Initializer CodePackages are Windows-only, explicitly state this limitation at the top of the page.
GitHub Create Pull Request
Service Fabric Azure Service Fabric reverse proxy ...articles/service-fabric/service-fabric-reverseproxy.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation explicitly states that the Service Fabric reverse proxy is not available for Linux clusters, and all examples and guidance are Windows-centric. There are no Linux-specific instructions, examples, or alternatives provided. The page assumes Windows usage throughout, and Linux users are informed that the feature is unavailable to them.
Recommendations
  • Clearly indicate at the top that reverse proxy is Windows-only, to prevent confusion for Linux users.
  • Provide links or references to any Linux alternatives or workarounds, if available (e.g., custom proxy solutions or other Service Fabric communication patterns for Linux clusters).
  • If reverse proxy support for Linux is planned, mention roadmap or expected timelines.
  • Add a prominent note in the 'Next steps' section to clarify that all guidance applies only to Windows clusters.
GitHub Create Pull Request
Service Fabric Standalone Service Fabric clusters overview ...-fabric/service-fabric-standalone-clusters-overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
Although the page introduction claims Service Fabric clusters run on both Windows Server and Linux, the content and supported operating systems section clarify that Linux is not yet supported for standalone clusters. Security and operational guidance is almost entirely Windows-focused, with no Linux-specific instructions or examples. This creates confusion and friction for Linux users seeking parity.
Recommendations
  • Clarify early in the document that standalone clusters are currently Windows-only, despite the initial claim of Linux support.
  • Remove or revise statements suggesting Linux support until it is available.
  • Add a prominent note or warning about Linux support status to prevent misleading readers.
  • When Linux support becomes available, provide equivalent Linux examples, instructions, and security guidance.
GitHub Create Pull Request
Service Fabric Configure the upgrade of a Service Fabric application ...abric/service-fabric-visualstudio-configure-upgrade.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation is heavily focused on Windows tooling, specifically Visual Studio and PowerShell, for upgrading Service Fabric applications. All examples and workflows reference Windows tools, with no mention of Linux/macOS equivalents or cross-platform CLI options. Linux users are not provided with guidance or examples for completing the upgrade process.
Recommendations
  • Add instructions and examples for upgrading Service Fabric applications using Azure CLI or REST API, which are cross-platform.
  • Mention and provide guidance for using Service Fabric CLI (sfctl), which works on Linux/macOS.
  • Clarify which steps are Windows-only and provide alternative workflows for Linux/macOS users.
  • Include Linux/macOS-specific examples for configuring upgrade parameters and health policies.
GitHub Create Pull Request
Service Fabric Introduction to the Service Fabric Infrastructure Service .../articles/service-fabric/infrastructure-service-faq.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides a PowerShell-only example for bypassing Infrastructure Service, and references Service Fabric Explorer (a Windows-centric tool) without mentioning Linux/macOS alternatives. While Service Fabric is cross-platform, the guidance and examples are Windows-focused, creating friction for Linux/macOS users.
Recommendations
  • Add equivalent CLI or REST API examples for bypassing Infrastructure Service, suitable for Linux/macOS users.
  • Mention and link to cross-platform management tools (e.g., Azure CLI, Service Fabric CLI) where possible.
  • Clarify if Service Fabric Explorer is available cross-platform or suggest alternatives for Linux/macOS users.
  • Provide Linux/macOS-specific instructions or note any limitations for non-Windows users.
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 using Azure PowerShell modules and references PowerShell-based tools prominently. While Azure CLI and ARM/Bicep are mentioned, PowerShell examples are given first and in more detail, which may create friction for Linux/macOS users who prefer CLI or scripting tools native to their platforms.
Recommendations
  • Add explicit Azure CLI examples for key operations (e.g., deleting NodeTypes, restarting/reimaging scale sets) alongside PowerShell examples.
  • Ensure CLI and Bicep/ARM template usage is described with equal prominence to PowerShell.
  • Clarify that all recommended tools (Azure CLI, ARM templates, Bicep) are fully cross-platform and provide links to their documentation.
  • Consider listing Azure CLI examples before or alongside PowerShell to avoid 'windows_first' bias.
GitHub Create Pull Request
Service Fabric Architecture of Azure Service Fabric ...articles/service-fabric/service-fabric-architecture.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation mentions PowerShell cmdlets as a primary management interface for Service Fabric, without referencing Linux/macOS equivalents such as Azure CLI or REST APIs. This may give the impression that management is Windows-centric, and Linux users may not realize alternative tools exist.
Recommendations
  • Explicitly mention cross-platform management options, such as Azure CLI or REST APIs, alongside PowerShell cmdlets.
  • Provide links or references to documentation on managing Service Fabric clusters from Linux/macOS environments.
  • Clarify which management tools are available on which platforms to avoid confusion.
GitHub Create Pull Request
Service Fabric Azure Service Fabric security best practices ...rvice-fabric/service-fabric-best-practices-security.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation provides both Windows and Linux guidance for key security tasks, such as certificate generation and secret encryption, but Windows-specific tools (PowerShell, Windows Defender, Azure DSC) are mentioned first or exclusively in several sections. Windows examples and terminology appear before Linux equivalents, and some sections (Windows Defender, DSC, security baselines) are Windows-only without Linux alternatives or parity suggestions.
Recommendations
  • Where possible, present Windows and Linux examples side-by-side or in parallel sections, rather than Windows-first.
  • For sections like security baselines and antimalware, provide links or references to Linux security best practices (e.g., CIS Linux benchmarks, Linux antivirus solutions) or clarify Linux equivalents.
  • Mention Linux tooling (such as openssl, Linux security modules, etc.) alongside Windows tools, and avoid PowerShell-heavy bias unless the task is Windows-only.
  • Clarify when a feature or recommendation is Windows-only and provide Linux-specific guidance or alternatives where applicable.
  • Ensure that template snippets and instructions are equally applicable to Linux clusters, or note any differences.
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: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides several manual scaling instructions using PowerShell cmdlets (e.g., Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState) without mentioning Linux/macOS equivalents or CLI alternatives. Windows/PowerShell-based steps are given first and exclusively in critical scaling workflows, while Linux clusters are only referenced in the 'Next steps' section. There are no Bash, Azure CLI, or cross-platform examples for these operations.
Recommendations
  • Add Azure CLI or Bash examples for scaling operations, especially for disabling/removing nodes and managing cluster state.
  • Explicitly mention cross-platform tools or workflows for Linux/macOS users, such as using Azure CLI or REST API for node management.
  • Clarify if PowerShell cmdlets are available on Linux/macOS (via PowerShell Core), or provide alternative commands.
  • Ensure that instructions for scaling clusters are equally accessible for both Windows and Linux clusters, not just in 'Next steps'.
GitHub Create Pull Request
Service Fabric Application lifecycle in Service Fabric ...service-fabric/service-fabric-application-lifecycle.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page heavily references PowerShell cmdlets and Windows-centric tooling (e.g., Remove-ServiceFabricApplicationPackage, Register-ServiceFabricApplicationType) throughout all lifecycle phases, often as the primary or only command-line example. While REST API and .NET SDK methods are also mentioned, there is a notable lack of explicit Linux/macOS CLI examples (such as Azure CLI or Service Fabric CLI [sfctl]), and no bash or cross-platform shell commands are provided. This creates friction for Linux/macOS users, who must infer or research equivalent commands.
Recommendations
  • Add explicit examples using Service Fabric CLI (sfctl) and/or Azure CLI for all major operations alongside PowerShell examples.
  • Where PowerShell cmdlets are referenced, provide equivalent bash or cross-platform command-line snippets.
  • Clarify in each section which tools are cross-platform and which are Windows-only.
  • Link to Linux/macOS-specific guidance or quickstarts where available.
  • Consider reordering examples to show cross-platform tools (sfctl, REST API) before or alongside Windows PowerShell.
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 PowerShell examples for configuring auto scaling policies, but does not offer equivalent Linux/macOS command-line examples (e.g., Bash, CLI, or cross-platform tools). Windows-specific tools (PowerShell) are presented alongside C# and manifest examples, but Linux users are left without guidance for command-line operations. The documentation also presents PowerShell examples before mentioning Linux support, and does not clarify how Linux users should perform these tasks.
Recommendations
  • Add Azure CLI or Bash examples for configuring scaling policies, especially for Linux-based Service Fabric clusters.
  • Explicitly state which PowerShell commands are cross-platform (if any), or provide alternatives for Linux/macOS users.
  • Clarify any limitations or differences for Linux clusters, and link to relevant Linux-specific documentation.
  • Consider reordering examples so that cross-platform or manifest-based approaches are shown before Windows-specific tools.
  • Mention any GUI or portal-based configuration options if available, for broader accessibility.
GitHub Create Pull Request
Service Fabric Azure Service Fabric networking best practices ...ice-fabric/service-fabric-best-practices-networking.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation provides both Windows and Linux guidance in several sections, but there is a notable Windows bias in example ordering, tool references, and some explanations. Windows/PowerShell examples and terminology are often presented first or exclusively, while Linux equivalents are sometimes missing or referenced second. Some sections (e.g., Azure DevOps, Client API, application networking) focus on Windows-specific tools or patterns without Linux parity.
Recommendations
  • Ensure all PowerShell/API examples are accompanied by equivalent CLI or Linux-native examples, especially in sections referencing 'Client API' and Azure DevOps.
  • When referencing tools (e.g., Service Fabric Explorer, reverse proxy), clarify Linux compatibility and provide Linux-specific instructions or links.
  • Avoid presenting Windows examples or terminology first unless the feature is Windows-only; alternate ordering or group by OS.
  • Expand application networking guidance to include Linux container scenarios and networking modes.
  • Where possible, provide ARM template samples for both Windows and Linux clusters, not just Windows.
  • Clarify when a feature or tool is Windows-only to reduce confusion for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Azure Service Fabric application resource model ...ervice-fabric/service-fabric-concept-resource-model.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page for the Azure Service Fabric application resource model demonstrates notable Windows bias. All deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) without mention of Azure CLI equivalents or Bash scripting. Application packaging instructions reference Visual Studio, a Windows-centric tool, and do not provide alternatives for Linux/macOS users. No Linux-specific guidance or cross-platform examples are present, and Windows tools are mentioned first and exclusively.
Recommendations
  • Add Azure CLI examples for deployment, upgrade, and deletion alongside PowerShell examples.
  • Provide instructions for packaging applications using cross-platform tools (e.g., dotnet CLI, SF SDK for Linux/macOS).
  • Mention and link to Linux/macOS-compatible development environments (e.g., VS Code, command-line tools) for application packaging.
  • Clarify which steps are Windows-only and offer Linux/macOS alternatives where possible.
  • Ensure screenshots and walkthroughs are not exclusively tied to Windows UI (e.g., Visual Studio), or supplement them with cross-platform options.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Docker Compose Deployment Preview ...ticles/service-fabric/service-fabric-docker-compose.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both PowerShell and Service Fabric CLI (sfctl) examples for deploying Docker Compose files, but PowerShell examples are presented first and in greater detail. PowerShell is a Windows-centric tool, while sfctl is cross-platform. There are no explicit Linux/macOS-specific instructions or examples, and no mention of Linux shell alternatives for PowerShell commands.
Recommendations
  • Present sfctl (Service Fabric CLI) examples before PowerShell, as sfctl is cross-platform and more relevant to Linux/macOS users.
  • Clarify that PowerShell commands are Windows-specific, and that sfctl is recommended for Linux/macOS environments.
  • Add explicit Linux/macOS instructions, such as how to install sfctl and prerequisites for running Service Fabric Compose deployments on those platforms.
  • Consider providing Bash shell examples for common tasks if applicable.
  • Mention any limitations or differences for Linux/macOS users, if present.
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-specific tools (e.g., RDP, Windows command prompt for ping). There are no equivalent examples for Linux/macOS users (such as Azure CLI or Bash), and Windows tools are mentioned first and exclusively. This creates friction for non-Windows users, as they must translate instructions or find alternative tooling.
Recommendations
  • Add Azure CLI (az) examples alongside PowerShell for all deployment steps.
  • Include Bash shell commands for template deployment and network testing (e.g., ping, ssh).
  • Mention cross-platform remote access methods (e.g., SSH for Linux VMs) in addition to RDP.
  • Clarify that PowerShell examples are for Windows users, and provide links or instructions for Linux/macOS users.
  • Consider restructuring examples so that cross-platform tools (Azure CLI) are shown first or equally.
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-centric tools and workflows. PowerShell is mentioned first for application creation, and Visual Studio (a Windows-first IDE) is referenced for parameter management. While sfctl and Jenkins are mentioned, Linux-native examples and workflows are less prominent, and the ordering favors Windows tools.
Recommendations
  • Provide explicit Linux/macOS command-line examples for parameter passing, such as using sfctl with install.sh, and clarify how Linux users can replicate Visual Studio/PowerShell workflows.
  • Add sample shell scripts (bash) for parameter substitution and deployment, highlighting cross-platform approaches.
  • Reorder examples so that Linux-native tools (sfctl, Jenkins) are presented before or alongside Windows tools.
  • 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 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 is generally platform-neutral in its conceptual explanations, but the 'Next steps' section and some linked references emphasize PowerShell for deployment/removal tasks, which is traditionally Windows-centric. There are no explicit Linux or cross-platform CLI examples or references, and the only advanced example for downloading a ServicePackage links to a PowerShell cmdlet. This creates friction for Linux/macOS users seeking parity.
Recommendations
  • Add equivalent Linux/macOS instructions and examples for deploying/removing applications, such as using Azure CLI or Service Fabric CLI (sfctl).
  • Include references to cross-platform tools and commands alongside PowerShell, especially in 'Next steps' and practical sections.
  • Clarify which steps or tools are platform-specific and provide alternatives where possible.
  • Link to documentation for Linux clusters and their management tools.
GitHub Create Pull Request
Virtual Machine Scale Sets Migrate deployments and resources to Virtual Machine Scale Sets in Flexible orchestration ...lexible-virtual-machine-scale-sets-migration-resources.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation references Azure CLI, Azure PowerShell, and ARM templates for creating and migrating resources, but does not provide explicit Linux/bash examples or mention Linux tools. PowerShell is mentioned alongside Azure CLI, but no Linux-specific scripting guidance is given. Windows scenarios (activation, updates) are listed before Linux (package managers) in outbound connectivity requirements. There are no explicit Linux/macOS shell examples or parity guidance.
Recommendations
  • Add explicit bash/Linux shell examples alongside Azure CLI and PowerShell, especially for VM creation and migration steps.
  • Mention Linux-specific migration considerations (e.g., package manager updates, SSH configuration) in relevant sections.
  • Ensure Linux scenarios are given equal prominence in outbound connectivity requirements, not listed after Windows scenarios.
  • Clarify that Azure CLI is cross-platform and provide example commands for both Windows (PowerShell) and Linux/macOS (bash).
  • Include links to Linux documentation or migration guides where appropriate.
GitHub Create Pull Request
Service Fabric Manage certificates in a Service Fabric cluster ...vice-fabric/cluster-security-certificate-management.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page provides extensive PowerShell examples and references Windows-specific tools (such as the Key Vault VM extension for Windows and S-channel), with minimal or no coverage of Linux/macOS equivalents. Windows terminology and mechanisms are presented first and in detail, while Linux-specific guidance is largely absent. The certificate provisioning and management flows are described primarily in the context of Windows VM/VMSS, and troubleshooting/programmatic examples are exclusively PowerShell-based.
Recommendations
  • Add equivalent Bash/CLI examples for certificate enrollment, provisioning, and management, especially for Azure CLI and REST API usage.
  • Explicitly document how certificate provisioning and autorollover work for Linux-based Service Fabric clusters, including supported extensions and mechanisms.
  • Clarify any Windows-only limitations or features, and provide guidance for Linux/macOS users where parity is possible.
  • Include troubleshooting steps and FAQ entries relevant to Linux environments.
  • Reference and link to Linux-specific documentation for Key Vault VM extensions (if available) and Service Fabric certificate management.
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 shown, with no mention of Azure CLI or Bash equivalents. PowerShell is presented as the sole scripting option for command-line operations, which may create friction for Linux/macOS users. The ordering of examples also tends to show PowerShell before other CLI options, reinforcing Windows-first patterns.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all command-line operations (add, remove, scale, configure node types).
  • Explicitly mention that PowerShell commands can be run cross-platform using PowerShell Core, or provide Bash/CLI alternatives.
  • Clarify whether any steps are Windows-only, or if all operations are supported on Linux/macOS.
  • Consider including a section on using Azure CLI for Service Fabric managed clusters, or linking to relevant CLI documentation.
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 ⚠ī¸ missing_linux_example
Summary
The documentation provides several examples and troubleshooting steps that are Windows-centric, such as referencing the Windows certificate store (LocalMachine\My), Win32 CryptoAPI, and Windows event logs. Linux equivalents are mentioned only briefly or as afterthoughts, and there are no concrete Linux command-line examples or troubleshooting guidance. This may create friction for Linux cluster administrators.
Recommendations
  • Provide explicit Linux examples for certificate storage, retrieval, and troubleshooting (e.g., using /var/lib/sfcerts, openssl, or Linux logging tools).
  • When referencing certificate stores, always mention both Windows and Linux paths equally and provide details for both.
  • Include Linux-specific troubleshooting steps and log file locations, not just Windows Event Log channels.
  • If referencing Windows APIs (e.g., CertGetCertificateChain), clarify the Linux equivalent or note how Service Fabric handles this on Linux.
  • Add examples using Linux tools (e.g., openssl, keytool) for certificate inspection and validation.
GitHub Create Pull Request
Service Fabric Azure Service Fabric container image management .../articles/service-fabric/container-image-management.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation references Windows container base images (microsoft/windowsservercore, microsoft/nanoserver) as default exclusions in cleanup, but does not mention Linux container base images or provide Linux-specific guidance. No examples or discussion of Linux container image management, nor parity in exclusion patterns for common Linux images (e.g., Ubuntu, Alpine) are provided.
Recommendations
  • Add examples or mention of Linux container base images (such as 'docker.io/library/ubuntu', 'docker.io/library/alpine') in the 'ContainerImagesToSkip' setting.
  • Clarify whether the cleanup settings and behaviors apply equally to Linux containers, and if not, provide Linux-specific guidance.
  • Provide examples of container image management for both Windows and Linux containers to ensure parity.
  • Explicitly state platform limitations if any features are Windows-only.
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 is primarily focused on deploying custom Windows images in Azure Service Fabric Managed Clusters. Windows terminology and examples are presented first and most prominently. The PowerShell example for role assignment is given without a Linux CLI equivalent, and the text repeatedly refers to 'custom windows images' rather than generic or Linux images. However, there are references and links to Linux custom image creation and Azure CLI usage, indicating partial Linux support.
Recommendations
  • Provide equivalent Azure CLI examples for role assignment and other operations alongside PowerShell.
  • Clarify that custom images can be Linux-based as well, and update language to be OS-neutral where appropriate.
  • Add explicit examples and guidance for deploying Linux custom images, including ARM template snippets and prerequisites.
  • Ensure links to Linux documentation are as prominent as Windows documentation.
  • Review terminology to avoid defaulting to 'Windows' unless the feature is Windows-only.
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 instructions for Service Fabric Explorer and ARM-managed clusters, consistently referencing Az PowerShell cmdlets (e.g., Remove-AzResource, AzSF PowerShell) for resource operations. While the az CLI is mentioned once for deleting applications, the majority of examples and guidance prioritize PowerShell tools, which are more commonly used on Windows. There are no explicit Linux/macOS examples or references to cross-platform alternatives for provisioning, scaling, or deleting resources.
Recommendations
  • Add explicit az CLI examples for all operations (provisioning, scaling, deleting) alongside PowerShell cmdlets.
  • Clarify that Az PowerShell cmdlets can be used on Linux/macOS via PowerShell Core, or provide links to relevant installation guides.
  • Where possible, mention ARM template usage with cross-platform deployment tools (e.g., Azure CLI, Bicep).
  • Ensure that guidance for managing Service Fabric resources is equally accessible to Linux/macOS users.
GitHub Create Pull Request
Service Fabric Describing Azure Service Fabric apps and services ...ic/service-fabric-application-and-service-manifests.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation is generally cross-platform, focusing on XML manifest structure and concepts. However, there is a notable bias in the warning that recommends using Visual Studio and a Windows file path to open the Service Fabric XSD schema for authoring manifests. This assumes the user is on Windows and using Visual Studio, with no mention of Linux or cross-platform alternatives. Additionally, the PowerShell module is mentioned as a way to create services, but no Linux/CLI equivalent is provided or referenced.
Recommendations
  • Provide guidance for Linux/macOS users on how to validate or edit Service Fabric manifest XML files, such as using VS Code (cross-platform) or other XML editors, and where to find the XSD schema on non-Windows systems.
  • When referencing PowerShell modules, also mention equivalent Azure CLI or REST API methods for creating services, if available.
  • Clarify whether the manifest authoring and validation steps are supported on Linux/macOS, and provide platform-agnostic instructions where possible.
GitHub Create Pull Request
Service Fabric Monitor Azure Service Fabric ...main/articles/service-fabric/monitor-service-fabric.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation generally covers both Windows and Linux clusters, but there are several areas where Windows tools and patterns are mentioned first or exclusively, and Linux equivalents are not always given equal prominence or detail. Windows-specific tools (such as EventStore APIs, Event Viewer, Diagnostics Agent) are described in detail, while Linux alternatives (such as Syslog, LTTng) are referenced but not explained or linked as thoroughly. Some example/tutorial links focus on Windows/.NET, and Linux-specific guidance is less visible.
Recommendations
  • Ensure Linux monitoring tools and patterns are described with equal detail and clarity as Windows equivalents.
  • Provide Linux-specific examples and tutorials, especially for cluster monitoring and application instrumentation.
  • Where Windows tools (e.g., Event Viewer, Diagnostics Agent) are mentioned, add corresponding Linux guidance (e.g., Syslog, LTTng, Linux agent configuration) and link to relevant documentation.
  • Avoid listing Windows tools or examples first unless there is a technical reason; alternate order or group by OS.
  • Add explicit Linux-focused sample queries and alert rules where possible.
GitHub Create Pull Request
Service Fabric RunToCompletion semantics and specifications ...blob/main/articles/service-fabric/run-to-completion.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page provides RunToCompletion semantics for Service Fabric containers and guest executables, but all code examples, container images, and tooling references are Windows-centric. Windows container images and Windows-specific commands (cmd, set, ping) are used exclusively, and PowerShell is the only CLI example for querying deployment status. No Linux container or Linux tooling examples are provided, nor is Linux compatibility discussed.
Recommendations
  • Add equivalent Linux container examples using popular Linux base images (e.g., Ubuntu, Alpine) and shell commands (bash, echo, ping).
  • Clarify whether RunToCompletion semantics are supported for Linux containers and guest executables, and provide explicit guidance for Linux users.
  • Include Linux CLI examples (e.g., using Bash or Azure CLI) for querying deployment status, or reference cross-platform tools.
  • Mention any limitations or differences in behavior between Windows and Linux environments for RunToCompletion.
  • If Linux support is limited, state this clearly at the top of the article.
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 there is a noticeable Windows bias. Windows-specific features (such as AD accounts, gMSA, BitLocker, and references to Windows standalone clusters) are discussed in detail, while Linux equivalents are either missing, mentioned only briefly, or flagged as TODOs. Examples and guidance for Linux users (e.g., disk encryption, user accounts, container security) are less comprehensive or absent.
Recommendations
  • Add explicit Linux examples for securing application data at rest (disk encryption) and clarify supported tools and patterns for Linux clusters.
  • Provide parity in user account and group management guidance for Linux clusters, including how to run services under different user accounts on Linux.
  • Include Linux-specific instructions and examples for certificate management and container security.
  • Ensure that all code snippets and configuration examples are applicable to both Windows and Linux, or provide separate examples for each platform.
  • Address the TODOs regarding disk encryption on Linux clusters with concrete guidance and links.
GitHub Create Pull Request
Service Fabric Application upgrade: upgrade parameters ...abric/service-fabric-application-upgrade-parameters.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page presents upgrade parameters for Service Fabric applications, but it displays a notable Windows bias. PowerShell and Visual Studio (Windows tools) are discussed first and in greater detail, with extensive parameter tables and explanations. SFCTL (the cross-platform CLI) is covered only after the Windows tools, and its section is less prominent and less detailed. There are no explicit Linux/macOS-specific examples or walkthroughs in the main content, though a Linux CLI tutorial is linked in 'Next steps'.
Recommendations
  • Reorganize the page to present SFCTL (cross-platform CLI) examples and parameters before or alongside PowerShell/Visual Studio, rather than after them.
  • Provide explicit Linux/macOS usage examples for SFCTL, including sample commands and parameter usage.
  • Clarify that SFCTL is the recommended tool for Linux/macOS users, and highlight its parity with PowerShell.
  • Add a comparison table showing which tools are available on which platforms.
  • Ensure that parameter explanations for SFCTL are as detailed as those for PowerShell/Visual Studio.
GitHub Create Pull Request
Service Fabric Advanced Application Upgrade Topics ...-fabric/service-fabric-application-upgrade-advanced.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page for advanced Service Fabric application upgrade topics relies heavily on PowerShell cmdlet examples (e.g., New-ServiceFabricService, Update-ServiceFabricService, Start-ServiceFabricApplicationUpgrade), which are Windows-centric. There are no equivalent examples or guidance for Linux/macOS users, such as using the Service Fabric CLI (sfctl) or REST APIs. The documentation also references Visual Studio for diff package upgrades, another Windows-first tool, and consistently presents Windows tools and patterns before any mention of cross-platform alternatives.
Recommendations
  • Add equivalent examples using the Service Fabric CLI (sfctl), which is cross-platform and supported on Linux/macOS.
  • Include REST API examples for relevant operations (e.g., creating/upgrading services, application upgrades).
  • Mention and link to documentation for Linux/macOS deployment workflows, including how to perform upgrades without PowerShell or Visual Studio.
  • Clarify which operations are possible on Linux clusters and provide guidance for Linux users where PowerShell/Visual Studio are not available.
  • Reorder sections or add notes to ensure Linux/macOS alternatives are presented alongside or before Windows-specific tools.
GitHub Create Pull Request
Service Fabric Application upgrade: data serialization ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-application-upgrade-data-serialization.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page provides links to application upgrade tutorials using Visual Studio and PowerShell, both of which are primarily Windows-centric tools. There are no explicit Linux/macOS examples or equivalent upgrade instructions using cross-platform tools (e.g., Azure CLI, Bash, or SDKs). The serialization guidance is focused on C# and .NET, but this is appropriate for Service Fabric workloads. However, the upgrade guidance implicitly prioritizes Windows tools.
Recommendations
  • Add upgrade instructions or links for Linux/macOS users, such as using Azure CLI, Bash scripts, or cross-platform SDKs.
  • Clarify whether PowerShell examples are compatible with PowerShell Core on Linux/macOS, or provide alternatives.
  • Consider including upgrade walkthroughs using Visual Studio Code (cross-platform) or other non-Windows IDEs.
  • Explicitly mention if Service Fabric application upgrades can be performed from Linux/macOS, and provide relevant guidance.
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: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation provides PowerShell-only examples and references to Windows-specific tools (e.g., http.sys), with no equivalent CLI or Linux-native commands. There are no Linux or cross-platform examples for performing Service Fabric application upgrades, which may hinder Linux/macOS users.
Recommendations
  • Add equivalent examples using Azure CLI or Service Fabric CLI (sfctl), which are cross-platform.
  • Explicitly mention if certain upgrade operations are only supported via PowerShell/Windows, and provide alternatives or workarounds for Linux users.
  • Clarify any Windows-only limitations (e.g., http.sys) and, where possible, suggest Linux-compatible approaches.
  • Include links to Linux/macOS-specific guidance for Service Fabric application management.
GitHub Create Pull Request
Service Fabric Restoring backup in Azure Service Fabric ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-backup-restore-service-trigger-restore.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page for restoring backup in Azure Service Fabric exclusively provides PowerShell-based examples and instructions, relying on the Microsoft.ServiceFabric.Powershell.Http module and Windows-specific tooling (e.g., PowerShell, certificate thumbprints, Windows-style paths). No Linux/macOS CLI, Bash, or cross-platform REST API examples are provided, nor is there guidance for Linux users on how to perform equivalent operations. The REST API is referenced, but only invoked via PowerShell, and there are no explicit instructions or code samples for using curl or other cross-platform tools.
Recommendations
  • Add cross-platform examples using Bash and curl for REST API calls, showing how to authenticate and trigger restore operations from Linux/macOS.
  • Document any prerequisites or limitations for Linux/macOS users, including how to obtain and use certificates for authentication.
  • Mention and link to any available Service Fabric CLI tools that work on Linux/macOS, or clarify if PowerShell is required.
  • Provide guidance for Linux users on installing PowerShell Core if it is required, and clarify compatibility.
  • Ensure REST API documentation is referenced with clear instructions for non-Windows environments.
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 emphasized for cluster upgrades and VM configuration. Windows-specific tools and registry keys are mentioned without Linux equivalents. Windows configuration examples and PowerShell commands are presented before or instead of Linux alternatives, creating friction for Linux users.
Recommendations
  • Include Linux-specific upgrade instructions and examples, such as using Bash or relevant Linux commands for cluster upgrades.
  • Provide Linux VM configuration examples alongside Windows registry and osProfile settings.
  • When referencing PowerShell, also show Bash or CLI alternatives for Linux clusters.
  • Clarify which steps are Windows-only and which are cross-platform, to help Linux users navigate the documentation.
  • Ensure parity by linking to Linux-specific resources and tutorials where appropriate.
GitHub Create Pull Request
Service Fabric On-demand backup in Azure Service Fabric ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-backup-restore-service-ondemand-backup.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page for on-demand backup in Azure Service Fabric is heavily focused on PowerShell-based workflows, with all code examples and module instructions provided exclusively for PowerShell. There are no Bash, CLI, or Linux/macOS-compatible examples or instructions, and PowerShell is presented as the default and only method for scripting and API calls. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer native tools.
Recommendations
  • Add equivalent examples using Azure CLI, Bash, or curl for REST API calls, making it clear how Linux/macOS users can perform the same operations.
  • Document prerequisites and installation steps for PowerShell Core (pwsh) on Linux/macOS, if PowerShell is required, and clarify any limitations.
  • Where possible, provide cross-platform guidance for connecting to Service Fabric clusters and triggering backups, including authentication methods compatible with Linux/macOS.
  • Explicitly state whether the Microsoft.ServiceFabric.Powershell.Http module is supported on PowerShell Core and non-Windows platforms, and offer alternatives if not.
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 is generally platform-neutral, focusing on Service Fabric's backup configuration concepts and REST API usage. However, in the 'File share' backup storage section, only Windows-style file share paths (\\StorageServer\BackupStore) and Windows authentication mechanisms are described. There are no examples or guidance for Linux-based file shares (e.g., SMB/CIFS mounts, NFS), nor is there mention of how Linux clusters might configure or access file shares. This creates a subtle but notable bias toward Windows environments.
Recommendations
  • Add examples and guidance for configuring file share backup storage using Linux-based clusters, including supported file share types (e.g., SMB/CIFS, NFS) and path formats.
  • Clarify whether Linux clusters can use file share backup storage, and if so, provide authentication and access instructions relevant to Linux.
  • If file share backup storage is Windows-only, explicitly state this limitation to inform Linux/macOS users.
  • Consider including both Windows and Linux path examples and authentication methods where applicable.
GitHub Create Pull Request
Service Fabric Change Azure Service Fabric cluster settings ...rvice-fabric/service-fabric-cluster-fabric-settings.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page provides a comprehensive reference for Service Fabric cluster settings, covering both Azure-hosted and standalone clusters. However, there is evidence of Windows bias: Windows terminology and tools (such as certificate store names like 'MY', 'LocalMachine', and references to NTLM authentication) are used throughout, and Windows-specific defaults are often mentioned before Linux equivalents. Some parameters and guidance reference Windows APIs (e.g., CertGetCertificateChain), and Windows-only features (like Windows Update integration) are present without clear Linux alternatives or parity. Linux-specific guidance is minimal, though some Linux settings are mentioned (e.g., LinuxExternalExecutablePath, EnforceLinuxMinTlsVersion).
Recommendations
  • Where Windows-specific terms (e.g., certificate store names, NTLM authentication) are used, add Linux equivalents or clarify Linux behavior.
  • Ensure Linux-specific settings are documented with equal detail and visibility, including certificate management, authentication, and file storage.
  • When referencing Windows APIs or tools, provide Linux alternatives or note if the feature is not applicable on Linux.
  • Add explicit notes or tables indicating which settings are platform-specific, and provide Linux/macOS guidance where possible.
  • Review default values and descriptions to ensure Linux defaults are equally clear and not overshadowed by Windows defaults.
GitHub Create Pull Request
Service Fabric Node types and virtual machine scale sets ...les/service-fabric/service-fabric-cluster-nodetypes.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page provides general information about Azure Service Fabric node types and virtual machine scale sets, but exhibits Windows bias in several areas. Examples and guidance reference Windows paths (e.g., 'D:\\SvcFab'), and the 'Next steps' section links to PowerShell scripts for Windows-specific tasks (changing RDP port ranges, admin username/password), without Linux or cross-platform alternatives. Linux-specific guidance is minimal, and Windows tools/patterns are mentioned first or exclusively.
Recommendations
  • Provide equivalent Linux/Bash examples for remote connection, port range changes, and admin credential updates.
  • Clarify when steps are Windows-only and offer Linux/macOS alternatives or links.
  • Use platform-neutral paths and examples where possible, or show both Windows and Linux variants.
  • Add guidance for managing Service Fabric clusters on Linux VM scale sets, including SSH access and Linux admin user management.
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 offering equivalent Linux/macOS CLI or REST API examples. While Service Fabric is cross-platform, the exclusive use of PowerShell in the example creates friction for Linux/macOS users who cannot use PowerShell natively.
Recommendations
  • Add equivalent examples using REST API or Service Fabric CLI (sfctl), which are cross-platform and supported on Linux/macOS.
  • Clearly indicate that PowerShell is Windows-specific and provide links or references to Linux/macOS-compatible tools.
  • Where possible, show REST or sfctl examples before or alongside PowerShell examples to improve parity.
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, but does not include equivalent Linux/macOS CLI examples (such as Azure CLI or Bash). PowerShell is presented as the only scripting interface, which is primarily used on Windows, and examples are consistently shown in PowerShell before any mention of cross-platform tools.
Recommendations
  • Add Azure CLI or Bash examples for configuring placement policies, as Service Fabric supports cross-platform management.
  • Explicitly mention if PowerShell examples are applicable on Linux/macOS (via PowerShell Core), or provide guidance for non-Windows users.
  • Consider including REST API or ARM template snippets for placement policy configuration, which are platform-agnostic.
  • Where possible, clarify any differences in configuration steps for Linux-based Service Fabric clusters.
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 ⚠ī¸ windows_first
Summary
The documentation provides a PowerShell example for querying Service Fabric partition health, using a Windows-style prompt and cmdlet. No equivalent Linux/macOS CLI example (such as Azure CLI or sfctl) is provided, and the example is presented early in the page. This creates friction for Linux/macOS users, as Service Fabric supports cross-platform management tools.
Recommendations
  • Add equivalent Linux/macOS examples using sfctl or Azure CLI for querying partition health.
  • Explicitly mention that PowerShell examples are for Windows, and provide links or instructions for Linux/macOS users.
  • Consider presenting cross-platform examples side-by-side, or defaulting to platform-neutral tools where possible.
GitHub Create Pull Request
Service Fabric Manage Azure Service Fabric app load using metrics ...ric/service-fabric-cluster-resource-manager-metrics.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides code examples for managing Service Fabric metrics primarily in C# and PowerShell. PowerShell is a Windows-centric tool, and no equivalent Linux/macOS CLI examples (such as Azure CLI or Bash) are provided. The PowerShell examples are given alongside C# code, but there is no mention of cross-platform tools or patterns, nor guidance for Linux users. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other tools.
Recommendations
  • Add Azure CLI examples for service creation and metric configuration, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Mention Bash scripting or REST API usage for metric management, providing sample commands or links to relevant documentation.
  • Explicitly state PowerShell's platform limitations and suggest alternatives for non-Windows environments.
  • Ensure that any references to tooling are inclusive of Linux/macOS users, or provide parity in examples.
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 and C# API examples for managing node tags and service tag requirements in Azure Service Fabric, but does not include equivalent examples for Linux/macOS users (e.g., Bash/CLI commands). PowerShell is presented first in each section, suggesting a Windows-centric approach. There is no mention of Linux tools or cross-platform CLI usage for these tasks.
Recommendations
  • Add Azure CLI or Bash examples for managing node tags and service tag requirements, if supported.
  • Clarify whether PowerShell commands are available cross-platform or Windows-only.
  • Mention any REST API endpoints or tools that can be used from Linux/macOS environments.
  • Consider presenting cross-platform methods (e.g., REST API, Azure CLI) before or alongside PowerShell examples.
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 consistently provides PowerShell examples for all operations, but does not mention or provide equivalent Linux/macOS command-line examples (such as Azure CLI or REST API usage). PowerShell is a Windows-centric tool, and its exclusive use creates friction for Linux/macOS users. The documentation also references Windows-specific tools (PowerShell cmdlets) without alternatives, and does not clarify whether these operations can be performed from non-Windows environments.
Recommendations
  • Add Azure CLI examples for all operations shown with PowerShell, as Azure CLI is cross-platform.
  • Mention REST API endpoints or SDK usage for Linux/macOS users where applicable.
  • Clarify whether PowerShell cmdlets can be used on Linux/macOS (via PowerShell Core), and provide installation guidance if so.
  • Explicitly state if certain operations are Windows-only, or provide links to Linux/macOS-compatible tooling.
  • Consider showing Azure CLI or REST API examples before PowerShell, or side-by-side, to emphasize cross-platform parity.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager: Movement cost ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-movement-cost.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides PowerShell examples for configuring move cost, but does not include equivalent Linux CLI or bash 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, reinforcing a Windows-first pattern. There is no mention of Linux-native tools or cross-platform CLI alternatives for Service Fabric management.
Recommendations
  • Add Azure CLI or Service Fabric CLI (sfctl) examples for move cost configuration and updates, as these are cross-platform and usable on Linux/macOS.
  • Explicitly note if certain operations are only possible via PowerShell, and provide guidance for Linux users if so.
  • Consider presenting cross-platform CLI examples before or alongside PowerShell to improve parity.
  • Clarify any limitations or differences for Linux/macOS users in a dedicated section.
GitHub Create Pull Request
Service Fabric Service sensitivity ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-sensitivity.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides configuration examples using XML, JSON, PowerShell, and C#. PowerShell is used extensively for service creation and updates, but there are no equivalent CLI or Bash examples for Linux/macOS users. PowerShell examples are presented before C# API examples, and no mention is made of cross-platform tools or commands (e.g., Azure CLI, Bash scripts) for managing Service Fabric clusters. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other tooling.
Recommendations
  • Add Azure CLI or Bash examples for service sensitivity and maximum load configuration, where possible.
  • Clarify whether PowerShell commands are supported on Linux/macOS (via PowerShell Core), and provide guidance if so.
  • Consider including REST API examples for service management, which are platform-neutral.
  • Explicitly state if certain operations are Windows-only, or provide links to Linux/macOS alternatives if available.
GitHub Create Pull Request
Service Fabric Secure an Azure Service Fabric cluster ...cles/service-fabric/service-fabric-cluster-security.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page covers securing Azure Service Fabric clusters and references both Azure-hosted and standalone Windows clusters. However, it consistently provides explicit guidance and links for Windows standalone clusters, while omitting equivalent instructions or links for standalone Linux clusters. Windows security (Kerberos) is discussed in detail, but there is no mention of Linux authentication mechanisms or how to secure standalone Linux clusters. Certificate creation is described with a Windows-centric focus, referencing Windows Server certificate services and tools like MakeCert.exe, with no Linux alternatives or guidance. The overall pattern is Windows-first, with Linux standalone scenarios largely missing.
Recommendations
  • Add explicit sections or links for securing standalone Linux Service Fabric clusters, including certificate setup and authentication options.
  • Provide Linux-specific examples for certificate creation and management (e.g., using OpenSSL or Linux CA tools).
  • Clarify which security scenarios and recommendations apply equally to Linux clusters, and highlight any differences.
  • Include guidance for Linux client authentication and node-to-node security, or state if Linux standalone clusters are not supported.
GitHub Create Pull Request
Service Fabric Azure Service Fabric standalone cluster scaling ...ce-fabric/service-fabric-cluster-scaling-standalone.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page for scaling Azure Service Fabric standalone clusters demonstrates a Windows bias. It references PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) and links to further instructions that appear Windows-specific. There are no Linux-specific examples, tools, or guidance, and the terminology and tooling are focused on Windows environments.
Recommendations
  • Add equivalent Linux instructions and examples, such as using Service Fabric CLI (sfctl) or REST APIs for cluster management.
  • Explicitly mention whether standalone clusters can be managed from Linux/macOS, and provide guidance if so.
  • Include links to Linux/macOS documentation or clarify if the process is Windows-only.
  • If PowerShell is required, note any cross-platform alternatives or limitations.
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 on upgrading an Azure Service Fabric standalone cluster demonstrates a Windows bias. It consistently links to Windows-specific guides (e.g., 'service-fabric-cluster-upgrade-windows-server.md', 'service-fabric-cluster-config-upgrade-windows-server.md') and references the Patch Orchestration Application only for Windows. There are no Linux-specific instructions, examples, or links, and the documentation does not clarify if Linux standalone clusters are supported or provide guidance for them.
Recommendations
  • Clarify early in the article whether standalone clusters are Windows-only, or explicitly state Linux support status.
  • If Linux standalone clusters are supported, provide equivalent upgrade and configuration instructions, or link to Linux-specific guides.
  • Reference or document the Patch Orchestration Application (POA) for Linux if available, or clarify its absence.
  • Where possible, use neutral language and examples, or present Linux and Windows options side by side.
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 provides code examples and administrative instructions primarily in PowerShell and C#, both of which are more closely associated with Windows environments. There are no equivalent Linux CLI or scripting examples (e.g., Bash, Azure CLI) for scaling operations. Windows tools and patterns (PowerShell cmdlets) are mentioned exclusively and before any Linux alternatives, which are absent. While the page does acknowledge platform differences, the practical guidance is Windows-centric.
Recommendations
  • Add Linux-specific examples for scaling operations, such as using Bash scripts or Azure CLI commands.
  • Include instructions or references for managing Service Fabric clusters on Linux, especially for tasks currently shown only in PowerShell.
  • Present code samples for both Windows and Linux platforms, or clarify when a sample is Windows-only.
  • Mention Linux administrative tools or patterns alongside PowerShell cmdlets, such as systemd or relevant Linux cluster management commands.
GitHub Create Pull Request
Service Fabric Azure Service Fabric DNS service ...n/articles/service-fabric/service-fabric-dnsservice.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides PowerShell examples for setting DNS names, references ApplicationManifest.xml (a Windows-centric deployment artifact), and does not offer equivalent Linux CLI or scripting examples (e.g., Bash, Azure CLI). Windows tools and patterns (PowerShell, Visual Studio) are mentioned before or instead of Linux alternatives. Linux limitations are noted, but Linux-centric workflows are not demonstrated.
Recommendations
  • Add Azure CLI or Bash examples for setting DNS names and managing Service Fabric services, especially for Linux clusters.
  • Include guidance for Linux users on editing deployment artifacts (e.g., Docker Compose, YAML) and deploying services without ApplicationManifest.xml.
  • Clarify how Linux users can enable DNS service (since portal is not supported), with step-by-step instructions using ARM templates or Azure CLI.
  • Mention and show Linux-friendly editors (e.g., VS Code) instead of only Visual Studio.
  • Provide explicit examples or links for containerized service deployments on Linux clusters.
GitHub Create Pull Request
Service Fabric Upgrading Azure Service Fabric clusters ...icles/service-fabric/service-fabric-cluster-upgrade.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides general guidance on upgrading Azure Service Fabric clusters, but there is a subtle Windows bias. References to PowerShell and Azure CLI are made for certificate management and port configuration, but Linux equivalents (such as Bash or Linux-specific CLI usage) are not explicitly mentioned. The section on OS image upgrades links only to Windows-specific patching guidance, suggesting Windows as the primary platform. However, most upgrade instructions are platform-agnostic, and no critical steps are Windows-only.
Recommendations
  • Explicitly mention that Azure CLI commands can be run from Bash on Linux/macOS, not just PowerShell.
  • Add examples or links for Linux/macOS users where PowerShell is referenced, such as using Azure CLI in Bash.
  • Provide guidance or links for patching cluster nodes running Linux OS images, if supported.
  • Clarify which features or steps are Windows-only and which are cross-platform, to avoid confusion.
GitHub Create Pull Request
Service Fabric Learn more about Azure Service Fabric ...icles/service-fabric/service-fabric-content-roadmap.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides a broad overview of Azure Service Fabric, which supports both Windows and Linux. However, there are several instances where Windows-specific tools, services, and examples are mentioned first or exclusively. For example, references to 'FabricHost.exe' as an auto-start Windows service, standalone cluster creation only for Windows, and frequent mention of PowerShell cmdlets without equal prominence for Linux equivalents. Linux support is acknowledged, but Linux-specific instructions, tools, and examples are often missing or secondary.
Recommendations
  • Provide Linux-specific examples and instructions alongside Windows ones, especially for cluster setup, management, and health monitoring.
  • Mention Linux CLI tools (such as sfctl) and bash scripts with equal prominence to PowerShell.
  • Clarify which features are Windows-only and which are cross-platform, linking to the differences page where relevant.
  • Add explicit guidance for Linux users in sections where only Windows tools or workflows are described.
  • Ensure that references to Windows executables (e.g., FabricHost.exe) are accompanied by Linux equivalents or notes about platform differences.
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 primarily references Windows-specific event logging mechanisms (ETW/Windows Event logs, Windows Azure diagnostics agent) and tools, without mentioning Linux equivalents or providing Linux-specific guidance. Windows tools and patterns are discussed first and exclusively, creating friction for Linux cluster administrators.
Recommendations
  • Explicitly mention how Service Fabric events are logged and accessed on Linux clusters, including any differences in event channels, logging mechanisms, or monitoring tools.
  • Provide examples or references for accessing Service Fabric events on Linux (e.g., using syslog, journald, or Azure Monitor integration for Linux nodes).
  • Clarify whether the Azure diagnostics agent and event logging methods are applicable to Linux clusters, and if not, suggest Linux-compatible alternatives.
  • Ensure parity in guidance and examples for both Windows and Linux Service Fabric clusters.
GitHub Create Pull Request
Service Fabric Package an existing executable to Azure Service Fabric ...abric/service-fabric-guest-executables-introduction.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits mild Windows bias. It references Visual Studio as a packaging tool and provides a path to the Service Fabric SDK schema in a Windows directory (C:\Program Files\...), without mentioning Linux/macOS equivalents or alternatives. There are no explicit Linux/macOS examples or guidance, and the directory structure example uses a Windows executable (.exe), which may imply Windows-centric usage.
Recommendations
  • Add explicit instructions or examples for packaging and deploying guest executables on Linux/macOS, including references to relevant tools and SDK locations.
  • Mention cross-platform command-line utilities and their usage for packaging and deployment, not just Visual Studio.
  • Provide sample directory structures and file naming conventions that are platform-agnostic (e.g., using .sh or .out for Linux executables alongside .exe).
  • Clarify whether the Service Fabric SDK and schema files are available on Linux/macOS, and if so, provide their typical installation paths.
GitHub Create Pull Request
Service Fabric Azure Service Fabric hosting model ...rticles/service-fabric/service-fabric-hosting-model.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides PowerShell-based command-line examples for creating services with the Exclusive Process model, but does not include equivalent examples for Linux environments (e.g., Azure CLI, Bash, or Service Fabric CLI). The only command-line example is PowerShell, and the documentation refers to PowerShell cmdlets for management tasks, which are Windows-centric. There is no mention of Linux tools or workflows, nor are Linux/macOS equivalents shown or referenced.
Recommendations
  • Add Azure CLI or Service Fabric CLI (sfctl) examples for creating and managing services, especially for commands currently only shown in PowerShell.
  • Explicitly mention Linux/macOS support and provide guidance or links for non-Windows users.
  • Where PowerShell cmdlets are referenced, provide equivalent REST API or CLI commands, or at least note their availability.
  • Consider adding a short section or callout clarifying cross-platform management options for Service Fabric clusters.
GitHub Create Pull Request
Service Fabric Azure Service Fabric image store connection string ...fabric/service-fabric-image-store-connection-string.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation references PowerShell as the primary example for interacting with Service Fabric clusters (e.g., retrieving the cluster manifest), and links to a PowerShell-based deployment guide as the next step. While .NET and REST are mentioned, PowerShell is presented first and most prominently. There are no explicit Linux or cross-platform CLI examples (such as Azure CLI or Bash), nor is there mention of Linux tooling or workflows.
Recommendations
  • Add Azure CLI or Bash examples for retrieving the cluster manifest and deploying applications, highlighting cross-platform approaches.
  • Mention Linux/macOS compatibility for Service Fabric tooling where applicable.
  • Provide links to documentation or guides for Linux users, such as using Service Fabric CLI (sfctl) or REST APIs from non-Windows environments.
  • Balance example ordering so that PowerShell is not always presented first, or clarify that PowerShell is just one option.
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 is notably Windows-centric: all manifest examples are based on a Windows Server 2016 container sample, and several explanations reference Windows-specific tools (e.g., 'winver' for OS build detection). There is little to no mention of Linux container scenarios, and no Linux-specific manifest examples or guidance are provided, despite Service Fabric supporting Linux containers.
Recommendations
  • Add parallel manifest examples based on a Linux container sample, or clarify which elements differ for Linux containers.
  • When referencing OS build detection, include Linux equivalents (e.g., 'uname -r' or '/etc/os-release') alongside Windows instructions.
  • Explicitly call out any settings or patterns that are Windows-only, and provide Linux alternatives or note when features are cross-platform.
  • Update references to file paths (e.g., 'c:\VolumeTest\Data') to include Linux-style paths or clarify platform-specific differences.
  • Where PowerShell or Windows command-line tools are mentioned, provide equivalent Linux shell commands if applicable.
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 ⚠ī¸ powershell_heavy
Summary
The documentation covers both Kestrel (cross-platform) and HTTP.sys (Windows-only) for ASP.NET Core in Service Fabric. However, HTTP.sys (a Windows-only web server) is described in detail and presented before Kestrel in several sections, with extensive configuration and code examples. The documentation also references Windows-specific tools (e.g., netsh) and concepts (e.g., Windows HTTP Server API, kernel driver) without always providing Linux/macOS equivalents or clarifying cross-platform alternatives early. While Kestrel is ultimately recommended for cross-platform scenarios, the ordering and depth of HTTP.sys coverage may create friction for Linux/macOS users.
Recommendations
  • Move Kestrel (cross-platform) guidance and examples before HTTP.sys (Windows-only) in all sections, making it the default/primary path.
  • Explicitly call out HTTP.sys as Windows-only at the start of relevant sections, and direct Linux/macOS users to Kestrel.
  • Where Windows-specific tools (e.g., netsh) or configuration are mentioned, clarify that these are not applicable to Linux/macOS and provide alternative guidance or state 'not required on Linux/macOS'.
  • Add a short summary table or decision tree at the top to help users quickly choose the correct web server for their OS.
  • Ensure all critical code/configuration examples are shown for Kestrel first, and only then for HTTP.sys as a Windows-specific option.
GitHub Create Pull Request
Service Fabric Reliable services app manifest examples ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-manifest-example-reliable-services-app.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides Service Fabric application and service manifest examples, but the examples and descriptions are implicitly Windows-centric. Batch scripts (.bat), references to Windows accounts (NetworkService, Administrators), and mentions of ServiceFabric PowerShell module are present, with no Linux-specific equivalents or guidance. There are no examples or notes for Linux clusters, nor for using shell scripts or Linux user/group patterns. This creates friction for Linux users, though the content is not strictly Windows-only.
Recommendations
  • Add Linux-specific examples, such as using shell scripts (.sh) in SetupEntryPoint and EntryPoint elements.
  • Clarify which manifest features and account types are supported on Linux clusters, and provide guidance for Linux user/group configuration.
  • Mention and provide examples for Linux deployment tools (e.g., Azure CLI, sfctl) alongside or before Windows/PowerShell references.
  • Explicitly note any cross-platform differences in supported features (e.g., RunAsPolicy, account types, endpoint configuration) and link to relevant Linux documentation.
GitHub Create Pull Request
Service Fabric Replica soft delete for enhanced data protection in Service Fabric ...s/service-fabric/service-fabric-replica-soft-delete.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page for 'Replica soft delete 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 or cross-platform tooling. There are no examples or guidance for Linux/macOS users, and the documentation assumes familiarity with Windows/PowerShell tools.
Recommendations
  • Include equivalent examples using cross-platform Service Fabric CLI (sfctl) commands where available.
  • Explicitly mention whether the described PowerShell cmdlets are available or not on Linux/macOS, and provide alternative instructions if possible.
  • Add notes or links for Linux/macOS users on how to perform the same operations (e.g., using REST APIs, sfctl, or SDKs in other languages).
  • Clarify any platform limitations if the APIs or features are only available on Windows.
GitHub Create Pull Request
Service Fabric Define Service Configuration in StartupServices.xml for a Service Fabric Application ...service-fabric/service-fabric-startupservices-model.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation is heavily focused on Visual Studio workflows and Windows-centric development patterns for Service Fabric applications. All examples and instructions reference Visual Studio features (Build/Rebuild/F5/Ctrl+F5/Publish), which are only available on Windows. There are no Linux/macOS equivalents or guidance for cross-platform development, and no mention of alternative tooling or workflows for non-Windows users.
Recommendations
  • Add explicit guidance for Linux/macOS users, including how to manage service configuration without Visual Studio.
  • Provide examples or references for command-line tools (e.g., Azure CLI, Service Fabric CLI, PowerShell Core) that work on Linux/macOS for deploying and configuring Service Fabric applications.
  • Clarify which parts of the workflow are Windows-only and offer alternative approaches for cross-platform scenarios.
  • Mention any limitations or differences for Linux/macOS users in the context of StartupServices.xml and Service Fabric SDK usage.
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 examples (such as Bash, Azure CLI, or cross-platform tools). PowerShell is presented as the primary scripting interface, and Windows-style command prompts are used. REST and API options are mentioned, but scripting and command-line guidance is Windows-centric.
Recommendations
  • Add cross-platform CLI examples using Azure CLI or Bash scripts for health reporting.
  • Clarify whether PowerShell examples are usable on Linux/macOS (PowerShell Core), and provide guidance for those platforms.
  • Mention and demonstrate any available Linux-native Service Fabric CLI tools (e.g., sfctl) for health reporting.
  • Explicitly note platform support for each method (API, PowerShell, REST) and highlight Linux/macOS options where available.
GitHub Create Pull Request
Service Fabric Specifying Service Fabric service endpoints ...ce-fabric/service-fabric-service-manifest-resources.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides a PowerShell example for deploying Service Fabric applications, which is Windows-centric. The Service Fabric tooling and SDK path references are Windows-first (e.g., C:\Program Files\Microsoft SDKs\Service Fabric\schemas\...), and the PowerShell deployment example is given without a Linux equivalent. While there is a brief mention of Linux clusters regarding certificate storage, Linux deployment patterns and CLI examples are missing.
Recommendations
  • Add equivalent Linux deployment instructions and examples, such as using Azure CLI or Service Fabric CLI (sfctl) for application deployment.
  • Mention the Linux SDK/schema location alongside the Windows path.
  • Provide cross-platform guidance for endpoint configuration and certificate management.
  • Ensure that all PowerShell examples are accompanied by Linux/macOS alternatives.
GitHub Create Pull Request
Service Fabric Fault Analysis Service overview .../service-fabric/service-fabric-testability-overview.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page provides usage instructions for the Fault Analysis Service in Service Fabric, referencing C# and PowerShell as the primary ways to interact with the service. PowerShell is a Windows-centric tool, and no Linux or cross-platform CLI examples (such as Bash, Azure CLI, or REST API usage) are provided. There is no mention of Linux tooling or patterns, nor are Linux-specific instructions or parity considerations discussed.
Recommendations
  • Add examples for using the Fault Analysis Service from Linux/macOS environments, such as via Azure CLI, Bash scripts, or REST API calls.
  • Clarify whether the Fault Analysis Service APIs can be accessed from non-Windows platforms and provide guidance for those scenarios.
  • If PowerShell Core (cross-platform) is supported, specify this and provide relevant examples.
  • Include information about any limitations or differences when using Service Fabric and Fault Analysis Service on Linux clusters.
GitHub Create Pull Request
Virtual Machines Associate a virtual machine to a capacity reservation group .../virtual-machines/capacity-reservation-associate-vm.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides examples for both Windows and Linux VMs, but there are several areas of Windows bias. PowerShell examples are given equal prominence to Azure CLI, but PowerShell is a Windows-centric tool. The ARM template example is exclusively for Windows Server images, with no Linux image option shown. The portal instructions reference password complexity requirements typical for Windows, and the ARM template parameters and allowed values are all Windows versions. Linux-specific examples (e.g., ARM template for Ubuntu or Red Hat) are missing, and Windows terminology/tools (PowerShell, Windows images) are mentioned before or instead of Linux equivalents.
Recommendations
  • Add ARM template examples for Linux VM images (e.g., Ubuntu, CentOS, Red Hat) alongside the Windows template.
  • In portal instructions, clarify password requirements for Linux VMs (e.g., SSH key option, username restrictions).
  • Ensure CLI and PowerShell examples show both Windows and Linux image creation, or clarify that the example is for a Linux VM when using Ubuntu.
  • In ARM template parameters, include allowed values for popular Linux distributions.
  • Where PowerShell is used, note that it is primarily for Windows users, and suggest Bash/CLI for Linux/macOS users.
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 tools (Hyper-V, PowerShell Convert-VHD), presents Windows/Hyper-V steps first, and lacks parity for Linux-native workflows (e.g., creating/converting VHDs on Linux). Linux users are left without clear guidance for key steps such as VHD creation/conversion, making the process notably Windows-centric.
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 preparing VHDs, not just referencing Windows/WSL.
  • Mention and link to Linux virtualization solutions (e.g., KVM, VirtualBox) alongside Hyper-V.
  • Reorganize sections so Linux-native workflows are presented before or alongside Windows/Hyper-V options.
  • Clarify which steps are platform-agnostic and which are Windows-specific, and provide alternatives where possible.
GitHub Create Pull Request
Virtual Machines Create an Azure Image Builder Bicep file or ARM template JSON template .../articles/virtual-machines/linux/image-builder-json.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides both Windows and Linux examples for Azure Image Builder, but there is a notable Windows bias in several areas. PowerShell is frequently referenced for checksum generation and image operations, often before Linux equivalents. Windows-specific customizers (PowerShell, WindowsRestart, WindowsUpdate) are described in detail, while Linux customizers (Shell) are covered but less prominently. Windows tools and commands (e.g., PowerShell cmdlets, Sysprep) are mentioned first or exclusively in some sections, and instructions for generating checksums or performing operations often default to Windows/PowerShell before Linux alternatives.
Recommendations
  • Ensure Linux (bash/terminal) examples are provided alongside PowerShell examples for all operations, especially checksum generation and image template operations.
  • Present Linux and Windows examples with equal prominence, alternating which is shown first or grouping by OS.
  • Add more detailed Linux-specific guidance for customizers and validations, matching the depth given to Windows customizers.
  • Where possible, reference cross-platform tools (e.g., Azure CLI) before platform-specific tools (e.g., PowerShell).
  • Clarify in each section which features are Windows-only and which are cross-platform to avoid confusion.
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: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
While the documentation is focused on Linux VMs and provides comprehensive Azure CLI examples (which are cross-platform), the PowerShell section is disproportionately detailed, with many more examples and advanced usage patterns than the CLI section. Additionally, several PowerShell examples reference Windows-specific tools (e.g., ipconfig, .ps1 scripts, and Windows-specific parameter handling) and sometimes use Windows-centric terminology or defaults. REST API and ARM template examples also default to PowerShell/Windows script snippets (e.g., Write-Host, .ps1 files) rather than bash or sh scripts, despite the Linux focus. In some cases, Windows usage is described before Linux, or only Windows behaviors are explained in detail.
Recommendations
  • Expand the Azure CLI section to include all advanced scenarios currently only covered in PowerShell (e.g., using script URIs, output/error blob streaming, parameters, running as a different user, scale set commands, etc.).
  • Ensure REST API and ARM template examples use bash/sh scripts (e.g., echo Hello World!) rather than PowerShell (.ps1) scripts, or provide both Linux and Windows script examples where appropriate.
  • When referencing built-in command IDs or parameter handling, clearly distinguish Linux and Windows behaviors, and provide Linux-first explanations and examples.
  • Avoid using Windows-specific command IDs (e.g., ipconfig) or clarify their Linux equivalents (e.g., ifconfig or ip).
  • Balance the depth of PowerShell and CLI coverage, ensuring Linux users can accomplish all tasks without needing to translate from PowerShell/Windows-centric instructions.
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 Windows development and tools (Visual Studio, PowerShell) before Linux equivalents (Eclipse, Yeoman), but provides parity in describing both environments. No Windows-only tools or examples are given exclusively, and Linux support is clearly acknowledged.
Recommendations
  • Consider listing Linux development options before or alongside Windows options to avoid subtle ordering bias.
  • Add explicit links to Linux quickstart guides or examples in the 'Next steps' section, not just Windows/.NET quickstart.
  • Ensure that all referenced guides (e.g., quickstart) have Linux equivalents easily discoverable.
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 Azure Service Fabric Reliable Collections serialization concepts and .NET code examples. However, in the 'Next steps' section, Windows-centric tools (Visual Studio and PowerShell) are mentioned before any Linux/macOS alternatives, and no Linux-native upgrade tooling is referenced. There are no Linux-specific examples or guidance, which may create minor friction for non-Windows users.
Recommendations
  • Add links or references to Linux/macOS-compatible upgrade tools, such as Azure CLI or Service Fabric CLI (sfctl), in the 'Next steps' section.
  • Include examples or guidance for performing application upgrades on Linux-based Service Fabric clusters.
  • Clarify that the serialization concepts and code samples are applicable across platforms, and note any platform-specific differences 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 major operations (attach, detach, move VMs), but PowerShell examples are always present and shown alongside CLI. PowerShell is a Windows-centric tool, and its inclusion in every section, with detailed parameters, creates a mild Windows bias. Additionally, PowerShell examples are sometimes more detailed than their CLI counterparts. However, the Azure CLI is cross-platform and is included throughout, ensuring Linux/macOS users can complete all tasks. There are no Windows-only tools or patterns, and no critical steps are Windows-exclusive.
Recommendations
  • Ensure Azure CLI examples are as detailed as PowerShell examples, including all relevant parameters.
  • Consider listing Azure CLI examples before PowerShell examples, or clarifying that Azure CLI is recommended for cross-platform use.
  • Add a brief note explaining that Azure CLI works on Linux/macOS/Windows, while PowerShell is primarily for Windows users.
  • If possible, provide Bash script examples for advanced scenarios, or link to Azure CLI scripting guides for Linux users.
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 PowerShell examples are consistently shown alongside CLI and portal, and are often detailed. While Azure CLI is cross-platform, PowerShell is primarily used on Windows, and its inclusion may signal a Windows bias. However, Linux/macOS users can fully use the Azure CLI and ARM templates, and no critical functionality is Windows-only. The ordering sometimes puts PowerShell after CLI, but both are always present.
Recommendations
  • Clarify that Azure CLI is fully cross-platform and recommended for Linux/macOS users.
  • Consider adding brief notes for Linux/macOS users, e.g., 'Azure CLI commands can be run on Linux, macOS, and Windows.'
  • If possible, include Bash shell script examples for common tasks, or link to Azure CLI Bash usage guides.
  • Ensure that PowerShell is not presented as the default or primary method, but as an alternative for Windows users.
  • Explicitly mention that all features are available via CLI and ARM templates, regardless of OS.
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 creating an Azure Compute Gallery using the Azure Portal, Azure CLI, PowerShell, and REST API. While all major cross-platform tools are covered, the PowerShell example is given equal prominence alongside CLI and REST, and the ordering of examples sometimes places PowerShell before REST. However, the CLI examples (which are cross-platform) are present and complete. There is no evidence of exclusive Windows tooling or missing Linux/macOS examples, but PowerShell is included as a first-class option, which may be unnecessary for Linux/macOS users.
Recommendations
  • Consider listing Azure CLI examples before PowerShell examples, as CLI is cross-platform and more relevant for Linux/macOS users.
  • Explicitly note that PowerShell is primarily for Windows users, and recommend Azure CLI for Linux/macOS.
  • Ensure that all CLI examples are as detailed as PowerShell examples.
  • If possible, add Bash scripting examples for Linux users, or clarify that Azure CLI commands can be run in Bash.
GitHub Create Pull Request
Service Fabric Describe a cluster by using Cluster Resource Manager ...ce-fabric-cluster-resource-manager-cluster-description.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides configuration examples for both Windows (ClusterManifest.xml) and cross-platform/standalone (ClusterConfig.json) deployments. However, Windows-specific configuration (ClusterManifest.xml under <WindowsServer>) is presented first and in greater detail, and PowerShell examples are included for service creation and updates, with no Linux CLI or bash equivalents. The documentation references WindowsServer in the infrastructure example, which may create a perception of Windows preference, though it also covers standalone (non-Windows) deployments.
Recommendations
  • Add explicit Linux/macOS CLI examples (e.g., using Azure CLI or bash scripts) for service creation and updates alongside PowerShell.
  • Clarify that ClusterConfig.json applies to both Windows and Linux standalone clusters, and provide examples for Linux node configuration if applicable.
  • Consider presenting cross-platform configuration examples (ClusterConfig.json) before or alongside Windows-specific (ClusterManifest.xml) examples.
  • Mention any Linux-specific considerations or differences in Service Fabric cluster setup, if relevant.
  • If PowerShell is shown, also show equivalent Azure CLI or bash commands for parity.
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, Windows-specific tools and scenarios (such as IIS lift-and-shift and Mirantis Container Runtime) are mentioned in detail, and Windows container examples and links are often presented before or alongside Linux equivalents. The IIS scenario is Windows-only, but this is appropriate given its nature. Overall, Linux support is present and referenced, but Windows tools and examples are slightly more prominent.
Recommendations
  • Ensure Linux container examples and tutorials are given equal prominence and placement as Windows examples.
  • Add more Linux-specific scenarios (e.g., Apache/Nginx lift-and-shift, Linux-based guest executables) alongside Windows scenarios.
  • Clarify when certain features or tools are Windows-only to avoid confusion for Linux users.
  • Consider alternating the order of Windows and Linux links/examples to avoid 'windows_first' bias.
GitHub Create Pull Request
Service Fabric Learn Azure Service Fabric terminology ...es/service-fabric/service-fabric-technical-overview.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation page exhibits mild Windows bias. Windows-specific terminology and tools (such as references to Windows services and EXE/DLL files) are mentioned first or exclusively in several sections, especially in the infrastructure concepts and code package descriptions. The explanation of node startup references Windows services and executables without mentioning Linux equivalents or startup patterns. However, Linux is acknowledged in some places (e.g., Docker containers on Linux, guest executables), and the development cluster is noted as available on Windows, Linux, or Mac.
Recommendations
  • Add Linux-specific details alongside Windows descriptions, such as how Service Fabric nodes start on Linux (e.g., systemd services, relevant Linux processes).
  • When describing code packages, mention typical Linux executable formats (e.g., ELF binaries) and clarify that EXE/DLL is Windows-specific.
  • Where Windows services or tools are referenced, provide Linux equivalents or note differences in cluster/node management.
  • Ensure examples and terminology are presented in a platform-neutral way, or explicitly call out platform-specific differences.
  • Consider alternating the order of Windows and Linux mentions to avoid 'windows_first' bias.
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 are consistently presented alongside or immediately after CLI examples, and in some cases, the PowerShell extension used is 'ApplicationHealthWindows', which may be confusing for Linux users. The documentation does not provide Linux shell-specific examples (e.g., Bash scripts), but since Azure CLI is cross-platform, Linux users are not blocked. There is a slight bias in the ordering and in the PowerShell-centric explanations, but Linux parity is largely maintained.
Recommendations
  • Clarify in PowerShell examples when the extension is for Windows VMs and provide the correct extension name for Linux VMs if different.
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and recommend CLI for cross-platform usage.
  • Consider providing a Bash script example for end-to-end automation on Linux.
  • In PowerShell examples, mention that PowerShell Core is available cross-platform, or clarify if examples require Windows PowerShell.
  • Ensure that the Application Health extension example in PowerShell uses 'ApplicationHealthLinux' when the VM image is Linux, to avoid confusion.
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: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides Azure CLI and Resource Graph examples, but does not explicitly show Linux-specific commands or mention Linux tools. The only CLI example uses Azure CLI, which is cross-platform, but the documentation does not clarify that it works on Linux/macOS. The mention of Azure Site Recovery 'via PowerShell' in the backup table could imply a Windows bias, as PowerShell is traditionally Windows-centric, though PowerShell Core is cross-platform. There are no explicit Linux/macOS examples or references, and Windows is mentioned first in some contexts (e.g., 'Mix operating systems | Yes, Linux and Windows can reside...').
Recommendations
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows.
  • Add explicit Linux/macOS command examples where relevant (e.g., bash syntax, shell environment setup).
  • For features like Azure Site Recovery, specify if PowerShell Core is supported on Linux/macOS, or provide equivalent Azure CLI examples.
  • Ensure parity in mentioning operating systems (e.g., 'Linux and Windows' instead of 'Windows and Linux').
  • Where VM extensions or health monitoring are discussed, note any OS-specific requirements or differences.
GitHub Create Pull Request
Virtual Machine Scale Sets Create an Azure scale set that uses Availability Zones ...s/virtual-machine-scale-sets-use-availability-zones.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for creating and updating scale sets with Availability Zones. However, PowerShell examples are given equal prominence to CLI, and in some sections (such as 'Update scale set to add availability zones'), PowerShell is presented immediately after CLI and before REST API. The CLI examples are cross-platform, but PowerShell is Windows-centric. There are no explicit Linux/macOS shell examples (e.g., Bash), and the documentation does not mention Linux-specific tools or patterns. The ARM template section references both Linux and Windows getting started articles, but does not provide explicit Linux shell commands.
Recommendations
  • Add Bash shell examples alongside PowerShell, especially for update operations.
  • Explicitly note that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Consider reordering examples to show CLI first, then PowerShell, to reinforce cross-platform parity.
  • Add clarifying notes for Linux/macOS users where PowerShell is referenced, suggesting CLI as the alternative.
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. In some sections, PowerShell examples are more detailed or appear before CLI equivalents. Portal instructions are also included, but there is a slight tendency to present Windows-oriented tools first. No critical features are Windows-only, and Linux parity is generally maintained.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and preferred by Linux/macOS users.
  • Ensure CLI and PowerShell examples are equally detailed and comprehensive.
  • Where possible, explicitly mention that Azure CLI works on Linux/macOS and provide bash-friendly syntax.
  • Add brief notes clarifying that PowerShell is available cross-platform, but CLI is native to Linux/macOS.
  • Review tab order in tabbed content to ensure CLI is not always after PowerShell.
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/PowerShell tools and patterns are mentioned or shown first, and Windows-specific extension types (ApplicationHealthWindows) are used in sample code. The PowerShell section is detailed and prominent, and Windows extension types are used in REST and PowerShell examples, while Linux types are only referenced in CLI. Overall, Linux parity is mostly present, but Windows bias is evident in ordering and sample emphasis.
Recommendations
  • Ensure Linux and Windows examples are presented in parallel, or alternate which is shown first in each section.
  • Explicitly show both ApplicationHealthLinux and ApplicationHealthWindows extension types in all relevant sample code (REST, PowerShell, CLI).
  • Add more Linux-specific troubleshooting and verification steps, such as systemd or firewall configuration examples.
  • Clarify in each example which OS it targets, and provide equivalent Linux and Windows instructions for all steps.
  • Consider adding macOS-specific notes where relevant, especially for Bash/Python scripts.
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 (bash/shell) and PowerShell examples for creating instant access snapshots, but PowerShell is presented immediately after CLI and before Resource Manager Template and Portal instructions. There are no Linux-specific tools or patterns mentioned, but the ordering of examples (CLI, PowerShell, Portal, ARM) may subtly prioritize Windows users. All CLI examples use bash syntax, which is cross-platform, but PowerShell is highlighted as a separate tab, which may reinforce Windows-centric workflows. No Linux/macOS-specific issues or missing examples are detected.
Recommendations
  • Consider explicitly noting that Azure CLI commands work on Linux, macOS, and Windows, to reinforce cross-platform support.
  • If possible, provide example CLI commands using both bash and PowerShell syntax, or clarify that PowerShell examples are for Windows users while CLI is for all platforms.
  • Ensure that Linux/macOS users are aware that all tasks can be completed using Azure CLI, and that PowerShell is optional.
  • If there are any Linux-specific considerations (e.g., file permissions, shell differences), mention them.
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 primarily focused on Linux, as indicated by the title and content. However, PowerShell examples are provided alongside Azure CLI and ARM template examples, and PowerShell is presented before Azure CLI in the deployment section. There is a brief mention of a Windows extension, but no Windows-specific tools or patterns dominate the content. All technical instructions, troubleshooting, and known issues are Linux-centric, and Linux tools and commands are used throughout.
Recommendations
  • Move Azure CLI examples before PowerShell examples, as CLI is cross-platform and more relevant for Linux users.
  • Clarify that PowerShell examples are optional and primarily for users on Windows or those who prefer PowerShell.
  • Consider adding Bash script examples for automation, as Bash is the default shell for most Linux distributions.
  • Ensure that all screenshots and command snippets are clearly labeled as Linux-specific to avoid confusion.
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: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation is generally cross-platform and provides technical details relevant to both Linux and Windows users. However, there is a subtle bias in the 'Recommended OS for Performance' row, which lists 'Windows Server 2019+' as the recommended OS without a Linux equivalent or guidance. Additionally, while Linux tools (like lstopo) are referenced and Linux OS support is listed, there are no explicit examples or recommendations for optimal Linux distributions or configurations, whereas Windows is specifically recommended.
Recommendations
  • Add a recommended Linux distribution (or distributions) for performance parity in the 'Recommended OS for Performance' row, such as 'RHEL 8.6+', 'Ubuntu 20.04+', or similar, based on Azure's own benchmarking or support statements.
  • If Windows Server 2019+ is recommended for specific features, clarify what those features are and whether equivalent features or performance can be achieved on Linux.
  • Where possible, provide Linux-specific configuration tips or references, especially for HPC workloads (e.g., kernel tuning, NUMA awareness, or driver installation best practices).
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 throughout, but PowerShell examples are always given immediately after CLI, and often with equal prominence. There is a slight 'windows_first' bias in that PowerShell (a Windows-centric tool, though now cross-platform) is always paired with CLI, and never omitted or de-emphasized. However, all examples and explanations are clearly tailored for Linux VMs, and the CLI is always presented first. No Windows-only tools or patterns are mentioned, and Linux-specific tools (like waagent) are referenced. There are no missing Linux examples, and no Windows tools are prioritized over Linux equivalents.
Recommendations
  • Consider explicitly noting that Azure PowerShell is cross-platform and can be used on Linux/macOS, to avoid confusion for Linux users.
  • Where possible, highlight Bash/CLI as the primary method for Linux users, and clarify PowerShell is optional.
  • Add brief guidance for users who may not have PowerShell installed on Linux, linking to installation instructions.
  • Ensure that CLI examples are always shown first (as is currently the case), and consider grouping PowerShell examples in a separate section for users who prefer it.
GitHub Create Pull Request
Virtual Machines Azure Key Vault VM Extension for Linux ...rticles/virtual-machines/extensions/key-vault-linux.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation is focused on Linux, but there are several sections where Windows-oriented tools (PowerShell) are presented first or in greater detail than Linux-native equivalents. Azure PowerShell deployment instructions and troubleshooting are given before Azure CLI, and PowerShell is referenced in warnings and notes. However, Linux-specific instructions and paths are present throughout, and Azure CLI examples are provided. There are no missing Linux examples or Windows-only tools.
Recommendations
  • Present Azure CLI instructions before Azure PowerShell, as CLI is more cross-platform and native to Linux/macOS.
  • Add explicit notes clarifying that PowerShell is optional and not required for Linux users.
  • Where warnings reference PowerShell-specific issues (e.g., escaping in settings.json), clarify that these are only relevant if using PowerShell, and provide Linux/CLI-specific troubleshooting if applicable.
  • Ensure troubleshooting and support sections reference both CLI and PowerShell equally, with CLI first.
  • Consider adding Bash or shell script deployment examples for Linux users, if relevant.
GitHub Create Pull Request
Virtual Machines Create an image definition and image version ...s/blob/main/articles/virtual-machines/image-version.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides parity for both Linux and Windows throughout, with CLI and REST examples defaulting to Linux, but PowerShell examples defaulting to Windows. Windows is sometimes mentioned first in PowerShell examples, and PowerShell is given its own section with Windows-centric parameters. However, Linux is well-represented in CLI and REST, and the 'Before you begin' section lists Linux guidance first. No critical tasks are Windows-only.
Recommendations
  • In PowerShell example blocks, show both Linux and Windows variants, or default to Linux as in CLI/REST.
  • When listing OS-specific steps or parameters, alternate the order or clarify parity.
  • Explicitly note that PowerShell can be used for Linux images, and provide a Linux example.
  • Ensure that all example code blocks (especially PowerShell) demonstrate both Linux and Windows usage.
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 provides comprehensive instructions for creating and uploading a Red Hat Enterprise Linux VHD for Azure across multiple hypervisors (Hyper-V, KVM, VMware, Kickstart). However, in most sections, Hyper-V (a Windows-native hypervisor) is presented first, and references to Windows tools (e.g., Hyper-V Manager, convert-vhd cmdlet) appear before Linux alternatives. The introductory notes mention Hyper-V tools before Linux/KVM/VMware, and the step-by-step guides for each RHEL version begin with Hyper-V before Linux-native options. All necessary Linux-native instructions are present, but Windows/Hyper-V is prioritized in ordering and framing.
Recommendations
  • Reorder sections so that Linux-native hypervisors (KVM, VMware, Kickstart) are presented before Hyper-V, or at least alternate the order to avoid implicit prioritization.
  • In introductory notes, mention Linux-native tools (e.g., qemu-img, KVM, VMware) alongside or before Windows tools like Hyper-V Manager and convert-vhd.
  • Ensure that Linux-native conversion instructions (e.g., qemu-img) are as prominent as Windows/Hyper-V instructions.
  • Consider adding a summary table or navigation section that equally highlights all supported hypervisors and platforms.
  • Clarify that Hyper-V is not required for Linux users, and that all steps can be completed on Linux-native platforms.
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 sync in Azure and provides comprehensive Linux-specific guidance, examples, and commands. However, the introductory sections discuss Windows Server 2016 time sync improvements and reference Windows documentation before Linux-specific details. This is a minor 'windows_first' bias in the narrative, but all technical guidance and examples are Linux-centric.
Recommendations
  • Move Windows Server 2016 discussion and links to a background or context section, or after Linux-specific information.
  • Begin the page with Linux time sync context and Azure-specific Linux features before referencing Windows infrastructure.
  • Ensure that Linux documentation links and examples are presented before any Windows references, unless Windows context is strictly necessary.
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 Linux and Windows VM images, but there are signs of Windows bias. PowerShell examples are provided alongside Azure CLI, and Windows-specific references (e.g., Sysprep, Windows upload instructions) are sometimes mentioned before Linux equivalents. Some links and examples reference Windows paths or tools first. However, Linux is also covered, and CLI examples are present.
Recommendations
  • Ensure Linux and Windows examples are presented with equal prominence, alternating their order where possible.
  • Provide Bash/Linux shell examples alongside PowerShell, especially in FAQ and walkthroughs.
  • Where referencing upload instructions or tools, mention Linux and Windows equally and avoid defaulting to Windows-first ordering.
  • Review linked pages to ensure Linux parity in referenced content.
  • Clarify when a feature or step is OS-agnostic, and avoid unnecessary Windows-centric language.
GitHub Create Pull Request
Virtual Machines vCPU quotas ...ute-docs/blob/main/articles/virtual-machines/quotas.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for checking vCPU quotas, but PowerShell is featured as a primary tab, and its inclusion may be unnecessary for Linux users. The CLI example is generic and cross-platform, but PowerShell is a Windows-centric tool. There are no Linux-specific shell examples (e.g., Bash), and PowerShell is presented equally alongside CLI, which may create friction for Linux/macOS users.
Recommendations
  • Clarify that PowerShell is primarily for Windows users, and Azure CLI is recommended for Linux/macOS.
  • Consider presenting Azure CLI examples first, as it is cross-platform.
  • Add explicit Bash shell examples or notes for Linux users, if relevant.
  • Mention that PowerShell Core is available cross-platform, but most Linux users prefer CLI.
  • Add a short section or note indicating which tools are best for each OS.
GitHub Create Pull Request