Service Fabric

810
Total Pages
600
Linux-Friendly Pages
210
Pages with Bias
25.9%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

718 issues found
Showing 501-525 of 718 flagged pages
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-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a notable Windows bias by exclusively referencing PowerShell-based administrative APIs (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica) and command-line examples. There is no mention of Linux or cross-platform equivalents, nor are there examples using Linux-native tools or CLI patterns. The documentation assumes the use of PowerShell and Windows tooling, which may create friction for Linux/macOS users managing Service Fabric clusters.
Recommendations
  • Include equivalent Linux/macOS command-line examples using Service Fabric CLI (sfctl) or REST APIs where available.
  • Explicitly mention cross-platform management options and provide links to relevant documentation for Linux/macOS users.
  • Clarify whether the described APIs (e.g., Restore-ServiceFabricReplica) are available via sfctl or REST, and provide usage examples.
  • Reorder examples or explanations so that cross-platform options are presented alongside or before Windows/PowerShell-specific instructions.
  • Add notes or sections addressing Linux/macOS cluster management workflows for replica soft delete.
GitHub Create Pull Request
Service Fabric Azure Service Fabric set up reverse proxy ...es/service-fabric/service-fabric-reverseproxy-setup.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Standalone cluster instructions and references (e.g., ClusterConfig.json, certificate management) are written for Windows environments, with links and examples pointing to Windows Server-specific guides. There is no mention of Linux-based standalone clusters, nor are Linux-specific certificate store details or upgrade instructions provided. The documentation refers to Windows paths (e.g., D:\SvcFab) and store names (e.g., 'My'), and upgrade instructions for standalone clusters link to Windows Server documentation. No Linux/macOS command-line examples or configuration patterns are given for standalone clusters.
Recommendations
  • Add explicit instructions and examples for Linux-based standalone clusters, including certificate management and configuration file locations.
  • Provide parity in upgrade instructions for standalone clusters running on Linux, with links to relevant Linux documentation.
  • Clarify which steps or settings are OS-specific, and offer alternatives or notes for Linux/macOS users.
  • Include Linux/macOS command-line examples where PowerShell or Windows tools are referenced.
  • Avoid using Windows paths or store names exclusively; mention Linux equivalents where relevant.
GitHub Create Pull Request
Service Fabric Azure Service Fabric reverse proxy diagnostics ...ice-fabric/service-fabric-reverse-proxy-diagnostics.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation page demonstrates a moderate Windows bias. Diagnostic error codes and terminology (e.g., ERROR_WINHTTP_TIMEOUT, ERROR_SUCCESS, winHttpError) are Windows-centric, and troubleshooting examples reference Windows-specific APIs and error codes. The 'Next steps' section prioritizes Windows Azure Diagnostics and Visual Studio for event viewing, with no mention of Linux equivalents or cross-platform tools. There are no explicit Linux/macOS examples or guidance for collecting or viewing logs on non-Windows platforms.
Recommendations
  • Add Linux/macOS-specific troubleshooting examples, including common error codes and log formats.
  • Include instructions for collecting and viewing Service Fabric reverse proxy logs using Linux-native tools (e.g., journald, syslog, Azure Monitor on Linux).
  • Reference cross-platform log aggregation and viewing solutions, such as Azure Monitor, Log Analytics, or open-source tools.
  • Balance the 'Next steps' section by mentioning Linux-compatible tools and IDEs (e.g., VS Code, CLI-based monitoring).
  • Clarify which error codes/messages are Windows-specific and provide Linux equivalents where applicable.
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-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias. It repeatedly references Visual Studio-specific workflows (Build/Rebuild/F5/Ctrl+F5/Publish), which are only available on Windows. The only command-line tooling mentioned is PowerShell, with no mention of Linux/macOS equivalents (such as Bash, CLI, or cross-platform tools). There are no examples or guidance for deploying or managing Service Fabric applications from Linux or macOS environments, nor is there any mention of how StartupServices.xml fits into non-Windows workflows. The documentation assumes the use of Visual Studio and Windows-centric deployment patterns throughout.
Recommendations
  • Add explicit guidance for Linux/macOS users, including how to deploy Service Fabric applications without Visual Studio.
  • Provide examples using Azure CLI, Bash, or other cross-platform tools for managing Service Fabric applications and manifests.
  • Clarify whether StartupServices.xml is relevant or supported in non-Windows environments, and if not, suggest alternatives.
  • Reorder examples or add parallel sections for Linux/macOS workflows to avoid Windows-first presentation.
  • Mention any limitations or differences for users working outside Windows/Visual Studio.
GitHub Create Pull Request
Service Fabric Scale out a Service Fabric managed cluster ...icles/service-fabric/tutorial-managed-cluster-scale.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively uses Azure PowerShell and provides only PowerShell-based examples for scaling out a Service Fabric managed cluster. There is no mention of Linux/macOS-compatible tools (such as Azure CLI), nor are alternative commands or instructions provided for non-Windows platforms. The prerequisites and example code assume a Windows environment, creating friction for Linux/macOS users.
Recommendations
  • Include Azure CLI examples for scaling node types, as Azure CLI is cross-platform and works on Linux/macOS.
  • Update prerequisites to mention both Azure PowerShell and Azure CLI, with links to installation instructions for all platforms.
  • Explicitly state platform compatibility for each method, and recommend the most cross-platform approach first.
  • Consider providing bash or shell script examples alongside PowerShell.
GitHub Create Pull Request
Service Fabric Add and remove node types of a Service Fabric managed cluster ...abric/tutorial-managed-cluster-add-remove-node-type.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily biased toward Windows, with all examples and instructions using Azure PowerShell. There are no CLI (az) or Linux/macOS-specific instructions or examples, despite mentioning that CLI is an option. The prerequisites only list Azure PowerShell, which is primarily used on Windows, and do not mention the Azure CLI or Bash alternatives.
Recommendations
  • Add equivalent Azure CLI examples for adding and removing node types, as Azure CLI is cross-platform and works natively on Linux/macOS.
  • Update the prerequisites section to mention both Azure PowerShell and Azure CLI, including installation instructions for Linux/macOS users.
  • Explicitly state which commands are platform-agnostic and provide guidance for users on non-Windows platforms.
  • Consider reordering or presenting examples for both PowerShell and CLI side-by-side, or defaulting to CLI for cross-platform parity.
GitHub Create Pull Request
Service Fabric Deploy app with a user-assigned managed identity ...vice-fabric-application-user-assigned-managed-identity.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page references PowerShell in the context of managing user-assigned managed identities and links to a PowerShell-centric guide. No equivalent CLI, Bash, or Linux/macOS-specific instructions or examples are provided. The mention of PowerShell as the primary management tool and the lack of cross-platform alternatives indicate a Windows bias.
Recommendations
  • Include Azure CLI and Bash examples alongside PowerShell for managing user-assigned managed identities.
  • Link to cross-platform guides (e.g., Azure CLI documentation) when referencing identity management tasks.
  • Explicitly state platform compatibility for all tools and scripts.
  • Provide guidance for Linux/macOS users where PowerShell is referenced.
GitHub Create Pull Request
Service Fabric Custom Image .../articles/service-fabric/how-to-deploy-custom-image.md
Medium Priority View Details →
Scanned: 2026-01-12 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 page demonstrates a Windows bias by focusing on 'custom windows images' in the introduction, providing only PowerShell examples for role assignment, and referencing Windows-specific tools and patterns before Linux equivalents. Linux-specific examples and CLI commands are either missing or referenced as links rather than shown inline, making the process less clear for Linux/macOS users.
Recommendations
  • Include explicit Linux/macOS examples for key steps, such as using Azure CLI for role assignment (e.g., 'az role assignment create ...').
  • Balance introductory language to mention both Windows and Linux custom images equally.
  • Provide ARM template examples for both Windows and Linux images, highlighting any differences.
  • Show Linux CLI commands inline, not just as links, especially for critical operations.
  • Clarify that the process applies to both Windows and Linux images where relevant.
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-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page predominantly references PowerShell cmdlets (e.g., Remove-AzResource, AzSF PowerShell cmdlet) for management operations, which are traditionally Windows-centric. There are no explicit CLI/bash examples or Linux/macOS alternatives provided, and the workflow assumes familiarity with PowerShell tools. This creates friction for Linux/macOS users who may prefer or require az CLI or ARM template approaches.
Recommendations
  • Add equivalent az CLI commands for all PowerShell cmdlet examples (e.g., show how to delete resources with az resource delete).
  • Explicitly mention that az CLI is cross-platform and provide usage examples for Linux/macOS users.
  • Clarify that ARM templates can be authored and deployed from any OS, and provide links or examples for Linux/macOS environments.
  • Where possible, avoid referencing only PowerShell cmdlets; provide parity with bash/CLI commands.
GitHub Create Pull Request
Service Fabric Use Azure DDoS Protection in a Service Fabric managed cluster ...rvice-fabric/how-to-managed-cluster-ddos-protection.md
Medium Priority View Details →
Scanned: 2026-01-12 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 notable Windows bias by providing only Azure PowerShell examples for key steps, referencing PowerShell before Azure CLI, and omitting explicit Linux/macOS command-line instructions. All command-line snippets use PowerShell syntax, which is native to Windows, and there are no bash or cross-platform CLI alternatives for tasks like service principal lookup or role assignment.
Recommendations
  • Add equivalent Azure CLI (az) command examples for all PowerShell instructions, especially for service principal lookup and role assignment.
  • Clearly indicate that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Where possible, show both PowerShell and CLI examples side-by-side, or default to CLI for broader accessibility.
  • Mention that ARM templates and Azure Portal are platform-agnostic, and highlight steps that can be performed without Windows-specific tools.
GitHub Create Pull Request
Service Fabric Azure Service Fabric releases ...ocs/blob/main/articles/service-fabric/release-notes.md
Medium Priority View Details →
Scanned: 2026-01-12 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 releases shows a moderate Windows bias. Several key announcements and instructions reference Windows-specific configuration properties (such as 'windowsConfiguration.enableAutomaticUpdates') and tools (e.g., Web Platform Installer, Visual Studio). In sections discussing durability and VM scale sets, Windows configuration is mentioned first or exclusively, with Linux equivalents either omitted or mentioned later. However, there are also references to Linux support and features, and no critical tasks appear to be Windows-only.
Recommendations
  • Whenever referencing VM scale set configuration, include both Windows and Linux property examples, or clarify Linux equivalents.
  • When mentioning tools (e.g., Web Platform Installer, Visual Studio), add Linux/macOS alternatives (e.g., CLI, VS Code, SFCTL).
  • Ensure that configuration snippets and code samples are provided for both Windows and Linux clusters where applicable.
  • Review and update documentation to mention Linux/macOS support equally, especially in upgrade, deployment, and configuration sections.
  • Add explicit notes or links for Linux/macOS users in sections that currently only mention Windows settings.
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-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides a PowerShell-only example for bypassing the Infrastructure Service, with no equivalent Linux/macOS command or guidance. The use of Service Fabric Explorer and PowerShell cmdlets reflects a Windows-centric approach, and there is no mention of Linux-native tools or cross-platform alternatives.
Recommendations
  • Include equivalent Linux/macOS command-line instructions, such as using Azure CLI, Bash, or REST API for cluster operations.
  • Clarify whether Service Fabric Explorer is accessible from non-Windows platforms and provide usage instructions for Linux/macOS if available.
  • Add notes or examples for managing Service Fabric clusters from Linux environments, especially for critical operations like bypassing Infrastructure Service.
  • Reference cross-platform tools or document REST API endpoints where applicable.
GitHub Create Pull Request
Service Fabric Create clusters on Windows Server and Linux ...rvice-fabric/service-fabric-azure-clusters-overview.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page describes Service Fabric clusters on both Windows Server and Linux, but the technical details and examples focus exclusively on Windows-specific tools and processes (e.g., FabricHost.exe, Fabric.exe, FabricGateway.exe). There are no Linux-specific equivalents or instructions, and no examples or mentions of Linux service management, process names, or deployment patterns. This creates ambiguity for Linux users about how clusters operate or are managed on Linux systems.
Recommendations
  • Add explicit descriptions of the Linux equivalents to Windows processes (e.g., what replaces FabricHost.exe, Fabric.exe, FabricGateway.exe on Linux).
  • Include Linux-specific instructions or examples for cluster node setup, service management, and deployment.
  • Clarify any differences in cluster management, security, and scaling between Windows and Linux platforms.
  • Provide parity in technical detail for both platforms, ensuring Linux users have actionable information.
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-01-12 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 page exhibits a moderate Windows bias. Windows-specific tools (PowerShell, Windows Defender, DSC) and examples are presented first or exclusively in several sections, with Linux equivalents sometimes provided later or omitted. Windows security baselines and antimalware guidance are detailed, while Linux alternatives are not discussed. Some sections, such as Windows Defender, are Windows-only, and Linux users are referred to generic antimalware documentation without specifics.
Recommendations
  • Present Windows and Linux examples side-by-side or in parallel sections, rather than Windows-first.
  • Include Linux-specific security baseline recommendations and tooling (e.g., CIS benchmarks, Linux security modules).
  • Provide concrete Linux antimalware guidance or recommended practices, not just a note to refer to generic documentation.
  • Where PowerShell is used for Windows, offer Bash or other Linux-native equivalents for all tasks.
  • Clarify which steps or tools are platform-specific and provide alternatives where possible.
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-01-12 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 demonstrates a moderate Windows bias. Windows-specific tools (PowerShell, RDP, Windows Update) are referenced more frequently and sometimes exclusively. Examples and explanations often mention Windows before Linux, and some sections (like DevOps and patching) focus on Windows workflows without equivalent Linux guidance. Linux is mentioned, but examples and operational details are less thorough.
Recommendations
  • Provide Linux-specific examples alongside Windows ones, especially for operational tasks (e.g., using Bash/CLI for client API access, patching, and cluster management).
  • Mention Linux tools and workflows explicitly in sections currently focused on Windows (e.g., SSH-based management, Linux update mechanisms).
  • Ensure parity in DevOps guidance by including Linux deployment and operational scenarios.
  • Balance the order of presentation so Linux is not always secondary to Windows.
  • Clarify which ports/rules are relevant only to Windows or Linux clusters, and provide guidance for both.
GitHub Create Pull Request
Service Fabric Update a cluster to use certificate common name ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-change-cert-thumbprint-to-cn.md
Medium Priority View Details →
Scanned: 2026-01-12 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 deployment instructions using PowerShell commands and Windows file paths, with no equivalent examples for Linux/macOS users. The only explicit deployment example uses PowerShell, and there is no mention of Azure CLI or Bash alternatives. Windows tooling and patterns (PowerShell, C:\temp paths) are presented exclusively, creating friction for users on non-Windows platforms.
Recommendations
  • Add equivalent deployment instructions using Azure CLI (az deployment group create) with Bash syntax and Linux/macOS file paths.
  • Include notes or examples for Linux/macOS users on how to prepare and deploy ARM templates.
  • Avoid using Windows-specific file paths (e.g., C:\temp) in generic examples; use cross-platform paths or show both.
  • Explicitly mention that both PowerShell and Azure CLI can be used, and link to relevant Azure CLI documentation.
GitHub Create Pull Request
Service Fabric Create a Service Fabric cluster in the Azure portal ...e-fabric/service-fabric-cluster-creation-via-portal.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation describes creating a Service Fabric cluster using the Azure portal, which supports both Linux and Windows clusters. However, several steps and examples (e.g., Remote Desktop credentials, management operations via PowerShell, VM size recommendations) are presented in a Windows-centric manner. There are no explicit Linux-specific instructions or examples, and Windows terminology (such as Remote Desktop) is used without mention of Linux alternatives (e.g., SSH).
Recommendations
  • Add explicit instructions and examples for Linux clusters, such as SSH key setup for VM access instead of only mentioning Remote Desktop credentials.
  • Where management operations are referenced (e.g., PowerShell), mention Azure CLI and provide equivalent Linux/macOS command examples.
  • Clarify which steps or options differ for Linux clusters (e.g., supported VM images, OS-specific configuration).
  • Ensure screenshots and UI references are inclusive of both Linux and Windows cluster creation flows.
  • Add a section or notes highlighting Linux-specific considerations and best practices.
GitHub Create Pull Request
Service Fabric Manage Service Fabric cluster upgrades ...fabric/service-fabric-cluster-upgrade-version-azure.md
Medium Priority View Details →
Scanned: 2026-01-12 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-only instructions for validating upgrade paths, with no equivalent CLI or Bash examples for Linux/macOS users. The only command-line example is Windows-centric, and the section on supported cluster versions lists Windows environments first. There is no mention of Linux-specific tools or workflows, and Linux users must infer how to perform tasks without direct guidance.
Recommendations
  • Add Azure CLI and/or Bash examples for validating upgrade paths, alongside PowerShell.
  • Explicitly mention Linux/macOS compatibility in command-line sections.
  • Present Windows and Linux environments equally in examples and lists.
  • Include notes or links for Linux/macOS users where workflows differ.
GitHub Create Pull Request
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-01-12 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 demonstrates a notable Windows bias by providing command-line examples exclusively using PowerShell cmdlets, which are native to Windows. There are no equivalent examples for Linux/macOS users, such as Bash, Azure CLI, or REST API usage. The documentation also refers to Windows-centric tools first and does not mention Linux-specific workflows or alternatives.
Recommendations
  • Add equivalent examples using Azure CLI, Bash scripts, or REST API calls for managing node tags and services.
  • Explicitly state cross-platform support and provide guidance for Linux/macOS users.
  • Reorder examples so that platform-neutral methods (e.g., REST API, Azure CLI) are presented before or alongside PowerShell.
  • Include notes or links to Linux/macOS documentation for Service Fabric management.
GitHub Create Pull Request
Service Fabric Change Azure Service Fabric cluster settings ...rvice-fabric/service-fabric-cluster-fabric-settings.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Many configuration parameters and descriptions reference Windows-specific concepts, tools, and defaults (e.g., certificate store names like 'MY', NTLM authentication, Windows Defender Firewall, and references to Windows-only features). Where platform differences exist, Windows is often mentioned first or exclusively, with Linux equivalents either missing, less detailed, or only referenced as exceptions. Some parameters have Windows-centric defaults or guidance, and links to further documentation are Windows-focused. There is a lack of explicit Linux/macOS configuration examples or parity in explanations for cross-platform users.
Recommendations
  • Add explicit Linux/macOS configuration examples and guidance for all parameters that differ by platform.
  • Where Windows-specific terms (e.g., certificate store names, NTLM, Windows Defender Firewall) are used, provide Linux/macOS equivalents or note their absence.
  • Ensure that platform-specific defaults are clearly indicated, and provide parity in documentation for Linux/macOS users.
  • Include links to Linux/macOS-focused documentation where available.
  • Review and update references to Windows-only tools and patterns to include cross-platform alternatives.
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-01-12 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 Windows bias by providing PowerShell examples for service creation and metric configuration, with no equivalent Linux/macOS CLI (such as Bash or Azure CLI) examples. Windows/PowerShell commands are presented as the only automation method, and there is no mention of Linux-native tools or cross-platform alternatives. This could create friction for users managing Service Fabric clusters from Linux or macOS environments.
Recommendations
  • Add equivalent examples using Azure CLI or Bash scripts for service creation and metric configuration.
  • Explicitly mention cross-platform management options and tools available for Linux/macOS users.
  • Clarify which commands are Windows-only and provide guidance for Linux/macOS users on how to achieve the same tasks.
  • Consider reordering examples so that cross-platform or Linux-native options are presented alongside or before Windows-specific ones.
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-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example Powershell Heavy
Summary
The documentation shows a moderate Windows bias. Windows-specific tools and patterns (e.g., PowerShell cmdlets, Visual Studio, Windows services like FabricHost.exe) are mentioned first or exclusively in several sections. Examples and instructions for Linux are less prominent or missing, especially for standalone clusters and some operational tasks. Linux support is acknowledged, but parity is not consistently demonstrated, and some features are noted as unsupported or less documented for Linux.
Recommendations
  • Provide Linux-specific examples and instructions alongside Windows ones, especially for cluster creation, management, and upgrades.
  • Highlight cross-platform CLI tools (e.g., sfctl) equally with PowerShell, and show Linux usage examples.
  • Clarify which features/tools are available on Linux and provide links to Linux-focused documentation where possible.
  • Avoid mentioning Windows tools (PowerShell, Visual Studio) first; present platform-neutral or Linux-first options where appropriate.
  • Add explicit guidance for Linux users in 'Next steps' and operational sections.
  • Document workarounds or alternatives for Linux where features are missing.
GitHub Create Pull Request
Service Fabric Service sensitivity ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-sensitivity.md
Medium Priority View Details →
Scanned: 2026-01-12 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 configuring service sensitivity and maximum load, but does not offer equivalent command-line instructions for Linux/macOS users (e.g., Bash, CLI). Windows-centric tools and APIs (PowerShell, C#) are presented before any mention of cross-platform alternatives, and there is no guidance for Linux-native workflows.
Recommendations
  • Add CLI examples using Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • Explicitly mention Linux/macOS compatibility for configuration files (XML/JSON) and deployment steps.
  • Reorder examples so that platform-neutral methods (manifest, JSON) appear before Windows-specific tools.
  • Provide Bash or shell script equivalents for dynamic service sensitivity updates.
  • Clarify any platform-specific limitations or requirements for the APIs and tools shown.
GitHub Create Pull Request
Service Fabric Overview of Service Fabric and containers ...s/service-fabric/service-fabric-containers-overview.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides both Linux and Windows information, but Windows scenarios and tools (IIS, Windows Server containers, Mirantis Container Runtime) are emphasized more prominently. Windows examples and references (such as IIS lift-and-shift and Windows container types) are described in greater detail, and Windows-specific links are sometimes listed before Linux equivalents. There is a lack of parity in scenario depth for Linux (e.g., no equivalent to the IIS lift-and-shift example for Linux web servers), and Windows container runtimes are discussed in more detail than Linux. Linux examples are present but less emphasized.
Recommendations
  • Add Linux-specific scenarios, such as Apache/Nginx lift-and-shift, to match the IIS example for Windows.
  • Ensure Linux tutorials and links are listed alongside or before Windows equivalents, especially in introductory and 'next steps' sections.
  • Provide equal detail for Linux container runtimes and their configuration as is given for Windows (e.g., mention containerd, Podman, etc. if supported).
  • Balance the discussion of container types and isolation by describing Linux container isolation mechanisms in equal detail.
  • Where Windows tools (like IIS) are mentioned, include Linux alternatives (e.g., Apache, NGINX) and how they can be containerized with Service Fabric.
GitHub Create Pull Request
Service Fabric Manage certificates in an Azure Service Fabric cluster ...https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-security-update-certs-azure.md
Medium Priority View Details →
Scanned: 2026-01-12 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 demonstrates a notable Windows bias, primarily through exclusive use of PowerShell for deployment and certificate management examples, references to Windows certificate stores (e.g., Cert:\CurrentUser\TrustedPeople), and lack of Linux/macOS CLI or scripting alternatives. All command-line instructions are given in PowerShell, with no mention of Azure CLI, Bash, or cross-platform certificate management tools. The workflow assumes a Windows environment for local certificate operations and cluster connections.
Recommendations
  • Provide equivalent Azure CLI or Bash examples for template deployment, certificate import, and cluster connection.
  • Reference cross-platform certificate stores and management tools (e.g., OpenSSL, Linux certificate locations).
  • Include instructions for macOS/Linux users on how to import certificates and connect to clusters.
  • Clarify which steps are platform-agnostic and which require platform-specific commands.
  • Order examples so that platform-neutral or cross-platform methods appear before Windows-specific ones.
GitHub Create Pull Request
← Previous Page 21 of 29 Next →