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 751-775 of 2475 flagged pages
Service Fabric Architecture of Azure Service Fabric ...articles/service-fabric/service-fabric-architecture.md
Medium Priority View Details →
Scanned: 2026-02-27 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page describes the architecture of Azure Service Fabric in a platform-neutral manner overall, but the Management subsystem section specifically mentions 'PowerShell cmdlets' as the primary tooling for provisioning, deploying, patching, upgrading, and de-provisioning applications. No equivalent Linux/macOS tooling (such as CLI commands, REST APIs, or Bash scripts) is mentioned. Additionally, Windows security is referenced as an option for securing communication, but Linux alternatives are not discussed.
Recommendations
  • Mention cross-platform management tools such as Azure CLI, REST APIs, or Bash scripts alongside PowerShell cmdlets.
  • Clarify whether the management subsystem can be accessed and managed from Linux/macOS environments, and provide examples or references.
  • When referencing security mechanisms, note Linux-compatible options (e.g., X509 certificates, Kerberos, etc.) where applicable.
  • Ensure that examples and tooling references are platform-neutral or include both Windows and Linux/macOS options.
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-27 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Windows and Linux examples for key security tasks, such as certificate generation and secret encryption. However, Windows-specific tools (PowerShell, Windows Defender, DSC) are often mentioned first or exclusively, and Windows-centric guidance (e.g., security baselines, Defender exclusions) is more detailed. Linux equivalents are present for encryption but less emphasized overall, and some sections (Windows Defender, DSC) are Windows-only without Linux alternatives or parity notes.
Recommendations
  • Ensure Linux examples are given equal prominence and detail, especially in sections where Windows examples are shown first.
  • Add Linux security baseline recommendations (e.g., CIS benchmarks, OS-specific hardening guides) alongside Windows baselines.
  • For Windows Defender/DSC sections, explicitly mention Linux alternatives (e.g., ClamAV, auditd, Ansible/Chef/Puppet for configuration management) or clarify if no direct equivalent exists.
  • Where Windows tools (PowerShell, DSC) are referenced, provide Linux command-line or scripting alternatives (bash, Python, etc.) where possible.
  • Consider a summary table contrasting Windows and Linux approaches for common security tasks in Service Fabric clusters.
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-27 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 in C# and PowerShell for configuring Service Fabric placement policies. PowerShell is a Windows-centric tool, and no equivalent Linux/macOS CLI (such as Azure CLI or REST API) examples are provided. PowerShell examples are consistently shown alongside C# code, with no mention of cross-platform alternatives. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other tools.
Recommendations
  • Add Azure CLI examples for each placement policy, as Azure CLI is cross-platform and widely used.
  • Mention REST API options for configuring placement policies, with example requests.
  • Clarify whether PowerShell examples are only applicable to Windows clusters, and provide guidance for Linux-based clusters.
  • Consider referencing Service Fabric CLI (sfctl), which is cross-platform, if applicable.
  • Ensure that documentation sections do not assume PowerShell as the default tool for all users.
GitHub Create Pull Request
Service Fabric Azure Service Fabric application resource model ...ervice-fabric/service-fabric-concept-resource-model.md
Medium Priority View Details →
Scanned: 2026-02-27 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a notable Windows bias. All deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) without any mention of Azure CLI equivalents or Linux/macOS-friendly workflows. Application packaging is described via Visual Studio, a Windows-centric tool, and no alternative methods (e.g., dotnet CLI or cross-platform tools) are provided. The examples and screenshots consistently reference Windows paths and tools, with no Linux/macOS parity.
Recommendations
  • Add Azure CLI examples for deployment and deletion tasks (e.g., az deployment group create, az resource delete).
  • Provide instructions for packaging applications using cross-platform tools such as the dotnet CLI or Service Fabric SDK commands, rather than relying solely on Visual Studio.
  • Include Linux/macOS file path examples and clarify that the procedures are applicable across platforms.
  • Mention that PowerShell Core is available on Linux/macOS, but highlight Azure CLI as the preferred cross-platform tool.
  • Add a note or section for Linux/macOS users outlining any differences or additional requirements.
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-27 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page primarily references PowerShell for deployment/removal tasks and links to PowerShell-specific resources. There is an implicit assumption of Windows usage, as seen in the 'Next steps' section and the linked example for downloading a ServicePackage in advance, which points to a PowerShell module. No Linux or cross-platform CLI examples or references are provided, and Linux tooling is not mentioned.
Recommendations
  • Add equivalent Linux/bash examples for deployment and removal tasks, using Azure CLI or Service Fabric CLI where available.
  • Include links to Linux/macOS documentation or tools for Service Fabric operations.
  • Clarify which steps or tools are cross-platform and which are Windows-specific.
  • Mention any limitations or differences for Linux nodes in Service Fabric clusters, if applicable.
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-27 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page on Azure Service Fabric Events demonstrates a Windows bias by primarily referencing Windows Event logs, ETW, and the Windows Azure diagnostics agent as the default mechanisms for event access and monitoring. There are no explicit Linux/macOS examples or mentions of equivalent tooling or patterns for non-Windows Service Fabric clusters, and Windows-specific tools are discussed first and most prominently.
Recommendations
  • Add explicit guidance for accessing Service Fabric events on Linux clusters, including references to Linux-compatible logging mechanisms (e.g., stdout/stderr, syslog, Azure Monitor integration for Linux).
  • Provide examples or links for configuring diagnostics and event collection on Linux-based Service Fabric clusters.
  • Mention cross-platform tools and APIs (such as EventStore REST APIs) earlier and more prominently to emphasize parity.
  • Clarify which event access methods are Windows-only and which are cross-platform, to help users understand applicability.
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-27 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation provides a thorough conceptual overview of X.509 certificate-based authentication in Service Fabric clusters, with configuration examples in XML. However, there is a notable Windows bias in troubleshooting and tool references: Windows certificate store paths ('LocalMachine\My') are mentioned first and most often, Windows event log channels are referenced for troubleshooting, and Windows-specific tools (CAPI2 logging, Win32 CryptoAPI) are discussed in detail. Linux equivalents are mentioned briefly (e.g., '*var/lib/sfcerts*'), but not explained or exemplified. No Linux-specific troubleshooting guidance or tool references are provided.
Recommendations
  • Add explicit Linux certificate store paths and explain how Service Fabric nodes on Linux locate and load certificates.
  • Provide Linux-specific troubleshooting steps, including relevant log file locations and commands (e.g., journalctl, syslog, Service Fabric logs).
  • Reference Linux tools for certificate validation and troubleshooting (e.g., openssl, certtool, systemd logs) alongside Windows tools.
  • Include examples of cluster manifest configuration and certificate management for Linux environments.
  • Clarify any differences in certificate handling or error codes between Windows and Linux nodes.
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-27 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page 'Manage certificates in a Service Fabric cluster' demonstrates a moderate Windows bias. PowerShell is the only scripting example provided for certificate enrollment, and the Key Vault VM extension is discussed exclusively in the context of Windows. The extension's schema and behaviors are described as Windows-specific, and there is no mention of Linux equivalents or cross-platform alternatives for certificate provisioning or automation. Windows tools and patterns (such as S-channel and certificate linking) are explained in detail, while Linux-specific mechanisms (e.g., Azure Key Vault extension for Linux, certificate handling on Linux nodes) are absent. Additionally, Windows-centric terminology and examples appear first and dominate the technical walkthroughs.
Recommendations
  • Add Linux-specific examples for certificate provisioning and automation, such as using Azure CLI or Bash scripts instead of only PowerShell.
  • Document the Key Vault VM extension for Linux, or clarify its availability and limitations for Linux VM/VMSS nodes.
  • Provide guidance for managing certificates in Service Fabric clusters running on Linux, including certificate store locations and access control.
  • Explicitly state which features or steps are Windows-only, and offer alternatives or workarounds for Linux/macOS users.
  • Include cross-platform sample templates and scripts, or link to relevant Linux documentation.
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-27 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides examples for managing Service Fabric managed cluster node types using the Azure Portal, ARM templates, and PowerShell. While ARM templates and Portal are cross-platform, all CLI/scripted examples are exclusively in PowerShell, with no mention of Azure CLI (az) or Bash equivalents. This creates friction for Linux/macOS users who do not have native access to PowerShell or prefer Bash/Azure CLI. There is also an implicit bias toward Windows tooling by only referencing PowerShell for automation and scripting.
Recommendations
  • Add Azure CLI (az) command examples alongside PowerShell for all supported operations (add, remove, scale, configure properties, etc.).
  • Explicitly state if certain operations are only possible with PowerShell, and provide guidance for Linux/macOS users (e.g., using Azure Cloud Shell or cross-platform PowerShell).
  • Where possible, provide Bash script snippets or note ARM template usage as the recommended cross-platform automation method.
  • Clarify in each section which tools are supported on which platforms, to help users choose the best approach for their OS.
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-27 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides best practice examples primarily using Azure PowerShell, with PowerShell-based APIs and modules referenced before Azure CLI or other cross-platform tools. While Azure CLI and ARM/Bicep are mentioned, the explicit examples and links for critical operations (delete, restart, reimage) are PowerShell-centric, potentially creating friction for Linux/macOS users who prefer CLI or scripting alternatives.
Recommendations
  • Add explicit Azure CLI examples and links for NodeType deletion, VMSS restart, and reimage operations, alongside PowerShell examples.
  • Ensure that CLI and PowerShell guidance are presented equally, ideally with CLI examples shown first or in parallel, since CLI is cross-platform.
  • Clarify that Azure PowerShell is available on Linux/macOS, but highlight CLI as the default for cross-platform scenarios.
  • Consider including sample ARM/Bicep template snippets for common operations, not just linking to general ARM documentation.
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-27 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides a PowerShell command example for bypassing the Infrastructure Service, without offering a Linux/macOS equivalent or clarifying cross-platform support. Service Fabric Explorer is mentioned, but no CLI or Linux-native tools are referenced. The PowerShell example is presented as the only way to perform the operation, which may create friction for Linux/macOS users managing Service Fabric clusters.
Recommendations
  • Clarify whether the PowerShell command is supported on Linux/macOS (e.g., via PowerShell Core or Azure CLI).
  • Provide equivalent instructions or commands for Linux/macOS users, such as using Azure CLI, REST API, or PowerShell Core if available.
  • Mention cross-platform management tools and their usage for the described operations.
  • Explicitly state platform limitations if the operation is Windows-only, to avoid confusion.
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-02-27 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 guidance is platform-neutral (focused on Azure Resource Manager templates and JSON), the migration steps for nonmanaged clusters with Basic SKU load balancer and IP resources rely heavily on PowerShell scripts and Windows-specific tooling. PowerShell is used exclusively for cluster management, node disabling/removal, and DNS updates, with no equivalent Bash, Azure CLI, or cross-platform examples. Additionally, sample templates and examples often reference Windows VM configurations before mentioning Linux equivalents, and the only explicit Linux sample is linked but not demonstrated in the migration steps.
Recommendations
  • Provide Azure CLI or Bash equivalents for all PowerShell migration steps, especially for cluster management, node disabling/removal, and DNS updates.
  • Explicitly mention and demonstrate Linux VM migration scenarios alongside Windows examples, not just as a linked template.
  • Clarify which steps are platform-agnostic and which require Windows-specific tools, and offer alternatives where possible.
  • Add guidance for macOS/Linux users on how to perform Service Fabric cluster operations without PowerShell (e.g., using Azure CLI or REST APIs).
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-27 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 for RunToCompletion semantics in Service Fabric presents Windows container examples exclusively, references Windows-specific container images, and uses Windows command syntax (cmd.exe). It also provides PowerShell as the only CLI example for querying deployment status, with no mention of Linux containers, Bash, or cross-platform alternatives. This creates friction for Linux/macOS users wishing to use RunToCompletion semantics with Linux containers or query deployment status from non-Windows environments.
Recommendations
  • Add equivalent examples using Linux containers (e.g., Ubuntu or Alpine images) and Linux shell commands.
  • Provide Bash or cross-platform CLI examples for querying deployment status (e.g., using sfctl or REST API).
  • Clarify whether RunToCompletion semantics are supported for Linux containers and guest executables on Linux nodes.
  • Mention any platform limitations explicitly, so users know if Linux scenarios are unsupported.
  • Ensure code samples and manifest snippets are not Windows-specific unless the feature is Windows-only.
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-27 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides monitoring guidance for Azure Service Fabric clusters on both Windows and Linux, but there are several areas where Windows-specific tools and patterns are mentioned first or exclusively, and Linux equivalents are less prominent or missing. Windows tools like Event Viewer, ETW, and Diagnostics Agent are referenced with more detail, while Linux alternatives (such as LTTng, Syslog, and Linux-specific configuration) are mentioned but not explained in depth or with examples. Some tutorials and examples focus on .NET applications, which are cross-platform, but Windows-centric monitoring solutions are often presented first or with more detail.
Recommendations
  • Provide Linux-specific examples and walkthroughs for configuring monitoring, especially for EventStore, Syslog, and performance counters.
  • Ensure that Linux tools (like LTTng and Syslog) are described with the same depth as Windows tools (ETW, Event Viewer).
  • Add links or tutorials for monitoring Service Fabric clusters on Linux, similar to those provided for Windows.
  • When listing monitoring solutions or agents, present Windows and Linux options side-by-side rather than Windows-first.
  • Clarify which features are Windows-only and which are available on Linux, to reduce confusion.
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-27 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 (e.g., running services under Active Directory domain accounts, gMSA, BitLocker) are mentioned with detailed links and explanations, while Linux equivalents are either missing or referenced only briefly. Examples and guidance for Linux clusters (e.g., disk encryption, user accounts, certificate management) are sparse or absent, and Windows tools/patterns are often described first or exclusively.
Recommendations
  • Add explicit examples and guidance for Linux clusters, including how to run services under Linux user accounts and manage security principals.
  • Provide instructions or links for encrypting disks on Linux clusters, not just Windows/BitLocker.
  • Ensure parity in certificate management and secret handling for Linux, including any differences in procedure or tooling.
  • When mentioning Windows-specific features (e.g., gMSA, BitLocker), clarify if/when Linux equivalents exist and provide links or guidance.
  • Balance the order of examples and explanations so Linux and Windows are treated equally, or clearly indicate when a feature is Windows-only.
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-27 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 focused on PowerShell-based workflows, with all command-line examples provided exclusively in PowerShell. There are no Bash, CLI, or Linux/macOS-specific instructions or examples. The prerequisite section assumes the use of PowerShell modules, and REST API usage is also demonstrated via PowerShell scripts. There is no mention of Linux/macOS equivalents or guidance for users on those platforms.
Recommendations
  • Add Bash or Azure CLI examples for REST API calls, demonstrating how to trigger backups and track progress from Linux/macOS environments.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is required for all scenarios, or if REST API calls can be made directly from any platform.
  • Provide guidance on connecting to Service Fabric clusters from Linux/macOS, including authentication and certificate handling.
  • Explicitly state platform requirements and alternatives for non-Windows users, or link to cross-platform documentation.
  • Consider including sample curl commands for REST API operations.
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-27 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 in its guidance for authoring Service Fabric manifests. It recommends using Visual Studio and a Windows file path to validate XML schema ordering, without mentioning cross-platform alternatives. Additionally, PowerShell is referenced for service creation, but no Linux CLI or scripting equivalents are provided. However, the core manifest concepts and examples are platform-neutral, and Service Fabric supports Linux clusters, so Linux users can complete the task with some friction.
Recommendations
  • Add instructions for validating XML schema ordering using cross-platform tools (e.g., VS Code, xmllint, or other editors available on Linux/macOS).
  • Mention the location of the ServiceFabricServiceModel.xsd schema file on Linux clusters, if applicable.
  • Provide CLI examples for creating services (e.g., using Azure CLI or sfctl) alongside PowerShell references.
  • Ensure that references to Windows tools are accompanied by Linux/macOS alternatives where possible.
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-27 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-specific tooling throughout all lifecycle phases (deploy, test, upgrade, remove, maintenance). While REST API and .NET methods are also mentioned, PowerShell examples and references are prominent and often listed first. There is no explicit mention of Linux-native command-line tools or examples (such as Bash, sfctl, or Azure CLI usage), nor is there guidance for Linux/macOS users on equivalent workflows. This creates friction for non-Windows users, as they must infer or locate Linux-compatible instructions elsewhere.
Recommendations
  • Add Linux/macOS-friendly examples using sfctl and Azure CLI for each lifecycle phase alongside PowerShell examples.
  • Explicitly mention cross-platform tools and clarify which commands are available on Windows, Linux, and macOS.
  • Where PowerShell is referenced, provide equivalent Bash or CLI commands and link to relevant documentation.
  • Ensure REST API usage is demonstrated with cross-platform tools (e.g., curl, sfctl) and not just .NET or PowerShell.
  • Consider a table or section summarizing tool parity for Windows and Linux users.
GitHub Create Pull Request
Service Fabric Advanced Application Upgrade Topics ...-fabric/service-fabric-application-upgrade-advanced.md
Medium Priority View Details →
Scanned: 2026-02-27 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page heavily relies on PowerShell cmdlets for examples and instructions, with no mention of Linux/macOS equivalents or cross-platform CLI tools. All command-line examples use PowerShell syntax, and references to Service Fabric management are exclusively through PowerShell. There is no guidance for Linux users on how to perform these tasks, nor are Linux tools or patterns mentioned.
Recommendations
  • Add equivalent examples using Azure CLI or Service Fabric CLI (sfctl), which are cross-platform and supported on Linux/macOS.
  • Explicitly mention that PowerShell examples are for Windows, and provide alternative instructions for Linux/macOS users.
  • Include links to documentation about managing Service Fabric applications from Linux/macOS environments.
  • Where possible, clarify which features or commands are Windows-only, and which are available cross-platform.
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-27 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page primarily discusses data serialization in the context of Azure Service Fabric, which is cross-platform. However, in the 'Next steps' section, Windows-centric tools and workflows (Visual Studio and PowerShell) are mentioned first and exclusively, with no Linux/macOS equivalents or CLI alternatives provided. The main content is platform-neutral, but the upgrade guidance is Windows-biased.
Recommendations
  • Add examples or links for upgrading applications using cross-platform tools such as Azure CLI or Service Fabric CLI (sfctl), which are available on Linux and macOS.
  • Include guidance for non-Windows environments, such as using VS Code or command-line tools for application upgrades.
  • Clarify if PowerShell examples are compatible with PowerShell Core on Linux/macOS, or provide Bash equivalents.
GitHub Create Pull Request
Service Fabric Application upgrade: upgrade parameters ...abric/service-fabric-application-upgrade-parameters.md
Medium Priority View Details →
Scanned: 2026-02-27 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page presents Windows/PowerShell and Visual Studio parameters and workflows first, with detailed tables and explanations. SFCTL (Service Fabric CLI), which is cross-platform and especially relevant for Linux users, is covered later and with less detail. The examples and parameter tables are heavily PowerShell-centric, and Linux-specific workflows (SFCTL) are not given equal prominence or example depth. There are no Linux-specific examples or explicit parity checks for Linux/macOS users.
Recommendations
  • Reorder sections so that SFCTL (Service Fabric CLI) parameters and workflows appear before or alongside PowerShell/Visual Studio, emphasizing cross-platform usage.
  • Provide example command invocations for SFCTL, similar to the PowerShell examples, including sample JSON parameter files.
  • Add a comparison table showing parameter mappings between PowerShell, Visual Studio, and SFCTL to clarify parity.
  • Explicitly mention Linux/macOS compatibility for SFCTL and highlight any differences or caveats.
  • Include a brief note at the start clarifying that all upgrade modes and parameters are available via SFCTL on Linux/macOS, not just Windows tools.
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-27 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 demonstrates notable Windows bias. The only example provided for preserving application parameters during an upgrade uses PowerShell, with no equivalent CLI or Linux/macOS example. References to Windows-specific tools (PowerShell, http.sys, Windows HTTP Server API) are made without mentioning cross-platform alternatives or clarifying platform limitations. The 'Next steps' section prioritizes Visual Studio and PowerShell tutorials, both Windows-centric, and lacks guidance for Linux/macOS users.
Recommendations
  • Add equivalent examples using Azure CLI or Service Fabric CLI (sfctl), which are cross-platform.
  • Clarify which steps or tools are Windows-only and provide Linux/macOS alternatives where possible.
  • Include explicit guidance or links for Linux/macOS users, such as using sfctl or REST APIs.
  • Mention platform limitations (e.g., http.sys and Windows HTTP Server API) and suggest Linux/macOS-compatible approaches.
  • Balance 'Next steps' with tutorials for Linux/macOS environments.
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-27 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides PowerShell-based manual scaling instructions and references Windows-centric tooling (e.g., PowerShell cmdlets like Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState) without offering equivalent Linux CLI or cross-platform guidance. Windows/PowerShell examples are presented first and exclusively in step-by-step procedures, creating friction for Linux users. However, the page does mention Linux clusters and is not strictly Windows-only.
Recommendations
  • Add equivalent Linux CLI instructions (e.g., using sfctl or REST API) for manual scaling operations alongside PowerShell examples.
  • Explicitly note which commands are Windows-only and provide cross-platform alternatives where possible.
  • Consider including bash or sfctl examples in parallel with PowerShell for all cluster management tasks.
  • Clarify any limitations for Linux clusters and link to Linux-specific guidance when relevant.
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-27 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Service Fabric clusters, but PowerShell (a Windows-centric tool) is given a dedicated section and additional upgrade examples are only shown in PowerShell. Windows-specific registry and OS configuration steps are described in detail, while equivalent Linux instructions are missing. The order of presentation and example coverage subtly favors Windows users, and Linux users may need to infer or research equivalent steps.
Recommendations
  • Provide Bash or shell script examples for manual cluster upgrade steps, especially where PowerShell is used.
  • Include Linux-specific instructions for disabling automatic updates (e.g., using systemd or apt/yum configuration) alongside Windows registry and OS profile settings.
  • When discussing VM scale set configuration, mention both 'windowsConfiguration' and 'linuxConfiguration' blocks in ARM templates.
  • Where PowerShell cmdlets are used for Service Fabric management, reference or link to equivalent Linux tools or CLI commands if available.
  • Present cross-platform examples in parallel or alternate between Windows and Linux to avoid the perception of Windows-first bias.
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-27 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page for restoring backups in Azure Service Fabric is heavily biased towards Windows and PowerShell usage. All code examples use PowerShell, including REST API calls, and require installation of the Microsoft.ServiceFabric.Powershell.Http module. There are no examples or guidance for Linux/macOS users, such as using Bash, curl, or cross-platform tools. The documentation assumes the user is on Windows, and does not mention alternative approaches for non-Windows environments.
Recommendations
  • Add equivalent Bash/curl examples for REST API calls, showing how to trigger backup/restore and track progress from Linux/macOS.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is required for all operations, or if REST API calls can be made directly from any OS.
  • Mention any cross-platform CLI tools (such as Azure CLI) that can be used for these tasks, or explicitly state if only PowerShell is supported.
  • Provide guidance for Linux/macOS users on authentication (e.g., certificate handling) and connecting to Service Fabric clusters.
  • If PowerShell is required, note that PowerShell Core is available cross-platform and provide installation instructions for Linux/macOS.
GitHub Create Pull Request
← Previous Page 31 of 99 Next →