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

Live Progress

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

Scan Information

Started At: 2026-02-21 00:00:11

Finished At: In Progress

Status: in_progress

Target Repo: Azure Compute

Current Phase: discovery

Files Queued: 282

Files Completed: 282

Problematic Pages

95 issues found
Service Fabric Azure Service Fabric reverse proxy ...articles/service-fabric/service-fabric-reverseproxy.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation explicitly states that the Service Fabric reverse proxy is not available for Linux clusters, and all examples and guidance are focused on Windows clusters. There are no Linux-specific instructions, examples, or workarounds provided, and the feature is unavailable for Linux users.
Recommendations
  • Clearly state early in the document that the reverse proxy feature is Windows-only, and link to alternative approaches for Linux clusters if available.
  • Provide guidance or references for Linux users on how to achieve similar functionality, such as using other proxy solutions or patterns.
  • If/when Linux support is added, ensure examples and instructions are provided for both platforms.
GitHub Create Pull Request
Service Fabric Standalone Service Fabric clusters overview ...-fabric/service-fabric-standalone-clusters-overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
Although the introduction claims Service Fabric clusters can run on Windows Server and Linux, the actual content and supported operating systems list indicate that standalone clusters are currently Windows-only. Security sections reference Windows authentication and Windows-specific features, with no Linux guidance or examples. Linux is mentioned in the description, but not supported in practice for standalone clusters.
Recommendations
  • Clarify in the introduction and throughout the page that standalone clusters are currently Windows-only, and Linux support is not available yet.
  • Remove or update the description to avoid implying Linux support where it does not exist.
  • Add a section or note about the roadmap or alternatives for Linux users, such as Azure Service Fabric managed clusters or other deployment options.
  • Provide explicit guidance for Linux users, including links to relevant documentation or alternatives.
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. All upgrade instructions and examples reference Visual Studio (a Windows-only IDE) and PowerShell (primarily a Windows shell), with no mention of Linux/macOS alternatives or cross-platform CLI tools. There are no examples or guidance for Linux users, and Windows tools are presented first and exclusively.
Recommendations
  • Add instructions for upgrading Service Fabric applications using Azure CLI or REST API, which are cross-platform.
  • Include examples for Linux/macOS users, such as using Bash or cross-platform PowerShell Core (pwsh) if applicable.
  • Mention and link to any available non-Windows tooling for Service Fabric application upgrades.
  • Clarify whether certain steps are Windows-only, and provide Linux/macOS alternatives where possible.
GitHub Create Pull Request
Service Fabric Initializer CodePackages in Service Fabric ...in/articles/service-fabric/initializer-codepackages.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page for Initializer CodePackages in Service Fabric presents only Windows container examples, exclusively references Windows container images (nanoserver:1809), uses Windows file paths and commands (cmd, C:\ paths), and does not mention or provide examples for Linux containers or Linux file systems. The ApplicationManifest and ServiceManifest examples are Windows-centric, and the workflow assumes Windows containers and tooling. There is no guidance for Linux container scenarios, nor any mention of cross-platform support.
Recommendations
  • Add examples using Linux container images (e.g., Ubuntu, Alpine) and Linux file paths.
  • Provide equivalent Linux shell commands (e.g., bash, sh) for initialization steps.
  • Clarify whether Initializer CodePackages are supported for Linux containers in Service Fabric, and if so, provide guidance and examples.
  • Mention any platform limitations explicitly (e.g., if Initializer CodePackages are Windows-only, state this clearly).
  • Ensure volume mounts and file operations are shown for both Windows and Linux container scenarios.
GitHub Create Pull Request
Service Fabric Service Fabric application upgrade ...s/service-fabric/service-fabric-application-upgrade.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page for Service Fabric application upgrade exhibits notable Windows bias. All code examples are provided exclusively in PowerShell, a Windows-centric tool. References to Service Fabric PowerShell cmdlets and Windows HTTP Server API (http.sys) are made without Linux equivalents or guidance. There are no examples or instructions for Linux/macOS users, and Windows tools are mentioned first and exclusively throughout the page.
Recommendations
  • Add equivalent CLI examples using Azure CLI or Service Fabric CLI (sfctl), which are cross-platform.
  • Provide guidance for Linux/macOS users, including how to perform upgrades and manage application parameters on non-Windows platforms.
  • Mention Linux-specific considerations, such as how HTTPS endpoints and certificate management differ from Windows (http.sys).
  • Ensure that references to PowerShell are accompanied by alternative commands or links for Linux/macOS users.
  • Clarify which features or steps are Windows-only and provide alternatives or workarounds for Linux clusters.
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 ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation consistently provides PowerShell examples for all key operations (creating, updating, querying, and removing application groups/capacity), but does not offer equivalent Linux/macOS CLI examples (such as Azure CLI, Bash, or REST API). PowerShell is primarily a Windows tool, and its exclusive use creates friction for Linux/macOS users. There is no mention of cross-platform tools or alternative command-line methods.
Recommendations
  • Add Azure CLI examples for all operations shown in PowerShell, if supported.
  • Mention REST API endpoints or provide sample requests for relevant actions.
  • Clarify whether PowerShell cmdlets are available cross-platform (e.g., via PowerShell Core), and provide guidance for Linux/macOS users.
  • If PowerShell is the only supported method, explicitly state this limitation and link to any available cross-platform alternatives or workarounds.
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 omits equivalent Linux CLI or bash examples. PowerShell is presented first, followed by C#, with no mention of Linux-native tools or cross-platform command-line alternatives. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other scripting environments.
Recommendations
  • Add Azure CLI or bash examples for configuring move cost, especially for service creation and updates.
  • Clarify whether PowerShell commands can be run cross-platform (e.g., via PowerShell Core), or provide guidance for Linux/macOS users.
  • Consider presenting examples in a platform-neutral order, or explicitly state platform requirements for each example.
  • Mention any REST API or SDK alternatives that are platform-agnostic.
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 detailed conceptual overview of Service Fabric health monitoring, but the only practical example for reporting and evaluating application health is given using PowerShell. There are no equivalent Linux/macOS CLI or REST API examples, despite the text mentioning REST and FabricClient APIs. This creates friction for Linux/macOS users, who may not have access to PowerShell or Windows-specific cmdlets.
Recommendations
  • Add equivalent examples using the Service Fabric CLI (sfctl), which is cross-platform and supported on Linux/macOS.
  • Include REST API usage examples for health reporting and querying, as referenced in the text.
  • Mention and link to documentation for Linux/macOS tools (sfctl, REST) alongside PowerShell, not after or instead of.
  • Clarify which tools are available on which platforms, and provide guidance for Linux/macOS users.
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: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation references PowerShell for deployment/removal and uses a PowerShell module link for downloading ServicePackages, but does not provide Linux/CLI equivalents or mention cross-platform tools. This may create friction for Linux/macOS users managing Service Fabric clusters.
Recommendations
  • Include Azure CLI or cross-platform command examples alongside PowerShell, especially for deployment/removal and ServicePackage download steps.
  • Link to documentation for Linux-based Service Fabric cluster management where available.
  • Clarify which steps are platform-agnostic and which are Windows-specific, and provide alternatives or notes for Linux/macOS users.
  • If certain operations are only possible via PowerShell, explicitly state this and suggest workarounds or alternatives for non-Windows users.
GitHub Create Pull Request
Service Fabric Learn more about Azure Service Fabric ...icles/service-fabric/service-fabric-content-roadmap.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides a broad overview of Azure Service Fabric, which supports both Windows and Linux. However, there is a notable Windows bias: Windows-specific tools (e.g., PowerShell, Visual Studio) are mentioned first or exclusively in several places, and some examples (such as standalone cluster creation and scaling) are only given for Windows. Linux equivalents are sometimes missing or referenced less prominently. The documentation also frequently references Windows executables (e.g., FabricHost.exe) without clarifying Linux alternatives or differences, and PowerShell is often listed before CLI or REST options.
Recommendations
  • Provide Linux-specific examples and instructions alongside Windows ones, especially for cluster creation, scaling, and upgrades.
  • Mention Linux tools (e.g., Bash, sfctl CLI) before or equally with Windows tools like PowerShell.
  • Clarify differences in process management and service hosting between Windows and Linux nodes.
  • Add links to Linux-specific documentation and quickstarts where available.
  • Ensure parity in 'Next steps' and throughout the document, so Linux users can easily find relevant guidance.
GitHub Create Pull Request
Service Fabric Replica soft delete for enhanced data protection in Service Fabric ...s/service-fabric/service-fabric-replica-soft-delete.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page for Replica Soft Delete in Service Fabric heavily references PowerShell cmdlets (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica) and administrative APIs without providing equivalent examples or guidance for Linux/macOS users. All command-line examples and API references are Windows-centric, and there is no mention of Linux tooling, CLI alternatives, or cross-platform SDK usage. This creates friction for non-Windows users, especially since Service Fabric supports Linux clusters.
Recommendations
  • Add examples using Service Fabric CLI (sfctl) for Linux/macOS users, where applicable.
  • Clarify whether the PowerShell cmdlets have direct equivalents in sfctl or REST APIs and provide those examples.
  • Explicitly state if certain administrative operations are Windows-only, or provide cross-platform alternatives.
  • Include sample commands and screenshots for Linux environments, not just Windows/PowerShell.
  • Mention SDK usage in cross-platform languages (e.g., .NET Core, Java) where relevant.
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. Windows file paths and certificate store names are referenced first, with Linux equivalents mentioned only briefly. No Linux CLI (e.g., Bash, sfctl) examples are provided for deployment or endpoint configuration, and Windows terminology/tools appear before Linux alternatives.
Recommendations
  • Add Linux-specific deployment examples using sfctl or Bash scripts alongside PowerShell.
  • Mention Linux file paths and certificate storage locations equally with Windows paths, not as an afterthought.
  • Provide clear guidance for Linux/macOS users on how to perform endpoint configuration and application deployment.
  • Where possible, show cross-platform commands or note differences in tooling and workflow.
GitHub Create Pull Request
Virtual Machines Associate a virtual machine to a capacity reservation group .../virtual-machines/capacity-reservation-associate-vm.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation covers both Windows and Linux VMs, and provides parity in API, Portal, CLI, and PowerShell instructions. However, the ARM template example is Windows-centric: it only shows Windows image SKUs and parameters, with no Linux image option or example. Additionally, the ARM template section does not mention how to deploy a Linux VM, and the PowerShell examples (which are inherently Windows-focused) are presented alongside CLI examples, but CLI examples do include Linux (Ubuntu) images. The ordering of examples is generally neutral, but the ARM template bias is notable.
Recommendations
  • Add a Linux VM ARM template example, or at least show how to modify the template to deploy a Linux VM (e.g., using Ubuntu or other popular Linux distributions).
  • In the ARM template parameters, include both Windows and Linux image options, or provide guidance for Linux users.
  • Clarify in the ARM template section that the example is for Windows, and provide a link or snippet for Linux VM ARM templates.
  • Ensure that all examples (especially templates) are inclusive of both Windows and Linux scenarios, as the feature applies to both.
GitHub Create Pull Request
Virtual Machines Create and upload an Ubuntu Linux VHD in Azure ...rticles/virtual-machines/linux/create-upload-ubuntu.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation, while focused on Ubuntu Linux VHD creation, frequently references Windows tools (Hyper-V, PowerShell's Convert-VHD), presents Windows/Hyper-V steps first or exclusively, and lacks equivalent Linux-native tooling guidance for critical steps such as VHD creation and conversion. Linux users may struggle to follow the process without additional research or tooling.
Recommendations
  • Provide Linux-native instructions for creating and converting VHDs (e.g., using qemu-img, VBoxManage, or other open-source tools).
  • Add examples for extracting and manipulating VHDs on Linux/macOS, not just referencing Windows/WSL.
  • Mention Linux virtualization solutions (KVM, VirtualBox, QEMU) alongside Hyper-V, and link to relevant guides.
  • Ensure PowerShell/Convert-VHD steps are accompanied by Linux alternatives.
  • Clarify which steps are OS-agnostic and which are Windows-specific, and offer parity where possible.
GitHub Create Pull Request
Service Fabric Manage certificates in a Service Fabric cluster ...vice-fabric/cluster-security-certificate-management.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation provides a mix of JSON ARM template examples and PowerShell scripts, with a clear preference for Windows-centric tooling and patterns. The Key Vault VM extension is described as 'KeyVaultForWindows', and the linking behavior is explicitly stated as 'Only Windows'. PowerShell is the only scripting language shown for certificate enrollment. While the documentation covers Azure Service Fabric clusters in general, it assumes Windows as the default platform for VM extensions, certificate provisioning, and scripting, with no Linux-specific examples or guidance.
Recommendations
  • Add equivalent Bash/CLI examples for certificate enrollment and management, especially for Linux-based clusters.
  • Clarify which steps and extensions are Windows-only, and provide Linux alternatives where available (e.g., Key Vault VM extension for Linux).
  • Include references to Linux certificate stores and provisioning mechanisms, such as using PEM files and configuring certificates in Linux VMSS nodes.
  • Ensure troubleshooting and FAQ sections address Linux scenarios and scripting options.
  • Explicitly state platform limitations and provide links to Linux-specific documentation where relevant.
GitHub Create Pull Request
Service Fabric X.509 Certificate-based Authentication in a Service Fabric Cluster ...ticles/service-fabric/cluster-security-certificates.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation provides detailed explanations of X.509 certificate-based authentication in Service Fabric clusters, with configuration examples primarily in XML and references to both Windows and Linux certificate storage paths. However, troubleshooting sections and tool references are heavily Windows-centric, mentioning Windows event logs, CAPI2 logging, Win32 CryptoAPI, and Windows certificate stores first or exclusively. Linux equivalents are mentioned briefly or as parenthetical notes, but not explained in depth or with examples.
Recommendations
  • Add explicit Linux/macOS troubleshooting guidance, including log locations, relevant commands (e.g., journalctl, syslog), and certificate management tools.
  • Provide Linux/macOS-specific examples for certificate storage, retrieval, and validation (e.g., using OpenSSL, certutil, or systemd paths).
  • Clarify differences in certificate store handling between Windows and Linux, and offer step-by-step instructions for both platforms.
  • Include references to Linux documentation and tools alongside Windows ones, not just as parentheticals.
  • Ensure that troubleshooting error codes and remediation steps are applicable to Linux/macOS, or provide platform-specific guidance.
GitHub Create Pull Request
Service Fabric Custom Image .../articles/service-fabric/how-to-deploy-custom-image.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page primarily discusses deploying custom Windows images on Azure Service Fabric Managed Clusters. Windows terminology and examples are presented first and most prominently, including a PowerShell command for role assignment. While there are references to Linux custom image creation and Azure CLI usage, Windows-specific language and tools are emphasized, and Linux/macOS equivalents are not provided for all steps.
Recommendations
  • Clarify in the introduction whether Linux images are supported for Service Fabric Managed Clusters and provide parity in examples if so.
  • Add Linux/macOS command-line examples (e.g., Azure CLI or Bash) alongside PowerShell for role assignment and image management.
  • Balance terminology by referring to 'Windows or Linux custom images' where applicable, rather than only 'custom windows images'.
  • Ensure links to Linux documentation are as prominent as Windows links.
  • Explicitly state any limitations or differences for Linux images, if present.
GitHub Create Pull Request
Service Fabric Configure or modify a Service Fabric managed cluster node type ...vice-fabric/how-to-managed-cluster-modify-node-type.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides examples for managing Service Fabric managed cluster node types using the Azure Portal, ARM templates, and PowerShell. PowerShell is the only CLI-based scripting example shown, with no mention of Azure CLI or Bash equivalents. PowerShell is presented as the default scripting tool for automation, and there are no Linux/macOS-specific instructions or examples. This creates friction for users on non-Windows platforms who may prefer or require Azure CLI or Bash.
Recommendations
  • Add Azure CLI examples for all tasks where PowerShell is used (e.g., adding, removing, scaling node types, configuring placement properties).
  • Explicitly mention that PowerShell Core is cross-platform, or clarify if only Windows PowerShell is supported.
  • Where possible, provide Bash or shell script examples for ARM template deployments.
  • Consider listing Azure CLI examples before or alongside PowerShell to avoid Windows-first bias.
  • Add a note clarifying platform compatibility for the provided scripts and tools.
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 predominantly references PowerShell cmdlets (Az PowerShell, AzSF PowerShell) for managing Service Fabric resources, with no explicit mention of Linux/macOS equivalents or CLI alternatives in several sections. While the Azure CLI (az resource) is mentioned once for deleting applications, PowerShell is presented as the primary tool for most operations, and examples or guidance for Linux/macOS users are missing.
Recommendations
  • Add Azure CLI equivalents for all PowerShell cmdlet examples, especially for provisioning and deleting resources.
  • Explicitly state that Azure CLI can be used on Linux/macOS and provide sample commands.
  • Where possible, include ARM template usage examples that are platform-agnostic.
  • Clarify which management operations can be performed using cross-platform tools and which are PowerShell-only.
GitHub Create Pull Request
Service Fabric Introduction to the Service Fabric Infrastructure Service .../articles/service-fabric/infrastructure-service-faq.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides a PowerShell-only example for bypassing Infrastructure Service, and references Service Fabric Explorer (a GUI tool primarily available on Windows). There are no equivalent Linux/macOS CLI examples or guidance, and Windows-centric tooling is mentioned first and exclusively.
Recommendations
  • Add equivalent Linux/macOS CLI examples (e.g., using sfctl or REST API) for cluster operations.
  • Clarify whether Service Fabric Explorer is accessible cross-platform or provide alternatives for Linux/macOS users.
  • Mention cross-platform tools and commands alongside PowerShell examples.
  • Explicitly note any limitations or differences for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Migrate an Azure Service Fabric cluster to availability zone support ...ce-fabric/migrate-service-fabric-availability-zones.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides extensive PowerShell-based migration steps for Service Fabric clusters, especially for nonmanaged clusters with Basic SKU load balancer and IP resources. All command-line examples are given in PowerShell, with no equivalent Azure CLI or bash examples. The sample templates referenced are mostly Windows-based, and Windows paths (e.g., 'D:\\SvcFab') are used in configuration snippets. Linux tools and patterns are not mentioned, and Linux migration steps are not provided, despite Service Fabric supporting Linux node types.
Recommendations
  • Add Azure CLI/bash equivalents for all PowerShell migration commands, especially for resource deployment, node disabling/removal, and DNS updates.
  • Reference and provide Linux sample templates alongside Windows templates, ensuring parity in guidance.
  • Use OS-agnostic paths or clarify when Windows-specific paths are required; provide Linux path examples where applicable.
  • Mention Linux node type migration considerations and highlight any differences or similarities.
  • Ensure that instructions for disabling/removing nodes and updating resources are available for Linux clusters, not just Windows clusters.
GitHub Create Pull Request
Service Fabric RunToCompletion semantics and specifications ...blob/main/articles/service-fabric/run-to-completion.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a notable Windows bias. All code examples are for Windows containers (using Windows NanoServer images and Windows CMD commands), and the only command-line querying example is via PowerShell. There are no Linux container examples, nor are Linux shell commands or tools mentioned. The documentation assumes familiarity with Windows container development and omits Linux equivalents.
Recommendations
  • Add equivalent examples for Linux containers (e.g., using Ubuntu or Alpine images and bash commands).
  • Provide instructions and sample manifests for Linux container scenarios.
  • Include Linux shell command examples (e.g., using Bash or CLI tools) for querying deployment status.
  • Clarify whether RunToCompletion semantics are supported for Linux containers, and if so, provide guidance.
  • If Windows-only, explicitly state this limitation at the top of the article.
GitHub Create Pull Request
Service Fabric Describing Azure Service Fabric apps and services ...ic/service-fabric-application-and-service-manifests.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation contains a notable Windows bias in its guidance for authoring Service Fabric manifests. It recommends opening the ServiceFabricServiceModel.xsd schema file in Visual Studio, referencing a Windows file path (C:\Program Files\Microsoft SDKs\Service Fabric\schemas\ServiceFabricServiceModel.xsd), and does not mention Linux/macOS alternatives or cross-platform tools for schema validation or authoring. Additionally, PowerShell is referenced as a way to create service instances, but no Linux CLI equivalent is provided.
Recommendations
  • Provide cross-platform instructions for schema validation and authoring, such as using VS Code or other editors on Linux/macOS.
  • Mention the location of ServiceFabricServiceModel.xsd on Linux clusters, if applicable, or clarify if schema validation is only possible on Windows.
  • Include CLI examples for creating service instances using Azure CLI or Service Fabric CLI (sfctl), not just PowerShell.
  • Avoid referencing Windows file paths exclusively; provide Linux/macOS equivalents or note platform differences.
  • Ensure tooling recommendations (e.g., Visual Studio) are balanced with cross-platform options (e.g., VS Code, XML lint tools).
GitHub Create Pull Request
Service Fabric Monitor Azure Service Fabric ...main/articles/service-fabric/monitor-service-fabric.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation covers monitoring for both Windows and Linux Service Fabric clusters, but there is a noticeable Windows bias in several areas. Windows-specific tools (Event Log, Event Viewer, Diagnostics Agent) are mentioned first or exclusively, while Linux equivalents are referenced later or with less detail. Some examples and tutorials focus on Windows/.NET applications, and Linux-specific guidance is often relegated to links or brief notes. EventStore APIs are Windows-only, and Linux configuration is described as 'different' without concrete examples. Overall, Linux users can achieve parity, but must navigate more friction and less direct guidance.
Recommendations
  • Provide Linux-specific monitoring examples and walkthroughs alongside Windows examples, not just as links.
  • When referencing tools (e.g., Event Viewer, Diagnostics Agent), immediately mention Linux equivalents (e.g., Syslog, Azure Monitor agent) and provide parallel instructions.
  • Add explicit Linux sample code or configuration snippets for cluster and infrastructure monitoring.
  • Clarify which features are Windows-only and offer alternative approaches for Linux users where possible.
  • Ensure tutorials and sample queries are applicable to both platforms, or provide Linux-specific variants.
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 Service Fabric application security in a generally platform-agnostic manner, but several sections show Windows bias. Windows-specific features (such as Active Directory domain accounts and gMSA) are mentioned before Linux equivalents or without Linux alternatives. Disk encryption is referenced only via BitLocker and PowerShell, with Linux disk encryption left as a TODO. Some examples and explanations focus on Windows tools and patterns, and Linux-specific guidance is missing or deferred.
Recommendations
  • Add explicit Linux examples and guidance where only Windows is mentioned, especially for disk encryption and user account management.
  • Ensure Linux equivalents (such as Linux disk encryption methods, Linux user/group management) are described alongside Windows features.
  • Where Windows tools (e.g., PowerShell, BitLocker, AD accounts, gMSA) are referenced, provide links or instructions for Linux alternatives (e.g., LUKS for disk encryption, Linux service accounts).
  • Review examples and ensure both Windows and Linux scenarios are covered, or clarify when a feature is Windows-only.
  • Update TODOs to include actionable Linux guidance rather than leaving them as placeholders.
GitHub Create Pull Request
Service Fabric Application lifecycle in Service Fabric ...service-fabric/service-fabric-application-lifecycle.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page for the Service Fabric application lifecycle consistently references PowerShell cmdlets and Windows-centric tooling (e.g., Copy-ServiceFabricApplicationPackage, Register-ServiceFabricApplicationType) alongside .NET APIs and REST operations. PowerShell examples and cmdlets are mentioned in nearly every lifecycle phase, often before or instead of Linux-friendly alternatives. There is no explicit mention of Linux/macOS command-line equivalents (such as Azure CLI or sfctl), and no Linux-specific examples or guidance are provided. The [!INCLUDE [links to azure cli and service fabric cli](./includes/service-fabric-sfctl.md)] is present, but actual usage examples or parity are missing throughout the main content.
Recommendations
  • Add explicit examples and instructions using Azure CLI and sfctl for each lifecycle phase (deploy, upgrade, remove, etc.), ensuring Linux/macOS users can follow along without PowerShell.
  • Where PowerShell cmdlets are referenced, provide equivalent Azure CLI/sfctl commands side-by-side.
  • Clarify which tools are cross-platform and which are Windows-only, and link to Linux/macOS-specific guidance where available.
  • Review all code snippets and procedural steps to ensure Linux/macOS users are not left out or forced to infer their own equivalents.
  • Consider reordering examples so that cross-platform tools (Azure CLI/sfctl/REST) are presented before or alongside Windows-specific tools.
GitHub Create Pull Request
Service Fabric Advanced Application Upgrade Topics ...-fabric/service-fabric-application-upgrade-advanced.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides numerous PowerShell cmdlet examples for Service Fabric application upgrades, with no equivalent CLI or Linux/macOS instructions. All command-line examples use PowerShell syntax, and references to tooling (such as Visual Studio) are Windows-centric. There is no mention of Service Fabric CLI (sfctl), Bash, or cross-platform alternatives, which may create friction for Linux/macOS users.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and supported on Linux/macOS.
  • Include Bash or generic shell command examples where applicable, alongside PowerShell.
  • Mention cross-platform tools and workflows, such as using sfctl or Azure portal, in addition to Visual Studio and PowerShell.
  • Clarify which features or commands are Windows-only, and provide guidance for Linux/macOS users where parity exists.
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. No equivalent Linux/macOS upgrade examples or tooling are mentioned. The core serialization guidance is platform-neutral, but the 'Next steps' section directs users to Windows-first workflows.
Recommendations
  • Add links or sections for upgrading Service Fabric applications using Linux/macOS-compatible tools (e.g., Azure CLI, REST API, or cross-platform SDKs).
  • Explicitly mention if PowerShell Core is supported on Linux/macOS, and provide relevant examples if so.
  • Provide parity by including upgrade tutorials for Linux environments, or clarify if Service Fabric application upgrades are Windows-only.
  • If Visual Studio is Windows-only for Service Fabric upgrades, suggest alternative IDEs or command-line options for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Application upgrade: upgrade parameters ...abric/service-fabric-application-upgrade-parameters.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page presents Windows/PowerShell and Visual Studio upgrade parameters first and in greater detail, with tables and examples, before mentioning the cross-platform Service Fabric CLI (sfctl). PowerShell is emphasized throughout, and parameter tables are labeled 'PowerShell, Visual Studio' even when CLI equivalents exist. Linux/macOS users must scroll past Windows-focused content to reach CLI information, and CLI parameters are described with less detail and fewer examples.
Recommendations
  • Reorganize the page to present upgrade methods in a neutral order (e.g., PowerShell, Visual Studio, SFCTL, REST), or start with cross-platform tools like SFCTL.
  • Add equivalent parameter tables and examples for SFCTL, matching the detail given for PowerShell.
  • Clarify that PowerShell is Windows-only and highlight SFCTL as the recommended cross-platform tool for Linux/macOS users.
  • Provide example upgrade commands for SFCTL, including parameter usage, similar to PowerShell examples.
  • Consider grouping upgrade methods by platform (Windows vs. cross-platform) or clearly marking which tools are platform-specific.
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 instructions using PowerShell modules and commands. There are no examples or guidance for Linux/macOS users, such as using Bash, curl, or cross-platform tools. The Service Fabric Explorer UI is mentioned, but the primary automation and scripting guidance is Windows-centric.
Recommendations
  • Add equivalent Bash/curl examples for REST API calls, showing how Linux/macOS users can trigger backups and track progress.
  • Document how to authenticate and connect to Service Fabric clusters from Linux/macOS, including certificate handling.
  • Mention any cross-platform CLI tools (e.g., Azure CLI, sfctl) that can be used for backup operations, and provide examples.
  • Clarify whether the PowerShell module is available or supported on PowerShell Core for Linux/macOS, and if so, provide installation instructions.
  • Consider restructuring sections so that REST API usage is shown in a cross-platform way (e.g., curl), not only via PowerShell.
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 for restoring backups in Azure Service Fabric is heavily focused on PowerShell-based workflows, specifically using the Microsoft.ServiceFabric.Powershell.Http module and PowerShell scripting. All code examples are provided in PowerShell, with no equivalent examples for Linux/macOS users (e.g., Bash, curl, or cross-platform CLI tools). The prerequisite section also requires installation of a PowerShell module, and REST API calls are demonstrated only via PowerShell. There is no mention of Linux-compatible tools or instructions for users on non-Windows platforms.
Recommendations
  • Add REST API examples using curl or HTTPie for cross-platform compatibility.
  • Document how to authenticate and make Service Fabric REST calls from Linux/macOS (e.g., using client certificates).
  • Mention and provide guidance for Azure CLI or other cross-platform tools if available.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is required for all restore operations, or if REST calls can be made directly from any OS.
  • Include a section or note for Linux/macOS users outlining supported workflows and any limitations.
GitHub Create Pull Request
Service Fabric Understanding periodic backup configuration ...-fabric-backuprestoreservice-configure-periodic-backup.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page 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 UNC paths (\\StorageServer\BackupStore) and Windows authentication mechanisms are described, with no mention of Linux-compatible file share paths (e.g., SMB/CIFS mounts) or authentication methods. There are no examples or guidance for Linux users on configuring file share backup storage.
Recommendations
  • Add examples and instructions for configuring file share backup storage from Linux nodes, including SMB/CIFS mount paths and authentication options.
  • Clarify whether Linux Service Fabric clusters can use file share backup storage, and if so, provide guidance on Linux-compatible file share paths and credential handling.
  • Mention any limitations or differences for Linux clusters regarding file share backup storage.
  • If file share backup storage is Windows-only, explicitly state this to avoid confusion for Linux users.
GitHub Create Pull Request
Service Fabric Capacity planning and scaling for Azure Service Fabric ...bric/service-fabric-best-practices-capacity-scaling.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides several PowerShell-based examples and instructions for scaling operations (e.g., using Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState) without offering equivalent Linux/bash/CLI commands or guidance. This creates friction for Linux users, who may not have access to PowerShell or may be unfamiliar with its usage. The documentation does mention Linux clusters in the 'Next steps' section, but operational guidance is Windows-centric.
Recommendations
  • Provide equivalent Azure CLI or bash commands for all PowerShell examples, especially for node management tasks (e.g., disabling/removing nodes).
  • Explicitly note if certain operations must be performed from a Windows environment, and suggest alternatives or workarounds for Linux users.
  • Add links or references to Linux-specific Service Fabric management documentation where available.
  • Clarify in each example whether the command is cross-platform or Windows-only.
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: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation provides both Windows and Linux Resource Manager template samples, but several sections show Windows bias. PowerShell is used for deployment and upgrade examples, with no equivalent Bash or Linux-native commands. Windows-specific tools and registry keys are referenced for VM patching, while Linux equivalents are missing. Windows configuration properties are shown, but Linux VM configuration is not. Upgrade instructions use Windows MSI packages and PowerShell, with no Linux (DEB) example provided.
Recommendations
  • Add Bash or Azure CLI examples for deployment and upgrade tasks alongside PowerShell.
  • Include Linux VM configuration properties (e.g., osProfile.linuxConfiguration) in template snippets.
  • Provide Linux-specific guidance for patch management (e.g., disabling automatic updates on Linux VMs).
  • Show how to manually upgrade clusters using Linux tools and DEB packages, not just Windows MSI and PowerShell.
  • Ensure that for every Windows registry or configuration reference, a Linux equivalent (if applicable) is mentioned.
GitHub Create Pull Request
Service Fabric Azure Service Fabric networking best practices ...ice-fabric/service-fabric-best-practices-networking.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page presents several examples and explanations that prioritize Windows tools and patterns, such as referencing PowerShell APIs, Windows-specific port usage, and ARM templates for Windows clusters. Windows-related scenarios (e.g., patching, DevOps tasks) are described in detail, while Linux equivalents are either briefly mentioned or omitted. PowerShell is referenced as the primary client API example, and some sample templates are Windows-focused. Linux-specific guidance is less prominent and sometimes missing.
Recommendations
  • Provide Linux CLI (az, bash) examples alongside PowerShell for cluster management and networking tasks.
  • Include ARM template samples for Linux clusters with NSG rules, not just Windows.
  • Clarify which port ranges and rules apply to Linux clusters, and which do not (e.g., ephemeral ports).
  • Expand on Linux-specific operational tasks (e.g., patching, DevOps) and reference relevant tools (e.g., Ansible, Bash scripts).
  • Ensure parity in application networking examples for Linux containers and workloads.
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 most security best practices, including certificate creation and secret encryption. However, Windows-specific tools (PowerShell, Windows Defender, Azure DSC) are often mentioned first or exclusively, and Windows examples precede Linux equivalents in several sections. Windows Defender and DSC are discussed without Linux alternatives, and Windows-centric terminology (certificate store, PowerShell commands) is prominent. Linux examples are present but sometimes secondary.
Recommendations
  • Ensure Linux examples are presented alongside Windows examples, not after them.
  • Where Windows-specific tools (e.g., Windows Defender, DSC) are discussed, explicitly mention Linux alternatives (e.g., common Linux antivirus solutions, configuration management tools like Ansible or Chef).
  • Use neutral terminology where possible (e.g., 'certificate store' vs. 'Linux certificate location').
  • For sections that are Windows-only, clarify that Linux users should refer to their own platform-specific tools.
  • Consider adding links to Linux-focused security baseline guidance and best practices.
GitHub Create Pull Request
Service Fabric Change Azure Service Fabric cluster settings ...rvice-fabric/service-fabric-cluster-fabric-settings.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation page provides a comprehensive reference for Service Fabric cluster settings, but there is evidence of Windows bias. Windows terminology (e.g., 'MY' certificate store, 'LocalMachine', NTLM authentication, Windows Defender Firewall) is used throughout, and Windows-specific settings are often mentioned first or exclusively. Some settings reference Windows tools and APIs (e.g., CertGetCertificateChain, ETW traces, Windows Firewall). Linux equivalents are sometimes present, but not always explained or given equal prominence. The guidance for standalone clusters links only to a Windows Server page, and there are no Linux-specific configuration examples or references for standalone clusters.
Recommendations
  • Add explicit Linux configuration examples and references, especially for standalone clusters.
  • Where Windows-specific terminology is used (e.g., certificate store names), clarify Linux equivalents or alternatives.
  • Ensure Linux-specific settings (such as X509Folder, LinuxExternalExecutablePath, EnforceLinuxMinTlsVersion) are explained and given equal prominence.
  • Provide links to Linux documentation for standalone Service Fabric clusters, if available.
  • Review guidance and descriptions to ensure Linux/macOS users can follow all steps without ambiguity or missing information.
GitHub Create Pull Request
Service Fabric Describe a cluster by using Cluster Resource Manager ...ce-fabric-cluster-resource-manager-cluster-description.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides examples and configuration snippets for both Windows (ClusterManifest.xml with <WindowsServer>) and cross-platform/standalone (ClusterConfig.json) deployments. However, Windows-specific configuration (ClusterManifest.xml with <WindowsServer>) is presented first and more prominently, and PowerShell examples are included for service creation and updates, while Linux-native equivalents (e.g., Bash, CLI) are absent. There is no explicit mention of Linux/macOS tools or patterns, and the documentation does not clarify Linux parity or differences for standalone Service Fabric clusters.
Recommendations
  • Include explicit Linux/macOS deployment examples, such as ClusterManifest.xml with <Linux> infrastructure or reference to Linux node setup.
  • Add Bash or Azure CLI equivalents for PowerShell commands, or clarify if PowerShell is required/cross-platform.
  • Document any differences or limitations for Linux-based Service Fabric clusters, if applicable.
  • Present cross-platform configuration examples (ClusterConfig.json) before or alongside Windows-specific examples to avoid Windows-first bias.
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 Windows-style paths and commands (e.g., 'PS C:\Users\User > Get-ServiceFabricPartitionHealth'). No equivalent Linux or cross-platform example is given, and the example is presented early in the article. The rest of the documentation is platform-neutral, focusing on concepts and configuration files, but the only concrete example is Windows-centric.
Recommendations
  • Add equivalent Linux/macOS CLI examples (e.g., using Azure CLI, sfctl, or Service Fabric REST API) alongside PowerShell examples.
  • When showing command-line usage, include both Windows (PowerShell) and Linux (bash) variants, or note cross-platform tools.
  • Clarify if the PowerShell example is Windows-only and provide guidance for Linux users on how to achieve the same task.
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: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ 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 range, admin username/password), without Linux equivalents or parity. The documentation mentions both 'ServiceFabricLinuxNode' and 'ServiceFabricNode' in the extension snippet, but practical examples and tooling focus on Windows scenarios.
Recommendations
  • Provide Linux-specific examples for connecting to cluster nodes, such as using SSH instead of RDP.
  • Include guidance or scripts for changing admin credentials and port ranges on Linux clusters.
  • Show Linux file paths (e.g., '/var/lib/svcfab') alongside Windows paths in configuration examples.
  • Balance PowerShell references with Bash/CLI equivalents for common cluster management tasks.
  • Clarify which steps are OS-specific and provide links to Linux documentation where appropriate.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager - Placement Policies ...ce-manager-advanced-placement-rules-placement-policies.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page provides code examples in C# and PowerShell only, with no mention of Linux-native tools or cross-platform CLI alternatives. All command-line examples use PowerShell cmdlets, which are primarily associated with Windows environments, and there is no guidance for Linux/macOS users on how to perform equivalent operations.
Recommendations
  • Add Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention whether the PowerShell cmdlets are available and supported on Linux/macOS (e.g., via PowerShell Core), or provide alternatives if not.
  • Include a note or section for Linux/macOS users, clarifying how to configure placement policies using supported tools on those platforms.
  • If REST API or ARM template options exist for configuring these policies, provide examples or references.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Auto Scaling Services and Containers ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-autoscaling.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides detailed examples for configuring auto scaling policies in Azure Service Fabric using application manifests, C# APIs, and PowerShell. However, all CLI examples are exclusively PowerShell-based, with no equivalent Bash or Linux CLI examples. The PowerShell examples are presented alongside C# and manifest examples, but there is no mention of Linux tooling or cross-platform command-line approaches. This creates friction for Linux/macOS users, especially since Service Fabric supports Linux containers and clusters.
Recommendations
  • Add Bash or Azure CLI examples for configuring scaling policies, especially for Linux clusters.
  • Explicitly state which PowerShell commands are cross-platform (if any), or provide alternatives for Linux users.
  • Mention Linux-specific considerations or limitations where relevant, such as differences in resource monitoring or activation models.
  • Include links or references to Linux administration guides for Service Fabric where applicable.
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 metrics in Azure Service Fabric primarily in C# and PowerShell. PowerShell is a Windows-centric tool, and no equivalent Linux/macOS CLI (e.g., Azure CLI, Bash, or REST API) examples are provided. The PowerShell examples are presented alongside C# code, but there is no mention of cross-platform alternatives or guidance for Linux/macOS users. This creates friction for non-Windows users who may not have access to PowerShell or prefer other tools.
Recommendations
  • Add Azure CLI examples for service creation and metric management, as Azure CLI is cross-platform.
  • Include REST API sample calls for metric configuration and reporting, which are platform-agnostic.
  • Mention Bash scripting or other Linux-native approaches where appropriate.
  • Clarify which operations are possible via Azure Portal or other graphical tools.
  • Explicitly note PowerShell's platform limitations and provide links to Linux/macOS alternatives.
GitHub Create Pull Request
Service Fabric Service sensitivity ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-sensitivity.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation provides PowerShell examples for configuring service sensitivity and maximum load, but does not offer equivalent CLI or scripting examples for Linux/macOS users. The PowerShell API is referenced exclusively, and there is no mention of cross-platform tools (such as Azure CLI or REST API) for these operations. This creates friction for Linux/macOS administrators who may not have access to PowerShell or prefer native tools.
Recommendations
  • Add Azure CLI or REST API examples for configuring service sensitivity and maximum load, if supported.
  • Clarify whether PowerShell commands can be run cross-platform (e.g., via PowerShell Core) or if they are Windows-only.
  • If PowerShell is the only supported scripting interface, explicitly state this limitation and suggest alternatives for Linux/macOS users.
  • Consider including sample scripts or instructions for editing cluster manifests and application manifests using standard text editors or automation tools available on Linux/macOS.
GitHub Create Pull Request
Service Fabric Azure Service Fabric standalone cluster scaling ...ce-fabric/service-fabric-cluster-scaling-standalone.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page on scaling Azure Service Fabric standalone clusters shows a Windows bias by referencing PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) and linking to a Windows Server-specific guide for scaling standalone clusters. There are no Linux-specific examples, commands, or guidance, and Windows tools are mentioned exclusively for critical cluster operations.
Recommendations
  • Add equivalent Linux instructions for querying and updating cluster configuration, such as using Service Fabric CLI (sfctl) or REST APIs.
  • Provide examples for scaling standalone clusters on Linux, including relevant commands and configuration steps.
  • Clarify if standalone clusters are supported on Linux, and if not, explicitly state Windows-only support to avoid confusion.
  • If Linux is supported, ensure parity in documentation for node management and configuration upgrades.
GitHub Create Pull Request
Service Fabric Upgrade an Azure Service Fabric standalone cluster ...ce-fabric/service-fabric-cluster-upgrade-standalone.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page references Windows-specific upgrade procedures and tools (e.g., Patch Orchestration Application for Windows) and links to upgrade/configuration guides with 'windows-server' in their URLs. There are no explicit Linux examples, and Linux upgrade/configuration paths are not mentioned or linked, creating friction for Linux users managing Service Fabric standalone clusters.
Recommendations
  • Add explicit guidance and links for Linux-based Service Fabric standalone clusters, including upgrade and configuration procedures.
  • Ensure that references to upgrade/configuration guides are platform-neutral or provide separate links for Windows and Linux.
  • Mention whether features like Patch Orchestration Application are available for Linux, and if not, suggest alternatives or clarify limitations.
  • Include Linux-specific examples and instructions where applicable, especially for cluster configuration and upgrade steps.
GitHub Create Pull Request
Service Fabric Azure Service Fabric dynamic node tags ...tps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-node-tagging.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page provides PowerShell examples for managing node tags and service requirements, but does not offer equivalent CLI or scripting examples for Linux/macOS users (e.g., Bash, Azure CLI). PowerShell is a Windows-centric tool, and its exclusive use here creates friction for non-Windows users. There is no mention of Linux-native tools or cross-platform alternatives for these operations.
Recommendations
  • Add Azure CLI examples for managing node tags and service requirements, as Azure CLI is cross-platform.
  • If REST APIs are available for these operations, provide explicit curl or HTTP request examples for Linux/macOS users.
  • Mention whether PowerShell Core (pwsh) is supported on Linux/macOS for these commands, and clarify any limitations.
  • Consider including Bash or shell script examples if relevant.
  • Clearly indicate if certain operations are only possible via PowerShell, and provide guidance for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Secure an Azure Service Fabric cluster ...cles/service-fabric/service-fabric-cluster-security.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page for securing an Azure Service Fabric cluster demonstrates moderate Windows bias. Windows Server clusters and Windows security mechanisms (Kerberos, group Managed Service Accounts, Windows certificate services, MakeCert.exe) are referenced frequently and often before or instead of Linux equivalents. Standalone cluster security is discussed only for Windows, with no mention of Linux standalone clusters or their security setup. Certificate creation instructions and recommendations are Windows-centric, and Linux-specific guidance is largely absent.
Recommendations
  • Add explicit guidance for securing standalone Linux Service Fabric clusters, including certificate setup and client authentication.
  • Include Linux-focused examples and instructions for certificate creation (e.g., using OpenSSL instead of MakeCert.exe or Windows certificate services).
  • Clarify whether standalone Linux clusters are supported and, if so, provide links or sections for their security configuration.
  • Balance references to Windows tools with Linux equivalents, such as mentioning OpenSSL for certificate management.
  • Ensure recommendations and best practices are platform-neutral where possible, or clearly indicate platform-specific steps.
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 exhibits a moderate Windows bias. All deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) without any mention of Azure CLI equivalents or Bash scripting. Application packaging instructions rely on Visual Studio, a Windows-centric tool, and do not provide alternatives for Linux/macOS users. The workflow assumes familiarity with Windows tools and patterns, and Linux options are omitted entirely.
Recommendations
  • Add Azure CLI examples for deployment, upgrade, and deletion tasks alongside PowerShell examples.
  • Provide instructions for packaging Service Fabric applications using cross-platform tools (e.g., dotnet CLI, sfctl, or manual zip commands) instead of only Visual Studio.
  • Include guidance for Linux/macOS users, such as using Bash or cross-platform editors.
  • Clearly indicate when a step is Windows-only and offer Linux/macOS alternatives where possible.
GitHub Create Pull Request
Service Fabric Upgrading Azure Service Fabric clusters ...icles/service-fabric/service-fabric-cluster-upgrade.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation generally avoids explicit Windows-only instructions, but there are subtle biases. In the 'Upgrading OS images for cluster nodes' section, the only linked guidance is for patching Windows operating systems, with no mention or link for Linux-based clusters. Additionally, the 'Patch Orchestration Application (POA)' is described as a solution for OS patching, but only in the context of Windows. Throughout the page, when mentioning tools for management (e.g., PowerShell/Azure CLI), PowerShell is listed first, which may suggest a Windows-first approach. There are no explicit Linux-specific examples or references, and Linux parity for OS image upgrades is not addressed.
Recommendations
  • Add a parallel section or link for upgrading or patching Linux-based Service Fabric cluster nodes, if supported.
  • When listing management tools (e.g., PowerShell/Azure CLI), alternate the order or clarify that both are supported equally.
  • Explicitly state if certain features (such as POA or OS patching) are Windows-only, and provide Linux alternatives or note if not applicable.
  • Include Linux-specific examples or references where appropriate, especially in sections discussing OS upgrades and management.
GitHub Create Pull Request
Service Fabric Manage apps for multiple environments ...e-fabric-manage-multiple-environment-app-configuration.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page presents Windows/PowerShell examples and tools first and in more detail, with limited mention of Linux equivalents. PowerShell cmdlets are highlighted, and Visual Studio workflows (Windows-centric) are described, while Linux-native workflows (e.g., sfctl, Jenkins) are mentioned briefly or without example. There are no explicit Linux/macOS command examples or guidance.
Recommendations
  • Add explicit Linux/macOS command-line examples for common tasks, such as using sfctl and shell scripts.
  • Provide sample scripts or workflows for Linux environments, including how to use environment variables and parameter files.
  • Ensure Jenkins and other cross-platform CI/CD tools are given equal prominence and detailed examples.
  • Clarify which tools are cross-platform and which are Windows-only, to help users choose the right workflow.
GitHub Create Pull Request
Service Fabric Scalability of Service Fabric services .../service-fabric/service-fabric-concepts-scalability.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides code examples and administrative patterns primarily using PowerShell, which is a Windows-centric tool. No equivalent Linux command-line examples (such as Bash, CLI, or REST API) are given. Windows tools and PowerShell cmdlets are mentioned first and exclusively, creating friction for Linux users who may not have access to PowerShell or prefer native Linux tooling. While the page does mention Linux in the 'Choosing a platform' section, it does not provide Linux-specific operational guidance or parity in examples.
Recommendations
  • Add equivalent Linux command-line examples using Bash, Azure CLI, or REST API for service creation, updates, and scaling operations.
  • Mention Linux-native tools and patterns alongside PowerShell, not just in the platform comparison section.
  • Clarify which operations can be performed on Linux clusters and provide links or references to Linux-specific documentation.
  • Consider reordering examples so that Windows and Linux approaches are presented together, or alternate which is shown first.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Events ...es/service-fabric/service-fabric-diagnostics-events.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page for Azure Service Fabric Events primarily references Windows-centric logging mechanisms (ETW/Windows Event logs, Windows Azure diagnostics agent) and does not mention Linux equivalents or provide Linux-specific guidance. Windows tools and patterns are discussed first and exclusively, with no examples or instructions for accessing Service Fabric events on Linux clusters.
Recommendations
  • Add information about how Service Fabric events are logged and accessed on Linux clusters, including supported logging mechanisms (e.g., stdout, syslog, Azure Monitor integration for Linux).
  • Provide Linux-specific examples or clarify any differences in event access/configuration between Windows and Linux clusters.
  • Mention any limitations or differences in event availability or tooling for Linux Service Fabric clusters.
  • Ensure parity in documentation by referencing both Windows and Linux approaches where applicable.
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, mentions Visual Studio and ApplicationManifest.xml (Windows-centric patterns), and does not offer Linux CLI or cross-platform alternatives. While the page acknowledges Linux support and its limitations, practical guidance and examples are heavily Windows-focused, creating friction for Linux users.
Recommendations
  • Add equivalent Linux CLI examples (e.g., Azure CLI, Bash scripts) for setting DNS names and managing Service Fabric services.
  • Clarify how Linux users can accomplish tasks that are shown with PowerShell or ApplicationManifest.xml, including any limitations or required tools.
  • Provide guidance for enabling DNS service on Linux clusters using ARM templates, including any Linux-specific considerations.
  • Mention and link to Linux-compatible editors and workflows for editing manifests, rather than only referencing Visual Studio.
  • Explicitly state which features or steps are Windows-only and offer alternatives or workarounds for Linux users where possible.
GitHub Create Pull Request
Service Fabric Package an existing executable to Azure Service Fabric ...abric/service-fabric-guest-executables-introduction.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page shows a mild Windows bias. It references the Service Fabric SDK schema location using a Windows file path and does not mention Linux equivalents or paths. The use of Visual Studio as a primary tool is also Windows-centric, though it does mention command-line utilities. There are no explicit Linux/macOS examples or instructions, and the documentation does not clarify cross-platform packaging steps.
Recommendations
  • Add information about the location of Service Fabric SDK schema files on Linux/macOS, or clarify if the SDK is only available on Windows.
  • Include explicit instructions or examples for packaging and deploying guest executables using cross-platform tools (e.g., Azure CLI, Service Fabric CLI) where possible.
  • Mention and link to Linux/macOS-compatible development environments or tools if supported.
  • Clarify in the introduction if certain steps or tools (like Visual Studio) are Windows-only, and provide alternatives for other platforms if available.
GitHub Create Pull Request
Service Fabric Azure Service Fabric hosting model ...rticles/service-fabric/service-fabric-hosting-model.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides PowerShell examples and references for managing Service Fabric services, with no equivalent Linux CLI or cross-platform examples. PowerShell is presented as the primary tooling for service creation and management, and REST API and .NET SDK are mentioned, but Linux-native tools (such as sfctl or Azure CLI) are not referenced. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer platform-agnostic tools.
Recommendations
  • Add examples using sfctl (Service Fabric CLI), which is cross-platform and commonly used on Linux/macOS.
  • Include Azure CLI examples where applicable for service creation and management.
  • Clarify that PowerShell examples are Windows-specific and provide alternative instructions for Linux/macOS users.
  • Reorder examples so that REST API or cross-platform CLI examples are shown before or alongside PowerShell.
  • Link to documentation for sfctl and Azure CLI usage with Service Fabric.
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 page references PowerShell as the primary example for interacting with Service Fabric clusters and retrieving the cluster manifest. It also links to a PowerShell-based deployment guide as the main 'Next steps'. While Service Fabric is cross-platform, the documentation prioritizes Windows/PowerShell tools and does not provide equivalent Linux/macOS CLI or scripting examples.
Recommendations
  • Add examples using Azure CLI or Service Fabric CLI (sfctl) for Linux/macOS users, especially for tasks like retrieving the cluster manifest and deploying/removing applications.
  • Include links to Linux/macOS-specific documentation or guides alongside PowerShell references.
  • Mention cross-platform tooling (e.g., sfctl, REST API) earlier in the documentation, not just as an afterthought.
  • Provide sample commands for both Windows (PowerShell) and Linux/macOS (bash/CLI) wherever possible.
GitHub Create Pull Request
Service Fabric Azure Service Fabric container application manifest examples ...abric/service-fabric-manifest-example-container-app.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page for Azure Service Fabric container application manifest examples demonstrates a Windows bias. The manifest examples are explicitly based on a Windows Server 2016 container sample, and several instructions reference Windows-specific tools and patterns (e.g., using 'winver' to get the OS build version). There is no mention of Linux-based Service Fabric clusters, nor are there Linux-specific manifest examples or guidance. Some explanations (such as certificate handling) mention both Windows and Linux, but the overall focus and examples are Windows-centric.
Recommendations
  • Provide equivalent manifest examples based on Linux container samples, or clarify if Linux clusters are not supported for these scenarios.
  • When referencing OS build versions, include instructions for obtaining the build/version on Linux (e.g., 'cat /etc/os-release' or 'uname -r').
  • Add notes or sections highlighting any differences or limitations when deploying to Linux-based Service Fabric clusters.
  • Ensure that any referenced sample repositories include Linux examples if Linux is supported.
  • Explicitly state in the introduction if the guidance is only applicable to Windows clusters, to set user expectations.
GitHub Create Pull Request
Service Fabric Reliable services app manifest examples ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-manifest-example-reliable-services-app.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page provides Service Fabric application and service manifest examples. While the manifest XML itself is platform-neutral, there are subtle indications of Windows bias: Windows tools (e.g., PowerShell) are mentioned as the default for service creation, and batch scripts (.bat) are used in examples. Windows-specific accounts (e.g., NetworkService, Administrators) are referenced, and Windows terminology appears before Linux equivalents. No explicit Linux examples or guidance are provided.
Recommendations
  • Add Linux-specific examples, such as using shell scripts (.sh) for SetupEntryPoint, alongside batch (.bat) examples.
  • Mention Linux user/group equivalents when describing security principals (e.g., use 'root' or custom Linux users/groups).
  • Provide instructions or references for creating services using Linux tools (e.g., Azure CLI, Bash) in addition to PowerShell.
  • Clarify which features and manifest elements are supported on Linux Service Fabric clusters, and note any platform-specific limitations.
  • Include a section or links for Linux/macOS users, highlighting differences and best practices.
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 numerous PowerShell-based deployment examples and references Windows-centric tools (e.g., RDP, 'C:\' paths, PowerShell commands) without offering equivalent Linux/macOS CLI (Azure CLI) or SSH examples. Windows tools and patterns are mentioned first and exclusively, and there are no Linux/macOS-specific instructions or parity for key deployment steps.
Recommendations
  • Add Azure CLI (az) examples alongside PowerShell for all deployment steps.
  • Include SSH instructions for accessing VMs, in addition to RDP.
  • Use platform-neutral file paths and terminology where possible.
  • Explicitly note any differences or requirements for Linux/macOS users.
  • Provide sample ARM template deployment commands for Linux/macOS environments.
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 explicit Windows paths and commands. No equivalent Linux or cross-platform CLI examples (such as Bash, Azure CLI, or REST with curl) are provided. PowerShell is presented as the primary scripting interface, and Windows-centric patterns (e.g., PS C:\> prompts) are used throughout. REST is mentioned but not exemplified, and there is no guidance for Linux/macOS users on how to perform similar tasks.
Recommendations
  • Add equivalent examples using Azure CLI or Bash scripts for health reporting, especially for REST endpoints.
  • Include sample REST calls using curl or HTTPie, showing how to report health from Linux/macOS environments.
  • Clarify which PowerShell commands are available cross-platform (PowerShell Core), and provide notes or alternatives for Linux/macOS users.
  • Reorder sections so that REST or cross-platform approaches are presented before or alongside PowerShell.
  • Explicitly mention any limitations or requirements for Linux/macOS users, and provide links to relevant tools or documentation.
GitHub Create Pull Request
Service Fabric Define Service Configuration in StartupServices.xml for a Service Fabric Application ...service-fabric/service-fabric-startupservices-model.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation is heavily focused on Visual Studio workflows (Build/Rebuild/F5/Ctrl+F5/Publish), which are Windows-centric. All examples and instructions reference Visual Studio and its UI, with no mention of Linux/macOS equivalents or CLI-based workflows. The only alternative deployment methods mentioned are ARM templates and PowerShell cmdlets, but these are referenced briefly and without example parity. There are no Linux/macOS-specific instructions or examples, and the documentation implicitly assumes a Windows development environment.
Recommendations
  • Add explicit guidance for Linux/macOS users, including how to manage service configuration and deployment without Visual Studio.
  • Provide CLI-based examples (using Azure CLI, Service Fabric CLI, or PowerShell Core where cross-platform) for creating and deploying applications with StartupServices.xml.
  • Clarify which features are Visual Studio/Windows-only and offer alternative workflows for non-Windows environments.
  • Include screenshots or instructions for Linux/macOS development tools (e.g., VS Code, command-line workflows).
GitHub Create Pull Request
Service Fabric Service communication with the ASP.NET Core ...vice-fabric-reliable-services-communication-aspnetcore.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation covers both Windows-only (HTTP.sys) and cross-platform (Kestrel) web servers for ASP.NET Core in Service Fabric. However, it gives extensive coverage to HTTP.sys, a Windows-only technology, including detailed examples and endpoint configuration instructions. Windows-specific tools like netsh are mentioned, and Windows platform limitations are called out. Kestrel, the cross-platform option, is also well documented and recommended for Linux scenarios, but Windows tools and patterns (such as HTTP.sys and netsh) are presented first and in greater detail. There are no explicit Linux/macOS-specific examples or troubleshooting tips, and some configuration guidance (e.g., endpoint registration) is Windows-centric.
Recommendations
  • Add explicit Linux/macOS examples and troubleshooting tips, especially for Service Fabric clusters running on Linux.
  • Clarify which steps and configurations are Windows-only versus cross-platform, and highlight Linux compatibility in relevant sections.
  • Present Kestrel (the cross-platform option) before HTTP.sys in examples and guidance, or clearly indicate when Windows-only features are being discussed.
  • Include notes or links to Linux-specific Service Fabric documentation where available.
  • Avoid mentioning Windows tools (e.g., netsh) without Linux equivalents or alternatives.
GitHub Create Pull Request
Virtual Machine Scale Sets Networking for Azure Virtual Machine Scale Sets ...ne-scale-sets/virtual-machine-scale-sets-networking.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for most tasks, but PowerShell examples are often presented before CLI examples. In some sections, PowerShell is the only scripting language shown (e.g., querying public IPs), and CLI examples are not always as prominent. There are no Linux-specific shell examples (e.g., Bash), but the CLI is cross-platform. The documentation references both Windows and Linux for Accelerated Networking, but PowerShell is generally associated with Windows, and its prominence may create friction for Linux/macOS users.
Recommendations
  • Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and more accessible to Linux/macOS users.
  • Ensure all PowerShell examples have equivalent Azure CLI examples.
  • Where possible, include Bash shell snippets for common tasks to further improve Linux parity.
  • Clarify that Azure CLI commands work on all platforms, and highlight this in introductory sections.
  • Add links to Linux/macOS-specific guidance where relevant.
GitHub Create Pull Request
Service Fabric Fault Analysis Service overview .../service-fabric/service-fabric-testability-overview.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page provides usage instructions for C# (via the Microsoft.ServiceFabric NuGet package) and PowerShell (via the Service Fabric SDK and PowerShell module). There are no Linux/macOS CLI examples or references to cross-platform tools such as Azure CLI or REST APIs. PowerShell, which is traditionally Windows-centric, is mentioned as the primary scripting interface, and no Linux-specific guidance is given.
Recommendations
  • Add examples for using the Fault Analysis Service via Azure CLI or REST API, if available, to support Linux/macOS users.
  • Clarify whether PowerShell Core (cross-platform) is supported, and provide installation instructions for Linux/macOS if so.
  • Include guidance for invoking Fault Analysis Service actions from non-Windows environments, such as using Python SDKs or other cross-platform tools.
  • Explicitly state any platform limitations if the Fault Analysis Service is only accessible via Windows 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 scale sets, but does not provide explicit Linux/bash examples or parity for PowerShell commands. Azure PowerShell is mentioned alongside Azure CLI, but examples and links for PowerShell are provided without equivalent Linux/bash or cross-platform CLI examples. Windows-specific scenarios (activation, updates) are listed before Linux equivalents, and Windows tools are referenced more prominently. There are no explicit Linux-focused migration steps or examples.
Recommendations
  • Add explicit bash/Linux shell examples alongside PowerShell examples, especially for Azure CLI usage.
  • Ensure that CLI examples are shown first or equally with PowerShell, as Azure CLI is cross-platform.
  • Provide links to Linux-specific documentation or migration guides where relevant.
  • When listing scenarios (e.g., outbound connectivity requirements), alternate or balance Windows and Linux mentions.
  • Clarify that Azure CLI is cross-platform and suitable for Linux/macOS users.
GitHub Create Pull Request
Virtual Machines Restrict managed disks from being imported or exported ...tual-machines/disks-restrict-import-export-overview.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides both Azure CLI and PowerShell links for configuring the NetworkAccessPolicy, but references to PowerShell and Windows-centric tools appear first and more prominently. The custom RBAC role section links only to a PowerShell-based guide, omitting CLI or ARM template alternatives. There are no explicit Linux/macOS examples or parity in the RBAC section, and PowerShell is mentioned before CLI in the network access policy section.
Recommendations
  • Add links and examples for creating custom RBAC roles using Azure CLI and/or ARM templates, not just PowerShell.
  • Ensure CLI and PowerShell examples are presented together, or alternate which comes first.
  • Explicitly mention that all steps can be performed on Linux/macOS using Azure CLI, and provide sample commands.
  • Review all sections for Windows-first language and ensure Linux/macOS parity.
GitHub Create Pull Request
Virtual Machines Upload a VHD to Azure or copy a disk across regions - Azure CLI ...machines/linux/disks-upload-vhd-to-managed-disk-cli.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides both Linux and Windows context and includes bash scripting for disk copy operations. However, the AzCopy example for uploading a VHD is shown only with a Windows-style path and AzCopy.exe invocation, with no explicit Linux/macOS equivalent. The AzCopy command is not shown with a Linux path or executable name, and there is no mention of how to run AzCopy on Linux/macOS. Additionally, the first and only explicit upload example uses Windows conventions, which may create friction for Linux/macOS users.
Recommendations
  • Add explicit AzCopy upload examples for Linux/macOS, using a Linux path (e.g., '/home/user/mydisk.vhd') and the appropriate executable name (e.g., './azcopy' or 'azcopy').
  • Clarify that AzCopy is cross-platform and provide download/run instructions for Linux/macOS.
  • Where file paths are referenced, show both Windows and Linux/macOS path formats.
  • Consider mentioning any Linux-specific considerations for preparing VHDs, if applicable.
GitHub Create Pull Request
Virtual Machines Run scripts in a Linux VM in Azure using managed Run Commands ...articles/virtual-machines/linux/run-command-managed.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
Although the page is focused on Linux VMs, there is notable Windows bias in several areas: PowerShell examples and tools (e.g., Set-AzVMRunCommand, New-AzStorageBlobSASToken) are heavily featured, often before or instead of Azure CLI equivalents. REST API and ARM template examples use Windows-centric script syntax (e.g., Write-Host, .ps1 files) without Linux/bash alternatives. Some explanations reference Windows-specific behaviors (e.g., 'Secondary Logon' service) and do not clarify Linux distinctions. Several advanced scenarios (streaming output to blobs, parameter passing) are only shown in PowerShell, with no CLI or Linux-native scripting examples.
Recommendations
  • Add Azure CLI examples for all advanced scenarios currently only shown in PowerShell (e.g., streaming output/error to blobs, parameter passing, running as a different user).
  • In REST API and ARM template sections, provide Linux/bash script examples alongside Windows/PowerShell (.ps1) examples.
  • Clarify when instructions or notes are Windows-specific, and provide Linux alternatives or explanations.
  • Ensure Linux/bash syntax is used in examples where the context is Linux VMs (e.g., use echo, bash scripts, .sh files instead of Write-Host, .ps1).
  • Reorder sections so Azure CLI (Linux-friendly) examples appear before PowerShell, or at least equally.
  • Where PowerShell tools are mentioned (e.g., New-AzStorageBlobSASToken), provide CLI alternatives or links.
GitHub Create Pull Request
Service Fabric Architecture of Azure Service Fabric ...articles/service-fabric/service-fabric-architecture.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page for 'Architecture of Azure Service Fabric' exhibits mild Windows bias. The management subsystem section explicitly mentions PowerShell cmdlets as a primary means of managing Service Fabric, without referencing Linux/macOS equivalents (such as CLI tools or REST APIs). Additionally, Windows security is mentioned alongside X509 certificates in the transport subsystem, but Linux authentication mechanisms are not discussed. The overall architectural description is platform-neutral, but administrative tooling is presented with a Windows-first perspective.
Recommendations
  • Mention cross-platform management tools (such as Azure CLI, REST APIs, or Service Fabric CLI) alongside PowerShell cmdlets.
  • Clarify if PowerShell cmdlets are available on Linux/macOS via PowerShell Core, or provide alternative instructions for Linux users.
  • Discuss Linux authentication mechanisms (such as certificate-based authentication) in the transport subsystem, or clarify platform support.
  • Add explicit notes or links to Linux/macOS documentation for managing Service Fabric clusters.
GitHub Create Pull Request
Service Fabric Overview of Service Fabric and containers ...s/service-fabric/service-fabric-containers-overview.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides a balanced overview of Service Fabric container support for both Linux and Windows. However, there is a slight bias in the order and emphasis: Windows container runtimes and tools (Mirantis Container Runtime, DockerEE) are listed in detail, while Linux only mentions Docker. Windows scenarios (such as IIS lift-and-shift) are described first in the 'Scenarios for using containers' section, and Windows-specific links are often shown before Linux equivalents. There are no missing Linux examples, and Linux support is clearly documented.
Recommendations
  • List Linux container runtimes and tools with equal detail as Windows (e.g., mention containerd, Podman if relevant).
  • Present Linux and Windows examples in parallel or alternate order to avoid 'Windows first' bias.
  • Add more Linux-specific scenarios (e.g., Apache, NGINX, Python workloads) alongside Windows/IIS examples.
  • Ensure that Linux tutorials and links are given equal prominence in 'Next steps' and throughout the page.
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 (a Windows-centric tool) is consistently presented alongside CLI, and in some sections, PowerShell examples are shown before or with equal prominence to CLI. There are no Linux-specific shell examples (e.g., Bash), but Azure CLI is cross-platform. No Windows-only tools or patterns are mentioned, and the content is not Windows-specific.
Recommendations
  • Explicitly note that Azure CLI commands work on Linux, macOS, and Windows, and recommend CLI for cross-platform users.
  • Consider showing Azure CLI examples before PowerShell, or labeling PowerShell as 'Windows only' where appropriate.
  • Add a brief note for Linux/macOS users clarifying that PowerShell examples are for Windows, and Azure CLI is the preferred option for non-Windows environments.
  • If relevant, include Bash scripting examples or highlight CLI usage in Linux/macOS terminals.
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 'Create zone spanning or zonal scale sets'), PowerShell is listed before ARM template examples. There is a slight bias in listing Windows-oriented tools (PowerShell) alongside cross-platform tools (CLI), and PowerShell examples are detailed and prominent. There are no missing Linux examples, as CLI and ARM templates are cross-platform, and the portal instructions are platform-agnostic.
Recommendations
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users, while PowerShell is primarily for Windows (though PowerShell Core is available for Linux/macOS).
  • Consider listing Azure CLI examples before PowerShell examples to emphasize Linux parity.
  • Add clarifying notes about the platform compatibility of each tool.
  • Ensure that ARM template examples reference both Linux and Windows quick-start links equally, as is already done.
GitHub Create Pull Request
Virtual Machines Deprovision or generalize a VM before creating an image ...docs/blob/main/articles/virtual-machines/generalize.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides clear, separate instructions for both Linux and Windows VM generalization. However, the Windows section includes more detailed prerequisites and troubleshooting steps, and Windows PowerShell/Command Prompt examples are shown first in some places. The Linux section is concise and relies heavily on waagent, but does provide links to distro-specific guides. Both OSes are covered, but Windows examples and tools are sometimes presented with more depth.
Recommendations
  • Expand Linux prerequisites to match the detail level of Windows (e.g., common issues, troubleshooting).
  • Provide more explicit Linux CLI examples for deprovisioning and generalizing, including error handling.
  • Ensure parity in guidance for post-generalization steps (e.g., marking VM as generalized, disk handling).
  • Consider listing Linux instructions first, or alternating order in future revisions.
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. However, PowerShell is presented as a primary method alongside CLI, despite PowerShell being predominantly a Windows tool. The CLI example is given first, which is positive, but the PowerShell section is equally prominent and may imply parity, even though PowerShell usage on Linux/macOS is less common. No Linux-specific tools or shell examples (e.g., Bash) are provided, but Azure CLI is cross-platform.
Recommendations
  • Clarify that PowerShell is primarily for Windows users, and Azure CLI is recommended for Linux/macOS.
  • Consider adding a Bash shell example or note that Azure CLI commands work natively in Bash on Linux/macOS.
  • Explicitly state platform compatibility for each example (e.g., 'Azure CLI: Windows, Linux, macOS; PowerShell: Windows, Linux (with PowerShell Core)').
  • If possible, provide links or guidance for installing Azure CLI and PowerShell on Linux/macOS.
GitHub Create Pull Request
Service Fabric Deny assignment policy for Service Fabric managed clusters ...cles/service-fabric/managed-cluster-deny-assignment.md
Low 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 and links primarily using Azure PowerShell modules, with PowerShell mentioned before Azure CLI and sfctl. While Azure PowerShell is cross-platform, its prominence and the lack of explicit Linux/macOS command examples may create friction for non-Windows users. The page does mention Azure CLI and sfctl, but PowerShell is referenced first and most often.
Recommendations
  • Add explicit Azure CLI examples for key operations (e.g., deleting NodeTypes, restarting/reimaging scale sets) alongside PowerShell examples.
  • Ensure that CLI and sfctl commands are shown before or equally with PowerShell in best practice sections.
  • Clarify that Azure PowerShell and Azure CLI are both cross-platform, and provide guidance for Linux/macOS users.
  • Where possible, include sample commands for sfctl (which is Python-based and Linux-friendly) for relevant tasks.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Docker Compose Deployment Preview ...ticles/service-fabric/service-fabric-docker-compose.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both PowerShell and Service Fabric CLI (sfctl) examples for deploying Docker Compose files to Azure Service Fabric. However, PowerShell commands are presented first and in greater detail, with explicit command blocks for each operation. The CLI section is presented second, and while it covers the same operations, it is less emphasized. There is no mention of Linux-specific tools or patterns, but the inclusion of sfctl commands does provide Linux/macOS parity. No Linux-specific example or guidance is given, and PowerShell is a Windows-centric tool.
Recommendations
  • Present CLI (sfctl) examples before PowerShell, or at least equally, to avoid Windows-first bias.
  • Explicitly mention that sfctl is cross-platform and suitable for Linux/macOS users.
  • Add a brief note or section for Linux/macOS users, clarifying that PowerShell commands are Windows-specific and that sfctl is the recommended tool for non-Windows environments.
  • Consider including example shell commands for Linux/macOS where relevant (e.g., using Bash).
GitHub Create Pull Request
Service Fabric Overview of Azure Service Fabric ...ain/articles/service-fabric/service-fabric-overview.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation mentions both Windows and Linux support for Service Fabric, and provides parity in describing development environments for each. However, in the 'Any OS, any cloud' section, Windows development (with Visual Studio and PowerShell) is described first, followed by Linux development (with Eclipse and Yeoman). The quickstart link also points to a .NET-based tutorial, which may be more Windows-centric, though .NET Core is cross-platform.
Recommendations
  • Alternate the order of Windows and Linux mentions to avoid implicit prioritization.
  • Provide quickstart links for both Windows (.NET) and Linux (Java/.NET Core) users.
  • Explicitly state that .NET Core examples are cross-platform when referenced.
  • Ensure that Linux tooling (Eclipse, Yeoman) is given equal prominence and example coverage as Windows tooling (Visual Studio, PowerShell).
GitHub Create Pull Request
Service Fabric Learn Azure Service Fabric terminology ...es/service-fabric/service-fabric-technical-overview.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page is generally cross-platform and describes Service Fabric concepts applicable to both Windows and Linux. However, there is a mild Windows bias in the 'Infrastructure concepts' section, where Windows-specific tools (FabricHost.exe, Fabric.exe, FabricGateway.exe) are mentioned as auto-start Windows services, without clarifying Linux equivalents or behaviors. Additionally, Windows terminology (EXE/DLL) is used in the 'Code package' section before mentioning Linux guest executables. The order of examples and explanations tends to reference Windows first, with Linux support noted later.
Recommendations
  • Clarify that FabricHost.exe, Fabric.exe, and FabricGateway.exe are also present on Linux nodes, and describe their startup mechanisms on Linux (e.g., systemd services) if applicable.
  • When mentioning executable formats (EXE/DLL), add Linux equivalents (e.g., ELF binaries, .so files) to ensure parity.
  • Where Windows services or tools are referenced, add a brief note about Linux equivalents or behaviors.
  • Consider alternating the order of Windows and Linux examples or explicitly stating cross-platform support where relevant.
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: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation is generally platform-neutral, focusing on .NET serialization concepts relevant to Azure Service Fabric. However, in the 'Next steps' section, Windows-centric tools (Visual Studio and PowerShell) are mentioned for application upgrades, with no Linux/macOS alternatives or parity. PowerShell is referenced as a primary upgrade method, and Visual Studio is listed before any CLI or cross-platform options.
Recommendations
  • Add references to cross-platform upgrade methods, such as Azure CLI or Service Fabric CLI (sfctl), especially for Linux/macOS users.
  • Include links or examples for upgrading applications on Linux/macOS, or clarify if PowerShell/Visual Studio are Windows-only and provide alternatives.
  • Consider listing cross-platform tools before Windows-specific ones, or grouping them by platform for clarity.
GitHub Create Pull Request
Virtual Machine Scale Sets Spot Placement Score ...les/virtual-machine-scale-sets/spot-placement-score.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation provides platform-specific instructions for accessing the Spot Placement Score via Azure CLI and Azure PowerShell, with PowerShell examples appearing after CLI. However, both CLI and PowerShell are cross-platform tools, and no Windows-specific tools or patterns are prioritized. No explicit Windows bias is present, but minor 'windows_first' bias is detected as PowerShell is listed after CLI, which is often associated with Windows, though both are available on Linux/macOS.
Recommendations
  • Clarify that Azure CLI and Azure PowerShell are available on Linux/macOS as well as Windows.
  • Consider adding explicit notes or links to installation guides for Azure CLI and PowerShell on Linux/macOS.
  • If possible, provide sample commands for Bash or other Linux-native shells to reinforce parity.
  • Ensure that all instructions and examples are platform-neutral unless a platform-specific difference exists.
GitHub Create Pull Request
Virtual Machine Scale Sets Rolling upgrades with MaxSurge for Virtual Machine Scale Sets ...hine-scale-sets/virtual-machine-scale-sets-maxsurge.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides configuration examples for rolling upgrades with MaxSurge using Azure Portal, CLI, PowerShell, and ARM templates. While the CLI example is cross-platform, the PowerShell example is Windows-specific and is given equal prominence. There is no explicit Linux bias, but PowerShell is highlighted as a main method, which may create friction for Linux/macOS users. The CLI example is not shown first; Portal is, then CLI, then PowerShell, which is a minor 'windows_first' bias.
Recommendations
  • Clarify that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
  • Consider adding Bash script examples or noting that PowerShell is Windows-specific.
  • Explicitly mention that PowerShell examples are for Windows users, and CLI is recommended for Linux/macOS.
  • Ensure parity in instructions for Linux/macOS users, such as troubleshooting or environment setup notes.
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 areas where Windows bias is evident: PowerShell examples are often presented before or alongside Bash, Windows-specific extension types (ApplicationHealthWindows) are used in sample code, and Windows tools (PowerShell cmdlets) are given equal prominence to cross-platform CLI commands. The REST API examples use ApplicationHealthWindows as the default extension type, even though ApplicationHealthLinux is also supported. The documentation does not omit Linux examples, but Windows terminology and tools are frequently mentioned first or in parallel, creating minor friction for Linux/macOS users.
Recommendations
  • Ensure Linux examples (Bash/Python) are shown before or equally with Windows/PowerShell examples, especially in critical sections.
  • Use ApplicationHealthLinux as the default extension type in generic sample code, or show both Linux and Windows variants.
  • Clarify in REST/CLI examples that both ApplicationHealthLinux and ApplicationHealthWindows are supported, and provide explicit Linux-focused samples.
  • Where possible, avoid using Windows-specific terminology or tools unless necessary, and always provide Linux equivalents.
  • Consider grouping examples by platform, or using tabs to clearly distinguish Linux and Windows workflows.
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 presented alongside CLI and REST, and the CLI is shown first in most cases. However, PowerShell is a Windows-centric tool, and its inclusion does not disadvantage Linux/macOS users since the CLI and REST examples are fully cross-platform and appear before PowerShell. There are no Windows-specific tools or patterns mentioned exclusively or before Linux equivalents, and no critical steps are Windows-only.
Recommendations
  • Maintain the current order of examples, with Azure CLI and REST API shown before PowerShell.
  • Clarify in the PowerShell section that it is primarily for Windows users, and recommend Azure CLI or REST for Linux/macOS users.
  • Ensure parity in example detail and completeness across CLI, REST, and PowerShell sections.
  • Consider adding a brief note at the top indicating that Azure CLI and REST API are fully cross-platform, while PowerShell is Windows-centric.
GitHub Create Pull Request
Virtual Machines Azure VM Extensions and Features for Linux ...articles/virtual-machines/extensions/features-linux.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all major tasks, but consistently presents PowerShell examples immediately after CLI, and sometimes with more detailed output. There are no missing Linux examples or Windows-only tools, but PowerShell is emphasized alongside CLI throughout, even though PowerShell is less common on Linux. The ordering (CLI first, then PowerShell) is good, but the repeated PowerShell focus may create minor friction for Linux users.
Recommendations
  • Consider clarifying that Azure PowerShell is cross-platform but less common on Linux, and recommend CLI as the primary method for Linux users.
  • Where possible, highlight Bash/CLI as the default for Linux, and mention PowerShell as an alternative.
  • Add explicit notes about PowerShell availability on Linux, or link to installation instructions for Linux users.
  • Review output examples to ensure parity between CLI and PowerShell, and avoid implying PowerShell is required for Linux tasks.
GitHub Create Pull Request
Virtual Machines Secure Azure Managed Disk Downloads and Uploads ...icles/virtual-machines/disks-secure-upload-download.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for securing managed disk uploads/downloads, but PowerShell (a Windows-centric tool) is presented before CLI in several sections. Portal, PowerShell, and CLI are all referenced, but PowerShell is often listed before CLI, which may subtly prioritize Windows users. However, Linux/macOS users are not blocked from completing tasks, as CLI instructions are present and relevant links for Linux-specific tasks are included.
Recommendations
  • Alternate the order of PowerShell and CLI examples, or present CLI first to avoid implicit Windows prioritization.
  • Explicitly mention that Azure CLI works cross-platform and is recommended for Linux/macOS users.
  • Ensure that all critical tasks have both PowerShell and CLI examples, and clarify any platform-specific limitations.
  • Consider grouping PowerShell and CLI examples together, labeling them clearly for each platform.
GitHub Create Pull Request
Virtual Machines What's new in Azure Disk Storage ...blob/main/articles/virtual-machines/disks-whats-new.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The 'What's new in Azure Disk Storage' page is mostly platform-neutral, focusing on Azure Disk Storage features, regional availability, and enhancements. However, there are minor signs of Windows bias: some links and references point to Windows documentation first or exclusively, and Windows-specific documentation is sometimes mentioned before Linux equivalents. For example, the 'expand with Ultra Disks and Premium SSD v2' feature links to a Windows-specific article, and the 'LastOwnershipUpdateTime' property documentation links to a Windows page. Linux documentation is referenced in some places, but not always with equal prominence.
Recommendations
  • Ensure that all feature documentation links include both Windows and Linux versions, or use platform-neutral pages when possible.
  • When referencing platform-specific guides (e.g., expanding disks), mention both Windows and Linux articles equally and in parallel.
  • Review linked documentation to confirm Linux parity and add Linux/macOS examples where missing.
  • Avoid defaulting to Windows documentation unless the feature is Windows-only.
GitHub Create Pull Request
Virtual Machines NVIDIA GPU Driver Extension - Azure Linux VMs ...es/virtual-machines/extensions/hpccompute-gpu-linux.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation is focused on Linux VMs, but includes PowerShell examples for deploying the extension, and in some sections, PowerShell is presented before Azure CLI or Linux-native commands. This may create friction for Linux users, as PowerShell is not the default scripting environment on Linux, and Azure CLI is more commonly used. However, Linux-specific commands and troubleshooting steps are provided throughout, and the overall guidance is Linux-centric.
Recommendations
  • Move Azure CLI examples before PowerShell examples, as Azure CLI is the primary tool for Linux users.
  • Clearly indicate that PowerShell examples are optional and primarily for users who prefer PowerShell or are working cross-platform.
  • Add Bash shell script examples for common tasks, such as extension deployment and troubleshooting, to further improve Linux parity.
  • Ensure that all screenshots and walkthroughs use Linux environments and tools.
  • Consider removing PowerShell examples entirely, or placing them in a separate 'Windows users' section, since the extension is Linux-specific.
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 several sections (notably deployment and troubleshooting) present Azure PowerShell examples before Azure CLI, and provide more detailed PowerShell guidance. This ordering and emphasis may create friction for Linux users, who typically prefer Azure CLI or shell-based workflows. However, all critical tasks are also covered with Azure CLI, and Linux-specific details are well documented.
Recommendations
  • Present Azure CLI examples before Azure PowerShell in all sections, as CLI is more native to Linux environments.
  • Expand troubleshooting guidance to include more CLI-based commands and workflows, matching the detail given for PowerShell.
  • Add explicit notes clarifying that Azure CLI is recommended for Linux users, and PowerShell is optional.
  • Ensure all JSON and shell examples use Linux path conventions and syntax (e.g., avoid PowerShell-specific backslashes or quoting).
GitHub Create Pull Request
Virtual Machines Create an image definition and image version ...s/blob/main/articles/virtual-machines/image-version.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Linux and Windows guidance, but there is a subtle bias in example ordering and tool emphasis. In the PowerShell section, Windows examples are shown first and more prominently, while Linux is mentioned as an alternative. The CLI section is more neutral, but overall, Windows terminology and PowerShell are prioritized in some areas.
Recommendations
  • In PowerShell examples, show Linux usage first or provide parallel examples for both OS types.
  • Ensure that CLI and PowerShell sections equally highlight Linux and Windows scenarios, including explicit Linux-focused examples.
  • Where possible, clarify that both Linux and Windows are supported and provide links to OS-specific guidance directly in each example.
  • Review example ordering so Linux and Windows are alternated or presented together, rather than Windows first.
GitHub Create Pull Request
Virtual Machines Install VM Watch ...lob/main/articles/virtual-machines/install-vm-watch.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation provides parity for both Windows and Linux users, with CLI, PowerShell, and ARM template examples. However, in sections where screenshots are shown, Windows installations are presented first, followed by Linux. Additionally, PowerShell examples are included, which are Windows-centric, but CLI and ARM template examples are also provided, ensuring Linux users are not excluded.
Recommendations
  • Alternate the order of screenshots and examples so Linux is shown first in some sections.
  • Explicitly state that PowerShell is Windows-only and recommend Bash or CLI for Linux users.
  • Consider adding Bash script examples for Linux users alongside PowerShell.
  • Ensure that all instructions and validation steps are equally clear for both OS types.
GitHub Create Pull Request
Virtual Machines Create an Azure Image Builder Bicep file or ARM template JSON template .../articles/virtual-machines/linux/image-builder-json.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation provides extensive parity between Windows and Linux throughout, with clear sections and examples for both OS types. However, there are minor signs of Windows bias: PowerShell and Windows-specific tools are sometimes mentioned first or exclusively (e.g., PowerShell for checksum generation, WindowsRestart/WindowsUpdate customizers, and PowerShell validator examples), and Windows commands are occasionally shown before Linux equivalents. The guidance for generating SHA256 checksums and some validator examples reference PowerShell cmdlets before Linux commands. Windows customizers (PowerShell, WindowsRestart, WindowsUpdate) are described in detail, while Linux equivalents (Shell) are covered but less prominently. Overall, Linux users can complete all tasks, but may need to scroll past Windows-first content or adapt some instructions.
Recommendations
  • Ensure Linux and macOS examples (e.g., shell commands, checksum generation) are presented alongside or before Windows/PowerShell equivalents.
  • Where PowerShell is referenced for checksum generation, add Linux/macOS alternatives (e.g., sha256sum) in the same prominence.
  • In customizer and validator sections, balance the order and detail between Windows and Linux types.
  • Highlight Linux-specific customizers and validation options as much as Windows ones.
  • Consider a table or side-by-side comparison for OS-specific commands and tools to improve clarity.
GitHub Create Pull Request
Virtual Machines Create and upload a Red Hat Enterprise Linux VHD for use in Azure ...les/virtual-machines/linux/redhat-create-upload-vhd.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation covers multiple hypervisors (Hyper-V, KVM, VMware, Kickstart) for preparing a Red Hat Enterprise Linux VHD for Azure. However, in several sections, instructions for Hyper-V (a Windows-centric hypervisor) are presented first, and the workflow often references Hyper-V Manager as the primary example, with Linux-native hypervisors (KVM, VMware) following. There are also occasional references to Windows tools (e.g., Hyper-V Manager, convert-vhd cmdlet) before Linux alternatives, but Linux workflows and tools are thoroughly documented. No critical steps are Windows-only, and Linux users can complete all tasks.
Recommendations
  • Reorder sections so that Linux-native hypervisors (KVM, VMware, Kickstart) are presented before Hyper-V, or at least in parallel tabs.
  • When mentioning disk conversion tools, list Linux-native tools (e.g., qemu-img) before Windows tools (e.g., Hyper-V Manager, convert-vhd).
  • Clarify that Hyper-V instructions are for users on Windows, and highlight Linux-native workflows for Linux users.
  • Consider adding a summary table at the top showing parity between Windows and Linux tools/workflows for each step.
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: 2 bias types
Detected Bias Types
⚠ī¸ windows_reference ⚠ī¸ powershell_example
Summary
The documentation is focused on Linux VM time synchronization in Azure and provides extensive Linux-specific guidance, commands, and examples. However, there are minor signs of Windows bias: references to Windows Server 2016 time improvements and links to Windows documentation are given in the introduction and 'Next steps' sections, and a PowerShell example is provided for base64 encoding cloud-init (though the main cloud-init example is Linux-centric). No critical Linux examples are missing, and all configuration steps are Linux-oriented.
Recommendations
  • Move or minimize Windows Server references to a background section, clarifying their relevance to Linux users.
  • Provide a Linux shell command (e.g., `base64 cloud-config.txt`) for base64 encoding cloud-init files, alongside the PowerShell example.
  • Ensure 'Next steps' links prioritize Linux resources or clearly indicate Windows-specific links are for background only.
GitHub Create Pull Request
Virtual Machines Share VM images in a compute gallery ...in/articles/virtual-machines/shared-image-galleries.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation covers both Linux and Windows VM images, but there is evidence of Windows bias. PowerShell examples are given alongside Azure CLI, but PowerShell is a Windows-centric tool. Windows-specific tools and terminology (e.g., Sysprep, Windows upload instructions, Windows image links) are mentioned before or more prominently than Linux equivalents. In some cases, Windows links are listed first or separately, and PowerShell examples are provided even though Linux users typically use Bash/CLI. However, Linux-specific instructions (e.g., waagent for generalization, Linux upload links) are present, and Azure CLI examples are included, mitigating the bias.
Recommendations
  • Ensure Linux and Windows examples are presented with equal prominence, ideally side-by-side or in parallel sections.
  • When referencing tools, mention Linux equivalents (e.g., waagent) before or alongside Windows tools (e.g., Sysprep), not after.
  • Provide Bash or shell script examples for Linux users where PowerShell is used for Windows.
  • When linking to upload instructions or specialized image creation, list Linux and Windows links together, not with Windows first.
  • Clarify that Azure CLI is cross-platform and encourage its use for both Linux and Windows users.
GitHub Create Pull Request