1642
Pages Scanned
477
Pages Flagged
1642
Changed Pages
29.0%
% Pages Flagged
Scan Information
Started At: 2026-01-12 00:00:07
Finished At: 2026-01-12 07:14:27
Status: completed
Target Repo: Azure Compute
Current Phase: discovery
Files Queued: 1642
Files Completed: 1642
Problematic Pages
477 issues found
Service Fabric
Enable Disk Encryption for Service Fabric managed cluster nodes
...abric/how-to-managed-cluster-enable-disk-encryption.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page exhibits a strong Windows bias. All step-by-step instructions, deployment, and verification commands are provided exclusively using PowerShell and Windows-centric Azure tools. There is minimal mention of Linux, and no Linux-specific guidance or examples are given for Service Fabric managed cluster disk encryption. Even though Azure Disk Encryption supports Linux (via DM-Crypt), the documentation focuses on Windows and BitLocker, and all verification steps use PowerShell cmdlets without Linux alternatives.
Recommendations
- Add explicit Linux instructions and examples, including how to enable and verify disk encryption on Linux-based Service Fabric managed cluster nodes.
- Provide Azure CLI examples for all deployment and verification steps, not just for Key Vault creation.
- Reference Linux documentation and tools (e.g., DM-Crypt usage, Linux VM extension details) alongside Windows/BitLocker equivalents.
- Clarify which steps are OS-agnostic and which require OS-specific actions, and organize content so Linux and Windows parity is clear.
- Include sample ARM templates and verification commands for Linux clusters.
Create Pull Request
Service Fabric
Initializer CodePackages in Service Fabric
...in/articles/service-fabric/initializer-codepackages.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a strong Windows bias: all examples use Windows containers, Windows-specific images, and Windows file paths. The only complete example references Windows container images and uses Windows command syntax (cmd, C:\ paths, type, ping). There is no mention or example of Linux containers, Linux file paths, or Linux command syntax, nor any guidance for Linux/macOS users.
Recommendations
- Add equivalent examples for Linux containers, using Linux-based images (e.g., Ubuntu, Alpine) and Linux command syntax (sh, /bin/bash, /workspace/log.txt, cat, sleep).
- Clarify whether Initializer CodePackages are supported for Linux containers and, if not, explicitly state this limitation.
- If supported, provide ApplicationManifest and ServiceManifest snippets for Linux containers, including volume mounts with Linux paths.
- Rephrase introductory and example sections to be platform-neutral or to present both Windows and Linux options side-by-side.
- Add a note about cross-platform compatibility and any differences in behavior between Windows and Linux container support.
Service Fabric
Add application cert to a cluster in PowerShell
...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/scripts/service-fabric-powershell-add-application-certificate.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation is entirely focused on PowerShell, a tool most commonly used on Windows. All code samples and instructions use PowerShell cmdlets, with no mention of Bash, Azure CLI, or cross-platform alternatives. Windows-specific concepts (such as certificate stores like LocalMachine\My) are referenced without Linux equivalents. There are no examples or guidance for Linux/macOS users, making it difficult for them to follow the steps.
Recommendations
- Add equivalent Azure CLI or Bash examples for each step, ensuring Linux/macOS users can follow along.
- Explicitly mention cross-platform options and note any differences in certificate handling between Windows and Linux.
- Provide guidance on how to install and use Azure PowerShell on Linux/macOS, or link to relevant resources.
- Include notes or sections addressing certificate store locations and management on Linux systems.
Service Fabric
Performance monitoring with Azure Diagnostics
.../service-fabric/service-fabric-diagnostics-perf-wad.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
powershell_heavy
Summary
The documentation page is heavily focused on Windows clusters, specifically using the Windows Azure Diagnostics (WAD) extension. All configuration examples, counter specifiers, and deployment instructions are tailored to Windows environments. Linux clusters are mentioned only briefly, with a link to a separate page, and no Linux-specific configuration or deployment examples are provided. The use of PowerShell for deployment further reinforces the Windows bias.
Recommendations
- Provide equivalent Linux examples for configuring performance counter collection using the Log Analytics agent, including sample configuration files and deployment commands.
- Include side-by-side or clearly separated instructions for both Windows and Linux clusters throughout the document.
- Offer CLI or ARM template deployment examples that work on Linux/macOS, such as using Azure CLI instead of PowerShell.
- Clarify which performance counters are available on Linux and how to specify them.
- Link to or summarize the Linux documentation within this page for easier cross-reference.
Service Fabric
Remove a node type in Azure Service Fabric | Microsoft Docs
...rvice-fabric/service-fabric-how-to-remove-node-type.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation exclusively uses PowerShell commands and Windows-centric tools for all operational steps, with no mention of Linux/macOS equivalents or cross-platform alternatives. There are no Bash, Azure CLI, or REST API examples, and the workflow assumes a Windows environment for cluster management.
Recommendations
- Provide equivalent Azure CLI commands for each PowerShell example, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Include Bash script examples for cluster operations where possible.
- Mention REST API alternatives for resource management tasks.
- Explicitly state platform requirements and offer guidance for Linux/macOS users on how to perform these tasks.
- Reorder examples to present cross-platform solutions first, or side-by-side with PowerShell.
Service Fabric
How to migrate to TLS (Transport Layer Security) 1.3 for Service Fabric
...vice-fabric/how-to-migrate-transport-layer-security.md
High Priority
View Details â
Detected Bias Types
windows_only
missing_linux_example
windows_tools
windows_first
Summary
The documentation is explicitly Windows-centric, stating that the steps are for Windows machines and that Linux isn't supported at this time. All prerequisites and upgrade instructions reference Windows Server, PowerShell, and Windows compatibility modes, with no mention of Linux equivalents or guidance for Linux/macOS users. There are no examples, instructions, or notes for Linux clusters, and the page does not address how or if TLS 1.3 migration is possible on non-Windows platforms.
Recommendations
- Clearly state Linux support status and roadmap for TLS 1.3 in Service Fabric clusters.
- Provide equivalent instructions or callouts for Linux clusters where possible, or link to relevant Linux documentation.
- Include Linux-specific prerequisites, upgrade steps, and configuration examples if/when support is available.
- If Linux is not supported, offer alternative security recommendations for Linux users.
- Avoid using Windows tools (e.g., PowerShell) exclusively; mention cross-platform alternatives if applicable.
Service Fabric
Create a Service Fabric cluster using Bicep
...in/articles/service-fabric/quickstart-cluster-bicep.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation is heavily biased towards Windows and PowerShell, with all setup, deployment, and certificate management instructions provided exclusively for Windows environments. There are no Linux/macOS equivalents for critical steps such as certificate creation, resource deployment, or cleanup, and Windows tools/scripts are referenced throughout. This creates significant friction for Linux/macOS users attempting to follow the quickstart.
Recommendations
- Provide equivalent instructions for Linux/macOS users, including using Azure CLI and OpenSSL for certificate creation and management.
- Offer bash script alternatives for steps currently covered by PowerShell scripts.
- Clearly indicate platform-specific requirements and offer guidance for cross-platform compatibility.
- Reorder examples to present cross-platform (Azure CLI) options before or alongside PowerShell.
- Document how to clean up certificates on Linux/macOS systems.
Service Fabric
Quickly deploy an existing app to a cluster
...b/main/articles/service-fabric/quickstart-guest-app.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
powershell_heavy
Summary
The documentation is heavily Windows-centric, focusing exclusively on Visual Studio for Windows, referencing Windows path limitations, and mentioning PowerShell scripts for deployment. There are no instructions or examples for Linux/macOS users, nor any mention of cross-platform tooling or alternatives to Visual Studio and PowerShell.
Recommendations
- Add instructions for deploying from Linux/macOS, including use of Service Fabric CLI (sfctl) and/or Azure CLI.
- Include examples using VS Code or command-line tools instead of Visual Studio, which is Windows-only.
- Provide Linux/macOS-specific guidance for project setup, deployment, and cluster management.
- Mention and show how to run PowerShell scripts on Linux (via PowerShell Core), or provide Bash script alternatives.
- Address path length issues on Linux/macOS, if relevant, or clarify that these are Windows-specific concerns.
Service Fabric
Deploy a Service Fabric cluster using the Azure portal
...es/service-fabric/quickstart-classic-cluster-portal.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation exclusively guides users to deploy a Service Fabric cluster using Windows Server 2019-Datacenter virtual machines. There is no mention of Linux-based clusters, nor are users given the option to select a Linux OS or provided with Linux-specific instructions or parity notes. All examples and screenshots assume Windows, and the process for certificate management and cluster access is described only for Windows environments.
Recommendations
- Add instructions and screenshots for deploying Service Fabric clusters on Linux-based VM images, such as Ubuntu or CentOS.
- Explicitly mention Linux as a supported OS option in the 'Operating system' dropdown and provide guidance for Linux selection.
- Include notes or sections describing differences in certificate management and access for Linux users (e.g., importing certificates, accessing Service Fabric Explorer).
- Ensure parity in example resource group, certificate, and cluster creation steps for Linux users.
- If certain features are Windows-only, clearly state this and link to Linux-specific documentation or workarounds.
Service Fabric
RunToCompletion semantics and specifications
...blob/main/articles/service-fabric/run-to-completion.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation page exhibits a strong Windows bias. All code examples use Windows containers and Windows-specific commands (cmd, set, exit, etc.), with explicit references to Windows Server container images. Query instructions mention PowerShell and C# APIs, with no mention of Linux or cross-platform alternatives. There are no Linux container examples, nor any guidance for running on Linux or macOS environments.
Recommendations
- Add equivalent examples using Linux containers (e.g., Ubuntu or Alpine images) with Linux shell commands.
- Include instructions for querying deployment status using cross-platform tools (e.g., Azure CLI, REST API) or Linux shell equivalents.
- Clarify which features are supported on Linux clusters and containers, and note any differences.
- Present Windows and Linux examples side-by-side, or alternate which platform is shown first.
- Reference documentation for creating Linux container applications with Service Fabric.
Service Fabric
Update the RDP username and password in PowerShell
...ts/service-fabric-powershell-change-rdp-user-and-pw.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation is heavily biased towards Windows and PowerShell. All examples and instructions use Azure PowerShell, with no mention of Bash, Azure CLI, or Linux/macOS-compatible workflows. The script sample, command explanations, and installation instructions are exclusively for PowerShell, which is natively a Windows tool. There are no Linux or cross-platform alternatives provided, making it difficult for non-Windows users to follow the guide.
Recommendations
- Add equivalent Azure CLI (az) examples for updating RDP username and password.
- Include Bash script samples or instructions for Linux/macOS users.
- Mention cross-platform compatibility of Azure PowerShell (if applicable) and provide installation guidance for Linux/macOS.
- Present Linux/macOS alternatives alongside or before Windows/PowerShell examples to ensure parity.
Service Fabric
Run a service under system and local security accounts
...ce-fabric/service-fabric-application-runas-security.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page focuses on Service Fabric's ability to run services under local or system accounts, but it is heavily oriented toward Windows environments. It references Windows-specific account types (LocalUser, NetworkService, LocalService, LocalSystem), Active Directory domain accounts, and group managed service accounts, all of which are Windows concepts. There are no examples or mentions of Linux equivalents, nor any guidance for Service Fabric clusters running on Linux. All XML manifest examples assume Windows-style accounts and groups, and there is no discussion of how these features work (or do not work) on Linux clusters.
Recommendations
- Add explicit sections or notes describing how (or if) local/system account features work on Linux Service Fabric clusters.
- Provide Linux-specific examples, including how to run services under Linux user/group accounts, and clarify any differences or limitations.
- Mention Linux tools and patterns for managing service identities, such as systemd service users or Linux group management.
- Clarify which features are Windows-only and provide alternative approaches for Linux users where possible.
- Ensure that navigation and 'next steps' links include Linux-relevant documentation.
Service Fabric
Service Fabric app upgrade tutorial
...-fabric/service-fabric-application-upgrade-tutorial.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The tutorial is heavily focused on Windows development environments, specifically Visual Studio, and does not mention or provide guidance for Linux or macOS users. All instructions, screenshots, and tooling references are Windows-centric, with no alternatives or parity for non-Windows platforms. The only alternative mentioned is a separate PowerShell tutorial, which is also Windows-focused.
Recommendations
- Provide equivalent instructions for Linux/macOS users, such as using Service Fabric CLI (sfctl) or Azure CLI for application upgrades.
- Include examples and screenshots for cross-platform tools and workflows.
- Explicitly state platform requirements and offer links to Linux/macOS documentation where available.
- Add a section or callout for non-Windows users, guiding them to appropriate tools and documentation.
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
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page exhibits a strong Windows bias. All command-line examples use PowerShell, and references are made exclusively to Windows-specific modules (Microsoft.ServiceFabric.Powershell.Http). There are no CLI, Bash, or Linux/macOS shell examples, nor any mention of cross-platform alternatives. The prerequisites and workflow assume the use of PowerShell and Windows-centric tooling, making it difficult for Linux/macOS users to follow or replicate the procedures directly.
Recommendations
- Provide equivalent examples using Bash, curl, or cross-platform tools for invoking REST APIs.
- Document how to install and use Service Fabric CLI (sfctl), which is cross-platform, for backup and restore operations.
- Clarify whether the PowerShell modules are available or supported on PowerShell Core (pwsh) on Linux/macOS, and provide installation instructions if so.
- Add explicit notes or sections for Linux/macOS users, including authentication and certificate handling steps.
- Reorder examples so that cross-platform methods (REST API via curl, sfctl) are presented before or alongside PowerShell examples.
Service Fabric
Periodic backup and restore in Azure Service Fabric
...ce-fabric-backuprestoreservice-quickstart-azurecluster.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation is heavily biased towards Windows, with all command-line examples using PowerShell and the Microsoft.ServiceFabric.Powershell.Http module. There are no Linux or cross-platform CLI examples, and the prerequisites and instructions assume a Windows environment (e.g., certificate store locations, PowerShell modules). The limitation section explicitly states that Service Fabric PowerShell cmdlets are in preview and that there is no support for Service Fabric clusters on Linux, making it impossible for Linux users to follow the documented procedures.
Recommendations
- Add equivalent instructions and examples for Linux environments, using cross-platform tools such as Azure CLI, REST API via curl, or Service Fabric CLI (sfctl) where possible.
- Clarify which features are Windows-only and provide alternative approaches for Linux clusters if available.
- Document certificate management steps for Linux (e.g., using PEM files and OpenSSL) rather than only referencing Windows certificate stores.
- Explicitly state platform limitations earlier in the document to set expectations for Linux/macOS users.
- If Linux support is planned, provide a roadmap or workaround guidance.
Service Fabric
Periodic backup/restore in standalone Azure Service Fabric
...bric-backuprestoreservice-quickstart-standalonecluster.md
High Priority
View Details â
Detected Bias Types
windows_tools
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation is heavily biased towards Windows, with all command-line examples using PowerShell and Windows-specific modules. The prerequisites and instructions reference Windows-only tools, such as Microsoft.ServiceFabric.PowerShell.Http and X.509 certificate management via Windows stores. There is no mention of Linux equivalents, and a limitation is explicitly stated: 'No support for Service Fabric clusters on Linux.'
Recommendations
- Clearly state Linux/macOS limitations at the top of the page, not just in the caveats section.
- If partial Linux support exists (e.g., via REST API), provide Linux/macOS-compatible examples using curl or other cross-platform tools.
- Reference Linux documentation or alternatives for certificate management and cluster connection.
- If the feature is Windows-only, consider creating a separate page or section for Linux users explaining the lack of support and possible workarounds.
- Ensure that any future updates include parity for Linux, or provide a roadmap for when Linux support will be available.
Service Fabric
Set up Microsoft Entra ID for client authentication
...ce-fabric/service-fabric-cluster-creation-setup-aad.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation is heavily oriented toward Windows and PowerShell workflows. All setup, configuration, and troubleshooting examples use PowerShell scripts (.ps1), with no equivalent bash, shell, or Linux-native instructions. The prerequisites and troubleshooting sections assume use of Windows tools and Azure Cloud Shell (PowerShell), and there is no guidance for Linux users on alternative approaches. Windows-specific capabilities (such as configuring Entra authentication for existing clusters) are mentioned before Linux, and Linux limitations are noted but not addressed with workarounds.
Recommendations
- Provide Linux-native setup instructions, such as bash scripts or Azure CLI equivalents for all major steps (app registration, user assignment, ARM template updates).
- Include explicit Linux examples for cluster creation and management, using tools commonly available on Linux (e.g., Azure CLI, REST API calls, or Python scripts).
- Document any manual steps Linux users must perform that are automated by PowerShell scripts, and provide sample commands.
- Clarify which steps can be completed on Linux and which require Windows, and offer alternatives or workarounds where possible.
- Reorder sections so that Linux and Windows instructions are presented in parallel, or at least give Linux parity in visibility.
- Address known Linux limitations with guidance or links to issue trackers/workarounds.
Service Fabric
Configure your Azure Service Fabric standalone cluster
...cles/service-fabric/service-fabric-cluster-manifest.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
powershell_heavy
Summary
The documentation is heavily focused on Windows environments, with all examples, file paths, and tooling references tailored to Windows. There are no Linux or macOS equivalents provided for key tasks such as finding IP addresses, configuring diagnostics/logs, or cluster deployment. Windows-specific tools (e.g., ipconfig, netsh) and file paths (e.g., C:\ProgramData\SF) are used exclusively, and references to security are either Windows Active Directory or X509, with no mention of Linux authentication or file system conventions.
Recommendations
- Add Linux/macOS equivalents for all command-line instructions (e.g., use 'ifconfig' or 'ip addr' instead of 'ipconfig').
- Provide sample file paths and configuration examples using Linux conventions (e.g., '/var/sf/data', '/var/sf/log').
- Include instructions for configuring diagnostics and logs on Linux, referencing Linux tools and storage locations.
- Clarify whether Service Fabric standalone clusters are supported on Linux, and if not, state this explicitly at the top of the documentation.
- If Linux is supported, add Linux-specific security configuration guidance (e.g., PAM, certificate storage).
- Present examples for both platforms side-by-side or in separate sections to ensure parity.
Virtual Machines
Azure Backup for SQL Server running in Azure VM
...extensions/backup-azure-sql-server-running-azure-vm.md
High Priority
View Details â
Detected Bias Types
windows_tools
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page is heavily focused on Windows-based deployment and management of Azure Backup for SQL Server in Azure VMs. It exclusively references the 'AzureBackupWindowsWorkload' extension, provides only PowerShell examples for registration, and does not mention or provide guidance for Linux-based SQL Server VMs or alternative tooling (such as Bash, Azure CLI, or Linux extensions). Windows terminology and tools are used throughout, with no Linux parity.
Recommendations
- Clarify whether Linux-based SQL Server VMs are supported or not. If supported, add equivalent instructions and examples for Linux VMs.
- Provide Azure CLI and/or Bash examples for registering the VM and managing backups, alongside PowerShell.
- If Linux is not supported, explicitly state this limitation at the top of the article to set expectations for non-Windows users.
- Reference any Linux-specific extensions or backup mechanisms if available.
- Reorganize examples so that cross-platform options (PowerShell, CLI, ARM templates) are presented together, not Windows-first.
Service Fabric
Azure Service Fabric Standalone Package for Windows Server
...https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-standalone-package-contents.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation is heavily focused on Windows Server, with all examples and tools provided being Windows-specific (PowerShell scripts, .exe files, Windows security templates). There are no Linux/macOS equivalents, nor any mention of how to perform these tasks on non-Windows platforms. The documentation assumes the user is operating in a Windows environment and does not provide guidance for Linux users.
Recommendations
- Add equivalent instructions and tooling for Linux (e.g., bash scripts, Linux-compatible binaries).
- Clearly state platform limitations and provide links to Linux/macOS documentation if available.
- Include Linux/macOS configuration templates and security scenarios.
- If Service Fabric Standalone is Windows-only, clarify this early and direct Linux users to alternative solutions.
Service Fabric
Standalone Cluster Deployment Preparation
...rvice-fabric-cluster-standalone-deployment-preparation.md
High Priority
View Details â
Detected Bias Types
windows_tools
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation is heavily biased towards Windows environments, with all examples, tools, and requirements specific to Windows Server. There is no mention of Linux or macOS support, and all instructions (including required services, file systems, and validation scripts) are Windows-only. This creates significant barriers for users wishing to deploy Service Fabric clusters on non-Windows platforms.
Recommendations
- Clearly state platform support at the beginning of the documentation, including whether Linux/macOS are supported for standalone clusters.
- If Linux is supported, provide equivalent instructions, requirements, and examples for Linux environments (e.g., supported distributions, required packages, file system types, service equivalents).
- Offer Linux/macOS versions of validation scripts and tools, or document alternative manual validation steps.
- Include download links and configuration templates for Linux deployments if available.
- If only Windows is supported, explicitly mention this to avoid confusion for non-Windows users.
Service Fabric
Debug your application in Visual Studio
...ce-fabric/service-fabric-debugging-your-application.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
powershell_heavy
Summary
The documentation is heavily focused on Windows and Visual Studio workflows, with all examples, screenshots, and instructions tailored to Windows environments. There is no mention of Linux/macOS equivalents for debugging Service Fabric applications, nor are alternative tools or scripts (such as Bash) discussed. The only script example is a PowerShell (.ps1) file, and all tooling references (Cloud Explorer, Visual Studio) are Windows-centric.
Recommendations
- Add explicit guidance for debugging Service Fabric applications on Linux/macOS, including supported IDEs (such as VS Code, Eclipse, JetBrains Rider) and command-line workflows.
- Provide Linux/macOS-specific instructions for setting up a local development cluster, including any required dependencies and configuration steps.
- Include script examples in Bash (.sh) alongside PowerShell (.ps1), and clarify how to invoke scripts on non-Windows platforms.
- Document alternative tracing and debugging tools available on Linux/macOS, such as using dotnet CLI, remote debugging via SSH, or integration with other IDEs.
- Clearly indicate platform limitations and provide links to cross-platform resources where Windows-only features are described.
Service Fabric
Query for cluster events using the EventStore APIs
...-fabric/service-fabric-diagnostics-eventstore-query.md
High Priority
View Details â
Detected Bias Types
windows_only
missing_linux_example
Summary
The documentation explicitly states that the EventStore APIs are GA only for Windows clusters running on Azure, with no mention of Linux support or examples. All sample queries and code are generic, but the platform limitation means Linux users cannot use these APIs. There are no Linux-specific instructions, workarounds, or parity notes.
Recommendations
- Clearly state platform limitations at the top of the page.
- Provide information about Linux support status and roadmap, if available.
- If Linux support exists or is planned, add equivalent examples and instructions for Linux clusters.
- Offer alternative diagnostic/event solutions for Linux clusters if EventStore is unavailable.
- Add a comparison table for feature availability across Windows and Linux clusters.
Service Fabric
Report and check health with Azure Service Fabric
...ric-diagnostics-how-to-report-and-check-service-health.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page exhibits a notable Windows bias: all examples and instructions are centered around Windows tools (Visual Studio, PowerShell, Local Cluster Manager), with no mention of Linux/macOS equivalents or cross-platform alternatives. Steps for creating clusters, deploying applications, and checking health are exclusively described using Windows-specific tools and workflows, leaving Linux/macOS users without guidance.
Recommendations
- Add instructions for setting up a local Service Fabric dev cluster on Linux/macOS, including required tools and commands.
- Provide examples using Service Fabric CLI (sfctl), which is cross-platform, for cluster management and health checks.
- Include deployment and health check steps using REST API and/or sfctl, demonstrating parity for Linux/macOS users.
- Mention and link to cross-platform IDEs (e.g., VS Code) and how to use them for Service Fabric development.
- Clearly indicate which steps are Windows-only and provide alternatives for other platforms where possible.
Service Fabric
Azure Service Fabric Event Store
...ervice-fabric/service-fabric-diagnostics-eventstore.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page for Azure Service Fabric Event Store exhibits a notable Windows bias. The EventStore APIs and UX are stated to be available only for Windows clusters on Azure, with Linux support described as 'in progress.' All instructions, examples, and enablement steps are tailored to Windows clusters, with no Linux-specific guidance or parity. This creates friction for Linux users, who cannot currently use the EventStore functionality.
Recommendations
- Clearly indicate current limitations and expected timelines for Linux support.
- Provide alternative monitoring or diagnostic solutions for Linux clusters until EventStore is available.
- Add Linux-specific sections or examples as soon as support is available.
- Link to Linux-compatible tools or documentation for similar functionality.
- Regularly update the documentation to reflect progress on Linux parity.
Service Fabric
Create an Azure Service Fabric container application
...ervice-fabric/service-fabric-get-started-containers.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
This documentation page is heavily biased toward Windows environments. It exclusively describes creating and deploying Windows container applications on Azure Service Fabric, with all examples, prerequisites, and tooling focused on Windows (e.g., Visual Studio, Windows Server, Docker for Windows, PowerShell). Linux equivalents are not provided, and Linux users are directed elsewhere. Critical steps (like building and deploying containers, configuring clusters, and using Service Fabric features) are only described for Windows, making the guide unusable for Linux/macOS users.
Recommendations
- Provide parallel Linux/macOS instructions and examples for each major step, including Dockerfile base images, cluster setup, and deployment.
- Include Linux-compatible tooling (e.g., VS Code, CLI commands) and avoid exclusive reliance on Visual Studio and PowerShell.
- Clearly indicate which sections are Windows-specific and link to Linux/macOS equivalents where available.
- Add Linux container examples and highlight differences in Service Fabric support between Windows and Linux.
- Ensure that prerequisites and troubleshooting steps include Linux options.
Service Fabric
Set up a Windows development environment
.../articles/service-fabric/service-fabric-get-started.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation is heavily focused on Windows, with all instructions, examples, and tooling references specific to Windows environments. PowerShell is used exclusively for scripting, and only Windows installers and tools (Visual Studio, Docker for Windows) are mentioned. There are no Linux/macOS command examples or installation instructions on this page, and Windows-specific steps (e.g., enabling PowerShell script execution) are required. Linux and Mac are only referenced via links, not in the main content.
Recommendations
- Add equivalent Linux/macOS installation instructions and command-line examples alongside Windows steps.
- Provide Bash or shell script examples for cluster setup and application deployment.
- Mention Linux/macOS compatible tools (e.g., VS Code, Docker for Linux/macOS) and how to use them.
- Ensure that prerequisites and troubleshooting steps are platform-agnostic or clearly separated by OS.
- Present platform options equally, not with Windows-first ordering.
Service Fabric
Deploy a .NET app in a container to Azure Service Fabric
...rvice-fabric/service-fabric-host-app-in-a-container.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
powershell_heavy
windows_tools
Summary
The documentation is heavily oriented toward Windows, with all examples and instructions assuming a Windows environment. Prerequisites require Windows-specific features (Hyper-V, Windows Containers), Docker Desktop for Windows, and Visual Studio. All scripting is done with PowerShell, and there are no Linux/macOS alternatives or mentions. The application is containerized as a Windows container, and Service Fabric cluster creation is described only for Windows Server nodes. No guidance is provided for Linux containers, Linux Service Fabric clusters, or using Linux-native tools.
Recommendations
- Add equivalent instructions and examples for Linux/macOS users, including prerequisites (Docker for Linux, .NET SDK, Service Fabric CLI).
- Provide Bash/Azure CLI scripts alongside PowerShell for resource creation and management.
- Clarify whether Service Fabric supports Linux containers for .NET apps, and if so, include a Linux containerization workflow.
- Include guidance for using cross-platform editors (e.g., VS Code) and command-line tools for users who do not use Visual Studio.
- Explicitly state platform limitations (e.g., if Service Fabric only supports Windows containers for .NET apps) and link to Linux alternatives if available.
Service Fabric
Create and Publish a .NET Core app to a remote Linux Cluster
...e-fabric/service-fabric-how-to-publish-linux-app-vs.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation is heavily oriented around Visual Studio, a Windows-only tool, and all workflow steps assume usage of Windows and Visual Studio. There are no examples or guidance for Linux/macOS users (e.g., using CLI tools or VS Code), and Windows-specific patterns (like .exe removal, win7-x64 runtime identifier) are mentioned before their Linux equivalents.
Recommendations
- Add instructions for creating and publishing .NET Core Service Fabric applications using cross-platform tools such as the .NET CLI and VS Code.
- Provide Linux/macOS-specific workflows, including project creation, build, and publish steps using command-line tools.
- Include screenshots and examples for Linux environments.
- Clarify which steps are Windows-only and offer alternatives for Linux/macOS users.
- Mention prerequisites and installation steps for Linux/macOS environments.
Service Fabric
Create a Windows container application on Service Fabric in Azure
...service-fabric/service-fabric-quickstart-containers.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
powershell_heavy
windows_tools
Summary
The documentation is strongly focused on Windows, with all examples, tools, and instructions tailored exclusively for Windows environments. Visual Studio and Windows PowerShell are required, and only Windows container images are discussed. Linux alternatives are mentioned only as a link to a separate quickstart, with no Linux examples or parity in the main content.
Recommendations
- Provide equivalent Linux/macOS instructions and examples inline or in parallel, not just as a separate link.
- Include examples using cross-platform tools (e.g., Azure CLI, Docker CLI) instead of relying solely on Windows PowerShell and Visual Studio.
- Mention Linux container images and deployment steps where relevant.
- Clarify which steps are Windows-specific and offer Linux/macOS alternatives for cluster creation, certificate management, and deployment.
- Add notes about cross-platform compatibility and tooling where possible.
Service Fabric
Use Patch Orchestration Application
...bric/service-fabric-patch-orchestration-application.md
High Priority
View Details â
Detected Bias Types
windows_tools
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation for Patch Orchestration Application (POA) is strongly Windows-centric. It exclusively describes patch orchestration for Windows nodes, relies on Windows Update mechanisms, Windows NT services, and PowerShell scripts for deployment, upgrade, and removal. All configuration parameters and operational details focus on Windows updates. Linux patching is only mentioned in a FAQ, redirecting users to a separate Azure VMSS feature, with no POA parity or examples for Linux clusters. There are no Linux-specific instructions, tools, or examples provided.
Recommendations
- Clearly state POA is Windows-only at the top of the documentation, if that is the case.
- If POA supports Linux, add equivalent instructions, examples, and scripts for Linux clusters, including deployment, configuration, and troubleshooting.
- Provide parity in tooling: offer Bash or CLI examples alongside PowerShell, and describe how to automate patching for Linux nodes.
- If Linux is not supported, provide a comparison table or section outlining alternatives for Linux clusters, and link to those resources more prominently.
- Ensure all configuration parameters and operational details specify their applicability (Windows-only, Linux-only, or both).
Service Fabric
Quickly create a .NET app on Service Fabric in Azure
...les/service-fabric/service-fabric-quickstart-dotnet.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation is heavily Windows-centric, requiring Visual Studio, PowerShell commands, and Windows-specific Service Fabric tools. There are no instructions or examples for Linux or macOS users, and all setup, deployment, and debugging steps assume a Windows environment.
Recommendations
- Add instructions for setting up a Service Fabric development cluster on Linux and macOS, including prerequisites and tooling.
- Provide equivalent command-line examples using Bash or other Linux shells, and document the use of Service Fabric CLI (sfctl) for cluster management.
- Include guidance for using cross-platform IDEs (such as VS Code) and .NET CLI for building and debugging the application.
- Clearly indicate platform-specific steps and provide alternative workflows for non-Windows users.
- Reference Linux container setup guides and Service Fabric Explorer access from Linux/macOS.
Service Fabric
Service Fabric project creation next steps
...ric/service-fabric-project-creation-next-step-tasks.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
powershell_heavy
Summary
The documentation page exhibits a notable Windows bias. Tutorials and walkthroughs are exclusively for Windows, with no mention of Linux/macOS equivalents. Deployment instructions reference PowerShell and Windows-specific tools, and the 'Next steps' section highlights creating a Windows cluster without alternatives for Linux. There is no guidance or parity for users on Linux or macOS platforms.
Recommendations
- Add equivalent tutorials and walkthroughs for Linux (and macOS) environments, including examples for creating clusters, deploying applications, and managing services.
- Include deployment instructions using cross-platform tools (e.g., Azure CLI, Bash scripts) alongside PowerShell.
- Clearly indicate which features or steps are Windows-only, and provide alternatives or workarounds for Linux/macOS users.
- Reorder examples or provide parallel instructions so Windows and Linux users are equally supported.
- Mention Service Fabric Explorer and other tools' availability or alternatives for non-Windows platforms.
Service Fabric
Create an actor-based service on Azure Service Fabric
...e-fabric/service-fabric-reliable-actors-get-started.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
powershell_heavy
Summary
The documentation is heavily Windows-centric, focusing exclusively on Visual Studio and Windows tooling for C# development. All examples, screenshots, and instructions assume a Windows environment, with no Linux/macOS equivalents provided. PowerShell is used for package management, and there are no instructions for using Linux-compatible tools or IDEs. Although a Java/Linux link is mentioned at the top, the main content does not address Linux users or provide parity for C# development on non-Windows platforms.
Recommendations
- Add equivalent instructions for developing Reliable Actors in C# on Linux/macOS, such as using VS Code, JetBrains Rider, or the .NET CLI.
- Include Linux/macOS-specific commands for package management (e.g., dotnet CLI instead of PowerShell).
- Provide screenshots and steps for Linux/macOS environments.
- Clarify which steps are Windows-only and offer alternatives for other platforms.
- Ensure that prerequisites and setup instructions cover cross-platform development environments.
Service Fabric
Create your first Service Fabric application in C#
...fabric/service-fabric-reliable-services-quick-start.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
powershell_heavy
Summary
The documentation is heavily oriented toward Windows development, specifically using Visual Studio and PowerShell scripts. All examples and instructions are for C# on Windows, with no Linux/macOS equivalents provided for project creation, deployment, or diagnostics. Windows-specific tools and patterns (Visual Studio, ETW, PowerShell) are mentioned exclusively, and Linux alternatives are absent.
Recommendations
- Provide equivalent instructions and examples for Linux/macOS users, such as using the Service Fabric CLI (sfctl), dotnet CLI, or VS Code.
- Include Linux/macOS deployment steps, such as building and running Service Fabric applications using terminal commands.
- Mention Linux-compatible diagnostic and logging tools (e.g., using sfctl or log files) instead of only referencing ETW and Visual Studio windows.
- Add links to Linux/macOS quickstarts and ensure parity in the 'Next steps' section.
- Clarify which steps are Windows-only and offer alternatives or links for other platforms.
Service Fabric
Run an Azure Service Fabric service as an AD user or group
...bric/service-fabric-run-service-as-ad-user-or-group.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation is heavily focused on Windows environments, specifically Windows Server standalone clusters and Active Directory. All examples and instructions reference Windows-only technologies (Active Directory, PowerShell, gMSA), with no mention of Linux or cross-platform equivalents. The use of PowerShell commands and Windows-centric security models excludes Linux/macOS users, making it unclear if or how these steps could be performed on non-Windows platforms.
Recommendations
- Clarify whether running Service Fabric services as AD users/groups is supported or possible on Linux clusters. If not, explicitly state this limitation.
- If Linux support exists, provide equivalent instructions and examples for Linux clusters, including relevant tools and authentication mechanisms.
- Mention cross-platform alternatives to PowerShell commands, or provide CLI/bash equivalents where possible.
- Consider referencing Microsoft Entra ID or other identity providers that may be more cross-platform friendly, if applicable.
Service Fabric
Run an Azure Service Fabric service under a gMSA account
...s/service-fabric/service-fabric-run-service-as-gmsa.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation is heavily focused on Windows environments, specifically Windows Server standalone clusters. All examples and instructions use Windows-specific tools (PowerShell cmdlets, Windows Features), and there is no mention of Linux or cross-platform equivalents. The prerequisites and steps assume a Windows infrastructure and Active Directory, with no guidance for Linux clusters or non-Windows authentication mechanisms.
Recommendations
- Clearly state at the beginning that the instructions are Windows-only and provide links or notes about Linux/macOS support (or lack thereof).
- If Service Fabric on Linux supports similar functionality, add equivalent instructions for Linux clusters, including relevant tools and configuration steps.
- If gMSA is not supported on Linux, mention alternative secure credential management approaches for Linux clusters.
- Provide a comparison table or section outlining differences between Windows and Linux Service Fabric cluster authentication options.
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
windows_tools
Summary
The documentation page exhibits a strong Windows bias. The reverse proxy feature is explicitly stated as unavailable for Linux clusters, with all examples, configuration guidance, and referenced tools (such as http.sys-based servers and Windows-specific environment setup) tailored to Windows environments. There are no Linux equivalents or workarounds provided, and critical functionality is not supported on Linux.
Recommendations
- Clearly state the lack of Linux support at the top of the article and in the prerequisites.
- Provide guidance or alternatives for Linux users, such as recommended patterns for service discovery and communication in Linux clusters.
- If possible, include a roadmap or link to updates regarding Linux support for reverse proxy.
- Offer Linux-specific examples or documentation for similar scenarios (e.g., using nginx or Envoy as a reverse proxy in Service Fabric Linux clusters).
- Reference Linux-compatible tools and patterns where applicable, or clarify Windows-only sections.
Service Fabric
Run a script when an Azure Service Fabric service starts
...fabric/service-fabric-run-script-at-service-startup.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page is heavily biased towards Windows environments. All code and script examples use Windows batch files (.bat), Windows-specific tools (setx, REG, PowerShell.exe), and Windows filesystem paths. Visual Studio instructions and screenshots are Windows-centric. Linux is only briefly mentioned in a single note about AccountType, with no Linux shell script or deployment examples provided.
Recommendations
- Provide equivalent Linux examples using shell scripts (e.g., MySetup.sh) and Linux commands for setting environment variables.
- Include instructions for packaging and deploying startup scripts in Linux Service Fabric clusters, including file permissions and location.
- Show how to debug startup scripts on Linux, including log file locations and redirection.
- Add parity for PowerShell examples by providing bash or sh equivalents.
- Clarify differences in user/account configuration between Windows and Linux clusters, with explicit Linux manifest samples.
Service Fabric
Scale up an Azure Service Fabric non-primary node type
...abric/service-fabric-scale-up-non-primary-node-type.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation is heavily biased towards Windows environments, with all command-line examples provided in PowerShell, explicit references to Windows file paths (e.g., C:\), and instructions for certificate management and deployment that assume Windows tooling. There are no Linux/macOS CLI equivalents, and the VM upgrade scenario focuses exclusively on Windows Server SKUs. This creates significant friction for Linux/macOS users attempting to follow the guide.
Recommendations
- Provide equivalent Azure CLI (az) commands for all PowerShell examples, ensuring cross-platform compatibility.
- Include Linux/macOS file path examples and instructions for certificate generation and management (e.g., using OpenSSL).
- Add guidance for upgrading clusters with Linux-based VM SKUs, not just Windows Server.
- Explicitly state platform requirements and offer links to platform-specific guides where appropriate.
- Reorder examples so that cross-platform solutions (Azure CLI, ARM templates) are presented before or alongside Windows/PowerShell-specific instructions.
Service Fabric
Containerize your Azure Service Fabric services on Windows
...ce-fabric/service-fabric-services-inside-containers.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
powershell_heavy
Summary
The documentation is exclusively focused on Windows, with explicit statements that the feature only works for Windows. All examples, instructions, and tooling (Visual Studio, PowerShell scripts, Windows container isolation modes) are Windows-specific. There are no Linux/macOS equivalents, nor any guidance for those platforms.
Recommendations
- Clearly state Windows-only support at the top and provide a link to Linux containerization guidance if/when available.
- Add a section describing the status of Linux/macOS support and any workarounds or alternatives.
- If possible, provide Linux/macOS equivalents for packaging, scripting, and deployment steps (e.g., Bash scripts, Docker commands).
- Mention cross-platform tools or approaches where relevant, or clarify that certain steps are not applicable outside Windows.
- Ensure future updates include Linux parity as Service Fabric container support evolves.
Service Fabric
Scale up an Azure Service Fabric primary node type
...ce-fabric/service-fabric-scale-up-primary-node-type.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation is heavily biased toward Windows environments, with all command-line examples provided in PowerShell and references to Windows file paths and certificate stores. The upgrade scenario is described only for Windows Server OS, and Linux-specific instructions are minimal and not integrated into the main workflow. There are no Bash, Azure CLI, or Linux-native examples, and Windows tools and conventions are used throughout.
Recommendations
- Provide equivalent Bash/Azure CLI examples for all PowerShell commands, especially for cluster deployment, certificate management, and resource cleanup.
- Include Linux file path and certificate store references where relevant.
- Offer a parallel Linux scenario (e.g., upgrading from Ubuntu 18.04 to Ubuntu 20.04) with step-by-step instructions.
- Clearly indicate which steps differ for Linux clusters and provide explicit guidance.
- Avoid assuming Windows as the default; present Windows and Linux options side-by-side or in separate sections.
- Reference Linux tools (e.g., openssl for certificate generation, Linux file system paths) where appropriate.
Service Fabric
Testability: Service communication
...ice-fabric-testability-scenarios-service-communication.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation exclusively provides PowerShell cmdlet examples (e.g., Move-ServiceFabricPrimaryReplica, Stop-ServiceFabricNode, Invoke-ServiceFabricPartitionQuorumLoss) for all testability actions, which are Windows-centric tools. There are no equivalent examples or instructions for Linux or macOS users, nor any mention of cross-platform alternatives. This creates friction for non-Windows users attempting to follow the guidance.
Recommendations
- Add equivalent CLI examples using Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
- Explicitly mention that PowerShell cmdlets are Windows-only and provide links or instructions for Linux/macOS users.
- Reorder examples so that cross-platform tools (sfctl) are presented first or alongside PowerShell examples.
- Include a table or section summarizing available tools for each platform.
Service Fabric
Tutorial: Build a .NET application in Azure Service Fabric
...ce-fabric/service-fabric-tutorial-create-dotnet-app.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The tutorial is heavily oriented toward Windows development, requiring Visual Studio and a Windows developer computer. All instructions, screenshots, and tooling references are for Windows and Visual Studio, with no mention of Linux/macOS alternatives or cross-platform development options. There are no examples or guidance for Linux users, and key steps (local cluster setup, debugging, project creation) are tied to Windows-only tools.
Recommendations
- Add explicit instructions for Linux/macOS users, including prerequisites and supported tooling (e.g., Visual Studio Code, CLI tools).
- Describe how to create and manage Service Fabric clusters locally on Linux/macOS, referencing the Service Fabric CLI (sfctl) and Docker-based clusters.
- Provide equivalent steps for project creation and deployment using dotnet CLI and VS Code, including screenshots or terminal commands.
- Clarify which steps are Windows-only and offer alternatives or workarounds for other platforms.
- Include troubleshooting notes for Linux/macOS environments, especially around cluster setup and debugging.
Service Fabric
Create infrastructure for a cluster on AWS
...rvice-fabric-tutorial-standalone-create-infrastructure.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation is heavily biased toward Windows. All examples and instructions assume the use of Windows Server EC2 instances, with PowerShell scripts and Windows-specific tools (RDP, net use, SMB, remote registry). There are no Linux/macOS alternatives or guidance, despite Service Fabric's 'any OS, any cloud' positioning.
Recommendations
- Provide parallel instructions for creating Linux-based EC2 instances, including recommended distributions and configuration steps.
- Include Linux shell script equivalents for setting up users, configuring firewalls, and opening ports.
- Offer guidance for connecting to Linux instances (e.g., SSH) and validating connectivity (e.g., using scp, sftp, or NFS instead of SMB).
- Clarify which Service Fabric features require Windows and which are available cross-platform.
- Explicitly state the limitations (if any) of running Service Fabric on Linux, and link to relevant documentation.
Service Fabric
Standalone Service Fabric clusters overview
...-fabric/service-fabric-standalone-clusters-overview.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page exhibits a notable Windows bias. While the introduction claims Service Fabric clusters run on both Windows Server and Linux, the detailed sections focus almost exclusively on Windows features, authentication methods, and supported operating systems. Windows security mechanisms (Kerberos, group Managed Service Accounts, Active Directory) are described in detail, with no equivalent Linux authentication or management patterns mentioned. The 'Supported operating systems' section explicitly states that Linux isn't yet supported for standalone clusters, contradicting the initial claim of Linux support. No Linux-specific examples, tools, or guidance are provided.
Recommendations
- Clarify the actual Linux support status for standalone clusters at the top of the page to avoid misleading users.
- If Linux support is planned or partial, provide a roadmap or guidance for Linux users.
- Add Linux-specific sections or examples for cluster creation, security (e.g., certificate management, Linux authentication patterns), and management.
- Mention Linux equivalents for Windows tools and patterns (such as using OpenSSL for certificates, Linux service accounts, etc.).
- Ensure that any future updates maintain parity in examples and instructions for both platforms.
Service Fabric
Define Service Configuration in StartupServices.xml for a Service Fabric Application
...service-fabric/service-fabric-startupservices-model.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page is heavily oriented toward Windows development environments, specifically Visual Studio. All workflow descriptions, examples, and screenshots reference Visual Studio features (Build/Rebuild/F5/Ctrl+F5/Publish), which are Windows-only. The only command-line tooling mentioned is PowerShell, with no mention of Linux/macOS equivalents (e.g., Bash, CLI tools). There are no examples or guidance for Linux/macOS users, nor any mention of how to achieve similar workflows outside of Windows/Visual Studio.
Recommendations
- Add explicit guidance for deploying Service Fabric applications on Linux/macOS, including supported workflows and tooling.
- Provide command-line examples using cross-platform tools (e.g., Azure CLI, Bash scripts) alongside PowerShell.
- Clarify which features (such as StartupServices.xml) are Visual Studio/Windows-only and suggest alternatives for Linux/macOS users.
- Include screenshots or descriptions for non-Windows environments if supported.
- Add a section summarizing platform limitations and parity for Service Fabric application deployment.
Service Fabric
Monitor a Service Fabric cluster in Azure
...vice-fabric/service-fabric-tutorial-monitor-cluster.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation is heavily biased toward Windows environments. It repeatedly references Windows clusters, Windows-specific tools (such as Windows Performance Counters), and PowerShell cmdlets for monitoring and health queries. There are no Linux cluster creation or monitoring examples, nor any mention of Linux equivalents for performance counters or command-line tools. All example commands and walkthroughs are Windows-centric, with no guidance for Linux/macOS users.
Recommendations
- Add explicit instructions and examples for creating and monitoring Linux Service Fabric clusters, including links to Linux cluster templates.
- Include Linux/macOS equivalents for all PowerShell cmdlets, such as REST API, Azure CLI, or Service Fabric CLI (sfctl) commands.
- Document how to collect and monitor Linux performance counters, referencing Linux tools (e.g., collectd, sysstat, or Azure Monitor's Linux agent).
- Ensure parity in screenshots and walkthroughs for Linux clusters in the Azure portal.
- Where Windows-specific references are made (e.g., Windows Performance Counters), provide a Linux alternative or clarify platform limitations.
Service Fabric
Configure the upgrade of a Service Fabric application
...abric/service-fabric-visualstudio-configure-upgrade.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page focuses exclusively on Windows-centric tools and workflows, specifically Visual Studio and PowerShell, for configuring and upgrading Service Fabric applications. There are no examples or guidance for Linux/macOS users, nor are cross-platform CLI alternatives mentioned. The upgrade process is described only in terms of Visual Studio dialogs and PowerShell commands, both of which are primarily available on Windows.
Recommendations
- Add instructions and examples for upgrading Service Fabric applications using cross-platform tools such as Azure CLI or Service Fabric CLI (sfctl).
- Include Linux/macOS-specific workflows and screenshots where applicable.
- Mention platform requirements and alternatives up front, clarifying which steps are Windows-only and providing parity for other operating systems.
- Provide sample commands for Linux shells (bash/zsh) alongside PowerShell examples.
- Reference documentation for Service Fabric development on Linux/macOS clusters.
Virtual Machine Scale Sets
Tutorial - Install applications in a scale set with Azure PowerShell
...machine-scale-sets/tutorial-install-apps-powershell.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The tutorial exclusively uses Azure PowerShell and Windows-centric tools, with all examples focused on deploying IIS (a Windows web server) using PowerShell scripts. There are no Linux or Bash examples, nor any mention of Linux application deployment, making the documentation strongly biased toward Windows environments.
Recommendations
- Add equivalent examples for deploying applications to Linux VM Scale Sets, such as installing Apache or Nginx using Bash scripts.
- Include sample Custom Script Extension configurations for Linux, demonstrating use of shell scripts and Linux package managers (e.g., apt, yum).
- Provide Azure CLI commands alongside PowerShell examples for cross-platform parity.
- Reference both Windows and Linux documentation in the 'Custom Script Extension overview' section.
- Clarify in the introduction that the tutorial is Windows-specific, or split into separate Windows and Linux guides.
Virtual Machine Scale Sets
Using Desired State Configuration With Virtual Machine Scale Sets
...l-machine-scale-sets/virtual-machine-scale-sets-dsc.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation is heavily focused on Windows and PowerShell Desired State Configuration (DSC), with all examples and references using Windows-centric tooling (Microsoft.Powershell.DSC, WMF, .ps1 scripts). There is no mention of Linux equivalents, nor examples for configuring Linux VMs or using cross-platform DSC solutions. All links and next steps point to Windows/PowerShell documentation.
Recommendations
- Add explicit guidance and examples for configuring Linux VM Scale Sets, including supported extensions and configuration management tools (e.g., Azure Custom Script Extension for Linux, Azure Machine Configuration for Linux, or third-party tools like Ansible, Chef, or Puppet).
- Clarify whether DSC extension is supported for Linux VMs, and if not, provide alternative solutions for Linux users.
- Include Linux-specific ARM template snippets and walkthroughs alongside Windows examples.
- Balance references and links to include Linux documentation and cross-platform configuration management resources.
Virtual Machines
Attach an existing OS disk to a VM
.../blob/main/articles/virtual-machines/attach-os-disk.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates significant Windows bias by providing only PowerShell-based examples and instructions, which are specific to Windows environments. There are no CLI, Bash, or Linux/macOS shell examples, nor are Linux-specific considerations or patterns mentioned. The workflow and tooling described (e.g., PowerShell cmdlets, RDP) are Windows-centric, making it difficult for Linux users to follow or adapt the instructions.
Recommendations
- Add equivalent examples using Azure CLI (az) commands, which are cross-platform and work on Linux/macOS.
- Include Bash shell script snippets for common operations (disk, network, VM creation) alongside PowerShell.
- Explicitly mention Linux VM scenarios, including SSH access setup and Linux-specific disk attachment considerations.
- Reorganize the documentation to present cross-platform (CLI) instructions first, or side-by-side with PowerShell.
- Clarify which steps are universal and which are Windows-specific, especially regarding OS disk attachment and network rules.
Virtual Machines
Add monitoring & diagnostics to an Azure virtual machine
...es/virtual-machines/extensions/diagnostics-template.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation is heavily focused on Windows virtual machines, with all examples, configuration snippets, and explanations tailored to Windows (WAD) diagnostics extension. Linux equivalents (LAD) are only mentioned in passing, and there are no Linux-specific configuration examples, XML schemas, or template snippets. The guidance, troubleshooting, and sample links are all Windows-centric, leaving Linux users without actionable steps or parity in monitoring and diagnostics setup.
Recommendations
- Add equivalent examples and configuration snippets for Linux VMs using the Linux Diagnostics Extension (LAD) and/or Azure Monitor Agent.
- Include links to Linux-specific sample templates and documentation, such as diagnostics extension schema for Linux.
- Provide XML or JSON configuration examples for Linux diagnostics, including performance counters and log collection relevant to Linux.
- Clarify differences and migration steps for both Windows and Linux users, especially given the upcoming deprecation.
- Ensure troubleshooting and deployment instructions are available for both Azure PowerShell (Windows) and Azure CLI (Linux/macOS).
Virtual Machines
Desired State Configuration for Azure overview
...n/articles/virtual-machines/extensions/dsc-overview.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation page is heavily biased toward Windows environments, focusing almost exclusively on PowerShell Desired State Configuration (DSC) and Windows Management Framework (WMF). All example code, cmdlets, and configuration scripts are Windows/PowerShell-centric, with no mention of Linux equivalents or cross-platform DSC usage. The prerequisites, architecture, and deployment sections assume Windows VMs and tools, and there are no examples or guidance for Linux VM scenarios.
Recommendations
- Add explicit guidance for using DSC or equivalent configuration management tools on Linux VMs in Azure.
- Provide Linux-specific examples for deploying and managing configuration extensions, including relevant CLI commands and file locations.
- Clarify whether the DSC extension supports Linux VMs, and if not, suggest alternative approaches for Linux configuration management (e.g., using Azure Custom Script Extension, Ansible, or Chef).
- Include cross-platform notes and parity tables to help users understand feature availability and limitations for both Windows and Linux.
- Reorder examples to present both Windows and Linux scenarios, or clearly indicate platform-specific sections.
Virtual Machines
Desired State Configuration extension with Azure Resource Manager templates
...n/articles/virtual-machines/extensions/dsc-template.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
missing_linux_example
Summary
The documentation is heavily focused on Windows and PowerShell Desired State Configuration (DSC). All examples, settings, and troubleshooting are tailored to Windows VMs and PowerShell scripts, with no mention of Linux equivalents or cross-platform DSC support. Windows terminology and tools are used exclusively, and there are no Linux-specific instructions or examples.
Recommendations
- Add explicit guidance for Linux VMs, including whether DSC extension is supported or alternatives for Linux configuration management (e.g., using Custom Script Extension, Azure Machine Configuration, or third-party tools like Ansible/Chef/Puppet).
- Provide Linux-specific examples for deploying configuration management via ARM/Bicep templates, if supported.
- Clarify in the introduction and extension settings which platforms are supported and link to Linux documentation where relevant.
- If DSC extension is Windows-only, state this clearly at the top and direct Linux users to appropriate alternatives.
- Include troubleshooting and settings sections relevant to Linux, or note differences in extension behavior between platforms.
Virtual Machines
Use Azure Policy to restrict VM extension installation (Windows)
...al-machines/extensions/extensions-rmpolicy-howto-ps.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation is heavily biased toward Windows environments, focusing exclusively on Windows VM scenarios and using Azure PowerShell for all examples. There are no Linux/macOS-specific instructions, nor are alternative tools (such as Azure CLI or Bash) mentioned. The examples and file paths are tailored to Windows users, and the page title and customer intent reinforce a Windows-only perspective.
Recommendations
- Add equivalent examples for Linux VMs, including how to restrict extensions on Linux virtual machines.
- Provide Azure CLI and Bash examples alongside PowerShell, or at least mention their availability.
- Use platform-neutral language and file paths where possible, or show both Windows and Linux file path conventions.
- Clarify which steps are universal and which are Windows-specific, and link to Linux/macOS documentation if available.
- Update the page title and customer intent to reflect cross-platform applicability if the policy applies to all VM types.
Virtual Machines
Troubleshooting Windows VM extension failures
...n/articles/virtual-machines/extensions/troubleshoot.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation is heavily focused on Windows VM extension troubleshooting, with most examples, error messages, and solutions tailored to Windows environments. PowerShell commands and Windows-specific tools (Task Manager, Control Panel, certmgr.msc) are used exclusively or presented first. Linux troubleshooting is only briefly mentioned, with limited guidance and no equivalent step-by-step examples or error analyses for Linux VMs.
Recommendations
- Provide parallel Linux examples for all troubleshooting steps, including CLI commands, log locations, and error messages.
- Include Linux-specific troubleshooting scenarios and solutions, such as common issues with waagent, permissions, or systemd services.
- Use neutral language and structure, presenting both Windows and Linux instructions side-by-side where possible.
- Reference Linux tools (e.g., journalctl, systemctl, openssl) and their usage for troubleshooting extensions.
- Add sample outputs and log snippets from Linux VMs to match the detail given for Windows.
Virtual Machines
Create and upload an OpenBSD image
...ticles/virtual-machines/linux/create-upload-openbsd.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates Windows bias primarily in the VHD creation and conversion steps. It exclusively mentions Hyper-V (a Windows-only virtualization tool) for creating the .vhd file and provides only a PowerShell example for converting VHDX to fixed VHD format. There are no Linux/macOS alternatives or examples for these critical steps, which may hinder non-Windows users from completing the process without additional research.
Recommendations
- Include instructions and examples for creating and converting VHD files using Linux/macOS tools such as qemu-img or VirtualBox.
- Mention cross-platform alternatives to Hyper-V, such as KVM, QEMU, or VirtualBox, and link to relevant guides.
- Provide Linux/macOS command-line examples for VHD conversion (e.g., qemu-img convert -f ...).
- Present Windows and Linux/macOS options side-by-side or in parallel sections to ensure parity.
Virtual Machines
Copy snapshot of managed disk to subscription (Windows) - PowerShell
...sample-copy-snapshot-to-same-or-different-subscription.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation is heavily focused on Windows and PowerShell, with no mention of Linux or macOS alternatives. All examples and tooling references are for PowerShell, and the page title and sample script are explicitly Windows-centric. There are no Bash, CLI, or Linux/macOS instructions, making it difficult for non-Windows users to follow.
Recommendations
- Add equivalent Azure CLI or Bash examples for Linux/macOS users.
- Include a section describing cross-platform approaches and tools.
- Clarify in the introduction whether the process is possible on Linux/macOS, and link to relevant documentation if available.
- Balance references to Windows and Linux documentation in 'Next steps'.
Virtual Machines
PowerShell Sample - Export/Copy snapshot as VHD to a storage account in different region
...nes-powershell-sample-copy-snapshot-to-storage-account.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation is heavily focused on PowerShell, with all examples, explanations, and referenced commands using Azure PowerShell cmdlets. There are no Bash, CLI, or Linux-native examples provided, nor is there any mention of how to perform the same task on Linux/macOS platforms. The use of PowerShell and Windows-centric tools is exclusive and presented as the only method.
Recommendations
- Add equivalent Azure CLI or Bash script examples for exporting/copying snapshots as VHDs.
- Include a section or links for Linux/macOS users detailing how to accomplish the same task using platform-appropriate tools.
- Mention cross-platform compatibility and clarify whether the PowerShell script can be run on PowerShell Core on Linux/macOS.
- Reorder or balance examples so that Linux and Windows approaches are presented equally.
Virtual Machines
Use a VHD snapshot to create multiple identical managed disks (Windows) - PowerShell
...al-machines-powershell-sample-create-snapshot-from-vhd.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation is heavily biased towards Windows and PowerShell, providing only Windows-specific instructions and examples. There are no Linux or Bash equivalents, and all references, scripts, and next steps are tailored for Windows users, making it difficult for Linux/macOS users to follow or replicate the process.
Recommendations
- Add equivalent Bash or Azure CLI examples for Linux/macOS users.
- Include a section describing how to perform the same task on Linux, referencing relevant tools and commands.
- Update the title and description to clarify if the process is Windows-only, or broaden the scope to include cross-platform instructions.
- Provide links to Linux VM documentation and script samples.
Container Instances
Create a standby pool for Azure Container Instances
...r-instances/container-instances-standby-pool-create.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 all major steps, but PowerShell (a Windows-centric tool) is given equal prominence as CLI, and specific PowerShell cmdlets are referenced throughout. ARM template deployment instructions mention PowerShell before CLI in some places. There are no Linux-specific shell examples (e.g., Bash scripts), nor any mention of Linux/macOS-specific considerations. The documentation assumes users are familiar with PowerShell and Windows tooling, which may create friction for Linux/macOS users.
Recommendations
- Add explicit Bash shell script examples for Linux/macOS users alongside PowerShell examples.
- Clarify that Azure CLI works cross-platform and highlight its use for Linux/macOS users.
- Avoid listing PowerShell deployment commands before CLI commands in ARM template sections; prefer CLI-first or parallel presentation.
- Include notes or links for installing and using Azure CLI and PowerShell on Linux/macOS.
- Consider removing PowerShell examples from main flow or moving them to a dedicated section for Windows users.
Container Instances
Tutorial - Trigger container group by Azure function
...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/container-instances/container-instances-tutorial-azure-function-trigger.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
missing_linux_example
Summary
The tutorial is heavily focused on PowerShell and Windows-centric tooling, with all code examples using Azure PowerShell cmdlets and no mention of Bash, Azure CLI, or Linux/macOS alternatives for function development or resource management. Visual Studio Code is referenced, but only in the context of PowerShell and the Azure Functions extension, which may be cross-platform but the workflow and examples are Windows/PowerShell-first. Linux users are expected to adapt PowerShell commands without guidance, and there are no examples or instructions for using Bash, Azure CLI, or developing with other languages supported by Azure Functions.
Recommendations
- Provide equivalent Azure CLI examples for resource management tasks (e.g., enabling managed identity, assigning roles, creating container groups).
- Include instructions and code samples for creating and deploying Azure Functions using Bash or other supported languages (such as Python, JavaScript).
- Clarify cross-platform support for Visual Studio Code and the Azure Functions extension, and explicitly mention Linux/macOS compatibility.
- Offer guidance for Linux/macOS users on installing and using PowerShell Core, or provide alternative workflows using native tools.
- Present examples for both Windows and Linux users side-by-side, or indicate which steps are platform-agnostic.
Service Fabric
Deploy app with a user-assigned managed identity
...vice-fabric-application-user-assigned-managed-identity.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page references PowerShell in the context of managing user-assigned managed identities and links to a PowerShell-centric guide. No equivalent CLI, Bash, or Linux/macOS-specific instructions or examples are provided. The mention of PowerShell as the primary management tool and the lack of cross-platform alternatives indicate a Windows bias.
Recommendations
- Include Azure CLI and Bash examples alongside PowerShell for managing user-assigned managed identities.
- Link to cross-platform guides (e.g., Azure CLI documentation) when referencing identity management tasks.
- Explicitly state platform compatibility for all tools and scripts.
- Provide guidance for Linux/macOS users where PowerShell is referenced.
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by focusing on 'custom windows images' in the introduction, providing only PowerShell examples for role assignment, and referencing Windows-specific tools and patterns before Linux equivalents. Linux-specific examples and CLI commands are either missing or referenced as links rather than shown inline, making the process less clear for Linux/macOS users.
Recommendations
- Include explicit Linux/macOS examples for key steps, such as using Azure CLI for role assignment (e.g., 'az role assignment create ...').
- Balance introductory language to mention both Windows and Linux custom images equally.
- Provide ARM template examples for both Windows and Linux images, highlighting any differences.
- Show Linux CLI commands inline, not just as links, especially for critical operations.
- Clarify that the process applies to both Windows and Linux images where relevant.
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_tools
missing_linux_example
Summary
The documentation page predominantly references PowerShell cmdlets (e.g., Remove-AzResource, AzSF PowerShell cmdlet) for management operations, which are traditionally Windows-centric. There are no explicit CLI/bash examples or Linux/macOS alternatives provided, and the workflow assumes familiarity with PowerShell tools. This creates friction for Linux/macOS users who may prefer or require az CLI or ARM template approaches.
Recommendations
- Add equivalent az CLI commands for all PowerShell cmdlet examples (e.g., show how to delete resources with az resource delete).
- Explicitly mention that az CLI is cross-platform and provide usage examples for Linux/macOS users.
- Clarify that ARM templates can be authored and deployed from any OS, and provide links or examples for Linux/macOS environments.
- Where possible, avoid referencing only PowerShell cmdlets; provide parity with bash/CLI commands.
Service Fabric
Use Azure DDoS Protection in a Service Fabric managed cluster
...rvice-fabric/how-to-managed-cluster-ddos-protection.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a notable Windows bias by providing only Azure PowerShell examples for key steps, referencing PowerShell before Azure CLI, and omitting explicit Linux/macOS command-line instructions. All command-line snippets use PowerShell syntax, which is native to Windows, and there are no bash or cross-platform CLI alternatives for tasks like service principal lookup or role assignment.
Recommendations
- Add equivalent Azure CLI (az) command examples for all PowerShell instructions, especially for service principal lookup and role assignment.
- Clearly indicate that Azure CLI is cross-platform and suitable for Linux/macOS users.
- Where possible, show both PowerShell and CLI examples side-by-side, or default to CLI for broader accessibility.
- Mention that ARM templates and Azure Portal are platform-agnostic, and highlight steps that can be performed without Windows-specific tools.
Service Fabric
Azure Service Fabric releases
...ocs/blob/main/articles/service-fabric/release-notes.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page for Azure Service Fabric releases shows a moderate Windows bias. Several key announcements and instructions reference Windows-specific configuration properties (such as 'windowsConfiguration.enableAutomaticUpdates') and tools (e.g., Web Platform Installer, Visual Studio). In sections discussing durability and VM scale sets, Windows configuration is mentioned first or exclusively, with Linux equivalents either omitted or mentioned later. However, there are also references to Linux support and features, and no critical tasks appear to be Windows-only.
Recommendations
- Whenever referencing VM scale set configuration, include both Windows and Linux property examples, or clarify Linux equivalents.
- When mentioning tools (e.g., Web Platform Installer, Visual Studio), add Linux/macOS alternatives (e.g., CLI, VS Code, SFCTL).
- Ensure that configuration snippets and code samples are provided for both Windows and Linux clusters where applicable.
- Review and update documentation to mention Linux/macOS support equally, especially in upgrade, deployment, and configuration sections.
- Add explicit notes or links for Linux/macOS users in sections that currently only mention Windows settings.
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_tools
missing_linux_example
Summary
The documentation provides a PowerShell-only example for bypassing the Infrastructure Service, with no equivalent Linux/macOS command or guidance. The use of Service Fabric Explorer and PowerShell cmdlets reflects a Windows-centric approach, and there is no mention of Linux-native tools or cross-platform alternatives.
Recommendations
- Include equivalent Linux/macOS command-line instructions, such as using Azure CLI, Bash, or REST API for cluster operations.
- Clarify whether Service Fabric Explorer is accessible from non-Windows platforms and provide usage instructions for Linux/macOS if available.
- Add notes or examples for managing Service Fabric clusters from Linux environments, especially for critical operations like bypassing Infrastructure Service.
- Reference cross-platform tools or document REST API endpoints where applicable.
Service Fabric
Create clusters on Windows Server and Linux
...rvice-fabric/service-fabric-azure-clusters-overview.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation page describes Service Fabric clusters on both Windows Server and Linux, but the technical details and examples focus exclusively on Windows-specific tools and processes (e.g., FabricHost.exe, Fabric.exe, FabricGateway.exe). There are no Linux-specific equivalents or instructions, and no examples or mentions of Linux service management, process names, or deployment patterns. This creates ambiguity for Linux users about how clusters operate or are managed on Linux systems.
Recommendations
- Add explicit descriptions of the Linux equivalents to Windows processes (e.g., what replaces FabricHost.exe, Fabric.exe, FabricGateway.exe on Linux).
- Include Linux-specific instructions or examples for cluster node setup, service management, and deployment.
- Clarify any differences in cluster management, security, and scaling between Windows and Linux platforms.
- Provide parity in technical detail for both platforms, ensuring Linux users have actionable information.
Service Fabric
Azure Service Fabric security best practices
...rvice-fabric/service-fabric-best-practices-security.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page exhibits a moderate Windows bias. Windows-specific tools (PowerShell, Windows Defender, DSC) and examples are presented first or exclusively in several sections, with Linux equivalents sometimes provided later or omitted. Windows security baselines and antimalware guidance are detailed, while Linux alternatives are not discussed. Some sections, such as Windows Defender, are Windows-only, and Linux users are referred to generic antimalware documentation without specifics.
Recommendations
- Present Windows and Linux examples side-by-side or in parallel sections, rather than Windows-first.
- Include Linux-specific security baseline recommendations and tooling (e.g., CIS benchmarks, Linux security modules).
- Provide concrete Linux antimalware guidance or recommended practices, not just a note to refer to generic documentation.
- Where PowerShell is used for Windows, offer Bash or other Linux-native equivalents for all tasks.
- Clarify which steps or tools are platform-specific and provide alternatives where possible.
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 demonstrates a moderate Windows bias. Windows-specific tools (PowerShell, RDP, Windows Update) are referenced more frequently and sometimes exclusively. Examples and explanations often mention Windows before Linux, and some sections (like DevOps and patching) focus on Windows workflows without equivalent Linux guidance. Linux is mentioned, but examples and operational details are less thorough.
Recommendations
- Provide Linux-specific examples alongside Windows ones, especially for operational tasks (e.g., using Bash/CLI for client API access, patching, and cluster management).
- Mention Linux tools and workflows explicitly in sections currently focused on Windows (e.g., SSH-based management, Linux update mechanisms).
- Ensure parity in DevOps guidance by including Linux deployment and operational scenarios.
- Balance the order of presentation so Linux is not always secondary to Windows.
- Clarify which ports/rules are relevant only to Windows or Linux clusters, and provide guidance for both.
Service Fabric
Update a cluster to use certificate common name
...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-change-cert-thumbprint-to-cn.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page provides deployment instructions using PowerShell commands and Windows file paths, with no equivalent examples for Linux/macOS users. The only explicit deployment example uses PowerShell, and there is no mention of Azure CLI or Bash alternatives. Windows tooling and patterns (PowerShell, C:\temp paths) are presented exclusively, creating friction for users on non-Windows platforms.
Recommendations
- Add equivalent deployment instructions using Azure CLI (az deployment group create) with Bash syntax and Linux/macOS file paths.
- Include notes or examples for Linux/macOS users on how to prepare and deploy ARM templates.
- Avoid using Windows-specific file paths (e.g., C:\temp) in generic examples; use cross-platform paths or show both.
- Explicitly mention that both PowerShell and Azure CLI can be used, and link to relevant Azure CLI documentation.
Service Fabric
Create a Service Fabric cluster in the Azure portal
...e-fabric/service-fabric-cluster-creation-via-portal.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation describes creating a Service Fabric cluster using the Azure portal, which supports both Linux and Windows clusters. However, several steps and examples (e.g., Remote Desktop credentials, management operations via PowerShell, VM size recommendations) are presented in a Windows-centric manner. There are no explicit Linux-specific instructions or examples, and Windows terminology (such as Remote Desktop) is used without mention of Linux alternatives (e.g., SSH).
Recommendations
- Add explicit instructions and examples for Linux clusters, such as SSH key setup for VM access instead of only mentioning Remote Desktop credentials.
- Where management operations are referenced (e.g., PowerShell), mention Azure CLI and provide equivalent Linux/macOS command examples.
- Clarify which steps or options differ for Linux clusters (e.g., supported VM images, OS-specific configuration).
- Ensure screenshots and UI references are inclusive of both Linux and Windows cluster creation flows.
- Add a section or notes highlighting Linux-specific considerations and best practices.
Service Fabric
Manage Service Fabric cluster upgrades
...fabric/service-fabric-cluster-upgrade-version-azure.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides PowerShell-only instructions for validating upgrade paths, with no equivalent CLI or Bash examples for Linux/macOS users. The only command-line example is Windows-centric, and the section on supported cluster versions lists Windows environments first. There is no mention of Linux-specific tools or workflows, and Linux users must infer how to perform tasks without direct guidance.
Recommendations
- Add Azure CLI and/or Bash examples for validating upgrade paths, alongside PowerShell.
- Explicitly mention Linux/macOS compatibility in command-line sections.
- Present Windows and Linux environments equally in examples and lists.
- Include notes or links for Linux/macOS users where workflows differ.
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
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a notable Windows bias by providing command-line examples exclusively using PowerShell cmdlets, which are native to Windows. There are no equivalent examples for Linux/macOS users, such as Bash, Azure CLI, or REST API usage. The documentation also refers to Windows-centric tools first and does not mention Linux-specific workflows or alternatives.
Recommendations
- Add equivalent examples using Azure CLI, Bash scripts, or REST API calls for managing node tags and services.
- Explicitly state cross-platform support and provide guidance for Linux/macOS users.
- Reorder examples so that platform-neutral methods (e.g., REST API, Azure CLI) are presented before or alongside PowerShell.
- Include notes or links to Linux/macOS documentation for Service Fabric management.
Service Fabric
Change Azure Service Fabric cluster settings
...rvice-fabric/service-fabric-cluster-fabric-settings.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page exhibits a moderate Windows bias. Many configuration parameters and descriptions reference Windows-specific concepts, tools, and defaults (e.g., certificate store names like 'MY', NTLM authentication, Windows Defender Firewall, and references to Windows-only features). Where platform differences exist, Windows is often mentioned first or exclusively, with Linux equivalents either missing, less detailed, or only referenced as exceptions. Some parameters have Windows-centric defaults or guidance, and links to further documentation are Windows-focused. There is a lack of explicit Linux/macOS configuration examples or parity in explanations for cross-platform users.
Recommendations
- Add explicit Linux/macOS configuration examples and guidance for all parameters that differ by platform.
- Where Windows-specific terms (e.g., certificate store names, NTLM, Windows Defender Firewall) are used, provide Linux/macOS equivalents or note their absence.
- Ensure that platform-specific defaults are clearly indicated, and provide parity in documentation for Linux/macOS users.
- Include links to Linux/macOS-focused documentation where available.
- Review and update references to Windows-only tools and patterns to include cross-platform alternatives.
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 demonstrates a Windows bias by providing PowerShell examples for service creation and metric configuration, with no equivalent Linux/macOS CLI (such as Bash or Azure CLI) examples. Windows/PowerShell commands are presented as the only automation method, and there is no mention of Linux-native tools or cross-platform alternatives. This could create friction for users managing Service Fabric clusters from Linux or macOS environments.
Recommendations
- Add equivalent examples using Azure CLI or Bash scripts for service creation and metric configuration.
- Explicitly mention cross-platform management options and tools available for Linux/macOS users.
- Clarify which commands are Windows-only and provide guidance for Linux/macOS users on how to achieve the same tasks.
- Consider reordering examples so that cross-platform or Linux-native options are presented alongside or before Windows-specific ones.
Service Fabric
Learn more about Azure Service Fabric
...icles/service-fabric/service-fabric-content-roadmap.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
powershell_heavy
Summary
The documentation shows a moderate Windows bias. Windows-specific tools and patterns (e.g., PowerShell cmdlets, Visual Studio, Windows services like FabricHost.exe) are mentioned first or exclusively in several sections. Examples and instructions for Linux are less prominent or missing, especially for standalone clusters and some operational tasks. Linux support is acknowledged, but parity is not consistently demonstrated, and some features are noted as unsupported or less documented for Linux.
Recommendations
- Provide Linux-specific examples and instructions alongside Windows ones, especially for cluster creation, management, and upgrades.
- Highlight cross-platform CLI tools (e.g., sfctl) equally with PowerShell, and show Linux usage examples.
- Clarify which features/tools are available on Linux and provide links to Linux-focused documentation where possible.
- Avoid mentioning Windows tools (PowerShell, Visual Studio) first; present platform-neutral or Linux-first options where appropriate.
- Add explicit guidance for Linux users in 'Next steps' and operational sections.
- Document workarounds or alternatives for Linux where features are missing.
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 extensive PowerShell examples for configuring service sensitivity and maximum load, but does not offer equivalent command-line instructions for Linux/macOS users (e.g., Bash, CLI). Windows-centric tools and APIs (PowerShell, C#) are presented before any mention of cross-platform alternatives, and there is no guidance for Linux-native workflows.
Recommendations
- Add CLI examples using Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
- Explicitly mention Linux/macOS compatibility for configuration files (XML/JSON) and deployment steps.
- Reorder examples so that platform-neutral methods (manifest, JSON) appear before Windows-specific tools.
- Provide Bash or shell script equivalents for dynamic service sensitivity updates.
- Clarify any platform-specific limitations or requirements for the APIs and tools shown.
Service Fabric
Overview of Service Fabric and containers
...s/service-fabric/service-fabric-containers-overview.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation provides both Linux and Windows information, but Windows scenarios and tools (IIS, Windows Server containers, Mirantis Container Runtime) are emphasized more prominently. Windows examples and references (such as IIS lift-and-shift and Windows container types) are described in greater detail, and Windows-specific links are sometimes listed before Linux equivalents. There is a lack of parity in scenario depth for Linux (e.g., no equivalent to the IIS lift-and-shift example for Linux web servers), and Windows container runtimes are discussed in more detail than Linux. Linux examples are present but less emphasized.
Recommendations
- Add Linux-specific scenarios, such as Apache/Nginx lift-and-shift, to match the IIS example for Windows.
- Ensure Linux tutorials and links are listed alongside or before Windows equivalents, especially in introductory and 'next steps' sections.
- Provide equal detail for Linux container runtimes and their configuration as is given for Windows (e.g., mention containerd, Podman, etc. if supported).
- Balance the discussion of container types and isolation by describing Linux container isolation mechanisms in equal detail.
- Where Windows tools (like IIS) are mentioned, include Linux alternatives (e.g., Apache, NGINX) and how they can be containerized with Service Fabric.
Service Fabric
Manage certificates in an Azure Service Fabric cluster
...https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-security-update-certs-azure.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a notable Windows bias, primarily through exclusive use of PowerShell for deployment and certificate management examples, references to Windows certificate stores (e.g., Cert:\CurrentUser\TrustedPeople), and lack of Linux/macOS CLI or scripting alternatives. All command-line instructions are given in PowerShell, with no mention of Azure CLI, Bash, or cross-platform certificate management tools. The workflow assumes a Windows environment for local certificate operations and cluster connections.
Recommendations
- Provide equivalent Azure CLI or Bash examples for template deployment, certificate import, and cluster connection.
- Reference cross-platform certificate stores and management tools (e.g., OpenSSL, Linux certificate locations).
- Include instructions for macOS/Linux users on how to import certificates and connect to clusters.
- Clarify which steps are platform-agnostic and which require platform-specific commands.
- Order examples so that platform-neutral or cross-platform methods appear before Windows-specific ones.
Service Fabric
Azure Service Fabric disaster recovery
...les/service-fabric/service-fabric-disaster-recovery.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. It references Windows-specific tools and APIs (e.g., PowerShell cmdlets like Repair-ServiceFabricPartition), links to cluster creation instructions for Windows Server, and omits explicit Linux or cross-platform command examples. Troubleshooting and recovery actions are described with Windows-centric terminology and tooling, and there is no mention of Linux equivalents or guidance for Linux-based Service Fabric clusters.
Recommendations
- Provide Linux-specific examples and instructions for key recovery and troubleshooting steps, such as using Service Fabric CLI (sfctl) or REST APIs.
- Include links to documentation for creating and managing Service Fabric clusters on Linux, not just Windows Server.
- Mention cross-platform tools and patterns (e.g., sfctl, REST API) alongside or before Windows PowerShell equivalents.
- Clarify which procedures and APIs are available and supported on Linux clusters, and note any differences.
- Add troubleshooting guidance relevant to Linux environments (e.g., systemd, journalctl, Linux process management).
Service Fabric
Start and stop cluster nodes
.../service-fabric/service-fabric-node-transition-apis.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page exhibits a moderate Windows bias. PowerShell commands are referenced alongside managed API calls, but there is no mention of Linux CLI equivalents or cross-platform tooling. All code samples are in C# and reference .NET APIs, which are primarily used on Windows. There are no bash, Linux CLI, or cross-platform examples, and Windows/PowerShell tools are mentioned before any Linux alternatives (which are absent).
Recommendations
- Add equivalent Linux CLI or bash examples for node management tasks, such as using Azure CLI, REST API, or Service Fabric CLI (sfctl) where applicable.
- Explicitly mention cross-platform tools and how Linux/macOS users can perform the same operations.
- Include sample commands and scripts for Linux environments, and clarify any platform-specific limitations or requirements.
- Reorder references so that cross-platform or platform-neutral APIs are mentioned before platform-specific tools like PowerShell.
Service Fabric
Configure networking modes for container services
...cles/service-fabric/service-fabric-networking-modes.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific instructions and caveats are presented before Linux equivalents, and certain features (such as mixing networking modes) are only supported on Windows. Windows-only configuration steps (e.g., NSG for UDP/53, network reset on reboot) are described in detail, while Linux-specific guidance is minimal or absent. There are no Linux-specific configuration examples, and limitations for Linux clusters are mentioned only as notes.
Recommendations
- Add explicit Linux configuration examples, including ARM template snippets and service manifests tailored for Linux clusters.
- Clarify which steps apply to both Windows and Linux, and which are Windows-only, using clear sectioning or callouts.
- Provide Linux-specific troubleshooting tips and caveats, similar to the Windows notes.
- Present Linux and Windows instructions in parallel where possible, rather than focusing on Windows first.
- Expand on Linux networking mode limitations and offer guidance or alternatives for Linux users.
Service Fabric
Configure Azure Service Fabric Reliable Services
...bric/service-fabric-reliable-services-configuration.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page exhibits a moderate Windows bias. Windows-specific tools (PowerShell, Visual Studio) are referenced first and exclusively in key sections (e.g., viewing the cluster manifest, configuring via Visual Studio templates). Configuration file examples use Windows-style paths (e.g., 'f:\SharedLog.Log') without Linux equivalents. There is only a brief mention of Linux in the context of certificate formats, with no Linux/macOS-specific configuration or tooling examples provided.
Recommendations
- Provide equivalent Linux/macOS commands for viewing and editing the cluster manifest (e.g., using CLI tools or text editors).
- Include Linux-style path examples (e.g., '/var/sharedlog/SharedLog.Log') alongside Windows paths.
- Add instructions for configuring Reliable Services using cross-platform tools (e.g., Azure CLI, VS Code) rather than only Visual Studio.
- Clarify any platform-specific differences in configuration file locations or formats.
- Ensure that all code and configuration samples are platform-neutral or provide both Windows and Linux/macOS variants.
Azure Impact Reporting
Azure Impact Reporting: Connectors Troubleshooting Guide
...e-impact-reporting/connectors-troubleshooting-guide.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides troubleshooting steps for both Bash and PowerShell users, but PowerShell examples and instructions are consistently presented alongside or immediately after Bash, sometimes with additional detail for PowerShell (e.g., file locking). Azure PowerShell module update instructions are included, but there is no equivalent guidance for updating Azure CLI for Bash users. In some sections, PowerShell-specific troubleshooting (e.g., $ErrorActionPreference) is mentioned without Bash equivalents. The order of presentation is generally Bash first, but parity is not perfect.
Recommendations
- Add equivalent Azure CLI update instructions for Bash users (e.g., 'az upgrade').
- Where PowerShell-specific troubleshooting is given (such as $ErrorActionPreference), provide Bash equivalents (e.g., error handling tips with 'set -e' or checking exit codes).
- Ensure that any additional details given for PowerShell (such as file locking) are also covered for Bash/Linux users (e.g., file permissions, open file handles).
- Consider grouping Bash and PowerShell instructions separately or clarifying which applies to which OS/platform.
- If possible, add explicit macOS notes where Bash instructions may differ.
Container Instances
Big containers on Azure container instances
...ob/main/articles/container-instances/big-containers.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation lists PowerShell as a deployment option before Linux-friendly tools like Azure CLI, and does not provide any Linux/macOS-specific examples or guidance. There is a lack of parity in examples and tool recommendations, which may cause friction for Linux/macOS users.
Recommendations
- List Azure CLI before PowerShell when mentioning deployment options, as CLI is cross-platform.
- Add explicit Linux/macOS examples for deploying container groups, such as sample Azure CLI commands.
- Clarify that all deployment methods (CLI, portal, ARM templates) are cross-platform and provide links to relevant Linux/macOS documentation.
- Avoid implying PowerShell is the primary or default method for deployment.
Container Instances
Config Maps for Azure Container Instances
.../container-instances/container-instances-config-map.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 all major workflows, but PowerShell (a Windows-centric tool) is given equal prominence as CLI, and is referenced in ARM template deployment instructions. Windows-specific patterns (such as PowerShell objects and Invoke-Expression) are described in detail, while Linux container config map mounting is only briefly mentioned. The Windows container section describes a custom retrieval method, but does not offer parity in example depth for Linux. The documentation does not provide Linux shell scripting examples or highlight Linux-native tools, and PowerShell is referenced as a primary automation method throughout.
Recommendations
- Add Linux shell scripting examples (e.g., Bash) for common workflows, especially for config map retrieval and automation.
- Clarify that Azure CLI is cross-platform and can be used on Linux/macOS, and consider listing CLI examples before PowerShell.
- Expand the Linux container section to show how to access config map values from within the container (e.g., using cat, ls, etc.), matching the detail given for Windows containers.
- Where PowerShell is referenced for ARM template deployment, also show Bash/CLI equivalents.
- Explicitly mention Linux/macOS support and provide troubleshooting tips for those platforms where relevant.
Container Instances
Quickstart - Create a container instance - Azure Resource Manager template
...r-instances/container-instances-quickstart-template.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation primarily demonstrates deployment using the Azure Portal, with only a brief mention of Azure PowerShell, Azure CLI, and REST API as alternatives. There are no explicit command-line examples for Linux/macOS users, and the mention of PowerShell precedes CLI, which is more cross-platform. The lack of Linux/macOS-specific instructions or screenshots creates friction for non-Windows users.
Recommendations
- Add explicit Azure CLI examples for template deployment, including command syntax and expected output.
- Include instructions and screenshots for using Azure CLI on Linux/macOS.
- Present CLI examples before PowerShell, emphasizing cross-platform compatibility.
- Clarify that Azure CLI is available on Windows, Linux, and macOS, and link to installation guides for each.
Container Instances
Configure role permissions for standby pools in Azure Container Instances
...container-instances-standby-pool-configure-permissions.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation consistently references the Azure portal UI for role assignment and troubleshooting, which is platform-agnostic but often associated with Windows workflows. When mentioning programmatic access, it lists PowerShell and CLI together, but does not provide explicit Linux/macOS CLI examples or mention Bash, nor does it offer parity for Linux-specific tools or workflows. There are no screenshots or step-by-step CLI/Bash instructions, and REST API examples are generic. The troubleshooting and monitoring sections do not show Linux-specific guidance or alternatives to the portal.
Recommendations
- Add explicit Azure CLI (az) command examples for role assignment and troubleshooting, with syntax suitable for Bash on Linux/macOS.
- Include references to Linux/macOS environments when discussing programmatic access, not just PowerShell.
- Provide parity in troubleshooting steps, such as showing how to query Log Analytics using Azure CLI or Bash scripts.
- Clarify that the Azure portal is web-based and accessible from any OS, but offer alternatives for users who prefer command-line tools.
- Add a section or note highlighting Linux/macOS workflows and tools for managing Azure RBAC and monitoring.
Container Instances
Standby pools for Azure Container Instances
...instances/container-instances-standby-pool-overview.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page demonstrates a moderate Windows bias. The only provider registration example is given in PowerShell, and PowerShell is the first example shown in the availability zones section, with Azure CLI and REST following. There are no explicit Linux/macOS-specific instructions or examples, and the use of Azure Cloud Shell (which supports Bash and PowerShell) is mentioned but only PowerShell commands are shown for critical setup steps.
Recommendations
- Provide Azure CLI (az) examples for provider registration and other setup steps alongside PowerShell, as Azure CLI is cross-platform and preferred by many Linux/macOS users.
- Ensure that CLI examples are presented before or alongside PowerShell examples, not after.
- Explicitly mention that all commands can be run in Azure Cloud Shell Bash as well as PowerShell, and clarify any platform-specific differences if they exist.
- Add notes or links for Linux/macOS users about prerequisites or environment setup if relevant.
Container Instances
Use Azure Log Analytics to monitor standby pool events for Azure Container Instances
...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/container-instances/container-instances-standby-pools-monitor-pool-events.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring diagnostic settings, but PowerShell is given equal prominence despite being Windows-centric. The instructions for creating a Log Analytics workspace and setting up alerts are exclusively portal-based, which is platform-neutral but may be more familiar to Windows users. There are no explicit Linux/macOS shell examples (e.g., Bash), nor are there instructions for using tools like Cloud Shell or direct REST calls from Linux environments. The CLI example is cross-platform, but PowerShell is Windows-first and no Linux-specific guidance is offered.
Recommendations
- Add explicit Bash shell examples for Linux/macOS users, especially for REST API calls using curl.
- Clarify that Azure CLI works on Linux/macOS and provide installation or usage notes for those platforms.
- Consider mentioning Azure Cloud Shell as a cross-platform option.
- If PowerShell is shown, note that PowerShell Core is available on Linux/macOS and provide usage instructions.
- Ensure that examples and instructions do not assume a Windows environment; add parity for Linux/macOS where possible.
Service Fabric
Migrate from Azure Cloud Services to Service Fabric
...ic/cloud-services-to-service-fabric-migration-guide.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation page exhibits a notable Windows bias. PowerShell is the only command-line example provided for cluster setup and application deployment, with no Azure CLI or Bash equivalents. Visual Studio (Windows-only) is the sole development environment mentioned for creating Service Fabric applications, and the 'Prepare your development environment' link points to Windows-specific instructions. Linux/macOS tooling and workflows are not discussed, and Windows-centric migration scenarios (IIS, Windows Containers) are detailed, while Linux alternatives are omitted.
Recommendations
- Add Azure CLI and Bash examples for cluster creation, application packaging, and deployment alongside PowerShell.
- Include instructions for developing Service Fabric applications using cross-platform tools such as VS Code, .NET CLI, and Docker.
- Provide explicit guidance for Linux/macOS users, including environment setup, certificate management, and troubleshooting.
- Mention Linux container support and migration strategies for non-Windows workloads.
- Ensure that examples and tool recommendations are presented in a platform-neutral order, or grouped by OS.
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
missing_linux_example
Summary
The documentation page demonstrates a notable Windows bias. PowerShell is used exclusively for scripting examples, and Windows-specific tools and patterns (such as the Key Vault VM extension for Windows and S-channel APIs) are referenced without Linux equivalents. The Key Vault VM extension documentation and examples are Windows-centric, and there are no Linux or cross-platform alternatives provided for certificate provisioning, management, or automation. Troubleshooting and FAQ sections also use PowerShell, with no mention of Bash, Azure CLI, or Linux-native approaches.
Recommendations
- Provide equivalent examples using Azure CLI and Bash scripts for certificate enrollment and management.
- Reference and document the Key Vault VM extension for Linux, if available, or clarify Linux support and alternatives.
- Include cross-platform guidance for certificate provisioning, especially for clusters running on Linux VMs.
- Mention Linux-specific certificate stores and access control mechanisms where relevant.
- Ensure that all automation and scripting examples have both Windows (PowerShell) and Linux (Bash/Azure CLI) versions.
- Clarify any Windows-only features (such as S-channel linking) and provide Linux alternatives or workarounds.
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
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. Windows terminology, tools, and APIs (e.g., Win32 CryptoAPI, Windows certificate store paths, Windows event logs, CAPI1/CNG provider types) are referenced first and in detail, with Linux equivalents mentioned only briefly or not at all. Troubleshooting and configuration examples focus on Windows-specific paths and error codes, and there is a lack of explicit Linux/macOS troubleshooting guidance or examples.
Recommendations
- Provide explicit Linux/macOS equivalents for all Windows-specific instructions, such as certificate store paths, error codes, and troubleshooting steps.
- Include Linux/macOS event log locations and diagnostic procedures alongside Windows event log guidance.
- Reference Linux certificate management tools (e.g., OpenSSL, certtool) and Service Fabric's Linux certificate handling mechanisms.
- Clarify how configuration settings map to Linux environments, especially for certificate storage and retrieval.
- Add Linux/macOS-specific error codes and troubleshooting scenarios.
- Ensure examples and explanations are presented in a platform-neutral order, or alternate which platform is shown first.
Service Fabric
Azure Service Fabric container image management
.../articles/service-fabric/container-image-management.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates bias towards Windows by referencing Windows-specific container images (microsoft/windowsservercore, microsoft/nanoserver) as default exclusions in cleanup settings, and mentioning them before Linux equivalents. There are no explicit Linux container image examples or discussion of Linux-specific considerations, which may leave Linux/macOS users unclear about best practices or defaults for their platforms.
Recommendations
- Include examples of Linux container images (e.g., ubuntu, alpine, centos) in the 'ContainerImagesToSkip' setting and documentation.
- Clarify whether the default exclusions apply to Linux images, and if not, provide guidance for Linux users.
- Add a section discussing platform-specific behaviors or considerations for both Windows and Linux container images.
- Ensure parity in examples and explanations for both Windows and Linux container scenarios.
Service Fabric
Create an Azure Load Balancer rule for a cluster
...n/articles/service-fabric/create-load-balancer-rule.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for creating a load balancer rule, but PowerShell (a Windows-centric tool) is given a dedicated section with a detailed, step-by-step example. The CLI example is presented first, but the PowerShell section is more elaborate. No Linux-specific tools or shell examples (e.g., Bash) are provided, and there is no mention of Linux/macOS-specific considerations or parity in the PowerShell section.
Recommendations
- Add explicit Bash shell examples for Azure CLI usage on Linux/macOS, including environment setup and command execution.
- Clarify that Azure CLI works cross-platform and is recommended for Linux/macOS users.
- Mention that PowerShell Core is available on Linux/macOS, or provide a brief note about its cross-platform support.
- Ensure that any advanced configuration steps shown in PowerShell are also covered for Azure CLI users.
- Consider adding a table or section comparing CLI and PowerShell approaches, highlighting platform compatibility.
Service Fabric
Deploy an application to a managed cluster using Azure Resource Manager
...bric/how-to-managed-cluster-app-deployment-template.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a notable Windows bias. All command-line deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzServiceFabricManagedClusterApplication), with no Azure CLI, Bash, or cross-platform alternatives provided. The application packaging workflow is described using Visual Studio, a Windows-centric IDE, with no mention of Linux/macOS equivalents or command-line packaging. Windows tools and patterns are referenced exclusively and presented first, leaving Linux/macOS users without direct guidance for completing key steps.
Recommendations
- Add Azure CLI examples for deployment and deletion alongside PowerShell commands.
- Provide instructions for packaging the application using cross-platform tools (e.g., dotnet CLI, zip utilities) instead of or in addition to Visual Studio.
- Include screenshots or descriptions for Linux/macOS workflows where relevant (e.g., uploading to Azure Storage via CLI or portal).
- Explicitly state platform requirements and offer parity guidance for non-Windows users.
- Reorder or balance examples so that Windows and Linux/macOS approaches are presented equally.
Service Fabric
Configure managed identity support in an existing Service Fabric cluster
...existing-cluster-enable-managed-identity-token-service.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation references Service Fabric Explorer and the Azure portal for cluster management and troubleshooting, both of which are primarily Windows-centric tools. It also mentions PowerShell as a method for viewing upgrade policies, without providing equivalent Linux/macOS CLI (e.g., Azure CLI or REST API) instructions or examples. No Linux-specific tools, commands, or examples are provided, and the documentation implicitly assumes the user is operating in a Windows environment.
Recommendations
- Add Azure CLI examples for viewing and managing cluster upgrade policies, as Azure CLI is cross-platform.
- Mention REST API alternatives for cluster management tasks, which are OS-agnostic.
- Include instructions or references for accessing Service Fabric Explorer from non-Windows environments (e.g., via browser).
- Clarify which steps are platform-independent and which require Windows-specific tools, and provide Linux/macOS alternatives where possible.
Service Fabric
Deploy a Service Fabric managed cluster across Availability Zones
...ce-fabric/how-to-managed-cluster-availability-zones.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation provides command-line examples exclusively using PowerShell (Az Module), and references PowerShell commands for cluster node management. There are no CLI/bash examples for Linux/macOS users, nor are cross-platform alternatives mentioned. This creates friction for non-Windows users, who must translate or research equivalent commands.
Recommendations
- Add Azure CLI (az) command examples for all PowerShell commands, especially for resource actions and cluster node management.
- Explicitly mention that Azure CLI is cross-platform and provide usage instructions for Linux/macOS.
- Where PowerShell is referenced, offer equivalent bash/CLI syntax side-by-side.
- Clarify which tools are available on which platforms, and link to installation guides for Azure CLI on Linux/macOS.
Service Fabric
Set up IP tags on a Service Fabric managed cluster
...icles/service-fabric/how-to-managed-cluster-ip-tags.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation references provisioning IPTags using a PowerShell module (Az.Network), which is a Windows-centric tool, and does not provide equivalent instructions or examples for Linux/macOS users (e.g., Azure CLI or REST API). This creates friction for non-Windows users who may not use PowerShell.
Recommendations
- Add instructions and examples for provisioning IPTags using Azure CLI, which is cross-platform.
- Include REST API example for IPTags provisioning for users who prefer direct API calls.
- Clarify that PowerShell is one option and link to Linux/macOS alternatives.
- Ensure all prerequisite steps are covered for both Windows and Linux/macOS environments.
Service Fabric
Configure maintenance control for Service Fabric managed cluster
...e-fabric/how-to-managed-cluster-maintenance-control.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation exclusively provides PowerShell-based examples and commands for configuring maintenance control on Service Fabric managed clusters. There are no CLI, Bash, or Linux/macOS-specific instructions, and all command-line guidance assumes use of PowerShell and Windows tools. This creates friction for users on Linux or macOS, who must translate or adapt the instructions themselves.
Recommendations
- Add equivalent Azure CLI (az) examples for all PowerShell commands, as Azure CLI is cross-platform and works on Linux/macOS.
- Include Bash script snippets for resource group and cluster deployment steps.
- Explicitly mention cross-platform alternatives and provide links to relevant Azure CLI documentation.
- Reorder examples so that cross-platform (CLI) instructions appear before or alongside PowerShell commands.
Service Fabric
Use Application Gateway in a Service Fabric managed cluster
...e-fabric/how-to-managed-cluster-application-gateway.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page provides step-by-step instructions for configuring Azure Application Gateway with Service Fabric managed clusters, but all command-line examples use PowerShell (specifically Azure PowerShell cmdlets), which are native to Windows. There are no Bash, Azure CLI, or Linux/macOS shell equivalents provided, and PowerShell is referenced before any other tooling. This creates friction for Linux/macOS users who may not have PowerShell installed or prefer Azure CLI.
Recommendations
- Add equivalent Azure CLI (az) commands for all PowerShell examples, especially for authentication, service principal lookup, and role assignment.
- Include notes or links on how to install and use Azure PowerShell on Linux/macOS, or recommend Azure CLI as a cross-platform alternative.
- Present both PowerShell and CLI examples side-by-side, or default to Azure CLI for broader platform compatibility.
- Explicitly mention that ARM templates are platform-agnostic and can be deployed via Azure CLI, PowerShell, or the portal.
Service Fabric
Deploy application secrets to a Service Fabric managed cluster
...e-fabric/how-to-managed-cluster-application-secrets.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools and patterns, such as the 'KeyVault extension' (linked to a Windows-only page), and by mentioning certificate store names like 'MY' (which are Windows conventions) without providing Linux equivalents or guidance. There are no Linux/macOS-specific instructions, examples, or references to Linux certificate stores or VM extensions. The examples and links focus on Windows tooling and do not address how Linux users should perform equivalent tasks.
Recommendations
- Add explicit instructions and examples for Linux clusters, including how to install certificates and manage secrets using Linux-compatible VM extensions (e.g., Key Vault extension for Linux).
- Reference Linux certificate stores (such as /etc/ssl/certs or other relevant paths) and provide guidance on how to specify them.
- Ensure that all linked documentation (such as VM extension guides) includes both Windows and Linux options, or link to Linux-specific documentation where appropriate.
- Include sample ARM templates or CLI commands for Linux clusters, and clarify any differences in process or parameters.
- Present examples for both platforms side-by-side, or clearly indicate platform-specific steps.
Service Fabric
Configure autoscaling for Service Fabric managed cluster nodes
...les/service-fabric/how-to-managed-cluster-autoscale.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page exhibits a notable Windows bias. All command-line examples use PowerShell cmdlets (e.g., New-AzResourceGroup, New-AzResourceGroupDeployment, Remove-AzResource), which are native to Windows and require either Windows or PowerShell Core on other platforms. There are no CLI examples using cross-platform tools like Azure CLI (az), nor are there bash or Linux/macOS-specific instructions. Windows terminology and tools are referenced first and exclusively throughout the step-by-step sections, with no mention of Linux alternatives or parity.
Recommendations
- Add equivalent Azure CLI (az) command examples for all PowerShell cmdlets, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Explicitly mention that PowerShell Core can be used on Linux/macOS, or provide installation guidance for non-Windows users.
- Include bash script examples or instructions for Linux/macOS users where appropriate.
- Reorder or parallelize examples so that Windows and Linux/macOS instructions are presented together, or clarify platform applicability at the start of each section.
- Reference Linux-specific considerations (e.g., VM images, metric availability) where relevant.
Service Fabric
Add Azure Dedicated Host to a Service Fabric managed cluster (SFMC)
...rvice-fabric/how-to-managed-cluster-dedicated-hosts.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a notable Windows bias by exclusively providing PowerShell examples for all command-line operations, such as authentication, resource group creation, deployment, and role assignment. There are no CLI (az), Bash, or Linux/macOS-specific instructions or examples. Windows tools and patterns (e.g., RDP, PowerShell) are mentioned first and exclusively, which may create friction for Linux/macOS users who typically use Bash or Azure CLI.
Recommendations
- Add equivalent Azure CLI (az) command examples for all PowerShell steps, including authentication, resource group creation, deployment, and role assignment.
- Include Bash script snippets or instructions for Linux/macOS users.
- Clarify that all steps can be performed from any OS using Azure CLI, not just PowerShell.
- Mention SSH as an alternative to RDP for VM access where appropriate.
- Consider reordering examples so that cross-platform tools (Azure CLI) are shown first or side-by-side with PowerShell.
Service Fabric
Create a Service Fabric managed cluster (SFMC) with Ephemeral OS disks for node types
...ce-fabric/how-to-managed-cluster-ephemeral-os-disks.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides explicit instructions and code samples for deploying the ARM template using PowerShell cmdlets, which are primarily Windows-centric. There are no examples or guidance for deploying via Azure CLI, Bash, or other Linux/macOS-friendly tools. The admin credentials are described in terms of RDP (a Windows protocol), and the PowerShell method is listed before any mention of cross-platform alternatives. No Linux/macOS-specific instructions or parity examples are provided.
Recommendations
- Add equivalent deployment instructions and code samples using Azure CLI (az deployment group create), which works on Linux, macOS, and Windows.
- Include Bash script examples for template deployment.
- Mention SSH as an alternative to RDP for admin access, and clarify how Linux/macOS users can connect to VMs.
- Explicitly state that the ARM portal and Azure CLI methods are cross-platform.
- Reorder examples so that cross-platform methods (Azure CLI, portal) are listed before Windows/PowerShell-specific instructions.
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
missing_linux_example
Summary
The documentation consistently provides PowerShell examples for command-line operations (add, remove, scale, configure placement properties), but does not mention or provide equivalent examples for Linux/macOS users (e.g., Azure CLI, Bash). PowerShell is a Windows-centric tool, and its use is assumed throughout, creating friction for users on other platforms. Additionally, PowerShell instructions are given before any mention of cross-platform alternatives, and no Linux/macOS-specific tooling or guidance is offered.
Recommendations
- Add Azure CLI examples for all command-line operations (add, remove, scale, configure placement properties, etc.), as Azure CLI is cross-platform and widely used on Linux/macOS.
- Explicitly state that PowerShell examples are for Windows, and provide Bash/Azure CLI equivalents for Linux/macOS users.
- Where possible, mention cross-platform tools first or alongside PowerShell, to avoid implying Windows is the default or only supported platform.
- Include notes or links to installation guides for Azure CLI on Linux/macOS.
- Review all sections for other Windows-specific assumptions (e.g., drive letter conventions) and clarify their applicability to Linux-based clusters.
Service Fabric
Configure network settings for Service Fabric managed clusters
...es/service-fabric/how-to-managed-cluster-networking.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation page exhibits several Windows biases. Most command-line examples use PowerShell cmdlets (New-AzResourceGroup, New-AzResourceGroupDeployment, Login-AzAccount, etc.) with no mention of Linux/macOS equivalents (e.g., Azure CLI, Bash). Remote Desktop (RDP) instructions and screenshots are Windows-centric, with no guidance for SSH access to Linux nodes. The public IP verification step uses a PowerShell command, and there are no alternative instructions for Linux users. Throughout, Windows tools and patterns are referenced exclusively or before any cross-platform alternatives.
Recommendations
- Provide Azure CLI and Bash examples alongside PowerShell for all command-line steps, especially resource group creation, deployment, and querying resources.
- Include SSH instructions and screenshots for connecting to Linux nodes, not just RDP for Windows.
- Clarify which steps are OS-agnostic and which require Windows-specific tools, and offer alternatives where possible.
- Explicitly mention Linux/macOS support for Service Fabric managed clusters and link to relevant documentation.
- For public IP verification, show equivalent Azure CLI commands usable on Linux/macOS.
Service Fabric
Upgrading Azure Service Fabric managed clusters
...cles/service-fabric/how-to-managed-cluster-upgrades.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page exhibits a Windows bias by only listing Windows cluster versions in the REST API example output and omitting any mention or example of Linux cluster versions. There are no Linux-specific instructions, examples, or references to Linux Service Fabric managed clusters, despite Service Fabric supporting both Windows and Linux environments.
Recommendations
- Include REST API example output that shows both Windows and Linux cluster versions, or alternate between them.
- Explicitly mention that Service Fabric managed clusters can run on Linux, and provide guidance or links for Linux-specific upgrade scenarios.
- Add examples of Resource Manager templates and upgrade settings for Linux clusters, including relevant OS type values.
- Reference documentation or sections that address Linux operating system support and differences in upgrade procedures, if any.
Service Fabric
Add a virtual machine scale set extension to a Service Fabric managed cluster node type
...ervice-fabric/how-to-managed-cluster-vmss-extension.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page exhibits a notable Windows bias. The only CLI example provided is for PowerShell (Add-AzServiceFabricManagedNodeTypeVMExtension), with no mention of Azure CLI, Bash, or Linux/macOS alternatives. The main extension example uses 'KeyVaultForWindows' as the type, and there is no discussion of Linux-specific VM extensions or cross-platform considerations. Windows tools and patterns are referenced exclusively and appear first, with no parity for Linux users.
Recommendations
- Add equivalent Azure CLI and/or Bash examples for adding VM extensions to Service Fabric managed cluster node types.
- Include documentation and examples for Linux-specific VM extensions (e.g., KeyVaultForLinux) and clarify when to use each.
- Provide guidance for macOS users, especially for scripting and automation tasks.
- Reorder examples or add parallel examples so that Windows and Linux approaches are presented equally.
- Explicitly mention cross-platform support and limitations for Service Fabric managed cluster extensions.
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
missing_linux_example
Summary
The documentation page shows a moderate Windows bias. PowerShell is referenced repeatedly as a primary tool for managing Service Fabric clusters, with direct links to PowerShell cmdlets and examples. While Azure CLI and sfctl (cross-platform tools) are mentioned in the utility table, the best practices section exclusively highlights PowerShell for key operations (delete, restart, reimage), and does not provide equivalent Azure CLI or sfctl command examples. This may create friction for Linux/macOS users who do not use PowerShell.
Recommendations
- Add equivalent Azure CLI and sfctl command examples for all PowerShell cmdlets referenced, especially in the best practices section.
- Explicitly mention that Azure CLI and sfctl are cross-platform and suitable for Linux/macOS users.
- Reorder examples so that cross-platform tools (Azure CLI, sfctl) are shown before or alongside PowerShell.
- Clarify which tools are recommended for Linux/macOS users in the best practices section.
Service Fabric
Monitor Azure Service Fabric
...main/articles/service-fabric/monitor-service-fabric.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page generally covers both Windows and Linux clusters, but there are several instances of Windows bias. Windows-specific tools and patterns (Event Log, ETW, Diagnostics Agent) are mentioned first or exclusively, with Linux equivalents referenced less prominently or as afterthoughts. Some tutorials and examples focus on .NET/Windows, and Linux configuration steps are often deferred to linked pages rather than explained inline. The EventStore API is noted as Windows-only, and some monitoring setup recommendations are Windows-centric.
Recommendations
- Provide Linux-specific examples and configuration steps inline, not just as links.
- Ensure that Linux tools (e.g., LTTng, Syslog) are described with equal detail and prominence as Windows tools (e.g., ETW, Event Log).
- Add tutorials and sample code for Linux clusters, including non-.NET applications.
- Clearly indicate feature parity or limitations for Linux vs. Windows (e.g., EventStore API availability).
- When listing monitoring tools or agents, present Windows and Linux options side-by-side.
- Avoid using Windows-centric language or examples as the default; alternate or balance ordering.
Service Fabric
Add a managed identity to a Service Fabric managed cluster node type
...ed-identity-managed-cluster-virtual-machine-scale-sets.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page provides command-line examples exclusively using PowerShell cmdlets (New-AzResourceGroup, New-AzUserAssignedIdentity, New-AzRoleAssignment, etc.), with no equivalent Azure CLI or Bash examples for Linux/macOS users. The VM image configuration in the ARM template defaults to Windows Server, and references to Linux VM images or deployment patterns are absent. Troubleshooting and deployment instructions reference the Azure portal and PowerShell, omitting Linux-native workflows.
Recommendations
- Add Azure CLI examples for all PowerShell commands, ensuring Linux/macOS users can follow along without needing PowerShell.
- Include ARM template snippets or parameter sets for Linux VM images (e.g., Ubuntu), and clarify how to use managed identities with Linux node types.
- Reorder examples so that cross-platform (ARM template, Azure CLI) instructions appear before or alongside PowerShell examples.
- Explicitly mention Linux support and link to relevant documentation for Linux Service Fabric clusters where applicable.
Service Fabric
Monitoring data reference for Azure Service Fabric
...les/service-fabric/monitor-service-fabric-reference.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a notable Windows bias. Performance counter examples are exclusively Windows-centric, referencing Windows-specific categories and tools (e.g., Performance Monitor). There are no Linux equivalents or instructions for collecting similar metrics on Linux-based Service Fabric clusters. Windows tools and patterns are mentioned first and exclusively, with no parity for Linux users.
Recommendations
- Add equivalent Linux performance counter categories and metrics, such as those available via sysstat, top, or collectd.
- Provide instructions or examples for collecting metrics on Linux nodes, including recommended tools and integration with Azure Monitor.
- Clarify which metrics are available on Linux clusters and note any differences or limitations.
- Include screenshots or references to Linux monitoring tools (e.g., atop, htop, Prometheus exporters) alongside Windows Performance Monitor.
- Explicitly state platform support for each metric or counter listed.
Service Fabric
Deploy a Service Fabric managed cluster using the Azure portal
...es/service-fabric/quickstart-managed-cluster-portal.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation describes deploying a Service Fabric managed cluster using the Azure portal, focusing exclusively on portal-based steps and certificate management. The cluster nodes are explicitly stated to be Windows Server 2019 VMs, and there is no mention of Linux-based Service Fabric clusters or how Linux/macOS users might interact with the cluster, especially regarding certificate import and browser integration. All instructions and screenshots assume a Windows-centric workflow, with no guidance for Linux or macOS environments.
Recommendations
- Add notes clarifying that Service Fabric managed clusters currently only support Windows node types, or provide information about Linux support if available.
- Include instructions for importing and using client certificates on Linux and macOS (e.g., using Firefox, Chrome, or command-line tools like OpenSSL).
- Provide guidance for Linux/macOS users on accessing Service Fabric Explorer, including browser certificate handling.
- If possible, mention alternative cluster deployment options (e.g., ARM templates, CLI) and link to documentation with Linux/macOS parity.
- Explicitly state platform limitations and recommend alternatives for non-Windows users where relevant.
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
windows_tools
missing_linux_example
powershell_heavy
Summary
The documentation page exhibits moderate Windows bias. Windows-specific tools and patterns such as Active Directory domain accounts, group managed service accounts (gMSA), and BitLocker are mentioned with more detail and prominence than their Linux equivalents. Powershell is referenced for disk encryption, while Linux disk encryption is only noted as a TODO. Examples and guidance for running services under security accounts are detailed for Windows (including AD and gMSA), but Linux approaches are not described. In several sections, Windows features are discussed first or exclusively, with Linux support only briefly mentioned or omitted.
Recommendations
- Provide equivalent Linux examples and instructions for all security features, such as running services under specific user accounts and encrypting disks.
- Include Linux-specific tools and patterns (e.g., systemd service accounts, Linux file permissions, LUKS disk encryption) alongside Windows features.
- Ensure that examples and guidance are presented in a cross-platform manner, or at least alternate the order in which Windows and Linux approaches are described.
- Remove TODOs and replace them with actual Linux guidance and links.
- Where Powershell is referenced, add Bash or CLI equivalents for Linux users.
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
windows_first
Summary
The documentation consistently references PowerShell cmdlets and Windows-centric tools (e.g., Copy-ServiceFabricApplicationPackage, Register-ServiceFabricApplicationType) as primary command-line interfaces for managing Service Fabric applications. These are listed before or alongside REST API and .NET methods, but Linux-native equivalents (such as Azure CLI or sfctl) are not directly mentioned in step-by-step instructions or examples. The only nod to cross-platform tooling is a brief link to a page about Azure CLI and sfctl, without any concrete usage examples or parity in the main lifecycle walkthroughs.
Recommendations
- Add explicit Linux/macOS-friendly command examples using Azure CLI and sfctl for each lifecycle phase (deploy, upgrade, remove, etc.), alongside PowerShell examples.
- In each step where PowerShell cmdlets are referenced, include equivalent Azure CLI/sfctl commands and clearly indicate cross-platform options.
- Reorder or parallelize examples so that Windows and Linux/macOS approaches are presented with equal prominence.
- Expand the 'includes/service-fabric-sfctl.md' section to provide concrete, in-context examples rather than just a link.
Service Fabric
Deploy and upgrade with Azure Resource Manager
...vice-fabric/service-fabric-application-arm-resource.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates a notable Windows bias. PowerShell is the only command-line example provided for resource removal, with no equivalent Bash, Azure CLI, or Linux/macOS instructions. Windows-centric tools (PowerShell, Remove-AzResource) are mentioned exclusively or before Linux alternatives. The 'Next steps' section lists PowerShell before CLI, and there is no explicit guidance for Linux/macOS users or parity in examples.
Recommendations
- Add equivalent Azure CLI and Bash examples for all PowerShell commands, especially for resource removal.
- Explicitly mention that all operations can be performed from Linux/macOS using Azure CLI or REST API, and provide links.
- In 'Next steps', list cross-platform tools (CLI, REST API) before or alongside PowerShell.
- Include notes or sections clarifying platform compatibility and any differences in workflow for Linux/macOS users.
Service Fabric
Advanced Application Upgrade Topics
...-fabric/service-fabric-application-upgrade-advanced.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page exhibits a strong Windows bias, primarily by providing PowerShell-only examples and referencing Windows-centric tools and workflows (PowerShell cmdlets, Visual Studio) without mentioning or demonstrating equivalent Linux/macOS approaches (such as Azure CLI, REST API, or cross-platform SDKs). There are no Linux/macOS shell examples, and the guidance assumes familiarity with Windows tooling, which may hinder non-Windows users.
Recommendations
- Add equivalent Azure CLI and/or REST API examples for all PowerShell cmdlets mentioned, especially for service creation, updates, and upgrades.
- Explicitly mention cross-platform alternatives (e.g., Azure CLI, .NET SDK, REST API) and link to their documentation.
- Provide sample commands for Linux/macOS environments (bash, CLI) alongside PowerShell examples.
- Clarify which features or tools are available cross-platform and note any limitations.
- Include a section on upgrading applications using Linux/macOS, with step-by-step instructions.
Service Fabric
Manage Azure Service Fabric application secrets
...fabric/service-fabric-application-secret-management.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides both Windows and Linux links for certificate setup, but in the critical section on deploying applications with encrypted secrets, only PowerShell (Windows) and C# examples are given. There is no Linux CLI or bash example for creating application instances with encrypted parameters, and the scripting example is Windows-centric (PowerShell). Windows tools and patterns (PowerShell) are mentioned exclusively for scripting, and Windows is implicitly prioritized in example order and tooling.
Recommendations
- Add equivalent Linux CLI/bash examples for creating Service Fabric application instances with encrypted parameters (e.g., using sfctl or REST API).
- Explicitly mention Linux tooling and scripting options alongside PowerShell, such as sfctl, Azure CLI, or bash scripts.
- Ensure example order alternates or is grouped by platform, rather than defaulting to Windows/PowerShell first.
- Clarify any platform-specific differences in scripting and deployment, and link to Linux-specific guides where appropriate.
Service Fabric
Application upgrade: data serialization
...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-application-upgrade-data-serialization.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates Windows bias by listing Visual Studio and PowerShell upgrade tutorials as the only explicit 'next steps', both of which are primarily Windows tools. There are no Linux/macOS equivalents or examples provided, nor is there mention of cross-platform CLI alternatives. The focus on C# and Data Contract serialization is expected for Service Fabric, but the upgrade guidance is Windows-centric.
Recommendations
- Add explicit instructions or links for upgrading applications using cross-platform tools such as Azure CLI or Service Fabric CLI (sfctl), which work on Linux/macOS.
- Include examples or tutorials for performing upgrades from Linux/macOS environments.
- Mention platform-agnostic approaches alongside Windows-specific tools in the 'Next steps' section.
- Clarify which steps are Windows-only and provide Linux/macOS alternatives where possible.
Service Fabric
Troubleshooting application upgrades
...https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-application-upgrade-troubleshooting.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page exclusively uses PowerShell commands and outputs for all troubleshooting and recovery examples, with no mention of Linux/macOS equivalents (such as Service Fabric CLI or REST API). Windows tooling (PowerShell, Visual Studio) is referenced throughout, and alternative Linux/macOS workflows are not described or linked. This creates friction for users on non-Windows platforms.
Recommendations
- Add equivalent examples using Service Fabric CLI (sfctl) for Linux/macOS users alongside PowerShell commands.
- Include references and links to documentation for CLI and REST API usage for troubleshooting and upgrades.
- Explicitly state platform requirements for each command/tool and provide guidance for cross-platform users.
- Balance the order of examples so that Linux/macOS tools are presented alongside or before Windows tools where appropriate.
- Add troubleshooting steps and outputs for CLI/REST API workflows.
Service Fabric
Azure Service Fabric Central Secret Service
...vice-fabric/service-fabric-application-secret-store.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a notable Windows bias. All command-line examples for interacting with the Central Secret Service REST API use PowerShell and Windows-specific tooling (Invoke-WebRequest), with no equivalent Linux/macOS examples (e.g., curl). File paths and mount points show Windows first, with Linux alternatives only mentioned in comments. There is no guidance for Linux users on how to perform key actions, such as secret creation or management, using native Linux tools.
Recommendations
- Provide Linux/macOS command-line examples using curl or similar tools alongside PowerShell examples.
- Show both Windows and Linux file paths/mount points equally in documentation, not just as commented alternatives.
- Explicitly mention authentication and certificate handling steps for Linux clusters, including how to install and reference certificates.
- Add notes or sections clarifying any platform-specific differences in Service Fabric cluster configuration and secret management.
- Where XML snippets reference file paths, show both Windows and Linux formats side by side.
Service Fabric
Application upgrade: upgrade parameters
...abric/service-fabric-application-upgrade-parameters.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page demonstrates a Windows bias by prioritizing PowerShell and Visual Studio (Windows-only tools) in both structure and detail. The main parameter tables and explanations are presented first for PowerShell and Visual Studio, with SFCTL (the cross-platform CLI) covered only after. Examples and parameter formats are given for PowerShell (hashtable syntax) and Visual Studio dialogs, with less detail for SFCTL. There are no Linux/macOS-specific examples or notes, and Windows tools are mentioned and described before their Linux equivalents.
Recommendations
- Reorder sections so that SFCTL (cross-platform CLI) is presented before or alongside PowerShell/Visual Studio.
- Provide explicit Linux/macOS examples for SFCTL commands, including sample CLI invocations and parameter formats.
- Add notes clarifying platform compatibility for each tool (e.g., PowerShell: Windows, SFCTL: Windows/Linux/macOS).
- Include a table or summary comparing upgrade workflows across platforms.
- Ensure that parameter descriptions and examples are equally detailed for SFCTL as for PowerShell.
- Reference Linux/macOS upgrade tutorials more prominently, not just in 'Next steps'.
Service Fabric
Service Fabric application upgrade
...s/service-fabric/service-fabric-application-upgrade.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates a notable Windows bias. The only code example provided uses PowerShell, a Windows-centric tool, with no equivalent Bash or Linux CLI example. References to Windows-specific technologies (e.g., http.sys, PowerShell cmdlets) are present, and upgrade instructions prioritize Windows tools and workflows. There is no mention of Linux/macOS equivalents or cross-platform alternatives, making it difficult for non-Windows users to follow the upgrade process.
Recommendations
- Provide equivalent Bash or Service Fabric CLI examples for Linux/macOS users alongside PowerShell examples.
- Explicitly mention cross-platform tools (e.g., sfctl) and link to their documentation.
- Clarify which instructions or features are Windows-only and offer alternatives where possible.
- Add troubleshooting and upgrade workflow guidance for Linux/macOS environments.
- Reorder examples so that cross-platform or Linux options are presented before or alongside Windows-specific ones.
Service Fabric
Understanding periodic backup configuration
...-fabric-backuprestoreservice-configure-periodic-backup.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias primarily in the backup storage section, where file share examples and authentication methods are described exclusively using Windows-style UNC paths (\\StorageServer\BackupStore) and Windows authentication mechanisms. There is no mention of Linux-compatible file share paths (such as NFS or SMB mounts), nor are Linux authentication patterns or examples provided. Windows terminology and tooling (Integrated Windows Authentication) are presented first and exclusively, with no Linux alternatives or parity.
Recommendations
- Add examples for configuring backup storage using Linux-compatible file shares, such as NFS or SMB mounts, including sample paths and authentication methods.
- Include instructions for mounting and accessing file shares from Linux nodes, with relevant commands and configuration details.
- Clarify whether the backup feature supports Linux-based clusters and, if so, provide explicit guidance for Linux/macOS environments.
- Present both Windows and Linux options in parallel, rather than Windows-first or Windows-only.
- Mention any platform-specific limitations or requirements for backup storage types.
Service Fabric
Upgrade the configuration of an Azure Service Fabric cluster
...-fabric/service-fabric-cluster-config-upgrade-azure.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation lists Windows-centric tools (PowerShell) before cross-platform alternatives (Azure CLI), and provides specific PowerShell command references. No explicit Linux/macOS examples or guidance are given, though Azure CLI is mentioned as an option.
Recommendations
- Present Azure CLI examples and references before or alongside PowerShell, emphasizing CLI's cross-platform compatibility.
- Include explicit Linux/macOS instructions or notes to reassure non-Windows users that all steps are supported on their platforms.
- Provide sample commands for both PowerShell and Azure CLI, clearly labeling which platforms they work on.
- Mention that Azure Resource Explorer and Azure Portal are web-based and platform-agnostic.
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
missing_linux_example
Summary
The documentation page demonstrates Windows bias primarily in the Management subsystem section, where PowerShell cmdlets are mentioned as the main tooling for lifecycle management. There is no mention of Linux equivalents (such as Bash scripts, CLI commands, or REST APIs), nor are cross-platform tools highlighted. The transport subsystem also references Windows security as an option for securing communication, but does not mention Linux authentication mechanisms. No explicit Linux/macOS examples or tools are provided anywhere in the document.
Recommendations
- Include references to cross-platform management tools, such as Azure CLI, REST APIs, or Bash scripts, alongside PowerShell.
- Mention Linux authentication mechanisms (e.g., OpenSSL, PAM, or Kerberos) in the transport subsystem section.
- Add explicit examples or notes for Linux/macOS users where platform-specific tooling is discussed.
- Ensure that all tooling and command references are presented in a platform-neutral way, or provide parallel examples for both Windows and 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_tools
missing_linux_example
windows_first
Summary
The documentation page exclusively provides PowerShell-based examples and instructions, which are native to Windows. All command-line operations (module installation, cluster connection, backup triggering, REST calls) are shown using PowerShell syntax and Windows-specific modules. There are no Linux/macOS CLI equivalents (e.g., Bash, curl, Azure CLI), nor any mention of how to perform these tasks on non-Windows platforms. The documentation assumes the use of Windows tooling throughout, creating friction for Linux/macOS users.
Recommendations
- Add equivalent examples using Bash and curl for REST API calls.
- Document how to authenticate and connect to Service Fabric clusters from Linux/macOS.
- Provide Azure CLI or Service Fabric CLI (sfctl) examples for backup operations.
- Clarify platform requirements for the Microsoft.ServiceFabric.Powershell.Http module and suggest alternatives for Linux/macOS.
- Reorder examples so that cross-platform methods (REST API, Azure CLI) are shown before or alongside PowerShell.
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
missing_linux_example
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Service Fabric clusters, but PowerShell (a Windows-centric tool) is given a dedicated section and is used for cluster upgrades without Linux alternatives. Windows-specific registry and template settings are discussed in detail, while Linux equivalents are not mentioned. Upgrade instructions and disabling updates focus on Windows, with no Linux guidance. Although links to both Windows and Linux cluster creation tutorials are provided at the end, the main body of the documentation is notably Windows-focused.
Recommendations
- Add Linux-specific instructions and examples for cluster upgrades, including shell commands and package formats (e.g., .deb for Linux).
- Provide Linux equivalents for registry and update management (e.g., systemd, apt, yum, or configuration files).
- Include Bash or other cross-platform scripting examples alongside PowerShell.
- Clarify which steps are Windows-only and provide parity for Linux users where possible.
- Present examples for both platforms in parallel, or alternate which platform is shown first.
Service Fabric
Differences between Cloud Services (extended support) and Service Fabric
...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cloud-services-migration-differences.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation references Service Fabric running on both Windows and Linux, but examples, API mappings, and tooling references (e.g., Connect-WindowsFabricCluster) are Windows-centric. There are no explicit Linux or cross-platform command-line examples, and Windows tools are mentioned without Linux equivalents. The ordering and language often put Windows first, and there is a lack of practical guidance for Linux users.
Recommendations
- Provide explicit Linux examples and tooling references alongside Windows ones (e.g., show how to connect to a Service Fabric cluster from Linux).
- Mention cross-platform tools and APIs where available, or clarify platform-specific differences.
- Ensure that when listing supported platforms, Linux is mentioned equally and not as a secondary option.
- Add migration guidance and code samples that work on Linux, including deployment and management steps.
- Where Windows-specific tools are referenced (e.g., Connect-WindowsFabricCluster), include Linux alternatives or note their absence.
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_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a notable Windows bias, particularly in its operational examples and tooling references. Key scaling procedures (both vertical and horizontal) are described using PowerShell commands and Windows-centric tools, with no equivalent Linux CLI or script examples provided. The step-by-step instructions for scaling in/out reference PowerShell and Service Fabric PowerShell cmdlets exclusively, omitting Linux alternatives such as Bash scripts or Service Fabric CLI commands. Additionally, Windows tools and patterns are mentioned first and more frequently, while Linux guidance is relegated to a single link in the 'Next steps' section.
Recommendations
- Add Linux-specific examples for scaling operations, using Bash and Service Fabric CLI (sfctl) commands.
- Include cross-platform instructions for disabling/removing nodes, not just PowerShell cmdlets.
- Present both Windows and Linux procedures side-by-side or clearly indicate platform-specific steps.
- Reference Linux tools (e.g., sfctl, Azure CLI) where appropriate, and provide links to their documentation.
- Ensure that operational guidance (e.g., for scaling, node management) is not exclusively tied to Windows environments.
Service Fabric
Service Fabric cluster capacity planning considerations
...cles/service-fabric/service-fabric-cluster-capacity.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page exhibits mild Windows bias. It references Windows-specific tools (such as Remove-ServiceFabricNodeState and Patch Orchestration Application) and provides instructions for standalone clusters only for Windows, with no equivalent Linux guidance. Additionally, when discussing configuration changes, Windows instructions are given before Linux/Azure instructions, and Linux/Unix-specific examples or tools are missing.
Recommendations
- Add explicit guidance and examples for managing standalone clusters on Linux, including configuration upgrade instructions and relevant tooling.
- When referencing tools or commands (e.g., Remove-ServiceFabricNodeState), clarify whether Linux equivalents exist or provide alternative Linux instructions.
- Include Patch Orchestration Application alternatives or guidance for Linux clusters, or clarify its applicability.
- Ensure that instructions for Azure-hosted clusters and standalone clusters are presented in parallel for both Windows and Linux, with equal prominence.
- Where possible, use cross-platform terminology and avoid assuming Windows as the default environment.
Service Fabric
Create an Azure Service Fabric cluster template
...ric/service-fabric-cluster-creation-create-template.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a notable Windows bias, primarily by providing only PowerShell examples for testing the Resource Manager template, referencing Windows-centric sample templates, and omitting equivalent Linux/macOS CLI instructions. The sample template linked is for a Windows cluster, and there is no mention of using Azure CLI or Bash for Linux/macOS users. Windows tools and workflows are presented as the default, with Linux-specific guidance limited to a single note about Microsoft Entra ID setup.
Recommendations
- Add Azure CLI and Bash examples for testing and deploying Resource Manager templates, alongside PowerShell.
- Include links to sample templates for Linux clusters, not just Windows.
- Present Windows and Linux/macOS instructions side-by-side or in separate tabs/sections for parity.
- Clarify which steps and parameters are OS-agnostic and which are platform-specific.
- Reference cross-platform tools (e.g., Azure CLI) before or alongside Windows-only tools.
Service Fabric
Create an Azure Service Fabric cluster
...vice-fabric/service-fabric-cluster-creation-via-arm.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation exhibits a moderate Windows bias. PowerShell (a Windows-centric tool) is consistently presented first in all command examples, and Windows file paths (e.g., c:\certificates) are used in both PowerShell and Azure CLI examples, even when the CLI is cross-platform. There are no explicit Linux shell (bash) examples, and the use of Windows-specific tools and patterns (e.g., ConvertTo-SecureString, Set-AzKeyVaultAccessPolicy) is prevalent. While Ubuntu templates are referenced and the Azure CLI is shown, Linux/macOS users may encounter friction due to the lack of native shell examples and persistent Windows-centric defaults.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or present CLI (cross-platform) first.
- Provide native bash/Linux shell examples for all CLI commands, using Linux-style paths (e.g., /home/user/certificates) and environment variable syntax.
- Explicitly note when a command or tool is Windows-only, and provide Linux/macOS equivalents where possible.
- Use OS-agnostic language and file paths in documentation, or provide both Windows and Linux/macOS path examples.
- Highlight any differences in prerequisites or setup steps for Linux/macOS users.
Service Fabric
Azure Service Fabric Programmatic Scaling
...-fabric/service-fabric-cluster-programmatic-scaling.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a notable Windows bias: PowerShell cmdlets are mentioned as the only scripting alternative to the .NET SDK, with no Linux/macOS equivalents (such as Azure CLI or Bash examples). Windows tools and patterns (PowerShell, .NET SDK) are referenced exclusively, and scripting examples are provided only for PowerShell, not for cross-platform shells. This may create friction for Linux/macOS users who do not use PowerShell.
Recommendations
- Add Azure CLI examples for scaling operations, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Mention Bash scripting as an alternative to PowerShell for automation.
- Present cross-platform examples (e.g., Azure CLI) before or alongside PowerShell examples.
- Clarify which tools and SDKs are supported on Linux/macOS and provide relevant links.
- Explicitly state that PowerShell is available on Linux/macOS, if recommending its use.
Service Fabric
Specifying Service Fabric service endpoints
...ce-fabric/service-fabric-service-manifest-resources.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
powershell_heavy
windows_first
Summary
The documentation page demonstrates a moderate Windows bias. It references Windows file paths for SDK/schema locations, uses PowerShell exclusively for deployment examples, and mentions Windows certificate stores before Linux equivalents. Linux-specific instructions are present but secondary, and no Linux shell (bash) deployment examples are provided.
Recommendations
- Include Linux/macOS equivalents for all Windows-specific instructions, such as schema file locations and certificate stores.
- Provide deployment examples using Azure CLI, Bash, or other cross-platform tools alongside PowerShell.
- Mention Linux paths and procedures at the same prominence and order as Windows ones.
- Clarify any platform-specific differences in endpoint configuration, certificate management, and port ACLing.
- Add explicit notes or sections for Linux/macOS users where behaviors or commands differ.
Service Fabric
Set up Microsoft Entra ID for client authentication in the Azure portal
...vice-fabric-cluster-creation-setup-azure-ad-via-portal.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page provides detailed instructions and examples for configuring Microsoft Entra ID authentication for Service Fabric clusters, but all command-line connection examples use PowerShell, with no Linux/macOS equivalents (such as Azure CLI or REST API). Troubleshooting and connection sections reference PowerShell exclusively. While there are some notes about Linux-specific limitations, the overall guidance and examples are Windows-centric, making it harder for Linux/macOS users to follow or replicate the steps.
Recommendations
- Add equivalent Linux/macOS connection instructions using Azure CLI or REST API, especially for cluster authentication and management tasks.
- Provide explicit examples for connecting to Service Fabric clusters from Linux/macOS environments, including required tools and setup steps.
- Include troubleshooting steps and solutions for common issues encountered on Linux/macOS, not just PowerShell/Windows.
- Clarify any platform-specific limitations and offer workarounds or alternatives for Linux/macOS users.
- Where possible, present cross-platform commands (e.g., Azure CLI) before or alongside PowerShell examples.
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
windows_tools
missing_linux_example
Summary
The documentation page exhibits a moderate Windows bias. While it mentions both Windows and Linux node types in the Service Fabric extension, several examples and references (such as dataPath using Windows-style paths and certificate store naming) are Windows-centric. The 'Next steps' section prioritizes Windows-specific tasks like RDP port changes and admin credential management, with links to PowerShell scripts and RDP usage, but does not provide equivalent Linux SSH instructions or examples. There are no explicit Linux/macOS walkthroughs or parity in remote connection guidance.
Recommendations
- Add Linux/macOS-specific examples for connecting to cluster nodes (e.g., SSH instructions alongside RDP/PowerShell).
- Include Linux-style paths (e.g., /var/svcfab) in the Service Fabric extension example and clarify cross-platform usage.
- Provide parity in 'Next steps' by linking to Linux/macOS remote connection and credential management guides.
- Explicitly mention and demonstrate Linux tools and workflows where Windows tools (RDP, PowerShell) are referenced.
Service Fabric
Remote connect to an Azure Service Fabric cluster node
...ce-fabric-cluster-remote-connect-to-azure-cluster-node.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page demonstrates a Windows-first bias: Windows (RDP) connection steps and screenshots are presented before Linux (SSH) equivalents, and the examples and visuals focus primarily on Windows tools (Remote Desktop Connection). Additionally, the 'Next steps' section links to PowerShell scripts for Windows-specific tasks, with no Linux alternatives provided.
Recommendations
- Provide Linux/SSH connection screenshots and examples alongside or before Windows/RDP examples.
- Include links to Linux-specific scripts or CLI instructions for tasks like changing SSH port ranges and updating admin credentials.
- Balance the presentation order so that Linux and Windows instructions are equally prominent.
- Reference cross-platform tools (e.g., Azure CLI, Bash) where possible, not just PowerShell.
- Clarify any OS-specific differences in steps and provide parity in troubleshooting guidance.
Virtual Machine Scale Sets
Enable Azure Disk Encryption for Virtual Machine Scale Sets
...virtual-machine-scale-sets/disk-encryption-overview.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page shows a notable Windows bias: Windows OS disk encryption is supported, while Linux OS disk encryption is explicitly not supported. Tutorial links mention PowerShell (Windows-centric) and CLI, but do not clarify if Linux-specific instructions or parity exist. The examples and guidance focus on Windows scenarios first, and Linux support is limited to data disks only, with no Linux OS disk encryption walkthrough.
Recommendations
- Clearly state the limitations for Linux users at the top of the page.
- Provide explicit Linux CLI examples and workflows, or link directly to Linux-specific guides.
- Ensure that tutorial links clarify which OSes are supported and offer Linux alternatives where possible.
- If Linux OS disk encryption is not supported, suggest alternative approaches or workarounds for Linux users.
Virtual Machine Scale Sets
Proximity placement groups for Virtual Machine Scale Sets
...rtual-machine-scale-sets/proximity-placement-groups.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by presenting only PowerShell-based examples for creating and managing proximity placement groups and VM scale sets. Windows tools (PowerShell cmdlets) are used exclusively throughout the step-by-step instructions, with no equivalent Azure CLI or Linux/macOS shell examples provided. The only mention of Azure CLI is in a brief note at the end, without any concrete example or guidance. This creates friction for Linux/macOS users who primarily use Bash and Azure CLI.
Recommendations
- Provide equivalent Azure CLI examples alongside PowerShell examples for all major tasks (creating proximity placement groups, listing them, creating scale sets, checking alignment status).
- Clearly indicate cross-platform options at the start of the documentation, and avoid presenting Windows/PowerShell as the default or only method.
- Add links to Linux/macOS-specific documentation where relevant, and ensure parity in example depth and clarity.
- Consider reordering sections so that CLI and PowerShell examples are presented together, or alternate which is shown first.
Virtual Machine Scale Sets
Create a standby pool for Virtual Machine Scale Sets
...les/virtual-machine-scale-sets/standby-pools-create.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples, but PowerShell is given equal prominence as CLI, and deployment instructions for ARM and Bicep templates mention PowerShell tools (New-AzResourceGroupDeployment) alongside CLI. There is no explicit Linux/macOS bias, but the presence of PowerShell and Windows-specific tooling may create friction for Linux users. The portal instructions are platform-neutral, but PowerShell is a Windows-centric tool, and its mention may imply a Windows-first approach.
Recommendations
- Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and recommend CLI for cross-platform usage.
- List CLI examples before PowerShell examples to reduce Windows-first perception.
- For ARM and Bicep deployment, highlight az deployment group create as the primary method, and mention PowerShell as an alternative for Windows users.
- Add notes clarifying that PowerShell Core is available on Linux/macOS, if PowerShell usage is necessary.
- Consider adding bash script examples for Linux users where relevant.
Virtual Machine Scale Sets
Create an Azure scale set that uses Availability Zones
...s/virtual-machine-scale-sets-use-availability-zones.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for creating and updating scale sets with Availability Zones, but PowerShell (a Windows-centric tool) is given equal prominence to CLI, and in some update scenarios, CLI and PowerShell are shown before REST API/ARM template. There are no explicit Linux/macOS shell examples (e.g., Bash), and the ARM template section references both Linux and Windows but does not provide a full Linux-specific example. The documentation does not mention any Linux-specific tools or patterns, and the PowerShell examples may not be directly usable on Linux/macOS without additional setup.
Recommendations
- Add explicit Bash shell examples for Linux/macOS users alongside Azure CLI commands.
- Clarify that Azure CLI is cross-platform and can be used on Linux/macOS, and provide installation/use links for those platforms.
- Ensure that Linux examples (e.g., ARM template for Linux VMs) are shown with equal detail and prominence as Windows examples.
- Consider listing Azure CLI (cross-platform) examples before PowerShell (Windows-centric) examples to reduce perceived Windows bias.
- Add notes or links for Linux/macOS users on how to use PowerShell Core if needed.
Service Fabric
Import certificates into a container
...s/service-fabric/service-fabric-securing-containers.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific details (such as PFX export, ACLs, and environment variables) are described first and in greater depth, with Linux equivalents mentioned briefly and lacking code examples. The only code sample provided is C# for importing a PFX file, which is relevant to Windows but not Linux (which uses PEM and unencrypted private keys). There are no Linux shell or code examples for certificate import, nor guidance on handling PEM/private key files inside Linux containers.
Recommendations
- Provide equivalent Linux-focused code examples (e.g., Bash or Python) for importing PEM and private key files inside containers.
- Describe Linux-specific certificate handling steps, including file permissions and security considerations.
- Present Windows and Linux instructions/examples in parallel, or clearly separate them for clarity.
- Include references to Linux-native tools (e.g., openssl) for certificate import and management.
- Clarify differences in environment variables and certificate formats between platforms with side-by-side tables or sections.
Virtual Machines
Azure Key Vault VM Extension for Linux
...rticles/virtual-machines/extensions/key-vault-linux.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation is focused on Linux, but several sections show Windows bias. PowerShell examples are presented before Azure CLI equivalents, and PowerShell is referenced as a primary deployment and troubleshooting tool. Windows-centric patterns (e.g., PowerShell, ARM template notes referencing Windows VM portal guides) appear before or in place of Linux-native alternatives, even though the extension is Linux-specific.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and native to Linux/macOS.
- Minimize references to Windows-specific tools and guides (e.g., avoid linking to Windows VM portal instructions in Linux docs).
- Add explicit Bash shell examples for common tasks (e.g., troubleshooting, file manipulation) to complement or replace PowerShell snippets.
- Clarify that PowerShell is optional and not required for Linux users; highlight CLI and Bash as primary tools.
- Ensure troubleshooting and support sections provide parity for Linux-native workflows (e.g., using journalctl, tail, grep for logs).
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_tools
missing_linux_example
windows_first
Summary
The documentation page provides code samples for configuring Service Fabric placement policies using C# and PowerShell only. PowerShell is a Windows-centric tool, and no equivalent Linux/macOS command-line examples (such as Azure CLI, Bash, or REST API) are provided. The documentation assumes familiarity with Windows tooling and omits guidance for Linux-based Service Fabric clusters, which can create friction for non-Windows users.
Recommendations
- Add Azure CLI examples for all placement policy configurations, as Azure CLI is cross-platform.
- Include REST API examples for service creation and placement policy configuration.
- Explicitly mention how Linux-based Service Fabric clusters can be managed, and link to relevant documentation.
- If PowerShell is required, clarify whether PowerShell Core (cross-platform) is supported and provide usage instructions for Linux/macOS.
- Present cross-platform examples (CLI, REST) 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_tools
missing_linux_example
windows_first
Summary
The documentation provides detailed examples for configuring auto scaling in Azure Service Fabric using PowerShell and C# APIs, both of which are strongly associated with Windows environments. There are no equivalent Linux/macOS CLI or scripting examples (e.g., Bash, Azure CLI, REST API), and PowerShell is presented as the primary command-line automation tool. Windows-centric tools and patterns are referenced exclusively, and Linux support is mentioned only in passing, with no actionable guidance for Linux users.
Recommendations
- Add examples using Azure CLI, Bash scripts, or REST API for configuring auto scaling policies, ensuring Linux/macOS users have clear, actionable steps.
- Explicitly document which features and commands are supported on Linux clusters, and provide guidance for Linux-specific workflows.
- Where PowerShell is used, offer equivalent commands using cross-platform tools (e.g., Azure CLI) and clarify platform compatibility.
- Reorder examples so that cross-platform or Linux-compatible methods are presented before or alongside Windows/PowerShell methods.
Service Fabric
Describe a cluster by using Cluster Resource Manager
...ce-fabric-cluster-resource-manager-cluster-description.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation page exhibits a moderate Windows bias. Windows terminology and configuration formats (ClusterManifest.xml with <WindowsServer>), Windows-specific examples, and PowerShell commands are presented before or more prominently than Linux equivalents. There is little explicit mention of Linux-specific configuration or tooling, and the examples and instructions assume a Windows-centric environment, especially for standalone clusters and local development. PowerShell is used for service management examples, with no Linux CLI or bash alternatives provided.
Recommendations
- Provide explicit Linux configuration examples, such as using Linux-based node definitions in ClusterManifest.xml or ClusterConfig.json.
- Include Linux CLI equivalents (e.g., Service Fabric CLI (sfctl)) alongside PowerShell commands for service creation and updates.
- Clarify that Service Fabric supports both Windows and Linux nodes, and note any differences in configuration or deployment steps.
- Where examples use <WindowsServer> in XML, also show <Linux> or cross-platform alternatives.
- Add notes or sections on Linux-specific considerations for cluster setup, node properties, and resource management.
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 command-line examples exclusively in PowerShell, which is a Windows-centric tool, and does not mention or provide equivalent examples for Linux or macOS environments (such as Bash, CLI, or shell scripts). The PowerShell examples are presented first and are the only command-line examples, creating friction for users on non-Windows platforms. There is no discussion of Linux-specific tools or patterns, nor any guidance for Linux/macOS users on how to perform the same operations.
Recommendations
- Add Azure CLI or Bash examples for service creation and update commands, ensuring Linux/macOS users have clear instructions.
- Explicitly mention cross-platform tools and provide guidance for running Service Fabric commands on Linux/macOS.
- Clarify whether PowerShell commands can be run via PowerShell Core on Linux/macOS, or provide alternatives if not.
- Reorder examples or provide parallel Windows and Linux/macOS sections to avoid implicit prioritization of Windows.
Service Fabric
Roll over an Azure Service Fabric cluster certificate
...vice-fabric/service-fabric-cluster-rollover-cert-cn.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation provides only a Windows PowerShell script for rolling over a Service Fabric cluster certificate, with Windows file paths and no mention of Linux/macOS equivalents. There are no Bash, CLI, or cross-platform examples, and the workflow assumes use of Windows tools and conventions.
Recommendations
- Add equivalent instructions and scripts using Azure CLI and Bash for Linux/macOS users.
- Use cross-platform file path examples or clarify platform-specific differences.
- Explicitly mention how Linux/macOS users can perform certificate upload and VMSS update steps.
- Provide guidance on running Azure PowerShell in cross-platform environments (e.g., PowerShell Core on Linux/macOS) if applicable.
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
windows_tools
missing_linux_example
windows_first
Summary
The documentation consistently provides PowerShell examples for all operations, which is a Windows-centric tool. There are no equivalent examples for Linux/macOS users, such as Azure CLI, Bash, or REST API commands. The PowerShell examples are always presented first, reinforcing a Windows-first perspective. This creates friction for users on non-Windows platforms, as they must seek out alternative methods themselves.
Recommendations
- Add equivalent Azure CLI, Bash, or REST API examples for all PowerShell commands.
- Clearly indicate which commands are platform-specific and provide guidance for Linux/macOS users.
- Consider presenting cross-platform examples (e.g., Azure CLI) before or alongside PowerShell to promote parity.
- Reference official documentation for Linux/macOS management of Service Fabric clusters.
Service Fabric
Cluster Resource Manager - Management Integration
...fabric-cluster-resource-manager-management-integration.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation provides a detailed example of querying Service Fabric health using a PowerShell command (Get-ServiceFabricPartitionHealth), which is specific to Windows environments. There are no equivalent examples or instructions for Linux/macOS users, such as using the Service Fabric CLI (sfctl) or REST API. The only command-line tooling shown is Windows-centric, and no Linux-native tools or patterns are mentioned.
Recommendations
- Add equivalent Linux/macOS examples using sfctl or REST API for health queries.
- Explicitly mention cross-platform tooling and provide instructions for both Windows and Linux/macOS users.
- Where PowerShell is used, include the analogous command for Linux (e.g., sfctl partition health).
- Clarify any platform-specific limitations or differences in tooling.
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
windows_first
Summary
The documentation page exhibits a notable Windows bias. It references PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) as the primary method for managing and scaling standalone Service Fabric clusters, without mentioning equivalent Linux commands, tools, or workflows. The linked 'scale a standalone cluster' guide is explicitly for Windows Server, and there is no guidance or examples for Linux-based clusters. This creates friction for Linux/macOS users and implies that Windows is the default or only supported platform for standalone cluster management.
Recommendations
- Provide equivalent Linux examples using Service Fabric CLI (sfctl), REST API, or other cross-platform tools for cluster scaling operations.
- Clarify platform support for standalone clusters (Windows vs. Linux) and explicitly mention any limitations.
- Add links or sections for Linux-specific cluster scaling documentation, if available.
- Ensure that references to PowerShell cmdlets are accompanied by Linux alternatives or a note about platform compatibility.
- Reorganize examples so that Windows and Linux instructions are presented side-by-side or in parallel sections.
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 demonstrates a moderate Windows bias. While it mentions that Service Fabric clusters can run on both Azure (which can be Linux or Windows) and standalone Windows Server, the examples and linked guides for standalone clusters are exclusively for Windows. Windows authentication (Kerberos) is discussed in detail, with no mention of Linux equivalents (such as LDAP, PAM, or certificate-based authentication on Linux). Certificate creation and management references Windows Server certificate services and Windows tools, with no guidance for Linux-based certificate management. There are no explicit Linux examples or instructions for standalone clusters, and Windows terminology and tools are referenced first and exclusively in several sections.
Recommendations
- Add explicit instructions and examples for setting up node-to-node and client-to-node security on standalone Linux clusters.
- Include Linux-compatible certificate creation and management workflows (e.g., using OpenSSL, Let's Encrypt, or other Linux CA tools).
- Reference Linux authentication mechanisms or clarify how certificate-based authentication works on Linux clusters.
- Balance references to Windows tools (e.g., MakeCert.exe, Windows Server certificate service) with Linux alternatives.
- Where standalone clusters are discussed, clarify support and provide parity for Linux environments.
Virtual Machines
Troubleshooting Azure Disk Encryption for Linux VMs
...tual-machines/linux/disk-encryption-troubleshooting.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation is focused on Linux VMs and provides Linux-specific troubleshooting steps. However, when discussing how to check encryption status and disable disk encryption, it consistently presents Azure PowerShell (Windows-centric) commands first and in greater detail, with CLI commands mentioned only briefly and after PowerShell. No Linux-native tools or shell examples are provided for these Azure management tasks.
Recommendations
- Provide Azure CLI examples alongside or before PowerShell examples, as Azure CLI is cross-platform and preferred by many Linux users.
- Explicitly mention that Azure CLI can be used from Linux/macOS and provide full command output examples.
- Where possible, include Bash shell or Linux-native commands for local disk status checks, not just Azure management commands.
- Ensure that instructions for disabling or checking encryption are not PowerShell-centric and offer parity for Linux users.
Virtual Machines
Create shared Azure Linux VM images using the portal
...rticles/virtual-machines/linux/shared-images-portal.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page is focused on creating and sharing Linux VM images using the Azure portal, but in the 'Before you begin' section, it references a tutorial for creating a managed image using Azure PowerShell and links to a snapshot creation guide under a Windows-specific path. There are no explicit Linux CLI (e.g., Bash, Azure CLI) examples or links, and the initial instructions for image creation reference Windows-oriented resources before Linux equivalents.
Recommendations
- Include links to Linux-specific tutorials for creating managed images, such as using Azure CLI or Bash scripts.
- Reference cross-platform guides or clarify that the PowerShell tutorial is applicable to Linux/macOS (if true), or provide alternatives.
- Ensure snapshot creation links point to Linux-relevant documentation or provide both Windows and Linux options.
- Add explicit Azure CLI examples for common tasks, especially for Linux users who may not use PowerShell.
Virtual Machines
Manage Virtual Machine restore points
...ain/articles/virtual-machines/manage-restore-points.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides only Azure PowerShell examples for managing VM restore points, with no equivalent CLI (az), Bash, or Linux/macOS-specific instructions. All code samples use PowerShell syntax, which is native to Windows and less common on Linux/macOS. There is no mention of cross-platform tools or alternative workflows for non-Windows users.
Recommendations
- Add Azure CLI (az) examples alongside PowerShell for all major operations.
- Explicitly mention that PowerShell Core is available on Linux/macOS, or link to installation instructions.
- Provide Bash script examples for common tasks where appropriate.
- Ensure that instructions do not assume the user is on Windows; clarify cross-platform compatibility.
- List both PowerShell and CLI options in parallel, or indicate which is recommended for each OS.
Virtual Machines
Enable MSP on an Existing Virtual Machine or Virtual Machine Scale Set
...tual-machines/metadata-security-protocol/brownfield.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation demonstrates a Windows bias by providing detailed extension status examples and output for Windows VMs only, referencing Windows-specific tools and paths, and omitting equivalent Linux extension output or validation examples. Windows extension installation is described as automatic, while Linux requires a separate explicit API call, but no Linux output or validation details are shown.
Recommendations
- Add example output and validation details for the Linux Proxy Agent extension, similar to the Windows example.
- Include Linux-specific extension status codes, messages, and file paths to demonstrate parity.
- Present Windows and Linux instructions and examples side-by-side or in parallel sections.
- Clarify the Linux installation process with explicit REST API call examples and expected results.
Virtual Machines
Customer intent: "As an IT administrator managing Azure IaaS virtual machines, I want to implement a backup and disaster recovery plan for unmanaged disks, so that I can ensure data durability and high availability in the event of localized or regional failures."
...al-machines/page-blobs-backup-and-disaster-recovery.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 coverage in its scope, but there are several instances of Windows bias. Windows tools (e.g., PowerShell, Volume Shadow Service) are mentioned first and in more detail, with Linux alternatives (e.g., fsfreeze) referenced briefly or as less capable. Examples and links for backup automation and snapshot management often point to Windows-specific resources or PowerShell, with Linux CLI or scripting alternatives less emphasized or missing. Some backup consistency features are described as unavailable for Linux, and Linux-specific guidance is sometimes relegated to notes or external links.
Recommendations
- Provide Linux CLI and shell script examples alongside PowerShell for all backup and snapshot operations.
- Mention Linux tools (e.g., fsfreeze, Azure CLI, AzCopy) with equal prominence and detail as Windows tools.
- Ensure Linux-specific documentation links are included and referenced in the main text, not just in 'Next steps' or notes.
- Describe application-consistent backup strategies for Linux in more detail, including third-party options or best practices.
- Avoid presenting Windows tools or workflows first; alternate or parallelize Windows and Linux instructions.
- Clarify limitations and workarounds for Linux users where Windows features (e.g., VSS) are unavailable.
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
All CLI examples use the Windows Server image (Win2022DataCenter) and do not mention or provide examples for Linux VM images. There is no guidance for Linux users, and the documentation implicitly assumes Windows as the default platform.
Recommendations
- Include equivalent examples using popular Linux images (e.g., UbuntuLTS, CentOS, Debian) alongside Windows examples.
- Add notes clarifying MSP support for Linux VMs and any platform-specific considerations.
- Where screenshots are provided, show both Windows and Linux VM deployment scenarios.
- Explicitly mention that the commands work for both Windows and Linux VMs, or note any differences.
Service Fabric
Scale a Service Fabric cluster in or out
.../service-fabric/service-fabric-cluster-scale-in-out.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates a notable Windows bias. PowerShell is used extensively for examples and critical operations (such as node removal), with Windows-specific cmdlets and terminology (e.g., Remove-ServiceFabricNodeState, Get-ServiceFabricNode). While Azure CLI and sfctl commands are provided, PowerShell examples are often presented first and in more detail. There is no explicit mention of Linux shell equivalents for Service Fabric management tasks, nor guidance for Linux/macOS users regarding prerequisites or environment setup. The documentation assumes familiarity with Windows tooling and omits Linux-specific instructions for connecting to clusters or running Service Fabric commands.
Recommendations
- Provide Linux/macOS shell (bash) equivalents for all PowerShell examples, especially for critical operations like node removal and scaling.
- Clearly indicate which commands are cross-platform and which are Windows-only.
- Add guidance for Linux/macOS users on setting up Service Fabric CLI tools and connecting to clusters.
- Present Azure CLI and sfctl examples before or alongside PowerShell, rather than after.
- Include troubleshooting notes for common Linux/macOS issues (e.g., permissions, environment variables).
Service Fabric
Common questions about Microsoft Azure Service Fabric
...cles/service-fabric/service-fabric-common-questions.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page exhibits several signs of Windows bias. Examples and recommendations often reference Windows-specific tools (e.g., PowerShell, Windows Server upgrade paths), and anti-virus exclusions list only Windows directories and processes. Where authentication to Key Vault is discussed, PowerShell is suggested as the method, with no mention of Linux alternatives. There are no explicit Linux or bash examples, and Windows terminology (e.g., 'Program Files') is used exclusively. Linux/macOS users may find it difficult to map these instructions to their environments.
Recommendations
- Provide Linux/macOS equivalents for all Windows-specific instructions, such as bash scripts or CLI commands.
- List anti-virus exclusions for Linux-based clusters, including relevant directories and processes.
- When discussing OS upgrades, include guidance for Linux distributions (e.g., Ubuntu, CentOS) alongside Windows Server.
- Offer authentication examples using cross-platform tools (e.g., Azure CLI, REST API) in addition to PowerShell.
- Avoid using Windows terminology exclusively; clarify when instructions are OS-specific.
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
windows_tools
missing_linux_example
Summary
The documentation shows a moderate Windows bias. PowerShell examples are provided alongside CLI, but references to Windows tools (like Sysprep) and Windows-specific links appear before or more prominently than Linux equivalents. Some sections (e.g., image generalization, uploading VHDs) mention Windows first or link to Windows-specific guides before Linux ones. There are also references to Azure PowerShell and .NET SDK, which are more commonly used on Windows, with less emphasis on cross-platform or Linux-native tooling. Linux examples are present but sometimes secondary.
Recommendations
- Ensure CLI examples are shown before or alongside PowerShell, as Azure CLI is cross-platform.
- When mentioning OS-specific tools (e.g., Sysprep for Windows, waagent for Linux), present both equally and in parallel, not Windows first.
- Provide direct links to Linux documentation and examples wherever Windows links are given.
- Highlight cross-platform SDKs and tools (Python, Go, Node.js) more prominently.
- Add explicit Linux/macOS command-line examples where only PowerShell is shown.
- Review and balance the order of OS references in tables and lists.
Service Fabric
Upgrade Linux OS for Azure Service Fabric
...es/service-fabric/service-fabric-cluster-upgrade-os.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation page for upgrading Linux OS in Azure Service Fabric is heavily focused on Az PowerShell cmdlets for cluster management tasks, with step-by-step examples provided only in PowerShell. While the scenario is Linux-specific, the management tooling and examples are Windows-centric, and PowerShell is presented as the primary interface for critical operations. Linux-native alternatives (e.g., Azure CLI, Bash scripts) are not mentioned or demonstrated, and PowerShell examples appear before any Linux command-line instructions.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell cmdlets, especially for cluster and node type management.
- Provide Bash script samples for common tasks, such as updating vmImage, adding/removing node types, and querying cluster state.
- Explicitly mention that Az PowerShell can be run cross-platform, but highlight native Linux management options.
- Reorder examples so that Linux-native tools (Azure CLI, Bash) are shown before or alongside PowerShell.
- Clarify prerequisites for Linux users, such as installing Azure CLI, sfctl, and jq, and provide links to their documentation.
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 displays a Windows bias by consistently referencing Windows-specific upgrade guides and tools, such as linking to 'service-fabric-cluster-upgrade-windows-server.md' and 'service-fabric-cluster-config-upgrade-windows-server.md' for upgrade instructions. The Patch Orchestration Application is described as 'for Windows,' with no mention of Linux equivalents or guidance. There are no Linux/macOS-specific examples, instructions, or links, and Windows terminology is used exclusively.
Recommendations
- Include parallel documentation links and instructions for Linux-based Service Fabric clusters, if supported.
- Explicitly mention whether features like Patch Orchestration Application are available or not for Linux clusters.
- Provide configuration and upgrade examples for Linux environments, including relevant file paths, commands, and tools.
- Clarify platform support in each section to help users on non-Windows systems understand applicability.
Service Fabric
Upgrading Azure Service Fabric clusters
...icles/service-fabric/service-fabric-cluster-upgrade.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page exhibits moderate Windows bias. While most upgrade instructions are platform-neutral, several management actions (certificate management, port opening, etc.) mention PowerShell and Azure CLI, but do not provide explicit Linux/macOS guidance or examples. The OS patching section links only to Windows-specific instructions, with no mention of Linux node patching. The Patch Orchestration Application is described only in the context of Windows. Windows terminology (NTLM, FileStoreService) is referenced without Linux alternatives or caveats.
Recommendations
- Provide explicit Linux/macOS examples for all CLI operations, including certificate management and port opening.
- Include links or sections for patching Linux-based Service Fabric clusters, if supported.
- Clarify whether Patch Orchestration Application and OS image upgrades are available for Linux clusters, and provide instructions if so.
- When mentioning Windows-specific features (e.g., NTLM, FileStoreService), note Linux equivalents or limitations.
- Ensure that Azure CLI examples are presented in a cross-platform manner, and avoid PowerShell-only instructions.
Service Fabric
Scalability of Service Fabric services
.../service-fabric/service-fabric-concepts-scalability.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a Windows bias by providing PowerShell examples exclusively for service scaling operations, referencing Windows-specific tools and cmdlets (e.g., Update-ServiceFabricService, New-ServiceFabricService), and omitting equivalent Linux CLI or script examples. Windows tooling is mentioned first and most prominently, while Linux alternatives are not presented, creating friction for Linux users.
Recommendations
- Add equivalent Linux CLI examples (e.g., using Service Fabric CLI (sfctl) or REST API) alongside PowerShell commands.
- Explicitly mention Linux-compatible tools and workflows for scaling operations.
- Present examples for both platforms in parallel, or clarify platform-specific differences where relevant.
- Avoid referencing Windows tools/cmdlets exclusively; provide parity in documentation structure and examples.
Service Fabric
Azure Service Fabric application resource model
...ervice-fabric/service-fabric-concept-resource-model.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a notable Windows bias: all command-line deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) with no mention of Azure CLI equivalents, which are cross-platform. The application packaging workflow is described using Visual Studio (Windows-only) and Windows file paths, with no alternatives for Linux/macOS users (e.g., dotnet CLI, Service Fabric SDK for Linux, or cross-platform zip tools). Screenshots and instructions assume Azure Portal usage but do not address Linux/macOS workflows or tools.
Recommendations
- Add Azure CLI examples for deployment and resource management (e.g., az deployment group create, az resource delete).
- Include instructions for packaging Service Fabric applications using cross-platform tools (e.g., dotnet CLI, zip command).
- Provide alternative steps for Linux/macOS users, such as using VS Code or command-line utilities instead of Visual Studio.
- Present examples for both Windows and Linux/macOS, or use cross-platform commands first.
- Explicitly state that the workflow is supported on Linux/macOS and link to relevant documentation.
Service Fabric
Connect securely to an Azure Service Fabric cluster
...ice-fabric/service-fabric-connect-to-secure-cluster.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates a notable Windows bias. PowerShell is the only scripting example for connecting to clusters, with no Linux shell or bash equivalents for key operations. Certificate installation instructions are detailed for Windows (including PowerShell commands), but for Mac and Linux, only minimal or generic guidance is provided. Windows-specific tools and terminology (e.g., certificate stores, PowerShell cmdlets) are used throughout, and Windows instructions are consistently presented before alternatives. There are no Linux-specific examples for connecting via CLI or managing certificates.
Recommendations
- Add Linux-specific examples for connecting to clusters, including bash commands and instructions for common Linux distributions.
- Provide certificate installation steps for Linux (e.g., using openssl, certutil, or browser settings for Firefox/Chrome).
- Include parity for PowerShell commands with bash or shell equivalents, especially for certificate management.
- Clearly separate platform-specific instructions and ensure Linux/macOS guidance is as detailed as Windows.
- Mention cross-platform tools (e.g., sfctl, openssl) first, or in parallel, rather than defaulting to Windows tools.
Service Fabric
Azure Files volume driver for Service Fabric
...ic/service-fabric-containers-volume-logging-drivers.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
minor_windows_paths
manifest_windows_examples
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific details, examples, and tools (PowerShell, Windows paths, Windows Server versioning) are frequently presented first or exclusively, especially in deployment and configuration sections. While Linux equivalents are present in most command-line examples, Windows-centric tools and patterns (PowerShell, Windows paths, Windows Server versioning) are emphasized, and manifest examples use Windows-style paths. The recommended deployment script is PowerShell-only, requiring Linux users to run PowerShell scripts, which may not be native to their environment.
Recommendations
- Provide Bash or shell script equivalents for the recommended PowerShell deployment, or document how to run the PowerShell script on Linux/macOS (e.g., via pwsh).
- Ensure manifest examples include both Windows and Linux path conventions (e.g., c:\... and /mnt/...).
- When listing prerequisites, mention Linux requirements and tools (e.g., Bash, SFCTL) before or alongside Windows ones.
- Clarify how Linux/macOS users can perform all steps without relying on Windows-only tooling.
- Add explicit Linux/macOS sample manifests and deployment walkthroughs.
- Where possible, avoid using Windows-specific terminology or paths as defaults in cross-platform documentation.
Service Fabric
Induce Chaos in Service Fabric clusters
...cles/service-fabric/service-fabric-controlled-chaos.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation provides detailed examples for running Chaos in Service Fabric using C# and PowerShell, both of which are Windows-centric. PowerShell is a Windows-native tool, and no equivalent Linux/macOS CLI or shell examples are given. References to Service Fabric PowerShell modules and cmdlets are present, but there is no mention of Linux-compatible tools (e.g., Bash, Azure CLI, or REST usage from curl). This creates friction for Linux/macOS users, who must infer how to perform these tasks without direct guidance.
Recommendations
- Add Linux/macOS-friendly examples, such as using Bash with curl to invoke the REST API for Chaos operations.
- Include instructions for using Azure CLI (if supported) to manage Chaos runs.
- Explicitly mention cross-platform alternatives to PowerShell, or clarify if PowerShell Core is supported on Linux/macOS.
- Reorder examples so that platform-neutral (REST API) or cross-platform methods are presented first, followed by platform-specific ones.
- Document any prerequisites or limitations for Linux/macOS users, such as Service Fabric SDK support or required tools.
Service Fabric
Create a cluster using certificate common name
...-fabric/service-fabric-create-cluster-using-cert-cn.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page exclusively provides PowerShell examples for certificate upload and cluster deployment, with file paths and commands tailored to Windows environments. There are no CLI, Bash, or Linux/macOS-specific instructions, nor any mention of cross-platform alternatives. This creates friction for Linux/macOS users who may not have access to PowerShell or Windows-style file paths.
Recommendations
- Add equivalent Azure CLI (az) commands for certificate upload and cluster deployment, which are cross-platform.
- Include Bash examples for Linux/macOS users, especially for file paths and scripting.
- Explicitly mention that the process can be completed on Linux/macOS and provide guidance or links to relevant documentation.
- Avoid using Windows-specific file paths (e.g., C:\users\sfuser\...) in generic instructions; use environment-neutral paths or provide alternatives.
- Clarify tool requirements and suggest installation steps for non-Windows platforms if PowerShell is required.
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page is mostly platform-neutral, but there is a subtle Windows bias in the 'Feature support' section, where 'Nested Virtualization' links exclusively to a Windows/Hyper-V guide. In the networking section, bandwidth/throughput testing references NTTTCP, a Microsoft tool primarily associated with Windows, without mentioning Linux alternatives or providing parity. Windows terminology and tools are mentioned before Linux equivalents (if any), and Linux-specific guidance is minimal.
Recommendations
- Include links or references to Linux-specific nested virtualization documentation (e.g., KVM/QEMU).
- Mention and provide examples of Linux-compatible bandwidth/throughput testing tools (e.g., iperf, netperf) alongside NTTTCP.
- Where Windows tools are referenced, add Linux alternatives and usage notes to ensure parity.
- Review all feature support links to ensure Linux documentation is equally represented.
Virtual Machines
Enable Trusted launch on existing Gen2 VMs
...rticles/virtual-machines/trusted-launch-existing-vm.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation provides parity for both Linux and Windows VMs in terms of Azure CLI, Portal, and ARM template instructions. However, there is a notable bias towards Windows/PowerShell tooling: PowerShell examples are given equal prominence to CLI, and ARM template deployment steps use PowerShell exclusively. The documentation references RDP for Windows and SSH for Linux, but PowerShell is presented as a primary automation tool, which is Windows-centric. There are no Linux shell (bash) equivalents for ARM template deployment, and PowerShell is referenced in places where cross-platform alternatives exist.
Recommendations
- Add bash (Linux shell) examples for ARM template deployment, using Azure CLI or native bash commands.
- Clarify that PowerShell examples are for users on Windows, and provide equivalent instructions for Linux/macOS users.
- Where PowerShell is used for automation, offer Azure CLI or bash alternatives, especially for template deployments.
- Ensure that cross-platform tools (Azure CLI, REST API) are mentioned before or alongside Windows-specific tools.
- Explicitly state that all steps can be performed from Linux/macOS using Azure CLI and provide links to relevant installation guides.
Virtual Machines
List, update, and delete resources
...in/articles/virtual-machines/update-image-resources.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all major operations. However, PowerShell examples are given equal prominence and detail as CLI, despite PowerShell being primarily a Windows tool. In some sections, PowerShell examples appear immediately after CLI, and REST examples are included only for listing shared galleries, not for update or delete operations. There are no Linux-specific shell examples (e.g., bash scripting), and PowerShell is presented as a cross-platform option, which may not reflect typical Linux/macOS usage patterns.
Recommendations
- Clarify that PowerShell is available cross-platform, but most Linux/macOS users prefer bash or shell scripting with Azure CLI.
- Add explicit bash/zsh shell script examples for common Linux/macOS workflows, especially for tasks involving variables, loops, or output parsing.
- Consider including REST API examples for update and delete operations to provide a platform-neutral alternative.
- Where PowerShell is presented, note its installation and usage on Linux/macOS, or link to guidance for non-Windows users.
- If possible, show CLI examples using both Windows (cmd/PowerShell) and Linux/macOS (bash/zsh) syntax for variable assignment and command chaining.
Virtual Machines
Manage, Update, and Delete VM Applications on Azure
...in/articles/virtual-machines/vm-applications-manage.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides parity across Azure Portal, REST, CLI, and PowerShell for managing VM Applications, but PowerShell examples (which are Windows-centric) are always present and sometimes referenced in CLI scripting notes. In scripting sections, PowerShell is used for advanced CLI scripting, and PowerShell tabs are always included, suggesting a Windows-first approach. However, Azure CLI examples are present and suitable for Linux/macOS, and REST API usage is platform-neutral. No critical steps are Windows-only, but the prominence of PowerShell and its use in scripting guidance may create friction for Linux/macOS users.
Recommendations
- Where scripting is shown with PowerShell for CLI, provide equivalent Bash examples for Linux/macOS users.
- Explicitly note that Azure CLI commands work on Linux/macOS and provide sample Bash scripting for multi-instance operations.
- Consider alternating the order of CLI and PowerShell tabs, or defaulting to CLI in documentation targeting cross-platform users.
- Add a short section clarifying tool parity and platform support, reassuring Linux/macOS users they can perform all tasks.
- Review any advanced scripting examples to ensure Bash alternatives are present and clear.
Service Fabric
Azure Service Fabric deployment with FabricClient
...service-fabric-deploy-remove-applications-fabricclient.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page exhibits a notable Windows bias. It references Visual Studio and PowerShell as primary tools for packaging and deploying Service Fabric applications, with file paths and workflows that are Windows-centric. All example paths use Windows conventions (e.g., C:\Users\...), and troubleshooting steps rely on PowerShell cmdlets and Windows SDK modules. There are no Linux/macOS equivalents or examples, nor is there guidance for performing these tasks on non-Windows platforms.
Recommendations
- Add explicit instructions and examples for Linux/macOS users, including file path conventions and alternative tools.
- Provide CLI-based workflows (e.g., using Service Fabric CLI 'sfctl') alongside PowerShell examples, and reference them equally.
- Clarify which steps are platform-agnostic and which require Windows-specific tools, offering alternatives where possible.
- Include troubleshooting steps for Linux environments, such as using Bash scripts or sfctl commands.
- Document how to package and upload applications from Linux/macOS, including any required SDKs or dependencies.
Service Fabric
Deploy a cluster across Availability Zones
...vice-fabric/service-fabric-cross-availability-zones.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
missing_linux_example
Summary
The documentation page exhibits a notable Windows bias, especially in the migration section, where all operational examples are provided exclusively in PowerShell, referencing Windows-centric tools and patterns (e.g., disabling nodes, removing resources, updating DNS). There is no mention of equivalent Linux/macOS CLI commands (such as Azure CLI or bash scripts), and the only sample template link for Linux (Ubuntu) does not include operational steps. Windows/PowerShell instructions are presented first and exclusively for critical migration tasks, creating friction for Linux/macOS users.
Recommendations
- Provide equivalent Azure CLI (az) or bash script examples for all operational steps, especially in migration and resource management sections.
- Explicitly mention cross-platform tooling options (e.g., Azure CLI, REST API) alongside PowerShell.
- Add a Linux/macOS migration walkthrough, including disabling nodes, removing resources, and updating DNS using non-Windows tools.
- Ensure sample templates and code snippets are available for both Windows and Linux deployments, and reference them equally.
- Where PowerShell is used, add a note or table mapping each command to its Azure CLI equivalent.
Service Fabric
Overview of Azure and standalone Service Fabric clusters
...icles/service-fabric/service-fabric-deploy-anywhere.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_first
Summary
The documentation discusses Service Fabric clusters on both Windows Server and Linux, but it highlights that standalone clusters are not available on Linux. There are no Linux-specific examples, tools, or operational guidance, and the text generally references Windows Server first. This creates a bias toward Windows environments, especially for standalone deployments.
Recommendations
- Explicitly state the limitations and alternatives for Linux users regarding standalone clusters.
- Provide Linux-specific guidance or links for deploying Service Fabric clusters in supported scenarios.
- Include operational examples or references for Linux environments where Service Fabric is supported.
- Balance the order of mention between Windows and Linux to avoid implicit prioritization.
Service Fabric
Deploy an existing executable to Azure Service Fabric
...s/service-fabric/service-fabric-deploy-existing-app.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a notable Windows bias. Windows tooling (Visual Studio, PowerShell) is presented first and in greater detail, with step-by-step instructions and explanations. Linux alternatives (Yeoman, manual packaging) are mentioned after Windows tools, with less detail and fewer examples. The deployment section only provides a PowerShell script for Windows, with no equivalent Bash or CLI example for Linux. Batch files and Windows-specific patterns (e.g., .cmd scripts) are referenced in examples, while Linux shell scripts are not. This creates friction for Linux/macOS users who may struggle to adapt Windows-centric instructions.
Recommendations
- Provide Bash or Azure CLI deployment examples for Linux/macOS users alongside the PowerShell script.
- Include Linux shell script examples (e.g., .sh) in the SetupEntrypoint section, not just .cmd batch files.
- Expand the Yeoman section with more detailed, step-by-step instructions and screenshots, matching the depth of the Visual Studio walkthrough.
- Present Windows and Linux tooling in parallel, or alternate which is shown first, to avoid implicit prioritization.
- Add troubleshooting and verification steps for Linux/macOS environments, similar to those shown for Windows.
Service Fabric
Azure Service Fabric Diagnose Common Scenarios
...-fabric/service-fabric-diagnostics-common-scenarios.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates mild Windows bias, particularly in the monitoring and diagnostics sections. Windows terminology and examples (such as '.NET CLR Memory', 'Windows Performance Counters') are presented first and in detail, while Linux equivalents are mentioned only briefly or parenthetically. There are no explicit Linux command-line or tool examples, and most counter examples are Windows-specific. The documentation assumes familiarity with Windows-centric tools and patterns, with Linux support referenced but not illustrated.
Recommendations
- Provide explicit Linux examples for performance counters, including sample Linux counter names and formats.
- Include screenshots or walkthroughs of the Linux-specific UI paths (e.g., 'Data > Linux Performance Counters').
- Add sample queries and alert rules for Linux-specific metrics (such as CPU, memory, and disk counters).
- Clarify any differences in setup or troubleshooting steps for Linux clusters.
- Ensure parity in diagnostic tool recommendations, mentioning Linux-compatible agents and solutions where relevant.
Service Fabric
Azure Service Fabric Event Aggregation with EventFlow
...service-fabric-diagnostics-event-aggregation-eventflow.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows development tools (Visual Studio, Solution Explorer, Debug output window) and omitting Linux/macOS equivalents or instructions. All setup and verification steps assume a Windows environment, with no mention of cross-platform alternatives (e.g., dotnet CLI, VS Code, Linux file paths, or terminal commands). This creates friction for developers working on Linux or macOS, who may not use Visual Studio or have access to Windows-specific UI elements.
Recommendations
- Add instructions for installing EventFlow NuGet packages using the dotnet CLI (e.g., 'dotnet add package') for Linux/macOS users.
- Include guidance for editing configuration files and setting build actions outside of Visual Studio, such as using VS Code or command-line tools.
- Provide verification steps that work on Linux/macOS, such as viewing logs in the terminal or using cross-platform IDEs.
- Mention file paths and project structure conventions for non-Windows environments.
- Explicitly state that the instructions apply to all platforms, and highlight any platform-specific considerations.
Service Fabric
Event Aggregation with Microsoft Azure Diagnostics
...ic/service-fabric-diagnostics-event-aggregation-wad.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page exhibits a notable Windows bias. It focuses almost exclusively on the Windows Azure Diagnostics (WAD) extension, with all configuration examples, templates, and code snippets tailored to Windows clusters. Windows-specific tools (PowerShell, Visual Studio Diagnostic Event Viewer, ETW logs) are referenced throughout, and all step-by-step instructions use Windows terminology and patterns. There is no coverage of Linux diagnostics (LAD) or Linux-specific configuration, nor any Linux command-line examples. Although a selector for Linux documentation is present at the top, this page itself is Windows-centric and does not provide Linux parity.
Recommendations
- Add equivalent Linux (LAD) configuration examples and templates directly to this page, or clearly link to them in each relevant section.
- Include Linux command-line instructions (e.g., Azure CLI, Bash) alongside PowerShell examples.
- Reference Linux-compatible tools for viewing and analyzing logs (e.g., less, grep, Kibana, etc.), not just Visual Studio.
- Clarify which instructions and templates are Windows-only, and provide guidance for Linux clusters where steps differ.
- Ensure that all major sections (deployment, configuration, log analysis) have Linux-specific guidance or links.
Service Fabric
Azure Service Fabric Events
...es/service-fabric/service-fabric-diagnostics-events.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by primarily referencing Windows-centric logging mechanisms (ETW/Windows Event logs), mentioning the Windows Azure diagnostics agent, and omitting explicit instructions or examples for accessing Service Fabric events on Linux clusters. There are no Linux-specific event access patterns or tools discussed, nor is parity established in example order or detail.
Recommendations
- Add explicit instructions and examples for accessing Service Fabric events on Linux clusters, such as using Linux diagnostics agents or syslog integration.
- Mention Linux-compatible monitoring tools and logging channels (e.g., journald, syslog) alongside Windows Event logs.
- Clarify whether the EventStore REST APIs and Service Fabric Client Library are fully cross-platform, and provide usage examples on Linux/macOS.
- Ensure documentation sections reference both Windows and Linux approaches equally, ideally presenting cross-platform methods first.
Service Fabric
Set up monitoring with Azure Monitor logs
...service-fabric/service-fabric-diagnostics-oms-setup.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
powershell_heavy
Summary
The documentation page demonstrates a notable Windows bias: Windows clusters and tools (such as PowerShell and WAD) are referenced first and in detail, with Linux-specific instructions relegated to external links. All code examples use PowerShell, with no Linux CLI or Bash equivalents. The Service Fabric Analytics solution is stated to be Windows-only, and Linux users are repeatedly redirected elsewhere, with no direct guidance or parity in examples.
Recommendations
- Include direct Linux/Bash/CLI examples alongside PowerShell commands for deploying and configuring Azure Monitor logs.
- Provide a step-by-step Linux workflow for connecting clusters to Log Analytics, not just a link to another article.
- Clarify which features are Windows-only and offer Linux alternatives or workarounds in the same document.
- Present instructions for both platforms side-by-side or clearly label platform-specific sections.
- Reference Linux tools (e.g., OMSAgent, syslog integration) with equal prominence and detail as Windows tools (WAD, PowerShell).
Service Fabric
Monitor Linux cluster events in Azure Service Fabric
...ervice-fabric/service-fabric-diagnostics-oms-syslog.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page is focused on monitoring Service Fabric events for Linux clusters via Syslog, but the configuration examples and terminology reference Windows-oriented tools and patterns (e.g., 'AzureWinFabCsv', 'AzureWinFabCrashDump', 'AzureTableWinFabEtwQueryable', 'WinFabLttProducer') before or alongside the Linux-specific SyslogConsumer. The naming and example values in configuration are Windows-centric, which may create confusion for Linux users. However, the core instructions are Linux-relevant and do not prevent Linux users from completing the task.
Recommendations
- Provide Linux-specific configuration examples that omit or clarify the purpose of Windows-related consumer instances.
- Explain the relevance (or irrelevance) of Windows-named parameters for Linux clusters.
- List Linux-relevant tools and patterns first, and clarify which configuration items are required for Linux clusters only.
- Add a note to explicitly distinguish between Windows and Linux configuration sections.
Service Fabric
Azure Service Fabric DNS service
...n/articles/service-fabric/service-fabric-dnsservice.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page demonstrates several Windows biases. Windows clusters are described as fully supported, while Linux support is called out as limited and with restrictions. Examples for setting DNS names via PowerShell are provided, but there are no equivalent Linux CLI or Bash examples. The ApplicationManifest.xml example references Visual Studio, a Windows-centric tool. Enabling DNS service via the Azure portal is described as available for Windows but not for Linux clusters, with no Linux-specific alternatives shown first or in detail. The limitations section reiterates Linux restrictions, but does not offer Linux workarounds or parity guidance.
Recommendations
- Provide Linux-specific CLI examples (e.g., Bash, Azure CLI, or REST API) for tasks currently shown only with PowerShell.
- Include instructions for enabling DNS service on Linux clusters using supported methods (e.g., ARM templates, CLI), with step-by-step guidance.
- Offer guidance for editing ApplicationManifest.xml using cross-platform editors and tools, not just Visual Studio.
- Present Linux alternatives or parity information alongside Windows instructions, rather than only listing limitations.
- Add troubleshooting and workaround sections specifically for Linux users where features are limited.
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
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by presenting PowerShell-based deployment instructions first and in greater detail, with no equivalent Linux/macOS shell or script examples for the PowerShell commands. The CLI (sfctl) section is present but comes after the PowerShell examples, and the documentation refers to Windows-specific features (e.g., 'Isolation (only for Windows)'). There is no mention of Linux/macOS-specific guidance, nor are there bash or shell script equivalents for the PowerShell commands.
Recommendations
- Provide Linux/macOS shell (bash/zsh) equivalents for all PowerShell commands, especially for deployment, status checks, upgrades, and rollbacks.
- Present CLI (sfctl) instructions before or alongside PowerShell examples to avoid Windows-first ordering.
- Explicitly mention platform compatibility for each tool and command, clarifying which steps work on Linux/macOS.
- Add notes or sections for Linux/macOS users, including any prerequisites or differences in setup.
- Where Windows-only features are mentioned (e.g., Isolation), clarify alternatives or limitations for Linux/macOS.
Service Fabric
Enable disk encryption for Linux clusters
...c/service-fabric-enable-azure-disk-encryption-linux.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation page for enabling disk encryption for Linux clusters in Azure Service Fabric exhibits a moderate Windows bias. PowerShell commands are presented first and in greater detail throughout, with explicit references to Windows-style paths (e.g., c:\certificates) and reliance on PowerShell-specific tooling. Although Azure CLI examples are provided for most steps, PowerShell is consistently prioritized and some instructions (such as certificate handling) are more Windows-centric. There is minimal mention of Linux-native tools or shell scripting, and the use of Windows file paths in Linux contexts may confuse non-Windows users.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and preferred for Linux/macOS users.
- Replace Windows-style file paths (e.g., c:\certificates) with Linux-style paths (e.g., /home/user/certificates) in Linux-specific documentation.
- Include bash shell scripting examples for certificate password handling and file manipulation.
- Clarify any steps that require PowerShell, and provide Linux-native alternatives or note platform limitations.
- Add explicit notes or sections for Linux/macOS users, highlighting differences in environment setup and command usage.
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
windows_tools
Summary
The documentation provides a detailed conceptual overview of Service Fabric health monitoring, but the only concrete example for reporting and querying health uses Windows PowerShell cmdlets. There are no equivalent examples for Linux/macOS users (e.g., using Bash, REST API, or cross-platform CLI tools). The documentation also references PowerShell as a primary mechanism for interacting with Service Fabric health, without mentioning Linux-compatible alternatives or providing parity in example coverage.
Recommendations
- Add equivalent health reporting and querying examples using Bash and the Service Fabric CLI (sfctl), which is cross-platform.
- Include REST API examples for health reporting and querying, as these are platform-agnostic.
- Explicitly mention Linux/macOS support and tools (e.g., sfctl, REST) alongside PowerShell in all sections discussing health reporting.
- Reorder examples or provide both Windows and Linux/macOS examples side-by-side to ensure parity.
- Link to documentation pages that describe Linux/macOS usage of Service Fabric health features.
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
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell as the primary tool for interacting with Service Fabric clusters, mentioning Visual Studio for publishing (a Windows-centric IDE), and linking to PowerShell-based deployment guides. There are no explicit Linux or macOS command-line examples, nor are cross-platform tools like Azure CLI or Bash scripts mentioned. The documentation assumes a Windows development environment and does not provide guidance for Linux/macOS users.
Recommendations
- Add examples using Azure CLI or REST API for cluster manifest retrieval and application deployment, which are cross-platform.
- Include instructions for deploying applications from Linux/macOS environments, possibly with Bash or Python scripts.
- Reference cross-platform editors (e.g., VS Code) in addition to Visual Studio.
- Link to documentation pages that describe Linux/macOS workflows for Service Fabric.
- Explicitly state platform compatibility for each tool or method mentioned.
Service Fabric
Package an existing executable to Azure Service Fabric
...abric/service-fabric-guest-executables-introduction.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page exhibits a Windows bias by referencing Windows-specific tools and paths (e.g., Service Fabric SDK installed in 'C:\Program Files\...'), mentioning Visual Studio as a primary packaging/deployment method, and omitting explicit Linux/macOS equivalents or examples. There are no Linux/macOS-specific instructions, examples, or tool references, which may create friction for non-Windows users.
Recommendations
- Add explicit instructions and examples for packaging and deploying guest executables from Linux/macOS environments, including command-line utilities and file paths.
- Reference cross-platform tools (such as Azure CLI, Service Fabric CLI) and provide parity in documentation for Linux/macOS users.
- Include sample directory structures and manifest file locations as they would appear on Linux/macOS systems.
- Mention alternative IDEs or editors for Linux/macOS users, not just Visual Studio.
- Clarify whether the Service Fabric SDK and packaging tools are available and supported on Linux/macOS, and provide installation instructions if so.
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_tools
windows_first
Summary
The documentation page demonstrates a moderate Windows bias. The 'Next steps' section specifically directs users to PowerShell-based deployment and removal instructions, and the only example for downloading a ServicePackage in advance links to a PowerShell cmdlet. There are no explicit Linux or cross-platform CLI examples, and Windows tools (PowerShell) are mentioned exclusively for operational tasks, suggesting a Windows-first approach.
Recommendations
- Include equivalent Linux/macOS instructions using Azure CLI, Service Fabric CLI (sfctl), or REST API where possible.
- Provide cross-platform examples side-by-side, especially for deployment, removal, and package management tasks.
- Reference documentation pages for Linux/macOS workflows in the 'Next steps' section.
- Clarify which steps or tools are platform-specific and offer alternatives for non-Windows environments.
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_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a notable Windows bias. All command-line examples use PowerShell cmdlets (e.g., New-ServiceFabricService), and there are no equivalent CLI or bash examples for Linux/macOS users. References to management operations (deploy, remove, query) link exclusively to PowerShell modules, and the 'Next steps' section explicitly describes using PowerShell to manage applications. There is no mention of Azure CLI, Service Fabric CLI (sfctl), or bash scripting, which are the primary tools for Linux/macOS environments.
Recommendations
- Add equivalent examples using Azure CLI (az sf) and/or Service Fabric CLI (sfctl) for all PowerShell commands.
- Include bash shell examples where appropriate, especially for service creation and management.
- Reference cross-platform tools (Azure CLI, sfctl, REST API) before or alongside PowerShell, not exclusively after.
- Clarify in the 'Next steps' and relevant sections that management can be performed from Linux/macOS using CLI tools.
- Where PowerShell is mentioned, explicitly note its cross-platform availability or provide alternatives for non-Windows users.
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
windows_tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell and Visual Studio (Windows-centric tools) are mentioned first and in more detail when describing how to pass parameters during application creation. The use of PowerShell cmdlets and Visual Studio parameter files is emphasized, while Linux/macOS workflows (such as sfctl and install.sh) are mentioned but not elaborated upon. There is also a reference to Azure DevOps and Jenkins for string substitution, but the examples and guidance lean toward Windows tooling.
Recommendations
- Provide equivalent Linux/macOS command-line examples (e.g., bash scripts, sfctl usage) alongside PowerShell examples.
- Expand on the use of sfctl and install.sh for Linux/macOS users, including sample commands and parameter file handling.
- Include guidance for non-Windows IDEs or editors (such as VS Code) for managing parameter files.
- Ensure that references to deployment workflows (e.g., Jenkins) include both Windows and Linux script examples.
- Consider reordering examples so that Linux/macOS options are presented alongside or before Windows options.
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 demonstrates a notable Windows bias. The manifest examples are based on a Windows Server 2016 container sample, and Windows-specific tools and patterns (such as 'winver' for OS build detection and 'c:\VolumeTest\Data' paths) are referenced. Windows instructions and terminology (e.g., PFX certificates, LocalMachine store) are given before or instead of Linux equivalents. There are no Linux-specific manifest examples, and Linux/macOS users are left to infer how to adapt the instructions.
Recommendations
- Provide equivalent Linux-based manifest examples, referencing Linux container images and filesystem paths (e.g., '/mnt/VolumeTest/Data').
- Explicitly mention Linux/macOS procedures for tasks like OS build detection (e.g., 'cat /etc/os-release') and certificate handling (PEM format, Linux certificate stores).
- Clarify cross-platform differences in resource governance, volume drivers, and certificate import, with side-by-side instructions or notes.
- Avoid referencing Windows tools (e.g., 'winver') without Linux alternatives.
- Ensure all features and patterns are described for both Windows and Linux environments, or clearly state any platform limitations.
Service Fabric
Change FabricTransport settings
...service-fabric-reliable-actors-fabrictransportsettings.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page exhibits Windows bias by exclusively referencing Windows certificate store concepts (e.g., 'LocalMachine', 'My'), using Windows-centric certificate subject names (e.g., 'WinFabric-Test-SAN1-Alice'), and omitting Linux-specific configuration examples. Although there is a brief note about PEM certificates for Linux, all XML configuration samples and parameter values are tailored to Windows environments, with no guidance for Linux equivalents.
Recommendations
- Add explicit Linux configuration examples, including how to specify certificate paths and stores on Linux nodes.
- Clarify which parameters are Windows-only (e.g., 'CertificateStoreLocation', 'CertificateStoreName') and provide Linux alternatives or note if they should be omitted.
- Include sample XML snippets for Linux, demonstrating PEM certificate usage and typical Linux certificate paths.
- Use neutral or Linux-relevant subject names in examples, not just 'WinFabric-Test-SAN1-Alice/Bob'.
- Provide a table or section comparing Windows and Linux certificate configuration parameters and behaviors.
Service Fabric
Reliable services app manifest examples
...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-manifest-example-reliable-services-app.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
powershell_heavy
windows_first
Summary
The documentation page demonstrates a Windows bias through references to Windows-specific tools and patterns, such as mentioning ServiceFabric PowerShell modules for service creation, using .exe and .bat files for entry points, and referencing Windows accounts (NetworkService, Administrators). There is no mention of Linux equivalents, nor are Linux-specific examples (e.g., shell scripts, Linux user/group patterns) provided. The documentation assumes Windows conventions throughout, which may create friction for Linux/macOS users.
Recommendations
- Add Linux-specific examples, such as using shell scripts (.sh) for SetupEntryPoint and EntryPoint, and clarify how to configure these for Linux clusters.
- Document Linux user/group equivalents and how Service Fabric maps or creates principals on Linux nodes.
- Include instructions or references for managing Service Fabric applications using Linux CLI tools (e.g., sfctl) instead of only PowerShell.
- Explicitly note differences in resource governance, endpoint configuration, and security policies between Windows and Linux clusters.
- Reorder examples or add parallel Linux sections so that Linux users do not have to mentally translate Windows patterns.
Service Fabric
Package an Azure Service Fabric app
...articles/service-fabric/service-fabric-package-apps.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page exhibits a notable Windows bias. All command-line examples use Windows-specific tools (tree, msbuild.exe, PowerShell cmdlets), and all file paths are Windows-style. Visual Studio is presented as the primary packaging tool, with no mention of Linux/macOS alternatives. There are no Linux shell or cross-platform examples for packaging, testing, or compressing Service Fabric applications. PowerShell is used exclusively for validation and compression, with no Bash or CLI alternatives provided.
Recommendations
- Add equivalent Linux/macOS examples for directory structure (e.g., using 'tree' or 'ls' with Unix paths).
- Document how to package Service Fabric applications using cross-platform .NET CLI (dotnet) or msbuild on Linux/macOS.
- Provide instructions for validating and compressing packages using Service Fabric CLI (sfctl) or REST API, where available.
- Include file path examples in both Windows and Unix formats.
- Clarify which steps/tools are Windows-only and offer alternatives for Linux/macOS users.
- Mention any platform limitations explicitly so users can plan accordingly.
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
windows_tools
Summary
The documentation page demonstrates a notable Windows bias: all deployment and management examples use PowerShell commands, with no mention of Azure CLI, Bash, or Linux/macOS alternatives. Windows tools and patterns (such as RDP and Windows-style file paths) are referenced exclusively, and Windows-centric terminology is used throughout. There are no Linux/macOS-specific instructions or examples, which could create friction for non-Windows users.
Recommendations
- Provide equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Include Bash script snippets and Linux/macOS terminal commands where relevant, especially for deployment and resource management.
- Mention SSH as an alternative to RDP for accessing VMs, and provide instructions for both.
- Use platform-neutral file paths and command syntax in examples, or show both Windows and Linux/macOS variants.
- Explicitly state that all templates and procedures are compatible with Linux/macOS, and highlight any platform-specific considerations.
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_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates a notable Windows bias. PowerShell is heavily featured for command-line examples, with no mention of Linux/macOS equivalents (such as Bash, CLI, or cross-platform tools). Windows-specific tools and patterns (PowerShell cmdlets, Windows paths) are presented exclusively and before REST or API alternatives. There are no Linux/macOS shell examples, nor guidance for users on non-Windows platforms.
Recommendations
- Add equivalent examples using Azure CLI, Bash, or other cross-platform tools for health reporting and querying.
- Explicitly mention Linux/macOS compatibility for Service Fabric health reporting, including any required setup or differences.
- Provide REST API usage examples with curl or httpie, showing how Linux/macOS users can perform the same operations.
- Clarify which tools are available on which platforms, and link to installation/setup guides for Linux/macOS users.
- Reorder examples so REST and cross-platform methods are presented before or alongside PowerShell, not after.
Service Fabric
Change ReliableDictionaryActorStateProvider settings
...e-actors-reliabledictionarystateprovider-configuration.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing Visual Studio (Windows-only for Service Fabric), using Windows-style paths in examples, and mentioning PowerShell commands without Linux equivalents. The configuration workflow is described in terms of files and tools typically found on Windows, with little guidance for Linux users. Linux-specific instructions are minimal and relegated to a single note about certificate formatting.
Recommendations
- Provide explicit instructions for configuring settings.xml and cluster manifests on Linux, including typical file locations and editing workflows.
- Include Linux command-line equivalents (e.g., Azure CLI, sfctl, or bash commands) for PowerShell commands like Get-ServiceFabricClusterManifest.
- Show sample paths using Linux conventions (e.g., /var/log/servicefabric/SharedLog.Log) alongside Windows paths.
- Clarify how Linux users can generate and edit configuration files if not using Visual Studio.
- Add a Linux/macOS-specific example for certificate configuration and other platform-dependent settings.
Service Fabric
Service Fabric Backup and Restore
...ric/service-fabric-reliable-services-backup-restore.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page for Service Fabric Backup and Restore demonstrates a moderate Windows bias. The only explicit tooling example for testing backup and restore uses the PowerShell cmdlet `Start-ServiceFabricPartitionDataLoss`, with no mention of Linux/macOS equivalents or cross-platform alternatives. Windows-specific tools and APIs (e.g., kernel32, .NET's Directory.Move) are referenced for file operations and workarounds, but Linux/macOS file system considerations are not discussed. No Linux or bash examples are provided for backup/restore testing or automation, and Windows-centric terminology (PowerShell, kernel32) appears before any mention of cross-platform approaches.
Recommendations
- Provide equivalent Linux/macOS instructions for testing backup and restore, such as using Service Fabric CLI (sfctl) or REST APIs.
- Include bash or shell script examples for backup/restore operations alongside PowerShell examples.
- Discuss file system limitations and workarounds for Linux/macOS (e.g., path length, permissions) in addition to Windows-specific issues.
- Reference cross-platform tools and APIs before or alongside Windows-specific ones.
- Clarify which APIs and methods are platform-agnostic and which are Windows-only.
Service Fabric
Service communication with the ASP.NET Core
...vice-fabric-reliable-services-communication-aspnetcore.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation demonstrates a moderate Windows bias, primarily through its extensive coverage of HTTP.sys (a Windows-only web server), references to Windows-specific tools (netsh), and frequent mentions of Windows APIs. While Kestrel (cross-platform) is recommended and well-documented, HTTP.sys sections lack Linux/macOS alternatives and do not clarify that those features are unavailable on non-Windows platforms. Windows-specific instructions and examples (such as endpoint registration and port sharing) are presented before or instead of Linux equivalents, and troubleshooting/configuration scenarios often assume Windows capabilities.
Recommendations
- Clearly mark Windows-only sections and features, and provide equivalent Linux/macOS guidance or alternatives where possible.
- Add explicit Linux/macOS examples for service hosting, endpoint configuration, and troubleshooting, especially for Kestrel.
- Where Windows tools (like netsh) are referenced, suggest cross-platform alternatives or clarify their absence on Linux/macOS.
- Reorder examples so that cross-platform (Kestrel) instructions appear before Windows-only (HTTP.sys) instructions.
- Add a summary table or section comparing feature parity and limitations between Windows and Linux/macOS Service Fabric deployments.
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
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a notable Windows bias by exclusively referencing PowerShell-based administrative APIs (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica) and showing command output screenshots from Windows environments. There is no mention of Linux/macOS equivalents, CLI alternatives, or cross-platform usage patterns. All example commands and API references are Windows-centric, and the documentation does not clarify how Linux users should perform these operations.
Recommendations
- Add equivalent examples using Service Fabric CLI (sfctl) for Linux/macOS users.
- Explicitly document how to perform replica soft delete and restore operations on Linux clusters, including any differences in tooling or workflow.
- Include screenshots or output examples from Linux environments where relevant.
- Clarify whether the PowerShell APIs are available cross-platform, and if not, provide alternative instructions.
- Reorder examples to present cross-platform or CLI methods before or alongside PowerShell commands.
Service Fabric
Secure service remoting communications with C#
...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-reliable-services-secure-communication.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a notable Windows bias. All code examples and configuration references are tailored for Windows environments, such as using Windows certificate stores (StoreLocation.LocalMachine, StoreName="My") and thumbprint-based certificate lookup, with only a brief note about Linux certificate location and format. There are no Linux-specific code samples or configuration patterns, and Windows terminology and tools are used exclusively throughout the main content. The page also presents Windows/C# content before mentioning Java/Linux alternatives.
Recommendations
- Provide parallel Linux-specific code examples, especially for certificate handling (e.g., loading PEM files from /var/lib/sfcerts).
- Include configuration samples that demonstrate Linux-compatible certificate settings.
- Clarify any platform-specific differences in APIs, certificate management, and deployment steps.
- Balance the order of presentation so Linux guidance is not secondary or relegated to notes.
- Reference cross-platform tools and patterns where possible, or clearly indicate platform limitations.
Service Fabric
Add and remove node types of a Service Fabric managed cluster
...abric/tutorial-managed-cluster-add-remove-node-type.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation is heavily biased towards Windows, with all examples using Azure PowerShell and no mention or examples of equivalent Linux/macOS workflows (e.g., Azure CLI or Bash). Prerequisites and instructions assume PowerShell usage, which is native to Windows, and do not provide guidance for users on Linux or macOS platforms.
Recommendations
- Add equivalent Azure CLI examples for all tasks (adding/removing node types), as CLI is cross-platform and works natively on Linux/macOS.
- Update prerequisites to mention both Azure PowerShell and Azure CLI, with installation links for each platform.
- Explicitly state that the tutorial works on Linux/macOS and provide any platform-specific notes if necessary.
- Consider showing CLI/Bash examples before or alongside PowerShell examples to avoid Windows-first bias.
Service Fabric
Azure Service Fabric reverse proxy diagnostics
...ice-fabric/service-fabric-reverse-proxy-diagnostics.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates a Windows bias primarily through references to Windows-specific tools and terminology (e.g., 'Windows Azure Diagnostics', 'ERROR_WINHTTP_TIMEOUT', 'winHttpError'), and by mentioning Windows-centric workflows (Visual Studio) in the 'Next steps' section. There are no explicit Linux/macOS troubleshooting examples, nor are cross-platform log collection methods or tools discussed. Windows error codes and APIs are referenced in diagnostic payloads without Linux equivalents or translation.
Recommendations
- Add equivalent Linux/macOS troubleshooting examples, including common error codes and diagnostic patterns for those platforms.
- Mention and document cross-platform log collection methods (e.g., using Linux diagnostics agents, Azure Monitor, or open-source tools).
- Clarify whether the error codes (e.g., ERROR_WINHTTP_TIMEOUT) are relevant only to Windows nodes, and provide Linux equivalents if available.
- Include instructions for viewing and interpreting logs on Linux/macOS clusters, such as using command-line tools or alternative IDEs.
- Rephrase 'Windows Azure Diagnostics' to 'Azure Diagnostics' and specify Linux support where applicable.
- Provide parity in 'Next steps' for Linux/macOS users, such as links to Linux-compatible monitoring tools or documentation.
Service Fabric
Azure Service Fabric set up reverse proxy
...es/service-fabric/service-fabric-reverseproxy-setup.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. Standalone cluster instructions and references are consistently tied to Windows Server, with links and examples focused on Windows-specific configuration files and upgrade guides. There are no explicit Linux/macOS examples or guidance for standalone clusters, and the documentation refers to Windows Server guides for key configuration steps. Azure-hosted cluster instructions are platform-neutral, but standalone cluster support is Windows-centric.
Recommendations
- Provide explicit instructions and examples for configuring reverse proxy on standalone clusters running Linux (if supported).
- Reference Linux/macOS equivalents for configuration and upgrade steps, including links to relevant documentation.
- Clarify platform support for standalone clusters and indicate if Linux is not supported, or provide parity where possible.
- Ensure that references to upgrade/configuration guides include both Windows and Linux versions, or state platform limitations.
Service Fabric
Azure Service Fabric CLI- sfctl chaos
.../articles/service-fabric/service-fabric-sfctl-chaos.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation for 'sfctl chaos' demonstrates a Windows bias primarily through its use of Windows-specific terminology and references, such as 'Windows file time' and linking to .NET's DateTime.ToFileTimeUtc method. There are no explicit Linux/macOS examples or references, and the documentation does not clarify how Linux/macOS users should specify time arguments or handle platform differences. The CLI itself is cross-platform, but the documentation assumes a Windows-centric context.
Recommendations
- Provide equivalent Linux/macOS instructions or examples, especially for time formatting and conversion.
- Clarify whether 'Windows file time' is required on all platforms, and offer guidance/tools for Linux/macOS users to generate compatible values.
- Include references to cross-platform date/time conversion utilities (e.g., Python, shell commands) for Linux/macOS users.
- Add explicit notes or examples showing usage on Linux/macOS, including any differences in behavior or prerequisites.
Service Fabric
Azure Service Fabric CLI- sfctl node
...n/articles/service-fabric/service-fabric-sfctl-node.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
Summary
The documentation is largely platform-neutral, focusing on the sfctl CLI, which is cross-platform. However, there is a notable Windows bias in the 'remove-state' command section, where guidance and links are provided only for standalone clusters running on Windows Server, with no mention of Linux equivalents or instructions for Linux clusters.
Recommendations
- Add equivalent guidance and links for managing node state in standalone Service Fabric clusters running on Linux.
- Clarify whether the described procedures and links are applicable to Linux clusters, and if not, provide Linux-specific instructions.
- Ensure that any references to platform-specific documentation (such as adding/removing nodes) include both Windows and Linux versions, or explicitly state platform limitations.
Service Fabric
Learn Azure Service Fabric terminology
...es/service-fabric/service-fabric-technical-overview.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page exhibits a moderate Windows bias. Key infrastructure concepts (such as the node definition) reference Windows-specific tools and patterns (e.g., auto-start Windows service, FabricHost.exe) without mentioning Linux equivalents or patterns. Executable file types are described as EXE/DLL, which are Windows-centric, and Windows containers are mentioned before Docker containers on Linux. There is a lack of explicit Linux examples or terminology in critical sections, and Windows tools/patterns are presented first or exclusively.
Recommendations
- Explicitly describe Linux equivalents for node management (e.g., systemd services, Linux process patterns) alongside Windows services.
- When discussing executables, mention Linux binary formats (e.g., ELF) and clarify how Service Fabric handles them.
- Present Docker containers on Linux before or alongside Windows containers to avoid Windows-first ordering.
- Add examples or explanations for Linux-specific deployment and operational steps where Windows tools are referenced.
- Ensure terminology and examples are platform-neutral or provide parity between Windows and Linux/macOS.
Service Fabric
Integrate API Management with Service Fabric in Azure
...abric/service-fabric-tutorial-deploy-api-management.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
powershell_heavy
Summary
The documentation is strongly oriented toward Windows environments. It assumes the use of a Windows Service Fabric cluster, references Windows-specific development tools (Visual Studio), and provides step-by-step instructions for creating and deploying .NET services using Visual Studio. There are no equivalent instructions or examples for Linux clusters, Linux development environments, or cross-platform tooling. PowerShell is used for scripting and certificate handling, with no Bash or Linux alternatives shown. Linux users are left to infer or adapt steps, which may create significant friction.
Recommendations
- Add explicit instructions for setting up a Linux Service Fabric cluster, including links to relevant tutorials.
- Provide examples for developing and deploying Service Fabric services using cross-platform tools (e.g., VS Code, CLI, Java, or .NET Core on Linux).
- Include Linux/macOS equivalents for certificate handling and base64 encoding (e.g., using openssl and base64 commands).
- Show Bash scripts alongside PowerShell for template deployment and resource management.
- Clarify which steps are Windows-specific and offer alternatives for Linux/macOS users.
- Reference Linux development environment setup guides and Service Fabric SDK installation for Linux.
Service Fabric
How to view Azure Service Fabric entities' aggregated health
...bric/service-fabric-view-entities-aggregated-health.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation consistently provides detailed PowerShell examples for querying Service Fabric health, with no equivalent examples for Linux/macOS command-line environments (e.g., Bash, CLI). PowerShell is a Windows-centric tool, and its usage is shown before REST API alternatives. There is no mention of Linux-native tools, nor are there instructions for running PowerShell cross-platform. This creates friction for Linux/macOS users, who must rely on REST API or .NET SDK without command-line parity.
Recommendations
- Add Azure CLI examples for all PowerShell cmdlets, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Explicitly mention that PowerShell Core is available on Linux/macOS, and provide installation instructions or usage notes if PowerShell is required.
- Include Bash/cURL examples for REST API calls to demonstrate how Linux/macOS users can perform equivalent queries.
- Reorder sections so that cross-platform methods (REST API, Azure CLI) are presented before or alongside PowerShell.
- Clarify any platform-specific limitations or requirements for Service Fabric tooling.
Service Fabric
Configure secure Azure Service Fabric cluster connections
...rvice-fabric-visualstudio-configure-secure-connections.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation is heavily oriented toward Windows environments, focusing on Visual Studio and PowerShell for configuring secure connections to Azure Service Fabric clusters. Certificate installation instructions and command-line tooling are exclusively Windows-centric, with no mention of Linux/macOS equivalents or cross-platform alternatives. This creates friction for non-Windows users attempting to follow the guide.
Recommendations
- Add instructions for installing .pfx certificates on Linux/macOS, such as using OpenSSL or system-specific certificate stores.
- Include examples of connecting to Service Fabric clusters using cross-platform tools (e.g., Azure CLI, Service Fabric CLI) where possible.
- Provide guidance for editing publish profiles and resolving certificate parameters on Linux/macOS systems.
- Clarify which steps are Windows-specific and offer Linux/macOS alternatives or references.
- Mention cross-platform IDEs (such as VS Code) if supported, or explicitly state Windows-only requirements.
Service Fabric
Troubleshoot with system health reports
...understand-and-troubleshoot-with-system-health-reports.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a notable Windows bias. All command-line examples use PowerShell syntax and Windows-style paths (e.g., 'PS C:\>'), with no mention of Linux or macOS equivalents. There is no reference to Service Fabric CLI (sfctl), Bash, or cross-platform tools. The only instructions for clearing health reports and querying cluster/application/service/partition/replica health are given as PowerShell cmdlets, and links to further instructions also point to Windows/PowerShell-specific documentation. This creates friction for Linux/macOS users and may prevent them from easily following the troubleshooting steps.
Recommendations
- Add equivalent examples using sfctl (Service Fabric CLI), which is cross-platform and works on Linux/macOS.
- Explicitly mention that all PowerShell commands can be run on Windows, and provide Bash/sfctl alternatives for Linux/macOS.
- Where possible, use generic API references (e.g., REST API, .NET SDK) and show how to invoke them from different platforms.
- Reorder examples so that cross-platform tools (sfctl, REST API) are shown first or alongside PowerShell.
- Update links to include Linux/macOS documentation and troubleshooting guides.
Virtual Machine Scale Sets
Azure Disk Encryption and Azure Virtual Machine Scale Sets extension sequencing
...ine-scale-sets/disk-encryption-extension-sequencing.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page claims to focus on enabling Azure Disk Encryption for Linux IaaS VMs, but the main sample templates and extension sequencing examples exclusively use Windows-centric tools and scripts (PowerShell, Windows disk formatting, Windows diagnostics extension). Linux-specific examples are only referenced as a link, not shown inline, and are not given equal prominence or detail.
Recommendations
- Provide inline sample templates and extension sequencing examples using Linux tools (e.g., shell scripts for disk formatting, Linux diagnostics extensions).
- Show Linux examples before or alongside Windows examples to match the stated Linux focus.
- Replace or supplement PowerShell script references with bash or shell script references for Linux scenarios.
- Explicitly mention Linux equivalents for extensions and commands where Windows-specific ones are shown.
- Ensure that Linux users can follow the documentation without needing to consult external links for critical steps.
Service Fabric
Add a node type to an Azure Service Fabric cluster
...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/virtual-machine-scale-set-scale-node-type-scale-out.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing Windows file paths (e.g., 'D:\\SvcFab') in configuration examples, omitting Linux-specific paths or considerations. The 'Next steps' section links to a standalone cluster scaling guide that is explicitly for Windows Server, with no mention of Linux equivalents. There are no Linux/macOS-specific instructions, examples, or notes, and Windows conventions (such as drive letters) are used by default.
Recommendations
- Include Linux-specific configuration examples, such as using '/var/svcfab' for dataPath instead of 'D:\\SvcFab'.
- Add notes or sections clarifying differences when deploying on Linux-based clusters, including any required changes to ARM templates or Service Fabric extension properties.
- Provide links to Linux/macOS standalone cluster scaling documentation, or clarify if such functionality is not supported.
- Ensure that all examples are either cross-platform or presented in both Windows and Linux formats.
Virtual Machine Scale Sets
Creating and configuring a key vault for Azure Disk Encryption
...irtual-machine-scale-sets/disk-encryption-key-vault.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation mentions Azure PowerShell and the Az module alongside Azure CLI and the portal, but does not provide explicit Linux/macOS-specific guidance or examples. The references to PowerShell and Az module, which are traditionally Windows-centric, are given equal prominence to the CLI, and no mention is made of Bash, shell scripting, or Linux-specific installation or usage patterns. There are no explicit Linux/macOS examples or troubleshooting notes, and the 'Next steps' section lists PowerShell before CLI.
Recommendations
- Add explicit instructions or examples for Linux/macOS users, such as Bash or shell scripting with Azure CLI.
- Clarify that Azure CLI is cross-platform and provide installation steps for Linux/macOS.
- Ensure that CLI examples are shown before or alongside PowerShell examples.
- Include troubleshooting notes for Linux/macOS environments where relevant.
- Balance references to PowerShell with equivalent Linux/macOS tools or workflows.
Virtual Machine Scale Sets
Customer intent: As a cloud administrator, I want to deploy and customize Virtual Machine Scale Sets, so that I can efficiently manage workloads and optimize resource utilization in my existing infrastructure.
...virtual-machine-scale-sets/includes/mvss-next-steps.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page references deploying templates via Azure Resource Manager documentation specifically through a PowerShell link, suggesting a Windows-centric approach. There are no explicit Linux or cross-platform CLI examples or links provided, and PowerShell is mentioned before any Linux alternatives. While there is a mention of deploying a Linux scale set, the deployment instructions themselves are biased towards Windows/PowerShell.
Recommendations
- Include links to Azure CLI and Bash deployment documentation alongside PowerShell.
- Provide explicit examples for Linux/macOS users, such as using Azure CLI or Bash scripts.
- Ensure that cross-platform tools are referenced equally and not only after Windows tools.
- Add a section or note clarifying that all steps can be performed on Linux/macOS using supported Azure tools.
Virtual Machine Scale Sets
Create a scale set from a generalized image
...chine-scale-sets/instance-generalized-image-version.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation provides extensive PowerShell examples and advanced workflows using Windows-centric tools, while Linux/macOS equivalents (such as Bash scripting or cloud-init integration) are absent. PowerShell is given a dedicated, detailed section with both simplified and extended parameter sets, whereas CLI examples are briefer and lack comparable depth. Windows tools and patterns (e.g., Get-Credential, New-AzResourceGroup, New-AzLoadBalancer) are used exclusively in the PowerShell section, with no mention of Linux-native automation or scripting approaches. The ordering also places PowerShell after CLI but with much more detail, and there is no explicit parity for Linux users in advanced scenarios.
Recommendations
- Add equivalent Bash or shell scripting examples for advanced workflows, matching the PowerShell extended parameter set.
- Include guidance on using Linux-native tools (e.g., cloud-init, SSH key management, automation via Bash scripts) for scale set creation.
- Explicitly mention cross-platform compatibility and provide notes for Linux/macOS users where PowerShell-specific commands are used.
- Ensure advanced configuration steps (networking, load balancing, etc.) are shown using Azure CLI or ARM templates, not just PowerShell.
- Balance example depth between PowerShell and CLI sections, and consider showing CLI/Bash examples first or side-by-side.
Virtual Machine Scale Sets
Create a Virtual Machine Scale Set with instance mix
...cles/virtual-machine-scale-sets/instance-mix-create.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation provides examples for Azure Portal, Azure CLI, Azure PowerShell, and REST API. However, the PowerShell section is notably more detailed, with multiple example commands and advanced usage (configuration object), while the CLI section is more basic. PowerShell is a Windows-centric tool, and its prominence and depth suggest a bias toward Windows users. Additionally, the prerequisites mention PowerShell before CLI, and the CLI examples use Ubuntu images but do not reference Linux-specific shell usage or scripting. There is no explicit Linux shell (bash) or macOS Terminal example, and PowerShell is presented as a primary automation tool, which may disadvantage Linux/macOS users.
Recommendations
- Expand Azure CLI examples to include advanced scenarios, matching the depth of PowerShell examples.
- Add explicit bash shell examples for Linux/macOS users, including scripting and automation patterns.
- Clarify that Azure CLI is cross-platform and provide guidance for Linux/macOS environments (e.g., SSH key management, environment variables).
- Reorder prerequisites to mention CLI before PowerShell, or present both equally.
- Consider adding notes or links for installing and using Azure CLI and PowerShell on Linux/macOS.
Virtual Machine Scale Sets
Create a scale set from a specialized image version using the Azure CLI
...chine-scale-sets/instance-specialized-image-version.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation provides extensive PowerShell examples for creating a scale set from a specialized image, with detailed steps and resource configuration. The PowerShell section uses Windows-centric tools and patterns (e.g., New-AzLoadBalancer, RDP NAT pools), while the CLI examples are much simpler and do not cover equivalent networking or load balancer setup. The PowerShell example is significantly more comprehensive and appears before any Linux-specific guidance. There are no bash or Linux shell examples for advanced scenarios, and Windows tools/patterns are referenced exclusively in the PowerShell section.
Recommendations
- Add equivalent bash/Linux shell examples for advanced scenarios, including networking and load balancer setup using Azure CLI.
- Ensure that Linux/macOS users are guided through the same level of detail for resource creation as Windows/PowerShell users.
- Explicitly mention cross-platform compatibility for CLI commands and clarify any OS-specific prerequisites.
- Consider reordering sections so that CLI (cross-platform) examples are presented before PowerShell (Windows-only) examples.
Virtual Machine Scale Sets
Spot Placement Score
...les/virtual-machine-scale-sets/spot-placement-score.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides platform-specific instructions for Azure PowerShell and Azure CLI, but the PowerShell section is more detailed and prominent. The CLI section does not clarify Linux/macOS usage or show shell-specific examples, and PowerShell is presented as a distinct tab, which may imply Windows-first bias. There are no explicit Linux/macOS shell examples (e.g., Bash), nor any mention of Linux-specific considerations. The Azure portal and REST API sections are platform-neutral, but the lack of Linux/macOS command-line examples and the prominence of PowerShell suggest a moderate Windows bias.
Recommendations
- Add explicit Bash/Linux shell examples for the Azure CLI, showing usage in a Linux/macOS terminal.
- Clarify that Azure CLI works cross-platform and provide example outputs for Linux/macOS.
- Balance the PowerShell and CLI sections in detail and order, ensuring CLI instructions are as comprehensive as PowerShell.
- Consider adding a note or section on Linux/macOS compatibility and any platform-specific caveats.
- If possible, provide troubleshooting steps or error handling examples relevant to Linux/macOS environments.
Virtual Machine Scale Sets
Configure role permissions for standby pools
...hine-scale-sets/standby-pools-configure-permissions.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation exclusively describes role assignment and troubleshooting using the Azure Portal UI, with no mention of command-line alternatives. Where programmatic access is referenced, only PowerShell and CLI are mentioned, but no concrete examples are given for either. There are no Linux/macOS-specific instructions or examples, and the troubleshooting steps rely on Azure Portal and Log Analytics, which are cross-platform but presented in a way that assumes GUI usage typical of Windows users.
Recommendations
- Provide equivalent Azure CLI commands for all role assignment steps, with explicit Linux/macOS usage examples.
- Include instructions for using Azure PowerShell and Azure CLI for troubleshooting, with sample commands.
- Clarify that Azure CLI is cross-platform and provide links to installation and usage guides for Linux/macOS.
- Add a section or callout for Linux/macOS users, highlighting any differences or considerations.
- Ensure REST API examples are accompanied by CLI and PowerShell equivalents, and show how to use curl or similar tools on Linux/macOS.
Virtual Machine Scale Sets
Use Azure Log Analytics to monitor standby pool events
...achine-scale-sets/standby-pools-monitor-pool-events.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 configuring diagnostic settings, but PowerShell (a Windows-centric tool) is given equal prominence to CLI. There is no mention of Bash or Linux-specific instructions, and the guidance for creating resources and configuring settings is oriented around the Azure portal and PowerShell, which are more familiar to Windows users. The CLI example is cross-platform, but the absence of explicit Linux/macOS guidance or troubleshooting tips creates a subtle Windows bias.
Recommendations
- Add explicit Bash/Linux shell examples where CLI is shown, including notes about running az CLI on Linux/macOS.
- Clarify that Azure CLI commands work on Linux/macOS and provide troubleshooting tips for common Linux issues (e.g., authentication, environment variables).
- Add a note that PowerShell Core is available cross-platform, or provide Bash alternatives for PowerShell commands.
- Consider listing CLI (cross-platform) examples before PowerShell to emphasize Linux parity.
- Include links to Linux/macOS setup guides for Azure CLI and PowerShell Core.
Virtual Machine Scale Sets
Get Prediction Results for Standby pools for Virtual Machine Scale Sets (Preview)
...machine-scale-sets/standby-pools-prediction-results.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides examples for Azure CLI, PowerShell, and REST API. However, the PowerShell example is given equal prominence as the CLI, and PowerShell is a Windows-centric tool. There are no Linux/macOS-specific shell examples (such as Bash or curl), nor is there mention of Linux tools or workflows. The ordering of examples places CLI first, which is cross-platform, but PowerShell is still highlighted, and no explicit Linux guidance is given.
Recommendations
- Add Linux/macOS-specific examples, such as using curl or httpie for the REST API.
- Clarify that Azure CLI commands work on Linux/macOS and provide any necessary installation or usage notes for those platforms.
- If PowerShell is mentioned, also mention Bash or other common Linux shells for parity.
- Explicitly state platform compatibility for each tool in the documentation.
- Consider adding a Bash script example for parsing the JSON output from Azure CLI.
Virtual Machine Scale Sets
Create a scale set that uses Azure Spot Virtual Machines
...b/main/articles/virtual-machine-scale-sets/use-spot.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
missing_linux_example
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Azure Spot Virtual Machines in scale sets, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and there are references to Windows-specific resources and examples. The ARM template section mentions both Linux and Windows but does not provide explicit Linux-centric examples. The eviction simulation section links only to a Windows/PowerShell guide for further information. Overall, there is a moderate Windows bias, especially in example tooling and follow-up resources.
Recommendations
- Provide explicit Linux/macOS command-line examples, such as Bash scripts or Linux-specific CLI usage patterns.
- Ensure that links to further reading or examples include Linux-focused documentation (e.g., simulate eviction with Azure CLI or REST from Linux).
- When referencing PowerShell, clarify its cross-platform availability or provide alternatives for Linux users.
- In ARM template sections, include concrete Linux VM examples and highlight Linux-specific considerations.
- Balance the order of examples so that CLI (cross-platform) is shown before PowerShell, and avoid implying PowerShell is the default for all users.
Virtual Machine Scale Sets
Automatic instance repairs with Azure Virtual Machine Scale Sets
...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-automatic-instance-repairs.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides examples for Azure PowerShell, Azure CLI, REST API, and Azure Portal. However, PowerShell examples are consistently presented before CLI examples, and PowerShell is referenced heavily throughout, including in important notes and breaking change announcements. There is no explicit mention of Linux/macOS-specific considerations, nor are there any bash or shell script examples. The CLI examples use generic syntax, but PowerShell is given prominence, which may create friction for Linux/macOS users who do not use PowerShell.
Recommendations
- Present Azure CLI examples before PowerShell examples, or alternate the order to avoid Windows-first bias.
- Add explicit bash/shell script examples for common tasks, especially for enabling and updating policies.
- Include notes clarifying that Azure CLI works natively on Linux/macOS and provide links to CLI installation guides for those platforms.
- Reduce the emphasis on PowerShell in notes and breaking change announcements, or provide equivalent CLI-focused notes.
- Where PowerShell is referenced, clarify that it is available cross-platform, or provide alternative commands for bash users.
Virtual Machine Scale Sets
Automatic OS image upgrades with Azure Virtual Machine Scale Sets
...e-sets/virtual-machine-scale-sets-automatic-upgrade.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Windows and Linux information, but there are several signs of Windows bias. Windows-specific configuration properties (e.g., enableAutomaticUpdates) are discussed in detail, and Windows Server SKUs are listed extensively. PowerShell examples are given before Azure CLI examples, and ARM/Bicep template snippets default to Windows images. Windows terminology and tools (e.g., drive letters, Windows Update) are mentioned more frequently and in more detail than Linux equivalents. However, Linux support is clearly stated and Azure CLI examples are present, so Linux users can complete the tasks with some friction.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples so Linux users see CLI first in some sections.
- Add explicit Linux-focused configuration examples, especially for ARM/Bicep templates (e.g., show Canonical/Ubuntu image defaults).
- Provide notes or examples for Linux-specific behaviors (e.g., disk mounting, extension scripts) where Windows drive letters or Windows Update are discussed.
- Balance the discussion of OS-specific properties (e.g., mention Linux patching modes or update mechanisms where Windows Update is referenced).
- Ensure that all examples (ARM, Bicep, CLI, PowerShell) show both Windows and Linux image configurations.
Virtual Machine Scale Sets
Deploy an application to an Azure Virtual Machine Scale Set
...ne-scale-sets/virtual-machine-scale-sets-deploy-app.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation provides both Linux and Windows guidance, but several sections show Windows bias. Windows/PowerShell examples and tools (e.g., PowerShell DSC) are described in greater detail and appear before Linux equivalents. The Windows DSC example is extensive, while the Linux cloud-init section is shorter and lacks a direct example. References to PowerShell and Windows tools are frequent, and some links and next steps prioritize Windows management. Linux-specific examples and parity in detail are missing in some areas.
Recommendations
- Provide equally detailed Linux examples for application deployment, matching the depth of the PowerShell DSC section (e.g., a full cloud-init YAML example).
- Ensure Linux instructions and examples are presented alongside or before Windows ones, especially in summary tables and lists.
- Include links to Linux management guides in 'Next steps', not just PowerShell/Windows ones.
- Expand on Linux-native configuration management tools (e.g., Ansible, Chef) as alternatives to PowerShell DSC.
- Where both Azure CLI and PowerShell are referenced, ensure CLI (cross-platform) examples are shown first or equally.
- Add explicit Linux troubleshooting and best practices sections to match Windows coverage.
Virtual Machine Scale Sets
Overview of autoscale with Azure Virtual Machine Scale Sets
...-sets/virtual-machine-scale-sets-autoscale-overview.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page shows a moderate Windows bias. Windows tools (PowerShell) are frequently mentioned and often listed before cross-platform alternatives (Azure CLI). Examples for manual scaling are given for Azure Portal, Azure CLI, and Azure PowerShell, but there is no explicit Linux shell example (e.g., Bash). In the 'Next steps' and other sections, PowerShell is often listed first or exclusively, and links to PowerShell-centric management guides are provided. While Azure CLI is cross-platform, the documentation does not provide parity for Linux/macOS users in terms of command-line examples or tool recommendations.
Recommendations
- Provide explicit Bash/Linux shell examples alongside PowerShell, especially for common tasks.
- Ensure Azure CLI examples are shown before or alongside PowerShell examples to emphasize cross-platform support.
- Add links to Linux/macOS management guides for Virtual Machine Scale Sets.
- Clarify that Azure CLI works on Linux/macOS and highlight any OS-specific considerations.
- Balance references to Windows tools (PowerShell) with equivalent Linux/macOS tools or workflows.
Virtual Machine Scale Sets
Use extension sequencing with Azure Virtual Machine Scale Sets
...ets/virtual-machine-scale-sets-extension-sequencing.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a notable Windows bias. All concrete extension sequencing examples using Azure PowerShell and Azure CLI are explicitly for Windows-based scale sets, referencing Windows-specific extensions (ApplicationHealthWindows, CustomScriptExtension for Windows). There are no Linux-based extension examples, nor are Linux equivalents (e.g., ApplicationHealthLinux, CustomScriptExtension for Linux) mentioned. Windows tools and patterns (PowerShell, Windows extension names) are presented exclusively, and always before any Linux alternatives (which are absent).
Recommendations
- Add parallel examples for Linux-based scale sets, using Linux-specific extensions (e.g., ApplicationHealthLinux, CustomScriptExtension for Linux).
- Explicitly mention that extension sequencing applies to both Windows and Linux scale sets.
- Provide CLI and PowerShell commands for Linux scenarios, including relevant extension names and settings.
- Reference documentation for Linux extensions alongside Windows ones.
- Avoid language that implies Windows is the default or only supported platform.
Virtual Machine Scale Sets
Use Application Health extension with Azure Virtual Machine Scale Sets
...le-sets/virtual-machine-scale-sets-health-extension.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation demonstrates a moderate Windows bias. REST API and PowerShell examples are provided first and are exclusively for Windows-based scale sets, while Linux examples appear only in the Azure CLI sections and are placed after Windows examples. PowerShell is emphasized as a primary tool, with no Linux shell or scripting equivalents. Troubleshooting and log location sections do mention Linux, but operational examples and walkthroughs are Windows-centric, and Linux users must infer or adapt steps for their platforms.
Recommendations
- Provide REST API examples for both Windows and Linux scale sets, not just Windows.
- Include PowerShell alternatives for Linux, such as Bash or Python scripts, or clarify PowerShell Core cross-platform usage.
- Present Linux and Windows examples side-by-side or alternate which is shown first.
- Expand troubleshooting and operational examples to include Linux-specific commands and workflows.
- Clarify tool availability and usage for Linux users, especially where PowerShell is referenced.
Virtual Machine Scale Sets
Maintenance notifications for Virtual Machine Scale Sets in Azure
...tps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-maintenance-notifications.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples are presented before Azure CLI, and only PowerShell (a Windows-centric tool) is given as a script example, with no equivalent Bash or Linux shell example. References to scheduled events link to Windows-specific documentation. There is no explicit mention of Linux/macOS command-line environments or examples, and Linux users may need to infer usage from CLI commands.
Recommendations
- Provide Bash/Linux shell examples alongside PowerShell, especially for scripting maintenance tasks.
- Include links to Linux/macOS scheduled events documentation, not just Windows.
- Clarify that Azure CLI is cross-platform and can be used on Linux/macOS, and consider presenting CLI examples before or alongside PowerShell.
- Add notes or sections for Linux/macOS users, highlighting any differences or considerations.
- Ensure all referenced documentation (e.g., scheduled events) has Linux/macOS equivalents linked.
Virtual Machine Scale Sets
Custom metrics for rolling upgrades on Virtual Machine Scale Sets
...tual-machine-scale-sets-rolling-upgrade-custom-metrics.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell examples are provided for nearly every major operation, and Windows-specific extension types (ApplicationHealthWindows) are shown before or alongside Linux equivalents. In several places, Windows tools and patterns (PowerShell scripts, Windows extension types) are presented before Linux alternatives, and the PowerShell example for the health endpoint response is more elaborate than the Bash/Python example. However, Linux/CLI examples are present throughout, and REST API examples are provided, mitigating the impact.
Recommendations
- Ensure Linux and Windows extension types are presented equally, with clear guidance for both (e.g., ApplicationHealthLinux and ApplicationHealthWindows).
- Present CLI/Bash examples before PowerShell examples to avoid implicit prioritization of Windows workflows.
- Expand Linux/macOS scripting examples (e.g., provide a shell-only or Python-only example for endpoint response, not requiring iptables or Python).
- Clarify in each example which OS/platform it applies to, and provide parity for both where possible.
- Where PowerShell is used, offer an equivalent Bash or shell script for Linux/macOS users.
- Explicitly mention that all features are available on both Linux and Windows VMSS, and link to OS-specific extension documentation.
Virtual Machine Scale Sets
Terminate notification for Azure Virtual Machine Scale Set instances
...s/virtual-machine-scale-sets-terminate-notification.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation demonstrates a moderate Windows bias. Windows and PowerShell are frequently referenced, with Windows links and examples often appearing before Linux equivalents. PowerShell examples are provided in detail, but there is no equivalent Bash or Linux shell scripting example. REST API and Azure CLI sections are platform-neutral, but the scripting guidance is Windows-centric. References to Scheduled Events link to Windows documentation first, and Linux links are secondary. There is a lack of Linux-specific command-line or scripting examples for enabling and responding to termination notifications.
Recommendations
- Add Bash or shell script examples for enabling termination notifications, mirroring the PowerShell samples.
- Ensure Linux documentation links are presented alongside or before Windows links, especially in sections discussing Scheduled Events.
- Include explicit instructions or examples for Linux users to query and respond to scheduled events using curl, wget, or Python.
- Balance the order of examples so that Linux and Windows are equally represented, or alternate which platform is shown first.
- Reference Linux-specific troubleshooting steps if any platform differences exist.
Virtual Machines
Automatic Extension Upgrade for VMs and scale sets in Azure
...ticles/virtual-machines/automatic-extension-upgrade.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation demonstrates a moderate Windows bias. In code examples (REST API, PowerShell, ARM template), the extension type is consistently set to 'DependencyAgentWindows' and the publisher to 'Microsoft.Azure.Monitoring.DependencyAgent', even when the CLI examples use 'DependencyAgentLinux'. PowerShell examples are provided only for Windows extensions, and the use of PowerShell itself is inherently Windows-centric. ARM template and REST API samples also default to Windows extension types. There is no explicit Linux-focused PowerShell or ARM template example, and the documentation does not alternate or balance Windows and Linux examples. The supported extensions table does list both Windows and Linux extensions, but example usage is Windows-first and lacks Linux parity in several critical sections.
Recommendations
- Provide parallel examples for both Windows and Linux extension types in all code samples (REST API, PowerShell, ARM template, etc.), not just CLI.
- Alternate the order of Windows and Linux examples, or present both together, to avoid Windows-first bias.
- Include notes or guidance for Linux users where PowerShell is referenced, such as using Azure CLI or REST API.
- Explicitly show how to enable automatic extension upgrade for a Linux VM/VMSS in PowerShell and ARM template sections.
- Add a section clarifying cross-platform support and tooling for both Windows and Linux users.
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page for Azure VM Watch demonstrates moderate Windows bias. Several health signals and checks are Windows-specific (e.g., System Errors from Windows event log, Hardware Health Monitor via Windows event log, fallback to w32tm for clock sync on Windows). Windows tools and patterns (event log, w32tm) are mentioned explicitly, while Linux equivalents are either absent or less detailed. In some cases, Windows checks are described first or exclusively, and Linux-specific metrics are less prominent or only briefly mentioned.
Recommendations
- Add equivalent Linux examples and tooling references for all Windows-specific checks (e.g., describe how system errors are collected on Linux, such as via syslog or journald).
- For hardware health, provide Linux methods (e.g., SMART monitoring, dmesg parsing) alongside Windows event log collection.
- For clock skew, specify the Linux fallback mechanism (e.g., ntpd, chrony status) when NTP server is inaccessible.
- Ensure all tables and descriptions mention both Linux and Windows approaches where applicable, and avoid listing Windows methods first unless they are more widely applicable.
- Where a metric or check is Windows-only, clearly state the Linux equivalent or note its absence.
Virtual Machines
Automatic Guest Patching for Azure Virtual Machines and Scale Sets
...ticles/virtual-machines/automatic-vm-guest-patching.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation provides comprehensive coverage for both Windows and Linux VMs, but there is a notable Windows bias: Windows examples and tools (PowerShell, CLI) are presented first and in greater detail, with multiple PowerShell and CLI examples for Windows but fewer for Linux. Several patch orchestration modes are Windows-only, and Windows-specific tools and registry settings are described in detail, while Linux equivalents are less emphasized. The 'Next steps' section links only to Windows VM management.
Recommendations
- Present Linux and Windows examples in parallel, or alternate which comes first in each section.
- Add equivalent PowerShell and CLI examples for Linux where missing, especially for patch mode changes and VM creation/update.
- Include more detail on disabling/enabling automatic updates for Linux distributions (beyond Ubuntu and RHEL).
- Provide 'Next steps' links for Linux VM management alongside Windows.
- Clarify Linux-specific requirements and troubleshooting steps, matching the depth given to Windows.
- Where Windows registry keys are mentioned, explain the Linux configuration file equivalents.
Virtual Machines
Customer intent: "As a cloud architect, I want to develop a robust backup and disaster recovery strategy for my Azure VMs and their managed disks, so that my organization can ensure data availability and minimize downtime during outages or data loss incidents."
...s/backup-and-disaster-recovery-for-azure-iaas-disks.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific tools and patterns (e.g., Volume Shadow Service, SQL Server Always On) are mentioned before their Linux equivalents, and Windows examples (such as SQL Server) are more detailed. Linux alternatives (like fsfreeze) are referenced briefly and with less explanation. There are no concrete Linux command examples or detailed Linux application backup scenarios, while Windows tools and workflows are described in greater depth.
Recommendations
- Provide equal detail for Linux backup coordination tools (e.g., expand on fsfreeze usage, mention LVM snapshots, etc.)
- Include Linux application examples (e.g., PostgreSQL, MySQL, MongoDB) with backup and disaster recovery strategies
- Add step-by-step Linux command examples for snapshot coordination and restore operations
- Mention Linux-native backup solutions and patterns alongside Windows ones, not after
- Balance references to Windows and Linux in tables and scenario descriptions
Virtual Machines
Overview backup options for VMs
...blob/main/articles/virtual-machines/backup-recovery.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation generally covers backup options for both Windows and Linux VMs, but in the 'Managed snapshots' section, the only example link provided is for Windows ('Create copy of VHD stored as a Managed Disk'), with no equivalent Linux example or mention. This prioritizes Windows and may leave Linux users unclear about their workflow.
Recommendations
- Add a Linux-specific example or documentation link for creating managed disk snapshots on Linux VMs.
- Ensure that examples and references are provided for both Windows and Linux platforms in all sections.
- Where platform-specific instructions exist, present them side-by-side or clearly indicate differences.
Virtual Machines
Associate a virtual machine to a capacity reservation group
.../virtual-machines/capacity-reservation-associate-vm.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation exhibits a moderate Windows bias. While it claims to apply to both Windows and Linux VMs, several examples and templates (especially the ARM template) are Windows-centric, with Windows images and parameters shown by default. PowerShell is given equal prominence to Azure CLI, but PowerShell is a Windows-first tool. The ARM template only demonstrates Windows VM creation, with no Linux image or configuration example. Password complexity requirements are described in Windows terms. In most sections, Windows tools and patterns (PowerShell, Windows images) are shown before or instead of Linux equivalents.
Recommendations
- Add explicit Linux VM ARM template examples, including imageReference for popular Linux distributions (e.g., Ubuntu, CentOS).
- In ARM template parameters, include both Windows and Linux OS options, with clear instructions for each.
- Clarify password requirements for Linux VMs (e.g., SSH keys) and provide guidance for Linux administrator account setup.
- In PowerShell sections, note that PowerShell is cross-platform but most users on Linux/macOS will prefer Azure CLI or REST API.
- Where examples use Windows-centric terminology (e.g., RDP port 3389), add Linux-relevant alternatives (e.g., SSH port 22).
- Ensure that Linux is represented equally in example code, screenshots, and step-by-step instructions.
Virtual Machines
Associate a virtual machine scale set with Uniform Orchestration to a capacity reservation group.
...pacity-reservation-associate-virtual-machine-scale-set.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation exhibits a moderate Windows bias. PowerShell examples are provided for every scenario, and ARM template parameters and variables are heavily focused on Windows (e.g., Windows OS versions, PowerShell DSC, Windows-specific images). There is no equivalent Linux-focused ARM template example, and Windows terminology/tools (PowerShell DSC, WebDeploy) are referenced without Linux alternatives. While Azure CLI examples use Ubuntu images, the ARM template and scripting guidance are Windows-centric, and PowerShell is given equal or greater prominence than CLI. Linux/macOS users may find it less intuitive to adapt the ARM template or automation examples for their environments.
Recommendations
- Add Linux-focused ARM template examples (e.g., using Ubuntu or other Linux images, removing PowerShell DSC and Windows-specific parameters).
- Include Bash shell scripting examples alongside PowerShell for automation tasks.
- Balance the documentation by referencing Linux tools and deployment patterns (e.g., cloud-init, Linux admin username conventions) where appropriate.
- Clarify that Azure CLI commands work cross-platform and highlight any OS-specific considerations.
- Provide links or notes for adapting Windows-centric steps (like DSC or WebDeploy) to Linux equivalents (e.g., cloud-init, custom script extensions).
Virtual Machines
Share a Capacity Reservation Group in Azure
...s/virtual-machines/capacity-reservation-group-share.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
powershell_heavy
windows_first
Summary
The documentation provides cross-platform guidance using REST API, Azure CLI, PowerShell, and ARM templates. However, there is a notable bias toward Windows tooling: PowerShell examples are present in every tabbed section, and references to PowerShell commands are frequent. The documentation refers to 'PowerShell' and 'PowerShell-interactive' in example blocks, which are Windows-centric, even though Azure PowerShell is available on Linux/macOS. Additionally, PowerShell examples are consistently shown alongside CLI, sometimes with more detail. There are no explicit Linux/macOS shell examples (e.g., bash scripts), and the CLI examples do not clarify platform differences. The documentation references 'Azure PowerShell' before CLI in some 'Learn more' links, and the overall pattern prioritizes Windows-native tooling.
Recommendations
- Add explicit bash/sh examples for Linux/macOS users, especially for common tasks.
- Clarify that Azure PowerShell is cross-platform, and provide installation/use guidance for Linux/macOS.
- Ensure CLI examples are shown first or in parallel with PowerShell, and highlight CLI as the recommended cross-platform tool.
- Where PowerShell is referenced, add notes or links for Linux/macOS installation and usage.
- Consider adding troubleshooting or environment setup notes for Linux/macOS users, especially where PowerShell is involved.
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation presents PowerShell as a primary method for configuring VM watch, with explicit PowerShell examples and references. While both CLI and ARM template methods are shown, the PowerShell example is given equal prominence, and there is no mention of Linux-specific shell commands (e.g., Bash) or guidance for Linux/macOS users beyond the Azure CLI. The instructions for finding the ARM template code segment reference Visual Studio Code, which is cross-platform but often associated with Windows. The documentation does clarify that the extension type differs for Windows and Linux, but does not provide Linux/macOS-specific command-line examples or troubleshooting tips.
Recommendations
- Add explicit Bash or shell examples for Linux/macOS users alongside PowerShell.
- Clarify that Azure CLI works cross-platform and highlight its use for Linux/macOS.
- Reorder examples to present CLI (cross-platform) before PowerShell.
- Include troubleshooting or environment notes for Linux/macOS users where relevant.
- Mention Linux-native editors (e.g., nano, vim) as alternatives to Visual Studio Code.
Virtual Machines
Remove a virtual machine scale set association from a capacity reservation group
...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/capacity-reservation-remove-virtual-machine-scale-set.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation provides API, Azure CLI, PowerShell, and Portal instructions for removing a VM scale set association from a capacity reservation group. PowerShell examples are given equal prominence to CLI, and PowerShell-specific cmdlets are referenced and linked, which may indicate a bias toward Windows tooling. The CLI examples use Azure CLI, which is cross-platform, but PowerShell is a Windows-centric tool (though available on Linux, it's less commonly used there). The documentation references PowerShell commands and links to their docs, but does not mention Bash, shell scripting, or Linux-native alternatives. In several places, PowerShell examples and references appear before or alongside CLI, but never after Linux-specific examples, and no Linux-specific tools or patterns are discussed.
Recommendations
- Add Bash or shell scripting examples for Linux users, especially for tasks that can be performed with REST API or Azure CLI.
- Clarify that Azure CLI is cross-platform and recommend it as the primary automation tool for Linux/macOS users.
- Reduce emphasis on PowerShell by moving PowerShell sections after CLI, or by explicitly noting PowerShell's cross-platform availability.
- Include notes or links to Linux/macOS-specific documentation or troubleshooting guides.
- Where PowerShell cmdlets are referenced, also provide equivalent CLI or REST API references.
Virtual Machines
Delete a VM and attached resources
...ute-docs/blob/main/articles/virtual-machines/delete.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation provides parity between Azure Portal, CLI, PowerShell, and REST API for managing VM deletion options. However, there is a notable Windows bias: PowerShell examples are given equal prominence to CLI, and PowerShell is a Windows-centric tool. REST API examples use Windows-specific images and OS types, and the FAQ and example sections reference Windows terminology and tools before Linux equivalents. The CLI examples are cross-platform, but Linux-specific scenarios are not highlighted, and Linux terminology is largely absent.
Recommendations
- Add explicit Linux/macOS shell examples (e.g., bash) where appropriate, especially for CLI usage.
- In REST API examples, use both Windows and Linux images and OS types to demonstrate parity.
- In FAQ and example sections, mention Linux scenarios and terminology alongside Windows.
- Clarify that PowerShell is primarily for Windows users and recommend CLI for Linux/macOS users.
- Provide links to Linux-focused documentation sections within the main content, not just in 'Next steps'.
Virtual Machines
Create Virtual Machine restore points
...ain/articles/virtual-machines/create-restore-points.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. Windows and PowerShell are mentioned before Linux and CLI alternatives, with PowerShell links and references given more prominence. There is no example or explicit guidance for Linux users (e.g., Bash, Azure CLI), and Windows-specific terminology (application consistency) is explained in more detail than Linux equivalents (file system consistency). The page lacks parity in examples and tool recommendations for Linux/macOS users.
Recommendations
- Add explicit Azure CLI and Bash examples alongside PowerShell for all API operations.
- Mention Linux/macOS tools and workflows equally, and provide direct links to CLI documentation before or alongside PowerShell.
- Clarify consistency modes for both Windows and Linux, and provide examples for each.
- Reorder references so that CLI and PowerShell are presented together, or CLI first if targeting cross-platform users.
- Include a section or tip specifically for Linux/macOS users outlining recommended tools and steps.
Virtual Machines
Migrate from Azure Disk Encryption to encryption at host
...n/articles/virtual-machines/disk-encryption-migrate.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific tools (PowerShell, manage-bde) and examples are often presented first or in greater detail, while Linux instructions are sometimes less explicit or relegated to comments. PowerShell is used heavily for both general and Linux scenarios, and Windows domain join/removal steps are more detailed than Linux equivalents. Some Linux migration steps (especially for encrypted OS disks) rely on external links or generic file transfer methods, rather than providing step-by-step parity with Windows. Windows-centric terminology and tools (e.g., manage-bde, Remove-Computer) are emphasized, and Linux alternatives are not always equally described.
Recommendations
- Present Linux and Windows examples side-by-side, with equal detail and prominence.
- Provide explicit Linux command-line examples (bash, CLI) for all major steps, not just PowerShell or comments.
- Expand Linux domain join/removal instructions with concrete commands and troubleshooting tips.
- Avoid presenting Windows steps or tools first; alternate or group by OS.
- Include more Linux-specific troubleshooting and verification steps (e.g., checking dm-crypt status, SELinux/AppArmor considerations).
- Ensure all PowerShell examples for Linux are matched with native Linux shell alternatives.
Virtual Machines
Server-side encryption of Azure managed disks
...blob/main/articles/virtual-machines/disk-encryption.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
minor_windows_reference
Summary
The documentation generally maintains parity between Windows and Linux, referencing both Azure PowerShell and Azure CLI for most tasks. However, there are several instances of Windows bias: Windows/PowerShell links and examples are consistently listed before Linux/CLI equivalents, and references to Windows-specific technologies (e.g., BitLocker, Cryptography API: Next Generation) appear without equal prominence for Linux alternatives. Some sections link only to Windows-specific articles for key tasks (e.g., automatic key rotation), and PowerShell is mentioned before CLI in revoking access instructions.
Recommendations
- Alternate the order of Windows and Linux examples/links to avoid consistently listing Windows first.
- Ensure all critical tasks (such as enabling automatic key rotation) have direct Linux/CLI documentation links, not just Windows/PowerShell.
- When referencing Windows technologies (e.g., BitLocker, CNG), also mention Linux equivalents (e.g., dm-crypt, cryptsetup) with equal detail.
- Where possible, provide cross-platform code samples or clarify that both PowerShell and CLI are supported for all operations.
- Review and update references to ensure Linux users are not directed to Windows-specific articles for core workflows.
Virtual Machines
Deploy a ZRS managed disk
...lob/main/articles/virtual-machines/disks-deploy-zrs.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a notable Windows bias. PowerShell is heavily used in Resource Manager Template and prerequisite sections, with no Bash or cross-platform alternatives. Windows-centric tools and patterns (e.g., ConvertTo-SecureString, PSCredential, Windows image references) are present throughout PowerShell and ARM template examples. In the PowerShell sections, only Windows VM creation is shown, with no Linux VM examples. The ARM template and feature registration steps use PowerShell exclusively, omitting Azure CLI or REST API equivalents. While Azure CLI examples use Linux images, the PowerShell and ARM template tabs are Windows-focused and shown before any Linux alternatives.
Recommendations
- Add Bash and Azure CLI equivalents for feature registration and ARM template deployment steps.
- Include Linux VM creation examples in PowerShell and ARM template sections.
- Provide REST API examples for feature registration and disk creation.
- Ensure examples for both Windows and Linux are present and balanced in all tabs.
- Explicitly note cross-platform alternatives where PowerShell is used.
- Reorder examples so that Linux and Windows are presented with equal prominence.
Virtual Machines
Ultra disks for VMs - Azure managed disks
...in/articles/virtual-machines/disks-enable-ultra-ssd.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation consistently provides examples using Windows images (Win2016Datacenter) in CLI and PowerShell commands, and references Windows-specific quickstarts for portal deployment. There are no explicit Linux VM examples or instructions for deploying Ultra Disks with Linux images, nor are there links to Linux-specific quickstarts. This creates friction for Linux users, who must infer how to adapt the instructions for their platforms.
Recommendations
- Add Linux VM examples alongside Windows examples in CLI and PowerShell sections (e.g., use Ubuntu or RHEL images).
- Include links to Linux VM quickstart documentation in the portal deployment instructions.
- Explicitly mention any differences or considerations for Linux VMs when deploying or managing Ultra Disks.
- Ensure parity in screenshots and walkthroughs for both Windows and Linux VM creation flows.
Virtual Machines
Instantly access managed disk snapshots
...les/virtual-machines/disks-instant-access-snapshots.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides both Azure CLI (cross-platform) and Azure PowerShell (Windows-centric) examples for creating instant access snapshots, but does not include explicit Linux/macOS shell examples or mention Linux-specific considerations. The PowerShell example is given equal prominence to Azure CLI, and no bash-specific or Linux-native instructions are provided. There is no mention of Linux tools or patterns, and the CLI examples use syntax compatible with bash but do not clarify Linux/macOS usage or differences.
Recommendations
- Add explicit bash/Linux/macOS shell examples for CLI commands, including variable declaration and command usage in those environments.
- Clarify that Azure CLI commands are cross-platform and provide any necessary notes for Linux/macOS users (e.g., environment variable syntax differences, authentication methods).
- Include troubleshooting or usage notes for Linux users, such as file permissions, shell compatibility, or installation instructions for Azure CLI on Linux/macOS.
- Consider adding a table or section comparing Azure CLI and PowerShell usage on different platforms.
- Ensure that Linux/macOS users are addressed in introductory sections to reinforce parity.
Virtual Machines
Deploy a Premium SSD v2 managed disk
...n/articles/virtual-machines/disks-deploy-premium-v2.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation demonstrates a Windows bias in several ways: VM creation examples consistently use Windows images (e.g., 'Win2016Datacenter'), variable names and credential handling are tailored to Windows conventions, and PowerShell is given equal prominence to Azure CLI throughout. There are no explicit Linux VM creation examples, nor are Linux-specific considerations (such as SSH authentication or Linux images) discussed. This may cause friction for Linux/macOS users, who must adapt Windows-centric instructions to their platforms.
Recommendations
- Add explicit Linux VM creation examples using common Linux images (e.g., UbuntuLTS) in Azure CLI and PowerShell sections.
- Include authentication examples using SSH keys for Linux VMs, rather than only password-based authentication.
- Clarify cross-platform usage of Azure CLI, emphasizing that it works natively on Linux/macOS.
- Balance PowerShell and CLI coverage, noting that PowerShell is primarily a Windows tool, while CLI is cross-platform.
- Adjust variable names and credential handling to be platform-neutral or provide both Windows and Linux variants.
Virtual Machines
Enable shared disks for Azure managed disks
.../main/articles/virtual-machines/disks-shared-enable.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for all disk types and operations, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and in some sections (such as 'Share an existing disk' and 'Using Azure shared disks with your VMs'), PowerShell examples are shown before CLI. There are no Linux-specific shell examples (e.g., Bash), nor are there any Linux/macOS-specific notes or guidance. The documentation assumes parity between CLI and PowerShell, but PowerShell is a Windows-first tool, and its prominence may create friction for Linux/macOS users.
Recommendations
- Always present Azure CLI examples before PowerShell, as CLI is cross-platform and native to Linux/macOS.
- Add explicit Bash shell examples where appropriate, especially for mounting disks to Linux VMs.
- Include notes or links for Linux/macOS users on how to install and use Azure CLI.
- Provide guidance or examples for disk attachment and SCSI PR commands using Linux tools (e.g., sg_persist, multipath).
- Clarify that PowerShell is optional and not required for Linux/macOS users.
Virtual Machines
Share an Azure managed disk across VMs
...cs/blob/main/articles/virtual-machines/disks-shared.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation shows moderate Windows bias. Windows clustering (WSFC) and related tools are described first and in greater detail, with explicit links to Windows-specific guides and templates. Linux support is mentioned, but Linux examples are less detailed, and there are no step-by-step Linux configuration examples. The 'Examples' section provides detailed Windows (WSFC) scenarios before Linux, and Linux examples lack equivalent depth. Windows tools and patterns (e.g., WSFC, CSV) are referenced more prominently than Linux equivalents (e.g., Pacemaker, Corosync).
Recommendations
- Add step-by-step Linux configuration examples, similar to those provided for Windows (e.g., setting up Pacemaker/Corosync with shared disks).
- Provide Linux-first or parallel examples in the 'Examples' section to balance the order and depth of coverage.
- Include links to official Linux HA cluster documentation and templates, as is done for Windows.
- Explicitly mention and provide guidance for Linux-specific tools (e.g., sg_persist, fence_scsi) in the context of Azure shared disks.
- Ensure parity in the level of detail for both Windows and Linux sections, especially for common workloads and deployment scenarios.
Virtual Machines
What's new in Azure Disk Storage
...blob/main/articles/virtual-machines/disks-whats-new.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page is primarily a feature update summary and does not provide detailed code examples. However, there is evidence of Windows bias in the form of Windows documentation links being presented before Linux equivalents, references to Windows-specific tools (PowerShell), and some update links pointing only to Windows guides. Linux/macOS parity is not always clear, and in some cases, Linux documentation is referenced after Windows, or not at all.
Recommendations
- Ensure that all feature documentation and how-to guides are linked for both Windows and Linux/macOS users, ideally side-by-side.
- Avoid listing Windows documentation links before Linux equivalents; use a neutral or alphabetical order.
- Where PowerShell or Windows tools are mentioned, also mention Linux/macOS equivalents (e.g., Bash, Azure CLI) and provide links.
- Audit all referenced documentation to ensure Linux/macOS users can complete tasks without friction.
- Add explicit statements about cross-platform support for new features where relevant.
Virtual Machines
Deploy Ephemeral OS disks
...articles/virtual-machines/ephemeral-os-disks-deploy.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 support in principle, but several sections show Windows bias. PowerShell examples are given in detail, while no Linux-specific shell examples (e.g., Bash) are provided. Template examples use Windows images by default, and admin credentials are shown as username/password rather than SSH keys. Windows tools (PowerShell) are covered in a dedicated section, while Linux equivalents (e.g., Bash scripting, cloud-init) are missing. The CLI section is neutral, but overall, Windows patterns and tools are prioritized.
Recommendations
- Add explicit Linux VM template examples using popular Linux images (e.g., Ubuntu, CentOS) and SSH key authentication.
- Provide Bash or shell scripting equivalents for PowerShell commands, especially for VM and scale set deployments.
- Include Linux-specific guidance for admin credential setup (e.g., using --generate-ssh-keys in CLI, cloud-init for customization).
- Balance the order of examples so that Linux and Windows are equally represented, or alternate which comes first.
- Add notes or links to Linux admin tooling and best practices for ephemeral OS disk deployments.
Virtual Machines
Use Azure Storage Explorer to manage Azure managed disks
...l-machines/disks-use-storage-explorer-managed-disks.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page describes using Azure Storage Explorer, a cross-platform GUI tool, to manage Azure managed disks. While the main instructions are platform-neutral, the 'Next steps' section exclusively links to Windows VM scenarios and does not provide Linux equivalents. There are no Linux-specific examples or guidance, and Windows is implicitly prioritized in follow-up tasks.
Recommendations
- Add 'Next steps' links for Linux VM scenarios, such as creating a VM from a VHD or attaching a managed disk to a Linux VM.
- Ensure parity in example tasks and follow-up documentation for both Windows and Linux users.
- Explicitly mention that Azure Storage Explorer is available on Linux/macOS and provide installation instructions for those platforms if not already present.
- Where relevant, include screenshots or notes for Linux/macOS versions of the tool to reassure non-Windows users.
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides a detailed PowerShell script for determining VM support for ephemeral OS disks, but does not offer equivalent examples for Linux/macOS users (e.g., Bash, Azure CLI). PowerShell is featured exclusively and prominently, creating friction for non-Windows users. The mention of CLI is generic and lacks concrete examples.
Recommendations
- Add equivalent Azure CLI (bash) examples/scripts for checking VM SKU support for ephemeral OS disks.
- Present CLI and PowerShell examples side-by-side or in parallel sections to ensure parity.
- Explicitly mention cross-platform alternatives and clarify which commands/tools work on Linux/macOS.
- Consider providing downloadable scripts in both PowerShell and Bash formats.
Virtual Machines
Export Azure resource groups that contain VM extensions
...ticles/virtual-machines/extensions/export-templates.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing Windows tools and patterns first and most prominently. The sample deployment scripts generated by the export process are described as 'PowerShell and Azure CLI scripts', with PowerShell mentioned first and no explicit mention of Bash or Linux shell scripts. The ms.collection metadata is set to 'windows', and the list of supported extensions names Windows versions before Linux equivalents. There are no explicit Linux/macOS-specific instructions or examples, and no screenshots or walkthroughs for Linux users.
Recommendations
- Mention Bash or Linux shell script samples alongside PowerShell and Azure CLI, and provide explicit examples for Linux/macOS users.
- Ensure extension lists alternate or group Windows and Linux versions equally, rather than listing Windows first.
- Add screenshots or step-by-step instructions for Linux/macOS users where UI or CLI differences exist.
- Update metadata (ms.collection) to include Linux if the content is cross-platform.
- Clarify that Azure CLI is cross-platform and provide examples of its use on Linux/macOS.
Virtual Machines
Azure support for Generation 2 VMs
...cs/blob/main/articles/virtual-machines/generation-2.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation displays moderate Windows bias. Windows examples and PowerShell commands are presented before Linux equivalents, and some critical steps (such as uploading and creating managed disks from .vhd files) are only shown using Windows/PowerShell tooling, with no Linux CLI or cross-platform alternatives. References to Hyper-V and Windows-centric features appear more frequently and are linked before Linux resources. While Linux support is mentioned and some CLI examples are provided, Linux users may encounter friction due to missing or less prominent Linux-specific guidance.
Recommendations
- Provide equivalent Linux examples for all PowerShell commands, especially for tasks like creating managed disks from .vhd files (e.g., using Azure CLI or REST API).
- Ensure Linux and Windows examples are presented with equal prominence, ideally side-by-side or in parallel sections.
- Include references to Linux-specific documentation and tools where appropriate, not just Windows/Hyper-V.
- When listing supported images or features, alternate the order or group by OS type to avoid Windows-first presentation.
- Add explicit instructions for Linux users in sections where only Windows/PowerShell guidance is given.
Virtual Machines
Tenable One-Click Nessus Extension for Azure VMs
...b/main/articles/virtual-machines/extensions/tenable.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides only PowerShell command-line examples for deploying the Nessus Agent extension, which is primarily a Windows-centric tool. No Linux-native CLI examples (such as Azure CLI or Bash) are provided, and the command-line section is introduced as 'PowerShell' without mentioning alternatives. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer Bash/Azure CLI. Additionally, the command-line instructions and parameter descriptions are presented from a Windows/PowerShell perspective.
Recommendations
- Add equivalent Azure CLI (az vm extension set) examples for Linux/macOS users.
- Explicitly mention that PowerShell is available cross-platform, but provide Bash/Azure CLI alternatives for users who prefer native Linux tools.
- Reorder or parallelize examples so that Linux and Windows approaches are presented with equal prominence.
- Clarify any platform-specific requirements or limitations in the deployment process.
Virtual Machines
Azure FPGA Attestation Service
...machines/field-programmable-gate-arrays-attestation.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides both PowerShell and Bash script examples for attestation, but PowerShell is presented first and in greater detail (including monitoring and validation steps). The Bash example is less complete, lacking explicit instructions for monitoring attestation status. There is a notable emphasis on PowerShell tooling and scripts, with some post-validation steps and monitoring only described for PowerShell, leaving Linux/macOS users without equivalent guidance.
Recommendations
- Provide Bash/Linux equivalents for all PowerShell scripts, especially for monitoring attestation status (e.g., a Bash script or curl command for polling status).
- Present Bash and PowerShell examples side-by-side, or alternate which is shown first, to avoid implicit prioritization of Windows.
- Explicitly mention how Linux/macOS users can perform all steps, including post-validation and error checking.
- Clarify that all scripts and tools are cross-platform, and highlight any platform-specific limitations.
- Add troubleshooting and support instructions for Linux/macOS users.
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation page exhibits a moderate Windows bias. The PowerShell method is presented first and in greatest detail, with multiple example scripts and cmdlet explanations. The REST API section requires installing armclient via Chocolatey, a Windows-only package manager, with instructions only for Windows (cmd.exe/PowerShell). There are no Linux/macOS installation alternatives for armclient. While Azure CLI and portal methods are included and are cross-platform, the CLI section is brief and lacks step-by-step examples compared to PowerShell. Windows disk management tools are mentioned before Linux equivalents in planning guidance.
Recommendations
- Provide Linux/macOS installation instructions for armclient, or recommend a cross-platform REST client (e.g., curl, httpie) with example commands.
- Expand Azure CLI examples to match the detail and scenarios covered in the PowerShell section, including step-by-step scripts.
- When listing disk/volume managers, alternate or balance the order between Windows and Linux tools.
- Explicitly note cross-platform compatibility for all tooling and commands.
- Consider adding Bash or shell script examples for Linux users where appropriate.
Virtual Machines
Create an image definition and image version
...s/blob/main/articles/virtual-machines/image-version.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation provides parity between Windows and Linux in most CLI and REST examples, but PowerShell examples are Windows-centric, and Windows terminology (Sysprep, PowerShell cmdlets) is mentioned before Linux equivalents. The PowerShell tab focuses on Windows scenarios, with Linux only briefly referenced. Windows tools and patterns (Sysprep, PowerShell) are mentioned before Linux equivalents (waagent).
Recommendations
- Provide explicit Linux-focused PowerShell examples (e.g., using -OsType Linux and Linux-specific preparation steps).
- Ensure Linux preparation steps (waagent) are mentioned alongside or before Windows (Sysprep) in all relevant sections.
- Balance example order so Linux and Windows are presented equally, or alternate which is shown first.
- Add notes or links for Linux users in PowerShell sections, clarifying how to adapt commands for Linux images.
- Where Windows tools (Sysprep, PowerShell) are referenced, ensure Linux alternatives are equally described and linked.
Virtual Machines
Customer intent: "As an IT administrator managing virtual machines, I want to aggregate OS update statuses and availability states across my machines, so that I can efficiently monitor and ensure the health of my infrastructure."
...es/virtual-machines/includes/azure-virtual-machines.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation presents both Azure CLI and Azure PowerShell examples for each query, with PowerShell (a Windows-centric tool) always included and often referenced in metadata and custom tags. Windows-specific terminology and tools (e.g., PowerShell, KB IDs for Windows updates) are present throughout. While Linux is supported (e.g., queries for Linux patching), Windows examples and terminology appear first and more frequently. There are no Linux/macOS-specific shell examples (e.g., bash, zsh), nor are there references to Linux-native tools or patterns outside of Azure CLI. The documentation does not provide parity for Linux/macOS users who may prefer native shell scripting or tools.
Recommendations
- Add bash/zsh shell script examples for Linux/macOS users alongside PowerShell.
- Ensure Linux-specific queries and terminology are presented with equal prominence and order as Windows examples.
- Reference Linux-native tools (e.g., curl, jq, grep) where appropriate for scripting and automation.
- Clarify that Azure CLI is cross-platform and highlight usage on Linux/macOS.
- Remove or balance Windows-centric metadata and custom tags (e.g., devx-track-azurepowershell) with Linux/macOS equivalents.
Virtual Machines
Create an encrypted image version with customer-managed keys
.../articles/virtual-machines/image-version-encryption.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples are presented first and in greater detail, with explicit references to Windows-centric tools and APIs (e.g., Cryptography API: Next Generation). While Azure CLI and Portal instructions are provided, the PowerShell section is more extensive, and Windows tools are mentioned before their Linux equivalents. There are no Linux-specific command-line examples or references to Linux-native tools or patterns.
Recommendations
- Present CLI examples before or alongside PowerShell examples to better support Linux/macOS users.
- Expand CLI instructions to match the detail and coverage of PowerShell examples.
- Include explicit notes or examples for Linux/macOS environments, such as shell scripting or integration with Linux-native tools.
- Replace or supplement references to Windows-specific cryptographic APIs with platform-neutral or Linux-relevant documentation.
- Clarify that Azure CLI works cross-platform and highlight any OS-specific considerations.
Virtual Machines
Customer intent: As a cloud storage administrator, I want to adjust the expiration settings of Shared Access Signatures for disks and snapshots, so that I can ensure compliance with the upcoming 60-day limit and maintain uninterrupted access for my users.
...articles/virtual-machines/includes/disks-sas-change.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation lists Azure PowerShell as a primary tool for managing SAS on disks and snapshots, alongside REST API and Azure CLI. PowerShell is a Windows-centric tool, and its mention in every example (with direct links) may suggest a Windows bias. Additionally, PowerShell is listed after REST API and Azure CLI, but its inclusion in all workflows may imply parity that doesn't exist for Linux/macOS users, as PowerShell is less commonly used or installed by default on those platforms.
Recommendations
- Explicitly state that Azure CLI and REST API are fully cross-platform and preferred for Linux/macOS users.
- Provide example commands for Azure CLI and REST API for each task, and clarify installation/usage instructions for non-Windows platforms.
- De-emphasize PowerShell as a primary tool, or provide equivalent bash/shell script examples.
- Add a note about PowerShell Core availability on Linux/macOS if PowerShell examples are retained.
Virtual Machines
Customer intent: "As an IT administrator, I want to troubleshoot common VM extension failures in Azure Resource Manager templates, so that I can ensure the proper deployment and functionality of IaaS infrastructure."
...des/virtual-machines-common-extensions-troubleshoot.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page references a Windows-specific template authoring guide and links to a Windows-focused TOC, without mentioning or providing equivalent Linux resources or examples. This suggests a bias toward Windows environments in both guidance and resource organization.
Recommendations
- Include links to Linux-specific template authoring documentation alongside Windows resources.
- Provide troubleshooting examples and guidance for both Windows and Linux VM extensions.
- Ensure TOC and navigation options are available for Linux users.
- Explicitly state when guidance applies to both platforms, or clarify differences.
Virtual Machines
Customer intent: As a system administrator, I want to hibernate and manage virtual machines using various tools, so that I can optimize resource usage and maintain system performance effectively.
...nes/includes/hibernate-resume-platform-instructions.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation demonstrates a moderate Windows bias. PowerShell examples are provided for every operation, often with detailed output, while Linux/macOS-specific shell examples (e.g., Bash) are not shown. The only CLI examples use Azure CLI, which is cross-platform, but PowerShell (Windows-centric) is given equal or greater prominence, and Windows-specific requirements (e.g., page file on C:) are called out without Linux equivalents. There are no explicit Linux/macOS shell command examples, and the documentation assumes familiarity with Windows tools and patterns.
Recommendations
- Add explicit Bash or Linux/macOS shell examples for each operation, especially for viewing VM state and managing hibernation.
- Clarify that Azure CLI commands work on Linux/macOS, and provide sample outputs from those platforms.
- For OS configuration notes, include Linux-specific guidance (e.g., swap file or hibernation setup for Linux VMs).
- Balance PowerShell and CLI examples, and avoid giving PowerShell more detail or prominence than CLI.
- Where Windows-specific requirements are listed, add equivalent Linux/macOS requirements or explicitly state if none exist.
Virtual Machines
Customer intent: As a cloud security administrator, I want to configure Azure Key Vault and Disk Encryption Set so that I can securely manage encryption keys for our managed disks across multiple subscriptions in compliance with security policies.
...-machines-disks-encryption-create-key-vault-powershell.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation exclusively uses Azure PowerShell for all examples and instructions, with no mention of Azure CLI, Bash, or Linux/macOS workflows. All commands and setup steps assume the use of PowerShell, which is natively available only on Windows and less commonly used on Linux/macOS. There are no alternative examples or guidance for users on non-Windows platforms.
Recommendations
- Add equivalent Azure CLI examples for all steps, as Azure CLI is cross-platform and commonly used on Linux/macOS.
- Explicitly mention that PowerShell examples can be run on Linux/macOS if PowerShell Core is installed, but provide CLI/Bash alternatives for greater accessibility.
- Include a section or note on platform compatibility, clarifying which tools are available on which operating systems.
- Consider reordering examples so that cross-platform tools (Azure CLI) are presented first or alongside PowerShell.
Virtual Machines
Customer intent: As a cloud administrator, I want to retrieve the encryption type of a specified disk in a resource group, so that I can ensure compliance with security standards for our virtual machines.
...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/includes/virtual-machines-disks-encryption-status-powershell.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation provides only a PowerShell example for retrieving the encryption type of a disk in Azure, with no equivalent example for Linux/macOS users (e.g., Azure CLI or Bash). This creates a bias towards Windows environments and tools.
Recommendations
- Add an Azure CLI example for Linux/macOS users.
- Include Bash or shell script alternatives where possible.
- Clearly indicate platform requirements for each example.
Virtual Machines
Customer intent: "As a cloud administrator, I want to create and manage incremental snapshots of virtual disks, so that I can efficiently utilize storage and ensure data integrity while complying with the snapshot limitations and performance impacts."
...tual-machines-disks-incremental-snapshots-restrictions.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation page references Azure PowerShell samples before Azure CLI, and links to PowerShell scripts for critical operations like checking disk status and managing snapshots. While Azure CLI is mentioned, the primary example and link are PowerShell-focused, which may create friction for Linux/macOS users who typically use CLI or Bash scripts.
Recommendations
- Provide Linux/macOS-specific examples using Azure CLI and Bash where PowerShell is referenced.
- Ensure that CLI examples are given equal prominence and are linked directly, not only as secondary options.
- Explicitly mention cross-platform compatibility for all scripts and commands.
- Add a section or note clarifying how Linux/macOS users can perform all documented tasks without PowerShell.
Virtual Machines
Customer intent: As a cloud architect, I want to understand the limitations of shared disks across different disk types, so that I can effectively design and implement scalable virtual machine solutions in the cloud environment.
.../includes/virtual-machines-disks-shared-limitations.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation repeatedly references Windows Server Failover Cluster as the only clustering solution, linking exclusively to Windows Server documentation. There are no mentions of Linux clustering solutions (e.g., Pacemaker, Corosync), nor any Linux-specific limitations or guidance. All clustering examples and hardware requirements are Windows-centric, creating a perception that shared disk features are primarily for Windows users.
Recommendations
- Add references to Linux clustering solutions (such as Pacemaker or Corosync) and discuss their compatibility and limitations with Azure shared disks.
- Include links to Linux documentation for clustering and shared disk usage.
- Explicitly state whether shared disks are supported or unsupported for Linux-based clusters, and provide guidance for Linux users.
- Balance examples and references between Windows and Linux to ensure parity.
Virtual Machines
Use infrastructure automation tools
...articles/virtual-machines/infrastructure-automation.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation generally covers both Linux and Windows automation tools, but there are several instances of Windows bias. Windows-specific tools (PowerShell DSC, Windows Resource Manager template examples, Chef on Windows, Puppet install on Windows) are mentioned or linked before Linux equivalents, and some sections lack Linux examples or parity (e.g., Chef and Puppet). Windows tools like PowerShell DSC are highlighted, while Linux alternatives (cloud-init, Ansible) are sometimes presented later or with less detail. Some 'Learn how to' links are Windows-only or Windows-first.
Recommendations
- Ensure every Windows example or link has a Linux/macOS equivalent, especially for Chef and Puppet sections.
- Present Linux and Windows examples side-by-side or in parallel, rather than listing Windows first.
- Add more Linux-focused 'Learn how to' links for Chef and Puppet, not just Windows install guides.
- Where Windows tools (e.g., PowerShell DSC) are mentioned, also highlight Linux-native alternatives (e.g., Ansible, cloud-init) with equal prominence.
- Review ordering of examples and links to avoid Windows-first presentation.
- Clarify cross-platform support in each section, especially where only Windows is referenced.
Virtual Machines
Prepare Linux for imaging
...ticles/virtual-machines/linux/create-upload-generic.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page is focused on Linux preparation for Azure imaging, but references to Windows tools (Hyper-V Manager, PowerShell cmdlets) are given first and in more detail than Linux alternatives. For example, disk conversion and resizing instructions prioritize Hyper-V Manager and PowerShell (Convert-VHD, Resize-VHD) before mentioning Linux tools like qemu-img. This ordering and emphasis may create friction for Linux users, although Linux alternatives are provided.
Recommendations
- Present Linux-native tools (qemu-img, vbox-manage) before or alongside Windows tools when discussing disk conversion and resizing.
- Provide more detailed Linux-specific instructions for tasks currently described with Windows tools (e.g., converting VHDX to VHD using qemu-img).
- Include explicit examples for common Linux environments (e.g., KVM, VirtualBox) where only Hyper-V/Windows instructions are currently detailed.
- Clarify that Windows tools are optional and not required for Linux users.
- Ensure that all critical steps can be completed using Linux-native tools, with equal detail and prominence.
Virtual Machines
Create and upload a CentOS-based Linux VHD
...rticles/virtual-machines/linux/create-upload-centos.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates a notable Windows bias by exclusively referencing Hyper-V (a Windows virtualization tool) for creating and managing VHDs, providing links to Windows-centric instructions, and omitting equivalent Linux-based workflows (such as using KVM, qemu-img, or VirtualBox CLI). Windows tools and terminology (Hyper-V Manager, convert-vhd cmdlet) are mentioned first and sometimes exclusively, while Linux alternatives are only briefly referenced or not explained in detail.
Recommendations
- Add step-by-step instructions for creating and converting VHDs using Linux-native tools (e.g., qemu-img, KVM, VirtualBox CLI).
- Include links to official documentation for Linux virtualization solutions and disk conversion utilities.
- Present Linux and Windows options side-by-side, or provide separate sections for each platform.
- Clarify that Hyper-V is only one of several options and not a requirement.
- Provide parity in example commands and screenshots for Linux environments.
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
missing_linux_example
Summary
The documentation page is focused on creating and uploading an Ubuntu Linux VHD for Azure, but it repeatedly references Windows-specific tools (notably Hyper-V and PowerShell's Convert-VHD) for VHD creation and conversion. Instructions for using Hyper-V Manager and Convert-VHD are provided, but there are no equivalent examples or guidance for Linux-native virtualization and disk conversion tools (e.g., qemu-img, VirtualBox, KVM). Windows tools are mentioned first and exclusively in critical steps, creating friction for Linux/macOS users.
Recommendations
- Add instructions and examples for creating and converting VHDs using Linux-native tools such as qemu-img, VirtualBox, or KVM.
- Provide parity for disk conversion steps, e.g., show how to convert raw disks to fixed-size VHD using qemu-img.
- Include links to Linux/macOS virtualization guides alongside the Hyper-V references.
- Clarify which steps are platform-agnostic and which require platform-specific tooling, offering alternatives where needed.
Virtual Machines
Creating and configuring a key vault for Azure Disk Encryption with Microsoft Entra ID (previous release)
...irtual-machines/linux/disk-encryption-key-vault-aad.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation provides extensive PowerShell examples and scripts, including certificate handling paths using Windows conventions (e.g., C:\certificates), and relies heavily on Windows-centric tooling. While Azure CLI and portal instructions are included, PowerShell is often presented first and in greater detail. There are no Linux shell (bash) or macOS-specific examples, and certificate-based authentication is explicitly noted as unsupported on Linux VMs, but Windows patterns are still shown. The lack of Linux-native scripting or file path examples may create friction for Linux users.
Recommendations
- Add bash shell examples for all major steps, especially for certificate generation, file handling, and key vault operations.
- Include Linux file path conventions (e.g., /home/user/certs/mycert.pfx) in examples alongside Windows paths.
- Clarify which steps are cross-platform and which are Windows-only, especially for certificate-based authentication.
- Present Azure CLI examples before PowerShell when targeting Linux audiences.
- Explicitly mention Linux prerequisites and common tools (e.g., openssl for certificate generation) where relevant.
Virtual Machines
Creating and configuring a key vault for Azure Disk Encryption
...es/virtual-machines/linux/disk-encryption-key-vault.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
powershell_heavy
windows_first
Summary
While the documentation is targeted at Linux VM administrators and references Linux-specific quickstarts, it repeatedly presents Azure PowerShell (a Windows-centric tool) alongside Azure CLI, and links to PowerShell scripts and quickstarts as primary resources. PowerShell examples and tools are mentioned as equally valid for Linux, but in practice, PowerShell is far less common on Linux. The documentation also lists PowerShell scripts before CLI scripts in several places, and does not clarify that CLI is the more typical tool for Linux users.
Recommendations
- Prioritize Azure CLI examples and scripts in the main text and quickstart listings, as CLI is the standard on Linux.
- Clearly indicate that Azure PowerShell is less commonly used on Linux and provide installation guidance only as a secondary option.
- List CLI scripts and quickstarts before PowerShell equivalents in all sections.
- Add explicit notes about tool suitability for Linux, e.g., 'Azure CLI is recommended for Linux users.'
- Remove or de-emphasize PowerShell references in sections specifically targeting Linux unless there is a compelling cross-platform reason.
Virtual Machines
Azure Disk Encryption scenarios on Linux VMs
...ticles/virtual-machines/linux/disk-encryption-linux.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
powershell_heavy
windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all major operations, but PowerShell (a Windows-centric tool) is given equal or greater prominence throughout. PowerShell cmdlets are referenced first in some critical backup instructions, and PowerShell-specific patterns (e.g., sequence version GUID generation) are explained in detail. There are multiple references to using PowerShell locally, and some instructions (such as Resource Manager template parameter retrieval) show PowerShell before CLI. The documentation assumes familiarity with PowerShell and its workflow, which may create friction for Linux/macOS users who prefer Bash and CLI tools.
Recommendations
- Prioritize Azure CLI examples and instructions before PowerShell, as CLI is cross-platform and native to Linux/macOS.
- Where PowerShell-specific steps are described (e.g., GUID generation for sequence version), provide equivalent Bash/CLI instructions or clarify that CLI handles these automatically.
- In Resource Manager template sections, show CLI commands before PowerShell, or present both together with equal prominence.
- Clarify that PowerShell is available on Linux/macOS, but recommend CLI for Linux users.
- Reduce references to Windows-centric workflows (e.g., local PowerShell installation) and highlight cross-platform alternatives.
- Add explicit Bash script examples for common tasks (e.g., variable initialization, disk mounting) where PowerShell scripts are shown.
Virtual Machines
Azure Disk Encryption sample scripts
...rtual-machines/linux/disk-encryption-sample-scripts.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation page, while focused on Azure Disk Encryption for Linux VMs, provides almost all automation and Azure interaction examples using PowerShell cmdlets and scripts. Key tasks such as listing encrypted VMs, uploading VHDs, managing Key Vault secrets, and attaching disks are shown exclusively with PowerShell, a Windows-centric tool. There are no az CLI, Bash, or Linux-native command examples for these Azure operations, and PowerShell is presented as the default/only method for interacting with Azure resources, which may create friction for Linux/macOS users who prefer or require non-Windows tooling.
Recommendations
- Provide equivalent az CLI and Bash script examples for all Azure resource management tasks (listing encrypted VMs, uploading VHDs, managing Key Vault secrets, attaching disks).
- Clearly indicate when PowerShell is required and offer guidance for installing and using PowerShell Core on Linux/macOS, or alternatives using native Linux tools.
- Where possible, link to or embed Linux-native workflows for Azure Disk Encryption tasks, ensuring parity in automation and scripting.
- Reorder examples so that Linux-native tools (az CLI, Bash) are presented before or alongside PowerShell, especially in documentation targeted at Linux users.
Virtual Machines
Azure Disk Encryption with Microsoft Entra App Linux IaaS VMs (previous release)
...es/virtual-machines/linux/disk-encryption-linux-aad.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation provides both Azure CLI and PowerShell examples for Linux VM disk encryption, but PowerShell is emphasized throughout, with more detailed scripts and explanations. Windows-centric tools and terminology (PowerShell cmdlets, Windows flags, references to BitLocker and Windows disk operations) are used extensively, sometimes even in Linux-specific contexts. In several places, PowerShell examples are presented before CLI, and some sections (e.g., pre-encrypted VHD) use Windows flags or lack explicit Linux CLI parity. There are also minor instances of Windows terminology in template instructions and backup/restore references.
Recommendations
- Ensure CLI examples are as detailed and prominent as PowerShell examples, especially for Linux scenarios.
- Remove or clarify Windows-specific flags (e.g., '-Windows' in Set-AzVMOSDisk) when describing Linux workflows.
- Add explicit Linux shell commands for disk operations (e.g., formatting, mounting) alongside PowerShell scripts.
- Review template instructions to ensure Linux terminology is used and avoid references to Windows VMs in Linux sections.
- Where PowerShell is referenced, clarify its cross-platform availability or provide equivalent bash/CLI instructions.
- Consider reordering sections so CLI examples appear before PowerShell for Linux-focused documentation.
Virtual Machines
Azure Disk Encryption with Microsoft Entra app prerequisites (previous release)
...virtual-machines/linux/disk-encryption-overview-aad.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page, while focused on Linux VMs, contains several instances of Windows bias. Windows-specific registry changes and BitLocker Group Policy settings are described in detail, with no equivalent Linux security or encryption configuration guidance. Windows tools (PowerShell scripts) are referenced explicitly, and Windows examples appear before or instead of Linux alternatives. There is little to no coverage of Linux-specific troubleshooting or configuration steps for disk encryption prerequisites.
Recommendations
- Add Linux-specific troubleshooting and configuration guidance, especially for network, TLS, and encryption prerequisites.
- Include Linux command-line examples (e.g., Bash, CLI) for verifying connectivity and configuring prerequisites.
- Provide parity in script references by highlighting Linux CLI scripts equally or before PowerShell scripts.
- If Windows-specific sections are necessary, clearly separate them and provide equivalent Linux sections.
- Mention Linux disk encryption mechanisms (e.g., dm-crypt, cryptsetup) if relevant, and clarify any differences in prerequisites.
Virtual Machines
How to upgrade Azure Disk Encryption on a disk
...cles/virtual-machines/linux/disk-encryption-upgrade.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page exhibits a notable Windows bias. The migration process is only documented using Azure PowerShell, with no Linux-specific CLI or script examples. The upgrade instructions and examples focus on PowerShell, a Windows-centric tool, and do not provide parity for Linux users. While the CLI is mentioned for version discovery, it is not offered for the migration step, and the migration process appears inaccessible to Linux-only environments.
Recommendations
- Provide Azure CLI-based migration instructions if supported, or clarify if migration is only possible via PowerShell.
- Include Bash or shell script examples for Linux users, or document how Linux administrators can perform the migration from non-Windows environments.
- Explicitly state platform requirements and offer guidance for Linux/macOS users on installing and using Azure PowerShell (e.g., via PowerShell Core on Linux).
- If migration is not possible outside PowerShell, add a clear note about this limitation and suggest alternatives or workarounds for Linux-only environments.
Virtual Machines
Azure CLI - Enable customer-managed keys with SSE - managed disks
...chines/linux/disks-enable-customer-managed-keys-cli.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation is primarily cross-platform and uses Azure CLI examples, which are suitable for both Linux and Windows. However, in the 'Next steps' section, PowerShell-based disaster recovery guides for VMware and Hyper-V are mentioned, which are Windows-centric tools. These are listed before any Linux-specific alternatives, and no Linux equivalents or parity guidance are provided for these scenarios.
Recommendations
- Add Linux/bash-based instructions or links for disaster recovery scenarios currently covered only by PowerShell.
- Explicitly mention if certain tasks (e.g., disaster recovery for VMware/Hyper-V) can be performed with Azure CLI or other cross-platform tools, or clarify Windows-only limitations.
- Reorder or balance the 'Next steps' section to present Linux-friendly options before or alongside Windows/PowerShell options.
- Where PowerShell is required, provide a note about Linux/macOS alternatives or workarounds, if any.
Virtual Machines
Enable end-to-end encryption using encryption at host - Azure CLI - managed disks
...chines/linux/disks-enable-host-based-encryption-cli.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation is primarily focused on Azure CLI usage, which is cross-platform and Linux-friendly. However, there are signs of Windows bias: references to PowerShell and Windows tools (especially in the 'Next steps' section, which links only to PowerShell samples), and important notes about breaking changes for 'PowerShell and Azure CLI' users, with PowerShell mentioned first. There are no explicit Linux/macOS examples, and the linked sample repository is PowerShell-centric, potentially leaving Linux users without parity for advanced scenarios.
Recommendations
- Add explicit Bash/Linux shell script samples alongside PowerShell samples in the linked repository.
- Provide links to Linux/macOS-specific documentation or sample repositories for managed disk encryption scenarios.
- When mentioning tooling, avoid listing PowerShell before CLI, or clarify cross-platform support.
- Include a note in 'Next steps' about where Linux/macOS users can find equivalent resources.
- Ensure that all example scripts in the documentation itself are tested and work on Linux/macOS (which is mostly true here, but the external samples are PowerShell-only).
Virtual Machines
Upload a VHD to Azure or copy a disk across regions - Azure CLI
...machines/linux/disks-upload-vhd-to-managed-disk-cli.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page exhibits moderate Windows bias. The primary upload example uses 'AzCopy.exe' with a Windows-style path, and does not provide a Linux/macOS equivalent (e.g., 'azcopy' or './azcopy' with POSIX paths). The only explicit file path example is Windows ('c:\somewhere\mydisk.vhd'), and there is no mention of Linux/macOS installation or usage patterns for AzCopy. The page also refers to preparing VHDs for Azure with a link to a Windows-specific guide, without referencing a Linux alternative. While most Azure CLI commands are cross-platform, the AzCopy section is Windows-centric, and Linux users may be left to infer how to adapt the instructions.
Recommendations
- Provide explicit AzCopy command examples for Linux/macOS, using POSIX paths (e.g., '/home/user/mydisk.vhd') and the correct executable name ('azcopy' or './azcopy').
- Include instructions or links for installing AzCopy on Linux/macOS, not just Windows.
- Reference or link to a guide for preparing VHDs for Azure from Linux, in addition to the Windows guide.
- Where file paths are shown, offer both Windows and Linux/macOS variants.
- Clarify that Azure CLI and AzCopy are cross-platform, and note any platform-specific differences.
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
windows_tools
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides both Windows and Linux coverage, but there is a notable Windows bias in several areas: PowerShell commands and tools are frequently referenced (sometimes exclusively), Windows-specific customizers (WindowsRestart, WindowsUpdate) exist without Linux equivalents, and Windows examples or notes often appear before Linux ones. Some instructions (e.g., generating SHA256 checksums, troubleshooting, Sysprep) are Windows-centric or use PowerShell as the default, with Linux alternatives mentioned later or not at all. The lack of a Linux restart customizer and the prioritization of Windows tools and patterns create friction for Linux/macOS users.
Recommendations
- Provide Linux/macOS command alternatives alongside PowerShell examples, especially for checksum generation and troubleshooting.
- Ensure Linux examples are presented with equal prominence and detail as Windows examples.
- Add a Linux restart customizer or document recommended Linux restart patterns for parity.
- Where Windows-only features exist (e.g., WindowsRestart, WindowsUpdate), clearly state Linux alternatives or workarounds.
- Avoid presenting Windows tools or patterns first unless they are universally applicable; alternate order or group by OS.
- Expand troubleshooting and operational examples to include Linux-native tools and commands.
Virtual Machines
Learn about hibernating your Linux virtual machine
...icles/virtual-machines/linux/hibernate-resume-linux.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 creating and managing Linux VMs with hibernation, but PowerShell examples are given equal prominence to CLI, despite PowerShell being a Windows-centric tool. The use of PowerShell is pervasive throughout, and in some cases, PowerShell is presented before or alongside CLI, which may create friction for Linux/macOS users who typically use Bash and CLI. There is also mention of 'git bash' for running Linux commands, which is a Windows tool, and may confuse native Linux users.
Recommendations
- Prioritize Azure CLI and Bash examples over PowerShell, as these are more native to Linux/macOS environments.
- Move PowerShell examples to a separate section or clearly mark them as relevant for Windows users managing Linux VMs remotely.
- Remove references to 'git bash' when instructing users to run commands on Linux; simply refer to the terminal or shell.
- Ensure all steps and examples can be completed using native Linux tools and workflows.
- Add explicit notes clarifying which examples are intended for Windows users and which for Linux/macOS users.
Virtual Machines
How to Connect to the Azure Image Builder build VM
...al-machines/linux/image-builder-connect-to-build-vm.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. Windows terminology (RDP, WinRM) is frequently mentioned, and Windows examples or documentation links are often listed before or alongside Linux equivalents. Some sections, such as password reset instructions, reference the Azure portal's 'Reset Password' blade, which is primarily relevant for Windows VMs. The Azure Bastion section refers to connecting to a Windows VM using SSH or RDP, but does not provide explicit Linux SSH instructions or examples. The Serial Console documentation link points to a Windows-focused page. Linux-specific connection methods and troubleshooting steps are less detailed or referenced after Windows options.
Recommendations
- Provide explicit Linux SSH connection instructions and examples alongside or before Windows RDP/WinRM examples.
- Link to Linux-specific documentation for Azure Serial Console and Bastion, not just Windows-focused pages.
- Clarify which instructions (such as password reset) apply to Linux VMs, and provide Linux-specific guidance if the process differs.
- Ensure that Linux connection methods (SSH, etc.) are described with equal detail and prominence as Windows methods.
- Avoid using Windows-centric terminology (e.g., RDP, WinRM) without also referencing Linux equivalents (SSH).
Virtual Machines
Azure VM Image Builder service DevOps task (preview)
...es/virtual-machines/linux/image-builder-devops-task.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific tools (PowerShell) and terminology are frequently mentioned, often before or in more detail than their Linux equivalents. Windows examples and instructions (e.g., PowerShell commands, Windows Update task, directory paths) are given first or exclusively in several sections, while Linux instructions are sometimes less detailed or presented as secondary. Some features (like Windows Restart or elevated commands) are noted as unsupported, but workarounds or Linux alternatives are not always explained. The overall structure and examples favor Windows users, creating friction for Linux/macOS users.
Recommendations
- Present Linux and Windows examples side-by-side or alternate which is shown first.
- Expand Linux-specific instructions and examples to match the detail given for Windows (e.g., more bash script samples, troubleshooting steps).
- Include Linux/macOS tool references (e.g., bash, sh) wherever PowerShell is mentioned.
- Clarify Linux-specific limitations and provide workarounds or alternatives.
- Explicitly state Linux/macOS support and parity in feature lists and prerequisites.
- Where features are Windows-only or unsupported, provide equivalent Linux guidance or note the absence.
Virtual Machines
Troubleshoot Azure VM Image Builder
...s/virtual-machines/linux/image-builder-troubleshoot.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation exhibits moderate Windows bias. Windows tools (PowerShell, Sysprep, WinRM, Windows-specific error codes) are frequently mentioned, often with detailed examples and troubleshooting steps. Linux equivalents (waagent, SSH, shell scripts) are referenced but generally with less detail and sometimes only as secondary notes. Some troubleshooting sections and examples (e.g., Sysprep, Windows Update, restart errors) are Windows-centric, with Linux guidance either missing or less emphasized.
Recommendations
- Ensure Linux troubleshooting examples are provided alongside Windows ones, with equal detail (e.g., show waagent errors, Linux restart issues, Linux-specific log analysis).
- Present Linux and Windows commands in parallel, rather than Windows-first (e.g., show Azure CLI and shell examples before PowerShell).
- Expand Linux-specific error scenarios and solutions, such as permissions, SSH connectivity, and customization failures.
- Reference Linux documentation and support resources as prominently as Windows ones.
- Where Windows tools (PowerShell, Sysprep) are explained in detail, provide similar depth for Linux tools (waagent, shell scripting, systemd, etc.).
Virtual Machines
Create and upload an Oracle Linux VHD
...les/virtual-machines/linux/oracle-create-upload-vhd.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page exhibits a Windows bias by exclusively referencing Hyper-V (a Windows virtualization tool) for VHD creation and management, providing links to Windows-specific instructions, and using Hyper-V Manager for VM operations. There are no examples or guidance for equivalent Linux tools (such as KVM, qemu-img, or VirtualBox) for creating or managing VHDs, nor are Linux workflows mentioned for tasks like shutting down the VM or converting disk formats. Windows/Hyper-V tools and patterns are mentioned first and exclusively, which may create friction for Linux users.
Recommendations
- Add instructions and examples for creating and managing VHDs using Linux-native tools (e.g., KVM, qemu-img, VirtualBox).
- Provide Linux command-line equivalents for VM operations such as shutdown, disk conversion, and management.
- Include links to Linux-specific documentation for virtualization and VHD creation.
- Present both Windows and Linux workflows in parallel, or prioritize Linux examples given the target audience (Oracle Linux on Azure).
Virtual Machines
Quickstart: Create a Linux VM cluster in Azure using Terraform
...rtual-machines/linux/quick-cluster-create-terraform.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for verifying results, but Azure PowerShell (a Windows-centric tool) is presented as a primary tab alongside Azure CLI. The PowerShell example is included even though the scenario is focused on Linux VM clusters, and PowerShell is not natively available on most Linux distributions. There are no Linux shell-specific examples (e.g., Bash, SSH, SCP) for interacting with the deployed VMs, nor is there mention of Linux-native tooling for verification.
Recommendations
- Prioritize Azure CLI and Bash examples over PowerShell in the verification steps, as these are more universally available across platforms.
- Add Linux shell (Bash) commands for verifying VM status, such as using SSH to connect to the VMs or using az CLI from a Linux shell.
- If PowerShell is included, clarify its cross-platform availability and provide installation guidance for Linux/macOS users.
- Consider removing or de-emphasizing PowerShell examples in Linux-focused documentation unless there is a clear cross-platform rationale.
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
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
While the documentation is focused on Linux VMs and provides Azure CLI examples for Linux shell scripts, there is a notable bias toward PowerShell and Windows-centric tooling. Many advanced examples and features (such as output streaming, SAS token generation, and parameter passing) are only demonstrated using PowerShell cmdlets, with little or no equivalent Azure CLI or Linux-native command coverage. REST and ARM template examples often use PowerShell script syntax (Write-Host, .ps1), and instructions for generating SAS tokens reference PowerShell tools first. Some sections (e.g., parameter passing, output blob streaming) lack Linux CLI parity, and Windows terminology (e.g., 'myscript.ps1', 'ipconfig') appears before or instead of Linux equivalents.
Recommendations
- Provide Azure CLI examples for all advanced scenarios currently covered only by PowerShell (e.g., output/error blob streaming, parameter passing, long-running scripts).
- Use Linux shell script syntax (e.g., .sh, echo) in REST and ARM template examples, or show both Windows and Linux script examples side by side.
- Reference Linux-native tools for SAS token generation and blob management (e.g., az storage blob generate-sas) before or alongside PowerShell equivalents.
- Ensure command IDs and examples use Linux-relevant commands (e.g., ifconfig, bash scripts) and avoid Windows-first terminology (e.g., ipconfig, .ps1) unless explicitly targeting Windows.
- Clarify differences in parameter passing and script invocation between Linux and Windows, with explicit Linux examples.
Virtual Machines
Run scripts in a Linux VM in Azure using action Run Commands
...ob/main/articles/virtual-machines/linux/run-command.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation is focused on Linux VMs but includes several PowerShell examples and references to Windows-centric tooling (PowerShell cmdlets). PowerShell is not a native Linux tool, and its use may create friction for Linux users. The PowerShell example is presented alongside Azure CLI, but the CLI example is more prominent. There are references to differences between Linux and Windows logs, with Windows-specific log lines described first. The documentation does not provide any Bash or shell script examples for local execution, nor does it mention Linux-native tools for scripting or automation.
Recommendations
- Replace or supplement PowerShell examples with Bash or shell script equivalents, especially for local execution scenarios.
- Ensure Azure CLI examples are presented before PowerShell, as CLI is more common for Linux users.
- Clarify that PowerShell is optional and not required for Linux VM management.
- Provide troubleshooting steps using Linux-native tools and commands.
- When discussing differences between Linux and Windows, describe Linux behavior first.
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 page consistently presents Hyper-V (a Windows technology) as the first and primary example for preparing RHEL VHDs for Azure. References to Windows tools (Hyper-V Manager, convert-vhd cmdlet) are prominent and appear before Linux alternatives. While Linux hypervisors (KVM, VMware, Kickstart) are covered in detail, the initial guidance and prerequisites direct users to Windows-centric workflows, and Windows tools are mentioned without equal Linux alternatives in some places.
Recommendations
- Reorder sections so that Linux-native hypervisors (KVM, VMware, Kickstart) are presented before or alongside Hyper-V, not after.
- In the prerequisites, mention Linux tools (e.g., qemu-img, virt-manager) for VHD creation and conversion before or alongside Windows tools.
- Where Windows-specific tools (Hyper-V Manager, convert-vhd cmdlet) are referenced, provide direct Linux equivalents (e.g., qemu-img commands) in the same context.
- Add explicit guidance for performing all steps on Linux-only environments, including VHD conversion, disk alignment, and VM creation.
- Ensure that references to Windows documentation are balanced with links to Linux documentation or community resources.
Virtual Machines
Run scripts in an Azure Linux VM
...n/articles/virtual-machines/linux/run-scripts-in-vm.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation, while titled and scoped for Linux VMs, repeatedly references Windows-specific tools and scripting languages (PowerShell) alongside Linux options. Several features (Run Command, Hybrid Runbook Worker) highlight PowerShell and Windows usage, sometimes before mentioning Bash or Python. The Hybrid Runbook Worker section links only to Windows installation instructions, omitting Linux setup guidance. No concrete Linux script examples or Linux-specific tool usage are provided.
Recommendations
- Provide explicit Linux script examples (e.g., Bash, Python) for each feature, not just mention Bash generically.
- Ensure Linux installation instructions for Hybrid Runbook Worker are included and linked.
- Reorder lists and descriptions to mention Linux tools and scripting languages first, given the page's Linux focus.
- Add Linux-specific troubleshooting tips and usage patterns for each feature.
- Avoid referencing Windows-only tools (e.g., PowerShell Workflow, Graphical runbooks) unless Linux equivalents are also described.
Virtual Machines
Overview of Azure Disk Storage
...in/articles/virtual-machines/managed-disks-overview.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation page exhibits mild Windows bias in several areas. Windows terminology, tools, and links are often presented first or exclusively, such as references to Sysprep, MBR/GPT partitioning with Windows links, and PowerShell. Some sections (e.g., image creation) link only to Windows-specific guides, and Windows drive letters are mentioned before Linux device paths. Linux equivalents are present in some places but are less prominent or relegated to secondary mentions.
Recommendations
- Ensure all example links (e.g., image creation, disk upload) have both Linux and Windows versions, and present them side-by-side or in a neutral order.
- When discussing partitioning (MBR/GPT), include Linux-specific links (e.g., to parted, gdisk, or relevant Linux documentation) and explain how partitioning works on Linux VMs.
- Mention Linux device paths (e.g., /dev/sda) alongside Windows drive letters when describing disk roles and usage.
- Avoid referencing Windows-specific tools (e.g., Sysprep, PowerShell) without also mentioning Linux equivalents (e.g., waagent, Azure CLI).
- Where cluster managers are discussed, give equal prominence to Linux options (e.g., Pacemaker) as to Windows Server Failover Cluster.
Virtual Machines
Advanced Configuration for MSP
...s/metadata-security-protocol/advanced-configuration.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation provides a Windows-specific example (with a Windows file path and SYSTEM user) before any Linux example, and does not offer equivalent Linux/macOS examples for process identity rules. Windows tools and patterns (e.g., C:\Windows\OEM\Unattend.wsf.exe, SYSTEM user) are mentioned exclusively in the WireServer schema example, while Linux process identity examples are limited to generic paths and group names. No explicit Linux/macOS-specific guidance or parity is provided for configuring RBAC rules based on Linux process metadata.
Recommendations
- Add Linux/macOS-specific examples for process identity rules, such as using /usr/bin/nginx, user 'root', or group 'www-data'.
- Provide parallel examples for both Windows and Linux in all schema expansions, especially for WireServer.
- Explicitly mention how Linux/macOS users can determine process names, executable paths, and user/group names for rule authoring.
- Avoid presenting Windows examples first or exclusively; alternate or combine with Linux/macOS examples.
- Clarify any platform-specific differences in process metadata handling.
Virtual Machines
Specify Marketplace purchase plan information using Azure PowerShell
...b/main/articles/virtual-machines/marketplace-images.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation page is heavily focused on Azure PowerShell, with all CLI examples provided in PowerShell syntax. There are no equivalent examples using Azure CLI (az), Bash, or Linux-native tools, despite the page stating applicability to Linux VMs. Windows-centric tools and patterns (e.g., PowerShell cmdlets, Windows networking conventions) are used exclusively and referenced first. The linked resources also point to Windows/PowerShell documentation. This creates friction for Linux/macOS users who may not have or use PowerShell.
Recommendations
- Add equivalent Azure CLI (az) and Bash examples for all major steps, including retrieving VM plan info, creating image definitions, and deploying VMs.
- Explicitly mention cross-platform alternatives and clarify which steps can be performed on Linux/macOS.
- Update references and links to include both Windows/PowerShell and Linux/CLI documentation.
- Consider reordering examples so that cross-platform (CLI/Bash) instructions appear before or alongside PowerShell examples.
Virtual Machines
Deploy a VM or Virtual Machine Scale Set with MSP
...tual-machines/metadata-security-protocol/greenfield.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page exhibits Windows bias by explicitly describing the Windows provisioning process for GuestProxyAgent (GPA) as simpler and not providing equivalent Linux-specific examples or guidance. The warning highlights a difference in procedure but does not offer step-by-step instructions or ARM template samples for Linux users, nor does it mention Linux tooling or commands. All examples and references are generic or Windows-centric.
Recommendations
- Add explicit Linux provisioning steps, including how to configure GPA after VM/VMSS creation.
- Provide ARM template or REST API examples tailored for Linux VMs, clarifying any differences.
- Include Linux command-line (e.g., Bash, Azure CLI) examples alongside Windows/PowerShell where appropriate.
- Clarify any limitations or required manual steps for Linux users, and link to detailed Linux guidance if available.
Virtual Machines
Frequently Asked Questions About MSP
...les/virtual-machines/metadata-security-protocol/faq.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation displays a Windows bias in its explanation of provisioning and agent installation. It references the 'Windows philosophy' as the default model, discusses GPA installation as a step available in Windows but not Linux, and does not provide Linux-specific examples or guidance for checking MSP status or installing GPA. The lack of Linux command-line examples and the framing of Windows patterns as normative create friction for Linux users.
Recommendations
- Provide explicit Linux command-line examples (e.g., using curl, jq, or bash) for checking MSP status and component health.
- Describe Linux-native workflows for GPA installation and MSP enablement, including any supported VM extension mechanisms.
- Avoid framing Windows patterns as the default or preferred model; present both Windows and Linux approaches equally.
- Clarify any differences in agent management between Windows and Linux, and offer guidance for Linux users to achieve parity.
Virtual Machines
Convert Audit Logs to an Allowlist
...ecurity-protocol/other-examples/audit-logs-to-rules.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
windows_examples_in_schema
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific tools (PowerShell, .exe allowlist generator) and examples (sample identities, schema) are presented first or exclusively, and the PowerShell workflow is far more detailed than the CLI (Linux/macOS-friendly) workflow. The allowlist generator tool is only available as a Windows executable. Sample schemas and identities are Windows-centric, with little parity for Linux processes. Linux instructions are present but less detailed and less emphasized.
Recommendations
- Provide equal depth and step-by-step guidance for Linux/macOS users using Azure CLI and ARM templates.
- Offer a cross-platform version of the allowlist generator tool (e.g., Python, .NET Core, or containerized).
- Include Linux process examples and sample identities in the rules schema.
- List CLI instructions before or alongside PowerShell instructions, not after.
- Explicitly mention macOS compatibility where relevant.
- Ensure screenshots and sample outputs include both Windows and Linux cases.
Virtual Machines
Metadata Security Protocol (MSP)
...irtual-machines/metadata-security-protocol/overview.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation lists Windows operating systems first in compatibility, and provides a warning that Windows users can enable GuestProxyAgent (GPA) from an ARM template, while Linux users must follow a more complex, two-step process. No Linux-specific example or workaround is provided for GPA configuration, and the documentation does not elaborate on Linux tooling or patterns for MSP setup.
Recommendations
- Provide explicit Linux configuration steps for enabling GPA, including example commands and tooling.
- Offer ARM template snippets or automation guidance for Linux users, if possible.
- List supported Linux distributions before or alongside Windows in compatibility sections to avoid Windows-first perception.
- Clarify any differences in process for Linux and Windows, and offer parity where feasible.
Virtual Machines
NV series migration guide
...-machines/migration/sizes/nv-series-migration-guide.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation demonstrates a Windows bias by referencing only Windows guest OS support for NVv4 VMs, linking exclusively to Windows-specific driver installation guides and extensions, and omitting Linux migration steps, driver instructions, or parity notes. Linux users are left without guidance for migration, driver setup, or troubleshooting, especially for NVsv3, which does support Linux.
Recommendations
- Include explicit Linux migration steps and considerations for supported VM series (e.g., NVsv3).
- Provide links to Linux-specific GPU driver installation guides and extension documentation.
- Clarify which VM series support Linux and which are Windows-only, ideally in a summary table.
- Add FAQ entries addressing Linux scenarios, such as driver compatibility and extension support.
- Ensure parity in example commands, instructions, and troubleshooting for both Windows and Linux users.
Virtual Machines
Move resources associated with a maintenance configuration to another region
...nes/move-region-maintenance-configuration-resources.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell commands are presented first and in more detail, with variable examples using PowerShell syntax. The main migration instructions link to a Windows-specific tutorial (toc/breadcrumb paths include 'windows'), and PowerShell is mentioned before CLI throughout. While CLI examples are provided, Linux/macOS users may find the ordering and emphasis on PowerShell and Windows navigation patterns less intuitive.
Recommendations
- Provide Bash variable examples alongside PowerShell examples for variable setup.
- Alternate the order of PowerShell and CLI instructions, or present CLI first to balance platform emphasis.
- Ensure migration instruction links point to platform-neutral or Linux/macOS-specific guides where possible.
- Clarify that CLI commands work on Linux/macOS and provide any OS-specific caveats.
- Add explicit notes or sections for Linux/macOS users, especially in navigation and troubleshooting.
Virtual Machines
SCSI to NVMe for Linux VMs
...docs/blob/main/articles/virtual-machines/nvme-linux.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation, while focused on Linux VMs, relies heavily on PowerShell-based workflows and examples for migration, controller checks, and script execution. Windows-centric tools (PowerShell, Azure CLI in PowerShell syntax) are used for critical steps, and PowerShell instructions are presented before any Linux-native alternatives. There is minimal guidance for performing these tasks using native Linux tools or shell commands, creating friction for Linux/macOS users who may not use PowerShell.
Recommendations
- Provide equivalent Linux shell (bash) commands for all PowerShell examples, especially for checking VM controller types and running migration scripts.
- Offer instructions for using Azure CLI in bash (native Linux syntax), not just PowerShell.
- Include guidance for downloading and running migration scripts directly from a Linux terminal, without requiring PowerShell.
- Clarify whether the migration script can be run in Azure Cloud Shell (bash) or on a local Linux system, and provide steps for both.
- Move Linux-native instructions and examples before PowerShell/Windows-centric ones, or present them side-by-side.
- Explicitly state any prerequisites or limitations for Linux/macOS users regarding the migration process.
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation page exhibits a moderate Windows bias. Windows troubleshooting steps and service names are frequently presented first, and Windows-specific tools (such as 'sc query') are used in examples. Some troubleshooting commands for Windows (e.g., checking service status) are shown, but equivalent Linux commands (e.g., 'systemctl status') are missing or less detailed. In some sections, only Windows service checks are provided, or the Windows example is shown before the Linux one, even when both platforms are supported.
Recommendations
- Provide Linux equivalents for all Windows troubleshooting commands (e.g., show 'systemctl status' for Linux services alongside 'sc query' for Windows).
- Present Windows and Linux instructions in parallel, or alternate which platform is shown first to avoid implicit prioritization.
- Include explicit Linux command examples for checking eBPF and GPA status, such as 'systemctl status azure-proxy-agent', 'lsmod', or 'journalctl'.
- Ensure all troubleshooting steps are equally detailed for both platforms, including log locations, error codes, and service management.
- Where Windows-specific tools or patterns are mentioned, add notes or alternatives for Linux users.
Virtual Machines
Migrate Managed image to Compute gallery
...igration/migration-managed-image-to-compute-gallery.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides migration instructions for both Linux and Windows VMs, but example scripts are given for Azure CLI and PowerShell, with PowerShell (a Windows-centric tool) featured as a dedicated tab. The CLI example uses Azure CLI, which is cross-platform, but the PowerShell example is Windows-focused and presented equally. There are no Linux shell-specific examples (e.g., Bash), nor is there mention of Linux-native scripting or tools. The ordering of examples (CLI, then PowerShell) is neutral, but the presence of PowerShell as a primary method may signal Windows bias.
Recommendations
- Add explicit Bash shell examples for Linux users, showing equivalent steps using Azure CLI in a Linux shell context.
- Clarify that Azure CLI commands are cross-platform and provide any Linux-specific nuances (such as authentication differences).
- Consider adding a note or tab for Linux/macOS users, highlighting any differences or confirming parity.
- If PowerShell is shown, also show Bash or other Linux-native scripting examples for parity.
Virtual Machines
Monitoring data reference for Azure Virtual Machines
...main/articles/virtual-machines/monitor-vm-reference.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. Several log tables and data collection methods are described with explicit references to Windows-specific tools (e.g., Windows Event Log, IIS logs, Windows DNS servers, Windows Security Events, Windows Firewall). These Windows-centric tables and collection methods are listed before or more prominently than their Linux equivalents. While Linux support is present (e.g., Syslog, Linux Daemons), Linux examples and tools are less detailed, and some sections lack parity in Linux-specific instructions or examples. The only explicit example link provided is for Linux (collecting Percentage CPU metric), but most references and log tables are Windows-first or Windows-only.
Recommendations
- Add equivalent Linux examples and instructions wherever Windows tools or logs are mentioned (e.g., provide examples for collecting Linux audit logs, firewall logs, and DNS events).
- Ensure Linux-specific monitoring tables and data collection methods are described with equal detail and prominence.
- Where Windows-only features are listed (e.g., IIS logs, Windows Event Log), clarify Linux alternatives or note limitations.
- Present examples and tables in a way that alternates or balances Windows and Linux content, rather than listing Windows first.
- Include explicit Linux/macOS usage scenarios and troubleshooting tips alongside Windows ones.
Virtual Machines
Tutorial - Move Azure single instance Virtual Machines from regional to zonal availability zones
...achines/move-virtual-machines-regional-zonal-portal.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page primarily describes how to move Azure VMs using the Azure Portal, which is cross-platform. However, in the prerequisites and next steps, it references Windows-specific documentation and PowerShell, with no mention of Linux/macOS equivalents or Azure CLI examples. The link to check VM SKU availability points to a Windows/PowerShell-specific page, and the 'Next steps' section only references PowerShell or CLI, but the main page does not provide any CLI examples or parity guidance for Linux/macOS users.
Recommendations
- Include Azure CLI examples alongside PowerShell for all steps, especially in 'Next steps' and any referenced guides.
- Ensure links to prerequisite tasks (e.g., checking VM SKU availability) point to both Windows/PowerShell and Azure CLI/Linux documentation.
- Explicitly mention that all steps can be performed via CLI on Linux/macOS and provide direct links or inline examples.
- Add a note clarifying platform parity and guiding users to platform-appropriate tools.
Virtual Machines
Network security group test
...ticles/virtual-machines/network-security-group-test.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by exclusively using RDP (Remote Desktop Protocol) as the example for testing inbound connections, which is only relevant to Windows VMs. There are no equivalent Linux examples (such as SSH) provided, and the inbound test walkthrough implicitly prioritizes Windows scenarios. Although both Linux and Windows VM creation links are mentioned in prerequisites, the actual test instructions and screenshots focus solely on Windows use cases.
Recommendations
- Add a parallel example for Linux VMs, such as testing inbound SSH (port 22) connections, with step-by-step instructions and screenshots.
- Explicitly state that the inbound test can be used for other protocols/services (e.g., SSH for Linux, HTTP/HTTPS for web servers) and provide example values.
- Ensure that both Windows and Linux scenarios are covered equally in all sections, including troubleshooting advice.
- Consider alternating the order of examples or providing a combined table for common protocols (RDP, SSH, HTTP, etc.) to avoid Windows-first presentation.
Virtual Machines
Troubleshoot restore point failures
...cles/virtual-machines/restore-point-troubleshooting.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific tools (services.msc, Control Panel, Event Viewer, COM+, VSS, Visual C++ Redistributable) are referenced frequently, often without Linux equivalents or alternatives. Troubleshooting steps and error resolutions for Windows are more detailed and provided first, while Linux instructions are shorter and sometimes lack direct analogs (e.g., for COM+, VSS, Visual C++ Redistributable). Some troubleshooting steps reference PowerShell and Windows portal workflows before mentioning CLI or Linux methods.
Recommendations
- Provide Linux equivalents for all troubleshooting steps involving Windows-only tools (e.g., services.msc, Event Viewer, COM+, VSS).
- Add Linux-specific error codes and troubleshooting guidance where only Windows errors are described.
- Ensure CLI and Linux commands/examples are presented alongside or before Windows/PowerShell instructions.
- Clarify which steps are OS-specific and offer parity in depth and clarity for both platforms.
- Reference Linux package managers and system tools (e.g., systemctl, journalctl, dmesg) where appropriate.
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation generally covers both Windows and Linux VMs, but several sections show Windows bias. Windows tools (PowerShell) are mentioned before Linux equivalents (Azure CLI), and some examples or links are Windows-first. The Antimalware section is Windows-centric, with no Linux alternative discussed. In the Key Vault section, PowerShell is recommended for Windows and CLI for Linux, but the ordering and emphasis favor Windows. Some cross-linking (e.g., SSH from Windows to Linux) is present, but Linux usage patterns are less detailed.
Recommendations
- Provide Linux alternatives or equivalents for Windows-only features (e.g., Antimalware).
- Present examples and tool recommendations for both platforms side-by-side, or alternate which comes first.
- Expand Linux-specific guidance, especially for security tooling and automation.
- Ensure parity in depth and clarity of instructions for Linux and Windows users.
- Explicitly state when features are Windows-only and suggest Linux alternatives if available.
Virtual Machines
Azure premium storage: Design for high performance
...ticles/virtual-machines/premium-storage-performance.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
sql_server_bias
missing_linux_example
Summary
The documentation page demonstrates moderate Windows bias. Windows tools (PerfMon, Storage Spaces, PowerShell) are mentioned before or more prominently than their Linux equivalents (iostat, MDADM). SQL Server (a Windows-centric workload) is used as the primary example throughout, with Linux alternatives or examples rarely provided. Disk striping instructions are more detailed for Windows (including PowerShell and Server Manager UI), while Linux is referenced briefly with a link. Some benchmarking and performance measurement sections mention Windows tools first or in more detail. Linux parity is present in some areas (e.g., iostat, MDADM, Linux benchmarking links), but Windows-centric patterns and examples dominate.
Recommendations
- Provide Linux examples and instructions with equal detail and prominence as Windows, especially for disk striping, benchmarking, and performance measurement.
- Use a mix of application examples (e.g., PostgreSQL, MySQL, Oracle) alongside SQL Server to illustrate scenarios for Linux users.
- List Linux tools (e.g., iostat, vmstat, MDADM) before or alongside Windows tools, not after.
- Expand Linux-specific configuration guidance (e.g., file system tuning, RAID setup) to match the depth given to Windows.
- Add step-by-step Linux command examples where PowerShell or Windows UI steps are shown.
- Balance references to Windows and Linux in tables, diagrams, and summary sections.
Virtual Machines
Set up Azure HPC or AI VMs
.../blob/main/articles/virtual-machines/set-up-hpc-vms.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation generally maintains parity between Windows and Linux, referencing both platforms for VM creation, disk attachment, SSH connection, and GPU driver installation. However, in the GPU driver installation section, only Windows instructions are provided for AMD GPUs, with no Linux equivalent. Additionally, Windows examples (e.g., AMD GPU drivers) are listed before Linux ones, and some links (e.g., SSH from Windows) are referenced after Linux/macOS, but the order is inconsistent.
Recommendations
- Add instructions or links for installing AMD GPU drivers on Linux VMs, if supported.
- Ensure that Linux and Windows examples are presented in parallel or grouped by OS for clarity.
- Review the order of examples and links to avoid subtle prioritization of Windows over Linux/macOS.
- Explicitly state if certain features (e.g., AMD GPU drivers) are not available on Linux, to avoid confusion.
Virtual Machines
Share Gallery Images Across Tenants by Using an App Registration
...icles/virtual-machines/share-using-app-registration.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 sharing gallery images across tenants. However, the PowerShell section is significantly more detailed, including full networking and VM configuration steps, while the CLI section is much shorter and omits these details. The PowerShell examples use Windows-centric tools and patterns (e.g., RDP rules, Windows OS configuration), and the networking setup is only shown for PowerShell. This creates friction for Linux/macOS users who may prefer CLI or need Linux-specific guidance.
Recommendations
- Expand the Azure CLI section to include full VM creation steps, including networking setup, similar to the PowerShell example.
- Provide Linux-specific VM creation examples (e.g., using --os-type Linux, SSH configuration, Linux-friendly networking rules).
- Ensure parity in detail and completeness between CLI and PowerShell sections.
- Avoid Windows-centric configuration in generic examples; offer both Windows and Linux VM creation scenarios.
Virtual Machines
Dlsv6 size series (Preview)
...virtual-machines/sizes/general-purpose/dlsv6-series.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation references Windows-specific technologies (e.g., Hyper-V nested virtualization) and tools (NTTTCP for bandwidth testing) without mentioning Linux equivalents or alternatives. Windows features and resources are sometimes referenced first or exclusively, while Linux-specific guidance is minimal or absent.
Recommendations
- When mentioning nested virtualization, include links or notes about Linux support and relevant technologies (e.g., KVM, nested virtualization on Linux).
- For bandwidth testing, mention Linux tools (e.g., iperf, netperf) alongside NTTTCP, and provide links to their usage in Azure.
- Ensure feature support and optimization notes explicitly address both Windows and Linux, with links to Linux documentation where available.
- Review all resource links and examples to ensure Linux parity, adding Linux-specific documentation where missing.
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is given extensive coverage with multiple detailed scripts, including scenarios for availability sets and local execution. The CLI section is present and cross-platform, but is less detailed than PowerShell. The Terraform example references a Windows VM quickstart, and the code sample is for a Windows VM. There are no explicit Linux-specific examples, and Windows tools/patterns (PowerShell, Windows VM resource blocks) are mentioned first or exclusively in several places.
Recommendations
- Add explicit Linux VM examples in the Terraform section, referencing azurerm_linux_virtual_machine and providing sample code.
- Balance PowerShell and CLI coverage by expanding CLI examples to cover all scenarios shown for PowerShell, including availability sets and local execution.
- Reference Linux quickstart documentation alongside Windows quickstart in the Terraform section.
- Ensure that examples and code samples alternate or equally represent both Windows and Linux VMs.
- Add notes clarifying that Azure CLI commands work identically on Linux, macOS, and Windows, and provide shell script examples where appropriate.
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is presented as the primary scripting example, and the CLI authentication example uses PowerShell syntax rather than Bash. There are no explicit Linux/macOS shell examples (e.g., Bash), and Windows-centric tools (PowerShell, Azure portal) are mentioned before cross-platform alternatives. This may create friction for Linux/macOS users who expect Bash or shell examples and parity in migration instructions.
Recommendations
- Provide Bash shell examples for Azure CLI commands, using standard Bash variable syntax and command chaining.
- Clarify that Azure CLI commands are cross-platform and show both Windows (PowerShell) and Linux/macOS (Bash) usage patterns.
- Include explicit instructions for Linux/macOS users, such as opening a terminal and using Bash, especially in the Azure CLI section.
- Where PowerShell is used, offer equivalent Bash commands for Linux/macOS users.
- Review screenshots and UI instructions to ensure they are not Windows-specific (e.g., referencing Windows-only features or UI elements).
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_first
Summary
The documentation provides detailed instructions for resizing VMs using the Azure portal and Azure PowerShell, but does not include equivalent examples for Azure CLI, which is more commonly used on Linux/macOS. PowerShell is Windows-centric, and its exclusive use in code samples creates friction for Linux/macOS users. The ordering also presents Windows/PowerShell methods before mentioning CLI, and no CLI example is shown.
Recommendations
- Add step-by-step instructions and code samples for resizing VMs using Azure CLI, which works cross-platform.
- Present CLI and PowerShell examples side-by-side or in parallel sections, rather than PowerShell-only.
- Explicitly mention that Azure CLI is available and suitable for Linux/macOS users, and link to relevant CLI documentation.
- Consider including Bash or shell script examples for common tasks.
Virtual Machines
Create an Azure snapshot of a virtual hard disk
...rticles/virtual-machines/snapshot-copy-managed-disk.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell (a Windows-centric tool) is given its own section with detailed examples, and references to Windows-specific VM creation are provided before Linux equivalents. The 'Next steps' section links to Windows instructions first for both Portal and PowerShell, while the CLI section links to Linux instructions. There is no explicit Linux PowerShell example, and the CLI examples, while cross-platform, are not highlighted as the primary method for Linux users.
Recommendations
- Ensure that Linux-specific instructions are provided and linked equally in all tool sections, especially in 'Next steps'.
- Present CLI examples before or alongside PowerShell examples, as CLI is more universally applicable across platforms.
- Add explicit notes or examples for Linux users in the PowerShell section, or clarify PowerShell's cross-platform capabilities.
- Balance references to Windows and Linux VMs throughout, ensuring neither is prioritized in example ordering or linking.
- Where possible, provide bash script examples for Linux users alongside PowerShell for Windows users.
Virtual Machines
Create SSH keys with the Azure CLI
...b/main/articles/virtual-machines/ssh-keys-azure-cli.md
Medium Priority
View Details â
Detected Bias Types
linux_first
missing_windows_example
Summary
The documentation is strongly oriented toward Linux workflows: all command examples use Linux-style paths, Bash commands, and Linux file permission patterns (chmod). There are no PowerShell or Windows Command Prompt examples, nor any mention of Windows-specific SSH key storage locations or usage patterns. While the page claims applicability to both Linux and Windows VMs, it does not provide guidance for Windows users on generating, storing, or using SSH keys with Azure CLI.
Recommendations
- Add equivalent examples for Windows users, including PowerShell and Command Prompt commands.
- Document typical Windows SSH key storage paths (e.g., C:\Users\<username>\.ssh\).
- Explain how to set file permissions for private keys on Windows, or note differences in security practices.
- Clarify any differences in Azure CLI usage or SSH key handling between Linux/macOS and Windows platforms.
- Consider alternating or parallel presentation of Linux and Windows examples to improve parity.
Virtual Machines
Create SSH keys in the Azure portal
...blob/main/articles/virtual-machines/ssh-keys-portal.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates Windows bias primarily in the 'Connect to the VM' section, where only a PowerShell prompt is mentioned for running the SSH command, with no reference to Linux or macOS terminals. Additionally, the example assumes a Windows file path format and does not provide Linux/macOS equivalents. The page also links to a guide for using SSH from Windows when discussing Linux VMs, further reinforcing the Windows-centric approach.
Recommendations
- Include explicit instructions for connecting to the VM from Linux and macOS terminals, such as using the Terminal app and appropriate file paths (e.g., ~/.ssh/mySSHKey.pem).
- Provide example SSH commands for Linux/macOS alongside the PowerShell example.
- Avoid referencing only Windows tools or guides when discussing Linux VM management; link to platform-neutral or Linux/macOS-specific documentation as well.
- Clarify that the SSH command works on all platforms and note any platform-specific considerations (e.g., file permissions on private keys in Linux/macOS).
Virtual Machines
User data for Azure Virtual Machine
...-docs/blob/main/articles/virtual-machines/user-data.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page exhibits a Windows bias by consistently using Windows-centric examples in JSON templates (e.g., 'osType': 'Windows', 'windowsConfiguration', Windows-specific image references), mentioning Windows configuration options, and omitting explicit Linux-focused examples or templates. Linux users are referenced only indirectly, with no direct example of Linux VM creation or configuration. The only Linux-specific guidance is a link to another page for IMDS sample code, but the main documentation lacks parity in examples and patterns.
Recommendations
- Provide explicit Linux VM examples in all JSON templates (e.g., 'osType': 'Linux', Linux image references, and Linux-specific configuration options).
- Include Linux-specific sections or notes alongside Windows ones, such as 'linuxConfiguration' in the VMSS example.
- Ensure that Linux examples are shown with equal prominence and order as Windows examples.
- Add sample user data scripts relevant to Linux (e.g., bash scripts) in addition to or instead of generic base64 strings.
- Clarify any differences in user data handling between Windows and Linux VMs.
Virtual Machines
Upgrade Gen1 VMs to Trusted launch
...s/virtual-machines/trusted-launch-existing-vm-gen-1.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific tools (MBR2GPT.exe, Defrag, BitLocker, PowerShell) are described in detail, with step-by-step instructions and troubleshooting. Linux instructions are present but less detailed, often limited to validation steps or generic statements. Windows examples and tools are frequently presented first or exclusively, while Linux alternatives are less emphasized or missing.
Recommendations
- Provide equally detailed Linux upgrade instructions, including steps for converting MBR to GPT and adding EFI partitions for non-endorsed distros.
- Include Linux-specific troubleshooting sections analogous to the Windows troubleshooting (e.g., handling partition issues, EFI setup failures).
- Present Linux and Windows examples side-by-side or in parallel, rather than Windows-first.
- Reference Linux disk management and partitioning tools (e.g., gdisk, parted) where appropriate.
- Offer guidance for BitLocker equivalents on Linux (e.g., LUKS) if relevant.
- Clarify and expand support for custom Linux images, including manual steps if Azure Marketplace images are not used.
Virtual Machines
Deploy a Trusted Launch VM
...ain/articles/virtual-machines/trusted-launch-portal.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation provides both Linux and Windows guidance for deploying Trusted Launch VMs, but there is a notable Windows bias in several areas. PowerShell examples are extensive and exclusively use Windows images and parameters, while Linux equivalents are either missing or less detailed. In multi-step PowerShell workflows, only Windows VM creation is shown, and Windows-specific tools and patterns (like RDP rules, Bitlocker notes) are referenced without Linux parity. In some sections, Windows examples or terminology appear first or are more prominent.
Recommendations
- Add equivalent PowerShell examples for Linux VM deployment, including Linux-specific parameters and OS disk handling.
- Ensure that multi-step PowerShell workflows (such as network configuration and VM creation from gallery images) include Linux variants.
- Balance the order of examples so that Linux and Windows are presented with equal prominence, or alternate which comes first.
- Where Windows-specific tools or concepts are mentioned (e.g., Bitlocker, RDP), include Linux equivalents (e.g., LUKS, SSH) or clarify applicability.
- Review screenshots and UI instructions to ensure Linux scenarios are visually represented alongside Windows.
- Expand notes and tips to address Linux-specific concerns (e.g., secure boot implications for unsigned drivers, SSH key management).
Virtual Machines
Enable Trusted launch on existing Uniform scale set
...icles/virtual-machines/trusted-launch-existing-vmss.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
powershell_heavy
Summary
The documentation page exhibits several signs of Windows bias. Examples and code snippets consistently use Windows-centric images (e.g., 'MicrosoftWindowsServer'), and the ARM template quickstart links to a Windows-specific template. PowerShell instructions are detailed and prominent, while Linux-specific examples (such as using Ubuntu or other Linux images) are absent from all code samples. The extension publisher table mentions Linux, but no Linux image or command-line examples are provided. The documentation assumes familiarity with Windows tooling and patterns, and Windows is prioritized in examples and references.
Recommendations
- Add explicit Linux examples (e.g., using Ubuntu or Red Hat images) in ARM template, CLI, and PowerShell sections.
- Provide sample code snippets for Linux image references alongside Windows examples.
- Link to both Windows and Linux quickstart ARM templates.
- Clarify any differences or requirements for Linux Trusted launch enablement (e.g., Secure Boot, vTPM support).
- Ensure extension publisher examples show both Windows and Linux usage.
- Balance PowerShell and CLI instructions, and mention cross-platform alternatives where possible.
Virtual Machines
Guest updates and host maintenance overview
...icles/virtual-machines/updates-maintenance-overview.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation generally covers both Windows and Linux VMs, but there are several signs of Windows bias. Windows terminology and features (e.g., Hotpatching for Windows Server Azure Edition) are described in detail, while equivalent Linux features are not mentioned or are less prominent. References to scheduled events and maintenance notifications link to Windows documentation first, and PowerShell is mentioned as a deployment tool before Azure CLI. Some features (like Hotpatch) are Windows-only, and examples or links for Linux are sometimes secondary or missing.
Recommendations
- Ensure that Linux examples and documentation links are presented alongside or before Windows equivalents, especially in sections like scheduled events and maintenance notifications.
- Highlight Linux-specific features or limitations where Windows-only features (e.g., Hotpatch) are discussed, and provide alternative solutions for Linux users.
- When listing deployment tools, mention Azure CLI and Linux-native tools before or alongside PowerShell, and provide example commands for both platforms.
- Add more explicit Linux usage examples and workflows throughout the documentation to ensure parity.
- Clearly indicate when a feature is Windows-only and suggest Linux alternatives or workarounds.
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation exhibits several forms of Windows bias: Windows concepts and links (e.g., Secure Boot, Hyper-V Shielded VM) are introduced first and referenced more frequently than Linux equivalents. Command examples are often provided for both Azure CLI and PowerShell, but PowerShell (a Windows-centric tool) is given equal or greater prominence, and Linux-specific shell examples are less common or absent in some sections. Troubleshooting and validation workflows reference Windows tools and documentation before Linux alternatives. Some sections lack Linux-specific examples or troubleshooting steps, and Windows terminology is used as the default.
Recommendations
- Ensure Linux shell (bash) examples are provided alongside PowerShell for all CLI commands, especially in troubleshooting and validation sections.
- When referencing Secure Boot and other security features, include links to Linux documentation (e.g., UEFI Secure Boot on Linux, Linux kernel documentation) in addition to Windows resources.
- Present Linux and Windows examples in parallel tabs or sections, with equal prominence and ordering.
- Expand troubleshooting steps to include Linux-specific workflows and tools, not just Windows-centric approaches.
- Avoid using Windows terminology as the default; clarify when instructions apply to both platforms or provide platform-specific guidance.
Virtual Machines
Use Premium SSD v2 with VMs in availability set
...l-machines/use-premium-ssd-v2-with-availability-set.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation provides step-by-step instructions for deploying Premium SSD v2 disks with VMs in an availability set using Azure CLI, PowerShell, and the Azure Portal. However, the VM creation examples in both CLI and PowerShell use Windows images (e.g., Win2016Datacenter), and there are no explicit Linux VM examples or references. PowerShell instructions are given equal prominence to CLI, but PowerShell is a Windows-centric tool. There is no mention of Linux-specific considerations, nor are there examples for Linux VM images or SSH credential handling. The documentation implicitly prioritizes Windows by example and tooling, which may create friction for Linux/macOS users.
Recommendations
- Include explicit Linux VM creation examples in both Azure CLI and PowerShell sections (e.g., use UbuntuLTS or CentOS images).
- Add notes or examples for SSH credential setup for Linux VMs.
- Clarify that Azure CLI is cross-platform and provide guidance for Linux/macOS users where relevant.
- Mention Linux-specific considerations (e.g., disk formatting, mounting) if applicable.
- Balance the order and prominence of Windows and Linux examples to avoid implicit prioritization.
Virtual Machines
Deploying disks with Azure Resource Manager templates
...l-machines/using-managed-disks-template-deployments.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page consistently uses Windows-centric examples and references, such as the 'vm-simple-windows' template and Windows image parameters, without providing equivalent Linux-focused examples or parameters. All JSON code samples use Windows images, and the only referenced quickstart template in the walkthrough is for Windows. Linux is only mentioned in the 'Next steps' section as a link, not in the main instructional content.
Recommendations
- Provide parallel Linux VM examples throughout the document, including JSON snippets referencing Linux images and parameters.
- Reference both Windows and Linux quickstart templates when illustrating template changes and comparisons.
- Include explanations of any Linux-specific considerations (e.g., osType, imageReference) in the template sections.
- Alternate or balance the order of Windows and Linux examples to avoid implicit prioritization.
Virtual Machines
Creating Virtual Machine Restore Points using Azure portal
...hines/virtual-machines-create-restore-points-portal.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page focuses exclusively on using the Azure portal for creating and restoring VM restore points, which is cross-platform. However, when referencing further steps for creating a VM from a disk and attaching restored disks, the links provided point only to Windows-specific guides. There are no Linux-specific instructions or examples, and Linux parity is not addressed in these critical steps.
Recommendations
- Include links to equivalent Linux documentation for creating a VM from a disk and attaching managed disks.
- Add notes or examples for Linux users, clarifying any differences in the process.
- Ensure that referenced guides cover both Windows and Linux scenarios, or provide parallel instructions.
- Explicitly mention that the process applies to both Windows and Linux VMs, or highlight any OS-specific considerations.
Virtual Machines
Use virtual machine restore points
...ual-machines/virtual-machines-create-restore-points.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a mild Windows bias. Application consistency is described in detail for Windows (using VSS writers), while Linux is mentioned only as supporting file system consistency and requiring pre- and post-scripts, with no further guidance or examples. Windows terminology (VSS) is introduced first and explained, whereas Linux alternatives are referenced generically. No Linux-specific examples, tools, or scripts are provided, and troubleshooting guidance is not differentiated by OS.
Recommendations
- Provide explicit Linux examples for application-consistent restore points, including sample pre- and post-scripts.
- List common Linux tools or patterns (e.g., fsfreeze, custom shell scripts) for achieving application consistency.
- Balance the explanation order: describe Linux and Windows approaches equally, rather than focusing on Windows first.
- Add troubleshooting steps specific to Linux VM agent and extension issues.
- Clarify any differences in restore point behavior or limitations between Windows and Linux VMs.
Virtual Machines
Overview of VM Applications in the Azure Compute Gallery
...blob/main/articles/virtual-machines/vm-applications.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation demonstrates a moderate Windows bias. Windows tools (PowerShell, cmd.exe, msiexec) are mentioned frequently and sometimes before Linux equivalents. Troubleshooting and extension status examples are given only in PowerShell, with no Linux CLI or Bash alternatives. File renaming and installer examples for Windows are more detailed and precede Linux sections. Some Linux troubleshooting and operational examples are missing or less emphasized.
Recommendations
- Provide equivalent Linux CLI (az CLI, Bash) commands for troubleshooting and extension status checks, alongside PowerShell examples.
- Ensure Linux examples (e.g., install/remove scripts, file renaming) are presented with equal detail and prominence as Windows examples.
- When discussing command interpreters, mention Bash and Linux scripting patterns before or alongside Windows tools.
- Add Linux/macOS-specific troubleshooting steps and operational guidance where only Windows/PowerShell is currently shown.
- Balance the order of presentation so Linux and Windows are treated equally (e.g., alternate which OS is described first in sections).
Virtual Machines
Create and deploy VM Application on Azure
...in/articles/virtual-machines/vm-applications-how-to.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation exhibits a moderate Windows bias. Many code samples and automation pipeline templates (GitHub Actions, Azure DevOps, Jenkins, GitLab) default to Windows-centric filenames (e.g., app.exe, app-config.json) and explicitly set --os-type Windows when creating VM Application definitions, even though Linux is supported. PowerShell examples are abundant and sometimes more detailed than their Bash/Linux equivalents. Windows tools (msiexec, powershell.exe, .exe installers) are featured prominently, often before or instead of Linux alternatives. While Linux/Bash examples are present for packaging and install scripts, the automation and CI/CD sections lack parity for Linux-first scenarios and do not provide clear guidance for deploying Linux applications in pipelines.
Recommendations
- In all pipeline and automation examples (GitHub Actions, Azure DevOps, Jenkins, GitLab), provide parallel Linux-focused samples (e.g., using app.sh, app.deb, app.rpm, app-config.yaml, and --os-type Linux).
- When showing code for creating VM Application definitions, alternate or equally present --os-type Linux and --os-type Windows, or clarify that both are supported.
- In install script tabs, ensure Linux formats (.sh, .deb, .rpm, .tar.gz) are shown first or equally with Windows formats (.exe, .msi, .ps1).
- Avoid defaulting to Windows filenames (app.exe, app-config.json) in generic templates; use neutral or alternate with Linux equivalents.
- Add explicit guidance for Linux/macOS users in CI/CD pipeline sections, including how to package, upload, and deploy Linux applications.
- Balance PowerShell and Bash examples in all sections, ensuring Linux users have clear, complete instructions.
Virtual Machines
Create a VM from a generalized image in a gallery
...icles/virtual-machines/vm-generalized-image-version.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 most scenarios, but the PowerShell sections are significantly more detailed, with full resource creation flows and advanced configuration. The PowerShell examples are inherently Windows-centric, and the VM creation steps in PowerShell default to Windows VMs (using Set-AzVMOperatingSystem -Windows), with no equivalent Linux PowerShell example. Network security rules in PowerShell focus on RDP (port 3389), which is Windows-specific, and the password requirements link points to a Windows FAQ. In REST examples, both Linux and Windows VM creation are shown, but the PowerShell bias remains strong throughout. The CLI examples do show Linux VM creation with SSH keys, but the PowerShell sections are more comprehensive and default to Windows patterns.
Recommendations
- Add PowerShell examples for Linux VM creation, including Set-AzVMOperatingSystem -Linux and SSH key authentication.
- Balance the detail level between CLI and PowerShell sections, ensuring Linux scenarios are equally covered in PowerShell.
- When showing network security rules, include examples for SSH (port 22) alongside RDP (port 3389) in PowerShell.
- Reference Linux password/SSH requirements, not just Windows password complexity.
- Where possible, avoid defaulting to Windows-centric resource names, patterns, or tools in examples.
Virtual Machines
Create a VM from a specialized image version
...icles/virtual-machines/vm-specialized-image-version.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 creating VMs from specialized images. However, the PowerShell examples are extensive, using Windows-centric cmdlets and patterns, while the CLI examples are much shorter and less detailed. The PowerShell sections include full networking setup and resource creation, whereas the CLI sections only show basic VM creation. The PowerShell examples use Windows-specific tools and terminology, and are presented alongside CLI, but with much more detail. There is a subtle Windows bias in the depth and completeness of examples, and in the use of PowerShell as the primary scripting language for advanced scenarios.
Recommendations
- Expand Azure CLI examples to include full networking setup and resource creation, matching the detail of PowerShell examples.
- Add Bash shell scripting examples for Linux users, especially for multi-step workflows.
- Clarify that PowerShell examples are cross-platform (if true), or provide equivalent Bash/Cloud Shell scripts.
- Avoid using Windows-specific terminology (e.g., RDP rules) without also mentioning Linux equivalents (e.g., SSH).
- Ensure that advanced scenarios (e.g., RBAC, cross-tenant, networking) have parity between CLI and PowerShell, and are not PowerShell-only.
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring VM vCore customization, but the PowerShell example is more detailed and uses SDK objects directly. The CLI example uses Ubuntu as the image, but there are no Linux-specific configuration or verification steps shown. Windows/PowerShell tooling is given equal or greater prominence, and there are no bash or Linux-native command examples for post-deployment verification. The ARM template section is neutral, but overall, Windows/PowerShell patterns are slightly favored.
Recommendations
- Add Linux-specific verification steps (e.g., how to check vCPU count and SMT status in Linux using lscpu or /proc/cpuinfo).
- Provide bash or shell script examples for VM creation and configuration, not just Azure CLI.
- Ensure parity in detail between PowerShell and CLI examples (e.g., show how to use CLI to set advanced properties, not just basic flags).
- Explicitly mention how Linux users can perform equivalent post-deployment checks and troubleshooting.
- Consider listing CLI (cross-platform) examples before PowerShell (Windows-centric) examples.
Virtual Machines
VM watch Collectors Suite
.../articles/virtual-machines/vm-watch-collector-suite.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page for VM watch Collectors Suite demonstrates a moderate Windows bias. Several collectors (e.g., system_error, hardware_health_monitor) are described as Windows-only, with explicit references to Windows EventLog and tools like w32tm. The default NTP server is time.windows.com, and fallback logic is described only for Windows. Linux equivalents (such as syslog, journalctl, or chrony/ntpd for time sync) are not mentioned, and some collectors are eligible only on Windows machines. In collector descriptions, Windows tools and patterns are referenced before Linux, and Linux-specific details are sparse or missing.
Recommendations
- Add Linux/macOS equivalents for collectors that currently reference Windows-only tools (e.g., mention syslog/journalctl for system errors, chrony/ntpd for clock skew).
- Provide explicit eligibility and behavior descriptions for Linux/macOS where currently only Windows is described.
- Include Linux/macOS examples and tool references alongside or before Windows examples where applicable.
- Clarify which collectors are cross-platform and which are platform-specific, and provide guidance or alternatives for Linux/macOS users.
- Consider using neutral or cross-platform defaults (e.g., pool.ntp.org for NTP) instead of Windows-centric ones.
Virtual Machines
Set up Oracle ASM on an Azure Linux virtual machine | Microsoft Docs
...tual-machines/workloads/oracle/configure-oracle-asm.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation is generally Linux-focused, as the main Oracle ASM setup is on a Linux VM. However, there is notable Windows bias in the setup of the X Server VM, which is exclusively described as a Windows 10 workstation using Xming, with no mention of Linux or macOS alternatives. The instructions for tunneling and file transfer use PowerShell and Windows-centric patterns first, and do not provide equivalent Linux/macOS shell examples. The documentation assumes the user's workstation is Windows for critical steps, which may create friction for Linux/macOS users.
Recommendations
- Provide instructions for setting up X Server on Linux (e.g., using Xorg or X11) and macOS (e.g., XQuartz), including installation and launch steps.
- Include Linux/macOS shell equivalents for all PowerShell commands, especially for Azure Bastion tunneling and SCP file transfer.
- Mention cross-platform SSH and SCP usage, and clarify how Linux/macOS users can perform all steps without a Windows VM.
- List X Server options for all major platforms and provide links to their documentation.
- Reorder examples so that Linux/macOS options are presented alongside or before Windows-specific instructions, where appropriate.
Virtual Machines
Connect Azure ExpressRoute with Oracle Cloud Infrastructure | Microsoft Docs
...nes/workloads/oracle/configure-azure-oci-networking.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. While the topic is cross-cloud and the audience includes Linux users (as indicated by the 'Applies to: Linux VMs' tag), most step-by-step instructions focus on Azure Portal GUI actions and PowerShell commands, with no equivalent CLI or Linux-native examples. References to automation mention Terraform and Azure CLI, but when describing manual configuration, only PowerShell is cited for advanced tasks (e.g., configuring ExpressRoute FastPath). There are no explicit Linux shell or Azure CLI command examples, and the order of presentation favors Windows-centric tools and workflows.
Recommendations
- Add Azure CLI command examples alongside PowerShell for all configuration steps, especially for ExpressRoute FastPath and virtual network gateway setup.
- Explicitly mention and provide Linux shell (bash) equivalents for verification steps, such as querying ARP records and route tables.
- Ensure that automation and scripting sections include instructions for authenticating and running Terraform from Linux environments.
- Where screenshots or UI instructions are given, clarify that these steps are platform-agnostic or provide CLI alternatives for headless/Linux users.
Virtual Machines
Implement Oracle Golden Gate on an Azure Linux VM | Microsoft Docs
...hines/workloads/oracle/configure-oracle-golden-gate.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
Although the documentation is for deploying Oracle Golden Gate on Azure Linux VMs, there is notable Windows bias in the setup of the X Server component. The guide mandates the creation of a Windows VM (ggXServer) specifically to run Xming X Server for graphical installation, with detailed Windows instructions and screenshots. No equivalent Linux or macOS X Server setup is described. Additionally, PowerShell commands are used for Bastion tunneling and file transfer, with no Bash or Linux-native alternatives provided. The documentation assumes the user's local environment is Windows for critical steps, creating friction for Linux/macOS users.
Recommendations
- Provide instructions for setting up an X Server on Linux (e.g., using Xorg, X11 forwarding via SSH, or XQuartz on macOS) as an alternative to the Windows Xming VM.
- Include Bash-based examples for Bastion tunneling and SCP file transfer, not just PowerShell.
- Add guidance for performing graphical Oracle installer steps from a Linux or macOS desktop, or document how to use SSH X11 forwarding from those platforms.
- Present cross-platform options for all steps that currently assume Windows, and avoid Windows-first ordering in critical sections.
- Where screenshots are used, provide Linux/macOS equivalents or clarify platform differences.
Virtual Machines
Red Hat Enterprise Linux bring-your-own-subscription Azure images | Microsoft Docs
...ain/articles/virtual-machines/workloads/redhat/byos.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation provides both Azure CLI (cross-platform) and PowerShell examples for provisioning Red Hat Enterprise Linux BYOS images on Azure. However, the PowerShell section is notably more detailed, including full scripts for networking and VM setup, while the CLI section is more basic. Windows-specific tools (PowerShell, Az PowerShell modules) are featured, and the PowerShell example appears after the CLI but is more comprehensive, potentially implying a Windows-centric workflow. There are no Linux/macOS-specific automation examples (e.g., Bash scripts, cloud-init, Terraform, Ansible), and the CLI instructions do not cover advanced scenarios shown in PowerShell.
Recommendations
- Expand the Azure CLI section to include full end-to-end deployment scripts, matching the detail of the PowerShell example (networking, SSH keys, etc.).
- Add Linux/macOS-specific automation examples, such as Bash scripts, cloud-init, or Ansible playbooks for VM provisioning.
- Include guidance for using cross-platform tools (e.g., Terraform, Ansible) with explicit Linux/macOS usage instructions.
- Clarify that PowerShell is primarily a Windows tool and offer alternatives for Linux/macOS users.
- Ensure parity in example depth and complexity between CLI and PowerShell sections.
Container Instances
Update or delete a standby pool for Azure Container Instances
...nces/container-instances-standby-pool-update-delete.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation provides both Azure CLI and PowerShell examples for updating and deleting standby pools, but PowerShell (a Windows-centric tool) is given equal prominence and detailed usage. The ARM template section mentions deployment via both az CLI and New-AzResourceGroupDeployment (PowerShell), but does not clarify Linux/macOS deployment patterns. There is no explicit Linux/macOS bias, but the presence and parity of PowerShell examples, and references to Windows tools, may create friction for non-Windows users.
Recommendations
- Clarify that Azure CLI commands work cross-platform (Windows, Linux, macOS) and recommend CLI for Linux/macOS users.
- Add explicit notes or examples for Linux/macOS users, such as shell syntax (bash/zsh) for CLI commands.
- Deprioritize PowerShell examples or move them after CLI examples, as CLI is more universal.
- For ARM template deployment, provide Linux/macOS deployment commands (e.g., az deployment group create) before PowerShell equivalents.
- Consider adding a section on platform compatibility for each tool.
Service Fabric
Configure a Service Fabric managed cluster to use a NAT gateway
...s/service-fabric/how-to-managed-cluster-nat-gateway.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides example commands for ARM templates, Azure CLI, Azure PowerShell, and Azure portal. While Azure CLI is cross-platform, Azure PowerShell is Windows-centric and its example is more detailed and multi-step than the CLI example. The PowerShell example is given equal prominence to the CLI, and both are listed before the Azure portal steps. There are no Linux-specific shell examples (e.g., Bash scripts), nor is there explicit mention of Linux/macOS compatibility for the CLI commands. The documentation does not reference Windows-only tools, but the inclusion and detail of PowerShell may signal a slight Windows bias.
Recommendations
- Clarify that Azure CLI commands work on Linux/macOS as well as Windows.
- Add Bash shell script examples for Linux users, especially for multi-step operations.
- Note any platform-specific differences or requirements for Azure CLI and PowerShell.
- Consider listing CLI examples before PowerShell to reflect cross-platform parity.
- Explicitly mention that Azure PowerShell is available on Linux/macOS (if true), or provide alternatives if not.
Service Fabric
Describing Azure Service Fabric apps and services
...ic/service-fabric-application-and-service-manifests.md
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page exhibits mild Windows bias by referencing Windows-specific tools and paths (Visual Studio, C:\Program Files\...), and suggesting the use of Visual Studio for schema validation. There is no mention of Linux/macOS equivalents or cross-platform alternatives for authoring or validating manifest files. Additionally, the only tooling example given is for Windows, and Windows file paths are used exclusively.
Recommendations
- Include instructions for validating XML schema on Linux/macOS, such as using xmllint, VS Code, or other cross-platform editors.
- Mention cross-platform locations for Service Fabric SDK files, or provide guidance for locating schema files on non-Windows systems.
- Provide examples or references for editing manifests using editors available on Linux/macOS.
- Avoid using Windows paths exclusively; use environment variables or generic paths where possible.
Service Fabric
Service Fabric Azure Resource Manager deployment guardrails
...ic/service-fabric-azure-resource-manager-guardrails.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation page exhibits a minor Windows bias by listing the Windows Server cluster creation link before the Linux equivalent in the 'Next steps' section. The main technical content is platform-neutral, focusing on Azure Resource Manager templates and Service Fabric concepts without OS-specific commands or tooling.
Recommendations
- List Linux and Windows cluster creation links in parallel or alphabetically to avoid implicit prioritization.
- Explicitly state that the guidance applies equally to both Windows and Linux clusters where relevant.
- If examples or troubleshooting steps are added in future, ensure parity by providing both Windows and Linux versions.
Service Fabric
Overview of Azure Service Fabric
...ain/articles/service-fabric/service-fabric-overview.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page demonstrates a mild Windows bias. Windows development tools (Visual Studio, PowerShell, .NET SDK) are mentioned before Linux equivalents, and the quickstart link points to a .NET (Windows-centric) guide. Linux tooling (Eclipse, Yeoman, Java SDK) is referenced, but less prominently and after Windows tools. No explicit Linux/macOS examples or walkthroughs are provided, and there is no direct parity in example depth or visibility.
Recommendations
- Provide Linux/macOS quickstart links alongside the Windows/.NET quickstart.
- Present Linux and Windows development environments with equal prominence and detail.
- Include example workflows for both PowerShell (Windows) and Bash/CLI (Linux/macOS) where relevant.
- List Linux tools and patterns before or alongside Windows tools to avoid ordering bias.
- Ensure all referenced guides (e.g., quickstart) have Linux/macOS equivalents easily discoverable.
Service Fabric
Create a Linux container app on Service Fabric in Azure
...e-fabric/service-fabric-quickstart-containers-linux.md
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_example_in_cleanup
Summary
The documentation is strongly Linux-focused throughout, with all main instructions and examples using Linux commands, tools, and patterns. However, in the 'Clean up resources' section, Windows-specific instructions (Certificates MMC snap-in) are mentioned first when describing how to remove certificates, with Mac and Ubuntu following. The mention of PowerShell is only in passing as an alternative management tool, and no PowerShell examples are provided.
Recommendations
- When listing platform-specific instructions (such as removing certificates), present Linux/macOS instructions first or in parallel with Windows, to reinforce the Linux focus.
- Consider grouping platform-specific cleanup instructions under clear subheadings (Windows, Mac, Ubuntu) for parity.
- If mentioning PowerShell as a management tool, also mention Linux equivalents (bash scripts, CLI) with equal prominence.
- Ensure that any platform-specific tooling is described with parity, and avoid listing Windows tools before Linux/macOS tools in Linux-focused documentation.
Azure Impact Reporting
Azure Impact Reporting: Create an Azure Monitor Alert Connector
...ure-impact-reporting/create-azure-monitor-connector.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides both Bash and PowerShell script examples for connector creation, but PowerShell examples are listed first and in more detail. There is a slight preference for Windows/PowerShell tools, and troubleshooting does not mention Linux-specific issues or considerations. The documentation does not discuss Linux/macOS-specific prerequisites or potential platform differences, which may leave Linux users with unanswered questions.
Recommendations
- Alternate the order of Bash and PowerShell examples, or present Bash examples first to balance representation.
- Explicitly mention Linux/macOS compatibility and any platform-specific requirements or caveats.
- Add troubleshooting steps relevant to Bash/Linux environments (e.g., permissions, shell compatibility).
- Clarify that both Bash and PowerShell scripts are equally supported and provide links to platform-specific guidance if available.
Azure Impact Reporting
Azure Impact Reporting Connectors for Azure Monitor: FAQ
...main/articles/azure-impact-reporting/connectors-faq.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for enabling debug mode and verifying connector creation, but PowerShell examples are consistently listed second. There is a slight bias toward Windows by explicitly mentioning PowerShell and not providing Linux/macOS-specific troubleshooting steps or tool alternatives. However, Bash examples are present, and the Azure portal instructions are platform-neutral.
Recommendations
- Alternate the order of Bash and PowerShell examples to avoid implicit prioritization.
- Explicitly mention that Bash examples apply to Linux/macOS and PowerShell to Windows, clarifying cross-platform applicability.
- Add troubleshooting notes or links for Linux/macOS users if there are known platform-specific issues.
- Consider including CLI examples for other shells (e.g., zsh) or specifying that Bash instructions are valid for most Unix-like systems.
Container Instances
Configure custom DNS settings for container group in Azure Container Instances
.../container-instances/container-instances-custom-dns.md
Low Priority
View Details â
Detected Bias Types
windows_tools
powershell_heavy
Summary
The documentation page is generally Linux/Bash-centric, with all CLI examples formatted for Bash and explicit notes about Linux container support. However, there is a notable Windows bias in the choice of container image: the YAML example uses the 'mcr.microsoft.com/powershell:latest' image, which is a Microsoft-maintained PowerShell image. This may suggest a Windows-centric workflow, even though the container is deployed with 'osType: Linux'. There are no PowerShell or Windows command prompt examples, but the use of PowerShell as the container workload could be confusing or less relevant for Linux-focused users.
Recommendations
- Provide alternative YAML examples using more common Linux images (e.g., Ubuntu, Alpine, nginx) to demonstrate DNS configuration in a typical Linux container.
- Clarify that the PowerShell image is cross-platform and runs on Linux, or explicitly mention its suitability for Linux containers.
- Add a note or example for users who may want to use a native Linux shell (e.g., bash, sh) as the container entrypoint.
- Ensure that the documentation does not imply that PowerShell is required for Linux container scenarios.
Container Instances
Encrypt deployment data
...ontainer-instances/container-instances-encrypt-data.md
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
powershell_heavy
Summary
The documentation page demonstrates mild Windows bias. While most command-line examples use Azure CLI (which is cross-platform), instructions for creating and managing Azure Key Vault resources explicitly mention Azure PowerShell and Azure Portal before Azure CLI, and some critical configuration steps (like enabling Soft Delete and Do Not Purge) are described as being performed via PowerShell or CLI, with PowerShell mentioned first. There are no Linux-specific examples, nor is Bash scripting shown, and screenshots and UI instructions are based on the Azure Portal, which is platform-agnostic but often associated with Windows workflows. No steps are strictly Windows-only, but the ordering and tool references may subtly favor Windows users.
Recommendations
- List Azure CLI before Azure PowerShell when describing resource creation and configuration steps, as CLI is more universally available across platforms.
- Provide explicit Bash/Linux shell examples for variable assignment and scripting, especially where CLI commands are shown.
- Clarify that all CLI and PowerShell commands work on Linux, macOS, and Windows, and link to platform-specific setup guides.
- Add notes or examples for Linux/macOS users where file upload or editing is mentioned (e.g., using SCP, SFTP, or VS Code Remote for Cloud Shell).
- Avoid mentioning PowerShell first unless there is a technical reason; strive for parity in tool recommendations.
Container Instances
Execute commands in running container instance
...ticles/container-instances/container-instances-exec.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation provides both Linux (Bash) and Windows (Command Prompt) examples for executing commands in running Azure container instances. However, the Windows example is given equal prominence and detail, including a full output listing, and Windows-specific terminology (cmd.exe, Command Prompt) is used. There is no mention of PowerShell, but the documentation does reference Windows tools and patterns. The examples are balanced, but Windows terminology and examples are presented with similar emphasis as Linux, rather than Linux-first, which is more typical for container documentation.
Recommendations
- Present Linux examples first, as containers are most commonly Linux-based.
- Add explicit macOS notes if there are platform-specific behaviors.
- Clarify that az container exec works identically across platforms, and highlight any differences.
- Provide more Linux troubleshooting examples or shell usage tips.
- Reduce Windows-specific terminology unless necessary for the task.
Container Instances
Set environment variables in container instance
...instances/container-instances-environment-variables.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for setting environment variables in Azure Container Instances, but it demonstrates a mild Windows bias. PowerShell (a Windows-centric tool) is given a dedicated section, and the CLI examples include explicit instructions for Windows Command Prompt users before Linux/Bash users. There is no explicit Linux shell example for PowerShell, nor are macOS-specific considerations mentioned. The YAML section does use Linux containers and Bash, but overall, Windows tools and patterns are presented first or exclusively in some cases.
Recommendations
- Provide Linux/macOS-specific instructions and examples where relevant, especially for shell quoting and environment variable syntax.
- Reorder examples so that cross-platform tools (Azure CLI, YAML) are presented before Windows-specific tools (PowerShell).
- Add explicit notes or examples for macOS users, especially regarding shell differences.
- Clarify that PowerShell Core is available on Linux/macOS, and provide corresponding examples if relevant.
- Ensure that all instructions referencing shell syntax (quotes, environment variable expansion) include both Windows and Linux/macOS variants.
Container Instances
Azure Resource Manager template samples
.../container-instances/container-instances-samples-rm.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation page displays minor Windows bias. In the sample templates table, the only application-specific Windows container example (MS NAV with SQL Server and IIS) is highlighted, while Linux examples are mostly generic. In the deployment section, Azure PowerShell is listed as a primary deployment option alongside Azure CLI, but no explicit Linux/macOS-specific tools or instructions are provided. Windows tools (PowerShell, IIS, SQL Server) are mentioned, but Linux equivalents are not. However, Linux container samples are present and Azure CLI is cross-platform.
Recommendations
- Add Linux/macOS-specific deployment instructions or examples, such as Bash scripts or references to Linux-native tools.
- Balance application samples by including a Linux-specific application example (e.g., LAMP stack) to match the Windows MS NAV sample.
- Clarify that Azure CLI is cross-platform and highlight its use for Linux/macOS users.
- List deployment options in a neutral order (e.g., CLI first, then PowerShell) or group by platform.
Container Instances
Get standby pool for Azure Container Instances details
...tances/container-instances-standby-pool-get-details.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides examples for Azure CLI, PowerShell, and REST API. However, PowerShell is highlighted as a primary method alongside CLI, which can be seen as Windows-centric since PowerShell is most commonly used on Windows. There is no mention of Linux/macOS shell alternatives (e.g., Bash scripts), and PowerShell is presented before REST, reinforcing a Windows-first approach. All examples are generic, but the inclusion and emphasis on PowerShell may create friction for Linux/macOS users who do not use PowerShell.
Recommendations
- Add Bash shell examples for Linux/macOS users, especially for common tasks shown in PowerShell.
- Clarify that Azure CLI works cross-platform and is recommended for Linux/macOS.
- Consider reordering tabs to show CLI first, then Bash, then PowerShell, then REST.
- Explicitly mention platform compatibility for each example.
Container Instances
Understand the health state of your standby pool for Azure Container Instances
...ances/container-instances-standby-pool-health-state.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for retrieving the health state of a standby pool, but the PowerShell example is given equal prominence to the CLI example, despite PowerShell being primarily a Windows tool. There is no mention of Linux/macOS-specific shell usage (e.g., Bash), nor are there any Linux/macOS-specific troubleshooting or usage notes. The CLI example is cross-platform, but the documentation does not clarify this, and the PowerShell example may suggest a Windows-centric workflow.
Recommendations
- Explicitly state that Azure CLI commands work on Linux/macOS as well as Windows.
- Add Bash or shell script examples for Linux/macOS users, especially for parsing or processing output.
- Clarify that PowerShell is available cross-platform, but note its prevalence on Windows.
- Include troubleshooting or usage notes relevant to Linux/macOS environments (e.g., authentication, environment setup).
- Consider listing CLI examples first, as they are more universally applicable.
Container Instances
Get prediction results for standby pools for Azure Container Instances (Preview)
...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/container-instances/container-instances-standby-pool-prediction-results.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for retrieving prediction results, but PowerShell (a Windows-centric tool) is given its own dedicated example section, and is listed immediately after CLI. There are no Linux/macOS-specific shell examples (e.g., Bash, curl), nor are there explicit instructions for Linux users. The CLI example is cross-platform, but PowerShell's prominence and lack of Linux-specific guidance indicate a mild Windows bias.
Recommendations
- Add explicit Bash/curl examples for REST API calls to demonstrate Linux/macOS usage.
- Clarify that Azure CLI works on Linux/macOS and provide installation/use links for those platforms.
- Consider listing CLI examples before PowerShell, or grouping them together as 'cross-platform' and 'Windows-specific' sections.
- Mention that PowerShell Core is available on Linux/macOS if relevant, or clarify platform support.
Container Instances
Request a container from a Standby pool for Azure Container Instances
...https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/container-instances/container-instances-standby-pool-request-container.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for requesting a container from a standby pool, but PowerShell (a Windows-centric tool) is given equal prominence as CLI, and is presented before ARM template and REST examples. There are no Linux-specific shell examples (e.g., Bash), nor is there mention of Linux/macOS tooling or usage patterns. The CLI example is cross-platform, but the presence and prominence of PowerShell may create friction for Linux/macOS users.
Recommendations
- Clarify that Azure CLI commands work on Linux/macOS and Windows, and consider providing explicit Bash examples or notes for Linux/macOS users.
- De-emphasize PowerShell as a primary method, or move it after CLI and ARM/REST examples.
- Add a note that PowerShell is primarily for Windows, and suggest alternatives for Linux/macOS users.
- Where possible, provide Linux/macOS shell usage patterns (e.g., Bash scripts) alongside PowerShell.
Container Instances
Override entrypoint in container instance
...ntainer-instances/container-instances-start-command.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation provides both Linux and Windows shell examples, but Windows-specific tools (PowerShell cmdlet) are mentioned explicitly and given equal prominence to cross-platform tools (Azure CLI). The PowerShell example is listed before the Azure portal and template methods, and the documentation references Windows shell ('cmd') alongside Linux shells. However, the main worked example uses Azure CLI, which is cross-platform, and all command-line examples use Linux syntax. There is no critical omission of Linux/macOS instructions, but Windows tools are given notable visibility.
Recommendations
- Add explicit Linux/macOS command-line examples where PowerShell is mentioned, such as Bash scripts or shell commands.
- Reorder examples to show cross-platform (CLI, portal, template) methods before Windows-specific tools.
- Clarify that Azure CLI is available on Windows, Linux, and macOS.
- Where PowerShell is referenced, add a note or link to equivalent Bash usage for Linux/macOS users.
- Consider adding a section on using Bash or other Linux-native scripting for container management.
Container Instances
Troubleshoot common issues
...ainer-instances/container-instances-troubleshooting.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation provides both Linux and Windows examples for container deployment and troubleshooting, but Windows-specific considerations and tools (such as PowerShell, Windows image support, and Windows networking delays) are often mentioned before or in greater detail than their Linux equivalents. Some instructions explicitly mention Bash as the default shell, with only a brief note that PowerShell/Command Prompt require adjustment, but do not provide direct Linux/macOS alternatives for all steps. Windows-specific troubleshooting (e.g., network readiness delays, image support) is given dedicated sections, while Linux issues are covered more generally.
Recommendations
- Ensure Linux/macOS examples are presented with equal prominence and detail as Windows examples.
- Provide explicit command-line examples for both Bash (Linux/macOS) and PowerShell/Command Prompt (Windows) where variable assignment or shell-specific syntax is required.
- Balance troubleshooting sections so that Linux-specific issues (such as common exit codes, networking quirks, or image compatibility) are covered with similar depth as Windows sections.
- Where Windows tools or patterns are mentioned (e.g., ping -t for keeping containers alive), offer direct Linux equivalents (e.g., tail -f /dev/null) and explain their usage.
- Add a summary table or section that clearly distinguishes platform-specific behaviors and recommendations.
Service Fabric
Configure and use applications with managed identity on a Service Fabric managed cluster
...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/how-to-managed-cluster-application-managed-identity.md
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates a mild Windows bias, primarily through its reference to PowerShell in the link for managing user-assigned managed identities and the absence of Linux/macOS-specific command-line examples. The only external tool mentioned is PowerShell, with no mention of Azure CLI or Bash alternatives. No explicit OS-specific instructions are provided, but the documentation assumes familiarity with Windows-centric tooling and patterns.
Recommendations
- Include Azure CLI and Bash examples alongside or before PowerShell references, especially for identity management tasks.
- When linking to external resources, provide both PowerShell and Azure CLI/Bash documentation links.
- Explicitly state that the ARM template and manifest editing steps are OS-agnostic, and clarify any platform-specific requirements.
- Add a note or section for Linux/macOS users, highlighting any differences or confirming parity.
Service Fabric
Use a Public IP address prefix in a Service Fabric managed cluster
...vice-fabric/how-to-managed-cluster-public-ip-prefix.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying a public IP address prefix in a Service Fabric managed cluster. However, PowerShell (a Windows-centric tool) is given its own dedicated section and example, while Linux/macOS equivalents (such as Bash scripting or explicit Linux CLI usage) are not mentioned. The ordering of examples places Azure CLI first, which is cross-platform, but the inclusion and prominence of PowerShell may suggest a slight Windows bias. There are no Linux-specific instructions or notes, and no mention of macOS.
Recommendations
- Clarify that Azure CLI commands work on Windows, Linux, and macOS.
- Add explicit Bash shell examples for Linux/macOS users, especially for template deployment.
- Note any platform-specific differences or prerequisites for Azure CLI and PowerShell.
- Consider mentioning cross-platform compatibility in the requirements section.
- If PowerShell is shown, consider showing Bash or Linux shell equivalents for parity.
Service Fabric
Plan an Azure Service Fabric cluster deployment
...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-azure-deployment-preparation.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation generally maintains OS neutrality, but in the 'Next steps' section, the link to creating a Windows cluster is listed before the Linux equivalent. No examples, tools, or instructions are specific to Windows or PowerShell, and Linux is mentioned as a supported OS throughout. No critical steps are Windows-only.
Recommendations
- List Windows and Linux cluster creation links side-by-side or alternate their order to avoid implicit prioritization.
- Continue to ensure examples and instructions are OS-agnostic or provide both Windows and Linux variants where appropriate.
- Explicitly mention Linux support in any sections discussing templates, scripts, or tooling if relevant.
Virtual Machine Scale Sets
Azure Virtual Machine Scale Sets Attached Data Disks
...cale-sets/virtual-machine-scale-sets-attached-disks.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Windows and Linux examples for preparing data disks in scale sets, but the Windows (PowerShell) example is presented first and uses a named script (prepare_vm_disks.ps1) with explicit PowerShell invocation. The Linux example follows, using bash. The initial tutorial links list Azure CLI before PowerShell, but the main example section gives Windows precedence. There is a slight bias toward Windows/PowerShell in ordering and example prominence.
Recommendations
- Alternate the order of Windows and Linux examples, or present them side-by-side for parity.
- Explicitly state that both Windows and Linux are supported before showing examples.
- Provide equal detail and context for both PowerShell and Bash scripts (e.g., describe what each script does).
- Where possible, use cross-platform tools (e.g., Azure CLI) as the primary example, with OS-specific instructions as secondary.
- Add a note that Linux/macOS users can use Azure CLI and Bash for all operations, and link to relevant tutorials.
Virtual Machines
Boot integrity monitoring overview
...virtual-machines/boot-integrity-monitoring-overview.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation demonstrates a mild Windows bias. Windows examples and terminology (e.g., PowerShell, WindowsAttestation publisher) are presented before Linux equivalents in several sections. The PowerShell tab is present, but there is no Bash or Linux shell scripting tab. Troubleshooting and configuration steps reference Windows-centric extension names and tools, and screenshots are from the Azure portal, which is platform-neutral but often reflects Windows conventions. However, Linux template examples are provided, and CLI instructions are generally cross-platform.
Recommendations
- Add a Bash or Linux shell scripting tab alongside PowerShell for parity.
- Ensure Linux examples are presented alongside or before Windows examples in all sections.
- Clarify that Azure portal and CLI instructions apply equally to Linux and Windows VMs.
- Include troubleshooting examples and error messages for Linux (e.g., referencing Microsoft.Azure.Security.LinuxAttestation.GuestAttestation failures).
- Balance screenshots to show Linux VM context where possible.
Virtual Machines
Support matrix for VM restore points
...n/articles/virtual-machines/concepts-restore-points.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation presents Windows operating system support details before Linux, listing specific Windows versions and only referencing Linux distributions in a general way. No PowerShell or Windows-specific tooling is used in examples, and Linux support is described, but Windows is given more detailed attention and is listed first.
Recommendations
- Present Windows and Linux operating system support in parallel, or list Linux first in some sections to balance presentation.
- Provide a more detailed list of supported Linux distributions (or link more prominently to the endorsed distros page).
- Ensure examples and guidance for creating restore points (referenced in 'Next steps') include both Linux and Windows scenarios equally.
Virtual Machines
Create a Gallery for Sharing Resources
.../blob/main/articles/virtual-machines/create-gallery.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides examples for Azure Portal, Azure CLI, PowerShell, and REST API. PowerShell is included as a dedicated example tab alongside CLI, which is cross-platform. However, PowerShell is primarily a Windows tool, and there is no mention of Linux/macOS-specific shell commands (e.g., Bash, shell scripts) or guidance for Linux users. In the ordering of examples, PowerShell is given equal prominence to CLI, and in some sections, it appears before REST, which may reinforce Windows-centric workflows. No explicit Linux tools or patterns are mentioned.
Recommendations
- Clarify that Azure CLI examples work on Linux/macOS as well as Windows.
- Add Bash or shell script examples where relevant, especially for automation scenarios.
- Note PowerShell's cross-platform availability, but avoid implying it is required for Linux/macOS users.
- Consider ordering CLI examples before PowerShell to emphasize cross-platform support.
- Explicitly mention that all tasks can be completed on Linux/macOS using CLI and REST.
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
windows_tools
Summary
The documentation page is focused on Linux VM extensions, but consistently presents both Azure CLI and Azure PowerShell examples for all operations. PowerShell examples are given equal prominence to CLI, despite PowerShell being a Windows-centric tool (even though it is available on Linux, CLI is more common for Linux users). References to ARM templates link to Windows documentation first, and some terminology (such as 'PowerShell') may be confusing for Linux users. However, all examples and screenshots are Linux-specific, and Linux tools (Azure CLI, waagent, Bash) are well represented.
Recommendations
- Prioritize Azure CLI examples and place them before PowerShell examples, as CLI is more widely used on Linux.
- Clarify that PowerShell is available on Linux, but Azure CLI is the recommended tool for Linux users.
- Link to ARM template documentation that is Linux-specific, or provide parity in links for both Windows and Linux.
- Where possible, use Bash and Linux-native commands in examples and troubleshooting sections.
- Consider omitting PowerShell examples or moving them to a separate tab or appendix for Linux-focused documentation.
Virtual Machines
Dedicated hosts include file
...es/virtual-machines/includes/dedicated-hosts-resize.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides examples for Azure Portal, Azure CLI, and PowerShell, with PowerShell (a Windows-centric tool) given a dedicated section and detailed command syntax. The CLI section uses Azure CLI, which is cross-platform, but PowerShell is highlighted separately, and no mention is made of Bash or Linux-specific workflows. The ordering places PowerShell after CLI, but the PowerShell section is more verbose and links to further Windows-specific resources.
Recommendations
- Add explicit Bash examples for Linux/macOS users, especially for scripting resize operations.
- Clarify that Azure CLI commands work identically on Linux, macOS, and Windows.
- Include a note or section for Linux/macOS users, mentioning alternative shell environments and any OS-specific considerations.
- Balance the detail level between PowerShell and CLI sections, ensuring Linux users have equally comprehensive guidance.
Virtual Machines
Prepare a Debian Linux VHD
...les/virtual-machines/linux/debian-create-upload-vhd.md
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page is focused on preparing Debian Linux VHDs for Azure and is generally Linux-centric. However, there is evidence of Windows bias in the 'Prerequisites' and 'Installation notes' sections, where Windows tools (Hyper-V, convert-vhd cmdlet) are mentioned first and in more detail than Linux alternatives. Linux tools for VHD creation (e.g., qemu-img) are covered later, but Windows options are introduced before Linux equivalents, and links to Windows-specific instructions are provided.
Recommendations
- Mention Linux-native VHD creation tools (e.g., qemu-img, VBoxManage) alongside or before Windows tools in the prerequisites section.
- Provide links to Linux-specific guides for creating and converting VHD files.
- Clarify that Hyper-V is only one of several options and highlight Linux alternatives equally.
- If referencing Windows tools, also give equivalent Linux command-line examples and documentation links.
- Ensure that Linux users can complete all steps without needing Windows or Windows-only tools.
Virtual Machines
Azure VM Image Builder networking options
...les/virtual-machines/linux/image-builder-networking.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation presents Windows-related examples and tools (PowerShell) before their Linux equivalents (Azure CLI) in several places. For example, in the 'Checklist for using your virtual network' section, PowerShell examples are consistently listed after Azure CLI, but the links for Windows and PowerShell are present throughout. Additionally, the 'Required permissions' section lists both CLI and PowerShell, but PowerShell is called out specifically for Windows users. There is also an 'IMPORTANT' note that is Windows-specific (WinRM configuration), while no equivalent Linux-specific caveat is provided.
Recommendations
- Ensure Linux/Azure CLI examples are presented first or equally alongside Windows/PowerShell examples.
- Add Linux-specific notes or caveats where Windows-specific ones are present (e.g., SSH configuration impacts).
- Where possible, clarify that PowerShell is available cross-platform, or provide Bash examples for Linux/macOS users.
- Review linked example pages to ensure Linux and Windows parity in depth and clarity.
Virtual Machines
Use a template to deploy Azure Spot Virtual Machines
.../main/articles/virtual-machines/linux/spot-template.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation mentions Azure PowerShell (Windows-centric) before Azure CLI in the 'Next steps' section, and links to a Windows-specific PowerShell guide. No Linux-specific tools or examples are provided, although the template itself is OS-agnostic and uses Ubuntu as the VM image.
Recommendations
- List Azure CLI before Azure PowerShell in 'Next steps', as CLI is cross-platform.
- Provide explicit Linux/macOS usage examples, such as deploying the template via Azure CLI on Linux.
- Include links to Linux-specific guides or troubleshooting resources.
- Clarify that the template can be used from any OS and provide instructions for both Windows and Linux users.
Virtual Machines
MSP Feature Configuration
...l-machines/metadata-security-protocol/configuration.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation shows mild Windows bias. Windows is mentioned first in several places (e.g., 'automatic GPA installation (when true) or uninstallation (when false) on a Windows VM'), and example resource names use 'GPAWinVM'. However, Linux is supported and audit log locations are documented for both OSes. No PowerShell-only examples or Windows-exclusive instructions are present, but Windows terminology and ordering are favored.
Recommendations
- Use neutral example resource names (e.g., 'GPAExampleVM' instead of 'GPAWinVM').
- When describing behaviors, mention both Windows and Linux equally (e.g., 'automatic GPA installation/uninstallation on Windows or Linux VMs').
- Ensure that any OS-specific instructions or behaviors are documented for both Windows and Linux, with equal prominence.
- Alternate the order in which Windows and Linux are listed/described, or use OS-neutral phrasing.
- Add explicit Linux configuration examples if any OS-specific steps exist.
Virtual Machines
We're retiring Azure unmanaged disks by March 31, 2026
...ticles/virtual-machines/unmanaged-disks-deprecation.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation page exhibits minor Windows bias by listing Windows migration resources before Linux equivalents and referencing PowerShell as a primary tool for querying affected VMs, with no mention of Linux CLI alternatives (e.g., Azure CLI, Bash). However, both Windows and Linux migration guides are linked, and the overall instructions are platform-neutral.
Recommendations
- Present Linux and Windows migration links together or alternate their order to avoid Windows-first bias.
- Include Linux-friendly command-line examples (e.g., Azure CLI, Bash scripts) alongside PowerShell for querying affected VMs.
- Explicitly mention Linux tools and workflows in sections discussing VM discovery and migration.
- Add a note clarifying that all steps can be performed on Linux/macOS using Azure CLI or portal, not just PowerShell.
Service Fabric
Create an Azure Service Fabric container application on Linux
...-fabric/service-fabric-get-started-containers-linux.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation is primarily focused on Linux, but there are minor instances of Windows bias. Notably, the instructions for logging into Docker and building the image suggest opening a PowerShell window, which is a Windows-specific tool. Additionally, the example commands are sometimes shown with Windows conventions (e.g., PowerShell), and Windows tools are mentioned before their Linux equivalents in some places. However, the majority of the content, tooling, and examples are Linux-centric, and Linux users can complete all tasks without significant friction.
Recommendations
- Replace 'Open a PowerShell window' with 'Open a terminal window' or specify both PowerShell (Windows) and terminal (Linux/macOS) options.
- Ensure all command examples use cross-platform syntax (e.g., bash) and avoid Windows-specific conventions unless explicitly needed.
- If referencing Windows tools or patterns, always provide the Linux/macOS equivalent first or alongside.
- Review for any other subtle Windows-first language and adjust to prioritize Linux/macOS context, given the article's focus.
Service Fabric
Reliable Collection object serialization
...c-reliable-services-reliable-collections-serialization.md
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page demonstrates mild Windows bias by referencing Windows-specific tools (Visual Studio and PowerShell) in the 'Next steps' section, with no mention of Linux/macOS equivalents or cross-platform alternatives. The examples and technical content are platform-neutral C#, but the upgrade guidance and tooling references prioritize Windows environments.
Recommendations
- Add instructions or links for upgrading applications using cross-platform tools such as Azure CLI or Service Fabric CLI.
- Include guidance for Linux/macOS users on how to perform upgrades and serialization tasks outside of Visual Studio and PowerShell.
- Explicitly mention platform compatibility for the code samples and APIs, clarifying if/when they are usable on Linux/macOS.
- Provide parity in 'Next steps' by listing Linux/macOS-friendly tutorials and troubleshooting guides.
Service Fabric
Create a Linux Service Fabric cluster in Azure
...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-tutorial-create-vnet-and-linux-cluster.md
Low Priority
View Details â
Detected Bias Types
windows_path_examples
windows_file_path_patterns
Summary
The documentation is focused on deploying a Linux Service Fabric cluster using Azure CLI and Service Fabric CLI, with no PowerShell or Windows-specific tools used in the main instructions. However, several example file paths use Windows-style (e.g., C:\MyCertificates), and there is no mention of Linux/macOS file path equivalents. This may cause minor confusion for Linux/macOS users, but the overall workflow is cross-platform.
Recommendations
- Provide Linux/macOS file path examples alongside Windows paths (e.g., ~/MyCertificates or /home/user/MyCertificates).
- Add a note clarifying that file paths should be adapted to the user's OS.
- Explicitly mention that Azure CLI and Service Fabric CLI are cross-platform and can be used on Linux/macOS.
- Consider showing Linux/macOS shell commands (e.g., export VAR=value) if environment variables are set.
Service Fabric
Azure Service Fabric versions
...ain/articles/service-fabric/service-fabric-versions.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation page presents Windows content first, including upgrade procedures and OS support tables, and references Windows-specific tools and lifecycle links before Linux equivalents. While Linux parity is generally maintained via tab selectors and parallel tables, Windows is consistently prioritized in structure and navigation. Some links and upgrade procedures are Windows-specific or default to Windows, with Linux guidance less prominent.
Recommendations
- Present Windows and Linux tabs in a neutral order (e.g., alphabetical or randomized) or default to user's OS when possible.
- Ensure upgrade procedures and links are available and equally prominent for Linux clusters.
- Add Linux-specific lifecycle and support links alongside Windows equivalents in summary sections.
- Review cross-references to ensure Linux guidance is not omitted or less visible than Windows guidance.
- Consider a combined summary table for OS support, with clear separation for Windows and Linux, to avoid Windows-first presentation.
Virtual Machine Scale Sets
Encrypt disks for Azure scale sets with Azure CLI
...cles/virtual-machine-scale-sets/disk-encryption-cli.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_heavy
minor_linux_example
Summary
The documentation page is titled and described as targeting Windows Virtual Machine Scale Sets, and the introductory context is Windows-centric. However, the main Azure CLI examples use Linux images and Linux tooling (Custom Script Extension with a shell script), and there is a link to a Linux batch file example at the end. The page does not provide explicit Windows-specific CLI commands or PowerShell examples, but the framing and references are Windows-first, with Linux support present but less emphasized.
Recommendations
- Update the title and description to clarify that both Windows and Linux VMSS are supported, or provide separate sections/examples for each.
- Add explicit Windows VMSS examples (e.g., using Windows images, Windows Custom Script Extension, and PowerShell commands) alongside the Linux examples.
- Present Linux and Windows examples in parallel, or clearly indicate which steps apply to which OS.
- Ensure that references to OS support (such as the ADE supported OS link) are accompanied by guidance for both platforms.
- Move or duplicate the Linux batch file example to a more prominent location, not just in 'Next steps'.
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
windows_tools
missing_linux_example
Summary
The documentation page demonstrates mild Windows bias. Windows-specific scenarios (such as VM activation and Windows updates) are mentioned before Linux equivalents, and troubleshooting links are provided only for Windows. There are no explicit Linux-focused migration examples or references to Linux-specific tools or package managers. Azure PowerShell is listed as a primary tool alongside Azure CLI, but Linux-specific command-line patterns are not highlighted. The only CLI example uses Azure CLI, which is cross-platform, but the overall narrative and troubleshooting guidance favor Windows environments.
Recommendations
- Add explicit Linux migration scenarios and troubleshooting links (e.g., for Linux VM activation or common Linux update issues).
- Provide examples of Linux package manager outbound connectivity requirements (e.g., apt, yum, zypper) and link to relevant documentation.
- Ensure parity in listing tools: mention Bash scripting and Linux-native automation tools alongside PowerShell.
- Where Windows-specific requirements are listed (e.g., activation, updates), provide Linux equivalents in parallel.
- Consider reordering sections so that Windows and Linux requirements are presented together, or alternate which is listed first.
Virtual Machine Scale Sets
Create virtual machines in a Flexible scale set using Azure portal
...ale-sets/flexible-virtual-machine-scale-sets-portal.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates mild Windows bias. Password requirements link to a Windows-specific FAQ, and Windows terminology (e.g., 'Password' complexity) is described before Linux SSH key options. The password requirements reference a Windows documentation page, while the SSH key generation link is Linux/macOS-specific but less prominent. No explicit Linux command-line examples or Linux-specific troubleshooting are provided, and Windows is mentioned first when discussing OS image choices.
Recommendations
- Provide equal prominence to Linux and Windows options when describing administrator account setup, including direct links to both Linux and Windows documentation for password/SSH requirements.
- When referencing password requirements, link to a cross-platform or Linux-specific page if available, or clarify that requirements apply to both OS types.
- Mention Linux images first or alternate the order to avoid Windows-first bias.
- Include a brief note or link about Linux-specific considerations (e.g., SSH key management, cloud-init usage) in the portal workflow.
- Ensure that screenshots and examples reflect both Windows and Linux scenarios where relevant.
Virtual Machine Scale Sets
Update a Virtual Machine Scale Set with instance mix
...cles/virtual-machine-scale-sets/instance-mix-update.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for updating VMSS instance mix settings, but PowerShell (a Windows-centric tool) is given equal prominence to CLI, and is presented before REST API examples. There are no explicit Linux/macOS-specific examples or notes, and PowerShell code is detailed and assumes familiarity with Windows tooling. However, Azure CLI is cross-platform and all critical tasks can be completed with CLI or REST API, so Linux/macOS users are not blocked.
Recommendations
- Explicitly state that Azure CLI commands work on Linux/macOS and Windows.
- Add a note clarifying that PowerShell examples are primarily for Windows users, while CLI is recommended for Linux/macOS.
- Consider presenting Azure CLI examples before PowerShell, or grouping them together with a note on platform compatibility.
- If relevant, mention installation or usage differences for CLI on Linux/macOS.
- Add troubleshooting or FAQ notes for Linux/macOS users if any issues are known.
Virtual Machine Scale Sets
Get high availability and cost savings with Spot Priority Mix for Virtual Machine Scale Sets
...ticles/virtual-machine-scale-sets/spot-priority-mix.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation presents Azure CLI and Azure PowerShell examples in parallel, but PowerShell is shown as a first-class method throughout, and no explicit Linux/macOS shell (e.g., Bash) examples are provided. The CLI examples use generic syntax compatible with Linux/macOS, but PowerShell is given equal prominence, which may imply a Windows-centric approach. There are no references to Linux-specific tools or workflows, and the portal instructions are platform-neutral.
Recommendations
- Explicitly mention that Azure CLI commands work on Linux/macOS and provide sample Bash shell usage (e.g., with environment variables or piping).
- Add a note clarifying that PowerShell examples are for Windows and Azure PowerShell Core is available cross-platform, if relevant.
- Consider including a Bash script example for scale set creation and update to demonstrate parity.
- If there are any platform-specific caveats (e.g., CLI installation, authentication), link to Linux/macOS instructions.
- Ensure that CLI examples are shown before PowerShell, or clarify that both are supported equally across platforms.
Virtual Machine Scale Sets
Understand the health state of your standby pool
...rtual-machine-scale-sets/standby-pools-health-state.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides examples for Azure CLI, PowerShell, and REST API. The PowerShell example is given equal prominence to the CLI example, but PowerShell is a Windows-centric tool. There is no explicit mention of Linux/macOS-specific shell usage (e.g., Bash), nor are there examples showing how to use the REST API with Linux-native tools like curl or httpie. The CLI example is cross-platform, but the ordering and inclusion of PowerShell may suggest a slight Windows bias.
Recommendations
- Add explicit Bash/Linux/macOS shell examples for REST API usage (e.g., using curl or httpie).
- Clarify that Azure CLI is cross-platform and works on Linux/macOS as well as Windows.
- Consider including Bash scripting examples for automation on Linux/macOS.
- If PowerShell is included, note that PowerShell Core is available cross-platform, or provide equivalent Bash examples.
Virtual Machine Scale Sets
Get standby pool and instance details
...irtual-machine-scale-sets/standby-pools-get-details.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for all major tasks, but PowerShell examples are given equal prominence as CLI, despite PowerShell being primarily a Windows tool. There is no explicit Linux shell scripting or macOS-specific guidance, and PowerShell is presented as a first-class option, which may create friction for Linux/macOS users who typically use Bash or other shells. However, the Azure CLI and REST API examples are cross-platform and sufficient for Linux/macOS users.
Recommendations
- Clarify that Azure CLI commands work on Linux/macOS and Windows equally.
- Add Bash shell scripting examples for common tasks, especially where PowerShell is shown.
- Explicitly mention platform compatibility for each example tab.
- Consider moving PowerShell examples after CLI examples, or labeling CLI as the recommended cross-platform approach.
Virtual Machine Scale Sets
Delete or update a standby pool for Virtual Machine Scale Sets
...tual-machine-scale-sets/standby-pools-update-delete.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for updating and deleting standby pools, but PowerShell (a Windows-centric tool) is given equal prominence and is mentioned in deployment instructions (e.g., ARM/Bicep templates) alongside the CLI. The use of PowerShell-specific cmdlets and deployment instructions referencing PowerShell before Linux-native alternatives (like Bash scripts or automation) shows a mild Windows bias. However, Azure CLI examples are present and shown first, which are cross-platform, and REST API examples are included. There are no Linux/macOS-specific examples or notes, and no mention of Linux tools or shell scripting.
Recommendations
- Add explicit Bash or shell script examples for Linux/macOS users where appropriate.
- Clarify that Azure CLI commands work on Linux/macOS and Windows, and consider adding OS-specific notes.
- When referencing deployment methods (ARM/Bicep), mention cross-platform automation tools (e.g., Bash, GitHub Actions) before or alongside PowerShell.
- Include troubleshooting notes or links for Linux/macOS environments if any differences exist.
- Ensure that PowerShell is not presented as the default or primary method unless required.
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, update VMSS), but consistently lists PowerShell examples after CLI and before any Linux-specific shell scripts. The PowerShell examples use Windows-centric syntax (backticks, variable assignment), and troubleshooting links for disk migration and proximity placement groups point to Windows documentation first. There is no explicit Linux bias, but the ordering and example selection subtly favor Windows/PowerShell users.
Recommendations
- Ensure that Linux/macOS shell examples (e.g., Bash scripts) are provided where PowerShell is shown, especially for advanced scenarios.
- When linking to migration or troubleshooting guides, include both Windows and Linux documentation, or link to OS-neutral pages.
- Alternate the order of CLI and PowerShell examples, or group them under 'Command-line' with clear OS applicability.
- Explicitly state that Azure CLI works cross-platform and highlight any OS-specific caveats.
- Add notes or examples for common Linux/macOS patterns (e.g., using export for environment variables, handling file paths).
Virtual Machine Scale Sets
Autoscale Virtual Machine Scale Sets in the Azure portal
...le-sets/virtual-machine-scale-sets-autoscale-portal.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation page primarily describes how to configure autoscale rules for Azure Virtual Machine Scale Sets using the Azure portal, which is cross-platform. However, when referencing command-line alternatives, it consistently lists Azure PowerShell (Windows-centric) before Azure CLI (cross-platform). Additionally, the 'Next steps' section links only to PowerShell-based management documentation, omitting Azure CLI or Linux-native alternatives. There are no Linux/macOS-specific examples or considerations, and Windows tools/patterns are mentioned first throughout.
Recommendations
- When referencing command-line alternatives, list Azure CLI before or alongside Azure PowerShell to emphasize cross-platform support.
- In the 'Next steps' section, provide links to both Azure PowerShell and Azure CLI management documentation.
- Explicitly mention that the Azure portal and Azure CLI are available on Linux/macOS, and provide examples or links for those platforms.
- Add a brief note or section highlighting parity and considerations for Linux/macOS users, especially for automation or scripting tasks.
Virtual Machine Scale Sets
Change the upgrade policy mode on Virtual Machine Scale Sets
...ts/virtual-machine-scale-sets-change-upgrade-policy.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides platform-specific instructions for Azure Portal, CLI, PowerShell, and ARM Template. While CLI and ARM Template are cross-platform, PowerShell is Windows-centric and is given a dedicated section with detailed examples. The PowerShell example is as detailed as the CLI example, but there is no mention of Bash, Linux shell, or macOS-specific guidance. The ordering of tabs places PowerShell before ARM Template, which may subtly prioritize Windows tooling.
Recommendations
- Explicitly mention that Azure CLI commands work on Linux/macOS and Windows, and consider providing Bash-specific examples or notes where relevant.
- Clarify that PowerShell Core is available cross-platform, or provide Bash equivalents for PowerShell commands where possible.
- Consider reordering tabs so that cross-platform tools (CLI, ARM Template) appear before Windows-centric tools (PowerShell).
- Add a note for Linux/macOS users about installing and using Azure CLI and PowerShell Core.
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 major operations, but PowerShell examples are always present and shown after CLI, which is cross-platform. There are no Linux/macOS-specific examples or mentions of platform-specific considerations. The use of PowerShell may imply a Windows bias, as it is traditionally associated with Windows environments, although PowerShell Core is available cross-platform. No explicit Windows-only tools or instructions are present, but the documentation does not address Linux/macOS shell usage or potential differences.
Recommendations
- Clarify that Azure CLI commands work on Windows, Linux, and macOS, and recommend CLI for cross-platform users.
- Add bash or shell script examples for Linux/macOS users where appropriate.
- Note that PowerShell Core is available on Linux/macOS, or provide links to installation instructions for non-Windows platforms.
- Explicitly mention that all operations can be performed from Linux/macOS using Azure CLI.
- Consider reordering examples to show CLI first, emphasizing its cross-platform nature.
Virtual Machine Scale Sets
Rolling upgrades with MaxSurge for Virtual Machine Scale Sets
...hine-scale-sets/virtual-machine-scale-sets-maxsurge.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides configuration instructions for rolling upgrades with MaxSurge using the Azure Portal, Azure CLI, PowerShell, and ARM templates. While the CLI and ARM template examples are cross-platform, the PowerShell example is Windows-specific and presented as a primary method. The PowerShell tab is included before ARM template instructions, and there is no mention of Linux/macOS-specific tools (e.g., Bash scripting, Cloud Shell usage on Linux/macOS, or cross-platform automation patterns). There are no explicit Linux/macOS examples or guidance.
Recommendations
- Add explicit Bash shell examples for Linux/macOS users, especially for scripting with Azure CLI.
- Clarify that Azure CLI commands work identically on Windows, Linux, and macOS, and recommend CLI for cross-platform automation.
- Reorder tabs so CLI instructions appear before PowerShell, emphasizing CLI as the default cross-platform method.
- Mention Azure Cloud Shell as a cross-platform environment for running CLI and PowerShell commands.
- Note any limitations or differences for Linux/macOS users when using PowerShell (e.g., installation requirements, feature parity).
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
missing_linux_example
powershell_heavy
Summary
The documentation page exhibits mild Windows bias. While it generally describes Azure orchestration modes in a platform-neutral way, there are several areas where Windows is referenced first or exclusively. For example, the Managed Identity section links to a Windows VMSS-specific guide, and Azure Site Recovery is noted as supported 'via PowerShell' (a Windows-centric tool) without mentioning Linux alternatives. There are no explicit Linux CLI or shell script examples; the only command-line example uses Azure CLI, which is cross-platform, but the documentation does not clarify Linux usage or provide bash-specific guidance. Overall, Linux/macOS users may need to infer or adapt instructions, but most features are described in a way that is not strictly Windows-only.
Recommendations
- Add explicit Linux/macOS examples or notes where PowerShell is referenced, such as for Azure Site Recovery.
- Ensure links and references to Managed Identity configuration include Linux VMSS guides, not only Windows.
- Where command-line examples are given, clarify cross-platform compatibility and provide bash or shell script equivalents if relevant.
- Review all feature tables and descriptions to ensure Linux support is mentioned where applicable, especially for VM extensions and monitoring.
- Avoid referencing Windows tools (e.g., PowerShell) exclusively; mention Azure CLI or REST API alternatives where possible.
Virtual Machine Scale Sets
Performing manual upgrades on Virtual Machine Scale Sets
...https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-perform-manual-upgrades.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides examples for Azure Portal, Azure CLI, PowerShell, and REST API. While CLI and REST are cross-platform, the PowerShell section is Windows-centric and is presented before REST. There is no explicit Linux/macOS bias, but PowerShell is a Windows-first tool and its inclusion without Bash or other Linux-native shell examples may create friction for Linux users. The CLI example is cross-platform and shown before PowerShell, which helps mitigate bias.
Recommendations
- Add explicit Bash or shell script examples for Linux users, especially for automation scenarios.
- Clarify that Azure CLI commands work on Linux, macOS, and Windows.
- Consider mentioning cross-platform alternatives to PowerShell for Linux/macOS users.
- Reorder sections to consistently present cross-platform tools (CLI, REST) before Windows-centric tools (PowerShell).
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 frequently presented before CLI, and some advanced examples are more detailed in PowerShell. There is a slight preference for Windows tools and patterns, with PowerShell examples shown before CLI in several sections. However, Linux/macOS users can generally complete all tasks using the CLI or ARM templates, and Linux-specific links/examples are present where relevant.
Recommendations
- Present CLI examples before PowerShell examples to reflect cross-platform parity.
- Ensure CLI and PowerShell examples are equally detailed and comprehensive.
- Explicitly state that CLI commands work on Linux/macOS and Windows, and clarify any platform-specific caveats.
- Where PowerShell is referenced, provide Bash or shell script equivalents for Linux/macOS users.
- Review external links to ensure Linux documentation is as discoverable and prominent as Windows documentation.
Virtual Machine Scale Sets
Use scale-in policies with Azure Virtual Machine Scale Sets
...ale-sets/virtual-machine-scale-sets-scale-in-policy.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation presents Azure PowerShell examples before Azure CLI examples, and uses PowerShell-specific syntax and terminology. This ordering and emphasis may suggest a Windows-centric approach, especially since PowerShell is most commonly associated with Windows environments, even though it is cross-platform. There is no explicit mention of Linux/macOS-specific considerations, nor are there examples using Bash or other Linux-native tools. However, Azure CLI examples are provided, which are suitable for Linux/macOS users.
Recommendations
- Present Azure CLI examples before PowerShell examples, as CLI is more commonly used on Linux/macOS.
- Explicitly mention that Azure CLI commands work on Linux/macOS and provide guidance for those platforms.
- Add notes clarifying PowerShell's cross-platform availability, but avoid implying it is the default for all users.
- Consider including Bash script examples for resource creation and management, or link to Linux/macOS-specific guides.
- Ensure troubleshooting and next steps sections reference both CLI and PowerShell equally, and highlight platform parity.
Virtual Machines
Availability options for Azure Virtual Machines
...cs/blob/main/articles/virtual-machines/availability.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation page is mostly platform-neutral, but in the 'Load balancer' section, PowerShell is mentioned before CLI as an example for quickstarts, and both links are provided. This ordering may subtly prioritize Windows users. There are no Linux-specific examples in the main body, but the 'Next steps' section does link to Linux-focused tutorials. No Windows-only tools or patterns are exclusively referenced, but PowerShell is given equal prominence to CLI, which is more cross-platform.
Recommendations
- Present CLI examples before PowerShell examples, as CLI is cross-platform and more accessible to Linux/macOS users.
- Explicitly mention that both CLI and PowerShell are supported, and clarify which is recommended for Linux/macOS users.
- Add Linux/macOS-specific notes or examples in relevant sections to further improve parity.
- Ensure that all referenced quickstarts and tutorials have Linux/macOS equivalents and are clearly labeled.
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Windows and Linux applicability, but there is a mild bias toward Windows in the ordering and tooling. PowerShell is mentioned as a primary method for enabling boot diagnostics, with CLI and ARM Template alternatives. The link for configuring the storage firewall for Azure Serial Console points to a Windows-specific troubleshooting page, even though Linux VMs are supported. Windows screenshots/examples are presented alongside Linux, but Windows tools (PowerShell) are given a dedicated section before ARM templates.
Recommendations
- Ensure that Linux-specific tools (such as Bash scripts or Linux shell commands) are given equal prominence to PowerShell, with example commands for enabling boot diagnostics on Linux VMs.
- When referencing troubleshooting guides or configuration steps, provide both Windows and Linux links, or clarify applicability for both OS types.
- Alternate the order of examples so that Linux and Windows are presented with parity, or group them together when possible.
- Explicitly mention cross-platform support in CLI and ARM Template sections, and provide sample commands for both Linux and Windows environments.
Virtual Machines
Best practices for virtual machine cost optimization
...s/virtual-machines/cost-optimization-best-practices.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation demonstrates mild Windows bias. Windows-specific recommendations (e.g., 'Use at least B2 for Windows machines', 'Azure Hybrid Benefit for Windows Server') are given without equivalent Linux guidance. Windows pricing and licensing options are mentioned before Linux, and some cost-saving tips are Windows-only. There are no Linux-specific cost optimization examples or tools highlighted, and Linux is generally referenced second or as an afterthought.
Recommendations
- Add Linux-specific cost optimization tips, such as recommendations for Linux VM series, licensing, and storage.
- Provide parity in examples: if mentioning Azure Hybrid Benefit for Windows, clarify Linux licensing options (e.g., bring-your-own subscription for RHEL/SUSE).
- When listing pricing pages or VM sizes, alternate or parallelize Windows and Linux references.
- Include automation and shutdown examples relevant to Linux (e.g., using cron, Azure Automation for Linux VMs).
- Ensure that recommendations for VM sizing, disk types, and policies explicitly address both Windows and Linux use cases.
Virtual Machines
Create a capacity reservation in Azure
...ticles/virtual-machines/capacity-reservation-create.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides examples for Azure Portal, Azure CLI, and Azure PowerShell in parallel tabbed sections. However, PowerShell is given equal prominence to CLI, despite being primarily a Windows tool. In some sections, PowerShell examples are shown immediately after CLI, and PowerShell-specific commands are referenced directly. There are no Linux-specific shell examples (e.g., Bash), and no mention of platform differences or considerations for Linux/macOS users. The CLI examples are cross-platform, but the presence and prominence of PowerShell may create a perception of Windows bias.
Recommendations
- Clarify that Azure CLI commands work on Linux, macOS, and Windows equally, and consider providing explicit Bash examples or notes for Linux/macOS users.
- Add a brief note explaining that PowerShell examples are primarily for Windows users, and that Linux/macOS users should use Azure CLI or Bash.
- Consider reordering tabs so that CLI (cross-platform) appears before PowerShell, or add a 'Bash' tab for Linux/macOS users if there are platform-specific nuances.
- Reference platform parity in introductory sections, reassuring users that all major steps can be completed on Linux/macOS using CLI.
Virtual Machines
Modify a capacity reservation in Azure
...ticles/virtual-machines/capacity-reservation-modify.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides parity between Azure CLI and PowerShell examples, but PowerShell is always presented as a first-class option alongside CLI, and is shown in every tabbed section. There is a subtle Windows bias in that PowerShell is a Windows-centric tool (even though it is now cross-platform, many users still associate it with Windows), and the ordering of tabs is API, Portal, CLI, then PowerShellâplacing PowerShell last but always present. There are no explicit Linux-only examples, and no mention of Linux-specific tools or shell patterns (e.g., bash scripting). However, the CLI examples are cross-platform and suitable for Linux/macOS users, and the documentation states applicability to both Linux and Windows VMs.
Recommendations
- Explicitly mention that Azure CLI commands work on Linux/macOS and provide sample bash/zsh usage where relevant.
- Clarify that PowerShell is available cross-platform, but highlight CLI as the default for Linux/macOS users.
- Consider reordering tabs so CLI appears before PowerShell, or add a note for Linux users recommending CLI.
- Add troubleshooting tips or links for Linux/macOS users if there are known issues with PowerShell or CLI on those platforms.
Virtual Machines
Proximity placement groups
...ocs/blob/main/articles/virtual-machines/co-location.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
minor_windows_tools
Summary
The documentation generally maintains cross-platform parity, explicitly stating applicability to both Linux and Windows VMs. However, there are minor signs of Windows bias: PowerShell is mentioned before CLI in several places, and Windows terminology/tools (PowerShell, Availability Set Overview page) are referenced slightly more prominently than their Linux equivalents. Examples and links for both platforms are provided, but Windows tools are sometimes listed first.
Recommendations
- Alternate the order of CLI and PowerShell references so Linux tools are not always second.
- Where possible, provide equal detail for both CLI and PowerShell commands, or combine instructions for cross-platform tools.
- Mention Linux-specific management interfaces (e.g., Azure CLI in Cloud Shell, Linux VM portals) where relevant.
- Ensure screenshots and UI references are platform-neutral or provide both Linux and Windows examples.
Virtual Machines
Configure Event Hubs for VM watch
...ticles/virtual-machines/configure-eventhub-vm-watch.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page exhibits mild Windows bias. References to PowerShell and Windows tools are present before Linux equivalents, and links to configuration instructions mention PowerShell alongside ARM templates and CLI. The log file troubleshooting section does provide both Linux and Windows paths, but there are no explicit Linux/macOS command-line examples (e.g., using Bash or Linux-native tools) for configuring or viewing Event Hubs data. Windows terminology and patterns (e.g., C:/WindowsAzure paths, PowerShell) are mentioned first or exclusively in some places.
Recommendations
- Provide Linux/macOS command-line examples (e.g., Bash, Azure CLI) alongside or before Windows/PowerShell examples.
- Ensure links to configuration instructions highlight Linux/macOS methods equally (not just PowerShell).
- When mentioning log file paths or troubleshooting, present Linux and Windows paths in parallel, not sequentially.
- Add screenshots or instructions for viewing Event Hubs data using Linux/macOS tools (e.g., az CLI, curl, jq) if possible.
- Review terminology to avoid Windows-centric language (e.g., use 'file system path' instead of 'C:/...').
Virtual Machines
Deploy Azure dedicated hosts
...in/articles/virtual-machines/dedicated-hosts-how-to.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides parity between Azure Portal, Azure CLI, and PowerShell for all major operations. However, there is a mild Windows bias: PowerShell examples are given equal weight to CLI, and in some sections (e.g., 'Reassign an existing VM', 'Move a VM from dedicated host to multitenant infrastructure'), PowerShell is presented after CLI but with detailed variable usage and scripting, which is more familiar to Windows users. The CLI examples are cross-platform, but PowerShell is inherently Windows-centric (though available on Linux, it's less commonly used there). There are no explicit Linux-only examples (e.g., bash scripts), and the documentation does not mention Linux-specific tools or patterns. The Portal instructions are neutral.
Recommendations
- Add explicit bash script examples for common tasks to demonstrate Linux-native workflows.
- Clarify that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
- Consider mentioning that PowerShell is available on Linux/macOS, but CLI is more typical for those platforms.
- Where relevant, note any differences in experience or prerequisites for Linux/macOS users (e.g., SSH keys, shell environment).
- If possible, add troubleshooting or tips sections for Linux users (e.g., dealing with az CLI installation, permissions, etc.).
Virtual Machines
Use a disk encryption set across Microsoft Entra tenants
...l-machines/disks-cross-tenant-customer-managed-keys.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation page exhibits mild Windows bias by referencing PowerShell and Windows-specific installation instructions before Linux alternatives. The PowerShell section links to 'Install Azure PowerShell on Windows with PowerShellGet', and PowerShell is presented before Azure CLI in several places. However, Azure CLI examples are provided, and no critical steps are Windows-only.
Recommendations
- Provide installation instructions for Azure PowerShell on Linux/macOS alongside Windows.
- Avoid referencing Windows-specific installation methods (e.g., PowerShellGet) without mentioning cross-platform alternatives.
- Alternate the order of PowerShell and CLI examples, or present CLI first to better reflect cross-platform usage.
- Explicitly state that both PowerShell and CLI are cross-platform, and provide links to installation guides for all OSes.
Virtual Machines
Benchmark your application on Azure Disk Storage
...lob/main/articles/virtual-machines/disks-benchmarks.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation introduces Windows benchmarking tools (DiskSpd) before Linux equivalents (FIO), and mentions DiskSpd as the primary example for Windows. The order and phrasing subtly prioritize Windows tools and patterns, though Linux is acknowledged and FIO is referenced. No explicit Linux example is missing, but the Windows tool is listed first and its link precedes the Linux tool.
Recommendations
- Present Linux and Windows tools in parallel, or alternate which is mentioned first.
- Provide equal detail and prominence to both DiskSpd and FIO, including links and example usage.
- Consider adding explicit command-line examples for both platforms in the main documentation, not just in includes.
- Clarify that both Linux and Windows are fully supported and provide parity in instructions.
Virtual Machines
Copy a snapshot to a new region
...ines/disks-copy-incremental-snapshot-across-regions.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for copying snapshots, but the PowerShell section is detailed and includes installation instructions, which may suggest a Windows-centric approach. The CLI examples use Bash syntax, which is cross-platform, but there are no explicit Linux/macOS-specific notes or troubleshooting tips. The manual copy section references .NET sample code, which is more common on Windows. There are no examples or guidance for Linux-specific tools or shell environments beyond Bash, nor any mention of macOS.
Recommendations
- Add explicit Linux/macOS troubleshooting notes for Azure CLI usage (e.g., common permission issues, path differences).
- Include example scripts using native Linux tools or environments (e.g., zsh, fish) if relevant.
- Provide parity in installation instructions for Azure CLI and PowerShell on Linux/macOS.
- Reference or provide sample code in languages popular on Linux/macOS (e.g., Python, Go) for manual copy operations.
- Clarify that Bash examples work on Linux/macOS and Windows (WSL, Git Bash), and mention any platform-specific caveats.
Virtual Machines
Enable on-demand disk bursting
...ain/articles/virtual-machines/disks-enable-bursting.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation page presents both Azure PowerShell and Azure CLI examples, but PowerShell (a Windows-centric tool) is listed before CLI. The PowerShell section is more detailed, and references to 'cmdlets' and the Azure PowerShell module are prominent. There is no explicit mention of Linux/macOS-specific shell environments or considerations, and no Bash or shell script examples are provided. The Azure portal and Resource Manager template sections are neutral, but the command-line guidance leans toward Windows tools and patterns.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and more common for Linux/macOS users.
- Add explicit Bash/shell script examples or notes for Linux/macOS users where relevant.
- Clarify that Azure CLI and Cloud Shell are fully supported on Linux/macOS, and provide links or instructions for installation on those platforms.
- Avoid referring to command-line examples as 'cmdlets' when discussing CLI, as this is a PowerShell-specific term.
- Consider adding a section or note about using these commands in Linux/macOS environments, including any differences or prerequisites.
Virtual Machines
Migrate Standard HDD OS disks by September 08, 2028
...n/articles/virtual-machines/disks-hdd-os-retirement.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation mentions both Linux and Windows VMs as affected, but when listing tools and examples for identifying affected disks, it references Azure PowerShell before Azure CLI and provides a PowerShell command first. The Disk Storage Center is a GUI tool that is most familiar to Windows users. There are no explicit Linux/macOS shell examples (e.g., Bash), and the CLI example is shown after PowerShell, suggesting a Windows-first approach.
Recommendations
- Present Azure CLI (cross-platform) examples before PowerShell examples.
- Include Bash shell script examples for Linux/macOS users.
- Clarify that Disk Storage Center is accessible via browser on any OS, not just Windows.
- Add explicit guidance for Linux/macOS users, such as using Azure CLI in Bash or Zsh.
- Ensure parity in troubleshooting and migration steps for both platforms.
Virtual Machines
Enable end-to-end encryption using encryption at host - Azure portal - managed disks
...-machines/disks-enable-host-based-encryption-portal.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation demonstrates mild Windows bias by listing Azure PowerShell examples before Azure CLI, referencing PowerShell in links and resource samples, and providing links to Windows-specific guides before Linux equivalents. However, both PowerShell and CLI commands are shown, and the Azure portal instructions are platform-neutral.
Recommendations
- Alternate the order of PowerShell and CLI examples, or show CLI first for parity.
- Ensure that resource/sample links include Linux/CLI equivalents, not just PowerShell/Windows.
- Explicitly mention that all portal steps apply equally to Linux and macOS users.
- Add a 'See also' section with Linux/macOS-specific resources or troubleshooting tips.
Virtual Machines
Increase performance of Premium SSDs and Standard SSD/HDDs
.../articles/virtual-machines/disks-enable-performance.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 tasks, with Azure CLI (Linux/macOS friendly) presented first. However, the PowerShell section is extensive and uses Windows-centric scripting patterns, and the page metadata and custom tags (e.g., 'devx-track-azurepowershell') suggest a PowerShell/Windows bias. There are no explicit Linux/macOS shell examples (e.g., bash-only or zsh-only), nor are there any references to Linux-specific tools or workflows. The Azure CLI examples are generic and do not leverage Linux-specific features or discuss Linux nuances. The Azure portal instructions are platform-neutral.
Recommendations
- Add explicit bash/zsh examples for Linux/macOS users, especially for scripting and automation.
- Include notes on Linux-specific considerations (e.g., environment variables, shell differences, file permissions) when using Azure CLI.
- Balance PowerShell and CLI coverage by highlighting CLI as the cross-platform default and referencing PowerShell as an alternative for Windows users.
- Remove or balance metadata/tags that suggest PowerShell as the primary approach.
- Add troubleshooting or tips for Linux/macOS users where workflows may differ.
Virtual Machines
Create an incremental snapshot
...ticles/virtual-machines/disks-incremental-snapshots.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI (cross-platform) and Azure PowerShell (Windows-centric) examples for all major tasks, but consistently lists PowerShell examples immediately after CLI and gives them equal prominence. There are no Linux-specific shell examples (e.g., Bash-only idioms), and no mention of Linux-native tools or patterns. The CLI examples are generic and work on both Linux and Windows, but the PowerShell examples are Windows-specific and more verbose, potentially giving the impression of Windows as a first-class platform. No explicit Linux bias or missing Linux examples, but the parity could be improved.
Recommendations
- Add explicit Bash shell examples where appropriate, especially for scripting tasks, to demonstrate Linux-native usage.
- Clarify in introductory sections that Azure CLI commands work identically on Linux, macOS, and Windows.
- Consider listing CLI examples before PowerShell, and labeling PowerShell as Windows-centric.
- If possible, mention Linux tools (e.g., jq for JSON parsing) or patterns that Linux users might use in conjunction with Azure CLI.
- Add a note that PowerShell Core is available cross-platform, but most users on Linux will use Bash with Azure CLI.
Virtual Machines
Convert a disk from LRS to ZRS
...ain/articles/virtual-machines/disks-migrate-lrs-zrs.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation presents Azure Portal instructions first, which are platform-neutral, but then lists Azure PowerShell before Azure CLI in all code example sections. PowerShell is a Windows-centric tool, while Azure CLI is cross-platform. No Linux/macOS-specific tools or shell examples are provided, and PowerShell is given precedence over CLI, which may create friction for Linux/macOS users.
Recommendations
- List Azure CLI examples before Azure PowerShell in each section, as CLI is cross-platform and more familiar to Linux/macOS users.
- Explicitly mention that Azure CLI works on Linux/macOS and provide shell-specific notes where relevant.
- Consider including bash or shell script examples for common operations, especially in migration scenarios.
- Add a brief note about PowerShell Core availability on Linux/macOS if PowerShell examples are retained.
- Ensure links and references (such as 'Find and delete unattached disks') do not point only to Windows-specific pages.
Virtual Machines
Change the performance of Azure managed disks
...n/articles/virtual-machines/disks-performance-tiers.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides parallel examples for both Azure CLI and Azure PowerShell, but PowerShell (a Windows-centric tool) is given equal prominence and detail as Azure CLI. The use of PowerShell and references to its installation may create friction for Linux/macOS users, as PowerShell is less commonly used or pre-installed on those platforms. The documentation does not show explicit Linux shell examples (e.g., bash), and the ordering of examples sometimes places PowerShell before CLI. There are no Linux-specific commands or troubleshooting notes, and the portal instructions are platform-neutral.
Recommendations
- Clearly indicate that Azure CLI commands are cross-platform and preferred for Linux/macOS users.
- Provide bash-specific examples or notes for Linux users (e.g., variable syntax differences).
- Add troubleshooting notes for common Linux/macOS issues (e.g., CLI installation, environment variables).
- Consider listing Azure CLI examples before PowerShell, or grouping by platform relevance.
- Explicitly mention that PowerShell is available on Linux/macOS, but may require installation.
Virtual Machines
Restrict managed disks from being imported or exported
...tual-machines/disks-restrict-import-export-overview.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation page exhibits mild Windows bias. PowerShell and Windows-centric links are mentioned first in several sections, and references to custom RBAC roles point to PowerShell-based instructions. While CLI and Linux alternatives are present, they are often listed second or less prominently. The page also uses Windows/PowerShell terminology and links before Linux/CLI equivalents.
Recommendations
- Present CLI/Linux examples and links alongside or before Windows/PowerShell ones.
- Ensure references to custom roles include both PowerShell and CLI/ARM template methods, not just PowerShell.
- Use neutral language when referring to tools (e.g., 'Azure CLI or PowerShell' instead of 'PowerShell').
- Add explicit Linux/macOS instructions where only Windows/PowerShell is referenced.
- Review linked articles to ensure Linux parity in step-by-step guides.
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation demonstrates mild Windows bias in several areas. Windows-specific details (such as page file placement) are discussed more thoroughly and appear before Linux equivalents. PowerShell is mentioned explicitly for customer-managed keys, with Linux CLI only referenced secondarily. Examples and sizing guidance for Windows images are presented before Linux images, and some sections (like page file placement) only discuss Windows patterns. There is a lack of parity in example depth and tool coverage for Linux/macOS users.
Recommendations
- Ensure Linux and Windows examples are presented with equal prominence and detail, ideally side-by-side.
- Include explicit Linux/macOS command-line examples (e.g., Bash, Azure CLI) wherever PowerShell is referenced.
- Discuss Linux-specific disk/file system patterns (e.g., swap file placement) in sections that currently only mention Windows details.
- When mentioning tools or deployment methods (CLI, PowerShell, Portal), list Linux/macOS options first or equally.
- Add more Linux image sizing examples and clarify any differences in deployment or management for Linux VMs.
Virtual Machines
Azure Linux VM Agent Overview
...in/articles/virtual-machines/extensions/agent-linux.md
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_reference
windows_first
Summary
The documentation is overwhelmingly Linux-focused, as expected for the Azure Linux VM Agent. However, there are minor instances of Windows bias: Windows tools (putty.exe) are referenced when discussing SSH key compatibility, and a link to a Windows VM deployment tutorial is included in the Ubuntu Cloud Images section. These references may distract or confuse Linux users, but do not prevent Linux users from completing tasks.
Recommendations
- Remove or de-emphasize references to Windows tools (e.g., putty.exe) unless strictly necessary for cross-platform scenarios.
- Replace or supplement Windows VM deployment tutorial links with Linux equivalents when discussing Linux-specific configuration.
- Ensure that all example links and resources in Linux documentation are Linux-centric unless cross-platform context is required.
Virtual Machines
Azure Disk Encryption for Linux
...es/virtual-machines/extensions/azure-disk-enc-linux.md
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation is focused on Azure Disk Encryption for Linux and provides Linux-centric schema and deployment examples. However, in the warning section, the PowerShell cmdlet (Get-AzVMDiskEncryptionStatus) is mentioned before the Azure CLI equivalent (az vm encryption show), which may indicate a subtle Windows-first bias. The troubleshooting and support sections do not reference any Windows-specific tools or patterns, and the examples are all Linux-oriented.
Recommendations
- List the Azure CLI command before the PowerShell cmdlet when providing cross-platform instructions, as CLI is natively available on Linux/macOS.
- Explicitly state that both CLI and PowerShell are supported, and clarify which is recommended for Linux users.
- Consider providing Bash script examples for common operations, as Linux users are more likely to use Bash than PowerShell.
- Review other documentation links to ensure Linux tools and patterns are prioritized or at least equally represented.
Virtual Machines
Chef extension for Azure VMs
...blob/main/articles/virtual-machines/extensions/chef.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation covers both Linux and Windows, but exhibits subtle Windows bias. The publisher value ('Chef.Bootstrap.WindowsAzure') and extension type ('ChefClient' for Windows) are mentioned before Linux equivalents. There is no explicit Linux-specific deployment example (e.g., for Windows, a PowerShell path is shown, but for Linux, only a CLI example is given). Troubleshooting paths are shown for both OSes, but Windows is listed second. The documentation references Windows-specific naming conventions and tools (e.g., publisher name, extension type), and does not provide parity in example scripts or commands for Linux (e.g., no bash deployment example, only Azure CLI).
Recommendations
- Present Linux and Windows examples side-by-side, or alternate which OS is shown first.
- Provide explicit Linux deployment examples using bash scripts, not just Azure CLI.
- Clarify publisher and extension type values for both Linux and Windows in a more balanced way.
- Include Linux-specific troubleshooting steps and file paths before or alongside Windows equivalents.
- Review for any missing Linux-specific options or settings and document them if available.
Virtual Machines
Azure Machine Configuration (guest configuration)
...les/virtual-machines/extensions/guest-configuration.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides parity between Windows and Linux for all extension installation methods (Azure Portal, CLI, ARM/Bicep/Terraform templates), but consistently lists Windows examples and terminology before Linux equivalents in several places. The PowerShell section is included as a primary method, which is Windows-centric, while no Linux-native shell (e.g., Bash) examples are given. There is minor bias in ordering and tool emphasis, but Linux users are not blocked from completing any tasks.
Recommendations
- Alternate the order of Windows and Linux examples, or present Linux examples first in some sections.
- Include Bash or shell script examples for Linux users alongside PowerShell, especially for automation scenarios.
- Explicitly mention that PowerShell Core is cross-platform if recommending PowerShell for Linux users.
- Clarify in the portal instructions that both Windows and Linux extensions are available, and show screenshots or steps for both OS types.
- Add a section or note highlighting any Linux-specific considerations or troubleshooting tips.
Virtual Machines
Use Application Health extension with Azure Virtual Machines
...ticles/virtual-machines/extensions/health-extension.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_examples_first
Summary
The documentation consistently presents Windows-based examples before Linux equivalents, especially in REST API and PowerShell sections. PowerShell commands (Windows-centric) are given more prominence and detail, while Linux examples (using Azure CLI) are provided but always after Windows ones. The extension type naming is clear for both OSes, and Linux is supported throughout, but the ordering and emphasis favor Windows users.
Recommendations
- Alternate the order of examples so that Linux (Azure CLI) examples are shown first in some sections.
- Provide Bash script examples for Linux users where PowerShell scripts are shown for Windows.
- Add explicit notes clarifying parity and equivalence between Windows and Linux steps.
- Ensure troubleshooting and log file sections highlight Linux paths and commands as prominently as Windows ones.
- Consider grouping OS-specific instructions together or using tabs for OS selection to reduce perceived bias.
Virtual Machines
Qualys Cloud Agent Extension for Azure VMs
...ob/main/articles/virtual-machines/extensions/qualys.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides deployment instructions for both Windows and Linux VMs, generally maintaining parity between the two platforms. However, there is a notable emphasis on PowerShell as a deployment method, which is natively a Windows tool, even though a Linux PowerShell option is mentioned. In several sections, Windows instructions or links are listed before Linux equivalents, subtly prioritizing Windows. There are no missing Linux examples or exclusive use of Windows-only tools, but the ordering and tool emphasis reflect a mild Windows bias.
Recommendations
- Provide Bash or native Linux CLI examples alongside PowerShell for Linux deployments, as PowerShell is less common on Linux.
- Alternate the order of Windows and Linux instructions/links to avoid consistently listing Windows first.
- Explicitly mention and provide examples for Linux-native automation tools (e.g., Bash scripts, cloud-init) in addition to Ansible, Chef, and Puppet.
- Clarify when PowerShell is required on Linux and offer guidance for users who prefer native Linux tools.
Virtual Machines
Enable InfiniBand on HPC VMs - Azure Virtual Machines | Microsoft Docs
...icles/virtual-machines/extensions/enable-infiniband.md
Low Priority
View Details â
Detected Bias Types
windows_tools
powershell_heavy
windows_first
Summary
The documentation provides both Linux and Windows instructions for enabling InfiniBand, but there is a slight Windows bias in the VM extension section, where Azure PowerShell is mentioned as the primary tool for adding extensions, and Windows-specific extension details are given before Linux equivalents. Manual installation instructions are more detailed for Linux, but Windows users are directed to a download link without step-by-step guidance. The overall structure and examples are reasonably balanced, but Windows tools and patterns are referenced first or exclusively in some sections.
Recommendations
- Include Azure CLI and portal instructions for adding VM extensions, not just PowerShell.
- Present Linux and Windows extension details in parallel or with equal prominence.
- Provide step-by-step manual installation instructions for Windows, similar to the Linux example.
- Ensure Linux examples and tools are mentioned first or side-by-side with Windows equivalents.
Virtual Machines
InfiniBand driver extension - Azure Linux VMs
...al-machines/extensions/hpc-compute-infiniband-linux.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
Summary
The documentation is focused on Linux VMs and provides both Azure CLI and PowerShell examples for deploying the InfiniBand driver extension. However, PowerShell examples are given equal prominence to Azure CLI, despite PowerShell being a Windows-centric tool. There are multiple PowerShell examples (including for VMSS), but no Linux-native command-line examples (e.g., Bash, cloud-init, or ARM template deployment via Linux tools). Troubleshooting also references PowerShell first, and the support section mentions MSDN (Windows-centric) forums. There is a brief mention of a Windows extension, but no Windows-specific instructions are present.
Recommendations
- Prioritize Azure CLI examples over PowerShell, as Azure CLI is cross-platform and native to Linux/macOS.
- Add Bash or shell script examples for ARM template deployment from Linux environments.
- Clarify that PowerShell examples are optional and primarily for Windows users.
- Reference Linux-specific support channels or forums in addition to MSDN.
- Ensure troubleshooting steps highlight Azure CLI and Linux-native tools before PowerShell.
Virtual Machines
Azure virtual machine extensions and features
.../main/articles/virtual-machines/extensions/overview.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation presents both Linux and Windows information, but there is a subtle Windows bias. Windows tools (PowerShell) are mentioned alongside Azure CLI, and Windows troubleshooting is referenced first. In some sections, Windows examples or links are listed before Linux equivalents. The troubleshooting table is balanced, but the overall flow and tool mentions favor Windows slightly.
Recommendations
- Alternate the order of Linux and Windows references throughout the documentation to avoid consistently listing Windows first.
- Explicitly mention Linux tools (e.g., Bash, shell scripting) alongside PowerShell when discussing extension management.
- Provide example commands for both Linux and Windows environments in relevant sections, or link to parity examples.
- Ensure troubleshooting guidance is equally detailed and easy to find for both platforms.
- Consider a platform-neutral introduction before splitting into OS-specific details.
Virtual Machines
Project Flash - Advancing Azure Virtual Machine availability monitoring
.../blob/main/articles/virtual-machines/flash-overview.md
Low Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a mild Windows bias by referencing Windows-specific documentation first (e.g., scheduled events link points to a Windows path), and by omitting explicit Linux/macOS examples or references. No PowerShell-heavy or Windows-only tools are presented, but the lack of Linux parity in examples and links may create friction for non-Windows users.
Recommendations
- Provide parallel Linux/macOS documentation links where Windows-specific links are given (e.g., scheduled events for Linux VMs).
- Include example workflows or references for Linux VM monitoring, especially in sections discussing scheduled events and health events.
- Ensure that cross-platform tools (Azure CLI, REST API) are mentioned and exemplified alongside any Windows-centric tools.
- Review all linked articles to verify Linux parity and update this overview to explicitly mention Linux support where applicable.
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
recommended_windows
missing_mac_example
Summary
The documentation is generally cross-platform and includes Linux and Windows support throughout. However, there is a subtle Windows bias: Windows is listed first in several places, and Windows Server 2019 is specifically recommended for performance, while no Linux distribution is similarly highlighted. There are no macOS-specific examples or recommendations. Linux examples (e.g., lstopo output) are present, but Windows tools for topology are not mentioned, nor are Linux distributions recommended for performance.
Recommendations
- List Linux and Windows equally or alternate order in tables and recommendations.
- Recommend specific Linux distributions for performance, similar to Windows Server 2019.
- Include macOS notes or clarify its support status, if relevant.
- If recommending OS for performance, provide rationale and equivalent Linux guidance.
- Add Windows-specific topology tools (e.g., Coreinfo, Windows System Information) if lstopo is shown for Linux.
Virtual Machines
Azure VM Image Builder overview
...in/articles/virtual-machines/image-builder-overview.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
low_linux_example
Summary
The documentation generally presents both Windows and Linux support, but there are several areas where Windows tools, terminology, or examples are given first or exclusively. PowerShell is often mentioned before Azure CLI, and Windows-specific tools (e.g., Sysprep, Windows security baseline) are referenced without Linux equivalents. Linux examples and tools are present but sometimes secondary. There are no critical missing Linux instructions, but the overall tone and ordering subtly favor Windows.
Recommendations
- Ensure Linux and Windows examples are always presented in parallel, with equal prominence.
- When referencing Windows-specific tools (e.g., Sysprep, Windows security baseline), also mention Linux equivalents (e.g., waagent for deprovisioning, CIS Linux baselines).
- Alternate the order of Windows and Linux examples/tabs to avoid always listing Windows first.
- Expand references to Linux-specific configuration management tools (e.g., cloud-init, Ansible) where appropriate.
- Provide direct links to Linux baseline templates or best practices, similar to the Windows baseline template link.
Virtual Machines
Customer intent: As a system administrator, I want to restrict uploads and downloads for Azure managed disks using identity verification, so that I can enforce security policies and ensure only authorized users can access sensitive data.
...ines/includes/disks-azure-ad-upload-download-portal.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation presents PowerShell examples before Azure CLI examples in several sections, and references PowerShell as a primary method for role assignment and disk configuration. While Azure CLI is included, the ordering and emphasis may subtly favor Windows users, as PowerShell is a Windows-centric tool. No explicit Linux/macOS exclusion is present, but the pattern may create friction for non-Windows users.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples, as CLI is cross-platform.
- Explicitly mention that Azure CLI works on Linux/macOS and provide installation links.
- Add Bash or shell script examples where relevant.
- Clarify that all steps can be performed on Linux/macOS using Azure CLI.
- Avoid implying PowerShell is the default or preferred method unless necessary.
Virtual Machines
Customer intent: As a cloud administrator, I want to expand virtual machine disks efficiently, so that I can manage storage capacity without downtime and ensure optimal performance in my infrastructure.
...al-machines-disks-expand-without-downtime-restrictions.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation mentions both Azure CLI and Azure PowerShell as supported tools, but PowerShell (a Windows-centric tool) is listed before CLI, and Windows-specific instructions (such as the Windows rescan function) are referenced before Linux equivalents. The rescan instructions for Windows are slightly more detailed, and the link for Windows is to a Microsoft driver page, while the Linux link is to Azure documentation. There is a subtle prioritization of Windows tools and patterns.
Recommendations
- List cross-platform tools (Azure CLI) before Windows-specific tools (PowerShell) to avoid implicit prioritization.
- Ensure Linux and Windows instructions are equally detailed and prominent.
- Provide direct Linux command examples (e.g., using 'lsblk', 'partprobe', or 'echo 1 > /sys/block/sdX/device/rescan') alongside Windows examples.
- Include parity in troubleshooting steps for both platforms.
- Where possible, link to official Linux documentation or community resources for disk management.
Virtual Machines
Customer intent: As a cloud administrator, I want to benchmark disk performance using custom I/O workloads, so that I can optimize storage configurations for maximum read and write IOPS in my virtual machines.
...ncludes/virtual-machines-managed-disks-benchmarking.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation presents Windows benchmarking tool (DISKSPD) and its usage before introducing the Linux equivalent (FIO). The Windows tool is described in detail with command-line examples first, followed by the Linux tool. There is a clear separation between Windows and Linux sections, but Windows is prioritized in order and coverage. Both platforms have example commands and explanations, but Windows tools are mentioned and explained first.
Recommendations
- Present Linux (FIO) and Windows (DISKSPD) tools in parallel, or alternate their order in examples.
- Add a comparison table summarizing both tools, their installation, and usage for quick reference.
- Explicitly state platform applicability at the start of each section.
- Ensure equal depth of explanation and example coverage for both platforms.
- Consider including macOS guidance if applicable.
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Windows and Linux parity for the core installation steps, with CLI and ARM template examples that apply to both platforms. However, there is a subtle Windows bias: Windows screenshots are shown before Linux ones, and PowerShell examples (Windows-centric) are provided alongside CLI and ARM template, but no Linux shell-specific examples (e.g., Bash scripting) are included. The quickstart links for VM creation are presented with Windows first, then Linux. No critical Linux functionality is missing, but the ordering and example types favor Windows.
Recommendations
- Alternate the order of Windows and Linux screenshots, or present them side-by-side.
- Provide Bash shell scripting examples for Linux users alongside PowerShell examples.
- Present quickstart links for Windows and Linux together, or alternate their order.
- Explicitly state that CLI and ARM template examples are cross-platform and suitable for Linux/macOS users.
- Consider adding a Linux/macOS validation workflow (e.g., using SSH or Bash) for confirming extension installation.
Virtual Machines
Azure Instance Metadata Service for virtual machines
...articles/virtual-machines/instance-metadata-service.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Windows (PowerShell) and Linux (bash/curl) examples for all major usage scenarios, but consistently lists Windows/PowerShell examples before Linux equivalents. Troubleshooting and routing table sections also show Windows commands and outputs first, and use PowerShell for Azure CLI examples, even in Linux sections. There is a slight emphasis on Windows tools (PowerShell, route print, ipconfig) and patterns, with Linux alternatives provided but sometimes as secondary. No critical Linux gaps are present; all tasks can be completed on Linux.
Recommendations
- Alternate the order of Windows and Linux examples, or present Linux examples first in sections marked as 'linux-related-content'.
- Use cross-platform Azure CLI examples (az CLI) instead of PowerShell CLI in Linux troubleshooting sections.
- Where possible, provide more detailed Linux troubleshooting steps and outputs, matching the depth of Windows sections.
- Explicitly mention macOS compatibility in Linux examples, or provide macOS-specific notes where command syntax may differ.
- Review sample code and links to ensure parity in language and platform support.
Low Priority
View Details â
Detected Bias Types
windows_tools
powershell_heavy
windows_first
Summary
The documentation provides both Linux/macOS and Windows-specific instructions for connecting to a Linux VM via SSH. While Linux instructions are thorough and presented first, the Windows section relies heavily on PowerShell/Azure PowerShell for certain operations (such as obtaining the host fingerprint via the portal), and references Windows-specific tools (cmd.exe, PowerShell). There is a slight bias in that the Windows tab uses Azure PowerShell for host fingerprint validation, whereas the Linux tab uses direct SSH commands. However, both platforms are covered with parity in most core steps.
Recommendations
- Provide a direct, non-PowerShell method for Windows users to obtain the host fingerprint, such as using PuTTY or Windows-native OpenSSH.
- Include examples for popular Windows SSH clients (e.g., PuTTY) alongside PowerShell/cmd.exe.
- Clarify that Windows 10 and later include OpenSSH, and show how to use it in cmd.exe or PowerShell without requiring Azure PowerShell.
- Ensure troubleshooting steps and links are equally accessible and detailed for both platforms.
- Consider listing Linux/macOS instructions before Windows only if the majority of users are expected to be on those platforms, otherwise present both tabs equally.
Virtual Machines
Enable Azure Disk Encryption for Linux VMs
...les/virtual-machines/linux/disk-encryption-overview.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation is focused on enabling Azure Disk Encryption for Linux VMs and is generally Linux-centric. However, there is evidence of Windows bias in the form of frequent references to PowerShell and Azure PowerShell cmdlets, with PowerShell examples and quickstarts mentioned alongside (and sometimes before) Azure CLI equivalents. The 'Next steps' section lists both CLI and PowerShell quickstarts, and the terminology table includes 'PowerShell cmdlets' as a primary concept, despite the Linux focus. There are no missing Linux examples or exclusive references to Windows tools, but the prominence of PowerShell may create friction for Linux users who prefer native Linux tooling.
Recommendations
- Prioritize Azure CLI examples and quickstarts before PowerShell in all lists and sections, as CLI is more native to Linux environments.
- Clarify that PowerShell is cross-platform, but emphasize CLI as the recommended approach for Linux users.
- Remove or de-emphasize 'PowerShell cmdlets' from the terminology table unless specifically relevant to Linux users.
- Ensure that all scripts and examples are available in Bash/CLI format, and highlight these as the default for Linux documentation.
- Add a note explaining the differences between CLI and PowerShell usage on Linux, and recommend CLI for most users.
Virtual Machines
Expand Virtual Hard Disks on a Linux VM
...b/main/articles/virtual-machines/linux/expand-disks.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
Summary
The documentation is strongly focused on Linux, with all operational examples and procedures using Linux commands and tools. However, a single section at the end provides a PowerShell script for checking classic VM SKU support for expanding disks without downtime, with no equivalent Bash/Azure CLI example for Linux users.
Recommendations
- Provide an equivalent Bash/Azure CLI script for Linux users to check classic VM SKU support for expanding disks without downtime.
- Clarify whether the PowerShell script is only necessary for Windows users, or if Linux users should use an alternative method.
- If the check is relevant for Linux VM administrators, ensure parity by offering platform-agnostic or Linux-native instructions.
Virtual Machines
Configure LVM and RAID on encrypted devices - Azure Disk Encryption
...l-machines/linux/how-to-configure-lvm-raid-on-crypt.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both PowerShell and Azure CLI examples for VM deployment, disk attachment, and encryption steps, with PowerShell (Windows) examples consistently presented first. However, all OS-level configuration, LVM, and RAID instructions are Linux-specific, and no Windows-only tools or patterns are used for the core storage management tasks. The overall bias is minor and limited to the ordering and prominence of Windows-centric Azure management commands.
Recommendations
- Present Azure CLI (Linux/macOS-friendly) examples before PowerShell examples, or alternate the order to avoid implicit prioritization.
- Explicitly state that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Consider grouping Azure CLI and PowerShell examples together, or use tabs to allow users to select their preferred environment.
- Add a brief note clarifying that PowerShell examples are for users on Windows, while Azure CLI is recommended for Linux/macOS.
Virtual Machines
Verify encryption status for Linux - Azure Disk Encryption
...tual-machines/linux/how-to-verify-encryption-status.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
Although the documentation is targeted at Linux VMs, the PowerShell section is presented before the Azure CLI section, and PowerShell examples are extensive and detailed. This ordering and emphasis may create friction for Linux users, who are more likely to use Bash and Azure CLI. However, Linux-native commands (lsblk, cryptsetup) and Azure CLI examples are present and comprehensive, so Linux users can still complete all tasks.
Recommendations
- Move the Azure CLI section before the PowerShell section to prioritize Linux-friendly tooling.
- Add a note clarifying that PowerShell examples are primarily for users managing Linux VMs from Windows or cross-platform environments.
- Consider reducing the length and detail of PowerShell examples, or providing parity in Azure CLI/Bash examples.
- Explicitly state that all Azure CLI commands are intended for Bash or Linux shell environments.
- Highlight Linux-native commands and workflows (lsblk, cryptsetup) earlier in the document.
Virtual Machines
Quickstart - Create a Linux VM in the Azure portal
...articles/virtual-machines/linux/quick-create-portal.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Windows (PowerShell) and Linux/macOS (Bash) instructions for connecting to the VM via SSH, but Windows/PowerShell is mentioned first. The only explicit tool mentioned for Windows is PowerShell, while Bash is referenced for Linux/macOS. There are no missing Linux examples, and the overall flow is Linux-focused, but the order and explicit mention of PowerShell create minor Windows bias.
Recommendations
- Present Bash (Linux/macOS) and PowerShell (Windows) instructions in parallel or in tabs, rather than listing Windows first.
- Explicitly mention common Linux terminal emulators (e.g., GNOME Terminal, Konsole) and macOS Terminal when referencing Bash.
- Consider providing screenshots for both Windows and Linux/macOS terminal environments.
- Clarify that the SSH command works identically across platforms, and highlight any platform-specific steps (e.g., setting file permissions) in a dedicated section.
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation is primarily focused on Linux, but there are instances where Windows tools and patterns are mentioned before or in addition to Linux equivalents. Specifically, SSH usage from Windows is highlighted with a dedicated link, and Azure PowerShell examples (Windows-centric) are provided alongside Azure CLI. The reference to the Azure portal for creating NSG rules links to a Windows-specific quickstart. These sections may create minor friction for Linux/macOS users.
Recommendations
- Provide equivalent guidance for SSH usage from Linux/macOS, not just Windows.
- When referencing Azure portal documentation, link to Linux-specific or neutral guides rather than Windows-specific ones.
- Present Azure CLI (cross-platform) examples before Azure PowerShell (Windows-centric) examples, or clarify platform applicability.
- Ensure troubleshooting and next steps include parity for Linux/macOS users where Windows-specific instructions are given.
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_first
windows_reference
powershell_example
Summary
The documentation is focused on Linux VM time sync in Azure and provides thorough Linux-specific guidance and examples. However, it repeatedly references Windows Server 2016 improvements and links to Windows documentation before or in parallel with Linux explanations. There is a PowerShell example for base64 encoding cloud-init, but no Linux shell equivalent. The page does not provide Windows-only instructions, but Windows context and tooling are mentioned first or exclusively in some places.
Recommendations
- Move Windows-specific context and references to a background or separate section, focusing the main content on Linux.
- Provide a Linux shell (e.g., base64) example for encoding cloud-init, not just PowerShell.
- When referencing time sync improvements, highlight Linux-specific mechanisms first, and only mention Windows as underlying infrastructure if necessary.
- Ensure all examples and tooling instructions are available for Linux users, especially for tasks like ARM template preparation.
- Add parity in cross-references: link to Linux time sync documentation as prominently as Windows references.
Virtual Machines
Scheduled Events for Linux VMs in Azure
...in/articles/virtual-machines/linux/scheduled-events.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation is generally Linux-focused and provides Bash and Python examples, but PowerShell samples are consistently presented alongside or immediately after Bash, and in some cases before Python. In the 'Query for events' and 'Start an event' sections, PowerShell is given equal prominence to Bash, despite PowerShell being a Windows-centric tool (even though it is available on Linux, Bash is far more common in Linux environments). There is a slight 'windows_first' bias in the order of links and references, such as the 'Platform initiated maintenance' link using Windows breadcrumbs/toc, and PowerShell examples being shown before Python. No critical Linux examples are missing, and all tasks can be completed using Linux-native tools.
Recommendations
- Present Bash examples first in all code sample sections, followed by Python, and then PowerShell (if included at all).
- Clarify that PowerShell is optional and less common on Linux, and recommend Bash for Linux users.
- Ensure all internal links and breadcrumbs reference Linux documentation first when the page is Linux-focused.
- Consider adding more Linux-native tool examples (e.g., using wget or other CLI utilities) if relevant.
- Explicitly state that PowerShell is cross-platform but Bash is the default for Linux.
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates mild Windows bias by consistently listing Windows tools (PowerShell) before Linux equivalents (CLI), referencing 'Scheduled Events for Windows' before Linux, and providing links to Windows-specific pages first. There are no explicit Linux command examples or Linux-first instructions, and PowerShell is mentioned as a primary tool for managing maintenance, which may create friction for Linux users.
Recommendations
- Alternate the order of CLI and PowerShell references so that Linux tools are sometimes listed first.
- Provide explicit Linux command examples and walkthroughs, not just links.
- Ensure that references to 'Scheduled Events' and other features mention Linux and Windows equally, or use neutral phrasing.
- Add direct links to Linux-specific documentation where appropriate, and clarify parity between Windows and Linux features.
- Consider including bash or shell script examples alongside PowerShell.
Virtual Machines
Export an image version to a managed disk
...es/virtual-machines/managed-disk-from-image-version.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation presents both Azure CLI and PowerShell examples for exporting an image version to a managed disk. However, the PowerShell section is given equal prominence to the CLI, despite PowerShell being primarily a Windows-centric tool. The CLI examples use Bash-style syntax, which is cross-platform, but the PowerShell examples are detailed and extensive, potentially signaling a Windows-first approach. There are no Linux-specific tools or shell examples (e.g., Bash scripts), nor is there any mention of macOS. The CLI section is presented first, which helps mitigate bias, but the inclusion and detail of PowerShell examples may create friction for Linux/macOS users unfamiliar with PowerShell.
Recommendations
- Clarify that Azure CLI commands work on Linux, macOS, and Windows, and are the recommended cross-platform approach.
- Consider adding Bash script examples or notes for Linux/macOS users.
- Explicitly state PowerShell is optional and primarily for Windows users.
- Add a note about Azure CLI installation and usage on Linux/macOS.
- Ensure parity in example depth and explanation between CLI and PowerShell sections.
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation presents the Windows ARM template example before the Linux example, despite both being equally supported. No Windows-specific tools, PowerShell commands, or exclusive patterns are present, and both platforms have full template parity. However, the ordering may subtly signal a Windows preference.
Recommendations
- Present Windows and Linux examples in parallel or alternate the order in different sections.
- Explicitly state that both Windows and Linux are equally supported.
- Consider adding a summary table comparing key differences between the templates for both platforms.
Virtual Machines
Azure Dedicated Host SKU Retirement Migration Guide
...l-machines/migration/dedicated-host-migration-guide.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides examples for stopping and starting VMs using PowerShell, CLI, and Portal. PowerShell (a Windows-centric tool) is listed first in each case, followed by CLI and Portal. No explicit Linux/macOS bias is present, but the ordering gives Windows tools priority, which may subtly signal preference for Windows users.
Recommendations
- Rotate the order of example tabs so CLI (cross-platform) appears first, or list CLI before PowerShell to emphasize platform neutrality.
- Explicitly state that Azure CLI works on Windows, Linux, and macOS, and provide installation links for each platform.
- Add brief notes or links for Bash scripting or other Linux-native tools if relevant.
- Ensure that all referenced commands and guides are equally accessible and clear for Linux/macOS users.
Virtual Machines
Monitor Azure Virtual Machines
...docs/blob/main/articles/virtual-machines/monitor-vm.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation page demonstrates mild Windows bias. Windows terminology (e.g., 'Windows events', IIS logs) is mentioned before Linux equivalents (Syslog, SNMP), and Windows-specific tools (Performance Diagnostics, IIS logs) are highlighted. The troubleshooting section links primarily to Windows documentation, and examples or recommendations often mention Windows first or in more detail. Linux is supported, but coverage is less detailed and sometimes secondary.
Recommendations
- Ensure Linux examples and terminology (e.g., Syslog, SNMP, Apache/Nginx logs) are presented alongside or before Windows equivalents.
- Provide equal detail for Linux troubleshooting tools and workflows, including direct links to Linux-specific documentation.
- Include Linux/macOS screenshots and walkthroughs in sections describing portal or agent onboarding.
- Clarify parity in supported features (e.g., which logs, metrics, and diagnostics are available for Linux VMs).
- Add explicit examples for configuring monitoring and alerts on Linux VMs, not just Windows.
Virtual Machines
Move a maintenance configuration to another Azure region
...tual-machines/move-region-maintenance-configuration.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation repeatedly mentions PowerShell before CLI when describing how to create, assign, and delete maintenance configurations. This ordering subtly prioritizes Windows tooling. However, CLI examples are present and shown in detail, including in the main workflow, which supports Linux/macOS users. No exclusively Windows-only tools or missing Linux examples are found.
Recommendations
- List CLI before PowerShell in instructions, as CLI is cross-platform and preferred by many Linux/macOS users.
- Explicitly note that CLI commands work on Linux/macOS and Windows.
- Add Bash or shell script examples where appropriate to further support Linux users.
- Consider a dedicated section for Linux/macOS users if any platform-specific caveats exist.
Virtual Machines
Overview of virtual machines in Azure
...e-docs/blob/main/articles/virtual-machines/overview.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation generally maintains parity between Windows and Linux, but there are several instances of Windows bias. PowerShell is frequently mentioned and listed before Azure CLI in tables describing how to query locations and VM images, and Windows tools (PowerShell) are often referenced alongside or before Linux-friendly tools (CLI). Some examples and instructions are presented in a Windows-first order, and PowerShell is sometimes given more detailed coverage than CLI. However, Linux-specific sections and links are present, and Linux is clearly supported.
Recommendations
- List Azure CLI and Linux examples before or alongside PowerShell examples in tables and instructions.
- Ensure that all examples and instructions are provided for both CLI and PowerShell, with equal detail.
- Highlight Linux-specific management tools and workflows where relevant.
- Add explicit Linux/macOS command-line examples where only PowerShell is shown.
- Review ordering in tables and lists to avoid consistently putting Windows/PowerShell first.
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for checking vCPU quotas, but the PowerShell example is presented second and is Windows-specific. There is a slight bias towards Windows by including PowerShell as a dedicated example tab, which is only relevant for Windows users, while Linux/macOS users are limited to the Azure CLI. No Linux-specific tools or shell examples are given, and PowerShell is presented as an equal alternative despite its platform specificity.
Recommendations
- Explicitly note that PowerShell is Windows-only and Azure CLI is cross-platform.
- Add Bash or shell script examples for Linux/macOS users where relevant.
- Consider listing CLI examples first, as they are cross-platform.
- If PowerShell Core is supported on Linux/macOS, clarify this and provide installation instructions or usage notes.
Virtual Machines
Isolated Image Builds for Azure VM Image Builder
...chines/security-isolated-image-builds-image-builder.md
Low Priority
View Details â
Detected Bias Types
windows_tools
powershell_heavy
windows_first
Summary
The documentation page demonstrates mild Windows bias primarily in its instructions for registering the Microsoft.ContainerInstance provider, where both Azure CLI and PowerShell commands are given, but PowerShell is mentioned second. The use of PowerShell as an example tool and the lack of explicit Linux shell (bash) or macOS instructions may create minor friction for non-Windows users. However, the rest of the documentation is platform-neutral, focusing on Azure concepts and resources without OS-specific tooling or examples.
Recommendations
- Include bash (Linux/macOS) equivalents for all command-line instructions, especially for resource provider registration.
- Explicitly mention that Azure CLI works cross-platform and provide examples for Linux/macOS users.
- Where PowerShell is referenced, clarify its availability on Linux/macOS or provide alternative commands.
- Review troubleshooting and best practices links to ensure Linux/macOS parity in examples and instructions.
Virtual Machines
Share Resources in Azure Compute Gallery
...s/blob/main/articles/virtual-machines/share-gallery.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides examples for Azure Portal, Azure CLI, and PowerShell. While Azure CLI is cross-platform, PowerShell is primarily associated with Windows, and its inclusion as a dedicated example may signal a Windows bias. Additionally, PowerShell examples are given equal prominence to CLI, and there are no Linux/macOS-specific shell examples (e.g., Bash scripts), nor is there mention of Linux-specific considerations. The ordering of examples (Portal, CLI, then PowerShell) is standard, but the presence of PowerShell without a Linux shell equivalent suggests a mild Windows bias.
Recommendations
- Add explicit Bash or shell script examples for Linux/macOS users, especially for tasks involving Azure CLI.
- Clarify that Azure CLI commands work on Linux/macOS and Windows equally.
- Consider mentioning cross-platform compatibility in the introduction to reassure non-Windows users.
- If PowerShell is included, note that PowerShell Core is available on Linux/macOS, or provide equivalent Bash commands.
Virtual Machines
Dldsv6 size series (Preview)
...irtual-machines/sizes/general-purpose/dldsv6-series.md
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page is largely platform-neutral, focusing on VM specifications and features. However, the only specific tooling mentioned for network performance testing is NTTTCP, a Microsoft-developed tool that is primarily Windows-focused (though it does have a Linux port, this is not mentioned). Additionally, the link for nested virtualization support points to a Windows/Hyper-V guide, with no mention of KVM or Linux equivalents. No Linux/macOS-specific tools or examples are provided, and Windows references appear first or exclusively in these cases.
Recommendations
- Explicitly mention Linux-compatible tools for bandwidth testing, such as iperf3, and provide links to their usage.
- For nested virtualization, clarify Linux support and link to relevant KVM documentation if supported.
- Where tooling is referenced, provide both Windows and Linux/macOS options, or clarify cross-platform availability.
- Add notes or examples for Linux/macOS users where applicable, especially in sections referencing tools or features that may differ by OS.
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page is generally platform-neutral, focusing on VM size specifications and features. However, there is mild Windows bias in the 'Feature support' section, where 'Nested Virtualization' links only to a Windows/Hyper-V guide, and in the 'Network' section, where bandwidth testing references NTTTCP, a tool originally developed for Windows. There are no Linux-specific examples, tools, or links, and Windows terminology appears first or exclusively in these contexts.
Recommendations
- Include links or references to Linux/KVM nested virtualization documentation if supported or clarify if only Windows is supported.
- Mention Linux-compatible bandwidth testing tools (e.g., iperf, netperf) alongside NTTTCP, and provide relevant links.
- Where features/tools are Windows-only, explicitly state Linux support status to avoid ambiguity.
- Add Linux-specific optimization guidance or examples where relevant.
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page is largely platform-neutral, focusing on VM specifications and features. However, there is mild Windows bias in the 'Feature support' section, where 'Nested Virtualization' links to a Windows-specific (Hyper-V) guide, and in the 'Bandwidth/Throughput testing' section, which references NTTTCPâa Microsoft tool most commonly used on Windows. No Linux-specific examples, tools, or links are provided, and Windows tools/patterns are mentioned before Linux equivalents (if any).
Recommendations
- Include links to Linux-specific nested virtualization documentation (e.g., KVM/QEMU guides) alongside the Windows Hyper-V link.
- Mention and link to Linux-compatible network throughput testing tools (e.g., iperf, netperf) in the networking section.
- Ensure that any referenced tools or guides are available and documented for both Windows and Linux platforms.
- Where features differ by OS (e.g., disk encryption), provide clear guidance and parity in documentation for both Windows and Linux users.
Virtual Machines
NC_RTXPRO6000BSE_v6 size series
...s/sizes/gpu-accelerated/nc-rtxpro6000-bse-v6-series.md
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page is largely neutral and platform-agnostic, focusing on VM sizes and hardware specifications. However, there is mild Windows bias in the 'Feature support' section, which links to Windows-specific nested virtualization documentation before mentioning Linux, and in the networking sections, which reference NTTTCP (a Windows tool) for bandwidth testing without mentioning Linux alternatives. No command-line examples are present, so there is no Powershell or CLI bias.
Recommendations
- When referencing tools like NTTTCP, explicitly mention Linux alternatives (e.g., iperf, netperf) and provide links to relevant documentation.
- In feature support lists, present Windows and Linux features in parallel, or mention Linux first where appropriate.
- If discussing nested virtualization, include links to both Windows and Linux guides, or clarify platform applicability.
- Ensure that any future examples or instructions include both Windows and Linux variants.
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page is largely platform-neutral, focusing on VM specifications and features. However, there is mild Windows bias in the 'Feature support' section, where 'Nested Virtualization' links only to a Windows/Hyper-V guide, and in the 'Network' section, where the recommended bandwidth/throughput testing tool (NTTTCP) is a Windows-centric utility. Linux equivalents or guidance are not provided, and Windows terminology/tools are mentioned first or exclusively in these contexts.
Recommendations
- For 'Nested Virtualization', add or link to Linux/KVM nested virtualization documentation if supported, or clarify platform limitations.
- In the 'Network' section, mention Linux-compatible bandwidth testing tools (e.g., iperf, netperf) alongside NTTTCP, and provide links to relevant Linux usage guides.
- Where features/tools are Windows-only, explicitly state platform restrictions and suggest Linux alternatives or workarounds.
- Review all feature support links to ensure Linux parity and add Linux-specific documentation where missing.
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page is largely neutral and platform-agnostic, but there are subtle signs of Windows bias. The only tool mentioned for bandwidth/throughput testing is NTTTCP, which is a Windows-centric tool (though it has a Linux port, it's less commonly referenced in Linux documentation). Additionally, the link for nested virtualization support points to a Windows-specific guide, and the order of mentioning Azure Disk Encryption lists Linux after Windows. However, all VM features and specifications are presented equally for both Linux and Windows, and most resources are generic.
Recommendations
- Include Linux-native tools for bandwidth/throughput testing (e.g., iperf3, netperf) alongside NTTTCP, with links to relevant guides.
- When referencing nested virtualization, provide links to both Windows and Linux documentation (if available), or clarify platform support.
- Ensure parity in listing feature support and restrictions for both Linux and Windows, and avoid listing Windows features first unless justified.
- Add explicit examples or troubleshooting steps for both Linux and Windows where OS-specific requirements (e.g., NVMe driver support) are mentioned.
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page is largely platform-neutral, focusing on VM specifications and features. However, there is mild Windows bias in the 'Feature support' section, where 'Nested Virtualization' links to a Windows-specific Hyper-V guide, and in the 'Network' section, where bandwidth testing references NTTTCPâa Windows-centric toolâwithout mentioning Linux alternatives. Windows terminology/tools are mentioned before Linux equivalents, and Linux-specific guidance is minimal.
Recommendations
- Provide equivalent Linux documentation links for nested virtualization (e.g., KVM/QEMU guides).
- Mention and link to Linux-compatible network bandwidth testing tools (e.g., iperf, netperf) alongside NTTTCP.
- Ensure that feature support and troubleshooting notes reference both Windows and Linux resources where applicable.
- Clarify in notes or tables when features/tools are Windows-only and suggest Linux alternatives.
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation is largely platform-neutral, focusing on VM specifications and features. However, there is mild Windows bias in the 'Feature support' section, where the link for Nested Virtualization points to a Windows/Hyper-V guide, and in the 'Network' section, where bandwidth testing references NTTTCP, a tool originally Windows-centric. Windows and Linux disk encryption support are listed together, but the nested virtualization and network testing resources favor Windows first.
Recommendations
- Include links to Linux/KVM nested virtualization documentation if relevant for Azure VMs.
- Mention Linux equivalents for network bandwidth testing (e.g., iperf, netperf) alongside NTTTCP.
- Where possible, provide parity in external documentation links for both Windows and Linux.
- Clarify that features/tools apply to both platforms, or note any platform-specific limitations.
Virtual Machines
Mdsv3 Very High Memory size series
...al-machines/sizes/memory-optimized/mdsv3-vhm-series.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation lists compatible OS images for the Mdsv3-VHM-series with Windows Server mentioned first, followed by Linux distributions. No command-line examples, tooling, or operational instructions are provided, so there is no evidence of Powershell-heavy or Windows-tools bias. The only minor bias is the ordering of Windows before Linux in the compatibility list.
Recommendations
- List Linux distributions before or alongside Windows in compatibility sections to avoid implying Windows primacy.
- Explicitly state that all features and instructions apply equally to Linux and Windows unless there are OS-specific caveats.
- If future documentation adds operational examples, ensure parity by providing both Linux (bash/CLI) and Windows (PowerShell) instructions.
Virtual Machines
Troubleshoot problems with shared images in Azure
...cles/virtual-machines/troubleshooting-shared-images.md
Low Priority
View Details â
Detected Bias Types
windows_tools
powershell_heavy
windows_first
Summary
The documentation references both Azure CLI and PowerShell for troubleshooting, but explicitly mentions the PowerShell '-Debug' switch alongside the CLI '--debug' switch. PowerShell is a Windows-centric tool, and its mention may imply a Windows-first approach. No Linux/macOS-specific troubleshooting tools or shell examples are provided, and PowerShell is listed before any Linux shell alternatives. There are no explicit Linux/macOS command examples, nor is Bash or other Unix shell troubleshooting discussed.
Recommendations
- Add explicit Bash or shell examples for Linux/macOS users, such as using Azure CLI in Bash with '--debug'.
- Clarify that PowerShell is optional and provide parity for Linux/macOS troubleshooting workflows.
- Mention cross-platform alternatives to PowerShell, such as Bash or zsh, and provide equivalent troubleshooting steps.
- Ensure that references to tools are ordered neutrally or with cross-platform tools first (e.g., Azure CLI before PowerShell).
Virtual Machines
Trusted Launch for Azure VMs
.../blob/main/articles/virtual-machines/trusted-launch.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
windows_heavy_references
Summary
The documentation page for Trusted Launch for Azure VMs is generally cross-platform, but exhibits mild Windows bias. Windows examples and references (such as ARM templates for Windows VMs) are listed before Linux equivalents, and links to Windows-specific documentation (e.g., Secure Boot, TPM, VBS, Credential Guard) are more prevalent. Some sections, such as Virtualization-based Security and vTPM, reference Windows features and tools without mentioning Linux equivalents or alternatives. However, Linux support is clearly indicated, and Linux-specific notes (e.g., Secure Boot and driver installation) are present.
Recommendations
- Provide Linux-focused deployment examples (e.g., ARM templates for Linux VMs) alongside Windows examples.
- Include references to Linux documentation for Secure Boot, TPM, and attestation, not just Windows links.
- Mention Linux alternatives or equivalents for features like Virtualization-based Security and Credential Guard, or clarify their applicability.
- Ensure that examples and references are balanced between Windows and Linux, or alternate their order.
- Add more explicit guidance for Linux users in sections that currently focus on Windows tools or features.
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation demonstrates a mild Windows bias. Windows tools and terminology (such as PowerShell and Windows signature templates) are mentioned alongside or before Linux equivalents. In scenario 3, 'MicrosoftWindowsTemplate' is listed as a signature template, but there is no explicit mention of Linux-specific templates. The instructions for creating gallery and image definition resources list 'Azure portal, PowerShell, CLI, or REST API', with PowerShell (Windows-centric) mentioned before CLI (cross-platform). However, Linux verification commands (mokutil) and useful links for Linux distributions are provided, showing some effort toward Linux parity.
Recommendations
- List Azure CLI before PowerShell when describing cross-platform workflows.
- Explicitly mention Linux-specific signature templates if available, or clarify their absence.
- Provide example workflows using Linux tools (e.g., OpenSSL) for certificate/key creation.
- Include Linux/macOS-specific instructions for gallery/image resource creation, if they differ.
- Clarify that all steps can be performed on Linux/macOS where applicable.
Low Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation generally addresses both Linux and Windows VMs, but there is a subtle Windows bias: in the 'Reduce downtime' section, scheduled events for Linux are mentioned after Windows, and no concrete examples or commands are provided for either platform. There is also a lack of platform-specific guidance or parity in examples, which could leave Linux users seeking more actionable information.
Recommendations
- Present Linux and Windows examples side-by-side, or alternate which platform is mentioned first.
- Provide concrete examples or links for both Linux and Windows (e.g., sample scripts for handling scheduled events on each OS).
- Ensure that any platform-specific tools or procedures are described equally for both Linux and Windows.
- Explicitly mention any differences in handling reboots or downtime between Linux and Windows VMs.
Virtual Machines
Overview of Maintenance control for OS image upgrades on Azure Virtual Machine Scale Sets
...ines/virtual-machine-scale-sets-maintenance-control.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page shows a Windows bias by listing Azure PowerShell as the first management option and highlighting PowerShell in the 'Next steps' section, while Linux-friendly tools like Azure CLI are mentioned but not emphasized. No Linux/macOS-specific examples or guidance are provided.
Recommendations
- Provide equal prominence to Azure CLI in both the management options and next steps sections.
- Include direct links to CLI-based walkthroughs or examples for Linux/macOS users.
- Add a note clarifying that all features are available via CLI and portal, and mention platform compatibility.
- Rotate or randomize the order of management options to avoid implicit prioritization.
Virtual Machines
VM Snapshot extension using VM restore points
...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/virtual-machines-restore-points-vm-snapshot-extension.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation page demonstrates a mild Windows bias by referencing Windows-specific technologies (VSS) and listing Windows examples and tools before their Linux equivalents. While Linux is mentioned and supported, Windows terminology and troubleshooting steps are more prominent.
Recommendations
- Present Windows and Linux information in parallel, rather than listing Windows first.
- Expand Linux-specific troubleshooting guidance, including common issues with pre-/post-scripts.
- Provide equal detail for both VMSnapshot Windows and Linux extensions, including links to Linux-specific documentation.
- Clarify the Linux restore point process, especially how application consistency is achieved.
- Include Linux-first or cross-platform examples where possible.
Virtual Machines
Copy VM restore points to another region
...achines/virtual-machines-copy-restore-points-how-to.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation is largely platform-neutral in its API focus, but there is a subtle Windows bias in the ordering and detail of configuration examples. Windows-specific configuration fields (such as 'windowsConfiguration', 'winRM', 'additionalUnattendContent', and 'certificateStoreName on Windows') are described first and in greater detail than their Linux equivalents. Linux configuration is present but less detailed and always follows Windows fields. Some fields (e.g., 'certificateStore') are labeled as Windows-only, with no Linux alternative or explanation.
Recommendations
- Present Linux and Windows configuration examples with equal detail and in parallel, rather than listing Windows first.
- Clarify which fields are Windows-only and provide Linux alternatives or explicitly state when a feature is not available for Linux.
- Expand Linux configuration documentation to match the depth provided for Windows (e.g., provide examples for customData, SSH options, and disk restore points).
- Add explicit notes or tables comparing Windows and Linux restore point behaviors and supported features.