Service Fabric
810
Total Pages
600
Linux-Friendly Pages
210
Pages with Bias
25.9%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
718 issues found
Showing 651-675 of 718 flagged pages
Service Fabric
Add a managed identity to a Service Fabric managed cluster node type
...ed-identity-managed-cluster-virtual-machine-scale-sets.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page is heavily biased towards Windows and PowerShell usage. All command-line examples use PowerShell cmdlets, with no Azure CLI or Bash alternatives provided. The VM image example uses Windows Server exclusively, and there is no mention of Linux-based node types or deployment patterns. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer using Bash/Azure CLI.
Recommendations
- Provide equivalent Azure CLI commands for all PowerShell examples, especially for identity creation, role assignment, and deployment steps.
- Include examples of deploying Service Fabric node types using Linux VM images (e.g., Ubuntu), and clarify any differences or limitations.
- Add notes or sections specifically addressing Linux/macOS users, including setup instructions and troubleshooting relevant to those platforms.
- Present examples for both Windows and Linux in parallel, or at least alternate which is shown first to avoid implicit prioritization.
Create Pull Request
Service Fabric
Describing Azure Service Fabric apps and services
...ic/service-fabric-application-and-service-manifests.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page displays mild Windows bias, primarily in its tooling recommendations and file path references. The only explicit tool suggestion for authoring manifests is to open the ServiceFabricServiceModel.xsd schema in Visual Studio, referencing a Windows file path (C:\Program Files\Microsoft SDKs\Service Fabric\schemas\ServiceFabricServiceModel.xsd). No Linux/macOS equivalent tool or workflow is mentioned. Additionally, the PowerShell module is referenced for service creation, but no Linux CLI alternative is provided or discussed.
Recommendations
- Include instructions or recommendations for editing and validating manifest XML files on Linux/macOS, such as using VS Code, JetBrains Rider, or command-line XML validators.
- Provide Linux/macOS file paths for Service Fabric SDK schema files, if available, or clarify how to obtain them on non-Windows platforms.
- Mention cross-platform Service Fabric CLI (sfctl) commands for service creation and management, alongside or instead of PowerShell.
- Avoid referencing Windows tools (Visual Studio, PowerShell) exclusively; offer parity in examples and tool suggestions.
Service Fabric
Advanced Application Upgrade Topics
...-fabric/service-fabric-application-upgrade-advanced.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily biased towards Windows, with all command-line examples using PowerShell cmdlets and references to Windows-centric tools (Visual Studio, PowerShell). There are no CLI, Bash, or Linux-native examples, nor are cross-platform alternatives mentioned. This creates friction for Linux/macOS users who may use Service Fabric CLI (sfctl) or ARM templates exclusively.
Recommendations
- Add equivalent examples using Service Fabric CLI (sfctl) for all PowerShell cmdlets.
- Explicitly mention cross-platform tools and workflows, such as ARM templates and REST APIs, where applicable.
- Include Linux/macOS-specific instructions for common upgrade scenarios.
- Reorder examples to present cross-platform options first, or side-by-side with Windows/PowerShell examples.
- Clarify which features are available via CLI, REST, or ARM, and note any platform limitations.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits Windows bias by referencing Visual Studio and PowerShell as primary upgrade methods, both of which are Windows-centric tools. There are no explicit Linux/macOS equivalents or examples provided for application upgrades, and the upgrade tutorials listed in 'Next steps' focus on Windows tools first, with no mention of cross-platform CLI alternatives.
Recommendations
- Add explicit instructions and examples for upgrading applications using cross-platform tools such as Azure CLI or Service Fabric CLI (sfctl), which work on Linux/macOS.
- Include links to tutorials or documentation for Linux/macOS users, ensuring parity with Visual Studio and PowerShell guides.
- Reorder 'Next steps' to present cross-platform methods before or alongside Windows-specific tools.
- Clarify which tools are Windows-only and provide alternatives for other platforms.
Service Fabric
Service Fabric application upgrade
...s/service-fabric/service-fabric-application-upgrade.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias. The only code example provided uses PowerShell, a Windows-centric tool, with no equivalent CLI or Linux/macOS instructions. Windows-specific tools (PowerShell, http.sys) are referenced exclusively or before any cross-platform alternatives. The troubleshooting and next steps sections also direct users to Windows/PowerShell/Visual Studio-based tutorials, with no mention of Linux or cross-platform workflows.
Recommendations
- Add equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
- Explicitly mention Linux/macOS support and provide links to relevant documentation for those platforms.
- When referencing Windows-specific tools (e.g., http.sys), clarify the behavior or alternatives on Linux.
- Ensure that upgrade instructions and troubleshooting guides include both Windows and Linux/macOS workflows.
- Reorder examples so that cross-platform tools (CLI) are shown before or alongside Windows/PowerShell examples.
Service Fabric
Create clusters on Windows Server and Linux
...rvice-fabric/service-fabric-azure-clusters-overview.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page describes Service Fabric clusters on both Windows Server and Linux, but the technical details and examples focus exclusively on Windows-specific tools and processes (e.g., FabricHost.exe, Fabric.exe, FabricGateway.exe). There are no Linux-specific equivalents or instructions, nor any mention of Linux service management or process names, which may leave Linux users unclear about how the cluster operates or is managed on their platform.
Recommendations
- Add explicit references to Linux equivalents for Service Fabric processes (e.g., systemd service names, process names, or management commands).
- Include examples or explanations for how cluster nodes are managed and started on Linux (e.g., how the Service Fabric runtime is launched, what services are involved, and how to troubleshoot).
- Where Windows-specific executables are mentioned, provide a parallel description for Linux (e.g., what replaces FabricHost.exe, Fabric.exe, and FabricGateway.exe on Linux).
- Clarify any differences in deployment, management, or troubleshooting between Windows and Linux clusters.
- Consider adding a table or section that compares Windows and Linux cluster node architecture and management.
Service Fabric
Understanding periodic backup configuration
...-fabric-backuprestoreservice-configure-periodic-backup.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily in the backup storage configuration section, where file share examples use Windows UNC paths (\\StorageServer\BackupStore) and reference Integrated Windows Authentication. No Linux or cross-platform file share examples (e.g., NFS, SMB mounting on Linux) are provided, nor are Linux authentication patterns discussed. Windows-specific terminology and patterns are presented first and exclusively, potentially leaving Linux/macOS users without clear guidance for on-premises backup storage configuration.
Recommendations
- Add examples for configuring file share backup storage using Linux-compatible paths and protocols (e.g., NFS, SMB/CIFS mounts).
- Document authentication methods for Linux environments, such as username/password for SMB, Kerberos, or NFS exports.
- Clarify whether Service Fabric supports Linux-based file shares and provide step-by-step instructions for Linux/macOS users.
- Reorder or parallelize examples so that Windows and Linux approaches are presented side-by-side.
- Explicitly mention any platform limitations or differences in backup storage configuration.
Service Fabric
Set up Microsoft Entra ID for client authentication in the Azure portal
...vice-fabric-cluster-creation-setup-azure-ad-via-portal.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides only PowerShell-based examples for connecting to Service Fabric clusters with Microsoft Entra ID, with no mention of Linux/macOS command-line alternatives (e.g., Azure CLI, REST API, or cross-platform SDKs). Troubleshooting and connection instructions are exclusively focused on PowerShell, which is primarily a Windows tool. There is a brief note about Linux limitations, but no Linux-specific guidance or parity in examples.
Recommendations
- Add equivalent Linux/macOS connection instructions using Azure CLI, REST API, or cross-platform SDKs.
- Include troubleshooting steps for Linux users, especially given the known portal viewing issue.
- Clearly indicate which steps are platform-agnostic and which require Windows-specific tools.
- Provide links or references to Service Fabric tools and SDKs available for Linux/macOS.
- If PowerShell is required on Linux, explain how to install and use PowerShell Core on Linux.
Service Fabric
Azure Service Fabric security best practices
...rvice-fabric/service-fabric-best-practices-security.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows-specific tools (PowerShell, Windows Defender, DSC) are mentioned and exemplified before or more prominently than Linux equivalents. Some sections (e.g., Windows Defender, security baselines) are Windows-only, and Windows examples (PowerShell) are presented before Linux (bash/openssl) in encryption workflows. Linux guidance is present but less detailed or secondary in order.
Recommendations
- Present Linux and Windows examples side-by-side or in parallel sections, rather than Windows first.
- Provide equivalent Linux tooling recommendations (e.g., mention Linux antivirus solutions, security baselines) where Windows tools are discussed.
- Clarify when a feature or tool is Windows-only and suggest Linux alternatives or workarounds.
- Expand Linux-specific instructions and examples to match the detail provided for Windows.
- Where possible, use cross-platform commands or scripts (e.g., Azure CLI) as primary examples.
Service Fabric
Create a cluster using certificate common name
...-fabric/service-fabric-create-cluster-using-cert-cn.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page exclusively provides PowerShell commands and Windows file path examples for certificate management and cluster deployment, with no mention of Linux/macOS equivalents or cross-platform tools. All scripting and automation steps assume a Windows environment, creating friction for users on other platforms.
Recommendations
- Provide equivalent Bash/Azure CLI examples for certificate upload and deployment steps.
- Mention cross-platform tools (e.g., Azure CLI, OpenSSL) for certificate handling and template deployment.
- Use platform-neutral file paths in examples, or show both Windows and Linux/macOS paths.
- Explicitly state platform requirements or limitations, and link to Linux/macOS instructions if available.
Service Fabric
Service Fabric Backup and Restore
...ric/service-fabric-reliable-services-backup-restore.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. The only explicit tooling example for testing backup and restore is the PowerShell cmdlet 'Start-ServiceFabricPartitionDataLoss', with no mention of Linux/macOS equivalents or cross-platform CLI alternatives. There are references to .NET APIs and Windows-specific workarounds (e.g., kernel32 APIs for long paths), but no guidance for Linux/macOS users. There are no Linux shell or cross-platform CLI examples for backup/restore operations, and Windows tools are mentioned exclusively.
Recommendations
- Provide equivalent Linux/macOS instructions for testing backup and restore, such as using Azure CLI, Service Fabric CLI (sfctl), or REST APIs.
- Mention and demonstrate cross-platform alternatives to PowerShell cmdlets, e.g., sfctl commands for inducing data loss and restoring partitions.
- Add notes or examples for handling long file paths on Linux/macOS, including relevant system calls or utilities.
- Ensure that tooling and code samples are presented in a platform-neutral way, or provide parallel examples for both Windows and Linux/macOS environments.
Service Fabric
Change FabricTransport settings
...service-fabric-reliable-actors-fabrictransportsettings.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: certificate configuration examples consistently use Windows-centric terminology and values (e.g., 'LocalMachine', 'My', 'WinFabric-Test-SAN1-Alice'), and do not provide equivalent Linux configuration examples. While there is a brief note about PEM-formatted certificates for Linux, all XML examples and parameter values are tailored to Windows certificate stores and naming conventions. There are no Linux-specific configuration samples or guidance for Linux certificate store locations, names, or patterns.
Recommendations
- Add explicit Linux configuration examples, including XML snippets with Linux-appropriate values for certificate store location and name.
- Document the differences in certificate handling between Windows and Linux, such as where certificates should be placed and how to reference them.
- Provide guidance on converting Windows-centric parameters (e.g., 'LocalMachine', 'My') to their Linux equivalents, or clarify which parameters are ignored or required on Linux.
- Include a section or table summarizing platform-specific differences for all relevant settings.
Service Fabric
Common FabricClient exceptions thrown
...service-fabric/service-fabric-errors-and-exceptions.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page focuses exclusively on .NET and Windows-centric exception types and error codes, referencing Windows-specific concepts such as X509 certificate stores and .NET exception classes. There are no examples, notes, or guidance for Linux environments, nor any mention of Linux-specific error handling, certificate management, or cross-platform considerations.
Recommendations
- Include examples or notes on how exceptions and error codes manifest when using FabricClient APIs on Linux environments.
- Document Linux-specific certificate store locations and management patterns, such as differences in X509 store handling.
- Add guidance for troubleshooting and handling exceptions in cross-platform scenarios, including any differences in error codes or behaviors.
- Reference equivalent Linux tools or commands where applicable, and clarify any platform-specific limitations or differences.
Service Fabric
Deploy a Service Fabric cluster using the Azure portal
...es/service-fabric/quickstart-classic-cluster-portal.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively guides users to deploy a Service Fabric cluster using Windows Server 2019 Datacenter as the operating system, with no mention of Linux-based deployment options. All instructions, screenshots, and examples assume a Windows environment, and there are no Linux-specific notes, alternatives, or parity guidance. This presents a strong Windows bias and may exclude or confuse users seeking to deploy Service Fabric clusters on Linux.
Recommendations
- Include instructions and screenshots for deploying Service Fabric clusters using Linux-based virtual machines (e.g., Ubuntu or CentOS).
- Add a section or notes highlighting differences between Windows and Linux deployments, including certificate handling and cluster management.
- Provide parity in examples, such as how to import certificates on Linux systems and access Service Fabric Explorer from Linux clients.
- Explicitly mention Linux support in the prerequisites and operating system selection steps, and offer guidance for users who prefer or require Linux environments.
Service Fabric
Service Fabric cluster security: client roles
...ervice-fabric/service-fabric-cluster-security-roles.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation describes Service Fabric client roles and access control but does not provide any platform-specific examples or tooling references. However, the only mention of cluster creation refers to the Azure portal and cluster manifest file, which are typically associated with Windows-centric workflows. There are no Linux-specific instructions, examples, or references to Linux tools or patterns, and no mention of cross-platform command-line usage (e.g., Bash, CLI, etc.).
Recommendations
- Include explicit examples for both Windows (PowerShell) and Linux (Bash/CLI) when describing how to configure client roles and permissions.
- Reference cross-platform tools such as Azure CLI and provide sample commands for both Windows and Linux environments.
- Clarify whether the cluster manifest file and related configuration steps are identical on Linux clusters, and provide guidance for Linux users if there are differences.
- Add links or sections that address Linux-specific workflows, such as using Service Fabric on Linux, and how access control is managed in those scenarios.
Service Fabric
Overview of Azure and standalone Service Fabric clusters
...icles/service-fabric/service-fabric-deploy-anywhere.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation discusses Service Fabric clusters on both Windows Server and Linux, but it highlights that standalone clusters are not available on Linux and does not provide Linux-specific examples or operational guidance. Windows is implicitly prioritized by mentioning standalone clusters in the context of Windows only, and there is a lack of parity in examples or tooling for Linux users.
Recommendations
- Explicitly state the limitations and alternatives for Linux users regarding standalone clusters.
- Provide Linux-specific operational guidance, examples, and tooling references where possible.
- Ensure that any feature comparison or instructions are presented in a balanced manner, with Linux and Windows options given equal prominence.
- Link to Linux-focused documentation or migration guides for users interested in Service Fabric on Linux.
- Clarify any differences in management, scaling, and diagnostics for Linux clusters, and offer best practices for Linux environments.
Service Fabric
Query for cluster events using the EventStore APIs
...-fabric/service-fabric-diagnostics-eventstore-query.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exhibits a Windows bias by explicitly stating that the EventStore APIs are GA only for Windows clusters running on Azure, with no mention of Linux support or examples. All code and usage examples assume Windows clusters, and there are no Linux-specific instructions, caveats, or parity notes. There are no references to Linux tools, shell commands, or patterns, and the documentation does not clarify the status or usage for Service Fabric clusters running on Linux.
Recommendations
- Clearly state the current support status for Linux clusters, including any limitations or roadmap for EventStore APIs on Linux.
- If Linux support exists or is planned, provide equivalent Linux usage examples, including REST queries and client library usage.
- Include notes or guidance for Linux users, such as differences in endpoint URLs, authentication, or setup steps.
- Add troubleshooting or caveats for Linux clusters, if there are known issues or differences.
- Ensure that future updates to the documentation maintain parity between Windows and Linux, with examples and instructions for both platforms.
Service Fabric
Azure Service Fabric Event Store
...ervice-fabric/service-fabric-diagnostics-eventstore.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exhibits a Windows bias by repeatedly stating that EventStore APIs and UX are only available for Windows clusters running on Azure, with no Linux support yet. All instructions, examples, and enablement steps are written with the assumption of a Windows cluster, and there are no Linux-specific examples, guidance, or parity notes beyond a brief mention that Linux support is planned for the future.
Recommendations
- Explicitly state the current lack of Linux support at the top of the documentation and provide a timeline or roadmap for Linux parity if possible.
- Add a dedicated section outlining the differences between Windows and Linux cluster support for EventStore, including any workarounds or alternative monitoring options for Linux users.
- Once Linux support is available, update all examples and instructions to include both Windows and Linux workflows, configuration snippets, and troubleshooting steps.
- Provide links to Linux-compatible monitoring and diagnostics tools as alternatives until EventStore is available for Linux clusters.
- Regularly update the documentation to reflect progress on Linux support and communicate changes clearly to users.
Service Fabric
Overview of Service Fabric and containers
...s/service-fabric/service-fabric-containers-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides a balanced overview of Service Fabric container support for both Linux and Windows. However, in some sections, Windows-specific scenarios (such as IIS lift-and-shift) are mentioned before Linux examples, and Windows container details are sometimes more elaborated. Still, Linux examples and tutorials are present and linked, and Linux support is clearly described.
Recommendations
- Ensure Linux and Windows examples are presented with equal prominence and detail.
- When listing scenarios or features, alternate the order or group by OS to avoid implicit prioritization.
- Expand Linux-specific scenarios (e.g., Apache/Nginx lift-and-shift) to match the detail given to Windows/IIS.
- Where possible, provide parallel Linux and Windows code snippets or references.
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
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page for Service Fabric application and service manifest examples displays mild Windows bias. Windows-specific concepts (such as running scripts via .bat files, references to NETWORKSERVICE, and local admin accounts) are used throughout the examples. The only script example is a Windows batch file (Setup.bat), and the documentation mentions using the ServiceFabric PowerShell module for service creation. There is no explicit mention of Linux equivalents, such as shell scripts (.sh), Linux user accounts, or Linux-specific deployment notes. However, the manifest XML itself is cross-platform, and the page does not block Linux users from completing the task.
Recommendations
- Add examples or notes for Linux deployments, such as using shell scripts (.sh) in SetupEntryPoint.
- Clarify that user and group principals can be mapped to Linux users/groups and provide guidance for Linux clusters.
- Mention Linux-compatible tools for service creation (e.g., Azure CLI or REST API) alongside PowerShell.
- Include a brief section on cross-platform considerations for Service Fabric manifests.
Service Fabric
Change Azure Service Fabric cluster settings
...rvice-fabric/service-fabric-cluster-fabric-settings.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page provides a comprehensive reference for Service Fabric cluster settings, but exhibits mild Windows bias. Windows-specific terminology and tools (e.g., certificate store names like 'My', NTLM authentication, references to Windows Defender Firewall, and default paths like 'd:\svcfab') are prevalent. Windows concepts (such as certificate store handling and account types) are mentioned before or instead of Linux equivalents. Some settings and guidance reference Windows-only behaviors or tools, and Linux-specific guidance is minimal or absent. While many settings are cross-platform, Linux users may need to infer or adapt instructions, as Linux-specific examples, paths, and terminology are often missing.
Recommendations
- Add explicit Linux equivalents for settings that reference Windows concepts (e.g., certificate stores, account types, NTLM authentication).
- Provide Linux-specific examples, paths, and terminology alongside Windows references.
- Clarify which settings are platform-specific and which are cross-platform, ideally with a table or annotation.
- Include guidance for Linux users where Windows tools or behaviors are mentioned (e.g., how to handle certificates, firewall configuration, or file paths on Linux).
- Ensure Linux settings (such as '/usr/bin/' for external executables, '/var/lib/waagent' for certificates) are given equal prominence and explanation.
Service Fabric
Azure Service Fabric Docker Compose Deployment Preview
...ticles/service-fabric/service-fabric-docker-compose.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both PowerShell and Service Fabric CLI (sfctl) examples for deploying Docker Compose files on Azure Service Fabric. However, PowerShell examples are presented first and in greater detail, which may suggest a Windows-first bias. The CLI examples are included and are cross-platform, but there is no explicit mention of Linux/macOS compatibility or guidance for those environments. The documentation does not exclusively use Windows tools, but the ordering and emphasis favor Windows users.
Recommendations
- Explicitly state that sfctl is cross-platform and suitable for Linux/macOS users.
- Consider presenting CLI examples before PowerShell, or at least side-by-side, to avoid Windows-first ordering.
- Add brief instructions or links for installing sfctl on Linux/macOS.
- Clarify any limitations or differences for Linux/macOS users, if applicable.
Service Fabric
Overview of Azure Service Fabric
...ain/articles/service-fabric/service-fabric-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Minor Windows Tools
Summary
The documentation generally presents Azure Service Fabric as a cross-platform solution, explicitly mentioning both Windows and Linux support throughout. However, there is a subtle 'Windows-first' ordering in some sections, and Windows tools (Visual Studio, PowerShell) are mentioned before Linux equivalents. Linux tooling is referenced, but with less detail and after Windows tools.
Recommendations
- When listing supported platforms or environments, alternate the order (e.g., 'Linux and Windows Server') or mention both together to avoid implicit prioritization.
- Provide equal detail for Linux development tools (e.g., mention Bash, VS Code, or other common Linux workflows alongside Visual Studio/PowerShell).
- Ensure that links to getting started guides for both Windows and Linux are equally prominent.
- Where possible, include examples or references for both .NET and Java SDKs in parallel, not just in separate sections.
Service Fabric
Reliable Collection object serialization
...c-reliable-services-reliable-collections-serialization.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation is generally platform-neutral, focusing on .NET serialization concepts relevant to Azure Service Fabric. However, in the 'Next steps' section, Windows-centric tools (Visual Studio and PowerShell) are listed before any Linux/macOS alternatives, and PowerShell is specifically highlighted without mention of cross-platform CLI options. There are no Linux-specific examples or references to Linux tooling for application upgrades.
Recommendations
- Add examples or references for upgrading applications using cross-platform tools such as Azure CLI or Service Fabric CLI (sfctl), especially for Linux/macOS users.
- Ensure that Linux/macOS-friendly upgrade tutorials are linked alongside Visual Studio and PowerShell guides.
- Explicitly state platform requirements for any tool or process mentioned, and provide alternatives when available.
- Consider including sample code or instructions for running Service Fabric workloads on Linux, if applicable.
Service Fabric
Create an Azure Load Balancer rule for a cluster
...n/articles/service-fabric/create-load-balancer-rule.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for creating Azure Load Balancer rules. However, the PowerShell section is given equal prominence to Azure CLI, despite PowerShell being primarily a Windows tool. There are no Linux/macOS-specific shell examples (e.g., Bash), nor is there mention of Linux-specific considerations. The CLI example is cross-platform, but the inclusion and detailed walkthrough of PowerShell may suggest a Windows bias, especially for users unfamiliar with PowerShell on non-Windows systems.
Recommendations
- Clarify that Azure CLI is fully cross-platform and recommended for Linux/macOS users.
- Consider moving the Azure CLI section before PowerShell, or explicitly state CLI is the preferred method for non-Windows platforms.
- Remove or de-emphasize PowerShell unless there are Windows-specific requirements.
- Add a note for Linux/macOS users highlighting that PowerShell Core is available cross-platform, but Azure CLI is simpler and native.
- Include troubleshooting or environment setup notes for Linux/macOS users if needed.