283
Pages Scanned
93
Pages Flagged
283
Changed Pages
32.9%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:09
Scan Information
Started At: 2026-02-17 00:00:09
Finished At: In Progress
Status: in_progress
Target Repo: Azure Compute
Current Phase: discovery
Files Queued: 283
Files Completed: 283
Problematic Pages
92 issues found
Service Fabric
Initializer CodePackages in Service Fabric
...in/articles/service-fabric/initializer-codepackages.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page for Initializer CodePackages in Service Fabric is heavily focused on Windows containers. All examples use Windows container images (nanoserver), Windows paths (C:\...), and Windows commands (cmd, echo, type, ping). There is no mention of Linux container support, nor are any Linux-based examples or equivalents provided. Windows-specific tools and patterns are referenced exclusively.
Recommendations
- Add examples using Linux container images (e.g., Ubuntu, Alpine) and Linux commands (bash, echo, cat, etc.).
- Clarify whether Initializer CodePackages are supported for Linux containers and, if so, provide Linux-specific guidance.
- Include documentation snippets showing Linux path conventions and volume mounts.
- If the feature is Windows-only, explicitly state this early in the article to avoid confusion.
Create Pull Request
Service Fabric
Azure Service Fabric reverse proxy
...articles/service-fabric/service-fabric-reverseproxy.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation explicitly states that the Service Fabric reverse proxy is not available for Linux clusters, and all examples, explanations, and guidance are implicitly Windows-centric. There are no Linux-specific instructions, examples, or alternatives provided, and the feature is unavailable on Linux clusters.
Recommendations
- Clearly state at the beginning that the reverse proxy feature is Windows-only, to avoid confusion for Linux users.
- Provide guidance or links to alternative patterns for service discovery and communication on Linux clusters.
- If possible, mention roadmap or alternatives for Linux users, or clarify that Linux clusters must use other approaches.
Service Fabric
Standalone Service Fabric clusters overview
...-fabric/service-fabric-standalone-clusters-overview.md
High Priority
View Details â
Detected Bias Types
missing_linux_example
windows_first
Summary
The documentation page claims Service Fabric clusters can run on Windows Server and Linux, but the content and supported OS list indicate that standalone clusters are currently Windows-only. Security sections reference Windows-specific features (Kerberos, group Managed Service Accounts, Active Directory) without Linux equivalents or guidance. No Linux-specific instructions, examples, or supported OS details are provided.
Recommendations
- Clarify in the introduction that standalone clusters are currently Windows-only, despite the initial claim of Linux support.
- Remove or update the description to avoid implying Linux support if it is not available.
- If Linux support is planned or available in other scenarios, provide clear guidance or links to Linux-specific documentation.
- Add Linux-specific examples, instructions, and supported OS details when Linux support becomes available.
Service Fabric
RunToCompletion semantics and specifications
...blob/main/articles/service-fabric/run-to-completion.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page presents RunToCompletion semantics in Service Fabric with a strong Windows bias. All code examples use Windows containers (nanoserver), Windows-specific commands (cmd, echo, ping, set, exit), and the only CLI example for querying deployment status is via PowerShell. There are no Linux container examples, nor any mention of Linux-compatible commands, tools, or workflows. The documentation assumes familiarity with Windows container development and does not provide Linux parity.
Recommendations
- Add equivalent examples using Linux containers (e.g., Ubuntu or Alpine images) with bash commands.
- Include instructions for querying deployment status using Linux tools (such as Azure CLI or REST API), not just PowerShell.
- Clarify whether RunToCompletion semantics are supported for Linux containers and guest executables, and if so, provide Linux-specific guidance.
- Present examples for both Windows and Linux environments, or explicitly state if the feature is Windows-only.
Service Fabric
Application upgrade: upgrade parameters
...abric/service-fabric-application-upgrade-parameters.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page presents upgrade parameters for Service Fabric applications, but gives primary focus to Windows-centric tools (PowerShell and Visual Studio) in both structure and examples. The PowerShell and Visual Studio sections are detailed and appear first, while Linux-compatible tools (SFCTL CLI) are covered later and with less depth. No explicit Linux/macOS examples are provided for parameter usage, and PowerShell examples are shown before SFCTL, potentially creating friction for Linux users.
Recommendations
- Add explicit Linux/macOS examples for parameter usage with SFCTL, including sample commands.
- Reorganize the page to present cross-platform tools (SFCTL, REST API) before or alongside Windows tools.
- Clarify which parameters are available or behave differently across platforms.
- Ensure parity in detail and guidance for SFCTL usage as is provided for PowerShell and Visual Studio.
- Consider adding a comparison table showing parameter mapping between PowerShell, Visual Studio, and SFCTL.
Service Fabric
Azure Service Fabric networking best practices
...ice-fabric/service-fabric-best-practices-networking.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation provides both Windows and Linux guidance for Service Fabric networking, but there is a notable Windows bias. Windows/PowerShell examples and terminology appear first or exclusively in several sections, such as API endpoints, DevOps integration, and application networking. PowerShell is referenced as the primary client API example, and Windows-specific tools and scenarios (e.g., RDP, Windows Updates, Windows containers) are described in detail, while Linux equivalents are often missing or less prominent. Linux-specific guidance is present but less detailed and sometimes referenced second.
Recommendations
- Ensure Linux examples and terminology are presented alongside Windows examples, not after or omitted.
- Add explicit Linux CLI/API usage examples (e.g., Azure CLI, Service Fabric CLI) where PowerShell is referenced.
- Include Linux container networking scenarios and best practices, matching the detail given for Windows containers.
- Provide Linux-specific DevOps integration guidance (e.g., using Azure DevOps tasks with Linux clusters).
- Balance the order of examples so Linux and Windows are treated equally in tables and lists.
Service Fabric
Application lifecycle in Service Fabric
...service-fabric/service-fabric-application-lifecycle.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation consistently references PowerShell cmdlets and .NET API methods for managing the Service Fabric application lifecycle, with no explicit examples or instructions for Linux users. While REST API options are mentioned, there is a lack of parity in terms of CLI (e.g., Azure CLI, sfctl) usage examples, and no Linux shell or cross-platform command-line instructions are provided. This creates friction for Linux/macOS users, who must infer or research equivalent commands.
Recommendations
- Add explicit examples using Azure CLI and/or sfctl for each lifecycle operation (deploy, upgrade, remove, etc.), especially where PowerShell cmdlets are currently shown.
- Where PowerShell is referenced, provide equivalent bash/shell or cross-platform CLI commands, or at least link to relevant Linux instructions.
- Clarify in each section that REST API and CLI tools are cross-platform, and provide sample usage for non-Windows environments.
- In 'Preserving disk space' and 'Cleaning up files' sections, include Linux shell command examples or reference to sfctl/Azure CLI documentation for automation.
Service Fabric
Understanding periodic backup configuration
...-fabric-backuprestoreservice-configure-periodic-backup.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation page for Azure Service Fabric periodic backup configuration shows minor Windows bias. The only on-premises backup storage example provided is a Windows file share (with Windows authentication and UNC path syntax), and there are no examples or mentions of Linux-compatible storage options (such as NFS or SMB mounts on Linux). The file share configuration and authentication methods are Windows-centric, and Linux users are not given guidance or parity examples for configuring on-premises backup storage.
Recommendations
- Add examples and guidance for configuring backup storage using Linux-compatible file shares, such as NFS or SMB mounts.
- Clarify whether the file share backup storage option supports Linux-based clusters and, if so, provide sample paths and authentication methods for Linux.
- Mention any limitations or requirements for Linux users when configuring on-premises backup storage.
- Consider including a note or section about cross-platform compatibility for backup storage options.
Service Fabric
Service sensitivity
...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-sensitivity.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides PowerShell examples for configuring service sensitivity and maximum load, but does not include equivalent Linux/macOS CLI examples (such as Azure CLI or REST API). PowerShell is presented as the primary scripting interface, which may create friction for Linux/macOS users. The C# API is also shown, but this is cross-platform. The overall configuration (XML/JSON manifests) is platform-neutral, but operational scripting is Windows-centric.
Recommendations
- Add Azure CLI or REST API examples for creating and updating services with sensitivity and maximum load settings, if supported.
- Clarify whether PowerShell examples are usable on Linux/macOS (via PowerShell Core), or provide Bash shell equivalents.
- Explicitly mention any limitations or alternative workflows for Linux/macOS users.
- Consider reordering examples so that platform-neutral (manifest, JSON) approaches are shown first, followed by scripting interfaces.
Service Fabric
Service Fabric Cluster Resource Manager - Application Groups
...ice-fabric-cluster-resource-manager-application-groups.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation provides only PowerShell and C# examples for managing Service Fabric Application Groups, with no mention of Linux-compatible CLI tools (such as sfctl) or Bash equivalents. PowerShell is a Windows-centric tool, and its exclusive use creates friction for Linux/macOS users. There is no guidance or example for Linux users, even though Service Fabric supports cross-platform management.
Recommendations
- Add examples using sfctl (Service Fabric CLI), which is cross-platform and works on Linux/macOS.
- Include Bash or shell command equivalents where possible.
- Explicitly mention that PowerShell examples are for Windows, and provide Linux/macOS alternatives.
- Link to documentation about using Service Fabric on Linux, including management tools and APIs.
Service Fabric
Scalability of Service Fabric services
.../service-fabric/service-fabric-concepts-scalability.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides code examples and administrative patterns primarily using PowerShell and C#, with PowerShell being a Windows-centric tool. There are no equivalent Linux CLI or scripting examples (e.g., Bash, sfctl), and Windows tools are referenced first and exclusively in administrative sections. This creates friction for Linux users, who must translate Windows-centric instructions to Linux-compatible commands.
Recommendations
- Add Linux CLI examples using sfctl or Bash scripts alongside PowerShell examples.
- Mention Linux administrative tools and patterns (e.g., sfctl, REST API) wherever PowerShell is referenced.
- Present examples for both platforms in parallel, or clarify when a tool is Windows-only.
- Include links to Linux-specific Service Fabric documentation or guides.
Service Fabric
Azure Service Fabric standalone cluster scaling
...ce-fabric/service-fabric-cluster-scaling-standalone.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page for scaling Azure Service Fabric standalone clusters exhibits Windows bias. It references PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) without providing equivalent Linux or cross-platform CLI examples. The linked 'scale a standalone cluster' guide is titled 'service-fabric-cluster-windows-server-add-remove-nodes.md', further suggesting a Windows-centric approach. No Linux-specific guidance or parity is offered, leaving Linux users without clear instructions.
Recommendations
- Add examples using Service Fabric CLI (sfctl) or REST APIs, which are cross-platform.
- Explicitly state if standalone cluster scaling is Windows-only; if not, provide Linux/macOS instructions.
- Include guidance for Linux-based deployments, such as how to query cluster manifests and perform configuration upgrades on Linux.
- Link to or create documentation for scaling standalone clusters on Linux, if supported.
Service Fabric
Azure Service Fabric Docker Compose Deployment Preview
...ticles/service-fabric/service-fabric-docker-compose.md
Medium 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, with more detailed command coverage and explanations, which may create friction for Linux/macOS users. The CLI examples are included and cover equivalent functionality, but PowerShell is emphasized and described as the default approach.
Recommendations
- Present CLI (sfctl) examples before or alongside PowerShell examples to avoid Windows-first bias.
- Expand CLI example explanations to match the detail provided for PowerShell commands.
- Explicitly note that sfctl is cross-platform and recommended for Linux/macOS users.
- Consider adding a short section clarifying OS compatibility for each tool.
- If possible, provide Bash or shell script examples for common workflows.
Service Fabric
Define Service Configuration in StartupServices.xml for a Service Fabric Application
...service-fabric/service-fabric-startupservices-model.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation is heavily oriented around Visual Studio workflows (Build/Rebuild/F5/Ctrl+F5/Publish), which are Windows-centric. All deployment and configuration examples reference Visual Studio and Windows-specific patterns. There are no examples or guidance for Linux/macOS users, nor mention of cross-platform tooling or workflows for Service Fabric application development.
Recommendations
- Add explicit guidance for Linux/macOS users, including how to manage service configuration and deployment without Visual Studio.
- Provide examples using cross-platform tools such as Azure CLI, Service Fabric CLI (sfctl), or PowerShell Core (if applicable).
- Clarify which features are Visual Studio/Windows-only and offer alternative approaches for Linux/macOS environments.
- Include sample workflows for editing and deploying StartupServices.xml and ApplicationManifest.xml on Linux/macOS.
Service Fabric
Manage certificates in a Service Fabric cluster
...vice-fabric/cluster-security-certificate-management.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation provides a mix of platform-neutral JSON ARM template examples and PowerShell scripts, but the only explicit scripting example for certificate enrollment is in PowerShell. The Key Vault VM extension is described as 'for Windows', and its documentation links and schema are Windows-specific. The 'linkOnRenewal' feature is explicitly noted as Windows-only, and troubleshooting sections reference Windows APIs (S-channel, CERT_RENEWAL_PROP_ID). Linux equivalents (such as Azure Key Vault Linux VM extension, Bash/CLI examples, or Linux certificate store handling) are not mentioned or demonstrated. Windows-centric tools and patterns (PowerShell, Windows certificate store, S-channel) are referenced before or instead of Linux alternatives.
Recommendations
- Add Azure CLI or Bash scripting examples for certificate enrollment and management alongside PowerShell.
- Explicitly mention and link to the Key Vault VM extension for Linux, and clarify any differences in behavior or limitations.
- Provide guidance or examples for managing certificates on Linux nodes (e.g., certificate store locations, permissions, monitoring).
- Where Windows-specific features are discussed (e.g., linkOnRenewal, S-channel), note Linux alternatives or limitations.
- Ensure troubleshooting and FAQ sections address Linux scenarios, including relevant APIs and certificate handling.
- Balance example order so Linux and Windows are equally represented, or clarify when features are Windows-only.
Service Fabric
X.509 Certificate-based Authentication in a Service Fabric Cluster
...ticles/service-fabric/cluster-security-certificates.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation provides a thorough conceptual overview of X.509 certificate-based authentication in Service Fabric clusters, but exhibits mild Windows bias. Windows terminology and tools (e.g., certificate store paths like 'LocalMachine\My', references to Win32 CryptoAPI, and event log locations) are mentioned first or exclusively. Troubleshooting sections focus on Windows event logs and CAPI2 logging, with no equivalent Linux guidance. While Linux paths are briefly mentioned (e.g., '/var/lib/sfcerts'), Windows-centric examples and APIs dominate, creating friction for Linux users.
Recommendations
- Add Linux-specific examples for certificate store locations, certificate management, and troubleshooting (e.g., relevant log files, commands for viewing certificates).
- When referencing Windows tools or APIs (e.g., CertGetCertificateChain, CAPI2 logging), provide Linux equivalents or clarify if the guidance is Windows-only.
- Ensure troubleshooting steps include Linux/macOS guidance, such as how to access Service Fabric logs, check certificate permissions, and validate certificate chains.
- Where possible, present cross-platform examples side-by-side, or note differences in behavior and configuration between Windows and Linux clusters.
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation page exhibits Windows bias by focusing on custom Windows images, providing PowerShell examples for role assignment, and referencing Windows/PowerShell tools and patterns before their Linux equivalents. Although there are links to Linux documentation for creating custom images and using Azure CLI, the main narrative and examples prioritize Windows terminology and tools.
Recommendations
- Provide equivalent Linux/bash examples for role assignment (e.g., using Azure CLI instead of PowerShell).
- Clarify that custom images can be Linux-based and provide explicit Linux image deployment examples.
- Ensure that references to Linux documentation are as prominent as Windows documentation.
- Add ARM template examples for Linux node types if supported.
- Mention any limitations or differences for Linux custom images in Service Fabric Managed Clusters.
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 â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides examples for configuring Service Fabric managed cluster node types using Azure Portal, ARM templates, and PowerShell. PowerShell is the only CLI example provided, with no equivalent Bash, Azure CLI, or Linux/macOS shell examples. The PowerShell examples are presented prominently and repeatedly, creating friction for Linux/macOS users who cannot use PowerShell natively. There is no explicit mention of Windows-only features, so the bias is not justified by feature scope.
Recommendations
- Add Azure CLI examples alongside PowerShell for all tasks (add, remove, scale, configure placement properties, etc.), as Azure CLI is cross-platform and works on Linux/macOS.
- Clarify that PowerShell examples are for Windows users and provide guidance for Linux/macOS users.
- Consider referencing Bash scripting or ARM template deployment via Azure CLI for Linux/macOS users.
- Review all sections where PowerShell is used and ensure parity with Azure CLI or Bash examples.
Service Fabric
Introduction to the Service Fabric Infrastructure Service
.../articles/service-fabric/infrastructure-service-faq.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides a PowerShell-only example for bypassing Infrastructure Service, and references Service Fabric Explorer (a GUI tool primarily used on Windows). No Linux/bash alternatives or cross-platform CLI examples are given, even though Service Fabric clusters can be managed from Linux/macOS environments.
Recommendations
- Add equivalent bash/CLI examples for bypassing Infrastructure Service, using Azure CLI or Service Fabric CLI (sfctl) where possible.
- Clarify whether the PowerShell command is required or if cross-platform tools can be used.
- Mention Service Fabric Explorer alternatives or accessibility from non-Windows platforms.
- Provide guidance for Linux/macOS users on connecting to Service Fabric clusters and performing similar operations.
Service Fabric
Deny assignment policy for Service Fabric managed clusters
...cles/service-fabric/managed-cluster-deny-assignment.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides examples and links primarily for Azure PowerShell, mentioning it before Azure CLI and other cross-platform tools. PowerShell is highlighted in the best practices section and in the recommended APIs for managing Service Fabric managed clusters, which may create friction for Linux/macOS users who prefer Azure CLI or other cross-platform utilities.
Recommendations
- Provide Azure CLI examples alongside Azure PowerShell examples for key operations such as deleting NodeTypes, restarting, and reimaging scale sets.
- Mention Azure CLI before or equally with Azure PowerShell in the best practices section to reinforce cross-platform parity.
- Clarify that Azure PowerShell is available cross-platform, but also highlight CLI usage for Linux/macOS users.
- Add explicit Linux/macOS guidance or callouts where relevant, especially in sections referencing PowerShell-heavy workflows.
Service Fabric
Learn about Azure Service Fabric application security
...ric/service-fabric-application-and-service-security.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation provides a general overview of Service Fabric application security, but several sections exhibit Windows bias. Windows-specific features (e.g., Active Directory, gMSA, BitLocker) are mentioned before or without Linux equivalents. Examples and guidance for Linux clusters are sparse or missing, especially regarding disk encryption and user account management. The use of Windows terminology and tools (e.g., NetworkService, BitLocker, gMSA) is more prominent, and Linux-specific instructions are often absent or relegated to TODO comments.
Recommendations
- Add explicit Linux examples for disk encryption (e.g., using Azure Disk Encryption with Linux, or dm-crypt/LUKS).
- Provide guidance on managing user accounts and security principals for Linux clusters, including relevant Linux account types and group management.
- Include Linux-specific instructions or references for certificate management and service startup scripts.
- Ensure parity in examples and mention Linux options alongside Windows options, rather than only in passing or as TODOs.
- Clarify which features are Windows-only and provide alternative approaches for Linux where possible.
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
powershell_heavy
windows_first
Summary
The documentation page primarily discusses data serialization in the context of Azure Service Fabric, which is cross-platform. However, in the 'Next steps' section, application upgrade tutorials are listed for Visual Studio and PowerShell, both of which are Windows-centric tools. PowerShell is mentioned as a primary upgrade method, and there is no mention of Linux/macOS CLI or tooling alternatives, nor are Linux-specific examples provided. The serialization discussion is focused on C# and .NET, but this is appropriate for Service Fabric workloads.
Recommendations
- Add links or references to application upgrade tutorials using Azure CLI or Service Fabric CLI (sfctl), which are cross-platform and commonly used on Linux/macOS.
- Clarify that PowerShell and Visual Studio are Windows-centric, and provide Linux/macOS alternatives where possible.
- Consider including examples or guidance for upgrading Service Fabric applications on Linux clusters, if supported.
- Ensure parity in 'Next steps' by listing Linux/macOS-friendly tools alongside Windows tools.
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
missing_linux_example
windows_first
Summary
The documentation demonstrates a notable Windows bias. PowerShell is the only command-line example shown, and Windows-specific tools (e.g., http.sys) are referenced without Linux equivalents. There are no CLI or SDK examples for Linux/macOS users, and the guidance assumes familiarity with Windows administration patterns. The 'Next steps' section also prioritizes Visual Studio and PowerShell, both Windows-centric tools.
Recommendations
- Add equivalent Azure CLI or Service Fabric CLI (sfctl) examples for Linux/macOS users alongside PowerShell commands.
- When referencing Windows-specific components (like http.sys), clarify their Linux/macOS equivalents or note platform limitations.
- Include guidance or links for performing upgrades using cross-platform tools (e.g., sfctl, REST API, or SDKs) where possible.
- In 'Next steps', add tutorials for Linux/macOS workflows (e.g., using sfctl or Azure CLI) and not just Visual Studio/PowerShell.
Service Fabric
Service Fabric Explorer blocking operations
...ged-cluster-service-fabric-explorer-blocking-operation.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page predominantly references Az PowerShell cmdlets for managing Service Fabric resources, with no explicit mention of Linux/macOS equivalents or CLI usage except for a brief reference to 'az resource' for deleting applications. PowerShell examples and terminology are presented first and most frequently, which may create friction for Linux/macOS users who typically use Azure CLI or bash scripts.
Recommendations
- Add Azure CLI examples for all operations (e.g., creating, deleting, scaling applications/services) alongside PowerShell cmdlets.
- Clarify that Az PowerShell cmdlets can be used cross-platform, or specify any limitations for Linux/macOS users.
- Where possible, provide ARM template examples and instructions for both PowerShell and CLI users.
- Ensure that references to PowerShell are balanced with CLI/bash alternatives, especially in 'Best practices' sections.
Service Fabric
Monitor Azure Service Fabric
...main/articles/service-fabric/monitor-service-fabric.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation covers monitoring for both Windows and Linux Service Fabric clusters, but there is a tendency to mention Windows-specific tools and workflows first (e.g., EventStore APIs, Event Log/Event Viewer, Diagnostics Agent). Some examples and tutorials focus primarily on .NET applications and Windows clusters, with Linux equivalents referenced but not always given equal detail or prominence. Linux-specific guidance is sometimes relegated to links or brief mentions, rather than integrated examples or walkthroughs.
Recommendations
- Ensure Linux monitoring examples and workflows are presented alongside Windows equivalents, not just referenced via links.
- Provide explicit Linux sample code, configuration snippets, and screenshots where Windows examples are shown (e.g., for EventStore, logging setup, agent configuration).
- Clarify when a feature is Windows-only (such as EventStore APIs) and offer alternative Linux approaches or tools.
- Balance tutorial coverage so that Linux users can follow step-by-step guides without needing to search for additional resources.
- Highlight cross-platform tools and practices (such as Service Fabric Explorer, FabricObserver, and Azure Monitor agent) with equal detail for both OSes.
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 contains a notable Windows bias in its guidance for validating manifest XML schemas. It exclusively recommends opening the schema file in Visual Studio using a Windows file path, with no mention of Linux/macOS alternatives or cross-platform editors. Additionally, the only tool-specific advice is Windows-centric and appears early in the article.
Recommendations
- Provide instructions for validating manifest XML schemas using cross-platform tools such as VS Code, xmllint, or other XML editors available on Linux/macOS.
- Include Linux/macOS file paths for the schema file, or clarify where the schema can be found on those platforms.
- When referencing editors like Visual Studio, also mention cross-platform alternatives (e.g., VS Code with XML extensions, JetBrains Rider, or command-line tools).
- Ensure that any tool-specific guidance is either cross-platform or that platform-specific instructions are grouped together and clearly labeled.
Service Fabric
Advanced Application Upgrade Topics
...-fabric/service-fabric-application-upgrade-advanced.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page provides extensive PowerShell examples and references to PowerShell cmdlets for Service Fabric application upgrades, with no mention of Linux/macOS equivalents or cross-platform CLI tools. Windows/PowerShell tools are presented as the default method for performing upgrades, and there is no guidance for Linux users on how to accomplish these tasks using Azure CLI, REST API, or Service Fabric CLI (sfctl).
Recommendations
- Add equivalent examples using Azure CLI (az), Service Fabric CLI (sfctl), or REST API for application upgrade operations.
- Clearly indicate which PowerShell cmdlets are available cross-platform (if any), and provide guidance for Linux/macOS users.
- Include links or references to Linux/macOS documentation or tools for Service Fabric management.
- Where possible, show both Windows and Linux/macOS workflows side by side, or note any limitations for non-Windows users.
Service Fabric
Architecture of Azure Service Fabric
...articles/service-fabric/service-fabric-architecture.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
Summary
The documentation references PowerShell cmdlets and administrative APIs as the primary means for managing Service Fabric clusters, without mentioning Linux equivalents such as Azure CLI or REST APIs. This may give the impression that management is Windows/PowerShell-centric, potentially confusing or excluding Linux/macOS users.
Recommendations
- Explicitly mention cross-platform management options such as Azure CLI and REST APIs alongside PowerShell.
- Provide examples or references for managing Service Fabric clusters from Linux/macOS environments.
- Clarify that PowerShell Core is available cross-platform, if relevant, or link to documentation on using PowerShell on Linux/macOS.
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 â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation for on-demand backup in Azure Service Fabric is heavily focused on PowerShell-based workflows, with all code examples using PowerShell cmdlets or PowerShell-based REST calls. There are no examples or guidance for Linux/macOS users, such as using Bash, curl, or Azure CLI. The prerequisite section also assumes PowerShell usage and module installation, which is Windows-centric. This creates friction for Linux/macOS users who may need to perform the same tasks.
Recommendations
- Add equivalent Bash/curl examples for REST API calls, demonstrating how to trigger backups and track progress from Linux/macOS.
- Mention Azure CLI commands if available for backup operations.
- Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is required for all platforms or provide alternatives for Linux/macOS.
- Reorganize examples to show cross-platform parity, e.g., REST API via curl first, then PowerShell.
- Add a note about platform support and limitations, explicitly stating if certain operations are Windows-only.
Service Fabric
Capacity planning and scaling for Azure Service Fabric
...bric/service-fabric-best-practices-capacity-scaling.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides numerous PowerShell-based examples and instructions for scaling Service Fabric clusters, but does not offer equivalent Linux CLI (bash, Azure CLI) examples or guidance. Windows/PowerShell commands are presented first and exclusively, creating friction for Linux users who may not have access to PowerShell or Windows tools.
Recommendations
- Add equivalent Azure CLI or bash examples for scaling operations, such as disabling/removing nodes and managing cluster resources.
- Clearly indicate which commands are Windows-specific and provide alternative instructions for Linux environments.
- Where PowerShell is referenced, link to Linux-compatible tools or scripts (e.g., Azure CLI, REST API calls).
- Ensure that manual and programmatic scaling instructions are platform-neutral or include both Windows and Linux options.
Service Fabric
Restoring backup in Azure Service Fabric
...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-backup-restore-service-trigger-restore.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page exclusively uses PowerShell and the Microsoft.ServiceFabric.Powershell.Http module for all CLI and scripting examples, with no mention of Linux/macOS-compatible tools or equivalent Bash/cURL examples. All REST API calls are demonstrated via PowerShell, and prerequisites focus on installing Windows-specific PowerShell modules. There is no guidance for Linux/macOS users on how to perform these tasks, despite Service Fabric supporting cross-platform clusters.
Recommendations
- Add Bash/cURL examples for REST API calls, showing how to authenticate and trigger restores from Linux/macOS.
- Mention any cross-platform CLI tools (such as Azure CLI or Service Fabric CLI) that can be used for backup/restore operations.
- Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is required for all scenarios, or if REST API calls can be made directly from any platform.
- Provide guidance on certificate handling and authentication for Linux/macOS users.
- Include a note about platform compatibility and limitations, if any exist.
Service Fabric
Azure Service Fabric infrastructure as Code Best Practices
...tps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-best-practices-infrastructure-as-code.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Resource Manager templates, but PowerShell is featured prominently and exclusively for certain operations (e.g., cluster upgrades). Windows-specific tools and registry keys are mentioned without Linux equivalents, and Windows configuration is discussed before Linux. While Linux is referenced and linked, some critical upgrade tasks are only shown for Windows/PowerShell.
Recommendations
- Add Linux-specific examples for cluster upgrades, including equivalent commands (e.g., using Bash or Azure CLI) for manual upgrades.
- When referencing registry keys or Windows Update settings, clarify Linux equivalents or explicitly state if not applicable.
- Provide parity in scripting examples (e.g., show Bash or Python for deployment and upgrade tasks alongside PowerShell).
- Ensure that Linux configuration options (such as disabling automatic updates) are discussed with equal prominence.
- Where possible, avoid presenting Windows tools or patterns before Linux equivalents unless Windows is the default or only supported platform.
Service Fabric
Change Azure Service Fabric cluster settings
...rvice-fabric/service-fabric-cluster-fabric-settings.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation presents Service Fabric cluster settings in a platform-neutral way, but several parameters and descriptions reference Windows-specific concepts (e.g., certificate store names like 'MY', store locations like 'LocalMachine', NTLM authentication, and Windows Defender Firewall). Windows terminology and tools are often mentioned first or exclusively, with Linux equivalents less visible or absent. Some settings are described as 'Windows only' without Linux alternatives or guidance. There are also references to Windows-specific behaviors (e.g., 'Windows Fabric Replicator', 'Windows Fabric waits', 'Windows only' log settings) and links to Windows-focused documentation. Linux-specific settings are present but less prominent.
Recommendations
- For parameters referencing Windows concepts (e.g., certificate stores, NTLM, firewall), add explicit Linux equivalents or clarify Linux behavior.
- Where settings are 'Windows only', provide Linux alternatives or note Linux limitations.
- Ensure Linux-specific settings (e.g., X509Folder, LinuxExternalExecutablePath, EnforceLinuxMinTlsVersion) are as prominent as Windows settings.
- Add examples or guidance for Linux cluster configuration and upgrade, not just Windows/Windows Server.
- Review descriptions and guidance to avoid defaulting to Windows terminology when Linux is supported.
Service Fabric
Node types and virtual machine scale sets
...les/service-fabric/service-fabric-cluster-nodetypes.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page provides general information about Azure Service Fabric node types and virtual machine scale sets, but several sections and examples show Windows bias. The JSON snippet for the Service Fabric Virtual Machine extension uses a Windows-style file path (e.g., 'D:\\SvcFab'), and the 'Next steps' section links to PowerShell scripts for RDP port changes and admin credential updates, which are Windows-specific tasks. There are no Linux/macOS equivalents or guidance for Linux node types, and Windows tools (RDP, PowerShell) are referenced without alternatives.
Recommendations
- Provide Linux-specific examples, such as using Linux file paths (e.g., '/var/svcfab') in the 'dataPath' property.
- Include guidance or links for connecting to Linux nodes (e.g., SSH instructions) alongside RDP/PowerShell examples.
- Add parity for admin credential changes and port management on Linux VMs, referencing Bash scripts or Azure CLI.
- Clarify when a step is Windows-only and offer Linux alternatives where possible.
- Mention Linux node types and their configuration explicitly, not just as an option in the property table.
Service Fabric
Service Fabric Cluster Resource Manager - Placement Policies
...ce-manager-advanced-placement-rules-placement-policies.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page provides code examples primarily in C# and PowerShell for configuring Service Fabric placement policies. PowerShell is a Windows-centric tool, and no equivalent Linux/macOS CLI examples (such as Azure CLI or REST API) are provided. All operational examples for service creation and placement policy configuration use PowerShell, which may create friction for users managing Service Fabric clusters from Linux or macOS environments.
Recommendations
- Add Azure CLI examples for service creation and placement policy configuration, if supported.
- Include REST API examples for configuring placement policies, to provide platform-neutral guidance.
- Clarify whether PowerShell is required or if cross-platform tools can be used, and link to relevant documentation.
- Consider mentioning or linking to any available Linux/macOS management tools for Service Fabric clusters.
Service Fabric
Manage Azure Service Fabric app load using metrics
...ric/service-fabric-cluster-resource-manager-metrics.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page provides code examples for managing Service Fabric metrics primarily in C# and PowerShell. PowerShell is a Windows-centric tool, and no equivalent Linux/macOS CLI examples (such as Azure CLI or bash scripts) are provided. The PowerShell examples are given alongside C# code, but there is no mention of cross-platform alternatives or guidance for Linux/macOS users. This creates friction for users operating Service Fabric clusters on non-Windows environments.
Recommendations
- Add Azure CLI examples for service creation and metric management, which are cross-platform.
- Mention and link to any REST API documentation for Service Fabric metric management, as REST APIs are platform-neutral.
- If PowerShell is required, clarify whether PowerShell Core (pwsh) is supported on Linux/macOS, and provide guidance for installation and usage.
- Explicitly state any limitations or differences for Linux/macOS users, and provide alternative workflows if available.
- Consider including bash script examples or references to Service Fabric SDK tools available for Linux.
Service Fabric
Service Fabric Cluster Resource Manager: Movement cost
...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-movement-cost.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page provides PowerShell examples for configuring MoveCost in Service Fabric, but does not include equivalent Linux CLI (e.g., Bash, Azure CLI) or cross-platform scripting examples. PowerShell is presented before C# in each example section, and no Linux-specific guidance or parity is offered for command-line operations. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer native tools.
Recommendations
- Add Azure CLI or Bash examples for creating and updating Service Fabric services with MoveCost, where possible.
- Clarify whether PowerShell commands are supported on Linux/macOS (via PowerShell Core), and provide instructions if so.
- Consider including REST API or SDK examples for cross-platform usage.
- Explicitly mention any limitations or alternatives for Linux/macOS users in relevant sections.
- Present cross-platform examples (e.g., Azure CLI, REST API) before or alongside PowerShell to avoid Windows-first bias.
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 â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides example code for configuring auto scaling policies using application manifests, C# APIs, and PowerShell. However, all CLI/script examples are PowerShell-based, with no equivalent Bash or Linux CLI examples. PowerShell is a Windows-centric tool, and its exclusive use creates friction for Linux/macOS users. The documentation does not mention or demonstrate Linux-native tools or workflows for managing Service Fabric auto scaling policies, nor does it clarify whether PowerShell Core (cross-platform) is supported. Additionally, PowerShell examples are presented alongside C# and manifest examples, but no Linux-first or cross-platform CLI guidance is given.
Recommendations
- Add Bash or Azure CLI examples for configuring auto scaling policies, especially for Linux-based Service Fabric clusters.
- Clarify whether PowerShell Core can be used on Linux/macOS, or specify if the PowerShell examples are Windows-only.
- Mention and demonstrate Linux-native management workflows (e.g., REST API, Azure CLI, Bash scripts) for Service Fabric auto scaling.
- Consider providing a table or section comparing Windows and Linux management options for Service Fabric auto scaling.
- Explicitly state any limitations or differences for Linux clusters in auto scaling configuration and management.
Service Fabric
Cluster Resource Manager - Management Integration
...fabric-cluster-resource-manager-management-integration.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides a PowerShell example (Get-ServiceFabricPartitionHealth) for querying cluster health, with no equivalent Linux/macOS CLI or REST API example. The example is shown using Windows paths and PowerShell syntax, and no mention is made of cross-platform tools or commands. This creates friction for Linux/macOS users, as Service Fabric supports cross-platform management via CLI and REST, but only Windows tooling is demonstrated.
Recommendations
- Add equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
- Mention REST API options for health queries, which are platform-agnostic.
- When showing PowerShell examples, also provide the analogous sfctl or REST command, and note any differences.
- Avoid using Windows paths (e.g., C:\Users\User) unless necessary; use generic or platform-neutral prompts.
- Clarify that management operations can be performed from Linux/macOS, and link to relevant cross-platform tooling documentation.
Service Fabric
Azure Service Fabric dynamic node tags
...tps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-node-tagging.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation provides detailed PowerShell examples for managing node tags and configuring services, but does not include equivalent CLI or scripting examples for Linux/macOS users (e.g., Azure CLI, Bash, or REST API usage). PowerShell is a Windows-centric tool, and its exclusive use here creates friction for users on other platforms.
Recommendations
- Add examples using Azure CLI or Bash scripts for managing node tags and configuring services, as these are cross-platform and widely used by Linux/macOS users.
- Include REST API examples for all operations (adding/removing node tags, creating/updating services with tags), as REST is platform-agnostic.
- Explicitly state whether the PowerShell cmdlets are available cross-platform (e.g., via PowerShell Core), and if not, provide alternatives.
- Consider reordering or parallelizing examples so that non-Windows methods are shown alongside PowerShell and C#.
Service Fabric
Secure an Azure Service Fabric cluster
...cles/service-fabric/service-fabric-cluster-security.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page covers security for Azure Service Fabric clusters, including both Azure-hosted and standalone Windows clusters. However, it consistently references Windows Server clusters and Windows-specific security mechanisms (such as Kerberos, group Managed Service Accounts, Windows certificate services, MakeCert.exe), and links only to Windows-specific guides for standalone clusters. There are no explicit examples or guidance for standalone Linux clusters, nor are Linux certificate creation tools or Linux security patterns mentioned. The concept section briefly states that Linux clusters follow the same security principles, but practical Linux guidance is missing.
Recommendations
- Add explicit guidance and links for securing standalone Linux Service Fabric clusters, including certificate setup and client authentication.
- Include Linux-specific certificate creation tools (e.g., OpenSSL) and examples alongside Windows tools like MakeCert.exe.
- Provide parity in example links and walkthroughs for Linux clusters, not just Windows clusters.
- Clarify which security features are available or recommended for Linux clusters, and note any limitations.
Service Fabric
Health monitoring in Service Fabric
...s/service-fabric/service-fabric-health-introduction.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
Summary
The documentation provides a PowerShell-only example for reporting and evaluating application health in Service Fabric, without offering equivalent Linux/macOS CLI or REST API examples. While Service Fabric is cross-platform, the exclusive use of PowerShell in the example creates friction for Linux/macOS users who may not have access to PowerShell or prefer other tools.
Recommendations
- Add equivalent examples using the Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
- Provide REST API examples for health reporting and querying, as these are platform-agnostic.
- Mention PowerShell as one option, but ensure Linux/macOS users are equally supported with their native tools.
- Clarify in the example section that PowerShell is Windows-specific, and link to Linux/macOS alternatives.
Service Fabric
Upgrade an Azure Service Fabric standalone cluster
...ce-fabric/service-fabric-cluster-upgrade-standalone.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page on upgrading an Azure Service Fabric standalone cluster demonstrates a Windows bias. It references Windows-specific upgrade guides and tools (e.g., Patch Orchestration Application for Windows), and links to documentation with 'windows-server' in the URL. There are no examples or guidance for Linux-based standalone clusters, nor is it clarified whether Linux is supported or not.
Recommendations
- Clarify early in the documentation whether standalone clusters are Windows-only or if Linux is supported.
- If Linux-based standalone clusters are supported, provide equivalent upgrade instructions, configuration examples, and patching guidance for Linux.
- If only Windows is supported, explicitly state this to avoid confusion for Linux/macOS users.
- Where possible, use platform-neutral language and examples, or provide parallel sections for both Windows and Linux.
Service Fabric
Azure Service Fabric application resource model
...ervice-fabric/service-fabric-concept-resource-model.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page for the Azure Service Fabric application resource model demonstrates a notable Windows bias. All deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource), with no mention of Azure CLI equivalents or Linux/macOS workflows. The application packaging step is shown using Visual Studio, a Windows-centric tool, and directory paths are given in Windows format. There are no instructions or examples for Linux/macOS users, nor is cross-platform tooling discussed.
Recommendations
- Add Azure CLI examples for deployment, upgrade, and deletion steps alongside PowerShell examples.
- Include instructions for packaging applications using cross-platform tools (e.g., dotnet CLI, SF tooling) instead of only Visual Studio.
- Show directory paths in both Windows and Linux/macOS formats, or clarify that the steps are applicable cross-platform.
- Mention or link to Linux/macOS-specific guidance for Service Fabric application management.
- Consider providing sample scripts or workflows for Linux/macOS users.
Service Fabric
Learn more about Azure Service Fabric
...icles/service-fabric/service-fabric-content-roadmap.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation page provides a broad overview of Azure Service Fabric, which supports both Windows and Linux. However, there are several instances of Windows bias: Windows-specific tools (PowerShell, Visual Studio) are mentioned before their Linux equivalents, Windows services and executables are referenced without clear Linux alternatives, and some examples or instructions are Windows-centric. Linux support is acknowledged, but Linux-specific examples, tools, and workflows are often missing or secondary.
Recommendations
- Provide Linux-specific examples and workflows alongside Windows instructions, especially in sections referencing PowerShell, Visual Studio, and Windows executables.
- Mention Linux CLI tools (e.g., Bash, sfctl) and package management options where PowerShell or Windows tools are discussed.
- Clarify which features are Windows-only and which are cross-platform, linking to Linux documentation where appropriate.
- Add explicit instructions or links for creating and managing clusters on Linux, including supported programming models and deployment methods.
- Balance the order of presentation so Linux and Windows are treated equally in examples and tool references.
Service Fabric
Azure Service Fabric hosting activation and deactivation life cycle
...les/service-fabric/service-fabric-hosting-lifecycle.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page on Azure Service Fabric hosting activation and deactivation life cycle is largely platform-neutral in its conceptual explanations, but the 'Next steps' section and some linked references emphasize PowerShell for deployment/removal tasks, which is most commonly associated with Windows. There is no explicit mention of Linux equivalents or cross-platform tooling, and PowerShell is presented as the default method for operational tasks.
Recommendations
- Add examples or links for deploying/removing applications using cross-platform tools (e.g., Azure CLI, REST API, or Service Fabric CLI) alongside PowerShell.
- Clarify whether PowerShell examples are usable on Linux/macOS (via PowerShell Core), or provide Linux-specific instructions if differences exist.
- Include references to Linux/macOS documentation or operational guides where relevant.
- Ensure that linked references (such as [Deploy and remove applications]) include parity for Linux/macOS users.
Service Fabric
Upgrading Azure Service Fabric clusters
...icles/service-fabric/service-fabric-cluster-upgrade.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation provides general guidance on upgrading Azure Service Fabric clusters, but in sections such as 'Upgrading OS images for cluster nodes', it references Windows-specific patching and links only to Windows patching documentation. Additionally, PowerShell is mentioned as a tool for cluster management alongside Azure CLI, but Linux-specific tools or examples are not provided. The order of mention and focus on Windows patching creates a Windows-first impression, and Linux cluster upgrade scenarios are not addressed.
Recommendations
- Add explicit guidance and links for patching/upgrading Linux-based Service Fabric clusters, if supported.
- Provide Linux/macOS-specific examples for cluster management tasks (e.g., using Azure CLI or Bash scripts).
- Clarify whether Service Fabric clusters can run on Linux nodes and, if so, include parity documentation for OS image upgrades and patch orchestration.
- When mentioning PowerShell, also mention Bash/Azure CLI usage for Linux/macOS users, with example commands.
Service Fabric
Azure Service Fabric Events
...es/service-fabric/service-fabric-diagnostics-events.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation page for Azure Service Fabric Events primarily references Windows-specific logging mechanisms (ETW/Windows Event logs) and the Windows Azure diagnostics agent. There are no explicit examples or guidance for accessing or monitoring Service Fabric events on Linux-based clusters, nor are Linux-native tools or patterns mentioned. Windows tools and approaches are presented first and exclusively, creating friction for Linux users.
Recommendations
- Add documentation and examples for accessing Service Fabric events on Linux clusters, including supported logging mechanisms (e.g., stdout, syslog, or Azure Monitor integration for Linux).
- Mention Linux-native monitoring tools and how they can be used to visualize or analyze Service Fabric events.
- Clarify which approaches are Windows-only and provide Linux equivalents where possible.
- Ensure parity in guidance for configuring diagnostics and event collection on both Windows and Linux clusters.
Service Fabric
Azure Service Fabric DNS service
...n/articles/service-fabric/service-fabric-dnsservice.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides PowerShell examples for setting DNS names, references ApplicationManifest.xml (a Windows-centric deployment artifact), and describes enabling DNS service via Azure portal (Windows clusters only). Linux support is mentioned as limited, but there are no Linux-specific examples or guidance for equivalent tasks (e.g., using CLI, ARM templates, or other Linux-friendly tools). Windows tools and patterns are presented first and in greater detail, creating friction for Linux users.
Recommendations
- Add explicit Linux-focused examples for setting DNS names, such as using Azure CLI, ARM templates, or other Linux-compatible methods.
- Clarify which steps are Windows-only and provide alternative instructions for Linux clusters where possible.
- Include guidance on how Linux users can enable DNS service (since portal is not supported), with step-by-step ARM template or CLI instructions.
- Balance the order of examples so Linux methods are not always secondary or omitted.
- Mention any limitations or workarounds for Linux clusters more prominently, and link to relevant Linux-specific documentation.
Service Fabric
Azure Service Fabric hosting model
...rticles/service-fabric/service-fabric-hosting-model.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides PowerShell-based examples and references for managing Service Fabric services, with no equivalent CLI or Linux-native examples. PowerShell is featured as the primary command-line tool, and there is no mention of Service Fabric CLI (sfctl) or Bash examples, which are relevant for Linux/macOS users. This creates friction for non-Windows users, though the underlying concepts are cross-platform.
Recommendations
- Add equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
- When referencing PowerShell commands, also provide the analogous sfctl or REST API commands.
- Explicitly mention that PowerShell examples are for Windows and provide guidance for Linux/macOS users.
- Consider adding a table or section summarizing management options for both Windows and Linux environments.
Service Fabric
Azure Service Fabric image store connection string
...fabric/service-fabric-image-store-connection-string.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page references PowerShell as the primary example for interacting with Service Fabric clusters, and links to PowerShell-based deployment/removal guides as the main 'next steps'. While Service Fabric is cross-platform, the examples and guidance are Windows-centric, with PowerShell mentioned before .NET and REST alternatives. There are no explicit Linux/macOS CLI or scripting examples, nor is Azure CLI or Bash referenced.
Recommendations
- Add examples and links for deploying and managing Service Fabric clusters using cross-platform tools such as Azure CLI, Bash, or Python SDK.
- Include Linux/macOS-specific instructions or clarify that the guidance applies equally to those platforms.
- Reorder references so that cross-platform or platform-neutral tools (e.g., REST API, .NET Core) are mentioned before or alongside PowerShell.
- Provide explicit guidance for verifying cluster manifests and connection strings on Linux/macOS environments.
Service Fabric
Azure Service Fabric container application manifest examples
...abric/service-fabric-manifest-example-container-app.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page for Azure Service Fabric container application manifest examples demonstrates a notable Windows bias. The manifest examples and explanations are explicitly based on a Windows Server 2016 container sample. Several features and instructions (such as obtaining the OS build version with 'winver', Windows-style paths like 'c:\VolumeTest\Data', and references to the ServiceFabric PowerShell module) are Windows-specific or presented with Windows-first terminology. There are no Linux-specific examples, paths, or instructions, and Linux parity is only briefly mentioned in passing (e.g., certificate handling).
Recommendations
- Add equivalent Linux-based manifest examples or clarify which sections apply to Linux clusters.
- When referencing Windows tools (e.g., 'winver'), provide the Linux equivalent (e.g., 'cat /etc/os-release' or 'uname -r').
- Use cross-platform path examples or provide both Windows and Linux path formats where relevant.
- Clarify in the introduction whether the examples are intended for Windows-only clusters, or provide guidance for Linux clusters if supported.
- When mentioning PowerShell or Windows-specific tools, also reference Linux equivalents (e.g., Azure CLI, Bash scripts) if available.
Service Fabric
Manage apps for multiple environments
...e-fabric-manage-multiple-environment-app-configuration.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page presents Windows/PowerShell examples first and in greater detail, with explicit mention of PowerShell cmdlets and Visual Studio workflows. Linux tooling (sfctl) is mentioned, but with less detail and no explicit Linux shell example. There is no clear example or workflow for Linux/macOS users outside of a brief mention of sfctl and Jenkins.
Recommendations
- Provide explicit Linux/macOS shell examples for application creation, such as using sfctl with sample JSON parameter input.
- Balance the order of examples: present Linux/macOS workflows alongside or before Windows/PowerShell examples.
- Expand on Jenkins and other cross-platform CI/CD tools with sample scripts for parameter substitution.
- Clarify which tools are cross-platform and which are Windows-only, to help users choose appropriate workflows.
Service Fabric
Networking patterns for Azure Service Fabric
...s/service-fabric/service-fabric-patterns-networking.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page provides only PowerShell-based deployment examples and references Windows tools (e.g., RDP, Windows command prompt for ping), with no equivalent Linux/macOS CLI (such as Azure CLI or Bash) examples. Windows-centric terminology and patterns are presented first and exclusively, creating friction for Linux/macOS users who may not use PowerShell or RDP.
Recommendations
- Add Azure CLI (az) command examples alongside PowerShell for template deployments, resource creation, and querying.
- Provide Linux/macOS-friendly instructions for accessing VMs (e.g., SSH instead of RDP), and for network testing (e.g., ping from Bash shell).
- Explicitly mention cross-platform options for template deployment and management, clarifying that PowerShell is not required.
- Where Windows command prompt examples are given (e.g., ping), add Bash equivalents.
- Consider including a note at the start clarifying that all examples can be adapted for Linux/macOS users, and link to relevant cross-platform Azure documentation.
Service Fabric
Add custom Service Fabric health reports
...rticles/service-fabric/service-fabric-report-health.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page for 'Add custom Service Fabric health reports' demonstrates a notable Windows bias. PowerShell is used extensively for command-line examples, and all CLI examples are given in PowerShell syntax with Windows-style prompts (PS C:\>). There is no mention of Linux/macOS equivalents, such as Bash or Azure CLI, nor are cross-platform command-line tools referenced. Windows tools and patterns (PowerShell) are presented before REST API options, and no Linux-specific guidance is provided.
Recommendations
- Add equivalent Bash or Azure CLI examples for health reporting, especially for REST and cluster management tasks.
- Clarify whether PowerShell cmdlets are available cross-platform (e.g., via PowerShell Core), and provide guidance for Linux/macOS users.
- Explicitly mention how Linux-based Service Fabric clusters can report health, including any limitations or differences.
- Consider reordering sections so that REST API examples (which are platform-neutral) are presented before PowerShell.
- Add notes about cross-platform support for Service Fabric tooling, and link to relevant Linux/macOS documentation.
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 â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation consistently references PowerShell cmdlets (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica, Get-ServiceFabricReplica) as the primary or sole method for interacting with the replica soft delete feature. There are no CLI, REST, or Linux-native examples or references, and the use of PowerShell is assumed throughout. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other tooling.
Recommendations
- Include equivalent examples using Service Fabric CLI (sfctl) or REST APIs, if available, alongside PowerShell examples.
- Explicitly mention if the PowerShell cmdlets are cross-platform (e.g., available in PowerShell Core on Linux/macOS), or provide guidance for Linux/macOS users.
- Document FabricClient API usage with code snippets in a cross-platform language (e.g., C#/.NET Core, Python) to show how to invoke the same operations programmatically.
- Clarify any platform limitations (e.g., if certain APIs are only available on Windows nodes) to set expectations for non-Windows users.
Service Fabric
Specifying Service Fabric service endpoints
...ce-fabric/service-fabric-service-manifest-resources.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides a PowerShell example for deploying Service Fabric applications, which is Windows-centric. The schema file path is given only for Windows (C:\Program Files\Microsoft SDKs\Service Fabric\schemas\ServiceFabricServiceModel.xsd), and PowerShell is referenced as the tool for deployment, with no Linux CLI or Bash equivalent shown. While there is a brief mention of Linux certificate storage, Linux deployment workflows are not demonstrated.
Recommendations
- Add equivalent Linux/macOS deployment examples using Azure CLI or Bash scripts.
- Mention the location of schema files for Linux installations, if applicable.
- Provide guidance for Linux users on how to deploy Service Fabric applications (e.g., using sfctl or Azure CLI).
- Ensure that references to tools (like PowerShell) are accompanied by cross-platform alternatives.
Service Fabric
Fault Analysis Service overview
.../service-fabric/service-fabric-testability-overview.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page provides usage examples for C# and PowerShell, but does not mention or provide equivalent examples for Linux/macOS command-line tools or scripting environments (such as Bash or CLI). The PowerShell example assumes a Windows environment and references the Service Fabric SDK, which is primarily Windows-focused. There is no mention of Linux-native tools or how to use the Fault Analysis Service from Linux/macOS, despite Service Fabric supporting Linux clusters.
Recommendations
- Add examples for using the Fault Analysis Service from Linux/macOS environments, such as via Bash scripts, Azure CLI, or REST API.
- Clarify whether the PowerShell module is available and supported on Linux (via PowerShell Core), or provide alternative instructions for Linux users.
- Mention any prerequisites or limitations for Linux clusters, and provide guidance for Linux developers on how to access Fault Analysis Service features.
- Ensure parity in documentation by including Linux/macOS-specific instructions alongside Windows/PowerShell examples.
Service Fabric
Configure the upgrade of a Service Fabric application
...abric/service-fabric-visualstudio-configure-upgrade.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation is heavily focused on Windows tools, specifically Visual Studio and PowerShell, for configuring and upgrading Service Fabric applications. All examples and workflows reference Windows-centric tools, with no mention of Linux/macOS alternatives or cross-platform CLI usage. Linux users are not provided with equivalent instructions or examples, creating friction for those not on Windows.
Recommendations
- Add instructions and examples for upgrading Service Fabric applications using Azure CLI or REST API, which are cross-platform.
- Mention and link to any Linux-compatible Service Fabric tooling or workflows, such as sfctl.
- Clarify which steps are Windows-only and provide Linux/macOS alternatives where possible.
- Include sample commands and manifest edits using Linux shell syntax where relevant.
Virtual Machines
Create and upload an Ubuntu Linux VHD in Azure
...rticles/virtual-machines/linux/create-upload-ubuntu.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page, while focused on Ubuntu Linux VHD creation for Azure, exhibits notable Windows bias. Hyper-V (a Windows-only virtualization tool) is referenced as the primary example for creating VHDs, with links to Windows documentation. Steps involving VM management and VHD conversion are described using Hyper-V Manager and the Convert-VHD PowerShell cmdlet, with no Linux-native alternatives (such as qemu-img or KVM) provided. Windows tools and patterns are mentioned first and exclusively in several critical steps, creating friction for Linux/macOS users.
Recommendations
- Add Linux-native instructions for creating and managing VHDs (e.g., using qemu-img, KVM, or VirtualBox).
- Provide Linux/macOS alternatives for VHD conversion (e.g., qemu-img convert).
- Include steps for shutting down or managing VMs using Linux tools (e.g., virsh, virt-manager).
- Reorder examples so Linux-native tools are presented first or alongside Windows tools.
- Clarify that Hyper-V and Convert-VHD are Windows-specific, and link to Linux/macOS equivalents.
Virtual Machines
Create and upload a Red Hat Enterprise Linux VHD for use in Azure
...les/virtual-machines/linux/redhat-create-upload-vhd.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation provides comprehensive instructions for creating and uploading a Red Hat Enterprise Linux VHD for Azure, covering multiple hypervisors (Hyper-V, KVM, VMware, Kickstart). However, there is a notable Windows bias: Hyper-V (a Windows-only tool) is presented first in nearly every major section and is referenced as the primary example for VM creation and disk conversion. Windows tools and terminology (e.g., Hyper-V Manager, PowerShell cmdlets like 'convert-vhd') are mentioned before their Linux equivalents. Linux/KVM/VMware instructions are present and detailed, but the ordering and framing prioritize Windows/Hyper-V scenarios.
Recommendations
- Reorder sections so that Linux-native hypervisors (KVM, VMware, Kickstart) are presented before or alongside Hyper-V, especially since the audience is preparing Linux VMs.
- Where disk conversion is discussed, mention Linux tools (e.g., qemu-img) before or alongside Windows tools (e.g., Hyper-V Manager, convert-vhd).
- Clarify that Hyper-V steps are only required if using Windows, and highlight Linux-native workflows for users on Linux/macOS.
- Consider a summary table at the top showing all supported hypervisors and their OS requirements, helping users quickly find relevant instructions.
- Ensure that Linux/KVM/VMware instructions are equally prominent and not referenced as secondary or 'see also' content.
Virtual Machines
Create an Azure Image Builder Bicep file or ARM template JSON template
.../articles/virtual-machines/linux/image-builder-json.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation provides both Linux and Windows coverage for Azure Image Builder, including examples for shell and PowerShell customizers, and validation steps. However, there is a notable Windows bias in several areas: PowerShell and Windows-specific tools (e.g., Get-FileHash, Invoke-WebRequest, Sysprep) are referenced more frequently and often before Linux equivalents; PowerShell commands for checksum generation and image operations are shown alongside Azure CLI, but Windows tools are sometimes mentioned first. Some customizers (WindowsRestart, WindowsUpdate) are Windows-only, but this is appropriate given their OS specificity. Linux examples are present but occasionally less detailed or appear after Windows examples.
Recommendations
- Ensure Linux tools and commands (e.g., sha256sum, wget/curl) are mentioned equally and before or alongside Windows tools in relevant sections.
- Where PowerShell is referenced for checksum generation, provide Linux/Mac equivalents (sha256sum) with equal prominence.
- For image build/cancel operations, show Azure CLI examples first or highlight their cross-platform nature.
- In sections where Windows-specific customizers are described, clarify that Linux alternatives (e.g., Shell customizer for reboots) are not available and suggest workarounds if possible.
- Expand Linux example coverage where possible, ensuring parity in detail and visibility.
Virtual Machines
Run scripts in a Linux VM in Azure using managed Run Commands
...articles/virtual-machines/linux/run-command-managed.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
powershell_heavy
windows_first
missing_linux_example
Summary
While the page is intended for Linux VMs, there is notable Windows bias in the documentation. PowerShell (Set-AzVMRunCommand, etc.) is heavily featured alongside Azure CLI, and many examples and notes reference Windows-specific tools, parameters, and patterns. Some examples use Windows-centric terminology (e.g., 'ipconfig' as a commandId, PowerShell script references in REST/ARM templates), and PowerShell is presented as a primary management method, even though Linux users are more likely to use Azure CLI or native Linux tools. There are also sections where Windows behaviors are described before Linux equivalents, and some REST/ARM examples use PowerShell scripts instead of shell scripts.
Recommendations
- Prioritize Azure CLI and Bash examples for Linux-focused documentation, and move PowerShell examples to a secondary position or a dedicated section.
- Ensure all REST/ARM template examples use shell scripts (e.g., 'echo Hello World!' or bash scripts) rather than PowerShell scripts.
- When referencing commandIds, use Linux-relevant commands (e.g., 'ifconfig') rather than Windows ones like 'ipconfig'.
- Clarify in notes and parameter explanations when a behavior is Windows-only, and provide Linux-specific guidance first.
- Where PowerShell is shown, explicitly note that it is cross-platform (if so), or provide Bash/CLI equivalents.
- Review all examples and ensure that Linux users can follow them without needing to interpret or translate Windows/PowerShell-specific instructions.
Virtual Machines
Share VM images in a compute gallery
...in/articles/virtual-machines/shared-image-galleries.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation covers both Windows and Linux VM images, but there are several signs of Windows bias. PowerShell examples and references are prominent and often appear before or alongside CLI examples, with some features and links (e.g., finding Marketplace images, uploading VHDs, creating specialized images) referencing Windows-specific pages first or exclusively. In some cases, Linux equivalents are mentioned but not always with equal detail or visibility. The FAQ and example sections tend to show Windows/PowerShell usage before Linux/CLI, and some links default to Windows guides.
Recommendations
- Ensure that Linux/CLI examples are provided wherever PowerShell/Windows examples are shown, and present them with equal prominence.
- When referencing guides or tutorials (e.g., uploading VHDs, creating specialized images), link to both Windows and Linux versions side-by-side, or use a neutral landing page.
- In tables and lists, alternate the order of Windows and Linux examples or group them together to avoid implicit prioritization.
- Expand Linux-specific troubleshooting, examples, and links to match the depth of Windows coverage.
- Review FAQ answers and ensure Linux scenarios are addressed with equal clarity and detail.
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_tools
powershell_heavy
windows_first
Summary
The documentation page for Service Fabric application and service manifest examples shows minor Windows bias. There are references to Windows-specific tools (e.g., 'ServiceFabric PowerShell module'), Windows account types (e.g., 'NetworkService', 'Administrators'), and scripts (e.g., 'Setup.bat'), with no equivalent Linux examples or explicit mention of Linux-compatible approaches. Windows terminology and tools are referenced first and exclusively, even though Service Fabric supports Linux clusters and .NET Core workloads.
Recommendations
- Add Linux-specific examples, such as using shell scripts (.sh) instead of batch files (.bat) for SetupEntryPoint.
- Mention Linux account types and how RunAsPolicy works on Linux clusters.
- Reference Linux deployment tools (e.g., Azure CLI, Bash) alongside PowerShell.
- Clarify which manifest features are cross-platform and which are Windows-only.
- Provide guidance or links for Linux users on adapting the manifest for Linux clusters.
Service Fabric
Overview of Azure Service Fabric
...ain/articles/service-fabric/service-fabric-overview.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation mentions both Windows and Linux support for Azure Service Fabric, but Windows development tools (Visual Studio and PowerShell) are listed before Linux equivalents (Eclipse, Yeoman). No explicit PowerShell-heavy examples or Windows-only tools are present, and Linux is acknowledged as a supported platform. However, the ordering and phrasing subtly prioritize Windows development.
Recommendations
- Present Windows and Linux development options in parallel, rather than listing Windows first.
- Explicitly mention .NET Core support for Linux alongside .NET SDK for Windows.
- Provide links to both Windows and Linux quickstart guides in the 'Next steps' section.
- Ensure examples and tooling references are balanced between Windows and Linux.
Service Fabric
Learn Azure Service Fabric terminology
...es/service-fabric/service-fabric-technical-overview.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation page is generally cross-platform, but there are subtle signs of Windows bias. Windows-specific terminology and tools (such as references to Windows services and EXE/DLL files) are mentioned first or exclusively in some sections, particularly in the 'Node' and 'Code package' definitions. The description of node startup references only Windows services and executables, and the code package section assumes EXE/DLL files as typical, which are Windows-centric. However, Linux support is acknowledged in container and guest executable sections, and the overall content is mostly platform-neutral.
Recommendations
- Clarify that node startup processes and equivalents exist for Linux, not just Windows services.
- When describing code packages, mention typical Linux binaries (e.g., ELF files, .so libraries) alongside EXE/DLL files.
- Provide explicit examples or references for Linux-specific deployment and operational patterns where relevant.
- Ensure that descriptions of Service Fabric internals (such as FabricHost.exe) note Linux equivalents or clarify if Windows-only.
- Review ordering of examples and terminology to avoid always mentioning Windows first.
Virtual Machine Scale Sets
Attach or detach a virtual machine to or from a Virtual Machine Scale Set
...le-sets/virtual-machine-scale-sets-attach-detach-vm.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all major operations (attach, detach, move), but consistently lists Azure PowerShell examples after Azure CLI and before any Linux-specific guidance. There are no explicit Linux/macOS shell examples beyond Azure CLI, and PowerShell is presented as a primary scripting option, which is more relevant to Windows users. However, Azure CLI is cross-platform and the examples use Ubuntu images, so Linux users are not blocked.
Recommendations
- Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and are recommended for cross-platform use.
- Consider providing Bash shell script examples for common operations, or clarify that Azure CLI is the preferred tool for Linux/macOS.
- Mention that PowerShell Core is available cross-platform, but highlight Azure CLI as the default for Linux/macOS users.
- Ensure that CLI examples do not assume Windows-specific conventions (e.g., backslashes for line continuation).
Virtual Machines
Associate a virtual machine to a capacity reservation group
.../virtual-machines/capacity-reservation-associate-vm.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
arm_template_windows_only
Summary
The documentation covers both Windows and Linux VMs, but exhibits mild Windows bias in several areas. PowerShell examples are provided throughout, and the ARM template section only demonstrates Windows VM deployment. Windows-specific parameters (e.g., OSVersion) are prominent in the ARM template, and Windows images are used by default. In some sections, Windows terminology and tools (PowerShell, Windows image references) appear before or more prominently than Linux equivalents, despite the CLI examples using Ubuntu images.
Recommendations
- Add a Linux-focused ARM template example, or clarify how to modify the template for Linux VM deployment (e.g., show publisher/offer/sku for Ubuntu or other distributions).
- Balance PowerShell and CLI coverage by ensuring both are equally prominent and by mentioning Bash or shell scripting where relevant.
- In ARM template parameters, include both Windows and Linux image options, or add guidance for Linux users.
- Where Windows terminology appears first (e.g., administrator account password requirements, OSVersion), clarify applicability to Linux or provide Linux-specific guidance.
- Consider alternating CLI and PowerShell order, or explicitly state that both Windows and Linux are supported for all command-line examples.
Virtual Machines
Create an image definition and image version
...s/blob/main/articles/virtual-machines/image-version.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Linux and Windows guidance, but there is a mild Windows bias in example ordering and PowerShell usage. In the PowerShell section, Windows is shown first in the example, with Linux mentioned as an alternative. PowerShell is also presented as a primary scripting option, which is more native to Windows. However, CLI and REST examples are provided and are OS-neutral, and Linux-specific guidance is linked in the 'Before you begin' section.
Recommendations
- In PowerShell examples, show Linux as the primary example or provide parallel Linux and Windows examples.
- Explicitly state that PowerShell can be used on Linux/macOS, or recommend Azure CLI for cross-platform users.
- Ensure that Linux and Windows are treated equally in example ordering and explanations.
- Add notes or links about using PowerShell Core on Linux/macOS where PowerShell is referenced.
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for checking vCPU quotas. However, PowerShell is highlighted as a primary method alongside CLI, and its inclusion may create friction for Linux/macOS users, as PowerShell is traditionally Windows-centric (though now cross-platform). The CLI example is shown first, which is positive, but the PowerShell section is equally prominent and may imply parity between CLI and PowerShell usage, despite CLI being more native to Linux/macOS environments.
Recommendations
- Clarify that Azure CLI is the recommended cross-platform tool for Linux/macOS users.
- Add a note that PowerShell is available cross-platform, but CLI is more commonly used on Linux/macOS.
- Consider providing Bash script examples or highlighting CLI usage for automation on Linux.
- Ensure that CLI instructions are comprehensive and cover all relevant use cases.
Service Fabric
Azure Service Fabric container image management
.../articles/service-fabric/container-image-management.md
Low Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation mentions Windows container base images (microsoft/windowsservercore, microsoft/nanoserver) as defaults in the 'ContainerImagesToSkip' setting, but does not mention Linux base images or provide Linux-specific examples. There are no explicit Linux container image examples or guidance, and the examples focus on Windows images first.
Recommendations
- Add examples showing how to skip common Linux base images (e.g., 'docker.io/library/ubuntu', 'docker.io/library/alpine').
- Clarify that the container image management applies to both Windows and Linux containers, if applicable.
- Provide sample settings or scenarios for Linux container deployments.
- Mention any differences in cleanup behavior between Windows and Linux containers, if relevant.
Service Fabric
Azure Service Fabric security best practices
...rvice-fabric/service-fabric-best-practices-security.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Windows and Linux guidance for most security best practices, including certificate creation and secret encryption. However, Windows-specific tools (PowerShell, Windows Defender, Azure DSC) are often mentioned first or exclusively, and Windows examples (PowerShell commands) are presented before Linux equivalents. Some sections (Windows Defender, Windows security baselines) are Windows-only, but these are clearly marked and do not impact Linux users. Overall, Linux parity is good, but Windows bias is evident in ordering and tool references.
Recommendations
- Present Linux and Windows examples side-by-side or alternate their ordering to avoid Windows-first bias.
- Where possible, mention Linux equivalents (e.g., for Azure DSC, reference Ansible or other Linux configuration tools).
- Clarify when a section is Windows-only and provide links to Linux alternatives if available.
- Expand Linux-specific guidance where possible, such as recommended Linux security baselines or antivirus solutions.
- Ensure PowerShell and Windows tool references are balanced with Linux command-line and tool examples.
Service Fabric
Describe a cluster by using Cluster Resource Manager
...ce-fabric-cluster-resource-manager-cluster-description.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation provides configuration examples for both Windows (ClusterManifest.xml) and cross-platform/standalone (ClusterConfig.json) deployments. However, Windows-specific configuration (ClusterManifest.xml under <WindowsServer>) is consistently presented first, and PowerShell examples are included for service creation and updates without Linux CLI or script equivalents. There is a mild bias toward Windows tools and patterns, but Linux/standalone parity is generally maintained via JSON examples and explanations.
Recommendations
- Add Linux CLI (e.g., Bash, Azure CLI) examples for service creation and updates alongside PowerShell examples.
- Clarify that PowerShell commands can be run on Linux via PowerShell Core, or provide equivalent commands using cross-platform tools.
- Consider presenting cross-platform (ClusterConfig.json) examples before or alongside Windows-specific (ClusterManifest.xml) examples.
- Explicitly mention Linux/macOS support for standalone Service Fabric clusters where relevant.
Service Fabric
Package an existing executable to Azure Service Fabric
...abric/service-fabric-guest-executables-introduction.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page exhibits mild Windows bias. The directory structure example uses a Windows-style .exe file (existingapp.exe), and the schema definition path is given only in Windows format (C:\Program Files\Microsoft SDKs\Service Fabric\schemas\ServiceFabricServiceModel.xsd). There are references to Visual Studio as a packaging tool, but no mention of Linux/macOS equivalents or cross-platform CLI tools. No Linux/macOS-specific examples or file paths are provided.
Recommendations
- Add examples using Linux/macOS file paths and executable formats (e.g., existingapp, not just existingapp.exe).
- Mention cross-platform tools or CLI alternatives to Visual Studio for packaging and deploying guest executables.
- Provide information about where schema files are located on Linux/macOS, if available.
- Include sample directory structures and manifest file references using Linux/macOS conventions.
- Clarify if Service Fabric SDK and guest executable packaging are supported on Linux/macOS, and provide guidance if so.
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
windows_tools
Summary
The documentation provides a balanced overview of Service Fabric container support for both Linux and Windows. However, there is a slight bias in mentioning Windows container runtimes and tools in more detail, and Windows scenarios (such as IIS lift-and-shift) are described before Linux equivalents. Windows tutorials and links are sometimes listed before Linux ones, and Windows-specific tools (Mirantis Container Runtime, DockerEE) are highlighted, while Linux only mentions Docker generically.
Recommendations
- Ensure Linux and Windows tutorials/examples are presented together or alternate their order to avoid 'windows_first' bias.
- Expand Linux-specific scenarios and examples, such as using NGINX or other common Linux workloads, to match the detail given to Windows/IIS scenarios.
- Mention Linux container runtimes and tools (e.g., containerd, Podman) if relevant, not just Docker.
- Provide parity in describing container isolation mechanisms for Linux (cgroups, namespaces) alongside Windows/Hyper-V explanations.
- Add links to Linux container documentation and quickstarts with equal prominence as Windows links.
Service Fabric
Service communication with the ASP.NET Core
...vice-fabric-reliable-services-communication-aspnetcore.md
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation provides comprehensive guidance for both Kestrel (cross-platform) and HTTP.sys (Windows-only) web servers in Service Fabric Reliable Services. While Kestrel is recommended and well-documented for cross-platform (Linux/Windows) scenarios, HTTP.sys (a Windows-only technology) is also described in detail, with its limitations on non-Windows platforms clearly stated. In some sections, Windows-specific tools and patterns (such as HTTP.sys and netsh) are mentioned before their Linux equivalents or alternatives, and Windows-specific configuration is sometimes described first. However, the documentation does not omit Linux support and generally recommends Kestrel for cross-platform use.
Recommendations
- When introducing HTTP.sys, explicitly state up front that it is Windows-only and direct Linux/macOS users to Kestrel before providing HTTP.sys details.
- In code and configuration examples, consider showing Kestrel (cross-platform) examples first, or in parallel with HTTP.sys, to reinforce Linux parity.
- Where Windows-specific tools (like netsh) are mentioned, briefly note that these are not required for Kestrel or on Linux.
- Add a short summary table or section at the top clarifying which features are cross-platform and which are Windows-only.
- Ensure that all critical scenarios (stateless/stateful, internal/external) have Kestrel-based examples and guidance shown first or equally.
Service Fabric
Reliable Collection object serialization
...c-reliable-services-reliable-collections-serialization.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation is generally platform-neutral, focusing on .NET serialization concepts relevant to Azure Service Fabric Reliable Collections. However, in the 'Next steps' section, Windows-centric tools (Visual Studio and PowerShell) are mentioned for application upgrades, with no Linux/macOS alternatives or parity (e.g., CLI or Bash examples). The main content does not reference Windows-specific tools or patterns, but the ordering and selection of upgrade tutorials may create friction for non-Windows users.
Recommendations
- Add links or references to cross-platform upgrade methods, such as using Azure CLI or Bash scripts, if available.
- Clarify whether PowerShell examples are compatible with PowerShell Core on Linux/macOS, or provide alternative instructions.
- Consider mentioning Visual Studio Code or other cross-platform IDEs for application upgrades.
- Explicitly state if certain upgrade methods are Windows-only, and provide Linux/macOS alternatives where possible.
Virtual Machine Scale Sets
Enable Automatic Zone Balance on Virtual Machine Scale Sets (Preview)
...virtual-machine-scale-sets/auto-zone-balance-enable.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for all major operations, but PowerShell examples are consistently presented after Azure CLI, and not before. However, in the PowerShell examples, the Application Health extension is shown using the Windows extension type ('ApplicationHealthWindows'), while the CLI example uses 'ApplicationHealthLinux'. This could cause confusion for Linux users following the PowerShell path. There are no Linux/macOS-specific command-line gaps, and all features are accessible via cross-platform tools (Azure CLI, REST API, Portal).
Recommendations
- In PowerShell examples, clarify when to use 'ApplicationHealthWindows' vs. 'ApplicationHealthLinux' for the extension type, or provide both variants.
- Add a note that Azure PowerShell is cross-platform, but that the extension type should match the VM OS.
- Consider mentioning that Azure CLI is available on Windows, Linux, and macOS, and is recommended for Linux/macOS users.
- Ensure that Linux-specific extension types are shown in PowerShell examples when the VM image is Linux.
Virtual Machine Scale Sets
Custom metrics for rolling upgrades on Virtual Machine Scale Sets
...tual-machine-scale-sets-rolling-upgrade-custom-metrics.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation provides both Linux and Windows examples for configuring the application health extension and custom metrics, but there is a mild Windows bias in several areas. In the 'Install the application health extension' section, PowerShell (Windows) and Azure CLI (cross-platform) are both shown, but REST and PowerShell examples use 'ApplicationHealthWindows' as the extension type, while CLI uses 'ApplicationHealthLinux'. In the sample application section, both Bash (Linux) and PowerShell (Windows) scripts are given, but the PowerShell example is more elaborate and prominent. Throughout, Windows tools (PowerShell) are consistently presented alongside cross-platform tools, sometimes before Linux alternatives. However, Linux parity is generally maintained, and the documentation is not Windows-only.
Recommendations
- Ensure that all examples for extension installation and configuration explicitly show both 'ApplicationHealthLinux' and 'ApplicationHealthWindows' types, with clear guidance for each OS.
- Where PowerShell and Bash examples are given, ensure both are equally detailed and prominent.
- In REST API examples, provide sample payloads for both Linux and Windows extension types.
- Where possible, present CLI (cross-platform) examples before PowerShell (Windows-only) examples.
- Add clarifying notes about OS-specific extension types and commands to help users select the correct option.
Virtual Machine Scale Sets
Migrate deployments and resources to Virtual Machine Scale Sets in Flexible orchestration
...lexible-virtual-machine-scale-sets-migration-resources.md
Low Priority
View Details â
Detected Bias Types
windows_first
minor_windows_tools
Summary
The documentation provides migration guidance for Azure Virtual Machine Scale Sets in Flexible orchestration. While the content is generally platform-neutral, there are a few minor instances of Windows bias: Windows/PowerShell is mentioned alongside Azure CLI and ARM templates, and Windows-specific scenarios (such as Windows VM activation and Windows updates) are listed before Linux equivalents. However, Linux scenarios (e.g., access to Linux package managers) are also mentioned, and most examples use Azure CLI, which is cross-platform.
Recommendations
- Ensure Linux-specific migration scenarios (such as package manager access) are given equal prominence and detail as Windows scenarios.
- Where PowerShell is referenced, provide Bash/Linux shell equivalents or clarify that Azure CLI is recommended for cross-platform users.
- When listing common outbound connectivity scenarios, alternate the order or group Windows and Linux examples together to avoid 'windows_first' bias.
- Consider including explicit Linux migration examples or references to Linux documentation where relevant.
Virtual Machine Scale Sets
Configure rolling upgrades on Virtual Machine Scale Sets
...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-configure-rolling-upgrades.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for all operations, but PowerShell is featured equally alongside CLI and is presented in a way that may imply parity. However, PowerShell is a Windows-centric tool, and no explicit Linux/macOS shell examples (e.g., Bash, shell scripting) are given. The CLI examples are cross-platform, but PowerShell is given its own section and is not clearly marked as Windows-only. Additionally, in some sections, PowerShell appears immediately after CLI, which may subtly prioritize Windows tools.
Recommendations
- Clarify that PowerShell examples are intended for Windows users, and Azure CLI is cross-platform.
- Consider adding explicit Bash or shell script examples where relevant, or note that Azure CLI commands can be run in Bash, Zsh, or other Linux/macOS shells.
- In tabbed sections, consider labeling PowerShell as '(Windows)' and CLI as '(cross-platform)' to reduce ambiguity.
- If possible, add notes for Linux/macOS users about installing and using Azure CLI, and link to relevant documentation.
- Ensure that CLI examples are always shown first, or at least clarify their cross-platform nature.
Virtual Machine Scale Sets
Networking for Azure Virtual Machine Scale Sets
...ne-scale-sets/virtual-machine-scale-sets-networking.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for most tasks, but PowerShell (a Windows-centric tool) is often presented before CLI, and some sections (such as querying public IPs) show PowerShell examples before CLI or in greater detail. Portal instructions are also included, but there is no explicit Linux/macOS shell example or mention of Bash scripting, and PowerShell is referenced as a primary scripting method. However, Azure CLI (cross-platform) is present throughout, and ARM templates are used for platform-neutral configuration.
Recommendations
- Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and more accessible to Linux/macOS users.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
- Add Bash shell scripting examples where relevant, especially for tasks like querying public IPs.
- Where PowerShell is used, clarify that Azure CLI is the recommended tool for Linux/macOS users.
- Ensure parity in detail between PowerShell and CLI examples (e.g., if PowerShell shows multiple query methods, show equivalent CLI methods).
Virtual Machine Scale Sets
Orchestration modes for Virtual Machine Scale Sets in Azure
...sets/virtual-machine-scale-sets-orchestration-modes.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation is generally cross-platform and describes orchestration modes for Azure Virtual Machine Scale Sets, which support both Linux and Windows VMs. However, there is a minor bias in the example command for assigning a fault domain during VM creation, which uses Azure CLI syntax but does not explicitly show Linux shell or PowerShell alternatives. Additionally, some links reference Windows-specific managed identity configuration, but the overall guidance applies to both Linux and Windows. Windows is mentioned first in some mixed OS contexts, but Linux parity is maintained.
Recommendations
- Provide explicit Linux shell and PowerShell examples for Azure CLI commands where relevant.
- Clarify that Azure CLI commands work on both Linux and Windows platforms.
- When referencing managed identity documentation, include links for both Linux and Windows VMSS setup.
- Ensure that mixed OS examples alternate the order (e.g., 'Linux and Windows' vs. 'Windows and Linux') to avoid subtle ordering bias.
Virtual Machine Scale Sets
Create an Azure scale set that uses Availability Zones
...s/virtual-machine-scale-sets-use-availability-zones.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for creating and updating scale sets with Availability Zones. However, PowerShell examples are given equal prominence to CLI, and in some sections (such as 'Use Azure PowerShell'), PowerShell is presented before Linux-specific guidance. Additionally, the CLI examples use --generate-ssh-keys, which is Linux-centric, but there is no explicit mention of Linux/macOS compatibility or shell-specific instructions. The Resource Manager template section references both Linux and Windows getting started articles, but the PowerShell section could be perceived as Windows-centric due to its prominence and detail.
Recommendations
- Ensure that Azure CLI examples are presented before PowerShell, as CLI is cross-platform and more relevant for Linux/macOS users.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide shell-specific notes if needed.
- Add bash/zsh shell example blocks where appropriate, especially for update operations.
- Clarify that PowerShell is primarily for Windows users, and recommend CLI for Linux/macOS.
- Consider adding a short section or note about Linux/macOS compatibility for each method.
Virtual Machines
Instantly access managed disk snapshots
...les/virtual-machines/disks-instant-access-snapshots.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides both Azure CLI (bash-style) and Azure PowerShell examples for creating instant access snapshots, but does not include explicit Linux/macOS-specific instructions or examples (e.g., Bash shell, Python SDK, or REST API). PowerShell is presented as a primary scripting option alongside Azure CLI, and Windows-centric tools (PowerShell, Portal) are given equal or greater prominence. There are no Linux-specific troubleshooting tips or parity notes. The CLI examples use Bash syntax, but there is no explicit mention of Linux/macOS compatibility or alternative shells.
Recommendations
- Add explicit Bash shell examples and clarify that Azure CLI commands are cross-platform (Linux/macOS/Windows).
- Include REST API or Python SDK examples for snapshot creation and state monitoring, which are platform-neutral.
- Mention any OS-specific considerations (e.g., file path handling, authentication) for Linux/macOS users.
- Ensure that CLI examples are tested and work on Linux/macOS, and note any differences if present.
- Consider adding troubleshooting or tips for Linux environments (e.g., environment variable handling, az CLI installation).
Virtual Machines
Azure Key Vault VM Extension for Linux
...rticles/virtual-machines/extensions/key-vault-linux.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation is focused on the Azure Key Vault VM Extension for Linux and provides extensive Linux-specific details. However, in deployment and troubleshooting sections, Azure PowerShell examples are given first and in greater detail, with CLI examples following. There are warnings and troubleshooting steps that reference PowerShell-specific issues, and PowerShell is used as the primary deployment method before CLI, which is more cross-platform. There are no missing Linux examples, and all file paths, certificate handling, and operational details are Linux-centric.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and native for Linux users.
- Add explicit notes clarifying that PowerShell is optional and not required for Linux users.
- Expand troubleshooting steps to include CLI commands and not just PowerShell.
- Where PowerShell-specific warnings are given, provide equivalent CLI guidance for Linux users.
- Consider removing or minimizing PowerShell deployment instructions, or move them to a separate section for Windows administrators.
Virtual Machines
Deprovision or generalize a VM before creating an image
...docs/blob/main/articles/virtual-machines/generalize.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides clear, separate instructions for both Linux and Windows VM generalization. However, the Windows section includes more detailed prerequisites and troubleshooting steps, and Windows PowerShell/Command Prompt examples are shown before Linux equivalents in some sections. The Windows example for marking a VM as generalized uses PowerShell, while the Linux example uses Azure CLI, potentially causing friction for cross-platform users. Overall, Linux instructions are present and functional, but Windows receives slightly more attention and detail.
Recommendations
- Ensure Linux and Windows sections have parity in detail and troubleshooting guidance.
- Provide Azure CLI examples for Windows VM generalization, not just PowerShell.
- Consider presenting Linux and Windows instructions in parallel or with equal prominence.
- Add troubleshooting tips for Linux deprovisioning similar to those given for Windows Sysprep.
Virtual Machines
Azure VM Extensions and Features for Linux
...articles/virtual-machines/extensions/features-linux.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell examples throughout, but PowerShell examples are always given alongside CLI and never omitted. However, PowerShell is featured equally and sometimes before CLI, despite the Linux focus. The documentation references Azure PowerShell as a primary tool for managing Linux VM extensions, which is more commonly used on Windows. There are no missing Linux examples, and all sample scripts and ARM templates are Linux-centric. The severity of bias is low, as Linux users can complete all tasks using CLI, ARM templates, or portal, but the prominence of PowerShell may cause minor confusion or friction.
Recommendations
- Feature Azure CLI examples before Azure PowerShell examples, as CLI is the cross-platform default for Linux users.
- Clarify that Azure PowerShell is optional and primarily for users who prefer it, not required for Linux VM management.
- Consider grouping CLI and PowerShell examples under clear tabs, with CLI as the default/first tab.
- Add explicit notes that Azure CLI is recommended for Linux/macOS environments.
- Review and minimize references to PowerShell unless necessary for parity.
Virtual Machines
NVIDIA GPU Driver Extension - Azure Linux VMs
...es/virtual-machines/extensions/hpccompute-gpu-linux.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation is clearly focused on Linux VMs, with extensive Linux-specific instructions and examples. However, PowerShell examples are provided alongside Azure CLI and ARM template examples, and PowerShell is mentioned before Azure CLI in the deployment section. There are no missing Linux examples or Windows-only tools, but the ordering and inclusion of PowerShell (a Windows-centric tool) may create minor friction for Linux users.
Recommendations
- Move Azure CLI examples before PowerShell examples, as Azure CLI is more commonly used on Linux.
- Clarify that PowerShell examples are optional and primarily for users on Windows or cross-platform PowerShell Core.
- Consider providing Bash script examples for common deployment scenarios.
- Explicitly note that Azure CLI is the recommended tool for Linux users.
Virtual Machines
HBv3-series virtual machine (VM) overview, architecture, topology - Azure Virtual Machines | Microsoft Docs
...main/articles/virtual-machines/hbv3-series-overview.md
Low Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation is largely cross-platform and includes both Linux and Windows support. However, there is a subtle Windows-first bias: the 'Recommended OS for Performance' is listed as 'Windows Server 2019+' without a Linux equivalent, and the temporary storage section uses the term 'page file' (a Windows concept) without mentioning the Linux swap partition. While Linux tools (like lstopo) are shown, there are no Windows equivalents or instructions for Windows users to inspect NUMA topology, which could be a minor omission for parity.
Recommendations
- In the 'Recommended OS for Performance' row, also recommend a specific Linux distribution/version for optimal performance (e.g., RHEL 8.x, Ubuntu 20.04+).
- In the temporary storage section, clarify the equivalent Linux concept (e.g., swap partition) alongside 'page file'.
- If possible, provide Windows-native tooling or instructions (e.g., using 'coreinfo' or Windows System Information) for inspecting NUMA topology, or explicitly state that such tools are not available if that's the case.
- Ensure that examples and recommendations are balanced for both Linux and Windows, especially in sections where performance tuning or system inspection is discussed.
Virtual Machines
Time sync for Linux VMs in Azure
...blob/main/articles/virtual-machines/linux/time-sync.md
Low Priority
View Details â
Detected Bias Types
windows_reference
powershell_example
Summary
The documentation is focused on Linux VM time synchronization in Azure and provides Linux-centric guidance, commands, and examples. However, it references Windows Server 2016 improvements and links to Windows documentation in the introduction and conclusion. Additionally, a PowerShell example is provided for base64 encoding a cloud-init file, which is a Windows-centric tool, even though the rest of the guidance is Linux-focused.
Recommendations
- Move Windows references to a background section or footnote, clarifying their relevance to Linux VM time sync.
- Provide a Linux equivalent for the PowerShell base64 encoding example, such as using 'base64' or 'openssl' on Linux.
- Ensure that all examples and tooling instructions are available for Linux users, especially for tasks like preparing cloud-init files.
- Clarify that the PowerShell example is optional and provide context for users on non-Windows platforms.