1359
Pages Scanned
298
Pages Flagged
1359
Changed Pages
21.9%
% Pages Flagged
Scan Information
Started At: 2026-01-13 06:17:07
Finished At: 2026-01-13 06:27:08
Status: completed
Target Repo: Azure
Current Phase: discovery
Files Queued: 1359
Files Completed: 1359
Problematic Pages
298 issues found
Automation
Get started with Azure Automation State Configuration
.../articles/automation/automation-dsc-getting-started.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
powershell_heavy
Summary
The documentation page exhibits a strong Windows bias. All configuration examples use Windows PowerShell DSC syntax and resources (e.g., WindowsFeature IIS), with no Linux equivalents or cross-platform examples. The only VM creation link is for Windows, and references to DSC documentation and resources are Windows-centric. Linux support is only mentioned in passing, and there are no Linux-specific instructions, examples, or resource references.
Recommendations
- Add Linux DSC configuration examples, such as managing Linux packages or services using cross-platform DSC resources.
- Include links to Linux VM creation guides alongside Windows VM creation instructions.
- Reference Linux-specific DSC documentation and resources where applicable.
- Clarify current support status for Linux DSC, especially given the retirement announcement, and provide migration or alternative guidance for Linux users.
- Present examples for both Windows and Linux side-by-side, or indicate platform-specific steps clearly.
Create Pull Request
App Service
Managed Instance on App Service overview (preview)
...main/articles/app-service/overview-managed-instance.md
High Priority
View Details â
Detected Bias Types
windows_only
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation is heavily biased toward Windows, with all examples, configuration options, and tooling (PowerShell, registry, MSI, IIS, RDP) being Windows-specific. There is no mention of Linux equivalents, and the platform is explicitly stated as Windows-only. Linux users are excluded from using this feature, and no guidance is provided for Linux or cross-platform scenarios.
Recommendations
- Clearly state at the top that Managed Instance is Windows-only and provide links to Linux/container alternatives.
- Add a comparison table or section highlighting feature parity and differences between Windows Managed Instance and Linux App Service plans.
- Offer migration guidance for Linux users, including recommended hosting options and how to achieve similar isolation/customization.
- If future Linux support is planned, mention roadmap or alternatives.
- Ensure that documentation for related features (e.g., configuration scripts, storage mounts) includes Linux/container examples where applicable.
Artifact Signing
Sign a CI policy by using Artifact Signing
...ain/articles/artifact-signing/how-to-sign-ci-policy.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, requiring Azure PowerShell and providing only PowerShell-based examples with Windows-style file paths. Prerequisites and instructions assume a Windows environment, with no mention of Linux/macOS alternatives or cross-platform usage. The deployment section exclusively references Windows Defender Application Control, further reinforcing the Windows-centric approach.
Recommendations
- Provide equivalent instructions and examples for Linux/macOS users, including bash or shell commands where possible.
- Clarify whether Az.TrustedSigning and related modules can be used on non-Windows platforms, and document installation steps for those platforms.
- Use cross-platform file path examples or note differences for Linux/macOS (e.g., /tmp/root.cer).
- Include guidance for signing and deploying CI policies in non-Windows environments, if supported.
- Add links to relevant Linux/macOS documentation or tools, if available.
Artifact Signing
Set up signing integrations to use Artifact Signing
...ticles/artifact-signing/how-to-signing-integrations.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, with all detailed setup instructions and examples tailored exclusively for Windows environments. It relies on Windows-specific tools (SignTool.exe, MSI installers, winget, PowerShell), and does not provide equivalent instructions or examples for Linux or macOS users. Linux/macOS users are left without guidance for setting up Artifact Signing, especially for the SignTool integration.
Recommendations
- Provide explicit instructions for Linux/macOS users, including supported signing tools and setup steps.
- Include examples for cross-platform tools (e.g., OpenSSL, osslsigncode, or platform-agnostic SDK usage) where possible.
- If SignTool is Windows-only, clarify alternative signing workflows for Linux/macOS users using Artifact Signing SDK or other integrations.
- List Linux/macOS compatible installers and commands (e.g., .NET runtime installation via apt, yum, or brew).
- Ensure parity in authentication and configuration examples for non-Windows platforms.
Artifact Signing
Device Guard Signing Service migration to Artifact Signing
...gning/how-to-device-guard-signing-service-migration.md
High Priority
View Details â
Detected Bias Types
windows_tools
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation is heavily Windows-centric, with all examples, tools, and instructions tailored exclusively for Windows environments. It references Windows-specific directories, PowerShell cmdlets, and tools like SignTool and MSIX Packaging Tool, with no mention of Linux or macOS equivalents or workflows. The migration and deployment steps assume Windows OS and do not provide guidance for cross-platform scenarios.
Recommendations
- Add explicit notes about platform support and limitations, clarifying whether Artifact Signing and CI policies are Windows-only or if Linux/macOS are supported.
- If Linux/macOS support exists, provide equivalent instructions for those platforms, including directory paths, command-line tools, and deployment steps.
- Where PowerShell is used, offer Bash or shell script alternatives for Linux/macOS users.
- Reference cross-platform signing tools if available, or clarify that SignTool and MSIX Packaging Tool are Windows-only.
- Restructure examples to either be platform-neutral or to present Linux/macOS instructions alongside Windows ones, rather than Windows-first.
- Include troubleshooting and verification steps for non-Windows platforms if supported.
Automation
Create modular runbooks in Azure Automation
.../main/articles/automation/automation-child-runbooks.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation is heavily focused on PowerShell and Windows-centric tools and patterns. All examples use PowerShell syntax and cmdlets, with explicit references to Windows PowerShell and the Az.Automation module. There are no examples or guidance for Linux/macOS users, such as using Python runbooks or Bash scripts, nor is there mention of cross-platform alternatives. Windows tools and terminology are used exclusively and presented first, making it difficult for non-Windows users to follow or adapt the instructions.
Recommendations
- Add examples for Python and/or Bash runbooks, which are supported in Azure Automation and commonly used on Linux/macOS.
- Clarify which features and cmdlets are cross-platform and which are Windows-only.
- Provide equivalent instructions and code samples for Linux/macOS environments, including authentication and context management.
- Explicitly state platform limitations and offer links to platform-specific documentation where appropriate.
- Reorder examples or provide parallel examples so that Windows and Linux/macOS users are equally supported.
Automation
Compile DSC configurations in Azure Automation State Configuration
...lob/main/articles/automation/automation-dsc-compile.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, with all code examples and tooling references using Windows PowerShell and Windows-centric paths. There are no Linux/macOS-specific examples, nor any mention of cross-platform alternatives for compiling DSC configurations. Windows tools and patterns are presented exclusively and before any mention of Linux, and the only compilation methods described are via the Azure portal or Windows PowerShell.
Recommendations
- Add explicit notes about Linux/macOS support status for DSC compilation in Azure Automation.
- If Linux/macOS compilation is supported, provide equivalent examples using cross-platform PowerShell Core (pwsh) and clarify any differences.
- Include sample paths and commands for Linux/macOS environments where applicable.
- Mention any limitations or retirement of Linux DSC support more prominently and link to migration guidance.
- If Windows-only is intentional due to platform support, clarify this at the top of the article to set expectations for non-Windows users.
Automation
Work with Azure Desired State Configuration extension version history
...rticles/automation/automation-dsc-extension-history.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
powershell_heavy
windows_tools
Summary
The documentation exclusively covers Windows operating systems, PowerShell, and Windows Management Framework (WMF) in all examples and version histories. There is no mention of Linux or macOS support, nor are there examples or instructions for non-Windows platforms. The only reference to Linux is an end-of-life/retirement announcement, further reinforcing the Windows-centric focus.
Recommendations
- Clearly state the current support status for Linux/macOS, including any retirement or alternative solutions.
- If Linux support is deprecated, provide links or guidance for users migrating from Linux DSC to supported alternatives (e.g., Azure Automation, Ansible, Chef, etc.).
- If any versions previously supported Linux, include those in the version history and document their features and limitations.
- Add a section comparing Windows and Linux DSC extension capabilities, even if only for historical context.
- Provide migration guides or FAQs for Linux users affected by the retirement.
Automation
Set up Azure Automation continuous deployment with Chocolatey
...in/articles/automation/automation-dsc-cd-chocolatey.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, with all examples, configuration scripts, and tooling (Chocolatey, PowerShell DSC, WindowsFeature, xNetworking, etc.) being Windows-specific. There is no guidance or example for Linux or macOS users, and Linux support is explicitly deprecated. The workflow, commands, and package management are all tailored to Windows, making it difficult or impossible for Linux users to follow or adapt the instructions.
Recommendations
- Clearly state at the beginning that the guide is Windows-only and Linux support is deprecated.
- Provide links to equivalent Linux workflows (e.g., using apt, yum, or native Azure Automation alternatives for Linux) if available.
- If Azure Automation State Configuration for Linux is retired, suggest alternative Azure solutions for Linux configuration management (such as Azure VM extensions for custom scripts, or third-party tools like Ansible, Chef, or Puppet).
- Add a section comparing Windows and Linux approaches to continuous deployment in Azure, highlighting current limitations and alternatives.
- Remove or update references that imply cross-platform support where it no longer exists.
Automation
Create configurations from existing servers for Azure Automation State Configuration
...ticles/automation/automation-dsc-config-from-server.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. It only references Windows PowerShell 5.1, PowerShell DSC, and Windows-specific tools like SharePointDSC and ReverseDSC, with no Linux/macOS equivalents or examples. Linux is mentioned only in a link, with no guidance or parity for non-Windows users.
Recommendations
- Add explicit guidance or examples for Linux/macOS users, such as using DSC for Linux or alternative configuration management tools.
- Clarify whether ReverseDSC or similar extraction tools exist for Linux environments, or state the limitation clearly.
- Provide Linux/macOS command-line examples where possible, or reference cross-platform DSC solutions.
- Reorganize the content to mention cross-platform or Linux support (if any) earlier, not just in a link.
- If the solution is Windows-only, add a clear note at the top to set expectations for Linux/macOS users.
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates a notable Windows bias. It exclusively references PowerShell DSC concepts, cmdlets, and types (such as [PSCredential]), and all examples and terminology are Windows-centric. There are no Linux/macOS configuration examples, nor are Linux equivalents or patterns mentioned. The only Linux-specific content is a retirement announcement, indicating reduced or discontinued support for Linux DSC in Azure Automation.
Recommendations
- Add explicit notes clarifying the current support status for Linux/macOS DSC in Azure Automation, including alternatives if available.
- Provide examples or guidance for Linux/macOS users, such as how to manage configurations outside of Azure Automation or using cross-platform DSC tools.
- If Linux support is deprecated, offer migration paths or recommend other configuration management solutions for Linux/macOS users.
- Avoid using Windows-specific terminology (e.g., [PSCredential]) without explanation or cross-platform alternatives.
Automation
Deploy an Amazon Web Services VM with an Azure Automation runbook
...icles/automation/automation-scenario-aws-deployment.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation exclusively uses PowerShell and Windows-centric tools (PowerShell Gallery, PowerShell ISE) for all examples and instructions. There are no references to Linux/macOS alternatives (e.g., Bash, AWS CLI in shell, CloudShell), nor are cross-platform scripting options discussed. The workflow assumes familiarity with Windows environments and does not provide guidance for users on Linux or macOS platforms.
Recommendations
- Add equivalent instructions using AWS CLI and Bash for Linux/macOS users.
- Mention and provide examples for using Azure Automation Python runbooks, which are cross-platform.
- Include steps for installing and using the AWS CLI on Linux/macOS, and show how to authenticate and provision VMs via shell scripts.
- Clarify that PowerShell Core is available on Linux/macOS and provide instructions for those platforms if PowerShell is required.
- Avoid referencing Windows-only tools (e.g., PowerShell ISE) without alternatives; suggest VS Code or other cross-platform editors.
- Present examples for both Windows and Linux/macOS users side-by-side, or at least note platform differences.
Automation
Use the Azure Automation graphical runbook SDK (preview)
...blob/main/articles/automation/graphical-runbook-sdk.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation is heavily oriented toward Windows and PowerShell workflows. All examples and SDK usage revolve around PowerShell commands and concepts, with no mention of Linux or cross-platform alternatives. The SDK itself appears to be designed for Windows environments, and there are no instructions, examples, or guidance for Linux/macOS users.
Recommendations
- Clarify platform support for the SDK (is it Windows-only, or can it be used on Linux/macOS with .NET Core?).
- If cross-platform usage is possible, provide Linux/macOS installation and usage instructions.
- Include examples using bash or other Linux-native scripting tools if supported.
- Explicitly state any platform limitations and suggest alternatives for Linux/macOS users.
- If the SDK is Windows-only, recommend equivalent automation approaches for Linux users (e.g., Python SDKs, Azure CLI, etc.).
Automation
Manage runbooks in Azure Automation
...-docs/blob/main/articles/automation/manage-runbooks.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation is heavily biased toward PowerShell and Windows-centric tooling. All code examples use PowerShell cmdlets, with file paths and script references in Windows format (e.g., C:\Runbooks\Sample_TestRunbook.ps1). There is no mention of Bash, CLI, or Linux/macOS-specific workflows, nor are there examples using cross-platform tools like Azure CLI. Windows/PowerShell methods are presented exclusively and often first, with no Linux alternatives or parity.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell cmdlets, especially for creating, importing, publishing, and retrieving runbooks.
- Include Linux/macOS file path examples and clarify cross-platform compatibility for scripts.
- Explicitly state which features/tools are cross-platform and which are Windows-only.
- Provide guidance for authoring and managing runbooks from Linux/macOS environments.
- Mention and demonstrate Python runbooks and their management using non-Windows tools.
- Add troubleshooting and best practices sections relevant to Linux/macOS users.
Automation
Manage Office 365 services using Azure Automation
...ocs/blob/main/articles/automation/manage-office-365.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 all examples and instructions using Windows PowerShell cmdlets and modules. There is an explicit note that the Microsoft Graph PowerShell module must be run from Windows PowerShell, and no Linux/macOS alternatives or cross-platform guidance are provided. The workflow assumes familiarity with Windows-centric tools and patterns, and does not mention Bash, cross-platform PowerShell Core, or CLI alternatives.
Recommendations
- Provide guidance and examples for Linux/macOS users, including any available cross-platform alternatives (e.g., PowerShell Core, Azure CLI, Microsoft Graph CLI, REST API).
- Clarify which steps are Windows-only and suggest workarounds or alternatives for non-Windows platforms.
- If the Microsoft Graph PowerShell module is truly Windows-only, explicitly state this limitation at the top and link to cross-platform options.
- Include example scripts and runbook instructions for Bash, PowerShell Core, or other supported shells where possible.
- Reorder examples so that platform-neutral or cross-platform approaches are presented first, or at least in parallel with Windows-specific instructions.
Automation
Azure Quickstart - Install Hybrid Worker extension on Azure portal.
...omation/quickstarts/install-hybrid-worker-extension.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a Windows bias by focusing exclusively on installing the Hybrid Worker extension for Windows Azure Virtual Machines. All step-by-step instructions, screenshots, and extension selection refer only to 'Azure Automation Windows Hybrid Worker', with no mention or examples for Linux VMs. Prerequisites and installation steps are Windows-specific, and there is no guidance for Linux users, despite the initial claim that both Windows and Linux VMs are supported.
Recommendations
- Add explicit instructions and screenshots for installing the Hybrid Worker extension on Linux Azure Virtual Machines.
- Include Linux-specific extension names and configuration steps, if they differ from Windows.
- Update the prerequisites section to mention both Windows and Linux VM requirements.
- Present Windows and Linux instructions in parallel or clearly separate sections to ensure parity.
- Clarify any differences in extension capabilities or limitations between Windows and Linux.
Automation
Azure Quickstart - Configure a VM with Desired State Configuration
...n/articles/automation/quickstarts/dsc-configuration.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation is heavily oriented towards Windows and PowerShell, with most instructions and examples assuming a Windows environment. Although there is a brief mention of configuring a LAMP stack (Linux), the tooling, terminology, and examples are all PowerShell-centric. The documentation also notes that Azure Automation DSC for Linux has retired, and does not provide alternative Linux/macOS guidance or parity for configuration management. Windows tools and patterns (PowerShell Gallery, MOF compilation, etc.) are referenced exclusively, with no Linux-native equivalents or alternatives.
Recommendations
- Clearly state the limitations and alternatives for Linux/macOS users, including supported configuration management options (e.g., Azure Policy Guest Configuration, Ansible, Chef, etc.).
- Provide links or guidance for Linux/macOS users to migrate from DSC to supported solutions.
- Offer example workflows or scripts for Linux/macOS environments using supported tools.
- Reorder or clarify sections to make it clear that the quickstart is Windows-only, and direct Linux/macOS users to relevant documentation.
- Remove or update references to Chocolatey and other Windows-specific tools in 'Next steps' for Linux/macOS parity.
Automation
Troubleshoot Azure Automation State Configuration issues
...automation/troubleshoot/desired-state-configuration.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
missing_linux_example
Summary
The documentation is heavily oriented toward Windows and PowerShell, with most troubleshooting steps, examples, and cmdlets focused on Windows environments. PowerShell DSC and related modules are referenced throughout, and Windows-specific tools (such as w32tm and PowerShell certificate management) are used exclusively in examples. Linux troubleshooting is only mentioned in a single scenario, with minimal detail and no parity in examples or step-by-step guidance.
Recommendations
- Provide Linux-specific troubleshooting steps and examples for each scenario, especially for log collection, agent registration, and certificate management.
- Include Bash or shell command equivalents alongside PowerShell commands where applicable.
- Reference Linux DSC extension documentation and tools (such as OMI, omiserver logs, or systemd journal) in relevant sections.
- Ensure that Linux onboarding and error resolution steps are given equal prominence and detail as Windows steps.
- Add guidance for managing certificates and DSC configuration files on Linux nodes.
- Where PowerShell cmdlets are referenced, clarify if/how they apply to Linux, or provide alternatives.
Automation
Configure machines to a desired state in Azure Automation
...automation/tutorial-configure-servers-desired-state.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation is heavily biased toward Windows environments, with all examples and instructions using Windows PowerShell cmdlets and focusing on Windows Server VMs. There are no Linux/macOS examples, and the prerequisites and configuration steps are exclusively Windows-centric. References to Linux support are limited to retirement announcements, with no guidance for Linux users.
Recommendations
- Add explicit Linux/macOS onboarding and configuration examples, including Bash/CLI equivalents.
- Provide sample DSC configurations for Linux targets (e.g., installing Apache instead of IIS).
- Clarify current support status for Linux and offer migration or alternative guidance for Linux users.
- List Linux prerequisites and link to Linux VM creation guides alongside Windows instructions.
- Include cross-platform notes or tables summarizing differences and supported features.
Backup
Troubleshoot data recovery from Microsoft Azure Backup Server by using Azure Backup
...ckup/backup-azure-alternate-dpm-server-troubleshoot.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation is focused exclusively on Microsoft Azure Backup Server (MABS), which is a Windows-based solution. All troubleshooting steps and error messages reference Azure Backup Server and Data Protection Manager (DPM), both of which are Windows-only tools. There are no examples, recommendations, or mentions of Linux or macOS equivalents, nor guidance for users operating outside the Windows ecosystem.
Recommendations
- Clarify early in the documentation that MABS is a Windows-only product, and provide links or references to Azure Backup solutions for Linux and macOS if available.
- Add troubleshooting guidance or cross-references for Azure Backup scenarios on Linux servers (e.g., using the Azure Backup agent for Linux, or Azure VM backup for Linux VMs).
- Where possible, include parity tables or notes indicating which steps/tools are applicable to Linux environments, or provide alternative instructions for Linux users.
Backup
Troubleshoot System Center Data Protection Manager
.../articles/backup/backup-azure-scdpm-troubleshooting.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation is heavily oriented toward Windows environments, referencing Windows-specific tools (e.g., 'net stop dpmra', NT AUTHORITY\SYSTEM, MARS agent) and does not provide any Linux or macOS troubleshooting guidance or examples. There are no alternative commands, patterns, or considerations for non-Windows platforms.
Recommendations
- Clarify early in the documentation that System Center Data Protection Manager (DPM) is a Windows-only product, if that is the case.
- If Linux or macOS agents or interoperability exist, provide troubleshooting steps and examples for those platforms.
- If DPM does not support Linux/macOS, explicitly state this to set expectations for cross-platform users.
- Where possible, provide equivalent commands or troubleshooting steps for Linux-based backup solutions if the documentation is intended for a broader audience.
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 deployment and cleanup instructions use PowerShell scripts, with no Azure CLI or Bash examples. The VM template provisions only Windows VMs, with no mention of Linux images or parameters. Windows tools and patterns (PowerShell, Windows VM images, RDP port) are referenced exclusively and before any Linux equivalents, which are absent.
Recommendations
- Add Azure CLI and Bash examples for deploying the Bicep file and cleaning up resources.
- Include instructions for provisioning Linux VMs in the Bicep template, with parameters for popular Linux distributions.
- Provide parity in monitoring and backup job instructions using cross-platform tools (Azure CLI, REST API).
- Reorder or balance examples so that Linux and Windows are treated equally.
- Explicitly mention that the template is Windows-only, and link to Linux VM backup documentation if available.
Backup
Tutorial - Back Up SQL Server Databases to Azure
...-docs/blob/main/articles/backup/tutorial-sql-backup.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation is heavily oriented toward Windows environments. It exclusively references Windows-specific extensions (AzureBackupWindowsWorkload, SqlIaaSExtension), Windows service accounts (NT Service\AzureWLBackupPluginSvc), and does not mention Linux VMs or provide instructions/examples for SQL Server running on Linux. All screenshots and steps assume a Windows VM context, and there is no guidance for Linux users.
Recommendations
- Explicitly state whether Linux SQL Server VMs are supported or not in the prerequisites.
- If Linux support exists, add a dedicated section for Linux VMs, including required extensions, service account setup, and any differences in backup configuration.
- Provide Linux-specific troubleshooting steps and error messages.
- Include screenshots and examples for Linux environments where applicable.
- If Linux is not supported, clearly mention this limitation at the beginning of the documentation.
Communication Services
Teams Phone Extensibility
...uickstarts/tpe/teams-phone-extensibility-quickstart.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation page exhibits a strong Windows bias, particularly in administrative and provisioning steps. All command-line examples for Teams administration use PowerShell cmdlets and modules, which are native to Windows. There are no Linux/macOS equivalents or guidance for cross-platform alternatives. The Azure CLI section also mixes in PowerShell modules, and instructions for installing modules (e.g., Install-Module) are Windows-centric. The Teams Admin Center and Microsoft 365 Admin Center are referenced, but all automation and scripting is shown via PowerShell. No Bash, shell, or Linux-native tooling is mentioned, and the order of presentation always assumes Windows/PowerShell as the default environment.
Recommendations
- Provide equivalent Bash or shell scripts for provisioning steps, especially for Azure CLI and bot registration.
- Document how to use Teams PowerShell modules on Linux/macOS via PowerShell Core, including installation steps and caveats.
- Explicitly state cross-platform requirements and limitations for each administrative step.
- Add notes or sections for Linux/macOS users, including troubleshooting and alternative workflows.
- Where possible, use Azure CLI commands instead of PowerShell for resource provisioning, as Azure CLI is cross-platform.
- Clarify which steps require Windows-only tools and suggest remote or web-based alternatives (e.g., Teams Admin Center web UI).
Firewall
Deploy and configure Enterprise CA certificates for Azure Firewall Premium
.../firewall/premium-deploy-certificates-enterprise-ca.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
powershell_heavy
Summary
The documentation is heavily biased towards Windows environments, with instructions and tooling (certtmpl.msc, Internet Explorer, Active Directory Certification Services) that are exclusive to Windows. No Linux or cross-platform alternatives are provided for certificate creation, management, or export, and all examples and screenshots are Windows-centric. This creates significant friction for Linux/macOS users, who cannot follow the documented steps without access to a Windows Server and related tools.
Recommendations
- Provide equivalent instructions for Linux/macOS environments, such as using OpenSSL for certificate creation and export.
- Mention cross-platform certificate authorities (e.g., EJBCA, Dogtag, or OpenSSL-based CA) as alternatives to Active Directory Certification Services.
- Include examples of certificate requests and exports using command-line tools available on Linux/macOS.
- Clarify which steps are Windows-specific and offer guidance for non-Windows users.
- Add screenshots and walkthroughs for Linux/macOS workflows where possible.
Load Balancer
Quickstart: Create a public load balancer - Azure portal
...cer/quickstart-load-balancer-standard-public-portal.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
windows_first
Summary
The documentation is heavily biased toward Windows, especially in the 'Install IIS' section, which provides only Windows PowerShell commands for installing IIS on the backend VMs. There are no instructions or examples for deploying a Linux-based web server (such as Apache or Nginx) on Linux VMs, nor are there Bash or Linux CLI equivalents. The workflow assumes Windows VMs and tools, making it difficult for Linux/macOS users to follow or replicate the steps without significant adaptation.
Recommendations
- Add parallel instructions for deploying a Linux VM (e.g., Ubuntu) and installing a web server (Apache, Nginx) using Bash commands.
- Provide both Windows and Linux examples side-by-side in the 'Install IIS' section, or offer a choice at the beginning of the quickstart.
- Reference Linux tools and patterns (e.g., SSH, Bash, apt/yum) where appropriate.
- Clarify that the load balancer works with both Windows and Linux VMs, and link to relevant Linux quickstarts if available.
Migrate
Support for Hyper-V assessment in Azure Migrate and Modernize
...ain/articles/migrate/migrate-support-matrix-hyper-v.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, with Windows Server versions and PowerShell remoting as core requirements for Hyper-V assessment. Windows tools and patterns (PowerShell, WinRM, WMI) are mentioned first and in detail, while Linux support is referenced but not elaborated with equivalent examples or tooling. Critical features such as SQL Server and ASP.NET web app discovery are not supported for Linux, and all sample scripts and configuration instructions are Windows-centric.
Recommendations
- Provide Linux-specific examples and instructions where possible, especially for appliance deployment, credential setup, and dependency analysis.
- Clarify Linux limitations up front and offer alternative solutions or workarounds for unsupported features (e.g., SQL Server discovery on Linux).
- Balance the order of presentation so Linux requirements and patterns are described alongside Windows, not after.
- Include sample scripts or configuration steps for Linux environments (e.g., SSH setup, sudo configuration, package manager commands).
- Explicitly state which features are Windows-only and suggest Linux migration alternatives or roadmap if possible.
Migrate
ASP.NET app containerization and migration to App Service
...te/tutorial-app-containerization-aspnet-app-service.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation is heavily biased towards Windows environments for ASP.NET app containerization. All prerequisites, installation steps, and operational instructions require a Windows machine, PowerShell, and Windows-specific tools (Web Deploy). There are no Linux/macOS alternatives or instructions for running the containerization tool or migrating ASP.NET apps from non-Windows environments. The only Linux references are for Java/Tomcat scenarios, not ASP.NET.
Recommendations
- Provide clear guidance on whether ASP.NET Core apps (which can run cross-platform) are supported, and if so, add Linux/macOS instructions.
- If the tool is Windows-only, explicitly state this limitation at the top of the documentation.
- Offer alternative manual containerization steps for ASP.NET apps on Linux/macOS (e.g., Dockerfile templates, migration guides).
- Include troubleshooting and log location guidance for non-Windows environments if/when support is added.
- Add parity in examples and prerequisites for Linux/macOS users where possible, or link to relevant resources.
Migrate
Azure App Containerization ASP.NET; Containerization and migration of ASP.NET applications to Azure Kubernetes.
...ate/tutorial-app-containerization-aspnet-kubernetes.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 for ASP.NET app containerization. All instructions, prerequisites, and examples assume the use of a Windows machine, Windows Server, PowerShell, and Microsoft-specific tools (Web Deploy). There are no Linux/macOS alternatives or parity for ASP.NET scenarios, and all steps require Windows-only technologies. Linux is only mentioned in the context of Java/Tomcat apps, not ASP.NET.
Recommendations
- Clarify early that ASP.NET containerization is currently Windows-only, and explicitly state Linux/macOS are unsupported for this scenario.
- If possible, provide or link to guidance for containerizing ASP.NET apps from Linux/macOS environments (e.g., using .NET Core, cross-platform Dockerfiles, or remote Windows hosts).
- Offer alternative instructions or tooling for Linux/macOS users where feasible, or suggest workarounds (such as using a Windows VM in Azure or locally).
- Present prerequisites and examples for both platforms where applicable, or clearly segment Windows-only steps.
- Consider adding a comparison table of supported platforms and scenarios for quick reference.
Migrate
Discover AWS instances with Azure Migrate Discovery and assessment
...cs/blob/main/articles/migrate/tutorial-discover-aws.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation exhibits a notable Windows bias. The Azure Migrate appliance is required to run on Windows Server (2019/2022), with no mention of Linux as a host OS. All setup and installation instructions rely exclusively on PowerShell scripts and Windows tools (IIS, Windows Activation Service), with no Linux equivalents or alternatives provided. Examples and instructions for running the installer are Windows/PowerShell-only. Linux is only referenced as a target for discovery, not as a platform for hosting the appliance or running the installer.
Recommendations
- Provide instructions and support for running the Azure Migrate appliance on Linux hosts, or clarify if this is not possible.
- Offer Linux shell script equivalents for the installer and configuration steps, or document a Linux-native installation path.
- Include Linux-first or side-by-side examples for setup, not just PowerShell/Windows.
- Document any limitations or rationale for Windows-only appliance hosting to help Linux users understand their options.
- If Windows hosting is required, make this explicit in the prerequisites and suggest workarounds for Linux-only environments (e.g., using a Windows VM).
Migrate
Discover servers on Hyper-V with Azure Migrate Discovery and assessment
...lob/main/articles/migrate/tutorial-discover-hyper-v.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation is heavily oriented toward Windows environments, specifically Windows Server and Hyper-V. All setup, configuration, and scripting examples use PowerShell and Windows-native tools. Linux is mentioned only as a supported target OS for discovery, but there are no Linux-specific instructions, examples, or parity for appliance deployment, host preparation, or troubleshooting. Windows tools and patterns (WinRM, PowerShell, Hyper-V Manager, Local Group Policy Editor) are used exclusively, with no mention of Linux equivalents or alternative workflows for non-Windows users.
Recommendations
- Provide explicit instructions and examples for Linux-based Hyper-V hosts (if supported), or clarify that only Windows-based Hyper-V hosts are supported.
- Include Linux command-line alternatives where PowerShell or Windows tools are used, or state limitations if not possible.
- Add parity in appliance deployment instructions for Linux environments, if supported (e.g., using KVM/QEMU, or instructions for deploying the appliance on a Linux VM).
- Clarify in prerequisites and throughout the document which steps are Windows-only, and provide guidance for Linux/macOS administrators where relevant.
- If Windows-only is a hard requirement, state this clearly at the top of the documentation.
Active Directory B2C
Request an access token in Azure Active Directory B2C
...ob/main/articles/active-directory-b2c/access-tokens.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation mentions Microsoft PowerShell as an example HTTP client for testing the POST request, but does not mention Linux/macOS alternatives (such as curl or httpie), nor does it provide example commands for those platforms. This creates a subtle bias towards Windows users by implying PowerShell is the default or preferred tool, and omits guidance for Linux/macOS users.
Recommendations
- Mention cross-platform HTTP clients such as curl and httpie alongside PowerShell.
- Provide example commands for requesting tokens using curl or httpie.
- Clarify that any HTTP client can be used, and link to relevant documentation for Linux/macOS tools.
Active Directory B2C
Twilio Verify App with Azure Active Directory B2C
...b/main/articles/active-directory-b2c/partner-twilio.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation demonstrates a Windows bias by focusing exclusively on .NET (typically associated with Windows environments) and referencing configuration via web.config files. There are no examples or guidance for Linux/macOS users, such as using cross-platform .NET Core, environment variables, or deployment steps for Linux-based hosting. Instructions for uploading certificates and hosting the demo app are tailored to Azure App Service (commonly used with Windows), with no mention of Linux alternatives.
Recommendations
- Provide instructions for deploying the demo app on Linux-based environments (e.g., Azure App Service for Linux, Docker, or on-premises Linux servers).
- Include configuration examples using environment variables or appsettings.json, which are more common in cross-platform .NET Core applications.
- Clarify whether the sample app supports .NET Core/.NET 6+ and provide steps for running it on Linux/macOS.
- Add certificate creation and management instructions for Linux (e.g., using OpenSSL).
- Ensure all code/configuration samples are platform-agnostic or provide parallel examples for Linux/macOS.
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation provides a generally cross-platform overview but introduces notable Windows bias in the Managed Instance section, which is Windows-only and highlights Windows-specific features and tools (e.g., COM, registry, MSI, PowerShell, RDP) without Linux equivalents or alternatives. Windows tools (PowerShell, RDP) are mentioned exclusively, and Linux support is only referenced as 'not supported' without further guidance or parity.
Recommendations
- Clearly separate Windows-only features (like Managed Instance) and provide equivalent Linux/container guidance or alternatives where possible.
- Include Linux-focused examples or scenarios, especially in sections discussing command-line tools and deployment patterns.
- When mentioning Windows tools (e.g., PowerShell, RDP), also mention Linux alternatives (e.g., Bash scripts, SSH) where applicable.
- Provide links or references to Linux/container documentation for users seeking those options.
- In decision guides, offer more detail on Linux/container use cases, not just as a negative ('not supported'), but with positive guidance.
Automation
Manage role permissions and security in Azure Automation
...les/automation/automation-role-based-access-control.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 only Azure PowerShell examples for role assignment and management tasks, with no mention of equivalent Azure CLI commands or Linux/macOS workflows. The PowerShell approach is presented as the sole scripting option, and there is no guidance for users who may be working from Linux or macOS environments. This creates friction for non-Windows users who may prefer or require cross-platform tools.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell cmdlet workflows, including role assignment, listing roles, and removing assignments.
- Explicitly mention that Azure CLI is cross-platform and provide links to relevant CLI documentation.
- Include notes or sections clarifying that all role management operations can be performed from Linux/macOS using Azure CLI.
- Where scripts are shown, offer both PowerShell and CLI versions side-by-side.
- Review any referenced links to ensure Linux/macOS parity is maintained.
Automation
Start an Azure Automation Runbook from a Webhook
...s/blob/main/articles/automation/automation-webhooks.md
Medium 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 usage. All code samples, automation steps, and REST API usage are demonstrated exclusively with PowerShell commands and Windows file paths. There are no examples for Linux/macOS users (e.g., Bash, curl, or cross-platform Azure CLI). Windows tools and patterns (PowerShell cmdlets, Windows-style file paths) are mentioned exclusively and always before any Linux alternatives (which are not present). This creates friction for non-Windows users.
Recommendations
- Provide equivalent examples using Bash and curl for webhook invocation and REST API calls.
- Include Azure CLI examples for creating, updating, and deleting webhooks and runbooks.
- Use platform-neutral file paths and clarify where Windows-specific syntax is used.
- Explicitly mention cross-platform support and limitations, and link to Linux/macOS guidance where relevant.
- Add notes or sections for Linux/macOS users, including troubleshooting tips for common issues on those platforms.
Automation
Use Azure Private Link to securely connect networks to Azure Automation
...in/articles/automation/how-to/private-link-security.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides a PowerShell-only example for configuring the 'publicNetworkAccess' property, with no equivalent CLI, REST API, or Linux/macOS shell example. The State Configuration section references PowerShell DSC as the configuration management tool, which is Windows-centric. While the documentation mentions Linux support in the context of Update Management and Log Analytics agent, actionable examples and tooling are Windows-first or Windows-only.
Recommendations
- Add Azure CLI and/or REST API examples for setting 'publicNetworkAccess', demonstrating parity for Linux/macOS users.
- Include Bash or shell script equivalents alongside PowerShell commands.
- Mention cross-platform configuration management options (e.g., Chef, Ansible, or native Linux DSC) in the State Configuration section.
- Ensure screenshots and UI instructions clarify any OS-specific requirements or differences.
- Explicitly state Linux/macOS support wherever features are available, and provide links to relevant Linux documentation.
Automation
Azure Automation State Configuration overview
...ob/main/articles/automation/automation-dsc-overview.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 DSC is the primary focus throughout, with Windows-specific tools and terminology (e.g., WMF, WinRM, PowerShell cmdlets) mentioned first and in more detail. Linux support is acknowledged but lacks equivalent depth, examples, or tooling references. Proxy support and configuration details are more thoroughly explained for Windows, with Linux relegated to brief mentions. No Linux-specific configuration or onboarding examples are provided.
Recommendations
- Provide Linux-specific examples for onboarding, configuration, and troubleshooting, similar to the Windows sections.
- Include references to Linux-native tools and commands (e.g., shell scripts, systemd integration) where appropriate.
- Present Windows and Linux requirements and instructions in parallel, rather than listing Windows first and in greater detail.
- Expand documentation on Linux proxy support and network configuration, matching the detail given for Windows.
- Add links to Linux DSC extension documentation and community resources.
Automation
Configure runbook output and message streams
...s/automation/automation-runbook-output-and-messages.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation is heavily focused on Windows PowerShell, with all examples and tooling references using PowerShell cmdlets and syntax. There are no examples or guidance for Linux/macOS users, such as Bash, Python, or cross-platform CLI usage. Windows-specific tools and patterns (e.g., preference variables, PowerShell redirection, Az.Automation cmdlets) are mentioned exclusively, and the section on retrieving runbook output explicitly references 'Windows PowerShell' without alternatives. This creates friction for users operating on Linux/macOS or those using Python runbooks.
Recommendations
- Add equivalent examples for Bash, Azure CLI, or Python where possible, especially for retrieving runbook output and handling streams.
- Clarify which features and cmdlets are available cross-platform, and note any limitations for Linux/macOS users.
- Include references to Python runbooks and their output handling, with sample code and retrieval methods.
- Reorganize sections to present cross-platform approaches first or in parallel, rather than Windows/PowerShell-only.
- Explicitly state when a feature or cmdlet is Windows-only, and provide alternatives for other platforms.
Automation
Azure Automation extension for Visual Studio Code
...ation/how-to/runbook-authoring-extension-for-vscode.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
Summary
The documentation page references PowerShell modules as a prerequisite for local runbook execution but does not mention Linux-specific requirements or provide guidance for Linux/macOS users. There are no examples or instructions tailored to Linux environments, and the documentation assumes familiarity with PowerShell, which is traditionally Windows-centric, despite PowerShell Core being cross-platform.
Recommendations
- Explicitly mention that PowerShell Core is available on Linux/macOS and provide installation instructions for those platforms.
- Include guidance for installing Python packages on Linux/macOS, such as using pip or system package managers.
- Clarify any differences in extension usage or runbook debugging on Linux/macOS, if applicable.
- Add screenshots or notes indicating that the extension works on Linux/macOS, or specify any limitations.
- Ensure that all steps and terminology (e.g., right-click context menus) are applicable to Linux/macOS environments.
Automation
Remediate noncompliant Azure Automation State Configuration servers
...b/main/articles/automation/automation-dsc-remediate.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation prioritizes Windows remediation by providing direct PowerShell examples and references to Windows-specific tools (Update-DscConfiguration, Run Command). Linux remediation is described in less detail, lacks direct script examples, and refers users to external documentation. Windows solutions are presented first and more comprehensively, while Linux users face more manual or indirect steps.
Recommendations
- Provide direct, in-page Linux remediation script examples (e.g., Python or shell commands) similar to the PowerShell example for Windows.
- Clarify and expand the Linux remediation steps, including explicit commands and workflow.
- Balance the order of presentation by alternating or paralleling Windows and Linux instructions.
- Reference Linux-specific tools and modules where applicable, not just Windows/PowerShell ones.
- Ensure that Linux users are not required to consult external documentation for basic remediation tasks.
Automation
Send an email from an Azure Automation runbook
...blob/main/articles/automation/automation-send-email.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation exclusively uses PowerShell for all examples and instructions, including runbook creation, resource management, and cleanup. There are no Bash, CLI, or Linux/macOS-specific instructions or examples. Windows tools and patterns (PowerShell cmdlets, Windows-centric terminology) are mentioned throughout, with no parity for Linux users. The documentation assumes the use of PowerShell both locally and in the Azure Automation context, which may create friction for users on Linux or macOS who prefer Bash or Azure CLI.
Recommendations
- Add equivalent examples using Azure CLI and Bash scripts for each major step (resource creation, secret management, runbook creation, cleanup).
- Include guidance for Linux/macOS users on installing and using Azure CLI and/or PowerShell Core.
- Clarify that Azure Automation supports Python runbooks and provide a Python example for sending email via SendGrid.
- Reorder sections or provide parallel instructions so Linux/macOS patterns are not always secondary to Windows/PowerShell.
- Explicitly mention cross-platform support and link to relevant documentation for non-Windows environments.
Automation
Manage Runtime Environment and Associated Runbooks in Azure Automation
...main/articles/automation/manage-runtime-environment.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation demonstrates a notable Windows bias, primarily through its heavy focus on PowerShell examples, repeated references to PowerShell modules and tools (e.g., Az PowerShell package, PowerShell Gallery), and the use of Windows-centric terminology and patterns. While Python is mentioned as an alternative runtime, examples, screenshots, and REST API payloads overwhelmingly default to PowerShell scenarios. Linux/macOS-specific guidance, such as package formats, is only briefly referenced and lacks parity in example depth and clarity.
Recommendations
- Provide equal, detailed examples for Python runbooks, including REST API payloads and portal workflows.
- Include Linux/macOS-specific instructions and screenshots, especially for package management and runtime environment creation.
- Highlight Python and Linux options alongside PowerShell, rather than defaulting to PowerShell-first explanations.
- Clarify package upload formats for both PowerShell and Python, with explicit Linux/macOS guidance (e.g., .whl files, supported OS versions).
- Add troubleshooting and usage examples for Python runbooks and Linux environments.
- Reference cross-platform tools (e.g., Azure CLI) with parity to PowerShell, and provide examples for both.
Automation
Author graphical runbooks in Azure Automation
...les/automation/automation-graphical-authoring-intro.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation is heavily oriented around Windows PowerShell and PowerShell Workflow, with all examples, scripting references, and tooling focused exclusively on PowerShell. There is no mention of Bash, Linux shell scripting, or cross-platform alternatives, and the documentation assumes familiarity with Windows-centric tools and patterns. Linux/macOS users are not provided with equivalent examples or guidance, creating friction for those not using Windows environments.
Recommendations
- Clarify that Azure Automation graphical runbooks are PowerShell-based and note platform limitations up front.
- Provide explicit guidance for Linux/macOS users, including any prerequisites or limitations (e.g., PowerShell Core support, installation steps).
- Add examples using PowerShell Core (pwsh) and clarify cross-platform compatibility.
- Where possible, mention or link to Bash or other Linux-native automation options in Azure (e.g., Python runbooks, Bash scripts in Logic Apps).
- Include a section comparing Windows PowerShell and PowerShell Core, with notes on differences and supported features in Azure Automation.
- Add troubleshooting tips for Linux/macOS users (e.g., file downloads, script execution).
Automation
Remove DSC and node from Automation State Configuration
...configuration/remove-node-and-configuration-package.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation demonstrates a moderate Windows bias. Windows and PowerShell tools are mentioned first and in greater detail, with explicit PowerShell cmdlet references and examples. Linux instructions are present but less detailed, and Linux-specific steps are often described generically or as manual file deletions, while Windows users are given dedicated PowerShell cmdlets. The overall structure and example order favor Windows and PowerShell, creating friction for Linux users.
Recommendations
- Provide equivalent Linux command-line examples (e.g., shell scripts) for unregistering nodes and deleting configurations, not just manual file deletion.
- Mention Linux tools and commands (such as omicli, systemctl, or relevant DSC/OMI utilities) where appropriate, and provide step-by-step instructions similar to the PowerShell examples.
- Ensure that Linux instructions are as detailed and explicit as Windows/PowerShell instructions, including troubleshooting tips and automation options.
- Present Windows and Linux examples side-by-side or in parallel tabs, rather than listing Windows/PowerShell first.
- Include references to Linux documentation and community resources for DSC management.
Automation
Quickstart - Enable managed identities for your Automation account using the Azure portal
...cles/automation/quickstarts/enable-managed-identity.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page is primarily focused on using the Azure portal UI, which is cross-platform. However, the only next step tutorial linked is for creating an Automation PowerShell runbook, which is Windows-centric. There are no examples or references to Linux shell scripting, Bash, or cross-platform automation approaches. The documentation implicitly prioritizes Windows/PowerShell patterns over Linux equivalents.
Recommendations
- Include links or examples for creating Automation runbooks using Python or Bash, which are more common on Linux/macOS.
- Add a 'Next steps' link to a tutorial for Linux users, such as 'Create Automation Python runbook using managed identity'.
- Explicitly mention that Automation runbooks can be authored in multiple languages and provide parity in guidance.
- Where PowerShell is referenced, clarify cross-platform support or alternatives for Linux/macOS users.
Automation
Troubleshoot extension-based Hybrid Runbook Worker issues in Azure Automation
.../troubleshoot/extension-based-hybrid-runbook-worker.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation generally provides parity between Windows and Linux troubleshooting steps for Hybrid Runbook Workers, including separate sections and commands for each OS. However, there is a notable Windows bias in several areas: Windows examples and tools (such as PowerShell scripts and registry edits) are often presented first, and some troubleshooting scenarios (e.g., registry permissions, event logs, UAC issues) are Windows-specific with no Linux equivalent or guidance. Windows-centric terminology (e.g., 'Microsoft-SMA event logs', 'Win32 Process') is used throughout, and some references (like log collection scripts) are PowerShell-heavy, with Linux alternatives mentioned but less detailed. In some scenarios, only Windows instructions are given, or Windows tools are referenced before their Linux counterparts.
Recommendations
- Alternate the order of Windows and Linux instructions to avoid always presenting Windows first.
- Where Windows-specific troubleshooting (e.g., registry, event logs, UAC) is described, provide Linux equivalents or explicitly state if not applicable.
- Ensure Linux troubleshooting tools and scripts are described with equal detail and clarity as Windows/PowerShell tools.
- Add more Linux-specific troubleshooting scenarios, such as SELinux/AppArmor issues, systemd service failures, or log analysis tips.
- Use OS-neutral terminology where possible, and clarify when a step is OS-specific.
- Provide references to Linux documentation or community resources for deeper troubleshooting.
Automation
Use Source Control Integration in Azure Automation
...main/articles/automation/source-control-integration.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a strong bias toward Windows and PowerShell. All command-line examples use Azure PowerShell cmdlets, with no mention of Bash, Azure CLI, or Linux/macOS workflows. Instructions for assigning roles and configuring source control are exclusively provided for PowerShell, and references to file encoding issues link to PowerShell/VSCode documentation. There are no Linux/macOS-specific instructions or parity examples, and Windows tools and patterns are presented first and exclusively.
Recommendations
- Add equivalent examples using Azure CLI and Bash for all PowerShell command-line instructions, especially for role assignment and source control configuration.
- Explicitly state platform compatibility for PowerShell cmdlets and clarify if they can be run on Linux/macOS (e.g., via PowerShell Core).
- Provide guidance for Linux/macOS users on prerequisites, authentication, and troubleshooting, including common editors and encoding issues.
- Include links to cross-platform documentation and tools where available.
- Reorder or balance examples so that Windows and Linux/macOS instructions are presented with equal prominence.
API Management
Use Managed Identities in Azure API Management | Microsoft Docs
...t/api-management-howto-use-managed-service-identity.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides detailed instructions and code samples for Azure PowerShell, which is primarily a Windows-centric tool, and does not offer equivalent examples for Azure CLI or bash scripts that are more commonly used on Linux/macOS. PowerShell instructions are presented before ARM template examples, and there are no Linux/macOS-specific guidance or parity for command-line operations.
Recommendations
- Add Azure CLI examples alongside or before PowerShell examples for all operations (creating, updating, and removing managed identities).
- Explicitly mention cross-platform tools and provide bash script samples where appropriate.
- Clarify that Azure PowerShell is available on Linux/macOS, but highlight Azure CLI as the preferred cross-platform option.
- Ensure that all step-by-step instructions are available for both PowerShell and CLI users.
- Consider reordering examples so that cross-platform solutions (CLI, ARM templates) appear before Windows-specific tools.
App Service
Quickstart: Deploy an ASP.NET web app
...lob/main/articles/app-service/quickstart-dotnetcore.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. Visual Studio (Windows-only) is presented as the primary development environment, with detailed step-by-step instructions and screenshots. PowerShell is recommended for Windows hosting and receives its own section, while Linux equivalents are referenced but not given equal prominence or detail. Some CLI and VS Code instructions are cross-platform, but Windows tools and workflows are generally described first and in greater depth. There are also cases where Linux users are redirected to other tools rather than provided direct instructions.
Recommendations
- Ensure that Linux-specific instructions are provided with equal detail and screenshots, especially for publishing and deployment steps.
- Present cross-platform tools (such as Azure CLI and VS Code) before Windows-only tools in the documentation flow.
- Avoid recommending PowerShell as the default for Windows hosting; instead, clarify parity and provide equivalent Bash/Linux shell examples.
- Include explicit instructions and examples for Linux users in all major sections, not just references to other documentation.
- Balance screenshots and walkthroughs between Windows and Linux environments.
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page exhibits a Windows bias primarily in its examples and configuration patterns. Most code samples and configuration instructions reference Windows-specific paths (e.g., 'c:\data\import'), and there is a lack of explicit Linux/macOS equivalents or guidance. The documentation does not mention Linux/macOS-specific tooling, environment variables, or file system paths, nor does it provide parity examples for non-Windows platforms. This may create friction for developers working on Linux/macOS, especially when configuring file bindings or running WebJobs locally.
Recommendations
- Provide Linux/macOS equivalents for file system paths in all examples (e.g., '/home/user/data/import').
- Explicitly mention that environment variables and configuration files work cross-platform, and note any platform-specific caveats.
- Include notes or sections on running and developing WebJobs on Linux/macOS, including any required dependencies or differences in behavior.
- Ensure that all examples and instructions are platform-neutral or provide alternatives for each major OS.
- Reference cross-platform tools (such as Azure CLI) where relevant, and avoid assuming Visual Studio or Windows-only tooling.
Automation
Troubleshoot Azure Automation managed identity issues
...n/articles/automation/troubleshoot/managed-identity.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page exclusively uses PowerShell cmdlets (e.g., Connect-AzAccount, Get-AzVM, Invoke-RestMethod) and provides only PowerShell-based troubleshooting scripts and examples. There are no Bash, Azure CLI, or Linux/macOS shell equivalents, nor are cross-platform patterns mentioned. The examples and troubleshooting steps assume the reader is using Windows tooling, creating friction for Linux/macOS users.
Recommendations
- Add equivalent Azure CLI and Bash examples for all PowerShell cmdlets and scripts.
- Explicitly mention that the steps apply to both Windows and Linux/macOS Automation accounts, and clarify any platform-specific differences.
- Provide troubleshooting scripts in Bash or Python for Linux/macOS users.
- List cross-platform tools and commands before or alongside Windows/PowerShell examples.
- Include notes on how to run these commands on Linux/macOS, including installation instructions for required modules.
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation exclusively describes managing workspace access using the Azure portal GUI, with screenshots and instructions tailored to the portal interface. There are no examples or references to command-line tools (such as Azure CLI or PowerShell), nor are Linux/macOS-specific workflows or tools mentioned. While the Azure portal is cross-platform via web browser, many Linux users prefer or require CLI-based management, which is not covered.
Recommendations
- Add instructions and examples for managing workspace access using Azure CLI, which is available on Linux, macOS, and Windows.
- Include references to relevant Azure CLI documentation for role assignment and revocation.
- If PowerShell examples are added in the future, ensure Azure CLI equivalents are provided and shown first or side-by-side.
- Explicitly state that the Azure portal is accessible from any OS via browser, but highlight CLI alternatives for automation and scripting.
Application Gateway
TLS policy overview for Azure Application Gateway
...ion-gateway/application-gateway-ssl-policy-overview.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 and Windows-centric tools first and exclusively when discussing how to view or configure TLS policy details. There are no explicit Linux or macOS command examples, nor are cross-platform CLI instructions provided alongside PowerShell references. The 'Next steps' section links only to a PowerShell-based configuration guide, omitting Linux-friendly Azure CLI or REST API walkthroughs.
Recommendations
- Add Azure CLI examples for all configuration and inspection tasks, ensuring parity with PowerShell instructions.
- Explicitly mention REST API and Portal methods where applicable, and provide step-by-step guides for Linux/macOS users.
- In tables and notes, reference CLI and REST API options alongside PowerShell, not after or instead of.
- Update 'Next steps' to link to both PowerShell and CLI/REST API guides for configuring TLS policies.
Application Gateway
What is Azure Application Gateway v2?
.../blob/main/articles/application-gateway/overview-v2.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation page demonstrates a moderate Windows bias. Migration instructions and preview registration/unregistration are presented exclusively with Azure PowerShell commands, which are most commonly used and best supported on Windows. The 'Next steps' section links to a tutorial with a '-ps' suffix, suggesting PowerShell as the primary method. There are no Linux/macOS-specific CLI examples, nor are cross-platform Azure CLI commands provided for key operations. Windows-centric tooling is mentioned before any alternatives, and Linux parity is not addressed.
Recommendations
- Provide Azure CLI examples alongside PowerShell for all registration, migration, and management tasks.
- Explicitly mention that Azure CLI is cross-platform and supported on Linux/macOS.
- Add links to tutorials using Azure CLI or ARM templates for creating and managing Application Gateway v2.
- Clarify which commands/tools are available and supported on Linux/macOS.
- Ensure that Linux/macOS users are not required to use PowerShell for critical operations.
Application Gateway
Generate self-signed certificate with a custom root CA
...ticles/application-gateway/self-signed-certificates.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation demonstrates a moderate Windows bias. Windows and PowerShell are referenced first or exclusively in several key sections, such as the prerequisites (listing Windows before Linux), IIS configuration, and especially in the Application Gateway upload section, which provides only Azure PowerShell examples with Windows file paths. Linux equivalents (e.g., Azure CLI, Linux certificate store instructions) are missing or less emphasized.
Recommendations
- Provide Azure CLI examples for uploading certificates to Application Gateway, using Linux/macOS file paths.
- Include instructions for adding root certificates to Linux/macOS trusted stores (e.g., update-ca-certificates, Keychain Access for macOS).
- List Linux before or alongside Windows in prerequisites and examples, or use neutral phrasing.
- Offer NGINX and Apache configuration screenshots/images, not just IIS.
- Clarify that OpenSSL commands work cross-platform and show example file paths for both OS types.
Azure Resource Manager
Linter rule - no location expressions outside of parameter default values
...anager/bicep/linter-rule-no-loc-expr-outside-params.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation provides deployment guidance exclusively using Azure PowerShell commands, which are primarily Windows-centric. There are no examples or mentions of cross-platform alternatives such as Azure CLI, and the discussion of parameter naming conflicts is specific to PowerShell cmdlets. This creates friction for Linux/macOS users who typically use Azure CLI or other tools.
Recommendations
- Add equivalent Azure CLI examples for deployment scenarios, including parameter naming guidance.
- Mention that Azure CLI is cross-platform and provide links to relevant documentation.
- Clarify which guidance applies to PowerShell and which to CLI, so users can choose the appropriate workflow.
- Consider listing CLI examples before or alongside PowerShell examples to avoid Windows-first bias.
Azure Resource Manager
Create multiple resource instances in Bicep
...icles/azure-resource-manager/bicep/quickstart-loops.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides deployment and cleanup instructions using Azure CLI and Azure PowerShell, but does not include explicit Linux/macOS shell examples (e.g., Bash). While Azure CLI is cross-platform, the examples use Windows-style variable assignment (resourceGroupName = "{provide-a-resource-group-name}") instead of Bash syntax (resourceGroupName="value"). PowerShell examples are given equal prominence, and Visual Studio Code is recommended, which is cross-platform, but no mention is made of Linux-specific tooling or shell environments. The documentation assumes familiarity with Windows/PowerShell patterns and does not address Linux/macOS users directly.
Recommendations
- Add explicit Bash examples for variable assignment and command usage, e.g., resourceGroupName="value" instead of resourceGroupName = "value".
- Clarify that Azure CLI commands work on Linux/macOS and provide shell-specific notes where syntax differs.
- Include a section or note for Linux/macOS users about environment setup and command usage.
- Consider listing Bash examples before PowerShell, or at least alternating order to avoid Windows-first bias.
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page exhibits moderate Windows bias. Windows-specific backup mechanisms (VSS) are described in detail before Linux equivalents, and PowerShell is mentioned as the tool for restoring managed disks, with no Linux CLI or Bash alternatives provided. Linux backup consistency relies on custom scripting, but no example scripts or guidance are given, whereas Windows VSS is explained thoroughly. The documentation generally presents Windows approaches first and in more depth.
Recommendations
- Provide equivalent CLI/Bash examples for Linux users, especially for restore operations currently described only with PowerShell.
- Include sample pre/post scripts for Linux VM application-consistent backups, or link to such resources.
- Present Windows and Linux instructions side-by-side or in parallel sections to avoid Windows-first ordering.
- Mention cross-platform tools (e.g., Azure CLI) for backup and restore tasks, with examples for both OSes.
Backup
Quickstart - Configure vaulted backup for an Azure Kubernetes Service (AKS) cluster using Azure Backup via Azure Bicep
.../main/articles/backup/quick-kubernetes-backup-bicep.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 deployment instructions and referencing PowerShell modules in the prerequisites. There are no Linux/macOS CLI examples, and the deployment workflow is tailored to Windows users (e.g., right-click to paste in shell window). This creates friction for Linux/macOS users who typically use Azure CLI or Bash.
Recommendations
- Add Azure CLI deployment instructions alongside PowerShell, with equivalent parameter prompts and resource creation steps.
- Update prerequisites to mention both Azure PowerShell and Azure CLI, with links to installation guides for each.
- Replace or supplement Windows-specific instructions (e.g., right-click to paste) with cross-platform guidance (e.g., use Ctrl+Shift+V in Linux terminals).
- Clearly indicate that both PowerShell and CLI are supported, and provide parity in example scripts.
Application Gateway
Troubleshoot backend health issues in Azure Application Gateway
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-backend-health-troubleshooting.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, with troubleshooting steps and command-line examples predominantly using PowerShell and Windows-specific tools. Windows methods (PowerShell, certlm.msc, netstat via cmd) are described in detail, often before or instead of Linux equivalents. Linux guidance is sparse, with only brief mentions of OpenSSL and no CLI or shell command examples for common troubleshooting tasks. This bias may hinder Linux/macOS users from efficiently following the documentation.
Recommendations
- Provide equivalent Linux/macOS command-line examples for all PowerShell commands (e.g., use Azure CLI, curl, netcat, ss, openssl).
- Include Linux/macOS methods for certificate inspection and export (e.g., using openssl, keytool, or system certificate stores).
- Present troubleshooting steps for both Windows and Linux environments side-by-side, or clearly indicate platform-specific instructions.
- Reference Linux/macOS tools (e.g., systemctl, journalctl, firewall-cmd/ufw) when discussing server/network troubleshooting.
- Ensure Azure CLI examples are given equal prominence to PowerShell, as CLI is cross-platform.
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 command-line example for enabling logging uses PowerShell, with no mention of Azure CLI, Bash, or Linux/macOS alternatives. The log conversion tip references Visual Studio and a C# tool, both Windows-centric, without alternatives for other platforms. Additionally, the examples for viewing and analyzing logs focus on Excel and Power BI, which are primarily Windows tools, and these are mentioned before any cross-platform or open-source options. There are no Linux/macOS-specific instructions or parity in tooling or examples.
Recommendations
- Add Azure CLI examples for enabling diagnostic logging, which work on Linux/macOS and Windows.
- Include instructions or examples for using Bash or shell scripting to interact with logs.
- Reference cross-platform log conversion tools (e.g., Python scripts) or provide guidance for using jq or csvkit.
- Mention open-source or cross-platform data visualization tools (e.g., Grafana, Kibana) alongside Excel and Power BI.
- Explicitly state that all steps can be performed on Linux/macOS and provide any necessary platform-specific notes.
Application Gateway
Create Azure Application Gateway custom error pages
...blob/main/articles/application-gateway/custom-error.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides configuration instructions only using Azure PowerShell, with no mention of Azure CLI, Bash, or Linux/macOS-friendly alternatives. The PowerShell examples are presented as the sole programmatic method, which may create friction for users on Linux or macOS who typically use Azure CLI or scripting languages other than PowerShell.
Recommendations
- Add equivalent Azure CLI examples for configuring custom error pages at both global and listener levels.
- Explicitly mention that Azure PowerShell is cross-platform, but provide installation and usage notes for Linux/macOS users.
- Include Bash or shell script examples where appropriate.
- Reorder or parallelize example sections so that CLI and PowerShell instructions are presented together, not PowerShell-only.
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation is heavily focused on Azure PowerShell, with all deployment steps and code samples provided exclusively in PowerShell syntax. There are no Bash, Azure CLI, or Linux/macOS-specific instructions or examples. References to VM creation link only to Windows VM guides, and PowerShell is assumed as the primary tool throughout, creating friction for Linux/macOS users who typically use Bash and Azure CLI.
Recommendations
- Add equivalent Azure CLI (Bash) examples for all deployment steps, including resource group, VNet, subnet, public IP, and Bastion creation.
- Include links to Linux VM creation guides alongside Windows VM guides.
- Explicitly mention cross-platform options (e.g., Azure CLI, Bash, Cloud Shell) in the introduction and prerequisites.
- Reorganize sections to present both PowerShell and CLI/Bash options side-by-side or in parallel, rather than PowerShell-only.
- Clarify that Azure PowerShell can be used on Linux/macOS, but provide guidance for users who prefer CLI/Bash.
Cost Management Billing
Calculate Enterprise Agreement (EA) savings plan cost savings
...ling/savings-plan/calculate-ea-savings-plan-savings.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation exclusively uses Microsoft Excel for data preparation and calculation steps, with all screenshots and instructions tailored to Excel's Windows interface. There are no examples or guidance for Linux/macOS users or alternative spreadsheet tools (e.g., LibreOffice Calc, Google Sheets), despite a brief mention that other applications can be used.
Recommendations
- Provide explicit instructions and screenshots for at least one cross-platform spreadsheet tool (e.g., LibreOffice Calc, Google Sheets).
- Include notes or links to resources for opening and manipulating CSV files on Linux/macOS.
- Clarify any differences in formula syntax or filtering steps for non-Excel applications.
- Consider listing alternative command-line methods (e.g., using pandas in Python, csvkit) for users who prefer not to use GUI spreadsheet tools.
Dev Box
Stop Dev Boxes Automatically When User Disconnects
...rticles/dev-box/how-to-configure-stop-on-disconnect.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page focuses on stopping Dev Boxes when users disconnect from RDP sessions, a Windows-specific protocol. There is no mention of Linux/macOS remote access methods (e.g., SSH, VNC), nor any examples or guidance for non-Windows environments. The instructions and terminology are tailored exclusively to Windows users.
Recommendations
- Clarify whether stop-on-disconnect applies to non-Windows Dev Boxes and remote access methods such as SSH or VNC.
- Provide examples or notes for Linux/macOS users, including how disconnects are detected and handled for those platforms.
- Explicitly state platform limitations if the feature is Windows-only, or update the documentation to cover Linux/macOS parity if supported.
- Include references to Linux/macOS remote access patterns where relevant.
Automation
Use an alert to trigger an Azure Automation runbook
...utomation/automation-create-alert-triggered-runbook.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation page exhibits a strong Windows bias by exclusively using PowerShell for all code examples, setup instructions, and runbook creation steps. Prerequisites and links reference Windows-centric resources (e.g., 'quick-create-powershell' for VMs, Azure Az PowerShell module), and there are no Bash, CLI, or Linux/macOS-specific instructions or examples. The workflow assumes users are familiar with PowerShell and does not mention or demonstrate how to accomplish the same tasks using Azure CLI, Bash, or other cross-platform tools.
Recommendations
- Provide equivalent examples using Azure CLI (az) commands, which are cross-platform and work on Linux/macOS.
- Include instructions for creating and managing Automation runbooks using Bash or shell scripts, where supported.
- Reference Linux/macOS VM creation guides alongside Windows guides in prerequisites.
- Clarify which steps are platform-agnostic (e.g., portal actions) and which require adaptation for non-Windows environments.
- Add notes or links for installing and using Azure CLI on Linux/macOS.
- Consider providing sample runbooks written in Python, which is supported in Azure Automation and is cross-platform.
Automation
Disaster recovery for Azure Automation
...in/articles/automation/automation-disaster-recovery.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
windows_first
Summary
The documentation page exhibits a notable Windows bias, primarily through exclusive use of PowerShell scripts and workflows for migration tasks, with no mention of Bash, Python, or Linux-native alternatives. All scripting examples and instructions are centered on PowerShell, a Windows-centric tool, and references to installation steps and hybrid worker management default to Windows tabs and links. Linux users are left without direct guidance or parity in automation and migration workflows.
Recommendations
- Provide equivalent Bash or Python scripts for asset migration, or document how Linux users can perform these tasks using cross-platform tools (e.g., Azure CLI, REST API).
- Include Linux/macOS-specific instructions and examples alongside PowerShell, especially for runbook migration and hybrid worker setup.
- Ensure documentation tabs and links offer Linux-first or cross-platform options, not just Windows.
- Clarify which steps are platform-agnostic and which require Windows-specific tooling, and suggest alternatives for Linux users where possible.
Automation
Using a user-assigned managed identity for an Azure Automation account
...main/articles/automation/add-user-assigned-identity.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page is heavily biased toward Windows and PowerShell usage. Nearly all CLI examples use PowerShell cmdlets, with no Bash, Azure CLI, or Linux shell equivalents provided. Even REST API and ARM template sections rely on PowerShell for invocation and authentication. The order of presentation consistently puts PowerShell/Windows-centric approaches first, and there is no mention of Linux-specific tooling or cross-platform alternatives. Python is only briefly mentioned for runbooks, but not for setup or deployment tasks.
Recommendations
- Add equivalent Azure CLI (az) examples for all PowerShell cmdlets, especially for resource creation, role assignment, and identity management.
- Provide Bash or shell script examples for REST API calls, using curl or httpie, and show how to obtain access tokens on Linux/macOS.
- Include instructions for deploying ARM templates using Azure CLI (az deployment group create) and not just PowerShell.
- Clearly indicate which steps and scripts are cross-platform and which are Windows-specific.
- Consider reordering examples so that platform-neutral or cross-platform methods (portal, REST API, ARM template, Azure CLI) are presented before PowerShell.
- Add troubleshooting and verification steps for Linux/macOS environments.
Automation
Manage connections in Azure Automation
...lob/main/articles/automation/automation-connections.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. PowerShell (and Az module) examples are provided extensively and are presented before Python/Linux alternatives. The creation and management of connections are described primarily through PowerShell cmdlets, with no mention of equivalent Bash, Azure CLI, or Linux-native workflows. The 'Create a new connection' section only covers PowerShell and portal methods, omitting Linux/macOS command-line approaches. The Python section is present but secondary, and no Linux shell or Azure CLI examples are given.
Recommendations
- Add Azure CLI examples for creating and managing connections, especially for Linux/macOS users.
- Include Bash or shell script samples for common connection management tasks.
- Present examples in a more platform-neutral order (e.g., CLI, PowerShell, Python), or use tabs for each platform.
- Explicitly mention cross-platform compatibility and any platform-specific limitations.
- Clarify whether PowerShell examples can be run on PowerShell Core on Linux/macOS, or if they are Windows-only.
Automation
Create a standalone Azure Automation account
...les/automation/automation-create-standalone-account.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. Most automation and key management examples use Azure PowerShell, with no CLI (az) or Bash/Linux shell equivalents provided. PowerShell runbooks and tutorials are emphasized and listed first, while Python is mentioned only as an alternative. There are no explicit instructions or examples for Linux/macOS users, and Windows-centric tools (PowerShell) are referenced exclusively for command-line operations.
Recommendations
- Add equivalent Azure CLI (az) commands for key rotation and other management tasks alongside PowerShell examples.
- Provide Bash or shell script examples for Linux/macOS users where applicable.
- Reorder tutorial links to present Python and PowerShell examples equally, or clarify cross-platform options.
- Explicitly state that PowerShell Core is available on Linux/macOS, and link to installation instructions.
- Include notes or sections addressing Linux/macOS users, highlighting any platform-specific considerations.
Automation
Configure data based on STIG for Azure Automation State Configuration
...tomation/automation-dsc-configuration-based-on-stig.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation is heavily focused on Windows and PowerShell, with all examples and tooling references centered around Windows PowerShell DSC and the PowerSTIG project. There is no mention of Linux/macOS equivalents, and Linux onboarding is only referenced via a link, not in the main content. The article assumes familiarity with Windows tooling and does not provide guidance for Linux users.
Recommendations
- Include explicit examples and instructions for configuring Linux servers using Azure Automation State Configuration.
- Mention and link to Linux DSC resources, such as the OMI-based DSC agent for Linux.
- Clarify which features are Windows-only and provide Linux alternatives where possible.
- Add a section describing how Linux users can achieve STIG compliance using Azure Automation, including any limitations.
- Present onboarding steps for both Windows and Linux side-by-side, rather than referencing Linux only in a link.
Automation
Integrate Azure Automation State Configuration with Azure Monitor Logs
...main/articles/automation/automation-dsc-diagnostics.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation is heavily biased towards Windows, with all code examples and instructions using PowerShell and Az PowerShell modules. There are no CLI, Bash, or Linux/macOS-specific instructions or examples. The prerequisites and tooling (e.g., xDscDiagnostics, Az PowerShell) are Windows-centric, and there is no mention of Linux alternatives or parity. The guidance assumes the user is on a Windows environment, creating friction for Linux/macOS users.
Recommendations
- Add equivalent instructions and examples using Azure CLI (az) and Bash scripts for Linux/macOS users.
- Explicitly mention platform compatibility for each tool/module, and provide alternatives where possible.
- Include notes or sections for Linux/macOS users, clarifying any limitations or differences in workflow.
- If PowerShell Core is supported on Linux/macOS, clarify usage and provide cross-platform examples.
- Reference Linux onboarding and management documentation if available, or clarify end-of-life/retirement status for Linux DSC.
Automation
Configure data at scale for Azure Automation State Configuration
...cles/automation/automation-dsc-config-data-at-scale.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation is heavily focused on Windows and PowerShell, with all examples and instructions referencing Windows PowerShell DSC. There is no mention of Linux/macOS equivalents, nor are there examples or guidance for non-Windows platforms. The prerequisites and next steps are all Windows-centric, and Linux users are only referenced in a link, not in the main content.
Recommendations
- Add explicit instructions and examples for configuring data at scale using Linux/macOS-compatible DSC implementations (e.g., cross-platform PowerShell, Open Management Infrastructure).
- Clarify which steps are applicable to Linux/macOS and provide alternative commands or tools where needed.
- Include references to Linux DSC onboarding and configuration in the main body, not just as a link.
- Highlight any platform limitations or differences up front, so users know what to expect.
Automation
Convert configurations to composite resources for Azure Automation State Configuration
...articles/automation/automation-dsc-create-composite.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation is heavily focused on Windows PowerShell 5.1 and does not provide explicit guidance or examples for Linux/macOS users. All instructions and references are centered around PowerShell, with no mention of cross-platform alternatives or compatibility considerations for non-Windows environments. The introductory section and steps assume a Windows context, and links point to Windows-centric resources.
Recommendations
- Explicitly state whether the CompositeResource module and related tooling work on PowerShell Core (cross-platform) and/or Linux/macOS.
- Provide examples or instructions for running the process on Linux/macOS, including any required dependencies or differences.
- Clarify any limitations or required adaptations for non-Windows platforms, such as MOF file handling or DSC support.
- Include links to documentation about Linux DSC agent onboarding and configuration.
- Add a section comparing Windows and Linux workflows for composite resource creation and usage.
Automation
Enable Azure Automation State Configuration
.../main/articles/automation/automation-dsc-onboarding.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 and PowerShell examples are presented first and in greater detail, with Linux instructions often relegated to later sections or presented as addenda. Most configuration and onboarding steps rely on PowerShell scripts and Windows-specific tooling (WMF 5, PowerShell DSC cmdlets), with Linux instructions sometimes referencing Windows tools for initial setup. Linux examples are less detailed, and some advanced scenarios (custom metaconfigurations, remote onboarding) require Windows-based tools or PowerShell, creating friction for Linux/macOS users.
Recommendations
- Provide Linux/macOS examples alongside Windows/PowerShell instructions, not just as addenda.
- Expand Linux-specific guidance, including native Linux commands and scripts for all major steps (e.g., generating and applying metaconfigurations).
- Document Linux/macOS workflows that do not require access to Windows or PowerShell tools.
- Clarify which steps are platform-specific and offer parity in tooling or alternatives where possible.
- Include troubleshooting and status-checking instructions for Linux nodes, not just Windows.
- Where PowerShell is required, note any Linux-compatible options (e.g., PowerShell Core) or provide equivalent bash/python scripts.
IoT Hub
Get started with module identity and module twins (Portal)
...ob/main/articles/iot-hub/module-twins-portal-dotnet.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation is heavily oriented towards Windows development, specifically using Visual Studio and .NET. All examples and instructions assume the use of Windows tools (Visual Studio, NuGet GUI), with no mention of Linux/macOS equivalents (e.g., VS Code, CLI tools, .NET Core cross-platform usage). There are no Linux/macOS-specific instructions or examples, and Windows development patterns are presented exclusively and first.
Recommendations
- Add instructions for creating and running the .NET console app using cross-platform tools like VS Code or the .NET CLI.
- Include Linux/macOS-specific setup steps (e.g., installing .NET SDK, using terminal commands for NuGet package installation).
- Provide code snippets and screenshots for Linux/macOS environments.
- Clarify that the .NET SDK and Azure IoT libraries are cross-platform and provide guidance for non-Windows users.
- Mention alternative editors (VS Code, JetBrains Rider) and package managers (dotnet CLI) in addition to Visual Studio.
Migrate
Support for physical discovery and assessment in Azure Migrate and Modernize
...in/articles/migrate/migrate-support-matrix-physical.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation demonstrates a notable Windows bias. Windows tools and patterns (PowerShell, WinRM, WMI) are mentioned first and in more detail, with explicit requirements and links. PowerShell scripts are referenced for appliance setup, and Windows prerequisites are described extensively. Linux support is present, but Linux instructions are less detailed, often summarized as 'ensure SSH and commands are available.' SQL Server discovery and ASP.NET web app assessment are Windows-only, with Linux explicitly not supported. Example scripts and troubleshooting links are Windows-centric, with no Linux equivalents provided.
Recommendations
- Provide Linux-first or parallel examples for appliance setup (e.g., bash scripts or manual steps for Linux).
- Include troubleshooting and configuration links for Linux (e.g., SSH hardening, required package installation).
- Expand Linux server requirements with explicit command-line examples and permission setup instructions.
- Clarify limitations for Linux (e.g., SQL Server discovery, ASP.NET web apps) and suggest alternative approaches or roadmap for parity.
- Balance the order of presentation: alternate Windows and Linux instructions, or group by OS.
- Where PowerShell is referenced, offer Linux shell alternatives or note equivalent steps.
Nat Gateway
Manage a Standard V2 NAT Gateway
...lob/main/articles/nat-gateway/manage-nat-gateway-v2.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation provides detailed step-by-step instructions and code samples exclusively for the Azure portal and Azure PowerShell, with no mention or examples for Azure CLI, Bash, or other Linux/macOS-native tools. All command-line automation is shown using PowerShell cmdlets, which are Windows-centric, though PowerShell Core is cross-platform. There is no guidance for users who prefer or require Linux-native workflows.
Recommendations
- Add equivalent Azure CLI examples for all operations (create, update, remove NAT gateway, manage IPs/prefixes).
- Explicitly mention that PowerShell Core is available cross-platform, but also provide Bash/Azure CLI commands for parity.
- Consider including a tab for 'Azure CLI' alongside 'Azure PowerShell' and 'Azure portal' in all code sections.
- Link to Azure CLI installation and authentication guides for Linux/macOS users.
- Ensure terminology and instructions do not assume a Windows environment (e.g., avoid references to Windows-only tools or patterns).
Network Watcher
Filter Virtual Network Flow Logs (Preview)
...n/articles/network-watcher/vnet-flow-logs-filtering.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation exclusively uses Azure PowerShell cmdlets (New-AzNetworkWatcherFlowLog, Set-AzNetworkWatcherFlowLog, etc.) for all examples and instructions, with no mention of Azure CLI, REST API, or other cross-platform tools. This creates friction for Linux/macOS users who may prefer or require non-PowerShell workflows.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell cmdlet instructions.
- Reference REST API documentation for programmatic access from any platform.
- Explicitly state that PowerShell cmdlets can be run on Linux/macOS via PowerShell Core, but provide native CLI alternatives.
- Consider reordering or balancing examples so CLI and PowerShell are presented side-by-side.
Automation
Edit textual runbooks in Azure Automation
...articles/automation/automation-edit-textual-runbook.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation is heavily focused on PowerShell and Windows workflows. All command-line examples use Windows PowerShell, with Windows file paths and terminology. There are no examples or guidance for Linux/macOS users, such as using PowerShell Core (pwsh), cross-platform file paths, or Azure CLI alternatives. Windows tools and patterns are mentioned exclusively, and Linux parity is missing.
Recommendations
- Add examples using PowerShell Core (pwsh) with cross-platform file paths (e.g., /home/user/runbooks).
- Clarify that Az PowerShell module can be used on Linux/macOS, and provide instructions for those platforms.
- Include Azure CLI examples for runbook management, where possible.
- Explicitly mention any platform limitations or differences in the editor and cmdlet usage.
- Reorder or balance examples so Linux/macOS usage is shown alongside Windows.
Automation
Azure Automation network configuration details
...rticles/automation/automation-network-configuration.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation references Windows-specific DSC resources (e.g., WaitFor resources in the /powershell/dsc/reference/resources/windows/waitForAllResource link) when discussing node-to-node communication, without mentioning Linux equivalents or cross-platform alternatives. Windows terminology and links appear first and exclusively in the context of DSC resource examples.
Recommendations
- Include references to Linux DSC resources and documentation, such as links to cross-platform DSC modules or Linux-specific resources.
- Clarify whether the guidance applies equally to Linux nodes, and provide examples or notes for Linux/macOS environments where applicable.
- Add explicit mention of any differences in network configuration or resource requirements for Linux/macOS Hybrid Runbook Workers and State Configuration nodes.
- Where Windows-specific resources are mentioned, provide Linux alternatives or note if none exist.
Automation
Runbook authoring using VS Code in Azure Automation
...in/articles/automation/automation-runbook-authoring.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 operating systems are listed first in the supported OS matrix, and examples for directory paths use Windows-style (C:\abc) exclusively. The documentation focuses heavily on PowerShell, with specific mention of Windows PowerShell 5.1 and PowerShell Core, but provides no Linux/macOS-specific usage examples, troubleshooting, or directory path conventions. Debugging support is only described for PowerShell, with Python debugging relegated to a generic recommendation to use a debugger extension, without platform-specific guidance.
Recommendations
- Include Linux/macOS directory path examples alongside Windows (e.g., /home/user/abc).
- Provide explicit instructions or screenshots for changing directories and configuring settings on Linux/macOS.
- Add troubleshooting tips or notes for Linux/macOS users, especially regarding PowerShell and Python environment setup.
- Clarify any platform-specific limitations or differences in feature support.
- Balance the order of OS mentions and examples so Linux/macOS are not always listed after Windows.
- Offer parity in debugging guidance for Python runbooks on Linux/macOS.
Automation
Runbook execution in Azure Automation
...in/articles/automation/automation-runbook-execution.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation is heavily focused on PowerShell runbooks and Windows-centric tools and patterns. All code examples use PowerShell syntax, and references to modules, environment variables, and file paths are Windows-specific (e.g., C:\temp, $env:TEMP). Windows tools like WinSCP.exe and IIS are mentioned as examples, with no Linux equivalents or cross-platform alternatives provided. There are no Bash, Python, or Linux shell examples, and Linux-specific considerations are only briefly mentioned in passing (e.g., Defender for Cloud constraints).
Recommendations
- Provide equivalent Linux/macOS examples for runbook scripting, such as Bash or Python runbooks.
- Include Linux-specific file paths and environment variable usage (e.g., /tmp instead of C:\temp or $env:TEMP).
- Mention Linux tools and modules (e.g., scp, Apache/Nginx administration) alongside Windows tools like WinSCP and IIS.
- Clarify which features and modules are cross-platform, and explicitly note any Windows-only limitations.
- Add examples and guidance for managing Linux resources and handling Linux-specific errors or authentication scenarios.
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page generally covers both Windows and Linux scenarios, but there is a notable Windows bias in the Python interpreter selection section. Windows-specific environment variables and file paths (e.g., C:\Python2\python.exe) are described in detail, while Linux equivalents (e.g., /usr/bin/python3, $PATH usage) are not mentioned or illustrated. Windows Hybrid Runbook Worker configuration is explained first and in more depth, with Linux only referenced briefly. No Linux-specific examples or instructions are provided for Python interpreter selection or environment variable setup.
Recommendations
- Add explicit Linux examples for configuring Python interpreter selection, including environment variable usage and typical Linux file paths (e.g., /usr/bin/python3).
- Describe how Linux Hybrid Runbook Workers locate Python interpreters, including any differences from Windows.
- Ensure that instructions and examples for both platforms are presented in parallel, or alternate which is shown first.
- Include troubleshooting tips for Linux users similar to those provided for Windows.
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 tools are referenced first and more frequently, especially in backup and retention sections. Linux guidance is present but less detailed, and Linux-specific examples are limited to TLS configuration. Several cmdlets and procedures are described only for Windows/PowerShell, with no direct Linux or cross-platform alternatives provided.
Recommendations
- Provide Linux/macOS equivalents for PowerShell cmdlets, such as CLI or REST API examples for exporting runbooks and DSC configurations.
- Include Linux-first or side-by-side examples for asset management and backup procedures.
- Reference cross-platform tools (e.g., Azure CLI, az automation) before or alongside Windows/PowerShell tools.
- Clarify which procedures are platform-agnostic and which are Windows-specific.
- Expand Linux guidance beyond TLS configuration, especially in backup and retention sections.
Automation
Migrate from Orchestrator to Azure Automation (Beta)
...ticles/automation/automation-orchestrator-migration.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation is heavily focused on Windows and PowerShell, with all examples, tooling, and migration steps centered around Windows technologies. There is no mention of Linux/macOS equivalents, nor are there examples or guidance for users on those platforms. The migration process assumes the use of Windows PowerShell, Windows file paths, and Windows-based modules and tools, creating friction for Linux/macOS users.
Recommendations
- Provide equivalent instructions and examples for Linux/macOS users, including how to run PowerShell Core (pwsh) on those platforms.
- Clarify whether the migration toolkit and Runbook Converter can be used on Linux/macOS, and if not, offer alternatives or workarounds.
- Use platform-neutral file path examples or show both Windows and Linux/macOS paths.
- Document any limitations or requirements for Linux/macOS users explicitly.
- Include notes about PowerShell Core compatibility for cmdlets and modules mentioned.
- If tools are Windows-only, suggest cross-platform alternatives or containerized approaches.
Automation
Use Azure Automation runbooks and modules in PowerShell Gallery
...main/articles/automation/automation-runbook-gallery.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a strong Windows and PowerShell bias. All examples and workflows focus exclusively on PowerShell and Windows-centric tools, with no mention of Linux/macOS equivalents or cross-platform considerations. Scenarios and sample runbooks reference Windows Azure VMs and PowerShell modules, and there are no Bash, Python, or Linux-native instructions or examples. The documentation assumes users are familiar with PowerShell and Windows conventions, making it less accessible for Linux/macOS users.
Recommendations
- Include examples and instructions for Linux/macOS users, such as using Bash or Python runbooks.
- Highlight cross-platform compatibility of Azure Automation and clarify which features are Windows-only.
- Provide sample runbooks for Linux Azure VMs (e.g., file copy to/from Linux VMs).
- Add guidance on managing modules and runbooks with Linux-native tools and workflows.
- Explicitly state any limitations or differences for non-Windows platforms.
Automation
Handle errors in Azure Automation graphical runbooks
...omation/automation-runbook-graphical-error-handling.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation is heavily focused on Windows PowerShell, with all examples and error handling patterns described in terms of PowerShell cmdlets and syntax. There is no mention of Linux or cross-platform alternatives, nor are Bash or Python examples provided. Windows tools and terminology (e.g., PowerShell, Write-Warning, Start-AzVM) are used exclusively, and no Linux/macOS-specific guidance is offered.
Recommendations
- Add equivalent examples using Bash, Python, or other supported languages for graphical runbooks.
- Clarify whether graphical runbooks and error handling features are available and work identically on Linux/macOS hybrid workers.
- Mention cross-platform cmdlets or automation modules if available.
- Provide guidance on handling errors in non-PowerShell activities (e.g., Bash, Python) within graphical runbooks.
- Explicitly state any platform limitations or differences in error handling behavior.
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. PowerShell (a Windows-centric technology) is presented first and in greatest detail, with multiple sections and examples focused on Windows PowerShell and its workflows. Many examples and known issues reference Windows file paths (e.g., C:\modules), environment variables (e.g., TEMP), and Windows-specific behaviors. Linux support is mentioned only in passing, with no Linux-specific examples, troubleshooting, or guidance. Python runbooks mention Linux only briefly, and graphical runbooks are explicitly unsupported on Linux Hybrid Runbook Workers. There are no code samples or instructions tailored for Linux/macOS users.
Recommendations
- Add Linux/macOS-specific examples for PowerShell (especially for Hybrid Runbook Workers), including file paths, environment variables, and troubleshooting steps.
- Explicitly document differences and limitations for Linux Hybrid Runbook Workers, including supported features and workarounds.
- Provide parity in examples: for every Windows-centric example (e.g., C:\modules), include the equivalent Linux/macOS example (e.g., /usr/src/PSModules).
- Clarify which features/tools are Windows-only and suggest alternatives or workarounds for Linux/macOS users.
- Expand Python runbook documentation to include more Linux-specific guidance, especially for package management and environment setup.
- Reorder sections or provide parallel guidance so Linux/macOS users do not have to sift through Windows-specific content to find relevant information.
Automation
Track updated files with an Azure Automation watcher task
...s/automation/automation-scenario-using-watcher-task.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation is strongly biased toward Windows environments, with all examples and instructions using PowerShell and Windows-style paths (e.g., D:\examplefiles). There are no Linux or macOS equivalents provided for file creation, directory paths, or hybrid worker setup. The only scripting language mentioned is PowerShell, and the runbooks referenced are PowerShell-based, with no Bash or Python alternatives. The instructions for triggering watcher tasks explicitly require remoting into a worker and using PowerShell commands, which may not be directly applicable to Linux/macOS hybrid workers.
Recommendations
- Add Linux/macOS examples for file creation (e.g., using 'touch ExampleFile1.txt' in Bash).
- Clarify whether hybrid runbook workers can run on Linux, and if so, provide setup and usage instructions for non-Windows environments.
- Include notes on path formats for Linux/macOS (e.g., '/home/examplefiles' instead of 'D:\examplefiles').
- Offer alternative runbook examples using Bash or Python, if supported.
- Explicitly state any platform limitations for watcher tasks and hybrid runbook workers.
Automation
Use Microsoft Entra ID in Azure Automation to authenticate to Azure
...ob/main/articles/automation/automation-use-azure-ad.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation is heavily focused on PowerShell and Windows-centric tools and patterns. All code examples and module references are PowerShell-specific, with no mention of Linux/macOS equivalents or cross-platform scripting options. Windows PowerShell is referenced explicitly, and there are no Bash, Azure CLI, or cross-platform automation examples provided.
Recommendations
- Add equivalent examples using Azure CLI (az) commands, which are cross-platform and widely used on Linux/macOS.
- Clarify which steps are PowerShell-specific and provide guidance or links for Linux/macOS users.
- Include Bash or Python runbook examples, or reference the ability to use these languages in Azure Automation.
- Mention that Azure Automation supports Python runbooks and provide a simple Python example for credential management.
- Reorder sections or explicitly state that PowerShell examples are for all platforms where PowerShell Core is available, or provide platform-specific instructions.
Automation
Automation services in Azure - overview
...s/blob/main/articles/automation/automation-services.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation demonstrates a moderate Windows bias, primarily through the heavy emphasis on PowerShell for automation, frequent references to Windows-centric tools (e.g., registry, Active Directory, SQL Server), and by mentioning PowerShell before Python or other cross-platform scripting options. While Linux support is acknowledged (especially in Azure Automanage), examples and scenarios are often Windows-oriented, and Linux-specific guidance or parity is lacking.
Recommendations
- Provide Linux-specific examples and scenarios alongside Windows ones, especially for Azure Automation and in-guest management.
- Highlight Bash, Python, and other cross-platform scripting options equally with PowerShell, including sample runbooks and integration patterns.
- Explicitly mention Linux equivalents for Windows tools (e.g., systemd, cron, Linux file system monitoring) in automation scenarios.
- Clarify which features and modules are cross-platform and which are Windows-only, to help users plan accordingly.
- Add links to Linux-focused documentation or tutorials for Azure Automation, Functions, and Automanage.
Automation
Migration guidance from Change Tracking and inventory using Log Analytics to Azure Monitoring Agent
...g/guidance-migration-log-analytics-monitoring-agent.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides migration guidance for both Windows and Linux VMs, but the only scripting example is a PowerShell script, which is Windows-centric (despite PowerShell Core being cross-platform). There are no Bash or Linux-native CLI examples, and the prerequisites and instructions for scripting focus on PowerShell modules and patterns. The portal-based instructions are platform-neutral, but scripting and automation guidance is biased towards Windows/PowerShell users. Linux users may face friction due to lack of native examples.
Recommendations
- Provide equivalent Bash or shell script examples for Linux users, especially for automation and bulk migration scenarios.
- Include Azure CLI instructions for migration tasks where possible, as Azure CLI is cross-platform and widely used on Linux.
- Explicitly document any Linux-specific considerations or steps, such as agent removal or DCR assignment, in addition to Windows steps.
- Clarify which steps or scripts are supported on Linux/macOS, and provide troubleshooting guidance for non-Windows environments.
- Consider reordering examples so that platform-neutral or Linux instructions are presented alongside or before Windows/PowerShell examples.
Automation
Context switching in Azure Automation
...ocs/blob/main/articles/automation/context-switching.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation is heavily focused on Azure PowerShell cmdlets and runbooks, with all examples and recommendations using PowerShell syntax and tools. There is no mention of Linux-native automation tools, Bash, CLI equivalents, or cross-platform scripting approaches. This creates friction for Linux/macOS users who may prefer or require non-PowerShell solutions.
Recommendations
- Add equivalent Azure CLI (az) examples for context management and runbook automation.
- Include Bash or Python script snippets demonstrating context switching and management.
- Explicitly state platform requirements and provide guidance for Linux/macOS users.
- Mention cross-platform automation options and how context switching issues manifest outside PowerShell.
Automation
Delete an Azure Automation Run As account
...blob/main/articles/automation/delete-run-as-account.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_first
Summary
The documentation page focuses on deleting Azure Automation Run As accounts primarily through PowerShell or the Azure portal, both of which are Windows-centric. There are no examples or instructions for Linux/macOS users (e.g., Azure CLI, Bash), and PowerShell is mentioned as the main scripting tool. The portal instructions also implicitly favor Windows due to common usage patterns.
Recommendations
- Add equivalent instructions and examples using Azure CLI, which is cross-platform and commonly used on Linux/macOS.
- Include Bash script samples for deleting Run As accounts.
- Explicitly mention that PowerShell Core is available on Linux/macOS if PowerShell is required, and provide platform-agnostic command examples.
- Reorder examples so that cross-platform tools (Azure CLI) are shown before or alongside PowerShell.
- Clarify any portal steps that may differ for non-Windows users (e.g., browser compatibility, UI differences).
Automation
Manage your Azure Automation account
...e-docs/blob/main/articles/automation/delete-account.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides detailed instructions for managing Azure Automation accounts primarily via the Azure portal and Azure PowerShell. PowerShell examples are given for deletion and solution removal, but there are no equivalent Azure CLI or Bash examples, nor are Linux/macOS-specific instructions or considerations mentioned. PowerShell is a Windows-centric tool, and its usage is presented before any alternative command-line options. This creates friction for Linux/macOS users who may prefer or require Azure CLI or Bash.
Recommendations
- Add Azure CLI examples for all PowerShell commands, especially for deleting Automation accounts and removing Log Analytics solutions.
- Explicitly mention that Azure CLI can be used from Linux/macOS and provide syntax parity.
- Where PowerShell is referenced, clarify cross-platform availability or link to installation guides for non-Windows systems.
- Ensure that command-line examples are presented in parallel tabs (PowerShell, CLI, REST) and not just PowerShell.
- Add a section or note on managing Automation accounts from Linux/macOS environments.
Automation
Disable system-assigned managed identity for Azure Automation account
.../automation/disable-managed-identity-for-automation.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation provides a detailed PowerShell-based example for disabling a system-assigned managed identity via REST API, relying on Windows-specific tools and cmdlets. There are no equivalent examples or instructions for Linux/macOS users (e.g., using curl, Azure CLI, or bash), and the workflow assumes familiarity with PowerShell and Windows authentication patterns.
Recommendations
- Add Linux/macOS examples using curl or HTTPie to send the PATCH request.
- Provide Azure CLI equivalents for authentication and REST API invocation.
- Include instructions for obtaining an access token on Linux/macOS (e.g., via Azure CLI).
- Present cross-platform examples side-by-side or indicate which steps are OS-agnostic.
- Avoid assuming PowerShell as the default scripting environment.
Automation
Using a system-assigned managed identity for an Azure Automation account
...s/automation/enable-managed-identity-for-automation.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation page is heavily biased towards Windows and PowerShell usage. All code examples for enabling and using managed identities (except one Python example) are written in PowerShell, with no Bash, CLI, or Linux-native scripting alternatives. Windows tools and paths are mentioned first or exclusively in several places, and Linux instructions are minimal and less detailed. This bias creates friction for Linux/macOS users, who may struggle to follow or adapt the steps without additional guidance.
Recommendations
- Provide Azure CLI (az) examples alongside PowerShell for all major tasks, including enabling managed identity, assigning roles, and authenticating.
- Include Bash shell script examples for REST API calls, using curl or httpie, especially for token acquisition and ARM template deployment.
- Add Linux/macOS-specific instructions for file paths, environment variables, and runbook worker setup.
- Ensure all steps that use PowerShell have equivalent CLI or Bash alternatives, and present them in parallel or alternate sections.
- Mention cross-platform tools (e.g., Azure CLI, curl) before or alongside Windows-specific tools.
- Clarify which steps are platform-agnostic and which are Windows-specific, and provide guidance for Linux/macOS users where necessary.
Automation
Deploy an extension-based Windows or Linux User Hybrid Runbook Worker in Azure Automation
...ation/extension-based-hybrid-runbook-worker-install.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page, while claiming to support both Windows and Linux Hybrid Runbook Workers, demonstrates several Windows biases. Windows-specific tools (PowerShell 5.1, .NET Framework) are emphasized, with PowerShell-based examples and cmdlets shown first and in greater detail. ARM/Bicep/CLI/REST examples focus almost exclusively on Windows VM creation and extension installation, with Linux equivalents either missing or only referenced generically. Folder permissions and troubleshooting notes are Windows-centric, and the Bicep/ARM templates only provision Windows VMs. Linux-specific requirements and patterns are less detailed, and Linux extension installation is not covered in the infrastructure-as-code sections.
Recommendations
- Provide equivalent Linux VM creation and extension installation examples in Bicep, ARM templates, CLI, and REST API sections.
- Include Linux-specific troubleshooting steps and folder permission guidance, similar to the Windows coverage.
- Add Linux-first or side-by-side examples for PowerShell, CLI, and REST API usage, not just Windows-first.
- Expand documentation of Linux prerequisites, supported tools, and hardening/permissions requirements.
- Ensure infrastructure-as-code samples (Bicep/ARM) include Linux VM images and extension installation.
- Clarify when PowerShell Core is required or supported for Linux, and provide Bash/SSH alternatives where applicable.
Automation
Disable local authentication in Azure Automation
...in/articles/automation/disable-local-authentication.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-based examples for disabling local authentication in Azure Automation. All command-line instructions use PowerShell cmdlets, with no mention of Linux/macOS alternatives (e.g., Bash, curl, or Azure CLI). The PowerShell example is presented as the primary (and only) method, which may create friction for Linux/macOS users who do not have access to PowerShell or prefer native tools.
Recommendations
- Add equivalent examples using Azure CLI and/or REST API calls with curl for Linux/macOS users.
- Explicitly mention platform-agnostic alternatives and clarify that PowerShell is not required if using REST API directly.
- Reorder or parallelize examples so that Linux/macOS methods are shown alongside or before Windows/PowerShell examples.
- Provide guidance on authentication and prerequisites for non-Windows environments.
Automation
Move your Azure Automation account to another subscription
...s/blob/main/articles/automation/how-to/move-account.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation provides command-line examples exclusively using Azure PowerShell cmdlets (Remove-AzResource, Remove-AzActionGroup), with no equivalent Azure CLI or REST API examples. This creates friction for Linux/macOS users, who are more likely to use Azure CLI or REST API. The portal instructions are platform-neutral, but all scripting guidance is Windows/PowerShell-centric.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell commands shown (e.g., az resource delete, az monitor action-group delete).
- Include REST API sample requests for resource deletion and action group removal.
- Explicitly mention that PowerShell examples require installation on non-Windows platforms and link to cross-platform installation guides.
- Present CLI and PowerShell examples side-by-side or alternate their order to avoid Windows-first bias.
Automation
Manage Python 3 packages in Azure Automation
...ocs/blob/main/articles/automation/python-3-packages.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
powershell_heavy
windows_tools
Summary
The documentation demonstrates a moderate Windows bias. Windows and PowerShell examples are presented for Python 3.8 package management, with explicit instructions to use a Windows machine for wheel generation, while Linux instructions are only given for Python 3.10. PowerShell cmdlets are provided for package management, but no equivalent Linux CLI or Bash examples are offered. Windows terminology and tooling (e.g., win_amd64, PowerShell) appear before or instead of Linux alternatives, potentially creating friction for Linux/macOS users.
Recommendations
- Provide Linux/macOS equivalents for all package management steps, especially for Python 3.8 (e.g., show how to generate wheels on Linux for 3.8).
- Include Bash/Azure CLI examples for package operations alongside PowerShell cmdlets.
- Present Linux and Windows instructions in parallel or in tabs, rather than Windows-first.
- Clarify which steps are OS-agnostic and which require specific platforms, and offer guidance for both.
- Add explicit notes or sections for macOS users where relevant.
Automation
Manage databases in Azure SQL databases using Azure Automation
...articles/automation/manage-sql-server-in-automation.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation is heavily focused on PowerShell and Windows-centric tools, with all code samples and automation instructions using PowerShell cmdlets. There are no examples or guidance for Linux/macOS users, such as using Bash, Azure CLI, or cross-platform scripting. The instructions for Hybrid Runbook Worker setup and module installation are also PowerShell-specific, and Windows terminology (e.g., elevated PowerShell prompt) is used throughout.
Recommendations
- Provide equivalent examples using Azure CLI and Bash scripts for Linux/macOS users.
- Include instructions for installing required modules on Linux/macOS Hybrid Runbook Workers.
- Clarify cross-platform compatibility of Azure Automation and Hybrid Runbook Worker, and document any OS-specific limitations.
- Present examples for both Windows and Linux/macOS environments, or explicitly state if only Windows is supported.
- Add notes or links to official documentation for Linux/macOS users on connecting to Azure SQL and managing identities.
Automation
Migrate an existing agent-based hybrid workers to extension-based-workers in Azure Automation
...g-agent-based-hybrid-worker-to-extension-based-workers.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation demonstrates a notable Windows bias. In critical migration and deployment sections, examples and templates (Bicep, ARM, PowerShell) are exclusively or primarily for Windows VMs, with explicit references to Windows images, PowerShell, and Windows-specific extension types. Linux equivalents are either missing, mentioned as alternatives without examples, or relegated to notes. PowerShell is emphasized as the main scripting tool, with Linux instructions and bash commands only present in the removal section. The use of 'HybridWorkerForWindows' as the default extension type in code samples further reinforces this bias.
Recommendations
- Provide full Bicep and ARM template examples for Linux VMs, including image references and extension types (e.g., 'HybridWorkerForLinux').
- Include PowerShell and Azure CLI commands specifically for Linux VMs, demonstrating installation and management of the Hybrid Worker extension.
- Ensure REST API examples clearly show both Windows and Linux extension types, with sample payloads for each.
- Present Linux and Windows instructions side-by-side or in parallel tabs, rather than Windows-first or Windows-only.
- Expand Linux prerequisites and troubleshooting sections to match the depth of Windows coverage.
- Reference Linux-specific documentation and tools where appropriate, not just Windows/PowerShell.
Automation
Migrate from a Run As account to Managed identities
...automation/migrate-run-as-accounts-managed-identity.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation is heavily biased toward PowerShell-based automation and examples, with all code samples and migration steps using PowerShell cmdlets (e.g., Connect-AzAccount, Get-AzResourceGroup). There are no examples or guidance for users who may use Python, Bash, or other scripting languages commonly used on Linux/macOS. The documentation assumes the use of PowerShell and Windows-centric tools, which may not be familiar or available to Linux/macOS users, especially for hybrid worker scenarios.
Recommendations
- Add equivalent examples using Azure CLI (az) commands, which are cross-platform and commonly used on Linux/macOS.
- Provide sample scripts in Python (using the Azure SDK for Python) for authenticating with managed identities in Azure Automation.
- Explicitly mention that PowerShell Core (pwsh) is available cross-platform, and clarify if the scripts are compatible with PowerShell Core on Linux/macOS.
- Include notes or links for Linux/macOS users on how to set up and use PowerShell or alternative tools in Azure Automation.
- Where possible, provide Bash or shell script equivalents for common tasks, especially for role assignment and resource queries.
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is repeatedly emphasized as the primary automation language, especially in the context of Desired State Configuration (DSC) and runbooks. Windows-centric tools and scenarios (Active Directory, SharePoint Server, SQL Server) are mentioned, and PowerShell Gallery integration is highlighted before Python support. While Linux support is acknowledged, examples and tooling references are predominantly Windows-focused, and Linux-specific patterns or tools are not equally detailed.
Recommendations
- Provide Linux-specific examples and scenarios, such as automating common Linux services (e.g., Apache, Nginx, systemd units) alongside Windows examples.
- Highlight Bash, Shell, or Python runbooks with equal prominence to PowerShell, including links to relevant galleries or repositories for Linux scripts.
- Expand on Linux configuration management options, such as Ansible or native Linux DSC resources, and clarify how Azure Automation integrates with them.
- List Linux tools and patterns (e.g., cron, systemd timers) in shared capabilities and common scenarios sections.
- Ensure that documentation for modules, galleries, and hybrid worker setup includes Linux-specific instructions and troubleshooting.
Automation
Manage Python 2 packages in Azure Automation
...-docs/blob/main/articles/automation/python-packages.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides explicit instructions for downloading Python package dependencies only on Windows, with no equivalent Linux/macOS example. The command given is for Windows (using a Windows path and pip executable), and the text specifies 'On a Windows 64-bit machine...' without mentioning Linux or macOS alternatives. This creates friction for non-Windows users who need to perform the same task.
Recommendations
- Add equivalent instructions and examples for Linux/macOS users, such as using 'pip download' in a bash shell.
- Clarify that the process is cross-platform and provide commands for both Windows and Linux/macOS.
- Avoid language that implies Windows is required unless it is truly the only supported platform.
- Consider listing Linux/macOS instructions before or alongside Windows instructions to avoid implicit prioritization.
Automation
Configure runbook input parameters in Azure Automation
...b/main/articles/automation/runbook-input-parameters.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 by focusing almost exclusively on PowerShell-based examples and workflows, which are native to Windows. All code samples, parameter configuration, and runbook invocation instructions use PowerShell or Windows-centric tools and patterns. There are no Linux shell (bash), cross-platform CLI, or macOS-specific examples for starting or interacting with runbooks. Even SDK and REST API sections use Windows-centric terminology (e.g., GUID creation in PowerShell). Python runbooks are mentioned but lack concrete examples for Linux/macOS users. This bias may create friction for users on Linux or macOS platforms who do not use PowerShell.
Recommendations
- Add equivalent examples using Azure CLI (az) for starting runbooks and passing parameters, which is cross-platform.
- Provide bash or shell script examples for Linux/macOS users, especially for tasks like passing JSON objects.
- Clarify which steps and tools are platform-agnostic and which are Windows-specific.
- Include notes or sections for macOS/Linux users, such as how to generate GUIDs, manage JSON files, and invoke REST APIs without PowerShell.
- Expand Python runbook examples to show parameter passing from Linux/macOS environments.
Automation
Manage certificates in Azure Automation
...n/articles/automation/shared-resources/certificates.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation page is heavily focused on PowerShell cmdlets and Windows-centric tooling for certificate management in Azure Automation. All CLI examples are in PowerShell, and Windows tools (e.g., Add-AzureCertificate, New-AzAutomationCertificate) are referenced exclusively. There are no Bash, Azure CLI, or Linux-native examples for certificate upload or management. Python examples are provided for runbook access, but not for certificate creation or upload. The documentation assumes the use of Windows cryptographic providers and PowerShell workflows, creating friction for Linux/macOS users.
Recommendations
- Add equivalent Azure CLI and/or Bash examples for certificate creation, upload, and management.
- Document Linux/macOS workflows for preparing and uploading certificates, including OpenSSL usage.
- Clarify cross-platform compatibility of certificate providers and formats.
- Provide guidance for Linux users on how to interact with Azure Automation certificates outside of PowerShell.
- List Python or REST API methods for certificate asset creation and management.
Automation
Manage credentials in Azure Automation
...in/articles/automation/shared-resources/credentials.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation page is heavily focused on Windows PowerShell and related cmdlets for managing credentials in Azure Automation. All CLI examples are PowerShell-based, with no Bash, Linux shell, or cross-platform CLI alternatives provided. Windows tools and patterns (e.g., PSCredential, PowerShell modules) are mentioned exclusively and before Python equivalents. There is no mention of Linux/macOS-specific workflows or guidance for users who do not have access to Windows/PowerShell environments.
Recommendations
- Add Azure CLI examples for credential management, which are cross-platform and work on Linux/macOS.
- Include Bash or shell script snippets for common credential operations where possible.
- Explicitly state platform requirements for PowerShell examples and provide alternatives for non-Windows users.
- Document how Linux/macOS users can interact with Azure Automation credentials (e.g., via REST API, Azure CLI, or Python SDK).
- Reorder sections so that cross-platform methods (Azure portal, Azure CLI, Python SDK) are presented before or alongside Windows-specific tools.
Automation
Remove user-assigned managed identity for Azure Automation account
...n/articles/automation/remove-user-assigned-identity.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 by exclusively providing PowerShell-based examples and instructions for command-line and scripting tasks. There are no Linux/macOS shell (e.g., Bash, Azure CLI) equivalents, and PowerShell is presented as the default tool for REST API calls and verification steps. Windows tools and patterns (such as PowerShell cmdlets and Windows-style file paths) are used throughout, with no mention of Linux-native alternatives or cross-platform approaches.
Recommendations
- Add Azure CLI examples for all operations currently shown only in PowerShell.
- Provide Bash shell examples for REST API calls (e.g., using curl) and verification steps.
- Use platform-neutral file path syntax or clarify path differences for Linux/macOS.
- Explicitly state cross-platform support for all steps, and note any OS-specific requirements.
- Include notes or links for installing and using PowerShell Core on Linux/macOS if PowerShell must be used.
Automation
Runtime Environment in Azure Automation
...in/articles/automation/runtime-environment-overview.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 emphasized as the primary scripting language, with multiple runtime versions listed and examples focused on PowerShell environments. Azure CLI usage is described only in the context of PowerShell 7.4, with no mention of Bash or native Linux shell environments. Package management examples and references (e.g., PSGallery) are Windows-centric, and Linux/macOS equivalents (such as Bash scripting, pip for Python, or native shell usage) are not discussed. The documentation does not provide Linux/macOS-specific guidance or examples, making it less accessible for non-Windows users.
Recommendations
- Include examples and guidance for using Azure CLI in Bash or native Linux/macOS shells.
- Add explicit instructions for Python runbooks, including package management via pip and usage in Linux/macOS environments.
- Reference Linux/macOS package sources (e.g., PyPI) and shell scripting alternatives alongside PowerShell.
- Clarify cross-platform support and limitations for each runtime environment.
- Provide parity in documentation structure, listing Linux/macOS options and examples before or alongside Windows/PowerShell ones.
Automation
Manage modules in Azure Automation
...b/main/articles/automation/shared-resources/modules.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation is heavily focused on PowerShell modules and Windows-centric tools, with most examples and instructions tailored to Windows environments. Internal cmdlets and modules are explicitly unavailable on Linux Hybrid Runbook Workers, and there are no equivalent Linux or cross-platform examples provided. The guidance for module authoring, importing, and management is almost entirely PowerShell/Windows-oriented, with only brief mention of Python modules and no detailed Linux/macOS instructions or parity.
Recommendations
- Add equivalent Linux/macOS examples for module management, including CLI and scripting approaches using Bash or Azure CLI.
- Document limitations and alternatives for Linux Hybrid Runbook Workers more prominently, and provide guidance for Linux users where Windows-only features are unavailable.
- Include cross-platform best practices for authoring and importing modules, such as using .NET Core or PowerShell Core for compatibility.
- Expand the Python section to include more detail and parity with PowerShell instructions.
- Clearly mark Windows-only features and suggest Linux/macOS alternatives or workarounds.
Automation
Manage schedules in Azure Automation
...main/articles/automation/shared-resources/schedules.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a strong bias towards Windows and PowerShell. All CLI examples use PowerShell cmdlets, with no mention or examples of Bash, Azure CLI, or cross-platform scripting. The use of PowerShell-specific constructs (e.g., .NET types, PowerShell syntax) further limits applicability for Linux/macOS users. Windows/PowerShell tools are referenced exclusively and presented before any mention of alternatives. There are no Linux/macOS-specific instructions or parity examples.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell cmdlets shown, using Bash syntax where appropriate.
- Explicitly state cross-platform options for managing schedules (e.g., Azure CLI, REST API) and link to relevant documentation.
- Include notes or sections clarifying which instructions are platform-agnostic and which are Windows/PowerShell-specific.
- Provide guidance for Linux/macOS users on installing and using Azure CLI or REST API for schedule management.
- Where PowerShell is required, clarify how to use PowerShell Core on Linux/macOS, or offer alternatives.
Automation
Manage variables in Azure Automation
...main/articles/automation/shared-resources/variables.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 (and specifically Windows PowerShell) is referenced as the primary scripting environment for variable management, with all CLI examples given in PowerShell. Windows-specific terminology and cmdlets (e.g., 'Windows PowerShell', 'Hybrid Runbook Worker') are used throughout, and there are no Bash, Azure CLI, or Linux shell examples. The Python section is included, but only as runbook code, not as general CLI usage. No Linux/macOS shell equivalents or guidance are provided for users who may prefer or require non-Windows environments.
Recommendations
- Add Azure CLI examples for variable management tasks alongside PowerShell examples.
- Clarify which cmdlets and features are available cross-platform (Windows, Linux, macOS) and which are Windows-only.
- Provide Bash or shell script examples for common tasks, or explicitly state if such functionality is unavailable.
- Avoid using 'Windows PowerShell' as the default term; use 'PowerShell' and specify platform differences where relevant.
- Include guidance for Linux/macOS users on how to perform equivalent operations, or note any limitations.
- Add a section on platform compatibility for Automation features and tools.
Automation
Start a runbook in Azure Automation
...e-docs/blob/main/articles/automation/start-runbooks.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 by providing only Windows PowerShell examples and focusing on Windows tools (PowerShell cmdlets) for command-line automation. There are no Linux/macOS CLI examples (e.g., Azure CLI, Bash), and PowerShell is presented as the primary scripting method. The page does not mention cross-platform alternatives or clarify PowerShell Core support, and Windows-centric terminology is used throughout.
Recommendations
- Add equivalent Azure CLI examples for starting and managing runbooks, which work natively on Linux/macOS.
- Clarify whether PowerShell Core (cross-platform) is supported, and provide examples if so.
- Include Bash or REST API examples for common tasks, especially for parameter passing and job tracking.
- Reorder sections so that cross-platform methods (Azure CLI, REST API) are presented before or alongside Windows PowerShell.
- Explicitly mention platform compatibility for each method, helping users choose the right tool for their OS.
Automation
Troubleshoot agent-based Hybrid Runbook Worker issues in Azure Automation
...icles/automation/troubleshoot/hybrid-runbook-worker.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. Troubleshooting steps and examples are frequently presented for Windows first, with PowerShell and Windows-specific tools (e.g., registry edits, event logs, config files in Windows paths) featured prominently. Linux troubleshooting is covered in a separate section, but many scenarios (such as module updates, config file changes, and proxy issues) provide only Windows-specific instructions or examples, with Linux equivalents missing or less detailed. Windows tools and patterns (e.g., registry, event logs, PowerShell cmdlets) are mentioned exclusively or before Linux alternatives.
Recommendations
- Ensure every troubleshooting scenario includes both Windows and Linux instructions/examples where applicable.
- Provide Linux equivalents for Windows-specific steps (e.g., config file locations, service management commands, log file paths, authentication methods).
- Present Windows and Linux troubleshooting steps in parallel, rather than segregating them or listing Windows first.
- Include Linux shell commands and configuration file examples alongside PowerShell and Windows registry instructions.
- Reference Linux logs and diagnostic tools (e.g., journalctl, /var/log/) where Windows event logs are mentioned.
- Clarify when a step is Windows-only and provide alternative guidance for Linux users.
Automation
Troubleshoot Azure Automation shared resource issues
...n/articles/automation/troubleshoot/shared-resources.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation is heavily focused on PowerShell cmdlets and scripts, which are native to Windows environments. All troubleshooting examples and resolutions use PowerShell commands (e.g., Remove-AzAutomationModule, New-AzAutomationModule, Connect-AzAccount), with no mention of Bash, Azure CLI, or Linux/macOS alternatives. Windows-specific terminology and tools (DLL errors, .psd1/.psm1 files, PowerShell runbooks) are used exclusively, and no Linux/macOS-specific troubleshooting steps or examples are provided.
Recommendations
- Add equivalent Azure CLI commands and examples for each PowerShell cmdlet mentioned, especially for module management and authentication.
- Include troubleshooting steps for Linux/macOS users, such as how to handle module imports and runbook errors in non-Windows environments.
- Mention cross-platform tools and patterns (e.g., Bash scripts, Python runbooks) where applicable.
- Provide guidance on using Azure Automation with Linux Hybrid Workers, if relevant.
- Reorder examples to present cross-platform solutions first, or at least in parallel with Windows/PowerShell solutions.
Automation
Troubleshoot Azure Automation runbook issues
...blob/main/articles/automation/troubleshoot/runbooks.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation is heavily focused on PowerShell and Windows-centric tools and workflows. All code examples use PowerShell cmdlets, with no mention of Bash, Azure CLI, or Linux/macOS-specific troubleshooting steps. Windows/PowerShell tools (e.g., PowerShell ISE, Windows-specific modules) are referenced exclusively, and there is no parity for users who prefer or require Linux/macOS environments. Even when Python is mentioned, no examples or troubleshooting steps are provided for it.
Recommendations
- Add Azure CLI (az) and Bash examples alongside PowerShell for common tasks such as starting runbooks, authenticating, and managing modules.
- Include troubleshooting steps and examples for Python runbooks, especially since Python is supported and mentioned.
- Reference cross-platform editors (e.g., VS Code) and avoid recommending Windows-only tools like PowerShell ISE.
- Explicitly state which solutions are platform-agnostic and which are Windows-specific, and provide alternatives for Linux/macOS where needed.
- Add notes or sections addressing common Linux/macOS issues (e.g., module installation, authentication differences, hybrid worker setup on Linux).
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a notable bias towards Windows and PowerShell. Most examples and feature announcements focus on PowerShell runbooks, with Windows terminology and tools mentioned more frequently and often before Linux equivalents. While Linux is occasionally referenced (e.g., Hybrid Runbook Worker support), there is a lack of parity in examples, guidance, and tool coverage for Linux and macOS users. Python is mentioned as an alternative, but PowerShell (a Windows-centric technology) dominates the documentation, and there are few explicit Linux/macOS usage scenarios or examples.
Recommendations
- Provide equal examples and guidance for Linux/macOS users, including bash and shell scripting runbooks.
- When announcing new features (e.g., Azure CLI support), clarify cross-platform compatibility and provide Linux/macOS usage instructions.
- Include Linux/macOS-specific troubleshooting, migration, and setup steps where relevant.
- Ensure that references to tools (e.g., VS Code extension, CLI) mention cross-platform support and usage.
- Add explicit Linux/macOS runbook samples alongside PowerShell examples.
Azure App Configuration
Tutorial for using Azure App Configuration Key Vault references in a Java Spring Boot app | Microsoft Docs
...-configuration/use-key-vault-references-spring-boot.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. Environment variable setup is presented first using Windows-specific commands (setx, PowerShell), with Linux/macOS instructions shown last and less clearly. The use of setx and PowerShell is emphasized, while the Linux/macOS export command is not explained in detail. There is also an implicit assumption that users are familiar with Windows command-line tools, and the restart requirement is only mentioned for Windows. No Linux/macOS-specific troubleshooting or alternative patterns are provided.
Recommendations
- Present Linux/macOS and Windows environment variable setup instructions side-by-side or in parallel tabs, rather than listing Windows first.
- Explain the export command for Linux/macOS users and clarify any differences (e.g., persistence of environment variables).
- Add troubleshooting notes for Linux/macOS users, such as how to verify environment variables and restart requirements.
- Avoid using Windows-specific commands (setx, PowerShell) without equivalent Linux/macOS context.
- Include explicit examples for Linux/macOS users where Windows tools or patterns are mentioned.
Azure Change Tracking Inventory
Azure Change Tracking Extension Version Details and Known Issues
...change-tracking-inventory/extension-version-details.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation generally lists Windows notes before Linux in tables and issue descriptions, and provides more detail for Windows-specific features (e.g., registry, environment variables, Knowledge Base IDs). Some workarounds and recommendations (such as upgrading the AMA or using KQL functions) are described only for Windows, with Linux issues often noted as 'None' or without equivalent guidance. There are references to Windows-specific tools and concepts (registry, services) without Linux equivalents or parity in explanation.
Recommendations
- Ensure Linux notes/examples are presented with equal detail and priority as Windows, including workarounds and upgrade recommendations.
- Provide Linux equivalents for Windows-specific features (e.g., describe how Linux daemons are handled, or how to work with Linux file paths/environment variables).
- When listing OS-specific notes, alternate the order or present both OSes together to avoid implicit prioritization.
- Include troubleshooting steps and workaround details for Linux issues where possible, not just for Windows.
- Expand documentation on Linux-specific extension features and known issues, matching the depth given to Windows.
Azure App Configuration
Quickstart for Azure App Configuration with Aspire
.../articles/azure-app-configuration/quickstart-aspire.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation repeatedly references Docker Desktop as the container runtime, which is primarily a Windows/macOS tool, and does not mention Linux-native alternatives (e.g., Docker Engine, Podman). In steps involving container runtime setup, Docker Desktop is named as the example, suggesting a Windows/macOS-first approach. There are no explicit PowerShell or Windows command-line examples, but the choice of tooling and ordering implies a bias toward Windows/macOS environments.
Recommendations
- Mention Linux-native container runtimes (e.g., Docker Engine, Podman) alongside Docker Desktop when discussing prerequisites and setup steps.
- Provide explicit instructions or notes for Linux users on how to start their container runtime (e.g., 'systemctl start docker' or 'podman start').
- Ensure screenshots and UI references are not exclusively from Docker Desktop; include examples from Linux environments where possible.
- When listing prerequisites, avoid listing Docker Desktop first or exclusively; use neutral language such as 'an OCI-compliant container runtime (e.g., Docker Desktop, Docker Engine, Podman)'.
Azure Change Tracking Inventory
Azure Change Tracking and Inventory Support Matrix
...-inventory/change-tracking-inventory-support-matrix.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 concepts (registry, services, file paths) are listed before Linux equivalents in tables and examples. Windows tools and terminology (e.g., registry, Windows services, c:\ paths) are referenced more frequently and with greater detail. Powershell is used as the interactive shell for all CLI examples, even when Linux commands are shown. Linux-specific instructions and examples are present but often appear after Windows ones, and some configuration options (like data collection frequency) are only available for Windows resources.
Recommendations
- Present Linux and Windows examples side-by-side, or alternate which platform is shown first in tables and examples.
- Use a neutral shell prompt for CLI examples (e.g., bash or generic 'az' CLI), especially for Linux instructions.
- Expand Linux-specific guidance, such as configuration options, troubleshooting, and limitations.
- Include Linux file path examples in alerting/query scenarios (e.g., /etc/hosts) alongside Windows paths.
- Clarify which features are Windows-only and provide Linux alternatives or workarounds where possible.
- Balance the depth of explanation for both platforms, ensuring Linux users have parity in actionable information.
Azure Change Tracking Inventory
Azure Change Tracking and Inventory Overview by Using Azure Monitor Agent
...change-tracking-inventory/overview-monitoring-agent.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates Windows bias primarily in the 'Track registry keys' section, which exclusively discusses Windows registry monitoring, listing only Windows registry keys and their purposes. There are no equivalent Linux configuration file or daemon monitoring examples. Throughout the page, Windows terminology (e.g., registry, Windows services) is mentioned before Linux equivalents (e.g., daemons), and no Linux-specific examples or tables are provided for configuration tracking. The page lacks parity in describing how Linux-specific changes (such as monitoring /etc files, systemd units, or package managers) are tracked, leaving Linux/macOS users with less actionable information.
Recommendations
- Add a parallel section for Linux configuration tracking, detailing which files (e.g., /etc/passwd, /etc/ssh/sshd_config), directories, or daemon/service changes are monitored.
- Provide Linux-specific examples and tables similar to the Windows registry key table, such as monitoring systemd unit files, cron jobs, or package manager changes.
- Clarify how Change Tracking and Inventory works on Linux/macOS, including supported features and limitations.
- Ensure examples and terminology alternate or balance between Windows and Linux, rather than listing Windows first.
- Include screenshots or walkthroughs for Linux systems where appropriate.
Azure Change Tracking Inventory
Quickstart: Enable Azure Change Tracking and Inventory for Single and Multiple Machines from the Portal
...nges-collect-inventory-azure-change-tracking-inventory.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation demonstrates a moderate Windows bias. Windows VM creation is linked in prerequisites, and Windows concepts (Registry, Files, Software) are mentioned first in applicability. Most screenshots and portal instructions are generic, but examples and terminology often prioritize Windows. Linux-specific instructions are present but less emphasized, and the CLI section provides both Windows and Linux commands, though Windows is often listed first. There is no PowerShell-specific content, but the overall flow and examples tend to favor Windows users.
Recommendations
- Add explicit links to both Windows and Linux VM creation guides in prerequisites.
- Alternate the order of Windows and Linux examples and terminology throughout the document.
- Include more Linux-specific screenshots and examples where applicable.
- Ensure that Linux file, software, and configuration tracking is described with equal detail as Windows Registry and Software.
- Clarify any differences in portal experience for Linux VMs, if any exist.
Azure Functions
Guide for running C# Azure Functions in an isolated worker process
...icles/azure-functions/dotnet-isolated-process-guide.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 (Visual Studio, Azure PowerShell) are mentioned before or alongside cross-platform options, and Windows configuration steps are often described first. Some CLI examples use Azure PowerShell or reference Windows-specific settings before Linux equivalents. Linux-specific instructions and examples are present but sometimes appear after Windows ones or are less detailed. There are few explicit Linux/macOS shell examples, and some deployment/configuration sections focus on Windows workflows.
Recommendations
- Ensure Linux/macOS examples (e.g., bash, Azure CLI) are presented alongside or before Windows/PowerShell equivalents.
- Balance tool recommendations by highlighting cross-platform editors (VS Code, JetBrains Rider) and CLI workflows before Windows-only tools.
- Provide explicit Linux/macOS shell commands and configuration steps wherever Windows/PowerShell commands are shown.
- Clarify which steps are OS-agnostic and which are platform-specific, grouping instructions by platform where necessary.
- Expand troubleshooting and deployment sections with Linux/macOS-specific guidance and examples.
Azure Functions
Build a serverless workflow using Durable Functions - Azure Functions
...unctions/durable/scenario-build-serverless-workflow.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides command examples for Windows-specific shells (PowerShell, Cmd) alongside bash, and sometimes lists Windows options before Linux/macOS. In several places, Windows tools and patterns (such as PowerShell and Cmd) are explicitly called out, and Linux/macOS instructions are not always presented first or with equal prominence. Some sections (e.g., virtual environment activation for Python) offer Windows-specific instructions in more detail than Linux/macOS. There are also places where Windows command syntax is shown before or alongside bash, but Linux/macOS users may need to infer their own equivalents.
Recommendations
- Present Linux/macOS instructions before Windows ones, or side-by-side with equal prominence.
- Ensure all command examples are available for bash/zsh and not just Windows shells.
- Add explicit Linux/macOS instructions wherever Windows-specific tools (PowerShell, Cmd) are mentioned.
- Use generic, cross-platform CLI commands where possible, and clarify OS-specific differences only when necessary.
- Review all code blocks and tabs to ensure Linux/macOS users are not required to infer steps from Windows examples.
Azure Functions
Migrate apps from Azure Functions version 1.x to 4.x
...rticles/azure-functions/migrate-version-1-version-4.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 in its migration instructions, especially in the initial steps for identifying function apps to migrate. Only PowerShell scripts are provided for listing apps and setting the active subscription, with no equivalent Azure CLI or Bash examples for Linux/macOS users. The use of Azure PowerShell and references to Visual Studio (a primarily Windows tool) further reinforce this bias. Linux alternatives are not mentioned or provided, and Windows-centric tools and patterns are presented first and exclusively in critical sections.
Recommendations
- Provide Azure CLI and Bash script examples alongside PowerShell for identifying and managing function apps, ensuring Linux/macOS users have clear instructions.
- Explicitly mention cross-platform tools (e.g., VS Code, Azure CLI) in addition to Visual Studio, and clarify which steps can be performed on Linux/macOS.
- Add notes or sections that address Linux/macOS environments, including any differences in workflow or tool usage.
- Reorder examples or provide parallel instructions so that Windows and Linux/macOS users are equally supported.
Azure Functions
Azure Functions Premium plan
...ain/articles/azure-functions/functions-premium-plan.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a moderate Windows bias. Examples for configuring Premium plan features are consistently provided for Azure CLI and Azure PowerShell, but no Linux-specific shell examples (e.g., Bash) are given. PowerShell examples are included throughout, which are primarily relevant for Windows users. In the migration section, it is explicitly stated that migration between Consumption and Premium plans is only supported on Windows, with no Linux alternative or workaround. In some tables and feature lists, Windows options are listed before Linux, and the region scale-out table shows higher limits for Windows in most regions, with some regions not supporting Linux at all.
Recommendations
- Add explicit Bash examples for all CLI commands to demonstrate Linux parity.
- Clarify that Azure CLI commands work cross-platform and provide notes for Linux/macOS users where relevant.
- Where PowerShell is mentioned, provide equivalent Bash or shell script examples.
- In migration section, offer guidance or alternatives for Linux users, or clarify future support plans.
- In tables and lists, alternate or randomize order of Windows and Linux, or present both equally.
- Highlight any feature gaps for Linux and provide links to tracking issues or roadmap.
Azure Netapp Files
Migrate volumes to Azure NetApp Files
...ob/main/articles/azure-netapp-files/migrate-volumes.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. The only explicit code sample for automating migration uses PowerShell, with no equivalent Bash or Linux shell script provided. The feature registration steps are shown first with Azure PowerShell, and only secondarily mention Azure CLI as an alternative. There are no Linux/macOS-specific instructions or examples for scripting or automation, and the tip for workflow automation links only to a PowerShell script. The rest of the migration process is platform-neutral (REST API, portal, ONTAP CLI), but the initial onboarding and scripting guidance favor Windows users.
Recommendations
- Provide equivalent Bash or Azure CLI sample scripts for migration assistant workflow automation.
- Show Azure CLI commands before or alongside PowerShell commands in feature registration steps.
- Add explicit guidance for Linux/macOS users on how to perform migration steps, including scripting and automation.
- Include links to Linux/macOS sample scripts in the 'TIP' section, not just PowerShell.
- Ensure all automation and scripting examples are available for both Windows and Linux platforms.
Azure Resource Manager
Add module settings in the Bicep config file
...s/azure-resource-manager/bicep/bicep-config-modules.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page demonstrates a moderate Windows bias. Credential precedence and authentication examples prioritize Azure CLI and Azure PowerShell, both of which are Windows-centric tools (especially PowerShell). The credential precedence list and explanatory text mention Azure PowerShell before other cross-platform options. There are no explicit Linux/macOS examples or references to Linux-native authentication workflows, and no mention of platform-specific considerations for Linux/macOS users.
Recommendations
- Include explicit examples or notes for Linux/macOS users, such as using Azure CLI (which is cross-platform) and Environment credentials.
- Reorder credential precedence examples to show cross-platform options (AzureCLI, Environment, ManagedIdentity) before Windows-specific ones (AzurePowerShell, VisualStudio).
- Add a section or note clarifying that Azure CLI and Bicep are cross-platform, and provide links or instructions for installation and usage on Linux/macOS.
- Mention any platform-specific differences or caveats, such as authentication flows or environment variable setup for EnvironmentCredential on Linux/macOS.
Azure Resource Manager
Use Bicep to create a new resource group
.../azure-resource-manager/bicep/create-resource-group.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Bicep files, but PowerShell (a Windows-centric tool) is always presented immediately after Azure CLI, and with equal prominence. There are no Linux/macOS-specific shell examples (e.g., Bash), nor is there any mention of platform differences or requirements for PowerShell on non-Windows systems. The documentation assumes familiarity with PowerShell, which may create friction for Linux/macOS users.
Recommendations
- Explicitly state that Azure CLI commands work cross-platform (Windows, Linux, macOS) and are recommended for non-Windows users.
- Add Bash shell examples for Linux/macOS users, especially for multi-line commands.
- Clarify that PowerShell Core is available on Linux/macOS, but Azure CLI is typically more native.
- Consider listing Azure CLI examples before PowerShell, or grouping platform-specific instructions.
- Add a note about prerequisites for each platform (e.g., installing Azure CLI on Linux/macOS).
Azure Resource Manager
Configure development environment for deployment scripts in Bicep | Microsoft Docs
...manager/bicep/deployment-script-bicep-configure-dev.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 scripting and resource deployment examples, including uploading files to Azure Storage and deploying Bicep files, with no equivalent Bash or cross-platform CLI examples provided. Docker volume mounting instructions use Windows-style paths and drive letters (e.g., d:/docker), which are not applicable to Linux/macOS. The order of presentation often favors PowerShell/Windows approaches first, and Linux/macOS users must infer or adapt steps themselves.
Recommendations
- Provide Bash/Azure CLI equivalents for all PowerShell deployment and upload commands, especially for uploading files to Azure Storage and deploying Bicep files.
- Include Docker volume mounting examples using Linux/macOS paths (e.g., /home/user/docker:/data) alongside Windows examples.
- Clarify cross-platform compatibility for all steps, explicitly noting differences or requirements for Linux/macOS users.
- Where PowerShell is used, mention how to run these scripts on Linux/macOS (e.g., via pwsh), or provide alternative Bash scripts.
- Reorder examples or provide parallel instructions so that Linux/macOS users are not required to adapt Windows-centric steps.
Azure Resource Manager
Data types in Bicep
...in/articles/azure-resource-manager/bicep/data-types.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page is mostly platform-neutral, but it contains a notable Windows bias in the 'Integers' section, where PowerShell is mentioned as the example deployment tool and its integer range limitation is discussed. No equivalent mention is made of Linux/macOS tools (such as Azure CLI or Bash), nor are their behaviors or limitations described. Additionally, links to Bicep CLI installation reference Visual Studio Code and its Bicep extension, which is often associated with Windows, and do not mention cross-platform installation or usage.
Recommendations
- Include information about deploying Bicep files using Azure CLI on Linux/macOS, and specify any integer range limitations or differences for those platforms.
- When discussing command-line tools, mention both PowerShell (Windows) and Azure CLI (cross-platform) equally, or provide examples for both.
- Add installation and usage instructions for Bicep CLI on Linux/macOS, and clarify that Visual Studio Code and the Bicep extension are available cross-platform.
- Review all tool references to ensure parity and avoid implying Windows is the default or only supported platform.
Azure Resource Manager
Bicep What-If: Preview Changes Before Deployment
...rticles/azure-resource-manager/bicep/deploy-what-if.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides extensive examples for Azure CLI and Azure PowerShell, but PowerShell examples are shown alongside CLI in nearly every section and sometimes first. There are no explicit Linux/macOS shell examples (e.g., bash, zsh), and PowerShell is a Windows-centric tool (despite cross-platform support, most Linux users prefer bash). Visual Studio Code is mentioned, but not in a way that addresses OS-specific usage. The cleanup section refers to 'Azure CLI or Azure PowerShell', but the CLI tab is labeled 'CLI' rather than 'Azure CLI', which could cause confusion. No Linux-specific patterns, troubleshooting, or environment setup are discussed.
Recommendations
- Add explicit bash/zsh examples for Linux/macOS users, especially for scripting and output parsing.
- Clarify that Azure CLI commands work on Linux/macOS and provide shell-specific notes (e.g., quoting, environment variables).
- Include troubleshooting notes for common Linux/macOS issues (e.g., file permissions, path separators).
- Mention cross-platform editors (e.g., VS Code on Linux/macOS) and provide links to relevant setup guides.
- Reorder examples so Azure CLI (which is cross-platform) appears before PowerShell, or alternate the order.
- Label tabs and code blocks clearly as 'Azure CLI (Windows/macOS/Linux)' and 'PowerShell (Windows/macOS/Linux)' to reduce ambiguity.
Azure Resource Manager
Use deployment scripts in Bicep
...zure-resource-manager/bicep/deployment-script-bicep.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides both Azure CLI (Linux-friendly) and Azure PowerShell (Windows-centric) examples for deployment scripts in Bicep, but consistently presents PowerShell examples immediately after CLI, and in some cases, only PowerShell deployment commands are shown for deploying Bicep files. Script management sections give equal coverage to Azure CLI and PowerShell, but deployment instructions are PowerShell-only. There is no explicit Linux shell (bash) or macOS Terminal example for deploying Bicep files, nor are there instructions for using non-Windows tools (e.g., Bash, zsh, or cross-platform alternatives) to deploy scripts. The documentation assumes familiarity with PowerShell and Windows patterns, which may create friction for Linux/macOS users.
Recommendations
- Add explicit Bash (Linux/macOS) examples for deploying Bicep files, using 'az deployment group create' or similar Azure CLI commands.
- Present CLI (cross-platform) examples before PowerShell examples to reduce Windows-first bias.
- Clarify that Azure CLI commands work on Linux/macOS and provide terminal instructions for those platforms.
- Where PowerShell scripts are shown for deployment, provide equivalent Bash/CLI commands.
- Mention cross-platform development environments and tools (e.g., VS Code, Docker, native shells) for script development and deployment.
Azure Resource Manager
Create Bicep files - Visual Studio
...ger/bicep/quickstart-create-bicep-use-visual-studio.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation is focused on Visual Studio, which is primarily a Windows application, and does not provide Linux/macOS alternatives for authoring Bicep files. While deployment instructions include both Azure CLI and PowerShell, the authoring workflow is Windows-centric, and Linux users are only briefly referenced via a link to Visual Studio Code documentation.
Recommendations
- Explicitly state that Visual Studio is Windows-only and recommend Visual Studio Code for Linux/macOS users.
- Add a short section summarizing how Linux/macOS users can author Bicep files (e.g., using VS Code or other editors).
- Ensure that all critical steps (authoring, deployment, cleanup) have clear Linux/macOS-compatible instructions or links.
- Consider reordering or visually separating Windows-only instructions from cross-platform steps.
Azure Resource Manager
Create and deploy a template spec with Bicep
...urce-manager/bicep/quickstart-create-template-specs.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation exhibits a moderate Windows bias. File path examples consistently use Windows-style paths (e.g., C:\templates\main.bicep) without showing Linux/macOS alternatives. While both Azure PowerShell and Azure CLI are covered, PowerShell examples and references appear first in most sections, and PowerShell is a Windows-centric tool. There is no explicit mention or example of Linux/macOS file paths, shell environments, or platform-specific considerations for CLI usage. The 'Grant access' section links only to a PowerShell tutorial, omitting CLI or portal alternatives. There is a note about a known issue with PowerShell, but no guidance for Linux users. Overall, Linux/macOS users can complete the tasks, but may encounter friction due to Windows-centric patterns and lack of parity in examples.
Recommendations
- Provide Linux/macOS file path examples (e.g., /home/user/templates/main.bicep) alongside Windows paths.
- Explicitly mention that Azure CLI commands work cross-platform and note any platform-specific differences.
- Include links to CLI and portal tutorials for role assignment, not just PowerShell.
- Alternate the order of PowerShell and CLI examples, or present CLI first to reflect its cross-platform nature.
- Add notes or callouts for any platform-specific issues or workarounds, especially for Linux/macOS users.
Azure Resource Manager
Publish modules to private module registry
...ce-manager/bicep/quickstart-private-module-registry.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation consistently provides both Azure CLI and Azure PowerShell examples for all commands, but PowerShell is a Windows-centric tool and is presented as a primary alternative to Azure CLI. The tooling recommendations focus on Visual Studio and Visual Studio Code, which, while cross-platform, are often associated with Windows workflows. There are no explicit Linux/macOS shell examples (e.g., Bash), and no mention of Linux-specific patterns or considerations. The use of PowerShell throughout, and the absence of Linux/macOS shell alternatives, creates friction for non-Windows users.
Recommendations
- Add Bash shell examples alongside Azure CLI commands to demonstrate usage in typical Linux/macOS environments.
- Clarify that Azure CLI commands work natively on Linux/macOS and Windows, and provide any OS-specific notes if needed.
- Mention cross-platform editors (e.g., VS Code) explicitly as available on Linux/macOS, and consider referencing alternatives like Vim or JetBrains IDEs.
- If PowerShell is shown, note that PowerShell Core is available on Linux/macOS, or provide Bash equivalents.
- Ensure screenshots and instructions do not assume Windows-only workflows.
Azure Resource Manager
Use deployment scripts in Azure Resource Manager templates
...source-manager/templates/deployment-script-template.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page exhibits a moderate Windows/PowerShell bias. PowerShell examples are consistently presented first and in greater detail, with inline and external script samples almost exclusively using PowerShell (.ps1) syntax. The main walkthrough for running scripts in Cloud Shell uses Azure PowerShell, and the troubleshooting and output handling sections focus on PowerShell variables and patterns. While Azure CLI/bash is supported and referenced, CLI examples are less prominent, and Linux/macOS users may need to infer or adapt from PowerShell-centric instructions.
Recommendations
- Provide parallel Azure CLI/bash examples for every PowerShell example, including inline and external script samples.
- Alternate the order of examples so that Azure CLI/bash is sometimes shown first.
- Expand the walkthroughs and troubleshooting sections to include CLI/bash-specific instructions and output handling.
- Clarify that both PowerShell and CLI scripts run in Linux containers, and highlight cross-platform development environments.
- Add explicit notes or sections for Linux/macOS users, including tips for adapting PowerShell-centric instructions.
Azure Resource Manager
Develop ARM templates for cloud consistency
...source-manager/templates/template-cloud-consistency.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, especially in its scripting and tooling examples. PowerShell commands are frequently presented, often before or alongside Azure CLI equivalents, but Linux/macOS shell alternatives are not shown. Several examples reference Windows-specific paths, scripts, and VM images, with little mention of Linux equivalents. The use of Windows-centric tools (PowerShell, Visual Studio) is emphasized, and examples for Linux VM images, shell scripts, or Linux-based development environments are absent.
Recommendations
- Provide Bash or shell script equivalents for PowerShell commands, especially for tasks like verifying template functions, listing resource providers, VM images, and VM sizes.
- Include Linux VM image examples alongside Windows VM image references in ARM template samples.
- Reference Linux/macOS-compatible development tools (such as VS Code, JetBrains IDEs) in the testing and automation section, not just Visual Studio.
- Show examples of using Linux shell scripts with Custom Script Extensions, not only PowerShell scripts.
- Ensure that documentation sections presenting commands or scripts alternate or balance Windows and Linux/macOS examples, or present them side-by-side.
- Explicitly mention cross-platform support for Azure CLI and provide guidance for Linux/macOS users where workflows differ.
Azure Resource Manager
Create portal forms for template spec
...anager/templates/template-specs-create-portal-forms.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
powershell_heavy
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell (a Windows-centric tool) is mentioned first in both prerequisites and example commands for creating and updating template specs. The documentation references Windows-specific cmdlets (Get-AzSubscription, Get-AzADUser, Get-AzADServicePrincipal) in parameter descriptions, and PowerShell examples are shown before Azure CLI equivalents. However, Azure CLI examples are provided, and no steps are strictly Windows-only; Linux/macOS users can complete all tasks using Azure CLI.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples to avoid Windows-first ordering.
- Reference Azure CLI commands for obtaining tenantId and objectId (e.g., az account show, az ad user show) in parameter descriptions, not just PowerShell cmdlets.
- Explicitly state that all steps can be performed on Linux/macOS using Azure CLI.
- Add notes or links for installing and using Azure CLI on Linux/macOS.
- Where possible, use generic terminology (e.g., 'command line') instead of 'PowerShell' when not required.
Backup
Restore Azure Kubernetes Service (AKS) using Azure Backup
...les/backup/azure-kubernetes-service-cluster-restore.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page references Azure PowerShell as an alternative method for restoring AKS clusters and links to a PowerShell-specific guide, but does not mention or provide examples for Linux/macOS command-line tools (such as Azure CLI or Bash scripts). The main restore workflow is described via the Azure Portal UI, which is cross-platform, but the only programmatic example referenced is Windows-centric. There is no mention of Linux/macOS equivalents or parity in automation approaches.
Recommendations
- Add references and examples for restoring AKS clusters using Azure CLI, which is cross-platform and widely used on Linux/macOS.
- Ensure that any linked guides (such as the PowerShell guide) have equivalent Azure CLI or Bash script documentation.
- Explicitly mention that the Azure Portal workflow is OS-agnostic, and clarify any steps that may differ for Linux/macOS users.
- Where automation is discussed, provide both PowerShell and CLI examples side-by-side.
Backup
Azure Resource Manager and Bicep files
...lob/main/articles/backup/backup-rm-template-samples.md
Medium Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation page lists Azure Resource Manager and Bicep templates for Azure Backup features. While most templates are platform-agnostic, one template specifically highlights deploying a Windows Server VM with backup enabled, without mentioning Linux VM equivalents or providing parity. Additionally, the Windows example appears before any mention of Linux, which is absent.
Recommendations
- Add equivalent templates and examples for deploying and backing up Linux VMs, such as Ubuntu or CentOS, alongside the Windows Server VM example.
- Explicitly state that the templates are platform-agnostic where applicable, and clarify any platform-specific limitations.
- Ensure that examples for Linux are provided and are given equal prominence as Windows examples.
- Where a template is Windows-specific, explain why and provide guidance for Linux users.
Backup
Azure Backup - Archive tier overview
...docs/blob/main/articles/backup/archive-tier-support.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation lists PowerShell as a supported client before CLI, and references PowerShell-specific pivots in links. There are no explicit Linux/macOS examples or mentions of Linux-specific tools or patterns. The use of PowerShell as a primary automation example may create friction for Linux/macOS users, though Azure CLI is also listed as supported.
Recommendations
- Ensure that CLI examples are provided alongside PowerShell examples, especially for automation tasks.
- List CLI and PowerShell clients together, or alternate their order to avoid Windows-first perception.
- Explicitly mention Linux/macOS support and provide guidance or examples for those platforms.
- Where screenshots or walkthroughs are given, include CLI-based steps and outputs.
- Clarify that all features are equally available via CLI on Linux/macOS, and note any exceptions.
Backup
Back up Azure Kubernetes Service (AKS) using Azure CLI
...p/azure-kubernetes-service-cluster-backup-using-cli.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation is largely cross-platform, focusing on Azure CLI commands which work on Windows, Linux, and macOS. However, there is evidence of Windows bias in the private endpoint creation section, where PowerShell-style syntax (backticks for line continuation and variable assignment with $) is used, which is specific to Windows PowerShell. Additionally, the example for fetching the subnet ID and creating a private endpoint uses PowerShell conventions, potentially confusing Linux/macOS users. The mention of Azure PowerShell as an alternative is given early, but no Linux shell equivalents are provided for the PowerShell-specific examples.
Recommendations
- Provide bash/zsh equivalents for all PowerShell-specific examples, especially for private endpoint creation and variable assignment.
- Use cross-platform syntax for line continuation (e.g., \ for bash) and variable assignment (e.g., var=value for bash).
- Clearly indicate which examples are platform-specific and offer alternatives for Linux/macOS users.
- Consider showing bash examples first or side-by-side with PowerShell to avoid Windows-first impression.
Backup
Private Endpoints Overview: Version 2 Experience
...icles/backup/backup-azure-private-endpoints-concept.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. It repeatedly references Windows-specific backup tools (MARS agent, DPM, MABS) and scenarios, with little to no mention of Linux backup agents or workflows. Examples and recommendations are centered around Windows workloads (SQL Server, SAP HANA in Azure VMs, MARS agent, DPM), and there is no guidance for Linux VM backup or restore operations, nor are Linux-specific tools or commands referenced. The documentation assumes the use of Windows-centric backup solutions and does not provide parity for Linux users.
Recommendations
- Include explicit examples and guidance for Linux VM backup and restore operations using private endpoints.
- Mention Linux backup agents (such as Azure Backup for Linux VMs) and clarify their compatibility or limitations with private endpoints.
- Provide Linux command-line examples (e.g., using Azure CLI, shell scripts) alongside or before Windows/Powershell examples.
- Reference Linux-specific considerations for DNS configuration, agent installation, and network connectivity.
- Clarify whether private endpoints support Linux workloads and agents, and if not, document workarounds or alternatives.
Backup
Troubleshoot Azure Backup failures caused by agent or extension issues
...up-azure-troubleshoot-vm-backup-fails-snapshot-timeout.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 troubleshooting steps, tools, and examples (services.msc, Control Panel, Event Viewer, regsvr32.exe, .NET, Visual C++ Redistributable, AppLocker) are described in detail, often with screenshots and step-by-step instructions. Linux guidance is present but less detailed, with fewer explicit commands, no screenshots, and less coverage of common Linux troubleshooting tools. PowerShell is referenced for job cancellation, but Linux CLI alternatives are not shown. Windows-specific tools and patterns (services.msc, Event Viewer, AppLocker) are mentioned without Linux equivalents, and Windows examples often precede Linux ones.
Recommendations
- Provide Linux-specific troubleshooting steps with equivalent detail, including explicit commands for checking agent status, logs, and extension health.
- Include Linux screenshots or terminal output examples where Windows screenshots are used.
- Mention Linux alternatives for Windows tools (e.g., systemctl for services.msc, journalctl/syslog for Event Viewer, Linux security frameworks for AppLocker).
- Offer CLI examples for job management (e.g., Azure CLI commands for cancelling backup jobs) alongside PowerShell.
- Ensure Linux instructions are presented with equal prominence and detail as Windows instructions, and alternate the order in which OS-specific steps are presented.
Backup
Azure Backup release notes - Archive
.../main/articles/backup/backup-release-notes-archived.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page for Azure Backup release notes shows some evidence of Windows bias. Several features and updates specifically mention Windows-centric tools such as MARS (Microsoft Azure Recovery Services agent), Microsoft Azure Backup Server (MABS), and Windows Server compatibility. These Windows tools are referenced by name and described in detail, while Linux/macOS equivalents are not mentioned or are less prominent. In feature lists, Windows-specific solutions (MARS, MABS) are often listed before Linux-related features, and PowerShell is referenced for automation, with less emphasis on Bash/CLI or cross-platform scripting. However, the page also covers cross-platform workloads (AKS, PostgreSQL, SAP HANA on RHEL), and many features are platform-agnostic.
Recommendations
- Ensure parity by explicitly mentioning Linux/macOS support or alternatives where Windows tools (MARS, MABS) are referenced.
- Provide examples or links for Linux/macOS backup agents or procedures alongside Windows-specific instructions.
- When listing features, alternate the order or group by platform-neutral features first, then platform-specific ones.
- Reference Azure CLI and Bash scripting equally with PowerShell, especially for automation and policy management.
- Add notes or links to documentation for Linux backup scenarios (e.g., Azure Backup for Linux VMs, SAP HANA on Linux) wherever Windows backup tools are discussed.
Backup
Automation in Azure Backup support matrix
...blob/main/articles/backup/backup-support-automation.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation consistently lists PowerShell as a primary automation method for Azure Backup tasks, with 'Supported' and example links for PowerShell in nearly every operation and resource type. PowerShell is a Windows-centric tool, and its presence as the first column in all tables, as well as the frequent use of PowerShell-specific documentation links, signals a Windows-first approach. There is little to no mention of Linux/macOS-specific scripting environments (e.g., Bash, shell scripts), nor any explicit guidance for Linux users on using PowerShell Core cross-platform. The CLI is present and supported, but PowerShell is always listed first and often receives more detailed example links. No Linux-specific tools or patterns are mentioned.
Recommendations
- Reorder columns to list Azure CLI before PowerShell, or alternate the order to avoid implicit prioritization.
- Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
- Add notes or links about using PowerShell Core on Linux/macOS, if relevant, or clarify any limitations.
- Provide example scripts in Bash/shell where possible, especially for common automation scenarios.
- Include a section or callout for Linux/macOS users describing best practices and tool choices for automation.
- Audit example links to ensure CLI examples are as comprehensive and prominent as PowerShell ones.
Backup
Support matrix for Azure VM backups
...lob/main/articles/backup/backup-support-matrix-iaas.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. Windows tools and backup agents (such as MARS, DPM, and MABS) are described in detail and are supported only for Windows, with Linux support explicitly marked as 'Not supported' in several sections. Windows-specific restore and backup scenarios are often described first or in more detail, and PowerShell is referenced as the default automation tool for restore operations. Linux backup support is present but more limited, with several advanced features (such as file-level backup with agents, DPM/MABS integration, and Docker/ZFS support) unavailable. Linux examples and tools are less emphasized, and Linux users are often directed to generic or OS-agnostic solutions rather than dedicated Linux tooling.
Recommendations
- Provide parity in backup and restore features for Linux VMs, such as agent-based file-level backup and restore.
- Include Linux CLI (az CLI, Bash) examples alongside or before PowerShell examples for restore operations.
- Expand documentation of Linux-specific limitations and workarounds, and offer guidance for common Linux backup scenarios.
- Highlight Linux support and scenarios earlier in the documentation, not just in dedicated Linux sections.
- Where features are Windows-only, clearly state the roadmap or alternatives for Linux users.
Backup
Quickstart - Install Azure Backup extension in an AKS cluster
...main/articles/backup/quick-install-backup-extension.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation exclusively describes installation of the Azure Backup extension in AKS using the Azure portal UI, with screenshots and step-by-step instructions. There are no examples or instructions for command-line installation via Azure CLI, which is the typical approach for Linux/macOS users. The 'Next steps' section mentions CLI, PowerShell, ARM, Bicep, and Terraform, but the main quickstart only covers the portal workflow, which is most commonly used on Windows. This creates friction for Linux/macOS users who may prefer or require CLI-based automation.
Recommendations
- Add parallel instructions for installing the Backup extension using Azure CLI, including example commands.
- Explicitly mention that the portal workflow is cross-platform, but highlight CLI alternatives for Linux/macOS users.
- Include links or inline examples for PowerShell and CLI in the main quickstart, not just in 'Next steps'.
- Clarify any platform-specific requirements or limitations for each installation method.
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
powershell_heavy
Summary
The documentation for Azure Backup shows a notable Windows bias. Windows backup scenarios (MARS agent, DPM, MABS) are described first and in greater detail, with Linux support often mentioned as 'not supported' or as a secondary note. Windows-specific tools (MARS agent, DPM, MABS) are referenced throughout, while Linux backup options are limited and less prominently featured. There are no Linux-specific examples or guidance for on-premises backup, and agent-based backup is only available for Windows. App-consistent backup for Linux requires custom scripting, which is referenced but not explained in detail here.
Recommendations
- Add Linux-first or Linux-parity examples for backup scenarios, especially for on-premises machines.
- Provide explicit guidance and examples for configuring app-consistent backups on Linux, including links to relevant scripts and best practices.
- Clearly indicate alternatives for Linux users where Windows-only tools (MARS agent, DPM, MABS) are mentioned.
- Reorganize tables and sections to present Windows and Linux support side-by-side, rather than Windows-first.
- Include Linux-specific limitations and workarounds more prominently, not just as footnotes.
- Reference cross-platform backup tools or third-party solutions where Microsoft tooling is Windows-only.
Backup
Create and use private endpoints for Azure Backup
...re-docs/blob/main/articles/backup/private-endpoints.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. Most automation and scripting examples are provided using PowerShell, with explicit references to uploading and running .ps1 scripts in the Azure Cloud Shell (which defaults to PowerShell). File paths use Windows conventions (e.g., C:\<filepath>), and there are no Bash, CLI, or Linux/macOS shell equivalents for key tasks such as role creation, DNS entry management, or private endpoint approval. The documentation also references Windows-centric tools (MARS agent, DPM server) and patterns before mentioning alternatives. Linux/macOS users are left to infer how to adapt these steps, creating friction and potential confusion.
Recommendations
- Provide Azure CLI and Bash examples alongside PowerShell for all automation and scripting tasks, especially for role/permission creation, DNS entry management, and private endpoint approval.
- Use cross-platform file path conventions or clarify when Windows paths are used; provide Linux/macOS equivalents.
- Explicitly mention that Cloud Shell supports Bash and provide instructions/scripts for both Bash and PowerShell.
- Reference Linux-compatible backup agents and tools where relevant, or clarify platform requirements.
- Ensure that all critical steps (such as creating resources, managing permissions, and DNS configuration) have Linux/macOS-friendly instructions and examples.
Backup
Quickstart - Configure backup for Azure Database for PostgreSQL - Flexible Servers with a Bicep file
...ackup/quick-backup-postgresql-flexible-server-bicep.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 PowerShell deployment instructions for the Bicep template and referencing Azure PowerShell for subsequent operations. There are no CLI (az) or Bash examples, and the instructions for pasting code reference Windows shell conventions. This creates friction for Linux/macOS users who typically use Bash and Azure CLI.
Recommendations
- Add Azure CLI (az deployment group create) examples for deploying the Bicep template.
- Include Bash shell instructions for copying and running commands.
- Reference both PowerShell and CLI documentation in 'Next steps' and throughout the page.
- Explicitly mention cross-platform compatibility and provide links to Linux/macOS setup guides.
Backup
Quickstart - Resource Manager template VM Backup
.../blob/main/articles/backup/quick-backup-vm-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. The main deployment example uses Azure PowerShell exclusively, with no equivalent Azure CLI or Bash example provided. The template itself is described as deploying a Windows VM, and PowerShell commands are used for both deployment and cleanup. Linux/macOS users are only briefly mentioned as being able to use Azure CLI or REST API, but no concrete examples or guidance are given for those platforms.
Recommendations
- Add step-by-step Azure CLI and Bash examples for template deployment and resource cleanup, shown alongside PowerShell examples.
- Explicitly mention cross-platform compatibility and provide guidance for Linux/macOS users.
- Include a note or section on how to deploy Linux VMs with the template, or link to Linux-specific templates.
- Reorder examples so that CLI/Bash instructions are presented before or alongside PowerShell, not after.
- Ensure all referenced scripts and commands have Linux/macOS equivalents.
Backup
Quickstart - Configure vaulted backup for an Azure Kubernetes Service (AKS) cluster using Azure Backup via Azure Resource Manager
...ob/main/articles/backup/quick-kubernetes-backup-arm.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 deployment instructions for the ARM template, with no equivalent Azure CLI or Bash example for Linux/macOS users. Prerequisites and next steps also emphasize PowerShell first, and do not offer Linux-native alternatives for the main deployment workflow.
Recommendations
- Add Azure CLI and Bash examples for deploying the ARM template, shown alongside or before PowerShell.
- Explicitly mention that Azure CLI is cross-platform and provide installation instructions for Linux/macOS.
- Ensure that all critical workflows (deployment, restore, management) have Linux/macOS-friendly instructions and examples.
- Reorder next steps to present CLI and PowerShell equally, or alternate which is listed first.
Backup
Soft delete for SQL server in Azure VM and SAP HANA in Azure VM workloads
...articles/backup/soft-delete-sql-saphana-in-azure-vm.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides detailed instructions for the Azure portal and Azure PowerShell, with all CLI examples using PowerShell cmdlets. There are no examples or guidance for Linux/macOS users, such as using Azure CLI, Bash, or REST API. The PowerShell instructions are presented as the only scripting option, and the portal instructions do not mention OS-specific considerations, but PowerShell is Windows-centric.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell commands, enabling Linux/macOS users to perform soft delete operations from the command line.
- Include REST API references or examples for advanced users who may not use PowerShell.
- Explicitly state OS compatibility for each method (portal, PowerShell, CLI) and recommend alternatives for non-Windows environments.
- Reorder or parallelize examples so that PowerShell and CLI/REST are presented together, not with PowerShell first.
- Add a note clarifying that PowerShell can be installed on Linux/macOS, but Azure CLI is the preferred cross-platform solution.
Batch
Migrate Batch account certificates to Azure Key Vault
...in/articles/batch/batch-certificate-migration-guide.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation mentions both Windows and Linux support for the Azure Key Vault VM extension, but provides links to separate documentation for each without giving direct examples or guidance for either platform. Windows is mentioned first in the FAQ section, and there are no concrete Linux command examples or step-by-step instructions for Linux users. Some Linux-specific details are discussed (e.g., certificateStoreLocation, file permissions), but practical examples are missing.
Recommendations
- Provide explicit Linux and Windows example workflows for migrating certificates, including sample commands and configuration snippets.
- Ensure Linux examples are presented alongside or before Windows examples, especially in sections discussing certificate access and installation.
- Include troubleshooting tips specific to Linux environments (e.g., SELinux, file permissions, common errors).
- Add a table or side-by-side comparison of steps for both platforms to highlight parity.
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates Windows bias by providing only Windows-centric examples (C# SDK with a Windows VM image), referencing Windows-specific VM images and node agent SKUs, and omitting Linux/macOS equivalents. No Linux VM image update example or cross-platform SDK usage is shown, and the example code uses Windows-specific identifiers and patterns.
Recommendations
- Add example code for updating a pool with a Linux VM image (e.g., Ubuntu or CentOS) and corresponding node agent SKU.
- Include cross-platform SDK usage examples (e.g., Python, CLI, or REST calls that are OS-agnostic).
- Present examples for both Windows and Linux in parallel, or alternate which OS is shown first.
- Explicitly mention Linux/macOS compatibility and provide guidance for those platforms where relevant.
Batch
Storage and data movement for rendering
...rticles/batch/batch-rendering-storage-data-movement.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation provides more detailed and explicit examples for Windows, including command-line usage and mounting instructions, while Linux equivalents are either less detailed or missing. Windows tools and patterns (cmdkey, net use, mapped drives) are described in depth, with Linux mounting and usage covered only briefly. The azcopy example uses Windows-style syntax, and Linux-specific mounting (e.g., with Azure Files) is not shown. This creates friction for Linux/macOS users who may need to infer or seek out additional steps.
Recommendations
- Add explicit Linux/macOS examples for mounting Azure Files shares (e.g., using mount.cifs or SMB mounting commands).
- Provide azcopy usage examples with Linux/macOS syntax and flags.
- Include parity in step-by-step instructions for both Windows and Linux/macOS, especially for mounting and accessing file shares.
- Reference Linux tools and patterns (e.g., shell commands, fstab configuration) alongside Windows tools.
- Ensure all major workflows (copying, mounting, accessing files) have both Windows and Linux/macOS examples.
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page exhibits moderate Windows bias. Windows-specific tools (PowerShell) and patterns are mentioned before or more prominently than their Linux equivalents. Examples for disk preparation and management are more detailed for Windows (with PowerShell commands), while Linux guidance is less explicit and lacks equivalent shell script examples. Some sections, such as directory junctions and service management, focus on Windows-specific issues or features, with Linux alternatives mentioned second or not at all.
Recommendations
- Provide Linux shell script examples (e.g., using fdisk, mkfs, mount) for disk preparation, similar to the PowerShell example for Windows.
- Ensure that Linux tools and patterns (e.g., systemd for service management, symlinks vs. hard-links) are described with equal detail and prominence as Windows equivalents.
- Present both Windows and Linux instructions/examples side-by-side, rather than listing Windows first.
- Include references to Linux-specific troubleshooting and management tools where appropriate.
- Review sections for implicit Windows-first language and rephrase to treat platforms equally.
Cost Management Billing
Link a partner ID to your Power Platform and Dynamics Customer Insights accounts with your Azure credentials
...-billing/manage/link-partner-id-power-apps-accounts.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is referenced frequently and in detail, with explicit cmdlet examples and guidance. The Azure portal (a GUI tool most commonly used on Windows) is presented as the primary method for PAL association, with CLI and PowerShell alternatives mentioned later. The PowerShell examples are more extensive than Azure CLI, and some product-specific instructions (e.g., changing owners) reference PowerShell cmdlets without equivalent Linux/macOS-friendly alternatives. There is no mention of Bash or shell scripting, and the overall flow assumes familiarity with Windows-centric tools.
Recommendations
- Provide Linux/macOS-specific instructions or notes, especially for Azure CLI usage and authentication.
- Ensure Azure CLI examples are as detailed as PowerShell examples, and consider showing CLI before PowerShell to reduce Windows-first bias.
- Mention cross-platform compatibility explicitly for all tools, including PowerShell Core and Azure CLI.
- Add troubleshooting or setup guidance for Linux/macOS environments (e.g., installing PowerShell Core, using Azure CLI on non-Windows OS).
- Where PowerShell is referenced for product-specific actions, provide equivalent Azure CLI or REST API instructions if available.
Cost Management Billing
Link a partner ID to your account thatâs used to manage customers
...cles/cost-management-billing/manage/link-partner-id.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation exhibits a Windows bias by presenting all command-line examples with Windows-style prompts (C:\>), referencing PowerShell first and in detail, and using Windows-specific terminology (e.g., 'Install the PowerShell module', 'C:\ az ...'). There are no explicit Linux/macOS shell examples, and installation instructions do not mention platform differences. The Azure CLI section also uses Windows prompts and omits Linux/macOS usage notes.
Recommendations
- Provide Linux/macOS shell examples alongside Windows/PowerShell examples, using appropriate prompts (e.g., $ for bash/zsh).
- Clarify that both PowerShell and Azure CLI are cross-platform, and include installation instructions for Linux/macOS.
- Remove Windows-specific prompt (C:\>) from CLI examples, or show both Windows and Linux/macOS variants.
- Mention platform-specific considerations for module/extension installation (e.g., use pip or apt for CLI on Linux).
- Ensure screenshots and instructions are not Windows-centric, or provide alternatives for other platforms.
Cost Management Billing
Transfer Azure product billing ownership to a Microsoft Customer Agreement
...gement-billing/manage/mca-request-billing-ownership.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation exclusively describes the transfer process using the Azure portal web interface, with screenshots and instructions tailored to a GUI experience. There are no command-line examples, nor any mention of cross-platform tools (such as Azure CLI or REST API), which are commonly used by Linux/macOS users. The instructions implicitly assume a Windows-centric workflow by focusing solely on the portal and not referencing CLI or automation options.
Recommendations
- Add equivalent instructions for performing billing ownership transfers using the Azure CLI, which is cross-platform and widely used on Linux/macOS.
- Include REST API references or examples for advanced/automated scenarios.
- Explicitly mention that the portal is accessible from any OS/browser, but provide parity for users who prefer or require command-line or automated workflows.
- Where screenshots are used, clarify that the portal experience is OS-agnostic and not limited to Windows.
Cost Management Billing
Copy billing roles from one MCA to another MCA across tenants with a script
...s/cost-management-billing/manage/mca-role-migration.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation is heavily biased towards Windows and PowerShell. All scripting examples are provided only in PowerShell, and instructions explicitly direct users to select PowerShell in Azure Cloud Shell, with no mention of Bash or cross-platform alternatives. There are no Linux/macOS-specific instructions or script examples, and the workflow assumes familiarity with Windows/PowerShell tooling.
Recommendations
- Provide equivalent Bash or Azure CLI script examples for Linux/macOS users.
- Clarify whether the PowerShell script can be run in Azure Cloud Shell Bash or on Linux/macOS with PowerShell Core.
- Add instructions for uploading and running scripts using Bash in Cloud Shell.
- List both PowerShell and Bash/CLI options in prerequisites and workflow steps.
- Explicitly state platform compatibility for the script and tools used.
Cost Management Billing
Programmatically create Azure subscriptions for a Microsoft Partner Agreement with the latest APIs
...ically-create-subscription-microsoft-partner-agreement.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides examples for REST, Azure CLI, and Azure PowerShell for all major steps. However, PowerShell is referenced in every section, and instructions for installing PowerShell modules are included, which are primarily relevant to Windows users. In several sections, PowerShell is listed before Azure CLI, and REST, which can subtly prioritize Windows workflows. There are no explicit Linux/macOS shell examples (e.g., Bash), nor are there notes about cross-platform compatibility for PowerShell. Some PowerShell installation instructions (e.g., PowerShellGet) are Windows-centric and may not work as-is on Linux/macOS. No Linux-specific tools or patterns are mentioned.
Recommendations
- Add explicit notes about PowerShell cross-platform support, including installation steps for Linux/macOS.
- Include Bash or shell script examples where applicable, especially for REST API calls (e.g., using curl).
- List Azure CLI examples before PowerShell, as CLI is natively cross-platform.
- Clarify that Azure CLI and REST API methods work identically on Linux, macOS, and Windows.
- Remove or supplement Windows-centric PowerShell module installation instructions with Linux/macOS equivalents.
- Consider adding troubleshooting notes for Linux/macOS users regarding PowerShell module installation.
Cost Management Billing
Permissions to view and manage Azure savings plans
...agement-billing/savings-plan/permission-view-manage.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page provides only Azure PowerShell examples for managing savings plan permissions and roles, with no mention of cross-platform alternatives such as Azure CLI, Bash, or REST API usage from Linux/macOS environments. The reliance on PowerShell (traditionally a Windows tool) and lack of Linux/macOS-specific instructions or parity examples creates friction for non-Windows users.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell scripts, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Explicitly state that PowerShell Core is available for Linux/macOS, and provide installation instructions or links.
- Include REST API example calls using curl or similar tools to demonstrate platform-agnostic management.
- Clarify which tools and commands are supported on Linux/macOS and provide troubleshooting guidance for non-Windows environments.
Data Factory
Copy data from/to a file system
...ob/main/articles/data-factory/connector-file-system.md
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-style paths (backslashes, UNC paths) are shown first and exclusively in examples. References to enabling local machine access under Self-hosted Integration Runtime point to PowerShell commands, with no Linux equivalent or guidance. The use of Windows terminology (e.g., 'FileServer', '\\myserver\share') is prevalent, while Linux alternatives are only briefly mentioned (Samba) and lack concrete examples. There are no Linux-specific sample configurations, and the documentation does not clarify how to author paths for Linux shares or provide Linux command-line instructions.
Recommendations
- Provide Linux-specific examples for file paths (e.g., /mnt/share, /srv/samba/share) alongside Windows UNC paths.
- Include instructions and sample commands for configuring Self-hosted Integration Runtime access on Linux, such as using shell scripts or systemd, not just PowerShell.
- Expand the Samba mention with a step-by-step guide or link to Azure-relevant Samba setup documentation.
- Clarify how to format 'host' and 'folderPath' properties for Linux shares in both JSON and UI authoring.
- Add troubleshooting tips for common Linux/Samba issues (permissions, SELinux, etc.).
- Ensure all command-line references (e.g., enabling local access) have Linux equivalents.
Databox Online
Deploy VMs on your Azure Stack Edge Pro device via templates
...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-online/azure-stack-edge-gpu-deploy-virtual-machine-templates.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation is heavily oriented toward Windows environments, with all command-line examples using PowerShell, references to Windows paths (e.g., C:\WINDOWS\system32), and instructions for editing the Windows hosts file and using Windows-specific tools like Notepad. There is no mention of Linux/macOS equivalents for these steps, and no bash/CLI examples are provided. Even when Linux VMs are referenced, the workflow and tooling assume a Windows client. This creates friction for Linux/macOS users attempting to follow the guide.
Recommendations
- Provide bash/Azure CLI examples for all PowerShell commands, especially for resource group, storage account, and VM creation.
- Include instructions for editing the hosts file on Linux/macOS (e.g., /etc/hosts) and mention appropriate editors (nano, vim, etc.).
- Clarify how to install and use Azure Storage Explorer and AzCopy on Linux/macOS, including certificate handling.
- Show sample outputs from Linux/macOS terminals where relevant.
- Explicitly state cross-platform requirements and provide parity in steps for Linux/macOS users.
Devtest Labs
Create custom artifacts for VMs
...n/articles/devtest-labs/devtest-lab-artifact-author.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 code examples for artifact creation use PowerShell scripts and Windows-specific commands (e.g., powershell.exe, Chocolatey). There are no Linux shell script examples, nor is there guidance for creating Linux-compatible artifacts. The process for Linux artifact creation is only mentioned in passing (targetOsType: Linux), with no practical examples or instructions. Windows tools and patterns (PowerShell, Chocolatey) are referenced exclusively and appear before any mention of Linux equivalents.
Recommendations
- Add parallel examples for Linux artifacts, including sample artifactfile.json and corresponding shell script (e.g., Bash) usage.
- Show how to use Linux package managers (e.g., apt, yum) in artifact scripts.
- Provide a Linux-focused runCommand example, such as executing a Bash script.
- Explicitly mention and demonstrate how to structure artifacts for Linux VMs, including handling secure strings and parameters.
- Ensure that Linux instructions and examples are presented alongside Windows examples, not only as an afterthought.
Cost Management Billing
Software costs not included in Azure savings plans
...nt-billing/savings-plan/software-costs-not-included.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page focuses heavily on Windows VM software costs, listing only Windows Server-related meters and omitting any mention of Linux VM software costs or licensing. There are no examples or discussion of Linux or open-source VM scenarios, which may lead Linux users to question whether similar costs or considerations apply to them.
Recommendations
- Add a section clarifying software cost implications for Linux VMs (e.g., noting that Linux VMs typically do not incur additional OS licensing costs).
- Explicitly state that the listed meters apply only to Windows workloads and that Linux workloads are not subject to these charges.
- If there are any software meters relevant to Linux or other OSes, include them for completeness.
- Consider a comparison table showing differences in software cost treatment between Windows and Linux VMs under savings plans.
Cost Management Billing
Troubleshoot Azure subscription sign-in issues
...roubleshoot-subscription/troubleshoot-sign-in-issue.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides browser troubleshooting steps for Edge, Chrome, and Safari, but consistently lists Edge (a Windows-centric browser) first and omits explicit instructions for Firefox, which is popular on Linux. There are no references to Linux-specific browsers or command-line tools, and no mention of Linux/macOS-specific troubleshooting steps for clearing cache or cookies. The examples and instructions are tailored to Windows and macOS environments, with Linux parity lacking.
Recommendations
- Include explicit instructions for Firefox, a common browser on Linux.
- Add steps for clearing cache/cookies in Linux environments (e.g., using Firefox or Chromium on Linux).
- Avoid always listing Edge first; rotate or group browsers by platform.
- Mention any command-line options for troubleshooting (e.g., clearing browser data via CLI on Linux).
- Clarify that instructions apply to all platforms, and note any platform-specific differences.
Devtest Labs
Create environments from ARM templates
...evtest-labs/devtest-lab-create-environment-from-arm.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a notable Windows bias in its automation section, providing a detailed PowerShell script and usage instructions for automating environment creation, while only briefly mentioning Azure CLI as an alternative without any example or walkthrough. The PowerShell example is extensive and presented first, with no equivalent Bash or Linux shell script provided. This creates friction for Linux/macOS users who may prefer or require CLI or Bash-based automation.
Recommendations
- Add a full Azure CLI example (with Bash syntax) for automating environment creation, including parameter handling and deployment steps.
- Present both PowerShell and Azure CLI examples side-by-side, or clearly indicate parity between platforms.
- Explicitly mention platform compatibility for each automation method, clarifying that PowerShell is available cross-platform but CLI is native to Linux/macOS.
- Consider providing a table or section comparing PowerShell and CLI approaches for common tasks in DevTest Labs.
Data Factory
BCDR for Azure Data Factory and Azure Synapse Analytics Pipelines
...n/articles/data-factory/pipelines-disaster-recovery.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. It references Azure PowerShell for automation (e.g., disabling triggers, approving private endpoints) and links to PowerShell-based scripts without mentioning or providing equivalent Bash/CLI examples for Linux/macOS users. Automation steps and tooling are described primarily in terms of Windows-centric technologies, with no explicit Linux alternatives or parity.
Recommendations
- Provide equivalent Azure CLI (az) and Bash script examples for all PowerShell automation tasks, such as disabling triggers and approving private endpoints.
- Explicitly mention cross-platform support and clarify which steps can be completed on Linux/macOS, including links to relevant documentation.
- Add notes or sections for Linux/macOS users, highlighting any differences or additional steps required.
- Where possible, use platform-neutral language (e.g., 'use Azure CLI or PowerShell') and order examples so that neither platform is prioritized.
Deployment Environments
Grant access to Azure Deployment Environments
...nments/how-to-manage-deployment-environments-access.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation exclusively provides instructions and screenshots for using the Azure portal GUI, which is most commonly accessed from Windows environments. There are no examples or guidance for performing role assignments using cross-platform tools such as Azure CLI, Azure PowerShell, or REST APIs, which would be relevant for Linux and macOS users. The lack of command-line or automation-friendly instructions creates friction for non-Windows users and those working in headless or automated environments.
Recommendations
- Add equivalent instructions for assigning roles using Azure CLI (az role assignment), which works on Linux, macOS, and Windows.
- Include Azure PowerShell examples, noting that PowerShell Core is cross-platform.
- Provide REST API examples for role assignment for automation and platform neutrality.
- Explicitly state that the Azure portal is web-based and can be accessed from any OS, but highlight CLI and API alternatives for users who prefer or require non-GUI workflows.
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by prioritizing Azure PowerShell and portal-based setup instructions, both of which are most familiar to Windows users. There are no explicit Linux/macOS CLI examples (such as Azure CLI or Bash), and PowerShell is mentioned before any cross-platform alternatives. This may create friction for Linux/macOS users who prefer command-line tools native to their platforms.
Recommendations
- Add explicit Azure CLI (az) examples for creating and managing DNS Private Resolvers, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Ensure that setup instructions reference both PowerShell and CLI options, and present them in parallel or with CLI first.
- Include notes or links for Linux/macOS users on how to perform equivalent tasks using their preferred tools.
- Review referenced quickstarts and tutorials to ensure Linux/macOS parity and visibility.
Firewall
Quickstart: Create an Azure Firewall with Availability Zones - Resource Manager template
...re-docs/blob/main/articles/firewall/deploy-template.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates bias towards Windows by exclusively deploying Windows Server virtual machines in the example environment, mentioning Windows VMs as the only option, and providing only PowerShell commands for resource cleanup without Linux/macOS alternatives. There are no examples or instructions for deploying Linux VMs or using cross-platform tools like Azure CLI or Bash for resource management.
Recommendations
- Include options to deploy Linux-based virtual machines alongside or instead of Windows Server VMs in the template and documentation.
- Provide equivalent cleanup instructions using Azure CLI or Bash scripts for Linux/macOS users.
- Mention cross-platform tools and patterns (e.g., Azure CLI, Bash) before or alongside Windows/PowerShell examples.
- Clarify that the template can be customized to deploy different OS types and provide guidance for doing so.
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides a PowerShell example for configuring prescaling, but does not include equivalent examples for Linux/macOS users (e.g., Azure CLI, Bash, or REST API). PowerShell is a Windows-centric tool, and its example is presented before Bicep/ARM template references. There is no mention of Azure CLI or cross-platform scripting options, which may create friction for non-Windows users.
Recommendations
- Add Azure CLI example for configuring prescaling, as CLI is cross-platform and widely used on Linux/macOS.
- Include REST API example or reference for users who prefer direct API calls.
- Present examples in a neutral order (e.g., Portal, CLI, PowerShell, Bicep) or group them by platform.
- Explicitly state that PowerShell examples can be run on Linux/macOS via PowerShell Core, or clarify platform requirements.
Firewall
Quickstart: Create an Azure Firewall and IP Groups - Resource Manager template
...ain/articles/firewall/quick-create-ipgroup-template.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation provides only a Windows PowerShell example for resource cleanup (Remove-AzResourceGroup) and does not mention or provide equivalent Azure CLI or Bash commands for Linux/macOS users. The use of PowerShell as the sole example and lack of Linux-native tooling or examples creates friction for non-Windows users.
Recommendations
- Add Azure CLI and/or Bash examples for resource group deletion (e.g., az group delete --name <your resource group name> --yes --no-wait).
- Where PowerShell is used, explicitly mention cross-platform alternatives and link to relevant documentation.
- Ensure that all critical operations (deployment, cleanup, management) have both PowerShell and CLI/Bash examples.
- Consider listing CLI/Bash examples before or alongside PowerShell to avoid implicit Windows-first bias.
Governance
Learn Azure Policy for Kubernetes
...es/governance/policy/concepts/policy-for-kubernetes.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 tools (Azure portal, Azure CLI, Azure PowerShell) are referenced throughout, with Azure portal instructions often presented first. Azure PowerShell is mentioned as an alternative to Azure CLI for resource provider registration, but no Linux-specific shell or package manager instructions (e.g., apt, yum, Homebrew) are provided for installing Azure CLI. The documentation does not provide explicit Linux/macOS installation or troubleshooting guidance, nor does it mention platform-specific differences for commands or prerequisites. However, most operational commands (kubectl, helm) are cross-platform, and the add-on itself only supports Linux node pools, which is clearly stated.
Recommendations
- Add explicit instructions for installing Azure CLI on Linux and macOS, including package manager commands (apt, yum, Homebrew).
- When listing command-line instructions, clarify platform compatibility and provide any necessary platform-specific notes (e.g., path differences, shell syntax).
- When presenting Azure portal instructions, alternate or parallelize with CLI instructions, and clarify that both are cross-platform.
- If Azure PowerShell is mentioned, also mention Bash or other Linux-native shells where appropriate.
- Include troubleshooting steps or notes for Linux/macOS users, especially for common issues like permissions, networking, or environment setup.
- Make clear that all kubectl and helm commands are cross-platform and provide any platform-specific caveats if relevant.
IoT Dps
Quickstart - Provision a simulated TPM device to Microsoft Azure IoT Hub
.../articles/iot-dps/quick-create-simulated-device-tpm.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates a notable Windows bias. Windows is referenced as the default development environment, with most examples and instructions tailored for Windows users (e.g., Visual Studio, .NET SDK on Windows, .exe simulators). Linux/macOS alternatives are mentioned only in passing or deferred to external SDK documentation. Critical steps, such as running the TPM simulator, building projects, and using Visual Studio, are described exclusively for Windows, with no explicit Linux/macOS commands or toolchain guidance. The use of Windows-specific tools (Visual Studio, Simulator.exe) and command prompts further increases friction for non-Windows users.
Recommendations
- Provide explicit Linux/macOS instructions for all major steps, including installing prerequisites, building SDKs, and running the TPM simulator.
- Include Linux/macOS command-line equivalents alongside Windows commands (e.g., use 'make', 'gcc', or 'clang' for C SDK builds, and provide .sh scripts or instructions for running the simulator).
- Reference cross-platform IDEs (e.g., VS Code) and toolchains where possible, or clarify how to use Visual Studio Code or other editors on Linux/macOS.
- Ensure that all sample code and device simulator tools are available and documented for Linux/macOS, or provide containerized solutions (e.g., Docker) for cross-platform parity.
- Reorganize prerequisite sections to present Windows, Linux, and macOS options equally, rather than defaulting to Windows.
Governance
Planning a change from Desired State Configuration extension to machine configuration
...onfiguration/whats-new/migrating-from-dsc-extension.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. It focuses almost exclusively on PowerShell DSC (Desired State Configuration), references Windows PowerShell versions, and provides examples and migration steps that assume Windows-centric tooling and workflows. There is no mention of Linux/macOS equivalents, nor are there examples or guidance for users managing Linux VMs with DSC or machine configuration. The use of PowerShell cmdlets and references to Windows-specific services (like Local Configuration Manager) further reinforce the bias.
Recommendations
- Add explicit guidance and examples for Linux VMs, including how to check for DSC extension presence and migrate configurations.
- Clarify whether machine configuration supports Linux and, if so, provide Linux-specific migration steps and tooling.
- Include references to Linux DSC resources and modules, and describe any differences in workflow or compatibility.
- Provide sample commands or scripts for Linux environments (e.g., Bash, Azure CLI) where appropriate.
- Mention any limitations or considerations for non-Windows platforms in the migration process.
Governance
Details of the initiative definition structure
...nce/policy/concepts/initiative-definition-structure.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
powershell_heavy
windows_first
Summary
The documentation page is largely platform-neutral, focusing on JSON structure and Azure concepts. However, there is a notable Windows bias in the 'strongType' section, where the only tool mentioned for resource type validation is 'Get-AzResourceProvider', a PowerShell cmdlet. No Linux/macOS equivalent (such as Azure CLI) is referenced, and PowerShell is mentioned before any cross-platform alternatives.
Recommendations
- Include Azure CLI equivalents (e.g., 'az provider show' or 'az provider list') alongside PowerShell examples for resource type validation.
- Explicitly mention that both PowerShell and Azure CLI can be used for these tasks, and provide sample commands for each.
- Where possible, link to cross-platform documentation or note platform compatibility for tools.
- Avoid listing Windows-specific tools first; present cross-platform options equally.
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides examples for Azure CLI, REST API, Azure PowerShell, Visual Studio Code extension, and GitHub Actions. However, Azure PowerShell examples are given equal or greater prominence than Azure CLI, and PowerShell-specific features (like jobs) are described in detail. There is no mention of Linux/macOS-specific shell usage (e.g., Bash), nor are there examples for Bash, zsh, or other common Linux/macOS environments. The documentation assumes familiarity with PowerShell and Windows-centric tooling, and does not clarify cross-platform compatibility for PowerShell commands or provide Linux/macOS-specific guidance.
Recommendations
- Add explicit Bash/zsh examples for command-line operations, especially for REST API calls using curl or similar tools.
- Clarify that Azure CLI is cross-platform and provide usage notes for Linux/macOS users.
- Add a section or note about running Azure PowerShell on Linux/macOS, including installation and usage differences.
- Balance the order of examples, presenting Azure CLI before PowerShell, or interleave them to avoid Windows-first perception.
- Mention and demonstrate use of native Linux/macOS tools (e.g., curl, jq) for REST API interactions.
- Include troubleshooting notes for common Linux/macOS issues (e.g., authentication, environment setup).
IoT Dps
How to programmatically create an Azure Device Provisioning Service enrollment group for X.509 certificate attestation
...blob/main/articles/iot-dps/quick-enroll-device-x509.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_heavy_language
missing_linux_example
windows_tools
Summary
The documentation demonstrates a notable Windows bias. Windows is referenced first and most frequently in prerequisites, sample instructions, and tooling. Many steps explicitly mention using a Windows command prompt, and some certificate generation instructions link only to Windows-specific tabs or tools. While the article claims Linux is supported and some commands are cross-platform, there are missing or unclear instructions for Linux/macOS users, especially for Java and C# samples. Windows tools (like Git Bash) are recommended without Linux alternatives, and screenshots are Windows-centric.
Recommendations
- Explicitly provide Linux/macOS instructions and examples alongside Windows, especially for command-line steps and sample execution.
- Avoid language like 'Windows-based machine' in prerequisites; instead, specify cross-platform requirements.
- For certificate generation, link to both Windows and Linux tabs or provide equivalent Linux/macOS commands (e.g., OpenSSL usage).
- Include screenshots from Linux/macOS environments or clarify that UI is identical.
- When recommending tools like Git Bash, also mention Linux/macOS equivalents (e.g., native bash, zsh).
- For Java and C# samples, clarify how to run commands on Linux/macOS (e.g., using Terminal, Mono, or .NET Core on Linux).
- Add notes or pivots for Linux/macOS users where file paths, shell commands, or environment variables differ.
IoT Hub
Get Started with ADR and Certificate Management in IoT Hub (Preview)
...main/articles/iot-hub/iot-hub-device-registry-setup.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation page displays a Windows bias by explicitly highlighting PowerShell as a deployment method, labeling it as 'Windows only', and mentioning it alongside Azure CLI as a primary option. The PowerShell script method is presented in the deployment table before any mention of Linux/macOS shell scripting alternatives, and there is no explicit mention of Bash or Linux/macOS shell script equivalents. While the Azure CLI is cross-platform, the PowerShell method's prominence and lack of Linux script parity suggest a moderate Windows bias.
Recommendations
- Add explicit Bash or shell script examples for Linux/macOS users alongside PowerShell scripts.
- Clarify that Azure CLI is cross-platform and provide instructions for installation and usage on Linux/macOS.
- If scripts are provided, ensure both PowerShell and Bash versions are available and referenced equally.
- Avoid labeling deployment methods as 'Windows only' without offering Linux/macOS alternatives.
- Consider reordering examples so that cross-platform methods (Azure CLI, Bash) are presented before Windows-specific ones.
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page exhibits a moderate Windows bias in the .NET/C# section, where Windows/PowerShell/ETW instructions and tools are presented first and in greater detail, with explicit mention of PowerShell scripts and Event Tracing for Windows (ETW). The Linux equivalent (dotnet-trace) is described after Windows, but is covered adequately. Other SDKs (C, Java, JavaScript, Python, Embedded C) provide platform-neutral or cross-platform instructions, with no notable Windows bias.
Recommendations
- Present Linux and Windows instructions side-by-side or in parallel sections, rather than Windows-first.
- Include explicit mention of macOS support (if applicable) for .NET tracing tools.
- Provide parity in detail and troubleshooting tips for Linux/macOS users, matching the depth given to Windows/PowerShell/ETW.
- Consider referencing cross-platform tracing tools where possible, or clarify platform limitations.
- Add a summary table comparing trace collection methods across platforms for .NET.
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation presents configuration instructions via three pivots: Azure portal, Azure CLI, and Azure PowerShell. The inclusion of Azure PowerShell as a primary method introduces a Windows bias, as PowerShell is traditionally associated with Windows environments. The order of pivots (portal, CLI, PowerShell) also places PowerShell before any explicit mention of Linux/macOS alternatives, and there is no mention of Bash or Linux-specific tooling.
Recommendations
- Clarify that Azure CLI is fully supported on Linux/macOS and provide explicit Bash examples where relevant.
- Add a note indicating that PowerShell Core is cross-platform, or provide Bash equivalents for all PowerShell commands.
- Reorder pivots or add a Linux/macOS-specific section to highlight parity and reduce perceived Windows-first bias.
- Explicitly mention platform compatibility for each method (portal, CLI, PowerShell) at the start of the documentation.
IoT Hub
Monitor IoT messages with distributed tracing (preview)
...b/main/articles/iot-hub/iot-hub-distributed-tracing.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a notable Windows bias, especially in the 'Run a sample application' section. Instructions for building and running the sample application are detailed for Windows (Visual Studio, .exe files, Windows SDK), while Linux/macOS equivalents are only referenced via external links. Windows tools and patterns (Visual Studio, command prompt, .exe) are mentioned exclusively or before alternatives, and Linux build/run steps are missing from the main flow.
Recommendations
- Add explicit Linux/macOS build and run instructions inline, including common tools (e.g., gcc/clang, make, cmake) and sample terminal commands.
- Provide example output for Linux/macOS environments, not just Windows (e.g., .out files, Linux shell prompts).
- Mention and show how to use cross-platform editors (e.g., VS Code, vim) and terminals.
- Ensure parity in troubleshooting steps (e.g., compiler errors on Linux/macOS).
- List Linux/macOS prerequisites (e.g., apt-get install cmake, build-essential) alongside Windows prerequisites.
IoT Hub
Tutorial - Set up and use metrics and logs with an Azure IoT hub
...ain/articles/iot-hub/tutorial-use-metrics-and-diags.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation demonstrates a mild Windows bias. While Azure CLI is used for resource setup (which is cross-platform), the only device simulation example is a .NET/C# console app, with instructions and commands (dotnet restore/run) that are most familiar to Windows users. There are no Linux/macOS-specific instructions, troubleshooting tips, or alternative device simulation examples (e.g., Python). Screenshots and portal navigation are Windows-centric, and there is no mention of Linux-specific issues or parity. PowerShell is referenced as an alternative to CLI, but no Bash or Linux shell examples are provided.
Recommendations
- Add explicit instructions for running the simulated device app on Linux/macOS, including any required dependencies or troubleshooting tips.
- Provide a cross-platform device simulation example (e.g., Python sample) alongside the .NET/C# example.
- Include Linux/macOS-specific notes for Azure CLI usage, such as shell syntax differences or environment setup.
- Add screenshots or descriptions that reflect Linux/macOS environments where relevant.
- Mention Bash or Linux shell alternatives to PowerShell for resource setup.
Load Balancer
Quickstart: Create an internal load balancer - Azure portal
...r/quickstart-load-balancer-standard-internal-portal.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
powershell_heavy
windows_tools
Summary
The documentation page demonstrates a notable Windows bias. All VM creation steps use Windows Server images, and the only example for installing a web server (IIS) is via Windows PowerShell. There are no instructions or examples for deploying Linux VMs, nor for installing a web server (such as Apache or Nginx) on Linux. The testing steps also assume a Windows environment (using Microsoft Edge). This creates friction for users who prefer or require Linux-based solutions.
Recommendations
- Add parallel instructions for creating Linux VMs (e.g., Ubuntu) in the portal.
- Provide Linux-specific steps for installing a web server (e.g., Apache or Nginx) using Bash commands.
- Include testing instructions using Linux tools (e.g., curl, Firefox) on the test VM.
- Present both Windows and Linux examples side-by-side or allow users to select their preferred OS path.
- Avoid assuming Windows-only environments in screenshots and step descriptions.
Migrate
Enhancing Web App Assessment With Code Scan Reports for Azure Migration
...lob/main/articles/migrate/add-copilot-code-insights.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias primarily in the AppCAT CLI instructions and linked references. Java assessment instructions explicitly reference Windows tabs and do not provide Linux/macOS equivalents or examples. .NET tool installation is shown using the dotnet CLI, which is cross-platform, but all referenced quickstarts and guides for Java projects are linked with '?tabs=windows', suggesting Windows-centric instructions. There are no explicit Linux/macOS commands, troubleshooting steps, or screenshots.
Recommendations
- Provide explicit Linux/macOS instructions and examples for AppCAT CLI usage, including installation and report generation for both .NET and Java projects.
- Ensure referenced quickstart and guide links include Linux/macOS tabs or sections, not just Windows.
- Add troubleshooting guidance for Linux/macOS users (e.g., file permissions, CLI path issues).
- Include screenshots or terminal examples from Linux/macOS environments alongside Windows ones.
IoT Hub
Tutorial - Create and upload certificates for testing
...blob/main/articles/iot-hub/tutorial-x509-test-certs.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation exhibits a moderate Windows bias. Windows-specific instructions and tools (Git Bash, winpty, references to Windows installation paths) are presented first or exclusively in key sections, and the use of PowerShell is mentioned in the context of provided scripts. Linux instructions are present and generally equivalent, but Windows-centric patterns (such as recommending Git Bash for OpenSSL on Windows, and using winpty) are emphasized, and Linux/macOS users may need to adapt steps or ignore Windows-specific advice.
Recommendations
- Present Linux/macOS instructions first or in parallel with Windows instructions, rather than defaulting to Windows-first.
- Clarify that Git Bash is a workaround for Windows users, and provide explicit instructions for native Linux/macOS terminals.
- When mentioning provided scripts, ensure parity by referencing both Bash and PowerShell equally, and clarify their applicability to each platform.
- Avoid recommending Windows-specific tools (like winpty or Git Bash) in general prerequisites; instead, provide platform-specific guidance in dedicated sections.
- Add troubleshooting notes for common Linux/macOS issues (e.g., OpenSSL config file locations, permissions).
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation page exhibits a Windows bias by providing extensive PowerShell examples first, using Windows-centric tools and patterns, and referencing Windows Server images in VM creation. While Azure CLI examples (cross-platform) are present, PowerShell is given priority and more detail, and the VM creation example in PowerShell uses a Windows image exclusively.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples to emphasize cross-platform support.
- Add PowerShell Core examples or clarify that PowerShell commands can be run on Linux/macOS with PowerShell Core.
- In VM creation examples, show both Windows and Linux images in PowerShell and CLI sections.
- Explicitly mention platform compatibility for all command-line tools.
- Balance the depth and detail of examples between PowerShell and CLI sections.
Load Balancer
Azure Load Balancer health probes
...s/load-balancer/load-balancer-custom-probe-overview.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page references PowerShell as the primary method for creating a public load balancer, with no equivalent Linux/macOS CLI or Bash example in the 'Next steps' section. The mention of Azure PowerShell, Azure CLI, Templates, or API is grouped together, but only PowerShell is directly linked for a quickstart. This creates a subtle Windows bias by prioritizing Windows tooling and omitting Linux/macOS-specific guidance or examples.
Recommendations
- Add equivalent Azure CLI (az) quickstart links and examples for Linux/macOS users alongside PowerShell references.
- Provide Bash or shell script examples for probe configuration and management.
- Ensure that all instructions and code samples are available for both PowerShell and Azure CLI, and present them in parallel or alternate order.
- Explicitly state cross-platform compatibility and provide guidance for users on Linux/macOS.
Migrate
Migrate VMware virtual machines to Azure with server-side encryption(SSE) and customer-managed keys(CMK) using the Migration and modernization tool
...es/migrate/how-to-migrate-vmware-vms-with-cmk-disks.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page exclusively uses Azure PowerShell for all command-line examples and instructions, with no mention of Azure CLI, Bash, or cross-platform alternatives. All sample commands, references, and linked tutorials are PowerShell-based, which is primarily associated with Windows environments. There are no Linux/macOS-specific instructions or examples, and the workflow assumes familiarity with PowerShell, potentially creating friction for users on non-Windows platforms.
Recommendations
- Add equivalent Azure CLI (az) examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Explicitly mention that Azure PowerShell can be installed and used on Linux/macOS, and provide installation instructions or links.
- Reorder or parallelize examples so that CLI and PowerShell instructions are presented together, or allow users to select their preferred shell.
- Include notes or sections for Linux/macOS users, highlighting any platform-specific considerations or differences.
- Link to cross-platform documentation where possible, rather than Windows-specific guides.
Migrate
VMware server discovery support in Azure Migrate and Modernize
...main/articles/migrate/migrate-support-matrix-vmware.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
powershell_heavy
Summary
The documentation demonstrates a notable Windows bias. Windows-specific tools (PowerShell, WMI) and patterns are mentioned more frequently and in greater detail than Linux equivalents. Windows requirements and examples (such as PowerShell, WMI, WinRM, Windows authentication, and SQL Server discovery) are presented first or exclusively, while Linux support is often limited or omitted (e.g., SQL Server and ASP.NET web app discovery are not supported on Linux). Linux instructions are less detailed, and Linux-specific tools or patterns (such as Bash, SSH, sudo) are mentioned only briefly or as secondary options.
Recommendations
- Provide Linux-first or Linux-parity examples and instructions alongside Windows examples, especially for appliance deployment and credential configuration.
- Include detailed Linux-specific setup steps for features currently described only for Windows (e.g., SQL Server discovery, web app discovery).
- Expand on Linux tools and patterns (e.g., Bash scripts, systemd, SSH key management) where PowerShell and Windows tools are described.
- Clearly indicate feature gaps for Linux and provide workarounds or alternatives where possible.
- Ensure that Linux requirements and supported distributions are listed as prominently and in as much detail as Windows versions.
- Add troubleshooting and FAQ sections for common Linux migration issues.
Migrate
Quickstart to create an Azure Migrate project using Portal
...lob/main/articles/migrate/quickstart-create-project.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a notable Windows bias in the section describing command-line operations for Azure Migrate. It instructs users to install the Azure CLI and then explicitly directs them to use PowerShell as Administrator to execute commands, without mentioning Linux or macOS terminals. No Linux/macOS-specific instructions or examples are provided, and the workflow assumes a Windows environment. This may create friction for users on non-Windows platforms.
Recommendations
- Include instructions for running Azure CLI commands on Linux and macOS terminals (e.g., bash, zsh).
- Clarify that Azure CLI can be used on any supported OS, and provide OS-agnostic command examples.
- Avoid specifying 'PowerShell as Administrator' unless necessary, and offer equivalent steps for Linux/macOS (e.g., using sudo if required).
- Add a note or section highlighting cross-platform compatibility and any OS-specific considerations.
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-specific instructions (such as WMI Control configuration and user group assignments) are presented in greater detail and often before Linux equivalents. Windows tools and workflows (WMI, WinRM, SQL Server with Windows authentication) are described step-by-step, while Linux instructions are more concise and sometimes lack equivalent depth (e.g., no GUI walkthroughs or troubleshooting for Linux). SQL Server examples are Windows-centric, with no parity for Linux-based SQL deployments. Hyper-V coverage is inherently Windows-only, and the page often lists Windows before Linux in tables and sections.
Recommendations
- Provide equally detailed, step-by-step instructions for Linux server configuration, including troubleshooting and verification steps.
- Include Linux-first examples in tables and sections to balance presentation order.
- Offer parity for Linux-based SQL Server deployments, including authentication and permission setup.
- Add more Linux-specific troubleshooting, screenshots, and tool references (e.g., SELinux, systemd, journalctl) where applicable.
- Clarify when instructions are Windows-only and offer Linux alternatives or links.
- For Hyper-V, explicitly state its Windows-only nature and suggest Linux virtualization equivalents if relevant.
Migrate
Set up an Azure Migrate appliance for server assessment in a VMware environment
...ain/articles/migrate/how-to-set-up-appliance-vmware.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation page exhibits a moderate Windows bias. The PowerShell installer script is mentioned as the only alternative to the OVA template, with no Linux shell or bash equivalent provided. The VDDK installation instructions specify a Windows file path (C:\Program Files\VMware\VMware Virtual Disk Development Kit) and do not mention Linux installation steps or paths. Credential examples and validation focus on Windows domain and non-domain accounts, with Linux credentials mentioned only in passing and no Linux-specific guidance or troubleshooting. Most configuration and troubleshooting steps assume Windows environments, and screenshots show Windows-centric interfaces.
Recommendations
- Provide Linux shell/bash installer script examples and instructions alongside PowerShell.
- Include Linux-specific steps for installing and configuring the VDDK, including default Linux paths and permissions.
- Offer parity in credential setup and validation for Linux servers, with troubleshooting tips for common Linux authentication issues.
- Add screenshots and configuration manager examples from Linux environments.
- Explicitly state OS requirements and supported platforms for the appliance, and clarify any limitations for Linux users.
Migrate
Troubleshoot issues with agentless and agent-based dependency analysis
...lob/main/articles/migrate/troubleshoot-dependencies.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, WinRM, Registry Editor, WMI, Control Panel) are frequently mentioned, often with detailed step-by-step instructions and troubleshooting guidance. PowerShell and Windows error remediation steps are more thorough and appear before Linux equivalents. Linux troubleshooting is present but less detailed, and some sections (e.g., registry edits, WMI, UAC, PowerShell language mode) are Windows-only, with no Linux alternatives or parity guidance. Linux examples are sometimes present but are less emphasized and often follow Windows instructions.
Recommendations
- Ensure Linux troubleshooting steps are as detailed as Windows, including step-by-step instructions for common errors.
- Provide Linux-first or parallel examples for all commands and remediation steps, especially in sections where Windows tools (PowerShell, Registry Editor, WMI) are used.
- Where Windows-specific tools are referenced, add equivalent Linux tools or commands (e.g., for registry edits, suggest Linux config file changes if relevant).
- Balance the order of examples so that Linux and Windows are presented together or alternately, not always Windows first.
- Expand Linux error codes and remediation guidance, including more context for SSH, permissions, and agent installation issues.
- Add troubleshooting screenshots or walkthroughs for Linux environments, similar to those provided for Windows.
Migrate
Troubleshoot the Azure Migrate appliance
...s/blob/main/articles/migrate/troubleshoot-appliance.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. Troubleshooting steps and examples often reference Windows tools (Control Panel, admin command prompt, Notepad, PowerShell, WMI, WinRM, registry edits) and provide Windows-specific instructions first or exclusively. Linux guidance is present in some sections, but is less detailed and sometimes appears after Windows instructions. Some remediation steps for appliance/server issues are Windows-only or assume familiarity with Windows environments, creating friction for Linux/macOS users.
Recommendations
- Ensure Linux troubleshooting steps are provided with equal detail and prominence as Windows steps.
- Where Windows tools (e.g., Control Panel, Notepad, PowerShell) are referenced, offer Linux/macOS equivalents (e.g., timedatectl, nano/vim, Bash scripts).
- Present Linux and Windows examples side-by-side or in parallel tabs, rather than Windows-first.
- Expand Linux-specific remediation guidance, especially for time sync, hosts file edits, and service management.
- Clarify which steps are OS-agnostic and which require OS-specific commands, and provide alternatives for macOS where relevant.
Migrate
Discover servers running in a VMware environment with Azure Migrate Discovery and assessment
...blob/main/articles/migrate/tutorial-discover-vmware.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. Critical setup steps (such as deploying the Azure Migrate appliance without OVA) are described only for Windows (PowerShell script on Windows Server 2019/2022), with no Linux alternative. Windows tools (PowerShell, Windows authentication, IIS) are mentioned first or exclusively in several places. Linux support is referenced, but Linux-specific setup instructions, troubleshooting, and parity for appliance deployment are missing.
Recommendations
- Provide explicit instructions for deploying the Azure Migrate appliance on Linux hosts, including supported distributions and setup scripts.
- Offer Linux shell (bash/ssh) examples alongside PowerShell for appliance setup and management.
- Clarify whether the PowerShell script method is Windows-only, and if so, provide a Linux equivalent or state Linux limitations.
- Include troubleshooting and configuration steps for Linux environments (e.g., SELinux, firewalls, systemd services).
- Ensure Linux tools and patterns (such as systemd, SSH, Linux authentication) are described with equal prominence as Windows tools.
- Add parity for application discovery examples (e.g., Apache/Tomcat for Linux, not just IIS/ASP.NET for Windows).
Nat Gateway
Troubleshoot Azure NAT Gateway
...ocs/blob/main/articles/nat-gateway/troubleshoot-nat.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, particularly in troubleshooting and example sections. Windows tools (PsPing, PowerShell Invoke-WebRequest) are highlighted with direct links, while Linux equivalents are mentioned more generically and without links. Some troubleshooting steps (e.g., resolving failed network interfaces) provide detailed PowerShell instructions but lack equivalent Linux CLI or Azure CLI examples, making it harder for Linux/macOS users to follow along.
Recommendations
- Provide Azure CLI or REST API examples alongside PowerShell for resource management and troubleshooting tasks, especially for resolving failed states.
- Include direct links to Linux tool documentation (e.g., nc, curl) similar to those provided for Windows tools.
- Ensure troubleshooting steps are platform-neutral or explicitly offer both Windows and Linux/macOS procedures.
- Present Linux and Windows examples side-by-side, rather than listing Windows tools first.
- Clarify that Azure Resource Explorer and portal-based steps are OS-agnostic, and avoid browser recommendations that imply Windows preference (e.g., 'recommended to use Microsoft Edge browser').
Network Watcher
Managed Identity for Virtual Network Flow Logs
...les/network-watcher/vnet-flow-logs-managed-identity.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation exclusively uses Azure PowerShell cmdlets for all examples and setup instructions, with no mention of Azure CLI, Bash, or Linux-native workflows. Prerequisites and links consistently reference PowerShell, and there are no Linux/macOS-specific instructions or examples. This creates friction for users on non-Windows platforms who may prefer or require Bash/Azure CLI.
Recommendations
- Provide equivalent Azure CLI examples for all PowerShell cmdlets shown.
- Update prerequisite links to include both PowerShell and Azure CLI/Bash instructions.
- Clarify that Azure Cloud Shell supports both Bash and PowerShell, and show how to select Bash.
- Add notes or sections for Linux/macOS users, including installation and usage guidance for Azure CLI.
- Ensure that all critical workflows can be completed using Azure CLI/Bash, not just PowerShell.
Reliability
Migrate an Azure Service Fabric cluster to availability zone support
...ob/main/articles/reliability/migrate-service-fabric.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates a notable Windows bias, particularly in the migration steps for clusters using Basic SKU load balancer and IP resources. All command-line examples are provided exclusively in PowerShell, with no equivalent Bash, Azure CLI, or Linux-native instructions. Windows-centric tools and patterns (e.g., PowerShell cmdlets, Windows file paths) are used throughout, and the only explicit OS reference in sample templates is a Windows template, with the Ubuntu template merely linked but not shown or explained. This creates friction for Linux/macOS users who may not have access to PowerShell or be familiar with its usage.
Recommendations
- Provide equivalent Azure CLI or Bash examples for all PowerShell commands, especially for resource deployment, node disabling, and removal steps.
- Explicitly mention Linux/macOS compatibility and provide guidance for users on those platforms.
- Show sample templates and migration steps for Ubuntu/Linux clusters inline, not just as external links.
- Avoid Windows-specific file paths (e.g., D:\\SvcFab) or provide Linux equivalents where relevant.
- Clarify which steps/tools are OS-agnostic and which require adaptation for Linux/macOS.
Resource Mover
Common questions about Azure Resource Mover
.../blob/main/articles/resource-mover/common-questions.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page references PowerShell as the only CLI example for managing managed identities and permissions with Azure Resource Mover, without mentioning or providing parity for Linux/macOS users (e.g., Azure CLI or Bash). Instructions for manual operations are PowerShell-centric, and there is no guidance for equivalent steps using cross-platform tools. This creates friction for non-Windows users.
Recommendations
- Provide Azure CLI (az) examples alongside PowerShell cmdlets for all manual operations, especially for assigning managed identities and roles.
- Explicitly mention that PowerShell is available cross-platform, but clarify when Windows-specific features are required.
- Add Bash scripting examples or reference how Linux/macOS users can perform equivalent tasks.
- Reorder examples so that cross-platform tools (Azure CLI) are presented before or alongside PowerShell.
- Include a note on tool compatibility for different operating systems.
Resource Mover
Modify destination settings when moving Azure VMs between regions with Azure Resource Mover
...main/articles/resource-mover/modify-target-settings.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides detailed instructions and examples for modifying destination settings using PowerShell, which is primarily a Windows-centric tool. There are no equivalent examples or guidance for Linux/macOS users, such as using Azure CLI, Bash, or REST API. The only automation example is PowerShell, and it is presented as the sole method for scripting these changes.
Recommendations
- Add equivalent examples using Azure CLI commands for modifying destination settings.
- Include Bash script snippets for Linux/macOS users.
- Reference REST API methods for advanced users who may not use PowerShell.
- Explicitly state cross-platform options and link to relevant documentation for non-Windows environments.
- Ensure that automation and scripting sections do not assume PowerShell as the default or only option.
Resource Mover
Remove resources from a move collection in Azure Resource Mover
.../main/articles/resource-mover/remove-move-resources.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
windows_first
Summary
The documentation provides detailed PowerShell-based instructions for removing resources from Azure Resource Mover, with no mention of Linux/macOS command-line alternatives (such as Azure CLI or Bash). All automation examples use PowerShell cmdlets, which are native to Windows and less commonly used on Linux/macOS. There is no guidance for users who prefer or require cross-platform tools, and PowerShell is presented as the default/only scripting option.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell cmdlets shown, 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 links.
- Reorder or parallelize examples so that Azure CLI and PowerShell instructions are presented side-by-side or with equal prominence.
- Include notes or links for Bash scripting or other automation options where appropriate.
- Clarify any platform-specific limitations or differences in the tools.
Resource Mover
Move encrypted Azure VMs across regions by using Azure Resource Mover
...ver/tutorial-move-region-encrypted-virtual-machines.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_first
Summary
The documentation demonstrates a notable Windows bias in the section on copying keys between key vaults, where only a PowerShell script is provided with no equivalent Bash, Azure CLI, or Linux-native instructions. The script requires PowerShell and specific modules, which are most easily available on Windows. Additionally, references to disk encryption link first to Windows VM guides, and Windows update instructions are given before Linux guidance. No Linux/macOS alternatives for the key copy step are described.
Recommendations
- Provide equivalent instructions and scripts for Linux/macOS users, such as Bash or Azure CLI commands to copy keys between key vaults.
- Explicitly mention how Linux/macOS users can install and use PowerShell Core, or offer a cross-platform script.
- Ensure that documentation links and examples for disk encryption are balanced between Windows and Linux, or presented together.
- Where possible, use Azure CLI examples, which are cross-platform, instead of PowerShell-only scripts.
Sap
Set up Pacemaker on RHEL in Azure | Microsoft Docs
...ap/workloads/high-availability-guide-rhel-pacemaker.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation is generally focused on RHEL and Linux, but there is a notable Windows bias in the section about configuring Azure shared disks, where only PowerShell examples are provided for disk creation and attachment, with no Azure CLI or portal instructions shown inline. Additionally, references to Azure resource management often default to PowerShell, a Windows-centric tool, before mentioning CLI alternatives. The use of Windows-specific terminology and tools (PowerShell, resource group management via PowerShell) appears before Linux-native equivalents, which may create friction for Linux/macOS users.
Recommendations
- Provide Azure CLI examples alongside PowerShell for all resource creation and management tasks, especially for disk creation and attachment.
- Explicitly mention and link to Azure Portal instructions where relevant, not just as a reference.
- Where PowerShell is used, add equivalent bash/CLI commands inline, not just as a note.
- Ensure that Linux-native tooling (Azure CLI, bash scripts) is presented first or at least equally with PowerShell.
- Audit other sections for subtle Windows-first language or tool choices and adjust for parity.
Sap
Set up Pacemaker on SUSE Linux Enterprise Server (SLES) in Azure | Microsoft Docs
...ap/workloads/high-availability-guide-suse-pacemaker.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
powershell_heavy
windows_first
Summary
The documentation is focused on SUSE Linux Enterprise Server (SLES) and Pacemaker on Azure, with all technical steps and examples using Linux commands and tools. However, there is a notable Windows bias in the section on creating and attaching Azure shared disks, where only PowerShell examples are provided for disk creation and attachment, despite Azure CLI and Portal being mentioned as alternatives. Additionally, references to Windows maintenance documentation appear before Linux equivalents in some places, and the services metadata includes 'virtual-machines-windows' even though the guide is Linux-specific.
Recommendations
- Provide Azure CLI examples for creating and attaching Azure shared disks alongside PowerShell, as CLI is cross-platform and preferred by many Linux users.
- Reorder references to maintenance documentation so Linux links appear before Windows links in Linux-focused articles.
- Remove or clarify Windows-specific service tags and metadata in Linux-only documentation to avoid confusion.
- Explicitly link to Azure CLI and Portal instructions for disk operations, not just mention them.
- Ensure all automation and scripting examples are available in Bash/CLI as well as PowerShell where relevant.
Security
Azure Operational Security | Microsoft Docs
...articles/security/fundamentals/operational-security.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation demonstrates a moderate Windows bias, with frequent references to Windows-specific tools, terminology, and examples. Windows servers, Windows event logs, and Windows-centric monitoring are mentioned before or more prominently than Linux equivalents. While Linux is acknowledged as a supported platform, concrete examples, instructions, or tool references for Linux are often missing or less detailed. Windows-centric management tools (e.g., System Center Data Protection Manager, Windows event logs) are referenced without Linux alternatives, and diagnostic sections focus on Windows VMs and logs first.
Recommendations
- Add explicit Linux examples and instructions alongside Windows ones, especially for monitoring, diagnostics, and backup scenarios.
- Reference Linux equivalents for Windows tools (e.g., syslog for event logs, Linux backup solutions) and provide parity in documentation.
- Ensure that mentions of supported platforms (Windows, Linux) are balanced and that Linux is not relegated to secondary status.
- Include CLI and REST API usage examples that are platform-neutral or show both Windows and Linux usage.
- Clarify when features/tools are Windows-only and suggest Linux alternatives or workarounds.
Security
Detect and respond to ransomware attacks
...les/security/fundamentals/ransomware-detect-respond.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page exhibits a moderate Windows bias. It references Windows-specific tools and concepts such as PowerShell Operational logs and Security Event logs, and links to Defender for Endpoint documentation that is Windows-centric. There are no explicit Linux/macOS examples or mentions of equivalent Linux tools (e.g., syslog, auditd, Linux event logs) or commands. The guidance assumes familiarity with Windows patterns and omits Linux-specific detection and response steps, which may create friction for Linux users managing Azure resources.
Recommendations
- Include Linux/macOS equivalents for event log monitoring (e.g., syslog, auditd, journald).
- Provide examples of ransomware detection and response for Linux VMs in Azure, such as using Linux security tools (e.g., ClamAV, Linux Defender for Endpoint agent).
- Reference Linux-specific incident response actions (e.g., isolating Linux VMs, disabling compromised Linux accounts, patching via apt/yum/zypper).
- Add links to Linux Defender for Endpoint documentation and Linux security best practices.
- Ensure that examples and recommendations are balanced between Windows and Linux environments.
Security
Prevent subdomain takeovers with Azure DNS alias records and Azure App Service's custom domain verification
...n/articles/security/fundamentals/subdomain-takeover.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias, primarily through exclusive use of PowerShell scripts and references, with no Linux/macOS shell (bash, CLI) equivalents provided. The main tool for identifying dangling DNS records is a PowerShell script, and the only example for automating resource graph queries is via PowerShell. There is no mention of cross-platform alternatives, nor are Linux/macOS-specific instructions or examples given.
Recommendations
- Provide equivalent instructions and scripts for Azure CLI (az), Bash, or cross-platform scripting languages (e.g., Python) alongside PowerShell examples.
- Explicitly state platform compatibility for the provided PowerShell scripts, and offer installation guidance for PowerShell Core on Linux/macOS if PowerShell must be used.
- Include example commands for Linux/macOS users, such as using Azure CLI to query Resource Graph or manage DNS records.
- Add a note clarifying that the guidance applies to all platforms and highlight any platform-specific steps or limitations.
- Where possible, link to cross-platform tools or repositories, and encourage contributions for non-Windows environments.
Sentinel
Anomalies detected by the Microsoft Sentinel machine learning engine
...ocs/blob/main/articles/sentinel/anomalies-reference.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
powershell_heavy
Summary
The documentation page exhibits a notable Windows bias. Many anomaly detection rules and examples reference Windows-specific data sources (such as Windows Security logs and event IDs), and PowerShell is explicitly mentioned as a sub-technique. There is a lack of parity for Linux/macOS: no equivalent examples, log sources, or event IDs are provided for non-Windows platforms. The documentation does not mention Linux audit logs, syslog, or macOS equivalents, nor does it provide guidance for anomaly detection on those platforms.
Recommendations
- Add equivalent anomaly detection examples for Linux (e.g., using auditd, syslog, journald) and macOS (e.g., Unified Logs, Apple System Logger).
- Reference Linux/macOS event types and IDs where applicable, such as login failures, account creation, and code execution.
- Include Linux/macOS-specific MITRE ATT&CK sub-techniques (e.g., Bash, Zsh, Python) alongside PowerShell.
- Document how to onboard Linux/macOS logs into Sentinel for anomaly detection.
- Provide sample queries or detection rules for Linux/macOS environments.
- Avoid listing Windows examples first or exclusively when describing cross-platform features.
Site Recovery
Trusted launch VMs with Azure Site Recovery
...lob/main/articles/site-recovery/concepts-trusted-vm.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation exhibits moderate Windows bias. Several features (shared disks, 'Create a new VM' flow) are explicitly supported only for Windows OS, with Linux support either missing or not yet available. Windows is mentioned first in support matrices and feature lists. There are no Linux-specific examples or CLI commands, and migration instructions reference PowerShell and CLI channels but do not provide Linux-specific guidance or parity. The documentation does list supported Linux distributions and kernels, but practical Linux usage scenarios and examples are lacking.
Recommendations
- Provide Linux-specific examples and CLI commands, especially for migration and agent uninstallation.
- Clarify timelines or workarounds for Linux support in features currently limited to Windows (e.g., shared disks, VM creation flow).
- Present OS support in a neutral order or highlight Linux parity where available.
- Add troubleshooting and usage notes for Linux users, especially where steps differ from Windows.
- Explicitly state when a feature is unavailable for Linux and suggest alternatives or expected availability.
Sentinel
Stream data from Microsoft Defender XDR to Microsoft Sentinel in the Azure portal
...in/articles/sentinel/connect-microsoft-365-defender.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. It references Windows-specific technologies (Active Directory, Defender for Identity sensors, Windows Defender Antivirus) and focuses on integration patterns that are most relevant to Windows environments. There are no explicit Linux/macOS examples, nor is there guidance for non-Windows endpoints or identity sources. The event tables and configuration steps assume the reader is operating in a Microsoft-centric, Windows-heavy infrastructure, with no mention of Linux/macOS equivalents or how to handle non-Windows data sources.
Recommendations
- Add guidance for integrating Linux/macOS endpoints with Microsoft Sentinel, including how to stream security events from those platforms.
- Include examples or references for collecting identity and authentication data from non-Active Directory sources (e.g., LDAP, Azure AD-only, or Linux PAM logs).
- Clarify whether the connector supports ingestion of security events from Linux/macOS endpoints and, if so, provide configuration steps.
- If advanced hunting tables or features are Windows-only, explicitly state this and suggest alternative approaches for Linux/macOS data.
- Provide parity in examples, such as showing KQL queries for Linux event tables if available.
Sentinel
This file is auto-generated . Do not edit manually. Changes will be overwritten.
...in/articles/sentinel/includes/deprecated-connectors.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a notable Windows bias. Several deprecated connectors and data collection instructions focus on Windows agents, Windows machines, and Windows-specific event types (e.g., SecurityEvent, IIS logs). Windows examples and prerequisites are presented before or instead of Linux equivalents. While there is a section for Syslog (Linux), most other connectors lack explicit Linux instructions or parity, and Windows tooling (agents, event types) is referenced more frequently and prominently.
Recommendations
- For each connector, explicitly document Linux/macOS support, including prerequisites and installation steps for non-Windows platforms.
- Where Windows agents or event types are referenced, provide equivalent Linux/macOS agent instructions (e.g., AMA on Linux, syslog, auditd, etc.) and event types.
- Present Linux/macOS examples and tools alongside or before Windows examples to ensure parity.
- Clarify which connectors are Windows-only and which support cross-platform ingestion, and provide migration guidance for Linux users where relevant.
- Add links to Linux/macOS agent installation guides and troubleshooting resources.
Sentinel
Microsoft Sentinel User and Entity Behavior Analytics (UEBA) reference
...ure-docs/blob/main/articles/sentinel/ueba-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, primarily through its focus on Windows-centric data sources (e.g., Windows Security Events, Windows Forwarded Events, Microsoft Defender XDR, Active Directory) and terminology. Device and OS examples are exclusively Windows (e.g., 'Device family: Windows', 'Operating system: Windows 10'), with no mention of Linux or macOS equivalents in enrichment fields or sample values. There are no examples or guidance for Linux/macOS endpoints, log sources, or device enrichments, and Windows tools and patterns are referenced before any cross-platform or Linux alternatives.
Recommendations
- Add explicit examples and documentation for Linux and macOS endpoints, including how their logon/authentication events can be ingested and analyzed by UEBA.
- Include Linux/macOS device families and operating systems in enrichment field sample values and descriptions.
- Document supported Linux/macOS log sources and connectors (e.g., syslog, auditd, OSQuery) in the data sources table.
- Clarify whether non-Windows devices are supported for device insights and how their data is mapped.
- Provide parity in device-related enrichments and sample values for Linux/macOS.
- If Windows-only, clearly state limitations and recommend alternatives for non-Windows environments.
Storage
Plan for an Azure Files deployment
.../main/articles/storage/files/storage-files-planning.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation exhibits moderate Windows bias. Azure File Sync is described as a Windows Server-only solution, and Windows terminology and tools (Active Directory, SMB, PowerShell) are referenced more frequently and often before Linux equivalents. In protocol and identity sections, Windows OS versions are listed first and in more detail, while Linux is mentioned secondarily. There are references to using PowerShell and CLI for management and backup, but Linux-specific tools and workflows are not described. Examples and guidance for Linux (and macOS) users are limited or deferred to other documentation.
Recommendations
- Provide explicit Linux and macOS examples for mounting, managing, and backing up Azure file shares, including CLI commands and configuration steps.
- Include parity in tool recommendations (e.g., show Linux CLI workflows alongside PowerShell).
- Clarify limitations and alternatives for Linux users regarding Azure File Sync and other Windows-centric features.
- List supported OSes in a neutral order or group them by protocol rather than by Windows-first.
- Add links to Linux/macOS-specific guides wherever Windows tools or workflows are mentioned.
Storage
Zonal Placement for Azure File Shares
...cs/blob/main/articles/storage/files/zonal-placement.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
windows_first
Summary
The documentation provides command-line examples exclusively using Azure PowerShell, which is primarily a Windows-centric tool. There are no CLI examples for Linux/macOS users (e.g., Azure CLI or Bash). The structure presents PowerShell as the only scripting option, and does not mention or provide parity for Linux-native tools or workflows. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer Azure CLI/bash.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and preferred by many Linux/macOS users.
- Explicitly mention that Azure CLI can be used and provide links to Azure CLI documentation.
- Consider reordering or presenting both PowerShell and Azure CLI examples side-by-side, or allow users to select their preferred platform/tool via tabs.
- Clarify any limitations or differences between PowerShell and Azure CLI for these operations, if any exist.
Storage
Authorize access for AzCopy with a service principal
...mmon/storage-use-azcopy-authorize-service-principal.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation provides both Linux and Windows examples for environment variable setup, but consistently uses PowerShell for interactive examples (such as prompting for secrets/passwords) and references Windows-specific tools like Export-PfxCertificate. Guidance for secure secret entry is only shown in PowerShell, with no Linux shell equivalent. Windows tools and patterns (PowerShell, certificate store) are mentioned before or instead of Linux alternatives, and the Azure CLI section uses different environment variable values for Windows and Linux without clear explanation.
Recommendations
- Provide equivalent secure secret entry examples for Linux shells (e.g., using 'read -s' in bash) alongside PowerShell prompts.
- Mention Linux alternatives to Windows certificate management tools (e.g., 'openssl' for exporting certificates).
- Clarify why environment variable values differ between Windows and Linux for Azure CLI integration, and ensure parity if possible.
- Where PowerShell is used for interactive examples, also show bash/zsh equivalents for Linux/macOS users.
- Avoid referencing Windows certificate store and Export-PfxCertificate without mentioning Linux/macOS certificate handling.
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
powershell_heavy
Summary
The documentation provides both Windows and Linux troubleshooting steps, but Windows tools (iscsicli, mpclaim, PowerShell scripts) are frequently mentioned first or exclusively in some sections. Windows-specific scripts and parameters are highlighted, and PowerShell is referenced for configuration changes. Linux equivalents are present but sometimes secondary, and some examples (like session limits) are Windows-only.
Recommendations
- Ensure Linux examples and tools (e.g., iscsiadm, multipath) are mentioned first or alongside Windows equivalents.
- Provide parity in troubleshooting steps, including session limits and configuration changes for Linux/macOS.
- Include Bash or Python script examples for Linux where PowerShell scripts are provided for Windows.
- Clarify any OS-specific limitations and provide workarounds or alternatives for Linux/macOS users.
- Where possible, use cross-platform Azure CLI commands and avoid Windows-centric terminology.
Storage
What's New in Azure Files and Azure File Sync
...cs/blob/main/articles/storage/files/files-whats-new.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 terminology, tools (PowerShell), and features (Azure File Sync agent for Windows, Windows Server support) are frequently mentioned, often before or in greater detail than Linux equivalents. PowerShell and Windows-centric management patterns are referenced more often than Linux alternatives. Some features and enhancements are described with a Windows-first perspective, and Linux-specific examples or parity details are sometimes missing or less emphasized.
Recommendations
- Ensure Linux and macOS management tools (e.g., Bash, shell scripts, Linux CLI examples) are mentioned alongside PowerShell and Windows tools.
- Provide explicit Linux/macOS usage examples for Azure File Sync, mounting shares, and management tasks wherever Windows examples are given.
- Highlight parity and limitations for Linux/macOS users in feature descriptions, especially for agent extensions and authentication scenarios.
- Balance the order of presentation so Linux/NFS features are not consistently listed after Windows/SMB features.
- Add links to Linux/macOS documentation and troubleshooting guides in 'See also' sections.
Storage
Improve SMB Azure File Share Performance
...cs/blob/main/articles/storage/files/smb-performance.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 for SMB Multichannel, but Windows examples, tools, and configuration steps are presented first and in greater detail. Windows-specific tools (robocopy, diskspd.exe, PowerShell) are used for performance testing and verification, with no Linux equivalents or examples provided. Registration steps for features use only Azure PowerShell and portal, omitting CLI or Linux-native options. References to further documentation are Windows-centric.
Recommendations
- Provide Linux equivalents for performance testing (e.g., fio, dd, or ioping) and show example commands.
- Include Linux methods for verifying SMB Multichannel status and configuration (e.g., using smbstatus, dmesg, or mount options).
- Add Azure CLI examples for feature registration alongside PowerShell and portal instructions.
- Balance references to documentation by including links to Linux SMB Multichannel resources (e.g., Samba documentation).
- Present examples for both platforms in parallel tabs or sections, rather than Windows-first.
- Clarify any platform-specific limitations or differences in feature support.
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 workflows (such as Robocopy and the Previous Versions tab in File Explorer) are described in detail, with step-by-step instructions and screenshots. These Windows features are presented before Linux equivalents, and Linux-specific instructions are less detailed and appear later in the document. There is a lack of parity in example depth, especially for restoring SMB snapshots on Linux, where only mounting is described, not browsing or restoring files. Windows tools (Robocopy, File Explorer) are mentioned exclusively for local restore, while Linux alternatives are not discussed. PowerShell examples are present throughout, but Linux shell alternatives are limited to Azure CLI and basic mount/cp commands.
Recommendations
- Provide Linux/macOS-specific examples for restoring files from SMB snapshots, including browsing and copying files after mounting.
- Include parity in screenshots and step-by-step instructions for Linux workflows, similar to those provided for Windows.
- Mention and demonstrate Linux-native tools (e.g., rsync, cp) for copying/restoring files from mounted SMB/NFS snapshots.
- Clarify which features (such as Previous Versions) are Windows-only, and suggest Linux/macOS alternatives where possible.
- Ensure that example order alternates or is grouped by platform, rather than consistently presenting Windows first.
Application Gateway
What is Azure Application Gateway
...ocs/blob/main/articles/application-gateway/overview.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation lists Windows-centric tools (Azure PowerShell) before cross-platform options (Azure CLI) in the 'Next steps' section. This ordering may subtly signal a preference for Windows environments, and the explicit mention of PowerShell as a primary method can reinforce Windows bias, even though CLI is available. No Linux/macOS-specific examples or tools are mentioned.
Recommendations
- List Azure CLI before Azure PowerShell in example links, as CLI is cross-platform and widely used on Linux/macOS.
- Explicitly state that Azure CLI works on Linux/macOS and provide links to installation guides for those platforms.
- Add a note clarifying that all features are available via CLI and portal, ensuring Linux/macOS users are not disadvantaged.
- Consider including a Linux/macOS-specific quickstart or example to demonstrate parity.
Application Gateway
Application gateway components
.../application-gateway/application-gateway-components.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation lists Azure PowerShell (Windows-centric) before Azure CLI (cross-platform) in the 'Next steps' section, suggesting a subtle preference for Windows tools. No examples or instructions are given in this article, so there is no evidence of missing Linux examples or exclusive use of Windows tools. The rest of the content is platform-neutral.
Recommendations
- List Azure CLI before Azure PowerShell in 'Next steps', as CLI is cross-platform and more accessible to Linux/macOS users.
- Ensure future articles linked from this page provide both PowerShell and CLI examples, or prioritize CLI for parity.
- Explicitly mention that both CLI and PowerShell are supported and link to platform-specific instructions if available.
Active Directory B2C
Set up OAuth 2.0 client credentials flow
.../active-directory-b2c/client-credentials-grant-flow.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation page demonstrates mild Windows bias. It references PowerShell as the primary method for generating GUIDs and provides a PowerShell script as the first example for obtaining an access token. Windows tools and terminology are mentioned before cross-platform or Linux alternatives, though a cURL example is also provided. There is no explicit Linux/macOS example for GUID generation, and the scripting section leads with PowerShell.
Recommendations
- Include Linux/macOS command-line examples for GUID generation (e.g., `uuidgen` or `openssl rand -hex 16`).
- Present cURL (cross-platform) examples before or alongside PowerShell examples.
- Explicitly state that all steps can be performed on Linux/macOS and provide equivalent commands where relevant.
- Reference platform-agnostic online tools for tasks like GUID generation before mentioning Windows-specific tools.
- Add notes or sections for Linux/macOS users to clarify parity and any differences.
Automation
Enforce job execution on Azure Automation Hybrid Runbook Worker
...cles/automation/enforce-job-execution-hybrid-worker.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for policy creation and assignment, but PowerShell (a Windows-centric tool) is given equal prominence and is described in detail. There is a slight 'Windows first' bias in that PowerShell is presented as a primary option, and some explanatory details (such as resource ID retrieval) are shown only for PowerShell. No Linux/macOS-specific issues are present, but the documentation assumes familiarity with PowerShell, which is less common on non-Windows platforms.
Recommendations
- Ensure all command examples are fully covered for Azure CLI, which is cross-platform, and clarify that Azure CLI works natively on Linux/macOS.
- Add notes or links for installing and using Azure CLI on Linux/macOS.
- Where PowerShell-specific instructions are given (e.g., retrieving ResourceId), provide equivalent Azure CLI commands.
- Explicitly state that both Azure CLI and PowerShell are supported on all platforms, and recommend Azure CLI for Linux/macOS users.
- Consider listing Azure CLI examples before PowerShell to reduce perceived Windows bias.
Azure App Configuration
Configuration Provider Overview
...e-app-configuration/configuration-provider-overview.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation page demonstrates a mild Windows bias by listing .NET/.NET Framework libraries and samples first, which are traditionally associated with Windows development. The sample links for .NET libraries point to examples named 'DotNetCore' and 'DotNetFramework/WebDemo', which are often Windows-centric. There is no explicit mention of Linux/macOS compatibility for these libraries, nor are there platform-specific usage notes or parity assurances. However, the page does include libraries and samples for Java, Python, JavaScript, and Go, which are cross-platform.
Recommendations
- Explicitly state platform compatibility for each library, especially for .NET and .NET Framework, clarifying Linux/macOS support.
- Include Linux/macOS-specific sample links or usage notes for .NET libraries if supported.
- Balance the order of presentation by alternating or grouping cross-platform libraries together, rather than listing Windows-centric ones first.
- Add a section or note on cross-platform development considerations, especially for .NET users deploying on Linux.
- Ensure that all sample repositories include Linux/macOS instructions where applicable.
Azure Resource Manager
Bicep accessor operators
...icles/azure-resource-manager/bicep/operators-access.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation page is largely platform-neutral in its technical content and examples, focusing on Bicep syntax. However, in the 'Next steps' section, Windows-centric tools (Azure PowerShell, Visual Studio Code) are mentioned first or exclusively, and there is no explicit mention of Linux/macOS alternatives or parity (e.g., Azure CLI usage on Linux, VS Code alternatives, or cross-platform deployment instructions).
Recommendations
- Explicitly mention that Azure CLI is cross-platform and provide example commands for both Azure CLI and Azure PowerShell.
- Clarify that Visual Studio Code is available on Linux/macOS, or suggest other editors if applicable.
- Add a note or section on deploying Bicep files from Linux/macOS, including any platform-specific considerations.
- Ensure that instructions and links do not imply Windows is the default or only supported environment.
Application Gateway
Private Application Gateway deployment
...tion-gateway/application-gateway-private-deployment.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation presents Azure portal instructions first, followed by Azure PowerShell and then Azure CLI. PowerShell examples are detailed and include output, while CLI examples are present but less emphasized. There is a slight preference for Windows-centric tools (PowerShell) and ordering, which may create friction for Linux/macOS users who typically use Azure CLI or REST API. However, CLI instructions are present and functional, and REST API, ARM Template, Bicep, and Terraform are mentioned as options for configuration, though not exemplified.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples to better support Linux/macOS users.
- Include REST API, ARM Template, Bicep, and Terraform example snippets for feature registration and configuration.
- Clarify that Azure CLI works cross-platform and highlight its usage for non-Windows environments.
- Ensure output examples for CLI commands are as detailed as those for PowerShell.
- Add explicit notes or sections for Linux/macOS users where relevant.
Application Gateway
Configure Azure Application Gateway Private Link
...articles/application-gateway/private-link-configure.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation presents configuration options in the order: Azure portal, Azure PowerShell, and Azure CLI. The PowerShell section is detailed and extensive, with full command walkthroughs and cmdlet references, while the Azure CLI section is present but slightly less emphasized. There are no Linux/macOS-specific notes, nor are there Bash or shell script examples. The documentation does not mention Linux tools or patterns, and the PowerShell example precedes the CLI example, which may be more familiar to Linux/macOS users.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and preferred by many Linux/macOS users.
- Add explicit notes confirming that Azure CLI commands work on Linux/macOS and provide installation instructions or links for those platforms.
- Include Bash or shell script snippets for common tasks, where appropriate.
- Add troubleshooting or environment setup tips for Linux/macOS users, such as handling authentication or permissions.
- Ensure parity in detail and completeness between PowerShell and CLI sections.
Batch
Create a Batch pool with specified public IP addresses
...docs/blob/main/articles/batch/create-pool-public-ip.md
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation lists Azure PowerShell as a method for creating public IP addresses alongside the Azure portal and Azure CLI, but does not mention Linux/macOS equivalents (such as Bash scripts or direct REST API usage) for PowerShell. The order of methods places the Azure portal (GUI, often Windows-centric) first, then CLI, then PowerShell, which may subtly prioritize Windows tooling. However, the main example for creating the Batch pool uses Ubuntu as the VM image, and the REST API is platform-neutral.
Recommendations
- Explicitly mention that Azure CLI is cross-platform and provide sample commands for both Windows (PowerShell) and Linux/macOS (Bash).
- Clarify that PowerShell is available on Linux/macOS, or provide Bash examples for Linux users.
- Consider listing CLI and REST API methods before PowerShell and portal to avoid Windows-first ordering.
- Add a note or section highlighting Linux/macOS workflows for creating public IP addresses.
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The release notes mention Windows Server 2019/2022 and HPC Pack 2019 support before Linux equivalents. Windows-specific tools (HPC Pack) are highlighted, while Linux features (e.g., Slurm, Ubuntu 22) are mentioned later and with less detail. No Linux/macOS-specific examples or parity notes are provided.
Recommendations
- List Linux and Windows support/features together, or alternate their order to avoid Windows-first bias.
- Provide equal detail for Linux features (e.g., mention supported distributions and versions for Slurm clusters).
- Include notes/examples for Linux/macOS users where relevant, such as installation instructions or supported tools.
- Explicitly state Linux/macOS compatibility for new features where applicable.
IoT Central
Upload files from devices to Azure storage
...icles/iot-central/core/howto-configure-file-uploads.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation page exhibits minor Windows bias, primarily in the sample output and tooling references. The sample code's terminal output explicitly shows 'Machine: Windows_NT', and instructions reference using VS Code and <kbd>F5</kbd> for debugging, which is most common on Windows. However, the code snippets and commands (git, npm) are cross-platform, and there are no PowerShell-specific examples or Windows-only tools. Linux/macOS users can follow the instructions, but may encounter minor friction due to Windows-centric references.
Recommendations
- Show sample output for Linux/macOS (e.g., 'Machine: Linux', 'Machine: Darwin') alongside Windows output.
- Clarify that VS Code and <kbd>F5</kbd> debugging works on Linux/macOS as well.
- Avoid referencing OS-specific details in sample outputs unless necessary, or provide equivalent examples for other platforms.
- Explicitly state that the sample code and commands work on Linux/macOS, and mention any prerequisites for those platforms if needed.
IoT Hub Device Update
Prepare an update to import into Azure Device Update for IoT Hub | Microsoft Docs
...b/main/articles/iot-hub-device-update/create-update.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation page is generally cross-platform, focusing on Azure CLI usage in Bash environments and recommending Azure Cloud Shell. However, there is a subtle Windows bias: PowerShell-specific syntax is mentioned before Linux alternatives, and tips about escaping characters in PowerShell are given more prominence than Linux/Bash equivalents. The examples themselves use Bash syntax, but Windows/PowerShell considerations are frequently highlighted, which may create minor friction for Linux/macOS users.
Recommendations
- When discussing line continuation and escaping, present Bash/Linux guidance first, then mention PowerShell as an alternative.
- Include explicit examples for both Bash and PowerShell where syntax differs, ideally side-by-side.
- Add tips for common Bash/Linux issues (e.g., quoting/escaping) to balance PowerShell-specific notes.
- Clarify that Azure CLI is fully supported on Linux/macOS and provide links to platform-specific installation guides.
IoT Hub Device Update
Azure Device Update for IoT Hub using a Raspberry Pi image
...es/iot-hub-device-update/device-update-raspberry-pi.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation is generally Linux-focused, as the tutorial centers on a Raspberry Pi running a Yocto Linux image. However, there is a minor Windows bias in the SSH instructions, which specify using a PowerShell window to connect to the Raspberry Pi, without mentioning Linux/macOS terminal usage. No other Windows-specific tools, examples, or patterns are present, and all command-line instructions use Linux utilities.
Recommendations
- Update the SSH instructions to mention connecting from a Linux or macOS terminal, e.g., 'Open a terminal (PowerShell on Windows, Terminal on Linux/macOS) and run:'
- Ensure that any references to command-line usage are inclusive of all platforms, not just Windows.
- If screenshots or examples are shown from Windows tools (e.g., PowerShell), consider adding equivalent Linux/macOS visuals or notes.
IoT Hub
How to manage devices and modules using twins
...docs/blob/main/articles/iot-hub/manage-device-twins.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation includes several tips specifically for PowerShell users, such as escaping double quotes, but does not mention Linux/macOS shell equivalents (e.g., bash, zsh). Additionally, references to running Azure CLI in Windows Terminal and Cloud Shell are made before mentioning cross-platform compatibility, and no Linux/macOS-specific shell usage notes are provided. All CLI examples are generic, but the only shell-specific advice is for Windows/PowerShell users.
Recommendations
- Add equivalent shell escaping advice for bash/zsh users (e.g., how to handle quotes in Linux/macOS shells).
- Explicitly state that Azure CLI commands work on Linux/macOS and provide example commands for those platforms if there are differences.
- Mention common Linux/macOS terminals (e.g., GNOME Terminal, iTerm2) alongside Windows Terminal when discussing where to run Cloud Shell.
- Where PowerShell-specific tips are given, provide parity for bash/zsh users.
Resource Mover
Move resources to another region with Azure Resource Mover
...es/resource-mover/move-region-within-resource-group.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation presents Windows VM requirements before Linux VM requirements and mentions installing Windows updates explicitly, while Linux instructions are more generic. No command-line examples (PowerShell, Bash, CLI) are given, and no Windows-only tools or patterns are referenced. The overall process is portal-centric and does not show significant platform bias beyond ordering.
Recommendations
- List Linux VM requirements before or alongside Windows VM requirements to avoid implicit prioritization.
- Provide explicit Linux update instructions or link to common distributor update guides.
- Ensure parity in troubleshooting and prerequisites for both platforms.
- If command-line examples are added in future, include both PowerShell (Windows) and Bash/Azure CLI (Linux/macOS) equivalents.
Automation
Forward Azure Automation job data to Azure Monitor logs
...mation/automation-manage-send-joblogs-log-analytics.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation page demonstrates mild Windows bias, primarily through the use of PowerShell as the only mentioned CLI tool for interacting with job logs, and by referencing Windows-centric patterns (PowerShell error streams) when discussing job errors. There are no explicit Linux/macOS CLI examples (e.g., Azure CLI, Bash), nor is there mention of cross-platform alternatives for querying or automating these tasks outside of the Azure Portal and PowerShell. However, the majority of the instructions are portal-based and platform-agnostic, and the core log querying uses Kusto Query Language (KQL), which is not platform-specific.
Recommendations
- Add examples using Azure CLI (az) for querying job logs and managing diagnostic settings, alongside PowerShell.
- Explicitly mention that all portal-based steps are platform-agnostic and accessible from any OS.
- Where PowerShell is referenced (e.g., error streams), clarify how equivalent behavior or output can be obtained when using Bash or Python runbooks.
- Provide links or references to cross-platform automation and scripting documentation for Azure Automation.
Automation
Azure Automation Hybrid Runbook Worker Overview
...rticles/automation/automation-hybrid-runbook-worker.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation generally maintains parity between Windows and Linux, explicitly stating support for both platforms in most sections. However, there are subtle signs of Windows bias: PowerShell is mentioned as a primary onboarding channel before alternatives, and references to runbook job restarts specifically mention 'PowerShell Workflow runbooks' (which are Windows-centric). Windows terminology (e.g., 'System account') is used first, with Linux equivalents mentioned second. No Linux/macOS-specific examples, tools, or troubleshooting are provided, and onboarding instructions link to a combined Windows/Linux page without previewing Linux-specific steps.
Recommendations
- Provide explicit Linux/macOS examples and troubleshooting steps, especially for onboarding and runbook execution.
- Mention Linux tools and patterns (e.g., Bash, shell scripts) alongside PowerShell, and avoid listing PowerShell first unless contextually necessary.
- Clarify differences in runbook execution and permissions between Windows and Linux (e.g., differences in local accounts, service management).
- Ensure that all references to onboarding, management, and troubleshooting equally highlight Linux/macOS workflows.
- Consider adding a dedicated section or callouts for Linux/macOS users where platform-specific behavior or requirements exist.
Automation
Create an Azure Automation account using a Resource Manager template
...ation/quickstart-create-automation-account-template.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides deployment instructions for both PowerShell and Azure CLI, but PowerShell (a Windows-centric tool) is mentioned first and in more detail. The error handling and parameter instructions reference PowerShell before Azure CLI, and the example parameter syntax is shown for PowerShell first. There are no Linux-specific tools or shell examples (e.g., Bash), and the documentation does not mention platform differences or considerations for Linux/macOS users.
Recommendations
- Present Azure CLI (cross-platform) instructions before PowerShell, or in parallel, to avoid Windows-first bias.
- Include explicit Bash examples for Linux/macOS users where command-line deployment is discussed.
- Clarify that both PowerShell and Azure CLI are available on all platforms, and link to installation guides for Linux/macOS.
- Add a note about platform neutrality of the ARM template deployment process.
- Ensure error messages and troubleshooting steps reference both PowerShell and Azure CLI equally.
Automation
Quickstart: Use Terraform to create an Azure Automation account
...ickstarts/create-azure-automation-account-terraform.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for verifying results, but PowerShell is given equal prominence and is referenced in the 'Next steps' section. The final tutorial link specifically highlights PowerShell runbooks, which are Windows-centric, without mentioning Linux or Python alternatives. No Linux-specific tools or shell examples are provided, though the Azure CLI is cross-platform.
Recommendations
- Add explicit Bash/Linux shell examples for verification steps, showing usage in native Linux/macOS environments.
- Mention that Azure CLI commands work on Linux/macOS and provide any necessary platform-specific notes.
- In the 'Next steps' section, include links to tutorials for creating Python runbooks or using Linux-based automation, not just PowerShell.
- Clarify that PowerShell is available cross-platform, but also highlight alternatives for Linux/macOS users.
Azure Resource Manager
Template functions - deployment
...rce-manager/templates/template-functions-deployment.md
Low Priority
View Details â
Detected Bias Types
windows_tools
Summary
The documentation is largely platform-neutral, focusing on ARM template functions and their outputs. However, in the 'environment' section, when listing commands to view registered Azure environments, the Windows PowerShell cmdlet 'Get-AzEnvironment' is mentioned alongside the cross-platform 'az cloud list' CLI command. No Linux/macOS-specific tools or shell examples are provided, but the CLI command is listed first.
Recommendations
- Clarify that both 'az cloud list' and 'Get-AzEnvironment' are available on all platforms, but 'az cloud list' is cross-platform while 'Get-AzEnvironment' is PowerShell-specific.
- Provide example usage for both commands, noting platform compatibility.
- Consider adding a note or table summarizing which commands/tools are available on Windows, Linux, and macOS.
- If mentioning PowerShell, also mention Bash or other common Linux/macOS shells where relevant.
Automation
Archive for What's new in Azure Automation
...ocs/blob/main/articles/automation/whats-new-archive.md
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page is largely neutral and covers both Windows and Linux platforms for Azure Automation features. However, there is some evidence of Windows bias: Windows tools/scripts are named and referenced explicitly (e.g., 'Create Automation Windows HybridWorker'), and Windows support is sometimes mentioned before Linux equivalents (e.g., Hybrid Runbook Worker support for Windows Server 2008 R2 is highlighted separately). References to PowerShell modules (Az modules) and the PowerShell Gallery are present, but Linux equivalents (such as bash scripts or Linux-native tooling) are not described in detail. Most features and updates do mention Linux support where relevant, and Linux distributions are listed for compatibility, but examples and tooling references tend to favor Windows.
Recommendations
- Where Windows scripts/tools are named, ensure Linux equivalents are equally described and linked.
- Provide example commands or scripts for Linux alongside PowerShell/Windows examples.
- When referencing tools (e.g., Az modules), clarify Linux compatibility and usage, or offer Linux-native alternatives.
- Avoid listing Windows support before Linux unless there is a technical reason; present both platforms in parallel.
- Include more explicit Linux/macOS usage scenarios and troubleshooting tips.
Azure Change Tracking Inventory
Tutorial: Change a Workspace and Configure Data Collection Rules
...torial-change-workspace-configure-data-collection-rule.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
windows_registry_heavy
Summary
The documentation provides parity for both Windows and Linux file tracking, but Windows-specific concepts (Registry, environment variables) are given prominent placement and detail. Windows examples and tabs are listed before Linux equivalents, and Windows Registry configuration is covered in detail without a Linux equivalent (such as Linux configuration files or system settings). No PowerShell or CLI examples are present, but Windows-centric terminology and ordering may create friction for Linux users.
Recommendations
- Present Linux and Windows examples in parallel or alternate their order to avoid Windows-first bias.
- Include Linux equivalents for Windows Registry tracking, such as monitoring key configuration files (e.g., /etc/sysctl.conf, /etc/passwd) or system settings.
- Add more Linux-specific guidance or troubleshooting tips, especially for common Linux scenarios.
- Clarify that environment variable usage in paths is Windows-specific, and provide Linux alternatives (e.g., $HOME, $PATH).
- Consider adding CLI examples for Linux (bash, shell) where appropriate, not just Azure CLI.
Azure Functions
Event-driven Scaling in Azure Functions
.../main/articles/azure-functions/event-driven-scaling.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page shows a mild Windows bias. While most examples use Azure CLI (which is cross-platform), PowerShell examples are provided as a secondary tab, and there is a specific note about scale-in behaviors that applies only to 'apps running on Windows in a Consumption plan.' No explicit Linux/macOS-specific instructions, troubleshooting, or parity notes are given. There are no references to Windows-only tools, but the documentation does not clarify platform differences or provide Linux/macOS-specific examples where relevant.
Recommendations
- Add explicit notes clarifying that Azure CLI commands work on Linux/macOS and Windows, and provide bash/zsh shell examples if there are platform-specific considerations.
- Where PowerShell is shown, consider providing equivalent bash or shell script examples for Linux/macOS users.
- Clarify any platform-specific behaviors (such as the 'drain mode' note for Windows Consumption plan apps) and state whether/how they differ for Linux/macOS.
- Add troubleshooting or configuration notes for Linux/macOS users if there are known differences in scaling or deployment.
- Ensure that examples and instructions are presented in a platform-neutral way, or alternate between Windows and Linux/macOS examples.
Azure Functions
App settings reference for Azure Functions
...ain/articles/azure-functions/functions-app-settings.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation is generally cross-platform, but there are several instances of Windows bias. Windows-specific examples (e.g., environment variable delimiters, file paths) are presented before Linux equivalents, and some settings or tools (like PowerShell and Windows-specific Node.js version settings) are described without equal Linux/macOS coverage or with Windows as the default. PowerShell is referenced as a supported runtime, but Linux shell equivalents are not mentioned. Some settings are explicitly marked as Windows-only, and Windows patterns (e.g., %HOME% for paths) are used in examples.
Recommendations
- Present Linux/macOS examples alongside or before Windows examples, especially for environment variable delimiters and file paths.
- Where settings are Windows-only, provide Linux/macOS alternatives or clarify equivalent settings for those platforms.
- Include Linux/macOS shell examples (e.g., Bash) where PowerShell is referenced.
- Avoid using Windows-centric patterns (like %HOME%) in examples without showing the Linux/macOS equivalent ($HOME).
- Ensure that all platform-specific settings are clearly marked and alternatives are provided for other platforms.
Azure Functions
Update Language Versions in Azure Functions
...n/articles/azure-functions/update-language-versions.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation generally maintains parity between Windows and Linux, but there is a consistent pattern of presenting Windows instructions and examples before Linux equivalents. Windows-specific tools and configuration patterns (such as .NET isolated worker, PowerShell, and Windows portal/CLI commands) are often described first or in more detail. Some sections (e.g., updating language versions via Azure portal or CLI) default to Windows tabs and commands, requiring Linux users to scroll or switch tabs for their instructions. PowerShell is included as a first-class language throughout, which is inherently Windows-centric.
Recommendations
- Alternate the order of Windows and Linux instructions/examples, or present them side-by-side to avoid implicit prioritization.
- Explicitly call out Linux/macOS compatibility in introductory sections and tool requirements.
- Ensure all examples and instructions for updating language versions, troubleshooting, and slot management are equally detailed for Linux as for Windows.
- Where PowerShell is referenced, provide Bash or other Linux-native shell equivalents if applicable.
- Add a summary table at the top showing OS/language support and limitations for quick reference.
Azure Resource Manager
Bicep functions - deployment
...e-resource-manager/bicep/bicep-functions-deployment.md
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation references both Windows PowerShell (Get-AzEnvironment) and Azure CLI (az cloud list) tools for listing Azure environments, but lists the PowerShell command first and provides a direct link to its documentation before the CLI equivalent. No Linux/macOS-specific examples or guidance are given, and the overall examples are platform-neutral otherwise.
Recommendations
- List Azure CLI (az cloud list) before PowerShell commands, as CLI is cross-platform.
- Provide explicit Linux/macOS usage notes or examples where relevant.
- Clarify that both tools are available cross-platform, but CLI is natively supported on Linux/macOS.
- Add links to Azure CLI installation and usage guides for Linux/macOS users.
Azure Resource Manager
Bicep functions - resources
...ure-resource-manager/bicep/bicep-functions-resource.md
Low Priority
View Details â
Detected Bias Types
windows_tools
powershell_heavy
windows_first
Summary
The documentation page provides both Azure CLI and PowerShell examples for discovering list operations, but the PowerShell example (Get-AzProviderOperation) is presented first and is more detailed. The CLI example is present but less emphasized. There are no Linux/macOS-specific examples or mentions of platform differences. No examples rely on Windows-only tools, but the ordering and emphasis slightly favor Windows/PowerShell users.
Recommendations
- Present Azure CLI examples before PowerShell examples to avoid implicit Windows-first bias.
- Expand Azure CLI examples with more context and explanation, matching the detail given to PowerShell.
- Explicitly state that both CLI and PowerShell commands work cross-platform and provide links to installation guides for Linux/macOS.
- Consider adding a note or example for using Bicep and related tools on Linux/macOS, if relevant.
Azure Functions
Storage considerations for Azure Functions
...ain/articles/azure-functions/storage-considerations.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
minor_windows_tools
Summary
The documentation generally maintains cross-platform neutrality, but there are minor signs of Windows bias. Windows hosting plans and features are mentioned before Linux equivalents in several places, and PowerShell examples are provided alongside Azure CLI, sometimes with more detail. Some settings and scaling notes are Windows-specific, and Windows plans are referenced first in certain deployment scenarios. However, Linux-specific features (like mounting Azure Files) are clearly documented, and Linux parity is generally maintained.
Recommendations
- Ensure Linux and macOS examples are provided alongside Windows/PowerShell examples, especially in sections describing deployment and configuration.
- When listing hosting plans or features, alternate the order or explicitly mention Linux parity where applicable.
- Clarify which features/settings are Windows-only and provide Linux alternatives or workarounds where possible.
- Expand Linux-specific guidance, such as mounting file shares, with more detailed examples and troubleshooting tips.
- Where PowerShell is used, provide equivalent Bash or Azure CLI commands for Linux/macOS users.
Azure Resource Manager
Create and deploy Azure deployment stacks in Bicep
...cles/azure-resource-manager/bicep/deployment-stacks.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation consistently presents Azure PowerShell examples before Azure CLI examples in every code tab, and PowerShell is referenced as a primary tool throughout. This ordering and emphasis may subtly favor Windows users, as PowerShell is natively available on Windows and historically associated with that platform. However, Azure CLI is cross-platform and all examples are provided for both tools, with no actual functionality missing for Linux/macOS users. No Windows-only tools or patterns are used, and all commands are available via Azure CLI, which works on Linux/macOS.
Recommendations
- Alternate the order of PowerShell and CLI examples, or present CLI examples first to reflect cross-platform parity.
- Explicitly state that both Azure PowerShell and Azure CLI are available on all major platforms, including Linux and macOS.
- Where possible, highlight CLI usage as the default for scripting and automation, since it is more universally available.
- Add a short section clarifying that PowerShell Core is available for Linux/macOS, and link to installation instructions for non-Windows platforms.
- Consider a single combined example section (CLI and PowerShell side-by-side) for brevity and parity.
Azure Resource Manager
Develop a deployment script in Bicep
...re-resource-manager/bicep/deployment-script-develop.md
Low Priority
View Details â
Detected Bias Types
windows_tools
powershell_heavy
windows_first
Summary
The documentation provides both Azure CLI (Bash) and Azure PowerShell examples for every major scenario, maintaining parity in most technical content. However, there are signs of Windows bias: PowerShell is treated as a first-class scripting option throughout, and Windows-specific tools and APIs (e.g., CommandLineToArgvW, Connect-AzAccount) are referenced. The documentation sometimes references Windows concepts (e.g., .ps1 scripts, PowerShell cmdlets) and APIs before or more prominently than their Linux equivalents. The use of PowerShell as a primary scripting language, and references to Windows APIs, may create friction for Linux/macOS users who are less familiar with these tools.
Recommendations
- Clarify that PowerShell is cross-platform and provide explicit notes or links for Linux/macOS users on installing and using PowerShell Core.
- Where Windows-specific APIs (e.g., CommandLineToArgvW) are referenced, explain how argument parsing works on Linux/macOS, or note that this is abstracted away in the container environment.
- Add a short section or callout for Linux/macOS users, highlighting any differences in script authoring, file permissions, or environment setup.
- Ensure that CLI (Bash) examples are shown before or alongside PowerShell examples, rather than after.
- Explicitly mention that both Bash and PowerShell containers run on Ubuntu, and clarify any OS-specific behaviors or limitations.
Low Priority
View Details â
Detected Bias Types
windows_tools
Summary
The documentation page references Visual Studio Code and the Bicep CLI, both of which are cross-platform tools. However, there is a minor bias in the linter rule list: the rule 'use-recent-az-powershell-version' references PowerShell, which is traditionally associated with Windows, though it is now available on Linux/macOS. No command-line examples are shown, and no Windows-specific tools or patterns are prioritized. The page does not provide Linux/macOS-specific examples or mention platform-specific differences.
Recommendations
- Clarify that both Visual Studio Code and Bicep CLI are available on Windows, Linux, and macOS.
- If referencing PowerShell, note that PowerShell Core is cross-platform and provide equivalent Bash/Azure CLI guidance where relevant.
- Add explicit command-line examples for both Windows (PowerShell/CMD) and Linux/macOS (Bash) to demonstrate parity.
- Mention any platform-specific considerations for using the Bicep linter, if any exist.
Azure Resource Manager
Create a private container registry in Azure for Bicep modules
...zure-resource-manager/bicep/private-module-registry.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation presents both Azure PowerShell and Azure CLI examples for key tasks, but PowerShell (a Windows-centric tool) is consistently listed first. There is a notable emphasis on PowerShell commands and references to Windows-specific paths. Linux and macOS equivalents are mentioned for local cache paths, but command-line examples do not include explicit Linux/macOS shell variants (e.g., Bash). No Linux-specific tools or workflows are described, and the documentation assumes familiarity with Windows tooling and patterns.
Recommendations
- Alternate the order of Azure PowerShell and Azure CLI examples, or present CLI examples first to reduce implicit Windows prioritization.
- Add explicit Bash/zsh shell examples for Linux/macOS users where relevant, especially for file paths and environment variables.
- Highlight cross-platform usage of Azure CLI, and clarify that PowerShell is available on Linux/macOS but is less commonly used.
- Include troubleshooting or tips for Linux/macOS users, such as permissions or path expansion nuances.
- Reference Linux/macOS documentation links alongside Windows-specific ones.
Azure Resource Manager
Create Bicep files with Visual Studio Code
...les/azure-resource-manager/bicep/visual-studio-code.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation is generally cross-platform, focusing on Visual Studio Code and Bicep, which are available on Windows, Linux, and macOS. However, there are subtle Windows biases: Azure PowerShell is mentioned alongside Azure CLI as a prerequisite, and PowerShell examples are provided in parallel with CLI examples. In the 'Insert Resource' section, Azure CLI is listed before Azure PowerShell, but both are given equal prominence. There are no Linux-specific tools or patterns mentioned, and no macOS-specific considerations. The documentation does not provide Linux/macOS-specific troubleshooting or example screenshots, but it does not prevent Linux/macOS users from completing tasks.
Recommendations
- Explicitly state that all instructions and tools (VS Code, Bicep extension, Azure CLI) work on Linux and macOS as well as Windows.
- Include Linux/macOS-specific notes or screenshots where relevant (e.g., keyboard shortcuts, file paths).
- When listing command-line tools, clarify that Azure CLI is cross-platform and highlight its parity with PowerShell.
- Add troubleshooting tips for Linux/macOS environments if there are known issues (e.g., permissions, installation paths).
- Avoid implying PowerShell is required or preferred; emphasize CLI as the default for cross-platform use.
Azure Resource Manager
What are the resource providers for Azure services
...anager/management/azure-services-resource-providers.md
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page lists resource providers for Azure services and provides examples for finding resource providers using Azure CLI, PowerShell, and Python SDK. There is a minor Windows bias: PowerShell (a Windows-centric tool) is given as an example alongside CLI and Python, and references to 'Windows Azure Service Management API' and 'Azure Serial Console for Windows' appear in the text. However, Linux/macOS users are not blocked from completing any tasks, as Azure CLI and Python examples are cross-platform.
Recommendations
- Clarify that PowerShell examples are primarily for Windows users, and suggest Bash or shell alternatives for Linux/macOS.
- Where PowerShell is shown, consider showing Bash or shell equivalents for Linux/macOS users.
- When referencing 'Windows Azure Service Management API', clarify its relevance to non-Windows environments.
- For sections mentioning 'Azure Serial Console for Windows', provide links or notes about Linux/macOS equivalents if available.
Backup
Back up Azure Kubernetes Service by using Azure Backup
...cles/backup/azure-kubernetes-service-cluster-backup.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates a mild Windows bias by referencing Azure PowerShell as an alternative method for backup and restore, both in the introduction and in the 'Next steps' section, without mentioning Azure CLI or Bash equivalents. There are no Linux/macOS-specific instructions or examples, and the only command-line example given uses kubectl (which is cross-platform). The documentation focuses on GUI (Azure portal) workflows, but when scripting is mentioned, it is Windows-centric.
Recommendations
- Include Azure CLI examples alongside or before Azure PowerShell examples for backup and restore operations.
- Explicitly mention that kubectl commands work on Linux/macOS and provide any OS-specific caveats if relevant.
- Add links to Linux/macOS-friendly guides or scripts where applicable.
- Ensure parity in 'Next steps' by listing Azure CLI documentation if available.
Backup
Azure Kubernetes Service (AKS) backup support matrix
...azure-kubernetes-service-cluster-backup-support-matrix.md
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation references Azure PowerShell alongside Azure CLI, Terraform, ARM, and Bicep as supported tools for backup and restore operations. Azure PowerShell is a Windows-centric tool, and its mention (including dedicated links for backup and restore) signals a Windows bias. There is no explicit mention of Linux/macOS equivalents for PowerShell, nor are there Bash or shell script examples. Additionally, the order of tools in the 'Next steps' section lists Azure PowerShell before ARM and Bicep, which may reinforce a Windows-first perception. However, the main backup extension itself only supports Ubuntu or Azure Linux node pools, and not Windows-based node pools, which is a technical limitation rather than a documentation bias.
Recommendations
- Provide explicit Bash or shell script examples for Linux/macOS users where PowerShell is referenced.
- Clarify that Azure CLI and Terraform are cross-platform and recommend them for Linux/macOS users.
- Reorder tool references in 'Next steps' to list cross-platform tools first (e.g., Azure CLI, Terraform) and note platform specificity for PowerShell.
- Add a note that Azure PowerShell is primarily for Windows and suggest alternatives for Linux/macOS users.
Backup
Tutorial - Restore a VM with Azure CLI
...ocs/blob/main/articles/backup/tutorial-restore-disk.md
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation is primarily focused on Azure CLI, which is cross-platform and suitable for both Linux and Windows users. However, there is a notable reference to PowerShell and a link to a PowerShell-based tutorial early in the page, and some terminology (such as 'container-name' and 'item-name' referring to VMs) may be more familiar to Windows/Azure users. The only explicit mention of an alternative platform is the PowerShell link, which is presented before the CLI instructions. All command examples are in Azure CLI, which is not Windows-specific, and there are no PowerShell or Windows command examples in the main content. There are no Linux/macOS-specific instructions or examples, but the CLI commands are applicable across platforms.
Recommendations
- Move or rephrase the PowerShell reference so it does not appear before the CLI instructions, or add a similar reference for Bash/shell scripting if relevant.
- Explicitly state that all Azure CLI commands work on Linux, macOS, and Windows, and consider adding a brief note or section for common Linux/macOS shell environments.
- If there are any platform-specific caveats (e.g., path handling, authentication differences), mention them.
- Consider adding a short example of running these commands in a Bash shell to reinforce cross-platform parity.
Low Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation shows minor Windows bias, particularly in sections discussing browser support and keyboard layout configuration. Windows tools and workflows are mentioned first or exclusively, such as instructions for setting keyboard layouts, while Linux/macOS equivalents are omitted. There are no PowerShell-heavy sections or exclusive use of Windows tools, but Linux/macOS users may need to infer their own steps.
Recommendations
- Add instructions for setting keyboard layouts on Linux and macOS systems alongside the Windows example.
- When listing browser support, mention Linux explicitly and provide guidance for supported browsers on Linux.
- Ensure examples and configuration steps are presented for all major platforms (Windows, Linux, macOS) where relevant.
- Avoid listing Windows tools or workflows first unless they are universally applicable; use neutral or platform-agnostic language where possible.
Batch
Copy applications and data to pool nodes
...ain/articles/batch/batch-applications-to-pool-nodes.md
Low Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation page exhibits mild Windows bias by referencing Windows-specific installation formats (e.g., .exe, .msi) and omitting explicit Linux/macOS examples or tool references. Windows-centric terminology appears first in several sections, and there are no mentions of Linux package formats (e.g., .sh, .deb, .rpm) or cross-platform installation commands.
Recommendations
- Add examples for Linux/macOS application installation, such as using shell scripts (.sh), or package managers (apt, yum, etc.).
- Mention Linux/macOS equivalents alongside Windows examples (e.g., .deb/.rpm for .msi, bash scripts for PowerShell).
- Clarify that application packages and resource files can be used for any OS, and provide sample install commands for both Windows and Linux.
- Include notes or links to documentation on Linux/macOS node configuration and data transfer best practices.
Bastion
Tutorial: Deploy Azure Bastion using specified settings: Azure portal
...b/main/articles/bastion/tutorial-create-host-portal.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation mentions both Windows and Linux virtual machines, but in the prerequisites section, the Windows VM creation link is listed before the Linux VM creation link. Additionally, port requirements for Windows (RDP) are listed before Linux (SSH). However, there are no examples, instructions, or tools that are exclusive to Windows or PowerShell, and the tutorial is focused on Azure portal usage, which is cross-platform.
Recommendations
- List Linux VM creation links before or alongside Windows VM creation links to avoid implicit prioritization.
- List port requirements for Linux (SSH) before or alongside Windows (RDP).
- Explicitly state that all steps are applicable to both Windows and Linux VMs.
- Add clarifying notes or examples for Linux/macOS users where relevant, especially in connection steps.
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation page displays a mild Windows bias: Windows examples and tools (cmd.exe) are consistently mentioned before Linux equivalents, and Windows-specific patterns (e.g., environment variable naming conventions, file path separators) are described in detail. Linux is covered, but often as a secondary consideration, and some explanations (e.g., directory postfixes) use Windows-style paths by default.
Recommendations
- Present Linux and Windows examples side-by-side, or alternate which is shown first.
- Use neutral language when describing environment variable naming conventions and file paths, or provide both Windows and Linux formats explicitly.
- Clarify Linux-specific behaviors and provide Linux-first examples where appropriate.
- Ensure tables and examples include both Windows and Linux variants for all relevant variables and paths.
Batch
Choose VM sizes and images for pools
...e-docs/blob/main/articles/batch/batch-pool-vm-sizes.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both PowerShell and Azure CLI examples for listing VM sizes and images, but PowerShell (a Windows-centric tool) is consistently mentioned first in lists and tips. There are no Linux-specific shell examples (e.g., Bash), nor is there mention of Linux/macOS-specific tooling or patterns. However, Azure CLI is cross-platform and included in all example commands, and the documentation explicitly covers both Windows and Linux VM images.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or list Azure CLI first to reflect its cross-platform nature.
- Add explicit Bash shell examples where relevant, especially for Linux/macOS users.
- Clarify that Azure CLI is available on Windows, Linux, and macOS.
- Include notes or links for installing and using Azure CLI on Linux/macOS.
- If PowerShell is mentioned, note that PowerShell Core is available cross-platform, or provide equivalent Bash commands.
Cost Management Billing
Programmatically create Azure subscriptions with legacy APIs
...manage/programmatically-create-subscription-preview.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides examples for REST, Azure PowerShell, and Azure CLI when creating EA subscriptions, but PowerShell is given a prominent position, including explicit instructions to use Azure Cloud Shell with PowerShell. The PowerShell tab appears before Azure CLI, and references to installing PowerShell modules are present. There is no mention of Bash or Linux/macOS-specific shell usage, nor are there any examples or notes about platform differences for CLI or REST usage. For MCA and MPA accounts, only REST API examples are provided, which are platform-neutral. However, the overall pattern and ordering suggest a mild Windows/PowerShell bias, especially in the EA section.
Recommendations
- Add explicit notes that Azure CLI and REST API examples work equally well on Linux, macOS, and Windows.
- Instruct users that Azure Cloud Shell supports both Bash and PowerShell, and provide Bash examples or clarify that CLI commands can be run in Bash.
- Reorder example tabs so that Azure CLI appears before PowerShell, or alternate ordering in different sections.
- Where PowerShell module installation is discussed, provide equivalent instructions for Azure CLI installation on Linux/macOS.
- Add a brief section or callout confirming cross-platform compatibility for all API and CLI commands.
Cost Management Billing
Programmatically create MCA subscriptions across tenants
...bscription-microsoft-customer-agreement-across-tenants.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 retrieving the service principal ID, but lists Azure CLI first. However, throughout the rest of the document, all command-line examples are platform-agnostic (HTTP requests via REST API), and there are no explicit Windows-only tools or patterns. There is a slight bias in listing PowerShell as an alternative, but no Linux shell (e.g., Bash) or macOS-specific instructions are provided. No explicit Linux/macOS examples or troubleshooting notes are present.
Recommendations
- Add explicit Linux/macOS instructions or troubleshooting notes for Azure CLI and REST API usage.
- Include Bash shell examples for relevant CLI commands.
- Clarify that Azure CLI is cross-platform and can be used on Linux/macOS, and provide installation links for non-Windows platforms.
- Consider listing Azure CLI examples before PowerShell, or provide parity in example order.
- Mention any platform-specific caveats (e.g., authentication differences) if applicable.
Cost Management Billing
Protect tenants and subscriptions from abuse and fraud attacks
...gement-billing/manage/protect-tenants-subscriptions.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a mild Windows bias by referencing Microsoft-specific tools and portals (Azure portal, Microsoft 365 Admin Center, Microsoft Entra ID) without mentioning cross-platform or Linux/macOS alternatives. No command-line examples are provided, and where deletion or management actions are described, only web-based or Windows-centric interfaces are referenced. Additionally, related links such as 'Delete resource group and resources' default to Azure PowerShell tabs, with no mention of Azure CLI or REST API alternatives that are more platform-agnostic.
Recommendations
- Include examples using Azure CLI and REST API for subscription and resource management, as these are cross-platform and work on Linux/macOS.
- Where possible, provide parity in instructions for actions (deleting tenants, transferring subscriptions) using both GUI (portal) and CLI/API methods.
- Explicitly mention that the described actions can be performed from any OS using browser-based portals or CLI tools.
- In related content, ensure that links or tabs default to platform-neutral tools (e.g., Azure CLI) or provide equal visibility to both PowerShell and CLI/API options.
Cost Management Billing
View and download Azure usage and charges
...ement-billing/understand/download-azure-daily-usage.md
Low Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page focuses almost exclusively on the Azure Portal (web UI) and Azure CLI for usage and charges, which are cross-platform. However, all screenshots and step-by-step instructions implicitly assume a Windows environment (e.g., GUI screenshots, navigation patterns), and there are no explicit Linux/macOS examples, such as shell scripting or automation patterns. There is no mention of Powershell or Windows-only tools, but the ordering and visual cues favor Windows users. Linux parity is present via Azure CLI, but not highlighted.
Recommendations
- Add explicit notes that the Azure Portal and Azure CLI are cross-platform and can be used from Linux/macOS.
- Include screenshots or instructions for Linux/macOS environments where relevant (e.g., terminal usage, file downloads).
- Provide example automation patterns for Linux/macOS (e.g., using curl/wget to download files, bash scripting).
- Clarify that all CLI commands work on Linux/macOS and Windows equally.
- If Powershell is mentioned elsewhere, ensure Bash equivalents are provided.
IoT Dps
Symmetric key attestation with Azure DPS
...articles/iot-dps/concepts-symmetric-key-attestation.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides platform-specific examples for generating derived device keys, with the Windows/PowerShell example presented before the Linux/openssl example. The PowerShell example is detailed and uses Windows-specific tooling, while the Linux example uses openssl. Both platforms are covered, but Windows is given precedence in ordering and example detail.
Recommendations
- Present Linux and Windows examples in parallel or alternate their order to avoid implicit prioritization.
- Ensure equal detail and clarity in both Linux and Windows instructions.
- Consider adding macOS-specific instructions if there are platform differences (e.g., openssl usage nuances).
- Explicitly state that all examples are equivalent and supported across platforms.
- Include a cross-platform script or language-neutral pseudocode for key derivation.
IoT Hub
Register and connect an IoT device
...cs/blob/main/articles/iot-hub/create-connect-device.md
Low Priority
View Details â
Detected Bias Types
windows_tools
powershell_heavy
windows_first
Summary
The documentation mentions Windows-centric tools such as PowerShell and Visual Studio Code extensions as primary alternatives for managing device identities, with PowerShell listed first. While the main instructions use the Azure portal and Azure CLI (which are cross-platform), the 'Other tools' section prioritizes Windows tools and does not mention Linux-native options (e.g., Bash scripts, Linux desktop tools) or clarify CLI parity for Linux/macOS. There are no explicit Linux/macOS examples or recommendations, and Windows tools are referenced before REST API or other platform-neutral methods.
Recommendations
- Add explicit examples or notes for Linux/macOS users, such as using Bash scripts or shell commands for device management.
- Clarify that Azure CLI is fully supported on Linux/macOS and provide installation links for those platforms.
- List REST API and cross-platform tools before Windows-specific tools like PowerShell.
- If PowerShell is mentioned, note that PowerShell Core is available on Linux/macOS and provide usage examples for those platforms.
- Include references to Linux desktop tools or open-source alternatives if available.
IoT Hub
Create and delete routes and endpoints by using Azure Resource Manager
...-docs/blob/main/articles/iot-hub/how-to-routing-arm.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Resource Manager templates, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and in some cases appears first. File path examples use backslashes (e.g., "my\path\to\template.json"), which are Windows-style and may confuse Linux/macOS users. There are no explicit Linux/macOS-specific instructions, nor is Bash or shell scripting mentioned. The Azure portal instructions are platform-neutral, but command-line sections show a mild Windows bias.
Recommendations
- Show Azure CLI examples first, as it is cross-platform and preferred for Linux/macOS users.
- Use forward slashes in file path examples or note that Linux/macOS users should use forward slashes.
- Explicitly mention that Azure CLI works on Linux/macOS and provide Bash shell usage notes where relevant.
- Consider adding a Bash script example for template deployment.
- Clarify that PowerShell Core is available cross-platform, but most Linux/macOS users will use Azure CLI.
IoT Hub
Understand Azure IoT Hub endpoints
...ob/main/articles/iot-hub/iot-hub-devguide-endpoints.md
Low Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation page shows mild Windows bias, primarily in the example code for listing blobs in Azure Storage, which uses C# and the Microsoft.Azure.Storage libraryâa pattern most familiar and accessible to Windows users. Additionally, the instructions for assigning Cosmos DB roles mention Azure CLI and Azure PowerShell, but do not provide explicit Linux/macOS command examples or clarify cross-platform usage. No Linux-specific tools, SDKs, or code samples are provided, and Windows-centric technologies are implicitly prioritized.
Recommendations
- Provide equivalent code samples using Python (with Azure SDK), Bash, or other cross-platform languages for tasks like listing blobs in Azure Storage.
- Explicitly mention that Azure CLI is cross-platform and provide example commands for Linux/macOS users, especially for role assignment in Cosmos DB.
- Include references to Linux/macOS compatible SDKs and tools where relevant.
- Balance example order by alternating or leading with cross-platform or Linux-friendly examples.
- Clarify that PowerShell is available on Linux/macOS, or offer Bash alternatives where possible.
IoT Dps
Quickstart - Use Terraform to create a DPS instance
...ticles/iot-dps/quick-setup-auto-provision-terraform.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash (Azure CLI) and Azure PowerShell examples for verifying the DPS resource, but the PowerShell example is given equal prominence and is not clearly marked as Windows-specific. There is no explicit Linux/macOS example for PowerShell, and the structure may imply parity between Bash and PowerShell, which can be confusing for Linux/macOS users. However, the main workflow uses Terraform, which is cross-platform, and the Bash (Azure CLI) example is present.
Recommendations
- Clearly label Azure PowerShell examples as Windows-only or primarily for Windows users.
- Present Bash (Azure CLI) examples first to prioritize cross-platform usage.
- Add explicit notes or tabs for Linux/macOS users, clarifying that Azure CLI is recommended for those platforms.
- Consider omitting PowerShell examples unless there is a specific Windows-only step, or provide equivalent Linux/macOS instructions where possible.
IoT Hub Device Update
Import an update to Azure Device Update for IoT Hub
...b/main/articles/iot-hub-device-update/import-update.md
Low Priority
View Details â
Detected Bias Types
windows_tools
powershell_heavy
windows_first
Summary
The documentation page demonstrates some Windows bias, primarily in the 'Import using the Device Update APIs' section, where PowerShell modules are highlighted as a sample method for programmatic import, and PowerShell is mentioned as a cross-platform tool. Additionally, the mention of supported browsers for the Azure portal lists Microsoft Edge first, and the use of Windows-centric tools (PowerShell, Storage Explorer) is more prominent than Linux alternatives. However, the Azure CLI instructions are Bash-centric and suitable for Linux/macOS, and AzCopy is recommended for large uploads, which is cross-platform.
Recommendations
- Provide explicit Linux/macOS shell script examples for API usage, not just PowerShell.
- List cross-platform tools (AzCopy, Azure CLI) before Windows-specific ones (PowerShell, Storage Explorer).
- Include Linux-native upload methods (e.g., curl, Python scripts) for Azure Blob Storage.
- Clarify that PowerShell is available on Linux/macOS, but also offer Bash or Python alternatives for scripting.
- When listing supported browsers, avoid Windows-first ordering or mention all major browsers equally.
IoT Hub
Upload files from your device to the cloud with Azure IoT Hub
...-docs/blob/main/articles/iot-hub/how-to-file-upload.md
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation mentions Azure PowerShell as a configuration option for file upload before listing Linux-friendly alternatives like Azure CLI and the Azure portal. PowerShell is primarily a Windows tool, and its mention alongside CLI and portal may suggest a Windows-centric approach. However, the main SDK usage examples are language-based and do not show explicit OS bias.
Recommendations
- List Azure CLI before Azure PowerShell when describing configuration options, as CLI is cross-platform.
- Explicitly state that Azure CLI and Azure portal are cross-platform and suitable for Linux/macOS users.
- If PowerShell is mentioned, clarify that Azure PowerShell is available on Linux/macOS, or provide links to installation instructions for non-Windows platforms.
- Consider adding a note or section for Linux/macOS users to highlight parity and any OS-specific considerations.
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for managing IP filter rules, but the PowerShell section is given equal prominence to CLI, and no Linux/macOS-specific shell examples (e.g., Bash) are provided. The screenshots and portal instructions are platform-neutral, but the command-line guidance may feel Windows-centric due to the inclusion of PowerShell and lack of Linux/macOS shell examples.
Recommendations
- Add explicit Bash or shell script examples for Linux/macOS users, especially for tasks like parsing or manipulating the JSON output from Azure CLI.
- Clarify that Azure CLI commands work cross-platform and provide tips for Linux/macOS environments (e.g., using jq for JSON parsing).
- Consider reordering sections so that Azure CLI (which is cross-platform) appears before PowerShell, or explicitly state platform applicability for each method.
- Mention that PowerShell Core is available on Linux/macOS, if relevant, and provide installation guidance or links.
IoT Hub
Managing public network access for Azure IoT Hub
...main/articles/iot-hub/iot-hub-public-network-access.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 checking IoT Hub access, but PowerShell is shown alongside CLI without explicit Linux/macOS shell examples. The troubleshooting and workflow instructions reference the Azure portal and Cloud Shell, which are cross-platform, but command-line examples do not clarify Linux/macOS usage or show bash-specific patterns. There is a subtle Windows-first bias in the ordering and inclusion of PowerShell commands, and no explicit Linux/macOS shell commands or screenshots.
Recommendations
- Add explicit bash/zsh shell examples for Linux/macOS users, especially for Azure CLI commands.
- Clarify that Azure CLI commands work cross-platform and can be run in bash, zsh, or other shells.
- If showing PowerShell, also show equivalent bash commands and note platform compatibility.
- Include screenshots or instructions for Linux/macOS environments where relevant.
- State platform compatibility for each command example (e.g., 'This command works in bash, PowerShell, etc.')
IoT Hub
X.509 certificates | Microsoft Docs
...b/main/articles/iot-hub/reference-x509-certificates.md
Low Priority
View Details â
Detected Bias Types
windows_tools
powershell_heavy
windows_first
Summary
The documentation page is largely cross-platform, with most examples using OpenSSL and Bash, which are standard on Linux/macOS. However, in the 'Verify certificate manually after upload' section, the PowerShell script is mentioned first as a method to generate a verification certificate, and Windows tooling (PowerShell) is given equal prominence to Bash/OpenSSL. The reference to 'the PowerShell script supplied by Microsoft' and the ordering of Windows tools before Bash/OpenSSL indicate a mild Windows bias.
Recommendations
- List Bash/OpenSSL methods before PowerShell to reflect the prevalence of Linux/macOS in IoT and cloud development.
- Clarify that all methods (PowerShell, Bash, OpenSSL) are equally supported and available on their respective platforms.
- Explicitly mention platform compatibility for each script/tool (e.g., 'PowerShell (Windows), Bash (Linux/macOS)').
- Provide links or instructions for installing Bash/OpenSSL on Windows, and PowerShell on Linux/macOS, if relevant.
- Ensure parity in example depth and troubleshooting for both Windows and Linux/macOS users.
IoT Hub
Overview of Azure IoT Hub message enrichments
...ticles/iot-hub/iot-hub-message-enrichments-overview.md
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation lists Azure PowerShell as a configuration method alongside Azure CLI and Portal, but does not mention Linux/macOS-specific tools or clarify cross-platform parity. PowerShell is a Windows-centric tool, and its mention before any Linux-specific alternatives (such as Bash scripts or REST API usage) may suggest a Windows-first approach. However, Azure CLI is cross-platform, and no examples are given that are exclusive to Windows or PowerShell.
Recommendations
- Explicitly state that Azure CLI is cross-platform and supported on Linux/macOS.
- Provide REST API or SDK examples for configuring enrichments, which are platform-neutral.
- Clarify that PowerShell is available on Linux/macOS, or provide Bash script examples for parity.
- Ensure that any command-line examples are shown for both Azure CLI and PowerShell, with CLI (Linux-friendly) examples shown first.
Low Priority
View Details â
Detected Bias Types
missing_linux_example
windows_first
Summary
The documentation does not provide any OS-specific examples, but all references to connecting to virtual machines via port forwarding implicitly assume RDP or similar Windows-centric scenarios. There is no mention of Linux tools (e.g., SSH) or Linux/macOS workflows, and all tutorials and screenshots focus on the Azure portal, which is platform-neutral but omits command-line or OS-specific guidance. The lack of explicit Linux/macOS parity is a subtle bias.
Recommendations
- Add explicit examples for connecting to Linux VMs using SSH, including port mapping scenarios.
- Include references to Linux/macOS command-line tools and workflows (e.g., using SSH with custom ports).
- Ensure tutorials mention both RDP (Windows) and SSH (Linux/macOS) use cases.
- Add screenshots or CLI examples for both Windows and Linux/macOS environments.
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page is largely platform-neutral, focusing on Azure NAT Gateway concepts and configuration. However, there is a notable Windows bias in the 'Default outbound access' section, where only Windows-specific services (Windows Activation and Windows Updates) are mentioned as requiring outbound connectivity. Additionally, upgrade instructions for basic resources reference PowerShell (a Windows-centric tool) first, with no mention of Linux/macOS alternatives (e.g., Azure CLI, Bash). No Linux/macOS-specific examples, tools, or considerations are provided.
Recommendations
- Include Linux/macOS-specific outbound connectivity requirements (e.g., package updates, activation for Linux VMs) alongside Windows examples.
- Provide upgrade instructions using cross-platform tools such as Azure CLI or Bash scripts, not just PowerShell.
- Explicitly mention that NAT Gateway supports outbound connectivity for all VM OS types, and clarify any OS-specific caveats.
- Where PowerShell is referenced, add equivalent Azure CLI or REST API documentation links/examples.
Reliability
Reliability Guides for Azure Services
.../articles/reliability/overview-reliability-guidance.md
Low Priority
View Details â
Detected Bias Types
windows_tools
Summary
The documentation page is a service index listing reliability guides for Azure services. While the page itself is largely platform-neutral, there is one instance where a Windows-specific tool (Azure PowerShell) is mentioned for deploying Azure Firewall with availability zones. No Linux/macOS equivalents or cross-platform CLI options are referenced in this context.
Recommendations
- Where PowerShell is mentioned (e.g., 'Deploy Azure Firewall with availability zones by using Azure PowerShell'), add or link to equivalent instructions using Azure CLI, which is cross-platform.
- Ensure that any future examples or tool references include both Windows and Linux/macOS options, or use platform-neutral tools like Azure CLI.
- Consider reviewing linked reliability guides for similar biases, as this index may inherit bias from those documents.
Resource Mover
Move Azure VMs across regions with Azure Resource Mover
...esource-mover/tutorial-move-region-virtual-machines.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Windows and Linux prerequisites, but Windows is mentioned first in the VM preparation section. No command-line examples (PowerShell, Bash, CLI) are given, and the tutorial is entirely portal-based, so there are no Windows-only tools or examples. The only minor bias is listing Windows before Linux when discussing certificate updates.
Recommendations
- List Linux and Windows instructions in parallel or alternate order to avoid implicit prioritization.
- Explicitly state that the portal-based workflow is OS-agnostic and does not require Windows-specific tools.
- If command-line alternatives are added in the future, ensure both PowerShell and Bash/Azure CLI examples are provided.
Reliability
Reliability in Azure Managed Redis
...main/articles/reliability/reliability-managed-redis.md
Low Priority
View Details â
Detected Bias Types
missing_linux_example
Summary
The documentation page does not provide any OS-specific examples or instructions, but in the 'Backup and restore' section, it mentions that automation for import/export can be implemented using Azure CLI or Azure PowerShell. However, it does not clarify that Azure CLI is cross-platform and that Azure PowerShell is available on Linux/macOS, nor does it provide Linux/macOS-specific command examples or shell scripts. No explicit Windows tools or PowerShell-heavy bias is present, but the lack of Linux/macOS parity in examples is a minor omission.
Recommendations
- Clarify that Azure CLI is cross-platform and can be used on Linux/macOS as well as Windows.
- Provide example commands for both Azure CLI (bash/zsh) and Azure PowerShell, and note their platform compatibility.
- If automation scripts are referenced, include sample bash scripts for Linux/macOS users.
- Explicitly mention that Azure PowerShell is available on Linux/macOS, or link to installation instructions for non-Windows platforms.
Resource Mover
Move Azure VMs to availability zones in another region with Azure Resource Mover
...ticles/resource-mover/move-region-availability-zone.md
Low Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page generally maintains parity between Windows and Linux, but there is a subtle Windows bias. In the 'Check VM requirements' section, Windows is mentioned first when verifying supported VMs and when discussing certificate updates. For Windows, explicit instructions are given ('install the latest Windows updates'), while for Linux, users are told to 'follow the Linux distributor guidance' without further detail or example. No command-line examples (PowerShell, Bash, CLI) are present, so there is no overt tooling bias, but Windows is consistently referenced before Linux.
Recommendations
- Provide explicit Linux guidance or examples for updating certificates and CRLs, similar to the Windows instructions.
- Alternate the order of Windows and Linux references to avoid always listing Windows first.
- Where possible, link to or include Linux-specific documentation or commands for common tasks.
- Ensure that any future command-line examples include both PowerShell and Bash/Azure CLI equivalents.
Resource Mover
Support matrix for moving Azure VMs to another region with Azure Resource Mover
.../resource-mover/support-matrix-move-region-azure-vm.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation presents Windows VM support before Linux VM support, listing Windows operating systems and requirements first. However, both Windows and Linux platforms are covered in detail, with no exclusive Windows tools, examples, or instructions that would prevent Linux users from completing the task. There are no PowerShell-heavy sections, Windows-only patterns, or missing Linux examples.
Recommendations
- Reorder sections to present Windows and Linux support in parallel or alternate order, or combine into a single 'Supported Operating Systems' table to avoid implicit prioritization.
- Explicitly mention that instructions and requirements apply equally to both Windows and Linux unless otherwise stated.
- Ensure parity in notes and troubleshooting guidance for both platforms (e.g., password reset instructions for Linux are present, but check for similar parity in other areas).
Role Based Access Control
Azure built-in roles - Azure RBAC
...n/articles/role-based-access-control/built-in-roles.md
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page lists Azure built-in roles for RBAC in a platform-neutral manner, but there is mild evidence of Windows bias. Several roles and descriptions reference Windows-specific technologies (e.g., Windows 365, Windows Admin Center, NTFS permissions, SMB, Windows file servers) without mentioning Linux/macOS equivalents. Windows-related roles are present in the Compute and Storage sections, and Windows terminology appears in role names and descriptions. However, there are also roles for Linux/OSS technologies (e.g., Azure Red Hat OpenShift, Kubernetes), and the page does not provide usage examples or command-line instructions that would favor Windows or PowerShell.
Recommendations
- Where Windows-specific roles or terminology are used (e.g., NTFS, SMB, Windows Admin Center), add clarifying notes about Linux/macOS equivalents or alternatives, if available.
- Ensure parity by referencing Linux file permissions (e.g., POSIX ACLs) where relevant, especially in Storage roles.
- Consider adding links or references to documentation about managing Azure resources from Linux/macOS environments (e.g., Azure CLI, Bash, SSH).
- If roles are Windows-only, explicitly state their platform limitations.
- Review role descriptions for implicit assumptions about Windows environments and clarify cross-platform applicability.
Security
Azure encryption overview | Microsoft Docs
.../articles/security/fundamentals/encryption-overview.md
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates mild Windows bias, particularly in the section on SMB encryption, which exclusively references Windows versions and tools. There are no explicit Linux or macOS examples or mentions for SMB access, nor are cross-platform command-line examples provided for encryption tasks. The order of presentation also tends to mention Windows technologies first when discussing SMB and VPN protocols.
Recommendations
- Include references to Linux and macOS clients for SMB access, such as using smbclient or mounting Azure Files via CIFS on Linux.
- Provide cross-platform examples for encryption-related tasks, including command-line snippets for Linux (e.g., using OpenSSL, curl, or Azure CLI on bash).
- Mention Linux support for VPN protocols (IPsec, SSTP, OpenVPN) and provide links to relevant Azure documentation for non-Windows platforms.
- When listing supported platforms or tools, present them in a neutral or alphabetical order, and avoid Windows-first phrasing.
- Add notes or links to platform-specific guides for macOS and Linux users where relevant.
Site Recovery
Azure Virtual Machines disaster recovery - High Churn support
...recovery/concepts-azure-to-azure-high-churn-support.md
Low Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation mentions supported operating systems for Enhanced Churn (Windows, then Linux distros), but does not provide any OS-specific examples, commands, or guidance. There is a subtle 'Windows first' bias in the support matrix, listing Windows before Linux and not specifying Linux versions for the standard High Churn (only for Enhanced Churn preview). No PowerShell or Windows tool bias is present, but Linux parity could be improved by clarifying supported Linux versions and providing OS-specific troubleshooting or configuration notes.
Recommendations
- Explicitly list supported Linux distributions and versions for all churn support levels, not just Enhanced Churn preview.
- Provide OS-specific guidance or troubleshooting steps for both Windows and Linux VMs, especially if there are differences in agent installation, configuration, or performance.
- Ensure examples and screenshots are applicable to both Windows and Linux VMs, or clarify when steps differ.
- Avoid listing Windows before Linux in support matrices unless there is a technical reason.
Sentinel
The Advanced Security Information Model (ASIM) Network Session normalization schema reference | Microsoft Docs
...main/articles/sentinel/normalization-schema-network.md
Low Priority
View Details â
Detected Bias Types
windows_examples
windows_terms
windows_first
Summary
The documentation page is generally cross-platform and vendor-neutral, but there is a mild Windows bias in examples and terminology. Several example values use Windows-specific paths (e.g., C:\Windows\explorer.exe), hostnames (e.g., DESKTOP-1282V4D), and domain formats (domain\hostname). Windows terms are sometimes mentioned before Linux equivalents, and Windows-style examples are more prevalent than Linux/macOS ones. No critical functionality is locked to Windows, and Linux is referenced in some places (e.g., process ID type guidance), but Linux/macOS users may find the examples less relatable.
Recommendations
- Add Linux/macOS equivalent examples alongside Windows ones (e.g., /usr/bin/sshd, linux-host1).
- Clarify that fields like process names, hostnames, and domain formats are platform-agnostic and provide examples for multiple OSes.
- When describing formats (e.g., FQDN), mention both Windows and Linux conventions equally.
- Avoid using Windows paths and hostnames exclusively in examples; rotate or pair with Linux/macOS samples.
- Explicitly state cross-platform applicability where relevant.