Service Fabric

407
Total Pages
336
Linux-Friendly Pages
71
Pages with Bias
17.4%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

1305 issues found
Showing 351-375 of 1305 flagged pages
Service Fabric Fault Analysis Service overview .../service-fabric/service-fabric-testability-overview.md
Medium Priority View Details →
Scanned: 2026-02-16 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page provides usage instructions for the Fault Analysis Service in Service Fabric, referencing C# and PowerShell as the primary ways to interact with the service. PowerShell is a Windows-centric tool, and no Linux or cross-platform CLI examples (such as Bash, Azure CLI, or REST API usage) are provided. There is no mention of Linux tooling or patterns, nor are Linux-specific instructions or parity considerations discussed.
Recommendations
  • Add examples for using the Fault Analysis Service from Linux/macOS environments, such as via Azure CLI, Bash scripts, or REST API calls.
  • Clarify whether the Fault Analysis Service APIs can be accessed from non-Windows platforms and provide guidance for those scenarios.
  • If PowerShell Core (cross-platform) is supported, specify this and provide relevant examples.
  • Include information about any limitations or differences when using Service Fabric and Fault Analysis Service on Linux clusters.
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-15 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, without mentioning Linux/macOS equivalents or CLI alternatives. Service Fabric Explorer is referenced, which is cross-platform, but the command-line guidance is Windows-centric.
Recommendations
  • Add equivalent Azure CLI or Bash examples for bypassing Infrastructure Service, or clarify if PowerShell is required regardless of OS.
  • Explicitly state whether the PowerShell cmdlet is available on Linux/macOS (via PowerShell Core), and provide installation guidance if so.
  • If the operation is only possible via PowerShell, clarify this limitation for Linux/macOS users.
  • Consider providing links or instructions for using Service Fabric Explorer from Linux/macOS if relevant.
GitHub Create Pull Request
Service Fabric Azure Service Fabric networking best practices ...ice-fabric/service-fabric-best-practices-networking.md
Medium Priority View Details →
Scanned: 2026-02-15 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page presents several examples and references that prioritize Windows tools and patterns, such as PowerShell, and often mentions Windows-specific concepts before Linux equivalents. Some sections (e.g., API access, DevOps, and port explanations) focus on Windows tools or provide Windows-centric guidance, while Linux alternatives are less prominent or missing. Although Linux is referenced, parity in examples and explanations is lacking.
Recommendations
  • Provide Linux CLI (az, bash) examples alongside PowerShell for cluster management and networking tasks.
  • Clarify when guidance applies to both Windows and Linux, and explicitly note any differences.
  • Add Linux-specific guidance for DevOps/API access, including relevant tools and commands.
  • Ensure port explanations and security rule tables clearly indicate which apply to Linux, which to Windows, and provide Linux-specific context.
  • Include ARM template samples for Linux clusters, not just Windows.
  • Balance references to Windows and Linux throughout the page, avoiding Windows-first ordering unless justified.
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-15 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides links to application upgrade tutorials using Visual Studio and PowerShell, both of which are primarily Windows-centric tools. No equivalent Linux/macOS upgrade examples or CLI instructions are mentioned or linked. The serialization guidance is focused on C# and .NET, which are cross-platform, but the upgrade workflow references Windows tools first and exclusively.
Recommendations
  • Add links or sections describing how to perform application upgrades using cross-platform tools such as Azure CLI or Service Fabric CLI (sfctl), which are available on Linux/macOS.
  • Include upgrade examples or tutorials for Linux/macOS environments, or explicitly state if only Windows tools are supported for certain workflows.
  • If PowerShell is referenced, clarify whether PowerShell Core (cross-platform) is supported, and provide instructions for Linux/macOS if applicable.
  • Consider mentioning Visual Studio Code as a cross-platform alternative to Visual Studio for relevant tasks.
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-15 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation references PowerShell cmdlets as primary management tools in the Management subsystem section, without mentioning Linux/macOS equivalents (such as Azure CLI or REST APIs). Additionally, Windows security is mentioned alongside X509 certificates in the Transport subsystem, suggesting Windows-first patterns. No explicit Linux/macOS management examples or tools are provided.
Recommendations
  • Add references to Azure CLI and REST API management options alongside PowerShell cmdlets.
  • Clarify that Service Fabric management can be performed from Linux/macOS using CLI or API tools.
  • Provide examples or links for Linux/macOS users to manage Service Fabric clusters.
  • Mention Linux security mechanisms (e.g., certificate-based auth) where relevant, not just Windows security.
GitHub Create Pull Request
Service Fabric Node types and virtual machine scale sets ...les/service-fabric/service-fabric-cluster-nodetypes.md
Medium Priority View Details →
Scanned: 2026-02-15 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides general information about Azure Service Fabric node types and VM scale sets, and includes a JSON snippet for the Service Fabric Virtual Machine extension. While the extension supports both Linux and Windows nodes, the example uses Windows-style paths (e.g., 'D:\\SvcFab') and certificate store names, which are Windows-centric. Additionally, the 'Next steps' section links to PowerShell-based scripts for RDP port and credential changes, without mentioning Linux/SSH equivalents or alternatives. There are no explicit Linux examples or guidance for Linux users, and Windows patterns (RDP, PowerShell) are referenced first or exclusively.
Recommendations
  • Provide Linux-specific examples, such as using SSH for remote connection instead of RDP.
  • Include Linux file path conventions (e.g., '/var/svcfab') in extension examples.
  • Add links or guidance for managing Linux node types (e.g., changing SSH port/user/password) alongside Windows/PowerShell scripts.
  • Clarify which steps or scripts are Windows-only and provide Linux alternatives where possible.
  • Mention Linux certificate store handling if relevant.
GitHub Create Pull Request
Service Fabric Custom Image .../articles/service-fabric/how-to-deploy-custom-image.md
Medium Priority View Details →
Scanned: 2026-02-15 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page focuses primarily on deploying custom Windows images in Service Fabric Managed Clusters, with Windows terminology and PowerShell examples presented. While it references Linux custom image creation and Azure CLI for browsing marketplace images, the main narrative and examples are Windows-centric, and the PowerShell command is given without a Linux CLI equivalent.
Recommendations
  • Add explicit examples and guidance for deploying Linux custom images in Service Fabric Managed Clusters, including ARM template snippets for Linux node types.
  • Provide Azure CLI or Bash equivalents for role assignment and other operations currently shown only in PowerShell.
  • Clarify in the introduction that both Windows and Linux images are supported, and highlight any differences or limitations.
  • Ensure links to Linux documentation are as prominent as Windows links, and avoid Windows-first language unless the 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-15 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 exclusively provides PowerShell-based examples and instructions, including module installation and REST API calls via PowerShell. There are no examples or guidance for Linux/macOS users (e.g., Bash, curl, Azure CLI), and Windows/PowerShell tools are mentioned first and exclusively throughout. This creates friction for non-Windows users, though REST APIs are referenced and could be used from other platforms.
Recommendations
  • Add equivalent Bash/curl examples for REST API calls, showing how Linux/macOS users can trigger backups and track progress.
  • Mention Azure CLI commands if available for Service Fabric backup operations.
  • Clarify that the Microsoft.ServiceFabric.Powershell.Http module is Windows-only, and provide alternative instructions for Linux/macOS users (e.g., using REST APIs directly).
  • Reorganize sections to present cross-platform approaches (REST API, Azure CLI) before or alongside PowerShell examples.
  • Explicitly state platform requirements for each tool or command.
GitHub Create Pull Request
Service Fabric Cluster Resource Manager - Management Integration ...fabric-cluster-resource-manager-management-integration.md
Medium Priority View Details →
Scanned: 2026-02-15 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides a PowerShell example for querying partition health, using the Get-ServiceFabricPartitionHealth cmdlet with a Windows-style prompt. No equivalent Linux or cross-platform CLI example is given. The example and command syntax are Windows-centric, potentially creating friction for Linux/macOS users who may use Service Fabric CLI or REST APIs instead. The rest of the documentation is generally platform-neutral, but the example section is notably Windows-focused.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl) for Linux/macOS users.
  • Mention REST API options for querying health, which are platform-agnostic.
  • Clarify that PowerShell is one option, and provide links or references to cross-platform tools.
  • Where possible, show both Windows and Linux command examples side-by-side.
GitHub Create Pull Request
Service Fabric Learn more about Azure Service Fabric ...icles/service-fabric/service-fabric-content-roadmap.md
Medium Priority View Details →
Scanned: 2026-02-15 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 provides a broad overview of Azure Service Fabric, which supports both Windows and Linux. However, there is a notable Windows bias: Windows-specific tools (e.g., PowerShell, Visual Studio) are mentioned first or exclusively in several sections, and Windows terminology (e.g., Windows service, FabricHost.exe) is used without always clarifying Linux equivalents. Some examples and links focus on Windows clusters, and Linux standalone clusters are explicitly noted as unsupported. CLI tools are mentioned, but PowerShell is often listed first. There are few explicit Linux examples or instructions, and Linux tools (e.g., Bash, Linux-specific CLI usage) are not highlighted.
Recommendations
  • Ensure that examples and instructions for cluster creation, management, and health monitoring are provided for both Windows and Linux, with Linux examples shown alongside or before Windows ones where possible.
  • Clarify when features or instructions are Windows-only, and provide Linux alternatives or note limitations.
  • Mention Linux tools (e.g., Bash, Linux CLI usage) and provide sample commands for Linux users.
  • Balance the order of tool mentions (e.g., list CLI and PowerShell together, or mention CLI first for cross-platform parity).
  • Add links and references to Linux-specific documentation and guides where available.
  • Explicitly state feature parity or differences, and link to the 'Differences between Service Fabric on Linux and Windows' page earlier in the document.
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-02-15 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides command-line examples only in PowerShell, references PowerShell cmdlets for management tasks, and does not mention or provide examples for Linux/macOS CLI tools (such as sfctl) or Bash equivalents. This creates friction for Linux/macOS users, who must translate PowerShell commands or seek alternative tooling.
Recommendations
  • Add equivalent examples using sfctl (the cross-platform Service Fabric CLI) for all PowerShell command examples, especially for service creation and management.
  • Mention sfctl as a supported tool for Linux/macOS users alongside PowerShell.
  • Where possible, provide Bash or generic REST API examples in addition to PowerShell.
  • Clarify in the 'Next steps' and other sections that PowerShell is not the only supported management tool, and link to Linux/macOS-friendly documentation.
GitHub Create Pull Request
Service Fabric Manage apps for multiple environments ...e-fabric-manage-multiple-environment-app-configuration.md
Medium Priority View Details →
Scanned: 2026-02-15 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page presents Windows/PowerShell examples first and in more detail, with explicit mention of PowerShell cmdlets and Visual Studio workflows. Linux tooling (sfctl, install.sh) is mentioned, but lacks example commands or detailed guidance. There are no explicit Linux/macOS shell examples or parity in walkthroughs, creating friction for non-Windows users.
Recommendations
  • Add explicit Linux/macOS shell examples for parameter passing, e.g., using sfctl and install.sh.
  • Provide sample scripts or command lines for Linux environments alongside PowerShell examples.
  • Ensure Visual Studio/PowerShell workflows are matched with CLI-based workflows suitable for Linux/macOS users.
  • Clarify which tools are cross-platform and which are Windows-only, to help users choose the right workflow.
GitHub Create Pull Request
Service Fabric Upgrading Azure Service Fabric clusters ...icles/service-fabric/service-fabric-cluster-upgrade.md
Medium Priority View Details →
Scanned: 2026-02-15 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation provides general guidance for upgrading Azure Service Fabric clusters, but there are subtle signs of Windows bias. For example, when discussing OS image upgrades, the only linked guidance is for patching Windows operating systems. Additionally, references to PowerShell are made before Azure CLI, and no explicit Linux-specific examples or guidance are provided. However, most instructions are platform-agnostic and do not prevent Linux/macOS users from completing the tasks.
Recommendations
  • Add links and guidance for patching/upgrading Linux-based Service Fabric clusters, if supported.
  • When mentioning PowerShell, always mention Azure CLI alongside it, and provide CLI examples where possible.
  • Ensure that references to tools and examples are presented in a platform-neutral order (e.g., 'Azure CLI/PowerShell' instead of 'PowerShell/Azure CLI').
  • Clarify if certain features (like Patch Orchestration Application) are Windows-only, and provide Linux alternatives or explicitly state 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-15 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides several PowerShell-based deployment examples (e.g., New-ServiceFabricApplication) and references to Windows file paths and certificate stores (e.g., C:\Program Files\..., X509StoreName="MY"). While there is a brief note about Linux certificate storage, Linux/macOS equivalents for deployment commands and tooling are missing. Windows tools and patterns are mentioned first and most prominently.
Recommendations
  • Add equivalent Linux/macOS deployment examples using Azure CLI or sfctl where possible.
  • When referencing file paths or certificate stores, provide both Windows and Linux equivalents in the main text, not just in notes.
  • Include a section or callout for Linux/macOS users describing any differences in workflow, especially for certificate management and application deployment.
  • When showing PowerShell commands, provide bash/shell alternatives if supported.
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-15 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides a comprehensive overview of certificate management in Azure Service Fabric clusters, but it exhibits Windows bias in several areas. PowerShell is the only scripting example provided for programmatic certificate enrollment, and references to Windows-specific tools and concepts (such as certificate stores, ACLing, S-channel, and Key Vault VM extension for Windows) are frequent and often precede or exclude Linux equivalents. The Key Vault VM extension is described primarily in its Windows context, and there is no mention of Linux-specific certificate provisioning mechanisms or examples. While the JSON ARM templates are cross-platform, operational guidance and troubleshooting are Windows-centric.
Recommendations
  • Add Linux-specific examples for certificate provisioning and management, such as using Azure CLI or Bash scripts instead of only PowerShell.
  • Document the Key Vault VM extension for Linux, including its schema, behaviors, and any differences from the Windows extension.
  • Provide guidance for certificate store locations and access control on Linux nodes, including how Service Fabric handles certificates on Linux.
  • Include troubleshooting steps and FAQ entries relevant to Linux environments.
  • Ensure that scripting and automation examples are available in both PowerShell and Bash/Azure CLI.
  • Clarify which features or steps are Windows-only and provide Linux alternatives where possible.
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-15 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 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 alternatives. This creates friction for Linux/macOS users, as PowerShell is primarily a Windows tool and not natively available on all platforms. Additionally, PowerShell examples are consistently given, and no Linux-specific tools or workflows are referenced. The ordering often presents Portal and PowerShell before ARM templates, and there are no explicit Linux/macOS parity notes.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all relevant operations (add, remove, scale, configure placement properties, etc.).
  • Explicitly mention that ARM templates and Portal are cross-platform and suitable for Linux/macOS users.
  • Where PowerShell is referenced, note that PowerShell Core is available cross-platform, but Azure CLI is often preferred for Linux/macOS.
  • Consider providing Bash script snippets for ARM template deployments.
  • Clarify any limitations or parity gaps for Linux/macOS users.
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-15 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 several sections and examples prioritize Windows tools and terminology. Windows-specific tools (e.g., EventStore APIs, Diagnostics Agent, Event Viewer) are mentioned before Linux equivalents, and some features (like EventStore APIs) are noted as Windows-only without clear Linux alternatives or guidance. Linux monitoring is referenced but often lacks detailed examples or step-by-step parity with Windows instructions.
Recommendations
  • Ensure Linux monitoring tools and workflows are described with equal detail and prominence as Windows equivalents.
  • Add Linux-specific examples for configuring and querying Service Fabric events, logs, and performance counters, especially where Windows tools (e.g., Event Viewer, Diagnostics Agent) are referenced.
  • Where features are Windows-only (e.g., EventStore APIs), provide clear Linux alternatives or guidance, or explicitly state the limitation and recommend best practices for Linux users.
  • Review tutorials and linked resources to ensure Linux users can follow along and complete monitoring tasks without friction.
  • Consider adding a comparative table or section summarizing monitoring approaches and tools for both Windows and Linux clusters.
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-15 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation generally describes Service Fabric's X.509 certificate authentication in a cross-platform manner, but there are several areas where Windows-specific terminology, tools, and patterns are prioritized or mentioned first. Windows certificate store paths and Win32 CryptoAPI are referenced before or instead of Linux equivalents. Troubleshooting guidance and event log locations are Windows-centric, and PowerShell/C++ error codes are used without Linux-specific alternatives or guidance.
Recommendations
  • When referencing certificate stores, always mention both Windows and Linux paths together (e.g., 'LocalMachine\My' (Windows) or '/var/lib/sfcerts' (Linux)).
  • For troubleshooting, provide Linux equivalents for event log locations and diagnostic steps (e.g., journalctl, syslog, or Service Fabric log file locations on Linux nodes).
  • When discussing API calls (like Win32 CryptoAPI), clarify the Linux equivalent or note how the functionality is implemented/can be debugged on Linux.
  • Include Linux-specific error messages or troubleshooting steps alongside Windows error codes.
  • If PowerShell or Windows tools are referenced, provide Linux CLI or script alternatives (e.g., OpenSSL commands for certificate inspection).
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-15 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page predominantly references Az PowerShell cmdlets (e.g., Remove-AzResource, AzSF PowerShell cmdlets) for managing Service Fabric resources, with no explicit mention or examples of equivalent Azure CLI commands or Linux/macOS workflows. While 'az resource' is briefly mentioned for deleting applications, the majority of guidance and links are PowerShell-focused, which may create friction for Linux/macOS users who rely on Azure CLI.
Recommendations
  • Provide equivalent Azure CLI commands alongside PowerShell cmdlets for all management operations (e.g., creating and deleting applications, services, and application type versions).
  • Clarify when Az PowerShell cmdlets are required versus when Azure CLI can be used, and note any platform limitations.
  • Include example commands for both Windows (PowerShell) and Linux/macOS (Azure CLI) users in each relevant section.
  • Link to Azure CLI documentation where appropriate, not just PowerShell modules.
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-15 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page 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), and Windows container images. Querying deployment status is described only via PowerShell and C# APIs, with no mention of Linux tools or cross-platform alternatives. There are no examples or guidance for Linux containers or Linux-based workflows, despite Service Fabric supporting Linux containers.
Recommendations
  • Add equivalent Linux container examples using popular Linux base images (e.g., Ubuntu, Alpine) and shell commands (bash, echo, ping, etc.).
  • Provide guidance or examples for querying deployment status using Linux tools or cross-platform CLI (e.g., Azure CLI, sfctl).
  • Clarify which aspects are Windows-specific and which are cross-platform, to help Linux/macOS users understand applicability.
  • Consider including a section or links for Linux container application development with RunToCompletion semantics.
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-15 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Service Fabric clusters, but PowerShell is featured prominently and exclusively for several critical operations (e.g., manual cluster upgrade). Windows-specific tools and registry settings are discussed without Linux equivalents or alternatives. Windows configuration properties are shown before any mention of Linux, and some upgrade instructions are Windows-centric.
Recommendations
  • Include Linux-specific instructions and examples for manual cluster upgrades, such as using Bash scripts or Linux-native tools.
  • Provide equivalent Linux configuration guidance for disabling automatic updates and managing upgrades, or clarify if/when these steps are not needed on Linux.
  • Balance PowerShell and CLI examples throughout, ensuring that Linux users have clear, actionable steps for all major operations.
  • Explicitly note when a step is Windows-only, and provide links or references to Linux documentation where appropriate.
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-15 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page primarily describes Service Fabric application and service manifests, which are cross-platform concepts. However, there are signs of Windows bias: the only tooling example given for validating XML schema is Visual Studio with a Windows file path, and the only explicit mention of command-line tooling for service creation is PowerShell. No Linux/macOS equivalents (such as VS Code, xmllint, or Azure CLI) are mentioned, nor are cross-platform file paths or tools provided. Windows-specific tools and patterns are referenced first and exclusively.
Recommendations
  • Add examples and instructions for validating XML manifests using cross-platform tools (e.g., VS Code, xmllint, or other editors) and reference Linux/macOS file paths.
  • Include Azure CLI or REST API examples for service creation and management, not just PowerShell.
  • Mention cross-platform approaches for editing and validating manifests, such as using VS Code extensions or command-line utilities.
  • Clarify that Service Fabric can be used on Linux and provide links or notes for Linux-specific guidance where relevant.
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-15 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., Active Directory, gMSA, BitLocker) are mentioned before Linux equivalents or without Linux parity. Some examples and links focus on Windows scenarios (e.g., disk encryption via PowerShell, running services as AD users), while Linux-specific guidance is minimal or missing. The section on encrypting disks references BitLocker and PowerShell for Windows, with only a TODO for Linux disk encryption.
Recommendations
  • Add explicit Linux examples for disk encryption, such as using Azure Disk Encryption with Linux or dm-crypt/LUKS.
  • Provide parity for service account management on Linux clusters, including guidance for Linux user/group configuration.
  • Ensure container certificate access examples cover both Windows and Linux clusters with clear instructions.
  • Where Windows-specific tools (e.g., PowerShell, BitLocker, gMSA) are mentioned, add or link to Linux alternatives and clarify platform applicability.
  • Review 'Next steps' links to ensure Linux users are not directed only to Windows-centric content.
GitHub Create Pull Request
Service Fabric Application upgrade: upgrade parameters ...abric/service-fabric-application-upgrade-parameters.md
Medium Priority View Details →
Scanned: 2026-02-15 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page presents PowerShell and Visual Studio (Windows-centric tools) parameters and workflows first and in greater detail, with Linux/macOS (SFCTL/CLI) options covered later and less prominently. Most parameter tables and examples are focused on PowerShell and Visual Studio, with SFCTL (the cross-platform CLI) described in a separate, shorter section. There are no explicit Linux/macOS command-line examples or screenshots, and the PowerShell/Visual Studio workflow dominates the narrative.
Recommendations
  • Reorder sections or provide parallel sections so that SFCTL (Service Fabric CLI) parameters and workflows are presented alongside PowerShell/Visual Studio, not after them.
  • Add explicit SFCTL command-line examples for common upgrade scenarios, similar to the PowerShell examples.
  • Clarify in the introduction that SFCTL is the recommended cross-platform tool for Linux/macOS users.
  • Where parameter tables are shown, include a column for SFCTL equivalents, or provide a unified table indicating which parameters apply to which tool.
  • Add Linux/macOS-specific notes or screenshots where appropriate.
  • Ensure that links to Linux/macOS upgrade tutorials are as prominent as those for PowerShell/Visual Studio.
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-15 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/PowerShell usage. All code examples are provided exclusively in PowerShell, and the prerequisite steps require installation of a PowerShell module (Microsoft.ServiceFabric.Powershell.Http). There are no examples or guidance for Linux/macOS users, such as using Azure CLI, curl, or other cross-platform tools to interact with the REST APIs. The documentation assumes the reader is using Windows and PowerShell, creating friction for Linux/macOS users who may need to restore backups in Service Fabric clusters.
Recommendations
  • Add equivalent examples using Azure CLI, curl, or other cross-platform tools for REST API calls.
  • Document how to authenticate and make REST API calls from Linux/macOS environments, including certificate handling.
  • Clarify whether the PowerShell module is required for all scenarios, or if REST API calls can be made directly from any platform.
  • Provide sample scripts or commands for Linux/macOS users to trigger restores and track progress.
  • Mention any limitations or requirements for Linux/macOS users explicitly.
GitHub Create Pull Request
← Previous Page 15 of 53 Next →