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 1576-1600 of 2475 flagged pages
Service Fabric Application lifecycle in Service Fabric ...service-fabric/service-fabric-application-lifecycle.md
Medium Priority View Details →
Scanned: 2026-02-12 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., PowerShell commands, .NET APIs) alongside REST APIs, but does not provide Linux-specific CLI examples (such as Azure CLI or sfctl) for critical lifecycle operations. PowerShell commands are often listed before REST API alternatives, and there is no explicit guidance for Linux/macOS users, despite Service Fabric supporting cross-platform clusters and management.
Recommendations
  • Add equivalent Azure CLI and sfctl command examples for all major lifecycle operations (deploy, upgrade, remove, etc.), especially in sections where only PowerShell cmdlets are shown.
  • Explicitly mention cross-platform tools (Azure CLI, sfctl) in each operation, not just in the introductory include.
  • Where PowerShell is referenced, clarify its platform limitations and suggest alternatives for Linux/macOS users.
  • Consider showing REST API, CLI, and PowerShell examples side-by-side, or in a consistent order (e.g., CLI first, then PowerShell), to avoid Windows-first bias.
  • Add a short section or note about managing Service Fabric applications from Linux/macOS, linking to relevant guides.
GitHub Create Pull Request
Service Fabric Advanced Application Upgrade Topics ...-fabric/service-fabric-application-upgrade-advanced.md
Medium Priority View Details →
Scanned: 2026-02-12 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 features PowerShell cmdlets for Service Fabric application upgrades, with all command-line examples and upgrade procedures shown exclusively in PowerShell syntax. There is no mention of Linux/macOS equivalents, such as the Service Fabric CLI (sfctl), nor are cross-platform tools or workflows discussed. Windows tools and patterns (PowerShell, Visual Studio) are referenced first and exclusively, creating friction for Linux/macOS users.
Recommendations
  • Add equivalent examples using the Service Fabric CLI (sfctl), which is cross-platform and supported on Linux/macOS.
  • Mention and link to documentation for sfctl and other cross-platform tools where PowerShell is referenced.
  • Clarify which features or commands are Windows-only, and which are available cross-platform.
  • Provide guidance for Linux/macOS users on how to perform upgrades and configuration using sfctl or REST APIs.
  • Include notes or sections for Linux/macOS users, especially where PowerShell or Visual Studio are referenced.
GitHub Create Pull Request
Service Fabric Custom Image .../articles/service-fabric/how-to-deploy-custom-image.md
Medium Priority View Details →
Scanned: 2026-02-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page is not strictly Windows-only, but it demonstrates Windows bias by consistently referring to 'custom windows images' and providing PowerShell examples for role assignment. Linux equivalents (such as Bash/CLI commands) are not provided, and Windows terminology is used first throughout. However, links to Linux custom image creation and Azure CLI image browsing are included, mitigating some bias.
Recommendations
  • Clarify that custom images can be Linux or Windows, and provide examples for both.
  • Add Azure CLI (bash) examples for role assignment alongside PowerShell.
  • Use neutral language (e.g., 'custom images' instead of 'custom windows images') unless the feature is truly Windows-only.
  • Show Linux ARM template image references and marketplace plan examples.
  • Explicitly state Linux support and link to relevant Linux documentation where possible.
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-12 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 examples (PowerShell) are often presented first, and Windows-specific tools (Windows Defender, Azure DSC, PowerShell commands) are discussed in dedicated sections. Windows terminology and tools are referenced more frequently, and some sections (Windows Defender, security baselines) are Windows-only, with Linux alternatives not always described. Linux examples are present but sometimes less detailed or positioned after Windows instructions.
Recommendations
  • Present Windows and Linux examples side-by-side or in parallel sections to avoid Windows-first ordering.
  • Expand Linux-specific guidance for security baselines and antimalware, referencing common Linux tools (e.g., SELinux, AppArmor, ClamAV) or Azure-supported Linux security extensions.
  • Clarify when a feature or tool is Windows-only and provide Linux alternatives or explicitly state if none exist.
  • Ensure parity in detail and clarity between Windows and Linux instructions, especially for certificate and secret management.
  • Add links to Linux-focused documentation where only Windows links are currently provided.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page for on-demand backup in Azure Service Fabric is heavily biased towards Windows/PowerShell usage. All code examples and instructions rely exclusively on PowerShell and the Microsoft.ServiceFabric.Powershell.Http module, with no mention of Linux/macOS-compatible tools or CLI alternatives. REST API usage is also shown only via PowerShell, and there are no Bash/cURL or cross-platform examples. This creates friction for Linux/macOS users, who may not have access to PowerShell or the required modules.
Recommendations
  • Add Bash/cURL examples for REST API calls, showing how to trigger backups and track progress using standard Linux/macOS tools.
  • Mention cross-platform alternatives to Microsoft.ServiceFabric.Powershell.Http, if available, or clarify if PowerShell Core (pwsh) is supported on Linux/macOS.
  • Provide guidance for Linux/macOS users on connecting to Service Fabric clusters and performing backup operations without PowerShell.
  • Explicitly state any limitations or requirements for non-Windows environments, and link to relevant documentation for Linux/macOS users.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides detailed examples for configuring auto scaling in Azure Service Fabric using C#, application manifests, and PowerShell. The PowerShell examples are Windows-specific, and there are no equivalent Linux CLI or scripting examples (such as Bash or Azure CLI). The documentation references Windows-specific tools and patterns (e.g., PowerShell cmdlets) without mentioning or demonstrating Linux alternatives, which may create friction for Linux users.
Recommendations
  • Add equivalent examples using Azure CLI or Bash scripts for configuring auto scaling policies, especially for Linux-based Service Fabric clusters.
  • Explicitly state when a given example or tool (such as PowerShell) is Windows-only, and provide guidance or links for Linux users.
  • Where possible, provide cross-platform instructions or note any limitations for Linux clusters (e.g., which features are supported on Linux vs. Windows).
  • Include a section or table summarizing which management tools and APIs are available on each platform (Windows, Linux, macOS).
GitHub Create Pull Request
Service Fabric Azure Service Fabric image store connection string ...fabric/service-fabric-image-store-connection-string.md
Medium Priority View Details →
Scanned: 2026-02-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page references PowerShell as the primary example for interacting with Service Fabric clusters (e.g., retrieving the cluster manifest), and links to PowerShell-based deployment guidance first. There is no explicit mention of Linux/macOS command-line tools or examples (such as Bash, Azure CLI, or cross-platform SDKs), and Windows-centric tools like Visual Studio are referenced for publishing. While Service Fabric is cross-platform, the documentation leans toward Windows workflows.
Recommendations
  • Add examples using Azure CLI or Bash scripts for retrieving cluster manifests and deploying applications, highlighting cross-platform approaches.
  • Mention cross-platform SDKs (e.g., .NET Core, Python) for programmatic access, and provide sample code or links.
  • Clarify that PowerShell examples can be run on Linux/macOS via PowerShell Core, or provide alternative commands.
  • Reference Visual Studio Code as a cross-platform IDE for deployment, not just Visual Studio.
  • Ensure links to deployment guides include both Windows and Linux/macOS workflows.
GitHub Create Pull Request
Service Fabric Upgrade an Azure Service Fabric standalone cluster ...ce-fabric/service-fabric-cluster-upgrade-standalone.md
Medium Priority View Details →
Scanned: 2026-02-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page references Windows-specific upgrade and configuration guides (e.g., links ending with '-windows-server.md'), and the Patch Orchestration Application is described only for Windows. There are no explicit Linux examples or equivalent Linux-focused upgrade/configuration guidance, suggesting a Windows-first approach and missing Linux parity.
Recommendations
  • Add links and examples for Linux-based Service Fabric standalone clusters, including upgrade and configuration instructions.
  • Clarify whether Service Fabric standalone clusters are supported on Linux, and if so, provide Linux-specific guidance or note any limitations.
  • Mention or link to any Linux patch orchestration solutions if available, or explicitly state if POA is Windows-only.
  • Ensure that references to configuration files and procedures are applicable to both Windows and Linux, or clearly differentiate when they are not.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation is heavily oriented toward Visual Studio workflows, referencing Windows-specific actions (Build/Rebuild/F5/Ctrl+F5/Publish) and UI elements. There are no examples or guidance for Linux/macOS users or cross-platform CLI workflows. The only mention of non-Visual Studio deployment is a brief reference to ARM and PowerShell cmdlets, with no Linux equivalents or detailed instructions.
Recommendations
  • Add explicit guidance for Linux/macOS users, including how to manage StartupServices.xml outside Visual Studio.
  • Provide CLI-based examples (e.g., Azure CLI, Service Fabric CLI) for deploying and configuring applications, not just PowerShell.
  • Clarify which parts of the workflow are Visual Studio/Windows-only and offer alternatives for cross-platform development.
  • Mention any limitations or support status for StartupServices.xml in non-Windows environments.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides a PowerShell-only example for deploying Service Fabric applications, references Windows file paths and certificate stores before mentioning Linux equivalents, and generally assumes a Windows-centric workflow. Linux-specific instructions are minimal and appear after the Windows context.
Recommendations
  • Provide equivalent Linux CLI (e.g., Azure CLI, sfctl) examples alongside PowerShell commands for deploying applications and overriding parameters.
  • Mention Linux certificate store paths and behaviors earlier and more prominently, not only as a note after Windows instructions.
  • Clarify any platform-specific differences in endpoint configuration and deployment, and link to Linux/macOS-specific guides where available.
  • Where file paths are referenced (e.g., schema definitions), include Linux equivalents if applicable.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation provides thorough coverage of X.509 certificate-based authentication in Service Fabric clusters, but exhibits Windows bias in several areas. Windows-specific terminology and tools (e.g., certificate store paths like LocalMachine\My, references to Win32 CryptoAPI, and event log channels) are mentioned first or exclusively, with Linux equivalents only briefly referenced or omitted. Troubleshooting sections and configuration examples often default to Windows-centric approaches, and PowerShell/C++ error codes are used without cross-platform alternatives.
Recommendations
  • Ensure Linux certificate store paths and management tools are described alongside Windows equivalents, not as afterthoughts.
  • Provide troubleshooting guidance for Linux clusters, including log locations and certificate management commands (e.g., using openssl or Linux-specific logs).
  • Include Linux/macOS error codes and diagnostic steps where C++/Windows error codes are given.
  • Clarify when a feature or configuration is Windows-only, and provide Linux alternatives or note limitations.
  • Balance example ordering so Linux and Windows are equally represented, or explicitly state platform applicability.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides examples for configuring Service Fabric managed cluster node types using Azure Portal, ARM templates, and PowerShell. PowerShell is the only CLI example provided, with no equivalent Bash, Azure CLI, or Linux/macOS shell instructions. PowerShell is presented as the exclusive scripting option for command-line operations, and is mentioned before any Linux-friendly alternatives. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer Azure CLI/Bash.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all command-line operations (add, remove, scale, configure placement properties, etc.).
  • Explicitly state that PowerShell examples are cross-platform (if true), or provide guidance for Linux/macOS users on how to use PowerShell Core or Azure CLI.
  • Where possible, provide Bash scripts or instructions for Linux/macOS environments.
  • Mention Azure CLI as an alternative in introductory sections and throughout the document.
  • Clarify any limitations or prerequisites for PowerShell usage on non-Windows platforms.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides a PowerShell-only example for bypassing Infrastructure Service, and references Service Fabric Explorer (a GUI tool typically used on Windows). No Linux/macOS CLI or tool alternatives are mentioned, and the PowerShell command is presented without cross-platform context. The overall guidance assumes Windows-centric patterns, creating friction for Linux/macOS users.
Recommendations
  • Provide equivalent CLI examples for Linux/macOS users, such as using Azure CLI or REST API where possible.
  • Clarify whether the PowerShell command can be run from PowerShell Core on Linux/macOS, or provide alternative commands.
  • Mention cross-platform tools or interfaces (e.g., Azure Portal, Service Fabric CLI) where relevant.
  • Add notes about Service Fabric Explorer accessibility from non-Windows platforms, or suggest 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-12 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. However, there is a notable Windows bias: PowerShell is the only scripting example provided for certificate enrollment, and the Key Vault VM extension is discussed exclusively in its Windows variant. The documentation references Windows-specific certificate store concepts (e.g., 'LocalMachine', 'MY'), and the linking-on-renewal feature is described as 'Only Windows'. There are no explicit Linux/macOS examples or guidance for equivalent certificate provisioning or automation, and Windows terminology/tools are used throughout, often without mentioning Linux alternatives.
Recommendations
  • Add CLI/bash examples for certificate enrollment and provisioning, using Azure CLI or REST API, to complement PowerShell scripts.
  • Document the Key Vault VM extension for Linux (if available), or clarify limitations and provide Linux-specific guidance for certificate provisioning.
  • Include references to Linux certificate stores (e.g., /etc/ssl/certs) and explain how Service Fabric clusters on Linux nodes should manage certificates.
  • Where Windows-specific features (like linking-on-renewal) are discussed, explicitly state Linux/macOS limitations or alternatives.
  • Ensure that JSON ARM templates and deployment steps are annotated for cross-platform applicability, noting any OS-specific requirements.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides several examples and links to Azure PowerShell modules for managing Service Fabric managed clusters, with PowerShell mentioned before Azure CLI and other cross-platform tools. While Azure CLI and ARM/Bicep templates are referenced, PowerShell is emphasized in the best practices section and specific tasks, potentially creating friction for Linux/macOS users who may prefer CLI or other cross-platform utilities.
Recommendations
  • Add explicit Azure CLI examples for all tasks currently demonstrated with Azure PowerShell (e.g., deleting NodeTypes, restarting/reimaging scale sets).
  • Mention Azure CLI alongside PowerShell in the best practices section, ensuring parity in guidance.
  • Where possible, provide code snippets or links for both PowerShell and CLI for common operations.
  • Clarify that Azure PowerShell is available cross-platform, but highlight CLI as a native option for Linux/macOS users.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page primarily references Az PowerShell cmdlets for managing Service Fabric resources, with explicit links to PowerShell modules. While the Azure CLI (az resource) is mentioned for deleting applications, PowerShell is presented first and more frequently. There are no Linux-specific examples or explicit mention of Linux/macOS compatibility for the recommended management operations.
Recommendations
  • Provide Azure CLI examples for all operations (e.g., unprovisioning application type versions, creating applications/services) alongside PowerShell examples.
  • Clarify that Azure CLI commands are cross-platform and highlight their usage for Linux/macOS users.
  • Ensure links to Azure CLI documentation are as prominent as PowerShell links.
  • Consider adding a note about the parity between PowerShell and Azure CLI for managing ARM-managed Service Fabric resources.
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-12 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 is a noticeable Windows bias. Windows-specific tools (such as EventStore APIs, Event Viewer, Diagnostics Agent) are mentioned first or exclusively, with Linux equivalents referenced later or less prominently. Some examples and tutorials focus on Windows/.NET, and Linux-specific instructions are often relegated to brief mentions or links. There are missing Linux-specific walkthroughs and examples, especially for cluster monitoring and event access.
Recommendations
  • Add Linux-specific examples and walkthroughs for cluster monitoring, event access, and log collection, similar to the Windows-focused tutorials.
  • Ensure Linux tools and patterns (such as LTTng, Syslog, and Linux agent configuration) are described in detail and given equal prominence to Windows tools.
  • Provide sample code and configuration snippets for Linux clusters, including how to access Service Fabric events and logs.
  • Where Windows tools are mentioned (e.g., Event Viewer, Diagnostics Agent), immediately reference the Linux equivalents and link to relevant guides.
  • Expand tutorials to include Linux application monitoring and diagnostics, not just .NET/Windows scenarios.
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-12 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, but the 'Next steps' section highlights Windows-centric tools (Visual Studio and PowerShell) for application upgrades, with no mention of Linux/macOS equivalents or CLI options. PowerShell and Visual Studio are Windows-first tools, and their exclusive mention creates friction for Linux/macOS users.
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/macOS.
  • Mention Visual Studio Code as a cross-platform IDE alternative for application management.
  • Clarify which upgrade methods are Windows-only and provide Linux/macOS alternatives where possible.
  • Include explicit guidance for Linux/macOS users in the 'Next steps' section.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page for Service Fabric application upgrades exhibits a notable Windows bias. PowerShell is the only command-line example provided, and all upgrade-related tooling references (such as Start-ServiceFabricApplicationUpgrade and Update-ServiceFabricService) are PowerShell cmdlets. There are no examples or instructions for Linux/macOS users (e.g., using sfctl or REST APIs), and Windows-specific tools (like http.sys) are referenced without Linux equivalents. The 'Next steps' section also prioritizes Visual Studio and PowerShell, both Windows-centric tools, with no mention of cross-platform alternatives.
Recommendations
  • Add equivalent examples using sfctl (the cross-platform Service Fabric CLI) for Linux/macOS users wherever PowerShell examples are shown.
  • Mention and link to REST API documentation for application upgrades as a platform-agnostic alternative.
  • Clarify when features or limitations (such as http.sys or certificate handling) are Windows-specific, and provide Linux/macOS guidance if applicable.
  • In the 'Next steps' section, include tutorials or references for upgrading applications using sfctl or REST APIs.
  • Where possible, present cross-platform examples first or in parallel with Windows/PowerShell examples.
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-12 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 demonstrates notable Windows bias. All code examples use Windows containers (nanoserver), Windows-specific commands (cmd, echo, ping, set, exit), and reference Windows container compatibility. Querying deployment status is described only via PowerShell and C# APIs, with no mention of Linux equivalents or CLI tools. There are no examples or guidance for Linux containers or Linux-based workflows, despite Service Fabric supporting containers in general.
Recommendations
  • Add examples using Linux containers (e.g., Ubuntu or Alpine images) with equivalent shell commands.
  • Provide guidance for querying deployment status using cross-platform tools, such as Azure CLI or REST APIs, or document Linux-compatible alternatives.
  • Clarify whether RunToCompletion semantics are supported for Linux containers and, if so, include relevant code snippets.
  • Present examples for both Windows and Linux environments, or explicitly state if the feature is Windows-only.
  • Avoid referencing Windows container version compatibility exclusively; mention Linux container considerations if applicable.
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-12 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 and validating manifest XML files. It explicitly recommends opening the Service Fabric XSD schema in Visual Studio using a Windows file path ("C:\Program Files\Microsoft SDKs\Service Fabric\schemas\ServiceFabricServiceModel.xsd") and does not mention Linux or cross-platform alternatives for schema validation or authoring. Additionally, PowerShell is referenced as a way to create service instances, with no mention of Linux equivalents (e.g., Azure CLI, Bash scripts).
Recommendations
  • Provide instructions or examples for validating manifest XML files on Linux/macOS, such as using xmllint, VS Code with the XML extension, or cross-platform editors.
  • Mention the location of the ServiceFabricServiceModel.xsd schema on Linux clusters, or clarify if it is only available on Windows.
  • When referencing PowerShell for service creation, also mention Azure CLI or REST API alternatives that are available cross-platform.
  • Where file paths are given, provide Linux/macOS equivalents if applicable, or clarify platform limitations.
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-12 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 cross-platform context, but exhibits mild Windows bias. Windows-specific features (e.g., AD accounts, gMSA, BitLocker) are mentioned before or more prominently than Linux equivalents. Some sections (e.g., disk encryption, user accounts) provide Windows-only examples or reference Windows tools, while Linux guidance is missing or relegated to TODOs.
Recommendations
  • Add explicit Linux examples for disk encryption (e.g., using Azure Disk Encryption with Linux VMSS, or referencing Linux encryption tools).
  • Provide parity in user account configuration: clarify how Linux clusters handle service user accounts, and add examples for Linux service principals.
  • When referencing Windows-specific features (e.g., BitLocker, gMSA), clearly indicate their platform scope and provide Linux alternatives or links where possible.
  • Ensure that Linux and Windows examples are presented together or alternately, rather than Windows-first.
  • Complete the TODO for 'Encrypt disks on Linux clusters?' with actionable guidance.
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-12 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 for restoring backups in Azure Service Fabric is heavily biased towards Windows and PowerShell usage. All command-line examples use PowerShell syntax and require the Microsoft.ServiceFabric.Powershell.Http module, which is Windows-centric. There are no examples or guidance for Linux/macOS users (e.g., using Bash, curl, or cross-platform Service Fabric CLI). Windows tools and patterns are mentioned exclusively and presented first, with no mention of Linux equivalents or alternative workflows.
Recommendations
  • Provide equivalent examples using Bash/curl for REST API calls, suitable for Linux/macOS users.
  • Clarify whether the PowerShell module is required for all platforms, or suggest cross-platform alternatives (e.g., Azure CLI, Service Fabric CLI, or direct REST API usage).
  • Add explicit instructions for Linux/macOS environments, including certificate handling and authentication steps.
  • Indicate platform requirements and limitations for each method (PowerShell module, Service Fabric Explorer, REST API).
  • Consider reordering or grouping examples by platform, or clearly labeling Windows-only steps.
GitHub Create Pull Request
Service Fabric Health monitoring in Service Fabric ...s/service-fabric/service-fabric-health-introduction.md
Medium Priority View Details →
Scanned: 2026-02-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides a PowerShell-only example for reporting and evaluating application health in Service Fabric, without offering equivalent Linux/macOS CLI or REST API examples. The text mentions REST as an option but does not demonstrate its usage. This creates friction for Linux/macOS users, as PowerShell is not natively available on those platforms and Service Fabric clusters can run on Linux nodes.
Recommendations
  • Add equivalent examples using the Service Fabric CLI (sfctl), which is cross-platform and supported on Linux/macOS.
  • Provide REST API example(s) for health reporting and querying, as REST is platform-agnostic.
  • Clarify in the example section that PowerShell is Windows-specific, and link to Linux/macOS alternatives.
  • Ensure future documentation includes both Windows and Linux/macOS usage patterns where applicable.
GitHub Create Pull Request
Service Fabric Understanding periodic backup configuration ...-fabric-backuprestoreservice-configure-periodic-backup.md
Medium Priority View Details →
Scanned: 2026-02-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page for configuring periodic backups in Azure Service Fabric is mostly platform-neutral, focusing on REST API usage and JSON configuration. However, in the 'File share' backup storage section, only Windows-style file share paths (\\StorageServer\BackupStore) and Integrated Windows Authentication are mentioned, with no reference to Linux or SMB/CIFS equivalents. Windows authentication patterns are described first and exclusively, potentially creating friction for Linux users wishing to use file shares. There are no explicit Linux examples or guidance for configuring file shares from Linux nodes.
Recommendations
  • Add examples and guidance for configuring file share backup storage from Linux-based Service Fabric clusters, including SMB/CIFS mount instructions and authentication options.
  • Clarify whether Linux clusters can use file share backup storage and, if so, provide sample paths and authentication methods relevant to Linux.
  • Mention any limitations or differences for Linux clusters regarding file share backup storage.
  • Consider including both Windows and Linux file share path formats and authentication patterns in examples.
GitHub Create Pull Request
← Previous Page 64 of 99 Next →