155
Pages Scanned
25
Pages Flagged
155
Changed Pages
16.1%
% Pages Flagged
Scan Information
Started At: 2026-01-17 00:00:08
Finished At: 2026-01-17 00:06:01
Status: completed
Target Repo: Azure
Current Phase: discovery
Files Queued: 155
Files Completed: 155
Problematic Pages
25 issues found
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
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page is heavily focused on Windows-specific tools and workflows, particularly SignTool, PowerShell, and Windows installers (MSI, Setup.exe, winget). All setup instructions, examples, and prerequisites for the main integration (SignTool) are Windows-only, with no mention of Linux/macOS alternatives or cross-platform signing tools. Other integrations (GitHub Actions, Azure DevOps, SDK) are referenced but not documented in detail, and no Linux/macOS-specific signing guidance is provided.
Recommendations
- Clearly indicate that SignTool integration is Windows-only, and provide guidance for Linux/macOS users on alternative signing methods or integrations.
- Add explicit sections or examples for Linux/macOS users, such as using the Artifact Signing SDK, GitHub Actions, or Azure DevOps pipelines from non-Windows environments.
- Document cross-platform signing workflows, including how to use Artifact Signing from Linux/macOS CI runners or developer machines.
- If possible, provide parity for installation and usage instructions for the Artifact Signing SDK or other integrations on Linux/macOS.
- List platform compatibility for each integration at the top of the page, so users can quickly identify which options are available for their OS.
Create Pull Request
Backup
Back up SQL Server databases to Azure
...blob/main/articles/backup/backup-azure-sql-database.md
High Priority
View Details →
Detected Bias Types
windows_tools
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation is heavily focused on Windows environments: all examples, instructions, and tooling (SSMS, NT SERVICE accounts, PowerShell, Windows file paths, Task Manager, SMB shares) are Windows-specific. There is no mention of Linux-based SQL Server VMs, nor are Linux equivalents (such as Linux authentication, file permissions, or shell commands) provided. This creates friction for users running SQL Server on Linux in Azure VMs, who cannot directly follow the steps or examples.
Recommendations
- Explicitly state whether the Azure Backup solution supports SQL Server on Linux VMs. If not supported, clarify this early in the documentation.
- If Linux SQL Server VMs are supported, add Linux-specific instructions for configuring permissions, managing service accounts, and setting up local backup folders (e.g., using chown/chmod, Linux paths, systemd service management).
- Provide shell (bash) and/or sqlcmd examples for Linux environments alongside PowerShell examples.
- Clarify any limitations or differences in backup extension installation and operation on Linux VMs.
- Include screenshots or CLI steps relevant to Linux environments (e.g., using Azure CLI, Linux file managers, etc.).
Site Recovery
Azure Site Recovery Deployment Planner for VMware disaster recovery
...cles/site-recovery/site-recovery-deployment-planner.md
High Priority
View Details →
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation for the Azure Site Recovery Deployment Planner for VMware disaster recovery is heavily Windows-centric. All instructions, prerequisites, and examples assume the use of Windows Server or Windows PC, with no mention of Linux or macOS support or alternatives. The tool itself appears to require Windows, and report generation requires Excel on Windows. There are no Linux/macOS usage instructions, examples, or parity tools provided.
Recommendations
- Clearly state in the prerequisites and introduction whether the Deployment Planner tool is Windows-only, and if so, explain the rationale.
- If possible, provide a Linux-compatible version of the Deployment Planner tool, or document any workarounds for Linux/macOS users (e.g., running the tool in a Windows VM or via Wine).
- Offer alternative report generation instructions for users who do not have access to Excel on Windows (e.g., using LibreOffice, or exporting to CSV).
- Add a note about platform limitations early in the documentation to set expectations for non-Windows users.
Site Recovery
Run the deployment Planner for VMware disaster recovery with Azure Site Recovery
...ecovery/site-recovery-vmware-deployment-planner-run.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation for running the Deployment Planner for VMware disaster recovery with Azure Site Recovery demonstrates a notable Windows bias. All examples for gathering VM lists use VMware vSphere PowerCLI (PowerShell), and instructions reference Windows-specific tools (ASRDeploymentPlanner.exe, Notepad, UNC paths). The report output requires Microsoft Excel on Windows, and there is no mention of Linux/macOS alternatives or guidance for running the tool or processing results on non-Windows platforms.
Recommendations
- Provide equivalent Linux/macOS instructions for gathering VM lists (e.g., using VMware CLI tools, Python scripts, or bash commands).
- Clarify whether ASRDeploymentPlanner.exe can be run under Wine or Mono on Linux/macOS, or explicitly state Windows-only requirements.
- Suggest cross-platform alternatives for viewing and processing the report output (e.g., LibreOffice for Excel files, or provide CSV output options).
- Add a section explicitly outlining platform requirements and limitations, so non-Windows users can plan accordingly.
- If the tool is strictly Windows-only, recommend remote access or VM solutions for Linux/macOS users.
Cost Management Billing
Tutorial - Optimize centrally managed Azure Hybrid Benefit for SQL Server
...ling/scope-level/tutorial-azure-hybrid-benefits-sql.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. It references PowerShell scripts as the primary method for analyzing Azure SQL license usage and links only to Windows-specific instructions for registering SQL Server VMs with the SQL IaaS Agent Extension. No Linux or cross-platform alternatives are mentioned, and Windows tools/patterns are presented first and exclusively.
Recommendations
- Include equivalent CLI or Bash examples for gathering SQL license usage, or clarify if PowerShell scripts work on Linux/macOS via PowerShell Core.
- Add links to documentation for registering SQL Server VMs running on Linux, if supported, or explicitly state if the registration process is Windows-only.
- Where PowerShell is referenced, note platform compatibility and provide guidance for Linux/macOS users.
- If certain steps are Windows-only, clarify this in the documentation to set expectations for Linux users.
Site Recovery
Scale VMware/physical disaster recovery with Azure Site Recovery
...cles/site-recovery/vmware-physical-large-deployment.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation is generally cross-platform and covers both VMware VMs and physical servers, which can be Windows or Linux. However, there are subtle signs of Windows bias: the only explicit scripting example for triggering failover uses a PowerShell cmdlet, and compliance checks and preparation steps are described in more detail for Windows than Linux. Linux compliance is mentioned only briefly, and no Linux-native scripting or command-line examples are provided.
Recommendations
- Provide equivalent Linux command-line examples (e.g., using Azure CLI or REST API) for tasks like triggering failover, not just PowerShell.
- Expand on Linux compliance preparation steps, or link to detailed guidance for Linux machines, similar to the Windows-focused troubleshooting and preparation links.
- When referencing automation (e.g., runbooks), clarify that both PowerShell and Bash/CLI scripts are supported and provide examples for both where possible.
- Ensure that monitoring and setup instructions reference tools and workflows familiar to Linux administrators, not just those common in Windows environments.
Security
Security best practices for IaaS workloads in Azure | Microsoft Docs
...-docs/blob/main/articles/security/fundamentals/iaas.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation generally covers both Windows and Linux VMs, but there are several instances where Windows-specific tools, terminology, and examples are presented first or exclusively. PowerShell cmdlets (e.g., Add-AzKeyVaultKey) are referenced without Linux CLI equivalents, and some backup/snapshot links point to Windows-specific pages. Antimalware recommendations include Windows Defender and System Center Endpoint Protection, which are Windows-only, with less emphasis on Linux alternatives. Monitoring and diagnostics sections mention Windows-focused extensions and tools before Linux options. While Linux is acknowledged, examples and actionable steps are often Windows-centric or lack Linux parity.
Recommendations
- Provide CLI/bash equivalents for PowerShell cmdlets, especially for key management and encryption operations.
- Include Linux-specific antimalware solutions and examples alongside Windows Defender/System Center Endpoint Protection.
- Ensure backup and snapshot instructions link to both Windows and Linux VM documentation.
- Present Windows and Linux examples side-by-side or alternate which is shown first.
- Expand monitoring/diagnostics instructions to explicitly cover Linux VM extensions and tools.
Azure Functions
Deployment technologies in Azure Functions
...s/azure-functions/functions-deployment-technologies.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation generally covers both Windows and Linux deployment options for Azure Functions, but there are subtle biases. Windows-based deployment methods (such as source control, local Git, and FTPS) are called out as 'Windows-only' in the technology availability table, but Linux equivalents are not always described in equal detail. Examples and instructions often mention Visual Studio and Visual Studio Code (which are more Windows-centric), and Windows deployment mechanisms are frequently listed first. Some deployment instructions lack explicit Linux command-line examples, and the use of Kudu/scm is explained more thoroughly for Windows than for Linux. Overall, Linux deployment is supported and described, but Windows patterns and tools are prioritized or explained more deeply.
Recommendations
- Add explicit Linux/macOS command-line examples for deployment steps where only Windows/Visual Studio/VS Code are mentioned.
- Balance the order of presentation so that Linux deployment options and tools are described alongside or before Windows equivalents where possible.
- Expand explanations of Linux-specific deployment behaviors, especially where Kudu/scm is limited or absent.
- Clarify which tools (e.g., Azure Functions Core Tools, Azure CLI) are fully cross-platform and provide usage examples for Linux/macOS.
- Where deployment methods are Windows-only, suggest Linux alternatives or link to relevant Linux documentation.
Azure Functions
Monitor executions in Azure Functions
.../main/articles/azure-functions/functions-monitoring.md
Medium Priority
View Details →
Detected Bias Types
missing_linux_example
windows_first
Summary
The documentation generally avoids platform-specific bias, but there are a few areas where Windows is implicitly favored. Notably, the 'Performance Counters' feature is only supported on Windows, and the 'Built-in log streaming' method does not support Linux in the Consumption plan, but these limitations are called out. However, examples and instructions for Linux users (such as alternative log streaming methods or how to monitor performance on Linux) are not provided. In sections where platform limitations exist, Windows capabilities are described first or exclusively, with Linux limitations mentioned as exceptions rather than providing Linux-centric guidance.
Recommendations
- Where features are Windows-only (e.g., Performance Counters, built-in log streaming), provide Linux alternatives or guidance for Linux users (e.g., suggest using Live Metrics Stream or other monitoring tools).
- Explicitly document recommended monitoring workflows for Linux-hosted Azure Functions, including any differences in setup or available features.
- Add examples or links for Linux/macOS users where relevant, especially in sections that describe features unavailable on Linux.
- Consider reordering sections so that Linux limitations are described upfront, or provide parity in example coverage.
Azure Functions
Migrate apps from Azure Functions version 3.x to 4.x
...rticles/azure-functions/migrate-version-3-version-4.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page for migrating Azure Functions from version 3.x to 4.x shows a moderate Windows bias. The initial step to identify function apps to migrate provides only a PowerShell script, with no equivalent Azure CLI, Bash, or Linux-native example. PowerShell is a Windows-centric tool, and its exclusive use may create friction for Linux/macOS users. Additionally, references to Azure PowerShell are made before mentioning cross-platform alternatives. However, the rest of the migration instructions are largely language-agnostic or use cross-platform tools (such as Azure Functions Core Tools), and there is no evidence of Windows-only tools or patterns in the core migration steps.
Recommendations
- Provide an Azure CLI or Bash example alongside the PowerShell script for identifying function apps to migrate.
- Explicitly mention that Azure PowerShell is available cross-platform, but offer alternatives for users who prefer CLI or Bash.
- Where scripts or commands are given, ensure both Windows and Linux/macOS equivalents are presented, or clarify cross-platform compatibility.
- Review the documentation for other places where Windows-first tools are mentioned and add Linux/macOS parity.
Cost Management Billing
Save on SAP HANA Large Instances with an Azure reservation
...-docs/prepay-hana-large-instances-reserved-capacity.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation provides all command-line examples using armclient with PowerShell syntax and Azure PowerShell code blocks. There is no mention of Linux/macOS equivalents, nor are cross-platform tools or shell examples (such as Bash/cURL) provided. This creates friction for Linux/macOS users who may not use PowerShell or armclient in the same way.
Recommendations
- Include equivalent examples using Bash and cURL or HTTPie for REST API calls.
- Clarify whether armclient is cross-platform and provide installation/use instructions for Linux/macOS if applicable.
- Use generic REST API examples (e.g., with cURL) alongside PowerShell to ensure parity.
- Explicitly state that the process is platform-agnostic if true, and highlight any platform-specific requirements.
Cost Management Billing
Manage Azure Reservations
...nt-billing/reservations/manage-reserved-vm-instance.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation provides command-line examples exclusively using PowerShell cmdlets for reservation management tasks (e.g., splitting a reservation), without offering Azure CLI equivalents or REST API sample calls. This creates friction for Linux/macOS users, who typically use Azure CLI or direct API calls rather than PowerShell. The page also refers to PowerShell as the primary automation tool, implicitly favoring Windows environments.
Recommendations
- Add Azure CLI examples for all reservation management tasks currently demonstrated with PowerShell, especially for splitting reservations and updating scope.
- Include REST API sample requests (with curl or HTTP examples) for relevant operations to ensure cross-platform accessibility.
- Clearly indicate that PowerShell is one of several supported tools, and link to Azure CLI and REST API documentation for parity.
- Where screenshots or instructions reference PowerShell, provide equivalent steps for CLI and API usage.
Cost Management Billing
Calculate EA reservations cost savings
...ling/reservations/calculate-ea-reservations-savings.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation primarily demonstrates the reservation savings calculation process using Microsoft Excel, a Windows-centric application, and all step-by-step instructions and screenshots are based on Excel. While it briefly mentions that other spreadsheet applications can be used, no examples or guidance are provided for Linux/macOS alternatives (e.g., LibreOffice Calc, Google Sheets). There are no command-line or open-source tool examples, and the workflow assumes a GUI-heavy, Windows-first approach.
Recommendations
- Provide explicit instructions or examples for performing the same calculations in LibreOffice Calc, Google Sheets, or other cross-platform spreadsheet tools.
- Include screenshots or step-by-step guidance for at least one non-Windows spreadsheet application.
- Mention command-line alternatives (e.g., using Python/pandas or csvkit) for users who prefer scripting or do not use GUI spreadsheet tools.
- Clarify any differences in CSV handling or formula syntax between Excel and other spreadsheet applications.
Cost Management Billing
SQL IaaS extension registration options for Cost Management administrators
...billing/scope-level/sql-iaas-extension-registration.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides PowerShell script examples and references for checking and completing SQL IaaS Agent extension registration, but does not mention or provide equivalent CLI, Bash, or Linux/macOS-specific instructions. The registration process is described primarily through Azure portal steps and PowerShell automation, with no discussion of cross-platform alternatives. This creates friction for Linux/macOS users who may prefer or require non-PowerShell tooling.
Recommendations
- Add Azure CLI examples for checking registration status and enabling SQL IaaS Agent extension registration, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Explicitly state whether PowerShell Core (pwsh) is supported for the provided scripts, and clarify any Windows-only requirements.
- Provide Bash script or REST API examples for automation, or link to relevant cross-platform documentation.
- Include a note on platform compatibility for the PowerShell scripts, and suggest alternatives for non-Windows environments.
Cost Management Billing
Permissions to View and Manage Azure Reservations
...t-management-billing/reservations/view-reservations.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
missing_linux_example
Summary
The documentation provides a section on managing reservation access using PowerShell but does not mention or provide examples for cross-platform alternatives such as Azure CLI, which is widely used on Linux and macOS. The only command-line tool referenced is Azure PowerShell, and the only command shown is a PowerShell cmdlet. There are no CLI or REST API examples, and the documentation does not clarify whether the described PowerShell steps are available or equivalent on non-Windows platforms.
Recommendations
- Add equivalent Azure CLI examples for managing reservation RBAC roles, including commands for viewing and assigning roles.
- Clarify whether the PowerShell steps can be performed using Azure CLI or REST API, and link to relevant documentation.
- Explicitly state that Azure PowerShell is cross-platform if that is the case, or provide installation/use guidance for Linux/macOS users.
- Wherever possible, present both PowerShell and CLI examples side by side, or at least mention both approaches.
Cost Management Billing
Transition to centrally managed Azure Hybrid Benefit
...-management-billing/scope-level/transition-existing.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page provides a PowerShell script as the primary method for analyzing SQL Server license usage across Azure subscriptions, without mentioning or providing equivalent Linux/macOS-friendly alternatives (such as Azure CLI, Bash, or REST API examples). PowerShell is natively available only on Windows, and while cross-platform versions exist, many Linux/macOS users expect CLI or Bash examples. The documentation also refers to PowerShell before mentioning APIs or other methods, indicating a Windows-first approach.
Recommendations
- Provide equivalent examples using Azure CLI or Bash scripts for analyzing SQL Server license usage.
- Explicitly mention REST API options for license usage analysis and link to relevant API documentation.
- Clarify that PowerShell Core is available cross-platform, but also offer instructions for Linux/macOS users who may prefer CLI or Bash.
- Where PowerShell scripts are referenced, add notes or links to cross-platform installation guides.
Service Bus Messaging
Test locally by using the Azure Service Bus emulator
...us-messaging/test-locally-with-service-bus-emulator.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides setup instructions for both Windows and Linux/macOS, but the Windows instructions are presented first and in greater detail, including explicit PowerShell and WSL steps. Linux/macOS instructions are less detailed and lack step-by-step guidance. Some examples (like file paths in .env) default to Windows syntax, and the automated script section is Windows-centric.
Recommendations
- Present Linux/macOS instructions before or alongside Windows instructions, with equal detail.
- Provide explicit step-by-step commands for Linux/macOS users, including terminal commands for cloning the repo and running scripts.
- Clarify file path syntax for both Windows and Linux/macOS in environment variable examples.
- Include screenshots or terminal output examples for Linux/macOS users.
- Ensure that any PowerShell/WSL steps are matched with equivalent bash/zsh instructions for Linux/macOS.
Migrate
Discover, assess, and migrate Amazon Web Services (AWS) EC2 VMs to Azure
...icles/migrate/tutorial-migrate-aws-virtual-machines.md
Medium Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation exhibits moderate Windows bias. The replication appliance required for migration must be hosted on Windows Server 2022, with no Linux alternative mentioned. Windows-specific instructions and screenshots are provided first and in more detail, while Linux steps (such as Mobility agent installation) are present but less emphasized. The appliance setup and management rely on Windows tools and patterns, and Linux users must adapt by using a Windows VM for the appliance, which may create friction.
Recommendations
- Clearly state early in the documentation that the replication appliance must run on Windows Server, and explain why no Linux alternative exists.
- Provide guidance for Linux-only environments, such as how to provision a temporary Windows Server VM for the appliance if needed.
- Where possible, offer parity in example commands, screenshots, and troubleshooting steps for both Windows and Linux VMs.
- Highlight any Linux-specific considerations or limitations (e.g., Amazon Linux migration restrictions) in a dedicated section.
- If future Azure Migrate releases support Linux-based appliances, update documentation to reflect this.
Azure Functions
Memory profiling of Python apps in Azure Functions
...es/azure-functions/python-memory-profiler-reference.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation generally maintains cross-platform parity, but in the 'Profile Python function app in local development environment' section, Windows commands and PowerShell are mentioned first and in more detail. The instructions for creating and activating a Python virtual environment list Windows commands before Linux equivalents, and PowerShell is specifically called out, which may subtly prioritize Windows users.
Recommendations
- Present Linux/macOS and Windows instructions side-by-side or in parallel tabs, rather than listing Windows first.
- Use neutral language such as 'Open a terminal (Windows PowerShell, Linux shell, or macOS Terminal)' instead of 'Open a Windows PowerShell or any Linux shell as you prefer.'
- Explicitly mention macOS where relevant, not just 'Linux'.
- Consider using code blocks with OS-specific tabs for commands (e.g., venv creation and activation) to improve clarity for all users.
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
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for configuring scale limits, but PowerShell is shown as a primary tab alongside CLI, which may indicate a slight Windows-first bias. There are no Linux/macOS-specific instructions or examples, and PowerShell is not natively available on Linux/macOS unless explicitly installed. However, the CLI examples are cross-platform, and no critical functionality is locked to Windows-only tools.
Recommendations
- Ensure that Azure CLI examples are always shown first, as CLI is cross-platform.
- Clarify that Azure PowerShell is available on Linux/macOS, or provide Bash examples where relevant.
- Add explicit notes or links for Linux/macOS users regarding installation or usage of PowerShell if needed.
- Consider including screenshots or walkthroughs for Linux/macOS environments to demonstrate parity.
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
Summary
The documentation is generally cross-platform and covers both Windows and Linux scenarios for Azure Functions app settings. However, there are minor instances of Windows bias: some examples use Windows-style paths (e.g., %HOME%\typescript), and in a few cases, Windows-specific settings (like WEBSITE_NODE_DEFAULT_VERSION) are mentioned before their Linux equivalents. Additionally, recommendations for managing app settings programmatically mention Azure PowerShell and Azure CLI together, but PowerShell is listed first, which may suggest a slight preference for Windows tooling. Overall, Linux-specific settings and considerations are present and well-documented.
Recommendations
- Where possible, provide both Windows and Linux/macOS examples for environment variables and paths (e.g., show $HOME/typescript for Linux/macOS alongside %HOME%\typescript for Windows).
- When listing tools for programmatic management (e.g., Azure CLI, Azure PowerShell), alternate the order or clarify parity to avoid perceived preference.
- Ensure that OS-specific settings (like WEBSITE_NODE_DEFAULT_VERSION for Windows) are clearly marked and that Linux equivalents (like linuxFxVersion) are equally visible and explained.
- Continue to expand Linux/macOS-specific notes and examples, especially for developer scenarios (local.settings.json, file paths, etc.).
Container Apps
Code to cloud options in Azure Container Apps
.../main/articles/container-apps/code-to-cloud-options.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page for 'Code to cloud options in Azure Container Apps' demonstrates mild Windows bias. Windows-centric tools (Visual Studio, Visual Studio Code) are mentioned first and exclusively in the 'Code editor' and 'Next steps' sections, with no mention of Linux/macOS alternatives or editors. While the Infrastructure as Code section references both PowerShell and Bash, PowerShell is listed first, and there are no explicit Linux/macOS command examples or guidance. There is no evidence of exclusive use of Windows-only tools, but the examples and recommendations are oriented toward Windows users.
Recommendations
- Include examples or references for popular Linux/macOS code editors (e.g., JetBrains Rider, Vim, Emacs) and their integration with Azure Container Apps.
- Provide explicit Bash examples alongside PowerShell, and clarify cross-platform CLI usage.
- Add notes or links for Linux/macOS users on how to install and use Azure CLI and Azure Developer CLI.
- Balance the ordering of tool mentions (e.g., Bash before PowerShell in CLI sections) to avoid Windows-first perception.
Azure Functions
Use Python and TensorFlow for machine learning in Azure
...ure-functions/functions-machine-learning-tensorflow.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides examples for Bash, PowerShell, and Cmd throughout, but consistently lists Windows-specific tools and patterns (PowerShell, Cmd) before Bash/Linux equivalents. Windows command syntax is often shown first, and troubleshooting advice is focused on Windows-specific issues (e.g., registry changes for long paths). The use of 'py' launcher is highlighted for Windows, and PowerShell/Cmd examples are given equal or greater prominence than Bash. However, Linux/macOS instructions are present for all critical steps, and the tutorial is not Windows-only.
Recommendations
- Present Bash/Linux examples first in each command section, as Bash is the default shell on Linux/macOS and increasingly on Windows (WSL, Git Bash).
- Balance troubleshooting advice by including common Linux/macOS issues (e.g., permissions, missing packages) alongside Windows-specific errors.
- Where possible, use cross-platform commands (e.g., 'python' instead of 'py') and clarify when a command is Windows-only.
- Explicitly state that all steps are supported on Linux/macOS and highlight any platform-specific differences.
- Consider grouping platform-specific instructions under clear headings or tabs, rather than interleaving them.
Security
Azure encryption overview | Microsoft Docs
.../articles/security/fundamentals/encryption-overview.md
Low Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation is generally platform-neutral, focusing on Azure's encryption features and models. However, there is a minor Windows bias in the 'SMB encryption' section, which references Windows Server and desktop versions exclusively, without mentioning Linux SMB client support or alternatives. Additionally, examples and tool references throughout the page do not provide parity for Linux/macOS users where relevant (e.g., no mention of Linux SMB client encryption or cross-platform VPN client options).
Recommendations
- In the 'SMB encryption' section, mention that Linux SMB clients (such as smbclient or mount.cifs) can also connect to Azure Files and support SMB encryption, with links to relevant documentation.
- Where VPN client options are discussed, clarify that Linux and macOS clients can connect to Azure VPN gateways using standard IPsec/IKE or OpenVPN protocols, and provide links to cross-platform setup guides.
- Ensure that any references to client-side encryption tools or methods include cross-platform options, not just those available on Windows.
- If command-line examples or tool references are added in future updates, provide both Windows (PowerShell) and Linux/macOS (bash, CLI) examples.
Security
Introduction to Azure security | Microsoft Docs
...s/blob/main/articles/security/fundamentals/overview.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation is generally cross-platform and highlights Azure's support for both Windows and Linux workloads. However, there are several instances where Windows/PowerShell tools and patterns are mentioned first or exclusively, such as in SQL VM TDE configuration (PowerShell cmdlets), IIS diagnostic features, and references to Windows-specific features in identity management tables. Linux equivalents or examples are not always provided, and Windows terminology sometimes appears before Linux alternatives.
Recommendations
- Where PowerShell or Windows-specific instructions are given (e.g., SQL VM TDE, App Service diagnostics), add equivalent CLI/bash or Linux-native examples if supported.
- When discussing diagnostic features (such as IIS trace logs), clarify Linux alternatives (e.g., Apache/Nginx logging) or note platform differences.
- In tables or feature lists that mention Windows-specific capabilities (e.g., Microsoft Entra join for Windows 10), clearly indicate platform applicability and provide parity notes for Linux/macOS where relevant.
- Ensure that examples and instructions for common tasks (backup, encryption, monitoring) explicitly mention support for Linux and provide links to Linux-specific guidance where available.