211
Pages Scanned
62
Pages Flagged
211
Changed Pages
29.4%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:08
Scan Information
Started At: 2026-01-23 00:00:08
Finished At: 2026-01-23 18:07:07
Status: failed
Target Repo: Azure
Current Phase: discovery
Files Queued: 211
Files Completed: 211
Problematic Pages
62 issues found
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
Summary
The documentation page for managing certificates in Azure Automation is heavily focused on PowerShell cmdlets and Windows-centric tooling. Most examples and workflows use PowerShell, with only secondary mention of Python. There is no explicit guidance or examples for Linux/macOS users, such as using Azure CLI, Bash, or platform-agnostic certificate management approaches. The reliance on PowerShell and references to Windows cryptographic providers may create friction for non-Windows users.
Recommendations
- Add equivalent examples using Azure CLI and/or REST API for certificate management tasks.
- Clarify whether PowerShell cmdlets can be run cross-platform (e.g., via PowerShell Core on Linux/macOS), and provide instructions if so.
- Include notes or examples for uploading certificates from Linux/macOS systems, including how to prepare .pfx/.cer files and any platform-specific caveats.
- Mention alternative cryptographic providers if supported, or clarify Windows-only requirements.
- Ensure that Python examples cover both certificate creation and retrieval, not just access.
Create Pull Request
Application Gateway
Scaling and Zone-redundant Application Gateway v2
...eway/application-gateway-autoscaling-zone-redundant.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page provides a link to a tutorial for creating an autoscaling, zone redundant application gateway using Azure PowerShell, without mentioning or linking to equivalent instructions for Linux/macOS users (e.g., Azure CLI, ARM templates, or Bicep). This suggests a bias toward Windows/PowerShell tooling, potentially creating friction for users on other platforms.
Recommendations
- Add links or references to equivalent tutorials using Azure CLI, ARM templates, or Bicep, which are cross-platform and commonly used on Linux/macOS.
- Where PowerShell is mentioned, clarify that Azure CLI or other tools can also be used, and provide examples or links.
- Ensure that step-by-step guides for key tasks (such as creating an autoscaling, zone redundant application gateway) are available for both PowerShell and CLI/ARM/Bicep.
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page for Application Gateway V1 retirement and migration to V2 demonstrates a notable Windows bias. Migration instructions and tooling are centered around Azure PowerShell scripts, with no mention of Azure CLI or Bash alternatives. All automation and example references are PowerShell-specific, and there are no Linux/macOS-friendly migration workflows or sample commands provided.
Recommendations
- Provide equivalent Azure CLI (az) commands and scripts for migration tasks, especially for configuration and public IP retention.
- Include Bash or shell script examples for common migration scenarios.
- Clearly state platform requirements for provided scripts, and offer guidance for Linux/macOS users.
- Reference cross-platform tooling where possible, and clarify any limitations or differences in migration workflows for non-Windows environments.
Azure Netapp Files
Create volume replication for Azure NetApp Files
...etapp-files/cross-region-replication-create-peering.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page provides Azure PowerShell examples first and in detail for feature registration, with only a brief mention of Azure CLI as an alternative. The primary step-by-step instructions use PowerShell syntax, which is most familiar to Windows users. There are no explicit Linux/macOS command-line examples or screenshots, and the CLI alternative is not shown directly in the workflow.
Recommendations
- Provide explicit Azure CLI command examples alongside PowerShell, especially for feature registration and status checking.
- Include screenshots or instructions that clarify CLI usage on Linux/macOS platforms.
- Where possible, order examples so that CLI and PowerShell are presented equally, or clarify platform neutrality.
- Add notes or links for Linux/macOS users on how to install and use Azure CLI for these tasks.
Backup
Restore VMs by using the Azure portal using Azure Backup
...b/main/articles/backup/backup-azure-arm-restore-vms.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides several examples and guidance using PowerShell and references to Windows-specific documentation (e.g., restoring VMs with custom images, availability sets, and network configurations). Windows/PowerShell patterns are mentioned before or instead of Linux/CLI alternatives, and links for further steps often point to Windows-centric pages. There are few, if any, explicit Linux or Azure CLI examples for VM restore operations, and Linux-specific considerations are limited to brief notes (e.g., cloud-init password reset).
Recommendations
- Add Azure CLI examples for restoring VMs and disks, especially in sections currently referencing PowerShell.
- Include links to Linux-specific documentation for tasks like attaching disks, creating VMs from disks, and configuring networking.
- Where guidance references Windows tutorials (e.g., custom images, availability sets), provide equivalent Linux documentation links.
- Expand post-restore steps for Linux VMs, such as troubleshooting SSH access, agent installation, and domain rejoin procedures.
- Ensure that examples and screenshots are not exclusively Windows-focused, and clarify when steps apply equally to Linux VMs.
Logic Apps
Why move from BizTalk Server to Azure Logic Apps?
...ticles/logic-apps/biztalk-server-migration-overview.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
powershell_heavy
windows_first
Summary
The documentation page provides a comprehensive comparison between BizTalk Server (a Windows-only product) and Azure Logic Apps. While the page is not about a Windows-only Azure feature, it does exhibit some Windows bias: Windows tools (MMC, PowerShell, Windows registry) are referenced as primary management and configuration methods for BizTalk Server, and deployment/operations examples often mention PowerShell before Bash or CLI. Windows-centric patterns (e.g., GAC, registry, MMC) are described in detail, with limited Linux/macOS alternatives or parity notes. However, Azure Logic Apps and related Azure services are presented as cross-platform and cloud-native, with developer experiences and hosting options for both Windows and Linux. The bias is moderate, mainly because BizTalk Server is inherently Windows-only, but Linux/macOS users seeking migration guidance may find some friction due to the Windows-centric framing.
Recommendations
- When describing deployment, management, or configuration patterns for BizTalk Server, explicitly note that these are Windows-only and suggest Azure-native or cross-platform alternatives for Azure Logic Apps.
- In sections referencing PowerShell, MMC, or Windows registry, add notes or links to Bash/CLI equivalents for Azure Logic Apps and related Azure services.
- Where developer experiences are listed, clarify which tools are cross-platform (e.g., Visual Studio Code, Azure CLI) and which are Windows-only.
- In migration guidance, highlight how Azure Logic Apps and related services support Linux/macOS environments, and provide links to relevant documentation for those platforms.
- Consider reordering examples so that Azure Logic Apps (cross-platform) is described first in relevant sections, or at least in parity with BizTalk Server.
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 instructions for managing a Standard V2 NAT Gateway using the Azure portal and Azure PowerShell, but does not include any examples or guidance for Linux/macOS users via Azure CLI or other cross-platform tools. All command-line examples are exclusively PowerShell-based, which may create friction for users on non-Windows platforms.
Recommendations
- Add equivalent Azure CLI examples for all tasks (create, associate, remove, add/remove IPs/prefixes) alongside PowerShell instructions.
- Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
- Where PowerShell modules are referenced, provide Azure CLI command references and links.
- Consider reordering or parallelizing example tabs so that Azure CLI is presented before or alongside PowerShell, not only after portal instructions.
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Windows and Linux guidance for upgrading TLS, but Windows instructions and PowerShell cmdlets are consistently mentioned first and more prominently. Several backup and data management procedures reference only Windows PowerShell cmdlets, with no equivalent CLI or Linux-native commands provided. This creates friction for Linux/macOS users, who must infer or research their own solutions.
Recommendations
- When listing platform-specific instructions, alternate the order or present Linux and Windows guidance in parallel sections.
- For backup/export tasks (runbooks, DSC configurations), provide Azure CLI or REST API examples alongside PowerShell cmdlets, or explicitly state if only PowerShell is supported.
- Where possible, include Linux/macOS-compatible commands or scripts for asset management and data export.
- Clarify if certain features (like asset export) are not available on Linux, and suggest alternative approaches for non-Windows users.
Application Gateway
Migrate from V1 to V2 - Azure Application Gateway
...lob/main/articles/application-gateway/migrate-v1-v2.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation is heavily focused on Azure PowerShell scripts and cmdlets for migration, with all examples and instructions using PowerShell syntax. There are no CLI (az), Bash, or Linux/macOS-specific examples or guidance. The installation and usage instructions assume a PowerShell environment, which is native to Windows but only optionally available on Linux/macOS. This creates friction for users on non-Windows platforms who may prefer or require Bash/CLI workflows.
Recommendations
- Provide equivalent Azure CLI (az) commands and scripts for migration tasks, or clarify if PowerShell is strictly required.
- Include instructions for running PowerShell scripts on Linux/macOS (e.g., via PowerShell Core), and note any platform-specific caveats.
- Add Bash or shell script examples where possible, especially for certificate handling and file operations.
- Explicitly state platform requirements and alternatives at the start of the documentation.
- Consider linking to cross-platform migration tools or community scripts if official support is limited.
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_first
missing_linux_example
Summary
The documentation page for Azure Application Gateway v2 shows a notable Windows/PowerShell bias. Migration guidance and preview registration/unregistration steps are provided only as Azure PowerShell commands, with no equivalent Azure CLI (bash) or ARM template examples. The main tutorial linked is PowerShell-based, and PowerShell is referenced before any cross-platform alternatives. This creates friction for Linux/macOS users who may prefer or require bash/CLI workflows.
Recommendations
- Provide Azure CLI (bash) equivalents for all PowerShell commands, especially for migration and preview registration/unregistration steps.
- Link to or create tutorials using Azure CLI and ARM templates, not just PowerShell.
- When listing command-line instructions, present cross-platform (CLI) examples before or alongside PowerShell examples.
- Clarify that PowerShell commands can be run on Linux/macOS, but highlight CLI alternatives for users who do not use PowerShell.
Application Gateway
Tutorial: Improve web application access - Azure Application Gateway
.../articles/application-gateway/tutorial-autoscale-ps.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The tutorial is heavily focused on Azure PowerShell and Windows-specific tooling, such as the use of PowerShell cmdlets and Windows certificate management commands. No equivalent Bash, Azure CLI, or Linux/macOS instructions are provided, and Windows tools (e.g., New-SelfSignedCertificate, Export-PfxCertificate) are used for certificate creation and export. This creates friction for Linux/macOS users, who must find alternative methods to complete key steps.
Recommendations
- Provide Azure CLI equivalents for all Azure resource creation and management steps.
- Include instructions for creating self-signed certificates on Linux/macOS (e.g., using OpenSSL) and exporting to PFX format.
- Add notes or links to cross-platform tools and methods where PowerShell or Windows-specific commands are used.
- Consider reordering or parallelizing examples so that Linux/macOS methods are presented alongside Windows/PowerShell approaches.
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_first
Summary
The documentation for disaster recovery in Azure Automation is heavily focused on PowerShell scripts and workflows for asset migration, with no mention of Bash, Python, or cross-platform alternatives. While the page states applicability to both Linux and Windows VMs, all migration examples and tooling are PowerShell-centric, and instructions reference Windows tabs and runtime versions first. There are no Linux/macOS-specific examples or guidance for users who prefer or require non-Windows tooling.
Recommendations
- Provide equivalent Bash or Python scripts for asset migration, or clarify if PowerShell Core (cross-platform) is supported and provide instructions for Linux/macOS environments.
- Add explicit instructions or examples for running migration scripts on Linux/macOS, including prerequisites and installation steps for PowerShell Core.
- Reorder or balance examples so that Linux and Windows instructions are presented equally, or in parallel tabs.
- Clarify any platform limitations (e.g., if only PowerShell is supported, state that PowerShell Core is required and provide installation guidance for Linux/macOS users).
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 tooling, with all examples and instructions using PowerShell modules and cmdlets. There are no examples or guidance for Linux/macOS users, such as using Azure CLI, Bash, or Python SDKs. The term 'Windows PowerShell' is used explicitly, and no cross-platform alternatives are mentioned, which may create friction for non-Windows users.
Recommendations
- Add equivalent examples using Azure CLI (az) commands for credential management and authentication, which are cross-platform.
- Clarify that PowerShell Core (pwsh) is supported on Linux/macOS and provide examples or notes for running scripts on these platforms.
- Mention and provide examples for using the Azure SDK for Python or other languages to authenticate with Microsoft Entra ID in Azure Automation.
- Where 'Windows PowerShell' is referenced, clarify if the steps also apply to PowerShell Core, and if not, provide alternatives.
- Include a section or callout for Linux/macOS users outlining supported approaches and any limitations.
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
missing_linux_example
windows_tools
Summary
The documentation page is heavily focused on PowerShell and Windows-centric tools and patterns. Most examples, code snippets, and workflows use PowerShell, PowerShell Workflow, or graphical runbooks (which are PowerShell-based). The process of passing parameters, especially with JSON objects, is demonstrated exclusively with PowerShell and Windows-oriented cmdlets. There is minimal coverage of Python runbooks, and no examples or guidance for Linux/macOS users on how to interact with Azure Automation runbooks using native Linux tools or shell scripts. The SDK and REST API sections are platform-neutral, but the practical examples and step-by-step instructions are Windows/PowerShell-centric.
Recommendations
- Add equivalent examples for starting and passing parameters to runbooks using Bash, Azure CLI, or other Linux-native tools.
- Provide Python runbook parameter examples that show how to invoke them from Linux/macOS environments, including sample Bash scripts.
- Clarify which steps are platform-agnostic (e.g., REST API, SDK) and provide explicit Linux/macOS usage instructions where possible.
- Include notes or sections on how Linux/macOS users can install and use Azure CLI to interact with Azure Automation.
- Balance the order of examples so that PowerShell and Linux-native approaches are presented with equal prominence.
Automation
Manage credentials in Azure Automation
...in/articles/automation/shared-resources/credentials.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation for managing credentials in Azure Automation is heavily focused on PowerShell and Windows-centric tooling. All CLI examples are in PowerShell, and references to creating credentials outside the portal are exclusively via Windows PowerShell. There is no mention of Linux/macOS shell equivalents (such as Azure CLI or Bash), nor are there examples for non-Windows environments. Python is covered for runbooks, but only as an alternative scripting language, not for credential management or asset creation from Linux/macOS shells.
Recommendations
- Add Azure CLI examples for credential asset management, demonstrating how to create, retrieve, and delete credentials from Linux/macOS terminals.
- Clarify whether credential asset management is possible via Azure CLI or REST API, and provide links or examples if so.
- Explicitly state any limitations or platform dependencies for credential management, so Linux/macOS users know what is and isn't possible.
- Reorder sections so that platform-neutral or cross-platform methods (e.g., Azure portal, REST API, Azure CLI) are presented before Windows PowerShell.
- Include notes or guidance for Linux/macOS users on how to interact with Azure Automation credentials, especially for asset creation and retrieval outside of runbooks.
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 generally covers both Windows and Linux scenarios for running C# Azure Functions in an isolated worker process, but there are several instances of Windows bias. Windows-specific tools (Visual Studio, PowerShell) are mentioned before Linux alternatives, and Windows examples (such as CLI commands and project configuration) often appear first. Some deployment and configuration instructions provide more detail for Windows than Linux, and PowerShell is referenced as a primary automation tool. Linux equivalents are present but sometimes less emphasized or described after Windows options.
Recommendations
- Ensure Linux and macOS instructions/examples are presented alongside or before Windows equivalents, especially in sections about deployment, configuration, and debugging.
- Provide parity in detail for Linux/macOS tooling (e.g., Azure CLI, bash scripts) where PowerShell or Visual Studio is referenced.
- Add explicit Linux/macOS examples for all CLI commands, especially for deployment, configuration, and debugging steps.
- Where possible, use cross-platform tools (Azure CLI, VS Code) as primary examples, or clearly indicate platform-specific steps.
- Review and update sections where Windows tools or patterns are mentioned exclusively or first, to ensure Linux/macOS users have equal guidance.
Azure Functions
host.json reference for Azure Functions 2.x
...b/main/articles/azure-functions/functions-host-json.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation is generally cross-platform, but there are a few areas of Windows bias. The 'managedDependency' feature is described as PowerShell-only, which is a Windows-centric technology, and references to 'requirements.psd1' are PowerShell-specific. Some settings (e.g., 'tempFolder' in snapshot configuration) mention Windows environment variables (e.g., %TEMP%) and folders like LOCALAPPDATA and APPDATA before Linux equivalents. The documentation also references Kudu performance counters, which are more relevant to Windows environments. Examples and explanations sometimes mention Windows paths or conventions first, with Linux details appearing only as notes or secondary explanations.
Recommendations
- Clarify managedDependency support for non-Windows platforms or provide equivalent guidance for other languages/runtimes.
- When referencing environment variables or folders (e.g., tempFolder), explicitly mention Linux/macOS equivalents (such as $TMPDIR or /tmp) alongside Windows variables.
- If features like Kudu performance counters are Windows-specific, note their platform limitations and suggest alternatives for Linux/macOS users.
- Ensure examples and explanations are presented in a platform-neutral way, or provide parallel examples for Linux/macOS where relevant.
Azure Netapp Files
Azure NetApp Files for Azure Government
...b/main/articles/azure-netapp-files/azure-government.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides access instructions for Azure NetApp Files in Azure Government via the portal, Azure CLI, REST API, and PowerShell. While the CLI and REST API sections are platform-neutral, the PowerShell section is detailed and prominent, and PowerShell is a Windows-centric tool. Additionally, PowerShell instructions are given more space and detail than Linux-native alternatives (such as Bash or scripting with curl for REST API access). There are no Linux/macOS-specific examples or references to Linux-native tools for connecting to Azure Government.
Recommendations
- Add explicit Linux/macOS instructions for connecting to Azure Government, such as using Bash scripts with Azure CLI.
- Include examples using curl or other Linux-native tools for REST API access.
- Clarify that PowerShell Core is cross-platform, or provide alternative instructions for Linux/macOS users where appropriate.
- Ensure parity in example depth and detail for both Windows and Linux/macOS users.
Azure Resource Manager
Relocate an Azure Container Registry to another region
...management/relocation/relocation-container-registry.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page for relocating an Azure Container Registry exhibits several Windows biases. PowerShell commands (e.g., Get-AzContainerRegistryRepository, Import-AzContainerImage, Set-AzAksCluster) are presented without equivalent Bash/Azure CLI examples, and in some cases, PowerShell commands are shown before or instead of CLI commands. There is a lack of explicit Linux/macOS shell examples for key steps, such as enumerating repositories and integrating with AKS, which may create friction for non-Windows users.
Recommendations
- Provide Azure CLI/Bash equivalents for all PowerShell commands, especially for repository enumeration, image import, and AKS integration.
- When listing commands, present Azure CLI (cross-platform) examples first, followed by PowerShell alternatives.
- Explicitly note when commands are platform-specific, and link to documentation for both Windows and Linux/macOS users.
- Add a section or callouts for Linux/macOS users, clarifying any differences in workflow or tooling.
Azure Resource Manager
Relocation guidance for Azure Firewall
...e-manager/management/relocation/relocation-firewall.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation provides step-by-step instructions for relocating Azure Firewall using the Azure Portal and PowerShell, but does not include examples or guidance for Linux/macOS users who may prefer Azure CLI or Bash. All command-line examples use PowerShell, and references to scripting or automation are exclusively PowerShell-based. There is no mention of Azure CLI, Bash, or cross-platform alternatives, which may create friction for non-Windows users.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell commands, ensuring Linux/macOS users can follow along without needing PowerShell.
- Explicitly mention that both PowerShell and Azure CLI can be used for ARM template export, modification, and deployment, and link to Azure CLI documentation.
- Where automation is referenced, clarify cross-platform options and provide Bash script samples if appropriate.
- Consider reordering or parallelizing instructions so that Azure Portal, PowerShell, and Azure CLI/Bash options are presented equally.
Backup
About the Azure Virtual Machine restore process
...cs/blob/main/articles/backup/about-azure-vm-restore.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page describes the Azure VM restore process in a generally platform-neutral way, but there is notable bias in the 'Restore an encrypted VM' scenario. This section exclusively references restoring encrypted Windows VMs and instructs users to use PowerShell to create the VM after restoring disks. There are no equivalent instructions or references for restoring encrypted Linux VMs, nor are Linux command-line tools (such as Azure CLI or Bash) mentioned. The restore scenarios table also lists Windows-specific links for encrypted VM restore, with no Linux parity.
Recommendations
- Add instructions and examples for restoring encrypted Linux VMs, including any required steps and supported scenarios.
- Include Azure CLI or Bash examples alongside PowerShell for VM creation after disk restore, where applicable.
- Clarify in the encrypted VM restore section whether Linux VMs are supported, and if not, explicitly state this limitation.
- Ensure restore scenarios table covers both Windows and Linux VM restore processes, or clearly delineates platform-specific steps.
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page for Azure Backup architecture demonstrates a notable Windows bias in its coverage of on-premises backup scenarios. It exclusively describes backup methods and agents (MARS, DPM, MABS) that only support Windows machines, with explicit statements that Linux machines aren't supported for direct backup. There are no Linux-specific backup examples, agents, or equivalent tooling mentioned for on-premises Linux systems. The documentation also presents Windows backup tools and workflows first and in detail, while Linux is only referenced to note its lack of support.
Recommendations
- Clearly state at the beginning which backup scenarios are Windows-only and provide links or references to Azure-supported backup solutions for Linux (e.g., Azure Backup for Linux VMs, third-party solutions, or Azure Files/Blob backup).
- Add a dedicated section or callout summarizing Linux backup options in Azure, including supported scenarios and limitations.
- Where possible, provide parity in examples and workflows for Linux VMs (e.g., how Azure Backup works for Linux VMs, supported features, and any differences).
- If on-premises Linux backup is not supported, explicitly mention alternative approaches or recommended practices for Linux environments.
Backup
Back Up and Restore Encrypted Azure VMs
...ob/main/articles/backup/backup-azure-vms-encryption.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation is generally cross-platform and covers both Windows and Linux Azure VMs with encrypted disks. However, there is a notable bias in the 'Provide permissions' section, where only a PowerShell example is given for identifying a VM's associated Key Vault, with no equivalent Azure CLI or Bash example for Linux/macOS users. Additionally, PowerShell is mentioned first in the automation context, and screenshots and instructions are primarily portal-based, which is neutral but could be improved with more CLI parity.
Recommendations
- Add Azure CLI and Bash examples alongside PowerShell commands, especially for tasks like identifying the Key Vault associated with a VM.
- Where automation is referenced, provide both PowerShell and Azure CLI links/examples, and mention them equally.
- Ensure that any code snippets or command-line instructions are available for both Windows and Linux/macOS environments.
- Explicitly state that all steps can be performed from Linux/macOS using Azure CLI where applicable.
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation covers restoring encrypted Azure VMs for both Windows and Linux, but exhibits some Windows bias. PowerShell is mentioned as the primary automation method for recreating VMs from restored disks, with no equivalent CLI or Linux-native example provided. The OS disk swap note links only to Windows instructions, and Linux restore steps are brief and lack detailed guidance or examples. Windows-related actions and tools are mentioned first or exclusively in some sections.
Recommendations
- Provide Azure CLI and/or Bash examples for creating a VM from restored disks, alongside PowerShell.
- Include a link or section for swapping OS disks on Linux VMs, not just Windows.
- Expand the Linux restore section with step-by-step instructions and example commands for reinstalling the ADE extension and mounting disks.
- Ensure parity in troubleshooting and next steps for both Windows and Linux VM scenarios.
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
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation provides comprehensive coverage for both Windows and Linux Azure VM backup scenarios, but there are notable signs of Windows bias. Windows-specific tools (MARS agent, DPM, MABS) are referenced and supported, while their use for Linux is explicitly marked as unsupported. Restore examples and instructions frequently mention PowerShell and Windows-centric workflows, with Linux alternatives rarely described in detail. Windows scenarios and tools are often listed first, and some restore methods (e.g., file-level restore, disk replacement) reference Windows patterns or tools without Linux-specific guidance. Linux support is present, but less detailed and with more unsupported features.
Recommendations
- Provide Linux CLI (az, bash) examples alongside PowerShell for restore and backup operations.
- Include more detailed Linux-specific workflows for restore scenarios, especially for file-level restore and disk replacement.
- Clarify Linux limitations and offer workarounds or alternatives where possible.
- Balance the order of presentation so that Linux and Windows are treated equally in tables and lists.
- Reference Linux-native backup tools or scripts where relevant, or explain why they are not supported.
Cloud Services Extended Support
About Azure Cloud Services (extended support)
...n/articles/cloud-services-extended-support/overview.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation mentions Windows-centric tools (PowerShell, Visual Studio) as primary deployment options, and lists them before cross-platform alternatives like ARM templates and the Azure Portal. There are no explicit Linux/macOS examples or CLI references, which may create friction for non-Windows users.
Recommendations
- Include Azure CLI examples for deployment, as it is cross-platform and widely used on Linux/macOS.
- List cross-platform options (ARM templates, Azure Portal, Azure CLI) before Windows-specific tools (PowerShell, Visual Studio) when describing deployment methods.
- Clarify which deployment tools are available on which platforms, and provide links to relevant documentation for Linux/macOS users.
- Add explicit Linux/macOS guidance or examples where possible, especially in sections about scripting or automation.
Data Share
Tutorial: Share outside your org - Azure Data Share
...-docs/blob/main/articles/data-share/share-your-data.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides parallel examples for Azure Portal, Azure CLI, and PowerShell. However, the PowerShell examples and instructions are notably more detailed, and some file upload examples use Windows-style paths (e.g., D:\testFiles\textfile.csv) without Linux/macOS equivalents. There is no explicit mention of Linux/macOS-specific instructions or examples, especially for file uploads and local environment setup. The Azure CLI examples are cross-platform, but PowerShell is Windows-centric and presented with more context and detail.
Recommendations
- Add explicit Linux/macOS file path examples (e.g., /home/user/testFiles/textfile.csv) alongside Windows paths in PowerShell and CLI sections.
- Clarify that PowerShell Core is available on Linux/macOS, and provide instructions for installing and running PowerShell on those platforms.
- Include Bash examples for file uploads to Azure Storage using az CLI or other cross-platform tools.
- Balance the detail level between PowerShell and Azure CLI sections to ensure parity for non-Windows users.
- Note any platform-specific limitations or differences where relevant.
Data Share
Tutorial: Accept & receive data - Azure Data Share
...ob/main/articles/data-share/subscribe-to-data-share.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides examples for Azure Portal, Azure CLI, and PowerShell. While Azure CLI is cross-platform, PowerShell examples are given equal prominence and detail, and some PowerShell commands reference Windows-specific file paths (e.g., D:\testFiles). There are no explicit Linux/macOS shell examples (e.g., Bash scripts for file upload), and PowerShell is presented as a primary automation option, which may create friction for Linux/macOS users. Additionally, in some sections, PowerShell instructions reference running commands locally or in Azure Cloud Shell, but do not clarify Linux usage or alternatives.
Recommendations
- Add explicit Bash or shell script examples for file operations, especially for uploading files to Azure Storage from Linux/macOS.
- Clarify that Azure CLI commands work equally on Windows, Linux, and macOS, and highlight any OS-specific considerations.
- Avoid Windows-specific file paths in examples (e.g., use generic paths or show both Windows and Linux/macOS variants).
- Where PowerShell is referenced, note that Azure Cloud Shell supports Bash and PowerShell, and provide Bash equivalents for common tasks.
- Consider reordering examples so that cross-platform options (Azure CLI, Bash) are presented before PowerShell.
DNS
Resolve Azure and on-premises domains.
.../blob/main/articles/dns/private-resolver-hybrid-dns.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides detailed instructions and screenshots for configuring DNS conditional forwarders using a Windows DNS server, but does not offer equivalent examples or guidance for Linux-based DNS servers (such as BIND or dnsmasq). PowerShell and portal quickstarts are listed before CLI options, and the only on-premises DNS configuration example is for Windows, potentially creating friction for Linux users.
Recommendations
- Add explicit instructions and examples for configuring conditional forwarders on popular Linux DNS servers (e.g., BIND, dnsmasq, Unbound).
- Include screenshots or configuration file snippets for Linux DNS server setups.
- List CLI-based quickstarts before or alongside PowerShell/portal options to avoid Windows-first ordering.
- Clarify that the procedures are applicable to both Windows and Linux DNS servers, and provide links to external resources for Linux DNS configuration if full instructions are out of scope.
Event Grid
Troubleshoot network connectivity issues - Azure Event Grid | Microsoft Docs
...ticles/event-grid/troubleshoot-network-connectivity.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation consistently presents Windows/PowerShell examples and tools (psping.exe, tcpping.exe) first and in more detail, with Linux alternatives (telnet) mentioned only briefly and lacking parity in explanation. The troubleshooting steps and sample commands are Windows-centric, which may create friction for Linux/macOS users seeking equivalent workflows.
Recommendations
- Provide Linux/macOS equivalents for all troubleshooting commands (e.g., use 'nc' or 'nmap' for port checks, 'hping3' or 'tcping' for TCP pinging).
- Present Linux/macOS examples alongside Windows/PowerShell examples, not only as a brief mention.
- Include installation instructions or links for Linux/macOS tools where Windows tools are referenced.
- Ensure tool recommendations are cross-platform (e.g., Wireshark is good, but also mention tcpdump for Linux).
- Reorder examples so that Windows and Linux/macOS commands are presented with equal prominence.
Event Hubs
Geo-disaster recovery - Azure Event Hubs| Microsoft Docs
...ocs/blob/main/articles/event-hubs/event-hubs-geo-dr.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides platform-specific instructions for manual failover using Azure portal, Azure CLI, PowerShell, and C#. While Azure CLI is cross-platform, PowerShell is Windows-centric and is listed before C# and after CLI. There are no explicit Linux/macOS shell examples (e.g., Bash), nor is there mention of Linux-specific tooling or patterns. The ordering of examples tends to favor Windows tools (PowerShell) and the Azure portal, which is most commonly accessed from Windows environments. No Linux/macOS-specific guidance or troubleshooting is provided.
Recommendations
- Add explicit Bash examples for manual failover using Azure CLI to demonstrate Linux/macOS usage.
- Clarify that Azure CLI commands work on Linux/macOS and provide sample shell scripts for automation.
- Reorder platform-specific sections so that cross-platform tools (CLI) are listed before Windows-centric ones (PowerShell).
- Include troubleshooting notes or tips for Linux/macOS users, if any platform-specific issues exist.
- Consider adding a short section or note confirming full parity of features and commands across Windows, Linux, and macOS.
Expressroute
About ExpressRoute virtual network gateways
...ssroute/expressroute-about-virtual-network-gateways.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
Summary
The documentation page for ExpressRoute virtual network gateways provides configuration examples and references primarily using Azure PowerShell, with no equivalent Azure CLI or Linux/macOS shell examples. The only code sample for subnet creation is PowerShell-specific, and the REST API/PowerShell section omits mention of Azure CLI, which is cross-platform. This creates friction for Linux and macOS users who are more likely to use Azure CLI or Bash.
Recommendations
- Add equivalent Azure CLI examples alongside PowerShell code samples for all configuration tasks, especially subnet creation.
- Include references and links to Azure CLI documentation in the REST API/PowerShell section.
- When listing tools or commands, present Azure CLI and PowerShell together, or list CLI first to emphasize cross-platform support.
- Clarify that all operations can be performed using Azure CLI on Linux/macOS, and provide guidance for non-Windows users.
Load Balancer
Outbound-only load balancer configuration
...e-docs/blob/main/articles/load-balancer/egress-only.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides step-by-step instructions for configuring an outbound-only load balancer in Azure, but all virtual machine creation and connectivity testing examples use Windows Server as the VM image and Microsoft Edge as the browser. There are no Linux VM creation examples, nor are there instructions for testing connectivity from a Linux VM (e.g., using curl or a Linux browser). This creates a bias toward Windows, making it less clear for Linux users how to follow the guide.
Recommendations
- Include parallel instructions for creating a Linux VM (e.g., Ubuntu) in the 'Create virtual machine' section, with appropriate admin account setup.
- Add connectivity testing steps for Linux VMs, such as using curl or wget from the command line to verify outbound connectivity (e.g., curl https://whatsmyip.org).
- Clarify that the configuration applies to both Windows and Linux VMs, and provide notes or links to Linux-specific guidance where relevant.
- When referencing browsers, mention alternatives available on Linux (e.g., Firefox, Chromium) or use command-line tools for parity.
Load Balancer
Tutorial: Create a public load balancer with an IP-based backend - Azure portal
...d-balancer/tutorial-load-balancer-ip-backend-portal.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
powershell_heavy
windows_tools
Summary
The documentation exclusively uses Windows Server VM images and Windows PowerShell commands for configuring IIS on backend VMs. There are no Linux VM options or Linux-based web server installation instructions, and Windows/PowerShell patterns are presented as the only approach. This creates friction for users wishing to deploy Linux-based backend pools.
Recommendations
- Provide parallel instructions for creating Linux VMs (e.g., Ubuntu) in the backend pool.
- Include Linux-based web server setup (e.g., Apache or Nginx) using Bash/SSH commands.
- Show both Windows and Linux examples for backend VM configuration and load balancer testing.
- Explicitly mention that backend pools can use Linux VMs and link to relevant Linux setup guides.
Load Balancer
Tutorial: Protect your public load balancer with Azure DDoS Protection
...s/load-balancer/tutorial-protect-load-balancer-ddos.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
powershell_heavy
windows_tools
Summary
The tutorial exclusively uses Windows Server VM images and provides only Windows PowerShell commands for installing and configuring IIS. There are no Linux VM options, nor are there Bash or Linux-native instructions for web server setup. The documentation assumes Windows as the default, which creates friction for users who prefer or require Linux-based solutions.
Recommendations
- Provide parallel instructions for creating Linux VMs (e.g., Ubuntu) in the 'Create virtual machines' section.
- Include Bash commands for installing and configuring a web server (such as Apache or Nginx) on Linux VMs.
- Offer users a choice between Windows and Linux VM images when demonstrating backend pool configuration.
- Clarify that IIS installation is for demonstration purposes and suggest Linux alternatives for cross-platform parity.
- Add notes or links to documentation for Linux-based load balancer backend scenarios.
Load Balancer
Move an Azure Load Balancer to another Azure region
...ad-balancer/move-across-regions-azure-load-balancer.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation provides detailed instructions for moving Azure Load Balancers using the Azure portal and Azure PowerShell, but does not include any examples or guidance for Linux/macOS command-line users. All CLI-based instructions use Azure PowerShell cmdlets, which are primarily Windows-centric, and reference Windows tools like notepad.exe for editing templates. There are no Azure CLI (az) examples, which are cross-platform and preferred by many Linux/macOS users.
Recommendations
- Add equivalent Azure CLI (az) command examples for all PowerShell steps, including exporting, editing, and deploying ARM templates.
- Replace or supplement references to Windows-specific tools (e.g., notepad.exe) with cross-platform alternatives (e.g., code, nano, vim, or generic 'edit with your preferred text editor').
- Clarify that both Azure PowerShell and Azure CLI can be used for these operations, and provide links to relevant Azure CLI documentation.
- Consider reordering sections so that cross-platform methods (Azure portal and Azure CLI) are presented before Windows-specific PowerShell instructions.
Load Balancer
Quickstart: Create a public load balancer - Azure portal
...cer/quickstart-load-balancer-standard-public-portal.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
windows_first
Summary
The documentation provides only Windows/PowerShell instructions for configuring IIS on backend VMs, with no mention of Linux alternatives (such as Apache or Nginx) or Linux command-line examples. The VM setup and load balancer creation steps are platform-neutral, but the web server installation and configuration section is Windows-centric, using PowerShell and IIS exclusively. This creates friction for users deploying Linux VMs as backend pool members.
Recommendations
- Add a parallel section for Linux VMs, showing how to install and configure a web server (e.g., Apache or Nginx) using Bash commands.
- Explicitly state that backend VMs can be either Windows or Linux, and provide guidance for both.
- Include example scripts for Linux (Ubuntu, CentOS, etc.) to match the PowerShell IIS setup.
- Mention that IIS is Windows-only, and suggest alternatives for Linux users.
Load Balancer
Quickstart: Create a public load balancer - ARM template
...r/quickstart-load-balancer-standard-public-template.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides only Azure PowerShell examples for deploying the ARM template, with no equivalent Azure CLI (bash) or Linux/macOS shell instructions. The step-by-step deployment walkthrough is PowerShell-centric, and the example commands use Windows-oriented patterns (e.g., Read-Host, Write-Host). Although the Azure portal and CLI are briefly mentioned as alternatives, no concrete Linux/macOS-friendly instructions or examples are given.
Recommendations
- Add step-by-step deployment instructions using Azure CLI (az) in bash, suitable for Linux/macOS users.
- Present both PowerShell and CLI examples side-by-side, or allow users to select their preferred environment.
- Avoid using Windows/PowerShell-specific patterns (e.g., Read-Host) as the only example for input collection.
- Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and provide examples for both.
- Ensure screenshots and walkthroughs are not exclusively Windows/PowerShell-centric.
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page for Azure Logic Apps examples and scenarios is generally cross-platform, but there is a notable tendency to mention PowerShell and Windows-centric scripting before Linux alternatives. For example, in the 'Run code from your workflows' section, PowerShell is listed alongside JavaScript, .NET, and C#, but there is no mention of Bash, shell scripts, or Linux-native scripting options. Additionally, deployment and management examples reference Azure DevOps and Visual Studio Code, which are cross-platform, but do not provide parity examples for Linux CLI or shell scripting. The overall bias is moderate, as Linux/macOS users can still complete all tasks, but may need to adapt Windows-centric instructions.
Recommendations
- Add examples for running Bash or shell scripts from Logic Apps workflows, alongside PowerShell.
- Explicitly mention Linux/macOS compatibility for Visual Studio Code and Azure DevOps workflows.
- Include references or links to using Azure CLI and scripting on Linux/macOS for deployment and management tasks.
- Where PowerShell is referenced, provide equivalent Bash or shell script examples if supported.
Migrate
Azure SQL assessments in Azure Migrate Discovery and assessment tool
...s/migrate/concepts-azure-sql-assessment-calculation.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation for Azure SQL assessments in Azure Migrate Discovery and assessment tool displays a moderate Windows bias. While the tool itself is cross-platform and supports assessment of SQL Server instances from VMware, Hyper-V, and physical environments (which can include Linux), the documentation repeatedly references Windows-specific patterns, tools, and best practices. Examples and links for SQL Server on Azure VM sizing and migration consistently point to Windows-focused resources, such as Windows Server Failover Clusters and PowerShell-based configuration. There is little to no mention of Linux-based SQL Server deployments, nor guidance for Linux-specific migration scenarios, tools, or best practices. Linux SQL Server users may find it challenging to map the guidance to their environments.
Recommendations
- Add explicit examples and guidance for assessing and migrating SQL Server instances running on Linux (RHEL, Ubuntu, SUSE, etc.), including any differences in discovery, sizing, and migration steps.
- Include links to Linux-specific best practices for SQL Server on Azure VM (e.g., /azure/azure-sql/virtual-machines/linux/).
- Clarify which steps, recommendations, or features are Windows-only and which are applicable to Linux SQL Server deployments.
- Provide parity in documentation for high availability and disaster recovery scenarios on Linux (e.g., Pacemaker clusters, Linux witness options).
- Where PowerShell or Windows tools are referenced, offer equivalent Bash/CLI/Linux-native alternatives if available.
Migrate
Tutorial to assess SQL instances in VMware VMs for migration to SQL Server on Azure VM, Azure SQL Managed Instance and Azure SQL Database
...ob/main/articles/migrate/tutorial-assess-sql-vmware.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation is generally platform-neutral regarding the assessment of SQL Server instances in VMware VMs for migration to Azure SQL solutions. However, there are several subtle signs of Windows bias: references to Windows Server Failover Clusters and Cloud Witness (Windows-only), links to Windows-specific performance guidelines, and no mention of Linux SQL Server scenarios or Linux-specific migration considerations. Examples and screenshots do not clarify whether Linux-based SQL Server instances are supported or how their migration might differ.
Recommendations
- Explicitly state whether Linux-based SQL Server instances in VMware VMs are supported for assessment and migration.
- Provide examples or notes for Linux SQL Server instances, including any differences in assessment, migration, or Azure SQL configuration.
- Where Windows-specific features (e.g., Cloud Witness, Windows Server Failover Clusters) are mentioned, clarify alternatives or limitations for Linux environments.
- Add links to Linux SQL Server performance guidelines and best practices for running SQL Server on Linux in Azure VMs.
- Ensure screenshots and instructions are inclusive of both Windows and Linux SQL Server scenarios, or clearly state any platform limitations.
Logic Apps
Create workflows with multiple Azure services
...ic-apps/tutorial-process-email-attachments-workflow.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page provides examples and instructions for both Azure PowerShell and Azure CLI when creating and managing Azure resources, but PowerShell and Windows-centric tools (such as Storage Explorer) are mentioned first or exclusively in several places. The tutorial also assumes use of the Azure portal, which is cross-platform, but the in-portal function editing is only supported on Windows, and this is called out. The use of Storage Explorer (a GUI tool available on Windows, macOS, and Linux) is required, but no alternatives or command-line options are suggested for Linux users. Overall, Linux parity is present but not emphasized, and Windows/PowerShell options are often listed before Linux/CLI equivalents.
Recommendations
- Ensure that Azure CLI examples are presented alongside or before PowerShell examples, especially in steps for creating resources and retrieving keys.
- Explicitly mention that Storage Explorer is available for Linux and macOS, and suggest command-line alternatives (such as az storage commands) for users who prefer CLI workflows.
- Where in-portal editing is Windows-only, provide clear instructions for local development on Linux/macOS, including links to relevant guides.
- Add notes or tips for Linux/macOS users throughout the tutorial to highlight any differences or alternative approaches.
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation for 'Create an Azure SQL assessment' demonstrates a moderate Windows bias. Several sections reference Windows-specific tools and patterns, such as Windows Server Failover Clusters and Cloud Witness, without mentioning Linux equivalents or alternatives. Links and examples for performance guidelines and high availability reference Windows-focused documentation. There are no Linux-specific examples or guidance for scenarios like cluster quorum or disk witness configuration. The documentation assumes familiarity with Windows environments and does not provide parity for Linux-based SQL Server deployments.
Recommendations
- Add explicit guidance for Linux-based SQL Server deployments, including how to configure high availability and disaster recovery in Azure VMs running Linux.
- Include links to Linux-specific performance guidelines and best practices for SQL Server on Azure VMs.
- Provide examples or notes for configuring cluster quorum and witness options for Linux environments, such as using shared disk or file share witness.
- Clarify which features or recommendations are Windows-only and suggest Linux alternatives where applicable.
Migrate
Tutorial to assess SQL instances for migration to SQL Server on Azure VM, Azure SQL Managed Instance and Azure SQL Database
...docs/blob/main/articles/migrate/tutorial-assess-sql.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page generally describes the assessment process for migrating SQL Server instances to Azure SQL, which is relevant for both Windows and Linux SQL Server deployments. However, there is a notable bias towards Windows in the high availability and disaster recovery section, where only Windows Server Failover Clusters and related tooling (Cloud Witness, Shared Disk) are mentioned. The linked best practices for VM sizing also point to Windows-specific guidance. Linux equivalents (such as Pacemaker clusters or Linux witness options) are not referenced, and Windows patterns are described first and exclusively in relevant sections.
Recommendations
- Add guidance or references for high availability and disaster recovery for SQL Server on Linux, such as Pacemaker clusters or Linux-based witness options.
- Include links to performance best practices for SQL Server on Azure VMs running Linux, not just Windows.
- Clarify in relevant sections whether the described features and recommendations apply to both Windows and Linux SQL Server deployments, or specify any limitations.
- Where Windows-specific tooling is mentioned (e.g., Cloud Witness), provide Linux alternatives or note if none exist.
Nat Gateway
Quickstart: Create a Standard V2 Azure NAT Gateway - Deployment templates
...-gateway/quickstart-create-nat-gateway-v2-templates.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides deployment instructions primarily using Azure PowerShell, with CLI examples only present for Bicep deployments. The ARM template deployment section exclusively uses PowerShell, which is more familiar to Windows users, and the PowerShell examples are presented before CLI alternatives. There is no explicit Linux shell (bash) example for ARM template deployment, and PowerShell is the default for resource cleanup as well.
Recommendations
- Add Azure CLI (bash) examples for ARM template deployment alongside PowerShell, ensuring Linux/macOS users have clear instructions.
- Present CLI and PowerShell examples side-by-side or in tabs for all deployment and cleanup steps, rather than defaulting to PowerShell.
- Explicitly mention that both Azure CLI and PowerShell are cross-platform, but provide bash syntax for CLI commands to improve accessibility for Linux/macOS users.
- Ensure that instructions for copying/pasting commands do not assume Windows conventions (e.g., right-click to paste).
Firewall
Azure Firewall known issues and limitations
...s/blob/main/articles/firewall/firewall-known-issues.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
Summary
The documentation page is generally platform-neutral and focuses on Azure Firewall service limitations. However, there are minor signs of Windows bias: PowerShell is mentioned as the primary tool for updating firewall policy tags, and IIS is referenced as an example for FTP server configuration. There are no Linux/macOS-specific CLI or tool examples, and PowerShell is suggested without parity for Bash/CLI. No critical sections are Windows-only, and most guidance applies equally to all platforms.
Recommendations
- When mentioning PowerShell cmdlets (e.g., Set-AzFirewallPolicy), also provide equivalent Azure CLI (az) commands or REST API examples for Linux/macOS users.
- When referencing IIS for FTP configuration, add a note or link to equivalent configuration steps for common Linux FTP servers (e.g., vsftpd, proftpd).
- Ensure that troubleshooting steps and mitigations do not assume use of Windows-only tools unless the feature is Windows-specific.
- Where possible, clarify that portal and REST API actions are cross-platform.
API Management
Deploy an Azure API Management Instance to Multiple Azure Regions
...management/api-management-howto-deploy-multi-region.md
Low Priority
View Details â
Detected Bias Types
windows_tools
powershell_heavy
windows_first
Summary
The documentation page provides Azure CLI and Azure PowerShell examples for managing multi-region API Management deployments, but it mentions the PowerShell cmdlet before the CLI and does not provide Bash/Linux shell script examples. The references to Azure PowerShell (set-azapimanagement) and the ordering of example tools may create a mild Windows bias. However, the core instructions are portal-based and the CLI is documented, so Linux/macOS users can complete all tasks.
Recommendations
- Provide explicit Bash/Linux shell script examples alongside Azure CLI commands where automation is discussed.
- List Azure CLI examples before PowerShell examples, as CLI is cross-platform.
- Clarify that all CLI commands work on Linux/macOS and link to CLI installation docs for those platforms.
- Where PowerShell is mentioned, note that Azure PowerShell is available on Linux/macOS, or link to installation instructions.
API Management
Backup and restore your Azure API Management instance for disaster recovery
...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-howto-disaster-recovery-backup-restore.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides detailed PowerShell examples for backup and restore operations before CLI and REST examples, and uses PowerShell-specific cmdlets and variable syntax. While Azure PowerShell is cross-platform, its usage and syntax are more familiar to Windows users. The CLI (Bash) and REST examples are present and reasonably complete, but PowerShell is presented first and in greater detail, which may create friction for Linux/macOS users who typically prefer Bash/CLI.
Recommendations
- Present Azure CLI (Bash) examples before or alongside PowerShell examples to better support Linux/macOS users.
- Explicitly note that Azure PowerShell is cross-platform and provide installation instructions for Linux/macOS.
- Ensure parity in detail and explanation between PowerShell and CLI sections.
- Consider adding troubleshooting tips or links for common Linux/macOS issues with Azure PowerShell, 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
Summary
The documentation generally maintains cross-platform parity, but there are minor signs of Windows bias. In the 'Mount file shares' section, Azure CLI (Linux-friendly) instructions are presented before PowerShell, but both are provided. However, elsewhere, references to Consumption plans often specify 'Windows only' before mentioning Linux, and PowerShell is mentioned as a supported language for managed dependencies in Azure Files before other languages. There are no critical sections that are Windows-only, and Linux-specific guidance (such as mounting Azure Files) is clearly marked and provided.
Recommendations
- Ensure all example commands and configuration settings are shown for both Windows (PowerShell) and Linux (CLI/bash) where applicable.
- When referencing features or settings, clarify platform applicability (e.g., 'Windows only', 'Linux only') in a consistent manner.
- Where PowerShell is mentioned for managed dependencies, also mention equivalent support or limitations for other languages (e.g., Python, Node.js) if relevant.
- Continue to provide Linux-specific instructions and highlight them where appropriate.
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
powershell_heavy
windows_tools
Summary
The documentation is generally cross-platform and covers both Windows and Linux scenarios for Azure Functions app settings. However, there are minor signs of Windows bias: Windows-specific syntax and examples (e.g., %HOME% for paths), Windows-only settings are sometimes listed before Linux equivalents, and PowerShell-specific settings are documented in detail. Additionally, recommendations for programmatic management of settings mention Azure PowerShell before Azure CLI, and some legacy settings reference Windows behaviors. Linux/macOS equivalents are present but sometimes appear after Windows references.
Recommendations
- Where examples use Windows-specific syntax (e.g., %HOME%), provide equivalent Linux/macOS examples (e.g., $HOME or /home).
- When listing platform-specific settings (such as WEBSITE_TIME_ZONE), present Windows and Linux options side-by-side or in parallel tables.
- In sections recommending tools for managing settings, mention Azure CLI before or alongside Azure PowerShell, as CLI is cross-platform.
- Review ordering of platform-specific notes to ensure Linux/macOS information is not consistently secondary.
- For PowerShell-heavy sections, ensure parity by referencing equivalent scripting or automation options for Linux/macOS (e.g., Bash, Azure CLI).
Azure Functions
Migrate Consumption plan apps to Flex Consumption in Azure Functions
...unctions/migration/migrate-plan-consumption-to-flex.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Linux and Windows migration paths for Azure Functions Consumption to Flex Consumption plans. However, Windows/PowerShell/Azure CLI examples and instructions are frequently presented first or in greater detail, especially in the Windows pivot sections. Some command-line examples and scripts are tailored to Windows environments, and Windows-specific tools and patterns (such as Azure CLI commands for Windows, PowerShell scripting, and portal navigation) are emphasized. The Linux migration path is covered, but the overall structure and example ordering tend to prioritize Windows users.
Recommendations
- Ensure Linux and Windows instructions/examples are presented with equal prominence and detail.
- Where possible, provide Linux-first or side-by-side examples, especially for CLI commands and scripting.
- Avoid defaulting to Windows/PowerShell tools in generic sections; highlight cross-platform alternatives (e.g., Bash, Azure CLI, jq).
- Explicitly call out differences in tooling and workflow between Linux and Windows, and provide parity in troubleshooting and advanced configuration examples.
- Review and balance the ordering of platform pivots so Linux users do not need to scroll past Windows-heavy content to find relevant instructions.
Azure Resource Manager
Bicep functions - resources
...ure-resource-manager/bicep/bicep-functions-resource.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both PowerShell and Azure CLI examples for discovering 'list' operations, but the PowerShell (Windows-centric) example is presented first, followed by the Azure CLI example. No other evidence of Windows bias is present; all code samples are in Bicep, which is cross-platform, and no Windows-specific tools or patterns are referenced elsewhere.
Recommendations
- Present Azure CLI (cross-platform) examples before PowerShell examples, or present both together with equal prominence.
- Explicitly note that both Azure CLI and PowerShell are supported on Windows, Linux, and macOS, and provide links to installation guides for each platform.
- Where possible, add Bash or shell script examples for common resource queries to further improve Linux parity.
Azure Resource Manager
Template functions - resources
...ource-manager/templates/template-functions-resource.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation is generally cross-platform and focuses on ARM template functions, which are platform-agnostic. However, in the section about discovering 'list' operations for resource types, the PowerShell example is presented before the Azure CLI example. This is a minor instance of Windows-first bias, as Azure CLI is more commonly used on Linux/macOS, while PowerShell is more associated with Windows.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples, especially in sections relevant to both Linux/macOS and Windows users.
- Explicitly state that both CLI and PowerShell commands are supported on all platforms, and link to installation guides for each.
- Where possible, provide Bash or shell script examples for common tasks, in addition to PowerShell.
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The glossary is generally cross-platform and workload-neutral, but there are some mild signs of Windows bias. Windows-specific tools and technologies (e.g., VSS, DPM, MABS, MARS Agent) are referenced without always providing Linux/macOS equivalents or context. In the 'Application consistent backup' entry, VSS is mentioned first, with Linux alternatives only briefly referenced as 'pre or post scripts.' The 'Snapshot' entry links only to Windows disk snapshot documentation. Windows backup concepts (bare metal, system state) are described, but Linux equivalents are not discussed. However, most of these terms are workload-specific and reflect Azure Backup's actual supported workloads, which are often Windows-centric.
Recommendations
- Where Windows tools (e.g., VSS) are mentioned, provide equal detail or links for Linux/macOS alternatives (e.g., fsfreeze, custom scripts, etc.).
- In entries like 'Application consistent backup,' clarify how Linux workloads achieve consistency and link to relevant documentation.
- For concepts like 'bare metal backup' and 'system state backup,' note whether these are Windows-only and, if so, clarify Linux/macOS limitations or alternatives.
- In 'Snapshot,' add links to Linux disk snapshot documentation or clarify that the link is Windows-specific.
- Where workload-specific Windows tools are referenced (DPM, MABS, MARS Agent), clarify their platform scope and mention Linux backup options if available.
Low Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The Azure Bastion FAQ documentation demonstrates minor Windows bias in several areas. Browser recommendations mention Windows first and provide more detail for Windows users. Keyboard layout configuration instructions are exclusively for Windows, with no guidance for Linux or macOS users. There are no explicit Linux/macOS examples for setting keyboard layouts or other OS-specific tasks, potentially creating friction for non-Windows users.
Recommendations
- Add instructions for configuring keyboard layouts on Linux and macOS systems alongside the Windows steps.
- When listing supported browsers, present options for all platforms equally and avoid listing Windows first unless there is a technical reason.
- Where OS-specific configuration is discussed (e.g., keyboard layouts), include parity guidance for Linux and macOS users.
- Review other sections for subtle Windows-first language and ensure Linux/macOS users are equally addressed where relevant.
Container Apps
Deploy the Dapr extension for Azure Functions in Azure Container Apps
...in/articles/container-apps/dapr-functions-extension.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both PowerShell and curl examples for invoking Azure Functions and viewing logs, but PowerShell examples are presented first in each case. This ordering may subtly suggest a Windows-first approach. However, all critical steps are covered with cross-platform tools (Azure CLI, curl), and Linux/macOS users can follow the instructions without issue.
Recommendations
- Present curl (cross-platform) examples before PowerShell examples, or side-by-side, to avoid implying Windows is the primary platform.
- Explicitly state that all commands work on Linux/macOS unless otherwise noted.
- Consider adding Bash script examples for multi-step processes, if relevant.
- Clarify that Azure CLI is cross-platform and works on Windows, Linux, and macOS.
Container Apps
Troubleshooting in Azure Container Apps
...s/blob/main/articles/container-apps/troubleshooting.md
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
powershell_heavy
Summary
The documentation provides troubleshooting guidance for Azure Container Apps and generally maintains platform neutrality. However, there are mild signs of Windows bias: references to running Docker commands in an 'elevated command prompt' and explicit mention of 'Docker on Windows' before Linux/Mac equivalents. PowerShell examples are given equal prominence to Bash, but the PowerShell module (Az.App) is referenced without mentioning Linux/macOS compatibility. The instructions and tooling otherwise work cross-platform, but Windows terminology and ordering are slightly favored.
Recommendations
- When referencing Docker, mention Linux and macOS usage alongside Windows, e.g., 'If you're running Docker on Windows, Linux, or macOS, ensure Docker Engine is running.'
- Replace 'elevated command prompt' with platform-neutral language, such as 'a terminal with appropriate permissions.'
- Clarify that the Az.App PowerShell module is available on all platforms where PowerShell Core runs, not just Windows.
- Ensure that Bash and PowerShell examples are presented with equal visibility and context for all platforms.
- Where possible, add notes or links for Linux/macOS users regarding installation or usage differences.
Event Grid
Concepts (push delivery) in Event Grid basic
...s/azure-docs/blob/main/articles/event-grid/concepts.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation page provides example links for creating Event Grid subscriptions using Azure CLI, Azure PowerShell, and ARM templates. The PowerShell example is listed before the ARM template, and both CLI and PowerShell are mentioned, but no explicit Linux/macOS shell or Bash examples are given. PowerShell is a cross-platform tool, but its historical association with Windows and its placement before other examples may create a perception of Windows bias. No Windows-only tools or patterns are referenced, and the main concepts are platform-neutral.
Recommendations
- Add explicit Bash or shell script examples for Linux/macOS users, or clarify that Azure CLI examples work identically across platforms.
- List Azure CLI (which is cross-platform) and Bash examples before PowerShell to reduce perceived Windows-first bias.
- Include a note clarifying PowerShell's cross-platform support, if PowerShell examples are retained.
- Ensure that all referenced sample scripts have clear instructions for both Windows and Linux/macOS environments.
Load Balancer
Tutorial: Create a single virtual machine inbound NAT rule - Azure portal
...ancer/tutorial-load-balancer-port-forwarding-portal.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides SSH connection instructions for both Mac/Linux (Bash) and Windows (PowerShell) users, but the SSH command examples use Windows path notation (backslashes) and show the Windows-style example first. There are no PowerShell-specific commands or Windows-only tools mentioned, and the tutorial is otherwise platform-neutral.
Recommendations
- Provide both Windows and Linux/macOS SSH command examples, with correct path notation for each (e.g., use './Downloads/lb-key-pair.pem' for Linux/macOS and '.\Downloads\lb-key-pair.pem' for Windows).
- Explicitly show the Bash/Linux/macOS example first, or present both side-by-side.
- Clarify that the SSH command syntax may differ slightly depending on the user's OS and shell.
Logic Apps
Call Azure Functions from workflows
...cles/logic-apps/call-azure-functions-from-workflows.md
Low Priority
View Details â
Detected Bias Types
windows_tools
powershell_heavy
windows_first
Summary
The documentation provides examples and instructions for creating and managing Azure Functions using both cross-platform and Windows-specific tools. However, there is a slight bias towards Windows tools and patterns: PowerShell is mentioned as a way to find tenant IDs, and Visual Studio (Windows-only) is listed before Visual Studio Code and Azure CLI. The use of Kudu (Advanced Tools) for editing files is also more familiar to Windows users. Linux/macOS equivalents (such as Bash, cross-platform CLI commands, or VS Code) are present but not emphasized equally.
Recommendations
- When listing tools for creating Azure Functions, mention cross-platform options (Azure CLI, VS Code) before Windows-only tools (Visual Studio, PowerShell).
- Provide explicit Bash/Azure CLI commands for tasks like finding tenant IDs, object IDs, and editing function.json, alongside PowerShell examples.
- Clarify that Kudu is accessible via the browser and is not Windows-specific, and suggest alternatives for editing files (e.g., using Azure CLI or VS Code).
- Ensure screenshots and step-by-step instructions are not overly tailored to Windows UI conventions.
Logic Apps
Multi-region deployments for disaster recovery in Azure Logic Apps
.../articles/logic-apps/multi-region-disaster-recovery.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation occasionally references PowerShell scripts and manual operations (e.g., activating a secondary Logic App instance) as example mechanisms, but does not provide equivalent examples for Linux/macOS users (such as Bash/CLI). PowerShell is mentioned as a way to manually run user operations, but no Linux shell alternatives are suggested. The documentation also tends to mention Windows-centric tools (PowerShell) before cross-platform or Linux-native options.
Recommendations
- When suggesting manual script-based operations (e.g., activating a Logic App), provide examples using Azure CLI (az), Bash, or other cross-platform tools alongside PowerShell.
- Explicitly mention that Azure CLI and REST API calls can be used from any OS, and provide sample commands for Linux/macOS users.
- Avoid implying PowerShell is the only or primary method for automation; present it as one option among several.
- Where 'run a script' is suggested, clarify that both PowerShell and Bash (or other shells) are supported, and link to relevant cross-platform documentation.
Low Priority
View Details â
Detected Bias Types
windows_reference
Summary
The documentation is generally platform-neutral, focusing on Azure NAT Gateway concepts and configuration. However, there is a minor Windows bias in the 'Default outbound access' section, which specifically mentions Windows Activation and Windows Updates as requiring outbound connectivity. No Linux/macOS-specific examples, tools, or patterns are referenced, but the overall guidance applies equally to all OS types. No PowerShell-only examples or Windows-centric tooling is present.
Recommendations
- Add a brief note clarifying that Linux and other OSes may also require outbound connectivity for package updates and activation, not just Windows.
- Where outbound connectivity is discussed, mention common Linux/macOS scenarios (e.g., apt/yum updates, OS activation if relevant) alongside Windows examples.
- Ensure future quickstarts and tutorials include CLI and portal instructions that are OS-agnostic, or provide both PowerShell and Bash/Azure CLI examples where relevant.