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 726-750 of 2475 flagged pages
Service Fabric Azure Service Fabric dynamic node tags ...tps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-node-tagging.md
Medium Priority View Details →
Scanned: 2026-02-28 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides PowerShell examples for managing node tags and service requirements, but does not include equivalent Linux/macOS CLI (e.g., Bash, Azure CLI) or cross-platform REST API examples. PowerShell is primarily a Windows tool, and its prominence creates friction for Linux/macOS users who may not have access to PowerShell or prefer other tools.
Recommendations
  • Add examples using Azure CLI or REST API for managing node tags and service requirements, as these are cross-platform and accessible from Linux/macOS.
  • Explicitly mention whether PowerShell cmdlets are available on Linux/macOS, or provide guidance for Linux users (e.g., using PowerShell Core, if supported).
  • Include Bash or shell script examples where possible, or clarify if only PowerShell is supported.
  • Ensure REST API documentation is referenced and linked for users on non-Windows platforms.
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-28 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 scaling Azure Service Fabric standalone clusters demonstrates a Windows bias. It references PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) without providing equivalent Linux or cross-platform CLI examples. The linked 'scale a standalone cluster' documentation appears to be Windows Server-focused, and there is no mention of Linux tooling or procedures for scaling standalone clusters, despite Service Fabric supporting Linux nodes.
Recommendations
  • Add examples using Service Fabric CLI (sfctl) or REST APIs for cluster scaling, which are cross-platform.
  • Explicitly mention whether standalone cluster scaling is supported on Linux, and provide guidance or links for Linux-based clusters.
  • If PowerShell is required, clarify whether PowerShell Core (cross-platform) is supported, or provide Bash/Linux shell alternatives.
  • Ensure linked documentation (e.g., 'scale a standalone cluster') covers Linux scenarios or clearly states if only Windows is supported.
GitHub Create Pull Request
Service Fabric Secure an Azure Service Fabric cluster ...cles/service-fabric/service-fabric-cluster-security.md
Medium Priority View Details →
Scanned: 2026-02-28 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 securing an Azure Service Fabric cluster exhibits moderate Windows bias. Windows Server clusters and Windows security mechanisms (Kerberos, Windows accounts, group Managed Service Accounts) are mentioned prominently and often before Linux equivalents. References to certificate creation tools and best practices are Windows-centric (e.g., MakeCert.exe, Windows Server certificate service). There is a lack of explicit Linux example links or guidance for standalone Linux clusters, and Linux-specific certificate management or authentication patterns are not discussed. The concept of Linux clusters is acknowledged, but practical instructions and parity are missing.
Recommendations
  • Add explicit guidance and links for securing standalone Linux Service Fabric clusters, including certificate creation and management using Linux tools (e.g., OpenSSL).
  • Provide Linux-specific examples for node-to-node and client-to-node security setup, including configuration templates and authentication mechanisms.
  • Mention Linux certificate authorities and tools alongside Windows Server certificate service.
  • Ensure parity in recommendations for production certificate creation and management for Linux environments.
  • Clarify which instructions are applicable to both Windows and Linux, and highlight any differences.
GitHub Create Pull Request
Service Fabric Upgrade an Azure Service Fabric standalone cluster ...ce-fabric/service-fabric-cluster-upgrade-standalone.md
Medium Priority View Details →
Scanned: 2026-02-28 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page references Windows-specific upgrade and configuration guides (e.g., 'service-fabric-cluster-upgrade-windows-server.md', 'service-fabric-cluster-config-upgrade-windows-server.md') and the Patch Orchestration Application for Windows. There are no explicit Linux examples or links to Linux-specific upgrade/configuration documentation, despite Service Fabric standalone clusters supporting Linux nodes.
Recommendations
  • Add links to Linux-specific upgrade and configuration documentation where available.
  • Provide examples or instructions for Linux clusters, such as how to patch Linux nodes or upgrade Service Fabric on Linux.
  • Clarify when a feature or tool is Windows-only, and offer Linux alternatives or note limitations.
  • Ensure parity in documentation structure and guidance for both Windows and Linux users.
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-28 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides general guidance for upgrading Azure Service Fabric clusters but exhibits some Windows bias. Windows-specific tools (PowerShell) are mentioned alongside Azure CLI, but Linux equivalents (such as Bash or Linux-specific guidance) are not explicitly referenced. The section on OS image upgrades links only to Windows patching guidance, with no mention of Linux node patching. Windows terminology and tools are sometimes mentioned first or exclusively, and Linux/macOS users may need to infer their own workflows.
Recommendations
  • Explicitly mention Linux/macOS support where applicable, especially for cluster management and upgrades.
  • Provide Linux-specific examples or clarify when Azure CLI commands are cross-platform.
  • Add links or sections for patching Linux-based Service Fabric clusters, if supported.
  • Ensure that references to PowerShell are balanced with Bash or Azure CLI examples, and clarify tool parity.
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-28 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 exhibits several Windows biases: all deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) without any Azure CLI or Linux/macOS alternatives; Visual Studio is referenced for packaging the sample application, with no mention of cross-platform tools; and Windows file paths and patterns are used throughout. No Linux/macOS-specific guidance or parity is provided, creating friction for non-Windows users.
Recommendations
  • Add Azure CLI examples for deployment and deletion tasks alongside PowerShell examples.
  • Mention and provide instructions for packaging Service Fabric applications using cross-platform tools (e.g., dotnet CLI, sfctl, or manual zip commands).
  • Include Linux/macOS file path examples and clarify any OS-specific steps.
  • Explicitly state that Visual Studio is optional and provide alternatives for non-Windows environments.
  • Consider referencing VS Code or other editors for cross-platform development.
GitHub Create Pull Request
Service Fabric Scalability of Service Fabric services .../service-fabric/service-fabric-concepts-scalability.md
Medium Priority View Details →
Scanned: 2026-02-28 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides code examples and administrative instructions primarily using PowerShell and C#, both of which are more commonly associated with Windows environments. There are no equivalent Linux CLI or bash examples, and PowerShell commands are referenced as the main administrative tooling. The 'Choosing a platform' section does acknowledge Linux, but only in the context of implementation differences, not in terms of parity of tooling or examples.
Recommendations
  • Add Linux-specific CLI/bash examples alongside PowerShell for administrative tasks (e.g., scaling services, creating/removing instances).
  • Reference and link to Service Fabric CLI (sfctl) usage for Linux users, and provide equivalent commands where possible.
  • Explicitly mention cross-platform administrative tools and workflows, clarifying which commands are available on both Windows and Linux.
  • Ensure that examples and instructions are presented in a platform-neutral way, or in parallel sections for Windows and Linux.
GitHub Create Pull Request
Service Fabric Learn more about Azure Service Fabric ...icles/service-fabric/service-fabric-content-roadmap.md
Medium Priority View Details →
Scanned: 2026-02-28 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 covers Azure Service Fabric concepts for both Windows and Linux, but there are several areas where Windows is prioritized or Linux parity is lacking. Windows-specific tools (PowerShell, Visual Studio) are mentioned first or exclusively in some sections, and standalone clusters are only supported on Windows. Examples and explanations often reference Windows services and executables before Linux equivalents, and Linux-specific guidance is minimal or missing in some areas.
Recommendations
  • Provide Linux-specific examples and instructions alongside Windows ones, especially for cluster creation, management, and upgrades.
  • Mention Linux CLI tools (e.g., Bash, sfctl) before or alongside PowerShell, and clarify which tools are cross-platform.
  • Add explicit guidance for Linux users in sections about application lifecycle, health monitoring, and diagnostics.
  • Clearly indicate feature parity and limitations for Linux throughout the documentation, linking to the differences page where relevant.
  • Include Linux-focused 'Next Steps' and sample links, not just Windows/Visual Studio-centric ones.
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-28 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page for Azure Service Fabric Events demonstrates a moderate Windows bias. It references Windows Event logs, ETW, and the Windows Azure diagnostics agent as primary mechanisms for accessing events, with no mention of Linux equivalents or cross-platform tooling. Windows-specific tools and patterns are mentioned first and exclusively, potentially creating friction for Linux cluster administrators.
Recommendations
  • Add information about how Service Fabric events are logged and accessed on Linux clusters, including any differences in event channels, logging mechanisms, or monitoring tools.
  • Include examples or references for accessing Service Fabric events on Linux, such as using syslog, journald, or Azure Monitor integration for Linux clusters.
  • Clarify which instructions or tools are Windows-only and provide Linux alternatives where available.
  • Consider reordering sections to present cross-platform or platform-neutral methods (such as REST APIs) before platform-specific tooling.
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-28 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 scripting examples. Windows tools (PowerShell, ApplicationManifest.xml editing in Visual Studio) are mentioned and demonstrated, while Linux alternatives (such as Azure CLI, Bash, or editing manifests in Linux environments) are not. Additionally, enabling DNS service via the Azure portal is described, but it is noted that Linux clusters cannot use this method, with no Linux-specific guidance provided. Windows-centric approaches are presented first or exclusively in several sections.
Recommendations
  • Add Linux-specific examples for setting DNS names, such as using Azure CLI or Bash scripts.
  • Provide guidance for editing manifests and deploying services from Linux environments (e.g., using VS Code, nano, or vim).
  • Include instructions for enabling DNS service in Linux clusters, focusing on ARM templates and CLI methods, since portal support is unavailable.
  • Clarify which steps or features are Windows-only and provide Linux alternatives where possible.
  • Balance PowerShell examples with Azure CLI or Bash equivalents for cross-platform parity.
GitHub Create Pull Request
Service Fabric Health monitoring in Service Fabric ...s/service-fabric/service-fabric-health-introduction.md
Medium Priority View Details →
Scanned: 2026-02-28 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides a PowerShell-only example for reporting and evaluating application health in Service Fabric, without offering equivalent Linux/macOS CLI or REST API examples. The main example uses Windows PowerShell cmdlets, which may create friction for Linux users, as Service Fabric supports cross-platform management via REST and CLI tools.
Recommendations
  • Add equivalent examples using Service Fabric REST API for health reporting and querying, which are platform-agnostic.
  • Include examples using Azure CLI or Service Fabric CLI (sfctl) for health reporting and evaluation, which work on Linux/macOS.
  • Clearly indicate that PowerShell is one option, and provide links or references to cross-platform alternatives.
  • Ensure that all critical tasks demonstrated with Windows tools are also shown with Linux-compatible methods.
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-28 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-based examples and references for managing Service Fabric services, with no equivalent Linux CLI or cross-platform examples. PowerShell is presented as the primary tooling for service creation and management, and REST API and .NET examples are included, but Linux-native tools (such as sfctl or Azure CLI) are not mentioned. The 'Next steps' section also directs users to PowerShell for application management.
Recommendations
  • Add examples using sfctl (Service Fabric CLI), which is cross-platform and commonly used on Linux/macOS.
  • Include Azure CLI commands where applicable for service creation and management.
  • Explicitly mention that PowerShell examples are for Windows, and provide Linux/macOS alternatives.
  • Update 'Next steps' to reference both PowerShell and sfctl/Azure CLI documentation for application deployment/removal.
  • Clarify any platform-specific limitations, if present, to help users understand which tools are supported on their OS.
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-02-28 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page 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, both of which are primarily Windows-centric tools. Linux equivalents (sfctl and install.sh) are mentioned but receive less prominence and explanation.
Recommendations
  • Provide more detailed Linux/macOS examples, such as using sfctl and install.sh, including sample commands and parameter formats.
  • Ensure Linux tools (sfctl) are given equal prominence and explanation as PowerShell and Visual Studio.
  • Add explicit guidance for Linux/macOS users on managing parameter files and deployment workflows.
  • Consider including a table or section comparing Windows and Linux workflows for parameter management.
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-28 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page for Service Fabric application and service manifest examples exhibits mild Windows bias. It references Windows-specific accounts (e.g., NetworkService, Administrators), uses Windows-style scripts (Setup.bat), and mentions the ServiceFabric PowerShell module for service creation. There are no explicit Linux examples or references to Linux equivalents for user accounts, startup scripts, or tooling. The manifest XML itself is cross-platform, but supporting instructions and examples are Windows-centric.
Recommendations
  • Add examples or notes for Linux deployments, such as using shell scripts (.sh) instead of batch files (.bat) for SetupEntryPoint.
  • Clarify how user accounts and groups map to Linux (e.g., use of system users, sudo, etc.) and whether NetworkService/Administrators concepts apply.
  • Mention or link to Linux-compatible tools for deploying and managing Service Fabric applications (e.g., Service Fabric CLI instead of PowerShell).
  • Provide guidance for cross-platform manifest authoring, highlighting any OS-specific considerations.
  • Explicitly state when examples are Windows-only and offer Linux alternatives where possible.
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-02-28 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 (e.g., RDP, Windows command prompt for ping), without offering equivalent Linux/macOS instructions or CLI examples. Windows tools and patterns are mentioned first and exclusively, creating friction for non-Windows users.
Recommendations
  • Add Azure CLI (az) examples for all deployment steps alongside PowerShell commands.
  • Include instructions for accessing VMs via SSH (for Linux/macOS) in addition to RDP.
  • Show Linux/macOS command-line equivalents for network testing (e.g., ping, ssh).
  • Clarify that Service Fabric clusters can be managed from any OS and provide cross-platform guidance.
  • Consider referencing Bash scripts or templates for Linux users.
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-28 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 the Service Fabric cluster manifest and links to a PowerShell-based deployment guide as the next step. While .NET and REST are mentioned as alternatives, PowerShell is consistently presented first and most prominently. There are no explicit Linux/macOS shell (e.g., Bash/CLI) examples or references, and the documentation assumes Visual Studio for publishing, which is Windows-centric.
Recommendations
  • Add Azure CLI or Bash examples for retrieving the cluster manifest and managing the ImageStoreConnectionString, if supported.
  • Include references or links to cross-platform tools or SDKs (e.g., Service Fabric CLI, REST API usage with curl) alongside PowerShell.
  • Clarify if certain operations (such as Visual Studio publishing) are Windows-only, and suggest alternatives for Linux/macOS users.
  • Balance the order of tool mentions (e.g., list REST, .NET, and PowerShell together or in a non-Windows-first order).
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-28 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page for 'Replica soft delete for enhanced data protection in Service Fabric' demonstrates notable Windows bias. All command-line/API examples reference PowerShell cmdlets (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica), with no mention of equivalent Linux CLI tools or usage patterns. The documentation repeatedly refers to administrative operations via PowerShell, and does not provide examples or guidance for Linux/macOS users, even though Service Fabric supports cross-platform development and management. This creates friction for non-Windows users who may need to perform these operations via REST APIs, FabricClient SDKs, or other cross-platform tools.
Recommendations
  • Add examples for performing replica soft delete and restore operations using cross-platform tools such as the Service Fabric CLI (sfctl), REST APIs, or FabricClient SDKs.
  • Clarify whether the PowerShell cmdlets are available on Linux/macOS (via PowerShell Core), or provide alternative instructions if not.
  • Include sample commands for querying and managing replicas using sfctl or REST endpoints.
  • Explicitly mention cross-platform support and provide links to relevant Linux/macOS documentation.
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-28 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation provides thorough 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 sections: HTTP.sys is discussed in detail, including endpoint configuration and port sharing, but is explicitly marked as Windows-only. Windows-specific tools and APIs (such as netsh and the Windows HTTP Server API) are referenced without Linux/macOS equivalents. In some sections, Windows/HTTP.sys is discussed before Kestrel, and endpoint configuration examples are given in a Windows-centric context. The debugging section references Visual Studio, a Windows-first tool, as the next step. While Kestrel is recommended for cross-platform scenarios, Linux/macOS users may find some friction due to Windows-centric explanations and lack of parity in tooling and examples.
Recommendations
  • Ensure that all examples and configuration instructions for Kestrel are presented before or alongside HTTP.sys/Windows-specific guidance.
  • Add explicit notes or sections clarifying Linux/macOS support, including any limitations or differences in Service Fabric hosting and endpoint configuration.
  • Provide Linux/macOS equivalents for any Windows tools mentioned (e.g., netsh), or clarify when such tools are not needed for Kestrel.
  • Include cross-platform debugging guidance (such as using Visual Studio Code or CLI tools) in the 'Next steps' section.
  • Where possible, highlight that Kestrel is the preferred option for Linux/macOS and provide clear instructions for those platforms.
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-28 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 interaction, but does not mention or provide equivalent Linux/macOS CLI examples (such as Azure CLI, Bash, or cross-platform tools). PowerShell is presented as the primary scripting interface, and Windows-style paths and prompts are used. This creates friction for Linux/macOS users, who may not have access to PowerShell or prefer native tools.
Recommendations
  • Add equivalent examples using Azure CLI or Bash scripts for health reporting tasks.
  • Explicitly mention cross-platform support for Service Fabric CLI tools, if available, and provide links or references.
  • Clarify whether PowerShell examples are usable on PowerShell Core (pwsh) on Linux/macOS, or provide alternatives.
  • Include REST API examples with curl commands for Linux/macOS users.
  • Use neutral prompts and paths (e.g., $> or #) in examples, or provide both Windows and Linux/macOS variants.
GitHub Create Pull Request
Service Fabric Fault Analysis Service overview .../service-fabric/service-fabric-testability-overview.md
Medium Priority View Details →
Scanned: 2026-02-28 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 PowerShell instructions for using the Fault Analysis Service, but does not mention or provide examples for Linux/macOS users (e.g., Bash, CLI, or REST API usage). It references Windows-centric tools (PowerShell, Service Fabric SDK) without Linux equivalents, and omits guidance for cross-platform environments.
Recommendations
  • Add examples for using the Fault Analysis Service from Linux/macOS, such as via Azure CLI, Bash, or REST API.
  • Mention how Linux users can install and use Service Fabric SDK and interact with the Fault Analysis Service.
  • Clarify whether PowerShell is required or if alternative cross-platform tools are available.
  • Provide parity in code samples and tooling instructions for non-Windows platforms.
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-28 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation is heavily oriented towards Windows development workflows, specifically Visual Studio and PowerShell. All deployment and configuration examples reference Visual Studio features (Build/Rebuild/F5/Ctrl+F5/Publish) and PowerShell cmdlets, with no mention of Linux/macOS equivalents or cross-platform tooling. There are no examples or guidance for Linux/macOS users, and the documentation assumes the use of Windows-centric tools and patterns throughout.
Recommendations
  • Add explicit guidance for Linux/macOS users, including how to manage service configuration and deployment without Visual Studio.
  • Provide examples using Azure CLI or cross-platform tools instead of (or in addition to) PowerShell.
  • Clarify which features are exclusive to Visual Studio/Windows and offer alternative workflows for Linux/macOS users where possible.
  • Mention any limitations or differences for Linux/macOS users up front, so expectations are set clearly.
GitHub Create Pull Request
Service Fabric Learn Azure Service Fabric terminology ...es/service-fabric/service-fabric-technical-overview.md
Medium Priority View Details →
Scanned: 2026-02-28 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page is generally platform-neutral, but there are notable Windows-centric elements. Windows terminology and tools (such as references to Windows services and EXE/DLL files) are mentioned first or exclusively in several sections. The description of nodes references an 'auto-start Windows service' and Windows executables, with no mention of Linux equivalents or service management patterns. Code package examples focus on EXE/DLL files, which are Windows-specific, and do not provide Linux examples (such as ELF binaries or .sh scripts). While Linux support is acknowledged, Windows patterns are presented first and more prominently.
Recommendations
  • Add Linux-specific terminology and examples alongside Windows references (e.g., mention systemd services, ELF binaries, .sh scripts).
  • Clarify how Service Fabric nodes and services are managed on Linux (e.g., what replaces the Windows service model, how executables are launched).
  • Provide parity in code package examples by including Linux file types and startup patterns.
  • Ensure that references to Windows tools and patterns are balanced with Linux equivalents throughout the documentation.
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-28 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 focuses exclusively on upgrading Service Fabric applications using Visual Studio and PowerShell, both of which are Windows-centric tools. All examples and instructions are tailored to Windows environments, with no mention of Linux/macOS alternatives or cross-platform CLI tools. Linux users are not provided with equivalent guidance, creating friction for those not on Windows.
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 Linux-compatible tools or workflows for Service Fabric application upgrades.
  • Clarify if Visual Studio and PowerShell are required, and provide alternative guidance for Linux/macOS users if possible.
  • Include sample commands for Bash or other Linux shells where applicable.
GitHub Create Pull Request
Service Fabric Custom Image .../articles/service-fabric/how-to-deploy-custom-image.md
Medium Priority View Details →
Scanned: 2026-02-27 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. Although there are references to Linux custom image creation and Azure CLI usage, the main focus and examples are Windows-centric, and the PowerShell command for role assignment is given without a Linux/CLI equivalent.
Recommendations
  • Provide Azure CLI examples for role assignments alongside PowerShell.
  • Clarify if Linux VM images are supported for Service Fabric Managed Clusters and, if so, include Linux-specific guidance and examples.
  • Balance the order and prominence of Windows and Linux instructions, ensuring Linux users can easily follow the process.
  • Explicitly state any platform limitations (e.g., if only Windows node types are supported) to avoid confusion.
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-02-27 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page frequently references Az PowerShell cmdlets (e.g., Remove-AzResource, AzSF PowerShell cmdlets) for managing Service Fabric resources, and provides PowerShell examples and links before mentioning or providing Azure CLI equivalents. While Azure CLI is referenced for deleting applications, PowerShell is emphasized for most operations, and no explicit Linux/macOS-friendly examples or guidance are given.
Recommendations
  • Include Azure CLI examples for all operations, not just application deletion, to ensure parity for Linux/macOS users.
  • Mention that Azure CLI is cross-platform and provide links to relevant CLI documentation.
  • Where PowerShell is referenced, clarify if the cmdlet is available in Azure Cloud Shell (which supports Linux/macOS) or if there are CLI alternatives.
  • Add explicit notes or examples for Linux/macOS users to avoid confusion.
GitHub Create Pull Request
← Previous Page 30 of 99 Next →