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 326-350 of 2475 flagged pages
Service Fabric Learn more about Azure Service Fabric ...icles/service-fabric/service-fabric-content-roadmap.md
Medium Priority View Details →
Scanned: 2026-03-07 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation provides a broad overview of Azure Service Fabric, which supports both Windows and Linux. However, there are several instances where Windows concepts, tools, and examples are presented first or exclusively. Windows-specific tools (e.g., PowerShell, Visual Studio) are mentioned before their Linux equivalents, and some sections (such as standalone clusters) only reference Windows, with Linux support noted as unavailable. There is frequent mention of Windows executables and services (e.g., FabricHost.exe), and PowerShell is often highlighted as a management tool, with less emphasis on Linux CLI or scripting alternatives. Linux examples and tools are sometimes missing or relegated to secondary status.
Recommendations
  • Ensure that Linux equivalents (e.g., CLI commands, Bash scripts) are presented alongside PowerShell examples, not just referenced.
  • When describing cluster management, highlight Linux tools and workflows equally, and provide links to Linux-specific documentation.
  • In sections where Windows executables are discussed, clarify the Linux equivalents or note differences more prominently.
  • For standalone clusters, provide a roadmap or guidance for Linux users, even if full support is not yet available.
  • Avoid presenting Windows tools (e.g., Visual Studio, PowerShell) before Linux alternatives unless the feature is Windows-only.
  • Add explicit Linux examples and screenshots where possible, especially in 'Next steps' and quick start guides.
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-03-07 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page provides general guidance on upgrading Azure Service Fabric clusters, which are not inherently Windows-only. However, in the 'Upgrading OS images for cluster nodes' section, the only linked guidance is for patching Windows operating systems, with no mention or link to Linux equivalents. Additionally, throughout the page, PowerShell is mentioned as a tool for managing certificates and ports, but Azure CLI is also referenced, mitigating some bias. Windows-specific patching tools (Patch Orchestration Application) are discussed without Linux alternatives.
Recommendations
  • Add explicit guidance and links for upgrading Linux-based Service Fabric cluster node OS images, if supported.
  • When mentioning PowerShell, always pair with Azure CLI or Bash examples, or clarify cross-platform support.
  • If Patch Orchestration Application (POA) is Windows-only, clarify this and provide Linux alternatives or state limitations.
  • Ensure that all management actions (certificates, ports, node properties) include Linux-compatible tooling and examples.
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-07 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 shows a notable Windows bias. It references Windows Event logs, ETW, and the Windows Azure diagnostics agent as primary mechanisms for accessing Service Fabric events, without mentioning Linux equivalents or providing Linux-specific guidance. Windows tools and patterns are discussed first and exclusively, and there are no examples or instructions for accessing events on Linux-based Service Fabric clusters.
Recommendations
  • Add information about how Service Fabric events are accessed and logged on Linux clusters, including any differences in event channels, logging mechanisms, or monitoring tools.
  • Include Linux-specific examples or references (such as using syslog, journald, or other Linux logging agents) for event collection and integration with Azure Monitor.
  • Clarify which features or instructions are Windows-only, and provide parallel guidance for Linux where possible.
  • If certain event access methods are not available on Linux, explicitly state this and suggest alternative approaches.
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-07 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation provides a PowerShell-only example for reporting and evaluating application health in Service Fabric, without mentioning or demonstrating equivalent Linux/macOS methods (such as REST API, CLI, or SDK usage). The PowerShell cmdlet is presented as the primary approach, and no Linux-native tooling or cross-platform instructions are given. This creates friction for Linux/macOS users, who may not have access to PowerShell or Windows-specific cmdlets.
Recommendations
  • Add equivalent examples using REST API, Service Fabric CLI (sfctl), or SDK methods for health reporting and querying, suitable for Linux/macOS environments.
  • Explicitly mention cross-platform options (REST, sfctl, SDKs) alongside PowerShell, and clarify which tools are available on which platforms.
  • Consider presenting cross-platform examples first, or at least in parallel with Windows/PowerShell examples.
  • Link to documentation for Linux/macOS-compatible tools and APIs for Service Fabric health reporting and querying.
GitHub Create Pull Request
Service Fabric Azure Service Fabric image store connection string ...fabric/service-fabric-image-store-connection-string.md
Medium Priority View Details →
Scanned: 2026-03-07 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 PowerShell-based deployment instructions as the next step. While .NET and REST are mentioned as alternatives, PowerShell is presented first and most prominently. There are no explicit Linux/bash examples or references to Linux-native tools for these tasks.
Recommendations
  • Add examples or links for performing cluster manifest retrieval and application deployment using Linux/macOS tools (e.g., Azure CLI, bash, or REST via curl).
  • Ensure parity in documentation by providing step-by-step instructions for Linux users alongside PowerShell instructions.
  • Clarify which tools are cross-platform and which are Windows-specific, especially for deployment workflows.
  • Consider linking to Linux/macOS-specific guides or including a section for non-Windows environments.
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-07 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page on Azure Service Fabric hosting activation and deactivation life cycle is largely platform-neutral in its conceptual explanations. However, the 'Next steps' section directs users to deploy and remove applications specifically 'in PowerShell', and the only linked example for downloading a ServicePackage in advance references a PowerShell module. There are no equivalent Linux/bash examples or references to cross-platform tools, which may create friction for Linux/macOS users.
Recommendations
  • Add Linux/bash CLI examples alongside PowerShell examples for deployment and management tasks.
  • Update 'Next steps' to include links to cross-platform deployment instructions (e.g., Azure CLI, REST API, or Service Fabric CLI).
  • Where PowerShell modules are referenced, note if there are equivalent commands for Linux/macOS or clarify if the operation is Windows-only.
  • Ensure that conceptual sections remain platform-neutral, and provide parity in operational guidance.
GitHub Create Pull Request
Service Fabric Manage apps for multiple environments ...e-fabric-manage-multiple-environment-app-configuration.md
Medium Priority View Details →
Scanned: 2026-03-07 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides examples for managing application parameters in Azure Service Fabric, with a notable emphasis on PowerShell and Visual Studio workflows. PowerShell is mentioned first for application creation, and Visual Studio parameter files are discussed in detail. Linux-oriented tools (sfctl, install.sh) are referenced but receive less prominence and explanation.
Recommendations
  • Present Linux-native tools (sfctl, install.sh) before or alongside PowerShell examples to ensure equal visibility.
  • Expand explanations and examples for sfctl and install.sh usage, including sample commands and workflows for Linux/macOS users.
  • Clarify which tools are cross-platform and which are Windows-only, to help users choose appropriate options.
  • Add explicit Linux/macOS parameter file handling guidance, especially for users not using Visual Studio.
GitHub Create Pull Request
Service Fabric Azure Service Fabric container application manifest examples ...abric/service-fabric-manifest-example-container-app.md
Medium Priority View Details →
Scanned: 2026-03-07 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page provides container application manifest examples for Azure Service Fabric, but it exhibits a Windows bias. The examples are based on the 'Windows Server 2016 Container Sample', and Windows-specific tools (e.g., 'winver' command) and paths (e.g., 'c:\VolumeTest\Data') are referenced. Linux equivalents are not mentioned, and there are no explicit Linux-focused examples or guidance. While some notes acknowledge Linux (e.g., certificate handling), the overall presentation and examples are Windows-centric.
Recommendations
  • Add Linux-based manifest examples or clarify which elements differ for Linux clusters.
  • Include Linux-specific instructions for obtaining OS build/version (e.g., 'cat /etc/os-release' or 'uname -r') instead of only referencing 'winver'.
  • Provide sample container volume paths using Linux conventions (e.g., '/mnt/VolumeTest/Data') alongside Windows paths.
  • Explicitly state which features and settings are cross-platform and which are Windows-only.
  • Reference or link to Linux container samples if available.
GitHub Create Pull Request
Service Fabric Reliable services app manifest examples ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-manifest-example-reliable-services-app.md
Medium Priority View Details →
Scanned: 2026-03-07 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page provides Service Fabric manifest examples and references Windows-specific concepts and tools, such as running scripts via .bat files and mentioning the ServiceFabric PowerShell module for service creation. The examples and explanations assume Windows conventions (e.g., .exe, .bat, NETWORKSERVICE account), and do not provide Linux equivalents or guidance for Linux clusters. Windows terminology and tools are mentioned first or exclusively, creating friction for Linux users.
Recommendations
  • Add Linux-specific examples, such as using shell scripts (.sh) instead of .bat files for SetupEntryPoint and EntryPoint.
  • Mention and provide guidance for Linux Service Fabric clusters, including differences in user accounts, file permissions, and service management.
  • Include instructions for creating services using Linux CLI tools (e.g., sfctl) alongside or instead of PowerShell.
  • Clarify which manifest features and settings are cross-platform and which are Windows-only, and link to Linux-specific documentation where relevant.
  • Ensure terminology is inclusive (e.g., 'NETWORKSERVICE' vs. Linux equivalents) and explain any platform-specific concepts.
GitHub Create Pull Request
Service Fabric Networking patterns for Azure Service Fabric ...s/service-fabric/service-fabric-patterns-networking.md
Medium Priority View Details →
Scanned: 2026-03-07 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides only PowerShell-based deployment examples and references Windows-centric tools and patterns (e.g., RDP, Windows directory paths, PowerShell commands). There are no equivalent Bash/CLI examples or explicit guidance for Linux/macOS users, and Windows tools (like RDP) are mentioned before alternatives. This creates friction for non-Windows users, though the underlying Azure features are cross-platform.
Recommendations
  • Add Azure CLI (az) and Bash shell examples alongside PowerShell for all deployment steps.
  • Mention SSH as a remote access method for Linux VMs instead of only referencing RDP.
  • Use platform-neutral directory paths and command prompts (e.g., ~/ instead of C:\).
  • Explicitly note that templates and networking features are usable from any OS, and link to Linux/macOS-specific guidance where relevant.
  • Provide sample commands for Linux/macOS users to deploy ARM templates and manage networking resources.
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-07 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation provides comprehensive coverage of both Kestrel (cross-platform) and HTTP.sys (Windows-only) web servers for ASP.NET Core integration with Azure Service Fabric. However, there is a notable Windows bias in several areas: HTTP.sys (Windows-only) is described in detail and appears before Kestrel in the structure; Windows-specific tools and APIs (such as netsh and Windows HTTP Server API) are referenced without Linux equivalents; endpoint configuration examples and explanations are often tied to Windows concepts. While Kestrel is recommended for Linux and cross-platform scenarios, Windows-specific patterns and terminology are presented first and more extensively.
Recommendations
  • Reorder sections so that cross-platform Kestrel guidance appears before Windows-only HTTP.sys.
  • Explicitly call out Linux/macOS support and limitations at the start of relevant sections.
  • Provide Linux/macOS-specific troubleshooting tips or configuration advice where appropriate.
  • Clarify that HTTP.sys and related endpoint configuration steps are Windows-only, and offer alternative guidance for Linux users.
  • Add links or references to Linux/macOS development environment setup and debugging tools (e.g., VS Code, CLI).
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-07 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 API links exclusively for PowerShell usage. There is no mention of Linux/macOS equivalents, CLI usage, or cross-platform SDK approaches. This creates friction for Linux/macOS users, as Service Fabric supports Linux clusters and the APIs can be accessed via .NET SDK or REST, but only Windows/PowerShell tooling is documented.
Recommendations
  • Add examples for using the relevant APIs (Remove, Restore, Get Replica) via the Service Fabric .NET SDK, REST API, or CLI, which are cross-platform.
  • Explicitly mention how Linux/macOS users can perform replica soft delete and recovery operations, including any limitations or differences.
  • Provide sample commands or code snippets for Linux environments, such as using sfctl (Service Fabric CLI) or direct SDK calls.
  • Clarify whether the PowerShell APIs are available only on Windows, and if so, what alternatives exist for Linux clusters.
GitHub Create Pull Request
Service Fabric Add custom Service Fabric health reports ...rticles/service-fabric/service-fabric-report-health.md
Medium Priority View Details →
Scanned: 2026-03-07 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides extensive PowerShell examples for health reporting in Service Fabric, with no equivalent Linux/macOS CLI or scripting examples. Windows/PowerShell tools are mentioned first and exclusively in example sections, while REST and API options are described but not demonstrated with Linux-friendly tools. This creates friction for Linux/macOS users, who must infer or research their own methods for interacting with Service Fabric health reporting.
Recommendations
  • Add equivalent examples using Azure CLI, Bash, or curl for REST operations, demonstrating health report submission from Linux/macOS environments.
  • Clarify which PowerShell commands are cross-platform (if any) and provide guidance for Linux users if PowerShell Core is supported.
  • Explicitly mention Linux/macOS support for Service Fabric health reporting and link to relevant tools or documentation.
  • Reorder sections to present REST and API methods before or alongside PowerShell, emphasizing platform-neutral approaches.
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-03-07 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 workflows reference Windows tools, with no mention of Linux/macOS alternatives or cross-platform CLI options. Linux users are not provided with equivalent instructions or examples, creating friction for non-Windows environments.
Recommendations
  • Add instructions and examples for upgrading Service Fabric applications using Azure CLI or REST API, which are cross-platform.
  • Mention and link to any available Linux/macOS tooling for Service Fabric application management.
  • Provide parity in examples, such as showing how to configure upgrade parameters and health policies using non-Windows tools.
  • Clarify which steps are Windows-only and offer alternatives for Linux/macOS users where possible.
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-07 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is strongly oriented toward Windows development workflows, specifically Visual Studio, with repeated references to Windows-centric tools and patterns (e.g., F5/Ctrl+F5/Publish, Visual Studio UI, PowerShell module). There are no examples or guidance for Linux/macOS users, nor any mention of cross-platform alternatives for developing or deploying Service Fabric applications. The page assumes the use of Visual Studio and Windows, omitting CLI or non-Windows tooling.
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 other cross-platform tools for creating and deploying Service Fabric applications.
  • Clarify which features are Visual Studio/Windows-only and suggest alternative workflows for non-Windows environments.
  • Include sample workflows for editing and deploying ApplicationManifest.xml and StartupServices.xml using command-line tools or editors available on Linux/macOS.
GitHub Create Pull Request
Service Fabric Fault Analysis Service overview .../service-fabric/service-fabric-testability-overview.md
Medium Priority View Details →
Scanned: 2026-03-07 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides explicit instructions for using the Fault Analysis Service with PowerShell and C#, but does not mention or provide examples for Linux/macOS users (e.g., Bash/CLI, REST API, or cross-platform SDK usage). The PowerShell instructions assume a Windows environment, and there is no guidance for equivalent operations on Linux or macOS.
Recommendations
  • Add examples or instructions for using the Fault Analysis Service from Linux/macOS environments, such as via Azure CLI, Bash scripts, or REST API.
  • Clarify whether the PowerShell module or SDK is available and supported on non-Windows platforms, or provide alternatives if not.
  • Include cross-platform C#/.NET Core examples if applicable, and note any platform-specific limitations.
  • Explicitly state if certain features are Windows-only, to set expectations for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Deploy and upgrade with Azure Resource Manager ...vice-fabric/service-fabric-application-arm-resource.md
Medium Priority View Details →
Scanned: 2026-03-06 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 removing Service Fabric application resources and refers to PowerShell before CLI in the 'Next steps' section. There are no equivalent CLI or cross-platform examples for Linux/macOS users, which may create friction for those not using Windows.
Recommendations
  • Add Azure CLI examples alongside PowerShell for resource removal and management tasks.
  • Explicitly mention that REST API calls can be made using tools like curl or HTTPie, and provide example commands.
  • In 'Next steps', list CLI and PowerShell together or in alternating order to avoid Windows-first bias.
  • Where possible, clarify which tools are cross-platform and recommend them for non-Windows users.
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-06 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page provides some Windows-centric examples and references, such as Windows-style file paths (e.g., 'D:\\SvcFab'), mentions of RDP port changes, and PowerShell scripts for post-deployment tasks. While the Service Fabric extension supports both Linux and Windows nodes, the examples and 'Next steps' links focus on Windows tools and workflows, with no Linux-specific guidance or parity in examples.
Recommendations
  • Provide Linux/Unix-style path examples (e.g., '/var/lib/servicefabric') alongside Windows paths in the extension snippet.
  • Include Linux-specific instructions or references for remote connection (e.g., using SSH) in the 'Next steps' section.
  • Add links or scripts for managing Linux VMs (e.g., changing SSH port, updating Linux admin users) similar to the PowerShell/RDP-focused scripts for Windows.
  • Clarify in the documentation when a step or example is Windows-only, and offer Linux alternatives where possible.
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-06 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page primarily references Windows-centric tools and workflows, such as Visual Studio and PowerShell, in the 'Next steps' section. These are presented before any Linux/macOS alternatives, and no Linux-native upgrade examples (e.g., CLI or Bash) are provided. The serialization guidance is focused on C#/.NET, which is cross-platform, but the upgrade tooling references are Windows-biased.
Recommendations
  • Add equivalent Linux/macOS upgrade walkthroughs using Azure CLI or Service Fabric CLI (sfctl), and reference them alongside PowerShell and Visual Studio.
  • Mention cross-platform development environments (e.g., VS Code, JetBrains Rider) for application upgrades.
  • Ensure that upgrade tutorials and troubleshooting guides include Linux/macOS-compatible commands and examples.
  • Clarify which tools are Windows-only and provide links to Linux/macOS alternatives where available.
GitHub Create Pull Request
Service Fabric Deny assignment policy for Service Fabric managed clusters ...cles/service-fabric/managed-cluster-deny-assignment.md
Medium Priority View Details →
Scanned: 2026-03-06 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides examples and links primarily for Azure PowerShell modules when describing best practices for managing Service Fabric managed clusters. PowerShell is a Windows-centric tool, and its mention precedes Azure CLI and other cross-platform tools. While Azure CLI and ARM/Bicep templates are referenced, the PowerShell examples are highlighted first and in more detail, which may create friction for Linux/macOS users.
Recommendations
  • Provide equivalent Azure CLI examples alongside PowerShell examples for all recommended actions (e.g., deleting NodeTypes, restarting/reimaging scale sets).
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Consider listing Azure CLI examples before PowerShell examples, or presenting both together.
  • Add links to relevant Azure CLI documentation for Service Fabric managed clusters.
  • Clarify that PowerShell is available cross-platform, but CLI may be more familiar to Linux/macOS users.
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-06 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 Infrastructure Service, and references Service Fabric Explorer (a GUI tool typically used on Windows). No Linux or cross-platform CLI alternatives are mentioned, and Windows-centric patterns (PowerShell cmdlets) are presented without Linux parity.
Recommendations
  • Add equivalent Linux/macOS command-line examples using Azure CLI or REST API, if available.
  • Clarify whether the PowerShell cmdlet is supported on Linux (via PowerShell Core), or provide alternatives.
  • Mention cross-platform tools or interfaces (e.g., Azure Portal, Azure CLI) where possible.
  • If Service Fabric Explorer is Windows-only, recommend any web-based or cross-platform alternatives.
GitHub Create Pull Request
Service Fabric Azure Service Fabric networking best practices ...ice-fabric/service-fabric-best-practices-networking.md
Medium Priority View Details →
Scanned: 2026-03-06 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 provides both Windows and Linux guidance for Service Fabric networking, but there are several instances of Windows bias. Windows/PowerShell examples and terminology are mentioned first or exclusively (e.g., client API used by PowerShell, classic PowerShell tasks in Azure DevOps, Windows container-specific guidance). Some example links and templates are Windows-focused, and Linux-specific examples or CLI equivalents are less prominent or missing. While Linux is referenced, Windows patterns and tools are often prioritized.
Recommendations
  • Ensure Linux CLI (az, bash) examples are provided alongside PowerShell examples, especially for cluster management and networking tasks.
  • When referencing ARM templates or sample clusters, include both Windows and Linux templates, or clarify applicability.
  • Mention Linux-specific networking considerations and tools (e.g., firewall, port management) where relevant.
  • Balance the order of Windows and Linux guidance so Linux is not always secondary.
  • Clarify when guidance is Windows-only and provide Linux alternatives or links where possible.
GitHub Create Pull Request
Service Fabric Service Fabric Explorer blocking operations ...ged-cluster-service-fabric-explorer-blocking-operation.md
Medium Priority View Details →
Scanned: 2026-03-06 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page primarily references Az PowerShell cmdlets for managing Service Fabric resources, with explicit links to PowerShell modules. While it mentions 'az resource' for deleting applications, PowerShell examples and terminology are more prominent and appear first. There are no explicit Linux/macOS CLI examples or references to Bash, nor is there guidance for users on non-Windows platforms.
Recommendations
  • Add equivalent Azure CLI (az) commands for all management operations, not just deletions.
  • Provide examples for Bash or cross-platform usage, highlighting that Azure CLI works on Linux/macOS.
  • Clarify when PowerShell is required and when Azure CLI can be used, to help users on non-Windows systems.
  • Consider listing Azure CLI examples before or alongside PowerShell examples for parity.
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-06 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily focused on PowerShell-based workflows, with all CLI examples and module instructions using PowerShell. There are no examples or guidance for Linux/macOS users, such as using Azure CLI, curl, or other cross-platform tools to interact with the REST API. The prerequisite section assumes PowerShell usage and does not mention alternatives for non-Windows environments.
Recommendations
  • Add equivalent examples using Azure CLI or curl for REST API calls, suitable for Linux/macOS users.
  • Mention cross-platform tools and workflows in the prerequisites, such as Azure CLI or REST clients.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is required only for Windows/PowerShell users, and provide alternatives for other platforms.
  • Reorder sections or provide parallel examples so Linux/macOS users are not forced to translate PowerShell scripts.
  • Explicitly state platform requirements if certain steps are Windows-only, and link to Linux/macOS guidance where available.
GitHub Create Pull Request
Service Fabric Scalability of Service Fabric services .../service-fabric/service-fabric-concepts-scalability.md
Medium Priority View Details →
Scanned: 2026-03-06 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides code examples and administrative patterns primarily using PowerShell, which is a Windows-centric tool. No Linux command-line equivalents (such as Bash, CLI, or REST API) are provided for scaling operations. Windows/PowerShell examples are shown first and exclusively, creating friction for Linux users who may need to perform similar tasks. The only explicit Linux mention is in the 'Choosing a platform' section, which discusses implementation differences but does not provide Linux-specific operational guidance.
Recommendations
  • Add equivalent Linux command-line examples using Bash, Azure CLI, or REST API for scaling operations (e.g., creating/removing services, updating instance counts).
  • Mention and link to Linux-specific Service Fabric management tools or documentation where applicable.
  • Where PowerShell is referenced, clarify if the operation can be performed via cross-platform tools and provide those alternatives.
  • Ensure examples and administrative patterns are presented for both Windows and Linux, or note any limitations for Linux users.
GitHub Create Pull Request
← Previous Page 14 of 99 Next →