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 1026-1050 of 2475 flagged pages
Service Fabric Service communication with the ASP.NET Core ...vice-fabric-reliable-services-communication-aspnetcore.md
Medium Priority View Details →
Scanned: 2026-02-22 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation provides thorough coverage of both Kestrel (cross-platform) and HTTP.sys (Windows-only) web servers for ASP.NET Core in Azure Service Fabric. However, Windows-specific tools and APIs (e.g., HTTP.sys, netsh, Windows HTTP Server API) are discussed in detail, often before or alongside Kestrel. HTTP.sys usage is described with explicit notes about Windows-only support, but Linux/macOS equivalents or considerations are not mentioned. Examples and endpoint configuration instructions reference Windows tools (netsh) and concepts, and there are no explicit Linux/macOS setup or troubleshooting examples. Kestrel is correctly positioned as the preferred cross-platform option, but Windows-specific patterns and tools are given significant space and are sometimes discussed first.
Recommendations
  • Add explicit Linux/macOS instructions or troubleshooting notes for Service Fabric and ASP.NET Core hosting, especially for endpoint configuration and port management.
  • Include example workflows or code snippets for Linux/macOS environments, such as how to configure firewall rules or manage ports without Windows tools like netsh.
  • Clarify that Kestrel is the only supported web server for Linux/macOS, and provide guidance for Linux users on avoiding Windows-only features.
  • Reorder sections to present cross-platform (Kestrel) options before Windows-only (HTTP.sys) options, emphasizing Linux/macOS parity.
  • Add a summary table or section highlighting platform support for each web server and feature.
GitHub Create Pull Request
Service Fabric Reliable Collection object serialization ...c-reliable-services-reliable-collections-serialization.md
Medium Priority View Details →
Scanned: 2026-02-22 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides code examples and references that are platform-neutral (C#), but in the 'Next steps' section, Windows-centric tools (Visual Studio and PowerShell) are mentioned for application upgrades, with PowerShell specifically called out. There are no Linux/macOS equivalents (such as CLI or Bash) referenced alongside these tools, which may create friction for non-Windows users.
Recommendations
  • Add links or references to Linux/macOS-compatible upgrade methods, such as using Azure CLI or Bash scripts, if available.
  • Clarify whether the PowerShell and Visual Studio tutorials are Windows-only, and provide alternative instructions for Linux/macOS users if possible.
  • Consider mentioning cross-platform tools earlier or alongside Windows tools to ensure parity.
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-22 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 examples for PowerShell commands and usage, which are Windows-centric, and presents these before mentioning REST or API alternatives. There are no equivalent Linux/bash CLI examples or references to cross-platform tools. The PowerShell examples are extensive and shown first, while REST is only briefly mentioned and lacks concrete examples. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer bash/CLI workflows.
Recommendations
  • Add equivalent bash or Azure CLI examples for sending health reports and querying health status.
  • Explicitly mention cross-platform alternatives to PowerShell, such as Azure CLI or REST, and provide concrete examples.
  • Clarify which tools are available on Linux/macOS and how to perform the same tasks without PowerShell.
  • Consider reorganizing the examples so REST or cross-platform approaches are presented before or alongside PowerShell.
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-22 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 Windows-centric. The Service Fabric schema path is given only for Windows. Linux-specific deployment instructions and CLI examples are missing or less prominent, though there is a brief mention of the Linux certificate store location.
Recommendations
  • Add equivalent Linux/macOS deployment examples using Azure CLI or Service Fabric CLI (sfctl), especially for application deployment and parameter overrides.
  • Mention the schema location for Linux installations, or clarify if it is not applicable.
  • Ensure that Linux-specific instructions (such as certificate handling, endpoint configuration, and port ACLing) are as detailed as Windows instructions.
  • Where PowerShell is used, provide alternative commands for Linux/macOS users.
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-22 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on Visual Studio workflows and Windows-centric tooling. All deployment and configuration examples reference Visual Studio features (Build/Rebuild/F5/Ctrl+F5/Publish), which are Windows-only. There are no Linux/macOS equivalents or guidance for cross-platform development, and the only alternative deployment methods mentioned are ARM templates and PowerShell cmdlets, both referenced after Visual Studio. No CLI or Linux-native tools are discussed, and all screenshots and instructions assume Windows environments.
Recommendations
  • Add explicit guidance for Linux/macOS users, including how to manage StartupServices.xml outside Visual Studio.
  • Provide examples using Azure CLI, Service Fabric CLI (sfctl), or other cross-platform tools for deployment and configuration.
  • Clarify which features are Visual Studio/Windows-only and offer alternative workflows for Linux/macOS users.
  • Include sample workflows for editing and deploying StartupServices.xml from non-Windows environments.
  • Mention any limitations or unsupported scenarios for Linux/macOS users up front.
GitHub Create Pull Request
Service Fabric Fault Analysis Service overview .../service-fabric/service-fabric-testability-overview.md
Medium Priority View Details →
Scanned: 2026-02-22 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 usage instructions for the Fault Analysis Service in Service Fabric, with explicit PowerShell guidance and references to the Service Fabric SDK and PowerShell module. There are no Linux/macOS CLI or scripting examples (such as Bash or Azure CLI), nor is there mention of Linux-specific tools or workflows. The focus on PowerShell and Windows SDK tools creates friction for Linux/macOS users, who may need to find alternative methods or tools.
Recommendations
  • Add examples for using the Fault Analysis Service via Azure CLI or Bash scripts, if supported.
  • Clarify whether the Fault Analysis Service APIs can be accessed from Linux/macOS environments, and provide guidance for those platforms.
  • Mention any cross-platform SDKs or tools (such as .NET Core, REST APIs) that can be used from Linux/macOS.
  • If PowerShell is required, note the availability of PowerShell Core on Linux/macOS and provide installation instructions.
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-22 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-centric tools, specifically Visual Studio and PowerShell, for configuring and upgrading Service Fabric applications. All examples and upgrade instructions reference Visual Studio dialogs and PowerShell cmdlets, with no mention of Linux/macOS alternatives or cross-platform CLI tools. The page does not provide guidance for users on Linux or macOS, nor does it reference Azure CLI or REST API options for application upgrades.
Recommendations
  • Add instructions or links for upgrading Service Fabric applications using Azure CLI or REST API, which are cross-platform.
  • Include examples for configuring upgrade parameters and health policies using Linux/macOS-compatible tools.
  • Clarify whether Visual Studio and PowerShell are required, or if alternative workflows exist for non-Windows environments.
  • Mention any limitations or required workarounds for Linux/macOS users, if applicable.
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-02-22 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides a PowerShell-only example for bypassing the Infrastructure Service, and references Service Fabric Explorer (a GUI tool typically used on Windows). There are no Linux CLI or cross-platform alternatives mentioned for these operations, and Windows tools/patterns are presented first and exclusively.
Recommendations
  • Add equivalent Linux/macOS command-line examples, such as using Azure CLI or REST API if available.
  • Clarify whether the PowerShell command can be run from PowerShell Core on Linux/macOS, or provide Bash alternatives.
  • Mention cross-platform access to Service Fabric Explorer or alternatives for Linux users.
  • Explicitly state platform requirements for any commands or tools, and provide guidance for Linux/macOS users where possible.
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-22 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page for the Azure Service Fabric application resource model exhibits notable Windows bias. All deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) without any equivalent Azure CLI or Bash examples. The application packaging step references Visual Studio, a Windows-centric tool, and does not mention cross-platform alternatives. There are no Linux/macOS-specific instructions or examples, and Windows tools are presented as the default approach.
Recommendations
  • Add Azure CLI examples for deployment and deletion tasks alongside PowerShell examples.
  • Include instructions for packaging applications using cross-platform tools (such as dotnet CLI or sfpkg command-line utility) instead of only Visual Studio.
  • Provide guidance for Linux/macOS users on uploading application packages to Azure Blob Storage (e.g., using az storage blob upload).
  • Ensure screenshots and walkthroughs are not exclusively tied to Windows tools or interfaces.
  • Mention that all steps can be completed on Linux/macOS and provide links to relevant cross-platform documentation.
GitHub Create Pull Request
Service Fabric Configure or modify a Service Fabric managed cluster node type ...vice-fabric/how-to-managed-cluster-modify-node-type.md
Medium Priority View Details →
Scanned: 2026-02-22 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides examples for managing Service Fabric managed cluster node types using the Azure Portal, ARM templates, and PowerShell. However, all CLI/scripted examples are exclusively in PowerShell, with no mention of Azure CLI (az), Bash, or cross-platform scripting alternatives. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer using the Azure CLI.
Recommendations
  • Add Azure CLI (az) command examples alongside PowerShell for all relevant operations (add, remove, scale, configure node types).
  • Explicitly mention that PowerShell examples require Azure PowerShell module and may not be available on all platforms.
  • Where possible, provide Bash or cross-platform scripting guidance, or link to Azure CLI documentation.
  • Clarify if any operations are only possible with PowerShell and explain why, or provide workarounds for non-Windows users.
GitHub Create Pull Request
Service Fabric Monitor Azure Service Fabric ...main/articles/service-fabric/monitor-service-fabric.md
Medium Priority View Details →
Scanned: 2026-02-22 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation covers monitoring Azure Service Fabric clusters on both Windows and Linux, but there are several areas where Windows tools and examples are mentioned first or exclusively. Windows-specific tools (e.g., Event Log, Event Viewer, Diagnostics Agent) are referenced before or more prominently than Linux equivalents. Some sections lack Linux-specific examples or guidance, and Windows terminology (ETW, EventSource) is used without always providing Linux alternatives (LTTng, Syslog). However, Linux support is acknowledged and most monitoring approaches are described as cross-platform.
Recommendations
  • Ensure Linux-specific tools and workflows (e.g., LTTng, Syslog, Linux agent configuration) are described with equal prominence and detail as Windows tools.
  • Provide Linux-focused examples and tutorials alongside Windows ones, especially for cluster monitoring, event access, and agent setup.
  • When referencing Windows tools (Event Viewer, Diagnostics Agent), immediately mention the Linux equivalents and link to relevant Linux documentation.
  • Clarify which features are Windows-only (e.g., EventStore APIs) and provide alternative solutions or workarounds for Linux users.
  • Add sample code or configuration snippets for Linux environments where only Windows examples are currently given.
GitHub Create Pull Request
Service Fabric Understanding periodic backup configuration ...-fabric-backuprestoreservice-configure-periodic-backup.md
Medium Priority View Details →
Scanned: 2026-02-22 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page is generally platform-neutral regarding Azure Service Fabric periodic backup configuration, but there is a notable bias in the 'File share' backup storage section. Only Windows-style UNC paths (\\StorageServer\BackupStore) and Windows authentication methods are described, with no mention of Linux-compatible file share paths (e.g., SMB mounts on Linux) or authentication options. Additionally, Windows authentication is discussed first and in more detail, while Linux alternatives are absent.
Recommendations
  • Add examples and guidance for configuring file share backup storage using Linux-compatible paths and authentication methods (e.g., mounting SMB shares on Linux, using CIFS, specifying credentials).
  • Clarify whether Linux clusters can use file share backup storage and provide any relevant limitations or instructions.
  • Where authentication options are discussed, mention Linux equivalents or note if only Windows authentication is supported.
  • Consider including a note about cross-platform compatibility for backup storage options, especially for standalone clusters.
GitHub Create Pull Request
Service Fabric Azure Service Fabric security best practices ...rvice-fabric/service-fabric-best-practices-security.md
Medium Priority View Details →
Scanned: 2026-02-22 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Windows and Linux guidance for key security tasks, but Windows examples and tools (such as PowerShell and Windows Defender) are often presented first or exclusively. Windows-specific recommendations (e.g., security baselines, Defender, DSC) are highlighted, while Linux equivalents are not mentioned or are less detailed. Some sections (like Windows Defender) are Windows-only, but this is acknowledged. Overall, Linux users can complete the tasks, but may experience friction due to Windows-first presentation and lack of Linux-specific tooling recommendations.
Recommendations
  • Ensure Linux examples are presented alongside Windows examples, not after them.
  • Provide Linux-specific security baseline recommendations (e.g., CIS benchmarks, OS hardening guides) where Windows baselines are mentioned.
  • Mention Linux antimalware solutions or clarify best practices for Linux security in relevant sections.
  • Where PowerShell is used for Windows, provide equivalent Bash or CLI commands for Linux.
  • Explicitly note when a feature or tool is Windows-only, and offer Linux alternatives or guidance where possible.
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-02-22 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides general guidance on Azure Service Fabric node types and VM scale sets, referencing both Windows and Linux node types in the extension snippet. However, there is a subtle Windows bias: the JSON example uses a Windows-style file path ('D:\\SvcFab') for the 'dataPath' property, and the 'Next steps' section links to PowerShell scripts for RDP port and admin credential changes, which are Windows-specific tasks. No equivalent Linux examples or guidance are provided, and Windows patterns (such as RDP and file paths) are mentioned first or exclusively.
Recommendations
  • Provide Linux-specific examples for the 'dataPath' property (e.g., '/var/svcfab') alongside the Windows path.
  • Add guidance or links for SSH access and Linux admin credential changes, mirroring the Windows RDP/PowerShell examples.
  • Clarify which steps or scripts are Windows-only and offer Linux alternatives where possible.
  • Ensure that examples and property descriptions are OS-neutral or include both Windows and Linux variants.
GitHub Create Pull Request
Service Fabric Describe a cluster by using Cluster Resource Manager ...ce-fabric-cluster-resource-manager-cluster-description.md
Medium Priority View Details →
Scanned: 2026-02-22 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation provides configuration examples for both Windows (ClusterManifest.xml) and cross-platform/standalone (ClusterConfig.json) deployments. However, Windows-specific configuration (ClusterManifest.xml with <WindowsServer>) is presented first and more prominently, and PowerShell examples are included for service creation and updates, with no equivalent Linux shell or CLI examples. The documentation refers to WindowsServer as the infrastructure type in the XML example, which may imply Windows bias, but also includes JSON examples suitable for Linux/standalone clusters. No explicit Linux/macOS examples or tools (such as Bash, Azure CLI, or Linux-specific guidance) are provided.
Recommendations
  • Add explicit Linux/Unix/macOS configuration examples, such as referencing <Linux> infrastructure in ClusterManifest.xml or providing guidance for Linux node setup.
  • Include Azure CLI or Bash examples for service creation and updates alongside PowerShell and C#.
  • Clarify that ClusterConfig.json is suitable for Linux/standalone deployments and provide links or references to Linux-specific Service Fabric documentation.
  • Balance the order of examples so that Linux/cross-platform options are presented equally or before Windows-specific ones.
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-22 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation generally avoids OS-specific instructions, but in the 'Upgrading OS images for cluster nodes' section, it explicitly links only to Windows patching guidance and references Patch Orchestration Application (POA) as a Windows solution. There are no equivalent Linux instructions or links, and the section title does not clarify that it is Windows-only. Additionally, PowerShell and Azure CLI are mentioned together for some tasks, but no Linux-specific tools or examples are provided, and Windows patching is discussed before any mention of Linux.
Recommendations
  • Add a parallel section or link for upgrading OS images on Linux-based Service Fabric clusters, if supported.
  • Clarify in the 'Upgrading OS images for cluster nodes' section title or body that the linked guidance is Windows-specific, and provide Linux guidance or a statement if Linux is not supported.
  • Where PowerShell/Azure CLI are mentioned, ensure Linux users are explicitly addressed (e.g., provide Bash/Azure CLI examples or clarify cross-platform support).
  • Review for any other OS-specific tools or patterns and ensure Linux parity or clear labeling.
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-22 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page on Azure Service Fabric Events primarily references Windows-centric logging mechanisms (ETW/Windows Event logs, Windows Azure diagnostics agent) and monitoring tools. There are no explicit Linux/macOS equivalents or examples provided, nor is there guidance for accessing Service Fabric events from Linux-based clusters. The Windows tools and patterns are mentioned first and exclusively, creating friction for Linux users.
Recommendations
  • Add documentation and examples 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 tools, if available, and provide configuration guidance.
  • Clarify which event access methods are cross-platform (such as EventStore REST APIs) and highlight their use for Linux/macOS users.
  • Where possible, provide parity in examples and tool references for both Windows and Linux environments.
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-22 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides PowerShell examples for setting DNS names but does not offer equivalent Linux CLI or bash examples. Windows-centric tools (PowerShell, Visual Studio) are mentioned for service configuration, while Linux alternatives are not. The limitations section notes Linux support is restricted, but the overall guidance and examples are Windows-first, creating friction for Linux users.
Recommendations
  • Add Linux CLI/bash examples for configuring DNS names, such as using Azure CLI or REST API.
  • Mention cross-platform editors (e.g., VS Code) alongside Visual Studio for editing ApplicationManifest.xml.
  • Clarify how Linux users can enable DNS service (e.g., via ARM templates or CLI) and highlight any differences.
  • Provide explicit guidance or links for Linux users to complete tasks that are shown with PowerShell for Windows.
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-22 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page references PowerShell as the primary example for interacting with Service Fabric clusters (e.g., retrieving the cluster manifest), and links to a PowerShell-based deployment article as the next step. While .NET and REST are mentioned, PowerShell is presented first and most prominently. There are no explicit Linux/macOS CLI or tooling examples (such as Azure CLI, Bash, or cross-platform scripts), and the workflow assumes Visual Studio for publishing, which is Windows-centric.
Recommendations
  • Add examples using Azure CLI or Bash scripts for retrieving cluster manifests and deploying applications, highlighting cross-platform approaches.
  • Include references to cross-platform tools (e.g., Service Fabric CLI, sfctl) and document their usage for Linux/macOS users.
  • Balance the order of examples so that PowerShell is not always presented first; alternate with cross-platform or Linux-native tools.
  • Clarify that Visual Studio is Windows-centric and suggest alternatives for Linux/macOS users (e.g., VS Code, command-line tools).
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-22 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. There are several indications of Windows bias: (1) Windows terminology and tools are referenced first or exclusively, such as 'ServiceFabric PowerShell module' for service creation, (2) examples use Windows-style batch scripts (Setup.bat) and executables (.exe), (3) security principals reference Windows system groups (Administrators, NetworkService), and (4) domain account support is noted as Windows-only. There are no explicit Linux or cross-platform examples, and Linux-specific guidance is missing.
Recommendations
  • Add examples using Linux shell scripts (e.g., Setup.sh) and non-.exe binaries to demonstrate cross-platform deployment.
  • Mention and provide examples for using Service Fabric CLI (sfctl) or REST API for service management, which are cross-platform, instead of only referencing PowerShell.
  • Clarify which security principal concepts (users, groups) are supported on Linux clusters and provide Linux-specific guidance.
  • Explicitly note any manifest settings or patterns that differ between Windows and Linux clusters, and link to relevant Linux documentation.
  • Where possible, show both Windows and Linux approaches side-by-side in manifest and operational examples.
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-22 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page for Replica Soft Delete in Service Fabric heavily references PowerShell APIs (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica) and provides examples and links exclusively to PowerShell cmdlets. There are no examples or explicit instructions for Linux/macOS users, such as using the Service Fabric CLI (sfctl) or REST APIs, even though Service Fabric supports cross-platform management. The documentation assumes Windows tooling and does not mention Linux equivalents or alternative workflows.
Recommendations
  • Add examples using sfctl (Service Fabric CLI) for Linux/macOS users, showing how to remove, restore, and query replicas.
  • Mention REST API endpoints or FabricClient SDK usage for cross-platform scenarios.
  • Clarify whether the PowerShell APIs are available only on Windows, and provide guidance for Linux users if not.
  • Include a section or note explicitly addressing Linux/macOS management options for replica soft delete operations.
GitHub Create Pull Request
Service Fabric Initializer CodePackages in Service Fabric ...in/articles/service-fabric/initializer-codepackages.md
Medium Priority View Details →
Scanned: 2026-02-21 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 presents only Windows container examples, exclusively references Windows container images (nanoserver:1809), uses Windows file paths and commands (cmd, C:\ paths), and does not mention or provide examples for Linux containers or Linux file systems. The ApplicationManifest and ServiceManifest examples are Windows-centric, and the workflow assumes Windows containers and tooling. There is no guidance for Linux container scenarios, nor any mention of cross-platform support.
Recommendations
  • Add examples using Linux container images (e.g., Ubuntu, Alpine) and Linux file paths.
  • Provide equivalent Linux shell commands (e.g., bash, sh) for initialization steps.
  • Clarify whether Initializer CodePackages are supported for Linux containers in Service Fabric, and if so, provide guidance and examples.
  • Mention any platform limitations explicitly (e.g., if Initializer CodePackages are Windows-only, state this clearly).
  • Ensure volume mounts and file operations are shown for both Windows and Linux container scenarios.
GitHub Create Pull Request
Service Fabric Service Fabric application upgrade ...s/service-fabric/service-fabric-application-upgrade.md
Medium Priority View Details →
Scanned: 2026-02-21 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 Service Fabric application upgrade exhibits notable Windows bias. All code examples are provided exclusively in PowerShell, a Windows-centric tool. References to Service Fabric PowerShell cmdlets and Windows HTTP Server API (http.sys) are made without Linux equivalents or guidance. There are no examples or instructions for Linux/macOS users, and Windows tools are mentioned first and exclusively throughout the page.
Recommendations
  • Add equivalent CLI examples using Azure CLI or Service Fabric CLI (sfctl), which are cross-platform.
  • Provide guidance for Linux/macOS users, including how to perform upgrades and manage application parameters on non-Windows platforms.
  • Mention Linux-specific considerations, such as how HTTPS endpoints and certificate management differ from Windows (http.sys).
  • Ensure that references to PowerShell are accompanied by alternative commands or links for Linux/macOS users.
  • Clarify which features or steps are Windows-only and provide alternatives or workarounds for Linux clusters.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager - Application Groups ...ice-fabric-cluster-resource-manager-application-groups.md
Medium Priority View Details →
Scanned: 2026-02-21 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation consistently provides PowerShell examples for all key operations (creating, updating, querying, and removing application groups/capacity), but does not offer equivalent Linux/macOS CLI examples (such as Azure CLI, Bash, or REST API). PowerShell is primarily a Windows tool, and its exclusive use creates friction for Linux/macOS users. There is no mention of cross-platform tools or alternative command-line methods.
Recommendations
  • Add Azure CLI examples for all operations shown in PowerShell, if supported.
  • Mention REST API endpoints or provide sample requests for relevant actions.
  • Clarify whether PowerShell cmdlets are available cross-platform (e.g., via PowerShell Core), and provide guidance for Linux/macOS users.
  • If PowerShell is the only supported method, explicitly state this limitation and link to any available cross-platform alternatives or workarounds.
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-21 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides PowerShell examples for configuring move cost, but omits equivalent Linux CLI or bash examples. PowerShell is presented first, followed by C#, with no mention of Linux-native tools or cross-platform command-line alternatives. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other scripting environments.
Recommendations
  • Add Azure CLI or bash examples for configuring move cost, especially for service creation and updates.
  • Clarify whether PowerShell commands can be run cross-platform (e.g., via PowerShell Core), or provide guidance for Linux/macOS users.
  • Consider presenting examples in a platform-neutral order, or explicitly state platform requirements for each example.
  • Mention any REST API or SDK alternatives that are platform-agnostic.
GitHub Create Pull Request
← Previous Page 42 of 99 Next →