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

1235 issues found
Showing 101-125 of 1235 flagged pages
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
Service Fabric Configure the upgrade of a Service Fabric application ...abric/service-fabric-visualstudio-configure-upgrade.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 is heavily focused on Windows tooling, specifically Visual Studio and PowerShell, for configuring and upgrading Service Fabric applications. All examples and upgrade instructions reference Windows tools, with no mention of Linux/macOS equivalents or cross-platform alternatives. There are no CLI or script examples for Linux users, and PowerShell is presented as the primary method for manual upgrades.
Recommendations
  • Add instructions and examples for upgrading Service Fabric applications using Azure CLI or REST API, which are cross-platform.
  • Include guidance for Linux/macOS users, such as how to configure upgrades without Visual Studio or PowerShell.
  • Mention and link to any available cross-platform tooling or SDKs for Service Fabric application management.
  • Clarify if certain features (like Visual Studio integration) are Windows-only, and provide alternative workflows for non-Windows environments.
GitHub Create Pull Request
Service Fabric RunToCompletion semantics and specifications ...blob/main/articles/service-fabric/run-to-completion.md
Medium Priority View Details →
Scanned: 2026-02-18 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation page presents RunToCompletion semantics primarily in the context of Windows containers and Windows-specific tools. All code examples reference Windows container images and use Windows command syntax (cmd.exe). Querying deployment status is described using PowerShell and C# APIs, with no mention of Linux equivalents or cross-platform CLI tools. There are no examples or guidance for Linux containers or Linux-based workflows, despite Service Fabric supporting containers in general.
Recommendations
  • Add Linux container examples (e.g., using Ubuntu or Alpine images) alongside Windows container examples.
  • Provide equivalent Linux shell commands (bash/sh) for CodePackage entry points.
  • Mention and demonstrate querying deployment status using Azure CLI or Service Fabric CLI (sfctl), which are cross-platform.
  • Clarify any limitations or differences in RunToCompletion semantics for Linux containers, if applicable.
  • Reorganize examples to show both Windows and Linux scenarios, or explicitly state if RunToCompletion is Windows-only.
GitHub Create Pull Request
Service Fabric Advanced Application Upgrade Topics ...-fabric/service-fabric-application-upgrade-advanced.md
Medium Priority View Details →
Scanned: 2026-02-18 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 advanced Service Fabric application upgrade topics consistently uses PowerShell cmdlets for examples and references, with no mention of Linux/macOS equivalents or cross-platform CLI tools. All command-line instructions are given in PowerShell, and there is no guidance for Linux users on how to perform these tasks using Service Fabric CLI (sfctl) or REST APIs. This creates friction for Linux/macOS users, who may not have access to PowerShell or may prefer native tools.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and supported on Linux/macOS.
  • Mention REST API options for relevant operations, with links to documentation.
  • Clarify which PowerShell cmdlets are Windows-only and provide guidance for Linux/macOS users.
  • In 'Next steps', include links to tutorials for Linux/macOS users, such as 'Upgrading your Application Using sfctl'.
  • Where possible, provide ARM template examples alongside PowerShell, and clarify their cross-platform applicability.
GitHub Create Pull Request
Service Fabric Azure Service Fabric standalone cluster scaling ...ce-fabric/service-fabric-cluster-scaling-standalone.md
Medium Priority View Details →
Scanned: 2026-02-18 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page on scaling Azure Service Fabric standalone clusters demonstrates Windows bias by exclusively referencing PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) and linking to a Windows Server-specific guide for scaling standalone clusters. There are no Linux-specific instructions, examples, or mentions of Linux tooling for cluster scaling, despite Service Fabric standalone clusters being theoretically deployable on Linux.
Recommendations
  • Add Linux-specific instructions for scaling standalone clusters, including relevant CLI commands and configuration steps.
  • Provide examples using Linux shell tools (e.g., Bash, sfctl) alongside PowerShell examples.
  • Clarify whether standalone cluster scaling is supported on Linux, and if not, state this explicitly to avoid confusion.
  • Link to Linux documentation or guides if available, or note limitations if Linux support is incomplete.
GitHub Create Pull Request
Service Fabric Restoring backup in Azure Service Fabric ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-backup-restore-service-trigger-restore.md
Medium Priority View Details →
Scanned: 2026-02-18 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 restoring backups in Azure Service Fabric is heavily focused on PowerShell-based workflows, specifically using the Microsoft.ServiceFabric.Powershell.Http module and PowerShell scripting for REST API calls. All code examples and instructions are provided exclusively in PowerShell, with no mention of Linux/macOS equivalents (such as Bash, curl, or Azure CLI). The prerequisite section also assumes PowerShell usage and Windows tooling, and there is no guidance for Linux users on how to perform equivalent operations. This creates friction for Linux/macOS users, who may not have access to PowerShell or the required modules.
Recommendations
  • Add equivalent examples using Bash and curl for REST API calls, as Service Fabric REST APIs are platform-agnostic.
  • Document how to authenticate and make REST calls from Linux/macOS, including certificate handling.
  • Mention Azure CLI commands where possible for cross-platform parity.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is required for all scenarios, or if REST calls can be made directly from any OS.
  • Provide guidance for Linux/macOS users on connecting to Service Fabric clusters and restoring backups.
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-18 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides configuration examples using Application Manifest (XML/JSON), PowerShell, and C# APIs. PowerShell examples are prominent and shown before C# API examples, but there are no CLI or Bash examples for Linux/macOS users. The PowerShell API is Windows-centric, and no equivalent Linux-friendly command-line instructions (such as Azure CLI or REST API usage) are provided. This creates friction for Linux/macOS administrators managing Service Fabric clusters.
Recommendations
  • Add Azure CLI or REST API examples for configuring service sensitivity and maximum load, if supported.
  • Clarify whether PowerShell commands can be run cross-platform (PowerShell Core), or specify Windows-only limitations.
  • Provide guidance for Linux/macOS users on how to perform equivalent operations, or explicitly state if certain operations are Windows-only.
  • Consider including Bash shell script examples or references to SDKs/libraries usable on Linux/macOS.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager - Placement Policies ...ce-manager-advanced-placement-rules-placement-policies.md
Medium Priority View Details →
Scanned: 2026-02-18 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 for configuring Service Fabric placement policies using C# and PowerShell. PowerShell is a Windows-centric tool, and no equivalent Linux/macOS CLI examples (such as Azure CLI or REST API) are provided. All operational examples for service creation and placement policy configuration use PowerShell, which may create friction for Linux/macOS users who do not have access to PowerShell or prefer cross-platform tools. Additionally, PowerShell examples are consistently shown alongside C# code, with no mention of Linux-native alternatives.
Recommendations
  • Add Azure CLI examples for service creation and placement policy configuration, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Document REST API usage for configuring placement policies, providing sample requests and responses.
  • Explicitly mention whether PowerShell is required, and provide guidance for Linux/macOS users on alternative tools.
  • Consider including Bash scripts or references to Service Fabric SDK tools available on Linux.
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-18 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 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 channels and tools, and do not address how Linux-based Service Fabric clusters can access or monitor events.
Recommendations
  • Add information about how Service Fabric events are logged and accessed on Linux clusters, including any differences in event channels or monitoring tools.
  • Provide examples or instructions for accessing events using Linux-compatible tools (e.g., syslog, journald, Azure Monitor integration for Linux).
  • Clarify whether the EventStore REST APIs and Service Fabric Client Library are fully cross-platform, and provide usage examples for Linux environments.
  • Explicitly state if certain features or event channels are Windows-only, and offer alternative approaches for Linux users where possible.
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-18 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page for 'Replica soft delete for enhanced data protection in Service Fabric' demonstrates a notable Windows/PowerShell bias. All command-line/API usage examples reference PowerShell cmdlets (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica, Get-ServiceFabricReplica), with no mention of Linux CLI equivalents, REST APIs, or cross-platform SDK usage. The documentation assumes the use of Windows tooling and does not provide guidance for Linux or macOS users, despite Service Fabric supporting cross-platform clusters.
Recommendations
  • Include equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and supported on Linux/macOS.
  • Document REST API or FabricClient SDK usage for soft delete and restore operations, with code snippets in a cross-platform language (e.g., Python, C# .NET Core).
  • Explicitly state if certain features or APIs are only available via PowerShell or Windows, or clarify cross-platform support.
  • Add a section or callouts for Linux/macOS users, outlining the steps and tools they should use to achieve the same tasks.
GitHub Create Pull Request
Service Fabric Fault Analysis Service overview .../service-fabric/service-fabric-testability-overview.md
Medium Priority View Details →
Scanned: 2026-02-18 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides explicit PowerShell instructions for using the Fault Analysis Service, but does not mention or provide examples for Linux/macOS command-line tools or SDKs. The PowerShell section is prominent, and no equivalent Bash, CLI, or cross-platform scripting guidance is given. This creates friction for Linux/macOS users, though workarounds exist via the C# API or REST endpoints.
Recommendations
  • Add Azure CLI or Bash examples for inducing faults and running test scenarios, if supported.
  • Clarify whether the Fault Analysis Service APIs can be accessed from Linux/macOS environments, and provide guidance for those platforms.
  • Mention or link to any cross-platform SDKs or tools (e.g., .NET Core, REST API) usable from Linux/macOS.
  • If PowerShell is required, note whether PowerShell Core (cross-platform) is supported, and provide installation instructions for Linux/macOS.
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-18 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 provides conceptual information applicable to both Windows and Linux clusters. However, it exhibits Windows bias in several ways: PowerShell is the only CLI example shown for service creation, and all operational links reference PowerShell cmdlets. There are no Linux-specific CLI examples (e.g., Bash, Azure CLI), and PowerShell is presented before REST and .NET API options. This creates friction for Linux users, as Service Fabric supports Linux clusters but the documentation does not demonstrate parity in tooling or examples.
Recommendations
  • Add Azure CLI or Bash examples for service creation and management, especially for commands like New-ServiceFabricService.
  • Include references to Linux-compatible tools and workflows, such as sfctl (Service Fabric CLI) and REST API usage from Bash.
  • Clarify in the introduction that the concepts apply to both Windows and Linux clusters, and provide links to Linux-specific operational documentation.
  • Where PowerShell is referenced, add a note or section for Linux users explaining equivalent commands and tools.
GitHub Create Pull Request
Service Fabric Manage certificates in a Service Fabric cluster ...vice-fabric/cluster-security-certificate-management.md
Medium Priority View Details →
Scanned: 2026-02-18 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides a significant number of PowerShell-based examples for certificate management and provisioning, and references Windows-specific tools and behaviors (such as Key Vault VM extension for Windows, S-channel, and certificate linking). While the overall guidance is Azure-centric and much of the process is cross-platform, the hands-on and troubleshooting sections focus on Windows and PowerShell, with little to no mention of Linux equivalents or alternative scripting approaches. Windows-specific mechanisms (e.g., certificate store locations, S-channel, linking on renewal) are discussed in detail, while Linux/macOS scenarios are not addressed.
Recommendations
  • Add equivalent Linux/bash examples for certificate enrollment, provisioning, and management (e.g., using Azure CLI or REST API instead of PowerShell).
  • Clarify which steps are Windows-specific and provide guidance for Linux/macOS clusters where applicable.
  • Reference Key Vault VM extension for Linux and document any differences in behavior or configuration.
  • Include troubleshooting steps and FAQs relevant to Linux/macOS environments.
  • Where Windows-specific concepts (like S-channel or certificate linking) are discussed, explicitly state their applicability and provide alternatives or note limitations for Linux/macOS.
GitHub Create Pull Request
Service Fabric Custom Image .../articles/service-fabric/how-to-deploy-custom-image.md
Medium Priority View Details →
Scanned: 2026-02-18 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page primarily discusses deploying custom Windows images in Service Fabric Managed Clusters, with Windows terminology and PowerShell examples shown. While there are references to Linux custom image creation and Azure CLI for browsing Marketplace images, the main focus and examples are Windows-centric, and PowerShell is used for role assignment without a Linux CLI equivalent.
Recommendations
  • Provide explicit Linux-focused examples for deploying custom images, including ARM template snippets for Linux node types.
  • Add Azure CLI or Bash equivalents for role assignment commands alongside PowerShell.
  • Clarify which steps are applicable to both Windows and Linux node types, and highlight any differences.
  • Include links to Linux-specific documentation where relevant, such as custom image creation and deployment.
GitHub Create Pull Request
← Previous Page 5 of 50 Next →