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 1926-1950 of 2475 flagged pages
Service Fabric Specifying Service Fabric service endpoints ...ce-fabric/service-fabric-service-manifest-resources.md
Medium Priority View Details →
Scanned: 2026-02-04 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides PowerShell-based deployment examples and references to Windows file paths and certificate stores before mentioning Linux equivalents. The main deployment example uses PowerShell, and the Service Fabric SDK schema path is given only in Windows format. Linux-specific details (such as certificate store location) are mentioned only briefly and after Windows instructions.
Recommendations
  • Provide equivalent Linux/macOS deployment commands (e.g., using Azure CLI or Bash scripts) alongside PowerShell examples.
  • Mention Linux file paths and certificate store locations in parallel with Windows paths, not only as a note.
  • Clarify any platform-specific differences in endpoint configuration and deployment, and link to Linux/macOS-specific guides where relevant.
  • Add explicit examples for Linux clusters, including how to deploy and manage endpoints using Linux tools.
GitHub Create Pull Request
Service Fabric Fault Analysis Service overview .../service-fabric/service-fabric-testability-overview.md
Medium Priority View Details →
Scanned: 2026-02-04 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 Fault Analysis Service overview provides usage examples and tooling references primarily for C# (via .NET and NuGet) and PowerShell, both of which are traditionally Windows-centric. The PowerShell instructions assume use of the Service Fabric SDK and PowerShell module, with no mention of Linux/macOS equivalents (such as Bash, Azure CLI, or REST API usage). There are no examples or guidance for Linux/macOS users, nor is there any indication that the Fault Analysis Service is Windows-only.
Recommendations
  • Add examples for using the Fault Analysis Service from Linux/macOS environments, such as via Azure CLI, Bash, or REST API.
  • Clarify platform support for the Fault Analysis Service (if it is cross-platform, explicitly state so; if not, explain limitations).
  • Provide links or references to documentation for Linux/macOS users, including installation and usage instructions for Service Fabric SDK on those platforms.
  • Include sample commands or code snippets for non-Windows environments to ensure parity.
GitHub Create Pull Request
Service Fabric Custom Image .../articles/service-fabric/how-to-deploy-custom-image.md
Medium Priority View Details →
Scanned: 2026-02-03 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page primarily references Windows custom images and provides PowerShell commands for role assignment, with no equivalent Linux CLI or Bash examples. While it mentions Azure Marketplace images and links to both Linux and Windows image tutorials, the main workflow and examples are Windows-centric, and Linux-specific instructions are missing for key steps.
Recommendations
  • Provide equivalent Azure CLI or Bash examples for role assignment and other operations currently shown only in PowerShell.
  • Clarify whether Linux custom images are supported for Service Fabric Managed Clusters and, if so, include explicit instructions and examples for Linux images.
  • Ensure that references to image creation and deployment include both Windows and Linux workflows, or clearly state any platform limitations.
  • Where links to external tutorials are provided, summarize the Linux steps inline for parity.
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-03 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides examples for managing Service Fabric managed cluster node types using the Azure Portal, ARM templates, and PowerShell. However, all CLI/scripted examples use PowerShell cmdlets (e.g., New-AzServiceFabricManagedNodeType, Remove-AzServiceFabricManagedNodeType), with no mention of Azure CLI equivalents or Bash scripting. There are no Linux/macOS-specific instructions or examples, and PowerShell is presented as the only scripting interface, which may create friction for users on non-Windows platforms.
Recommendations
  • Add Azure CLI examples for all operations currently shown with PowerShell (e.g., adding, removing, scaling node types).
  • Explicitly state whether PowerShell cmdlets are cross-platform (PowerShell Core) or require Windows.
  • If Azure CLI does not support certain operations, clarify this and provide guidance for Linux/macOS users (e.g., using ARM templates via az deployment).
  • Consider including Bash scripting examples for ARM template deployments.
  • Add a note about cross-platform management options for Service Fabric managed clusters.
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-03 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-based workflows, requiring the Microsoft.ServiceFabric.Powershell.Http module and providing all code examples in PowerShell. There are no CLI, Bash, or cross-platform REST examples using tools like curl, nor any mention of Linux/macOS alternatives for connecting to the cluster or invoking REST APIs. This creates friction for Linux/macOS users, who must translate all examples and may not have access to the required PowerShell modules.
Recommendations
  • Provide equivalent examples using Bash and curl for REST API calls, demonstrating how to authenticate and invoke the same Service Fabric APIs from Linux/macOS.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is available and supported on PowerShell Core (pwsh) on Linux/macOS. If not, explicitly state this limitation.
  • Include instructions for connecting to Service Fabric clusters and managing certificates on Linux/macOS, or link to relevant documentation.
  • Where possible, use Azure CLI or cross-platform tools for authentication and management, or at least mention them as alternatives.
  • Add a section summarizing cross-platform support and any limitations for non-Windows users.
GitHub Create Pull Request
Service Fabric Advanced Application Upgrade Topics ...-fabric/service-fabric-application-upgrade-advanced.md
Medium Priority View Details →
Scanned: 2026-02-03 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 cmdlets for Service Fabric application upgrades, with all command-line examples using PowerShell syntax and referencing Windows-specific tools. There are no CLI or Linux-native examples (such as Azure CLI, Bash, or REST API), and the documentation does not mention or link to cross-platform alternatives. This creates friction for Linux/macOS users managing Service Fabric clusters.
Recommendations
  • Add Azure CLI examples (az sf application upgrade, az sf service create, etc.) alongside PowerShell cmdlets.
  • Mention REST API options for application and service upgrades, with example payloads.
  • Clarify which operations are only available via PowerShell (if any), and provide guidance for Linux/macOS users.
  • Link to cross-platform Service Fabric SDK/CLI documentation where appropriate.
  • If PowerShell Core (pwsh) is supported cross-platform, clarify this and provide examples using it on Linux/macOS.
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-03 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides some cross-platform information (e.g., mentions both 'ServiceFabricLinuxNode' and 'ServiceFabricNode' in the extension type), but several examples and guidance are Windows-centric. The dataPath example uses a Windows path (D:\\SvcFab), and the 'Next steps' section links to PowerShell scripts for RDP port and user management, which are Windows-specific. There are no explicit Linux/macOS command examples or references to SSH or Linux-native tools for remote access or management.
Recommendations
  • Add Linux/macOS-specific examples for remote connection (e.g., SSH instructions) alongside or in place of RDP/PowerShell examples.
  • Provide Linux file path examples (e.g., /var/lib/servicefabric) in the extension snippet and property descriptions.
  • Include references or links to Linux-native management scripts or Azure CLI usage for Linux clusters.
  • Clarify in the 'Next steps' section which scripts or guides are Windows-only, and provide Linux equivalents where possible.
GitHub Create Pull Request
Service Fabric Secure an Azure Service Fabric cluster ...cles/service-fabric/service-fabric-cluster-security.md
Medium Priority View Details →
Scanned: 2026-02-03 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation frequently references Windows Server clusters and Windows security options, providing explicit links and instructions for Windows scenarios. While it mentions that concepts apply to both Linux and Windows clusters, there are no direct examples, instructions, or links for Linux standalone clusters. Windows-specific configuration steps and recommendations are given more prominence, and Linux users may find it unclear how to implement equivalent security measures for standalone clusters.
Recommendations
  • Add explicit instructions and links for securing standalone Linux Service Fabric clusters, including certificate setup and configuration.
  • Provide parity in examples and walkthroughs for Linux environments, such as using Linux tools (e.g., OpenSSL) for certificate generation and installation.
  • Clarify which security features and steps apply equally to Linux clusters, and highlight any differences or limitations.
  • Include Linux-specific recommendations and best practices for Service Fabric cluster security.
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-03 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides code examples for configuring auto scaling in Azure Service Fabric using application manifests, C# APIs, and PowerShell. However, all command-line examples are exclusively in PowerShell, with no Linux shell (bash/CLI) equivalents. The PowerShell cmdlets and object types shown are Windows-centric, and there is no mention of how to perform these operations on Linux clusters or using cross-platform tools. This creates friction for Linux users, especially those running containerized workloads on Linux nodes.
Recommendations
  • Add equivalent examples using Azure CLI or REST API, which are cross-platform and usable on Linux/macOS.
  • Explicitly document any differences or limitations for Linux clusters, especially regarding management tools and supported features.
  • If PowerShell is required, clarify whether PowerShell Core (cross-platform) is supported and provide installation guidance for Linux/macOS.
  • Include bash or shell script examples for common operations where possible.
  • Reference Linux-specific documentation or tooling for Service Fabric cluster management.
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-02-03 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides PowerShell and ApplicationManifest.xml (Visual Studio) examples for setting DNS names, but does not include Linux-native equivalents (e.g., Azure CLI, Bash, or cross-platform tools). It also references Visual Studio and PowerShell before mentioning ARM templates, and does not provide Linux command-line examples for common tasks. Additionally, enabling DNS service through the Azure portal is not supported for Linux clusters, but this limitation is noted. Overall, the documentation assumes a Windows-centric workflow for several key operations.
Recommendations
  • Add Azure CLI examples for enabling DNS service and setting DNS names, especially for Linux users.
  • Provide Bash or cross-platform scripting examples where PowerShell is used.
  • Explicitly mention and link to Linux-native tools or workflows for managing Service Fabric clusters and services.
  • Clarify which steps are Windows-only and provide alternative instructions for Linux where possible.
  • Reorder sections to present ARM template and CLI-based approaches before PowerShell and Visual Studio examples, to avoid Windows-first bias.
GitHub Create Pull Request
Service Fabric Fault Analysis Service overview .../service-fabric/service-fabric-testability-overview.md
Medium Priority View Details →
Scanned: 2026-02-03 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page for the Fault Analysis Service overview provides usage instructions for C# (via the Microsoft.ServiceFabric NuGet package) and PowerShell (via the Service Fabric SDK and PowerShell module). There are no examples or guidance for Linux/macOS users, such as using Bash, CLI, or REST API equivalents. The focus on PowerShell and lack of Linux tooling or examples creates friction for non-Windows users.
Recommendations
  • Add examples for using the Fault Analysis Service via Azure CLI, Bash, or REST API to support Linux/macOS users.
  • Clarify whether the PowerShell instructions are Windows-only, and provide alternative instructions for Linux/macOS environments if available.
  • Indicate platform requirements for the Service Fabric SDK and Fault Analysis Service usage, so users know what is supported on their OS.
  • If certain features are Windows-only, explicitly state this to avoid confusion.
GitHub Create Pull Request
Service Fabric Configure the upgrade of a Service Fabric application ...abric/service-fabric-visualstudio-configure-upgrade.md
Medium Priority View Details →
Scanned: 2026-02-03 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 is heavily focused on Windows tooling, specifically Visual Studio and PowerShell, for upgrading Service Fabric applications. All examples and instructions reference Windows-centric tools and workflows, with no mention of Linux/macOS alternatives or cross-platform CLI options. This creates friction for users on non-Windows platforms, as they are not provided with guidance or examples relevant to their environments.
Recommendations
  • Add instructions and examples for upgrading Service Fabric applications using cross-platform tools such as Azure CLI or Service Fabric CLI (sfctl), where possible.
  • Clarify which steps are Windows-only and provide alternative workflows for Linux/macOS users, especially for manual upgrades.
  • Include Linux/macOS shell examples (e.g., Bash) alongside PowerShell examples for hash table input formats and manifest editing.
  • Explicitly state platform requirements and limitations at the beginning of the document, so non-Windows users can quickly assess applicability.
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-03 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation is heavily oriented toward Windows and Visual Studio workflows. All examples and instructions reference Visual Studio features (Build/Rebuild/F5/Ctrl+F5/Publish), and PowerShell is mentioned as the only CLI example for service creation. There is no mention of Linux/macOS tooling, nor are cross-platform alternatives (such as Azure CLI, SFCTL, or VS Code) discussed. This creates friction for Linux/macOS users who may use Service Fabric in non-Windows environments.
Recommendations
  • Add explicit notes clarifying that StartupServices.xml is only supported for Visual Studio deployments on Windows.
  • Provide alternative instructions or links for Linux/macOS users, such as using ARM templates, Azure CLI, or SFCTL for service deployment and configuration.
  • Mention that the Visual Studio workflow is Windows-only and suggest cross-platform development environments (e.g., VS Code) for non-Windows users, with guidance on how to manage service configuration in those contexts.
  • Include examples of deploying Service Fabric applications using non-Windows tools where possible.
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-02-03 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation consistently provides only PowerShell-based deployment examples and command-line instructions, with no mention of Azure CLI, Bash, or Linux/macOS workflows. Windows tools and patterns (e.g., RDP, Windows-style paths, PowerShell prompts) are used exclusively and presented first, making it less accessible for Linux/macOS users.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all deployment steps.
  • Include instructions for accessing VMs using SSH (for Linux/macOS) in addition to RDP.
  • Use platform-neutral file paths and prompts in examples, or provide both Windows and Linux/macOS variants.
  • Explicitly state that the templates and procedures are cross-platform, and clarify any platform-specific requirements.
  • Reference Bash or shell scripting alternatives where applicable.
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-03 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 exhibits a moderate Windows bias. PowerShell is the only scripting example shown for programmatic certificate enrollment, and references to Windows-specific mechanisms (such as S-channel, ACLing, and Key Vault VM extension for Windows) are prominent. The Key Vault VM extension is described primarily in its Windows context, and the linking feature is explicitly stated as 'Only Windows.' Linux equivalents (such as Linux VM extensions, CLI, or bash scripting) are not mentioned, and Windows-centric terminology and examples appear first or exclusively.
Recommendations
  • Provide Linux/macOS equivalents for scripting and automation, such as Azure CLI or bash examples for certificate enrollment and management.
  • Reference and link to the Key Vault VM extension for Linux documentation, and clarify differences in behavior or configuration.
  • Discuss certificate provisioning and ACLing in the context of Linux nodes (e.g., file permissions, certificate stores), especially for clusters that may run on Linux VMSS.
  • Where Windows-specific features (like S-channel or CERT_RENEWAL_PROP_ID) are discussed, explicitly note their absence or alternatives on Linux.
  • Balance example order so that Linux/macOS approaches are presented alongside or before Windows-specific ones where applicable.
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-03 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias by prioritizing Azure PowerShell examples and references in the 'Best practices' section, listing PowerShell before Azure CLI, and omitting explicit Linux/macOS command examples for cluster management tasks. While ARM templates, Bicep, and Azure CLI are mentioned, actionable examples and links are PowerShell-centric, which may create friction for Linux/macOS users.
Recommendations
  • Provide explicit Azure CLI examples and links for all management tasks currently shown with PowerShell (e.g., deleting NodeType, restarting/reimaging scale sets).
  • Ensure that CLI commands are shown alongside PowerShell commands in all relevant sections.
  • Clarify that Azure CLI is cross-platform and provide usage notes for Linux/macOS users.
  • Consider reordering examples so that CLI and PowerShell are presented equally, or CLI is shown first for cross-platform parity.
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-03 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation page for RunToCompletion semantics in Azure Service Fabric demonstrates a notable Windows bias. All code examples use Windows containers (nanoserver:1809) and Windows command syntax (cmd, set, exit, etc.), with explicit references to Windows container compatibility. Querying deployment status is shown only via PowerShell and C# APIs, both Windows-centric tools. There are no Linux container examples, nor any mention of Linux shell commands or querying tools. The documentation does not clarify whether RunToCompletion semantics are supported for Linux containers, nor does it provide guidance for Linux users.
Recommendations
  • Add equivalent examples using Linux containers (e.g., Ubuntu, Alpine) and Linux shell commands (bash, echo, exit, etc.) to demonstrate RunToCompletion semantics for non-Windows environments.
  • Clarify whether RunToCompletion semantics are supported for Linux containers and guest executables, and note any platform limitations.
  • Provide instructions for querying deployment status using cross-platform tools (e.g., Azure CLI, REST API) or Linux-native equivalents.
  • Reorder examples or provide parallel Windows and Linux sections to avoid Windows-first presentation.
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-03 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 on X.509 Certificate-based Authentication in Service Fabric clusters exhibits moderate Windows bias. Windows terminology and tools (e.g., certificate stores like LocalMachine\My, Win32 CryptoAPI, Windows event logs, CAPI2 logging) are referenced first and in detail, while Linux equivalents are mentioned briefly or parenthetically. Troubleshooting and configuration examples focus on Windows paths and APIs, with limited guidance for Linux users. There are no explicit Linux/macOS command-line examples or troubleshooting steps.
Recommendations
  • Provide Linux/macOS-specific examples for certificate management (e.g., using OpenSSL, Linux file paths, and certificate stores).
  • Expand troubleshooting guidance to include Linux/macOS log locations and diagnostic tools.
  • Clarify how Service Fabric certificate presentation and validation works on Linux, including differences in certificate storage and access.
  • When referencing Windows-specific APIs or tools, offer Linux/macOS alternatives or note platform differences.
  • Include explicit Linux/macOS configuration snippets and step-by-step instructions where relevant.
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-03 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides a PowerShell-only example for bypassing Infrastructure Service throttling, with no equivalent CLI or Linux/macOS instructions. It references Service Fabric Explorer, which is cross-platform, but omits Linux-native command-line options. The overall guidance assumes familiarity with Windows tooling.
Recommendations
  • Provide equivalent Azure CLI or REST API examples for managing Infrastructure Service operations, especially for bypassing throttling.
  • Clarify whether the PowerShell command is required or if alternatives exist for Linux/macOS users.
  • Explicitly mention cross-platform management options and tools where available.
  • Add a note about platform requirements for the PowerShell command, and link to Linux/macOS-compatible instructions if possible.
GitHub Create Pull Request
Service Fabric Initializer CodePackages in Service Fabric ...in/articles/service-fabric/initializer-codepackages.md
Medium Priority View Details →
Scanned: 2026-02-03 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page for Initializer CodePackages in Service Fabric presents only Windows container examples, using Windows-specific images, file paths, and commands (cmd, C:\ paths, type, ping). There is no mention of Linux container equivalents, nor are Linux file paths, shell commands, or images referenced. The example and guidance are exclusively Windows-focused, which creates friction for Linux users seeking parity.
Recommendations
  • Add a parallel example using Linux containers (e.g., mcr.microsoft.com/ubuntu or other Linux images), with Linux shell commands (bash/sh), file paths (/workspace/log.txt), and appropriate volume mounts.
  • Clarify whether Initializer CodePackages are supported for Linux containers in Service Fabric, and if so, provide guidance and examples.
  • If there are limitations or differences for Linux containers, explicitly document them to help users understand platform-specific behavior.
  • Present examples for both Windows and Linux containers, or clearly indicate platform scope at the beginning of the article.
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-03 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 PowerShell cmdlets (e.g., Remove-AzResource, AzSF PowerShell cmdlets) for managing Service Fabric resources, with no mention of equivalent Bash/CLI commands or Linux/macOS workflows. While az resource is referenced, PowerShell examples and terminology are given first and most frequently, which may create friction for Linux/macOS users who typically use Bash and the Azure CLI.
Recommendations
  • Provide Azure CLI (az) command examples alongside PowerShell cmdlets for all operations, especially for resource deletion, creation, and scaling.
  • Clarify that az CLI commands work cross-platform and are recommended for Linux/macOS users.
  • Reorder examples to present CLI and PowerShell options equally, or group them by platform.
  • Add notes or links for Linux/macOS users on how to perform these operations without PowerShell.
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-03 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation covers both Windows and Linux Service Fabric clusters, but there is a tendency to mention Windows tools and patterns first, such as Event Log/Event Viewer, ETW, and Diagnostics Agent. Some examples and tutorials are Windows/.NET-focused, and Linux equivalents are referenced but not always given equal detail or example coverage. Linux-specific configuration is sometimes only linked, not described inline. PowerShell is mentioned as an automation option, but Linux CLI or scripting alternatives are not highlighted.
Recommendations
  • Provide Linux-specific examples and walkthroughs alongside Windows ones, especially for cluster monitoring and diagnostics setup.
  • When referencing tools (e.g., Event Viewer, ETW), also mention and briefly describe Linux equivalents (e.g., LTTng, Syslog) in the same section.
  • Include sample commands or scripts for Linux environments (e.g., Bash, CLI) where PowerShell is referenced.
  • Ensure that tutorials and code samples for application monitoring include Linux/.NET Core scenarios, not just .NET Framework/Windows.
  • Clarify in each section whether the guidance applies to both Windows and Linux, and link to Linux-specific 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-03 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 in its description of Service Fabric application and service manifests, focusing on XML configuration and concepts. However, there is a notable Windows bias in the tooling recommendations: the warning section suggests using Visual Studio on Windows and references the ServiceFabricServiceModel.xsd file path in 'C:\Program Files\Microsoft SDKs\Service Fabric\schemas', which is a Windows-specific location. Additionally, PowerShell is mentioned as a way to create service instances before any Linux alternatives, and there are no explicit Linux/macOS tooling or workflow examples provided.
Recommendations
  • Add equivalent instructions for Linux/macOS users, such as how to validate manifest XML schemas using cross-platform editors (e.g., VS Code, JetBrains Rider) and where to find the ServiceFabricServiceModel.xsd file on non-Windows systems.
  • Mention cross-platform Service Fabric CLI (sfctl) or Azure CLI commands for creating service instances, alongside or before PowerShell.
  • Where file paths are referenced, provide both Windows and Linux/macOS examples.
  • Explicitly state that the manifest authoring and deployment process is supported on Linux/macOS, and link to relevant cross-platform tooling documentation.
GitHub Create Pull Request
Service Fabric Application lifecycle in Service Fabric ...service-fabric/service-fabric-application-lifecycle.md
Medium Priority View Details →
Scanned: 2026-02-03 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 demonstrates a notable Windows bias. PowerShell cmdlets are referenced extensively and often listed before or alongside REST and .NET API methods, with no mention of Linux-native CLI equivalents (such as sfctl or Azure CLI) in the main lifecycle sections. The workflow examples and automation guidance rely heavily on PowerShell, which is primarily a Windows tool, and there is little to no explicit guidance for Linux/macOS users, despite Service Fabric supporting cross-platform clusters and management.
Recommendations
  • Include Linux/macOS-friendly command-line examples using sfctl and Azure CLI in all lifecycle phases (deploy, upgrade, remove, etc.), not just in the introductory links.
  • Where PowerShell cmdlets are mentioned, provide equivalent sfctl or Azure CLI commands side-by-side.
  • Add explicit notes or sections for Linux/macOS users, clarifying any differences or limitations in tooling or workflow.
  • Ensure automation examples (such as cleanup policies) are shown using cross-platform tools/scripts, not just PowerShell.
  • Review and update links to point to cross-platform documentation where available.
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-03 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page is generally platform-neutral in its discussion of data serialization and rolling upgrades in Azure Service Fabric. However, in the 'Next steps' section, upgrade tutorials are presented for Visual Studio and PowerShell, both of which are primarily Windows-centric tools. No Linux/macOS equivalents (such as CLI or cross-platform IDEs) are mentioned or linked, and PowerShell is highlighted before any Linux-friendly options.
Recommendations
  • Add links or references to upgrading Service Fabric applications using cross-platform tools such as Azure CLI or Service Fabric CLI (sfctl), which are available on Linux/macOS.
  • Include examples or tutorials for application upgrades using non-Windows environments, or clarify if certain upgrade paths are Windows-only.
  • Mention cross-platform IDEs (such as VS Code) if relevant for application upgrade workflows.
GitHub Create Pull Request
← Previous Page 78 of 99 Next →