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 201-225 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-03-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides examples for both Windows (ClusterManifest.xml, PowerShell) and cross-platform (ClusterConfig.json) configurations, but Windows-specific XML examples and PowerShell commands are presented first and more frequently. There are no explicit Linux/macOS command-line examples (e.g., Bash, CLI), and the XML configuration is shown only for WindowsServer clusters, potentially implying Windows as the default or primary platform. However, JSON-based configuration is also covered, which is applicable to Linux clusters and cross-platform scenarios.
Recommendations
  • Add explicit Linux cluster configuration examples (e.g., ClusterManifest.xml for Linux, if supported, or clarify if only JSON is used for Linux).
  • Include Azure CLI or Bash command examples for service creation and updates alongside PowerShell and C#.
  • Clarify in the configuration sections which examples are for Windows, which are for Linux, and which are cross-platform.
  • Ensure parity in example ordering (e.g., JSON before XML, CLI before PowerShell) to avoid implicit Windows-first bias.
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-03-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides PowerShell and C# examples for configuring Service Fabric move cost, but does not include equivalent Linux/macOS command-line examples (e.g., Azure CLI, Bash, or REST API). PowerShell is a Windows-centric tool, and its exclusive use in examples creates friction for Linux/macOS users. There is no mention of cross-platform tools or guidance for non-Windows environments.
Recommendations
  • Add Azure CLI examples for creating and updating Service Fabric services with move cost settings, as Azure CLI is cross-platform.
  • If REST APIs are available for these operations, provide REST or HTTP request examples.
  • Explicitly mention whether PowerShell Core (cross-platform) can be used, or clarify if only Windows PowerShell is supported.
  • Include notes or links for Linux/macOS users on how to perform equivalent operations.
  • Consider reordering examples so that cross-platform methods (CLI/REST) are shown before or alongside PowerShell.
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-03-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides PowerShell examples for configuring service sensitivity and maximum load, but does not offer equivalent Linux/macOS CLI examples (such as Bash or Azure CLI). PowerShell is presented as the primary scripting interface, which may create friction for Linux/macOS users. However, the core configuration can also be performed via manifest files (XML/JSON), which are cross-platform, and the C# API is platform-neutral. The bias is mostly in the scripting examples and ordering.
Recommendations
  • Add Bash or Azure CLI examples for creating and updating services with sensitivity and maximum load settings, if supported.
  • Clarify whether PowerShell examples are usable on Linux/macOS (via PowerShell Core), or provide alternative instructions for non-Windows environments.
  • Consider presenting cross-platform manifest (XML/JSON) examples first, followed by scripting/API examples.
  • Explicitly mention any limitations or parity gaps for Linux/macOS users in scripting or tooling.
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-03-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page provides security guidance for Azure Service Fabric clusters, referencing both Azure-hosted and standalone Windows clusters. However, it consistently presents Windows-specific instructions, tools, and links before Linux equivalents, and omits explicit Linux standalone cluster guidance. Certificate creation and security setup are described with Windows-centric tools and references, while Linux-specific instructions, examples, or links are missing or only briefly mentioned.
Recommendations
  • Add explicit guidance and links for securing standalone Linux Service Fabric clusters, including certificate setup and client authentication.
  • Provide Linux-focused examples for certificate creation and management (e.g., using OpenSSL or Linux certificate authorities), rather than only referencing Windows Server certificate services.
  • Clarify which instructions apply to Linux clusters and which are Windows-only, to avoid confusion.
  • Ensure parity in recommendations and tooling references for Linux users (e.g., mention Linux-native certificate management tools alongside Windows tools).
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-03-09 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 and configuration guides (e.g., 'service-fabric-cluster-upgrade-windows-server.md', 'service-fabric-cluster-config-upgrade-windows-server.md') and the Patch Orchestration Application for Windows. There are no explicit Linux or cross-platform instructions or links, and Windows terminology appears before any mention of Linux equivalents (if any exist).
Recommendations
  • Add or link to Linux-specific upgrade and configuration guides for Service Fabric standalone clusters, if supported.
  • Clarify in the introduction whether the standalone cluster upgrade process is Windows-only or cross-platform.
  • If Linux clusters are supported, provide equivalent examples, instructions, and references for Linux environments.
  • Mention Linux patch orchestration options or explicitly state if POA is Windows-only.
  • Ensure that references to configuration files and procedures are platform-neutral where possible.
GitHub Create Pull Request
Service Fabric Scalability of Service Fabric services .../service-fabric/service-fabric-concepts-scalability.md
Medium Priority View Details →
Scanned: 2026-03-09 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 patterns primarily using PowerShell and C#, with no equivalent Linux CLI or scripting examples. Windows tooling (PowerShell cmdlets) is mentioned exclusively and first, and Linux-specific guidance is missing. The only explicit Linux mention is in a platform comparison section, but Linux operational parity is not demonstrated in scaling scenarios.
Recommendations
  • Add equivalent Linux CLI examples (e.g., using sfctl or REST API) alongside PowerShell for service and application management tasks.
  • Mention Linux tooling and patterns (such as sfctl, bash scripts, or Azure CLI) wherever PowerShell is referenced.
  • Clarify which administrative actions are possible on Linux clusters and provide links to Linux-specific documentation.
  • Ensure that Linux users can follow scaling workflows without relying on Windows/PowerShell tools.
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-03-09 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 but does not offer equivalent Linux CLI (e.g., Bash, Azure CLI) examples. Windows tools (PowerShell, ApplicationManifest.xml via Visual Studio) are mentioned before Linux alternatives, and Linux limitations are noted without guidance or parity. There are no Linux-specific walkthroughs or examples for enabling or configuring DNS service, especially for containerized services.
Recommendations
  • Add Azure CLI or Bash examples for configuring DNS service and setting DNS names, especially for Linux clusters.
  • Include instructions for editing ARM templates and deploying from Linux environments (e.g., using az CLI).
  • Clarify how Linux users can set DNS names for services (e.g., via ARM templates, Docker Compose, or other methods).
  • Provide guidance for Linux users on verifying DNS settings and troubleshooting, including alternatives to Service Fabric Explorer if not available.
  • Explicitly state any workarounds or alternative approaches for Linux users where portal or PowerShell options are unavailable.
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-03-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page on Azure Service Fabric hosting activation and deactivation life cycle is largely platform-neutral in its conceptual explanations. However, the 'Next steps' section directs users to deployment instructions specifically in PowerShell, and the only linked example for downloading a ServicePackage references a PowerShell cmdlet. There are no Linux or cross-platform CLI examples or links, and PowerShell is mentioned before any Linux alternatives, which may create friction for Linux/macOS users.
Recommendations
  • Add links to equivalent Linux/macOS deployment instructions using Azure CLI or Service Fabric CLI (sfctl), where available.
  • Provide examples for downloading ServicePackages and deploying/removing applications using cross-platform tools (e.g., Azure CLI, sfctl) alongside PowerShell.
  • Clarify in the 'Next steps' section that PowerShell is one option, and offer alternatives for Linux/macOS users.
  • Ensure that conceptual sections reference platform-agnostic tools or note platform-specific differences where relevant.
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-03-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page references PowerShell as the primary example for interacting with Service Fabric clusters, and links to PowerShell-based deployment/removal guides. While REST and .NET are mentioned as alternatives, PowerShell is presented first and most prominently. There are no explicit Linux/macOS CLI or tooling examples (e.g., Azure CLI, Bash), nor is cross-platform parity discussed.
Recommendations
  • Add examples using Azure CLI or Bash scripts for retrieving cluster manifests and deploying applications, where possible.
  • Mention cross-platform tools and workflows (e.g., Azure CLI, REST API usage from Bash or Python) alongside PowerShell.
  • Clarify whether PowerShell Core (cross-platform) is supported, and provide instructions for Linux/macOS users.
  • Include links to Linux/macOS-specific documentation or note any limitations for non-Windows users.
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-03-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides a PowerShell-only example for reporting and evaluating application health in Service Fabric, without offering equivalent Linux/macOS CLI or REST API examples. While Service Fabric supports cross-platform management, the exclusive use of PowerShell in the example creates friction for Linux/macOS users.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl) for Linux/macOS users.
  • Include REST API sample requests for health reporting and querying.
  • Mention cross-platform tools and clarify PowerShell is one option among several.
  • Consider showing Linux/macOS examples before or alongside Windows/PowerShell examples.
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-03-09 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 model presents PowerShell examples exclusively, with no equivalent Linux CLI or cross-platform examples. Windows tooling (PowerShell) is mentioned first and most prominently for service creation and management, while REST API and .NET client alternatives are referenced but not demonstrated for Linux. There is no mention of Linux-specific tools or workflows, and no guidance for Linux/macOS users on how to perform equivalent tasks.
Recommendations
  • Add CLI examples using Azure CLI or Service Fabric CLI (sfctl), which are cross-platform and usable on Linux/macOS.
  • Include REST API usage examples with curl or similar tools to demonstrate Linux-friendly workflows.
  • Explicitly mention that PowerShell commands can be run on Linux/macOS using PowerShell Core, or provide alternatives if not possible.
  • Ensure that links to management documentation include Linux/macOS-compatible options.
  • Where PowerShell is referenced, add a note or section for Linux/macOS users describing equivalent steps.
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-03-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page provides container application manifest examples for Azure Service Fabric, but it is based on Windows Server 2016 Container Sample manifests and frequently references Windows-specific concepts (e.g., 'winver' for OS build, Windows file paths, and Windows container compatibility). There are no explicit Linux examples or Linux-specific guidance, and Windows terminology and tools are mentioned first or exclusively in several places.
Recommendations
  • Add equivalent Linux-based manifest examples, referencing Linux container samples and using Linux file paths.
  • Include guidance on obtaining OS build/version information on Linux (e.g., using 'uname' or '/etc/os-release').
  • Clarify which features and manifest settings are cross-platform and which are Windows-only.
  • Mention Linux-specific container image tags or compatibility considerations.
  • Provide links to Linux container sample repositories, if available.
GitHub Create Pull Request
Service Fabric Reliable services app manifest examples ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-manifest-example-reliable-services-app.md
Medium Priority View Details →
Scanned: 2026-03-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page for Service Fabric Reliable Services app manifest examples shows a moderate Windows bias. It references Windows-specific concepts (such as 'NetworkService', 'Administrators' group, and 'Setup.bat'), and mentions the ServiceFabric PowerShell module as a way to create service instances, without providing equivalent Linux/bash examples or guidance. The manifest examples use Windows-style user/group names and scripts, and do not clarify cross-platform differences or provide Linux-specific instructions. While Service Fabric supports Linux, the page does not demonstrate Linux parity in its examples or guidance.
Recommendations
  • Add Linux-specific examples, such as using bash scripts for SetupEntryPoint (e.g., 'Setup.sh' instead of 'Setup.bat'), and clarify how user/group principals map on Linux clusters.
  • Mention and provide examples for creating service instances using CLI tools available on Linux (e.g., Azure CLI or Service Fabric CLI), not just PowerShell.
  • Document any differences in account types, system groups, and security policies between Windows and Linux Service Fabric clusters.
  • Ensure that manifest examples and explanations are annotated to indicate which elements are Windows-only, Linux-only, or cross-platform.
  • Add a section or note explicitly addressing Linux/macOS users, including links to relevant documentation.
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-03-09 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 examples and references Windows-centric tools (e.g., RDP, Windows directory paths, PowerShell commands) throughout. There are no equivalent Linux/macOS CLI (Azure CLI) examples, and Windows patterns (such as RDP and PowerShell) are mentioned exclusively or before any Linux alternatives. This creates friction for Linux/macOS users, who must translate the instructions themselves.
Recommendations
  • Add Azure CLI (az) command examples alongside PowerShell for all deployment steps.
  • Mention SSH as a remote access alternative to RDP, and provide SSH examples for accessing VMs.
  • Use platform-neutral file paths or clarify that paths are examples.
  • Explicitly state that both Windows and Linux VM scale sets are supported, and note any platform-specific differences.
  • Provide sample ARM templates and deployment instructions for Linux-based Service Fabric clusters, if supported.
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-03-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation provides both Windows-specific (HTTP.sys) and cross-platform (Kestrel) guidance for ASP.NET Core in Service Fabric. However, Windows tools and patterns (HTTP.sys, Windows HTTP Server API, netsh) are discussed in detail, often before their Linux equivalents. HTTP.sys is clearly marked as Windows-only, but Linux-specific guidance is limited. Kestrel, the cross-platform option, is recommended for Linux, but Linux-specific instructions, troubleshooting, or examples are missing. Windows tools (like netsh) are referenced without Linux alternatives.
Recommendations
  • Add explicit Linux/macOS instructions for Service Fabric and ASP.NET Core integration, including any OS-specific configuration steps.
  • Provide troubleshooting guidance for Linux scenarios (e.g., firewall, port allocation, permissions) similar to the Windows/HTTP.sys coverage.
  • Include Linux/macOS-specific examples or notes where Windows tools (like netsh) are mentioned.
  • Clarify cross-platform support in each section, especially when recommending Kestrel for Linux.
  • Consider adding a comparison table or section summarizing Windows vs. Linux differences for Service Fabric Reliable Services with ASP.NET Core.
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-03-09 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 heavily references PowerShell cmdlets (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica, Get-ServiceFabricReplica) and provides examples and API links exclusively for PowerShell. There is no mention of Linux or cross-platform equivalents (such as CLI, REST, or SDK usage), nor are Linux-specific instructions or examples provided. The documentation assumes familiarity with Windows tooling and patterns, potentially creating friction for Linux/macOS users managing Service Fabric clusters.
Recommendations
  • Add examples and instructions for using the relevant Service Fabric APIs via cross-platform tools (e.g., Azure CLI, REST API, or .NET SDK) where possible.
  • Explicitly mention whether the PowerShell cmdlets are available on Linux/macOS (via PowerShell Core), or provide alternative commands for Linux users.
  • Clarify if the feature is supported on Linux-based Service Fabric clusters and, if so, provide Linux-specific guidance.
  • Include sample commands or code snippets for Linux environments, such as bash scripts or CLI usage.
  • Document any limitations or differences in feature support between Windows and Linux clusters.
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-03-09 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 detailed examples for reporting health in Service Fabric using PowerShell, with explicit PowerShell command snippets and references to Windows paths (e.g., PS C:\>). There are no equivalent Linux/bash examples or mentions of Linux-native tools for interacting with Service Fabric health reporting. The PowerShell examples are presented before REST API examples, and REST is only briefly mentioned without concrete sample payloads or curl commands. This creates friction for Linux/macOS users, who may not have access to PowerShell or Windows-specific tooling.
Recommendations
  • Add equivalent bash or shell examples for health reporting using REST APIs, including sample curl commands and payloads.
  • Clarify whether PowerShell commands can be run cross-platform (e.g., via PowerShell Core on Linux/macOS), and provide guidance for Linux/macOS users.
  • Present REST API examples with full request/response samples before or alongside PowerShell examples to ensure parity.
  • Mention any available CLI tools (e.g., Azure CLI, sfctl) that can be used on Linux/macOS for Service Fabric health reporting, with examples.
  • Explicitly state platform requirements for PowerShell examples, and provide alternatives for non-Windows environments.
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-03-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on Visual Studio workflows, referencing Windows-specific build and deployment actions (Build/Rebuild/F5/Ctrl+F5/Publish) and GUI interactions. There are no Linux/macOS equivalents or CLI-based examples provided. The only alternative mentioned is ARM or PowerShell cmdlets, but these are not explained or demonstrated in detail, and the primary guidance is for Windows/Visual Studio users.
Recommendations
  • Add explicit instructions or examples for Linux/macOS users, such as using Service Fabric CLI (sfctl) or Azure DevOps pipelines.
  • Clarify whether StartupServices.xml can be used or managed outside Visual Studio, and if not, state this limitation clearly.
  • Provide sample workflows or scripts for deploying Service Fabric applications on Linux, including how to handle service-level configuration.
  • Mention cross-platform tools and alternatives before or alongside Windows/Visual Studio-specific guidance.
GitHub Create Pull Request
Service Fabric Fault Analysis Service overview .../service-fabric/service-fabric-testability-overview.md
Medium Priority View Details →
Scanned: 2026-03-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides usage guidance for C# (via the Microsoft.ServiceFabric NuGet package) and PowerShell (via the ServiceFabric PowerShell module), but does not mention or provide examples for Linux/macOS command-line tools, Bash, or cross-platform CLI usage. There is no mention of Linux-specific tools or instructions, which may create friction for non-Windows users.
Recommendations
  • Add examples or instructions for using the Fault Analysis Service from Linux/macOS environments, such as via the Service Fabric CLI (sfctl), REST API, or Bash scripting.
  • Clarify whether the PowerShell and C# approaches are supported on Linux (e.g., PowerShell Core, .NET Core), or if they are Windows-only.
  • If the Fault Analysis Service is only accessible via Windows tools, explicitly state this limitation to set user expectations.
  • Provide links or references to cross-platform tools or documentation where available.
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-03-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page focuses on C# and .NET serialization, which is cross-platform, but the 'Next steps' section highlights Windows-centric tools (Visual Studio and PowerShell) for application upgrades, mentioning them before any Linux alternatives. There are no Linux CLI or cross-platform upgrade examples provided, and the recommended serializer is Data Contract, which is historically tied to .NET Framework and Windows, though now supported on .NET Core/.NET 5+.
Recommendations
  • Add examples or links for upgrading applications using Linux/macOS tools, such as Azure CLI or Service Fabric CLI (sfctl).
  • Mention cross-platform editors (e.g., VS Code) alongside Visual Studio.
  • Clarify that PowerShell Core is cross-platform, or provide Bash/CLI equivalents for upgrade steps.
  • Explicitly state that Data Contract serialization is supported on .NET Core/.NET 5+ for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Custom Image .../articles/service-fabric/how-to-deploy-custom-image.md
Medium Priority View Details →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page primarily references Windows custom images and provides PowerShell examples for role assignment, with Windows terminology and patterns appearing before Linux equivalents. While Linux custom images are briefly referenced, Windows is emphasized throughout, and Linux-specific examples or CLI commands are missing.
Recommendations
  • Provide explicit examples and instructions for deploying Linux custom images on Service Fabric Managed Clusters.
  • Include Azure CLI commands alongside PowerShell examples for role assignments and image management.
  • Clarify parity between Windows and Linux image support, including any limitations or differences.
  • Ensure Linux terminology and references are given equal prominence, not just as links.
GitHub Create Pull Request
Service Fabric Deploy and upgrade with Azure Resource Manager ...vice-fabric/service-fabric-application-arm-resource.md
Medium Priority View Details →
Scanned: 2026-03-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 PowerShell-only examples for removing Service Fabric resources and references PowerShell before cross-platform tools like the Service Fabric CLI. There are no CLI or REST API examples for Linux/macOS users, and PowerShell is presented as the primary automation method, which may create friction for non-Windows users.
Recommendations
  • Add equivalent Azure CLI and Service Fabric CLI examples for resource removal and management tasks, especially where PowerShell is currently the only example.
  • When referencing tools, mention cross-platform options (e.g., Service Fabric CLI, Azure CLI) before or alongside PowerShell.
  • Provide REST API examples with curl or HTTPie for tasks like deleting resources, to support users on all platforms.
  • Clarify in each section which tools are cross-platform and which are Windows-only.
GitHub Create Pull Request
Service Fabric Azure Service Fabric security best practices ...rvice-fabric/service-fabric-best-practices-security.md
Medium Priority View Details →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Windows and Linux examples for encrypting secrets, but Windows/PowerShell examples are often presented first and in greater detail. Windows-specific tools (e.g., Windows Defender, PowerShell commands) are mentioned exclusively, and Windows security baselines are discussed without Linux equivalents. Some sections, such as Windows Defender and security baselines, are Windows-only by nature, but overall, Linux parity could be improved in several areas.
Recommendations
  • Present Linux and Windows examples side-by-side or alternate which comes first to avoid implicit prioritization.
  • Where Windows-specific tools are discussed (e.g., Windows Defender, security baselines), add equivalent Linux guidance (e.g., recommend Linux security baselines, discuss common Linux antivirus solutions, or clarify if none are required).
  • Expand Linux-specific instructions for certificate management and secret encryption to match the detail provided for Windows.
  • Clarify when a feature or section is Windows-only to reduce confusion for Linux users.
  • Add links or references to Linux documentation for security best practices where possible.
GitHub Create Pull Request
Service Fabric Application upgrade: upgrade parameters ...abric/service-fabric-application-upgrade-parameters.md
Medium Priority View Details →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation prioritizes Windows-centric tools (PowerShell, Visual Studio) in both structure and detail. PowerShell and Visual Studio are discussed first and in greater depth, with parameter tables and examples tailored to these tools. Linux/macOS-friendly tools (SFCTL/CLI) are covered later and less prominently. There are no explicit Linux/macOS command-line examples or screenshots, and the CLI section is less detailed in terms of real-world usage patterns.
Recommendations
  • Reorganize the documentation to present SFCTL (Service Fabric CLI) on equal footing with PowerShell and Visual Studio, or consider leading with SFCTL as it is cross-platform.
  • Provide explicit SFCTL command-line examples for common upgrade scenarios, similar to the PowerShell examples.
  • Include Linux/macOS-specific notes or screenshots where appropriate, especially for CLI usage.
  • Clarify in parameter tables which options are available for each tool, and ensure parity in explanation and detail.
  • Consider adding a summary table at the top comparing PowerShell, Visual Studio, and SFCTL approaches, with links to detailed sections.
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-03-08 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 guidance on managing certificates in Azure Service Fabric clusters, with a strong focus on Azure-native mechanisms and Windows-centric tooling. PowerShell is the only scripting example provided for certificate enrollment, and references to the Key Vault VM extension are explicitly for Windows. There are no Linux-specific examples, nor is there mention of Linux-compatible provisioning agents or cross-platform scripting alternatives.
Recommendations
  • Provide equivalent CLI or Bash examples for certificate enrollment and management, such as using Azure CLI or REST API calls, in addition to PowerShell.
  • Clarify whether the Key Vault VM extension is available for Linux VMs, and if not, mention Linux-compatible alternatives (e.g., Key Vault secrets extension for Linux, or custom scripts).
  • Explicitly state any platform limitations for provisioning agents and extensions, and provide guidance for Linux-based Service Fabric clusters if supported.
  • Where JSON ARM templates are used, add notes or examples highlighting any OS-specific settings or differences.
  • In troubleshooting and FAQ sections, include Linux/macOS command-line examples where possible.
GitHub Create Pull Request
← Previous Page 9 of 99 Next →