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 451-475 of 2475 flagged pages
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-05 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation is generally OS-neutral in its explanations of Service Fabric activation and deactivation lifecycle, but there is a subtle Windows/PowerShell bias. The only explicit tooling reference for deployment/removal is to PowerShell, and the 'Next steps' section links to PowerShell-based guides without mentioning Linux/CLI alternatives. There are no Linux-specific examples or cross-platform command-line instructions.
Recommendations
  • Add references to cross-platform deployment/removal guides using Azure CLI or Service Fabric CLI (sfctl), especially in the 'Next steps' section.
  • Where PowerShell is mentioned, clarify if the instructions are Windows-only and provide equivalent steps for Linux/macOS if available.
  • Consider including at least one Linux/macOS example or note on how to perform common lifecycle operations on non-Windows platforms.
  • Link to documentation for Service Fabric on Linux, if relevant, to help non-Windows users.
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-05 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page provides Service Fabric application and service manifest examples, but exhibits mild Windows bias. It references Windows-specific concepts (e.g., NETWORKSERVICE account, Setup.bat, .exe files), and mentions the ServiceFabric PowerShell module as a way to create service instances, without offering Linux equivalents or examples. The manifest examples use Windows-style executables (.exe, .bat), and the security principal examples reference Windows system groups (Administrators, NetworkService). No Linux-specific guidance, tools, or examples are provided.
Recommendations
  • Add examples or notes for Linux deployments, such as using shell scripts (.sh) instead of .bat files, and referencing Linux user/group concepts.
  • Mention cross-platform tools (e.g., Azure CLI, sfctl) for managing Service Fabric applications, alongside or instead of PowerShell.
  • Clarify which features and manifest settings are supported on Linux clusters, and highlight any differences.
  • Provide sample manifests or code snippets that use Linux-compatible entry points and security principals.
GitHub Create Pull Request
Service Fabric Reliable Collection object serialization ...c-reliable-services-reliable-collections-serialization.md
Medium Priority View Details →
Scanned: 2026-03-05 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation is generally platform-neutral, focusing on .NET serialization concepts relevant to Azure Service Fabric. However, in the 'Next steps' section, Windows-centric tools (Visual Studio and PowerShell) are mentioned for application upgrades, with no equivalent Linux/macOS tooling or examples provided. Additionally, PowerShell is highlighted as a primary upgrade method, which may create friction for Linux/macOS users.
Recommendations
  • Add examples or links for upgrading applications using cross-platform tools such as Azure CLI or REST APIs.
  • Mention Linux/macOS-compatible development environments (e.g., Visual Studio Code, JetBrains Rider) alongside Visual Studio.
  • Clarify if PowerShell examples are cross-platform (PowerShell Core), or provide Bash/Azure CLI alternatives.
  • Explicitly state platform requirements for upgrade tutorials, so Linux/macOS users know what is 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-05 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation provides comprehensive coverage of both Kestrel (cross-platform) and HTTP.sys (Windows-only) web servers for ASP.NET Core in Service Fabric. However, it exhibits Windows bias by: (1) giving detailed attention to HTTP.sys, a Windows-only technology, including endpoint configuration and port sharing, (2) referencing Windows-specific tools (e.g., netsh) and APIs, (3) mentioning Windows features and HTTP.sys before Kestrel in several sections, and (4) lacking explicit Linux/macOS example snippets or guidance (such as how to configure Service Fabric for Linux, or how to debug/deploy on Linux/macOS). While Kestrel is recommended for cross-platform scenarios, Linux-specific considerations are not addressed, and all code samples are generic or Windows-centric.
Recommendations
  • Add explicit Linux/macOS guidance for Service Fabric and ASP.NET Core integration, including any OS-specific configuration steps.
  • Include example snippets or troubleshooting tips for Linux/macOS environments (e.g., directory paths, permissions, firewall configuration).
  • Clarify in each section which features are Windows-only (e.g., HTTP.sys, netsh) and which are cross-platform.
  • Provide links to Linux/macOS documentation for Service Fabric and ASP.NET Core where relevant.
  • Ensure Kestrel (cross-platform) examples are shown first or highlighted for Linux users.
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-05 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page for 'Replica soft delete for enhanced data protection in Service Fabric' heavily references PowerShell APIs (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica) and provides examples and screenshots based on Windows tooling. There is no mention of Linux/macOS equivalents, nor are cross-platform CLI or SDK usage patterns discussed. The documentation assumes familiarity with Windows administrative tools and does not clarify whether the described APIs or features are available or usable on Linux-based Service Fabric clusters.
Recommendations
  • Explicitly state whether the PowerShell APIs are available on Linux/macOS, or provide equivalent CLI/SDK usage examples for those platforms.
  • Include examples using cross-platform tools such as Azure CLI, REST API, or .NET Core SDK (FabricClient) for managing replicas.
  • Clarify any platform limitations for the soft delete feature (e.g., if it is Windows-only, state so clearly).
  • Add screenshots or command output from Linux environments if applicable.
  • Reorder sections or examples to avoid always presenting Windows/PowerShell first.
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-05 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed PowerShell examples for health reporting in Service Fabric, with explicit Windows paths and commands (e.g., 'PS C:\>'). There are no equivalent Linux/bash CLI examples, and PowerShell is presented before REST and API options. This creates friction for Linux/macOS users, as Service Fabric supports cross-platform clusters and REST/CLI usage, but the documentation does not demonstrate parity.
Recommendations
  • Add equivalent bash/CLI examples for health reporting, using Azure CLI or Service Fabric CLI tools where available.
  • Clarify which PowerShell commands are available cross-platform (e.g., PowerShell Core) and which are Windows-only.
  • Present REST and API examples before or alongside PowerShell, emphasizing their cross-platform nature.
  • Explicitly mention Linux/macOS support and link to relevant tools or documentation for those environments.
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-03-05 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page primarily uses Windows/PowerShell tooling for deployment examples (e.g., New-ServiceFabricApplication), references Windows file paths for schema files, and generally presents Windows-specific details before Linux equivalents. Linux-specific information is minimal and often relegated to brief notes.
Recommendations
  • Provide equivalent Linux CLI (e.g., Azure CLI or sfctl) examples alongside or in place of PowerShell commands for deploying Service Fabric applications.
  • When referencing file paths (such as schema locations), include both Windows and Linux paths where applicable.
  • Ensure that Linux-specific behaviors (such as certificate store locations) are given equal prominence and explanation, not just brief notes.
  • Consider adding a dedicated section or callouts for Linux/macOS users, especially for deployment and certificate management steps.
  • Where possible, alternate the order of Windows and Linux examples to avoid implicit prioritization.
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-05 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page focuses exclusively on Visual Studio workflows and features (such as Build/Rebuild/F5/Ctrl+F5/Publish) for Service Fabric applications, which are Windows-centric. It does not provide examples or guidance for Linux/macOS users, nor does it mention alternative tools or workflows for those platforms. References to PowerShell are present, but only as a passing mention, and no Linux equivalents (such as Bash or CLI commands) 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, Bash, or other cross-platform tools for deploying Service Fabric applications.
  • Clarify which features are Visual Studio/Windows-only and suggest alternative workflows for non-Windows environments.
  • Include sample commands or scripts for Linux-based Service Fabric clusters, if supported.
GitHub Create Pull Request
Service Fabric Fault Analysis Service overview .../service-fabric/service-fabric-testability-overview.md
Medium Priority View Details →
Scanned: 2026-03-05 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page provides examples for using the Fault Analysis Service via C# and PowerShell, but does not mention or provide equivalent examples for Linux/macOS users (e.g., Bash, CLI, or REST API usage). The PowerShell example assumes Windows environments and tools, and there is no guidance for Linux users on how to interact with the Fault Analysis Service.
Recommendations
  • Add examples for using the Fault Analysis Service via Azure CLI or REST API, which are cross-platform and usable on Linux/macOS.
  • Mention any prerequisites or SDKs for Linux/macOS environments, if available.
  • If PowerShell Core is supported on Linux/macOS, clarify this and provide relevant instructions.
  • Ensure that documentation sections do not assume Windows-only tools unless the feature is Windows-specific.
GitHub Create Pull Request
Service Fabric Custom Image .../articles/service-fabric/how-to-deploy-custom-image.md
Medium Priority View Details →
Scanned: 2026-03-04 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 is notably Windows-focused: it refers to 'custom windows images' throughout, provides only PowerShell (Windows-centric) examples for role assignment, and references Windows/PowerShell CLI documentation before Linux equivalents. There are no explicit Linux-specific examples or instructions, and the ARM template examples do not clarify Linux support. The page title and content do not indicate this is a Windows-only feature, and Service Fabric Managed Clusters support both Windows and Linux node types.
Recommendations
  • Clarify in the introduction whether custom images for Linux node types are supported and, if so, provide explicit instructions and examples for Linux.
  • Include Linux-specific CLI examples (e.g., using Azure CLI or Bash) for role assignment and other operations, not just PowerShell.
  • When referencing documentation, link to both Linux and Windows guides equally, or provide a neutral, cross-platform reference.
  • Update terminology to refer to 'custom images' (not just 'custom windows images') where appropriate, and specify differences if any exist.
  • Add ARM template examples for deploying Linux-based custom images if supported.
GitHub Create Pull Request
Service Fabric On-demand backup in Azure Service Fabric ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-backup-restore-service-ondemand-backup.md
Medium Priority View Details →
Scanned: 2026-03-04 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 on-demand backup in Azure Service Fabric exclusively provides PowerShell-based examples and instructions, including module installation and REST API usage via PowerShell. There are no examples or guidance for Linux/macOS users (e.g., Bash, curl, Azure CLI), and PowerShell is presented as the primary and only scripting method, which creates friction for non-Windows users.
Recommendations
  • Add equivalent Bash/curl examples for REST API calls, showing how to trigger backups and track progress from Linux/macOS.
  • Mention Azure CLI commands if available for backup operations, or clarify their absence.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is required for all platforms, or provide alternatives for Linux/macOS users.
  • Include a note about cross-platform support and any limitations for Linux/macOS users.
  • Consider showing Bash/curl examples before or alongside PowerShell to improve parity.
GitHub Create Pull Request
Service Fabric RunToCompletion semantics and specifications ...blob/main/articles/service-fabric/run-to-completion.md
Medium Priority View Details →
Scanned: 2026-03-04 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates notable Windows bias. All code examples use Windows containers (nanoserver), Windows-specific commands (cmd, echo, ping, set, exit), and reference Windows container compatibility. Query instructions are provided only for PowerShell and C#, with no mention of Linux/macOS equivalents or cross-platform CLI tools. There are no examples or guidance for Linux containers or non-Windows environments, despite Service Fabric supporting containers in general.
Recommendations
  • Add examples using Linux containers (e.g., Ubuntu or Alpine images) and Linux shell commands.
  • Provide instructions for querying deployment status using Azure CLI or cross-platform tools, not just PowerShell.
  • Clarify whether RunToCompletion semantics are supported for Linux containers and, if so, provide equivalent code and manifest examples.
  • Mention any platform-specific limitations or differences explicitly.
  • Ensure that introductory and code sections do not assume Windows familiarity unless the feature is Windows-only.
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-04 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page primarily discusses data serialization in the context of Azure Service Fabric, which is cross-platform. However, in the 'Next steps' section, it references upgrading applications using Visual Studio and PowerShell—both of which are traditionally Windows-centric tools—before mentioning any CLI or Linux-native alternatives. There are no explicit Linux/macOS examples or references to cross-platform tools like Azure CLI or Service Fabric CLI.
Recommendations
  • Include examples or references for upgrading applications using cross-platform tools such as Azure CLI or Service Fabric CLI (sfctl), especially for Linux/macOS users.
  • When listing upgrade tutorials, either provide parity (e.g., 'Upgrading your Application Using Azure CLI') or clarify which tools are cross-platform.
  • Consider mentioning Visual Studio Code as a cross-platform alternative to Visual Studio, if applicable.
  • Explicitly state when a tool or method is Windows-only to help set expectations for non-Windows users.
GitHub Create Pull Request
Service Fabric Application upgrade: upgrade parameters ...abric/service-fabric-application-upgrade-parameters.md
Medium Priority View Details →
Scanned: 2026-03-04 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page presents upgrade parameters for Service Fabric applications, but gives primary focus to Windows-centric tools (PowerShell and Visual Studio) in both structure and examples. PowerShell and Visual Studio are discussed first and in greater detail, with parameter tables and example formats, while Linux-compatible tools (SFCTL CLI) are covered later and less thoroughly. There are no explicit Linux command examples or walkthroughs in the main content, and the SFCTL section lacks parity in example depth compared to PowerShell. This creates friction for Linux/macOS users, though workarounds exist via SFCTL and REST.
Recommendations
  • Reorganize the page to present SFCTL (cross-platform CLI) examples and parameters before or alongside PowerShell/Visual Studio.
  • Provide explicit Linux/macOS command examples using SFCTL, including sample upgrade commands and parameter usage.
  • Clarify which tools are cross-platform and which are Windows-only, to guide users appropriately.
  • Ensure parameter tables for SFCTL match the detail and clarity of PowerShell/Visual Studio sections.
  • Add a note at the top indicating that PowerShell and Visual Studio are Windows-only, and SFCTL is recommended for Linux/macOS users.
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-03-04 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides example code for configuring auto scaling policies in Azure Service Fabric using application manifests, C# APIs, and PowerShell. However, all CLI examples are PowerShell-based, with no equivalent Bash or Linux CLI examples. PowerShell is a Windows-centric tool, and its exclusive use creates friction for Linux/macOS users. Additionally, PowerShell examples are presented alongside C# and manifest examples, but no Linux-native tooling or cross-platform CLI (such as sfctl) is mentioned or demonstrated. The documentation does note that resource monitoring is supported for containerized applications on Linux, but the practical guidance and examples are Windows-oriented.
Recommendations
  • Add equivalent examples using sfctl (Service Fabric CLI), which is cross-platform and works on Linux/macOS.
  • Provide Bash shell script examples for relevant operations, especially for updating scaling policies.
  • Clarify which steps or commands are Windows-only and which are cross-platform.
  • Mention Linux/macOS tooling and workflows explicitly where applicable.
  • Consider reordering examples so that cross-platform options are presented before or alongside Windows-specific ones.
GitHub Create Pull Request
Service Fabric Architecture of Azure Service Fabric ...articles/service-fabric/service-fabric-architecture.md
Medium Priority View Details →
Scanned: 2026-03-04 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation references PowerShell cmdlets as a primary management interface for Service Fabric, and mentions Windows security as a transport option, with no equivalent Linux tooling or examples provided. While the architectural concepts are platform-neutral, the management subsystem section gives Windows-oriented tools first and omits Linux alternatives, creating friction for Linux users.
Recommendations
  • Add references to Linux-compatible management tools, such as Azure CLI or REST APIs, alongside PowerShell cmdlets.
  • Explicitly mention cross-platform options for cluster management and lifecycle operations.
  • Clarify that X509 certificates are supported for secure transport on Linux, and provide links or examples for Linux security configuration.
  • Ensure examples and tooling references are balanced between Windows and Linux, or note platform-specific differences.
GitHub Create Pull Request
Service Fabric Node types and virtual machine scale sets ...les/service-fabric/service-fabric-cluster-nodetypes.md
Medium Priority View Details →
Scanned: 2026-03-04 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides general information about Azure Service Fabric node types and virtual machine scale sets, but there are subtle signs of Windows bias. Examples and guidance reference Windows-style paths (e.g., 'D:\\SvcFab'), and the 'Next steps' section links primarily to PowerShell scripts and RDP-related tasks, which are Windows-centric. There is no explicit Linux/macOS guidance or examples for connecting to nodes or managing clusters, despite the mention of 'ServiceFabricLinuxNode' in the extension snippet.
Recommendations
  • Provide equivalent Linux/macOS examples for remote connection (e.g., SSH instructions alongside RDP/PowerShell).
  • Include Linux file path examples (e.g., '/var/svcfab') when referencing 'dataPath'.
  • Add links to Bash/CLI scripts or documentation for Linux cluster management tasks.
  • Clarify which instructions are OS-specific and offer parity for both Windows and Linux 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-04 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 creates friction for Linux/macOS users.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl) for Linux/macOS.
  • Include REST API examples for health reporting and querying, which are platform-agnostic.
  • Mention cross-platform tools and clarify which commands are available on each OS.
  • Where PowerShell is used, provide links or references to Linux/macOS alternatives.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Events ...es/service-fabric/service-fabric-diagnostics-events.md
Medium Priority View Details →
Scanned: 2026-03-04 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-specific event logging mechanisms (ETW/Windows Event logs) and the Windows Azure diagnostics agent, with no mention of Linux equivalents or guidance for Linux-based Service Fabric clusters. The examples and instructions focus on Windows tools and patterns, and Linux event access methods are not discussed.
Recommendations
  • Add information about how Service Fabric events are accessed and logged on Linux-based clusters, including supported logging mechanisms (e.g., stdout, syslog, journald).
  • Provide examples or references for configuring diagnostics and monitoring on Linux clusters, such as using the Azure Monitor agent for Linux.
  • Clarify which event access methods are cross-platform (e.g., EventStore REST APIs) and which are Windows-only.
  • Consider including a comparison table or section outlining differences in event access between Windows and Linux clusters.
GitHub Create Pull Request
Service Fabric Azure Service Fabric hosting activation and deactivation life cycle ...les/service-fabric/service-fabric-hosting-lifecycle.md
Medium Priority View Details →
Scanned: 2026-03-04 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation references PowerShell for deployment/removal tasks and for downloading ServicePackages in advance, without mentioning Linux equivalents (such as Azure CLI or REST API). There are no explicit Linux/macOS command examples or tool references, and the linked guidance for deployment/removal is PowerShell-centric. This may create friction for Linux/macOS users managing Service Fabric clusters.
Recommendations
  • Provide equivalent Azure CLI or REST API examples for deployment, removal, and ServicePackage download tasks.
  • Include references or links to Linux/macOS-compatible tools and documentation where available.
  • Clarify in the 'Next steps' section if PowerShell is required, or offer alternative instructions for non-Windows users.
  • Where possible, add notes about cross-platform support for Service Fabric management tasks.
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-03-04 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is the only command-line example shown for deploying applications with parameter overrides, and Windows file paths and certificate store names (e.g., 'C:\Program Files\...', 'MY' store) are mentioned first or exclusively in several places. While there is a brief note about Linux certificate storage, Linux/macOS command-line equivalents and deployment instructions are missing.
Recommendations
  • Provide equivalent Linux/macOS command-line examples (e.g., using Azure CLI or sfctl) alongside PowerShell for deploying Service Fabric applications with parameter overrides.
  • Mention Linux file paths and certificate store locations in parallel with Windows paths, not only as a note after the Windows example.
  • Clarify any differences in endpoint/certificate configuration between Windows and Linux clusters, and link to relevant Linux-specific documentation where appropriate.
  • If certain features or commands are Windows-only, explicitly state this and provide Linux alternatives or workarounds if available.
GitHub Create Pull Request
Service Fabric X.509 Certificate-based Authentication in a Service Fabric Cluster ...ticles/service-fabric/cluster-security-certificates.md
Medium Priority View Details →
Scanned: 2026-03-04 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides detailed explanations and examples for X.509 certificate-based authentication in Service Fabric clusters, but exhibits Windows bias in several areas. Windows certificate store paths and tools are mentioned first or exclusively, such as 'LocalMachine\My', with Linux equivalents only briefly referenced. Troubleshooting sections focus on Windows event logs and tools (e.g., CAPI2 logging), with no Linux log or troubleshooting guidance. Code snippets and configuration examples use Windows-centric terminology and paths, and there are no explicit Linux/macOS command examples or troubleshooting steps.
Recommendations
  • Provide Linux/macOS equivalents for certificate store paths and management (e.g., clarify how certificates are stored and loaded on Linux nodes, with explicit paths and commands).
  • Include troubleshooting guidance for Linux clusters, such as relevant log locations, commands (e.g., journalctl, syslog), and certificate validation tools (e.g., openssl, certtool).
  • Add Linux/macOS-focused examples for certificate provisioning, validation, and rotation, including sample commands for certificate installation and verification.
  • When referencing Windows tools (e.g., CAPI2 logging, Win32 CryptoAPI), also mention or link to Linux/macOS alternatives or explain how similar diagnostics can be performed on those platforms.
  • Ensure parity in example ordering: present Linux/macOS examples alongside or before Windows examples where possible.
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-04 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides a comprehensive overview of certificate management in Azure Service Fabric clusters, but exhibits a moderate Windows bias. PowerShell is the only CLI scripting language shown for programmatic certificate enrollment, and the Key Vault VM extension is described primarily in its Windows variant. The 'linkOnRenewal' feature and S-channel behavior are discussed as Windows-specific, with no mention of Linux equivalents or alternatives. JSON ARM templates are cross-platform, but operational scripting and troubleshooting focus on Windows tools and patterns. Linux scenarios, tools, or command-line examples (e.g., Azure CLI, bash scripting, or Linux VM extensions) are not covered, and Windows-specific mechanisms are often described first or exclusively.
Recommendations
  • Add Azure CLI (az) and/or bash scripting examples for certificate enrollment and management, alongside or in place of PowerShell.
  • Document the use of the Key Vault VM extension for Linux (if supported), or clarify any platform limitations.
  • Explicitly mention Linux/macOS support for Service Fabric clusters, and provide guidance or links for certificate provisioning and management on those platforms.
  • When discussing Windows-specific features (e.g., S-channel, linkOnRenewal), clearly state their platform scope and, if possible, provide Linux/macOS alternatives or note their absence.
  • Balance the ordering of examples and explanations so that Linux and cross-platform approaches are presented alongside Windows ones, not only after or not at all.
GitHub Create Pull Request
Service Fabric Introduction to the Service Fabric Infrastructure Service .../articles/service-fabric/infrastructure-service-faq.md
Medium Priority View Details →
Scanned: 2026-03-04 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 bypassing Infrastructure Service, and references Service Fabric Explorer (a GUI tool typically used on Windows). No equivalent Linux/macOS CLI or tooling examples are given, and PowerShell is presented as the default method for manual operations.
Recommendations
  • Add equivalent CLI examples for Linux/macOS users, such as using Azure CLI or REST API calls where possible.
  • Clarify whether the PowerShell command can be run from PowerShell Core on Linux/macOS, or provide alternative commands.
  • Mention cross-platform tools or interfaces (e.g., Azure CLI, REST API) for managing Service Fabric clusters.
  • If Service Fabric Explorer is Windows-only, note alternatives for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Initializer CodePackages in Service Fabric ...in/articles/service-fabric/initializer-codepackages.md
Medium Priority View Details →
Scanned: 2026-03-04 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 Initializer CodePackages in Service Fabric provides only Windows container examples, uses Windows-specific images (nanoserver), Windows paths, and Windows command syntax (cmd, C:\ paths). It explicitly references Windows container compatibility and does not provide any Linux container or cross-platform examples. All sample manifests, commands, and volume mounts are Windows-centric, creating friction for Linux/macOS users.
Recommendations
  • Add equivalent examples using Linux containers (e.g., Ubuntu or Alpine images) with Linux command syntax and paths.
  • Document any platform limitations or differences in Initializer CodePackages for Linux containers, if applicable.
  • Provide guidance or links for creating Service Fabric applications with Linux containers.
  • Clarify whether Initializer CodePackages are supported for Linux container workloads, and if not, state this explicitly.
GitHub Create Pull Request
← Previous Page 19 of 99 Next →