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 1151-1175 of 2475 flagged pages
Service Fabric Azure Service Fabric application resource model ...ervice-fabric/service-fabric-concept-resource-model.md
Medium Priority View Details →
Scanned: 2026-02-20 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates notable Windows bias. All deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) with no mention of Azure CLI equivalents or Linux/macOS-friendly workflows. Application packaging is described via Visual Studio, a Windows-centric tool, with no alternative for Linux/macOS users. There are no examples or guidance for Linux/macOS users, and Windows tools are referenced first and exclusively.
Recommendations
  • Add Azure CLI examples for deployment, upgrade, and deletion tasks (e.g., az deployment group create, az resource delete).
  • Provide guidance for packaging Service Fabric applications using cross-platform tools (such as dotnet CLI or manual zip commands) instead of only Visual Studio.
  • Include instructions and screenshots for Linux/macOS environments where applicable.
  • Clearly indicate which steps are Windows-only and offer alternatives for other platforms.
  • Consider referencing cross-platform editors (e.g., VS Code) for editing manifest and template files.
GitHub Create Pull Request
Service Fabric Learn more about Azure Service Fabric ...icles/service-fabric/service-fabric-content-roadmap.md
Medium Priority View Details →
Scanned: 2026-02-20 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation provides a broad overview of Azure Service Fabric, which is a cross-platform service supporting both Windows and Linux. However, there are several areas where Windows-specific tools, terminology, and examples are mentioned first or exclusively. Windows services and executables (e.g., FabricHost.exe, Fabric.exe) are referenced without Linux equivalents or clarifications. PowerShell is often listed before CLI or REST alternatives. Standalone cluster creation is only supported on Windows, but this is clearly stated. There is a lack of explicit Linux command examples or parity in tooling references, and Windows terminology (e.g., 'auto-start Windows service') is used without Linux context.
Recommendations
  • Where possible, provide Linux-specific examples, especially for cluster management, health queries, and application lifecycle tasks.
  • When referencing tools (e.g., PowerShell, Service Fabric Explorer), ensure CLI and REST API alternatives are equally highlighted and described.
  • Clarify when features, tools, or terminology are Windows-only, and provide Linux equivalents or note limitations.
  • Add explicit Linux command-line examples (using sfctl or bash) alongside PowerShell examples.
  • Review the order of tool references to avoid always listing Windows tools first.
GitHub Create Pull Request
Service Fabric Package an existing executable to Azure Service Fabric ...abric/service-fabric-guest-executables-introduction.md
Medium Priority View Details →
Scanned: 2026-02-20 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias. It references Windows file paths (e.g., 'C:\Program Files\Microsoft SDKs\Service Fabric\schemas\ServiceFabricServiceModel.xsd'), and does not provide Linux/macOS equivalents or examples. There are no explicit Linux packaging or deployment instructions, and Visual Studio (a Windows-centric tool) is mentioned as a primary method. The directory structure example uses a Windows-style executable (.exe), and there is no mention of Linux binaries or cross-platform packaging considerations.
Recommendations
  • Add Linux/macOS equivalents for SDK schema file locations, or clarify if the SDK is available on those platforms.
  • Include examples for packaging and deploying Linux/macOS executables (e.g., .sh, ELF binaries) alongside Windows (.exe) examples.
  • Mention cross-platform command-line tools (such as Azure CLI or Service Fabric CLI) and provide instructions for Linux/macOS users.
  • Clarify Visual Studio alternatives for Linux/macOS users, or link to relevant cross-platform tooling.
  • Explicitly state platform support and limitations for guest executables in Service Fabric clusters.
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-20 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides a conceptual overview of Service Fabric activation and deactivation lifecycle, but the 'Next steps' section and some linked examples reference PowerShell and Windows-centric tools without mentioning Linux equivalents. There are no explicit Linux/bash examples or references to Linux tooling, and PowerShell is presented as the primary method for deployment/removal, which may create friction for Linux/macOS users.
Recommendations
  • Add equivalent Linux/bash examples for deploying and removing applications, referencing the Service Fabric CLI (sfctl) or REST API.
  • In the 'Next steps' section, include links to Linux/macOS deployment/removal documentation alongside PowerShell.
  • Clarify in the text that Service Fabric supports both Windows and Linux clusters, and highlight any platform-specific differences.
  • Where PowerShell is mentioned, add a note or alternative example for Linux users.
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 →
Scanned: 2026-02-20 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page for Azure Service Fabric container application manifest examples demonstrates a Windows bias. The manifest examples are based on a Windows Server 2016 container sample, and references to Windows-specific tools (e.g., 'winver' for OS build detection) are present. There are no explicit Linux-based manifest examples or instructions, and the only mention of Linux is in passing (e.g., certificate handling differences), without concrete Linux-focused guidance or samples.
Recommendations
  • Provide parallel manifest examples based on a Linux container sample, or clarify which elements differ for Linux clusters.
  • When referencing OS build detection, include Linux equivalents (e.g., 'cat /etc/os-release' or 'uname -r') alongside Windows instructions.
  • Explicitly state which manifest elements or features are Windows-only, and which are cross-platform, to help Linux users understand applicability.
  • Add links or references to Linux-specific Service Fabric container documentation where relevant.
  • If certain features (like volume drivers or isolation modes) differ on Linux, note these differences and provide Linux-appropriate configuration guidance.
GitHub Create Pull Request
Service Fabric Health monitoring in Service Fabric ...s/service-fabric/service-fabric-health-introduction.md
Medium Priority View Details →
Scanned: 2026-02-20 00:00
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, with most of the content being platform-neutral. However, the only concrete example of reporting and evaluating health uses PowerShell cmdlets, which are Windows-centric tools. There are no equivalent examples for Linux or cross-platform environments (e.g., using REST API, CLI, or SDKs), and PowerShell is referenced as the primary method for health reporting. This creates friction for Linux/macOS users, who may not have access to these cmdlets or may prefer other tools.
Recommendations
  • Add equivalent examples using the Service Fabric REST API for health reporting and querying, which are cross-platform.
  • Include code snippets using the Service Fabric SDKs (e.g., .NET Core, Java) for reporting health, which work on Linux/macOS.
  • Mention and provide examples using Azure CLI or Bash scripts if available.
  • Clarify in the example section that PowerShell is one option, and link to documentation for other platforms and tools.
GitHub Create Pull Request
Service Fabric Azure Service Fabric hosting model ...rticles/service-fabric/service-fabric-hosting-model.md
Medium Priority View Details →
Scanned: 2026-02-20 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides PowerShell examples for creating services and managing Service Fabric hosting models, but does not include equivalent Linux CLI (e.g., sfctl) or bash examples. PowerShell is presented as the primary method, with REST and .NET API alternatives mentioned, but Linux-native tooling is absent. References to PowerShell cmdlets are frequent and appear before REST or .NET options, creating friction for Linux/macOS users.
Recommendations
  • Add equivalent examples using sfctl (Service Fabric CLI) for Linux/macOS users alongside PowerShell examples.
  • Explicitly mention that all operations shown with PowerShell can be performed with sfctl or REST API, and provide links or sample commands.
  • Where PowerShell cmdlets are referenced, include corresponding sfctl commands in the same section or immediately after.
  • Clarify any platform-specific limitations if certain features are not available on Linux clusters.
GitHub Create Pull Request
Service Fabric Azure Service Fabric image store connection string ...fabric/service-fabric-image-store-connection-string.md
Medium Priority View Details →
Scanned: 2026-02-20 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows/PowerShell environments. It references PowerShell for retrieving the cluster manifest and links to a PowerShell-based deployment guide as the next step, without providing equivalent Linux/bash or cross-platform CLI examples. The mention of Visual Studio (a primarily Windows tool) for publishing to Azure further reinforces the Windows-centric approach. There are no explicit Linux or macOS instructions or examples for managing the ImageStoreConnectionString.
Recommendations
  • Add Azure CLI or bash examples for retrieving the cluster manifest and managing the ImageStoreConnectionString, ensuring Linux/macOS users have clear guidance.
  • Include references or links to cross-platform tools or documentation (e.g., Azure CLI, REST API usage with curl) alongside or before PowerShell examples.
  • Mention Visual Studio Code as an alternative to Visual Studio for cross-platform development, if applicable.
  • Provide a 'Next steps' link to a cross-platform deployment guide, not just PowerShell.
GitHub Create Pull Request
Service Fabric Service communication with the ASP.NET Core ...vice-fabric-reliable-services-communication-aspnetcore.md
Medium Priority View Details →
Scanned: 2026-02-20 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation covers both Windows (HTTP.sys) and cross-platform (Kestrel) web servers for ASP.NET Core in Service Fabric. However, Windows-specific tools and APIs (HTTP.sys, Windows HTTP Server API, netsh) are discussed in detail, with explicit notes about Windows-only support. Kestrel, the cross-platform option, is recommended for Linux, but Linux-specific configuration, troubleshooting, or example code is not provided. Windows tools and patterns (e.g., netsh, ServiceManifest.xml endpoint registration) are mentioned before Linux equivalents, and Linux users may lack guidance for certain scenarios.
Recommendations
  • Add explicit Linux/macOS example configurations, especially for ServiceManifest.xml and Kestrel usage.
  • Include troubleshooting tips for Linux deployments (e.g., firewall, port assignment, certificate management for HTTPS).
  • Clarify any OS-specific limitations or differences for Service Fabric on Linux, such as port assignment, endpoint registration, and service discovery.
  • Provide links or references to Linux-specific Service Fabric documentation where relevant.
  • Ensure that all code samples and configuration snippets are annotated with their OS applicability.
GitHub Create Pull Request
Service Fabric Networking patterns for Azure Service Fabric ...s/service-fabric/service-fabric-patterns-networking.md
Medium Priority View Details →
Scanned: 2026-02-20 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides deployment instructions and examples exclusively using PowerShell commands, with no mention of Azure CLI, Bash, or Linux/macOS-compatible tooling. Windows-centric tools (PowerShell, RDP, Windows-style file paths) are referenced throughout, and Windows command-line examples are shown first or exclusively. There are no Linux/macOS equivalents or guidance for cross-platform users, despite Service Fabric supporting Linux clusters and Azure Resource Manager templates being deployable from any OS.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all deployment steps, including resource group and template deployment.
  • Mention Bash/terminal usage and provide Linux/macOS-friendly file path examples.
  • Clarify that ARM templates can be deployed from any OS, and link to cross-platform deployment documentation.
  • Include SSH instructions for accessing VMs instead of only referencing RDP.
  • Explicitly state Windows-specific steps where relevant, and provide Linux alternatives where possible.
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-20 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 Service Fabric applications, which is a Windows-centric tool. Windows file paths and certificate store names (e.g., 'MY') are referenced first, though Linux equivalents are briefly mentioned. There are no Linux CLI or bash examples for deployment, and Windows terminology/tools are presented before Linux alternatives.
Recommendations
  • Add equivalent Linux CLI (e.g., sfctl) or bash examples for deploying applications and passing parameters.
  • Mention Linux file paths and certificate store locations alongside Windows paths, not just as a note.
  • Clarify any differences in endpoint/certificate handling between Windows and Linux clusters.
  • Where PowerShell is used, provide a Linux command alternative or link to relevant Linux tooling documentation.
GitHub Create Pull Request
Service Fabric Define Service Configuration in StartupServices.xml for a Service Fabric Application ...service-fabric/service-fabric-startupservices-model.md
Medium Priority View Details →
Scanned: 2026-02-20 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation is heavily focused on Visual Studio workflows (Build/Rebuild/F5/Ctrl+F5/Publish), which are Windows-centric. All examples and instructions reference Visual Studio and Windows-specific deployment patterns, with no mention of Linux/macOS equivalents or cross-platform tooling. There are references to PowerShell modules for service creation, but no Linux CLI or scripting alternatives are provided. The documentation does not clarify how Linux/macOS users can achieve similar workflows, nor does it mention cross-platform Service Fabric tooling.
Recommendations
  • Add explicit guidance for Linux/macOS users, including how to manage service configuration and deployment without Visual Studio.
  • Provide CLI-based examples (using Azure CLI, sfctl, or other cross-platform tools) for deploying and configuring Service Fabric applications.
  • Clarify which features are Visual Studio/Windows-only and offer alternatives or workarounds for Linux/macOS environments.
  • Mention any limitations or differences for Linux/macOS users upfront, so expectations are clear.
GitHub Create Pull Request
Service Fabric Fault Analysis Service overview .../service-fabric/service-fabric-testability-overview.md
Medium Priority View Details →
Scanned: 2026-02-20 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides usage examples for PowerShell and C#, both of which are most commonly associated with Windows environments. There are no Linux-specific CLI or scripting examples (e.g., Bash, Azure CLI), nor is there mention of Linux tooling or patterns. PowerShell is highlighted as the primary scripting interface, and no Linux/macOS equivalents or guidance are given.
Recommendations
  • Add examples for using Fault Analysis Service via Azure CLI or Bash scripts, if supported.
  • Clarify whether the Fault Analysis Service APIs can be accessed from Linux/macOS environments, and provide guidance for those platforms.
  • Mention cross-platform SDKs or tools (e.g., Python, Java) if available, and provide sample usage.
  • If PowerShell Core (cross-platform) is supported, specify this and provide Linux/macOS installation instructions.
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-20 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page for 'Replica soft delete for enhanced data protection in Service Fabric' heavily references PowerShell cmdlets (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica) and administrative APIs without providing equivalent examples or guidance for Linux/macOS users. All command-line examples and API references are Windows-centric, and there is no mention of Linux tooling or cross-platform alternatives. The documentation assumes familiarity with Windows tools and patterns, creating friction for users operating Service Fabric clusters on Linux.
Recommendations
  • Add examples using Service Fabric CLI (sfctl), which is cross-platform and supported on Linux/macOS.
  • Clarify whether the PowerShell APIs are available via REST or other SDKs usable from Linux/macOS.
  • Provide sample commands for querying, removing, and restoring replicas using sfctl or FabricClient APIs in non-Windows environments.
  • Explicitly state platform limitations if certain features are Windows-only, or highlight parity where available.
  • Include screenshots or output examples from Linux terminals where relevant.
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-20 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides extensive PowerShell examples and references, with no equivalent Linux or cross-platform CLI examples. Windows/PowerShell tools are mentioned first and exclusively in example sections, creating friction for Linux/macOS users who may not have access to PowerShell or Windows-specific Service Fabric tooling.
Recommendations
  • Add equivalent examples using Azure CLI or Service Fabric CLI (sfctl), which are cross-platform and supported on Linux/macOS.
  • Explicitly mention that PowerShell commands are Windows-specific and provide guidance for Linux/macOS users.
  • Include REST API examples with curl or similar tools for Linux/macOS users, especially in sections where PowerShell is used.
  • Reorder examples so that cross-platform methods (API, REST, CLI) are presented before or alongside Windows/PowerShell methods.
GitHub Create Pull Request
Service Fabric Custom Image .../articles/service-fabric/how-to-deploy-custom-image.md
Medium Priority View Details →
Scanned: 2026-02-19 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page primarily discusses deploying custom Windows images in Service Fabric Managed Clusters, with Windows terminology and PowerShell examples shown. While Linux custom image creation is referenced, the main focus and examples are Windows-centric, and the PowerShell command is given without a Linux CLI equivalent.
Recommendations
  • Clarify at the top whether Linux node types are supported for custom images in Service Fabric Managed Clusters.
  • Provide equivalent Azure CLI examples for role assignment (e.g., az role assignment create) alongside PowerShell.
  • Include explicit guidance or examples for deploying Linux custom images if supported, such as ARM template snippets for Linux VM images.
  • Balance terminology to refer to both Windows and Linux images where applicable, rather than only 'custom windows images'.
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-19 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page for RunToCompletion semantics in Service Fabric presents Windows container examples exclusively, references Windows-specific container images, and uses Windows command syntax (cmd, echo, set, ping). PowerShell is the only CLI example given for querying deployment status, with no mention of Linux or cross-platform alternatives. There is no guidance or example for Linux containers or querying status from Linux/macOS environments.
Recommendations
  • Add Linux container examples (e.g., using Ubuntu or Alpine images) alongside Windows container examples.
  • Provide equivalent shell command examples (bash/sh) for Linux containers, replacing Windows cmd syntax.
  • Include instructions for querying deployment status using Service Fabric CLI (sfctl) or REST API, which are cross-platform.
  • Clarify whether RunToCompletion semantics are supported for Linux containers, and if so, provide relevant guidance.
  • Mention any platform-specific limitations explicitly, so Linux/macOS users know what is and isn't supported.
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 →
Scanned: 2026-02-19 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides several PowerShell-based manual scaling instructions and references Windows-centric tooling (e.g., PowerShell cmdlets like Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState) without offering equivalent Linux CLI or script examples. Windows/PowerShell instructions are presented first and exclusively in critical scaling workflows, creating friction for Linux users. While Service Fabric supports Linux clusters, the manual scaling guidance is not platform-neutral.
Recommendations
  • Add equivalent Linux CLI instructions (e.g., using sfctl or Service Fabric REST API) alongside PowerShell examples for node management.
  • Clearly indicate which steps are platform-specific and provide links or references to Linux documentation where appropriate.
  • Where possible, use platform-neutral language and tooling (e.g., ARM templates, REST API) for examples.
  • Include a section or callout for Linux users detailing how to perform scaling operations using Linux-compatible tools.
GitHub Create Pull Request
Service Fabric Application upgrade: upgrade parameters ...abric/service-fabric-application-upgrade-parameters.md
Medium Priority View Details →
Scanned: 2026-02-19 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page presents upgrade parameters for Service Fabric applications, but it exhibits Windows bias by prioritizing PowerShell and Visual Studio (Windows tools) in both structure and examples. The PowerShell and Visual Studio sections are detailed and appear first, while Linux-friendly tools (SFCTL CLI) are covered later and with less emphasis. There are no explicit Linux command examples or walkthroughs in the main content, and the parameter tables focus on PowerShell/Visual Studio, with SFCTL parameters separated. Although the 'Next steps' section links to Linux CLI guides, the main article lacks parity in examples and guidance for Linux/macOS users.
Recommendations
  • Add Linux/SFCTL CLI examples alongside PowerShell examples in parameter tables and explanations.
  • Reorganize the page so that SFCTL CLI (cross-platform) is presented equally or before Windows-specific tools.
  • Include explicit notes or guidance for Linux/macOS users in relevant sections.
  • Ensure parameter descriptions reference both Windows and Linux tools where applicable.
  • Consider adding a comparison table showing how to perform upgrades using PowerShell, Visual Studio, SFCTL CLI, and REST, with OS applicability.
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 →
Scanned: 2026-02-19 00:00
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 CLI examples are PowerShell-based, with no equivalent Bash or Linux CLI examples. The PowerShell examples are shown alongside C# and manifest examples, but there is no mention of Linux-specific tools or commands. Additionally, the documentation does not clarify whether the PowerShell commands are usable on Linux (via PowerShell Core), nor does it provide guidance for Linux users who may prefer Bash or other scripting environments.
Recommendations
  • Add Bash or Azure CLI examples for configuring scaling policies, especially for Linux users.
  • Clarify whether PowerShell examples are compatible with PowerShell Core on Linux, or provide alternative instructions for Linux environments.
  • Mention any Linux-specific considerations or limitations when configuring auto scaling policies.
  • If certain features are Windows-only, explicitly state so to avoid confusion.
GitHub Create Pull Request
Service Fabric Cluster Resource Manager - Management Integration ...fabric-cluster-resource-manager-management-integration.md
Medium Priority View Details →
Scanned: 2026-02-19 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides a PowerShell example (Get-ServiceFabricPartitionHealth) for querying health reports but does not offer equivalent examples or commands for Linux/macOS environments. There is no mention of cross-platform CLI tools (such as sfctl) or REST API alternatives, which may create friction for non-Windows users.
Recommendations
  • Include equivalent examples using sfctl (Service Fabric CLI), which is cross-platform and works on Linux/macOS.
  • Mention REST API options for querying health reports, with example requests.
  • Clarify that PowerShell examples are for Windows and provide links or code snippets for Linux/macOS users.
  • Consider a table or section summarizing management tool parity across platforms.
GitHub Create Pull Request
Service Fabric Manage apps for multiple environments ...e-fabric-manage-multiple-environment-app-configuration.md
Medium Priority View Details →
Scanned: 2026-02-19 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides examples for specifying parameters during application creation, with PowerShell and Visual Studio mentioned first and in detail. Linux-friendly tools like sfctl are referenced, but not explained as thoroughly, and there is no explicit Linux/macOS workflow example. The use of PowerShell and Visual Studio (Windows-centric tools) is emphasized, while Linux equivalents or cross-platform alternatives are less prominent.
Recommendations
  • Add explicit Linux/macOS workflow examples, such as using sfctl from Bash or install.sh scripts.
  • Provide sample shell commands for parameter passing on Linux/macOS.
  • Clarify which tools are cross-platform and which are Windows-only.
  • Ensure that Linux/macOS users are guided on how to perform equivalent tasks without PowerShell or Visual Studio.
GitHub Create Pull Request
Service Fabric Networking patterns for Azure Service Fabric ...s/service-fabric/service-fabric-patterns-networking.md
Medium Priority View Details →
Scanned: 2026-02-19 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides only PowerShell-based deployment commands and examples, with no mention of Azure CLI or Bash equivalents. Windows-specific tools (PowerShell, RDP) are referenced exclusively or before alternatives, and even basic connectivity checks use Windows command prompt syntax. There are no Linux/macOS-specific instructions or examples, which creates friction for non-Windows users.
Recommendations
  • Add Azure CLI (az) command examples alongside PowerShell for template deployments and resource creation.
  • Include Bash shell examples for connectivity checks (e.g., using ping from Linux/macOS terminals).
  • Mention SSH as an alternative to RDP for accessing VMs, especially for Linux users.
  • Clarify that Service Fabric clusters can be managed from any OS, and provide cross-platform guidance where applicable.
  • Consider reorganizing examples so that cross-platform tools (Azure CLI, SSH) are presented before or alongside Windows-specific tools.
GitHub Create Pull Request
Service Fabric Fault Analysis Service overview .../service-fabric/service-fabric-testability-overview.md
Medium Priority View Details →
Scanned: 2026-02-19 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page for the Fault Analysis Service overview provides usage instructions primarily for C# and PowerShell, with explicit mention of the Service Fabric SDK and PowerShell module installation. There are no examples or instructions for Linux/macOS users, such as using CLI tools or REST APIs, nor is there mention of cross-platform alternatives. This creates friction for Linux/macOS users who may not have access to PowerShell or Windows-specific SDKs.
Recommendations
  • Add examples for using the Fault Analysis Service via Azure CLI or REST API, which are cross-platform.
  • Clarify whether the Fault Analysis Service APIs can be accessed from Linux/macOS environments and provide relevant instructions.
  • Mention any limitations or prerequisites for Linux/macOS users, and provide guidance for equivalent tooling.
  • If PowerShell is required, note the availability of PowerShell Core on Linux/macOS and provide installation instructions.
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-19 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page provides extensive PowerShell examples and references Windows-specific tools and extensions (e.g., Key Vault VM extension for Windows, S-channel, Windows certificate store concepts). While the core certificate management concepts are cross-platform and Azure-centric, the hands-on automation and scripting guidance is heavily Windows-focused, with PowerShell as the primary scripting language and Windows-specific mechanisms discussed in detail. There is minimal mention of Linux or cross-platform equivalents, and Windows patterns/tools are presented first and exclusively in critical automation sections.
Recommendations
  • Add equivalent Bash/CLI examples for certificate enrollment and management, especially for Key Vault operations.
  • Document how certificate provisioning and autorollover can be achieved on Linux-based Service Fabric clusters, including any differences in VM extensions or certificate store handling.
  • Clarify which steps or tools are Windows-only and provide guidance for Linux/macOS users where possible.
  • Reference or link to Linux-specific documentation for Service Fabric certificate management if available.
  • Where PowerShell is used, offer Azure CLI or REST API alternatives for cross-platform automation.
GitHub Create Pull Request
← Previous Page 47 of 99 Next →