Service Fabric

407
Total Pages
336
Linux-Friendly Pages
71
Pages with Bias
17.4%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

1305 issues found
Showing 151-175 of 1305 flagged pages
Service Fabric Azure Service Fabric standalone cluster scaling ...ce-fabric/service-fabric-cluster-scaling-standalone.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 on scaling Azure Service Fabric standalone clusters exhibits Windows bias by exclusively referencing PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) and linking to Windows Server-specific guides. There are no Linux-specific examples, tools, or instructions, and the terminology and guidance assume a Windows environment, despite standalone clusters being theoretically cross-platform.
Recommendations
  • Add equivalent Linux instructions, including examples using Bash, CLI, or relevant Linux tools for cluster manifest querying and configuration upgrades.
  • Clarify whether standalone Service Fabric clusters can be managed on Linux, and if so, provide parity in documentation for Linux users.
  • If PowerShell is required on Linux, explicitly state this and provide installation guidance.
  • Link to or create Linux-specific guides for scaling standalone clusters, if supported.
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-19 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 examples, tools, or links to Linux-specific upgrade/configuration documentation. The page does not clarify whether Linux clusters are supported or provide guidance for Linux users.
Recommendations
  • Add explicit guidance or links for upgrading Service Fabric standalone clusters running on Linux, if supported.
  • Provide Linux-specific examples or documentation references alongside Windows ones.
  • Clarify in the introduction whether the guidance applies to both Windows and Linux clusters, or is Windows-only.
  • Mention Linux equivalents for patch orchestration or cluster configuration, if available.
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-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 PowerShell examples for configuring Service Fabric service move cost, but does not offer equivalent Linux CLI or bash examples. PowerShell is primarily a Windows tool, and its exclusive use in examples creates friction for Linux/macOS users. Additionally, PowerShell examples are presented before C# code, reinforcing a Windows-first bias. No Linux-native tools or commands (such as Azure CLI or REST API) are mentioned for these operations.
Recommendations
  • Add equivalent Azure CLI or REST API examples for configuring and updating move cost, which are cross-platform and usable from Linux/macOS.
  • Explicitly mention whether PowerShell commands can be run on Linux/macOS (via PowerShell Core), or clarify if they are Windows-only.
  • Consider providing bash or shell script examples for common operations, or link to relevant cross-platform tooling.
  • Reorder examples so that cross-platform methods (Azure CLI, REST API) are shown before or alongside PowerShell.
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-19 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 examples for managing node tags and service requirements, but does not offer equivalent Linux/macOS command-line examples (such as Azure CLI, Bash, or REST API usage). PowerShell is primarily a Windows tool, and its prominence creates friction for Linux/macOS users. The documentation also references PowerShell before C# APIs and omits mention of cross-platform tools or workflows.
Recommendations
  • Add examples using Azure CLI or REST API for managing node tags and service requirements, as these are cross-platform and accessible to Linux/macOS users.
  • Explicitly state whether PowerShell commands are supported on Linux/macOS (via PowerShell Core), and provide guidance if so.
  • Consider including Bash or shell script examples where appropriate, or reference relevant Service Fabric CLI tools if available.
  • Reorder examples so that cross-platform tools (REST API, CLI) are presented 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-02-19 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 Linux/macOS CLI examples (such as Bash, sfctl, or REST API). The PowerShell-centric approach and references to Windows tools may create friction for Linux users, even though Service Fabric supports cross-platform management.
Recommendations
  • Add equivalent examples using sfctl (Service Fabric CLI) for Linux/macOS users, especially for service creation and updates.
  • Include REST API examples for configuring sensitivity and maximum load, which are platform-agnostic.
  • Explicitly mention cross-platform support and clarify which tools are available on each OS.
  • Reorder sections so that cross-platform or platform-agnostic methods (e.g., Application Manifest, REST API) are presented before Windows-specific tools like PowerShell.
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-19 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 consistently presents Windows-specific guidance and links before Linux equivalents, and omits explicit instructions or links for securing standalone Linux clusters. While the concept of certificate-based security is described as applicable to both Windows and Linux, practical setup instructions and references are only provided for Windows standalone clusters, leaving Linux users without clear guidance.
Recommendations
  • Add explicit instructions and links for securing standalone Linux Service Fabric clusters, including certificate setup and client authentication.
  • Ensure that examples and guidance for both Windows and Linux are presented in parallel, or clarify when features are Windows-only.
  • Include references to Linux-compatible certificate management tools and patterns (e.g., OpenSSL, Linux certificate stores) where relevant.
  • If Linux standalone clusters are not supported, state this clearly to avoid confusion.
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-19 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 Azure Service Fabric Events primarily references Windows-centric tools and patterns, such as ETW/Windows Event logs and the Windows Azure diagnostics agent, without mentioning Linux equivalents or providing Linux-specific guidance. The examples and instructions focus on Windows mechanisms for event access and monitoring, and Windows tools are mentioned first and exclusively.
Recommendations
  • Add explicit guidance for accessing Service Fabric events on Linux clusters, including supported logging mechanisms (e.g., stdout, syslog, Azure Monitor integration for Linux).
  • Mention Linux-compatible diagnostics agents or methods, such as Azure Monitor agent for Linux, and clarify any differences in event collection and visualization.
  • Provide examples or links for querying and analyzing Service Fabric events from Linux environments, including REST API usage and integration with cross-platform tools.
  • Clearly state any limitations or differences in event access between Windows and Linux clusters, if applicable.
GitHub Create Pull Request
Service Fabric Upgrading Azure Service Fabric clusters ...icles/service-fabric/service-fabric-cluster-upgrade.md
Medium Priority View Details →
Scanned: 2026-02-19 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation provides general guidance for upgrading Azure Service Fabric clusters, but there are subtle signs of Windows bias. For example, in the 'Upgrading OS images for cluster nodes' section, the only linked guidance is for patching Windows operating systems, with no mention of Linux node patching. Additionally, PowerShell is mentioned as a management tool alongside Azure CLI, but Linux-specific tools or workflows are not highlighted. Windows-related documentation is referenced first or exclusively in some sections, potentially creating friction for Linux users.
Recommendations
  • Add explicit guidance or links for patching/upgrading Linux node OS images in Service Fabric clusters, if supported.
  • Ensure examples for cluster management (certificates, ports, etc.) include both PowerShell and Bash/Azure CLI commands, or clarify parity.
  • Mention Linux support and limitations where relevant, especially in sections referencing Windows-specific features or tools.
  • Provide links to Linux-specific Service Fabric documentation where available.
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-19 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page for the Azure Service Fabric application resource model demonstrates notable Windows bias. All deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) without any Azure CLI or Bash equivalents. The packaging step relies on Visual Studio, a Windows-centric tool, and the directory structure uses Windows path conventions. There are no Linux/macOS-specific instructions or alternatives provided, and Windows tools are referenced before any cross-platform options.
Recommendations
  • Add Azure CLI examples for deployment and deletion alongside PowerShell cmdlets.
  • Provide guidance for packaging applications using cross-platform tools (e.g., dotnet CLI, SF SDK, or manual zip commands) instead of only Visual Studio.
  • Include Linux/macOS path conventions and instructions where relevant.
  • Mention that the Azure portal and Resource Manager templates are platform-agnostic, and clarify any steps that are Windows-only.
  • Where screenshots or instructions reference Windows UI/tools, add notes or alternatives for Linux/macOS users.
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-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 code examples and administrative instructions primarily using PowerShell and C#, with no equivalent Linux CLI or scripting examples. Windows tools (PowerShell cmdlets) are referenced exclusively for cluster and service management, and Linux alternatives are not mentioned or demonstrated. The 'Choosing a platform' section does acknowledge Linux, but only in the context of implementation differences, not in operational guidance.
Recommendations
  • Add equivalent Linux CLI examples (e.g., using Azure CLI, Bash scripts, or Service Fabric CLI) alongside PowerShell examples.
  • Reference Linux management tools and workflows where PowerShell cmdlets are mentioned.
  • Explicitly state when a feature or example is Windows-only, and provide Linux alternatives or note limitations.
  • Ensure Linux operational guidance is present for tasks like scaling services, creating/removing instances, and cluster management.
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-19 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 technology. However, there are several areas where Windows-specific tools, services, and patterns are mentioned first or exclusively, such as references to Windows services (FabricHost.exe), PowerShell cmdlets, and standalone cluster creation only for Windows. Linux equivalents are sometimes missing or mentioned later. This creates friction for Linux users, especially in cluster management and lifecycle operations.
Recommendations
  • Ensure that CLI (sfctl) examples and references are given equal prominence to PowerShell, especially in lifecycle and health monitoring sections.
  • Add explicit Linux examples and instructions where only Windows or PowerShell are mentioned, such as cluster creation, management, and scaling.
  • Clarify which features are Windows-only and which are cross-platform, ideally with side-by-side comparison tables.
  • Provide links to Linux-specific documentation and tools in 'Next steps' and throughout the page.
  • Mention Linux container support and Java programming model earlier, alongside Windows/.NET references.
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-19 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 PowerShell-only example for reporting and evaluating application health, with no equivalent example for Linux or cross-platform tools (e.g., Bash, REST, or CLI). PowerShell cmdlets are mentioned before REST APIs, and no Linux-specific guidance or parity is provided for common health reporting tasks.
Recommendations
  • Add equivalent examples using cross-platform tools such as Azure CLI, Bash scripts, or REST API calls for health reporting and querying.
  • Explicitly mention how Linux/macOS users can perform the same health reporting and querying tasks, referencing any required Service Fabric CLI or REST endpoints.
  • Reorder or supplement the 'Health reporting' section to present cross-platform methods (e.g., REST, CLI) before or alongside PowerShell examples.
  • Clarify in the example section that PowerShell is one option, and provide links or code snippets for Linux/macOS users.
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-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 PowerShell examples for setting DNS names, references ApplicationManifest.xml (a Windows-centric deployment artifact), and describes portal-based configuration (which is not supported for Linux clusters). While Linux support is mentioned, Linux-specific instructions, examples, and parity for non-containerized workloads are missing. Windows tools and patterns (PowerShell, Visual Studio, ApplicationManifest.xml) are presented first and exclusively, with no equivalent Linux CLI or YAML-based examples.
Recommendations
  • Add Linux-specific instructions for enabling DNS service, including CLI (az, sfctl) or ARM template workflows.
  • Provide examples for setting DNS names using Linux-compatible tools (e.g., sfctl, az CLI, YAML manifests for containerized workloads).
  • Clarify limitations for Linux clusters and offer guidance/workarounds for Linux users (e.g., how to enable DNS service without portal access).
  • Include sample workflows for Linux containerized services, such as Docker Compose or Kubernetes YAML, to demonstrate DNS integration.
  • Balance the order of examples so Linux approaches are presented alongside or before Windows-specific tools.
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-19 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. It references Windows file paths (e.g., Service Fabric SDK schema location), and the example directory structure uses a Windows-style executable (.exe). There are no explicit Linux/macOS examples or references to cross-platform tools or file paths. Visual Studio (a Windows-centric tool) is mentioned as a primary packaging method, and no Linux packaging or deployment workflow is described.
Recommendations
  • Add examples of packaging and deploying guest executables on Linux/macOS, including relevant file paths and executable formats (e.g., .sh, .out).
  • Mention cross-platform command-line tools or alternatives to Visual Studio for packaging and deploying applications.
  • Clarify if the Service Fabric SDK and schema files are available and usable on Linux/macOS, and provide their respective paths.
  • Include sample directory structures and manifests for Linux/macOS guest executables.
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-19 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation references PowerShell for deployment/removal tasks and links to a PowerShell-specific cmdlet for downloading ServicePackages. There are no equivalent Linux/bash examples or references to cross-platform tools. The 'Next steps' section directs users to PowerShell-based workflows, and the only explicit tooling example is Windows-centric.
Recommendations
  • Add Linux/bash CLI examples for deploying, removing, and downloading ServicePackages, using Azure CLI or Service Fabric CLI where available.
  • Include references to cross-platform tools and documentation, such as sfctl (Service Fabric CLI) for Linux/macOS users.
  • Update 'Next steps' to link to both PowerShell and Linux/bash workflows, or clarify which steps are cross-platform.
  • Where PowerShell cmdlets are mentioned, provide equivalent commands for Linux/macOS environments.
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-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 conceptual information about Azure Service Fabric hosting models, but when it comes to practical examples and management instructions, it heavily features PowerShell commands and references, which are Windows-centric. There are no CLI or Linux/macOS-specific examples for creating or managing services, and PowerShell is mentioned first and most prominently. This creates friction for Linux/macOS users, who may need to use Azure CLI or REST APIs instead.
Recommendations
  • Add Azure CLI examples for creating services with different ServicePackageActivationMode values.
  • Explicitly mention cross-platform management options (e.g., Azure CLI, REST API) alongside PowerShell.
  • Reorder or balance example sections so that Windows and Linux/macOS options are presented equally.
  • Link to documentation for Linux/macOS management tools 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-02-19 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation references PowerShell as the primary example for interacting with the Service Fabric cluster manifest and links to a PowerShell-based deployment guide as the next step. While .NET and REST are mentioned, PowerShell is listed first and is the only example explicitly linked. There are no Linux-specific tools or CLI examples provided, and the workflow is described in a way that assumes familiarity with Windows-centric tools.
Recommendations
  • Add Azure CLI or Service Fabric CLI (sfctl) examples for retrieving the cluster manifest and managing the ImageStoreConnectionString, especially for Linux/macOS users.
  • Include links to cross-platform tools and documentation, such as sfctl or REST API guides, alongside PowerShell references.
  • When listing programmatic options (PowerShell, .NET, REST), rotate or randomize the order, or explicitly state that all are supported equally.
  • Provide a 'Next steps' section that includes Linux/macOS-friendly guides, not just PowerShell-based ones.
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-19 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 shows a notable Windows bias. The manifest examples are explicitly based on a Windows Server 2016 Container Sample, and several instructions reference Windows-specific tools or patterns (e.g., 'winver' for OS build, Windows file paths like 'c:\VolumeTest\Data'). There is minimal mention of Linux equivalents, and no Linux-specific manifest examples or guidance are provided, despite Service Fabric supporting Linux containers.
Recommendations
  • Add Linux-based manifest examples or provide a parallel Linux section, including differences in file paths, volume mounts, and certificate handling.
  • When referencing OS-specific tools (e.g., 'winver'), also mention Linux equivalents (e.g., 'cat /etc/os-release' or 'uname -r').
  • Clarify which features or manifest elements are Windows-only and which are cross-platform.
  • Update volume mount examples to include Linux path formats (e.g., '/mnt/data') where appropriate.
  • Explicitly state any limitations or differences for Linux container support in Service Fabric.
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-02-19 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page provides Service Fabric manifest examples and explanations. While the manifest XML itself is cross-platform, the narrative and examples show a bias toward Windows patterns: batch scripts (.bat), references to Windows accounts (NetworkService, Administrators), and mentions of ServiceFabric PowerShell module for service creation. There are no Linux-specific examples (e.g., shell scripts, Linux user/group patterns), and Windows tools/scripts are referenced exclusively or first.
Recommendations
  • Add Linux-specific examples alongside Windows ones, such as using shell scripts (.sh) in SetupEntryPoint and EntryPoint.
  • Clarify which user/group patterns are valid for Linux Service Fabric clusters (e.g., use of local users, system groups).
  • Mention Linux equivalents for service creation (e.g., Azure CLI or sfctl) instead of only referencing PowerShell.
  • Explicitly note cross-platform differences in account types and script formats in relevant sections.
  • Provide guidance or links for Linux/macOS users deploying Service Fabric applications, including manifest considerations.
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-19 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-only (HTTP.sys) and cross-platform (Kestrel) web servers for ASP.NET Core in Service Fabric. However, Windows-specific tools and APIs (HTTP.sys, netsh, Windows HTTP Server API) are discussed in detail and often before their Linux equivalents. There are explicit notes about HTTP.sys being Windows-only, but Linux/macOS users are not provided with equivalent examples or troubleshooting guidance for non-Windows environments. The configuration and endpoint setup sections focus heavily on Windows patterns, and Visual Studio debugging is referenced without mention of cross-platform alternatives.
Recommendations
  • Add explicit Linux/macOS guidance and examples for Service Fabric scenarios using Kestrel, including endpoint configuration and troubleshooting.
  • Clarify which sections are Windows-only and which are cross-platform, ideally with clear headings or callouts.
  • Provide links or references to Linux/macOS development tools (e.g., VS Code, CLI debugging) where Visual Studio is mentioned.
  • Ensure troubleshooting and configuration guidance covers Linux/macOS scenarios, especially for port assignment and firewall configuration.
  • Consider including a summary table comparing Windows and Linux/macOS approaches for common tasks.
GitHub Create Pull Request
Service Fabric Reliable Collection object serialization ...c-reliable-services-reliable-collections-serialization.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 provides examples and references primarily in C#/.NET, which is cross-platform, but the 'Next steps' section lists Windows-centric tools (Visual Studio and PowerShell) before mentioning any alternatives. There are no Linux-specific upgrade tools or examples, and PowerShell is highlighted as a primary automation method, which may create friction for Linux/macOS users who prefer Bash or other native tools.
Recommendations
  • Add examples or links for upgrading applications using Bash or CLI tools on Linux/macOS, such as Azure CLI or Service Fabric CLI.
  • Mention cross-platform alternatives to PowerShell for automation, or clarify that PowerShell Core is available on Linux/macOS.
  • Reorder 'Next steps' to present platform-neutral or Linux-friendly options before Windows-specific ones.
  • Explicitly state if the guidance is applicable to Linux/macOS Service Fabric clusters, and provide any relevant differences.
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-19 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. There is no equivalent Linux CLI example (e.g., using sfctl or Azure CLI), and the PowerShell example is presented as the default method. The documentation references the Service Fabric SDK schema location using a Windows file path first, and only later mentions the Linux certificate store location. Linux-specific deployment commands and patterns are missing.
Recommendations
  • Add equivalent Linux/macOS deployment examples using sfctl or Azure CLI alongside PowerShell.
  • Mention Linux file paths and tools (e.g., sfctl, bash) where relevant, not just Windows paths.
  • Present cross-platform instructions in parallel, or clarify which steps are OS-specific.
  • Include a note about how Linux users can override endpoints and deploy applications, referencing relevant tools and commands.
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-19 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' consistently references PowerShell APIs (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica) and provides examples and links exclusively for PowerShell usage. There is no mention of Linux or cross-platform equivalents, nor are CLI or REST API examples provided. The documentation assumes the use of Windows tooling and patterns, which may create friction for Linux/macOS users managing Service Fabric clusters.
Recommendations
  • Add equivalent examples for Linux/macOS users, such as using Service Fabric CLI (sfctl) or REST APIs where available.
  • Clarify whether the PowerShell APIs are supported on Linux via PowerShell Core, or provide guidance for Linux users.
  • Include links and usage examples for cross-platform tools (e.g., sfctl commands for removing/restoring replicas).
  • Explicitly state any limitations or parity gaps for Linux/macOS users in the feature support section.
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-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 detailed PowerShell examples for health reporting and cluster connection, but does not offer equivalent Linux/bash 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, bash scripts, or Service Fabric CLI (sfctl) for health reporting and cluster connection.
  • Clarify which tools are cross-platform and which are Windows-only, and provide guidance for Linux/macOS users.
  • Mention REST API as a cross-platform option earlier and provide more detailed REST examples.
  • Where PowerShell is used, note if the commands are available on PowerShell Core (cross-platform) or only on Windows PowerShell.
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-19 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 and references features (Build/Rebuild/F5/Ctrl+F5/Publish) that are exclusive to Windows environments. All examples and screenshots are based on Visual Studio, with no mention of Linux/macOS tooling or workflows (such as CLI, VS Code, or cross-platform deployment methods). There are references to PowerShell as an alternative, but no Linux shell or cross-platform CLI examples are provided.
Recommendations
  • Add explicit guidance for Linux/macOS users, including how to manage service configuration and deployment without Visual Studio.
  • Provide examples using Azure CLI, Service Fabric CLI (sfctl), or PowerShell Core (if cross-platform) for creating and deploying applications.
  • Clarify which features are Visual Studio/Windows-only and offer alternative workflows for non-Windows environments.
  • Include screenshots or walkthroughs for cross-platform tools (e.g., VS Code, CLI) where possible.
GitHub Create Pull Request
← Previous Page 7 of 53 Next →