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 1526-1550 of 2475 flagged pages
Service Fabric Cluster Resource Manager - Management Integration ...fabric-cluster-resource-manager-management-integration.md
Medium Priority View Details →
Scanned: 2026-02-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides a PowerShell example for querying partition health, using Windows-style paths and commands (e.g., 'PS C:\Users\User > Get-ServiceFabricPartitionHealth'), without offering equivalent Linux/macOS CLI or REST API examples. This suggests a bias toward Windows environments and tools, potentially creating friction for Linux/macOS users who may use Service Fabric CLI (sfctl) or REST APIs instead.
Recommendations
  • Add equivalent Linux/macOS examples using Service Fabric CLI (sfctl) or REST API calls for health queries.
  • Mention cross-platform management tools and clarify which commands are available on each OS.
  • Where possible, provide both Windows (PowerShell) and Linux/macOS (bash/sfctl/REST) examples side-by-side.
  • Explicitly note any limitations or differences in tooling between platforms.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides a PowerShell example for deploying Service Fabric applications, which is Windows-centric. The schema file path references a Windows directory first. Linux-specific information is limited to a single note about certificate storage, and Linux deployment examples or CLI equivalents are missing.
Recommendations
  • Add equivalent Linux deployment instructions using Azure CLI or Service Fabric CLI (sfctl).
  • Provide Linux file path examples for schema files alongside Windows paths.
  • Include notes or examples for managing endpoints and certificates on Linux clusters, such as using Kestrel or configuring certificates in /var/lib/sfcerts.
  • Ensure that PowerShell examples are accompanied by cross-platform alternatives.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides extensive PowerShell examples and references Windows-specific tools (such as the Key Vault VM extension for Windows and S-channel APIs). Windows terminology and mechanisms are frequently mentioned first or exclusively, and Linux-specific guidance or parity is not provided for certificate provisioning, management, or automation. The Key Vault VM extension is described only for Windows, and there are no Bash/CLI or Linux-native examples for certificate enrollment, provisioning, or rotation.
Recommendations
  • Add equivalent Bash/CLI examples for certificate enrollment and management, especially for Key Vault operations.
  • Document the Key Vault VM extension for Linux, or clarify its availability and usage for Linux VM/VMSS nodes.
  • Provide guidance for certificate provisioning and autorollover in Service Fabric clusters hosted on Linux (if supported), including relevant tools and automation patterns.
  • Explicitly note any Windows-only limitations and offer alternative approaches for Linux/macOS users where possible.
  • Ensure troubleshooting and FAQ sections include Linux scenarios and commands.
GitHub Create Pull Request
Service Fabric X.509 Certificate-based Authentication in a Service Fabric Cluster ...ticles/service-fabric/cluster-security-certificates.md
Medium Priority View Details →
Scanned: 2026-02-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides detailed conceptual and configuration guidance for X.509 certificate-based authentication in Service Fabric clusters, but exhibits a moderate Windows bias. Windows-specific terminology and tools (e.g., 'LocalMachine\My' certificate store, Win32 CryptoAPI, CAPI2 logging, error codes, and troubleshooting steps) are mentioned first or exclusively in several places. Linux equivalents are referenced only briefly or parenthetically, and there are no concrete Linux-specific examples or troubleshooting steps. This may create friction for Linux users, especially when interpreting certificate store paths, error diagnostics, or when following troubleshooting advice.
Recommendations
  • Provide Linux-specific examples alongside Windows ones, especially for certificate store paths (e.g., expand on the mention of '/var/lib/sfcerts').
  • Include Linux troubleshooting steps and log locations, not just Windows Event Log and CAPI2 logging.
  • When referencing Windows APIs (e.g., Win32 CryptoAPI), clarify the equivalent behavior or configuration on Linux.
  • List Linux and Windows paths/tools in parallel, not just as parentheticals after Windows-first explanations.
  • Add a section or callouts for common Linux-specific certificate issues and how to resolve them.
GitHub Create Pull Request
Service Fabric Azure Service Fabric container image management .../articles/service-fabric/container-image-management.md
Medium Priority View Details →
Scanned: 2026-02-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation references Windows container base images (microsoft/windowsservercore, microsoft/nanoserver) as default exclusions in the cleanup process, and mentions Windows images before Linux equivalents. There are no explicit Linux container image examples or references, and the documentation does not clarify Linux-specific behaviors or provide parity examples for Linux container images.
Recommendations
  • Add examples referencing common Linux container images (e.g., 'docker.io/library/ubuntu', 'docker.io/library/alpine') in the 'ContainerImagesToSkip' setting.
  • Clarify whether the cleanup process applies equally to Linux containers and Windows containers, and note any differences.
  • Provide guidance or examples for Linux-based Service Fabric clusters, if applicable.
  • Mention Linux container image management patterns or considerations alongside Windows examples.
GitHub Create Pull Request
Service Fabric Custom Image .../articles/service-fabric/how-to-deploy-custom-image.md
Medium Priority View Details →
Scanned: 2026-02-13 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 presented. While Linux is referenced in links and some concepts, Windows is mentioned first and PowerShell is used for role assignment, with no equivalent Linux CLI example provided. The ARM template examples are generic, but the focus and examples are Windows-centric.
Recommendations
  • Add explicit Linux-focused examples and clarify Linux support for custom images in Service Fabric Managed Clusters.
  • Provide Azure CLI commands for role assignment alongside PowerShell examples.
  • Mention Linux image types and marketplace images equally with Windows, and clarify any limitations or parity.
  • Ensure that links to Linux documentation are as prominent as Windows 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-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides a PowerShell-only example for bypassing Infrastructure Service, and references Service Fabric Explorer (a Windows-centric tool) without mentioning Linux/macOS alternatives. There are no Linux CLI or cross-platform examples for cluster operations, and Windows tools/patterns are mentioned first or exclusively.
Recommendations
  • Add equivalent Linux/macOS command-line examples (e.g., using sfctl or Azure CLI) for cluster operations.
  • Clarify whether Service Fabric Explorer is available cross-platform or suggest alternatives for Linux/macOS users.
  • Where PowerShell is used, provide Bash or cross-platform CLI equivalents if possible.
  • Explicitly note any limitations or differences for Linux clusters, if relevant.
GitHub Create Pull Request
Service Fabric Configure or modify a Service Fabric managed cluster node type ...vice-fabric/how-to-managed-cluster-modify-node-type.md
Medium Priority View Details →
Scanned: 2026-02-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides step-by-step instructions for configuring and modifying Service Fabric managed cluster node types using the Azure Portal, ARM templates, and PowerShell. However, all CLI/scripted examples are exclusively in PowerShell, with no mention of Azure CLI (az) or Bash scripting. This creates friction for Linux/macOS users, as PowerShell is not the default or preferred tool on those platforms. Additionally, the documentation refers to PowerShell cmdlets without clarifying cross-platform support or offering alternatives.
Recommendations
  • Add Azure CLI (az) command examples for all operations currently shown only with PowerShell, such as adding, removing, and scaling node types.
  • Explicitly state whether the PowerShell cmdlets used are supported on PowerShell Core (cross-platform) or only on Windows PowerShell.
  • Where possible, provide Bash scripting examples or clarify that ARM template deployment can be performed with az CLI on any platform.
  • Reorder sections or provide parallel examples so that Linux/macOS users see relevant options without needing to adapt Windows-centric instructions.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation predominantly references PowerShell cmdlets (Az PowerShell, AzSF PowerShell) for managing Service Fabric resources, with no mention of Linux/macOS equivalents or usage of Azure CLI except for a single az resource example. This creates friction for users on Linux or macOS, as PowerShell is traditionally Windows-centric and not the default shell on those platforms.
Recommendations
  • Provide equivalent Azure CLI commands for all management operations, as Azure CLI is cross-platform and preferred on Linux/macOS.
  • Explicitly state that PowerShell cmdlets can be run on Linux/macOS if supported, or provide installation guidance.
  • Reorder examples to show Azure CLI usage first or alongside PowerShell, ensuring parity.
  • Clarify any platform-specific limitations or requirements for the AzSF PowerShell module.
GitHub Create Pull Request
Service Fabric Describing Azure Service Fabric apps and services ...ic/service-fabric-application-and-service-manifests.md
Medium Priority View Details →
Scanned: 2026-02-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation contains a notable Windows bias, primarily in the 'WARNING' section recommending Visual Studio and referencing a Windows file path for schema validation. It also mentions the ServiceFabric PowerShell module as a way to create service instances, without referencing Linux equivalents or cross-platform tools. However, the core content (manifest XML, concepts) is platform-neutral.
Recommendations
  • Provide instructions for validating XML schema on Linux/macOS, such as using VS Code, xmllint, or other cross-platform editors/tools.
  • Mention cross-platform deployment tools (e.g., Azure CLI, sfctl) alongside PowerShell.
  • Clarify that Service Fabric development and deployment can be performed on Linux clusters and provide links or examples for Linux users.
  • Avoid referencing Windows file paths exclusively; if schema files are available on Linux, specify their location.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation frequently references PowerShell cmdlets and Windows-specific tools (e.g., Copy-ServiceFabricApplicationPackage, Register-ServiceFabricApplicationType, Remove-ServiceFabricApplicationPackage) alongside .NET APIs and REST operations. PowerShell examples are consistently provided, but Linux equivalents (such as Azure CLI or sfctl) are not mentioned in the main lifecycle steps, despite a brief link to CLI documentation at the top. Windows tools and patterns are often listed first, and there is no explicit guidance or examples for Linux/macOS users, which creates friction for those not on Windows.
Recommendations
  • Add explicit Azure CLI and sfctl command examples for each lifecycle operation (deploy, upgrade, remove, etc.), not just REST or PowerShell.
  • Where PowerShell cmdlets are referenced, include corresponding Linux/macOS-friendly commands and clarify cross-platform support.
  • Reorder tool mentions so that cross-platform options (REST, CLI) are listed before or alongside Windows-specific tools.
  • Add a section or note clarifying which tools are supported on Linux/macOS and how to accomplish the same tasks.
GitHub Create Pull Request
Service Fabric Service Fabric application upgrade ...s/service-fabric/service-fabric-application-upgrade.md
Medium Priority View Details →
Scanned: 2026-02-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page for Service Fabric application upgrades exhibits notable Windows bias. PowerShell is the only CLI example provided, and references to Windows-specific tools (e.g., http.sys, PowerShell cmdlets) are prominent. There are no Linux or cross-platform CLI examples (such as Azure CLI, REST API, or Service Fabric CLI), nor are Linux-specific upgrade workflows discussed. References to upgrade tutorials and troubleshooting are also Windows-centric, with Visual Studio and PowerShell mentioned exclusively.
Recommendations
  • Add equivalent Linux/macOS examples using Service Fabric CLI (sfctl), Azure CLI, or REST API for application upgrades.
  • Mention cross-platform tools and workflows alongside Windows tools, not just after or instead of them.
  • Clarify which features or steps are Windows-only and provide Linux alternatives where possible.
  • Include links to Linux/macOS-specific tutorials and troubleshooting guides.
  • Ensure that upgrade scenarios and health checks are described in a platform-neutral way unless they are inherently Windows-specific.
GitHub Create Pull Request
Service Fabric Monitor Azure Service Fabric ...main/articles/service-fabric/monitor-service-fabric.md
Medium Priority View Details →
Scanned: 2026-02-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation covers monitoring for Azure Service Fabric clusters on both Windows and Linux, but there is a notable Windows bias in several areas. Windows-specific tools (such as EventStore APIs and Diagnostics Agent) are mentioned first or exclusively, with Linux equivalents referenced later or in less detail. Some examples and tutorials focus on Windows clusters or .NET applications, with Linux-specific guidance often relegated to links or brief notes. The EventStore APIs are Windows-only, and Windows event channels (ETW/Event Viewer) are described in detail, while Linux channels (LTTng/Syslog) are mentioned but not explained as thoroughly. Linux configuration steps and examples are less prominent.
Recommendations
  • Provide Linux-specific examples and tutorials with equal prominence to Windows ones, especially for cluster and infrastructure monitoring.
  • Expand explanations of Linux event channels (LTTng/Syslog) and their configuration, matching the detail given to Windows (ETW/Event Viewer).
  • Include Linux-focused sample queries and alert rules, and clarify any differences in setup or available metrics.
  • Ensure that references to tools and agents (e.g., Diagnostics Agent, Azure Monitor agent) include clear Linux instructions and links.
  • Add more examples for application monitoring using non-.NET stacks (e.g., Java, Node.js) on Linux clusters.
GitHub Create Pull Request
Service Fabric RunToCompletion semantics and specifications ...blob/main/articles/service-fabric/run-to-completion.md
Medium Priority View Details →
Scanned: 2026-02-13 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 notable Windows bias by exclusively providing Windows container examples (using Windows NanoServer images and Windows-specific commands), referencing Windows container compatibility, and only mentioning PowerShell and C# tools for querying deployment status. No Linux container examples, Linux commands, or cross-platform querying methods are provided, despite Service Fabric supporting containers in general.
Recommendations
  • Add equivalent Linux container examples (e.g., using Ubuntu or Alpine images) to demonstrate RunToCompletion semantics for Linux workloads.
  • Include Linux shell commands (such as Bash or CLI tools) for querying deployment status, or reference cross-platform Service Fabric CLI tools.
  • Clarify in the introduction whether RunToCompletion semantics are supported for Linux containers and, if so, provide guidance for Linux users.
  • Ensure examples and terminology are inclusive of both Windows and Linux environments where applicable.
GitHub Create Pull Request
Service Fabric Learn about Azure Service Fabric application security ...ric/service-fabric-application-and-service-security.md
Medium Priority View Details →
Scanned: 2026-02-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides a general overview of Service Fabric application security, but several sections show a Windows bias. Windows-specific features (e.g., Active Directory, gMSA, BitLocker) are mentioned with more detail or first, while Linux equivalents are missing or only briefly referenced. Examples and guidance for Linux clusters are limited, and some features (like disk encryption) reference Windows tools (PowerShell, BitLocker) without Linux parity or links.
Recommendations
  • Add explicit Linux examples and guidance for securing Service Fabric clusters, including disk encryption and certificate management.
  • Mention Linux tools and patterns (e.g., dm-crypt, LUKS, Linux user accounts) alongside Windows features, or clarify feature parity.
  • Provide links to Linux-specific documentation or third-party resources where Azure-native solutions are not available.
  • Ensure that sections referencing Windows tools (e.g., PowerShell, BitLocker) also reference Linux equivalents or note limitations.
  • Where features are Windows-only, clearly state this to avoid confusion.
GitHub Create Pull Request
Service Fabric Advanced Application Upgrade Topics ...-fabric/service-fabric-application-upgrade-advanced.md
Medium Priority View Details →
Scanned: 2026-02-13 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 extensive PowerShell examples and references, with no equivalent CLI or Linux/macOS instructions. All command-line guidance is given in PowerShell syntax, and Windows tooling (Visual Studio, PowerShell cmdlets) is mentioned first or exclusively. There is no mention of cross-platform alternatives such as Azure CLI, Bash, or Linux/macOS-compatible tools, despite Service Fabric supporting Linux clusters and cross-platform management.
Recommendations
  • Add Azure CLI examples for all PowerShell cmdlet usages, especially for service creation, updates, and upgrades.
  • Explicitly note which PowerShell commands can be run on Linux/macOS (using PowerShell Core), and provide Bash or shell script alternatives where possible.
  • Include guidance for managing Service Fabric applications on Linux clusters, referencing relevant tools and patterns.
  • Mention Visual Studio Code as a cross-platform IDE alongside Visual Studio.
  • Clarify any Windows-only limitations for features or commands, and provide Linux/macOS parity notes where applicable.
GitHub Create Pull Request
Service Fabric On-demand backup in Azure Service Fabric ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-backup-restore-service-ondemand-backup.md
Medium Priority View Details →
Scanned: 2026-02-13 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 on-demand backup in Azure Service Fabric is heavily biased toward Windows/PowerShell usage. All code examples use PowerShell, including REST API calls, and there is no mention of Linux/macOS-compatible tools or shell commands (such as Bash, curl, or Azure CLI). The prerequisite section requires installation of a PowerShell module, and there are no instructions for Linux users or alternative approaches. This creates friction for Linux/macOS users who may not have PowerShell installed or prefer native tools.
Recommendations
  • Add equivalent Bash/curl examples for REST API calls, showing how to trigger backups and track progress using standard Linux tools.
  • Mention and provide guidance for using Azure CLI (az) where possible, as it is cross-platform.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is required for all platforms, or if there are alternatives for Linux/macOS.
  • Reorganize examples so that cross-platform methods (REST API, Azure CLI) are presented before or alongside PowerShell examples.
  • Explicitly state platform requirements and provide links to PowerShell installation instructions for Linux/macOS if PowerShell is required.
GitHub Create Pull Request
Service Fabric Understanding periodic backup configuration ...-fabric-backuprestoreservice-configure-periodic-backup.md
Medium Priority View Details →
Scanned: 2026-02-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page is generally platform-neutral, but the 'File share' backup storage section exclusively references Windows-style file shares (\\server\share) and Integrated Windows Authentication, without mentioning Linux-compatible alternatives or SMB mounting instructions for Linux/macOS. Windows authentication patterns are described first and in detail, while no Linux-specific guidance or examples are provided for on-premises backup storage.
Recommendations
  • Add instructions or examples for configuring file share backup storage using SMB mounts on Linux/macOS clusters.
  • Mention Linux-compatible authentication options (e.g., username/password, Kerberos, or mounting via CIFS) for file shares.
  • Clarify whether Linux Service Fabric clusters can use file share backup storage, and if so, provide parity guidance.
  • Consider including a note about limitations or supported platforms for file share backup storage, especially if Windows-only.
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-02-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides both Windows and Linux guidance for Azure Service Fabric networking, but there are several areas where Windows examples, tools, or terminology are prioritized or exclusively mentioned. PowerShell and Windows-specific tasks are referenced before Linux equivalents, and some example links and templates are Windows-focused. Linux-specific instructions and examples are less prominent or missing in some sections.
Recommendations
  • Ensure Linux examples and CLI commands are provided alongside PowerShell/Windows examples, especially for cluster management and networking tasks.
  • Where PowerShell is referenced (e.g., Client API, Azure DevOps), add equivalent Azure CLI or bash examples for Linux users.
  • Balance the order of presentation so Linux and Windows are treated equally (e.g., mention Linux and Windows together, not always Windows first).
  • Provide ARM template samples for Linux clusters with NSG, not just Windows clusters.
  • Clarify when a feature or example is Windows-only, and offer Linux alternatives or note Linux limitations.
  • Expand references to Linux-specific networking considerations, such as firewall configuration or port management.
GitHub Create Pull Request
Service Fabric Restoring backup in Azure Service Fabric ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-backup-restore-service-trigger-restore.md
Medium Priority View Details →
Scanned: 2026-02-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page for restoring backup in Azure Service Fabric is heavily biased towards Windows and PowerShell usage. All code examples and instructions rely exclusively on PowerShell commands and modules (Microsoft.ServiceFabric.Powershell.Http), with no mention of Linux/macOS-compatible alternatives or CLI tools. The REST API is only demonstrated via PowerShell scripts, and there is no guidance for Bash, curl, or cross-platform approaches. The prerequisites and workflow assume a Windows environment, creating friction for Linux/macOS users.
Recommendations
  • Provide equivalent examples using Azure CLI, Bash scripts, or curl for REST API calls.
  • Document how to authenticate and connect to Service Fabric clusters from Linux/macOS, including certificate handling.
  • Mention any cross-platform tools or SDKs available for Service Fabric backup/restore operations.
  • Clarify whether the PowerShell module is required or if REST API calls can be made directly from any OS.
  • Add a section explicitly addressing Linux/macOS users, outlining supported workflows and limitations.
GitHub Create Pull Request
Service Fabric Azure Service Fabric infrastructure as Code Best Practices ...tps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-best-practices-infrastructure-as-code.md
Medium Priority View Details →
Scanned: 2026-02-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Service Fabric clusters, but PowerShell (a Windows-centric tool) is given its own section and is used for cluster upgrade operations without Linux alternatives. Windows-specific registry keys and VM template properties are discussed in detail, while Linux equivalents are not mentioned. The upgrade instructions for Service Fabric clusters rely solely on PowerShell commands, which are not natively available on Linux/macOS. Windows VM configuration is described before Linux, and disabling Windows Update is covered, but not Linux patching.
Recommendations
  • Provide Bash or Azure CLI equivalents for all PowerShell commands, especially for cluster upgrade operations.
  • Include Linux-specific instructions for VM patch management and configuration, such as disabling automatic updates on Linux VMs.
  • Mention Linux registry/file system equivalents or clarify when a step is Windows-only.
  • Ensure that Linux examples are presented alongside Windows examples, not only in the 'Next steps' section.
  • Add notes or links to Linux/macOS compatible tools for tasks currently described with Windows-only utilities.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation generally covers both Windows and Linux scenarios for Service Fabric security, but there is a noticeable pattern of Windows-first presentation, especially in sections about certificate management and encryption. Windows-specific tools (e.g., PowerShell, Windows Defender, Azure DSC) are discussed in detail, sometimes with limited or no Linux equivalents or guidance. Some sections, such as Windows Defender and security baselines, are Windows-only, but this is appropriate. However, in other areas, Windows examples and tools are presented before Linux equivalents, and some advanced configuration (e.g., antimalware exclusions) lacks Linux guidance.
Recommendations
  • When presenting cross-platform procedures (such as certificate creation and secret encryption), alternate the order of Windows and Linux examples or present them side-by-side.
  • Where Windows-specific tools (e.g., PowerShell, Windows Defender, Azure DSC) are discussed, add clear notes or equivalent Linux guidance (e.g., using ClamAV or other Linux antimalware solutions, or how to configure Linux security baselines).
  • For sections that only provide Windows examples (such as antimalware exclusions), explicitly state if there is no Linux equivalent or provide links to Linux security best practices.
  • Ensure that all critical security workflows (certificate management, secret encryption, managed identity usage) have complete Linux examples and not just links to separate articles.
  • Consider adding a summary table at the start of the document indicating which features or practices are Windows-only, Linux-only, or cross-platform.
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-02-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides a comprehensive reference for Service Fabric cluster settings, but exhibits some Windows bias. Windows terminology (e.g., 'Windows Fabric', 'Windows only' flags, 'MY' certificate store, NTLM authentication, Windows Defender Firewall) is used throughout, and Windows-specific settings are often mentioned before Linux equivalents. Some parameters (e.g., NTLM, Windows Update, log file settings) are marked 'Windows only' or default to Windows values, with Linux alternatives not always explained. Linux-specific settings (e.g., certificate folders, LinuxExternalExecutablePath) are present but less prominent. There are no explicit Linux configuration examples or guidance for Linux users, and some settings reference Windows APIs or documentation (e.g., CertGetCertificateChain) without Linux equivalents.
Recommendations
  • Add explicit Linux/macOS configuration examples or guidance for key settings, especially where Windows defaults or terminology are used.
  • Where parameters are Windows-only, clarify Linux equivalents or note if not applicable.
  • Ensure Linux-specific settings (e.g., certificate storage, log file paths, firewall configuration) are described with equal prominence.
  • Reference Linux documentation or APIs where Windows APIs are mentioned.
  • Review default values and descriptions to ensure Linux parity and avoid Windows-centric language where possible.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager - Placement Policies ...ce-manager-advanced-placement-rules-placement-policies.md
Medium Priority View Details →
Scanned: 2026-02-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation consistently provides PowerShell examples for configuring Service Fabric placement policies, but does not include equivalent Linux/macOS CLI or scripting examples (such as Azure CLI or Bash). PowerShell is primarily a Windows tool, and its exclusive use here creates friction for Linux/macOS users. Additionally, PowerShell examples are presented immediately after C# code samples, with no mention of cross-platform alternatives.
Recommendations
  • Add Azure CLI examples for each placement policy configuration, as Azure CLI is cross-platform and commonly used on Linux/macOS.
  • Mention and link to any relevant REST API documentation for configuring placement policies, which can be used from any OS.
  • Clarify whether PowerShell examples are usable on Linux/macOS (via PowerShell Core), or provide Bash scripting alternatives.
  • Explicitly state if certain configuration steps are only possible via PowerShell, and provide guidance for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager - Application Groups ...ice-fabric-cluster-resource-manager-application-groups.md
Medium Priority View Details →
Scanned: 2026-02-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page provides only PowerShell and C# examples for managing Service Fabric Application Groups. PowerShell is a Windows-centric tool, and no equivalent Linux/macOS CLI or scripting examples (such as Azure CLI, Bash, or REST API) are provided. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer cross-platform tools.
Recommendations
  • Add Azure CLI examples for all operations shown (creating, updating, querying, and removing Application Groups and capacities).
  • Include REST API examples where applicable, as these are platform-agnostic.
  • Mention that PowerShell examples are Windows-centric and provide guidance for Linux/macOS users on alternative tools.
  • Consider referencing or linking to documentation about Service Fabric CLI (sfctl), if relevant, and provide examples using it.
GitHub Create Pull Request
← Previous Page 62 of 99 Next →