Service Fabric

407
Total Pages
335
Linux-Friendly Pages
72
Pages with Bias
17.7%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

2475 issues found
Showing 1801-1825 of 2475 flagged pages
Service Fabric Service communication with the ASP.NET Core ...vice-fabric-reliable-services-communication-aspnetcore.md
Medium Priority View Details →
Scanned: 2026-02-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation provides detailed coverage of both Kestrel (cross-platform) and HTTP.sys (Windows-only) web servers for ASP.NET Core in Service Fabric. However, HTTP.sys is discussed first and in greater depth, with Windows-specific concepts (like netsh, Windows HTTP Server API, and kernel driver) explained extensively. Windows tools and patterns (e.g., ServiceManifest.xml Endpoint configuration for HTTP.sys, netsh usage) are mentioned without Linux equivalents. There are no explicit Linux/macOS-specific examples or guidance, and some sections (e.g., endpoint configuration, port assignment) focus on Windows behaviors before cross-platform considerations. While Kestrel is recommended for Linux, Linux-specific troubleshooting, deployment, or configuration details are missing.
Recommendations
  • Reorder sections to discuss Kestrel (cross-platform) before HTTP.sys (Windows-only), emphasizing Linux/macOS parity.
  • Add explicit Linux/macOS examples and guidance for Service Fabric Reliable Services with ASP.NET Core, including deployment, port configuration, and troubleshooting.
  • Clarify that HTTP.sys is Windows-only earlier in the document and highlight Kestrel as the default for Linux/macOS scenarios.
  • Provide Linux/macOS-specific notes for ServiceManifest.xml endpoint configuration, firewall handling, and certificate management.
  • Include links or references to Linux/macOS development environment setup and debugging tools.
GitHub Create Pull Request
Service Fabric Add custom Service Fabric health reports ...rticles/service-fabric/service-fabric-report-health.md
Medium Priority View Details →
Scanned: 2026-02-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed examples for health reporting in Service Fabric using PowerShell, which is Windows-centric, and shows PowerShell examples before REST. There are no equivalent Linux/bash or cross-platform CLI examples for health reporting, nor is there guidance for Linux users on how to perform these tasks outside of PowerShell. The REST API is mentioned but not demonstrated with concrete examples, and the PowerShell examples dominate the practical guidance.
Recommendations
  • Add equivalent examples using Azure CLI or bash scripts for health reporting, especially for Linux/macOS users.
  • Provide explicit guidance on using REST APIs with curl or similar tools, including sample requests and responses.
  • Clarify which tools are cross-platform and which are Windows-only, and recommend alternatives for Linux/macOS users.
  • Consider including a section on using Service Fabric SDKs or tools on Linux, if supported.
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 →
Scanned: 2026-02-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page for 'Replica soft delete for enhanced data protection in Service Fabric' demonstrates notable Windows bias. All command-line/API examples reference PowerShell cmdlets (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica), and there is no mention of Linux equivalents or cross-platform CLI usage. The documentation assumes the use of Windows tooling and APIs, with no guidance for Linux/macOS users on how to perform equivalent operations. This creates friction for non-Windows users, though workarounds may exist via FabricClient APIs or REST endpoints.
Recommendations
  • Add examples using cross-platform Service Fabric CLI (sfctl) where possible, alongside PowerShell examples.
  • Clarify whether the new APIs (e.g., Restore-ServiceFabricReplica) are accessible via sfctl or REST, and provide usage instructions for Linux/macOS users.
  • Explicitly state platform support for the administrative APIs and tools, and link to relevant Linux/macOS documentation.
  • If PowerShell is required, note any limitations for Linux users and suggest alternatives.
GitHub Create Pull Request
Service Fabric Specifying Service Fabric service endpoints ...ce-fabric/service-fabric-service-manifest-resources.md
Medium Priority View Details →
Scanned: 2026-02-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides a PowerShell example for deploying applications, which is Windows-centric. Windows file paths and certificate store names are referenced first, with Linux equivalents mentioned later and only briefly. There are no Linux CLI (e.g., Bash or sfctl) deployment examples, and Windows terminology/tools (like PowerShell) are presented before Linux alternatives.
Recommendations
  • Add Linux/macOS deployment examples using sfctl or Bash scripts alongside PowerShell examples.
  • Mention Linux file paths and certificate store locations earlier and more prominently.
  • Clarify cross-platform differences in endpoint/certificate handling and deployment commands.
  • Provide parity in tooling references (e.g., show both PowerShell and sfctl for application deployment).
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 →
Scanned: 2026-02-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation is heavily focused on Visual Studio workflows, which are Windows-centric, and repeatedly references PowerShell as the tool for creating service instances. There are no examples or guidance for Linux/macOS users, nor are cross-platform tools or CLI alternatives mentioned. The documentation implicitly assumes Windows as the primary development environment for Service Fabric applications.
Recommendations
  • Add explicit guidance for Linux/macOS users, including how to manage Service Fabric applications and service configuration using cross-platform tools like Azure CLI or Service Fabric CLI.
  • Include examples for deploying and configuring Service Fabric applications on Linux clusters, or clarify if StartupServices.xml is not supported outside Visual Studio/Windows.
  • Mention alternative editors (e.g., VS Code) and workflows for non-Windows environments, if applicable.
  • If StartupServices.xml is strictly a Visual Studio feature, add a clear note stating its Windows-only scope to reduce confusion.
GitHub Create Pull Request
Service Fabric Fault Analysis Service overview .../service-fabric/service-fabric-testability-overview.md
Medium Priority View Details →
Scanned: 2026-02-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page for the Fault Analysis Service overview in Azure Service Fabric presents usage examples and tooling primarily for C# and PowerShell, with explicit instructions for PowerShell (a Windows-centric tool) and no mention of Linux or cross-platform CLI alternatives. There is no guidance for Linux/macOS users on how to interact with the Fault Analysis Service, such as using Azure CLI, REST APIs, or Service Fabric CLI (sfctl).
Recommendations
  • Add examples for using the Fault Analysis Service with Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • Include instructions for invoking Fault Analysis Service APIs via REST, which is platform-agnostic.
  • Clarify that PowerShell is Windows-specific and provide Linux/macOS alternatives where possible.
  • Reorder examples so that cross-platform options (e.g., sfctl, REST) are presented before or alongside PowerShell.
GitHub Create Pull Request
Service Fabric Standalone Service Fabric clusters overview ...-fabric/service-fabric-standalone-clusters-overview.md
Medium Priority View Details →
Scanned: 2026-02-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
Although the introduction claims Service Fabric clusters can run on both Windows Server and Linux, the documentation page only provides details and examples for Windows environments. The 'Supported operating systems' section explicitly states that Linux isn't yet supported for standalone clusters, and all security and scaling guidance is Windows-centric. Linux-specific instructions, examples, or parity are missing throughout.
Recommendations
  • Clarify in the introduction that standalone clusters are currently Windows-only, despite the general Service Fabric platform supporting Linux.
  • Remove or revise statements implying Linux support for standalone clusters unless Linux support is imminent.
  • Add a section outlining Linux support status and roadmap, if relevant.
  • If Linux support is planned, provide equivalent Linux examples, tools, and instructions alongside Windows guidance.
  • Ensure that future updates include Linux-specific guidance as soon as support is available.
GitHub Create Pull Request
Service Fabric Application upgrade: upgrade parameters ...abric/service-fabric-application-upgrade-parameters.md
Medium Priority View Details →
Scanned: 2026-02-05 00:00
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 →
Scanned: 2026-02-05 00:00
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 →
Scanned: 2026-02-05 00:00
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 →
Scanned: 2026-02-05 00:00
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 →
Scanned: 2026-02-05 00:00
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 →
Scanned: 2026-02-05 00:00
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 →
Scanned: 2026-02-05 00:00
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 →
Scanned: 2026-02-05 00:00
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 →
Scanned: 2026-02-05 00:00
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
Service Fabric Manage certificates in a Service Fabric cluster ...vice-fabric/cluster-security-certificate-management.md
Medium Priority View Details →
Scanned: 2026-02-05 00:00
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 →
Scanned: 2026-02-05 00:00
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 →
Scanned: 2026-02-05 00:00
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 →
Scanned: 2026-02-05 00:00
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 →
Scanned: 2026-02-05 00:00
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 →
Scanned: 2026-02-05 00:00
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 →
Scanned: 2026-02-05 00:00
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 →
Scanned: 2026-02-05 00:00
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 →
Scanned: 2026-02-05 00:00
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
← Previous Page 73 of 99 Next →