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 1551-1575 of 2475 flagged pages
Service Fabric Describe a cluster by using Cluster Resource Manager ...ce-fabric-cluster-resource-manager-cluster-description.md
Medium Priority View Details →
Scanned: 2026-02-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Windows and cross-platform (JSON) configuration examples for Service Fabric clusters, but Windows-specific XML (ClusterManifest.xml) and PowerShell examples are presented first or exclusively in several sections. PowerShell is the only CLI example shown for service creation and updates, with no Linux/macOS CLI (e.g., Bash, Azure CLI) equivalents. The XML configuration is specifically labeled as 'WindowsServer', and there is no mention of Linux-based Service Fabric clusters or their configuration patterns.
Recommendations
  • Add explicit examples and guidance for Linux-based Service Fabric clusters, including configuration files and supported OS types.
  • Provide equivalent Bash or Azure CLI examples for service creation and updates, alongside PowerShell.
  • Clarify whether the XML configuration applies only to Windows clusters and provide Linux configuration alternatives if supported.
  • Ensure that cross-platform JSON examples are given equal prominence and context as Windows XML examples.
  • Mention any limitations or differences for Linux/macOS users, if applicable.
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 →
Scanned: 2026-02-13 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 PowerShell examples for configuring move cost, but does not include equivalent Linux/macOS CLI (e.g., Bash, Azure CLI) examples. PowerShell is presented before C# in all cases, and there is no mention of Linux-native tools or cross-platform command-line options for Service Fabric management. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other tooling.
Recommendations
  • Add Bash or Azure CLI examples for creating and updating Service Fabric services and move cost settings.
  • Mention cross-platform management options (such as Azure CLI, REST API, or Service Fabric CLI) where available.
  • Clarify whether PowerShell commands are supported on Linux/macOS (via PowerShell Core), and provide guidance for users on those platforms.
  • Consider presenting cross-platform or neutral examples (e.g., Azure CLI, REST API) before Windows-specific ones.
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 →
Scanned: 2026-02-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides detailed PowerShell examples for managing node tags and service requirements, but does not include equivalent CLI or scripting examples for Linux/macOS users. PowerShell is a Windows-centric tool, and its exclusive use here creates friction for users managing Service Fabric clusters on Linux. No Linux-native commands (such as Bash, Azure CLI, or REST API examples) are provided, despite REST APIs being mentioned.
Recommendations
  • Add examples using Azure CLI or Bash scripts for managing node tags and service requirements.
  • Provide REST API sample requests for adding/removing node tags and configuring service tag requirements, as REST APIs are mentioned as an interface.
  • Clarify whether PowerShell examples are compatible with PowerShell Core on Linux/macOS, or provide alternative instructions if not.
  • Ensure that Linux/macOS users can complete all documented tasks without relying on Windows 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 →
Scanned: 2026-02-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides detailed PowerShell examples for configuring auto scaling policies, but does not include equivalent Linux CLI or cross-platform examples (such as Azure CLI, REST API, or bash scripting). The PowerShell cmdlets and .NET/C# APIs shown are primarily Windows-centric, and there is no guidance for Linux-native Service Fabric management tools or workflows. This creates friction for Linux users, especially as Service Fabric supports Linux clusters and container workloads.
Recommendations
  • Add equivalent examples using Azure CLI, REST API, or Service Fabric CLI (sfctl), which are cross-platform and work on Linux/macOS.
  • Clearly indicate which management approaches are Windows-only (e.g., PowerShell cmdlets) and provide Linux alternatives where possible.
  • Include bash or shell script snippets for common operations, or reference official Linux management documentation.
  • Explicitly state any limitations or differences in auto scaling support between Windows and Linux clusters, especially where features or tooling diverge.
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 →
Scanned: 2026-02-13 00:00
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 only PowerShell is used for CLI examples. There are no Linux/macOS CLI equivalents (such as Azure CLI or REST API), and PowerShell is presented before any mention of alternative tools. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer cross-platform tools.
Recommendations
  • Add Azure CLI examples for all PowerShell commands shown, as Azure CLI is cross-platform and widely used.
  • Mention REST API options where applicable, especially for service creation and metric management.
  • Clearly indicate which commands are Windows-only and provide guidance for Linux/macOS users.
  • Consider showing Azure CLI or REST API examples before PowerShell, or at least in parallel, to avoid Windows-first bias.
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 →
Scanned: 2026-02-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides extensive PowerShell examples for configuring service sensitivity and maximum load in Azure Service Fabric, but does not offer equivalent CLI or scripting examples for Linux/macOS users. The use of PowerShell and references to Windows tooling may create friction for users managing Service Fabric clusters on non-Windows platforms.
Recommendations
  • Add Azure CLI or REST API examples for configuring service sensitivity and maximum load, where possible.
  • Clarify whether PowerShell commands can be run cross-platform (e.g., with PowerShell Core) or if they are Windows-only.
  • Provide guidance for Linux/macOS users on how to achieve the same configuration tasks, including any limitations.
  • Explicitly mention if certain operations are only supported via PowerShell or Windows tools, and suggest alternatives if available.
GitHub Create Pull Request
Service Fabric Secure an Azure Service Fabric cluster ...cles/service-fabric/service-fabric-cluster-security.md
Medium Priority View Details →
Scanned: 2026-02-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page for securing an Azure Service Fabric cluster presents security scenarios and technologies applicable to both Azure-hosted clusters and standalone Windows clusters. However, it repeatedly references Windows Server clusters and provides links and guidance specifically for Windows environments, with no equivalent examples or links for standalone Linux clusters. Windows security (Kerberos) is discussed, but Linux authentication options are not mentioned. Certificate creation recommendations focus on Windows tools and services, with no Linux tooling or process described. The concept of Linux clusters is acknowledged, but practical guidance is missing.
Recommendations
  • Add explicit guidance and links for securing standalone Linux Service Fabric clusters, including certificate setup and authentication options.
  • Provide Linux-specific examples for certificate creation and management (e.g., using OpenSSL, Linux certificate stores).
  • Mention Linux authentication patterns (e.g., local user accounts, integration with Linux-based identity providers) where relevant.
  • Ensure parity in references and links for both Windows and Linux standalone cluster scenarios.
  • Clarify which features or recommendations apply to both OS types, and which are Windows-specific.
GitHub Create Pull Request
Service Fabric Azure Service Fabric standalone cluster scaling ...ce-fabric/service-fabric-cluster-scaling-standalone.md
Medium Priority View Details →
Scanned: 2026-02-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page for scaling Azure Service Fabric standalone clusters demonstrates a Windows bias. It references PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) without providing equivalent Linux or cross-platform CLI examples. The linked 'scale a standalone cluster' documentation is specifically for Windows Server, and there is no mention of Linux-based Service Fabric standalone clusters or instructions for scaling them. This creates friction for Linux users who may wish to deploy or manage Service Fabric clusters outside of Windows environments.
Recommendations
  • Clarify whether Service Fabric standalone clusters are supported on Linux. If so, provide Linux-specific instructions and examples for scaling operations.
  • Include cross-platform CLI examples (such as Service Fabric CLI or REST API usage) alongside PowerShell commands.
  • If standalone clusters are Windows-only, explicitly state this in the documentation to avoid confusion for Linux users.
  • Reference or link to any Linux-specific documentation if available.
GitHub Create Pull Request
Service Fabric Azure Service Fabric DNS service ...n/articles/service-fabric/service-fabric-dnsservice.md
Medium Priority View Details →
Scanned: 2026-02-13 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 setting DNS names, references ApplicationManifest.xml (a Windows-centric deployment artifact), and describes enabling DNS service via the Azure portal (Windows clusters only), but does not offer equivalent Linux CLI or deployment examples. Linux support is mentioned as limited, but no Linux-specific guidance or parity in examples is provided.
Recommendations
  • Add Linux-specific examples for setting DNS names, such as using Azure CLI or ARM templates for containerized services.
  • Clarify Linux deployment workflows, including how to enable DNS service for Linux clusters (since portal is not supported).
  • Provide sample commands or scripts for Linux users (e.g., Bash, Azure CLI) alongside PowerShell examples.
  • Explicitly note differences in ApplicationManifest.xml usage for Linux clusters, or provide Docker Compose examples where relevant.
  • Highlight limitations for Linux clusters more prominently and link to Linux-specific 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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation provides a detailed conceptual overview of Service Fabric health monitoring, but the only practical example for reporting and evaluating application health uses PowerShell cmdlets, which are Windows-specific. No equivalent Linux or cross-platform CLI (such as Azure CLI or REST API) example is given, and PowerShell is presented as the default method for interacting with Service Fabric health reporting. This creates friction for Linux/macOS users, as they must seek out alternative methods not documented here.
Recommendations
  • Add examples using Azure CLI or REST API for reporting and querying health, which are cross-platform and supported on Linux/macOS.
  • Explicitly mention that PowerShell is Windows-specific and provide links or guidance for Linux/macOS users.
  • Consider including sample code using the Service Fabric SDK in languages like Python or .NET Core, which are cross-platform.
  • Reorder or supplement the 'Example: Report and evaluate application health' section to show Linux-compatible methods first or alongside PowerShell.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page on Azure Service Fabric image store connection strings shows a moderate Windows/PowerShell bias. It references PowerShell as the primary way to retrieve the cluster manifest and links to a PowerShell-based deployment guide as the next step. There is no mention of Linux/macOS CLI equivalents (such as Azure CLI or Bash scripts), and Windows/PowerShell tools are presented first and most prominently.
Recommendations
  • Add examples or references for retrieving the cluster manifest using Azure CLI or Bash scripts, especially for Linux/macOS users.
  • Include links to cross-platform tools or documentation (e.g., Azure CLI, REST API usage with curl) alongside or before PowerShell references.
  • Clarify whether the described procedures and tools are available and supported on Linux/macOS, and provide parity where possible.
  • Consider adding a 'Platform support' note to indicate that Service Fabric management can be performed from non-Windows environments, if applicable.
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-13 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 examples and tooling references that prioritize Windows/PowerShell workflows (e.g., PowerShell cmdlets, Visual Studio, Deploy-FabricApplication.ps1) and mentions them before Linux equivalents. While sfctl and Jenkins are referenced, there are no concrete Linux/macOS command examples, and the overall guidance is oriented toward Windows-centric tools and patterns.
Recommendations
  • Add explicit Linux/macOS examples for application creation and parameter passing, such as full sfctl command lines and shell script snippets.
  • Include step-by-step instructions for using Jenkins or other cross-platform CI/CD tools, not just mentioning them.
  • Balance the order of examples so Linux/macOS and Windows workflows are presented equally.
  • Reference cross-platform editors and deployment tools 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-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page references Windows-specific upgrade guides and tools (e.g., Patch Orchestration Application for Windows) and links primarily to Windows Server-focused upgrade/configuration articles. There is no mention of Linux-specific upgrade procedures, tools, or configuration guides, nor are Linux examples provided. This creates friction for Linux cluster administrators seeking parity.
Recommendations
  • Add links and references to Linux-specific Service Fabric standalone cluster upgrade guides, if available.
  • Provide examples and instructions for upgrading and configuring Service Fabric clusters running on Linux, including patch orchestration and configuration management.
  • Clarify in the documentation when a feature or tool is Windows-only, and offer Linux alternatives or workarounds where possible.
  • Ensure that both Windows and Linux procedures are covered in parallel, or explicitly state platform limitations.
GitHub Create Pull Request
Service Fabric Azure Service Fabric application resource model ...ervice-fabric/service-fabric-concept-resource-model.md
Medium Priority View Details →
Scanned: 2026-02-13 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 the Azure Service Fabric application resource model demonstrates a notable Windows bias. All deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) without mention of Azure CLI or other cross-platform tools. Application packaging instructions reference Visual Studio, a Windows-centric IDE, and do not provide alternatives for Linux/macOS users. There are no Linux/macOS-specific examples or guidance, and Windows tools and patterns are presented exclusively and first.
Recommendations
  • Add Azure CLI examples for deployment and deletion tasks alongside PowerShell examples.
  • Provide instructions for packaging Service Fabric applications using cross-platform tools (e.g., dotnet CLI, SF SDK for Linux/macOS).
  • Mention and link to cross-platform IDEs or command-line alternatives for application packaging.
  • Clearly indicate which steps are Windows-only and offer Linux/macOS equivalents where possible.
  • Ensure screenshots and walkthroughs are not exclusively tied to Windows/Visual Studio.
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-13 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 and administrative instructions primarily using PowerShell, which is a Windows-centric tool. There are no equivalent Linux CLI or script examples (e.g., Bash, Azure CLI) for scaling Service Fabric services. Windows/PowerShell commands are presented first and exclusively, which may create friction for Linux users. The only explicit Linux mention is in the 'Choosing a platform' section, which discusses implementation differences but does not provide Linux-specific operational guidance.
Recommendations
  • Add equivalent Linux/Bash/Azure CLI examples for scaling operations (e.g., creating/removing services, updating instance counts).
  • Reference Linux tooling (such as Azure CLI or REST API) alongside PowerShell, not just in the 'Choosing a platform' section.
  • Ensure administrative instructions are platform-neutral or provide parallel guidance for both Windows and Linux users.
  • Consider linking to Linux-specific Service Fabric documentation or guides where appropriate.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation covers both Windows and Linux usage of Azure Service Fabric, but exhibits several Windows biases. Windows-specific tools (PowerShell, Visual Studio) and terminology (Windows service, FabricHost.exe) are mentioned first or exclusively in key sections. Examples and instructions often default to Windows, with Linux equivalents referenced later or omitted. Standalone cluster creation and upgrades are described only for Windows, with Linux support explicitly stated as unavailable. Some CLI and REST API options are mentioned, but PowerShell is emphasized. Visual Studio is referenced for cluster creation, but no Linux-native tooling is suggested.
Recommendations
  • Provide Linux-specific examples and instructions alongside Windows ones, especially for cluster creation, upgrades, and management.
  • Mention Linux CLI tools (e.g., sfctl) and Bash scripts before or alongside PowerShell, and clarify their parity.
  • Include references to Linux-native development environments (e.g., VS Code, JetBrains Rider) where Visual Studio is mentioned.
  • Clearly indicate which features are Windows-only and which are cross-platform, linking to the Linux/Windows differences page.
  • Add guidance for Linux users on monitoring, diagnostics, and health reporting using Linux tools.
  • Update 'Next steps' to include Linux cluster creation and management, or clarify Linux limitations.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Events ...es/service-fabric/service-fabric-diagnostics-events.md
Medium Priority View Details →
Scanned: 2026-02-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page describes Service Fabric event logging primarily in terms of Windows-centric tools and patterns, such as ETW/Windows Event logs and the Windows Azure diagnostics agent. There is no mention of Linux equivalents or guidance for accessing events on Linux-based Service Fabric clusters, nor are Linux-specific monitoring tools or log channels referenced. Windows tools and terminology are presented first and exclusively.
Recommendations
  • Add explicit guidance for accessing Service Fabric events on Linux clusters, including supported log channels (e.g., stdout, syslog, Azure Monitor integration for Linux).
  • Mention Linux-compatible diagnostics agents or methods, such as Azure Monitor agent or Log Analytics agent for Linux.
  • Provide examples or links for querying and visualizing events from Linux clusters, including any differences in configuration or event formats.
  • Clarify which features or event channels are Windows-only and which are cross-platform.
  • Ensure parity in documentation structure by presenting Linux and Windows approaches side-by-side where applicable.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation references the Service Fabric SDK schema location using a Windows file path and does not mention Linux or cross-platform equivalents. The only explicit tooling path given is Windows-specific, and there is no mention of Linux/Mac installation or usage patterns. However, the overall guidance is mostly platform-agnostic, and the examples reference general concepts and cross-platform languages (e.g., Node.js, Java, C++).
Recommendations
  • Add information about the location of Service Fabric SDK files on Linux/macOS, if available.
  • Clarify whether the packaging and deployment process is supported and documented for Linux/macOS, and provide equivalent instructions or links.
  • When referencing file paths or tools, include both Windows and Linux/macOS examples, or note platform differences.
  • Explicitly state if certain steps or tools are Windows-only, and provide alternatives or workarounds for Linux/macOS users where possible.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides PowerShell examples for creating services with the Exclusive Process model and references PowerShell cmdlets for querying and managing Service Fabric services. PowerShell is a Windows-centric tool, and no equivalent Linux CLI (such as sfctl) or bash examples are provided. Additionally, PowerShell is mentioned before REST and FabricClient options, reinforcing Windows-first patterns.
Recommendations
  • Add examples using sfctl (Service Fabric CLI), which is cross-platform and commonly used on Linux/macOS, for service creation and management.
  • Include bash or shell script examples where applicable, especially for querying and managing deployed service packages.
  • Mention Linux/macOS-compatible tools and workflows alongside PowerShell, and clarify any platform limitations.
  • Reorder sections to avoid always listing Windows tools first, or explicitly state tool parity.
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-13 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 a moderate Windows bias. The examples and explanations are based on the Windows Server 2016 Container Sample, and Windows-specific tools and patterns (such as 'winver' for OS build detection and Windows-style paths like 'c:\VolumeTest\Data') are referenced first or exclusively. There is limited mention of Linux equivalents, and no Linux-specific manifest examples or guidance are provided, even though Service Fabric supports Linux containers. The certificate handling section does mention both PFX (Windows) and PEM (Linux) formats, but overall, Linux users may find it difficult to adapt these examples without additional guidance.
Recommendations
  • Provide equivalent Linux-based manifest examples, including Linux-style paths and container images.
  • Include instructions for determining OS build/version on Linux (e.g., using 'uname -a' or '/etc/os-release'), alongside the Windows 'winver' command.
  • Clarify which manifest settings or features are cross-platform and which are Windows-only.
  • Reference both Windows and Linux sample repositories, if available.
  • Add notes or callouts where behavior differs between Windows and Linux containers (e.g., volume mounting, certificate formats, isolation modes).
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page heavily references PowerShell cmdlets (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica, Get-ServiceFabricReplica) and administrative APIs, but does not provide equivalent examples or instructions for Linux/macOS users. There is no mention of Linux CLI tools, REST APIs, or cross-platform SDK usage for replica management. The focus on PowerShell and Windows-centric tooling creates friction for non-Windows users.
Recommendations
  • Add examples using Service Fabric CLI (sfctl), which is cross-platform and available on Linux/macOS.
  • Document how to use REST APIs or FabricClient SDKs in cross-platform languages (e.g., Python, Java) to perform replica soft delete and restore operations.
  • Clarify whether the PowerShell cmdlets are available on Linux (via PowerShell Core), and if not, provide alternative instructions.
  • Include sample commands and screenshots for Linux/macOS environments where applicable.
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-13 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 notable Windows bias by providing extensive PowerShell examples and referencing Windows command-line patterns. There are no equivalent Linux/bash examples, nor is there guidance for Linux users on how to perform health reporting tasks using cross-platform tools. PowerShell is presented as the primary CLI method, with no mention of Linux-native alternatives or Azure CLI. This creates friction for Linux/macOS users, especially those running Service Fabric clusters on Linux or developing cross-platform applications.
Recommendations
  • Add bash or Azure CLI examples for health reporting, especially for REST calls and cluster interactions.
  • Explicitly mention that PowerShell commands are for Windows, and provide guidance for Linux users (e.g., using curl for REST, or Azure CLI where possible).
  • Include notes or sections on how to perform equivalent tasks on Linux/macOS clusters, including any limitations or differences.
  • Consider referencing cross-platform scripting options, such as PowerShell Core (pwsh), if applicable, and clarify compatibility.
  • Ensure REST examples include sample curl commands for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Fault Analysis Service overview .../service-fabric/service-fabric-testability-overview.md
Medium Priority View Details →
Scanned: 2026-02-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides explicit instructions for using the Fault Analysis Service via PowerShell and C#, but does not mention or provide examples for Linux/macOS users (e.g., Bash, CLI, or REST API usage). The PowerShell module is highlighted as the primary scripting interface, and there is no guidance for equivalent Linux tooling or cross-platform approaches.
Recommendations
  • Add examples or references for using the Fault Analysis Service via Azure CLI, Bash, or REST API, if available.
  • Clarify whether PowerShell Core (cross-platform) is supported, and provide instructions for Linux/macOS users if so.
  • Mention any limitations or alternative approaches for non-Windows users.
  • Ensure that code and scripting examples are provided for both Windows and Linux environments, or explicitly state if only Windows is supported.
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-13 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 oriented toward Windows environments, specifically Visual Studio workflows. All deployment and configuration examples reference Visual Studio actions (Build/Rebuild/F5/Ctrl+F5/Publish), which are Windows-only. The only alternative deployment methods mentioned are ARM templates and PowerShell cmdlets, with no Linux/macOS equivalents or CLI examples. There are no instructions or examples for Linux/macOS users, nor any mention of cross-platform tooling or workflows.
Recommendations
  • Add explicit guidance for Linux/macOS users, including how to manage service configuration and deployment without Visual Studio.
  • Provide Azure CLI or cross-platform PowerShell Core examples for deploying Service Fabric applications and configuring StartupServices.xml.
  • Clarify which features are Visual Studio/Windows-only and offer alternative workflows for other platforms.
  • Mention any limitations or supported scenarios for Linux/macOS users up front, so they can determine applicability.
  • Include references to Service Fabric SDK usage on Linux/macOS, if supported, and how StartupServices.xml fits into those workflows.
GitHub Create Pull Request
Service Fabric Application upgrade: upgrade parameters ...abric/service-fabric-application-upgrade-parameters.md
Medium Priority View Details →
Scanned: 2026-02-12 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 parameter tables, with detailed examples and descriptions for these tools. Linux-compatible tools (SFCTL/CLI) are covered later and less thoroughly, with fewer concrete examples and less guidance. No explicit Linux/macOS command examples are provided for parameter usage, and Windows tools are consistently mentioned first.
Recommendations
  • Add explicit Linux/macOS command examples using SFCTL for each parameter, similar to the PowerShell examples.
  • Reorganize the page to present all upgrade methods (PowerShell, Visual Studio, SFCTL, REST) equally, or group by platform rather than tool.
  • Include a comparison table showing parameter mapping between PowerShell and SFCTL to help Linux users.
  • Ensure that Linux CLI options are described with the same level of detail and examples as Windows tools.
  • Consider mentioning cross-platform tools (e.g., Azure CLI, REST API) earlier in the article.
GitHub Create Pull Request
← Previous Page 63 of 99 Next →