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 676-700 of 2475 flagged pages
Service Fabric Scalability of Service Fabric services .../service-fabric/service-fabric-concepts-scalability.md
Medium Priority View Details →
Scanned: 2026-03-01 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides code examples and administrative patterns primarily using PowerShell and C#, both of which are strongly associated with Windows environments. There are no equivalent Linux CLI or bash examples, and PowerShell commands are referenced as the main administrative method. The section on platform differences does mention Linux, but only in the context of logging implementation, not in operational examples. This creates friction for Linux users who may not have access to PowerShell or prefer bash/CLI tools.
Recommendations
  • Add equivalent Linux CLI/bash examples for administrative actions, such as scaling services and creating/removing instances.
  • Reference Service Fabric REST APIs or cross-platform tools where possible, rather than only PowerShell.
  • Clarify which PowerShell commands are available on Linux (if any), or provide guidance for Linux users.
  • Ensure Linux operational patterns are mentioned alongside Windows/PowerShell patterns, not only in the platform differences section.
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-01 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation provides a broad overview of Azure Service Fabric, which is a cross-platform technology supporting both Windows and Linux. However, there are multiple instances where Windows concepts, tools, and examples are mentioned first or exclusively, such as references to Windows services (FabricHost.exe), PowerShell cmdlets, and standalone cluster creation only for Windows. Linux equivalents are sometimes mentioned later or omitted, and some tooling (e.g., PowerShell) is highlighted without clear Linux alternatives.
Recommendations
  • Ensure Linux-specific examples and tools (such as Bash, Linux CLI, or sfctl) are presented alongside or before Windows/PowerShell examples.
  • Clarify when features or instructions are Windows-only, and provide Linux alternatives or links where available.
  • Expand documentation on Linux cluster creation and management, or clearly state limitations and roadmap for Linux support.
  • Where possible, use cross-platform terminology and avoid defaulting to Windows-specific concepts (e.g., 'auto-start Windows service') unless necessary.
  • Highlight Linux support for Service Fabric in relevant sections, including programming models, cluster management, and health monitoring.
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-01 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, ApplicationManifest.xml in Visual Studio) are mentioned before Linux alternatives, and Linux-specific limitations are noted without offering Linux-centric workflows or examples. There is no guidance for Linux users on how to set DNS names or manage Service Fabric clusters using Linux-native tools.
Recommendations
  • Add examples for setting DNS names using Linux-native tools, such as Azure CLI or Bash scripts.
  • Include instructions for editing ARM templates and deploying services from Linux environments.
  • Provide guidance for managing Service Fabric clusters and services on Linux, including containerized workflows.
  • Mention Linux-friendly editors and approaches (e.g., VS Code, nano, vim) for editing ApplicationManifest.xml.
  • Clarify any differences in workflows between Windows and Linux, and ensure Linux users have a clear path to accomplish all documented tasks.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Docker Compose Deployment Preview ...ticles/service-fabric/service-fabric-docker-compose.md
Medium Priority View Details →
Scanned: 2026-03-01 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both PowerShell and Service Fabric CLI (sfctl) examples for deploying Docker Compose files to Azure Service Fabric. However, PowerShell commands are presented first and in greater detail, which may signal a Windows-first bias. The CLI examples are included and are cross-platform, but the prominence and depth of PowerShell coverage may create friction for Linux/macOS users.
Recommendations
  • Present CLI (sfctl) examples before PowerShell, or at least give them equal prominence.
  • Explicitly note that sfctl is cross-platform and preferred for Linux/macOS users.
  • Add clarifying statements about platform compatibility for each tool.
  • Ensure that all critical operations (deploy, status, upgrade, rollback, etc.) are covered equally for both PowerShell and CLI.
  • Consider adding a table or section comparing PowerShell and CLI usage, highlighting cross-platform options.
GitHub Create Pull Request
Service Fabric Azure Service Fabric hosting activation and deactivation life cycle ...les/service-fabric/service-fabric-hosting-lifecycle.md
Medium Priority View Details →
Scanned: 2026-03-01 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page on Azure Service Fabric hosting activation and deactivation life cycle shows a moderate Windows/PowerShell bias. While the core concepts are platform-agnostic, the only explicit tooling reference for deployment/removal is PowerShell, and the 'Next steps' section links only to PowerShell-based workflows. There are no Linux/bash equivalents or cross-platform CLI examples provided, and the only advanced example for downloading ServicePackages in advance links to a PowerShell cmdlet. This may cause friction for Linux/macOS users.
Recommendations
  • Add Azure CLI or Bash examples for deploying and removing applications, alongside or in place of PowerShell examples.
  • Where possible, link to cross-platform documentation or explicitly note Linux/macOS workflows.
  • If certain operations are only possible in PowerShell, clearly state this and provide Linux alternatives or workarounds if available.
  • Include references to Linux tools or scripts for managing Service Fabric clusters, especially for common tasks like package deployment.
GitHub Create Pull Request
Service Fabric Reliable services app manifest examples ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-manifest-example-reliable-services-app.md
Medium Priority View Details →
Scanned: 2026-03-01 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page provides Service Fabric manifest examples and references Windows-specific concepts and tools, such as running scripts via Setup.bat, using EXE files, and referencing Windows user accounts (Administrators, NetworkService). Windows terminology and patterns (e.g., .bat files, EXE hosts, PowerShell module mention) are used throughout, with no explicit Linux equivalents or guidance. However, the content is not exclusively Windows-only, and Service Fabric supports Linux clusters, so Linux users may experience friction but can adapt the examples.
Recommendations
  • Add Linux-specific examples, such as using shell scripts (.sh) for SetupEntryPoint and EntryPoint, and referencing Linux user/group concepts.
  • Clarify which manifest settings and patterns are cross-platform and which are Windows-only.
  • Mention Linux deployment tools (e.g., Azure CLI, Bash) alongside PowerShell, and provide links to Linux Service Fabric documentation.
  • Where EXE or .bat files are referenced, note that Linux services should use ELF binaries and shell scripts.
  • Explicitly state any platform-specific limitations or requirements for Service Fabric manifest elements.
GitHub Create Pull Request
Service Fabric Add custom Service Fabric health reports ...rticles/service-fabric/service-fabric-report-health.md
Medium Priority View Details →
Scanned: 2026-03-01 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed examples for health reporting in Service Fabric using PowerShell, with explicit Windows paths and commands. PowerShell is presented as a primary CLI method, but there are no equivalent Linux/bash examples or references to cross-platform CLI tools. The REST API and .NET API are mentioned, but CLI guidance is Windows-centric.
Recommendations
  • Add examples using Azure CLI or Service Fabric CLI (sfctl), which are cross-platform and supported on Linux/macOS.
  • Clarify whether PowerShell examples are usable on PowerShell Core (pwsh) on Linux/macOS, or provide bash equivalents.
  • Explicitly mention cross-platform tooling and provide sample commands for Linux/macOS environments.
  • Reorder sections so that REST and cross-platform CLI methods are presented before or alongside PowerShell.
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-03-01 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 specifying Service Fabric service endpoints, with XML manifest examples that are cross-platform. However, there is a notable bias in deployment instructions and tooling: the only concrete example of deploying an application uses the Windows PowerShell cmdlet New-ServiceFabricApplication, with a Windows-style path prompt (PS C:\>). There is no equivalent example for Linux (e.g., using sfctl or Azure CLI), and the only mention of Linux is a brief note about the certificate store path. Windows tools and patterns are presented first and exclusively in deployment scenarios.
Recommendations
  • Add Linux/macOS deployment examples using sfctl or Azure CLI alongside the PowerShell example.
  • When showing command-line examples, provide both Windows and Linux/macOS equivalents, or note when a tool is Windows-only.
  • Clarify in the text that Service Fabric supports both Windows and Linux clusters, and link to cross-platform deployment guides.
  • Consider reordering or grouping examples so that Windows and Linux approaches are presented with parity.
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-03-01 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 build/publish actions (F5/Ctrl+F5/Publish) and GUI interactions. There are no examples or guidance for Linux/macOS users or CLI-based workflows, and PowerShell is mentioned as the alternative for service creation, with no Linux equivalent provided.
Recommendations
  • Add explicit guidance for Linux/macOS users, including how to manage StartupServices.xml and ApplicationManifest.xml outside Visual Studio.
  • Provide CLI-based examples (e.g., using Azure CLI, Bash, or cross-platform tools) for deploying Service Fabric applications.
  • Clarify which features are Visual Studio/Windows-only and offer alternatives or workarounds for Linux/macOS environments.
  • Mention any limitations or unsupported scenarios for Linux/macOS users up front.
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-01 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation provides thorough coverage of both Kestrel (cross-platform) and HTTP.sys (Windows-only) web servers for ASP.NET Core integration with Azure Service Fabric Reliable Services. However, Windows-specific tools and patterns (such as HTTP.sys, Windows HTTP Server API, netsh, and ServiceManifest.xml endpoint registration) are discussed in detail and often before their Linux equivalents. The HTTP.sys section is extensive, despite being Windows-only, and references Windows tools like netsh and kernel drivers. Kestrel (the cross-platform option) is covered well, but Windows-specific mechanisms and terminology (e.g., endpoint registration, port sharing, kernel drivers) are prominent and discussed first in several sections. There are no Linux/macOS-specific troubleshooting tips, environment setup instructions, or explicit parity notes. PowerShell is not directly referenced, but Windows tools are.
Recommendations
  • Add explicit notes or sections clarifying Linux/macOS support and limitations for Service Fabric Reliable Services and ASP.NET Core integration.
  • Provide Linux/macOS-specific troubleshooting tips, environment setup instructions, and example workflows (e.g., how to configure ServiceManifest.xml endpoints, firewall rules, and port assignment on Linux).
  • Where Windows tools (like netsh or HTTP.sys) are mentioned, offer Linux alternatives or clarify that these steps are not required for Kestrel on Linux/macOS.
  • Ensure Kestrel examples are shown first or equally with HTTP.sys, and highlight its cross-platform nature.
  • Add links to Linux/macOS documentation for Service Fabric and ASP.NET Core hosting where relevant.
GitHub Create Pull Request
Service Fabric Replica soft delete for enhanced data protection in Service Fabric ...s/service-fabric/service-fabric-replica-soft-delete.md
Medium Priority View Details →
Scanned: 2026-03-01 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 'Replica soft delete for enhanced data protection in Service Fabric' demonstrates notable Windows bias. All command-line/API examples reference PowerShell cmdlets (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica), which are Windows-centric tools. There is no mention of Linux equivalents, nor are examples provided for Linux/macOS users (such as using Service Fabric CLI, REST APIs, or FabricClient in .NET Core). Windows tools and patterns are presented exclusively and first, creating friction for non-Windows users.
Recommendations
  • Add examples using Service Fabric CLI (sfctl) for Linux/macOS users, if supported.
  • Document REST API endpoints or FabricClient usage in .NET Core for cross-platform parity.
  • Clarify whether the PowerShell cmdlets are available on Linux via PowerShell Core, or provide alternative instructions.
  • Explicitly state any limitations or differences for Linux clusters, if applicable.
  • Where possible, show both Windows and Linux/macOS workflows side-by-side.
GitHub Create Pull Request
Service Fabric Standalone Service Fabric clusters overview ...-fabric/service-fabric-standalone-clusters-overview.md
Medium Priority View Details →
Scanned: 2026-03-01 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
Although the page introduction claims Service Fabric clusters run on both Windows Server and Linux, the actual content and supported OS list indicate that standalone clusters are currently Windows-only. Security sections reference Windows authentication and Windows-specific features, and there are no Linux-specific examples or guidance. The documentation gives Windows details first and omits Linux parity.
Recommendations
  • Clarify in the introduction that standalone clusters are currently Windows-only, and Linux support is not yet available.
  • Remove or update statements suggesting Linux parity unless Linux support is imminent.
  • If Linux support is planned, provide equivalent Linux examples, security guidance, and supported OS lists.
  • Explicitly state that all instructions and examples are for Windows environments to avoid confusion.
GitHub Create Pull Request
Service Fabric Fault Analysis Service overview .../service-fabric/service-fabric-testability-overview.md
Medium Priority View Details →
Scanned: 2026-03-01 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page provides examples and instructions for using the Fault Analysis Service primarily via C# and PowerShell, with explicit mention of the Service Fabric SDK and PowerShell module installation. There are no Linux/macOS CLI or scripting examples (such as Bash, Azure CLI, or REST API usage), nor is there guidance for Linux-based Service Fabric clusters. The focus on PowerShell and Windows tools creates friction for Linux/macOS users.
Recommendations
  • Add examples for using the Fault Analysis Service via Azure CLI, Bash scripts, or REST API, which are cross-platform.
  • Clarify whether the Fault Analysis Service is available and supported on Linux-based Service Fabric clusters.
  • Provide installation and usage instructions for Linux/macOS environments, including any required SDKs or tools.
  • Mention alternative scripting options for non-Windows users, such as Python or Bash.
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-28 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 provides RunToCompletion semantics for Service Fabric, but all code examples, container images, and tooling references are Windows-centric. The examples exclusively use Windows containers (nanoserver), Windows-specific commands (cmd, echo, ping, set), and PowerShell for querying deployment status, with no mention of Linux container equivalents or Linux/macOS tooling. This creates friction for Linux users and does not demonstrate Linux parity.
Recommendations
  • Add equivalent Linux container examples (e.g., using Ubuntu or Alpine images) alongside Windows examples.
  • Show Linux shell commands (bash, sh) for CodePackage entry points and exit scenarios.
  • Include instructions for querying deployment status using Linux tools (e.g., Azure CLI, REST API, or Service Fabric CLI) instead of only PowerShell.
  • Clarify any platform limitations (if RunToCompletion semantics are Windows-only, state this explicitly; if not, show cross-platform usage).
  • Present examples for both Windows and Linux containers, or note differences in supported features.
GitHub Create Pull Request
Service Fabric Deploy and upgrade with Azure Resource Manager ...vice-fabric/service-fabric-application-arm-resource.md
Medium Priority View Details →
Scanned: 2026-02-28 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides PowerShell examples for application removal and references PowerShell as a deployment tool before mentioning CLI. There are no explicit Linux/macOS examples or references to Linux-native tools, and PowerShell is presented as the primary scripting interface for resource management tasks.
Recommendations
  • Add equivalent Azure CLI examples for application removal and management, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Mention Service Fabric CLI (sfctl) and Azure CLI alongside PowerShell when describing deployment and management workflows.
  • Provide guidance or links for Linux/macOS users, clarifying how to perform tasks without PowerShell.
  • Ensure that REST API usage examples are platform-neutral and include sample curl commands for Linux/macOS users.
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-28 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 the Service Fabric application lifecycle consistently references PowerShell cmdlets and Windows-centric tooling (e.g., PowerShell commands, .NET APIs) for operational tasks such as deployment, upgrade, removal, and cleanup. While REST API endpoints are mentioned, there is a lack of explicit Linux/macOS CLI examples (such as Azure CLI or sfctl) and Linux-native workflows. PowerShell is presented as the primary scripting interface, and Windows tools are often listed before REST APIs, with no clear Linux parity or guidance.
Recommendations
  • Add explicit examples using Azure CLI and sfctl for each operational task (deploy, upgrade, remove, cleanup), especially for Linux/macOS users.
  • Where PowerShell cmdlets are referenced, provide equivalent sfctl or Azure CLI commands alongside.
  • Clarify which tools are cross-platform and which are Windows-only, and recommend Linux-friendly alternatives where possible.
  • Reorder examples so that cross-platform tools (REST API, sfctl, Azure CLI) are presented before or alongside Windows-specific tools.
  • Include notes or links to Linux/macOS guidance for Service Fabric operations.
GitHub Create Pull Request
Service Fabric Azure Service Fabric container application manifest examples ...abric/service-fabric-manifest-example-container-app.md
Medium Priority View Details →
Scanned: 2026-02-28 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows Server 2016 container samples as the basis for the examples, mentioning Windows-specific tools (e.g., 'winver' for OS build detection), and using Windows file paths (e.g., 'c:\VolumeTest\Data'). Linux equivalents, such as Linux container samples, Linux file paths, or Linux OS build detection methods, are not provided. While some sections mention Linux (e.g., certificate handling), the overall examples and guidance are Windows-centric.
Recommendations
  • Include Linux-based container manifest examples or reference Linux container samples alongside Windows samples.
  • Provide Linux file path examples (e.g., '/mnt/VolumeTest/Data') in volume bindings.
  • Mention Linux methods for detecting OS build/version (e.g., 'cat /etc/os-release' or 'uname -r') in the ImageOverrides section.
  • Clarify which features are cross-platform and which are Windows-only, and provide parity guidance where possible.
  • Add links to Linux-specific Service Fabric container documentation or samples.
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-28 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-based deployment example and refers to Windows file paths and certificate stores before mentioning Linux equivalents. The only explicit deployment command is shown in PowerShell with a Windows path, and the Service Fabric SDK schema path is given in Windows format. The Linux certificate store location is mentioned, but only after the Windows example. There are no CLI or bash examples for Linux/macOS users.
Recommendations
  • Provide equivalent deployment examples using Azure CLI or bash scripts for Linux/macOS users alongside PowerShell examples.
  • Mention Linux file paths and certificate store locations alongside Windows paths, not after.
  • Clarify which steps or features are cross-platform and which are Windows-specific, if any.
  • Where possible, use platform-agnostic language or provide parallel instructions for both environments.
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-28 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page provides a comprehensive overview of certificate management in Azure Service Fabric clusters, but exhibits Windows bias in several ways. PowerShell is the only scripting example provided for certificate enrollment, and references to Windows-specific tools and concepts (such as certificate stores, ACLing, S-channel, and Key Vault VM extension for Windows) are frequent. Windows terminology and mechanisms are mentioned first or exclusively, with little to no guidance for Linux users or parity in examples. While Service Fabric supports Linux clusters, the documentation does not address Linux-specific certificate provisioning, scripting, or operational patterns.
Recommendations
  • Add equivalent Bash/CLI scripting examples for certificate enrollment and management, especially for Key Vault operations.
  • Include guidance or examples for certificate provisioning and management on Linux Service Fabric clusters, such as using Linux VM extensions or manual certificate installation.
  • Clarify which mechanisms and tools are Windows-only and provide Linux alternatives where possible (e.g., certificate store locations, ACLing, VM extensions).
  • Mention Linux-specific considerations for certificate rotation, cleanup, and monitoring.
  • Link to Linux-focused Service Fabric documentation or provide a section summarizing Linux differences.
GitHub Create Pull Request
Service Fabric Custom Image .../articles/service-fabric/how-to-deploy-custom-image.md
Medium Priority View Details →
Scanned: 2026-02-28 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page primarily discusses deploying custom Windows images to Service Fabric Managed Clusters, with PowerShell examples and terminology focused on Windows. While there are references to Linux custom images and Azure CLI, the main example and workflow are Windows-centric, and the PowerShell command is given without a Linux equivalent.
Recommendations
  • Provide equivalent Linux/bash examples for role assignment (e.g., using Azure CLI instead of PowerShell).
  • Clarify when instructions are applicable to both Windows and Linux node types, or explicitly state if only Windows is supported.
  • Add ARM template examples for Linux images, or note any limitations for Linux custom images.
  • Ensure that references to Linux documentation are as prominent as Windows documentation.
GitHub Create Pull Request
Service Fabric Migrate an Azure Service Fabric cluster to availability zone support ...ce-fabric/migrate-service-fabric-availability-zones.md
Medium Priority View Details →
Scanned: 2026-02-28 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides extensive PowerShell examples and references to Windows-specific tools (e.g., Service Fabric PowerShell cmdlets, AzureRm modules) for migration steps, especially in the 'Basic SKU load balancer and IP resources' scenario. There are no equivalent CLI or Linux/macOS instructions, and PowerShell is used exclusively for critical migration tasks. While ARM templates are platform-neutral, the operational steps are Windows-centric.
Recommendations
  • Add Azure CLI examples for all migration steps, especially for resource deployment, node disabling/removal, and DNS updates.
  • Document how to perform Service Fabric cluster operations (e.g., node disable/remove) using cross-platform tools or REST APIs.
  • Explicitly mention that PowerShell steps can be performed with Azure CLI or Bash on Linux/macOS, and provide sample commands.
  • Clarify any Windows-only requirements (e.g., if Service Fabric cmdlets are required, note their OS support and alternatives).
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-28 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page exhibits mild Windows bias. The only explicit tooling recommendation is to use Visual Studio on Windows and reference a local Windows path for the Service Fabric schema file. Additionally, the PowerShell module is mentioned as a way to create service instances, but no equivalent CLI or Linux-native tools are referenced. Windows tooling and patterns are mentioned before any cross-platform alternatives, and Linux/macOS users are not provided with parity guidance.
Recommendations
  • Add instructions for validating manifest XML schema using cross-platform editors (e.g., VS Code, JetBrains Rider) and explain how to obtain the schema file on Linux/macOS.
  • Mention Azure CLI or Service Fabric CLI (sfctl) as alternatives to PowerShell for creating service instances, with example commands.
  • Clarify how Linux/macOS users can author, validate, and deploy manifests, including any differences in tooling or workflow.
  • Ensure that references to Windows-specific paths/tools are accompanied by Linux/macOS equivalents or notes.
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-28 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 the Azure Portal, ARM templates, and PowerShell. PowerShell is the only CLI example provided, with no mention of Azure CLI or Bash equivalents. PowerShell is a Windows-centric tool, and its exclusive use creates friction for Linux/macOS users. Additionally, PowerShell examples are given equal or greater prominence than ARM templates, and no Linux-native tooling is referenced.
Recommendations
  • Add Azure CLI examples for all tasks currently demonstrated with PowerShell, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that PowerShell examples are Windows-centric and provide guidance for Linux/macOS users (e.g., recommend Azure CLI or ARM templates).
  • Consider showing Azure CLI examples before or alongside PowerShell to avoid 'windows_first' bias.
  • Where possible, clarify that ARM templates can be deployed from any OS using Azure CLI or portal.
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-28 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 Windows-centric tool) without mentioning Linux/macOS alternatives. No Linux CLI or cross-platform commands are given, and Windows patterns are presented first and exclusively.
Recommendations
  • Add equivalent Linux/macOS command-line examples (e.g., using Azure CLI, REST API, or Service Fabric CLI if available).
  • Clarify whether the PowerShell command is required or if cross-platform tools can be used.
  • Mention any cross-platform management tools or interfaces for Service Fabric clusters.
  • If Service Fabric Explorer is Windows-only, note this and suggest alternatives for Linux/macOS 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-02-28 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides best practice examples using Azure PowerShell modules and references PowerShell-based tools before mentioning cross-platform alternatives. While Azure CLI and ARM/Bicep are listed, PowerShell is emphasized in guidance and example links, and no explicit Linux/macOS shell examples are provided. The 'sfctl' tool (which is cross-platform) is mentioned only in a table, not in narrative or examples.
Recommendations
  • Add explicit Azure CLI examples for key operations (e.g., deleting NodeTypes, restarting/reimaging scale sets) alongside PowerShell examples.
  • Mention cross-platform tools (Azure CLI, sfctl) in the narrative best practices section, not just in tables.
  • Clarify that Azure PowerShell is available on Linux/macOS, but also provide Bash/Linux shell usage examples for parity.
  • Ensure that guidance does not imply PowerShell is the preferred or only option for managing Service Fabric clusters.
GitHub Create Pull Request
← Previous Page 28 of 99 Next →