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 226-250 of 2475 flagged pages
Service Fabric Service Fabric application upgrade ...s/service-fabric/service-fabric-application-upgrade.md
Medium Priority View Details →
Scanned: 2026-03-08 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 upgrade demonstrates a notable Windows bias. PowerShell is the only CLI example provided, and Windows-specific tools (like PowerShell cmdlets and references to http.sys) are mentioned exclusively. There are no Linux or cross-platform CLI examples (such as Azure CLI, REST API, or Service Fabric CLI), and Windows terminology appears first or exclusively in several sections. This creates friction for Linux/macOS users, who may not be able to follow the instructions directly.
Recommendations
  • Add equivalent Linux/macOS examples using Service Fabric CLI (sfctl), Azure CLI, or REST API for application upgrade operations.
  • Clarify which steps are Windows-only and provide cross-platform alternatives where possible.
  • Mention Linux-specific considerations, such as differences in certificate handling (since http.sys is Windows-specific), and provide guidance for Linux clusters.
  • Reorder or balance examples so that Windows and Linux approaches are presented equally.
  • Link to documentation for Linux clusters and cross-platform tooling.
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-03-08 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 provides a broad overview of Azure Service Fabric, which supports both Windows and Linux. However, there are several instances where Windows-specific tools, services, and examples are mentioned first or exclusively, such as references to PowerShell cmdlets, Windows services (FabricHost.exe), and standalone cluster creation only for Windows. Linux equivalents are sometimes mentioned later or not at all, and some sections lack Linux-specific guidance or examples.
Recommendations
  • Ensure Linux examples and tools (such as Bash, Linux CLI usage, and Linux-specific cluster creation) are presented alongside or before Windows examples where applicable.
  • Clarify when features are Windows-only and provide alternative guidance or links for Linux users.
  • Add explicit instructions or links for Linux cluster creation and management, or clearly state limitations.
  • Balance references to PowerShell with Bash/CLI equivalents for Linux users.
  • Highlight Linux support in programming models and deployment scenarios more prominently.
GitHub Create Pull Request
Service Fabric Networking patterns for Azure Service Fabric ...s/service-fabric/service-fabric-patterns-networking.md
Medium Priority View Details →
Scanned: 2026-03-08 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 only PowerShell-based deployment examples and command snippets, with no mention of Azure CLI or Bash equivalents. Windows tools and patterns (such as RDP and PowerShell) are referenced exclusively or before any Linux alternatives. There are no Linux/macOS-specific instructions or examples, which creates friction for non-Windows users deploying Service Fabric clusters with Azure networking features.
Recommendations
  • Add Azure CLI (az) command examples alongside PowerShell for all deployment steps.
  • Include Bash shell snippets for Linux/macOS users where relevant.
  • Mention SSH as a secure jump box alternative to RDP for accessing VMs in the virtual network.
  • Clarify that Service Fabric clusters can be managed and deployed from Linux/macOS as well as Windows, and provide links or references to cross-platform tooling.
  • Where PowerShell is used, note that equivalent steps can be performed with Azure CLI or ARM templates from any OS.
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-03-08 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 notable Windows bias. All deployment, upgrade, and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) without any Azure CLI or Bash equivalents. Application packaging is described via Visual Studio, a Windows-centric tool, with no mention of cross-platform alternatives. No Linux/macOS-specific instructions or examples are provided, and Windows tools are referenced first and exclusively.
Recommendations
  • Add Azure CLI examples for deployment, upgrade, and deletion tasks alongside PowerShell.
  • Include instructions for packaging applications using cross-platform tools (e.g., dotnet CLI, SF tooling) instead of only Visual Studio.
  • Mention how Linux/macOS users can perform equivalent actions, including uploading packages and managing resources.
  • Consider providing Bash scripts or referencing Azure Cloud Shell for cross-platform parity.
GitHub Create Pull Request
Service Fabric Service communication with the ASP.NET Core ...vice-fabric-reliable-services-communication-aspnetcore.md
Medium Priority View Details →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation provides thorough coverage of both HTTP.sys (Windows-only) and Kestrel (cross-platform) web servers for ASP.NET Core integration with Azure Service Fabric Reliable Services. However, Windows-specific tools and patterns (such as HTTP.sys, netsh, and Windows HTTP Server API) are described in detail, often before their Linux equivalents or alternatives. There are explicit notes about HTTP.sys being Windows-only, but Linux/macOS users are not given equivalent examples or troubleshooting guidance for non-Windows environments. Kestrel is described as the preferred cross-platform option, but Linux-specific considerations (such as firewall configuration, service manifest setup, or troubleshooting) are not addressed. Additionally, some example code and configuration steps are presented with Windows-centric assumptions (e.g., endpoint registration, port sharing), and Visual Studio debugging is referenced as a next step without mention of Linux/macOS alternatives.
Recommendations
  • Add explicit Linux/macOS guidance for Service Fabric development and deployment, including example commands and troubleshooting steps.
  • Provide parity in example code and configuration instructions for Linux environments (e.g., how to configure firewall rules, manage ports, and debug applications on Linux).
  • Mention cross-platform development tools (such as VS Code or CLI-based debugging) alongside Visual Studio.
  • Clarify any differences in Service Fabric setup, deployment, and runtime behavior between Windows and Linux, especially for Kestrel.
  • Include links or references to Linux/macOS-specific documentation for Service Fabric and ASP.NET Core.
GitHub Create Pull Request
Service Fabric Azure Service Fabric DNS service ...n/articles/service-fabric/service-fabric-dnsservice.md
Medium Priority View Details →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides PowerShell examples for setting DNS names but does not offer equivalent Linux CLI or scripting examples. Windows tools (PowerShell, Visual Studio) are referenced for service configuration, while Linux-specific guidance is limited. The Linux support section is brief and highlights limitations, but does not provide parity in walkthroughs or examples for Linux users.
Recommendations
  • Add Linux CLI (e.g., Azure CLI, Bash) examples for configuring DNS service and setting DNS names.
  • Include instructions for editing service manifests and deploying on Linux clusters using common Linux tools.
  • Clarify how Linux users can accomplish tasks that are shown with PowerShell or Visual Studio, possibly referencing cross-platform tools or alternatives.
  • Expand the Linux section to provide step-by-step guidance for containerized services, including how to enable DNS service without the portal.
  • Where possible, present Linux and Windows examples side-by-side, or indicate which steps are platform-specific.
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-03-08 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 and retrieving the cluster manifest. It also mentions Visual Studio (a Windows-centric tool) for publishing to Azure. While Service Fabric is cross-platform, the documentation leans towards Windows tools and patterns, with PowerShell and Visual Studio mentioned before alternatives. There are no explicit Linux/macOS command examples or references to cross-platform CLI tools.
Recommendations
  • Add examples using Azure CLI or Service Fabric CLI (sfctl), which are cross-platform and can be used on Linux/macOS.
  • Mention and provide sample commands for retrieving cluster manifests using REST API or .NET Core (not just .NET Framework), highlighting their cross-platform compatibility.
  • Include guidance for Linux/macOS users, such as how to configure and verify ImageStoreConnectionString using non-Windows tools.
  • Balance references to Visual Studio with alternatives like VS Code or command-line deployment methods.
GitHub Create Pull Request
Service Fabric Configure or modify a Service Fabric managed cluster node type ...vice-fabric/how-to-managed-cluster-modify-node-type.md
Medium Priority View Details →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides command-line examples exclusively using Azure PowerShell cmdlets, with no mention of Azure CLI or Bash scripting alternatives. This creates friction for Linux and macOS users who may prefer or require cross-platform tools. Additionally, the documentation refers to Windows-centric concepts such as drive letters (e.g., 'S', 'C', 'D'), which are not applicable to Linux environments, without clarifying their relevance or providing Linux equivalents.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all command-line operations (adding, removing, scaling node types, etc.), as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Where drive letters are discussed, clarify that this is a Windows-specific concept and explain how disk mounting works for Linux-based node types, or note if only Windows OS images are supported.
  • Explicitly state OS support (Windows/Linux) for node types and features where relevant, and provide examples for both if supported.
  • Consider adding Bash script examples for ARM template deployments, or reference the Azure CLI documentation for template deployment.
  • If certain operations are only possible with PowerShell or on Windows, clearly call this out to set expectations for non-Windows users.
GitHub Create Pull Request
Service Fabric Deny assignment policy for Service Fabric managed clusters ...cles/service-fabric/managed-cluster-deny-assignment.md
Medium Priority View Details →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides examples and links primarily for Azure PowerShell modules when describing best practices for managing Service Fabric managed clusters. PowerShell is a Windows-centric tool, and its mention precedes Azure CLI and other cross-platform tools. While Azure CLI and ARM/Bicep are referenced in the utility table, actionable examples and guidance are PowerShell-heavy, which may create friction for Linux/macOS users.
Recommendations
  • Add explicit Azure CLI examples alongside PowerShell examples for key actions (e.g., deleting NodeTypes, restarting/reimaging scale sets).
  • Mention Azure CLI before or alongside PowerShell in best practices sections to reinforce cross-platform parity.
  • Clarify that Azure CLI and ARM/Bicep are fully supported and provide links to relevant CLI documentation for Service Fabric managed clusters.
  • Consider including sample commands for both PowerShell and CLI where possible.
GitHub Create Pull Request
Service Fabric Migrate an Azure Service Fabric cluster to availability zone support ...ce-fabric/migrate-service-fabric-availability-zones.md
Medium Priority View Details →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides extensive PowerShell-based migration steps and examples, especially for the Basic SKU migration scenario. PowerShell commands and Windows-centric paths (e.g., 'D:\\SvcFab') are used exclusively, with no equivalent Bash, Azure CLI, or Linux/macOS-friendly instructions. Sample templates and migration walkthroughs are often Windows-focused, and Windows tooling (PowerShell, Windows paths) is presented first or exclusively, even though Service Fabric supports Linux node types.
Recommendations
  • Provide Azure CLI or Bash equivalents for all PowerShell commands, especially for resource deployment, node disabling, and DNS updates.
  • Include Linux/macOS-friendly instructions and examples, such as using Azure CLI or REST API for cluster management.
  • Ensure sample templates and walkthroughs reference both Windows and Linux node types (e.g., include Ubuntu examples alongside Windows).
  • Clarify which steps are OS-agnostic and which are Windows-specific, and offer guidance for Linux users where possible.
GitHub Create Pull Request
Service Fabric X.509 Certificate-based Authentication in a Service Fabric Cluster ...ticles/service-fabric/cluster-security-certificates.md
Medium Priority View Details →
Scanned: 2026-03-08 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, but exhibits Windows bias in several areas. Windows 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 (e.g., 'var/lib/sfcerts'). Troubleshooting guidance and error codes are Windows-centric, and there are no Linux-specific examples or troubleshooting steps. This creates friction for Linux users, though most concepts are cross-platform.
Recommendations
  • Provide Linux-specific certificate store paths, commands, and troubleshooting steps alongside Windows examples.
  • Include Linux error codes and log locations relevant to Service Fabric clusters.
  • Clarify when instructions or examples are Windows-only, and offer Linux alternatives where possible.
  • Expand troubleshooting guidance to address Linux scenarios, such as certificate permissions and storage.
  • Ensure parity in example ordering (e.g., mention Linux paths/tools before or alongside Windows ones).
GitHub Create Pull Request
Service Fabric Azure Service Fabric container image management .../articles/service-fabric/container-image-management.md
Medium Priority View Details →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation references Windows container base images (microsoft/windowsservercore, microsoft/nanoserver) exclusively in the 'ContainerImagesToSkip' setting, and provides examples that focus on Windows images. There are no Linux container image examples or explicit mention of Linux container management, despite Service Fabric supporting both Windows and Linux containers. The documentation does not provide parity for Linux users in terms of examples or guidance.
Recommendations
  • Add examples of Linux container images (e.g., 'docker.io/library/alpine', 'mcr.microsoft.com/dotnet/runtime') in the 'ContainerImagesToSkip' setting and elsewhere.
  • Clarify that the cleanup and management settings apply to both Windows and Linux containers, if applicable.
  • Provide guidance or notes for Linux-specific scenarios, such as differences in image management or cleanup behavior.
  • Ensure that descriptions and examples are inclusive of both Windows and Linux container images.
GitHub Create Pull Request
Service Fabric Introduction to the Service Fabric Infrastructure Service .../articles/service-fabric/infrastructure-service-faq.md
Medium Priority View Details →
Scanned: 2026-03-08 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 or cross-platform CLI examples are given, and Windows tools/patterns are mentioned first or exclusively.
Recommendations
  • Add equivalent Linux/macOS command-line examples using Azure CLI or REST API if available.
  • Clarify whether Service Fabric Explorer is accessible cross-platform or provide alternatives for Linux users.
  • Mention any prerequisites or limitations for Linux/macOS users when performing cluster operations.
  • If PowerShell is required, note how Linux/macOS users can install and use PowerShell Core.
GitHub Create Pull Request
Service Fabric Service Fabric Explorer blocking operations ...ged-cluster-service-fabric-explorer-blocking-operation.md
Medium Priority View Details →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides management guidance for Service Fabric Explorer blocking operations, but consistently references Az PowerShell cmdlets (e.g., Remove-AzResource, AzSF PowerShell cmdlet) for resource management tasks. While the 'az resource' CLI is mentioned once, PowerShell examples and terminology are prioritized, which may create friction for Linux/macOS users who typically use the Azure CLI or ARM templates. No Linux-specific examples or explicit cross-platform guidance is provided.
Recommendations
  • Include Azure CLI equivalents for all PowerShell cmdlet examples, especially for resource deletion and creation.
  • Explicitly mention that ARM templates and Azure CLI are cross-platform and suitable for Linux/macOS users.
  • Provide links to Azure CLI documentation alongside PowerShell links.
  • Clarify that Az PowerShell cmdlets are Windows-centric and suggest alternatives for non-Windows environments.
GitHub Create Pull Request
Service Fabric Monitor Azure Service Fabric ...main/articles/service-fabric/monitor-service-fabric.md
Medium Priority View Details →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation covers monitoring Azure Service Fabric clusters on both Windows and Linux, but there are several instances where Windows tools and patterns (such as EventStore APIs, Event Log/Event Viewer, Diagnostics Agent) are mentioned first or exclusively, with Linux equivalents referenced later or less prominently. Some examples and tutorials focus on .NET/Windows, and Linux-specific guidance is often relegated to links or brief notes. There are missing Linux-specific examples for some monitoring scenarios, and Windows-centric terminology (ETW, Event Log) is used without always providing Linux alternatives (LTTng, Syslog) in equal detail.
Recommendations
  • Provide Linux-specific examples and walkthroughs for key monitoring scenarios, especially where Windows tools (EventStore APIs, Event Log, Diagnostics Agent) are highlighted.
  • Ensure Linux equivalents (LTTng, Syslog, Azure Monitor agent configuration) are described with equal prominence and detail, not just referenced via links.
  • Add sample code or configuration snippets for Linux clusters where Windows/PowerShell examples are given.
  • Where possible, present cross-platform instructions or note differences clearly, rather than defaulting to Windows-first explanations.
  • Include more explicit guidance for monitoring .NET Core applications on Linux, not just .NET Framework/.NET on Windows.
GitHub Create Pull Request
Service Fabric Describing Azure Service Fabric apps and services ...ic/service-fabric-application-and-service-manifests.md
Medium Priority View Details →
Scanned: 2026-03-08 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 manifest files. It explicitly recommends opening the ServiceFabricServiceModel.xsd schema in Visual Studio at a Windows file path (C:\Program Files\Microsoft SDKs\Service Fabric\schemas\...), which is only valid on Windows. No equivalent instructions or file paths are provided for Linux/macOS users, nor are cross-platform XML editors or schema validation tools mentioned. Additionally, PowerShell is referenced as a way to create service instances, with no mention of cross-platform alternatives.
Recommendations
  • Provide instructions or file paths for accessing the ServiceFabricServiceModel.xsd schema on Linux/macOS, or clarify if it is not available.
  • Mention cross-platform XML editors (such as VS Code with XML extensions) and how to load the schema for IntelliSense and validation.
  • When referencing PowerShell for service creation, also mention cross-platform tools (such as Azure CLI or Service Fabric CLI) and provide example commands.
  • Review the documentation for other implicit Windows-first assumptions and add Linux/macOS guidance where applicable.
GitHub Create Pull Request
Service Fabric Application lifecycle in Service Fabric ...service-fabric/service-fabric-application-lifecycle.md
Medium Priority View Details →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page frequently references PowerShell cmdlets and Windows-centric tools for Service Fabric application lifecycle management, often listing them before or alongside REST and .NET API methods. There is minimal mention of Linux-specific CLI tools (e.g., sfctl), and no explicit Linux command examples are provided. The bias is most evident in deployment, upgrade, and cleanup sections, where PowerShell is the primary scripting interface discussed.
Recommendations
  • Add explicit examples using sfctl (Service Fabric CLI) for Linux/macOS users in each lifecycle phase, especially for deployment, upgrade, and removal.
  • Where PowerShell cmdlets are mentioned, also provide equivalent sfctl or Azure CLI commands.
  • Clarify which tools are cross-platform and which are Windows-only, to help users choose the right interface.
  • Consider restructuring lists so REST, sfctl, and PowerShell are presented in parallel, not always with PowerShell first.
  • Add notes or links to Linux/macOS-specific guidance for Service Fabric operations.
GitHub Create Pull Request
Service Fabric Architecture of Azure Service Fabric ...articles/service-fabric/service-fabric-architecture.md
Medium Priority View Details →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation mentions PowerShell cmdlets as the primary example for management operations, and references Windows security as a transport option before X509 certificates. No Linux-specific tools or examples (such as Bash, CLI, or Linux security mechanisms) are provided, and PowerShell is presented as the default management interface.
Recommendations
  • Add examples or references to Azure CLI or Bash scripts for management operations alongside PowerShell.
  • Mention Linux-compatible security mechanisms (such as OpenSSL or SSH) in the transport subsystem discussion.
  • Clarify that Service Fabric management can be performed from Linux/macOS using REST APIs or Azure CLI, not just PowerShell.
  • Ensure parity in documentation by listing cross-platform tools and interfaces before or alongside Windows-specific ones.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager - Application Groups ...ice-fabric-cluster-resource-manager-application-groups.md
Medium Priority View Details →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page provides only PowerShell and C# examples for managing Service Fabric Application Groups, with no Linux/macOS CLI or scripting equivalents. All command-line instructions use PowerShell cmdlets, which are native to Windows. There is no mention of cross-platform tools (such as Azure CLI, REST API, or Bash scripts) that Linux/macOS users could use to perform equivalent operations.
Recommendations
  • Add Azure CLI examples for all PowerShell cmdlet operations, if supported.
  • Mention and provide REST API examples for managing Application Groups, especially for users on Linux/macOS.
  • Clarify whether PowerShell cmdlets can be used via PowerShell Core on Linux/macOS, or if they are Windows-only.
  • Include Bash or shell script examples where possible.
  • Explicitly state platform requirements for the PowerShell examples, and link to cross-platform alternatives if available.
GitHub Create Pull Request
Service Fabric RunToCompletion semantics and specifications ...blob/main/articles/service-fabric/run-to-completion.md
Medium Priority View Details →
Scanned: 2026-03-08 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 a notable Windows bias. All code examples use Windows containers (nanoserver), Windows-specific commands (cmd, echo, ping, set, exit), and reference Windows container compatibility. Query instructions are given only for PowerShell and C#, with no mention of Linux/macOS equivalents or CLI tools. There are no examples for Linux containers or Linux shell commands, and Windows terminology is used throughout.
Recommendations
  • Add equivalent examples using Linux containers (e.g., Ubuntu images) and Linux shell commands (bash, echo, ping, exit).
  • Clarify whether RunToCompletion semantics are supported for Linux containers and guest executables, and provide guidance if so.
  • Include instructions for querying deployment status using Azure CLI or Linux shell tools, if available.
  • Balance the documentation by showing both Windows and Linux scenarios, or explicitly state if the feature is Windows-only.
GitHub Create Pull Request
Service Fabric Learn about Azure Service Fabric application security ...ric/service-fabric-application-and-service-security.md
Medium Priority View Details →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation covers Azure Service Fabric application security in a generally cross-platform manner, but several sections show Windows bias. Windows-specific features (e.g., Active Directory, gMSA, BitLocker) are mentioned before or more prominently than Linux equivalents. Some examples and links focus on Windows tools or configurations, and Linux-specific guidance is sometimes missing or relegated to TODO comments.
Recommendations
  • Add Linux-specific examples and guidance where only Windows instructions are given (e.g., disk encryption, user accounts).
  • Ensure parity in mentioning both Windows and Linux options for securing hosting environments, containers, and application data at rest.
  • Where Windows tools (e.g., BitLocker, gMSA) are referenced, provide equivalent Linux solutions (e.g., dm-crypt/LUKS, Linux user/group management) or clarify if no equivalent exists.
  • Remove or resolve TODO comments about Linux features, providing concrete instructions or links.
  • When listing options, alternate or balance Windows and Linux mentions to avoid 'Windows-first' ordering.
GitHub Create Pull Request
Service Fabric Advanced Application Upgrade Topics ...-fabric/service-fabric-application-upgrade-advanced.md
Medium Priority View Details →
Scanned: 2026-03-08 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 extensive PowerShell examples and references, with no equivalent Linux CLI or cross-platform examples. Windows/PowerShell tools are mentioned exclusively, and there is no guidance for Linux/macOS users on how to perform Service Fabric application upgrades using CLI or REST APIs. The bias is notable, as Linux users may struggle to follow the instructions or complete the tasks without additional research.
Recommendations
  • Add Azure CLI examples for all PowerShell cmdlets shown, especially for service creation, upgrades, and parameter updates.
  • Mention and link to REST API documentation for Service Fabric management tasks, which are cross-platform.
  • Clarify which PowerShell cmdlets are available on Linux/macOS (via PowerShell Core), and provide guidance for users on those platforms.
  • Provide sample scripts or commands for Linux users, or explicitly state if certain tasks are Windows-only.
  • Reorganize sections to present cross-platform options first, or in parallel, rather than Windows/PowerShell exclusively.
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-03-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on PowerShell for all CLI examples, including REST API calls, and exclusively references the Microsoft.ServiceFabric.Powershell.Http module. There are no examples or guidance for Linux/macOS users (e.g., Bash, Azure CLI, curl), nor is there mention of cross-platform tools. This creates friction for non-Windows users, as Service Fabric clusters can be managed from Linux/macOS but the documentation does not provide parity.
Recommendations
  • Add Bash/curl examples for REST API calls alongside PowerShell examples.
  • Mention Azure CLI equivalents if available, or clarify if only PowerShell is supported.
  • Document any prerequisites or limitations for Linux/macOS users (e.g., certificate handling, authentication).
  • Reference cross-platform tools or SDKs where possible.
  • Explicitly state if certain modules (e.g., Microsoft.ServiceFabric.Powershell.Http) are Windows-only, and provide alternatives or workarounds.
GitHub Create Pull Request
Service Fabric Understanding periodic backup configuration ...-fabric-backuprestoreservice-configure-periodic-backup.md
Medium Priority View Details →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page is generally platform-neutral, but the 'File share' backup storage section exclusively references Windows file share paths (\\StorageServer\BackupStore) and Integrated Windows Authentication, without mentioning Linux-compatible alternatives or SMB mounting instructions for Linux. Windows authentication patterns are described first and in detail, while Linux or cross-platform approaches are missing.
Recommendations
  • Add examples or guidance for configuring file share backup storage using SMB mounts on Linux clusters, including sample paths and authentication methods.
  • Clarify whether Linux-based Service Fabric clusters can use file share backup storage, and if so, provide parity instructions for Linux authentication and mounting.
  • Mention cross-platform alternatives (such as NFS or Azure Files with Linux) if supported.
  • Explicitly state any limitations or requirements for Windows-only file share backup storage, so Linux/macOS users are aware.
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-03-08 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 code examples and instructions using PowerShell modules and cmdlets. There are no examples or guidance for Linux/macOS users, such as using Bash, curl, or cross-platform tools to interact with the REST API. The PowerShell module installation and usage instructions are presented first and exclusively, creating friction for non-Windows users.
Recommendations
  • Add Bash/curl examples for REST API calls, showing how Linux/macOS users can trigger backups and track progress.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is required for all operations, or if REST API calls can be made directly from any platform.
  • Provide guidance on authenticating and connecting to Service Fabric clusters from Linux/macOS, including certificate handling.
  • Explicitly state platform requirements or limitations if any features are Windows-only.
  • Consider including cross-platform CLI tools (e.g., Azure CLI) if available for Service Fabric backup operations.
GitHub Create Pull Request
← Previous Page 10 of 99 Next →