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 626-650 of 2475 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-03-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 Replica Soft Delete in Service Fabric consistently references PowerShell APIs (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica) and provides examples and screenshots based on Windows tooling. There is no mention of Linux equivalents, CLI usage, or cross-platform SDK/API patterns. The documentation assumes familiarity with PowerShell and does not clarify whether these operations can be performed on Linux/macOS clusters or provide alternative commands for those platforms.
Recommendations
  • Add examples using Service Fabric CLI (sfctl), if available, for Linux/macOS users.
  • Clarify whether the PowerShell APIs are available or supported on Linux clusters, or provide equivalent REST/SDK usage.
  • Include screenshots and command outputs from Linux environments where possible.
  • Explicitly state platform requirements for the administrative APIs (PowerShell vs. CLI vs. SDK) and provide guidance for non-Windows users.
GitHub Create Pull Request
Service Fabric Add custom Service Fabric health reports ...rticles/service-fabric/service-fabric-report-health.md
Medium Priority View Details →
Scanned: 2026-03-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 extensive PowerShell examples and references, with no equivalent Linux/macOS CLI examples (such as Bash or Azure CLI). Windows tools and patterns (PowerShell cmdlets, Windows-style paths) are mentioned exclusively and before REST or API alternatives. This creates friction for Linux/macOS users, who are not shown how to perform health reporting tasks using their native tools.
Recommendations
  • Add equivalent Bash or Azure CLI examples for health reporting tasks, especially where PowerShell is used.
  • Clarify whether Service Fabric health reporting can be performed from Linux/macOS nodes and, if so, provide guidance for those environments.
  • Mention cross-platform REST usage earlier and provide concrete examples for Linux/macOS users (e.g., using curl).
  • Where PowerShell is referenced, note its availability on Linux/macOS, or provide alternatives if not supported.
  • Ensure that all configuration and reporting steps are documented for both Windows and Linux environments, including any differences in tooling or prerequisites.
GitHub Create Pull Request
Service Fabric Configure the upgrade of a Service Fabric application ...abric/service-fabric-visualstudio-configure-upgrade.md
Medium Priority View Details →
Scanned: 2026-03-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation focuses exclusively on upgrading Service Fabric applications using Visual Studio and PowerShell, both of which are Windows-centric tools. There are no examples or guidance for Linux/macOS users, such as using cross-platform CLI tools or alternative workflows. The only upgrade methods described are via Visual Studio (Windows-only) and PowerShell (primarily Windows), with no mention of Azure CLI, REST API, or Linux-compatible tools.
Recommendations
  • Add instructions and examples for upgrading Service Fabric applications using cross-platform tools such as Azure CLI or REST API.
  • Mention and link to any Linux/macOS-compatible workflows for Service Fabric application upgrades.
  • Clarify if PowerShell Core (pwsh) is supported for Service Fabric cmdlets on Linux/macOS, and provide relevant examples if so.
  • If Visual Studio is required, explicitly state its Windows-only nature and suggest alternatives for non-Windows users.
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-03-01 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page presents RunToCompletion semantics in Service Fabric with a strong Windows bias. All code examples use Windows containers (nanoserver), Windows-specific commands (cmd, echo, ping, set, exit), and reference Windows container compatibility. Querying deployment status is shown only via PowerShell and C# APIs, with no mention of Linux equivalents or CLI usage. There are no examples or guidance for Linux containers or Linux-based workflows, despite Service Fabric supporting Linux containers.
Recommendations
  • Add code examples using Linux containers (e.g., Ubuntu or Alpine images) and Linux shell commands.
  • Include instructions for querying deployment status using Azure CLI or Service Fabric CLI (sfctl), which are cross-platform.
  • Clarify whether RunToCompletion semantics are supported for Linux containers and, if so, provide parity in examples and guidance.
  • Present Windows and Linux examples side-by-side or indicate platform-specific differences explicitly.
  • Mention any limitations or considerations for Linux container scenarios, if applicable.
GitHub Create Pull Request
Service Fabric Capacity planning and scaling for Azure Service Fabric ...bric/service-fabric-best-practices-capacity-scaling.md
Medium Priority View Details →
Scanned: 2026-03-01 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides several manual scaling instructions and examples using PowerShell cmdlets (e.g., Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState) without mentioning Linux/macOS equivalents or cross-platform CLI alternatives. PowerShell is referenced as the primary tool for manual operations, and Windows-specific tooling is presented first or exclusively in step-by-step guides. However, the page does acknowledge Linux clusters and links to Linux-specific cluster creation documentation, indicating some awareness of cross-platform needs.
Recommendations
  • Add Azure CLI or Service Fabric CLI (sfctl) examples for scaling operations, especially for disabling/removing nodes, to support Linux/macOS users.
  • Clarify whether PowerShell cmdlets are available cross-platform (via PowerShell Core), or provide alternatives where they are not.
  • Where PowerShell is used, mention if/how Linux users can perform equivalent actions, and link to relevant Linux tooling documentation.
  • Ensure step-by-step guides include both Windows and Linux approaches, or explicitly state if a step is Windows-only.
GitHub Create Pull Request
Service Fabric Application upgrade: data serialization ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-application-upgrade-data-serialization.md
Medium Priority View Details →
Scanned: 2026-03-01 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page references Windows-centric tools (Visual Studio and PowerShell) for application upgrades in the 'Next steps' section, with no mention of Linux/macOS alternatives or CLI options. Examples and recommendations are focused on C# and .NET serialization, which are cross-platform, but the upgrade guidance is Windows-oriented.
Recommendations
  • Add guidance or links for upgrading Service Fabric applications using cross-platform tools such as Azure CLI or REST APIs.
  • Mention Linux/macOS-compatible development environments (e.g., VS Code, JetBrains Rider) alongside Visual Studio.
  • Clarify whether PowerShell instructions are compatible with PowerShell Core on Linux/macOS, or provide Bash/CLI equivalents.
  • Explicitly state if certain upgrade steps are Windows-only, and provide Linux/macOS alternatives 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-03-01 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides code examples for configuring Service Fabric placement policies using C# and PowerShell. All command-line examples use PowerShell, which is Windows-centric, and there are no equivalent examples for Linux/macOS environments (e.g., Bash, Azure CLI, or REST API). The documentation implicitly assumes Windows as the primary platform for operational tasks, potentially creating friction for Linux/macOS users.
Recommendations
  • Add Azure CLI or REST API examples for configuring placement policies, as these are cross-platform and usable from Linux/macOS.
  • Explicitly mention whether PowerShell examples are supported on Linux (via PowerShell Core), or provide Bash equivalents if possible.
  • Clarify any platform-specific limitations or requirements for Service Fabric management tools.
  • Consider including a section on managing Service Fabric clusters from Linux/macOS, referencing relevant tools and documentation.
GitHub Create Pull Request
Service Fabric Deny assignment policy for Service Fabric managed clusters ...cles/service-fabric/managed-cluster-deny-assignment.md
Medium Priority View Details →
Scanned: 2026-03-01 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides examples and references to Azure PowerShell modules for managing Service Fabric managed clusters, with PowerShell mentioned first and in detail. While Azure CLI and ARM/Bicep are also referenced, PowerShell is emphasized, and there are no explicit Linux/macOS shell examples or callouts. The use of PowerShell-centric guidance may create friction for Linux/macOS users, though Azure CLI and ARM tools are cross-platform.
Recommendations
  • Add explicit Azure CLI command examples for key operations (e.g., deleting NodeType, restarting/reimaging scale sets) alongside PowerShell examples.
  • Clarify that Azure CLI and ARM/Bicep tools are fully cross-platform and suitable for Linux/macOS users.
  • Consider providing bash/zsh shell snippets or guidance for Linux/macOS users where appropriate.
  • Ensure that references to PowerShell are balanced with equivalent CLI guidance, especially in 'Best practices' sections.
GitHub Create Pull Request
Service Fabric Cluster Resource Manager - Management Integration ...fabric-cluster-resource-manager-management-integration.md
Medium Priority View Details →
Scanned: 2026-03-01 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, with no equivalent Linux/macOS CLI example (such as using sfctl or REST API). The PowerShell example is presented as the sole method, and Windows paths are referenced, suggesting a Windows-first approach. No Linux-specific tools or cross-platform guidance is given for the health report example.
Recommendations
  • Add equivalent Linux/macOS examples using sfctl (Service Fabric CLI) or REST API for querying partition health.
  • Mention that PowerShell is Windows-specific and provide guidance for non-Windows users.
  • Include cross-platform instructions and clarify tool availability for Linux/macOS administrators.
  • Where possible, show both Windows and Linux commands side-by-side.
GitHub Create Pull Request
Service Fabric Custom Image .../articles/service-fabric/how-to-deploy-custom-image.md
Medium Priority View Details →
Scanned: 2026-03-01 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page exhibits moderate Windows bias. Windows terminology and examples are presented first and most prominently, including the use of 'custom windows images' and a PowerShell command for role assignment. Linux equivalents are referenced but not demonstrated, and the ARM template examples are generic but lack explicit Linux-focused guidance.
Recommendations
  • Clarify that custom images can be Linux-based as well, and provide explicit examples for Linux custom images.
  • Include Linux CLI (az) commands for role assignment alongside the PowerShell example.
  • Ensure that ARM template examples show both Windows and Linux image scenarios, or note any differences.
  • Reorder sections to treat Windows and Linux equally, or explicitly state if Windows is required for certain steps.
GitHub Create Pull Request
Service Fabric Advanced Application Upgrade Topics ...-fabric/service-fabric-application-upgrade-advanced.md
Medium Priority View Details →
Scanned: 2026-03-01 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 numerous PowerShell-based examples and references, with no equivalent CLI or Linux/macOS instructions. Windows tools and patterns (PowerShell cmdlets) are used exclusively for key upgrade operations, and PowerShell is referenced first and often. There are no examples using Service Fabric CLI (sfctl), Bash, or cross-platform tools, which creates friction for Linux/macOS users.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and supported on Linux/macOS.
  • Where PowerShell cmdlets are referenced, also mention the corresponding sfctl command or REST API, if available.
  • Clarify which operations are possible via CLI or REST API for non-Windows environments.
  • Include Bash or shell script examples where appropriate.
  • Update 'Next steps' to include links to Linux/macOS upgrade tutorials or CLI-based guides.
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-03-01 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-specific examples (e.g., PowerShell commands, Windows Defender, Windows security baselines) are often presented first or in greater detail. Windows tools and patterns (PowerShell, Windows Defender, DSC) are mentioned exclusively or before Linux equivalents. Linux examples are present for certificate generation and secret encryption, but some sections (e.g., Windows Defender, security baselines) are Windows-only without Linux alternatives or parity suggestions.
Recommendations
  • Ensure Linux examples are presented alongside Windows examples, not after or as an afterthought.
  • Where Windows-specific tools (e.g., PowerShell, Windows Defender, DSC) are discussed, provide Linux equivalents or clarify their absence.
  • For security baseline recommendations, reference industry-standard Linux baselines (e.g., CIS benchmarks) and configuration management tools (e.g., Ansible, Chef, Puppet) for Linux clusters.
  • Explicitly note when a feature or tool is Windows-only and suggest Linux alternatives or best practices.
  • Consider balancing the order of examples so Linux and Windows are equally represented in critical sections.
GitHub Create Pull Request
Service Fabric Azure Service Fabric container application manifest examples ...abric/service-fabric-manifest-example-container-app.md
Medium Priority View Details →
Scanned: 2026-03-01 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 manifest examples are based on a Windows Server 2016 container sample, and Windows-specific concepts (such as 'winver' for OS build detection and Windows file paths) are referenced. Windows tools (e.g., 'winver' command) are mentioned exclusively for OS build identification, and Windows paths (e.g., 'c:\VolumeTest\Data') are used in volume binding examples. Linux equivalents (such as 'uname' for OS build or Linux file paths) are not provided. Certificate handling is explained for both Windows (PFX) and Linux (PEM), but Linux-specific manifest examples or guidance are missing.
Recommendations
  • Provide Linux-based manifest examples or reference a Linux container sample repository.
  • Mention Linux tools (e.g., 'uname -r') for OS build/version detection alongside 'winver'.
  • Show Linux file path conventions (e.g., '/mnt/volume/data') in volume binding examples.
  • Clarify which manifest settings are cross-platform and which are Windows-specific.
  • Add explicit guidance or links for Linux Service Fabric container deployments.
GitHub Create Pull Request
Service Fabric Health monitoring in Service Fabric ...s/service-fabric/service-fabric-health-introduction.md
Medium Priority View Details →
Scanned: 2026-03-01 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation provides a PowerShell-only example for reporting and evaluating application health in Service Fabric, without offering equivalent Linux/macOS CLI or REST API examples. The use of PowerShell cmdlets is presented as the primary method, and no cross-platform alternatives (such as Azure CLI, REST, or SDK code samples) are shown. This creates friction for Linux/macOS users, who may not have access to PowerShell or the cmdlets referenced.
Recommendations
  • Add equivalent examples using REST API calls for health reporting and querying, which are cross-platform.
  • Include Azure CLI or .NET SDK code samples for health report submission and evaluation.
  • Explicitly mention Linux/macOS-compatible methods alongside PowerShell, and clarify platform support for each example.
  • Consider showing REST or cross-platform examples first, or in parallel with PowerShell examples.
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-03-01 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides PowerShell examples and references PowerShell cmdlets for service creation and management, with no equivalent Linux CLI (e.g., Azure CLI, Bash) examples. PowerShell is mentioned first and most prominently, which may create friction for Linux/macOS users, although REST API and .NET examples are also provided.
Recommendations
  • Add Azure CLI or Bash examples for service creation and management tasks, especially for commands like creating services with Exclusive Process model.
  • Mention cross-platform tools (such as Azure CLI) alongside PowerShell, and clarify their applicability.
  • Provide guidance or links for Linux/macOS users on how to perform equivalent operations.
  • Ensure REST API examples are highlighted as cross-platform options.
GitHub Create Pull Request
Service Fabric Networking patterns for Azure Service Fabric ...s/service-fabric/service-fabric-patterns-networking.md
Medium Priority View Details →
Scanned: 2026-03-01 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page consistently uses PowerShell for deployment examples and command-line instructions, with no mention of Azure CLI or Bash equivalents. Windows tools and patterns (such as RDP and Windows directory paths) are referenced, and Windows-style command prompts are shown. Linux/macOS users are not provided with alternative instructions or examples, creating friction for those not using Windows.
Recommendations
  • Provide Azure CLI and Bash equivalents for all PowerShell deployment commands.
  • Include examples using Linux/macOS directory paths and shell prompts.
  • Mention SSH as a remote access method alongside RDP, and provide instructions for Linux/macOS users.
  • Clearly indicate when PowerShell is required, and offer guidance for cross-platform users.
  • Add notes or sections specifically addressing Linux/macOS workflows for Service Fabric networking setup.
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-03-01 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation provides comprehensive coverage of X.509 certificate-based authentication in Service Fabric clusters, but exhibits moderate Windows bias. Windows-specific concepts (certificate stores, Win32 CryptoAPI, event logs, error codes, and troubleshooting tools) are mentioned first or exclusively, with Linux equivalents only briefly referenced. Troubleshooting and configuration examples focus on Windows paths and tools, and some advanced troubleshooting steps (like CAPI2 logging) are Windows-only. Linux-specific guidance is minimal and often relegated to parenthetical notes.
Recommendations
  • Expand Linux-specific instructions, paths, and troubleshooting steps (e.g., detail how to access logs and certificate stores on Linux nodes).
  • Provide Linux/macOS equivalents for Windows-centric error codes, tools, and troubleshooting workflows.
  • Include explicit Linux examples for certificate configuration and management, not just brief mentions.
  • Clarify any differences in certificate handling between Windows and Linux nodes, especially for advanced scenarios.
  • Add links or references to Linux documentation for Service Fabric certificate management and troubleshooting.
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-03-01 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides a mix of conceptual guidance and hands-on examples for managing certificates in Azure Service Fabric clusters. While much of the content is platform-agnostic and focuses on Azure-native mechanisms (Key Vault, VM extensions, ARM templates), there is a notable bias toward Windows in several areas: PowerShell is the only scripting example provided for certificate enrollment, and the Key Vault VM extension is described exclusively in its Windows variant. Additionally, certain explanations (such as certificate linking and S-channel) are explicitly Windows-specific, and Windows terminology/tools are referenced before any Linux alternatives (if any exist). There are no Linux/bash examples for certificate enrollment or provisioning, and the documentation does not mention the Key Vault VM extension for Linux, which exists and is relevant for cross-platform clusters.
Recommendations
  • Add bash/CLI examples for certificate enrollment and provisioning alongside PowerShell examples.
  • Mention and link to the Key Vault VM extension for Linux (https://learn.microsoft.com/en-us/azure/virtual-machines/extensions/key-vault-linux) when discussing provisioning agents.
  • Clarify which mechanisms and examples are Windows-specific and provide Linux/macOS equivalents where possible.
  • When discussing certificate linking and S-channel, explicitly state that these are Windows-only features and describe Linux alternatives (such as OpenSSL or other certificate handling mechanisms).
  • Ensure that ARM template snippets and deployment steps are platform-neutral or indicate any OS-specific requirements.
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-03-01 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides examples for configuring Service Fabric managed cluster node types using Azure Portal, ARM templates, and PowerShell. PowerShell is the only CLI example provided, with no mention of Azure CLI or Bash scripting, which are more common on Linux/macOS. The PowerShell examples are presented alongside Portal and ARM template methods, but there is no Linux-specific guidance or parity for command-line operations. The documentation does not reference Windows-only features, so the bias is not intentional.
Recommendations
  • Add Azure CLI examples for all operations (add, remove, scale, configure placement properties, etc.) to ensure Linux/macOS users have equivalent command-line guidance.
  • Mention Bash scripting or provide links to Azure CLI documentation for Service Fabric managed clusters.
  • Clarify that PowerShell examples are cross-platform (if applicable), or explicitly state any limitations for Linux/macOS users.
  • Consider listing Azure CLI examples before or alongside PowerShell to avoid 'windows_first' bias.
GitHub Create Pull Request
Service Fabric Introduction to the Service Fabric Infrastructure Service .../articles/service-fabric/infrastructure-service-faq.md
Medium Priority View Details →
Scanned: 2026-03-01 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 alternatives. While Service Fabric clusters can be managed from Linux, the examples and tooling focus on Windows/PowerShell, creating friction for Linux/macOS users.
Recommendations
  • Add equivalent CLI examples for Linux/macOS users, such as using Azure CLI or REST API where possible.
  • Mention cross-platform management tools or clarify if Service Fabric Explorer is available on Linux/macOS.
  • Provide guidance for Linux users on how to perform the same operations (e.g., bypassing Infrastructure Service) without PowerShell.
  • Explicitly state if certain commands or tools are Windows-only, and offer alternatives or workarounds.
GitHub Create Pull Request
Service Fabric Monitor Azure Service Fabric ...main/articles/service-fabric/monitor-service-fabric.md
Medium Priority View Details →
Scanned: 2026-03-01 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 both Windows and Linux Service Fabric clusters, but there are several areas where Windows tools and examples are mentioned first or exclusively. Windows-specific tools (e.g., Event Log/Event Viewer, Diagnostics Agent) are referenced before Linux equivalents, and some tutorials/examples focus on .NET/Windows scenarios. Linux-specific guidance is present but often secondary, and some configuration details for Linux are only linked, not explained inline.
Recommendations
  • Ensure Linux monitoring tools and workflows are described with equal prominence and detail as Windows equivalents.
  • Provide Linux-specific examples and tutorials directly in the documentation, not just as external links.
  • When referencing tools (e.g., EventStore, Diagnostics Agent), clarify their availability and alternatives for Linux clusters.
  • Add sample code and configuration snippets for Linux (e.g., using Syslog, LTTng, Application Insights for Linux workloads).
  • Where Windows tools are mentioned (e.g., Event Viewer), immediately follow with Linux alternatives (e.g., Syslog, LTTng) and how to access equivalent data.
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-03-01 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation contains evidence of Windows bias, notably in the warning suggesting the use of Visual Studio and referencing a Windows file path for schema validation. Additionally, the mention of using the ServiceFabric PowerShell module to create service instances implies Windows-centric tooling. Windows examples and tools are presented first and exclusively, with no Linux/macOS alternatives or parity guidance.
Recommendations
  • Provide instructions for validating manifest XML schema using cross-platform tools (e.g., VS Code, xmllint, or other XML editors) and reference Linux/macOS file paths if applicable.
  • Mention and provide examples for using Service Fabric CLI (sfctl) or REST APIs for service management, which are cross-platform, alongside PowerShell.
  • Ensure that tooling recommendations (such as Visual Studio) are accompanied by alternatives for Linux/macOS users (e.g., VS Code, JetBrains Rider, or command-line tools).
  • Explicitly state if certain features or tools are Windows-only, and offer Linux/macOS equivalents or workarounds where possible.
GitHub Create Pull Request
Service Fabric Service Fabric Explorer blocking operations ...ged-cluster-service-fabric-explorer-blocking-operation.md
Medium Priority View Details →
Scanned: 2026-03-01 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides management guidance for Service Fabric Explorer and ARM-managed clusters. It consistently recommends Az PowerShell cmdlets (e.g., Remove-AzResource, AzSF PowerShell) for operations, and references PowerShell before or instead of Azure CLI equivalents. While az resource (Azure CLI) is mentioned once, PowerShell is the dominant example format. There are no Linux-specific examples or explicit parity guidance.
Recommendations
  • Provide Azure CLI equivalents for all PowerShell cmdlets, especially for operations like unprovisioning application type versions, creating applications, and services.
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Where possible, show both PowerShell and Azure CLI examples side-by-side.
  • Clarify if any operations are PowerShell-only, and offer alternatives or workarounds for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Migrate an Azure Service Fabric cluster to availability zone support ...ce-fabric/migrate-service-fabric-availability-zones.md
Medium Priority View Details →
Scanned: 2026-03-01 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page provides migration guidance for Azure Service Fabric clusters to availability zone support. While much of the content is platform-neutral (focused on ARM templates and Azure resources), the step-by-step migration for clusters with Basic SKU load balancer and IP resources relies exclusively on PowerShell commands and Windows-centric tooling (e.g., Service Fabric PowerShell cmdlets). Additionally, Windows-based examples (such as sample templates and file paths) are referenced before Linux equivalents, and Linux-specific guidance is minimal or absent.
Recommendations
  • Provide equivalent Bash/CLI examples for all PowerShell steps, especially for disabling/removing nodes and updating resources.
  • Reference and link to Linux/Ubuntu sample templates alongside Windows templates in migration sections.
  • Clarify which steps are platform-agnostic and which require Windows, and offer Linux alternatives where possible.
  • Explicitly mention if certain operations (e.g., Service Fabric node management) can be performed via Azure CLI or REST API, and provide those examples.
  • Ensure file paths and certificate handling are explained for both Windows and Linux environments.
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-03-01 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 Windows bias. Windows-specific features (like AD domain accounts, gMSA, BitLocker) are mentioned with more detail or exclusively, while Linux equivalents are missing or relegated to TODO comments. Examples and guidance often reference Windows tools or patterns first, and Linux-specific instructions are sparse or absent.
Recommendations
  • Add explicit Linux examples for securing disks at rest (e.g., using Azure Disk Encryption with Linux clusters).
  • Provide parity in guidance for running services under different user accounts on Linux clusters, including how to configure principals and policies.
  • Include Linux-specific instructions for certificate management and container security, matching the detail given for Windows (e.g., gMSA alternatives).
  • Ensure that API gateway and service communication examples include Linux-friendly tools and patterns, not just ASP.NET Core or Windows-centric approaches.
  • Remove or resolve TODO comments regarding Linux disk encryption and provide actionable guidance.
GitHub Create Pull Request
← Previous Page 26 of 99 Next →