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 1976-2000 of 2475 flagged pages
Service Fabric Azure Service Fabric Events ...es/service-fabric/service-fabric-diagnostics-events.md
Medium Priority View Details →
Scanned: 2026-02-03 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page for Azure Service Fabric Events demonstrates a Windows bias by primarily referencing Windows-specific logging mechanisms (ETW/Windows Event logs) and the Windows Azure diagnostics agent. There are no explicit examples or instructions for accessing Service Fabric events on Linux clusters, nor are Linux-native tools or patterns mentioned. The documentation assumes the use of Windows-based monitoring and diagnostics tools, which may create friction for Linux users.
Recommendations
  • Add explicit guidance for accessing Service Fabric events on Linux clusters, including supported logging mechanisms and monitoring tools.
  • Mention Linux equivalents to ETW/Windows Event logs, such as syslog, journald, or other Linux-native logging solutions.
  • Clarify whether the Azure diagnostics agent and event logging features are available and supported on Linux clusters, and provide configuration instructions if so.
  • Include Linux-specific examples or note any limitations for Linux users.
GitHub Create Pull Request
Service Fabric Health monitoring in Service Fabric ...s/service-fabric/service-fabric-health-introduction.md
Medium Priority View Details →
Scanned: 2026-02-03 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation provides only PowerShell examples for reporting and evaluating Service Fabric health, with no equivalent examples for Linux/macOS users (e.g., Bash, CLI, or REST). The use of PowerShell is presented as the default, and Windows-centric tooling appears first and exclusively in the example section, creating friction for users on non-Windows platforms.
Recommendations
  • Add equivalent examples using Azure CLI, Bash, or REST API for health reporting and querying, which are cross-platform.
  • Explicitly mention and link to Linux/macOS-compatible tools and workflows for Service Fabric health operations.
  • Reorder or balance example sections so that Windows and Linux approaches are presented with equal prominence.
  • Clarify in the example section that PowerShell is one option, and provide guidance for users on other platforms.
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-03 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell and Visual Studio (Windows-centric tools) are mentioned first and in greater detail, with explicit references to PowerShell cmdlets and scripts. While sfctl (cross-platform CLI) is mentioned, there are no concrete Linux/macOS shell examples, and the workflow descriptions focus on Windows tools and patterns. There is no clear parity in examples or guidance for Linux/macOS users, especially regarding parameter file usage and deployment scripts.
Recommendations
  • Add explicit Linux/macOS shell examples for application creation and parameter passing using sfctl and bash scripts.
  • Clarify how parameter files are used in non-Visual Studio workflows, such as with CLI or CI/CD pipelines on Linux.
  • Reorder examples so that cross-platform tools (sfctl) are presented before or alongside Windows-specific tools (PowerShell, Visual Studio).
  • Provide links or references to Linux/macOS-specific guidance for Service Fabric deployments.
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-03 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page on the Azure Service Fabric hosting model demonstrates a moderate Windows bias. PowerShell is the only CLI example shown for service creation, and PowerShell-based management links are referenced throughout. There are no Linux CLI (e.g., Bash, Azure CLI) or cross-platform examples, nor is there mention of Linux-specific tooling or patterns. This creates friction for Linux/macOS users, who must infer or research equivalent commands and workflows.
Recommendations
  • Add Azure CLI examples for service creation and management, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention Linux support for Service Fabric and provide guidance or links for Linux users.
  • Reference REST API usage with curl or similar tools for Linux users, not just .NET and PowerShell.
  • Clarify any platform-specific limitations or differences in hosting model configuration and management.
  • Ensure that management operations (e.g., querying, health reporting, restarting code packages) are documented with both PowerShell and Azure CLI/REST API examples.
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-03 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page frequently references PowerShell and Visual Studio for deployment and configuration tasks, both of which are traditionally Windows-centric tools. Examples and next steps focus on PowerShell usage, with no mention of Linux/macOS equivalents (such as Azure CLI, Bash, or cross-platform SDKs). There is no guidance for Linux/macOS users on how to retrieve or set the ImageStoreConnectionString, nor are alternative workflows or tools suggested.
Recommendations
  • Add examples using Azure CLI, Bash, or cross-platform SDKs for retrieving and setting the ImageStoreConnectionString.
  • Include instructions for deploying and managing Service Fabric clusters from Linux/macOS environments.
  • Reference cross-platform tools and workflows alongside PowerShell and Visual Studio, ensuring parity in documentation.
  • Clarify which steps or tools are Windows-only and provide alternatives for non-Windows users where possible.
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-03 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page for Service Fabric Reliable Services app manifest examples shows moderate Windows bias. It references Windows concepts (NetworkService, Administrators group, .bat scripts), uses Windows-style executable names (VotingWeb.exe, Setup.bat), and mentions ServiceFabric PowerShell module for service creation. There are no explicit Linux/macOS equivalents or examples, and Windows terminology appears first and exclusively in several places.
Recommendations
  • Add Linux/macOS-specific examples, such as using shell scripts (.sh) in SetupEntryPoint and EntryPoint, and clarify how to specify these in manifests.
  • Document Linux/macOS equivalents for user/group principals (e.g., mapping to Unix users/groups), and clarify differences in account types.
  • Mention cross-platform deployment patterns and tools (e.g., Service Fabric CLI, sfctl) alongside PowerShell.
  • Note any platform-specific constraints or behaviors for manifest elements (e.g., RunAsPolicy, resource governance) on Linux clusters.
  • Where Windows concepts are referenced (e.g., NetworkService, Administrators), provide Linux analogs or clarify platform applicability.
GitHub Create Pull Request
Service Fabric Azure Service Fabric container application manifest examples ...abric/service-fabric-manifest-example-container-app.md
Medium Priority View Details →
Scanned: 2026-02-03 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. The examples and explanations are based on the 'Windows Server 2016 Container Sample', and Windows-specific tools and patterns (such as 'winver' for OS build detection and Windows-style paths like 'c:\VolumeTest\Data') are referenced exclusively or before Linux equivalents. There is no mention of Linux container samples, Linux path conventions, or Linux-specific instructions, and the manifest examples do not show Linux container scenarios or cross-platform considerations.
Recommendations
  • Include Linux-based container sample manifests and link to a Linux sample repository if available.
  • Provide Linux path examples (e.g., '/mnt/VolumeTest/Data') alongside Windows paths in volume binding sections.
  • Mention Linux commands for OS build/version detection (e.g., 'cat /etc/os-release' or 'uname -r') where 'winver' is referenced.
  • Clarify which manifest features or settings are cross-platform and which are Windows-only.
  • Add notes or examples for certificate handling on Linux (e.g., PEM file usage) and highlight differences in environment variable exposure.
  • Ensure parity in instructions for deploying and managing Service Fabric containers on Linux clusters.
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-03 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation covers both Windows-only (HTTP.sys) and cross-platform (Kestrel) hosting options for ASP.NET Core in Azure Service Fabric. However, it provides more detailed examples and configuration steps for HTTP.sys (Windows-only) before Kestrel, and does not explicitly show Linux/macOS-specific configuration, troubleshooting, or deployment steps. Windows tools and APIs (e.g., netsh, Windows HTTP Server API) are referenced without Linux equivalents, and there is no mention of Linux/macOS-specific considerations for Service Fabric clusters or ASP.NET Core hosting.
Recommendations
  • Add explicit Linux/macOS deployment and configuration examples for Service Fabric clusters running ASP.NET Core services with Kestrel.
  • Include troubleshooting tips or notes for common Linux/macOS issues (e.g., firewall configuration, permissions, directory paths).
  • Clarify in relevant sections that HTTP.sys is Windows-only and provide alternative guidance for Linux/macOS users (e.g., always use Kestrel).
  • Where Windows tools (like netsh) are mentioned, note that these steps are not required or applicable on Linux/macOS.
  • Consider reordering sections so that cross-platform (Kestrel) guidance appears before Windows-only (HTTP.sys) guidance.
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-03 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 presents all command-line/API examples using PowerShell cmdlets (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica), which are Windows-centric tools. There is no mention of Linux equivalents, cross-platform CLI usage, or REST API alternatives. The documentation assumes use of Windows tooling and does not provide guidance for Linux/macOS users, even though Service Fabric supports Linux clusters.
Recommendations
  • Include examples using Service Fabric CLI (sfctl), which is cross-platform and commonly used on Linux/macOS.
  • Mention REST API endpoints or FabricClient SDK usage for replica management, clarifying how Linux users can perform equivalent operations.
  • Add a section or note specifying how Linux cluster administrators can query, remove, and restore replicas using non-Windows tools.
  • Clarify whether the PowerShell cmdlets are available or supported on Linux, or provide alternatives if not.
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-03 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed PowerShell examples for health reporting and cluster connection, but does not offer equivalent examples for Linux/macOS users (e.g., Bash, CLI, or cross-platform scripts). PowerShell is featured prominently and exclusively in example commands, and Windows-style paths (e.g., PS C:\>) are used. REST and API methods are mentioned, but practical command-line usage for Linux environments is not demonstrated.
Recommendations
  • Add equivalent examples using Azure CLI or Bash scripts for health reporting and cluster connection, suitable for Linux/macOS users.
  • Clarify whether PowerShell examples are usable on Linux (via PowerShell Core), and provide guidance for Linux users if so.
  • Include cross-platform instructions for installing and using Service Fabric command-line tools on Linux/macOS.
  • Show REST API usage with curl or similar tools, including sample requests and authentication guidance for Linux environments.
  • Avoid using Windows-style paths and prompts exclusively; use generic or platform-neutral prompts where possible.
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-03 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page primarily uses Windows/PowerShell tooling for deployment examples (e.g., New-ServiceFabricApplication), references Windows file paths for schema locations, and generally presents Windows-specific details before Linux equivalents. Linux-specific instructions are minimal and only briefly mentioned (e.g., certificate store path).
Recommendations
  • Provide equivalent Linux CLI examples (e.g., using sfctl or Azure CLI) alongside PowerShell commands for deploying applications and passing parameters.
  • Mention Linux file paths and configuration locations wherever Windows paths are referenced (e.g., for schema files).
  • Explicitly state any differences or additional steps required for Linux clusters, especially regarding endpoint/certificate management and deployment.
  • Ensure Linux examples are presented with equal prominence, not only as afterthoughts or notes.
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-03 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page generally presents Service Fabric concepts in a cross-platform manner, noting support for both Windows and Linux. However, there are subtle signs of Windows bias: Windows-specific tools and processes (such as auto-start Windows services and EXE/DLL terminology) are described first and in detail, while Linux equivalents are not explicitly mentioned or explained. For example, the node description focuses on Windows services and executables, and the code package section refers to EXE/DLL files, which are Windows-centric. Linux-specific process/service management is not discussed, and Linux file types or patterns are not illustrated.
Recommendations
  • Explicitly mention Linux equivalents when describing node startup and service management (e.g., systemd services, ELF binaries).
  • Provide examples or notes for Linux file types and process management alongside Windows EXE/DLL references.
  • Clarify that Service Fabric supports both Windows and Linux nodes, and highlight any differences in terminology or tooling where relevant.
  • Where Windows-specific terms are used, add Linux-specific terminology or examples for parity.
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-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page primarily references PowerShell cmdlets (Az PowerShell, AzSF PowerShell) for managing Service Fabric resources, with no mention of equivalent Azure CLI commands or Linux/macOS workflows. While az resource is mentioned once, the majority of examples and guidance are PowerShell-centric, which may create friction for Linux or macOS users who typically use Azure CLI or Bash.
Recommendations
  • Include Azure CLI equivalents for all PowerShell cmdlet examples, especially for common operations like creating, deleting, and scaling resources.
  • Clarify when Az PowerShell is required versus when Azure CLI can be used, and provide links to relevant Azure CLI documentation.
  • Add explicit notes or examples for Linux/macOS users, ensuring parity in instructions and tooling.
  • Where possible, provide ARM template examples that are platform-agnostic.
GitHub Create Pull Request
Service Fabric Application lifecycle in Service Fabric ...service-fabric/service-fabric-application-lifecycle.md
Medium Priority View Details →
Scanned: 2026-02-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page for the Service Fabric application lifecycle demonstrates a notable Windows bias. PowerShell cmdlets are referenced throughout as primary examples for operational tasks (deploy, upgrade, remove, cleanup), often listed before REST API or .NET methods. There is little to no mention of Linux-specific tools, shell commands, or cross-platform CLI usage (such as Azure CLI or sfctl), despite Service Fabric supporting Linux clusters. This may create friction for Linux/macOS users who do not use PowerShell or Windows-centric tooling.
Recommendations
  • Add equivalent Linux/macOS examples using Azure CLI and sfctl for all operational steps (deploy, upgrade, remove, cleanup).
  • Ensure REST API and cross-platform CLI commands are presented before or alongside PowerShell cmdlets, not after.
  • Explicitly state cross-platform support and clarify which tools are available on Linux/macOS.
  • Where PowerShell is used, provide alternative shell or CLI commands for Linux users.
  • Add notes or links to Linux-specific documentation where relevant.
GitHub Create Pull Request
Service Fabric Manage Azure Service Fabric app load using metrics ...ric/service-fabric-cluster-resource-manager-metrics.md
Medium Priority View Details →
Scanned: 2026-02-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides both C# and PowerShell examples for managing Service Fabric metrics, but PowerShell is featured prominently and exclusively as the CLI example. There are no Linux/macOS CLI equivalents (such as Azure CLI or REST API examples), and PowerShell is presented before any mention of cross-platform alternatives. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer platform-agnostic tools.
Recommendations
  • Add Azure CLI examples for all PowerShell commands shown, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include REST API examples where appropriate, especially for service creation and metric updates.
  • Explicitly mention platform compatibility for PowerShell commands and suggest alternatives for non-Windows users.
  • Reorder examples so that cross-platform options (Azure CLI, REST API) are shown before or alongside PowerShell.
  • Clarify whether Service Fabric management tasks can be performed equally well from Linux/macOS, and link to relevant documentation.
GitHub Create Pull Request
Service Fabric Azure Service Fabric hosting activation and deactivation life cycle ...les/service-fabric/service-fabric-hosting-lifecycle.md
Medium Priority View Details →
Scanned: 2026-02-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page describes the Azure Service Fabric hosting activation and deactivation lifecycle in a platform-neutral way, but the only explicit example or next-step guidance for deploying/removing applications is via PowerShell, which is primarily a Windows tool. There are no Linux/macOS CLI or script examples, nor are Linux tools or patterns mentioned. The link for downloading a ServicePackage in advance also points to a PowerShell cmdlet, with no Linux equivalent provided.
Recommendations
  • Add equivalent examples for Linux/macOS users, such as using Azure CLI or Service Fabric CLI (sfctl) for deployment and package management.
  • Include links to documentation for Linux-based Service Fabric clusters and their management tools.
  • Where PowerShell is referenced, clarify if cross-platform PowerShell Core is supported, or provide alternative commands for bash/shell environments.
  • Ensure that next steps and code samples cover both Windows and Linux workflows equally.
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-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation provides both Windows and Linux guidance for key security tasks, but Windows examples and tools (e.g., PowerShell, Windows Defender, Windows security baselines) are often presented first or exclusively, with Linux equivalents sometimes referenced later or less prominently. Windows-specific tools and configuration patterns (e.g., PowerShell commands, Windows Defender configuration) are described in detail, while Linux alternatives are less emphasized or omitted in some sections.
Recommendations
  • Present Windows and Linux examples side-by-side or in parallel sections to ensure equal visibility.
  • Where Windows-specific tools (e.g., PowerShell, Windows Defender) are discussed, provide clear Linux alternatives or explicitly state when no equivalent exists.
  • Add more Linux-focused security baseline recommendations and reference common Linux security tools (e.g., SELinux, AppArmor, Linux antivirus solutions) where appropriate.
  • Ensure that instructions for deploying certificates, configuring ACLs, and encrypting secrets are equally detailed for both platforms.
  • Clarify platform-specific limitations or differences to help users understand which guidance applies to their environment.
GitHub Create Pull Request
Service Fabric Overview of Azure and standalone Service Fabric clusters ...icles/service-fabric/service-fabric-deploy-anywhere.md
Medium Priority View Details →
Scanned: 2026-02-02 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation discusses Service Fabric clusters on both Windows Server and Linux, but it notes that standalone clusters are not available on Linux. The page generally presents Windows as the default or primary platform, with Linux mentioned as a secondary consideration. There are no Linux-specific examples or guidance, and the limitations for Linux are referenced only via a link, not explained directly.
Recommendations
  • Explicitly state the limitations for Linux clusters in the main content, not just via a link.
  • Provide a summary table or section outlining feature parity and gaps between Windows and Linux clusters.
  • Include Linux-specific guidance or examples where relevant, or clarify when features are Windows-only.
  • Ensure that Linux is mentioned equally in benefits and limitations sections, not just as an afterthought.
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-02 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Windows (ClusterManifest.xml) and cross-platform (ClusterConfig.json) configuration examples, but all imperative command-line examples are given only in PowerShell, with no Linux CLI or Bash equivalents. The only explicit infrastructure example for local clusters uses <WindowsServer> in ClusterManifest.xml, and PowerShell is used for service management, which may create friction for Linux users. However, the core concepts and JSON-based configuration are cross-platform.
Recommendations
  • Add CLI/Bash examples for service creation and updates, using Service Fabric CLI (sfctl), which is supported on Linux/macOS.
  • Clarify when examples (such as <WindowsServer> in ClusterManifest.xml) are Windows-specific, and provide Linux equivalents (e.g., <Linux> infrastructure blocks) where appropriate.
  • Where PowerShell is used, add a note or alternative showing how to accomplish the same task on Linux using sfctl or REST API.
  • Ensure that imperative examples (service creation, updates) are shown for both Windows (PowerShell) and Linux (CLI/Bash/sfctl).
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-02 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 demonstrates a Windows bias by primarily referencing Windows-specific logging mechanisms (ETW/Windows Event logs) and the Windows Azure diagnostics agent. There is no mention of Linux equivalents or guidance for accessing Service Fabric events on Linux clusters, nor are Linux-specific tools or examples provided. Windows tools and patterns are mentioned first and exclusively.
Recommendations
  • Add explicit guidance for accessing Service Fabric events on Linux clusters, including supported logging mechanisms (e.g., stdout/stderr, syslog, or Azure Monitor integration for Linux nodes).
  • Mention and provide examples of how to access and analyze events on Linux-based Service Fabric clusters.
  • Clarify any differences in event logging and diagnostics configuration between Windows and Linux clusters.
  • If certain features are Windows-only, explicitly state this to inform Linux users of any limitations.
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-02 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 'Networking patterns for Azure Service Fabric' demonstrates a moderate Windows bias. All command-line examples use PowerShell, with no Bash, Azure CLI, or Linux/macOS shell equivalents. The workflow and deployment instructions are written from a Windows-centric perspective (e.g., file paths like C:\SFSamples\...), and RDP is referenced as the remote access method, which is primarily a Windows protocol. There are no explicit instructions or examples for Linux/macOS users, nor are alternative tools or commands mentioned.
Recommendations
  • Provide Azure CLI and/or Bash examples alongside PowerShell commands for template deployment and resource management.
  • Include Linux/macOS file path examples where relevant, or use platform-neutral paths.
  • Mention SSH as an alternative to RDP for accessing VMs, especially for Linux-based clusters.
  • Clarify that the instructions apply to both Windows and Linux node types where appropriate, or note any differences.
  • Add a brief section or callout for Linux/macOS users, highlighting any platform-specific considerations.
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-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is notably Windows-centric, focusing exclusively on Visual Studio tooling and workflows (Build/Rebuild/F5/Ctrl+F5/Publish), which are only available on Windows. There is no mention of Linux/macOS development environments, nor are alternative workflows or tools provided for non-Windows platforms. Examples and instructions are tailored to Windows users, with references to PowerShell and Visual Studio, and no Linux equivalents or parity guidance.
Recommendations
  • Explicitly state that StartupServices.xml is only supported for Visual Studio deployments on Windows, and clarify limitations for Linux/macOS users.
  • Provide alternative instructions or workflows for Linux/macOS users, if possible, or link to documentation for ARM/cmdlet-based deployments that work cross-platform.
  • Add a section comparing Windows and Linux/macOS development experiences for Service Fabric applications, highlighting any feature gaps.
  • If Linux/macOS support is not possible for this feature, make this clear early in the documentation to set expectations.
GitHub Create Pull Request
Service Fabric Manage certificates in a Service Fabric cluster ...vice-fabric/cluster-security-certificate-management.md
Medium Priority View Details →
Scanned: 2026-02-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page provides extensive PowerShell examples and references to Windows-specific tooling and patterns (such as certificate store locations, ACLing, and Key Vault VM extension for Windows). While the core certificate management concepts are platform-neutral, the hands-on examples, troubleshooting, and automation scripts are almost exclusively presented using Windows-centric tools and PowerShell, with little to no mention of Linux equivalents or cross-platform approaches. Windows terminology and mechanisms (e.g., S-channel, certificate store, ACLing) are explained in detail, while Linux alternatives are absent or implied.
Recommendations
  • Add equivalent examples using Azure CLI and/or Bash scripts for certificate enrollment, provisioning, and rotation.
  • Explicitly document how certificate provisioning and management works for Service Fabric clusters running on Linux VMs/VMSS, including any differences in certificate store handling, permissions, and automation.
  • Reference and link to Key Vault VM extension documentation for Linux, if available, or clarify limitations.
  • When discussing certificate stores, ACLing, and linking, provide Linux-specific guidance (e.g., file permissions, OpenSSL usage) where relevant.
  • Ensure troubleshooting and FAQ sections include Linux scenarios and commands.
GitHub Create Pull Request
Service Fabric Custom Image .../articles/service-fabric/how-to-deploy-custom-image.md
Medium Priority View Details →
Scanned: 2026-02-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page for deploying custom images on Azure Service Fabric Managed Clusters demonstrates a Windows bias. The introductory section and examples refer specifically to 'custom windows images', and the only command-line example provided uses PowerShell (New-AzRoleAssignment), with no equivalent Azure CLI or Linux shell example. While there are references to Linux custom image creation and Azure CLI for browsing images, actionable steps and examples are Windows-centric, potentially creating friction for Linux/macOS users.
Recommendations
  • Provide Azure CLI examples alongside PowerShell commands for role assignment and other operations.
  • Clarify whether Linux-based custom images are supported for Service Fabric Managed Clusters and, if so, include explicit instructions and examples for Linux images.
  • Balance references to Windows and Linux in introductory and instructional text, ensuring Linux users are equally addressed.
  • Add notes or sections for Linux/macOS users, including shell command equivalents and relevant links.
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-02 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, without mentioning Linux/macOS equivalents or cross-platform CLI alternatives. The use of PowerShell cmdlets and lack of Bash/Azure CLI examples may create friction for Linux/macOS administrators.
Recommendations
  • Include equivalent Azure CLI or REST API instructions for bypassing Infrastructure Service operations, if available.
  • Clarify whether the PowerShell command is required or if cross-platform alternatives exist.
  • Add notes or examples for Linux/macOS users, especially for cluster management tasks.
  • Indicate platform requirements for commands, so users know if a Windows environment is necessary.
GitHub Create Pull Request
← Previous Page 80 of 99 Next →