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 2051-2075 of 2475 flagged pages
Service Fabric Describing Azure Service Fabric apps and services ...ic/service-fabric-application-and-service-manifests.md
Medium Priority View Details →
Scanned: 2026-02-01 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page on describing Azure Service Fabric apps and services shows mild Windows bias. It references Windows file paths (e.g., 'C:\Program Files\Microsoft SDKs\Service Fabric\schemas\ServiceFabricServiceModel.xsd'), recommends using Visual Studio (a Windows-centric tool) for schema validation, and mentions the ServiceFabric PowerShell module for service creation before any Linux equivalents. There are no explicit Linux/macOS examples or tooling recommendations, and Windows terminology appears first in several places.
Recommendations
  • Add equivalent instructions for Linux/macOS users, such as how to locate schema files on those platforms.
  • Recommend cross-platform editors (e.g., VS Code) for XML schema validation and intelli-sense.
  • Mention Linux CLI tools (e.g., Azure CLI, sfctl) for service creation alongside PowerShell.
  • Provide examples or notes for Linux/macOS file paths and environment setup.
  • Ensure that references to Windows tools are balanced with Linux/macOS alternatives where possible.
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-02-01 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation references PowerShell and Visual Studio as primary tools for application upgrade walkthroughs, both of which are traditionally Windows-centric. PowerShell is available on Linux/macOS, but Service Fabric PowerShell modules and Visual Studio are most commonly used on Windows. No explicit Linux/macOS CLI or cross-platform upgrade example is provided, and the documentation does not mention Linux-native tools or workflows.
Recommendations
  • Add equivalent upgrade walkthroughs using Azure CLI or Service Fabric CLI (sfctl), which are cross-platform.
  • Clarify whether PowerShell examples work on Linux/macOS, or provide Bash/shell alternatives where appropriate.
  • Mention cross-platform development environments (e.g., VS Code) or provide links to documentation for upgrading applications from non-Windows systems.
  • Explicitly state platform requirements for each tool or example, so users know if a Windows environment is required.
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-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 most security best practices, but Windows examples and tools (such as PowerShell and Windows Defender) are often presented first or exclusively. Some sections, like Windows Defender and security baselines, are Windows-specific, but these are appropriately marked. However, in sections like certificate encryption, Windows/PowerShell examples precede Linux/openssl examples, and Windows-specific tooling is referenced more frequently.
Recommendations
  • Alternate the order of Windows and Linux examples, or present them side-by-side to avoid implicit prioritization.
  • Clearly label Windows-only sections and provide equivalent Linux guidance or explicitly state when no Linux equivalent exists.
  • Where possible, reference cross-platform tools and patterns before platform-specific ones.
  • Expand Linux-specific security baseline recommendations (e.g., CIS benchmarks, Linux antimalware options) to match Windows coverage.
  • Ensure that all code samples and configuration steps are available for both platforms, or link to Linux/macOS equivalents.
GitHub Create Pull Request
Service Fabric Architecture of Azure Service Fabric ...articles/service-fabric/service-fabric-architecture.md
Medium Priority View Details →
Scanned: 2026-02-01 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation references PowerShell cmdlets and Windows security as primary management and security mechanisms, without mentioning Linux equivalents (such as Azure CLI, Bash, or Linux security integration). Windows tools and patterns are mentioned first and exclusively in key management sections, creating friction for Linux/macOS users seeking parity.
Recommendations
  • Include Azure CLI and REST API examples for management tasks alongside PowerShell cmdlets.
  • Clarify whether management operations (provision, deploy, patch, upgrade) can be performed using cross-platform tools, and provide links or examples.
  • Mention Linux-compatible security mechanisms (such as X509 certificates) before or alongside Windows security.
  • Add a note on platform support for Service Fabric management and clarify any Windows-only limitations.
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-01 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation consistently provides PowerShell examples for managing Service Fabric Application Groups, with no equivalent examples for Linux/macOS users (e.g., Azure CLI, Bash, or REST API). PowerShell is primarily a Windows tool, and its exclusive use in examples creates friction for users operating Service Fabric clusters on Linux or from non-Windows environments. The C# SDK examples are cross-platform, but operational/command-line instructions are Windows-centric.
Recommendations
  • Add equivalent Azure CLI or REST API examples for all PowerShell commands shown, especially for creating, updating, and querying application groups.
  • Explicitly mention which commands/tools are available on Linux/macOS and provide links to relevant cross-platform documentation.
  • If certain features are only available via PowerShell, clearly state this limitation and suggest alternatives or workarounds for Linux users.
  • Consider including Bash script examples or instructions for using Service Fabric CLI (sfctl), if applicable.
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-02-01 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides command-line examples exclusively using PowerShell cmdlets for managing node tags and service tag requirements in Azure Service Fabric. There are no equivalent examples for Linux/macOS users, such as Bash, CLI, or REST API usage. This creates friction for users operating Service Fabric clusters on non-Windows environments.
Recommendations
  • Add examples using Azure CLI or Bash scripts for managing node tags and service tag requirements.
  • Include REST API sample requests for tag operations, as these are platform-agnostic.
  • Explicitly mention how Linux/macOS users can perform these tasks, and provide links to relevant cross-platform tools or documentation.
  • Clarify whether PowerShell Core (cross-platform) is supported, and if so, provide usage notes.
GitHub Create Pull Request
Service Fabric Azure Service Fabric hosting activation and deactivation life cycle ...les/service-fabric/service-fabric-hosting-lifecycle.md
Medium Priority View Details →
Scanned: 2026-02-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 for Azure Service Fabric hosting activation and deactivation life cycle exhibits moderate Windows bias. The only explicit example for deploying or managing Service Fabric applications refers to PowerShell, a Windows-centric tool. The 'Next steps' section links specifically to PowerShell-based deployment/removal instructions, with no mention of Linux equivalents (such as Service Fabric CLI or REST API). There are no examples or references to Linux/macOS workflows, tools, or commands, and no mention of cross-platform deployment patterns.
Recommendations
  • Include Linux/macOS deployment examples using Service Fabric CLI (sfctl) or REST API alongside PowerShell instructions.
  • Add references or links to documentation for Linux/macOS Service Fabric node management.
  • Clarify which steps or tools are cross-platform and which are Windows-specific.
  • Where PowerShell is referenced, provide equivalent CLI commands for Linux users.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Events ...es/service-fabric/service-fabric-diagnostics-events.md
Medium Priority View Details →
Scanned: 2026-02-01 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page on Azure Service Fabric Events primarily references Windows-specific logging mechanisms (ETW/Windows Event logs) and the Windows Azure diagnostics agent. There are no explicit examples or guidance for accessing or configuring Service Fabric events on Linux clusters, nor are Linux-native logging tools or patterns mentioned. This may create friction for Linux users seeking parity.
Recommendations
  • Add explicit documentation or examples for accessing Service Fabric events on Linux clusters, including references to Linux-native logging mechanisms (e.g., syslog, journald, or custom log files).
  • Clarify whether the described diagnostics agent and event logging mechanisms apply to both Windows and Linux clusters, or provide Linux-specific alternatives if not.
  • Include Linux-focused guidance or links to relevant documentation for configuring diagnostics and accessing events on Linux-based Service Fabric clusters.
  • Ensure that any references to monitoring tools or agents are inclusive of both Windows and Linux environments, or clearly state platform limitations.
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-01 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page provides several examples and deployment instructions using PowerShell commands and Windows file paths, with Windows-centric terminology and tooling presented first or exclusively. Linux equivalents are mentioned only briefly and lack detailed examples, which may create friction for Linux/macOS users.
Recommendations
  • Include equivalent Linux/macOS deployment instructions, such as using Azure CLI or Service Fabric CLI (sfctl), alongside PowerShell examples.
  • Provide Linux file path references and clarify differences in certificate storage (e.g., /var/lib/sfcerts) with concrete examples.
  • Add explicit Linux/macOS code snippets for common tasks (e.g., application deployment, endpoint configuration) to ensure parity.
  • Where PowerShell is used, note the Linux/macOS alternative and link to relevant documentation.
GitHub Create Pull Request
Service Fabric Define Service Configuration in StartupServices.xml for a Service Fabric Application ...service-fabric/service-fabric-startupservices-model.md
Medium Priority View Details →
Scanned: 2026-02-01 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is notably Windows-centric, focusing exclusively on Visual Studio workflows and referencing Windows-specific tools and patterns (e.g., F5/Ctrl+F5, right-click->Publish, Visual Studio project templates). There are no examples or guidance for Linux/macOS users or for cross-platform Service Fabric development and deployment. The only alternative deployment methods mentioned are ARM and PowerShell cmdlets, but these are referenced briefly and not demonstrated. The documentation assumes use of Visual Studio, which is primarily a Windows tool, and omits any mention of Linux-compatible workflows, such as using Service Fabric CLI (sfctl) or cross-platform editors.
Recommendations
  • Add equivalent instructions and examples for deploying Service Fabric applications using Linux/macOS tools, such as sfctl, Azure CLI, or VS Code.
  • Clarify which features are Visual Studio-specific and provide alternative cross-platform workflows where possible.
  • Include sample commands for Linux/macOS environments for tasks like building, deploying, and managing Service Fabric applications.
  • Reference cross-platform Service Fabric SDKs and document how StartupServices.xml fits into non-Visual Studio workflows, if supported.
  • Explicitly state any limitations or lack of support for StartupServices.xml outside Visual Studio, and guide Linux/macOS users to supported 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-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 a comprehensive overview of certificate management in Azure Service Fabric clusters, but exhibits a moderate Windows bias. PowerShell is the only scripting language shown for programmatic certificate enrollment, and the Key Vault VM extension is described exclusively in its Windows variant. The documentation references Windows-specific certificate store locations and behaviors (such as ACLing and S-channel linking), and Windows-centric terminology and examples appear before or instead of Linux equivalents. There is little to no mention of Linux/macOS-specific certificate provisioning or automation approaches, and no Bash/CLI examples are provided.
Recommendations
  • Add equivalent Bash/Azure CLI examples for certificate enrollment and management, especially for tasks currently shown only in PowerShell.
  • Clarify whether the Key Vault VM extension and Service Fabric VM extension have Linux support, and if so, provide Linux-specific instructions and examples.
  • Discuss certificate store locations and ACLing approaches for Linux nodes, if supported.
  • Explicitly note any limitations or differences for Linux/macOS clusters, and link to relevant documentation.
  • Where Windows-specific features (like S-channel linking) are discussed, state their applicability and alternatives for Linux environments.
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-01 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 exhibits a moderate Windows bias. Windows-specific tools, APIs, and troubleshooting steps are mentioned first or exclusively (e.g., references to the Windows certificate store, Win32 CryptoAPI, CAPI2 logging, and error codes). Linux equivalents are only briefly mentioned or omitted, and there are no concrete Linux/macOS command examples or troubleshooting guidance. This may create friction for Linux users configuring or diagnosing Service Fabric clusters.
Recommendations
  • Provide explicit Linux/macOS equivalents for certificate storage paths, management commands, and troubleshooting steps (e.g., show how to check certificates in /var/lib/sfcerts, use OpenSSL, or relevant Linux logs).
  • When referencing Windows-specific APIs or logs (e.g., Win32 CryptoAPI, CAPI2 logging), add parallel guidance for Linux (e.g., OpenSSL verification, syslog, journalctl, or Service Fabric logs on Linux).
  • Include Linux/macOS-specific error messages and common troubleshooting steps.
  • Where possible, show both Windows and Linux examples side-by-side, especially for certificate installation, validation, and cluster manifest configuration.
  • Clarify any platform-specific limitations or differences in Service Fabric certificate handling.
GitHub Create Pull Request
Service Fabric Custom Image .../articles/service-fabric/how-to-deploy-custom-image.md
Medium Priority View Details →
Scanned: 2026-02-01 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referring to 'custom windows images' throughout, providing only PowerShell examples for role assignment, and mentioning Windows/PowerShell tools before their Linux equivalents. Although there are references to Linux custom image creation and Azure CLI, no Linux-specific command examples or workflows are provided for key steps such as role assignment.
Recommendations
  • Clarify that Service Fabric Managed Cluster supports both Windows and Linux node types if applicable.
  • Provide Linux-specific examples for role assignment (e.g., using Azure CLI or Bash).
  • Include ARM template examples for both Windows and Linux images, or clarify any OS-specific differences.
  • Present Linux and Windows workflows in parallel, rather than focusing on Windows terminology and examples.
  • Ensure references to documentation for both Windows and Linux image creation are equally prominent.
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-01 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides detailed PowerShell examples for managing Service Fabric managed cluster node types but does not mention or provide equivalent examples for Linux/macOS users (e.g., Azure CLI, Bash). All command-line automation is shown using PowerShell, which is primarily a Windows tool, and there is no guidance for users on non-Windows platforms. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other tools.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all command-line operations (adding, removing, scaling node types, etc.).
  • Explicitly state that PowerShell examples can be run cross-platform (if true), or provide installation guidance for PowerShell on Linux/macOS.
  • Where possible, provide Bash or shell script equivalents, or reference Azure CLI documentation for equivalent tasks.
  • Clarify in each section that users can choose between PowerShell and Azure CLI, and link to relevant Azure CLI 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-02-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 links primarily for Azure PowerShell modules when describing best practices for managing Service Fabric managed clusters. PowerShell is a Windows-centric tool, and its examples are listed before Azure CLI and other cross-platform options. While Azure CLI and ARM templates are mentioned, actionable examples and direct links for critical operations (delete, restart, reimage) are given only for PowerShell, with no equivalent CLI or Linux-native command examples.
Recommendations
  • Add Azure CLI examples and links for all critical operations (delete NodeType, restart, reimage) alongside PowerShell examples.
  • Ensure that CLI and Bicep/ARM template usage is described with parity to PowerShell, including direct documentation links.
  • Explicitly state that all recommended tools (CLI, ARM, Bicep, Portal) are cross-platform and suitable for Linux/macOS users.
  • Consider reordering examples so that cross-platform tools (CLI, ARM, Bicep) are listed before or alongside PowerShell.
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-01 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 (Az PowerShell, AzSF PowerShell) for managing Service Fabric resources, with no mention of Linux/macOS equivalents or CLI alternatives. This creates friction for non-Windows users, as PowerShell is a Windows-native tool, and the Azure CLI (which is cross-platform) is only briefly mentioned for deletion operations. There are no Linux/macOS-specific instructions or examples.
Recommendations
  • Include Azure CLI examples for all operations (create, delete, scale) alongside PowerShell cmdlets, as Azure CLI is cross-platform.
  • Explicitly mention that PowerShell Core is available on Linux/macOS if PowerShell must be used, and provide installation guidance.
  • Where possible, provide ARM template examples for resource management, as these are platform-agnostic.
  • Clarify which tools are required for each OS and provide parity in instructions.
GitHub Create Pull Request
Service Fabric Initializer CodePackages in Service Fabric ...in/articles/service-fabric/initializer-codepackages.md
Medium Priority View Details →
Scanned: 2026-02-01 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page for Initializer CodePackages in Service Fabric provides only Windows container examples, exclusively referencing Windows container images, Windows file paths, and Windows command-line tools (cmd, echo, type, ping). There are no Linux container or cross-platform examples, and the example assumes familiarity with Windows container development. This creates friction for Linux/macOS users who may wish to use Initializer CodePackages with Linux containers.
Recommendations
  • Add a parallel example using Linux containers (e.g., Ubuntu or Alpine images) with Linux file paths and shell commands (bash, echo, cat, sleep).
  • Clarify in the introduction whether Initializer CodePackages are supported for Linux containers and, if so, provide guidance for Linux users.
  • Where possible, use cross-platform patterns or explicitly note platform limitations.
  • If Initializer CodePackages are Windows-only, state this clearly at the top of the page.
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-01 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation generally covers both Windows and Linux clusters for Azure Service Fabric monitoring, but there is a noticeable Windows-first bias in several sections. Windows tools and patterns (such as Event Log/Event Viewer, Diagnostics Agent, and ETW providers) are mentioned before their Linux equivalents, and some examples or tutorials focus primarily on Windows or .NET applications. Linux-specific instructions and tools are referenced, but often as secondary notes or links, and there is a lack of explicit Linux example walkthroughs or parity in some areas.
Recommendations
  • Ensure that Linux monitoring tools and configuration steps are presented with equal prominence and detail as Windows equivalents.
  • Provide explicit Linux example walkthroughs for common monitoring scenarios, including sample code and configuration steps.
  • Where Windows tools (e.g., Event Viewer, Diagnostics Agent) are mentioned, immediately follow with Linux equivalents (e.g., Syslog, Linux platform diagnostics) and clarify differences.
  • Add tutorials or links for monitoring non-.NET applications and Linux-native workloads on Service Fabric.
  • Review and update references to ensure Linux and cross-platform tools are not only mentioned but demonstrated.
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-01 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation page on RunToCompletion semantics in Service Fabric demonstrates a notable Windows bias. All code examples use Windows container images and Windows-specific shell commands (cmd, set, exit, etc.), with no mention or example of Linux containers or Linux shell equivalents. Querying deployment status is described only via PowerShell and C# APIs, with no Linux CLI or cross-platform alternatives. The introductory note and example code are explicitly Windows-focused, and Linux parity is not addressed.
Recommendations
  • Add equivalent examples using Linux containers (e.g., Ubuntu or Alpine images) and Linux shell commands (bash, echo, exit, etc.).
  • Clarify whether RunToCompletion semantics are supported for Linux containers and, if so, provide Linux-specific guidance.
  • Include instructions for querying deployment status using cross-platform tools (e.g., Azure CLI, REST API) or Linux-native commands if available.
  • Explicitly state any limitations or differences for Linux container support, if applicable.
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-01 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page for the Service Fabric application lifecycle consistently references PowerShell cmdlets and Windows-centric tooling (e.g., Copy-ServiceFabricApplicationPackage, Register-ServiceFabricApplicationType) alongside .NET APIs and REST operations. PowerShell examples and commands are frequently mentioned before or in preference to cross-platform alternatives, and there is little explicit mention of Linux/macOS workflows or CLI parity. While REST APIs and .NET APIs are referenced (which are cross-platform), the documentation implicitly assumes familiarity with Windows tooling and does not provide Linux-specific examples or guidance.
Recommendations
  • Add explicit examples using Service Fabric CLI (sfctl), which is cross-platform and recommended for Linux/macOS users.
  • Where PowerShell cmdlets are mentioned, also provide equivalent sfctl or Azure CLI commands.
  • Include notes or sections clarifying differences or additional steps for Linux/macOS environments, especially for deployment and lifecycle management.
  • Ensure that links to CLI documentation are prominent and not only included as a general reference.
  • Consider reordering examples so that cross-platform tools (sfctl, REST API) are presented before or alongside PowerShell cmdlets.
GitHub Create Pull Request
Service Fabric Fault Analysis Service overview .../service-fabric/service-fabric-testability-overview.md
Medium Priority View Details →
Scanned: 2026-02-01 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides usage instructions for C# (via the Microsoft.ServiceFabric NuGet package) and PowerShell, but does not mention or provide examples for Linux/macOS command-line tools, Service Fabric CLI (sfctl), or REST API usage. This creates friction for Linux/macOS users who cannot use PowerShell natively and may rely on cross-platform tools.
Recommendations
  • Add examples using Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • Mention REST API options for interacting with the Fault Analysis Service, if available.
  • Clarify which tools are supported on which platforms and provide parity in instructions for Linux/macOS users.
  • Consider adding a table or section comparing usage across Windows, Linux, and macOS 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-02-01 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation covers Service Fabric application security in a generally cross-platform manner, but several sections show Windows bias. Examples and references often focus on Windows tools and patterns (e.g., Active Directory, gMSA, BitLocker) with Linux equivalents either missing or relegated to TODOs. Windows-specific features are sometimes described before Linux options, and some security configuration examples (e.g., disk encryption) only link to Windows/PowerShell guides, leaving Linux users without clear guidance.
Recommendations
  • Provide explicit Linux examples and instructions alongside Windows ones, especially for disk encryption and service account management.
  • Add links to Linux-specific documentation where only Windows/PowerShell guides are referenced (e.g., encrypting disks on Linux clusters).
  • When mentioning Windows tools (e.g., BitLocker, gMSA), clarify their platform specificity and offer Linux alternatives or note limitations.
  • Ensure that examples and walkthroughs are balanced between Windows and Linux, or clearly indicate platform applicability.
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-01 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 on-demand backup in Azure Service Fabric is heavily focused on PowerShell-based workflows, with all command-line examples using PowerShell and the Microsoft.ServiceFabric.Powershell.Http module. There are no CLI, Bash, or Linux-native instructions, nor any mention of cross-platform alternatives. The use of PowerShell and related modules is presented as the default and only method, which may create friction for Linux/macOS users who typically use Bash, Azure CLI, or REST APIs directly.
Recommendations
  • Add equivalent examples using Azure CLI (az sf cluster, az rest) or Bash/cURL for REST API calls.
  • Clarify whether the PowerShell module is required on all platforms, and if so, provide installation instructions for Linux/macOS (e.g., via PowerShell Core).
  • Explicitly mention cross-platform support and provide guidance for Linux/macOS users.
  • Where REST API is referenced, provide direct cURL or HTTP request examples instead of only PowerShell.
  • Reorder examples so that REST API or cross-platform methods are shown before or alongside PowerShell.
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-02-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 detailed step-by-step instructions for scaling operations using PowerShell commands (e.g., Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState), but does not offer equivalent Linux CLI or bash examples. The manual scaling sections consistently reference PowerShell as the primary tool, and do not mention Linux alternatives or cross-platform Service Fabric CLI usage. Windows/PowerShell instructions are presented first and exclusively, creating friction for Linux users who may not have access to PowerShell or may prefer bash/CLI workflows.
Recommendations
  • Add equivalent Linux/Bash/Service Fabric CLI examples for all PowerShell commands (e.g., show how to disable nodes, check node status, and remove node state using Linux tools or the Service Fabric CLI).
  • Explicitly mention cross-platform tools (such as Service Fabric CLI or REST API) where possible, and clarify which instructions are platform-specific.
  • Where PowerShell is referenced, provide a note or link to Linux instructions, or indicate if the operation can be performed via the Service Fabric CLI or REST API.
  • Reorder examples so that cross-platform or Linux instructions are presented alongside or before Windows/PowerShell examples, where appropriate.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Auto Scaling Services and Containers ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-autoscaling.md
Medium Priority View Details →
Scanned: 2026-02-01 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides code examples for configuring auto scaling in Azure Service Fabric using application manifests, C# APIs, and PowerShell. All CLI/script examples use PowerShell, which is primarily a Windows tool. There are no Linux shell (bash/CLI) equivalents or guidance for Linux users. The PowerShell examples are presented for both instance-based and partition-based scaling, and appear before any mention of Linux compatibility. While the text notes that resource monitoring is supported for containerized applications on Linux, practical configuration examples and tooling guidance are Windows-centric.
Recommendations
  • Add equivalent CLI examples for Linux environments, such as using Azure CLI, Bash scripts, or REST API calls.
  • Explicitly document how Linux users can perform the same auto scaling configuration tasks, including any required tools or commands.
  • Clarify any limitations or differences in auto scaling configuration between Windows and Linux clusters.
  • If PowerShell is required for certain operations, state this clearly and provide alternatives or workarounds for Linux users.
GitHub Create Pull Request
← Previous Page 83 of 99 Next →