← Back to Dashboard
262
Pages Scanned
87
Pages Flagged
262
Changed Pages
33.2%
% Pages Flagged

Scan Information

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

Finished At: 2026-02-10 18:44:36

Status: completed

Target Repo: Azure Compute

Current Phase: discovery

Files Queued: 262

Files Completed: 262

Problematic Pages

87 issues found
Service Fabric Initializer CodePackages in Service Fabric ...in/articles/service-fabric/initializer-codepackages.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation for Initializer CodePackages in Service Fabric is heavily focused on Windows containers. All examples use Windows container images, Windows file paths, and Windows command syntax (cmd, echo, type, ping). There is no mention of Linux container equivalents, nor are Linux examples or guidance provided. The documentation assumes the reader is deploying to Windows-based Service Fabric clusters and does not address Linux scenarios.
Recommendations
  • Add parallel examples for Linux containers, using Linux container images (e.g., Ubuntu, Alpine) and Linux command syntax (bash, echo, cat, etc.).
  • Clarify whether Initializer CodePackages are supported for Linux containers in Service Fabric. If not supported, explicitly state this limitation.
  • If Linux is supported, provide guidance on specifying Linux file paths and volume mounts, and show how to adapt the ServiceManifest and ApplicationManifest for Linux scenarios.
  • Ensure that introductory sections mention both Windows and Linux container support (if applicable), and link to relevant getting started guides for both platforms.
GitHub Create Pull Request
Service Fabric Azure Service Fabric reverse proxy ...articles/service-fabric/service-fabric-reverseproxy.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation for Azure Service Fabric reverse proxy is Windows-focused because the reverse proxy feature is not available for Linux clusters. The page clearly states this in the Supported Platforms note. All examples and configuration guidance are therefore implicitly Windows-only, and there are no Linux equivalents or workarounds provided.
Recommendations
  • Explicitly state early in the document that reverse proxy is not available for Linux clusters, and provide links or guidance for alternative service discovery or proxying approaches for Linux clusters.
  • Where possible, suggest Linux-compatible alternatives or clarify which Service Fabric features are available on Linux.
  • Consider adding a section on how Linux users can achieve similar functionality using other tools or patterns, if feasible.
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: 3 bias types
Detected Bias Types
⚠️ missing_linux_example ⚠️ windows_first ⚠️ windows_tools
Summary
Although the introduction claims Service Fabric clusters can run on both Windows Server and Linux, the documentation page exclusively lists Windows Server versions as supported operating systems for standalone clusters, and references Windows-specific security features and tools (Kerberos, group Managed Service Accounts, Active Directory). No Linux equivalents, examples, or instructions are provided, and Linux is explicitly stated as 'not yet supported' for standalone clusters.
Recommendations
  • Clarify in the introduction that standalone clusters are currently Windows-only, despite general Service Fabric support for Linux.
  • Remove or rephrase statements implying Linux parity for standalone clusters until Linux support is available.
  • When Linux support is added, provide equivalent Linux examples, instructions, and security guidance (e.g., certificate management, authentication methods, OS patching).
  • Explicitly state the scope of Windows-only support in the relevant sections to avoid confusion for Linux users.
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
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation is heavily focused on Windows-specific tools and workflows, particularly Visual Studio and PowerShell. All upgrade instructions and examples reference Visual Studio dialogs and PowerShell cmdlets, with no mention of Linux/macOS alternatives or cross-platform CLI tools. There are no examples or guidance for performing Service Fabric application upgrades from Linux or macOS environments.
Recommendations
  • Add instructions for upgrading Service Fabric applications using cross-platform tools such as Azure CLI or Service Fabric CLI (sfctl), where possible.
  • Include examples for Linux/macOS users, such as command-line workflows that do not require Visual Studio or PowerShell.
  • Clarify which steps are Windows-only and provide alternative approaches for non-Windows environments.
  • Reference documentation for Service Fabric management from Linux/macOS, if available.
GitHub Create Pull Request
Service Fabric Application upgrade: upgrade parameters ...abric/service-fabric-application-upgrade-parameters.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation page prioritizes Windows-centric tools (PowerShell, Visual Studio) in both structure and example detail. Parameters for PowerShell and Visual Studio are listed and explained first, with detailed examples and descriptions, while Linux/macOS equivalents (SFCTL/CLI) are covered later and with less depth. There are no explicit Linux/macOS command examples or walkthroughs in the main body, and PowerShell-specific patterns (e.g., hashtable syntax) are shown without Linux equivalents. The 'Next steps' section does link to Linux CLI documentation, but the main page content is notably Windows-focused.
Recommendations
  • Reorganize the documentation so that SFCTL (CLI) parameters and usage are presented alongside PowerShell/Visual Studio, or even first, to avoid Windows-first ordering.
  • Provide explicit Linux/macOS SFCTL command examples for common upgrade scenarios, including parameter overrides and health policy configuration.
  • When showing PowerShell-specific syntax (e.g., hashtable), also show the equivalent JSON or CLI syntax for SFCTL.
  • Clarify which tools are cross-platform and which are Windows-only, to help users choose the appropriate workflow.
  • Add a table or section comparing PowerShell, Visual Studio, and SFCTL workflows for application upgrades, highlighting platform compatibility.
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_tools ⚠️ missing_linux_example
Summary
The documentation is heavily focused on PowerShell-based workflows, referencing the Microsoft.ServiceFabric.Powershell.Http module and providing all command-line examples exclusively in PowerShell. There are no CLI, Bash, or cross-platform REST examples using tools like curl or az CLI, which creates friction for Linux/macOS users. The Service Fabric Explorer UI is mentioned, but all scripting and automation guidance assumes a Windows/PowerShell environment.
Recommendations
  • Provide equivalent examples using cross-platform tools such as curl for REST API calls.
  • Include guidance for using the Azure CLI (az sf) where possible, or note if such functionality is unavailable.
  • Clarify whether the PowerShell module can be used on PowerShell Core (pwsh) on Linux/macOS, and if so, provide installation instructions for those platforms.
  • If certain features are Windows-only, explicitly state this to set user expectations.
  • Add Bash or shell script examples for common tasks, especially for REST API interactions.
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 references PowerShell and Visual Studio as primary tools for application upgrades, both of which are traditionally Windows-centric. The 'Next steps' section lists Visual Studio and PowerShell upgrade tutorials before any mention of cross-platform or Linux-native tooling, and does not provide Linux-specific or CLI-based alternatives. The serialization discussion is focused on C# and .NET, which are cross-platform, but the upgrade tooling guidance leans toward Windows environments.
Recommendations
  • Add explicit guidance or links for upgrading Service Fabric applications using cross-platform tools, such as Azure CLI or REST APIs, where available.
  • Include Linux/macOS-compatible instructions or note any limitations for non-Windows users.
  • Clarify whether PowerShell Core (cross-platform) is supported, and provide examples for Bash or other Linux-native shells if possible.
  • If Visual Studio Code or other cross-platform editors can be used for upgrades, mention them alongside Visual Studio.
GitHub Create Pull Request
Service Fabric Upgrade an Azure Service Fabric standalone cluster ...ce-fabric/service-fabric-cluster-upgrade-standalone.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation page for upgrading an Azure Service Fabric standalone cluster demonstrates a Windows bias. References and links are primarily to Windows Server-specific guides (e.g., 'service-fabric-cluster-upgrade-windows-server.md', 'service-fabric-cluster-config-upgrade-windows-server.md'), and the Patch Orchestration Application is described only for Windows. There are no explicit Linux examples, nor are Linux-specific upgrade or configuration instructions provided, despite Service Fabric standalone clusters being available for both Windows and Linux.
Recommendations
  • Add explicit instructions and examples for upgrading Service Fabric standalone clusters running on Linux, including links to Linux-specific documentation where available.
  • Clarify which steps or tools are Windows-only and provide Linux equivalents or note any limitations for Linux users.
  • Include references to Linux configuration files, command-line tools, and patch orchestration solutions applicable to Linux clusters.
  • Ensure parity in example order (e.g., present Linux and Windows instructions side-by-side or in alternating order).
GitHub Create Pull Request
Service Fabric Scalability of Service Fabric services .../service-fabric/service-fabric-concepts-scalability.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation provides code examples for scaling Service Fabric services primarily using PowerShell and C#. PowerShell is a Windows-centric tool, and no equivalent Linux command-line examples (such as Bash, CLI, or REST API) are provided. The documentation also references Windows tools and patterns first, with no mention of Linux-native management workflows or tools, which may create friction for Linux users.
Recommendations
  • Add Linux-friendly command-line examples, such as using Azure CLI, Bash scripts, or REST API calls for managing Service Fabric services.
  • Explicitly mention cross-platform management options and clarify which commands/tools work on Linux clusters.
  • Where PowerShell is referenced, provide a Linux equivalent or note if no direct equivalent exists.
  • Consider adding a section or callouts for Linux-specific workflows, especially for cluster management and service scaling.
GitHub Create Pull Request
Service Fabric Secure an Azure Service Fabric cluster ...cles/service-fabric/service-fabric-cluster-security.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation provides security guidance for Azure Service Fabric clusters and standalone clusters, but consistently presents Windows-specific instructions and links before Linux equivalents. Standalone cluster security is described only for Windows Server, with no mention of Linux standalone clusters or how to secure them. Certificate creation recommendations and tooling reference Windows Server certificate services, with no Linux alternatives or parity guidance.
Recommendations
  • Add explicit guidance and links for securing standalone Service Fabric clusters on Linux, if supported.
  • Where certificate creation is discussed, include Linux-compatible tools and instructions (e.g., OpenSSL) alongside Windows Server certificate services.
  • Clarify whether standalone Linux clusters are supported, and if not, state this explicitly to avoid confusion.
  • Ensure examples and instructions are presented in a platform-neutral order, or provide parallel examples for both Windows and Linux where applicable.
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_first ⚠️ missing_linux_example
Summary
The documentation page for the Azure Service Fabric hosting activation and deactivation life cycle is generally platform-neutral in its conceptual explanations. However, there are subtle signs of Windows bias: the 'Next steps' section points only to PowerShell-based deployment/removal instructions, and the only concrete example for pre-downloading a ServicePackage links to a PowerShell cmdlet. There are no references to Linux-native tools, Bash, or cross-platform CLI equivalents, nor are Linux/macOS deployment workflows mentioned or linked.
Recommendations
  • In the 'Next steps' section, add links to Linux/macOS deployment instructions using Azure CLI, Bash scripts, or Service Fabric CLI (sfctl), if available.
  • When referencing actions like pre-downloading a ServicePackage, provide Linux/macOS equivalents (e.g., using sfctl or REST API) alongside PowerShell examples.
  • Ensure that conceptual explanations and examples do not assume PowerShell as the default tool, and clarify when a step is platform-specific.
  • Where possible, include cross-platform code snippets or note differences in workflow between Windows and Linux clusters.
GitHub Create Pull Request
Service Fabric Upgrading Azure Service Fabric clusters ...icles/service-fabric/service-fabric-cluster-upgrade.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ windows_tools
Summary
The documentation provides upgrade guidance for Azure Service Fabric clusters in a generally platform-neutral manner. However, in several sections, Windows-centric tools (PowerShell) are mentioned before or instead of Linux/macOS equivalents. The OS image upgrade section links only to Windows patching documentation, and PowerShell is referenced as a primary automation tool alongside Azure CLI, but Linux-specific guidance is not surfaced. There is an implicit prioritization of Windows tools and workflows, which may create friction for Linux/macOS users.
Recommendations
  • Explicitly mention and provide examples for Linux/macOS users where PowerShell is referenced, such as using Azure CLI or Bash scripts.
  • In sections about OS image upgrades, include links or guidance for patching Linux-based Service Fabric clusters, if supported.
  • Ensure that automation and scripting examples are provided for both PowerShell and Bash/Azure CLI.
  • Where possible, clarify which instructions apply to both Windows and Linux clusters, and note any platform-specific differences.
GitHub Create Pull Request
Service Fabric Fault Analysis Service overview .../service-fabric/service-fabric-testability-overview.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation provides usage instructions for C# (via NuGet) and PowerShell, but does not mention or provide examples for Linux/macOS command-line tools, such as Bash, Azure CLI, or REST API usage. PowerShell is highlighted as the primary scripting interface, which is Windows-centric, and there is no guidance for Linux users on how to interact with the Fault Analysis Service outside of C# code.
Recommendations
  • Add examples for using the Fault Analysis Service via Azure CLI or REST API, which are cross-platform.
  • Clarify whether PowerShell Core (cross-platform) is supported, and provide instructions for Linux/macOS users if so.
  • Include Bash or shell script examples for common operations, or explicitly state if only PowerShell is supported.
  • If the Fault Analysis Service can only be managed via PowerShell on Windows, make this limitation clear to set expectations for Linux/macOS users.
GitHub Create Pull Request
Virtual Machines Deploy a Trusted Launch VM ...ain/articles/virtual-machines/trusted-launch-portal.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation covers both Linux and Windows VMs for Trusted Launch and provides parity in Azure Portal, CLI, and template instructions. However, PowerShell examples are exclusively Windows-focused, and Windows-specific parameters and patterns are shown first in several places. Linux PowerShell usage is not addressed, and PowerShell sections do not mention Linux VM creation, which may create friction for Linux users who prefer PowerShell or need parity in scripting.
Recommendations
  • Add PowerShell examples for Linux Trusted Launch VM deployment, including Linux image parameters and admin credential patterns.
  • In PowerShell sections, clarify which examples are for Windows and provide equivalent Linux VM creation steps.
  • Where possible, present CLI and template examples for both Linux and Windows side-by-side, or clarify applicability.
  • Review ordering so that Linux and Windows examples are presented with equal prominence, especially in scripting sections.
GitHub Create Pull Request
Virtual Machines Create a VM from a specialized image version ...icles/virtual-machines/vm-specialized-image-version.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 both Azure CLI and PowerShell examples for creating VMs from specialized images, but the PowerShell examples are extensive and detailed, while the CLI examples are more concise. The PowerShell examples use Windows-centric constructs (e.g., New-AzNetworkSecurityRuleConfig for RDP port 3389), and the CLI and PowerShell tabs are presented in parallel, but PowerShell scripts are much longer and more prominent. There are no Linux shell (bash) script equivalents for the detailed resource creation steps, and the PowerShell examples assume a Windows environment. The documentation does not provide parity for Linux users who may prefer bash scripting or native Linux tools for automation.
Recommendations
  • Add detailed bash shell script examples for resource creation, matching the depth of the PowerShell examples.
  • Clarify that PowerShell examples can be run cross-platform (if true), or provide explicit instructions for Linux/macOS users.
  • When showing network security rules, include examples for both SSH (port 22) and RDP (port 3389), and explain their relevance for Linux and Windows VMs.
  • Ensure that CLI and shell examples cover all steps shown in PowerShell, including network setup and VM configuration.
  • Consider presenting CLI/bash examples before or alongside PowerShell to avoid Windows-first perception.
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: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page provides extensive PowerShell-based examples and references to Windows-specific tools and patterns (such as S-channel, certificate store locations like 'LocalMachine', and the Key Vault VM extension for Windows). PowerShell is used exclusively for scripting certificate enrollment, with no Bash, CLI, or Linux-native alternatives shown. Windows terminology and mechanisms (ACLing, certificate store, S-channel) are described in detail, while Linux/macOS equivalents are not mentioned or are absent. The Key Vault VM extension is referenced primarily in its Windows context, and the documentation does not provide guidance for Linux-based Service Fabric clusters or certificate management on non-Windows nodes.
Recommendations
  • Provide equivalent examples using Azure CLI and Bash for certificate enrollment and management, alongside PowerShell.
  • Clarify which mechanisms (e.g., Key Vault VM extension, certificate store, ACLing) are Windows-only, and offer Linux/macOS alternatives or note their absence.
  • Include documentation or links for managing certificates on Linux-based Service Fabric clusters, if supported.
  • Explicitly state platform limitations where features are Windows-only, to help non-Windows users understand applicability.
  • Add troubleshooting and FAQ sections relevant to Linux/macOS environments.
GitHub Create Pull Request
Service Fabric X.509 Certificate-based Authentication in a Service Fabric Cluster ...ticles/service-fabric/cluster-security-certificates.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation provides a thorough conceptual overview of X.509 certificate-based authentication in Service Fabric clusters, but exhibits a moderate Windows bias. Windows terminology, tools, and patterns are mentioned first or exclusively in several areas (e.g., certificate store paths, troubleshooting logs, API calls). Linux equivalents are referenced only briefly or as afterthoughts, and there are no concrete Linux/macOS-specific configuration or troubleshooting examples. This may create friction for non-Windows users attempting to implement or debug certificate-based authentication.
Recommendations
  • Provide explicit Linux/macOS examples for certificate storage paths, certificate management, and troubleshooting steps (e.g., where to find logs, how to check certificate presence/permissions on Linux).
  • When referencing certificate stores (e.g., LocalMachine\My), always include the Linux equivalent (e.g., /var/lib/sfcerts) in the same sentence or in parallel examples.
  • For troubleshooting, add guidance on where to find Service Fabric logs on Linux, and how to enable equivalent detailed logging (since CAPI2 and Windows Event Viewer are Windows-specific).
  • When mentioning API calls or configuration flags (e.g., Win32 CryptoAPI, CertGetCertificateChain), clarify their applicability to Windows and provide Linux-specific notes or alternatives if available.
  • Ensure that all example XML snippets and configuration walkthroughs explicitly mention any differences or additional steps required for Linux clusters.
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: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation provides a PowerShell-only example for bypassing the Infrastructure Service, without mentioning or providing equivalent commands for Linux/macOS users. The use of PowerShell cmdlets and references to Service Fabric Explorer (which is primarily a Windows tool) creates friction for users managing clusters from non-Windows environments.
Recommendations
  • Include equivalent CLI or REST API examples for Linux/macOS users (e.g., Azure CLI, Service Fabric CLI, or REST calls).
  • Clarify whether the PowerShell command is required or if alternatives exist for non-Windows platforms.
  • Mention cross-platform management tools and provide links or examples for their usage.
  • Note any limitations for Linux/macOS users if certain operations are Windows-only.
GitHub Create Pull Request
Service Fabric Deny assignment policy for Service Fabric managed clusters ...cles/service-fabric/managed-cluster-deny-assignment.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation page provides examples and links for Azure PowerShell before Azure CLI, and references PowerShell modules for cluster management tasks. While ARM templates, Bicep, Azure portal, and Azure CLI are mentioned, PowerShell commands are highlighted first and in detail, with CLI only referenced in a summary table. This ordering and emphasis may create friction for Linux/macOS users who prefer CLI or non-PowerShell workflows.
Recommendations
  • Provide equivalent Azure CLI examples and links alongside PowerShell commands for all management tasks.
  • When listing tools or utilities, alternate the order or explicitly state cross-platform options first (e.g., Azure CLI, ARM templates, Bicep).
  • Add explicit notes that Azure CLI is fully supported on Linux/macOS and provide direct links to CLI documentation for common tasks.
  • Where possible, include sample commands for both PowerShell and CLI for key operations (e.g., deleting NodeType, restarting/reimaging scale sets).
GitHub Create Pull Request
Service Fabric Custom Image .../articles/service-fabric/how-to-deploy-custom-image.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page for deploying custom images on Azure Service Fabric Managed Clusters shows a notable Windows bias. The introductory section and examples focus on 'custom windows images', and the only command-line example provided uses PowerShell (New-AzRoleAssignment), with no equivalent Azure CLI or Linux shell example. References to finding marketplace images link to both Windows and Linux instructions, but the PowerShell example is shown first and exclusively. There is no explicit guidance or examples for Linux-based custom images, even though Service Fabric supports both Windows and Linux node types.
Recommendations
  • Add explicit examples and guidance for deploying Linux-based custom images, including any differences in process or requirements.
  • Provide Azure CLI commands alongside PowerShell examples for role assignment and other resource management tasks.
  • Clarify in the introduction that both Windows and Linux custom images are supported, and structure examples to show parity.
  • Ensure ARM template examples mention both Windows and Linux scenarios if there are differences.
GitHub Create Pull Request
Service Fabric Configure or modify a Service Fabric managed cluster node type ...vice-fabric/how-to-managed-cluster-modify-node-type.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation frequently uses PowerShell for command-line examples and does not provide equivalent instructions for Linux/macOS users (e.g., Azure CLI or Bash). PowerShell is presented as the only scripting option for programmatic management, and it is referenced before any cross-platform alternatives. This creates friction for users on Linux or macOS who may not have access to PowerShell or prefer native tools.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all command-line tasks (adding, removing, scaling node types, etc.), since Azure CLI is cross-platform and widely used.
  • Explicitly mention that PowerShell examples are applicable on Windows and Linux (where PowerShell Core is available), but provide Azure CLI/Bash alternatives for Linux/macOS users.
  • Clarify in each section that ARM templates can be deployed using Azure CLI, not just PowerShell.
  • Consider reordering examples so that cross-platform tools (Azure CLI, ARM templates) are shown before or alongside PowerShell.
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: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation consistently references Az PowerShell cmdlets (e.g., Remove-AzResource, AzSF PowerShell cmdlets) for managing Service Fabric resources, with no mention of equivalent Azure CLI commands or Linux/macOS workflows. This creates friction for users on non-Windows platforms, as PowerShell is traditionally Windows-centric and not all users have it installed or prefer it. The examples and guidance are PowerShell-heavy, and Linux/macOS users may need to seek out their own alternatives.
Recommendations
  • Include Azure CLI examples (e.g., az resource delete) alongside PowerShell cmdlets for all operations.
  • Clarify that Az PowerShell cmdlets are cross-platform, but provide explicit instructions for installing and using them on Linux/macOS.
  • Where possible, provide ARM template snippets or REST API examples for resource management.
  • Add notes or sections specifically addressing Linux/macOS usage, ensuring parity in guidance.
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 ⚠️ windows_tools ⚠️ powershell_heavy
Summary
The documentation page on RunToCompletion semantics in Service Fabric exhibits notable Windows bias. The code examples exclusively use Windows containers (nanoserver:1809) and Windows command syntax (cmd, set, exit), with no mention of Linux container equivalents. The 'Query deployment status' section only provides PowerShell and C# examples, omitting Linux CLI or REST API alternatives. The introductory note explicitly assumes familiarity with Windows container creation, and all example manifests are named and described as Windows-specific.
Recommendations
  • Add equivalent Linux container examples (e.g., using Ubuntu or Alpine images) and Linux shell commands in ServiceManifest.xml.
  • Clarify whether RunToCompletion semantics are supported for Linux containers and guest executables, and provide examples if so.
  • Include instructions for querying deployment status using Linux tools (e.g., Azure CLI, REST API, or Bash scripts) alongside PowerShell.
  • Balance the introductory context to mention both Windows and Linux container scenarios if supported.
GitHub Create Pull Request
Service Fabric Monitor Azure Service Fabric ...main/articles/service-fabric/monitor-service-fabric.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation generally covers both Windows and Linux clusters for monitoring Azure Service Fabric, but there is a noticeable Windows-first bias in several sections. Windows tools and patterns (such as Event Log, Event Viewer, ETW, Diagnostics Agent) are mentioned before their Linux equivalents, and some examples and tutorials are focused on Windows/.NET applications. Linux-specific instructions and examples are present but often referenced as secondary or in separate links, and some features (like EventStore APIs) are explicitly Windows-only without Linux alternatives described in detail.
Recommendations
  • Ensure Linux monitoring instructions and examples are presented with equal prominence and detail as Windows ones.
  • Where features are Windows-only (e.g., EventStore APIs), clearly state Linux alternatives or workarounds, and provide links to Linux-specific documentation inline.
  • Add direct Linux application monitoring examples (e.g., using Application Insights with Java or Python on Linux nodes) alongside .NET/Windows examples.
  • When referencing tools (e.g., Diagnostics Agent, Event Viewer), immediately follow with the Linux equivalent (e.g., Syslog, LTTng) and provide configuration steps.
  • In summary and recommended setup sections, explicitly mention Linux setup steps and tools, not just Windows-focused ones.
GitHub Create Pull Request
Service Fabric Application lifecycle in Service Fabric ...service-fabric/service-fabric-application-lifecycle.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation consistently references PowerShell cmdlets and Windows-centric tooling (e.g., Copy-ServiceFabricApplicationPackage, Register-ServiceFabricApplicationType) as primary command-line interfaces for managing the Service Fabric application lifecycle. While REST APIs and .NET methods are also mentioned, there is a notable absence of Linux-native CLI examples (such as Azure CLI or sfctl) in the main lifecycle steps. This creates friction for Linux/macOS users, who may not have access to PowerShell or Windows-specific tools.
Recommendations
  • Include equivalent Azure CLI (az sf) or Service Fabric CLI (sfctl) commands alongside PowerShell cmdlets for all lifecycle operations (deploy, upgrade, remove, etc.).
  • Add explicit notes or examples for Linux/macOS users, clarifying which tools are cross-platform and how to perform tasks without PowerShell.
  • Where possible, show Linux/macOS shell commands (bash) in parallel with PowerShell, especially for automation scenarios.
  • Link to cross-platform tool documentation (sfctl, Azure CLI) in each relevant section.
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 provides a general overview of Service Fabric application security, with some sections and examples that are Windows-centric or reference Windows tools and patterns first. There are references to running services under Windows-specific accounts (Active Directory, gMSA), and disk encryption is only linked to a Windows PowerShell example, with a TODO for Linux. Linux equivalents are mentioned but not detailed, and examples or step-by-step instructions for Linux are missing in several sections.
Recommendations
  • Add explicit Linux examples for disk encryption and securing data at rest, including links to relevant Azure documentation for Linux VMSS disk encryption.
  • Provide parallel instructions or references for running services under Linux user accounts, including any differences in manifest configuration or security principal setup.
  • Ensure that examples and walkthroughs for certificate management, endpoint configuration, and container security include both Windows and Linux scenarios, with clear distinctions.
  • Where Windows-specific features (e.g., gMSA, AD integration) are mentioned, clarify Linux alternatives or state if no equivalent exists.
  • Reorder examples or provide side-by-side Windows and Linux instructions to avoid Windows-first bias.
GitHub Create Pull Request
Service Fabric Advanced Application Upgrade Topics ...-fabric/service-fabric-application-upgrade-advanced.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page for advanced Service Fabric application upgrades is heavily focused on PowerShell-based workflows, with all command-line examples using PowerShell cmdlets and no mention of Linux/macOS equivalents (such as Service Fabric CLI or REST API usage). Windows/PowerShell tools are referenced first and exclusively, creating friction for users managing Service Fabric clusters on Linux or from non-Windows environments.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and supported on Linux/macOS.
  • Where PowerShell cmdlets are referenced, include a note or link to CLI/REST API documentation for non-Windows users.
  • Clarify which features or commands are available across platforms, and indicate any Windows-only limitations.
  • Provide ARM template and manifest examples alongside CLI commands for parity.
  • Update 'Next steps' to include links to Linux/macOS upgrade tutorials or CLI-based guides.
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 upgrades demonstrates a notable Windows bias. PowerShell is the only command-line example provided, and all upgrade tooling references (e.g., Get-ServiceFabricApplication, Start-ServiceFabricApplicationUpgrade, Update-ServiceFabricService) are PowerShell cmdlets. There are no examples or guidance for Linux/macOS users, such as using the Service Fabric CLI (sfctl) or REST APIs. The documentation also references Windows-specific components (e.g., http.sys) without clarifying platform differences or alternatives.
Recommendations
  • Add equivalent examples using the Service Fabric CLI (sfctl), which is cross-platform, alongside or instead of PowerShell examples.
  • Mention REST API options for application upgrades, which are platform-agnostic.
  • Clarify when features or errors (such as http.sys certificate handling) are specific to Windows, and provide Linux/macOS alternatives or caveats where applicable.
  • In the 'Next steps' section, include links to tutorials or guides for Linux/macOS users, such as 'Upgrading your Application Using sfctl'.
  • Where PowerShell cmdlets are referenced, add a note or table mapping to equivalent sfctl commands.
GitHub Create Pull Request
Service Fabric Architecture of Azure Service Fabric ...articles/service-fabric/service-fabric-architecture.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation references PowerShell cmdlets as the primary means for managing Service Fabric clusters and applications, without mentioning equivalent Linux/macOS management tools or CLI options. Windows security is mentioned as a transport option before X509 certificates, and no Linux-specific management patterns are described. This creates friction for Linux users seeking parity in cluster management and automation.
Recommendations
  • Include references to cross-platform management tools such as Azure CLI, REST APIs, or Service Fabric CLI (sfctl) alongside PowerShell cmdlets.
  • Clarify that PowerShell cmdlets are available on Linux/macOS via PowerShell Core, or provide Linux/macOS-specific instructions/examples.
  • Mention X509 certificates before or alongside Windows security as a transport option, and clarify Linux support.
  • Add explicit notes or links to Linux/macOS management documentation for Service Fabric clusters.
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, with all command-line examples using PowerShell syntax and Windows-specific modules. There are no equivalent Linux/macOS CLI or REST API examples using cross-platform tools (e.g., curl, Azure CLI, or bash). The prerequisite steps and operational guidance assume a Windows environment and PowerShell, which may create friction for Linux/macOS users.
Recommendations
  • Add equivalent examples using cross-platform tools such as curl, Azure CLI, or bash scripts for REST API calls.
  • Clarify whether the Service Fabric PowerShell module is required for all platforms, and if not, provide installation and usage instructions for Linux/macOS.
  • Include explicit guidance for Linux/macOS users on how to authenticate and interact with the Service Fabric REST APIs (e.g., using certificates with curl or other HTTP clients).
  • Reorganize examples so that REST API usage is shown independently of PowerShell, or provide both PowerShell and cross-platform examples side-by-side.
  • Document any platform limitations (if any) for Service Fabric backup/restore operations, so users know if certain steps are Windows-only.
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: 3 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page for configuring periodic backups in Azure Service Fabric shows evidence of Windows bias, primarily in the 'File share' backup storage section. Only Windows-style UNC paths (\\StorageServer\BackupStore) and Integrated Windows Authentication are described, with no mention of Linux-compatible file share options (such as NFS, SMB mounting on Linux, or cross-platform authentication patterns). The examples and instructions for file share access are Windows-centric, and there is no guidance for Linux/macOS users on how to configure or access file shares for backup storage. Additionally, Windows authentication methods are presented first and exclusively, without Linux alternatives.
Recommendations
  • Add documentation for configuring file share backup storage using Linux/macOS nodes, including supported protocols (e.g., NFS, SMB) and authentication methods.
  • Provide examples of mounting and accessing file shares from Linux-based Service Fabric clusters, including sample paths and credential handling.
  • Clarify whether Linux clusters can use the file share backup option, and if so, provide parity in instructions for both platforms.
  • If file share backup is Windows-only, explicitly state this limitation to avoid confusion for Linux users.
GitHub Create Pull Request
Service Fabric Azure Service Fabric infrastructure as Code Best Practices ...tps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-best-practices-infrastructure-as-code.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Service Fabric clusters, but PowerShell is featured prominently and exclusively for some upgrade operations. Windows-specific tools and registry settings are discussed without Linux equivalents or alternatives. Windows VM configuration details are given before Linux, and some upgrade instructions are Windows-centric.
Recommendations
  • Provide equivalent Bash or Linux shell examples for manual upgrade operations currently shown only in PowerShell.
  • Include Linux-specific instructions for disabling automatic updates and managing OS upgrades, such as using cloud-init or systemd settings.
  • Clarify which steps are Windows-only and provide Linux alternatives or links to Linux documentation where appropriate.
  • Balance the order of Windows and Linux references, presenting both options side-by-side when possible.
GitHub Create Pull Request
Service Fabric Capacity planning and scaling for Azure Service Fabric ...bric/service-fabric-best-practices-capacity-scaling.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation page provides detailed step-by-step instructions for scaling Service Fabric clusters, but the manual scaling sections exclusively reference PowerShell commands (e.g., Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState) without mentioning Linux equivalents or cross-platform alternatives. There are no bash/CLI examples or guidance for Linux users, and the use of PowerShell is presented as the default approach for cluster management tasks. This creates friction for Linux/macOS users, who may not have access to PowerShell or may prefer native Linux tools.
Recommendations
  • Add equivalent examples for Linux environments, such as using Azure CLI, Service Fabric CLI (sfctl), or bash scripts for node management tasks.
  • Clearly indicate which commands are Windows-only and provide cross-platform alternatives where possible.
  • Include links or references to Linux/macOS documentation for Service Fabric cluster management.
  • Reorder examples to present cross-platform or Linux-native tools alongside or before Windows/PowerShell examples.
GitHub Create Pull Request
Service Fabric Node types and virtual machine scale sets ...les/service-fabric/service-fabric-cluster-nodetypes.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation provides a general overview of Service Fabric node types and VM scale sets, with some references to both Windows and Linux nodes. However, there are signs of Windows bias: the example configuration uses a Windows-style file path (D:\SvcFab) and certificate store naming conventions, and the 'Next steps' section links to PowerShell scripts for RDP port and credential management, which are Windows-specific tasks. There are no explicit Linux/macOS examples or equivalent SSH instructions for remote connectivity or admin management.
Recommendations
  • Include Linux/macOS-specific examples, such as using SSH for remote connection and managing credentials.
  • Provide sample configuration snippets with Linux-style paths (e.g., /var/svcfab) when 'type' is ServiceFabricLinuxNode.
  • Add links to documentation or scripts for managing Linux nodes, such as changing SSH keys or port ranges.
  • Clarify which instructions apply to Windows nodes and which to Linux nodes, especially in 'Next steps'.
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 references that prioritize Windows and PowerShell usage, with Linux equivalents mentioned less prominently or omitted. Windows tools and patterns (e.g., PowerShell, Windows containers, Windows-specific ARM templates) are referenced before or instead of Linux alternatives. Some sections, such as API access and DevOps, focus on PowerShell and Windows-specific workflows, while Linux guidance is less detailed or missing. Example ARM templates and networking scenarios are Windows-centric, and Linux-specific instructions are often relegated to links or brief mentions.
Recommendations
  • Provide Linux CLI (az, bash) examples alongside PowerShell commands, especially for API access and cluster management.
  • Include Linux-focused ARM template samples and reference them equally with Windows examples.
  • Clarify when instructions or features apply to both Windows and Linux clusters, and explicitly note any differences.
  • Add more Linux-specific networking scenarios and troubleshooting steps.
  • Ensure that DevOps and automation examples include Linux agent workflows, not just classic PowerShell tasks.
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 ⚠️ windows_tools ⚠️ powershell_heavy
Summary
The documentation generally covers both Windows and Linux scenarios for Service Fabric security, but there is a noticeable Windows-first bias in several sections. Windows-specific tools (PowerShell, Windows Defender, DSC) are described in detail, often before or with more emphasis than Linux equivalents. Some examples and recommendations are Windows-centric, with Linux alternatives provided later or in less detail. Windows Defender configuration is covered extensively, while Linux antimalware is only briefly mentioned as unsupported.
Recommendations
  • Ensure Linux examples and instructions are presented with equal prominence and detail as Windows ones, especially in sections like certificate management and encryption.
  • Where Windows tools (e.g., PowerShell, Windows Defender, DSC) are mentioned, provide clear Linux alternatives or explicitly state when no equivalent exists.
  • Avoid presenting Windows examples first by default; alternate or parallelize example order for cross-platform parity.
  • Expand on Linux antimalware and security baseline options, or link to relevant resources if available.
  • Clarify which features or recommendations are Windows-only and which are cross-platform, to reduce confusion.
GitHub Create Pull Request
Service Fabric Change Azure Service Fabric cluster settings ...rvice-fabric/service-fabric-cluster-fabric-settings.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation lists Service Fabric cluster settings in a platform-neutral way, but there are several signs of Windows bias. Windows terminology and tools (e.g., certificate store names like 'My', NTLM authentication, references to Windows-specific features like Windows Update, and default paths like d:\svcfab) are prevalent throughout. Some settings and defaults are described primarily in Windows terms, with Linux equivalents either omitted or mentioned secondarily. There are parameters whose guidance is Windows-centric (e.g., references to Windows Defender Firewall, Windows node management, and PowerShell-style paths), and Linux-specific configuration is rarely highlighted or explained in parity. The documentation does not provide Linux/macOS-specific examples or guidance for certificate management, file paths, or service management, even though Service Fabric supports Linux clusters.
Recommendations
  • For each setting that references Windows-specific concepts (e.g., certificate store names, NTLM, Windows Update), add Linux equivalents or clarify platform applicability.
  • Where file paths or store names are mentioned, provide both Windows and Linux examples (e.g., 'My' vs. '/var/lib/waagent').
  • Explicitly document Linux/macOS configuration steps, especially for certificate management, service activation, and file system paths.
  • Add notes or tables indicating which settings are Windows-only, Linux-only, or cross-platform.
  • Include Linux/macOS-focused examples for common configuration scenarios.
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: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example ⚠️ windows_first
Summary
The documentation page provides code examples for configuring Service Fabric placement policies using C# and PowerShell. All command-line examples use PowerShell, which is a Windows-centric tool, and there are no equivalent examples for Linux/macOS users (e.g., Azure CLI, Bash, or REST API). The documentation implicitly assumes a Windows environment for operational tasks, which may create friction for users managing Service Fabric clusters from Linux/macOS.
Recommendations
  • Add Azure CLI or REST API examples for configuring placement policies, as these are cross-platform and commonly used on Linux/macOS.
  • Explicitly mention whether PowerShell commands can be run on Linux/macOS (e.g., via PowerShell Core), or provide alternative instructions if not.
  • Clarify any platform-specific requirements for Service Fabric management, and link to cross-platform tooling where available.
  • Consider reordering examples so that cross-platform options (if available) are presented first or alongside Windows-specific tools.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Auto Scaling Services and Containers ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-autoscaling.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation provides example code for configuring auto scaling policies in Service Fabric using application manifests, C# APIs, and PowerShell. However, all command-line examples use PowerShell, which is Windows-centric, and there are no equivalent Linux shell (e.g., Bash/CLI) examples. The documentation does mention that resource monitoring is supported for containerized applications on Linux, but practical configuration steps and code samples are only shown for Windows tools and patterns. This creates friction for Linux users who may need to adapt or research how to perform these tasks on their platform.
Recommendations
  • Add equivalent examples using Azure CLI or Bash scripts for configuring scaling policies, especially for Linux clusters.
  • Clearly indicate which steps or commands are platform-specific and provide guidance or links for Linux users.
  • If PowerShell is required for some operations, explain how Linux users can install and use PowerShell Core, or provide alternative approaches.
  • Include notes or sections explicitly addressing Linux configuration workflows for Service Fabric auto scaling.
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 both C# and PowerShell examples for managing Service Fabric metrics, but omits equivalent Linux/macOS command-line examples (such as Azure CLI or REST API). PowerShell is featured as the only scripting/command-line interface, which is Windows-centric. There is no mention of Linux-native tools or workflows, nor are Linux/macOS users guided on how to perform these tasks without PowerShell.
Recommendations
  • Add Azure CLI examples for service creation and metric management, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include REST API examples for metric configuration and load reporting, which are platform-agnostic.
  • Explicitly mention how Linux/macOS users can perform these operations, and clarify any differences or limitations.
  • Consider reordering examples so that platform-neutral options (C#, CLI, REST) appear before or alongside PowerShell.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager - Application Groups ...ice-fabric-cluster-resource-manager-application-groups.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example ⚠️ windows_first
Summary
The documentation page for Service Fabric Cluster Resource Manager - Application Groups predominantly provides PowerShell examples and references, which are Windows-centric. There are no CLI/bash examples or explicit instructions for Linux/macOS users. PowerShell commands are presented before C# code samples, and no cross-platform alternatives (such as Azure CLI or REST API) are mentioned. This creates friction for users managing Service Fabric clusters from Linux/macOS environments.
Recommendations
  • Add Azure CLI examples for all operations shown with PowerShell (e.g., creating/updating applications, querying load information).
  • Explicitly mention REST API endpoints or SDKs that can be used from any platform.
  • Clarify whether PowerShell commands can be run from Linux/macOS (using PowerShell Core), and provide guidance if so.
  • Reorder examples or provide parallel examples for Windows (PowerShell) and Linux/macOS (CLI/bash) where possible.
  • Include a note about cross-platform management options for Service Fabric clusters.
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: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation provides configuration examples for both ClusterManifest.xml (Windows Server clusters) and ClusterConfig.json (standalone deployments, which can be Linux or Windows). However, code samples for service creation and updates are given only in C# and PowerShell, with no Linux CLI or cross-platform examples. The XML configuration is shown under a <WindowsServer> element, and PowerShell is used for operational tasks, suggesting a Windows-first approach. There is no explicit mention of Linux-specific operational workflows, nor are Linux CLI equivalents (such as sfctl) demonstrated.
Recommendations
  • Add Linux-specific operational examples using sfctl (Service Fabric CLI) for service creation, updates, and placement constraints.
  • Clarify that ClusterConfig.json applies to both Linux and Windows standalone clusters, and provide explicit Linux deployment context where relevant.
  • Where PowerShell is used, provide equivalent commands for Linux/macOS users (e.g., sfctl or REST API).
  • Include notes or sections highlighting any differences or considerations for Linux clusters, especially in configuration and management tasks.
GitHub Create Pull Request
Service Fabric Cluster Resource Manager - Management Integration ...fabric-cluster-resource-manager-management-integration.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation provides only PowerShell-based examples for querying Service Fabric health, with no equivalent Linux/macOS CLI or REST API examples. This may create friction for users managing Service Fabric clusters from non-Windows environments.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • Include REST API examples for health queries, as these are platform-agnostic.
  • Explicitly mention that the PowerShell example is for Windows and provide guidance for Linux/macOS users.
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 ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation provides PowerShell examples for creating and updating Service Fabric services with move cost, but does not include equivalent CLI or script examples for Linux/macOS users. PowerShell is primarily a Windows tool, and its use here creates friction for users managing Service Fabric clusters from Linux environments. All command-line examples are PowerShell-only, with no mention of Azure CLI, Bash, or other cross-platform tools.
Recommendations
  • Add equivalent Azure CLI or REST API examples for creating and updating Service Fabric services with move cost, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Clarify whether PowerShell examples are supported on Linux (via PowerShell Core), and provide guidance for Linux users if so.
  • Include Bash or script examples where possible, or reference documentation for Linux/macOS management of Service Fabric clusters.
  • Explicitly mention cross-platform management options for Service Fabric clusters, if available.
GitHub Create Pull Request
Service Fabric Service sensitivity ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-sensitivity.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation provides configuration examples using XML, JSON, PowerShell, and C# APIs. PowerShell is featured prominently for service creation and updates, but there are no equivalent CLI (e.g., Bash, Azure CLI, or REST API) examples for Linux/macOS users. PowerShell is a Windows-centric tool, and its use without alternatives creates friction for non-Windows users. The C# API is cross-platform, but operational examples (service creation/update) are Windows-first and PowerShell-heavy.
Recommendations
  • Add Azure CLI or REST API examples for service sensitivity and maximum load configuration, if supported.
  • Clarify whether PowerShell commands can be run cross-platform (e.g., via PowerShell Core on Linux/macOS) or provide Bash/CLI alternatives.
  • Explicitly mention platform requirements for each example (e.g., 'Windows only', 'cross-platform', etc.).
  • Provide guidance for Linux/macOS users on how to perform equivalent operations.
GitHub Create Pull Request
Service Fabric Azure Service Fabric application resource model ...ervice-fabric/service-fabric-concept-resource-model.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example ⚠️ windows_first
Summary
The documentation page for the Azure Service Fabric application resource model demonstrates a notable Windows bias. All deployment and management examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) without mention of Azure CLI equivalents or cross-platform scripting options. The application packaging workflow is described using Visual Studio, a Windows-centric tool, with no alternative guidance for Linux/macOS users. There are no Linux/macOS-specific instructions or examples, and Windows tools and patterns are presented first and exclusively.
Recommendations
  • Provide Azure CLI examples for deployment, upgrade, and deletion tasks alongside PowerShell examples.
  • Include instructions for packaging Service Fabric applications using cross-platform tools (e.g., dotnet CLI, SF SDK on Linux/macOS).
  • Mention alternative editors or build tools for non-Windows environments (e.g., VS Code, command-line packaging).
  • Clarify which steps are platform-agnostic and which require Windows, and offer Linux/macOS workarounds where possible.
  • Add notes or links to official cross-platform Service Fabric documentation.
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: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation provides a broad overview of Azure Service Fabric, which supports both Windows and Linux. However, there is a noticeable Windows bias in several areas: Windows services and executables (e.g., FabricHost.exe) are described in detail, often before Linux equivalents are mentioned or without Linux-specific details; PowerShell is frequently referenced as a primary management tool, with CLI and REST APIs listed as alternatives; and some examples and links (e.g., standalone cluster creation) are Windows-only, with Linux support explicitly called out as unavailable. Linux is acknowledged, but examples, tooling, and instructions are often Windows-centric or presented first.
Recommendations
  • Provide Linux-specific examples and instructions alongside Windows ones, especially for cluster management, service deployment, and health monitoring.
  • Reference Linux-native tools (e.g., Bash, Linux CLI) and workflows equally with PowerShell and Windows tools.
  • Where features are Windows-only, clearly label them as such and provide alternative guidance or links for Linux users.
  • Ensure that links to getting started, tutorials, and samples include Linux options where available.
  • Consider reordering sections so that Linux and Windows are presented with equal prominence, or explicitly state platform applicability at the start of each section.
GitHub Create Pull Request
Service Fabric Azure Service Fabric dynamic node tags ...tps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-node-tagging.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation provides detailed PowerShell examples for managing node tags and service requirements, but does not include equivalent Linux/macOS CLI examples (such as Bash, Azure CLI, or REST API usage). PowerShell is presented first and exclusively for command-line operations, which may create friction for users managing Service Fabric clusters from non-Windows environments.
Recommendations
  • Add examples using Azure CLI or REST API for managing node tags and service requirements, which are cross-platform.
  • Include Bash or shell script examples for Linux/macOS users where applicable.
  • Clarify whether PowerShell Core (cross-platform) is supported, and if so, provide guidance for installation and usage on Linux/macOS.
  • Present cross-platform examples before or alongside Windows/PowerShell examples to improve parity.
GitHub Create Pull Request
Service Fabric Azure Service Fabric standalone cluster scaling ...ce-fabric/service-fabric-cluster-scaling-standalone.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation page on scaling Azure Service Fabric standalone clusters demonstrates Windows bias by referencing only PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) for cluster management tasks, without mentioning or providing equivalent Linux commands or tools. The linked 'scale a standalone cluster' documentation is Windows Server-specific, and there are no examples or guidance for Linux-based standalone clusters, despite Service Fabric supporting Linux nodes in some scenarios.
Recommendations
  • Provide equivalent Linux commands or scripts (e.g., using Service Fabric CLI or REST API) for cluster scaling operations.
  • Clarify whether standalone clusters can be managed on Linux, and if so, include Linux-specific instructions and examples.
  • If certain operations are Windows-only, explicitly state this in the documentation to set user expectations.
  • Reference cross-platform tools (such as sfctl) alongside PowerShell, and provide parity in example usage.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Docker Compose Deployment Preview ...ticles/service-fabric/service-fabric-docker-compose.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides both PowerShell and Service Fabric CLI (sfctl) examples for deploying Docker Compose files to Azure Service Fabric. However, PowerShell examples are presented first and in greater detail, which may suggest a Windows-centric approach. While the CLI commands are cross-platform, the initial emphasis on PowerShell could create friction for Linux/macOS users.
Recommendations
  • Present CLI (sfctl) examples before or alongside PowerShell examples to emphasize cross-platform support.
  • Explicitly mention that sfctl is supported on Linux/macOS and provide installation links or instructions.
  • Clarify that PowerShell examples are primarily for Windows users, and encourage Linux/macOS users to use sfctl.
  • Consider adding a short section or note highlighting platform parity and best practices for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Overview of Azure and standalone Service Fabric clusters ...icles/service-fabric/service-fabric-deploy-anywhere.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation discusses Service Fabric clusters on both Windows Server and Linux, but the standalone cluster feature is only available on Windows. Linux is mentioned as a supported OS for Service Fabric clusters, but standalone clusters are explicitly unavailable on Linux. There are no Linux-specific examples, tools, or operational guidance provided, and the documentation does not offer alternative solutions or workarounds for Linux users seeking standalone deployments.
Recommendations
  • Clearly state early in the document that standalone clusters are Windows-only, and provide guidance or alternatives for Linux users.
  • Add a section summarizing what Linux users can and cannot do, with links to relevant Linux documentation.
  • If possible, provide information on Azure-based Linux clusters and clarify the limitations for standalone Linux deployments.
  • Ensure that Linux users are not left without actionable next steps by referencing the 'Differences between Service Fabric on Linux and Windows' page more prominently.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Events ...es/service-fabric/service-fabric-diagnostics-events.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page on Azure Service Fabric Events predominantly references Windows-centric logging and monitoring tools (ETW/Windows Event logs, Windows Azure diagnostics agent) and does not provide equivalent Linux examples or mention Linux-native logging mechanisms. The initial and primary guidance is focused on Windows approaches, with no explicit instructions for accessing or monitoring Service Fabric events on Linux clusters.
Recommendations
  • Include instructions or references for accessing Service Fabric events on Linux clusters, such as using syslog, journald, or other Linux-native logging solutions.
  • Clarify whether the described event logging mechanisms (ETW, Windows Event logs, Windows Azure diagnostics agent) apply only to Windows-based clusters, and provide parity guidance for Linux-based clusters if supported.
  • Add examples or links to documentation for monitoring Service Fabric events on Linux, including integration with Azure Monitor from Linux nodes.
  • Explicitly state any limitations or differences in event access between Windows and Linux clusters to help users understand platform-specific considerations.
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: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation page for Azure Service Fabric DNS service demonstrates several Windows biases. PowerShell is the only CLI example provided for setting DNS names, with no Linux CLI (e.g., Bash, Azure CLI) equivalent. Visual Studio is mentioned as the default editor for ApplicationManifest.xml, and there is no guidance for Linux users on how to perform these tasks. The limitations section notes reduced Linux support, but examples and instructions are generally Windows-centric or omit Linux-specific workflows.
Recommendations
  • Add equivalent Linux/Bash/Azure CLI examples for tasks currently shown only with PowerShell.
  • Provide instructions for editing ApplicationManifest.xml using common Linux editors (e.g., vim, nano) and clarify how Linux users can deploy and configure services.
  • Explicitly document any Linux-specific steps or differences, especially where portal functionality is unavailable.
  • Where features are Windows-only, clearly mark those sections and provide alternative guidance for Linux users where possible.
GitHub Create Pull Request
Service Fabric Health monitoring in Service Fabric ...s/service-fabric/service-fabric-health-introduction.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation provides a detailed conceptual overview of Service Fabric health monitoring, which is a cross-platform feature. However, the only concrete example of reporting and evaluating health uses PowerShell cmdlets, which are Windows-centric. There are no equivalent Linux/bash/REST examples, nor is there mention of Linux tools or workflows for health reporting. The documentation also references Windows PowerShell tools as the primary method for interacting with Service Fabric health, creating friction for Linux/macOS users.
Recommendations
  • Add examples using REST API for health reporting and querying, which are platform-agnostic.
  • Include sample code snippets for reporting health using the Service Fabric SDK in cross-platform languages (e.g., Python, .NET Core, Java).
  • Provide Linux/bash CLI examples (e.g., using sfctl or curl) alongside PowerShell examples.
  • Explicitly mention Linux/macOS compatibility and tools where relevant, and link to cross-platform tooling documentation.
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_tools ⚠️ missing_linux_example
Summary
The documentation provides command-line examples only using PowerShell cmdlets (e.g., New-ServiceFabricService), with no equivalent examples for Linux/macOS users (such as Azure CLI, Bash, or REST via curl). All operational instructions reference PowerShell modules, and there is no mention of Linux-native tools or cross-platform workflows. This creates friction for non-Windows users, who must translate or research equivalent commands themselves.
Recommendations
  • Add Azure CLI examples for all service creation and management tasks alongside PowerShell examples.
  • Include REST API usage examples with curl or HTTPie to demonstrate cross-platform approaches.
  • Explicitly mention cross-platform tooling support and link to relevant documentation for Linux/macOS users.
  • Clarify in each example whether the command is Windows-only, and provide alternatives where possible.
GitHub Create Pull Request
Service Fabric Manage apps for multiple environments ...e-fabric-manage-multiple-environment-app-configuration.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias by prioritizing PowerShell and Visual Studio workflows, mentioning Windows-centric tools and scripts first, and lacking explicit Linux/macOS command examples for key tasks such as application creation and deployment. While sfctl and Jenkins are mentioned, the examples and guidance are primarily oriented toward Windows users.
Recommendations
  • Add explicit Linux/macOS command-line examples for application creation and parameter passing using sfctl and shell scripts.
  • Provide parity in deployment workflow examples, such as showing how to use Bash scripts or Linux-native CI/CD tools alongside PowerShell and Visual Studio.
  • Ensure that references to tools like Replace Tokens include Linux-compatible alternatives or usage instructions.
  • Clarify which steps or tools are cross-platform and which are Windows-specific, to help users on non-Windows systems navigate the documentation more easily.
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_tools ⚠️ missing_linux_example
Summary
The documentation page provides manifest examples for Service Fabric applications, but several elements and examples show a bias toward Windows environments. The startup script is specified as a .bat file (Setup.bat), which is a Windows batch script, and the service executables are .exe files, both of which are Windows-specific. There are no Linux-equivalent examples (such as .sh scripts or ELF binaries), nor is there guidance for Linux users on how to adapt these manifest entries for Linux clusters. Additionally, references to running services as NETWORKSERVICE and local admin accounts are Windows-centric, with no mention of Linux service accounts or equivalents.
Recommendations
  • Provide parallel examples using Linux-compatible scripts (e.g., Setup.sh) and service executables (e.g., ELF binaries) in the manifest.
  • Add notes or sections explaining how to configure service manifests for Linux clusters, including differences in user accounts, permissions, and startup scripts.
  • Clarify which manifest elements are cross-platform and which require platform-specific configuration, ideally linking to Linux-specific documentation where available.
  • Where Windows-specific accounts (e.g., NETWORKSERVICE) are mentioned, provide Linux equivalents or note their absence.
  • Ensure that references to PowerShell or Windows tools are balanced with Linux CLI or scripting alternatives if relevant.
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: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools ⚠️ windows_first
Summary
The documentation page for 'Networking patterns for Azure Service Fabric' demonstrates a notable Windows bias. All command-line deployment examples use PowerShell cmdlets (New-AzResourceGroup, New-AzResourceGroupDeployment, Get-AzPublicIpAddress), with no mention of Azure CLI or Bash equivalents. Additionally, some example outputs and instructions reference Windows-specific tools (e.g., RDP, Windows command prompt ping syntax), and the use of Windows file paths (C:\SFSamples\...). There are no Linux/macOS-specific instructions or examples, and the documentation assumes a Windows environment for both authoring and cluster access.
Recommendations
  • Provide equivalent Azure CLI (az ...) commands alongside PowerShell examples for all deployment steps.
  • Include Bash shell examples and Linux/macOS file path formats where relevant.
  • When referencing remote access, mention SSH as an alternative to RDP for Linux-based VMs.
  • Avoid using only Windows command prompt syntax (e.g., ping); provide cross-platform alternatives.
  • Clarify that the templates and instructions are platform-agnostic, and highlight any steps that are Windows-specific.
GitHub Create Pull Request
Service Fabric Add custom Service Fabric health reports ...rticles/service-fabric/service-fabric-report-health.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation provides detailed PowerShell examples for health reporting and cluster connection, but does not offer equivalent examples for Linux/macOS users (e.g., Bash, CLI, or cross-platform scripts). PowerShell is presented as the primary scripting interface, and Windows-style command prompts are shown first. REST API usage is mentioned but not demonstrated with concrete examples, and there is no guidance for Linux-native tools or workflows.
Recommendations
  • Add equivalent examples using Azure CLI or Bash scripts for Linux/macOS users, especially for connecting to clusters and sending health reports.
  • Clarify whether PowerShell Core (cross-platform) is supported, and if so, provide usage notes for Linux/macOS.
  • Provide REST API example requests using curl or similar Linux-native tools, including sample payloads and authentication guidance.
  • Explicitly mention any platform limitations (e.g., if PowerShell cmdlets are Windows-only) and direct Linux/macOS users to supported alternatives.
  • Reorder examples so that cross-platform or REST approaches are presented before or alongside Windows/PowerShell-specific instructions.
GitHub Create Pull Request
Service Fabric Azure Service Fabric image store connection string ...fabric/service-fabric-image-store-connection-string.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page repeatedly references PowerShell and Visual Studio for deployment and configuration tasks, which are primarily Windows-centric tools. Examples and next steps focus on PowerShell, with no mention of Linux/macOS equivalents (such as Azure CLI, Bash, or cross-platform SDKs). There is no guidance for Linux/macOS users on how to retrieve or set the ImageStoreConnectionString, nor are alternative workflows provided.
Recommendations
  • Add examples using Azure CLI, Bash, or cross-platform SDKs for retrieving and setting the ImageStoreConnectionString.
  • Include instructions for deploying applications from Linux/macOS environments, highlighting any differences or limitations.
  • Reference cross-platform tools and workflows alongside PowerShell and Visual Studio, ensuring parity in documentation.
  • Clarify whether any steps are Windows-only, and provide alternatives or workarounds for non-Windows users where 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: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools
Summary
The documentation page demonstrates a moderate Windows bias: it references the Windows Server 2016 Container Sample as the basis for its examples, and in the manifest XML and explanatory text, Windows-specific tools and patterns (such as 'winver' to get the OS build version and Windows file paths like 'c:\VolumeTest\Data') are mentioned before or instead of Linux equivalents. However, the documentation does mention Linux in some explanatory comments (e.g., PEM files for certificates on Linux), and the manifest schema itself is not inherently Windows-only.
Recommendations
  • Provide Linux-based example manifests or explicitly note Linux compatibility where applicable.
  • When referencing OS build version detection (e.g., for image overrides), include Linux commands (such as 'uname -r') alongside 'winver'.
  • Use cross-platform file paths in examples, or show both Windows and Linux path formats.
  • Clarify in the introduction if the examples are Windows-specific, and if so, link to Linux equivalents if available.
  • Ensure that referenced sample repositories or links include both Windows and Linux samples, or clearly indicate their OS focus.
GitHub Create Pull Request
Service Fabric Overview of Azure Service Fabric ...ain/articles/service-fabric/service-fabric-overview.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 mentions both Windows and Linux support for Service Fabric, but Windows development tools (Visual Studio, PowerShell, .NET SDK) are described first and in more detail, while Linux equivalents (Eclipse, Yeoman, Java SDK) are mentioned briefly. There are no example commands or workflows shown for Linux, and the quickstart link points to a .NET (Windows-centric) guide, with no immediate Linux alternative provided.
Recommendations
  • Provide parallel quickstart links for both Windows (.NET) and Linux (Java/.NET Core) development.
  • Include example workflows or commands for Linux environments, such as using Yeoman or Eclipse.
  • Balance the description of development tools by giving equal detail to Linux options (e.g., how to set up a local cluster, deploy, and manage applications on Linux).
  • Consider listing Linux development options before or alongside Windows options in relevant sections.
GitHub Create Pull Request
Service Fabric Replica soft delete for enhanced data protection in Service Fabric ...s/service-fabric/service-fabric-replica-soft-delete.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation page for Replica soft delete in Service Fabric predominantly references PowerShell cmdlets (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica, Get-ServiceFabricReplica) for administrative operations and API usage. There are no examples or instructions for Linux/macOS users, such as using Service Fabric CLI (sfctl) or REST APIs, nor is there mention of equivalent tooling or workflows outside of PowerShell. This creates friction for users managing Service Fabric clusters on Linux or from non-Windows environments.
Recommendations
  • Add equivalent examples using sfctl (Service Fabric CLI), which is cross-platform and commonly used on Linux/macOS.
  • Document REST API endpoints or FabricClient SDK usage for replica management, with code snippets in languages/platforms supported on Linux/macOS.
  • Clarify whether the PowerShell cmdlets are required, or if all functionality is available via CLI/SDK/REST for Linux users.
  • Include a note or section explicitly addressing Linux/macOS cluster management workflows for replica soft delete.
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: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example ⚠️ powershell_heavy
Summary
The documentation page focuses on defining service configuration in StartupServices.xml for Service Fabric applications, with a strong emphasis on Visual Studio workflows and PowerShell usage. All examples and workflows are described in the context of Visual Studio, a Windows-only tool, and PowerShell is referenced as the method for creating service instances. There are no Linux/macOS equivalents or alternative instructions provided, and the documentation does not mention cross-platform tooling or workflows.
Recommendations
  • Add guidance for Linux/macOS users, including how to manage Service Fabric application configuration and deployment using cross-platform tools (e.g., Azure CLI, Service Fabric CLI, or REST APIs).
  • Provide examples for deploying and managing Service Fabric applications outside of Visual Studio, such as using command-line tools available on Linux/macOS.
  • Clarify which features or workflows are Windows/Visual Studio-specific and offer alternative instructions for non-Windows environments where possible.
  • Include references to cross-platform documentation or tooling for Service Fabric application development and deployment.
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 both Azure CLI and Azure PowerShell for creating and managing Virtual Machine Scale Sets, but does not provide explicit Linux/macOS shell examples or parity in command-line instructions. PowerShell is mentioned alongside Azure CLI, but no bash or Linux-native scripting examples are given. Windows-specific scenarios (activation, updates) are listed before Linux equivalents, and some network connectivity examples highlight Windows needs first.
Recommendations
  • Provide explicit bash/Linux shell examples for key Azure CLI commands, especially for VM creation and migration steps.
  • Include Linux-specific migration considerations (e.g., package manager connectivity, Linux VM extension installation).
  • Balance example order: list Linux and Windows scenarios together, or alternate which is mentioned first.
  • Reference Linux-native tools or scripting patterns where appropriate, not just PowerShell.
  • Clarify that Azure CLI commands are cross-platform and provide sample commands in bash syntax.
GitHub Create Pull Request
Service Fabric Specifying Service Fabric service endpoints ...ce-fabric/service-fabric-service-manifest-resources.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ windows_tools
Summary
The documentation page provides several examples and deployment instructions using Windows-centric tools and patterns, notably PowerShell (e.g., New-ServiceFabricApplication) and references to Windows file paths (e.g., C:\Program Files\...). While Linux is mentioned briefly (regarding certificate store location), most practical deployment examples and tooling references are Windows-first or Windows-only, with no Linux CLI equivalents or parity in example ordering.
Recommendations
  • Provide equivalent Linux deployment examples using Service Fabric CLI (sfctl) or bash scripts alongside PowerShell examples.
  • Mention Linux file paths and configuration locations in parallel with Windows paths wherever relevant.
  • Clarify which commands and tooling are cross-platform, and link to Linux/macOS-specific documentation where available.
  • Order examples so that Linux and Windows are presented with equal prominence, or explicitly note platform-specific steps.
GitHub Create Pull Request
Service Fabric Learn Azure Service Fabric terminology ...es/service-fabric/service-fabric-technical-overview.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools
Summary
The documentation page is generally cross-platform and describes Service Fabric concepts applicable to both Windows and Linux. However, there is a subtle Windows bias in the 'Node' section, where Windows-specific tools and processes (auto-start Windows service, FabricHost.exe) are mentioned first and in detail, while Linux equivalents are not described. The terminology and examples tend to reference Windows processes and executable types (EXE/DLL) before mentioning Linux support. There are no explicit Linux/Unix examples or references to Linux-specific tools or patterns.
Recommendations
  • Add parallel descriptions for Linux nodes, including how Service Fabric is started and managed on Linux (e.g., systemd services, process names).
  • When referencing executables, clarify that on Linux, these may be ELF binaries and not EXE/DLL files.
  • Provide examples or notes for Linux-specific deployment and management patterns where they differ from Windows.
  • Ensure that mentions of Windows services and processes are balanced with Linux equivalents, or explicitly state when a concept is Windows-only.
GitHub Create Pull Request
Virtual Machines Azure Key Vault VM Extension for Linux ...rticles/virtual-machines/extensions/key-vault-linux.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 is focused on Linux, but several sections show Windows bias. PowerShell deployment examples are presented before Azure CLI, and troubleshooting instructions reference PowerShell first. There are no direct examples of using native Linux tools (e.g., Bash, cloud-init, or ARM templates via Linux shell), and the CLI examples use backticks (`) for line continuation, which is a Windows convention. The documentation does not provide explicit Linux shell command examples for deploying or troubleshooting the extension, nor does it discuss Linux-native automation approaches.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and preferred on Linux.
  • Use Bash-style line continuation (\) in CLI examples, not backticks (`), to match Linux shell conventions.
  • Add explicit Bash deployment examples (e.g., using az CLI from Linux shell).
  • Include troubleshooting steps using Linux tools (e.g., journalctl, systemctl, tail) to view logs and service status.
  • Reference Linux-native automation methods (cloud-init, Ansible, etc.) for extension deployment.
  • Clarify that PowerShell examples are optional and primarily for Windows users.
GitHub Create Pull Request
Virtual Machines Create and upload an Ubuntu Linux VHD in Azure ...rticles/virtual-machines/linux/create-upload-ubuntu.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation, while focused on Ubuntu Linux, repeatedly references Windows tools (notably Hyper-V and PowerShell's Convert-VHD) as the primary or only method for creating and converting VHDs. Linux-native alternatives for VHD creation and conversion (such as qemu-img or VBoxManage) are not mentioned, and the workflow assumes access to Hyper-V/Windows for critical steps. This creates friction for Linux/macOS users and may block those without Windows access.
Recommendations
  • Provide Linux-native instructions for creating and converting VHDs (e.g., using qemu-img, VBoxManage, or other open-source tools).
  • List Linux and cross-platform tools before or alongside Windows/Hyper-V options.
  • Include example commands for VHD conversion on Linux/macOS.
  • Clarify which steps require Windows/Hyper-V and offer alternatives where possible.
  • Consider adding a table comparing tool options for each OS.
GitHub Create Pull Request
Virtual Machines Create a VM from a generalized image in a gallery ...icles/virtual-machines/vm-generalized-image-version.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ windows_tools
Summary
The documentation provides both Azure CLI and PowerShell examples for creating VMs from generalized images in an Azure Compute Gallery. However, PowerShell examples are heavily focused on Windows workflows, with commands like Set-AzVMOperatingSystem -Windows and explicit references to Windows-specific configuration (e.g., RDP rules, Windows credential prompts). In several PowerShell code blocks, only Windows VM creation is shown, with no Linux equivalent. Additionally, in the full parameter set for PowerShell, the operating system is always set to Windows, and network security rules are configured for RDP (port 3389), which is Windows-specific. The CLI examples are more Linux-friendly, but PowerShell examples are presented before or alongside CLI, and the PowerShell workflow is Windows-centric. REST and Portal instructions do show both Linux and Windows options, but the PowerShell bias may create friction for Linux/macOS users who prefer scripting in PowerShell or need parity.
Recommendations
  • Add PowerShell examples for creating Linux VMs, using Set-AzVMOperatingSystem -Linux and appropriate credential handling (e.g., SSH keys).
  • In PowerShell sections, clarify when the example is Windows-only and provide Linux alternatives where possible.
  • Ensure network security group rules in PowerShell examples include SSH (port 22) for Linux VMs, not just RDP (port 3389) for Windows.
  • Consider presenting CLI examples before PowerShell, as CLI is cross-platform and more Linux/macOS friendly.
  • Explicitly state OS options in PowerShell examples, and provide guidance for both Windows and Linux VM creation.
GitHub Create Pull Request
Virtual Machine Scale Sets Attach or detach a virtual machine to or from a Virtual Machine Scale Set ...le-sets/virtual-machine-scale-sets-attach-detach-vm.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides Azure CLI, Azure PowerShell, and portal instructions for attaching/detaching VMs to/from VM Scale Sets. While Azure CLI is cross-platform and examples use Ubuntu images, PowerShell examples are given equal prominence and are shown immediately after CLI, which may imply parity but can be seen as Windows-centric since PowerShell is most commonly used on Windows. There is a minor 'windows_first' bias in troubleshooting links, which reference Windows-specific documentation for disk conversion and proximity placement group operations, even though Linux equivalents exist.
Recommendations
  • Clarify that Azure PowerShell is available on macOS/Linux, or provide Bash examples where appropriate.
  • Ensure troubleshooting links reference both Windows and Linux documentation for disk conversion and proximity placement group operations.
  • Consider listing CLI examples before PowerShell, as CLI is more universally available across platforms.
  • Explicitly state that all shown commands (CLI/PowerShell) are cross-platform unless there are platform-specific caveats.
GitHub Create Pull Request
Virtual Machine Scale Sets Custom metrics for rolling upgrades on Virtual Machine Scale Sets ...tual-machine-scale-sets-rolling-upgrade-custom-metrics.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation provides both Linux (Bash/Python) and Windows (PowerShell) examples for configuring the application health extension response, but there is a mild Windows bias in several areas. PowerShell examples are consistently present and sometimes shown before or alongside Linux equivalents. Windows-specific extension types (ApplicationHealthWindows) are used in code samples and REST payloads, sometimes before Linux equivalents. The REST and PowerShell sections use Windows extension types by default, and PowerShell is given equal or greater prominence than Bash. However, Linux parity is generally maintained, and CLI/Bash examples are present for all major workflows.
Recommendations
  • When showing extension type in JSON or REST samples, use ApplicationHealthLinux as the default or show both Linux and Windows variants.
  • In REST API examples, clarify that both ApplicationHealthLinux and ApplicationHealthWindows are valid, and provide explicit Linux-focused sample payloads.
  • Ensure Bash/Python examples are shown before or at least equally with PowerShell, especially in sections where Linux is the more common platform.
  • Add a note clarifying that all workflows are supported on both Linux and Windows VMSS, and highlight any platform-specific differences if present.
  • Consider adding more troubleshooting examples for Linux environments (e.g., systemd, firewall configuration) to match the PowerShell troubleshooting depth.
GitHub Create Pull Request
Virtual Machines Enable Trusted launch on existing Gen2 VMs ...rticles/virtual-machines/trusted-launch-existing-vm.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides parity for both Linux and Windows VMs, with clear indications that Trusted launch applies to both. However, there is a mild Windows bias in the ordering and tooling: PowerShell examples are provided and referenced frequently, and PowerShell commands are used for ARM template deployment and VM deallocation, even though Linux users would typically use Bash or Azure CLI. In several sections, Windows-centric tools (PowerShell, RDP) are mentioned before their Linux equivalents (CLI, SSH), and PowerShell is used for template deployment without an explicit Bash alternative.
Recommendations
  • Provide Bash shell equivalents for all PowerShell commands, especially for ARM template deployment and VM deallocation/start.
  • Where possible, show CLI/Bash examples before or alongside PowerShell, or clarify which commands are cross-platform.
  • Explicitly state that Azure CLI commands can be run from Bash on Linux/macOS, and provide sample Bash usage for template deployment.
  • Ensure that references to remote access methods (RDP/SSH) are presented with Linux/SSH first or equally.
  • Add a note clarifying that PowerShell is available cross-platform, but Bash/CLI is native to Linux/macOS.
GitHub Create Pull Request
Virtual Machines VM vCore Customization ...lob/main/articles/virtual-machines/vm-customization.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ minor_windows_tools
Summary
The documentation provides configuration instructions for VM vCore Customization using the Azure portal, Azure CLI, PowerShell, and ARM templates. While the CLI and ARM template examples are cross-platform, the PowerShell section is Windows-specific and is presented before any Linux/macOS shell alternatives (such as Bash or shell scripting). The CLI example uses Ubuntu as the image, but the PowerShell example is given equal prominence, which may create minor friction for Linux/macOS users. There are no Linux-specific shell examples (e.g., Bash), and PowerShell is referenced as a primary automation tool, which is more common on Windows.
Recommendations
  • Add Bash or shell script examples for Linux/macOS users alongside PowerShell, especially for automation scenarios.
  • Explicitly mention that Azure CLI is cross-platform and preferred for Linux/macOS users, while PowerShell is primarily for Windows.
  • Consider reordering examples to present CLI and ARM template options before PowerShell, or group platform-specific tools clearly.
  • Clarify in the PowerShell section that it is intended for Windows users, and suggest alternatives for Linux/macOS.
GitHub Create Pull Request
Service Fabric Azure Service Fabric container image management .../articles/service-fabric/container-image-management.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation page for Azure Service Fabric container image management shows mild Windows bias. Windows container base images (microsoft/windowsservercore, microsoft/nanoserver) are mentioned as default exclusions in cleanup, and no Linux container image examples (e.g., Ubuntu, Alpine) are provided. The configuration examples and descriptions do not reference Linux-specific considerations, and Windows images are listed first and exclusively in the 'ContainerImagesToSkip' setting.
Recommendations
  • Include examples of Linux container images (e.g., 'docker.io/library/ubuntu', 'docker.io/library/alpine') in the 'ContainerImagesToSkip' setting and documentation.
  • Clarify whether the cleanup features and settings apply equally to Linux containers, and mention any platform-specific differences if they exist.
  • Provide guidance or examples for clusters running Linux containers, ensuring parity in documentation for both Windows and Linux scenarios.
GitHub Create Pull Request
Service Fabric Describing Azure Service Fabric apps and services ...ic/service-fabric-application-and-service-manifests.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation contains mild Windows bias. It references opening the Service Fabric XSD schema in Visual Studio using a Windows file path, and suggests using the ServiceFabric PowerShell module to create service instances. There are no equivalent Linux/macOS tool suggestions or examples, and Windows tools are mentioned first and exclusively.
Recommendations
  • Add instructions or examples for validating manifest XML schema using cross-platform editors (e.g., VS Code) and note where the schema file is located on Linux clusters.
  • Mention or provide examples using Azure CLI or Service Fabric CLI (sfctl) for service creation, which are cross-platform, instead of only referencing PowerShell.
  • Where file paths or tools are Windows-specific, add Linux/macOS equivalents or clarify when a step is only relevant to Windows 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 ordering and emphasis: Windows container runtimes and scenarios (e.g., IIS lift and shift) are described before Linux equivalents, and Windows-specific tools (Mirantis Container Runtime, DockerEE) are listed in detail, while Linux is simply described as 'Docker'. The IIS scenario is Windows-only, but this is appropriate given its nature. Linux examples and tutorials are present and linked, but Windows scenarios tend to be described first or in more detail.
Recommendations
  • Present Linux and Windows examples and scenarios in parallel, rather than listing Windows first.
  • Provide more detail on Linux container runtimes and scenarios, such as common use cases (e.g., NGINX, Apache, Node.js) and Linux-specific best practices.
  • Ensure that Linux tutorials and samples are as prominently featured and described as Windows ones.
  • Where Windows-specific tools are listed, consider mentioning popular Linux alternatives or clarifying the parity.
GitHub Create Pull Request
Service Fabric Package an existing executable to Azure Service Fabric ...abric/service-fabric-guest-executables-introduction.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools
Summary
The documentation page demonstrates a mild Windows bias by referencing Windows file paths (e.g., C:\Program Files\Microsoft SDKs\Service Fabric\schemas\ServiceFabricServiceModel.xsd) and mentioning Visual Studio as a primary tool for packaging and deploying guest executables. There are no explicit Linux/macOS examples, nor are Linux-specific tools or file paths mentioned. However, the content itself is not exclusive to Windows and discusses general concepts applicable to any executable type.
Recommendations
  • Include Linux/macOS equivalents for SDK schema file paths and clarify where these files are located on non-Windows systems.
  • Provide command-line examples using cross-platform tools (e.g., Azure CLI, PowerShell Core, Bash) for packaging and deploying guest executables.
  • Mention alternative IDEs or editors (such as VS Code) and their usage for Linux/macOS users.
  • Add explicit notes or sections for Linux/macOS users to ensure parity in instructions and tooling.
GitHub Create Pull Request
Service Fabric Service communication with the ASP.NET Core ...vice-fabric-reliable-services-communication-aspnetcore.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ powershell_heavy
Summary
The documentation provides a balanced overview of both Kestrel (cross-platform) and HTTP.sys (Windows-only) web servers for ASP.NET Core in Azure Service Fabric. However, there is a notable emphasis on HTTP.sys, including detailed configuration and usage sections, despite it being Windows-only. Windows-specific tools and APIs (such as netsh and the Windows HTTP Server API) are referenced without always providing equivalent Linux/macOS guidance. The HTTP.sys section appears before the Kestrel section, and some explanations and diagrams focus on Windows-specific mechanisms. However, Kestrel is clearly recommended for cross-platform scenarios, and Linux users are not blocked from completing any tasks.
Recommendations
  • Move the Kestrel (cross-platform) section before the HTTP.sys (Windows-only) section to emphasize Linux/macOS parity.
  • Clearly label HTTP.sys sections and code samples as 'Windows-only' at the start of those sections.
  • Where Windows tools like netsh are mentioned, briefly note that these are not required or available on Linux/macOS, and clarify that Kestrel is the supported option for those platforms.
  • Consider adding a short summary or table at the top of the article indicating which web server options are cross-platform and which are Windows-only.
  • Ensure that all critical code samples and configuration steps are available for Kestrel, and that Linux/macOS users are not directed to Windows-only features.
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: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides usage instructions for Azure portal, REST API, Azure CLI, and Azure PowerShell. While all major cross-platform interfaces are covered, the PowerShell example is given its own section and is presented after CLI, which is cross-platform. The documentation does not show Linux-specific tools or shell examples (e.g., Bash/curl for REST API), and the PowerShell section may imply a slight Windows bias by highlighting PowerShell usage, which is most common on Windows.
Recommendations
  • Add explicit Bash/curl examples for the REST API section to demonstrate usage from Linux/macOS.
  • Clarify that Azure CLI is cross-platform and works on Linux/macOS/Windows.
  • Consider listing CLI and REST API examples before PowerShell, or grouping them together to avoid implying a Windows-first workflow.
  • Mention that PowerShell Core is available on Linux/macOS if relevant, or clarify when examples are Windows-only.
GitHub Create Pull Request
Virtual Machine Scale Sets Configure rolling upgrades on Virtual Machine Scale Sets ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-configure-rolling-upgrades.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring, monitoring, canceling, and restarting rolling upgrades on Virtual Machine Scale Sets. However, PowerShell examples are given equal prominence to CLI, and in some sections (such as setting/updating the rolling upgrade policy), the PowerShell tab appears immediately after CLI, which may imply a slight Windows-first orientation. There are no Linux-specific tools or shell script examples, but the Azure CLI commands are fully cross-platform. No critical functionality is locked to Windows-only tools, and ARM template examples are also provided.
Recommendations
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows equally.
  • Consider listing CLI examples before PowerShell in all sections, or explicitly note CLI is cross-platform.
  • Add a brief note for Linux/macOS users that PowerShell examples are optional and CLI is recommended for cross-platform automation.
  • If possible, provide Bash script snippets for common automation scenarios to further demonstrate Linux parity.
GitHub Create Pull Request
Virtual Machines Time sync for Linux VMs in Azure ...blob/main/articles/virtual-machines/linux/time-sync.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ windows_first
Summary
The documentation page is focused on time synchronization for Linux VMs in Azure and provides comprehensive Linux-specific guidance. However, the introductory section discusses Windows Server 2016 time sync improvements and Windows host algorithms before explaining Linux mechanisms, which may create a perception of 'windows_first' bias. All configuration examples, tools, and troubleshooting steps are Linux-centric, with no PowerShell or Windows-specific commands or tools used for Linux VM configuration.
Recommendations
  • Move the Windows Server 2016 time sync discussion to a background or infrastructure section, clarifying its relevance to Linux VMs.
  • Begin the overview with Linux-specific time sync mechanisms and Azure's support for Linux time sync, then mention host infrastructure details as context.
  • Add a brief statement clarifying that while Azure hosts run Windows Server, all configuration and management for Linux VMs is performed using Linux-native tools.
GitHub Create Pull Request
Virtual Machine Scale Sets Networking for Azure Virtual Machine Scale Sets ...ne-scale-sets/virtual-machine-scale-sets-networking.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation provides both Azure CLI and PowerShell examples for most networking tasks with Azure Virtual Machine Scale Sets, but PowerShell (Windows-centric) examples are often presented before CLI (cross-platform) examples. In some sections, only PowerShell examples are given for querying resources, with CLI shown later or not at all. There are no Linux/macOS-specific shell examples (e.g., Bash scripts), and Windows tools/patterns (PowerShell) are sometimes prioritized. However, most tasks can be completed using the CLI, which is cross-platform.
Recommendations
  • Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and preferred for Linux/macOS users.
  • Ensure every PowerShell example has a corresponding Azure CLI example.
  • Where possible, provide Bash script snippets for Linux/macOS users, especially for tasks involving scripting or automation.
  • Explicitly state that Azure CLI works on Windows, Linux, and macOS to guide users.
  • Review sections where only PowerShell is shown (e.g., querying public IPs) and add CLI equivalents.
  • Avoid language that implies PowerShell is the default or preferred method unless the feature is Windows-only.
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: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides examples for creating an Azure Compute Gallery using the Portal, Azure CLI, PowerShell, and REST API. While the CLI and REST examples are cross-platform, PowerShell examples are included and presented as a primary method alongside CLI, and the ordering of examples often places PowerShell before REST. There is a mild 'Windows-first' bias in the inclusion and ordering of PowerShell examples, which are only relevant to Windows users. However, Linux/macOS users are not blocked from completing any tasks, as CLI and REST examples are present and fully functional.
Recommendations
  • Clearly indicate that PowerShell examples are Windows-only and suggest CLI/REST for Linux/macOS users.
  • Consider placing CLI examples before PowerShell examples to emphasize cross-platform support.
  • Add a note at the top of the example sections clarifying platform compatibility for each method.
  • Ensure parity in example detail and completeness between CLI and PowerShell sections.
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 in several places, Windows/PowerShell examples are presented before Linux/CLI equivalents. The PowerShell tab examples use Windows as the default, while the CLI tab uses Linux. The introductory OS-specific guidance lists Linux first, but the PowerShell section defaults to Windows, and PowerShell is inherently a Windows-centric tool (though available on Linux, it's less common for Linux users). No critical Linux examples or tools are missing, but the ordering and example defaults show a mild Windows bias.
Recommendations
  • Alternate the order of CLI and PowerShell examples so Linux/CLI is not always second.
  • In PowerShell examples, default to Linux where appropriate or provide both Linux and Windows variants.
  • Explicitly state that PowerShell commands can be run on Linux, but CLI is more common for Linux workflows.
  • Ensure parity in example depth and clarity between CLI and PowerShell sections.
  • Consider adding Bash script examples for Linux users where complex workflows are shown.
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 ⚠️ missing_linux_example
Summary
The documentation provides both Azure CLI and PowerShell examples for key tasks, but PowerShell examples are often shown alongside or before CLI, and some references (such as finding Marketplace images) link to Windows/PowerShell-specific pages first. In some cases, Linux equivalents are mentioned but not given equal prominence or example coverage. There are also references to Windows tools (Sysprep) before Linux equivalents (waagent), and some links for uploading VHDs are split into Windows and Linux, but the Windows link appears first. Overall, while the documentation is not exclusively Windows-focused, there is a mild bias toward Windows/PowerShell in example ordering and reference links.
Recommendations
  • Ensure Azure CLI examples are presented before or alongside PowerShell, as CLI is cross-platform.
  • When referencing external guides (e.g., uploading VHDs), present Linux and Windows links together or in parallel, not with Windows first.
  • Provide explicit Linux-focused examples or references where only Windows/PowerShell examples are given.
  • When mentioning tools (e.g., Sysprep vs waagent), present both with equal prominence and detail.
  • Audit linked documentation to ensure Linux parity in referenced guides.
GitHub Create Pull Request
Virtual Machines vCPU quotas ...ute-docs/blob/main/articles/virtual-machines/quotas.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for checking vCPU quotas, but the PowerShell example is given equal prominence and detail, and the CLI example is not explicitly labeled as Linux/macOS-friendly. The tab order places CLI first, but PowerShell is presented as a full alternative, which may create a slight Windows bias. No Linux-specific tools or shell examples are provided, but the CLI example is cross-platform.
Recommendations
  • Explicitly note that Azure CLI works on Linux, macOS, and Windows, and is the recommended cross-platform tool.
  • Add a brief example of running the Azure CLI command in a Linux/macOS shell (e.g., bash), or clarify that the CLI example is suitable for Linux/macOS users.
  • Consider mentioning that PowerShell Core is available on Linux/macOS if relevant, or clarify if the PowerShell example is Windows-only.
  • If possible, add troubleshooting notes for common Linux/macOS issues (e.g., authentication, environment setup) when using Azure CLI.
GitHub Create Pull Request